mutter-common-46.0-xscaling.1-1.fc40.noarch mutter-46.0-xscaling.1-1.fc40.x86_64
mutter-common-46.0-xscaling.1-1.fc40.noarch
mutter-46.0-xscaling.1-1.fc40.x86_64
mutter-46.0-xscaling.1-1.fc40.x86_64
KOk, that's the working copy supposedly
KHmm
Ntotally does i am trying to avoid the typical carousel workflow that every install has as i find it annoying ;p
DLet me try KDE and see if it boots
DBluefin's F40 worked FWIW
SYeah I see, I like these menus so I could just go straight to what I want and do things in the order I want. It's just the apply part I'm not so sure of in the design ^^
Dwhich mutter patches are you applying?
Dbazzite KDE boots just fine for me
KXwayland fractional scaling, which was working
KTriple buffering
KAnd Nvidia copy fix
KThat's all
Dcopy fix -> explicit sync?
KThink it may be related to me also offering mutter-common
KAs precious tests were fine
KNo that's already included
KThe copy fix is for dual GPU laptops and it causes a 50% drop in performance
DI thought that wasn't landing in this gnome version
KSo that's nice to have
DHow the hell is the triple buffering fix still not merged?
DPhoronix has been writing about that MR for years
Ni can try to add some coloring and move it to the bottom see how that feels
SMaybe, that could help
Dhttps://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_2039296
I guess this will land in 47
I guess this will land in 47
GitLab
Use triple buffering if and when the previous frame is running late. This means the next frame will be dispatched on time instead of also starting late. It...
RAnyone else dislike how GitHub Actions handles martixes?
All I need is to output a list of tags generated in the reusable build workflows. But nope. Why would that be easy?
All I need is to output a list of tags generated in the reusable build workflows. But nope. Why would that be easy?
BThey aren’t my favorite but I’ve gotten a feel for them
RTomorrow I'll pick on you to help generate an array of images built by the reusable workflow then 
Jok colin braindump incoming ... just got home so decompressing but wanna get some notes out
Jdiffs will be worked on, they just need multi-team work, (down to the podman/skopeo bits, not just ostree)
Jwe're probably more aligned with coreOS than the rest of fedora on some things, especially the bit with the kernel cadence we wanna do for bluefin, along with a weekly cadence for gts.
Jsysexts got a nice +1, he's a fan
Jthere's things we could be doing but don't have time/cycles for that would be really useful for them upstream - I'm thinking things like powerwash, etc. and the thing bsherman fixed, that kind of stuff
Jlots of the the things that are useful, like local layering etc. bring along a ton of tech debt, all the rpm stuff, etc. Moving to a pure bootc thing will take time, but I'm keen on helping push this more by leveraging systexts and brew so that users don't need to rely on local layering.
Jother than that, the same things as discussions with others, silverblue/kinoite needs more help upstream, lack of resources and developers all around for everyone
Jhe wasn't aware about all the stuff ucore is doing, so I put it on his radar.
Jalso found out that I'm copresenting with him at rh summit, so we're going to meet a few more times and get some slides going
Bjust put it in the SBOM thread and we can discuss
Jooh can someone tldr me on the sbom stuff?
J
Jlol THREE YEARS AGO
DBazzite should probably add plasma-workspace-x11 to kde images until the nvidia issues are fixed.
DDon't get me wrong, I love the idea of wayland and want it to succeed. But the issues are still numerous on Nvidia hardware
Byou have an opinion that...
D?
KIs this still an issue with the flicker patches in place?
Kactually hold on, can't answer that
Kthey're coming with KDE 6.1
Kwhich is in testing for F40 right now
KI will only add that package if the flickering still occurs on 6.1
Kif it does not, I'd rather let the 1980s remain in the 1980s
