Bug 405781 – crash in Theme:

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 405781 - crash in Theme:


Summary:	crash in Theme:


Status:	RESOLVED DUPLICATE of bug 351001

Product:	gnome-control-center
Classification:	Core
Component:	[obsolete] theme-manager
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Thomas Wood
QA Contact:	Control-Center Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-02-08 16:13 UTC by chimpninja
Modified:	2007-02-08 16:54 UTC

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

Description chimpninja 2007-02-08 16:13:15 UTC

Version: 2.16.1

What were you doing when the application crashed?



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

Memory status: size: 34267136 vsize: 0 resident: 34267136 share: 0 rss: 15732736 rss_rlim: 0
CPU usage: start_time: 1170950943 rtime: 0 utime: 829 stime: 0 cutime:477 cstime: 0 timeout: 352 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-theme-manager'

(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 -1225189712 (LWP 13581)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 109048

Thread 1 (Thread -1225189712 (LWP 13581))

#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 strcmp
from /lib/tls/i686/cmov/libc.so.6
#5 g_str_equal
from /usr/lib/libglib-2.0.so.0
#6 g_hash_table_lookup
from /usr/lib/libglib-2.0.so.0
#7 g_quark_from_string
from /usr/lib/libglib-2.0.so.0
#8 gtk_rc_get_im_module_path
from /usr/lib/libgtk-x11-2.0.so.0
#9 gtk_rc_get_im_module_path
from /usr/lib/libgtk-x11-2.0.so.0
#10 gtk_rc_get_im_module_path
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_rc_get_im_module_path
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_rc_parse
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_rc_reparse_all_for_settings
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_rc_reparse_all
from /usr/lib/libgtk-x11-2.0.so.0
#15 g_cclosure_marshal_VOID__PARAM
from /usr/lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#20 g_object_class_override_property
from /usr/lib/libgobject-2.0.so.0
#21 g_enum_register_static
from /usr/lib/libgobject-2.0.so.0
#22 g_object_notify
from /usr/lib/libgobject-2.0.so.0
#23 _gtk_settings_handle_event
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#25 _gdk_events_init
from /usr/lib/libgdk-x11-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 main
#0 __kernel_vsyscall

Comment 1 Jens Granseuer 2007-02-08 16:54:58 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.

If the crash is reproducible, can you please install debugging symbols for gtk+ and glib, and attach a stacktrace with full debugging symbols to bug 351001?
Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!


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