https://bugs.kde.org/show_bug.cgi?id=505245
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma/discover/-/commit/1c6ff6 |ma/discover/-/commit/d0a224
|894e551a53c387d9f9a9f0429f6 |7567523ca77d880347cde926dad
|3442e50 |4ca43c5
--- Comment #8 from Nate Graham <n...@kde.org> ---
Git commit d0a2247567523ca77d880347cde926dad4ca43c5 by Nate Graham.
Committed on 09/06/2025 at 14:12.
Pushed by ngraham into branch 'Plasma/6.4'.
FlatpakTransactionThread: Copy job to new ref after rebase
When rebasing, the transaction still has the reference of the old item.
When rebasing is done and we know the new ref, the reference we ask for
during the new_operation_cb sets the new reference as current. This
causes an assert to fail the transaction, since the transaction
has the reference for the old item, even the job is still the same job.
Possible fix for this is to just copy the job and insert new ref as key
to the m_jobTransactionsByRef map, with the copied job: The job is
the same job for both the old and new reference.
(cherry picked from commit 1c6ff6894e551a53c387d9f9a9f0429f63442e50)
Co-authored-by: Akseli Lahtinen <akse...@akselmo.dev>
M +4 -0 libdiscover/backends/FlatpakBackend/FlatpakTransactionThread.cpp
https://invent.kde.org/plasma/discover/-/commit/d0a2247567523ca77d880347cde926dad4ca43c5
--
You are receiving this mail because:
You are watching all bug changes.
