Bug 372759 – crash in Theme: trying to add DarkX-2s t...

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 372759 - crash in Theme: trying to add DarkX-2s t...


Summary:	crash in Theme: trying to add DarkX-2s t...


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-09 01:05 UTC by henry.kelderman
Modified:	2006-11-09 19:43 UTC

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

Description henry.kelderman 2006-11-09 01:05:28 UTC

Version: 2.16.1

What were you doing when the application crashed?
trying to add DarkX-2s theme to Themes (tarball)


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

Memory status: size: 82100224 vsize: 0 resident: 82100224 share: 0 rss: 17186816 rss_rlim: 0
CPU usage: start_time: 1163120489 rtime: 0 utime: 197 stime: 0 cutime:181 cstime: 0 timeout: 16 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/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225390416 (LWP 7164)]
[New Thread -1267549280 (LWP 7175)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 84586

Thread 1 (Thread -1225390416 (LWP 7164))

#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 André Klapper 2006-11-09 19:43:41 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 issue is fixed in version 2.16.2.

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