[Wayland-bugs] [Bug 794736] NULL pointer exception singal 11 (SEGV) in wl_proxy_marshal
https://bugzilla.gnome.org/show_bug.cgi?id=794736 Daniel Boles changed: What|Removed |Added Status|NEW |RESOLVED URL||https://gitlab.gnome.org/GN ||OME/gtk/issues/129 Resolution|--- |OBSOLETE -- You are receiving this mail because: You are on the CC list for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 105803] jumping cursor on dell xps
https://bugs.freedesktop.org/show_bug.cgi?id=105803 Bug ID: 105803 Summary: jumping cursor on dell xps Product: Wayland Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: libinput Assignee: wayland-bugs@lists.freedesktop.org Reporter: m...@gotu.dk Created attachment 138412 --> https://bugs.freedesktop.org/attachment.cgi?id=138412&action=edit evemu recording, that should contain 2-3 jumps my cursor is jumping every once in a while. i've tried following the guidelines to gather as much info as i can about the issue. i'm using latest Debian Buster/Sid, libinput 1.10.3, on a Dell XPS 9370 xinput list-props "DELL07E6:00 06CB:76AF Touchpad": Device 'DELL07E6:00 06CB:76AF Touchpad': Device Enabled (139): 1 Coordinate Transformation Matrix (141): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Tapping Enabled (280): 0 libinput Tapping Enabled Default (281): 0 libinput Tapping Drag Enabled (282):1 libinput Tapping Drag Enabled Default (283):1 libinput Tapping Drag Lock Enabled (284): 0 libinput Tapping Drag Lock Enabled Default (285): 0 libinput Tapping Button Mapping Enabled (286): 1, 0 libinput Tapping Button Mapping Default (287): 1, 0 libinput Natural Scrolling Enabled (288): 0 libinput Natural Scrolling Enabled Default (289): 0 libinput Disable While Typing Enabled (290):1 libinput Disable While Typing Enabled Default (291):1 libinput Scroll Methods Available (292):1, 1, 0 libinput Scroll Method Enabled (293): 1, 0, 0 libinput Scroll Method Enabled Default (294): 1, 0, 0 libinput Click Methods Available (295): 1, 1 libinput Click Method Enabled (296):1, 0 libinput Click Method Enabled Default (297):1, 0 libinput Middle Emulation Enabled (298):0 libinput Middle Emulation Enabled Default (299):0 libinput Accel Speed (300): 0.00 libinput Accel Speed Default (301): 0.00 libinput Left Handed Enabled (302): 0 libinput Left Handed Enabled Default (303): 0 libinput Send Events Modes Available (261): 1, 1 libinput Send Events Mode Enabled (262):0, 0 libinput Send Events Mode Enabled Default (263):0, 0 Device Node (264): "/dev/input/event20" Device Product ID (265):1739, 30383 libinput Drag Lock Buttons (304): libinput Horizontal Scroll Enabled (305): 1 udevadm info /sys/class/input/event20 : P: /devices/pci:00/:00:15.1/i2c_designware.1/i2c-8/i2c-DELL07E6:00/0018:06CB:76AF.0002/input/input26/event20 N: input/event20 S: input/by-path/pci-:00:15.1-platform-i2c_designware.1-event-mouse E: DEVLINKS=/dev/input/by-path/pci-:00:15.1-platform-i2c_designware.1-event-mouse E: DEVNAME=/dev/input/event20 E: DEVPATH=/devices/pci:00/:00:15.1/i2c_designware.1/i2c-8/i2c-DELL07E6:00/0018:06CB:76AF.0002/input/input26/event20 E: ID_INPUT=1 E: ID_INPUT_HEIGHT_MM=56 E: ID_INPUT_TOUCHPAD=1 E: ID_INPUT_WIDTH_MM=101 E: ID_PATH=pci-:00:15.1-platform-i2c_designware.1 E: ID_PATH_TAG=pci-_00_15_1-platform-i2c_designware_1 E: ID_SERIAL=noserial E: LIBINPUT_DEVICE_GROUP=18/6cb/76af:i2c-DELL07E6:00 E: LIBINPUT_MODEL_TOUCHPAD_VISIBLE_MARKER=1 E: MAJOR=13 E: MINOR=84 E: SUBSYSTEM=input E: USEC_INITIALIZED=4691620 cat /sys/class/dmi/id/modalias : dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: -- 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 105803] jumping cursor on dell xps
https://bugs.freedesktop.org/show_bug.cgi?id=105803 --- Comment #1 from Martin Jørgensen --- the physical dimensions are: 105 mm width x 60 mm height the whole surface is clickable, but it's easier to press the lower part of the path where it also intepres left,middle,right click depending on whether your finger is. -- 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 105803] jumping cursor on dell xps
https://bugs.freedesktop.org/show_bug.cgi?id=105803 --- Comment #2 from Martin Jørgensen --- Created attachment 138413 --> https://bugs.freedesktop.org/attachment.cgi?id=138413&action=edit xorg log, with the jump notifications -- 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 105803] jumping cursor on dell xps
https://bugs.freedesktop.org/show_bug.cgi?id=105803 Martin Jørgensen changed: What|Removed |Added Assignee|wayland-bugs@lists.freedesk |peter.hutte...@who-t.net |top.org | QA Contact||xorg-t...@lists.x.org Component|libinput|Input/libinput Product|Wayland |xorg -- 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 105804] Custom resolutions for Wayland
https://bugs.freedesktop.org/show_bug.cgi?id=105804 Bug ID: 105804 Summary: Custom resolutions for Wayland Product: Wayland Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: medium Component: wayland Assignee: wayland-bugs@lists.freedesktop.org Reporter: kkll...@gmail.com Hello I've been using Wayland for quite a long time already. Since one of my displays provides invalid EDID data, I'm unable to set the resolution properly, because the OS think that the device supports only 4 resolutions: 640x480, 848x480, 800x600 and 1024x768. Until lately, I used a hacky solution – forcing the kernel to load a specific EDID for specific output on boot. That way, I was able to use only resolution specified in that EDID. But lately, that solution stopped working on my machine, and, since Wayland does not support adding custom resolution, I was forced back to X, because thanks to xrandr I'm capable of doing so. I think that Wayland should have an option to replicate that feature. -- 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 105804] Custom resolutions for Wayland
https://bugs.freedesktop.org/show_bug.cgi?id=105804 Pekka Paalanen changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Pekka Paalanen --- Hi, adding custom video modes is a feature of your particular Wayland display server. All configuration is up to each Wayland display server individually. They could agree on a mutual configuration standard, but that would be out of scope for Wayland as understood by the bugzilla product/component in this bug. Loading an EDID file through the kernel seems like a good solution to me, so it might be worth figuring out why it stopped working. If you want to make a configuration with your display server, please consult your specific display server documentation. FWIW, for years people have come up once in a while suggesting that Wayland should replicate X11 RandR, but it has never gained enough traction with the major desktop projects to become a serious proposal. Sorry. I think two major counter-arguments are: a) access control, we do not want arbitrary applications changing video modes at will, and b) once the Wayland display server accepts connections so that an app could program a video mode, the server has already initialized the display hardware so it's too late and will lead to glitchy user experience. Drafting such an interface would also be a considerable amount of work for a feature that most big desktop environments already implement by some other means. -- 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 89323] Ability to adjust touchpad scrolling speed
https://bugs.freedesktop.org/show_bug.cgi?id=89323 --- Comment #4 from Krasi --- Hi I need the opposite , for me the scrolling speed is way too slow on P50 Peter: "this is something that would need to be sorted in the toolkits/compositor." Sorry I didn't quite understand where do I need to open the issue for this feature request? -- 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 105809] Clickpad: Allow scroll gesture in soft button area
https://bugs.freedesktop.org/show_bug.cgi?id=105809 Bug ID: 105809 Summary: Clickpad: Allow scroll gesture in soft button area Product: Wayland Version: 1.5.0 Hardware: All OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: libinput Assignee: wayland-bugs@lists.freedesktop.org Reporter: golo...@gmail.com # Scenario A Steps to reproduce: Start a two-finger scroll gesture, and then move one finger to the bottom of the clickpad (soft button area), Current behavior: When one finger reached the soft button area, the scroll is stopped. Wanted behavior: The scroll does not stop. # Scenario B Steps to reproduce: With two fingers placed on the soft button area, start a scroll gesture. Current behavior: No scroll. Wanted behavior: Do scroll. # Why 1. User can scroll more amount of offset in one gesture. 2. Consistency of human touch sense and human visual sense. When human performs a scroll gesture, the brain expects to see the screen scroll. If the finger moves but the screen doesn't move, the brain experiences an inconsistency, which induces a discomfort. -- 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 100271] Weston crashes after typing in GTK open dialog
https://bugs.freedesktop.org/show_bug.cgi?id=100271 --- Comment #5 from bugrepor...@safetymail.info --- It crashes on native Wayland for me. Here are the steps In terminal run weston Click weston-terminal and type gedit Press Ctrl+O, then start typing /home/username/.config/weston.ini - The actual file doesn't have to exist, but the dot after /home/username/ has to for the crash to occur. Interestingly, typing /home/.username/somefile doesn't crash. After pressing Enter in the file picker, within 1-3 secs click close icon in gedit. It should crash in 1-3 secs. Getting these in journalctl Process 10925 (weston) of user 1000 dumped core. Stack trace of thread 10925: #0 0x7f7b35090860 raise (libc.so.6) #1 0x7f7b350908e0 __restore_rt (libc.so.6) #2 0x55880e702e50 n/a (n/a) Process 10788 (weston) of user 1000 dumped core. Stack trace of thread 10788: #0 0x7fc41066a860 raise (libc.so.6) #1 0x7fc41066a8e0 __restore_rt (libc.so.6) #2 0x7fc41066a860 raise (libc.so.6) #3 0x7fc41066bec9 abort (libc.so.6) #4 0x7fc4106ad437 __libc_message (libc.so.6) #5 0x7fc4106b378b malloc_printerr (libc.so.6) #6 0x7fc4106b536c _int_free (libc.so.6) #7 0x7fc41104ac20 n/a (libwayland-server.so.0) #8 0x7fc41104f619 n/a (libwayland-server.so.0) #9 0x7fc41104acff wl_client_destroy (libwayland-server.so.0) #10 0x7fc41104adb9 n/a (libwayland-server.so.0) #11 0x7fc41104c9b2 wl_event_loop_dispatch (libwayland-server.so.0) #12 0x7fc41104b14c wl_display_run (libwayland-server.so.0) #13 0x556795293417 n/a (weston) #14 0x7fc410656f4a __libc_start_main (libc.so.6) #15 0x5567952939ba _start (weston) -- 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 105022] Lenovo P50 - Slow fine touchpad movement makes it jump
https://bugs.freedesktop.org/show_bug.cgi?id=105022 Krasi changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #32 from Krasi --- is the attachment ok? just to confirm that the mouse still jumps. Less often, but the issue is still there. I can make another recording if needed. -- 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 104828] Wobbly AlpsPS/2 ALPS DualPoint TouchPad
https://bugs.freedesktop.org/show_bug.cgi?id=104828 --- Comment #50 from Hi-Angel --- (In reply to Tomas Janousek from comment #46) > It should be noted that this code enables hysteresis on my ThinkPad (T25) > which previously didn't require any, making the touchpad unusable again. :-( > > Shall I open a new bug and attach what? libinput debug-events/evemu-record? Generally, it'd be interesting to see the output of "libinput debug-events --verbose" around the note about hysteresis being enabled. Unfortunately I'm a bit lost about how the code have evolved since last time I looked, and with the (old) git version I'm using (582e3c00) the note about hysteresis being enabled appears within the informational header, before I touch the touchpad, and not within the timecodes. Unless piped to grep — in which case it works differently, and only appears after touching the touchpad. So I'm personally lost a bit about how it all behaves ATM. -- 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
