Rejecting for now. If someone has a patch I might consider it otherwise
this needs specification work at freedesktop.
** Changed in: alacarte (Ubuntu)
Status: Unconfirmed = Rejected
--
alacarte doesn't honor changed .desktop files
https://launchpad.net/bugs/62304
--
ubuntu-bugs mailing
Travis Watkins schrieb:
- Define error
it fails for the user with no visual feedback.
- Show me how alacarte is supposed to know when nautilus/gnome-panel
fails to launch a .desktop file
as described in the comment on 2006-09-25
Perhaps this should be reassigned to the panel? The original
The only way to reliably fix this is to fix the freedesktop
specification. The underlying problem is that there is no clean way
that meets the specification to override the NoDisplay attribute of the
.desktop file without copying the whole file to the user's applications
directory. Matthias's
I'm afraid I'm going to have to reject this bug on the basis that the
existing behaviour is well known, more predictable and is even
documented in the GNOME Desktop System Administrators Guide in the
online documentation:
Since user menu files take precedence over the system menu file, it
will
reopening, even if's documented, it doesn't make sense. there is a
proposed fix. documenting omissions isn't equivalent to fixing.
** Changed in: alacarte (Ubuntu)
Status: Rejected = Unconfirmed
--
alacarte doesn't honor changed .desktop files
https://launchpad.net/bugs/62304
--
- Define error
- Show me how alacarte is supposed to know when nautilus/gnome-panel fails to
launch a .desktop file
Perhaps this should be reassigned to the panel? The original .desktop
file is still in /usr/share/applications so it can look there.
--
alacarte doesn't honor changed .desktop
How would you suggest I fix this? Even if I read every .desktop file
that Alacarte had changed and updated the Exec that wouldn't be right,
people change the Exec lines on purpose (to add nonXgl or aoss, for
example). There is no way to automatically know when this should happen.
--
alacarte
save the original entry/entries from the desktop file together with the
changed file. Maybe in the case of an error, check the saved entry with
the one from the desktop file to see, if they changed. In my use case,
the Exec entry saved by alacarte and the original entry (not yet saved)
by alacarte