Bug#406912: tasksel-data: Should add numlockx to desktop
Package: tasksel-data Version: 2.63 Severity: minor Hi, After installing Debian for a desktop use, numlock is not set by default, this is a pain for people who have to remember to set it each time they log in, and they will eventually say "GNU/Linux sucks" just because of this irritating behavior :) (real story). For enabling numlock by default, the apparently currently preferred way is to just install the numlockx package, which properly hooks into the X session scripts. I'd hence suggest to add the numlockx package to the desktop task. Samuel -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- Samuel Thibault <[EMAIL PROTECTED]> M. MIMRAM Samuel Antonin en voila un qui etait predestiné -+- #ens-mim - Quelles gueules qu'ils ont les ptits nouveaux ? -+-
Bug#406912: tasksel-data: Should add numlockx to desktop
Miroslav Kure, le Mon 15 Jan 2007 17:38:22 +0100, a écrit : > On Mon, Jan 15, 2007 at 12:56:14AM +0100, Samuel Thibault wrote: > > > > I'd hence suggest to add the numlockx package to the desktop task. > > Think about the poor laptop users who will have to turn it off each > time they login, because half of the keyboard would be unusable for > them. > > ...and they will eventually say "GNU/Linux sucks" just because of this > irritating behavior :) (real story). Gaah :) But there's a laptop task, isn't there a way to have it somehow "conflict" with numlockx? Samuel
Bug#406912: tasksel-data: Should add numlockx to desktop
On Mon, Jan 15, 2007 at 12:56:14AM +0100, Samuel Thibault wrote: > > I'd hence suggest to add the numlockx package to the desktop task. Think about the poor laptop users who will have to turn it off each time they login, because half of the keyboard would be unusable for them. ...and they will eventually say "GNU/Linux sucks" just because of this irritating behavior :) (real story). -- Miroslav Kure -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#406912: tasksel-data: Should add numlockx to desktop
Samuel Thibault wrote: > After installing Debian for a desktop use, numlock is not set by > default, this is a pain for people who have to remember to set it each > time they log in, and they will eventually say "GNU/Linux sucks" just > because of this irritating behavior :) (real story). > > For enabling numlock by default, the apparently currently preferred way > is to just install the numlockx package, which properly hooks into the X > session scripts. I suspect that if I do this, I will get plenty of complaints from everyone who has turned numlock off in their bios, and don't want it on, about it being forced on. Iff you can prove otherwise, I'll consider it. -- see shy jo signature.asc Description: Digital signature
Bug#406912: tasksel-data: Should add numlockx to desktop
Joey Hess, le Mon 15 Jan 2007 23:19:03 -0500, a écrit : > Samuel Thibault wrote: > > But there's a laptop task, isn't there a way to have it somehow > > "conflict" with numlockx? > > You think the laptop task is installed on all laptops? I'm sure this is > not the case, for various reasons. > > This point about laptops is enough for me to give up on the idea. numlockx should then be properly advertised another way: in the X section of debian manual, FAQ, or any other official place where people would find it. My point is that very _few_ people know that installing numlockx is just sufficient for having numlock set at bootup, while I guess (maybe that's only a guess, but neither of us can answer, only polling can) that most people would prefer numlock set. Or rather: it's quite difficult for those people that want it do discover that they should just install numlockx, hence documentation. Samuel
Bug#406912: tasksel-data: Should add numlockx to desktop
Samuel Thibault wrote: > My point is that very _few_ people know that installing numlockx is just > sufficient for having numlock set at bootup, while I guess (maybe that's > only a guess, but neither of us can answer, only polling can) that most > people would prefer numlock set. Or rather: it's quite difficult for > those people that want it do discover that they should just install > numlockx, hence documentation. I still don't understand why most people will want to configure their computer to use something different from the bios default. If I want numlock on, I set it in the bios, then it's always on, even during early bootup. A program that turns it on when X starts feels strongly of hack to me. -- see shy jo signature.asc Description: Digital signature
Bug#406912: tasksel-data: Should add numlockx to desktop
Joey Hess, le Tue 16 Jan 2007 10:18:59 -0500, a écrit : > I still don't understand why most people will want to configure their > computer to use something different from the bios default. If I want > numlock on, I set it in the bios, then it's always on, even during early > bootup. A program that turns it on when X starts feels strongly of hack > to me. The problem is that both Linux and the X server _clear_ numlock, whatever the BIOS configuration. I actually asked Xorg about the issue and never got any answer, so I took it as "bah we don't care, people just use kde stuff or numlockx". Samuel
Bug#406912: tasksel-data: Should add numlockx to desktop
Joey Hess, le Tue 16 Jan 2007 11:26:01 -0500, a écrit : > Samuel Thibault wrote: > > The problem is that both Linux and the X server _clear_ numlock, > > whatever the BIOS configuration. > > Eh, that certianly didn't used to be true on x86 hardware. I've been noticing this behavior on x86 hardware at least since 1998. Samuel
Bug#406912: tasksel-data: Should add numlockx to desktop
On Tuesday 16 January 2007 16:18, Joey Hess wrote: > I still don't understand why most people will want to configure their > computer to use something different from the bios default. If I want > numlock on, I set it in the bios, then it's always on, even during > early bootup. A program that turns it on when X starts feels strongly > of hack to me. That's not true unfortunately (at least in my experience). Linux seems to set its own initial state of numlock. What I have done in the past, is uncomment '#LEDS=+num' in /etc/concole-tools/config. Maybe it could be considered a kernel bug that Linux does not respect the BIOS setting... pgpX0f9Zk1vT5.pgp Description: PGP signature
Bug#406912: tasksel-data: Should add numlockx to desktop
Samuel Thibault wrote: > The problem is that both Linux and the X server _clear_ numlock, > whatever the BIOS configuration. Eh, that certianly didn't used to be true on x86 hardware. I don't have any to check right now.. -- see shy jo signature.asc Description: Digital signature
