Autorepeat rate and delay in KDE suddenly excruciatingly slow

seth · 2022-09-06 19:51:14

https://wiki.archlinux.org/title/CPU_frequency_scaling
Essentially compare

cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq

now and when things go down, BUT: this would not explain why restarting kwin/replacing it w/ openbox would remedy the situation.

cfr · 2022-09-07 00:10:01

seth wrote:

https://wiki.archlinux.org/title/CPU_frequency_scaling

My apologies, but why would that cause Xorg/kwin_x11/plasmashell/etc. to take a greater % of CPU cycles when booted on AC/when on AC? Assuming the frequency would be scaled down on battery versus AC?

All my bugs are eluding me today. My battery readings seem sane. I'm almost reassured to be told fan2 is running at 65535 rpm as usual. (fan2 works incredibly hard despite being a figment of linux's imagination.)

seth · 2022-09-07 06:14:06

My apologies, but why would that cause Xorg/kwin_x11/plasmashell/etc. to take a greater % of CPU cycles when booted on AC/when on AC? Assuming the frequency would be scaled down on battery versus AC?

To have a bigger share of the cake, either Xorg got hungrier or the cake shrunk.
(Xorg might not take more CPU cycles, but your system got slower and doesn't wake out of the lowe power state)

cfr · 2022-09-08 14:08:36

Thanks for the explanation.

It doesn't seem to be stuck at a lower frequency. Xorg is currently using enough to make typing painful but not excruciating.

cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq 
2700000
2984681
3100012
3026277

When I woke the system a couple of minutes ago

On battery earlier (low Xorg madness; yesterday, I think)

On AC yesterday (Xorg usage low)

Maximum CPU frequency is

I'm using the intel_pstate driver and it is using the powersave governor. I believe that's probably normal? The firmware settings are set for performance on AC and balanced on battery, but I've read that the intel_pstate thing can override those anyway (and they don't correspond exactly to the available governors for sure).

'pkill xembedsniproxy' has marginal, if any effect on Xorg usage and doesn't affect typing in any discernible way.

'pkill plasmashell' (after killing xembedsniproxy) increases Xorg's CPU usage, if anything. (I doubt it really increases it, but it certainly doesn't decrease it.)

'kwin_x11 --replace' works nicely, thank-you!

One way I can push up Xorg usage is to hold down a key. That is, if I have 'top' open in one window and type a lot of 'k's, say, in another, Xorg usage temporarily jumps massively. I realise it might push it up a bit, but should it add 20% to the % CPU usage?

seth · 2022-09-08 14:35:55

One way I can push up Xorg usage is to hold down a key. That is, if I have 'top' open in one window and type a lot of 'k's, say, in another

