Public bug reported:

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

** Affects: file-roller (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-crash need-amd64-retrace saucy

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1203755

Title:
  file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1203755/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to