file-roller crashed with SIGSEGV in egg_tree_multi_drag_button_press_event()

Bug #1216330 reported by Dimitri John Ledkov
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

opened a tar.xz with .git/* in it.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: file-roller 3.8.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6
Uname: Linux 3.11.0-3-generic x86_64
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Sat Aug 24 15:54:47 2013
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2012-01-12 (589 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318)
MarkForUpload: True
ProcCmdline: file-roller /tmp/ocaml-estring_20130822.orig.tar.xz
SegvAnalysis:
 Segfault happened at: 0x41cb30: mov (%rbx),%rsi
 PC (0x0041cb30) ok
 source "(%rbx)" (0x00000047) 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=0x16e86f0, return_value=0x7fffded2a840, n_param_values=<optimised out>, param_values=0x7fffded2a8f0, invocation_hint=<optimised out>, marshal_data=<optimised out>) at /build/buildd/gtk+3.0-3.8.2/./gtk/gtkmarshalers.c:85
 g_closure_invoke (closure=0x16e86f0, return_value=0x7fffded2a840, n_param_values=2, param_values=0x7fffded2a8f0, invocation_hint=0x7fffded2a890) at /build/buildd/glib2.0-2.37.6/./gobject/gclosure.c:777
 signal_emit_unlocked_R (node=node@entry=0x1294810, detail=detail@entry=0, instance=instance@entry=0x14345a0, emission_return=emission_return@entry=0x7fffded2a9c0, instance_and_params=instance_and_params@entry=0x7fffded2a8f0) at /build/buildd/glib2.0-2.37.6/./gobject/gsignal.c:3582
 g_signal_emit_valist (instance=<optimised out>, signal_id=<optimised out>, detail=<optimised out>, var_args=var_args@entry=0x7fffded2aa88) at /build/buildd/glib2.0-2.37.6/./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 autopilot cdrom dip kvm libvirtd lpadmin plugdev sambashare sbuild sudo

Revision history for this message
Dimitri John Ledkov (xnox) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 egg_tree_multi_drag_button_press_event (widget=0x14345a0, event=0x47, data=<optimized out>) at eggtreemultidnd.c:365
 g_closure_invoke (closure=0x2, return_value=0x7fffded2a840, n_param_values=3738347760, param_values=0x7fffded2a890, invocation_hint=0x0) at /build/buildd/glib2.0-2.37.6/./gobject/gclosure.c:777
 signal_emit_unlocked_R (node=node@entry=0x1294810, detail=detail@entry=0, instance=instance@entry=0x14345a0, emission_return=emission_return@entry=0x7fffded2a9c0, instance_and_params=instance_and_params@entry=0x7fffded2a8f0) at /build/buildd/glib2.0-2.37.6/./gobject/gsignal.c:3582
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fffded2aa88) at /build/buildd/glib2.0-2.37.6/./gobject/gsignal.c:3336
 g_signal_emit (instance=instance@entry=0x14345a0, signal_id=<optimized out>, detail=detail@entry=0) at /build/buildd/glib2.0-2.37.6/./gobject/gsignal.c:3382

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in file-roller (Ubuntu):
importance: Undecided → Medium
summary: - file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
+ file-roller crashed with SIGSEGV in
+ egg_tree_multi_drag_button_press_event()
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 file-roller (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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