Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
xorg-server 1.13.0, two screens, mouse stuck on first screen
View unanswered posts
View posts from last 24 hours
View posts from last 7 days

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
headrift
n00b
n00b


Joined: 07 Jan 2008
Posts: 4

PostPosted: Thu Sep 06, 2012 5:11 pm    Post subject: xorg-server 1.13.0, two screens, mouse stuck on first screen Reply with quote

I emerged xorg-server 1.13.0 this morning, used emerge @x11-module-rebuild, rebooted, and now my mouse is stuck on the first screen. I use a two screen setup, and the cursor in prior versions would move freely between screens. Since the update, if I move the cursor to the side where the second screen should start (right side of left screen) it wraps around to the other side of the first screen (left side of left screen). Both screens display properly, and the cursor behaved properly before the update. I haven't changed any use flags.

The only error in Xorg.0.log is one about evdev not being able to open /dev/input/mouse0 -- I changed the mouse input device section to the "mouse" driver from evdev, same problem, but without the error. I also tried changing the device from mouse0 to /dev/input/mice with both drivers, same problem.

The only file in /etc/xorg.conf.d/ is 50-vboxmouse.conf -- I've tried removing this directory elsewhere to get it out of the way, but it hasn't helped. The man page for xorg.conf seems to indicate that xorg.conf should still be in /etc/X11/ so I've left it there. I haven't tried symlinking it into /etc/X11/xorg.conf.d/ yet, might do that next, but I'm not sure it will help as this seems to be a change in the way the mouse is used, and the screens still display correctly. The keyboard, if started in the second screen, works in the second screen until I move it to the first screen, where it then stays.

I haven't been able to find mention of this problem elsewhere, but I might be searching the wrong places or with the wrong words. I might have to revert back to an earlier xorg-server version, but I don't like doing that.

In xorg.conf, my input device section for the mouse currently looks like this:

Code:

Section "InputDevice"
  Identifier "Mouse"
  Driver "evdev"
  Option "Device" "/dev/input/mouse0"
  Option "ZAxisMapping" "4 5"
EndSection


...and my server layout like this:

Code:

Section "ServerLayout"
  Identifier "Dual Monitors"
  Screen 0 "Left" 0 0
  Screen 1 "Right" RightOf "Left"
  InputDevice "Keyboard" "CoreKeyboard"
  InputDevice "Mouse" "CorePointer"
  Option "Xinerama" "0"
EndSection


I think those are set up right, but 1.13.0 must be handling them differently than 1.12.99.905 was... I'm not sure, and haven't been able to find anything about configuration changes. If there's a link I missed, which is entirely possible, please let me know. If there are other files I need to post, I'd be happy to post them.
Back to top
View user's profile Send private message
gorkypl
Guru
Guru


Joined: 04 Oct 2010
Posts: 444
Location: Kraków, PL

PostPosted: Thu Sep 06, 2012 8:04 pm    Post subject: Reply with quote

First thing:
xorg.conf.d is a directory that replaces xorg.conf file. You should use one or another. Every file that is inside xorg.conf.d is read, and it contents is treated as it was the part of xorg.conf

So start by removing (or moving to another place) every file that is inside xorg.conf.d and the xorg.conf file.
If you are using evdev, there is no need to use Mouse section that you have pasted.

Next steps depend on the graphics driver that you are using, so please write what is it.
_________________
BTW, TWM FTW!
Back to top
View user's profile Send private message
Gusar
Advocate
Advocate


Joined: 09 Apr 2005
Posts: 2665
Location: Slovenia

PostPosted: Thu Sep 06, 2012 9:11 pm    Post subject: Reply with quote

gorkypl wrote:
xorg.conf.d is a directory that replaces xorg.conf file.

The directory doesn't replace the file, it's an addition to it. All files in the directory are read, then xorg.conf is read. It's easiest to think of xorg.conf as being equivalent to xorg.conf.d/99-something.conf
Back to top
View user's profile Send private message
gorkypl
Guru
Guru


Joined: 04 Oct 2010
Posts: 444
Location: Kraków, PL

PostPosted: Thu Sep 06, 2012 9:25 pm    Post subject: Reply with quote

Obviously you are right :)
Still presence of configuration in two places may lead to a mess when searching problems in other users' configs, that's why I usually suggest to use one or another.
_________________
BTW, TWM FTW!
Back to top
View user's profile Send private message
chithanh
Developer
Developer


Joined: 05 Aug 2006
Posts: 2158
Location: Berlin, Germany

PostPosted: Thu Sep 06, 2012 9:54 pm    Post subject: Reply with quote

