John Andersen wrote:

On April 7, 2017 12:52:36 AM PDT, Per Jessen 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

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 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

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 Fri, 7 Apr 2017 14:45:23 +0200 "Carlos E. R." 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

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)

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 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 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

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 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