|
This happened to me as well, check if a slight change to the systemd
unit file helps: /lib/systemd/system/console-setup.service RequiresMountsFor=/usr /tmp i.e. add /tmp My /tmp is mounted as tmpfs so that could pose a problem. After changing this line console-setup seems to start normally during the boot up. On Sat, 26 Nov 2016 18:55:59 +0100 Nicolas LE CAM > Package: console-setup > Version: 1.153 > Followup-For: Bug #818065 > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > * What exactly did you do (or not do) that was effective (or > ineffective)? > * What was the outcome of this action? > * What outcome did you expect instead? > > *** End of the template - remove these template lines *** > > MIME-Version: 1.0 > Content-Transfer-Encoding: 8bit > Content-Type: text/plain; charset="UTF-8" > From: Nicolas LE CAM > To: Debian Bug Tracking System <818065@bugs.debian.org> > Subject: Re: console-setup is not read correctly at boottime and must be started > manually > Bcc: Nicolas LE CAM > > Package: console-setup > Version: 1.153 > Followup-For: Bug #818065 > > Dear Maintainer, > > Same problem here, I'm not sure if it's exactly the same cause though. > > In my case it seems to be a problem with /tmp availability or writability so also related to bug #620491 except this one was happening with sysvinit and is marked fixed. > > $ systemctl status console-setup.service > ● console-setup.service - Set console font and keymap > Loaded: loaded (/lib/systemd/system/console-setup.service; enabled; vendor preset: enabled) > Active: failed (Result: exit-code) since Sat 2016-11-26 18:17:30 CET; 14min ago > Process: 386 ExecStart=/lib/console-setup/console-setup.sh (code=exited, status=1/FAILURE) > Main PID: 386 (code=exited, status=1/FAILURE) > CPU: 393ms > > nov. 26 18:17:30 rio systemd[1]: Starting Set console font and keymap... > nov. 26 18:17:30 rio console-setup.sh[386]: /bin/setupcon: 866: /bin/setupcon: cannot open /tmp/tmpkbd.LsV4Kk: No such file > nov. 26 18:17:30 rio systemd[1]: console-setup.service: Main process exited, code=exited, status=1/FAILURE > nov. 26 18:17:30 rio systemd[1]: Failed to start Set console font and keymap. > nov. 26 18:17:30 rio systemd[1]: console-setup.service: Unit entered failed state. > nov. 26 18:17:30 rio systemd[1]: console-setup.service: Failed with result 'exit-code'. > > Executing /lib/console-setup/console-setup.sh in the console seems to fix the problem, no more errors reported afterwards : > > $ systemctl status console-setup.service > ● console-setup.service - Set console font and keymap > Loaded: loaded (/lib/systemd/system/console-setup.service; enabled; vendor preset: enabled) > Active: active (exited) since Sat 2016-11-26 18:32:54 CET; 14min ago > Process: 340 ExecStart=/lib/console-setup/console-setup.sh (code=exited, status=0/SUCCESS) > Main PID: 340 (code=exited, status=0/SUCCESS) > Tasks: 0 (limit: 4915) > Memory: 0B |