-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xdg-desktop-portal-wlr not starting #68
Comments
The logs you posted indicate a core dump, but I don't think you have debugging symbols for xdpw, so that won't help. I have a theory that xdpw is trying to exit gracefully (for one reason or another) but is segfaulting trying to free memory that was never allocated. I created an issue for that already, but it is secondary to your issue and it just means we don't have any nice log messages. Can you share the versions of pipewire, xdg-desktop-portal, and xdg-desktop-portal-wlr that you're using? On arch, the output of I think your real issue (including slow to start GTK apps) is improperly set environment variables. I wrote up an explanation here, but long story short, you should probably do what the sway wiki suggested, but for the XDG_CURRENT_DESKTOP variable. This particular writeup is new, and if it is helpful (or not), I'd appreciate feedback. Let me know how it goes. If you have no luck with tweaking variables or updating packages, we can gather logs from manual runs and possibly get a build with debugging symbols to test. |
Thank for the explanation. Unfortunately, setting the XDG_CURRENT_DESKTOP variable does not help either (in theory it is already correctly set in
These are the versions of the installed packages:
|
Okay, let's try starting xdpw manually. Kill both xdg-desktop-portal and xdg-desktop-portal-wlr and run the following: /usr/lib/xdg-desktop-portal -vr & /usr/lib/xdg-desktop-portal-wlr -l DEBUG 2>&1 | tee xdpw.log That log should help shed some light on what's going on. |
Ok, here is the log:
And after that the following started to appear:
|
This is your issue. Are you sure pipewire is running? It should start automatically via socket activation, but for debugging, I would recommend ensuring that it is already running. If you can confirm it is, do its logs contain anything of interest? It would have been better if you had run the exact command I shared, which would have increased the log level and given us more information. Also, can you confirm that you killed all existing xdp/xdpw instances first. |
Oh, I wrote it by hand and somehow didn't noticed the entire line. Here it is now:
Pipewire is definitely not starting. The systemd unit is inactive and if I try to start it manually I get this:
I will install the git version and see if that changes anything. Edit: |
You can start pipewire like this for more debugging output. The line mentioned in those pipewire logs is just a generic error handler, so we may need more verbose output.
Edit: Also, even though pipewire is giving that error, is it exiting? I'm assuming it is, but pipewire creates noisy logs. Some errors may not be fatal. |
OK. So I run The two red lines:
Edit: The output:
|
I can't say at this point why pipewire is failing to start on boot (or, more likely, as a result of socket activation), but starts fine when run manually. That's a pipewire issue (and one that I can't reproduce, as I have an identical setup with no issues). My recommendation might be to try uninstalling and reinstalling pipewire in case some service/socket files have gotten messed up. Also check on any systemd overrides that might be present for pipewire configs. It seems like xdpw is working as expected when pipewire is running though, so I am going to close this issue. As you continue to debug pipewire, if you have other questions I can help with, you can @ mention me in this closed issue, or I usually hang around #sway on freenode. If you try to reach me on IRC, nick mention me (danshick) so I get a notification. |
Thanks for your time @danshick ! I solved the problem! (I gues at least). The systemd units for |
No idea how it would have gotten masked. It definitely shouldn't be. Happy to help and glad it's fixed! |
Interestingly, I'm getting the same issue. It fails because it can't connect to pipewire, but the pipewire services are available: $ systemctl --user status pipewire.service
● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-12-08 13:40:08 PST; 14s ago
TriggeredBy: ● pipewire.socket
Main PID: 1093 (pipewire)
Tasks: 2 (limit: 38407)
Memory: 15.2M
CPU: 40ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
└─1093 /usr/bin/pipewire
Dec 08 13:40:08 nt-endeavour systemd[1085]: Started PipeWire Multimedia Service.
~
$ systemctl --user status pipewire.socket
● pipewire.socket - Multimedia System
Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-12-08 13:40:08 PST; 17s ago
Triggers: ● pipewire.service
Listen: /run/user/1000/pipewire-0 (Stream)
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/pipewire.socket
Dec 08 13:40:08 nt-endeavour systemd[1085]: Listening on Multimedia System.
~
$ systemctl --user status xdg-desktop-portal-wlr
× xdg-desktop-portal-wlr.service - Portal service (wlroots implementation)
Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal-wlr.service; static)
Active: failed (Result: exit-code) since Wed 2021-12-08 13:40:36 PST; 1s ago
Process: 1806 ExecStart=/usr/lib/xdg-desktop-portal-wlr (code=exited, status=1/FAILURE)
Main PID: 1806 (code=exited, status=1/FAILURE)
CPU: 5ms
Dec 08 13:40:36 nt-endeavour systemd[1085]: xdg-desktop-portal-wlr.service: Scheduled restart job, restart counter is at 5.
Dec 08 13:40:36 nt-endeavour systemd[1085]: Stopped Portal service (wlroots implementation).
Dec 08 13:40:36 nt-endeavour systemd[1085]: xdg-desktop-portal-wlr.service: Start request repeated too quickly.
Dec 08 13:40:36 nt-endeavour systemd[1085]: xdg-desktop-portal-wlr.service: Failed with result 'exit-code'.
Dec 08 13:40:36 nt-endeavour systemd[1085]: Failed to start Portal service (wlroots implementation).
~
$ /usr/lib/xdg-desktop-portal -vr & /usr/lib/xdg-desktop-portal-wlr -l DEBUG 2>&1 | tee xdpw.log
[1] 1846
2021/12/08 13:40:43 [ERROR] - config: no config file found
2021/12/08 13:40:43 [DEBUG] - config: outputname: (null)
2021/12/08 13:40:43 [DEBUG] - config: max_fps: 0.000000
2021/12/08 13:40:43 [DEBUG] - config: exec_before: (null)
2021/12/08 13:40:43 [DEBUG] - config: exec_after: (null)
2021/12/08 13:40:43 [DEBUG] - config: chooser_cmd: (null)
2021/12/08 13:40:43 [DEBUG] - config: chooser_type: default
XDP: load portals from /usr/share/xdg-desktop-portal/portals
2021/12/08 13:40:43 [DEBUG] - dbus: connected
2021/12/08 13:40:43 [DEBUG] - wlroots: wl_display connected
2021/12/08 13:40:43 [DEBUG] - pipewire: pw_loop created
2021/12/08 13:40:43 [DEBUG] - pipewire: establishing connection to core
XDP: loading /usr/share/xdg-desktop-portal/portals/wlr.portal
XDP: portal implementation for wlroots, sway, Wayfire, river
XDP: portal implementation supports org.freedesktop.impl.portal.Screenshot
XDP: portal implementation supports org.freedesktop.impl.portal.ScreenCast
XDP: loading /usr/share/xdg-desktop-portal/portals/gtk.portal
XDP: portal implementation for gnome
XDP: portal implementation supports org.freedesktop.impl.portal.FileChooser
XDP: portal implementation supports org.freedesktop.impl.portal.AppChooser
XDP: portal implementation supports org.freedesktop.impl.portal.Print
XDP: portal implementation supports org.freedesktop.impl.portal.Notification
XDP: portal implementation supports org.freedesktop.impl.portal.Inhibit
XDP: portal implementation supports org.freedesktop.impl.portal.Access
XDP: portal implementation supports org.freedesktop.impl.portal.Account
XDP: portal implementation supports org.freedesktop.impl.portal.Email
XDP: portal implementation supports org.freedesktop.impl.portal.Lockdown
XDP: portal implementation supports org.freedesktop.impl.portal.Settings
XDP: loading /usr/share/xdg-desktop-portal/portals/gnome-keyring.portal
XDP: portal implementation for gnome
XDP: portal implementation supports org.freedesktop.impl.portal.Secret
2021/12/08 13:40:43 [ERROR] - pipewire: couldn't connect to context
2021/12/08 13:40:43 [DEBUG] - pipewire: disconnecting fom core
2021/12/08 13:40:43 [ERROR] - xdpw: failed to initialize screencast |
Hi,
I am running Archlinux with sway and I don't know exactly when this started happening, but xdg-desktop-portal-wlr does not work for me anymore. The following error is shown:
Maybe related: I am also experiencing this problem with GTK apps taking a while to start. However, the solution stated there does not work for me.
The text was updated successfully, but these errors were encountered: