Bug 416942 – 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 416942 - crash in Theme:


Summary:	crash in Theme:


Status:	RESOLVED DUPLICATE of bug 349471

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-03-10 23:49 UTC by socrates_pina
Modified:	2007-03-11 00:39 UTC

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

Description socrates_pina 2007-03-10 23:49:48 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: 68792320 vsize: 0 resident: 68792320 share: 0 rss: 18669568 rss_rlim: 0
CPU usage: start_time: 1173570506 rtime: 0 utime: 1187 stime: 0 cutime:1037 cstime: 0 timeout: 150 it_real_value: 0 frequency: 239

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 -1225791824 (LWP 5436)]
[New Thread -1254409312 (LWP 5520)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 117576

Thread 1 (Thread -1225791824 (LWP 5436))

#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 strrchr
from /lib/tls/i686/cmov/libc.so.6
#5 g_path_get_dirname
from /usr/lib/libglib-2.0.so.0
#6 gnome_theme_details_reread_themes_from_disk
#7 main
#0 __kernel_vsyscall

Comment 1 Pedro Villavicencio 2007-03-11 00:39:56 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.


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