Hi Workstation WG,
as the F28 Final release is quickly approaching, it would be nice if the WG would start working on a Fedora Magazine article "What's New in F28 Workstation". The article should be finished prior Readiness meeting for F28 Final, planned on 2018-Apr-26.
Regards, Jan
I've simultaneously pitched a "What's new in GNOME 3.28" article to the magazine. These two articles could easily become one. Is there anyone from this team willing to co-author with me?
On Wed, 2018-04-18 at 09:11 +0200, Jan Kurik wrote:
Hi Workstation WG,
as the F28 Final release is quickly approaching, it would be nice if the WG would start working on a Fedora Magazine article "What's New in F28 Workstation". The article should be finished prior Readiness meeting for F28 Final, planned on 2018-Apr-26.
Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic _______________________________________________ desktop mailing list -- desktop@lists.fedoraproject.org To unsubscribe send an email to desktop-leave@lists.fedoraproject.org
Hi,
I've begun drafting this. I have some questions about F28 that I'm hoping some folks on this list can provide more details on.
Are there any new or interesting changes to:
* pipewire * wayland * libva * freetype * OPTIMUS/hybrid GPU support
Can anyone point me to[1] or verify what changes to power management have been accepted? I know there was a lot of back and forth over auto- suspend that eventually got deferred. Have any other changes to improve power management been *accepted* into F28?
I know upstream did a lot of work with Thunderbolt device security. I don't have hardware to experiment with any of that. Can someone provide me[1] a summary of those new features?
Last call for anything else people want to see added to the "What's New in Fedora 28 Workstation" article!
~link
1: A pagure.io ticket or bug is sufficient. I can dig out the details.
On Wed, 2018-04-18 at 20:21 -0700, Link Dupont wrote:
I've simultaneously pitched a "What's new in GNOME 3.28" article to the magazine. These two articles could easily become one. Is there anyone from this team willing to co-author with me?
On Wed, 2018-04-18 at 09:11 +0200, Jan Kurik wrote:
Hi Workstation WG,
as the F28 Final release is quickly approaching, it would be nice if the WG would start working on a Fedora Magazine article "What's New in F28 Workstation". The article should be finished prior Readiness meeting for F28 Final, planned on 2018-Apr-26.
Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic _______________________________________________ desktop mailing list -- desktop@lists.fedoraproject.org To unsubscribe send an email to desktop-leave@lists.fedoraproject.o rg
desktop mailing list -- desktop@lists.fedoraproject.org To unsubscribe send an email to desktop-leave@lists.fedoraproject.org
On Sat, 2018-04-21 at 10:09 -0700, Link Dupont wrote:
Hi,
I've begun drafting this. I have some questions about F28 that I'm hoping some folks on this list can provide more details on.
*snip*
Here is one thing that *VERY BADLY NEEDS EXPLAINING*:
https://bugzilla.gnome.org/show_bug.cgi?id=757255 https://help.gnome.org/misc/release-notes/3.28/
I just upgraded my laptop to F28 and had no damn idea what had happened to right click. Apparently it had changed to how Macs do it because obviously Linux users expect everything to work like it does on a Mac. (What?)
On Fri, Apr 27, 2018 at 3:37 PM, Adam Williamson adamwill@fedoraproject.org wrote:
On Sat, 2018-04-21 at 10:09 -0700, Link Dupont wrote:
Hi,
I've begun drafting this. I have some questions about F28 that I'm hoping some folks on this list can provide more details on.
*snip*
Here is one thing that *VERY BADLY NEEDS EXPLAINING*:
https://bugzilla.gnome.org/show_bug.cgi?id=757255 https://help.gnome.org/misc/release-notes/3.28/
I just upgraded my laptop to F28 and had no damn idea what had happened to right click. Apparently it had changed to how Macs do it because obviously Linux users expect everything to work like it does on a Mac. (What?)
Yeah I'm totally lost on this, not least of which is I'm not experiencing the behavior reported in the bug or the release notes. The application referenced in the release notes is not installed by default. And the application once installed doesn't have the options in it that the release notes says it should have.
(And off topic but I do *not* like that very prominent HURT ME BUTTON, labeled "Touchpad" with an on/off slider. Turning it off is for real and easy. Turning it back on again? Hahaha, figure it out yourself!)
On Fri, 2018-04-27 at 16:45 -0600, Chris Murphy wrote:
On Fri, Apr 27, 2018 at 3:37 PM, Adam Williamson adamwill@fedoraproject.org wrote:
On Sat, 2018-04-21 at 10:09 -0700, Link Dupont wrote:
Hi,
I've begun drafting this. I have some questions about F28 that I'm hoping some folks on this list can provide more details on.
*snip*
Here is one thing that *VERY BADLY NEEDS EXPLAINING*:
https://bugzilla.gnome.org/show_bug.cgi?id=757255 https://help.gnome.org/misc/release-notes/3.28/
I just upgraded my laptop to F28 and had no damn idea what had happened to right click. Apparently it had changed to how Macs do it because obviously Linux users expect everything to work like it does on a Mac. (What?)
Yeah I'm totally lost on this, not least of which is I'm not experiencing the behavior reported in the bug or the release notes. The application referenced in the release notes is not installed by default. And the application once installed doesn't have the options in it that the release notes says it should have.
I imagine this depends to some extent on hardware. I don't think it applies if your laptop has *physical* mouse buttons on it somewhere, for e.g. It also may not apply if the laptop does button emulation in firmware or something, such that libinput can't change it.
(And off topic but I do *not* like that very prominent HURT ME BUTTON, labeled "Touchpad" with an on/off slider. Turning it off is for real and easy. Turning it back on again? Hahaha, figure it out yourself!)
Well, that's obviously there for the case where you have some other input device and don't want accidental touches on the touchpad getting in the way. E.g. a USB mouse, or you use the touchscreen. It's not really *that* hard to trigger again with tab / enter if you hit it by accident when you *don't* have an external mouse or a touch screen, really...I guess it could stand a bit better 'don't click this without thinking about it' labelling, though...
On Fri, Apr 27, 2018 at 4:54 PM, Adam Williamson adamwill@fedoraproject.org wrote:
On Fri, 2018-04-27 at 16:45 -0600, Chris Murphy wrote:
On Fri, Apr 27, 2018 at 3:37 PM, Adam Williamson adamwill@fedoraproject.org wrote:
On Sat, 2018-04-21 at 10:09 -0700, Link Dupont wrote:
Hi,
I've begun drafting this. I have some questions about F28 that I'm hoping some folks on this list can provide more details on.
*snip*
Here is one thing that *VERY BADLY NEEDS EXPLAINING*:
https://bugzilla.gnome.org/show_bug.cgi?id=757255 https://help.gnome.org/misc/release-notes/3.28/
I just upgraded my laptop to F28 and had no damn idea what had happened to right click. Apparently it had changed to how Macs do it because obviously Linux users expect everything to work like it does on a Mac. (What?)
Yeah I'm totally lost on this, not least of which is I'm not experiencing the behavior reported in the bug or the release notes. The application referenced in the release notes is not installed by default. And the application once installed doesn't have the options in it that the release notes says it should have.
I imagine this depends to some extent on hardware. I don't think it applies if your laptop has *physical* mouse buttons on it somewhere, for e.g. It also may not apply if the laptop does button emulation in firmware or something, such that libinput can't change it.
The release notes say "all touchpads".
This is a one piece touchpad no buttons (it does click) on a skylake HP. So it's pretty new. I'd think it'd be affected by this change given the descriptions.
(And off topic but I do *not* like that very prominent HURT ME BUTTON, labeled "Touchpad" with an on/off slider. Turning it off is for real and easy. Turning it back on again? Hahaha, figure it out yourself!)
Well, that's obviously there for the case where you have some other input device and don't want accidental touches on the touchpad getting in the way. E.g. a USB mouse, or you use the touchscreen. It's not really *that* hard to trigger again with tab / enter if you hit it by accident when you *don't* have an external mouse or a touch screen, really...I guess it could stand a bit better 'don't click this without thinking about it' labelling, though...
Sure. How about putting *that* into Tweaks? Although I've never run into such a feature to totally disable the touchpad on macOS or Windows so the idea there's a real need here strikes me as specious.
On Fri, Apr 27, 2018 at 6:04 PM, Chris Murphy lists@colorremedies.com wrote:
The release notes say "all touchpads".
That's wrong, I think it's supposed to only affect clickpads
On Fri, Apr 27, 2018 at 5:20 PM, mcatanzaro@gnome.org wrote:
On Fri, Apr 27, 2018 at 6:04 PM, Chris Murphy lists@colorremedies.com wrote:
The release notes say "all touchpads".
That's wrong, I think it's supposed to only affect clickpads
Near as I can tell that's what I have.
On Fri, 2018-04-27 at 17:26 -0600, Chris Murphy wrote:
On Fri, Apr 27, 2018 at 5:20 PM, mcatanzaro@gnome.org wrote:
On Fri, Apr 27, 2018 at 6:04 PM, Chris Murphy lists@colorremedies.com wrote:
The release notes say "all touchpads".
That's wrong, I think it's supposed to only affect clickpads
Near as I can tell that's what I have.
Might be the 'firmware click emulation' thing, if I'm right about that. I guess who-t could explain.
On Fri, Apr 27, 2018 at 04:27:26PM -0700, Adam Williamson wrote:
On Fri, 2018-04-27 at 17:26 -0600, Chris Murphy wrote:
On Fri, Apr 27, 2018 at 5:20 PM, mcatanzaro@gnome.org wrote:
On Fri, Apr 27, 2018 at 6:04 PM, Chris Murphy lists@colorremedies.com wrote:
The release notes say "all touchpads".
That's wrong, I think it's supposed to only affect clickpads
Near as I can tell that's what I have.
Might be the 'firmware click emulation' thing, if I'm right about that. I guess who-t could explain.
"clickpads" are touchpads that don't have their own buttons but they have a hinge where you depress the whole touchpad. Those touchpads only have a left button, the right button is emulated in libinput based on the finger count, the finger positions and a combination of hope and despair. The libinput doc has pretty pictures. Well, pictures: https://wayland.freedesktop.org/libinput/doc/latest/clickpad_softbuttons.htm...
Chris: the previous gsetting was 'default' so if you ever changed it manually to 'areas' in the past (e.g. for debugging something), the change to a different default wouldn't affect you because you already have your own setting already. I strongly suspect that's the case for you, run this to verify: gsettings get org.gnome.desktop.peripherals.touchpad click-method If it says 'areas', you changed it at some point in the past.
Cheers, Peter
On Sun, Apr 29, 2018 at 6:20 PM, Peter Hutterer peter.hutterer@who-t.net wrote:
Chris: the previous gsetting was 'default' so if you ever changed it manually to 'areas' in the past (e.g. for debugging something), the change to a different default wouldn't affect you because you already have your own setting already. I strongly suspect that's the case for you, run this to verify: gsettings get org.gnome.desktop.peripherals.touchpad click-method If it says 'areas', you changed it at some point in the past.z
$ gsettings get org.gnome.desktop.peripherals.touchpad click-method 'fingers'
Only now do I grok "areas" and "fingers" in this screenshot as referencing the two settings in the release notes *which uses neither term* so I had no idea what it was referring to.
https://drive.google.com/open?id=10uahu6XOownq7oJS8O2TXg7TvW6Yy1_h
So the description there for "fingers" is what I've always experienced on this laptop with Fedora 25 through 28, and Windows 10. I tap two fingers at the same time to get a contextual menu. Meanwhile the release notes say "keep one finger in contact with the touchpad and tap with another finger" and that does nothing for me. Nothing happens. And yet the release notes say it's the default.
On Sun, Apr 29, 2018 at 07:08:18PM -0600, Chris Murphy wrote:
On Sun, Apr 29, 2018 at 6:20 PM, Peter Hutterer peter.hutterer@who-t.net wrote:
Chris: the previous gsetting was 'default' so if you ever changed it manually to 'areas' in the past (e.g. for debugging something), the change to a different default wouldn't affect you because you already have your own setting already. I strongly suspect that's the case for you, run this to verify: gsettings get org.gnome.desktop.peripherals.touchpad click-method If it says 'areas', you changed it at some point in the past.z
$ gsettings get org.gnome.desktop.peripherals.touchpad click-method 'fingers'
Only now do I grok "areas" and "fingers" in this screenshot as referencing the two settings in the release notes *which uses neither term* so I had no idea what it was referring to.
https://drive.google.com/open?id=10uahu6XOownq7oJS8O2TXg7TvW6Yy1_h
So the description there for "fingers" is what I've always experienced on this laptop with Fedora 25 through 28, and Windows 10. I tap two fingers at the same time to get a contextual menu. Meanwhile the release notes say "keep one finger in contact with the touchpad and tap with another finger" and that does nothing for me. Nothing happens. And yet the release notes say it's the default.
the release notes are inaccurate then. "tapping" has a specific meaning for touchpads [1], a short tap with a finger while *not* actually triggering a physical click. The changed default has no effect on tapping, only on clicking (and that only on clickpads).
On windows tapping and clicking are interlinked (for good reasons) but libinput can have a two-finger click cause a different button than a two-finger tap.
Cheers, Peter
[1] https://wayland.freedesktop.org/libinput/doc/latest/tapping.html
On Mon, 2018-04-30 at 11:23 +1000, Peter Hutterer wrote:
On Sun, Apr 29, 2018 at 07:08:18PM -0600, Chris Murphy wrote:
On Sun, Apr 29, 2018 at 6:20 PM, Peter Hutterer peter.hutterer@who-t.net wrote:
Chris: the previous gsetting was 'default' so if you ever changed it manually to 'areas' in the past (e.g. for debugging something), the change to a different default wouldn't affect you because you already have your own setting already. I strongly suspect that's the case for you, run this to verify: gsettings get org.gnome.desktop.peripherals.touchpad click-method If it says 'areas', you changed it at some point in the past.z
$ gsettings get org.gnome.desktop.peripherals.touchpad click-method 'fingers'
Only now do I grok "areas" and "fingers" in this screenshot as referencing the two settings in the release notes *which uses neither term* so I had no idea what it was referring to.
https://drive.google.com/open?id=10uahu6XOownq7oJS8O2TXg7TvW6Yy1_h
So the description there for "fingers" is what I've always experienced on this laptop with Fedora 25 through 28, and Windows 10. I tap two fingers at the same time to get a contextual menu. Meanwhile the release notes say "keep one finger in contact with the touchpad and tap with another finger" and that does nothing for me. Nothing happens. And yet the release notes say it's the default.
the release notes are inaccurate then. "tapping" has a specific meaning for touchpads [1], a short tap with a finger while *not* actually triggering a physical click. The changed default has no effect on tapping, only on clicking (and that only on clickpads).
Yeah, I noticed that too. The description in Tweak Tool is accurate: it says "Click the touchpad with two fingers for right-click and three fingers for middle-click". Sorry, Chris, I didn't realize you were being confused by the inaccurate description in the release notes.
OTOH, when you (Chris) say "So the description there for "fingers" is what I've always experienced on this laptop with Fedora 25 through 28", that seems odd. It was *definitely* not the default in F25. I don't see how you could have got that setting other than by doing it manually. Peter, is there any other way he could've got that setting?
On Mon, Apr 30, 2018 at 08:50:29AM -0700, Adam Williamson wrote:
On Mon, 2018-04-30 at 11:23 +1000, Peter Hutterer wrote:
On Sun, Apr 29, 2018 at 07:08:18PM -0600, Chris Murphy wrote:
On Sun, Apr 29, 2018 at 6:20 PM, Peter Hutterer peter.hutterer@who-t.net wrote:
Chris: the previous gsetting was 'default' so if you ever changed it manually to 'areas' in the past (e.g. for debugging something), the change to a different default wouldn't affect you because you already have your own setting already. I strongly suspect that's the case for you, run this to verify: gsettings get org.gnome.desktop.peripherals.touchpad click-method If it says 'areas', you changed it at some point in the past.z
$ gsettings get org.gnome.desktop.peripherals.touchpad click-method 'fingers'
Only now do I grok "areas" and "fingers" in this screenshot as referencing the two settings in the release notes *which uses neither term* so I had no idea what it was referring to.
https://drive.google.com/open?id=10uahu6XOownq7oJS8O2TXg7TvW6Yy1_h
So the description there for "fingers" is what I've always experienced on this laptop with Fedora 25 through 28, and Windows 10. I tap two fingers at the same time to get a contextual menu. Meanwhile the release notes say "keep one finger in contact with the touchpad and tap with another finger" and that does nothing for me. Nothing happens. And yet the release notes say it's the default.
the release notes are inaccurate then. "tapping" has a specific meaning for touchpads [1], a short tap with a finger while *not* actually triggering a physical click. The changed default has no effect on tapping, only on clicking (and that only on clickpads).
Yeah, I noticed that too. The description in Tweak Tool is accurate: it says "Click the touchpad with two fingers for right-click and three fingers for middle-click". Sorry, Chris, I didn't realize you were being confused by the inaccurate description in the release notes.
OTOH, when you (Chris) say "So the description there for "fingers" is what I've always experienced on this laptop with Fedora 25 through 28", that seems odd. It was *definitely* not the default in F25. I don't see how you could have got that setting other than by doing it manually. Peter, is there any other way he could've got that setting?
if the gsettings key is on 'fingers', then I'm pretty sure he set it at some point in the past. Or maybe some lucky stray radiation flipping exactly the right bit ;) There's the off-chance that at some point rawhide defaulted to fingers a few years back when this was added. But that requires more digging time than I'm willing to spend on this right now, sorry. Bastien or Carlos may know.
Just as another piece of information in case you need it: the clickfinger behaviour on the other hand is the libinput default for some touchpads like the apple ones. so some users would've seen clickfinger behaviour on their touchpads even with gnome being on 'default'. Those users too aren't affected by this change because either they accepted the default behaviour or manually switched to 'areas' in the past.
Cheers, Peter
On Fri, Apr 27, 2018 at 03:54:25PM -0700, Adam Williamson wrote:
On Fri, 2018-04-27 at 16:45 -0600, Chris Murphy wrote:
On Fri, Apr 27, 2018 at 3:37 PM, Adam Williamson adamwill@fedoraproject.org wrote:
On Sat, 2018-04-21 at 10:09 -0700, Link Dupont wrote:
Hi,
I've begun drafting this. I have some questions about F28 that I'm hoping some folks on this list can provide more details on.
*snip*
Here is one thing that *VERY BADLY NEEDS EXPLAINING*:
https://bugzilla.gnome.org/show_bug.cgi?id=757255 https://help.gnome.org/misc/release-notes/3.28/
I just upgraded my laptop to F28 and had no damn idea what had happened to right click. Apparently it had changed to how Macs do it because obviously Linux users expect everything to work like it does on a Mac. (What?)
Yeah I'm totally lost on this, not least of which is I'm not experiencing the behavior reported in the bug or the release notes. The application referenced in the release notes is not installed by default. And the application once installed doesn't have the options in it that the release notes says it should have.
I imagine this depends to some extent on hardware. I don't think it applies if your laptop has *physical* mouse buttons on it somewhere, for e.g. It also may not apply if the laptop does button emulation in firmware or something, such that libinput can't change it.
(And off topic but I do *not* like that very prominent HURT ME BUTTON, labeled "Touchpad" with an on/off slider. Turning it off is for real and easy. Turning it back on again? Hahaha, figure it out yourself!)
Well, that's obviously there for the case where you have some other input device and don't want accidental touches on the touchpad getting in the way. E.g. a USB mouse, or you use the touchscreen. It's not really *that* hard to trigger again with tab / enter if you hit it by accident when you *don't* have an external mouse or a touch screen, really...I guess it could stand a bit better 'don't click this without thinking about it' labelling, though... --
fwiw, libinput has a setting where it can automatically disable the touchpad for external mice but it's not integrated into GNOME (afaik). It's a bit problematic in that it provides little feedback once set. Ideally you want a OSD to signal your touchpad's disabled now. Otherwise it's hard to guess why nothing works after the bluetooth mouse in the sock drawer randomly decided to connect to your host.
So while the libinput feature is there, I'm not sure I can fully recommend it as a user-friendly solution for GNOME.
Cheers, Peter
PS: do not keep mice in a sock drawer. That's not their natural habitat.
Hi,
On 28-04-18 00:45, Chris Murphy wrote:
On Fri, Apr 27, 2018 at 3:37 PM, Adam Williamson adamwill@fedoraproject.org wrote:
On Sat, 2018-04-21 at 10:09 -0700, Link Dupont wrote:
Hi,
I've begun drafting this. I have some questions about F28 that I'm hoping some folks on this list can provide more details on.
*snip*
Here is one thing that *VERY BADLY NEEDS EXPLAINING*:
https://bugzilla.gnome.org/show_bug.cgi?id=757255 https://help.gnome.org/misc/release-notes/3.28/
I just upgraded my laptop to F28 and had no damn idea what had happened to right click. Apparently it had changed to how Macs do it because obviously Linux users expect everything to work like it does on a Mac. (What?)
Yeah I'm totally lost on this, not least of which is I'm not experiencing the behavior reported in the bug or the release notes. The application referenced in the release notes is not installed by default. And the application once installed doesn't have the options in it that the release notes says it should have.
So there are 2 possible explanations for why you are / your laptop is not affected by this:
1) You've once upon a time changed the setting in gnome-tweak-tool, so it is no longer at its "default" value (which now changed) but pinned to the value you've chosen
2) Linux does not properly recognize your touchpad as a touchpad so it is running in mouse emulation, since you also wrote:
(And off topic but I do *not* like that very prominent HURT ME BUTTON, labeled "Touchpad" with an on/off slider. Turning it off is for real and easy. Turning it back on again? Hahaha, figure it out yourself!)
2) seems unlikely, because in mouse-emulation mode that button would not hurt you. Note there is a good rationale for having that button, some people seriously like touchpads only use the trackstick or always carry an actual mouse with them.
Note many laptop keyboards have a hotkey to toggle the touchpad on and off, to accommodate such users. This hotkey effectively toggles the option behind that slider, so the slider is mostly there for people without the hotkey.
Regards,
Hans
p.s.
FWIW I personally I'm not in favor of the change of the default from the tried and trusted PC / windows standard button-areas behavior to the mac click-finger behavior. I've stated as much in the GNOME bug about this.
On Sun, Apr 29, 2018 at 12:34 PM, Hans de Goede hdegoede@redhat.com wrote:
Hi,
On 28-04-18 00:45, Chris Murphy wrote:
Yeah I'm totally lost on this, not least of which is I'm not experiencing the behavior reported in the bug or the release notes. The application referenced in the release notes is not installed by default. And the application once installed doesn't have the options in it that the release notes says it should have.
So there are 2 possible explanations for why you are / your laptop is not affected by this:
- You've once upon a time changed the setting in gnome-tweak-tool,
so it is no longer at its "default" value (which now changed) but pinned to the value you've chosen
I had to install Tweaks so since the last clean install, the default was not changed by me.
- Linux does not properly recognize your touchpad as a touchpad
so it is running in mouse emulation, since you also wrote:
No idea whether it's in mouse emulation or how to determine if it is.
$ dmesg | grep -i synap [ 1.527140] psmouse serio1: synaptics: queried max coordinates: x [..5690], y [..4772] [ 1.556655] psmouse serio1: synaptics: queried min coordinates: x [1250..], y [1084..] [ 1.556660] psmouse serio1: synaptics: Your touchpad (PNP: SYN3217 SYN1e00 SYN0002 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-input@vger.kernel.org. [ 1.614463] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 0xf00123/0x840300/0x12e800/0x400000, board id: 3214, fw id: 2407757 [ 1.651393] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input5 [chris@f28h ~]$
(And off topic but I do *not* like that very prominent HURT ME BUTTON, labeled "Touchpad" with an on/off slider. Turning it off is for real and easy. Turning it back on again? Hahaha, figure it out yourself!)
- seems unlikely, because in mouse-emulation mode that button
would not hurt you. Note there is a good rationale for having that button, some people seriously like touchpads only use the trackstick or always carry an actual mouse with them.
Tried it, it does in fact turn off the touchpad entirely, and it took me a while to figure out how to turn it back on.
We have an auto-revert timeout when making certain video changes that might result in the computer becoming unusable.
FWIW I personally I'm not in favor of the change of the default from the tried and trusted PC / windows standard button-areas behavior to the mac click-finger behavior. I've stated as much in the GNOME bug about this.
I'm fairly confused by the terminology and I'll split the blame for that on Synaptics, Apple, Microsoft and my (mal)adaptive behavior: after all I did finally say "fuck it" and reprogrammed myself to tolerate natural scrolling because I got sick of changing the setting everywhere.
--- Chris Murphy
On Sun, Apr 29, 2018 at 03:52:25PM -0600, Chris Murphy wrote:
On Sun, Apr 29, 2018 at 12:34 PM, Hans de Goede hdegoede@redhat.com wrote:
Hi,
On 28-04-18 00:45, Chris Murphy wrote:
Yeah I'm totally lost on this, not least of which is I'm not experiencing the behavior reported in the bug or the release notes. The application referenced in the release notes is not installed by default. And the application once installed doesn't have the options in it that the release notes says it should have.
So there are 2 possible explanations for why you are / your laptop is not affected by this:
- You've once upon a time changed the setting in gnome-tweak-tool,
so it is no longer at its "default" value (which now changed) but pinned to the value you've chosen
I had to install Tweaks so since the last clean install, the default was not changed by me.
you may have changed it via gsettings directly (see my other email)
- Linux does not properly recognize your touchpad as a touchpad
so it is running in mouse emulation, since you also wrote:
No idea whether it's in mouse emulation or how to determine if it is.
$ dmesg | grep -i synap [ 1.527140] psmouse serio1: synaptics: queried max coordinates: x [..5690], y [..4772] [ 1.556655] psmouse serio1: synaptics: queried min coordinates: x [1250..], y [1084..] [ 1.556660] psmouse serio1: synaptics: Your touchpad (PNP: SYN3217 SYN1e00 SYN0002 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-input@vger.kernel.org. [ 1.614463] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 0xf00123/0x840300/0x12e800/0x400000, board id: 3214, fw id: 2407757 [ 1.651393] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input5 [chris@f28h ~]$
it's not in mouse emulation, otherwise you'd see a PS/2 Wheel Mouse device. fwiw, googling for the PNP ids suggests you have HP Spectre, and looking at the pictures of the current model indicates you have a clickpad.
(And off topic but I do *not* like that very prominent HURT ME BUTTON, labeled "Touchpad" with an on/off slider. Turning it off is for real and easy. Turning it back on again? Hahaha, figure it out yourself!)
- seems unlikely, because in mouse-emulation mode that button
would not hurt you. Note there is a good rationale for having that button, some people seriously like touchpads only use the trackstick or always carry an actual mouse with them.
Tried it, it does in fact turn off the touchpad entirely, and it took me a while to figure out how to turn it back on.
We have an auto-revert timeout when making certain video changes that might result in the computer becoming unusable.
There's a similar-ish bug for a touch input toggle open here: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/29
IMO the most appropriate course would be for GNOME to be aware of available pointer devices and re-enable the touchpad automatically when all other pointer devices disappear. Doable but there are a few tricky details, in addition to the whole issue of "someone needs to actually write that code".
Cheers, Peter
FWIW I personally I'm not in favor of the change of the default from the tried and trusted PC / windows standard button-areas behavior to the mac click-finger behavior. I've stated as much in the GNOME bug about this.
I'm fairly confused by the terminology and I'll split the blame for that on Synaptics, Apple, Microsoft and my (mal)adaptive behavior: after all I did finally say "fuck it" and reprogrammed myself to tolerate natural scrolling because I got sick of changing the setting everywhere.
Chris Murphy _______________________________________________ desktop mailing list -- desktop@lists.fedoraproject.org To unsubscribe send an email to desktop-leave@lists.fedoraproject.org
desktop@lists.fedoraproject.org
-
Adam Williamson -
Chris Murphy -
Hans de Goede -
Jan Kurik -
Link Dupont -
mcatanzaro＠gnome.org -
Peter Hutterer