| Summary: | transfer to any media player (even an empty directory) fails | ||
|---|---|---|---|
| Product: | [Unmaintained] kio | Reporter: | Harri <harald.dunkel> |
| Component: | general | Assignee: | Amarok Bugs <amarok-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | adawit |
| Priority: | NOR | Keywords: | triaged |
| Version First Reported In: | 3.5 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Harri
2007-08-29 12:19:30 UTC
PS: Platform is AMD64 Just tried it with 95 tracks, mixed flac/mp3. All transferred successfully (there was one failure, which was because the artist/album/title were all exactly the same -- the filename on the generic device is by default built from these three track properties). Looks from your paths like you're copying from NFS...perhaps there's some NFS issues going on. But if so there's little we can do...we use KIO in the generic media device, so if there is a NFS problem it is probably deeper in KDE. Make sure you're not trying to copy the same track twice (as represented by the trio of album/artist/title -- or if so adjust the Song Location field to compensate). You can be sure that I don't try to copy the same track twice. But even if I would, there shouldn't be a problem if I use "synchronize". My directories are all local. NFS is not involved. Can't reproduce either. Maybe it's a permission issue. PS: Did you note that the list of files Amarok complains about is not constant? Come on. Setting this bug to "WORKSFORME" is not a solution. I would be glad to help to track this down, but we need some constructive communication here. Dude, we don't mark it as worksforme because we have the mark-everything-as-worksforme addiction. The bug report isn't reproducable as it is, so go and aggregate more information. Compile Amarok with --enable-debug and watch STDOUT, ask in the forum or on IRC for help with interpreting the output and considering it actually is a bug we can reproduce in any way, reopen the report and describe what we have to do. Don't open it until you got _any_ information which either helps reproducing or fixing. What's "synchronize"? When you give detailed reproduction steps, we follow them, and can't reproduce it, it usually means a problem on your end, not ours. "WORKSFORME" is the perfect status for the bug at that point. Anyways, like I said, the generic device just uses KIO. If we get an error from the KIO job, it's outputted to the console. So watch the console output when it's transferring...the error text will have the format "file transfer failed: <errortext>" "Synchronize to Media Device" can be found in the right-button menu on a playlist. I had hoped it adds and removes audio files on the player according to the changes applied to the playlist since the last sync. Does it? About the KIO errors: There are tons of them, but AFAICS the error messages in question just say "kio (KIOConnection): ERROR: Could not write data". Here is some more output: : : kio (KLauncher): ERROR: SlavePool: No communication with slave. kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kio (KLauncher): ERROR: SlavePool: No communication with slave. kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kio (KIOConnection): ERROR: Could not write data kio (KLauncher): ERROR: SlavePool: No communication with slave. kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kio (KLauncher): ERROR: SlavePool: No communication with slave. kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kio (KLauncher): ERROR: SlavePool: No communication with slave. kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kio (KIOConnection): ERROR: Could not write data kio (KLauncher): ERROR: SlavePool: No communication with slave. kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kio (KLauncher): ERROR: SlavePool: No communication with slave. kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kio (KLauncher): ERROR: SlavePool: No communication with slave. : : Regards Harri "Synchronize to media device" doesn't remove, only adds, as far as I know. Perhaps on an iPod it does synchronization. I'm going to reassign this to kio. We're using standard KIO to do the transferring, so if you're getting those errors they'll be able to help you figure it out a lot better than I can (that's the error text that's given to us). Is this still an issue in the latest stable version of KDE 4? 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 set the bug status 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! Dear Bug Submitter, 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! |