https://bugzilla.novell.com/show_bug.cgi?id=723339 https://bugzilla.novell.com/show_bug.cgi?id=723339#c13 --- Comment #13 from Vincent Untz <vuntz@suse.com> 2011-10-20 12:40:44 UTC --- So this is the issue: 2011-10-20 15:58:16 <1> linux.site(2481) [YCP] Bootloader.ycp:1535 handleSELinuxPAM called 2011-10-20 15:58:16 <1> linux.site(2481) [YCP] Bootloader.ycp:1543 call disableSELinuxPAM It turns out that this calls pam-config: void disableSELinuxPAM () { string cmd_disable_se = "pam-config -d --selinux 2>/dev/null"; string cmd_enable_aa = "pam-config -a --apparmor 2>/dev/null"; map out = (map) SCR::Execute (.target.bash, cmd_disable_se); y2debug("result of disabling the SELinux PAM module is %1", out); out = (map) SCR::Execute (.target.bash, cmd_enable_aa); y2debug("result of enabling the AppArmor PAM module is %1", out); } And this apparently breaks the hack we have in kiwi-config-openSUSE where we temporarily comment out the pam_gnome_keyring bit in /etc/pam.d/common-auth-pc. Not sure how we should handle that :/ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.