[Bug 297432] Kamil crashed after sending email
https://bugs.kde.org/show_bug.cgi?id=297432 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel mon...@kde.org --- Kmail crashed after I sent an email. MAybe because the name of the mail agent is empty, i.e. in kmail2 4.8.1 there is no possibility to enter a name for a mail agent (smtp) in the change dialogue. There is modify you can change name of smtp. Could you paste a screenshot where you try to change name ? -- 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 169937] Kontact's calendar misplaces the name of the month on the monthly report
https://bugs.kde.org/show_bug.cgi?id=169937 Tom tm@gmx-topmail.de changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- 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 297288] IMAP Attachments
https://bugs.kde.org/show_bug.cgi?id=297288 --- Comment #2 from Richard Ssekibuule rkayo...@gmail.com --- - Kmail/Kontact version 4.7.3 - KDE version 4.7.4 - Behavior reproducible all the time - Any size of attachment that I receive through IMAP - Configuration: IMAP E-Mail Server --- Same behavior with or without offline mode enabled - Server configured: imap.googlemail.com On Tue Apr 3 2012 15:33:55 Christophe Giboudeaux wrote: https://bugs.kde.org/show_bug.cgi?id=297288 Christophe Giboudeaux cgiboude...@gmx.com changed: What|Removed |Added Component|mail|general Version|4.7 pre |unspecified Product|kontact |kmail2 --- Comment #1 from Christophe Giboudeaux cgiboude...@gmx.com --- Please give more details: - Which kmail/kontact version ? - is it reproducible ? - how big are the attachements ? - how are the IMAP accounts configured ? (dimap, imap..) -- 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 297432] Kamil crashed after sending email
https://bugs.kde.org/show_bug.cgi?id=297432 --- Comment #2 from S. Burmeister sven.burmeis...@gmx.net --- Created attachment 70131 -- https://bugs.kde.org/attachment.cgi?id=70131action=edit dialogue that appears when clicking on modify, starting with server lacking name -- 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 297432] Kamil crashed after sending email
https://bugs.kde.org/show_bug.cgi?id=297432 --- Comment #3 from Laurent Montel mon...@kde.org --- it's the same dialog from kdepim 4.4 for example. And there is a rename button to rename it in treeview or when you create a new transport you can named it -- 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 297432] Kamil crashed after sending email
https://bugs.kde.org/show_bug.cgi?id=297432 --- Comment #4 from S. Burmeister sven.burmeis...@gmx.net --- You are right. However, if you click on add the same dialogue, i.e. without the possibility to give a name, is shown. Hence the user has to add without name and then rename. I think it would be better if at least the add would include the name input. Regarding the crash, I started kmail2 from scratch, i.e. no accounts, no akonadi data etc and it crashed after I added the smtp and sent the first email. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 277366] KMail2 needs a conversation view like GMail oder Apple Mail
https://bugs.kde.org/show_bug.cgi?id=277366 Michele michelu...@inventati.org changed: What|Removed |Added CC||michelu...@inventati.org --- Comment #1 from Michele michelu...@inventati.org --- this is a duplicate of bug 98383 -- 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 297450] New: Kontact crashed on exit
https://bugs.kde.org/show_bug.cgi?id=297450 Bug ID: 297450 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crashed on exit Classification: Unclassified OS: Linux Reporter: bernard.nys...@skynet.be Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.7.3) KDE Platform Version: 4.7.4 (4.7.4) Qt Version: 4.7.4 Operating System: Linux 3.0.0-17-generic x86_64 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: I wanted to quit Kontact by clicking on the Exit icon in the menu bar. When I did it, Kontact crashed... -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f69f00d57a0 (LWP 2671))] Thread 5 (Thread 0x7f69d6415700 (LWP 2672)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f69ec92ac2c in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f69ec92ad59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f69e7d22efc in start_thread (arg=0x7f69d6415700) at pthread_create.c:304 #4 0x7f69ed63a59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 4 (Thread 0x7f69d5afc700 (LWP 2673)): #0 0xff600140 in ?? () #1 0x7fff639ff7e7 in ?? () #2 0x7f69e750a07b in __GI_clock_gettime (clock_id=1, tp=0x7f69d5afbb70) at ../sysdeps/unix/clock_gettime.c:100 #3 0x7f69ee9b5074 in do_gettime (frac=0x7f69d5afbb88, sec=0x7f69d5afbb80) at tools/qelapsedtimer_unix.cpp:123 #4 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #5 0x7f69eea776ed in QTimerInfoList::updateCurrentTime (this=0x7f69d00020d0) at kernel/qeventdispatcher_unix.cpp:339 #6 0x7f69eea77a33 in QTimerInfoList::timerWait (this=0x7f69d00020d0, tm=...) at kernel/qeventdispatcher_unix.cpp:442 #7 0x7f69eea7644c in timerSourcePrepareHelper (src=optimized out, timeout=0x7f69d5afbc4c) at kernel/qeventdispatcher_glib.cpp:136 #8 0x7f69e7253ff2 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f69e7254dfd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f69e7255429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f69eea76f3e in QEventDispatcherGlib::processEvents (this=0x7f69d8b0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:424 #12 0x7f69eea4acf2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #13 0x7f69eea4aef7 in QEventLoop::exec (this=0x7f69d5afbde0, flags=...) at kernel/qeventloop.cpp:201 #14 0x7f69ee96227f in QThread::exec (this=optimized out) at thread/qthread.cpp:498 #15 0x7f69ee964d05 in QThreadPrivate::start (arg=0xaa1f40) at thread/qthread_unix.cpp:331 #16 0x7f69e7d22efc in start_thread (arg=0x7f69d5afc700) at pthread_create.c:304 #17 0x7f69ed63a59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #18 0x in ?? () Thread 3 (Thread 0x7f69857c1700 (LWP 2725)): #0 0x7f69e7d261fd in __pthread_mutex_unlock_usercnt (mutex=optimized out, decr=optimized out) at pthread_mutex_unlock.c:52 #1 __pthread_mutex_unlock (mutex=0x1447db8) at pthread_mutex_unlock.c:290 #2 0x7f69e7253fe4 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f69e7254dfd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f69e7255429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f69eea76f3e in QEventDispatcherGlib::processEvents (this=0x12d4690, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f69eea4acf2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f69eea4aef7 in QEventLoop::exec (this=0x7f69857c0db0, flags=...) at kernel/qeventloop.cpp:201 #8 0x7f69ee96227f in QThread::exec (this=optimized out) at thread/qthread.cpp:498 #9 0x7f69eea2dcbf in QInotifyFileSystemWatcherEngine::run (this=0x1370310) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x7f69ee964d05 in QThreadPrivate::start (arg=0x1370310) at thread/qthread_unix.cpp:331 #11 0x7f69e7d22efc in start_thread (arg=0x7f69857c1700) at pthread_create.c:304 #12 0x7f69ed63a59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #13 0x in ?? () Thread 2 (Thread 0x7f697a4cd700 (LWP 3539)): #0 0x7f69e7254404 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f69e7254e6a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f69e7255429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f69eea76f3e in QEventDispatcherGlib::processEvents
[Bug 296975] kmail2 does not show html mail
https://bugs.kde.org/show_bug.cgi?id=296975 Andre Klapper a9016...@gmx.de changed: What|Removed |Added CC||a9016...@gmx.de --- Comment #1 from Andre Klapper a9016...@gmx.de --- Note that the text/plain part of the email is empty so *in case* KMail prefers Plain Text over HTML this is not a 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
[Bug 297450] Kontact crashed on exit
https://bugs.kde.org/show_bug.cgi?id=297450 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel mon...@kde.org --- already fixed. Update your kdepim -- 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 297450] Kontact crashed on exit
https://bugs.kde.org/show_bug.cgi?id=297450 Laurent Montel mon...@kde.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- 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 297432] Kamil crashed after sending email
https://bugs.kde.org/show_bug.cgi?id=297432 --- Comment #5 from Laurent Montel mon...@kde.org --- When you add you have a dialogbox to select type of account and you can add name here. Ok for crash will look at. But bt is not when you send but when you create transport -- 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 297464] New: keep deleted mail from other users
https://bugs.kde.org/show_bug.cgi?id=297464 Bug ID: 297464 Severity: wishlist Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: keep deleted mail from other users Classification: Unclassified OS: Linux Reporter: diego.ercol...@gmail.com Hardware: Other Status: UNCONFIRMED Component: general Product: kmail2 caused by problems that I have described in bug #Bug 294027 I cannot use kmail anymore. I've opted for clawsmail that have a feature that is very useful: I have some cyrus-imap shared folder and in these folder my colleague can delete mails so from time to time I don't see mails if I don't read before him. Clawsmail periodically get via IMAP new mails and if some mail is deleted by my colleague, it shows mail greyed out telling that it had deleted but I can always see that mail for a while. After a period (I don't know if it is customizable) deleted mails disappears. I think this feature is very useful. -- 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 297465] New: KMail stops receive new mails after mysql restart
https://bugs.kde.org/show_bug.cgi?id=297465 Bug ID: 297465 Severity: normal Version: 4.8 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: KMail stops receive new mails after mysql restart Classification: Unclassified OS: Linux Reporter: vo.z...@gmail.com Hardware: Other Status: UNCONFIRMED Component: general Product: kmail2 Everytime I need to restart mysql server kmail stops to receive new mails. To fix that I need to open htop and terminate all akonadi server processes, then go back to the kmail window and do a manual email check. -- 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 297468] New: Kmail crashed after viewing 20+emails and switching to the next
https://bugs.kde.org/show_bug.cgi?id=297468 Bug ID: 297468 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail crashed after viewing 20+emails and switching to the next Classification: Unclassified OS: Linux Reporter: crgla...@gmail.com Hardware: openSUSE RPMs Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.0) KDE Platform Version: 4.8.1 (4.8.1) release 483 Qt Version: 4.8.0 Operating System: Linux 3.1.9-1.4-desktop x86_64 Distribution: openSUSE 12.1 (x86_64) -- Information about the crash: I had almost given up on Kontact/Kmail because it simply was not working. Too many issue to list. I decided to give it one more try. Although I have progressed further than any other time in the last 3 months it is still not ready for prime time. I am not a developer and I don't want to disparage their efforts. I do want to say though that this seems to be a project that should not have been released to the public. Simple task such as moving from one email to the next should not cause a crash. I will come back and try Kontact/Kmail again at some point in the future because there are many aspects of the package that are better than anything else available. But in the mean time I will continue to use TB. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f959a39f760 (LWP 9221))] Thread 9 (Thread 0x7f957bdcb700 (LWP 9224)): #0 0x7f959222ee6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9596bbcc12 in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7f9596bbcc49 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x7f959222af05 in start_thread () from /lib64/libpthread.so.0 #4 0x7f95978ae10d in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7f957b4ca700 (LWP 9225)): #0 0x7f95978a4ff3 in poll () from /lib64/libc.so.6 #1 0x7f9591d1ba98 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f9591d1bf59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f959801b526 in QEventDispatcherGlib::processEvents (this=0x7f95740008c0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f9597feb272 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f9597feb4c7 in QEventLoop::exec (this=0x7f957b4c9e20, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f9597eec137 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f9597eef15b in QThreadPrivate::start (arg=0x644110) at thread/qthread_unix.cpp:298 #8 0x7f959222af05 in start_thread () from /lib64/libpthread.so.0 #9 0x7f95978ae10d in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f9526a84700 (LWP 10257)): #0 0x7f959222f1eb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9597eef5cf in wait (time=3, this=0x156c9c0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=optimized out, mutex=0x156c938, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7f9597ee29df in QThreadPoolThread::run (this=0x157e570) at concurrent/qthreadpool.cpp:141 #4 0x7f9597eef15b in QThreadPrivate::start (arg=0x157e570) at thread/qthread_unix.cpp:298 #5 0x7f959222af05 in start_thread () from /lib64/libpthread.so.0 #6 0x7f95978ae10d in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f95275bf700 (LWP 10259)): #0 0x7f959222f1eb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9597eef5cf in wait (time=3, this=0x1c75da0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=optimized out, mutex=0x1df3418, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7f9597ee29df in QThreadPoolThread::run (this=0x1df6a20) at concurrent/qthreadpool.cpp:141 #4 0x7f9597eef15b in QThreadPrivate::start (arg=0x1df6a20) at thread/qthread_unix.cpp:298 #5 0x7f959222af05 in start_thread () from /lib64/libpthread.so.0 #6 0x7f95978ae10d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f9516ba2700 (LWP 10266)): #0 0x7f959222f1eb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9597eef5cf in wait (time=3, this=0x1838dc0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=optimized out, mutex=0x1918078, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7f9597ee29df in QThreadPoolThread::run (this=0x7f9520022c60) at concurrent/qthreadpool.cpp:141 #4 0x7f9597eef15b in QThreadPrivate::start (arg=0x7f9520022c60) at thread/qthread_unix.cpp:298 #5 0x7f959222af05 in start_thread () from /lib64/libpthread.so.0 #6 0x7f95978ae10d in clone () from /lib64/libc.so.6 Thread 4 (Thread
[Bug 296975] kmail2 does not show html mail
https://bugs.kde.org/show_bug.cgi?id=296975 --- Comment #2 from Martin Tlustos martin.tlus...@gmail.com --- No, I have prefer html over plain text enabled. -- 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 297331] Kmail crashed when trying saving an attachement
https://bugs.kde.org/show_bug.cgi?id=297331 Dimitrios Glentadakis dgl...@gmail.com changed: What|Removed |Added CC||dgl...@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
[Bug 297331] Kmail crashed when trying saving an attachement
https://bugs.kde.org/show_bug.cgi?id=297331 --- Comment #2 from Dimitrios Glentadakis dgl...@gmail.com --- Created attachment 70153 -- https://bugs.kde.org/attachment.cgi?id=70153action=edit New crash information added by DrKonqi kmail (1.13.7) on KDE Platform 4.6.5 (4.6.5) using Qt 4.7.4 - What I was doing when the application crashed: I was trying to download an attachement I have gmail with imap -- Backtrace (Reduced): #6 foldCase (haystack=0x29827ca, haystackLen=value optimized out, haystackOffset=value optimized out, needle=0x1f212ba, needleLen=9, cs=value optimized out) at tools/qchar.cpp:1202 #7 bm_find (haystack=0x29827ca, haystackLen=value optimized out, haystackOffset=value optimized out, needle=0x1f212ba, needleLen=9, cs=value optimized out) at tools/qstringmatcher.cpp:100 #8 qFindStringBoyerMoore (haystack=0x29827ca, haystackLen=value optimized out, haystackOffset=value optimized out, needle=0x1f212ba, needleLen=9, cs=value optimized out) at tools/qstringmatcher.cpp:319 #9 0x7f9c073bef5f in contains (this=0x28f34d0) at /usr/lib/qt4/include/QtCore/qstring.h:904 #10 KMail::ImapJob::slotGetNextMessage (this=0x28f34d0) at /usr/src/debug/kdepim-4.4.11.1/kmail/imapjob.cpp:311 -- 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 297331] Kmail crashed when trying saving an attachement
https://bugs.kde.org/show_bug.cgi?id=297331 Dimitrios Glentadakis dgl...@gmail.com changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|WORKSFORME |--- --- Comment #3 from Dimitrios Glentadakis dgl...@gmail.com --- i reopened as today i have again the crash -- 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 291890] Kmail2 ignores signatures of inline PGP messages
https://bugs.kde.org/show_bug.cgi?id=291890 Thomas Zell t.z...@gmx.de changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- --- Comment #4 from Thomas Zell t.z...@gmx.de --- Probably it's better to leave this as a bug reported against kmail2. So I'm marking the old bug report as a duplicate of this one. -- 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 247657] kwatchgnupg breaks gpg parsing of kmail
https://bugs.kde.org/show_bug.cgi?id=247657 Thomas Zell t.z...@gmx.de changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Thomas Zell t.z...@gmx.de --- still exists in kmail2 *** This bug has been marked as a duplicate of bug 291890 *** -- 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 291890] Kmail2 ignores signatures of inline PGP messages
https://bugs.kde.org/show_bug.cgi?id=291890 --- Comment #5 from Thomas Zell t.z...@gmx.de --- *** Bug 247657 has been marked as a duplicate of this 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
[Bug 297468] Kmail crashed after viewing 20+emails and switching to the next
https://bugs.kde.org/show_bug.cgi?id=297468 Christophe Giboudeaux cgiboude...@gmx.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christophe Giboudeaux cgiboude...@gmx.com --- *** This bug has been marked as a duplicate of bug 286307 *** -- 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 286307] Kmail crash (QNetworkAccessHttpBackend::replyDownloadMetaData, QNetworkAccessHttpBackend::qt_static_metacall, QObject::event)
https://bugs.kde.org/show_bug.cgi?id=286307 --- Comment #121 from Christophe Giboudeaux cgiboude...@gmx.com --- *** Bug 297468 has been marked as a duplicate of this 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
[Bug 289097] error Unable to fetch item from backend when entering IMAP folder
https://bugs.kde.org/show_bug.cgi?id=289097 Rolf Eike Beer k...@opensource.sf-tec.de changed: What|Removed |Added CC||k...@opensource.sf-tec.de --- Comment #23 from Rolf Eike Beer k...@opensource.sf-tec.de --- I see the very same error, but on 2 different hosts: #1: my N900. I'm using the KoMo packages from experiemental, updates at least once a week. Since I upgraded to the packages after the last build server outage (~4 weeks ago) I see this basically when entering any folder. Most often I'm asked immediately afterwards to enter my IMAP password once again, so this would match the previous comments about transfer delays. #2: my desktop machine, running openSUSE 12.1 AMD64. This has never been a problem before (at least for me), but since todays upgrade to 4.8.2 I see this when I try to look into the inbox. Other folders work, I can even read mails there. But if I read a new mail there it will not be marked as read, I also can't delete emails. I quit Kontact and did akonadictl stop and waited for all processes to disappear, but this didn't help in any way. -- 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 283484] KMail filters do not work on unread mails
https://bugs.kde.org/show_bug.cgi?id=283484 Guido Schmidt pande...@gmx.net changed: What|Removed |Added CC||pande...@gmx.net --- Comment #4 from Guido Schmidt pande...@gmx.net --- @Tobias: I've just updated from latest 4.7.x to 4.8.2 (SUSE12.1-RPMs) and since then incoming filters do not work anymore, neither automatically nor by hand. Marking messages as read has no effect. So, whatever youv'e changed it made things worse, at least in my case. -- 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 283484] KMail filters do not work on unread mails
https://bugs.kde.org/show_bug.cgi?id=283484 --- Comment #5 from Guido Schmidt pande...@gmx.net --- Please ignore my last comment. I did not relogin after the update. Filtering is working as expected. Sorry for having bothered you. -- 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 277711] Migration fails to fail if KWallet prompt cancelled
https://bugs.kde.org/show_bug.cgi?id=277711 --- Comment #1 from Szczepan Hołyszewski rula...@wp.pl --- At this point probably everyone who were to suffer from this bug suffered from it and got over it... -- 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 297500] New: Kontact crashed spnontaneously
https://bugs.kde.org/show_bug.cgi?id=297500 Bug ID: 297500 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crashed spnontaneously Classification: Unclassified OS: Linux Reporter: jbrsubscr...@gmail.com Hardware: openSUSE RPMs Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.2) KDE Platform Version: 4.8.2 (4.8.2) Qt Version: 4.8.1 Operating System: Linux 3.1.10-23-default x86_64 Distribution: openSUSE 12.1 (x86_64) -- Information about the crash: - Kontact crashed spontaneously. Not busy with anything in particular. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7fe4f319f760 (LWP 1701))] Thread 3 (Thread 0x7fe4da6b3700 (LWP 1702)): #0 0x7fe4eb041e6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe4ef9d1c12 in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7fe4ef9d1c49 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x7fe4eb03df05 in start_thread () from /lib64/libpthread.so.0 #4 0x7fe4f06c310d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fe4d9d9a700 (LWP 1703)): #0 0x7fe4f06b9ff3 in poll () from /lib64/libc.so.6 #1 0x7fe4eab2ea98 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe4eab2ef59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe4f0e312e6 in QEventDispatcherGlib::processEvents (this=0x7fe4d40008c0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7fe4f0e01012 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fe4f0e01267 in QEventLoop::exec (this=0x7fe4d9d99e20, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fe4f0d01547 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7fe4f0d0456b in QThreadPrivate::start (arg=0x75f6c0) at thread/qthread_unix.cpp:298 #8 0x7fe4eb03df05 in start_thread () from /lib64/libpthread.so.0 #9 0x7fe4f06c310d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fe4f319f760 (LWP 1701)): [KCrash Handler] #6 QNetworkAccessHttpBackend::replyDownloadMetaData (this=0x3359d70, hm=optimized out, sc=optimized out, rp=optimized out, pu=optimized out, db=optimized out, contentLength=-1) at access/qnetworkaccesshttpbackend.cpp:827 #7 0x7fe4ec008909 in QNetworkAccessHttpBackend::qt_static_metacall (_o=0x3359d70, _c=optimized out, _id=optimized out, _a=optimized out) at .moc/release-shared/moc_qnetworkaccesshttpbackend_p.cpp:91 #8 0x7fe4f0e1b2b6 in QObject::event (this=0x3359d70, e=optimized out) at kernel/qobject.cpp:1204 #9 0x7fe4f18160d4 in notify_helper (e=0x7fe48800c7a0, receiver=0x3359d70, this=0x637bc0) at kernel/qapplication.cpp:4554 #10 QApplicationPrivate::notify_helper (this=0x637bc0, receiver=0x3359d70, e=0x7fe48800c7a0) at kernel/qapplication.cpp:4526 #11 0x7fe4f181af53 in QApplication::notify (this=0x7fff74a39370, receiver=0x3359d70, e=0x7fe48800c7a0) at kernel/qapplication.cpp:4415 #12 0x7fe4f255a886 in KApplication::notify (this=0x7fff74a39370, receiver=0x3359d70, event=0x7fe48800c7a0) at /usr/src/debug/kdelibs-4.8.2/kdeui/kernel/kapplication.cpp:311 #13 0x7fe4f0e0222c in QCoreApplication::notifyInternal (this=0x7fff74a39370, receiver=0x3359d70, event=0x7fe48800c7a0) at kernel/qcoreapplication.cpp:876 #14 0x7fe4f0e05aca in sendEvent (event=0x7fe48800c7a0, receiver=0x3359d70) at kernel/qcoreapplication.h:231 #15 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x60da60) at kernel/qcoreapplication.cpp:1500 #16 0x7fe4f0e30e53 in sendPostedEvents () at kernel/qcoreapplication.h:236 #17 postEventSourceDispatch (s=0x643cf0) at kernel/qeventdispatcher_glib.cpp:279 #18 0x7fe4eab2e58d in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #19 0x7fe4eab2ed88 in ?? () from /usr/lib64/libglib-2.0.so.0 #20 0x7fe4eab2ef59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #21 0x7fe4f0e3127f in QEventDispatcherGlib::processEvents (this=0x60d320, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:424 #22 0x7fe4f18b976e in QGuiEventDispatcherGlib::processEvents (this=optimized out, flags=optimized out) at kernel/qguieventdispatcher_glib.cpp:204 #23 0x7fe4f0e01012 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #24 0x7fe4f0e01267 in QEventLoop::exec (this=0x7fff74a39300, flags=...) at kernel/qeventloop.cpp:204 #25 0x7fe4f0e05dc5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148 #26 0x00403919 in ?? () #27 0x7fe4f060923d in __libc_start_main () from /lib64/libc.so.6 #28 0x00403e51 in _start () Possible duplicates by query: bug 297468, bug 297174, bug 297059, bug 296901, bug 296658. Reported using DrKonqi -- You
[Bug 297134] Filter action mark as read doesn't mark as read anymore since 4.8.1
https://bugs.kde.org/show_bug.cgi?id=297134 sevens pe...@opzninges.nl changed: What|Removed |Added CC||pe...@opzninges.nl -- 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
