Bug 176997

Summary: Last.fm stream stops when track changes
Product: [Applications] amarok Reporter: Dan <dan76>
Component: generalAssignee: Amarok Bugs <amarok-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Dan 2008-12-05 17:31:19 UTC 
Version:           SVN 892965 (using Devel)
Compiler:          gcc 4.3.2 -O3 -march=native
OS:                Linux
Installed from:    Compiled sources

I updated KDE SVN and phonon to latest svn trunk and Amarok stalls last.fm streaming when track changes. With phonon 4.2.0 the problem doesn't happen, but since the latest kdebase svn needs phonon 4.2.70 or better, I can't use phonon 4.2.0 anymore.

For example, the first track plays fine and if I click skip, it plays fine. But if I left track playing and it will change to the next track after it finished, it stalls and there's no sound anymore.

Probably a Amarok/phonon issue, but I don't know where's the problem.
Comment 1 Dan 2008-12-05 19:01:30 UTC 
Well, I'm closing this. The "solution" is to use phonon 4.2.80.
Comment 2 Dan 2009-10-25 17:38:57 UTC 

*** This bug has been marked as a duplicate of bug 172471 ***
Comment 3 Dan 2009-10-25 17:57:39 UTC 
I decided to reopen this because I still have this annoying problem. I'm using the latest KDE SVN, Lastest Phonon  SVN, latest xine( 1.1.16.3 ), latest Amarok and last.fm always get stuck when track changes...

How can I debug this? I want very much to help you figure it out what's going on.
Comment 4 Dan 2009-10-25 17:58:22 UTC 
I decided to reopen this because I still have this annoying problem. I'm using the latest KDE SVN, Lastest Phonon  SVN, latest xine( 1.1.16.3 ), latest Amarok and last.fm always get stuck when track changes...

How can I debug this? I want very much to help you figure it out what's going on.
Comment 5 Mark Kretschmann 2009-10-25 18:33:52 UTC 
*** Bug 211801 has been marked as a duplicate of this bug. ***
Comment 6 Mark Kretschmann 2009-10-25 18:35:31 UTC 

*** This bug has been marked as a duplicate of bug 201233 ***
Comment 7 Dan 2009-10-25 18:39:13 UTC 
Ok, so what is the "correct" bug? This is marked as RESOLVED. How can we just reopen it and mark UNRESOLVED?
Comment 8 Myriam Schweingruber 2009-10-26 00:14:54 UTC 
(In reply to comment #7)
> Ok, so what is the "correct" bug? This is marked as RESOLVED. How can we just
> reopen it and mark UNRESOLVED?

You don't since it is marked as a duplicate. Please use bug 201333 for anything new about it.