stable

banshee-2.6.2-25.fc25, dbus-sharp-0.8.1-3.fc25, & 3 more

FEDORA-2017-8ccc53509f created by spot 7 years ago for Fedora 25

Bring fixes from later banshee builds to Fedora 25. Fix issue where banshee could not process podcasts with Windows encoded XML.

How to install

Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:

sudo dnf upgrade --refresh --advisory=FEDORA-2017-8ccc53509f

This update has been submitted for testing by spot.

7 years ago

This update has been pushed to testing.

7 years ago
User Icon davidcostanzo commented & provided feedback 7 years ago
karma

I followed the instructions to enable testing packages and confirmed that, after doing so, Banshee was able to download episodes from the podcast cited in https://bugzilla.redhat.com/show_bug.cgi?id=1409665 and I was able to listen to two episodes (that's all I tried). The console printed:

[Warn  11:17:59.643] DosLineBreaks detected in xml
[Warn  11:17:59.646] UTF-8 BOM detected in xml

As the episode list was downloaded. Presumably, this means that there were two odd things about the RSS and Banshee has corrected both of them.

Unfortunately, when I tried other Podcasts from the same site (Cadena Ser: http://cadenaser.com/ser/podcasts/) they did not work. However, I believe these are failing for unrelated reasons and I plan to open a separate bug once I have done more investigation. Note that none of these worked before the fix, so this is not a regression.

Banshee continues to be "generally functional". I was able to do all of the things that I typically do: listen to MP3s from my machine, listen to some Internet radio sites, get updates for podcasts and listen to them.

Thanks for the fix!

BZ#1409665 Banshee cannot process podcasts whose XML has Windows end-of-line sequences

This update has reached 7 days in testing and can be pushed to stable now if the maintainer wishes

7 years ago

This update has been submitted for stable by spot.

7 years ago
User Icon davidcostanzo commented & provided feedback 7 years ago

I've noticed a few times in the past week that when I try to quit Banshee (Media -> Quit, not click the close button), the application becomes unresponsive and I have to "force quit" the application. That never happened before I started testing this change, but it could be due to some unrelated change to the system. I haven't been able to pin down any repro steps--it only happens after I've been using Banshee for a long time (mostly listening to podcasts and Internet radio).

I don't know how to gather any useful information, such as stack traces of running threads.

This update has been pushed to stable.

7 years ago

Please login to add feedback.

Metadata
Type
bugfix
Karma
1
Signed
Content Type
RPM
Test Gating
Autopush Settings
Unstable by Karma
-3
Stable by Karma
3
Stable by Time
disabled
Dates
submitted
7 years ago
in testing
7 years ago
in stable
7 years ago
BZ#1409665 Banshee cannot process podcasts whose XML has Windows end-of-line sequences
0
0

Automated Test Results