Antoine Martin

Good news! Tracked down the issue - it isn't a problem with Xorg, but rather with pam. There needs to be an Alpine version of [/etc/pam.d/qubes-gui-agent](https://github.com/QubesOS/qubes-gui-agent-linux/blob/master/appvm-scripts/etc/pam.d/qubes-gui-agent). I've been trying for...

Doesn't seem to have to do with pam anymore (edit: or maybe it does??) strace: ```log execve("/usr/bin/qubes-gui-runuser", ["/usr/bin/qubes-gui-runuser", "user", "/etc/X11", "/bin/sh", "-l", "-c", "exec /usr/bin/xinit /etc/X11/xin"...], 0x7ffdc547b8d0 /* 23 vars...

@moiselazarus Apologies for the delay, I was without my laptop for a little while. You will find the repo updated with latest openrc files. Following this guide to setting up...

Current state of `qubes-gui-runuser` issue: * fixed error `connect(3, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 24) = -1 ENOENT (No such file or directory)` by installing `musl-nscd`, executing `echo 'hosts: files dns' > /etc/nsswitch.conf`,...

Debugged the issue: the qubes-gui-runuser issue had to do with two things: one was an error of mine in misunderstanding the command syntax, and the other was that qubes-run-xorg was...

> > `Failed to open xengntshr: Permission denied!` > > Missing udev rules from https://github.com/QubesOS/qubes-linux-utils/blob/master/udev/udev-qubes-misc.rules ? Or maybe `user` isn't a member of `qubes` group? Adding `user` to `qubes` group...

> `qubes-session` process should run as `user`, and should have that user environment (including `HOME=/home/user`). > > > `qvm-run alpine urxvt` does not work > > You can add `-p`...

> > starts `qubes-session` under `user`, but it stalls > > It should remain running, with various children processes (mostly dependent on /etc/xdg/autostart content). The question is whether `qrexec-fork-server` is...

Memory ballooning doesn't work, any pointers that I could follow? Note that no initcpio hooks have been adapted to Alpine. I suspect it may have something to do with that....

> > Memory ballooning doesn't work, any pointers that I could follow? > > That's about `qubes-meminfo-writer` service. Indeed, `/sbin/meminfo-writer` is started on boot, but it doesn't do anything when...