k3b crashed with SIGSEGV in K3b::Device::from2Byte()

Bug #405603 reported by tech_support79 on 2009-07-28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Fix Released
k3b (Ubuntu)

Bug Description

Binary package hint: k3b

I tried to open K3B for the first time and got this error. It then prompted me to install additional codecs for more functionality which I did. Upon opening K3B again, mouse cursor stays on the rotating spheres.

Description: Ubuntu karmic (development branch)
Release: 9.10

Installed: 1.66.0~alpha2-0ubuntu5
  Candidate: 1.66.0~alpha2-0ubuntu5
  Version table:
 *** 1.66.0~alpha2-0ubuntu5 0
        500 http://archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
Date: Mon Jul 27 21:33:05 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/k3b
Package: k3b 1.66.0~alpha2-0ubuntu5
ProcCmdline: /usr/bin/k3b
ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
 Segfault happened at: 0xc27357 <_ZN3K3b6Device9from2ByteEPh+7>: movzbl (%eax),%edx
 PC (0x00c27357) ok
 source "(%eax)" (0x0978f002) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: k3b
 K3b::Device::from2Byte(unsigned char*) ()
 K3b::Device::Device::determineSupportedWriteSpeeds() const
 K3b::Device::Device::determineMaximalWriteSpeed() const ()
 K3b::Device::Device::init(bool) ()
Title: k3b crashed with SIGSEGV in K3b::Device::from2Byte()
Uname: Linux 2.6.31-4-generic i686
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

StacktraceTop:K3b::Device::from2Byte (d=0x9655ff8 "��\020f\005")
K3b::Device::Device::determineSupportedWriteSpeeds (
__kernel_vsyscall ()
select () from /lib/tls/i686/cmov/libc.so.6
QProcessManager::run (this=0x95ef7a0)

Changed in k3b (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Changed in k3b (Ubuntu):
status: New → Triaged
Changed in k3b:
status: Unknown → Confirmed
Changed in k3b:
status: Confirmed → Fix Released
Jonathan Thomas (echidnaman) wrote :

Should be fixed in Lucid now.

Changed in k3b (Ubuntu):
status: Triaged → Fix Released
Changed in k3b:
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.