Bug 370199 – crash in Trash: ich habe die Themeneinst...

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 370199 - crash in Trash: ich habe die Themeneinst...


Summary:	crash in Trash: ich habe die Themeneinst...


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-11-03 20:35 UTC by ronny-berndt-beier
Modified:	2006-11-03 20:44 UTC

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

Description ronny-berndt-beier 2006-11-03 20:35:50 UTC

What were you doing when the application crashed?
ich habe die Themeneinstellungen gestartet


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

Memory status: size: 66756608 vsize: 0 resident: 66756608 share: 0 rss: 11993088 rss_rlim: 0
CPU usage: start_time: 1162584652 rtime: 0 utime: 102 stime: 0 cutime:90 cstime: 0 timeout: 12 it_real_value: 0 frequency: 10

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 -1225316160 (LWP 4594)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 82502

Thread 1 (Thread -1225316160 (LWP 4594))

#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 Karsten Bräckelmann 2006-11-03 20:44:37 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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