Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Can not login on flatpak wayland

Can not login on flatpak wayland

Edit: Nevermind, had to activate the wayland permissions on the flatpak spotify app (did it via flatseal)

 

Original:

Plan

Premium

Operating System

Arch Linux 6.2.13

sway version 1.8.1

Flatpak 1.15.4

 

My Question or Issue

Is Wayland not supported or do I have another error? I can't see through that.

When i open spotify flatpak it says my credentials are not found (though I can login with these in the browser).

Then there Is the login button in the spotify flatpak app which doesn't open my browser.

How can I open the browser to login or pass the credentials?

I tried:

 

 

 

 

 

 

flatpak run com.spotify.Client --username=deviceusername --password=regularspotifypassword --show-console

 

 

 

 

 

 

thanks for any help

 

can't find browsercan't find browserlogin error, can't open browserlogin error, can't open browser

Reply
2 Replies

For me this solution does not work, as my password has special symbols in it (also spaces).

So... I was hitting the same issue with regards of the impossibility of opening the browser.


First, the diagnosis step is to try opening a URL from the flatpak sandbox, so that you can look at the error:


$ flatpak run --command=xdg-open com.spotify.Client https://www.google.com
Failed to call portal: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface ?org.freedesktop.portal.OpenURI? on object at path /org/freedesktop/portal/desktop


In my case: flatpak is missing the particular portal to open URLs. If that's your case:

1) make sure that xdg-desktop-portal, xdg-desktop-portal-wlr (for wayland desktops such as sway) and xdg-desktop-portal-gtk (as fallback for what's not implemented by wlr, which is the case for OpenURI)

2) make sure that xdg-desktop-portal is started with the correct environment variables so that it enables wlr.

see https://wiki.archlinux.org/title/XDG_Desktop_Portal#xdg-desktop-portal-wlr_does_not_start_automatica...

3) if you are using xdg-desktop-portal >= 1.17, the implicit fallback was disabled, and you need to manually configure that. See https://github.com/flatpak/xdg-desktop-portal/issues/1077#issuecomment-1715896552

🙂 hopefully this message may prevent a few hours of debugging as I did

Suggested posts