> Do you have other things than the kernel from outside the Ubuntu
Archive?
Not much, just two packages:
uboot bootloader:
https://apt.armbian.com/pool/main/l/linux-u-boot-nanopct4-current/linux-u-boot-current-nanopct4_20.02.7_arm64.deb
board-specific configs and various tools, such as
Out of curiosity I tried to reproduce this on other SBC - NanoPi-M1
which also running Armbian. Interestingly, it's not reproducible on this
board.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rtkit in Ubuntu.
I have not seen it again in any environment since then.
Interesting that you hit it in such a specific environment.
I'd have expected that it might be incompatible components.
Do you have other things than the kernel from outside the Ubuntu Archive?
--
You received this bug notification because
I can reliably reproduce this:
1. Inside several aarch64 systemd-machined containers (with PrivateUsers=0 in
nspawn conf) with focal and running Gnome Shell session (accessed via TigerVNC
server). Hosts in NanoPC-T4.
2. On one bare metal NanoPC-T4 host with focal, running Gnome Shell Wayland
A full system restart resolved the issue for me, but thereby also
removed my chances to debug further. I hope the bug gives others that
might hit it as well a head start.
For now I'm marking it incomplete
** Changed in: rtkit (Ubuntu)
Status: New => Incomplete
--
You received this bug
I compared e.g. systemd-coredump vs rtkit.
Similar user add calls:
rtkit has:
--disabled-password
I recreated it without, and it made no difference.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rtkit in Ubuntu.
I was playing with different similar users (system user with nologin)
$ for u in $(grep nologin /etc/passwd | cut -d':' -f 1); do echo Trying $u;
/tmp/rtkit-0.12/rtkit-daemon --stderr --user-name $u; done
Working:
daemon bin sys games man lp mail news uucp proxy www-data backup list irc gnats
Knowing that --no-drop-privileges is related I was breaking that into
sub-sections.
I set -O0 for better debugging.
Then I dropped code of the drop-priv section.
This section is it:
1755 if (setgroups(0, NULL) < 0 ||
1756
This would work as well as a workaround:
--user-name root
setgroups and setresgid are safe, it is the user set via
setresuid
that makes it fail eventually.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rtkit in Ubuntu.
$ sudo userdel --remove rtkit
$ id rtkit
id: ‘rtkit’: no such user
$ sudo apt install --reinstall rtkit
$ id rtkit
uid=109(rtkit) gid=114(rtkit) groups=114(rtkit)
The issue does not go away by removing and recreating the user.
--
You received this bug notification because you are a member of
It is the raw clone call that fails:
101 if (__glibc_unlikely (ARCH_CLONE (_thread, STACK_VARIABLES_ARGS,
102 »···»···»···»···clone_flags, pd, >tid, tp, >tid)
103 »···»···»···== -1))
104 return
Similar:
https://superuser.com/questions/1440725/rtkit-fails-to-start-on-reboot
=> but I have no docker (nor runc/containerd)
https://bbs.archlinux.org/viewtopic.php?id=230079
=> re-install doesn't help for me (also I have no user issue)
--
You received this bug notification because you are a
Breakpoint 2, start_canary () at rtkit-daemon.c:2300
2300if (start_canary() < 0)
(gdb) n
1670if ((canary_fd = eventfd(0, EFD_NONBLOCK|EFD_CLOEXEC)) < 0 ||
(gdb)
1677if ((r = -pthread_create(_thread_id, NULL,
canary_thread, NULL)) < 0 ||
(gdb)
Breakpoint 1,
Thanks Christian for the bug report. I haven't see that issue reported
before. The rtkit user is correctly available on your system? Do you
have any warning/hint in the journal maybe?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Start through dbus fails the same way.
$ rtkitctl --start
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rtkit in Ubuntu.
https://bugs.launchpad.net/bugs/1871543
Title:
rtkit fails to start in focal "pthread_create
Reproducible:
$ sudo /usr/libexec/rtkit-daemon --stderr
rtkit-daemon[1764664]: Successfully called chroot.
rtkit-daemon[1764664]: Successfully dropped privileges.
rtkit-daemon[1764664]: Successfully limited resources.
rtkit-daemon[1764664]: pthread_create failed: Resource temporarily unavailable
The issue is on my workstation which might have all kind of config history.
On a fresh focal system it looks like "default off, start works"
root@f:~# systemctl status rtkit-daemon
● rtkit-daemon.service - RealtimeKit Scheduling Policy Service
Loaded: loaded
17 matches
Mail list logo
