gst0.10 doesn't play DVD/message confusing for it

Thanks for your bug. The dvd element has not been ported to gstreamer0.10 yet,
which is probably the reason why it doesn't read the file. I've opened a totem
bug upstream though because the dialog should say that instead of using the
current message: http://bugzilla.gnome.org/show_bug.cgi?id=325752

Upstream comment:

"Odd that it says 'location not found'. What does

  % gst-typefind-0.10 /path/to/file

show?"

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...

Totem error message along with gst error in the terminal.

Comment from upstream:

"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?"

Hello,

Yep, no problem anymore, you can close the bug :-)

Marking as fixed then!

Setting the bug to "in progress" it seems not reasonable, Brazilian, and you provided no explanation for the change. Therefore setting back to "fix released", since the original reporter does not get the bug anymore.