GNOME Bugzilla – Bug 343336
Crashes while creates new profile with already used name
Last modified: 2007-01-28 11:55:31 UTC
Distribution: Debian 3.1 (sarge) Package: gnome-terminal Severity: Normal Version: GNOME2.14.1 2.14.1 Gnome-Distributor: Debian Synopsis: Crashes while creates new profile with already used name Bugzilla-Product: gnome-terminal Bugzilla-Component: general Bugzilla-Version: 2.14.1 BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: Crash occurs after positive answer to question if i am sure to create profile with same name that is already in use. Steps to reproduce the crash: 1. Create profile 2. Create profile with same name Expected Results: Create profile with duplicit name or insist on a new name. How often does this happen? It was not always reproducible at beginning but now (after 2 or 3 crashes) it is. Additional Information: I have 13 ore more profiles. Debugging Information: Backtrace was generated from '/usr/bin/gnome-terminal' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1494267680 (LWP 19524)] [New Thread -1507755088 (LWP 19527)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 68524
Thread 1 (Thread -1494267680 (LWP 19524))
------- Bug created by bug-buddy at 2006-05-29 22:08 ------- Unknown version 2.14.1 in product gnome-terminal. Setting version to "2.14.x".
Confirming.
Don't know if this is useful or not, but one of the extra comments from bug 344808 looked interesting and showed that this might happen accidentally more often than we'd expect: Actually it matched a profile I did have, but it wasn't showing up in the dialog box, so I figured I must have deleted it.
*** Bug 344808 has been marked as a duplicate of this bug. ***
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. Marking this a duplicate of a newer bug 363609 with more information. *** This bug has been marked as a duplicate of 363609 ***