Hide Forgot
Description of problem: Hi, I'm not sure if it is related to wayland or some other component so I'm defaulting to wayland. I'm using default F25 installation with GNOME shell and autofs. When I access NFS mount point through /net/NFSserver/export which will later become unreachable because I move my laptop to some other location with that NFS unavailable, my custom bound keyboard shortcuts for launching gnome-terminal and web browser become unresponsive. The same applies for volume/brightness buttons on my T450s. After I bring laptop back to the original location with NFS available, all the queued shortcuts are being executed. Version-Release number of selected component (if applicable): xorg-x11-server-Xwayland-1.19.0-1.fc25 How reproducible: 100% Steps to Reproduce: 1. Enable autofs (maybe mounting some NFS suffice) 2. In GNOME shell set up some custom keyboard shortcut 3. Go to some reachable NFS export dir (cd /net/NFSserver/export) 4. Make NFS export location unreachable 5. Optionally suspend laptop/resume from sleep 6. Try to use custom key shortcut or hardware buttons for volume/brightness change Actual results: Volume/brightness, keyboard shortcuts are being queued and not actually executed Expected results: The aforementioned should work Additional info:
So after talking to kparal from Fedora QA, this bug is not related to wayland, go to reassign this to some other component. GNOME? I really don't know what is causing this. Note that I'm not using gnome components to go to the NFS mountpoint but when the mountpoint isn't reachable GNOME is hardly usable then.
Already reassigned.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.