file-roller crashed with SIGSEGV in g_main_context_dispatch()

Bug #122973 reported by Paul Dufresne
412
This bug affects 6 people
Affects Status Importance Assigned to Milestone
File Roller
Expired
Critical
file-roller (Ubuntu)
Fix Released
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

Tags: apport-crash
Revision history for this message
Paul Dufresne (paulduf) wrote :
Revision history for this message
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
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

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

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Jeremy Teale (jteale) wrote :

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

Revision history for this message
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
Revision history for this message
Paul Dufresne (paulduf) wrote :

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

Revision history for this message
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.

Revision history for this message
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

Revision history for this message
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.

Revision history for this message
George Dumitrescu (geod) wrote :

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

manzur (sl-solaris)
description: updated
Kees Cook (kees)
description: updated
mercedes (preciousa1237)
Changed in file-roller (Ubuntu):
status: Triaged → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

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

Revision history for this message
John Doe (jodo-deactivatedaccount) wrote :

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

Revision history for this message
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.
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.