Today, yay -Syyu traditionally launched. Updated. After reboot, after the GRUB screen, the system goes to the Endeavour menu, but there is only one item in this menu - the selection of BTRFS snapshots.
Uploaded to the snapshot before the update, everything seems to be fine.
But now the system is not shutting down.
He stops at this point for a few minutes
Then it stops at these points and nothing else happens…
Can this be fixed?
Hi. Please rename your topic to something like:
Why you updating using -Syyu
Use -Syu and if using yay then -Syu is not needed as it defaults to that by just using yay.
[sam@endeavouros ~]$ yay
[sudo] password for sam:
:: Synchronizing package databases...
endeavouros is up to date
core is up to date
extra 8.3 MiB 2.09 MiB/s 00:04 [--------------------------------------------------------------] 100%
multilib 139.9 KiB 157 KiB/s 00:01 [--------------------------------------------------------------] 100%
:: Searching AUR for updates...
:: Searching databases for updates...
there is nothing to do
[sam@endeavouros ~]$
Good question… And the answer is I don’t know. I’ve been doing this all the time I’ve been using Endeavour.
But my question is, how do I fix the problem of not shutting down the system?
Same problem here as well. This started after the last update
I updated properly using sudo pacman - Syu. So i don’t think the command you used to update is the problem
Have you tried sudo poweroff and systemctl poweroff within terminal?
Edit: journalctl -b -1
No changes, everything is as described in the title message
I have two of them in my system
/usr/share/bash-completion/completions
/usr/bin
Which one exactly? And what exactly should be done?
eos has there own eos-log-tool in the menu and can be uploaded here so the folks that can read the logs.
I searched for this issue a lot and finally got my laptop working by downgrading the packages :
linuxlinux-headersTo downgrade you can use the downgrade utility
Use the following command:
sudo downgrade linux linux-headers
Note: You may not be able run
sudocommand. It was happening with me.
Hence simply force shutdown your device. Then after restarting, do these steps quickly then restart again
PS:
At first i thought it was a systemd issue. So i tried downgrading it but everything was still the same
Then i thought it was maybe the stable kernel update issue so i tried to boot into the latest lts kernel but the issue persists there as well
Then i read this recent issue (https://gitlab.archlinux.org/archlinux/packaging/packages/broadcom-wl-dkms/-/issues/1) which states that it has something to do with Network Adapter. Hence downgrading to 6.6.4 will work
My Wifi Card is MT7921
If you resolve this issue, then please confirm whether you have the wifi card of the similar series (Ex: MT7922)
What points should be noted in the eos-log-tool?
Yes, I am a simple user 
Who first encountered a problem in Endeavour 
near same . i downgrade 6.6.3 ( never updated to 6.4 ) difference i need enable NetworkManager again . seem Broadcom-wl-dkms issue like you post
EDit … on same device as in your link
from " https://lore.kernel.org/all/87sf4belmm.fsf@turtle.gmx.de/ "
After upgrading to 6.6.5, I noticed that my laptop would hang on
shutdown and bisected that problem to this patch. Reverting it makes
the problem go away.
More specifically, NetworkManager and wpa_supplicant processes are hung.
This can also be triggered by "systemctl stop NetworkManager.service"
which does not complete and brings these two processes into a state of
uninterruptible sleep.
I also tried 6.1 and mainline, and could reproduce the hang in 6.1.66
but _not_ in 6.7-rc4, so maybe some patch from Linus' tree needs to be
applied to the stable branches.
I rolled back a couple of days ago, before the update (6.6.4) - everything works correctly. Most likely there is indeed a bug in 6.6.5
I’m having the same issue. . . . shutdown stops at wpasupplicant and networks during terminal line shutdown. . . just stalls and starts counting up the time in minutes. I have to just turn off the power. This is also using the newest kernel 6.6.5-arch 1-1. Didn’t happen with previous updated kernel.
Rich 
I am increasingly liking the option of installing the lts kernel.
At least for those users who just need the computer to work
I wonder how long each new kernel iteration takes before coming out. . . they seem to be coming out quite frequently. . . any thoughts on this?
Rich;)
boot and xorg
I would try the lts first, if it still happens then the logs will be important to find the problem.
I think something else is going on. . .I installed the LTS 6.1.66 kernel and I’m getting the same results during shutdown. . . System stalls in terminal at lines WPA supplicant and Networks and starts counting up the time . . . I wait for about 2 to 3 minutes and then have to shut down via power button. . . .
Rich;) I used AKM to install LTS and remove 6.6.5-arch 1-1. . .it worked perfectly doing this.
I excluded linux and linux-headers from updates, updating all the others - everything is fine.
I think it’s worth delaying the kernel update…
The LTS kernel is a really good back up to have. 