GNOME Bugzilla – Bug 530877
crash in File Browser: nautilus crashed when ac...
Last modified: 2008-05-01 12:48:40 UTC
Version: 2.20.0 What were you doing when the application crashed? nautilus crashed when accessing to a Windows Desktop folder. Other folders load correctly Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-tos #5 SMP Thu Feb 14 11:03:42 CET 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: nuoveXT.2.2 Memory status: size: 402067456 vsize: 402067456 resident: 30511104 share: 16027648 rss: 30511104 rss_rlim: 4294967295 CPU usage: start_time: 1209629646 rtime: 2395 utime: 2094 stime: 301 cutime:105 cstime: 19 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 0xb6b6a720 (LWP 3990)] (no debugging symbols found) 0xb7f05410 in __kernel_vsyscall ()
+ Trace 196593
Thread 1 (Thread 0xb6b6a720 (LWP 3990))
----------- .xsession-errors --------------------- ** (amule:5248): CRITICAL **: clearlooks_style_draw_box_gap: assertion `height >= -1' failed ** (amule:5248): CRITICAL **: clearlooks_style_draw_box_gap: assertion `height >= -1' failed connection_message_func(): Callback CALLBACK: fill-authentication!!! warning: .dynamic section for "/usr/lib/libxml2.so.2" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libtotem-plparser.so.10" is not at the expected address (wrong library or version mismatch?) Error while mapping shared library sections: /usr/lib/libcamel-1.2.so.10: No such file or directory. warning: .dynamic section for "/usr/lib/libedataserver-1.2.so.9" 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 ***