Bug 367789 - Agent zur E-Mail-Archivierung (akonadi_archivemail_agent), signal: Segmentation fault
Summary: Agent zur E-Mail-Archivierung (akonadi_archivemail_agent), signal: Segmentati...
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Archive Mail Agent (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-08-25 06:42 UTC by Don Curtis
Modified: 2016-08-25 08:02 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Don Curtis 2016-08-25 06:42:51 UTC 
Application: akonadi_archivemail_agent (4.14)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 3.16.7-35-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
KMail was performing the first daily Archive of one of the mail folders.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Agent zur E-Mail-Archivierung (akonadi_archivemail_agent), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#5  0x00007fb8c48cd9fb in QUrl::QUrl(QUrl const&) (this=0x6c69662d69752d78) at ../../src/corelib/arch/qatomic_x86_64.h:121
#6  0x00007fb8c48cd9fb in QUrl::QUrl(QUrl const&) (this=0x7fff1b1254d0, other=...) at io/qurl.cpp:4270
#7  0x00007fb8c5027a79 in KUrl::KUrl(KUrl const&) () at /usr/lib64/libkdecore.so.5
#8  0x0000000000412bff in _start ()

Possible duplicates by query: bug 347300.

Reported using DrKonqi
Comment 1 Laurent Montel 2016-08-25 07:43:50 UTC 
Sorry 4.14 is very old.
IT works fine here.
So I think it fixed in new release.
Reopen if you still have problem in 5.x. version (last is 5.3.0
Comment 2 Don Curtis 2016-08-25 08:02:49 UTC 
openSUSE 13.2 (KDE4 Plasma) is however still current.
Yes, it maybe that openSUSE Leap 42.x no longer suffers from this issue, but . . .