Weird freeze behavior at login screen

Ask Fedora
1

following the reinstall of fedora 44 i have experienced by now 3 freezes at the login screen

the freezes go form no response to buttons on the login to taking seconds to respond, the times there is no response, i had to turn pc off by the power button on the pc

all the situations happen when i updated pc nd then rebooted the pc to apply the said updates but left the pc unattended, if i enter in the kde session under my user and let it speep in case i leave it there, there is no problem, so is limited to when it reboots after a update and i dont enter into the session

it seems to be that the sleep rules do not apply on that moment and sort of chokes on itself when is on the login scren and no user was loaded

3

You may find clues in the system journal.
If you are using nvidia gpu make sure you have the rpmfusion drivers built and that they are loaded.

4

thank you, no nvidia here, just a apu, thank you for your reply, no nvidia gpu here, just a amd apu

i was trying to learn system journal, found something about journalctl but didnt found much here about anything

it sems that system should suspend when no user is loaded but system just stays there and sort of chokes on itself

5

Try this and see what it finds after a freeze:

sudo journalctl -b 0 -g amdgpu -p warning

That is scanning the journal for AMDGPU logs with severity warning or above since boot.

6

this is what it found

Aug 04 21:14:21 fedora kernel: amdgpu 0000:06:00.0: [drm] Failed to setup vendor infoframe on connector HDMI-

i have not had any crash because the pc was left sleeping, no reboot after updating leaving it unatended and without session open

7

When you see the bug again check the journal again.
If you have to reboot to get control then this is the command to see the journal from the previous boot.

sudo journalctl -b -1 -g amdgpu -p warning
8

will do, this journal, is for how many days? daily? this installation is from the weekend, i had the situation two times in sunday and monday but register i saw yesterday didnt show much, like 10 items and i had no problems after those two

9

The journal keeps logs for as long as there is disk space for them, then removes the oldest logs. There is are limits on the amount of disk space used.

I checked a few of my systems and my desktop has logs going back 12 months. My router has logs going back about 3 months (being on the internet I see a lot of logs attacking the system).

The details on are in man man journald.conf if you are interested.

10

then, the problem should be there, if it is gpu related, i personally dont think it is

i was looking at errors, fortunately it shows on yellow, blue and red things in terms of seriousness, it is a very long list, only saw something that wasnt even for gpu, it said that it had problems with clockspeed, but it didnt said for what, gpu, cpu? it was yellow for kernel so

the journal is very detailed but, i dont see anything i would say it is the problem

Aug 01 18:57:23 fedora kwin_wayland[4240]: Applying output configuration failed!

that one does not correspond to the time when the event happened

i do find this after one of the reboots to update the august 1

Aug 01 19:20:19 fedora plasma-discover[19867]: qrc:/qt/qml/org/kde/discover/qml/DiscoverDrawer.qml:246: TypeError: Passing incompatible arguments to C++ functio>
Aug 01 19:20:19 fedora plasma-discover[19867]: “Could not convert argument 0 from undefined to QVariantList”
Aug 01 19:20:19 fedora plasma-discover[19867]: “expression for enabled@qrc:/qt/qml/org/kde/discover/qml/DiscoverDrawer.qml:246”
Aug 01 19:20:19 fedora plasma-discover[19867]: “clear@file:///usr/lib64/qt6/qml/org/kde/kirigami/controls/PageRow.qml:527”
Aug 01 19:20:19 fedora plasma-discover[19867]: “expression for onCurrentTopLevelChanged@qrc:/qt/qml/org/kde/discover/qml/DiscoverWindow.qml:491”
Aug 01 19:20:19 fedora plasma-discover[19867]: “expression for onTriggered@qrc:/qt/qml/org/kde/discover/qml/TopLevelPageData.qml:25”

it repeats like 200 times on the log with same or similar lines

will try to reproduce the problem as you said before, thank you

11

Do you use discover to install or update software?
If you do not you could consider removing it and its dependencies.

12

i learned not long ago to use dnf, so of course, i use discover, i dont like console commands that i forget almost inmediatelly so i prefer a gui

13

a update, kde 6.7.4 came so i did a update, but on purpose turned off keyboard and mouse so pc didnt woke up, pc finished updates, and sat in login, doing nothing, for hours, no keyboard or mouse activity could wake it up because both were turned off, wireless devices

pc never applied rules to sleep or anything, it sat there

so there has been a change, but it needs to go to sleep, because it is wasting electricity, that is the problem, instead of doing what is supposed to, it is not going to sleep by itself