GNOME Bugzilla – Bug 349718
nautilus crashes with x-nautilus-desktop:///
Last modified: 2007-04-12 14:30:54 UTC
Steps to reproduce: Steps to reproduce the crash: 1. Open a nautilus window 2. Type in the location bar: x-nautilus-desktop:///ABCDEF ABCDEF is just a random string. Stack trace: Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225832768 (LWP 6002)] [New Thread -1228985424 (LWP 6003)] (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) (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) (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) (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) (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) (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) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xb7ed9221 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 69922
Thread 1 (Thread -1225832768 (LWP 6002))
Other information:
I can confirm that Distribution: Ubuntu 6.06 (dapper) Gnome Release: 2.15.90 2006-08-08 (JHBuild) BugBuddy Version: 2.15.91 Memory status: size: 60190720 vsize: 0 resident: 60190720 share: 0 rss: 19623936 rss_rlim: 0 CPU usage: start_time: 1155134479 rtime: 0 utime: 139 stime: 0 cutime:127 cstime: 0 timeout: 12 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 -1226606912 (LWP 6433)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 70140
Thread 1 (Thread -1226606912 (LWP 6433))
I can't reproduce this with current (2006-11-10) CVS HEAD.
but it is reproducable with the 2.16 cvs branch. would be great if we could find out what commit fixed this. with 2.16: Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-11-06 (JHBuild) BugBuddy Version: 2.16.0 Memory status: size: 74403840 vsize: 0 resident: 74403840 share: 0 rss: 23105536 rss_rlim: 0 CPU usage: start_time: 1163210918 rtime: 0 utime: 213 stime: 0 cutime:201 cstime: 0 timeout: 12 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 -1229908304 (LWP 6697)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 85251
Thread 1 (Thread -1229908304 (LWP 6697))
(In reply to comment #3) > but it is reproducable with the 2.16 cvs branch. would be great if we could > find out what commit fixed this. I'll assume that's either 2.16.0 or 2.16.1, as I think I've found the bug, and it's fixed in 2.16.2 (fun and games with "cvs -z3 diff -u -r NAUTILUS_2_16_1" against HEAD and looking where your stack trace asserted). It got fixed with the fix for #349840, changelog entry is 2006-11-06 Alexander Larsson <alexl@redhat.com> * libnautilus-private/nautilus-file.c (nautilus_file_new_from_relative_uri): Don't crash on old desktop dir and search dir uris. (#349840) Relevant patch is http://cvs.gnome.org/viewcvs/nautilus/libnautilus-private/nautilus-file.c?r1=1.394&r2=1.395&makepatch=1&diff_format=u
hmm my jhbuild with 2.16 module set uses cvs -z3 -q -d :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome update -P -d -A . thus I assume it uses HEAD !?
I think so. Given the -A to reset any sticky flags, it should be using HEAD.
*** Bug 368004 has been marked as a duplicate of this bug. ***
*** Bug 419964 has been marked as a duplicate of this bug. ***
bug 377228 is probably another duplicate.
oops... is this one a dup of bug 349840?
yes, andre, yes. sorry for the noise. So, 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 349840 ***