[arch-general] systemd virtual terminals

[David Benfell]

Hi,

Just when I thought I'd solved the systemd issues, it seems broken
again, coming back from a power outage. As near as I can tell--and
please understand I've never seen behavior quite like this before, so
conjecture might be the better term--my virtual terminals aren't
coming up at least in a recognizable form.

The behavior is weird. systemctl says that lxdm is running on vt07.
But I can't access vt07 using the usual <CTRL><ALT>F7 sequence. Also
when I log in, the password is visible. I've never ever seen the
latter behavior before. Delete key behavior seems erratic and I'm
feeling totally disoriented.

Fortunately, the network does come up, so I'm able to ssh in from a
still-sane system (it's a laptop and it apparently managed to stay up
throughout the power outage). I did this, not that it helps much:

graton# systemctl --failed
UNIT                           LOAD   ACTIVE SUB    JOB DESCRIPTION
fancontrol.service             loaded failed failed     Fan control daemon
i2prouter.service              loaded failed failed     I2P router
postgresql.service             loaded failed failed     PostgreSQL
database server
rc-local.service               loaded failed failed     /etc/rc.local
Compatibility
systemd-modules-load.service   loaded failed failed     Load Kernel
Modules
systemd-tmpfiles-clean.service loaded failed failed     Cleanup of
Temporary Directories
systemd-tmpfiles-setup.service loaded failed failed     Recreate
Volatile Files and Directories

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
JOB    = Pending job for the unit.

7 units listed. Pass --all to see inactive units, too.
graton#

I've tried to disable fancontrol; from what I can see, it will not run
on this system, so I don't know why it's still trying to run.
i2prouter is just broken on this system and has been for a while.
postgresql has also been failing since I converted to systemd, but is
not now important. And I thought I'd sorted out the tmp files, but:

graton# journalctl | grep tmpfile
Aug 14 23:21:36 graton systemd-tmpfiles[421]:
[/usr/lib/tmpfiles.d/legacy.co....
Aug 14 23:21:36 graton systemd[1]: systemd-tmpfiles-setup.service:
main pro...=1
Aug 14 23:21:36 graton systemd[1]: Unit systemd-tmpfiles-setup.service
ente...e.
Aug 14 23:35:00 graton systemd-tmpfiles[431]:
[/usr/lib/tmpfiles.d/legacy.co....
Aug 14 23:35:00 graton systemd[1]: systemd-tmpfiles-setup.service:
main pro...=1
Aug 14 23:35:00 graton systemd[1]: Unit systemd-tmpfiles-setup.service
ente...e.
Aug 14 23:49:49 graton systemd-tmpfiles[1356]:
[/usr/lib/tmpfiles.d/legacy.c....

Aug 14 23:49:49 graton systemd[1]: systemd-tmpfiles-clean.service:
main pro...=1
Aug 14 23:49:49 graton systemd[1]: Unit systemd-tmpfiles-clean.service
ente...e.
graton#

>From the fragmentary output, it looks to me like the problem is with
legacy.conf but I'm not seeing why this should be problematic:

d /run/lock 0755 root root -
d /run/lock/subsys 0755 root root -
d /run/lock/lockdev 0775 root lock -

/run and /run/lock both exist

I've tried rebooting; it didn't help.

Now what?

Thanks!
-- 
David Benfell
benfell at parts-unknown.org

-- 
David Benfell
benfell at parts-unknown.org
Sent from my Android phone with K-9 Mail. Please excuse my brevity.