Description of problem: I recently got an Ipod Classic and have been using Banshee to manage it. Everything WAS working perfectly. I suddenly realized it wasn't updating correctly though because I had changed some file paths and such so I ran "Rescan Music Library." During the last step (I believe it was importing) the step just kind of froze. It said it was importing for about fifteen minutes and got no where so I just closed banshee and restarted it. The library paths didn't update so I just removed all the music from the library, and then added it back. I'm not sure if this is what caused the problem, but this is when stuff started to go wrong. Now when I sync my Ipod or manage it myself (whatever I choose), sometimes it makes the changes and then syncs, but then sometimes it chooses not to sync after making changes. I can fix that if I reboot. Furthermore, now all the cover art is messed up on my Ipod. Banshee randomly chooses 2-3 album covers to set as all the album covers, every time I manage to sync it, but they are never the same. Each time I sync I can expect 2-3 new album covers for all my albums. However, the album cover from Death Magnetic seams to be very popular, and that one gets chosen a lot. I swear I am not joking about this, or making it up. I don't know if this helps at all but the death magnetic album gets converted by banshee each time I sync. The last issue is that sometimes when downloading cover art it says its downloading it for about fifteen minutes, and then just freezes at the bottom at like 60%. The album art appears after about one second though, but I still get stuck with the frozen progress bar. Simply restarting Banshee gets that to go away. Version-Release number of selected component (if applicable): banshee-1.4.2-3.fc10.i386 kernel 2.6.27.15-170.2.24.fc10.i686 How reproducible: All errors are periodic except for the cover art. The cover art is still weird on my Ipod, and I have tried to fix it like five times. I have 11Gb of music so it takes a while to try again. Steps to Reproduce: 1. Sync Ipod and unplug. Then sync and unplug again. 2. Try running "rescan music library" 3. Use Banshee. At some point it starts bugging out. Actual results: Banshee runs normally then over time it goes crazy. Expected results: It shouldn't do anything I said above. Additional info: What is going on?!? Please help.
I forgot to mention this but album art is ok on my computer. Just not on the Ipod.
Thank you for taking the time to report this problem. Can you please run banshee-1 --debug and attach the output. Also if you can find a place to upload a copy of ~/.config/banshee-1/banshee.db so that it might be available for further examination. The album art is unfortunately a bit problematic for all iPods, mine included. This however is a separate issue and should be filed as one. Also the next time, can I ask you to please break the text up in paragraphs to make it easier to read as well as giving your reports a more descriptive name. This makes our work a lot easier and increases the chances that we will be able to help you.
I have encountered an album art problem in the past, whensyncing to an Android phone, so it's definitely not iPod-only. Does the issue recur if you 1) move ~/.gconf/apps/banshee-1 out of the way, killall gconfd-2 and start banshee (to restore, replace the new ~/.gconf/apps/banshee-1 with the one you saved earlier and killall gconfd-2 again) 2) if that still does not work, if you move ~/.config/banshee out of the way and repopulate the music library from scratch That, plus the debug output, would allow us to provide more information to the upstream developers. Thanks.
I ran rm -r ~/.config, and then reloaded my library. Resynchronising my Ipod afterwards fixed the album art issue. Removing that config folder in general fixes any issues I am having with banshee, but then I have to wait an hour or so for my library to reload. If you're wondering why I removed the entire .config folder and not just .config/banshee-1 it's because banshee likes to mess up everything in that folder apparently. That's another bug I plan on filing. However, the last time I needed to remove that folder I saved it as config_backup. I will attach the entire .config folder to see if that helps out. I have also attached the output from banshee-1 --debug as banshee_debug.txt. This was ran after I removed that .config folder though. I will file the album art issue as a seperate bug.
Created attachment 333798 [details] Output from banshee-1 --dubug
Created attachment 333799 [details] Contents of .config
Upstream recommends checking this list of rescan bugs: http://bugzilla.gnome.org/buglist.cgi?query=product%3Abanshee+summary%3Arescan It looks like the first is particularly relevant: some files are deleted (in your case, moved) and these are not removed from the Banshee DB when it is rescanned. If you go back to the old database, and look on the left pane for the ones marked as missing, select them all and remove, would Banshee now sync properly? In which case, there is a decent workaround. The reason these files are not automatically removed is probably due to removable storage support -- you don't want to have to rescan files you have seen before that are just temporarily missing.
Could you clear up where exactly you would like me to remove information? I was assuming it was from .config/banshee-1/banshee.db, but that file can't be read because it's in sqlite format, which I do not know how to open.
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.