amarok causes keyboard lock

[bob jones]

Binary package hint: amarok

 Not sure how to reproduce; all I know is that after pushing a global shortcut key, Amarok will stop playing and break my keyboard. PS/2 mouse is fine, but keyboard stops responding and even ctrl-alt-backspace won't work. Only way to unlock the keyboard is to manually launch xkill through a desktop shortcut and kill Amarok.

[Johannes Tophøj Rasmussen (betonarbejder)]

I too have experienced this. Could shut down amarok from the system tray with the mouse

[whyhankee (paul-paulsplace)]

Same here after upgrading from Kubuntu Feisty to Gutsy, never experienced it before.

Sometimes amarok stoppes playing after trying one of the multimedia keys, sometimes i just notice amarok has stopped playing. After that the keyboard seems to be locked-up. WIth a little 'luck' i can logout from the desktop using the mouse.

[whyhankee (paul-paulsplace)]

just tried to reproduce it, started it from the command-line, this was the output:

$ amarok
Amarok: [Loader] Starting amarokapp..
Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp.
kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x8f72e0 ): KAccel object already contains an action name "play_pause"
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x8f72e0 ): KAccel object already contains an action name "play_pause"
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
QObject::connect: Incompatible sender/receiver arguments
        StarManager::ratingsColorsChanged() --> ContextBrowser::ratingOrScoreOrLabelsChanged(const QString&)

After a while (still playing music): Very strange! got a DCOPReply opcode, but we were not waiting for a reply!

While later: music stopped.
This is the moment where i need to kill amarok, dont attempt to close it by clicking the systray icon, this will lockup my keyboard.

$amarok --version
Qt: 3.3.7
KDE: 3.5.8
Amarok: 1.4.7

[Josh (hashbrowncipher)]

Seems to be a duplicate of #55585, or at least extremely similar.

[whyhankee (paul-paulsplace)]

in my case the following bugreport was the problem:
http://bugs.kde.org/show_bug.cgi?id=112437
(i disabled the proxy configuration script in konq, and it seems fine now ?!?!)