Post by Michael F. Stemper Post by Paul Post by Michael F. Stemper
About a week and a half back, I accepted the latest updates to 16.04
LTS and let update-manager restart the box.
After it came back, I logged in with no problems. Unfortunately, now
the root map doesn't respond to right-clicks -- no menu to give me
access to xterms.
Are the control-alt-F1 through control-alt-F7 function keys working ?
Kind of. This one actually has a bad keyboard.
Post by Paul
There are six virtual terminals plus a combo that causes the desktop
to come back instead.
<Fn>-<Alt>-<F2> gave me a place that let me type "xterm", the rest of
them had no visible effect. Throwing in <ctl> didn't change any
behavior, as the article suggested.
/var/log/syslog does not change when I click on the X-root. But,
[ *** ] in front of it, with the asterisks in red and moving.
A start job is running for Hold until boot process finishes up (1w 2d 1h
59 min 44s / no limit)
The time keeps changing.
The time is roughly when I rebooted after accepting the latest updates.
(I'd thought that it was Thursday, but it could have been Friday.)
- a known phenomenon?
- something that needs to be investigated further?
- something that says I should re-reboot and ignore?
That would be something systemd has started, which has not
completed. If you could see the console log, you would see the
dancing red asterisk there.
Now, this thread is a scattershot, all over the place, but it
did have one suggestion to pass along.
When you start, you can enter grub and edit the boot entry.
(Maybe pressing shift key would work.)
The boot entry has
quiet splash $vt_handoff
at the end of one of the lines. The "splash" causes
the log on the screen to be covered with an image so
you can't see it. By removing the three words, then press
F10 to use the temporarily edited boot line, you can
then see what is printed out at start, including the
systemd line with the red asterisks indicating a problem.
The only problem with the systemd output at that point,
is it doesn't say what is wrong.
One of the major operations Ubuntu would carry out, would
be starting up the SNAP subsystem. Which has a series of
loop mounts. It's possible that takes some resources.
Systemd also stores logs, which can be quite voluminous,
but I think some adjustments have been made in the
past to trim the size of that, so it doesn't fill slash.