The upstream bug was resolved in Plasma 5.27 via https://bugs.kde.org/show_bug.cgi?id=414559

@dinhnamhihi, is this still an issue? It has been a long time since there was an update to this task, and there have been many updates since this issue was opened.

Were you the user with the very old GF GT220 generation card using the nouveau driver?

@jedibrooker, is this still an issue? It has been a long time since there was an update to this task, and there have been many updates since this issue was opened.

Closing due to lack of response

On the 4.4 test ISO OpenCL has a similar error that clinfo is required to display this page, but could not be found

@livingsilver94 , is this still an issue?

Re-opening since the page still does not load.
There is now the error "The fwupdmgr tool is required to display this page, but could not be found"

Still needs D13506 as well

Thanks @joebonrichie!

I'm not sure, but I think I tried Alt+F4, Alt+F5 and all hotkeys I know. They didn't help. And 5.15 too. But I tested Mint with Cinnamon and MATE, Neon, AntiX and LXLE. They just work.

Are you able to switch to an alternate TTY (ALT+F4 or similar)? Also, you reported on the forum that the 5.15 kernel is good for you right?

In T9922#200947, @TClark77 wrote:

FWIW there is nothing currently in the Akonadi docs saying you shouldn't use sqlite. It was there in the past. https://techbase.kde.org/KDE_PIM/Akonadi#Why_not_use_sqlite.3F
Here is where they removed it: https://techbase.kde.org/index.php?title=KDE_PIM/Akonadi&curid=6207&diff=106967&oldid=106854

This documents where the change from MariaDB to SQLite can be configured by the user without changing the defaults:

FWIW there is nothing currently in the Akonadi docs saying you shouldn't use sqlite. It was there in the past. https://techbase.kde.org/KDE_PIM/Akonadi#Why_not_use_sqlite.3F
Here is where they removed it: https://techbase.kde.org/index.php?title=KDE_PIM/Akonadi&curid=6207&diff=106967&oldid=106854

vulkaninfo is provided by vulkan-tools. waylandinfo should be provided by wayland-utils, which isn't in the repos, but shouldn't be too hard to build.

Did a system update with the rebuilds included. This bug is resolved.

It's been fine for me since the update to kidletime.

Maybe working now after the rebuilds?

This doesn't appear to be fixed. There is no change in behavior on my system after a system update. I verified I have the updated kidletime package installed.

Note that the KDE case was closed, citing it as a downstream packaging issue.

Resolved by R4028:2828e84186c3: Update to 5.1.3.

I dont have the issue. @livingsilver94 opened this issue.

@clauded Is this still an issue? If so could you record a short video of the issue?

https://dev.getsol.us/R3428:edcaff198e92e49e93c140104c428fa11168c00b

Is this still an issue in unstable?

Update to 2022.4 D13538

Sorry I've missed a few releases now, let me get the latest release out and hopefully it fixes this issue on KDE

Fixed by https://dev.getsol.us/R2462:7cb4b521241f64939e6ba69166bf185b613c1a29

I figured it would. Go ahead and close this then (I don't have permission to do so).

It looks like polkit 121-26-1 in unstable fixes this issue.

I already have this locally if Girt accepts

Neochat didn't support encryption. But all my chats are encrypted. So Element is the only option in Solus. Or you decide to build Cinny :)

I'd suggest using neochat on plasma, as it's the KDE version of element

Neither can I in Budgie.

I just restart and check it. The globe offers me Deutsch, and it's already preselected. If I type with the help of the virtual keyboard, I can log in with the correct credentials.

on the virtualkeyboard there should be a globe symbol, can you click this and check if Deutsch is mentioned?

Hi, here comes the screen output of locale at my system:

This is working fine for me on two systems. can you check with the terminal command locale if everything is setup to the same language?

This is an upstream issue, we have to wait till it get fixed there

I need to rebase out polkit-noscript branch on the latest polkit release. Let's see where we land after that.

@clauded that makes sense because they all rely on polkit.

we build this now with llvm and qt6

I also experience the bug no. 3, that is, the transparency effect doesn't work in any application that uses the Hamburger menu (Dolphin, Gwenview, and Okular). This bug is reported on the KDE site:

@livingsilver94 I think it makes sense as long as it works.

No, nor it was my intention. I think the plan is OK and I'm waiting for the green start working on it.

Nope, no dice for me.

mmmh @livingsilver94 and @clauded can you please remove ~/.cache and reload the theme? I cannot reporduce any of the issues

Most likely they introduced new theming stuff, which I need to look at