GNOME Bugzilla – Bug 329702
Gnome-terminal Crash with editing profiles
Last modified: 2006-05-16 11:30:39 UTC
From: Geert Altena <geert@suespammers.org> To: submit@bugs.gnome.org X-Mailer: bug-buddy 2.13.0 Subject: Crash with editing profiles Distribution: Ubuntu 6.04 (dapper) Package: gnome-terminal Severity: Normal Version: GNOME2.13.90 2.13.90 Gnome-Distributor: Ubuntu Synopsis: Crash with editing profiles Bugzilla-Product: gnome-terminal Bugzilla-Component: general Bugzilla-Version: 2.13.90 BugBuddy-GnomeVersion: 2.0 (2.13.3) Description: Description of the crash: Steps to reproduce the crash: 1. select 'profiles' from 'Edit' menu 2. select default profile (just selecting) 3. click close Expected Results: Return to program How often does this happen? Every time Additional Information: It does not happen when: - closing the profile window without selecting the default profile (i.e. omitting step 2) - selecting the default profile, then clicking 'Edit' to edit it. After closing the Edit window the Profile window can be close without crashing 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) [Thread debugging using libthread_db enabled] [New Thread 46912590443952 (LWP 5165)] [New Thread 1082399072 (LWP 5174)] [New Thread 1082132832 (LWP 5168)] (no debugging symbols found) 0x00002aaaacaaf0ca in waitpid () from /lib/libpthread.so.0
+ Trace 65872
Thread 1 (Thread 46912590443952 (LWP 5165))
------- Bug created by bug-buddy at 2006-02-03 03:18 ------- Unknown version 2.13.90 in product gnome-terminal. Setting version to "2.13.x".
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.
Occurs only when /desktop/gnome/interface/accessibility is enabled/checked (using gconfi-editor) Apparently it's related to libatk-bridge.so. See http://ubuntuforums.org/showthread.php?t=125001 for more info. Not only gnome-termnal is affected, also synaptic so most likely it's a much wider issue than gnome-terminal. Is it still usefull to get a trace from a debugging symbols enabled gnometerminal?
For what I could see in Launchpad, this is a problem with Ubuntu's packages. Would you please fetch the latest versions of them all and tell me whether that fixes the problems you've experienced?
Duplicate of bug 325759. *** This bug has been marked as a duplicate of 325759 ***