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 615025 - Can't play .mkv with multiple tracks
Can't play .mkv with multiple tracks
Status: RESOLVED DUPLICATE of bug 591662
Product: GStreamer
Classification: Platform
Component: dont know
0.10.x
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-04-07 00:14 UTC by Ondra Pelech
Modified: 2010-04-07 09:46 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
stack trace of totem when opening the multitrack file (2.84 KB, application/octet-stream)
2010-04-07 00:14 UTC, Ondra Pelech 		Details

Description Ondra Pelech 2010-04-07 00:14:28 UTC 
Created attachment 158090 [details]
stack trace of totem when opening the multitrack file

totem can't play .mkv movies that have multiple audio or subtitle tracks.
for example files in this [0] torrent (except for the last one, which is ok, because it has only Japanese audio track and English subtitles track).

these files have one video, Japanese stereo and 6ch, English, French, German audio and English, French, German, Spanish, Dutch/Flemish subtitle tracks.

totem shows "An error occurred; Can't display both text subtitles and subpictures." error message.

I've attached a stack-trace, although I guess, that it won't be useful.

[0] http://thepiratebay.org/torrent/5033264/Hellsing_Ultimate_OVA_01-05_%5BDVDRip%28HQ%29_848x480%5D%5BAAC_jpn-eng-fre
Comment 1 Bastien Nocera 2010-04-07 00:25:14 UTC 
This is a dupe of a GStreamer bug, Sebastian would know which one.
Comment 2 Sebastian Dröge (slomo) 2010-04-07 09:46:19 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 591662 ***