Hi Brice,
On Mon, 07 May 2007 22:33:11 +0200,
Brice Goglin <[EMAIL PROTECTED]> wrote:
[...]
> Ok, thank you for all the testing. I am reassigning this bug to the
> kernel since: * downgrading evdev did not fix the problem * not starting
> X does not prevent the problem from occuring * the kerne
reassign 422273 linux-2.6
thank you
Sebastian P. Luque wrote:
>> Anyway, to eliminate all possible problems related to X, the best would
>> be to disable gdm/kdm/xdm/... at startup (moving their /etc/init.d/foo
>> script away temporarily is an easy way to do so), reboot (you shouldn't
>> get X s
On Fri, 04 May 2007 15:53:43 -0500,
"Sebastian P. Luque" <[EMAIL PROTECTED]> wrote:
[...]
> I have a strong hunch it's the new linux kernel though, because the
> light indicator worked during boot-up with the older kernel.
I should also add that this bug affects all light indicators in this
keyb
On Fri, 04 May 2007 21:35:26 +0200,
Brice Goglin <[EMAIL PROTECTED]> wrote:
[...]
> dpkg-reconfigure gdm shoud ask you to choose between gdm/kdm/xdm/...
> Anyway, to eliminate all possible problems related to X, the best would
> be to disable gdm/kdm/xdm/... at startup (moving their /etc/init.d/
Sebastian P. Luque wrote:
> On Fri, 04 May 2007 20:25:43 +0200,
> Brice Goglin <[EMAIL PROTECTED]> wrote:
>
> [...]
>
>
>> Did you upgrade some kde packages recently? (/var/log/dpkg.log might be
>> helpful) Does the problem happens if you don't use KDM at all? either
>> use startx directly to lo
On Fri, 04 May 2007 20:25:43 +0200,
Brice Goglin <[EMAIL PROTECTED]> wrote:
[...]
> Did you upgrade some kde packages recently? (/var/log/dpkg.log might be
> helpful) Does the problem happens if you don't use KDM at all? either
> use startx directly to login, or use xdm or gdm? The only related
Sebastian P. Luque wrote:
> On Fri, 04 May 2007 19:23:23 +0200,
> Brice Goglin <[EMAIL PROTECTED]> wrote:
>
> [...]
>
>
>> Could you downgrade xserver-xorg-input-evdev (1.1.2-6 is in Etch/stable
>> and testing) without downgrading the kernel? If the problem goes away,
>> the bug won't be related
On Fri, 04 May 2007 19:23:23 +0200,
Brice Goglin <[EMAIL PROTECTED]> wrote:
[...]
> Could you downgrade xserver-xorg-input-evdev (1.1.2-6 is in Etch/stable
> and testing) without downgrading the kernel? If the problem goes away,
> the bug won't be related to the kernel.
I tried that and the prob
Sebastian P. Luque wrote:
> I should have mentioned that I upgraded both simultaneously, and thought
> that would be relevant information. Also, I expect the issue to manifest
> itself during booting and that's not the case. Therefore, this seemed to
> be the place to report. Is my logic flawed?
On Fri, 04 May 2007 18:55:35 +0200,
Brice Goglin <[EMAIL PROTECTED]> wrote:
[...]
> It the problem appeared after an upgrade of the kernel, why did you
> assign this bug to xserver-xorg-input-evdev?
I should have mentioned that I upgraded both simultaneously, and thought
that would be relevant i
Sebastian P. Luque wrote:
> Upgrading to the kernel indicated below, the Num Lock light indicator on a
> Microsoft Natural Ergonomic keyboard stopped functioning. The indicator
> light is on during booting and initial KDM startup. It is turned off
> shortly after, and typing the Num Lock key work
Package: xserver-xorg-input-evdev
Version: 1:1.1.5-2
Severity: normal
Upgrading to the kernel indicated below, the Num Lock light indicator on a
Microsoft Natural Ergonomic keyboard stopped functioning. The indicator
light is on during booting and initial KDM startup. It is turned off
shortly af
12 matches
Mail list logo
