[Wayland-bugs] [Bug 771320] [Wayland] Maps widget is displayed at wrong position inside gnome-contacts

[gtk+]

https://bugzilla.gnome.org/show_bug.cgi?id=771320

Jonas Ådahl  changed:

   What|Removed |Added

 Attachment #337315|none|reviewed
 status||

--- Comment #11 from Jonas Ådahl  ---
Review of attachment 337315:

::: gdk/gdkwindow.c
@@ +5989,3 @@
+
+  display = gdk_window_get_display (window);
+  gdk_display_put_event (display, event);

Can be just "gdk_event_put (event);" since you do pretty much what that
function does here.

@@ +6013,3 @@
+{
+  configure_native_child (child);
+  move_native_children  (child);

Can fix the coding style issue (double space) while at it.

@@ +6102,3 @@
window->width, window->height);
 }
+  else

How come this is needed? Shouldn't we still skip moving if the absolute
position didn't change?

-- 
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 771841] [Wayland] Drop-down menus are broken in position and size on HiDPI screens

[gtk+]

https://bugzilla.gnome.org/show_bug.cgi?id=771841

--- Comment #30 from Daniel Buch  ---
Eventually the program will crash with this:

(gnome-calculator:9872): Gtk-WARNING **: Negative content width -7 (allocation
1, extents 4x4) while allocating gadget (node arrow, owner GtkTreeMenu)

(gnome-calculator:9872): Gdk-WARNING **: Error 71 (Protocol error) dispatching
to Wayland display.

-- 
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 771841] [Wayland] Drop-down menus are broken in position and size on HiDPI screens

[gtk+]

https://bugzilla.gnome.org/show_bug.cgi?id=771841

--- Comment #29 from Daniel Buch  ---
This behavior persist even though i patch these mutter patches.
As a last comment, i discovered that the shrinking problem, is widget
instance-wise. So clicking one button and the popup shrink to half the size
exponentially for each click.

>From my understanding, i believe this logic is now in gdk, not gtk and not
mutter - is that correct?

-- 
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 771841] [Wayland] Drop-down menus are broken in position and size on HiDPI screens

[gtk+]

https://bugzilla.gnome.org/show_bug.cgi?id=771841

--- Comment #28 from Daniel Buch  ---
Created attachment 337455
  --> https://bugzilla.gnome.org/attachment.cgi?id=337455=edit
Popup positioning

This shows that popup position (x,y) is _NOT_ multiplied by scaling factor.
Look at cursor and popup

-- 
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 771841] [Wayland] Drop-down menus are broken in position and size on HiDPI screens

[gtk+]

https://bugzilla.gnome.org/show_bug.cgi?id=771841

--- Comment #27 from Daniel Buch  ---
Created attachment 337454
  --> https://bugzilla.gnome.org/attachment.cgi?id=337454=edit
GtkMenu-Click-2

-- 
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 771841] [Wayland] Drop-down menus are broken in position and size on HiDPI screens

[gtk+]

https://bugzilla.gnome.org/show_bug.cgi?id=771841

--- Comment #26 from Daniel Buch  ---
Created attachment 337453
  --> https://bugzilla.gnome.org/attachment.cgi?id=337453=edit
GtkMenu-Click-1

This is when i click once, next will be shrink further by factor two. Next
attachment will show that

-- 
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 771841] [Wayland] Drop-down menus are broken in position and size on HiDPI screens

[gtk+]

https://bugzilla.gnome.org/show_bug.cgi?id=771841

--- Comment #25 from Daniel Buch  ---
Created attachment 337452
  --> https://bugzilla.gnome.org/attachment.cgi?id=337452=edit
Daniel setup info

-- 
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 771915] [Wayland]: Totem window misplaced after a state change

[gtk+]

https://bugzilla.gnome.org/show_bug.cgi?id=771915

kritph...@mongkhonvanit.tk changed:

   What|Removed |Added

 CC||kritph...@mongkhonvanit.tk

--- Comment #18 from kritph...@mongkhonvanit.tk ---
*** Bug 772664 has been marked as a duplicate of this bug. ***

-- 
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 98201] Cannot drag with hardware middle button of a touchpad

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=98201

Jehan  changed:

   What|Removed |Added

Summary|Cannot drag with middle |Cannot drag with hardware
   |button of a touchpad|middle button of a 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 98201] Cannot drag with middle button of a touchpad

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=98201

Jehan  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|NOTABUG |---

--- Comment #3 from Jehan  ---
> the cause here is that in order to trigger a middle click, you have to have 
> your finger in the middle button area (the same goes for the right button, 
> but a left click may be triggered from outside the area due to the hardware).
>
> libinput swallows any motion from a finger "pinned" to the software button 
> area.

