I have issues with steam flickering like crazy and discord as well, displaying the characters I type
I have issues with steam flickering like crazy and discord as well, displaying the characters I type out of order
BGitHub
Bumps Wandalen/wretry.action from 2.1.0 to 3.4.0.
Commits
0dd1d5d version 3.4.0
8e449ec Merge pull request #156 from dmvict/master
050710d Update action files, add option steps_context, update fi...
Commits
0dd1d5d version 3.4.0
8e449ec Merge pull request #156 from dmvict/master
050710d Update action files, add option steps_context, update fi...
DI really want X11 to die and Wayland to be successful, I just have issues on Wayland on my desktop still
Jwith 40 and nvk?
DNot nvk
DNvidia proprietary driver
DI tried to switch to nvk once and my system didn't boot
DThe discord issue completely disappears in X11.
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:testing
Digest: sha256:7abdc682980cd850a6dd6653ad4cae3daf85cf4dd350e4d98e509db7748563e5
Version: 40.20240419.0 (2024-04-19T23:01:15Z)
LayeredPackages: plasma-workspace-x11
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:testing
Digest: sha256:7abdc682980cd850a6dd6653ad4cae3daf85cf4dd350e4d98e509db7748563e5
Version: 40.20240419.0 (2024-04-19T23:01:15Z)
LayeredPackages: plasma-workspace-x11
B@j0rge you merge these instead of using merge queue?
J@bsherman the minder thing from stacklok will let us do sha pins and upgrades instead of version numbers
Jqueue doesn't work right with dependabot
Bwill be interesting to start working with that
DDon't get me wrong, I'm on team Wayland here, and want to switch to it 100%. It works amazing on my laptop with hybrid graphics, and on my steam deck, and on my other laptop with Intel graphics...
DNvidia when you don't have hybrid graphics is frankly awful right now
Jdid you layer what you needed?
DI layered the X11 package to see if that fixes my issues, and it does
DMy suggestion is to layer plasma-workspace-x11 by default in the bazzite nvidia images
DBecause the experience right now is regrettably so much better
Jif the layer works for you then that seems like a fine workaround?
DFor me, sure.
BI'd like to see bazzite specific requests (and likewise aurora/bluefin specific ones) sent to their respective discord channels... there seems to be a decent number of help question asked here... and I know this is more of a feature suggestion than "help" but I tend to see them as the same given the specific target image.
@j0rge if we don't intend the current channels to support the respective dev chatter, we could add some> just my thoughts...
@j0rge if we don't intend the current channels to support the respective dev chatter, we could add some> just my thoughts...
DMaybe do bazzite-dev
Dbluefin-dev
Jsgtm
Detc
JI'm not doing bluefin dev, I'm fine with the content in there like it is.
Dfair enough
Bso see my general comment above... it does relate to your suggestion, but there are many suggestions in this channel i would see similarly.
this suggestion specifically though, it's not up to me or jorge, etc... it's pretty much up to Kyle and those he works with to make those decisions
this suggestion specifically though, it's not up to me or jorge, etc... it's pretty much up to Kyle and those he works with to make those decisions
Jbut bazzite-dev seems necessary since that will be the majority of the users here pretty soon so we should split that before release
Bseems reasonable
Jbut IMO posting a thread in the forum with the workaround seems fine
JIt's not our fault a company with a 2 trillion dollar valuation can't get it together.
MLayering is a thing and it is a valid way to resolve this issue
DI agree with that ^ but they are at least trying
Dnew explicit sync patches should make things tolerable soon
Jalright then, we should be fine by the end of the F1 season, perfect. 
BI actually suggest the idea of building a custom image (see https://github.com/ublue-os/image-template) with such modifications as you are asking for here, then it's pretty clear to show a developer (eg, Kyle) "Hey look, this is what i did to solve problem X)
Bi gotta step away again for family stuff
Kback sorry
Kyeah that's expected, KDE 6.1 is supposed to fix
Kwhich should be in F40 before release
Kif we still have flicker on 6.1 I will add x11 packages, without question
Kotherwise that's gonna be an exercise for the end user until it dies for real in F41
DIsn't 6.1 out in June?
KKDE 6.1 is in testing right now for F40
MFair point. Layered packages missing are a pain
DAre we referring to different things? Here (https://community.kde.org/Schedules/Plasma_6) it says it hasn't branched yet.
DAnd won't until May
DNot trying to be antagonistic just confused
Kyea likely, package I'm looking at w/ the patch will be versioned 6.1
J
