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 383575 - crash in Terminal: i surfed in firefox whil...
crash in Terminal: i surfed in firefox whil...
Status: RESOLVED DUPLICATE of bug 361477
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-12-08 00:57 UTC by H.
Modified: 2007-01-19 22:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description H. 2006-12-08 00:57:15 UTC 
Version: 2.16.1

What were you doing when the application crashed?
i surfed in firefox while gnome-terminal sudden crashed


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

Memory status: size: 60678144 vsize: 0 resident: 60678144 share: 0 rss: 18599936 rss_rlim: 0
CPU usage: start_time: 1165515533 rtime: 0 utime: 5359 stime: 0 cutime:4559 cstime: 0 timeout: 800 it_real_value: 0 frequency: 112

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 -1226160464 (LWP 5343)]
[New Thread -1251193952 (LWP 5349)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 92447

Thread 1 (Thread -1226160464 (LWP 5343))

  • #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 IA__gtk_widget_style_get_valist
    at gtkwidget.c line 7590
  • #5 IA__gtk_widget_style_get
    at gtkwidget.c line 7624
  • #6 gtk_widget_get_draw_rectangle
    at gtkwidget.c line 2677
  • #7 widget_add_child_draw_rectangle
    at gtkwidget.c line 2663
  • #8 gtk_bin_forall
    at gtkbin.c line 133
  • #9 IA__gtk_container_forall
    at gtkcontainer.c line 1261
  • #10 gtk_widget_get_draw_rectangle
    at gtkwidget.c line 2689
  • #11 gtk_widget_queue_shallow_draw
    at gtkwidget.c line 2960
  • #12 IA__gtk_widget_queue_resize
    at gtkwidget.c line 2789
  • #13 gtk_widget_set_style_internal
    at gtkwidget.c line 5148
  • #14 reset_rc_styles_recurse
    at gtkwidget.c line 5348
  • #15 gtk_box_forall
    at gtkbox.c line 670
  • #16 IA__gtk_container_forall
    at gtkcontainer.c line 1261
  • #17 reset_rc_styles_recurse
    at gtkwidget.c line 5351
  • #18 gtk_notebook_forall
    at gtknotebook.c line 3793
  • #19 IA__gtk_container_forall
    at gtkcontainer.c line 1261
  • #20 reset_rc_styles_recurse
    at gtkwidget.c line 5351
  • #21 gtk_box_forall
    at gtkbox.c line 680
  • #22 IA__gtk_container_forall
    at gtkcontainer.c line 1261
  • #23 reset_rc_styles_recurse
    at gtkwidget.c line 5351
  • #24 gtk_bin_forall
    at gtkbin.c line 133
  • #25 IA__gtk_container_forall
    at gtkcontainer.c line 1261
  • #26 reset_rc_styles_recurse
    at gtkwidget.c line 5351
  • #27 IA__gtk_widget_reset_rc_styles
    at gtkwidget.c line 5361
  • #28 gtk_rc_reset_widgets
    at gtkrc.c line 1606
  • #29 reset_styles_idle
    at gtkicontheme.c line 602
  • #30 g_idle_dispatch
    at gmain.c line 3926
  • #31 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #32 g_main_context_iterate
    at gmain.c line 2677
  • #33 IA__g_main_loop_run
    at gmain.c line 2881
  • #34 IA__gtk_main
    at gtkmain.c line 1024
  • #35 ??
  • #36 ??
  • #37 _IO_stdin_used
  • #38 ??
  • #39 ??
  • #0 __kernel_vsyscall 






Comment 1


Mariano Suárez-Alvarez





          2006-12-08 20:10:27 UTC
        



This is very, very similar to the stack in bug 361477...






Comment 2


Mariano Suárez-Alvarez





          2007-01-19 22:42:47 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 361477 ***