On 2019-11-28 19:27, Patrick Dupre wrote: > To reproduce the bug (fedora 30) > 1) Create a sshfs on a remote machine from your home directory (sshfs user@machine:/home/dir ~/SSHFS) > 2) Lock the screen (I use gnome) > 3) Unplug the internet cable of your machine for example (the connection stalls > pretty often with a ADSL connection) > 4) Wait a minute and replug the cable > 5) Try to log back in your gnome session. > After I enter the password, the time wheel froze and nothing happen anymore > You can log on the machine through a stty, and kill the gnome-session to have a new graphic session. > After that it may happen that you cannot make the same sshfs again without restarting the machine. I do not have an F30 system available. So, I tried, and was unable to reproduce this on F31. I have the following. An F31 system with GNOME running in a VM. I mounted via sshfs the home directory on a system located in the USA. I then locked the screen. I disconnected the link in the VM's GUI. After more than a minute I reconnected the nic. I then entered my pw to unlock the screen and it unlocked immediately. Additionally, the sshfs mount was still functional. I was also able to unlock the screen with the NIC disconnected. Of course something like "df" hung until (I didn't leave it hung long) the NIC is reconnected. -- The key to getting good answers is to ask good questions. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
