Bug 106324 – Nautilus crash in file properties dialog

Bug 106324 - Nautilus crash in file properties dialog

Summary:	Nautilus crash in file properties dialog

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	nautilus (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Alexander Larsson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-10-05 15:29 EDT by James Drabb
Modified:	2007-11-30 17:10 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-10-06 13:07:40 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description James Drabb 2003-10-05 15:29:54 EDT

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5a) Gecko/20030811
Mozilla Firebird/0.6.1

Description of problem:
Nautilus crashes when changing a directories properties in nautilus.


Version-Release number of selected component (if applicable):
nautilus-2.4.0-3

How reproducible:
Always

Steps to Reproduce:
1. Create a new directory: mkdir ~/test
2. Give 555 permissions:  chown 555 ~/test
3. Open nautilus and right click on the test directorym then choose properties
and go to the permissions tab.  Click on the wirte check box for the user and
nautilus will crash every time.
    

Actual Results:  Nautilus crash

Expected Results:  Changing permissions on file/directory.

Additional info:

Comment 1 James Drabb 2003-10-05 19:58:10 EDT

Step 2. should be chmod 555 ~/test
Though I guess everyone knew that : )

Comment 2 Alexander Larsson 2003-10-06 13:07:40 EDT

Fixed in -4.

Note You need to log in before you can comment on or make changes to this bug.