Version: 1.0 (using 4.00.00 (KDE 4.0.0), Kubuntu packages) Compiler: gcc OS: Linux (i686) release 2.6.22-14-generic My preferred application order is KPDF, then Adobe Acrobat Reader. This is set up in my File Associations config, which I edit via a menu in Konqueror (apparently Kubuntu removed it from the main crontrol centre for reasons best known by them!). Konqueror respects this, Dolphin for kde3 respected this, but dolpin-kde4 does not: it launches Acrobat.
Could you please check whether adjusting the file associations with KDE4's systemsettings works? I'm not sure whether the file associations for KDE3 are also valid for KDE4... Thanks!
Rich, is this issue still reproducible in KDE 4.0.3? Thanks!
On Thursday 24 April 2008 07:28:31 Peter Penz wrote: > ------- Additional Comments From peter.penz gmx at 2008-04-24 08:28 > ------- Rich, is this issue still reproducible in KDE 4.0.3? Thanks! I'm not using any KDE4 stuff anymore (way too slow on my hardware) so can't test further, sorry. If you're really stuck I could install it all again ... let me know. rich
> If you're really stuck I could install it all again ... let me know. No problem. I'm just trying to clean up the huge number of bug-reports; I've set the issue to WORKSFORME, as I cannot reproduce this issue here. If it still occurs with KDE 4.1 (which should be faster then KDE 4.0), please just reopen the issue again.
I'm having this issue in KDE 4.8.4 using Dolphin 2.0 (!) I have a JNLP file, and the launch order was IcedTea javaws, then Firefox, and so on. In spite of this, Dolphin kept opening the file in Chrome. So I used the KDE System Settings to delete every entry except the OpenJDK and Sun JDK JNLP launchers. Sure enough, Dolphin's "Open with" menu for the file only shows Java Web Start or OpenJDK Java Web Start. And yet... When I click the JNLP file, Dolphin launches Chrome to open it.
(In reply to comment #5) > I'm having this issue in KDE 4.8.4 using Dolphin 2.0 (!) > > I have a JNLP file, and the launch order was IcedTea javaws, then Firefox, > and so on. In spite of this, Dolphin kept opening the file in Chrome. @mathew It is better to open a new report instead of replying/hijacking an old report closed more than 4 years ago. Your problem is actually bug 291177. Try KDE SC 4.9
I upgraded to KDE 4.9 and it is indeed fixed. Thanks very much!