[Wayland-bugs] [Bug 103298] infinite loop when lid events are repeated - list item points to itself

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=103298

Peter Hutterer  changed:

   What|Removed |Added

 Status|NEEDINFO|ASSIGNED

--- Comment #9 from Peter Hutterer  ---
Ok, got it. Sequence is: close lid, press key, open lid, close lid. i.e. the
open-lid event has to come in after the keyboard event. Patch is here:

https://lists.freedesktop.org/archives/wayland-devel/2017-October/035562.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 103476] RFE: libinput: Add support for Trust TB-4200 Wireless Scroll Tablet (Aiptek based)

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=103476

Peter Hutterer  changed:

   What|Removed |Added

 Status|NEW |NEEDINFO
 CC||peter.hutte...@who-t.net

--- Comment #1 from Peter Hutterer  ---
What's the physical size of the sensor area? We need to add an 60-evdev.hwdb
entry in systemd for the resolution on the x/y axes, that's probably enough to
make it work.

-- 
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 100043] non-Wacom tablets are not supported in xf86-input-libinput

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=100043

--- Comment #17 from Martin Kolman  ---
(In reply to Peter Hutterer from comment #16)
> Martin: best to file a new bug, attach an evemu-describe of the device and
> we can fix it from there.

OK, filled bug 103476. :)

-- 
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 103476] RFE: libinput: Add support for Trust TB-4200 Wireless Scroll Tablet (Aiptek based)

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=103476

Bug ID: 103476
   Summary: RFE: libinput: Add support for Trust TB-4200 Wireless
Scroll Tablet (Aiptek based)
   Product: Wayland
   Version: unspecified
  Hardware: All
OS: Linux (All)
Status: NEW
  Severity: major
  Priority: medium
 Component: libinput
  Assignee: wayland-bugs@lists.freedesktop.org
  Reporter: martin.kol...@gmail.com

I've recently got this tablet, but it doesn't seem to work with libinput:


říj 26 01:26:19 localhost.localdomain kernel: usb 1-1.2: new low-speed USB
device number 9 using ehci-pci
říj 26 01:26:19 localhost.localdomain kernel: usb 1-1.2: New USB device found,
idVendor=08ca, idProduct=0010
říj 26 01:26:19 localhost.localdomain kernel: usb 1-1.2: New USB device
strings: Mfr=1, Product=3, SerialNumber=0
říj 26 01:26:19 localhost.localdomain kernel: usb 1-1.2: Product: USB Tablet
Series Version 1.05
říj 26 01:26:19 localhost.localdomain kernel: usb 1-1.2: Manufacturer: AIPTEK
International Inc.


But accordingly to bug 100043 support could be added via a hwdb entry &
evemu-describe output should be provided. So here it is:


