Describe the package

I'd like to request the package (binary) micro from https://github.com/zyedidia/micro because it provides a very light-weight and user-friendly terminal editor option with "conventional" keybinds used by a majority of apps across multiple operating systems.

It is dramatically more usable as a basic text editor than Nano, the nearly ubiquitous default which it is named as a successor to. For example, Micro uses Ctrl+C and Ctrl+V for copy and paste. Nano uses "M-6" and "^U".

Within the same singular binary, it also provides syntax highlighting for most file types and languages, text completion, and a variety of powerful configurable features.

Personally, I would enjoy not needing to layer this anymore. If it is included via package, it should be confirmed that the package is up to date. Some package managers have an older version where, among other things, the system clipboard does not work, much like other terminal editors (in my experience).

Image

All Images

Describe the package

The default file manager in Sericea is Thunar which requires tumbler and not ffmpegthumbnailer (#49) I would also suggest excluding ffmpegthumbnailer for Sericea builds.

xfce:thunar:4.16:tumbler [Xfce Docs]
Arch Linux - thunar 4.18.4-1 (x86_64)

Image

Sericea

We can't use the same date tag on both 37 and 38 so we need to figure something out.

The goal is to be able to rollback to a specific date without having to look up the sha or whatever. For reference Fedora adds the date and sha to the version number, we should consider just following their approach:

38 points to 38.20230211.0.a22c714b
37 points to 37.20230211.0.3af18b81

They increment the third number if there's multiple builds in one day.

It'd be nice to have a diagram of all the images, which show which desktop comes with it (and perhaps the name and icon of each featured desktop) so that when non-Fedora-knowledgeable people see "sericia" they know that's sway, etc. We'll then stick it on the website.

Help wanted on this one!

https://github.com/orgs/ublue-os/discussions/106

Describe the package

I tried installing on a Surface Go 2. It currently has Fedora 38 beta which installed without issues.

When booting from ublue I receive an error before getting to a GUI or installation options.

dracut-initqueue: Unknown device: "/dev//run/install/repo//images/install.img": No such device
dracut-initqueue: Unknown device "/sys/": no such device

I've only tried booting from the main silverblue ISO

Image

Silverblue

The 38 builds are current missing the handy short sha tags.

Describe the package

Davinci Resolve, a popular video editing/color suite requires two layered packages, apr and apr-util, but otherwise works out of the box on Silverblue using the official installer. It conveniently installs to /opt, which is tracked by ostree. (Lucky!)

These are small packages, and I believe that including them would streamline the linux experience for someone trying to follow the steps on the Resolve website.

If these are out of scope, I would instead like to add an entry to the website.

Dependencies resolved.
================================================================================================================================================
 Package                                 Architecture                  Version                              Repository                     Size
================================================================================================================================================
Installing:
 apr                                     x86_64                        1.7.0-16.fc36                        fedora                        124 k
 apr-util                                x86_64                        1.6.1-20.fc36                        fedora                         95 k
Installing weak dependencies:
 apr-util-bdb                            x86_64                        1.6.1-20.fc36                        fedora                         12 k
 apr-util-openssl                        x86_64                        1.6.1-20.fc36                        fedora                         15 k

Transaction Summary
================================================================================================================================================
Install  4 Packages

Total download size: 246 k
Installed size: 541 k

Thanks!

Image

All Images

We need a method in the github action to ensure we kick off a build when the Fedora base image changes so there's as little lag between builds.

Additionally it'd be neat to implement these in the other images in the org so when the base image builds it kicks off all the other ones.

I've looked at:

• twiddler/is-my-docker-parent-image-out-of-date@v1 (Trying this one in the experimental repo)
• https://github.com/lucacome/docker-image-update-checker - this won't work it only supports Docker hub and we need to support all major registries.

Kyle helped us set up a ublue-os COPR where we can put stuff, and some of the images are pulling from RPMFusion, etc. We don't really have policy around third party repos but we should probably start talking about that.

This is all working ok for now, but long term we should just use the packages feature here for stuff when we can and just build them with actions.

Describe the package

I'd like to request the package zstd because ...

This is a common modern compression tool that we should provide.

Image

All Images

When I try to rebase an image with the latest tag like:

rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-desktop:latest

I get this error message:

error: Updating rpm-md repo 'rpmfusion-free-updates-testing': Failed to download gpg key for repo 'rpmfusion-free-updates-testing': Curl error (37): Couldn't read a file:// file for file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-37 [Couldn't open file /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-37]

Tested rebasing with other images with the latest tags; the same error pops up.

