Definitely the way forward. I want to sit down and work out a working GitHub action
Definitely the way forward. I want to sit down and work out a working GitHub action
AWe just need to add that Lorax templates and some wiring up to mkociso then the GitHub can do it
AMm I think I can work on this tomorrow
EWould really appreciate that. Will help in any way I can
AI’ll ping you for review and we can adapt Bazzite to use it as first consumer
KGitHub
Adds support for Prompt, a new terminal emulator flatpak.
KThen we can ship that in place of the gnome terminal only Nautilus extension
KLeaves it open for tons of choices
JYESSIR
JI'm all in
KKSettings for this are all dconf, default is gnome-terminal
K
FWould be interested on how would it coexist with default-flatpaks
I guess normally, without any issues?
I guess normally, without any issues?
Xyeah, probably
B@Marco @j0rge i sent a request through github to authorize cloudflare pages for the new blincus repo, if that's cool with y'all, it needs approval to proceed. domain will be
blincus.dev
Buntil then it's serving off the zimaboard in my laundry room, and... it doesn't suck tbh https://blincus.dev/
Blincus
Create isolated development environments for your projects quickly.
MWill take a look!
Bthank you!
Mdone
Bthank you, sir
Mfor working around SELinux issues. Is it frowned down to copy things to mutable locations (/usr/local/bin), set the correct context and restorecon. Then bind mount back over the incorrectly labeled binanry? This could be done via systemd oneshot like the ublue-nvidia service?
KKLogo menu
BQuestion: it seems that the HDR patches in the kernel will cause gamescope to fail on vega based graphics, was wondering if any of you guys tried running the HDR patches on a vega machine already?
KI'm afraid I don't have one to test against, but I will get back to you on that
BI don't know if you use the exact kernel that nobara uses, but GE was at least able to repro on a vega based laptop
KDo you have functioning frame rate control and refresh rate changing on your end? That's our remaining bug
BFrame rate control requires mesa patches
KWe essentially do, fsync and Nobara share patches
KYeah, those we have. But with the newest update specifically for the OLED the frame rate control broke and changing refresh rate causes the screen to black out
BHmm I have not seen this on my end, it works for me
KInteresting
BDon't know what the diff is between our stuff, maybe good to look into
KYeah I might just do that today
KAny chance you have a log of that crash you're getting?
BOnly issue I have with the frame limiter is that 60FPS gets me 30FPS. All seem off by factor of 2
KIs this with a 120 hertz display?
BWe don't carry all the oled patches yet
KI've seen this behavior on high refresh rate monitors
BJup
KYeah, I actually saw a workaround today where you just lie to gamescope and pass it double the refresh rate
KI haven't tested that in practice yet though
BYeah steam also only goes up to 60 in the non-unified slider for me. But I thought that was our gamescope-fork being weird
KThey broke something when they added 90 Hertz support for the OLED
KIt affects upstream too
BI'm running an older gamescope 3.13.16-plus1, maybe that is related then. When did it get introduced on your side?
KI want to say 3.16, but that might be too new
KI'd have to go back and check
K@j0rge
ZWhen are we going to see this in all images?
