By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 2639

Summary: screen-saver unlock dialog freezing GUI?
Product: TDE Reporter: ThoMaus <thomas.maus>
Component: tdebaseAssignee: Timothy Pearson <kb9vqf>
Status: RESOLVED FIXED    
Severity: major CC: bugwatch, deloptes, michele.calgaro, slavek.banko, thomas.maus
Priority: P5    
Version: R14.1.x [Trinity]   
Hardware: Other   
OS: Linux   
Compiler Version: TDE Version String:
Application Version: Application Name:
Bug Depends on:    
Bug Blocks: 2696    

Description ThoMaus 2016-04-19 13:30:24 CDT
I've experienced the following 2 times, and so far are not able to reproduce reliably:

If I return when the screen-saver/-lock just kicks in early (see bug 2638), and then interact (hit shift or move the mouse), the GUI freezes completely and does not react in any way to mouse or keyboard actions (even not to CTRL+ALT+DEL or CTRL+ALT+BS). Only resolution: reboot (this machine had no SSHD running, so I couldn't check deeper).

(Wild guess: a problem in focus grabbing???)


I assume this to be a TDE problems (and not a RAM problem), because no other window manager/screen locker tested showed similar problems, and the system RAM is occasionally massively exercised without any problems. (and RAM tests show no problem either, of course).
Comment 1 Slávek Banko 2016-04-19 13:37:30 CDT
Switch to a text console (Ctrl+Alt+F1) also does not work?

Note: Ctrl+Alt+Backspace is in Xorg disabled by default for a long time.
Comment 2 ThoMaus 2016-04-20 04:55:28 CDT
(In reply to Slávek Banko from comment #1)
> Switch to a text console (Ctrl+Alt+F1) also does not work?

Didn't work (and neither Ctrl+Alt+F2, ...+F3, ...).
Nor did Ctrl+Alt+Esc switch to a kill-cursor (in the hope of killing the potentially focus grabbing application).

Keyboard (internal notebook keyboard -- so no cabling issues) and mouse (both touchpad and USB mouse) very completely "dead": no mouse movements, no key entry into password field. As written originally: no reaction at all! 

> Note: Ctrl+Alt+Backspace is in Xorg disabled by default for a long time.

Not here.
Comment 3 Michele Calgaro 2016-04-21 02:02:43 CDT
Sounds like a kernel bug to me.
I encountered a similar situation 3 years ago. I was running 3.2.0 on Debian and there was a bug in the intel graphic card driver in the kernel. From time to time the computer would freeze completely: no mouse, no keyboard, nothing.

Thomas, does the "Raising Elephants Is So Utterly Boring" work?
Comment 4 ThoMaus 2016-06-12 12:24:57 CDT
(In reply to Michele Calgaro from comment #3)
> Sounds like a kernel bug to me.

I doubt this on the following grounds:

* it is not happening at all with any of the other GUIs I'm testing as substitute for KDE -- which covers at least 3 to 4 times the running time of TDE.

* it just recently happened with TDE when executing '/opt/trinity/bin/konqueror', just when the window was painted

> I encountered a similar situation 3 years ago. I was running 3.2.0 on Debian
> and there was a bug in the intel graphic card driver in the kernel. From
> time to time the computer would freeze completely: no mouse, no keyboard,
> nothing.

Sounds like what I experience -- but only under TDE. Perhaps some TDE-specific way of graphic lib calls?

> Thomas, does the "Raising Elephants Is So Utterly Boring" work?

Should it work?
(SysRq is normally deactivated on my traveling machines (like the one I test TDE on), as the disks are encrypted and I don't want to allow peeking into memory and retrieving the disk keys via SysRq!)
Comment 5 deloptes 2016-09-12 15:15:16 CDT
I was experiencing similar lock of the screen without an option to unlock. Sometimes it wrked with CTRL+Alt+F1, sometime it didn't.
Since I switched to a single one - specific screen saver, the issue was not observed anymore.

I hope this helps
Comment 6 Michele Calgaro 2018-07-12 09:34:26 CDT
There has been some work done on kdesktop lock process from the time the bug was reported, so perhaps whatever was causing this bug is now ok.
Slavek and I are not able to reproduce this bug at all and never ran into the reported issue.
We are closing the bug as resolved for the time being, but if anyone runs into the same problem again, please reopen it :-)