Bug 351001 – crash on 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 351001 - crash on Theme


Summary:	crash on Theme


Status:	RESOLVED INCOMPLETE

Product:	gtk+
Classification:	Platform
Component:	.General
Version:	2.10.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	gtk-bugs
QA Contact:	gtk-bugs

URL:
Whiteboard:

Duplicates:	361855 368685 376220 405781 (view as bug list)
Depends on:
Blocks:

Reported:	2006-08-12 06:35 UTC by cprofiriu
Modified:	2009-03-08 21:17 UTC

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

Description cprofiriu 2006-08-12 06:35:34 UTC

What were you doing when the application crashed?



Distribution: Fedora Core release 5.91 (FC6 Test2)
Gnome Release: 2.15.90 2006-08-03 (Red Hat, Inc)
BugBuddy Version: 2.15.90

Memory status: size: 80670720 vsize: 0 resident: 80670720 share: 0 rss: 16429056 rss_rlim: 0
CPU usage: start_time: 1155375386 rtime: 0 utime: 506 stime: 0 cutime:354 cstime: 0 timeout: 152 it_real_value: 0 frequency: 2

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208895792 (LWP 7996)]
(no debugging symbols found)
0xb7f3a402 in __kernel_vsyscall ()

+ Trace 70280

Thread 1 (Thread -1208895792 (LWP 7996))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 strcmp
from /lib/libc.so.6
#5 g_str_equal
from /lib/libglib-2.0.so.0
#6 g_hash_table_lookup
from /lib/libglib-2.0.so.0
#7 g_quark_from_string
from /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 /lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /lib/libgobject-2.0.so.0
#17 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#19 g_signal_emit
from /lib/libgobject-2.0.so.0
#20 g_object_class_override_property
from /lib/libgobject-2.0.so.0
#21 g_enum_register_static
from /lib/libgobject-2.0.so.0
#22 g_object_notify
from /lib/libgobject-2.0.so.0
#23 gtk_settings_get_for_screen
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_add_client_message_filter
from /usr/lib/libgdk-x11-2.0.so.0
#26 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#27 g_main_context_check
from /lib/libglib-2.0.so.0
#28 g_main_loop_run
from /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 Damien Durand 2006-08-12 10:57:37 UTC

Thank you for taking the time to report this bug. This bug report isn't very
useful because it doesn't describe the bug well. If you have time, please add a description to this repport.

Comment 2 Thomas Wood 2006-09-24 00:13:41 UTC

Could be a duplicate of bug 349888. Both crash shortly after calling gnome_gtk_module_info_get()

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

Comment 3 Thomas Wood 2006-09-30 16:43:27 UTC

Re-opening. This wasn't a duplicate of bug 349888.

Comment 4 Elijah Newren 2006-10-13 05:46:32 UTC

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

Comment 5 Thomas Wood 2006-10-15 15:18:12 UTC

No mention of gnome-theme-manager in the stack trace, only GTK+ and glib, so assuming a GTK+ bug?

Comment 6 Mariano Suárez-Alvarez 2006-11-01 03:33:32 UTC

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

Comment 7 André Klapper 2006-11-17 16:15:28 UTC

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

Comment 8 André Klapper 2006-11-17 16:16:09 UTC

(confirming.)

Comment 9 Jens Granseuer 2007-02-08 16:54:58 UTC

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

Comment 10 Matthias Clasen 2007-03-10 00:04:40 UTC

Needs a stack trace with symbols.

Comment 11 André Klapper 2008-11-15 17:35:53 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash.

If this is still an issue in gtk 2.12:
Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!

Comment 12 Tobias Mueller 2009-03-08 21:17:44 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!