Cursor stuck on one screen is a recurring issue with Xinerama. Sometimes it helps swapping the two monitors (exchanging the connectors and position in xorg.conf).

Unfortunately there is almost no interest in the Xinerama code upstream, so it is unlikely that the problem itself will be fixed.
Back to top
View user's profile Send private message
headrift
n00b
n00b


Joined: 07 Jan 2008
Posts: 4

PostPosted: Sat Sep 08, 2012 12:22 am    Post subject: Reply with quote

Played around with screen positions in xorg.conf briefly. When I arranged them above and below, the cursor would loop from bottom edge of the one screen back to the top instead of the side to the far side of the same screen, so I reverted back to 1.12.4 -- I might try to get it working again later on. I am mostly convinced that it's not a configuration issue after turning Xinerama on and off and TwinView on and off to no avail and playing with mouse drivers and paths.
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 7470

PostPosted: Sat Sep 08, 2012 12:55 am    Post subject: Reply with quote

I think it comes from nvidia proprietary drivers, something you don't explicitly tell us you have update (even your twinview reference tell us you are using them).

Since the last nvidia update, my xorg refuse to handle properly metamodes : and 1680x1050, null always disable left screen instead of the right one, no wonder how i swap my screen.
I'm still using xorg-1.12-0-r1 ebuild i have just update nvidia drivers to 302.17
Back to top
View user's profile Send private message
tacvbo
n00b
n00b


Joined: 28 May 2003
Posts: 39
Location: México City

PostPosted: Fri Sep 14, 2012 6:11 pm    Post subject: Re: xorg-server 1.13.0, two screens, mouse stuck on first sc Reply with quote

Same issue here using x11-base/xorg-server-1.13.0 & x11-drivers/nvidia-drivers-304.48. My configuration was working before upgrading. Mouse works (it can move from screen-to-screen) when Xinerama is on or Nvidia's Twinview is activated. There is no relevant evidence of any error on Xorg.0.log

Code:

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    Screen      1  "Screen1" RightOf "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from data in "/etc/conf.d/gpm"
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol"
    Option         "Device" "/dev/input/mice"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "LGD"
    HorizSync       41.3 - 54.8
    VertRefresh     40.3 - 60.1
    Option         "DPMS"
EndSection

Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "BenQ BL2400"
    HorizSync       30.0 - 83.0
    VertRefresh     50.0 - 76.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "NVS 4200M"
    BusID          "PCI:1:0:0"
    Screen          0
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "NVS 4200M"
    BusID          "PCI:1:0:0"
    Screen          1
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "TwinViewXineramaInfoOrder" "DFP-0"
    Option         "metamodes" "DFP: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "metamodes" "CRT: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection
Back to top
View user's profile Send private message
manwe_
l33t
l33t


Joined: 01 Feb 2006
Posts: 632
Location: Kraków/Cracow, Poland

PostPosted: Fri Sep 21, 2012 5:37 pm    Post subject: Reply with quote

Same problem for me :? I've updated xorg-server from 1.12.3 to 1.13.0 and nvidia-drivers from 304.37-r1 to 304.48. Never had such problem.

Using Layout1 and two outputs HDMI and VGA on my laptop:
Code:

$ cat /etc/X11/xorg.conf
Section "ServerLayout"
    Identifier        "Layout0"
    Screen            0  "Screen0" 0 0
    InputDevice       "Mouse0"      "CorePointer"
    InputDevice       "Keyboard0"   "CoreKeyboard"
    Option            "Xinerama"    "0"
EndSection

Section "ServerLayout"
    Identifier        "Layout1"
    Screen            0  "Screen1" 0 0
    Screen            1  "Screen2" RightOf "Screen1"
    InputDevice       "Mouse0"      "CorePointer"
    InputDevice       "Keyboard0"   "CoreKeyboard"
    Option            "Xinerama"    "0"
EndSection

Section "Files"
    ModulePath              "/usr/lib64/xorg/modules"
    FontPath                "built-ins"
    FontPath                "/home/manwe/.fonts"
    FontPath                "/usr/share/fonts/100dpi"
    FontPath                "/usr/share/fonts/75dpi"
    FontPath                "/usr/share/fonts/corefonts"
    FontPath                "/usr/share/fonts/cyrillic"
    FontPath                "/usr/share/fonts/default"
    FontPath                "/usr/share/fonts/dejavu"
    FontPath                "/usr/share/fonts/encodings"
    FontPath                "/usr/share/fonts/freefonts"
    FontPath                "/usr/share/fonts/liberation-fonts"
    FontPath                "/usr/share/fonts/misc"
    FontPath                "/usr/share/fonts/Speedo"
    FontPath                "/usr/share/fonts/terminus"
    FontPath                "/usr/share/fonts/ttf-bitstream-vera"
