STEPS TO REPRODUCE 1. Use Dolphin from Flatpak 2. Click on a PDF file OBSERVED RESULT A list of potential apps appears, but it doesn't include Okular EXPECTED RESULT Okular is part of that list SOFTWARE/OS VERSIONS KDE Plasma Version: master KDE Frameworks Version: master Qt Version: 5.15.3 ADDITIONAL INFORMATION The list of choices contains 'okularApplication_pdf', but the list of all apps only contains 'org.kde.okular'. That results in Okular not being shown
Can reproduce.
Can you still reproduce this? For me okular shows up just fine on master.
I'm still able to reproduce with everything on master and Okular installed from distro packages, built from source, and also as a flatpak. :)
Ha! It only happens with a system okular not with flatpak okular
This is a bit awkward... okularApplication_pdf.desktop is the actual desktop file associating with pdf, org.kde.okular.desktop does not. What happens then is that the xdg-desktop-portal queries the options for pdf, it gets back okularApplication_pdf.desktop and whatever else may handle pdf e.g. XDP: Recommended handlers for file, application/pdf: okularApplication_pdf, org.chromium.Chromium, org.gimp.GIMP, inkscape this then further trips up inside the portal because a) there isn't a single choice b) the scheme to be opened isn't remote and so should_use_default_app() doesn't apply c) right out the gate the user wouldn't have picked okular often enough for it to get auto-selected (i.e. the user would have had to pick okular a number of times from the dialog before it becomes implicit default) ultimately this results in the dialog popping up (which is kind of silly TBH) and that dialog will then does not contain okular because okularApplication_pdf.desktop is NoDisplay and org.kde.okular.desktop doesn't associate with PDF. Long story short: the behavior is expected. This ultimately shouldn't happen though, this bug is in effect a variant of https://github.com/flatpak/xdg-desktop-portal/issues/472 - the portal really shouldn't be starting an appchooser dialog for pdf at all, but start the default app. The only practical reason for the app chooser to appears is when no handlers are found or when the user set always-ask on his system.
If we have all the information we need, we should be able to respond before even showing the dialog. What am I missing?
There's a flag that tells the xdg portal to invoke the impl even when otherwise not needed. That flag is not passed along as best I can tell. i.e. the application can explicitly ask for the dialog but we don't know whether that is the case (in which case we'd have to show the dialog) or not (which is when we could just return a value)