[Discover] [Bug 522815] Discover does not start until process is killed manually

https://bugs.kde.org/show_bug.cgi?id=522815

Oliver Beard <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
                   |ma/discover/-/commit/a8b553 |ma/discover/-/commit/0d0a1d
                   |8958594d90406aa0294d3934bcd |35c715838f585590d54a1a9d5b1
                   |06e7607                     |4cbd151

--- Comment #8 from Oliver Beard <[email protected]> ---
Git commit 0d0a1d35c715838f585590d54a1a9d5b14cbd151 by Oliver Beard.
Committed on 15/08/2026 at 14:11.
Pushed by olib into branch 'Plasma/6.7'.

DiscoverObject: Address quitting with concurrent KJobs

We have a mechanism that disables random eventloops (KJobs) from
quitting Discover outside of the user's interaction (see
QCoreApplication::setQuitLockEnabled in discover/main.cpp).

It so happens that we would at times have KJobs running also _after_
Discover's window closes. See how on the reported bugs they often
describe it happening early in the startup process.

This patch restores the Q*Application::quitLockEnabled property so that
once Discover is with its task and we let go and QCoreApplication can
let these jobs finish and eventually quit.

It changes the DummyBackend to issue a KJob at the start to be able to
reproduce this problem and eventually its fix.
Related: bug 497419, bug 522245, bug 518264


(cherry picked from commit a8b5538958594d90406aa0294d3934bcd06e7607)

Co-authored-by: Aleix Pol <[email protected]>

M  +2    -0    discover/DiscoverObject.cpp
M  +22   -0    libdiscover/backends/DummyBackend/DummyBackend.cpp

https://invent.kde.org/plasma/discover/-/commit/0d0a1d35c715838f585590d54a1a9d5b14cbd151

-- 
You are receiving this mail because:
You are watching all bug changes.