Bug 314073 - kscreenlocker_greet doesn't fork for multiple X screens
Summary: kscreenlocker_greet doesn't fork for multiple X screens
Status: RESOLVED NOT A BUG
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: library (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR grave
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 314533 329375 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-01-29 13:50 UTC by Alexey Shvetsov
Modified: 2019-12-06 19:45 UTC (History)
9 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey Shvetsov 2013-01-29 13:50:45 UTC
If you have 2 videocards e.g.
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Turks [Radeon HD 6670]
02:00.0 VGA compatible controller: NVIDIA Corporation GF106 [GeForce GTS 450] (rev a1)

And configured two screens e.g. :0.0 and :0.1 locker-qml will lock only one screen

Reproducible: Always
Comment 1 Adam Ziegler 2013-02-09 19:19:48 UTC
Can confirm the same behavior with two X screens across two nVidia cards - GTX 460 and GTX 465.  Lock screen appears over X screen 0, leaves X screen 1 untouched, but I can't do anything on either screen (as I would expect).

May or may not be related, but I also cannot get focus to the password field, so once the screen is locked, I need to hard-reset kdm to get back to a workable session.
Comment 2 Jens Mohr 2013-03-11 17:14:58 UTC
The same here:

- KDE 4.10.1
- two separate screens
- only one screen will locked the other show the session!

When i click the unlock button and wait then i get the focus to the password field.
Comment 3 Jens Mohr 2013-04-07 19:04:26 UTC
KDE 4.10.2

no changes!

- two separate screens - only one screen will locked the other show the session! When i click the unlock button and wait then i get the focus to the password field.
Comment 4 Martin Flöser 2015-01-23 11:25:36 UTC
Unfortunately multi-head support is not implemented in the lock screen infrastructure and I consider it as unlikely that we will implement it any time soon. It's nowadays difficult to configure (some drivers do not support such modes any more) and it needs significant changes in our lock screen architecture to support it. Changes I plan for 5.3 might make it easier to support such setups in a secure way.
Comment 5 Martin Flöser 2015-01-23 11:51:41 UTC
*** Bug 329375 has been marked as a duplicate of this bug. ***
Comment 6 Martin Flöser 2015-01-23 11:59:59 UTC
*** Bug 314533 has been marked as a duplicate of this bug. ***
Comment 7 Martin Flöser 2015-12-15 16:53:31 UTC
In a multi-head setup do you have two ksmserver instances?
Comment 8 jcwoods 2015-12-15 19:32:19 UTC
In my case, it does not run two instances of ksmserver.  I have a single instance, and the environment (from /proc/<pid>) indicates that it is pointed to DISPLAY :0.  My two displays are configured as :0.0 and :0.1, and the lock screen actually runs on :0.0.

[desktop:~]$ ps -elf | grep ksmserver
0 S xxxxxx     4273  4130  0  80   0 -  1082 unix_s Nov04 ?        00:00:00 kwrapper4 ksmserver
1 S xxxxxx     4274  4233  0  80   0 - 138946 poll_s Nov04 ?       00:00:09 kdeinit4: ksmserver [kdeinit]                  
[desktop:~]$ cat /proc/4273/environ | tr '\0' '\n' | grep DISPLAY
DISPLAY=:0
[desktop:~]$ cat /proc/4274/environ | tr '\0' '\n' | grep DISPLAY
DISPLAY=:0
Comment 9 Martin Flöser 2015-12-16 07:17:45 UTC
This will make it difficult. Ksmserver has to render the screen black and it looks like it doesn't have access to all X servers.

I'm afraid that this might be a problem which we won't fix any time soon. It will require quite some reworking on assumptions in the lock screen interaction.
Comment 10 David Edmundson 2019-12-06 19:45:06 UTC
We no longer support multiple screens.