https://bugzilla.novell.com/show_bug.cgi?id=739221

https://bugzilla.novell.com/show_bug.cgi?id=739221#c0

Summary: /etc/pam.d/xdm lacks pam_systemd module Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: All OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs@forge.provo.novell.com ReportedBy: javier@conti-menchini.ch QAContact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: ---

User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20100101 Firefox/9.0

In /etc/pam.d/xdm (in openSUSE 12.1) the pam_systemd module is missing by default. systemd-uaccess is used to set ACL on device files in some cases (e.g. when a digital camera is plugged in) and it's not able to get information about the user owning the session (i.e. /run/systemd/seats/seat0 is not updated by PAM), as we can see in the following example:

$ cat /run/systemd/seats/seat0 # This is private data. Do not parse. IS_VTCONSOLE=1

Putting the pam_systemd module in /etc/pam.d/xdm as follows:

$ cat /etc/pam.d/xdm #%PAM-1.0 auth include common-auth account include common-account password include common-password session required pam_loginuid.so session required pam_systemd.so kill-session-processes=1 session include common-session

Makes PAM update the /run/systemd/seats/seat0 correctly, as in the following example:

$ cat /run/systemd/seats/seat0 # This is private data. Do not parse. IS_VTCONSOLE=1 ACTIVE=521 ACTIVE_UID=1000 SESSIONS=521 UIDS=1000

And some devices that didn't work because of wrong permissions, start to work.

Probably, the case where a user boots with old SysV init should be managed too, but currently without that entry users using systemd may experience problems in using some devices.

Reproducible: Always

Steps to Reproduce: 1. Plug a device such a digital camera 2. Try using it as the user owning the session (not root) Actual Results: There is an error writing to the device

Expected Results: The user owning the session should be able to write to the device (if writing is supported)

See OP: http://lists.opensuse.org/opensuse/2011-12/msg01512.html