Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #814935
| From | Anton Zinoviev <anton@lml.bas.bg> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.maint.boot |
| Subject | Bug#857132: console-setup: additional info needed ? |
| Date | 2017-03-23 14:10 +0100 |
| Message-ID | <toaF4-2Eh-11@gated-at.bofh.it> (permalink) |
| References | <tnLQm-Xe-17@gated-at.bofh.it> <tnMCK-1Dh-7@gated-at.bofh.it> <tnNfr-2bK-1@gated-at.bofh.it> <tnObw-2PV-15@gated-at.bofh.it> <to7QR-Io-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
[I am sending a CC to pkg-systemd-maintainers@lists.alioth.debian.org] On Thu, Mar 23, 2017 at 11:07:14AM +0100, Sven Joachim wrote: > > 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. > > 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. Since systemd makes some configuration of the console, maybe the following scenario might explain what we observe: 1. systemd/udev creates a new console. 2. systemd begins the initialization of this console. 3. udev runs /etc/console-setup/cached_setup_font.sh by the following rule: ACTION=="add", SUBSYSTEM=="vtconsole", KERNEL=="vtcon*", RUN+="/etc/console-setup/cached_setup_font.sh" 4. Now cached_setup_font.sh and systemd execute in parallel. If cached_setup_font.sh wins, it will configure the console font first and then systemd will load another font. My tests of how systemd works show that it does the following: 1. It reads the curent font of the current console. 2. Then it does some things to the console(s) (configuration). 3. When a new console is created it loads on it the font read in 1. Therefore, it seems to me that if cached_setup_font.sh completes its job before 1. then everything should be ok. And if systemd completes its configuration before cached_setup_font.sh starts its work, then again everything will be ok. However if both work simultaneously things can go wrong. 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. Anton Zinoviev
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#857132: console-setup: additional info needed ? Karsten Hilbert <karsten.hilbert@gmx.net> - 2017-03-22 11:40 +0100
Bug#857132: console-setup: additional info needed ? Anton Zinoviev <anton@lml.bas.bg> - 2017-03-22 12:30 +0100
Bug#857132: console-setup: additional info needed ? Karsten Hilbert <Karsten.Hilbert@gmx.net> - 2017-03-22 13:10 +0100
Bug#857132: console-setup: additional info needed ? Anton Zinoviev <anton@lml.bas.bg> - 2017-03-22 14:10 +0100
Bug#857132: console-setup: additional info needed ? Karsten Hilbert <Karsten.Hilbert@gmx.net> - 2017-03-22 15:30 +0100
Bug#857132: console-setup: additional info needed ? Anton Zinoviev <anton@lml.bas.bg> - 2017-03-22 16:00 +0100
Bug#857132: console-setup: additional info needed ? Karsten Hilbert <Karsten.Hilbert@gmx.net> - 2017-03-22 18:10 +0100
Bug#857132: console-setup: additional info needed ? Anton Zinoviev <anton@lml.bas.bg> - 2017-03-22 20:00 +0100
Bug#857132: console-setup: additional info needed ? Karsten Hilbert <Karsten.Hilbert@gmx.net> - 2017-03-22 22:30 +0100
Bug#857132: console-setup: additional info needed ? Sven Joachim <svenjoac@gmx.de> - 2017-03-23 11:10 +0100
Bug#857132: console-setup: additional info needed ? Karsten Hilbert <Karsten.Hilbert@gmx.net> - 2017-03-23 11:40 +0100
Bug#857132: console-setup: additional info needed ? Anton Zinoviev <anton@lml.bas.bg> - 2017-03-24 07:40 +0100
Bug#857132: console-setup: additional info needed ? Anton Zinoviev <anton@lml.bas.bg> - 2017-03-23 14:10 +0100
Bug#857132: console-setup: additional info needed ? Karsten Hilbert <Karsten.Hilbert@gmx.net> - 2017-03-23 14:30 +0100
Bug#857132: console-setup: additional info needed ? Michael Biebl <biebl@debian.org> - 2017-03-23 14:40 +0100
Bug#857132: console-setup: additional info needed ? Anton Zinoviev <anton@lml.bas.bg> - 2017-03-23 15:10 +0100
Bug#857132: console-setup: additional info needed ? Michael Biebl <biebl@debian.org> - 2017-03-23 15:40 +0100
Bug#857132: console-setup: additional info needed ? Anton Zinoviev <anton@lml.bas.bg> - 2017-03-23 15:50 +0100
Bug#857132: console-setup: additional info needed ? Felipe Sateler <fsateler@debian.org> - 2017-03-23 18:20 +0100
Bug#857132: console-setup: additional info needed ? Anton Zinoviev <anton@lml.bas.bg> - 2017-03-23 19:10 +0100
Bug#857132: console-setup: additional info needed ? Karsten Hilbert <Karsten.Hilbert@gmx.net> - 2017-03-24 12:00 +0100
Bug#857132: console-setup: additional info needed ? Karsten Hilbert <Karsten.Hilbert@gmx.net> - 2017-03-26 16:10 +0200
Bug#857132: console-setup: additional info needed ? Anton Zinoviev <anton@lml.bas.bg> - 2017-03-26 19:50 +0200
Bug#857132: console-setup: additional info needed ? Karsten Hilbert <Karsten.Hilbert@gmx.net> - 2017-03-26 20:30 +0200
Bug#857132: console-setup: additional info needed ? Anton Zinoviev <anton@lml.bas.bg> - 2017-03-26 23:10 +0200
Bug#857132: console-setup: additional info needed ? Karsten Hilbert <Karsten.Hilbert@gmx.net> - 2017-03-27 10:20 +0200
Bug#857132: console-setup: additional info needed ? Karsten Hilbert <Karsten.Hilbert@gmx.net> - 2017-04-05 12:00 +0200
Bug#857132: console-setup: additional info needed ? Karsten Hilbert <Karsten.Hilbert@gmx.net> - 2017-04-07 12:40 +0200
Bug#857132: console-setup: additional info needed ? Sven Joachim <svenjoac@gmx.de> - 2017-03-23 19:20 +0100
csiph-web