hello everyone!
I’ve had a bit of linux experience before, and was using Arco. I decided to hop to Endeavour for a cleaner experience without messy configs and default apps.
After a fresh install, the pulseaudio daemon is giving errors related to DBUS on startup, and aplay -l outputs no sound cards found. I can’t hear any audio, and pavucontrol only shows a dummy output and no devices to configure.
any help?
Why did you go for PulseAudio rather than PipeWire?
Such as?
What devices should be showing?
Could you provide the output of inxi -Faz ?
Also worth checking existing threads to see if you have similar hardware:
Welcome to the Forum. I also come from Arco enjoy Endeavour.
Someone will be along soon with an answer
2 Likes
yeah hi, i don’t really know the difference between pulse audio and pipewire but i had pulseaudio on arco so i went with that.
the pulseaudio daemon gives this error:
W: [pulseaudio] cli-command.c: stat('/etc/pulse/default.pa.d'): No such file or directory
W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead
W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead
the daemon does run though.
my mobo’s built in sound card should be showing up, i have a b560M ds3h.
here’s the output of inxi -Faz:
System:
Kernel: 5.17.7-arch1-1 arch: x86_64 bits: 64 compiler: gcc
v: 12.1.0 parameters: BOOT_IMAGE=/boot/vmlinuz-linux
root=UUID=1004fd2d-e233-4b58-812d-e9d1c6485734 rw loglevel=3
nowatchdog nvme_load=YES
Desktop: i3 v: 4.20.1 info: polybar vt: 7 dm: LightDM
v: 1.30.0 Distro: EndeavourOS base: Arch Linux
Machine:
Type: Desktop Mobo: Gigabyte model: B560M DS3H V2 v: x.x
serial: <superuser required> UEFI: American Megatrends LLC.
v: F3 date: 08/23/2021
CPU:
Info: model: 11th Gen Intel Core i5-11400F bits: 64
type: MT MCP arch: Rocket Lake family: 6 model-id: 0xA7 (167)
stepping: 1 microcode: 0x53
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled
cache: L1: 480 KiB desc: d-6x48 KiB; i-6x32 KiB L2: 3 MiB
desc: 6x512 KiB L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 800 high: 801 min/max: 800/4400 scaling:
driver: intel_pstate governor: powersave cores: 1: 800 2: 801
3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 9: 801 10: 800
11: 801 12: 800 bogomips: 62232
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2
ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and
__user pointer sanitization
Type: spectre_v2
mitigation: Enhanced IBRS, IBPB: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GA106 [GeForce RTX 3060 Lite Hash Rate]
vendor: Micro-Star MSI driver: nouveau v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 16 ports: active: DP-3
empty: DP-1,DP-2,HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:2504
class-ID: 0300
Device-2: Logitech Webcam C270 type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 1-3:3 chip-ID: 046d:0825
class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.3 with: Xwayland v: 22.1.1
compositor: Picom v: git-bc759 driver: X: loaded: modesetting
unloaded: vesa alternate: fbdev,nouveau,nv gpu: nouveau
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96
s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: DP-3 model: LG (GoldStar) 24GL600F
serial: <filter> built: 2021 res: 1920x1080 dpi: 92 gamma: 1.2
size: 531x298mm (20.91x11.73") diag: 609mm (24") ratio: 16:9
modes: max: 1920x1080 min: 720x400
OpenGL: renderer: llvmpipe (LLVM 13.0.1 256 bits)
v: 4.5 Mesa 22.0.3 direct render: Yes
Audio:
Device-1: Intel Tiger Lake-H HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel
alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3
chip-ID: 8086:43c8 class-ID: 0403
Device-2: NVIDIA vendor: Micro-Star MSI driver: snd_hda_intel
v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.1
chip-ID: 10de:228e class-ID: 0403
Device-3: Logitech Webcam C270 type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 1-3:3 chip-ID: 046d:0825
class-ID: 0102 serial: <filter>
Sound Server-1: ALSA v: k5.17.7-arch1-1 running: yes
Sound Server-2: PulseAudio v: 15.0 running: no
Sound Server-3: PipeWire v: 0.3.51 running: no
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8168 v: 8.050.00-NAPI modules: r8169
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000
bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp3s0 state: up speed: 1000 Mbps duplex: full
mac: <filter>
Bluetooth:
Device-1: TP-Link UB500 Adapter type: USB driver: btusb v: 0.8
bus-ID: 1-5:4 chip-ID: 2357:0604 class-ID: e001
serial: <filter>
Report: bt-adapter ID: hci0 rfk-id: 0 state: down
bt-service: enabled,running rfk-block: hardware: no
software: no address: <filter>
Drives:
Local Storage: total: 1.35 TiB used: 13.66 GiB (1.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Kingston
model: SA400S37480G size: 447.13 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD
serial: <filter> rev: 0000 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate
model: ST1000DM010-2EP102 size: 931.51 GiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD
rpm: 7200 serial: <filter> rev: CC46 scheme: GPT
Partition:
ID-1: / raw-size: 125.81 GiB size: 123.28 GiB (97.99%)
used: 13.63 GiB (11.1%) fs: ext4 dev: /dev/sda5 maj-min: 8:5
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 29.8 MiB (31.0%) fs: vfat dev: /dev/sda1 maj-min: 8:1
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 46.0 C mobo: 16.8 C
Fan Speeds (RPM): N/A
Info:
Processes: 278 Uptime: 5h 37m wakeups: 0 Memory: 15.5 GiB
used: 2.65 GiB (17.1%) Init: systemd v: 250 tool: systemctl
Compilers: gcc: 12.1.0 clang: 13.0.1 Packages: pacman: 1010
lib: 238 flatpak: 0 Shell: Zsh v: 5.8.1 running-in: alacritty
inxi: 3.3.15
That’s a Warning, not an Error.
Apparently PulseAudio isn’t running. Did you enable the service? What’s the output of
systemctl --user status pulseaudio
and
journalctl --user -u pulseaudio --no-pager
1 Like
Failed to connect to bus: No medium found
-- No entries --
@iron627
You could try adding this to the default grub command line and update grub.
snd_intel_dspcfg.dsp_driver=1
Try
sudo systemctl restart user@1000
where 1000 is your UID, then run the status command again.
that didn’t work 
Job for user@1000.service failed because the control process exited with error code.
See "systemctl status user@1000.service" and "journalctl -xeu user@1000.service" for details.
systemctl status user@1000.service:
× user@1000.service - User Manager for UID 1000
Loaded: loaded (/usr/lib/systemd/system/user@.service; static)
Active: failed (Result: exit-code) since Tue 2022-05-17 21:41:57 IST; 44s ago
Docs: man:user@.service(5)
Process: 2651 ExecStart=/usr/lib/systemd/systemd --user (code=exited, status=219/CGROUP)
Main PID: 2651 (code=exited, status=219/CGROUP)
CPU: 380us
May 17 21:41:57 hackmachine systemd[1]: Starting User Manager for UID 1000…
May 17 21:41:57 hackmachine systemd[1]: user@1000.service: Main process exited, code=exited, status=21>
May 17 21:41:57 hackmachine systemd[1]: user@1000.service: Failed with result ‘exit-code’.
May 17 21:41:57 hackmachine systemd[1]: Failed to start User Manager for UID 1000.
lines 1-12/12 (END)
journalctl -xeu user@1000.service:
░░ The job identifier is 31.
May 17 21:41:57 hackmachine systemd[620]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] fl>
May 17 21:41:57 hackmachine systemd[1]: user@1000.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit user@1000.service has successfully entered the 'dead' state.
May 17 21:41:57 hackmachine systemd[1]: Stopped User Manager for UID 1000.
░░ Subject: A stop job for unit user@1000.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit user@1000.service has finished.
░░
░░ The job identifier is 827 and the job result is done.
May 17 21:41:57 hackmachine systemd[1]: Starting User Manager for UID 1000...
░░ Subject: A start job for unit user@1000.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit user@1000.service has begun execution.
░░
░░ The job identifier is 827.
May 17 21:41:57 hackmachine systemd[1]: user@1000.service: Main process exited, code=exited, status=21>
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit user@1000.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 219.
May 17 21:41:57 hackmachine systemd[1]: user@1000.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit user@1000.service has entered the 'failed' state with result 'exit-code'.
May 17 21:41:57 hackmachine systemd[1]: Failed to start User Manager for UID 1000.
░░ Subject: A start job for unit user@1000.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit user@1000.service has finished with a failure.
░░
░░ The job identifier is 827 and the job result is failed.
Something is very wrong with your system. If the systemd user slice isn’t running then the vast majority of software will not run, or will not run in an expected way.
Check your system is fully up-to-date, check for any customisations you have made since installing, and if this is a fresh install then consider reinstalling and setting up from scratch, making sure things work before moving on to making another change.
2 Likes
alr, ill reinstall
that worked 
2 Likes
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.