Unable to AutoPlay DVDs

[Member RobK88]

I am having trouble autoplaying DVD’s with vlc player.

I suspect it may be related to my previous problems with automounting.
To get AntiX-19 (x86) to automount or even manually mount a DVD or CD, I had to manually create a mountpoint in Terminal:
sudo mkdir /media/cdrom
Now when I insert a DVD or CD, nothing really happens until I run the Rox File Manager and attempt to open up /media/cdrom. Then I see a message that the CD or DVD is automounting.

I would like to get vlc to automatically play a movie DVD when I insert a DVD.
I have set up the “Configure Automount” program as follows:

Checked “auto-luach preferred video player upon DVD insertion”

Command: /usr/bin/vlc dvd://

(I also tried “/usr/bin/vlc /media/cdrom” and tried “/usr/bin/vlc /dev/sr0”)

Nothing happens when I insert the DVD. I hear the disk spinning etc. I have to manually run vlc.

Any ideas for a fix?

[Forum Admin Dave]

Helpful

Up

0

::

Maybe the spacefm docs will help?
http://ignorantguru.github.io/spacefm/spacefm-manual-en.html#devices-settings-runa

Particularly the part on dvd’s and the other part on kernel polling

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

[Member RobK88]

Helpful

Up

0

::

Thanks for the tip regarding spacefm.

I ran spacefm and inserted the DVD, spacefm displayed a udevil error message stating the the mount point /media/sr0 could not be found.

So I manually created the mount point in terminal as follows:

sudo mkdir /media/sr0

Now it works!! I insert the DVD, the DVD automounts and vlc media player starts up and plays the movie DVD automatically!

P.S. I set up the “Configure Automount” program as follows:

Checked “auto-launch preferred video player upon DVD insertion”

Command: vlc simpledvd://

This sure looks like a bug in antiX-19 (x86). When I did a clean install of antiX-19, the antiX-19 installer should have created the mount point /media/sr0 for me.

• This reply was modified 3 years, 6 months ago by RobK88.
• This reply was modified 3 years, 6 months ago by RobK88.

[Forum Admin anticapitalista]

Helpful

Up

0

::

Did it set up mountpoint /media/cdrom?
It does seem that there is a bug in setting up internal hard drives/cd/dvd during installation.

• This reply was modified 3 years, 6 months ago by anticapitalista.
• This reply was modified 3 years, 6 months ago by anticapitalista.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member RobK88]

Helpful

Up

0

::

No, /media/cdrom was mever created either. (I manuallt created it using “sudo mkdir /dev/cdrom”

Yes, it sure looks like there is a bug in antiX-19 (x86) — likely with udev which should automatically create the mount points using rules found in /etc/udev/rules.d

[Forum Admin anticapitalista]

Helpful

Up

0

::

Can you test this for me please.

Make a backup of your current /etc/fstab and then delete the one you have.

Remove all mountpoint folders under /media (make sure they are unmounted otherwise you will delete the contents)

Run sudo make-fstab in a terminal.

Do all your hard drives, dvd drives etc now appear under /media?

thanks

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Moderator caprea]

Helpful

Up

0

::

I just did the above and yes, here all my harddrives etc appear now under media.

$ ls /media
cdrom  dvd    rootantiX17.2  rootantiX19  sr0
cdrw   dvdrw  rootantiX17.3  rootMX19

[Member RobK88]

Helpful

Up

0

::

Thank you for your post. I followed your instructions and generated a new /etc/fstab.

The new fstab is very similar to my original fastab (see below).
I ended up reverting to the original /etc/fstab since I liked the options better.

And during the generation of the new /etc/fstab, the following mountpoints were created in /media:

cdrom
cdrw
dvd
dvdrw
sr0
user (which is my username)

P.S When I insert a removable USB flash drive formatted in FAT32, a new mountpoint is typically created and shows up in the /media/user directory.

During the fresh install of antiX-19, shouldn’t the antiX-19 installer have created all these mountpoints?

As noted above, I preferred the original fstab file over the newly generated one:

Original /etc/fstab

# Pluggable devices are handled by uDev, they are not in fstab
UUID=2a6c1ed0-15d7-4f56-b5d6-92104c24477f / jfs defaults,noatime 1 1
UUID=4df08335-bd1b-4a3f-ac67-085f9f2fb131 /home jfs defaults,noatime 1 2
UUID=4e8fee7b-de51-418f-b3b5-0e5f52cead08 swap swap defaults 0 0 
/dev/cdrom                                 /media/cdrom                                iso9660    noauto,exec,users,ro            0 0
/dev/cdrw                                  /media/cdrw                                 iso9660    noauto,exec,users,rw            0 0
/dev/dvd                                   /media/dvd                                  udf        noauto,exec,users,ro            0 0
/dev/dvdrw                                 /media/dvdrw                                udf        noauto,exec,users,rw            0 0
/dev/sr0                                   /media/sr0                                  auto       noauto,exec,users,ro            0 0

Newly Generated fstab

# /etc/fstab: static file system information
#
# Created by make-fstab on Mon Nov  4 17:29:36 EST 2019

# <file system>                            <mount point>                               <type>     <options>                       <dump/pass>

# Added by make-fstab /dev/sda1  label=Linux-Swap
UUID=4e8fee7b-de51-418f-b3b5-0e5f52cead08  swap                                        swap       defaults                        0 0
# Added by make-fstab /dev/sda2  label=rootantiX19
UUID=2a6c1ed0-15d7-4f56-b5d6-92104c24477f  /                                           jfs        noauto,exec                     0 0
# Added by make-fstab /dev/sda3  label=homeantiX
UUID=4df08335-bd1b-4a3f-ac67-085f9f2fb131  /home                                       jfs        noauto,exec                     0 0
# Added by make-fstab /dev/cdrom
/dev/cdrom                                 /media/cdrom                                iso9660    noauto,exec,users,ro            0 0
# Added by make-fstab /dev/cdrw
/dev/cdrw                                  /media/cdrw                                 iso9660    noauto,exec,users,rw            0 0
# Added by make-fstab /dev/dvd
/dev/dvd                                   /media/dvd                                  udf        noauto,exec,users,ro            0 0
# Added by make-fstab /dev/dvdrw
/dev/dvdrw                                 /media/dvdrw                                udf        noauto,exec,users,rw            0 0
# Added by make-fstab /dev/sr0
/dev/sr0                                   /media/sr0                                  auto       noauto,exec,users,ro            0 0

• This reply was modified 3 years, 6 months ago by RobK88.

[Forum Admin anticapitalista]

Helpful

Up

0

::

As I posted above –

anticapitalista wrote:

…
It does seem that there is a bug in setting up internal hard drives/cd/dvd during installation.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member ModdIt]

Helpful

Up

0

::

Several users having dvd playback issues.
Changing regional code did not solve issue nor did any of the suggestions in this thread.

swapping out my drive solved issue for me immediately, further checks showed all affected had Asus drives same as me. I have had a lot of issues with that label already. Perfectly engineered, fail weeks to a couple of months after the garantee runs out. On occasion before.

I am now running an anchient japanese made IDE DVDRW drive with SATA to IDE converter. Bliss, it is just as fast as the drive I replaced, very quiet against GE90 Engine on Full thrust noise of the asus. And it plays the previously non working disks without issue.

Some new LG Drives coming on Feb 2 or roundabout, will update if these solve issues as I expect.

As yet I have not tried to solve autoplay. Will tackle that when the new drives are installed.

[Author]

Posts