kded4 crashed with SIGSEGV (NOT post-dist-upgrade restart)

Bug #391244 reported by Terry
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kde4libs (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kde4libs

I've restarted Jaunty (Kubuntu 9.04) maybe half a dozen times since upgrading from Hardy (skipping Intrepid) over a month ago, so I don't think this has to do with the dist. upgrade.

I had booted into Jaunty 40 mins earlier and had one terminal window open since then, not running anything.

I opened Konqueror and had done nothing more than open and look at a few of the title bar menus when I got the crash report. Unfortunately I can't tell you the version of the package I'm using because what the crash report pre-filled for me as the package name doesn't seem to be a package >.> ...
terry@moose:~$ apt-cache policy kde4libs
W: Unable to locate package kde4libs

Searching for that package in aptitude doesn't work either.

Only possibly relevant change I know of is that I installed all available package updates last night before rebooting this morning. I know a kernel image was one of them.

ProblemType: Crash
Architecture: i386
Disassembly: 0xb8070430:
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/kded4
Package: kdelibs-bin 4:4.2.2-0ubuntu5
ProcCmdline: kded4
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kde4libs
Stacktrace: #0 0xb8070430 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: kded4 crashed with SIGSEGV
Uname: Linux 2.6.28-13-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Terry (wearenotamused) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()

tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Thank you for taking the time to report this bug and helping to make Kubuntu better. However, the automated crash report didn't yield the required information to properly handle this bug. (The backtrace is useless.) Please go ahead and submit a new crash report if it crashes again with the latest available version of the package. Thanks in advance for your cooperation and understanding.

Changed in kde4libs (Ubuntu):
status: New → Invalid
visibility: private → public
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.