Cannot shutdown or reboot properly. Have to power down manually

Ask Fedora
, , ,
1

Hi everyone.

Just reaching out with the hope that somebody is able to assist me with an issue I’ve been experiencing on my new installation.

The problem: Basically, I cannot shutdown or restart my laptop properly. When I select either option it presents a black screen with the fedora logo and then hangs indefinitely. I end up having to manually power down the device.

The device is a 2014 Apple MacBook Air (intel). I have installed Fedora 38 KDE Plasma.

Any help would be appreciated. If there are any commands I can run to help troubleshoot please let me know.

Thank you :slight_smile:
spec

2

These “fedora logo screens” are the “beautiful” modes.

If you press Esc you get logs, please send these.

Or use journalctl -b -1 -r --priority err which will display the logs that are error or higher, from last boot, in reverse

3

Hi @boredsquirrel

I a pleasant twist, since posting this message my laptop has started behaving! I’m not sure why it’s working all of a sudden but nonetheless I have run the above command which outputs the following:

Mar 11 19:52:39 vsblinux dbus-broker-launch[907]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Mar 11 19:52:39 vsblinux dbus-broker-launch[907]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Mar 11 19:52:39 vsblinux dbus-broker-launch[907]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Mar 11 19:52:39 vsblinux dbus-broker-launch[907]: Activation request for 'org.bluez' failed.
Mar 11 19:52:39 vsblinux dbus-broker-launch[907]: Activation request for 'org.bluez' failed.
Mar 11 19:44:30 vsblinux wpa_supplicant[1274]: bgscan simple: Failed to enable signal strength monitoring
Mar 11 19:44:26 vsblinux sddm-helper[1532]: gkr-pam: unable to locate daemon control file
Mar 11 19:43:12 vsblinux systemd-vconsole-setup[458]: /usr/bin/setfont failed with exit status 71.
Mar 11 19:43:11 vsblinux systemd-vconsole-setup[264]: /usr/bin/setfont failed with exit status 71.
~
~
4

Sorry, I think I spoke too soon! The issue is back. I’ve run the command again and here is the output:

vazsingh@vsblinux:~$ journalctl -b -1 -r --priority err
Mar 11 21:18:40 vsblinux systemd[1]: Failed unmounting home.mount - /home.
Mar 11 21:18:40 vsblinux dbus-broker-launch[905]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Mar 11 21:18:40 vsblinux dbus-broker-launch[905]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Mar 11 21:18:40 vsblinux dbus-broker-launch[905]: Activation request for 'org.bluez' failed.
Mar 11 21:18:39 vsblinux dbus-broker-launch[905]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Mar 11 21:18:39 vsblinux dbus-broker-launch[905]: Activation request for 'org.bluez' failed.
Mar 11 21:18:39 vsblinux akonadiserver[2561]: org.kde.pim.akonadiserver: Control process died, exiting!
Mar 11 21:16:42 vsblinux wpa_supplicant[1274]: bgscan simple: Failed to enable signal strength monitoring
Mar 11 21:15:23 vsblinux abrt-notification[6937]: [🡕] System encountered a non-fatal error in __die()
Mar 11 21:15:20 vsblinux kernel: #PF: error_code(0x0000) - not-present page
Mar 11 21:15:20 vsblinux kernel: #PF: supervisor read access in kernel mode
Mar 11 21:15:20 vsblinux kernel: BUG: kernel NULL pointer dereference, address: 0000000000000020
Mar 11 20:54:33 vsblinux virtqemud[5753]: End of file while reading data: Input/output error
Mar 11 19:53:20 vsblinux wpa_supplicant[1274]: bgscan simple: Failed to enable signal strength monitoring
Mar 11 19:53:16 vsblinux sddm-helper[1527]: gkr-pam: unable to locate daemon control file
Mar 11 19:52:52 vsblinux systemd-vconsole-setup[469]: /usr/bin/setfont failed with exit status 71.
Mar 11 19:52:51 vsblinux systemd-vconsole-setup[263]: /usr/bin/setfont failed with exit status 71.
vazsingh@vsblinux:~$

Thank you

5

Hi Vaz, Fedora Asahi Remix should provide stability for your Mac. I would add tag Asahi Linux for help because they know known issues.

6

Hi Hank,

Thanks for your reply. For Fedora Asahi Remix does it matter that my Mac is an old Intel chip one and not one of the newer M1 or M2 silicon chips?

7

I must confess I overlooked the hardware requirements. Asahi remix runs on Apple M-series systems.

8

Hi all, it’s been a few days and I wanted to share with the community that for me the issue seems to have disappeared after updating the kernel to version 6.7.9-200.

2 Likes
9

Nice to hear that the kernel did the trick!