github-starred/firejail

Fork 0

mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00

[GH-ISSUE #1134] [Solved] Virtualbox error in Manjaro: "Effective UID is not root" #781

New issue

Closed

opened 2026-05-05 06:39:13 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 06:39:13 -06:00

Owner

Originally created by @ghost on GitHub (Mar 7, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1134

Hi there! :)
First of all, thank you really much, netblue30, for developing Firejail! :) I really like it, and use it a lot. The issue: VirtualBox is not working in Manjaro 17.0 inside Firejail (nor firejail VirtualBox %U, nor firejail VirtualBox), I get the following error message:

Effective UID is not root (euid=1000 egid=1000 uid=1000 gid=1000) (rc=-10)
Please try reinstalling VirtualBox.
where: SUPR3HardenedMain what: 2 VERR_PERMISSION_DENIED (-10) - Permission denied.

It works outside Firejail.
More info:
I have the following packages related to VirtualBox:

$ pacman -Q | grep virtualbox
linux310-virtualbox-host-modules 5.1.14-2
linux49-virtualbox-host-modules 5.1.14-7
virtualbox 5.1.14-3

And this kernel:

$ uname -a
Linux lemongrass-pc 4.9.13-1-MANJARO #1 SMP PREEMPT Sun Feb 26 13:27:28 UTC 2017 x86_64 GNU/Linux

Originally created by @ghost on GitHub (Mar 7, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1134 Hi there! :) First of all, thank you really much, netblue30, for developing Firejail! :) I really like it, and use it a lot. The issue: VirtualBox is not working in Manjaro 17.0 inside Firejail (nor firejail VirtualBox %U, nor firejail VirtualBox), I get the following error message: > Effective UID is not root (euid=1000 egid=1000 uid=1000 gid=1000) (rc=-10) > Please try reinstalling VirtualBox. > where: SUPR3HardenedMain what: 2 VERR_PERMISSION_DENIED (-10) - Permission denied. It works outside Firejail. More info: I have the following packages related to VirtualBox: ``` $ pacman -Q | grep virtualbox linux310-virtualbox-host-modules 5.1.14-2 linux49-virtualbox-host-modules 5.1.14-7 virtualbox 5.1.14-3 ``` And this kernel: ``` $ uname -a Linux lemongrass-pc 4.9.13-1-MANJARO #1 SMP PREEMPT Sun Feb 26 13:27:28 UTC 2017 x86_64 GNU/Linux ```

gitea-mirror

2026-05-05 06:39:13 -06:00

closed this issue
added the
information_old
label

gitea-mirror commented

2026-05-05 06:39:19 -06:00

Author

Owner

@Fred-Barclay commented on GitHub (Mar 8, 2017):

G'day @Lemongrass38 - great seeing you around here! 😄
What happens with firejail --noprofile virtualbox?

@Fred-Barclay commented on GitHub (Mar 8, 2017): G'day @Lemongrass38 - great seeing you around here! :smile: What happens with `firejail --noprofile virtualbox`?

gitea-mirror commented

2026-05-05 06:39:22 -06:00

Author

Owner

@netblue30 commented on GitHub (Mar 8, 2017):

Works fine on Debian stable with VirtualBox 5.0.24. Check if vbox kernel modules are loaded into the kernel when you start the computer:

$ lsmod | grep vbox
vboxpci                24576  0 
vboxnetadp             28672  0 
vboxnetflt             28672  0 
vboxdrv               450560  3 vboxnetadp,vboxnetflt,vboxpci

It is possible the version you have tries to load the kernel modules and is prevented by firejail.

You can also try after a computer startup to start VirtualBox without a sandbox, vbox manager comes up and loads the kernel modules, than you shut it down and start it in the sandbox.

@netblue30 commented on GitHub (Mar 8, 2017): Works fine on Debian stable with VirtualBox 5.0.24. Check if vbox kernel modules are loaded into the kernel when you start the computer: ````` $ lsmod | grep vbox vboxpci 24576 0 vboxnetadp 28672 0 vboxnetflt 28672 0 vboxdrv 450560 3 vboxnetadp,vboxnetflt,vboxpci ````` It is possible the version you have tries to load the kernel modules and is prevented by firejail. You can also try after a computer startup to start VirtualBox without a sandbox, vbox manager comes up and loads the kernel modules, than you shut it down and start it in the sandbox.

gitea-mirror commented

2026-05-05 06:39:23 -06:00

Author

Owner

@ghost commented on GitHub (Mar 14, 2017):

Hi, thank you both for the reply! ;)

Unfortunately after the day I posted this issue, I installed Arch and now my Manjaro refuses to boot. And as Arch is now my main OS, I can't easily reproduce the issue. I'm sorry for this "false alarm". I didn't mean to work you uselessly. Hmm. I just wished to help firejail become even better.

As for my part, Manjaro is based on Arch, and yes, it gave the exact same error message on the first run. But after I ran it as you said, netblue30, without firejail, and then VirtualBox opened. After this and changing to the linux-lts kernel (I don't know how much this can affect VirtualBox and firejail) VirtualBox opened in firejail like firejail virtualbox %u. So it seems that either the linux-lts kernel fixed that, or I had to run VirtualBox once outside firejail. When I ran it the next time, I didn't have to run VirtualBox outside firejail again. One of these fixed my issue.

Thank you really much again.

@Fred-Barclay : great to see you here too! :) Believe it or not, I learned Python3 in an afternoon/evening (I built upon my programming knowledge that I was thought instead of just using certain programs in high school), and started coding my homework right away. Very good indeed. :)

@ghost commented on GitHub (Mar 14, 2017): Hi, thank you both for the reply! ;) Unfortunately after the day I posted this issue, I installed Arch and now my Manjaro refuses to boot. And as Arch is now my main OS, I can't easily reproduce the issue. I'm sorry for this "false alarm". I didn't mean to work you uselessly. Hmm. I just wished to help firejail become even better. As for my part, Manjaro is based on Arch, and yes, it gave the exact same error message on the first run. But after I ran it as you said, netblue30, without firejail, and then VirtualBox opened. After this and changing to the linux-lts kernel (I don't know how much this can affect VirtualBox and firejail) VirtualBox opened in firejail like `firejail virtualbox %u`. So it seems that either the linux-lts kernel fixed that, or I had to run VirtualBox once outside firejail. When I ran it the next time, I didn't have to run VirtualBox outside firejail again. One of these fixed my issue. Thank you really much again. @Fred-Barclay : great to see you here too! :) Believe it or not, I learned Python3 in an afternoon/evening (I built upon my programming knowledge that I was thought instead of just using certain programs in high school), and started coding my homework right away. Very good indeed. :)

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#781

No description provided.

Rows
Columns