kactivitymanagerd crashed on login on armel

Bug #746202 reported by Tobin Davis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KDE Base
Unknown
High
kde-runtime (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: kdebase-runtime

The kactivitymanagerd application crashed on login with the kubuntu desktop armel images (omap & omap4). Bug was filed through the kde crash handler upstream, this is mainly for reporting to iso tracker.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: kdebase-runtime 4:4.6.1-0ubuntu1
ProcVersionSignature: User Name 2.6.38-7.39-omap 2.6.38
Uname: Linux 2.6.38-7-omap armv7l
Architecture: armel
Date: Wed Mar 30 20:47:53 2011
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: kdebase-runtime
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Tobin Davis (gruemaster) wrote :
tags: added: iso-testing
Revision history for this message
In , Tobin Davis (gruemaster) wrote :
Download full text (4.0 KiB)

Application: kactivitymanagerd (1.0)
KDE Platform Version: 4.6.1 (4.6.1)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-7-omap armv7l
Distribution: Ubuntu Natty (development branch)

-- Information about the crash:
- What I was doing when the application crashed:

The crash handler started immediately after booting, and continues to crash every reboot. The image is from Kubuntu Natty Beta 1 for omap. Also failed on omap4.

-- Backtrace:
Application: KDE Activity Manager (kactivitymanagerd), signal: Segmentation fault
[KCrash Handler]
#6 0x4144aef8 in Soprano::Client::LocalSocketClient::LocalSocketClient(QObject*) () from /usr/lib/libsopranoclient.so.1
#7 0x4046e3f0 in GlobalModelContainer (this=0x1396dc8) at ../../nepomuk/core/nepomukmainmodel.cpp:65
#8 operator-> (this=0x1396dc8) at ../../nepomuk/core/nepomukmainmodel.cpp:138
#9 Nepomuk::MainModel::init (this=0x1396dc8) at ../../nepomuk/core/nepomukmainmodel.cpp:176
#10 0x4046eb7e in Nepomuk::MainModel::MainModel (this=0x1396dc8, parent=0x130de90) at ../../nepomuk/core/nepomukmainmodel.cpp:158
#11 0x40467c20 in Nepomuk::ResourceManager::init (this=0x130de90) at ../../nepomuk/core/resourcemanager.cpp:323
#12 0x40467dbe in Nepomuk::ResourceManager::ResourceManager (this=0x130de90) at ../../nepomuk/core/resourcemanager.cpp:286
#13 0x40468f0e in ResourceManagerHelper () at ../../nepomuk/core/resourcemanager.cpp:306
#14 operator-> () at ../../nepomuk/core/resourcemanager.cpp:310
#15 Nepomuk::ResourceManager::instance () at ../../nepomuk/core/resourcemanager.cpp:314
#16 0x0000c19e in ActivityManagerPrivate::nepomukInitialized (this=0x12c6728) at ../../activitymanager/ActivityManager.cpp:261
#17 0x000134c8 in IsBackstoreAvailable (this=0x138a060, _c=QMetaObject::InvokeMetaMethod, _id=18, _a=0xbe9ed170) at activitymanageradaptor.cpp:81
#18 ActivityManagerAdaptor::qt_metacall (this=0x138a060, _c=QMetaObject::InvokeMetaMethod, _id=18, _a=0xbe9ed170) at activitymanageradaptor.moc:237
#19 0x4012df0e in QDBusConnectionPrivate::deliverCall (this=0x12c4c08, object=0x138a060, msg=..., metaTypes=..., slotIdx=22) at qdbusintegrator.cpp:942
#20 0x4012ea90 in QDBusConnectionPrivate::activateCall (this=0x12c4c08, object=0x138a060, flags=<value optimized out>, msg=...) at qdbusintegrator.cpp:845
#21 0x4012eff6 in QDBusConnectionPrivate::activateObject (this=0x12c4c08, node=..., msg=..., pathStartPos=<value optimized out>) at qdbusintegrator.cpp:1410
#22 0x4012f12c in QDBusActivateObjectEvent::placeMetaCall (this=0x12c2470) at qdbusintegrator.cpp:1524
#23 0x40e23eb8 in QObject::event (this=0xbe9ed8f0, e=<value optimized out>) at kernel/qobject.cpp:1226
#24 0x405e5850 in QApplication::event (this=0xbe9ed8f0, e=0x12c2470) at kernel/qapplication.cpp:2503
#25 0x405e4170 in QApplicationPrivate::notify_helper (this=<value optimized out>, receiver=0xbe9ed8f0, e=0x12c2470) at kernel/qapplication.cpp:4462
#26 0x405e7198 in QApplication::notify (this=0xbe9ed8f0, receiver=0xbe9ed8f0, e=0x12c2470) at kernel/qapplication.cpp:4341
#27 0x402f7218 in KApplication::notify (this=0xbe9ed8f0, receiver=0xbe9ed8f0, event=0x12c2470) at ../../kdeui/kernel/kapplication.cpp:311
#28 0x40e16792 in QCoreApplication::notifyInternal (th...

Read more...

Changed in kdebase:
importance: Unknown → High
status: Unknown → New
Revision history for this message
In , Kde-w (kde-w) wrote :

Soprano::Client::LocalSocketClient::LocalSocketClient(QObject*) () from
/usr/lib/libsopranoclient.so.1

can you please install soprano debug package and paste a new crashlog ?

Revision history for this message
Harald Sitter (apachelogger) wrote :

still an issue with 11.10? I cannot reproduce this on any arm device here.

affects: kdebase-runtime (Ubuntu) → kde-runtime (Ubuntu)
Changed in kde-runtime (Ubuntu):
status: New → Incomplete
Revision history for this message
Tobin Davis (gruemaster) wrote :

I don't recall seeing this particular issue in the latest 11.10 Beta 2 on omap4 (panda). It may very well have been fixed. Unfortunately, my time is dedicated to testing Ubuntu (desktop & server) on arm, and I only test Kubuntu sparingly as time allows, usually for releases. I'll check it IF I test the up-coming 11.10RC.

Revision history for this message
In , Thijs (thijs22nospam) wrote :

Closing for now while waiting for a full backtrace - if possible one with KDE SC 4.7+ (or Plasma Active, of course, depending on the use case here).

Changed in kde-baseapps:
status: New → Incomplete
Revision history for this message
In , Andrew-crouthamel (andrew-crouthamel) wrote :

Hello! Plasma 4 was replaced by Plasma 5 four years ago by the KDE community. In that time we have made great strides in stability and functionality. We are closing all Plasma 4 bugs as most of them are no longer applicable to the new frameworks Plasma 5 is built upon. If you could, please re-test with the latest version of Plasma 5, and submit a new bug to "plasmashell" if you continue to have an issue. Thank you!

Changed in kde-baseapps:
status: Incomplete → Unknown
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.