Treats m3u as pls and attempts to convert it to m3u

Bug #1992354 reported by Boris Gjenero
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
streamtuner2 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Trying to play https://lounge-radio.com/ via https://lounge-radio.com/listen128.m3u or http://nl1.streamhosting.ch:80/lounge128.mp3.m3u using Audacious fails. The problem is that, although the playlist is in m3u format, Streamtuner2 treats it as pls and tries to convert it to m3u. The resulting m3u is empty, only containing the #EXTM3U header. Debug output shown when running streamtuner2 -D shows what's going on:

---
[PROC] convert_playlist( http://nl1.streamhosting.ch:80/lounge128.mp3.m3u pls m3u )
[WARN] Possible playlist format mismatch: listformat=pls, http_mime=m3u, rx_probe=href, ext=m3u
[DATA] input extractor/regex: pls 44
[DATA] conversion from: pls with extractor: pls got URLs= <filter object at 0x7f0cec426da0>
[DATA] exporting with format: m3u into filename: /tmp/streamtuner2/bookmarks.7047123869479088044.m3u
[DATA] conversion to: m3u with rows= []
[EXEC] audacious /tmp/streamtuner2/bookmarks.7047123869479088044.m3u &
---

Both playlist URLs are served with "Content-Type: audio/x-mpegurl", which seems correct, the URL has the .m3u extension. I see no reason why Streamtuner2 should treat this as a pls.

As a workaround, go to Edit -> Properties -> Options (tab) -> Playlist conversion (section), and enable "Forgo any streaming URL and playlist format and playlist conversion for players".

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: streamtuner2 2.2.2+dfsg-2
ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
Uname: Linux 5.19.0-19-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.23.1-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Mon Oct 10 10:39:14 2022
PackageArchitecture: all
SourcePackage: streamtuner2
UpgradeStatus: Upgraded to kinetic on 2022-10-08 (1 days ago)

Revision history for this message
Boris Gjenero (boris-gjenero) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.