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 430324 - crash in Terminal:
crash in Terminal:
Status: RESOLVED DUPLICATE of bug 352444
Product: gnome-terminal
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-16 14:45 UTC by rpm
Modified: 2007-04-16 15:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description rpm 2007-04-16 14:45:38 UTC
Version: 2.16.1

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 178409472 vsize: 0 resident: 178409472 share: 0 rss: 133951488 rss_rlim: 0
CPU usage: start_time: 1175611706 rtime: 0 utime: 183783 stime: 0 cutime:123668 cstime: 0 timeout: 60115 it_real_value: 0 frequency: 0

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 -1226262864 (LWP 18762)]
[New Thread -1249670240 (LWP 18768)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226262864 (LWP 18762))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 ORBit_RootObject_duplicate_T
    from /usr/lib/libORBit-2.so.0
  • #11 CORBA_free
    from /usr/lib/libORBit-2.so.0
  • #12 CORBA_free
    from /usr/lib/libORBit-2.so.0
  • #13 ORBit_free_T
    from /usr/lib/libORBit-2.so.0
  • #14 ORBit_free
    from /usr/lib/libORBit-2.so.0
  • #15 CORBA_free
    from /usr/lib/libORBit-2.so.0
  • #16 gnome_accessibility_module_shutdown
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #17 gnome_accessibility_module_shutdown
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #18 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #21 atk_object_notify_state_change
    from /usr/lib/libatk-1.0.so.0
  • #22 gail_widget_new
    from /usr/lib/gtk-2.0/modules/libgail.so
  • #23 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #25 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #26 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #28 vte_terminal_accessible_get_type
    from /usr/lib/libvte.so.9
  • #29 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #31 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #32 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #33 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #34 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 gtk_window_set_auto_startup_notification
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 ??
  • #37 ??
  • #38 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 ??
  • #40 ??
  • #41 ??
  • #42 _gtk_window_set_is_active
    from /usr/lib/libgtk-x11-2.0.so.0
  • #0 __kernel_vsyscall

Comment 1 palfrey 2007-04-16 15:13:09 UTC
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 352444 ***