ark crashed with SIGSEGV in ~KDialog()

Bug #450167 reported by JR
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
KDE Utilities
Fix Released
High
kdeutils (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

had a zip file open and viewed a text file (ark's preview feature). i switched to another application. after some time, i found that ark crashed.

ProblemType: Crash
Architecture: amd64
Date: Tue Oct 13 10:17:13 2009
Disassembly: 0x71: Cannot access memory at address 0x71
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/ark
NonfreeKernelModules: nvidia
Package: ark 4:4.3.2-0ubuntu1
ProcCmdline: /usr/bin/ark -caption Ark /home/username/Desktop/archive.zip
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
SegvAnalysis:
 Segfault happened at: 0x71: Cannot access memory at address 0x71
 PC (0x00000071) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: kdeutils
StacktraceTop:
 ?? ()
 ~KDialog (this=0x7fff4e09d050,
 ?? () from /usr/lib/kde4/libarkpart.so
 ?? () from /usr/lib/kde4/libarkpart.so
 ?? () from /usr/lib/kde4/libarkpart.so
Title: ark crashed with SIGSEGV in ~KDialog()
Uname: Linux 2.6.31-13-generic x86_64
UserGroups: adm admin cdrom dialout kvm libvirtd lpadmin plugdev sambashare vboxusers

Revision history for this message
JR (juergen-richtsfeld) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
~KDialog (this=0x7fff4e09d050)
ArkViewer::view (filename=@0x7fff4e09d1f0,
Part::slotPreviewExtracted (this=0xdcd2c0,
Part::qt_metacall (this=0xdcd2c0,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
affects: ubuntu → kdeutils (Ubuntu)
Changed in kdeutils (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Fixed in KDE 4.3.4.

Changed in kdeutils (Ubuntu):
status: New → Fix Released
Changed in kdeutils:
status: Unknown → Fix Released
Changed in kdeutils:
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.