Changing the icon for a launcher on the Desktop shows the user's home folder instead of the location of the icon
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Nautilus |
Expired
|
Low
|
|||
One Hundred Papercuts |
Invalid
|
Undecided
|
Unassigned |
Bug Description
The properties dialog box for any icon on the gnome desktop shows you the current user's home folder instead of the current icon image (in say "/usr/share/
This does not occur when you see the Properties dialog of launchers in the gnome-panel or in Alacarte (the Menu Editor), which do show the current selected icon image.
How to recreate it:
Create a launcher on the gnome-panel for gnome-terminal. Right click on it and goto the properties dialog.
Then click on the icon image on the left. It will show you in the current selected icon image in its exact directory (say /usr/share/pixmaps)
Create an desktop launcher for gnome-terminal.
Right-click on the launcher and goto the Propeties dialog and click on the icon image appearing on the left. It shows the current user's home directory.
summary: |
- Changing an icon on the desktop shows the user's home folder instead of - current icon + Changing the icon for a launcher on the Desktop shows the user's home + folder instead of the location of the icon |
Changed in nautilus: | |
status: | Unknown → New |
Changed in nautilus: | |
importance: | Unknown → Low |
Changed in nautilus: | |
status: | New → Expired |
Thank you for bringing this bug to our attention. Unfortunately a paper cut should be a small usability issue that affects many people and is quick and easy to fix. I'm afraid this bug can't be addressed as part of this project.
I dont see any usability issue here. Hence not a papercut. Also, are you able to reproduce this in Karmic?
A paper cut is a minor usability annoyance that an average user would encounter on his/her first day of using a new installation of Ubuntu 9.10.
For further info about papercuts criteria , pls read > https:/ /wiki.ubuntu. com/PaperCut
Don't worry though, This bug has been marked as "invalid" ONLY in the papercuts project.
For resolution of the bug, kindly identify the projects affected and assign the bug to that project, otherwise the devs of the concerned project might not be notified of this problem.