GNOME Bugzilla – Bug 324227
Gnome Terminal crashes on recreation of Default profile after renaming original Default profile to new name
Last modified: 2007-11-27 02:56:06 UTC
Distribution: Debian 3.1 Package: gnome-terminal Severity: normal Version: GNOME2.8.3 2.8.2 Gnome-Distributor: Debian Synopsis: Gnome Terminal crashes on recreation of Default profile after renaming original Default profile to new name Bugzilla-Product: gnome-terminal Bugzilla-Component: general Bugzilla-Version: 2.8.2 BugBuddy-GnomeVersion: 2.0 (2.8.1) Description: Description of the crash: Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-terminal' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 3711)] [New Thread 32769 (LWP 3714)] [New Thread 16386 (LWP 3715)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x407cec0b in waitpid () from /lib/libpthread.so.0
+ Trace 64638
Thread 1 (Thread 16384 (LWP 3711))
------- Bug moved to this database by unknown@gnome.bugs 2005-12-16 00:23 UTC ------- Unknown version 2.8.2 in product gnome-terminal. Setting version to "2.8.x". The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was katokop1+bugbuddy@gmail.com.
Unique stacktrace according to simple-dup-finder. Marking new.
Created attachment 56148 [details] [review] bug324227.diff The crash also happens with other profiles than "Default". How to reproduce : 1. Open gnome-terminal 2. Create a new profile named "bart", works fine 3. Rename profile "bart" to "bart2" 4. Create a new profile named "bart", crashes Note that between steps 3 and 4 the list of profiles in the menu option "Terminal->Change Profile" is not updated. The patch disables renaming an existing profile. Renaming a profile is not really needed, because it's very easy to create a new profile based on an old profile, and then delete the old profile.
Thanks for the patch. However, if gnome-terminal crashes due to renaming, the cause should be fixed. The solution should not be to just disable whatever is crashing.
Just as a comment, this is due to the fact that a profile only has its visible_name key updated when it is renamed, but the directory in gconf keeps the old name. There's no straight-forward fix for this, except for not having the directories the profile name (calling them profile_1, profile_2, etc). I'm still thinking about the best way to solve this, and hence this will be left for 2.16.
*** Bug 342099 has been marked as a duplicate of this bug. ***
*** Bug 402283 has been marked as a duplicate of this bug. ***
*** Bug 399046 has been marked as a duplicate of this bug. ***
*** Bug 402092 has been marked as a duplicate of this bug. ***
*** Bug 461152 has been marked as a duplicate of this bug. ***
At risk of possibly stating the obvious, this doesn't happen if I make a profile with the same name as one that was created and deleted in the same session, and renaming existing profiles doesn't seem to be affected. Also, another minor bug that could be related: if I make two profiles with the same name in the same session, I don't get warned about the name clash on creating the second one.
I notice that if I create a profile named "Test" and then create another profile named "Test", I get a pop-up that says "You already have a profile called "Test". DO you want to create another profile with the same name?". If I pick "Yes", I get a crash in gnome-terminal 2.20. I see this warning echoed to the xterm terminal where I launched gnome-terminal: ** (gnome-terminal:2048): CRITICAL **: file terminal-profile.c: line 377: assertion `terminal_profile_lookup (name) == NULL' failed
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 499797 ***