Bazzite 41 testing branch feedback
Feel free to add your testing feedback on here, so we don't make a thread per tester
ROG Ally Z1E - bazzite-deck:testing-41.20241026 - KDE - so far no issues.
216 Replies
ROG Ally Z1E - bazzite-gnome-deck:testing-41.20241026 - can't switch to desktop; first attempt straight back to game mode after entering pin, second attempt black screen for a couple of minutes then pin screen and back to game mode, third attempt "verifying installation" then pin and back to game mode. Second reboot, switch to desktop shows verifying installation and straight back to game mode.
EDIT: Secure boot enabled and MOK enrolled
@hamido Ctrl alt f5
To access the terminal
Then type that command
Yep on it
16db07b8
https://paste.centos.org/view/16db07b8
Funny
@Kyle Gospo gnome deck is busted
Homed still has selinux errors
Ok hopefully you don't need to use desktop for a few hours
Although rippling snake rested gnome
Do you use extensions?
I do
Just default installed ones, tiling etc I haven't installed any extra ones
Yeah the default are fine
I'm on holiday so I don't actually need the thing to work but happy to test and help resolve any issues as and when I can
If any broke that's Kyle's problem
I'm a senior dev (backend) and I'm Linux based so shouldn't need to explain too much to me, I'm just new to container/layered OSs (used NixOS a bit before)
I'm not a fedora user though I'm a Debian user so not super familiar with the tooling
Oh in that case maybe you can figure it out
I'm having to view the log on mobile which isn't the best, I can see a few permissions issues, selinux stuff and some complaints about files not found
There is a gnome crash 3/4 in
Also looks like systemd-homed is being denied read access to home
Selinux policy issue i think
HHD also dumped its core
No access to home could cause both of those I imagine
The hhd-ui crashes when I ask for the version
I don't know why and at this point I don't care
It's just ugly
Fair enough
Electron weirdness about not being connected to a display
Ah
I don't see the grub menu on boot despite not hiding it either...
It's never shown for me
Yeah there are some selinux issue
About that
You can use ostree to chAnge the default deployment
So you don't need grub
I think esc makes it show
Yeah standard desktop way, how do I switch with ostree? Don't see it on the doc page in reading, just says how to pin
I don't need to rollback at the mo, happy to keep it "broken" to test for now, but just so I know for future
Rpm ostree rollback swaps to the previous
Although it may have been a karg swap
I see set-default too
Ok, rolled back and desktop is up again
Send another log
To crosscompare
No selinux weirdness
@Robert (p5) any ideas about ublue sulogin and /var/lib selinux?
Seems like selinux lost its /etc override
No idea unfortunately. I've got a custom build which doesn't depend on ublue. Anything you want me to check so we can narrow it down to either ublue or upstream?
Selinux
Did something happened to the /var override
I can't see anything weird on a non-ublue image. But to be honest, I'm not too sure what I'm looking for π
/var/lib/selinux exists and I use rechunk
Not sure if this matters, about a module license tainting the kernel...
Also don't know if this is expected, maybe because they're mount points?
Desktop with Geforce 1050 TI - bazzite-nvidia:testing-41.20241026 - KDE - get a blank screen with a blinking cursor in the top left of the screen, I can get into desktop with CTRL+ALT+F2, log in and launch desktop with
/usr/bin/startplasma-wayland
. Can get past the issue by turning on autologin. Looks like something is weird with SDDM, getting a core dump when systemd trying to load sddm https://paste.centos.org/view/1e7820de. Same issue on my Nvidia laptop (Geforce 930M)Also I have secure boot enabled
Is ok
If it's only on one of the logs it's not oj
Seems like selinux is sho5
I haven't compared them sorry, on holiday and looking at logs on mobile so it's hard to compare
Interesting that it works for @wolfyreload on the same device
You seem to be on Gnome and I'm on KDE. Think thats the difference
Aha, did I list the wrong image?
Can double check with
rpm-ostree status
if it's bazzite-gnome-deck then you on gnome bazzite-deck is kdeI'm definitely on bazzite-gnome-deck
I just wrote the wrong image name in my first post in the thread
@antheas I have a spare SSD drive lying around, would there be any benefit to putting gnome on it and seeing if I get the same issue an hamido?
maybe maybe not
first we need to fix the selinux issues
ok setroubleshoot is just broken and needs a patch
Just off out for the day, can test anything you need when I get back later
ROG Ally Z1E - bazzite-deck-gnome:testing-41.20241026 - Gnome - So I installed bazzite-deck-gnome on an external drive, rebased to testing and not getting issues. Gamemode and Desktop mode working fine. My ISO was an older gnome deck ISO. So I'm going to try a new installation with the latest ISO on the website, rebase and see if I can reproduce
I'm back if there's anything to test
The only modification I can think of is that I installed a package with brew, not sure how brew works on bazzite and whether it affects layering
My image was downloaded about 2-3 days ago so it's new
We will have a lot of fun on Tuesday
π¬
I'm not sure if I'm just imagining it but performance seems better in gaming. I'm playing aperture desk job, I'm set to Silent/10W in HHD and I'm getting ~80FPS, sure I was getting much lower on 40/stable
Perhaps yeah it's a newer kernel
New mesa too
Custom build?
ostree native
most likely
Just my own OCI image derived directly FROM quay.io/fedora-ostree-desktops/silverblue
Helps check whether issues are also present upstream and I can make more intrusive changes.
ah it's OCI
Just saw the unstable with selinux troubleshooter fix, should I try rebase to unstable and test it?
that was a harmless error
but maybe rebasing will help
I just tried installing bazzite-deck-gnome from iso and rebasing to testing. Unfortunately, I cannot reproduce the issue that hamido is getting. On the plus side I am set up to test both gnome and kde for the Rog Ally for other testing π
Ok rebasing to unstable still no desktop
How weird. I wonder what's different about mine? Secure boot? Some ujust script I've run such as Waydroid?
Gsconnect?
its something completely random that only happens to 10% of users and we will find out when its way too late
My Secure boot is on but I didn't have waydroid installed.
Launchpad
Bug #2081728 βStartup crash (meta_seat_impl_run_input_task) with......
[ Impact ]
GNOME Shell Wayland sessions crash on startup if Mouse Keys (and other?) accessibility features are enabled. This seems to affect a large number of people:
https://errors.ubuntu.com/problem/8a95f1902f49fc831d4bee942899ed1239896c64
[ Test Plan ]
1. Enable Mouse Keys: Settings > Accessibility > Pointing & Clicking > Mouse Keys = ON
2...
Let me try that.
find the gconf setting for it so we can make it a command
org.gnome.desktop.a11y.keyboard enable true
@Kyle Gospo we have a custom gnome shell right?GitLab
seat-impl: Initialize the impl reverse pointer slightly earlier (!4...
While it is eventually initialized in meta_seat_native_constructed, that's now too late since
there is an MR here
I've tried using gsettings to turn off mode keys like suggested, no change
can you give it one more shot and turn off all accessibility settings and reboot
this error looks like what you have
the stack trace is the same
How do I turn off all accessibility settings?
thats a very good question
Go back to the working base?
yeah sounds the easiest
I did turn on the OSK once actually, but it's off, all accessibility settings are currently off
Can reproduce a crash in gnome-deck:testing if I turn on Mouse Keys, like you mentioned in that article. When trying to go to desktop, booted back to gamemode
I'll toggle them all on then off and try again
theres an MR after we merge it it will prob work
Will that go to unstable if I just rebase to unstable again?
Yes
Fixed
Toggled this off then updated back to unstable
Kyle will look into merging that im sure
@Kyle Gospo here
How do I rebase to bazzite 41?
I believe it's newer kernel might fix an annoying issue I have with bazzite atm
bazzite-rollback-helper rebase testing
nvm i figured it out
thank you anyways!
hopefully it fixes my issue :3
π€
its ass is imaging βΌοΈ
omg it removes Xorg <3
i love this OS alredy
hades isnt launching on the testing branch βΉοΈ
and my issue in https://discord.com/channels/1072614816579063828/1299415224285135040 still persists :/
And how often is it is that an issue is there for ublue but not your image
Not often at all. There were more instances at the beginning of ublue, but now we have testing branches and everything's a lot more stable.
The last time was some issue with font cache in Bluefin over a year ago
I guess this instance might also be one, since the issue was with a login script we've added ourselves (don't fully understand the issue though)
@hamido @wolfyreload patched matter is live
Mutter?
its been a long day
just finished the announcement draft
yea
Indeed. Is there a gui button to update or do I need to ostree it?
if youre in unstable press teh button
GitHub
Release unstable-41.20241026.2: Unstable (F41.20241026, #c57a8a1) Β·...
This is an automatically generated changelog for release unstable-41.20241026.2.
Visit bazzite.gg for more information and to download Bazzite.
From previous unstable version unstable-41.20241026.1...
look how nice this looks lol
even has a rebase command now
The button? Is that the one in system in game mode?
yea
Love that the change log has the commands now :chefs_kiss:
Updated, restarting then I'm off to bed
Hmm, accent colour is working now, sure that wasn't working on stable/40
Loads of gnome extensions seem to be incompatible at the moment, no logo menu π
No GSConnect
accent color is headline feature
kyle will figure out the extensions
does the crash still happen tho?
all but gsconnect work now
Do you want me to turn that toggle back on to test?
gsconnect will likely work before launch
yea
How? They say incompatible in the extension manager
Still crashes π
Turned the toggle on, logged out, then tried to switch to desktop and it won't load
I don't have access to a keyboard until morning to get the journalctl log
huh?
Some of them are fine like Blur my Shell and Caffeine
All the stock ones that aren't in my screenshot
logo menu was updated
it's got gnome 47 marked
so does compiz
you have some weird shit going on there
the only extension in your entire list that isn't updated is gsconnect
I have them all working on 4 different devices right now
I've been back and forth between stable, testing and unstable to test this desktop crash, haven't changed anything else. Anyway, I don't have desktop access now until I get a keyboard tomorrow, turning on the accessibility toggle still breaks desktop on the latest testing/unstable build for me
in steamui, whats the build id
Just rebooting one sec
It's the wrong one, e339195
Why's it not gone to latest when I hit update? Do I need to change OS update channel to beta?
dunno
Hmm, can't get it to update from steam UI, keeps saying there's an update after I install it and reboot, but it's on the second to last build not the last
broke whoopsies happens
tomorrow is another day
Indeed, just wanted to check for you that the crash was fixed
appreciate it
but youll need to go into desktop
or tty
I grabbed the keyboard π
gimme a sec
Ok, updated, no desktop crash, it's working. Extensions still broken though
maybe it needs time to connect to the internet
tomorrow is a day too
extensions are in-image
thanks for checking
youre cooked
user is experiencing a bug
they are the only person to report it so far
maybe its the mutter version?
no
you bumped it
I am on the same image
no issue
extensions only check full gnome version
48?
47
well lucky you then he fell on both so you can fix them before tsuesday
Logo Menu, for example, says it's version 32, but if I click through to details it says 35
Magic lamp is 19, but 20 in details
Window effect 24, 25 in details
Upgrade assistant shows them all as compatible, so this menu on the extensions manager seems to be seeing separate info to upgrade assistant
Looking in
/use/share/gnome-shell/extensions
, the extensions are out of date, logo menu is showing version 32 / 23.2 which is compatible with gnome 46.Hope that helps. Off to bed for real now.
Upgraded to 9266bf8 and extensions are fixed. Night all!
(except game achievements, that's still broken, but I don't use it)
achievements are steam tho
Double checked on my ally. (bazzite-deck-gnome:unstable-41.20241027 af5e53c) All extensions working, including my user installed ones Dash to Panel, ArcMenu and Desktop Icons NG. And can't reproduce the accessiblilty desktop issue anymore. All looks good
I'm not sure what you mean sorry. What I meant was the gnome extension called "Game Achievements" was / is still showing as not compatible, though all the other extension are now fine.
Is the system update button supposed to work in game mode when I'm in testing branch? It doesn't seem to update, it asks me to reboot and when I do I'm back on the same version. Only way I can get it to update is to press the system update button in desktop mode that opens the terminal and shows all the things it's updating then asks me to type r to reboot
The os release drop-down says "Release Candidate" but whatever I change it to it goes back to RC
It's supposed to update
Hmmz I've tried it half a dozen times and it's not updating, it shows updates available, but after apply and reboot it's on the same hash/id
It's supposed to
Sometimes it doesnt
And we need to fix it
All good, just trying to report anything I find that doesn't seem right.
Is there a way I can view a log for game mode to see what might be going wrong? Or is it a known issue?
dunno and yes its a known issue
the steam updater is whack
Fun
Hey, is it possible that the openrazer kernel modules haven't been updated to 3.9.0 yet? When I tried to install openrazer via
ujust-install openrazer
it complained about an outdated python version. So I used sudo rpm-ostree cleanup -m
and tried it again. It installed fine now, but I'm getting "Linux detected connected devices but the daemon didn't. This could be either due to a permission problem or a kernel module problem." in RazerGenieshould be there
Okay, I'll try to figure out what's the issue then.
thanks btw
I'm out of my element here, but from what I see the kmod comes from here
https://copr.fedorainfracloud.org/coprs/ublue-os/akmods/package/openrazer-kmod/
, which clones from here https://github.com/ublue-os/openrazer
, which hasn't been updated to openrazer 3.9.0 yet. That's why my mouse hasn't been detected. Is there a way I can report it. Should I even report it?
bazzite-latest uses 3.9.0, but the kmod doesn'tYou're confusing me
Openrazer updated and our repo is outdated?
the kmod repo is outdated yeah
@Kyle Gospo will fix it
okay, thanks!
you can report it here
https://github.com/ublue-os/akmods
GitHub
GitHub - ublue-os/akmods: A caching layer for pre-built Fedora akmo...
A caching layer for pre-built Fedora akmod RPMs. Contribute to ublue-os/akmods development by creating an account on GitHub.
thank you
It's it normal to see the mouse cursor on desktop when I'm not in mouse mode? It always seems to be hovering over the keyboard messing up my input. Which brings me to another issue: keyboard on desktop sometimes stops inputting (quite frequently) and I have to hide and show it again.
Not certain these are issues in testing but I don't recall them in stable in the short time I was on it
KDE?
kde is the same version on both
Gnome
Have you forgotten the Gnome extensions debacle already π
im juggling 10 devices in my mind rn
No worries, I'm just playing.
How does one help out and join the testing branch?
you can rebase to the testing branch with this terminal command
bazzite-rollback-helper rebase testing
. You can switch back to stable with the command bazzite-rollback-helper rebase stable
Just updated to the latest testing branch build and it's been trying to boot for 10 minutes now, was looping with what looked like a kernel panic for a while, then it's been on "verifying installation" for about 5 minutes
verifying installation is steam
means your steam install took a dump, nothing more
boot to desktop and see if you can get steam to launch there
control + alt + f4
steamos-session-select plasma
Just switched tty gonna grab a log
I'm on Gnome
same command
Ok
It's really slow, struggling to login to a tty
Maybe you're running out of battery
My battery was very low, it's plugged in at the moment
It hit 0% then I plugged it in, started the update when it was about 5%
Exactly
Ally bug
Does it have some performance limits in Firmware when the battery is low?
Yea
Awesome π
Triggers the safety of the processor
And only stops when you shutdown
Then it starts trying to hibernate the system
But Linux is like what's that
Hah ok
I'll reboot
Shutdown/power on
One of those days, phone is about to run out of battery, ally out of battery, vape out of battery, and they all need the same charger cable π
Yikes, still shutting down. How robust are these immutable OSSs to just pulling the plug?
very
So just power cycle it, no big deal?
no biggie
libostree is intended for this
I kinda gathered that might be the case, thought I'd ask though
Booted in seconds this time
Can ignore my earlier message @Kyle Gospo about boot issue on the latest, user error; wasn't aware of the battery level issue until now
took a long while to boot into desktop mode on my steam deck. gtk apps also lost their theme and defaulted to light mode
oh wow everything kinda reset
wallpaper is gone and my screenshot bind no longer works
no idea what's going on here
flameshot is completely broken too
wow theming is all jank
this is also weird, I use to be able to use hotkeys with KDE's shortcut settings but now it's saying my compositor doesn't support hotkeys??
also holy crap steam's UI just increased like 4x
overall performance is more or less the same tho
https://paste.centos.org/view/b7d052c8
just a bunch of overall weird issues on the desktop
seems my binds work perfectly its just flameshot is completely borked, wont capture my screen at all
doesnt even pop up
like always tho it games flawlessly
Firefox is in light mode somebody send help
go into settings and change it?
flatpaks are weird about following system theme and dont always "follow"
yeah but I'm just pointing out how in the testing branch the "system" theme for gtk apps are light now instead of vapor
Nearly immune
Congrats on the release. π
I'm on a train at the mo, just woke the Ally up after sleep and the performance is atrocious, switching tdp in HHD making no difference, seems like it'll need a reboot.
Any know issues with sleep?
I also couldn't connect my Bluetooth headphones until I went to desktop and toggled Bluetooth off and on again, then back and they showed up in the list (already paired)
Rebooted and I'm back at ~100 FPS in space marine vs 11 FPS before reboot
You ran out of battery again probably
Or had it do ked
We're looking at this bug
Bios update might help
I put it to sleep when I went to sleep, it was on 100%, woke it up ~5 hours later when I woke up, it was at 96% and running terrible
Can I update bios without windows?
Yea
Do they provide downloads or does it have network update in bios?
On a train to work at the mo and only have my work laptop which I can't use to do it so I'll have to wait till I'm home tonight if it doesn't have network update
Leave it now just reboot
Yeah, I rebooted and it's been playing fine
Aaand that's the battery done π
so im not on testing but i got the update today? the desktop was weird at boot and dark mode is now broken
also the file picker changed, for the worse
You're gnome or kde
Sounds like gnome
yeah
Welcome to gnome 47
Kyle will check the dark mode if it's broken
Because he themes it I guess
π is kde generally more stable/reliable on bazzite? or its just... shit happens?
Potato potata, each have their own issues
I switched from Bazzite KDE to Bazzite Gnome because KDE was buggy as fuck for me, Gnome is much better when it comes to stability. But idk it may be my specific hardware or something.
k thx, im gonna stick with it then.
What device are you on?
Desktop. I meant that maybe it's just some combination of my CPU, Nvidia GPU etc. that makes KDE less stable. I mean, it's not like it was unusable. Only encountered on really breaking bug which I was able to fix, but there were small issues am basically non stop. System apps not opening, Krunner not working, widgets disappearing and changing positions, theme switching to default, monitor keept changing 165 to 120 Hz after every login etc. Tons of little, but annoying stuff.
Did you try x11?
It works better on NVIDIA
But X11 is removed on F41 anyway. I would probably have to layer it back or something, not really worth the hassle when Gnome works anyway.
Oh ok
I try to install bazzite-deck:testing into MSI Claw device
In lastest testing update kernel 6.11.5-307
Device not sleep (LED power always ON and CPU fan still working)
Wifi not work when device woke up.
Kernel Log here
https://pastebin.com/enrx3wH5
Pastebin
MSI Claw A1M-Bazzite OS kernel log - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
wifi device : Intel(R) Killer(TM) Wi-Fi 7 BE1750x
oh btw the bug that the gnome interface is sometimes flipped 180' after coming back from standby is still present
but is it tracked, cant find the issue on github
GitHub
Issues Β· ublue-os/bazzite
Bazzite is a cloud native image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices - including your favorite handheld. - Issues Β· ublue-os/bazzite
we dont even support the msi claw yet so keep those reports to #Attempt to add MSI Claw support? so that its in the same place since it is a work in progress. thanks π
there's minor support now but it's very much suffering from those issues