file-roller crashed with SIGSEGV in memmove()

Bug #402841 reported by Xavier Fung
44
This bug affects 8 people
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
New
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: file-roller

No ZIP file is made after selecting several files in Nautilus and click on "compress" in the context menu. Here are the steps:

1) Open Nautilus, and select some files to create an archive
2) Right click on the selected files and select "Compress ..."
3) A dialog box comes up asking you for the filename
4) When you go ahead, there is no ZIP file created and file-roller crashes. Nautilus does not have any issue.

ProblemType: Crash
Architecture: i386
Date: Wed Jul 22 11:08:21 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/file-roller
Package: file-roller 2.27.2-0ubuntu1
ProcCmdline: file-roller --default-dir=file:///media/hda5/Share/Works/chargebacks/801616877 --add file:///media/hda5/Share/Works/chargebacks/801616877/confirm_from_worldpay.txt file:///media/hda5/Share/Works/chargebacks/801616877/from_client_1.txt file:///media/hda5/Share/Works/chargebacks/801616877/from_client_2.txt file:///media/hda5/Share/Works/chargebacks/801616877/from_worldpay.txt file:///media/hda5/Share/Works/chargebacks/801616877/system_confirm_email_1.txt file:///media/hda5/Share/Works/chargebacks/801616877/system_confirm_email_2.txt
ProcEnviron:
 LANGUAGE=zh_HK.UTF-8
 PATH=(custom, no user)
 LANG=zh_HK.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-2.17-generic
SegvAnalysis:
 Segfault happened at: 0x3ddb3a <memmove+58>: movsb %ds:(%esi),%es:(%edi)
 PC (0x003ddb3a) ok
 source "%ds:(%esi)" (0x00e2da59) ok
 destination "%es:(%edi)" (0x00e2da59) in non-writable VMA region: 0x00a62000-0x00ec1000 r-xp /usr/lib/libgtk-x11-2.0.so.0.1705.0
SegvReason: writing VMA /usr/lib/libgtk-x11-2.0.so.0.1705.0
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 memmove () from /lib/tls/i686/cmov/libc.so.6
 g_strchug () from /usr/lib/libglib-2.0.so.0
 ?? ()
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: file-roller crashed with SIGSEGV in memmove()
Uname: Linux 2.6.31-2-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare scanner video

Revision history for this message
Xavier Fung (xavier114fch) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
tags: added: need-i386-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

visibility: private → public
Changed in file-roller (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Medium
status: New → Incomplete
tags: removed: need-i386-retrace
Revision history for this message
Alexey Kotlyarov (koterpillar) wrote :

I am affected by this bug. Here is a backtrace with debugging symbols and Valgrind log. Actually, when using Valgrind, program *did not* crash and created the archive.

Revision history for this message
Alexey Kotlyarov (koterpillar) wrote :

Valgrind log.

Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your work, there is no crash in this valgrind log though and you lack debug symbols for glib and gtk

Revision history for this message
Alexey Kotlyarov (koterpillar) wrote :

When using Valgrind (as described in wiki), crash does not happen. Attaching a (hopefully) better backtrace.

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you get a valgrind log anyway? those often workaround the crash but still list the issue

Revision history for this message
Alexey Kotlyarov (koterpillar) wrote :

Sure.

Changed in file-roller (Ubuntu):
status: Incomplete → New
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.