| Summary: | kmail crash on search | ||
|---|---|---|---|
| Product: | [Applications] kontact | Reporter: | Buddlespit <buddlespit> |
| Component: | Assignee: | kdepim bugs <kdepim-bugs> | |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | bjorn.bidar, jan_braun, kdenis, Kicer86, maraval_p, montel, schindler |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.5.3 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
new crash information with debug symboles New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Buddlespit
2016-06-23 12:40:42 UTC
could you add more debug info (package debug info) please ? (In reply to Laurent Montel from comment #1) > could you add more debug info (package debug info) please ? I wish I could. From what I understand, Just about everything in Arch is compiled with debug symbols stripped from the packages. Created attachment 99781 [details] New crash information added by DrKonqi kontact (5.2.2) using Qt 5.7.0 - What I was doing when the application crashed: Started Kmail/Kontact (didn't matters), wrote an random word in the search box and crashes. on my desktop I didn't got the issue (same hardware and software config, except my desktop has a kernel 4.5.x). Shell output from kmail: https://paste.kde.org/pdiop3el4 -- Backtrace (Reduced): #7 0x00002b96895083dd in __gnu_cxx::__verbose_terminate_handler () at /build/gcc-multilib/src/gcc/libstdc++-v3/libsupc++/vterminate.cc:95 #8 0x00002b9689506196 in __cxxabiv1::__terminate (handler=<optimized out>) at /build/gcc-multilib/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:47 #9 0x00002b96895061e1 in std::terminate () at /build/gcc-multilib/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:57 #10 0x00002b96895063f8 in __cxxabiv1::__cxa_throw (obj=obj@entry=0x1b061d0, tinfo=0x2b96897f0a38 <typeinfo for std::logic_error>, dest=0x2b968951b400 <std::logic_error::~logic_error()>) at /build/gcc-multilib/src/gcc/libstdc++-v3/libsupc++/eh_throw.cc:87 #11 0x00002b968952f3ef in std::__throw_logic_error (__s=0x2b9694fd9848 "basic_string::_M_construct null not valid") at /build/gcc-multilib/src/gcc/libstdc++-v3/src/c++11/functexcept.cc:74 Created attachment 99921 [details]
new crash information with debug symboles
deleting the email related stuff of baloo in ~/.local/share/baloo fixed it for me. Yup, deleting everything in /.local/share/baloo/email worked for me! I don't think this is really resolved, this is a bug that needs to be fixed. Unexperienced users wont know how to fix this. Created attachment 106677 [details]
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 0x00007f7fdef72cad 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 0x00007f7fdef70a16 in __cxxabiv1::__terminate (handler=<optimized out>) at /var/tmp/portage/sys-devel/gcc-6.3.0/work/gcc-6.3.0/libstdc++-v3/libsupc++/eh_terminate.cc:47
#10 0x00007f7fdef70a61 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 0x00007f7fdef70c79 in __cxxabiv1::__cxa_throw (obj=obj@entry=0x54eae90, tinfo=0x7f7fdf0b2890 <typeinfo for std::logic_error>, 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 0x00007f7fdef9b73f 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
*** Bug 390206 has been marked as a duplicate of this bug. *** *** Bug 389172 has been marked as a duplicate of this bug. *** Created attachment 123954 [details]
New crash information added by DrKonqi
kontact (5.12.3) using Qt 5.13.2
- What I was doing when the application crashed:
Searching for an email crashes KMail.
It occurs every time.
-- Backtrace (Reduced):
#8 0x00007ffbc0e9d81d in __gnu_cxx::__verbose_terminate_handler () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/vterminate.cc:95
#9 0x00007ffbc0eaa4da in __cxxabiv1::__terminate (handler=<optimized out>) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:47
#10 0x00007ffbc0eaa537 in std::terminate () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:57
#11 0x00007ffbc0eaa78e in __cxxabiv1::__cxa_throw (obj=obj@entry=0x5646c9e39830, tinfo=0x7ffbc0fe33c8 <typeinfo for std::logic_error>, dest=0x7ffbc0ec0830 <std::logic_error::~logic_error()>) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_throw.cc:95
#12 0x00007ffbc0ea0287 in std::__throw_logic_error (__s=__s@entry=0x7ffbc0f9e0e0 "basic_string::_M_construct null not valid") at /build/gcc/src/gcc/libstdc++-v3/src/c++11/functexcept.cc:66
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you! (In reply to Justin Zobel from comment #12) > Thank you for reporting this crash in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the crash with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! The bug no longer happens from what I know. It would be interesting to know if it still can be triggered with the corrupted baloo mail index. But I think the bug can be marked as resolved. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |