kded4 crashes with a segfault
Bug #989052 reported by
Jan Schneider
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plasma-widget-networkmanagement (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
After upgrading to Kubuntu 12.04 kded4 keeps crashing as soon as it's started.
---
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
DistroRelease: Ubuntu 12.04
Package: plasma-
PackageArchitec
ProcEnviron:
LANGUAGE=
TERM=xterm
PATH=(custom, user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcVersionSign
Tags: precise
Uname: Linux 3.2.0-24-generic x86_64
UpgradeStatus: Upgraded to precise on 2012-04-26 (15 days ago)
UserGroups: adm admin cdrom dialout dip fuse libvirtd lpadmin mythtv plugdev sambashare
affects: | kde4libs (Ubuntu) → plasma-widget-networkmanagement (Ubuntu) |
To post a comment you must log in.
If it helps, this is the standard output when starting kded4 manually:
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. terface: :Changed( ) muon-notifier" :deviceFound( Device* ) to BlueDevilDaemon ::deviceFound( Device* ) :stopDiscovery( ) :fromDbusMap: Setting "802-1x" not initialized :fromDbusMap: Setting "802-1x" not initialized :fromDbusMap: Setting "802-1x" not initialized :fromDbusMap: Setting "802-1x" not initialized :fromDbusMap: Setting "802-1x" not initialized :fromDbusMap: Setting "802-11- wireless- security" not initialized :fromDbusMap: Setting "802-1x" not initialized :fromDbusMap: Setting "802-11- wireless- security" not initialized :fromDbusMap: Setting "802-1x" not initialized :fromDbusMap: Setting "802-1x" not initialized :fromDbusMap: Setting "802-11- wireless- security" not initialized :fromDbusMap: Setting "802-1x" not initialized :fromDbusMap: Setting "802-11- wireless- security" not initialized :fromDbusMap: Setting "802-1x" not initialized :fromDbusMap: Setting "802-11- wireless- security" not initialized :fromDbusMap: Setting "802-1x" not initialized :fromDbusMap: Setting "802-1x" not initialized :fromDbusMap: Setting "802-11- wireless- security" not initialized
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Object::connect: No such signal QDBusAbstractIn
QDBusObjectPath: invalid path ""
QDBusObjectPath: invalid path "/modules/
kded(9818): The kded module name ' "muon-notifier" ' is invalid!
QObject::connect: Cannot connect (null):
QObject::connect: Cannot connect QTimer::timeout() to (null):
No new release at this moment
kded(9818)/Network Management (NetworkManager backend) ConnectionDbus:
kded(9818)/Network Management (NetworkManager backend) ConnectionDbus:
kded(9818)/Network Management (NetworkManager backend) ConnectionDbus:
kded(9818)/Network Management (NetworkManager backend) ConnectionDbus:
kded(9818)/Network Management (NetworkManager backend) ConnectionDbus:
kded(9818)/Network Management (NetworkManager backend) ConnectionDbus:
kded(9818)/Network Management (NetworkManager backend) ConnectionDbus:
kded(9818)/Network Management (NetworkManager backend) ConnectionDbus:
kded(9818)/Network Management (NetworkManager backend) ConnectionDbus:
kded(9818)/Network Management (NetworkManager backend) ConnectionDbus:
kded(9818)/Network Management (NetworkManager backend) ConnectionDbus:
kded(9818)/Network Management (NetworkManager backend) ConnectionDbus:
kded(9818)/Network Management (NetworkManager backend) ConnectionDbus:
kded(9818)/Network Management (NetworkManager backend) ConnectionDbus:
kded(9818)/Network Management (NetworkManager backend) ConnectionDbus:
kded(9818)/Network Management (NetworkManager backend) ConnectionDbus:
kded(9818)/Network Management (NetworkManager backend) ConnectionDbus:
kded(9818)/Network Management (NetworkManager backend) ConnectionDbus:
kded(9818)/Network Management (NetworkManager backend) ConnectionDbus...