Public bug reported:

I was using kmail, and wanted to re-sync my folders, it didn't seem to
be working, then akonadi_imap_resource crashed, now the sync has started
working again, so I can only presume I forced it to crash by my keeping
requesting my mail folders to sync, when they didn't appear to be.

Perhaps a case of user impatience on my part.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: kdepim-runtime 4:17.12.3-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Apr 13 19:18:02 2018
ExecutablePath: /usr/bin/akonadi_imap_resource
InstallationDate: Installed on 2018-04-10 (3 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
ProcCmdline: /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_2
 PATH=(custom, user)
 Segfault happened at: 0x7f47f83d9f01 
<_ZNK7Akonadi18CollectionFetchJob11collectionsEv+1>:      mov    0x18(%rsi),%rsi
 PC (0x7f47f83d9f01) ok
 source "0x18(%rsi)" (0x00000018) not located in a known VMA region (needed 
readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kdepim-runtime
 Akonadi::CollectionFetchJob::collections() const () at 
 () at /usr/lib/x86_64-linux-gnu/
 QMetaObject::activate(QObject*, int, int, void**) () at 
 KJob::finished(KJob*, KJob::QPrivateSignal) () at 
 KJob::~KJob() () at /usr/lib/x86_64-linux-gnu/
Title: akonadi_imap_resource crashed with SIGSEGV in 
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

** Affects: kdepim-runtime (Ubuntu)
     Importance: Undecided
         Status: New

** Tags: amd64 apport-crash bionic need-amd64-retrace

** Information type changed from Private to Public

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  akonadi_imap_resource crashed with SIGSEGV in

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to