kded4 crashed at update

Bug #277619 reported by RYan
248
This bug affects 10 people
Affects Status Importance Assigned to Milestone
kdelibs
Fix Released
High
kde4libs (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: kde4libs

I was applying the suggested updates to Kubuntu in Adept on the morning that Intrepid Ibex went beta when kded4 crashed. That's it.

ProblemType: Crash
Architecture: i386
Disassembly: 0xb7f07430:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/kded4
Package: kdelibs-bin 4:4.1.2-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: kded4
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kde4libs
Stacktrace: #0 0xb7f07430 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: kded4 crashed with SIGSEGV
Uname: Linux 2.6.27-4-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Revision history for this message
RYan (ryanv) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()

Changed in kde4libs:
importance: Undecided → Low
status: New → Triaged
Changed in kdelibs:
status: Unknown → In Progress
Revision history for this message
Bruce Miller (brm0423) wrote : Re: kded4 crashed with SIGSEGV

I suspect that the crash which apport is reporting on my system is the same as this one. It happened on the first login to KDE after I had applied a dist-upgrade on 2008-10-07, including release of the new kernel build 2.6.27-6. I had just rebooted in order to apply the kernel upgrade.

Revision history for this message
James Rosser (jarosser06) wrote :

I had the same thing happen on mine, i was running the latest upgrades through the terminal though instead of adept.

Revision history for this message
Olivier (olidel) wrote :

Same here.

Thanks

Revision history for this message
Valentin Longchamp (longfield) wrote :

Same happens here for Hardy with this ppa (deb http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu hardy main
) that I guess give the same kde4 packages that for Intrepid.

This bug is really annoying, not being able to use keyboard shortcuts is a killer for me.

Here is the error message I get:

kded(29721) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: "NetworkManager"
ASSERT: "d->keyToAction.value(key) == ad" in file /build/buildd/kde4libs-4.1.2/kdeui/shortcuts/kdedglobalaccel.cpp, line 412
valentin@thinkpad:~$ KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kded4 path = <unknown> pid = 29721
sock_file=/home/valentin/.kde4/socket-thinkpad/kdeinit4__0
kded(29748) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: "NetworkManager"
ASSERT: "d->keyToAction.value(key) == ad" in file /build/buildd/kde4libs-4.1.2/kdeui/shortcuts/kdedglobalaccel.cpp, line 412

Revision history for this message
Valentin Longchamp (longfield) wrote :

I solved it by removing the .kde4/share/config/kglobalshortcutsrc file, log out and then reapply default global shortcuts after login.

Changed in kde4libs:
importance: Low → Medium
Revision history for this message
LimCore (limcore) wrote :

bug#284184 can be a duplicate of this

Revision history for this message
Ralph (ralph-puncher-deactivatedaccount) wrote :

I was part the way through Synaptic updating Jaunty Alpha 6 to latest updates from the main server on March 21, 2009 and received the message:
"Sorry, the program kded4 closed unexpectedly."

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

I haven't seen this at all in KDE 4.3.x, and we haven't received any apport reports this cycle for it either. I'm inclined to believe that this is fixed.

Changed in kde4libs (Ubuntu):
status: Triaged → Fix Released
Changed in kdelibs:
status: In Progress → Fix Released
Changed in kdelibs:
importance: Unknown → High
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.