home.social

#xvfb — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #xvfb, aggregated by home.social.

  1. replacement update ...
    - CentOS Stream 10 container: Installing `epel-release` then `weston` gives me dependency issues. Currently a non-starter
    - Ubuntu 22.04 on arm64 (real machine, the others are in containers: Tells me the display number in the startup). xclock runs ok
    - Fedora or Ubuntu container (40/42/22.04): Works but segfaults with --xwayland unless you precreate /tmp/.X11-unix

    There is hope!

  2. #weston #xvfb replacement update ...
    - CentOS Stream 10 container: Installing `epel-release` then `weston` gives me dependency issues. Currently a non-starter
    - Ubuntu 22.04 on arm64 (real machine, the others are in containers: Tells me the display number in the startup). xclock runs ok
    - Fedora or Ubuntu container (40/42/22.04): Works but segfaults with --xwayland unless you precreate /tmp/.X11-unix

    There is hope!

  3. #weston #xvfb replacement update ...
    - CentOS Stream 10 container: Installing `epel-release` then `weston` gives me dependency issues. Currently a non-starter
    - Ubuntu 22.04 on arm64 (real machine, the others are in containers: Tells me the display number in the startup). xclock runs ok
    - Fedora or Ubuntu container (40/42/22.04): Works but segfaults with --xwayland unless you precreate /tmp/.X11-unix

    There is hope!

  4. #weston #xvfb replacement update ...
    - CentOS Stream 10 container: Installing `epel-release` then `weston` gives me dependency issues. Currently a non-starter
    - Ubuntu 22.04 on arm64 (real machine, the others are in containers: Tells me the display number in the startup). xclock runs ok
    - Fedora or Ubuntu container (40/42/22.04): Works but segfaults with --xwayland unless you precreate /tmp/.X11-unix

    There is hope!

  5. Why did no one tell me about #Xvfb before? Now I'm running #Everdo 'headless' on my server and have my desktop, laptop and phone all syncing to it. 🥳

  6. Why did no one tell me about #Xvfb before? Now I'm running #Everdo 'headless' on my server and have my desktop, laptop and phone all syncing to it. 🥳

  7. Why did no one tell me about #Xvfb before? Now I'm running #Everdo 'headless' on my server and have my desktop, laptop and phone all syncing to it. 🥳

  8. CW: debian/docker project show-and-tell with a lot of links

    One of my most useful personal projects is my own customized #Debian #Linux ISO image, with my packages, tools, dotfiles and configuration just the way I want it.

    It uses Debian Live to build the ISO, which can be used as a #liveusb or an installer. I can build it locally via #vagrant with #libvirt, or using a #GitHub workflow.

    Here's what I think is one of the coolest things: the GitHub workflow builds the ISO then packages it into a #Docker image. When run, that container provides the following:

    • an HTTP server from which the ISO can be download
    • a #VNC server (using #novnc and #Xvfb) for connecting to the live instance running on #QEMU with #kvm
    • a #websockify interface for accessing the VNC server in a web browser

    It's so useful for me to have my environment with me wherever I go as I carry it around with me on my #Ventoy thumb drive, whether running it as a one-off live instance or the installer, and to have the environment in a Docker container where I can spin it up as needed.

  9. CW: debian/docker project show-and-tell with a lot of links

    One of my most useful personal projects is my own customized #Debian #Linux ISO image, with my packages, tools, dotfiles and configuration just the way I want it.

    It uses Debian Live to build the ISO, which can be used as a #liveusb or an installer. I can build it locally via #vagrant with #libvirt, or using a #GitHub workflow.

    Here's what I think is one of the coolest things: the GitHub workflow builds the ISO then packages it into a #Docker image. When run, that container provides the following:

    • an HTTP server from which the ISO can be download
    • a #VNC server (using #novnc and #Xvfb) for connecting to the live instance running on #QEMU with #kvm
    • a #websockify interface for accessing the VNC server in a web browser

    It's so useful for me to have my environment with me wherever I go as I carry it around with me on my #Ventoy thumb drive, whether running it as a one-off live instance or the installer, and to have the environment in a Docker container where I can spin it up as needed.

  10. CW: debian/docker project show-and-tell with a lot of links

    One of my most useful personal projects is my own customized #Debian #Linux ISO image, with my packages, tools, dotfiles and configuration just the way I want it.

    It uses Debian Live to build the ISO, which can be used as a #liveusb or an installer. I can build it locally via #vagrant with #libvirt, or using a #GitHub workflow.

    Here's what I think is one of the coolest things: the GitHub workflow builds the ISO then packages it into a #Docker image. When run, that container provides the following:

    • an HTTP server from which the ISO can be download
    • a #VNC server (using #novnc and #Xvfb) for connecting to the live instance running on #QEMU with #kvm
    • a #websockify interface for accessing the VNC server in a web browser

    It's so useful for me to have my environment with me wherever I go as I carry it around with me on my #Ventoy thumb drive, whether running it as a one-off live instance or the installer, and to have the environment in a Docker container where I can spin it up as needed.

  11. CW: debian/docker project show-and-tell with a lot of links

    One of my most useful personal projects is my own customized #Debian #Linux ISO image, with my packages, tools, dotfiles and configuration just the way I want it.

    It uses Debian Live to build the ISO, which can be used as a #liveusb or an installer. I can build it locally via #vagrant with #libvirt, or using a #GitHub workflow.

    Here's what I think is one of the coolest things: the GitHub workflow builds the ISO then packages it into a #Docker image. When run, that container provides the following:

    • an HTTP server from which the ISO can be download
    • a #VNC server (using #novnc and #Xvfb) for connecting to the live instance running on #QEMU with #kvm
    • a #websockify interface for accessing the VNC server in a web browser

    It's so useful for me to have my environment with me wherever I go as I carry it around with me on my #Ventoy thumb drive, whether running it as a one-off live instance or the installer, and to have the environment in a Docker container where I can spin it up as needed.