[korganizer] [Bug 453121] calender can't connect to nextcloud
https://bugs.kde.org/show_bug.cgi?id=453121 --- Comment #9 from gjditchfi...@acm.org --- (In reply to m.eik michalke from comment #8) > i doubt that's the issue, at least im running with let's encrypt certs. > rather i suspect apache's TLS configuration could be causing this. can > anyone suggest how to best debug this, e.g. getting some informative logs of > the communication with the nextcloud server to get a hint what's going > wrong? the server itself doesn't log any errors; it hardly logged anything, > actually, as if it doesn't even get a request. I think you could use wireshark-qt to spy on the communication. I haven't found any hints about getting Qt to log more detail about the connection; maybe a Qt forum could help. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 453121] calender can't connect to nextcloud
https://bugs.kde.org/show_bug.cgi?id=453121 --- Comment #8 from m.eik michalke --- (In reply to gjditchfield from comment #7) > My second wild guess is that Qt and your browser use different > configurations; > Chrome uses a different SSL library, for instance. that would explain why access via browser is possible. > My third is that the Nextcloud CalDAV server is using a really old > certificate that could be > upgraded, but I'm way outside my knowledge. i doubt that's the issue, at least im running with let's encrypt certs. rather i suspect apache's TLS configuration could be causing this. can anyone suggest how to best debug this, e.g. getting some informative logs of the communication with the nextcloud server to get a hint what's going wrong? the server itself doesn't log any errors; it hardly logged anything, actually, as if it doesn't even get a request. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 453753] New: Akonadi crashes when opening KMail
https://bugs.kde.org/show_bug.cgi?id=453753 Bug ID: 453753 Summary: Akonadi crashes when opening KMail Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: akonadiserver (5.20.0 (22.04.0)) Qt Version: 5.15.3 Frameworks Version: 5.93.0 Operating System: Linux 5.17.7-gentoo-dist x86_64 Windowing System: Wayland Distribution: "Gentoo Base System release 2.8" DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: When I open KMail, it tries to start Akonadi, which immediately crashes. This is reproducible every time I open KMail. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x565000140274 in Akonadi::Server::SchemaVersion::generation (this=this@entry=0x7fb6a5bdc850) at /usr/include/qt5/QtCore/qshareddata.h:82 #5 0x5650001f97ba in Akonadi::Server::NotificationSubscriber::NotificationSubscriber (this=this@entry=0x7fb6983186f0, manager=manager@entry=0x565000581070, socketDescriptor=socketDescriptor@entry=163) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:307 #6 0x5650001f61bf in Akonadi::Server::NotificationManager::registerConnection (this=0x565000581070, socketDescriptor=163) at /tmp/portage/kde-apps/akonadi-22.04.0/work/akonadi-22.04.0/src/server/notificationmanager.cpp:87 #7 0x7fb6aae63d16 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #8 0x7fb6aae38415 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #9 0x7fb6aae3bab5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5 #10 0x7fb6aae8ab73 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/libQt5Core.so.5 #11 0x7fb6a935d60b in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #12 0x7fb6a935d8c8 in ?? () from /usr/lib64/libglib-2.0.so.0 #13 0x7fb6a935d97f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #14 0x7fb6aae8a604 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #15 0x7fb6aae36e3b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #16 0x7fb6aac817aa in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #17 0x7fb6aac82949 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #18 0x7fb6aa808f5a in ?? () from /usr/lib64/libc.so.6 #19 0x7fb6aa88e6fc in ?? () from /usr/lib64/libc.so.6 Thread 2 (Thread 0x7fb6a6aa6640 (LWP 19369) "QDBusConnection"): #1 0x7fb6aa8541a9 in clock_gettime () from /usr/lib64/libc.so.6 #2 0x7fb6aae89ec1 in qt_gettime() () from /usr/lib64/libQt5Core.so.5 #3 0x7fb6aae88809 in QTimerInfoList::updateCurrentTime() () from /usr/lib64/libQt5Core.so.5 #4 0x7fb6aae88c85 in QTimerInfoList::timerWait(timespec&) () from /usr/lib64/libQt5Core.so.5 #5 0x7fb6aae8a8de in timerSourcePrepare(_GSource*, int*) () from /usr/lib64/libQt5Core.so.5 #6 0x7fb6a935cd4b in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #7 0x7fb6a935d783 in ?? () from /usr/lib64/libglib-2.0.so.0 #8 0x7fb6a935d97f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #9 0x7fb6aae8a68e in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #10 0x7fb6aae36e3b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #11 0x7fb6aac817aa in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #12 0x7fb6ab173537 in QDBusConnectionManager::run() () from /usr/lib64/libQt5DBus.so.5 #13 0x7fb6aac82949 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #14 0x7fb6aa808f5a in ?? () from /usr/lib64/libc.so.6 #15 0x7fb6aa88e6fc in ?? () from /usr/lib64/libc.so.6 Thread 1 (Thread 0x7fb6a6ed8cc0 (LWP 19362) "akonadiserver"): #1 0x7fb6aa808624 in pthread_cond_timedwait () from /usr/lib64/libc.so.6 #2 0x7fb6aac882a5 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib64/libQt5Core.so.5 #3 0x7fb6aac82681 in QThread::wait(QDeadlineTimer) () from /usr/lib64/libQt5Core.so.5 #4 0x7fb6aac8149c in QThread::wait(unsigned long) () from /usr/lib64/libQt5Core.so.5 #5 0x565000223a40 in Akonadi::Server::AkThread::quitThread (this=this@entry=0x565000581070) at /tmp/portage/kde-apps/akonadi-22.04.0/work/akonadi-22.04.0/src/server/akthread.cpp:55 #6 0x5650001f527e in Akonadi::Server::NotificationManager::~NotificationManager (this=0x565000581070, __in_chrg=) at
[kmail2] [Bug 453240] kmail not downloading emails immediately on launch
https://bugs.kde.org/show_bug.cgi?id=453240 --- Comment #3 from BingMyBong --- (In reply to Christophe Giboudeaux from comment #2) > In KMail settings, Accounts / Receiving there's a "Retrieval Options" menu > for each account, Is the "Check mail on startup" box checked? Yes, its always been ticked -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 453240] kmail not downloading emails immediately on launch
https://bugs.kde.org/show_bug.cgi?id=453240 Christophe Giboudeaux changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Christophe Giboudeaux --- In KMail settings, Accounts / Receiving there's a "Retrieval Options" menu for each account, Is the "Check mail on startup" box checked? -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 451096] does not refresh when launching kontact after 30 mn
https://bugs.kde.org/show_bug.cgi?id=451096 --- Comment #2 from Philippe ROUBACH --- KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 KDE Gear 22.04.1 Problem stil there. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 453723] Kmail new message cannot choose non-default transport
https://bugs.kde.org/show_bug.cgi?id=453723 Christophe Giboudeaux changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 453723] Kmail new message cannot choose non-default transport
https://bugs.kde.org/show_bug.cgi?id=453723 --- Comment #4 from rob.d...@telus.net --- Found it. New message -> view -> mail transport Thanks for a push in the general direction -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 453723] Kmail new message cannot choose non-default transport
https://bugs.kde.org/show_bug.cgi?id=453723 --- Comment #3 from Christophe Giboudeaux --- (In reply to rob.dyck from comment #2) > composer -> view doesn't exit > only general, standard templates, custom templates, subject, charset, > headers, attachments, auto correction and auto resize image. In the composer window, not in KMail settings. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 453723] Kmail new message cannot choose non-default transport
https://bugs.kde.org/show_bug.cgi?id=453723 --- Comment #2 from rob.d...@telus.net --- composer -> view doesn't exit only general, standard templates, custom templates, subject, charset, headers, attachments, auto correction and auto resize image. -- You are receiving this mail because: You are the assignee for the bug.
