file-roller crashed with SIGSEGV

Bug #179690 reported by Carlos Renê
112
This bug affects 4 people
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: file-roller

file-roller crashed with SIGSEGV

ProblemType: Crash
Architecture: i386
Date: Wed Dec 26 16:17:03 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:///media/ilha01/usbfloppy-sdb/Mercyful%20Fate%20-%20Come%20To%20The%20Sabbath.rar
ProcCwd: /home/ilha01
ProcEnviron:
 LANGUAGE=pt_BR:pt:pt_PT
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: file-roller
Stacktrace:
 #0 0x08075123 in ?? ()
 #1 0x080b7010 in ?? ()
 #2 0x0808e05e in ?? ()
 #3 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: file-roller crashed with SIGSEGV
Uname: Linux Server 2.6.24-2-generic #1 SMP Thu Dec 20 17:36:12 GMT 2007 i686 GNU/Linux
UserGroups: adm audio cdrom dialout dip fax floppy fuse plugdev scanner tape

Revision history for this message
Carlos Renê (slipttees) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:fr_window_stoppable_cb (command=0x8256450, stoppable=0, window=0xbff4bfe8)
get_selection_data_from_clipboard_data (window=0x0, data=0x8107800)
g_io_channel_read_line () from /usr/lib/libglib-2.0.so.0
?? () from /usr/lib/libglib-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. Also a few easy steps to trigger the crash are needed, thanks you.

Changed in file-roller:
status: New → Incomplete
importance: Undecided → Medium
assignee: nobody → desktop-bugs
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.