https://bugzilla.gnome.org/show_bug.cgi?id=780820
Jonas Ådahl changed:
What|Removed |Added
Attachment #351962|none|reviewed
https://bugs.freedesktop.org/show_bug.cgi?id=104303
Peter Hutterer changed:
What|Removed |Added
Status|NEEDINFO|RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=100752
Peter Hutterer changed:
What|Removed |Added
Blocks||98535
https://bugs.freedesktop.org/show_bug.cgi?id=98535
Peter Hutterer changed:
What|Removed |Added
Depends on||100752
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #15 from Peter Hutterer ---
fwiw, I went through the touchpad acceleration code again and could not find
anything obviously wrong. An important definition: a 'normalized' coordinate is
one that's converted
https://bugzilla.gnome.org/show_bug.cgi?id=783901
Jonas Ådahl changed:
What|Removed |Added
Attachment #354146|none|reviewed
https://bugzilla.gnome.org/show_bug.cgi?id=783901
Jonas Ådahl changed:
What|Removed |Added
Attachment #354148|none|reviewed
https://bugzilla.gnome.org/show_bug.cgi?id=783901
Jonas Ådahl changed:
What|Removed |Added
Attachment #354147|none|accepted-commit_now
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #16 from Greg Reichow ---
Peter-
Thanks for your response. Agree that it does not look like there are any bugs
that are causing this behavior. It may just come down to preference. On your
earlier response, I
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #17 from Greg Reichow ---
Created attachment 136627
--> https://bugs.freedesktop.org/attachment.cgi?id=136627=edit
Accel profiles from lowclip.patch
Per comment above
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=104533
--- Comment #1 from Benjamin Tissoires ---
I think 352ce2b0575f195c8e6452a9 is right, as we really do not want the events
to be applied twice the fuzz.
The bug is more likely in synaptics.c for semi-mt devices.
https://bugs.freedesktop.org/show_bug.cgi?id=84817
--- Comment #14 from Paranoik ---
(In reply to Daniel Stone from comment #13)
> All these things are true of Wayland, and have been since day one.
> ...
> if you want the socket
> to be more widely accessible, then you can
https://bugs.freedesktop.org/show_bug.cgi?id=84817
Daniel Stone changed:
What|Removed |Added
Resolution|FIXED |NOTABUG
---
https://bugs.freedesktop.org/show_bug.cgi?id=84817
--- Comment #17 from Paranoik ---
(In reply to Daniel Stone from comment #16)
Under banned I mean banned by default. By default root and other users can't
access active wayland desktop.
Ok. I've added my restricted users to
https://bugs.freedesktop.org/show_bug.cgi?id=104533
Peter Hutterer changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=99212
Peter Hutterer changed:
What|Removed |Added
Status|NEEDINFO|RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=84817
--- Comment #11 from Daniel Stone ---
(In reply to Paranoik from comment #10)
> What is the problem to let everyone access the desktop by default? Why is it
> blocked? What is this wayland sudo talk is all about? The modern
https://bugs.freedesktop.org/show_bug.cgi?id=84817
--- Comment #12 from Paranoik ---
(In reply to Daniel Stone from comment #11)
> As you say, building in MAC would make the protocol completely different and
> require everyone to be aware. It would need either SELinux-style
https://bugs.freedesktop.org/show_bug.cgi?id=84817
--- Comment #13 from Daniel Stone ---
(In reply to Paranoik from comment #12)
> The only thing
> needed to rethink were: keyboard and mouse events should only be passed to
> active window, clipboard content should only be
19 matches
Mail list logo