F30 KDE Spin no Login GUI after update

[Ed Greshko]

I had a running F30 system in a KVM VM.

When updating with these latest packages

kf5-akonadi-server.x86_64             18.12.2-2.fc30             updates-testing
kf5-akonadi-server-mysql.x86_64       18.12.2-2.fc30             updates-testing
kf5-frameworkintegration.x86_64       5.55.0-2.fc30              updates-testing
kf5-frameworkintegration-libs.x86_64  5.55.0-2.fc30              updates-testing
kf5-kdeclarative.x86_64               5.55.0-2.fc30              updates-testing
kf5-kwayland.x86_64                   5.55.0-2.fc30              updates-testing
kf5-kxmlgui.x86_64                    5.55.0-2.fc30              updates-testing
kwin.x86_64                           5.15.2-3.fc30              updates-testing
kwin-common.x86_64                    5.15.2-3.fc30              updates-testing
kwin-libs.x86_64                      5.15.2-3.fc30              updates-testing
plasma-integration.x86_64             5.15.2-2.fc30              updates-testing
qt-settings.noarch                    30.0-1.fc30                updates-testing
qt5-qdbusviewer.x86_64                5.12.1-1.fc30              updates-testing
qt5-qtbase.x86_64                     5.12.1-2.fc30              updates-testing
qt5-qtbase-common.noarch              5.12.1-2.fc30              updates-testing
qt5-qtbase-gui.x86_64                 5.12.1-2.fc30              updates-testing
qt5-qtbase-mysql.x86_64               5.12.1-2.fc30              updates-testing
qt5-qtdeclarative.x86_64              5.12.1-1.fc30              updates-testing
qt5-qtgraphicaleffects.x86_64         5.12.1-1.fc30              updates-testing
qt5-qtimageformats.x86_64             5.12.1-1.fc30              updates-testing
qt5-qtlocation.x86_64                 5.12.1-1.fc30              updates-testing
qt5-qtmultimedia.x86_64               5.12.1-1.fc30              updates-testing
qt5-qtquickcontrols.x86_64            5.12.1-1.fc30              updates-testing
qt5-qtquickcontrols2.x86_64           5.12.1-1.fc30              updates-testing
qt5-qtscript.x86_64                   5.12.1-1.fc30              updates-testing
qt5-qtsensors.x86_64                  5.12.1-1.fc30              updates-testing
qt5-qtspeech.x86_64                   5.12.1-1.fc30              updates-testing
qt5-qtspeech-speechd.x86_64           5.12.1-1.fc30              updates-testing
qt5-qtsvg.x86_64                      5.12.1-1.fc30              updates-testing
qt5-qttools.x86_64                    5.12.1-1.fc30              updates-testing
qt5-qttools-common.noarch             5.12.1-1.fc30              updates-testing
qt5-qttools-libs-designer.x86_64      5.12.1-1.fc30              updates-testing
qt5-qtvirtualkeyboard.x86_64          5.12.1-1.fc30              updates-testing
qt5-qtwebchannel.x86_64               5.12.1-1.fc30              updates-testing
qt5-qtwebengine.x86_64                5.12.1-1.fc30              updates-testing
qt5-qtwebkit.x86_64                   5.212.0-0.34.alpha2.fc30   updates-testing
qt5-qtx11extras.x86_64                5.12.1-1.fc30              updates-testing
qt5-qtxmlpatterns.x86_64              5.12.1-2.fc30              updates-testing
sddm.x86_64                           0.18.0-6.fc30              updates-testing

The system will not go to the login screen.

It seems "stuck" with

[ OK ] Started Hold until boot process finishes up displayed

I can issue Alt-F2 to get to a TTY but I can't see anything obvious.

Know issue?

[Rodger Etz]

Hi,

Sounds like what I see using the F29 KDE spin upgraded to F30 on bare metal x86_64.

It seems SDDM is not launching properly via systemd anymore.

When you switch to another TTY, login and execute

systemctl stop sddm && sddm

it starts properly.

Did a quick strace and saw that something is trying to access some file without success when launching via systemd.

Sorry, didn't have time to dive into it and file an issue yet.

Best regards,
Rodger

