![](https://seccdn.libravatar.org/avatar/a4139df10120ce151e457fd1faff018d.jpg?s=120&d=mm&r=g)
On 1/14/21 3:35 AM, Patrick Shanahan wrote:
* Simon Becherer <simon@becherer.de> [01-13-21 10:36]:
Am 13.01.21 um 16:19 schrieb Wolfgang Mueller:
Having successfully performed "zypper install pavucontrol", I called "pavucontrol &", which opened a pop-up window containing the text "Establishing connection to PulseAudio. Please wait...". Then the system complained:
dbind-WARNING **: 16:02:59.169: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken
Any idea how to fix that?
mh, i am here at tumbleweed. i never started it from commandline, always from kde-menue multimedia.
i tested now from commandline: # pavucontrol
(pavucontrol:30222): dbind-WARNING **: 16:24:57.426: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-pcwnPdLd8U: Verbindungsaufbau abgelehnt
but it runs fine. (popup window with all the audio devices.) so i do not care about the warning message. !! its a warning not a error!!!
perhaps one need to be a member of audio group ???
Shouldn't be, in normal default configurations udev, logind and friends do magic so that the user who is logged in graphically has access to sound devices but remote users don't. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B