Bug 62804

Summary: weston-launch fails, due to using the incorrect tty by default with systemd-logind
Product: Wayland Reporter: Zach <zachcook1991>
Component: westonAssignee: Wayland bug list <wayland-bugs>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: medium    
Version: 1.0.x   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Zach 2013-03-27 10:42:15 UTC
weston-lauch fails with the following ouput:

Date: 2013-03-27 EDT
[06:26:39.134] weston 1.0.6
               http://wayland.freedesktop.org/
               Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=1.0.6
               Build:  
[06:26:39.134] OS: Linux, 3.8.4-1-overclock, #1 SMP PREEMPT Sun Mar 24 23:45:50 EDT 2013, x86_64
[06:26:39.134] Loading module '/usr/lib/weston/drm-backend.so'
[06:26:39.135] initializing drm backend
[06:26:39.138] couldn't open /dev/dri/card0, skipping
[06:26:39.138] failed to initialize egl
[06:26:39.138] failed to drop master: Permission denied
[06:26:39.146] fatal: failed to create compositor

This is caused by trying to use a tty that the user does not have permissions for, instead of the current tty for which systemd-logind gives permissions.

Running "weston-launch -t /dev/tty1" on tty1 will run correctly.

This only occurs when the user does not belong to the video or weston-launch groups, so that pam via systemd-logind is exclusively relied on to give permissions.
Comment 1 Zach 2013-04-02 19:38:44 UTC
This is actually due to immutable auditid in kernel

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.