$ sudo evemu-describe 
Available devices:
/dev/input/event0:  Lid Switch
/dev/input/event1:  Sleep Button
/dev/input/event2:  Power Button
/dev/input/event3:  AT Translated Set 2 keyboard
/dev/input/event4:  Logitech USB Laser Mouse
/dev/input/event5:  Logitech USB Receiver
/dev/input/event6:  Logitech USB Receiver
/dev/input/event7:  SynPS/2 Synaptics TouchPad
/dev/input/event8:  Video Bus
/dev/input/event9:  Video Bus
/dev/input/event10: TPPS/2 IBM TrackPoint
/dev/input/event11: ThinkPad Extra Buttons
/dev/input/event12: HDA Intel PCH Mic
/dev/input/event13: HDA Intel PCH Dock Mic
/dev/input/event14: HDA Intel PCH Dock Headphone
/dev/input/event15: HDA Intel PCH Headphone
/dev/input/event16: Integrated Camera: Integrated C
/dev/input/event17: Aiptek
Select the device event number [0-17]: 17  
# EVEMU 1.3
# Kernel: 4.13.5-200.fc26.x86_64
# DMI:
dmi:bvnLENOVO:bvr8AET65WW(1.45):bd05/14/2015:svnLENOVO:pn42404GG:pvrThinkPadT520:rvnLENOVO:rn42404GG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
# Input device name: "Aiptek"
# Input device ID: bus 0x03 vendor 0x8ca product 0x10 version 0x105
# Supported events:
#   Event type 0 (EV_SYN)
# Event code 0 (SYN_REPORT)
# Event code 1 (SYN_CONFIG)
# Event code 2 (SYN_MT_REPORT)
# Event code 3 (SYN_DROPPED)
# Event code 4 ((null))
# Event code 5 ((null))
# Event code 6 ((null))
# Event code 7 ((null))
# Event code 8 ((null))
# Event code 9 ((null))
# Event code 10 ((null))
# Event code 11 ((null))
# Event code 12 ((null))
# Event code 13 ((null))
# Event code 14 ((null))
# Event code 15 (SYN_MAX)
#   Event type 1 (EV_KEY)
# Event code 1 (KEY_ESC)
# Event code 59 (KEY_F1)
# Event code 60 (KEY_F2)
# Event code 61 (KEY_F3)
# Event code 62 (KEY_F4)
# Event code 63 (KEY_F5)
# Event code 64 (KEY_F6)
# Event code 65 (KEY_F7)
# Event code 66 (KEY_F8)
# Event code 67 (KEY_F9)
# Event code 68 (KEY_F10)
# Event code 87 (KEY_F11)
# Event code 88 (KEY_F12)
# Event code 128 (KEY_STOP)
# Event code 129 (KEY_AGAIN)
# Event code 130 (KEY_PROPS)
# Event code 131 (KEY_UNDO)
# Event code 132 (KEY_FRONT)
# Event code 133 (KEY_COPY)
# Event code 134 (KEY_OPEN)
# Event code 135 (KEY_PASTE)
# Event code 183 (KEY_F13)
# Event code 184 (KEY_F14)
# Event code 185 (KEY_F15)
# Event code 186 (KEY_F16)
# Event code 187 (KEY_F17)
# Event code 188 (KEY_F18)
# Event code 189 (KEY_F19)
# Event code 190 (KEY_F20)
# Event code 191 (KEY_F21)
# Event code 192 (KEY_F22)
# Event code 193 (KEY_F23)
# Event code 194 (KEY_F24)
# Event code 272 (BTN_LEFT)
# Event code 273 (BTN_RIGHT)
# Event code 274 (BTN_MIDDLE)
# Event code 320 (BTN_TOOL_PEN)
# Event code 321 (BTN_TOOL_RUBBER)
# Event code 322 (BTN_TOOL_BRUSH)
# Event code 323 (BTN_TOOL_PENCIL)
# Event code 324 (BTN_TOOL_AIRBRUSH)
# Event code 326 (BTN_TOOL_MOUSE)
# Event code 327 (BTN_TOOL_LENS)
# Event code 330 (BTN_TOUCH)
# Event code 331 (BTN_STYLUS)
# Event code 332 (BTN_STYLUS2)
#   Event type 2 (EV_REL)
# Event code 0 (REL_X)
# Event code 1 (REL_Y)
# Event code 8 (REL_WHEEL)
#   Event type 3 (EV_ABS)
# Event code 0 (ABS_X)
#   Value0
#   Min  0
#   Max   5999
#   Fuzz 0
#   Flat 0
#   Resolution   0
# Event code 1 (ABS_Y)
#   Value0
#   Min  0
#   Max   4499
#   Fuzz 0
#   Flat 0
#   Resolution   0
# Event code 8 (ABS_WHEEL)
#   Value0
#   Min

[Wayland-bugs] [Bug 98839] Somehow conditionalize hysteresis (hardware black/whitelist, device property introspection, user-exposed setting, etc)

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=98839

--- Comment #57 from Peter Hutterer  ---
doh, I thought I had pushed the !enabled fixed, done now and force-pushed so
the branch is up-to-date and ready for testing. Thanks for spotting that.
Commit is currently 1b251c2676130 but I may need to push more later.

The current event count of 5 means holding the finger stationary for ~60ms on
most touchpads. That's short enough that I can trigger it here even when trying
not to, usually it triggers before I even start moving the fingers, right after
I place it on the touchpad for the first time. That's on a T440 which is
equivalent to the X1 3rd iirc, so an older touchpad.

