[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0
https://bugs.kde.org/show_bug.cgi?id=389829 --- Comment #17 from Attila --- Created attachment 144297 --> https://bugs.kde.org/attachment.cgi?id=144297=edit SHOW ENGINE INNODB STATUS -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0
https://bugs.kde.org/show_bug.cgi?id=389829 --- Comment #16 from Attila --- Created attachment 144296 --> https://bugs.kde.org/attachment.cgi?id=144296=edit Journalctl Akonadi -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0
https://bugs.kde.org/show_bug.cgi?id=389829 --- Comment #15 from Attila --- Hi Raúl, thank you very much for your explanation. That was very helpfull. I can see in the log a line like: "Deadlock found when trying to get lock; try restarting transaction QMYSQL3: Unable to execute statement" "SHOW ENGINE INNODB STATUS" throws me lines out (see also attachments): LATEST DETECTED DEADLOCK 2021-12-07 08:24:45 0x7fde283ff640 *** (1) TRANSACTION: TRANSACTION 4390340, ACTIVE 0 sec starting index read mysql tables in use 6, locked 6 Regards -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 446595] New: no contacts listed/no synrchonization
https://bugs.kde.org/show_bug.cgi?id=446595 Bug ID: 446595 Summary: no contacts listed/no synrchonization Product: kontact Version: 5.15.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: contacts Assignee: kdepim-bugs@kde.org Reporter: wolkersdoerf...@web.de Target Milestone: --- SUMMARY Konact 5.15.3 (20.08.3), Linux (x86_64) release 5.10.0-9-amd64, is set up with a google account. Mail and calendar synchonize, tasks some tines, contacts never did *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. as above 2. 3. OBSERVED RESULT as above EXPECTED RESULT tasks and contacts will be synchonizes as well SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 401054] Stream parser exceptions
https://bugs.kde.org/show_bug.cgi?id=401054 Urs Joss changed: What|Removed |Added CC||tschent...@gmx.ch -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 446580] New: Contact synchronization with google doesn't work.
https://bugs.kde.org/show_bug.cgi?id=446580 Bug ID: 446580 Summary: Contact synchronization with google doesn't work. Product: kaddressbook Version: 5.18.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: sla...@ajon.eu CC: to...@kde.org Target Milestone: --- SUMMARY I can't synchronize contacts with google account anymore. After fresh install of Neon, synchronization of my contacts with google doesn't work. Address book can be created but is not synchronized with server. STEPS TO REPRODUCE 1. Create address book for google account. 2. Authenticate withing google to allow kaddressbook to access your contact details. 3. Refresh the folder - no update. OBSERVED RESULT Synchronization doesn't work. EXPECTED RESULT Synchronization of contacts should work. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 446579] New: Kontact crashes when I go to "Contacts"
https://bugs.kde.org/show_bug.cgi?id=446579 Bug ID: 446579 Summary: Kontact crashes when I go to "Contacts" Product: kontact Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: nicolas.fri...@hotmail.fr Target Milestone: --- Application: kontact (5.18.3 (21.08.3)) Qt Version: 5.15.3 Frameworks Version: 5.88.0 Operating System: Linux 5.11.0-41-generic x86_64 Windowing System: X11 Distribution: KDE neon User - Plasma 25th Anniversary Edition DrKonqi: 5.23.3 [KCrashBackend] -- Information about the crash: Happens everytime. Impossible to browse the contacts. Impossible to run kaddressbook, when I try to start it from terminal, it returns this : terminate called after throwing an instance of 'Akonadi::PayloadException' what(): Akonadi::PayloadException: Wrong payload type (requested: sp(0); present: sp(2)) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kaddressbook path = /usr/bin pid = 9737 KCrash: Arguments: /usr/bin/kaddressbook KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted [New LWP 2387] [New LWP 2396] [New LWP 2398] [New LWP 2404] [New LWP 2405] [New LWP 2406] [New LWP 2407] [New LWP 2408] [New LWP 2410] [New LWP 2413] [New LWP 2419] [New LWP 2464] [New LWP 2465] [New LWP 2466] [New LWP 2480] [New LWP 2510] [New LWP 2511] [New LWP 2532] [New LWP 6220] [New LWP 6239] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fbfdfa91aff in __GI___poll (fds=0x7fff863c8a78, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7fbfcb1c1200 (LWP 2384))] Thread 21 (Thread 0x7fbfca86d700 (LWP 6239)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7fbfca86c0b0, clockid=, expected=0, futex_word=0x7fbfca86c288) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7fbfca86c0b0, clockid=, mutex=0x7fbfca86c238, cond=0x7fbfca86c260) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7fbfca86c260, mutex=0x7fbfca86c238, abstime=0x7fbfca86c0b0) at pthread_cond_wait.c:656 #3 0x7fbfd9e6c20a in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x13c8 in ?? () #5 0x3a8511d1 in ?? () #6 0x13a7 in ?? () #7 0x3a8511d1 in ?? () #8 0x7fbf98011498 in ?? () #9 0x855416311f041c00 in ?? () #10 0x in ?? () Thread 20 (Thread 0x7fbfbaffd700 (LWP 6220)): #0 0x7fbfd5db14dd in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fbfd5d63568 in g_main_context_release () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fbfd5d64329 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbfd5d644a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fbfe006161b in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fbfe00058ab in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fbfdfe1f2c2 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fbfdfe2045c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fbfd68d6609 in start_thread (arg=) at pthread_create.c:477 #9 0x7fbfdfa9e293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7fbf38d40700 (LWP 2532)): #0 0x7fbfdfa91aff in __GI___poll (fds=0x7fbf2c004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fbfd5d6436e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fbfd5d644a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbfe006161b in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fbfe00058ab in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fbfdfe1f2c2 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fbfdfe2045c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fbfd68d6609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fbfdfa9e293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7fbf3a4b4700 (LWP 2511)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7fbf3a4b3268) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7fbf3a4b3218, cond=0x7fbf3a4b3240) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7fbf3a4b3240, mutex=0x7fbf3a4b3218) at pthread_cond_wait.c:638 #3
[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0
https://bugs.kde.org/show_bug.cgi?id=389829 --- Comment #14 from Raúl --- Attila, sorry for the delay in answering. I'm not a KDE developer but I can explain you what I suspect about this bug and how it can be related (if not duped) to https://bugs.kde.org/show_bug.cgi?id=434706. kontact/akonadi is a user fronted which shows data that those get from akonadi which, in turn, is closely bounded to a database. The database is made up of tables and registers. You can take a look at those tables and registers using an external database browser or the database command line client. For instance, in my case akonadi relies on mariadb database engine and I can query the akonadi data externally like this: ``` $ mariadb -S/run/user/1001/akonadi/mysql.socket MariaDB [(none)]> use akonadi; MariaDB [akonadi]> show tables ; +--+ | Tables_in_akonadi| +--+ | collectionattributetable | | collectionmimetyperelation | | collectionpimitemrelation| | collectiontable | | flagtable| | mimetypetable| | parttable| | parttypetable| | pimitemflagrelation | | pimitemtable | | pimitemtagrelation | | relationtable| | relationtypetable| | resourcetable| | schemaversiontable | | tagattributetable| | tagremoteidresourcerelationtable | | tagtable | | tagtypetable | +--+ 19 rows in set (0.001 sec) ``` kontact/kmail sends database queries to feed akonadi database and also to retrieve data. I think either the query flow or the database engine has some kind of bug or limitation. Hence one of the database queries locks some database tables (like those listed above) and therefore most of the database operations are locked (they cannot be completed). https://bugs.kde.org/show_bug.cgi?id=434706 explains some similar behavior and that is why I asked you to check if both reports are about the same problem. You are right that https://bugs.kde.org/show_bug.cgi?id=434706 is too technical and this is where you could get lost. In order to check whether the problem is the same or not, here is the list of actions that you can perform to verify: * Wait for the problem to reproduce or reproduce it yourself (if possible) * Check `journalctl -xe` output and look for recent output like this: ``` kmail[1317]: org.kde.pim.akonadicore: Received response with a different tag! akonadi_maildispatcher_agent[1586]: void SendJob::setFrom(const QString ) "m...@milianw.de" akonadi_maildispatcher_agent[1586]: d->m_returnPath "" akonadiserver[1305]: org.kde.pim.akonadiserver: QueryBuilder::exec(): database reported transaction deadlock, retrying transaction akonadiserver[1305]: org.kde.pim.akonadiserver: "Deadlock found when trying to get lock; try restarting transaction QMYSQL3: Unable to execute statement" akonadi_imap_resource[1583]: org.kde.pim.imapresource: "Connection to server lost." ``` * Additionally you can connect to the mariadb socket: `mariadb -S/run/user/1001/akonadi/mysql.socket` (1001 is your user code, maybe it's a different number) * Issue the following db engine query: `SHOW ENGINE INNODB STATUS` you should see that there is a deadlock detected: *LATEST DETECTED DEADLOCK* section in the https://bugs.kde.org/show_bug.cgi?id=434706 bug If you find out the same outcome, this and the other bug are quite possibly a duplicated. One additional comment is that I think the bug is not specifically about kmail, but about akonadi and its database engine usage. For getting a fix, we would need that someone with enough akonadi and DB knowledge to analyze and find out possible solutions. Unfortunately that is not by my hand. Regards, -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 446104] QtWebengine-based views broken in master - affects Kmail + Akregator + more in wayland session
https://bugs.kde.org/show_bug.cgi?id=446104 Philipp Reichmuth changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #2 from Philipp Reichmuth --- I'm seeing this in Qutebrowser and Falkon and what fixes it is setting QT_WEBENGINE_DISABLE_WAYLAND_WORKAROUND=1 (the variablecomes from an OpenSUSE patch: https://build.opensuse.org/package/view_file/KDE:Qt:5.15/libqt5-qtwebengine/disable-gpu-when-using-nouveau-boo-1005323.diff?expand=1) -- You are receiving this mail because: You are the assignee for the bug.
