extundelete crashed with SIGSEGV in ext2fs_extent_get()

Bug #1039698 reported by Jalakas
34
This bug affects 5 people
Affects Status Importance Assigned to Milestone
extundelete (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Crash on startup

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: extundelete 0.2.0-2
ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
Uname: Linux 3.5.0-11-generic x86_64
ApportVersion: 2.4-0ubuntu8
Architecture: amd64
Date: Tue Aug 21 19:08:48 2012
ExecutablePath: /usr/bin/extundelete
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: extundelete /dev/sda1 --restore-all
SegvAnalysis:
 Segfault happened at: 0x7f1872df35dd <ext2fs_extent_get+701>: mov 0x8(%rbx),%eax
 PC (0x7f1872df35dd) ok
 source "0x8(%rbx)" (0x196027200000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: extundelete
StacktraceTop:
 ext2fs_extent_get () from /lib/x86_64-linux-gnu/libext2fs.so.2
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: extundelete crashed with SIGSEGV in ext2fs_extent_get()
UpgradeStatus: Upgraded to quantal on 2012-08-02 (19 days ago)
UserGroups:

Revision history for this message
Jalakas (jalakas) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #956820, 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.

visibility: private → public
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in extundelete (Ubuntu):
status: New → Confirmed
Revision history for this message
lostwong (lostwong) wrote :

I think this might be fixable by updating the package to use v0.2.4.

I ran into this issue using both Ubuntu 12.04 and Fedora 17. I ended up compiling v0.2.4 from sourceforge.net (which was the most current at the time) on Fedora 17 and that ran fine.

Revision history for this message
Tristan Schmelcher (tschmelcher) wrote :

Confirmed that 0.2.4 compiled from source fixes the problem on Ubuntu 12.10 too (and it successfully recovered my file!).

Revision history for this message
Nobuto Murata (nobuto) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like the issue is fixed in 0.2.0-2.1/raring. Could you try it?

Changed in extundelete (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for extundelete (Ubuntu) because there has been no activity for 60 days.]

Changed in extundelete (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.