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 329702 - Gnome-terminal Crash with editing profiles
Gnome-terminal Crash with editing profiles
Status: RESOLVED DUPLICATE of bug 325759
Product: gnome-terminal
Classification: Core
Component: general
2.13.x
Other other
: High critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-02-03 03:18 UTC by geert
Modified: 2006-05-16 11:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description geert 2006-02-03 03:18:42 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

Thread 1 (Thread 46912590443952 (LWP 5165))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #4 g_log
    from /usr/lib/libglib-2.0.so.0
  • #5 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #6 gail_tree_view_new
    from /usr/lib/gtk-2.0/modules/libgail.so
  • #7 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #10 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 ??
  • #12 __libc_start_main
    from /lib/libc.so.6
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #0 waitpid
    from /lib/libpthread.so.0




------- 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".

Comment 1 Fabio Bonelli 2006-02-03 09:39:44 UTC
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.
Comment 2 geert 2006-02-04 14:13:12 UTC
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?
Comment 3 Guilherme de Siqueira Pastore 2006-03-12 15:43:25 UTC
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?
Comment 4 Fabio Bonelli 2006-05-16 11:30:39 UTC
Duplicate of bug 325759.

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