Bug 67837

Summary:	[weston-launch] default pam configuration breaks on fedora 19
Product:	Wayland	Reporter:	Joe Konno <joe.konno>
Component:	weston	Assignee:	Wayland bug list <wayland-bugs>
Status:	VERIFIED NOTABUG	QA Contact:
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	All
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Joe Konno 2013-08-06 17:47:41 UTC

After building wayland and weston 1.2.0, weston-launch does not work "out of the box" on a (fairly) pristine Fedora 19 installation. "Fairly" because I disabled selinux shortly after installation.

The first error encountered (stdout/stderr weston-launch):

  failed to open pam session: 14: Cannot make/remove an entry for the specified session

And /var/log/secure:

  Aug  6 10:18:30 $host weston-launch: pam_loginuid(login:session): set_loginuid failed
  Aug  6 10:18:30 $host weston-launch: pam_unix(login:session): session opened for user $user by (uid=1000)

I did a web search, found a cheap work-around for the pam issue here:
  https://ask.fedoraproject.org/question/25453/weston-launch-start-problem/

Which entails commenting out a line in the default pam configuration file:
  # #weston-launch# session    required     pam_loginuid.so

--

The expectation is that weston-launch "just works" with sufficient permissions (all documented) are granted. However, that is not the case on Fedora 19.

--

# yum list installed | grep -e "xkbcommon" -e "pam"
libxkbcommon.x86_64                      0.3.0-1.fc19                  @fedora  
libxkbfile.x86_64                        1.0.8-3.fc19                  @fedora  
pam.x86_64                               1.1.6-12.fc19                 @updates

Comment 1 Joe Konno 2013-08-06 21:46:05 UTC

This is an integration issue, not a Weston issue. Was missing a package.

Comment 2 Joe Konno 2013-08-06 21:46:50 UTC

Woops. Wrong bug. This is still an issue, disregard comment 1.

Comment 3 Kristian Høgsberg 2013-10-24 18:49:12 UTC

We talked about this off-line and the issues here was that you were logging in from ssh and trying to run weston-launch or running from under X11.  Either is not supported anymore, the uses cases for weston-launch is

 1) Use from a text mode login (a VT)

 2) Use from a systemd (or other init system) script with -u $USER and --tty 1

It still possible to log in from ssh and run weston as root, which is how we test it now.

In the future, with the logind integration, we may be able to do something like

 # openvt sudo -u krh weston

to launch it as a regular user from ssh.

Either way, I'm closing this bug as it's no longer how weston-launch is supposed to work.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.