Bluefin-lts doesn't include `xhost`?

Bluefin
1

Hey,

Put bluefin-lts on a new drive to replace my old one, and copied my user directory to the /var/home on the new drive, running the whole thing in a VM first to see how it goes

bluefin-lts appears to include distrobox, sure enough, but my scripts call for zenity and xhost, and neither one seem to be included. Looks like at least xhost is included in other releases, like bluefin, bazzite, etc. if I’m reading these forum threads correctly.

Is this by error or design?

Edit: I might be able to replace zenity with dialog (zenity does not work when installed via brew) but xhost is not a brew package, and installing via unpacked rpm in /usr/local would be a real PITA (lots of .so dependency packages)

Would this be more suitable as a bug report? Thanks

Edit: Noticing views, but no replies - is basically just nobody using bluefin-lts?

I personally hate btrfs because it feels like it introduces a geometric FS-usage proportional response latency to the system. Also why I stopped installing ZFS for root devices way long ago (on anything but Solaris-derivs). I always install Fedora to xfs thinvols, or any other distro, for that matter… e.g. Ubuntu or Debian using debootstrap : https://unixgreybeard.org/2024/08/12/the-miracle-of-debootstrap-installing-ubuntu-to-thin-lvm-in-a-very-archlinux-like-way/)

If there’s any way to install a bootc image on a different filesystem than it was containerized as, would love to know (I’m fantasizing, right?)

2

I think it’s more people don’t use X. :smiley: File an issue on the bluefin-lts repo and we can take a look, it might be useful for it to stick around for container work.

bootc install should work fine on other filesystems (lts defaults to XFS).

3

I might just not understand how distrobox works very well. I thought it required xhost for exporting apps. Admittedly, I don’t think I ever tried exported apps without implementing these instructions first, IIRC.

Reference: distrobox/docs/useful_tips.md at 3b9f0e8d3d8bd102e1636a22afffafe00777d30b · 89luca89/distrobox · GitHub

If your container is not able to connect to your host xserver, make sure to install xhost on the host machine and run xhost +si:localuser:$USER. If you wish to enable this functionality on future reboots add the above command to your ~/.distroboxrc

-$ cat ~/.distroboxrc xhost +si:localuser:$USER >/dev/null

re: bootc and filesystems, doesn’t it just overwrite the entire drive with a new disk image that’s whatever filesystem the container was created using?

Thanks

4

This might be the same situation as silverblue not including xauth. It is on kinoite and other base images.

xhost can interact with Xwayland.

Zenity on the otherhand would be a different discussion. It is part of gnome now and I currently have it on my bluefin derived image.

5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.