Hide Forgot
Description of problem: Attempting to recover from suspend on laptop always results in rapidly flashing authentication failure screens, then dropping to a screen with wallpaper and mouse motion, but nothing else functions. Must use power switch to escape. Version-Release number of selected component (if applicable): How reproducible: Running: F24 Alpha > Mate > Compiz. Close lid on laptop to suspend, open lid to recover, type correct password into dialog, click unlock or press [Enter]. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Samsung NP940X3g, i5, 4g RAM, 120G Sandisk Nano.
I'm sorry but this is more likely a bug in the screensaver or suspend/wakeup implementation on your hw. Are you able to lock/unlock the screensaver if not suspending? If you switch to text console after the suspend/resume are you able to login there?
1) Screen locks and unlocks correctly without suspend. 2) Switching to text console is not possible after failure. Nothing works but mouse movement and the power button. 3) System suspends and recovers as expected in F16, F21, F23. 4) No screensavers beyond what is default in Mate are installed. Anything else I can get for you?
Added info: Suspend recovery seems to be the broken element. Lock and unlock works, but suspending without screen locking fails partially. Compiz is obviously still working, as the Expo function also works. But nothing else does. Another factor may be that I am running F24 from an install on a 120g Sandisk Nano USB3.o Jump drive -- from a SUB3.0 port. This did not seem to present a problem in previous versions, but if pressed, I can't really remember ever suspending on them. Boot is quick enough that I typically just shut down.
Ok. Now it is letting me into another login, but throwing this error continuously: EXT4-fs error(device sdb3)
Failure seems to indicate once it suspends, it loses contact with the sdb3 (/root) partition, and can't read from it nor write to it, so whatever is left in memory, is all it's got to work with. Not sure it's worth trying to work around that. This looks like a corner case issue.
Reassigning to kernel as it is obvious that pam is not the culprit here.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs. Fedora 24 has now been rebased to 4.7.4-200.fc24. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 25, and are still experiencing this issue, please change the version to Fedora 25. If you experience different issues, please open a new bug report for those.
I can't add a whole lot more to this. I've since tested and the problem only occurs when operating out of a liveUSB or USB jump drive. The bare metal install works appropriately since the latest updates I have applied. This one should probably be closed then just to get it off the books. Sorry about the delay. Real Life happens, and takes priority. Thanks.
Thank you for letting us know. I'm going to close this now. The bug can be reopened if there is a problem.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs. Fedora 25 has now been rebased to 4.10.9-100.fc24. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.