Bug 460381

Summary:	Key bindings for root user are used instead of local user
Product:	[Plasma] kwin	Reporter:	kyrawertho
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	nate
Priority:	NOR
Version First Reported In:	5.26.0
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description kyrawertho 2022-10-13 16:50:45 UTC

SUMMARY

My custom keybindings are no longer working. Instead, I have to run systemsettings5 as sudo to change the keybindings.

I believe there may be other settings used from superuser as well because the cursor randomly changes to the default cursor instead of my own in some applications.

ADDITIONAL INFORMATION
Operating System: KDE neon 5.26
KDE Plasma Version: 5.26.0
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 5.4.0-128-generic (64-bit)
Graphics Platform: X11

Comment 1 Nate Graham 2022-10-14 19:06:59 UTC

> Instead, I have to run systemsettings5 as sudo to change the keybindings.
This is a symptom of a deeper problem, and doing this is highly likely to have caused even bigger problems for you that will be difficult to recover from.

What did it start happening? Did it start happening right after you did anything specific?

What custom keybindings are we talking about; how *exactly* did you set them? Which page in System Settings?

Comment 2 kyrawertho 2022-10-14 19:42:14 UTC

Specifically, I am using Flameshot (screenshot app) instead of the default Spectacle when pressing Print Screen.

Since this week's updates, it looked like my keybindings were correct but it started Spectacle again for making screenshots and it ran this as root.

The keybindings are in systemsettings > Shortcuts.

It looks like the issue has been resolved after rebooting (although I had to re-assign the keybindings). Still, it could seem like a security issue (?)  The cursor thing is still happening though, I don't know if it is related or possibly a Firefox issue (that's where it occurs).

Comment 3 Nate Graham 2022-10-17 18:51:52 UTC

> It looks like the issue has been resolved after rebooting
Yeah, when you update without rebooting, bad things like this can generally happen. Glad rebooting fixed it.