Summary: | When 2 processes call the same KAuth action, first executed action result returns to both | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kauth | Reporter: | Martin Kostolný <clearmartin> |
Component: | general | Assignee: | kdelibs bugs <kdelibs-bugs> |
Status: | CONFIRMED --- | ||
Severity: | critical | CC: | elvis.angelaccio, katyaberezyaka, nate, simonandric5, sitter |
Priority: | VHI | ||
Version: | 5.33.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Martin Kostolný
2017-04-25 17:41:59 UTC
Mhhh. This may actually be a substantial architectural defect. I'm only glancing over the code but it looks a whole lot like the way the client<->helper communication is built assumes that only one action of a single type e.g. "org.kde.foo.action" is run at any given time. Specifically the helper gets told to run an action and then informs on progress for that action via signals that only link to the request by the action name. That is why two instances of kwrite would get finished, the helper emits actionPerformed("org.kate.whatevs", {}) and both clients think their request is the one that was performed. Fixing this essentially needs the entire IPC to get changed :| Oh dear oh dear |