GNOME Bugzilla – Bug 539385
crash in Open Folder: Just browsing a Windows ...
Last modified: 2008-06-21 10:00:06 UTC
Version: 2.20.0 What were you doing when the application crashed? Just browsing a Windows WorkGroup. Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.18-4-686 #1 SMP Mon Mar 26 17:17:36 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 77467648 vsize: 77467648 resident: 25219072 share: 14602240 rss: 25219072 rss_rlim: 4294967295 CPU usage: start_time: 1213981288 rtime: 534 utime: 484 stime: 50 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6c18940 (LWP 29501)] (no debugging symbols found) 0xb7fde410 in ?? ()
+ Trace 200978
Thread 1 (Thread 0xb6c18940 (LWP 29501))
----------- .xsession-errors --------------------- (rhythmbox:2775): Rhythmbox-WARNING **: Error, impossible to activate plugin 'Magnatune Store' Traceback (most recent call last): File "/usr/lib/rhythmbox/plugins/artdisplay/__init__.py", line 315, in <module> class ArtDisplayPlugin (rb.Plugin): AttributeError: 'module' object has no attribute 'Plugin' (rhythmbox:2775): Rhythmbox-WARNING **: Could not load plugin artdisplay (rhythmbox:2775): Rhythmbox-WARNING **: Error, impossible to activate plugin 'Cover art' connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! Failed to read a valid object file image from memory. --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 522534 ***