[Akonadi] [Bug 367789] New: Agent zur E-Mail-Archivierung (akonadi_archivemail_agent), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=367789 Bug ID: 367789 Summary: Agent zur E-Mail-Archivierung (akonadi_archivemail_agent), signal: Segmentation fault Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: Archive Mail Agent Assignee: kdepim-bugs@kde.org Reporter: bugrprt21...@online.de Application: akonadi_archivemail_agent (4.14) KDE Platform Version: 4.14.9 Qt Version: 4.8.6 Operating System: Linux 3.16.7-35-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: KMail was performing the first daily Archive of one of the mail folders. The crash can be reproduced sometimes. -- Backtrace: Application: Agent zur E-Mail-Archivierung (akonadi_archivemail_agent), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #5 0x7fb8c48cd9fb in QUrl::QUrl(QUrl const&) (this=0x6c69662d69752d78) at ../../src/corelib/arch/qatomic_x86_64.h:121 #6 0x7fb8c48cd9fb in QUrl::QUrl(QUrl const&) (this=0x7fff1b1254d0, other=...) at io/qurl.cpp:4270 #7 0x7fb8c5027a79 in KUrl::KUrl(KUrl const&) () at /usr/lib64/libkdecore.so.5 #8 0x00412bff in _start () Possible duplicates by query: bug 347300. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 309474] akonadictl fsck : item has no RID
https://bugs.kde.org/show_bug.cgi?id=309474 Andrey Bondarenko changed: What|Removed |Added CC||abon...@mail.ru -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 364220] Crash after downloading mails
https://bugs.kde.org/show_bug.cgi?id=364220 wurfb...@b1-systems.de changed: What|Removed |Added CC||wurfb...@b1-systems.de --- Comment #3 from wurfb...@b1-systems.de --- had the same problems after updating to the newest packages of opensuse tumbleweed. Akonadiserver always restarts with the following message: Database "akonadi" opened using driver "QMYSQL" Executing search "searchUpdate-1472078875" searchUpdateResultsAvailable 270 0 results Got 0 results, out of which 0 are already in the collection Added 0 Search done "searchUpdate-1472078875" (without remote search) Search update finished All results: 0 Removed results: 0 Executing search "searchUpdate-1472078875" log_akonadiplugin_indexer: unknown term "attachment" "[\n0: akonadiserver() [0x574fe6]\n1: akonadiserver() [0x575300]\n2: /lib64/libc.so.6(+0x349f0) [0x7f7589a619f0]\n3: [0x7f7560050030]\n]\n" ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error) So i thougt it might have to do something with email Search. I went to Kontact Search Folder and deleted the folder "last search". This brings Kontact to crash. But after starting Kontact again the problem with akonadiserver restart was gone. To verify i did again in Kontact a search, after this i had the same behaviour. Akonadiserver begins to restart again. After delete the last search folder again akonadiserver is stable. Regards, Thomas -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367779] New: kmail always crashes when closing
https://bugs.kde.org/show_bug.cgi?id=367779 Bug ID: 367779 Summary: kmail always crashes when closing Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: tick...@tsiboboka.de Application: kmail (5.2.3) Qt Version: 5.7.0 Frameworks Version: 5.25.0 Operating System: Linux 4.1.27-27-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: closed the application openSUSE Leap 42.1 KMail 5.2.3 KDE Frameworks 5.25.0 Qt 5.7.0 The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcde0a10800 (LWP 7979))] Thread 20 (Thread 0x7fcd357fa700 (LWP 8019)): #0 0x7fcddda9cbfd in poll () at /lib64/libc.so.6 #1 0x7fcdd1e8de64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fcdd1e8df7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fcdde5b8f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fcdde5688cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fcdde3af06a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fcdde3b3899 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fcdd3b100a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7fcdddaa502d in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7fcd35ffb700 (LWP 8007)): #0 0x7fcddda9cbfd in poll () at /lib64/libc.so.6 #1 0x7fcdd1e8de64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fcdd1e8df7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fcdde5b8f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fcdde5688cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fcdde3af06a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fcdde3b3899 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fcdd3b100a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7fcdddaa502d in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7fcd367fc700 (LWP 8006)): #0 0x7fcdd3b1403f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fcdce6e6443 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fcdcea080a1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fcdd3b100a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fcdddaa502d in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7fcd36ffd700 (LWP 8005)): #0 0x7fcdd3b1403f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fcdce6e6443 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fcdcea080a1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fcdd3b100a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fcdddaa502d in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7fcd377fe700 (LWP 8004)): #0 0x7fcdd3b1403f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fcdce6e6443 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fcdcea080a1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fcdd3b100a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fcdddaa502d in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7fcd37fff700 (LWP 8003)): #0 0x7fcdd3b1403f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fcdce6e546d in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fcdcea080a1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fcdd3b100a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fcdddaa502d in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7fcd45f90700 (LWP 8001)): #0 0x7fcdd1ecfcf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fcdd1e8de4a in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fcdd1e8df7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fcdde5b8f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fcdde5688cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fcdde3af06a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fcdde3b3899 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fcdd3b100a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7fcdddaa502d in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7fcd46791700 (LWP 7999)): #0 0x7fcdd1ecfd14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fcdd1e8df86 in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #2 0x7fcdde5b8f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7fcdde5688cb in QEventLoop::exec(QFlags) () at
[kmail2] [Bug 367765] New: Incoming account order in configuration dialogue is mixed up after every restart
https://bugs.kde.org/show_bug.cgi?id=367765 Bug ID: 367765 Summary: Incoming account order in configuration dialogue is mixed up after every restart Product: kmail2 Version: Git (master) Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: config dialog Assignee: kdepim-bugs@kde.org Reporter: mail2h...@gmail.com In the configuration dialogue for incoming accounts the order of the accounts is changing every time I restart Kmail. So it does not have the order of the "customize account order". So every time you open this window everything is mixed afterward. This is annoying when you have many accounts. Using Kmail 5.2.3 Thank you Reproducible: Always Steps to Reproduce: 1. Start Kontact 2. Go to Kmail / Configuration 3. Go to Accounts 4. Press Ok to close the dialogue 5. Close Kontact 6. Start it again Actual Results: The Order of the accounts is mixed up after every restart of the program. Expected Results: The order should be every time the same or in the order you defined. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 350219] Kmail can't create IMAP top level folders
https://bugs.kde.org/show_bug.cgi?id=350219 Juha Tuomala changed: What|Removed |Added CC||t...@iki.fi --- Comment #13 from Juha Tuomala --- Confirmed. New manually created dovecot maildir folder doesn't appear either, regardless what I try. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 364220] Crash after downloading mails
https://bugs.kde.org/show_bug.cgi?id=364220 Ian changed: What|Removed |Added CC||ianse...@yahoo.co.uk --- Comment #2 from Ian --- Just had pages and pages of this warning on kmail 5.3.0 using Qt: 5.6.1 KDE Frameworks: 5.25.0 kf5-config: 1.0 KDE Plasma: 5.7.3 Kernel: 4.7.1-1-default "openSUSE Tumbleweed (20160820) (x86_64)" -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 362695] Kmail process continues running after exiting with File->quit.
https://bugs.kde.org/show_bug.cgi?id=362695 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.3.0 CC||mon...@kde.org Status|CONFIRMED |RESOLVED --- Comment #5 from Laurent Montel --- Fixed in 5.3.0 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 367750] New: Kmail crashed when mailboxes are larger then RAM but not such big as Virual memory amount
https://bugs.kde.org/show_bug.cgi?id=367750 Bug ID: 367750 Summary: Kmail crashed when mailboxes are larger then RAM but not such big as Virual memory amount 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: peter.fod...@stuba.sk Application: kontact (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.25.0 Operating System: Linux 4.7.1-1-default x86_64 Distribution: "openSUSE Tumbleweed (20160812) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: run application after OpenSUSE Tumbleeweed KDE update - Unusual behavior I noticed: akonadi mailbox updates takes unsual long time - Custom settings of the application: 3 tie POP3 and 1 time IMAP acounts with huge mailboxes (some are GiB large) 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 0x7f4a93109940 (LWP 5293))] Thread 30 (Thread 0x7f497f940700 (LWP 5410)): #0 0x7f4a8b98209f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4a80765129 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f4a80765840 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f4a80765a10 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f4a807625cd in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f4a8b97c474 in start_thread () at /lib64/libpthread.so.0 #6 0x7f4a8fad33ed in clone () at /lib64/libc.so.6 Thread 29 (Thread 0x7f49802c1700 (LWP 5409)): #0 0x7f4a8b98209f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4a80765129 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f4a80765840 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f4a80765a10 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f4a807625cd in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f4a8b97c474 in start_thread () at /lib64/libpthread.so.0 #6 0x7f4a8fad33ed in clone () at /lib64/libc.so.6 Thread 28 (Thread 0x7f4982c99700 (LWP 5376)): #0 0x7f4a8ad700a9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f4a8ad2ba7c in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7f4a8ad2bff4 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f4a8ad2c16c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f4a9060caeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f4a905b476a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f4a903da3b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f4a903df2d8 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f4a8b97c474 in start_thread () at /lib64/libpthread.so.0 #9 0x7f4a8fad33ed in clone () at /lib64/libc.so.6 Thread 27 (Thread 0x7f498349a700 (LWP 5374)): #0 0x7f4a903d6ff9 in QMutex::lock() () at /usr/lib64/libQt5Core.so.5 #1 0x7f4a9060c17f in () at /usr/lib64/libQt5Core.so.5 #2 0x7f4a8ad2b5a9 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #3 0x7f4a8ad2bf7b in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f4a8ad2c16c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f4a9060caeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f4a905b476a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f4a903da3b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f4a903df2d8 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f4a8b97c474 in start_thread () at /lib64/libpthread.so.0 #10 0x7f4a8fad33ed in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7f4986884700 (LWP 5368)): #0 0x7ffd534b0b94 in clock_gettime () #1 0x7f4a8fae00a6 in clock_gettime () at /lib64/libc.so.6 #2 0x7f4a9048ad96 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f4a9060a699 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f4a9060ac45 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f4a9060bfde in () at /usr/lib64/libQt5Core.so.5 #6 0x7f4a8ad2b5a9 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f4a8ad2bf7b in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f4a8ad2c16c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f4a9060caeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f4a905b476a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f4a903da3b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f4a903df2d8 in () at
[kontact] [Bug 367749] New: Kontact crashes
https://bugs.kde.org/show_bug.cgi?id=367749 Bug ID: 367749 Summary: Kontact crashes Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: fr.teichm...@aon.at Application: kontact (5.1.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-34-generic i686 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Crash after I tried "kontact Einstellen" (kontact options? in English?). Same reaction after "korganizer einstellen" and the same action as I tried to open KAdressBook. KDE as upgrade from 14.04 The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xab73d840 (LWP 4127))] Thread 33 (Thread 0x9231cb40 (LWP 4231)): #0 0xb7703c31 in __kernel_vsyscall () #1 0xb5f7dc4f in read () at ../sysdeps/unix/syscall-template.S:84 #2 0xb26b40e5 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb266eb9a in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb266f0a1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb266f244 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #6 0xb64aeb14 in QEventDispatcherGlib::processEvents (this=0xaa902d08, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #7 0xb6453953 in QEventLoop::processEvents (this=0x9231c194, flags=...) at kernel/qeventloop.cpp:128 #8 0xb6453daa in QEventLoop::exec (this=0x9231c194, flags=...) at kernel/qeventloop.cpp:204 #9 0xb6279f1d in QThread::exec (this=0xb661b68) at thread/qthread.cpp:503 #10 0xb6279ff8 in QThread::run (this=0xb661b68) at thread/qthread.cpp:570 #11 0xb627f43b in QThreadPrivate::start (arg=0xb661b68) at thread/qthread_unix.cpp:331 #12 0xb280b2b5 in start_thread (arg=0x9231cb40) at pthread_create.c:333 #13 0xb5f8f16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 32 (Thread 0x92b87b40 (LWP 4229)): #0 0xb266bf01 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb266e55b in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb266f014 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb266f244 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb64aeb14 in QEventDispatcherGlib::processEvents (this=0xa82057e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0xb6453953 in QEventLoop::processEvents (this=0x92b87194, flags=...) at kernel/qeventloop.cpp:128 #6 0xb6453daa in QEventLoop::exec (this=0x92b87194, flags=...) at kernel/qeventloop.cpp:204 #7 0xb6279f1d in QThread::exec (this=0xb5e9098) at thread/qthread.cpp:503 #8 0xb6279ff8 in QThread::run (this=0xb5e9098) at thread/qthread.cpp:570 #9 0xb627f43b in QThreadPrivate::start (arg=0xb5e9098) at thread/qthread_unix.cpp:331 #10 0xb280b2b5 in start_thread (arg=0x92b87b40) at pthread_create.c:333 #11 0xb5f8f16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 31 (Thread 0x93388b40 (LWP 4227)): #0 0xb5f9bd16 in __libc_disable_asynccancel (oldtype=) at ../nptl/cancellation.c:101 #1 0xb5f7dc58 in read () at ../sysdeps/unix/syscall-template.S:84 #2 0xb26b40e5 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb266eb9a in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb266f0a1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb266f244 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #6 0xb64aeb14 in QEventDispatcherGlib::processEvents (this=0xa77032f0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #7 0xb6453953 in QEventLoop::processEvents (this=0x93388194, flags=...) at kernel/qeventloop.cpp:128 #8 0xb6453daa in QEventLoop::exec (this=0x93388194, flags=...) at kernel/qeventloop.cpp:204 #9 0xb6279f1d in QThread::exec (this=0xb5e6820) at thread/qthread.cpp:503 #10 0xb6279ff8 in QThread::run (this=0xb5e6820) at thread/qthread.cpp:570 #11 0xb627f43b in QThreadPrivate::start (arg=0xb5e6820) at thread/qthread_unix.cpp:331 #12 0xb280b2b5 in start_thread (arg=0x93388b40) at pthread_create.c:333 #13 0xb5f8f16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 30 (Thread 0x93bbfb40 (LWP 4225)): #0 0xb631d31a in qt_gettime () at tools/qelapsedtimer_unix.cpp:163 #1 0xb64ac3e2 in QTimerInfoList::updateCurrentTime (this=0xa65068ac) at kernel/qtimerinfo_unix.cpp:84 #2 0xb64ac904 in QTimerInfoList::timerWait (this=0xa65068ac, tm=...) at kernel/qtimerinfo_unix.cpp:381 #3 0xb64adec9 in timerSourcePrepareHelper (timeout=0x93bbeff8, src=0xa6506878) at kernel/qeventdispatcher_glib.cpp:127 #4 timerSourcePrepare (source=0xa6506878, timeout=0x93bbeff8) at
[Akonadi] [Bug 340813] sometimes two copies of mysqld are running with Akonadi
https://bugs.kde.org/show_bug.cgi?id=340813 Denis Kurz changed: What|Removed |Added CC||i...@aschoettler.com --- Comment #8 from Denis Kurz --- *** Bug 367638 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 367638] DATABASE ERROR: 1452
https://bugs.kde.org/show_bug.cgi?id=367638 Denis Kurz changed: What|Removed |Added CC||denis.kurz+kdebugs@posteo.d ||e Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 340813 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 362695] Kmail process continues running after exiting with File->quit.
https://bugs.kde.org/show_bug.cgi?id=362695 --- Comment #4 from Christoph Pospiech --- Another observation (and work around) - unchecking the button "Settings -> Configure KMail -> Misc -> Folders -> Empty local trash folder on program exit" makes the effect disappear - the kmail process terminates gracefully. Looks like the "Empty local trash folder on program exit" is the culprit or closely related to it. -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 365944] KAddressbook crashes on startup with configured CardDav
https://bugs.kde.org/show_bug.cgi?id=365944 Denis Kurz changed: What|Removed |Added CC||fr.teichm...@aon.at --- Comment #7 from Denis Kurz --- *** Bug 366304 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 362150] Crashes on startup
https://bugs.kde.org/show_bug.cgi?id=362150 --- Comment #4 from Denis Kurz --- Oh no, now I confused the backtraces of the original bug report and comment 1! Actually, the bug reported here is a duplicate of bug 365944, and the bug in comment 1 is a duplicate of bug 365982. Sorry for the noise! *** This bug has been marked as a duplicate of bug 365944 *** -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 365944] KAddressbook crashes on startup with configured CardDav
https://bugs.kde.org/show_bug.cgi?id=365944 Denis Kurz changed: What|Removed |Added CC||versue...@gmx.net --- Comment #11 from Denis Kurz --- *** Bug 362150 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367716] Kmail crash when openning completion configuration from contextual menu in TO field when composing a new message
https://bugs.kde.org/show_bug.cgi?id=367716 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/libk ||depim/af3ed2c87a74d672e9e0e ||3e28a1ed9d7c95e9260 Status|UNCONFIRMED |RESOLVED Version Fixed In||5.3.1 --- Comment #2 from Laurent Montel --- Git commit af3ed2c87a74d672e9e0e3e28a1ed9d7c95e9260 by Montel Laurent. Committed on 24/08/2016 at 07:06. Pushed by mlaurent into branch 'Applications/16.08'. Fix Bug 367716 - Kmail crash when openning completion configuration from contextual menu in TO field when composing a new message FIXED-IN: 5.3.1 M +7-0src/addressline/addresslineedit/addresseelineedit.cpp M +1-0src/addressline/addresslineedit/addresseelineedit.h M +12 -1src/addressline/addresslineedit/addresseelineedit_p.cpp M +4-0src/addressline/addresslineedit/addresseelineedit_p.h M +2-0src/multiplyingline/multiplyingline.h M +4-0src/multiplyingline/multiplyinglineview_p.cpp http://commits.kde.org/libkdepim/af3ed2c87a74d672e9e0e3e28a1ed9d7c95e9260 -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 362150] Crashes on startup
https://bugs.kde.org/show_bug.cgi?id=362150 Denis Kurz changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #3 from Denis Kurz --- Sorry, pasted the wrong id in comment 2. *** This bug has been marked as a duplicate of bug 365982 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 365982] akonadiconsole crash when pressing the "browser" button
https://bugs.kde.org/show_bug.cgi?id=365982 Denis Kurz changed: What|Removed |Added CC||versue...@gmx.net --- Comment #1 from Denis Kurz --- *** Bug 362150 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.