| Summary: | kde-plasma/kglobalacceld-6.1.2 maxes CPU in tigervnc session | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Robin Bankhead <gentoo> |
| Component: | Current packages | Assignee: | Gentoo KDE team <kde> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | CC: | gentoo |
| Priority: | Normal | Keywords: | UPSTREAM |
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| URL: | https://bugs.kde.org/show_bug.cgi?id=489840 | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=306352 | ||
| Whiteboard: | bug exists since Plasma 4 | ||
| Package list: | Runtime testing required: | --- | |
| Attachments: | tigervnc session log | ||
|
Description
Robin Bankhead
2024-07-03 13:57:20 UTC
If you're already subscribed to an upstream bug for this: please mention that. Noted and apologies for the omission, but I (and one or two other Gentooers) arguably hijacked that ancient bug and brought a very broad set of symptoms and contexts to the table that in retrospect just muddied the waters irretrievably. I'm less then convinced everyone subscribed there even has the same bug. For the sake of eliminating that stale config had anything to do with this, I tried removing first ~/.config/kglobalshortcutsrc and then ~/.config in its entirety. In both cases the bug still occurred. If there is something further that needs doing to start with a 100% blank Plasma session, please advise and I'll try it. [Sidenote: When ~/.config/kglobalshortcutsrc is generated from scratch, as in both cases above, kwin has no default shortcuts created, not even Alt+Tab. Is this normal/expected?] (In reply to Robin Bankhead from comment #2) > Noted and apologies for the omission, but I (and one or two other Gentooers) > arguably hijacked that ancient bug and brought a very broad set of symptoms > and contexts to the table that in retrospect just muddied the waters > irretrievably. I'm less then convinced everyone subscribed there even has > the same bug. In that case you should open a different upstream bug. It is unlikely to be solved here. I raised a report here because this specific behaviour is not seen when running the same software combo under systemd, and Gentoo is almost unique in that it does not default to systemd.
I understand that it's upstream's bug to fix, but my hope was that Gentoo devs who have done the work to make KDE and tigervnc work on Gentoo (tigervnc officially doesn't even support non-systemd usage now as I understand it, and I bet KDE has increased presumption of it* with this release) might have some insight on how this unique environment might play into it.
Upstream is a dead end unless any devs there are running Gentoo (or I suppose Void/Slackware/whatever else remains non-systemd).
* Maybe I'm wrong about that but it's just a hunch when the attached log contains e.g.
"kf.kio.gui: Failed to determine systemd version, falling back to extremely legacy forking mode."
and
"Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name org.kde.kglobalaccel was not provided by any .service files")"
(In reply to Robin Bankhead from comment #5) Please do anyway -- we do work with upstream on these issues and often they give us advice even if they don't prioritise working on the bugs sometimes. |
