Apologies if I’m the one that put the incorrect tags on here or closed the issue, wasn’t my intent. I’m still learning my way around the Debian bug system for the first time.
For me: I’m not using nvidia at all. I’m running Wayland on an AMD chip with integrated Radeon graphics and seeing this issue. I’ll look into the backports links you provided, thank you! Cheers, Matt > On Sep 2, 2024, at 2:27 PM, Nicholas D Steeves <s...@debian.org> wrote: > > Control: tag -1 upstream fixed-upstream moreinfo > > Matt Farmer <m...@frmr.me> writes: > >> Is there any hope of getting a backport / update of sddm 0.20 into >> bookworm anytime soon? Or potentially backporting whatever the actual >> fix was upstream to 0.19? > > Following the issue that Pierre linked to leads to this commit: > > https://github.com/sddm/sddm/commit/4913a3ee51c186937156635b70fa9b0db3e57c06 > > and that commit looks like a safe and correct enough, focused and > targeted fix; however, it appears to depend on a bunch of work (almost > certainly the WaylandHelper stuff) that will probably make a > stable-update infeasible. > > Is this a Wayland-specific issue, Wayland-on-nVidia, or nVidia-specific? > I'd like to see 2/3 of the participants in this bug reply with this info. > >> I see that trixie has a version that's behaving correctly now, but >> unfortunately trying to install that deb onto my bookworm system by >> itself yields some errors. (Which isn't totally surprising, by any >> means.) > > Correct, this is not the way ;) > > Here is a possible solution: https://wiki.debian.org/BuildingFormalBackports > > If someone builds a formal backport and wants other people to benefit > from their work, here are links that show how to achieve this: > > https://mentors.debian.net/sponsors/ > https://wiki.debian.org/DebianMentorsFaq > > Please keep this bug open as a breadcrumb trail for other bookworm > users. > > Regards, > Nicholas
