Red Hat Bugzilla – Bug 1469776
fails to run on first boot after KDE install with ModuleNotFoundError: No module named 'pyanaconda.threads'
Last modified: 2017-07-24 21:16:58 EDT
Similar to https://bugzilla.redhat.com/show_bug.cgi?id=1463960 for anaconda, but for initial-setup.
On current Rawhide, if you install from the KDE live image and do not create a user during installation, initial-setup should run on the first boot, but it does not. In the journal, you can see these errors:
Jul 10 16:47:02 localhost.localdomain initial-setup: initializing the Anaconda log
Jul 10 16:47:02 localhost.localdomain initial-setup: initializing threading
Jul 10 16:47:02 localhost.localdomain initial-setup: Initial Setup crashed due to unhandled exception:
Traceback (most recent call last):
File "/usr/libexec/initial-setup/initial-setup-graphical", line 5, in <module>
is_instance = InitialSetup(gui_mode=True)
File "/usr/lib/python3.6/site-packages/initial_setup/__init__.py", line 141, in __init__
from pyanaconda.threads import initThreading
ModuleNotFoundError: No module named 'pyanaconda.threads'
Jul 10 16:47:02 localhost.localdomain initial-setup: Stopping the window manager (/usr/bin/kwin_x11)
This probably also affects the ARM disk image (where initial-setup must run on first boot or else the system is unusable), so nominating as an Alpha blocker per criterion "A working mechanism to create a user account must be clearly presented during installation and/or first boot of the installed system."
This should be fixed in 0.3.48 - but the build fails due to some unrelated s390 breakage:
I'll be on PTO from today afternoon so someone else will have to do the build once the s390 stuff is fixed.
I've sent the build now: https://koji.fedoraproject.org/koji/buildinfo?buildID=917785 . I'll go ahead and close this, openQA will verify with the next compose; I'll re-open if it's somehow still busted.