https://bugs.kde.org/show_bug.cgi?id=498751

            Bug ID: 498751
           Summary: System entering suspend / standy while updating
    Classification: KDE Neon
           Product: neon
           Version: unspecified
          Platform: Neon
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: neon-b...@kde.org
          Reporter: helium...@mailbox.org
                CC: carlosd....@gmail.com, j...@jriddell.org,
                    neon-b...@kde.org
  Target Milestone: ---

SUMMARY
After updating with Discover, I shut down the system with the option to update
and shut down. My laptop restarted and at some point I closed the lid and left.
A few hours later I opened it and noticed that updates were still installing.
The update screen was stuck at 94%, the cogwheel still spinning.

I strongly suspect that closing the lid caused the system to enter suspend
mode, and suspend mode caused the update to get stuck.

STEPS TO REPRODUCE
Note that I didn't actually try to reproduce it. I fear trying again might
result in a non-booting OS.
0. Have a system with a lid (laptop, tablet with cover, ...)
1. Download updates in Discover
2. Select "install updates and shut down"
3. Close the lid
4. Wait (maybe not necessary)
5. Open the lid

OBSERVED RESULT
Installing updates is stuck

EXPECTED RESULT
Either: installing updates continues
Or: system has aleady installed updates and shut down

In my opinion the second variant is preferable. It's rather unexpected to me
that the system would even react to closing the lid while installing updates
(especially when the option I chose is clear about the system shutting down
after install is done).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon 6.2
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1

HARDWARE
Huawei Matebook 14s

ADDITIONAL INFORMATION
Related thread on discuss.kde.org:
https://discuss.kde.org/t/updating-doesnt-finish/28334

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to