lazlo.vii

I think I might have found an answer. After googling and reading and rinsing and repeating I learned that the device scan at boot should be done by the initramfs. So I extracted the contents of my initramfs with: cp /boot/initramfs-debian* /tmp/initramfs.xz cd /tmp unxz *.xz cpio -i -d < initramfs The first place I looked was in the "init" script in the root on the cpio and I found this code section starting at line 383: # Setup btrfs, see bug 303529 setup_btrfsctl # start BTRFS volume detection [ -x /sbin/btrfsctl ] && /sbin/btrfsctl -a The command "btrfsctl" is

For several weeks I have had this issue on my server and I would like to resolve it before I upgrade the hardware this week. Basically, btrfs partitions are not recognized when the system boots up. In order to reboot the server I have to stop everything on my network that relies on NFS or LXD containers from the server. Then attach a keyboard, mouse and monitor to the server and boot it up, stop the NFS daemon, run btrfs device scan, then run mount -a, then start NFS and LXD and then start my containers. Then I disconnect my keyboard, mouse, and monitor and reconnect them to my desktop and

I think portage wants you to set the introspection USEFLAG for x11-libs/pango in /etc/portage/package.use, and then (most likely) you will have to add it for number of other gtk related packages as well. I have run into something similar with both LXDE and virt-manager. TBH, I don't really know what the introspection USEFLAG does or why it wants it. I hope that helps.

Getting closer! I have sound from Steam if after every reboot on my desktop system I start the steam-nvidia-launcher then open another terminal and do: pusleaudio --kill pulseaudio --start After doing this I can even start games the require Steam Play, A.K.A. Proton, A.K.A. Steam's fork of WINE (and why fsck -sake don't they just call it WINE?! I mean it's not like it's a secret or anything!) However I cannot launch games the require Vulkan. So no X4: Foundations or No Man's Sky. At this point I am not only getting frustrated, I am getting drunk. After all, why pound my head

I have this issue on my server at the moment, but I am not using KDE on it. It is still running Funtoo 1.3 and I discovered this while trying to rebuild the system with -mtune generic so I could upgrade the hardware next month without a reinstall. This issue stopped my "emerge -e @world" in it's tracks. On my desktop I just did a fresh install of Funtoo 1.4 and was able to install sys-apps/accountsservice without issues. I haven't looked into the issue any further because I am fighting with I desktop. If I win I get to use Steam in Funtoo. If it wins I have to keep Ubuntu installed

At some point in the future it would be nice to add automatic updates to the container so that it doesn't become a security risk if the user ignores it for too long: https://help.ubuntu.com/lts/serverguide/automatic-updates.html But lets get other things working before we try for bells and whistles.

For testing purposes I did a container wipe before I started this post. Both the host and the container return :0 when told to "echo $DISPLAY". The when told "xhost +local:" the host returned " bash: xhost: command not found" so I did "emerge -va xhost" then issued "xhost +local:" again and (because the containter was still running) the Steam Client launched immediately. I was also able to launch glxgears as root as well as with the steam account. Inside the container both the root account and the steam account can generate white noise with "pacat -vvvv /dev/urandom". However

Had another thought. How hard would it be to script the creation of a empty ext4 filesystem image that gets mounted into the Steam image? This could be used to store backups of the game installation files and be persistent across Steam container wipes.

A bit more info about things that do not work as expected: Trying to launch any game the using Steam Play, A.K.A. Proton, A.K.A. Steam's fork of WINE will cause a segfault in vgui2_s.so Steam seems to trying to use ALSA as it's audio backend. Here is a bit of /home/steam/.steam/error.log: AL lib: (WW) alc_initconfig: Failed to initialize backend "pulse" ALSA lib confmisc.c:767:(parse_card) cannot find card '0' ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_conc

OK, I made a huge step forward. The display couldn't be opened and I was reminded of errors I had seen while learning how to use x11vnc. That problem was caused because x11vnc couldn't find a valid .Xauthority file. So while trying to find a way to pass the tell glxgears to use a valid .Xauthority file I found this question and answer on askubuntu.com: https://askubuntu.com/questions/827070/cant-run-glxgears-in-root-on-lxc-2-0-container I passed my user account xauth into the steam container's root account I was able to run glxgears as root. On host do: $

This is from inside the docker container, looking at the display hardware: root@2b739c474a3e:/# ls -al /dev/nvi* crw-rw-rw- 1 root root 195, 254 Oct 29 01:34 /dev/nvidia-modeset crw-rw-rw- 1 root root 240, 0 Oct 29 01:34 /dev/nvidia-uvm crw-rw-rw- 1 root root 240, 1 Oct 29 01:34 /dev/nvidia-uvm-tools crw-rw-rw- 1 root root 195, 0 Oct 29 01:34 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Oct 29 01:34 /dev/nvidiactl root@2b739c474a3e:/# ls /dev/dri card0 renderD128 root@2b739c474a3e:/# lspci | grep VGA 08:00.0 VGA compatible controller: NVIDIA Corporation Device 1f02 (rev a1)

This is from dmesg on the host. The block of messages below repeats as long as the steam-nvidia-launcher is active: [53909.798612] systemd-logind[23]: Failed to start user slice user-1000.slice, ignoring: Launch helper exited with unknown return code 1 (org.freedesktop.DBus.Error.Spawn.ChildExited) [53909.801133] systemd-logind[23]: Failed to start user service, ignoring: Launch helper exited with unknown return code 1 [53909.803728] systemd-logind[23]: Failed to start session scope session-1.scope: Launch hel

I tried it last night. It cannot open the display: oot@2b739c474a3e:/# glxgears No protocol specified Error: couldn't open display :0 Is there anything else I should be trying?

4.19.67_p2-r1-debian-sources-lts Seems to missing a few things by default as well: >>> Emerging (1 of 1) app-emulation/docker-18.09.6_p20190604::nokit * docker-18.09.6_p20190604.tar.gz BLAKE2B SHA512 size 😉 ... [ ok ] * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 4.19.67_p2-r1-debian-sources-lts * Checking for suitable kernel configuration options... * CONFIG_MEMCG_SWA

I just ran into an issue with the Steam Docker install, so I built the debian-sources-lts real quick. I want to post this for you before I reboot and test docker again: * Messages for package sys-kernel/debian-sources-lts-4.19.67_p2-r1: * * To avoid automounting and auto(un)installing with /boot, * just export the DONT_MOUNT_BOOT variable. * * With binary use flag enabled /usr/src/linux * symlink automatically set to debian kernel >>> Auto-cleaning packages... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. real