[Akonadi] [Bug 401054] Stream parser exceptions
https://bugs.kde.org/show_bug.cgi?id=401054 --- Comment #8 from Aaron Williams --- *** Bug 440345 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 440345] org.kde.pim.kimap: The stream parser raised an exception: Unable to read more data
https://bugs.kde.org/show_bug.cgi?id=440345 Aaron Williams changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Aaron Williams --- *** This bug has been marked as a duplicate of bug 401054 *** -- 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 Aaron Williams changed: What|Removed |Added Version|unspecified |5.17.80 --- Comment #7 from Aaron Williams --- This happens every time I receive a corporate-wide email with an extremely long CC list (the cc line is over 15,000 characters in length). Once this email is hit no more emails can be downloaded. Usually, this is an invitation to a corporate-wide meeting in my case. The only way to recover is to: 1. Stop akonadi 2. Delete the calendar entry in the Office365 web GUI 3. Delete the email in my inbox in the web GUI 4. Delete it from the deleted items folder in the web gui 5. Make sure it's really gone 6. Start akonadi 7. Sometimes I can use akonadiconsole to delete the offending email and allow akonadi to work again, but this isn't reliable. 8. If 7 doesn't work: 9. stop akonadi 10. delete .local/share/akonadi/file_db_data and .local/share/akonadictl/search_db 11. start akonadi 12. run akonadictl fsck Once this is done things will work again, however it is a very slow process for Akonadi to rebuild everything since in my case I have several IMAP accounts with decades of emails. Also, I have to repeat this process every single time I receive a corporate-wide email or calendar invitation and it means I can't add it to my calendar. I appologize for the two duplicate bugs I entered but they might add some additional info not listed here. I consider this a critical bug, since this basically kills Akonadi every time an email with a huge CC list is received where recovery is difficult. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 440543] org.kde.pim.kimap: The stream parser raised an exception: Unable to read more data
https://bugs.kde.org/show_bug.cgi?id=440543 --- Comment #3 from Aaron Williams --- This time the Akonadi console was unable to clear it out. I deleted the file_db_data and search_db_data and ran fsck and this cleared up the problem. This problem happens every time I receive a corporate-wide email. My guess is that something in Akonadi cannot handle such a long cc list. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 440543] org.kde.pim.kimap: The stream parser raised an exception: Unable to read more data
https://bugs.kde.org/show_bug.cgi?id=440543 Aaron Williams changed: What|Removed |Added Platform|Other |openSUSE RPMs --- Comment #2 from Aaron Williams --- This is really becoming a problem as this is happening every time I receive a corporate-wide email. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 440840] New: Akonadi crashen when attempting to empty trash can in KMail
https://bugs.kde.org/show_bug.cgi?id=440840 Bug ID: 440840 Summary: Akonadi crashen when attempting to empty trash can in KMail Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: onno.tas...@spamfence.net Target Milestone: --- Application: akonadiserver (5.17.3 (21.04.3)) Qt Version: 5.15.2 Frameworks Version: 5.84.0 Operating System: Linux 5.13.6-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I wanted to empty my "local trash can" folder in KMail. There is no problem when emptying an IMAP trash can folder. This caused Akonadi to run into some synching, and finally crashing or at least freezing. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f75dfef1840 (LWP 10848))] [KCrash Handler] #6 std::__atomic_base::load (__m=, this=, this=, __m=) at /usr/include/c++/11/bits/atomic_base.h:481 #7 QAtomicOps::loadRelaxed (_q_value=..., _q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:239 #8 QBasicAtomicInteger::loadRelaxed (this=0x0) at /usr/include/qt5/QtCore/qbasicatomic.h:107 #9 QtPrivate::RefCount::ref (this=0x0) at /usr/include/qt5/QtCore/qrefcount.h:55 #10 QByteArray::QByteArray (a=..., this=0x7f75b0ff8470) at /usr/include/qt5/QtCore/qbytearray.h:525 #11 Akonadi::Protocol::PartMetaData::PartMetaData (this=0x7f75b0ff8470) at /usr/src/debug/akonadi-server-21.04.3-2.2.x86_64/build/src/private/protocol_gen.h:170 #12 Akonadi::Protocol::StreamPayloadResponse::metaData (this=0x7f7590069610) at /usr/src/debug/akonadi-server-21.04.3-2.2.x86_64/build/src/private/protocol_gen.h:3688 #13 Akonadi::Server::PartStreamer::requestPartMetaData (partName=..., this=0x7f75b0ff8630) at /usr/src/debug/akonadi-server-21.04.3-2.2.x86_64/src/server/storage/partstreamer.cpp:58 #14 Akonadi::Server::PartStreamer::streamPayload (partName=..., part=..., this=0x7f75b0ff8630) at /usr/src/debug/akonadi-server-21.04.3-2.2.x86_64/src/server/storage/partstreamer.cpp:63 #15 Akonadi::Server::PartStreamer::stream(bool, QByteArray const&, long long&, bool*) [clone .constprop.0] (this=this@entry=0x7f75b0ff8630, partName=..., partSize=@0x7f75b0ff8608: 0, changed=changed@entry=0x0, checkExists=true) at /usr/src/debug/akonadi-server-21.04.3-2.2.x86_64/src/server/storage/partstreamer.cpp:306 #16 0x5567abf8aeb7 in Akonadi::Server::ItemModifyHandler::parseStream (this=0x7f75900775e0) at /usr/src/debug/akonadi-server-21.04.3-2.2.x86_64/src/server/handler/itemmodifyhandler.cpp:287 #17 0x5567abf5957a in Akonadi::Server::Connection::parseStream (this=0x5567ad61a370, cmd=...) at /usr/include/c++/11/bits/unique_ptr.h:173 #18 0x5567abf5db12 in operator() (__closure=) at /usr/src/debug/akonadi-server-21.04.3-2.2.x86_64/src/server/storage/dbdeadlockcatcher.h:31 #19 Akonadi::Server::DbDeadlockCatcher::callFunc&> (func=..., this=, func=..., recursionCounter=0) at /usr/src/debug/akonadi-server-21.04.3-2.2.x86_64/src/server/storage/dbdeadlockcatcher.h:34 #20 Akonadi::Server::DbDeadlockCatcher::DbDeadlockCatcher > (func=..., this=) at /usr/src/debug/akonadi-server-21.04.3-2.2.x86_64/src/server/storage/dbdeadlockcatcher.h:26 #21 Akonadi::Server::Connection::handleIncomingData (this=0x5567ad61a370) at /usr/src/debug/akonadi-server-21.04.3-2.2.x86_64/src/server/connection.cpp:249 #22 0x7f75e2a6df5e in QObject::event (this=0x5567ad61a370, e=0x7f7590004780) at kernel/qobject.cpp:1314 #23 0x7f75e2a4193f in doNotify (event=0x7f7590004780, receiver=0x5567ad61a370) at kernel/qcoreapplication.cpp:1154 #24 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1140 #25 QCoreApplication::notifyInternal2 (receiver=0x5567ad61a370, event=0x7f7590004780) at kernel/qcoreapplication.cpp:1064 #26 0x7f75e2a449b7 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x5567ad61a080) at kernel/qcoreapplication.cpp:1821 #27 0x7f75e2a997d3 in postEventSourceDispatch (s=s@entry=0x7f7590004fe0) at kernel/qeventdispatcher_glib.cpp:277 #28 0x7f75e0c7a80f in g_main_dispatch (context=0x7f759c20) at ../glib/gmain.c:3337 #29 g_main_context_dispatch (context=0x7f759c20) at ../glib/gmain.c:4055 #30 0x7f75e0c7ab98 in g_main_context_iterate (context=context@entry=0x7f759c20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131 #31 0x7f75e0c7ac4f in g_main_context_iteration (context=0x7f759c20, may_block=1) at ../glib/gmain.c:4196 #32 0x7f75e2a98e54 in
[korganizer] [Bug 440835] Missing translation
https://bugs.kde.org/show_bug.cgi?id=440835 gjditchfi...@acm.org changed: What|Removed |Added Resolution|FIXED |DUPLICATE CC||gjditchfi...@acm.org --- Comment #2 from gjditchfi...@acm.org --- Fixed in newer versions. See bug 432820. *** This bug has been marked as a duplicate of bug 432820 *** -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 440835] Missing translation
https://bugs.kde.org/show_bug.cgi?id=440835 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED CC||mon...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Laurent Montel --- This string can be translated. But 5.13.3 is very old (last version is 5.18.0). So better to test with new version. Regards -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 440835] Missing translation
https://bugs.kde.org/show_bug.cgi?id=440835 kuuhaku changed: What|Removed |Added Version|5.15.3 |5.13.3 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 440835] New: Missing translation
https://bugs.kde.org/show_bug.cgi?id=440835 Bug ID: 440835 Summary: Missing translation Product: korganizer Version: 5.15.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kuuhaku...@protonmail.com Target Milestone: --- Created attachment 140634 --> https://bugs.kde.org/attachment.cgi?id=140634=edit Screenshot with missing translation In reminder window, the caption "Dismiss All" is not translated into German. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 439769] Akonadi fails with Mariadb 10.6.3
https://bugs.kde.org/show_bug.cgi?id=439769 Christophe Giboudeaux changed: What|Removed |Added CC||timo...@mindspring.com --- Comment #15 from Christophe Giboudeaux --- *** Bug 440777 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 440777] Akonadi crashed when reading IMAP inbox.
https://bugs.kde.org/show_bug.cgi?id=440777 Christophe Giboudeaux changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Christophe Giboudeaux --- Probably a duplicate bug if that started yesterday *** This bug has been marked as a duplicate of bug 439769 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 440777] Akonadi crashed when reading IMAP inbox.
https://bugs.kde.org/show_bug.cgi?id=440777 --- Comment #1 from Christopher Yeleighton --- Created attachment 140632 --> https://bugs.kde.org/attachment.cgi?id=140632=edit New crash information added by DrKonqi akonadiserver (5.17.3 (21.04.3)) using Qt 5.15.2 - What I was doing when the application crashed: I was trying to delete a message from my INBOX. -- Backtrace (Reduced): #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #7 0x7f14bdfe1864 in __GI_abort () at abort.c:79 [...] #9 0x7f14be04273c in malloc_printerr (str=str@entry=0x7f14be14e5a0 "tcache_thread_shutdown(): unaligned tcache chunk detected") at malloc.c:5626 #10 0x7f14be04791c in tcache_thread_shutdown () at malloc.c:3131 #11 __malloc_arena_thread_freeres () at /usr/src/debug/glibc-2.33-9.1.x86_64/malloc/arena.c:1001 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 440777] Akonadi crashed when reading IMAP inbox.
https://bugs.kde.org/show_bug.cgi?id=440777 Christopher Yeleighton changed: What|Removed |Added CC||giecr...@stegny.2a.pl -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 440831] New: Segmentation Fault on syncing MeContact
https://bugs.kde.org/show_bug.cgi?id=440831 Bug ID: 440831 Summary: Segmentation Fault on syncing MeContact Product: Akonadi Version: 5.17.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: EWS Resource Assignee: kdepim-bugs@kde.org Reporter: merl.andr...@outlook.com CC: kri...@op.pl Target Milestone: --- Created attachment 140630 --> https://bugs.kde.org/attachment.cgi?id=140630=edit gdb backtrace of segfault SUMMARY At least some accounts of outlook.com do have one element in MeContact. (tested with two separated accounts, same behavior). On trying to sync this element a Segmentation Fault occurs. This Segmentation Fault appears only if the element is not locally available already. STEPS TO REPRODUCE 1. Create an outlook.com account. Account must have one element in MeContact (element type EwsItemTypeItem or 0) 2. Add account to Akonadi. 3. Open akonadiconsole and synchronize all elements of the resource. OBSERVED RESULT As soon as the synchronizing process tries to sync MeContact a Segmentation Fault occurs. EXPECTED RESULT No Segmentation Faults at all. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux Kernel 5.1.9-arch1-1 (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I'm no expert at this (RF Engineer) but I was able to find this log message org.kde.pim.ews: "Could not find handler for item type 0" after which a nullptr is returned. So I thought maybe someone tries to access this nullptr. I managed to make a debug build and get gdb to work. back trace is attached. In ewsfetchitemsjob.cpp:300 we can find this: QString mimeType = EwsItemHandler::itemHandler(type)->mimeType(); As I understand it EwsItemTypeItem does not have a itemHandler and therefor creating it returns a nullptr and calling mimeType() gets me a Segmentation Fault. To prevent it I tested an addition where I firstly check if there is a nullptr and skip the element if itemHanlder(type) returns nullptr. This removed the issue. -- You are receiving this mail because: You are the assignee for the bug.
[Spam] [Bug 440820] How to get a cash app refund by raising a dispute?
https://bugs.kde.org/show_bug.cgi?id=440820 Ben Cooksley changed: What|Removed |Added Assignee|kdepim-bugs@kde.org |n...@kde.org Version|5.17.80 |unspecified Component|kontact plugin |Spam Product|akregator |Spam -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 440820] New: How to get a cash app refund by raising a dispute?
https://bugs.kde.org/show_bug.cgi?id=440820 Bug ID: 440820 Summary: How to get a cash app refund by raising a dispute? Product: akregator Version: 5.17.80 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: kontact plugin Assignee: kdepim-bugs@kde.org Reporter: js8435...@gmail.com Target Milestone: --- Raising a dispute is another way to request a refund on a cash app. If you are not getting the refund from the merchant by raising a refund request, then you have to raise a dispute for this. We recommend you contact our experts to know the process to get a cash app refund by raising a dispute. https://www.numbers-for-support.com/blog/cash-app-refund/ EXPECTED RESULT 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.
