Bug#857132: console-setup: additional info needed ?
Yesterday I upgraded 4.10.6 to 4.10.7 taken from experimental Linux hermes 4.10.0-trunk-686-pae #1 SMP Debian 4.10.7-1~exp1 (2017-03-30) i686 GNU/Linux and had a bit of hope to see this issue fixed because of commit f9955dcaceae3a6d5c747b065e1d9da1be50b5ba Author: Takashi Iwai Date: Wed Jan 11 17:09:50 2017 +0100 fbcon: Fix vc attr at deinit commit 8aac7f34369726d1a158788ae8aff3002d5eb528 upstream. fbcon can deal with vc_hi_font_mask (the upper 256 chars) and adjust the vc attrs dynamically when vc_hi_font_mask is changed at fbcon_init(). When the vc_hi_font_mask is set, it remaps the attrs in the existing console buffer with one bit shift up (for 9 bits), while it remaps with one bit shift down (for 8 bits) when the value is cleared. It works fine as long as the font gets updated after fbcon was initialized. However, we hit a bizarre problem when the console is switched to another fb driver (typically from vesafb or efifb to drmfb). At switching to the new fb driver, we temporarily rebind the console to the dummy console, then rebind to the new driver. During the switching, we leave the modified attrs as is. Thus, the new fbcon takes over the old buffer as if it were to contain 8 bits chars (although the attrs are still shifted for 9 bits), and effectively this results in the yellow color texts instead of the original white color, as found in the bugzilla entry below. An easy fix for this is to re-adjust the attrs before leaving the fbcon at con_deinit callback. Since the code to adjust the attrs is already present in the current fbcon code, in this patch, we simply factor out the relevant code, and call it from fbcon_deinit(). Bugzilla: https://bugzilla.suse.com/show_bug.cgi?id=1000619 Signed-off-by: Takashi Iwai Signed-off-by: Bartlomiej Zolnierkiewicz Cc: Arnd Bergmann Signed-off-by: Greg Kroah-Hartman in https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.10.7 However, no such luck :-) Perhaps, though, this inspires insight into more knowledgeable people as to what might be the exact cause ? Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
Bug#857132: console-setup: additional info needed ?
Anything else I can do to get this issue looked into ? Thanks, Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
Bug#857132: console-setup: additional info needed ?
On Sun, Mar 26, 2017 at 08:18:16PM +0200, Karsten Hilbert wrote: > One thing I *haven't* tested yet is whether earlier kernel > would make a difference -- not that I would think but who > knows. Just for kicks I booted all kernels installed on this machine (all prior experimentation was done under 4.10) -- the console did not get properly configured under any of 4.3, 4.6, or 4.9. I did manage to have parallelism detection kick in once though: [...] 1087 - 2017-03-27 09:54:40.488734408+02:00: /cached_setup_font.sh.running created 1087 - 2017-03-27 09:54:40.509440184+02:00: /cached_setup_font.sh.running deleted [reboot] 426 - 2017-03-27 09:57:39.157315082+02:00: /cached_setup_font.sh.running created 502 - 2017-03-27 09:57:40.195551438+02:00: /cached_setup_font.sh.running exists and contains [426 / 2017-03-27 09:57:39.157315082+02:00], exiting 426 - 2017-03-27 09:57:40.709767317+02:00: /cached_setup_font.sh.running deleted 657 - 2017-03-27 09:57:42.245186312+02:00: /cached_setup_font.sh.running created 657 - 2017-03-27 09:57:42.268458964+02:00: /cached_setup_font.sh.running deleted so at least we got this right, technically :-) These boots were under slightly heavier load: two external USB mass storage devices being online during the entire reboot cycle, one of which acts as backup swap while the other is a backup device being hit by another machine over the network as soon as the problem machine reaches network target. Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
Bug#857132: console-setup: additional info needed ?
On Sun, Mar 26, 2017 at 08:42:43PM +0300, Anton Zinoviev wrote: >> I have done some more experimentation and it shows fairly >> strange results. > > Thanks a lot! :) That is what I can contribute. > > Sometimes cached_setup_font.sh does not seem to get run AT > > ALL -- the log file simply does not exist after a clean boot. > > Maybe this happened because cached_setup_font.sh was run while / was > still read-only? Possibly. Suspecting that is why I chose / in the hope it'll get mounted rw real early :-) > > However, as witnessed by this log snippet from the most > > recent boot, it does not ALWAYS run in parallel: > > Let us clear one point: no matter whether it runs in parallel or not -- > the console is never configured properly? Or sometimes it is? It is NEVER configured properly anymore. It used to always work until fairly recently (shortly before I filed the bug) but now _never_ does, regardless of whether I can find a log under /. One thing I *haven't* tested yet is whether earlier kernel would make a difference -- not that I would think but who knows. Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
Bug#857132: console-setup: additional info needed ?
One more data point: > I edited the file /etc/console-setup/cached_setup_font.sh > to look like this: ... > the idea being to prevent it from running in parallel. ... > When the log file DOES exist it does indeed show > cached_setup_font.sh to run in parallel "early" in the boot > process and once more "later": However, as witnessed by this log snippet from the most recent boot, it does not ALWAYS run in parallel: 397 - 2017-03-26 15:53:08.218566865+02:00: /cached_setup_font.sh.running created 397 - 2017-03-26 15:53:09.054517233+02:00: /cached_setup_font.sh.running deleted 465 - 2017-03-26 15:53:09.569959665+02:00: /cached_setup_font.sh.running created 465 - 2017-03-26 15:53:09.656989307+02:00: /cached_setup_font.sh.running deleted 557 - 2017-03-26 15:53:09.701864078+02:00: /cached_setup_font.sh.running created 557 - 2017-03-26 15:53:09.743826537+02:00: /cached_setup_font.sh.running deleted (it took much longer this time for the second process 465 to be run) The only thing I can think of maybe having been different between this boot and other boots was: This time I let Debian boot all the way into SDDM, then DID NOT switch to a console right away but rather logged into KDE, and only switched to a VT once KDE login was finished. Probably doesn't help much, however. Thought I'd mention though. Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
Bug#857132: console-setup: additional info needed ?
I have done some more experimentation and it shows fairly
strange results.
I edited the file /etc/console-setup/cached_setup_font.sh
to look like this:
#!/bin/sh
# added
SEMAPHORE="/cached_setup_font.sh.running"
LOG="/console-cached_setup_font.sh-tracing.log"
TS=`date --rfc-3339=ns`
if test ! -f ${SEMAPHORE} ; then
> ${SEMAPHORE} ;
echo "$$ / $TS" > ${SEMAPHORE} ;
echo "$$ - $TS: ${SEMAPHORE} created" >> $LOG ;
else
VAL=`cat ${SEMAPHORE}` ;
echo "$$ - $TS: ${SEMAPHORE} exists and contains [$VAL], exiting"
>> $LOG ;
exit 0 ;
fi
# ---
setfont '/etc/console-setup/Lat15-Terminus16.psf.gz'
if ls /dev/fb* >/dev/null 2>/dev/null; then
for i in /dev/vcs[0-9]*; do
{ :
setfont '/etc/console-setup/Lat15-Terminus16.psf.gz'
} < /dev/tty${i#/dev/vcs} > /dev/tty${i#/dev/vcs}
done
fi
mkdir -p /run/console-setup
> /run/console-setup/font-loaded
for i in /dev/vcs[0-9]*; do
{ :
printf '\033%%G'
} < /dev/tty${i#/dev/vcs} > /dev/tty${i#/dev/vcs}
done
# added
rm -f ${SEMAPHORE} >> $LOG
TS=`date --rfc-3339=ns`
echo "$$ - $TS: ${SEMAPHORE} deleted" >> $LOG
# ---
the idea being to prevent it from running in parallel.
Observations after many reboots with neither semaphore nor
log existing:
Sometimes cached_setup_font.sh does not seem to get run AT
ALL -- the log file simply does not exist after a clean boot.
When the log file DOES exist it does indeed show
cached_setup_font.sh to run in parallel "early" in the boot
process and once more "later":
421 - 2017-03-24 11:31:44.262310078+01:00:
/cached_setup_font.sh.running created
423 - 2017-03-24 11:31:44.262785627+01:00:
/cached_setup_font.sh.running created
421 - 2017-03-24 11:31:45.721488930+01:00:
/cached_setup_font.sh.running deleted
423 - 2017-03-24 11:31:45.721489699+01:00:
/cached_setup_font.sh.running deleted
659 - 2017-03-24 11:31:47.733106958+01:00:
/cached_setup_font.sh.running created
659 - 2017-03-24 11:31:47.755347426+01:00:
/cached_setup_font.sh.running deleted
Note how the two early runs even manage to race each other
within a few (4) microseconds:
421 - 2017-03-24 11:31:44.262*3*10078+01:00:
/cached_setup_font.sh.running created
423 - 2017-03-24 11:31:44.262*7*85627+01:00:
/cached_setup_font.sh.running created
which means that this code:
#!/bin/sh
# added
SEMAPHORE="/cached_setup_font.sh.running"
LOG="/console-cached_setup_font.sh-tracing.log"
TS=`date --rfc-3339=ns`
if test ! -f ${SEMAPHORE} ; then
> ${SEMAPHORE} ;
echo "$$ / $TS" > ${SEMAPHORE} ;
runs in less than 4 µs because it manages to race inbetween
if test ! -f ${SEMAPHORE} ; then
> ${SEMAPHORE} ;
(that's why I first create the semaphore before taking the
time to pipe data into it).
Here's what journalctl -b records for that time span:
Mär 24 11:31:43 hermes systemd[1]: Starting Load/Save RF Kill Switch
Status...
Mär 24 11:31:44 hermes systemd[1]: Started Load/Save Screen Backlight
Brightness of backlight:intel_backlight.
Mär 24 11:31:44 hermes systemd[1]: Started Load/Save Screen Backlight
Brightness of backlight:acpi_video0.
Mär 24 11:31:44 hermes kernel: psmouse serio4: elantech: assuming
hardware version 2 (with firmware version 0x040101)
Mär 24 11:31:44 hermes kernel: ath: phy0: Enable LNA combining
Mär 24 11:31:44 hermes kernel: ath: phy0: ASPM enabled: 0x42
Mär 24 11:31:44 hermes kernel: ath: EEPROM regdomain: 0x60
Mär 24 11:31:44 hermes kernel: ath: EEPROM indicates we should expect a
direct regpair map
Mär 24 11:31:44 hermes kernel: ath: Country alpha2 being used: 00
Mär 24 11:31:44 hermes kernel: ath: Regpair used: 0x60
Mär 24 11:31:44 hermes kernel: psmouse serio4: elantech: Synaptics
capabilities query result 0x7e, 0x13, 0x0d.
Mär 24 11:31:44 hermes kernel: psmouse serio4: elantech: Elan sample
query result 19, 00, 00
Mär 24 11:31:44 hermes kernel: input: ETPS/2 Elantech Touchpad as
/devices/platform/i8042/serio4/input/input15
Mär 24 11:31:44 hermes kernel: ieee80211 phy0: Selected rate control
algorithm 'minstrel_ht'
Mär 24 11:31:44 hermes kernel: ieee80211 phy0: Atheros AR9285 Rev:2
mem=0xf89b, irq=17
Mär 24 11:31:44 hermes kernel: iTCO_vendor_support: vendor-support=0
Mär 24 11:31:44 hermes kernel: iTCO_wdt: Intel TCO WatchDog Timer
Driver v1.11
Mär 24 11:31:44 hermes kernel: iTCO_wdt: Found a ICH9M TCO device
(Version=2, TCOBASE=0x0860)
Mär 24 11:31:44 hermes kernel: iTCO_wdt: initialized. heartbeat=30 sec
Bug#857132: console-setup: additional info needed ?
On Thu, Mar 23, 2017 at 03:04:37PM +0200, Anton Zinoviev wrote: > Since systemd makes some configuration of the console, maybe the > following scenario might explain what we observe: ... lengthy analysis ... > So, if this scenario is possible, a natural question is what can be done > in order to make sure the scripts of console-setup do not execute in > parallel with systemd while configuring the console. This very much sounds like a possible cause for what I am observing and should be the path to follow first. Note that this problem has been observed previously (there's old, resolved bugs around this) which had a similar solution. A, perhaps fairly drastic, solution might be to delay setupcon font setting until all getty's have been started ? Thanks, Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
Bug#857132: console-setup: additional info needed ?
On Thu, Mar 23, 2017 at 11:07:14AM +0100, Sven Joachim wrote: > >> > ls -l /etc/console-setup/ > >> > >>-rwxr-xr-x 1 root root 465 Mar 22 11:20 cached_setup_font.sh > >>-rwxr-xr-x 1 root root 358 Mar 22 11:20 cached_setup_keyboard.sh > >>-rwxr-xr-x 1 root root73 Mar 22 11:20 cached_setup_terminal.sh > > > > Hm, the times of these three are too recent. I can see two possibilities: > > > > 1. either the bug no longer exists in this system, in which case we > > have to find out what caused these files to be created, or > > > > 2. the bug still exists and each time the system boots, it recreates > > these three files. In this case we have to find out the cause of this. > > There might be a third possibility which seems to happen on one of my > systems: the cached_setup_font.sh script does not work correctly when > run during boot by udev. Because this is what I am observing here, I > even added some debug messages to it to see if it is run at all (as > intended by /lib/udev/rules.d/90-console-setup.rules), and indeed it > does run but the font still remains unchanged. This very much hints at a dependency problems, does it not ? Does your system exhibiting this behaviour run systemd ? > Manually running /etc/console-setup/cached_setup_font.sh (or > setupcon -f, for that matter) works fine, so I'm a bit at a loss here. I'll constrain my "fixup" script to "-f" now to see whether that will consistently fix what I am seeing (IOW whether we can constrain the problem to font setting, which is likely). I have sometimes noted the following which seems to suggest that some dependency may come up late: Directly after boot, during which no VT switch occurred, I will see the login manager for KDE. When I now switch to the first console and then ALT-RIGHT through my other consoles up until vt6 they don't have a getty running just yet (they show up as empty black screens). The second round through all of them exhibit the getty login prompt. This happens only very rarely but it _does_ come up every so often. This fact does seem to hint a gettys being spawned in a delayed fashion. I have observed something else, but only ONCE so far: After running setupcon to fix the font problem one console (sitting at the login prompt) did not get the message - it stayed in the old, wrong font. Re-running setupcon fixed that console, too. Other consoles - which reset to the correct font upon the first setupcon invocation - where either logged in or sitting at the login prompt as well, so it's not whether they were logged in or not. Might there be a race between getty spawning and setupcon running ? Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
Bug#857132: console-setup: additional info needed ?
On Wed, Mar 22, 2017 at 08:48:16PM +0200, Anton Zinoviev wrote: > > 2017-03-22 13:05:13.364493514 +0100 /etc/console-setup/cached_setup_font.sh > > 2017-03-22 13:05:13.364493514 +0100 > > /etc/console-setup/cached_setup_keyboard.sh > > 2017-03-22 13:05:13.364493514 +0100 > > /etc/console-setup/cached_setup_terminal.sh > > 2017-03-22 12:54:59.368053266 +0100 > > /etc/console-setup/cached_UTF-8_del.kmap.gz > > 2017-03-22 12:53:10.459239057 +0100 /etc/default/console-setup > > 2017-03-07 09:26:01.171789164 +0100 /etc/default/keyboard > > It seems something has changed /etc/default/console-setup. If this file > is changed, then boot scripts of console-setup will recreate the > cached_* files in /etc. > > Do you know what has caused this file to be changed? That was me, again, because I hoped that setting # Change to "yes" and setupcon will explain what is being doing VERBOSE_OUTPUT="yes" from "no" to "yes" would generate helpful debugging output. However, I haven't been able to find any :-/ > Something unrelated that might explain the bug is this: maybe this > system runs X It does, yes. > but doesn't have framebuffer on the console? Oh, it does: dmseg: [ 20.377384] fbcon: inteldrmfb (fb0) is primary device ... [ 21.054248] Console: switching to colour frame buffer device 170x48 [ 21.084983] i915 :00:02.0: fb0: inteldrmfb frame buffer device fbset -v -i Linux Frame Buffer Device Configuration Version 2.1 (23/06/1999) (C) Copyright 1995-1999 by Geert Uytterhoeven Opening frame buffer device `/dev/fb0' Using current video mode from `/dev/fb0' mode "1366x768" geometry 1366 768 1366 768 32 timings 0 0 0 0 0 0 0 accel true rgba 8/16,8/8,8/0,0/0 endmode Getting further frame buffer information Frame buffer device information: Name: inteldrmfb Address : 0xd0048000 Size: 4227072 Type: PACKED PIXELS Visual : TRUECOLOR XPanStep: 1 YPanStep: 1 YWrapStep : 0 LineLength : 5504 Accelerator : No > BTW, instead of `systemctl restart console-setup.service` you can use > the command `setupcon`. OK, I will resort to that in order to minimize what is involved. Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
Bug#857132: console-setup: additional info needed ?
On Wed, Mar 22, 2017 at 04:49:27PM +0200, Anton Zinoviev wrote:
> Thanks. :) Well, can you report the state of the affairs before you run
>
> systemctl restart console-setup.service
>
> ls --full-time /etc/default/{console-setup,keyboard}
> /etc/console-setup/cached_*
Attached.
Full times directly after a reboot before manually restarting
console-setup.
Karsten
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
-rwxr-xr-x 1 root root 465 2017-03-22 13:05:13.364493514 +0100
/etc/console-setup/cached_setup_font.sh
-rwxr-xr-x 1 root root 358 2017-03-22 13:05:13.364493514 +0100
/etc/console-setup/cached_setup_keyboard.sh
-rwxr-xr-x 1 root root 73 2017-03-22 13:05:13.364493514 +0100
/etc/console-setup/cached_setup_terminal.sh
-rw-r--r-- 1 root root 4377 2017-03-22 12:54:59.368053266 +0100
/etc/console-setup/cached_UTF-8_del.kmap.gz
-rw-r--r-- 1 root root 2061 2017-03-22 12:53:10.459239057 +0100
/etc/default/console-setup
-rw-r--r-- 1 root root 587 2017-03-07 09:26:01.171789164 +0100
/etc/default/keyboard
Bug#857132: console-setup: additional info needed ?
On Wed, Mar 22, 2017 at 03:02:28PM +0200, Anton Zinoviev wrote:
> > > ls -l /etc/console-setup/
> >
> > -rwxr-xr-x 1 root root 465 Mar 22 11:20 cached_setup_font.sh
> > -rwxr-xr-x 1 root root 358 Mar 22 11:20 cached_setup_keyboard.sh
> > -rwxr-xr-x 1 root root73 Mar 22 11:20 cached_setup_terminal.sh
>
> Hm, the times of these three are too recent. I can see two possibilities:
>
> 1. either the bug no longer exists in this system, in which case we
> have to find out what caused these files to be created, or
>
> 2. the bug still exists and each time the system boots, it recreates
> these three files. In this case we have to find out the cause of this.
The latter: currently, after each boot, I manually run
systemctl restart console-setup.service
which fixes the console problem for me until the next boot.
That's why those files are from today.
> Can you check if the times of these three files change each time the
> system boots?
See above.
> And what about the files
> /etc/default/{keyboard,console-setup} -- do their times change too?
Likely because of the above, too.
> > (the line starting with ">" strikes me as odd - should it not
> > be on the "mkdir -p" line ?)
>
> This line creates an empty file /run/console-setup/font-loaded which is
I eventually figured as much...
> used by /lib/udev/rules.d/90-console-setup.rules to make sure the script
> /etc/console-setup/cached_setup_terminal.sh is not run before
> /etc/console-setup/cached_setup_font.sh.
OK, got it.
> These look ok as well...
Feel free to ask for more information you may need.
Thanks,
Karsten
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
Bug#857132: console-setup: additional info needed ?
On Wed, Mar 22, 2017 at 02:18:51PM +0300, Anton Zinoviev wrote:
> > is there anything I can do/provide to help get this resolved ?
>
> Yes, thanks! The output of the following commands:
Here you go:
> ls -l /etc/console-setup/
total 164
drwxr-xr-x 2 root root 4096 Mar 7 09:26 .
drwxr-xr-x 194 root root 12288 Mar 22 11:16 ..
-rw-r--r-- 1 root root 2417 Mar 2 2011 Lat15-Fixed16.psf.gz
-rw-r--r-- 1 root root 2328 Mar 11 2011 Lat15-Terminus16.psf.gz
-rw-r--r-- 1 root root 2351 Nov 12 2010 Lat15-TerminusBold16.psf.gz
-rw-r--r-- 1 root root 4086 Mar 11 2011 cached.kmap.gz
-rw-r--r-- 1 root root 4377 Mar 7 09:26 cached_UTF-8_del.kmap.gz
-rwxr-xr-x 1 root root 465 Mar 22 11:20 cached_setup_font.sh
-rwxr-xr-x 1 root root 358 Mar 22 11:20 cached_setup_keyboard.sh
-rwxr-xr-x 1 root root73 Mar 22 11:20 cached_setup_terminal.sh
-rw-r--r-- 1 root root34 Jan 11 2011 compose.ARMSCII-8.inc
-rw-r--r-- 1 root root31 Jan 11 2011 compose.CP1251.inc
-rw-r--r-- 1 root root31 Jan 11 2011 compose.CP1255.inc
-rw-r--r-- 1 root root31 Jan 11 2011 compose.CP1256.inc
-rw-r--r-- 1 root root41 Jan 11 2011 compose.GEORGIAN-ACADEMY.inc
-rw-r--r-- 1 root root36 Jan 11 2011 compose.GEORGIAN-PS.inc
-rw-r--r-- 1 root root32 Jan 11 2011 compose.IBM1133.inc
-rw-r--r-- 1 root root35 Jan 11 2011 compose.ISIRI-3342.inc
-rw-r--r-- 1 root root 3596 May 22 2016 compose.ISO-8859-1.inc
-rw-r--r-- 1 root root36 Jan 11 2011 compose.ISO-8859-10.inc
-rw-r--r-- 1 root root36 Jan 11 2011 compose.ISO-8859-11.inc
-rw-r--r-- 1 root root 3737 May 22 2016 compose.ISO-8859-13.inc
-rw-r--r-- 1 root root 3020 Mar 2 2016 compose.ISO-8859-14.inc
-rw-r--r-- 1 root root 3552 May 22 2016 compose.ISO-8859-15.inc
-rw-r--r-- 1 root root36 Jan 11 2011 compose.ISO-8859-16.inc
-rw-r--r-- 1 root root 2893 May 22 2016 compose.ISO-8859-2.inc
-rw-r--r-- 1 root root 3387 May 22 2016 compose.ISO-8859-3.inc
-rw-r--r-- 1 root root 2805 May 22 2016 compose.ISO-8859-4.inc
-rw-r--r-- 1 root root35 Jan 11 2011 compose.ISO-8859-5.inc
-rw-r--r-- 1 root root35 Jan 11 2011 compose.ISO-8859-6.inc
-rw-r--r-- 1 root root 1217 May 22 2016 compose.ISO-8859-7.inc
-rw-r--r-- 1 root root35 Jan 11 2011 compose.ISO-8859-8.inc
-rw-r--r-- 1 root root 3617 May 22 2016 compose.ISO-8859-9.inc
-rw-r--r-- 1 root root31 Jan 11 2011 compose.KOI8-R.inc
-rw-r--r-- 1 root root31 Jan 11 2011 compose.KOI8-U.inc
-rw-r--r-- 1 root root32 Jan 11 2011 compose.TIS-620.inc
-rw-r--r-- 1 root root31 Dec 5 2011 compose.VISCII.inc
-rw-r--r-- 1 root root 1359 Dec 5 2011 remap.inc
> cat /etc/console-setup/cached_setup_font.sh
#!/bin/sh
setfont '/etc/console-setup/Lat15-Terminus16.psf.gz'
if ls /dev/fb* >/dev/null 2>/dev/null; then
for i in /dev/vcs[0-9]*; do
{ :
setfont '/etc/console-setup/Lat15-Terminus16.psf.gz'
} < /dev/tty${i#/dev/vcs} > /dev/tty${i#/dev/vcs}
done
fi
mkdir -p /run/console-setup
> /run/console-setup/font-loaded
for i in /dev/vcs[0-9]*; do
{ :
printf '\033%%G'
} < /dev/tty${i#/dev/vcs} > /dev/tty${i#/dev/vcs}
done
(the line starting with ">" strikes me as odd - should it not
be on the "mkdir -p" line ?)
> cat /etc/console-setup/cached_setup_terminal.sh
#!/bin/sh
{ :
printf '\033%%G'
} < /dev/tty${1#vcs} > /dev/tty${1#vcs}
> cat /etc/default/console-setup
# Change to "yes" and setupcon will explain what is being doing
VERBOSE_OUTPUT="no"
# Setup these consoles. Most people do not need to change this.
ACTIVE_CONSOLES="/dev/tty[1-6]"
# Put here your encoding. Valid charmaps are: UTF-8 ARMSCII-8 CP1251
# CP1255 CP1256 GEORGIAN-ACADEMY GEORGIAN-PS IBM1133 ISIRI-3342
# ISO-8859-1 ISO-8859-2 ISO-8859-3 ISO-8859-4 ISO-8859-5 ISO-8859-6
# ISO-8859-7 ISO-8859-8 ISO-8859-9 ISO-8859-10 ISO-8859-11 ISO-8859-13
# ISO-8859-14 ISO-8859-15 ISO-8859-16 KOI8-R KOI8-U TIS-620 VISCII
CHARMAP="UTF-8"
# The codeset determines which symbols are supported by the font.
# Valid codesets are: Arabic Armenian CyrAsia CyrKoi CyrSlav Ethiopian
# Georgian Greek Hebrew Lao Lat15 Lat2 Lat38 Lat7 Thai Uni1 Uni2 Uni3
# Vietnamese. Read README.fonts for explanation.
CODESET="Lat15"
# Valid font faces are: VGA (sizes 8, 14 and 16), Terminus (sizes
# 12x6, 14, 16, 20x10, 24x1
Bug#857132: console-setup: additional info needed ?
Package: console-setup Version: 1.163 Followup-For: Bug #857132 Hi, is there anything I can do/provide to help get this resolved ? Thanks, Karsten -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 4.10.0-trunk-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages console-setup depends on: ii console-setup-linux 1.163 ii debconf 1.5.60 ii keyboard-configuration 1.163 ii xkb-data2.19-1 console-setup recommends no packages. Versions of packages console-setup suggests: ii locales 2.24-9 ii lsb-base 9.20161125 Versions of packages keyboard-configuration depends on: ii debconf 1.5.60 ii liblocale-gettext-perl 1.07-3+b1 Versions of packages console-setup-linux depends on: ii init-system-helpers 1.47 ii initscripts 2.88dsf-59.9 ii kbd 2.0.3-2+b1 ii keyboard-configuration 1.163 console-setup-linux suggests no packages. Versions of packages console-setup is related to: pn console-common pn console-data pn console-tools pn gnome-control-center ii kbd 2.0.3-2+b1 ii systemd 232-19 -- debconf information excluded
Bug#857132: console-setup (again) stopped to apply font at startup
On Wed, Mar 08, 2017 at 02:21:59PM +0200, Anton Zinoviev wrote: >> console-setup just stopped to apply font settings during startup. > > Does this system has some read-only file systems? Not that I am aware of, no. Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
Bug#857132: console-setup (again) stopped to apply font at startup
Package: console-setup Version: 1.163 Severity: important Hi, console-setup just stopped to apply font settings during startup. This happened before and was fixed about a year ago: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759657 Maybe not the same reason but the faulty behaviour is back... Manually running systemctl restart console-setup.service fixes the problem until the next reboot. Thanks for looking into the issue, Karsten -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 4.10.0-trunk-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages console-setup depends on: ii console-setup-linux 1.163 ii debconf 1.5.60 ii keyboard-configuration 1.163 ii xkb-data2.19-1 console-setup recommends no packages. Versions of packages console-setup suggests: ii locales 2.24-9 ii lsb-base 9.20161125 Versions of packages keyboard-configuration depends on: ii debconf 1.5.60 ii liblocale-gettext-perl 1.07-3+b1 Versions of packages console-setup-linux depends on: ii init-system-helpers 1.47 ii initscripts 2.88dsf-59.9 ii kbd 2.0.3-2+b1 ii keyboard-configuration 1.163 console-setup-linux suggests no packages. Versions of packages console-setup is related to: pn console-common pn console-data pn console-tools pn gnome-control-center ii kbd 2.0.3-2+b1 ii systemd 232-18 -- debconf information: console-setup/fontsize-text47: 8x16 * console-setup/charmap47: UTF-8 debian-installer/console-setup-udeb/title: * keyboard-configuration/model: Generische PC-Tastatur mit 105 Tasten (Intl) keyboard-configuration/unsupported_config_options: true keyboard-configuration/layout: console-setup/codesetcode: Lat15 console-setup/guess_font: console-setup/framebuffer_only: * console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic languages console-setup/use_system_font: keyboard-configuration/toggle: No toggling * console-setup/fontsize-fb47: 8x16 keyboard-configuration/modelcode: pc105 console-setup/store_defaults_in_debconf_db: true keyboard-configuration/layoutcode: de * keyboard-configuration/ctrl_alt_bksp: false console-setup/fontsize: 8x16 keyboard-configuration/store_defaults_in_debconf_db: true keyboard-configuration/unsupported_layout: true * keyboard-configuration/variant: Deutsch - Deutsch (ohne Akzenttasten) keyboard-configuration/unsupported_config_layout: true keyboard-configuration/optionscode: keyboard-configuration/other: * keyboard-configuration/altgr: The default for the keyboard layout * console-setup/fontface47: Terminus keyboard-configuration/variantcode: nodeadkeys * keyboard-configuration/compose: No compose key keyboard-configuration/xkb-keymap: de(nodeadkeys) keyboard-configuration/unsupported_options: true keyboard-configuration/switch: No temporary switch
Bug#759657: console-setup w/ systemd forgets font setting
On Tue, Dec 15, 2015 at 09:16:58AM +0100, Karsten Hilbert wrote: > I shall now add: > >>> This is a shot in the dark, but can you try and create the following >>> udev rules file: >>> >>> $ cat /etc/udev/rules.d/90-setupcon.rules >>> ACTION=="add", SUBSYSTEM=="vtconsole", KERNEL=="vtcon*", >>> RUN+="/bin/setupcon" This seems to fix it for me as well, even without the wait4udev settle rule Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
Bug#759657: console-setup: bug still exists
Package: console-setup Version: 1.128 Followup-For: Bug #759657 Just to let you know that this bug still exists albeit less frequently now. Karsten -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'stable'), (500, 'oldstable'), (50, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 4.0.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages console-setup depends on: ii console-setup-linux 1.128 ii debconf 1.5.56 ii keyboard-configuration 1.128 ii xkb-data2.14-1 console-setup recommends no packages. Versions of packages console-setup suggests: ii locales2.19-18 ii locales-all [locales] 2.19-18 ii lsb-base 4.1+Debian13+nmu1 Versions of packages keyboard-configuration depends on: ii debconf 1.5.56 ii initscripts 2.88dsf-59.2 ii liblocale-gettext-perl 1.05-8+b1 Versions of packages console-setup-linux depends on: ii kbd 1.15.5-2 ii keyboard-configuration 1.128 console-setup-linux suggests no packages. Versions of packages console-setup is related to: pn console-common pn console-data pn console-tools ii kbd 1.15.5-2 -- debconf information: keyboard-configuration/ctrl_alt_bksp: false console-setup/guess_font: keyboard-configuration/modelcode: pc105 keyboard-configuration/unsupported_options: true console-setup/codesetcode: Lat15 keyboard-configuration/altgr: The default for the keyboard layout debian-installer/console-setup-udeb/title: keyboard-configuration/variantcode: nodeadkeys keyboard-configuration/other: keyboard-configuration/model: Generische PC-Tastatur mit 105 Tasten (Intl) keyboard-configuration/toggle: No toggling * console-setup/fontsize-fb47: 8x16 keyboard-configuration/unsupported_config_options: true * console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic languages console-setup/framebuffer_only: * console-setup/charmap47: UTF-8 keyboard-configuration/compose: No compose key console-setup/fontsize: 8x16 keyboard-configuration/layout: keyboard-configuration/unsupported_config_layout: true keyboard-configuration/xkb-keymap: de(nodeadkeys) keyboard-configuration/unsupported_layout: true keyboard-configuration/layoutcode: de console-setup/use_system_font: keyboard-configuration/switch: No temporary switch * console-setup/fontface47: Terminus console-setup/store_defaults_in_debconf_db: true console-setup/fontsize-text47: 8x16 keyboard-configuration/variant: Deutsch - Deutsch (ohne Akzenttasten) keyboard-configuration/store_defaults_in_debconf_db: true keyboard-configuration/optionscode: -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150601164150.2847.11734.report...@hermes.hilbert.loc
Bug#759657: console-setup: problem back
Package: console-setup Version: 1.123 Followup-For: Bug #759657 This problem is back: it hasn't happened since I added the wait4udev thing but today it came back. Karsten -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'stable'), (500, 'oldstable'), (50, 'unstable'), (10, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.19.0-trunk-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages console-setup depends on: ii console-setup-linux 1.123 ii debconf 1.5.56 ii keyboard-configuration 1.123 ii xkb-data2.12-1 console-setup recommends no packages. Versions of packages console-setup suggests: ii locales2.19-18 ii locales-all [locales] 2.19-18 ii lsb-base 4.1+Debian13+nmu1 Versions of packages keyboard-configuration depends on: ii debconf 1.5.56 ii initscripts 2.88dsf-59 ii liblocale-gettext-perl 1.05-8+b1 Versions of packages console-setup-linux depends on: ii kbd 1.15.5-2 ii keyboard-configuration 1.123 console-setup-linux suggests no packages. Versions of packages console-setup is related to: pn console-common pn console-data pn console-tools ii kbd 1.15.5-2 -- debconf information: keyboard-configuration/xkb-keymap: de(nodeadkeys) console-setup/fontsize-text47: 8x16 console-setup/framebuffer_only: keyboard-configuration/ctrl_alt_bksp: false keyboard-configuration/unsupported_options: true keyboard-configuration/modelcode: pc105 keyboard-configuration/store_defaults_in_debconf_db: true keyboard-configuration/layout: console-setup/use_system_font: keyboard-configuration/variantcode: nodeadkeys keyboard-configuration/switch: No temporary switch console-setup/fontsize: 8x16 keyboard-configuration/optionscode: debian-installer/console-setup-udeb/title: console-setup/store_defaults_in_debconf_db: true keyboard-configuration/altgr: The default for the keyboard layout keyboard-configuration/toggle: No toggling console-setup/guess_font: keyboard-configuration/variant: Deutsch - Deutsch (ohne Akzenttasten) keyboard-configuration/model: Generische PC-Tastatur mit 105 Tasten (Intl) * console-setup/charmap47: UTF-8 * console-setup/fontsize-fb47: 8x16 keyboard-configuration/layoutcode: de keyboard-configuration/unsupported_layout: true keyboard-configuration/unsupported_config_options: true console-setup/codesetcode: Lat15 keyboard-configuration/compose: No compose key keyboard-configuration/unsupported_config_layout: true * console-setup/fontface47: Terminus keyboard-configuration/other: * console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic languages -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150428072757.30757.6531.report...@hermes.hilbert.loc
Bug#759657: console-setup: suggested fix seems to work
Package: console-setup Version: 1.122 Followup-For: Bug #759657 Out-of-band I received the suggestion to create /etc/systemd/system/console-setup.service.d/wait4udev.conf with the content [Unit] Wants=systemd-udev-settle.service After=systemd-udev-settle.service which delays running console-setup.service until after udev has settled thereby making sure loading the video driver and setting the final video mode has completed before console-setup.service is run. With this fix I have not been able to provoke the "forgotten setup" problem anymore in about ten soft and cold reboots. Karsten -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'stable-updates'), (500, 'stable'), (50, 'unstable'), (10, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.19.0-trunk-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages console-setup depends on: ii console-setup-linux 1.122 ii debconf 1.5.56 ii keyboard-configuration 1.122 ii xkb-data2.12-1 console-setup recommends no packages. Versions of packages console-setup suggests: ii locales2.19-18 ii locales-all [locales] 2.19-18 ii lsb-base 4.1+Debian13+nmu1 Versions of packages keyboard-configuration depends on: ii debconf 1.5.56 ii initscripts 2.88dsf-59 ii liblocale-gettext-perl 1.05-8+b1 Versions of packages console-setup-linux depends on: ii kbd 1.15.5-2 ii keyboard-configuration 1.122 console-setup-linux suggests no packages. Versions of packages console-setup is related to: pn console-common pn console-data pn console-tools ii kbd 1.15.5-2 -- debconf information: console-setup/fontsize-text47: 8x16 keyboard-configuration/switch: No temporary switch keyboard-configuration/xkb-keymap: de(nodeadkeys) * console-setup/charmap47: UTF-8 keyboard-configuration/layoutcode: de * console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic languages keyboard-configuration/layout: keyboard-configuration/altgr: The default for the keyboard layout keyboard-configuration/store_defaults_in_debconf_db: true keyboard-configuration/toggle: No toggling console-setup/fontsize: 8x16 keyboard-configuration/unsupported_layout: true keyboard-configuration/variant: Deutsch - Deutsch (ohne Akzenttasten) debian-installer/console-setup-udeb/title: console-setup/codesetcode: Lat15 keyboard-configuration/ctrl_alt_bksp: false console-setup/use_system_font: keyboard-configuration/unsupported_options: true keyboard-configuration/unsupported_config_options: true * console-setup/fontface47: Terminus keyboard-configuration/compose: No compose key console-setup/store_defaults_in_debconf_db: true console-setup/framebuffer_only: keyboard-configuration/other: keyboard-configuration/variantcode: nodeadkeys * console-setup/fontsize-fb47: 8x16 console-setup/guess_font: keyboard-configuration/model: Generische PC-Tastatur mit 105 Tasten (Intl) keyboard-configuration/optionscode: keyboard-configuration/unsupported_config_layout: true keyboard-configuration/modelcode: pc105 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150419111946.2225.77218.report...@hermes.hilbert.loc
Bug#759657: console-setup: system state after "fixing"
Package: console-setup Version: 1.121 Followup-For: Bug #759657 These are the system settings - after boot showing the wrong setup - but AFTER running systemctl restart console-setup.service - after which the setup is correct in other words just after the previous report, but "fixed". Maybe the system state below is any different ? I'll now test and report on the udev-settle fix that was suggested out-of-band. Karsten -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'stable-updates'), (500, 'stable'), (50, 'unstable'), (10, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.19.0-trunk-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages console-setup depends on: ii console-setup-linux 1.121 ii debconf 1.5.56 ii keyboard-configuration 1.121 ii xkb-data2.12-1 console-setup recommends no packages. Versions of packages console-setup suggests: ii locales2.19-17 ii locales-all [locales] 2.19-17 ii lsb-base 4.1+Debian13+nmu1 Versions of packages keyboard-configuration depends on: ii debconf 1.5.56 ii initscripts 2.88dsf-59 ii liblocale-gettext-perl 1.05-8+b1 Versions of packages console-setup-linux depends on: ii kbd 1.15.5-2 ii keyboard-configuration 1.121 console-setup-linux suggests no packages. Versions of packages console-setup is related to: pn console-common pn console-data pn console-tools ii kbd 1.15.5-2 -- debconf information: keyboard-configuration/variant: Deutsch - Deutsch (ohne Akzenttasten) * console-setup/fontface47: Terminus * console-setup/fontsize-fb47: 8x16 keyboard-configuration/model: Generische PC-Tastatur mit 105 Tasten (Intl) keyboard-configuration/toggle: No toggling keyboard-configuration/compose: No compose key keyboard-configuration/ctrl_alt_bksp: false keyboard-configuration/switch: No temporary switch keyboard-configuration/unsupported_options: true console-setup/codesetcode: Lat15 keyboard-configuration/layout: keyboard-configuration/xkb-keymap: de(nodeadkeys) keyboard-configuration/altgr: The default for the keyboard layout console-setup/framebuffer_only: keyboard-configuration/optionscode: keyboard-configuration/modelcode: pc105 console-setup/store_defaults_in_debconf_db: true keyboard-configuration/variantcode: nodeadkeys console-setup/use_system_font: console-setup/fontsize-text47: 8x16 keyboard-configuration/unsupported_config_options: true keyboard-configuration/other: keyboard-configuration/layoutcode: de keyboard-configuration/unsupported_config_layout: true debian-installer/console-setup-udeb/title: * console-setup/charmap47: UTF-8 keyboard-configuration/unsupported_layout: true console-setup/guess_font: console-setup/fontsize: 8x16 * console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic languages keyboard-configuration/store_defaults_in_debconf_db: true -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150419102102.24375.41142.report...@hermes.hilbert.loc
Bug#759657: console-setup: document settings #1
Package: console-setup
Version: 1.121
Followup-For: Bug #759657
This is just to document system information
- right after boot
- showing the wrong setup ("forgotten font")
- before "fixing" by reconfiguring console-setup
in case it is any different from the following report.
Karsten
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-updates'), (500,
'stable-updates'), (500, 'stable'), (50, 'unstable'), (10, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.19.0-trunk-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages console-setup depends on:
ii console-setup-linux 1.121
ii debconf 1.5.56
ii keyboard-configuration 1.121
ii xkb-data2.12-1
console-setup recommends no packages.
Versions of packages console-setup suggests:
ii locales2.19-17
ii locales-all [locales] 2.19-17
ii lsb-base 4.1+Debian13+nmu1
Versions of packages keyboard-configuration depends on:
ii debconf 1.5.56
ii initscripts 2.88dsf-59
ii liblocale-gettext-perl 1.05-8+b1
Versions of packages console-setup-linux depends on:
ii kbd 1.15.5-2
ii keyboard-configuration 1.121
console-setup-linux suggests no packages.
Versions of packages console-setup is related to:
pn console-common
pn console-data
pn console-tools
ii kbd 1.15.5-2
-- debconf information:
keyboard-configuration/ctrl_alt_bksp: false
console-setup/codesetcode: Lat15
keyboard-configuration/model: Generische PC-Tastatur mit 105 Tasten (Intl)
* console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic
languages
keyboard-configuration/xkb-keymap: de(nodeadkeys)
keyboard-configuration/unsupported_config_options: true
keyboard-configuration/modelcode: pc105
console-setup/framebuffer_only:
keyboard-configuration/variantcode: nodeadkeys
* console-setup/fontface47: Terminus
debian-installer/console-setup-udeb/title:
keyboard-configuration/layoutcode: de
keyboard-configuration/switch: No temporary switch
console-setup/fontsize-text47: 8x16
keyboard-configuration/unsupported_layout: true
keyboard-configuration/altgr: The default for the keyboard layout
keyboard-configuration/optionscode:
keyboard-configuration/other:
keyboard-configuration/compose: No compose key
keyboard-configuration/store_defaults_in_debconf_db: true
keyboard-configuration/toggle: No toggling
console-setup/use_system_font:
keyboard-configuration/variant: Deutsch - Deutsch (ohne Akzenttasten)
console-setup/fontsize: 8x16
keyboard-configuration/unsupported_config_layout: true
console-setup/guess_font:
keyboard-configuration/unsupported_options: true
keyboard-configuration/layout:
* console-setup/charmap47: UTF-8
* console-setup/fontsize-fb47: 8x16
console-setup/store_defaults_in_debconf_db: true
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/20150419101559.3894.74906.report...@hermes.hilbert.loc
Bug#759657: console-setup: still a problem
Package: console-setup Version: 1.119 Followup-For: Bug #759657 This bug still exists. Karsten -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'stable-updates'), (500, 'stable'), (50, 'unstable'), (10, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.19.0-trunk-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages console-setup depends on: ii console-setup-linux 1.119 ii debconf 1.5.55 ii keyboard-configuration 1.119 ii xkb-data2.12-1 console-setup recommends no packages. Versions of packages console-setup suggests: ii locales2.19-15 ii locales-all [locales] 2.19-15 ii lsb-base 4.1+Debian13+nmu1 Versions of packages keyboard-configuration depends on: ii debconf 1.5.55 ii initscripts 2.88dsf-58 ii liblocale-gettext-perl 1.05-8+b1 Versions of packages console-setup-linux depends on: ii kbd 1.15.5-2 ii keyboard-configuration 1.119 console-setup-linux suggests no packages. Versions of packages console-setup is related to: pn console-common pn console-data pn console-tools ii kbd 1.15.5-2 -- debconf information: keyboard-configuration/variant: Deutsch - Deutsch (ohne Akzenttasten) console-setup/fontsize: 8x16 console-setup/use_system_font: keyboard-configuration/store_defaults_in_debconf_db: true console-setup/fontsize-text47: 8x16 keyboard-configuration/toggle: No toggling keyboard-configuration/compose: No compose key keyboard-configuration/optionscode: keyboard-configuration/xkb-keymap: de(nodeadkeys) * console-setup/fontface47: Terminus * console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic languages console-setup/framebuffer_only: keyboard-configuration/unsupported_config_options: true keyboard-configuration/model: Generische PC-Tastatur mit 105 Tasten (Intl) keyboard-configuration/unsupported_layout: true * console-setup/fontsize-fb47: 8x16 keyboard-configuration/modelcode: pc105 keyboard-configuration/other: keyboard-configuration/unsupported_options: true keyboard-configuration/layoutcode: de keyboard-configuration/switch: No temporary switch console-setup/codesetcode: Lat15 keyboard-configuration/variantcode: nodeadkeys keyboard-configuration/ctrl_alt_bksp: false keyboard-configuration/unsupported_config_layout: true keyboard-configuration/layout: console-setup/guess_font: keyboard-configuration/altgr: The default for the keyboard layout * console-setup/charmap47: UTF-8 debian-installer/console-setup-udeb/title: console-setup/store_defaults_in_debconf_db: true -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150324074850.2967.34305.report...@hermes.hilbert.loc
Bug#759657: console-setup w/ systemd forgets font setting
Package: console-setup Version: 1.111 Severity: normal When systemd was introduced console-setup started to "forget" setting the font selected with debconf (as seen below). Initially, it was only every so often but since about yesterday it doesn't load the font on every single boot. This is hampering productivity on the console a _lot_. The problem can be corrected by running dpkg-reconfigure console-setup but that only lasts until the next boot. Let me know if you need more information. Thanks, Karsten -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'stable-updates'), (500, 'stable'), (50, 'unstable'), (10, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.16-trunk-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages console-setup depends on: ii console-setup-linux 1.111 ii debconf 1.5.53 ii keyboard-configuration 1.111 ii xkb-data2.12-1 console-setup recommends no packages. Versions of packages console-setup suggests: ii locales2.19-9 ii locales-all [locales] 2.19-9 ii lsb-base 4.1+Debian13 Versions of packages keyboard-configuration depends on: ii debconf 1.5.53 ii initscripts 2.88dsf-53.3 ii liblocale-gettext-perl 1.05-8+b1 Versions of packages console-setup-linux depends on: ii kbd 1.15.5-1 ii keyboard-configuration 1.111 console-setup-linux suggests no packages. Versions of packages console-setup is related to: pn console-common pn console-data pn console-tools ii kbd 1.15.5-1 -- debconf information: * console-setup/fontsize-fb47: 8x16 keyboard-configuration/ctrl_alt_bksp: false keyboard-configuration/layoutcode: de debian-installer/console-setup-udeb/title: keyboard-configuration/altgr: The default for the keyboard layout keyboard-configuration/model: Generische PC-Tastatur mit 105 Tasten (Intl) * console-setup/charmap47: UTF-8 console-setup/store_defaults_in_debconf_db: true keyboard-configuration/other: console-setup/framebuffer_only: keyboard-configuration/compose: No compose key keyboard-configuration/variant: Deutsch - Deutsch (ohne Akzenttasten) keyboard-configuration/unsupported_layout: true keyboard-configuration/optionscode: console-setup/fontsize-text47: 8x16 console-setup/codesetcode: Lat15 keyboard-configuration/unsupported_config_layout: true * console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic languages keyboard-configuration/layout: keyboard-configuration/switch: No temporary switch keyboard-configuration/store_defaults_in_debconf_db: true keyboard-configuration/toggle: No toggling console-setup/fontsize: 8x16 console-setup/guess_font: keyboard-configuration/unsupported_config_options: true keyboard-configuration/xkb-keymap: de(nodeadkeys) keyboard-configuration/modelcode: pc105 * console-setup/fontface47: Terminus console-setup/use_system_font: keyboard-configuration/unsupported_options: true keyboard-configuration/variantcode: nodeadkeys -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140829075320.2819.32149.report...@hermes.hilbert.loc
