GNOME Bugzilla – Bug 157703
Nautilus crashes when viewing file permissions
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian testing/unstable Package: nautilus Severity: normal Version: GNOME2.8.1 2.8.1 Gnome-Distributor: Ubuntu Synopsis: Nautilus crashes when viewing file permissions Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.8.1 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: When a file's permissions are set so that the permissions of the file are not viewable to the current user, and the user uses the Nautilus "Properties" dialog (right click on a file and select "Properties"), then selects the "Permissions" tab, Nautilus crashes. Steps to reproduce the crash: 1. Change permissions of a file so that the file is not readable by user x, but set the permissions of its directory to be at least readable by user x. 2. Running Nautilus as user x, go to that directory, and right click on the file and select "Properties", and select the "Permissions" tab. 4. Nautilus Crashes Expected Results: Some message saying that Nautilus cannot view the permissions of the file. How often does this happen? This crash happens every time the procedure above is followed. 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". ------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-08 18:09 ------- Unknown version 2.8.1 in product nautilus. Setting version to "1.0.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "nautilus". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was warner@cs.swarthmore.edu. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Thanks for the bug report. It appears that the stack trace didn't make it. Without a stack trace from the crash it's very hard to determine what caused the crash. Please see http://bugzilla.gnome.org/getting-traces.cgi for more information about getting a useful stack trace.
based on the description this seems like a duplicate of bug 151024
*** This bug has been marked as a duplicate of 151024 ***