yea as said I find upstream stuff where Fedora users have the same issue

Can confirm this happens on my system too.

Confirmed the bug still exists with the latest plasma update on unstable

It's solved now.

@Girtablulu this sounds like an upstream bug?

I can confirm the issue, desktop compositing is being disabled.

libavif patch here: D10857

Yea can add this on the next update, was actually waiting for someone requesting this because need to package libavif. Gonna add libheif support as well

There is also HEIF support: https://invent.kde.org/frameworks/kimageformats/-/blob/v5.80.0/CMakeLists.txt#L57

You're welcome, glad it helped.

My system didn't have /etc/kernel/ directory, but creating one and following your instructions has solved my issues. No more flickering or incorrect resolution upon reboot.

What you could try is forcing the mode for the displays. Or try to generate a proper edid and override that in the kms/kernel.

In T9640#182907, @STiAT wrote:

I'd be interested in if (in plasma) ALT-F2 + "plasmashell --replace" actually remedys the issue for the current session or if you get those issues even replacing the plasma sesssion, since that would be kwin issues then (kwin_x11 --replace)

Thanks for response.
Running "plasmashell --replace" seems to have no positive impact, however running "kwin_x11 --replace", whilst not setting everything to a normal state, at least enables more resolutions on a second screen and so I'm able to manually set it to 1920x1080 without having to reboot or mess with (un)pluging of cables or turning monitors on and off. Do you have any suggestions on how to narrow down potential kwin issues?
And to reiterate, the majority of issues aren't present with the LTS kernel.

Hi there,

I asked nathan when it's going to be fixed but it seems a fix is incoming :)

do you have autologin active?

1- ran eopkg check (sddm, breeze-icons, noto-sans-ttf and linux-firmware were broken and repaired)
2- tried to print a pdf : it worked...
3- tried to print the pdf I had problem with : unable to print (I have other pdf files I can't print so it's not just one file)

I gave it a quick test and everything is working, please check via Termial that you are really up to date sudo eopkg up and check for broken packages sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall and reinstall them

this surprises me because it was just a rebuild against our new tooling, gonna have a look later the day

@AlekEagle This is a Solus bug tracker, not Kubuntu's. There are many many differences in the versions, configurations, and integrations of the packages available to both distros. Unless someone can reproduce this on an up-to-date version of Solus, this Task will remain closed. Closing tasks which have not seen any activity in several months is a normal process on the bug tracker and helps us to ensure active support requests get more attention.

I'm running 455.38 for steam support. I'm even more perplexed considering this was a fresh install of Kubuntu 20.04 that I grabbed on the 25th.

@AlekEagle Well, we are on 460.32.03 and Plasma 5.20.4 (.5 in Unstable). I'm especially perplexed that your Plasma version is that old; 5.19 landed in July 2020.

I am on 455.38 and plasma 5.18.5, with the same issues, KDE plasma lock screen continues to freeze on lock.

Oh, this is my task. I guess I'll take the initiative :P

This can definitely be closed. They fixed it in framework 5.74 and we're now on 5.77.

No crashes here using Wayland. Give the age of this task, it's probably safe to close it.

We are on newer versions of nvidia and plasma, please reopen this if you still having the issue

It's not like I totally forgot that one last week and have it ready for plasma 5.20.2 update need to check some last bits for it but nothing major

wait what how is this even possible? oO

due no response since 2 years and having multiple DE's installed which I dont suggest and support I gonna close it

This has sat in accepted for inclusion for over 30 days. Clearly, there is a lack of demand for the inclusion of this software, nobody has stepped up to provide a completed patch, maintain it, and properly integrate it. Closing as a result. Feel free to reopen but only when someone offers a patch via our proper patch submission methods and volunteers to be maintainer.

56790c5337af

yea can have a look, just hope I dont need to create a patch...

R3756:efa9409d1390a78dd89f666a74021ceac8873d91

Yep "Always check if Firefox is your default browser" is enabled. Pretty sure "always check" is enabled by default. I knew I could make it stop asking me. I just thought you might like to know the issue exists. :)

can you go under firefox settings and check if you have ask always reg default browser? normally you set firefox as default via the plasma settings

@clivejo kup (kernel) hasn't seen a release in 3 years so wouldn't be eligible for inclusion anyways. If people need it, they can install it themselves. If they are using ypkg to build it, they will find out soon enough that there's a name conflict and adjust accordingly. We cannot and should not base package naming decisions on something that doesn't exist in the repo at the time of Request.

seems to cause no issues anymore going to re add it