GNOME Bugzilla – Bug 530267
crash in Home Folder: Acessing a windows share...
Last modified: 2008-04-28 17:04:03 UTC
What were you doing when the application crashed? Acessing a windows shared drive, the whole drive was shared, and I accessed "d", and also was a "d$" folder, acessing a normal share (just a folder) is ok. Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Thu Mar 27 16:52:38 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango Memory status: size: 446857216 vsize: 446857216 resident: 29540352 share: 17444864 rss: 29540352 rss_rlim: 18446744073709551615 CPU usage: start_time: 1209339714 rtime: 217 utime: 197 stime: 20 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 0x2b15204d7b80 (LWP 25602)] (no debugging symbols found) 0x00002b1519ffcedf in waitpid () from /lib/libpthread.so.0
+ Trace 196287
Thread 1 (Thread 0x2b15204d7b80 (LWP 25602))
----------- .xsession-errors (92024 sec old) --------------------- (rhythmbox:4549): RhythmDB-CRITICAL **: rhythmdb_entry_get_ulong: assertion `entry != NULL' failed (rhythmbox:4549): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed (rhythmbox:4549): RhythmDB-CRITICAL **: rhythmdb_entry_get_ulong: assertion `entry != NULL' failed (rhythmbox:4549): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed (rhythmbox:4549): RhythmDB-CRITICAL **: rhythmdb_entry_get_ulong: assertion `entry != NULL' failed (rhythmbox:4549): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed (rhythmbox:4549): RhythmDB-CRITICAL **: rhythmdb_entry_get_ulong: assertion `entry != NULL' failed ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Ok, i just installed the gnome-dgb metapackage and here is the report: Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Thu Mar 27 16:52:38 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango Memory status: size: 557473792 vsize: 557473792 resident: 39735296 share: 10473472 rss: 39735296 rss_rlim: 18446744073709551615 CPU usage: start_time: 1209347322 rtime: 5658 utime: 4865 stime: 793 cutime:21107 cstime: 5346 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0x2ab371378b80 (LWP 4992)] 0x00002ab36ae9dedf in waitpid () from /lib/libpthread.so.0
+ Trace 196336
Thread 1 (Thread 0x2ab371378b80 (LWP 4992))
----------- .xsession-errors (37 sec old) --------------------- (totem:9131): GStreamer-CRITICAL **: gst_object_unref: assertion `object != NULL' failed (totem:9131): GStreamer-CRITICAL **: gst_object_unref: assertion `object != NULL' failed (totem:9131): GStreamer-CRITICAL **: gst_object_unref: assertion `object != NULL' failed (totem:9131): GStreamer-CRITICAL **: gst_object_unref: assertion `object != NULL' failed (totem:9131): GStreamer-CRITICAL **: gst_object_unref: assertion `object != NULL' failed (totem:9131): GStreamer-CRITICAL **: gst_object_unref: assertion `object != NULL' failed connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! --------------------------------------------------
Thanks for the follow up on this. It is a known bug that happens when you browse a Windows/SMB share, and we already committed a patch for it...will be hopefully fixed in the next upgrade of your distro package. Feel free to report any other bug you find! *** This bug has been marked as a duplicate of 522534 ***