After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 581122 - Elements are not removed immediately on the iPod when removing them from the library (when using AutoSync)
Elements are not removed immediately on the iPod when removing them from the ...
Status: RESOLVED FIXED
Product: banshee
Classification: Other
Component: Device - iPod
git master
Other All
: Normal normal
: 1.5.0
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-05-02 18:42 UTC by Andrés G. Aragoneses (IRC: knocte)
Modified: 2009-05-14 17:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Proposed patch (541 bytes, patch)
2009-05-02 18:44 UTC, Andrés G. Aragoneses (IRC: knocte)
committed Details | Review

Description Andrés G. Aragoneses (IRC: knocte) 2009-05-02 18:42:35 UTC
Please describe the problem:
Elements are not removed immediately on the iPod after they happen on the library (when using AutoSync).

Steps to reproduce:
1. Have an empty library.
2. Import 2 songs (they get included automatically in 2 smart playlists as well: Recently Added, and Unheard).
3. Connect your iPod configured as AutoSync (the songs and playlists get transferred into the iPod).
4. Remove the 2 songs from your library.


Actual results:
The 2 playlists are removed from the iPod, but the songs remain there.

Expected results:
All music contents of the iPod should be removed.

Does this happen every time?
Yes.

Other information:
I'll provide a patch.
Comment 1 Andrés G. Aragoneses (IRC: knocte) 2009-05-02 18:44:55 UTC
Created attachment 133816 [details] [review]
Proposed patch

This fixes the problem.
Comment 2 Gabriel Burt 2009-05-14 16:58:52 UTC
Thanks Andres, committed to master and stable branches.
Comment 3 Andrés G. Aragoneses (IRC: knocte) 2009-05-14 17:45:35 UTC
Thanks Gabriel.

This problem has been fixed in the development version. The fix will be
available in the next major software release. Thank you for your bug report.