file-roller crashed with SIGSEGV in g_closure_invoke()

Bug #502104 reported by Vadim Peretokin
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: file-roller

Tried opening an archive, it somehow confused which folders went where when I opened it and crashed shortly after.

Worked fine on the second try though.

ProblemType: Crash
Architecture: amd64
Date: Fri Jan 1 11:35:59 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/file-roller
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate amd64 (20091020.3)
NonfreeKernelModules: nvidia
Package: file-roller 2.28.1-0ubuntu1
ProcCmdline: file-roller /home/username/Downloads/UbuntuSun-v4.tar.gz
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
SegvAnalysis:
 Segfault happened at: 0x41aa90: mov 0x0(%rbp),%rsi
 PC (0x0041aa90) ok
 source "0x0(%rbp)" (0x00000074) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
Title: file-roller crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.31-17-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare video

Revision history for this message
Vadim Peretokin (vperetokin) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:egg_tree_multi_drag_button_release_event (widget=0x129a030,
_gtk_marshal_BOOLEAN__BOXED (closure=0x15b87b0,
g_closure_invoke ()
?? () from /usr/lib/libgobject-2.0.so.0
g_signal_emit_valist ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in file-roller (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

Changed in file-roller (Ubuntu):
status: New → Invalid
visibility: private → public
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.