[kactivitymanagerd] [Bug 393578] Broken thread use

2018-05-16 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=393578 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[kactivitymanagerd] [Bug 393578] Broken thread use

2018-05-16 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=393578 --- Comment #4 from Christoph Feck --- Patch from comment #3 was committed. Did it resolve this issue? -- You are receiving this mail because: You are watching all bug changes.

[kactivitymanagerd] [Bug 393578] Broken thread use

2018-04-28 Thread Ivan Čukić
https://bugs.kde.org/show_bug.cgi?id=393578 --- Comment #3 from Ivan Čukić --- Yes, they removed a flag they used to pass to sqlite which made sqlite behave well in a multi-threaded environment (was almost ready to fork the driver like akonadi ppl did when I heard this :) ). IIRC, it was in 5.10.

[kactivitymanagerd] [Bug 393578] Broken thread use

2018-04-28 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=393578 --- Comment #2 from David Edmundson --- Didn't realise it was a recent change. Thats kinda good news. I'm on 5.11 beta here. Personally I'd just drop the thread. Your events come from either dbus which has its own thread and queue, or the xcb qpa which

[kactivitymanagerd] [Bug 393578] Broken thread use

2018-04-27 Thread Ivan Čukić
https://bugs.kde.org/show_bug.cgi?id=393578 --- Comment #1 from Ivan Čukić --- Yes, the sqlite driver in Qt was changed not to serialize the database access. Will see what to do... -- You are receiving this mail because: You are watching all bug changes.