Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Version-Release number of selected component (if applicable):
RHEL-7.0-20140307.n.0
Steps to Reproduce:
1. In a terminal window, as a non-root user, run "nautilus."
2. Make sure that nautilus has focus. This will be confirmed by a "Files"
menu being visible just to the right of "Activities" in gnome-shell. If
nautilus is not in focus, either click on or alt-tab to a nautilus window.
3. In a terminal window, as a non-root user, run "echo foo > ~/foo.txt"
4. In a terminal window, as a non-root user, run "echo bar > ~/bar.txt"
5. In a terminal window, as a non-root user, run "echo baz > ~/baz.txt"
6. In a terminal window, as a non-root user, run "chmod a-r ~/foo.txt ~/
bar.txt"
7. In a terminal window, as a non-root user, run "chmod a-w ~/foo.txt ~/
baz.txt"
1. Examine the icons for the foo.txt, bar.txt, and baz.txt files in nautilus.
Actual results:
All text files have same icons.
Expected results:
1. The foo.txt icon should have both a padlock icon and an x icon superimposed
on it.
2. The bar.txt icon should have an x icon superimposed on it.
3. The baz.txt icon should have a padlock icon superimposed on it.
Created attachment 878503[details]
add Requires on gnome-icon-theme-legacy
The "fix" in this case is very simple: install gnome-icon-theme-legacy
The problem is that for the emblems which Nautilus uses, the legacy names from gnome-icon-theme are used, and the legacy symlinks are only provided in gnome-icon-theme-legacy. On a default Fedora 19 install (which otherwise has very similar versions of packages to RHEL 7), Rhythmbox is installed by default, and Requires gnome-icon-theme-legacy. RHEL 7 does not have Rhythmbox installed by default, so gnome-icon-theme is not pulled in by default.
The fix should be to add gnome-icon-theme-legacy to the Nautilus Requires, which is what the attached patch does.
Brew scratch build: http://brewweb.devel.redhat.com/brew/taskinfo?taskID=7250158
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
Version-Release number of selected component (if applicable): RHEL-7.0-20140307.n.0 Steps to Reproduce: 1. In a terminal window, as a non-root user, run "nautilus." 2. Make sure that nautilus has focus. This will be confirmed by a "Files" menu being visible just to the right of "Activities" in gnome-shell. If nautilus is not in focus, either click on or alt-tab to a nautilus window. 3. In a terminal window, as a non-root user, run "echo foo > ~/foo.txt" 4. In a terminal window, as a non-root user, run "echo bar > ~/bar.txt" 5. In a terminal window, as a non-root user, run "echo baz > ~/baz.txt" 6. In a terminal window, as a non-root user, run "chmod a-r ~/foo.txt ~/ bar.txt" 7. In a terminal window, as a non-root user, run "chmod a-w ~/foo.txt ~/ baz.txt" 1. Examine the icons for the foo.txt, bar.txt, and baz.txt files in nautilus. Actual results: All text files have same icons. Expected results: 1. The foo.txt icon should have both a padlock icon and an x icon superimposed on it. 2. The bar.txt icon should have an x icon superimposed on it. 3. The baz.txt icon should have a padlock icon superimposed on it.