Re: [systemd-devel] [PATCH weston] doc/systemd: system service example

On Dec 29, 2017 15:32, "Mantas Mikulėnas" wrote: On Fri, Dec 29, 2017 at 11:09 PM, Matt Hoosier wrote: > > The approach that you and Pekka most recently put on record here: > > * User=foo > * PAMName=weston > > with a /etc/pam.d/weston that just does minimal stuff (enforce the > account exists

Re: [systemd-devel] [PATCH weston] doc/systemd: system service example

Hi Lennart, On Mon, Dec 4, 2017 at 9:11 AM, Pekka Paalanen wrote: > On Fri, 1 Dec 2017 18:25:35 +0100 > Lennart Poettering wrote: > >> On Fr, 01.12.17 13:42, Pekka Paalanen (ppaala...@gmail.com) wrote: >> >> > > > > This is racy, as the session ID is not really reliably predictable, >> > > > > a

[PATCH v5 1/7] libweston: set the seat automatically based on the XDG_SEAT environment variable

This will allow the seat to be set by the environment as pam_systemd typically sets the XDG_SEAT variable --- compositor/main.c | 2 +- libweston/compositor-drm.c | 5 + man/weston-drm.man | 7 +-- 3 files changed, 11 insertions(+), 3 deletions(-) diff --git a/compositor/

[PATCH v5 5/7] libweston: fbdev: Attempt to detect the first framebuffer device in the seat. instead of defaulting to /dev/fb0

This adds a function to detect the first framebuffer device in the current seat. Instead of hardcoding /dev/fb0, use udev to find the first framebuffer device in the seat. --- libweston/compositor-fbdev.c | 45 +--- 1 file changed, 42 insertions(+), 3 deleti

[PATCH v5 4/7] libweston: fbdev: set fb device info upon the first run.

This attempts to wake up secondary framebuffer devices (/dev/fb1 and up) as usually these devices start powered off, and the FBIOPUT_VSCREENINFO ioctl turns it on. This was tested on a qemu system with the options: -vga none -device VGA,id=video0 -device secondary-vga,id=video1 \ -device secondary

[PATCH v5 3/7] launcher-logind: only get a VT on seat0, as only seat0 supports VTs

As only seat0 supports TTYs, this changes the logind launcher where it detects a TTY, only if the seat is seat0. This has only been tested for logind --- libweston/launcher-logind.c | 22 -- libweston/launcher-util.c | 4 2 files changed, 16 insertions(+), 10 deletions(

[PATCH v5 7/7] libweston: fbdev: Follow the same logic as compositor-drm, and favor the boot_vga device

virtual framebuffer devices that are created by a modesetting driver have the same parent as the drm card devices. --- libweston/compositor-fbdev.c | 40 ++-- 1 file changed, 34 insertions(+), 6 deletions(-) diff --git a/libweston/compositor-fbdev.c b/libwesto

[PATCH v5 6/7] main: don't configure /dev/fb0 by default

--- compositor/main.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/compositor/main.c b/compositor/main.c index ecd034b9..02de108b 100644 --- a/compositor/main.c +++ b/compositor/main.c @@ -1454,9 +1454,6 @@ load_fbdev_backend(struct weston_compositor *c, parse_options(fbdev_opti

[PATCH v5 0/7] Make Weston multiseat aware

These patches make Weston handle multiple seats. Fixes from the last attempt include updating fbdev_set_screen_info , updating some fuzz, and making the selection of the framebuffer device similar to compositor-drm.c by favoring the boot_vga device https://github.com/n3rdopolis/weston nerdopoli

[PATCH v5 2/7] libweston: fbdev: support the --seat option, (and XDG_SEAT variable)

This allows the fbdev backend to run on, and use devices from the specified seat, similar to the drm backend. --- compositor/main.c| 2 ++ libweston/compositor-fbdev.c | 10 +- libweston/compositor-fbdev.h | 1 + 3 files changed, 12 insertions(+), 1 deletion(-) diff --git a/