Control: forwarded -1 https://github.com/systemd/systemd/issues/1969
Am 19.11.2015 um 19:32 schrieb Singer Michael:
> Hi Michael,
> the new version 228-2 has the error unfortunately not changed.
I looked into this a bit further.
Afaics, this is a regression that was introduced in v227 by commit
8
(Please ignore post #45 where my misconfigured mail transport totally messed up
formatting - sorry for that)
I observe the same behaviour with systemd 228-2, like several people report at
http://forum.siduction.org/index.php?topic=5901.0
Double checked that etc/systemd/system/getty.target.wants
(Please ignore post #45 where my misconfigured mail transport totally messed up
formatting - sorry for that)
I observe the same behaviour with systemd 228-2, like several people report at
http://forum.siduction.org/index.php?topic=5901.0
Double checked that etc/systemd/system/getty.target.wants
Observe the same behaviour with systemd 228-2, like several people report at
http://forum.siduction.org/index.php?topic=5901.0Double checked that
etc/systemd/system/getty.target.wants/getty@tty1.service as well as
/lib/systemd/system/getty@.service both contain 'IgnoreOnIsolate=yes' One user
in
On Thu, 19 Nov 2015 19:18:05 +0100 Singer Michael wrote:
> Am Donnerstag, 19. November 2015, 18:42:58 schrieb Michael Biebl:
> > Am 19.11.2015 um 18:22 schrieb Singer Michael:
> > > What else can I do to turn-off this behavior? It had until a few days
ago
> > > still works, ie I was not logged ou
Am Donnerstag, 19. November 2015, 18:42:58 schrieb Michael Biebl:
> Am 19.11.2015 um 18:22 schrieb Singer Michael:
> > What else can I do to turn-off this behavior? It had until a few days ago
> > still works, ie I was not logged out of the execution of the command
> > "systemctl isolate multi-user
Am 19.11.2015 um 18:22 schrieb Singer Michael:
> What else can I do to turn-off this behavior? It had until a few days ago
> still works, ie I was not logged out of the execution of the command
> "systemctl isolate multi-user.target".
With which systemd version did it still work?
--
Why is it
Am Donnerstag, 19. November 2015, 17:52:54 schrieb Michael Biebl:
> Hm, gettys have IgnoreOnIsolate=yes set, so this shouldn't happen.
>
> If you remove libpam-systemd, and re-login, i.e. you don't have a logind
> session registered, do you still get logged out?
Hi Michael,
Sorry, but the removal
Am 19.11.2015 um 17:16 schrieb Singer Michael:
> Reproducible steps (variant 1):
> 1. system is booted into the grahical.target (including login on KDE desktop)
> 2. With the key combination CTRL-ALT-F1 switch to the text console (tty)
> 3. Login as root on the system
> 4. "systemctl isolate multi-
Am Mittwoch, 18. November 2015, 23:56:55 schrieb Michael Biebl:
> Am 18.11.2015 um 09:57 schrieb Singer Michael:
> > Package: systemd
> > Version: 227-3
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > When changing the target you will be logged out automatically, for
> > example, with the f
Am 18.11.2015 um 09:57 schrieb Singer Michael:
> Package: systemd
> Version: 227-3
> Severity: normal
>
> Dear Maintainer,
>
> When changing the target you will be logged out automatically, for example,
> with the following command on a text console:
>
> # systemctl isolate multi-user.target
>
11 matches
Mail list logo
