[Akonadi] [Bug 440781] New: Kmail fails to append item/ akonadi db states wrong date format
https://bugs.kde.org/show_bug.cgi?id=440781
Bug ID: 440781
Summary: Kmail fails to append item/ akonadi db states wrong
date format
Product: Akonadi
Version: 5.17.90
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: grave
Priority: NOR
Component: IMAP resource
Assignee: kdepim-bugs@kde.org
Reporter: s.pa...@spiekerbros.com
Target Milestone: ---
SUMMARY
Since last update Kmail/ Akonadi fails to get new email from IMAP server. Kmail
reports "failed to append item" when synchronising mailbox. The Akonadi error
log states:
2021-08-09T14:00:17 [CRITICAL] org.kde.pim.akonadiserver: DATABASE ERROR:
2021-08-09T14:00:17 [CRITICAL] org.kde.pim.akonadiserver: Error code: "1292"
2021-08-09T14:00:17 [CRITICAL] org.kde.pim.akonadiserver: DB error:
"Incorrect datetime value: '2021-08-09T12:00:17Z' for column
`akonadi`.`pimitemtable`.`datetime` at row 1"
2021-08-09T14:00:17 [CRITICAL] org.kde.pim.akonadiserver: Error text:
"Incorrect datetime value: '2021-08-09T12:00:17Z' for column
`akonadi`.`pimitemtable`.`datetime` at row 1 QMYSQL: Unable to execute query"
2021-08-09T14:00:17 [CRITICAL] org.kde.pim.akonadiserver: Values: QMap((":0",
QVariant(int, 0))(":1", QVariant(QString, "6773"))(":2", QVariant(QString,
""))(":3", QVariant(QString, ""))(":4", QVariant(qlonglong, 21))(":5",
QVariant(qlonglong, 3))(":6", QVariant(QDateTime, QDateTime(2021-08-09
12:00:17.471 UTC Qt::UTC)))(":7", QVariant(QDateTime, QDateTime(2021-08-09
12:00:17.471 UTC Qt::UTC)))(":8", QVariant(bool, false))(":9",
QVariant(qlonglong, 2491777)))
2021-08-09T14:00:17 [CRITICAL] 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)"
2021-08-09T14:00:17 [WARN ] org.kde.pim.akonadiserver: Error during insertion
into table "PimItemTable" "Incorrect datetime value: '2021-08-09T12:00:17Z' for
column `akonadi`.`pimitemtable`.`datetime` at row 1 QMYSQL: Unable to execute
query"
2021-08-09T14:00:17 [WARN ] org.kde.pim.akonadiserver: Error while handling
command CreateItem on connection akonadi_imap_resource_0 (0x559fee8e4a30)
2021-08-09T14:00:26 [INFO ] org.kde.pim.akonadiserver: Subscriber
"MessageViewerMonitor - 94908118964128" disconnected
2021-08-09T14:00:26 [INFO ] org.kde.pim.akonadiserver: Subscriber
"MessageListTagMonitor - 94908119944352" disconnected
2021-08-09T14:00:26 [INFO ] org.kde.pim.akonadiserver: Subscriber "KMail Kernel
ETM - 94908118071664" disconnected
2021-08-09T14:00:26 [INFO ] org.kde.pim.akonadiserver: Subscriber
"SpecialCollectionsMonitor - 94908118206576" disconnected
2021-08-09T14:00:26 [INFO ] org.kde.pim.akonadiserver: Subscriber
"FilterManagerTagMonitor - 94908124039120" disconnected
2021-08-09T14:00:26 [INFO ] org.kde.pim.akonadiserver: Subscriber
"TagActionManagerMonitor - 94908124186832" disconnected
This even happens with a completely new user set up. The directory structure as
present on the IMAP server is correctly created in KMAIL upon setup, but
retrieving messages fails with the above error.
STEPS TO REPRODUCE
1. Try to get new mail from imap server
OBSERVED RESULT
KMAIL states "failed to append item" and does not show emails coming in upon
sync; as a result all email folders are empty and stay empty when setting up as
a new user.
EXPECTED RESULT
Emails actually show up in Kmail
I´ĺl happily create any logfile or anything else you need to squash this ugly
bug
OS: OpenSuse Tumbleweed
KDE:5.22.4
KDE Framework: 5.84.0
--
You are receiving this mail because:
You are the assignee for the bug.
[Akonadi] [Bug 420495] New: Akonadi Crashes upon removal of duplicates in folder
https://bugs.kde.org/show_bug.cgi?id=420495 Bug ID: 420495 Summary: Akonadi Crashes upon removal of duplicates in folder 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: s.pa...@spiekerbros.com Target Milestone: --- Application: akonadiserver (5.13.3 (19.12.3)) Qt Version: 5.14.1 Frameworks Version: 5.69.0 Operating System: Linux 5.6.4-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: As, once again, many duplicates are showing up in some folders I wanted to use the "remove duplicates in folder" functionality. This makes akonadi crash every time. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1292ce6800 (LWP 18221))] Thread 6 (Thread 0x7f12897fa700 (LWP 18231)): #0 0x7f1293a5e629 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f1293a13324 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1293a1345f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f1295488c0b in QEventDispatcherGlib::processEvents (this=0x7f126c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f1295430b9b in QEventLoop::exec (this=this@entry=0x7f12897f9da0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7f129525b5ce in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7f129525c698 in QThreadPrivate::start (arg=0x55c9d81878c0) at thread/qthread_unix.cpp:342 #7 0x7f1294722efa in start_thread () from /lib64/libpthread.so.0 #8 0x7f1295c243bf in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f1289ffb700 (LWP 18230)): #0 0x7f1294729795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f12952621db in QWaitConditionPrivate::wait (deadline=..., this=0x55c9d8159a30) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x55c9d8187170, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f1295262299 in QWaitCondition::wait (this=this@entry=0x55c9d8187168, mutex=mutex@entry=0x55c9d8187170, time=time@entry=18446744073709551615) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x55c9d804560c in Akonadi::Server::SearchTaskManager::searchLoop (this=0x55c9d8187140) at /usr/src/debug/akonadi-server-19.12.3-1.1.x86_64/src/server/search/searchtaskmanager.cpp:221 #5 0x7f129545ea19 in QObject::event (this=0x55c9d8187140, e=0x55c9d8187680) at kernel/qobject.cpp:1339 #6 0x7f1295431fdf in doNotify (event=0x55c9d8187680, receiver=0x55c9d8187140) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:153 #7 QCoreApplication::notify (event=0x55c9d8187680, receiver=0x55c9d8187140, this=) at kernel/qcoreapplication.cpp:1168 #8 QCoreApplication::notifyInternal2 (receiver=0x55c9d8187140, event=0x55c9d8187680) at kernel/qcoreapplication.cpp:1092 #9 0x7f1295434794 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55c9d81872f0) at kernel/qcoreapplication.cpp:1832 #10 0x7f1295489573 in postEventSourceDispatch (s=0x7f1268004fe0) at kernel/qeventdispatcher_glib.cpp:277 #11 0x7f1293a13048 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #12 0x7f1293a133d0 in ?? () from /usr/lib64/libglib-2.0.so.0 #13 0x7f1293a1345f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #14 0x7f1295488bee in QEventDispatcherGlib::processEvents (this=0x7f1268000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #15 0x7f1295430b9b in QEventLoop::exec (this=this@entry=0x7f1289ffada0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #16 0x7f129525b5ce in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #17 0x7f129525c698 in QThreadPrivate::start (arg=0x55c9d8187240) at thread/qthread_unix.cpp:342 #18 0x7f1294722efa in start_thread () from /lib64/libpthread.so.0 #19 0x7f1295c243bf in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f128a7fc700 (LWP 18229)): [KCrash Handler] #6 0x7f12952dca4e in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x0) at /usr/include/c++/9/bits/atomic_base.h:413 #7 QAtomicOps::loadRelaxed (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #8 QBasicAtomicInteger::loadRelaxed (this=0x0) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107 #9 QtPrivate::RefCount::deref
[korganizer] [Bug 406411] Korganizer daemon closes when plasma starts
https://bugs.kde.org/show_bug.cgi?id=406411 Frits Spieker changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #14 from Frits Spieker --- Hi. I just got an update to the 19. series of KDE on Tumbleweed and now Kontact and Akonadi have been updated as well (5.11), I can happily report that the bug indeed seems to have been fixed. No more crash of the reminder deamon. Suggest to close. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #212 from Frits Spieker --- (In reply to Eric Depagne from comment #203) > (In reply to Tristan Miller from comment #202) > > Is this problem still reproducible in the latest version of KMail? There > > haven't been any comments on this bug in over a year; I'm wondering if > > that's because the problem has been fixed or because it has driven most of > > the user base away. I'd love to return to using KMail but can't as long as > > this message duplication problem persists. (I was getting dozens of > > duplicated messages every day, which was too much to put up with.) > > It has been fixed I believe, since it disappeared from my kmail in 2015. Most definitely not fixed. Still run into it multiple times per day with some messages showing up 5 or more times. Sometimes I just delete the entire folder and filter and just set everything up again. Sometimes seems to do the trick. I have been unable to find any logic behind why some messages get duplicated where others don't (in the same folder). -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 406411] Korganizer daemon closes when plasma starts
https://bugs.kde.org/show_bug.cgi?id=406411 --- Comment #4 from Frits Spieker --- That was fast ;-) -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 406411] Korganizer daemon closes when plasma starts
https://bugs.kde.org/show_bug.cgi?id=406411 --- Comment #2 from Frits Spieker --- Created attachment 119340 --> https://bugs.kde.org/attachment.cgi?id=119340=edit Korganizer Reminder Daemon crashes at plasma login. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 406411] Korganizer daemon closes when plasma starts
https://bugs.kde.org/show_bug.cgi?id=406411 Frits Spieker changed: What|Removed |Added CC||s.pa...@spiekerbros.com --- Comment #1 from Frits Spieker --- I just updated my Tumbleweed as well and get exactly the same crash. I'll upload a crash-log. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405434] KMail crashes when trying to switch on add-blocker
https://bugs.kde.org/show_bug.cgi?id=405434 --- Comment #3 from Frits Spieker --- Hi, Still crashes reliably. Even a fresh install of Tumbleweed did not help. It's a bug I totally can work around and live with, so please feel free to put it on hold. Cheers, Frits -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405434] KMail crashes when trying to switch on add-blocker
https://bugs.kde.org/show_bug.cgi?id=405434 --- Comment #2 from Frits Spieker --- Created attachment 119300 --> https://bugs.kde.org/attachment.cgi?id=119300=edit log for Kontact crash whilst enabling add blocker -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405434] New: KMail crashes when trying to switch on add-blocker
https://bugs.kde.org/show_bug.cgi?id=405434 Bug ID: 405434 Summary: KMail crashes when trying to switch on add-blocker Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: s.pa...@spiekerbros.com Target Milestone: --- Application: kontact (5.10.2) Qt Version: 5.12.0 Frameworks Version: 5.55.0 Operating System: Linux 4.20.13-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Switched on add-blocker, selected a "addblocking list" from the drop-down list and clicked OK. Crashed immediately. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb22e243f40 (LWP 8736))] Thread 27 (Thread 0x7fb1250f3700 (LWP 9233)): #0 0x7fb23c60f428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb2361b7c57 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fb2361b85aa in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fb2361b8692 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fb236176131 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fb236178c67 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fb236179254 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fb2361ba7b1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fb23c608fab in start_thread () at /lib64/libpthread.so.0 #9 0x7fb23d5df6af in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7fb1e57fa700 (LWP 9227)): #0 0x7fb23c60f428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb23d91e595 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb23d91e6c5 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7fb23d91c7c2 in () at /usr/lib64/libQt5Core.so.5 #4 0x7fb23d9186e2 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fb23c608fab in start_thread () at /lib64/libpthread.so.0 #6 0x7fb23d5df6af in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7fb20b7fe700 (LWP 9220)): #0 0x7fb23d5da2f9 in syscall () at /lib64/libc.so.6 #1 0x7fb23d91aa04 in QSemaphore::acquire(int) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb23c75abd4 in () at /usr/lib64/libQt5Network.so.5 #3 0x7fb23d9186e2 in () at /usr/lib64/libQt5Core.so.5 #4 0x7fb23c608fab in start_thread () at /lib64/libpthread.so.0 #5 0x7fb23d5df6af in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7fb126237700 (LWP 9219)): #0 0x7fb23d5d4ae9 in poll () at /lib64/libc.so.6 #1 0x7fb23bc1f156 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb23bc1f27c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb23db22c5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb23dacd4fb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb23d917396 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fb23d9186e2 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fb23c608fab in start_thread () at /lib64/libpthread.so.0 #8 0x7fb23d5df6af in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7fb20a7fc700 (LWP 9024)): #0 0x7fb21830e48f in pa_srbchannel_read () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #1 0x7fb21830a9f8 in () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #2 0x7fb21830d74b in () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #3 0x7fb21830dae9 in () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #4 0x7fb21830e33a in () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #5 0x7fb218372ca8 in pa_mainloop_dispatch () at /usr/lib64/libpulse.so.0 #6 0x7fb218372f7c in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #7 0x7fb218373020 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #8 0x7fb218381039 in () at /usr/lib64/libpulse.so.0 #9 0x7fb21831de28 in () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #10 0x7fb23c608fab in start_thread () at /lib64/libpthread.so.0 #11 0x7fb23d5df6af in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7fb127fff700 (LWP 8789)): #0 0x7fb23d5d4ae9 in poll () at /lib64/libc.so.6 #1 0x7fb23bc1f156 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb23bc1f27c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb23db22c5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb23dacd4fb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb23d917396 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fb23d9186e2 in ()
[kontact] [Bug 400901] New: KMail crashes when closing a message window after search
https://bugs.kde.org/show_bug.cgi?id=400901 Bug ID: 400901 Summary: KMail crashes when closing a message window after search Product: kontact Version: 5.9.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: s.pa...@spiekerbros.com Target Milestone: --- Application: kontact (5.9.2) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.18.15-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Searched for a specific message using Tools > Find Message. Open message (double click on search result), close message (clicking on the "X"), Kmail crashes every time. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f65bb454ec0 (LWP 3656))] Thread 32 (Thread 0x7f646685d700 (LWP 7285)): #0 0x7f65cde608c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f65c6f25d37 in base::ConditionVariable::TimedWait () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:120 #2 0x7f65c6f27a0a in base::WaitableEvent::TimedWaitUntil () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:221 #3 0x7f65c6f27af2 in base::WaitableEvent::TimedWait () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:161 #4 0x7f65c6f2c8b1 in base::internal::SchedulerWorker::Delegate::WaitForWork () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:171 #5 0x7f65c6f2dd91 in base::internal::SchedulerWorker::Thread::ThreadMain () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:68 #6 0x7f65c6f381c1 in ThreadFunc () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:75 #7 0x7f65cde5a554 in start_thread () from /lib64/libpthread.so.0 #8 0x7f65cefc4ccf in clone () from /lib64/libc.so.6 Thread 31 (Thread 0x7f65957fa700 (LWP 7268)): #0 0x7f65cde608c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f65c6f25d37 in base::ConditionVariable::TimedWait () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:120 #2 0x7f65c6f27a0a in base::WaitableEvent::TimedWaitUntil () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:221 #3 0x7f65c6f27af2 in base::WaitableEvent::TimedWait () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:161 #4 0x7f65c6f2c8b1 in base::internal::SchedulerWorker::Delegate::WaitForWork () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:171 #5 0x7f65c6f2dd91 in base::internal::SchedulerWorker::Thread::ThreadMain () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:68 #6 0x7f65c6f381c1 in ThreadFunc () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:75 #7 0x7f65cde5a554 in start_thread () from /lib64/libpthread.so.0 #8 0x7f65cefc4ccf in clone () from /lib64/libc.so.6 Thread 30 (Thread 0x7f6476a45700 (LWP 7246)): #0 0x7f65cefba2c9 in poll () from /lib64/libc.so.6 #1 0x7f65cc9fef46 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f65cc9ff06c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f65cf6dfadb in QEventDispatcherGlib::processEvents (this=0x7f657c008d40, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f65cf68cadb in QEventLoop::exec (this=this@entry=0x7f6476a44be0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f65cf4dbde6 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f65cf4e59b7 in QThreadPrivate::start (arg=0x5650a2ffb6d0) at thread/qthread_unix.cpp:367 #7 0x7f65cde5a554 in start_thread () from /lib64/libpthread.so.0 #8 0x7f65cefc4ccf in clone () from /lib64/libc.so.6 Thread 29 (Thread 0x7f648938b700 (LWP 3778)): #0 0x7f65cca45426 in g_private_get () from /usr/lib64/libglib-2.0.so.0 #1 0x7f65cca27950 in g_thread_self () from /usr/lib64/libglib-2.0.so.0 #2 0x7f65cc9fdf9e in g_main_context_acquire () from /usr/lib64/libglib-2.0.so.0 #3 0x7f65cc9fee05 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f65cc9ff06c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f65cf6dfadb in QEventDispatcherGlib::processEvents (this=0x7f647c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f65cf68cadb in QEventLoop::exec (this=this@entry=0x7f648938abe0, flags=..., flags@entry=...) at
[Akonadi] [Bug 398282] Akonadi crashes frequently since upgrade to 5.9.0
https://bugs.kde.org/show_bug.cgi?id=398282 --- Comment #3 from Frits Spieker --- Hi. Updated PC today and so far (knock on wood) it seems indeed to be fixed. So far can consider as resolved indeed. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 398282] New: Akonadi crashes frequently since upgrade to 5.9.0
https://bugs.kde.org/show_bug.cgi?id=398282 Bug ID: 398282 Summary: Akonadi crashes frequently since upgrade to 5.9.0 Product: Akonadi Version: 5.9.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: libakonadi Assignee: kdepim-bugs@kde.org Reporter: s.pa...@spiekerbros.com Target Milestone: --- Created attachment 114789 --> https://bugs.kde.org/attachment.cgi?id=114789=edit backtrace for akonadi crash whilst trying to filter messages Application: akonadiserver (5.9.0) Qt Version: 5.11.1 Frameworks Version: 5.49.0 Operating System: Linux 4.18.5-1-default x86_64 Distribution: "openSUSE Tumbleweed" The backtrace is too long to be reported via the automatic reporting wizzard nor can it be pasted into the comment window. (too many characters) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 336581] accidental database loss causes Akonadi / KMail to silently break correct folder assignments
https://bugs.kde.org/show_bug.cgi?id=336581 Frits Spieker <s.pa...@spiekerbros.com> changed: What|Removed |Added CC||s.pa...@spiekerbros.com --- Comment #12 from Frits Spieker <s.pa...@spiekerbros.com> --- As to broken architecture... The dreaded KMail hanging with the message "Retrieving message/ folder content screen" showing indefinitely is back. On top of that KMail now always crashes when writing a new email using autofill for the receiver (start typing the email address and when trying to select one of the suggestions made, KMail will crash). I will search if a bug report has been filed for that one and if not I will file it myself. KMail/ Akonadi had been "OK-ish" for a couple of months (to the extent I even removed my backup solution of Thunderbird), but it is back to being near useless again. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 379585] Kontakt crashed upon restarting to get rid of "Retrieving Folder Content" screen
https://bugs.kde.org/show_bug.cgi?id=379585 --- Comment #3 from Frits Spieker <s.pa...@spiekerbros.com> --- Hi, I tried every trick in the book to re-create the bug, but no show. Might be also because since reporting it there were some updates to (among others) akonadi which made things a bit more stable. Consider it closed/ resolved for now. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 379585] Kontakt crashed upon restarting to get rid of "Retrieving Folder Content" screen
https://bugs.kde.org/show_bug.cgi?id=379585 --- Comment #2 from Frits Spieker <s.pa...@spiekerbros.com> --- Will do. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 379585] New: Kontakt crashed upon restarting to get rid of "Retrieving Folder Content" screen
https://bugs.kde.org/show_bug.cgi?id=379585 Bug ID: 379585 Summary: Kontakt crashed upon restarting to get rid of "Retrieving Folder Content" screen Product: kontact Version: 5.4.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: s.pa...@spiekerbros.com Target Milestone: --- Application: kontact (5.4.3) Qt Version: 5.7.1 Frameworks Version: 5.33.0 Operating System: Linux 4.10.12-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: As I was hit again with the "Retrieving Folder Content" on one of the folders which contains duplicates due to the filtering bug, I ran: - akonadictl fsck - akonadictl vacuum - akonadictl restart Closed Kontakt, restarted it which made kontakt crash. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f43f5b73940 (LWP 18809))] Thread 35 (Thread 0x7f43c11d2700 (LWP 27791)): #0 0x7f43ee43ddb3 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f43e537e052 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f43e538ceb0 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f43e538d3e3 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f43e538699c in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f43ee437537 in start_thread () at /lib64/libpthread.so.0 #6 0x7f43f25a204f in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7f42b700 (LWP 27789)): #0 0x7f43f25944bd in read () at /lib64/libc.so.6 #1 0x7f43ec22df00 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f43ec1e9562 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f43ec1e9a34 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f43ec1e9bac in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f43f30d31bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f43f307cb1a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f43f2eaa813 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f43f2eaf4c8 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f43ee437537 in start_thread () at /lib64/libpthread.so.0 #10 0x7f43f25a204f in clone () at /lib64/libc.so.6 Thread 33 (Thread 0x7f429047b700 (LWP 22551)): #0 0x7f43ee43d9a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f42c9167eb3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f42c949e2c1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f43ee437537 in start_thread () at /lib64/libpthread.so.0 #4 0x7f43f25a204f in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7f4290c7c700 (LWP 22550)): #0 0x7f43ee43d9a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f42c9167eb3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f42c949e2c1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f43ee437537 in start_thread () at /lib64/libpthread.so.0 #4 0x7f43f25a204f in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7f429147d700 (LWP 22549)): #0 0x7f43ee43d9a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f42c9167eb3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f42c949e2c1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f43ee437537 in start_thread () at /lib64/libpthread.so.0 #4 0x7f43f25a204f in clone () at /lib64/libc.so.6 Thread 30 (Thread 0x7f4291c7e700 (LWP 22548)): #0 0x7f43ee43d9a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f42c9167eb3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f42c949e2c1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f43ee437537 in start_thread () at /lib64/libpthread.so.0 #4 0x7f43f25a204f in clone () at /lib64/libc.so.6 Thread 29 (Thread 0x7f428d79d700 (LWP 22547)): #0 0x7f43ee43d9a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f42c9167eb3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f42c949e2c1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f43ee437537 in start_thread () at /lib64/libpthread.so.0 #4 0x7f43f25a204f in clone () at /lib64/libc.so.6 Thread 28 (Thread 0x7f4273fff700 (LWP 22546)): #0 0x7f43ee43d9a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f42c9167eb3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f42c949e2c1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f43ee437537 in start_thread () at /lib64/libpthread.so.0 #4 0x7f43f25a204f in clone () at /lib64/libc.so.6 Thread 27 (Thread 0x7f428c93b700 (LWP 22545)): #0 0x7f43ee43d9a6 in pthread_cond_wait@@GLIBC_2.3.2 ()
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #192 from Frits Spieker <s.pa...@spiekerbros.com> --- Excellent! Good to know there is some progress. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #190 from Frits Spieker <s.pa...@spiekerbros.com> --- But is one of the developers actually looking at this? The duplication of the messages, combined with the akonadi hanging itself out to dry when deleting messages (resulting in the famous "retrieving folder content" screen) makes KMail basically unusable. I'm really baffled how such a crucial piece of software (unless developers use other program to read email) can be so broken for so long. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 Frits Spieker <s.pa...@spiekerbros.com> changed: What|Removed |Added CC||s.pa...@spiekerbros.com --- Comment #181 from Frits Spieker <s.pa...@spiekerbros.com> --- (In reply to Andreas Mahel from comment #179) > I'm experiencing email duplication after filter activity as well (openSUSE > Tumbleweed, most recent versions). > > The filters move mainly mailing list traffic from a POP3 account into local > sub folders. > > Duplication happens both for automatic filtering as well as executing the > filters manually. > > In most cases, the duplicated entry shows a different size than the original > one (but not always). > > On top, selecting any of the two entries will result in Kmail endlessly > waiting for Akonadi. > > A akonadictl fsck and vacuum does not remove the duplicates; also a "Remove > duplicate emails" from the "Folder" menu does'nt, and ends with an error > message. > > In the meantime I have deleted the Akonadi database several times, as well > as re-created the filters manually, to no avail. > > As a workaround for myself I've written a short SQL script to show / delete > the offending rows from the database (from within akonadiconsole) - this is > tedious, but at least allows me to read all mails. > > (How) can I gather more information about what exactly is going on? Both > Kmail and Akonadi are kind of cryptic in their output - is there a way to > increase verbosity? Exactly as you describe. Sometimes I can get things going again for a short time by doing a restart of akonadi, but lately more often than not this causes akonadi to crash. Weird thing though; in some sub-folders the "delete duplicates" functionality works fine, in other sub-folders (underneath the same account) it will indeed hang everything solid with an error message at the end, just like you describe. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 376808] Akonadi stuck on retrieving folder content, ItemFetchJob Stuck, Failed: Multiple Merge Candidates
https://bugs.kde.org/show_bug.cgi?id=376808 Frits Spieker <s.pa...@spiekerbros.com> changed: What|Removed |Added CC||s.pa...@spiekerbros.com --- Comment #6 from Frits Spieker <s.pa...@spiekerbros.com> --- Same problem here. Updated on OpenSUSE Tumbleweed. The Kmail/ Akonadi combo is very much a "hit and miss" at the moment. Sometimes I can read quite some emails in a row, sometimes I get the "Retrieving Folder Content" message for hours on end. In the past restarting akonadi seemed to help, but no longer. Akonadi is at 5.4.3. I'll be happy to provide any logs, info whatever that could help in fixing this. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 376923] New: Akonadi crashes on restart when KMail hangs on "Retrieving folder content" (POP accounts). Akonadi also creates many dupplicates.
https://bugs.kde.org/show_bug.cgi?id=376923 Bug ID: 376923 Summary: Akonadi crashes on restart when KMail hangs on "Retrieving folder content" (POP accounts). Akonadi also creates many dupplicates. Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: s.pa...@spiekerbros.com Target Milestone: --- Application: akonadiserver (5.4.2) Qt Version: 5.7.1 Frameworks Version: 5.30.0 Operating System: Linux 4.9.11-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: When KMail hangs on "Retrieving Folder content" it sometimes helps to restart akonadi. However, since last update this does not help anymore; akonadi just crashes on the restart. Also, many duplicates and duplicates of duplicates are being created upon filtering. - Unusual behavior I noticed: The crash can be reproduced sometimes. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f63648868c0 (LWP 6998))] Thread 35 (Thread 0x7f62b4ff9700 (LWP 7192)): #0 0x7f635f24af64 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f635f20588a in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f635f2059ac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f636312418b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f63630cdaea in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f6362efb813 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f6362f004c8 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7f6361422454 in start_thread () from /lib64/libpthread.so.0 #8 0x7f63625f637f in clone () from /lib64/libc.so.6 Thread 34 (Thread 0x7f62b57fa700 (LWP 7189)): #0 0x7f63625ed66d in poll () from /lib64/libc.so.6 #1 0x7f635f205896 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f635f2059ac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f636312418b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f63630cdaea in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f6362efb813 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f6362f004c8 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7f6361422454 in start_thread () from /lib64/libpthread.so.0 #8 0x7f63625f637f in clone () from /lib64/libc.so.6 Thread 33 (Thread 0x7f62b5ffb700 (LWP 7184)): #0 0x7f63625ed66d in poll () from /lib64/libc.so.6 #1 0x7f635f205896 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f635f2059ac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f636312418b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f63630cdaea in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f6362efb813 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f6362f004c8 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7f6361422454 in start_thread () from /lib64/libpthread.so.0 #8 0x7f63625f637f in clone () from /lib64/libc.so.6 Thread 32 (Thread 0x7f62b67fc700 (LWP 7180)): #0 0x7f635f24af64 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f635f204d70 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f635f2057bb in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f635f2059ac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f636312418b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f63630cdaea in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f6362efb813 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7f6362f004c8 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7f6361422454 in start_thread () from /lib64/libpthread.so.0 #9 0x7f63625f637f in clone () from /lib64/libc.so.6 Thread 31 (Thread 0x7f62b77fe700 (LWP 7176)): [KCrash Handler] #6 0x7f63625415af in raise () from /lib64/libc.so.6 #7 0x7f63625429aa in abort () from /lib64/libc.so.6 #8 0x7f6362b5b69d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/libstdc++.so.6 #9 0x7f6362b59676 in ?? () from /usr/lib64/libstdc++.so.6 #10 0x7f6362b596c1 in std::terminate() () from /usr/lib64/libstdc++.so.6 #11 0x7f6362b598d8 in __cxa_throw () from /usr/lib64/libstdc++.so.6 #12 0x7f6363fdfc02 in Akonadi::Protocol::DataStream::operator<< (this=, val=) at
[Akonadi] [Bug 340046] after long inactivity (sleep) mailfilter agent remains at 0% indefinitely (and kmail at "Retrieving folder contents")
https://bugs.kde.org/show_bug.cgi?id=340046 Frits Spieker <s.pa...@spiekerbros.com> changed: What|Removed |Added CC||s.pa...@spiekerbros.com --- Comment #6 from Frits Spieker <s.pa...@spiekerbros.com> --- This ugly bug also rears its head in Opensuse Tumbleweed. akonadi is at version 16.12.1-1.1. As is kmail for that matter. Sometimes restarting akonadi does seem to help but never long. I can normally read some email, but then (without any pattern that I can find) the "retrieving etc" will occupy the message pane. As far as I can tell it most of the times starts when trying to read email from a POP3 account, but when it does it will also block IMAP folders. Any suggestions on producing usable input for debugging very welcome. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 267864] migration of akonadi_mixedmaildir_resource fails
https://bugs.kde.org/show_bug.cgi?id=267864 --- Comment #4 from Frits Spieker <s.pa...@spiekerbros.com> --- AFAIK it works fine now. I have quite some local mail folders and they all show up just fine. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 246195] Cannot create Google Contacts akonadi resource [strlen, strdup,extract_and_check_multi, ..., gcal_get_contacts]
https://bugs.kde.org/show_bug.cgi?id=246195 --- Comment #51 from Frits Spieker <s.pa...@spiekerbros.com> --- No longer present. Works fine now. -- You are receiving this mail because: You are on the CC list for the bug.
[kmail2] [Bug 310897] Reading mbox files is extremely slow and often fails to show message body
https://bugs.kde.org/show_bug.cgi?id=310897 --- Comment #4 from Frits Spieker <s.pa...@spiekerbros.com> --- As far as I know the bug is no longer there. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 369118] New: Multiple selection of "find in message" causes crash
https://bugs.kde.org/show_bug.cgi?id=369118 Bug ID: 369118 Summary: Multiple selection of "find in message" causes crash Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: s.pa...@spiekerbros.com Application: kontact (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.7.3-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was searching for a specific message so selected "find in message". The "search box" appeared at the bottom of the screen (so far so good). When I clicked "search in message" again, the application crashed. Tried again, but have not yet been able to reproduce. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbec73f25c0 (LWP 3112))] Thread 41 (Thread 0x7fbd177fe700 (LWP 3258)): #0 0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbda9ffb353 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fbdaa331971 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbec3da03ff in clone () at /lib64/libc.so.6 Thread 40 (Thread 0x7fbd17fff700 (LWP 3257)): #0 0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbda9ffb353 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fbdaa331971 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbec3da03ff in clone () at /lib64/libc.so.6 Thread 39 (Thread 0x7fbd1cdf4700 (LWP 3256)): #0 0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbda9ffb353 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fbdaa331971 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbec3da03ff in clone () at /lib64/libc.so.6 Thread 38 (Thread 0x7fbd1d5f5700 (LWP 3255)): #0 0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbda9ffb353 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fbdaa331971 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbec3da03ff in clone () at /lib64/libc.so.6 Thread 37 (Thread 0x7fbd1ddf6700 (LWP 3254)): #0 0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbda9ffb353 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fbdaa331971 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbec3da03ff in clone () at /lib64/libc.so.6 Thread 36 (Thread 0x7fbd1e5f7700 (LWP 3253)): #0 0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbda9ffb353 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fbdaa331971 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbec3da03ff in clone () at /lib64/libc.so.6 Thread 35 (Thread 0x7fbd1edf8700 (LWP 3252)): #0 0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbda9ffa201 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fbdaa331971 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbec3da03ff in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7fbd77fff700 (LWP 3251)): #0 0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbdaa300c4b in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fbdaa300c89 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbec3da03ff in clone () at /lib64/libc.so.6 Thread 33 (Thread 0x7fbd6e6ee700 (LWP 3214)): #0 0x7fbec3dacc1f in __libc_enable_asynccancel () at /lib64/libc.so.6 #1 0x7fbec3d976e2 in poll () at /lib64/libc.so.6 #2 0x7fbebeff5016 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fbebeff512c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fbec48d6aab in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fbd640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7fbec487e6fa in QEventLoop::exec(QFlags) (this=this@entry=0x7fbd6e6edc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fbec46a43c3 in QThread::exec() (this=) at thread/qthread.cpp:500 #7 0x7fbec46a92e8 in QThreadPrivate::start(void*) (arg=0x15e3da0) at
[Akonadi] [Bug 367846] KMail2 and akonadiconsole continuously lose connection to akonadi server - happens every 30 secs to 2 minutes.
https://bugs.kde.org/show_bug.cgi?id=367846 --- Comment #5 from Frits Spieker <s.pa...@spiekerbros.com> --- Not to be blunt, but deleting all imap accounts, dropping and recreating the akonadi database and recreating of all imap accounts is not what I would call resolved. It is a messy workaround and a very messy one at that. What about users that also still have pop3 email boxes? What about the less technical inclined? It's a messy workaround which hides a messy bug which is in need of a proper fix. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 367846] KMail2 and akonadiconsole continuously lose connection to akonadi server - happens every 30 secs to 2 minutes.
https://bugs.kde.org/show_bug.cgi?id=367846 Frits Spieker <s.pa...@spiekerbros.com> changed: What|Removed |Added CC||s.pa...@spiekerbros.com --- Comment #1 from Frits Spieker <s.pa...@spiekerbros.com> --- I am "glad" I am not the only one. Have exactly the same error. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 284252] possibility for user to control data location
https://bugs.kde.org/show_bug.cgi?id=284252 --- Comment #4 from Frits Spieker <s.pa...@spiekerbros.com> --- Hi Martin, Thank you very much for the very informative and lengthy answer. This is much appreciated! I had -almost- forgotten about it already again, but your email gives me some good ideas. I actually have a good NFS storage at home (with regular backups) and it really is worth looking into either storing it there or alternatively do it on a separate /Mail partition using some of the techniques you outline. So once again, thank you VERY much! At least it is a workable solution, although having an option in the " configure Kmail" where to store email would still be nice. A nice to have. Not a must to have. And I must say that KMail (and Kontakt) as a whole is actually behaving quite good lately. Still have the odd "duplicate messages" in folders sometimes, but have not been able to pinpoint what is causing it. I am really looking forward to the Plasma 5 version of Kontakt! Kind regards and my compliments to the development team! Frits -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 288364] Retrieving Folder Contents hanging without showing content
https://bugs.kde.org/show_bug.cgi?id=288364 --- Comment #43 from Frits Spieker s.pa...@spiekerbros.com --- Hi. Feel free to close. Seems to be working ok. Cheers, Frits On August 25, 2015 12:12:25 PM GMT+02:00, andreas.sturmlech...@gmail.com wrote: https://bugs.kde.org/show_bug.cgi?id=288364 --- Comment #42 from andreas.sturmlech...@gmail.com --- Can't say I've ever seen that error again since my previous message, and I'm (still) a permanent user of kmail2 - good to close? -- You are receiving this mail because: You voted for the bug. You are on the CC list for the bug. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 292767] KMail2 (4.8.0) incorrectly displays some messages (does not process the encoding)
https://bugs.kde.org/show_bug.cgi?id=292767 Frits Spieker s.pa...@spiekerbros.com changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #13 from Frits Spieker s.pa...@spiekerbros.com --- Hi, I had to install bogofilter again to test, but so far it seems to be behaving OK. PDF's arrive as normal attachments, don't get botched or anything like that. Seems resolved... -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 300159] Kontact crashes whilst accepting an invitation [@ MailCommon::Kernel::self]
https://bugs.kde.org/show_bug.cgi?id=300159 Frits Spieker s.pa...@spiekerbros.com changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #12 from Frits Spieker s.pa...@spiekerbros.com --- Hi, Seems to be fixed. I had to create an invite at work, sent it to my private email, clicked on accept and it beautifully got added to the calendar without any crashing. Well done! -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 288364] Retrieving Folder Contents hanging without showing content
https://bugs.kde.org/show_bug.cgi?id=288364 --- Comment #32 from Frits Spieker s.pa...@spiekerbros.com --- I am now on 4.10, RC2 and bug is still there. Going into its 3rd year almost without being fixed. *ANY* Developer out there; if you need data, examples, log files or whatever, just let me or other users know; we'll be more than happy to help and solve this bug. Just ignoring this bug does not make it go away; it might make the users go away which in the end also solves the problem. /cynism -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 288364] Retrieving Folder Contents hanging without showing content
https://bugs.kde.org/show_bug.cgi?id=288364 --- Comment #34 from Frits Spieker s.pa...@spiekerbros.com --- On Sunday 20 January 2013 10:14:36 you wrote: https://bugs.kde.org/show_bug.cgi?id=288364 --- Comment #33 from András Manţia aman...@kde.org --- Have you tried disabling nepomuk (desktop search) completely if it helps? BINGO!! Switched off nepomuk desktop search completely and as a result I now have a blindingly fast Kmail2, which is responsive and *immediately* shows the message content, no matter what message I click. Even works (as expected) whilst quickly scrolling through a long message list. Also; filtering works fast again. I just created an extra filter to move some messages in a particular folder to another one (based on a combination of sender and subject) and filtering the 500+ messages in that folder went faster than a blink of an eye. Trying to do something like that *with* nepomuk activated was a sure exercise in frustration. So now we have found the most likely culprit, where do we take this from here? Cheers and THANK YOU András for being the developer that -finally- asked the can you try this question. Cheers, Frits -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 288364] Retrieving Folder Contents hanging without showing content
https://bugs.kde.org/show_bug.cgi?id=288364 --- Comment #35 from Frits Spieker s.pa...@spiekerbros.com --- P.S. I am now on RC3 of 4.10 and with nepomuk enabled the bug immediately rears its ugly head again. Switch off Nepomuk and presto. Blindingly fast Kmail2 again. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 283080] Akonadi message Local Folders: Unsupported Type. Email from POP account disappear!
https://bugs.kde.org/show_bug.cgi?id=283080 --- Comment #4 from Frits Spieker s.pa...@spiekerbros.com --- I have not seen this message anymore for a long time. Personally I am more worried with bug 288364 - 'Retrieving Folder Contents hanging without showing content', which is making KMail2 if not virtually useless, than at least extremely difficult to work with. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 310897] Reading mbox files is extremely slow and often fails to show message body
https://bugs.kde.org/show_bug.cgi?id=310897 Frits Spieker s.pa...@spiekerbros.com changed: What|Removed |Added CC||s.pa...@spiekerbros.com --- Comment #1 from Frits Spieker s.pa...@spiekerbros.com --- Most likely the same bug as 288364 which has been around now for more than a year. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 288364] Retrieving Folder Contents hanging without showing content
https://bugs.kde.org/show_bug.cgi?id=288364 --- Comment #29 from Frits Spieker s.pa...@spiekerbros.com --- Is there any developer looking at this extremely annoying bug? Or is everybody celebrating making KDE the best release ever, totally ignoring that one of the core components (a lot of people do read email on their PC) is a piece of junk at the moment? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 288364] Retrieving Folder Contents hanging without showing content
https://bugs.kde.org/show_bug.cgi?id=288364 Frits Spieker s.pa...@spiekerbros.com changed: What|Removed |Added CC||s.pa...@spiekerbros.com --- Comment #28 from Frits Spieker s.pa...@spiekerbros.com --- Same problem here. Fresh install of 4.9.1 (OpenSuSE 12.2 64bit). Firing up kontact from the terminal shows: kontact(23366) MessageList::Core::ModelInvariantRowMapper::modelRowsRemoved: Could not find invariant to invalidate at current row 2292 kontact(23366) MessageList::Core::ModelInvariantRowMapper::modelRowsRemoved: Could not find invariant to invalidate at current row 2293 kontact(23366) MessageList::Core::ModelInvariantRowMapper::modelRowsRemoved: Could not find invariant to invalidate at current row 2294 kontact(23366) MessageList::Core::ModelInvariantRowMapper::modelRowsRemoved: Could not find invariant to invalidate at current row 2295 kontact(23366) MessageList::Core::ModelInvariantRowMapper::modelRowsRemoved: Could not find invariant to invalidate at current row 2296 kontact(23366) MessageList::Core::ModelInvariantRowMapper::modelRowsRemoved: Could not find invariant to invalidate at current row 2297 kontact(23366) MessageList::Core::ModelInvariantRowMapper::modelRowsRemoved: Could not find invariant to invalidate at current row 2298 kontact(23366) MessageList::Core::ModelInvariantRowMapper::modelRowsRemoved: Could not find invariant to invalidate at current row 2299 kontact(23366) MessageList::Core::ModelInvariantRowMapper::modelRowsRemoved: Could not find invariant to invalidate at current row 2300 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 303896] New: Kmail 2 crashes when reading emails fast
https://bugs.kde.org/show_bug.cgi?id=303896 Bug ID: 303896 Severity: crash Version: 4.8.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail 2 crashes when reading emails fast Classification: Unclassified OS: Linux Reporter: s.pa...@spiekerbros.com Hardware: openSUSE RPMs Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.4) KDE Platform Version: 4.8.4 (4.8.4) release 513 Qt Version: 4.8.2 Operating System: Linux 3.1.10-1.16-desktop x86_64 Distribution: openSUSE 12.1 (x86_64) -- Information about the crash: - What I was doing when the application crashed: clicking through the headers of emails fast (one email after the other) made KMail crash. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f5f57de8760 (LWP 2634))] Thread 3 (Thread 0x7f5f3f192700 (LWP 2635)): #0 0x7f5f4fc6be6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5f54600c12 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7f5f54f9f1a0) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #2 0x7f5f54600c49 in WTF::TCMalloc_PageHeap::runScavengerThread (context=optimized out) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #3 0x7f5f4fc67f05 in start_thread () from /lib64/libpthread.so.0 #4 0x7f5f552f210d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f5f3e891700 (LWP 2636)): #0 0x7f5f4fc6a01e in pthread_mutex_lock () from /lib64/libpthread.so.0 #1 0x7f5f4f757e91 in g_main_context_query () from /usr/lib64/libglib-2.0.so.0 #2 0x7f5f4f75899a in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f5f4f758f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f5f55a60e36 in QEventDispatcherGlib::processEvents (this=0x7f5f380008c0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7f5f55a30842 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f5f55a30a97 in QEventLoop::exec (this=0x7f5f3e890e20, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f5f559305f7 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #8 0x7f5f5593361b in QThreadPrivate::start (arg=0x63bbd0) at thread/qthread_unix.cpp:307 #9 0x7f5f4fc67f05 in start_thread () from /lib64/libpthread.so.0 #10 0x7f5f552f210d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f5f57de8760 (LWP 2634)): [KCrash Handler] #6 QNetworkAccessHttpBackend::replyDownloadMetaData (this=0x3e8c7f0, hm=optimized out, sc=optimized out, rp=optimized out, pu=optimized out, db=optimized out, contentLength=-1) at access/qnetworkaccesshttpbackend.cpp:828 #7 0x7f5f50c34509 in QNetworkAccessHttpBackend::qt_static_metacall (_o=0x3e8c7f0, _c=optimized out, _id=optimized out, _a=optimized out) at .moc/release-shared/moc_qnetworkaccesshttpbackend_p.cpp:91 #8 0x7f5f55a4ae06 in QObject::event (this=0x3e8c7f0, e=optimized out) at kernel/qobject.cpp:1204 #9 0x7f5f5644afe4 in notify_helper (e=0x7f5edc00c8b0, receiver=0x3e8c7f0, this=0x648f80) at kernel/qapplication.cpp:4551 #10 QApplicationPrivate::notify_helper (this=0x648f80, receiver=0x3e8c7f0, e=0x7f5edc00c8b0) at kernel/qapplication.cpp:4523 #11 0x7f5f5644fdb3 in QApplication::notify (this=0x7fff69621020, receiver=0x3e8c7f0, e=0x7f5edc00c8b0) at kernel/qapplication.cpp:4412 #12 0x7f5f57191746 in KApplication::notify (this=0x7fff69621020, receiver=0x3e8c7f0, event=0x7f5edc00c8b0) at /usr/src/debug/kdelibs-4.8.4/kdeui/kernel/kapplication.cpp:311 #13 0x7f5f55a31d0c in QCoreApplication::notifyInternal (this=0x7fff69621020, receiver=0x3e8c7f0, event=0x7f5edc00c8b0) at kernel/qcoreapplication.cpp:915 #14 0x7f5f55a355ba in sendEvent (event=0x7f5edc00c8b0, receiver=0x3e8c7f0) at kernel/qcoreapplication.h:231 #15 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x60dc00) at kernel/qcoreapplication.cpp:1539 #16 0x7f5f55a609a3 in sendPostedEvents () at kernel/qcoreapplication.h:236 #17 postEventSourceDispatch (s=0x6450d0) at kernel/qeventdispatcher_glib.cpp:279 #18 0x7f5f4f75858d in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #19 0x7f5f4f758d88 in ?? () from /usr/lib64/libglib-2.0.so.0 #20 0x7f5f4f758f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #21 0x7f5f55a60dcf in QEventDispatcherGlib::processEvents (this=0x60d4c0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:424 #22 0x7f5f564ee69e in QGuiEventDispatcherGlib::processEvents (this=optimized out, flags=optimized out) at kernel/qguieventdispatcher_glib.cpp:204 #23 0x7f5f55a30842 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #24 0x7f5f55a30a97 in QEventLoop::exec (this=0x7fff69620fb0, flags=...) at
[Bug 277530] Kmail encountered a fatal error and will terminate now. The error was: You do not have read/write access to your inbox folder
https://bugs.kde.org/show_bug.cgi?id=277530 --- Comment #9 from Frits Spieker s.pa...@spiekerbros.com --- Excellent stuff. Now the next nice step would be to allow users to actually store their email in a dedicated /Mail partition ;-). I really *hate* it that in the new KMail the mail messages sit in some hidden directory (especially killing with pop3). Thanks for fixing this nasty beast! -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 302206] New: Kontact crashes whilst shutting down KDE
https://bugs.kde.org/show_bug.cgi?id=302206 Bug ID: 302206 Severity: crash Version: 4.8.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crashes whilst shutting down KDE Classification: Unclassified OS: Linux Reporter: s.pa...@spiekerbros.com Hardware: openSUSE RPMs Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.4) KDE Platform Version: 4.8.4 (4.8.4) release 511 Qt Version: 4.8.2 Operating System: Linux 3.1.10-1.9-desktop x86_64 Distribution: openSUSE 12.1 (x86_64) -- Information about the crash: - What I was doing when the application crashed: Whilst shutting down KDE Kontact crashed. To my best knowledge Kontakt (showing the Mail part) was idle whilst shutting down KDE. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7fd9d0e6c760 (LWP 4366))] Thread 2 (Thread 0x7fd9b821c700 (LWP 4367)): #0 0x7fd9c8ceee6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd9cd683c12 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7fd9ce0221a0) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #2 0x7fd9cd683c49 in WTF::TCMalloc_PageHeap::runScavengerThread (context=optimized out) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #3 0x7fd9c8ceaf05 in start_thread () from /lib64/libpthread.so.0 #4 0x7fd9ce37510d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fd9d0e6c760 (LWP 4366)): [KCrash Handler] #6 indexOf (t=@0xd11a48, this=0xae9c60, from=optimized out) at /usr/include/QtCore/qlist.h:855 #7 QListQIODevice*::removeAll (this=0xae9c60, _t=@0xd11a48) at /usr/include/QtCore/qlist.h:772 #8 0x7fd9c1f9e753 in Soprano::Client::SocketHandler::~SocketHandler (this=0xd11a30, __in_chrg=optimized out) at /usr/src/debug/soprano-2.7.6/client/clientconnection.cpp:59 #9 0x7fd9c1f9e859 in Soprano::Client::SocketHandler::~SocketHandler (this=0xd11a30, __in_chrg=optimized out) at /usr/src/debug/soprano-2.7.6/client/clientconnection.cpp:61 #10 0x7fd9ce9b48f0 in QThreadStorageData::finish (p=0x60dc58) at thread/qthreadstorage.cpp:203 #11 0x7fd9ceab7bcd in QCoreApplicationPrivate::~QCoreApplicationPrivate (this=0x648bc0, __in_chrg=optimized out) at kernel/qcoreapplication.cpp:439 #12 0x7fd9cf4cd2d9 in QApplicationPrivate::~QApplicationPrivate (this=0x648bc0, __in_chrg=optimized out) at kernel/qapplication.cpp:223 #13 0x7fd9ceacd590 in cleanup (pointer=optimized out) at ../../src/corelib/tools/qscopedpointer.h:62 #14 ~QScopedPointer (this=0x7fff189f4d88, __in_chrg=optimized out) at ../../src/corelib/tools/qscopedpointer.h:100 #15 QObject::~QObject (this=0x7fff189f4d80, __in_chrg=optimized out) at kernel/qobject.cpp:817 #16 0x7fd9cf4d7a1e in QApplication::~QApplication (this=0x7fff189f4d80, __in_chrg=optimized out) at kernel/qapplication.cpp:1095 #17 0x00403998 in ~KontactApp (this=0x7fff189f4d80, __in_chrg=optimized out) at /usr/src/debug/kdepim-4.8.4/kontact/src/main.cpp:65 #18 main (argc=1, argv=0x7fff189f53a8) at /usr/src/debug/kdepim-4.8.4/kontact/src/main.cpp:198 Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 300159] Kontact crashes whilst accepting an invitation
https://bugs.kde.org/show_bug.cgi?id=300159 --- Comment #2 from Frits Spieker s.pa...@spiekerbros.com --- Hi, I click on the record button, which -in theory as far as I understand- should enter the entry into Calendar. No idea what you mean with kmail launch. Kind regards, Frits On Wednesday 16 May 2012 21:11:22 you wrote: https://bugs.kde.org/show_bug.cgi?id=300159 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel mon...@kde.org --- screenshot please ? (where you click) Do you have kmail launch ? - -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 300159] Kontact crashes whilst accepting an invitation
https://bugs.kde.org/show_bug.cgi?id=300159 --- Comment #4 from Frits Spieker s.pa...@spiekerbros.com --- On Thursday 17 May 2012 17:34:14 you wrote: https://bugs.kde.org/show_bug.cgi?id=300159 --- Comment #3 from Laurent Montel mon...@kde.org --- Do you have kmail started (as plugins or in standelone ?) I always fire up Kontact as a whole, so I take KMail is started as a plugin. I never start kmail as standalone anymore. Especially now there finally is a good plugin for google I really like the integration (Calendar, addresses etc.) it gives me. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 300159] New: Kontact crashes whilst accepting an invitation
https://bugs.kde.org/show_bug.cgi?id=300159 Bug ID: 300159 Severity: crash Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crashes whilst accepting an invitation Classification: Unclassified OS: Linux Reporter: s.pa...@spiekerbros.com Hardware: openSUSE RPMs Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.3) KDE Platform Version: 4.8.3 (4.8.3) release 503 Qt Version: 4.8.1 Operating System: Linux 3.1.10-1.9-desktop x86_64 Distribution: openSUSE 12.1 (x86_64) -- Information about the crash: - What I was doing when the application crashed: Clicked on the record option in invitation; Kontact crashes -- Backtrace: Application: Kontact (kontact), signal: Aborted [Current thread is 1 (Thread 0x7fafa5e45760 (LWP 7678))] Thread 3 (Thread 0x7faf8d74f700 (LWP 7690)): #0 0x7faf9dccce6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fafa265ec12 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7fafa2ffd1a0) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #2 0x7fafa265ec49 in WTF::TCMalloc_PageHeap::runScavengerThread (context=optimized out) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #3 0x7faf9dcc8f05 in start_thread () from /lib64/libpthread.so.0 #4 0x7fafa335010d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7faf8ce4e700 (LWP 7691)): #0 0x7fafa3346ff3 in poll () from /lib64/libc.so.6 #1 0x7faf9d7b9a98 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7faf9d7b9f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fafa3abe2e6 in QEventDispatcherGlib::processEvents (this=0x7faf840008c0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7fafa3a8e012 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fafa3a8e267 in QEventLoop::exec (this=0x7faf8ce4de20, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fafa398e547 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7fafa399156b in QThreadPrivate::start (arg=0x77d100) at thread/qthread_unix.cpp:298 #8 0x7faf9dcc8f05 in start_thread () from /lib64/libpthread.so.0 #9 0x7fafa335010d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fafa5e45760 (LWP 7678)): [KCrash Handler] #6 0x7fafa32a9d95 in raise () from /lib64/libc.so.6 #7 0x7fafa32ab2ab in abort () from /lib64/libc.so.6 #8 0x7fafa3986c94 in qt_message_output (msgType=optimized out, buf=optimized out) at global/qglobal.cpp:2252 #9 0x7fafa3986e4f in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=QtFatalMsg, msg=0x7faf8899a760 Fatal Error: Accessed global static '%s *%s()' after destruction. Defined at %s:%d, ap=0x7fff807de068) at global/qglobal.cpp:2298 #10 0x7fafa3986ff4 in qFatal (msg=optimized out) at global/qglobal.cpp:2481 #11 0x7faf8893df0a in operator- (this=optimized out) at /usr/src/debug/kdepim-4.8.3/mailcommon/mailkernel.cpp:48 #12 MailCommon::Kernel::self () at /usr/src/debug/kdepim-4.8.3/mailcommon/mailkernel.cpp:64 #13 0x7faf8892de39 in MailCommon::FolderCollection::writeConfig (this=0x14e33a0) at /usr/src/debug/kdepim-4.8.3/mailcommon/foldercollection.cpp:210 #14 0x7faf8892e861 in MailCommon::FolderCollection::~FolderCollection (this=0x14e33a0, __in_chrg=optimized out) at /usr/src/debug/kdepim-4.8.3/mailcommon/foldercollection.cpp:83 #15 0x7faf8892e8f9 in MailCommon::FolderCollection::~FolderCollection (this=0x14e33a0, __in_chrg=optimized out) at /usr/src/debug/kdepim-4.8.3/mailcommon/foldercollection.cpp:85 #16 0x7faf8892c616 in deref (value=0x14e33a0, d=0x1510d80) at /usr/include/QtCore/qsharedpointer_impl.h:342 #17 deref (this=optimized out) at /usr/include/QtCore/qsharedpointer_impl.h:336 #18 ~ExternalRefCount (this=optimized out, __in_chrg=optimized out) at /usr/include/QtCore/qsharedpointer_impl.h:401 #19 ~QSharedPointer (this=optimized out, __in_chrg=optimized out) at /usr/include/QtCore/qsharedpointer_impl.h:466 #20 QMaplong long, QSharedPointerMailCommon::FolderCollection ::freeData (x=0xc83c00, this=optimized out) at /usr/include/QtCore/qmap.h:651 #21 0x7fafa32ac9a1 in __run_exit_handlers () from /lib64/libc.so.6 #22 0x7fafa32aca25 in exit () from /lib64/libc.so.6 #23 0x7fafa3f355a6 in KCmdLineArgs::isSet (this=0x4e17e40, _opt=optimized out) at /usr/src/debug/kdelibs-4.8.3/kdecore/kernel/kcmdlineargs.cpp:1511 #24 0x00404377 in KontactApp::newInstance (this=0x7fff807e0ab0) at /usr/src/debug/kdepim-4.8.3/kontact/src/main.cpp:129 #25 0x7fafa51ed0b2 in KUniqueApplicationAdaptor::newInstance (this=0x775bf0, asn_id=optimized out, args=...) at /usr/src/debug/kdelibs-4.8.3/kdeui/kernel/kuniqueapplication.cpp:442 #26 0x7fafa51ed1dc in qt_static_metacall (_a=0x7fff807de960,
[Bug 289428] changing message flags (in KMail2) can lose message permanently
https://bugs.kde.org/show_bug.cgi?id=289428 Frits Spieker s.pa...@spiekerbros.com changed: What|Removed |Added CC||s.pa...@spiekerbros.com --- Comment #9 from Frits Spieker s pamme spiekerbros com 2012-02-06 14:52:25 --- I can confirm this bug. Started happening since upgrade to 4.8.0. Am on OpenSuse 12.1, 64bit. Repo RPM's. Thankfully I have set up akonadi to not delete messages from the pop3 server, as I too would have lost some important mail otherwise. Now can still read online. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 292767] KMail2 (4.8.0) incorrectly displays some messages (does not process the encoding)
https://bugs.kde.org/show_bug.cgi?id=292767 Frits Spieker s.pa...@spiekerbros.com changed: What|Removed |Added Attachment #68332|0 |1 is obsolete|| Attachment #68333|0 |1 is obsolete|| --- Comment #5 from Frits Spieker s pamme spiekerbros com 2012-02-02 13:14:29 --- Created an attachment (id=68431) -- (http://bugs.kde.org/attachment.cgi?id=68431) Should be an email with a PDF attachment. Nice example of a totally useless result in KMail2. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 293039] KMail fails to parse emails properly in some cases
https://bugs.kde.org/show_bug.cgi?id=293039 Frits Spieker s.pa...@spiekerbros.com changed: What|Removed |Added CC||s.pa...@spiekerbros.com --- Comment #9 from Frits Spieker s pamme spiekerbros com 2012-02-02 13:19:02 --- Seems to be exactly the same problem I am having. See bug: 292767 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 292767] KMail2 (4.8.0) incorrectly displays some messages (does not process the encoding)
https://bugs.kde.org/show_bug.cgi?id=292767 --- Comment #2 from Frits Spieker s pamme spiekerbros com 2012-01-30 10:58:34 --- Created an attachment (id=68332) -- (http://bugs.kde.org/attachment.cgi?id=68332) example 1 first example. For privacy reasons overwrote email addresses. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 292767] KMail2 (4.8.0) incorrectly displays some messages (does not process the encoding)
https://bugs.kde.org/show_bug.cgi?id=292767 --- Comment #3 from Frits Spieker s pamme spiekerbros com 2012-01-30 10:59:22 --- Created an attachment (id=68333) -- (http://bugs.kde.org/attachment.cgi?id=68333) different language, same problem -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 292767] New: KMail2 (4.8.0) incorrectly displays some messages (does not process the encoding)
https://bugs.kde.org/show_bug.cgi?id=292767 Summary: KMail2 (4.8.0) incorrectly displays some messages (does not process the encoding) Product: kmail2 Version: 4.8 Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: s.pa...@spiekerbros.com Version: 4.8 (using KDE 4.8.0) OS:Linux Since upgrade to KMail2 4.8, I run into the problem that some incoming emails don't show correct, but instead show the raw content such as the one below: * --_--=_112358201558820 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: quoted-printable = Lesen Sie diesen Newsletter mit Bildern und in Farbe!=0AKlicken Sie hier:= =0A=3D http://= mail.ebay.de= /r/mail/= 20eda9II1d386cII1332df1c853= =0A= =0A=0A= eBay hat diese Mitteilung an=20= [NAME REMOVED]= (= [NAME REMOVE]= )=0Agesendet. Ihr Vor- und Nachname in dieser Mitteilung sind=0Aein Hinwei= s darauf, dass die Nachricht tatsaechlich von eBay=0Astammt.=0A=0AMehr zum= Thema.=0A=3D=0Ahttp://rover.ebay.com/rover/4/0/8?eecl=3D3eesi=3DDEi=3D= 132af079cc5II= 20eda9II1d386cII1332df1c853= eepc=3D=0A=0A= --=0A=0AHallo=20= [NAME REMOVED]= !=0A=0A--=0A= =0AKostenlos einstellen!*=0ASagen Sie nicht, wir h=C3=A4tten Sie nicht gew= arnt=0A=0ANEU=0ANur f=C3=BCr kurze Zeit: kostenlos Auktionen einstellen, j= etzt jeden Tag der Woche=0A=0AJetzt Verkaufsrausch starten=0A=3D http://r= over.ebay.com/rover/4/0/8?eecl=3D3eesi=3DDEi=3D132af079cc6II= 20eda9II1d386cII1332df1c853= etc. etc *** The Encoding under the View menu option is set to AUTO, but also changing it to the encoding that can be found in the message header (UTF-8 in the example above) does not help. KMail started doing this since the upgrade to KDE4.8.0 (from 4.7.4). Reproducible: Sometimes Steps to Reproduce: I have not been able to discover a pattern. Some message show correctly, others like the one above. Totally mangled. Expected Results: Messages show correctly without the raw encoding showing on screen. If you need any other info or examples, just ask. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 284252] possibility for user to control data location
https://bugs.kde.org/show_bug.cgi?id=284252 Frits Spieker s.pa...@spiekerbros.com changed: What|Removed |Added CC||s.pa...@spiekerbros.com --- Comment #1 from Frits Spieker s pamme spiekerbros com 2011-10-19 10:26:51 --- I fully support this. I am on pop3 and always had my mail stored in a separate partition called Mail. Makes it very easy to backup and restore (or move to a new machine) With the new Kmail2, the email sits somewhere in a .local/share/akonadi/file_db_data/ directory without any copies made in the ~Mail directory. I really fail to see the logic behind hiding the mail in a cache like directory without proper means to back it up. On IMAP this might not be a too big issue, on POP3 it is suicide. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 283080] Akonadi message Local Folders: Unsupported Type. Email from POP account disappear!
https://bugs.kde.org/show_bug.cgi?id=283080 Frits Spieker s.pa...@spiekerbros.com changed: What|Removed |Added CC||s.pa...@spiekerbros.com --- Comment #2 from Frits Spieker s pamme spiekerbros com 2011-10-19 10:32:48 --- I get the same message (also on POP3) a couple times per week, but fortunately as I was not yet convinced of the stability of the new KMail2, I have set up my accounts to leave all email on the server. (Have to do a regular clean up through the web frontend, but at least I do not have email getting lost) -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 277530] Kmail encountered a fatal error and will terminate now. The error was: You do not have read/write access to your inbox folder
https://bugs.kde.org/show_bug.cgi?id=277530 --- Comment #3 from Frits Spieker s pamme spiekerbros com 2011-09-07 07:34:52 --- I got so sick and tired of this bug not being fixed, that I did a clean install of opensuse, upgraded straight to 4.7.0 and imported the mail in /home/username/Mail manually. It was still a pain in the proverbial donkey (getting rid of non functional akanodi_whatevers and having to go into akonadiconsole just to rename some top folders in KMail to something user friendly like XS4ALL comes to mind) but at least now I have a working mail system again. (Had temporarily gone to Claws). I had a lot more comments, but decided to delete them because I don't want to step on people's toes. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 281542] New: Akonadi Crashes with Google contacts
https://bugs.kde.org/show_bug.cgi?id=281542 Summary: Akonadi Crashes with Google contacts Product: Akonadi Version: 4.7 Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Google Resource AssignedTo: savag...@yahoo.com ReportedBy: s.pa...@spiekerbros.com CC: vkra...@kde.org, kdepim-bugs@kde.org Application: akonadi_googledata_resource (4.7) KDE Platform Version: 4.7.1 (4.7.1) Qt Version: 4.7.3 Operating System: Linux 2.6.37.6-0.7-desktop x86_64 Distribution: openSUSE 11.4 (x86_64) -- Information about the crash: Trying to synchronize my google contacts in Kontact causes akonadi to crash, repeatedly. For some strange reason KDE says it is version 4.7.1, but I a, quite certain (as in 100%) that I only have 4.7.0 installed. (not using any factory repository). The crash can be reproduced every time. -- Backtrace: Application: Akonadi Resource (akonadi_googledata_resource), signal: Segmentation fault [KCrash Handler] #6 0x7f8ece5c47e2 in __strlen_sse2 () from /lib64/libc.so.6 #7 0x7f8ece5c44d6 in strdup () from /lib64/libc.so.6 #8 0x7f8ed00e7403 in extract_and_check_multi (doc=value optimized out, xpath_expression=value optimized out, getContent=0, attr1=0x7f8ed00f6140 address, attr2=0x7f8ed00f613c rel, attr3=0x7f8ed00f6182 protocol, attr4=0x7f8ed00f615e primary, values=0xa875b0, types=0xa875c0, protocols=0xa875b8, pref=0xa875cc) at /usr/src/debug/libgcal-0.9.6/src/atom_parser.c:295 #9 0x7f8ed00e89ae in atom_extract_contact (entry=value optimized out, ptr_entry=0xa87500) at /usr/src/debug/libgcal-0.9.6/src/atom_parser.c:753 #10 0x7f8ed00ef4e6 in extract_all_contacts (doc=value optimized out, data_extract=value optimized out, length=value optimized out) at /usr/src/debug/libgcal-0.9.6/src/gcal_parser.c:434 #11 0x7f8ed00f34c5 in gcal_get_all_contacts (gcalobj=0x8c6860, length=0x77e338) at /usr/src/debug/libgcal-0.9.6/src/gcont.c:111 #12 0x7f8ed00f0df4 in gcal_get_updated_contacts (gcal_obj=0x8c6860, contacts=0x77e330, timestamp=value optimized out) at /usr/src/debug/libgcal-0.9.6/src/gcontact.c:296 #13 0x004171ee in _start () This bug may be a duplicate of or related to bug 246195. Possible duplicates by query: bug 279593, bug 278785, bug 278494, bug 275377, bug 271662. Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 277530] Kmail encountered a fatal error and will terminate now. The error was: You do not have read/write access to your inbox folder
https://bugs.kde.org/show_bug.cgi?id=277530 --- Comment #1 from Frits Spieker s pamme spiekerbros com 2011-07-30 04:29:51 --- Is anything being done with this bug? The 4.7.0 release has just come out and reading the horror stories on Google, it still exhibits the same bugs namely that pop3 accounts, with the mail stored in ~/Mail does not get imported correctly and Kmail complaining about not having read/write access to the inbox. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 278726] kmail2 migration doesn't support local folder layout supported in kmail1
https://bugs.kde.org/show_bug.cgi?id=278726 Frits Spieker s.pa...@spiekerbros.com changed: What|Removed |Added CC||s.pa...@spiekerbros.com --- Comment #1 from Frits Spieker s pamme spiekerbros com 2011-07-30 04:33:19 --- Sounds very much like the bug I reported a while ago and which many users with the mail in ~/Mail are encountering. My bug report is under 277530. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 277530] New: Kmail encountered a fatal error and will terminate now. The error was: You do not have read/write access to your inbox folder
https://bugs.kde.org/show_bug.cgi?id=277530 Summary: Kmail encountered a fatal error and will terminate now. The error was: You do not have read/write access to your inbox folder Product: kmail2 Version: 2.1.1 Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: s.pa...@spiekerbros.com Version: 2.1.1 (using KDE 4.6.4) OS:Linux For ages I have kept my mail in /home/user/Mail. The migration tool for 2.1.0 always crashed, but the migration tool for kmail 2.1.1. actually successfully created all POP3 accounts and also recognized the /home/user/Mail directory as a valid Maildir. However, upon starting Kmail (or Kontact), the application tells that a fatal error was encountered (see summary). I checked and re-checked and re-re-checked all permissions and the /Mail directory, all its subs and all files in there are owned by the user, and have all the right permissions (read / write and execute on the directories) In Kmail the top folders do show up, but none of the subfolders, let alone email messages in them. (well over 20k messages) When trying to do a retrieve mail on the KMail folder in Kmail, I get messages such as Folder /home/user/Mail/drafts does not seem to be a valid email folder (also for templates, trash etc.) Another message that pops up is Kmail Folders; Access control prohibits item creation in folder 'Foldername'. For testing purposes I have created a new account under linux and there Kmail works like a charm, so it seems to be choking on some old setting. New email messages do get retrieved from the email servers and do show up in Kmail, but not where I would expect them. Downgrading makes me loose these newly donwloaded messages, so I have now told akonadi to keep messages on the server. So far I have no choice but to downgrade again to a 1.x version of Kmail. I don't seem to be the only one with this problem if I do a Google, but I still need to find the golden solution. Reproducible: Always Steps to Reproduce: See above Expected Results: All email folders show up as expected containing all my email. I am on 4.6.5 of KDE, but that number did not show yet in the list. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 267864] migration of akonadi_mixedmaildir_resource fails
https://bugs.kde.org/show_bug.cgi?id=267864 Frits Spieker s.pa...@spiekerbros.com changed: What|Removed |Added CC||s.pa...@spiekerbros.com -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