Discussed in https://github.com/ublue-os/main/discussions/96

Hi,
I try to switch from fedora silverblue 38 to Ublue OS Main 38.
Problem is : when I try to rebase to it, it remove a bunch of things including nautilus and gnome-software-center.
I have tried to type "rpm-ostree reset" after rebasing to it, but it removed even more things and the computer didn't boot anymore, I needed to rollback to an older deployment.
Does someone have an idea?
Thanks you

EDIT : I just tried to type "rpm-ostree reset", then reboot, then rebase to ublue os and same problem, it removed a bunch of stuff and I have a black screen on startup.

Hi.

As discussed over on Discord. I've been having this wierd bug with images based on main, including itself.

If I go to CUPS admin in http://localhost:631/ there is no option Windows Printer via SAMBA under Add Printer > Other Network Printers.

This doesn't happen on a vanilla fresh install of Silverblue.

The output of rpm -qa '*samba*' is the same on both systems:

samba-common-4.17.6-0.fc37.noarch
samba-client-libs-4.17.6-0.fc37.x86_64
samba-common-libs-4.17.6-0.fc37.x86_64
samba-client-4.17.6-0.fc37.x86_64

Both systems are freshly installed side by side so I can test the differences between the two.

Since the tag changed on the builds to "nightly" I've noticed that Discover (the update app for KDE) always shows an available update from nightly > [date tag].

To me looks like a tagging/naming problem, but Jorge said to post an issue so (blame him lol).

https://drive.google.com/file/d/12wL7Ix6rRrLYLeG6iFsAM3xlJIHpwdAS/view?usp=sharing

Filing for future consideration. Currently rebasing to the signed image fails:

rpm-ostree rebase --experimental ostree-image-signed:docker://ghcr.io/ublue-os/base:latest
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/base:latest
error: Preparing import: Fetching manifest: containers-policy.json specifies a default of `insecureAcceptAnything`; refusing usage

According to the manpage we could set up the policy.json and probably also config in containers-registries.d to make it all seamless.

• https://www.mankier.com/5/containers-policy.json#Policy_Requirements-sigstoreSigned
• https://www.mankier.com/5/containers-registries.d

Hello!

It would be nice to have an automatic rawhide target that builds this container against Fedora Rawhide. This is especially useful during next Fedora release development...

this says it all

Hello! I found an issue when rebasing from Kionite to Silverblue, the config on Gnome is messed up. To fix this when you are a user, you have to set the themes, icons, window decorations, and cursors(?) in gnome-tweaks.

You also have to fix the fonts, which is as simple as running:

gsettings reset org.gnome.desktop.interface font-name
gsettings reset org.gnome.desktop.interface document-font-name
gsettings reset org.gnome.desktop.interface monospace-font-name
gsettings reset org.gnome.desktop.wm.preferences titlebar-font
gsettings reset org.gnome.desktop.interface text-scaling-factor

Do you think you could have this be an automatic fix on ublue-os? That would make this process far easier.

Right now we're making LXQt and MATE images but they're directly from the ostree builds and not derived from main. I was wondering if we should add (not replace) -main variants?

Personally I think we should make these so people who use those desktops can enjoy the QoL of -main, but they're not derived from Fedora so we should probably just say that.

I think it'd be useful to make them so people can try it, and then if there's interest we can help onramp them to Fedora to make an official build if there's interest.

Publish a github action workflow that can be used to build any software project in ublue-os as an RPM and publish the RPM in a package repository using github pages. This will allow us to include dependencies in layers during build time without relying too much on external infrastructure

For now it's hard to distinguish regular and modded Silverblue on a bootloader
(user needs to remember ostree entry number)

Describe the package

I'd like to request the package smartmontools and nvme-cli.

I saw a user in chat having problems with their disk and couldn't diagnose it properly, we should consider these tools for basic storage troubleshooting.

Image

All Images

I've checked in an initial contributing.md but it needs instructions for firing up a registry on your machine or local network and pushing to it. A simple one like docker/registry is probably more appropriate than k8s/harbor. 😄

Create a GHA
min ks from each repo
defines the location of custom image
slipstream into fedora iso
mkksiso
each of these is 560mb net installer for each flavor of image
attach to each release

installer checks if it's nvidia and can determine if it's an nvidia machine

Describe the package

Virtualbox is required for some use cases, and on Fedora OSTree its an absolute pain to setup.

1. Add another repo
2. Install the packages including kernel mods
3. sign the packages for secureboot to work

This sounds like a perfect usecase for your images!

Image

All Images

