Skip to content

Not able to use Dual Touchscreens Properly #1231

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
aldenparker opened this issue Mar 9, 2025 · 7 comments
Open

Not able to use Dual Touchscreens Properly #1231

aldenparker opened this issue Mar 9, 2025 · 7 comments
Labels
bug Something isn't working

Comments

@aldenparker
Copy link

When using Niri on my Asus Zenbook Duo, the two touch screens seem to be registered, but do not actual initiate mouse clicks. When I tap the screen, the mouse cursor disappears and the focus is shifted, but only once and then doesn't do it again until make another mouse input. I have setup touchpad configuration below.

System Information

Touchpad Config (Nix)

touchpad = {
  tap = true;
  natural-scroll = true;
  click-method = "clickfinger";
};

Relevant Libinput Device Output

Device:           ELAN1406:00 04F3:3101 Mouse
Kernel:           /dev/input/event23
Group:            7
Seat:             seat0, default
Capabilities:     pointer 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   *button
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   flat *adaptive custom
Rotation:         n/a

Device:           ELAN1406:00 04F3:3101 Touchpad
Kernel:           /dev/input/event24
Group:            7
Seat:             seat0, default
Size:             58x81mm
Capabilities:     pointer gesture
Tap-to-click:     disabled
Tap-and-drag:     enabled
Tap drag lock:    disabled
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: disabled
Calibration:      n/a
Scroll methods:   *two-finger edge 
Click methods:    *button-areas clickfinger 
Disable-w-typing: enabled
Disable-w-trackpointing: enabled
Accel profiles:   flat *adaptive custom
Rotation:         n/a

Device:           ELAN1406:00 04F3:3101 Keyboard
Kernel:           /dev/input/event25
Group:            7
Seat:             seat0, default
Capabilities:     keyboard 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0.0

Device:           ELAN9008:00 04F3:29B6
Kernel:           /dev/input/event14
Group:            8
Seat:             seat0, default
Size:             332x188mm
Capabilities:     touch 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      identity matrix
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0.0

Device:           ELAN9008:00 04F3:29B6 Stylus
Kernel:           /dev/input/event27
Group:            8
Seat:             seat0, default
Size:             343x194mm
Capabilities:     tablet 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      identity matrix
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   none
Rotation:         n/a

Device:           ELAN9009:00 04F3:29A1
Kernel:           /dev/input/event16
Group:            9
Seat:             seat0, default
Size:             332x96mm
Capabilities:     touch 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      identity matrix
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0.0

Device:           ELAN9009:00 04F3:29A1 Stylus
Kernel:           /dev/input/event19
Group:            9
Seat:             seat0, default
Size:             343x98mm
Capabilities:     tablet 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      identity matrix
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   none
Rotation:         n/a
  • niri version: niri stable v25.02 (commit b94a5db)
  • Distro: NixOS Stable (24.11)
  • GPU: NVIDIA GeForce RTX 2060 Mobile
  • CPU: Intel(R) Core(TM) i9-10980HK
@aldenparker aldenparker added the bug Something isn't working label Mar 9, 2025
@YaLTeR
Copy link
Owner

YaLTeR commented Mar 9, 2025

Touchpad is unrelated to touch.

I suspect that currently niri can only map all touchscreens to one output, and you might have to do it manually like so: https://github.com/YaLTeR/niri/wiki/Configuration:-Input

input {
    touch {
        map-to-output "eDP-1"
    }
}

Could you try to see if that makes at least one of the touchscreens work right? What I expect to happen is that both of them work, but both are mapped to the same screen (so only one is really usable).

@aldenparker
Copy link
Author

aldenparker commented Mar 9, 2025

Yes this did allow me to use the main touchscreen and yes it does map the second touchscreen to that main output. Is there anyway to individually map the outputs?

(PS. I skipped over this setting in documentation since I read somewhere else in the docks that by leaving it out the touchscreen would be mapped to all displays. I realize now this would only map 1 touchscreen to all displays and may have been confused with the two touchscreens)

@YaLTeR
Copy link
Owner

YaLTeR commented Mar 9, 2025

Not yet. So this would be #371

@aldenparker
Copy link
Author

aldenparker commented Mar 9, 2025

Fantastic thank you for clarifying. This can be marked as duplicate then.

@YaLTeR
Copy link
Owner

YaLTeR commented Mar 11, 2025

I mentioned this case in that issue. I have a question: do these dual touchscreens work without manual mapping anywhere else on Linux? Like GNOME or KDE? Because I'm still not sure if it's possible to automatically fetch the touch input to screen mapping from anywhere.

@aldenparker
Copy link
Author

aldenparker commented Mar 16, 2025

Yes it works perfectly with KDE. Auto fetches it and allows mapping to specific screens. Newest plasma 6. I did have to go into settings and manually adjust which touch panel maps to which screen though.

@YaLTeR
Copy link
Owner

YaLTeR commented Mar 16, 2025

I did have to go into settings and manually adjust which touch panel maps to which screen though.

So it wasn't correct automatically. What did they map to automatically?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants