crash on .jp2 files in jpc_qmfb_join_colgrp
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jasper (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Binary package hint: nautilus
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: nautilus 1:2.30.0-0ubuntu3
ProcVersionSign
Uname: Linux 2.6.32-19-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sun Apr 4 13:29:52 2010
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
ProcCmdline: nautilus
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f23eb32ae1c <jpc_qmfb_
PC (0x7f23eb32ae1c) ok
source "%r8" ok
destination "(%r10,%rax,1)" (0x7f23fabee970) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
jpc_qmfb_
jpc_ns_synthesize () from /usr/lib/
jpc_tsfb_
jpc_tsfb_
?? () from /usr/lib/
Title: nautilus crashed with SIGSEGV in jpc_qmfb_
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
summary: |
- nautilus crashed with SIGSEGV in jpc_qmfb_join_colgrp() + crash on .jp2 files in jpc_qmfb_join_colgrp |
Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace. wiki.ubuntu. com/DebuggingPr ogramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.
Please try to obtain a backtrace manually following the instructions at http://