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 417645 - crash in Terminal: Well, I was actually bei...
crash in Terminal: Well, I was actually bei...
Status: RESOLVED DUPLICATE of bug 399877
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-03-12 21:39 UTC by alexander.fairley
Modified: 2007-03-13 01:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description alexander.fairley 2007-03-12 21:39:23 UTC 
Version: 2.16.0

What were you doing when the application crashed?
Well, I was actually being distracted by an annoying person, and I looked back at the screen and saw bug buddy. It looks like all my terminals may have crashed which would be even more annoying than the person who was distracting me.


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:45:28 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Permissive
Accessibility: Disabled
----------- .xsession-errors (3532216 sec old) ---------------------
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
...Too much output, ignoring rest...
--------------------------------------------------

Memory status: size: 100515840 vsize: 0 resident: 100515840 share: 0 rss: 21221376 rss_rlim: 0
CPU usage: start_time: 1171913483 rtime: 0 utime: 2943 stime: 0 cutime:1650 cstime: 0 timeout: 1293 it_real_value: 0 frequency: 16756

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 -1208596784 (LWP 2374)]
[New Thread -1215259760 (LWP 2379)]
(no debugging symbols found)
0x00656402 in __kernel_vsyscall ()

+ Trace 118119

Thread 1 (Thread -1208596784 (LWP 2374))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gtk_widget_style_get_valist
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 gtk_widget_style_get
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 gtk_menu_bar_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 gtk_menu_bar_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 gtk_marshal_BOOLEAN__VOID
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 g_value_set_static_boxed
    from /lib/libgobject-2.0.so.0
  • #10 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #11 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #14 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gdk_window_is_viewable
    from /usr/lib/libgdk-x11-2.0.so.0
  • #17 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #18 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #19 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #20 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #21 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #23 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 g_cclosure_marshal_VOID__OBJECT
  • #25 __libc_start_main
    from /lib/libc.so.6
  • #26 g_cclosure_marshal_VOID__OBJECT
  • #0 __kernel_vsyscall 






Comment 1


Susana





          2007-03-13 01:17:18 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 399877 ***