Results 1 to 3 of 3

Thread: separate X screens - can't return pointer/cursor to primary screen

  1. #1
    Join Date
    Sep 2007
    Location
    State College, PA
    Beans
    30
    Distro
    Ubuntu 11.04 Natty Narwhal

    separate X screens - can't return pointer/cursor to primary screen

    I use a laptop, and frequently plug in to a separate monitor or to a TV screen. I have it set up to to separate X screens. When using my laptop touchpad, I find that once I move to the other monitor or TV screen, I can't return back to my laptop monitor. My USB mouse, however, is able to transition from screen to screen with no problem. I am not sure how to go about troubleshooting, so any advice is appreciated.

    I am using ubuntu 10.04 but had the same problem with 8.04 before I upgraded. I have an NVIDIA graphics card, and use the nvidia-settings (which generates the xorg.conf file) to manage the screens.

    Here is my xorg.conf:
    Code:
    # nvidia-settings: X configuration file generated by nvidia-settings
    # nvidia-settings:  version 1.0  (buildd@crested)  Sun Feb  1 20:25:37 UTC 2009
    
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig:  version 1.0  (buildmeister@builder58)  Fri Aug 14 18:33:37 PDT 2009
    
    Section "ServerLayout"
        Identifier     "Layout0"
        Screen      0  "Screen0" 0 0
        Screen      1  "Screen1" RightOf "Screen0"
    # commented out by update-manager, HAL is now used and auto-detects devices
    # Keyboard settings are now read from /etc/default/console-setup
    #    InputDevice    "Keyboard0" "CoreKeyboard"
    # commented out by update-manager, HAL is now used and auto-detects devices
    # Keyboard settings are now read from /etc/default/console-setup
    #    InputDevice    "Mouse0" "CorePointer"
    EndSection
    
    Section "Files"
    EndSection
    
    Section "ServerFlags"
        Option         "Xinerama" "0"
    EndSection
    
    # commented out by update-manager, HAL is now used and auto-detects devices
    # Keyboard settings are now read from /etc/default/console-setup
    #Section "InputDevice"
    #
    #    # generated from default
    #    Identifier     "Mouse0"
    #    Driver         "mouse"
    #    Option         "Protocol" "auto"
    #    Option         "Device" "/dev/psaux"
    #    Option         "Emulate3Buttons" "no"
    #    Option         "ZAxisMapping" "4 5"
    #EndSection
    
    # commented out by update-manager, HAL is now used and auto-detects devices
    # Keyboard settings are now read from /etc/default/console-setup
    #Section "InputDevice"
    #
    #    # generated from default
    #    Identifier     "Keyboard0"
    #    Driver         "kbd"
    #EndSection
    
    Section "Monitor"
        Identifier     "Monitor0"
        VendorName     "Unknown"
        ModelName      "QDS"
        HorizSync       30.0 - 75.0
        VertRefresh     60.0
        Option         "DPMS"
    EndSection
    
    Section "Monitor"
        Identifier     "Monitor1"
        VendorName     "Unknown"
        ModelName      "TV-0"
        HorizSync       28.0 - 55.0
        VertRefresh     43.0 - 72.0
    EndSection
    
    Section "Device"
        Identifier     "Device0"
        Driver         "nvidia"
        VendorName     "NVIDIA Corporation"
        BoardName      "GeForce 7150M / nForce 630M"
        BusID          "PCI:0:18:0"
        Screen          0
    EndSection
    
    Section "Device"
        Identifier     "Device1"
        Driver         "nvidia"
        VendorName     "NVIDIA Corporation"
        BoardName      "GeForce 7150M / nForce 630M"
        BusID          "PCI:0:18:0"
        Screen          1
    EndSection
    
    Section "Screen"
    
    # Removed Option "TwinView" "0"
    # Removed Option "metamodes" "DFP: nvidia-auto-select +0+0"
    # Removed Option "TwinView" "1"
    # Removed Option "metamodes" "CRT: nvidia-auto-select +0+0, DFP: nvidia-auto-select +0+0"
    # Removed Option "TwinView" "0"
    # Removed Option "metamodes" "DFP: nvidia-auto-select +0+0"
    # Removed Option "TwinView" "1"
    # Removed Option "metamodes" "CRT: nvidia-auto-select +1280+0, DFP: nvidia-auto-select +0+0"
        Identifier     "Screen0"
        Device         "Device0"
        Monitor        "Monitor0"
        DefaultDepth    24
        Option         "TwinView" "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" "TV: nvidia-auto-select +0+0"
        SubSection     "Display"
            Depth       24
        EndSubSection
    EndSection

  2. #2
    Join Date
    Sep 2007
    Location
    State College, PA
    Beans
    30
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: separate X screens - can't return pointer/cursor to primary screen

    Nobody?

    Well, if it's a mouse issue, I know that xorg.conf no longer controls the hardware, it's udev which does this. I also found all the udev ".rules" files in /lib/udev/rules.d/. I am not sure where to start now, though -- is this a mouse issue (or a monitor issue)? Can it even be fixed using these .rules files? I was hoping to start by comparing the rules for the touchpad and the USB mouse, and see if there are any clues there, but I'm having a hard time figuring out which devices are in which files.

    I also saw forum posts of touchpad problems/hacks that were fixed by creating a new .conf file in /usr/lib/X11/xorg.conf.d/.

    If anyone has any clues, even guesses, please help!

  3. #3
    Join Date
    Sep 2007
    Location
    State College, PA
    Beans
    30
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: separate X screens - can't return pointer/cursor to primary screen

    The upgrade to Ubuntu 10.10 has solved this issue. Since it appears I'm the only one with this problem, I'm going to mark as "solved" even though I never figured out what was wrong.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •