Anton Aylward said the following on 05/22/2010 09:42 PM:
I have a problem starting acroread from both Konqueror and Dolphin when clicking on a PDF icon.
Acroread starts up OK, but then I get a warning window saying
Error launching /home/anton/.local/share/applications/acroread.desktop Either KLauncher is not running anymore, or it failed to start the application
Well it started the application :-) So I click on OK for that modal dialogue box and ...
Acroread starts up again with the same file! I close acroread and now there's another modal dialogue box saying
KDEInit: could not launch /usr/bin/acroread
I've googled around a but but not found why this nonsense is happening.
I also ave Foxit and okular as alternatives This doesn't happen with them.
I found "a" solution.to this. I don't know if my reasoning makes sense. It seems that when you click on an icon in Konqeror or Dolphin it looks up the mime type and gets a corresponding <application>.desktop file that tells it what to do. I presume there is a search path analogous to the shell's PATH for this. When I edited the parameters for acroread it could not save them as /usr/share/applications/acroread.desktop and saved them instead as /home/anton/.local/share/applications/acroread.desktop It now seems that /home/anton/.local/share/applications/ is on the search path ahead of /usr/share/applications/ That would be fine, but it seems that unlike the shell, its not a "first found" matter. Having found /home/anton/.local/share/applications/acroread.desktop it goes on to find and execute according to /usr/share/applications/acroread.desktop AS WELL. Why the error messages are what they are, I don't understand. If - BIG IF - my interpretation is correct, then EITHER it was designed that way for some reason, but is also producing those odd messages OR the continuing after finding the first .desktop is a bug Of course if it is a bug then the bug may be that the first appears to fail so its perfectly reasonable to go on to the second. "Appears to fail"? I say "appears" because acroread does come up that first time and displays the PDF correctly. I only get the error dialog after leaving that first acroread. Which is why I wonder if the "bug" is an exit code from acroread. Removing one .desktop file or the other seems to clear the whole thing up, but I'm still wondering what's going on. Perhaps someone familiar with KDE internals can advise so I'll know what bug to post. Or not. -- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Knuth -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org