I recommend testing with sudo ./build/libinput-debug-events --verbose, that
prints a message when the hysteresis is disabled. If the message appears, then
hysteresis is ignored.

Nate: attachment 135028 has several non-moving event streams that last a second
or even longer. So it should definitely activate on your touchpad. I tested all
the attachments above (still and moving) and they all disable the hysteresis
within the first fraction of a second, before the first events come out of the
device.

The only case where the period may be significantly longer than 60ms would be
if the touchpad firmware filters pressure and you don't get *any* events before
the next motion event some time later. That can happen, see E 1.557756 in
Nate's attachment 135029 which is 119ms after the previous one. But that is the
exception. Needs fixing, sure, but a very niche issue.

-- 
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 103475] Tests fail, if XDG_RUNTIME_DIR is set, but directory is missing

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=103475

Bug ID: 103475
   Summary: Tests fail, if XDG_RUNTIME_DIR is set, but directory
is missing
   Product: Wayland
   Version: 1.4.0
  Hardware: Other
OS: Linux (All)
Status: NEW
  Severity: normal
  Priority: medium
 Component: wayland
  Assignee: wayland-bugs@lists.freedesktop.org
  Reporter: isacvirid...@aol.com

If XDG_RUNTIME_DIR is set (ex. "/tmp/xdg-$USER"), but the directory is not
present, most tests from "make check" fail. This happens, if one tries to build
wayland and run the tests on a freshly rebooted system. Creating the directory
manually enables the tests to complete.

-- 
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 103395] buttons on graphic tablet don't work

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=103395

--- Comment #10 from Peter Hutterer  ---
systemd bugs are here: https://github.com/systemd/systemd/issues

gnome doesn't care about the brand of the tablet, only whether it can find
enough pieces of information such as whether the tablet is internal (screen) or
external (usb). Those are provided by the data files in libwacom.

The problem with most of the cheap tablets is that they re-use the USB ids, so
two completely different tablets can look the same to the system. There's a
mirror of the data files here:
https://github.com/linuxwacom/libwacom/tree/master/data

Look at the wacom.example one, that gives you enough information to add a data
file for your tablet. Please send that as a git-formatted patch to
linuxwacom-de...@lists.sourceforge.net

-- 
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 781814] Applications don't receive clipboard when data source mimetype is "text/plain; charset=utf-8"

2017-10-26 Thread gtk+ 
https://bugzilla.gnome.org/show_bug.cgi?id=781814

Michael  changed:

   What|Removed |Added

 CC||zrax0...@gmail.com

--- Comment #5 from Michael  ---
This breaks copying from non-GTK apps in Windows as well.  From what I can
tell, the content of text/plain;charset=utf-8 is initialized with UTF8_STRING
the first time it is requested, but never updated again after that.  Thus,
pasting text from non-GTK apps on Windows will always return stale text.

-- 
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 103462] sudo ninja -C builddir/ install fails on my machine

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=103462

Peter Hutterer  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #2 from Peter Hutterer  ---
commit 8edae4feb63c34e2e4f335bb190057e2498ec8f0
Author: Peter Hutterer 
Date:   Thu Oct 26 16:45:24 2017 +1000

meson: require GTK 3.20

-- 
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 103461] build dependencies documentation doesn't work on my machine

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=103461

Peter Hutterer  changed:

   What|Removed |Added

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

--- Comment #2 from Peter Hutterer  ---
(In reply to zwhitchcox from comment #0)
> `
> Reading package lists... Done
> E: Unable to find a source package for libinput
> `

that indicates some missing apt setup/sources. What build-dep does is download
the source file of the package, look at it's build description for the .deb
package and then install the requirements listed in there. In your case, it
fails at the 'download the source' stage which indicates that one of your
repositories is either disabled or doesn't provide the source.

> Anyway, it would be nice to just have a list of dependencies, and I can just
> install them manually.

no, these have a tendency to be out of date and not in sync with the code. The
meson.build file is the authoritative source, so worst case just work through
the missing packages one-by-one.

> Right now, I'm stuck at `dot`, and I can't find that package anywhere.

at least yum/dnf can do a dnf install /usr/bin/dot and have the rest work
magically. I think apt has a similar 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 103298] infinite loop when lid events are repeated - list item points to itself

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=103298

