[kontact] [Bug 414794] kmail crashing in kitinerary when opening a mail
https://bugs.kde.org/show_bug.cgi?id=414794 Jan-Matthias Braun changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REPORTED --- Comment #2 from Jan-Matthias Braun --- It probably was a stupid idea to just set the status to resolved, as kde applications 19.08 are going to be around a bit longer. I am setting this back to reported and leave the decision on the status to people who actually know how and when to do this. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 414794] kmail crashing in kitinerary when opening a mail
https://bugs.kde.org/show_bug.cgi?id=414794 Jan-Matthias Braun changed: What|Removed |Added Component|general |mail -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 414794] kmail crashing in kitinerary when opening a mail
https://bugs.kde.org/show_bug.cgi?id=414794 Jan-Matthias Braun changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Jan-Matthias Braun --- This seems to be fixed in kde-applications 19.11.90. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 414794] New: kmail crashing in kitinerary when opening a mail
https://bugs.kde.org/show_bug.cgi?id=414794 Bug ID: 414794 Summary: kmail crashing in kitinerary when opening a mail Product: kontact Version: 5.12.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jan_br...@gmx.net Target Milestone: --- Application: kontact (5.12.3) Qt Version: 5.14.0 Frameworks Version: 5.64.0 Operating System: Linux 5.4.1 x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: I was opening a mail from the my inbox. I could repeat this several times on the same mail, i.e., there are mails I cannot read. Compiler flags are (this is gentoo after all) "-O2 -fomit-frame-pointer -march=native", so quite standard. The e-mail contains two parts, one is text/html, and the other is a pdf attachment. 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 0x7f5f8b57da40 (LWP 35527))] Thread 71 (Thread 0x7f5eae7fc700 (LWP 50226)): #0 0x7f5f9b05ed2d in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5f94e18f66 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x2e3b0450 in () #3 0x000553ec in () #4 0x2e3b1008 in () #5 0x in () Thread 70 (Thread 0x7f5db4b68700 (LWP 36127)): #0 0x7f5f9bfc7a6b in poll () at /lib64/libc.so.6 #1 0x7f5f9a65017e in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #2 0x7f5f9a65029f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f5f9c60d2eb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f5f9c5b5c1b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f5f9c400fde in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f5f9c40202f in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #7 0x7f5f9b057427 in start_thread () at /lib64/libpthread.so.0 #8 0x7f5f9bfd3d5f in clone () at /lib64/libc.so.6 Thread 69 (Thread 0x7f5db6ffd700 (LWP 35693)): #0 0x7f5f9b05e9f7 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5f8912b68b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f5f8912b297 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f5f9b057427 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5f9bfd3d5f in clone () at /lib64/libc.so.6 Thread 68 (Thread 0x7f5db77fe700 (LWP 35692)): #0 0x7f5f9b05e9f7 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5f8912b68b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f5f8912b297 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f5f9b057427 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5f9bfd3d5f in clone () at /lib64/libc.so.6 Thread 67 (Thread 0x7f5db7fff700 (LWP 35691)): #0 0x7f5f9b05e9f7 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5f8912b68b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f5f8912b297 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f5f9b057427 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5f9bfd3d5f in clone () at /lib64/libc.so.6 Thread 66 (Thread 0x7f5dccba1700 (LWP 35690)): #0 0x7f5f9b05e9f7 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5f8912b68b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f5f8912b297 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f5f9b057427 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5f9bfd3d5f in clone () at /lib64/libc.so.6 Thread 65 (Thread 0x7f5dcd3a2700 (LWP 35689)): #0 0x7f5f9b05e9f7 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5f8912b68b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f5f8912b297 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f5f9b057427 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5f9bfd3d5f in clone () at /lib64/libc.so.6 Thread 64 (Thread 0x7f5dcdba3700 (LWP 35688)): #0 0x7f5f9b05e9f7 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5f8912b68b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f5f8912b297 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f5f9b057427 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5f9bfd3d5f in clone () at /lib64/libc.so.6 Thread 63 (Thread 0x7f5dce8d6700
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 --- Comment #2 from Jan-Matthias Braun <jan_br...@gmx.net> --- For another account using SMTP, I am seeing another error in the notification widget. Instead of getting a "1", as for the original report, I am seeing "Serverfehler", the German translation of Server error, in the notification window, but unluckily no debug output in the terminal. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 --- Comment #1 from Jan-Matthias Braun <jan_br...@gmx.net> --- Further tests with another account revealed, that sending via the EWS resource works. So does sending via a local mail dispatcher, like ssmtp or nullmailer. Although akonadi/kmail2 seems to run into problems with sendmail compatibility issues of those. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added Severity|normal |grave -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] New: Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 Bug ID: 387926 Summary: Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1 Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Mail Dispatcher Agent Assignee: kdepim-bugs@kde.org Reporter: jan_br...@gmx.net Target Milestone: --- When trying to send an e-Mail since trying out the 17.12 pre-releases, I am unable to send e-Mails. In the official release, I have now recreated the SMTP but the problem persists, no mail gets out. The only debug message I am seeing after enabling diverse output in kdebugdialog5 is org.kde.pim.ksmtp: Socket error: 1 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 364670] kmail crash on search
https://bugs.kde.org/show_bug.cgi?id=364670
--- Comment #8 from Jan-Matthias Braun <jan_br...@gmx.net> ---
Created attachment 106677
--> https://bugs.kde.org/attachment.cgi?id=106677=edit
New crash information added by DrKonqi
kontact (5.5.3) using Qt 5.7.1
I was entering a search term in a mail folder. I am unsure if I have pressed
the enter button, but in general the procedure seems like the one layed out
above.
Distribution: Gentoo with standard buld flags ("-O2 -march=native").
-- Backtrace (Reduced):
#8 0x7f7fdef72cad in __gnu_cxx::__verbose_terminate_handler () at
/var/tmp/portage/sys-devel/gcc-6.3.0/work/gcc-6.3.0/libstdc++-v3/libsupc++/vterminate.cc:95
#9 0x7f7fdef70a16 in __cxxabiv1::__terminate (handler=) at
/var/tmp/portage/sys-devel/gcc-6.3.0/work/gcc-6.3.0/libstdc++-v3/libsupc++/eh_terminate.cc:47
#10 0x7f7fdef70a61 in std::terminate () at
/var/tmp/portage/sys-devel/gcc-6.3.0/work/gcc-6.3.0/libstdc++-v3/libsupc++/eh_terminate.cc:57
#11 0x7f7fdef70c79 in __cxxabiv1::__cxa_throw (obj=obj@entry=0x54eae90,
tinfo=0x7f7fdf0b2890 , dest=0x7f7fdef86cb0
<std::logic_error::~logic_error()>) at
/var/tmp/portage/sys-devel/gcc-6.3.0/work/gcc-6.3.0/libstdc++-v3/libsupc++/eh_throw.cc:87
#12 0x7f7fdef9b73f in std::__throw_logic_error (__s=0x7f7ed88afd28
"basic_string::_M_construct null not valid") at
/var/tmp/portage/sys-devel/gcc-6.3.0/work/gcc-6.3.0/libstdc++-v3/src/c++11/functexcept.cc:74
--
You are receiving this mail because:
You are the assignee for the bug.
[kontact] [Bug 364670] kmail crash on search
https://bugs.kde.org/show_bug.cgi?id=364670 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added CC||jan_br...@gmx.net -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367998] quick-search field does not receive some keys
https://bugs.kde.org/show_bug.cgi?id=367998 --- Comment #4 from Jan-Matthias Braun <jan_br...@gmx.net> --- (In reply to Jan-Matthias Braun from comment #3) > 2. Whenever I enter text into the search field, right after updating the > message list, the focus seems to go to the mail view, too. Of course, any > keystrokes won't go to the search field anymore. This is similar to the > original problem here and can be reproduced reliably without any folder > change. When there is no mail displayed in the message view, e.g., one of akonadi's i-m-not-serving-any-requests-periods, then the focus won't leave the search field. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case
https://bugs.kde.org/show_bug.cgi?id=222878 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added CC||jan_br...@gmx.net --- Comment #37 from Jan-Matthias Braun <jan_br...@gmx.net> --- And another (rather short) one for kontact 16.12.0 (gdb) bt #0 0x7f15af07199d in poll () from /lib64/libc.so.6 #1 0x7f15a8041266 in g_main_context_iterate.isra.42.lto_priv () from /usr/lib64/libglib-2.0.so.0 #2 0x7f15a7fc8a3c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f15acd8e7af in QEventDispatcherGlib::processEvents (this=0x1236fd0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7f15acd3a7ba in QEventLoop::exec (this=this@entry=0x7fffa171af30, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f15acd42bfd in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1261 #6 0x00404203 in main (argc=, argv=) at /var/tmp/portage/kde-apps/kontact-16.12.0/work/kontact-16.12.0/src/main.cpp:227 Cheers, Jan -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367998] quick-search field does not receive some keys
https://bugs.kde.org/show_bug.cgi?id=367998 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added CC||jan_br...@gmx.net --- Comment #3 from Jan-Matthias Braun <jan_br...@gmx.net> --- Hi! I am not sure, if this really is the same problem, but as I see it, I do see a general problem with the focus strategy. :-) 1. Whenever I select an e-Mail, the mail view is focused. This means, that actions like delete don't work anymore. Only when I select an e-Mail a second time, things are back to normal and the focus stays in the message list. 2. Whenever I enter text into the search field, right after updating the message list, the focus seems to go to the mail view, too. Of course, any keystrokes won't go to the search field anymore. This is similar to the original problem here and can be reproduced reliably without any folder change. The description of where the focus goes has been derived from ticking shift-tab until I was back at the search field. Assuming "Search Field" - "Message List" - "Message View" tab order. I.e., I went back and forth to see where the focus has ended up. My kde installation is up to date. I.e., kmail 16.12.0, plasma 5.8.5, and frameworks 5.29. The patch noted in Comment 1 is already applied, as far as I can see. I am not sure, when this started. Probably with the qtwebengine version? Does the mail view now focus itself? I really like kmail, so thanks for looking into this! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372022] kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.
https://bugs.kde.org/show_bug.cgi?id=372022 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #6 from Jan-Matthias Braun <jan_br...@gmx.net> --- (In reply to Jan-Matthias Braun from comment #5) > Update: I recompiled with "-fno-delete-null-pointer-checks -fno-lifetime-dse > -fno-schedule-insns2", but the crash still happens. Yeah, looks like I did not rccompile with these CFLAGS. Now I did and it looks quite a lot better. qtwebengine is still using wrong CFLAGS for gcc 6. :-( -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372022] kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.
https://bugs.kde.org/show_bug.cgi?id=372022 --- Comment #5 from Jan-Matthias Braun <jan_br...@gmx.net> --- Update: I recompiled with "-fno-delete-null-pointer-checks -fno-lifetime-dse -fno-schedule-insns2", but the crash still happens. Then I took a look at kdepim git and found at, that there is a KF5WebEngineViewerConfig in the works. So it looks like everything will change in git, right? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372022] kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.
https://bugs.kde.org/show_bug.cgi?id=372022 --- Comment #4 from Jan-Matthias Braun <jan_br...@gmx.net> --- In a side-note, the secondary crash happens when grabbing selected text: #0 0x7fffeedae224 in QtWebEngineCore::WebContentsAdapter::selectedText() const () from /usr/lib64/libQt5WebEngineCore.so.5 #1 0x760eb321 in QWebEnginePage::selectedText() const () from /usr/lib64/libQt5WebEngineWidgets.so.5 #2 0x760f8547 in QWebEngineView::selectedText() const () from /usr/lib64/libQt5WebEngineWidgets.so.5 #3 0x7fff027e5991 in MessageViewer::Viewer::selectedText() const (this=) at /var/tmp/portage/kde-apps/messagelib-16.08.2/work/messagelib-16.08.2/messageviewer/src/viewer/viewer.cpp:248 #4 0x7fff02e78600 in KMReaderWin::copyText() const (this=) at /var/tmp/portage/kde-apps/kmail-16.08.2/work/kdepim-16.08.2/kmail/src/kmreaderwin.cpp:399 #5 0x7fff02ed0508 in KMail::MessageActions::replyCommand (this=0x3bd4fc0, strategy=MessageComposer::ReplySmart) at /var/tmp/portage/kde-apps/kmail-16.08.2/work/kdepim-16.08.2/kmail/src/messageactions.cpp:477 #6 0x76ef3d1c in QtPrivate::QSlotObjectBase::call (a=0x7fffc930, r=0x3bd4fc0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:130 #7 QMetaObject::activate (sender=0x3bd0160, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3723 #8 0x77a4dea2 in QAction::triggered(bool) () from /usr/lib64/libQt5Widgets.so.5 #9 0x77a539ff in QAction::activate(QAction::ActionEvent) () from /usr/lib64/libQt5Widgets.so.5 #10 0x77a53aec in QAction::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #11 0x77a5c32c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #12 0x77a61739 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #13 0x76ec8f18 in QCoreApplication::notifyInternal2 (receiver=0x3bd0160, event=event@entry=0x7fffcc00) at kernel/qcoreapplication.cpp:988 #14 0x7723ef96 in QCoreApplication::sendEvent (event=0x7fffcc00, receiver=) at /usr/include/qt5/QtCore/qcoreapplication.h:231 #15 QShortcutMap::dispatchEvent (this=this@entry=0x449968, e=e@entry=0x7fffccb0) at kernel/qshortcutmap.cpp:674 #16 0x7723f069 in QShortcutMap::tryShortcut (this=this@entry=0x449968, e=e@entry=0x7fffccb0) at kernel/qshortcutmap.cpp:351 #17 0x771fad5f in QWindowSystemInterface::handleShortcutEvent (window=, window@entry=0xca8120, timestamp=, keyCode=82, modifiers=..., nativeScanCode=27, nativeVirtualKey=114, nativeModifiers=0, text=..., autorepeat=false, count=1) at kernel/qwindowsysteminterface.cpp:235 #18 0x77210fcc in QGuiApplicationPrivate::processKeyEvent (e=0x419f800) at kernel/qguiapplication.cpp:2008 #19 0x77216285 in QGuiApplicationPrivate::processWindowSystemEvent (e=e@entry=0x419f800) at kernel/qguiapplication.cpp:1699 #20 0x771f596b in QWindowSystemInterface::sendWindowSystemEvents (flags=...) at kernel/qwindowsysteminterface.cpp:654 #21 0x7fffe7a26900 in userEventSourceDispatch (source=) at eventdispatchers/qeventdispatcher_glib.cpp:76 #22 0x74a6bd17 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #23 0x74a6c788 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #24 0x74a6c91c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #25 0x76f1aeef in QEventDispatcherGlib::processEvents (this=0x4bb6d0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #26 0x76ec704a in QEventLoop::exec (this=this@entry=0x7fffd010, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #27 0x76ecf48d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1261 #28 0x004042c3 iat /var/tmp/portage/kde-apps/kontact-16.08.2/work/kdepim-16.08.2/kontact/src/main.cpp:223 n main (argc=, argv=) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372022] kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.
https://bugs.kde.org/show_bug.cgi?id=372022 --- Comment #3 from Jan-Matthias Braun <jan_br...@gmx.net> --- Looking at the stack trace again, I just remembered that v8 has problems with gcc 6 due to programming practices. I am recompiling qtwebengine with appropriate compiler flags to check if this is the underlying problem here... -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372022] kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.
https://bugs.kde.org/show_bug.cgi?id=372022 --- Comment #2 from Jan-Matthias Braun <jan_br...@gmx.net> --- Sorry for being incoherent: I am using qt 5.7.0, plasma 5.8.3, kde apps 16.08.2, and frameworks 5.27. The compiler is gcc 6.2.0. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372022] kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.
https://bugs.kde.org/show_bug.cgi?id=372022 --- Comment #1 from Jan-Matthias Braun <jan_br...@gmx.net> --- Side note: For all messages I see this error message in the logs: js: Uncaught ReferenceError: qt is not defined js: Uncaught ReferenceError: qt is not defined js: Uncaught ReferenceError: qt is not defined but it does not seem to interrupt kmail. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372022] New: kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.
https://bugs.kde.org/show_bug.cgi?id=372022 Bug ID: 372022 Summary: kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2. Product: kmail2 Version: 5.3.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: jan_br...@gmx.net Target Milestone: --- When selecting a mail in message view, the message is displayed and then disappears after a variable delay. Changing to another mail and then back does not triggering this behaviour. The disappearing message happens in the embedded message view as well as in an extra window (after double clicking the message). If the mail display is blank and I trigger any message related, e.g., reply, forward, delete, kmail crashes. But if I redisplay the message and do the same action while the display is intact, everything will work fine. Nonetheless, this mail focuses on the disappearing of the displayed mail. I see the following backtrace, which seems to lead into the depths of QtWebEngine. Received signal 11 SEGV_MAPERR 0008 #0 0x74cb3b3e base::debug::StackTrace::StackTrace() #1 0x74cb3c2b base::debug::(anonymous namespace)::StackDumpSignalHandler() #2 0x722cc2b0 #3 0x733785b0 v8::internal::IncrementalMarking::ActivateIncrementalWriteBarrier() #4 0x733787e7 v8::internal::IncrementalMarking::StartMarking() #5 0x73378943 v8::internal::IncrementalMarking::Start() #6 0x7368ac9f v8::internal::MemoryReducer::TimerTask::RunInternal() #7 0x74d46869 base::debug::TaskAnnotator::RunTask() #8 0x7541b323 scheduler::TaskQueueManager::ProcessTaskFromWorkQueue() #9 0x7541bda0 scheduler::TaskQueueManager::DoWork() #10 0x74d46869 base::debug::TaskAnnotator::RunTask() #11 0x74cd79d5 base::MessageLoop::RunTask() #12 0x74cd99ab base::MessageLoop::DoDelayedWork() #13 0x74cdaaaf base::MessagePumpDefault::Run() #14 0x74cefffd base::RunLoop::Run() #15 0x74cd6f65 base::MessageLoop::Run() #16 0x74a07baf content::RendererMain() #17 0x73dc4cdb content::RunZygote() #18 0x73dc5034 content::ContentMainRunnerImpl::Run() #19 0x73dc34e1 content::ContentMain() #20 0x7311d514 QtWebEngine::processMain() #21 0x00400703 main #22 0x722b9681 __libc_start_main #23 0x00400749 _start What additional information can I provide? Jan -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 371859] Segfault of kmail when removing a mail
https://bugs.kde.org/show_bug.cgi?id=371859 --- Comment #3 from Jan-Matthias Braun <jan_br...@gmx.net> --- (In reply to Michael.Calmer from comment #2) > (In reply to Jan-Matthias Braun from comment #1) > > I do have a question. I am experiencing problems with current QtWebEngine > > based kmail too: Sometimes, the mail display will become empty after a short > > delay. Changing to another mail and then back has a slight chance of not > > triggering this behaviour. If the mail display is blank and I trigger any > > message related, e.g., reply, forward, delete, kmail crashes. > > My crash happens not only while removing a mail. action, I wanted to write: any nessage releted action. ^^ > > But if I redisplay the message and do the same action while the display is > > intact, everything will work fine. > > Well, I cannot make the message visible. "redisplay" is not really working > for me. So you never see the message? I can at least see it shortly before it vanishes... > > Do you observe similar behaviour? Or should I file a new bug. > > Sounds a bit similar to what I see. > > > My backtrace hints to QtWebEngine. But unfortunately, I am using > > self-compiled qt 5.7 and the debug build for QtWebEngine is exhausting my > > disk space, i.e., my backtrace is worthless. > > I also saw other bugreports which point to this component together with the > use of the "nouveau" driver. I am using an up-to-date proprietary nvidia driver. I will try to get some useful debug information. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 371859] Segfault of kmail when removing a mail
https://bugs.kde.org/show_bug.cgi?id=371859 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added CC||jan_br...@gmx.net --- Comment #1 from Jan-Matthias Braun <jan_br...@gmx.net> --- Hi Michael, I do have a question. I am experiencing problems with current QtWebEngine based kmail too: Sometimes, the mail display will become empty after a short delay. Changing to another mail and then back has a slight chance of not triggering this behaviour. If the mail display is blank and I trigger any message related, e.g., reply, forward, delete, kmail crashes. But if I redisplay the message and do the same action while the display is intact, everything will work fine. Do you observe similar behaviour? Or should I file a new bug. My backtrace hints to QtWebEngine. But unfortunately, I am using self-compiled qt 5.7 and the debug build for QtWebEngine is exhausting my disk space, i.e., my backtrace is worthless. Cheers, Jan -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 363741] akonadi server 16.04.2: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 --- Comment #13 from Jan-Matthias Braun <jan_br...@gmx.net> --- it looks like my problem is somehow related to akonadi/kmail producing and not coping with invalid xapian searches. Right now, I have not seen another akonadi crash. The search that was crashing akonadi had a debug output representation (using the qdebug overload of operator << on term()) over half a screen, i.e., many lines with many many columns. I have no Idea where it came from -- and now it is gone. -- 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 363741] akonadi server 16.04.2: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 --- Comment #12 from Jan-Matthias Braun <jan_br...@gmx.net> --- Okay, I was able to remove a very reproducible crash (with the above mentioned segfault) during startup of akonadi (without any client running) by removing a search from the search folder in kmail. Since then, it is running for at least eight minutes (!) now and I haven't seen a SEGV up to now. By the way, is it normal, that different searches have the same name? In the logs I am seeing the Executing search "foo-1186278907-bar" lines. And the crashing search had the same name, as the search running before, which was much, much simpler. And checking now I see, that different searches often have the same search name in the logs, although from time to time the name seems to change. Revisiting older logs, the crash always happend with a reused search-name. But I cannot tell if it was the same search, always, because only now I went to instrument the code around the backtrace end in the akonadi-search code (xapian/xapiansearchstore.cpp:177) with lots of output. -- 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 363741] akonadi server 16.04.1: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 --- Comment #11 from Jan-Matthias Braun <jan_br...@gmx.net> --- I do see the same backtrace for xapian 1.3.7. -- 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 363741] akonadi server 16.04.1: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 --- Comment #10 from Jan-Matthias Braun <jan_br...@gmx.net> --- Ok, I have seen this one three times in a row, now, -- 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 363741] akonadi server 16.04.1: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 --- Comment #9 from Jan-Matthias Braun <jan_br...@gmx.net> --- Connecting into the running process indeed provides a better backtrace, although -- why? :-) Here it is: #0 0x in ?? () #1 0x7f6ef42d333b in ExternalPostList::ExternalPostList (this=0x7f6f0835a170, db=..., source_=, factor_=, matcher=0x7f6f137fcd30) at matcher/externalpostlist.cc:40 #2 0x7f6ef41e6d6b in Xapian::Internal::QueryPostingSource::postlist (this=, qopt=0x7f6f137fc650, factor=1) at api/queryinternal.cc:739 #3 0x7f6ef41e50a1 in Xapian::Query::Internal::postlist_sub_xor (this=, ctx=..., qopt=, factor=) at api/queryinternal.cc:634 #4 0x7f6ef41e6553 in Xapian::Internal::QueryBranch::do_or_like (this=this@entry=0x7f6f0807b490, ctx=..., qopt=qopt@entry=0x7f6f137fc650, factor=factor@entry=1, elite_set_size=elite_set_size@entry=0, first=first@entry=1) at api/queryinternal.cc:1186 #5 0x7f6ef41e6b1a in Xapian::Internal::QueryAndMaybe::postlist (this=0x7f6f0807b490, qopt=0x7f6f137fc650, factor=1) at api/queryinternal.cc:1550 #6 0x7f6ef42d35fa in LocalSubMatch::get_postlist (this=0x7f6f0807af50, matcher=0x7f6f137fcd30, total_subqs_ptr=0x7f6f137fc7bc) at matcher/localsubmatch.cc:204 #7 0x7f6ef42d9a51 in MultiMatch::get_mset (this=this@entry=0x7f6f137fcd30, first=first@entry=0, maxitems=10, check_at_least=check_at_least@entry=10, mset=..., stats=..., mdecider=0x0, sorter=0x0) at matcher/multimatch.cc:419 #8 0x7f6ef41d55e1 in Xapian::Enquire::Internal::get_mset (this=0x7f6f0807ad10, first=, maxitems=, check_at_least=, check_at_least@entry=0, rset=rset@entry=0x0, mdecider=0x0) at api/omenquire.cc:548 #9 0x7f6ef41d5924 in Xapian::Enquire::get_mset (this=this@entry=0x7f6f137fd050, first=, maxitems=, check_at_least=check_at_least@entry=0, rset=rset@entry=0x0, mdecider=0x0) at api/omenquire.cc:906 #10 0x7f6ee05e968d in Akonadi::Search::XapianSearchStore::exec (this=0x7f6ef009bf50, query=...) at /var/tmp/portage/kde-apps/akonadi-search-16.04.49./work/akonadi-search-16.04.49./xapian/xapiansearchstore.cpp:177 #11 0x7f6f12df8065 in Akonadi::Search::Query::exec (this=this@entry=0x7f6f137fd2c0) at /var/tmp/portage/kde-apps/akonadi-search-16.04.49./work/akonadi-search-16.04.49./core/query.cpp:252 #12 0x7f6f180fff7d in SearchPlugin::search (this=, akonadiQuery=..., collections=..., mimeTypes=...) at /var/tmp/portage/kde-apps/akonadi-search-16.04.49./work/akonadi-search-16.04.49./akonadiplugin/searchplugin.cpp:348 #13 0x0055b4eb in Akonadi::Server::SearchRequest::searchPlugins (this=this@entry=0x7f6f137fd900) at /var/tmp/portage/kde-apps/akonadi-16.04.49./work/akonadi-16.04.49./src/server/search/searchrequest.cpp:112 #14 0x0055b893 in Akonadi::Server::SearchRequest::exec (this=this@entry=0x7f6f137fd900) at /var/tmp/portage/kde-apps/akonadi-16.04.49./work/akonadi-16.04.49./src/server/search/searchrequest.cpp:123 #15 0x00444788 in Akonadi::Server::SearchManager::updateSearchImpl (this=0x27003f0, collection=..., cond=) at /var/tmp/portage/kde-apps/akonadi-16.04.49./work/akonadi-16.04.49./src/server/search/searchmanager.cpp:350 #16 0x7f6f1f8deaa9 in QObject::event (this=0x27003f0, e=) at kernel/qobject.cpp:1263 #17 0x7f6f1f8b2b5b in doNotify (event=0x7f6f08031ea0, receiver=0x27003f0) at kernel/qcoreapplication.cpp:1063 #18 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1049 #19 QCoreApplication::notifyInternal2 (receiver=0x27003f0, event=event@entry=0x7f6f08031ea0) at kernel/qcoreapplication.cpp:988 #20 0x7f6f1f8b526b in QCoreApplication::sendEvent (event=0x7f6f08031ea0, receiver=) at kernel/qcoreapplication.h:231 #21 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x2700600) at kernel/qcoreapplication.cpp:1649 #22 0x7f6f1f8b56d8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1503 #23 0x7f6f1f9063f3 in postEventSourceDispatch (s=0x7f6f080012d0) at kernel/qeventdispatcher_glib.cpp:276 #24 0x7f6f1dd2eb17 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #25 0x7f6f1dd2f4f8 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #26 0x7f6f1dd2f68c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #27 0x7f6f1f9067ff in QEventDispatcherGlib::processEvents (this=0x7f6f080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #28 0x7f6f1f8b0b1a in QEventLoop::exec (this=this@entry=0x7f6f137fde80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #29 0x7f6f1f6d2214 in QThread::exec (this=) at thread/qthread.cpp:507 #30 0x7f6f1f6d6e78 in QThreadPrivate::start (arg=0x27004c0) at thread/qthread_unix.cpp:344 #31 0x7f6f1e
[Akonadi] [Bug 363741] akonadi server 16.04.1: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added CC||jan_br...@gmx.net --- Comment #8 from Jan-Matthias Braun <jan_br...@gmx.net> --- Hi! I am seeing similar behaviour since 16.04.x, and checked up to 16.04.2 and 16.04-git. I am using qt 5.7, xapian 1.4, frameworks 5.23, and mariadb 10.1.14 on gentoo, too. One of my backtraces looks like this and is only partially usable: 0: akonadiserver() [0x4ac960] 1: akonadiserver() [0x4acc5f] 2: /lib64/libc.so.6(+0x33250) [0x7f025e5b3250] 3: /usr/lib64/libxapian.so.30(+0x1b2508) [0x7f0248531508] 4: /usr/lib64/libxapian.so.30(+0x7554b) [0x7f02483f454b] 5: /usr/lib64/libxapian.so.30(_ZNK6Xapian5Query8Internal20postlist_sub_or_likeERNS_8Internal9OrContextEP14QueryOptimiserd+0x21) [0x7f02483f1e21] 6: /usr/lib64/libxapian.so.30(+0x745a3) [0x7f02483f35a3] 7: /usr/lib64/libxapian.so.30(+0x74e1a) [0x7f02483f3e1a] 8: /usr/lib64/libxapian.so.30(+0x1b266a) [0x7f024853166a] 9: /usr/lib64/libxapian.so.30(+0x1c2991) [0x7f0248541991] 10: /usr/lib64/libxapian.so.30(_ZNK6Xapian7Enquire8Internal8get_msetEjjjPKNS_4RSetEPKNS_12MatchDeciderE+0x1c1) [0x7f02483dd8f1] 11: /usr/lib64/libxapian.so.30(_ZNK6Xapian7Enquire8get_msetEjjjPKNS_4RSetEPKNS_12MatchDeciderE+0x24) [0x7f02483ddc34] 12: /usr/lib64/libKF5AkonadiSearchXapian.so.5(_ZN7Akonadi6Search17XapianSearchStore4execERKNS0_5QueryE+0x8b6) [0x7f02481725d6] 13: /usr/lib64/libKF5AkonadiSearchCore.so.5(_ZN7Akonadi6Search5Query4execEv+0x245) [0x7f0258235a55] 14: /usr/lib64/qt5/plugins/akonadi/akonadi_search_plugin.so(+0x400c) [0x7f025844000c] 15: akonadiserver() [0x4cba6f] 16: akonadiserver() [0x44aaa8] 17: akonadiserver() [0x4835d0] 18: /usr/lib64/libQt5Core.so.5(_ZN7QObject5eventEP6QEvent+0xe9) [0x7f025e085aa9] 19: /usr/lib64/libQt5Core.so.5(_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent+0xfb) [0x7f025e059b5b] 20: /usr/lib64/libQt5Core.so.5(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x2db) [0x7f025e05c26b] 21: /usr/lib64/libQt5Core.so.5(+0x2de3f3) [0x7f025e0ad3f3] 22: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x297) [0x7f025c86eb17] 23: /usr/lib64/libglib-2.0.so.0(+0x294f8) [0x7f025c86f4f8] 24: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f025c86f68c] 25: /usr/lib64/libQt5Core.so.5(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x5f) [0x7f025e0ad7ff] 26: /usr/lib64/libQt5Core.so.5(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xfa) [0x7f025e057b1a] 27: /usr/lib64/libQt5Core.so.5(_ZN7QThread4execEv+0xb4) [0x7f025de79214] 28: /usr/lib64/libQt5Core.so.5(+0xaee78) [0x7f025de7de78] 29: /lib64/libpthread.so.0(+0x7434) [0x7f025d99c434] 30: /lib64/libc.so.6(clone+0x6d) [0x7f025e667ded] Now I have installed all debug symbols, but now I can only see mini-backtraces with even less information: 0: akonadiserver() [0x572666] 1: akonadiserver() [0x572982] 2: /lib64/libc.so.6(+0x33250) [0x7fa0e1fe9250] which leaves me at a loss for useful info. (I am not even getting dr konqi, I have to grab the debug info from the akonadi logs.) I am using a bunch of imap-servers including one akonadi-ews account. I have contacts and calendars in owncloud. These seem to get disabled all the while. What can I do to improve debugging information? Cheers, Jan -- 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 351814] Kmail 15.08 will not sync Outlook365 IMAP Folders
https://bugs.kde.org/show_bug.cgi?id=351814 --- Comment #28 from Jan-Matthias Braun <jan_br...@gmx.net> --- Okay, I think I have answered my own question: It is there and therefore I should better open a new but. Please excuse the noise... :-/ -- 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 351814] Kmail 15.08 will not sync Outlook365 IMAP Folders
https://bugs.kde.org/show_bug.cgi?id=351814 --- Comment #27 from Jan-Matthias Braun <jan_br...@gmx.net> --- Hi! I do have the impression that this issue came back with 15.12.: My outlook imap is not syncing anymore. Does somebody else see the same behaviour? Can the fix somehow have evaded going into 15.12 or should I open a new bug report? All the best, Jan -- 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 351814] Kmail 15.08 will not sync Outlook365 IMAP Folders
https://bugs.kde.org/show_bug.cgi?id=351814 --- Comment #17 from Jan-Matthias Braun <jan_br...@gmx.net> --- Hi! (In reply to jat255 from comment #16) > (In reply to Jan-Matthias Braun from comment #7) [...] > This sounds like you may want to open another bug report. To keep this one > clean, it would probably be best to keep it to people whose IMAP folders are > not getting updated at all. Actually, I am not convinced that these are two distinct behaviours. For the first, the imap-logs seem to be the same as in the original report, i.e., I would suspect a higher load of the corresponding resource for all these cases, at least it seems to be logging activity all the time. For the second---as an update, my INBOX right now hasn't been updated since 23rd of September, the resource being online and working all the while. This makes every update a stochastic event at best and the time lag has jumped from almost daily over after three days to not in all since 23rd of September. In other words, there is no reliable working component, but the symptoms seem similar, which makes it seem that I sometimes get lucky for small folders with 1-3 (!) e-Mails in them. > On another note, has anyone from the kmail team seen/commented on this bug? > There seem to be a lot people willing to help diagnose the problem, but very > few suggestions at this point. As Orion noted, this is a showstopper and I > have completely stopped using kmail because it is useless to me under > plasma. I wonder if there's a better way to get the devs' attention? Probably irc? I don't know and won't have time to check for a little longer. All the best and good luck, Jan -- 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
[kimap] [Bug 351814] Kmail 15.08 will not sync Outlook365 IMAP Folders
https://bugs.kde.org/show_bug.cgi?id=351814 --- Comment #22 from Jan-Matthias Braun <jan_br...@gmx.net> --- Whatever---it works! Thank you very much Daniel! All the best, Jan -- 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 351814] Kmail 15.08 will not sync Outlook365 IMAP Folders
https://bugs.kde.org/show_bug.cgi?id=351814 --- Comment #13 from Jan-Matthias Braun <jan_br...@gmx.net> --- The funny thing is, that smaller folders, like the Junk-Mail-Folder, updates occur. The inbox folder is quite huge, so I tried to move two years worth of e-Mails, but this action never got synced and probably made things only worse. -- 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 351814] Kmail 15.08 will not sync Outlook365 IMAP Folders
https://bugs.kde.org/show_bug.cgi?id=351814 --- Comment #12 from Jan-Matthias Braun <jan_br...@gmx.net> --- Hi, I cannot tell for bug #351993, as I am only experiencing this problem with our corporate exchange server. All other accounts are working flawlessly and respond fast. The same goes for bug #352701 -- this is a very localised one resource-only problem for me. For this exchange server imap idle never really seemed to have worked and now fetching mails seems to be stuck with some demanding operation which never seems to end. So I guess there is a general problem with the exchange server. -- 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 351395] kmail 4.81beta1 crashes when opening the composer window
https://bugs.kde.org/show_bug.cgi?id=351395 --- Comment #9 from Jan-Matthias Braun <jan_br...@gmx.net> --- So, I got it! I don't know how but I used the heuristic approach to track the offender. As the crash happens in slotEditorTextChanged I moved the connect back in the constructor, as is was obviously too early to work when not replying to anything. This worked out and then I just invested the 5 minutes to find the earliest non-offending position in the constructor, which is exactly after the call to readConfig() (and before setupStatusBar(...)). I hope this helps someone who actually knows what is happening. The patch I am going to attach now has the connect a hand full of lines later, as there are a lot of connects already so I think it is fitting. Honestly, it doesn't crash right now so I am happy. :-) -- 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 351395] kmail 4.81beta1 crashes when opening the composer window
https://bugs.kde.org/show_bug.cgi?id=351395 --- Comment #10 from Jan-Matthias Braun <jan_br...@gmx.net> --- Created attachment 94740 --> https://bugs.kde.org/attachment.cgi?id=94740=edit Moved the connect of the crashing slot back in code, so it could complete and the window opens. -- 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 351395] kmail 4.81beta1 crashes when opening the composer window
https://bugs.kde.org/show_bug.cgi?id=351395 --- Comment #11 from Jan-Matthias Braun <jan_br...@gmx.net> --- Created attachment 94741 --> https://bugs.kde.org/attachment.cgi?id=94741=edit Similar patch, using the new api for KMComposerEditorNg. Caution! I don't know what I am doing, but it is not crashing on hitting "new mail". :-) Just the same thing, but this time I used the new api after renaming the class and removing the comment and the old connect statement. -- 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 351395] kmail 15.08.1 crashes when opening the composer window
https://bugs.kde.org/show_bug.cgi?id=351395 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added Summary|kmail 4.81beta1 crashes |kmail 15.08.1 crashes when |when opening the composer |opening the composer window |window | -- 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 351395] kmail 15.08.1 crashes when opening the composer window
https://bugs.kde.org/show_bug.cgi?id=351395 --- Comment #12 from Jan-Matthias Braun <jan_br...@gmx.net> --- On a side note: The crash in slotEditorTextChanged() depended on the local bool textIsNotEmpty = !mComposerBase->editor()->document()->isEmpty(); The crash happend directly in the next call to mFindText->setEnabled(textIsNotEmpty); In my testing, the boolean condition was opposite when hitting reply and when hitting new message and only in the latter case it crashed in the call to setEnabled(...). -- 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 351814] Kmail 15.08 will not sync Outlook365 IMAP Folders
https://bugs.kde.org/show_bug.cgi?id=351814 --- Comment #11 from Jan-Matthias Braun <jan_br...@gmx.net> --- Another observation is, that the corresponding akondi_imap_resource is quite CPU-demanding; most of the time with around 15 % on my system. The Outlook resource is at 50 minutes compute time right now, in comparison to below 10 seconds for my three other resources. Nonetheless, I won't see new mails for days. Today (Wednesday) I saw the first update since Friday. The outlook resource has always been a bit slower with updates than the others, but only with the current version I am seeing no updates at all. Is there any specific diagnostic I can run? For example to better understand the imap logs? -- 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 351515] Akonadi-Resource 15.08 (&15.07.90) crash in background (probably while checking mails)
https://bugs.kde.org/show_bug.cgi?id=351515 --- Comment #3 from Jan-Matthias Braun <jan_br...@gmx.net> --- I am unsure, if this possibly is something like an updated version of bug #341860 . -- 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 345748] IMAP Crash Checking Gmail
https://bugs.kde.org/show_bug.cgi?id=345748 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added CC||jan_br...@gmx.net --- Comment #3 from Jan-Matthias Braun <jan_br...@gmx.net> --- Could be a duplicate of 341860 -- 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 341860] akonadi_imap_resource (4.14) segfault
https://bugs.kde.org/show_bug.cgi?id=341860 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added CC||jan_br...@gmx.net --- Comment #4 from Jan-Matthias Braun <jan_br...@gmx.net> --- Looks like bug #345748 is a duplicate and my bug #351515 could be the current state of the same bug. I don't know the code, but from the backtrace they both seem to trigger after receiving something. I know this is a hand-waving argument. -- 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 351515] Akonadi-Resource 15.08 (&15.07.90) crash in background (probably while checking mails)
https://bugs.kde.org/show_bug.cgi?id=351515 --- Comment #2 from Jan-Matthias Braun <jan_br...@gmx.net> --- I watched the situation and found out, that from 4 resources, only the gmail imap resource is crashing. -- 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 351814] Kmail 15.08 will not sync Outlook365 IMAP Folders
https://bugs.kde.org/show_bug.cgi?id=351814 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added CC||jan_br...@gmx.net --- Comment #7 from Jan-Matthias Braun <jan_br...@gmx.net> --- Hi! I am using kde-apps 15.08.1 version of kmail and I am having problems with an Exchange 2010 system, afaik. Nonetheless the symptoms are similar. Sometimes I am getting my INBOX updated, but most of the day not. I cannot even reproduce the update reliably. Stopping akonadi and restarting kmail won't work. I too am seeing this endless sequence in my imap-log: ... S: * SEARCH S: A032761 OK SEARCH completed. C: A032762 UID SEARCH UID 65508001:6551 S: * SEARCH S: A032762 OK SEARCH completed. C: A032763 UID SEARCH UID 65510001:65512000 ... and so on and on. In my .xsession-errors I got the impression, that it actually gets the new mails and feeds them to the indexer: Wrote 19189 bytes to ".../.local/share/akonadi/file_db_data/992243_r0" log_akonadi_indexer_agent: indexed 126 akonadiagentbase_log: 2837 log_akonadi_indexer_agent: Processing collection: 126 log_akonadi_indexer_agent: log_akonadi_indexer_agent: Indexing Valid new e-Mail 1 log_akonadi_indexer_agent: Indexing Valid new e-Mail 2 log_akonadi_indexer_agent: Indexing Valid new e-Mail 3 log_akonadi_indexer_agent: Indexing Valid new e-Mail 4 log_akonadi_indexer_agent: Indexing Valid new e-Mail 5 log_akonadi_indexer_agent: Indexed 5 items in (ms): 23 log_akonadi_indexer_agent: Indexing complete. Total time: 25 log_akonadi_indexer_agent: indexed 127 log_akonadi_indexer_agent: Processing collection: 127 log_akonadi_indexer_agent: log_akonadi_indexer_agent: Indexing Valid new e-Mail 1 log_akonadi_indexer_agent: Indexing Valid new e-Mail 2 log_akonadi_indexer_agent: Indexing Valid new e-Mail 3 log_akonadi_indexer_agent: Indexed 3 items in (ms): 13 log_akonadi_indexer_agent: Indexing complete. Total time: 15 log_akonadi_indexer_agent: Processing done All those e-Mail-Subjects are new and not in my inbox. For at least half a dozen akonadi restarts I was only seeing them once. So, different exchange server version, similar output and it looks like the new mails are indexed. But I am getting only around one INBOX update a day. All other accounts are working flawlessly. What can I do to help? All the best, Jan -- 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 351814] Kmail 15.08 will not sync Outlook365 IMAP Folders
https://bugs.kde.org/show_bug.cgi?id=351814 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #8 from Jan-Matthias Braun <jan_br...@gmx.net> --- *** This bug has been confirmed by popular vote. *** -- 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 351395] kmail 4.81beta1 crashes when opening the composer window
https://bugs.kde.org/show_bug.cgi?id=351395 --- Comment #4 from Jan-Matthias Braun <jan_br...@gmx.net> --- Seems reasonable, the description matches and I see similar output in .xsession-errors: log_templateparser: Identity found: 824152080 log_messageviewer: Node UNprocessed: 0x54bdb40 log_messageviewer: SET NODE: 0x54bdb40 true log_messageviewer: Node processed: "" "Content-Type: text/plain; charset=\"utf-8\"" log_templateparser: Command: REM= log_templateparser: Command: - log_templateparser: Command: BLANK log_templateparser: No appropriate charset found. log_messagecomposer: initalising autosave QObject::connect: Cannot connect MessageComposer::RecipientLineNG::addRecipient(RecipientLineNG*,QString) to (null)::addRecipient(RecipientLineNG*,QString) log_kmail: log_kmail: "kki" *** KMail got signal 11 (Exiting) log_kmail: current item 0 "Standard" log_messagecomposer: Plain text log_messagecomposer: Autosaving message log_messagecomposer: Chosen charset "iso-8859-1" log_messagecomposer: Done. log_messagecomposer: Making text/plain log_messagecomposer: Calling process. log_messagecomposer: Settled on encoding "quoted-printable" log_messagecomposer: A subjob finished. 0 more to go. log_messagecomposer: Calling process. log_messagecomposer: composing final message log_messagecomposer: NoError. log_messagecomposer: Writing message to disk as ... -- 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 351395] kmail 4.81beta1 crashes when opening the composer window
https://bugs.kde.org/show_bug.cgi?id=351395 --- Comment #6 from Jan-Matthias Braun <jan_br...@gmx.net> --- To get the backtrace, you can start kmail with gdb from a command-line, e.g., "gdb kmail" in konsole will do. Then type "run", to get kmail running, and when it crashes, you can type "back" to get the backtrace. You may need to install gdb manually. For the log: this is just the regular output. Start kmail from a command-line and this is what will be printed in the terminal window. When starting kmail from KDE this is hidden, but will typically be redirected to the file .xsession-errors in your home-directory, where you will find it. But actually already my two backtraces end at the same point. So you probably better check, if it really brings up new information. And right now am lacking time to help in fixing this, besides lacking the experience with kmail sources etc... :-( -- 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 351395] kmail 4.81beta1 crashes when opening the composer window
https://bugs.kde.org/show_bug.cgi?id=351395 --- Comment #7 from Jan-Matthias Braun <jan_br...@gmx.net> --- (In reply to Rajeev Bhatta from comment #5) > May be related so adding a comment here instead of opening another ticket. > > On the same version 4.81 Beta 1, I experienced Kmail to crash multiple times > when trying to work with moving folders around. > > If you can let me know how to generate the log will provide that too to > help.. I am a bit slow right now. I would not expect this to be a similar bug. My crash happens directly in the composer window code and this should not be involved in any kind when moving folders around. Check the backtrace if it includes lines with KMComposeWin::... , but I would guess not. -- 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 351395] kmail 4.81beta1 crashes when opening the composer window
https://bugs.kde.org/show_bug.cgi?id=351395 --- Comment #2 from Jan-Matthias Braun jan_br...@gmx.net --- Even when not closing the composer window, which was restored from a previous run, later I cannot open a new composer window. And kontact just crashes when clicking on an e-Mail address in a header or body of an e-Mail. The following backtrace was created with gdb in the latter case. Program received signal SIGSEGV, Segmentation fault. 0x77a81b55 in QAction::setEnabled(bool) () from /usr/lib64/libQt5Widgets.so.5 (gdb) back #0 0x77a81b55 in QAction::setEnabled(bool) () from /usr/lib64/libQt5Widgets.so.5 #1 0x7fff8b9780c9 in KMComposeWin::slotEditorTextChanged (this=0x5995f00) at /var/tmp/portage/kde-apps/kdepim-15.08.0/work/kdepim-15.08.0/kmail/editor/kmcomposewin.cpp:535 #2 0x7fff8b9c19db in KMComposeWin::qt_static_metacall (_o=optimized out, _c=optimized out, _id=optimized out, _a=optimized out) at /var/tmp/portage/kde-apps/kdepim-15.08.0/work/kdepim-15.08.0_build/kmail/moc_kmcomposewin.cpp:485 #3 0x76ea6fb1 in QMetaObject::activate (sender=0x59faaf0, signalOffset=optimized out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3718 #4 0x778cce95 in QTextEdit::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib64/libQt5Widgets.so.5 #5 0x76ea6fb1 in QMetaObject::activate (sender=0x59e9400, signalOffset=optimized out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3718 #6 0x778928dd in QWidgetTextControl::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib64/libQt5Widgets.so.5 #7 0x77892c8b in QWidgetTextControl::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQt5Widgets.so.5 #8 0x76ea70b4 in QMetaObject::activate (sender=sender@entry=0x59e9420, signalOffset=optimized out, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3733 #9 0x76ea7667 in QMetaObject::activate (sender=sender@entry=0x59e9420, m=m@entry=0x7760fae0 QTextDocument::staticMetaObject, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3583 #10 0x77546a43 in QTextDocument::contentsChanged (this=this@entry=0x59e9420) at .moc/moc_qtextdocument.cpp:378 #11 0x772d7442 in contentsChanged (this=0x59e95a0) at text/qtextdocument_p.cpp:1646 #12 QTextDocumentPrivate::finishEdit (this=0x59e95a0) at text/qtextdocument_p.cpp:1238 #13 0x772d786c in QTextDocumentPrivate::endEditBlock (this=optimized out) at text/qtextdocument_p.cpp:1193 #14 0x772d794e in QTextDocumentPrivate::endEditBlock (this=optimized out) at text/qtextdocument_p.cpp:1179 #15 0x7731c22d in rehighlight (operation=QTextCursor::End, cursor=..., this=0x59e9e60) at text/qsyntaxhighlighter.cpp:69 #16 QSyntaxHighlighter::rehighlight (this=optimized out) at text/qsyntaxhighlighter.cpp:368 #17 0x7fff8be8544d in PimCommon::RichTextEditor::setSpellCheckingLanguage (this=0x59faaf0, _language=...) at /var/tmp/portage/kde-apps/kdepim-15.08.0/work/kdepim-15.08.0/pimcommon/texteditor/richtexteditor/richtexteditor.cpp:616 #18 0x7fff8b975e83 in KMComposeWin::slotSpellCheckingLanguage (this=0x5995f00, language=...) at /var/tmp/portage/kde-apps/kdepim-15.08.0/work/kdepim-15.08.0/kmail/editor/kmcomposewin.cpp:523 #19 0x76ea68f6 in call (a=0x7fffb940, r=0x5995f00, this=0x59eec00) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #20 QMetaObject::activate (sender=0x59a6120, signalOffset=optimized out, local_signal_index=optimized out, argv=0x7fffb940) at kernel/qobject.cpp:3703 #21 0x7fffef434242 in Sonnet::DictionaryComboBox::dictionaryChanged(QString const) () from /usr/lib64/libKF5SonnetUi.so.5 #22 0x7fffef4342fe in Sonnet::DictionaryComboBox::Private::slotDictionaryChanged(int) () from /usr/lib64/libKF5SonnetUi.so.5 #23 0x7fffef4345a3 in Sonnet::DictionaryComboBox::setCurrentByDictionaryName(QString const) () from /usr/lib64/libKF5SonnetUi.so.5 #24 0x7fff8b97ed93 in KMComposeWin::readConfig (this=this@entry=0x5995f00, reload=reload@entry=false) at /var/tmp/portage/kde-apps/kdepim-15.08.0/work/kdepim-15.08.0/kmail/editor/kmcomposewin.cpp:650 #25 0x7fff8b991868 in KMComposeWin::KMComposeWin (this=this@entry=0x5995f00, aMsg=..., lastSignState=lastSignState@entry=false, lastEncryptState=lastEncryptState@entry=false, context=context@entry=KMail::Composer::New, id=id@entry=824152080, textSelection=..., customTemplate=..., __in_chrg=optimized out, __vtt_parm=optimized out) at /var/tmp/portage/kde-apps/kdepim-15.08.0/work/kdepim-15.08.0/kmail/editor/kmcomposewin.cpp:458 #26 0x7fff8b992651 in KMComposeWin::create (msg=..., lastSignState=lastSignState@entry=false, lastEncryptState=lastEncryptState@entry=false, context=context@entry=KMail::Composer::New
[kmail2] [Bug 351395] kmail 4.81beta1 crashes when opening the composer window
https://bugs.kde.org/show_bug.cgi?id=351395 Jan-Matthias Braun jan_br...@gmx.net changed: What|Removed |Added Summary|kmail 4.81beta1 crashes |kmail 4.81beta1 crashes |when opening the composer |when opening the composer |with new message for the |window |first time after startup| -- 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 351395] kmail 4.81beta1 crashes when opening the composer window
https://bugs.kde.org/show_bug.cgi?id=351395 Jan-Matthias Braun jan_br...@gmx.net changed: What|Removed |Added Severity|grave |critical -- 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 351395] kmail 4.81beta1 crashes when opening the composer with new message for the first time after startup
https://bugs.kde.org/show_bug.cgi?id=351395 --- Comment #1 from Jan-Matthias Braun jan_br...@gmx.net --- It at least worked once, when a composer window was open was at start restored from a previous run. I was able to just start hit reply and get a new window. On the other hand, it seems to be that a specific time after closing the last composer window, I cannot open a new one from kontact (kmail) again. Then I have to again start a new composer by evoking kmail from the command line. -- 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 351515] New: Akonadi-Resource 15.08 (15.07.90) crash in background (probably while checking mails)
https://bugs.kde.org/show_bug.cgi?id=351515 Bug ID: 351515 Summary: Akonadi-Resource 15.08 (15.07.90) crash in background (probably while checking mails) Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: jan_br...@gmx.net CC: kdepim-bugs@kde.org, vkra...@kde.org Application: akonadi_imap_resource (4.88.0) Qt Version: 5.5.0 Operating System: Linux 4.1.6+ x86_64 Distribution: Gentoo Base System release 2.2 -- Information about the crash: I was not interacting with kmail, therefore I assume the crash accured during background work. My accounts are typically checked all 5 mins. The system was not idle, I was working on another application on a different screen activity. Distribution: Gentoo This is most probably a duplicate of Bug 351097, but the crash assistant is not accepting this. I can press the connect to bug report button, but it is ignoring that. So please excuse the noise. -- Backtrace: Application: Akonadi Resource (akonadi_imap_resource), signal: Aborted Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f95c713f7c0 (LWP 24377))] Thread 4 (Thread 0x7f95c6b7a700 (LWP 24410)): #0 0x7f95cdf3f3ad in poll () from /lib64/libc.so.6 #1 0x7f95ccec0172 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f95ccec928f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f95c6c92f69 in QXcbEventReader::run (this=0x11aaad0) at qxcbconnection.cpp:1197 #4 0x7f95ce83bdee in QThreadPrivate::start (arg=0x11aaad0) at thread/qthread_unix.cpp:331 #5 0x7f95ccedc324 in start_thread () from /lib64/libpthread.so.0 #6 0x7f95cdf481ad in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f95c4e04700 (LWP 24501)): #0 0x7f95cdf3f3ad in poll () from /lib64/libc.so.6 #1 0x7f95cb4fcff4 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f95cb495dcc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f95cea8537c in QEventDispatcherGlib::processEvents (this=0x7f95b80008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #4 0x7f95cea29532 in QEventLoop::exec (this=this@entry=0x7f95c4e03e00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f95ce836e74 in QThread::exec (this=optimized out) at thread/qthread.cpp:503 #6 0x7f95ce83bdee in QThreadPrivate::start (arg=0x13389a0) at thread/qthread_unix.cpp:331 #7 0x7f95ccedc324 in start_thread () from /lib64/libpthread.so.0 #8 0x7f95cdf481ad in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f95b700 (LWP 27746)): #0 0x7f95cea84810 in size (this=0x7f95b40061a0) at ../../include/QtCore/../../src/corelib/tools/qlist.h:105 #1 count (this=0x7f95b40061a0) at ../../include/QtCore/../../src/corelib/tools/qlist.h:314 #2 socketNotifierSourceCheck (source=0x7f95b4006140) at kernel/qeventdispatcher_glib.cpp:74 #3 0x7f95cb4942c9 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #4 0x7f95cb4fcf98 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7f95cb495dcc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #6 0x7f95cea8537c in QEventDispatcherGlib::processEvents (this=0x7f95b4003520, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #7 0x7f95cea29532 in QEventLoop::exec (this=this@entry=0x7f95bfffee00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #8 0x7f95ce836e74 in QThread::exec (this=optimized out) at thread/qthread.cpp:503 #9 0x7f95ce83bdee in QThreadPrivate::start (arg=0x134cfe0) at thread/qthread_unix.cpp:331 #10 0x7f95ccedc324 in start_thread () from /lib64/libpthread.so.0 #11 0x7f95cdf481ad in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f95c713f7c0 (LWP 24377)): [KCrash Handler] #6 0x7f95cde933c7 in raise () from /lib64/libc.so.6 #7 0x7f95cde9475a in abort () from /lib64/libc.so.6 #8 0x7f95ce4a2b4d in __gnu_cxx::__verbose_terminate_handler () at /var/tmp/portage/sys-devel/gcc-5.2.0/work/gcc-5.2.0/libstdc++-v3/libsupc++/vterminate.cc:95 #9 0x7f95ce4a0966 in __cxxabiv1::__terminate (handler=optimized out) at /var/tmp/portage/sys-devel/gcc-5.2.0/work/gcc-5.2.0/libstdc++-v3/libsupc++/eh_terminate.cc:47 #10 0x7f95ce4a09b1 in std::terminate () at /var/tmp/portage/sys-devel/gcc-5.2.0/work/gcc-5.2.0/libstdc++-v3/libsupc++/eh_terminate.cc:57 #11 0x7f95ce4a0bc9 in __cxxabiv1::__cxa_throw (obj=0x143b880, tinfo=0x7f95cdb64360 typeinfo for Akonadi::ProtocolException, dest=0x7f95cdb11470 Akonadi::ProtocolException::~ProtocolException()) at /var/tmp/portage/sys-devel/gcc-5.2.0/work/gcc-5.2.0/libstdc++-v3/libsupc++/eh_throw.cc:87 #12 0x7f95cdb12281 in ?? () from /usr/lib64/libKF5AkonadiPrivate.so.5
[Akonadi] [Bug 351515] Akonadi-Resource 15.08 (15.07.90) crash in background (probably while checking mails)
https://bugs.kde.org/show_bug.cgi?id=351515 --- Comment #1 from Jan-Matthias Braun jan_br...@gmx.net --- Backtrace: Now with more resolved symbols in the crashing thread! Application: Akonadi Resource (akonadi_imap_resource), signal: Aborted Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f77eb3757c0 (LWP 3740))] Thread 4 (Thread 0x7f77eadb0700 (LWP 3819)): #0 0x7f77f21753ad in poll () from /lib64/libc.so.6 #1 0x7f77f10f6172 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f77f10ff28f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f77eaec8f69 in QXcbEventReader::run (this=0x6e9ad0) at qxcbconnection.cpp:1197 #4 0x7f77f2a71dee in QThreadPrivate::start (arg=0x6e9ad0) at thread/qthread_unix.cpp:331 #5 0x7f77f1112324 in start_thread () from /lib64/libpthread.so.0 #6 0x7f77f217e1ad in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f77e901b700 (LWP 3983)): #0 0x7f77f21713fd in read () from /lib64/libc.so.6 #1 0x7f77eea82073 in ?? () from /usr/lib64/libnvidia-tls.so.355.06 #2 0x7f77ef733620 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f77ef6ca36c in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #4 0x7f77ef732f98 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7f77ef6cbdcc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #6 0x7f77f2cbb37c in QEventDispatcherGlib::processEvents (this=0x7f77dc0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #7 0x7f77f2c5f532 in QEventLoop::exec (this=this@entry=0x7f77e901ae00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #8 0x7f77f2a6ce74 in QThread::exec (this=optimized out) at thread/qthread.cpp:503 #9 0x7f77f2a71dee in QThreadPrivate::start (arg=0x880620) at thread/qthread_unix.cpp:331 #10 0x7f77f1112324 in start_thread () from /lib64/libpthread.so.0 #11 0x7f77f217e1ad in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f77dbda9700 (LWP 4112)): #0 0x7f77f2cba962 in postEventSourcePrepare (s=0x7f77d40012f0, timeout=optimized out) at kernel/qeventdispatcher_glib.cpp:260 #1 0x7f77ef6cbb4d in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f77ef732f20 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f77ef6cbdcc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f77f2cbb37c in QEventDispatcherGlib::processEvents (this=0x7f77d40008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #5 0x7f77f2c5f532 in QEventLoop::exec (this=this@entry=0x7f77dbda8e00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f77f2a6ce74 in QThread::exec (this=optimized out) at thread/qthread.cpp:503 #7 0x7f77f2a71dee in QThreadPrivate::start (arg=0x88fa90) at thread/qthread_unix.cpp:331 #8 0x7f77f1112324 in start_thread () from /lib64/libpthread.so.0 #9 0x7f77f217e1ad in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f77eb3757c0 (LWP 3740)): [KCrash Handler] #6 0x7f77f20c93c7 in raise () from /lib64/libc.so.6 #7 0x7f77f20ca75a in abort () from /lib64/libc.so.6 #8 0x7f77f26d8b4d in __gnu_cxx::__verbose_terminate_handler () at /var/tmp/portage/sys-devel/gcc-5.2.0/work/gcc-5.2.0/libstdc++-v3/libsupc++/vterminate.cc:95 #9 0x7f77f26d6966 in __cxxabiv1::__terminate (handler=optimized out) at /var/tmp/portage/sys-devel/gcc-5.2.0/work/gcc-5.2.0/libstdc++-v3/libsupc++/eh_terminate.cc:47 #10 0x7f77f26d69b1 in std::terminate () at /var/tmp/portage/sys-devel/gcc-5.2.0/work/gcc-5.2.0/libstdc++-v3/libsupc++/eh_terminate.cc:57 #11 0x7f77f26d6bc9 in __cxxabiv1::__cxa_throw (obj=0x919ea0, tinfo=0x7f77f1d9a360 typeinfo for Akonadi::ProtocolException, dest=0x7f77f1d47470 Akonadi::ProtocolException::~ProtocolException()) at /var/tmp/portage/sys-devel/gcc-5.2.0/work/gcc-5.2.0/libstdc++-v3/libsupc++/eh_throw.cc:87 #12 0x7f77f1d60fcc in Akonadi::Protocol::DataStream::operator (this=0x7ffe8827c790, str=...) at /var/tmp/portage/kde-apps/akonadi-15.08.0/work/akonadi-15.08.0/src/private/datastream_p_p.h:211 #13 0x7f77f1d74f8a in Akonadi::Protocol::CreateItemCommandPrivate::deserialize (this=0x8b8f20, stream=...) at /var/tmp/portage/kde-apps/akonadi-15.08.0/work/akonadi-15.08.0/src/private/protocol.cpp:1955 #14 0x7f77f1d55745 in Akonadi::Protocol::deserialize (device=optimized out) at /var/tmp/portage/kde-apps/akonadi-15.08.0/work/akonadi-15.08.0/src/private/protocol.cpp:627 #15 0x7f77f4439c6b in Akonadi::SessionPrivate::dataReceived() () from /usr/lib64/libKF5AkonadiCore.so.5 #16 0x7f77f2c91fb1 in QMetaObject::activate (sender=0x7d9290, signalOffset=optimized out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3718 #17 0x7f77f2c91fb1 in QMetaObject::activate (sender=0x7d64c8, signalOffset=optimized out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3718 #18 0x7f77f3bbf470 in QAbstractSocketPrivate::canReadNotification() () from /usr/lib64
[kmail2] [Bug 351395] New: kmail 4.81beta1 crashes when opening the composer with new message for the first time after startup
https://bugs.kde.org/show_bug.cgi?id=351395 Bug ID: 351395 Summary: kmail 4.81beta1 crashes when opening the composer with new message for the first time after startup Product: kmail2 Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: jan_br...@gmx.net When creating a new message after launching kmail, it crashes and ends. If I (instead) start kmail and open the composer via reply to, or from command line with an e-Mail-Address as parameter, the composer opens and afterwards, I can use the new message action from the menu or the toolbar. gdb shows a segfault Program received signal SIGSEGV, Segmentation fault. 0x77a81b55 in QAction::setEnabled(bool) () from /usr/lib64/libQt5Widgets.so.5 (gdb) back #0 0x77a81b55 in QAction::setEnabled(bool) () from /usr/lib64/libQt5Widgets.so.5 #1 0x7fff8b7ec0f9 in KMComposeWin::slotEditorTextChanged (this=0x2b8a800) at /var/tmp/portage/kde-apps/kdepim-15.07.90/work/kdepim-15.07.90/kmail/editor/kmcomposewin.cpp:535 #2 0x7fff8b835a0b in KMComposeWin::qt_static_metacall (_o=optimized out, _c=optimized out, _id=optimized out, _a=optimized out) at /var/tmp/portage/kde-apps/kdepim-15.07.90/work/kdepim-15.07.90_build/kmail/moc_kmcomposewin.cpp:485 #3 0x76ea6fb1 in QMetaObject::activate (sender=0x219a0f0, signalOffset=optimized out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3718 #4 0x778cce95 in QTextEdit::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib64/libQt5Widgets.so.5 #5 0x76ea6fb1 in QMetaObject::activate (sender=0x4afa790, signalOffset=optimized out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3718 #6 0x778928dd in QWidgetTextControl::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib64/libQt5Widgets.so.5 #7 0x77892c8b in QWidgetTextControl::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQt5Widgets.so.5 #8 0x76ea70b4 in QMetaObject::activate (sender=sender@entry=0x4afa7b0, signalOffset=optimized out, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3733 #9 0x76ea7667 in QMetaObject::activate (sender=sender@entry=0x4afa7b0, m=m@entry=0x7760fae0 QTextDocument::staticMetaObject, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3583 #10 0x77546a43 in QTextDocument::contentsChanged (this=this@entry=0x4afa7b0) at .moc/moc_qtextdocument.cpp:378 #11 0x772d7442 in contentsChanged (this=0x4aed6b0) at text/qtextdocument_p.cpp:1646 #12 QTextDocumentPrivate::finishEdit (this=0x4aed6b0) at text/qtextdocument_p.cpp:1238 #13 0x772d786c in QTextDocumentPrivate::endEditBlock (this=optimized out) at text/qtextdocument_p.cpp:1193 #14 0x772d794e in QTextDocumentPrivate::endEditBlock (this=optimized out) at text/qtextdocument_p.cpp:1179 #15 0x7731c22d in rehighlight (operation=QTextCursor::End, cursor=..., this=0x48adf20) at text/qsyntaxhighlighter.cpp:69 #16 QSyntaxHighlighter::rehighlight (this=optimized out) at text/qsyntaxhighlighter.cpp:368 #17 0x7fff8be8544d in PimCommon::RichTextEditor::setSpellCheckingLanguage (this=0x219a0f0, _language=...) at /var/tmp/portage/kde-apps/kdepim-15.07.90/work/kdepim-15.07.90/pimcommon/texteditor/richtexteditor/richtexteditor.cpp:616 #18 0x7fff8b7e9eb3 in KMComposeWin::slotSpellCheckingLanguage (this=0x2b8a800, language=...) at /var/tmp/portage/kde-apps/kdepim-15.07.90/work/kdepim-15.07.90/kmail/editor/kmcomposewin.cpp:523 #19 0x76ea68f6 in call (a=0x7fffa7d0, r=0x2b8a800, this=0x42f98b0) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #20 QMetaObject::activate (sender=0xa97810, signalOffset=optimized out, local_signal_index=optimized out, argv=0x7fffa7d0) at kernel/qobject.cpp:3703 #21 0x7fffef240242 in Sonnet::DictionaryComboBox::dictionaryChanged(QString const) () from /usr/lib64/libKF5SonnetUi.so.5 #22 0x7fffef2402fe in Sonnet::DictionaryComboBox::Private::slotDictionaryChanged(int) () from /usr/lib64/libKF5SonnetUi.so.5 #23 0x7fffef2405a3 in Sonnet::DictionaryComboBox::setCurrentByDictionaryName(QString const) () from /usr/lib64/libKF5SonnetUi.so.5 #24 0x7fff8b7f2dc3 in KMComposeWin::readConfig (this=this@entry=0x2b8a800, reload=reload@entry=false) at /var/tmp/portage/kde-apps/kdepim-15.07.90/work/kdepim-15.07.90/kmail/editor/kmcomposewin.cpp:650 #25 0x7fff8b805898 in KMComposeWin::KMComposeWin (this=this@entry=0x2b8a800, aMsg=..., lastSignState=lastSignState@entry=false, lastEncryptState=lastEncryptState@entry=false,
