[Bug 292315] kmail crash while working in the inbox
https://bugs.kde.org/show_bug.cgi?id=292315 --- Comment #3 from Axel Braun --- Created attachment 72036 --> https://bugs.kde.org/attachment.cgi?id=72036&action=edit crash report another one bites the dust...on change of folders -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295780] Holiday Calendar for Serbia
https://bugs.kde.org/show_bug.cgi?id=295780 Christophe Giboudeaux changed: What|Removed |Added Status|NEW |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Christophe Giboudeaux --- Changing status -- 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 302337] New: In IMAP account Kmail2 does not show message body, but only headers and subject
https://bugs.kde.org/show_bug.cgi?id=302337 Bug ID: 302337 Severity: major Version: 4.8.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: In IMAP account Kmail2 does not show message body, but only headers and subject Classification: Unclassified OS: Linux Reporter: gkour...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kmail2 After a fresh installation of Kubuntu 12.04, IMAP gmail account works well in Kmail2. After few days the new messages come with not body text nor attachments. Only sender and headers are visible. Restart of Akonadi does not help. No errors are displayed. Same messages are visible through gmail web interface. Old messages are not affected and are with visible text. Read bugs 289734 and 298962 but there are not 100% same nor offering solutions. Reproducible: Always Steps to Reproduce: 1. Open kmail. 2. Wait for folder synchronization. 3. Click on any new gmail message received. Actual Results: Message header is displayed with no body text and no attachments. Expected Results: Message body text should be visible and attachments too. Read bugs 289734 and 298962 but there are not 100% same nor offering solutions (one of these dates back to 2009). -- 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 302337] In IMAP account Kmail2 does not show message body, but only headers and subject
https://bugs.kde.org/show_bug.cgi?id=302337 GK changed: What|Removed |Added Component|general |filtering --- Comment #1 from GK --- While just filed the bug, I noticed that in my gmail 'ALL MAIL' folder I have all messages duplicated. one has the Spamassanin in the header, the other does not. I set up the spam filter to exclude the gmail account and the messages started to appear normally (with body text and attachments). So the issue seems to be on the way the spam filter is treating messages. -- 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 295780] Holiday Calendar for Serbia
https://bugs.kde.org/show_bug.cgi?id=295780 --- Comment #5 from Milovan --- Hey, I didnt receive email notification about reply until status changed. I will tomorrow try to prepare file or at least provide you all info that is needed so we can complete this. Thanks, and sorry for a delay from my side. -- 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 302340] New: "save list" opens empty list dialogue
https://bugs.kde.org/show_bug.cgi?id=302340 Bug ID: 302340 Severity: normal Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: "save list" opens empty list dialogue Classification: Unclassified OS: Linux Reporter: martin.tlus...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: message list Product: kmail2 I have an email with about 160 recipients and would like to save it as a list/group. When opening the mail and using "save list," the list dialogue that opens up contains no addresses. Subsequently, saving is not possible as it complains that there are no addresses Reproducible: Always Steps to Reproduce: 1. Create a message with several addresses (to, CC, BCC) 2. click on "save list" 3. click on "save" in dialogue box Actual Results: Error message "add addresses first" (or similar), saving impossible Expected Results: addresses should be saved. -- 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 294272] Attachments within GPG-encrypted mails cannot be saved
https://bugs.kde.org/show_bug.cgi?id=294272 Stephan Schiffel changed: What|Removed |Added CC||stephan.schif...@gmx.de -- 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 302341] New: KMail crashes during mail composing
https://bugs.kde.org/show_bug.cgi?id=302341 Bug ID: 302341 Severity: crash Version: 4.8.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: KMail crashes during mail composing Classification: Unclassified OS: Linux Reporter: vojtech.zei...@opensuse.org 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: In composer window I right clicked to address field and choose to change order of refilling of adresses (rom various address books). Then KMail crashes. The crash does not seem to be reproducible. -- Backtrace: Application: KMail (kmail), signal: Aborted [Current thread is 1 (Thread 0x7fcce5d86780 (LWP 2256))] Thread 4 (Thread 0x7fccc7ae3700 (LWP 2941)): #0 0x7fcce0eb9e6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fccd7553c12 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7fccd7ef21a0) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #2 0x7fccd7553c49 in WTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #3 0x7fcce0eb5f05 in start_thread () from /lib64/libpthread.so.0 #4 0x7fcce30b110d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fccc71e2700 (LWP 2942)): #0 0x7fff4bbff8de in ?? () #1 0x7fccdb520d9a in clock_gettime () from /lib64/librt.so.1 #2 0x7fcce4639014 in do_gettime (frac=0x7fccc71e1bd8, sec=0x7fccc71e1bd0) at tools/qelapsedtimer_unix.cpp:123 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #4 0x7fcce471059d in QTimerInfoList::updateCurrentTime (this=0x7fccc00020d0) at kernel/qeventdispatcher_unix.cpp:343 #5 0x7fcce4710251 in timerSourceCheckHelper (src=) at kernel/qeventdispatcher_glib.cpp:150 #6 timerSourceCheckHelper (src=) at kernel/qeventdispatcher_glib.cpp:144 #7 0x7fccdb26c264 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #8 0x7fccdb26cab2 in ?? () from /usr/lib64/libglib-2.0.so.0 #9 0x7fccdb26cf59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #10 0x7fcce470fe36 in QEventDispatcherGlib::processEvents (this=0x7fccc8c0, flags=) at kernel/qeventdispatcher_glib.cpp:426 #11 0x7fcce46df842 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #12 0x7fcce46dfa97 in QEventLoop::exec (this=0x7fccc71e1e00, flags=...) at kernel/qeventloop.cpp:204 #13 0x7fcce45df5f7 in QThread::exec (this=) at thread/qthread.cpp:501 #14 0x7fcce45e261b in QThreadPrivate::start (arg=0xae7460) at thread/qthread_unix.cpp:307 #15 0x7fcce0eb5f05 in start_thread () from /lib64/libpthread.so.0 #16 0x7fcce30b110d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fcc7e042700 (LWP 8124)): #0 0x7fff4bbff8de in ?? () #1 0x7fccdb520d9a in clock_gettime () from /lib64/librt.so.1 #2 0x7fcce4639014 in do_gettime (frac=0x7fcc7e041b58, sec=0x7fcc7e041b50) at tools/qelapsedtimer_unix.cpp:123 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #4 0x7fcce471059d in QTimerInfoList::updateCurrentTime (this=0x7fcc6c001cd0) at kernel/qeventdispatcher_unix.cpp:343 #5 0x7fcce47108d3 in QTimerInfoList::timerWait (this=0x7fcc6c001cd0, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #6 0x7fcce470f30c in timerSourcePrepareHelper (src=, timeout=0x7fcc7e041c3c) at kernel/qeventdispatcher_glib.cpp:136 #7 0x7fcce470f3b5 in timerSourcePrepare (source=, timeout=) at kernel/qeventdispatcher_glib.cpp:169 #8 0x7fccdb26bb22 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #9 0x7fccdb26c92d in ?? () from /usr/lib64/libglib-2.0.so.0 #10 0x7fccdb26cf59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #11 0x7fcce470fe36 in QEventDispatcherGlib::processEvents (this=0x7fcc6c0008c0, flags=) at kernel/qeventdispatcher_glib.cpp:426 #12 0x7fcce46df842 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #13 0x7fcce46dfa97 in QEventLoop::exec (this=0x7fcc7e041dd0, flags=...) at kernel/qeventloop.cpp:204 #14 0x7fcce45df5f7 in QThread::exec (this=) at thread/qthread.cpp:501 #15 0x7fcce46bf62f in QInotifyFileSystemWatcherEngine::run (this=0x348f570) at io/qfilesystemwatcher_inotify.cpp:248 #16 0x7fcce45e261b in QThreadPrivate::start (arg=0x348f570) at thread/qthread_unix.cpp:307 #17 0x7fcce0eb5f05 in start_thread () from /lib64/libpthread.so.0 #18 0x7fcce30b110d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fcce5d86780 (LWP 2256)): [KCrash Handler] #6 0x7fcce300ad95 in raise () from /lib64/libc.so.6 #7 0x7fcce300c2ab in abort (
[Bug 289898] Reply using HTML: links are styled underlined
https://bugs.kde.org/show_bug.cgi?id=289898 Bernd Oliver Sünderhauf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Bernd Oliver Sünderhauf --- *** This bug has been marked as a duplicate of bug 285359 *** -- 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 285359] links are made underlined when replying
https://bugs.kde.org/show_bug.cgi?id=285359 Bernd Oliver Sünderhauf changed: What|Removed |Added CC||pancho...@riseup.net --- Comment #3 from Bernd Oliver Sünderhauf --- *** Bug 289898 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 284681] Regression: kmail2 does not offer receipients from the address book which have more than one email address
https://bugs.kde.org/show_bug.cgi?id=284681 Bernd Oliver Sünderhauf changed: What|Removed |Added CC||pancho...@riseup.net --- Comment #3 from Bernd Oliver Sünderhauf --- Works for me in 4.8.3 -- 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 46411] Add table support to HTML composing
https://bugs.kde.org/show_bug.cgi?id=46411 Bernd Oliver Sünderhauf changed: What|Removed |Added CC||pancho...@riseup.net --- Comment #8 from Bernd Oliver Sünderhauf --- This issue depends on Bug 287540. -- 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 249558] Font size of pasted formatted text can not be changed
https://bugs.kde.org/show_bug.cgi?id=249558 Bernd Oliver Sünderhauf changed: What|Removed |Added CC||pancho...@riseup.net --- Comment #2 from Bernd Oliver Sünderhauf --- This issue depends on Bug 287540. -- 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 288928] "Default domain" preset reveals local hostname
https://bugs.kde.org/show_bug.cgi?id=288928 Bernd Oliver Sünderhauf changed: What|Removed |Added Severity|major |normal -- 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 290379] Umlauts are sorted incorrectly in the sender identity configuration table.
https://bugs.kde.org/show_bug.cgi?id=290379 Bernd Oliver Sünderhauf changed: What|Removed |Added CC||pancho...@riseup.net --- Comment #5 from Bernd Oliver Sünderhauf --- Works fine here on a German language system. So yes this shouldn't be a kmail-specific problem. @Gunter: Can you still reproduce it? If yes, can you reproduce it in other sorting contexts? -- 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 302344] New: kmail sends invitation confirmation using wrong smtp transport
https://bugs.kde.org/show_bug.cgi?id=302344 Bug ID: 302344 Severity: normal Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail sends invitation confirmation using wrong smtp transport Classification: Unclassified OS: Linux Reporter: g...@4-mail.net Hardware: Fedora RPMs Status: UNCONFIRMED Component: misc Product: kmail2 I have over six different mail accounts configured in Kontact with different identities and different smtp transports. If I get a appointment invitation on a not default inbox and confirm it kmail sends the confirmation with the correct sender address but using the default smtp transport. In my identities I've set the correct smtp transport. The smtp server of my default transport (kolab) rejects the mail because of not matching sender address, so I'm unable to send out confirmations. Reproducible: Always Actual Results: Mail with confirmation stays in out box. -- 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 302228] Akonadi truncates incoming mail on IMAP resource
https://bugs.kde.org/show_bug.cgi?id=302228 --- Comment #2 from Roman Zimmermann --- Perhaps, this duplicates #298962 . But I'm not recognized as the reporter - so I'm unable to close a duplicate. -- 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 298393] kmail2 IMAP corrupts new mail
https://bugs.kde.org/show_bug.cgi?id=298393 dino changed: What|Removed |Added CC||dino.mo...@hotmail.it --- Comment #6 from dino --- The mails appear but with an empty body. No text, nothing. Checking on the server via webmail confirms the deletion of the text by kmail. -- 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 302375] New: Segfault when open an email - every time
https://bugs.kde.org/show_bug.cgi?id=302375 Bug ID: 302375 Severity: normal Version: 4.8.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Segfault when open an email - every time Classification: Unclassified OS: Linux Reporter: b...@univention.de Hardware: Archlinux Packages Status: UNCONFIRMED Component: general Product: kmail2 every time i open a specific email my kmail crashes with a Segementation fault. how/where can i get the email to post it here? i grepped in ~/.kde4/share/apps/kmail/mail for the subject and sender but did not get any matches. Reproducible: Always Steps to Reproduce: 1. open the email 2. segmentation fault 3. Actual Results: segfault Expected Results: seeing email content Application: kmail (4.8.4) KDE Platform Version: 4.8.4 (4.8.4) Qt Version: 4.8.2 Operating System: Linux 3.4.2-2-ARCH x86_64 -- Information about the crash: The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0370540780 (LWP 2371))] Thread 6 (Thread 0x7f035183c700 (LWP 2374)): #0 0x7f036b6ed8f4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7f036203137d in ?? () from /usr/lib/libQtWebKit.so.4 #2 0x7f0362031489 in ?? () from /usr/lib/libQtWebKit.so.4 #3 0x7f036b6e9e0e in start_thread () from /lib/libpthread.so.0 #4 0x7f036d8ed1ed in clone () from /lib/libc.so.6 Thread 5 (Thread 0x7f0350f3b700 (LWP 2375)): #0 0x7fff99fff8bf in clock_gettime () #1 0x7f0365260f6d in clock_gettime () from /lib/librt.so.1 #2 0x7f036e194344 in ?? () from /usr/lib/libQtCore.so.4 #3 0x7f036e26730d in ?? () from /usr/lib/libQtCore.so.4 #4 0x7f036e267653 in ?? () from /usr/lib/libQtCore.so.4 #5 0x7f036e2661cc in ?? () from /usr/lib/libQtCore.so.4 #6 0x7f0366211faf in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #7 0x7f036621269b in ?? () from /usr/lib/libglib-2.0.so.0 #8 0x7f0366212894 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #9 0x7f036e266b06 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQtCore.so.4 #10 0x7f036e23763f in QEventLoop::processEvents(QFlags) () from /usr/lib/libQtCore.so.4 #11 0x7f036e2378c8 in QEventLoop::exec(QFlags) () from /usr/lib/libQtCore.so.4 #12 0x7f036e13b6e0 in QThread::exec() () from /usr/lib/libQtCore.so.4 #13 0x7f036e13e67b in ?? () from /usr/lib/libQtCore.so.4 #14 0x7f036b6e9e0e in start_thread () from /lib/libpthread.so.0 #15 0x7f036d8ed1ed in clone () from /lib/libc.so.6 Thread 4 (Thread 0x7f030a86d700 (LWP 2500)): #0 0x7f036b6edc61 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7f036e13ead7 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4 #2 0x7f036e13238f in ?? () from /usr/lib/libQtCore.so.4 #3 0x7f036e13e67b in ?? () from /usr/lib/libQtCore.so.4 #4 0x7f036b6e9e0e in start_thread () from /lib/libpthread.so.0 #5 0x7f036d8ed1ed in clone () from /lib/libc.so.6 Thread 3 (Thread 0x7f030269f700 (LWP 2502)): #0 0x7f036b6edc61 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7f036e13ead7 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4 #2 0x7f036e13238f in ?? () from /usr/lib/libQtCore.so.4 #3 0x7f036e13e67b in ?? () from /usr/lib/libQtCore.so.4 #4 0x7f036b6e9e0e in start_thread () from /lib/libpthread.so.0 #5 0x7f036d8ed1ed in clone () from /lib/libc.so.6 Thread 2 (Thread 0x7f02f3fff700 (LWP 2503)): #0 0x7f036b6edc61 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7f036e13ead7 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4 #2 0x7f036e13238f in ?? () from /usr/lib/libQtCore.so.4 #3 0x7f036e13e67b in ?? () from /usr/lib/libQtCore.so.4 #4 0x7f036b6e9e0e in start_thread () from /lib/libpthread.so.0 #5 0x7f036d8ed1ed in clone () from /lib/libc.so.6 Thread 1 (Thread 0x7f0370540780 (LWP 2371)): [KCrash Handler] #5 0x7f036c898fed in ?? () from /usr/lib/libQtNetwork.so.4 #6 0x7f036c913d4a in ?? () from /usr/lib/libQtNetwork.so.4 #7 0x7f036e24d2ae in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #8 0x7f036e759f7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #9 0x7f036e75e3fa in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #10 0x7f036ff6fc66 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #11 0x7f036e2388ee in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #12 0x7f036e23c251 in QCoreApplicationPrivate::sendPostedEvents(Q
[Bug 302378] New: KMail produces a useless notification when an email is successfully sent
https://bugs.kde.org/show_bug.cgi?id=302378 Bug ID: 302378 Severity: wishlist Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: KMail produces a useless notification when an email is successfully sent Classification: Unclassified OS: Linux Reporter: alex.wauck+kdeb...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: UI Product: kmail2 The default is for KMail to produce a notification message when an email is successfully sent. I would argue that this is a bad default, since when the average person clicks "Send", they expect that the email will be sent. There is no need to notify the user in this manner upon success. If this is the default because it can sometimes take a while for messages to be sent, then the notification should be suppressed if the message is successfully sent within a certain amount of time (suggestion: 5 seconds). Take care that entering GPG or mail server passwords does not count toward this time limit. Reproducible: Always Steps to Reproduce: 1. Send an email. 2. Wait for notification to pop up in desktop's notification area Actual Results: Notification pops up. Expected Results: Nothing -- 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 290379] Umlauts are sorted incorrectly in the sender identity configuration table.
https://bugs.kde.org/show_bug.cgi?id=290379 Gunter Ohrner changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #6 from Gunter Ohrner --- I just checked, and this problem seems to be gone. However, I've not idea when and how it got fixed... I'm still running Kubuntu 11.10, yet with KDE 4.8.2 packages from KDE ppa and the QT-packages are listed with a "4:4.8.1" version number. -- 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 302381] New: Kmail consistent crash on first launch of day
https://bugs.kde.org/show_bug.cgi?id=302381 Bug ID: 302381 Severity: crash Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail consistent crash on first launch of day Classification: Unclassified OS: Linux Reporter: lightningstrik...@live.nl 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-26-generic i686 Distribution: Ubuntu 12.04 LTS -- Information about the crash: I have seen many bugs on here which look similar and may (or may not) be the same as this one, but there is one added little trigger which I have a feeling might help. This only happens to me when kmail is opened for the *first* time each day, or after I have rebooted during the day. Other sessions once the machine is switched on and kmail is accessed for the first time, function perfectly well. It is not just deleting objects either, it can be triggered by ANY function within kmail, from reading an email to clicking on a subfolder of your inbox to view its contents, emptying your wastebin, clicking on the top menu bar, whatever. However, this is now getting serious as there are an increasingly large number of reports since 4.8.2 coming out of these types of crashes. Attention would be welcomed :) The crash can be reproduced every time. -- 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 0xb5dbf740 (LWP 3615))] Thread 4 (Thread 0xb3cc1b40 (LWP 3619)): #0 0x00e12416 in __kernel_vsyscall () #1 0x01a3c96b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0x041a73dc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0xb6ff2263 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb6ff237f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0x01a38d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #6 0x04199ace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 3 (Thread 0xb3398b40 (LWP 3620)): #0 0x01efb3d0 in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0x01ebb6b6 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0x01ebbfaf in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x01ebc201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x00c008e7 in QEventDispatcherGlib::processEvents (this=0xb2a00468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x00bcc50d in QEventLoop::processEvents (this=0xb3398270, flags=...) at kernel/qeventloop.cpp:149 #6 0x00bcc7a9 in QEventLoop::exec (this=0xb3398270, flags=...) at kernel/qeventloop.cpp:204 #7 0x00ab594c in QThread::exec (this=0x918a940) at thread/qthread.cpp:501 #8 0x00ab5a3b in QThread::run (this=0x918a940) at thread/qthread.cpp:568 #9 0x00ab8de0 in QThreadPrivate::start (arg=0x918a940) at thread/qthread_unix.cpp:298 #10 0x01a38d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #11 0x04199ace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 2 (Thread 0xb18ffb40 (LWP 3623)): #0 0x00a98287 in __i686.get_pc_thunk.bx () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #1 0x00c0004c in postEventSourcePrepare (s=0x9431ae0, timeout=0xb18ff0bc) at kernel/qeventdispatcher_glib.cpp:255 #2 0x01ebb872 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x01ebbfaf in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x01ebc201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0x00c008e7 in QEventDispatcherGlib::processEvents (this=0x9433be0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x00bcc50d in QEventLoop::processEvents (this=0xb18ff240, flags=...) at kernel/qeventloop.cpp:149 #7 0x00bcc7a9 in QEventLoop::exec (this=0xb18ff240, flags=...) at kernel/qeventloop.cpp:204 #8 0x00ab594c in QThread::exec (this=0x94ed5b8) at thread/qthread.cpp:501 #9 0x00ba9b5d in QInotifyFileSystemWatcherEngine::run (this=0x94ed5b8) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x00ab8de0 in QThreadPrivate::start (arg=0x94ed5b8) at thread/qthread_unix.cpp:298 #11 0x01a38d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #12 0x04199ace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 1 (Thread 0xb5dbf740 (LWP 3615)): [KCrash Handler] #7 0x07af121d in QNetworkAccessHttpBackend::replyDownloadMetaData (this=0x998ee58, hm=, sc=0, rp=, pu=240, db=..., contentLength=-4165406276) at access/qnetworkaccesshttpbackend.cpp:827 #8 0x07b8837d in QNetworkAccessHttpBackend::qt_static_metacall (_o=0x998ee58, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xb2a26f40) at .moc/release-shared/moc_qnetworkaccesshttpbackend_p.cpp:91 #9 0x00bdfc01 in QMetaCallEvent::placeMeta
[Bug 302381] Kmail consistent crash on first launch of day or after reboot
https://bugs.kde.org/show_bug.cgi?id=302381 Thorsteinn A. Malmjursson changed: What|Removed |Added Summary|Kmail consistent crash on |Kmail consistent crash on |first launch of day |first launch of day or ||after reboot -- 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 302145] I cannot see a message without switch to html mode
https://bugs.kde.org/show_bug.cgi?id=302145 --- Comment #6 from Dimitrios Glentadakis --- Created attachment 72061 --> https://bugs.kde.org/attachment.cgi?id=72061&action=edit The normal behavior of kmail in html messages -- 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