[Akonadi] [Bug 340840] Show Facebook messages in KMail — make Facebook messages collection a mail collection
https://bugs.kde.org/show_bug.cgi?id=340840 Arthur Țițeică arthur.tite...@gmail.com changed: What|Removed |Added CC||arthur.tite...@gmail.com -- 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
[kleopatra] [Bug 340852] New: clipboard encryption fails
https://bugs.kde.org/show_bug.cgi?id=340852 Bug ID: 340852 Summary: clipboard encryption fails Product: kleopatra Version: 2.2.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: off...@vhaigis.com CC: m...@kde.org when using kleopatra encrypt clipboard function nothing happens. i can add an recipients key but after that nothing happens. clipboards content remains unencryted Reproducible: Always Steps to Reproduce: 1. copy text to clipboard 2. tell kleopatra to encrypt 3. add recipient Actual Results: nothing Expected Results: encrypted clipboard content -- 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 340853] New: KMail Version 4.8.5 crashed
https://bugs.kde.org/show_bug.cgi?id=340853 Bug ID: 340853 Summary: KMail Version 4.8.5 crashed Product: kmail2 Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: erwin.fel...@gmx.net KMail Version 4.8.5: After downloading the emails from the server and switching to the local inbox folder KMail crashed. After restart everything works fine again. This bug might appear after booting the computer but it is rare. -- 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 340853] KMail Version 4.8.5 crashed
https://bugs.kde.org/show_bug.cgi?id=340853 --- Comment #1 from Ing. Erwin Felkel erwin.fel...@gmx.net --- Created attachment 89536 -- https://bugs.kde.org/attachment.cgi?id=89536action=edit the crash 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
[kmail2] [Bug 25594] thread reconstruction
https://bugs.kde.org/show_bug.cgi?id=25594 Erik Quaeghebeur kdeb...@equaeghe.nospammail.net changed: What|Removed |Added CC||kdebugs@equaeghe.nospammail ||.net --- Comment #29 from Erik Quaeghebeur kdeb...@equaeghe.nospammail.net --- I think this feature request is still very much relevant. (In reply to Karsten Dambekalns from comment #12) Ok, breaking a thread is easy to mimic (create filter that removes the needed headers, bind that to a shortcut). What about linking? Filters can add headers, but I'd need to know the msg-id for this to work. I could look it up, but then I'd have to edit the filter first, then run it. Any better solution? This seems to indicate almost all functionality is present in KMail except for filters that can take two (or more... In-Reply-To may contain multiple ids) ordered arguments (highlighted mails), no? -- 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 283020] Store Kmail Tags in IMAP flags, like Thunderbird
https://bugs.kde.org/show_bug.cgi?id=283020 --- Comment #8 from Erik Quaeghebeur kdeb...@equaeghe.nospammail.net --- FYI: I saw that Trojita supports IMAP tags; perhaps some code can be borrowed there? -- 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 340840] Show Facebook messages in KMail — make Facebook messages collection a mail collection
https://bugs.kde.org/show_bug.cgi?id=340840 --- Comment #1 from Martin Klapetek mklape...@kde.org --- Interesting idea. I think it could be done; it would require extending KFbAPI (the facebook lib) and then the resource. Should be easy, even :) I'm happy to review those patches and maybe get it to kf5-based resource too, but I have no plans on working on the kdelibs4 versions. -- 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 340853] KMail Version 4.8.5 crashed
https://bugs.kde.org/show_bug.cgi?id=340853 Laurent Montel mon...@kde.org changed: What|Removed |Added Resolution|--- |WONTFIX CC||mon...@kde.org Status|UNCONFIRMED |RESOLVED --- Comment #2 from Laurent Montel mon...@kde.org --- Sorry it's a very old version. And crash is in soprano that we don't use now. So I close as wontfix. Sorry. Better to upgrade version. Regards -- 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 340015] Filter rules no longer matching after upgrade
https://bugs.kde.org/show_bug.cgi?id=340015 --- Comment #12 from Colin J Thomson co...@g6avk.demon.co.uk --- The list-id filtering is now working fine after updating to 4.14.3/Fedora 21. Thanks.. -- 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 340861] New: Kontact crashed while trying to open a message
https://bugs.kde.org/show_bug.cgi?id=340861 Bug ID: 340861 Summary: Kontact crashed while trying to open a message Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ali.sheri...@yahoo.com Application: kontact (4.14.2) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.16.6-2-desktop x86_64 Distribution: openSUSE 13.2 (Harlequin) (x86_64) -- Information about the crash: - What I was doing when the application crashed: I tried to open a message, but it didn't open. I closed Kontact and opened it, but it didn't work. Then I closed KOrganizer Reminder Daemon with Kontact, but the message didn't open and Kontact crashed. I couldn't open an another message. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f356777f800 (LWP 13052))] Thread 4 (Thread 0x7f354a2cd700 (LWP 13053)): #0 0x7f355ed9305f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f3562524686 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x7f35625246b9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7f355ed8f0a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f3564d027fd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f35099c2700 (LWP 13054)): #0 0x7f355ed9305f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f3562296e7d in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib64/libQtWebKit.so.4 #2 0x7f356254c1e6 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7f355ed8f0a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f3564d027fd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f34fb28c700 (LWP 13059)): #0 0x7f3564cfa3cd in poll () from /lib64/libc.so.6 #1 0x7f355e7c3be4 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f355e7c3cec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f356547d0de in QEventDispatcherGlib::processEvents (this=0x7f34f40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #4 0x7f356544ee6f in QEventLoop::processEvents (this=this@entry=0x7f34fb28bde0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f356544f165 in QEventLoop::exec (this=this@entry=0x7f34fb28bde0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f356534c0bf in QThread::exec (this=optimized out) at thread/qthread.cpp:538 #7 0x7f356534e79f in QThreadPrivate::start (arg=0x1d4b850) at thread/qthread_unix.cpp:349 #8 0x7f355ed8f0a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7f3564d027fd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f356777f800 (LWP 13052)): [KCrash Handler] #6 KMail::MessageActions::printMessage (this=0x20c5d90, preview=optimized out) at /usr/src/debug/kdepim-4.14.2/kmail/messageactions.cpp:508 #7 0x7f35654641fa in QMetaObject::activate (sender=sender@entry=0x1e172e0, m=m@entry=0x7f35669024a0 QAction::staticMetaObject, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7fffc72f4b10) at kernel/qobject.cpp:3576 #8 0x7f3565e58622 in QAction::triggered (this=this@entry=0x1e172e0, _t1=false) at .moc/release-shared/moc_qaction.cpp:276 #9 0x7f3565e59fd3 in QAction::activate (this=this@entry=0x1e172e0, event=event@entry=QAction::Trigger) at kernel/qaction.cpp:1257 #10 0x7f3566282b79 in QMenuPrivate::activateCausedStack (this=this@entry=0x2209d70, causedStack=..., action=action@entry=0x1e172e0, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1037 #11 0x7f35662870c9 in QMenuPrivate::activateAction (this=0x2209d70, action=0x1e172e0, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1129 #12 0x7f356628aaa5 in QMenu::mouseReleaseEvent (this=this@entry=0x2209cc0, e=e@entry=0x7fffc72f5240) at widgets/qmenu.cpp:2371 #13 0x7f3566c2cce5 in KMenu::mouseReleaseEvent (this=0x2209cc0, e=0x7fffc72f5240) at /usr/src/debug/kdelibs-4.14.2/kdeui/widgets/kmenu.cpp:464 #14 0x7f3565eadc0a in QWidget::event (this=this@entry=0x2209cc0, event=event@entry=0x7fffc72f5240) at kernel/qwidget.cpp:8389 #15 0x7f356628af2b in QMenu::event (this=0x2209cc0, e=0x7fffc72f5240) at widgets/qmenu.cpp:2480 #16 0x7f3565e5e76c in QApplicationPrivate::notify_helper (this=this@entry=0x1a51cd0, receiver=receiver@entry=0x2209cc0, e=e@entry=0x7fffc72f5240) at kernel/qapplication.cpp:4565 #17 0x7f3565e64dea in QApplication::notify (this=this@entry=0x7fffc72f6980, receiver=receiver@entry=0x2209cc0, e=e@entry=0x7fffc72f5240) at
[Akonadi] [Bug 340865] New: Kmail Error keeps popping up.
https://bugs.kde.org/show_bug.cgi?id=340865 Bug ID: 340865 Summary: Kmail Error keeps popping up. Product: Akonadi Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: deathsly...@gmail.com CC: kdepim-bugs@kde.org, vkra...@kde.org Application: akonadi_imap_resource (4.14) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.17.2-1-ARCH x86_64 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: Using my desktop when it suddenly appears, In my opinion it seems like it has something to do with KMAIL The crash can be reproduced sometimes. -- Backtrace: Application: Google Mail (deathslycer) of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library /usr/lib/libthread_db.so.1. [Current thread is 1 (Thread 0x7fbb9d263780 (LWP 2977))] Thread 3 (Thread 0x7fbb89b0f700 (LWP 2979)): #0 0x7fbb97aa4fc4 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #1 0x7fbb97a60220 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #2 0x7fbb97a60bcb in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7fbb97a60dbc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7fbb9c894397 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #5 0x7fbb9c863de1 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #6 0x7fbb9c864145 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #7 0x7fbb9c7587f9 in QThread::exec() () from /usr/lib/libQtCore.so.4 #8 0x7fbb9c75b05f in ?? () from /usr/lib/libQtCore.so.4 #9 0x7fbb98146314 in start_thread () from /usr/lib/libpthread.so.0 #10 0x7fbb98ae63ed in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7fbb8930e700 (LWP 3020)): #0 0x7fbb98add5bd in poll () from /usr/lib/libc.so.6 #1 0x7fbb97a60ca4 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fbb97a60dbc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fbb9c894397 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #4 0x7fbb9c863de1 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #5 0x7fbb9c864145 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #6 0x7fbb9c7587f9 in QThread::exec() () from /usr/lib/libQtCore.so.4 #7 0x7fbb9c75b05f in ?? () from /usr/lib/libQtCore.so.4 #8 0x7fbb98146314 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fbb98ae63ed in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7fbb9d263780 (LWP 2977)): [KCrash Handler] #5 0x7fbb9a45f04d in KIMAP::SearchJob::handleResponse(KIMAP::Message const) () from /usr/lib/libkimap.so.4 #6 0x7fbb9a450008 in KIMAP::SessionPrivate::responseReceived(KIMAP::Message const) () from /usr/lib/libkimap.so.4 #7 0x7fbb9c87e491 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #8 0x7fbb9bbb9b2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #9 0x7fbb9bbc0588 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #10 0x7fbb99c7a2da in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #11 0x7fbb9c86528d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #12 0x7fbb9c868651 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #13 0x7fbb9c894233 in ?? () from /usr/lib/libQtCore.so.4 #14 0x7fbb97a60a1d in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #15 0x7fbb97a60d08 in ?? () from /usr/lib/libglib-2.0.so.0 #16 0x7fbb97a60dbc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #17 0x7fbb9c89437d in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #18 0x7fbb9bc5d526 in ?? () from /usr/lib/libQtGui.so.4 #19 0x7fbb9c863de1 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #20 0x7fbb9c864145 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #21 0x7fbb9c8696e9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #22 0x7fbb9cd60b6c in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib/libakonadi-kde.so.4 #23 0x00418cde in _start () Possible duplicates by query: bug 340157, bug 339395, bug 332724, bug 332072, bug 331698.
[kontact] [Bug 340867] New: Kontact refuses to start complaining about a syntax error.
https://bugs.kde.org/show_bug.cgi?id=340867 Bug ID: 340867 Summary: Kontact refuses to start complaining about a syntax error. Product: kontact Version: 4.13.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: staka...@freenet.de Suddenly I am not able to use contact in my mail personality. I do not understand why. In terminal the message is: kontact Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kontact(7548) KDirWatch::removeDir: doesn't know /home/hermes/.kde4/share/apps/messageviewer/themes/ kontact(7548) KDirWatch::removeDir: doesn't know /usr/share/kde4/apps/messageviewer/themes/ json_parser - syntax error found, forcing abort, Line 1 Column 0 kontact(7548)/kdeui (kdelibs): No such XML file /home/hermes/.kde4/share/apps/kontact/default-.rc I can start all single components, included kmail. All mails in kmail are visible. Also organizer opens per itself. Bug when I try to start kontact, you get only the above (although kwallet askes for the password, so it comes up to that point at least (this is the working kmail component I think). Suggestions? Reproducible: Always Steps to Reproduce: 1. try to open kontact 2. does not open 3. open in terminal will give you the above. Actual Results: The start of Kontact aborts although the single coponents are startable. Expected Results: Kontact should start. This is apparently limited to this personality. But it is also true that it is this personality that receives all mail. -- 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 340818] Tries to attach directories
https://bugs.kde.org/show_bug.cgi?id=340818 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel mon...@kde.org --- I don't understand how you can make an error? If you want to attach a file you select file no ? -- 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