--- Comment #8 from Alban Browaeys  ---
Created attachment 135092
  --> https://bugs.freedesktop.org/attachment.cgi?id=135092=edit
debug: trigger a core dump on list corruption

I send this hack to get a coredump / backtrace instead of busy loop to help
other debug this issue. I will investigate anew as time passed and I somehow
lost track of the in and outs of this fix.
The core of the debug 

with this debug patch I get these journald entries and the adhoc coredumpctl
backtrace.

Note that 0x5647705b6c20 is added 0x564770541940 twice in a raw.


sept. 27 02:32:55 cyclope org.gnome.Shell.desktop[14480]: LIBINPUT : device
init event listener - 0x564770541940 which has prev (nil) and next (nil)
sept. 27 02:32:55 cyclope org.gnome.Shell.desktop[14480]: LIBINPUT : device PRE
add event listener -  to 0x564770545110
sept. 27 02:32:55 cyclope org.gnome.Shell.desktop[14480]: LIBINPUT : device PRE
add event listener -  0x5647705a72e0 which has prev (nil) and next (nil)
sept. 27 02:32:55 cyclope org.gnome.Shell.desktop[14480]: LIBINPUT : device
POST add event listener -  0x5647705a72e0 which has prev 0x564770545110 and
next 0x564770545110
sept. 27 02:32:55 cyclope org.gnome.Shell.desktop[14480]: LIBINPUT : device PRE
add event listener -  to 0x5647705b6c20
sept. 27 02:32:55 cyclope org.gnome.Shell.desktop[14480]: LIBINPUT : device PRE
add event listener -  0x5647705a71a8 which has prev (nil) and next (nil)
sept. 27 02:32:55 cyclope org.gnome.Shell.desktop[14480]: LIBINPUT : device
POST add event listener -  0x5647705a71a8 which has prev 0x5647705b6c20 and
next 0x5647705b6c20
sept. 27 02:32:55 cyclope org.gnome.Shell.desktop[14480]: LIBINPUT : device PRE
add event listener -  to 0x56477059c930
sept. 27 02:32:55 cyclope org.gnome.Shell.desktop[14480]: LIBINPUT : device PRE
add event listener -  0x5647705a70f8 which has prev (nil) and next (nil)
sept. 27 02:32:55 cyclope org.gnome.Shell.desktop[14480]: LIBINPUT : device
POST add event listener -  0x5647705a70f8 which has prev 0x56477059c930 and
next 0x56477059c930
sept. 27 02:33:14 cyclope org.gnome.Shell.desktop[14480]: LIBINPUT : device PRE
add event listener -  to 0x5647705b6c20
sept. 27 02:33:14 cyclope org.gnome.Shell.desktop[14480]: LIBINPUT : device PRE
add event listener -  0x564770541940 which has prev 0x564770541940 and next
0x564770541940
sept. 27 02:33:14 cyclope org.gnome.Shell.desktop[14480]: LIBINPUT : device
POST add event listener -  0x564770541940 which has prev 0x5647705b6c20 and
next 0x5647705a71a8
sept. 27 02:33:18 cyclope org.gnome.Shell.desktop[14480]: LIBINPUT : device PRE
add event listener -  to 0x5647705b6c20
sept. 27 02:33:18 cyclope org.gnome.Shell.desktop[14480]: LIBINPUT : device PRE
add event listener -  0x564770541940 which has prev 0x5647705b6c20 and next
0x5647705a71a8
sept. 27 02:33:18 cyclope org.gnome.Shell.desktop[14480]: LIBINPUT : device
POST add event listener -  0x564770541940 which has prev 0x564770541940 and
next 0x564770541940






   PID: 14799 (gnome-shell)
   UID: 1000 (prahal)
   GID: 1000 (prahal)
Signal: 6 (ABRT)
 Timestamp: Wed 2017-09-27 02:33:18 CEST (1min 1s ago)
  Command Line: /usr/bin/gnome-shell
