You are not logged in.
Hi, I'm using Hyprland on wayland (wlroots), and everything worked flawlessly up until my last reboot. I'm not sure why, but it seems that `xdg-desktop-portal` and `xdg-desktop-portal-wlr` are suddenly failing to start.
This is the output of
systemctl --user status xdg-desktop-portal.service○ xdg-desktop-portal.service - Portal service
Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static)
Active: inactive (dead)
Oct 23 11:05:52 pc systemd[852]: Started Portal service.
Oct 23 11:09:52 pc systemd[852]: Starting Portal service...
Oct 23 11:09:52 pc xdg-desktop-por[2997]: No skeleton to export
Oct 23 11:09:52 pc systemd[852]: Started Portal service.
Oct 23 11:12:34 pc systemd[852]: Starting Portal service...
Oct 23 11:12:34 pc systemd[852]: Started Portal service.
Oct 23 11:12:34 pc xdg-desktop-por[4411]: No skeleton to export
Oct 23 11:13:06 pc systemd[852]: Starting Portal service...
Oct 23 11:13:06 pc xdg-desktop-por[4579]: No skeleton to export
Oct 23 11:13:06 pc systemd[852]: Started Portal service.And this is output of
systemctl --user status xdg-desktop-portal-wlr.service× 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 Sun 2022-10-23 11:16:03 CEST; 30min ago
Duration: 21ms
Process: 6746 ExecStart=/usr/lib/xdg-desktop-portal-wlr (code=exited, status=1/FAILURE)
Main PID: 6746 (code=exited, status=1/FAILURE)
CPU: 46ms
Oct 23 11:16:03 pc systemd[852]: xdg-desktop-portal-wlr.service: Scheduled restart job, restart counter is at 5.
Oct 23 11:16:03 pc systemd[852]: Stopped Portal service (wlroots implementation).
Oct 23 11:16:03 pc systemd[852]: xdg-desktop-portal-wlr.service: Start request repeated too quickly.
Oct 23 11:16:03 pc systemd[852]: xdg-desktop-portal-wlr.service: Failed with result 'exit-code'.
Oct 23 11:16:03 pc systemd[852]: Failed to start Portal service (wlroots implementation).When I try to start the portal manually, there's this error message (from `/usr/lib/xdg-desktop-portal-wlr`):
2022/10/23 11:27:05 [ERROR] - dbus: failed to acquire service name: File exists
'impl->enter_count > 0' failed at ../pipewire/spa/plugins/support/loop.c:346 loop_leave()And running `/usr/lib/xdg-desktop-portal` manually just results in:
(/usr/lib/xdg-desktop-portal:14065): xdg-desktop-portal-WARNING **: 11:32:48.391: No skeleton to exportThis might be caused by something new that I've installed or something similar, but I've no idea what exactly, I've been making a lot of changes before the reboot this happened after, as I was just setting up the machine, from the error message, it seems like it has something to do with pipewire? However I'm not sure what is the issue exactly and even how to debug it. Any suggestions?
Last edited by koumakpet (2022-10-23 10:30:43)
Offline
Ok, so quick update, there really seems to be something wrong with pipewire, but I'm not sure whether it's an actual pipewire issue, or whether it's because the portals aren't running.
While the sound seems to be working fine, the issue occurs with anything pulseaudio related (using `pipewire-pulse`). Running `pactl info` just results in
Connection failure: TimeoutHowever the service does seem to be running
systemctl --user status pipewire-pulse.service● pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; preset: enabled)
Active: active (running) since Sun 2022-10-23 11:05:55 CEST; 44min ago
TriggeredBy: ● pipewire-pulse.socket
Main PID: 1228 (pipewire-pulse)
Tasks: 2 (limit: 18412)
Memory: 800.0K
CPU: 5ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
└─1228 /usr/bin/pipewire-pulse
Oct 23 11:05:55 pc systemd[852]: Started PipeWire PulseAudio.
Oct 23 11:05:55 pc pipewire-pulse[1228]: pw.context: 0x5653de72c080: no modules loaded from context.modulesOffline
Marking as solved, this was actually not an issue with the portals, that was just me being stupid. The issue with portals was that hyprland wiki suggested making a script that restarts these portals, which killed the original running proccesses of these, and started them directly without using systemd. They then failed to restart because they were already running.
The actual issue that I had was just with `pipewire-pulse`, and this happened because I was trying to implement a fix for discord notification suggested by arch wiki, by adding `/etc/pipewire/pipewire-pulse.conf` file with certain configuration. The issue was that I used a wrong closing bracket (`}` instead of `]`), which clearly caused some issues, although it is surprising that this wasn't reported a bit more clearly in the `pipewire-pulse` systemd log. But anyway, basically this was just me being an idiot, marking fixed.
Offline