Description of problem: When running banshee-1, if I choose to import media, it immediately crashes with a traceback. Version-Release number of selected component (if applicable): banshee-0.99.1-2.fc9.x86_64 How reproducible: Every time. Even with a clean config (essentially find -iname '*banshee*' -exec rm {} \;) Steps to Reproduce: 1. Start banshee 2. File->Import Media (or Ctrl-I) Actual results: Crashes Expected results: To open the Import Media dialogue Additional info: I've attached a tar of all the banshee-related config I have, but it also behaves the same if I remove those files. Also, a capture of the traceback.
Created attachment 306918 [details] Banshee traceback
Created attachment 306919 [details] Tar of banshee-related config
I can't reproduce w/ 0.99.2, so would you mind updating to Banshee 0.99.2 (yum --enablerepo=updates-testing update banshee) if it insists there is nothing to update you should be able to just do "rpm -Uhv http://koji.fedoraproject.org/packages/banshee/0.99.2/1.fc9/x86_64/banshee-0.99.2-1.fc9.x86_64.rpm" Please let me know if you can reproduce this bug with 0.99.2. Thanks
Created attachment 306925 [details] Banshee traceback for version 0.99.2
I can indeed. Please see the new banshee.log traceback. I don't know if it's relevant, but I'm running xfce4 as my desktop environment.
(In reply to comment #5) > I can indeed. Hmm thats strange. > > Please see the new banshee.log traceback. > > I don't know if it's relevant, but I'm running xfce4 as my desktop environment. It *may* be a dependency issue, I'll give it a shot later. In the mean time, could you try to import by right clicking on the music library?
That behaves the same way. I ran strace on it, and attach it here. Is there anything else I can do to gather more useful data?
Created attachment 307174 [details] strace -f -F banshee-1 (and then right-click->Import Media)
OK, this is weird. I did a couple of updates, one this morning, and I figured I'd try running banshee "just to see". It imports with no traceback! I'm still running banshee-0.99.2-1.fc9.x86_64. I guess this can be closed?
(In reply to comment #9) > OK, this is weird. > > I did a couple of updates, one this morning, and I figured I'd try running > banshee "just to see". > > It imports with no traceback! Great to hear! > > I'm still running banshee-0.99.2-1.fc9.x86_64. > > I guess this can be closed? I'd like to see if I can reproduce this (it honestly sounds like broken dependencies somewhere), sadly I've had a bit of trouble with RAM and QEMU the last couple of days, assuming that everything is fine, I'll close it.
(In reply to comment #10) > (In reply to comment #9) > > OK, this is weird. > > > > I did a couple of updates, one this morning, and I figured I'd try running > > banshee "just to see". > > > > It imports with no traceback! > Great to hear! > > > > I'm still running banshee-0.99.2-1.fc9.x86_64. > > > > I guess this can be closed? > I'd like to see if I can reproduce this (it honestly sounds like broken > dependencies somewhere), sadly I've had a bit of trouble with RAM and QEMU the > last couple of days, assuming that everything is fine, I'll close it. A clean Fedora 9 installation with Banshee 0.99.1 (original version reported) and XFCE (installed during installation) worked fine. I can't think of *any* logical explanation on WHY it acted like that and I really wish I did so I could provide a fix/feedback on what to do to get it to work. None the less, thank you for reporting the bug & if you can reproduce this sometime in the near future, I'd love to hear (just reopen the bug) especially if you can let me know what you did to make it happen again.