Bug 499796

Hmm, found this very similar Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/libdvdread/+bug/342890

So is this likely to be a dvdread bug? This is what ubuntu is doing:

---
libdvdread (4.1.3-4ubuntu2) jaunty; urgency=low

  * Use autogen.sh and configure script instead of configure2 till we figure
    out why configure2 breaks the library. (LP: #342890)
  * debian/control
    - Add autoconf, automake, libtool to 'Build-Depends' as required by the
      autogen.sh script.
  * debian/rules
    - Add -DHAVE_DLFCN_H to CFLAGS. Use autogen.sh instead of configure2 script.
  * debian/libdvdread-dev.install
    - Add .la and macro file to libdvdread-dev package.
  * debian/patches/04-fix-lib-version.patch
    - Correct the version of libdvdread.so file.
---

The other solution mentioned is "with xine, all works perfectly" :/

Jan (the upstream author of resindvd) mentions that this should be fixed in the current gst-plugins-bad master.

Given that we don't ship gst-plugins-bad, but do ship libdvdread, please test with the current gst-plugins-bad master.

I compiled the latest pre-prelease of gst-plugins-bad on my ubuntu system and DVD playback works very well there. I'm still struggling to get things working on F11 though. Given the fact that I also have issues with non-gstreamer DVD apps, there may actually be two bugs here (one fixed in recent -bad and one still in libdvdread).

I thought you said it worked "perfectly" with xine? Reassigning to libdvdread then.

(In reply to comment #4)
> I thought you said it worked "perfectly" with xine? Reassigning to libdvdread
> then.  

Sorry, that was just another quote from the Ubuntu bug (which I still don't know if it is related). However, I will try xine if that helps narrowing down the problem.

Ok, tested playing the DVD with mplayer and xine on F11, no luck. I also tried copying the relevant keys from ~/.dvdcss/ from my other system, still no luck.

Created attachment 343772 [details]
Console log with gst-plugins-bad 0.10.11.2

Created attachment 343774 [details]
Console log with gst-plugins-bad 0.10.11.2 and keys copied

And so I finally found the issue (!)

...
sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
sr 3:0:0:0: [sr0] Sense Key : Illegal Request [current] 
sr 3:0:0:0: [sr0] Add. Sense: Media region code is mismatched to logical unit region
end_request: I/O error, dev sr0, sector 308320
...

The drive did not have a region code set. I used regionset and now it works.
1) since when does linux care about dvd region protection in any way?
2) can this be worked around without using regionset?
3) if not, is there a way to tell the user what to do instead of crashing and/or showing useless messages?

Linux cares about the region protection because you have a drive with an RPC-II firmware (as all new drives are). With RPC-II, the drive itself actively refuses access to some of the data unless the correct region is set and CSS negotiation succeeds.

The only solution is to either set the correct region on the drive (can only be changed a limited number of times etc), or to find an RPC-I firmware for the drive model and reflash the drive with a 'region-free' firmware.

libdvdread should get us back a decent error when the region of the DVD and the drive don't match, so that the resindvd plugin could tell us what's wrong.

This would involve pulling code from regionset. Is there an upstream for libdvdread these days, that'll take patches?

(In reply to comment #11)
> libdvdread should get us back a decent error when the region of the DVD and the
> drive don't match, so that the resindvd plugin could tell us what's wrong.
That would be nice. I'm sure a few of the posters in the ubuntu bug linked above suffer from the same confusion as me...

> Is there an upstream for libdvdread these days, that'll take patches?  
I found a short explaination from *bsd:

---
Update to libdvdread 4.1.3. This is a fun one, as dvdread/dvdnav is now
maintained by the mplayer project and according to the changelog, this
dvdread package was split out from dvdnav in 4.1.3. Check the ChangeLog
in the distfile for the full drama.
---

the checks in libdvdread also need to take into account that the drive might be RPC-I, or already have been flashed with a region-free firmware. In that case, it doesn't matter if the region doesn't match.

Effectively, libdvdread needs to try and get some data, and only double-check about the regions if it fails.

This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Thanks for the report, folks. Ideally this should be moved to upstream bugtracker, but we don't have one yet. I've forwarded the request.

This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Still seems to be present in Fedora 13.

William Henry
The libdvdread error is still present in Fedora 14. 
[quasar@localhost ~]$ lsdvd
libdvdread: Using libdvdcss version 1.2.11 for DVD access
libdvdnav:DVDOpenFileUDF:UDFFindFile /VIDEO_TS/VIDEO_TS.IFO failed
libdvdnav:DVDOpenFileUDF:UDFFindFile /VIDEO_TS/VIDEO_TS.BUP failed
libdvdread: Can't open file VIDEO_TS.IFO.

From lshw:
*-cdrom:0
                description: DVD-RAM writer
                product: DVD A  DH20A4P
                vendor: ATAPI
                physical id: 2
                bus info: scsi@1:0.0.0
                logical name: /dev/cdrom1
                logical name: /dev/cdrw1
                logical name: /dev/dvd1
                logical name: /dev/dvdrw1
                logical name: /dev/scd0
                logical name: /dev/sr0
                logical name: /media/Pirates_Of_The_Carribean_4_USA
                version: 9P53
                capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
                configuration: ansiversion=5 mount.fstype=udf mount.options=ro,nosuid,nodev,relatime,uid=500,gid=500,umask=77,iocharset=utf8 state=mounted status=ready
              *-medium
                   physical id: 0
                   logical name: /dev/cdrom1
                   logical name: /media/Pirates_Of_The_Carribean_4_USA
                   configuration: mount.fstype=udf mount.options=ro,nosuid,nodev,relatime,uid=500,gid=500,umask=77,iocharset=utf8 state=mounted

The region code on my dvd device is unset. The disc type is DVD9

This is something only upstream can fix. No point in keeping this open. I asked the question again on current upstream mailing list: https://mailman.videolan.org/pipermail/libdvdnav-devel/2019-February/000709.html .