After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 158031 - Creating new profile changes all running instances to new profile
Creating new profile changes all running instances to new profile
Status: RESOLVED DUPLICATE of bug 125660
Product: gnome-terminal
Classification: Core
Component: general
2.8.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-11-12 11:03 UTC by Markus Bertheau
Modified: 2005-09-19 11:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description Markus Bertheau 2004-11-12 11:03:08 UTC
I don't know whether all of these steps are really neccessary, but they
illustrate the point.

1. Have two gnome-terminals open, only one profile.
2. Create a new profile. Say the new profile has a different background color.
3. Make sure that the default profile for new terminals is still the profile
'Default'.
4. Close the profile dialog.
5. Observe that the other terminal (i.e. the one you didn't click in to get to
the profiles menu) is set to the new profile too.

Expected behaviour:

Only the terminal that I used to create the new profile in is set to the new
profile after I finish creating that new profile.
Comment 1 Caleb Groom 2004-11-13 02:56:45 UTC
Markus, thanks for the report.  I'm confirming the bug so that the developers
will have a better shot at looking at the report.  I was not able to find any
duplicate reports.

I too have the same expected behavior.  Mainly because chaning the profile in
one termial via the menu will not also change the profile of all of the open
terminals.
Comment 2 Olav Vitters 2005-01-03 22:54:42 UTC
Might be related to bug 125660
Comment 3 Kjartan Maraas 2005-09-19 11:26:49 UTC
Fixed by the patch in bug 125660.

*** This bug has been marked as a duplicate of 125660 ***