| Summary: | Ecrypt blocks graphical login | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michael Monreal <michael.monreal+bugs> |
| Component: | ecryptfs-utils | Assignee: | Michal Hlavinka <mhlavink> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | esandeen, mhlavink |
| 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: | 2012-08-07 17:21:45 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Michael Monreal
2011-10-08 11:45:25 UTC
are there any other lines in the logs (/var/log/messages or /var/log/secure )? The line, you've attached is somehow debug message, it does not mean any problem, if you do not use pam automount. what is output of grep -r ecryptfs /etc/pam.d on your machine? And what is content of your /etc/pam.d/postlogin file? Thanks $ grep -r ecryptfs /etc/pam.d /etc/pam.d/postlogin:auth optional pam_ecryptfs.so unwrap /etc/pam.d/postlogin:password optional pam_ecryptfs.so unwrap /etc/pam.d/postlogin:session optional pam_ecryptfs.so unwrap /etc/pam.d/postlogin-ac:auth optional pam_ecryptfs.so unwrap /etc/pam.d/postlogin-ac:password optional pam_ecryptfs.so unwrap /etc/pam.d/postlogin-ac:session optional pam_ecryptfs.so unwrap $ cat /etc/pam.d/postlogin #%PAM-1.0 # This file is auto-generated. # User changes will be destroyed the next time authconfig is run. auth optional pam_ecryptfs.so unwrap password optional pam_ecryptfs.so unwrap session optional pam_ecryptfs.so unwrap btw I don't think there is anything of interest in dmesg. this is what I see when logging in root on the console: [ 126.254489] login[1163]: ecryptfs: pam_sm_authenticate: pam auth stack calls pam_ecryptfs module [ 126.254499] login[1163]: ecryptfs: pam_sm_authenticate: pam_ecryptfs: username = [root] [ 126.274294] login[1163]: pam_unix(login:session): session opened for user root by LOGIN(uid=0) [ 126.274305] login[1163]: ecryptfs: fill_keyring: Unable to get ecryptfs pam data : No module specific data is present [ 126.352986] login[1163]: ROOT LOGIN ON tty2 I've just tried to reproduce it on Fedora 15 and it works fine. Also, it's really odd that gdm does not work, because ecryptfs itself does nothing. It's called when something verifies your password and that's where gdm has already started. So nothing that should affect gdm start. Do you have your system fully updated? What version of ecryptfs-utils do you use? Do you see any selinux denial messages? Yes,everything is up to date. SELinux is completely disabled. I still don't know what causes this, because I can't reproduce it and there is no obvious error here. - do you use some special configuration for gdm? - do you use automatic login? - did you changed pam configuration? - do you have fingerprint reader? please try to reproduce this again. After you reproduce this problem, run following command (it's just a one-line command, bugzilla will split it probably): tar cvzf /tmp/logs.tgz /var/log/audit/audit.log /var/log/boot.log /var/log/messages /var/log/secure /var/log/gdm/ It will create file /tmp/logs.tgz, please attach it here. Thanks - do you use some special configuration for gdm? no - dont even know where I could do this - do you use automatic login? on one system I do, one one I don't. both were affected - did you changed pam configuration? no (but the ecryptfs package did?) - do you have fingerprint reader? on one system, but I think it is disabled I will try to reproduce this later if I get a chance This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |