I run openSuse Leap 15.2 with KDE plasma 15.18.6. When the built-in speaker is used by some program, the volume, which is very low, cannot be adjusted. When I click on the speaker icon in the panel, I see a pop-up window entitled "Audio Volume" with 2 tabs: - "Devices" with the message "No output or input devices found" and - "Applications" with the message "No applications play or recording audio". Why is the built-in speaker not recognized by KDE or Leap 15.2? How can I force the system to recognize the speaker? Thanks in advance and best regards, Wolfgang
Am 13.01.21 um 13:22 schrieb Wolfgang Mueller:
I run openSuse Leap 15.2 with KDE plasma 15.18.6.
When the built-in speaker is used by some program, the volume, which is very low, cannot be adjusted.
When I click on the speaker icon in the panel, I see a pop-up window entitled "Audio Volume" with 2 tabs:
- "Devices" with the message "No output or input devices found" and - "Applications" with the message "No applications play or recording audio".
Why is the built-in speaker not recognized by KDE or Leap 15.2? How can I force the system to recognize the speaker?
Thanks in advance and best regards, Wolfgang
Hello wolfgang, without exactly knowing what you are talking about "build in speaker" (did normally not have any audio, only beep, or you are talkling from a laptop), i suggest: install "pulse audio volum control" "pavucontrol" this will gave you more detailed posibilities of control of your audio output-input-devices than the kde build-in tool. simoN -- www.becherer.de
On Wed, 13 Jan 2021 at 14:30:18 +0100, Simon Becherer wrote:
[...] Hello wolfgang, without exactly knowing what you are talking about "build in speaker" (did normally not have any audio, only beep, or you are talking from a laptop),
You guessed it correctly: talking about a laptop, I have to apologize for not having mentioned it before.
i suggest: install "pulse audio volum control" "pavucontrol"
this will gave you more detailed posibilities of control of your audio output-input-devices than the kde build-in tool.
Thanks a lot, Simon. 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? Thanks in advance, Wolfgang
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!!! question is, could you raise or lower the sound output? check if you use the correct port. (line out) or (speakers) if speaker did not react, try to plug in external speakers and try again with this. if you have started a application, check again, there could be a new submenue inside pavucontrol where you could maybe exact for this application change settings (firefox as example sometimes has different output selection than the rest of the system) simoN -- B e c h e r e r GmbH Sondermaschinenbau Mauermatten Strasse 22 79183 Waldkirch Germany Tel.: (+49) (0)7681 3134 Fax: (+49) (0)7681 4378 Mail: info@becherer.de Web: www.becherer.de USt-ID-Nr.: DE 814912198 Registergericht: Freiburg HRB 701860 Geschäftsführer: Dipl.-Ing. (FH), EWE Simon H. Becherer Gerichtsstand / Sitz: Waldkirch Es gelten ausschließlich unsere allgemeinen Liefer- und Zahlungsbedingungen / Einkaufsbedingungen: www.becherer.de/AGB
* 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 ??? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
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
* Simon Lees <sflees@suse.de> [01-13-21 17:59]:
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.
fwiw: I am a member of "audio" and I do not get the "dbind-WARNING" and I do use pavucontrol but, I am on Tumbleweed. note: previous post delayed ~6 hours as I am currently under censorship. I have cc'd you so you do not have to wait. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
On 1/13/21 7:17 PM, Patrick Shanahan wrote:
* Simon Lees <sflees@suse.de> [01-13-21 17:59]:
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.
fwiw: I am a member of "audio" and I do not get the "dbind-WARNING" and I do use pavucontrol but, I am on Tumbleweed.
note: previous post delayed ~6 hours as I am currently under censorship. I have cc'd you so you do not have to wait.
Perhaps a little OT for this post, but as you name yourself a member of "audio"-- I don't know if that's a formal group, or what--here's my problem: Have a musical keyboard, "Studio 61" by Fatar, which I know works--I saw it demoed when I bought it--but I have yet to make a sound with it. When I research midi, I get recommends for several different midi apps, all of which seem to assume you have your keyboard working. What must I do to get the instrument to produce musical notes in my speakers? (TW). --doug
* Doug McGarrett <dmcgarrett@optonline.net> [01-13-21 21:12]:
On 1/13/21 7:17 PM, Patrick Shanahan wrote:
* Simon Lees <sflees@suse.de> [01-13-21 17:59]:
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.
fwiw: I am a member of "audio" and I do not get the "dbind-WARNING" and I do use pavucontrol but, I am on Tumbleweed.
note: previous post delayed ~6 hours as I am currently under censorship. I have cc'd you so you do not have to wait.
Perhaps a little OT for this post, but as you name yourself a member of "audio"-- I don't know if that's a formal group, or what--here's my problem: Have a musical keyboard, "Studio 61" by Fatar, which I know works--I saw it demoed when I bought it--but I have yet to make a sound with it. When I research midi, I get recommends for several different midi apps, all of which seem to assume you have your keyboard working. What must I do to get the instrument to produce musical notes in my speakers? (TW). --doug
you need to start a new thread as your conversation does not belong to this thread. ie: start a new message with a new To: and Subject: rather than responding to an existing message. or remove the "In-Reply-To:" header if you must respond using an existing msg. I have cc'd you as I am currently under censorship and this post may be delayed 6 or more hours before appearing on the list. after you provide a proper new post, we can discuss your problem(s). -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
Am 14.01.21 um 01:17 schrieb Patrick Shanahan:
!! its a warning not a error!!!
perhaps one need to be a member of audio group ???
fwiw: I am a member of "audio" and I do not get the "dbind-WARNING" and I do use pavucontrol but, I am on Tumbleweed.
do not ask why: today i tested again, (switching off computer over night) and i did not get the warning message any more.... tumbleweed, not a member of audio simoN -- www.becherer.de
On Wed, 13 Jan 2021 at 16:34:37 +0100, Simon Becherer wrote:
[...] question is, could you raise or lower the sound output? check if you use the correct port. (line out) or (speakers) if speaker did not react, try to plug in external speakers and try again with this. if you have started a application, check again, there could be a new submenue inside pavucontrol where you could maybe exact for this application change settings (firefox as example sometimes has different output selection than the rest of the system)
After any kind of trials, I did not manage PulseAudio to work. So, I gave up and returned to kmix which works without groans. Thank you, anyway. Wolfgang
On 13/01/2021 16:19, Wolfgang Mueller wrote:
You guessed it correctly: talking about a laptop, I have to apologize for not having mentioned it before.
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?
If you go to YaST -> Hardware -> Sound, is anything showing in the list as 'not configured'? If so, try doing a quick configuration with default settings. gumb
On Wed, 13 Jan 2021 at 18:00:08 +0100, gumb wrote:
[...] If you go to YaST -> Hardware -> Sound, is anything showing in the list as 'not configured'? If so, try doing a quick configuration with default settings.
You are right. Yast showed me two cards not yet configured. I configured one of them, the other one failed, but one was sufficient. Now, my audio works. Thanks a lot! Wolfgang
participants (6)
-
Doug McGarrett -
gumb -
Patrick Shanahan -
Simon Becherer -
Simon Lees -
Wolfgang Mueller