[Bug 295821] %CURSOR command on reply to sender template not working
https://bugs.kde.org/show_bug.cgi?id=295821 Kurosch Sadjadi-Nasab xors...@gmx.net changed: What|Removed |Added CC||xors...@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 281227] KMail2 4.7's Find messages ... reproducibly fails to search: Unknown error. (Unable to create persistent search)
https://bugs.kde.org/show_bug.cgi?id=281227 --- Comment #25 from Robin Green gree...@greenrd.org --- (In reply to comment #24) I have updated to KDE 4.8 on an Opensuse 12.1 system with a complete fresh setup of Akonadi, Kmail etc. - meaning that I deleted all respective folders and config files. I than added all my IMAP resources again - which worked very well - and tried the search functionality via the search dialog. Defect: There still is no option to select the folder to search in. Bug: Then I tried some combined conditions for the search - it all gave an empty result set although there are lots of emails which fit the conditions. Then I tried a search with only one condition for the complete email text. This gave me a result list - but not a reliable one. So nothing has improved with KDE 4.8. The search dialog in my opinion is completely useless as it is right now. It sounds like while some other pretty serious bugs are still there, this PARTICULAR bug (Unknown error dialog box) is fixed in 4.8 for you, after you have deleted and re-added your resources. Can you confirm this? -- 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 291263] kaddressbook layout could be more compact
https://bugs.kde.org/show_bug.cgi?id=291263 --- Comment #2 from Jonathan Marten j...@keelhaul.me.uk --- For white space issue as reported in screen shot, see review https://git.reviewboard.kde.org/r/104308/ -- 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 296254] New: Kontact crashed after start
https://bugs.kde.org/show_bug.cgi?id=296254 Bug ID: 296254 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crashed after start Classification: Unclassified OS: Linux Reporter: o...@team-wieland.de Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.0) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.0.0-16-generic x86_64 Distribution: Ubuntu 11.10 -- Information about the crash: Kontact crash immediately after start. This happens not every time. The crash can be reproduced some of the time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f4f656197c0 (LWP 17954))] Thread 5 (Thread 0x7f4f49915700 (LWP 17955)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f4f61e5cc2c in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f4f61e5cd59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f4f5d629efc in start_thread (arg=0x7f4f49915700) at pthread_create.c:304 #4 0x7f4f62b6c59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 4 (Thread 0x7f4f48ffc700 (LWP 17956)): #0 0xff60017b in ?? () #1 0x7f4f48ffbb30 in ?? () #2 0x7fff0475d7e7 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 3 (Thread 0x7f4ef80ba700 (LWP 17976)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216 #1 0x7f4f631ad4ff in wait (time=3, this=0x31a39b0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=optimized out, mutex=0x31a3958, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7f4f631a067f in QThreadPoolThread::run (this=0x31a4960) at concurrent/qthreadpool.cpp:141 #4 0x7f4f631ad08b in QThreadPrivate::start (arg=0x31a4960) at thread/qthread_unix.cpp:298 #5 0x7f4f5d629efc in start_thread (arg=0x7f4ef80ba700) at pthread_create.c:304 #6 0x7f4f62b6c59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x in ?? () Thread 2 (Thread 0x7f4ef59f9700 (LWP 17978)): #0 0x7f4f5d156f4b in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f4f5d157dfd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4f5d158429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4f632dac06 in QEventDispatcherGlib::processEvents (this=0x300e5a0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f4f632aa3e2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f4f632aa637 in QEventLoop::exec (this=0x7f4ef59f8d90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f4f631aa067 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f4f6328a17f in QInotifyFileSystemWatcherEngine::run (this=0x31913c0) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7f4f631ad08b in QThreadPrivate::start (arg=0x31913c0) at thread/qthread_unix.cpp:298 #9 0x7f4f5d629efc in start_thread (arg=0x7f4ef59f9700) at pthread_create.c:304 #10 0x7f4f62b6c59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7f4f656197c0 (LWP 17954)): [KCrash Handler] #6 deref (this=0x2e0072006f00ca) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:133 #7 qAtomicAssignQDBusMessagePrivate (x=0x2b53c60, d=@0x2af7fb8) at ../../include/QtCore/../../src/corelib/thread/qatomic.h:200 #8 QDBusMessage::operator= (this=0x2af7fb8, other=...) at qdbusmessage.cpp:549 #9 0x7f4f5fc9a664 in QDBusConnectionPrivate::processFinishedCall (call=0x2af7f70) at qdbusintegrator.cpp:1795 #10 0x7f4f58f5445a in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #11 0x7f4f58f576ea in dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #12 0x7f4f5fc986d9 in q_dbus_connection_dispatch (connection=optimized out) at qdbus_symbols_p.h:115 #13 QDBusConnectionPrivate::doDispatch (this=0x2169880) at qdbusintegrator.cpp:1129 #14 0x7f4f5fc9c6a5 in QDBusConnectionPrivate::socketRead (this=0x2169880, fd=optimized out) at qdbusintegrator.cpp:1149 #15 0x7f4f632bf9e1 in QMetaObject::activate (sender=0x23045d0, m=optimized out, local_signal_index=optimized out, argv=0x7fff046d9e70) at kernel/qobject.cpp:3547 #16 0x7f4f6330c95e in QSocketNotifier::activated (this=optimized out, _t1=5) at .moc/release-shared/moc_qsocketnotifier.cpp:103 #17 0x7f4f632c8d6b in QSocketNotifier::event (this=0x23045d0, e=0x7fff046da4e0) at kernel/qsocketnotifier.cpp:317 #18 0x7f4f63c9f104 in
[Bug 296133] Possible duplicate
https://bugs.kde.org/show_bug.cgi?id=296133 Jan malte.ge...@googlemail.com changed: What|Removed |Added CC||malte.ge...@googlemail.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 296133] Possible duplicate
https://bugs.kde.org/show_bug.cgi?id=296133 --- Comment #1 from Jan malte.ge...@googlemail.com --- Created attachment 69705 -- https://bugs.kde.org/attachment.cgi?id=69705action=edit New crash information added by DrKonqi kmail (4.8.0) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0 - What I was doing when the application crashed: selecting an other email after clearing the filterbar -- Backtrace (Reduced): #6 0x7f1daead13a5 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x7f1daead4b0b in __GI_abort () at abort.c:92 [...] #9 0x7f1daeb156e6 in malloc_printerr (action=3, str=0x7f1daebfbf90 double free or corruption (fasttop), ptr=optimized out) at malloc.c:6283 #10 0x7f1daeb199cc in __GI___libc_free (mem=optimized out) at malloc.c:3738 #11 0x7f1dace2691e in qMetaTypeDeleteHelperQDBusMessage (t=0x7f1d880d32a0) at ../../include/QtCore/../../src/corelib/kernel/qmetatype.h:134 -- 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 296260] New: Find messages returns many blank results at start of results
https://bugs.kde.org/show_bug.cgi?id=296260 Bug ID: 296260 Severity: normal Version: 4.7 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Find messages returns many blank results at start of results Classification: Unclassified OS: Linux Reporter: gree...@greenrd.org Hardware: Fedora RPMs Status: UNCONFIRMED Component: general Product: kmail2 Searching for bug in the subject line of emails results in several screenfuls of completely blank results at the top of the search results (no data displayed whatsoever). The other results look valid. -- 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 296261] New: Results in Find Messages cannot be sorted by date
https://bugs.kde.org/show_bug.cgi?id=296261 Bug ID: 296261 Severity: normal Version: 4.7 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Results in Find Messages cannot be sorted by date Classification: Unclassified OS: Linux Reporter: gree...@greenrd.org Hardware: Fedora RPMs Status: UNCONFIRMED Component: general Product: kmail2 Nothing happens when clicking on the Date column header in the Find Messages dialog, to try to sort the results by date. Sorting by Receiver works, but sorting by date does not. -- 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 296261] Results in Find Messages cannot be sorted by date
https://bugs.kde.org/show_bug.cgi?id=296261 Robin Green gree...@greenrd.org changed: What|Removed |Added Severity|normal |minor --- Comment #1 from Robin Green gree...@greenrd.org --- This bug has an easy workaround: click on Open Search Folder and then sort the folder by date. -- 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 296263] New: Move to trash is greyed out in search results message list
https://bugs.kde.org/show_bug.cgi?id=296263 Bug ID: 296263 Severity: wishlist Version: 4.7 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Move to trash is greyed out in search results message list Classification: Unclassified OS: Linux Reporter: gree...@greenrd.org Hardware: Fedora RPMs Status: UNCONFIRMED Component: message list Product: kmail2 If you go to the Last Search message list, and right-click on a message, the option to move to trash is greyed out. I would like to be able to trash emails (i.e. move them from whatever folder they are actually in to the trash), from the search results. -- 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 296263] Move to trash is greyed out in search results message list
https://bugs.kde.org/show_bug.cgi?id=296263 --- Comment #1 from Robin Green gree...@greenrd.org --- Easy workaround: Double-click on the message to open it, then click the Trash button. -- 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 296264] New: No ACL management for kolab calendars
https://bugs.kde.org/show_bug.cgi?id=296264 Bug ID: 296264 Severity: wishlist Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: No ACL management for kolab calendars Classification: Unclassified OS: Linux Reporter: nm...@netcourrier.com Hardware: Other Status: UNCONFIRMED Component: libkdepim Product: kdepim User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20100101 Firefox/10.0.1 Build Identifier: Kolab calendars access rights can't be managed at all with Kontact or KOrganizer. kmail offers a nice GUI management of ACL with the 'Folder properties' context menu command. A similar GUI exists for a kolab's contacts list, but all buttons are greyed. No such GUI exists for a kolab's calendar. Reproducible: Always Actual Results: Kolab's contacts and calendars access rights can't be managed simply. Expected Results: A working GUI management system for kolab's calendars and contacts. -- 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 295484] filtering removes email's content
https://bugs.kde.org/show_bug.cgi?id=295484 --- Comment #11 from Sascha Manns sascha.ma...@open-slx.de --- Hi Andreas, i've attached a akonadiconsole log. I've tested it with 2 mails. The mail just contains: X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on saigkill.homelinux.net X-Spam-Level: *** X-Spam-Status: No, score=3.2 required=5.0 tests=BAYES_95,NO_RECEIVED,NO_RELAYS autolearn=no version=3.3.2 From: bugzilla_nore...@novell.com To: opensuse-b...@opensuse.org Subject: [Bug 752768] New: Cannot sort repositories by priority Message-ID: bug-752768-21...@http.bugzilla.novell.com/ Date: Sun, 18 Mar 2012 11:37:28 + X-Bogosity: Unsure, tests=bogofilter, spamicity=0.486134, version=1.2.1 MIME-Version: 1.0 The rtf is the produced log from that 2 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
[Bug 276635] In certain KMail2 setups filters dont get applied
https://bugs.kde.org/show_bug.cgi?id=276635 m.eik michalke m...@reaktanz.de changed: What|Removed |Added CC||m...@reaktanz.de --- Comment #9 from m.eik michalke m...@reaktanz.de --- (In reply to comment #7) So can somebody still reproduce the bug with _POP3_? i *had* this problem (filters weren't applied) with a setup of two POP3 accunts and KDE 4.8. both accounts were configured to deliver mails to the default inbox. after i changed one of them to put fetched mails in another local folder, filtering suddenly worked again (i think i had to log out and back in again). -- 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 295484] filtering removes email's content
https://bugs.kde.org/show_bug.cgi?id=295484 --- Comment #12 from Sascha Manns sascha.ma...@open-slx.de --- Created attachment 69707 -- https://bugs.kde.org/attachment.cgi?id=69707action=edit debug log -- 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 281227] KMail2 4.7's Find messages ... reproducibly fails to search: Unknown error. (Unable to create persistent search)
https://bugs.kde.org/show_bug.cgi?id=281227 --- Comment #26 from Ralph Moenchmeyer r...@anracon.de --- (In reply to comment #25) It sounds like while some other pretty serious bugs are still there, this PARTICULAR bug (Unknown error dialog box) is fixed in 4.8 for you, after you have deleted and re-added your resources. Can you confirm this? I changed to KDE 4.8.1 meanwhile (packages from Opensuse's KDE Release Repository). I did not delete my IMAP resources and reattach it to Akonadi/Kmail when I changed from KDE 4.8.0 to 4.8.1. So, right now I can only confirm that the search dialog again gives me the choice to select a folder to search in together with the option to include subfolders in the search. Now the search dialog looks similar again as it was for older KDE 4 versions with KMail 1.X. I tried a search for emails with a certain customer name as part of the FROM field (= sender's email address). I checked that such mails were located somewhere in the subfolders. This search did not work correctly. It did not return any hit. However, this may have to do with an incorrect or incomplete update of nepomuk's database during my steps from 4.8.0 to 4.8.1. Therefore, I shall perform the following experiments: I shall delete and reconfigure my IMAP access. I shall wait until the nepomuk/ virtuoso-t load on the cpu is back to almost zero - which may take some time. Then, I shall try a search with single and combined criteria for mails in the email folder structure and see if that works correctly. If this does not work as expected: I shall again delete the IMAP resource and in addition delete all Nepomuk folders and configuration files in ~/.kde4. Then I shall setup the IMAP connection again within Kmail and try some email searches again. So please be patient - it may take some time. But I promise to report the results as soon as I have them. -- 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 295726] kmail crashes every now and then during checking mails
https://bugs.kde.org/show_bug.cgi?id=295726 Gerhard Hoogterp gerh...@frappe.xs4all.nl changed: What|Removed |Added CC||gerh...@frappe.xs4all.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
[Bug 295726] kmail crashes every now and then during checking mails
https://bugs.kde.org/show_bug.cgi?id=295726 --- Comment #5 from Gerhard Hoogterp gerh...@frappe.xs4all.nl --- Created attachment 69708 -- https://bugs.kde.org/attachment.cgi?id=69708action=edit New crash information added by DrKonqi kontact (4.8.0) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0 Just reading mails. Nothing special, but kontact crashes very often lately at unrelated moments. -- Backtrace (Reduced): #6 0x7ff7cfc12a14 in malloc_consolidate (av=0x7ff7b020) at malloc.c:5161 #7 0x7ff7cfc13a4f in malloc_consolidate (av=0x7ff7b020) at malloc.c:5115 #8 _int_malloc (av=0x7ff7b020, bytes=65536) at malloc.c:4373 #9 0x7ff7cfc163cd in __GI___libc_malloc (bytes=65536) at malloc.c:3660 #10 0x7ff7d02be088 in QByteArray::realloc (this=0x7ff7b0027658, alloc=65504) at tools/qbytearray.cpp:1452 -- 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 296157] kmail crash when opening a mail
https://bugs.kde.org/show_bug.cgi?id=296157 Christophe Giboudeaux cgiboude...@gmx.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Christophe Giboudeaux cgiboude...@gmx.com --- *** This bug has been marked as a duplicate of bug 295474 *** -- 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 296075] Kmail crash when deleting email
https://bugs.kde.org/show_bug.cgi?id=296075 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 295474 *** -- 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 296013] Sporadic segfaults of KMail2
https://bugs.kde.org/show_bug.cgi?id=296013 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 295474 *** -- 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 296015] kmail crash when selecting a mail box
https://bugs.kde.org/show_bug.cgi?id=296015 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 295474 *** -- 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 296034] Crash while changing folder
https://bugs.kde.org/show_bug.cgi?id=296034 Christophe Giboudeaux cgiboude...@gmx.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Christophe Giboudeaux cgiboude...@gmx.com --- *** This bug has been marked as a duplicate of bug 295474 *** -- 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 296273] New: anti spam wizard classify as ... filters do not train messages (CRM114)
https://bugs.kde.org/show_bug.cgi?id=296273 Bug ID: 296273 Severity: normal Version: 4.8 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: anti spam wizard classify as ... filters do not train messages (CRM114) Classification: Unclassified OS: Linux Reporter: m...@reaktanz.de Hardware: Ubuntu Packages Status: UNCONFIRMED Component: filtering Product: kmail2 the anti spam wizard in kmail2 successfully detects CRM114 installations and creates some filter rules. two of them, classify as spam and classify as non-spam, are also added as buttons to the menu. these two filters don't work as intended. at least they do not actually train messages to improve the CRM114 filtering, because the wizard-generated filter invokes the mailreaver script by run program, and not pipe through program. in effect, mails filtered by these rules are only moved to other folders (if at all). you can check this by applying these filters on mails and examine the headers afterwards -- the CRM114 headers remain unchanged. the wizard should generate filters that pipe mails through the mailreaver script instead. -- 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 246027] Kmail stoped with: KMail encountered a fatal error and will terminate now. The error was: Timeout trying to get lock.
https://bugs.kde.org/show_bug.cgi?id=246027 Everard Brown everardbr...@perpetua.org.uk changed: What|Removed |Added CC||everardbr...@perpetua.org.u ||k --- Comment #9 from Everard Brown everardbr...@perpetua.org.uk --- This problem still occurs in kdepim-4.8.1-3.fc16.x86_64 immediately after I start kmail - all I want to do is read my email :( I don't like Thunderbird but at least it allows me to read email. $ kmail QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. loaded the Generic plugin kmail2(6611)/kdepimlibs (mailtransport): Could not access Outbox. [everard@sisko OA-rails]$ kmail2(6611)/libakonadi Akonadi::GetLockJob::Private::timeout: Timeout trying to get lock. Check who has acquired the name org.kde.pim.SpecialCollections on DBus, using qdbus or qdbusviewer. kmail2(6611)/libakonadi Akonadi::SpecialCollectionsRequestJobPrivate::lockResult: Failed to get lock: Timeout trying to get lock. kmail2(6611) MailCommon::Kernel::emergencyExit: KMail encountered a fatal error and will terminate now. The error was: Timeout trying to get lock. -- 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 296277] New: Error messages from POP3 resources not shown
https://bugs.kde.org/show_bug.cgi?id=296277 Bug ID: 296277 Severity: normal Version: 4.7 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Error messages from POP3 resources not shown Classification: Unclassified OS: Linux Reporter: gree...@greenrd.org Hardware: Fedora RPMs Status: UNCONFIRMED Component: UI Product: kmail2 Bug 225497 was actually at least 2 bugs combined, and this is the bug from there that was never adressed as far as I can see: POP3 resources do not display error messages to the user. For example, I got an error from my POP mail host saying mailbox in use (it was actually due to my mailbox being full). But all I saw in kmail was no mails being downloaded. I had to change it from a secure to an insecure connection and use wireshark to see what the error message was. -- 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 210383] Hability to mark Individual items as read, instead of global feed sources
https://bugs.kde.org/show_bug.cgi?id=210383 --- Comment #1 from Adrián Chaves Fernández adriyeticha...@gmail.com --- This is with the mixed view, by the way (Ctrl+Shift+3). It does not affect me anymore since I am using the Normal view isntead. -- 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 281227] KMail2 4.7's Find messages ... reproducibly fails to search: Unknown error. (Unable to create persistent search)
https://bugs.kde.org/show_bug.cgi?id=281227 --- Comment #27 from Ralph Moenchmeyer r...@anracon.de --- (In reply to comment #25) It sounds like while some other pretty serious bugs are still there, this PARTICULAR bug (Unknown error dialog box) is fixed in 4.8 for you, after you have deleted and re-added your resources. Can you confirm this? Back again with the first results. I deleted and re-added my IMAP resource. It took only some minutes until could access the folder structure, which includes several GB of mails in a folder structure with about 100 folders. However, the mail indexer took 150 minutes to index the contents. After that the search in a given folder worked for the FROM and TO fields . But I had to click twice on the search button to get the correct number of hits - especially when using wild cards in the search term. The indexing of mail adresses (better its segments) remains a puzzle to me. Searching for TO adresses that contain de gives less results than a search for *.de. A search for TO adresses that contain .de (with the dot) gives an empty result set. From that I would conclude that only segments of the address are indexed. But even then a search for de should give the same amount of hits as *.de - which is not the case. OR combinations of search criteria for the TO field do not seem to work at all - with or without wild cards. I did not try search conditions with AND criteria much, but they do not seem to work either. In addition, a recursive search through a folder hierarchy does not work. At least not over three or more levels of the hierarchy. Moreover, sometimes a search does not work at first. reformulating the search term may give you some hits. And afterwards suddenly the original search works, too. Worst of all - after trying some searches with combined conditions virtuoso-t suddenly ran amok - using 4 of my CPU cores at a 100% level. This could not be stopped by deactivating Nepomuk via KDE's system-settings. I had to kill the virtuso-t process explicitely. As an additional test, I am going to stop akonadi, then delete all nepomuk configuration files and nepomuk directories and start everything again. -- 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 296294] New: kmail hangs on mutex in Nepomuk::ResourceManagerPrivate::allResourceDataOfType()
https://bugs.kde.org/show_bug.cgi?id=296294 Bug ID: 296294 Severity: crash Version: 4.8 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail hangs on mutex in Nepomuk::ResourceManagerPrivate::allResourceDataOfType () Classification: Unclassified OS: Linux Reporter: sti...@att.net Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kmail2 It may be a duplicate of bug 291801, but that bug lacks any stacktrace to confirm it. Kmail (running as part of Kontact) sometimes hangs when switching between folders or switching to a different Kontact component; in the stack trace below, the hang was caused by switching from KMail component to Akregator. (gdb) bt #0 0xb7774424 in __kernel_vsyscall () #1 0xb609b8a7 in syscall () at ../sysdeps/unix/sysv/linux/i386/syscall.S:30 #2 0xb62a6638 in _q_futex (val2=0, addr2=0x0, timeout=0x0, val=2, op=0, addr=0xae96a7b0) at thread/qmutex_unix.cpp:99 #3 QMutexPrivate::wait (this=0xae96a7b0, timeout=-1) at thread/qmutex_unix.cpp:113 #4 0xb62a2038 in QMutex::lock (this=0xae9629e0) at thread/qmutex.cpp:164 #5 0xb364a980 in lockInline (this=0xae9629e0) at /usr/include/qt4/QtCore/qmutex.h:188 #6 QMutexLocker (m=0xae9629e0, this=synthetic pointer) at /usr/include/qt4/QtCore/qmutex.h:109 #7 Nepomuk::ResourceData::constHasType (this=0xae9629b8, uri=...) at ../../nepomuk/core/resourcedata.cpp:248 #8 0xb365510e in Nepomuk::ResourceManagerPrivate::allResourceDataOfType (this=0x8586038, type=...) at ../../nepomuk/core/resourcemanager.cpp:129 #9 0xb365645d in Nepomuk::ResourceManager::allResourcesOfType (this=0x85872c8, type=...) at ../../nepomuk/core/resourcemanager.cpp:373 #10 0xb366a98a in Nepomuk::Tag::allTags () at ../../nepomuk/core/tag.cpp:130 #11 0xadbbc680 in KMail::TagActionManager::createActions() () from /usr/lib/libkmailprivate.so.4 #12 0xadc759c2 in ?? () from /usr/lib/kde4/kmailpart.so #13 0xb5f82a84 in customEvent (ev=0xbfc2d66c, this=0x83f2c88) at ../../kparts/part.cpp:319 #14 KParts::Part::customEvent (this=0x83f2c88, ev=0xbfc2d66c) at ../../kparts/part.cpp:303 #15 0xb63d740c in QObject::event (this=0x83f2c88, e=0xbfc2d66c) at kernel/qobject.cpp:1226 #16 0xb6924d24 in notify_helper (e=0xbfc2d66c, receiver=0x83f2c88, this=0x8110320) at kernel/qapplication.cpp:4555 #17 QApplicationPrivate::notify_helper (this=0x8110320, receiver=0x83f2c88, e=0xbfc2d66c) at kernel/qapplication.cpp:4527 #18 0xb692a15d in QApplication::notify (this=0xbfc2d66c, receiver=0x83f2c88, e=0xbfc2d66c) at kernel/qapplication.cpp:4284 #19 0xb74a7801 in KApplication::notify (this=0xbfc2ece4, receiver=0x83f2c88, event=0xbfc2d66c) at ../../kdeui/kernel/kapplication.cpp:311 #20 0xb63bc0ae in QCoreApplication::notifyInternal (this=0xbfc2ece4, receiver=0x83f2c88, event=0xbfc2d66c) at kernel/qcoreapplication.cpp:876 #21 0xb5f8f3a0 in sendEvent (event=0xbfc2d66c, receiver=optimized out) at /usr/include/qt4/QtCore/qcoreapplication.h:231 #22 KParts::MainWindow::createGUI (this=0x82000e0, part=0x8ab6640) at ../../kparts/mainwindow.cpp:101 #23 0xb7741d93 in Kontact::MainWindow::selectPlugin(KontactInterface::Plugin*) () from /usr/lib/libkontactprivate.so.4 #24 0xb7741084 in ?? () from /usr/lib/libkontactprivate.so.4 #25 0xb63d2de1 in QMetaObject::activate (sender=0x81f2120, m=0xb77536e4, local_signal_index=0, argv=0xbfc2d8f8) at kernel/qobject.cpp:3547 #26 0xb7744bb5 in ?? () from /usr/lib/libkontactprivate.so.4 #27 0xb63d2de1 in QMetaObject::activate (sender=0x81ff830, m=0xb77539dc, local_signal_index=0, argv=0xbfc2d9d8) at kernel/qobject.cpp:3547 #28 0xb77458b5 in ?? () from /usr/lib/libkontactprivate.so.4 #29 0xb7745941 in ?? () from /usr/lib/libkontactprivate.so.4 #30 0xb63d2de1 in QMetaObject::activate (sender=0x810ffc0, m=0xb72a8868, local_signal_index=1, argv=0xbfc2daf4) at kernel/qobject.cpp:3547 #31 0xb6f346fd in QItemSelectionModel::currentChanged (this=0x810ffc0, _t1=..., _t2=...) at .moc/release-shared/moc_qitemselectionmodel.cpp:173 #32 0xb6f3487c in QItemSelectionModel::setCurrentIndex (this=0x810ffc0, index=..., command=...) at itemviews/qitemselectionmodel.cpp:1175 #33 0xb6edc40d in QAbstractItemView::mousePressEvent (this=0x81ff830, event=0xbfc2e494) at itemviews/qabstractitemview.cpp:1682 #34 0xb697f488 in QWidget::event (this=0x81ff830, event=0xbfc2e494) at kernel/qwidget.cpp:8357 #35 0xb6d9c135 in QFrame::event (this=0x81ff830, e=0xbfc2e494) at widgets/qframe.cpp:557 #36 0xb6e2ee21 in QAbstractScrollArea::viewportEvent (this=0x81ff830, e=0xbfc2e494) at widgets/qabstractscrollarea.cpp:1043 #37 0xb6ed4cdc in QAbstractItemView::viewportEvent (this=0x81ff830, event=0xbfc2e494) at itemviews/qabstractitemview.cpp:1644 #38 0xb6e31546 in viewportEvent (this=optimized out, event=0xbfc2e494) at widgets/qabstractscrollarea_p.h:100 #39 eventFilter (e=0xbfc2e494, this=optimized out, o=optimized
[Bug 296299] New: receiving pop3 mail causes unresobably high cpu abuse and meaningless blinking with status icon enabled
https://bugs.kde.org/show_bug.cgi?id=296299 Bug ID: 296299 Severity: normal Version: 1.99.0 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: receiving pop3 mail causes unresobably high cpu abuse and meaningless blinking with status icon enabled Classification: Unclassified OS: Linux Reporter: and...@alweb.dk Hardware: Other Status: NEW Component: general Product: kmail2 User-Agent: Mozilla/5.0 (X11; Linux i686) KHTML/4.8.1 (like Gecko) Konqueror/4.8 Build Identifier: Receiving mail with kmail2 + maildir + filters is painfully slow, receiving 10 mails sometimes takes 15 seconds of 60% CPU load. Most of the load appears to come from mysqld. Mail indexing is disabled. It also causes the conflict resolution dialog to show without user interaction, which is clearly a sign of misdesign! the changed data is always the update time. Maybe the update time is changed everytime a filter is run, without considering if that changes anything? This clearly shows that the filtering is done all wrong, it should be done from the top. The current way it feels like the secratary puts all mail in a pile on the desk, and starts ripping it out of my hands to sort it, while I try to read it. I have learned to never believe the ready in kmail2s statusbar, but check in the process table first if any possibly related processes are active. During the time, the status area icon is blinking, causing the entire plasma panel to relayout, often without changing the number of mails - this make me think that it is updated for no reason, every time a filter is run, matching or not. Running kmail without power available is bad, since it uses so much power that the battery time much affected (allthough having indexing disabled helps on that part, along with the fixes in the nepomuk area) There is no maildir or filter component of the akonadi procuct, so I thought I would file this here under kmail2. Sorry if that is all wrong. Reproducible: Always -- 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 257722] IMAP resource can't handle temporary network connection losses
https://bugs.kde.org/show_bug.cgi?id=257722 --- Comment #30 from Kevin Ottens er...@kde.org --- OK, thanks for trying. Kind of confirm my theory... Now the difficult point will be to find out why the others auth scheme create such an issue and how to work around it... -- 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 295473] under kde 4.8.1 in kmail, empty trash is grayed out if kmail is set to empty trash automatically when closed
https://bugs.kde.org/show_bug.cgi?id=295473 Paul Loughman snow...@mtaonline.net changed: What|Removed |Added CC||snow...@mtaonline.net --- Comment #5 from Paul Loughman snow...@mtaonline.net --- Kubuntu 12.04 (precise pangolin) 64-bit KDE 4.8.1 Kontact/Kmail 4.8.0 The option Empty local trash folde on program exit is not checked. Situation: Launch Kontact. Trash folder is empty. New email is received. Delete the new email and it goes to the Trash folder. Right-click on Trash and the option to Empty Trash is grayed out. Quit Kontact. Relaunch Kontact. Right-click on Trash and the option to Empty Trash is available - no longer grayed out. Delete any new email and it is added to the Trash folder. Right-click on Trash and the option to Empty Trash is still available. Leave the Trash Folder alone - do not empty it. Quit Kontact. Relaunch Kontact. Right-click on Trash and the option to Empty Trash is still available. Delete any new email and it is added to the Trash folder. Right-click on Trash and the option to Empty Trash is still available. Repeatable: ALWAYS. -- 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 295684] Total loss of e-mail content withspam-filters
https://bugs.kde.org/show_bug.cgi?id=295684 Lukas Polacek lu...@ksp.sk changed: What|Removed |Added CC||lu...@ksp.sk -- 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 295684] Total loss of e-mail content withspam-filters
https://bugs.kde.org/show_bug.cgi?id=295684 --- Comment #2 from Lukas Polacek lu...@ksp.sk --- I confirm that all my 3 IMAP accounts are affected by this bug and but not my POP3 account. Only these 9 fields are left in the header. In-Reply-To: References: Date: Message-ID: Subject: From: To: X-Bogosity: MIME-Version: Possible workaround: Turn off spam filtering on IMAP accounts, it's in the Advanced tab in the Filtering rules menu. -- 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 289831] Kontact crash after closing kontact with crashed korganizer
https://bugs.kde.org/show_bug.cgi?id=289831 Bruno Friedmann brun...@ioda.net changed: What|Removed |Added CC||brun...@ioda.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 289831] Kontact crash after closing kontact with crashed korganizer
https://bugs.kde.org/show_bug.cgi?id=289831 --- Comment #15 from Bruno Friedmann brun...@ioda.net --- Created attachment 69720 -- https://bugs.kde.org/attachment.cgi?id=69720action=edit New crash information added by DrKonqi kontact (4.8.0) on KDE Platform 4.8.1 (4.8.1) release 481 using Qt 4.8.0 - What I was doing when the application crashed: Playing with my mails during the whole day. Then when I ask to quit, there's a message in tray telling that akonadi has loose connection with the imap folder on which I was during the quit. Then kontact crash. Seems not fixed in 4.8.1 unfortunately ! -- Backtrace (Reduced): #7 ~QString (this=0xe1da040, __in_chrg=optimized out) at /usr/include/QtCore/qstring.h:880 #8 ~AddrSpec (this=0xe1da038, __in_chrg=optimized out) at /usr/src/debug/kdepimlibs-4.8.1/kmime/kmime_header_parsing.h:54 #9 ~Mailbox (this=0xe1da030, __in_chrg=optimized out) at /usr/src/debug/kdepimlibs-4.8.1/kmime/kmime_header_parsing.h:68 #10 node_destruct (to=0xe1da018, from=0xe1da018, this=optimized out) at /usr/include/QtCore/qlist.h:431 #11 QListKMime::Types::Mailbox::free (data=0xe1da000, this=optimized out) at /usr/include/QtCore/qlist.h:757 -- 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 289831] Kontact crash after closing kontact with crashed korganizer
https://bugs.kde.org/show_bug.cgi?id=289831 Colin J Thomson co...@g6avk.demon.co.uk changed: What|Removed |Added CC|co...@g6avk.demon.co.uk | -- 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 296310] New: Kontact crashed when opening an unread mail at first startup
https://bugs.kde.org/show_bug.cgi?id=296310 Bug ID: 296310 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crashed when opening an unread mail at first startup Classification: Unclassified OS: Linux Reporter: m_loui...@yahoo.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.0) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.0.0-16-generic x86_64 Distribution: Ubuntu 11.10 -- Information about the crash: The first time I open it and want to read a newly-received email, Kontact crashes. I had this twice today (and never before). Kde is set up to run Kontact at startup. The crash can be reproduced some of the time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97 in ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S [Current thread is 1 (Thread 0x7f1ab0d987c0 (LWP 3425))] Thread 5 (Thread 0x7f1aa1045700 (LWP 3475)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x003086186c2c in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x003086186d59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f1aabe9aefc in start_thread (arg=0x7f1aa1045700) at pthread_create.c:304 #4 0x7f1aae5f059d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 4 (Thread 0x7f1aa072c700 (LWP 3476)): #0 __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97 #1 0x7f1aae58d62f in _L_lock_10501 () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7f1aae58b9c1 in __GI___libc_free (mem=0x7f1a5020) at malloc.c:3736 #3 0x7f1aaea588d4 in QTimerInfoList::unregisterTimer (this=0x16b9410, timerId=335544325) at kernel/qeventdispatcher_unix.cpp:507 #4 0x7f1aaea45f51 in stop (this=0x16cc390) at kernel/qtimer.cpp:266 #5 QTimer::stop (this=0x16cc390) at kernel/qtimer.cpp:263 #6 0x7f1aaea46055 in QTimer::timerEvent (this=0x16cc390, e=optimized out) at kernel/qtimer.cpp:279 #7 0x7f1aaea418d9 in QObject::event (this=0x16cc390, e=optimized out) at kernel/qobject.cpp:1157 #8 0x7f1aaf41c104 in notify_helper (e=0x7f1aa072bb50, receiver=0x16cc390, this=0x14c3320) at kernel/qapplication.cpp:4555 #9 QApplicationPrivate::notify_helper (this=0x14c3320, receiver=0x16cc390, e=0x7f1aa072bb50) at kernel/qapplication.cpp:4527 #10 0x7f1aaf420f83 in QApplication::notify (this=0x7fff7c5145e0, receiver=0x16cc390, e=0x7f1aa072bb50) at kernel/qapplication.cpp:4416 #11 0x7f1ab014e9a6 in KApplication::notify (this=0x7fff7c5145e0, receiver=0x16cc390, event=0x7f1aa072bb50) at ../../kdeui/kernel/kapplication.cpp:311 #12 0x7f1aaea285fc in QCoreApplication::notifyInternal (this=0x7fff7c5145e0, receiver=0x16cc390, event=0x7f1aa072bb50) at kernel/qcoreapplication.cpp:876 #13 0x7f1aaea599a2 in sendEvent (event=0x7f1aa072bb50, receiver=optimized out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #14 QTimerInfoList::activateTimers (this=0x16b9410) at kernel/qeventdispatcher_unix.cpp:611 #15 0x7f1aaea5736d in timerSourceDispatch (source=optimized out) at kernel/qeventdispatcher_glib.cpp:186 #16 timerSourceDispatch (source=optimized out) at kernel/qeventdispatcher_glib.cpp:180 #17 0x7f1aaea57391 in idleTimerSourceDispatch (source=optimized out) at kernel/qeventdispatcher_glib.cpp:233 #18 0x003008844a5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x003008845258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x003008845429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7f1aaea57b9f in QEventDispatcherGlib::processEvents (this=0x16b8950, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:424 #22 0x7f1aaea273e2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #23 0x7f1aaea27637 in QEventLoop::exec (this=0x7f1aa072bdc0, flags=...) at kernel/qeventloop.cpp:204 #24 0x7f1aae927067 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #25 0x7f1aae92a08b in QThreadPrivate::start (arg=0x16b8190) at thread/qthread_unix.cpp:298 #26 0x7f1aabe9aefc in start_thread (arg=0x7f1aa072c700) at pthread_create.c:304 #27 0x7f1aae5f059d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #28 0x in ?? () Thread 3 (Thread 0x7f1a5603b700 (LWP 3770)): [KCrash Handler] #6 malloc_consolidate (av=0x7f1a5020) at malloc.c:5153 #7 0x7f1aae588a4f in malloc_consolidate (av=0x7f1a5020) at malloc.c:5115 #8 _int_malloc (av=0x7f1a5020,
[Bug 194591] Adding Feed to Akregator Causes Crash [Article::title, Private, ArticleModel, SelectionController::articleHeadersAvailable]
https://bugs.kde.org/show_bug.cgi?id=194591 --- Comment #110 from Sebastián Ramírez te...@adinet.com.uy --- Created attachment 69721 -- https://bugs.kde.org/attachment.cgi?id=69721action=edit New crash information added by DrKonqi akregator (4.7.2) on KDE Platform 4.7.2 (4.7.2) release 5 using Qt 4.7.4 - What I was doing when the application crashed: Akregator continuos fail at normal mode. Akregator falla continuamente en modo normal. -- Backtrace (Reduced): #6 0xb76658b4 in Akregator::Article::title (this=0x8482ef0) at /usr/src/debug/kdepim-4.7.2/akregator/src/article.cpp:375 #7 0xb26eb177 in Akregator::ArticleModel::Private::Private (this=0x86c8fc8, articles_=..., qq=0x0) at /usr/src/debug/kdepim-4.7.2/akregator/src/articlemodel.cpp:76 #8 0xb26eb38b in Akregator::ArticleModel::ArticleModel (this=0x8630630, articles=..., parent=0x0) at /usr/src/debug/kdepim-4.7.2/akregator/src/articlemodel.cpp:79 #9 0xb26f1ae9 in Akregator::SelectionController::articleHeadersAvailable (this=0x8272508, job=0x84cf790) at /usr/src/debug/kdepim-4.7.2/akregator/src/selectioncontroller.cpp:212 #10 0xb26f1e25 in Akregator::SelectionController::qt_metacall (this=0x8272508, _c=QMetaObject::InvokeMetaMethod, _id=optimized out, _a=0xbf83aa08) at /usr/src/debug/kdepim-4.7.2/build/akregator/src/selectioncontroller.moc:92 -- 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 194591] Adding Feed to Akregator Causes Crash [Article::title, Private, ArticleModel, SelectionController::articleHeadersAvailable]
https://bugs.kde.org/show_bug.cgi?id=194591 Colin J Thomson co...@g6avk.demon.co.uk changed: What|Removed |Added CC|co...@g6avk.demon.co.uk | -- 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 296319] New: IMAP resources sometimes crashes (or: random crashes on akonadi resources).
https://bugs.kde.org/show_bug.cgi?id=296319 Bug ID: 296319 Severity: crash Version: 4.8 Priority: NOR CC: kdepim-bugs@kde.org, vkra...@kde.org Assignee: er...@kde.org Summary: IMAP resources sometimes crashes (or: random crashes on akonadi resources). Classification: Unclassified OS: Linux Reporter: icama...@st-andes.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: IMAP resource Product: Akonadi Application: akonadi_imap_resource (4.8) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.2.9 x86_64 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: I have two imap accounts, and I just open kontact and leave it open (expecting to get new mail notifications). After a while, it stops getting new mails (I *know* I got new mails, because the phone reports them, but the messages are not there on kmail). I have a mail check interval of 3 minutes on one account, and interval mail checking disabled on the other one. After kmail stops sending notifications, I tried to manually check mail: no luck, still no new messages, so, I closed kontact closing the window, and then the crash message came. Also, I get this error message on akonadi startup: Fetch Job Error - Plasma Desktop Shell Unknown error. (Unable to fetch item from backend) And I also get the error for the KOrganizer Reminder Daemon when I start kontact (same Unknown error... message). In my case, akonadi is using PostgreSQL backend (external PostgreSQL server, ie: Use internal PostgreSQL server checkbox deselected, PostgreSQL 9.1). Just let me know if I can give you more information. On kdelibs, I'm using a patched version with patch from bug #295474 (I took sources from kubuntu ppa, KDE version 4.8.1) Thanks! Ildefonso Camargo The crash can be reproduced some of the time. -- Backtrace: Application: st-andes of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault [Current thread is 1 (Thread 0x7f3087ff27a0 (LWP 3283))] Thread 2 (Thread 0x7f306700 (LWP 31335)): #0 0x7f3083971473 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f30822c1f68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f30822c2429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3087424c06 in QEventDispatcherGlib::processEvents (this=0x16dbda0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f30873f43e2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f30873f4637 in QEventLoop::exec (this=0x7f306fffedc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f30872f4067 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f308602e619 in KIMAP::SessionThread::run (this=0x16d2a90) at ../../kimap/sessionthread.cpp:181 #8 0x7f30872f708b in QThreadPrivate::start (arg=0x16d2a90) at thread/qthread_unix.cpp:298 #9 0x7f3083229efc in start_thread (arg=0x7f306700) at pthread_create.c:304 #10 0x7f308397d59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7f3087ff27a0 (LWP 3283)): [KCrash Handler] #6 check_parent_thread (currentThreadData=optimized out, parentThreadData=optimized out, parent=0x16cf890) at kernel/qobject.cpp:696 #7 check_parent_thread (parent=0x16cf890, parentThreadData=optimized out, currentThreadData=optimized out) at kernel/qobject.cpp:685 #8 0x7f308740da57 in QObject::QObject (this=0x15895a0, parent=0x16cf890) at kernel/qobject.cpp:729 #9 0x7f3084299946 in KJob::KJob (this=0x15895a0, parent=optimized out) at ../../kdecore/jobs/kjob.cpp:50 #10 0x7f30860144ed in KIMAP::Job::Job (this=0x15895a0, dd=...) at ../../kimap/job.cpp:37 #11 0x7f3086029c41 in KIMAP::SelectJob::SelectJob (this=0x15895a0, session=optimized out) at ../../kimap/selectjob.cpp:55 #12 0x0041582f in ImapIdleManager::onSessionRequestDone (this=0x159ca10, requestId=optimized out, session=optimized out, errorCode=optimized out) at ../../../resources/imap/imapidlemanager.cpp:88 #13 0x00416300 in ImapIdleManager::qt_metacall (this=0x159ca10, _c=QMetaObject::InvokeMetaMethod, _id=optimized out, _a=0x7fff9a314550) at ./imapidlemanager.moc:88 #14 0x7f3087409be9 in QMetaObject::activate (sender=0x156efe0, m=optimized out, local_signal_index=optimized out, argv=0x7fff9a314550) at kernel/qobject.cpp:3566 #15 0x004541d2 in SessionPool::sessionRequestDone (this=optimized out, _t1=7, _t2=0x16cf890, _t3=0, _t4=optimized out) at ./sessionpool.moc:140 #16 0x0045677e in SessionPool::processPendingRequests (this=0x156efe0) at
