Wayland and Plasmashell are spamming my syslog

Help
1

My syslog is 700,000 lines over 36 hours. 500,000 come from kwin_wayland. Where can I turn down the logging for these spammy servers?

/home/phord» cut -d\  -f5 /var/log/syslog | cut -d"[" -f1 | sort | uniq -c | sort -rn | head -5
 520958 kwin_wayland
 143737 plasmashell
  64290 kded6
  13181 plasma-discover
   3929 kscreenlocker_greet

It’s possibly my own fault because I was debugging some keyboard quirks last year. But if I’ve set any setting to enable these logs, I can’t find it now to turn them off. Is there an simple way to query dbus for non-default settings?

The logs I’m seeing from kwin_wayland are showing input events for every mouse event and every keyboard event. Here’s a small sample:

Sep 16 14:01:14 phord-x1y5 kwin_wayland[1337]: kwin_effect_mousemark: MouseChanged QPointF(4528.55,2002.01)
Sep 16 14:01:14 phord-x1y5 kwin_wayland[1337]: kwin_effect_mousemark: MouseChanged QPointF(4532.55,1995.35)
Sep 16 14:01:14 phord-x1y5 kwin_wayland[1337]: kwin_effect_mousemark: MouseChanged QPointF(4534.98,1991.71)
Sep 16 14:01:14 phord-x1y5 kwin_wayland[1337]: kwin_effect_mousemark: MouseChanged QPointF(4537,1989.68)
Sep 16 14:01:14 phord-x1y5 kwin_wayland[1337]: kwin_effect_mousemark: MouseChanged QPointF(4538,1986.68)
Sep 16 14:01:14 phord-x1y5 kwin_wayland[1337]: kwin_effect_mousemark: MouseChanged QPointF(4539,1985.68)
Sep 16 14:01:14 phord-x1y5 kwin_wayland[1337]: kwin_effect_mousemark: MouseChanged QPointF(4539,1984.68)
Sep 16 14:01:17 phord-x1y5 kwin_wayland[1337]: kwin_effect_mousemark: MouseChanged QPointF(4539,1984.68)
Sep 16 14:01:17 phord-x1y5 kwin_wayland[1337]: kf.globalaccel.kglobalacceld: Processed key "T" , current sequence "T" = "(no shortcut found)"
Sep 16 14:01:17 phord-x1y5 kwin_wayland[1337]: kf.globalaccel.kglobalacceld: Got unknown key "T"
Sep 16 14:01:18 phord-x1y5 kwin_wayland[1337]: kf.globalaccel.kglobalacceld: Processed key "A" , current sequence "T, A" = "(no shortcut found)"
Sep 16 14:01:18 phord-x1y5 kwin_wayland[1337]: kf.globalaccel.kglobalacceld: Got unknown key "A"
Sep 16 14:01:18 phord-x1y5 kwin_wayland[1337]: kf.globalaccel.kglobalacceld: Processed key "I" , current sequence "T, A, I" = "(no shortcut found)"
Sep 16 14:01:18 phord-x1y5 kwin_wayland[1337]: kf.globalaccel.kglobalacceld: Got unknown key "I"
Sep 16 14:01:18 phord-x1y5 kwin_wayland[1337]: kf.globalaccel.kglobalacceld: Processed key "L" , current sequence "T, A, I, L" = "(no shortcut found)"
Sep 16 14:01:18 phord-x1y5 kwin_wayland[1337]: kf.globalaccel.kglobalacceld: Got unknown key "L"
Sep 16 14:01:20 phord-x1y5 kwin_wayland[1337]: kf.globalaccel.kglobalacceld: Processed key "Right" , current sequence "A, I, L, Right" = "(no shortcut found)"
Sep 16 14:01:20 phord-x1y5 kwin_wayland[1337]: kf.globalaccel.kglobalacceld: Got unknown key "Right"
Sep 16 14:01:20 phord-x1y5 kwin_wayland[1337]: kf.globalaccel.kglobalacceld: Processed key "Return" , current sequence "I, L, Right, Return" = "(no shortcut found)"
Sep 16 14:01:20 phord-x1y5 kwin_wayland[1337]: kf.globalaccel.kglobalacceld: Got unknown key "Return"

The spam from plasmashell seems to be application-specific (maybe slack). Is there some general way I can curtail those logs, too?

1 Like
2

You can use kdebugsettings gui application, to see which debug settings you have on.

1 Like
3

It turned out to be partly caused by a debug build of libinput I installed when I was helping track some bug there a year ago. I installed the distro package to replace it, and the problem went away.

2 Likes
4

This helped, because I found some custom rules that turned on debugging, probably from some long-forgotten command I played with. I need to explore more, but this helped me get started.

5

I have the opposite problem where I don’t get log entries from KWin script and was hoping that changing log level for KWin Scripting entry from Warning to Full Debug would enable these log entries but it didn’t help. I’m investigating the problem in No log entries after turning "Debug new Windows" option on · Issue #94 · anametologin/krohnkite · GitHub

6

You can use this tool both ways.

7

That’s what I thought too so I changed KWin Scripting log level from Warning to Full Debug, removed custom rule *.debug=false and restarted computer but this didn’t help.