GNOME Bugzilla – Bug 158904
folders with rootpermissions disappear when rightclicking + crash
Last modified: 2005-06-13 21:40:36 UTC
When you create a folder as root in a directory that is readable as normal user, that folder disapears when you rightclick on it (as normal user). You can reproduce it by creating a folder like this one: drwx------ 2 root root 4096 Nov 18 07:34 lost+found now, there is also a crash... when you select the folder and press alt+enter to fire up the properties dialog, you can see it in a flash, but then nautilus crashes! Here is the backtrace with debugging information: Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -151135616 (LWP 3664)] [New Thread -165168208 (LWP 3685)] [Thread debugging using libthread_db enabled] [New Thread -151135616 (LWP 3664)] [New Thread -165168208 (LWP 3685)] [Thread debugging using libthread_db enabled] [New Thread -151135616 (LWP 3664)] [New Thread -165168208 (LWP 3685)] [New Thread -164901968 (LWP 3684)] [New Thread -164635728 (LWP 3683)] [New Thread -164369488 (LWP 3682)] [New Thread -164103248 (LWP 3681)] [New Thread -153601104 (LWP 3675)] 0x0082d7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 52337
Thread 7 (Thread -153601104 (LWP 3675))
This appears to be a unique stack trace, according to the simple-dup-finder. I'm adding the STACKTRACE keyword since it has debugging symbols.
and we are approaching the new gnome 2.10... and a bug like this is still present... it is easy reproduceable, but i don't have enough knowledge (yet) to fix it myself... try rightclicking your lost+found directory, everyone has one!
I don't get a crash, but I do see the folder disappear and I have to press ctrl+r to make it show up again in spatial icon view. Which view are you using? Oh, hold on. I get a SIGABRT when running nautilus in gdb when doing alt+enter. And when I press 'c' after that nautilus crashes...Marking up and putting on the 2.10.0 milestone tentatively.
What version of nautilus are you using ? here with nautilus 2.9.90 that doesn't crash and the folder stay here. BTW the crash seems to be the one in #165725, but it happens when you already are in a directory that you are not allowed to browse.
I tested using version 2.9.91, or CVS from a couple of days ago. What I did was to open $HOME, then move up to / and right click on /root or /lost+found - when right clicking on them they both were gone from the icon view - when marking them and doing alt+enter a new window was opened, then instantly closed and the folder in question was gone from the original icon view again - I attached to nautilus in gdb and did it once more and I saw that nautilus got a SIGABRT when trying to open the prefs window and then just closed it again instantly, but when I tried to continue nautilus crashed.
*** Bug 165725 has been marked as a duplicate of this bug. ***
*** Bug 151024 has been marked as a duplicate of this bug. ***
Under certain circumstances the property window can't handle single-file windows where the original file disappears (separate bugs really). Seb posted these instructions at Bug 165725: - cd /tmp - mkdir nautilus - touch nautilus/file - chmod a-x nautilus - nautilus /tmp/nautilus/ right click on "file", properties ... nautilus crashes. You can also create a file > 2GB with - dd if=/dev/zero of=bigfile bs=16k count=131073 and try to view its properties. Both causes the file to disappear and the properties window to crash over a null pointer. I've committed a fix to the crash on both branches so that the property window just disappears with the file - But the underlying bugs need to be addressed asap. (e.g. bug 165306).
*** Bug 160630 has been marked as a duplicate of this bug. ***
*** Bug 167183 has been marked as a duplicate of this bug. ***
*** Bug 168858 has been marked as a duplicate of this bug. ***
*** Bug 169318 has been marked as a duplicate of this bug. ***
The bug with the files > 2GB disappearing seem to be a gamin issue. I opened bug 167898 about it.
*** Bug 303528 has been marked as a duplicate of this bug. ***
*** Bug 304263 has been marked as a duplicate of this bug. ***
*** Bug 304283 has been marked as a duplicate of this bug. ***
*** Bug 307570 has been marked as a duplicate of this bug. ***