Can't install Extensions in WMaker / Linux Mint 17.2

[BasilRathbone]

Clicking on "Insert Guest Additions CD Image" while running WMaker (0.95.8+20170322) running on Linux Mint 17.2 fails.

VBOXADDITIONS_5.1.28_117968 never shows up under /media/my_name/

Inserting Guest Additions has never worked under any version of WMaker I've ever run.

I can log out of WMaker and log back in under XFCE and install guest additions but that's trashed the MDM Menu and my ability to log back in to WMaker.

[BasilRathbone]

Log file for Cinelerra (Linux Mint 17.2 / XFCE / WMaker)

[BasilRathbone]

prompt to upgrade Extension Pack from 5.1.22 to 5.1.28

[BasilRathbone]

Error message trying to mount Extension Pack

[BasilRathbone]

Attempting to mount Guest Additions in WMaker generates the following error message:

Could not mount the media/drive 'C:\Program Files\VirtualBox\VBoxGuestAdditions.iso' (VERR_PDM_MEDIA_LOCKED).

Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed} Callee: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

[Socratis]

Replying to BasilRathbone:

Could not mount the media/drive 'C:\Program Files\VirtualBox\VBoxGuestAdditions.iso' (VERR_PDM_MEDIA_LOCKED).

In your case if had you ​searched for that error (VERR_PDM_MEDIA_LOCKED) you'd have found out quite fast that your Guest Additions CD is already mounted in another VM, from a previous version. So, check the Media Manager and release the "VBoxGuestAdditions.iso" from whatever VM is using it.

May I suggest something? It's usually better and faster, if issues like this one (configuration, question) get first addressed in the ​VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is not a bug and someone from the developers has to deal with it and close it as "Invalid".

[BasilRathbone]

Replying to socratis:

Replying to BasilRathbone:

Could not mount the media/drive 'C:\Program Files\VirtualBox\VBoxGuestAdditions.iso' (VERR_PDM_MEDIA_LOCKED).

In your case if had you ​searched for that error (VERR_PDM_MEDIA_LOCKED) you'd have found out quite fast that your Guest Additions CD is already mounted in another VM, from a previous version. So, check the Media Manager and release the "VBoxGuestAdditions.iso" from whatever VM is using it.

May I suggest something? It's usually better and faster, if issues like this one (configuration, question) get first addressed in the ​VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is not a bug and someone from the developers has to deal with it and close it as "Invalid".

While that observation seems correct on the face of it, Socratis, there are NO OTHER VM's running -AND- I checked my mount point, /media/my_name, and found NO SUBDIRECTORIES under it.

There appears to be some conflict between VB and WMaker.

[BasilRathbone]

I'm more than happy to build a Linux Mint 17.2 / XFCE / WMaker VM under VirtualBox 5.1.22 and submit it for testing. Just tell me where and how to send it.

[Socratis]

I didn't say that there have to be other VMs running. I believe I was very clear.

• Check the Media Manager.
• Find the VBoxGuestAdditions.iso.
• See what VM has it mounted.
• Release the ISO from that VM or any other VM that has it mounted.

I didn't say anything about running VMs or your /media/my_name directory...

[BasilRathbone]

Replying to socratis:

I didn't say that there have to be other VMs running. I believe I was very clear.

• Check the Media Manager.
• Find the VBoxGuestAdditions.iso.
• See what VM has it mounted.
• Release the ISO from that VM or any other VM that has it mounted.

I didn't say anything about running VMs or your /media/my_name directory...

There is -NOTHING- mounted in the VM manager. It says the drive is empty.

[Socratis]

The VirtualBox Manager does *not* deal with the drives. Are you sure you go from the main VirtualBox Manager to the menu File » Virtual Media Manager... » Optical disks? Can I please see a picture of the Virtual Media Manager dialog, with the Optical disks?

[BasilRathbone]

Replying to socratis:

The VirtualBox Manager does *not* deal with the drives. Are you sure you go from the main VirtualBox Manager to the menu File » Virtual Media Manager... » Optical disks? Can I please see a picture of the Virtual Media Manager dialog, with the Optical disks?

The issue(s) appear to be between WMaker and VB only. I dropped back to XFCE and inserted the Guest Additions, then logged out of XFCE and back into WMaker. The Guest additions NOW appeared under /media/my_name as expected.

However installing the Guest Additions under WMaker trashed my MDM menu just like it did under XFCE (#17166).

[BasilRathbone]

I started over from scratch and made a new WMaker VM. When I clicked "Insert Guest Additions CD" under the devices drop-down menu, both Virtual Media Manager and VM Manager indicate the optical drive is then mounted -BUT- nothing shows up in WMaker.

I did a "sudo find / -name "VB*" and all that showed up was a link under /dev/disk/by-label the linked to ../../sr0.

There is absolutely nothing mounted under /media under any name.

Everything mounts and installs properly under XFCE but nothing mounts under WMaker.

[BasilRathbone]

WMaker doesn't recognize Guest Additions even when it's mounted manually in VB Manager before starting the VM.

This issue appears to be a WMaker issue only. WMaker is such a subset of Linux that it's probably not worth wasting much time over.

I'm much more concerned with item #17166 than this one. I can get around this issue by dropping back to XFCE, installing Guest Additions, then coming back to WMaker (as long as my MDM menu hasn't been trashed).