EndSection

Section "Module"
    Load  "extmod"
    Load  "record"
    Load  "dbe"
    Load  "glx"
    Load  "wfb"
EndSection

Section "InputDevice"
    Identifier  "Keyboard0"
    Driver      "kbd"
    Option      "AutoRepeat" "500 30"
    Option      "XkbRules" "xorg"
    Option      "XkbModel" "pc105"
    Option      "XkbLayout" "pl"
    Option      "XkbOptions" "eurosign:5,altwin:meta_super"
EndSection

Section "InputDevice"
    Identifier  "Mouse0"
    Driver      "mouse"
    Option      "Protocol" "auto"
    Option      "Device" "/dev/input/mice"
    Option      "Protocol" "ExplorerPS/2"
    Option      "ZAxisMapping" "4 5 6 7"
    Option      "Buttons" "10"
EndSection


Section "Monitor"
    Identifier    "Monitor0"
    Option        "DPMS"
    ModelName     "AUO"
EndSection

Section "Monitor"
    Identifier    "Monitor1"
    Option        "DPMS"
    ModelName     "HDMI"
EndSection

Section "Monitor"
    Identifier    "Monitor2"
    Option        "DPMS"
    ModelName     "VGA"
EndSection

Section "Device"
    Identifier    "Card0"
    Driver        "nvidia"
    VendorName    "nVidia Corporation"
    BoardName     "GeForce 9800GT"
    BusID         "PCI:1:0:0"
    VideoRam      1048576
    Option        "NoLogo" "1"
    Option        "RenderAccel" "true"
    Option        "CursorShadow" "1"
    Option        "Coolbits" "1"
    Option        "RandRRotation" "on"
EndSection

Section "Device"
    Identifier    "Card1"
    Driver        "nvidia"
    VendorName    "nVidia Corporation"
    BoardName     "GeForce 9800GT"
    BusID         "PCI:1:0:0"
    VideoRam      1048576
    Option        "NoLogo" "1"
    Option        "RenderAccel" "true"
    Option        "CursorShadow" "1"
    Option        "Coolbits" "1"
    Option        "RandRRotation" "on"
    Screen        0
    Option    "UseDisplayDevice" "DFP-1"
EndSection

Section "Device"
    Identifier    "Card2"
    Driver        "nvidia"
    VendorName    "nVidia Corporation"
    BoardName     "GeForce 9800GT"
    BusID         "PCI:1:0:0"
    VideoRam      1048576
    Option        "NoLogo" "1"
    Option        "RenderAccel" "true"
    Option        "CursorShadow" "1"
    Option        "Coolbits" "1"
    Option        "RandRRotation" "on"
    Screen        1
    Option    "UseDisplayDevice" "CRT-0"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Card0"
    Monitor        "Monitor0"
    DefaultDepth   24
    Option         "UseEvents" "False"
    Option         "TripleBuffer" "True"
    Option         "BackingStore" "True"
    Option         "AddARGBGLXVisuals" "True"
    Option         "TwinView" "0"
    SubSection     "Display"
        Depth      24
    EndSubSection
EndSection


Section "Screen"
    Identifier     "Screen1"
    Device         "Card1"
    Monitor        "Monitor1"
    DefaultDepth   24
    Option         "UseEvents" "False"
    Option         "TripleBuffer" "True"
    Option         "BackingStore" "True"
    Option         "AddARGBGLXVisuals" "True"
    Option         "TwinView" "0"
    SubSection     "Display"
        Depth      24
    EndSubSection
    Option         "UseEdidDpi" "false"
    Option         "DPI" "93 x 92"
EndSection


Section "Screen"
    Identifier     "Screen2"
    Device         "Card2"
    Monitor        "Monitor2"
    DefaultDepth   24
    Option         "UseEvents" "False"
    Option         "TripleBuffer" "True"
    Option         "BackingStore" "True"
    Option         "AddARGBGLXVisuals" "True"
    Option         "TwinView" "0"
    SubSection     "Display"
        Depth      24
    EndSubSection
    Option         "UseEdidDpi" "false"
    Option         "DPI" "93 x 92"
EndSection
Back to top
View user's profile Send private message
gimpel
Advocate
Advocate


Joined: 15 Oct 2004
Posts: 2720
Location: Munich, Bavaria

PostPosted: Sun Oct 14, 2012 9:11 pm    Post subject: Reply with quote

