GNOME Bugzilla – Bug 528940
crash in Home Folder:
Last modified: 2008-04-20 10:11:36 UTC
What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.0 2008-03-14 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-486 #1 Thu Mar 27 17:00:17 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 75370496 vsize: 75370496 resident: 20332544 share: 15056896 rss: 20332544 rss_rlim: 4294967295 CPU usage: start_time: 1208626088 rtime: 290 utime: 266 stime: 24 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 0xb6c1d720 (LWP 4249)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 195643
Thread 1 (Thread 0xb6c1d720 (LWP 4249))
----------- .xsession-errors (6 sec old) --------------------- Find Items 0 get 2490092 pop://2490092;auth=LOGIN@pop.gmx.at/ Find Items 0 get 6724940 pop://6724940@pop.gmx.at/ Find Items 0 get 2490092 pop://2490092;auth=LOGIN@pop.gmx.at/ Find Items 0 get 6724940 pop://6724940@pop.gmx.at/ Find Items 0 get 2490092 pop://2490092;auth=LOGIN@pop.gmx.at/ Find Items 0 connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
I tried to install debug packages for nautilus (but I am not sure, if they are the right ones: I installed nautilus-dbg. the packages glib, gtk+ and gnome-vfs I could not found, even some similar. Then I produced the crash once more: Once more: I oben nautilus - change to network-folders - click on a (shared) folder of a windows-xp-PC (installed is XP SP2) => Nautilus crushes .... *********************** Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-486 #1 Thu Mar 27 17:00:17 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 75489280 vsize: 75489280 resident: 21864448 share: 15540224 rss: 21864448 rss_rlim: 4294967295 CPU usage: start_time: 1208681457 rtime: 664 utime: 606 stime: 58 cutime:0 cstime: 0 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 0xb6b5c720 (LWP 3921)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 195672
Thread 1 (Thread 0xb6b5c720 (LWP 3921))
----------- .xsession-errors --------------------- initial setting of an image. no scaling scale = 1 new dimensions = (48,48) we need to scale up scale = 1 get 6724940 pop://6724940@pop.gmx.at/ Find Items 0 get 2490092 pop://2490092;auth=LOGIN@pop.gmx.at/ Find Items 0 warning: .dynamic section for "/usr/lib/libnss3.so.1d" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libssl3.so.1d" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libnssutil3.so.1d" is not at the expected address (wrong library or version mismatch?) -------------------------------------------------- *********************** And there was I file created "nautilus-debug-log.txt": ===== BEGIN MILESTONES ===== 0x8174d28 2008/04/20 11:10:57.5477 (GLog): Hit unhandled case 46 (Zeitüberschreitung) in fm_report_error_loading_directory 0x8174d28 2008/04/20 11:38:24.7275 (USER): debug log dumped due to signal 11 ===== END MILESTONES ===== ===== BEGIN RING BUFFER ===== 0x8174d28 2008/04/20 10:51:12.0047 (USER): window 0x821c828 open location: old="(none)", new="x-nautilus-desktop:" 0x8174d28 2008/04/20 10:51:14.8945 (USER): finished loading window 0x821c828: x-nautilus-desktop: 0x8174d28 2008/04/20 11:10:22.2559 (USER): window 0x84b3868 open location: old="(none)", new="smb://nofigroup;@192.168.0.2/document" 0x8174d28 2008/04/20 11:10:22.2941 (USER): present NEW spatial window=0x84b3868: smb://nofigroup;@192.168.0.2/document 0x8174d28 2008/04/20 11:10:57.5464 (USER): finished loading window 0x84b3868: smb://nofigroup;@192.168.0.2/document 0x8174d28 2008/04/20 11:10:57.5477 (GLog): Hit unhandled case 46 (Zeitüberschreitung) in fm_report_error_loading_directory 0x8174d28 2008/04/20 11:12:26.1897 (USER): window 0x84b3938 open location: old="(none)", new="network:" 0x8174d28 2008/04/20 11:12:26.1945 (USER): present NEW spatial window=0x84b3938: network: 0x8174d28 2008/04/20 11:12:31.2156 (USER): finished loading window 0x84b3938: network: 0x8174d28 2008/04/20 11:12:35.0098 (USER): selection changed in window 0x84b3938 network:///smblink-root 0x8174d28 2008/04/20 11:12:35.2112 (USER): fm_directory_view_activate_files window=0x84b3938 network:///smblink-root 0x8174d28 2008/04/20 11:12:35.2341 (USER): directory view open_location window=0x84b3938: smb:/// 0x8174d28 2008/04/20 11:12:35.2341 (USER): window 0x84b3938 open location: old="network:", new="smb:///" 0x8174d28 2008/04/20 11:12:35.2456 (USER): window 0x84b3a08 open location: old="(none)", new="smb:///" 0x8174d28 2008/04/20 11:12:35.2463 (USER): present NEW spatial window=0x84b3a08: smb:/// 0x8174d28 2008/04/20 11:12:35.9129 (USER): finished loading window 0x84b3a08: smb:/// 0x8174d28 2008/04/20 11:14:54.6196 (USER): finished loading window 0x84b3a08: smb:/// 0x8174d28 2008/04/20 11:14:55.2540 (USER): finished loading window 0x84b3a08: smb:/// 0x8174d28 2008/04/20 11:15:45.1100 (USER): window 0x84b3ad8 open location: old="(none)", new="network:" 0x8174d28 2008/04/20 11:15:45.1201 (USER): present NEW spatial window=0x84b3ad8: network: 0x8174d28 2008/04/20 11:15:47.5205 (USER): finished loading window 0x84b3ad8: network: 0x8174d28 2008/04/20 11:15:49.6275 (USER): selection changed in window 0x84b3ad8 network:///smblink-root 0x8174d28 2008/04/20 11:15:49.8592 (USER): fm_directory_view_activate_files window=0x84b3ad8 network:///smblink-root 0x8174d28 2008/04/20 11:15:49.8598 (USER): directory view open_location window=0x84b3ad8: smb:/// 0x8174d28 2008/04/20 11:15:49.8598 (USER): window 0x84b3ad8 open location: old="network:", new="smb:///" 0x8174d28 2008/04/20 11:15:49.8716 (USER): window 0x84b3ba8 open location: old="(none)", new="smb:///" 0x8174d28 2008/04/20 11:15:49.8719 (USER): present NEW spatial window=0x84b3ba8: smb:/// 0x8174d28 2008/04/20 11:15:50.4925 (USER): finished loading window 0x84b3ba8: smb:/// 0x8174d28 2008/04/20 11:18:40.4312 (USER): finished loading window 0x84b3ba8: smb:/// 0x8174d28 2008/04/20 11:18:41.0010 (USER): finished loading window 0x84b3ba8: smb:/// 0x8174d28 2008/04/20 11:18:43.7218 (USER): finished loading window 0x84b3ba8: smb:/// 0x8174d28 2008/04/20 11:18:46.2930 (USER): finished loading window 0x84b3ba8: smb:/// 0x8174d28 2008/04/20 11:18:46.5909 (USER): finished loading window 0x84b3ba8: smb:/// 0x8174d28 2008/04/20 11:38:19.6464 (USER): window 0x84b3c78 open location: old="(none)", new="smb://Wolfgang@192.168.0.2/document" 0x8174d28 2008/04/20 11:38:19.6575 (USER): present NEW spatial window=0x84b3c78: smb://Wolfgang@192.168.0.2/document 0x8174d28 2008/04/20 11:38:24.7275 (USER): debug log dumped due to signal 11 ===== END RING BUFFER ===== This configuration for the debug log can be re-created by putting the following in ~/nautilus-debug-log.conf (use ';' to separate domain names): [debug log] max lines=1000
thanks for the stacktrace, now the problem is evident. Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 522534 ***