You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Configuring gnome-terminal requires that <name> in profile.<name>.<option> be a UUID (any UUID works), but this is not documented. If it is anything other than a UUID then the profile will not be shown in the options or activated (even if it is marked as default).
For example, the following configuration correctly creates a profile whose visible name is "profile1":
I discovered this by running dconf watch /org/gnome/terminal/legacy/profiles:/ and then manually creating a new profile named "MyProfile". I got the following output:
The profile only seems to be created when the <name> in /org/gnome/terminal/legacy/profiles:/:<name>/visible-name is a UUID.
A fix for this could be to document that <name> must be a UUID.
Alternatively, given that <name> in profile.<name>.<option> doesn't have any good use other than to be a UUID, the following could be done:
the profile.<name>.visibleName option is removed;
<name> in profile.<name>.<option> is used to set /org/gnome/terminal/legacy/profiles:/:<UUID>/visible-name;
<name> in profile.<name>.<option> is passed to something akin to uuidgen --sha1 --namespace '@oid' --name profile.<name> to deterministically generate the UUID in /org/gnome/terminal/legacy/profiles:/:<UUID>/ for the profile.
I'm not sure about automatically generating the UUID, I think that would cause unnecessary breakage and also would require IFD, which we generally want to avoid.
Thank you for your contribution!
I marked this issue as stale due to inactivity.
Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'.
We welcome additional information that will help resolve this issue.
Please read the relevant sections below before commenting.
If you are the original author of the issue
If this is resolved, please consider closing it so that the maintainers know not to focus on this.
If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough.
If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.
If you are not the original author of the issue
If you are also experiencing this issue, please add details of your situation to help with the debugging process.
If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.
Memorandum on closing issues
Don't be afraid to manually close an issue, even if it holds valuable information.
Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost!
Closing obsolete issues is an important way to help maintainers focus their time and effort.
I think this got resolved in f58889c. Basically, the programs.gnome-terminal.profile option description now state that the name has to be an UUID. And there is an assertion verifying that they are UUIDs.
I'll close the issue, if you feel this is incorrect then feel free to comment and we'll reopen.
Are you following the right branch?
Is there an existing issue for this?
Issue description
Configuring gnome-terminal requires that
<name>
inprofile.<name>.<option>
be a UUID (any UUID works), but this is not documented. If it is anything other than a UUID then the profile will not be shown in the options or activated (even if it is marked as default).For example, the following configuration correctly creates a profile whose visible name is "profile1":
I discovered this by running
dconf watch /org/gnome/terminal/legacy/profiles:/
and then manually creating a new profile named "MyProfile". I got the following output:If, in the configuration, I replace
profile."060efe23-3ab4-4c71-8a38-dd13f89b400d"
withprofile.profile1
, I get the following output from dconf:The profile only seems to be created when the
<name>
in/org/gnome/terminal/legacy/profiles:/:<name>/visible-name
is a UUID.A fix for this could be to document that
<name>
must be a UUID.Alternatively, given that
<name>
inprofile.<name>.<option>
doesn't have any good use other than to be a UUID, the following could be done:profile.<name>.visibleName
option is removed;<name>
inprofile.<name>.<option>
is used to set/org/gnome/terminal/legacy/profiles:/:<UUID>/visible-name
;<name>
inprofile.<name>.<option>
is passed to something akin touuidgen --sha1 --namespace '@oid' --name profile.<name>
to deterministically generate the UUID in/org/gnome/terminal/legacy/profiles:/:<UUID>/
for the profile.Maintainer CC
@kamadorueda @rycee
System information
The text was updated successfully, but these errors were encountered: