| Summary: | Track list is full of "unknown" tracks after restart amarok and no way to browse ampache collection | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Łukasz Żarnowiecki <lukasz> |
| Component: | Services/Ampache | Assignee: | Amarok Bugs <amarok-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | eljefedelito, francoisvdven, yurupuqui+kde |
| Priority: | NOR | ||
| Version First Reported In: | 2.8.0 | ||
| Target Milestone: | 2.9 | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| URL: | http://i.imgur.com/ZinTg.png | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Ampache config file | ||
|
Description
Łukasz Żarnowiecki
2012-11-27 20:21:24 UTC
Amarok 2.5 is quite outdated now, please upgrade to Amarok 2.6 and try again. The same problem with amarok 2.6 Thank you for the feedback. I also had this with 2.6.0 on Debian Unstable. Removing the songs from the playlist, restarting Amarok, and re-browsing for files seems to have cleared it up the times I tried, but that's a good amount of effort which shouldn't be required IMHO. Thanks for looking into this. What with Amarok 2.7? (In reply to comment #5) > What with Amarok 2.7? Still waiting for feedback... (In reply to comment #6) > (In reply to comment #5) > > What with Amarok 2.7? > > Still waiting for feedback... Still in 2.7 Thank you for the feedback. Ampache collection works fine in Amarok v2.7.90-56-g69199bd Well in Amarok 2.8 bug still remain I can't reproduce this here at all. What exact Ampache version do you use? Is the Ampache server online when you start Amarok? >What exact Ampache version do you use? Ampache 3.5.4, I tried also git master, but is full of bugs. >Is the Ampache server online when you start Amarok? Absolutely Thank you for the feedback. Created attachment 85770 [details]
Ampache config file
Same situation here. After restarting Amarok, all that remains is a list full of empty tracks (no url, no tags).
Amarok is 2.8.0, having issues with two Ampache servers (3.5.4 and 3.6 alpha). My config file from one of them is attached to this comment. The access control list looks like this:
Name Start Address End Address Level User Type
DEFAULTv4 0.0.0.0 255.255.255.255 All All Web Interface
DEFAULTv4 0.0.0.0 255.255.255.255 All All Stream Access
DEFAULTv6 :: ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff All All Web Interface
DEFAULTv6 :: ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff All All Stream Access
DEFAULTv4 0.0.0.0 255.255.255.255 All All API/RPC
The issue is in AmpacheTrackForUrlWorker::run. We are trying to access the network manager from a separate thread, and kio gets unhappy. Not entirely sure the best way to adjust this. Will look into it further. Relevent debug output: amarok: BEGIN: virtual void AmpacheTrackForUrlWorker::run() amarok(28502)/kio (Scheduler) KIO::SchedulerPrivate::doJob: KIO is not thread-safe. QObject: Cannot create children for a parent that is in a different thread. (Parent is NetworkAccessManagerProxy(0x91ef0f8), parent's thread is QThread(0x8bc11a8), current thread is ThreadWeaver::Thread(0x92482e0) amarok: END__: virtual void AmpacheTrackForUrlWorker::run() [Took: 0s] Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Changing back to REPORTED per request of Myriam (Amarok dev). Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |
