Created attachment 1085438 [details] /var/log/lxdm.log Description of problem: Cannot login after recent update of lxdm Version-Release number of selected component (if applicable): lxdm-0.4.1-10.fc22.x86_64 How reproducible: Everytime Steps to Reproduce: 1. Start PC up to lxdm login screen 2. Select user and input password Actual results: Cannot login and go back to login screen again Expected results: Login with any problems Additional info: 1. After downgrade of lxdm to lxdm-0.4.1-9.fc22.x86_64, everything works for me 2. I was using 1280x800 screen resolution, lxdm-0.4.1-10.fc22.x86_64 will only diplay 1024x768 for me.
Created attachment 1085439 [details] part of /var/log/messages
Maybe you can log in when you change SELinux mode to permissive (or disabled)?
Thank you very much for your contact. My selinux status was "Enforcing", after changed it to "Disable", I can login now. Is this a lxdm bug or selinux bug?
Okay, thank you. Due to the fix for bug 1268900 , lxdm-binary now needs to write /var/run/lxdm/lxdm-XXX, and perhaps it is the culprit. Perhaps selinux-policy needs updating. Reassing to selinux-policy to ask to update.
F-24/23/21 selinux-policy may also need updating.
The relevant change between 0.4.1-9 and 0.4.1-10 is: http://pkgs.fedoraproject.org/cgit/lxdm.git/commit/?h=f22&id=ab0c2f863ea59dc2dac27c01f67fceefac8dcdb8
Is there chance to test it in permissive mode and run # ausearch -m avc -ts recent
Created attachment 1086389 [details] result of ausearch -m avc -ts this-month Thank you very much for your contact. My "ausearch -m avc -ts recent" returned "<no matches>", I attached my result of "ausearch -m avc -ts this-month" here. I found that I can login from lxdm-0.4.1-10.f22.x86_64 now, but the resolution kept to be 1024x768 although I changed it to 1280x800 before reboot.
Could you please try to run restorecon -R -v ~/ to see if it fixes this issue.
Thank you very much for your contact. I tried to run restorecon -R -v ~/ but the resolution was still 1024x768 after I changed it to 1280x800 and reboot again.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.