F31 hangs often

dmw73 · December 2, 2019, 6:39pm

Hi,

Desperate F31 user here. My F31 workstation has been hanging randomly since I upgraded from F30 to F31. Here is the basic system info:

Operating System: Fedora 31
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.61.0
Qt Version: 5.12.5
Kernel Version: 5.3.9-300.fc31.x86_64
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-4590 CPU @ 3.30GHz
Memory: 7.7 GiB of RAM

When I say it is “hanging,” I mean it goes completely unresponsive. Mouse cursor is frozen and keyboard is useless. I have to perform a hard reboot to recover. This has been happening fairly often, several times per day. At first I thought it was related to Firefox, but it has been happening apart from Firefox even being open.

I have been using Fedora for over a decade, and never had any such issues up until the past couple months. I would hate to abandon it for another distro, but it has reached the point of unusable, and I have not received help from support forums I’ve posted to.

After a reboot, I’ve looked through journalctl to see what was going on, and nothing is standing out as concerning. Here is the preceding minute before a hang event:

Dec 02 12:48:55 shamrock audit[2317]: CRED_DISP pid=2317 uid=0 auid=0 ses=4 subj=system_u:system_r:local_login_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/usr/bin/login" hostname=shamrock addr=? terminal=tty2 res=success'
Dec 02 12:48:55 shamrock login[2317]: pam_unix(login:session): session closed for user root
Dec 02 12:48:55 shamrock audit[2317]: USER_END pid=2317 uid=0 auid=0 ses=4 subj=system_u:system_r:local_login_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_selinux,pam_loginuid,pam_console,pam_selinux,pam_namespace,pam_keyinit,pam_keyinit,pam_limits,pam>
Dec 02 12:48:55 shamrock systemd[1]: getty@tty2.service: Succeeded.
Dec 02 12:48:55 shamrock audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=getty@tty2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 02 12:48:55 shamrock systemd[1]: session-4.scope: Succeeded.
Dec 02 12:48:55 shamrock systemd[1]: getty@tty2.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Dec 02 12:48:55 shamrock systemd-logind[869]: Session 4 logged out. Waiting for processes to exit.
Dec 02 12:48:55 shamrock systemd[1]: getty@tty2.service: Scheduled restart job, restart counter is at 1.
Dec 02 12:48:55 shamrock audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=getty@tty2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 02 12:48:55 shamrock audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=getty@tty2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 02 12:48:55 shamrock systemd[1]: Stopped Getty on tty2.
Dec 02 12:48:55 shamrock systemd[1]: Started Getty on tty2.
Dec 02 12:48:55 shamrock audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=getty@tty2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 02 12:48:55 shamrock systemd-logind[869]: Removed session 4.
Dec 02 12:48:55 shamrock sendmail[2416]: xB2HmtXV002416: from=<shamrock@wickersham.info>, size=251, class=0, nrcpts=1, msgid=<201912021748.xB2HmtXV002416@localhost.localdomain>, proto=SMTP, daemon=MTA, relay=localhost [127.0.0.1]
Dec 02 12:48:55 shamrock sendmail[2418]: STARTTLS=client, relay=smtp.gmail.com., version=TLSv1.3, verify=FAIL, cipher=TLS_AES_256_GCM_SHA384, bits=256/256
Dec 02 12:48:55 shamrock sendmail[2418]: ldapdb_canonuser_plug_init() failed in sasl_canonuser_add_plugin(): invalid parameter supplied
Dec 02 12:48:55 shamrock sendmail[2418]: _sasl_plugin_load failed on sasl_canonuser_init for plugin: ldapdb
Dec 02 12:48:56 shamrock sendmail[2418]: xB2HmtXV002416: to=<homesecurity4910@gmail.com>, delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=120251, relay=smtp.gmail.com. [108.177.9.109], dsn=2.0.0, stat=Sent (OK  1575308936 m133sm24087oia.29 - gsmtp)
Dec 02 12:48:56 shamrock sendmail[2418]: DIGEST-MD5 common mech free
Dec 02 12:48:56 shamrock sendmail[2418]: DIGEST-MD5 common mech free
Dec 02 12:48:57 shamrock org_kde_powerdevil[1729]: powerdevil: The profile  "AC" tried to activate "DimDisplay" a non-existent action. This is usually due to an installation problem, a configuration problem, or because the action is not supported
Dec 02 12:49:05 shamrock systemd[1]: Stopping User Manager for UID 0...
Dec 02 12:49:05 shamrock systemd[2339]: Stopped target Main User Target.
Dec 02 12:49:05 shamrock systemd[2339]: Stopped target Basic System.
Dec 02 12:49:05 shamrock systemd[2339]: Stopped target Paths.
Dec 02 12:49:05 shamrock systemd[2339]: Stopped target Sockets.
Dec 02 12:49:05 shamrock systemd[2339]: Stopped target Timers.
Dec 02 12:49:05 shamrock systemd[2339]: dbus.socket: Succeeded.
Dec 02 12:49:05 shamrock systemd[2339]: Closed D-Bus User Message Bus Socket.
Dec 02 12:49:05 shamrock systemd[2339]: pipewire.socket: Succeeded.
Dec 02 12:49:05 shamrock systemd[2339]: Closed Multimedia System.
Dec 02 12:49:05 shamrock systemd[2339]: Reached target Shutdown.
Dec 02 12:49:05 shamrock systemd[2339]: systemd-exit.service: Succeeded.
Dec 02 12:49:05 shamrock systemd[2339]: Started Exit the Session.
Dec 02 12:49:05 shamrock systemd[2339]: Reached target Exit the Session.
Dec 02 12:49:05 shamrock systemd[1]: user@0.service: Succeeded.
Dec 02 12:49:05 shamrock systemd[1]: Stopped User Manager for UID 0.
Dec 02 12:49:05 shamrock audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=user@0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 02 12:49:05 shamrock systemd[1]: Stopping User Runtime Directory /run/user/0...
Dec 02 12:49:05 shamrock systemd[1223]: run-user-0.mount: Succeeded.
Dec 02 12:49:05 shamrock systemd[1]: run-user-0.mount: Succeeded.
Dec 02 12:49:05 shamrock systemd[1]: user-runtime-dir@0.service: Succeeded.
Dec 02 12:49:05 shamrock systemd[1]: Stopped User Runtime Directory /run/user/0.
Dec 02 12:49:05 shamrock audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=user-runtime-dir@0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 02 12:49:05 shamrock systemd[1]: Removed slice User Slice of UID 0.
Dec 02 12:49:27 shamrock systemd-logind[869]: Power key pressed.
Dec 02 12:49:39 shamrock systemd-logind[869]: Power key pressed.
-- Reboot --

