Red Hat Bugzilla – Bug 243633
%d parameter for totem doesn't work
Last modified: 2008-08-02 19:40:35 EDT
Description of problem:
When inserting a dvd, totem is launched automatically but the dvd isn't played.
By using the "File" menu, then "Open location" and giving dvd:///dev/scd0 as
parameter, the dvd plays well.
Nevertheless, using the link "Play *movie name*" in the Movie menu of totem
doesn't work either. Maybe this a totem related bug, or volume mount related bug ?
Version-Release number of selected component (if applicable):
The freshrpms repo has been installed in order to install codec & dvd libraries.
The volume manager automatic launch is set as : "totem %d" for dvd medias.
- Insert a dvd
- Use "Play *movie name*" entry under the Movie menu of totem.
Totem displays an error about missing plugins.
Totem plays the movie.
Is the DVD mounted before you start playing?
Could you please send the output of lshal before and after you inserted the DVD?
Are you using the GStreamer or xine-lib backend of Totem (see about box)?
When I insert the dvd, the automount works well, it appears in the result of
Totem is launched at same time but doesn't play the dvd. When I click on the
"Movie" menu, I see the "Play the *dvd name*" in the list but totem isn't able
to read it. Using the "Open URL" menu (CTRL+L shortcut) , if I give
dvd:///dev/scd0 as parameter, it works well.
The backend is the Gstreamer one, version 0.10.12.
I attached the lshal outputs.
Created attachment 156787 [details]
lshal output before insertion of dvd
Created attachment 156788 [details]
lshal output after insertion of dvd
I have a 4MB video capture of the screen, showing the error of Totem, if needed,
just ask for it.
The video would be appreciated, although I wonder why dvd:///dev/scd0 would
work, and not /dev/scd0 (which is supposed to be changed to dvd:///dev/scd0 by
the playlist parser).
Otherwise, any chance for you to try totem from rawhide?
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there have not been any
updates to the report since thirty (30) days or more since we
requested additional information, we're assuming the problem
is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.
Setting status to "CLOSED INSUFFICIENT_DATA". If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.
Thank you in advance.
Note that maintenance for Fedora 7 will end 30 days after the GA of Fedora 9.