Same here - mouse jumps to the left of the left screen after upgrading to xorg-server 1.13. I do use nvidia-drivers, same version as before the update, but I do not use twinview or xinerama - just plain xorg separate screens with XBMC on the right one. This is incredibly annoying, as it causes me to search my mouspointer even more often than having it "hidden" somehwere on the TV screen.
_________________
http://proaudio.tuxfamily.org/wiki - pro-audio software overlay
Back to top
View user's profile Send private message
sjesman
n00b
n00b


Joined: 19 Oct 2012
Posts: 2

PostPosted: Fri Oct 19, 2012 10:44 am    Post subject: Reply with quote

Guys from https://bugs.archlinux.org/task/31959 fixed that:
From 29d84d5a7ca4cc12cce47de9313adeb8554fb894 Mon Sep 17 00:00:00 2001
From: Peter Hutterer <peter.hutterer@who-t.net>
Date: Thu, 18 Oct 2012 15:11:31 +1000
Subject: [PATCH] dix: fix zaphod screen scrossing (#54654)

POINTER_SCREEN coordinates are screen-relative. For a Zaphod setup, the
coordinates after a screen crossing are already relative to the new screen's
origin. Add that offset to the coordinates before re-setting.

regression introduced by
commit bafbd99080be49a17be97d2cc758fbe623369945
Author: Peter Hutterer <peter.hutterer@who-t.net>
Date: Wed Aug 8 11:34:32 2012 +1000

dix: work around scaling issues during WarpPointer (#53037)

X.Org Bug 54654 <http://bugs.freedesktop.org/show_bug.cgi?id=54654>

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
---
dix/getevents.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/dix/getevents.c b/dix/getevents.c
index 71d83c4..8b4379d 100644
--- a/dix/getevents.c
+++ b/dix/getevents.c
@@ -1400,8 +1400,9 @@ fill_pointer_events(InternalEvent *events, DeviceIntPtr pDev, int type,
coordinates were.
*/
if (flags & POINTER_SCREEN) {
- screenx = sx;
- screeny = sy;
+ scr = miPointerGetScreen(pDev);
+ screenx = sx + scr->x;
+ screeny = sy + scr->y;
}

scr = positionSprite(pDev, (flags & POINTER_ABSOLUTE) ? Absolute : Relative,
--
1.7.11.7

something that gentoo xorg-server guys could corret ? hithanh@gentoo.org
Back to top
View user's profile Send private message
sjesman
n00b
n00b


Joined: 19 Oct 2012
Posts: 2

PostPosted: Fri Oct 19, 2012 10:46 am    Post subject: gentoo xorg-server-1.13.0 multihead mouse bug Reply with quote

Guys from https://bugs.archlinux.org/task/31959 fixed that:
From 29d84d5a7ca4cc12cce47de9313adeb8554fb894 Mon Sep 17 00:00:00 2001
From: Peter Hutterer <peter.hutterer@who-t.net>
Date: Thu, 18 Oct 2012 15:11:31 +1000
Subject: [PATCH] dix: fix zaphod screen scrossing (#54654)

POINTER_SCREEN coordinates are screen-relative. For a Zaphod setup, the
coordinates after a screen crossing are already relative to the new screen's
origin. Add that offset to the coordinates before re-setting.

regression introduced by
commit bafbd99080be49a17be97d2cc758fbe623369945
Author: Peter Hutterer <peter.hutterer@who-t.net>
Date: Wed Aug 8 11:34:32 2012 +1000

dix: work around scaling issues during WarpPointer (#53037)

X.Org Bug 54654 <http://bugs.freedesktop.org/show_bug.cgi?id=54654>

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
---
dix/getevents.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/dix/getevents.c b/dix/getevents.c
index 71d83c4..8b4379d 100644
--- a/dix/getevents.c
+++ b/dix/getevents.c
@@ -1400,8 +1400,9 @@ fill_pointer_events(InternalEvent *events, DeviceIntPtr pDev, int type,
coordinates were.
*/
if (flags & POINTER_SCREEN) {
- screenx = sx;
- screeny = sy;
+ scr = miPointerGetScreen(pDev);
+ screenx = sx + scr->x;
+ screeny = sy + scr->y;
}

scr = positionSprite(pDev, (flags & POINTER_ABSOLUTE) ? Absolute : Relative,
--
1.7.11.7

something that gentoo xorg-server guys could corret ? hithanh@gentoo.org
Back to top
View user's profile Send private message
manwe_
l33t
l33t


Joined: 01 Feb 2006
Posts: 632
Location: Kraków/Cracow, Poland

PostPosted: Fri Nov 02, 2012 5:29 pm    Post subject: Reply with quote

Post it to bugs.gentoo, somebody will take care of this patch.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum