GNOME Bugzilla – Bug 506774
crash in Open Folder: SSH into directory with ...
Last modified: 2008-01-02 19:36:28 UTC
Version: 2.18.3 What were you doing when the application crashed? SSH into directory with space in the path Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.3 2007-10-12 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.23-gentoo-r3 #1 SMP Thu Dec 6 20:56:45 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Neu Memory status: size: 91635712 vsize: 91635712 resident: 37093376 share: 20131840 rss: 37093376 rss_rlim: 4294967295 CPU usage: start_time: 1199232471 rtime: 468 utime: 432 stime: 36 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1238775360 (LWP 5731)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 183753
Thread 1 (Thread -1238775360 (LWP 5731))
----------- .xsession-errors --------------------- Resource id: 0x2a0031b kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) Qt: Warning: QObject::disconnect: Unexpected null parameter Qt: Warning: QObject::disconnect: Unexpected null parameter ** (process:5694): WARNING **: Credentials byte was not nul ** (nautilus:5731): WARNING **: Possibly invalid new URI 'ssh://h1voltage@74.74.206.201:22/media/sdb1/Global_Docs/My Music' This can cause subtle evils like #48423 ** ERROR **: file nautilus-navigation-window.c: line 834 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers)) aborting... --------------------------------------------------
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 459221 ***