kactivitymanagerd crashed with SIGSEGV in QMetaObject::invokeMethod()

Bug #1565446 reported by Laurent Bonnaud
38
This bug affects 6 people
Affects Status Importance Assigned to Milestone
kactivities-kf5 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I get this crash every time I log in plasma.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: kactivities 5.18.0-0ubuntu1
Uname: Linux 4.5.0-040500-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Apr 3 12:20:28 2016
ExecutablePath: /usr/bin/kactivitymanagerd
ProcCmdline: /usr/bin/kactivitymanagerd start-daemon
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd547ebff92 <QMetaObject::invokeMethod(QObject*, char const*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument)+754>: mov (%r14),%rax
 PC (0x7fd547ebff92) ok
 source "(%r14)" (0x7575757575757575) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: kactivities-kf5
Title: kactivitymanagerd crashed with SIGSEGV in QMetaObject::invokeMethod()
UpgradeStatus: Upgraded to xenial on 2016-03-31 (3 days ago)
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare staff

Revision history for this message
Laurent Bonnaud (laurent-bonnaud) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 QMetaObject::invokeMethod(QObject*, char const*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () from /tmp/apport_sandbox_ZNvKU8/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 StatsPlugin::currentActivity() const () from /tmp/apport_sandbox_ZNvKU8/usr/lib/x86_64-linux-gnu/qt5/plugins/kactivitymanagerd/1/kactivitymanagerd_plugin_sqlite.so
 ResourceScoreMaintainer::Private::run() () from /tmp/apport_sandbox_ZNvKU8/usr/lib/x86_64-linux-gnu/qt5/plugins/kactivitymanagerd/1/kactivitymanagerd_plugin_sqlite.so
 QThreadPrivate::start(void*) () from /tmp/apport_sandbox_ZNvKU8/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 start_thread (arg=0x7fd521cb0700) at pthread_create.c:333

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in kactivities-kf5 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in kactivities-kf5 (Ubuntu):
status: New → Confirmed
Revision history for this message
Justa Guy (nginus) wrote :

In my case I was able to stop the error at logon by uninstalling (purging) kactivities, while leaving libkactivities6 installed for dependencies.

Revision history for this message
Laurent Bonnaud (laurent-bonnaud) wrote :

This bug is now fixed.

Changed in kactivities-kf5 (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.