GNOME Bugzilla – Bug 653134
Banshee looses DAAP shares after closing.
Last modified: 2020-03-17 09:18:14 UTC
If I add a daap share in Banshee and close the software, the daap share is not available upon next start of Banshee. I have to re-add the daap share after starting the software the next time. This problem occurs on x86 and AMD64 as well as 2.0.x and 2.1.x versions of Banshee. My daap server is based on mt-daapd, which works flawlessly using clients like Songbird.
The problem stays the same on 2.2.0. After closing, the once added share is gone, I have to re-add it at next start.
Same happens with 2.2.1 I assume it's not a bug but a feature, but would be nice banshee to keep the added daap servers and not only those detected through avahi
If I close (making sure banshee stops by making sure it is not playing music when I hit the close window button on the GUI) and then restart it resumes autodetecting the music share once again.
Banshee is not under active development anymore and had its last code changes more than three years ago. Its codebase has been archived. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is being shut down) if anyone takes the responsibility for active development again. See https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/264 for more info.