GNOME Bugzilla – Bug 677035
After syncing iPod, description-less phantom operation keeps animating progress bar and prevents closing Banshee
Last modified: 2012-05-29 19:06:21 UTC
Originally reported at: https://bugs.launchpad.net/bugs/864791 After updating to Banshee 2.2, syncing to iPod is successful, but leaves a phantom operation running with no description. The operation cannot be "stopped," but the iPod can be disconnected. Images are attached. == Dialog box when clicking red "X" button == Stop Operation This operation is still performing work. Would you like to stop it? == Dialog box when trying to close Banshee == Important tasks are running Closing Banshee now will cancel any currently running tasks. They cannot be resumed automatically the next time Banshee is run. == Terminal output at time of iPod sync == [7 Debug 14:13:54.355] Starting DAP sync [7 Debug 14:13:54.388] Preempting - Downloading Cover Art [7 Debug 14:13:54.389] Starting [7 Debug 14:13:54.391] Ending DAP sync [8 Debug 14:13:54.786] Starting AppleDevice sync thread cycle [8 Debug 14:13:54.786] Starting - Syncing iPod ** (Banshee:11299): CRITICAL **: itdb_splr_validate: assertion `at != ITDB_SPLAT_UNKNOWN' failed [8 Info 14:13:55.736] Wrote iPod database [8 Debug 14:13:55.737] Finished - Syncing iPod [8 Debug 14:13:55.738] Ending AppleDevice sync thread cycle == Steps to reproduce == 1. Click "Sync" button to sync to iPod (mine is a 4th generation Nano) 2. Two operation progress bars appear, one that says "Syncing iPod" and another with no description 3. After the sync succeeds, the "Syncing iPod" progress bar disappears, but the other one remains 4. Clicking the "Stop" button next to the remaining operation (and confirming in the subsequent dialog) does not remove the operation, but instead just adds the text "Stopping..." above it
Images and a video can be found at the Launchpad bug.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 657769 ***