https://bugs.kde.org/show_bug.cgi?id=517427
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|REPORTED |ASSIGNED --- Comment #2 from [email protected] --- Thanks for the bug report. It seems there are actually two issues here, which are only semi-related. First of all, the two different links for the audio file are because Kasts first tries to resolve all potential redirects before handing the actual link to VLC (or any other media backend). So the longer link should be the actual link to the mp3 file, while the shorter link is just a redirect link. I've added that resolution because VLC can only handle a handful of redirects before giving up. But there are a lot of podcasts where you have to follow 5 or more redirects before you get to the actual URL of the mp3. So, now you have shown a counterexample of this... I'm not sure what to do here. If I remove the code for resolving the redirect, then other podcasts will break. Maybe I need to try both links in succession. Anyway, downloading the file seems to work just fine. So you can always download the mp3 instead of streaming it until this is solved (like it was originally intended for podcasts :-p) Then the crash itself. That's actual not directly caused by the invalid link. But it's triggered by it. I've rewritten about half of the backend code for the upcoming 26.04 release, but that seems to have introduced a problem in the AudioManager code. The code wants to skip to the next track, but not without first deleting the invalid mp3 file if it was downloaded (which is not really relevant to your case here). It needs a pointer to the enclosure (i.e. mp3 file), but in the new code, the object that the pointer is pointing to has already been deleted, hence the segmentation fault and crash. The fix itself is trivial. I will push it to the git repo in a few minutes. You'll probably see the auto-triggered message in this report once it's been merged into master. Note that this fix is only for the crash, not yet for the invalid media/URL error. -- You are receiving this mail because: You are watching all bug changes.
