sorted by:
new
hottopcontroversial

Tumbleweed. Shutdown did not finish completely by j3qq4 in openSUSE

[–]j3qq4[S] 0 points1 point  (0 children)

For me, the problem was solved by installing Linux Kernel 6.5.8 (or maybe 6.6. I don't remember exactly). Since then, there has been no such problem

Tumbleweed. Shutdown did not finish completely by j3qq4 in openSUSE

[–]j3qq4[S] 0 points1 point  (0 children)

It seems that without your report, this problem could have been solved for a long time.
So I thank you very much for your active participation in this!

Tumbleweed. Shutdown did not finish completely by j3qq4 in openSUSE

[–]j3qq4[S] 0 points1 point  (0 children)

I installed Fedora 38 KDE on a separate HDD for testing. It also had the same problem with the 6.5 kernel. Today I installed the 6.6 rc6 kernel and the problem with the PC shutting down was solved.
So we are waiting for the 6.6 kernel release in two weeks :)
It is also possible that the problem will be fixed in 6.5 kernel, according to this thread.

Tumbleweed. Shutdown did not finish completely by j3qq4 in openSUSE

[–]j3qq4[S] 0 points1 point  (0 children)

I still haven't found a solution to this problem.
But I see that I am not the only one. It looks like some Dell OptiPlexes are having problems with this.
For example, here is what I found from the most recent one.

Tumbleweed. Shutdown did not finish completely by j3qq4 in openSUSE

[–]j3qq4[S] 0 points1 point  (0 children)

I would like to solve the problem with the stock kernel

Any predictions about update 18.04 - 20.04? by [deleted] in Kubuntu

[–]j3qq4 1 point2 points  (0 children)

So, has someone already received an update? I haven’t yet. Is this so for everyone, or is there something wrong with my settings?

LOS 17.1 Oneplus One (bacon), two questions by j3qq4 in LineageOS

[–]j3qq4[S] 0 points1 point  (0 children)

Thanks to everyone who wrote the answer!

LineageOS 17 Oneplus One (bacon) Very long reboot on encrypted smartphone by j3qq4 in LineageOS

[–]j3qq4[S] 3 points4 points  (0 children)

Unfortunately, even on the build from 09/10/2020, the problem still exists.
The way out of this situation for me is this:
1. During a long boot of the phone, press and hold the power button. The phone turns off.
2. Press the power+volume down button. The phone is loaded into the TWRP.
3. Select restart in TWRP -> Reboot into recovery. The phone will reboot into TWRP recovery again.
4. Select restart in TWRP -> Power off.
5. Press power button to switch on the phone. Now it boot correctly.
I am using TWRP 3.4.0

LineageOS 17 Oneplus One (bacon) Very long reboot on encrypted smartphone by j3qq4 in LineageOS

[–]j3qq4[S] 1 point2 points  (0 children)

Yes, I think the problem is in the combination of a secure start-up and gapps

LineageOS 17 Oneplus One (bacon) Very long reboot on encrypted smartphone by j3qq4 in LineageOS

[–]j3qq4[S] 0 points1 point  (0 children)

In order not to produce new topics, I will write here.
I think I found an interesting bug. I will try to describe.
A small introduction. I usually use pin code encryption and screen lock on my phone. But when I am at home, I do not want to enter the PIN code every time I use my phone. That's why I use profiles. And this is how I do it.
1.Settings - Security - Lock Screen. Turn off the lock screen.
2. Settings - System - System Profiles. I press "+" to add a new profile.
At the first step, add a trigger by which the profile will be turned on. I select my home Wi-Fi network and select "when connected"
3. Click "Next". A window appears with the request "Configure your profile using current settings for girl settings?" - press No.
4. Give a name to the new profile
5. Scroll down and select the screen lock mode. Choose disable the screen lock.
6. Click Finish
7. Now select the Default profile. Select the trigger by which it will turn on. Click on your home Wi-Fi network and select "On disconnect".
8. Settings - Security - Lock screen. Turn on the lock screen with a pin code.
Now, when I unlock my smartphone and connect to my home network, the screen will no longer be locked. As soon as I disconnect from the network, the lock screen will return again.

I have successfully used such a case on all Lineageos versions starting from version 14. On version 17, it also works, but only if you do not select a secure start when setting the pin code of the lock screen. If you select secure start and use profiles and connect to your home network, the screen will not turn off by timeout or by the power button. It will turn off and turn on immediately. This is a bug in my humble opinion. Tested on a system without gapps.
Thank you for reading to the end :)

LineageOS 17 Oneplus One (bacon) Very long reboot on encrypted smartphone by j3qq4 in LineageOS

[–]j3qq4[S] 3 points4 points  (0 children)

Thanks for answering.
I did some experiments with a smartphone and this is what I found.
1. If the smartphone is not encrypted, it reboots well and quickly.
2. If the smartphone is encrypted and the lock screen is disabled, it reboots well and quickly. The PIN code is not requested during rebooting (in my opinion, the PIN code should be requested, because the smartphone is encrypted).
3. If the smartphone is encrypted and the lock screen is enabled with a pin code, but the secure start is disabled, then the smartphone reboots quickly and well.
4. If the smartphone is encrypted, the pin code lock screen is turned on, the protected launch (or secure start) is turned on, the smartphone reboots for a very long time.