#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
<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
<asimvoc>allright
<asimvoc>i will do
<riteo>lemme know how it goes
<riteo>gl
<asimvoc>what permissions it will need?
<riteo>just like, user permissions
<riteo>`chown hellboy "/run/user/$(id -u hellboy)"`
<riteo>`chgrp hellboy "/run/user/$(id -u hellboy")`
<riteo>and some chmod for taste
asimvocquit (Excess Flood)
<riteo>shoot wrong quoting on the second one
<riteo>hope ya catch it
asimvocjoined
<asimvoc>oh my fucking god
<asimvoc>now pwuvcontrol work
<riteo>wahoo
<asimvoc>now what more?
<riteo>restart chromium and try casting
<asimvoc>same
<riteo>what do the logs say
<asimvoc>https://0x0.st/X5TY.txt
<asimvoc>the same
<riteo>I think it's not finding the pipewire socket for some reason?
<riteo>wait does pwvucontrol output any useful data
<riteo>instead of like Dummy Output
<riteo>also check if in the runtime dir there's a pipewire socket
Later messages