file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()

Bug #1203755 reported by Eliah Kagan
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
New
Undecided
Unassigned

Bug Description

In a Saucy amd64 system I opened a .tar.xz archive (which I'd previously created myself on another system with "tar cf ..." followed by "xz -9v ...") and double-clicked on the single folder it contained, to view its contents in file-roller itself before performing any extractions. file-roller crashed.

I believe this is bug 723841 but I am not 100% sure without looking at a good symbolic trace, so I'm posting this just in case. I'll try to compare the trace as soon as there's a good one, unless someone else (or the Apport retracing service bot) does so first.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: file-roller 3.8.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1
Uname: Linux 3.10.0-4-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Sat Jul 20 22:21:49 2013
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2013-07-17 (5 days ago)
InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130716)
MarkForUpload: True
ProcCmdline: file-roller file:///home/username/Downloads/Maplesoft.Maple.v13.0.LINUX.x64-TBE.tar.xz
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x41cb30: mov (%rbx),%rsi
 PC (0x0041cb30) ok
 source "(%rbx)" (0x00000048) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 ?? ()
 _gtk_marshal_BOOLEAN__BOXED (closure=0x2998cb0, return_value=0x7fff97fb62e0, n_param_values=<optimized out>, param_values=0x7fff97fb6390, invocation_hint=<optimized out>, marshal_data=<optimized out>) at /build/buildd/gtk+3.0-3.8.2/./gtk/gtkmarshalers.c:85
 g_closure_invoke (closure=0x2998cb0, return_value=0x7fff97fb62e0, n_param_values=2, param_values=0x7fff97fb6390, invocation_hint=0x7fff97fb6330) at /build/buildd/glib2.0-2.37.3/./gobject/gclosure.c:777
 signal_emit_unlocked_R (node=node@entry=0x265a990, detail=detail@entry=0, instance=instance@entry=0x27be610, emission_return=emission_return@entry=0x7fff97fb6460, instance_and_params=instance_and_params@entry=0x7fff97fb6390) at /build/buildd/glib2.0-2.37.3/./gobject/gsignal.c:3582
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fff97fb6528) at /build/buildd/glib2.0-2.37.3/./gobject/gsignal.c:3336
Title: file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :
information type: Private → Public
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 #723841, 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.

tags: removed: need-amd64-retrace
Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

Comparison of the stack trace here to https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/723841/comments/3, in combination with the similarity in circumstances triggering the crash, is sufficient to convince me this is the same bug.

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.