https://bugs.kde.org/show_bug.cgi?id=363085
Allen Winter changed:
What|Removed |Added
Resolution|--- |UPSTREAM
https://bugs.kde.org/show_bug.cgi?id=363085
--- Comment #18 from bl...@vivaldi.net ---
Resolved upstream. Bug status should be changed.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=363085
--- Comment #17 from Ian ---
(In reply to Fred Wells from comment #16)
> I'm having the same issue with Fedora (24) ...
> KMail: 5.2.3
> KDE Frameworks: 5.25.0
> Qt 5.6.1 (built against 5.6.1)
> KDE Plasma: 5.25.0
> Kernel:
https://bugs.kde.org/show_bug.cgi?id=363085
Fred Wells changed:
What|Removed |Added
CC||fred_we...@charter.net
https://bugs.kde.org/show_bug.cgi?id=363085
Ian changed:
What|Removed |Added
CC||ianse...@yahoo.co.uk
--- Comment
https://bugs.kde.org/show_bug.cgi?id=363085
--- Comment #14 from Ryein Goddard ---
Your talking about the kdepim package in the kubuntu repos? I didn't have it
installed, but I installed it and I didn't get any change.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=363085
--- Comment #13 from bl...@vivaldi.net ---
Ryein Goddard, have you tested this for kdepim 16.04 also?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=363085
--- Comment #12 from Ryein Goddard ---
The only other option is to do it asynchronously if that is what you mean. I
think it is discouraged because it is a blocking operation. This wouldn't only
be a problem if the gui was
https://bugs.kde.org/show_bug.cgi?id=363085
--- Comment #11 from bl...@vivaldi.net ---
exec() is a member of KJob class. Now let's look what tells us the
documentation:
* Executes the job synchronously.
*
* This will start a nested QEventLoop internally. Nested event loop can be
https://bugs.kde.org/show_bug.cgi?id=363085
--- Comment #10 from bl...@vivaldi.net ---
The last executed line of code is always the same:
Akonadi::CollectionStatisticsJob::CollectionStatisticsJob (this=0x9e98f0,
collection=..., parent=0x0)
at
https://bugs.kde.org/show_bug.cgi?id=363085
--- Comment #9 from bl...@vivaldi.net ---
Debugging session was really confusing. I found out that the certain thread
never finishes going in infinite loop like that
[Switching to thread 16 (Thread 0x7fff5dca4700 (LWP 1154))]
#0
https://bugs.kde.org/show_bug.cgi?id=363085
--- Comment #8 from bl...@vivaldi.net ---
Ryein Goddard, please check this
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/1584288
Click on "Does this bug affect you?" -> "Yes, it affects me".
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=363085
--- Comment #7 from bl...@vivaldi.net ---
It's really hard to debug this stuff in kubuntu because package kdepim-dbg is
missing. Why?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=363085
--- Comment #6 from bl...@vivaldi.net ---
KMailSettings::self()->emptyTrashOnExit() just reads settings and returns
"true" or "false". That's not it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=363085
--- Comment #5 from Ryein Goddard ---
Does that mean a problem exists in the emptyTrashOnExit() function? Because it
works while using the context menu right click. Are they that different, or
does the trash empty program
https://bugs.kde.org/show_bug.cgi?id=363085
--- Comment #4 from bl...@vivaldi.net ---
This is the actual problematic piece of code
KSharedConfig::Ptr config = KMKernel::config();
Akonadi::Collection trashCollection =
CommonKernel->trashCollectionFolder();
if
https://bugs.kde.org/show_bug.cgi?id=363085
rosenrot...@gmail.com changed:
What|Removed |Added
CC||rosenrot...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=363085
--- Comment #3 from bl...@vivaldi.net ---
Good. Now it's easy to create a patch fixing this.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=363085
--- Comment #2 from Ryein Goddard ---
I figured out why this is happening.
This happens because of the "Empty tocal trash folder on program exit" checkbox
is ticked.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=363085
bl...@vivaldi.net changed:
What|Removed |Added
CC||bl...@vivaldi.net
--- Comment #1 from
20 matches
Mail list logo