GNOME Bugzilla – Bug 325752
[0.10] doesn't play file copied from a DVD
Last modified: 2006-09-03 09:44:49 UTC
This bug has been described here: http://bugzilla.ubuntu.com/show_bug.cgi?id=21862 "I made an ISO of a DVD, so I can play the movie from the hard disk, but Totem can't open it anymore (used to work). It gives an error : "Can't play file blah-blah, location not found "." That's probably because gstreamer0.10 has no dvd element for the moment but the message is confusing, it should mention that
Odd that it says 'location not found'. What does % gst-typefind-0.10 /path/to/file show?
From distro bug: " Hi, Just installed a fresh Flight 4, and the problem is still there. The result of the command above is just : "No type found". $ gst-typefind-0.10 /media/Breezy_Home/vincent/lotus/Lotus_DVD.iso /media/Breezy_Home/vincent/lotus/Lotus_DVD.iso - No type found ... > Is the totem message saying "location not found" or "no type found"? Those are differents messages in fact ... Totem says "Location not found". "no type found" is the result of that gst command upstream asked about. It doesn't seem clear, so I made a screenshot that recapitulates the problem... http://librarian.launchpad.net/1577547/Screenshot-1.png Totem error message along with gst error in the terminal."
Can't reproduce this with up-to-date totem (1.5.92) and gst-plugins-ugly (0.10.4). With dvdreadsrc installed, opening a DVD iso file works just fine (totem will pass a dvd:///path/to/foo.iso URI), without dvdreadsrc installed it will throw an error telling you about the missing dvd handler. gst-typefind-0.10 doesn't recognise the ISO file, but that's actually not a problem, since totem does and prefixes the dvd:// bit, so only dvdreadsrc needs to be able to handle this right. If this is still a problem with current totem/gst-plugins-ugly, could you run totem like this: $ GST_DEBUG=totem:5,dvdreadsrc:5 totem dvd:///path/to/file.iso 2>dbg.log ... wait for error ... press control+C $ gzip dbg.log and attach the dbg.log.gz file?
from the bug submitter: "Yep, no problem anymore, you can close the bug :-)", closing the bug as fixed then