What if you press "k" nowhere (or some key that won't trigger a response)?
I'd rather assume this to be down to the repaints of the terminal, but even then this isn't normal and points to a problem w/ either the terminal emulator or kwin.

There's another thread that might or not be related: https://bbs.archlinux.org/viewtopic.php?id=279468

cfr · 2022-09-08 23:42:54

seth wrote:

One way I can push up Xorg usage is to hold down a key. That is, if I have 'top' open in one window and type a lot of 'k's, say, in another
What if you press "k" nowhere (or some key that won't trigger a response)?

Of all the dumb questions I have to ask, this has to be the dumbest. How can I do that? If I focus on the desktop, KDE immediately interprets whatever I type as input to the 'command line' (which I think means krunner?). I thought I could just switch this off, but I can't even figure out how to do that. (I'm sure this used to be possible in system settings and maybe it still is, but I can't find it.)

seth wrote:

I'd rather assume this to be down to the repaints of the terminal, but even then this isn't normal and points to a problem w/ either the terminal emulator or kwin.

I used the same emulator in openbox, so it would have to be the emulator in combination with something else, I think. (Although admittedly I didn't run this specific test in openbox.)

seth wrote:

There's another thread that might or not be related: https://bbs.archlinux.org/viewtopic.php?id=279468

Hmm. It's hard to tell, but the fact that turning off the compositor at least masks the issue in my case, while that thread is on a machine where the compositor isn't being used (because it stops the computer being turned off?) ... but they could both be caused by something crazy happening with repainting the screen? Or focus? I don't think mine can be to do with focus switching, but I may not have understood the suggestion.

I do see what I think is a repainting issue in kile, where a distorted remnant of a contextual menu stays around after the menu is closed. It doesn't actually affect kile's window, but the desktop to the side. (So if I had kile horizontally maximised, I don't think it would be visible.) I can exorcise the ghost by focusing on that part of the desktop. So if I keep a window open behind kile, I can hover the mouse over the other window and clear the ghost without having to click away from kile. (This is less annoying than having to switch virtual desktops or click on the desktop, and I usually have okular behind kile anyway.) I don't know if this problem occurs in openbox because I used kile horizontally maximised there. (Initially, openbox made the window so huge most of it was horizontally inaccessible and I think I maximised it horizontally to reduce it enough to be usable.)

EDIT: I could just kill it?

Last edited by cfr (2022-09-09 00:00:57)

seth · 2022-09-09 06:55:03

this has to be the dumbest. How can I do that?

No, it's not.
You need to find and focus a window that simply ignores keyboard output.
Or make one:

xev -event keyboard > /dev/null 2>&1

(the keyboard event handlig is to make sure that it reads the events and then we just redirect the output to nowhere)

I don't think mine can be to do with focus switching

That lead nowhere in the other thread either

It doesn't actually affect kile's window, but the desktop to the side.

That's not a problem w/ kile, but the desktop shell (plasma) - and your graphics driver.
https://wiki.archlinux.org/title/Intel_ … RI3_issues or possibly PSR/FBC (on the same wiki, disable them)
Or the compositor (in which case this would not happen w/ the compositor disabled)

Initially, openbox made the window so huge

The window size is usually requested by the client, openbox might not chose to sanitize it.

Edit

EDIT: I could just kill it?

Errr… kill what?

Last edited by seth (2022-09-09 06:55:33)

cfr · 2022-09-09 23:22:46

xev -event keyboard > /dev/null 2>&1

Thanks. This has no effect on Xorg usage. (Actually, it drops a bit.) I checked right before that I could still get Xorg to increase dramatically by typing lots of some character into another terminal window, so there's definitely a difference. I'm guessing this is kwin?

It makes sense if openbox doesn't sanitise the window sizes but kwin does. It's partly that things are bigger in openbox (fonts, icons), but that wouldn't explain the truly enormous width of kile's window.

seth · 2022-09-10 06:27:55

I'm guessing this is kwin?

If the compositor is relevant, otherwise it's the mere repainting of the terminal emulator (what might be down to it not being very efficient at that - tried xterm?)

Did you ever trigger the original problem during a session where the compositor was disabled the entire time?

cfr · 2022-09-15 21:50:25

seth wrote:

I'm guessing this is kwin?
If the compositor is relevant, otherwise it's the mere repainting of the terminal emulator (what might be down to it not being very efficient at that - tried xterm?)

I suspect the compositor. I'll try xterm to test, too. I've also not tried all of the intel things yet. xorg usage has been going up more slowly and not staying as consistently at the highest levels, so it's taking me longer to try things out. (I suspect the variation is some random factor or a matter of my usage of different applications or something.) I don't really see the sticking-around-menu problem when xorg usage isn't high. I've not reproduced it on the last kwin_x11 run even though xorg usage went pretty high (high 50s to 100%). I suspect it may be a side-effect of the main problem, but I don't really understand enough to be able to have sensible suspicions.

seth wrote:

Did you ever trigger the original problem during a session where the compositor was disabled the entire time?

I've never tried this, but I've just restarted kwin_x11 with compositing disabled. (I really don't like not having compositing, so it's not something I'd usually try except to test. I've got a small screen and it's handy to be able to read one window while working in another.)

Before I replaced this kwin_x11, I tried typing lots of something into konsole with the compositor off. xorg CPU % drops and konsole's goes up to around 20%, but the speed is fine. I know the % is of total CPU usage, so, presumably, if there's not much CPU usage, even a small amount will show as a large proportion?

EDTI; kwin_x11 is very noisy. When started from the command line, this is most obvious. I'm not sure the output is relevant because it is noisy regardless. Here's a sample from it when compositing is disabled prior to launch:

kwin_xkbcommon: XKB: Unrecognized RMLVO option "terminate:ctrl_alt_bksp+eurosign:5+compose:caps" was ignored
kwin_xkbcommon: XKB: inet:323:58: unrecognized keysym "XF86EmojiPicker"
kwin_xkbcommon: XKB: inet:324:58: unrecognized keysym "XF86Dictate"
file:///usr/share/kwin/tabbox/informative/contents/ui/main.qml:123: TypeError: Cannot call method 'longestCaption' of null
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2803, resource id: 0, major code: 53 (CreatePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2804, resource id: 77594725, major code: 55 (CreateGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2805, resource id: 77594725, major code: 72 (PutImage), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2806, resource id: 0, major code: 53 (CreatePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2807, resource id: 77594727, major code: 55 (CreateGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2808, resource id: 77594727, major code: 72 (PutImage), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2809, resource id: 0, major code: 53 (CreatePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2810, resource id: 77594729, major code: 55 (CreateGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2811, resource id: 77594729, major code: 72 (PutImage), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2812, resource id: 0, major code: 53 (CreatePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2813, resource id: 77594731, major code: 55 (CreateGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2814, resource id: 77594731, major code: 72 (PutImage), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2815, resource id: 0, major code: 53 (CreatePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2816, resource id: 77594733, major code: 55 (CreateGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2817, resource id: 77594733, major code: 72 (PutImage), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2818, resource id: 0, major code: 53 (CreatePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2819, resource id: 77594735, major code: 55 (CreateGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2820, resource id: 77594735, major code: 72 (PutImage), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2821, resource id: 0, major code: 53 (CreatePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2822, resource id: 77594737, major code: 55 (CreateGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2823, resource id: 77594737, major code: 72 (PutImage), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2824, resource id: 0, major code: 53 (CreatePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2825, resource id: 77594739, major code: 55 (CreateGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2826, resource id: 77594739, major code: 72 (PutImage), minor code: 0
libpng warning: iCCP: known incorrect sRGB profile
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 10214, resource id: 54525958, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 11014, resource id: 16777409, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 52010, resource id: 77594818, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 52011, resource id: 77594818, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 52014, resource id: 77594818, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 52015, resource id: 77594818, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 10907, resource id: 77594823, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 10911, resource id: 77594823, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 10912, resource id: 77594823, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 11782, resource id: 77594828, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 11783, resource id: 77594828, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 11786, resource id: 77594828, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 11787, resource id: 77594828, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 12638, resource id: 77594833, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 12639, resource id: 77594833, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 12642, resource id: 77594833, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 12643, resource id: 77594833, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 16901, resource id: 77594838, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 16902, resource id: 77594838, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 16905, resource id: 77594838, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 16906, resource id: 77594838, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2373, resource id: 77594843, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2374, resource id: 77594843, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2377, resource id: 77594843, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2378, resource id: 77594843, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 4174, resource id: 77594856, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 4175, resource id: 77594856, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 4178, resource id: 77594856, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 4179, resource id: 77594856, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 8302, resource id: 77594869, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 8303, resource id: 77594869, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 8306, resource id: 77594869, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 8307, resource id: 77594869, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 59405, resource id: 77594887, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 59406, resource id: 77594887, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 59409, resource id: 77594887, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 59410, resource id: 77594887, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 12635, resource id: 16777272, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 19982, resource id: 77594916, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 19986, resource id: 77594916, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 41218, resource id: 77594929, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 41219, resource id: 77594929, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 41222, resource id: 77594929, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 41223, resource id: 77594929, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 43498, resource id: 77594934, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 43499, resource id: 77594934, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 43502, resource id: 77594934, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 43503, resource id: 77594934, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 44797, resource id: 77594939, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 44798, resource id: 77594939, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 44801, resource id: 77594939, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 44802, resource id: 77594939, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 51890, resource id: 77594952, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 51891, resource id: 77594952, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 51894, resource id: 77594952, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 51895, resource id: 77594952, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 63335, resource id: 77594957, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 63336, resource id: 77594957, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 63339, resource id: 77594957, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 63340, resource id: 77594957, major code: 14 (GetGeometry), minor code: 0
kwin_core: XCB error: 3 (BadWindow), sequence: 11262, resource id: 4194859, major code: 129 (SHAPE), minor code: 6 (Input)
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 11263, resource id: 4194859, major code: 2 (ChangeWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 54604, resource id: 77594991, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 54605, resource id: 77594991, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 54608, resource id: 77594991, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 54609, resource id: 77594991, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55523, resource id: 77594996, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 55524, resource id: 77594996, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55527, resource id: 77594996, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 55528, resource id: 77594996, major code: 14 (GetGeometry), minor code: 0

When I've seen what happens with no compositing, I'll try it with and see if the output is any different.

Last edited by cfr (2022-09-17 04:22:41)

cfr · 2022-09-19 23:12:04

seth wrote:

Did you ever trigger the original problem during a session where the compositor was disabled the entire time?

I don't usually do this, but I just tested this for a couple/few days and I didn't see the problem when I disabled the compositor in system settings before restarting kwin_x11.

I then turned compositing back on. Xorg CPU % increased a bit, as I guess would be expected. However, so far it isn't steadily increasing as it usually does, which seems odd. However, I'll need to test a bit more.

kwin_x11 --replace
kwin_xkbcommon: XKB: Unrecognized RMLVO option "terminate:ctrl_alt_bksp+eurosign:5+compose:caps" was ignored
kwin_xkbcommon: XKB: inet:323:58: unrecognized keysym "XF86EmojiPicker"
kwin_xkbcommon: XKB: inet:324:58: unrecognized keysym "XF86Dictate"
libpng warning: iCCP: known incorrect sRGB profile
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3173, resource id: 77594630, major code: 18 (ChangeProperty), minor code: 0
libpng warning: iCCP: known incorrect sRGB profile
OpenGL vendor string:                   Intel
OpenGL renderer string:                 Mesa Intel(R) HD Graphics 620 (KBL GT2)
OpenGL version string:                  4.6 (Compatibility Profile) Mesa 22.1.7
OpenGL shading language version string: 4.60
Driver:                                 Intel
GPU class:                              Kaby Lake
OpenGL version:                         4.6
GLSL version:                           4.60
Mesa version:                           22.1.7
X server version:                       1.21.1
Linux kernel version:                   5.19.5
Requires strict binding:                yes
GLSL shaders:                           yes
Texture NPOT support:                   yes
Virtual Machine:                        no
QObject::connect(KWin::InputMethod, KWin::EffectsHandlerImpl): invalid nullptr parameter
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 6919, resource id: 54526146, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 6976, resource id: 23069004, major code: 18 (ChangeProperty), minor code: 0
file:///usr/share/kwin/tabbox/informative/contents/ui/main.qml:123: TypeError: Cannot call method 'longestCaption' of null
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 45312, resource id: 16793108, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 45313, resource id: 16793108, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 45316, resource id: 16793108, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 48211, resource id: 16793560, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 48212, resource id: 16793560, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 48215, resource id: 16793560, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 48216, resource id: 16793560, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 16582, resource id: 54526000, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 22666, resource id: 54525963, major code: 18 (ChangeProperty), minor code: 0

Is it still worth trying the intel stuff or is that irrelevant if it's the compositor?

Last edited by cfr (2022-09-19 23:15:27)

seth · 2022-09-20 07:33:20

irrelevant if it's the compositor

Something in the compositor is probably really overusing the CPU by annoying the server.
Does it maybe creep up when you suspend to/wakeup from RAM?

cfr · 2022-09-21 01:09:35

seth wrote:

irrelevant if it's the compositor
Something in the compositor is probably really overusing the CPU by annoying the server.
Does it maybe creep up when you suspend to/wakeup from RAM?

I wondered about this, but I don't *think* so. Maybe a bit, but it certainly creeps up even if I don't.

Currently, though, it isn't creeping up and I'm not sure why. I'm even using inkscape and things are staying calm. Not only isn't it creeping up, Xorg CPU % isn't at the level it normally *starts* at in kwin_x11. It's currently varying between 0.7 and 1.3, whereas it usually begins significantly higher (in the teens).

But I've not changed anything. I've not even updated. It's as if there's some factor I'm just not seeing. And kwin_x11 is as noisy as ever.

EDIT: It still spikes massively if I type lots of something into konsole, for example, but it doesn't lag because the base % is low, I guess. It is increasing slightly now, but it's still below where it would usually begin when it settles down.

Last edited by cfr (2022-09-21 15:53:52)

cfr · 2022-09-25 00:05:10

seth wrote:

Does it maybe creep up when you suspend to/wakeup from RAM?

I can't say this is noticeable, but I'm wondering if there might be any hint in the journal from a suspend/wakeup cycle:

Med 24 07:09:22 MyName systemd-logind[486]: Lid closed.
Med 24 07:09:22 MyName root[76338]: LID closed
Med 24 07:09:22 MyName root[76340]: arg1 is button/lid, arg2 is LID, arg3 is close and arg4 is
Med 24 07:09:23 MyName kscreenlocker_greet[76342]: Qt: Session management error: networkIdsList argument is NULL
Med 24 07:09:25 MyName kscreenlocker_greet[76342]: kf.coreaddons.desktopparser: Error: Could not find [Desktop Entry] group in  "/usr/share/sddm/themes/sddm-stellar-theme//metadata.desktop"
Med 24 07:09:25 MyName kscreenlocker_greet[76342]: kf.coreaddons.desktopparser: Error: Could not find [Desktop Entry] group in  "/usr/share/sddm/themes/sddm-stellar-theme/metadata.desktop"
Med 24 07:09:25 MyName kscreenlocker_greet[76342]: kf.coreaddons.desktopparser: Error: Could not find [Desktop Entry] group in  "/usr/share/sddm/themes/sddm-stellar-theme/metadata.desktop"
Med 24 07:09:25 MyName kscreenlocker_greet[76342]: libpng warning: iCCP: known incorrect sRGB profile
Med 24 07:09:25 MyName kscreenlocker_greet[76342]: libpng warning: iCCP: known incorrect sRGB profile
Med 24 07:09:26 MyName kscreenlocker_greet[76342]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:8:1: module "QtQuick.VirtualKeyboard" is not installed
Med 24 07:09:26 MyName kscreenlocker_greet[76342]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: Unable to assign [undefined] to bool
Med 24 07:09:26 MyName kscreenlocker_greet[76342]: kf.coreaddons.desktopparser: Error: Could not find [Desktop Entry] group in  "/usr/share/sddm/themes/sddm-stellar-theme/metadata.desktop"
Med 24 07:09:26 MyName kscreenlocker_greet[76342]: kf.coreaddons.desktopparser: Error: Could not find [Desktop Entry] group in  "/usr/share/sddm/themes/sddm-stellar-theme/metadata.desktop"
Med 24 07:09:26 MyName kscreenlocker_greet[76342]: kf.coreaddons.desktopparser: Error: Could not find [Desktop Entry] group in  "/usr/share/sddm/themes/sddm-stellar-theme/metadata.desktop"
Med 24 07:09:26 MyName kscreenlocker_greet[76342]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: Unable to assign [undefined] to bool
Med 24 07:09:26 MyName systemd[1]: Reached target Sleep.
Med 24 07:09:26 MyName systemd[1]: Starting System Suspend...
Med 24 07:09:27 MyName systemd-sleep[76364]: Entering sleep state 'suspend'...
Med 24 07:09:27 MyName kernel: PM: suspend entry (deep)
Med 24 07:09:27 MyName kernel: Filesystems sync: 0.007 seconds
Med 24 07:09:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 07:09:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 07:09:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 07:09:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 07:09:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 07:09:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 07:09:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 07:09:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 07:09:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
Med 24 17:30:27 MyName kernel: OOM killer disabled.
Med 24 17:30:27 MyName kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Med 24 17:30:27 MyName kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Med 24 17:30:27 MyName kernel: wlan0: deauthenticating from 18:35:d1:c8:ec:09 by local choice (Reason: 3=DEAUTH_LEAVING)
Med 24 17:30:27 MyName kernel: e1000e: EEE TX LPI TIMER: 00000011
Med 24 17:30:27 MyName kernel: ACPI: EC: interrupt blocked
Med 24 17:30:27 MyName kernel: ACPI: PM: Preparing to enter system sleep state S3
Med 24 17:30:27 MyName kernel: ACPI: EC: event blocked
Med 24 17:30:27 MyName kernel: ACPI: EC: EC stopped
Med 24 17:30:27 MyName kernel: ACPI: PM: Saving platform NVS memory
Med 24 17:30:27 MyName kernel: Disabling non-boot CPUs ...
Med 24 17:30:27 MyName kernel: smpboot: CPU 1 is now offline
Med 24 17:30:27 MyName kernel: smpboot: CPU 2 is now offline
Med 24 17:30:27 MyName kernel: smpboot: CPU 3 is now offline
Med 24 17:30:27 MyName kernel: ACPI: PM: Low-level resume complete
Med 24 17:30:27 MyName kernel: ACPI: EC: EC started
Med 24 17:30:27 MyName kernel: ACPI: PM: Restoring platform NVS memory
Med 24 17:30:27 MyName kernel: Enabling non-boot CPUs ...
Med 24 17:30:27 MyName kernel: x86: Booting SMP configuration:
Med 24 17:30:27 MyName kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Med 24 17:30:27 MyName kernel: CPU1 is up
Med 24 17:30:27 MyName kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
Med 24 17:30:27 MyName kernel: CPU2 is up
Med 24 17:30:27 MyName kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Med 24 17:30:27 MyName kernel: CPU3 is up
Med 24 17:30:27 MyName kernel: ACPI: PM: Waking up from system sleep state S3
Med 24 17:30:27 MyName kernel: ACPI: EC: interrupt unblocked
Med 24 17:30:27 MyName kernel: ACPI: EC: event unblocked
Med 24 17:30:27 MyName kernel: i915 0000:00:02.0: [drm] [ENCODER:94:DDI A/PHY A] is disabled/in DSI mode with an ungated DDI clock, gate it
Med 24 17:30:27 MyName kernel: i915 0000:00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it
Med 24 17:30:27 MyName kernel: i915 0000:00:02.0: [drm] [ENCODER:118:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it
Med 24 17:30:27 MyName kernel: nvme nvme0: 4/0/0 default/read/poll queues
Med 24 17:30:27 MyName kernel: usb 1-7: reset full-speed USB device number 3 using xhci_hcd
Med 24 17:30:27 MyName kernel: usb 1-8: reset high-speed USB device number 4 using xhci_hcd
Med 24 17:30:27 MyName kernel: psmouse serio1: synaptics: queried max coordinates: x [..5712], y [..4780]
Med 24 17:30:27 MyName kernel: psmouse serio1: synaptics: queried min coordinates: x [1232..], y [1074..]
Med 24 17:30:27 MyName kernel: OOM killer enabled.
Med 24 17:30:27 MyName kernel: Restarting tasks ... 
Med 24 17:30:27 MyName kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
Med 24 17:30:27 MyName kernel: done.
Med 24 17:30:27 MyName kernel: random: crng reseeded on system resumption
Med 24 17:30:27 MyName kernel: audit: type=1130 audit(1664037027.223:1157): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=fangfrisch comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Med 24 17:30:27 MyName kernel: PM: suspend exit
Med 24 17:30:27 MyName kernel: Bluetooth: hci0: Bootloader revision 0.0 build 26 week 38 2015
Med 24 17:30:27 MyName kernel: Bluetooth: hci0: Device revision is 16
Med 24 17:30:27 MyName kernel: Bluetooth: hci0: Secure boot is enabled
Med 24 17:30:27 MyName kernel: Bluetooth: hci0: OTP lock is enabled
Med 24 17:30:27 MyName kernel: Bluetooth: hci0: API lock is enabled
Med 24 17:30:27 MyName kernel: Bluetooth: hci0: Debug lock is disabled
Med 24 17:30:27 MyName kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Med 24 17:30:27 MyName kernel: Bluetooth: hci0: Found device firmware: intel/ibt-12-16.sfi
Med 24 17:30:27 MyName kernel: IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:f696:34ff:fedc:aaf5 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=185 TC=0 HOPLIMIT=255 FLOWLBL=18333 PROTO=UDP SPT=5353 DPT=5353 LEN=145 
Med 24 17:30:27 MyName audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=fangfrisch comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Med 24 17:30:27 MyName systemd-logind[486]: Lid opened.
Med 24 17:30:27 MyName systemd[1]: Started Download unofficial clamav virus definition files.
Med 24 17:30:27 MyName dhclient[76459]: Killed old client process
Med 24 17:30:27 MyName systemd-sleep[76364]: System returned from sleep state.
Med 24 17:30:27 MyName root[76462]: LID opened
Med 24 17:30:27 MyName root[76475]: arg1 is button/lid, arg2 is LID, arg3 is open and arg4 is
Med 24 17:30:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName root[76479]: ACPI group/action undefined: ibm/hotkey / LEN0268:00
Med 24 17:30:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName plasmashell[12910]: QXcbClipboard::setMimeData: Cannot set X11 selection owner
Med 24 17:30:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName systemd[909]: Stopped target Bluetooth.
Med 24 17:30:27 MyName systemd[1]: Stopped target Bluetooth Support.
Med 24 17:30:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName root[76481]: arg1 is ibm/hotkey, arg2 is LEN0268:00, arg3 is 00000080 and arg4 is 00006032
Med 24 17:30:27 MyName plasmashell[12910]: QXcbClipboard::setMimeData: Cannot set X11 selection owner
Med 24 17:30:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName systemd[909]: Reached target Bluetooth.
Med 24 17:30:27 MyName systemd[1]: Reached target Bluetooth Support.
Med 24 17:30:27 MyName root[76489]: ACPI group/action undefined: ibm/hotkey / LEN0268:00
Med 24 17:30:27 MyName root[76493]: arg1 is ibm/hotkey, arg2 is LEN0268:00, arg3 is 00000080 and arg4 is 00006032
Med 24 17:30:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName kscreenlocker_greet[76342]: QXcbClipboard: SelectionRequest too old
Med 24 17:30:27 MyName systemd[1]: systemd-suspend.service: Deactivated successfully.
Med 24 17:30:27 MyName systemd[1]: Finished System Suspend.
Med 24 17:30:27 MyName systemd[1]: Stopped target Sleep.
Med 24 17:30:27 MyName systemd[1]: Reached target Suspend.
Med 24 17:30:27 MyName systemd[1]: Stopped target Suspend.
Med 24 17:30:27 MyName audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Med 24 17:30:27 MyName audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Med 24 17:30:27 MyName kernel: audit: type=1130 audit(1664037027.810:1158): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Med 24 17:30:27 MyName kernel: audit: type=1131 audit(1664037027.810:1159): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Med 24 17:30:27 MyName systemd-logind[486]: Operation 'sleep' finished.
Med 24 17:30:28 MyName avahi-daemon[468]: Withdrawing address record for 192.168.0.10 on wlan0.
Med 24 17:30:28 MyName avahi-daemon[468]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.10.
Med 24 17:30:28 MyName avahi-daemon[468]: Interface wlan0.IPv4 no longer relevant for mDNS.
Med 24 17:30:28 MyName dhclient[76459]: DHCPREQUEST for 192.168.0.10 on wlan0 to 255.255.255.255 port 67
Med 24 17:30:28 MyName kernel: Bluetooth: hci0: Waiting for firmware download to complete
Med 24 17:30:28 MyName kernel: Bluetooth: hci0: Firmware loaded in 1546817 usecs
Med 24 17:30:28 MyName kernel: Bluetooth: hci0: Waiting for device to boot
Med 24 17:30:28 MyName kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Med 24 17:30:28 MyName kernel: Bluetooth: hci0: Device booted in 12952 usecs
Med 24 17:30:28 MyName kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-12-16.ddc
Med 24 17:30:28 MyName kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Med 24 17:30:28 MyName kernel: Bluetooth: hci0: Firmware revision 0.1 build 19 week 44 2021
Med 24 17:30:29 MyName dbus-daemon[479]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.2045' (uid=1000 pid=76342 comm="/usr/lib/kscreenlocker_greet --immediateLock --gra")
Med 24 17:30:29 MyName dbus-daemon[479]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Med 24 17:30:29 MyName kscreenlocker_greet[76342]: pam_systemd_home(kde:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Med 24 17:30:30 MyName kernel: wlan0: authenticate with 18:35:d1:c8:ec:09
Med 24 17:30:30 MyName kernel: wlan0: bad VHT capabilities, disabling VHT
Med 24 17:30:30 MyName kernel: wlan0: 80 MHz not supported, disabling VHT
Med 24 17:30:30 MyName kernel: wlan0: send auth to 18:35:d1:c8:ec:09 (try 1/3)
Med 24 17:30:30 MyName kernel: wlan0: authenticated
Med 24 17:30:30 MyName kernel: wlan0: associate with 18:35:d1:c8:ec:09 (try 1/3)
Med 24 17:30:30 MyName kernel: wlan0: RX AssocResp from 18:35:d1:c8:ec:09 (capab=0x1431 status=0 aid=2)
Med 24 17:30:30 MyName kernel: wlan0: associated
Med 24 17:30:30 MyName kernel: wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by 18:35:d1:c8:ec:09
Med 24 17:30:30 MyName dhclient[76622]: DHCPREQUEST for 192.168.0.10 on wlan0 to 255.255.255.255 port 67
Med 24 17:30:30 MyName dhclient[76622]: DHCPACK of 192.168.0.10 from 192.168.0.1
Med 24 17:30:30 MyName avahi-daemon[468]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.10.
Med 24 17:30:30 MyName avahi-daemon[468]: New relevant interface wlan0.IPv4 for mDNS.
Med 24 17:30:30 MyName avahi-daemon[468]: Registering new address record for 192.168.0.10 on wlan0.IPv4.
Med 24 17:30:30 MyName dhclient[76622]: bound to 192.168.0.10 -- renewal in 38284 seconds.
Med 24 17:30:32 MyName kernel: IN=wlan0 OUT= MAC= SRC=192.168.0.10 DST=255.255.255.255 LEN=140 TOS=0x00 PREC=0x00 TTL=64 ID=22375 DF PROTO=UDP SPT=21327 DPT=21327 LEN=120 
Med 24 17:30:32 MyName kernel: IN=wlan0 OUT= MAC= SRC=192.168.0.10 DST=255.255.255.255 LEN=140 TOS=0x00 PREC=0x00 TTL=64 ID=22376 DF PROTO=UDP SPT=21327 DPT=21328 LEN=120 
Med 24 17:30:36 MyName audit[76637]: USER_AUTH pid=76637 uid=1000 auid=1000 ses=3 msg='op=PAM:unix_chkpwd acct="username" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
Med 24 17:30:36 MyName kernel: audit: type=1100 audit(1664037036.880:1160): pid=76637 uid=1000 auid=1000 ses=3 msg='op=PAM:unix_chkpwd acct="username" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
Med 24 17:31:02 MyName kernel: IN=wlan0 OUT= MAC= SRC=192.168.0.10 DST=255.255.255.255 LEN=140 TOS=0x00 PREC=0x00 TTL=64 ID=26841 DF PROTO=UDP SPT=21327 DPT=21327 LEN=120 
Med 24 17:31:02 MyName kernel: IN=wlan0 OUT= MAC= SRC=192.168.0.10 DST=255.255.255.255 LEN=140 TOS=0x00 PREC=0x00 TTL=64 ID=26842 DF PROTO=UDP SPT=21327 DPT=21328 LEN=120 
Med 24 17:31:10 MyName clamd[477]: Sat Sep 24 17:31:10 2022 -> SelfCheck: Database modification detected. Forcing reload.
Med 24 17:31:10 MyName clamd[477]: Sat Sep 24 17:31:10 2022 -> Reading databases from /var/lib/clamav
Med 24 17:31:10 MyName systemd[1]: fangfrisch.service: Deactivated successfully.
Med 24 17:31:10 MyName audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=fangfrisch comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Med 24 17:31:10 MyName systemd[1]: fangfrisch.service: Consumed 1.361s CPU time.
Med 24 17:31:10 MyName kernel: audit: type=1131 audit(1664037070.420:1161): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=fangfrisch comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Med 24 17:31:29 MyName clamd[477]: Sat Sep 24 17:31:29 2022 -> Database correctly reloaded (8791759 signatures)
Med 24 17:31:29 MyName clamd[477]: Sat Sep 24 17:31:29 2022 -> Activating the newly loaded database...
Med 24 17:31:32 MyName kernel: IN=wlan0 OUT= MAC= SRC=192.168.0.10 DST=255.255.255.255 LEN=140 TOS=0x00 PREC=0x00 TTL=64 ID=35260 DF PROTO=UDP SPT=21327 DPT=21327 LEN=120 
Med 24 17:31:32 MyName kernel: IN=wlan0 OUT= MAC= SRC=192.168.0.10 DST=255.255.255.255 LEN=140 TOS=0x00 PREC=0x00 TTL=64 ID=35261 DF PROTO=UDP SPT=21327 DPT=21328 LEN=120 
Med 24 17:31:57 MyName chronyd[503]: Forward time jump detected!
Med 24 17:31:57 MyName chronyd[503]: Can't synchronise: no selectable sources

I was wondering in particular if

Med 24 17:30:27 MyName kernel: i915 0000:00:02.0: [drm] [ENCODER:94:DDI A/PHY A] is disabled/in DSI mode with an ungated DDI clock, gate it
Med 24 17:30:27 MyName kernel: i915 0000:00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it
Med 24 17:30:27 MyName kernel: i915 0000:00:02.0: [drm] [ENCODER:118:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it

indicated anything useful?

seth · 2022-09-25 07:07:29

https://intel-gfx.freedesktop.narkive.c … -dsi-ports
"Display Serial Interface"

This is about controlling the output and you don't have a problem there, I'd rather suspect kwin to stumble over the time jumps…
Has the problem meanwhile resurfaced?

cfr · 2022-09-26 13:57:01

seth wrote:

https://intel-gfx.freedesktop.narkive.c … -dsi-ports
"Display Serial Interface"
This is about controlling the output and you don't have a problem there, I'd rather suspect kwin to stumble over the time jumps…

Thank-you. I wouldn't have known what to make of that patch, even if I'd found it.

seth wrote:

Has the problem meanwhile resurfaced?

Xorg is currently using a minimum of high 20s % CPU and rising, but rising slowly. Typing repeats is slower than it should be, but not excruciating. When I first look at top, the % is much higher, but I think that's because I've just changed desktops. It will, I assume, keep going up, but it's not currently rising as fast as it was. I'm not sure why.

The time jumps are unavoidable, aren't they? If I use sleep?

seth · 2022-09-26 14:07:19

The time jumps are unavoidable, aren't they? If I use sleep?

Yes, but if we can blame a combination of compositor and S3 you could suspend/resume the compositor around S3 cycle (and it would be helpful for bug reports, I guess)

Any other process w/ suspicious CPU load?

cfr · 2022-09-27 04:55:31

seth wrote:

The time jumps are unavoidable, aren't they? If I use sleep?
Yes, but if we can blame a combination of compositor and S3 you could suspend/resume the compositor around S3 cycle (and it would be helpful for bug reports, I guess)

So the idea would be to stop compositing prior to S3 and start after? Would it be good to test that or is there another way of figuring out if that's what's happening?

Is it possible it could be related to something short of S3? E.g. if the laptop is left long enough for the screen to go blank, even though it doesn't sleep? It sometimes feels as if it has slowed while I've been off doing something else, but I'm not sure if that's a genuine effect or my imagination.

seth wrote:

Any other process w/ suspicious CPU load?

How do I determine what's suspicious? I don't have much idea of how much CPU different processes should take. I know something like Xorg probably shouldn't keep increasing because you don't expect it to be doing more over time (typically), chromium sometimes goes mad, though I'm not sure it eats CPU as much as it does memory. Chromium also sometimes makes Xorg seem entirely unresponsive until I switch to a console and back. I'm not sure it is unresponsive - I think it is still processing (some) input, but it is so slow, it gives the impression it's frozen. Some processes use a lot of resources briefly, but I've tended to assume that's expected (e.g. spideroakone, clamd).

Xorg definitely goes right up if I switch desktops.

I've also noticed the system seems to be forgetting my mouse, so I have to unplug and replug it. It didn't used to do this and it seems to happen if I've not used the mouse for a while, but it is sporadic. I looked at the journal but wasn't much the wiser. I may need a new mouse as it is quite old, but I'm not sure that explains the behaviour. I'm also not at all sure it has anything to do with the problem.

seth · 2022-09-27 07:53:33

So the idea would be to stop compositing prior to S3 and start after?

Yes. You could even automatize that w/ systemd sleep hooks.

How do I determine what's suspicious?

Aynthing w/ high CPU load while you're effectively not interacting w/ the system.

chromium sometimes goes mad, though I'm not sure it eats CPU as much as it does memory. Chromium also sometimes makes Xorg seem entirely unresponsive

If chromium was the cause, closing it and terminating all chromium processes should fix the situation.

e.g. spideroakone, clamd

seem to not be GUI processes, ie. could not explain spikes in Xorg no matter what they do.

I've also noticed the system seems to be forgetting my mouse

???
Is it a wireless one?
If not: let's assume the mouse is unstable on the USB (device disappears and re-shows in dmesg or the system journal a lot; also in the xorg log), this could increase the CPU load of Xorg just from reconfiguring the input devices all the time.

Or the mouse just responds badly to https://wiki.archlinux.org/title/Power_ … utosuspend (nb. that eg. TLP will alter that setting at runtime and iircs allows you to configure it for the specific device as well)

cfr · 2022-09-28 04:43:44

seth wrote:

How do I determine what's suspicious?
Aynthing w/ high CPU load while you're effectively not interacting w/ the system.
chromium sometimes goes mad, though I'm not sure it eats CPU as much as it does memory. Chromium also sometimes makes Xorg seem entirely unresponsive
If chromium was the cause, closing it and terminating all chromium processes should fix the situation.

I think chromium is probably its own problem rather than the cause of this one.

seth wrote:

e.g. spideroakone, clamd
seem to not be GUI processes, ie. could not explain spikes in Xorg no matter what they do.

spideroakone has a GUI element, but I'm pretty sure it uses noticeable resources when it's syncing things with the cloud.

This is really why I've been assuming spideroakone/clamd/freshclam etc. aren't relevant to the problem. They show up in top occasionally, when they're doing something and that's it.

I discovered today that if another process hogs CPU and I stop that process, xorg's % CPU does not immediately return to the levels I was seeing before, even though I've not restarted kwin_x11. I quit thunderbird because it was dominating top's list and xorg was as low as 6% whereas it wasn't dropping below the high 20s (at least) before I used thunderbird. This seemed a bit odd?

seth wrote:

I've also noticed the system seems to be forgetting my mouse
???
Is it a wireless one?

No. USB. I don't think they had wireless mice when I bought it.

seth wrote:

If not: let's assume the mouse is unstable on the USB (device disappears and re-shows in dmesg or the system journal a lot; also in the xorg log), this could increase the CPU load of Xorg just from reconfiguring the input devices all the time.
Or the mouse just responds badly to https://wiki.archlinux.org/title/Power_ … utosuspend (nb. that eg. TLP will alter that setting at runtime and iircs allows you to configure it for the specific device as well)

There is a lot of stuff about the mouse in xorg's log and the journal. I am using TLP, which enables USB autosuspend by default, I think. (I don't have anything relevant looking under /etc/udev/.)

I'm not convinced it forgets the mouse often enough to explain much, unless it is re-finding it without my unplugging and re-plugging it. I suspect it is doing this, but not terribly frequently. Typically, I need to run my kde-interference-undo script when the mouse gets re-added automatically or after a re-plug, so I think I'd know if this was happening really often. It happens more than it should, but I'm not sure it can explain xorg?

I also first noticed this problem when I was away when using a borrowed mouse and when its owner returned and I didn't have a mouse at all. (I borrow the mouse when cat-sitting, but when the humans come back, the desktop gets the mouse back!) I think I didn't see the issue with the borrowed mouse, but I definitely saw it the final week when I didn't use a mouse at all. (I think this corresponded to the system update which seemed to be related.)

seth · 2022-09-28 17:38:10

I discovered today that if another process hogs CPU and I stop that process, xorg's % CPU does not immediately return to the levels I was seeing before, even though I've not restarted kwin_x11. I quit thunderbird because it was dominating top's list and xorg was as low as 6% whereas it wasn't dropping below the high 20s (at least) before I used thunderbird. This seemed a bit odd?

No, the process could be busy w/ all sorts of things that are *not* asking the X11 server to do stuff.

cfr · 2022-10-01 23:57:21

seth wrote:

I discovered today that if another process hogs CPU and I stop that process, xorg's % CPU does not immediately return to the levels I was seeing before, even though I've not restarted kwin_x11. I quit thunderbird because it was dominating top's list and xorg was as low as 6% whereas it wasn't dropping below the high 20s (at least) before I used thunderbird. This seemed a bit odd?
No, the process could be busy w/ all sorts of things that are *not* asking the X11 server to do stuff.

I understand that, but why should xorg's CPU usage decrease even after thunderbird is stopped? I could understand if resources were diverted to thunderbird while it was running, but why wouldn't xorg usage return to what it was before once thunderbird was stopped? Usually the trend is ultra clear, even though it goes up and down from reading to reading. The trend is only ever up. Even if I turn off compositing, it returns to more-or-less the same usage when it's turned back on.

Currently trying sleep hooks, though xorg usage is increasing even without sleep. But I'll be interested to see if it helps.

seth · 2022-10-02 07:28:06

why wouldn't xorg usage return to what it was before once thunderbird was stopped

Because thunderbird wasn't loading the X11 server.

I quit thunderbird because it was dominating top's list and xorg was as low as 6% whereas it wasn't dropping below the high 20s (at least) before I used thunderbird

Did you mean that Xorg was at 20%, then you started TB, then Xorg dropped to 6% then you killed TP and that had no impact on Xorg?
Unless you can reliably reproduce that pattern, it's co·in·ci·dence.
Otherwise TB might trigger something in KWin that calms it down a bit

cfr · 2022-10-02 16:17:05

I'll see if I can reproduce the thunderbird pattern.

I'm having a problem with the sleep hooks. A web search suggested

/usr/bin/qdbus org.kde.KWin /Compositor suspend
/usr/bin/qdbus org.kde.KWin /Compositor resume

would stop/start the compositor and this worked from the command line, so I created, enabled and started /etc/systemd/system/kwin-compositor-sleep.service:

# https://wiki.archlinux.org/title/Power_management#Sleep_hooks
# - prefix in Exec lines causes non-zero exit status to be ignored & treated as successful

[Unit]
Description=kwin compositor sleep hook
Before=sleep.target
StopWhenUnneeded=yes

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=-/usr/bin/qdbus org.kde.KWin /Compositor suspend
ExecStop=-/usr/bin/qdbus org.kde.KWin /Compositor resume

[Install]
WantedBy=sleep.target

But this isn't working, I don't think. The journal shows the service activating and deactivating, but I don't think it is actually doing anything because I see

qdbus[133552]: Could not connect to D-Bus server: org.freedesktop.DBus.Error.NotSupported: Using X11 for dbus-daemon autolaunch was disabled at 
compile time, set your DBUS_SESSION_BUS_ADDRESS instead

How exactly am I'm supposed to use DBUS_SESSION_BUS_ADDRESS rather than X11 in the hook? Is there some option I need to pass to qdbus to stop it using X11? I'm not sure where to find documentation for qdbus. There doesn't seem to be a man page and I've only found specific snippets in the wiki.

seth · 2022-10-02 18:30:05

Use https://wiki.archlinux.org/title/Power_ … stem-sleep and https://gist.github.com/AladW/de1c5676d93d05a5a0e1 and there also import DBUS_SESSION_BUS_ADDRESS from eg. kwin_x11

Alternatively simply hardcode "Environment=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus" (assuming your UID is 1000, check "echo $DBUS_SESSION_BUS_ADDRESS" for the actual variable)

Edit: since qdbus won't block you might want to also briefly "sleep 0.5" or so to give KWin a chance to act before the system falls asleep

Last edited by seth (2022-10-02 18:31:15)

Arch Linux

#51 2022-09-06 19:51:14

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#52 2022-09-07 00:10:01

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#53 2022-09-07 06:14:06

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#54 2022-09-08 14:08:36

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#55 2022-09-08 14:35:55

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#56 2022-09-08 23:42:54

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#57 2022-09-09 06:55:03

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#58 2022-09-09 23:22:46

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#59 2022-09-10 06:27:55

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#60 2022-09-15 21:50:25

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#61 2022-09-19 23:12:04

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#62 2022-09-20 07:33:20

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#63 2022-09-21 01:09:35

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#64 2022-09-25 00:05:10

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#65 2022-09-25 07:07:29

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#66 2022-09-26 13:57:01

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#67 2022-09-26 14:07:19

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#68 2022-09-27 04:55:31

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#69 2022-09-27 07:53:33

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#70 2022-09-28 04:43:44

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#71 2022-09-28 17:38:10

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#72 2022-10-01 23:57:21

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#73 2022-10-02 07:28:06

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#74 2022-10-02 16:17:05

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

#75 2022-10-02 18:30:05

Re: Autorepeat rate and delay in KDE suddenly excruciatingly slow

Board footer