Automatic logout when changing the target

Begonnen von bluelupo, 2015/11/18, 09:43:50

Vorheriges Thema - Nächstes Thema

der_bud

Zitat von: horo in 2015/11/19, 10:47:17
... if you've already switched to multi-user.target and do again ...
horo, that's how powerusers debug their stuff: accidentally repeat the last command from history ...   ;)
Du lachst? Wieso lachst du? Das ist doch oft so, Leute lachen erst und dann sind sie tot.

horo

Please don't lapidate me even if I say "init 3"...
I put on my asbestos suit* and did another test: init 3 also drops you to the login each time - even when you're already in "level 3" or "multi-user.target", so I see it as a feature 'til someone from the team contradicts.

Ciao, Martin

* I'm lucky, no other harm occured, neither the hell froze nor little kittens were killed - phew!
omnia vincit pecunia :(

bluelupo

Current state: Even with the new version of systemd 228-2 has the error not changed.

melmarker

Ihr könnt hier noch ne Weile Handauflegen spielen - wie wäre es, wenn man einfach mal in oftc #debian-systemd fragt und/oder nen Bug malt?
Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. (Benjamin Franklin, November 11, 1755)
Never attribute to malice that which can be adequately explained by stupidity. (Hanlons razor)

der_bud

#19
Zitat von: melmarker in 2015/11/20, 00:36:32... und/oder nen Bug malt?

Zitat von: bluelupo in 2015/11/18, 09:43:50... EDIT: opened bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805442

---
Edit: question to all posters  here: does anybody have a clue with wich version of systemd it worked (or since when exactly it does not)? That would be useful info for the bug report.
Du lachst? Wieso lachst du? Das ist doch oft so, Leute lachen erst und dann sind sie tot.

der_bud

It looks like the developers have a clue what could have changed and are working on it, from the bug report:
Zitat von: bieblI looked into this a bit further.
Afaics, this is a regression that was introduced in v227 by commit
8c8da0e. Martin reverted that commit in 227-2, so this version is not
affected. In 227-3, that revert was replaced by upstream commit 4178002.
But that commit addressed some of the issues that were introduced by
8c8da0e.

I've forwarded this upstream and marked the bug accordingly.
Du lachst? Wieso lachst du? Das ist doch oft so, Leute lachen erst und dann sind sie tot.