| Summary: | daap connection suddenly lost | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Thorsten Hirsch <t.hirsch> |
| Component: | Collections/DAAP | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | caco3, ian.monroe, skywalker_99, vdboor |
| Priority: | NOR | ||
| Version: | 2.4.1 | ||
| Target Milestone: | --- | ||
| Platform: | Debian stable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
debug output when amarok loses daap connection
debug output now with amarok 2.2 |
||
Created attachment 36195 [details]
debug output when amarok loses daap connection
I know nothing about DAAP. Myriam: Playlist:: Means the The Playlist, something I hardly have any knowledge about. CC'ing me is probably not going to help fix this faster. Ian knows about DAAP though. Or at least he can CC the one that ported it to A2. Is there anything I can do to help you get this problem fixed? It's always reproducable here and very annoying. Maybe it's enough if you stabilize the connection to the daap server, i.e. include some retries or so...? The bug is still present in Amarok 2.2. Created attachment 37312 [details]
debug output now with amarok 2.2
Here only 1 song could be played (Nouvelle Vague - Killing Moon). All the other songs were skipped, because of the bug.
Ian, any news on this? Please also see comment #2 Forgot to set to daap Can somebody reproduce this with Amarok 2.2.1, Amarok 2.2.2 beta or current git? I can still reproduce this with Amarok 2.2.1. Thank you for the feedback, Thorsten. Can somebody else confirm this? *** Bug 220610 has been marked as a duplicate of this bug. *** confirmed by duplicate > [Playlist::Actions] [WARNING!] engineNewTrackPlaying: "<song name>" does not
match what the playlist controller thought it should be
Fascinating. In my playlist I also see tracks grouped with the wrong album. If the artist/album fields are empty, they are sometimes taken from the previous track.
That's interesting. I also have some kind of side effect. Besides the daap collection that causes the issue, I also have a local music collection. Playing songs from my local collection works completely fine. And playing songs from the daap collection causes the issue we are talking about. So far, so good. Now the side effect is: when playing songs from both collections (mixed randomly), the issue also occurs and I even can't play songs from my local collection anymore. Thorsten Updated to Amarok 2.2.2, but problem remains the same. The current problem is that nobody is working on DAAP in Amarok, so if somebody knows a coder wanting to work on that... Is this still valid with Amarok 2.3.1, to be released next week? Yes, problem still exists in 2.3.1. Thorsten Thank you for the feedback. Still valid in 2.4.0 on Ubuntu Natty and also in 2.4.1 on Gentoo. Daap playing stops after each track, but amarok displays the name of the next one via knotify. Hitting Play again forces amarok to go on with playing Thank you for the feedback. I can confirm this bug in version 2.4.1 on KDE 4.6.2. Is there any way to fix this? This makes DAAP almost useless for me :( My synology disk station would also support UPnP, which works fine with the media player on my mobile phone, how ever Amarok seems not be able to see it :( Any solution to that? (UPnP Inspector and other tools can see my uPnP server). Git commit bd0b738fc0ed623c95e8657061a5ddcfa6998aaf by Bart Cerneels. Committed on 01/07/2011 at 08:36. Pushed by shanachie into branch 'master'. DAAP: use protocol introspection responce types. Previously was using hardcoded values. Patch by Lukas Sandström. CCBUG:204043 REVIEW:101798 M +55 -122 src/core-impl/collections/daap/daapreader/Reader.cpp M +5 -4 src/core-impl/collections/daap/daapreader/Reader.h http://commits.kde.org/amarok/bd0b738fc0ed623c95e8657061a5ddcfa6998aaf Is this still valid with Amarok 2.6? Closing for lack of feedback. Please all, consider using UPnP instead of DAAP, Amarok works fine with it since there is a KIO slave for UPnP. |
Version: 2.1.1 (using KDE 4.3.0) OS: Linux Installed from: Debian stable Packages After playing 3 to 7 songs of a daap share, amarok says: [Playlist::Actions] [WARNING!] engineNewTrackPlaying: "<song name>" does not match what the playlist controller thought it should be ...and doesn't play any more songs from that share. Neither the amarok client's computer nor the daap share server computer have any lost connection entries in their dmesg output. And since the problem is reproducable and hasn't occured in rhythmbox at all, I think it's amarok's fault. The debug output starts with the 1st song of Talking Head's "Once in a Lifetime", i.e. "Psycho Killer". This one and the next 2 songs ("Take me to the River" and "Once in a Lifetime") have been played (the full song). But the 4th song ("Burning Down the House") didn't even start. The server's host name is "tuxi". There's no domain name (`hostname --fqdn` is also "tuxi", `hostname -d` is empty), so I don't know where "tuxi.local" is coming from. Pinging "tuxi.local" doesn't work on the amarok client computer. However, I don't think that this is causing the bug, because amarok was aware of tuxi's correct hostname for 3 songs, why should amarok forget it and use the wrong "tuxi.local" instead? By the way, the amarok share is still in the collection. But amarok can't play any songs anymore. They all lead to "<name> does not match what the playlist controller thought it should be". After restarting amarok (and waiting some minutes until amarok has found the dapp share), everything's working fine ...for 3, 4 or 5 songs again. I'll attach the debug output.