"New Login" on screen locker causes crash
52 views
Skip to first unread message
Axon
Jun 6, 2014, 1:56:34 AM6/6/14
to qubes...@googlegroups.com
This may not be Qubes-specific issue, but might be worth "fixing" on the
Qubes side anyway:
When using a screen locker (tested with kscreenlocker and xScreenSaver),
attempting to login as a new user or start a new session from the lock
screen seems to crash the system. (I only tested this on my own system,
of course, which has only one user set up. Since Qubes is a single-user
system, I think this is reasonable.)
Qubes side anyway:
When using a screen locker (tested with kscreenlocker and xScreenSaver),
attempting to login as a new user or start a new session from the lock
screen seems to crash the system. (I only tested this on my own system,
of course, which has only one user set up. Since Qubes is a single-user
system, I think this is reasonable.)
Marek Marczykowski-Górecki
Jun 8, 2014, 9:01:10 PM6/8/14
to Axon, qubes...@googlegroups.com
didn't found any obvious configuration option...
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
Axon
Aug 17, 2014, 8:46:06 AM8/17/14
to Marek Marczykowski-Górecki, qubes...@googlegroups.com
Marek Marczykowski-Górecki:
by default in Qubes even in KDE. I'll start another thread about this.)
XScreenSaver FAQ[1]:
> If gdmflexiserver is installed on your system, there should be a "New Login" button on xscreensaver's unlock dialog. If that doesn't appear or doesn't work right, check the setting of the "newLoginCommand" preference in the XScreenSaver.ad app-defaults file.
XScreenSaver Man[2]:
> newLoginCommand (class NewLoginCommand)
> If set, this is the shell command that is run when the "New Login" button is pressed on the unlock dialog box, in order to create a new desktop session without logging out the user who has locked the screen. Typically this will be some variant of gdmflexiserver (1) or kdmctl (1).
KDE Docs[3]:
> The displays specified in ReserveServers will not be started when kdm starts up, but when it is explicitly requested via the command socket. If reserve displays are specified, the KDE menu will have a Start New Session item near the bottom; use that to activate a reserve display with a new login session. The monitor will switch to the new display, and you will have a minute to login. If there are no more reserve displays available, the menu item will be disabled.
[1] http://www.jwz.org/xscreensaver/faq.html
[2] http://www.jwz.org/xscreensaver/man1.html
[3] http://docs.kde.org/stable/en/kde-workspace/kdm/kdmrc-xservers.html
> On 06.06.2014 07:56, Axon wrote:
>> This may not be Qubes-specific issue, but might be worth "fixing" on the
>> Qubes side anyway:
>>
>> When using a screen locker (tested with kscreenlocker and xScreenSaver),
>> attempting to login as a new user or start a new session from the lock
>> screen seems to crash the system. (I only tested this on my own system,
>> of course, which has only one user set up. Since Qubes is a single-user
>> system, I think this is reasonable.)
>
> IMO it's good idea to just block this feature in kdm/lightdm. Any idea how? I
> didn't found any obvious configuration option...
>
Do these help? (By the way, it might be a good idea to use XScreenSaver
>> This may not be Qubes-specific issue, but might be worth "fixing" on the
>> Qubes side anyway:
>>
>> When using a screen locker (tested with kscreenlocker and xScreenSaver),
>> attempting to login as a new user or start a new session from the lock
>> screen seems to crash the system. (I only tested this on my own system,
>> of course, which has only one user set up. Since Qubes is a single-user
>> system, I think this is reasonable.)
>
> IMO it's good idea to just block this feature in kdm/lightdm. Any idea how? I
> didn't found any obvious configuration option...
>
by default in Qubes even in KDE. I'll start another thread about this.)
XScreenSaver FAQ[1]:
> If gdmflexiserver is installed on your system, there should be a "New Login" button on xscreensaver's unlock dialog. If that doesn't appear or doesn't work right, check the setting of the "newLoginCommand" preference in the XScreenSaver.ad app-defaults file.
XScreenSaver Man[2]:
> newLoginCommand (class NewLoginCommand)
> If set, this is the shell command that is run when the "New Login" button is pressed on the unlock dialog box, in order to create a new desktop session without logging out the user who has locked the screen. Typically this will be some variant of gdmflexiserver (1) or kdmctl (1).
KDE Docs[3]:
> The displays specified in ReserveServers will not be started when kdm starts up, but when it is explicitly requested via the command socket. If reserve displays are specified, the KDE menu will have a Start New Session item near the bottom; use that to activate a reserve display with a new login session. The monitor will switch to the new display, and you will have a minute to login. If there are no more reserve displays available, the menu item will be disabled.
[1] http://www.jwz.org/xscreensaver/faq.html
[2] http://www.jwz.org/xscreensaver/man1.html
[3] http://docs.kde.org/stable/en/kde-workspace/kdm/kdmrc-xservers.html
0 new messages