If I understand this correctly, one use case speaks about switching user A
and user B, 1 session per each. The other use case speaks about 2 different
sessions for user A. User switching, as discussed here, is only concerned
about the former case, *different* users having a single session each.
+1
Multiple graphical sessions for the same user is not something
we'd want
to block the release on, I believe.
Well, originally I thought this to be something unrealistic, but in fact,
if user A is running a desktop session and wants to connect from a
different location via VNC for example, they might also want another
desktop session in the VNC. But we do not have any blocking criteria
against sharing a desktop via VNC or something like that at the moment
AFAIK.
Also, as usual with our criteria, user switching would only be
required to
work if it was offered by the desktop UI. If KDE decides to remove or hide
that option for whatever reason, we'd of course not require it to have it.
Similarly, we'd not mandate how exactly it is implemented - if I can switch
back to user A existing session only if I type "I❤️KDE" as my password,
otherwise I get a new session, that's fine, as long as it's clearly
communicated. KDE can set any defaults it wants.
+1
_______________________________________________
kde mailing list -- kde(a)lists.fedoraproject.org
To unsubscribe send an email to kde-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
--
Lukáš Růžička
FEDORA QE, RHCE
Red Hat
<
https://www.redhat.com>
Purkyňova 115
612 45 Brno - Královo Pole
lruzicka(a)redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <
https://redhat.com/trusted>