file-roller crashed with SIGSEGV

Bug #179509 reported by Nazo
6
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: file-roller

open 7z archive from nautilus, double-click tar archive and then crash

ProblemType: Crash
Architecture: i386
Date: Mon Dec 31 17:28:05 2007
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/file-roller
NonfreeKernelModules: cdrom
Package: file-roller 2.20.2-1ubuntu1
PackageArchitecture: i386
ProcCmdline: file-roller file:///home/nazo/backup.tar.7z
ProcCwd: /home/nazo
ProcEnviron:
 LANGUAGE=ja_JP:ja:en_GB:en
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=ja_JP.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: file-roller
Stacktrace:
 #0 0x08076017 in ?? ()
 #1 0x080bd490 in ?? ()
 #2 0x00000010 in ?? ()
 #3 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: file-roller crashed with SIGSEGV
Uname: Linux ubuntu-note 2.6.24-2-386 #1 Thu Dec 20 16:56:01 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Revision history for this message
Nazo (lovesyao) wrote :
description: updated
description: updated
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:fr_window_open_files__extract_done_cb (archive=0x80bd490,
g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
?? () from /usr/lib/libgobject-2.0.so.0
?? ()
?? ()

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
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in file-roller:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Changed in file-roller:
status: Incomplete → Invalid
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.