dolphin crashed with SIGSEGV in QTimer::setInterval()

[Carl Beech]

Binary package hint: kdebase

Description: Ubuntu karmic (development branch)
Release: 9.10

kdebase:
  Installed: 4:4.2.98-0ubuntu3
  Candidate: 4:4.2.98-0ubuntu3
  Version table:
 *** 4:4.2.98-0ubuntu3 0
        600 http://archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status
     4:4.2.2-0ubuntu4 0
        500 http://im.archive.ubuntu.com jaunty/main Packages

Performed while copying files from external USB hard drive

ProblemType: Crash
Architecture: i386
Date: Mon Aug 3 20:43:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/dolphin
NonfreeKernelModules: nvidia
Package: dolphin 4:4.2.98-0ubuntu3
ProcCmdline: dolphin -session 1010413c143dc000124864091400000039890033_1249246985_269153
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
SegvAnalysis:
 Segfault happened at: 0x722f2f0 <_ZN6QTimer11setIntervalEi+32>: mov 0x8(%esi),%eax
 PC (0x0722f2f0) ok
 source "0x8(%esi)" (0x40580cd4) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: kdebase
StacktraceTop:
 QTimer::setInterval(int) () from /usr/lib/libQtCore.so.4
 QTimer::start(int) () from /usr/lib/libQtCore.so.4
 ?? () from /usr/lib/libkio.so.5
 ?? () from /usr/lib/libkio.so.5
 KIO::CopyJob::qt_metacall(QMetaObject::Call, int, void**) ()
Title: dolphin crashed with SIGSEGV in QTimer::setInterval()
Uname: Linux 2.6.31-4-generic i686
UserGroups: adm admin audio cdrom dialout lpadmin mythtv netdev plugdev sambashare video

[Apport retracing service (apport)]

StacktraceTop:QTimer::setInterval (this=0x40580ccc, msec=200) at kernel/qtimer.cpp:361
QTimer::start (this=0x40580ccc, msec=200)
KIO::CopyJobPrivate::slotResultConflictCopyingFiles (
KIO::CopyJobPrivate::slotResultCopyingFiles (
KIO::CopyJob::qt_metacall (this=0x9e59cd8,

[Jonathan Thomas (echidnaman)]

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: http://bugs.kde.org/show_bug.cgi?id=199532
Once fixed in KDE, it will be included in Kubuntu once the KDE version the fix is in in reaches Kubuntu.

Thanks!