[Bug 307016] New: No wastebin for Local Folders resource means delete is permanent
https://bugs.kde.org/show_bug.cgi?id=307016 Bug ID: 307016 Severity: critical Version: 4.9.1 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: No wastebin for Local Folders resource means delete is permanent Classification: Unclassified OS: Linux Reporter: both1...@hotmail.com Hardware: Slackware Packages Status: UNCONFIRMED Component: mail Product: kontact It is not possible to specify a Wastebin/Trash folder when using the Local Maildir Folder resource. This means that deleting an email causes it to be permanently deleted without warning. If the mail is not in fact deleted, it is not clear where the message is placed after deletion. I believe that the same situation exists when using the KMail Mail Folder resource. 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 307022] New: akonadi_nepomuk_feeder : Segmentation fault (11)
https://bugs.kde.org/show_bug.cgi?id=307022 Bug ID: 307022 Severity: crash Version: 4.8 Priority: NOR CC: vkra...@kde.org Assignee: kdepim-bugs@kde.org Summary: akonadi_nepomuk_feeder : Segmentation fault (11) Classification: Unclassified OS: Linux Reporter: robert.ce...@blizevedly.cz Hardware: Ubuntu Packages Status: UNCONFIRMED Component: Nepomuk Feeder Agents Product: Akonadi Application: akonadi_nepomuk_feeder (4.8) KDE Platform Version: 4.8.5 (4.8.5) Qt Version: 4.8.1 Operating System: Linux 3.2.0-30-generic x86_64 Distribution: Ubuntu 12.04.1 LTS -- Information about the crash: feeder used in the background, running through Kontact. PC memory 16 GB, System 64-bit Kubuntu 12.04, no code modification. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Nepomuk Feeder (akonadi_nepomuk_feeder), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [KCrash Handler] #6 ref (this=0x85b1140) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121 #7 QByteArray (a=..., this=0x7fff0f6d28d0) at /usr/include/qt4/QtCore/qbytearray.h:440 #8 Akonadi::NotificationMessage::sessionId (this=0x7f31e468a758) at ../../libs/notificationmessage.cpp:125 #9 0x7f31f579bad0 in Akonadi::MonitorPrivate::acceptNotification (this=0x1569ad0, msg=...) at ../../akonadi/monitor_p.cpp:160 #10 0x7f31f579e4f5 in Akonadi::MonitorPrivate::cleanOldNotifications (this=0x1569ad0) at ../../akonadi/monitor_p.cpp:219 #11 0x7f31f579e58b in Akonadi::MonitorPrivate::emitNotification (this=0x1569ad0, msg=...) at ../../akonadi/monitor_p.cpp:292 #12 0x7f31f56fcb31 in Akonadi::ChangeRecorderPrivate::emitNotification (this=0x1569ad0, msg=...) at ../../akonadi/changerecorder_p.h:60 #13 0x7f31f579e7ed in Akonadi::MonitorPrivate::dispatchNotifications (this=0x1569ad0) at ../../akonadi/monitor_p.cpp:447 #14 0x7f31f5312281 in QMetaObject::activate (sender=0x15713b0, m=optimized out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3547 #15 0x7f31f570345d in Akonadi::EntityCacheAkonadi::Collection, Akonadi::CollectionFetchJob, Akonadi::CollectionFetchScope::processResult (this=0x15713b0, job=optimized out) at ../../akonadi/entitycache_p.h:192 #16 0x7f31f5312281 in QMetaObject::activate (sender=0x1534520, m=optimized out, local_signal_index=optimized out, argv=0x7fff0f6d2ec0) at kernel/qobject.cpp:3547 #17 0x7f31f5be5152 in KJob::result (this=optimized out, _t1=0x1534520) at ./kjob.moc:208 #18 0x7f31f5be5190 in KJob::emitResult (this=0x1534520) at ../../kdecore/jobs/kjob.cpp:318 #19 0x7f31f5317446 in QObject::event (this=0x1534520, e=optimized out) at kernel/qobject.cpp:1195 #20 0x7f31f2ef2894 in notify_helper (e=0x156d180, receiver=0x1534520, this=0x13626b0) at kernel/qapplication.cpp:4559 #21 QApplicationPrivate::notify_helper (this=0x13626b0, receiver=0x1534520, e=0x156d180) at kernel/qapplication.cpp:4531 #22 0x7f31f2ef7713 in QApplication::notify (this=0x7fff0f6d3860, receiver=0x1534520, e=0x156d180) at kernel/qapplication.cpp:4420 #23 0x7f31f61c03f6 in KApplication::notify (this=0x7fff0f6d3860, receiver=0x1534520, event=0x156d180) at ../../kdeui/kernel/kapplication.cpp:311 #24 0x7f31f52fde9c in QCoreApplication::notifyInternal (this=0x7fff0f6d3860, receiver=0x1534520, event=0x156d180) at kernel/qcoreapplication.cpp:876 #25 0x7f31f5301c6a in sendEvent (event=0x156d180, receiver=0x1534520) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #26 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x133d060) at kernel/qcoreapplication.cpp:1500 #27 0x7f31f532cf93 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #28 postEventSourceDispatch (s=optimized out) at kernel/qeventdispatcher_glib.cpp:279 #29 0x7f31efdefd53 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7f31efdf00a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7f31efdf0164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 0x7f31f532d3bf in QEventDispatcherGlib::processEvents (this=0x133e4d0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #33 0x7f31f2f9ad5e in QGuiEventDispatcherGlib::processEvents (this=optimized out, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #34 0x7f31f52fcc82 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #35 0x7f31f52fced7 in QEventLoop::exec (this=0x7fff0f6d37e0, flags=...) at kernel/qeventloop.cpp:204 #36 0x7f31f5301f67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148 #37 0x7f31f56d84d6 in Akonadi::AgentBase::init (r=0x1573910) at ../../akonadi/agentbase.cpp:564 #38 0x0040ac66 in
[Bug 283954] Only resources can modify remote revisions
https://bugs.kde.org/show_bug.cgi?id=283954 m00nraker m00nra...@gmx.net changed: What|Removed |Added CC||m00nra...@gmx.net --- Comment #13 from m00nraker m00nra...@gmx.net --- Confirmed, 4.9.1 still buggy :-( -- 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 251704] kmail2 does not allow creation of new top-level folder
https://bugs.kde.org/show_bug.cgi?id=251704 m00nraker m00nra...@gmx.net changed: What|Removed |Added CC||m00nra...@gmx.net --- Comment #16 from m00nraker m00nra...@gmx.net --- Confirmed, bug still not resolved. Still not possible to create top level folder (dovecot imap server). Using KDE 4.9.1... -- 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 292418] Kmail can't create IMAP top level folders
https://bugs.kde.org/show_bug.cgi?id=292418 --- Comment #14 from m00nraker m00nra...@gmx.net --- Bug is still present in KDE 4.9.1. Not resolved. Status has to be changed... -- 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 306997] impossible to open an existing contact by right click in kmail
https://bugs.kde.org/show_bug.cgi?id=306997 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel mon...@kde.org --- Yes I saw if some week ago and debug it. I have a solution but this week I am busy :) Will fix it this WE or next week. And I improve it for 4.10 it will not open kaddressbook but just open an addressbook edit contact. It's better. -- 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 296412] CalDAV resource fails to read Calender entries, but succeeds to write
https://bugs.kde.org/show_bug.cgi?id=296412 --- Comment #5 from Wolfgang Lorenz wl-c...@gmx.de --- Created attachment 74022 -- https://bugs.kde.org/attachment.cgi?id=74022action=edit Debugger output from akonadi console Hello, I'm having the same problem as Henning (reading fails, writing succeeds), but with an Open XChange server and without any error message, other than (from akonadi console): AgentBase(akonadi_davgroupware_resource_1): Unable to retrieve items: oxdav.*** I have attached the full debugging log of one Synchronize All call. Is there a way to get a more verbose output? I know, I could use the Akonadi Open-XChange-module, but I think the CalDAV-module is the more elegant solution for me. (Well, would be, if it was working with Open XChange. ;-) ) Version Info: Server: * Open XChange 6.20.7 Client: * OS: Fedora 16 * KDE: 4.8.5 -- 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 296412] CalDAV resource fails to read Calender entries, but succeeds to write
https://bugs.kde.org/show_bug.cgi?id=296412 Wolfgang Lorenz wl-c...@gmx.de changed: What|Removed |Added CC||wl-c...@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 307025] New: appearance-message window checkboxes not aligned
https://bugs.kde.org/show_bug.cgi?id=307025 Bug ID: 307025 Severity: minor Version: 4.9.1 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: appearance-message window checkboxes not aligned Classification: Unclassified OS: Linux Reporter: t...@klingt.org Hardware: Ubuntu Packages Status: UNCONFIRMED Component: UI Product: kmail2 the checkboxes in the appearance-message window widget are not aligned, the first check box is at a different position than the rest. see attachment 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 307025] appearance-message window checkboxes not aligned
https://bugs.kde.org/show_bug.cgi?id=307025 --- Comment #1 from tim blechmann t...@klingt.org --- Created attachment 74023 -- https://bugs.kde.org/attachment.cgi?id=74023action=edit screenshot -- 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 280841] next/previous message wrap around
https://bugs.kde.org/show_bug.cgi?id=280841 tim blechmann t...@klingt.org changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID |--- --- Comment #5 from tim blechmann t...@klingt.org --- reopening. i'd ask the devs to re-think this behavior, as it is quite an annoyance for people who are used to the behavior that was implemented in kmail1 as well as in all other email clients that i know of. -- 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 307025] appearance-message window checkboxes not aligned
https://bugs.kde.org/show_bug.cgi?id=307025 Laurent Montel mon...@kde.org changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED CC||mon...@kde.org Ever confirmed|0 |1 --- Comment #2 from Laurent Montel mon...@kde.org --- Will fix it soon. -- 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 289524] Any read articles are deleted when switching between feeds
https://bugs.kde.org/show_bug.cgi?id=289524 RunetMember runetmem...@gmail.com changed: What|Removed |Added CC||runetmem...@gmail.com --- Comment #1 from RunetMember runetmem...@gmail.com --- For some reason, ever since I upgraded to KDE 4.7, Akregator (from within Kontact) will delete an article if I mark it as read. The article isn't deleted right away. It only gets removed when I switch to another feed and switch back to the first one. Looks like I get same issue today after upgrading from 4.9.0 to 4.9.1 Never have this bug before. -- 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 289524] Any read articles are deleted when switching between feeds
https://bugs.kde.org/show_bug.cgi?id=289524 --- Comment #2 from RunetMember runetmem...@gmail.com --- Additional info: feed disappear only on Kontact-version of Akregator. Feed that disappear from Kontact, still visible in standalone Akregator application. -- 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 304438] Some feeds do not get updated until I flush Konqueror's cache
https://bugs.kde.org/show_bug.cgi?id=304438 --- Comment #2 from Christoph Lange lan...@web.de --- (In reply to comment #1) Does the issue always appear with the same feeds ? If yes, which feeds ? It appeared with the following two feeds: 1. http://www.heise.de/newsticker/heise-atom.xml (or maybe rather with its RSS variant at http://www.heise.de/newsticker/heise.rdf – sorry, I don't remember exactly, but if you need to know it I can check my old backups) 2. http://www.tagesschau.de/xml/rss2 -- 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 306918] Kontact 4.9.0 crashes when changing kolab storage format from v2 to v3
https://bugs.kde.org/show_bug.cgi?id=306918 Dirk Werner dwer...@curiousbits.de changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Dirk Werner dwer...@curiousbits.de --- I've done this a 2nd time and the conversion from kolab storage format v2 to v3 went through without problems. I set this resolved! -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 287140] editing a new time-planing item crashes Kontact
https://bugs.kde.org/show_bug.cgi?id=287140 Nick Leverton n...@leverton.org changed: What|Removed |Added CC||n...@leverton.org -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 287140] editing a new time-planing item crashes Kontact
https://bugs.kde.org/show_bug.cgi?id=287140 --- Comment #14 from Nick Leverton n...@leverton.org --- Created attachment 74028 -- https://bugs.kde.org/attachment.cgi?id=74028action=edit New crash information added by DrKonqi kontact (4.9.1) on KDE Platform 4.9.1 using Qt 4.8.2 - What I was doing when the application crashed: Creating a new Time Tracker item (I haven't used this feature before so have no tracker items at present). I entered the title and description but when i clicked on edit times, kontact crashed as attached. -- Backtrace (Reduced): #7 timetrackerstorage::rawevents (this=0xb407ba0) at ../../ktimetracker/timetrackerstorage.cpp:323 #8 0xa6fc6a42 in historydialog::listallevents (this=0xb5db488) at ../../ktimetracker/historydialog.cpp:105 #9 0xa6fc8b82 in historydialog::historydialog (this=0xb5db488, parent=0xb5690b8) at ../../ktimetracker/historydialog.cpp:85 #10 0xa6f9d6ab in EditTaskDialog::on_edittimespushbutton_clicked (this=0x9ef9ba8) at ../../ktimetracker/edittaskdialog.cpp:103 #11 0xa6f97e4d in EditTaskDialog::qt_static_metacall (_o=optimized out, _id=optimized out, _a=optimized out, _c=optimized out) at moc_edittaskdialog.cpp:52 -- 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 307039] New: Kmail after e-mailing a note using knotes
https://bugs.kde.org/show_bug.cgi?id=307039 Bug ID: 307039 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail after e-mailing a note using knotes Classification: Unclassified OS: Linux Reporter: kdeb...@pwa.cc Hardware: Debian testing Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (1.13.7) KDE Platform Version: 4.8.4 (4.8.4) Qt Version: 4.8.2 Operating System: Linux 3.2.0-3-amd64 x86_64 Distribution: Debian GNU/Linux testing (wheezy) -- Information about the crash: - What I was doing when the application crashed: * Wrote a note, and customized it using almost all possible options (RTF, widget colors, on which desktop should it appear, etc) * Right click on the title bar, select Mail... * In Kmail window clicked send - crash Although despite actions that were taken I believe it has nothing to do with them, but with custom message tags I created. I might be completely mistaken, but I'm deducting it by looking at classes and their methods' names. For sake of completeness: I removed ALL default message tags (like Friends, Family, etc.) Created bunch of new (6 to be exact) and each is applied using least sophisticated filter/condition editor(?) options - up to two or three conditions per filter. Results: After restarting Kmail, it regenerated index and all tags on e-mails were gone -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [KCrash Handler] #6 KMMessageTagMgr::find (this=0x0, aLabel=...) at ../../kmail/kmmessagetag.cpp:181 #7 0x7f1abdaef330 in KMMessageTagList::compareTags (this=this@entry=0x13e4920, lhs=..., rhs=...) at ../../kmail/kmmessagetag.cpp:325 #8 0x7f1abdaef487 in KMMessageTagList::prioritySort (this=0x13e4920) at ../../kmail/kmmessagetag.cpp:345 #9 0x7f1abd89ad97 in KMMsgInfo::tagList (this=0x1c72120) at ../../kmail/kmmsginfo.cpp:312 #10 0x7f1abd89ae18 in KMMsgInfo::tagString (this=0x1c72120) at ../../kmail/kmmsginfo.cpp:304 #11 0x7f1abd8e49ed in KMMsgBase::asIndexString (this=0x1c72120, length=@0x7fff57a2ed6c: 148) at ../../kmail/kmmsgbase.cpp:1176 #12 0x7f1abda31d6d in KMFolderIndex::writeMessages (this=this@entry=0x1031940, msg=msg@entry=0x0, flush=flush@entry=false, indexStream=indexStream@entry=0x100d890) at ../../kmail/kmfolderindex.cpp:526 #13 0x7f1abda3228f in KMFolderIndex::writeIndex (this=0x1031940, createEmptyIndex=false) at ../../kmail/kmfolderindex.cpp:130 #14 0x7f1abd90dd1d in KMFolderMbox::reallyDoClose (this=0x1031940) at ../../kmail/kmfoldermbox.cpp:289 #15 0x7f1abd864b3c in KMFolder::~KMFolder (this=0x1030af0, __in_chrg=optimized out) at ../../kmail/kmfolder.cpp:167 #16 0x7f1abd864ea9 in KMFolder::~KMFolder (this=0x1030af0, __in_chrg=optimized out) at ../../kmail/kmfolder.cpp:171 #17 0x7f1abd8a75be in qDeleteAllQListKMFolderNode*::iterator (end=..., begin=...) at /usr/include/qt4/QtCore/qalgorithms.h:322 #18 KMFolderDir::~KMFolderDir (this=0xf83cd0, __in_chrg=optimized out) at ../../kmail/kmfolderdir.cpp:91 #19 0x7f1abd8a7619 in KMFolderDir::~KMFolderDir (this=0xf83cd0, __in_chrg=optimized out) at ../../kmail/kmfolderdir.cpp:93 #20 0x7f1abd8a769e in qDeleteAllQListKMFolderNode*::iterator (end=..., begin=...) at /usr/include/qt4/QtCore/qalgorithms.h:322 #21 KMFolderRootDir::~KMFolderRootDir (this=0xf83b38, __in_chrg=optimized out) at ../../kmail/kmfolderdir.cpp:37 #22 0x7f1abd8aa20d in KMFolderMgr::~KMFolderMgr (this=0xf83b20, __in_chrg=optimized out) at ../../kmail/kmfoldermgr.cpp:51 #23 0x7f1abd8aa2a9 in KMFolderMgr::~KMFolderMgr (this=0xf83b20, __in_chrg=optimized out) at ../../kmail/kmfoldermgr.cpp:54 #24 0x7f1abd967dcd in KMKernel::cleanup (this=0x7fff57a2f4b0) at ../../kmail/kmkernel.cpp:1800 #25 0x00402ff5 in main (argc=optimized out, argv=optimized out) at ../../kmail/main.cpp:160 Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 303861] Can't write CalDav items from korganizer
https://bugs.kde.org/show_bug.cgi?id=303861 Myriam Schweingruber myr...@kde.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #10 from Myriam Schweingruber myr...@kde.org --- Confirmed on 4.8.x, can somebody else than the original reporter confirm on 4.9 as well? -- 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 293432] filters with two different entries of the same type are ignored
https://bugs.kde.org/show_bug.cgi?id=293432 --- Comment #3 from Barade barade.bar...@web.de --- This bug is still present (4.9.1). It happens to some mails that they're arent filtered correctly. When I apply manual filter (Ctrl+J) they're moved properly. I have checked Match any of the following and given a List-Id. Besides I've checked the default advanced options Apply this filter to incoming messages, from all accounts, Apply this filter on manual filtering and If this filter matches stop processing here. -- 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 301088] Cannot delete an IMAP folder, although it can create folders
https://bugs.kde.org/show_bug.cgi?id=301088 --- Comment #1 from h...@svw.info --- reproduceable on kmail2 4.9.1 using kubuntu packages -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 306997] impossible to open an existing contact by right click in kmail
https://bugs.kde.org/show_bug.cgi?id=306997 --- Comment #2 from Christian Trippe christiande...@web.de --- Thanks for the quick response. All your work on kmail is really much appreciated! -- 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 307058] New: KMail reacts sluggish but keeps telling my by system notification that it is not broken
https://bugs.kde.org/show_bug.cgi?id=307058 Bug ID: 307058 Severity: normal Version: 4.9.1 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: KMail reacts sluggish but keeps telling my by system notification that it is not broken Classification: Unclassified OS: Linux Reporter: marcel.wies...@gmx.de Hardware: openSUSE RPMs Status: NEW Component: message list Product: kmail2 Fresh conversion from kmail1, large local mail dir. Folders have 20k-50k messages. Reading new mail in a folder, going to the next unread message. Reaction is sluggish, 1) unread mails stay marked as unread in the message list for severeal seconds to minutes, unread counter is correctly decreased in the folder tree view on the left. 2) every now and then showing the mail body fails ( the mail body view shows a busy message that the folder's contents are currently being downloaded). Next attempt at showing a mail may succeed 3) kmail/akonadi/mysql eating CPU and memory in the background 4) Often during that time, a system notification pops up: (translated from German translation back to English): The resource 'KMail folder' is not inoperative. It is now online. Telling me it is not broken via system notification?? I know these are different symptoms but they occur together in one situation so my be caused by the same problem, so a single report by now. Reproducible: Always Steps to Reproduce: 1.Take a larger local mail collection 2.Get new mails 3.Open folder for reading, use + to navigate to next unread mail Actual Results: as above Expected Results: As fast as KMail1! -- 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 307062] New: After upgrading akonadi is running mad
https://bugs.kde.org/show_bug.cgi?id=307062 Bug ID: 307062 Severity: critical Version: 4.9 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: After upgrading akonadi is running mad Classification: Unclassified OS: Linux Reporter: thomas.pa...@gmx.de Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: Akonadi I'm using the kubuntu-backports of KDE 4.9 [https://launchpad.net/~kubuntu-ppa/+archive/backports] for Ubuntu 12.04 (precise) amd64. After the upgrade from 4:4.9.0 to 4:4.9.1 a few days ago, akonadi is running mad after login if not stop within a few seconds be typing akonadictl stop in a (hopefully quick opening konsole). To be very sure, I normally also 'kill -9' all processes listed by 'ps ax | grep akona'. Running mad in this case means that the system eats up all cpu-time, effectively making the system unusable within around 1 minute. Reproducible: Always Steps to Reproduce: 1. Just log in. Actual Results: Akonadi running mad, requiring a reboot after around 1 minute. Expected Results: Akonadi working in the background (or better not at all). For example, why are the akonadi processes not run as a low-priority nice value or in a process group that limit their cpu-usage? -- 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 307064] New: Mail folders synchronized once again every time it is opened
https://bugs.kde.org/show_bug.cgi?id=307064 Bug ID: 307064 Severity: normal Version: 4.9.1 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Mail folders synchronized once again every time it is opened Classification: Unclassified OS: Linux Reporter: marcel.wies...@gmx.de Hardware: Other Status: NEW Component: general Product: kmail2 Fresh conversion from KMail1, local mail folder, folders have 20k-50k images. Opening a folder for reading mails: 1) Message titles are loaded in the message list view, count is visible in the status line in the lower left corner. Takes about 1-2 secs/10k mails on my machine. Slightly slower than KMail1, but acceptable. All messages are visible, grouped/threaded. 2) Now comes a second step, and this is my complaint: A task opens (right lower corner) Folder is synchronized (translated back from German translation). While this task is active, mails cannot be read: The contents of this folder are being fetched (backtranslation again). The mixedmaildir agent eats one CPU core. Sometimes, this synchronization takes only a few seconds, sometimes, it takes 10-20 secs. Note: This happens every time I switch between folders in KMail, again and again. Reproducible: Always Steps to Reproduce: 1. Take a larger local mail setup 2. Have two or three folder 10k mails 3. Switch between them Actual Results: After loading the message titles, a synchronisation blocks reading mails Expected Results: Reading mails is possible immediately -- 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 307064] Mail folders synchronized once again every time it is opened
https://bugs.kde.org/show_bug.cgi?id=307064 --- Comment #1 from Marcel Wiesweg marcel.wies...@gmx.de --- addendum: I have one folder where the synchronization takes particularly long. More than a minute, as long as it took to write the bug report here. This is not the folder with the most 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 307065] New: Kmail crashed during searching IMAP folders
https://bugs.kde.org/show_bug.cgi?id=307065 Bug ID: 307065 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail crashed during searching IMAP folders Classification: Unclassified OS: Linux Reporter: kdeb...@pwa.cc Hardware: Debian testing Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (1.13.7) KDE Platform Version: 4.8.4 (4.8.4) Qt Version: 4.8.2 Operating System: Linux 3.2.0-3-amd64 x86_64 Distribution: Debian GNU/Linux testing (wheezy) -- Information about the crash: - What I was doing when the application crashed: Tried to find an e-mail, and used search function. When asked if I want to download messages to perform search, I agreed. After some time of downloading (a minute or two) Kmail crashed with SEGFAULT. Now, each time I start Kmail and try to open this IMAP account (there are two) it continues search/download and immediately crashes. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [KCrash Handler] #6 0x7f85f55876e6 in KMail::SearchJob::slotSearchDataSingleMessage (this=0x143d0e0, job=optimized out, data=...) at ../../kmail/searchjob.cpp:424 #7 0x7f85f5589197 in KMail::SearchJob::qt_static_metacall (_o=0x143d0e0, _c=optimized out, _id=optimized out, _a=optimized out) at ./searchjob.moc:72 #8 0x7f85f418554f in QMetaObject::activate (sender=0x22f0a60, m=optimized out, local_signal_index=optimized out, argv=0x7fffbb75f130) at kernel/qobject.cpp:3547 #9 0x7f85f5d0dbac in KJob::infoMessage (this=optimized out, _t1=0x22f0a60, _t2=..., _t3=...) at ./kjob.moc:222 #10 0x7f85f09dd697 in KIO::SimpleJobPrivate::_k_slotSlaveInfoMessage (this=optimized out, msg=...) at ../../kio/kio/job.cpp:516 #11 0x7f85f418554f in QMetaObject::activate (sender=0x1267c60, m=optimized out, local_signal_index=optimized out, argv=0x7fffbb75f2a0) at kernel/qobject.cpp:3547 #12 0x7f85f0a7cad5 in KIO::SlaveInterface::infoMessage (this=this@entry=0x1267c60, _t1=...) at ./slaveinterface.moc:301 #13 0x7f85f0a7f233 in KIO::SlaveInterface::dispatch (this=0x1267c60, _cmd=26, rawdata=...) at ../../kio/kio/slaveinterface.cpp:291 #14 0x7f85f0a7beca in KIO::SlaveInterface::dispatch (this=0x1267c60) at ../../kio/kio/slaveinterface.cpp:88 #15 0x7f85f0a7032e in KIO::Slave::gotInput (this=0x1267c60) at ../../kio/kio/slave.cpp:344 #16 0x7f85f418554f in QMetaObject::activate (sender=0x2519990, m=optimized out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3547 #17 0x7f85f09b24f2 in dequeue (this=optimized out) at ../../kio/kio/connection.cpp:82 #18 KIO::ConnectionPrivate::dequeue (this=0x2689310) at ../../kio/kio/connection.cpp:71 #19 0x7f85f4184a2e in QObject::event (this=0x2519990, e=optimized out) at kernel/qobject.cpp:1195 #20 0x7f85f46a470c in QApplicationPrivate::notify_helper (this=this@entry=0xf01530, receiver=receiver@entry=0x2519990, e=e@entry=0x23579a0) at kernel/qapplication.cpp:4556 #21 0x7f85f46a8b8a in QApplication::notify (this=0x7fffbb760310, receiver=0x2519990, e=0x23579a0) at kernel/qapplication.cpp:4417 #22 0x7f85f63048a6 in KApplication::notify (this=0x7fffbb760310, receiver=0x2519990, event=0x23579a0) at ../../kdeui/kernel/kapplication.cpp:311 #23 0x7f85f416fb5e in QCoreApplication::notifyInternal (this=0x7fffbb760310, receiver=receiver@entry=0x2519990, event=event@entry=0x23579a0) at kernel/qcoreapplication.cpp:915 #24 0x7f85f41739e1 in sendEvent (event=0x23579a0, receiver=0x2519990) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #25 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xe15220) at kernel/qcoreapplication.cpp:1539 #26 0x7f85f419e0e3 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #27 postEventSourceDispatch (s=0xe56b70) at kernel/qeventdispatcher_glib.cpp:279 #28 0x7f85eb533205 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7f85eb533538 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7f85eb5335f4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7f85f419e276 in QEventDispatcherGlib::processEvents (this=0xe16b00, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #32 0x7f85f474583e in QGuiEventDispatcherGlib::processEvents (this=optimized out, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #33 0x7f85f416e8af in QEventLoop::processEvents (this=this@entry=0x7fffbb75ffb0, flags=...) at kernel/qeventloop.cpp:149 #34 0x7f85f416eb38 in QEventLoop::exec (this=0x7fffbb75ffb0, flags=...) at kernel/qeventloop.cpp:204 #35 0x7f85f4173cf8 in QCoreApplication::exec () at
[Bug 307066] New: High memory consumption with large local mail setup.
https://bugs.kde.org/show_bug.cgi?id=307066 Bug ID: 307066 Severity: normal Version: 4.9.1 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: High memory consumption with large local mail setup. Classification: Unclassified OS: Linux Reporter: marcel.wies...@gmx.de Hardware: Other Status: NEW Component: general Product: kmail2 Fresh conversion from KMail 1, local mail setup, about 17 mails, in subfolders. Opening KMail, reading new mails in all relevant subfolders. Memory consumption: kontact 715 MB akonadi_mixedmaildir 415 MB akonadiserver 130 MB mysqld 107 MB total: 1,3 GB I'm talking about the 700 MB in kontact and the 400 MB in the resource. Is this cache? Is this linearly growing data structure? Is this lost memory? I am aware that a grouped list view with 5 mails will consume memory. Yet this is a lot. Memory stays constant, when the mail view show 0 messages, no decrease. Reproducible: Always Actual Results: Eats memory Expected Results: Eats less memory -- 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 307065] Kmail crashed during searching IMAP folders
https://bugs.kde.org/show_bug.cgi?id=307065 --- Comment #1 from Zefir kdeb...@pwa.cc --- Created attachment 74036 -- https://bugs.kde.org/attachment.cgi?id=74036action=edit New crash information added by DrKonqi kmail (1.13.7) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.2 - What I was doing when the application crashed: After successfully cancelling all attempts to continue searching and Kmail apparently started working normally, it now crashes every time when I send an e-mail. -- Backtrace (Reduced): #6 0x7f32f238a6e6 in KMail::SearchJob::slotSearchDataSingleMessage (this=0x354e5b0, job=optimized out, data=...) at ../../kmail/searchjob.cpp:424 #7 0x7f32f238c197 in KMail::SearchJob::qt_static_metacall (_o=0x354e5b0, _c=optimized out, _id=optimized out, _a=optimized out) at ./searchjob.moc:72 [...] #9 0x7f32f2b10bac in KJob::infoMessage (this=optimized out, _t1=0x282ae60, _t2=..., _t3=...) at ./kjob.moc:222 #10 0x7f32ed7e0697 in KIO::SimpleJobPrivate::_k_slotSlaveInfoMessage (this=optimized out, msg=...) at ../../kio/kio/job.cpp:516 [...] #12 0x7f32ed87fad5 in KIO::SlaveInterface::infoMessage (this=this@entry=0x347ff00, _t1=...) at ./slaveinterface.moc:301 -- 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 307065] Kmail crashed during searching IMAP folders
https://bugs.kde.org/show_bug.cgi?id=307065 Zefir kdeb...@pwa.cc changed: What|Removed |Added CC||kdeb...@pwa.cc -- 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 289524] Any read articles are deleted when switching between feeds
https://bugs.kde.org/show_bug.cgi?id=289524 --- Comment #3 from Christophe Giboudeaux cgiboude...@gmx.com --- which distribution are you both using ? -- 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 307065] Kmail crashed during searching IMAP folders
https://bugs.kde.org/show_bug.cgi?id=307065 Christoph Feck christ...@maxiom.de changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||christ...@maxiom.de Resolution|--- |UNMAINTAINED --- Comment #2 from Christoph Feck christ...@maxiom.de --- KMail 1.x is no longer maintained. If the issue is reproducible with KMail 2, please add a comment with an updated backtrace. -- 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 289140] Crash when opening an appointment email in the Outbox folder
https://bugs.kde.org/show_bug.cgi?id=289140 --- Comment #14 from Sergio Martins iamser...@gmail.com --- I can't make sense of the valgrind report. Anyway to reproduce this ? Could anyone send me the invitation ? -- 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 280761] crash after entering sieve password during fetch mail
https://bugs.kde.org/show_bug.cgi?id=280761 David Faure fa...@kde.org changed: What|Removed |Added CC||fa...@kde.org --- Comment #9 from David Faure fa...@kde.org --- I think the crash happens when this (the Session instance) gets deleted by some event handling that happens during the QDialog::exec() modal dialog. Then it crashes when accessing a member variable (m_url) of this, which is logical. Solution 1: use a non-modal dialog Solution 2: use Q[Weak]Pointer on this, a common recommendation for modal dialogs nowadays. -- 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 289524] Any read articles are deleted when switching between feeds
https://bugs.kde.org/show_bug.cgi?id=289524 --- Comment #4 from RunetMember runetmem...@gmail.com --- I using Kubuntu 12.04 x86_64. KDE 4.9.1 update installed with Kubuntu Backports PPA. -- 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 307079] New: Kmail error after saving settings
https://bugs.kde.org/show_bug.cgi?id=307079 Bug ID: 307079 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail error after saving settings Classification: Unclassified OS: Linux Reporter: pasc...@tut.by Hardware: Debian testing Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (1.13.7) KDE Platform Version: 4.8.4 (4.8.4) Qt Version: 4.8.2 Operating System: Linux 3.2.0-3-686-pae i686 Distribution: Debian GNU/Linux testing (wheezy) -- Information about the crash: - What I was doing when the application crashed: There have been many changes in the KMail settings: general appearance, managing folders and letters, safety, etc. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/i686/cmov/libthread_db.so.1. [KCrash Handler] #7 0xb6d5a92f in ?? () from /usr/lib/libkmailprivate.so.4 #8 0xb6a6bfa8 in ?? () from /usr/lib/libkmailprivate.so.4 #9 0xb6d32b8d in ?? () from /usr/lib/libkmailprivate.so.4 #10 0xb5d8fce2 in QMetaObject::activate (sender=0xa8f9c08, m=0xb72eb48c, local_signal_index=3, argv=0xbf982bd8) at kernel/qobject.cpp:3547 #11 0xb7134855 in KJob::result (this=this@entry=0xa8f9c08, _t1=_t1@entry=0xa8f9c08) at ./kjob.moc:208 #12 0xb71348a8 in KJob::emitResult (this=0xa8f9c08) at ../../kdecore/jobs/kjob.cpp:318 #13 0xb524c02d in KIO::SimpleJob::slotFinished (this=this@entry=0xa8f9c08) at ../../kio/kio/job.cpp:494 #14 0xb5254d7d in KIO::TransferJob::slotFinished (this=0xa8f9c08) at ../../kio/kio/job.cpp:1081 #15 0xb5253018 in qt_static_metacall (_a=0xbf982e0c, _id=7, _o=0xa8f9c08, _c=optimized out) at ./jobclasses.moc:388 #16 KIO::TransferJob::qt_static_metacall (_o=_o@entry=0xa8f9c08, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=7, _a=0xbf982e0c) at ./jobclasses.moc:375 #17 0xb5d8fce2 in QMetaObject::activate (sender=0xac7c868, m=0xb5426460, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3547 #18 0xb52fe835 in KIO::SlaveInterface::finished (this=this@entry=0xac7c868) at ./slaveinterface.moc:185 #19 0xb5301739 in KIO::SlaveInterface::dispatch (this=0xac7c868, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:172 #20 0xb52fdf0a in KIO::SlaveInterface::dispatch (this=0xac7c868) at ../../kio/kio/slaveinterface.cpp:88 #21 0xb52f09a8 in KIO::Slave::gotInput (this=this@entry=0xac7c868) at ../../kio/kio/slave.cpp:344 #22 0xb52f1004 in KIO::Slave::qt_static_metacall (_o=_o@entry=0xac7c868, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=2, _a=0xbf9830cc) at ./slave.moc:57 #23 0xb5d8fce2 in QMetaObject::activate (sender=0x9b392a0, m=0xb54230f0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3547 #24 0xb521a8d5 in KIO::Connection::readyRead (this=0x9b392a0) at ./connection.moc:106 #25 0xb521af38 in dequeue (this=optimized out) at ../../kio/kio/connection.cpp:82 #26 KIO::ConnectionPrivate::dequeue (this=0xb685e38) at ../../kio/kio/connection.cpp:71 #27 0xb5d8978a in QMetaCallEvent::placeMetaCall (this=0xb739220, object=0x9b392a0) at kernel/qobject.cpp:525 #28 0xb5d8dccb in QObject::event (this=0x9b392a0, e=0xb739220) at kernel/qobject.cpp:1195 #29 0xb602b47c in QApplicationPrivate::notify_helper (this=0x94f0978, receiver=0x9b392a0, e=0xb739220) at kernel/qapplication.cpp:4556 #30 0xb602fe7f in QApplication::notify (this=0xb739220, receiver=0x9b392a0, e=0xb739220) at kernel/qapplication.cpp:3938 #31 0xb74fa581 in KApplication::notify (this=0xbf9839f0, receiver=0x9b392a0, event=0xb739220) at ../../kdeui/kernel/kapplication.cpp:311 #32 0xb5d7755e in QCoreApplication::notifyInternal (this=0xbf9839f0, receiver=0x9b392a0, event=0xb739220) at kernel/qcoreapplication.cpp:915 #33 0xb5d7b76d in sendEvent (event=optimized out, receiver=optimized out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #34 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x948f150) at kernel/qcoreapplication.cpp:1539 #35 0xb5d7b9ec in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1432 #36 0xb5da96c4 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #37 postEventSourceDispatch (s=0x94f2d40) at kernel/qeventdispatcher_glib.cpp:279 #38 0xb3af9633 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #39 0xb3af99d0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #40 0xb3af9ab1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #41 0xb5da9841 in QEventDispatcherGlib::processEvents (this=0x948fec0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #42 0xb60de1fa in QGuiEventDispatcherGlib::processEvents (this=0x948fec0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #43 0xb5d7602c in QEventLoop::processEvents (this=this@entry=0xbf9838b8,
