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 374883 - crash in Terminal: Asleep! - carshed overni...
crash in Terminal: Asleep! - carshed overni...
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: 2006-11-13 21:56 UTC by kansei60
Modified: 2006-11-14 15:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description kansei60 2006-11-13 21:56:06 UTC 
Version: 2.16.0

What were you doing when the application crashed?
Asleep! - carshed overnight..  Terminal is 'constantly' crashing since FC 6


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:36:14 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Enabled

Memory status: size: 202993664 vsize: 0 resident: 202993664 share: 0 rss: 66510848 rss_rlim: 0
CPU usage: start_time: 1163397369 rtime: 0 utime: 381041 stime: 0 cutime:351216 cstime: 0 timeout: 29825 it_real_value: 0 frequency: 0

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 -1208981808 (LWP 2971)]
[New Thread -1231082608 (LWP 2976)]
(no debugging symbols found)
0x00761402 in __kernel_vsyscall ()

+ Trace 86198

Thread 1 (Thread -1208981808 (LWP 2971))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/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/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /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_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #21 atk_object_notify_state_change
    from /usr/lib/libatk-1.0.so.0
  • #22 vte_terminal_accessible_get_type
    from /usr/lib/libvte.so.9
  • #23 gtk_marshal_BOOLEAN__VOID
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #25 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #26 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #27 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #28 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 gdk_add_client_message_filter
    from /usr/lib/libgdk-x11-2.0.so.0
  • #31 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #32 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #33 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #34 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 g_cclosure_marshal_VOID__OBJECT
  • #36 __libc_start_main
    from /lib/libc.so.6
  • #37 g_cclosure_marshal_VOID__OBJECT
  • #0 __kernel_vsyscall 






Comment 1


Fabio Bonelli





          2006-11-14 15:52:57 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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