[kmail2] [Bug 345497] Expiry options on folder properties doesn't move mails
https://bugs.kde.org/show_bug.cgi?id=345497 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #2 from Laurent Montel mon...@kde.org --- Work fine here. Do you have error in console ? -- 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 345509] kmail shows 1 email left in outgoing mail folder (list) after successful sent
https://bugs.kde.org/show_bug.cgi?id=345509 --- Comment #1 from Robert Simai rsi...@suse.com --- Created attachment 91731 -- https://bugs.kde.org/attachment.cgi?id=91731action=edit wrong count for the outgoing mail folder Postausgang -- 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 345327] GUI freezes when selecting an email for display
https://bugs.kde.org/show_bug.cgi?id=345327 --- Comment #1 from Marcus Hardt marcus.ha...@iwr.fzk.de --- Not sure, but I think I managed to mitigate this by removing unavailable mountpoints from /etc/fstab. It seems that (just like the file dialogue) checks all entries in fstab -- and depending on the network one is in cannot reach them and runs into a timeout. Therefore, I suggest network sharesto be checked in a background thread. -- 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 345509] kmail shows 1 email left in outgoing mail folder (list) after successful sent
https://bugs.kde.org/show_bug.cgi?id=345509 --- Comment #2 from Robert Simai rsi...@suse.com --- Created attachment 91732 -- https://bugs.kde.org/attachment.cgi?id=91732action=edit count reset after clicking the 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
[kmail2] [Bug 345509] New: kmail shows 1 email left in outgoing mail folder (list) after successful sent
https://bugs.kde.org/show_bug.cgi?id=345509 Bug ID: 345509 Summary: kmail shows 1 email left in outgoing mail folder (list) after successful sent Product: kmail2 Version: unspecified Platform: RedHat RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: rsi...@suse.com 4.14.6 (kmail-4.14.6-16.2.x86_64, current in openSUSE 13.2) but I believe the issue has been there before. Sending email through SMTP (TLS+authentication) reliably works while kmail still counts 1 email in the local outgoing mail folder (Postausgang). There's actually no mail left and all went fine, it's however indicated in the folder list and very misleading as it appears as if something went wrong. The 1 disappears when I click the (empty) folder. The error doesn't happen always but fairly often. I'll probably attach two screenshots. Please let me know if there's anything for me to try out to help fix this. Reproducible: Sometimes -- 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 345497] Expiry options on folder properties doesn't move mails
https://bugs.kde.org/show_bug.cgi?id=345497 --- Comment #3 from Christian cnngime...@gmail.com --- (In reply to Laurent Montel from comment #2) Work fine here. Do you have error in console ? I get this: $ kmail --nofork libpng warning: iCCP: Not recognizing known sRGB profile that has been edited loaded the Generic plugin libpng warning: iCCP: too many profiles libpng warning: iCCP: too many profiles [almost 40 times the same libpng warning] ~StorageServiceJobConfigPrivate I think is not of much help. If there's a way to start some kind of debug output, please tell me how. -- 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 286553] Kmail signed emails invalid in Thunderbird w/ Enigmail
https://bugs.kde.org/show_bug.cgi?id=286553 --- Comment #33 from Sandro Knauß kna...@kolabsys.com --- @Fabian: state of the bug is relsoveld/fixed. But there is a bug on enigmail side. The reference is the commandline gpg. If that says that the signature is correct, than the retrieving mail client has a bug. I'm not very familiar with gpg, but mails signed with thunderbird and kmail look quite different, too. It seems that kmail adds an attachment and thunderbird not. There are two different implementations for signing: inline and PGP/Mime. Inline shouldn't used these days, but if you say, that thunderbird don't create an attachment, than thunderbird send inline. You can treat kmail via options-encryption-inline to use inline. But I know the thunderbird also understands PGP/Mime. I dislike that bugs are captured to talk about different things. If there is a new one, than open an new bug. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 343114] gets stuck on one request that times out, kmail and akonadiconsole do not display any mail payloads anymore, stuck waiting
https://bugs.kde.org/show_bug.cgi?id=343114 Allen Winter win...@kde.org changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED CC||win...@kde.org -- 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 345517] New: KMail crashes on exit
https://bugs.kde.org/show_bug.cgi?id=345517 Bug ID: 345517 Summary: KMail crashes on exit Product: kmail2 Version: 4.14.1 Platform: Debian stable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: b...@humanleg.org.uk Application: kmail (4.14.1) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.16.0-4-amd64 x86_64 Distribution: Debian GNU/Linux 8.0 (jessie) -- Information about the crash: - What I was doing when the application crashed: Closing KMail. - Unusual behavior I noticed: KMail had been continually complaining that the KMail folders were broken because it couldn't write to one of the directories. I couldn't see why it couldn't write to the directory. - Custom settings of the application: Had just upgraded an old kmail1 setup with disconnected imap folders. -- 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 0x7f8952207800 (LWP 6549))] Thread 5 (Thread 0x7f892a1b1700 (LWP 6556)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f894382006f in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f89438200a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f894cd2c0a4 in start_thread (arg=0x7f892a1b1700) at pthread_create.c:309 #4 0x7f894f47704d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7f88e8990700 (LWP 6559)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f8943542973 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f894384f7f6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f894cd2c0a4 in start_thread (arg=0x7f88e8990700) at pthread_create.c:309 #4 0x7f894f47704d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7f88e7c88700 (LWP 6560)): #0 0x7ffd937a3a32 in clock_gettime () #1 0x7f894f483c9d in __GI___clock_gettime (clock_id=optimized out, tp=optimized out) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f894fd2ea05 in do_gettime (frac=synthetic pointer, sec=synthetic pointer) at tools/qelapsedtimer_unix.cpp:127 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:144 #4 0x7f894fe11789 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7f88d80030d0) at kernel/qeventdispatcher_unix.cpp:354 #5 0x7f894fe10667 in timerSourceCheckHelper (src=0x7f88d8003070) at kernel/qeventdispatcher_glib.cpp:150 #6 0x7f89471588c1 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f8947158e83 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f8947158ffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f894fe10d37 in QEventDispatcherGlib::processEvents (this=0x7f88d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #10 0x7f894fde0271 in QEventLoop::processEvents (this=this@entry=0x7f88e7c87dd0, flags=...) at kernel/qeventloop.cpp:149 #11 0x7f894fde05d5 in QEventLoop::exec (this=this@entry=0x7f88e7c87dd0, flags=...) at kernel/qeventloop.cpp:204 #12 0x7f894fcd4e99 in QThread::exec (this=optimized out) at thread/qthread.cpp:538 #13 0x7f894fcd770f in QThreadPrivate::start (arg=0x2617290) at thread/qthread_unix.cpp:349 #14 0x7f894cd2c0a4 in start_thread (arg=0x7f88e7c88700) at pthread_create.c:309 #15 0x7f894f47704d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f88e6533700 (LWP 6566)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f893a3d8dea in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x7f893a3d8e19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x7f894cd2c0a4 in start_thread (arg=0x7f88e6533700) at pthread_create.c:309 #4 0x7f894f47704d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f8952207800 (LWP 6549)): [KCrash Handler] #6 ref (this=0xfff8) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:121 #7 QVector (v=..., this=0x3f4a990) at ../../include/QtCore/../../src/corelib/tools/qvector.h:123 #8 QVectorQVectorQPersistentModelIndexData* ::realloc (this=this@entry=0x24fd788, asize=59957040, aalloc=optimized out) at ../../include/QtCore/../../src/corelib/tools/qvector.h:532 #9 0x7f894fdd699a in detach_helper (this=0x24fd788) at ../../include/QtCore/../../src/corelib/tools/qvector.h:337 #10 detach (this=0x24fd788) at ../../include/QtCore/../../src/corelib/tools/qvector.h:147 #11 data (this=0x24fd788) at
[kontact] [Bug 345523] New: Kontact crashes upon startup because of ManageSieve password and kdewallet
https://bugs.kde.org/show_bug.cgi?id=345523 Bug ID: 345523 Summary: Kontact crashes upon startup because of ManageSieve password and kdewallet 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: mede...@gmail.com Application: kontact (4.14.3) KDE Platform Version: 4.14.3 (Compiled from sources) Qt Version: 4.8.5 Operating System: Linux 3.19.2-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: I was login into my session after a boot up. Kontact automatically starts as it was running the last time I shutdown the computer. If I enter directly my masterpassword for the kdewallet everything's fine. PB happens if I am not in front of my PC while the session is started, like when I enter that masterpassword 10mins after I logged in. - Unusual behavior I noticed: 1. Behind the kdewallet pop up for entering the masterpassword, a Manage Sieve password pop-up from Kontact asking for the ManageSieve account password is shown. I believed like for the rest the password of ManageSieve is also stored in KDEWallet but I am not so sure anymore... 2. When I finally enter the masterpassword in the KDEWallet pop-up and then the ManageSieve password in the Kontact pop up, I get this crash of Kontact. This has been systematically happening. Not a big issue are restart the soft works very fine but it is not right either. - Custom settings of the application: Manage Sieve protocol configure connecting to a ManageSieve server integrated in a Dovecot IMAP install. net-mail/dovecot-2.2.13-r1 The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7fd3ffc037c0 (LWP 3680))] Thread 3 (Thread 0x7fd3df770700 (LWP 3682)): #0 0x7fd3f7a4b53f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd3faa9af6a in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7fd3faa9afa9 in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x7fd3f7a47204 in start_thread () from /lib64/libpthread.so.0 #4 0x7fd3fd1d65bd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fd3dee6f700 (LWP 3684)): #0 0x7fd3fd1cd96d in poll () from /lib64/libc.so.6 #1 0x7fd3f6e2c724 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fd3f6e2c82c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fd3fe5c5ebe in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #4 0x7fd3fe5974bf in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #5 0x7fd3fe5977b5 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #6 0x7fd3fe493abf in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4 #7 0x7fd3fe4961ff in ?? () from /usr/lib64/qt4/libQtCore.so.4 #8 0x7fd3f7a47204 in start_thread () from /lib64/libpthread.so.0 #9 0x7fd3fd1d65bd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fd3ffc037c0 (LWP 3680)): [KCrash Handler] #5 0x7fd3fe54f847 in QUrl::setUserName(QString const) () from /usr/lib64/qt4/libQtCore.so.4 #6 0x7fd39254a4d8 in ?? () from /usr/lib64/libkmanagesieve.so.4 #7 0x7fd39254a9cc in ?? () from /usr/lib64/libkmanagesieve.so.4 #8 0x7fd39254b4e9 in ?? () from /usr/lib64/libkmanagesieve.so.4 #9 0x7fd39254c224 in ?? () from /usr/lib64/libkmanagesieve.so.4 #10 0x7fd3fe5ac97a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #11 0x7fd3feab61a2 in ?? () from /usr/lib64/libkdecore.so.5 #12 0x7fd3fe5ac97a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #13 0x7fd3f89f593f in ?? () from /usr/lib64/qt4/libQtNetwork.so.4 #14 0x7fd3f89ef539 in ?? () from /usr/lib64/qt4/libQtNetwork.so.4 #15 0x7fd3fe5ac97a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #16 0x7fd3f89cf92d in ?? () from /usr/lib64/qt4/libQtNetwork.so.4 #17 0x7fd3f89d8b0d in ?? () from /usr/lib64/qt4/libQtNetwork.so.4 #18 0x7fd3fd95338c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #19 0x7fd3fd959b40 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #20 0x7fd3ff00f30a in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #21 0x7fd3fe59889d in QCoreApplication::notifyInternal(QObject*, QEvent*)
[kmail2] [Bug 345530] Kmail crashed when i was changing imap account options
https://bugs.kde.org/show_bug.cgi?id=345530 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||4.14.7 --- Comment #1 from Laurent Montel mon...@kde.org --- Fixed in 4.14.7 -- 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 345530] New: Kmail crashed when i was changing imap account options
https://bugs.kde.org/show_bug.cgi?id=345530 Bug ID: 345530 Summary: Kmail crashed when i was changing imap account options Product: kmail2 Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ra...@autistici.org Application: kmail (4.14.6) KDE Platform Version: 4.14.6 Qt Version: 4.8.6 Operating System: Linux 3.19.0-10-generic i686 Distribution: Ubuntu Vivid Vervet (development branch) -- Information about the crash: - What I was doing when the application crashed: I was changing the srver suscriptions of an imap google account -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0xade66780 (LWP 2515))] Thread 6 (Thread 0xac45eb40 (LWP 2518)): #0 0xb7763bdc in __kernel_vsyscall () #1 0xb55ec25c in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb5c9dcf6 in __pthread_cond_wait (cond=0xb3744cb0, mutex=0xb3744c98) at forward.c:149 #3 0xb2ecc9ac in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb2ecc9ff in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0xb55e71aa in start_thread (arg=0xac45eb40) at pthread_create.c:333 #6 0xb5c90fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 5 (Thread 0xabaacb40 (LWP 2519)): #0 0xb7763bdc in __kernel_vsyscall () #1 0xb55ec25c in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb5c9dcf6 in __pthread_cond_wait (cond=0xabbab7dc, mutex=0xabbab7c4) at forward.c:149 #3 0xb2efb9f3 in WTF::ThreadCondition::wait(WTF::Mutex) () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb2bd7574 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0xb2ee27c6 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #6 0xb2efb369 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #7 0xb55e71aa in start_thread (arg=0xabaacb40) at pthread_create.c:333 #8 0xb5c90fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 4 (Thread 0xaacffb40 (LWP 2522)): #0 0xb7763bdc in __kernel_vsyscall () #1 0xb5c863db in poll () at ../sysdeps/unix/syscall-template.S:81 #2 0xb3d39110 in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb3d2a004 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb3d2a146 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb6b3f634 in QEventDispatcherGlib::processEvents (this=0xaa300468, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #6 0xb6b0bd4f in QEventLoop::processEvents (this=0xaacff254, flags=...) at kernel/qeventloop.cpp:149 #7 0xb6b0c0de in QEventLoop::exec (this=0xaacff254, flags=...) at kernel/qeventloop.cpp:204 #8 0xb69f0acb in QThread::exec (this=0x91716f8) at thread/qthread.cpp:538 #9 0xb69f0ca8 in QThread::run (this=0x91716f8) at thread/qthread.cpp:605 #10 0xb69f369e in QThreadPrivate::start (arg=0x91716f8) at thread/qthread_unix.cpp:349 #11 0xb55e71aa in start_thread (arg=0xaacffb40) at pthread_create.c:333 #12 0xb5c90fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 3 (Thread 0xa9f0fb40 (LWP 2525)): #0 0xb3d26cf1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb3d2986b in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb3d29f9a in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb3d2a146 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb6b3f634 in QEventDispatcherGlib::processEvents (this=0xa9600468, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #5 0xb6b0bd4f in QEventLoop::processEvents (this=0xa9f0f224, flags=...) at kernel/qeventloop.cpp:149 #6 0xb6b0c0de in QEventLoop::exec (this=0xa9f0f224, flags=...) at kernel/qeventloop.cpp:204 #7 0xb69f0acb in QThread::exec (this=0x8ff38f0) at thread/qthread.cpp:538 #8 0xb6aeb886 in QInotifyFileSystemWatcherEngine::run (this=0x8ff38f0) at io/qfilesystemwatcher_inotify.cpp:265 #9 0xb69f369e in QThreadPrivate::start (arg=0x8ff38f0) at thread/qthread_unix.cpp:349 #10 0xb55e71aa in start_thread (arg=0xa9f0fb40) at pthread_create.c:333 #11 0xb5c90fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 2 (Thread 0xa5503b40 (LWP 6155)): #0 0xb7763bdc in __kernel_vsyscall () #1 0xb55ec25c in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb5c9dcf6 in __pthread_cond_wait (cond=0xb05868f0, mutex=0xb05868d8) at forward.c:149 #3 0xb04672df in ?? () from /usr/lib/i386-linux-gnu/libQtScript.so.4 #4 0xb046731c in ?? () from /usr/lib/i386-linux-gnu/libQtScript.so.4 #5 0xb55e71aa in start_thread (arg=0xa5503b40) at
[kmail2] [Bug 345497] Expiry options on folder properties doesn't move mails
https://bugs.kde.org/show_bug.cgi?id=345497 Simon Andric simonandr...@gmail.com changed: What|Removed |Added CC||simonandr...@gmail.com -- 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 286553] Kmail signed emails invalid in Thunderbird w/ Enigmail
https://bugs.kde.org/show_bug.cgi?id=286553 Fabian mays...@web.de changed: What|Removed |Added CC||mays...@web.de --- Comment #32 from Fabian mays...@web.de --- What's the current state of this bug? I'm using kmail 4.14.6 in openSUSE 13.2. My signed mails are not valid in thunderbird (enigmail) and k-9 mail (openkeychain). I'm not very familiar with gpg, but mails signed with thunderbird and kmail look quite different, too. It seems that kmail adds an attachment and thunderbird not. Is there any workaround known? It's really annoying if most people can't verify my not encrypted mails. -- 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
[kontact] [Bug 170621] Pending to-do summary ignores summary configuration
https://bugs.kde.org/show_bug.cgi?id=170621 Simon Andric simonandr...@gmail.com changed: What|Removed |Added CC||simonandr...@gmail.com -- 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
