Bug 390632 – crash in Theme: changing icon theme in g...

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 390632 - crash in Theme: changing icon theme in g...


Summary:	crash in Theme: changing icon theme in g...


Status:	RESOLVED DUPLICATE of bug 364839

Product:	gnome-control-center
Classification:	Core
Component:	[obsolete] theme-manager
Version:	2.17.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-12-29 10:27 UTC by malek
Modified:	2006-12-29 17:35 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description malek 2006-12-29 10:27:19 UTC

Version: 2.17.3

What were you doing when the application crashed?
changing icon theme in gnome theme manager



Distribution: Fedora Core release 6 (Rawhide)
Gnome Release: 2.17.2 2006-11-07 (Red Hat, Inc)
BugBuddy Version: 2.17.3

System: Linux 2.6.19-1.2891.fc7 #1 SMP Thu Dec 21 10:59:07 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Enabled

Memory status: size: 40984576 vsize: 0 resident: 40984576 share: 0 rss: 15273984 rss_rlim: 0
CPU usage: start_time: 1167387935 rtime: 0 utime: 101 stime: 0 cutime:63 cstime: 0 timeout: 38 it_real_value: 0 frequency: 0

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 -1208927488 (LWP 2440)]
(no debugging symbols found)
0x00491402 in __kernel_vsyscall ()

+ Trace 97755

Thread 1 (Thread -1208927488 (LWP 2440))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 strlen
from /lib/libc.so.6
#5 giop_send_buffer_append_string
from /usr/lib/libORBit-2.so.0
#6 ORBit_marshal_value
from /usr/lib/libORBit-2.so.0
#7 ORBit_marshal_value
from /usr/lib/libORBit-2.so.0
#8 ORBit_marshal_any
from /usr/lib/libORBit-2.so.0
#9 ORBit_marshal_value
from /usr/lib/libORBit-2.so.0
#10 ORBit_marshal_value
from /usr/lib/libORBit-2.so.0
#11 ORBit_small_allocbuf
from /usr/lib/libORBit-2.so.0
#12 ORBit_small_invoke_stub
from /usr/lib/libORBit-2.so.0
#13 ORBit_small_invoke_stub_n
from /usr/lib/libORBit-2.so.0
#14 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#15 Accessibility_EventListener_notifyEvent
from /usr/lib/libspi.so.0
#16 ??
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#17 ??
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#18 exit
from /lib/libc.so.6
#19 __libc_start_main
from /lib/libc.so.6
#20 _start
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
GTK Accessibility Module initialized
Introspect error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the ne
GTK Accessibility Module initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
--------------------------------------------------

Comment 1 Jens Granseuer 2006-12-29 17:35:23 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 364839 ***