GNOME Bugzilla – Bug 303392
nautilus crash while using sftp and idling...
Last modified: 2005-05-07 21:09:27 UTC
Distribution: Debian 3.1 Package: nautilus Severity: normal Version: 2.8.2 Synopsis: nautilus crash while using sftp and idling... Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.8.2 BugBuddy-GnomeVersion: 2.0 (2.8.1) Description: Nautilus crashed while having an open sftp connection. it was allowed to idle, and when i tried to use it again, nautilus crashed... i hope the backtrace is good. Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1224325888 (LWP 4987)] [New Thread -1237025872 (LWP 4998)] [New Thread -1236759632 (LWP 4997)] [New Thread -1236493392 (LWP 4996)] [New Thread -1236227152 (LWP 4995)] [New Thread -1235960912 (LWP 4994)] [New Thread -1227568208 (LWP 4988)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 59318
Thread 6 (Thread -1235960912 (LWP 4994))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-05-07 16:53 UTC ------- Unknown version 2.8.2 in product nautilus. Setting version to "2.8.x".
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 161967 ***