Skip to main content ↑ ↓
Topic: Problems with dbus, pulseaudio, pipewire and pam_systemd (Read 2871 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Problems with dbus, pulseaudio, pipewire and pam_systemd

Hello fellow artix users!

In my quest to switch from dwm to xmonad, I encountered a problem. Well, several.

First one was while trying to use xmobar :

Code: [Select]
xmobar: SocketError {socketErrorMessage = "Network.Socket.connect: <socket: 12>: does not exist (No such file or directory)", socketErrorFatal = True, socketErrorAddress = Just (Address "unix:path=/run/user/1000/bus")}


which I fixed by adding this to /etc/enviroment :

Code: [Select]
DBUS_SYSTEM_BUS_ADDRESS=unix:path=/run/dbus/system_bus_socket

DBUS_SESSION_BUS_ADDRESS=unix:path=/run/dbus/system_bus_socket


Now, xmobar got working, but now sound does not work, neither pulseaudio nor pipewire.

pulse says E: [pulseaudio] main.c: Daemon startup failed.

pipewire says :

Code: [Select]
~ ❯❯❯ pipewire
[W][01298.169664][  module-rtkit.c:  183 translate_error()] RTKit error: org.freedesktop.DBus.Error.AccessDenied
[W][01298.169692][  module-rtkit.c:  517 set_nice()] could not set nice-level to -11: Permission denied
[W][01298.172089][  module-rtkit.c:  183 translate_error()] RTKit error: org.freedesktop.DBus.Error.AccessDenied
[W][01298.172104][  module-rtkit.c:  504 idle_func()] could not make thread realtime: Permission denied
                                                                                                                                   

~ ❯❯❯ pipewire-pulse
[E][01367.657720][     dbus-name.c:   61 dbus_request_name()] Failed to acquire org.pulseaudio.Server: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.115115" is not allowed to own the service "org.pulseaudio.Server" due to security policies in the configuration file
[E][01367.762610][  pulse-server.c:  920 do_set_client_name()] pulse-server 0x5629aebb55c0: failed to connect client: Host is down



The pam_systemd in title is there because the xmobar problem was because of there not being pam_systemd.

Re: Problems with dbus, pulseaudio, pipewire and pam_systemd

Reply #1 –
You have added your user to the rtkit's group?

Re: Problems with dbus, pulseaudio, pipewire and pam_systemd

Reply #2 –
"pam_systemd.so" in your pam config?

If that is the case, you didn't convert properly your arch system.
It is not sufficient to just remove systemd, you  should replace each installed package by its artix equivalent, from the artix repos.

In short, while a conversion is possible, you are probably better off to just do a fresh install, since you need to reinstall most packages anyway.

Re: Problems with dbus, pulseaudio, pipewire and pam_systemd

Reply #3 –
Quote from: artoo – on
"pam_systemd.so" in your pam config?

If that is the case, you didn't convert properly your arch system.
It is not sufficient to just remove systemd, you  should replace each installed package by its artix equivalent, from the artix repos.

In short, while a conversion is possible, you are probably better off to just do a fresh install, since you need to reinstall most packages anyway.


I'm on a fresh installation of artix runit. Just saying that xmobar requires pam_systemd

Re: Problems with dbus, pulseaudio, pipewire and pam_systemd

Reply #4 –
xmobar is not in Artix repos.

Code: [Select]
$ pacman -Ss xmobar
galaxy/i3status 2.13-3 (i3)
    Generates status bar to use with i3bar, dzen2 or xmobar
community/i3status 2.13-3 (i3)
    Generates status bar to use with i3bar, dzen2 or xmobar
community/xmobar 0.38-7
    Minimalistic Text Based Status Bar
community is an Arch Linux repository, not Artix repository. There is no guarantee that Arch Linux repositories will work without systemd, since Arch uses exclusively that init system. To what extent that dependency goes is unknown to me. It could be a false dependency, in which case setting the dependency to elogind manually in PKGBUILD should do the trick, or it could be more substantial than that.

Off topic, I don't see why would anyone switch to xmobar over dwm. It has everything a WM should have, and you can even extend it through patches if needed. Anything requiring a lot of dependencies is bloat anyway.

Re: Problems with dbus, pulseaudio, pipewire and pam_systemd

Reply #5 –
we can´t import xmobar into artix due tons of haskell packages, sorry.
 

Re: Problems with dbus, pulseaudio, pipewire and pam_systemd

Reply #6 –
I have a computer with Xmonad installed with pipewire and it works pretty good in Artix.

https://forum.artixlinux.org/index.php/topic,2634.msg17321.html#msg17321

I had the same issue with xmobar and the problem was the way I had configured the .xinitrc.

You should have:

Code: [Select]
dbus-launch xmonad

Instead of:

Code: [Select]
xmonad

I would remove all the enviroments variable you set before and I would change the configuration in the .xinitrc file.

PS: In my new machine I decided to install other WM from the Artix repositories, I decided to avoid Archlinux repositories as much as I can. I enabled them because I need them for work.

Best regards.

Artix Linux Colombia