#1 from Daniel Hahler above worked for me:
You can probably work around this, by creating the group manually:
# Create group:
sudo groupadd vboxusers
# Add user:
sudo usermod -a -G vboxusers [yourlogin]
# Then restart the module:
sudo invoke-rc.d vboxdrv start
Many thanks!
Dominik
--
I had installed virtualbox-ose to see if I liked it (I did), but decided
that I wanted the full version, so I installed Sun xVM VirtualBox and
loved it even more. Having the better version, I removed the Virtualbox-
OSE, which deleted the vboxusers group, which caused these symptoms on
my system.
Hi everyone, I could fix the same problem creating a new Group in:
System Administration Users and Groups Manage GRoups
After you create the new group you have to add an user in this group
(your login name).
Logout. them login and that's all.
Bye!
___
Juancho.
--
Cannot change
This bug was fixed in the package virtualbox-ose-modules - 8
---
virtualbox-ose-modules (8) hardy; urgency=low
* debian/control: Build also virtualbox-ose-modules-*-{386,rt,virtual}
(LP: #156740)
* debian/init:
- Merged from virtualbox-ose SVN
- Re-add stop action and
** Changed in: virtualbox-ose-modules (Ubuntu)
Assignee: Steve Kowalik (stevenk) = Daniel Hahler (blueyed)
Status: Confirmed = In Progress
--
Cannot change owner vboxusers for device /dev/vboxdrv
https://bugs.launchpad.net/bugs/153819
You received this bug notification because you
This is apparently a duplicate of Bug #154630
--
Cannot change owner vboxusers for device /dev/vboxdrv
https://bugs.launchpad.net/bugs/153819
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Steve, can you please take a look at this one?
** Changed in: virtualbox-ose-modules (Ubuntu)
Assignee: (unassigned) = Steve Kowalik (stevenk)
--
Cannot change owner vboxusers for device /dev/vboxdrv
https://bugs.launchpad.net/bugs/153819
You received this bug notification because you are
Yep, just checked my bash_history, and it looks like the steps to fix it
are just to manually run a sudo /etc/init.d/vboxdrv start afterwards
(to create the /dev/vboxdrv device with the right permissions now that
the group exists), and then add accounts to the vboxusers group
manually.
Since I
** Attachment added: debdiff for gutsy-proposed
http://launchpadlibrarian.net/10110644/virtualbox-ose-modules_6.1.dsc.diff
--
Cannot change owner vboxusers for device /dev/vboxdrv
https://bugs.launchpad.net/bugs/153819
You received this bug notification because you are a member of Ubuntu
I've experimented with using Depends and Pre-Depends, but could not make
it work, so that virtualbox-ose would get configured before virtualbox-
ose-modules-...
Therefor I think the right fix appears to just not chowning
/dev/vboxdrv, when the group vboxusers does not exist yet.
** Attachment
** Attachment removed: debdiff for gutsy-proposed
http://launchpadlibrarian.net/10110644/virtualbox-ose-
modules_6.1.dsc.diff
** Attachment added: debdiff for gutsy-proposed
http://launchpadlibrarian.net/10110654/virtualbox-ose-modules_6.1.dsc.diff
--
Cannot change owner vboxusers for
The problem is that virtualbox-ose-modules-* does not depend on
virtualbox-ose, which makes sure the user exists. And if you install
both packages together, the user is not created yet, when the modules
package expects it to be.
The problem can be reproduced as follows:
$ sudo groupdel vboxusers
Unfortunately this is a machine in my office which I've now left for the
weekend. When I ran grep vboxusers /etc/group after getting back to
the command line, it told me the group existed with GID 119, but had no
members. I worked out that the reason /dev/vboxdrv didn't exist is due
to the module
** Changed in: virtualbox-ose-modules (Ubuntu)
Sourcepackagename: virtualbox-ose = virtualbox-ose-modules
--
Cannot change owner vboxusers for device /dev/vboxdrv
https://bugs.launchpad.net/bugs/153819
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
The init script wants to make sure that the device is owned by the
correct group, but unfortunately the group does not get created by the
postinst scripts.
You say that the vboxusers group does exist already, but I don't think that's
the case. It would not say invalid group in this case
vboxusers should have been created by virtualbox-ose
** Changed in: virtualbox-ose-modules (Ubuntu)
Status: In Progress = Incomplete
--
Cannot change owner vboxusers for device /dev/vboxdrv
https://bugs.launchpad.net/bugs/153819
You received this bug notification because you are a member
16 matches
Mail list logo
