Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1469776 - fails to run on first boot after KDE install with ModuleNotFoundError: No module named 'pyanaconda.threads'
Summary: fails to run on first boot after KDE install with ModuleNotFoundError: No mod...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: initial-setup
Version: rawhide
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Martin Kolman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: AlphaBlocker, F27AlphaBlocker
TreeView+ depends on / blocked
 
Reported: 2017-07-11 19:51 UTC by Adam Williamson
Modified: 2017-07-25 01:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-25 01:16:58 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Adam Williamson 2017-07-11 19:51:10 UTC 
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[824]: initializing the Anaconda log
Jul 10 16:47:02 localhost.localdomain initial-setup[824]: initializing threading
Jul 10 16:47:02 localhost.localdomain initial-setup[824]: 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[982]: 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."
Comment 1 Martin Kolman 2017-07-12 10:34:28 UTC 
This should be fixed in 0.3.48 - but the build fails due to some unrelated s390 breakage:
https://koji.fedoraproject.org/koji/taskinfo?taskID=20474257

I'll be on PTO from today afternoon so someone else will have to do the build once the s390 stuff is fixed.
Comment 2 Adam Williamson 2017-07-25 01:16:58 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.