GNOME Bugzilla – Bug 532594
crash in Home Folder: tried to access a folder...
Last modified: 2008-05-11 11:08:04 UTC
What were you doing when the application crashed? tried to access a folder on a windows xp pc via network Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24 #1 SMP Thu Apr 3 19:54:42 CEST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: SphereCrystal Memory status: size: 91557888 vsize: 91557888 resident: 34783232 share: 18214912 rss: 34783232 rss_rlim: 4294967295 CPU usage: start_time: 1210493457 rtime: 422 utime: 381 stime: 41 cutime:20 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6b76720 (LWP 3484)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 197439
Thread 1 (Thread 0xb6b76720 (LWP 3484))
----------- .xsession-errors --------------------- Fenstermanager-Warnung:Treating resize request of legacy application 0x3400007 (World of W) as a fullscreen request ** (claws-mail:3570): WARNING **: [12:14:08] IMAP Fehler: stream error ** (claws-mail:3570): WARNING **: [12:14:08] IMAP4 Verbindung unterbrochen connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:3484): WARNING **: Keine Beschreibung für MIME-Type »x-directory/smb-share« gefunden (Datei ist »Neuer%20Ordner%20(2)«), teilen Sie dies der gnome-vfs-Mailingliste mit. warning: .dynamic section for "/usr/lib/libcairo.so.2" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
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 ***