The problem was first noticed when the system was given a clean installation of Debian Trixie some months ago whilst Trixie was then under development. As an issue it occurred almost 100% of the time when hibernation was engaged. Under Bookworm there was no problem at all with the same hardware configuration.
The system configuration uses a swap partition which is stored on Sata SSD. The system’s motherboard was replaced due to unrelated issues and trixie reinstalled from scratch but the locking problem has continued. After much difficulty as the system usually had to be reset after resuming it was discovered that the issue is not with the hibernation/resume but with the action of locking the system at the completion of the resume operation. At this point the locking would result in the system freezing instead. With the requirement to lock the computer after waking from sleep disabled, the use of hibernation/resume immediately regained its normal level of reliability. A second Trixie installed system has displayed the same issue although it does not freeze all the time when resuming, only occasionally. It has different hardware from the computer which is the subject of this bug report. It was thought initially the issue was the use of the hibernation option on the Lock Screen to hibernate the computer but has been now shown to be any use of hibernation in the system although the second mentioned computer seems more likely to freeze on resume if the Lock Screen hibernation function is engaged, as compared with selecting hibernation while unlocked. > On 24 Aug 2025, at 14:53, Debian Bug Tracking System <ow...@bugs.debian.org> > wrote: > > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 1111935: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1111935. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > As you requested using X-Debbugs-CC, your message was also forwarded to > patrickjrdunf...@gmail.com > (after having been given a Bug report number, if it did not have one). > > Your message has been sent to the package maintainer(s): > Debian Qt/KDE Maintainers <debian-qt-kde@lists.debian.org> > > If you wish to submit further information on this problem, please > send it to 1111...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 1111935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1111935 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems
