Bug 428342 – crash in Theme: próba instalacji motywu ...

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 428342 - crash in Theme: próba instalacji motywu ...


Summary:	crash in Theme: próba instalacji motywu ...


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-04-10 19:12 UTC by wojtek4410
Modified:	2007-04-10 19:27 UTC

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

Description wojtek4410 2007-04-10 19:12:20 UTC

Version: 2.16.1

What were you doing when the application crashed?
próba instalacji motywu dark x-2


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

Memory status: size: 68923392 vsize: 0 resident: 68923392 share: 0 rss: 16932864 rss_rlim: 0
CPU usage: start_time: 1176232254 rtime: 0 utime: 98 stime: 0 cutime:93 cstime: 0 timeout: 5 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 -1225206096 (LWP 6451)]
[New Thread -1245353056 (LWP 6485)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 126640

Thread 1 (Thread -1225206096 (LWP 6451))

#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 Jens Granseuer 2007-04-10 19:27:00 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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