[Wayland-bugs] [Bug 106179] weston-launch does not restore the interface
https://bugs.freedesktop.org/show_bug.cgi?id=106179 --- Comment #4 from Dilian--- Created attachment 139034 --> https://bugs.freedesktop.org/attachment.cgi?id=139034=edit Log of weston-launch, when it does not restore to the GUI This is the file `stdbuf -o 0 -e 0 weston-launch -v` generate from its start, until it doesn't return to the graphical interface after pressing Ctrl+Alt+Fn, and is then terminated with Alt+Backspace. The line "[07:14:56.166] activating session" is printed after pressing Alt+Backspace. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106141] Thinkpad X240 touchpad movement is jumpy and extremely imprecise
https://bugs.freedesktop.org/show_bug.cgi?id=106141 --- Comment #18 from abdulkadirfsa...@gmail.com --- (In reply to Peter Hutterer from comment #15) > > won't even detect two finger scroll now. > > that's... strange. the code that looks at the speed setting is not called > from the two-finger scrolling code. > > Can you confirm please: > At the speed where you notice the bumps, is the default speed in synaptics > faster or slower than libinput? > > Can you observe the bumps in synaptics? They are most likely smaller but > still there, so watch closely, do you get 1-3 pixel jumps with synaptics > when libinput jumps a lot more? Synaptics driver's speed is in no way slow. There are tiny bumps in synaptics also, maybe 1-3 pixels like you said. The acceleration in synaptics is much lower. I wasn't sure which setting was cursor speed so attached all synaptics parameters. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 105222] RFE: keyboard debouncing
https://bugs.freedesktop.org/show_bug.cgi?id=105222 Peter Huttererchanged: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |WONTFIX --- Comment #12 from Peter Hutterer --- Closing this bug as WONTFIX (again), sorry, see comment #11 for the reasons. I don't think we can have a good implementation that is reliable in libinput. I think that if a keyboard debouncing feature like this is implemented, it has to sit in the compositor where it's much easier to control through configuration options. libinput is too low-level for this. XKB already has something similar anyway for accessibility reasons so there's a chance that compositors can re-use that implementation. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106141] Thinkpad X240 touchpad movement is jumpy and extremely imprecise
https://bugs.freedesktop.org/show_bug.cgi?id=106141 --- Comment #17 from abdulkadirfsa...@gmail.com --- Created attachment 139033 --> https://bugs.freedesktop.org/attachment.cgi?id=139033=edit synaptics parameters -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 101139] Acceleration still too fast with slow and slow-medium finger movements
https://bugs.freedesktop.org/show_bug.cgi?id=101139 --- Comment #47 from Peter Hutterer--- Ok, another version to test please: https://github.com/whot/libinput/tree/wip/touchpad-pointer-accel-v6 Still feels roughly like the macOS one though there are some differences that tbh I can't quite put my finger on. Either way, it feels precise enough, especially at -0.1 (for me). -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 101806] plasma 5: system settings crashes when I leave desktop effects kcm
https://bugs.freedesktop.org/show_bug.cgi?id=101806 Timothy Arcerichanged: What|Removed |Added Product|Mesa|Wayland Component|Mesa core |wayland Assignee|mesa-dev@lists.freedesktop. |wayland-bugs@lists.freedesk |org |top.org QA Contact|mesa-dev@lists.freedesktop. | |org | --- Comment #4 from Timothy Arceri --- Since it crashed inside Wayland client lets move this bug there to start with. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106141] Thinkpad X240 touchpad movement is jumpy and extremely imprecise
https://bugs.freedesktop.org/show_bug.cgi?id=106141 --- Comment #16 from Peter Hutterer--- ok, I just replayed this here to check a patch that I thought would fix this - this data is complete garbage. It has a distinct saw tooth behaviour that causes the jumpy behaviour, e.g.: 19.038526: ↙↓ -1/ 1 | *** | 19.047722: ↙← -2/ 1 | *** | 19.057847: ↙← -2/ 1 | *** | 19.068035: ↙← -4/ 1 | *** | 19.078270: ↙← -22/ 1 | *** | 19.088396: ↙← -22/ 21 | *** | 19.097523: ↙↓ -1/ 21 | *** | 19.107754: ↙↓ -2/ 21 | *** | 19.117948: ↙↓ -1/ 21 | *** | 19.128083: ↙↓ -2/ 21 | *** | or: 17.026707: →↘ 22/ 1 | *** | 17.036102: →↘ 22/ 1 | *** | 17.046134: →↘ 22/ 1 | *** | 17.056361: →↘ 22/ 1 | *** | 17.066739: →↘1/ 1 | *** | 17.096367: →↘1/ 1 | *** | 17.106718: ↓↘1/ 19 | *** | 17.116698: ↓↘1/ 19 | *** | 17.127087: ↓↘1/ 19 | *** | 17.137231: ↓↘1/ 19 | *** | The questions in comment #15 are still valid but I suspect the only way to get rid of those jumps is by turning the pointer acceleration down by quite a bit. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106141] Thinkpad X240 touchpad movement is jumpy and extremely imprecise
https://bugs.freedesktop.org/show_bug.cgi?id=106141 Peter Huttererchanged: What|Removed |Added Status|ASSIGNED|NEEDINFO --- Comment #15 from Peter Hutterer --- > won't even detect two finger scroll now. that's... strange. the code that looks at the speed setting is not called from the two-finger scrolling code. Can you confirm please: At the speed where you notice the bumps, is the default speed in synaptics faster or slower than libinput? Can you observe the bumps in synaptics? They are most likely smaller but still there, so watch closely, do you get 1-3 pixel jumps with synaptics when libinput jumps a lot more? -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106113] libinput loses track and completely stops responding during two-finger scrolling
https://bugs.freedesktop.org/show_bug.cgi?id=106113 Peter Huttererchanged: What|Removed |Added Status|REOPENED|NEEDINFO --- Comment #8 from Peter Hutterer --- Please confirm: * this is an issue with the touch size or not (by testing git master) * there are stray button events coming from the device? if so, needs a separate bug -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 101147] Elantech touchpad double Tap Time too short on ASUS Zenbook UX410UQ
https://bugs.freedesktop.org/show_bug.cgi?id=101147 Peter Huttererchanged: What|Removed |Added Status|NEEDINFO|ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106109] Touchpad and Trackpoint locked together
https://bugs.freedesktop.org/show_bug.cgi?id=106109 --- Comment #7 from Peter Hutterer--- all good, I CC'd myself (I think :). iirc Gitlab automatically adds someone if you mention them by their handle. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106036] IBM Scrollpoint mouse: libinput mouse scrolling speed insanely fast
https://bugs.freedesktop.org/show_bug.cgi?id=106036 --- Comment #9 from Peter Hutterer--- the direction locking is very mild, it's supposed to help with vertical scrolling to not introduce any undue horizontal movement. There's a built-in trigger that needs to be exceeded before we start sending events for the other direction. It's definitely not a hard lock - you can scroll in all directions at all times. But your output above shows that it's (probably) working, you don't get any horiz movement in the vertical scroll even though, most likely, you have the odd horizontal event in the output. > Probably I should add a > struct normalized_coords unaccel; > instead of abusing wheel_degrees which was already declared in > fallback_flush_wheels() for a final version of the changes? yeah, that sounds good. I'm always in favour of localised variables that make the code more obvious, the compiler optimises them away anyway. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106197] plasma wayland cant create platform surface with mesa 18.1.0 rc1
https://bugs.freedesktop.org/show_bug.cgi?id=106197 Bug ID: 106197 Summary: plasma wayland cant create platform surface with mesa 18.1.0 rc1 Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: EGL/Wayland Assignee: wayland-bugs@lists.freedesktop.org Reporter: farmboy0+freedesk...@googlemail.com QA Contact: mesa-...@lists.freedesktop.org The error is EGL user error 0x3009 (EGL_BAD_MATCH) in eglCreatePlatformWindowSurfaceEXT Reverting to mesa 18.0.1 fixes this. Snippet from the log: kwin_wayland_drm: Using Atomic Mode Setting. kwin_wayland_drm: Number of planes: 12 kwin_wayland_drm: Atomic init for plane: 36 kwin_wayland_drm: 36: type' (id 7): 1 kwin_wayland_drm: "type" has enums: QVector("Primary", "Cursor", "Overlay") kwin_wayland_drm: Test all 3 possible enums: kwin_wayland_drm: Enum 'Overlay': runtime-value = 0 kwin_wayland_drm: Enum 'Primary': runtime-value = 1 kwin_wayland_drm: Enum 'Cursor': runtime-value = 2 kwin_wayland_drm: => "type" with mapped enum value "Primary" kwin_wayland_drm: 36: SRC_X' (id 8): 0 kwin_wayland_drm: 36: SRC_Y' (id 9): 0 kwin_wayland_drm: 36: SRC_W' (id 10): 125829120 kwin_wayland_drm: 36: SRC_H' (id 11): 70778880 kwin_wayland_drm: 36: CRTC_X' (id 12): 0 kwin_wayland_drm: 36: CRTC_Y' (id 13): 0 kwin_wayland_drm: 36: CRTC_W' (id 14): 1920 kwin_wayland_drm: 36: CRTC_H' (id 15): 1080 kwin_wayland_drm: 36: FB_ID' (id 16): 89 kwin_wayland_drm: 36: CRTC_ID' (id 19): 43 kwin_wayland_drm: Supported Transformations: QFlags() on plane 36 kwin_wayland_drm: Atomic init for plane: 37 kwin_wayland_drm: 37: type' (id 7): 1 kwin_wayland_drm: "type" has enums: QVector("Primary", "Cursor", "Overlay") kwin_wayland_drm: Test all 3 possible enums: kwin_wayland_drm: Enum 'Overlay': runtime-value = 0 kwin_wayland_drm: Enum 'Primary': runtime-value = 1 kwin_wayland_drm: Enum 'Cursor': runtime-value = 2 kwin_wayland_drm: => "type" with mapped enum value "Primary" kwin_wayland_drm: 37: SRC_X' (id 8): 0 kwin_wayland_drm: 37: SRC_Y' (id 9): 0 kwin_wayland_drm: 37: SRC_W' (id 10): 0 kwin_wayland_drm: 37: SRC_H' (id 11): 0 kwin_wayland_drm: 37: CRTC_X' (id 12): 0 kwin_wayland_drm: 37: CRTC_Y' (id 13): 0 kwin_wayland_drm: 37: CRTC_W' (id 14): 0 kwin_wayland_drm: 37: CRTC_H' (id 15): 0 kwin_wayland_drm: 37: FB_ID' (id 16): 0 kwin_wayland_drm: 37: CRTC_ID' (id 19): 0 kwin_wayland_drm: Supported Transformations: QFlags() on plane 37 kwin_wayland_drm: Atomic init for plane: 38 kwin_wayland_drm: 38: type' (id 7): 1 kwin_wayland_drm: "type" has enums: QVector("Primary", "Cursor", "Overlay") kwin_wayland_drm: Test all 3 possible enums: kwin_wayland_drm: Enum 'Overlay': runtime-value = 0 kwin_wayland_drm: Enum 'Primary': runtime-value = 1 kwin_wayland_drm: Enum 'Cursor': runtime-value = 2 kwin_wayland_drm: => "type" with mapped enum value "Primary" kwin_wayland_drm: 38: SRC_X' (id 8): 0 kwin_wayland_drm: 38: SRC_Y' (id 9): 0 kwin_wayland_drm: 38: SRC_W' (id 10): 0 kwin_wayland_drm: 38: SRC_H' (id 11): 0 kwin_wayland_drm: 38: CRTC_X' (id 12): 0 kwin_wayland_drm: 38: CRTC_Y' (id 13): 0 kwin_wayland_drm: 38: CRTC_W' (id 14): 0 kwin_wayland_drm: 38: CRTC_H' (id 15): 0 kwin_wayland_drm: 38: FB_ID' (id 16): 0 kwin_wayland_drm: 38: CRTC_ID' (id 19): 0 kwin_wayland_drm: Supported Transformations: QFlags() on plane 38 kwin_wayland_drm: Atomic init for plane: 39 kwin_wayland_drm: 39: type' (id 7): 1 kwin_wayland_drm: "type" has enums: QVector("Primary", "Cursor", "Overlay") kwin_wayland_drm: Test all 3 possible enums: kwin_wayland_drm: Enum 'Overlay': runtime-value = 0 kwin_wayland_drm: Enum 'Primary': runtime-value = 1 kwin_wayland_drm: Enum 'Cursor': runtime-value = 2 kwin_wayland_drm: => "type" with mapped enum value "Primary" kwin_wayland_drm: 39: SRC_X' (id 8): 0 kwin_wayland_drm: 39: SRC_Y' (id 9): 0 kwin_wayland_drm: 39: SRC_W' (id 10): 0 kwin_wayland_drm: 39: SRC_H' (id 11): 0 kwin_wayland_drm: 39: CRTC_X' (id 12): 0 kwin_wayland_drm: 39: CRTC_Y' (id 13): 0 kwin_wayland_drm: 39: CRTC_W' (id 14): 0 kwin_wayland_drm: 39: CRTC_H' (id 15): 0 kwin_wayland_drm: 39: FB_ID' (id 16): 0 kwin_wayland_drm: 39: CRTC_ID' (id 19): 0 kwin_wayland_drm: Supported Transformations: QFlags() on plane 39 kwin_wayland_drm: Atomic init for plane: 40 kwin_wayland_drm: 40: type' (id 7): 1 kwin_wayland_drm: "type" has enums: QVector("Primary", "Cursor", "Overlay") kwin_wayland_drm: Test all 3 possible enums: kwin_wayland_drm: Enum 'Overlay': runtime-value = 0 kwin_wayland_drm: Enum 'Primary': runtime-value = 1 kwin_wayland_drm: Enum 'Cursor': runtime-value = 2 kwin_wayland_drm: => "type" with mapped enum value "Primary" kwin_wayland_drm: 40: SRC_X' (id 8): 0 kwin_wayland_drm: 40: SRC_Y' (id 9): 0 kwin_wayland_drm: 40: SRC_W' (id 10): 0 kwin_wayland_drm: 40: SRC_H' (id 11): 0 kwin_wayland_drm: 40:
[Wayland-bugs] [Bug 105908] libinput: Palm detection does not seem to work at all for Lenovo X1 Carbon Sixth Generation
https://bugs.freedesktop.org/show_bug.cgi?id=105908 --- Comment #28 from naj...@posteo.net --- Thanks, but it will not build on my system. For, I get this error: Native dependency gtk+-3.0 found: NO found '3.18.9' but need: '>= 3.20' Still, Mint is about to be put onto the Ubuntu 18 base, which will mean a new libinput (and indeed a new gtk). -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106036] IBM Scrollpoint mouse: libinput mouse scrolling speed insanely fast
https://bugs.freedesktop.org/show_bug.cgi?id=106036 --- Comment #8 from peter.ganzh...@gmail.com --- Ok, this sounds reasonable to me. 1. I reverted all changes to /lib/udev/hwdb.d/70-mouse.hwdb. 2. I reverted all previous changes in fallback_flush_wheels() and inserted the following: if (device->model_flags & EVDEV_MODEL_SCROLLPOINT) { // Scrollpoint: Normalize scroll coords in wheel degrees and use evdev_post_scroll(). dispatch->wheel.y *= -1; normalize_delta(device, >wheel, _degrees); evdev_post_scroll(device, time, LIBINPUT_POINTER_AXIS_SOURCE_CONTINUOUS, _degrees); dispatch->wheel.x = 0; dispatch->wheel.y = 0; return; } Probably I should add a struct normalized_coords unaccel; instead of abusing wheel_degrees which was already declared in fallback_flush_wheels() for a final version of the changes? This leads to the following output of libinput-debug-events while using the scrollpoint: event13 POINTER_AXIS +1.34s vert 10.00* horiz 0.00 (continuous) event13 POINTER_AXIS +1.40s vert 10.00* horiz 0.00 (continuous) event13 POINTER_AXIS +1.45s vert 9.00* horiz 0.00 (continuous) event13 POINTER_AXIS +1.50s vert 22.00* horiz 0.00 (continuous) event13 POINTER_AXIS +1.55s vert 17.00* horiz 0.00 (continuous) event13 POINTER_AXIS +1.60s vert 16.00* horiz 0.00 (continuous) event13 POINTER_AXIS +2.02s vert -8.00* horiz 0.00 (continuous) event13 POINTER_AXIS +2.06s vert -17.00* horiz 0.00 (continuous) event13 POINTER_AXIS +2.11s vert -18.00* horiz 0.00 (continuous) event13 POINTER_AXIS +2.17s vert -23.00* horiz 0.00 (continuous) event13 POINTER_AXIS +2.22s vert -25.00* horiz 0.00 (continuous) event13 POINTER_AXIS +2.27s vert -22.00* horiz 0.00 (continuous) event13 POINTER_AXIS +2.32s vert -17.00* horiz 0.00 (continuous) event13 POINTER_AXIS +2.38s vert -1.00* horiz 0.00 (continuous) event13 POINTER_AXIS +3.14s vert 0.00 horiz -5.00* (continuous) event13 POINTER_AXIS +3.19s vert 0.00 horiz -14.00* (continuous) event13 POINTER_AXIS +3.24s vert 0.00 horiz -19.00* (continuous) event13 POINTER_AXIS +3.30s vert 0.00 horiz -30.00* (continuous) event13 POINTER_AXIS +3.34s vert 0.00 horiz -25.00* (continuous) event13 POINTER_AXIS +3.40s vert 0.00 horiz -11.00* (continuous) event13 POINTER_AXIS +3.45s vert 0.00 horiz -6.00* (continuous) event13 POINTER_AXIS +3.81s vert -1.00* horiz 0.00 (continuous) event13 POINTER_AXIS +3.86s vert -3.00* horiz 0.00 (continuous) event13 POINTER_AXIS +3.91s vert -1.00* horiz 1.00* (continuous) event13 POINTER_AXIS +3.96s vert 0.00 horiz 6.00* (continuous) event13 POINTER_AXIS +4.01s vert 0.00 horiz 4.00* (continuous) event13 POINTER_AXIS +4.06s vert 0.00 horiz 6.00* (continuous) event13 POINTER_AXIS +4.11s vert -6.00* horiz 0.00 (continuous) evemu-record shows this: E: 1.375987 0002 0008 -003 # EV_REL / REL_WHEEL-3 E: 1.375987 # SYN_REPORT (0) -- +456ms E: 1.431967 0002 0008 -034 # EV_REL / REL_WHEEL-34 E: 1.431967 # SYN_REPORT (0) -- +56ms E: 1.479969 0002 0008 -047 # EV_REL / REL_WHEEL-47 E: 1.479969 # SYN_REPORT (0) -- +48ms E: 1.535961 0002 0008 -054 # EV_REL / REL_WHEEL-54 E: 1.535961 # SYN_REPORT (0) -- +56ms E: 1.583955 0002 0008 -056 # EV_REL / REL_WHEEL-56 E: 1.583955 # SYN_REPORT (0) -- +48ms E: 1.639955 0002 0008 -051 # EV_REL / REL_WHEEL-51 E: 1.639955 # SYN_REPORT (0) -- +56ms E: 1.687952 0002 0008 -022 # EV_REL / REL_WHEEL-22 E: 1.687952 # SYN_REPORT (0) -- +48ms E: 1.943965 0002 0008 0005 # EV_REL / REL_WHEEL5 E: 1.943965 0002 0006 0003 # EV_REL / REL_HWHEEL 3 E: 1.943965 # SYN_REPORT (0) -- +256ms E: 1.991957 0002 0008 0006 # EV_REL / REL_WHEEL6 E: 1.991957 0002 0006 0020 # EV_REL / REL_HWHEEL 20 E: 1.991957 # SYN_REPORT (0) -- +48ms E: 2.047935 0002 0006 0024 # EV_REL / REL_HWHEEL 24 E: 2.047935 # SYN_REPORT (0) -- +56ms E: 2.095925 0002 0008 0001 # EV_REL / REL_WHEEL1 E: 2.095925 0002 0006 0026 # EV_REL / REL_HWHEEL 26 E: 2.095925 #
[Wayland-bugs] [Bug 106109] Touchpad and Trackpoint locked together
https://bugs.freedesktop.org/show_bug.cgi?id=106109 --- Comment #6 from Kadir--- (In reply to Peter Hutterer from comment #5) > start with mutter and let's see how we go from there. Please CC me on it > (@whot on gitlab) I submitted the bug at Gitlab, https://gitlab.gnome.org/GNOME/mutter/issues/128 I don't know how to CC you on Gitlab :) -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106179] weston-launch does not restore the interface
https://bugs.freedesktop.org/show_bug.cgi?id=106179 --- Comment #3 from Pekka Paalanen--- The reason I asked you to redirect weston-launch output into a file is because that will actually be Weston's log output and it will print lots. But if you do not redirect it into a file, you will lose it, because the virtual terminal printing stops working as soon as Weston starts. weston-launch is only necessary if you do not run a system service similar to logind. This is mentioned in the weston man page. I would not expect this to be related to your problem though. I have a suspicion, but for that I'd need the Weston log. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 105908] libinput: Palm detection does not seem to work at all for Lenovo X1 Carbon Sixth Generation
https://bugs.freedesktop.org/show_bug.cgi?id=105908 --- Comment #27 from Peter Hutterer--- ok, I just got mint 18.03 and checked the libinput version and it's 1.6.3. That version is over a year old, so most of the palm detection behaviour simply missing. Mint needs to update the package. tbh, you're probably better off just installing libinput from git. It's stable enough that you can even run git master any day without having to worry about breakages. https://wayland.freedesktop.org/libinput/doc/latest/building_libinput.html -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106179] weston-launch does not restore the interface
https://bugs.freedesktop.org/show_bug.cgi?id=106179 --- Comment #2 from Dilian--- weston-launch -v does not print anything. When I installed Weston I looked for way how to start it, then I found weston-launch, it worked, so I use it. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106179] weston-launch does not restore the interface
https://bugs.freedesktop.org/show_bug.cgi?id=106179 --- Comment #1 from Pekka Paalanen--- Could you redirect both stdout and stderr of weston-launch into a file, reproduce the issue, and attach the file here? Do you actually need to use weston-launch? You should never kill 'weston-launch', at least with SIGKILL, because that may leave your VT in a useless state. Try killing 'weston' instead. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106141] Thinkpad X240 touchpad movement is jumpy and extremely imprecise
https://bugs.freedesktop.org/show_bug.cgi?id=106141 --- Comment #14 from abdulkadirfsa...@gmail.com --- I reduced the touchpad speed all the way in settings and tested. The mouse is too slow and just - feels weird still. Inaccurate and won't even detect two finger scroll now. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106141] Thinkpad X240 touchpad movement is jumpy and extremely imprecise
https://bugs.freedesktop.org/show_bug.cgi?id=106141 --- Comment #13 from abdulkadirfsa...@gmail.com --- Created attachment 138991 --> https://bugs.freedesktop.org/attachment.cgi?id=138991=edit Reduced touchpad speed evemu-record -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106109] Touchpad and Trackpoint locked together
https://bugs.freedesktop.org/show_bug.cgi?id=106109 --- Comment #5 from Peter Hutterer--- start with mutter and let's see how we go from there. Please CC me on it (@whot on gitlab) -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs