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 414411 - crash in Terminal: i launched the applicati...
crash in Terminal: i launched the applicati...
Status: RESOLVED DUPLICATE of bug 353498
Product: gnome-terminal
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
: 421638 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-03-04 00:11 UTC by gnome-bugs
Modified: 2008-01-01 12:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description gnome-bugs 2007-03-04 00:11:38 UTC
Version: 2.16.1

What were you doing when the application crashed?
i launched the application


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

Memory status: size: 66625536 vsize: 0 resident: 66625536 share: 0 rss: 17534976 rss_rlim: 0
CPU usage: start_time: 1172956713 rtime: 0 utime: 3838 stime: 0 cutime:3546 cstime: 0 timeout: 292 it_real_value: 0 frequency: 36508

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 -1226291536 (LWP 17711)]
[New Thread -1268360288 (LWP 17719)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226291536 (LWP 17711))

  • #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 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_scrollbar_get_type
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 g_cclosure_marshal_VOID__OBJECT
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #13 gtk_widget_set_usize
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 _gtk_size_group_get_child_requisition
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 _gtk_size_group_compute_requisition
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_widget_size_request
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 gtk_hbox_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 g_cclosure_marshal_VOID__BOXED
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #24 _gtk_size_group_get_child_requisition
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 _gtk_size_group_compute_requisition
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 gtk_widget_size_request
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 ??
  • #28 ??
  • #29 ??
  • #30 ??
  • #31 ??
  • #32 ??
  • #33 ??
  • #0 __kernel_vsyscall

Comment 1 Susana 2007-03-24 15:07:44 UTC
*** Bug 421638 has been marked as a duplicate of this bug. ***
Comment 2 dechene 2007-05-03 12:39:02 UTC
I have a script that opens 16 gnome-terminal windows at once and ssh them to different computers.  About 1 in 10 times, one of the windows will crash on opening.  After this first window crashes, all subsequent windows will fail to open until I restart X.  I wonder if it's related . . . Very frustrating . . . 
Comment 3 Teppo Turtiainen 2008-01-01 12:43:51 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 353498 ***