file-roller crashed with SIGSEGV in g_closure_invoke()

Bug #425052 reported by Jayson Reis on 2009-09-06
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: file-roller

Just opened a file.

ProblemType: Crash
Architecture: amd64
Date: Sat Sep 5 23:24:01 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/file-roller
NonfreeKernelModules: nvidia
Package: file-roller 2.27.91-0ubuntu1
ProcCmdline: file-roller /home/username/Programas/skype-2.1.0.47.tar.bz2
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=pt_BR.UTF-8
 LANGUAGE=pt_BR.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
SegvAnalysis:
 Segfault happened at: 0x41aa10 <gtk_icon_set_add_source@plt+37304>: mov 0x0(%rbp),%rsi
 PC (0x0041aa10) ok
 source "0x0(%rbp)" (0x00000092) 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-9-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #350289, 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.

visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers