WILL NOT RUN FROM LINK/MENU/TOOLBAR

[caltrop]

only runs using GUI
any shortcuts will fail!

this has been an ongoing issue
would be nice if there was a simple fix...

---

OS Linux Mint 20.1 ulyssa
Desktop MATE Desktop Environment 1.24.0
Bash 5.0.17(1)-release x86_64-pc-linux-gnu
mono font DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"
kernel GNU/Linux 5.4.0-173-generic x86_64
kernel ver #191-Ubuntu SMP Fri Feb 2 13:55:07 UTC 2024

---

changed all file permissions
also lists error messages in the comments

Code: Select all

#!/usr/bin/bash
#------------------------------------------------------------------------------#
#                            Programmed By Liz                                 #
#------------------------------------------------------------------------------#
# change all vbox file permissions
#
# still doesn't fix the issue of NOT running from link/menu/toolbar
# runs fine from GUI or while GUI is active
# link/menu/toolbar has not worked for some time now
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# DESKTOP LINK (created by GUI)
#
# /usr/lib/virtualbox/VirtualBoxVM --comment "WinXP" --startvm "{2c989d1b-a127-41e1-882d-1e7431b63760}"
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# RESULT (COPY message gives more info than displayed)
#
# Failed to open a session for the virtual machine .
#
# The object functionality is limited.
#
# Result Code: E_ACCESSDENIED (0x80070005)
# Component: MachineWrap
# Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# {85632c68-b5bb-4316-a900-5eb28d3413df}
# this number does not exist in the file system
# some vbox thing...
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# $ vboxmanage -v
# 6.1.50_Ubuntur161033
#
# $ vboxmanage list vms
# "WinXP"         {2c989d1b-a127-41e1-882d-1e7431b63760}
# "TahrPup 6.0.5" {b041ffb5-5338-4f9c-bc54-a2e0a433678e}
# "DOS 6.22"      {082e8d63-a4c6-4f54-9d0c-0eb560432c64}
# "FreeDOS"       {d21070a1-59bc-4566-8a23-86d4a84358b5}
# "ReactOS"       {bdc47e1a-cdbb-4a4b-b955-87dacc069255}
#-------------------------------------------------------------------------------
clear
source ~/data/global.dat
p=664                                        # -rw-rw-r--
#-------------------------------------------------------------------------------
title-80.sh -t line "Changing All VBox File Permissions: 664 -rw-rw-r--"
dir="/home/caltrop/VirtualBox VMs"
find "$dir" -type f \! -perm "$p" | sort |   # find not $p
while read src
do
   chmod $p "$src"                           # set permission
   stat -c "%a %A %n" "$src"                 # display result
done
#-------------------------------------------------------------------------------

[arQon]

Even gnome should be able to cope with "VirtualBoxVM --startvm xyz" etc.

Only you can know what you did (or didn't do) to break things as badly as you apparently have, but whatever your permissions problem is (not being in vboxusers, etc) it seems likely that it was self-inflicted. Try undoing it.

Since you can't get it to work "unless the GUI is running", it sounds like your problem is really just an inability to start VBoxSVC. If you don't remember what you did it's probably easier to just reinstall VBox than to keep guessing and changing things at random, but IIRC the manual goes into plenty of detail about the groups you need to be a member of, etc, so if you prefer you could restore it that way instead.

[mariahcarey]

Look for any relevant error messages or logs in system log files (`/var/log/syslog`, `/var/log/messages`, etc.) that could provide clues about why VirtualBox is failing to launch from shortcuts or the menu.

[fth0]

Perhaps you have to use '/usr/bin/VirtualBoxVM' instead of '/usr/lib/virtualbox/VirtualBoxVM'. And note that it is a shell script.