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


Summary:	crash on Theme


Status:	RESOLVED INCOMPLETE

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-08-04 06:25 UTC by hlevyn
Modified:	2007-02-24 11:44 UTC

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

Description hlevyn 2006-08-04 06:25:34 UTC

What were you doing when the application crashed?
Going through various themes in the theme manager


Distribution: Gentoo Base System version 1.12.4
Gnome Release: 2.15.90 2006-08-02 (Gentoo)
BugBuddy Version: 2.15.90

Memory status: size: 37076992 vsize: 0 resident: 37076992 share: 0 rss: 14667776 rss_rlim: 0
CPU usage: start_time: 1154672678 rtime: 0 utime: 161 stime: 0 cutime:151 cstime: 0 timeout: 10 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/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1228810576 (LWP 18295)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 69959

Thread 1 (Thread -1228810576 (LWP 18295))

#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 ??
#4 ??
#0 __kernel_vsyscall

Comment 1 Sebastien Bacher 2006-08-04 08:19:23 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

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

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

Comment 3 Thomas Wood 2006-09-24 00:16:39 UTC

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

Comment 4 Thomas Wood 2006-10-02 21:50:24 UTC

The previous two bugs where not actually duplicates in the end. The stack trace here is virtually useless, so I'm going close this bug report as no further information has been provided. Please feel free to re-open this bug if you still experiance the problem, or can provide a better stack trace.

Comment 5 Felix Riemann 2007-02-24 11:44:51 UTC

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