You are not logged in.

#1 2016-03-11 14:19:15

MaxATK
New Member
Registered: 2016-03-11
Posts: 2

Another sound problem :(

Hello everybody

So, after a fresh intall of Bunsenlabs, surprise, no sound.
After a few hours of reading on this forum, everything looks ok.

But still no sound. In the mixer pavucontrol I see the sound level "dancing" but no sound at the jack plug.

When I run "volti &" I see some problem :

maxime@navi:~$ volti &
[1] 3030
maxime@navi:~$ Xlib.protocol.request.QueryExtension
X protocol error:
<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 667, sequence_number = 10, major_opcode = 33, minor_opcode = 0
X protocol error:
<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 667, sequence_number = 11, major_opcode = 33, minor_opcode = 0
X protocol error:
<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 667, sequence_number = 12, major_opcode = 33, minor_opcode =

Anyone have an idea what this means ?

I am now clueless

Thanks

Offline

#2 2016-03-11 14:39:32

damo
....moderator....
Registered: 2015-08-20
Posts: 6,734

Re: Another sound problem :(

I presume that you went through the steps in the sticky HowTo? Getting Sound working in BL

Now it is time to test it. from the terminal run volti like this:

volti &

If you do not get an error, your volti icon should pop up on your tint2 taskbar. If it does not, you will need to review 'aplay -l' and select another sound device.


Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt  «» BunsenLabs on DeviantArt

Offline

#3 2016-03-11 14:46:48

nobody
The Great
Registered: 2015-08-10
Posts: 3,655

Re: Another sound problem :(

damo wrote:

I presume that you went through the steps in the sticky HowTo? Getting Sound working in BL

Now it is time to test it. from the terminal run volti like this:

volti &

If you do not get an error, your volti icon should pop up on your tint2 taskbar. If it does not, you will need to review 'aplay -l' and select another sound device.

There's a possibly relevant comment about conflicting hotkeys here.

carstene1ns commented on 2014-12-30 23:04

@kiarash: BadAccess generally means that the hotkey is already assigned[1]. Do you have any other software running that might use the configured keys? Depending on the keys you want to use, this includes your window manager, browser, music player, etc. I suggest to close/reconfigure this software first and to try other hotkeys.
Also, install 'python2-xlib-svn', it includes some bugfixes as the last release is from 2009. If the problem persists, you can file a bug against volti upstream or ask for help on the forums.

[1]: http://stackoverflow.com/a/22727832
   
kiarash commented on 2014-12-30 13:48

Hi. My keyboard shortcuts don't work. I get this error on startup.

<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 157, sequence_number = 10, major_opcode = 33, minor_opcode = 0
X protocol error:
<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 157, sequence_number = 11, major_opcode = 33, minor_opcode = 0
X protocol error:
<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 157, sequence_number = 12, major_opcode = 33, minor_opcode = 0

Offline

#4 2016-03-11 15:03:43

damo
....moderator....
Registered: 2015-08-20
Posts: 6,734

Re: Another sound problem :(

The OP is running the command in a terminal, so the Xlib error shouldn't be anything to do with the keybinds?  Could it a theme/icon issue again?


Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt  «» BunsenLabs on DeviantArt

Offline

#5 2016-03-11 15:24:06

xaos52
The Good Doctor
From: Planet of the @pes
Registered: 2015-09-30
Posts: 695

Re: Another sound problem :(

Did OP install anything else, besides Bunsenlabs?

Offline

#6 2016-03-11 19:11:08

MaxATK
New Member
Registered: 2016-03-11
Posts: 2

Re: Another sound problem :(

I presume that you went through the steps in the sticky HowTo? Getting Sound working in BL

Indeed... volti still lunch and everything looks ok, except I have nothing out of the jack plug sad

Fresh install with some media software from depot

Offline

#7 2016-03-11 19:25:43

xaos52
The Good Doctor
From: Planet of the @pes
Registered: 2015-09-30
Posts: 695

Re: Another sound problem :(

some media software from depot

Care to expand on this?

Offline

#8 2016-03-26 07:18:03

svub
New Member
Registered: 2016-03-26
Posts: 1

Re: Another sound problem :(

Made volti work with this guide here, thanks!

And I think I figured out what caused the error

Xlib.protocol.request.QueryExtension
X protocol error:
<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 169, sequence_number = 10, major_opcode = 33, minor_opcode = 0
X protocol error:
<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 169, sequence_number = 11, major_opcode = 33, minor_opcode = 0
X protocol error:
<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 169, sequence_number = 12, major_opcode = 33, minor_opcode = 0

Openbox's autostart launches xfce4-volumed which seems to register hot keys already - but only the mute button works for me, not the volume keys. As a test, killing xfce4-volumed and restarting volti fixed it - no more error and mute, volume up, and down work. Thus, I just removed xfce4-volumed from my ~/.config/openbox/autostart. Seems to work so far. smile

Offline

Board footer

Powered by FluxBB