you can rebase to the gnome version, the unrecommended way. Worked for me once
you can rebase to the gnome version, the unrecommended way. Worked for me once
KIt usually works but there's some settings you might want to change
KThat's why its not reccomended
CKDE approximately starts with Gnome config files and then brute-force overwrites arbitrary parts of tens of files in arbitrary and hard-to-find places
Gbazzite-deck
KIts not tens, but its not zero either
CIt's hundreds if you count all of the garbage files KDE adds throughout the system
Ksudo rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck-gnome:latest
GWhat is that? Also i know nothing about linux
CI only know because I have tried to manually clean up that mess before, failed after several hundred changes, and reinstalled
CThe changes are irreversible and mangle Gnome's ability to function because they are not made correctly
KIf you know nothing than its better to just reinstall
KIts some dconf changes
Gis that the command?
Vyou can run
rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck-gnome:stable in the terminal, but people are writing already why you will have a bad time instead of just reinstallingGok
Vyes
KYes
KMy command is the correct one
KNot theirs
Vboth work
CYes, but theirs is "more" correct and better
KYes but your command is to rebase to unverified
K(plus it needs sudo but whatever)
Vit doesn't need sudo
KIt auto asks?
Vseems to work without it
Crpm-ostree does not need sudo
Costree does
AFyi very recent change
AAnd I think only for the update
Gso i should not do it
Abazzite-rollback-helper rebase bazzite-deck-gnome:stable should also work
LAnd only when locally invoked for that matter
CGnome will not look good or function correctly if you switch to it from KDE without reinstalling. With a professional software engineer's level of technical experience and 5 to 20 hours of dedicated effort, it can be untangled enough for either or both DEs to only seem slightly disfigured and broken. I do not recommend it
Abasically, config files from KDE stick around after a rebase, and it messes up Gnome
Aand it's a ton of config files that need to be fixed
Gyeah i only am used to windows also i am dual booting
Athe reverse also holds true, if you're on Gnome and rebase to KDE, Gnome config files mess with KDE
CNowhere near as much, but yeah
Abasically that's why rebasing between Gnome/KDE isn't officially supported
KTook me like half a hour and it was fine 100% I think
(But I have lots of experiance too)
(But I have lots of experiance too)
KIf this is your first time using Linux I reccomend reinstalling
Adid you manually partition bazzite during the dual boot setup?
Aif you did manual partition, it's actually pretty easy to reinstall bazzite without messing up dual boot
Ait's a bit more complicated if you did automatic partitioning
IThis was the issue that prevented me from being able to install Bazzite. Despite having a lot of storage, I needed about 50% of the partition to be able to do anything with it.
I reduced the root partition to my desire and will just add back the remaining space to windows post install.
Thanks, its weird how Bazzite is picky and wants to see 50:50 partitioning before allowing you to modify partitions or install.
I reduced the root partition to my desire and will just add back the remaining space to windows post install.
Thanks, its weird how Bazzite is picky and wants to see 50:50 partitioning before allowing you to modify partitions or install.
Gidk if you want i will send you the tutorial i watched
Awas it the retro game corp tutorial?
Athat was automatic
Anote that it's a bug, not intentional behavior
