[kontact] [Bug 459905] New: Kmail/Kontact crash when replying to email
https://bugs.kde.org/show_bug.cgi?id=459905 Bug ID: 459905 Summary: Kmail/Kontact crash when replying to email Classification: Applications Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ericsbinarywo...@gmail.com Target Milestone: --- Application: kontact (5.20.1 (22.04.1)) Qt Version: 5.15.6 Frameworks Version: 5.98.0 Operating System: Linux 5.19.12-200.fc36.x86_64 x86_64 Windowing System: X11 Distribution: "Fedora release 36 (Thirty Six)" DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: Seems to be related to bug #449898 and bug #449872 as I can get it to stop crashing if I set my encryption keys to "no key" in identity. Yet in bug 449898 the person says it was fixed for them with Kmail 21.12.2-2. But it's happening to me with Kmail 22.04.1. A regression perhaps? To be specific, my Kmail says Version 5.20.1 (22.04.1) The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7f1bd2c6a0b3 in QString::QString(QString const&) () from /lib64/libqgpgme.so.7 #5 0x7f1bd2c6a231 in QGpgME::QGpgMEAddUserIDJob::start(GpgME::Key const&, QString const&, QString const&, QString const&) () from /lib64/libqgpgme.so.7 #6 0x7f1bd3779e11 in KMComposerWin::slotRecipientAdded(MessageComposer::RecipientLineNG*) () from /lib64/libkmailprivate.so.5 #7 0x7f1c892db9a6 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #8 0x7f1bd3276541 in MessageComposer::RecipientLineNG::analyzeLine(QString const&) () from /lib64/libKF5MessageComposer.so.5 #9 0x7f1c892db9a6 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #10 0x7f1c8a0f9456 in QLineEdit::textChanged(QString const&) () from /lib64/libQt5Widgets.so.5 #11 0x7f1c892dbb2f in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #12 0x7f1c8a100c59 in QWidgetLineControl::textChanged(QString const&) () from /lib64/libQt5Widgets.so.5 #13 0x7f1c8a104460 in QWidgetLineControl::finishChange(int, bool, bool) () from /lib64/libQt5Widgets.so.5 #14 0x7f1c8a104722 in QWidgetLineControl::internalSetText(QString const&, int, bool) () from /lib64/libQt5Widgets.so.5 #15 0x7f1bd2b520f5 in PimCommon::AddresseeLineEdit::setText(QString const&) () from /lib64/libKF5PimCommonAkonadi.so.5 #16 0x7f1bd3273bfb in MessageComposer::RecipientLineNG::fieldsFromData() () from /lib64/libKF5MessageComposer.so.5 #17 0x7f1bd3273d2f in MessageComposer::RecipientLineNG::setData(QSharedPointer const&) () from /lib64/libKF5MessageComposer.so.5 #18 0x7f1c89d38764 in KPIM::MultiplyingLineEditor::addData(QSharedPointer const&, bool) () from /lib64/libKF5Libkdepim.so.5 #19 0x7f1bd327442e in MessageComposer::RecipientsEditor::addRecipient(QString const&, MessageComposer::Recipient::Type) () from /lib64/libKF5MessageComposer.so.5 #20 0x7f1bd3278db1 in MessageComposer::RecipientsEditor::setRecipientString(QVector const&, MessageComposer::Recipient::Type) () from /lib64/libKF5MessageComposer.so.5 #21 0x7f1bd32531d5 in MessageComposer::ComposerViewBase::setMessage(QSharedPointer const&, bool) () from /lib64/libKF5MessageComposer.so.5 #22 0x7f1bd37666c5 in KMComposerWin::setMessage(QSharedPointer const&, bool, bool, bool, bool, bool) () from /lib64/libkmailprivate.so.5 #23 0x7f1bd3764e2e in KMComposerWin::KMComposerWin(QSharedPointer const&, bool, bool, KMail::Composer::TemplateContext, unsigned int, QString const&, QString const&) () from /lib64/libkmailprivate.so.5 #24 0x7f1bd375ac55 in KMail::makeComposer(QSharedPointer const&, bool, bool, KMail::Composer::TemplateContext, unsigned int, QString const&, QString const&) () from /lib64/libkmailprivate.so.5 #25 0x7f1bd379378c in CreateReplyMessageJob::slotCreateReplyDone(MessageComposer::MessageFactoryNG::MessageReply const&) () from /lib64/libkmailprivate.so.5 #26 0x7f1c892db9a6 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #27 0x7f1bd322a0b6 in MessageComposer::MessageFactoryNG::createReplyDone(MessageComposer::MessageFactoryNG::MessageReply const&) () from /lib64/libKF5MessageComposer.so.5 #28 0x7f1bd329ddc4 in MessageComposer::MessageFactoryNG::slotCreateReplyDone(QSharedPointer const&, bool) () from /lib64/libKF5MessageComposer.so.5 #29 0x7f1c892db9a6 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #30 0x7f1bd329faa3 in MessageComposer::MessageFactoryReplyJob::slotReplyDone() () from /lib64/libKF5MessageComposer.so.5 #31 0x7f1c892db9a6 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #32 0x7f1bd314d0e3 in
[Akonadi] [Bug 435035] New: Cannot authorize Google because "browser may be not be secure"
https://bugs.kde.org/show_bug.cgi?id=435035 Bug ID: 435035 Summary: Cannot authorize Google because "browser may be not be secure" Product: Akonadi Version: 5.15.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Gmail resource Assignee: dvra...@kde.org Reporter: ericsbinarywo...@gmail.com CC: kdepim-bugs@kde.org Target Milestone: --- SUMMARY In KOrganizer calendars window when trying to sign into Google account oauth, after I put in my gmail address I cannot put in my password because it says "this browser or app may not be secure" STEPS TO REPRODUCE 1. Go to the Korganizer settings 2. Go to calendar tab 3. Click to either add or modify an existing Gmail account 4. click on configure next to the account. 5. Put in gmail address 6. get error OBSERVED RESULT Cannot complete oauth EXPECTED RESULT Complete oauth so that Korganizer can talk to Google Calendar SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 33 (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are on the CC list for the bug.
[kontact] [Bug 351215] New: Kontact Crashes on Close
https://bugs.kde.org/show_bug.cgi?id=351215 Bug ID: 351215 Summary: Kontact Crashes on Close Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ericsbinarywo...@gmail.com Application: kontact (4.14.9) KDE Platform Version: 4.14.9 Qt Version: 4.8.6 Operating System: Linux 4.1.3-201.fc22.x86_64 x86_64 Distribution: Fedora release 22 (Twenty Two) -- Information about the crash: To crash it, I just closed Kontact. The only sign that it's likely to crash is that emails stop updating correctly The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7ff3461fe900 (LWP 7889))] Thread 3 (Thread 0x7ff2f61e3700 (LWP 7890)): #0 0x0036a220c540 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff34b12ef61 in JSC::BlockAllocator::blockFreeingThreadMain() () at /lib64/libQtWebKit.so.4 #2 0x7ff34b42d6d6 in WTF::wtfThreadEntryPoint(void*) () at /lib64/libQtWebKit.so.4 #3 0x0036a2207555 in start_thread () at /lib64/libpthread.so.0 #4 0x0036a1b02b9d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7ff2ea2b3700 (LWP 7900)): #0 0x0036a328eee4 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x0036a324978a in g_main_context_check () at /lib64/libglib-2.0.so.0 #2 0x0036a3249d60 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x0036a3249ecc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x0036acfba4ee in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () at /lib64/libQtCore.so.4 #5 0x0036acf88791 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () at /lib64/libQtCore.so.4 #6 0x0036acf88b05 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () at /lib64/libQtCore.so.4 #7 0x0036ace78289 in QThread::exec() () at /lib64/libQtCore.so.4 #8 0x0036ace7aaac in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4 #9 0x0036a2207555 in start_thread () at /lib64/libpthread.so.0 #10 0x0036a1b02b9d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7ff3461fe900 (LWP 7889)): [KCrash Handler] #6 0x00313e3509eb in QItemSelectionModel::selectedIndexes() const () at /lib64/libQtGui.so.4 #7 0x7ff2ef4ac047 in MailCommon::FolderTreeWidget::selectedCollections() const () at /lib64/libmailcommon.so.4 #8 0x7ff2ec5e8333 in KMMainWidget::updateFolderMenu() () at /lib64/libkmailprivate.so.4 #9 0x7ff2ec6ef48b in KMMainWidget::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () at /lib64/libkmailprivate.so.4 #10 0x0036acf9e0c0 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /lib64/libQtCore.so.4 #11 0x0036acfa3d33 in QObject::event(QEvent*) () at /lib64/libQtCore.so.4 #12 0x00313ddc43ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQtGui.so.4 #13 0x00313ddcb206 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQtGui.so.4 #14 0x003aeac5505a in KApplication::notify(QObject*, QEvent*) () at /lib64/libkdeui.so.5 #15 0x0036acf89f1d in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /lib64/libQtCore.so.4 #16 0x0036acfbc9a0 in QTimerInfoList::activateTimers() () at /lib64/libQtCore.so.4 #17 0x0036acfb9b11 in timerSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQtCore.so.4 #18 0x0036a3249a8a in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #19 0x0036a3249e20 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #20 0x0036a3249ecc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #21 0x0036acfba4ce in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () at /lib64/libQtCore.so.4 #22 0x00313de6a626 in QGuiEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () at /lib64/libQtGui.so.4 #23 0x0036acf88791 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () at /lib64/libQtCore.so.4 #24 0x0036acf88b05 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () at /lib64/libQtCore.so.4 #25 0x003aea140ca3 in KJob::exec() () at /lib64/libkdecore.so.5 #26 0x7ff2ec5b0bce in KMKernel::cleanup() () at /lib64/libkmailprivate.so.4 #27 0x7ff2ec9a1b98 in KMailPart::~KMailPart() () at /usr/lib64/kde4/kmailpart.so #28 0x7ff2ec9a1e19 in KMailPart::~KMailPart() () at /usr/lib64/kde4/kmailpart.so #29 0x003afb80f8fe in KontactInterface::Plugin::~Plugin() () at /lib64/libkontactinterface.so.4 #30 0x7ff2ed1f6a36 in KMailPlugin::~KMailPlugin() () at /usr/lib64/kde4/kontact_kmailplugin.so #31
[kmail2] [Bug 351228] New: Dropbox for attachments configuration loads a web part that doesn't work
https://bugs.kde.org/show_bug.cgi?id=351228 Bug ID: 351228 Summary: Dropbox for attachments configuration loads a web part that doesn't work Product: kmail2 Version: 4.14.7 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: config dialog Assignee: kdepim-bugs@kde.org Reporter: ericsbinarywo...@gmail.com While looking through the Kmail options today, I saw that for large attachments, Kmail can send the file to dropbox and generate the link. But when I try to authorize Dropbox to Kmail, the website that's loaded doesn't work. I can type in my username/password, but the website doesn't recognize that I've typed anything and so the button to authorize it never becomes ungreyed. If it helps solve what the problem is, the placeholder text that tells you what to type into the box remains superimposed over what I'm typing. In normal operation on websites, this text disappears when the user starts typing. Reproducible: Always Steps to Reproduce: 1. Go to config for attachments 2. Try to configure dropbox 3. Type in username (I think it's email) and password 4. Try to click on the button to authorize it Actual Results: Can't click button because it (apparently) doesn't know I'm typing Expected Results: Should allow me to authorize dropbox. -- 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 319343] New: An akonadi resource for remember the milk
https://bugs.kde.org/show_bug.cgi?id=319343 Bug ID: 319343 Summary: An akonadi resource for remember the milk Classification: Unclassified Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ericsbinarywo...@gmail.com I would like Remember the Milk to integrate with Knotes via an akonadi resource Reproducible: Always Steps to Reproduce: 1. setup RTM akonadi resource 2. Use Knotes to manage RTM tasks 3. Profit Actual Results: Not there yet Expected Results: Should work -- 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 278887] Mbox resource never deletes email
https://bugs.kde.org/show_bug.cgi?id=278887 Eric Mesa ericsbinarywo...@gmail.com changed: What|Removed |Added CC||ericsbinarywo...@gmail.com --- Comment #7 from Eric Mesa ericsbinarywo...@gmail.com --- *** Bug 290013 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 290013] Kmail2 does not mark system messages as read, deleted, etc
https://bugs.kde.org/show_bug.cgi?id=290013 Eric Mesa ericsbinarywo...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from Eric Mesa ericsbinarywo...@gmail.com --- yeah, I'm ok with calling it a duplicate *** This bug has been marked as a duplicate of bug 278887 *** -- 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 290013] Kmail2 does not mark system messages as read, deleted, etc
https://bugs.kde.org/show_bug.cgi?id=290013 --- Comment #4 from Eric Mesa ericsbinaryworld gmail com 2012-01-06 11:52:46 --- The permissions are: -rw-rw.with myself as owner and mail as group owner. I click on the email and I get: kontact(9517): Error while fetching items. 103 Unknown error. (Cannot list root collection.) kontact(9517): Error while fetching items. 103 Unknown error. (Cannot list root collection.) kontact(9517): Error while fetching items. 103 Unknown error. (Cannot list root collection.) kontact(9517): Error while fetching items. 103 Unknown error. (Cannot list root collection.) kontact(9517): Error while fetching items. 103 Unknown error. (Cannot list root collection.) kontact(9517): Error while fetching items. 103 Unknown error. (Cannot list root collection.) kontact(9517): Error while fetching items. 103 Unknown error. (Cannot list root collection.) kontact(9517): Error while fetching items. 103 Unknown error. (Cannot list root collection.) (that's the output of Kontact in the commandline) But that only happens on the first email. All the others display without errors. And there are no errors as I delete them. But as soon as I go in and out of mutt, they call come back. Let me see akonadi. Here's me accessing the mail: request for item 411285 succeeded void Nepomuk::Query::QueryServiceClient::close() void Nepomuk::Query::QueryServiceClient::close() AkonadiAgentServer(9812)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know /var/spool/mail This comes up when I delete it: posting retrieval request for item 411286 there are 1 queues and 0 items in mine request for item 411286 still pending - waiting processing retrieval request for item 411286 parts: (RFC822) of resource: akonadi_mbox_resource_0 continuing request for item 411286 succeeded AkonadiAgentServer(9812)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know /var/spool/mail void Nepomuk::Query::QueryServiceClient::close() void Nepomuk::Query::QueryServiceClient::close() AkonadiAgentServer(9812)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know /var/spool/mail And that happens every time I try to delete one. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 290013] Kmail2 does not mark system messages as read, deleted, etc
https://bugs.kde.org/show_bug.cgi?id=290013 --- Comment #2 from Eric Mesa ericsbinaryworld gmail com 2012-01-05 01:25:08 --- It's MBox -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 290013] New: Kmail2 does not mark system messages as read, deleted, etc
https://bugs.kde.org/show_bug.cgi?id=290013 Summary: Kmail2 does not mark system messages as read, deleted, etc Product: kmail2 Version: unspecified Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: ericsbinarywo...@gmail.com Version: unspecified (using KDE 4.7.3) OS:Linux I have Kmail2 setup to check my system messages (the ones you get from cronjobs or logwatch). With Kmail 1 this worked perfectly. With Kmail2 when I mark a message as read or deleted, the next time that folder refreshes the message is once again marked as new. So while I can use Kmail2 to read these messages, I need to use mutt to actually delete them or mark hem as read. Reproducible: Always Steps to Reproduce: 1. Check system messages 2. Delete messages after reading 3. Refresh system messages 4. Messages are back and marked as new Actual Results: The messages appear again marked new Expected Results: Deleted messages should be removed from the system. Messages marked read should stay marked read. This is on Fedora 16 with the following kdepim package: http://lists.fedoraproject.org/pipermail/package-announce/2011-December/071186.html I'm not in front of the computer right now, but I know I applied this update. So I'm using whatever versions of Kontact/Kmail2 are in there. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
