I also want to generalize initial output description to being setup with a list of parameters and reading in config files in json format (and falling back to KScreen config files; that way we wouldn't have ugly mode switches on startup

I can do, but I'll explain my rationale for this first.

Instead of emitting cursorChanged from DrmBackend, modify SceneOpenGL to connect Platform::cursorChanged as opposed to Cursor::cursorChanged to the cursor texture update function.

more hacks

It seems we can get the correct path via the _rels file as per
https://en.wikipedia.org/wiki/Open_Packaging_Conventions

Running kcmshell5 icons style was a good suggestion.

remove hardcoded value

update

That framework change is released tomorrow, right? Is it worth reverting?
Including this, that's at least the second regression it's caused, which makes me worry there's even more we haven't found.

I really don't know that sharing model between contexts cause a such behavior.

Maybe change the subject line to start with [kcmkwin/kwindecoration] though we don't have a very good policy on this.

and removed the paddings from this patch's main.qml.

What problem are we solving?

It already says "Command line" in the group title on the left a console icon and unlike apps has the prefix "Run "

remove a stray newline

add a const

Ship it.

whitespace

fix obvious typo

Looks good.

If the only usage is the SNI model lets just rebuild the model on the ConfigEntries side.
You're right that sharing objects between contexts seems to cause issues.

Can you explain what you're working around?

Even if it did load MainToolbar icon size, why does that make them invisible as per the bug report?

fix copy pasta out of virtualbox

Yeah, and now you mention it the entirety of the xdgOutput setting is missing on construction too.

CI is now good to go.

Is it worth putting this in 5.15?

Why do we ever need to use a translated version?

Seems better, but I'm not sure I understand exactly.

Is this patch acceptable

(but who uses kcmshell anyway?).

FWIW, currently it'll only affect the lock screen as SDDM doesn't have any code (yet!) to enable software rendering.

Wait a few days. Frameworks tagging is the first Saturday of the month.

(the panel should be at the bottom of the screen; notifications should appear in the bottom right corner of the screen)