https://bugzilla.novell.com/show_bug.cgi?id=809822 https://bugzilla.novell.com/show_bug.cgi?id=809822#c1 --- Comment #1 from Frederic Crozat 2013-03-18 08:52:43 UTC --- vt2 to vt6 are started on demand by systemd-logind (see logind.conf(5) NAutoVTs parameter). nss-user-lookup.target isn't started by anything atm (see https://bugzilla.novell.com/show_bug.cgi?id=803471#c8 ), it should be started by the various network authentication service, to act as a sync point to allow authentication. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809822 https://bugzilla.novell.com/show_bug.cgi?id=809822#c3 --- Comment #3 from Frederic Crozat 2013-03-18 09:42:58 UTC --- (In reply to comment #2)

Hmmm .. on demand ... I guess if I switch onto e.g. VT2 then a login prompt should occur.

Yes, it should.

If this is done on demand or static at boot time does not matter as I'd like to see a login screen if I choose a specific VT e.g. VT2. And this had not happen. And accordingly to `systemctl list-units' the service systemd-logind was not active running. Beside this if on demand has to be configured this should be the default (IMHO).

I think you have an issue caused by bnc#809821 (I'm guessing it is the same system). on demand is by default. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809822 https://bugzilla.novell.com/show_bug.cgi?id=809822#c5 --- Comment #5 from Frederic Crozat 2013-03-18 09:56:04 UTC --- Hmm, after debugging this, might be worth testing if we supports multi-seats properly (both GDM and KDM), as referenced on http://www.freedesktop.org/wiki/Software/systemd/multiseat . I'm not sure we do. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809822 https://bugzilla.novell.com/show_bug.cgi?id=809822#c7 --- Comment #7 from Dr. Werner Fink 2013-03-20 22:18:25 UTC --- (In reply to comment #5) Just read some docu about multi seat configuration and found that the use case here is not a multi seat in locations nor graphic/keyboard/mouse hardware but simply a time sharing issue on the same seat that is same locations nor graphic/keyboard/mouse hardware. The advantage is that e.g. I just not logoput but lock my console and my wife or my daughter can work/play on the same system on an other console. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809822 https://bugzilla.novell.com/show_bug.cgi?id=809822#c9 --- Comment #9 from Dr. Werner Fink 2013-03-21 10:28:20 UTC --- (In reply to comment #8) As I'm a fvwm/xlock user this would provide some frustration to the other users ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809822 https://bugzilla.novell.com/show_bug.cgi?id=809822#c Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|fcrozat@suse.com |systemd-maintainers@suse.de -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809822 https://bugzilla.novell.com/show_bug.cgi?id=809822#c10 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME --- Comment #10 from Dr. Werner Fink 2013-12-05 08:00:35 UTC --- It was IMHO a problem with a broken dependency chain, that is if systemd can not fulfill its dependency chain some of the major services may fall by the wayside. With the latest updated version of systemd on 12.3 it works. Nevertheless we, that is systemd-maintainers should hold on mind that systemd caluculates its dependency chain or better tree at runtime and therefore this can cause trouble if there are loops and other conflict or contradiction included in the dependency rules! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.