KDM in Dual screen configuration - Need to move the mouse to type into the graphical login dialog

[Joe Merten]

Binary package hint: kdebase-workspace

Using Kubuntu 10.10

My primary display is the build-in display of the notebook.
The secondary display is an external display, plugged by a displayport cable.
The primary display is on right hand side, the secondary display on the left hand side.
-> See also the attached screenshot to understand my screen layout.

After poweron, the position of the mousepointer stays initially on the left display, which is the secondary one.
To type in my name and password, I have to move the mouse to the primary display, what is a littles uncomfortable (as far as a pointing device is available).

My video card is NVidia and I have configured dual head as Twin-View (to have composing).

In Kubuntu 9.04, 9.10 and 10.04 there was no need to move the mouse.
But I cannot remember the initially position of the mousepointer after poweron.

I'll also attach my xorg.conf

Joe.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: kdm 4:4.5.1-0ubuntu8
ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Thu Dec 9 21:59:15 2010
ExecutablePath: /usr/bin/kdm
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
SourcePackage: kdebase-workspace
XsessionErrors: (process:2297): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Joe Merten (kubuntu-jme)]

The previous posted screenshot contains wrong coordinate values in its textual comments.

[Harald Sitter (apachelogger)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!

[Joe Merten (kubuntu-jme)]

Manually forwarded to https://bugs.kde.org/show_bug.cgi?id=283280