Red Hat Bugzilla – Bug 327681
Firefox should pass URL to Rhythmbox when playing .m3u not /tmp file location
Last modified: 2018-04-11 06:02:53 EDT
In f8t3, clicking on an m3u (e.g.,
http://audio-ogg.ibiblio.org:8000/wcpe.ogg.m3u ) appears to finally have the
right file association- rhythmbox is offered as the default choice, and when you
tell firefox to open, rhythmbox opens up. So far so good.
After that, it is all downhill. It does not open playing the m3u I've just
clicked on, and it appears to actually have deleted all the default radio
stations as well. I assume these two issues are somehow related, so I haven't
opened a separate bug, but they may be two separate problems.
Marking as high because of the data destruction- deleting all the default radio
I don't see how the data loss could have occurred. Could you file another bug
with exact reproducer steps, and the command launching rhythmbox (/proc/<pid of
As for the problem you're seeing, it's the same problem as with the calendar for
evolution. Your browser downloads it to the disk, and rhythmbox treats local
playlists differently that it does remote ones. Local playlists are considered
to be additional playlists (so it should create an empty playlist with files in
them), remote playlists will go to the iradio.
Which browser are you using, still ephy? Could you double-check the command-line
as above (I'm certain it would have pushed a local file, instead of the remote URL)?
Weird. I can't duplicate the radio-list clearing effect now.
You're right, it is opening a file out of /tmp/ instead of the URL. Irrrritating.
ffox, not ephy, sorry, forgot to clear that up.
Moving to firefox then.
At this point, we're going to only be taking security fixes and major stability
fixes into this release of Fedora. However, we still want to ensure the bug is
fixed in the next version. We'd appreciate if you could test Firefox 3,
available at http://www.mozilla.com/en-US/firefox/all-beta.html or now shipping
as the default in Fedora rawhide and provide feedback as to whether it still
exists so we can file a ticket upstream to try to fix it in Firefox 3 before it
Still happens in F9 A1 w/ ffxb3.
We found that this bug has been already registered in the upstream database
(https://bugzilla.mozilla.org/show_bug.cgi?id=225882) and believe that it is
more appropriate to let it be resolved upstream.
Red Hat will continue to track the issue in the centralized upstream bug
tracker, and will review any bug fixes that become available for consideration
in future updates.
Thank you for the bug report.
https://bugzilla.mozilla.org/show_bug.cgi?id=137339 is the Unix/Linux version of