We've been using the images at: quay.io/fedora-ostree-desktops/
The new location is: quay.io/fedora/fedora-silverblue (as an example)

This issue is to track that change.

See also https://pagure.io/releng/issue/11047#comment-846909

When I install akmod-wl on my laptop using the silverblue-main:37 image, I get the following error. It works fine on the official silverblue image but this error apears on ublue. To reproduce, install silverblue, rebase to silverblue-main:37 image, type sudo rpm-ostree install akmod-wl then you get this error. The same thing happens on my laptop and in a vm.

Downloading from 'rpmfusion-nonfree'... done Importing packages... done Checking out packages... done Running pre scripts... done Running post scripts... done error: Running %post for akmod-wl: bwrap(/bin/sh): Child process killed by signal 1; run journalctl -t 'rpm-ostree(akmod-wl.post)' for more information

What happened?

I got a similar issue as #108. I tried the iso 1.1.0 and 1.3.1

1. Using the Fedora Media Writer I get the error (on nvidia variations only I think):

error: .../...tpm.c:150:unknown TPM error.

• I have the secure boot disabled
  I could solve this thanks to: https://discussion.fedoraproject.org/t/tpm-error-on-booting/76724
  Using ventoy also solved the issue.

2. But then going forward it gets stuck before the installer (screen appears with ventoy)
   

In terms of hardware, this is on my laptop Asus zenbook ux410 with 2 SSD (nvme0n1 and sda).

Relevant log output

No response

Quick release checklist:

• Update latest tags to F38
• Update ISO generator to source from release instead of development
• Beta announcement blog post

What happened?

Trying to install universalblue-38-x86_64-20230418.iso using Ventoy. It runs for a bit, then complains that the kickstart file is missing. I verified in the shell that the file isn’t there.
this occurs whether I select the main or Nvidia install.

Relevant log output

anaconda. 38.23.4-2.fc38 for Fedora 38 started.
* Installation log files are stored in tmp during the installation
* shell is avallable on TTY2 and in second TX pane (ctrl+b, then press 2)
* when reporting a bug add logs from /tmp as separate text/plain attachments
16:32:12 Kickstart File /run/install/ks.cfg is missing.

(Manually corrected ocr of pic of screen)

They are available here: https://quay.io/organization/fedora-ostree-desktops

I think it'd be cool to build them (especially for nvidia users), what do people think?

There are some mods that are more specific.

NVIDIA is a y/n and there are always two images. But now imagine additional things coming like

• Virtualbox support + signing
• QEMU support ootb
• custom drivers for Wifi cards
• some Davinci resolve mods
• ...

These would be way better in a modular design.

1. Block that adds packages to the install build
2. Block that adds additional commands

Somehow this could then be a "click to get" distro, where you get

• This distro exists, download it here
• This distro doesnt exist, here are the configs you can use to create your own repo

What do you think of that?

Image

All Images

Tracking issue for: https://github.com/cgwalters/bootc-examples

Add bootc to https://github.com/ublue-os/main for all image builds in base.

Describe the package

The potential akmod change discussed in https://github.com/orgs/ublue-os/discussions/106 would be a perfect opportunity to include the v4l2loopback package.

Since it is an akmod from RPMfusion, it would be a giant pain in the behind to layer and thus perfect candidate for inclusion in main.
Unified signing infrastructure, as discussed above, should make this hopefully painless. I'm currently trying to get it to world on the nvidia image.

The most common use-case is probably obs-virtualcam, it is the only thing keeping me from using ublue on my daily drivers, as I absolutely require it to make various videoconferencing software, which do not play nice on linux, work.

Image

All Images

As this is intended to be the upstream for other Ublue images, I don't think this is supposed to be templated from, rather inherited on.
I don't believe I can do this myself, someone with full perms has to do it.

Today in discord #general I responded to a question about how to get one/both of these drivers into a ublue image. An ensuing chat prompted the creation of this issue for further discussion on the topic.

xpadneo specifically supports xbox one wireless controller via bluetooth
xone supports xbox one controllers/accessories via USB or the USB wireless dongle, aims to replace xpad

I've personally been building my own image atop ublue-os main and nvidia to add these two drivers. As akmods, like the nvidia drivers, they also need a signing key to support Secure Boot systems.

So this is a multipart question:

1) should both xpadneo and xone be added to ublue-os/main ? just one? which? why?
It was suggested in chat that we already have udev rules for various devices so adding drivers like this doesn't seem like much of a stretch.

xpadneo pros:

