CNot sure when I'll get to it but I'll try to give that a shot
TAnyone know how to solve
Error: OCI runtime error: crun: ptsname: Inappropriate ioctl for deviceWait it just went away
Tnever seen that one before
TSeems to be working here, apart from being able to find containers on the host which I'd expect to not work since it's running inside a distrobox
KAwesome, thank you!
Xsure thanks, it appears i'm not watching the repo, i should get to that...
K@j0rge
Kdisappearing windows is some wobbly window bug
Kignore that lol
ESweet! Incredible work on getting all of this together
Jcan you post an update here? https://universal-blue.discourse.group/t/moving-to-gnomes-prompt-for-a-default-terminal/248
Universal Blue
Alright folks, here it is! https://blogs.gnome.org/chergert/2023/12/14/prompt/ and here’s a companion video I made: Find the repo here: Christian Hergert / prompt · GitLab Let’s use this thread for feedback/ideas, and then we can be good OSS citizens by kicking the tyres to get the terminal of our dreams! Here’s our in progress...
XI just noticed something funny.
XAll Ublue repos I checked have a checkout action step like this:
XI wondered why this makes no sense. Then I googled "Checkout Push to Registry action" and found this: https://github.com/redhat-actions/push-to-registry/blob/9986a6552bc4571882a4a67e016b17361412b4df/.github/workflows/multiple-build.yaml#L30C1-L32C34
XThe build action for the
push-to-registrySeems that at some point someone, probably jorge, copied some code that builds the
push-to-registrypush-to-registrywe're using
actions/checkout@v4Yeah
XThat's not what's funny.
XYeah, this goes back to the beginning. https://github.com/ublue-os/base/commit/b5217833327427c673ef39883ef7813b7f5e9f36
J@KyleGospo https://universal-blue.discourse.group/t/moving-to-gnomes-prompt-for-a-default-terminal/248/7
Universal Blue
Yeah this looks like this issue: Error if distrobox container has not been entered once (#31) · Issues · Christian Hergert / prompt · GitLab We might need to interact with them on boot or something as a workaround in the meantime, anyone have thoughts on that?
Bits just a wrong name it doesnt really matter
XThat's why I said it was funny not severe...
BRandom thought.... are there any plans for a hyprland build of ublue?
XThere are a lot of community images but not "official" ones. It would need a maintainer who uses the image and is willing to support others using it. Could be basically any community member, though.
BWith hypr now beibg available for install direct from dnf in fedora 39, I know I could just rpm- ostree install it at build, but was just curious
BWould someone with 0 experience be able to be a community maintainer?
XWell, you'd have to be willing to learn of course.
BLearning is a favorite hobby
BJust trying to figure if I could commit to it with work plus my 2 kids
XI think other high-level maintainers here have similar situations, and the community is here to help.
XIt's just needed that some person does the effort to kickstart it and commits to at least looking after the issues and PRs.
XEThe public signatures for our hwcompat images don't align. I think I should regenerate the key pairs for all of them:
https://github.com/ublue-os/bazzite/pull/615
https://github.com/ublue-os/bazzite/pull/615
Jkey looks the same in bazzite? which one doesn't match?
EThe keys for ASUS, Surface, and Framework base images (Kinoite and Silverblue). I wrote a test for Bazzites CI to verify the sigs before building the image
Joh I hadn't noticed that?
EI hadn't either because they successfully sign. It's very odd
JI think we just put the previous cosign.pub in those repos and use the org-wide secret?
EYeah
JI hadn't even noticed that, good catch!
EI figured we might as well add these tests to our downstream images. Establishes some form of verification. I wish the ci-test images were signed too
EWe can even do this for the Chainguard images Bluefin DX pulls from
Jci-test has been around a year longer than I anticipated
Jfeels like the upstream of silverblue/kinoite are getting a ton of attention now but the fedora parts are less maintained than they were before. 
Jthe fedora one didn't build for 10 days!
Jthis verification is a great idea!
EThank you! I was brainstorming over this yesterday after looking over a lot of the images Chainguard has and going through their documentation. Then this morning I put two and two together