Executable: /usr/bin/gnome-shell
 Control Group: /user.slice/user-1000.slice/session-396.scope
  Unit: session-396.scope
 Slice: user-1000.slice
   Session: 396
 Owner UID: 1000 (prahal)
   Boot ID: c29df59057834e2bb77ae569ae135cfb
Machine ID: 2b483dcbcecb6729df407c5b5382b0d1
  Hostname: cyclope
   Storage:
/var/lib/systemd/coredump/core.gnome-shell.1000.c29df59057834e2bb77ae569ae135cfb.14799.150647239800.lz4
   Message: Process 14799 (gnome-shell) of user 1000 dumped core.

Stack trace of thread 14799:
#0  0x7fd6b1220fff __GI_raise (libc.so.6)
#1  0x7fd6b122242a __GI_abort (libc.so.6)
#2  0x7fd6a859cea4 create_dump (libinput.so.10)
#3  0x7fd6a85a626b lid_switch_process_switch
(libinput.so.10)
#4  0x7fd6a85a10a9 evdev_process_event (libinput.so.10)
#5  0x7fd6a859cd2f libinput_dispatch (libinput.so.10)
#6  0x7fd6b22feeac dispatch_libinput
(libmutter-clutter-1.0.so)
#7  0x7fd6b17f2f67 g_main_dispatch (libglib-2.0.so.0)
#8  0x7fd6b17f31a0 g_main_context_iterate
(libglib-2.0.so.0)
#9  0x7fd6b17f34b2 g_main_loop_run (libglib-2.0.so.0)
#10 0x7fd6b2fa6a8c meta_run (libmutter.so.0)
#11 0x56476f0224b7 main (gnome-shell)
#12 0x7fd6b120e2e1 __libc_start_main (libc.so.6)
#13 0x56476f0225fa _start (gnome-shell)

Thread 1 (Thread 0x7fd6b47a9a80 (LWP 14799)):
#0  0x7fd6b1220fff in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:51
#1  0x7fd6b122242a in

[Wayland-bugs] [Bug 781909] Implement KDE's server-decoration protocol

2017-10-26 Thread gtk+ 
https://bugzilla.gnome.org/show_bug.cgi?id=781909

Matthias Clasen  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
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 103298] infinite loop when lid events are repeated - list item points to itself

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=103298

--- Comment #7 from Alban Browaeys  ---
Sorry taking me a while to sort out how to setup a test/dev environment in a
VM.
About the crash I think it is not directly related to this issue. The current
issue might prevent an user to reach the crash in gnome-shell.

In the crash I get gnome-shell hangs (100%cpu , libinput is in a busy
processing LID event list). But no crash. With the fix I get a crash at random
times but pretty much nailed down : shell_gtk_embed_window_created_cb is called
with its embed argument freed and dereference it. Sadly I cannot seem to sort
out how to reproduce (even though it kills my session every 2 days). I see that
with coredumpctl and gdb.

But I believe the current issue is higher priority. When libinput loop I cannot
even switch to a VT to kill it. Only way out is to ssh to the box and mess with
gdb.

-- 
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 777072] window shrinks when restored from maximized

2017-10-26 Thread gtk+ 
https://bugzilla.gnome.org/show_bug.cgi?id=777072

Matthias Clasen  changed:

   What|Removed |Added

 Attachment #354151|none|committed
 status||

-- 
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 777072] window shrinks when restored from maximized

2017-10-26 Thread gtk+ 
https://bugzilla.gnome.org/show_bug.cgi?id=777072

Matthias Clasen  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||mcla...@redhat.com
 Resolution|--- |FIXED

-- 
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 103395] buttons on graphic tablet don't work

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=103395

--- Comment #9 from akktor  ---
Thanks, it works.
I cant find systemd bug list. There is no choice on enter new bug.
It's actually xp-pen star 03. I don't understand what should i report to
libwacom? Is non-wacom tablet is supported on gnome-center?

-- 
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 103395] buttons on graphic tablet don't work

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=103395

--- Comment #8 from akktor  ---
Created attachment 135085
  --> https://bugs.freedesktop.org/attachment.cgi?id=135085=edit
spec

-- 
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 103298] infinite loop when lid events are repeated - list item points to itself

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=103298

