After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 736545 - Totem presents videos that can't be played
Totem presents videos that can't be played
Status: RESOLVED OBSOLETE
Product: totem
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-09-12 08:51 UTC by Allan Day
Modified: 2018-05-24 10:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Allan Day 2014-09-12 08:51:58 UTC
Testing the out of the box experience with Fedora 21 alpha last night, I opened the "Channels" section in Videos and tried to play a video. The video failed to play of course, because Fedora didn't have the necessary codecs (MPEG-4, H.264).

It's quite a poor initial experience to present content that cannot be played (compounded by the very poor way that PackageKit presents it - obviously not Totem's fault, but still makes it worse).
Comment 1 Bastien Nocera 2014-09-12 09:57:40 UTC
1. We cannot be certain whether we're going to be able to play videos, even if we did filter them out. In this case, we don't even know that it's H264 inside, so we couldn't filter it out anyway.

2. Catch 22, how do you trigger codecs installation if you can't open the files?

Let me know if you have specific requests for Totem in terms of UI for the missing plugins, but hiding the non-playable videos isn't feasible.
Comment 2 Allan Day 2014-09-12 10:19:41 UTC
Whatever the specifics of this bug, I hope we can agree that an out of the box experience where you are shown a bunch of content that produces errors when selected isn't acceptable.

(In reply to comment #1)
> 1. We cannot be certain whether we're going to be able to play videos, even if
> we did filter them out. In this case, we don't even know that it's H264 inside,
> so we couldn't filter it out anyway.

We which codecs each of these channels requires though, right? 

> 2. Catch 22, how do you trigger codecs installation if you can't open the
> files?

It would be easy to design some UI for installing codecs, which would then result in channels being displayed. But again, that requires knowing which channels are available and which codecs they require.
Comment 3 Allan Day 2016-03-07 19:22:40 UTC
(In reply to Allan Day from comment #2)
...
> We which codecs each of these channels requires though, right? 

Should have been: "We know which codecs each of these channels requires though, right?"
Comment 4 GNOME Infrastructure Team 2018-05-24 10:58:18 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/totem/issues/120.