Date: Fri, 24 Nov 2023 08:30:14 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 275295] Linuxulator: faccessat2 unsupported flag 0x100 Message-ID: <bug-275295-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275295 Bug ID: 275295 Summary: Linuxulator: faccessat2 unsupported flag 0x100 Product: Base System Version: 14.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: kenrap@kennethraplee.com Recently a weird file permission issue had popped up with using the Brave browser through the Linuxulator when trying to run it: /usr/local/bin/linux-brave: /compat/ubuntu/opt/brave.com/brave/brave-wrapper: Permission denied The permissions were fine and the problem continued to persist after trying multiple Ubuntu-lator re-installations, even with different versions, e.g.: jammy, lunar, mantic. Eventually I thought to peak into the dmesg output and found the following: linux: jid 0 pid 63533 (systemctl): faccessat2 unsupported flag 0x100 linux: jid 0 pid 64609 (systemctl): faccessat2 unsupported flag 0x100 linux: jid 0 pid 66611 (systemctl): faccessat2 unsupported flag 0x100 linux: jid 0 pid 75500 (systemctl): faccessat2 unsupported flag 0x100 linux: jid 0 pid 77301 (systemctl): faccessat2 unsupported flag 0x100 linux: jid 0 pid 79047 (systemctl): faccessat2 unsupported flag 0x100 linux: jid 0 pid 85152 (systemctl): faccessat2 unsupported flag 0x100 linux: jid 0 pid 88585 (grep): syscall splice not really implemented linux: jid 0 pid 64576 (kbd_mode): linux_ioctl_fallback fd=5, cmd=0x4b33 ('K',51) is not implemented linux: jid 0 pid 64576 (kbd_mode): linux_ioctl_fallback fd=5, cmd=0x4b33 ('K',51) is not implemented linux: jid 0 pid 50603 (systemctl): faccessat2 unsupported flag 0x100 linux: jid 0 pid 44462 (systemctl): faccessat2 unsupported flag 0x100 linux: jid 0 pid 44462 (systemctl): faccessat2 unsupported flag 0x100 linux: jid 0 pid 22 (systemctl): faccessat2 unsupported flag 0x100 linux: jid 0 pid 4658 (systemctl): faccessat2 unsupported flag 0x100 linux: jid 0 pid 11089 (setcap): capset[0] effective=0x80000000, permitted=0x0, inheritable=0x0 is not implemented linux: jid 0 pid 15094 (systemctl): faccessat2 unsupported flag 0x100 linux: jid 0 pid 16805 (systemctl): faccessat2 unsupported flag 0x100 linux: jid 0 pid 18843 (systemctl): faccessat2 unsupported flag 0x100 linux: jid 0 pid 20469 (systemctl): faccessat2 unsupported flag 0x100 linux: jid 0 pid 24832 (systemctl): faccessat2 unsupported flag 0x100 linux: jid 0 pid 84149 (systemctl): faccessat2 unsupported flag 0x100 linux: jid 0 pid 85600 (systemctl): faccessat2 unsupported flag 0x100 linux: jid 0 pid 98160 (curl): unsupported setsockopt level 6 optname 31 linux: jid 0 pid 16546 (gpg-agent): syscall inotify_init not implemented With regards to the "(gpg-agent)" line, I would like to note that I've also been having `apt update` GPG errors in the Ubuntu linuxulation. I've used `deb [trusted=yes] ...` in /compat/ubuntu/etc/apt/sources.list as a workaround to get updates but users shouldn't have to do this either. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-275295-227>