[Bug 1204864] New: xdg-desktop-portal not working after relogin
http://bugzilla.opensuse.org/show_bug.cgi?id=1204864 Bug ID: 1204864 Summary: xdg-desktop-portal not working after relogin Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs@opensuse.org Reporter: opendreas@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After relogin I cannot open links, pdf files in Telegram, Whatsapp, Kontact(Kmail), downloaded files in Firefox Flatpak. xdg-desktop-portal-kde won't start. For example, if I download a file with Firefox Flatpak and the system does not know which program to open it with, then xdg-desktop-portal-kde starts, but when I select the program with which the file should be opened, the program does not open. After a reboot everything opens again. System: OpenSUSE Leap 15.4 with Plasma 5.24.4. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204864 http://bugzilla.opensuse.org/show_bug.cgi?id=1204864#c1 Fabian Vogt <fabian@ritter-vogt.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fabian@ritter-vogt.de, | |opendreas@gmail.com Flags| |needinfo?(opendreas@gmail.c | |om) --- Comment #1 from Fabian Vogt <fabian@ritter-vogt.de> --- X11 or Wayland? Anything useful in the journal? If not, could you try "dbus-monitor" in parallel to triggering the issue? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204864 http://bugzilla.opensuse.org/show_bug.cgi?id=1204864#c2 --- Comment #2 from Andreas <opendreas@gmail.com> --- Created attachment 862555 --> http://bugzilla.opensuse.org/attachment.cgi?id=862555&action=edit dbus-monitor -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204864 http://bugzilla.opensuse.org/show_bug.cgi?id=1204864#c3 --- Comment #3 from Andreas <opendreas@gmail.com> --- (In reply to Fabian Vogt from comment #1)
X11 or Wayland? Anything useful in the journal? If not, could you try "dbus-monitor" in parallel to triggering the issue? X11
Journald, if I want to open a link in Telegram or Kontact Flatpak, Firefox won't start 3systemd Started app-flatpak-org.mozilla.firefox-12172.scope. user@1000.service Failed to load module "canberra-gtk-module" 3xdg-desktop-portal Invalid MIT-MAGIC-COOKIE-1 keyError: cannot open display: :99.0 xdg-desktop-portal-kde xdp-kde-background: GetAppState called: no parameters pdf from Telegram systemd Started app-flatpak-org.kde.okular-12948.scope. xdg-desktop-portal Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :99.0 xdg-desktop-portal qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. xdg-desktop-portal This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. xdg-desktop-portal Available platform plugins are: eglfs, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. dbus-monitor log when i click on link in telegram attached. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204864 http://bugzilla.opensuse.org/show_bug.cgi?id=1204864#c4 --- Comment #4 from Fabian Vogt <fabian@ritter-vogt.de> --- Display :99 sounds strange. Which display manager do you use? If it's lightdm, try sddm or gdm. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204864 http://bugzilla.opensuse.org/show_bug.cgi?id=1204864#c5 --- Comment #5 from Andreas <opendreas@gmail.com> --- (In reply to Fabian Vogt from comment #4)
Display :99 sounds strange. Which display manager do you use? If it's lightdm, try sddm or gdm. I'm using the default SDDM for KDE Plasma installation.
I reproduced this bug on Leap KDE Live CD 1. Install Firefox Flatpak 2. In the Firefox settings, set the opening of pdf files using the system application 3. Download pdf file and open 4. Relogin 5. Try to open it from downloads in Firefox -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204864 http://bugzilla.opensuse.org/show_bug.cgi?id=1204864#c6 --- Comment #6 from Fabian Vogt <fabian@ritter-vogt.de> --- (In reply to Andreas from comment #5)
(In reply to Fabian Vogt from comment #4)
Display :99 sounds strange. Which display manager do you use? If it's lightdm, try sddm or gdm. I'm using the default SDDM for KDE Plasma installation.
So the question is where DISPLAY=:99 is coming from. IIRC that's what Flatpak sets inside the sandbox for X11 mediation. I have no idea what might send that into the dbus activation environment.
I reproduced this bug on Leap KDE Live CD 1. Install Firefox Flatpak 2. In the Firefox settings, set the opening of pdf files using the system application 3. Download pdf file and open 4. Relogin 5. Try to open it from downloads in Firefox
I have the suspicion that flatpak breaks this somehow. Can you try the following (I don't have access to 15.4 myself currently): 1. qdbus-qt5 org.freedesktop.impl.portal.desktop.kde (to start the process without using flatpak) 2. Relogin 3. Try to trigger the issue And this: 1. Reproduce the issue 2. Run "qdbus-qt5 org.freedesktop.impl.portal.desktop.kde" (it should fail) 3. Run dbus-update-activation-environment --all 4. Try 2 again (it should succeed) 5. Try to trigger the issue again -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204864 http://bugzilla.opensuse.org/show_bug.cgi?id=1204864#c7 --- Comment #7 from Andreas <opendreas@gmail.com> --- (In reply to Fabian Vogt from comment #6)
(In reply to Andreas from comment #5)
(In reply to Fabian Vogt from comment #4)
Display :99 sounds strange. Which display manager do you use? If it's lightdm, try sddm or gdm. I'm using the default SDDM for KDE Plasma installation.
So the question is where DISPLAY=:99 is coming from. IIRC that's what Flatpak sets inside the sandbox for X11 mediation. I have no idea what might send that into the dbus activation environment.
I have the suspicion that flatpak breaks this somehow. Can you try the following (I don't have access to 15.4 myself currently): I tried to reproduce this on a Gnome Live CD and there is no such problem.
1. qdbus-qt5 org.freedesktop.impl.portal.desktop.kde (to start the process without using flatpak) I start it with sudo and "Could not connect to D-Bus server: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11"
And this: 1. Reproduce the issue 2. Run "qdbus-qt5 org.freedesktop.impl.portal.desktop.kde" (it should fail) 3. Run dbus-update-activation-environment --all 4. Try 2 again (it should succeed) 5. Try to trigger the issue again
sudo dbus-update-activation-environment --all "dbus-update-activation-environment: error: unable to connect to D-Bus: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11" -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204864 http://bugzilla.opensuse.org/show_bug.cgi?id=1204864#c8 --- Comment #8 from Andreas <opendreas@gmail.com> --- (In reply to Fabian Vogt from comment #6)
(In reply to Andreas from comment #5)
(In reply to Fabian Vogt from comment #4)
Display :99 sounds strange. Which display manager do you use? If it's lightdm, try sddm or gdm. I'm using the default SDDM for KDE Plasma installation.
So the question is where DISPLAY=:99 is coming from. IIRC that's what Flatpak sets inside the sandbox for X11 mediation. I have no idea what might send that into the dbus activation environment. Maybe this will be of some help https://github.com/flatpak/flatpak/issues/3357 https://github.com/flatpak/flatpak/issues/4279
I wanted to delete .Xauthority but the file is not in my home. Documentation says this file should be in home https://doc.opensuse.org/documentation/leap/security/html/book-security/cha-... xauth shows Using authority file /run/user/1000/xauth_coayRF I also tried changing the hostname, but that didn't help. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204864 http://bugzilla.opensuse.org/show_bug.cgi?id=1204864#c9 --- Comment #9 from Fabian Vogt <fabian@ritter-vogt.de> --- (In reply to Andreas from comment #7)
(In reply to Fabian Vogt from comment #6)
(In reply to Andreas from comment #5)
(In reply to Fabian Vogt from comment #4)
Display :99 sounds strange. Which display manager do you use? If it's lightdm, try sddm or gdm. I'm using the default SDDM for KDE Plasma installation.
So the question is where DISPLAY=:99 is coming from. IIRC that's what Flatpak sets inside the sandbox for X11 mediation. I have no idea what might send that into the dbus activation environment.
I have the suspicion that flatpak breaks this somehow. Can you try the following (I don't have access to 15.4 myself currently): I tried to reproduce this on a Gnome Live CD and there is no such problem.
1. qdbus-qt5 org.freedesktop.impl.portal.desktop.kde (to start the process without using flatpak) I start it with sudo
Don't run any of the commands with sudo. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204864 http://bugzilla.opensuse.org/show_bug.cgi?id=1204864#c10 --- Comment #10 from Andreas <opendreas@gmail.com> --- (In reply to Fabian Vogt from comment #9)
(In reply to Andreas from comment #7)
(In reply to Fabian Vogt from comment #6)
(In reply to Andreas from comment #5)
(In reply to Fabian Vogt from comment #4)
Display :99 sounds strange. Which display manager do you use? If it's lightdm, try sddm or gdm. I'm using the default SDDM for KDE Plasma installation.
So the question is where DISPLAY=:99 is coming from. IIRC that's what Flatpak sets inside the sandbox for X11 mediation. I have no idea what might send that into the dbus activation environment.
I have the suspicion that flatpak breaks this somehow. Can you try the following (I don't have access to 15.4 myself currently): I tried to reproduce this on a Gnome Live CD and there is no such problem.
1. qdbus-qt5 org.freedesktop.impl.portal.desktop.kde (to start the process without using flatpak) I start it with sudo
Don't run any of the commands with sudo.
qdbus-qt5 org.freedesktop.impl.portal.desktop.kde / /org /org/freedesktop /org/freedesktop/portal /org/freedesktop/portal/desktop It is the same without a issue and it doesn't fail with issue dbus-update-activation-environment --all nothing happens, the issue remains -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204864 http://bugzilla.opensuse.org/show_bug.cgi?id=1204864#c11 --- Comment #11 from Fabian Vogt <fabian@ritter-vogt.de> --- (In reply to Andreas from comment #10)
(In reply to Fabian Vogt from comment #9)
(In reply to Andreas from comment #7)
(In reply to Fabian Vogt from comment #6)
(In reply to Andreas from comment #5)
(In reply to Fabian Vogt from comment #4)
Display :99 sounds strange. Which display manager do you use? If it's lightdm, try sddm or gdm. I'm using the default SDDM for KDE Plasma installation.
So the question is where DISPLAY=:99 is coming from. IIRC that's what Flatpak sets inside the sandbox for X11 mediation. I have no idea what might send that into the dbus activation environment.
I have the suspicion that flatpak breaks this somehow. Can you try the following (I don't have access to 15.4 myself currently): I tried to reproduce this on a Gnome Live CD and there is no such problem.
1. qdbus-qt5 org.freedesktop.impl.portal.desktop.kde (to start the process without using flatpak) I start it with sudo
Don't run any of the commands with sudo.
qdbus-qt5 org.freedesktop.impl.portal.desktop.kde / /org /org/freedesktop /org/freedesktop/portal /org/freedesktop/portal/desktop
It is the same without a issue and it doesn't fail with issue
That is very strange, so the service is running correctly. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204864 http://bugzilla.opensuse.org/show_bug.cgi?id=1204864#c12 --- Comment #12 from Andreas <opendreas@gmail.com> --- (In reply to Fabian Vogt from comment #11)
(In reply to Andreas from comment #10)
(In reply to Fabian Vogt from comment #9)
(In reply to Andreas from comment #7)
(In reply to Fabian Vogt from comment #6)
(In reply to Andreas from comment #5)
(In reply to Fabian Vogt from comment #4) > Display :99 sounds strange. Which display manager do you use? If it's > lightdm, try sddm or gdm. I'm using the default SDDM for KDE Plasma installation.
So the question is where DISPLAY=:99 is coming from. IIRC that's what Flatpak sets inside the sandbox for X11 mediation. I have no idea what might send that into the dbus activation environment.
I have the suspicion that flatpak breaks this somehow. Can you try the following (I don't have access to 15.4 myself currently): I tried to reproduce this on a Gnome Live CD and there is no such problem.
1. qdbus-qt5 org.freedesktop.impl.portal.desktop.kde (to start the process without using flatpak) I start it with sudo
Don't run any of the commands with sudo.
qdbus-qt5 org.freedesktop.impl.portal.desktop.kde / /org /org/freedesktop /org/freedesktop/portal /org/freedesktop/portal/desktop
It is the same without a issue and it doesn't fail with issue
That is very strange, so the service is running correctly.
Maybe it's this bug that was fixed in Plasma 5.24.5? xdgactivation: Demand attention when a process fails to resolve its token https://invent.kde.org/plasma/kwin/-/commit/5390a4978f3a3903ede15ecd94a750b3... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204864 http://bugzilla.opensuse.org/show_bug.cgi?id=1204864#c13 --- Comment #13 from Andreas <opendreas@gmail.com> --- Here's another one, also fixed in 5.24.5 xdgactivation: Make sure we don't call setStartupId with an x11 token https://invent.kde.org/plasma/plasma-workspace/-/commit/3f4c5a22367732405a8c... -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com