> The steps I described were just a corner case to describe what I
> currently observe when switching users: even if I don't really switch
> between users, but I choose "switch user" and the login again on my
> user, I see another session opened on VT2 instead of logging me back on
> existing session on VT1.

That's what I don't mean. If I switch to the same user on VT2 I want a
*new* session. If I switch back to VT1 I continue with the old session.
If both VTs are in the same login session, I don't see the point of
this if we already have virtual desktops and Activities (in fact I've
never really seen the point of Activities either, but never mind).

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. Multiple graphical sessions for the same user is not something we'd want to block the release on, I believe.

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.