I am not clicking the "software button area" and trying to move this finger. On
Thinkpad X220, I have physical left, right and middle buttons.
See this image:
http://www.storagereview.com/images/Lenovo-ThinkPad-X220-TouchPad.jpg
So what I am doing is clicking this separate hardware button, and simply moving
a finger on the touchpad.

> libinput swallows any motion from a finger "pinned" to the software button 
> area. that's a feature, but in this case it's a bug - there is no good 
> solution here. libinput supports two fingers though, so you can click with 
> one finger and then put another finger down to move. tricky on a x220 with 
> it's small touchpad, but I don't think I'll change the behaviour, the 
> side-effects are just too big.

Funny thing is that this works on my X220 when using the software button area.
I didn't even know of the existence of this area (since it is much more
practical to use physical buttons).

Anyway reopening the bug report since it is about the hardware physical buttons
which don't work with libinput, and not the software button area.
Since they are separate hardware, I don't think there are any side effects
here.

-- 
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 98130] Trackpoint release event lost while moving

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=98130

Joachim Breitner  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|NEW |RESOLVED

--- Comment #4 from Joachim Breitner  ---
Thanks, glad to hear it is known and worked on. Is there an kernel(?) bug
report I should monitor?

-- 
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 97912] Feature Request: Support for Firmware Version Detection.

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=97912

Peter Hutterer  changed:

   What|Removed |Added

 CC||benjamin.tissoi...@gmail.co
   ||m, peter.hutte...@who-t.net

--- Comment #1 from Peter Hutterer  ---
This is something that needs to be discussed on the kernel side, but either way
it's going to be... tricky. The FW version is afaict a free-form string, so
we'd still need a lot of guesswork in libinput either way.

The simple approach would be another ioctl like e.g. EVIOCGUNIQ but I'm not
sure "the firmware" is precise enough since we still need to sometimes match on
DMI as well.

-- 
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 98130] Trackpoint release event lost while moving

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=98130

--- Comment #3 from Benjamin Tissoires  ---
(In reply to Joachim Breitner from comment #1)
> (If this is observable in the evemu log, does this mean that this is *not* a
> libinput bug?)

Yes, the evemu outputs what available from the kernel, so if the events are not
coming through here, it means libinput can't do much (especially for button
press/release).

Anyway, this is unfortunately a known bug. It is a firmware issue with the PS/2
firmware of the Synaptics touchpads. You might notice that this happens if your
palm rests on the touchpad sensor (with at least 2 touches).

We have a working solution that still needs to be merged.  Using RMI4 (custom
Synaptics protocol) over SMBus for these laptops solves the bug. Until then,
there is not much we can do, besides telling you not to touch the touchpad
while pressing the buttons (yeah, this sucks).

-- 
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 98009] missing CAP_POINTER on "Mad Catz Wired Xbox 360 Controller"

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=98009

Peter Hutterer  changed:

   What|Removed |Added

 CC||peter.hutte...@who-t.net

--- Comment #1 from Peter Hutterer  ---
hmm, that one shouldn't even be added by libinput. please attach the output
from sudo evemu-record against that device so I can reproduce it here, 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 98201] Cannot drag with middle button of a touchpad

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=98201

Peter Hutterer  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||peter.hutte...@who-t.net
 Resolution|--- |NOTABUG

--- Comment #2 from Peter Hutterer  ---
the cause here is that in order to trigger a middle click, you have to have
your finger in the middle button area (the same goes for the right button, but
a left click may be triggered from outside the area due to the hardware).

libinput swallows any motion from a finger "pinned" to the software button
area. that's a feature, but in this case it's a bug - there is no good solution
here. libinput supports two fingers though, so you can click with one finger
and then put another finger down to move. tricky on a x220 with it's small
touchpad, but I don't think I'll change the behaviour, the side-effects are
just too big.

alternatively, you can switch to clickfinger where you can press with three
fingers to trigger the middle button press, then release two while keeping one
finger down to then move the pointer. the middle button will be released
whenever the last finger is released

-- 
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 98194] [wishlist] API to use keyboard-specific XkbOptions

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=98194

Peter Hutterer  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||peter.hutte...@who-t.net
 Resolution|--- |WONTFIX

--- Comment #2 from Peter Hutterer  ---
see Pekka's answer, libinput sits below xkb and merely forwards the keycodes,
independent of any layout that may be applied later. The layout configuration
is the task of the compositor, not something we do/can/want to control from
within libinput

-- 
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 771841] [Wayland] Drop-down menus are broken in position and size on HiDPI screens

[gtk+]

https://bugzilla.gnome.org/show_bug.cgi?id=771841

--- Comment #24 from Sjoerd Simons  ---
Daniel can you indicate how exactly you rpreoduce the issue and what your setup
is, there might be some subtilities that these patches haven't covere ofcourse.

-- 
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