GNOME Bugzilla – Bug 429114
Nautilus lets you enter nonexistent mountpoints
Last modified: 2012-10-26 19:16:04 UTC
Version: 2.18.0.1 What were you doing when the application crashed? In "Properties" in the context menu for a mp3-player I tried to change the mount-point. Distribution: Gentoo Base System release 1.13.0_alpha12 Gnome Release: 2.18.0 2007-03-16 (Gentoo) BugBuddy Version: 2.18.0 System: Linux 2.6.20-gentoo-r5 #1 SMP PREEMPT Sun Apr 8 20:42:20 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10299905 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Lila Memory status: size: 90714112 vsize: 90714112 resident: 29261824 share: 19402752 rss: 29261824 rss_rlim: 4294967295 CPU usage: start_time: 1176376729 rtime: 18371 utime: 8074 stime: 10297 cutime:5777 cstime: 1431 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208199504 (LWP 28238)] 0xb7ff3410 in __kernel_vsyscall ()
+ Trace 127262
Thread 1 (Thread -1208199504 (LWP 28238))
----------- .xsession-errors (30342 sec old) --------------------- ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 MPlayer dev-SVN-rUNKNOWN-4.1.2 (C) 2000-2007 MPlayer Team CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (Family: 15, Model: 2, Stepping: 9) CPUflags: MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1 Kompilerad för x86 med tillägg: MMX MMX2 SSE SSE2 xscreensaver_disable: Could not find XScreenSaver window. [GUI] Adding video filter: pp Cache fill: 0.78% (16384 bytes) Cache fill: 0.78% (16384 bytes) Cache fill: 0.78% (16384 bytes) Cache fill: 0.78% (16384 bytes) Cache fill: 0.78% (16384 bytes) Cache fill: 0.78% ...Too much output, ignoring rest... --------------------------------------------------
Should clearify some things: i set the mount-point to /media/mp3play and that was accepted, but as soon as I hitted OK or opening the properties-dialog nautilus crashed and restarted. The problem seems to be that the mount-point got a / in it as remounted the mp3-player was not possible before I with gconf-edito changed the mount point from '/media/mp3play' to 'mp3play'. Maybe some failsafe here, or a sfaeguard preventing a users from enter a bad value?
*** Bug 430554 has been marked as a duplicate of this bug. ***
*** Bug 439755 has been marked as a duplicate of this bug. ***
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 406462 ***
So what has this bug with that bug to do? This one is a problem arising if mountpoint is with the help of properties in nautilus set to a faulty value (in this case a non accessible directory) which nautilus proporties dialog gladly accepts (i.e. clearly a nautilus bug)! Clearing/correcting mountpoints in gconf fixes this if it occurs (which I do not think nautilus should allow). With other word: this is a bug about nautilus properties dialog accepting a non accessible path as mountpoint and then crashing when it can't mount the media there.
Both bugs have the same stacktrace, which indicates a problem within gtk. As they have the same stacktrace, we're pretty sure both crashes are caused by the same problem. *** This bug has been marked as a duplicate of 406462 ***
Ok, then. Let me refrase my bugreport and maybe make it more clear: IGNORE THE DAMNED CRASH! Nautilus lets you enter a nonexistent/nonaccessible path as mountpoint without any checks to see if it really can mount something there before saving the mountpoint to gconf. It SHOULD test this when you close the dialog and before saving the change. Nautilus should probably give you a errormessage if the mountpoint is faulty. Change the mountpoint to a existing/accessible path (for me changeing from /mp3play to /media/mp3play) makes it work. The crash in this case is when it finnaly tries to mount the device on a non-existent path (i.e. remove and replug the device) but really is just a side effect of the above described bug!
*** Bug 483953 has been marked as a duplicate of this bug. ***
This is not relevant anymore, since we don't have such a page in the properties - I think in the past it was even provided by this extension and not natilus itself [1]. Anyway, closing as OBSOLETE.