Bug 359449 – crash in Terminal: I was doing absolutely n...

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 359449 - crash in Terminal: I was doing absolutely n...


Summary:	crash in Terminal: I was doing absolutely n...


Status:	RESOLVED DUPLICATE of bug 353498

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	GNOME Terminal Maintainers
QA Contact:	GNOME Terminal Maintainers

URL:
Whiteboard:

Duplicates:	427946 (view as bug list)
Depends on:
Blocks:

Reported:	2006-10-03 23:28 UTC by Johan Sköld
Modified:	2007-04-09 20:54 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Johan Sköld 2006-10-03 23:28:09 UTC

Version: 2.16.1

What were you doing when the application crashed?
I was doing absolutely nothing. Didn't even know I had it running. :S


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

Memory status: size: 86949888 vsize: 0 resident: 86949888 share: 0 rss: 11554816 rss_rlim: 0
CPU usage: start_time: 1159876604 rtime: 0 utime: 1014 stime: 0 cutime:885 cstime: 0 timeout: 129 it_real_value: 0 frequency: 742

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 -1226492240 (LWP 4889)]
[New Thread -1248064608 (LWP 5066)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 74385

Thread 1 (Thread -1226492240 (LWP 4889))

#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_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#7 gtk_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#8 gtk_notebook_popup_enable
from /usr/lib/libgtk-x11-2.0.so.0
#9 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#10 gtk_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_box_pack_start_defaults
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_widget_queue_resize
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_button_box_set_child_size
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_widget_reset_rc_styles
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_rc_get_theme_dir
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_icon_info_get_type
from /usr/lib/libgtk-x11-2.0.so.0
#25 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#26 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#27 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#28 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#29 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#30 ??
#31 ??
#32 _IO_stdin_used
#33 ??
#34 ??
#0 __kernel_vsyscall

Comment 1 Elijah Newren 2006-10-03 23:30:41 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.

Matches the stack trace in bug 357897, which has been marked as a duplicate of 353498

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

Comment 2 palfrey 2007-04-09 20:54:35 UTC

*** Bug 427946 has been marked as a duplicate of this bug. ***