GNOME Bugzilla – Bug 532731
crash in Computer: Partage de fichiers (jpe...
Last modified: 2008-05-12 10:37:03 UTC
Version: 2.20.0 What were you doing when the application crashed? Partage de fichiers (jpeg) debian/windows xp Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Mist Memory status: size: 88281088 vsize: 88281088 resident: 32948224 share: 17281024 rss: 32948224 rss_rlim: 4294967295 CPU usage: start_time: 1210585872 rtime: 2213 utime: 1979 stime: 234 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 0xb6c2f720 (LWP 3668)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 197518
Thread 1 (Thread 0xb6c2f720 (LWP 3668))
----------- .xsession-errors (160 sec old) --------------------- AttributeError: 'module' object has no attribute 'BrowserSource' (rhythmbox:3845): Rhythmbox-WARNING **: Could not load plugin jamendo (rhythmbox:3845): Rhythmbox-WARNING **: Error, impossible to activate plugin 'Jamendo' connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:3668): WARNING **: Aucune description trouvée pour le type MIME « x-directory/smb-share » (le fichier est « Mes%20documents »), veuillez avertir la liste de diffusion de gnome-vf ** Message: Hit unexpected error "Répertoire occupé" while doing a file operation. (nautilus:3668): Gtk-CRITICAL **: gtk_window_realize_icon: assertion `info->icon_pixmap == NULL' failed --------------------------------------------------
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 ***