Getting what seems like a spurious KeyboardInterrupt during a specific emerge operation. # emerge --config sys-libs/timezone-data Configuring pkg... * Found a regular file at /etc/localtime. * Some software may expect a symlink instead. * You may convert it to a symlink by removing the file and running: * emerge --config sys-libs/timezone-data * Copying /usr/share/zoneinfo/Europe/Helsinki to /etc/localtime. Unable to unshare: EINVAL (for FEATURES="ipc-sandbox network-sandbox pid-sandbox") Traceback (most recent call last): File "/usr/lib/portage/python3.10/socks5-server.py", line 6, in <module> import asyncio File "/usr/lib/python3.10/asyncio/__init__.py", line 8, in <module> from .base_events import * File "/usr/lib/python3.10/asyncio/base_events.py", line 18, in <module> import concurrent.futures File "/usr/lib/python3.10/concurrent/futures/__init__.py", line 8, in <module> from concurrent.futures._base import (FIRST_COMPLETED, File "/usr/lib/python3.10/concurrent/futures/_base.py", line 7, in <module> import logging File "/usr/lib/python3.10/logging/__init__.py", line 28, in <module> from string import Template File "<frozen importlib._bootstrap>", line 1027, in _find_and_load File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 688, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 879, in exec_module File "<frozen importlib._bootstrap_external>", line 1012, in get_code File "<frozen importlib._bootstrap_external>", line 672, in _compile_bytecode KeyboardInterrupt And it's definitely not me doing anything to trigger the signal. So far I'm seeing this on all the x86-32 boxes I tried, but didn't see it on x86-64 machines. The actual backtrace can change from one run to the next, presumably due to the asynchronous nature of the signal. I thought maybe my i686 cross distcc setup somehow screwed up my dev-lang/python, but I re-emerged it with FEATURES=-distcc and I'm still getting this. Also tried a few different kernels from ~5.0 to ~6.1-rc3. Seeing the problem on all of them.
Could you please: 1. share anything else interesting about your system, if any; 2. some more of the example backtraces; 3. include emerge --info; 4. indicate if you know when it started happening?
