Bug 1274169

Summary: Cannot login after recent update of lxdm
Product: [Fedora] Fedora Reporter: Daniel <danielsun3164>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 22CC: christoph.wickert, danielsun3164, dominick.grift, dwalsh, lvrabec, mgrepl, mtasaka, plautrba
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 20:41:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
/var/log/lxdm.log
none
part of /var/log/messages
none
result of ausearch -m avc -ts this-month none

Description Daniel 2015-10-22 08:04:21 UTC
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.

Comment 1 Daniel 2015-10-22 08:05:08 UTC
Created attachment 1085439 [details]
part of /var/log/messages

Comment 2 Mamoru TASAKA 2015-10-22 12:47:42 UTC
Maybe you can log in when you change SELinux mode to permissive (or disabled)?

Comment 3 Daniel 2015-10-23 02:19:05 UTC
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?

Comment 4 Mamoru TASAKA 2015-10-23 02:28:31 UTC
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.

Comment 5 Mamoru TASAKA 2015-10-23 03:22:11 UTC
F-24/23/21 selinux-policy may also need updating.

Comment 6 Mamoru TASAKA 2015-10-23 03:25:14 UTC
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

Comment 7 Miroslav Grepl 2015-10-23 08:25:10 UTC
Is there chance to test it in permissive mode and run

# ausearch -m avc -ts recent

Comment 8 Daniel 2015-10-26 07:14:51 UTC
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.

Comment 9 Miroslav Grepl 2015-11-11 08:25:51 UTC
Could you please try to run

restorecon -R -v ~/

to see if it fixes this issue.

Comment 10 Daniel 2015-11-23 12:55:01 UTC
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.

Comment 11 Fedora End Of Life 2016-07-19 20:41:58 UTC
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.