[Akonadi] [Bug 423672] org.kde.pim.imapresource: Failed to create folder on server: "Create failed, server replied: ... NO Mailbox already exists ... [ ALREADYEXISTS ]"
https://bugs.kde.org/show_bug.cgi?id=423672 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/pim/ ||kimap/commit/ee2900e3539483 ||b6f3d5eadfcf8cfc9c6ed42abe Resolution|--- |FIXED --- Comment #5 from Daniel Vrátil --- Git commit ee2900e3539483b6f3d5eadfcf8cfc9c6ed42abe by Daniel Vrátil, on behalf of Dennis Schridde. Committed on 07/07/2020 at 17:49. Pushed by dvratil into branch 'master'. Idempotent CREATE and DELETE If CREATE fails with an ALREADYEXISTS response code, that is not an error since the intended result (the object existing at the target location) has been achieved. Likewise, if DELETE fails with an NONEXISTENT response code, that is not an error since the intended result (the object being gone from the target location) has been achieved. Please note that for RENAME response code ALREADYEXISTS *is* an error since the content of the source folder was not moved as intended. cf. https://tools.ietf.org/html/rfc5530#section-3 M +27 -0src/createjob.cpp M +1-0src/createjob.h M +27 -0src/deletejob.cpp M +1-0src/deletejob.h https://invent.kde.org/pim/kimap/commit/ee2900e3539483b6f3d5eadfcf8cfc9c6ed42abe -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 423575] Akonadi server reproducibly eats ∞ memory (possibly in Akonadi::Server::Connection::handleIncomingData() [connection.cpp:274])
https://bugs.kde.org/show_bug.cgi?id=423575 --- Comment #5 from Daniel Vrátil --- Could you please check that you have the "Debugger" disabled in Akonadi Console? When the "Debugger" option is enabled, it causes the Server to generate a lots of debugging string data and send them over dbus. The "Debugger" option gets persisted in Akonadi Server for now, so even if you close Akonadi Console, the Akonadi Server will continue generating the data. I'll adjust the code to not persist the debugger accross Akonadi restarts. Anyway, that's what I see in the 20.04 screenshots, but that's just lots of temporary allocations, not the leaks. The leaks visible in the 18.04 heaptrack are related to QueryCache, which has been overhauled in 20.04. So I suspect what you are seeing on 18.04 is already fixed, and what you are seeing in 20.04 is either related to the Debugger being enabled and/or the real culprit is not shown on the screenshots. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 423575] Akonadi server reproducibly eats ∞ memory (possibly in Akonadi::Server::Connection::handleIncomingData() [connection.cpp:274])
https://bugs.kde.org/show_bug.cgi?id=423575 --- Comment #4 from Daniel Vrátil --- I take it back, it would still be useful to get the 20.04 heaptrack data, from the screenshots it seems to have better quality. You could try changing the compression algo (use .xz instead of .gz for instance). If you need some place where to upload such a huge file, I can give you upload access directly to my server. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 423575] Akonadi server reproducibly eats ∞ memory (possibly in Akonadi::Server::Connection::handleIncomingData() [connection.cpp:274])
https://bugs.kde.org/show_bug.cgi?id=423575 --- Comment #3 from Daniel Vrátil --- Never mind, I found the problem :) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 423575] Akonadi server reproducibly eats ∞ memory (possibly in Akonadi::Server::Connection::handleIncomingData() [connection.cpp:274])
https://bugs.kde.org/show_bug.cgi?id=423575 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org --- Comment #2 from Daniel Vrátil --- Thanks for the detailed data. Could you please share the heaptrack file for the 20.04 measurements? I'd like to investigate it in more depth. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] ItemRetrievalManager crash
https://bugs.kde.org/show_bug.cgi?id=408897 Daniel Vrátil changed: What|Removed |Added CC||stephan.diestelhorst@gmail. ||com --- Comment #19 from Daniel Vrátil --- *** Bug 422092 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] ItemRetrievalManager crash
https://bugs.kde.org/show_bug.cgi?id=408897 Daniel Vrátil changed: What|Removed |Added CC||s.pa...@spiekerbros.com --- Comment #18 from Daniel Vrátil --- *** Bug 420495 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] ItemRetrievalManager crash
https://bugs.kde.org/show_bug.cgi?id=408897 Daniel Vrátil changed: What|Removed |Added CC||peter.huy...@gmx.de --- Comment #20 from Daniel Vrátil --- *** Bug 422199 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 420495] Akonadi Crashes upon removal of duplicates in folder
https://bugs.kde.org/show_bug.cgi?id=420495 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 408897 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 419229] Akonadi crashes over and over again
https://bugs.kde.org/show_bug.cgi?id=419229 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 408897 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422092] Akonadi Server crashing in ItemRetrievalManager while syncing GMail
https://bugs.kde.org/show_bug.cgi?id=422092 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #10 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 408897 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422199] Akonadi crashes while KMail fetches IMAP-Servers
https://bugs.kde.org/show_bug.cgi?id=422199 Daniel Vrátil changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 408897 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] ItemRetrievalManager crash
https://bugs.kde.org/show_bug.cgi?id=408897 --- Comment #17 from Daniel Vrátil --- *** Bug 419229 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422079] Akonadi searches for file mysql-global.conf at wrong path
https://bugs.kde.org/show_bug.cgi?id=422079 Daniel Vrátil changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/pim/ ||akonadi/commit/911c2394f7ce ||01d1f22c63d9159b0ee4726b706 ||9 Status|REPORTED|RESOLVED --- Comment #2 from Daniel Vrátil --- Git commit 911c2394f7ce01d1f22c63d9159b0ee4726b7069 by Daniel Vrátil, on behalf of Yaroslav Sidlovsky. Committed on 27/05/2020 at 12:39. Pushed by dvratil into branch 'release/20.04'. Akonadi searches for file mysql-global.conf at wrong path Akonadi can't find `mysql-global.conf` placed at path `/etc/xdg/akonadi` dir. It looks for it at `/etc/xdg/akonadi/akonadi/` (see extra `akonadi/` part appended). Differential Revision: https://phabricator.kde.org/D29833 M +1-1src/server/storage/dbconfigmysql.cpp M +2-2src/widgets/selftestdialog.cpp https://invent.kde.org/pim/akonadi/commit/911c2394f7ce01d1f22c63d9159b0ee4726b7069 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 Daniel Vrátil changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #122 from Daniel Vrátil --- Google has approved KMail access to Gmail via Googla Sign-in today, so it should work again. Should you still see some errors, please let us know. https://www.reddit.com/r/kde/comments/gi5bol/kmailkontact_oauth_signin_with_gmail_enabled_again/ -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 400221] can't talk to dovecot imap server
https://bugs.kde.org/show_bug.cgi?id=400221 Daniel Vrátil changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||dvra...@kde.org --- Comment #10 from Daniel Vrátil --- Looks like a server issue requiring an old or incompatible crypto algos, which is beyond KDE PIM, sorry. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 411326] krunner hangs on first start
https://bugs.kde.org/show_bug.cgi?id=411326 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org --- Comment #9 from Daniel Vrátil --- There's no trivial way to make the DBus call in ktp-contact-runner asynchronous so that it does not block KRunner when KTP service is not running. This is due to how KDE Telepathy, and Telepthy itself for that matter, are designed. If you don't use KTP, just uninstall the package that provides the ktp-contact-runner plugin, or disable the runner in KRunner settings. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 420318] ItemRetrievalRequest heap-use-after-free
https://bugs.kde.org/show_bug.cgi?id=420318 Daniel Vrátil changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- Fixed by ItemRetrievalRequest/ItemRetriever refactoring. *** This bug has been marked as a duplicate of bug 408897 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] ItemRetrievalManager crash
https://bugs.kde.org/show_bug.cgi?id=408897 Daniel Vrátil changed: What|Removed |Added CC||lukas.ka...@centrum.cz --- Comment #16 from Daniel Vrátil --- *** Bug 420318 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 419726] trying to change POP3 resource crashes
https://bugs.kde.org/show_bug.cgi?id=419726 Daniel Vrátil changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Latest Commit||https://commits.kde.org/kde ||pim-runtime/6cdf43de73993cb ||4615844b3461078e9e1bef467 Status|NEEDSINFO |RESOLVED --- Comment #2 from Daniel Vrátil --- Git commit 6cdf43de73993cb4615844b3461078e9e1bef467 by Daniel Vrátil. Committed on 10/04/2020 at 21:58. Pushed by dvratil into branch 'master'. POP3: Remove the singleton pattern from Settings Summary: It's causing issues with the "new" out-of-process settings dialog which initializes a new Settings object each time and asserts when the SettingsHelper Q_GLOBAL_STATIC is already initialized. Instead just get rid of the singleton pattern and have Settings object be owned by whomever created it and pass a reference to it to the classes that need it. Subscribers: mkoller, kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D28732 M +58 -57 resources/pop3/accountwidget.cpp M +4-1resources/pop3/accountwidget.h M +10 -9resources/pop3/jobs.cpp M +3-1resources/pop3/jobs.h M +8-8resources/pop3/pop3config.cpp M +47 -46 resources/pop3/pop3resource.cpp M +4-0resources/pop3/pop3resource.h M +6-31 resources/pop3/settings.cpp M +10 -2resources/pop3/settings.h https://commits.kde.org/kdepim-runtime/6cdf43de73993cb4615844b3461078e9e1bef467 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] ItemRetrievalManager crash
https://bugs.kde.org/show_bug.cgi?id=408897 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||5.15 Latest Commit||https://commits.kde.org/ako ||nadi/b94b8115f9586033983b05 ||9ae1faa731ef3defb1 --- Comment #15 from Daniel Vrátil --- Git commit b94b8115f9586033983b059ae1faa731ef3defb1 by Daniel Vrátil. Committed on 23/03/2020 at 18:07. Pushed by dvratil into branch 'master'. Clean up ItemRetriever to clear up ownership of ItemRetrievalRequest The request is now passed by value to the retriever. An ItemRetrievalResult is then returned to the caller. A unique numerical identifier is used to identify the requests/response pairs. FIXED-IN: 5.15 M +7-5autotests/server/fakeitemretrievalmanager.cpp M +1-2autotests/server/fakeitemretrievalmanager.h M +14 -14 autotests/server/itemretrievertest.cpp M +1-0src/server/CMakeLists.txt M +2-2src/server/handler/itemcopyhandler.cpp M +1-1src/server/handler/itemcopyhandler.h M +2-2src/server/handler/itemmovehandler.cpp M +1-1src/server/handler/itemmovehandler.h M +13 -18 src/server/storage/itemretrievaljob.cpp M +13 -11 src/server/storage/itemretrievaljob.h M +49 -41 src/server/storage/itemretrievalmanager.cpp M +8-8src/server/storage/itemretrievalmanager.h C +7-18 src/server/storage/itemretrievalrequest.cpp [from: autotests/server/fakeitemretrievalmanager.h - 059% similarity] M +41 -10 src/server/storage/itemretrievalrequest.h M +39 -42 src/server/storage/itemretriever.cpp M +1-1src/server/storage/itemretriever.h https://commits.kde.org/akonadi/b94b8115f9586033983b059ae1faa731ef3defb1 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] ItemRetrievalManager crash
https://bugs.kde.org/show_bug.cgi?id=408897 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Summary|crash on start |ItemRetrievalManager crash -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 411054] starting kaddressbook crashes akonadiserver
https://bugs.kde.org/show_bug.cgi?id=411054 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 408897 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] crash on start
https://bugs.kde.org/show_bug.cgi?id=408897 --- Comment #14 from Daniel Vrátil --- *** Bug 411054 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] crash on start
https://bugs.kde.org/show_bug.cgi?id=408897 Daniel Vrátil changed: What|Removed |Added CC||pa...@web.de --- Comment #13 from Daniel Vrátil --- *** Bug 418026 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] crash on start
https://bugs.kde.org/show_bug.cgi?id=408897 Daniel Vrátil changed: What|Removed |Added CC||g...@g4b.org --- Comment #11 from Daniel Vrátil --- *** Bug 416900 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 417542] Akonadi crashes on plasma start and further attempts to start
https://bugs.kde.org/show_bug.cgi?id=417542 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|RESOLVED CC||dvra...@kde.org Resolution|--- |DUPLICATE --- Comment #3 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 408897 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] crash on start
https://bugs.kde.org/show_bug.cgi?id=408897 Daniel Vrátil changed: What|Removed |Added CC||ke...@kde.org --- Comment #12 from Daniel Vrátil --- *** Bug 417542 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 418026] Akonadi crashes on login
https://bugs.kde.org/show_bug.cgi?id=418026 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 408897 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 416900] akonadi crash when try to move imap folder
https://bugs.kde.org/show_bug.cgi?id=416900 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 408897 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 416379] Akonadi crashes when selecting lost and found folder
https://bugs.kde.org/show_bug.cgi?id=416379 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 408897 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 413260] click on a mail on local maildir folder crashed akonadi server
https://bugs.kde.org/show_bug.cgi?id=413260 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|RESOLVED CC||dvra...@kde.org Resolution|--- |DUPLICATE --- Comment #1 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 408897 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] crash on start
https://bugs.kde.org/show_bug.cgi?id=408897 Daniel Vrátil changed: What|Removed |Added CC||k...@equaeghe.nospammail.net --- Comment #10 from Daniel Vrátil --- *** Bug 416379 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] crash on start
https://bugs.kde.org/show_bug.cgi?id=408897 --- Comment #9 from Daniel Vrátil --- *** Bug 413260 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 413706] Akonadi Crash During Removal of Duplicates in a Folder
https://bugs.kde.org/show_bug.cgi?id=413706 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 408897 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 413921] crash on mail check
https://bugs.kde.org/show_bug.cgi?id=413921 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|RESOLVED CC||dvra...@kde.org Resolution|--- |DUPLICATE --- Comment #2 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 408897 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] crash on start
https://bugs.kde.org/show_bug.cgi?id=408897 Daniel Vrátil changed: What|Removed |Added CC||m...@marekpasnikowski.name --- Comment #7 from Daniel Vrátil --- *** Bug 413706 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] crash on start
https://bugs.kde.org/show_bug.cgi?id=408897 --- Comment #8 from Daniel Vrátil --- *** Bug 413921 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 413301] Kmail crashed when check email
https://bugs.kde.org/show_bug.cgi?id=413301 Daniel Vrátil changed: What|Removed |Added Resolution|--- |DUPLICATE CC||dvra...@kde.org Status|REPORTED|RESOLVED --- Comment #2 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 408897 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] crash on start
https://bugs.kde.org/show_bug.cgi?id=408897 --- Comment #6 from Daniel Vrátil --- *** Bug 414147 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 414147] Akonadi crashed after checkmail
https://bugs.kde.org/show_bug.cgi?id=414147 Daniel Vrátil changed: What|Removed |Added Resolution|--- |DUPLICATE CC||dvra...@kde.org Status|REPORTED|RESOLVED --- Comment #2 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 408897 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] crash on start
https://bugs.kde.org/show_bug.cgi?id=408897 Daniel Vrátil changed: What|Removed |Added CC||kol...@aon.at --- Comment #4 from Daniel Vrátil --- *** Bug 410586 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] crash on start
https://bugs.kde.org/show_bug.cgi?id=408897 Daniel Vrátil changed: What|Removed |Added CC||m...@blobel.com --- Comment #5 from Daniel Vrátil --- *** Bug 413301 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 410586] crash of akonadiserver when kaddressbook starts
https://bugs.kde.org/show_bug.cgi?id=410586 Daniel Vrátil changed: What|Removed |Added Resolution|--- |DUPLICATE CC||dvra...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 408897 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] crash on start
https://bugs.kde.org/show_bug.cgi?id=408897 Daniel Vrátil changed: What|Removed |Added CC||robby.engelmann@r-engelmann ||.de --- Comment #3 from Daniel Vrátil --- *** Bug 409110 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409110] Akonadi Server crash after some time of having Kontact running
https://bugs.kde.org/show_bug.cgi?id=409110 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|RESOLVED CC||dvra...@kde.org Resolution|--- |DUPLICATE --- Comment #2 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 408897 *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 410758] Cannot change timing for single occurrence
https://bugs.kde.org/show_bug.cgi?id=410758 Daniel Vrátil changed: What|Removed |Added Latest Commit||https://commits.kde.org/kca ||lutils/1e240368ed7cd0b01576 ||1ef214e5caf504e8f723 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Daniel Vrátil --- Git commit 1e240368ed7cd0b015761ef214e5caf504e8f723 by Daniel Vrátil, on behalf of Shashwat Jolly. Committed on 21/03/2020 at 12:45. Pushed by dvratil into branch 'release/20.04'. Fix bug where time of single instance of recurring event could not be changed Summary: - Removed QObject::connect calls in recurrenceactions.cpp as the required "clicked" signals are already handled in DialogButtonsHelper in kmessagebox - Updated variable type for storing return value of createKMessageBox Reviewers: mlaurent Reviewed By: mlaurent Subscribers: winterz, mlaurent, kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D28149 M +1-5src/recurrenceactions.cpp https://commits.kde.org/kcalutils/1e240368ed7cd0b015761ef214e5caf504e8f723 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416132] Plasma crash when notification popup appears
https://bugs.kde.org/show_bug.cgi?id=416132 Daniel Vrátil changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Daniel Vrátil --- Caused by https://phabricator.kde.org/D23339, fixed by https://phabricator.kde.org/D27671 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416566] kded5 segmentation faults in KWayland::Client::OutputManagement::createConfiguration when logging into Plasma 5.17.90 on Wayland
https://bugs.kde.org/show_bug.cgi?id=416566 Daniel Vrátil changed: What|Removed |Added Latest Commit||https://commits.kde.org/lib ||kscreen/691c85879cafad942ed ||f6245196da9f04bc4cb6f Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||5.18.2 --- Comment #6 from Daniel Vrátil --- Git commit 691c85879cafad942edf6245196da9f04bc4cb6f by Daniel Vrátil. Committed on 24/02/2020 at 13:57. Pushed by dvratil into branch 'Plasma/5.18'. fix(kwayland): wait longer for connection timeout and retry Summary: During login creating the connection to Wayland server may take longer than 1 second (KWin busy, high CPU and IO load, ...) causing WaylandConfig to time out and leave the backend in an inconsistent state. This patch increases the timeout to 3 seconds and sets the overall backend status to invalid if connecting to Wayland server times out. This will abort the pending KScreen operation and prevent it from interacting with the broken backend. The next KScreen operation will try to set up the backend again, hopefully successfully this time. FIXED-IN: 5.18.2 Reviewers: #plasma, romangg Reviewed By: #plasma, romangg Subscribers: romangg, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D27618 M +1-2backends/kwayland/waylandbackend.cpp M +0-1backends/kwayland/waylandbackend.h M +11 -3backends/kwayland/waylandconfig.cpp M +2-0backends/kwayland/waylandconfig.h https://commits.kde.org/libkscreen/691c85879cafad942edf6245196da9f04bc4cb6f -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413892] Plasma crash under Wayland when I unplugged second monitor
https://bugs.kde.org/show_bug.cgi?id=413892 Daniel Vrátil changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Version Fixed In||5.18.2 Latest Commit||https://commits.kde.org/lib ||kscreen/63cab28e74ee30706cc ||43958921ae4224e4ea1fc --- Comment #8 from Daniel Vrátil --- Git commit 63cab28e74ee30706cc43958921ae4224e4ea1fc by Daniel Vrátil. Committed on 21/02/2020 at 11:51. Pushed by dvratil into branch 'Plasma/5.18'. fix(kwayland): remove code with side-effects from Q_ASSERT Summary: FIXED-IN: 5.18.2 Reviewers: #plasma, davidedmundson, meven Reviewed By: #plasma, davidedmundson, meven Subscribers: meven, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D27536 M +2-1backends/kwayland/waylandconfig.cpp https://commits.kde.org/libkscreen/63cab28e74ee30706cc43958921ae4224e4ea1fc -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413892] Plasma crash under Wayland when I unplugged second monitor
https://bugs.kde.org/show_bug.cgi?id=413892 Daniel Vrátil changed: What|Removed |Added CC||dan...@lbe.rs --- Comment #3 from Daniel Vrátil --- *** Bug 416455 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 417380] Plasma crashes when connecting screen on wayland
https://bugs.kde.org/show_bug.cgi?id=417380 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|RESOLVED CC||dvra...@kde.org Resolution|--- |DUPLICATE --- Comment #2 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 413892 *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413892] Plasma crash under Wayland when I unplugged second monitor
https://bugs.kde.org/show_bug.cgi?id=413892 Daniel Vrátil changed: What|Removed |Added CC||pas...@dhermilly.dk --- Comment #5 from Daniel Vrátil --- *** Bug 417864 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 417864] Crashed when unplugging power/hdmi/usb on Wayland
https://bugs.kde.org/show_bug.cgi?id=417864 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|RESOLVED CC||dvra...@kde.org Resolution|--- |DUPLICATE --- Comment #1 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 413892 *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416455] Plasma on Wayland crashes when disconnecting external display (DisplayPort via Thunderbolt)
https://bugs.kde.org/show_bug.cgi?id=416455 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 413892 *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413892] Plasma crash under Wayland when I unplugged second monitor
https://bugs.kde.org/show_bug.cgi?id=413892 Daniel Vrátil changed: What|Removed |Added CC||kampfkartof...@tutanota.com --- Comment #4 from Daniel Vrátil --- *** Bug 417380 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ksmtp] [Bug 416870] kmail seems to be not compliant to RFC - earlytalker
https://bugs.kde.org/show_bug.cgi?id=416870 Daniel Vrátil changed: What|Removed |Added Product|kmailtransport |ksmtp CC||dvra...@kde.org Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[plasma-pass] [Bug 415027] Incomplete dependency list in README
https://bugs.kde.org/show_bug.cgi?id=415027 Daniel Vrátil changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/pla ||sma-pass/8079dc6bd1a134ca2c ||0ac56efa98124049ba1f64 Status|REPORTED|RESOLVED Version Fixed In||1.1.1 --- Comment #1 from Daniel Vrátil --- Git commit 8079dc6bd1a134ca2c0ac56efa98124049ba1f64 by Daniel Vrátil. Committed on 22/01/2020 at 07:38. Pushed by dvratil into branch 'master'. Update dependencies in README FIXED-IN: 1.1.1 M +2-2README.md https://commits.kde.org/plasma-pass/8079dc6bd1a134ca2c0ac56efa98124049ba1f64 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pass] [Bug 415029] Fails do compile due to Q_FOREACH
https://bugs.kde.org/show_bug.cgi?id=415029 Daniel Vrátil changed: What|Removed |Added Version Fixed In||1.1.1 Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/pla ||sma-pass/2667be0cd4343af4b2 ||300473e2026bf9d444c56a --- Comment #1 from Daniel Vrátil --- Git commit 2667be0cd4343af4b2300473e2026bf9d444c56a by Daniel Vrátil. Committed on 22/01/2020 at 07:45. Pushed by dvratil into branch 'master'. Bump minimum required Qt and Frameworks PP wouldn't compile against older Frameworks with disabled deprecated Qt functions and Q_FOREACH. FIXED-IN: 1.1.1 M +2-2CMakeLists.txt https://commits.kde.org/plasma-pass/2667be0cd4343af4b2300473e2026bf9d444c56a -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416132] New: Plasma crash when notification popup appears
https://bugs.kde.org/show_bug.cgi?id=416132 Bug ID: 416132 Summary: Plasma crash when notification popup appears Product: plasmashell Version: master Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dvra...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.80) (Compiled from sources) Qt Version: 5.13.2 Frameworks Version: 5.66.0 Operating System: Linux 5.4.8-200.fc31.x86_64 x86_64 Windowing system: X11 Distribution: "Fedora release 31 (Thirty One)" -- Information about the crash: - What I was doing when the application crashed: Whenever a notification popup appears, Plasma crashes with the following backtrace. I'm running current git master of Frameworks and Plasma Workspace against distribution Qt 5.13.2. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd71ca99840 (LWP 5162))] Thread 7 (Thread 0x7fd6ebfff700 (LWP 5193)): #0 0x7fd71f7cad45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib64/libpthread.so.0 #1 0x7fd71fdb68e3 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7fd71fdb6971 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7fd721ebd4e9 in QSGRenderThread::processEventsAndWaitForMore() () at /usr/lib64/libQt5Quick.so.5 #4 0x7fd721ebd78d in QSGRenderThread::run() () at /usr/lib64/libQt5Quick.so.5 #5 0x7fd71fdb0dc6 in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #6 0x7fd71f7c44e2 in start_thread () at /usr/lib64/libpthread.so.0 #7 0x7fd71fc0e693 in clone () at /usr/lib64/libc.so.6 Thread 6 (Thread 0x7fd6f13bb700 (LWP 5192)): #0 0x7fd71f7cad45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib64/libpthread.so.0 #1 0x7fd71fdb68e3 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7fd71fdb6971 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7fd721ebd4e9 in QSGRenderThread::processEventsAndWaitForMore() () at /usr/lib64/libQt5Quick.so.5 #4 0x7fd721ebd78d in QSGRenderThread::run() () at /usr/lib64/libQt5Quick.so.5 #5 0x7fd71fdb0dc6 in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #6 0x7fd71f7c44e2 in start_thread () at /usr/lib64/libpthread.so.0 #7 0x7fd71fc0e693 in clone () at /usr/lib64/libc.so.6 Thread 5 (Thread 0x7fd707310700 (LWP 5169)): #0 0x7fd71e9f3a4d in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fd71e9a7710 in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd71e9a7943 in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd71ffb58b3 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fd71ff5f24b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd71fdafc75 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fd721e320da in QQuickPixmapReader::run() () at /usr/lib64/libQt5Quick.so.5 #7 0x7fd71fdb0dc6 in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #8 0x7fd71f7c44e2 in start_thread () at /usr/lib64/libpthread.so.0 #9 0x7fd71fc0e693 in clone () at /usr/lib64/libc.so.6 Thread 4 (Thread 0x7fd707fc4700 (LWP 5168)): #0 0x7fd71f7cad45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib64/libpthread.so.0 #1 0x7fd71fdb68e3 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7fd71fdb6971 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7fd721ebd4e9 in QSGRenderThread::processEventsAndWaitForMore() () at /usr/lib64/libQt5Quick.so.5 #4 0x7fd721ebd78d in QSGRenderThread::run() () at /usr/lib64/libQt5Quick.so.5 #5 0x7fd71fdb0dc6 in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #6 0x7fd71f7c44e2 in start_thread () at /usr/lib64/libpthread.so.0 #7 0x7fd71fc0e693 in clone () at /usr/lib64/libc.so.6 Thread 3 (Thread 0x7fd71a65a700 (LWP 5165)): #0 0x7fd71e9a58f3 in g_source_ref () at /usr/lib64/libglib-2.0.so.0 #1 0x7fd71e9a59a1 in g_source_iter_next () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd71e9a6cc3 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd71e9a773b in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #4 0x7fd71e9a7943 in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fd71ffb58b3 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fd71ff5f24b in
[plasma-pass] [Bug 411815] Password filtering extremely slow
https://bugs.kde.org/show_bug.cgi?id=411815 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-pass/092a5f9fbb09e12c76 ||ff9f2f0db803bc950c78fc Resolution|--- |FIXED Version Fixed In||0.2 --- Comment #1 from Daniel Vrátil --- Git commit 092a5f9fbb09e12c76ff9f2f0db803bc950c78fc by Daniel Vrátil. Committed on 05/12/2019 at 14:24. Pushed by dvratil into branch 'master'. Delay filtering after user paused typing Wait 100ms after user has finished typing before applying the new filter to the QSFPM. This notably reduces the lag, especially with larger password stores. FIXED-IN: 0.2 M +32 -6plugin/passwordfiltermodel.cpp M +4-0plugin/passwordfiltermodel.h https://commits.kde.org/plasma-pass/092a5f9fbb09e12c76ff9f2f0db803bc950c78fc -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 411533] Seg fault seemingly without cause
https://bugs.kde.org/show_bug.cgi?id=411533 Daniel Vrátil changed: What|Removed |Added Product|kontact |akregator Component|general |general CC||dvra...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #52 from Daniel Vrátil --- I understand that. The KDE e.V. board has full access to the API keys on Google Cloud Console, so in the worst case they can handle this themselves or grant access to another member of the community. Historically, I've been taking care of this because I've initially implemented the Google integration and thus I have access to the API keys as well. Usually when some action needs to be taken the Board asks me to handle it. Lately I've been a bit busy, so I wasn't able to act soon enough. Hopefully this was the last action that had to be taken for a long while again :) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #50 from Daniel Vrátil --- There's nothing to complain about, Google has some requirements, we have to fulfill them if we want to integrate with their services. At some point they found out we do not comply with their requirement, sent us a warning, but I did not have time and energy to act on it, so they blocked new logins. I've now did the necessary changes and filed a request to have the login enabled again. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409234] akonadi with qt5 5.13 is unable to initialize database when using the PostgreSQL backend
https://bugs.kde.org/show_bug.cgi?id=409234 --- Comment #5 from Daniel Vrátil --- Git commit 8b8db29d10b2ef92deb2d87ff613f3d7f39af34e by Daniel Vrátil. Committed on 26/07/2019 at 11:32. Pushed by dvratil into branch 'Applications/19.04'. Fix compatibility with QMYSQL driver after 74aed95 Summary: QPSQL requires the table name passed to QSqlDatabase::record() to be lowercase since Qt 5.13, but doing that breaks QMYSQL, so only adjust the name when using QPSQL. Reviewers: #kde_pim, vkrause Reviewed By: #kde_pim, vkrause Subscribers: kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D22677 M +4-1src/server/storage/dbintrospector.cpp https://commits.kde.org/akonadi/8b8db29d10b2ef92deb2d87ff613f3d7f39af34e -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409641] Akonadi Server crashs upon start of Kontact
https://bugs.kde.org/show_bug.cgi?id=409641 Daniel Vrátil changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #4 from Daniel Vrátil --- Could you please start Akonadi by running akonadictl start --verbose and attach ~/.local/share/akonadi/akonadiserver.error file to this report after the server crashes? Thanks -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409641] Akonadi Server crashs upon start of Kontact
https://bugs.kde.org/show_bug.cgi?id=409641 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org --- Comment #3 from Daniel Vrátil --- Copying the relevant bt here: [KCrash Handler] #6 QString::~QString (this=, __in_chrg=) at /usr/include/c++/9/bits/atomic_base.h:326 #7 Akonadi::Server::Query::Condition::~Condition (this=0x7f260c214db8, __in_chrg=) at /usr/src/debug/akonadi-server-19.04.2-188.3.x86_64/src/server/storage/query.h:77 #8 0x556a6d01f454 in QVector::destruct (this=, to=0x7f260c214de8, from=0x7f260c214de8) at /usr/include/qt5/QtCore/qvector.h:356 #9 QVector::freeData (x=0x7f260c214d70, this=) at /usr/include/qt5/QtCore/qvector.h:553 #10 QVector::~QVector (this=, __in_chrg=) at /usr/include/qt5/QtCore/qvector.h:72 #11 Akonadi::Server::Query::Condition::~Condition (this=, __in_chrg=) at /usr/src/debug/akonadi-server-19.04.2-188.3.x86_64/src/server/storage/query.h:77 #12 0x556a6d01f454 in QVector::destruct (this=, to=0x7f260c5a7d18, from=0x7f260c59d9f8) at /usr/include/qt5/QtCore/qvector.h:356 #13 QVector::freeData (x=0x7f260c597d10, this=) at /usr/include/qt5/QtCore/qvector.h:553 #14 QVector::~QVector (this=, __in_chrg=) at /usr/include/qt5/QtCore/qvector.h:72 #15 Akonadi::Server::Query::Condition::~Condition (this=, __in_chrg=) at /usr/src/debug/akonadi-server-19.04.2-188.3.x86_64/src/server/storage/query.h:77 #16 0x556a6d01fc6c in QVector::destruct (this=, to=0x7f260c0b3838, from=0x7f260c0b3838) at /usr/include/qt5/QtCore/qvector.h:356 #17 QVector::freeData (x=0x7f260c0b37f0, this=0x7f262fffe240) at /usr/include/qt5/QtCore/qvector.h:553 #18 QVector::~QVector (this=0x7f262fffe240, __in_chrg=) at /usr/include/qt5/QtCore/qvector.h:72 #19 Akonadi::Server::Query::Condition::~Condition (this=0x7f262fffe240, __in_chrg=) at /usr/src/debug/akonadi-server-19.04.2-188.3.x86_64/src/server/storage/query.h:77 #20 Akonadi::Server::QueryBuilder::~QueryBuilder (this=0x7f262fffe230, __in_chrg=) at /usr/src/debug/akonadi-server-19.04.2-188.3.x86_64/src/server/storage/querybuilder.h:45 #21 0x556a6d04d90f in Akonadi::Server::ItemFetchHelper::buildFlagQuery (this=0x7f262fffe760) at /usr/src/debug/akonadi-server-19.04.2-188.3.x86_64/src/server/handler/itemfetchhelper.cpp:220 #22 0x556a6d051030 in Akonadi::Server::ItemFetchHelper::fetchItems(std::function&&) (this=this@entry=0x7f262fffe760, itemCallback=...) at /usr/src/debug/akonadi-server-19.04.2-188.3.x86_64/src/server/handler/itemfetchhelper.cpp:413 #23 0x556a6d04bc78 in Akonadi::Server::ItemFetchHandler::parseStream (this=0x7f260c062440) at /usr/include/c++/9/bits/std_function.h:398 #24 0x556a6d01b7be in Akonadi::Server::Connection::handleIncomingData (this=0x556a6dd27f10) at /usr/include/c++/9/bits/unique_ptr.h:357 #25 0x7f26620bd6b2 in QtPrivate::QSlotObjectBase::call (a=0x7f262fffe930, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #26 QSingleShotTimer::timerEvent (this=0x7f260c004cd0) at kernel/qtimer.cpp:318 #27 0x7f26620b1255 in QObject::event (this=0x7f260c004cd0, e=) at kernel/qobject.cpp:1282 #28 0x7f266208566f in doNotify (event=0x7f262fffea60, receiver=0x7f260c004cd0) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:142 #29 QCoreApplication::notify (event=0x7f262fffea60, receiver=0x7f260c004cd0, this=) at kernel/qcoreapplication.cpp:1141 #30 QCoreApplication::notifyInternal2 (receiver=0x7f260c004cd0, event=0x7f262fffea60) at kernel/qcoreapplication.cpp:1065 #31 0x7f26620db0ab in QTimerInfoList::activateTimers (this=0x7f260c0044f0) at kernel/qtimerinfo_unix.cpp:643 #32 0x7f26620db924 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:183 #33 0x7f2660617b33 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #34 0x7f2660617dc0 in ?? () from /usr/lib64/libglib-2.0.so.0 #35 0x7f2660617e4f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #36 0x7f26620dbcd1 in QEventDispatcherGlib::processEvents (this=0x7f260c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #37 0x7f26620842eb in QEventLoop::exec (this=this@entry=0x7f262fffeca0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #38 0x7f2661ebcf91 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #39 0x7f2661ebe112 in QThreadPrivate::start (arg=0x556a6dd25a00) at thread/qthread_unix.cpp:360 #40 0x7f266128efaa in start_thread () from /lib64/libpthread.so.0 #41 0x7f2661b2f71f in clone () from /lib64/libc.so.6 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409419] Mail system crashed
https://bugs.kde.org/show_bug.cgi?id=409419 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kim ||ap/8bc38d948c5386716c1d91cf ||e2ae2e9413da6541 Version Fixed In||5.11.3 --- Comment #1 from Daniel Vrátil --- Git commit 8bc38d948c5386716c1d91cfe2ae2e9413da6541 by Daniel Vrátil. Committed on 07/07/2019 at 16:47. Pushed by dvratil into branch 'Applications/19.04'. Fix int overflow when parsing ImapSet Summary: The ImapSet is a vector of qint64s, but while iteraring over the vector the code stored the value as an int, which could've caused overflow if the Id was large enough, triggering the Q_ASSERT below. FIXED-IN: 5.11.3 Reviewers: #kde_pim, vkrause Reviewed By: #kde_pim, vkrause Subscribers: kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D22271 M +2-2src/imapset.cpp https://commits.kde.org/kimap/8bc38d948c5386716c1d91cfe2ae2e9413da6541 -- You are receiving this mail because: You are watching all bug changes.
[phonon-backend-gstreamer] [Bug 409363] When pausing video playback the video output can turn black
https://bugs.kde.org/show_bug.cgi?id=409363 Daniel Vrátil changed: What|Removed |Added Latest Commit||https://commits.kde.org/pho ||non-gstreamer/ff1f48bda6d21 ||aa4dbda76c87ba8a1e7ab4b64e2 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||4.9.1 --- Comment #2 from Daniel Vrátil --- Git commit ff1f48bda6d21aa4dbda76c87ba8a1e7ab4b64e2 by Daniel Vrátil. Committed on 04/07/2019 at 12:03. Pushed by dvratil into branch '4.9'. X11Renderer: don't blank overlay on pause Summary: FIXED-IN: 4.9.1 Test Plan: Tested with Dolphin with patch D22050 applied, pausing a video preview in Info pane by clicking on it no longer blanks the video widget. Reviewers: O4 phonon, sitter Reviewed By: O4 phonon, sitter Differential Revision: https://phabricator.kde.org/D22254 M +6-4gstreamer/x11renderer.cpp M +1-1gstreamer/x11renderer.h https://commits.kde.org/phonon-gstreamer/ff1f48bda6d21aa4dbda76c87ba8a1e7ab4b64e2 -- You are receiving this mail because: You are watching all bug changes.
[phonon-backend-gstreamer] [Bug 409363] When pausing video playback the video output can turn black
https://bugs.kde.org/show_bug.cgi?id=409363 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Daniel Vrátil --- I can reproduce. Looks like a bug in the default X11 renderer -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 392092] akonadi_control crash on first start
https://bugs.kde.org/show_bug.cgi?id=392092 Daniel Vrátil changed: What|Removed |Added Version Fixed In||19.04.3 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/ako ||nadi/c21bb5220a3ae835a5183a ||fd58c186ba21f6c93d --- Comment #24 from Daniel Vrátil --- Git commit c21bb5220a3ae835a5183afd58c186ba21f6c93d by Daniel Vrátil. Committed on 28/06/2019 at 15:13. Pushed by dvratil into branch 'Applications/19.04'. Fix race-condition on akonadi_control start Summary: Check that there are no other akonadi_control instances running as the very first thing on startup. Previously this check would happen after AkApplication initialization, which contains some potential race- conditions, like rotating log files. The situation when akonadi_control is launched multiple times can occur on session startup, when multiple different components will attempt to launch Akonadi if its not yet running. FIXED-IN: 19.04.3 Reviewers: #kde_pim, vkrause Reviewed By: #kde_pim, vkrause Subscribers: kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D22092 M +2-14 src/akonadicontrol/main.cpp M +3-4src/shared/akapplication.cpp M +43 -6src/shared/akapplication.h https://commits.kde.org/akonadi/c21bb5220a3ae835a5183afd58c186ba21f6c93d -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409234] akonadi with qt5 5.13 is unable to initialize database when using the PostgreSQL backend
https://bugs.kde.org/show_bug.cgi?id=409234 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/ako ||nadi/74aed9542ba1ff1e6e93a5 ||50c42869647c4eba8e Version Fixed In||5.11.3 --- Comment #3 from Daniel Vrátil --- Git commit 74aed9542ba1ff1e6e93a550c42869647c4eba8e by Daniel Vrátil. Committed on 28/06/2019 at 14:04. Pushed by dvratil into branch 'Applications/19.04'. Adapt DBInitializer to behavior change of QPSQL driver in Qt 5.13 Summary: Since Qt 5.13 the QPSQL driver escapes table names, which makes them case-sensitive, therefore QSqlDatabase::record() must be called with a lower-case table name, otherwise it won't match. FIXED-IN: 5.11.3 Test Plan: Akonadi doesn't attempt to re-initialize all tables on each start when using Qt 5.13 Reviewers: vkrause Reviewed By: vkrause Subscribers: kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D22133 M +1-1src/server/storage/dbintrospector.cpp https://commits.kde.org/akonadi/74aed9542ba1ff1e6e93a550c42869647c4eba8e -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409234] akonadi with qt5 5.13 is unable to initialize database when using the PostgreSQL backend
https://bugs.kde.org/show_bug.cgi?id=409234 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- Created attachment 121187 --> https://bugs.kde.org/attachment.cgi?id=121187=edit Akonadi patch to fix compatibility with Qt 5.13 QPSQL driver Would you (or anyone else using PSQL and Qt 5.13) be able to build Akonadi with the attached patch and test it? I don't have access to a machine with Qt 5.13 right now, so I'm just guessing from the Qt commit. If the patch doesn't work I'll try to update to 5.13 over the weekend... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kholidays] [Bug 409189] Early May bank holiday for UK has been moved for 2020
https://bugs.kde.org/show_bug.cgi?id=409189 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kho ||lidays/b7a99e5a088fbc09db4d ||502000912d1d62509771 --- Comment #1 from Daniel Vrátil --- Git commit b7a99e5a088fbc09db4d502000912d1d62509771 by Daniel Vrátil, on behalf of Natsumi Higa. Committed on 26/06/2019 at 09:43. Pushed by dvratil into branch 'master'. Update UK Early May bank holiday for 2020 Summary: Reference: [[ https://www.gov.uk/bank-holidays | UK bank holidays - GOV.UK ]] Special thanks: Ian Neal, who reported the bug and suggested the change Reviewers: #kde_pim, dvratil Reviewed By: #kde_pim, dvratil Subscribers: iann, dvratil, kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D22099 M +1-1holidays/plan2/holiday_gb-eaw_en-gb M +1-1holidays/plan2/holiday_gb-nir_en-gb M +1-1holidays/plan2/holiday_gb-sct_en-gb https://commits.kde.org/kholidays/b7a99e5a088fbc09db4d502000912d1d62509771 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386173] akonadictl stop does not shut down database
https://bugs.kde.org/show_bug.cgi?id=386173 Daniel Vrátil changed: What|Removed |Added Version Fixed In||5.11.3 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/ako ||nadi/565700f7fc1d73e3376001 ||09867fc01cc647cf13 --- Comment #20 from Daniel Vrátil --- Git commit 565700f7fc1d73e337600109867fc01cc647cf13 by Daniel Vrátil. Committed on 20/06/2019 at 09:51. Pushed by dvratil into branch 'Applications/19.04'. Check Postgres status by checking return code of pg_ctl Summary: The current code which was checking the standard output of "pg_ctl status", doesn't work with non-English locale, causing Akonadi to leave Postgres running after shutdown, because it thinks the db is no longer running. FIXED-IN: 5.11.3 Reviewers: #kde_pim, mlaurent Reviewed By: #kde_pim, mlaurent Subscribers: mlaurent, kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D21871 M +2-2src/server/storage/dbconfigpostgresql.cpp https://commits.kde.org/akonadi/565700f7fc1d73e337600109867fc01cc647cf13 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 397316] akonadi loses connection with IMAP server after suspend (but not only, DB error too)
https://bugs.kde.org/show_bug.cgi?id=397316 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #5 from Daniel Vrátil --- There seem to be multiple issues mixed in here: 1) Multiple Merge Candidates error (bug #338658) - we will have automatic recovery in 19.08 release. 2) Transaction timeout/deadlock - this should be fixed in 19.04 already through various fixes from David. 3) SQL error when running akonadictl fsck - fixed in 18.08.3 (commit 89727ad4da4d) 4) IMAP/SMTP getting stuck - this should mostly be fixed in 19.04 by the transaction timeout fixes 5) akonadi fsck/vacuum running while database is in use - there's a task for that (https://phabricator.kde.org/T9753) Note that vacuum never fixes anything (it's just supposed to optimize the database for index performance and storage size) and fsck is not a solution to unstuck Akonadi if it stops syncing. All in all, I think this can be closed, if you hit any of the described issues, please file separate bug reports. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386173] akonadictl stop does not shut down database
https://bugs.kde.org/show_bug.cgi?id=386173 Daniel Vrátil changed: What|Removed |Added Status|REOPENED|CONFIRMED --- Comment #17 from Daniel Vrátil --- Thanks for the logs, both of you. Indeed it appears that Akonadi mistakenly thinks, that Postgres is no longer running. Do you guys use non-english locale by default? Could you please run the following command both when Postgres IS running and when it is NOT running, and paste its output here? pg_ctl status --pgdata=$HOME/.local/share/akonadi/db_data -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386173] akonadictl stop does not shut down database
https://bugs.kde.org/show_bug.cgi?id=386173 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org --- Comment #13 from Daniel Vrátil --- Can you get full debug logs of the Akonadi Server, please? You can do so by starting Akonadi manually from the commandline: akonadictl --verbose start ... (wait for a bit) akonadictl stop You can retrieve the full logfile from ~/.local/share/akonadi/akonadiserver.error -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 407170] Akonadi won't start for Domain Users
https://bugs.kde.org/show_bug.cgi?id=407170 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|RESOLVED CC||dvra...@kde.org Resolution|--- |FIXED --- Comment #1 from Daniel Vrátil --- This should be fixed as a side-effect of https://phabricator.kde.org/D21650 which has moved the MySQL socket file to /var/run/user//akonadi, so the hostname or username no longer appears in the socket name. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 394839] pimitemtable.remoteid Column Too Small For Exchange Calendar Via davmail
https://bugs.kde.org/show_bug.cgi?id=394839 Daniel Vrátil changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/ako ||nadi/c059d054251282c3bc8d94 ||6447fb156d4442afa3 Status|REPORTED|RESOLVED --- Comment #8 from Daniel Vrátil --- Git commit c059d054251282c3bc8d946447fb156d4442afa3 by Daniel Vrátil. Committed on 10/06/2019 at 09:21. Pushed by dvratil into branch 'master'. Raise limit for PimItem.remoteId to 1024 characters Summary: Some DAV servers produce exteremely long RIDs that do not fit into the current 255 character limit. This is only problem on MySQL, on other DBs we use TEXT, which has no length limit. On MySQL, just increasing the column length to 1024 is not enough, there's a limit on maximum length of VARBINARY/VARCHAR index, which is 756 bytes (255 characters). To be able to have an index on a VARBINARY column with up to 1024 characters we need to enable innodb_large_prefix and change how the extra characters are stored on the disk (ROW_FORMAT). Test Plan: Modified a unit-test to attempt creating an Item with 1024 characters long RID Reviewers: #kde_pim, vkrause Reviewed By: #kde_pim, vkrause Subscribers: kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D21714 M +2-0autotests/libs/itemappendtest.cpp M +2-2src/server/storage/akonadidb.xml M +6-1src/server/storage/dbinitializer_p.cpp M +6-0src/server/storage/dbupdate.xml M +3-0src/server/storage/mysql-global-mobile.conf https://commits.kde.org/akonadi/c059d054251282c3bc8d946447fb156d4442afa3 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408239] AKONADI_RESOURCE_MAIN is not mentioned in documentation
https://bugs.kde.org/show_bug.cgi?id=408239 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- Same goes for AKONADI_AGENT_MAIN. I guess it's some Doxygen flag to include macro apidox? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 406623] akonadi maildir resource crash cannot be reported via DrKonqi
https://bugs.kde.org/show_bug.cgi?id=406623 Daniel Vrátil changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/ako ||nadi/eb8c5dc661e2e63bc40df0 ||f01770332c8f7738b0 Status|REPORTED|RESOLVED --- Comment #2 from Daniel Vrátil --- Git commit eb8c5dc661e2e63bc40df0f01770332c8f7738b0 by Daniel Vrátil. Committed on 02/06/2019 at 12:52. Pushed by dvratil into branch 'master'. Set KAboutData in AgentBase to enable reporting from DrKonqi Summary: BUG: 406623 Reviewers: #kde_pim, mlaurent Reviewed By: #kde_pim, mlaurent Subscribers: mlaurent, kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D21512 M +1-1CMakeLists.txt M +9-4src/agentbase/agentbase.cpp M +8-4src/agentbase/agentbase.h M +5-4src/agentbase/resourcebase.cpp M +4-4src/agentbase/resourcebase.h https://commits.kde.org/akonadi/eb8c5dc661e2e63bc40df0f01770332c8f7738b0 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 406606] "Report bug" button is always disabled
https://bugs.kde.org/show_bug.cgi?id=406606 Daniel Vrátil changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.16.0 Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/drk ||onqi/dd95de337e30d310ecf689 ||eb7719eba77da366ff --- Comment #1 from Daniel Vrátil --- Git commit dd95de337e30d310ecf689eb7719eba77da366ff by Daniel Vrátil. Committed on 01/06/2019 at 22:28. Pushed by dvratil into branch 'Plasma/5.16'. Fix the 'Report bug' button being always disabled Summary: The commit d4ae04a7 has changed #define of HAVE_XMLRPCLCIENT to #cmakedefine01 - since HAVE_XMLRPCCLIENT is not defined anywhere in the CMakeFiles.txt, this lead to the 'Report bug' button being unconditionally disabled at compile time. Since KXmlRpcClient is a REQUIRED dependency (and has been for a while), we can just remove the macro altogether. FIXED-IN: 5.16.0 Test Plan: The 'Report bug' button is enabled Reviewers: dfaure Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D21527 M +0-1src/config-drkonqi.h.cmake M +2-7src/drkonqidialog.cpp https://commits.kde.org/drkonqi/dd95de337e30d310ecf689eb7719eba77da366ff -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #132 from Daniel Vrátil --- Git commit 8f230d7d7f8a4e2b97273585374a68902b5ef6cf by Daniel Vrátil. Committed on 31/05/2019 at 11:21. Pushed by dvratil into branch 'master'. Automatic recovery from Multiple Merge Candidates error Summary: Introduce a recovery codepath when Multiple Merge Candidates error occurs during Item merging. Since clients generally do not use merging, this really only happens during ItemSync. In such case we quitely delete all the conflicting items from the database and reschedule the collection sync. The next sync should then succeed and bring the collection into a consistent state. Note that this does not fix the Multiple Merge Candidates bug - it can still happen (and we still don't know how), but Akonadi should now be able to recover from it automatically without user intervention, thus making this issue less of a PITA. Test Plan: Successfuly auto-recovered a broken collection on my setup. Reviewers: #kde_pim, dfaure Reviewed By: dfaure Subscribers: vkrause, dfaure, ngraham, asturmlechner, kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D21455 M +3-3autotests/server/fakedatastore.cpp M +1-1autotests/server/fakedatastore.h M +65 -4src/server/handler/itemcreatehandler.cpp M +4-0src/server/handler/itemcreatehandler.h M +18 -16 src/server/storage/datastore.cpp M +3-1src/server/storage/datastore.h https://commits.kde.org/akonadi/8f230d7d7f8a4e2b97273585374a68902b5ef6cf -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404698] Decryption Oracle based on replying to PGP or S/MIME encrypted emails
https://bugs.kde.org/show_bug.cgi?id=404698 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org --- Comment #3 from Daniel Vrátil --- In KMail this attack requires that user would enable "Automatic decryption of encrypted messages when viewing" option in KMail settings, which is disabled by default. Without this option enabled the user has to click on "Decrypt" on the part that the attacker wants to leak. At this point, the user will still clearly see which part of the content was encrypted and which part was not. When the user wants to reply to this decrypted message, the content would indeed get leaked to the attacker. However, I believe that at this point KMail has done enough to prevent (by not enabling auto-decryption by default) and warn (by clearly showing which part is encrypted and which not) the user so he or she could judge for themselves the potential risks when replying to the message. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 405975] Crash when changing Mail Folder name in KMail
https://bugs.kde.org/show_bug.cgi?id=405975 Daniel Vrátil changed: What|Removed |Added Latest Commit||https://commits.kde.org/pim ||common/6a91923b8a9f31b75b52 ||0725f4b310203fbfb13b Version Fixed In||5.11 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Daniel Vrátil --- Git commit 6a91923b8a9f31b75b520725f4b310203fbfb13b by Daniel Vrátil. Committed on 03/04/2019 at 15:58. Pushed by dvratil into branch 'Applications/19.04'. Fix crash when applying collection ACL changes Summary: Another regression caused by switch to const/non-const attributes. FIXED-IN: 5.11 Test Plan: Couldn't reproduce the crash described in the bug report, but the backtrace is fairly obvious. Reviewers: #kde_pim, lbeltrame Reviewed By: lbeltrame Subscribers: lbeltrame, kde-pim, winterz Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D20159 M +2-2src/pimcommonakonadi/acl/collectionaclpage.cpp https://commits.kde.org/pimcommon/6a91923b8a9f31b75b520725f4b310203fbfb13b -- You are receiving this mail because: You are watching all bug changes.
[plasma-pass] [Bug 405970] Plasma-pass's icon is too similar to Plasma Vault's
https://bugs.kde.org/show_bug.cgi?id=405970 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Daniel Vrátil --- I think the icon is literally the same as used by Vaults. I'll ask VDG for help with designing a dedicated icon, because I suck at this :) I don't want to use an arbitrary icon that happens to look good in Breeze, because it may look completely irrelevant in other icon themes. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 380171] KMail crash on first start
https://bugs.kde.org/show_bug.cgi?id=380171 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org --- Comment #8 from Daniel Vrátil --- I think this is a race condition in the initial setup: the race could be that on first start the Maildir resource (that backs the "Local folders") starts discovering what folders exist in ~/.local/share/mail and starts creating them in Akonadi and at the same time KMail realizes there's no Inbox, Outbox etc. in Local Folders and starts creating them. At some point they clash as they both attempt to create the same collection - one of them wins and one of them fails with the SQL error - if KMail is the one who loses, it aborts the initial job and triggers the "fatal error" dialog. -- You are receiving this mail because: You are watching all bug changes.
[kcalcore] [Bug 405884] kcal library used by korganiser is not compliant with RFC 5545
https://bugs.kde.org/show_bug.cgi?id=405884 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kcalcore] [Bug 405884] kcal library used by korganiser is not compliant with RFC 5545
https://bugs.kde.org/show_bug.cgi?id=405884 Daniel Vrátil changed: What|Removed |Added Product|Akonadi |kcalcore Component|DAV Resource|general CC||dvra...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 403642] ASSERT failure in ResourceBase::collectionsRetrieved(): "Calling collectionsRetrieved() although no collection retrieval is in progress"
https://bugs.kde.org/show_bug.cgi?id=403642 Daniel Vrátil changed: What|Removed |Added Latest Commit|https://commits.kde.org/ako |https://commits.kde.org/ako |nadi/116ee0a56736b1bd4a9343 |nadi/4c98f59e21a524fc6feec9 |e5cc71a2bea2a2482b |01dd3ac0890d12d67d --- Comment #6 from Daniel Vrátil --- Git commit 4c98f59e21a524fc6feec901dd3ac0890d12d67d by Daniel Vrátil. Committed on 26/03/2019 at 09:26. Pushed by dvratil into branch 'Applications/19.04'. Fix handling of collectionChanged() in AgentBase Since both overloads get called by Monitor, the first one would realize the second one is implemented and instead of ignoring the change it would call changeProcessed(). When the second overload gets called and dispatches an actual task, when the task finished and called changeProcessed(), it had effectively skipped a task, breaking the delicate Resource state machine FIXED-IN: 5.11 M +1-1src/agentbase/agentbase.cpp https://commits.kde.org/akonadi/4c98f59e21a524fc6feec901dd3ac0890d12d67d -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 403642] ASSERT failure in ResourceBase::collectionsRetrieved(): "Calling collectionsRetrieved() although no collection retrieval is in progress"
https://bugs.kde.org/show_bug.cgi?id=403642 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/ako ||nadi/116ee0a56736b1bd4a9343 ||e5cc71a2bea2a2482b Version Fixed In||5.11 Resolution|--- |FIXED --- Comment #5 from Daniel Vrátil --- Git commit 116ee0a56736b1bd4a9343e5cc71a2bea2a2482b by Daniel Vrátil. Committed on 26/03/2019 at 09:24. Pushed by dvratil into branch 'master'. Fix handling of collectionChanged() in AgentBase Since both overloads get called by Monitor, the first one would realize the second one is implemented and instead of ignoring the change it would call changeProcessed(). When the second overload gets called and dispatches an actual task, when the task finished and called changeProcessed(), it had effectively skipped a task, breaking the delicate Resource state machine FIXED-IN: 5.11 M +1-1src/agentbase/agentbase.cpp https://commits.kde.org/akonadi/116ee0a56736b1bd4a9343e5cc71a2bea2a2482b -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 403642] ASSERT failure in ResourceBase::collectionsRetrieved(): "Calling collectionsRetrieved() although no collection retrieval is in progress"
https://bugs.kde.org/show_bug.cgi?id=403642 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org --- Comment #3 from Daniel Vrátil --- Created attachment 119035 --> https://bugs.kde.org/attachment.cgi?id=119035=edit Patch for Akonadi Hi Milian, could you try with this patch? It appears that SyncCollectionTree here is just a victim of another bug triggered by the previous ChangeReply for collection modification. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 405851] Akonadi maildir resources crashes on boot.
https://bugs.kde.org/show_bug.cgi?id=405851 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- It's an uncaught exception. Might be fixed by https://phabricator.kde.org/D19983 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404433] Messages wrongly shown as "unread"
https://bugs.kde.org/show_bug.cgi?id=404433 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org --- Comment #2 from Daniel Vrátil --- Can you check what's the state of the message on the IMAP server? Are they marked as read there, too? Sounds like an inconsistency between the statistics cache and real state. -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 369310] google resource must use kaccounts
https://bugs.kde.org/show_bug.cgi?id=369310 --- Comment #2 from Daniel Vrátil --- We plan to integrate with KAccounts at some point, but it's not as straightforward as it may seem and it's not the top priority for me at the moment. Any help would be greatly appreciated. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #8 from Daniel Vrátil --- What version of Kontact do you have? Indeed in previous versions it wasn't possible to switch to other authentication methods when the server URL was imap.gmail.com, but in the more recent version (I think since KDE Applications 18.04 or 18.08 - that's Kontact 5.8 or 5.9) it is possible if you select "Custom Account" -> "IMAP" then in the "Advanced" tab, the authentication method combo box should be accessible and you should be able to select PLAIN method and enter your username and password normally. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Priority|NOR |HI --- Comment #2 from Daniel Vrátil --- There's currently an issue with the API keys used by Kontact to authenticate against Google. We are working on getting the app re-enabled again for new users. For now, you can use PLAIN authentication method (instead of XOAUTH2/Gmail) to authenticate with Gmail (if you use 2-factor authentication you will need to generate an app-specific password on accounts.google.com). -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 404691] choosing reverse name => "France" become "FR"
https://bugs.kde.org/show_bug.cgi?id=404691 --- Comment #1 from Daniel Vrátil --- I can't reproduce it :( Does the country also change in Google Contacts web interface? -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 404694] selecting a sub folder => merge the adress book and sub folder, it is useless
https://bugs.kde.org/show_bug.cgi?id=404694 --- Comment #1 from Daniel Vrátil --- This is a known limitation of the current implementation of the Google Contacts resource and KAdressbook. There's work in progress on replacing the current KAddressbook model with KPeople-based model, which has smart support for merging contacts: https://phabricator.kde.org/T9595 Once that is done, this will be solved as well. -- You are receiving this mail because: You are watching all bug changes.
