Closed fahimscirex closed 1 year ago
exec dbus-launch Hyprland >/dev/null 2>&1
what if you don't dbus-launch
?
exec dbus-launch Hyprland >/dev/null 2>&1
what if you don't
dbus-launch
?
same result
well generally this looks like an issue with your dbus, not xdph / xdp
well generally this looks like an issue with your dbus, not xdph / xdp
any suggestions or possible workaround?
No clue. I just use sysd like a normal human being lol
I use artix openrc and it works fine
@fahimscirex Try on your init script to set dbus-launch Hyprland
, I proudly enjoy Artix Openrc and Greetd and it works. ;)
I also use Artix(runit) I did just dbus-lauch Hyprland, then opened kitty and executed
/usr/lib/xdg-desktop-portal-hyprland
The output
2023/06/18 18:56:36 [ERROR] - pipewire: couldn't connect to context
2023/06/18 18:56:36 [ERROR] - xdpw: failed to initialize screencast
'impl->enter_count > 0' failed at ../pipewire/spa/plugins/support/loop.c:349 loop_leave()
Try if it works the same way for you, if it does, then probably something is running in the wrong order.
xdg-desktop-portal-hyprland should be automatically started; dbus-launch Hyprland from your desktop manager / greeter (SDDM, greetd, GDM...) almost every one uses desktop files to describe desktop options, or in case of greetd use a predefined option.
Also, take in mind that you will need to start pipewire and wireplumber at startup, use exec-once from hyprland config file.
closing due to the v1.0 rewrite
Telegram, Waybar, Firefox taking too much time to open, they works fine when I remove
xdg-desktop-portal
. I'm on Artix runit, so systemd isn't involved anywhere.