Please let me know what else to look for and what other troubleshooting steps to perform.

Thanks!

jritter · December 2, 2019, 8:36pm

Hi dmw73,

To me the log looks like the system is still responsive in the background, probably the display server is stuck somehow.

Are you using wayland or xorg classic? What kind of graphics chip do you have? And when the system is in the hung state, it would be nice to know whether you can still ping the system or log into the system using SSH.

I have seen a similar thing happening on my rather old but trusty Lenovo W530 with a nvidia graphics chip when running GNOME on wayland and the nouveau driver. The solution was a fallback to xorg, since then the system worked reliably again.

Hope that helps!

Regards, Juerg

jritter · December 2, 2019, 8:39pm

Oh, I forgot to mention: The fallback can be done by selecting a different session in the graphical login screen. I’m a GNOME user, and I have a choice between GNOME and GNOME classical (xorg). I suppose for KDE it would work in a similar way.

Cheers, Juerg

dmw73 · December 3, 2019, 12:54pm

Hello Juerg,

Thanks for helping troubleshoot this.

At this moment, the local F31 graphical session is hung, so I proceeded to login remotely via ssh. The system was running fine in the ssh CLI, but it hung after about 5 minutes. I then logged in a 2nd time with ssh and it continued to run for another 5 minutes before hanging.

I am running xorg. I recall it was wayland, but I had changed it to see if it would make a difference.
The graphics adapter:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM]

The journalctl logs do not show any events around the time of the ssh sessions hanging. There are a bunch of errors from the time when I attempted to login from the KDE local session. Here are some snippets:

Dec 03 07:16:59 shamrock ksmserver[9863]: Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")
Dec 03 07:16:59 shamrock kaccess[9834]: Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")
Dec 03 07:16:59 shamrock kdeinit5[9828]: Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")

[snip]

Dec 03 07:19:14 shamrock systemd[1]: dbus-:1.1-org.kde.powerdevil.discretegpuhelper@2.service: Succeeded.
Dec 03 07:19:14 shamrock audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-:1.1-org.kde.powerdevil.discretegpuhelper@2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 03 07:19:15 shamrock systemd[1]: dbus-:1.1-org.kde.powerdevil.backlighthelper@2.service: Succeeded.
Dec 03 07:19:15 shamrock audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-:1.1-org.kde.powerdevil.backlighthelper@2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 03 07:19:29 shamrock kactivitymanagerd[10031]: Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")
Dec 03 07:19:29 shamrock kwin_x11[9878]: Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")
Dec 03 07:19:29 shamrock korgac[9969]: org.kde.knotifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP
Dec 03 07:19:29 shamrock plasmashell[9886]: Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")
Dec 03 07:19:29 shamrock krunner[9883]: Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")
Dec 03 07:19:29 shamrock kdeinit5[9828]: kf5.kded: found kded module "apperd" by prepending 'kded_' to the library path, please fix your metadata.
Dec 03 07:19:30 shamrock org_kde_powerdevil[9984]: Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")
Dec 03 07:19:54 shamrock plasmashell[9886]: kf5.karchive: bzDecompress returned -5

