0.0.35: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined

If you are filing this issue with a regular release please try master as it might already be fixed.

• master
• 0.3.35
• 0.3.34

Version, Distribution, Desktop Environment:

pipewire: 0.3.35 Distributor ID: Ubuntu Description: Ubuntu 21.04 Release: 21.04 Codename: hirsute Desktop: MATE

Description of Problem:

• Can't play or record
• Can't list audios
• Can't do nothing

Steps to Reproduce:

1. Install from source or via PPA/pipewire_debian
2. Set configs meson configure build -Dprefix=/usr -Daudiotestsrc=disabled -Dauto_features=enabled -Db_lto=true -Db_pie=true -Dlibcamera=auto -Ddocs=enabled -Dexamples=enabled -Dinstalled_tests=enabled -Dman=enabled -Dtest=disabled -Dvideotestsrc=disabled -Dvideoconvert=disabled -Dvolume=enabled -Dlibcamera=disabled
3. Try to start services

Actual Results:

gdp@gdp:~$ sudo systemctl --user restart pipewire-pulse.socket 

Failed to connect to bus: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined (consider using --machine=<user>@.host --user to connect to bus of other user)

Expected Results:

Empty indicates that service was correctly restarted

Additional Info Eg. pw-dump -N > file (As Attachment Please):

gdp@gdp:~/Downloads$ sudo pw-dump -N > file
pw-dump: symbol lookup error: pw-dump: undefined symbol: pw_deinit

gdp@gdp:~$ sudo pw-cli info 0
[E][000002369.123398][local-socket.c:64 pw_protocol_native_connect_local_socket()] connect failed: XDG_RUNTIME_DIR not set in the environment
Error: "failed to connect: No such file or directory"


gdp@gdp:~$ pw-cli info 0
Error: "failed to connect: Connection refused"

gdp@gdp:~$ systemctl --user status pipewire
● pipewire.service - Multimedia Service
     Loaded: loaded (/usr/local/lib/systemd/user/pipewire.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2021-09-14 20:48:42 -05; 2min 51s ago
TriggeredBy: ● pipewire.socket
    Process: 6986 ExecStart=/usr/local/bin/pipewire (code=exited, status=203/EXEC)
   Main PID: 6986 (code=exited, status=203/EXEC)

Sep 14 20:48:42 gdp systemd[2263]: pipewire.service: Scheduled restart job, restart counter is at 5.
Sep 14 20:48:42 gdp systemd[2263]: Stopped Multimedia Service.
Sep 14 20:48:42 gdp systemd[2263]: pipewire.service: Start request repeated too quickly.
Sep 14 20:48:42 gdp systemd[2263]: pipewire.service: Failed with result 'exit-code'.
Sep 14 20:48:42 gdp systemd[2263]: Failed to start Multimedia Service.

gdp@gdp:~/Documents$ sudo alsactl init
alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model (HDA NVidia at 0xfc080000 irq 36)
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -6
Found hardware: "HDA-Intel" "Nvidia GPU 0a HDMI/DP" "HDA:10de000a,10de0101,00100100" "0x1458" "0x34d6"
Hardware is initialized using a generic method
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration -2
Found hardware: "USB-Audio" "USB Mixer" "USB0c45:6367" "" ""
Hardware is initialized using a generic method
alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model (HD-Audio Generic at 0xfca00000 irq 85)
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:2 use case configuration -6
Found hardware: "HDA-Intel" "Realtek ALCS1200A" "HDA:10ec0b00,18491202,00100001" "0x1849" "0x1202"
Hardware is initialized using a generic method

journal

changed the description

changed the description

changed the description

I am getting this same message as well. OpenSUSE Tumbleweed, pipewire 0.3.35.

Trying to sudo systemctl enable --user pipewire gives the error. So does trying to inspect the pipewire service in any way, shape, or form from systemctl.

I also tried uninstalling pipewire and installing pulseaudio. I'm getting similar stuff such as https://bugs.gentoo.org/779157 and https://www.reddit.com/r/pop_os/comments/mj6b3a/no_audio_over_hdmi_on_kernel_511/

you almost certainly want to run this as user, not as root. It runs in the user's session, starting it with sudo means you're trying to start it as root and the various env vars aren't set for that.

Isnt that why --user is passed? Changing state requires sudo privs. Not sure how else to do it then

--user tells systemctl to use the user session bus of the calling user. Since you invoke systemctl as root (through sudo), it will try to modify the session bus of the root user. just drop the sudo and things will work.

Sudo was the problem, thanks guys

closed