[kontact] [Bug 316270] CRASH after creation and deletion of address book
https://bugs.kde.org/show_bug.cgi?id=316270 Rolf Eike Beer k...@opensource.sf-tec.de changed: What|Removed |Added CC||k...@opensource.sf-tec.de Severity|normal |crash -- 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
[Akonadi] [Bug 283334] After suspend to ram KMail does not work, akonadi says MySQL server has gone away.
https://bugs.kde.org/show_bug.cgi?id=283334 --- Comment #27 from Sven Eden sven.e...@gmx.de --- The live build of the akonadi server did improve the situation, my IMAP account didn't go offline, yet. However, every time I send an e-mail I get the following message: Account name: Save failed, server replied: A001889 BAD Error in IMAP command UID: Invalid arguments. However, the e-mails get sent and are stored in the sent folder like they should. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 283334] After suspend to ram KMail does not work, akonadi says MySQL server has gone away.
https://bugs.kde.org/show_bug.cgi?id=283334 Daniel Vrátil dvra...@redhat.com changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||1.10.2 Resolution|--- |FIXED --- Comment #28 from Daniel Vrátil dvra...@redhat.com --- Ok, so marking this as fixed, feel free to reopen this bug if you run into the problem again. Regarding the IMAP error, could you please open a separate bug report? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 277839] akonadiserver.socket path to long
https://bugs.kde.org/show_bug.cgi?id=277839 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/akon ||adi/6f6c691451726544487970e ||f325c71c4ae4a02fa --- Comment #11 from Christian Mollekopf chrig...@fastmail.fm --- Git commit 6f6c691451726544487970ef325c71c4ae4a02fa by Christian Mollekopf. Committed on 19/08/2013 at 09:31. Pushed by cmollekopf into branch '1.10'. Use the target of the symlink instead as socket directory. Socket paths must be shorter than 108 characters, and the symlink is quickly beyond that. By using the actual directory this can be avoided. This results in the socket used to start the mysql database, as well as the socket in akonadiconnectionrc being set to the /tmp/ path. REVIEW: 112152 M +2-2server/src/utils.cpp http://commits.kde.org/akonadi/6f6c691451726544487970ef325c71c4ae4a02fa -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 323672] Feeder crash on killing FindUnindexedItems Job
https://bugs.kde.org/show_bug.cgi?id=323672 Vishesh Handa m...@vhanda.in changed: What|Removed |Added Summary|Akonadi/Nepomuk error |Feeder crash on killing ||FindUnindexedItems Job -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 323675] Akonadi IMAP resource does not load translations from libkimap.mo
https://bugs.kde.org/show_bug.cgi?id=323675 Burkhard Lueck lu...@hube-lueck.de changed: What|Removed |Added CC||lu...@hube-lueck.de -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 323707] New: Mail dispatcher will ask twice for going online when sending an email after an offline period
https://bugs.kde.org/show_bug.cgi?id=323707 Bug ID: 323707 Summary: Mail dispatcher will ask twice for going online when sending an email after an offline period Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: f.faine...@gmail.com When the mail dispatcher has been offline, as a result of a an authentication failure or for some other reason, the next time an email is to be sent, it will ask twice for going back online. The first time is normal because the mail dispatcher is offline, but even after pressing Yes there is a second popup to ask if the mail dispatcher should be put online. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 323675] Akonadi IMAP resource does not load translations from libkimap.mo
https://bugs.kde.org/show_bug.cgi?id=323675 Daniel Vrátil dvra...@redhat.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||4.11.1 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||imlibs/5c1e2c4a5fdfd560d35a ||3a34818aa8c5bebf4c7a --- Comment #1 from Daniel Vrátil dvra...@redhat.com --- Git commit 5c1e2c4a5fdfd560d35a3a34818aa8c5bebf4c7a by Dan Vrátil. Committed on 19/08/2013 at 11:51. Pushed by dvratil into branch 'KDE/4.11'. Load KIMAP translations catalog REVIEW: 112153 FIXED-IN: 4.11.1 M +1-0kimap/CMakeLists.txt A +23 -0kimap/global.cpp [License: LGPL (v2+)] http://commits.kde.org/kdepimlibs/5c1e2c4a5fdfd560d35a3a34818aa8c5bebf4c7a -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 323709] Using KDE 4.10.2 Kmail 4.10.2, the HTML settings are erroneously re-enabled, e.g. after unrelated changes
https://bugs.kde.org/show_bug.cgi?id=323709 Jekyll Wu adap...@gmail.com changed: What|Removed |Added Component|general |general Version|4.10.4 |unspecified Assignee|unassigned-b...@kde.org |kdepim-bugs@kde.org Product|kde |kmail2 -- 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
[kaddressbook] [Bug 323717] New: Creating a new category for a contact creates a duplicate entry when re-editing contact categories
https://bugs.kde.org/show_bug.cgi?id=323717 Bug ID: 323717 Summary: Creating a new category for a contact creates a duplicate entry when re-editing contact categories Classification: Unclassified Product: kaddressbook Version: 4.11 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: is...@freemail.gr CC: to...@kde.org When creating a new contact and a new category is created and assigned to this contact, everything works as expected when the data entry is complete (OK pressed in the Add tags window and the New Contact window). However, when editing the contact, upon reentry in the categories list (pressing the ... button), the assigned tag is recreated and assigned two times. If Cancel is pressed, the contact is not changed as expected. If OK is pressed in the Add tags window with both identical tags selected, the tags are duplicated in the contact entry as well (and in the vcf file). If Nepomuk Cleaner is executed before or after the editing of the contact, the duplicate entry is removed and is not recreated upon further re-edits of tags. The same bug occurs when adding more than one tags. Reproducible: Always Steps to Reproduce: 1. Create a new contact 2. Add a new Category (tag) for the contact 3. Confirm the entry by pressing OK 4. Re-edit the contact and press the ... button to update the categories Actual Results: The assigend category is duplicated and both tag instances are selected If OK is pressed and the contact is saved, the tags will remain duplicated for the contact. Expected Results: The assigned category appears only once. This bug did not occur in 4.10.5 and possibly previous 4.10.x versions. -- 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
[kaddressbook] [Bug 323717] Creating a new category for a contact creates a duplicate entry when re-editing contact categories
https://bugs.kde.org/show_bug.cgi?id=323717 --- Comment #1 from Ioannis Ramfos is...@freemail.gr --- Created attachment 81784 -- https://bugs.kde.org/attachment.cgi?id=81784action=edit Tag list when re-editing categories, with duplicate entries shown -- 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
[kaddressbook] [Bug 323717] Creating a new category for a contact creates a duplicate entry when re-editing contact categories
https://bugs.kde.org/show_bug.cgi?id=323717 --- Comment #2 from Ioannis Ramfos is...@freemail.gr --- Created attachment 81785 -- https://bugs.kde.org/attachment.cgi?id=81785action=edit Contact categories when accepting tag list with duplicate entries -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 322958] KMail: duplicate special folder causes endless loop Emitting defaultFoldersChanged
https://bugs.kde.org/show_bug.cgi?id=322958 Frédéric COIFFIER frederic.coiff...@free.fr changed: What|Removed |Added CC||frederic.coiff...@free.fr -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 283334] After suspend to ram KMail does not work, akonadi says MySQL server has gone away.
https://bugs.kde.org/show_bug.cgi?id=283334 --- Comment #29 from Sven Eden sven.e...@gmx.de --- (In reply to comment #28) Ok, so marking this as fixed, feel free to reopen this bug if you run into the problem again. That was a bit fast. The Account died again. The main difference between the stable and the live build is, that the live build makes more noise. Instead of just one account name : Killed message I got several messages about items not being fetchable in offline mode surrounding this killed message. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 283334] After suspend to ram KMail does not work, akonadi says MySQL server has gone away.
https://bugs.kde.org/show_bug.cgi?id=283334 --- Comment #30 from Sven Eden sven.e...@gmx.de --- Sorry for the double post, I was too fast when I realized what was going on. damn browser history, really. I had written that Bug 316107 is about exactly my issues, which are still present. and wanted to 'move' there as I never had any issue with mysql (which is what _this_ bug is about). So while answering I was completely on the wrong track thinking to be in the *other* bug report. Sorry about the noise. However, IMAP is still unusable, even with live built akonadi server. But it has nothing to do with mysql. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 316107] big regression: kmail IMAP connection and message display problems
https://bugs.kde.org/show_bug.cgi?id=316107 --- Comment #9 from Sven Eden sven.e...@gmx.de --- I have tried with akonadi compiled from git://anongit.kde.org/akonadi , but IMAP stays switching to persistent offline mode after a while. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 323722] New: kontact crash when going to open a doc attached to an email
https://bugs.kde.org/show_bug.cgi?id=323722 Bug ID: 323722 Summary: kontact crash when going to open a doc attached to an email Classification: Unclassified Product: kontact Version: 4.11 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: tankta...@gmail.com Application: kontact (4.11) KDE Platform Version: 4.11.00 (Compiled from sources) Qt Version: 4.8.4 Operating System: Linux 3.10.7-gentoo x86_64 Distribution: NAME=Gentoo -- Information about the crash: - What I was doing when the application crashed: I have an email with an attached .doc file, I went to open it, clicking on the attachment then on Open with 'LibreOffice Writer'. At this point, it crashed. Saving via Save As... works fine. Also, Open With... and then choosing lowriter works fine. This also worked fine with KDE 4.10, from which I upgraded only yesterday. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f5cdf26f7c0 (LWP 4813))] Thread 3 (Thread 0x7f5cc4a15700 (LWP 4814)): #0 0x7f5cd693259c in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f5cd9c6c654 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7f5cd692dd96 in start_thread () from /lib64/libpthread.so.0 #3 0x7f5cdc49b46d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f5cc4114700 (LWP 4815)): #0 0x7f5cdc4926a3 in poll () from /lib64/libc.so.6 #1 0x7f5cd58f0e95 in g_main_context_iterate.isra.23.part.24 () from /usr/lib64/libglib-2.0.so.0 #2 0x7f5cd58f1005 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f5cdda6e906 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #4 0x7f5cdda34c72 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #5 0x7f5cdda34eb7 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #6 0x7f5cdd911708 in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4 #7 0x7f5cdd914aee in QThreadPrivate::start(void*) () from /usr/lib64/qt4/libQtCore.so.4 #8 0x7f5cd692dd96 in start_thread () from /lib64/libpthread.so.0 #9 0x7f5cdc49b46d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f5cdf26f7c0 (LWP 4813)): [KCrash Handler] #6 0x7f5cdc3e5aa5 in raise () from /lib64/libc.so.6 #7 0x7f5cdc3e6da5 in abort () from /lib64/libc.so.6 #8 0x7f5cdd909a14 in qt_message_output(QtMsgType, char const*) () from /usr/lib64/qt4/libQtCore.so.4 #9 0x7f5cdd909b9f in qt_message(QtMsgType, char const*, __va_list_tag*) () from /usr/lib64/qt4/libQtCore.so.4 #10 0x7f5cdd909d44 in qFatal(char const*, ...) () from /usr/lib64/qt4/libQtCore.so.4 #11 0x7f5cdbda240d in supportedProtocols(KService const) () from /usr/lib64/libkio.so.5 #12 0x7f5cdbda5688 in KRun::run(KService const, KUrl::List const, QWidget*, bool, QString const, QByteArray const) () from /usr/lib64/libkio.so.5 #13 0x7f5c79f75000 in MessageViewer::ViewerPrivate::attachmentOpenWith(KMime::Content*, KSharedPtrKService) () from /usr/lib64/libmessageviewer.so.4 #14 0x7f5c79f7b7ed in MessageViewer::ViewerPrivate::openAttachment(KMime::Content*, QString const) () from /usr/lib64/libmessageviewer.so.4 #15 0x7f5c79f5b946 in (anonymous namespace)::AttachmentURLHandler::handleClick(KUrl const, MessageViewer::ViewerPrivate*) const () from /usr/lib64/libmessageviewer.so.4 #16 0x7f5c79f5e558 in MessageViewer::URLHandlerManager::handleClick(KUrl const, MessageViewer::ViewerPrivate*) const () from /usr/lib64/libmessageviewer.so.4 #17 0x7f5c79f6ac75 in MessageViewer::ViewerPrivate::slotUrlOpen(QUrl const) () from /usr/lib64/libmessageviewer.so.4 #18 0x7f5c79f85d10 in MessageViewer::ViewerPrivate::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib64/libmessageviewer.so.4 #19 0x7f5cdda5533e in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #20 0x7f5cdcc3ae12 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #21 0x7f5cdcc40e5b in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #22 0x7f5cde598ef6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #23 0x7f5cdda3711c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #24 0x7f5cdda3ac43 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/qt4/libQtCore.so.4 #25 0x7f5cdda6e433
[kmail2] [Bug 323724] New: Getting spammed with wrong notifications
https://bugs.kde.org/show_bug.cgi?id=323724 Bug ID: 323724 Summary: Getting spammed with wrong notifications Classification: Unclassified Product: kmail2 Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: afies...@kde.org i'm checking out an new account in akonadi, I'm getting spammed with notifications kinda 350 new emails in kde-plasma-devel for emails that are not new (years old) and that are marked as read. Imho the notifier should be changed so it only notifies moderated new emails and unread. 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
[kontact] [Bug 323722] kontact crash when going to open a doc attached to an email
https://bugs.kde.org/show_bug.cgi?id=323722 Jekyll Wu adap...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Jekyll Wu adap...@gmail.com --- #11 0x7f5cdbda240d in supportedProtocols(KService const) () from /usr/lib64/libkio.so.5 #12 0x7f5cdbda5688 in KRun::run(KService const, KUrl::List const, QWidget*, bool, QString const, QByteArray const) () from /usr/lib64/libkio.so.5 Since you can reproduce the crash every time, please rebuild related packages[1] with debug symbols and provide a better backtrace. [1] http://www.gentoo.org/proj/en/qa/backtraces.xml -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 323722] kontact crash when going to open a doc attached to an email
https://bugs.kde.org/show_bug.cgi?id=323722 --- Comment #2 from Darin McBride tankta...@gmail.com --- Created attachment 81789 -- https://bugs.kde.org/attachment.cgi?id=81789action=edit New crash information added by DrKonqi kontact (4.11) on KDE Platform 4.11.00 using Qt 4.8.4 Same as earlier - but this time I've recompiled a bunch of stuff with the -ggdb flag as requested. Thanks! -- Backtrace (Reduced): #11 0x7f0279cb640d in supportedProtocols (_service=...) at /var/tmp/portage/kde-base/kdelibs-4.11.0/work/kdelibs-4.11.0/kio/kio/krun.cpp:377 #12 0x7f0279cb9688 in resolveURLs (_service=..., _urls=...) at /var/tmp/portage/kde-base/kdelibs-4.11.0/work/kdelibs-4.11.0/kio/kio/krun.cpp:742 #13 KRun::run (_service=..., _urls=..., window=optimized out, tempFiles=optimized out, suggestedFileName=..., asn=...) at /var/tmp/portage/kde-base/kdelibs-4.11.0/work/kdelibs-4.11.0/kio/kio/krun.cpp:1007 #14 0x7f0217e33000 in MessageViewer::ViewerPrivate::attachmentOpenWith (this=0x1d0bba0, node=optimized out, offer=...) at /var/tmp/portage/kde-base/kdepim-common-libs-4.11.0/work/kdepim-common-libs-4.11.0/messageviewer/viewer/viewer_p.cpp:761 #15 0x7f0217e397ed in MessageViewer::ViewerPrivate::openAttachment (this=0x1d0bba0, node=0x26bc680, name=...) at /var/tmp/portage/kde-base/kdepim-common-libs-4.11.0/work/kdepim-common-libs-4.11.0/messageviewer/viewer/viewer_p.cpp:392 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 323722] kontact crash when going to open a doc attached to an email
https://bugs.kde.org/show_bug.cgi?id=323722 Darin McBride tankta...@gmail.com changed: What|Removed |Added CC||tankta...@gmail.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 323736] New: Segfault when deleting lots of notes
https://bugs.kde.org/show_bug.cgi?id=323736 Bug ID: 323736 Summary: Segfault when deleting lots of notes Classification: Unclassified Product: kontact Version: unspecified Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: notes Assignee: kdepim-bugs@kde.org Reporter: b...@humanleg.org.uk Application: kontact (4.4.11) KDE Platform Version: 4.8.4 (4.8.4) Qt Version: 4.8.2 Operating System: Linux 3.2.0-4-amd64 x86_64 Distribution: Debian GNU/Linux 7.1 (wheezy) -- Information about the crash: - What I was doing when the application crashed: Deleting a note (actually lots of notes at once) - Custom settings of the application: This was a set of notes from a just-upgraded kde3 installation which had had the side effect of duplicating each of my notes about 100 times. I was trying to clean out some of the redundant ones. Reproducible: Always Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [KCrash Handler] #6 KNotesResourceManager::deleteNote (this=0x280f6e0, journal=0x2c61340) at ../../../../knotes/resourcemanager.cpp:109 #7 0x7effba64d1ac in KNotesPart::killSelectedNotes (this=0x27c3a90) at ../../../../kontact/plugins/knotes/knotes_part.cpp:354 #8 0x7effba64d52d in qt_static_metacall (_a=optimized out, _id=optimized out, _o=optimized out, _c=optimized out) at ./knotes_part.moc:89 #9 KNotesPart::qt_static_metacall (_o=optimized out, _c=optimized out, _id=optimized out, _a=0x7fff9e853bc0) at ./knotes_part.moc:67 #10 0x7effd60fa54f in QMetaObject::activate (sender=0x29b9e60, m=optimized out, local_signal_index=optimized out, argv=0x7fff9e853bc0) at kernel/qobject.cpp:3547 #11 0x7effd5487502 in QAction::triggered (this=this@entry=0x29b9e60, _t1=false) at .moc/release-shared/moc_qaction.cpp:277 #12 0x7effd54876f0 in QAction::activate (this=0x29b9e60, event=optimized out) at kernel/qaction.cpp:1257 #13 0x7effd58c1413 in QMenuPrivate::activateCausedStack (this=this@entry=0x18323b0, causedStack=..., action=action@entry=0x29b9e60, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1028 #14 0x7effd58c7729 in QMenuPrivate::activateAction (this=0x18323b0, action=0x29b9e60, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1120 #15 0x7effd6c32340 in KMenu::mouseReleaseEvent (this=0x4f9bac0, e=0x7fff9e854760) at ../../kdeui/widgets/kmenu.cpp:464 #16 0x7effd54dce10 in QWidget::event (this=0x4f9bac0, event=0x7fff9e854760) at kernel/qwidget.cpp:8371 #17 0x7effd58c89db in QMenu::event (this=0x4f9bac0, e=0x7fff9e854760) at widgets/qmenu.cpp:2469 #18 0x7effd548d70c in QApplicationPrivate::notify_helper (this=this@entry=0x16434c0, receiver=receiver@entry=0x4f9bac0, e=e@entry=0x7fff9e854760) at kernel/qapplication.cpp:4556 #19 0x7effd54923eb in QApplication::notify (this=optimized out, receiver=0x4f9bac0, e=0x7fff9e854760) at kernel/qapplication.cpp:4099 #20 0x7effd6b79886 in KApplication::notify (this=0x7fff9e855430, receiver=0x4f9bac0, event=0x7fff9e854760) at ../../kdeui/kernel/kapplication.cpp:311 #21 0x7effd60e4b5e in QCoreApplication::notifyInternal (this=0x7fff9e855430, receiver=0x4f9bac0, event=0x7fff9e854760) at kernel/qcoreapplication.cpp:915 #22 0x7effd548e54b in sendEvent (event=optimized out, receiver=optimized out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #23 QApplicationPrivate::sendMouseEvent (receiver=0x4f9bac0, event=0x7fff9e854760, alienWidget=0x0, nativeWidget=0x4f9bac0, buttonDown=0x7effd5f632a8, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3167 #24 0x7effd5508e8c in QETWidget::translateMouseEvent (this=this@entry=0x4f9bac0, event=event@entry=0x7fff9e854ed0) at kernel/qapplication_x11.cpp:4457 #25 0x7effd5507d51 in QApplication::x11ProcessEvent (this=0x7fff9e855430, event=0x7fff9e854ed0) at kernel/qapplication_x11.cpp:3646 #26 0x7effd552ebc2 in x11EventSourceDispatch (s=0x164a670, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #27 0x7effcdd2a355 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7effcdd2a688 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7effcdd2a744 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7effd6113276 in QEventDispatcherGlib::processEvents (this=0x1609b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #31 0x7effd552e83e in QGuiEventDispatcherGlib::processEvents (this=optimized out, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #32 0x7effd60e38af in QEventLoop::processEvents (this=this@entry=0x7fff9e8552a0, flags=...) at kernel/qeventloop.cpp:149 #33 0x7effd60e3b38 in QEventLoop::exec (this=0x7fff9e8552a0,
[kmail2] [Bug 323739] New: MDN's should be threaded with the original mail.
https://bugs.kde.org/show_bug.cgi?id=323739 Bug ID: 323739 Summary: MDN's should be threaded with the original mail. Classification: Unclassified Product: kmail2 Version: unspecified Platform: unspecified OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: MDN Assignee: kdepim-bugs@kde.org Reporter: res...@patuck.net MDN's as of now go to inbox by default. This is not ideal as they are not close to the emails themselves which are in the sent items folder making it harder to correlate emails with MDN's. This makes it hard to keep track of who has opened the email and who has not when sending more than one email with a similar subject. A way around this is to group MDN's with the email in the sent items(like a thread) and have an icon like the icon in the status to display the status of the email(just like we have one to notify us if a message is read or has an attachment). The actual MDN should be viewable from the email so the workflow for viewing a MDN would be: - Open sent email - Click view MDNs - Window opens with a list of MDNs for that email. However the status of the email can be seen by a 'read by recipient' or 'delivered and unread' or 'deleted before opening' icon in the status of the message. 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
[kmail2] [Bug 323739] MDN's should be threaded with the original mail.
https://bugs.kde.org/show_bug.cgi?id=323739 Reshad Patuck res...@patuck.net changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 323739] MDN's should be threaded with the original mail.
https://bugs.kde.org/show_bug.cgi?id=323739 Reshad Patuck res...@patuck.net changed: What|Removed |Added CC||res...@patuck.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
[kmail2] [Bug 323740] New: [Regression] Kontact/KMail starts eating one CPU when selecting a mail
https://bugs.kde.org/show_bug.cgi?id=323740 Bug ID: 323740 Summary: [Regression] Kontact/KMail starts eating one CPU when selecting a mail Classification: Unclassified Product: kmail2 Version: 4.11 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: k...@opensource.sf-tec.de I just upgraded my machine from SC 4.10.5 to 4.11. I'm using KMail-part in Kontact with an (online) IMAP account. After startup, once the first mail is selected, Kontact starts blocking one CPU (~20% on my Quadcore machine), akonadiserver usually uses the rest so both sum up to ~25% load. When in this state I can select some other mail but only get a message please wait while fetching contents of this folder. I also can't send any mail during this. Kontact isn't entirely locked up, e.g. I can navigate through the menu and the like. So I guess it is in some sort of loop talking to akonadi and getting flooded with replies so the event loop is always busy. Since I can easily reproduce this I can get you any sort of log/strace, but please tell me what to look for. 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
[kmail2] [Bug 316153] can't move or delete messages in imap inbox
https://bugs.kde.org/show_bug.cgi?id=316153 Jan Sommer summers...@web.de changed: What|Removed |Added CC||summers...@web.de --- Comment #4 from Jan Sommer summers...@web.de --- I have kind of the same problem in KMail with KDE SC 4.11 running with Kubuntu 12.04. My inbox has subfolders for mailinglists, I can delete/move to trash mails from the subfolder, but not from the toplevel inbox folder. Is that the same bug as described here or should I open a new bugreport? See also this thread: http://forum.kde.org/viewtopic.php?f=215t=117097p=290368#p290368 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 316153] can't move or delete messages in imap inbox
https://bugs.kde.org/show_bug.cgi?id=316153 Sébastien Escudier sebastien-de...@celeos.eu changed: What|Removed |Added CC||sebastien-de...@celeos.eu --- Comment #5 from Sébastien Escudier sebastien-de...@celeos.eu --- I also have this bug. I cannont delete or move messages from a top-level folder from my IMAP account. All the others sub-folders work fine. My trash folder is well configured. I am using kmail and kde version 4.10.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
[kleopatra] [Bug 215032] Smart Card - pkcs#11 Support
https://bugs.kde.org/show_bug.cgi?id=215032 Oyvind Hanssen ohans...@acm.org changed: What|Removed |Added CC||ohans...@acm.org --- Comment #2 from Oyvind Hanssen ohans...@acm.org --- I strongly support this request. The need for secure email, etc via a smartcard based PKI should be obvious. -- 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
[kmail2] [Bug 323740] [Regression] Kontact/KMail starts eating one CPU when selecting a mail
https://bugs.kde.org/show_bug.cgi?id=323740 Skander Morgenthaler sm...@gmx.de changed: What|Removed |Added CC||sm...@gmx.de --- Comment #1 from Skander Morgenthaler sm...@gmx.de --- Same problem here, using gentoo x86_64, kde 4.11, qt 4.8.5, gcc-4.7.3 and maildir ressources (fetching mails via pop3). I can read about one or two mails with enough patience (5-15 Minutes of waiting), after that kmail needs forever (1h) to display the next message. If I can help by providing more information, please let me know. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 323740] [Regression] Kontact/KMail starts eating one CPU when selecting a mail
https://bugs.kde.org/show_bug.cgi?id=323740 Rolf Eike Beer k...@opensource.sf-tec.de changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Rolf Eike Beer k...@opensource.sf-tec.de --- One more thing that I observed: if I quit kontact it will not go away, but hang around. It then uses less CPU time, but akonadi then uses more (numbers are something like 4% kontact 21% akonadi), so I think there is still the same communication going on in the background. When I then send send a term signal to kontact it really quits and akonadi immediately calms down. -- 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
[libkgapi] [Bug 313378] Etc/GMT timezone format not supported
https://bugs.kde.org/show_bug.cgi?id=313378 --- Comment #6 from Thiago Jung Bauermann thiago.bauerm...@gmail.com --- Hello, Sorry for the big delay. I am now using KDE 4.11 with KDE PIM 4.11 and libkgapi 2.0.1. The events I pasted above didn't show up after the upgrade, but after I removed and then re-added the Google Calendar and Tasks resource they did. This bug is solved, thanks! -- 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
[kontact] [Bug 323736] Segfault when deleting lots of notes
https://bugs.kde.org/show_bug.cgi?id=323736 Jekyll Wu adap...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED --- Comment #1 from Jekyll Wu adap...@gmail.com --- Application: kontact (4.4.11) Sorry, but that KDEPIM version is too old and no longer supported/maintained. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 323748] plasma crash on boot
https://bugs.kde.org/show_bug.cgi?id=323748 Jekyll Wu adap...@gmail.com changed: What|Removed |Added Component|general |general Version|4.11.0 |4.11 Assignee|plasma-b...@kde.org |kdepim-bugs@kde.org Product|plasma |Akonadi --- Comment #2 from Jekyll Wu adap...@gmail.com --- (In reply to comment #1) I have the same problem. It crashes on start, but I can launch krunner (alt + f2) and launch plasma-desktop. Gonzalo , you crash is a different one, totally unrelated with this one. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kdepim] [Bug 323753] New: Personal Settings in account wizards untranslatable
https://bugs.kde.org/show_bug.cgi?id=323753 Bug ID: 323753 Summary: Personal Settings in account wizards untranslatable Classification: Unclassified Product: kdepim Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wizards Assignee: kdepim-bugs@kde.org Reporter: lu...@hube-lueck.de in kdepim-runtime several script files like tine20wizard.es, imapwizard.es, kolabwizard.es, maildirwizard.es, mailboxwizard.es, pop3wizard.js have the untranslatable string Personal Settings no message extraction -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 323755] New: kmail2 crashed when opening sieve scripts window
https://bugs.kde.org/show_bug.cgi?id=323755 Bug ID: 323755 Summary: kmail2 crashed when opening sieve scripts window Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: tho...@fjellstrom.ca Application: kmail (4.10.5) KDE Platform Version: 4.10.5 Qt Version: 4.8.5 Operating System: Linux 3.9-1-amd64 x86_64 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: - What I was doing when the application crashed: I tried opening the window to manage sieve scripts. It crashed. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f23de76d780 (LWP 21324))] Thread 4 (Thread 0x7f23bc650700 (LWP 21327)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f23d0002ae2 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f23d0002b19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f23d939de0e in start_thread (arg=0x7f23bc650700) at pthread_create.c:311 #4 0x7f23dbac993d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 3 (Thread 0x7f23bbd4f700 (LWP 21328)): #0 0x7f23d3a88284 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f23d3a482e0 in g_main_context_acquire () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f23d3a49055 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f23d3a4929c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f23dc44dd06 in QEventDispatcherGlib::processEvents (this=0x7f23b40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #5 0x7f23dc41f7bf in QEventLoop::processEvents (this=this@entry=0x7f23bbd4edf0, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f23dc41fab5 in QEventLoop::exec (this=this@entry=0x7f23bbd4edf0, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f23dc31e8cf in QThread::exec (this=optimized out) at thread/qthread.cpp:536 #8 0x7f23dc320f6f in QThreadPrivate::start (arg=0x147d7b0) at thread/qthread_unix.cpp:338 #9 0x7f23d939de0e in start_thread (arg=0x7f23bbd4f700) at pthread_create.c:311 #10 0x7f23dbac993d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 2 (Thread 0x7f2371265700 (LWP 12438)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x7f23dc321424 in wait (time=3, this=0xa684020) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=optimized out, mutex=mutex@entry=0x3d9ac38, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7f23dc3148a5 in QThreadPoolThread::run (this=0x4b8e3e0) at concurrent/qthreadpool.cpp:141 #4 0x7f23dc320f6f in QThreadPrivate::start (arg=0x4b8e3e0) at thread/qthread_unix.cpp:338 #5 0x7f23d939de0e in start_thread (arg=0x7f2371265700) at pthread_create.c:311 #6 0x7f23dbac993d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 1 (Thread 0x7f23de76d780 (LWP 21324)): [KCrash Handler] #6 0x0030 in ?? () #7 0x7f23dc42b194 in QMetaObject::invokeMethod (obj=obj@entry=0x1f5b1310, member=member@entry=0x7f23ce8bf837 executeNextJob, type=type@entry=Qt::QueuedConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1166 #8 0x7f23ce8bae93 in invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., type=Qt::QueuedConnection, member=0x7f23ce8bf837 executeNextJob, obj=0x1f5b1310) at /usr/include/qt4/QtCore/qobjectdefs.h:418 #9 KManageSieve::Session::processResponse (this=this@entry=0x1f5b1310, response=..., data=...) at ../../../libksieve/kmanagesieve/session.cpp:259 #10 0x7f23ce8bbf72 in KManageSieve::Session::dataReceived (this=0x1f5b1310) at ../../../libksieve/kmanagesieve/session.cpp:138 #11 0x7f23dc434cf8 in QMetaObject::activate (sender=0x1c319770, m=optimized out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3547 #12 0x7f23ddc31222 in reemitReadyRead (this=optimized out, this=optimized out) at ../../kdecore/network/ktcpsocket.cpp:372 #13 KTcpSocket::qt_static_metacall (_o=0x1f5b1310, _id=16, _a=0x626f4a7478654e65, _c=optimized out) at ./ktcpsocket.moc:91 #14 0x7f23dc434cf8 in QMetaObject::activate (sender=sender@entry=0x1c3196b0, m=m@entry=0x7f23dc783540 QIODevice::staticMetaObject, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3547 #15 0x7f23dc47dbd0 in
