[kmail2] [Bug 485701] new messages in thread don't bring thread to top
https://bugs.kde.org/show_bug.cgi?id=485701 Ryein Goddard changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Ryein Goddard --- Never mind it appears it is an option in the sorting context menu. This should be the default though. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 485701] New: new messages in thread don't bring thread to top
https://bugs.kde.org/show_bug.cgi?id=485701 Bug ID: 485701 Summary: new messages in thread don't bring thread to top Classification: Applications Product: kmail2 Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ry...@live.com Target Milestone: --- New email messages in a thread do not bring the thread to the top of the list, or bottom if you have the messages sorted in reverse order. The date/time of the first email message in the thread is used instead of the newest. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 485426] Google Groupware agent stops syncing after a while
https://bugs.kde.org/show_bug.cgi?id=485426 Andre Woebbeking changed: What|Removed |Added CC||woebbek...@kde.org -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 485222] KMail Mail Display shows wrong date (just cutoff from the plain header, not regarding timezone information)
https://bugs.kde.org/show_bug.cgi?id=485222 Andre Woebbeking changed: What|Removed |Added CC||woebbek...@kde.org -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 412579] kmail notifications should take you to the actual email when clicked
https://bugs.kde.org/show_bug.cgi?id=412579 Ryein Goddard changed: What|Removed |Added CC||ry...@live.com --- Comment #35 from Ryein Goddard --- Same issue here. Clicking on a notification doesn't open kmail or take you to the email. -- You are receiving this mail because: You are the assignee for the bug.
[libkgapi] [Bug 484041] Changes don't get synced with google
https://bugs.kde.org/show_bug.cgi?id=484041 Torsten Bielen changed: What|Removed |Added CC||bie...@gmx.de --- Comment #3 from Torsten Bielen --- Same for me. -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 451620] akonadictl; sqlite: Error moving orphan items to collection 242 : Expression tree is too large (maximum depth 1000)
https://bugs.kde.org/show_bug.cgi?id=451620 --- Comment #4 from Erik Quaeghebeur --- (In reply to Christophe Marin from comment #3) > (In reply to Erik Quaeghebeur from comment #2) > > This is still an issue in latest KDE 5 versions. (I again had to apply my > > manual SQL fix.) > > If you mean akonadi < 24.02, it won't get the fix. This branch is closed, > you need to backport the change manually. Ah, nice, it seems the great commit https://invent.kde.org/pim/akonadi/-/commit/fcc37ce297df718430f83f7feb669573c9b135f2?page=3#995e689d409482037d49b6b0893848ff42e9f64f likely fixed the issue. (The function is now at https://invent.kde.org/pim/akonadi/-/blob/master/src/server/storagejanitor.cpp#L301.) AFAIU, It does seem though that the fix still passes through a C++ data structure and uses a two-step approach. Namely, first a list of orphans is queried, it is copied to a QList (https://invent.kde.org/pim/akonadi/-/blob/master/src/server/storagejanitor.cpp#L325), which is fed back into a second query that sets the orphaned items' collectionId to the lost+found one. This might be done more efficiently by directly selecting anything that qualifies as an orphan item using SQL directly in the WHERE of the UPDATE statement (cf. https://www.sqlite.org/lang_update.html, like in the DELETE statement in my Comment #1). -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 451620] akonadictl; sqlite: Error moving orphan items to collection 242 : Expression tree is too large (maximum depth 1000)
https://bugs.kde.org/show_bug.cgi?id=451620 --- Comment #3 from Christophe Marin --- (In reply to Erik Quaeghebeur from comment #2) > This is still an issue in latest KDE 5 versions. (I again had to apply my > manual SQL fix.) If you mean akonadi < 24.02, it won't get the fix. This branch is closed, you need to backport the change manually. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 485661] New: Kmail popup windows closes when trying to copy or move message to folder
https://bugs.kde.org/show_bug.cgi?id=485661 Bug ID: 485661 Summary: Kmail popup windows closes when trying to copy or move message to folder Classification: Applications Product: kmail2 Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: gerald.driss...@gmail.com Target Milestone: --- *** If I want to copy a message to a folder (right mouse button - Message - copy to folder), the popup window is killed as soon as I click on copy to folder. I cannot select a folder. *** SUMMARY STEPS TO REPRODUCE 1. Mark Message 2. Right click - copy or move message to 3. Popup window closes automatically (before you can even select a folder) OBSERVED RESULT Popup window closes automatically EXPECTED RESULT I should be able to select to folder to which I want to copy or move the message SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.0.3 (wayland) (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.1.0 Qt Version: 6.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[libkgapi] [Bug 485390] 0 % sync korganizer -> G calendar
https://bugs.kde.org/show_bug.cgi?id=485390 --- Comment #5 from Philippe ROUBACH --- Created attachment 168603 --> https://bugs.kde.org/attachment.cgi?id=168603=edit sync tasks G calendar -> korganizer stops at 0 % -- You are receiving this mail because: You are on the CC list for the bug.
