[Wayland-bugs] [Bug 95280] Middle button not working in X11 the same as with synaptics driver
https://bugs.freedesktop.org/show_bug.cgi?id=95280 --- Comment #13 from Marco Arioli --- Thank you very much! I didn't realize that "upper" buttons were connected to trackpoint and not to touchpad. -- 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 94910] The cursor "jump" sometimes
https://bugs.freedesktop.org/show_bug.cgi?id=94910
--- Comment #39 from Paviluf ---
(In reply to Dudley Du from comment #38)
> As the data shown in the event14.txt file, I found the ATTRS{baseline}="155
> 27",
> This baseline value should be abnormal, it should be force re-calibrated
> through the calibrate interface without any finger/conductor on it.
An other bug for this touchpad I guess... No one should have to force
re-calibrated his touchpad...
Dudley can you give me the v. 2.0 of the firmware please. Just in case there is
more bug in 2.1. Thanks !
--
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 766341] Do not rely on memfd as it requires a fairly recent kernel
https://bugzilla.gnome.org/show_bug.cgi?id=766341 --- Comment #11 from Ray Strode [halfline] --- we may have to check for EPERM in addition to ENOSYS. see this, oddly coincidental, irc log from this morning: [07:15:26] i fail to run GTK3 apps under wayland - it crashes with "creating shared memory file failed: Operation not permitted" [07:16:37] it crashes in create_shm_pool in gdkdisplay-wayland.c [07:26:40] memeka: what's the output of 'uname -a' ? [07:27:11] kernel 3.10.96, armv7l [07:27:37] memeka: and the version of gtk3 ? [07:27:52] i'm running debian, only created a root user [07:27:55] gtk3.20 [07:28:19] halfline, shouldn't that cause something like ENOSYS rather than EPERM? [07:28:46] memeka: sounds like you're hitting https://bugzilla.gnome.org/show_bug.cgi?id=766341 [07:28:49] pq: you'd think [07:28:55] :-p [07:29:14] pq: but apparently not ...his kernel is too old for memfd_create [07:29:18] and he's getting EPERM [07:29:41] right, that confused me [07:32:18] pq: i wonder if __NR_memfd_create maps to a different syscall [07:32:35] pq: (say it's accidentally getting the x86 number or something) -- 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 766341] Do not rely on memfd as it requires a fairly recent kernel
https://bugzilla.gnome.org/show_bug.cgi?id=766341 --- Comment #12 from Simon McVittie --- (In reply to Ray Strode [halfline] from comment #11) > we may have to check for EPERM in addition to ENOSYS. see this, oddly > coincidental, irc log from this morning I'd be tempted to ignore errno and just assume that any memfd_create() failure should result in fallback... is there any reason memfd_create() could fail where trying shm_open() wouldn't be a valid fallback? Looking at the memfd_create man page, EMFILE/ENFILE would fail in the same way for shm_open(), ENOMEM would probably have the same result for shm_open() too, and EINVAL can only happen if it's used wrong. -- 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 764310] Certain menus display at wrong position in configured multi-monitor setups under Wayland
https://bugzilla.gnome.org/show_bug.cgi?id=764310 Olivier Fourdan changed: What|Removed |Added CC||ofour...@redhat.com, ||r...@robster.org.uk, ||wayland-bugs@lists.freedesk ||top.org Component|wayland |Backend: Wayland Version|3.18.x |unspecified Assignee|mutter-ma...@gnome.bugs |gtk-b...@gtk.org Product|mutter |gtk+ QA Contact|mutter-ma...@gnome.bugs |gtk-b...@gtk.org --- Comment #1 from Olivier Fourdan --- Actually, I don't think this is mutter, but gtk/gdk. Looks like it's basing it's placing its menu based on the workarea using the 1st monitor size and position... This is still broken in 3.20 and current master, and can cause the menu to be placed completely off screen depending on the monitor layout... => moving to gtk+ -- 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 766341] Do not rely on memfd as it requires a fairly recent kernel
https://bugzilla.gnome.org/show_bug.cgi?id=766341 Ray Strode [halfline] changed: What|Removed |Added Attachment #327740|0 |1 is obsolete|| --- Comment #13 from Ray Strode [halfline] --- Created attachment 327791 --> https://bugzilla.gnome.org/attachment.cgi?id=327791&action=edit wayland: fall back to shm_open if memfd unavailable Debian stable currently ships with a 3.16 kernel, so it doesn't have memfd available. This commit adds shm_open fall back code for that case (for now). -- 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 764310] Certain menus display at wrong position in configured multi-monitor setups under Wayland
https://bugzilla.gnome.org/show_bug.cgi?id=764310 --- Comment #2 from Olivier Fourdan --- gtkmenu uses the workarea of the monitor where the menu is placed by doing: gdk_device_get_position (pointer, ..., &x, &y); monitor_num = gdk_screen_get_monitor_at_point (screen, x, y); gdk_screen_get_monitor_workarea (screen, monitor_num, &workarea); On Wayland, there is no global coordinates so gdk_device_get_position() returns relative position to the toplevel, so it will most likely fall in the first monitor. That in itself is wrong, but it won't cause much problem for most as the first monitor is usually placed in (0, 0). But if the monitor layout is set so the first monitor is shifted down, these values returned by gdk_device_get_position() fall outside of any monitor. +--+ x | | | | +---+ | | | | | | | | | | | | | +---+--+ PS: I reckon X11 impl is wrong as well, not as bad, but still wrong as it uses the workarea which is shifted down and reduced in height by the location of the first monitor, using such a monitor layout so the menu is misplaced as well on X11.. -- 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 765181] [Wayland] After renaming a file/folder, caret navigation and cursor is broken
https://bugzilla.gnome.org/show_bug.cgi?id=765181 Christian Stadelmann changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #11 from Christian Stadelmann --- This issue is gone with an update to gnome 3.20.2 (Gtk+ 3.20.4). Thank you! -- 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 764310] Certain menus display at wrong position in configured multi-monitor setups under Wayland
https://bugzilla.gnome.org/show_bug.cgi?id=764310 Olivier Fourdan changed: What|Removed |Added See Also||https://bugzilla.gnome.org/ ||show_bug.cgi?id=756579 --- Comment #3 from Olivier Fourdan --- This case should be covered by bug 756579 -- 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 95393] ELAN1000 touchpad erratic pointer after 1.2.4 -> 1.3.0 upgrade
https://bugs.freedesktop.org/show_bug.cgi?id=95393 Bug ID: 95393 Summary: ELAN1000 touchpad erratic pointer after 1.2.4 -> 1.3.0 upgrade Product: Wayland Version: 1.3.0 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: libinput Assignee: wayland-bugs@lists.freedesktop.org Reporter: ija...@gmail.com Created attachment 123733 --> https://bugs.freedesktop.org/attachment.cgi?id=123733&action=edit evemu-describe output Hi! After upgrading libinput to 1.3.0 from 1.2.4 in Arch Linux, the touchpad pointer movement became very erratic, the cursor jumps around. It feels like it barely detects my finger, instead of smooth movement the pointer skips and jumps. After downgrading libinput to 1.2.4 the pointer smoothly follows my finger. I've attached evemu-describe output. -- 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 766405] New: Stack shows incorrect frame in widget factory on wayland
https://bugzilla.gnome.org/show_bug.cgi?id=766405 Bug ID: 766405 Summary: Stack shows incorrect frame in widget factory on wayland Classification: Platform Product: gtk+ Version: unspecified OS: Linux Status: NEW Severity: normal Priority: Normal Component: Backend: Wayland Assignee: gtk-b...@gtk.org Reporter: mattdang...@gmail.com QA Contact: gtk-b...@gtk.org CC: r...@robster.org.uk, wayland-bugs@lists.freedesktop.org GNOME version: --- >From Timm Bäder on irc, on wayland sometimes stack shows a double drawn frame in the widget factory. http://i.imgur.com/JzcvonC.png I believe the problem is because for some reason after triggering a stack page transition, the stack is being drawn before its first tick callback. A gdk window is positioned wrong until that callback. Probably good for stack to always have consistent state, and have a patch for that which fixes this problem. But no idea if that ordering of draw->tick callback is expected, so opening the bug in case someone who knows more on the wayland side wants to dig in there. -- 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 766405] Stack shows incorrect frame in widget factory on wayland
https://bugzilla.gnome.org/show_bug.cgi?id=766405 --- Comment #1 from Matt Watson --- Created attachment 327845 --> https://bugzilla.gnome.org/attachment.cgi?id=327845&action=edit Fixes stack to always have consistent state. -- 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
