Hi all,
I have this problem on 8 embedded systems running armbian stretch that all
reports error like this on the systemd journal:
Feb 16 14:17:10 rod-ba82a8 console-setup.sh[293]: /bin/setupcon: 866:
/bin/setupcon: cannot open /tmp/tmpkbd.BccRnI: No such file
Feb 16 14:17:10 rod-ba82a8
Hi Anton,
> > > 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 have this same problem and I tried this solution and it didn't fix
> > the problem for me.
>
>
On Mon, Oct 23, 2017 at 02:55:58PM +, Rupert Perry wrote:
>
> > 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 have this same problem and I tried this solution and
Hi
> 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
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
Hello Anton
> Yes, in this case setupcon is never run from console-setup.sh. However
> there is no need to use setupcon in order to configure the font because
> this is done by /lib/udev/rules.d/90-console-setup.rules and the
> keyboard is configured by
On Tue, Jan 03, 2017 at 11:27:26PM +, Kristian Klausen wrote:
>
> So I looked a bit on the code, and I think the issue is caused by line
> 11 in console-setup (*), the line make so console-setup.sh does
> nothing at first run after boot, and as console-setup.service is only
> run once per
Hello
I have just experienced this issue after "upgrading" (rebuilding) my live image
to stretch from jessie.
As it is a live-image, every boot is "first boot" as Anton said could give
issue.
So I looked a bit on the code, and I think the issue is caused by line 11 in
console-setup (*),
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
On Sun, Mar 13, 2016 at 10:08:23AM +0100, Thomas Schmidt wrote:
>
>* What led up to the situation?
>
> Not reproduceable
There is a slight possibility for the current console-setup to leave the
console unconfigured during the first boot. Have you observed
misconfigured console more than
Package: console-setup
Version: 1.138
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Not reproduceable
* What exactly did you do (or not do) that was effective (or
ineffective)?
11 matches
Mail list logo
