Bug 351572 - Crash while installing 17.2
Summary: Crash while installing 17.2
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-08-21 16:28 UTC by robert.l.kief
Modified: 2018-02-01 09:49 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description robert.l.kief 2015-08-21 16:28:59 UTC
Application: akonadi_notes_agent (4.14)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.13.0-24-generic i686
Distribution: Linux Mint 17 Qiana

-- Information about the crash:
I was only installing Linux Mint 17.2 after doing all the current updates to 17.1.

-- Backtrace:
Application: Notes Agent (akonadi_notes_agent), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#7  ref (this=0x61636900) at ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:120
#8  QExplicitlySharedDataPointer (o=..., this=0xbfe1a7b0) at ../../include/QtCore/../../src/corelib/tools/qshareddata.h:169
#9  QDateTime::QDateTime (this=0xbfe1a7b0, other=...) at tools/qdatetime.cpp:2182
#10 0x08050f98 in _start ()

Possible duplicates by query: bug 342341, bug 341534, bug 339624.

Reported using DrKonqi
Comment 1 Denis Kurz 2017-06-23 20:21:47 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-02-01 09:49:20 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.