[Akonadi] [Bug 421077] Akonadi crashes after almost any boot

2022-11-22 Thread Mike McCarthy
https://bugs.kde.org/show_bug.cgi?id=421077

Mike McCarthy  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #6 from Mike McCarthy  ---
Changing status to RESOLVED-WORKSFORME as I can no longer reproduce in latest
openSuSE (leap 15.4).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 421077] Akonadi crashes after almost any boot

2022-11-21 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=421077

--- Comment #5 from Bug Janitor Service  ---
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!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 421077] Akonadi crashes after almost any boot

2022-11-07 Thread Mike McCarthy
https://bugs.kde.org/show_bug.cgi?id=421077

Mike McCarthy  changed:

   What|Removed |Added

 CC||m...@w1nr.net

--- Comment #4 from Mike McCarthy  ---
I do not see this behavior any more since I upgraded to OpenSUSE Leap 15.4
(latest).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 421077] Akonadi crashes after almost any boot

2022-10-29 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=421077

Justin Zobel  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #3 from Justin Zobel  ---
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 "REPORTED" when
replying. Thank you!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 421077] Akonadi crashes after almost any boot

2020-10-31 Thread Mike McCarthy
https://bugs.kde.org/show_bug.cgi?id=421077

Mike McCarthy  changed:

   What|Removed |Added

 CC||sy...@w1nr.net

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 421077] Akonadi crashes after almost any boot

2020-10-31 Thread Mike McCarthy
https://bugs.kde.org/show_bug.cgi?id=421077

--- Comment #2 from Mike McCarthy  ---
Created attachment 132907
  --> https://bugs.kde.org/attachment.cgi?id=132907=edit
New crash information added by DrKonqi

akonadiserver (5.14.2 (20.04.2)) using Qt 5.12.7

- What I was doing when the application crashed:

Just logged in. Running in Virtualbox on Windows 10 host.

-- Backtrace (Reduced):
#4  _mm_crc32_u64 (__V=, __C=) at
/usr/lib64/gcc/x86_64-suse-linux/7/include/smmintrin.h:848
#5  crc32 (ptr=0xfe69d8714ca8, len=, h=)
at tools/qhash.cpp:112
#6  0x7f355bc48914 in hash (seed=, len=,
p=) at tools/qhash.cpp:223
#7  qHash (key=..., seed=) at tools/qhash.cpp:239
#8  0x5650e742f22b in QHash::findNode
(this=this@entry=0x5650e80ae108, akey=..., ahp=ahp@entry=0x0) at
/usr/include/qt5/QtCore/qhash.h:934

-- 
You are receiving this mail because:
You are the assignee for the bug.