[regression] Phonon notification that Audio (HDA intel) does not work after JAUNTY update.

Bug #367326 reported by gidantribal
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Project Neon
Invalid
Undecided
Unassigned
amarok (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: amarok

Version: 2.0-SVN-Neon (using 4.2.65 (KDE 4.2.65 (KDE 4.3 >=
20090226)), Project Neon)
Compiler: cc
OS: Linux (x86_64) release 2.6.28-11-generic
________________________________________________________________________________

After running program twice in a small amount of time, it will pop up a
notification (Phonon notification) and will not play any sound, like if 'mute'
option is enabled.

Curiously if I run amarok-nightly in debug mode it works. PLUS, sometimes
amarok still doesn't work even if I kill all related processes previously
posted.

Amarok developers told me this is a problem related to Ubuntu and closed my bug
report.

_________________________________________________________________________________
When amarok is closed, these processes remain:

ps aux | grep amarok:
gidan 10497 0.0 0.1 144248 7764 ? S 21:28 0:00 kdeinit4:
kio_file [kdeinit] file
local:/home/gidan/.amarok-nightly/tmp/ksocket-gidan/klauncherT10483.slave-socket
local:/home/gidan/.amarok-nightly/tmp/ksocket-gidan/amarokX10467.slave-socket
gidan 17841 0.4 0.2 160368 11460 ? S 22:44 0:00 kdeinit4:
kio_http [kdeinit] http
local:/home/gidan/.amarok-nightly/tmp/ksocket-gidan/klauncherT10483.slave-socket
local:/home/gidan/.amarok-nightly/tmp/ksocket-gidan/amarokw17822.slave-socket
gidan 17842 0.3 0.2 160528 11544 ? S 22:44 0:00 kdeinit4:
kio_http [kdeinit] http
local:/home/gidan/.amarok-nightly/tmp/ksocket-gidan/klauncherT10483.slave-socket
local:/home/gidan/.amarok-nightly/tmp/ksocket-gidan/amarokb17822.slave-socket
gidan 17843 0.3 0.2 160528 11576 ? S 22:44 0:00 kdeinit4:
kio_http [kdeinit] http
local:/home/gidan/.amarok-nightly/tmp/ksocket-gidan/klauncherT10483.slave-socket
local:/home/gidan/.amarok-nightly/tmp/ksocket-gidan/amarokZ17822.slave-socket
gidan 17844 0.3 0.2 160528 11544 ? S 22:44 0:00 kdeinit4:
kio_http [kdeinit] http
local:/home/gidan/.amarok-nightly/tmp/ksocket-gidan/klauncherT10483.slave-socket
local:/home/gidan/.amarok-nightly/tmp/ksocket-gidan/amarokh17822.slave-socket

Changed in amarok (Ubuntu):
status: New → Invalid
Revision history for this message
gidantribal (aedo999) wrote :

@Jonathan Thomas:

can you please tell me who should I refer to report this bug? This ping-pong is starting to become annoying. Amarok in my system doesn't work at all and you continue playing with each-other. thanks.

Changed in amarok (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
gidantribal (aedo999) wrote :

problem does not pop up if you install a fresh 9.04 release and do not perform an upgrade. I think it will be difficult to track this bug.

Revision history for this message
Myriam Schweingruber (myriam) wrote :

I'm running a local installation of Amarok, and I sometimes have sound on KDE startup (4.2.3 btw), but on track change, out of the blue, the soundcard switches to no sound card at all.

This is not related to Amarok btw, the same happens randomly with Firefox and Konqueror.

Most of the time, the sound card gets disabled on KDE startup, so I think this is more a phonon bug than anything else.

Strangely, reading all bugs coming in on bugzilla on a daily basis, this has only ever been reported with Kubuntu Jaunty, so it really seems to be distribution specific.

Maybe some kernel module is the culprit, as bug #365096 seems to indicate...

Revision history for this message
Francesco (keggy85) wrote :

I have the same bug, and sometimes chash my kmix too

Revision history for this message
Harald Sitter (apachelogger) wrote :

Well, amarok-nightly messes your phonon device list up (since it is using a different phonon stack at this point). Though, it doesn't fit the issue description here. The mess-up would only appear if you go like:
all working -> used amarok-nightly -> trying to use system amarok -> phonon acts up starts crying (or not because it sends sound to the wrong device...) -> only reconfiguring with the system phonon is going to repair that (well, until next time anyway)

So, unless everyone who experiences this issue uses amarok-nightly or kde-nightly I would think that this particular issue is rather unrelated to project neon.

Changed in project-neon:
status: New → Incomplete
Revision history for this message
Sander Valcke (sander-valcke) wrote :

"problem does not pop up if you install a fresh 9.04 release and do not perform an upgrade. I think it will be difficult to track this bug."

Maybe the answer is found here?

http://ubuntuforums.org/showthread.php?t=1142010

after an upgrade the "phonon-backend-xine" package is not installed (upgraded from hardy to intrepid to jaunty here, gnome ubuntu, package was not installed), maybe it is installed if you do a fresh install? I had the same error message as listed here, installing the suggested package made Amarok work again :)

Revision history for this message
Andrew Ash (ash211) wrote :

This sounds very similar to bug 349847. gidantribal, does installing phonon-backend-xine fix the issue for you? If so we can mark this bug a duplicate of that one.

Thanks!

Revision history for this message
Myriam Schweingruber (myriam) wrote :

Andrew, sorry to be a tad picky, but the package name is phonon-xine-backend.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as requested 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 project-neon:
status: Incomplete → Invalid
Changed in amarok (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.