I PRed a shellcheck action but it went over like a lead balloon heh
I PRed a shellcheck action but it went over like a lead balloon heh
ZAlright so my only option to get a bit more proper colours on this display is to get a display calibrator
ZTo bazzite?
Jsome of the repos but it'd be nice to have them everywhere
ZIs the bazzite scripts not shellchecked?????
ZStop the presses, new CryoByte video
JI've looked at enough of the bazzite scripts to know that they're not all shellchecked, so if there's a way to make it happen automatically it would be a clear improvement.
ZI mean, shellchecking them using vscode is easy peazy
IHmm sorry to hear it is still crashing. Hideous tty is indeed a consequence of setting it to 0; on the bright side it shouldn’t be any worse than it was under 535? (At least that was the case for me) I believe you can set it back the way it was using kargs —delete=nvidia-drm.fbdev
IFor me I was completely unable to wake bluefin (GNOME) from sleep 100% of the time, and bazzite would refuse to let me past sddm like 60% of the time
PI can't seem to figure out how I'm supposed to edit my kernel cmdline? Do I just use grubby?
Erpm-ostree kargsI use
rpm-ostree kargs --editorShould've known it was handled by
rpm-ostree
SIt is the same as 535, I'm on Fedora Silverblue but I've realised a very custom system
SGDM on my end sometimes fails to start Wayland, only Wayland
SAnd yeah lock crashes Gnome Shell for but only after the monitors fully shut off
SI wonder if it might be related to having a dual monitor system 
SI remember at some point not having this issue but I can't quite put my finger on it
SOther than these 2 things the main remaining issues I have with Gnome on Nvidia Wayland is stream freezing on direct scanout (fullscreen games) and the stream in general having a very high CPU impact also creating some sort of constant frequent stutter
SThe correct term might be jidder but I'm not sure
PIs anyone aware of whether or not it's possible to add multiple custom modes to the same output via kernel args? Something to the tune of
video=<output>:<resX>x<resY>@<refreshrate>,<sameoutput>:<resX>x<resY>@<refreshrate>Kernel documentation didn't help me here
IYes, I should have specified: this was all under Wayland for me too, so at least there has been the fallback of X11
Pthis seems to work, if it's worth anything to anyone. I'm not doing any overclocking just adding resolutions that my monitor EDID lacks, despite supporting
CSince you're on @KyleGospo - I just got a new monitor and am testing out various games with 535/545. I'm having pretty horrific performance issues with specifically Dyson Sphere Program on both, with or without VRR/Freesync enabled, and different proton versions don't seem to help much. Different resolutions and refresh rates don't help, and the game seems to not be using system resources right when this monitor is plugged in, with or without another monitor. Any ideas for parts of the tech stack I haven't tested, or things which just aren't there yet upstream which could be causing this?
CAlso: the system copy of Prompt is working now
KThat's very strange, I'm afraid I have no idea where to even start on that one
KThat I'm glad to hear, it's like we thanks to us building it against stable GNOME rather than the nightly flatpaks
CGotcha
CAlright, I'll keep looking into it 
BAnybody have issues with fullscreen games on bazzite gnome? They lag like crazy until you make them windowed. I've had this issue with Civ 6 as well as Red Dead Redemption 2.
BIt's really frustrating. If the fullscreen window isn't focused, it's perfectly fine, but as soon as I focus it becomes unplayable.
BEven in the gnome overview the fps smooths out nicely, but then plummets when you open the game again
BI might rebase back to silverblue-main and see if I still have the issue.
F@EyeCantCU I'm testing your latest changes to flatpak-setup & this is what I see.
grep command outputs nothing, with either remove or install list.
INSTALL_LIST=$(echo $FLATPAK_LIST | grep -vf - $INSTALL_LIST_FILE)
INSTALL_LIST=$(echo $FLATPAK_LIST | grep -vf $INSTALL_LIST_FILE) #it should be like this
REMOVE_LIST=$(echo $FLATPAK_LIST | grep -f - $REMOVE_LIST_FILE)
REMOVE_LIST=$(echo $FLATPAK_LIST | grep -f $REMOVE_LIST_FILE) #it should be like this
while it should output Gnome Web in Remove list (on my system).
When setup is ran, it still installs everything, but flatpak has check for installed flatpaks, so it skips it.
grep command outputs nothing, with either remove or install list.
INSTALL_LIST=$(echo $FLATPAK_LIST | grep -vf - $INSTALL_LIST_FILE)
INSTALL_LIST=$(echo $FLATPAK_LIST | grep -vf $INSTALL_LIST_FILE) #it should be like this
REMOVE_LIST=$(echo $FLATPAK_LIST | grep -f - $REMOVE_LIST_FILE)
REMOVE_LIST=$(echo $FLATPAK_LIST | grep -f $REMOVE_LIST_FILE) #it should be like this
while it should output Gnome Web in Remove list (on my system).
When setup is ran, it still installs everything, but flatpak has check for installed flatpaks, so it skips it.
FI will try alternative with awk or sed
FI see the error, you added additional "-" where it's not needed.
Now with it removed, it outputs things normally
Now with it removed, it outputs things normally
FHmm, it still doesn't work well, now it deletes everything. I understand why
I solved the remove issue by including -o (only show matches, I would apply this to both install & remove)
but grep -vf doesn't work for some reason at all for install.
I uninstalled Calculator, but it does not appear in grep -vf for install
As far as I'm reading, grep -vf sometimes doesn't work with some piped commands. It's probably the case here with "flatpak list --columns=application"
I solved the remove issue by including -o (only show matches, I would apply this to both install & remove)
but grep -vf doesn't work for some reason at all for install.
I uninstalled Calculator, but it does not appear in grep -vf for install
As far as I'm reading, grep -vf sometimes doesn't work with some piped commands. It's probably the case here with "flatpak list --columns=application"
ZDoes Bazzite/Fedora Silverblue do anything with efibootmgr to re-add Windows on boot?
EIf the list is empty it falls back to the other command
EWill update the remove list as well
Fyes, I solved that issue I had.
the only thing remaining I can't solve is grep -vf not working with "flatpak list --columns=application" for flatpak removal. It outputs nothing while it should.
the only thing remaining I can't solve is grep -vf not working with "flatpak list --columns=application" for flatpak removal. It outputs nothing while it should.
FI originally wanted to work a bit on default-flatpaks module because currently in bling, you have to manually start flatpak-setup by deleting state version file for new changes.
With just this 1 issue remaining to be solved, I could ditch that state version file concept & enjoy in automatic update of default-flatpaks.
With just this 1 issue remaining to be solved, I could ditch that state version file concept & enjoy in automatic update of default-flatpaks.
EDo you have those Flatpaks installed?
EIf not, it should be empty
Fi have
EIt should use the same logic I added to install then
EAnd fallback to the whole list
EWill get that up momentarily
EIt only runs once anyway so it won't be problematic
