Does anyone have any objections to me adopting it? Anton?
I believe partman-btrfs is maintained by the whole d-i team and my name
there is for historical reasons. So, go ahead.
Anton Zinoviev
On Sun, Sep 20, 2020 at 10:18:07PM +0200, Holger Wansing wrote:
>
> any objections against me uploading console-setup with this pending
> changings?
Go ahead. Usually I am pushing in the archive only changes that I
consider ok for upload.
Anton Zinoviev
On Mon, Jul 20, 2020 at 09:03:33PM -0400, Nick Black wrote:
>
> Tested all three using the same methodology as outlined earlier.
>
> Looks perfect =].
Thanks.
Anton Zinoviev
ched updated versions of Arabic-Fixed16.psf,
Arabic-VGA16.psf and Lat15-Terminus16.psf. Hopefully, this time the
fonts are ok.
> Will this work be going upstream? I'm not clear on whether
> you're the upstream maintainer, or just Debian's.
In this case Debian = upstream.
Anton Zinoviev
A
X -> U+002D HYPHEN-MINUS or, if you prefer,
> U+004F LATIN CAPITAL LETTER O
What about these?
. for U+2610 BALLOT BOX
v for U+2611 BALLOT BOX WITH CHECK
x for U+2612 BALLOT BOX WITH X
Anton Zinoviev
On Tue, Jul 14, 2020 at 12:54:59PM -0400, Nick Black wrote:
>
> I'm happy to make these patches and send them upstream, but Anton Zinoviev
> requested that I file a bug here.
In this way the requiest is documented. More difficult to forget about it...
> I consider the following
ending on Linux-specific packages.
Why is it a problem to have an arch:all package which is installable
only on some architectures (due to missing dependencies)?
Anton Zinoviev
On Thu, Dec 20, 2018 at 06:02:47PM +, Dmitry Bogatov wrote:
>
> Anton, could you please clarify, how locale is set up by this function
> call if process inhereted no locale-related variables.
I don't know.
Anton Zinoviev
so make sure there are no files ~/.inutrc and the variable INPUTRC is
unset.
Anton Zinoviev
On Fri, Jun 01, 2018 at 04:28:23PM +0200, Samuel Thibault wrote:
>
> Maybe we should just go and define all X11 deadkeys in Linux (there
> are like 55 of them, that will fit), to be done with the issue.
Either this, or console-setup can have a hardcoded list of "Latin2"
sting
> rule.
And what should the future console-setup do with compose+^+S when the
encoding is UTF-8? How is this problem solved in X?
Anton Zinoviev
On Thu, May 31, 2018 at 11:12:43PM +0300, Anton Zinoviev wrote:
>
> only important bugs are fixed
I realised the word 'important' was very inapropriate in this context.
What is unimportant for one user can be very important for another. So
by 'important' bugs I meant things
think this could be fixed right in the Stretch.
When I have time I will upload a fixed package to Unstable.
I am not sure, but I think only important bugs are fixed in the stable
releases of Debian. Unless there is some change in the policies of
Debian of which I am not aware (which is not impossible, to be
honest...).
Anton Zinoviev
MAP=/etc/console-setup/cz.kmap
Remove this line from /etc/default/keyboard when you receive a message
that the bug has been fixed.
Anton Zinoviev
z-lat2-prog.kmap.gz
loadkeys cz-us-qwertz.kmap.gz
loadkeys sunt5-cz-us.kmap.gz
loadkeys sunt5-us-cz.kmap.gz
Anton Zinoviev
A is another nice font which is developed as x9 font but
is packaged as x8. Also all x8 VGA fonts and the non-bold Terminus font
are designed to look ok if they are used as x9 fonts.
Anton Zinoviev
its work. This solution works only because requiring
/tmp to be mounted means some other dependency will be satisfied as
well. But who knows what this other dependency is...
Anton Zinoviev
ithout-systemd.org.
Anton Zinoviev
and not
setupcon /etc/console-setup/cached_Lat15-TerminusBold24x12.psf.gz
Anton Zinoviev
On Sun, Jul 23, 2017 at 10:50:56PM +0200, Harry Haller wrote:
>
> The changes of the console after "dpkg-reconfigure console-setup" are
> as expected,
Does the console configure properly (even if only temporarily) if you
run "setupcon" instead of "dpkg-
e other scripts are short
and simple and do not require temporary files.
On the other hand, it seems likely to me that this bug is a duplicate of
#819288.
Anton Zinoviev
of 857132 and 861454. Unfortunately
nobody has been able to find the cause of this bug.
Anton Zinoviev
described earlier - a minimal installation without
> the standard utilities or a DE.
>
> Yes, it has systemd. However, I note that the one unstable machine I
> have with sysvinit does not exhibit this issue.
Then it seems this is a duplicate of the misterious bug #857132.
Anton Zinoviev
TFACE="TerminusBold"
> FONTSIZE="11x22"
>
> in /etc/default/console-setup.
What about /etc/console-setup/cached_setup_font.sh?
Something unusual about the kernel? Read-only file systems? With or
without systemd?
Anton Zinoviev
X developers.
Fortunately, this is not necessary because the type files define only a
few types and it is not difficult to hardcode the proper behaviour in
ckbcomp.
Anton Zinoviev
- Forwarded message from Torne Wuff -
Date: Thu, 6 Apr 2017 21:21:39 -0400
From: Torne Wuff
To: 620...@bugs.debian.org
Subject: Bug#620041:
Being able to set the font during initramfs would be immensely useful on my
HiDPI laptop, since the default console font renders the LUKS decryption
-setup does not try to do this. Which is unfortunate because
earlier versions of console-setup included font configuration in initrd.
Anton Zinoviev
py the altgr
part of the pc keyboard to the macintosh one.
Anton Zinoviev
s in the keyboard-configuration setup reduced to
> what's really available (it took me quite a long time to understand
> why I couldn't get the accents though everything looked fine).
Yes, this is an unfortunate bug which is reported from time to time.
Unfortunately, it can not be fixed because of
https://bugs.freedesktop.org/show_bug.cgi?id=33670
Anton Zinoviev
hink for early logs /run/initramfs/ can be used. Also
/usr/bin/logger might be able to help.
Anton Zinoviev
nt: no matter whether it runs in parallel or not --
the console is never configured properly? Or sometimes it is?
Anton Zinoviev
yet. And it would be
impossible to see an empty console without getty running on it.
Ofcourse, this doesn't explain why the configuration doesn't work --
because something overwrites it or because the configuration is
performed too early, while the system is not prepared for it yet.
Anton Zinoviev
t create problems. On the other hand,
if udev always runs cached_setup_font again, do both copies run in
parallel (this shoudn't be a problem for cached_setup_font but it is
good to know if such possibility exists)?
Anton Zinoviev
On Thu, Mar 23, 2017 at 03:30:36PM +0100, Michael Biebl wrote:
> >
> > ...suppose udev creates a new console. Then it has to be initialized
> > with some font, hasn't it?
>
> udev does not create any consoles. That's a misconception.
Well, whoever does it... :)
Anton Zinoviev
rule
ACTION=="add", SUBSYSTEM=="vtconsole", KERNEL=="vtcon*",
RUN+="/etc/console-setup/cached_setup_font.sh"
however the font of the current console is read _before_ the script
cached_setup_font.sh has had a chance to configure the font?
Anton Zinoviev
ything 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
sole-setup.service` you can use
the command `setupcon`.
Anton Zinoviev
On Wed, Mar 22, 2017 at 03:19:57PM +0100, Karsten Hilbert wrote:
> On Wed, Mar 22, 2017 at 03:02:28PM +0200, Anton Zinoviev wrote:
> >
> > 2. the bug still exists and each time the system boots, it recreates
> > these three files. In this case we have
t.sh.
> > cat /etc/default/console-setup
> > cat /etc/default/keyboard
These look ok as well...
Anton Zinoviev
-setup/cached_setup_terminal.sh
cat /etc/default/console-setup
cat /etc/default/keyboard
Anton Zinoviev
On Fri, Mar 17, 2017 at 08:17:42AM +0100, Jörn Heissler wrote:
>
> It appears to me that "Set console font and keymap" is done before
> live-config regenerates the files.
I think this explains the bug.
Anton Zinoviev
ched files to be more
recent than /etc/default/keyboard?
Anton Zinoviev
On Wed, Mar 08, 2017 at 12:02:45PM +0100, Karsten Hilbert wrote:
>
> console-setup just stopped to apply font settings during startup.
Does this system has some read-only file systems?
Anton Zinoviev
On Thu, Feb 09, 2017 at 10:46:01AM +0100, Christian PERRIER wrote:
>
> assuming from your word that the patch is OK...:-)
I hate when people rely on my word too much... :-)
Anton Zinoviev
.138~ -- "$@"
-dpkg-maintscript-helper rm_conffile /etc/init.d/console-setup 1.138~ -- "$@"
#DEBHELPER#
In this way the change becomes obvious --- only the order of execution
of the commands is changed. Rationale: according to update-rc.d(8) "The
script must have been deleted already. If the script is still present
then update-rc.d aborts with an error message." This, indeed, means
that update-rc.d has to be run before dpkg-maintscript-helper rm_conffile.
Anton Zinoviev
p; do
> if [ -x /etc/init.d/$file ]; then
> dpkg-maintscript-helper rm_conffile /etc/init.d/$file 1.138~ -- "$@"
> update-rc.d $file remove >/dev/null
> fi
> done
Thanks.
Anton Zinoviev
and the
keyboard is configured by /lib/systemd/system/keyboard-setup.service.
> As it is a live-image, every boot is "first boot" as Anton said could
> give issue.
How big is is this image? Will it be possible to send it to me so I can
test?
Anton Zinoviev
a-Terminus16.log (the first
font is for BSD, the second for Linux)?
Can you try building the package using clean sources, without any
changes, and see if this helps.
Anton Zinoviev
defined in most (all?) source fonts. I don't get such a message
when I build the package. What does the following command output:
grep '2116: no glyph defined' Fonts/*.log
Anton Zinoviev
/bdf. This particular
warning means that no suitable source font includes this glyph, so it has
been impossible to support it in the generated console font.
Anton Zinoviev
mmited a change that will make console-setup use untranslated
keyboard names in case of failed iconv. This should fix the bug in
console-setup. Of course, when we have more data or something
reproducible we can submit a bug against libc-bin.
Anton Zinoviev
his script here?
http://bugs.debian.org/420914
Anton Zinoviev
oment I don't have updated Debian machine so I can not debug.
Conceivably, the fix will be trivial. I don't know if the following
will fix the bug and if this is the right thing to do, but it seems
simple to change the first line
#!/usr/bin/perl
of Keyboard/kbdcompiler and Keyboard/kbdn
were upgraded after console-setup and
before the Linux kernel and nvidia?
> This error message is just a consequence of this bug.
Yes. The error message was added in version 1.138 after I became aware
that other packages modify the configuration file of console-setup.
Anton Zinoviev
ore empty braces
problems, it would be safer to protect against bugs caused by future
changes.
> How about just adding : to each brace, as in the following patch.
I like this solution.
Anton Zinoviev
/etc is not something we want in single user mode.
Anton Zinoviev
On Wed, May 18, 2016 at 12:12:29PM +, Holger Levsen wrote:
>
> it fails to build now, quoting from
> https://jenkins.debian.net/job/d-i_build_console-setup/211/console:
Thanks. Hopefuly, now it is fixed.
Anton Zinoviev
DefaultDependencies=no
After=console-screen.service kbd.service local-fs.target
RequiresMountsFor=/usr
ConditionPathExists=/bin/setupcon
[Service]
Type=oneshot
ExecStart=/lib/console-setup/console-setup.sh
RemainAfterExit=yes
Anton Zinoviev
arget
What about the following additional instruction: RequiresMountsFor=/usr
> Before=system-getty.slice
Nothing really serious is going to happen if this script is executed
after getty. Wouldn't it be better to remove this instruction?
Anton Zinoviev
TEST=="/run/console-setup/font-loaded",
> > RUN+="/etc/console-setup/cached_setup_terminal.sh %k"
> >
> > In theory this should reconfigure a tty each time it is allocated.
>
> I will give that a try. Will give you feedback.
At least with systemd this works. I wonder what makes mingetty different.
Anton Zinoviev
", KERNEL=="vcs[1-9]|vcs[1-9][0-9]",
TEST=="/run/console-setup/font-loaded",
RUN+="/etc/console-setup/cached_setup_terminal.sh %k"
In theory this should reconfigure a tty each time it is allocated.
Anton Zinoviev
s file contain a line like
this one:
1:2345:respawn:/sbin/getty 38400 tty1
Anton Zinoviev
that you put the files *.service in the package
console-setup-freebsd and (as far as I can tell) this doesn't seem an
oversight but rather done by intention. Why?
I think that the non-Linux ports of Debian do not use systemd or am I missing
something?
Anton Zinoviev
ot all necessary files were present in
/etc/console-setup. Normally setupcon does not run ckbcomp and in the
recent versions of console-setup (>=1.138) the keyboard-setup.sh init
script does not run setupcon.
Anton Zinoviev
On Thu, Apr 07, 2016 at 01:06:10AM +0300, Anton Zinoviev wrote:
>
> Unfortunately, at the moment I have no idea what might have caused this
> strange behaviour.
Ah, it just occured to me that maybe you have observed the following:
1. fsck displays its messages with correct non-break
aking space
> is better.
On the console 'non-breaking space' = 'space'.
Anton Zinoviev
On Sun, Mar 27, 2016 at 12:06:39PM -0300, Felipe Sateler wrote:
>
> But, maybe setupcon should force remove the cached script if it
> contains references to /tmp (or better yet, the script does not match
> /etc/console-setup/cached_*.map.gz)
Yes, something has to be done about
x somehow. However, an important question we have to
investigate here is this: why in your system the cached scripts rely on
files in /tmp.
Anton Zinoviev
irtual terminal,
No.
> Why is console-setup so slow?
It is not. :)
Anton Zinoviev
r
(where the sources of console-setup are), or not, but in any case I
think you can obtain such rights in no time.
Anton Zinoviev
le more than once?
Anton Zinoviev
configuration when there was a file with *600*?
> According to my own tests it is save to 'rm /etc/console-setup/*.gz'
It is safe to 'rm /etc/console-setup/cached_*'. These files can be
recreated by 'setupcon --save-only'.
Anton Zinoviev
tial understanding from people not already familiar with the
> package.
I agree in 100% with this.
Anton Zinoviev
e
> right thing when initscripts is not installed (ie, not abort the
> installation).
Another problem is the $remote_fs dependency of console-setup.sh. See
#621077.
Anton Zinoviev
onPathDoesntExist?
If yes, then we can use two units like these:
Unit 1:
ConditionPathExists=/etc/console-setup/cached_setup_keyboard.sh
ExecStart=/etc/console-setup/cached_setup_keyboard.sh
Unit 2:
ConditionPathDoesntExist=/etc/console-setup/cached_setup_keyboard.sh
ConditionPathExists=/bin/setupcon
ExecStart=/bin/setupcon --keyboard-only
Anton Zinoviev
etupcon
in order to configure the console. It is OK to configure the keyboard
in this way, but this usually will be slower than what the script
keyboard-setup.sh does -- instead of setupcon it runs
/etc/console-setup/cached_setup_keyboard.sh and reverts to using
setupcon only when this script
On Mon, Feb 29, 2016 at 04:41:41PM -0300, Felipe Sateler wrote:
> On 29 February 2016 at 15:22, Anton Zinoviev <an...@lml.bas.bg> wrote:
>
> > this script will move out of runlevel S on Linux and on FreeBSD there is no
> > systemd.
>
> Interesting. Why is it no lon
tags 796603 -help
thanks
On Mon, Feb 29, 2016 at 09:54:23AM -0300, Felipe Sateler wrote:
>
> On Mon, 22 Feb 2016 19:33:28 +0300 Anton Zinoviev <an...@lml.bas.bg> wrote:
> > tags 796603 + help patch
>
> I see you tagged this bug help. What can I do to help move
the sysadmin has to run
manually 'setupcon --save-only' when the installation completes and each time
he
modifies the configuration files of console-setup.
With the next release, I don't know yet.
Anton Zinoviev
s
is incorrect because console-setup relies on /usr being available and /usr is
provided by $remote_fs.
Anton Zinoviev
after running dpkg-reconfigure, the setting is not correctly restored
> after a reboot.
I expect a fixed package will be ready in a few days.
Anton Zinoviev
le-setup, some other package must have corrupted
/etc/default/keyboard but I have no idea which one.
Therefore, I'd like to ask you: Have you observed this bug in situations when
you
are certain you haven't used gnome-control-center or some other configuration
program based on systemd/localed?
Anton Zinoviev
On Sun, Aug 10, 2014 at 08:10:59PM +0300, Anton Zinoviev wrote:
> On Sun, Aug 10, 2014 at 04:36:50PM +0300, Victor Porton wrote:
> >
> > When the keyboard is in English mode, AltGr has no effect.
> >
> > When the keyboard is in Russian mode, holding AltGr temporarily
&
-setup removed the files
leaved
by older versions but there is nothing we can do about this, so not much will
be
gained if we keep the bug open.
Anton Zinoviev
son it removes XKBOPTIONS and
XKBMODEL is that it tries to do something with these variables.
Anton Zinoviev
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: im
but also the
keyboard) and the only reason you didn't notice this was that you used
QWERTY layout?
Anton Zinoviev
won't be able to fix later (because I don't
have the necessary time now).
Anton Zinoviev
; I suspect
that all of them are used very rarely.
Anton Zinoviev
going to help?
One of the things I have in my todo list for console-setup is to make it
work during the initrd phase. Therefore, it will be preferable if the
setup of the console doesn't run setupcon directly but by means of the
boot scripts in /etc/init.d because these scripts can check whether the
initrd has set already the console up or not.
Anton Zinoviev
depend on Debian specifics (such as the way
systemd and initrd are implemented).
Anton Zinoviev
On Wed, Dec 16, 2015 at 03:21:22PM +0100, Michael Biebl wrote:
> Am 16.12.2015 um 15:16 schrieb Anton Zinoviev:
> > On Wed, Dec 16, 2015 at 02:22:49PM +0100, Michael Biebl wrote:
> >>
> >> Wouldn't be hard to add this check to setupcon itself.
> >
> >
stemd too complex and so far I
haven't have enough time to learn how exactly it works. Therefore, for
the time being I am not qualified to work on this bug.
However console-setup has many contributors. Hopefully one of them
will be able to fix this bug.
Anton Zinoviev
ime
max: for reading log files
Anton Zinoviev
On Thu, Aug 27, 2015 at 03:18:17PM -0300, Felipe Sateler wrote:
>
> Does console-setup actually need to be run before user services are
> started? My guess is that it only needs to run before getty, but it
> should not block other services that want to start.
It should run before
for the other initrd-builders.
If the console is configured, then the main scripts of console-setup don't have
to
reconfigure the console again. Right now they do reconfigure it but it is in
my TODO
list to fix this.
Anton Zinoviev
to the information in
your bug report when you did dpkg-reconfigure keyboard-configuration you
chose an internationalised version of the standard 'us' layout. What
problems do you observe with this layout?
Anton Zinoviev
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject
will be able to use the combination
kbd_mode+loadkeys+kbd_leds in order to configure the keyboard.
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
-setup for handling hotplugged keyboards,
Ok, the inconvenience is not a problem. The problem is I don't
understant the meaning of this. :)
Is there some documentation or a sample code I can read?
Anton Zinoviev
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject
be executed only in Linux console.
Sorry for not having a patch ready. There can be several approaches, from
setting 'Conflicts: systemd-sysv' to providing a systemd unit file which
sets the TTY as needed.
I like the solution 'Conflicts: systemd-sysv'. :)
Anton Zinoviev
--
Ако не отговарям на
1 - 100 of 764 matches
Mail list logo
