GNOME Bugzilla – Bug 163430
Creating Profiles for Terminal
Last modified: 2005-09-18 19:43:39 UTC
Distribution: Debian testing/unstable Package: gnome-terminal Severity: normal Version: GNOME2.8.1 2.7.3 Gnome-Distributor: Ubuntu Synopsis: Creating Profiles for Terminal Bugzilla-Product: gnome-terminal Bugzilla-Component: general Bugzilla-Version: 2.7.3 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: I accidentially edited the default profile, instead of creating a new one. After saving the profile I had no default profile so I attempted to recreate the default profile. After selecting base on [new profile] and clicking on OK, system crashed. Steps to reproduce the crash: 1. Edit Default profile on Terminal 2. Close after editing then open another terminal 3. Create a new profile named Default and base it on the new profile Expected Results: System crashes How often does this happen? First time Additional Information: 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)...(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)...[Thread debugging using libthread_db enabled] [New Thread 1088301664 (LWP 5659)] [New Thread 1107446704 (LWP 5662)] [Thread debugging using libthread_db enabled] [New Thread 1088301664 (LWP 5659)] [New Thread 1107446704 (LWP 5662)] [Thread debugging using libthread_db enabled] [New Thread 1088301664 (LWP 5659)] [New Thread 1107446704 (LWP 5662)] (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)...0xffffe410 in __kernel_vsyscall ()
+ Trace 54289
Thread 1 (Thread 1088301664 (LWP 5659))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-01-09 03:51 ------- Unknown version 2.7.3 in product gnome-terminal. Setting version to "2.7.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-terminal". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was E1nstein@sbcglobal.net. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Hi, Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Should be fixed already. *** This bug has been marked as a duplicate of 122349 ***