Pipewire issue | Arch Linux Community | Page 1

latent urchin Jan 12, 2024, 3:49 PM

#

[E][00036.104212] mod.rt | [ module-rt.c: 280 pw_rtkit_bus_get()] Failed to connect to session bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead

[E][00036.106659] spa.dbus | [ dbus.c: 332 impl_connection_get()] Failed to connect to session bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead

[E][00036.106785] mod.portal | [ module-portal.c: 330 pipewire__module_init()] Failed to connect to session bus: Input/output error

Got this while trying to run pipewire, what?

real venture Jan 12, 2024, 3:54 PM

#

what DE and display system

#

issue is probably dbus not running

latent urchin Jan 12, 2024, 3:55 PM

#

i3, WM X11

#

yeah

#

how do i start it

#

googled it and only got stackeroverflow stuff from docker or something

latent urchin Jan 12, 2024, 3:56 PM

#

real venture what DE and display system

oh lightdm too

real venture Jan 12, 2024, 3:58 PM

#

not sure what the i3 convention is but you want to start it when i3 starts

latent urchin Jan 12, 2024, 3:58 PM

#

ok

#

what is the command to start it?

latent urchin Jan 12, 2024, 3:59 PM

#

real venture not sure what the i3 convention is but you want to start it when i3 starts

dbus-daemon?

real venture Jan 12, 2024, 4:00 PM

#

you use startx?

latent urchin Jan 12, 2024, 4:01 PM

#

no

#

its weird but i first enter the terminal and then manually start lightdm

#

as for some weird reason, my vm doesnt start when there is an active display manager running

latent urchin Jan 12, 2024, 4:02 PM

#

real venture you use startx?

killing the display manager sends me back to it, only way is sudo systemctl disable lightdm.service and then reboot and go on

real venture Jan 12, 2024, 4:02 PM

#

right

#

well I'm not sure how you're supposed to set it up properly

latent urchin Jan 12, 2024, 4:02 PM

#

what is the command?

#

i can start it on startup of i3

real venture Jan 12, 2024, 4:03 PM

#

I'm not sure but it's maybe dbus-launch

latent urchin Jan 12, 2024, 4:06 PM

#

real venture I'm not sure but it's maybe `dbus-launch`

DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/dbus-kETT6GkmWJ,guid=4cd68ffe8a82af90428d117565a1b0c1
DBUS_SESSION_BUS_PID=3625

real venture Jan 12, 2024, 4:07 PM

#

I wasn't asking for the output

#

does pipewire work now

latent urchin Jan 12, 2024, 4:07 PM

#

no thats what it says

latent urchin Jan 12, 2024, 4:07 PM

#

real venture I wasn't asking for the output

no

real venture Jan 12, 2024, 4:08 PM

#

huh

latent urchin Jan 12, 2024, 4:27 PM

#

real venture huh

i dunno

real venture Jan 12, 2024, 4:30 PM

#

me neither!

latent urchin Jan 12, 2024, 4:37 PM

#

real venture me neither!

dbus-broker.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus-broker.service; static)
Active: active (running) since Fri 2024-01-12 21:42:50 UTC; 22min ago
TriggeredBy: ● dbus.socket
Docs: man:dbus-broker-launch(1)
Main PID: 631 (dbus-broker-lau)
Tasks: 2 (limit: 18803)
Memory: 5.6M (peak: 6.4M)
CPU: 200ms
CGroup: /system.slice/dbus-broker.service
├─631 /usr/bin/dbus-broker-launch --scope system --audit
└─633 dbus-broker --log 4 --controller 9 --machine-id 435d760146d844a>

Jan 12 21:42:50 AcerNitro5-Arch systemd[1]: Starting D-Bus System Message Bus...
Jan 12 21:42:50 AcerNitro5-Arch systemd[1]: Started D-Bus System Message Bus.
Jan 12 21:42:50 AcerNitro5-Arch dbus-broker-launch[631]: Ready
Jan 12 21:42:58 AcerNitro5-Arch dbus-broker-launch[631]: Activation request for 'o>
Jan 12 21:43:31 AcerNitro5-Arch dbus-broker-launch[631]: Activation request for 'o>

#

DBUS is running

#Pipewire issue