[Akonadi] [Bug 376822] empty trash or all trash on imap account akonadi doesn't continue

[Bruno Friedmann]

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

Bruno Friedmann  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #4 from Bruno Friedmann  ---
Work wtih
Linux 5.9.12-1-default x86_64 GNU/Linux, nvidia: 450.80.02
Qt: 5.15.2, KDE Frameworks: 5.76.0, Plasma: 5.20.4, kmail2 5.15.3 (20.08.3)

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

[Akonadi] [Bug 376822] empty trash or all trash on imap account akonadi doesn't continue

[Justin Zobel]

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

Justin Zobel  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|CONFIRMED   |NEEDSINFO

--- Comment #3 from Justin Zobel  ---
Thank you for the crash report.

As it has been a while since this was reported, can you please test and confirm
if this issue is still occurring or if this bug report can be marked as
resolved.

I have set the bug status to "needsinfo" pending your response, please change
back to "reported" or "resolved/worksforme" when you respond, thank you.

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

[Akonadi] [Bug 376822] empty trash or all trash on imap account akonadi doesn't continue

[Christoph Feck]

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

--- Comment #2 from Christoph Feck  ---
Wasn't this connection shutdown already fixed?

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

[Akonadi] [Bug 376822] empty trash or all trash on imap account akonadi doesn't continue

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||dvra...@kde.org
   Priority|NOR |HI
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Daniel Vrátil  ---
ItemRetriever now uses QEventLoop to wait for request to be processed. If
Akonadi Server is shut down during that, the QEventLoop will cause
Connection::quit() to be executed, destroying the QSqlDriver and deleting the
thread. When the QEventLoop finishes and ItemRetriever::exec() returns, the
QSqlQuery() tries to dereference the already-destroyed QSqlDriver.

We need a mechanism to either prevent Connection::quit() from being executed
while an event loop is running on the Connection, or we need a way to quickly
abort ItemRetriever::exec() from Connection::quit() before destroying the SQL
connection and the thread.

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