-------- Original-Nachricht --------
An 22. März 2019, 10:51, Ed Greshko schrieb:
> I had a running F30 system in a KVM VM.
>
> When updating with these latest packages
>
> kf5-akonadi-server.x86_64             [18.12.2-2](tel:181222).fc30             updates-testing
> kf5-akonadi-server-mysql.x86_64       [18.12.2-2](tel:181222).fc30             updates-testing
> kf5-frameworkintegration.x86_64       [5.55.0-2](tel:55502).fc30              updates-testing
> kf5-frameworkintegration-libs.x86_[64  5.55.0-2](tel:[phone]).fc30              updates-testing
> kf5-kdeclarative.x86_64               [5.55.0-2](tel:55502).fc30              updates-testing
> kf5-kwayland.x86_64                   [5.55.0-2](tel:55502).fc30              updates-testing
> kf5-kxmlgui.x86_64                    [5.55.0-2](tel:55502).fc30              updates-testing
> kwin.x86_64                           [5.15.2-3](tel:51523).fc30              updates-testing
> kwin-common.x86_64                    [5.15.2-3](tel:51523).fc30              updates-testing
> kwin-libs.x86_64                      [5.15.2-3](tel:51523).fc30              updates-testing
> plasma-integration.x86_64             [5.15.2-2](tel:51522).fc30              updates-testing
> qt-settings.noarch                    [30.0-1](tel:3001).fc30                updates-testing
> qt5-qdbusviewer.x86_64                [5.12.1-1](tel:51211).fc30              updates-testing
> qt5-qtbase.x86_64                     [5.12.1-2](tel:51212).fc30              updates-testing
> qt5-qtbase-common.noarch              [5.12.1-2](tel:51212).fc30              updates-testing
> qt5-qtbase-gui.x86_64                 [5.12.1-2](tel:51212).fc30              updates-testing
> qt5-qtbase-mysql.x86_64               [5.12.1-2](tel:51212).fc30              updates-testing
> qt5-qtdeclarative.x86_64              [5.12.1-1](tel:51211).fc30              updates-testing
> qt5-qtgraphicaleffects.x86_64         [5.12.1-1](tel:51211).fc30              updates-testing
> qt5-qtimageformats.x86_64             [5.12.1-1](tel:51211).fc30              updates-testing
> qt5-qtlocation.x86_64                 [5.12.1-1](tel:51211).fc30              updates-testing
> qt5-qtmultimedia.x86_64               [5.12.1-1](tel:51211).fc30              updates-testing
> qt5-qtquickcontrols.x86_64            [5.12.1-1](tel:51211).fc30              updates-testing
> qt5-qtquickcontrols[2.x86](tel:2986)_64           [5.12.1-1](tel:51211).fc30              updates-testing
> qt5-qtscript.x86_64                   [5.12.1-1](tel:51211).fc30              updates-testing
> qt5-qtsensors.x86_64                  [5.12.1-1](tel:51211).fc30              updates-testing
> qt5-qtspeech.x86_64                   [5.12.1-1](tel:51211).fc30              updates-testing
> qt5-qtspeech-speechd.x86_64           [5.12.1-1](tel:51211).fc30              updates-testing
> qt5-qtsvg.x86_64                      [5.12.1-1](tel:51211).fc30              updates-testing
> qt5-qttools.x86_64                    [5.12.1-1](tel:51211).fc30              updates-testing
> qt5-qttools-common.noarch             [5.12.1-1](tel:51211).fc30              updates-testing
> qt5-qttools-libs-designer.x86_64      [5.12.1-1](tel:51211).fc30              updates-testing
> qt5-qtvirtualkeyboard.x86_64          [5.12.1-1](tel:51211).fc30              updates-testing
> qt5-qtwebchannel.x86_64               [5.12.1-1](tel:51211).fc30              updates-testing
> qt5-qtwebengine.x86_64                [5.12.1-1](tel:51211).fc30              updates-testing
> qt5-qtwebkit.x86_64                   [5.212.0-0.34](tel:[phone]).alpha2.fc30   updates-testing
> qt5-qtx11extras.x86_64                [5.12.1-1](tel:51211).fc30              updates-testing
> qt5-qtxmlpatterns.x86_64              [5.12.1-2](tel:51212).fc30              updates-testing
> sddm.x86_64                           [0.18.0-6](tel:01806).fc30              updates-testing
>
> The system will not go to the login screen.
>
> It seems "stuck" with
>
> [ OK ] Started Hold until boot process finishes up displayed
>
> I can issue Alt-F2 to get to a TTY but I can't see anything obvious.
>
> Know issue?
>
> --
> Right: I dislike the default color scheme Wrong: What idiot picked the default color scheme
> _______________________________________________
> test mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]

[Adam Williamson]

On Fri, 2019-03-22 at 16:07 +0000, Rodger Etz wrote:
> Hi,
>
> Sounds like what I see using the F29 KDE spin upgraded to F30 on bare metal x86_64.
>
> It seems SDDM is not launching properly via systemd anymore.
>
> When you switch to another TTY, login and execute
>
> systemctl stop sddm && sddm
>
> it starts properly.
>
> Did a quick strace and saw that something is trying to access some file without success when launching via systemd.
>
> Sorry, didn't have time to dive into it and file an issue yet.

It's likely to be the same thing affecting Rawhide:

https://bugzilla.redhat.com/show_bug.cgi?id=1686675

[Ed Greshko]

On 3/23/19 12:07 AM, Rodger Etz wrote:
> Sounds like what I see using the F29 KDE spin upgraded to F30 on bare metal x86_64.
>
> It seems SDDM is not launching properly via systemd anymore.
>
> When you switch to another TTY, login and execute
>
> systemctl stop sddm && sddm
>
> it starts properly.
>
> Did a quick strace and saw that something is trying to access some file without success when launching via systemd.
>
> Sorry, didn't have time to dive into it and file an issue yet.

Thanks.

Yes, it may be the BZ Adam refers to.