--- Comment #6 from Michael Thayer  ---
Note that the more applications (windows) running, the easier it is to trigger
this.

-- 
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 99268] With Clickfinger behavior, pointer movement briefly turns into a scroll when a thumb is dropped onto the pad

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=99268

--- Comment #6 from Nate Graham  ---
Yup, I can confirm that this is fixed now. 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 99703] Trackpad accidental two-finger touch stops cursor movement too early

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=99703

--- Comment #9 from Nate Graham  ---
This change fixes the issue 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 98802] RFE: libinput should let a thumb used for clicking rest anywhere on the pad, not just on the bottom edge

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=98802

--- Comment #4 from Nate Graham  ---
Created attachment 135060
  --> https://bugs.freedesktop.org/attachment.cgi?id=135060=edit
Thumb clicking while finger moves the pointer

-- 
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 98839] Somehow conditionalize hysteresis (hardware black/whitelist, device property introspection, user-exposed setting, etc)

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=98839

Nate Graham  changed:

   What|Removed |Added

 Status|NEEDINFO|NEW

--- Comment #56 from Nate Graham  ---
I tried out that branch on my hardware (after applying Daniel's fix) but it
didn't make any difference for me, even after holding a finger stationary for
30 seconds to try to get it to learn.

Maybe my hardware does less filtering than Daniel's. Still, it's a
night-and-day difference without hysteresis, and I don't see any jumpiness at
all when it's off.

-- 
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 789141] Segmentation fault when adding Google online account

2017-10-26 Thread gtk+ 
https://bugzilla.gnome.org/show_bug.cgi?id=789141

Matthias Clasen  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||mcla...@redhat.com
 Resolution|--- |FIXED

-- 
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 98839] Somehow conditionalize hysteresis (hardware black/whitelist, device property introspection, user-exposed setting, etc)

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=98839

--- Comment #55 from Daniel van Vugt  ---
After I fixed the typo, the fix was good but not perfect. On both X1 Carbon gen
4 and 5.

The system doesn't see long enough periods of a stationary finger in reality to
learn to disable hysteresis soon enough. But if I held my finger still for a
short while it would switch over properly.

While I like your thinking with that heuristic, and it should probably stay, I
still think some defaults (of off) need to be hardcoded for the problematic
touchpad models.

-- 
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 98839] Somehow conditionalize hysteresis (hardware black/whitelist, device property introspection, user-exposed setting, etc)

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=98839

--- Comment #54 from Daniel van Vugt  ---
Typo:

+   if (!tp->hysteresis.enabled)
+   tp_maybe_disable_hysteresis(tp);

should be:

+   if (tp->hysteresis.enabled)
+   tp_maybe_disable_hysteresis(tp);

-- 
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 98839] Somehow conditionalize hysteresis (hardware black/whitelist, device property introspection, user-exposed setting, etc)

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=98839

--- Comment #53 from Daniel van Vugt  ---
I like the ideas I'm seeing in your git branch.

Unfortunately that branch made zero improvement on either X1 Carbon gen 4 or 5.

-- 
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 103298] infinite loop when lid events are repeated - list item points to itself

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=103298

--- Comment #4 from Michael Thayer  ---
I was able to trigger the crash pretty easily with the old library still in use
by opening and closing the lid a few times in quick succession and then trying
to type an update to this bug.  After restarting I was not immediately able to
trigger it, but instead brought gnome-shell down with an assertion (g_malloc
failed to allocate 1.8x10^19 bytes).  Working down the stack a few frames it
looked like it was trying to use an invalid structure, presumably in memory
which had already been freed.  Which at least raises the possibility that
gnome-shell has some memory use bug which triggers on suspend and resume and
that libinput was collateral damage.

-- 
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 103208] One-finger movement on touchpad registered as two-finger scrolling with edge exclusion zone is touched

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=103208

--- Comment #15 from Peter Y. Chuang  ---
Couple of things:

