[kontact] [Bug 443037] Kontact Crashed When Starting
https://bugs.kde.org/show_bug.cgi?id=443037 --- Comment #1 from john4deidre2...@xtra.co.nz --- Created attachment 142595 --> https://bugs.kde.org/attachment.cgi?id=142595=edit New crash information added by DrKonqi kontact (5.18.2 (21.08.2)) using Qt 5.15.2 - What I was doing when the application crashed: When you intermittently start kontact it will crash with a seqfault. this is still happening with the most recent stable version of the kde pim -- Backtrace (Reduced): #6 0x7f0f6c97ea75 in QScopedPointer >::operator-> (this=0x8) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118 [...] #9 QAction::setText (this=this@entry=0x0, text=...) at kernel/qaction.cpp:714 #10 0x7f0f059b5f8a in KMMainWidget::updateFolderMenu (this=0x556cac5103b0) at /usr/src/debug/kmail-21.08.2-1.1.x86_64/src/kmmainwidget.cpp:3996 #11 0x7f0f059ad746 in KMMainWidget::setupActions (this=0x556cac5103b0) at /usr/src/debug/kmail-21.08.2-1.1.x86_64/src/kmmainwidget.cpp:3384 #12 0x7f0f05997c14 in KMMainWidget::KMMainWidget (this=, parent=, aGUIClient=, actionCollection=, config=..., this=, parent=, aGUIClient=, actionCollection=, config=...) at /usr/src/debug/kmail-21.08.2-1.1.x86_64/src/kmmainwidget.cpp:249 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 443037] Kontact Crashed When Starting
https://bugs.kde.org/show_bug.cgi?id=443037 john4deidre2...@xtra.co.nz changed: What|Removed |Added CC||john4deidre2...@xtra.co.nz -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 423426] POP3 setup wizard defaults to unencrypted connections.
https://bugs.kde.org/show_bug.cgi?id=423426 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #5 from Albert Astals Cid --- Laurent should this be marked as fixed? One of your commits says "Fix 423426" but this is not marked as fixed yet. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 434132] Text on HTML-"buttons" invisible
https://bugs.kde.org/show_bug.cgi?id=434132 --- Comment #6 from Attila --- Thank you for your quick reply. Indeed the checkbox "do not change color from origin html" wasn't ticked. That fixes the issue. Shouldn't the checkbox be ticked by default to avoid incorrect display on the screen? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 443988] New: KMail crashed after start-up of openSUSE PC from StandBy Mode, Login and Start of KMail
https://bugs.kde.org/show_bug.cgi?id=443988 Bug ID: 443988 Summary: KMail crashed after start-up of openSUSE PC from StandBy Mode, Login and Start of KMail Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: philipp.grim...@web.de Target Milestone: --- Application: kmail (5.18.1 (21.08.1)) Qt Version: 5.15.2 Frameworks Version: 5.86.0 Operating System: Linux 5.14.9-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: openSUSE Tumbleweed -- Information about the crash: - What I was doing when the application crashed: I started up my PC from its StandBy Mode, logged into openSUSE Tumbleweed and started KMail (as no programs were open anymore). Then the KMail App crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fd43d4ec040 (LWP 1931))] [KCrash Handler] #6 0x7fd44aab9a75 in QScopedPointer >::operator-> (this=0x8) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118 #7 qGetPtrHelper > > (ptr=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:1143 #8 QAction::d_func (this=0x0) at kernel/qaction.h:63 #9 QAction::setText (this=0x0, text=...) at kernel/qaction.cpp:714 #10 0x7fd452ef0f8a in KMMainWidget::updateFolderMenu() () from /lib64/libkmailprivate.so.5 #11 0x7fd452ee8746 in KMMainWidget::setupActions() () from /lib64/libkmailprivate.so.5 #12 0x7fd452ed2c14 in KMMainWidget::KMMainWidget(QWidget*, KXMLGUIClient*, KActionCollection*, QExplicitlySharedDataPointer const&) () from /lib64/libkmailprivate.so.5 #13 0x7fd452e9a75b in KMMainWin::KMMainWin(QWidget*) () from /lib64/libkmailprivate.so.5 #14 0x7fd452eac167 in KMKernel::openReader(bool, bool) () from /lib64/libkmailprivate.so.5 #15 0x7fd452eb14af in KMKernel::action(bool, bool, bool, QString const&, QString const&, QString const&, QString const&, QString const&, QUrl const&, QList const&, QStringList const&, QString const&, QString const&, QString const&) () from /lib64/libkmailprivate.so.5 #16 0x7fd452eaac43 in KMKernel::handleCommandLine(bool, QStringList const&, QString const&) () from /lib64/libkmailprivate.so.5 #17 0x561b26936882 in ?? () #18 0x7fd452fdd703 in ?? () from /lib64/libKF5KontactInterface.so.5 #19 0x7fd452fdd7e3 in KontactInterface::PimUniqueApplication::qt_metacall(QMetaObject::Call, int, void**) () from /lib64/libKF5KontactInterface.so.5 #20 0x7fd4495aa69b in QDBusConnectionPrivate::deliverCall (this=, object=, msg=..., metaTypes=..., slotIdx=) at ../../include/QtCore/../../src/corelib/tools/qvarlengtharray.h:190 #21 0x7fd4495ae08c in QDBusConnectionPrivate::activateCall (this=this@entry=0x7fd424003a00, object=0x7fffbade5710, flags=81, msg=...) at qdbusintegrator.cpp:904 #22 0x7fd4495ae91d in QDBusConnectionPrivate::activateCall (msg=..., flags=, object=, this=0x7fd424003a00) at qdbusintegrator.cpp:853 #23 QDBusConnectionPrivate::activateObject (this=0x7fd424003a00, node=..., msg=..., pathStartPos=) at qdbusintegrator.cpp:1521 #24 0x7fd4495b0e38 in QDBusActivateObjectEvent::placeMetaCall (this=0x561b2c62da40) at qdbusintegrator.cpp:1617 #25 0x7fd449f3afbe in QObject::event (this=0x7fffbade5710, e=0x561b2c62da40) at kernel/qobject.cpp:1314 #26 0x7fd44aabda7f in QApplicationPrivate::notify_helper (this=, receiver=0x7fffbade5710, e=0x561b2c62da40) at kernel/qapplication.cpp:3632 #27 0x7fd449f0e9ca in QCoreApplication::notifyInternal2 (receiver=0x7fffbade5710, event=0x561b2c62da40) at kernel/qcoreapplication.cpp:1064 #28 0x7fd449f11a17 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x561b26c8c1e0) at kernel/qcoreapplication.cpp:1821 #29 0x7fd449f66823 in postEventSourceDispatch (s=s@entry=0x561b26dea640) at kernel/qeventdispatcher_glib.cpp:277 #30 0x7fd443c10d5f in g_main_dispatch (context=0x7fd434005000) at ../glib/gmain.c:3381 #31 g_main_context_dispatch (context=0x7fd434005000) at ../glib/gmain.c:4099 #32 0x7fd443c110e8 in g_main_context_iterate (context=context@entry=0x7fd434005000, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4175 #33 0x7fd443c1119f in g_main_context_iteration (context=0x7fd434005000, may_block=1) at ../glib/gmain.c:4240 #34 0x7fd449f65ea4 in QEventDispatcherGlib::processEvents (this=0x561b26de7430, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #35 0x7fd449f0d3cb in QEventLoop::exec (this=this@entry=0x7fffbade51f0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #36 0x7fd449f156b0 in QCoreApplication::exec
[Akonadi] [Bug 443954] Crash in akonadi_ews_resource
https://bugs.kde.org/show_bug.cgi?id=443954 Nate Graham changed: What|Removed |Added Product|kde |Akonadi CC||n...@kde.org Component|general |general Assignee|unassigned-b...@kde.org |kdepim-bugs@kde.org -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 434132] Text on HTML-"buttons" invisible
https://bugs.kde.org/show_bug.cgi?id=434132 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #5 from Laurent Montel --- (In reply to Attila from comment #4) > The bug still exists on Fedora 34, KMail 5.16.2. > Can someone please take a look at this bug? > It is a bad user experience when E-Mails are not displayed correct and > therefore the user can't read them. There is a checkbox in configure->appearence->color-> "do not change color from origin html" could you check it and verify if it fixes your problem ? As there is not a testcase here I can't test it. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 443958] Kmail crash/segmentation fault when quitting the application
https://bugs.kde.org/show_bug.cgi?id=443958 --- Comment #1 from James Beddek --- Note: I see bugs like https://bugs.kde.org/show_bug.cgi?id=394419 which seem very similar to mine, but those have been closed due to inactivity by the looks of it. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 443958] New: Kmail crash/segmentation fault when quitting the application
https://bugs.kde.org/show_bug.cgi?id=443958 Bug ID: 443958 Summary: Kmail crash/segmentation fault when quitting the application Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: tel...@posteo.de Target Milestone: --- Application: kmail (5.18.2 (21.08.2)) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.87.0 Operating System: Linux 5.14.12-gentoo-dist x86_64 Windowing System: X11 Distribution: Gentoo Linux DrKonqi: 5.23.0 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Quitting the application. Either through the task bar or through the GUI interface. I believe this bug has only just started with the introduction of the 5.23.0 packages, but I am not sure. Hopefully the backtrace is useful (qtwebengine -g build times are a nightmare) The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [New LWP 104804] [New LWP 104859] [New LWP 104868] [New LWP 104870] [New LWP 104883] [New LWP 104902] [New LWP 104916] [New LWP 104957] [New LWP 104958] [New LWP 104959] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7f5212a056c2 in __futex_abstimed_wait_common64 (futex_word=futex_word@entry=0x7f51fa437910, expected=104859, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=128, cancel=cancel@entry=true) at ../sysdeps/nptl/futex-internal.c:74 __preamble__ Thread 11 (Thread 0x7f51ddffb640 (LWP 104959) "ThreadPoolForeg"): #0 0x7f5212a056c2 in __futex_abstimed_wait_common64 (futex_word=futex_word@entry=0x7f51ddffa380, expected=expected@entry=0, clockid=clockid@entry=1, abstime=abstime@entry=0x7f51ddffa220, private=private@entry=0, cancel=cancel@entry=true) at ../sysdeps/nptl/futex-internal.c:74 #1 0x7f5212a0572b in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7f51ddffa380, expected=expected@entry=0, clockid=clockid@entry=1, abstime=abstime@entry=0x7f51ddffa220, private=private@entry=0) at ../sysdeps/nptl/futex-internal.c:123 #2 0x7f52129ff1b4 in __pthread_cond_wait_common (abstime=0x7f51ddffa220, clockid=1, mutex=0x7f51ddffa330, cond=0x7f51ddffa358) at pthread_cond_wait.c:504 #3 __pthread_cond_timedwait (cond=0x7f51ddffa358, mutex=0x7f51ddffa330, abstime=0x7f51ddffa220) at pthread_cond_wait.c:637 #4 0x7f5219ede094 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f5219edea68 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f5219ebb87c in base::internal::WorkerThread::Delegate::WaitForWork(base::WaitableEvent*) () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f5219ebbf0a in base::internal::WorkerThread::RunWorker() () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f5219ebbd9d in base::internal::WorkerThread::RunPooledWorker() () at /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7f5219ee155a in base::(anonymous namespace)::ThreadFunc(void*) () at /usr/lib64/libQt5WebEngineCore.so.5 #10 0x7f52129f8e1e in start_thread (arg=0x7f51ddffb640) at pthread_create.c:481 #11 0x7f52157509cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f51dd7fa640 (LWP 104958) "ThreadPoolForeg"): #1 0x7f5212a0572b in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7f51dd7f9380, expected=expected@entry=0, clockid=clockid@entry=1, abstime=abstime@entry=0x7f51dd7f9220, private=private@entry=0) at ../sysdeps/nptl/futex-internal.c:123 #2 0x7f52129ff1b4 in __pthread_cond_wait_common (abstime=0x7f51dd7f9220, clockid=1, mutex=0x7f51dd7f9330, cond=0x7f51dd7f9358) at pthread_cond_wait.c:504 #3 __pthread_cond_timedwait (cond=0x7f51dd7f9358, mutex=0x7f51dd7f9330, abstime=0x7f51dd7f9220) at pthread_cond_wait.c:637 #4 0x7f5219ede094 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f5219edea68 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f5219ebb87c in base::internal::WorkerThread::Delegate::WaitForWork(base::WaitableEvent*) () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f5219ebbfbe in base::internal::WorkerThread::RunWorker() () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f5219ebbd9d in base::internal::WorkerThread::RunPooledWorker() () at /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7f5219ee155a in base::(anonymous namespace)::ThreadFunc(void*) () at /usr/lib64/libQt5WebEngineCore.so.5 #10 0x7f52129f8e1e in start_thread (arg=0x7f51dd7fa640) at
[kmail2] [Bug 443949] New: kmail freezes when answering complex mail
https://bugs.kde.org/show_bug.cgi?id=443949 Bug ID: 443949 Summary: kmail freezes when answering complex mail Product: kmail2 Version: 5.16.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: gran...@tempmail.de Target Milestone: --- After a while of sending and receiving responses to an email (-thread) kmail freezes on composing the next response. When it unfreezes and I change the content (e.g. just type "hello") it freezes again. I dont know how to figure out what exactly makes kmail freeze I already disabled spell checking and removed pictures. I also switched rich text to off. The mail is approx 4.5 k raw source lines long -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 443829] All components are empty sporadically
https://bugs.kde.org/show_bug.cgi?id=443829 --- Comment #4 from dralexander...@protonmail.com --- I forgot to precise that I tried to restart Kontact afterwards but again, all the configuration vanished. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 443829] All components are empty sporadically
https://bugs.kde.org/show_bug.cgi?id=443829 --- Comment #3 from dralexander...@protonmail.com --- (In reply to gjditchfield from comment #1) > - Restarting Akonadi: type "akonadictl restart" at the command line, or use > the Server menu of the Akonadi Console app. I reproduced the same issue today and I used the terminal to set the command "akonadictl restart". Here is the result of this command : /usr/bin/mysqlcheck: Got error: 1049: Unknown database 'akonadi' when selecting the database org.kde.pim.akonadiserver: Running DB initializer org.kde.pim.akonadiserver: DB initializer done Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) org.kde.pim.akonadicontrol: Akonadi server is now operational. org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f7da0003f20) ) org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f7da0003f20) identified as "AgentBaseChangeRecorder - 93852054106672" org.kde.pim.akonadicontrol: Agent instance with identifier "akonadi_imap_resource_11" does not exist org.kde.pim.akonadicontrol: Agent instance with identifier "akonadi_maildispatcher_agent" does not exist org.kde.pim.akonadicontrol: Agent instance with identifier "akonadi_imap_resource_12" does not exist After waiting for several minutes without update, I interrupted the script. I do not know if it can explain the several bugs I had so far. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 443948] Email not loading
https://bugs.kde.org/show_bug.cgi?id=443948 --- Comment #1 from dralexander...@protonmail.com --- Created attachment 142565 --> https://bugs.kde.org/attachment.cgi?id=142565=edit Folder loading -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 443948] New: Email not loading
https://bugs.kde.org/show_bug.cgi?id=443948 Bug ID: 443948 Summary: Email not loading Product: kontact Version: 5.17.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: dralexander...@protonmail.com Target Milestone: --- SUMMARY Due to the previous bug encountered, I uninstalled and reinstalled Kontact and created a few of my account one more time. With only two email accounts set up in mail component since yesterday, the folders are still loading and the content of the email is not visible (cf. the prinscreen). Even the synchronisation with the incoming server does not respond. I send two emails and I received them instantaneously on Thunderbird but still nothing on Kmail. STEPS TO REPRODUCE 1. Email forder content keeps loading over time 2. 3. OBSERVED RESULT EXPECTED RESULT Loading and synchronisation time reduced SOFTWARE/OS VERSIONS Windows: / macOS: / Linux/KDE Plasma: Manjaro KDE (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0
https://bugs.kde.org/show_bug.cgi?id=389829 --- Comment #9 from Attila --- The bug still exists on Fedora 34, KMail 5.16.2, Akonadi 5.16.2 (20.12.2). Can someone please take a look at this bug? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 434132] Text on HTML-"buttons" invisible
https://bugs.kde.org/show_bug.cgi?id=434132 --- Comment #4 from Attila --- The bug still exists on Fedora 34, KMail 5.16.2. Can someone please take a look at this bug? It is a bad user experience when E-Mails are not displayed correct and therefore the user can't read them. -- You are receiving this mail because: You are the assignee for the bug.
