← Back to team overview

ubuntustudio-bugs team mailing list archive

[Bug 746202] Re: kactivitymanagerd crashed on login on armel

 

Launchpad has imported 4 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=269802.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2011-03-31T05:41:52+00:00 Tobin Davis wrote:

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 (this=<value optimized out>, receiver=<value optimized out>, event=0x12c2470) at kernel/qcoreapplication.cpp:731
#29 0x40e18cc4 in sendEvent (receiver=0x0, event_type=0, data=0x1292c78) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#30 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x1292c78) at kernel/qcoreapplication.cpp:1372
#31 0x40e33a04 in sendPostedEvents (s=0x12ce910) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#32 postEventSourceDispatch (s=0x12ce910) at kernel/qeventdispatcher_glib.cpp:277
#33 0x415057f6 in g_main_context_dispatch () from /lib/arm-linux-gnueabi/libglib-2.0.so.0
#34 0x41505d40 in ?? () from /lib/arm-linux-gnueabi/libglib-2.0.so.0
#35 0x41505d40 in ?? () from /lib/arm-linux-gnueabi/libglib-2.0.so.0
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Reported using DrKonqi

Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
runtime/+bug/746202/comments/2

------------------------------------------------------------------------
On 2011-04-08T00:22:21+00:00 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 ?

Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
runtime/+bug/746202/comments/3

------------------------------------------------------------------------
On 2011-12-03T10:53:16+00:00 Thijs 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).

Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
runtime/+bug/746202/comments/6

------------------------------------------------------------------------
On 2018-09-04T19:06:09+00:00 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!

Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
runtime/+bug/746202/comments/7


** Changed in: kde-baseapps
       Status: Incomplete => Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to kde-runtime in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/746202

Title:
  kactivitymanagerd crashed on login on armel

Status in KDE Base:
  Unknown
Status in kde-runtime package in Ubuntu:
  Incomplete

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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-baseapps/+bug/746202/+subscriptions