GNOME Bugzilla – Bug 375019
crash in lacks_info (nautilus-directory-async.c:1672)
Last modified: 2008-03-23 14:31:00 UTC
Version: 2.16.3 What were you doing when the application crashed? Connecting to a remote filesystem using SSH Distribution: Ubuntu 6.06 (dapper) Gnome Release: 2.17.2 2006-11-08 (JHBuild) BugBuddy Version: 2.16.0 Memory status: size: 82419712 vsize: 0 resident: 82419712 share: 0 rss: 34177024 rss_rlim: 0 CPU usage: start_time: 1163491123 rtime: 0 utime: 1415 stime: 0 cutime:1236 cstime: 0 timeout: 179 it_real_value: 0 frequency: 0 Backtrace was generated from '/opt/gnome2/bin/nautilus' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1227384352 (LWP 5320)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 86296
Thread 1 (Thread -1227384352 (LWP 5320))
looks unique, good trace, confirming.
*** Bug 375585 has been marked as a duplicate of this bug. ***
*** Bug 375923 has been marked as a duplicate of this bug. ***
*** Bug 376091 has been marked as a duplicate of this bug. ***
fwiw, my duplicate (bug #375923) did NOT occur when browsing over ssh... I was viewing a *local* directory.
*** Bug 376449 has been marked as a duplicate of this bug. ***
quote "No matter if the above option is checked or not, running "nautilus cdda://" in gnome-terminal made nautilus crash. (I don't know if it was the right URI, but it was the best one I could guess.)"
+ Trace 89482
nautilus_directory_async_state_changed() seems to call file_needs_high_priority_work_done ( file=0x0)
*** Bug 380235 has been marked as a duplicate of this bug. ***
*** Bug 382305 has been marked as a duplicate of this bug. ***
Closing as OBSOLETE, since this is a 2.16-only crash with no duplicates in the last months, so we can assume it has been fixed or it was a configuration/distro problem. Please reopen the bug if you still get the same crash with latest versions of Nautilus, and feel free to report any other bug you find, thanks!