After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 359387 - display width with multihead-adi-card and fglrx
display width with multihead-adi-card and fglrx
Status: RESOLVED DUPLICATE of bug 327530
Product: gdm
Classification: Core
Component: general
2.14.x
Other All
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-03 20:05 UTC by Matthias Kuhn
Modified: 2006-10-17 20:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Matthias Kuhn 2006-10-03 20:05:41 UTC
Please describe the problem:
When I start gdm, the mouse is on the right side of the display and the focus is not on the text field for the username.
I have an IBM T43 Laptop with fingerprint reader. The window requesting you swiping the finger over the chip is at exactly the same place, although it ought to be in the center of the screen.
Somebody in this thread reports the bug is resolved by changing the driver http://forums.gentoo.org/viewtopic-t-503403.html . Nevertheless, I don't think it's a driver issue, as the splash screen when starting gnome is in the center of the screen again.
Nevertheless, this is quiet new. I don't know the exact version of the driver with which it started, but I remember, that not a year ago it wasn't that way.

Steps to reproduce:
1. Get a T43
2. Install ati-drivers 8.28.8
3. Get gdm 2.14.9
4. Start it


Actual results:
You have to move the mouse, before being able to type your username/password

Expected results:
You can straight away start typing your keyboard.
The Screen only expanded to two-screen-width, when there is actually a second one connected.

Does this happen every time?
yes

Other information:
Comment 1 Matthias Kuhn 2006-10-04 11:25:13 UTC
Just tried with fglrx 8.27.10-r1 and the issue doesn't exist there.
Comment 2 Brian Cameron 2006-10-17 20:16:33 UTC
I think this was fixed in 2.15.10 and 2.16, so I'd recommend upgrading.  Marking as a duplicate of bug #327530.

*** This bug has been marked as a duplicate of 327530 ***