[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#348437: marked as done (kdm auto-login causes keyboard failure)

Your message dated Mon, 15 Jan 2007 11:49:22 +0100
with message-id <20070115104922.GA7367@pryan.sytes.net>
and subject line Bug#348437: About your bug: "kdm auto-login causes keyboard failure" on the Debian BTS
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: kdm
Version: 3.4.3-3

This is already reported by a few hundred people on google.
Problem: Box is set to autologin with KDM, after I am logged in, the keyboard either does not work or does weird things like auto-repeats etc. 

Using GDM fixes the problem as GDM does not appear to have the same bug.
This occurs on two separate machines & reported by users on google/mailing lists/etc-- many people have the issue, it appears it has not been fixed in Debian Etch yet :( 

Using: Debian Etch
I am using Linux box 2.6.15.1 #2 SMP PREEMPT Mon Jan 16 17:43:05 EST 2006 i686 GNU/Linux and libc-2.3.5 

Thanks!

Justin.

--- End Message ---
--- Begin Message --- 
On Sun, Jan 14, 2007 at 04:42:48AM -0500, Justin Piszcz wrote:
> 
> 
> On Sun, 14 Jan 2007, Ana Guerrero wrote:
> 
> > Hi,
> > 
> > We (the Debian Qt/KDE team) are trying to update the bug status of some
> > old bugs in the BTS.
> > 
> > You filed the bug
> >  #348437 "kdm auto-login causes keyboard failure"
> > some time ago, you can read the bug report at:
> > http://bugs.debian.org/348437
> > 
> 
> Hmm I no longer remember, I switched to GDM and have not had a problem 
> since and also migrated to a different machine since then, if you google 
> the error/problem, you will find that other people also have the same 
> problem, perhaps one of them is still experiencing it or has the same 
> hardware to reproduce it.

Yes, but every problem could be a different bug, not exaclty the same.
We need a way to reproduce the problem in order to search for a
solution, since this is not longer possible and we do not know if the
bug is still there  i'll close the bug.

Thanks for your response!

Ana

--- End Message ---
Reply to: