file-roller crashed with SIGSEGV in g_main_context_dispatch()

Bug #122973 reported by Paul Dufresne on 2007-06-29
412
This bug affects 6 people
Affects Status Importance Assigned to Milestone
File Roller
Expired
Critical
file-roller (Ubuntu)
Medium
Ubuntu Desktop Bugs
Declined for Karmic by Sebastien Bacher

Bug Description

Binary package hint: file-roller

Was closing the application, all had seems to go well.
First time it happened, did not try to repeat.

ProblemType: Crash
Architecture: amd64, i386
Date: Fri Jun 29 01:45:47 2007
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/file-roller
NonfreeKernelModules: cdrom
Package: File Roller 2.24.1
PackageArchitecture: amd64, i386
ProcCmdline: file-roller file:///home/paul/SecondLife_i686_1_17_2_0.tar-1
ProcCwd: /home/paul
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fr_CA.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_context_dispatch ()
 ?? () from /usr/lib/libglib-2.0.so.0
Title: file-roller crashed with SIGSEGV in g_main_context_dispatch()
Uname: Linux Arcturus 2.6.22-7-generic #1 SMP Mon Jun 25 17:07:55 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video
SegvAnalysis:
 Segfault happened at: 0x43470a: mov 0x1f8(%rax),%rdi
 PC (0x0043470a) ok
 source "0x1f8(%rax)" (0xaaaaaaaaaaaaaca2) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA

Paul Dufresne (paulduf) wrote :
Jeremy Teale (jteale) wrote :

Thanks you for reporting. Please attempt to generate a backtrace with debugging symbols by using the repository described at https://wiki.ubuntu.com/DebuggingProgramCrash. You can follow the instructions at https://wiki.ubuntu.com/Backtrace to produce a backtrace.

Changed in file-roller:
assignee: nobody → desktop-bugs
status: New → Incomplete

StacktraceTop:check_clipboard_cb (data=<value optimized out>) at fr-window.c:1864
g_timeout_dispatch (source=0xae1db0, callback=0x44af91, user_data=0x0) at /build/buildd/glib2.0-2.13.5/glib/gmain.c:3488
IA__g_main_context_dispatch (context=0x699520) at /build/buildd/glib2.0-2.13.5/glib/gmain.c:2061
g_main_context_iterate (context=0x699520, block=1, dispatch=1, self=<value optimized out>) at /build/buildd/glib2.0-2.13.5/glib/gmain.c:2694
IA__g_main_loop_run (loop=0x700960) at /build/buildd/glib2.0-2.13.5/glib/gmain.c:2898

Jeremy Teale (jteale) wrote :

I've added an upstream bug watch. It seems to have already been reported. Thanks very much for the stacktraces.

Paul Dufresne (paulduf) wrote :

Do you realize you are thanking a program?
https://launchpad.net/~apport/
It works by looking for bugs with need-[architecture]-retrace tag that is automatically added by apport itself, add the traces, and then
remove the tag.
What I find strange is that it took so long to find my bug.

Changed in file-roller:
importance: Undecided → Medium
status: Incomplete → Confirmed
Changed in fileroller:
status: Unknown → New
Changed in fileroller:
status: New → Confirmed
Changed in file-roller:
status: Confirmed → Triaged
Paul Dufresne (paulduf) wrote :

I should probably say that this bug have only happened once for me.

Walter_Wittel (wittelw) wrote :

Crashed for me on 8.04 trying to archive a crash for a different bug. I'll attach this one without compressing. Hope this helps.

Sebastien Bacher (seb128) wrote :

Don't attach crash files to the bug, use apport to send those when required, in this case the bug has a debug backtrace already so there is no need to attach a new crash

Eric Tranier (13et) wrote :

when i want download a file to the net (spicebird beta) if i choose open with archiver it's run ok if i record it to my home firefox close.

George Dumitrescu (geod) wrote :

Trying to make an archive on ftp, and crashed...

manzur (sl-solaris) on 2009-01-07
description: updated
Kees Cook (kees) on 2009-09-16
description: updated
mercedes (preciousa1237) on 2010-02-26
Changed in file-roller (Ubuntu):
status: Triaged → New
Sebastien Bacher (seb128) wrote :

There is no recent duplicate, is somebody still getting that issue in lucid?

I can only speak for myself, but I havn't seen this anymore.

Pedro Villavicencio (pedro) wrote :

marking it as fixed then and please comment when you make a change to the status. thanks.

Changed in file-roller (Ubuntu):
status: New → Fix Released
Changed in file-roller:
status: Confirmed → Invalid
Changed in file-roller:
importance: Unknown → Critical
status: Invalid → Expired
To post a comment you must log in.