gvfsd-archive crashed with SIGSEGV in __archive_check_magic()

Bug #267420 reported by Sune Keller
52
This bug affects 6 people
Affects Status Importance Assigned to Milestone
libarchive (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: gvfs

Occurred after deleting .tar.gz archive which was mounted and displayed in a Nautilus browser window.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/gvfs/gvfsd-archive
Package: gvfs-backends 0.99.6-0ubuntu3
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/gvfs/gvfsd-archive file=file:///home/username/Desktop/DarkGlass_Reworked.tar.gz
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games:/opt/thinlinc/bin
 LANG=en_DK.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 __archive_check_magic () from /usr/lib/libarchive.so.2
 archive_read_next_header () from /usr/lib/libarchive.so.2
 ?? ()
 ?? ()
 ?? ()
Title: gvfsd-archive crashed with SIGSEGV in __archive_check_magic()
Uname: Linux 2.6.27-2-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev pulse pulse-rt sambashare scanner tape video

Tags: apport-crash
Revision history for this message
Sune Keller (sune-keller) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:__archive_check_magic (a=0x9e54180, magic=14594245, state=6, function=0xb7e92b71 "archive_read_next_header")
archive_read_next_header (_a=0x9e54180, entryp=0xb7b52278) at libarchive/archive_read.c:300
do_open_for_read (backend=0x9e40818, job=0x9e530f0, filename=0x9e54470 "/DarkGlass_Reworked/index.desktop")
run (job=0x9e530f0) at gvfsjobopenforread.c:134
g_vfs_job_run (job=0x9e530f0) at gvfsjob.c:198

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gvfs:
importance: Undecided → Medium
Revision history for this message
Sebastien Bacher (seb128) wrote :

the crash is a libarchive one

Revision history for this message
Andreas Henriksson (andreas-fatal) wrote :

This segfault is the internal consistency checker being triggered. The bug is likely in gvfs(d-archive) which probably passes in a corrupt struct archive.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in libarchive (Ubuntu):
status: New → Confirmed
Revision history for this message
Savvas Radevic (medigeek) wrote :

Can you please check with libarchive 3.x (libarchive-dev / libarchive12) in ubuntu 12.04?

Changed in libarchive (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Sune Keller (sune-keller) wrote :

I can confirm that gvfsd-archive no longer chrashes with libarchive12 3.0.3-6ubuntu1 in Ubuntu precise/12.04.

$ apt-cache policy libarchive12
libarchive12:
  Installed: 3.0.3-6ubuntu1
  Candidate: 3.0.3-6ubuntu1
  Version table:
 *** 3.0.3-6ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

The archive stays mounted and I can stil browse it (i.e. in Nautilus it shows under places and I can navigate its folder structure), but _obviously_ the files cannot be found when trying to read them e.g. when trying to copy a file or reading it in gedit. Unmounting the archive afterwards also goes just fine.

I'm wondering, though, if from a user experience point of view it wouldn't be smarter to either not allow deleting a mounted archive, or to umount it when it is deleted.

tl;dr: Fixed.

Revision history for this message
Savvas Radevic (medigeek) wrote :

Thank you for testing! I'll set it as "Fix released" (I'm not sure whether it should be marked as "Invalid"). The suggestion you mentioned is valid, but should be filed upstream: http://libarchive.github.com/ - http://code.google.com/p/libarchive/issues/list (The issue tracker is still at google code)

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