https://bugs.kde.org/show_bug.cgi?id=489840
--- Comment #31 from Robin Bankhead <kde.b...@headbank.co.uk> --- (In reply to Davide Favaro from comment #30) > coss posting to #489840 and #306352 because I don't know which one is the > correct one. > I have the same problem: remote TigerVNC session eating 100%. I have gentoo > and plasma 6.2.4 with NO .xmod* files or folder (never had) and I'm on > systemd. Thanks Davide, this eliminates any possibility that absence of systemd was a factor. This can now be raised with TigerVNC team. I wonder, though: We haven't seen anything similar happen with other desktops (Davide mentioned in forum that he had no issues with LxQt, and I've none on Fluxbox). We've seen that a flood of SocketNotifier events from Xvnc's RECORD extension is what causes kglobalacceld's problem (I hope I've described that accurately from what's been said above). But is it something unique to KDE that is in turn causing that flood to be generated? If the same flood of events was happening in another desktop without kglobalacceld to act as "canary", would there be any way to tell? (Executing xdotool always triggers this bug under KDE, under Fluxbox I see no ill-effect.) -- You are receiving this mail because: You are watching all bug changes.