[snip]

Dec 03 07:22:50 shamrock org_kde_powerdevil[9984]: org.kde.bluez: Cannot open /dev/rfkill for reading!
Dec 03 07:22:50 shamrock org_kde_powerdevil[9984]: powerdevil: The profile  "AC" tried to activate "DimDisplay" a non-existent action. This is usually due to an installation problem, a configuration problem, or because the action is not supported
Dec 03 07:22:50 shamrock org_kde_powerdevil[9984]: powerdevil: Handle button events action could not check for screen configuration
Dec 03 07:22:50 shamrock org_kde_powerdevil[9984]: KActivities: FATAL ERROR: Failed to contact the activity manager daemon

[snip]

Dec 03 07:24:54 shamrock plasmashell[9886]: invalid metadata "/usr/lib64/qt5/plugins/kcm_kget_mirrorsearchfactory.so"
Dec 03 07:24:54 shamrock plasmashell[9886]: invalid metadata "/usr/lib64/qt5/plugins/opendocumentthumbnail.so"
Dec 03 07:24:54 shamrock plasmashell[9886]: invalid metadata "/usr/lib64/qt5/plugins/krunner_pimcontacts.so"
Dec 03 07:24:54 shamrock plasmashell[9886]: invalid metadata "/usr/lib64/qt5/plugins/ktpaccountskcm_plugin_haze.so"
Dec 03 07:24:54 shamrock plasmashell[9886]: invalid metadata "/usr/lib64/qt5/plugins/ktptextui_message_filter_highlight.so"
Dec 03 07:24:54 shamrock plasmashell[9886]: invalid metadata "/usr/lib64/qt5/plugins/kcm_kget_metalinkfactory.so"
Dec 03 07:24:54 shamrock plasmashell[9886]: org.kde.plasmaquick: Applet preload policy set to 1
Dec 03 07:27:49 shamrock plasmashell[9886]: kf5.karchive: bzDecompress returned -5
Dec 03 07:28:39 shamrock plasmashell[9886]: trying to show an empty dialog
Dec 03 07:28:39 shamrock plasmashell[9886]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height"
Dec 03 07:28:39 shamrock plasmashell[9886]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height"
Dec 03 07:28:39 shamrock plasmashell[9886]: trying to show an empty dialog

I don’t have Gnome installed, and I don’t believe I have any other desktop environment available other than KDE. I could try to find something lightweight and install it to see if it runs or not.

In the mean time, any other suggestions would be greatly appreciated.

Thanks,
DMW

dmw73 · December 3, 2019, 1:17pm

Something else I noticed that I did not expect.

Loginctl shows four sessions:

[root@shamrock user2]# loginctl list-sessions
SESSION  UID USER     SEAT  TTY
     17 1000 user1 seat0
      2 1002 user2    seat0
     89 1002 user2          pts/0
     c4  982 lightdm  seat0

4 sessions listed.

I am logged in via ssh as user2. I do not expect to see user1 or user2 with seat0 sessions; they should have been closed. Is it possible that the KDE logout process is not completing?

[root@shamrock user2]# who
user2    pts/0        2019-12-03 08:05 (192.168.8.20)

[root@shamrock user2]# ps -ef | grep -i user1
avahi     851       1  0 Dec02 ?        00:00:00 avahi-daemon: running [shamrock.local]
user1    4311       1  0 Dec02 ?        00:00:00 /usr/libexec/geoclue-2.0/demos/agent
user1    5693       1  0 Dec02 ?        00:00:00 /usr/sbin/firebird

Also notice above that geoclue and firebird are running as user1, even though user1 is not logged in. Is this happening in error? I did not intentionally install geoclue or firebird, I don’t know why they are there.

jritter · December 3, 2019, 8:45pm

Hi dwm73,

Interesting that you are still able to log in after these hangs. As I am a GNOME user, I am not very familiar with the processes generating the logs you posted. But I guess the following aspect might be interesting:

When you SSH into the system after the hangs, do you see any performance issues like high CPU load or high load average (>4)? Or any other I/O issues? Try run the following commands as root when the hang occurs:

# uptime
# sar 1 10

sar is part of the sysstat package, you might have to install it:

# dnf install sysstat

Regarding the user processes: Do you see those after you logged out user1 regularly, or after a hang occurred?

And another thing: After the second hang, was the system frozen for good, or did it again sort of recover?

Regards,
Juerg