kcmshell4 crashed with SIGSEGV in KonqHistoryProviderPrivate::notifyClear() clearing history

Bug #445515 reported by fritzvantom
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
KDE Base
Fix Released
High
kdebase (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: kdebase-runtime

(k)ubuntu 9.10 beta
kdebase-runtime 4:4.3.2-0ubuntu1

ProblemType: Crash
Architecture: i386
Date: Wed Oct 7 17:00:06 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kcmshell4
NonfreeKernelModules: nvidia
Package: kdebase-runtime 4:4.3.2-0ubuntu1
ProcCmdline: /usr/bin/kcmshell4 kcmhistory
ProcEnviron:
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
 LANGUAGE=
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SegvAnalysis:
 Segfault happened at: 0xd02ed7 <_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+103>: mov 0x4(%esi),%eax
 PC (0x00d02ed7) ok
 source "0x4(%esi)" (0x0000017d) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kdebase-runtime
StacktraceTop:
 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
 ?? () from /usr/lib/libkonq.so.5
 ?? () from /usr/lib/kde4/kcm_history.so
 ?? () from /usr/lib/kde4/kcm_history.so
 QMetaObject::activate(QObject*, int, int, void**) ()
Title: kcmshell4 crashed with SIGSEGV in QMetaObject::activate()
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
fritzvantom (fritz-van-tom) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:QMetaObject::activate (sender=0x179, m=0x2da1ca0, local_signal_index=3,
KonqHistoryProviderPrivate::notifyClear (this=0x179)
HistorySidebarConfig::slotClearHistory (this=0x98374f8)
HistorySidebarConfig::qt_metacall (this=0x98374f8,
QMetaObject::activate (sender=0x99aed20,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in kdebase-runtime (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Changed in kdebase-runtime (Ubuntu):
importance: Medium → Low
status: New → Triaged
affects: kdebase-runtime (Ubuntu) → kdebase (Ubuntu)
visibility: private → public
summary: - kcmshell4 crashed with SIGSEGV in QMetaObject::activate()
+ kcmshell4 crashed with SIGSEGV in
+ KonqHistoryProviderPrivate::notifyClear() clearing history
Changed in kdebase (Ubuntu):
importance: Low → Medium
Xiegai Shan (xiegaishan)
Changed in kdebase (Ubuntu):
assignee: nobody → Xiegai Shan (p.s.)
Xiegai Shan (xiegaishan)
Changed in kdebase (Ubuntu):
status: Triaged → In Progress
Xiegai Shan (xiegaishan)
Changed in kdebase (Ubuntu):
assignee: Xiegai Shan (p.s.) → nobody
status: In Progress → Confirmed
Changed in kdebase:
status: Unknown → Fix Released
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Fixed in KDE 4.4 RC2 and 4.3.5.

Changed in kdebase (Ubuntu):
status: Confirmed → Fix Released
Changed in kdebase:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
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.