dolphin crashed with SIGSEGV in KUiServerJobTracker::Private::_k_killJob()

Bug #450923 reported by Alan Fischer e Silva on 2009-10-14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kde4libs (Ubuntu)

Bug Description

Binary package hint: kdebase

Description: Ubuntu karmic (development branch)
Release: 9.10

  Installed: 4:4.3.2-0ubuntu1
  Candidate: 4:4.3.2-0ubuntu1
  Version table:
 *** 4:4.3.2-0ubuntu1 0
        500 karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
CheckboxSubmission: 222dae1e3f7f9fb033fafa900cd74e97
CheckboxSystem: 78db936e3abcbc195af890c2658b7bc7
Date: Tue Oct 13 22:46:30 2009
Disassembly: 0x736f5020: Cannot access memory at address 0x736f5020
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/dolphin
Package: dolphin 4:4.3.2-0ubuntu1
ProcCmdline: /usr/bin/dolphin -icon system-file-manager -caption Dolphin /home/username
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
 Segfault happened at: 0x736f5020: Cannot access memory at address 0x736f5020
 PC (0x736f5020) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: kdebase
 ?? ()
 KUiServerJobTracker::Private::_k_killJob() ()
 KUiServerJobTracker::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/
 QMetaObject::activate(QObject*, int, int, void**) ()
 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/
Title: dolphin crashed with SIGSEGV in KUiServerJobTracker::Private::_k_killJob()
Uname: Linux 2.6.31-13-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

StacktraceTop:?? ()
KUiServerJobTracker::Private::_k_killJob (this=0xa849470)
KUiServerJobTracker::qt_metacall (this=0xa5d16e8,
QMetaObject::activate (sender=0xa852db0,
QMetaObject::activate (sender=0xa852db0, m=0xf7a604,

Changed in kdebase (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
affects: kdebase (Ubuntu) → kde4libs (Ubuntu)
Changed in kde4libs (Ubuntu):
importance: Medium → Low
status: New → Triaged
visibility: private → public
Jonathan Thomas (echidnaman) wrote :

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. But don't worry! This issue is being tracked by the KDE developers at:
Once fixed in KDE, it will be included in Kubuntu once the KDE version the fix is in in reaches Kubuntu.


Changed in kde4libs (Ubuntu):
status: Triaged → Invalid
Changed in kdelibs:
status: Unknown → Confirmed
Changed in kdelibs:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.