https://bugs.kde.org/show_bug.cgi?id=427861
--- Comment #105 from ratijas <m...@ratijas.tk> --- > I don't see any other errors and I see that on every change I make I've > getting "Unable to assign [undefined] to QString" or "Unable to assign > [undefined] to Int" from various libraries, depends on the widget, so I think > that should point to something? Of course they should be fixed at some point, but they are [[mostly harmless]]. Unlike binding loops, "Unable to assign [undefined]" kind of errors are usually just the results of races in component initialization code, technically speaking, like, when one property wants to evaluate its bindings, but not all of dependecies in such expression are ready yet. Eventually it re-evaluates when they become ready, and everything settles down. But again, of course should be fixed, because such noise makes it harder to spot the real problem. Back on topic: maybe you somehow managed to enable the "kiosk mode"? It's a thing where a user is denied most forms of interaction and customization. And until very recently there was a pretty undocumented shortcut which could be silently triggered on a Plasma Desktop to lock it down. There is some info on where to find those settings: https://develop.kde.org/deploy/kiosk/introduction/ -- You are receiving this mail because: You are watching all bug changes.
