[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 the assignee for the bug.
[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 the assignee for the bug.
[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 the assignee for the bug.
[kmail2] [Bug 409301] New: not possible to customize pop account
https://bugs.kde.org/show_bug.cgi?id=409301 Bug ID: 409301 Summary: not possible to customize pop account Product: kmail2 Version: 5.10.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: daniel.mo...@laposte.net Target Milestone: --- when opening an account it is not possible to customize it if it is of pop type. With imap account no problem as I can get a directory with all the typical sub-directories with inbox, sent, etc... This setting is not possible with pop account. STEPS TO REPRODUCE 1. settings/account/reception/edit/ does not propose advanced/identity setting 2. 3. OBSERVED RESULT impossible to create a customized directory for all e-mails of this pop account EXPECTED RESULT like imap account SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 4:5.15.4 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION if I am right it was possible before to create a "unified" box which contained all e-mails of all created customized accounts. This appears in my kmail left panel. It has been created long time ago but is no more running. Theres is no possibility to delete it -- You are receiving this mail because: You are the assignee for the bug.
[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 the assignee for the bug.
[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 the assignee for the bug.
[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 the assignee for the bug.
[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 the assignee for the bug.
[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 the assignee for the bug.
[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 the assignee for the bug.
[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 the assignee for the bug.
[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 the assignee for the bug.
[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 the assignee for the bug.
[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 the assignee for the bug.
[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 the assignee for the bug.
[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 the assignee for the bug.
[Akonadi] [Bug 408042] Calendar cannot be fetched from server because the login credentials string is too long
https://bugs.kde.org/show_bug.cgi?id=408042 --- Comment #1 from Daniel --- SOLUTION: I solved the described problem by issuing the following command in my lokal akonadi MariaDB: use akonadi; ALTER TABLE PimItemTable MODIFY remoteId varbinary(1000); -- You are receiving this mail because: You are the assignee for the bug.
[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 on the CC list for the bug. You are the assignee for the bug.
[akregator] [Bug 408079] New: Fetching feeds causes duplicated items
https://bugs.kde.org/show_bug.cgi?id=408079 Bug ID: 408079 Summary: Fetching feeds causes duplicated items Product: akregator Version: GIT (master) Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: feed parser Assignee: kdepim-bugs@kde.org Reporter: danielrosc...@phoenitydawn.de Target Milestone: --- When fetching a feed multiple times akregator duplicates existing items when the content of a fetched item differs from the content of the same item already available locally. I'm suffering from this bug now since 10+ years and would like to see it finally gone. Here is my theory why it happens: Instead of using the guid only to compare two items for equality, Akregator builds a hash over title, description, content, link and author (https://github.com/KDE/akregator/blob/0d588dcbfb9cc93dec5b6bcbf3b01336ca1d09ce/src/feed/feed.cpp#L581-L585 and https://github.com/KDE/akregator/blob/0d588dcbfb9cc93dec5b6bcbf3b01336ca1d09ce/src/article.cpp#L189) and checks that as well, unless the guid started with "hash:". I believe this is not according to the specification, which states: > guid stands for globally unique identifier. It's a string that uniquely > identifies the item. > When present, an aggregator may choose to use this string to determine if an > item is new. > > http://some.server.com/weblogItem3207 > > There are no rules for the syntax of a guid. Aggregators must view them as a > string. It's up to > the source of the feed to establish the uniqueness of the string. http://www.rssboard.org/rss-specification#ltguidgtSubelementOfLtitemgt The current behavior produces duplicate items when authors fix typos in their posts or when software inserts random bits in the data (e.g. in Javascript included in the markup (Podlove Publisher is known for that (https://github.com/podlove/podlove-publisher/blob/192a2710b6ad3d0f5eff67f4daacb5d6dac6ab4a/lib/modules/subscribe_button/button.php#L88))). The latter case is particularly annoying as it produces a new item every single time akregator fetches the feed. I'd be happy to provide additional information if necessary. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 408042] New: Calendar cannot be fetched from server because the login credentials string is too long
https://bugs.kde.org/show_bug.cgi?id=408042
Bug ID: 408042
Summary: Calendar cannot be fetched from server because the
login credentials string is too long
Product: Akonadi
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: server
Assignee: kdepim-bugs@kde.org
Reporter: danielinberli...@gmail.com
Target Milestone: ---
Created attachment 120361
--> https://bugs.kde.org/attachment.cgi?id=120361=edit
Text file with error message
The calendar entries cannot be fetched from server because the login
credentials string is too long. I can see all calendars in KOrganizer, but the
calendar display filed remains empty.
Reason seems to be that the domain name of the server is very long.
It is a Horde server.
The client system running Akonadi is an OpenSUSE Leap 15.1.
All other calendars from this horde system can be displayed without problems
(domain name much shorter).
Reason seems to be a database table, column remoteId is to short, see the
following error message (for data protection reasons I have replaced some
letters by x letters, but I did not change the number of letters):
2019-05-25T23:59:16.891848+02:00 loa1 akonadiserver[3907]:
org.kde.pim.akonadiserver: Error while handling command FetchItems on
connection akonadi_davgroupware_resource_3 (0x55628b8621c0)
2019-05-25T23:59:16.895902+02:00 loa1 akonadiserver[3907]: message repeated 3
times: [ org.kde.pim.akonadiserver: Error while handling command FetchItems on
connection akonadi_davgroupware_resource_3 (0x55628b8621c0)]
2019-05-25T23:59:19.334931+02:00 loa1 akonadiserver[3907]:
org.kde.pim.akonadiserver: DATABASE ERROR:
2019-05-25T23:59:19.335251+02:00 loa1 akonadiserver[3907]:
org.kde.pim.akonadiserver: Error code: "1406"
2019-05-25T23:59:19.335417+02:00 loa1 akonadiserver[3907]:
org.kde.pim.akonadiserver: DB error: "Data too long for column 'remoteId' at
row 1"
2019-05-25T23:59:19.335599+02:00 loa1 akonadiserver[3907]:
org.kde.pim.akonadiserver: Error text: "Data too long for column 'remoteId'
at row 1 QMYSQL3: Der Befehl konnte nicht ausgeführt werden"
2019-05-25T23:59:19.335735+02:00 loa1 akonadiserver[3907]:
org.kde.pim.akonadiserver: Values: QMap((":0", QVariant(int, 0))(":1",
QVariant(QString,
"https://www.x.de/h/rpc.php/calendars/xx.xxx...@x-xxx-xxx.de/calendar~OV5Iqp6YmUNuhCyok2UpkJN/Ham4UixcxFU3Ft6PRqFr9X2.ics#04008200E00074C5B7101A82E00890B6EB6A4B4BD4011000544F59A1A0F4D341A8CF12EB09461AE62018-10-25T13:00:00+00:00;))(":2",
QVariant(QString, "\"065c4f8744e0ae5a4e2d3ea03efe3b88\""))(":3",
QVariant(QString, ""))(":4", QVariant(qlonglong, 85))(":5", QVariant(qlonglong,
3))(":6", QVariant(QDateTime, QDateTime(2019-05-25 21:59:19.334 UTC
Qt::TimeSpec(UTC(":7", QVariant(QDateTime, QDateTime(2019-05-25
21:59:19.334 UTC Qt::TimeSpec(UTC(":8", QVariant(bool, false))(":9",
QVariant(qlonglong, 0)))
2019-05-25T23:59:19.335874+02:00 loa1 akonadiserver[3907]:
org.kde.pim.akonadiserver: Query: "INSERT INTO PimItemTable (rev, remoteId,
remoteRevision, gid, collectionId, mimeTypeId, datetime, atime, dirty, size)
VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9)"
2019-05-25T23:59:19.336000+02:00 loa1 akonadiserver[3907]:
org.kde.pim.akonadiserver: Error during insertion into table "PimItemTable"
"Data too long for column 'remoteId' at row 1 QMYSQL3: Der Befehl konnte nicht
ausgeführt werden"
2019-05-25T23:59:19.336129+02:00 loa1 akonadiserver[3907]:
org.kde.pim.akonadiserver: Error while handling command CreateItem on
connection akonadi_davgroupware_resource_3 (0x55628b8621c0)
2019-05-25T23:59:19.336255+02:00 loa1 akonadi_davgroupware_resource[6897]:
org.kde.pim.akonadicore: Creating/updating items from the akonadi database
failed: "Failed to append item"
2019-05-25T23:59:19.339166+02:00 loa1 akonadi_davgroupware_resource[6897]:
org.kde.pim.akonadicore: Error during ItemSync: "Failed to append item"
I would be very thankfull if you could have a look at this.
Regards,
Daniel
--
You are receiving this mail because:
You are the assignee for the bug.
[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 the assignee for the bug.
[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 the assignee for the bug.
[kmail2] [Bug 406103] New: KMail won't display messages, crashes on Quit
https://bugs.kde.org/show_bug.cgi?id=406103 Bug ID: 406103 Summary: KMail won't display messages, crashes on Quit Product: kmail2 Version: 5.10.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: boven...@bovender.de Target Milestone: --- Application: kmail (5.10.3) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: KMail stopped displaying messages; Akonadi logged database timeout errors. When I quit KMail in this situation (which happens very often) with CTRL+Q, I get this crash report. I also wrote about this problem here: https://forum.kde.org/viewtopic.php?f=215=159963 The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f202710bbc0 (LWP 32100))] Thread 26 (Thread 0x7f1fc2ec5700 (LWP 4924)): #0 0x7f2019909ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f1fc2ec4710, expected=0, futex_word=0x7f1fc2ec48f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f2019909ed9 in __pthread_cond_wait_common (abstime=0x7f1fc2ec47b0, mutex=0x7f1fc2ec48a8, cond=0x7f1fc2ec48d0) at pthread_cond_wait.c:533 #2 0x7f2019909ed9 in __pthread_cond_timedwait (cond=0x7f1fc2ec48d0, mutex=0x7f1fc2ec48a8, abstime=0x7f1fc2ec47b0) at pthread_cond_wait.c:667 #3 0x7f200e868177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f200e868ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f200e868bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f200e826851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f200e829387 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f200e829974 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f200e86acd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f20199036db in start_thread (arg=0x7f1fc2ec5700) at pthread_create.c:463 #11 0x7f202415788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f1f675f7700 (LWP 3744)): #0 0x7f2019909ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f1f675f6710, expected=0, futex_word=0x7f1f675f68f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f2019909ed9 in __pthread_cond_wait_common (abstime=0x7f1f675f67b0, mutex=0x7f1f675f68a8, cond=0x7f1f675f68d0) at pthread_cond_wait.c:533 #2 0x7f2019909ed9 in __pthread_cond_timedwait (cond=0x7f1f675f68d0, mutex=0x7f1f675f68a8, abstime=0x7f1f675f67b0) at pthread_cond_wait.c:667 #3 0x7f200e868177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f200e868ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f200e868bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f200e826851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f200e8296b6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f200e829974 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f200e86acd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f20199036db in start_thread (arg=0x7f1f675f7700) at pthread_create.c:463 #11 0x7f202415788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7f1ecd2ac700 (LWP 3655)): #0 0x7f2019909ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f1ecd2ab710, expected=0, futex_word=0x7f1ecd2ab8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f2019909ed9 in __pthread_cond_wait_common (abstime=0x7f1ecd2ab7b0, mutex=0x7f1ecd2ab8a8, cond=0x7f1ecd2ab8d0) at pthread_cond_wait.c:533 #2 0x7f2019909ed9 in __pthread_cond_timedwait (cond=0x7f1ecd2ab8d0, mutex=0x7f1ecd2ab8a8, abstime=0x7f1ecd2ab7b0) at pthread_cond_wait.c:667 #3 0x7f200e868177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f200e868ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f200e868bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f200e826851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f200e8296b6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f200e829974 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f200e86acd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f20199036db in start_thread (arg=0x7f1ecd2ac700) at pthread_create.c:463
[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 the assignee for the bug.
[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 the assignee for the bug.
[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 the assignee for the bug.
[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 the assignee for the bug.
[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 the assignee for the bug.
[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 the assignee for the bug.
[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 the assignee for the bug.
[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 the assignee for the bug.
[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 the assignee for the bug.
[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 the assignee for the bug.
[kaddressbook] [Bug 398847] Kaddressbook not parsing gmail contacts
https://bugs.kde.org/show_bug.cgi?id=398847 Daniel Vrátil changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/lib ||kgapi/2a85825b3a15a6d87fd9d ||79a61af31927d716641 Version Fixed In||5.10.3 --- Comment #15 from Daniel Vrátil --- Git commit 2a85825b3a15a6d87fd9d79a61af31927d716641 by Daniel Vrátil. Committed on 24/02/2019 at 21:40. Pushed by dvratil into branch 'Applications/18.12'. Contacts: fix email type deserialization FIXED-IN: 5.10.3 M +14 -0src/contacts/contact.cpp M +5-0src/contacts/contact.h M +4-2src/contacts/contactsservice.cpp https://commits.kde.org/libkgapi/2a85825b3a15a6d87fd9d79a61af31927d716641 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 334569] KOrganizer not syncing properly with modified repeated events in google calendar
https://bugs.kde.org/show_bug.cgi?id=334569 Daniel Vrátil changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||5.11 Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kde ||pim-runtime/2cbb8037d3d7b6c ||e2610129800499b465c892da3 --- Comment #14 from Daniel Vrátil --- Git commit 2cbb8037d3d7b6ce2610129800499b465c892da3 by Daniel Vrátil. Committed on 23/02/2019 at 10:47. Pushed by dvratil into branch 'master'. Google Calendar: fix recurrence instance handling With the fix in LibKGAPI we no longer need any additional magic to handle recurrence instances. FIXED-IN: 5.11 M +1-1CMakeLists.txt M +2-39 resources/google/calendar/calendarresource.cpp https://commits.kde.org/kdepim-runtime/2cbb8037d3d7b6ce2610129800499b465c892da3 -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 334569] KOrganizer not syncing properly with modified repeated events in google calendar
https://bugs.kde.org/show_bug.cgi?id=334569 --- Comment #13 from Daniel Vrátil --- Git commit 52eb4116f96063fe9a047abdf27f5020ff698687 by Daniel Vrátil. Committed on 23/02/2019 at 10:38. Pushed by dvratil into branch 'master'. Calendar: fix recurrence handling Parse and set recurringEventId and properly distinguish between ID and iCalUID fields, which allows to identify recurrence instances M +1-1CMakeLists.txt M +115 -91 src/calendar/calendarservice.cpp M +10 -1src/calendar/calendarservice.h M +18 -0src/calendar/event.cpp M +12 -0src/calendar/event.h M +1-1src/calendar/eventcreatejob.cpp M +2-2src/calendar/eventdeletejob.cpp M +1-1src/calendar/eventmodifyjob.cpp M +2-2src/calendar/eventmovejob.cpp https://commits.kde.org/libkgapi/52eb4116f96063fe9a047abdf27f5020ff698687 -- You are receiving this mail because: You are on the CC list for the bug.
[libkgapi] [Bug 342369] akonadi google contacts5 does not respect view
https://bugs.kde.org/show_bug.cgi?id=342369 --- Comment #12 from Daniel Vrátil --- The problem is that if we keep some data only locally because we cannot sync them to Google, it goes against the principle of Akonadi being only a cache and it can also lead to data loss - if you would delete your Akonadi database, you would lose all this information that we couldn't upload to Google. We should encode the custom fields that Google does not support out-of-the-box into some "extra" fields that we can sync to Google (but unfortunately no other clients will likely be able to understand them), and eventually have the feature where the Contact Editor would only allow changing fields that the respective backend supports (so if Google does not support Contact name ordering, we would simply not make it configurable when creating a new contact in Google Contacts addressbook). For now, I'll look into the first step - encoding everything into the extra fields. -- You are receiving this mail because: You are on the CC list for the bug.
[libkgapi] [Bug 342369] akonadi google contacts5 does not respect view
https://bugs.kde.org/show_bug.cgi?id=342369 --- Comment #9 from Daniel Vrátil --- Also, let's keep this bug only about the name order, I saw the other reports about photo issues :) Please report the problem with the country separately. -- You are receiving this mail because: You are on the CC list for the bug.
[libkgapi] [Bug 342369] akonadi google contacts5 does not respect view
https://bugs.kde.org/show_bug.cgi?id=342369 --- Comment #8 from Daniel Vrátil --- I see - this is an attribute that is stored in the contact itself, very likely gets lost on next sync because Google doesn't support it. I'll see if we can be more clever about keeping local information during contact sync, only overwrite things that Google actually supports. -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 356367] Google Calendar's Repeated events not correctly updated
https://bugs.kde.org/show_bug.cgi?id=356367 Daniel Vrátil changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 334569 *** -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 334569] KOrganizer not syncing properly with modified repeated events in google calendar
https://bugs.kde.org/show_bug.cgi?id=334569 Daniel Vrátil changed: What|Removed |Added CC||matti.kettu...@gmail.com --- Comment #12 from Daniel Vrátil --- *** Bug 356367 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 371700] akonadi_googlecontacts_resource not regarding the proxy settings
https://bugs.kde.org/show_bug.cgi?id=371700 Daniel Vrátil changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 383970 *** -- You are receiving this mail because: You are on the CC list for the bug.
[libkgapi] [Bug 342369] akonadi google contacts5 does not respect view
https://bugs.kde.org/show_bug.cgi?id=342369 --- Comment #5 from Daniel Vrátil --- Where do you even configure the order in which names are displayed in KAddressbook, I can't actually find it. Can you check if the values are filled correctly on the Google side? -- You are receiving this mail because: You are on the CC list for the bug.
[kmail2] [Bug 404052] Crash during/after filtering inbox, probably related to Qt WebEngine integration
https://bugs.kde.org/show_bug.cgi?id=404052 --- Comment #6 from Daniel Vrátil --- Could you try reproducing under valgrind? valgrind --track-origins=yes --num-callers=50 kmail &> log.txt It will be ludicrously slow due to webengine, but it's our only hope figuring out why it crashes. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 402229] Sqlite backend error with schema update 36 & 37 (5.10.0)
https://bugs.kde.org/show_bug.cgi?id=402229 --- Comment #5 from Daniel Vrátil --- Git commit 42d6c38c4dc619f23ca00ad42d9c538fc9ca2f78 by Daniel Vrátil, on behalf of Konrad Rzepecki. Committed on 06/02/2019 at 17:14. Pushed by dvratil into branch 'Applications/18.12'. Fix SQLite backend foreign key PRAGMAs Summary: SQLite backend contain "PRAGMA foreign_key_check=OFF/ON" which ins't correct SQLite syntax. Author intention was probably disengage key checking. In SQLlite this can be achieved be temporary deffer key check. Correct syntax is in this case "PRAGMA defer_foreign_keys=ON/OFF". This partial resolves bug 402229. Reviewers: dvratil Reviewed By: dvratil Subscribers: lbeltrame, anthonyfieroni, kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D18781 M +46 -46 autotests/server/dbtest_data/dbinit_sqlite M +50 -50 autotests/server/dbtest_data/dbinit_sqlite_incremental M +2-2src/server/storage/dbinitializer_p.cpp https://commits.kde.org/akonadi/42d6c38c4dc619f23ca00ad42d9c538fc9ca2f78 -- You are receiving this mail because: You are the assignee for the bug.
[libkgapi] [Bug 402973] Changing Google password results in no access
https://bugs.kde.org/show_bug.cgi?id=402973 Daniel Vrátil changed: What|Removed |Added Product|kmail2 |libkgapi Component|general |General Assignee|kdepim-bugs@kde.org |dvra...@kde.org Version|5.9.3 |GIT -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 402973] Changing Google password results in no access
https://bugs.kde.org/show_bug.cgi?id=402973 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- I think I have a suspicion as to what happens, but I have not confirmed it and haven't checked the code either, so this is just an educated guess: When you change account password Google likely expires both the Access token and the Refresh token - the code may not be ready to handle invalid Refresh token and just keeps trying to get a new Access token using the - now invalid - Refresh token instead of throwing both away and showing the Google login dialog to receive a new pair. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 121298] open link in external firefox
https://bugs.kde.org/show_bug.cgi?id=121298 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL CC||dvra...@kde.org --- Comment #7 from Daniel Vrátil --- I think so. All links are opened with QDesktopServices using the default browser and since everything is based on Chromium or WebKit these days, there's no difference anyway :) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 293895] Timestamp in log files
https://bugs.kde.org/show_bug.cgi?id=293895 Daniel Vrátil changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/ako ||nadi/a4e7f9310cefd847ac5c6e ||4c6ba8ea4673199892 --- Comment #1 from Daniel Vrátil --- Fixed in master, will be in 19.04. https://commits.kde.org/akonadi/a4e7f9310cefd847ac5c6e4c6ba8ea4673199892 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 402149] Akonadi EWS ressource unable to start since update to KDE Applications 18.12
https://bugs.kde.org/show_bug.cgi?id=402149 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- Can you check whether the process (akonadi_ews_resource) is actually running? -- You are receiving this mail because: You are the assignee for the bug.
[knotes] [Bug 402075] Synchronizing with google keep
https://bugs.kde.org/show_bug.cgi?id=402075 Daniel Vrátil changed: What|Removed |Added URL||https://issuetracker.google ||.com/issues/36760910 CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- Unfortunately Google Keep does not have any public API that we could use :( https://issuetracker.google.com/issues/36760910 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 402084] Color of "Birthdays & Anniversaries" cannot be changed by user
https://bugs.kde.org/show_bug.cgi?id=402084 --- Comment #1 from Daniel Kraus --- Interestingly, by accident I just now found out that it *is* possible to change the color, via Settings -> Colors and Fonts -> Resources -> Birthdays and Anniversaries. However, me and the others (see referenced forum posts) are testimony to the fact that this is not very discoverable. Is it not possible to enable the usual context sub-menu? -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 402084] New: Color of "Birthdays & Anniversaries" cannot be changed by user
https://bugs.kde.org/show_bug.cgi?id=402084 Bug ID: 402084 Summary: Color of "Birthdays & Anniversaries" cannot be changed by user Product: korganizer Version: 5.9.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: boven...@bovender.de Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Add a calendar "Birthdays and Anniversaries". 2. Try to change the color by right-clicking on the entry in the Calendar Manager, then hovering over the submenu "Calendar Colors". OBSERVED RESULT The menu entries "Assign Color..." and "Disable Color" are disabled. EXPECTED RESULT The menu entries "Assign Color..." and "Disable Color" should be enabled. SOFTWARE/OS VERSIONS KDE Neon 5.14 ADDITIONAL INFORMATION See https://forum.kde.org/viewtopic.php?t=138840, https://forum.kde.org/viewtopic.php?t=139052 (nevermind the topic subjects, these are both concerned with not being able to change the birthday calendar color) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 402058] Proper way to manage autostarted Akonadi resources
https://bugs.kde.org/show_bug.cgi?id=402058 --- Comment #5 from Daniel Vrátil --- When you disable the agents in KMail configuration they will still run, but they will be completely inactive, using almost no memory and no CPU, just quietly sitting there. The migration agent can performs payload and metadata migration which require understanding the meaning of the payload, since Akonadi only sees the payload as a binary blob. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 402058] Proper way to manage autostarted Akonadi resources
https://bugs.kde.org/show_bug.cgi?id=402058 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Daniel Vrátil --- It should already work if you put the modified .desktop file to a custom path that is specified in XDG_DATA_DIRS env variable before the default one (/usr/share). Then the modified file should take precedence. We are not going to implement any user configuration for this - users don't know what is really needed for the whole system to work, so they would disable things like the migration agent and then complain to us that Akonadi doesn't work... The grand plan is to implement start-and-shutdown-on-demand capability for Akonadi and its resources so that the processes are not running when they are not needed. We are missing one important bit in Akonadi before implementing this feature though, so keeping this open for now. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 401704] Accepting Google Calendar invite makes me the organizer and duplicates the event
https://bugs.kde.org/show_bug.cgi?id=401704 Daniel Robbins changed: What|Removed |Added CC||k...@danieljrobbins.com -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 401704] New: Accepting Google Calendar invite makes me the organizer and duplicates the event
https://bugs.kde.org/show_bug.cgi?id=401704 Bug ID: 401704 Summary: Accepting Google Calendar invite makes me the organizer and duplicates the event Product: korganizer Version: 5.7.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: invitations Assignee: kdepim-bugs@kde.org Reporter: k...@danieljrobbins.com Target Milestone: --- SUMMARY Possible duplicate of 328616 which was reported in 2013. But I'm creating a new ticket to get more visibility with proper reproduction steps as this seems pretty trivial. STEPS TO REPRODUCE 1. Add event to Google Calendar from a non-korganizer account (any other account and not from korganizer) 2. Make sure the event invite includes the account tied to korganizer and kmail 3. Send out the event invite 4. Accept the invite by clicking 'accept' in kmail that should have been emailed from Google. OBSERVED RESULT Two events are now in Google Calendar 1) the original event with the original organizer 2) a new event with me as the organizer with the same attendees + the original organizer additionally my status is not updated that I accepted the original event EXPECTED RESULT > My status updated on the original event. > Not creating a new event with me as the organizer SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04 (available in About System) KDE Plasma Version: 5.12.6 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 357819] Korganizer doesn't send calendar events to Google account
https://bugs.kde.org/show_bug.cgi?id=357819 Daniel Robbins changed: What|Removed |Added CC||k...@danieljrobbins.com --- Comment #4 from Daniel Robbins --- Just switched to Linux from Mac about 3 weeks ago. Also experiencing this. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable
https://bugs.kde.org/show_bug.cgi?id=399167 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Daniel Vrátil --- The Multiple Merge Candidates issue and the transaction deadlock are not exactly the same issue, but I believe they are somewhat connected. I don't have a plan yet how to solve this (a workaround for the transaction deadlock is to use Postgres :)), if anyone has a simple set of steps how to reliably reproduce this issue, it would be a tremendous help. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388790] SMTP does not support OAuth2
https://bugs.kde.org/show_bug.cgi?id=388790 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||dvra...@kde.org --- Comment #3 from Daniel Vrátil --- Applications 18.12 introduced support for OAuth/2FA support for Gmail SMTP. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 399306] It should be possible to disable cache
https://bugs.kde.org/show_bug.cgi?id=399306 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #1 from Daniel Vrátil --- For local resources, we typically keep around only metadata and email envelope in the Akonadi cache. The actual email headers and body are loaded from the resource on demand, cached inside Akonadi temporarily and then expired after some configured period (usually 5 minutes or so). The same can be configured for any resource (for example the IMAP resource works the same way unless you select "Download email for offline access") - the caching and expiration policy can actually be configured on per folder basis, but generally, you configure it for the entire resource (by changing it in the top-level folder) and let the subfolders inherit the policies. It is not possible to bypass the caching completely (that is including the metadata), not even for local resources, which is by design. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 399231] Kmail uses a low resolution icon for the notification
https://bugs.kde.org/show_bug.cgi?id=399231 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||dvra...@kde.org Ever confirmed|0 |1 --- Comment #1 from Daniel Vrátil --- We should probably call KNotification with icon name instead of passing an actual pixmap (or we should be more clever about picking the right pixmap size). -- You are receiving this mail because: You are the assignee for the bug.
[knotes] [Bug 399551] Knotes Crash on start
https://bugs.kde.org/show_bug.cgi?id=399551 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- Could you make sure all your packages are up-to-date? Looks like you may have an issue with mixed versions of libraries. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 399331] Kontact/flatpak installation fails
https://bugs.kde.org/show_bug.cgi?id=399331 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Resolution|--- |MOVED Status|REPORTED|RESOLVED --- Comment #1 from Daniel Vrátil --- Let's move the Flapak-related discussion on https://github.com/flathub/org.kde.kontact/issues/4 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 381955] kmail hangs or causes desktop to hang when used with Nouveau graphics driver
https://bugs.kde.org/show_bug.cgi?id=381955 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|RESOLVED URL||https://bugs.freedesktop.or ||g/show_bug.cgi?id=91632 CC||dvra...@kde.org Resolution|--- |UPSTREAM --- Comment #5 from Daniel Vrátil --- Sorry, this issue is out of our control, it's a problem between QtWebEngine and Nouveau. There's an upstream bug report for this in the nouveau bug tracker: https://bugs.freedesktop.org/show_bug.cgi?id=91632 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 397979] akonadi,permanently, disk write, a mean of 1.2 Mb
https://bugs.kde.org/show_bug.cgi?id=397979
--- Comment #7 from Daniel Vrátil ---
Looks like Item retrieval ended up in an endless loop.
My first suspicion, since this is a maildir resource, is that the journal log
got corrupted or contains some wrong information, so let's try this:
akonadictl stop
mv ~/.config/akonadi/agent_config_akonadi_maildir_resource_0_changes.dat{,.bkp}
akonadictl start
This will rename the resource's journal file, so a new one will be created on
start. This /may/ mean the changes you did that were stuck in the file (like
marking an email as read or moving it to another folder) will be lost, but at
least we will know what's wrong.
If it does not help, we'll try to debug it further.
--
You are receiving this mail because:
You are the assignee for the bug.
[Akonadi] [Bug 388196] akonadi_control crash after login
https://bugs.kde.org/show_bug.cgi?id=388196 --- Comment #2 from Daniel Vrátil --- Something weird in your setup. Can you check that all files in ~/.local/share/akonadi are owned by your user and writable? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 396657] Search mail kills akonadi server
https://bugs.kde.org/show_bug.cgi?id=396657 Daniel Vrátil changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Daniel Vrátil --- I think we've fixed this in 18.08, please do reopen if it starts happening again. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 397979] akonadi,permanently, disk write, a mean of 1.2 Mb
https://bugs.kde.org/show_bug.cgi?id=397979 Daniel Vrátil changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||dvra...@kde.org Status|REPORTED|NEEDSINFO --- Comment #5 from Daniel Vrátil --- I need some debug output from Akonadi, otherwise I can't even guess what's going on. Enable logging and restart Akonadi from terminal: export QT_LOGGING_RULES="*=true;qt_*=false" akonadictl restart You should be seeing more than plenty of messages, you may want to redirect them to a file. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 393280] Repeated entries of 'Executing search "kontact-476707713-SearchSession"' in Akonadi log
https://bugs.kde.org/show_bug.cgi?id=393280 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||dvra...@kde.org Ever confirmed|0 |1 --- Comment #3 from Daniel Vrátil --- Whenever something changes in Akonadi we need to re-run persistent search queries to update the content of the "Search" folders in KMail, because currently there's no other way to figure out whether the new email matches the search filter or not (it's not run on every single change, but it is scheduled to run in about a second after the first change). If the query affects many collections or has many results (like in your case, 10219), it can hinder the performance. A workaround is to remove the persistent search folders from KMail (which sucks, I know...) Proper fix, of course, is for me to figure out how to match a single email against the search query so we can evaluate it on per-email basis instead of having to re-run the entire search query every time. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 397649] Unified Folder
https://bugs.kde.org/show_bug.cgi?id=397649 Daniel Vrátil changed: What|Removed |Added Latest Commit||https://commits.kde.org/kma ||il/52eee4a475ad2e27c732d988 ||701f1ef6dd128754 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Daniel Vrátil --- Git commit 52eee4a475ad2e27c732d988701f1ef6dd128754 by Daniel Vrátil. Committed on 10/09/2018 at 18:42. Pushed by dvratil into branch 'master'. Merge branch 'dev/unified-mailboxes' The Unified Mailboxes Agent (which in reality is a Resource in order to be able to own Collections) creates Inbox, Sent and Drafts virtual Collections and links all Items from real special Collections into them. It listens for changes in the source collections and updates the virtual Collections accordingly. Uses can also customize the default unified mailboxes and create their own. The agent can be enabled or disalbed from KMail's Plugins settings like other agents. By default the agent is off, however, if KMail detects that user has more than one account set up it will ask the user if they want to enable the feature. User is only ever asked once, the purpose is to make the feature easier to discover without bothering users with only one email account. CHANGELOG: Unified mailboxes in KMail Test Plan: Reviewers: mlaurent Reviewed By: mlaurent Subscribers: lueck, ngraham, mlaurent, kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D15065 M +1-1kmail.categories M +1-1src/configuredialog/configureaccountpage.cpp M +2-0 src/configuredialog/configureplugins/configurepluginslistwidget.cpp M +13 -0src/kmkernel.cpp M +2-1src/kmkernel.h M +53 -0src/kmmainwidget.cpp M +1-0src/kmmainwidget.h M +4-1src/settings/kmail.kcfg.cmake https://commits.kde.org/kmail/52eee4a475ad2e27c732d988701f1ef6dd128754 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 397882] Google resource crashes constantly
https://bugs.kde.org/show_bug.cgi?id=397882 Daniel Vrátil changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 397239 *** -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 397239] crash when searching with kmail
https://bugs.kde.org/show_bug.cgi?id=397239 Daniel Vrátil changed: What|Removed |Added CC||tomas.teije...@gmail.com --- Comment #3 from Daniel Vrátil --- *** Bug 397882 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 384929] Detect captive portals
https://bugs.kde.org/show_bug.cgi?id=384929 Daniel Vrátil changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- We tried using NetworkManager to detect whether we are behind a captive protal, unfortunately it sometimes had false positives. Maybe things have improved since then. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387612] IMAP gmail request OAUTH authntication with no user request
https://bugs.kde.org/show_bug.cgi?id=387612 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Daniel Vrátil --- This has been relaxed in recent versions. IMAP will still prefer XOAUTH authentication if it's supported by the server (Gmail), but allows users to choose alternative authentication methods if they wish. -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 372712] Protocol::HelloResponse not correctly parsed, the object is just a Command with type set
https://bugs.kde.org/show_bug.cgi?id=372712 Daniel Vrátil changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #8 from Daniel Vrátil --- Should be fixed now that the protocol implementation is autogenerated -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[Akonadi] [Bug 377674] WARNING_README.txt in home folder
https://bugs.kde.org/show_bug.cgi?id=377674 Daniel Vrátil changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- This file is created by the iCal/vCard folder resource. I guess you somehow accidentally set up your home folder as a source folder for one of those. Make sure none of your calendars or addressbooks point to your home folder, then you can safely remove the file. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 335091] Akonadiconsole hangs when using the debugger for a longer time
https://bugs.kde.org/show_bug.cgi?id=335091 Daniel Vrátil changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Daniel Vrátil --- We switched to a model in 18.08, so unless you try to resize columns, it keeps Akonadi Console responsive even with a long logging session. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 310437] Wish for a ActiveSync resource in akonadi for full Exchange compatibility
https://bugs.kde.org/show_bug.cgi?id=310437 Daniel Vrátil changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED CC||dvra...@kde.org --- Comment #10 from Daniel Vrátil --- We now have a native EWS resource. It's not perfect, but I think it's already better than nothing :) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 361575] Background operation cause crash of akonadi_imap (Akonadi::Protocol::HelloResponse::HelloResponse)
https://bugs.kde.org/show_bug.cgi?id=361575 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Daniel Vrátil --- This should be fixed at this point, the protocol is now generated and the Hello response always arrives immediately. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 227672] MAPI support in kmail
https://bugs.kde.org/show_bug.cgi?id=227672 Daniel Vrátil changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #20 from Daniel Vrátil --- We now have a stock EWS resource to support syncing with Exchange servers, I think EWS is much preferred over MAPI theses days. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[Akonadi] [Bug 345305] Save tags in xattr when it makes sense
https://bugs.kde.org/show_bug.cgi?id=345305 Daniel Vrátil changed: What|Removed |Added Component|Tag Resource|general CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- The Tag resource is gone, but tags are now fully supported by Akonadi internally so they could be written back by resources. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 340840] Show Facebook messages in KMail — make Facebook messages collection a mail collection
https://bugs.kde.org/show_bug.cgi?id=340840 Daniel Vrátil changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX CC||dvra...@kde.org --- Comment #3 from Daniel Vrátil --- Unfortunately Facebook no longer provides access to messages through any of their APIs. -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 280103] Inbox should be sync first
https://bugs.kde.org/show_bug.cgi?id=280103 Daniel Vrátil changed: What|Removed |Added CC||mollek...@kolabsys.com --- Comment #3 from Daniel Vrátil --- *** Bug 328716 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[Akonadi] [Bug 328716] A full sync should prioritize important collections and possibly sync multiple in parallel
https://bugs.kde.org/show_bug.cgi?id=328716 Daniel Vrátil changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 280103 *** -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 49871] why not have an IMAP precommand?
https://bugs.kde.org/show_bug.cgi?id=49871 Daniel Vrátil changed: What|Removed |Added CC||rjwyso...@gmail.com --- Comment #8 from Daniel Vrátil --- *** Bug 314945 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 314945] No option to choose PREAUTH authentication for IMAP
https://bugs.kde.org/show_bug.cgi?id=314945 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #3 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 49871 *** -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 208188] Wish: Hide Akonadi, or allow Akonadi resources to be renamed
https://bugs.kde.org/show_bug.cgi?id=208188 Daniel Vrátil changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED CC||dvra...@kde.org -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 302550] make CheckBox for enable/disable the autostart Akonadi server in System Settings/Akonadi Configuration
https://bugs.kde.org/show_bug.cgi?id=302550 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #1 from Daniel Vrátil --- Akonadi is started on demand, so if any app needs it, it will be started. Otherwise it would not work :) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 293895] Timestamp in log files
https://bugs.kde.org/show_bug.cgi?id=293895 Daniel Vrátil changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||dvra...@kde.org -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 290078] Akonadi should restart itself when it is hanging
https://bugs.kde.org/show_bug.cgi?id=290078 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Daniel Vrátil --- If Akonadi gets really really stuck, then it cannot really restart itself :) I think this refers more to the problem of Akonadi sessions in KMail getting stuck, I think this has been fixed in the meantime. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 292744] Is impossible switch Akonadi resource to "online" with KOrganizer
https://bugs.kde.org/show_bug.cgi?id=292744 --- Comment #2 from Daniel Vrátil --- Replaced with Google Calendar Resource years ago. The online/offline mode is reported by Qt now, so it should work the same for all resources. That said, we still do not have a button to synchronize all calendars from KOrganizer, I made a Phabricator task for that. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[Akonadi] [Bug 292744] Is impossible switch Akonadi resource to "online" with KOrganizer
https://bugs.kde.org/show_bug.cgi?id=292744 Daniel Vrátil changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- Replaced with Google Calendar Resource years ago. The online/offline mode is reported by Qt now, so it should work the same for all resources. That said, we still do not have a button to synchronize all calendars from KOrganizer, I made a Phabricator task for that. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[Akonadi] [Bug 257339] No need to insert username and password even if I disable KWallet
https://bugs.kde.org/show_bug.cgi?id=257339 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #2 from Daniel Vrátil --- Although undoubtedly KWallet has many shortcomings, it is the only viable password storage solution we have and we do not really support the no-kwallet usecase at this point (as that would mean implementing kwallet fallbacks everywhere in PIM). We may choose to implement this at some point if an alternative password storage appears that we will want to support. -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 223048] Store IMAP resources in an encrypted format
https://bugs.kde.org/show_bug.cgi?id=223048 Daniel Vrátil changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED CC||dvra...@kde.org --- Comment #2 from Daniel Vrátil --- Nowadays full-disk encryption is de facto a standard, so we will not implement this for Akonadi only. If this is still a concern, there are various existing solution how to encrypt only specific folders. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 280103] Inbox should be sync first
https://bugs.kde.org/show_bug.cgi?id=280103 Daniel Vrátil changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED CC||dvra...@kde.org --- Comment #2 from Daniel Vrátil --- The ResourceBase now pre-sorts the collections before sync: inbox first, then favorite collections, trash as the last. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[Akonadi] [Bug 221671] posssibility to limit number of mails downloaded with IMAP
https://bugs.kde.org/show_bug.cgi?id=221671 Daniel Vrátil changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||dvra...@kde.org --- Comment #2 from Daniel Vrátil --- Sadly, this has not been implemented yet, but it is on the roadmap now. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 252145] Akonadi should read MIME aliases when items are added (eg. text/x-vcard should map to text/directory)
https://bugs.kde.org/show_bug.cgi?id=252145 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #6 from Daniel Vrátil --- This I think has been fixed by now. -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 267165] External MySQL server with custom port number
https://bugs.kde.org/show_bug.cgi?id=267165 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Daniel Vrátil --- The GUI has been removed in the KF5/Qt5 port, we don't have a replacement yet. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 269139] akonadi-googledata uses unsecure HTTP
https://bugs.kde.org/show_bug.cgi?id=269139 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Daniel Vrátil --- The replacement Google resources use HTTPS everywhere. -- You are receiving this mail because: You are on the CC list for the bug.
