[Bug 266451] Birthdays Anniversaries showing duplicate entries.
https://bugs.kde.org/show_bug.cgi?id=266451 Martin littlec...@gmx.net changed: What|Removed |Added CC||littlec...@gmx.net -- 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 302222] New: Crash on click on a IMAP folder
https://bugs.kde.org/show_bug.cgi?id=30 Bug ID: 30 Severity: crash Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Crash on click on a IMAP folder Classification: Unclassified OS: Linux Reporter: f...@laposte.net Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.3) KDE Platform Version: 4.8.3 (4.8.3) Qt Version: 4.8.1 Operating System: Linux 3.2.0-25-generic x86_64 Distribution: Ubuntu 12.04 LTS -- Information about the crash: Experiencing troubles with IMAP account : Popup with Connection lost Then click ok The a crash occured when click on a IMAP folder -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7fa5f8fb57c0 (LWP 2089))] Thread 4 (Thread 0x7fa5d6a2a700 (LWP 2093)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7fa5eb297dec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fa5eb297f19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fa5f3dcfe9a in start_thread (arg=0x7fa5d6a2a700) at pthread_create.c:308 #4 0x7fa5f63004bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 3 (Thread 0x7fa5d6111700 (LWP 2094)): #0 0x7fa5f62f4b03 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7fa5eeba4036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa5eeba4164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa5f6c8b426 in QEventDispatcherGlib::processEvents (this=0x7fa5d8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7fa5f6c5ac82 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fa5f6c5aed7 in QEventLoop::exec (this=0x7fa5d6110dc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fa5f6b59fa7 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7fa5f6b5cfcb in QThreadPrivate::start (arg=0x20b3d70) at thread/qthread_unix.cpp:298 #8 0x7fa5f3dcfe9a in start_thread (arg=0x7fa5d6111700) at pthread_create.c:308 #9 0x7fa5f63004bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 2 (Thread 0x7fa58ef09700 (LWP 2100)): #0 0x7fa5f3dd1f69 in __pthread_mutex_lock (mutex=0x7fa58a60) at pthread_mutex_lock.c:92 #1 0x7fa5eebdf5a1 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa5eeba3337 in g_main_context_release () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa5eeba3fe9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa5eeba4164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fa5f6c8b426 in QEventDispatcherGlib::processEvents (this=0x7fa588c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7fa5f6c5ac82 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #7 0x7fa5f6c5aed7 in QEventLoop::exec (this=0x7fa58ef08d90, flags=...) at kernel/qeventloop.cpp:204 #8 0x7fa5f6b59fa7 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #9 0x7fa5f6c3a9ff in QInotifyFileSystemWatcherEngine::run (this=0x2573960) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x7fa5f6b5cfcb in QThreadPrivate::start (arg=0x2573960) at thread/qthread_unix.cpp:298 #11 0x7fa5f3dcfe9a in start_thread (arg=0x7fa58ef09700) at pthread_create.c:308 #12 0x7fa5f63004bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #13 0x in ?? () Thread 1 (Thread 0x7fa5f8fb57c0 (LWP 2089)): [KCrash Handler] #6 QNetworkAccessHttpBackend::replyDownloadMetaData (this=0x32e1e90, hm=..., sc=optimized out, rp=..., pu=optimized out, db=..., contentLength=-1) at access/qnetworkaccesshttpbackend.cpp:827 #7 0x7fa5f5335709 in QNetworkAccessHttpBackend::qt_static_metacall (_o=0x32e1e90, _c=optimized out, _id=optimized out, _a=optimized out) at .moc/release-shared/moc_qnetworkaccesshttpbackend_p.cpp:91 #8 0x7fa5f6c75446 in QObject::event (this=0x32e1e90, e=optimized out) at kernel/qobject.cpp:1195 #9 0x7fa5f717e894 in notify_helper (e=0x7fa56800ba50, receiver=0x32e1e90, this=0x1b2cef0) at kernel/qapplication.cpp:4559 #10 QApplicationPrivate::notify_helper (this=0x1b2cef0, receiver=0x32e1e90, e=0x7fa56800ba50) at kernel/qapplication.cpp:4531 #11 0x7fa5f7183713 in QApplication::notify (this=0x7fff10faefa0, receiver=0x32e1e90, e=0x7fa56800ba50) at kernel/qapplication.cpp:4420 #12 0x7fa5f89b8bb6 in KApplication::notify (this=0x7fff10faefa0, receiver=0x32e1e90,
[Bug 302223] New: Kmail crashed at startup
https://bugs.kde.org/show_bug.cgi?id=302223 Bug ID: 302223 Severity: crash Version: 4.8.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail crashed at startup Classification: Unclassified OS: Linux Reporter: as...@isa.upv.es Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.4) KDE Platform Version: 4.8.4 (4.8.4) Qt Version: 4.8.1 Operating System: Linux 3.2.0-25-generic x86_64 Distribution: Ubuntu 12.04 LTS -- Information about the crash: - What I was doing when the application crashed: Starting Kmail 4.8.4 after logging in. Subsequent Kmail starts worked out OK, so this might be a low-priority issue. The crash does not seem to be reproducible. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:39 [Current thread is 1 (Thread 0x7f63091637c0 (LWP 5545))] Thread 7 (Thread 0x7f62e6fc5700 (LWP 5547)): #0 0x7f63064ab0bd in read () at ../sysdeps/unix/syscall-template.S:82 #1 0x7f62fed928cf in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f62fed57ba4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f62fed57fd6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f62fed5849a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f62e6fca98b in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so #6 0x7f62fed799e5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f6303f87e9a in start_thread (arg=0x7f62e6fc5700) at pthread_create.c:308 #8 0x7f63064b84bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #9 0x in ?? () Thread 6 (Thread 0x7f62e63b9700 (LWP 5548)): #0 0x7f63064acb03 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f62fed58036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f62fed5849a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f62ecf62406 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f62fed799e5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6303f87e9a in start_thread (arg=0x7f62e63b9700) at pthread_create.c:308 #6 0x7f63064b84bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x in ?? () Thread 5 (Thread 0x7f62d705b700 (LWP 5586)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f62fb44bdec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f62fb44bf19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f6303f87e9a in start_thread (arg=0x7f62d705b700) at pthread_create.c:308 #4 0x7f63064b84bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 4 (Thread 0x7f62d675a700 (LWP 5587)): #0 0x7f63064acb03 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f62fed58036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f62fed58164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6306e43426 in QEventDispatcherGlib::processEvents (this=0x7f62d8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f6306e12c82 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f6306e12ed7 in QEventLoop::exec (this=0x7f62d6759dc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f6306d11fa7 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f6306d14fcb in QThreadPrivate::start (arg=0xfe0ae0) at thread/qthread_unix.cpp:298 #8 0x7f6303f87e9a in start_thread (arg=0x7f62d675a700) at pthread_create.c:308 #9 0x7f63064b84bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 3 (Thread 0x7f6289263700 (LWP 5694)): #0 0x7f63064acb03 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f62fed58036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f62fed58164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6306e43426 in QEventDispatcherGlib::processEvents (this=0x7f62840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f6306e12c82 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f6306e12ed7 in QEventLoop::exec (this=0x7f6289262d90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f6306d11fa7 in
[Bug 302224] New: Kmail crashed on opening
https://bugs.kde.org/show_bug.cgi?id=302224 Bug ID: 302224 Severity: crash Version: 4.8.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail crashed on opening Classification: Unclassified OS: Linux Reporter: sven.burmeis...@gmx.net Hardware: Compiled Sources Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.4) KDE Platform Version: 4.8.4 (4.8.4) release 513 (Compiled from sources) Qt Version: 4.8.2 Operating System: Linux 3.1.10-1.9-default i686 Distribution: openSUSE 12.1 (i586) -- Information about the crash: - What I was doing when the application crashed: I started kmail and it crashed. It might be that I clicked on the close icon after kmail's window appeared since I wanted to close another window while kmail started. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0xb17bd9f0 (LWP 17049))] Thread 4 (Thread 0xb0094b70 (LWP 17054)): #0 0xb5866782 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0xb5e5c5cc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libc.so.6 #2 0xb385e189 in ?? () from /usr/lib/libQtWebKit.so.4 #3 0xb385e1cf in ?? () from /usr/lib/libQtWebKit.so.4 #4 0xb5862a7d in start_thread () from /lib/libpthread.so.0 #5 0xb5e4eabe in clone () from /lib/libc.so.6 Thread 3 (Thread 0xaf76cb70 (LWP 17055)): #0 0xb4581c90 in clock_gettime () from /lib/librt.so.1 #1 0xb6ba2c35 in do_gettime (frac=0xaf76c050, sec=0xaf76c048) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0xb6c8c486 in QTimerInfoList::updateCurrentTime (this=0xaee01abc) at kernel/qeventdispatcher_unix.cpp:343 #4 0xb6c8c7ea in QTimerInfoList::timerWait (this=0xaee01abc, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #5 0xb6c8afe3 in timerSourcePrepareHelper (src=optimized out, timeout=0xaf76c13c) at kernel/qeventdispatcher_glib.cpp:136 #6 0xb44c844c in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #7 0xb44c9207 in ?? () from /usr/lib/libglib-2.0.so.0 #8 0xb44c97fa in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #9 0xb6c8bb47 in QEventDispatcherGlib::processEvents (this=0xaee00468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #10 0xb6c5764d in QEventLoop::processEvents (this=0xaf76c2d0, flags=...) at kernel/qeventloop.cpp:149 #11 0xb6c578e9 in QEventLoop::exec (this=0xaf76c2d0, flags=...) at kernel/qeventloop.cpp:204 #12 0xb6b40dac in QThread::exec (this=0x8411c50) at thread/qthread.cpp:501 #13 0xb6b40e9b in QThread::run (this=0x8411c50) at thread/qthread.cpp:568 #14 0xb6b44290 in QThreadPrivate::start (arg=0x8411c50) at thread/qthread_unix.cpp:307 #15 0xb5862a7d in start_thread () from /lib/libpthread.so.0 #16 0xb5e4eabe in clone () from /lib/libc.so.6 Thread 2 (Thread 0xadce8b70 (LWP 17061)): #0 0xb5866b15 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0xb5e5c624 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libc.so.6 #2 0xb6b4478f in wait (time=3, this=0x85c9710) at thread/qwaitcondition_unix.cpp:84 #3 QWaitCondition::wait (this=0x85c96e0, mutex=0x85c96dc, time=3) at thread/qwaitcondition_unix.cpp:158 #4 0xb6b36c04 in QThreadPoolThread::run (this=0x85c98b0) at concurrent/qthreadpool.cpp:141 #5 0xb6b44290 in QThreadPrivate::start (arg=0x85c98b0) at thread/qthread_unix.cpp:307 #6 0xb5862a7d in start_thread () from /lib/libpthread.so.0 #7 0xb5e4eabe in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb17bd9f0 (LWP 17049)): [KCrash Handler] #6 0xb664c157 in QAbstractScrollArea::verticalScrollBar (this=0x82c16a0) at widgets/qabstractscrollarea.cpp:633 #7 0xb746d0c9 in restoreScrollBarState (this=0x84f0108) at /usr/src/debug/kdelibs-4.8.4/kdeui/itemviews/kviewstatesaver.cpp:68 #8 qt_static_metacall (_o=0x84efa50, _c=optimized out, _id=optimized out, _a=optimized out) at /usr/src/debug/kdelibs-4.8.4/build/kdeui/kviewstatesaver.moc:53 #9 KViewStateSaver::qt_static_metacall (_o=0x84efa50, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x85987e8) at /usr/src/debug/kdelibs-4.8.4/build/kdeui/kviewstatesaver.moc:46 #10 0xb6c6abc1 in QMetaCallEvent::placeMetaCall (this=0x85e43d8, object=0x84efa50) at kernel/qobject.cpp:525 #11 0xb6c73d2b in QObject::event (this=0x84efa50, e=0x85e43d8) at kernel/qobject.cpp:1204 #12 0xb613f404 in notify_helper (e=0x85e43d8, receiver=0x84efa50, this=0x808f968) at kernel/qapplication.cpp:4551 #13 QApplicationPrivate::notify_helper (this=0x808f968, receiver=0x84efa50, e=0x85e43d8) at kernel/qapplication.cpp:4523 #14 0xb6144743 in QApplication::notify (this=0x85e43d8, receiver=0x84efa50, e=0x85e43d8) at kernel/qapplication.cpp:4280 #15 0xb74a7491 in KApplication::notify (this=0xbf884f2c, receiver=0x84efa50, event=0x85e43d8) at /usr/src/debug/kdelibs-4.8.4/kdeui/kernel/kapplication.cpp:311 #16 0xb6c58dce in QCoreApplication::notifyInternal
[Bug 249100] akonadi kolab/imap: double entry after edit
https://bugs.kde.org/show_bug.cgi?id=249100 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO CC||chrig...@fastmail.fm Resolution|--- |WORKSFORME --- Comment #4 from Christian Mollekopf chrig...@fastmail.fm --- I can't reproduce this with current master (~4.9), any instructions on how to reproduce this? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 259574] conflict resolution box appears a lot
https://bugs.kde.org/show_bug.cgi?id=259574 --- Comment #47 from Hussam Al-Tayeb hus...@visp.net.lb --- it's happening a lot again in kde 4.8.4 when an email is passed through spam filter but not filtered to go to a specific folder (other than the Inbox folder). -- 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 299355] crash right after starting kmail
https://bugs.kde.org/show_bug.cgi?id=299355 --- Comment #7 from Hussam Al-Tayeb hus...@visp.net.lb --- This is a dup of bug 301453 -- 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 259574] conflict resolution box appears a lot
https://bugs.kde.org/show_bug.cgi?id=259574 --- Comment #48 from Graeme Hewson b...@wormhole.me.uk --- I see it happen often when receiving mail in threads I've marked as Ignore and when doing Bogomail filtering. Ironically, I don't even want to do Bogomail filtering on the busy account (with the ignored threads), but due to bug 285802 I have to have filtering on all accounts or none (see my comment 6 there). -- 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 302226] New: Kmail crashed on close
https://bugs.kde.org/show_bug.cgi?id=302226 Bug ID: 302226 Severity: crash Version: 4.8.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail crashed on close Classification: Unclassified OS: Linux Reporter: sven.burmeis...@gmx.net Hardware: openSUSE RPMs Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (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.9-desktop x86_64 Distribution: openSUSE 12.1 (x86_64) -- Information about the crash: - What I was doing when the application crashed: After I clicked on the close icon in kmail's title-bar it crashed. -- Backtrace: Application: KMail (kmail), signal: Aborted [Current thread is 1 (Thread 0x7f895dd9f780 (LWP 7225))] Thread 3 (Thread 0x7f893f81e700 (LWP 7543)): #0 0x7f8958ed9e6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f894f573c12 in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7f894f573c49 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x7f8958ed5f05 in start_thread () from /lib64/libpthread.so.0 #4 0x7f895b0d110d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f893d402700 (LWP 24774)): #0 0x7f8958eda1eb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f895c602a8f in wait (time=3, this=0x1340140) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=optimized out, mutex=0x13403c8, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7f895c5f5e9f in QThreadPoolThread::run (this=0x1341810) at concurrent/qthreadpool.cpp:141 #4 0x7f895c60261b in QThreadPrivate::start (arg=0x1341810) at thread/qthread_unix.cpp:307 #5 0x7f8958ed5f05 in start_thread () from /lib64/libpthread.so.0 #6 0x7f895b0d110d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f895dd9f780 (LWP 7225)): [KCrash Handler] #6 0x7f895b02ad95 in raise () from /lib64/libc.so.6 #7 0x7f895b02c2ab in abort () from /lib64/libc.so.6 #8 0x7f895b65af2d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/libstdc++.so.6 #9 0x7f895b6590d6 in ?? () from /usr/lib64/libstdc++.so.6 #10 0x7f895b659103 in std::terminate() () from /usr/lib64/libstdc++.so.6 #11 0x7f895b659246 in __cxa_rethrow () from /usr/lib64/libstdc++.so.6 #12 0x7f895c61e2db in QHashData::detach_helper2 (this=0x7f88f0166580, node_duplicate=0x7f8953e83c10 QHashKUrl, QHashDummyValue::duplicateNode(QHashData::Node*, void*), node_delete=0x7f8953e83bb0 QHashKUrl, QHashDummyValue::deleteNode2(QHashData::Node*), nodeSize=32, nodeAlign=8) at tools/qhash.cpp:227 #13 0x7f8953e84782 in QHashKUrl, QHashDummyValue::detach_helper (this=0x77a18630) at /usr/include/QtCore/qhash.h:584 #14 0x7f8953e7f459 in detach (this=0x77a18630) at /usr/include/QtCore/qhash.h:303 #15 QHash (other=..., this=0x77a18630) at /usr/include/QtCore/qhash.h:282 #16 QSet (this=0x77a18630, other=...) at /usr/include/QtCore/qset.h:60 #17 QForeachContainer (t=..., this=0x77a18630) at /usr/include/QtCore/qglobal.h:2345 #18 Nepomuk::ResourceData::resetAll (this=0x7f88f0159c70, isDelete=true) at /usr/src/debug/kdelibs-4.8.4/nepomuk/core/resourcedata.cpp:174 #19 0x7f8953e7ff3e in Nepomuk::ResourceData::~ResourceData (this=0x7f88f0159c70, __in_chrg=optimized out) at /usr/src/debug/kdelibs-4.8.4/nepomuk/core/resourcedata.cpp:106 #20 0x7f8953e87f26 in Nepomuk::ResourceManagerPrivate::cleanupCache (this=optimized out, num=-1) at /usr/src/debug/kdelibs-4.8.4/nepomuk/core/resourcemanager.cpp:194 #21 0x7f8953e8816c in Nepomuk::ResourceManager::~ResourceManager (this=0x8ba580, __in_chrg=optimized out) at /usr/src/debug/kdelibs-4.8.4/nepomuk/core/resourcemanager.cpp:292 #22 0x7f8953e88239 in Nepomuk::ResourceManager::~ResourceManager (this=0x8ba580, __in_chrg=optimized out) at /usr/src/debug/kdelibs-4.8.4/nepomuk/core/resourcemanager.cpp:299 #23 0x7f895c7132f5 in QObjectPrivate::deleteChildren (this=0x664720) at kernel/qobject.cpp:1917 #24 0x7f895c71955c in QObject::~QObject (this=0x77a18a80, __in_chrg=optimized out) at kernel/qobject.cpp:927 #25 0x7f895ba8da1e in QApplication::~QApplication (this=0x77a18a80, __in_chrg=optimized out) at kernel/qapplication.cpp:1095 #26 0x00402e27 in ~KMailApplication (this=0x77a18a80, __in_chrg=optimized out) at /usr/src/debug/kdepim-4.8.4/kmail/main.cpp:42 #27 main (argc=optimized out, argv=optimized out) at /usr/src/debug/kdepim-4.8.4/kmail/main.cpp:113 Possible duplicates by query: bug 180214. 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 249100] akonadi kolab/imap: double entry after edit
https://bugs.kde.org/show_bug.cgi?id=249100 --- Comment #5 from Raimar Sandner kde-b...@404not-found.de --- I don't use the Kolab resource anymore, possibly this has been fixed in newer versions of KDE. Could someone who was also affected check? As far as I am concerned this bug can be closed. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 302228] New: Akonadi truncates incoming mail on IMAP resource
https://bugs.kde.org/show_bug.cgi?id=302228 Bug ID: 302228 Severity: critical Version: 4.8 Priority: NOR CC: kdepim-bugs@kde.org, vkra...@kde.org Assignee: er...@kde.org Summary: Akonadi truncates incoming mail on IMAP resource Classification: Unclassified OS: Linux Reporter: toro...@gmail.com Hardware: Gentoo Packages Status: UNCONFIRMED Component: IMAP resource Product: Akonadi I configured kmail for a few different IMAP accounts. After a few days incoming emails bodies were displayed empty. A quick look at my webmail account showed that the e-mails were indeed empty (and I'm sure they had content when they were sent). After I've stopped akonadi incoming mails were unharmed again. Exiting kmail alone did not make a difference. So far this behavior only shows on one E-Mail account (provided by GMX). I'm unsure whether I can reproduce this. The risk of losing important information this way is just too big. Any suggestions how I can debug this without losing mails? Reproducible: Didn't try -- 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 302228] Akonadi truncates incoming mail on IMAP resource
https://bugs.kde.org/show_bug.cgi?id=302228 --- Comment #1 from Roman Zimmermann toro...@gmail.com --- BTW: I started off with a clean akonadi configuration. -- 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 299589] Some filters don't filter incoming messages automatically, only after manually applying all filters
https://bugs.kde.org/show_bug.cgi?id=299589 Sergey V Turchin z...@altlinux.org changed: What|Removed |Added CC||z...@altlinux.org -- 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 299968] Filters aren't applied on incoming mails
https://bugs.kde.org/show_bug.cgi?id=299968 Sergey V Turchin z...@altlinux.org changed: What|Removed |Added CC||z...@altlinux.org -- 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 300585] Kmail applies only the first of multiple rules within a filter.
https://bugs.kde.org/show_bug.cgi?id=300585 Sergey V Turchin z...@altlinux.org changed: What|Removed |Added CC||z...@altlinux.org -- 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 295051] Filters are not applied to newly received messages (IMAP)
https://bugs.kde.org/show_bug.cgi?id=295051 Sergey V Turchin z...@altlinux.org changed: What|Removed |Added CC||z...@altlinux.org -- 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 302230] New: Kontact crashed when trying to change notebooks in Kjots
https://bugs.kde.org/show_bug.cgi?id=302230 Bug ID: 302230 Severity: crash Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crashed when trying to change notebooks in Kjots Classification: Unclassified OS: Linux Reporter: dpi...@gmail.com Hardware: Fedora RPMs Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.3) KDE Platform Version: 4.8.3 (4.8.3) Qt Version: 4.8.2 Operating System: Linux 3.4.2-4.fc17.x86_64 x86_64 Distribution: Fedora release 17 (Beefy Miracle) -- Information about the crash: Trying to change notebooks in Kjots using the menu: Go - Previous Book. Caused Kontact to crash. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. 82T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f780e517880 (LWP 1959))] Thread 3 (Thread 0x7f780332d700 (LWP 1960)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:166 #1 0x0034ade1677d in WTF::TCMalloc_PageHeap::scavengerThread (this=0x34ae8009a0) at wtf/FastMalloc.cpp:2495 #2 0x0034ade16889 in WTF::TCMalloc_PageHeap::runScavengerThread (context=optimized out) at wtf/FastMalloc.cpp:1618 #3 0x003300c07d14 in start_thread (arg=0x7f780332d700) at pthread_create.c:309 #4 0x0033008f199d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7f7802a2c700 (LWP 1961)): #0 0x0033008e8eef in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x0033004479b4 in g_main_context_poll (n_fds=1, fds=0x7f77fc0029c0, timeout=8359, context=0x7f77fc0009a0, priority=optimized out) at gmain.c:3440 #2 g_main_context_iterate (context=context@entry=0x7f77fc0009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=error reading variable: Unhandled dwarf expression opcode 0xfa) at gmain.c:3141 #3 0x003300447ad4 in g_main_context_iteration (context=0x7f77fc0009a0, may_block=1) at gmain.c:3207 #4 0x003308da4506 in QEventDispatcherGlib::processEvents (this=0x7f77fc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x003308d7513f in QEventLoop::processEvents (this=this@entry=0x7f7802a2bd20, flags=...) at kernel/qeventloop.cpp:149 #6 0x003308d753c8 in QEventLoop::exec (this=0x7f7802a2bd20, flags=...) at kernel/qeventloop.cpp:204 #7 0x003308c78650 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #8 0x003308c7b5eb in QThreadPrivate::start (arg=0x24cb2a0) at thread/qthread_unix.cpp:307 #9 0x003300c07d14 in start_thread (arg=0x7f7802a2c700) at pthread_create.c:309 #10 0x0033008f199d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7f780e517880 (LWP 1959)): [KCrash Handler] #6 QModelIndex (other=..., this=0x7fff8d7b5370) at /usr/include/QtCore/qabstractitemmodel.h:65 #7 KJotsWidget::selectNext (this=0x3ad9160, role=42, step=-1) at /usr/src/debug/kdepim-4.8.3/kjots/kjotswidget.cpp:1209 #8 0x003308d8cb9f in QMetaObject::activate (sender=0x50d31f0, m=optimized out, local_signal_index=optimized out, argv=0x7fff8d7b5580) at kernel/qobject.cpp:3547 #9 0x0034a5dc41c2 in QAction::triggered (this=this@entry=0x50d31f0, _t1=false) at .moc/release-shared/moc_qaction.cpp:276 #10 0x0034a5dc43b0 in QAction::activate (this=0x50d31f0, event=optimized out) at kernel/qaction.cpp:1257 #11 0x0034a61fd1a3 in QMenuPrivate::activateCausedStack (this=this@entry=0x367eb40, causedStack=..., action=action@entry=0x50d31f0, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1028 #12 0x0034a62034b9 in QMenuPrivate::activateAction (this=0x367eb40, action=0x50d31f0, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1120 #13 0x0034a70fed70 in KMenu::mouseReleaseEvent (this=0x36e0920, e=0x7fff8d7b6120) at /usr/src/debug/kdelibs-4.8.3/kdeui/widgets/kmenu.cpp:464 #14 0x0034a5e19b50 in QWidget::event (this=0x36e0920, event=0x7fff8d7b6120) at kernel/qwidget.cpp:8371 #15 0x0034a620476b in QMenu::event (this=0x36e0920, e=0x7fff8d7b6120) at widgets/qmenu.cpp:2469 #16 0x0034a5dca37c in QApplicationPrivate::notify_helper (this=this@entry=0x2322150, receiver=receiver@entry=0x36e0920, e=e@entry=0x7fff8d7b6120) at kernel/qapplication.cpp:4551 #17 0x0034a5dcf05b in QApplication::notify (this=optimized out, receiver=0x36e0920, e=0x7fff8d7b6120) at kernel/qapplication.cpp:4094 #18 0x0034a7045a56 in KApplication::notify (this=0x7fff8d7b6df0, receiver=0x36e0920, event=0x7fff8d7b6120) at /usr/src/debug/kdelibs-4.8.3/kdeui/kernel/kapplication.cpp:311 #19 0x003308d763ee in QCoreApplication::notifyInternal (this=0x7fff8d7b6df0, receiver=0x36e0920,
[Bug 302233] New: Kontact crashes when deleting email
https://bugs.kde.org/show_bug.cgi?id=302233 Bug ID: 302233 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crashes when deleting email Classification: Unclassified OS: Linux Reporter: m...@gmx.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.9 beta2) KDE Platform Version: 4.8.90 (4.8.90) Qt Version: 4.8.1 Operating System: Linux 3.2.0-23-generic x86_64 Distribution: Ubuntu 12.04 LTS -- Information about the crash: - What I was doing when the application crashed: Sometimes when I delete an email message, Kontact will crash. I'm currently running Version 4.9 beta2 on KDE Platform Version 4.8.90 (4.8.90), Kubuntu 12.04 The crash can be reproduced some of the 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 0x7f3db3c117c0 (LWP 10433))] Thread 4 (Thread 0x7f3d967a5700 (LWP 10556)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f3db0417dec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f3db0417f19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f3dab8cbe9a in start_thread (arg=0x7f3d967a5700) at pthread_create.c:308 #4 0x7f3db11494bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 3 (Thread 0x7f3d95ea4700 (LWP 10559)): #0 0x7f3db113db03 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f3dab3ff036 in g_main_context_poll (n_fds=1, fds=0x7f3d900029c0, timeout=7677, context=0x7f3d99a0, priority=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3440 #2 g_main_context_iterate (dispatch=1, block=optimized out, context=0x7f3d99a0, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3141 #3 g_main_context_iterate (context=0x7f3d99a0, block=optimized out, dispatch=1, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3083 #4 0x7f3dab3ff164 in g_main_context_iteration (context=0x7f3d99a0, may_block=1) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3207 #5 0x7f3db18be426 in QEventDispatcherGlib::processEvents (this=0x7f3d98c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f3db188dc82 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f3db188ded7 in QEventLoop::exec (this=0x7f3d95ea3dc0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f3db178cfa7 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #9 0x7f3db178ffcb in QThreadPrivate::start (arg=0x1269130) at thread/qthread_unix.cpp:298 #10 0x7f3dab8cbe9a in start_thread (arg=0x7f3d95ea4700) at pthread_create.c:308 #11 0x7f3db11494bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #12 0x in ?? () Thread 2 (Thread 0x7f3d47f06700 (LWP 10730)): #0 0x7f3db113db03 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f3dab3ff036 in g_main_context_poll (n_fds=1, fds=0x7f3d400029b0, timeout=-1, context=0x7f3d49a0, priority=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3440 #2 g_main_context_iterate (dispatch=1, block=optimized out, context=0x7f3d49a0, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3141 #3 g_main_context_iterate (context=0x7f3d49a0, block=optimized out, dispatch=1, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3083 #4 0x7f3dab3ff164 in g_main_context_iteration (context=0x7f3d49a0, may_block=1) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3207 #5 0x7f3db18be426 in QEventDispatcherGlib::processEvents (this=0x7f3d48c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f3db188dc82 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f3db188ded7 in QEventLoop::exec (this=0x7f3d47f05d90, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f3db178cfa7 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #9 0x7f3db186d9ff in QInotifyFileSystemWatcherEngine::run (this=0x1cfbe80) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x7f3db178ffcb in QThreadPrivate::start (arg=0x1cfbe80) at thread/qthread_unix.cpp:298 #11 0x7f3dab8cbe9a in start_thread (arg=0x7f3d47f06700) at pthread_create.c:308 #12 0x7f3db11494bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #13 0x in ?? () Thread 1 (Thread 0x7f3db3c117c0 (LWP 10433)): [KCrash Handler] #6 0x0002 in ?? () #7
[Bug 249100] akonadi kolab/imap: double entry after edit
https://bugs.kde.org/show_bug.cgi?id=249100 --- Comment #6 from KDEBugs wombat...@gmail.com --- Please close this bug. A newer version has fixed the issue. Everything is now working. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 249100] akonadi kolab/imap: double entry after edit
https://bugs.kde.org/show_bug.cgi?id=249100 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WORKSFORME |FIXED -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 302235] New: Mail sending delayed or does not work / Freezes
https://bugs.kde.org/show_bug.cgi?id=302235 Bug ID: 302235 Severity: normal Version: 4.9 pre Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Mail sending delayed or does not work / Freezes Classification: Unclassified OS: Linux Reporter: m.w...@web.de Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kmail2 Since Kmail 4.9 Beta 2 (did not test Beta1) I experience an extreme delay (10 min or more) or indefinite freezes on sending emails. Killing Kmail then is the only solution. During those freezes I see highly cpu-usage of virtuoso-t (25-35%). Killing virtuoso-t just leads to a restart. Reproducible: Always Steps to Reproduce: 1. Write an Email 2. Send 3. Freeeze of Kmail (either indefinitely or fdor a very long time) -- 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 302242] New: BUG changing folders
https://bugs.kde.org/show_bug.cgi?id=302242 Bug ID: 302242 Severity: crash Version: 4.8.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: BUG changing folders Classification: Unclassified OS: Linux Reporter: aniello.barle...@buongiorno.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.4) KDE Platform Version: 4.8.4 (4.8.4) Qt Version: 4.8.1 Operating System: Linux 3.2.0-26-generic x86_64 Distribution: Ubuntu 12.04 LTS -- Information about the crash: - What I was doing when the application crashed: I've tried to open the incoming folder, starting from a manually-created folder, and kmail crashes -- 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 0x7fc7988547c0 (LWP 24280))] Thread 5 (Thread 0x7fc77bd5e700 (LWP 24281)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7fc795052dec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fc795052f19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fc790516e9a in start_thread (arg=0x7fc77bd5e700) at pthread_create.c:308 #4 0x7fc795d844bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 4 (Thread 0x7fc77b445700 (LWP 24282)): #0 0x7fc79001b930 in pthread_mutex_lock@plt () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fc7900855a1 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc79004a01b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc79004a164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc7964f9426 in QEventDispatcherGlib::processEvents (this=0x7fc7740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7fc7964c8c82 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #6 0x7fc7964c8ed7 in QEventLoop::exec (this=0x7fc77b444dc0, flags=...) at kernel/qeventloop.cpp:204 #7 0x7fc7963c7fa7 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #8 0x7fc7963cafcb in QThreadPrivate::start (arg=0x11c5610) at thread/qthread_unix.cpp:298 #9 0x7fc790516e9a in start_thread (arg=0x7fc77b445700) at pthread_create.c:308 #10 0x7fc795d844bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 3 (Thread 0x7fc727fff700 (LWP 24296)): #0 0x7fc795d78b03 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7fc79004a036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc79004a164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc7964f9426 in QEventDispatcherGlib::processEvents (this=0x7fc728c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7fc7964c8c82 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fc7964c8ed7 in QEventLoop::exec (this=0x7fc727ffed90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fc7963c7fa7 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7fc7964a89ff in QInotifyFileSystemWatcherEngine::run (this=0x12ac6d0) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7fc7963cafcb in QThreadPrivate::start (arg=0x12ac6d0) at thread/qthread_unix.cpp:298 #9 0x7fc790516e9a in start_thread (arg=0x7fc727fff700) at pthread_create.c:308 #10 0x7fc795d844bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 2 (Thread 0x7fc7277fe700 (LWP 24332)): #0 0x7fc795d770bd in read () at ../sysdeps/unix/syscall-template.S:82 #1 0x7fc7900848cf in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc790049ba4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc790049fd6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc79004a164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc7964f9426 in QEventDispatcherGlib::processEvents (this=0x7fc718002930, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7fc7964c8c82 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #7 0x7fc7964c8ed7 in QEventLoop::exec (this=0x7fc7277fdd90, flags=...) at kernel/qeventloop.cpp:204 #8 0x7fc7963c7fa7 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #9 0x7fc7964a89ff in QInotifyFileSystemWatcherEngine::run (this=0x34b3740) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x7fc7963cafcb in QThreadPrivate::start (arg=0x34b3740) at
[Bug 297136] Once quicksearch as been used, you can change of mail folders, but will always see the same mails
https://bugs.kde.org/show_bug.cgi?id=297136 Philipp Woelfel woel...@gmx.net changed: What|Removed |Added CC||woel...@gmx.net --- Comment #4 from Philipp Woelfel woel...@gmx.net --- I can confirm this bug for KDE 4.8.4 (OpenSuSE build) and the latest KDE 4.9 packages (probably beta2) available from OpenSuSE. This bug renders the folder quicksearch useless. Moreover, once I have accidentally entered something in there, I have to restart kmail2 in order to get back to a predictable behavior. Therefore, I think the bug is critical. -- 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 301924] Kontact crashes when I click on new message button
https://bugs.kde.org/show_bug.cgi?id=301924 kdes...@pedro.violates.us changed: What|Removed |Added CC||kdes...@pedro.violates.us -- 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 261559] KMail stopped recognizing KWallet for password for specific SMTP server
https://bugs.kde.org/show_bug.cgi?id=261559 Anthony RENOUX anthony.ren...@free.fr changed: What|Removed |Added CC||anthony.ren...@free.fr -- 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 293271] KMail doesn't remember the SMTP password
https://bugs.kde.org/show_bug.cgi?id=293271 Anthony RENOUX anthony.ren...@free.fr changed: What|Removed |Added CC||anthony.ren...@free.fr -- 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 302252] New: kontact crashes
https://bugs.kde.org/show_bug.cgi?id=302252 Bug ID: 302252 Severity: crash Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kontact crashes Classification: Unclassified OS: Linux Reporter: qw9876...@gmail.com Hardware: Fedora RPMs Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.3) KDE Platform Version: 4.8.3 (4.8.3) Qt Version: 4.8.2 Operating System: Linux 3.4.2-4.fc17.x86_64 x86_64 Distribution: Fedora release 17 (Beefy Miracle) -- Information about the crash: - What I was doing when the application crashed: kontact crashes on start up and also when I logged off and turn off the pc -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library /lib64/libthread_db.so.1. 82T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7fd570194880 (LWP 4915))] Thread 2 (Thread 0x7fd564c17700 (LWP 4916)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:166 #1 0x003cb041677d in WTF::TCMalloc_PageHeap::scavengerThread (this=0x3cb0e009a0) at wtf/FastMalloc.cpp:2495 #2 0x003cb0416889 in WTF::TCMalloc_PageHeap::runScavengerThread (context=optimized out) at wtf/FastMalloc.cpp:1618 #3 0x003042407d14 in start_thread (arg=0x7fd564c17700) at pthread_create.c:309 #4 0x0030420f199d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7fd570194880 (LWP 4915)): [KCrash Handler] #6 0x003042035965 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x003042037118 in __GI_abort () at abort.c:91 #8 0x00304a871234 in qt_message_output (msgType=msgType@entry=QtFatalMsg, buf=optimized out) at global/qglobal.cpp:2260 #9 0x00304a8713e8 in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, msg=0x304fc3e0a0 QWidget: Must construct a QApplication before a QPaintDevice, ap=ap@entry=0x7fff4a643de8) at global/qglobal.cpp:2306 #10 0x00304a871574 in qFatal (msg=optimized out) at global/qglobal.cpp:2489 #11 0x00304f60cebe in QWidgetPrivate::QWidgetPrivate (this=0x2341cb0, version=264194) at kernel/qwidget.cpp:321 #12 0x00304fa7cd5a in QDialogPrivate (this=0x2341cb0) at ../../src/gui/dialogs/qdialog_p.h:77 #13 QDialog::QDialog (this=0x1d63690, parent=0x0, f=...) at dialogs/qdialog.cpp:260 #14 0x003ca99a7fc9 in KDialog::KDialog (this=0x1d63690, parent=optimized out, flags=...) at /usr/src/debug/kdelibs-4.8.3/kdeui/dialogs/kdialog.cpp:190 #15 0x003ca99b8847 in KMessageBox::errorListWId (parent_id=0, text=..., strlist=..., caption=..., options=...) at /usr/src/debug/kdelibs-4.8.3/kdeui/dialogs/kmessagebox.cpp:840 #16 0x003ca99b8b45 in KMessageBox::error (parent=optimized out, text=..., caption=..., options=...) at /usr/src/debug/kdelibs-4.8.3/kdeui/dialogs/kmessagebox.cpp:821 #17 0x003cb749b97f in MailCommon::Kernel::emergencyExit (this=this@entry=0x2189fd0, reason=...) at /usr/src/debug/kdepim-4.8.3/mailcommon/mailkernel.cpp:185 #18 0x003cb749bd60 in MailCommon::Kernel::createDefaultCollectionDone (this=0x2189fd0, job=0x21a4400) at /usr/src/debug/kdepim-4.8.3/mailcommon/mailkernel.cpp:150 #19 0x00304a98cb9f in QMetaObject::activate (sender=0x21a4400, m=optimized out, local_signal_index=optimized out, argv=0x7fff4a6442e0) at kernel/qobject.cpp:3547 #20 0x003ca93336b2 in KJob::result (this=this@entry=0x21a4400, _t1=_t1@entry=0x21a4400) at /usr/src/debug/kdelibs-4.8.3/x86_64-redhat-linux-gnu/kdecore/kjob.moc:207 #21 0x003ca93336f0 in KJob::emitResult (this=0x21a4400) at /usr/src/debug/kdelibs-4.8.3/kdecore/jobs/kjob.cpp:318 #22 0x003ca93337ad in KJob::kill (this=0x21a4400, verbosity=KJob::EmitResult) at /usr/src/debug/kdelibs-4.8.3/kdecore/jobs/kjob.cpp:117 #23 0x003cad370357 in Akonadi::Session::clear (this=this@entry=0x1c7aa80) at /usr/src/debug/kdepimlibs-4.8.3/akonadi/session.cpp:425 #24 0x003cad3705e4 in Akonadi::Session::~Session (this=0x1c7aa80, __in_chrg=optimized out) at /usr/src/debug/kdepimlibs-4.8.3/akonadi/session.cpp:394 #25 0x003cad370629 in Akonadi::Session::~Session (this=0x1c7aa80, __in_chrg=optimized out) at /usr/src/debug/kdepimlibs-4.8.3/akonadi/session.cpp:396 #26 0x00304a879628 in QThreadStorageData::finish (p=0x1b0c658) at thread/qthreadstorage.cpp:203 #27 0x00304a9794df in QCoreApplicationPrivate::~QCoreApplicationPrivate (this=0x1b44450, __in_chrg=optimized out) at kernel/qcoreapplication.cpp:439 #28 0x00304f5c9649 in QApplicationPrivate::~QApplicationPrivate (this=0x1b44450, __in_chrg=optimized out) at kernel/qapplication.cpp:223 #29 0x00304a98dc3c in cleanup (pointer=optimized out) at ../../src/corelib/tools/qscopedpointer.h:62 #30 ~QScopedPointer (this=0x7fff4a6447f8, __in_chrg=optimized
[Bug 301924] Kontact crashes when I click on new message button
https://bugs.kde.org/show_bug.cgi?id=301924 --- Comment #1 from kdes...@pedro.violates.us --- Had the same problem, also on OpenSuse 12.1 But it was fixed when updating my packages. -- 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 302263] New: Adding Google account failed with: Parsing token page failed
https://bugs.kde.org/show_bug.cgi?id=302263 Bug ID: 302263 Severity: normal Version: 4.8 Priority: NOR CC: kdepim-bugs@kde.org Assignee: d...@progdan.cz Summary: Adding Google account failed with: Parsing token page failed Classification: Unclassified OS: Linux Reporter: lukas.za...@gmail.com Hardware: Other Status: UNCONFIRMED Component: Google Resource Product: Akonadi I am unable to add a Google account as it always fails. I use 2-step verification, but the issue was reproduced even with 2-step verification switched off. Reproducible: Always Steps to Reproduce: 1. akondadi configuration - add - google calendar and tasks 2. sign into google 3. enter PIN code (when 2-step configuration is ON) 4. allow access Actual Results: Parsing token failed Expected Results: token is obtains, account is added I am using fedora 17 (KDE 4.8.3) with akonadi-google-0.3.1-1.fc17.x86_64. -- 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 302263] Adding Google account failed with: Parsing token page failed
https://bugs.kde.org/show_bug.cgi?id=302263 Dan Vratil d...@progdan.cz changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Component|Google Resource |General Version Fixed In||0.4.1 Version|4.8 |0.4.0 Resolution|--- |DUPLICATE Product|Akonadi |libkgapi --- Comment #1 from Dan Vratil d...@progdan.cz --- *** This bug has been marked as a duplicate of bug 301240 *** -- 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 301240] Parsing token page failed
https://bugs.kde.org/show_bug.cgi?id=301240 Dan Vratil d...@progdan.cz changed: What|Removed |Added CC||lukas.za...@gmail.com --- Comment #7 from Dan Vratil d...@progdan.cz --- *** Bug 302263 has been marked as a duplicate of this bug. *** -- 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 302277] New: Email stuck in outbox
https://bugs.kde.org/show_bug.cgi?id=302277 Bug ID: 302277 Severity: normal Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Email stuck in outbox Classification: Unclassified OS: Linux Reporter: christopherhe...@gmail.com Hardware: RedHat RPMs Status: UNCONFIRMED Component: general Product: kmail2 I composed an email. I clicked send, assuming that it would be sent. A couple of hours later, I looked at kmail2's UI. There was still a message in the outbox. No sending progress bar showed. I clicked File-Send Queued Messages. The email still sat in the outbox, no progress bar showed. I rebooted my system, logged in again, restarted kmail2, and clicked File-Send Queued Messages. Still no joy. No diagnostic dialog. No diagnostic output on the console. Went to the outbox. Opened the message. Clicked send. It got sent. Reproducible: Always Expected Results: Send my email, or give me a dialog explaining that you're not going to do that and why you can't do that. -- 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 291760] Inline MIME-part with Content-Description is rendered inline but still listed as attachment
https://bugs.kde.org/show_bug.cgi?id=291760 Alexander Potashev aspotas...@gmail.com changed: What|Removed |Added CC||aspotas...@gmail.com --- Comment #1 from Alexander Potashev aspotas...@gmail.com --- In my opinion, it is handy to have all non-text objects (including inlined images, etc) in a list along with attachments. Otherwise one might not notice an inlined image when looking through an e-mail message. -- 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 302278] New: Message view does not respect JPEG orientation of inline images
https://bugs.kde.org/show_bug.cgi?id=302278 Bug ID: 302278 Severity: normal Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Message view does not respect JPEG orientation of inline images Classification: Unclassified OS: Linux Reporter: aspotas...@gmail.com Hardware: Gentoo Packages Status: NEW Component: UI Product: kmail2 Inlined JPEG image appears upside-down in the KMail's message view. Reproducible: Didn't try Steps to Reproduce: 1. Ask someone (probably yourself) to send you a photo with orientation info written in JPEG metadata. 2. Open the received message in the KMail's message view by single-clicking on it in the message list. Actual Results: 3. Look at the inlined image - it is possibly turned upside-down. Expected Results: 3. JPEG image in the correct orientation in the KMail's message view. 1. When saved in a file and opened in Gwenview, the photo can be seen in the correct orientation. 2. My e-mail message's source looks like this: ...some headers... --Apple-Mail-1FB7AC89-4950-444D-A787-9FDC466AFBB6 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii --Apple-Mail-1FB7AC89-4950-444D-A787-9FDC466AFBB6 Content-Disposition: inline; filename=photo.JPG Content-Type: image/jpeg; name=photo.JPG Content-Transfer-Encoding: base64 ...many letters and digits encoding the binary file... --Apple-Mail-1FB7AC89-4950-444D-A787-9FDC466AFBB6-- -- 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 244113] KNotes keeps re-enabling spell checking in notes when it starts
https://bugs.kde.org/show_bug.cgi?id=244113 Christopher Smith chry...@gmail.com changed: What|Removed |Added CC||chry...@gmail.com --- Comment #5 from Christopher Smith chry...@gmail.com --- Confirming on KDE/KNotes 4.8.2 on Gentoo. This bug has been outstanding for two years now; can we please get it confirmed? -- 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
