Bug 356434 – crash in Terminal: Opening evolution overto...

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 356434 - crash in Terminal: Opening evolution overto...


Summary:	crash in Terminal: Opening evolution overto...


Status:	RESOLVED DUPLICATE of bug 348979

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:

Depends on:
Blocks:

Reported:	2006-09-17 19:15 UTC by Kevin Kubasik
Modified:	2006-09-17 19:49 UTC

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

Description Kevin Kubasik 2006-09-17 19:15:43 UTC

Version: 2.16.0

What were you doing when the application crashed?
Opening evolution overtop of it with Xgl and compiz enabled.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 51146752 vsize: 0 resident: 51146752 share: 0 rss: 18505728 rss_rlim: 0
CPU usage: start_time: 1158450078 rtime: 0 utime: 3211 stime: 0 cutime:2659 cstime: 0 timeout: 552 it_real_value: 0 frequency: 54894

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 -1208228176 (LWP 7437)]
[New Thread -1231193184 (LWP 7442)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 72595

Thread 1 (Thread -1208228176 (LWP 7437))

#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 g_type_check_is_value_type
from /usr/lib/libgobject-2.0.so.0
#5 g_value_type_compatible
from /usr/lib/libgobject-2.0.so.0
#6 g_object_class_override_property
from /usr/lib/libgobject-2.0.so.0
#7 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#8 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#9 gtk_widget_set_style_internal
at gtkwidget.c line 5131
#10 reset_rc_styles_recurse
at gtkwidget.c line 5338
#11 IA__gtk_widget_reset_rc_styles
at gtkwidget.c line 5351
#12 gtk_rc_reset_widgets
at gtkrc.c line 1606
#13 reset_styles_idle
at gtkicontheme.c line 602
#14 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#15 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#16 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#17 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#18 IA__gtk_main
at gtkmain.c line 1024
#19 ??
#20 ??
#21 _IO_stdin_used
#22 ??
#23 ??
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-09-17 19:34:38 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 bug 348979, which is a duplicate of bug 348814.

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

Comment 2 Karsten Bräckelmann 2006-09-17 19:43:20 UTC

Sorry for the stock response, Kevin. ;)

Comment 3 Karsten Bräckelmann 2006-09-17 19:49:01 UTC

Moving around. Sorry for the noise.


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

Comment 4 Kevin Kubasik 2006-09-17 19:49:46 UTC

No worries, I do enough work with bugzilla to be over it. Glad you guys already know about the bug ;)