Linux

66809 readers

266 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 7 years ago

MODERATORS

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

Bazzite rebasing question (lemmy.ml)

submitted 14 hours ago* (last edited 13 hours ago) by ItsPlasmaSir@lemmy.ml to c/linux@lemmy.ml

6 comments fedilink hide all child comments

I rebased my laptop install to bazzite-dx yesterday and for some reason, the stable branch installed a testing image (testing-44.20260802) instead of the latest stable image (stable-44.20260802). I pinned to the latest stable for now but does anyone know why bazzite rebase helper would do this?

Edit: I just checked the release info again since that was last night for me, and it just installed the same image again. Rebasing via rpm-ostree pulls the same image too. I’m gonna rebase back to normal bazzite for now and check to see if this also happened to my desktop I switched a couple weeks ago

Edit 2: Yep, my desktop was also on a test image. I wouldn’t have even thought to check if the test image wasn’t locking up my laptop. Until now bazzite has been so stable for me, now I’m wishing I left my desktop on fedora as a backup in case something like that happens again

top 6 comments

sorted by: hot top controversial new old

[–] TheModerateTankie@hexbear.net 3 points 11 hours ago (1 children)

Is it not letting you rebase to stable?

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

[–] ItsPlasmaSir@lemmy.ml 2 points 10 hours ago (1 children)

Rebasing to normal Bazzite worked fine, but for some reason rebasing on Bazzite-DX, even when picking a specific stable image, would pull the testing image from the same day every time

[–] TheModerateTankie@hexbear.net 1 points 9 hours ago* (last edited 9 hours ago)

Oh, I see. From the bug reports posted, it looks like the -dx image is based on the bazzite deck 44 image for some reason, which isn't out of testing yet. ~~If that's deliberate it's an odd choice~~. The new deck 44 image should be updated to stable soon.

edit: Further reading indicates it's based on the deck image so that they don't have to maintain two different dx versions.

[–] throwaway403@programming.dev 2 points 10 hours ago (1 children)

A couple of issue trackers I found that may (or may not be) related:

Question: Could you paste the output of rpm-ostree status?

[–] ItsPlasmaSir@lemmy.ml 1 points 9 hours ago* (last edited 9 hours ago)

Thanks for the links, I still hadn’t rebased my desktop yet so I took a before and after of both rpm-ostree and fastfetch, and saw 209 in effect

Before

After

What has me still confused is that the different bazzite update tool in the testing image was also confused by the image

Bazzite Update Tool

I mean why would it say a stable image has a testing id and bootloader if its not testing

[–] warmaster@lemmy.world 1 points 12 hours ago

Damn, now I want to check if I'm on testing too... I rebased from bazzite-deck to bazzite.