[Bug 221452] sysutils/consolekit2: session's active state lost when switching between virtual terminals
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 16 May 2021 21:42:35 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221452
Adriaan de Groot <adridg@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |adridg@freebsd.org
Status|Open |In Progress
--- Comment #34 from Adriaan de Groot <adridg@freebsd.org> ---
- If I **reboot** and go to text and start Plasma, so the very very first
session
(and sometimes a later session, I haven't got a good handle on this), it
does change, here's my second session after a reboot:
Session2:
unix-user = '1001'
realname = 'Adriaan de Groot'
seat = 'Seat1'
session-type = 'unspecified'
session-class = 'user'
session-state = 'active'
active = TRUE
x11-display = ':0'
x11-display-device = '/dev/ttyv8'
display-device = '/dev/ttyv1'
remote-host-name = ''
is-local = TRUE
on-since = '2021-05-16T21:31:18.505346Z'
login-session-id = ''
XDG_RUNTIME_DIR = '/var/run/user/1001'
VTNr = '9'
- Sometimes, from the text console like I just described, the session will be
active, but a switch to text-mode sets it to not-active, and then switching
back again to X11 doesn't do anything. It remains not-active. Like I said,
I don't have a good handle on this.
Logging out, goting to root and running `service sddm onestart` to get SDDM:
- Log in from SDDM to a Plasma X11 session with the "regular"
Plasma session selected, then the session is not marked active:
Session5:
unix-user = '1001'
realname = 'Adriaan de Groot'
seat = 'Seat3'
session-type = 'unspecified'
session-class = 'user'
session-state = 'online'
active = FALSE
x11-display = ':0'
x11-display-device = ''
display-device = '/dev/ttyv0'
remote-host-name = ''
is-local = TRUE
on-since = '2021-05-16T21:39:37.540427Z'
login-session-id = ''
XDG_RUNTIME_DIR = '/var/run/user/1001'
VTNr = '1'
switching to a text vt (ctrl-alt-F2) gives the same output from
ck-list-sessions,
and switching back to X (alt-F9) still has the same. I find the
*display-device*
line to be rather misleading: yes, I suppose root did start SDDM from there,
but it's not where the session lives. Similarly, the VTNr is wrong (that ..
seems familiar and may just be a SDDM bug) and x11-display-device isn't
set at all.
So it may be more a display manager / SDDM-specific problem, than CK itself.
--
You are receiving this mail because:
You are the assignee for the bug.