loginctl ignoring user given sessions IDs at command-line
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd |
Fix Released
|
Unknown
|
|||
systemd (Ubuntu) |
Fix Released
|
Medium
|
Dimitri John Ledkov | ||
Zesty |
Fix Released
|
Medium
|
Dimitri John Ledkov |
Bug Description
[Impact]
loginctl command does not process session IDs given on the command-line, like the documentation suggests. This makes it impossible to use simple command-line calls to check properties of a given session.
[Fix]
Backport upstream patch to fix the issue
[Testcase]
Use loginctl command and specify multiple session IDs at the command-line and verify that details about these sessons are brought up in the output.
[Regression Potential]
Minimal, current behaviour is not sane at all, and it is a typpo fix from '1' to 'i' meaning that first argument was always used, instead of the current iterated one.
Kubuntu zesty, 232-21ubuntu2
See upstream bug https:/
Changed in systemd (Ubuntu): | |
status: | New → Confirmed |
tags: | added: loginctl patch-forwarded-upstream zesty |
tags: | added: patch |
Changed in systemd: | |
status: | Unknown → New |
tags: |
added: patch-accepted-upstream removed: loginctl patch-forwarded-upstream |
tags: | removed: rls-aa-incoming |
Changed in systemd (Ubuntu Zesty): | |
status: | Triaged → In Progress |
description: | updated |
Changed in systemd: | |
status: | New → Fix Released |
Ubuntu 16.10 seems unaffected.
$ loginctl show-session 926 c2 927 | egrep Id=\|Leader
Id=926
Leader=24113
Id=c2
Leader=4175
Id=927
Leader=24212
$ loginctl show-session c2 927 926 | egrep Id=\|Leader
Id=c2
Leader=4175
Id=927
Leader=24212
Id=926
Leader=24113