Bug 356313 – crash in Trash: Logging back in from GDM...

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 356313 - crash in Trash: Logging back in from GDM...


Summary:	crash in Trash: Logging back in from GDM...


Status:	RESOLVED DUPLICATE of bug 354823

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-16 20:43 UTC by penguinpirate7
Modified:	2006-09-16 20:46 UTC

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

Description penguinpirate7 2006-09-16 20:43:48 UTC

What were you doing when the application crashed?
Logging back in from GDM after a logout.


Distribution: Gentoo Base System version 1.12.5
Gnome Release: 2.16.0 2006-09-14 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 16846848 vsize: 0 resident: 16846848 share: 0 rss: 6631424 rss_rlim: 0
CPU usage: start_time: 1158414190 rtime: 0 utime: 5 stime: 0 cutime:4 cstime: 0 timeout: 1 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224922944 (LWP 27436)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 72519

Thread 1 (Thread -1224922944 (LWP 27436))

#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 dbus_connection_send_with_reply
from /usr/lib/libdbus-1.so.2
#5 dbus_connection_send_with_reply_and_block
from /usr/lib/libdbus-1.so.2
#6 gnome_vfs_volume_monitor_client_shutdown_private
from /usr/lib/libgnomevfs-2.so.0
#7 gnome_vfs_volume_monitor_client_get_type
from /usr/lib/libgnomevfs-2.so.0
#8 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#9 g_object_set
from /usr/lib/libgobject-2.0.so.0
#10 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#11 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#12 g_object_new
from /usr/lib/libgobject-2.0.so.0
#13 gnome_vfs_volume_monitor_emit_pre_unmount
from /usr/lib/libgnomevfs-2.so.0
#14 gnome_vfs_get_volume_monitor
from /usr/lib/libgnomevfs-2.so.0
#15 ??
#16 ??
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-09-16 20:46:33 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.

Also, the maintainers need more information to fix the bug. Could you please answer the questions in the other report?


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