![]() ![]() Observed quite a few times working on advanced GPU stuff, especially compute shaders. The symptoms are black screen for a second, then the OS resets the hardware, restarts the driver, and resumes rendering of the desktop. UAC prompts are also displayed on another desktop, that’s how it’s impossible to automate them from within a program who triggered the UAC prompt.īTW, about crashing GPU drivers, on modern Windows the condition is recoverable. That desktop has restrictive security descriptor, most users don’t have permissions to interact with them. The login screen is simply rendered on a separate desktop. If failed, these GUI-related functions gonna return “access denied” status code instead of doing anything. To do anything on a desktop, like create windows, paint stuff, or interact with windows on that desktop, user doing that is required to pass an access check against the security descriptor of the desktop. Similar to files or registry keys, desktops have security descriptors attached (a data structure keeping who’s the owner, and optionally listing users/groups with their respective permissions on the object being controlled). Lock screen crashing seems like something inevitable (especially considering buggy graphic card drivers and so on), and it makes sense to prepare for it so that crashes won't bypass the screen locker. I'm not sure why GNOME screensaver cannot do something like this. If ksmserver itself crashes then the entire session closes. Ctrl+Alt+F2),Īfterwards switch back to the running session (Ctrl+Alt+F%2). In order to unlock switch to a virtual terminal (e.g. The screen locker is broken and unlocking is not possible anymore. If kscreenlocker crashes four times then KDE Session Management Server gives up, stops respawning kscreenlocker and simply draws the following text on the screen. If kscreenlocker crashes, the black rectangle is still here, and ksmserver will spawn kscreenlocker again but this time with software rendering (just in case it crashed due to graphics driver issue). The way it works is follows: ksmserver draws a black rectangle over everything and spawns kscreenlocker. Meanwhile, in KDE the lock screen is managed by KDE Session Management Server which ensures that lock screen cannot be bypassed by simply crashing its process. I find interesting that GNOME Screensaver's security depends on it to not crash.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |