Bug 164819 - amarok freezes keyboard through problems with sound engine
Summary: amarok freezes keyboard through problems with sound engine
Status: RESOLVED DUPLICATE of bug 109322
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-24 12:52 UTC by Kamil Dabrowski
Modified: 2008-06-24 20:34 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kamil Dabrowski 2008-06-24 12:52:48 UTC 
Version:            (using KDE 3.5.9)
Installed from:    Gentoo Packages
OS:                Linux

When i'm using Firefox and i want to see some movie on YouTube, first thing which i do is pausing amarok. Win+C, it's ok. I hear sound in Firefox. Then, when movie is still playing i put Win+X to play music in amarok. What happens? It freezes all keyboard signals in all programs. One thing which i can do, is to kill amarok. Without keyboard i cannot do this in terminal, so i've used KDE Guard System and have killed program by mouse.

Amarok version - 1.4.8
Comment 1 Mark Kretschmann 2008-06-24 15:40:56 UTC 
Yeah, the keyboard freezing thing is a known issue, probably from KDE, and has been reported before. You might want to search the KDE bug reports.

Annoying, but not really related to Amarok.
Comment 2 Kamil Dabrowski 2008-06-24 15:53:21 UTC 
Yeah. I've been searching more and i've found people have this problem without using amarok :) But that was in some old 3.1 (sth about that) version of KDE. Well, it must be something randomly happening in KDE. "It" should be "off" (meant: bug destroyed) in KDE4.
Comment 3 Kamil Dabrowski 2008-06-24 17:26:39 UTC 
I want to notice that even Num Lock stops working then. Maybe it would be some pointer to repair this.
Comment 4 Bram Schoenmakers 2008-06-24 20:34:47 UTC 

*** This bug has been marked as a duplicate of 109322 ***