[DSE-Dev] problem with gdm3 and sddm

Russell Coker russell at coker.com.au
Sun Jan 1 04:33:04 UTC 2017


The last big issue I want to fix for stretch is getting at least one of gdm3 
and sddm working, ideally both.

Below are the log messages I'm seeing when trying to run gdm3 in enforcing 
mode (after running "semodule -DB" and using audit2allow to allow basically 
everything on the system).  I think that the problem with getting a valid 
context for Debian-gdm is a large part of the problem.  Anyone have any ideas 
for how to debug this?

For sddm I saw very similar things with the added complication that sddm would 
SEGV.

I'm just about to upload a new policy package that has pretty much everything 
needed for stretch apart from whatever we find along the way to fixing gdm3 
and/or sddm.

Jan  1 15:28:28 server systemd: pam_selinux(systemd-user:session): Unable to 
get valid context for Debian-gdm
Jan  1 15:28:28 server systemd: pam_selinux(systemd-user:session): 
conversation failed
Jan  1 15:28:28 server systemd: pam_unix(systemd-user:session): session opened 
for user Debian-gdm by (uid=0)
Jan  1 15:28:29 server gdm-launch-environment]: pam_unix(gdm-launch-
environment:session): session closed for user Debian-gdm
Jan  1 15:28:29 server systemd-logind[509]: Removed session c655.
Jan  1 15:28:29 server gdm-launch-environment]: pam_unix(gdm-launch-
environment:session): session opened for user Debian-gdm by root(uid=0)
Jan  1 15:28:29 server systemd-logind[509]: New session c656 of user Debian-
gdm.
Jan  1 15:28:29 server systemd: pam_selinux(systemd-user:session): Unable to 
get valid context for Debian-gdm
Jan  1 15:28:29 server systemd: pam_selinux(systemd-user:session): 
conversation failed
Jan  1 15:28:29 server systemd: pam_unix(systemd-user:session): session opened 
for user Debian-gdm by (uid=0)

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/




More information about the SELinux-devel mailing list