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 408180 - crash in Terminal: Tried to select a differ...
crash in Terminal: Tried to select a differ...
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-02-15 10:32 UTC by kai-ubuntu-bug
Modified: 2007-02-15 17:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description kai-ubuntu-bug 2007-02-15 10:32:00 UTC
Version: 2.16.1

What were you doing when the application crashed?
Tried to select a different tab


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

Memory status: size: 155287552 vsize: 0 resident: 155287552 share: 0 rss: 47792128 rss_rlim: 0
CPU usage: start_time: 1170911960 rtime: 0 utime: 428801 stime: 0 cutime:121083 cstime: 0 timeout: 307718 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 -1226783056 (LWP 30893)]
[New Thread -1271039072 (LWP 30897)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226783056 (LWP 30893))

  • #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 ??
  • #0 __kernel_vsyscall

Comment 1 Mariano Suárez-Alvarez 2007-02-15 17:57:20 UTC
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.


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