#kisslinux

Unofficial KISS Linux community channel | https://kisscommunity.bvnf.space | post logs or else | song of the day https://yewtu.be/watch?v=S81bNIK4MaE
Earlier messages
<riteo>that's important
<asimvoc>dbus-launch dwl -s 'foot -s & pipewire & wbg /home/hellboy/Documents/Wallpapers/wallhaven-kxoqdm_1920x1080.png <&-'
<riteo>oh allright you did that inside dbus-launch
<riteo>then it's fine I think
<asimvoc>well
<riteo>you tried that pwvcontrol flatpak I sent?
<asimvoc>can send me again?
<asimvoc>will try now
<riteo>sure
<asimvoc>but i dont see why will work
<riteo>com.saivert.pwvucontrol
<riteo>asimvoc: because of the dummy output thing
<riteo>it's a pipewire mixer and it's flatpaked too so you should be able to see if flatpak is at least working there
<asimvoc>just need to restart chromium or the hole thing?
<riteo>no wait it's a separate app
<riteo>just run it and you should see basically pavucontrol but for pipewire
<asimvoc>started
<asimvoc>And get
<asimvoc>Lost Connection do Pipewire server
phinxyquit (Ping timeout: 248 seconds)
<riteo>bingo
<riteo>so flatpaked apps can't seem to connect to pipewire for some reason
<riteo>first of all, sanity check, `wpctl status` works?
<asimvoc>yeap
<riteo>all right
<riteo>try passing `XDG_RUNTIME_DIR` to the dbus activation environment
<asimvoc>just export?
<riteo>I had to switch my xdg runtime dir to the default location because applications were just ignoring it
<riteo>no export, dbus-update-activation-environment
<riteo>wait you did the dbus-update-activation-environment
<asimvoc>not this time
<asimvoc>but i did it
<riteo>you have to do it every time you start a user session afaik
<asimvoc>just the command without i3sock and swaysock
<asimvoc>did it
<riteo>oh all right
<asimvoc>nothing
<riteo>also add XDG_RUNTIME_DIR there
<riteo>in the command
asimvocquit (Remote host closed the connection)
asimvocjoined
<asimvoc>still the same
<riteo>I think flatpaked applications aren't finding the custom runtime dir
<riteo>for some reason
<riteo>the default location for that dir is `/run/user/$(id -u)`
<riteo>you could try making a dir there, adding permissions for your user and pointing the runtime dir variable there
<riteo>I had a similar problem
<riteo>ughhhhhhhh it looks indeed that's the issue
<riteo>there's this https://github.com/flatpak/flatpak/issues/4372 which is supposed to be fixed but I swear that I've seen a similar problem lately too
<riteo>just try the conventional `/run/user/$(id -u)` dir first
Later messages