You are not logged in.
Pages: 1
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
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
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:48Hi. 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
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
Did OP install anything else, besides Bunsenlabs?
Offline
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
Fresh install with some media software from depot
Offline
some media software from depot
Care to expand on this?
Offline
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.
Offline
Pages: 1