Login Text Box Doesn't Have Focus

Bug #46238 reported by MrMojoRising
10
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: gdm

When my gdm login screen loads up, the text box to input my username doesn't have focus (i.e. i can't just start typing my username) . I have to press a key first then the focus goes to the text box and i can start typing my username.

If i press a key at any time during boot up then the focus is correctly placed in the text box......no key press, no focus.

Revision history for this message
MrMojoRising (svenglar) wrote :

BTW i'm on Dapper Beta 2

Revision history for this message
MrMojoRising (svenglar) wrote :

Here's some more info on my setup:

GDM - 2.4.16
kernel - 2.6.15-21-386
ATI x700 mobile - opengl 2.0.5755 (8.24.8)

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. Do you use a xinerama setup?

Changed in gdm:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
MrMojoRising (svenglar) wrote :

No I do not use Xinerama....single screen setup here (i'm on a laptop).

Revision history for this message
Sebastien Bacher (seb128) wrote :

what gdm theme do you use? what is the focus when gdm starts on the boot?

Revision history for this message
MrMojoRising (svenglar) wrote :

I use the Human theme......But i've experiemented with others and the same problem persists.
I have a custom startup sounds play when login screen is ready...I tried disabling that but the problem still persists.

As for where the focus is.....I've no idea. When the login screen is ready the cursor is flashing in the text box. But not untill the second key that i press does anything get inputed to the text box.

If i press a key at any time during the boot up process then the focus is correclty in the login box....which makes me think it isn't just a GDM bug.

Revision history for this message
MrMojoRising (svenglar) wrote :

Any updates?

I'm using Dapper Drake now and i still have been having this problem up til now.....very annoying.

Revision history for this message
Sebastien Bacher (seb128) wrote :

no update or we would have commented on that page, maybe upstream would have better idea on what could cause that if somebody wants to forward it to bugzilla.gnome

Changed in gdm:
importance: Medium → Low
status: Needs Info → Unconfirmed
Revision history for this message
glinsvad (glinsvad) wrote :

I've noticed the same behaviour.

Setup is:
Acer TravelMate 2201LC
Intel Celeron processor 2.6GHz
ATI MOBILITY RADEON 9000 IGP
Linux 2.6.15-26-686

Does not depend on gdm theme nor keyboard issues. The first keypress is simply not registered. If I click the face browser, so I don't have to type in the username, the first keypress of the password is not registered in stead.

Revision history for this message
MrMojoRising (svenglar) wrote :

When i update to the latest kernel from kernel.org this problem goes away.....
However some other things brake so i went back to the stock Dapper kernel......and still have this problem.

The first key press simply isn't registered, and if it is registered it's not displayed in the text box.

Revision history for this message
Daniel Holbach (dholbach) wrote :

This is rather a kernel issue then.

Changed in gdm:
assignee: desktop-bugs → nobody
Revision history for this message
Ben Collins (ben-collins) wrote :

I'd be interested in knowing if this problem also occurs when booting in rescue mode to the console.

If this doesn't happen on console, then I believe it is not a kernel issue.

Revision history for this message
MrMojoRising (svenglar) wrote :

WHen i booted into Rescue Mode through GRUB and waited for everything to finish loading....at the first prompt i pressed a key and this message appeared followed by a new line and a flashing cursor waiting for a prompt...

[17179618.364000] input: AT Translated Set 2 keyboard as /class/input2

Then everything i pressed after that showed up on the screen.

Revision history for this message
Ben Collins (ben-collins) wrote :

Excellent information. From what I can tell, this is basically a hardware issue. Your keyboard just isn't communicating properly with the driver.

Rejecting on that basis.

Changed in linux-source-2.6.15:
status: Unconfirmed → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.