Bug 354989 – crash in Trash: Changing themes in Edgy ...

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 354989 - crash in Trash: Changing themes in Edgy ...


Summary:	crash in Trash: Changing themes in Edgy ...


Status:	RESOLVED DUPLICATE of bug 352265

Product:	gnome-applets
Classification:	Other
Component:	trash applet
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	gnome-applets Maintainers
QA Contact:	gnome-applets Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-09-08 16:24 UTC by cooked
Modified:	2010-01-24 01:06 UTC

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

Description cooked 2006-09-08 16:24:28 UTC

What were you doing when the application crashed?
Changing themes in Edgy Eft.

QT was an option in the Controls panel, and when clicked on, causes the system to freeze up for a second, and then a few windows to come up and crash before rendered.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 67833856 vsize: 0 resident: 67833856 share: 0 rss: 10014720 rss_rlim: 0
CPU usage: start_time: 1157731740 rtime: 0 utime: 86 stime: 0 cutime:82 cstime: 0 timeout: 4 it_real_value: 0 frequency: 12

Backtrace was generated from '/usr/libexec/trashapplet'

(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 -1224508768 (LWP 4937)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 71898

Thread 1 (Thread -1224508768 (LWP 4937))

#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 ??
#5 gdk_x11_drawable_get_xdisplay
from /usr/lib/libgdk-x11-2.0.so.0
#6 gdk_events_pending
from /usr/lib/libgdk-x11-2.0.so.0
#7 _gdk_events_queue
from /usr/lib/libgdk-x11-2.0.so.0
#8 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#9 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#10 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#11 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#12 bonobo_main
from /usr/lib/libbonobo-2.so.0
#13 bonobo_generic_factory_main_timeout
from /usr/lib/libbonobo-2.so.0
#14 bonobo_generic_factory_main
from /usr/lib/libbonobo-2.so.0
#15 panel_applet_factory_main_closure
from /usr/lib/libpanel-applet-2.so.0
#16 panel_applet_factory_main
from /usr/lib/libpanel-applet-2.so.0
#17 ??
#18 _IO_stdin_used
#19 ??
#20 ??
#21 ??
#0 __kernel_vsyscall

Comment 1 Danielle Madeley 2006-09-09 02:19:43 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 2 Karsten Bräckelmann 2006-09-13 20:13:48 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 352265 ***

Comment 3 Karsten Bräckelmann 2006-09-13 20:17:06 UTC

cooked, please add any additional information to bug 352265. Thanks.