Bug 3244 - GMC properties shows wrong group owner
Summary: GMC properties shows wrong group owner
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: distribution
Version: 6.0
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: Jonathan Blandford
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-06-03 16:27 UTC by mwn
Modified: 2013-04-02 04:13 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 1999-08-05 20:49:40 UTC
Embargoed:


Attachments (Terms of Use)

Description mwn 1999-06-03 16:27:24 UTC
In GNU Midnight Commander, when you right click on a file
and select Properties, then click on the Permissions tab,
the Group listing is incorrect.  It always gives the Group
the same as the User.  To see the correct group ownership,
use the (ls -l)command in a terminal window, or set up a
custom view in GMC that includes the group.

Comment 1 David Lawrence 1999-06-03 22:06:59 UTC
I was not able to replicate this problem with gmc-4.5.30-12 as shipped
with Red Hat 6.0.

Comment 2 mwn 1999-06-03 23:19:59 UTC
Would you mind trying the following just to be sure we are on the same
page?

Make a new file.  Right click on it and select Properties, then the
Permissions tab.  The goup and user should be the same, if using the
standard Red Hat User-Private Groups.  In the Group drop down box,
change the group to something else and click OK.  Right click on the
file again and go to the Permissions tab.  What does the group say?
On my system it reverts to the same name as the User, even though the
group has actually been changed to something else (as can be verified
with ls -l).  Thanks for your help.

Comment 3 mwn 1999-06-03 23:21:59 UTC
P.S. when I select About from the Help menu it says GMC 4.5.30.  Where
do you find the -12 in your 4.5.30-12?

Comment 4 Jeff Johnson 1999-06-04 09:18:59 UTC
Typing "rpm -q gmc" will display the name-version-release (the
package release is -12)


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