GNOME Bugzilla – Bug 540469
crash in Home Folder: Versuch, den Orderinhalt...
Last modified: 2008-06-27 11:54:28 UTC
What were you doing when the application crashed? Versuch, den Orderinhalt anzuzeigen - Gnome - Netzwerk Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-486 #1 Thu May 8 01:29:10 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 65105920 vsize: 65105920 resident: 22511616 share: 14643200 rss: 22511616 rss_rlim: 4294967295 CPU usage: start_time: 1214573206 rtime: 215 utime: 202 stime: 13 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (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 0xb6c36720 (LWP 4698)] (no debugging symbols found) 0xb7381f91 in waitpid () from /lib/libpthread.so.0
+ Trace 201521
Thread 1 (Thread 0xb6c36720 (LWP 4698))
----------- .xsession-errors (71 sec old) --------------------- xrdb: "*Text.background" on line 226 overrides entry on line 191 xrdb: "*Label.foreground" on line 232 overrides entry on line 151 xrdb: "*Text.foreground" on line 238 overrides entry on line 192 Initializing gnome-mount extension ** (gnome-cups-icon:4726): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:4726): WARNING **: IPP request failed with status 1280 seahorse nautilus module initialized (gnome-panel:4697): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x80e6b58 (gnome-panel:4697): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x80e6b58 (gnome-panel:4697): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -25 and height 24 --------------------------------------------------
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 522534 ***