https://bugs.kde.org/show_bug.cgi?id=473247
bluescreenaven...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bluescreenaven...@gmail.com
--- Comment #7 from bluescreenaven...@gmail.com ---
So my thinking is what if it prompts the user to hit Ctrl+Alt+Shift+Esc, and
then tells the user to log in with a session that ships with KDE that is just
"KDE Session Unlock", and the session could call something like this script:
SDDM supports logind v257's SecureAttentionKey with GDM and LightDM with
waiting patches
Maybe even the user logging into KDE could run that script if it detects a
simultaneous session, but this might make it hard for users that want
simultaneous sessions, and don't have KDE starting with systemd --user
#! /bin/bash
UserSessions=($(loginctl show-user $LOGNAME --property=Sessions --value))
SeatSessions=($(loginctl show-seat $XDG_SEAT --value --property=Sessions))
UnlockSessions=()
for UserSession in "${UserSessions[@]}"
do
for SeatSession in "${SeatSessions[@]}"
do
if [[ $UserSession == $SeatSession ]]
then
UnlockSessions+=($SeatSession)
break
fi
done
done
#loginctl unlock can take multiple sessions
loginctl unlock ${UnlockSessions[@]}"
#Determining which session is actually KDE, vs say a Weston session will be
the hardest bit
loginctl activate ...
--
You are receiving this mail because:
You are watching all bug changes.
