Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
kmail and akonadi crashes
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
tomtom69
Apprentice
Apprentice


Joined: 09 Nov 2010
Posts: 193
Location: Bavaria

PostPosted: Fri Feb 01, 2019 8:42 pm    Post subject: kmail and akonadi crashes Reply with quote

I have 2 systems recently installed from scratch about some months ago, and both got kmail installed some weeks ago, which causes crashes at different situations.
There seem to be 2 issues which are already known and which (1) cause akonadi to crash on first startup and (2) kmail to crash when an email is opened on a separate window and this window is closed. I seem to suffer from these two bugs:
[url]
https://bugzilla.redhat.com/show_bug.cgi?id=1448691
https://kde-bugs-dist.kde.narkive.com/zBCBPCPm/kmail2-bug-400838-new-crash-when-closing-message-window-with-qt-5-12
[/url]
Both bugs do not affect overall system stability, but they are annoying because one gets crash reports and needs to restart kmail.
Regarding the bug reports it looks like both issues are solved with kde-apps 18.12.
Q1: I have seen kmail-18.12.1 in portage. How can I contribute to testing this new version? (=how can I unmask it easily, how should I report issues, are there specific tests which I could help others with?)
Q2: Does anyone still use kmail with gentoo or am I the only one? (My family and me like kmail because it is easy to use, can open html emails without using an external browser, supports several identities, because it is "standalone" and not integrated into a browser-like application, supports drag-and-drop in KDE)

tom
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6825
Location: Austria

PostPosted: Fri Feb 01, 2019 8:54 pm    Post subject: Re: kmail and akonadi crashes Reply with quote

tomtom69 wrote:
Q1: I have seen kmail-18.12.1 in portage. How can I contribute to testing this new version?

kde overlay provides unmask files for that purpose. You don't have to actually add the overlay for that, you can download them manually (use the .keywords files): https://gitweb.gentoo.org/proj/kde.git/tree/Documentation/package.accept_keywords

tomtom69 wrote:
https://kde-bugs-dist.kde.narkive.com/zBCBPCPm/kmail2-bug-400838-new-crash-when-closing-message-window-with-qt-5-12

The link makes it seem you would have to have Qt 5.12 for that, which is neither stable nor in Portage at this point (only available through qt overlay).
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
tomtom69
Apprentice
Apprentice


Joined: 09 Nov 2010
Posts: 193
Location: Bavaria

PostPosted: Sat Feb 02, 2019 12:07 pm    Post subject: Reply with quote

I overlooked qt5.12 (I have 5.11.3 installed).
However I unmasked and upgraded kde apps to 18.12.1 and did some testing at least on one of the 2 machines. I still have both segfaults.

Akonadi segfaults at first startup after system boot (when it asks for the kwallet password), and restarts automatically. The debug information is classified "useless":
https://pastebin.com/p32XUfE6
The segfault occurs in ~80% at startup after boot.

Kmail segfaults always when I open a message in a separate window (double click on the message in the list), and when I close this message windows. In about 50% of the cases it segfaults on closing kmail (with the same debug information). Debug information is also classified as "useless":
https://pastebin.com/9xzMejnA

Comparing the debug information I was led to the two bugs mentioned, however if these are fixed with 18.12 this seems to be a wrong conclusion.
One interesting fact is that both crashes only happen if the system is idle. If I start kmail on a heavily loaded system, both crashes did not appear yet.
Is there anything else I could try?
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6825
Location: Austria

PostPosted: Sat Feb 02, 2019 12:32 pm    Post subject: Reply with quote

Stacktraces are always useless unless you install debug information: https://wiki.gentoo.org/wiki/Debugging
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
tomtom69
Apprentice
Apprentice


Joined: 09 Nov 2010
Posts: 193
Location: Bavaria

PostPosted: Sat Feb 02, 2019 8:08 pm    Post subject: Reply with quote

Thank you for the help.
I enabled debugging according to the instructions, and re-compiled kmail and the libraries that look involved with debug support. Now the crash information when closing a mail message from a separate kmail window is classified als "may be helpful":
https://pastebin.com/rf0wLjBg
I was not able to get into the source code when running kmail inside a gdb session yet, but I will try further to achieve this.
Because reproducing the akonadi crash takes more effort I started with the kmail segfault.
Is this more useful, or do I need to enable debugging for further packages?
My programming experience is more on an embedded uC level (no c++, no qt) , so it is hard for me to see what is going wrong.
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6825
Location: Austria

PostPosted: Sat Feb 02, 2019 8:29 pm    Post subject: Reply with quote

To increase usefulness you would need to add debug info to qtwebengine as well, at least.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
tomtom69
Apprentice
Apprentice


Joined: 09 Nov 2010
Posts: 193
Location: Bavaria

PostPosted: Sat Feb 02, 2019 8:55 pm    Post subject: Reply with quote

qtwebengine was already emerged with debug info
from /etc/portage/package.env/kde-debug:
dev-qt/qtwebengine debugsyms installsources
Back to top
View user's profile Send private message
tomtom69
Apprentice
Apprentice


Joined: 09 Nov 2010
Posts: 193
Location: Bavaria

PostPosted: Mon Feb 04, 2019 7:03 pm    Post subject: Reply with quote

I did not succeed yet in getting gdb to show me the location where the segfault happens. gdb is able to start kmail and reports the segfault, but it doesn't show where the segfault happens:
https://pastebin.com/BcwqsYXc
Do I need to enable debugging on further libraries?

Because many issues are based on updated user profiles, I created a new user after the 18.12 update where I only set up keyboard layout and a test POP3 account on kmail. There is no difference when I use this newly created user profile.
Apart from this everything seems to work fine with the (not yet stabilized) kde-apps 18.12.
Back to top
View user's profile Send private message
tomtom69
Apprentice
Apprentice


Joined: 09 Nov 2010
Posts: 193
Location: Bavaria

PostPosted: Tue Feb 19, 2019 5:28 pm    Post subject: Reply with quote

updated to kde-apps-18.12.2 but still the same.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum