An album I added to my collection included one m3u8 file.
After updating, the file showed up in my Local Collection as a zero length mp3 file, instead of Saved Playlists.
Other types of playlists, including m3u files, appear in Saved Playlists as expected.
I tried renaming m3u files to m3u8 and back, and found the behaviour to be consistent.

Before filing a bug report I wanted to know if this has been encountered by others, or if I'm missing something.
I'm running Amarok 2.8.0 on Fedora19.
Thank you for your comments.

Strange, that file should not show in the collection, only in the saved playlist listing. Did you try running a rescan?

If you mean a Full rescan, no I haven't tried it.
I only did Update Collection, to no effect.

If I do a Full rescan, will I lose any data only present in the db, like cover associations?

no, of course not, it will only update the complete collection, while the update only does an incremental one that only checks for recent changes.

I did a Full rescan to no effect.
Any m3u8 files still show up in Local collection.
Identical files called *.m3u go to Saved Playlists instead.

Weird, as the only difference between .m3u and .m3u8 is the UTF-8 encoding...

If you run the command "file --mime-type /path/to/file" against a m3u and a m3u8 file, what is the output you get?
Also, is the m3u8 file UTF-8 formatted?

both mime types are text/plain.

about the m3u8, file says:
M3U playlist, UTF-8 Unicode (with BOM) text, with CRLF line terminators

Okay, my guess would be the Collection Scanner relies on extensions then - in which case m3u8 needs to be added to it's list of playlist extensions.

bcooksley wrote:Okay, my guess would be the Collection Scanner relies on extensions then - in which case m3u8 needs to be added to it's list of playlist extensions.

Please file a feature request in https://bugs.kde.org/enter_bug.cgi?product=amarok against the Collection/Local component.

Has anyone actually replicated the bug?
I really wanted to know whether this is a weird local config issue of mine or a plain Amarok bug.

You best file a bug report, there are certainly more testers there.