[opensuse] leap422 - screenlock is broken / loginctl unlock-sessions ?
My laptop running Leap422 for testing suddenly showed me this text, white on black - the screen locker is broken and unlocking is not possible anymore. blahblah. I switched to a virtual console and tried running "loginctl unlock-sessions". However, this required root access ?? How does a regular office user handle this? -- Per Jessen, Zürich (6.5°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On April 7, 2017 12:52:36 AM PDT, Per Jessen <per@computer.org> wrote:
My laptop running Leap422 for testing suddenly showed me this text, white on black -
the screen locker is broken and unlocking is not possible anymore. blahblah.
I switched to a virtual console and tried running "loginctl unlock-sessions". However, this required root access ?? How does a regular office user handle this?
They call you. After all, If it were easy, thieves would do it. I've had this happen once as well. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
John Andersen wrote:
On April 7, 2017 12:52:36 AM PDT, Per Jessen <per@computer.org> wrote:
My laptop running Leap422 for testing suddenly showed me this text, white on black -
the screen locker is broken and unlocking is not possible anymore. blahblah.
I switched to a virtual console and tried running "loginctl unlock-sessions". However, this required root access ?? How does a regular office user handle this?
They call you.
I was afraid of that. -- Per Jessen, Zürich (8.5°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 07/04/2017 à 11:23, Per Jessen a écrit :
John Andersen wrote:
On April 7, 2017 12:52:36 AM PDT, Per Jessen <per@computer.org> wrote:
My laptop running Leap422 for testing suddenly showed me this text, white on black -
the screen locker is broken and unlocking is not possible anymore. blahblah.
I switched to a virtual console and tried running "loginctl unlock-sessions". However, this required root access ?? How does a regular office user handle this?
They call you.
I was afraid of that.
Control Backspace twice send you to login screen jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd wrote:
Le 07/04/2017 à 11:23, Per Jessen a écrit :
John Andersen wrote:
On April 7, 2017 12:52:36 AM PDT, Per Jessen <per@computer.org> wrote:
My laptop running Leap422 for testing suddenly showed me this text, white on black -
the screen locker is broken and unlocking is not possible anymore. blahblah.
I switched to a virtual console and tried running "loginctl unlock-sessions". However, this required root access ?? How does a regular office user handle this?
They call you.
I was afraid of that.
Control Backspace twice send you to login screen
Ctrl-Alt-Backspace kills the X-server - I'm not sure I want to tell a user to do that, they might lose some work. -- Per Jessen, Zürich (9.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data venerdì 7 aprile 2017 13:35:58, Carlos E. R. ha scritto:
On 2017-04-07 11:35, jdd wrote:
Control Backspace twice send you to login screen
That sequence crashes and locks my laptop, requiring a hard reboot to recover. go to alt+ctl+tty1 login as any user and run the loginctl-script with sudo or run it as the respective user. In both cases you can then log in but(!) next lock will do the same, so: save your work. Log out and log in again. SDDM will not crash again (unless you do the same "dual login attempt" again.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-04-07 13:43, stakanov wrote:
In data venerdì 7 aprile 2017 13:35:58, Carlos E. R. ha scritto:
On 2017-04-07 11:35, jdd wrote:
Control Backspace twice send you to login screen
That sequence crashes and locks my laptop, requiring a hard reboot to recover. go to alt+ctl+tty1
Does not work, hard lock as I said. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
In data venerdì 7 aprile 2017 13:50:46, Carlos E. R. ha scritto:
On 2017-04-07 13:43, stakanov wrote:
In data venerdì 7 aprile 2017 13:35:58, Carlos E. R. ha scritto:
On 2017-04-07 11:35, jdd wrote:
Control Backspace twice send you to login screen
That sequence crashes and locks my laptop, requiring a hard reboot to recover.
go to alt+ctl+tty1
Does not work, hard lock as I said. You mean a black screen hardlock? Not the message? In this case with Leap you have AFAIK to change the kernel.
https://bugzilla.opensuse.org/show_bug.cgi?id=1017175 Never had any attention on that bug, but when you look on how many problems and bugs for sddm are open..... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-04-07 14:36, stakanov wrote:
In data venerdì 7 aprile 2017 13:50:46, Carlos E. R. ha scritto:
On 2017-04-07 13:43, stakanov wrote:
In data venerdì 7 aprile 2017 13:35:58, Carlos E. R. ha scritto:
On 2017-04-07 11:35, jdd wrote:
Control Backspace twice send you to login screen
That sequence crashes and locks my laptop, requiring a hard reboot to recover.
go to alt+ctl+tty1
Does not work, hard lock as I said. You mean a black screen hardlock? Not the message? In this case with Leap you have AFAIK to change the kernel.
I just mentioning that in my laptop at least, ctrl-alt-backspace twice locks the computer and needs a hard reboot, ie, power button. Last time I tried may have been a month ago. It is not related to the OP. I have not investigated it. I don't remember what login manager I use. The desktop is XFCE. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On Fri, 7 Apr 2017 14:45:23 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 2017-04-07 14:36, stakanov wrote:
In data venerdì 7 aprile 2017 13:50:46, Carlos E. R. ha scritto:
On 2017-04-07 13:43, stakanov wrote:
In data venerdì 7 aprile 2017 13:35:58, Carlos E. R. ha scritto:
On 2017-04-07 11:35, jdd wrote:
Control Backspace twice send you to login screen
That sequence crashes and locks my laptop, requiring a hard reboot to recover.
go to alt+ctl+tty1
Does not work, hard lock as I said. You mean a black screen hardlock? Not the message? In this case with Leap you have AFAIK to change the kernel.
I just mentioning that in my laptop at least, ctrl-alt-backspace twice locks the computer and needs a hard reboot, ie, power button. Last time I tried may have been a month ago.
But nobody suggested pressing ctrl-alt-backspace twice! jdd suggested Control Backspace twice, and stakanov suggested alt+ctl+tty1 once. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 07/04/2017 à 18:30, Dave Howorth a écrit :
But nobody suggested pressing ctrl-alt-backspace twice!
once or twice shouldn't change anything problem in such situation is that they are rare, so most people wont remember the right solution. if ever the data loss is a problem, one need an other computer to go to the web and ask or search no work cleanly done should need so much works (backup often, at least save often) When I was working as net admin, I warned my users: nothing will be saved by me and computers may be reset each night (ghost or G4L) BSOD where so common on this time that nobody objected :-( jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-04-07 18:35, jdd wrote:
Le 07/04/2017 à 18:30, Dave Howorth a écrit :
But nobody suggested pressing ctrl-alt-backspace twice!
once or twice shouldn't change anything
Yes, it does. Do it once, it is ignored, intentionally, to cover people pressing that combo once by mistake. It simply beeps. So you have to do it twice. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2017-04-07 18:35, jdd wrote:
Le 07/04/2017 à 18:30, Dave Howorth a écrit :
But nobody suggested pressing ctrl-alt-backspace twice!
once or twice shouldn't change anything
Yes, it does.
Do it once, it is ignored, intentionally, to cover people pressing that combo once by mistake. It simply beeps. So you have to do it twice.
Pressing Ctrl-Alt-Backspace by mistake? Really? Only slightly more likely that Ctrl-Alt-Delete by mistake, I would think. -- Per Jessen, Zürich (10.2°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-04-07 21:55, Per Jessen wrote:
Carlos E. R. wrote:
On 2017-04-07 18:35, jdd wrote:
Le 07/04/2017 à 18:30, Dave Howorth a écrit :
But nobody suggested pressing ctrl-alt-backspace twice!
once or twice shouldn't change anything
Yes, it does.
Do it once, it is ignored, intentionally, to cover people pressing that combo once by mistake. It simply beeps. So you have to do it twice.
Pressing Ctrl-Alt-Backspace by mistake? Really? Only slightly more likely that Ctrl-Alt-Delete by mistake, I would think.
I'm not kidding :-) It is a documented change somewhere. Originally one time would kill the X server. They changed it to twice to avoid errors. Maybe it is similar to some other key combination used for programs. ctrl-alt-supr is very well known. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 2017-04-07 18:30, Dave Howorth wrote:
On Fri, 7 Apr 2017 14:45:23 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 2017-04-07 14:36, stakanov wrote:
In data venerdì 7 aprile 2017 13:50:46, Carlos E. R. ha scritto:
On 2017-04-07 13:43, stakanov wrote:
In data venerdì 7 aprile 2017 13:35:58, Carlos E. R. ha scritto:
On 2017-04-07 11:35, jdd wrote: > Control Backspace twice send you to login screen
That sequence crashes and locks my laptop, requiring a hard reboot to recover.
go to alt+ctl+tty1
Does not work, hard lock as I said. You mean a black screen hardlock? Not the message? In this case with Leap you have AFAIK to change the kernel.
I just mentioning that in my laptop at least, ctrl-alt-backspace twice locks the computer and needs a hard reboot, ie, power button. Last time I tried may have been a month ago.
But nobody suggested pressing ctrl-alt-backspace twice!
jdd suggested Control Backspace twice, and stakanov suggested alt+ctl+tty1 once.
Control-backspace twice is a typo, does nothing (just deletes what I typed last). It is Control-alt-backspace twice which "send you to login screen", ie, kills the graphical session. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 04/07/2017 02:36 PM, stakanov wrote:
In data venerdì 7 aprile 2017 13:50:46, Carlos E. R. ha scritto:
On 2017-04-07 13:43, stakanov wrote:
In data venerdì 7 aprile 2017 13:35:58, Carlos E. R. ha scritto:
On 2017-04-07 11:35, jdd wrote:
Control Backspace twice send you to login screen
That sequence crashes and locks my laptop, requiring a hard reboot to recover.
go to alt+ctl+tty1
Does not work, hard lock as I said. You mean a black screen hardlock? Not the message? In this case with Leap you have AFAIK to change the kernel.
https://bugzilla.opensuse.org/show_bug.cgi?id=1017175
Never had any attention on that bug, but when you look on how many problems and bugs for sddm are open.....
... or closed as INVALID like my one: https://bugzilla.opensuse.org/show_bug.cgi?id=994205 At least we shouldn't get this damn sddm by default. cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/07/2017 04:50 AM, Carlos E. R. wrote:
On 2017-04-07 13:43, stakanov wrote:
In data venerdì 7 aprile 2017 13:35:58, Carlos E. R. ha scritto:
On 2017-04-07 11:35, jdd wrote:
Control Backspace twice send you to login screen
That sequence crashes and locks my laptop, requiring a hard reboot to recover. go to alt+ctl+tty1
Does not work, hard lock as I said.
Alt-SysRq reisub ??? At this moment, I do not remember what the default setting is for Alt-SysRq is. I know it is set to limited functions because of its power. You can find out with: cat /proc/sys/kernel/sysrq If you see a "1", the magic SysRq key is enabled. If you see a "0", you will have to enable it yourself by running the following command as root: echo "1" > /proc/sys/kernel/sysrq If you see another number, that means it is partially enabled, but some SysRq functions are disabled. Alt-SysRq-r takes the keyboard out of raw mode and control of it away from the X server. Alt-SysRq-k kills all programs on the current virtual console, including X. To cleanly restart a locked-up system, you can use: Alt-Sys-Rq with the keys reisub but pause for several seconds between each key. r puts the keyboard into raw mode, as I stated above. e sends the terminate signal to all processes, asking them to end gracefully. i sends the kill signal to all processes, forcing them to end immediately. s flushes data from your cache to disk. u remounts all file systems read-only. b reboots your computer. How do I remember this sequence for when I need it? Simple: Spelled backwards, it is "busier". I want the opposite. ;-) -- -Gerry Makaro aka Fraser_Bell on the forums, IRC, and mail at openSUSE.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday, April 7, 2017 1:43:55 PM EDT stakanov wrote:
SDDM will not crash again (unless you do the same "dual login attempt" again.
I don't think this is valid re: "dual login". I have a recent install of 42.2 (with KDE) which has been used very little. There is only 1 user set up. All updates are current. Other than the usual Packman multimedia additions and installation of the nvidia graphics driver, this system is pure vanilla. The "screen locker is broken . . . blah blah" screen began ocurring after one of the updates. Unfortunately I don't know which. I do know that after using the loginctl workaround to resume the session, the behavior repeats at a later time in that same session. In 42.2 is there no way to simply prevent the session from timing out and requiring another login? My machine runs 24x7 and I don't want the session to time out at all. Also, I notice in YaST that when lightdm is selected for installation, by default it pulls in the gtk greeter. If the kde-greeter is manually selected, the gtk-greeter is deselected and all appears OK. Is the gtk-greeter the default because the openSUSE branding is available only with the gtk version while there is no kde openSUSE branding? On a KDE desktop, which greeter version should be used or does it matter? Thanks, --dg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday, April 7, 2017 1:43:55 PM EDT stakanov wrote:
SDDM will not crash again (unless you do the same "dual login attempt" again.
I don't think this is valid re: "dual login". I have a recent install of 42.2 (with KDE) which has been used very little. There is only 1 user set up. All updates are current. Other than the usual Packman multimedia additions and installation of the nvidia graphics driver, this system is pure vanilla.
The "screen locker is broken . . . blah blah" screen began ocurring after one of the updates. Unfortunately I don't know which. I do know that after using the loginctl workaround to resume the session, the behavior repeats at a later time in that same session.
In 42.2 is there no way to simply prevent the session from timing out and requiring another login? My machine runs 24x7 and I don't want the session to time out at all.
Also, I notice in YaST that when lightdm is selected for installation, by default it pulls in the gtk greeter. If the kde-greeter is manually selected, the gtk-greeter is deselected and all appears OK. Is the gtk-greeter the default because the openSUSE branding is available only with the gtk version while there is no kde openSUSE branding? On a KDE desktop, which greeter version should be used or does it matter?
Thanks,
--dg I didn't notice and thus I used for 4 month the gtk without problem. Always felt greeted correctly. Plasma had not problem. Now I did uninstall and try
In data venerdì 7 aprile 2017 10:38:26, Dennis Gallien ha scritto: the QT version . Will be fun to see if the problem reappears. It is one of my doubts that 60% of all "KDE" bugs are not KDE but QT and Intel/Nivida bugs. Will report back on it here. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data venerdì 7 aprile 2017 16:55:32, stakanov ha scritto:
In data venerdì 7 aprile 2017 10:38:26, Dennis Gallien ha scritto:
On Friday, April 7, 2017 1:43:55 PM EDT stakanov wrote:
SDDM will not crash again (unless you do the same "dual login attempt" again.
I don't think this is valid re: "dual login". I have a recent install of 42.2 (with KDE) which has been used very little. There is only 1 user set up. All updates are current. Other than the usual Packman multimedia additions and installation of the nvidia graphics driver, this system is pure vanilla.
The "screen locker is broken . . . blah blah" screen began ocurring after one of the updates. Unfortunately I don't know which. I do know that after using the loginctl workaround to resume the session, the behavior repeats at a later time in that same session.
In 42.2 is there no way to simply prevent the session from timing out and requiring another login? My machine runs 24x7 and I don't want the session to time out at all.
Also, I notice in YaST that when lightdm is selected for installation, by default it pulls in the gtk greeter. If the kde-greeter is manually selected, the gtk-greeter is deselected and all appears OK. Is the gtk-greeter the default because the openSUSE branding is available only with the gtk version while there is no kde openSUSE branding? On a KDE desktop, which greeter version should be used or does it matter?
Thanks,
--dg
I didn't notice and thus I used for 4 month the gtk without problem. Always felt greeted correctly. Plasma had not problem. Now I did uninstall and try the QT version . Will be fun to see if the problem reappears. It is one of my doubts that 60% of all "KDE" bugs are not KDE but QT and Intel/Nivida bugs. Will report back on it here.
Oh, well it works flawlessly. But it is stunningly ugly. So I will continue to use the gtk greeter at least the latter is themed. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/07/2017 07:38 AM, Dennis Gallien wrote:
On Friday, April 7, 2017 1:43:55 PM EDT stakanov wrote: In 42.2 is there no way to simply prevent the session from timing out and requiring another login? My machine runs 24x7 and I don't want the session to time out at all.
Create a file with the following contents: #!/bin/sh xset dpms 0 0 0 xset -dpms xset s noblank Give it a meaningfull name, such as noblankscreen & save it in /bin Set the permissions rwxr-xr-x Set it as a login script for each user you want to disable screen blanking on. Log out, log back in, or reboot & log in. Check to see that it all worked by opening a terminal and typing: xset q The output should include something similar to the following lines: Screen Saver: prefer blanking: no allow exposures: yes DPMS (Energy Star): Standby: 0 Suspend: 0 Off: 0 DPMS is Disabled If you hibernate, lock the screen or launch a screensaver, this will reset. So, when you have done one of those three actions, drop to a console and issue the command "noblankscreen", or whatever you named your file. -- -Gerry Makaro aka Fraser_Bell on the forums, IRC, and mail at openSUSE.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday, April 7, 2017 3:12:06 PM EDT Fraser_Bell wrote:
Create a file with the following contents:
#!/bin/sh xset dpms 0 0 0 xset -dpms xset s noblank
Give it a meaningfull name, such as noblankscreen & save it in /bin
Set the permissions rwxr-xr-x
Set it as a login script for each user you want to disable screen blanking on.
Thanks very much! I'll give it a try. --dg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
My laptop running Leap422 for testing suddenly showed me this text, white on black -
the screen locker is broken and unlocking is not possible anymore. blahblah.
I switched to a virtual console and tried running "loginctl unlock-sessions". However, this required root access ?? How does a regular office user handle this? This is a known bug. SDDM does this generally under the following premisses (reproducible for me to a 100%): a) open user A b) open user B c) try to open user A again (this will fail as it is already open). Now wait until the screensaver comes up for user A. Screen locker will now be broken and show you the message. This is an SDDM
In data venerdì 7 aprile 2017 09:52:36, Per Jessen ha scritto: problem only. If you encounter this on a regular basis use LightDM that currently does not present this issue. The reason for why a virtual console requires root to shut down is that sddm is not running afaik with the users but this suid permissions. So you need root to shut down. BTW, it is good you did remind me. I am nearly sure that this has not been fixed in 42.3 alfa but I did not try. Will give it a shot today. It may be that this is graphics dependent (I have Intel and Nvidia on another machine). Workaround: you should never open the same user session twice. Or use lightDM. I think either me or somebody else did report the but since 42.1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data venerdì 7 aprile 2017 09:52:36, Per Jessen ha scritto:
My laptop running Leap422 for testing suddenly showed me this text, white on black -
the screen locker is broken and unlocking is not possible anymore. blahblah.
I switched to a virtual console and tried running "loginctl unlock-sessions". However, this required root access ?? How does a regular office user handle this? LOL, reads, did report the bug(!)
Substantially: sddm tries to open the same user twice, and crashes. LightDM does understand the user is already open and switches correctly to the open session. And does not crash. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 7 April 2017 at 17:52, Per Jessen <per@computer.org> wrote:
My laptop running Leap422 for testing suddenly showed me this text, white on black -
the screen locker is broken and unlocking is not possible anymore. blahblah.
I switched to a virtual console and tried running "loginctl unlock-sessions". However, this required root access ?? How does a regular office user handle this?
Probably not something a regular office user would do, but it seems the following does not require root: ``` loginctl list-sessions # Find ID that corresponds to GUI session, then run the following loginctl unlock-session <ID> ```
-- Per Jessen, Zürich (6.5°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- - Karl Cheng (Qantas94Heavy) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (10)
-
Carlos E. R. -
Dave Howorth -
Dennis Gallien -
Fraser_Bell -
jdd -
John Andersen -
Karl Cheng -
Per Jessen -
Rüdiger Meier -
stakanov