| Summary: | kmail2 crash after I selected something then tried to copy the selected data | ||
|---|---|---|---|
| Product: | [Applications] kmail2 | Reporter: | Nick <ndordea> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | ndordea |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Nick
2017-09-09 15:20:06 UTC
After the crash the attempt to create the bug [ with yes I know what I was doing at the crash time ] I got a window with the following info :
<message>
Results of the Analyzed Crash details
This report does not contain enough information for the developers, so the automated bug reporting process is not enabled for this crash.
If you wish, you can go back and change your answers
* The crash information was not generated because it was needed
* The information you can provide is not considered helpful enough in this case
</message>
So I got back and I selected an option only to be able of reporting a crash .
Is it any way of Fixing DrKonqi to accept ANY crash that happened .
It seems that DrKonqi classifies crashes in the good and bad one.
Due to that classification, the bad crashes are not reported because the users are frustrated by the implication that the crash happened but the automaton DrKonqi is not smart enough to find out WHY the crash happened .
As a user I am at loss because many times in the past I cancelled the bug reporting .
Lately kmail2 behaves strangely crashing when running under kontact or by itself
The crashes are so often that all debuginfo packages [ akonadi, kmail, kontact,kdepim ] are activated .
The crashes are very frequent and initiated from different angles :
1) crash due to "empty trash"
Yesterday I tried to create a bug .... the same window described above ...
select trash folder with the intent to empty it .... it crashed .
After that I analyzed what was in the trash ..... See below
~/.local/share/akonadi_maildir_resource_0/trash/cur> ls -al *
-rw-r--r-- 1 rocco users 75599 Sep 8 12:51 1504893060.R32.SuSE4Rocco.dom:2,S
-rw-r--r-- 1 rocco users 71433 Sep 8 12:51 1504893061.R374.SuSE4Rocco.dom
-rw-r--r-- 1 rocco users 53269 Sep 8 12:51 1504893061.R62.SuSE4Rocco.dom
-rw-r--r-- 1 rocco users 49224 Sep 8 12:51 1504893061.R892.SuSE4Rocco.dom
-rw-r--r-- 1 rocco users 34680 Sep 8 12:51 1504893061.R937.SuSE4Rocco.dom
-rw-r--r-- 1 rocco users 68641 Sep 8 12:51 1504893063.R226.SuSE4Rocco.dom
I noticed that in other folders all items are in format
nnnnnnnnnn.R[rr|rrr].SuSe4Rocco.dom:2,S
or
nnnnnnnnnn.R[rr|rrr].SuSe4Rocco.dom:2,PS
So, I did
i) stop akonadictl
ii) delete all trash items without the suffix :2,[S|PS]
iii) start akonadictl
iv) stat kmail2
v) go to trash, see what it is in it [ only one item !!! ]
vi) go back select trash folder select empty .... done.
2) crash due to "remove duplicated"
Similar to item 1). above .....
go to the "problem" folder check the cur/new/tmp to see its contents
I found many of items without the suffix :2,[S|PS]
delete them ..... voila the kmail behave properly till another special crash happens ....
3) move to trash is not complete
In some folders I want to select unread then after analyzing them [ subject, from, etc ] it I want to delete all of them .
edit+select all messages sometimes works sometimes select all messages is greyed out . That is the signal that there is at least an item that does not have the magic suffix :2,[PS|S] .
Then I apply the same method even if some emails are lost ....
[ Again DrKonqi is not impress with the crash ]
4) select some messages and use Move to trash .
Some of them are grayed out ....---> another angle of missing the suffix
Select one of them ...... crash . DrKonqi is not impress
5) If kmail2 is running under kontact, DrKonqi reports kontact as the culprit ... So I stopped running kmail2 under kontact to make sure that the crashes are created by hmail2 .
Questions :
1) Is there any method of verifying the kmail database [ in opensuse MariaDB ]
2) Although some of kde help indicates that after akonadictl stop , with the exception of "grep --color=auto mysql", you should not see any output from
ps -ux | grep mysql
That's not the case .....
How is it possible to stop akonadi database ?
3) in the same category .... kquitapp kmail | kontact .... does not work .
4) is there any procedure of eliminating all bad items OR fixing the responsible agent of making sure that they correctly process the emails we receive .
5) There are many KDE repos .
Is there any web page that explains what repos should be used .
There are so many Qt5, Qt5.x, LTS, KF5, etc .
6) Many times after a maintenance/upgrade there are crashes due to the mismatch in akonadi [ some agents fail to start ] but they are seen as kmail2 crash .
In 384286 it was a "knotact/kmail" but the root cause what akonadi failures .
Is it possible to have an akonadi crash rather than pointing to kmail2 having agents offline ?
Is it possible to enhance the pre-requisites, co-requisites of packaging to stop installing conflicting packages ?
I hope that KDE team will come with some solutions/answers/fixes soon .
Thank you for your help and support .
Nick
Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. 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! |