I'm afraid I don't have one to test against, but I will get back to you on that
I'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?
Kas soon as prompt has a stable release I can MR it
Ksince none of this stuff points to the .Devel namespace
ZIm excited!
A@EyeCantCU still feeling a bit weak so might have to postpone the work until tomorrow 
ESorry to hear that, but sounds good. I'll have a look over things today to get an idea of what would need to be done. Hope you start feeling better
AWe need to do the following:
1. Modify this guy to have a flatpak ref/flatpak apps as input parameter: https://github.com/ublue-os/lorax-compose/blob/main/action.yml
2. Modify this guy to add the Lorax template for flatpaks: https://github.com/ublue-os/lorax-compose/blob/main/mkociso
3. Wire the inputs from the action into the Lorax template
1. Modify this guy to have a flatpak ref/flatpak apps as input parameter: https://github.com/ublue-os/lorax-compose/blob/main/action.yml
2. Modify this guy to add the Lorax template for flatpaks: https://github.com/ublue-os/lorax-compose/blob/main/mkociso
3. Wire the inputs from the action into the Lorax template
GitHub
Contribute to ublue-os/lorax-compose development by creating an account on GitHub.
ESweet! I'll get to work on that after lunch! Thank you so much
B@EyeCantCU @akdev I’ve been only partially keeping up with the flatpak on image stuff. What’s the TL;DR? Do we just want to prove it can be done? Is it all about shipping Prompt pre-release?
K
ANo, it’s just the same way fedora SB does it
AI don’t know what Bazzite wants to ship but in general just seems like missing functionality we have been putting onto yafti
Kwould love to use whatever upstream does eventually
FIn yafti & default-flatpaks module
This is something I'm excited about
This is something I'm excited about
Kfor now our flatpak manager works
BAh, cool. You figured out how they do it so we can pre bundle a few desired flatpaks which will still be removable/upgradable by a user?
That’s pretty cool!
That’s pretty cool!
Kit'll retry until everything in the list is installed
Kso that's all we need
AYeah
EEven after installer support is there, I think the flatpak manager will certainly still be useful. Especially for people that rebase to the image
E@akdev I think this handles 1 & 2. Looking into 3
https://github.com/EyeCantCU/lorax-compose/commit/b95263cb6c492cdb307b7ef26348b0780e78d6c7
https://github.com/EyeCantCU/lorax-compose/commit/b95263cb6c492cdb307b7ef26348b0780e78d6c7
FIt would be nice to contribute this to startingpoint once it's done
AThat looks right, maybe it should be an option that can be specified multiple times?
ECan certainly look into that
JYES!!!!!!
B@j0rge @Marco could one of you make the blincus repo public please?
