Audio Crashes X on Login with ATI IXP 150

Bug #125393 reported by Jeffrey on 2007-07-12
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
linux-source-2.6.20 (Ubuntu)

Bug Description

I have the HP Pavilion ZV5000 Laptop. (quite popular model)
Multimedia audio controller: ATI Technologies Inc IXP150 AC'97 Audio Controller

Steps to Reproduce:
1. Turn Computer On
2. At Login Screen enter your username and password
* Special Note: The User account that you login with needs to have Audio enabled for that account.
* To enable audio, go to System > Administration > Users and Groups > Enter Password > Select User > Click Properties > Go to Users Privileges Tab > Check User Audio Devices.

It will show the splash screen and start to play the music.
At this point in time, it will freeze X and stop playing the login music half way through the jingle.
Mouse and Keyboard still work but everything else will freeze.
The menu bar and background does not load.
If this were Windows, I would say, it is similar to the explorer process freezing or not loading.

More Information:
I can still get to the terminal from here and mess around.
I can also still use the CTRL+ALT+Backspace and it will take me back to the login screen, at which point I can at least restart the system.

Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in recently. We were wondering if this is still an issue for you? Thanks in advance.

Jeffrey (jeffreymcgrath) wrote :

Yes. It crashes my system like you can't believe.

Xubuntu, Ubuntu, Edubuntu, Linux Mint, Fedora, PCLinuxOS 2007 all have problems with audio.

So I dont know if it is a kernal issue or what.

Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at . Thanks in advance!

Changed in linux-source-2.6.20:
assignee: brian-murray → nobody
status: Incomplete → New

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.


2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Michele Mangili (mangilimic) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers