[Wayland-bugs] [Bug 91369] Libinput 0.19 and 0.20 ignore POINTINGSTICK_CONST_ACCEL

2017-05-24 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=91369

--- Comment #56 from Charles Plessy  ---
(In reply to Peter Hutterer from comment #53)
> anyone?

Thanks a lot for the instructions on how to test your new code.  I compiled and
ran analyze-trackpoint, and got ranges around 25 or 30.

For testing how to configure trackpoint speed from the GNOME preferences menu,
I am more in difficulty.  I am using the computer at work and I have plenty of
windows open, which makes it difficult to find the right moment to restart the
X session.  I am also unfamiliar on how to install and uninstall C libraries
cleanly (I fully rely on Debian packages for 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 101179] Touchpad clicking disables cursor movement, breaks click and drag

2017-05-24 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101179

--- Comment #1 from Britt Yazel  ---
Yep it seems to be specific with Kernel 4.11.x, as rolling back to 4.10.11
fixes this 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 101179] Touchpad clicking disables cursor movement, breaks click and drag

2017-05-24 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101179

Bug ID: 101179
   Summary: Touchpad clicking disables cursor movement, breaks
click and drag
   Product: Wayland
   Version: unspecified
  Hardware: Other
OS: All
Status: NEW
  Severity: critical
  Priority: medium
 Component: libinput
  Assignee: wayland-bugs@lists.freedesktop.org
  Reporter: bwya...@gmail.com

My trackpad seems to be acting up today on Archlinux after updating to Linux
4.11 (though I'm not sure if that is just a coincidence or not). My touchpad on
my Dell xps 13 used to feel great, and I could click and drag without any
issues. However, since booting the first time after updating, any time I left
or right click, it seems to disable touchpad input and the cursor will not
respond anymore. This completely breaks clicking and dragging, and is overall
very annoying

-- 
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 101140] Expose an acceleration setting

2017-05-24 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101140

--- Comment #4 from Peter Hutterer  ---
Not sure where you get the thinkpad part from. They get the most testing
because I have access to them, if I have no access to others *and* I get little
contribution from others it's hard to improve them. My point was that
apparently Apple gets something that's good enough for their hardware, there's
no real reason we can't do the same given that we know about the different
hardware in libinput and can adjust it as needed (we already have a special
acceleration for the x230 for example).

mouse acceleration has a speed setting and a profile that merely forwards the
input as-is. That's not usable on touchpads, so we don't export it. If someone
comes up with a new acceleration profile that works better for touchpads we can
talk about it, but chances are it'll be better for all touchpads, so we can
just change the current one to this new code.

-- 
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 101140] Expose an acceleration setting

2017-05-24 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101140

Nate Graham  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WONTFIX |---

--- Comment #3 from Nate Graham  ---
"Ehh, good enough for me" doesn't strike me as the best response for a project
that aims for 100% adoption across all Linux hardware. We don't all use
Thinkpads.

I understand how exposing a specific setting limits your ability to change the
algorithm the future. But libinput's mouse module exposes a set of different
acceleration profiles, rather than a slider value or something. What's wrong
with doing the same type of thing for touchpads?

-- 
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 98535] libinput touchpad acceleration tracker bug

2017-05-24 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=98535
Bug 98535 depends on bug 101140, which changed state.

Bug 101140 Summary: Expose an acceleration setting
https://bugs.freedesktop.org/show_bug.cgi?id=101140

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WONTFIX |---

-- 
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 91369] Libinput 0.19 and 0.20 ignore POINTINGSTICK_CONST_ACCEL

2017-05-24 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=91369

--- Comment #55 from alexey polusov  ---
Hello guys. I have Dell Latitude 5470 running ubuntu 16.04.
And I have the exact same problem:

I am unable to achieve acceptable results with all the different knobs that are
available. If I tune down acceleration, I am able to do detailed pointing, but
the stick is generally so slow, that it takes ages to cross the screen. On the
other hand, if I increase the acceleration, even the slightest movement of the
stick makes it jump significantly on the screen so that I am unable to do
detailed selections.

Is this bug relative to my issue? Is there any way to fix it right 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 782694] Copy and paste when on wayland not working well

2017-05-24 Thread gtk+
https://bugzilla.gnome.org/show_bug.cgi?id=782694

--- Comment #16 from Pavlo Rudyi  ---
Sometimes I must use the copy twice in Firefox. That's all about it.

-- 
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 783047] Many apps crash in gdk_event_source_prepare when logging out of GNOME

2017-05-24 Thread gtk+
https://bugzilla.gnome.org/show_bug.cgi?id=783047

Matthias Clasen  changed:

   What|Removed |Added

 Attachment #352502|none|accepted-commit_now
 status||

--- Comment #5 from Matthias Clasen  ---
Review of attachment 352502:

makes sense. please put it on gtk-3-22 and master

-- 
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 745289] wayland: do not use g_error() on connection errors

2017-05-24 Thread gtk+
https://bugzilla.gnome.org/show_bug.cgi?id=745289

Debarshi Ray  changed:

   What|Removed |Added

 Attachment #298098|none|committed
 status||

--- Comment #3 from Debarshi Ray  ---
Review of attachment 298098:

Looks similar to:
https://bugzilla.redhat.com/show_bug.cgi?id=1366897
https://bugzilla.gnome.org/show_bug.cgi?id=783047

(updating the patch's status to reflect reality)

::: gdk/wayland/gdkeventsource.c
@@ +164,3 @@
+{
+  g_warning ("Error %d (%s) dispatching to Wayland display.",
+ errno, g_strerror (errno));

Maybe we should use g_message instead?

See https://bugzilla.redhat.com/show_bug.cgi?id=1366897#c43 for a rationale.
The X11 backend (gdk_x_io_error) also uses g_message these days.

@@ +165,3 @@
+  g_warning ("Error %d (%s) dispatching to Wayland display.",
+ errno, g_strerror (errno));
+  exit (1);

Also, maybe, _exit instead?

-- 
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 783047] Many apps crash in gdk_event_source_prepare when logging out of GNOME

2017-05-24 Thread gtk+
https://bugzilla.gnome.org/show_bug.cgi?id=783047

Olivier Fourdan  changed:

   What|Removed |Added

 CC||ofour...@redhat.com

--- Comment #4 from Olivier Fourdan  ---
(In reply to Olivier Fourdan from comment #3)
> You have indentation issues in the patch (the { }), other than that, I think
> it makes sense.

Ah no, sorry, my bad, indentation is fine!

-- 
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 783047] Many apps crash in gdk_event_source_prepare when logging out of GNOME

2017-05-24 Thread gtk+
https://bugzilla.gnome.org/show_bug.cgi?id=783047

--- Comment #3 from Olivier Fourdan  ---
You have indentation issues in the patch (the { }), other than that, I think it
makes sense.

-- 
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 783047] Many apps crash in gdk_event_source_prepare when logging out of GNOME

2017-05-24 Thread gtk+
https://bugzilla.gnome.org/show_bug.cgi?id=783047

--- Comment #2 from Debarshi Ray  ---
Bug 745289 was another related issue fixed by:
https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=53028ff3bb0610f5fb4df360391af9ee23f61cfa

-- 
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 783047] Many apps crash in gdk_event_source_prepare when logging out of GNOME

2017-05-24 Thread gtk+
https://bugzilla.gnome.org/show_bug.cgi?id=783047

--- Comment #1 from Debarshi Ray  ---
Created attachment 352502
  --> https://bugzilla.gnome.org/attachment.cgi?id=352502=edit
wayland: Don't abort when preparing the source if connection is lost

-- 
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 783047] New: Many apps crash in gdk_event_source_prepare when logging out of GNOME

2017-05-24 Thread gtk+
https://bugzilla.gnome.org/show_bug.cgi?id=783047

Bug ID: 783047
   Summary: Many apps crash in gdk_event_source_prepare when
logging out of GNOME
Classification: Platform
   Product: gtk+
   Version: 3.22.x
OS: Linux
Status: NEW
  Severity: normal
  Priority: Normal
 Component: Backend: Wayland
  Assignee: gtk-b...@gtk.org
  Reporter: rishi...@lostca.se
QA Contact: gtk-b...@gtk.org
CC: r...@robster.org.uk, wayland-bugs@lists.freedesktop.org
 GNOME version: ---

See this Fedora bug for the backtraces:
https://bugzilla.redhat.com/show_bug.cgi?id=1258818

It looks very similar to this older Fedora bug, except that it one is about
gdk_event_source_check and the other gdk_event_source_prepare:
https://bugzilla.redhat.com/show_bug.cgi?id=1366897

It was fixed by:
https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=43b2b107f123a97e2040ddb7f429b611a16bdc41

I don't know if this is also triggered by logging out of GNOME, but it looks
plausible, so I am running with it.

-- 
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 91369] Libinput 0.19 and 0.20 ignore POINTINGSTICK_CONST_ACCEL

2017-05-24 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=91369

--- Comment #54 from Kai-Heng Feng  ---
Sorry for the late reply.

Subjectively, I think 50 is quite good.
But trackpoint scrolling is way too fast. Do I miss some additional settings?

-- 
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 782694] Copy and paste when on wayland not working well

2017-05-24 Thread gtk+
https://bugzilla.gnome.org/show_bug.cgi?id=782694

--- Comment #15 from Daniel Rowe  ---
So after a few more days using it not totally fixed. It is better, it not
broken all the time.

But its still does not work all the time.

-- 
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 101162] Chromium videos are lagging once the cursor is hidden

2017-05-24 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101162

Bug ID: 101162
   Summary: Chromium videos are lagging once the cursor is hidden
   Product: Wayland
   Version: unspecified
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
  Severity: normal
  Priority: medium
 Component: weston
  Assignee: wayland-bugs@lists.freedesktop.org
  Reporter: iliy...@hotmail.com

To reproduce the issue(at least on my machine this is the behavior, I'm using
weston 2.0.0):
Open chromium/chrome, load a youtube video, leave the pointer above it, after a
few seconds it will "hide". At this moment the FPS of the video drops
considerably(or probably this is the compositor's FPS) and the video lags. When
I move the cursor again so it becomes visible the problem goes away until it
gets hidden again. This doesn't happen with fullscreen video, maybe the black
surfaces that weston uses or something similar is the reason behind this, as on
my WM it happens with fullscreen windows and I don't use black surfaces.

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