Bug#760993: console-setup: CHARMAP no longer set properly
On Thu, Feb 18, 2016 at 08:10:54PM +0100, Kurt Roeckx wrote: > On Thu, Feb 18, 2016 at 06:16:26PM +0200, Anton Zinoviev wrote: > > On Tue, Sep 09, 2014 at 08:18:01PM +0200, Kurt Roeckx wrote: > > > Package: console-setup > > > Version: 1.111 > > > Severity: important > > > > > > In /etc/default/console-setup I have: > > > CHARMAP="ISO-8859-1" > > > > > > However, my console acts like it's in UTF-8 mode. > > > > > > If I restart the console-setup service it does get properly set, > > > so I'm guessing something else is overriding it. > > > > Hello! > > > > Do you remember if this system used systemd? > > > > Did you use the standard the QWERTY layout? I mean is it possible that > > the console was leaved unconfigured (not only the charmap, but also the > > keyboard) and the only reason you didn't notice this was that you used > > QWERTY layout? > > I have no idea on which system this was. At least on this one I > don't have console-setup installed, and I think it's currently the > only one without systemd. I'm going to guess it was on this one > anyway. > > All my systems are using qwerty. I might also have configured it > to not touch the font. It is a known bug that very often console-setup doesn't configure the console during the boot if the system is using systemd. This bug is going to be fixed in a next release, so I asked you this question in order fo find out if the same fix is going to fix the bug you reported as well. On one hand, you use qwerty layout and (sometimes) the system font. This means if the bug was observed on a system with systemd then it seems very likely that the bug you reported is identical with the bug "console-setup doesn't configure the console on boot with systemd". In this case we will be able to close both bugs. On the other hand, you suspect that the bug was observed on the system you used to write your last email message. You say that currently console-setup is not installed on this system. Unfortunately, your original bug report doesn't contain information whether console-setup was installed at the time you reported the bug, or not. If console-setup was not installed, then the symptoms you reported are expected even if keyboard-configuration was installed. So, what do you prefer we do with this bug? Anton Zinoviev
Bug#760993: console-setup: CHARMAP no longer set properly
On Thu, Feb 18, 2016 at 06:16:26PM +0200, Anton Zinoviev wrote: > On Tue, Sep 09, 2014 at 08:18:01PM +0200, Kurt Roeckx wrote: > > Package: console-setup > > Version: 1.111 > > Severity: important > > > > In /etc/default/console-setup I have: > > CHARMAP="ISO-8859-1" > > > > However, my console acts like it's in UTF-8 mode. > > > > If I restart the console-setup service it does get properly set, > > so I'm guessing something else is overriding it. > > Hello! > > Do you remember if this system used systemd? > > Did you use the standard the QWERTY layout? I mean is it possible that > the console was leaved unconfigured (not only the charmap, but also the > keyboard) and the only reason you didn't notice this was that you used > QWERTY layout? I have no idea on which system this was. At least on this one I don't have console-setup installed, and I think it's currently the only one without systemd. I'm going to guess it was on this one anyway. All my systems are using qwerty. I might also have configured it to not touch the font. Kurt
Bug#760993: console-setup: CHARMAP no longer set properly
On Tue, Sep 09, 2014 at 08:18:01PM +0200, Kurt Roeckx wrote: > Package: console-setup > Version: 1.111 > Severity: important > > In /etc/default/console-setup I have: > CHARMAP="ISO-8859-1" > > However, my console acts like it's in UTF-8 mode. > > If I restart the console-setup service it does get properly set, > so I'm guessing something else is overriding it. Hello! Do you remember if this system used systemd? Did you use the standard the QWERTY layout? I mean is it possible that the console was leaved unconfigured (not only the charmap, but also the keyboard) and the only reason you didn't notice this was that you used QWERTY layout? Anton Zinoviev
Bug#760993: console-setup: CHARMAP no longer set properly
On Thu, Sep 11, 2014 at 06:44:37PM +0200, Kurt Roeckx wrote: So I changed both FORK cases to be: $cmd $@ That doesn't change anything, and I don't see why that should change anything. Strange things can happen early in the boot process and this is the only relevant change between the recent versions of console-setup and the previous versions (and the previous versions have been tested for more than an year, so I trust they don't have the bug you reported). There have been bug reports about console-setup hanging because (maybe?) of non-existent devices /dev/ttyN. Nobody knows the cause of this and the forks in the present version of console-setup are there to fight this. Now, imagine this is what happens in your system. The previous version of console-setup would hang but the present is going to fork hanging printf commands instead. These printf commands are what configures the console from UTF-8 to 8-bit mode. We can hope that eventualy /dev/ttyN will activate and the printf will do its job, but who knows... maybe something is killing these processes (init, systemd, whatever). Anton Zinoviev -- 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/20140912132341.ga11...@logic.fmi.uni-sofia.bg
Bug#760993: console-setup: CHARMAP no longer set properly
On Tue, Sep 09, 2014 at 08:18:01PM +0200, Kurt Roeckx wrote: In /etc/default/console-setup I have: CHARMAP=ISO-8859-1 However, my console acts like it's in UTF-8 mode. If I restart the console-setup service it does get properly set, so I'm guessing something else is overriding it. In order to be sure that that the culprit is not console-setup but other program, do this: Open /bin/setupcon in a text editor and find the following block: elif [ $do_verbose ]; then case $verbose in NONE) report executing $cmd $@. $cmd $@ ;; FORK) # no arguments to suppress '\033%%@' and '\033%%G' report executing $cmd. $cmd $@ ;; *) report executing $cmd $@. $cmd $@ $verbose ;; esac else case $verbose in NONE) report executing $cmd $@. $cmd $@ /dev/null 21 ;; FORK) # no arguments to suppress '\033%%@' and '\033%%G' report executing $cmd. $cmd $@ ;; *) report executing $cmd $@. $cmd $@ ;; esac Then remove the symbol '' from both lines $cmd $@ Does the problem disappear if you do this? Anton Zinoviev -- 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/20140911160313.ga24...@logic.fmi.uni-sofia.bg
Bug#760993: console-setup: CHARMAP no longer set properly
On Thu, Sep 11, 2014 at 07:03:13PM +0300, Anton Zinoviev wrote: On Tue, Sep 09, 2014 at 08:18:01PM +0200, Kurt Roeckx wrote: In /etc/default/console-setup I have: CHARMAP=ISO-8859-1 However, my console acts like it's in UTF-8 mode. If I restart the console-setup service it does get properly set, so I'm guessing something else is overriding it. In order to be sure that that the culprit is not console-setup but other program, do this: Open /bin/setupcon in a text editor and find the following block: elif [ $do_verbose ]; then case $verbose in NONE) report executing $cmd $@. $cmd $@ ;; FORK) # no arguments to suppress '\033%%@' and '\033%%G' report executing $cmd. $cmd $@ ;; *) report executing $cmd $@. $cmd $@ $verbose ;; esac else case $verbose in NONE) report executing $cmd $@. $cmd $@ /dev/null 21 ;; FORK) # no arguments to suppress '\033%%@' and '\033%%G' report executing $cmd. $cmd $@ ;; *) report executing $cmd $@. $cmd $@ ;; esac Then remove the symbol '' from both lines $cmd $@ Does the problem disappear if you do this? So I changed both FORK cases to be: $cmd $@ That doesn't change anything, and I don't see why that should change anything. Kurt -- 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/20140911164437.ga21...@roeckx.be
Bug#760993: console-setup: CHARMAP no longer set properly
Package: console-setup Version: 1.111 Severity: important Hi, In /etc/default/console-setup I have: CHARMAP=ISO-8859-1 However, my console acts like it's in UTF-8 mode. If I restart the console-setup service it does get properly set, so I'm guessing something else is overriding it. Kurt -- 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/20140909181801.ga6...@roeckx.be
