Bug 2066304 - hang after login
Summary: hang after login
Keywords:
Status: CLOSED DUPLICATE of bug 2070130
Alias: None
Product: Fedora
Classification: Fedora
Component: sddm
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Neal Gompa
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-21 13:05 UTC by Karel Volný
Modified: 2022-04-04 15:40 UTC (History)
19 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-04-04 15:40:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Karel Volný 2022-03-21 13:05:03 UTC
Description of problem:
A minute or two after loging into graphical environment, my system hangs.

The concrete behaviour is:

1) If I log into default KDE session, after a while the screen freezes, there is no response to mouse or keyboard - although the keyboard is not completely dead, the sysrq key combos work (after enabling sysrq via configfile in /etc/sysctl.d/ of course).

2) If I log into X11 KDE session, after a while the screen goes black. The keyboard responds somehow - pressing e.g. capslock changes the capslock light state (it does not happen in the above case), but I cannot switch to another (text) console or whatever. (Sysrq works too, of course.)

3) If I do not log into graphical environment via sddm, but rather switch to text console and use `startx`, the graphical KDE session starts and keeps running  without any problem.

Looking into logs just before the hang, it is highly suspicious that it says it is starting session while a session is started already

bře 21 10:21:26 kvolny sddm-helper[4439]: Starting X11 session: "/usr/bin/X -nolisten tcp -background none -seat seat0 -noreset -keeptty -novtswitch -verbose 3" "/usr/bin/sddm-greeter --socket /tmp/sddm--iGfpta --theme /usr/share/sddm/themes/01-breeze-fedora"

Comment 2 P D 2022-03-24 20:08:40 UTC
This happens every other boot for me. Fedora 36 KDE

Comment 3 Vasiliy Glazov 2022-03-25 12:32:36 UTC
I have the same problem.

Comment 4 Vasiliy Glazov 2022-03-31 09:19:55 UTC
New information.
I can connect to hanged system via ssh. See that kwin_wayland load one core to 100%.

Comment 5 Jan Grulich 2022-03-31 12:22:57 UTC
I can reproduce. I downgraded to latest stable SDDM (sddm-0.19.0-19.fc36.x86_64) and the problem doesn't seem to occur. There was also a black screen delay for like 10s when I typed my password and clicked to log in and only then I could see Plasma loading, this doesn't happen with the stable version.

Comment 6 Fedora Blocker Bugs Application 2022-04-01 17:02:26 UTC
Proposed as a Blocker for 36-final by Fedora user vascom using the blocker tracking app because:

 KDE spin crashes because of non stable sddm version.

This made F36 KDE fully unfunctional.

Workaround now is downgrade sddm to last stable version.

Comment 7 Xose Vazquez Perez 2022-04-01 17:27:44 UTC
Does mesa-22.0.1-1.fc36 (updates-testing) fix totally/partially this issue ?

Comment 8 Vasiliy Glazov 2022-04-01 17:39:35 UTC
With mesa-22.0.1 still the same problems.

Comment 9 Adam Williamson 2022-04-01 18:30:43 UTC
Can folks affected by this report the output of:

rpm -qa | grep sddm

please? Thanks!

Comment 10 Vasiliy Glazov 2022-04-01 18:42:28 UTC
sddm-breeze-5.24.3-3.fc36.noarch
sddm-kcm-5.24.3-1.fc36.x86_64
sddm-0.19.0^git20220228.c257a40-4.fc36.x86_64
sddm-x11-0.19.0^git20220228.c257a40-4.fc36.noarch
sddm-themes-0.19.0^git20220228.c257a40-4.fc36.noarch

Comment 11 Adam Williamson 2022-04-01 19:06:11 UTC
If you replace sddm-x11 with sddm-wayland-generic (you may need to use dnf swap, not sure) does the problem go away?

Comment 12 Vasiliy Glazov 2022-04-01 19:44:40 UTC
After that I see just black screen instead of sddm.
But if I switch to Ctrl+Alt+F3 I can login to console. At top sddm-greeter use ~1% of one core and it on the top.

Comment 13 Sander de Leeuw 2022-04-02 19:41:14 UTC
Hi,

I can confirm this issue as well.

Upgraded my Fedora 35 Kinoite installation to version 36-beta, by running `rpm-ostree rebase` and rebooting the system.

After entering my username and password, it took much (about 15s) longer before the desktop appeared, compared to Fedora 35.
Then after 1-2 minutes, the desktop hangs and is unresponsive to my keyboard and mouse.

I was able to login my system using SSH (during this freeze), reboot and selected the previous Fedora 35 slot.
Then I ran `rpm-ostree rollback` and in Fedora 35 everything works fine again.


Kind regards,

Sander de Leeuw

Comment 14 Neal Gompa 2022-04-03 17:13:57 UTC
I've built a new git snapshot of SDDM which includes the merged version of the fix for another bug that seems like it might help here, does it help with this issue? https://koji.fedoraproject.org/koji/buildinfo?buildID=1942317

Comment 15 Vasiliy Glazov 2022-04-03 18:24:44 UTC
(In reply to Neal Gompa from comment #14)
> I've built a new git snapshot of SDDM which includes the merged version of
> the fix for another bug that seems like it might help here, does it help
> with this issue?
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1942317

It only helped half.
Hungs is absent at least for wayland session. But very long time black screen before KDE desktop show (about 30s) still present.

Comment 16 P D 2022-04-03 21:01:56 UTC
> I've built a new git snapshot of SDDM which includes the merged version of
> the fix for another bug that seems like it might help here, does it help
> with this issue?
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1942317

Before this update: 50% chance of the plasma wayland session freezing 1 minute or so after login

After this update: 99% chance of plasma wayland session crashing to the login screen 1 minute or so after login

Please just revert to the last STABLE version of sddm.

Comment 17 Neal Gompa 2022-04-03 22:17:59 UTC
Can folks try this scratch build? https://koji.fedoraproject.org/koji/taskinfo?taskID=85124690

Comment 18 P D 2022-04-03 23:20:15 UTC
That build works fine.

Comment 19 Karel Volný 2022-04-04 11:51:12 UTC
(In reply to Neal Gompa from comment #17)
> Can folks try this scratch build?
> https://koji.fedoraproject.org/koji/taskinfo?taskID=85124690

looks like this fixes the issue for me

Comment 20 Kamil Páral 2022-04-04 15:06:48 UTC
I believe this is the same bug as bug 2070130.

Comment 21 Geoffrey Marr 2022-04-04 15:40:51 UTC
Marking as a duplicate of 2070130 per discussion on asynchronous blocker discussion. [0]

If this bug is found to be a separate issue, we can reopen/repropose it.

[0] https://pagure.io/fedora-qa/blocker-review/issue/706

*** This bug has been marked as a duplicate of bug 2070130 ***


Note You need to log in before you can comment on or make changes to this bug.