Bug 508887 - Premium (patreon) and Standard feeds of the same podcast result in playback errors
Summary: Premium (patreon) and Standard feeds of the same podcast result in playback e...
Status: CONFIRMED
Alias: None
Product: kasts
Classification: Applications
Component: general (other bugs)
Version First Reported In: 25.08.0
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: bart
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-08-29 03:13 UTC by Frederick Schaefer
Modified: 2025-11-16 13:36 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
picture of errors present on feed refresh and playback (339.01 KB, image/png)
2025-08-29 03:13 UTC, Frederick Schaefer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Frederick Schaefer 2025-08-29 03:13:23 UTC
Created attachment 184546 [details]
picture of errors present on feed refresh and playback

SUMMARY
Subscribing to a second (premium patreon) feed of the same podcast results in "invalid media file" during playback attempts and database errors (unique constraint failed) when refreshing the feed. 

STEPS TO REPRODUCE
1. Subscribe to podcast through search (e.g. This machine kills or QAA)
2. Subscribe to a second/premium feed of the same podcast (e.g. via patreon).
3. Attempt playback from the second feed.

OBSERVED RESULT


EXPECTED RESULT
Playback fails with mysterious "Invalid media file, Error code: 8"
Refreshing feeds generates many "Database error, UNIQUE constraint failed: Entries.id Unable to fetch row"

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Garuda Linux
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.1

ADDITIONAL INFORMATION
n/a
Comment 1 bart 2025-11-16 13:36:16 UTC
This is very likely due to the fact that the rss/atom file contents are exactly the same for the (non-identical) versions of the podcast.
Currently kasts cannot handle those situations.  I'm working on a rewrite of the backend that would be able to deal with these kinds of unexpected duplicates.  This could take a while, though.