[kontact] [Bug 405874] New: Kontact settings crashed
https://bugs.kde.org/show_bug.cgi?id=405874 Bug ID: 405874 Summary: Kontact settings crashed Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: g...@kani.hu Target Milestone: --- Application: kontact (5.10.1) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.18.0-15-lowlatency x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: After updates, I can't open Kontact settings dialog at all. I'm using Neon (bionic). The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4e8d211bc0 (LWP 23107))] Thread 35 (Thread 0x7f4d249d6700 (LWP 23222)): #0 0x7f4e835b4649 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f4e8356e4d0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4e8356e6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4e8a69415b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f4d2c0874b0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f4e8a63564a in QEventLoop::exec(QFlags) (this=this@entry=0x7f4d249d59e0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f4e8a45d41a in QThread::exec() (this=) at thread/qthread.cpp:531 #6 0x7f4e8a45ebc2 in QThreadPrivate::start(void*) (arg=0x556b803e87d0) at thread/qthread_unix.cpp:361 #7 0x7f4e8543b6db in start_thread (arg=0x7f4d249d6700) at pthread_create.c:463 #8 0x7f4e89b4688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 34 (Thread 0x7f4d25ffb700 (LWP 23213)): #0 0x7f4e85441ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f4d25ffa710, expected=0, futex_word=0x7f4d25ffa8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f4e85441ed9 in __pthread_cond_wait_common (abstime=0x7f4d25ffa7b0, mutex=0x7f4d25ffa8a8, cond=0x7f4d25ffa8d0) at pthread_cond_wait.c:533 #2 0x7f4e85441ed9 in __pthread_cond_timedwait (cond=0x7f4d25ffa8d0, mutex=0x7f4d25ffa8a8, abstime=0x7f4d25ffa7b0) at pthread_cond_wait.c:667 #3 0x7f4e7aaa0177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f4e7aaa0ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f4e7aaa0bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f4e7aa5e851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f4e7aa616b6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f4e7aa61974 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f4e7aaa2cd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f4e8543b6db in start_thread (arg=0x7f4d25ffb700) at pthread_create.c:463 #11 0x7f4e89b4688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 33 (Thread 0x7f4d267fc700 (LWP 23212)): #0 0x7f4e85441ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f4d267fb710, expected=0, futex_word=0x7f4d267fb8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f4e85441ed9 in __pthread_cond_wait_common (abstime=0x7f4d267fb7b0, mutex=0x7f4d267fb8a8, cond=0x7f4d267fb8d0) at pthread_cond_wait.c:533 #2 0x7f4e85441ed9 in __pthread_cond_timedwait (cond=0x7f4d267fb8d0, mutex=0x7f4d267fb8a8, abstime=0x7f4d267fb7b0) at pthread_cond_wait.c:667 #3 0x7f4e7aaa0177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f4e7aaa0ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f4e7aaa0bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f4e7aa5e851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f4e7aa616b6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f4e7aa61974 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f4e7aaa2cd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f4e8543b6db in start_thread (arg=0x7f4d267fc700) at pthread_create.c:463 #11 0x7f4e89b4688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 32 (Thread 0x7f4d26ffd700 (LWP 23211)): #0 0x7f4e85441ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f4d26ffc710, expected=0, futex_word=0x7f4d26ffc8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f4e85441ed9 in __pthread_cond_wait_common (abstime=0x7f4d26ffc7b0, mutex=0x7f4d26ffc8a8, cond=0x7f4d26ffc8d0) at pthread_cond_wait.c:533 #2 0x7f4e85441ed9 in __pthread_cond_timedwait (cond=0x7
[kontact] [Bug 328713] New: Crash after message move between local folders.
https://bugs.kde.org/show_bug.cgi?id=328713 Bug ID: 328713 Summary: Crash after message move between local folders. Classification: Unclassified Product: kontact Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: g...@kani.hu Application: kontact (4.11.4) KDE Platform Version: 4.11.4 (Compiled from sources) Qt Version: 4.8.5 Operating System: Linux 3.11.1-pf x86_64 Distribution: "Gentoo Base System release 2.2" -- Information about the crash: - What I was doing when the application crashed: I moved ~50 messages between two local folders. Then again (aroung ~50)... After (!) the second process, kmail (in kontact) crashed, so messages moved successfully. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f670e89b7c0 (LWP 15411))] Thread 6 (Thread 0x7f66f45df700 (LWP 15412)): #0 0x7f670633cfbc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f670949f4c7 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7f6709e681c0 ) at wtf/FastMalloc.cpp:2495 #2 0x7f670949f549 in WTF::TCMalloc_PageHeap::runScavengerThread (context=) at wtf/FastMalloc.cpp:1618 #3 0x7f670633901a in start_thread () from /lib64/libpthread.so.0 #4 0x7f670bc091cd in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f66f3cde700 (LWP 15413)): #0 0x7f67052d5010 in pthread_mutex_lock@plt () from /usr/lib64/libglib-2.0.so.0 #1 0x7f670533f091 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #2 0x7f6705301d51 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f6705301e1c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f670d15000e in QEventDispatcherGlib::processEvents (this=0x7f66ec0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #5 0x7f670d11c246 in QEventLoop::processEvents (this=this@entry=0x7f66f3cdde30, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f670d11c548 in QEventLoop::exec (this=0x7f66f3cdde30, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f670d010755 in QThread::exec (this=) at thread/qthread.cpp:536 #8 0x7f670d012cbf in QThreadPrivate::start (arg=0x85f3a0) at thread/qthread_unix.cpp:338 #9 0x7f670633901a in start_thread () from /lib64/libpthread.so.0 #10 0x7f670bc091cd in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f669f75f700 (LWP 29894)): #0 0x7f670633d33e in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f670d01316b in wait (time=3, this=0x2091820) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x1d0e328, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7f670d0063d6 in QThreadPoolThread::run (this=0x20902f0) at concurrent/qthreadpool.cpp:141 #4 0x7f670d012cbf in QThreadPrivate::start (arg=0x20902f0) at thread/qthread_unix.cpp:338 #5 0x7f670633901a in start_thread () from /lib64/libpthread.so.0 #6 0x7f670bc091cd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f66952cf700 (LWP 29916)): #0 0x7f670533ee2d in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x7f670533f0c9 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #2 0x7f6705301ade in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #3 0x7f6705301d41 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f6705301e1c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f670d15000e in QEventDispatcherGlib::processEvents (this=0x7f6604003cd0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #6 0x7f670d11c246 in QEventLoop::processEvents (this=this@entry=0x7f66952cedf0, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f670d11c548 in QEventLoop::exec (this=0x7f66952cedf0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f670d010755 in QThread::exec (this=) at thread/qthread.cpp:536 #9 0x7f670d0fc1f3 in QInotifyFileSystemWatcherEngine::run (this=0x34588d0) at io/qfilesystemwatcher_inotify.cpp:256 #10 0x7f670d012cbf in QThreadPrivate::start (arg=0x34588d0) at thread/qthread_unix.cpp:338 #11 0x7f670633901a in start_thread () from /lib64/libpthread.so.0 #12 0x7f670bc091cd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f669d3e7700 (LWP 30016)): #0 0x7f670633d33e in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f670d01316b in wait (time=3, this=0x1300340) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x13005f8, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7f670d0063d6 in QThreadPoolThread::run (this=0x1944a30) at concurrent/qthreadpool.cpp:141 #4 0x7f670d012cbf in QThreadPrivate::start (arg=0x1944a30) a
[Akonadi] [Bug 324807] Sends no UID in UID STORE command
https://bugs.kde.org/show_bug.cgi?id=324807 --- Comment #10 from Tamás Gere --- Thank you! I'll test soon with the update release. -- 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
[Akonadi] [Bug 324807] After sending a mail Akonadi gives »A000685 BAD Error in IMAP command UID STORE: Invalid uidset«
https://bugs.kde.org/show_bug.cgi?id=324807
--- Comment #3 from Tamás Gere ---
Created attachment 82762
--> https://bugs.kde.org/attachment.cgi?id=82762&action=edit
kimaplog
Here is the imap log (thanks for pointing out this feature).
It has both type of the error messages. You will see, one of the "Sent" folder
has constantly 720 messages. Somehow I only see that body of test message which
I sent via that server which actually working (mostly), but making the second
type of error.
The only sign about the lost message I found (in kimap.log.3407.3 for example)
is:
C: A19 APPEND "INBOX.Sent" (\Seen $SENT) {426}
S: A19 NO Error in IMAP command received by server.
There is an other log file from another session where you see a working filter
action actually moving message inside the mailbox (not loosing these messages).
--
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
[Akonadi] [Bug 324807] After sending a mail Akonadi gives »A000685 BAD Error in IMAP command UID STORE: Invalid uidset«
https://bugs.kde.org/show_bug.cgi?id=324807 Tamás Gere changed: What|Removed |Added CC||g...@kani.hu --- Comment #1 from Tamás Gere --- I can confirm this. Having same problem. Additionally, I'm loosing the sent mail, which is painful in my case. I tried a trick: set the "sent folder" to local folder, then a filter to local folders to move message to the imap "sent" folder. Local store worked, but same result on filter action. Mail lost. I tried to move message by dragging from local folder to imap. Same result: message lost. The only case when I not loose message if I drag within same imap account. This issue started since I upgraded to 4.11 (from 4.10). these are the error messages: Append failed, server replied: A97 NO Error in IMAP command received by server. Store failed, server replied: A99 NO Error in IMAP command received by server. or Store failed, server replied: A68 BAD Error in IMAP command UID STORE: Invalid uidset Of course, the imap server setup may be related. I have two account set up. First one producing the first set of error messages. I'm loosing all sent e-mail there. The second account producing the second message >sometimes<. So in this case - as the bug reporter said - sometimes working, sometimes not. -- 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
[kmail2] [Bug 323929] kmail high cpu load, seems stuck looping on fetching mails from akonadi
https://bugs.kde.org/show_bug.cgi?id=323929 --- Comment #19 from Tamás Gere --- Hello! 4.11.1 upgrade solved all problems for me. Thanks. -- 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 323929] kmail high cpu load, seems stuck looping on fetching mails from akonadi
https://bugs.kde.org/show_bug.cgi?id=323929 Tamás Gere changed: What|Removed |Added CC||g...@kani.hu --- Comment #17 from Tamás Gere --- I can confirm too. I upgraded with 3 imap mailboxes. Seems akonadi is fine, since everything normal (fetches email properly, notifications are ok, feeds nepomuk, etc.) until kmail (or kontact with kmail module enabled) started up. After startup, kmail starts cycle over all e-mails in all mailbox and never finish. Akonadi console shows that kmail requesting "LSUB 0 INF (MIMETYPE (message/rfc822))" on all mailbox and processing all messsage. When finished, the whole process starts again. This endless process eats my cpu by akonadiserver and mysql (i use mysql as backend). It's impossible to work with kmail, because each mail fetching takes 3-10mins. Since I'm using kde (and kmail) for work, I tried find solution. After a lot of search, I found some suggestion: - search for same named resources which probably a leftover of bad migration process (didn't have any) - removed all imap accounts, and added only one. - removed all data in .local/share/akonadi/ - deleted all data in mysql database None of above worked for me. Since I have to work, I given up and downgraded all kdepim related ebuilds (I'm using gentoo) to 4.10.5. I didn't downgraded akonadi-server, it's still at 1.10.2-r1. Now I have some filter and organizer crash, akonadiconsole crashes on startup as well, but at least I can work with kmail. It's interesting what Maarten ter Huurne wrote. I don't have subfolder named "inbox", but all of my imap mailboxes has "INBOX." prefix. Therefore all of my other special folders (sent, trash, drafts, templates) are subfolders under inbox. That means I have special folder in special folder too. So maybe I'm affected by that "replace and re-parse" bug as well Now I think I'll upgrade again and play with these special folders. -- 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 265076] kmail on startup
https://bugs.kde.org/show_bug.cgi?id=265076 Tamás Gere changed: What|Removed |Added CC||g...@kani.hu --- Comment #8 from Tamás Gere 2011-07-13 00:14:40 --- I had same problem after a bigger update of my packages. After some inspection of packages, I noticed that not all was upgraded due to my wrong settings of the package manager (portage, gentoo). So some dependencies of kmail wasn't updated. I think the kde-misc/kwebkitpart was the main problem, but not sure. That had version 0.9.6 while 1.1.1 was out, and I seen some webkit related files in the crash report. Hope will help for some ppl. -- 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
