Julien Cristau, le Sat 26 Feb 2011 01:18:27 +0100, a écrit :
> On Sat, Feb 26, 2011 at 01:15:33 +0100, Samuel Thibault wrote:
>
> > Julien Cristau, le Fri 25 Feb 2011 18:44:22 +0100, a écrit :
> > > Why "at best"? It sounds like checking whether the active VT is in
> > > KD_TEXT is exactly what's
Julien Cristau, le Fri 25 Feb 2011 18:44:22 +0100, a écrit :
> Why "at best"? It sounds like checking whether the active VT is in
> KD_TEXT is exactly what's needed here.
No, because that may just be an fbterm, still using the normal keyboard
processing, and not Xorg.
Samuel
--
To UNSUBSCRIBE
On Sat, Feb 26, 2011 at 01:15:33 +0100, Samuel Thibault wrote:
> Julien Cristau, le Fri 25 Feb 2011 18:44:22 +0100, a écrit :
> > Why "at best"? It sounds like checking whether the active VT is in
> > KD_TEXT is exactly what's needed here.
>
> No, because that may just be an fbterm, still using
On Fri, Feb 25, 2011 at 20:20:47 +0200, Anton Zinoviev wrote:
> On Fri, Feb 25, 2011 at 06:44:22PM +0100, Julien Cristau wrote:
> >
> > Why "at best"? It sounds like checking whether the active VT is in
> > KD_TEXT is exactly what's needed here.
>
> How can this be tested?
>
Something like this
On Fri, Feb 25, 2011 at 06:44:22PM +0100, Julien Cristau wrote:
>
> Why "at best"? It sounds like checking whether the active VT is in
> KD_TEXT is exactly what's needed here.
How can this be tested?
Anton Zinoviev
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
On Fri, Feb 25, 2011 at 14:05:07 +0100, Samuel Thibault wrote:
> Otavio Salvador, le Fri 25 Feb 2011 13:01:59 +, a écrit :
> > if pidof X > /dev/null; then
> > echo "X is running"
> > else
> > echo "X isn't running"
> > fi
>
> Errr, surely not :)
>
> What Anton wants is to know wheth
On Fri, Feb 25, 2011 at 07:30:53PM +0200, Anton Zinoviev wrote:
> On Fri, Feb 25, 2011 at 12:23:27PM -0500, Lennart Sorensen wrote:
> >
> > Is 'fgconsole' of any help if one could combine it with knowing which
> > vt's have X currently running?
>
> Indeed!
Probably linux only though.
--
Len So
On Fri, Feb 25, 2011 at 12:23:27PM -0500, Lennart Sorensen wrote:
>
> Is 'fgconsole' of any help if one could combine it with knowing which
> vt's have X currently running?
Indeed!
Anton Zinoviev
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubs
On Fri, Feb 25, 2011 at 06:00:43PM +0100, Cyril Brulebois wrote:
> Anton Zinoviev (25/02/2011):
> > Testing the standard output and standard input never worked because
> > they are redirected by Debconf. In particular /usr/bin/tty outputs
> > "not a tty". For a long time the following code worke
Hi,
Anton Zinoviev (25/02/2011):
> Testing the standard output and standard input never worked because
> they are redirected by Debconf. In particular /usr/bin/tty outputs
> "not a tty". For a long time the following code worked:
>
> case `readlink /proc/self/fd/2` in
> /dev/tty[0-
On Fri, Feb 25, 2011 at 02:05:07PM +0100, Samuel Thibault wrote:
>
> What Anton wants is to know whether X is currently at the front or not.
> And you can't rely on DISPLAY being set (since you could be from sudo su
> -), and you can't rely on stdin being the VT (since you could be from
> screen).
On Fri, Feb 25, 2011 at 13:05, Samuel Thibault wrote:
> Otavio Salvador, le Fri 25 Feb 2011 13:01:59 +, a écrit :
>> if pidof X > /dev/null; then
>> echo "X is running"
>> else
>> echo "X isn't running"
>> fi
>
> Errr, surely not :)
heh.
> What Anton wants is to know whether X is cur
Otavio Salvador, le Fri 25 Feb 2011 13:01:59 +, a écrit :
> if pidof X > /dev/null; then
> echo "X is running"
> else
> echo "X isn't running"
> fi
Errr, surely not :)
What Anton wants is to know whether X is currently at the front or not.
And you can't rely on DISPLAY being set (sinc
On Fri, Feb 25, 2011 at 00:20, Samuel Thibault wrote:
> Anton Zinoviev, le Thu 24 Feb 2011 07:28:18 +0200, a écrit :
>> True. Other people have complained about this too. Unfortunately I
>> don't know a reliable way to test whether we are on the console or in X
>> and it is generally dangerous t
Anton Zinoviev, le Thu 24 Feb 2011 07:28:18 +0200, a écrit :
> True. Other people have complained about this too. Unfortunately I
> don't know a reliable way to test whether we are on the console or in X
> and it is generally dangerous to reconfigure the console if X is active.
Maybe dpkg-reco
On Wed, Feb 23, 2011 at 10:57:05PM -0600, Javier Vasquez wrote:
>
> Found the issue with the failure, but I don't like the solution, :-)
> One of the things keyboard-configuration doesn't ask, is whether there
> are alternative languages to the primary ones,
I suppose this is not going to change b
On Wed, Feb 23, 2011 at 10:50 PM, Anton Zinoviev wrote:
> reassign 614127 console-setup
> severity 614127 normal
> forcemerge 614550 614127
> thanks
>
> On Wed, Feb 23, 2011 at 09:35:42PM -0600, Javier Vasquez wrote:
>>
>> Package: console-setup
>> Version: 1.69
>>
>> Package: xkb-data
>> Version:
reassign 614127 console-setup
severity 614127 normal
forcemerge 614550 614127
thanks
On Wed, Feb 23, 2011 at 09:35:42PM -0600, Javier Vasquez wrote:
>
> Package: console-setup
> Version: 1.69
>
> Package: xkb-data
> Version: 2.1-1
So, the you have version 2.1-1 of xkb-data too. I am reassignin
On Wed, Feb 23, 2011 at 1:37 PM, Javier Vasquez wrote:
> ...
>> Some additional information from the original submitter (Javier Vasquez)
>> is required before this can be done.
>>
>> Javier, do you have console-setup installed on your machine? If yes,
>> then what is the version of the package xk
...
> Some additional information from the original submitter (Javier Vasquez)
> is required before this can be done.
>
> Javier, do you have console-setup installed on your machine? If yes,
> then what is the version of the package xkb-data and what happens if you
> run "setupcon" on the console?
On Wed, Feb 23, 2011 at 07:06:24PM +0100, Eric Valette wrote:
>
> Fixed home also. Without the new version of ckbcomp:
> 1) dpkg-reconfigure console-data fixe the keyboard but effect is
> lost upon reboot
> 2) dpkg-reconfigure keyboard-configuration does nothing (qwerty
> stay even aft
On 23/02/2011 15:55, Eric Valette wrote:
On 02/23/2011 01:54 PM, Anton Zinoviev wrote:
On Wed, Feb 23, 2011 at 01:16:01PM +0100, Eric Valette wrote:
I will test at home and report anyway.
Fixed home also. Without the new version of ckbcomp:
1) dpkg-reconfigure console-data fixe the keyboar
On 02/23/2011 01:54 PM, Anton Zinoviev wrote:
On Wed, Feb 23, 2011 at 01:16:01PM +0100, Eric Valette wrote:
I did a copy of the new ckbcomp to /usr/bin/ and then dpkg-reconfigure
keyboard-configuration. Rebooted. Problem seems to be gone.
Note: all machine that have the problem are 64 bits mac
On Wed, Feb 23, 2011 at 01:16:01PM +0100, Eric Valette wrote:
>
> I did a copy of the new ckbcomp to /usr/bin/ and then dpkg-reconfigure
> keyboard-configuration. Rebooted. Problem seems to be gone.
>
> Note: all machine that have the problem are 64 bits machine.
I don't know about the problem w
On 02/23/2011 11:51 AM, Eric Valette wrote:
I'm at work right now. Will test tonight and report.
I found a machine at work that did exhibit the problem after upgrade.
I did a copy of the new ckbcomp to /usr/bin/ and then dpkg-reconfigure
keyboard-configuration. Rebooted. Problem seems to be
On 02/23/2011 11:46 AM, Anton Zinoviev wrote:
On Wed, Feb 23, 2011 at 10:49:09AM +0100, Eric Valette wrote:
Thanks for the clarification. BTW the bug I have may be linked to
bug 614550 as I have this version of xkb-data.
Attached to this message you can find a version of ckbcomp that I
believ
On Wed, Feb 23, 2011 at 10:49:09AM +0100, Eric Valette wrote:
>
> Thanks for the clarification. BTW the bug I have may be linked to
> bug 614550 as I have this version of xkb-data.
Attached to this message you can find a version of ckbcomp that I
believe fixes 614550. Does it fix the problem on
On 02/23/2011 10:32 AM, Anton Zinoviev wrote:
On Mon, Feb 21, 2011 at 08:34:43AM +0100, Eric Valette wrote:
BTW: I see /bin/setupcon still looks for things installed in
/usr/bin which is a bad things if:
Everything required (the font and the keymap) is copied in
/etc/console-setup/. In result
On Mon, Feb 21, 2011 at 08:34:43AM +0100, Eric Valette wrote:
>
> BTW: I see /bin/setupcon still looks for things installed in
> /usr/bin which is a bad things if:
Everything required (the font and the keymap) is copied in
/etc/console-setup/. In result:
1. If you don't change the configuration
On 21/02/2011 08:28, Eric Valette wrote:
BTW: I see /bin/setupcon still looks for things installed in /usr/bin
which is a bad things if:
1) You boot in single mode
2) you have a fs problem
Because, at that time, /usr may not be mounted. I already fixed this one
once. But may b
On 21/02/2011 07:26, Christian PERRIER wrote:
Quoting Eric Valette (eric.vale...@free.fr):
And when I read the comments, I'm always thinking that people are
more interested in closing bugs than fixing them. Was working
before. Broke on 4 machines.
What can I say more than "console-data has no
Quoting Eric Valette (eric.vale...@free.fr):
> And when I read the comments, I'm always thinking that people are
> more interested in closing bugs than fixing them. Was working
> before. Broke on 4 machines.
What can I say more than "console-data has no chance to see very
active maintenance for w
And when I read the comments, I'm always thinking that people are more
interested in closing bugs than fixing them. Was working before. Broke
on 4 machines.
--eric
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas.
33 matches
Mail list logo