• xbox one controllers will work via bluetooth (I don't believe they function via bluetooh without this driver)

xpadneo cons:

• ???

xone pros:

• xbox one wireless usb dongle support
• claims to be " a modern replacement for xpad, aiming to be compatible with Microsoft's Game Input Protocol (GIP)."

xone cons:

• when installed will take priority over xpad for any supported devices, which some users may not prefer

2) If either are added, they need a signing key to enable Secure boot. How to handle this?

I'd personally suggest moving the existing key from nvidia into main and renaming it to ublue such that main would provide instructions to import like: sudo mokutil --import /etc/pki/akmods/certs/akmods-ublue.der

If so, it would be nice for this same key get re-used by the nvidia build so that only one key needs to be imported.

Though, there could be two distinct keys.

For reference, here's my repo and build of these akmods: https://github.com/bsherman/ublue-kmods/

Describe the package

I'd like to request the package htop because ...
having htop pre-installed is nice rather than using toolbx/distrobox container

Image

All Images

Create an application that is responsible for installing Flatpaks on first boot after a user finishes installation. It is intended as a replacement for custom zenity dialogs.

Project goals

• Config file driven via JSON/YAML
• Support for arbitrary pre and post-install commands
• Configuration driven screens
• Screen independent state management with ability to set defaults
• Extensible with drop-in Python classes / plugins to extend functionality

We take the list of packages and then send it to rpm-ostree install.

This creates one huge layer. If we had each package be it's own RUN so it maps out like this:

RUN rpm-ostree install package1
RUN rpm-ostree install package2

Then this would create smaller layers and would be more efficient instead of one huge layer. I'm guessing that on individual updates it would bring in one layer instead of having to download the huge layer any time any of the packages get updated.

(We need to look up how many layers are supported by podman)

The instructions are missing from the readme, we need to show people how to actually use these. :D

Hey!

I think having a default auto-update policy is great, but for my workstation I tend to try and "audit" what packages get added and removed between updates and give a chance of pinning deployments should I need to roll back a few versions. I also prevent my TPM from unlocking my root disk if any changes have been made to GRUB, which happens on an update.

I looked at this repo, the config repo, and then the documentation for rpm-ostreed. It seems I'll just need to set AutomaticUpdatePolicy to "none" in /etc/rpm-ostreed.conf (and if I wanted to, systemctl disable flatpak-system-update.timer, but automatic updates to flatpack sounds nice). Would it be reasonable to include these instructions in the README if this is the proper way to do this?

I figured I would open an issue here just to get some discussion on how others use automatic updates and how they administer their systems.

Describe the package

I'd like to request the package podman-compose because ... podman-compose is currently missing in Fedora ostree installation
podman-compose

Image

All Images

What happened?

When using the iso to install ublue a rpm-ostree-backend error occurs mentioning invalid reference for OCI container ostree format.

Relevant log output

$ plasma-discover
rpm-ostree-backend: Invalid reference for OCI container ostree format: "ostree-unverified-image:docker://ghcr.io/ublue-os/kinoite-nvidia:38"
1pm-ostree-backend: Starting transaction to check for updates
rpm-ostree-backend: Error: Can not start a transaction for resource with an invalid format. Please file a bug.
org.kde.plasma.libdiscover: transaction not part of the model RpmOstreeTransaction(0x55a798d95d40)
KCrash: Application 'plasma-discover' crashing...
The Wayland connection experienced a fatal error: Bad file descriptor

Describe the package

I'd like to request the package ffmpegthumbnailer on the main image. Getting this working is annoying so let's just fix this.

We'll need to rm .cache/thumbnails/failed too, probably in the post script?

Confirmed this works on silverblue but it appears to be filemanager agnostic.

Image

Silverblue

Dynamically display all available ublue-os images/flavors on the website updated without human interaction. Each image should display it's name, description, instructions on how to rebase, available tags, links to the github repo, readme, and when available link to ISO / signature for each image

• org.opencontainers.image.base.name
• org.opencontainers.image.base.digest
• org.opencontainers.image.vendor
• org.opencontainers.image.revision

Full list here.

We should look at a functional equivalent of a ChromeOS "powerwash": https://support.google.com/chromebook/answer/183084?hl=en

Hi,
First, thanks you a lot for your work!
This is not really a bug, more of a question, but I don't know where to ask it unfortunally.
On my computer, I haven't had any upgrade since the 13th april.
Is this normal, or is there a problem with my installation?
If this is normal, is there a policy for upgrade? Like, are they release once a week or something like that?
When I was running fedora silverblue, I had update nearly every day.
Thanks you a lot!