Bug 368955 – crash in Theme: adding a new icon set

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 368955 - crash in Theme: adding a new icon set


Summary:	crash in Theme: adding a new icon set


Status:	RESOLVED DUPLICATE of bug 352490

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:	2006-11-01 17:17 UTC by ronnie.henry
Modified:	2006-11-02 00:23 UTC

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

Description ronnie.henry 2006-11-01 17:17:38 UTC

Version: 2.16.1

What were you doing when the application crashed?
adding a new icon set


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

Memory status: size: 43585536 vsize: 0 resident: 43585536 share: 0 rss: 16076800 rss_rlim: 0
CPU usage: start_time: 1162401194 rtime: 0 utime: 598 stime: 0 cutime:436 cstime: 0 timeout: 162 it_real_value: 0 frequency: 10

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 -1226013008 (LWP 12272)]
[New Thread -1238283360 (LWP 12469)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 81513

Thread 1 (Thread -1226013008 (LWP 12272))

#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 free
from /lib/tls/i686/cmov/libc.so.6
#5 g_free
from /usr/lib/libglib-2.0.so.0
#6 gnome_theme_installer_run_cb
#7 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#8 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#12 file_transfer_dialog_wrap_async_xfer
#13 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#14 ??
#15 ??
#16 ??
#17 g_slice_alloc
from /usr/lib/libglib-2.0.so.0
#18 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#19 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#20 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#21 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#22 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#23 main
#0 __kernel_vsyscall

Comment 1 Thomas Wood 2006-11-01 17:43:38 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. 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. Thanks in advance!


Also a duplicate of bug 352490, but please do provide a new stack trace if you can as I haven't yet been able to reproduce this bug. Which icon theme were you trying to install?

Comment 2 Karsten Bräckelmann 2006-11-02 00:23:09 UTC

Yes, definitely the same issue as bug 352490.

Thomas, if you need more info on bug 352490, set it's status accordingly. While in NEW state, the bugsquad does not know you need more info and hence does not request it when closing duplicates. Doing so for you now.

Ronnie, the need for more info still stands. :)


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