jgrulich added a comment.
In https://phabricator.kde.org/D5775#108825, @apol wrote: > In https://phabricator.kde.org/D5775#108649, @jgrulich wrote: > > > In https://phabricator.kde.org/D5775#108558, @aacid wrote: > > > > > I don't think this is a fix. > > > > > > I can't really i good faith recommend people to use Okular from a flatpak if that means they can't start two okular instances. > > > > > > You have this problem even without this patch. When you now run two instances of Okular in flatpak then both will probably have same pid. Point of this patch is to make the dbus name predictable so you can allow access to it in flatpak manifest. > > > Albert has a point. Maybe it's something to bring to flatpak upstream, for example it could make sense to expose the actual pid as an env variable? Or a different but unique identifier? Problem is that the name, even when the pid would be unique, won't be predictable. You still need to change it to something like org.kde.appName.pid so you can use org.kde.appName.* in flatpak manifest. Problem is that you need to allow to own those dbus services and because of that the first instance won't let the other instance to register itself. REPOSITORY R271 KDBusAddons REVISION DETAIL https://phabricator.kde.org/D5775 To: apol, #frameworks, jgrulich Cc: aacid
