GNOME Bugzilla – Bug 376843
crash in Trash: initating an x session
Last modified: 2006-11-19 04:31:15 UTC
What were you doing when the application crashed? initating an x session Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:36:14 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors --------------------- localuser:root being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/5809 Window manager warning: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager. Window manager warning: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager. ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name 5885: assertion failed "pending != NULL" file "dbus-connection.c" line 2885 function dbus_connection_send_with_reply_and_block (bug-buddy:5933): GnomeUI-WARNING **: While connecting to session manager: Could not open network socket. ** (bug-buddy:5933): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 96907264 vsize: 0 resident: 96907264 share: 0 rss: 8753152 rss_rlim: 0 CPU usage: start_time: 1163941606 rtime: 0 utime: 10 stime: 0 cutime:8 cstime: 0 timeout: 2 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) [Thread debugging using libthread_db enabled] [New Thread -1208236336 (LWP 5915)] (no debugging symbols found) 0x00d8e402 in __kernel_vsyscall ()
+ Trace 87591
Thread 1 (Thread -1208236336 (LWP 5915))
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 366370 ***