Description of problem: I am unable to disable touchpad with the Fn+F3 key combination on a Dell N5040 laptop. Version-Release number of selected component (if applicable): 0.15.0-2.fc22 How reproducible: Always. Steps to Reproduce: 1. Boot up Fedora 22. 2. Login 3. Press Fn+F3 key combination to enable/disable touchpad. Actual results: Touchpad state doesn't get changed. Expected results: Touchpad gets disabled or enabled depending on a state before the key combo was pressed. Additional info: [user@box] $ cat /proc/bus/input/devices I: Bus=0011 Vendor=0002 Product=0008 Version=0300 N: Name="AlpsPS/2 ALPS DualPoint TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input6 U: Uniq= H: Handlers=mouse2 event8 B: PROP=9 B: EV=b B: KEY=e420 70000 0 0 0 0 B: ABS=260800001000003 Moving a switch to disable/enable touchpad in the Gnome Control Panel works as expected.
if you run sudo libinput-debug-events and then hit the shortcut, do you see a key event for it?
I see the key event for the shortcut when I run sudo libinput-debug-events.
punting over to g-s-d
Why is this bug closed although it is not fixed in the Fedora? If it is closed because it's transferred to the upstream, where is the link to the new bug report?
Please click the Status link to check what UPSTREAM means, effectively "deferred to upstream, they need to fix it first". Also Rui entered the external bug ID, it's in the "External Trackers" list at the top.
Ah, sorry. I wasn't able to find that information. Thank you.
Indeed this bug has been fixed upstream. The fix was included in gnome-settings-daemon 3.16.3 (not yet packaged for fedora 22): https://git.gnome.org/browse/gnome-settings-daemon/log/?h=gnome-3-16 Is gnome 3.16.3 panned to be released/packaged on f22? https://wiki.gnome.org/ThreePointSeventeen Any plan to back-port the patch down-stream?
I am doing that now. Thanks Luca!
https://bodhi.fedoraproject.org/updates/FEDORA-2015-14140 includes gnome-settings-daemon 3.16.3 update
control-center-3.16.3-1.fc22 gnome-settings-daemon-3.16.3-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-14140
Thank you Kalev! I've waited 3 months for this moment. :) How should I test new package? I've enabled fedora-updates-testing and I did dnf update --refresh but I do not see the new gnome-settings-daemon package? Did I misunderstood something?
It takes a day or so before the update is pushed out to mirrors. There's some manual release engineering work involved that they do only daily - signing packages and so on. Bodhi (the update wrangling system we have) will post another comment here when it's pushed out to the mirrors. Otherwise what you said above is exactly how to test it, just wait a bit :)
control-center-3.16.3-1.fc22, gnome-settings-daemon-3.16.3-1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update gnome-settings-daemon control-center'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-14140
Updated to gnome-settings-daemon 3.16.3 this morning, but the bug is still present. Already commented on gnome bugzilla.
(In reply to Kalev Lember from comment #12) > It takes a day or so before the update is pushed out to mirrors. There's > some manual release engineering work involved that they do only daily - > signing packages and so on. Bodhi (the update wrangling system we have) will > post another comment here when it's pushed out to the mirrors. > > Otherwise what you said above is exactly how to test it, just wait a bit :) I've updated to the gnome-settins-daemon 3.16.3 a couple of minutes ago and now I can enable and disable touchpad via the Fn+F3 combination on this laptop model, finally. Thanks Kalev again. (In reply to Luca Cavalli from comment #14) > Updated to gnome-settings-daemon 3.16.3 this morning, but the bug is still > present. Already commented on gnome bugzilla. What is the exact model of the touchpad you have? I have "AlpsPS/2 ALPS DualPoint TouchPad" and now it works. You can see your touchpad name in the output of the cat /proc/bus/input/devices command. Do you Luca have the same laptop? If not, maybe it's best to branch this bug report. Close this one as fixed and open a new one for you.
(In reply to Марко М. Костић (Marko M. Kostić) from comment #15) > (In reply to Luca Cavalli from comment #14) > > Updated to gnome-settings-daemon 3.16.3 this morning, but the bug is still > > present. Already commented on gnome bugzilla. > > What is the exact model of the touchpad you have? I have "AlpsPS/2 ALPS > DualPoint TouchPad" and now it works. You can see your touchpad name in the > output of the cat /proc/bus/input/devices command. > > Do you Luca have the same laptop? If not, maybe it's best to branch this bug > report. Close this one as fixed and open a new one for you. Nope, my touchpad is a: I: Bus=0011 Vendor=0002 Product=000e Version=0000 N: Name="ETPS/2 Elantech Touchpad" P: Phys=isa0060/serio4/input0 S: Sysfs=/devices/platform/i8042/serio4/input/input11 U: Uniq= H: Handlers=mouse1 event7 B: PROP=1 B: EV=b B: KEY=6420 30000 0 0 0 0 B: ABS=260800011000003 Yep, this bug is specific to Dell N5040, but gnome bugzilla entry seems generic :)
Then I think that the best course of action is to open a new bug report for your specific laptop on this Bugzilla and to mark this bug report as closed upstream. Kalev, what do you think?
No strong opinion here. Do what you think is best.
I'm trying to verify if my problem is hardware related or not. Марко, are you able to catch the 'Fn' key press (*alone*, not combined with any other key) with tools like libinput-debug-events, evtest, xev or showkey (this one running in terminal)? Thanks!
(In reply to Luca Cavalli from comment #19) > I'm trying to verify if my problem is hardware related or not. > > Марко, are you able to catch the 'Fn' key press (*alone*, not combined with > any other key) with tools like libinput-debug-events, evtest, xev or showkey > (this one running in terminal)? Thanks! Pressing Fn key in: libinput-debug-events: nothing evtest: nothing xev: nothing showkey: nothing All tools were runnning as root. (In reply to Kalev Lember from comment #18) > No strong opinion here. Do what you think is best. I will close this bug because it's tied to a specific model of the laptop and it's solved on this laptop. Luca, it's best to verify if you have a hardware error or not and then open a new bug for your laptop model if it's not a hardware error. Closing as fixed.
Probably a hardware problem. Also with fedora 21 live Fn key doesn't work. Sorry for the noise...
control-center-3.16.3-1.fc22, gnome-settings-daemon-3.16.3-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.