Bug 122008 - Sound output freezes X
Summary: Sound output freezes X
Status: RESOLVED WORKSFORME
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Sound (show other bugs)
Version: Alpha 1
Hardware: i686 SUSE Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Takashi Iwai
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-10 15:58 UTC by Forgotten User OS1JNCFbCX
Modified: 2005-10-14 12:09 UTC (History)
0 users

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User OS1JNCFbCX 2005-10-10 15:58:54 UTC
Since today I have a very strange effect on a ThinkPad T42p running 10.1 alpha1.
The interesting thing with this problem is that it does now occur reproducable
although it did never occur before and I did neither install new software nor
did I change the setup of the machine in any way.

The problem is that whenever any KDE application produces sound output the X
server does no longer react to the keyboard. The mouse pointer can still be
moved but clicking to any place on the desktop does not have any effect. What I
still can to is switching to a text console and running any application there. I
can even restart the X server from there which again results in a running X
system until another sound is played. This even happens after the whole system
is rebooted.

There is no message in syslog when the problem occurs.

When I unload all sound drivers before logging into KDE everything runs stable
(but obviously the sound).

The sound chip in the machine is a "Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)".

Any idea where I could look for the source of this problem? Any stale socket
file or something like that?
Comment 1 Forgotten User OS1JNCFbCX 2005-10-13 11:05:37 UTC
Hmm, now works again without changing anything.

Still the question: Do you have any idea what could have caused this?
Comment 2 Takashi Iwai 2005-10-14 12:09:26 UTC
No certain idea.  The X driver problem?