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

[namespace]

Binary package hint: k3b

I tried to open the karmic64-kubuntu-isoimage with k3b.
Irony at its best...

Description: Ubuntu 9.10
Release: 9.10

k3b:
  Installiert: 1.68.0~alpha3-0ubuntu1
  Kandidat: 1.68.0~alpha3-0ubuntu1
  Versions-Tabelle:
 *** 1.68.0~alpha3-0ubuntu1 0
        500 http://de.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: amd64
Date: Mon Nov 9 20:59:44 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/k3b
NonfreeKernelModules: nvidia
Package: k3b 1.68.0~alpha3-0ubuntu1
ProcCmdline: /usr/bin/k3b /home/username/Downloads/kubuntu-9.10-desktop-amd64.iso
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x7fde587d2380 <_ZN3K3b6Device9from4ByteEPh>: movzbl (%rdi),%eax
 PC (0x7fde587d2380) ok
 source "(%rdi)" (0x01d68004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: k3b
StacktraceTop:
 K3b::Device::from4Byte(unsigned char*) ()
 K3b::Device::Device::getSupportedWriteSpeedsViaGP(QList<int>&, K3b::Device::MediaType) const () from /usr/lib/libk3bdevice.so.6
 K3b::Device::Device::determineSupportedWriteSpeeds() const () from /usr/lib/libk3bdevice.so.6
 K3b::Medium::update() () from /usr/lib/libk3b.so.6
 K3b::MediaCache::PollThread::run() ()
Title: k3b crashed with SIGSEGV in K3b::Device::from4Byte()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #450794, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.