1) Just because I express my dislike of a feature doesn't mean I belittle it,
or believe that no one ever uses it, or believe it's worthless. In fact, I
believe I have made myself quite clear that I am fine with keeping the feature
as long as we remedy the problem it causes. My key point is that I don't see
any obvious logic that can accommodate absolutely *everything*, so the question
will, at some point, become which feature you would rather sacrifice (see point
no. 4).

2) I also want to make clear that I dislike the feature not just as a user of
MacBook, which has arguably the best touchpad around, but as a user of other
touchpads as well, such as the one on XPS 13, and some older touchpads on some
$300 laptops from like 5 years ago. So I am not proposing these things just
because I think MacBook does them, but because I've used multiple touchpads and
haven't found the offending feature useful when it isn't causing problems. But
if other users find that feature useful, that's fine.

3) Of course I don't expect the feature to go away just because I don't like
it. I have used Linux for long enough to know that things don't work like this
here (or anywhere). 

4) If not everything can be accommodated, there will come a point in the future
where one will have to choose one over another. As touchpads improve, it will
be the old features that will have to go if they get in the way of
accommodating new features, IMHO. That's not avoidable in the long-run.

5) Now, it's not like I haven't thought about how to fix this *without* gutting
the feature. Here are **two other potential ways** I've come up since the last
comment:

A) ABS_MT_ORIENTATION of palm touches on the left edge should always be
positive, and those on the right should always be negative because of how the
hands are normally placed, no matter how large the contact areas are.
Incorporating orientation data may provide an extra check to identify real
palms within the edge zones, or perhaps even help do away from edge exclusion
zone altogether. Orientations of fingers tend to fluctuate around the edges in
my observation, but since users don't often use the edges for tracking, finger
detection at the edges does not have to be 100% perfect IMHO. Granted, this
will probably make two-finger scrolling (and
one-finger-moving-one-finger-stationary-scrolling) around the edges less
consistent than in the middle of the touchpad. We can test and debate whether
this decrease in consistency is worth it.

B) Call the one-finger-moving-one-finger-stationary-scrolling something else
altogether, because it's not *really* two-finger scrolling. For now, let's call
it Legacy Mode. Then create a new two-finger scrolling (or Experimental Mode
for now) with new checks, so that end users can actually *test* and help refine
the extra checks, and, if they don't like them, revert back to the Legacy Mode.

-- 
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 103298] infinite loop when lid events are repeated - list item points to itself

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=103298

--- Comment #3 from Michael Thayer  ---
I think I am seeing the same thing with Ubuntu 17.10, libinput 1.8.2-2.  The
patch applies cleanly, I will see if it helps.

-- 
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 103462] sudo ninja -C builddir/ install fails on my machine

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=103462

Peter Hutterer  changed:

   What|Removed |Added

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

--- Comment #1 from Peter Hutterer  ---
workaround: run meson configure -Ddebug-gui=false , then run ninja
again, that'll disable the debug gui that requires gtk. I'll push out a fix to
check for the right gtk version as soon as the test suite run finishes.

-- 
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 103208] One-finger movement on touchpad registered as two-finger scrolling with edge exclusion zone is touched

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=103208

--- Comment #14 from Peter Hutterer  ---
ok, let's be clear here: comments like that are not productive. Don't belittle
the features others require/expect just because they don't match your
expectations or usage patterns. And don't assume that we're changing them just
because your usage pattern doesn't match the current implementation. Think
about how to *fix* this rather than belittling everything that you don't like.

-- 
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 103462] sudo ninja -C builddir/ install fails on my machine

2017-10-26 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=103462

Bug ID: 103462
   Summary: sudo ninja -C builddir/ install fails on my machine
   Product: Wayland
   Version: unspecified
  Hardware: Other
OS: All
Status: NEW
  Severity: normal
  Priority: medium
 Component: libinput
  Assignee: wayland-bugs@lists.freedesktop.org
  Reporter: zwhitch...@gmail.com

I get this error

../tools/libinput-debug-gui.c:405:9: error: ‘GDK_SEAT_CAPABILITY_ALL_POINTING’
undeclared (first use in this function)
 GDK_SEAT_CAPABILITY_ALL_POINTING,

Don't know what it means.

I'm on GalliumOS 2.1, a Chromebook, Samus

Sorry I can't really provide anything more than that.

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