| Earlier messages |
|---|
| <riteo> | uuuhh wait |
| <riteo> | you started pipewire in the user session? |
| <riteo> | because if you restart the compositor for some reason it gets confused because the dbus user connection is lost |
| <asimvoc> | i started in user session |
| <asimvoc> | is in my .profile |
| <riteo> | yeah but without restarting or something |
| <asimvoc> | yeah |
| <riteo> | like there's only one fresh process ever since you started dwl |
| <riteo> | all right |
| <asimvoc> | it just init pipewire when i loggin in |
| <riteo> | I'm trying to check my mental checklist |
| <riteo> | asimvoc what's your XDG_RUNTIME_DIR? |
| <asimvoc> | tmp/1000-runtime-dir |
| phinxy | quit (Ping timeout: 252 seconds) |
| <riteo> | mhhhh |
| <riteo> | that's really weird |
| phinxy | joined |
| <asimvoc> | yup |
| <riteo> | so to recap you have a dbus user session, pipewire, xdg-desktop-portal-* all started in this order |
| <asimvoc> | yup |
| <asimvoc> | my init profile is this order |
| <riteo> | uh wait |
| <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 |
| phinxy | quit (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 |
| Later messages |
|---|