Last *tiny* issue with bazzite-deck is that it has a *lot* of SDDM entries
Last tiny issue with bazzite-deck is that it has a lot of SDDM entries
VIs there any way to slim those down?
BI've just rebooted, and Wayland session just turns my displays off... As if it was going to sleep.
BLooking at journalctl it looks like kwin_wayland is just stopped
BAnd shortly afterwards a bunch of selinux errors
VShoot, don't think it is
VMight make a custom image...
Vbazzite-deck-desktop kekw
Bor maybe sddm is broken..i dont even know anymore... i can manually run
startplasma-wayland and it all works fine, but breaks when launched via sddm
Hyep sadly and those sddm entries are
gamemode, desktop (x11, desktop (wayland), firstboot (x11), firstboot (wayland) i believe
VYep, and they're in /usr/ 
Hyep
VIt's ok though! Been wanting to make a custom image and this is a good excuse
Hfirstboot ones are required i believe
Hor oneshot or whatever they are called
VIf I make it boot to SDDM would they still be?
Vfirstboot
VI'll take a look through the repo to see what I can do, anyway.
VGonna make the first wayland-only ublue image
Hbazzite boots into the X11 desktop on first boot for you to run portal, after that its gamemode (or desktop wayland if you ran
ujust autologin)Hand currently i am the only person with a system with non functional X11 
Hmy setup is cursed
VI'll see what I can do, ideally I'd just want it to go to SDDM on first boot
VWith 3 SDDM options for X11, Wayland and Game mode
Hyou will have to make edits to prevent the oneshots to be a requirement then, essentially overwrite the files that run the oneshot session on first boot and make sure you keep track of when those are updated upstream with incompatible changes
Hno idea where those said files are since i dont interact with that
VYeah I'm counting on needing to do that. I'll figure it out.
Bweird ...apparently lsmod is missing
H????
Bcan you do
which lsmod ?Bi might have messed the PATH up
Hmake sure you are not in a container
Bwhich is what i want to check
Bi am not
H
H
Blooks like my $PATH is messed up
Hthat would do it
Bthe problem is finding out where it messed up
Bi had an entry for spicetify in my .bashrc and .bash_profile
Hdefault is
$HOME/.local/bin:$HOME/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbinBmine is
/home/bingham/.local/bin:/home/bingham/bin:/home/bingham/.volta/bin:/home/bingham/.spicetify:/home/bingham/.cargo/bin:/home/bingham/.local/share/gem/ruby/3.0.0/bin:/home/bingham/.volta/bin:/bin:/home/bingham/.local/bin:/home/bingham/.volta/bin:/usr/local/bin:/usr/binHyoure missing everythingin sbin
Bi dont think over than the spicetify stuff i have anything playing with the $PATH
Hwhenever i update path i always do
export PATH="/new/path:$PATH"Bspicetify did it automatically as
PATH=$PATH:/home/bingham/.spicetifyHno idea what removed it then
Bso, i did a few things, mostly just remove the spicetify path and removed any zsh config and now it works?
Bi dont know what even happened there as half of the folders didnt exist
Bi did find a random xsess-env file in /tmp that i also deleted
