Bug 403424 – crash in Theme: agregando un tema

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 403424 - crash in Theme: agregando un tema


Summary:	crash in Theme: agregando un tema


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:	2007-02-02 01:31 UTC by bayar02
Modified:	2007-02-02 08:18 UTC

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

Description bayar02 2007-02-02 01:31:20 UTC

Version: 2.16.0

What were you doing when the application crashed?
agregando un tema


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 113700864 vsize: 0 resident: 113700864 share: 0 rss: 14757888 rss_rlim: 0
CPU usage: start_time: 1170379545 rtime: 0 utime: 5693 stime: 0 cutime:4184 cstime: 0 timeout: 1509 it_real_value: 0 frequency: 295

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)
[Thread debugging using libthread_db enabled]
[New Thread -1208527152 (LWP 16214)]
[New Thread -1270891632 (LWP 16260)]
(no debugging symbols found)
0x0035c402 in __kernel_vsyscall ()

+ Trace 107268

Thread 1 (Thread -1208527152 (LWP 16214))

#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 <signal handler called>
#4 free
from /lib/libc.so.6
#5 g_free
from /lib/libglib-2.0.so.0
#6 gnome_theme_installer_run_cb
#7 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#8 g_closure_invoke
from /lib/libgobject-2.0.so.0
#9 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#11 g_signal_emit
from /lib/libgobject-2.0.so.0
#12 file_transfer_dialog_wrap_async_xfer
#13 gnome_vfs_async_get_job_limit
from /usr/lib/libgnomevfs-2.so.0
#14 gnome_vfs_async_get_job_limit
from /usr/lib/libgnomevfs-2.so.0
#15 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#16 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#17 g_main_context_check
from /lib/libglib-2.0.so.0
#18 g_main_loop_run
from /lib/libglib-2.0.so.0
#19 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#20 main
#0 __kernel_vsyscall

Comment 1 Jens Granseuer 2007-02-02 08:18:40 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 352490 ***