Review Request: When a .desktop file (app shortcut) is modified and "copied"(re-written) from a system-wide to a user location; the icon should be saved, even when it was not modified

Darío Andrés andresbajotierra at
Sun Aug 23 21:38:11 BST 2009

This is an automatically generated e-mail. To reply, visit:

Review request for kdelibs.


Mh, I don't really know if this is a big deal but I wanted to try to fix it. (I'm not even sure if the workflow that derived in bug 164472 is a valid one just to try to fix this)

The file properties dialog only saves the icon field in the .desktop files; if the icon was indeed changed.
However, there is one more case in which saving the icon field will be needed: when modifying an icon/desktop that represents a system-wide .desktop file; changing some attribute. This will cause the .desktop to be rewritten to a local place (~/.local/share/applications/kde4); but the DesktopPlugin of the file properties will not write the Icon field;  causing this new icons to have an unknown/invalid/empty icon.

The patch checks if the path changed from the start upto the save moment; and will force saving the Icon field if the file was also a .desktop one

This addresses bug 164472.


  svn:// 1013119 



Primary testing: it worked; and fixed bug 164472. Editing a local desktop file without changing the icon didn't applied the icon field again.

I see a trailing space. If I commit this I'm going to remove it.



More information about the kde-core-devel mailing list