GNOME Bugzilla – Bug 535719
crash in Home Folder: I click the share folder...
Last modified: 2008-05-30 11:17:33 UTC
What were you doing when the application crashed? I click the share folder of windows on LanNetwork. 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 Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Lush Memory status: size: 104173568 vsize: 104173568 resident: 30629888 share: 17481728 rss: 30629888 rss_rlim: 4294967295 CPU usage: start_time: 1212144550 rtime: 498 utime: 470 stime: 28 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 0xb6c39720 (LWP 3707)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 199144
Thread 1 (Thread 0xb6c39720 (LWP 3707))
----------- .xsession-errors --------------------- Using default colormap which is TrueColor. Pixel format: 32 bits per pixel. Least significant byte first in each pixel. True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0 Using shared memory PutImage kbuildsycoca running... Reusing existing ksycoca connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:3707): WARNING **: MIME型 "x-directory/smb-share" (ファイルは "downloads") の説明が見つかりません。gnome-vfs メーリング・リストにお知らせ下さい。 warning: .dynamic section for "/usr/lib/libXdamage.so.1" 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 ***