Public bug reported:

Steps to reproduce:
install zesty VM
install virtualbox-guest-x11 (to enable 3d graphics)
reboot

screen blinks, nothing starts, everything is broken.

installing virtualbox-guest-dkms works, but just because of this udev rule:
https://anonscm.debian.org/cgit/pkg-virtualbox/virtualbox.git/tree/debian/virtualbox-guest-dkms.udev
KERNEL=="vboxguest", NAME="vboxguest", OWNER="root", MODE="0660"
KERNEL=="vboxuser", NAME="vboxuser", OWNER="root", MODE="0666"

please find a way to inject this rule now that your ship kernel modules, 
otherwise I'll be forced
to put an hard dependency from my x11 to my dkms packages (overriding de facto 
your kernel module).

Not sure why this issue is found only when we use the vbox *GL
implementation, but I suspect something breaks also in normal usage,
even if I can't easily prove it (not that I need to)

thanks for caring

Gianfranco
(Vbox maintainer)

** Affects: linux (Ubuntu)
     Importance: High
     Assignee: Andy Whitcroft (apw)
         Status: Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1677170

Title:
  Linux vbox guest modules needs udev rule

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  install zesty VM
  install virtualbox-guest-x11 (to enable 3d graphics)
  reboot

  screen blinks, nothing starts, everything is broken.

  installing virtualbox-guest-dkms works, but just because of this udev rule:
  
https://anonscm.debian.org/cgit/pkg-virtualbox/virtualbox.git/tree/debian/virtualbox-guest-dkms.udev
  KERNEL=="vboxguest", NAME="vboxguest", OWNER="root", MODE="0660"
  KERNEL=="vboxuser", NAME="vboxuser", OWNER="root", MODE="0666"

  please find a way to inject this rule now that your ship kernel modules, 
otherwise I'll be forced
  to put an hard dependency from my x11 to my dkms packages (overriding de 
facto your kernel module).

  Not sure why this issue is found only when we use the vbox *GL
  implementation, but I suspect something breaks also in normal usage,
  even if I can't easily prove it (not that I need to)

  thanks for caring

  Gianfranco
  (Vbox maintainer)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677170/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to