Bug 163487 – gnome-theme-manager crashes on start (bt w/symbols included)

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 163487 - gnome-theme-manager crashes on start (bt w/symbols included)


Summary:	gnome-theme-manager crashes on start (bt w/symbols included)


Status:	RESOLVED DUPLICATE of bug 149236

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

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Control-Center Maintainers
QA Contact:	Control-Center Maintainers

URL:
Whiteboard:

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

Reported:	2005-01-09 19:17 UTC by Bryan Hundven
Modified:	2005-01-27 02:40 UTC

See Also:
GNOME target:	---
GNOME version:	2.9/2.10

Description Bryan Hundven 2005-01-09 19:17:22 UTC

This bug may be associated with 163480.
control-center-2.9.3
Just after I submited that bug, This started to happen.
-------backtrace---------
Backtrace was generated from '/home/bryan/garnome/bin/gnome-theme-manager'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1223469120 (LWP 21414)]
0xb747e4ee in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 54312

Thread 1 (Thread -1223469120 (LWP 21414))

#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#1 libgnomeui_segv_handle
at gnome-ui-init.c line 741
#2 <signal handler called>
#3 IA__g_str_hash
at gstring.c line 77
#4 IA__g_hash_table_lookup
at ghash.c line 193
#5 top_theme_dir_changed
at gnome-theme-info.c line 949
#6 actually_dispatch_callback
at gnome-vfs-monitor.c line 271
#7 g_idle_dispatch
at gmain.c line 3821
#8 g_main_dispatch
at gmain.c line 1947
#9 IA__g_main_context_dispatch
at gmain.c line 2497
#10 g_main_context_iterate
at gmain.c line 2578
#11 IA__g_main_loop_run
at gmain.c line 2782
#12 IA__gtk_main
at gtkmain.c line 963
#13 main
at gnome-theme-manager.c line 1470
#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0

Comment 1 Bryan Hundven 2005-01-09 19:19:57 UTC

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

Comment 2 Andrew Sobala 2005-01-09 19:21:28 UTC

What do you do to trigger the crash? Is it reproducable?

Comment 3 Bryan Hundven 2005-01-09 19:23:25 UTC

I just start it.
--
Is there a problem with bugzilla or is it just me?
Every bug I post is in duplicate.

Comment 4 Andrew Sobala 2005-01-09 19:28:22 UTC

(It's just you, actually. How curious.)

Comment 5 Bryan Hundven 2005-01-10 09:44:48 UTC

So, I guess opening (3x) and closing it (2x) from a fresh startup (no gnome
related processes running) reveils the error for me.
This happens even after the patch from bug 161649:
http://bugzilla.gnome.org/attachment.cgi?id=35527
has been applied.

Comment 6 Kjartan Maraas 2005-01-11 17:07:35 UTC

I've seen this backtrace from a bunch of capplets too. And I also got it from
gpdf today when opening a pdf file. Seems like something is scribbling on
someone elses memory bits somewhere?

Comment 7 Kjartan Maraas 2005-01-27 02:40:46 UTC

Possible fix in bug #149236. This is a duplicate of that so I'm marking it as such.

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