Settings / File Associations entry for inode/directory contained, in the following order: Dolphin Gwenview Filelight With this configuration, opening the downloads directrory from firefox would open the directory in Filelight. Fixed by removing everything except Dolphin from the inode/directory list in File Associations panel, although this should not have been necessary. Reproducible: Always Steps to Reproduce: 1. Install Kubuntu 14.10 2. Install Firefox, remove rekonq, install filelight 3. Download something in firefox and try to open downloads directory from firefox Actual Results: Directory opens in filelight. Expected Results: Directory should open in Dolphin. Dolphin is above filelight in File Associations panel.
Hm, Firefox is no KDE application, so I wonder how it should respect those settings.
In Qt there's QDesktopServices::openUrl and I imagine there's some GTK equivalent which will be interpreted by KDE to launch the appropriate application. Shouldn't the choice of child application happen outside the parent application?
Hi ! I noticed a strange behavior regarding files associations, that only affect some GTK apps like Firefox / Thunderbird. I may file another bugreport if necessary. How to reproduce : 1) install a clean KDE Neon distribution (or Manjaro KDE, same behavior). Plasma 5.12.1. 2) install wine 3) check the files associations for PNG and JPEG images in the KDE settings : gwenview is first, wineserver is second 4) try to open a PNG or JPG in Dolphin : Gwenview is indeed invoked 5) try to open a PNG or JPG in Firefox : wineserver is invoked !! WORKAROUND 6) go back to the files associations preferences, move some items back and forth in the PNG / JPG lists ; save them 7) now, Gwenview will be invoked in Firefox, even though the list appears to be the same ! Gwenview is indeed displayed as "default" in the FF/TB preferences (while it was wineserver before) SO : the KDE files associations list IS taken into account by Firefox / Thunderbird BUT it has to be modified / saved first for some unknown reasons.
Confirmed as still happening on Kubuntu 19.10. Also confirmed that the workaround on comment #3 works.