On Fri, Feb 26, 2016 at 11:19:54AM +0100, Yuri D'Elia wrote:
>
> I've just experienced this bug. I've installed a fresh debian system on a new
> laptop (using sid) from scratch.
>
> I've configured console-setup to use TerminusBold 16x32, and while it works
> just after running dpkg-reconfigure
Package: console-setup
Version: 1.137
Followup-For: Bug #759657
I've just experienced this bug. I've installed a fresh debian system on a new
laptop (using sid) from scratch.
I've configured console-setup to use TerminusBold 16x32, and while it works
just after running dpkg-reconfigure, the set
On Sun, 17 Jan 2016 13:19:16 +0300 Anton Zinoviev wrote:
> On Sat, Jan 16, 2016 at 06:37:18PM +0100, Francesco Poli wrote:
> > On Mon, 11 Jan 2016 22:22:46 +0100 Francesco Poli wrote:
> >
> > Dear console-setup package maintainers,
> > is there anything blocking the adoption of the suggested solu
On Sat, Jan 16, 2016 at 06:37:18PM +0100, Francesco Poli wrote:
> On Mon, 11 Jan 2016 22:22:46 +0100 Francesco Poli wrote:
>
> Dear console-setup package maintainers,
> is there anything blocking the adoption of the suggested solution for
> this bug?
I am sorry if I have created the impression th
On Mon, 11 Jan 2016 22:22:46 +0100 Francesco Poli wrote:
[...]
> In conclusion, it really appears to be the solution to be adopted in
> order to fix this issue: once again, please consider adding such file
> as /lib/udev/rules.d/90-setupcon.rules to package console-setup.
[...]
Dear console-set
On Tue, 5 Jan 2016 19:19:41 +0100 Samuel Thibault wrote:
> Just my +1
>
> Francesco Poli, on Tue 05 Jan 2016 19:00:30 +0100, wrote:
> > [...]
> > > Anyway, the things will work even without such checks, so maybe your
> > > proposed solution can be used unchanged after all...
> >
> > Hello again
Just my +1
Francesco Poli, on Tue 05 Jan 2016 19:00:30 +0100, wrote:
> [...]
> > Anyway, the things will work even without such checks, so maybe your
> > proposed solution can be used unchanged after all...
>
> Hello again,
> I also tried the solution proposed [1] by Michael Biebl:
>
> $ cat
On Wed, 16 Dec 2015 16:28:34 +0200 Anton Zinoviev wrote:
[...]
> Anyway, the things will work even without such checks, so maybe your
> proposed solution can be used unchanged after all...
Hello again,
I also tried the solution proposed [1] by Michael Biebl:
$ cat /etc/udev/rules.d/90-setupco
Am 16.12.2015 um 15:28 schrieb Anton Zinoviev:
> On Wed, Dec 16, 2015 at 03:21:22PM +0100, Michael Biebl wrote:
>> I don't see why this check would make it init system dependend or
>> dependend on Debian specifics.
>
> I was talking about the following check: whether initrd has configured
> the
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.
> >
> > Setupcon is a portable script that can be used
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.
>
> Setupcon is a portable script that can be used on any distribution ---
> Debian or not, on Linux or FreeBSD, with system
On Wed, Dec 16, 2015 at 02:22:49PM +0100, Michael Biebl wrote:
>
> Wouldn't be hard to add this check to setupcon itself.
Setupcon is a portable script that can be used on any distribution ---
Debian or not, on Linux or FreeBSD, with systemd or without systemd.
Although currently console-setup
Am 16.12.2015 um 12:16 schrieb Anton Zinoviev:
> On Thu, Dec 10, 2015 at 03:47:24AM +0100, Michael Biebl wrote:
>>
>> $ cat /etc/udev/rules.d/90-setupcon.rules
>> ACTION=="add", SUBSYSTEM=="vtconsole", KERNEL=="vtcon*",
>> RUN+="/bin/setupcon"
>
> What does this do?
It runs setupcon when the bac
On Thu, Dec 10, 2015 at 03:47:24AM +0100, Michael Biebl wrote:
>
> $ cat /etc/udev/rules.d/90-setupcon.rules
> ACTION=="add", SUBSYSTEM=="vtconsole", KERNEL=="vtcon*",
> RUN+="/bin/setupcon"
What does this do? I mean when does the action "add" of "vtconsole"
occur? During the boot or when the
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*",
>>>
On Sat, Dec 12, 2015 at 01:52:29PM +, Brian Potkin wrote:
> On Thu 10 Dec 2015 at 03:47:24 +0100, Michael Biebl wrote:
>
> > Am 10.12.2015 um 00:55 schrieb Samuel Thibault:
> > > Eric Cooper, on Thu 19 Nov 2015 13:31:57 -0500, wrote:
> > >> While booting, it looks like the font switches from VG
On Thu 10 Dec 2015 at 03:47:24 +0100, Michael Biebl wrote:
> Am 10.12.2015 um 00:55 schrieb Samuel Thibault:
> > Eric Cooper, on Thu 19 Nov 2015 13:31:57 -0500, wrote:
> >> While booting, it looks like the font switches from VGA to Terminus
> >> during the boot messages. But then the screen is cl
Am 10.12.2015 um 03:47 schrieb Michael Biebl:
> ACTION=="add", SUBSYSTEM=="vtconsole", KERNEL=="vtcon*",
> RUN+="/bin/setupcon"
Unfortunate wrapping by the MUA.
This should be in one line, no line break:
ACTION=="add", SUBSYSTEM=="vtconsole", KERNEL=="vtcon*", RUN+="/bin/setupcon"
--
Why is it
Am 10.12.2015 um 00:55 schrieb Samuel Thibault:
> Eric Cooper, on Thu 19 Nov 2015 13:31:57 -0500, wrote:
>> While booting, it looks like the font switches from VGA to Terminus
>> during the boot messages. But then the screen is cleared and the
>> getty login prompts are back in VGA. If I run "set
Am 10.12.2015 um 00:55 schrieb Samuel Thibault:
> Eric Cooper, on Thu 19 Nov 2015 13:31:57 -0500, wrote:
>> While booting, it looks like the font switches from VGA to Terminus
>> during the boot messages. But then the screen is cleared and the
>> getty login prompts are back in VGA. If I run "set
Eric Cooper, on Thu 19 Nov 2015 13:31:57 -0500, wrote:
> While booting, it looks like the font switches from VGA to Terminus
> during the boot messages. But then the screen is cleared and the
> getty login prompts are back in VGA. If I run "setupcon" manually, it
> changes to Terminus.
So it see
On Wed, 9 Dec 2015 16:42:34 +0200 Anton Zinoviev wrote:
> On Tue, Dec 08, 2015 at 03:54:01PM +0100, Francesco Poli wrote:
> >
> > Dear console-setup maintainers, this bug has been reported quite some
> > time ago: is there any progress on this?
>
> In order to be honest, I must admit that I don'
On Tue, Dec 08, 2015 at 03:54:01PM +0100, Francesco Poli wrote:
>
> Dear console-setup maintainers, this bug has been reported quite some
> time ago: is there any progress on this?
In order to be honest, I must admit that I don't use systemd in my
systems. I find the behaviour of systemd too co
Control: severity -1 important
On Thu, 19 Nov 2015 13:31:57 -0500 Eric Cooper wrote:
[...]
> I see the same problem on every reboot.
>
> While booting, it looks like the font switches from VGA to Terminus
> during the boot messages. But then the screen is cleared and the
> getty login prompts
Package: console-setup
Version: 1.134
Followup-For: Bug #759657
I see the same problem on every reboot.
While booting, it looks like the font switches from VGA to Terminus
during the boot messages. But then the screen is cleared and the
getty login prompts are back in VGA. If I run "setupcon" m
On Fri, Aug 29, 2014 at 09:53:20AM +0200, Karsten Hilbert wrote:
>
> When systemd was introduced console-setup started to "forget" setting the
I don't known how exactly systemd works but it seems Bug#783976 may be
related to this:
> Package: console-cyrillic
> Severity: normal
>
> Dear Maintain
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 hamper
27 matches
Mail list logo
