Ubuntu

file-roller crashed with SIGSEGV in egg_tree_multi_drag_button_release_event()

Reported by Eliah Kagan on 2011-02-23
336
This bug affects 37 people
Affects Status Importance Assigned to Milestone
File Roller
New
Critical
file-roller (Ubuntu)
High
Unassigned
Precise
High
Unassigned

Bug Description

Binary package hint: file-roller

I opened a .7z archive and attempted to browse its contents by double-clicking on the single top-level folder it contained. That was when this crash occurred.

This appears to be similar or identical to bug 577380, but I didn't want to mark this as a duplicate (since that bug is Invalid), and I didn't want to upload this information there (as confusion could result if the author of that report then also provides the requested information).

Please let me know if there is other information I should provide. In particular, I'd be willing to try to create a small, redistributable .7z file that produces this problem.

This crash occurred on a Maverick amd64 system with file-roller 2.32.0-0ubuntu1 and p7zip-full 9.04~dfsg.1-1.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: file-roller 2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-27.47-generic 2.6.35.11
Uname: Linux 2.6.35-27-generic x86_64
Architecture: amd64
Date: Wed Feb 23 11:58:03 2011
ExecutablePath: /usr/bin/file-roller
InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406)
ProcCmdline: file-roller /media/Alucard/OS\ Disk\ Images/Windows.FLP.7z
ProcEnviron:
 LANGUAGE=en_US.utf8
 PATH=(custom, no user)
 LANG=en_US.utf8
 LC_MESSAGES=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x41d090: mov 0x0(%rbp),%rsi
 PC (0x0041d090) ok
 source "0x0(%rbp)" (0x00000058) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 ?? ()
 _gtk_marshal_BOOLEAN__BOXED (closure=0x276e8d0, return_value=0x7fffcd0ca9b0, n_param_values=<value optimized out>, param_values=0x2754f60, invocation_hint=<value optimized out>, marshal_data=0x41d060) at /build/buildd/gtk+2.0-2.22.0/gtk/gtkmarshalers.c:86
 g_closure_invoke (closure=0x276e8d0, return_value=0x7fffcd0ca9b0, n_param_values=2, param_values=0x2754f60, invocation_hint=0x7fffcd0ca970) at /build/buildd/glib2.0-2.26.1/gobject/gclosure.c:766
 signal_emit_unlocked_R (node=0x24b1cc0, detail=<value optimized out>, instance=<value optimized out>, emission_return=<value optimized out>, instance_and_params=<value optimized out>) at /build/buildd/glib2.0-2.26.1/gobject/gsignal.c:3252
 g_signal_emit_valist (instance=0x25141a0, signal_id=<value optimized out>, detail=0, var_args=0x7fffcd0cab60) at /build/buildd/glib2.0-2.26.1/gobject/gsignal.c:2993
Title: file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
UserGroups: adm admin cdrom lpadmin plugdev sambashare

visibility: private → public

StacktraceTop:
 egg_tree_multi_drag_button_release_event (widget=0x25141a0,
 _gtk_marshal_BOOLEAN__BOXED (closure=0x276e8d0,
 g_closure_invoke (closure=0x276e8d0,
 signal_emit_unlocked_R (node=0x24b1cc0,
 g_signal_emit_valist (instance=0x25141a0,

Changed in file-roller (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace

I have just experienced this with a .tar archive as well, indicating that it is not limited to .7z archive handling, which is also borne out by the duplicates: bug 577380 (.deb), bug 731981 and bug 732175 (.tar.bz2), and bug 755699 and bug 758803 (.tgz/.tar.gz). In light of these duplicates, all but one of which were marked as duplicates by the "Apport retracing service" bot, I'm changing this bug from New to Confirmed.

Changed in file-roller (Ubuntu):
status: New → Confirmed
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

I have just reported this bug upstream (https://bugzilla.gnome.org/show_bug.cgi?id=647586) and linked the upstream report and (this) downstream report to each other. Please let me know if there is anything else I can/should do.

Sebastien Bacher (seb128) wrote :

Thank you for sending the bug to GNOME

Changed in file-roller (Ubuntu):
status: Confirmed → Triaged
Changed in file-roller:
importance: Unknown → Medium
status: Unknown → New
Changed in file-roller (Ubuntu):
assignee: nobody → Rodrigo Moya (rodrigo-moya)
status: Triaged → In Progress
Changed in file-roller (Ubuntu):
assignee: Rodrigo Moya (rodrigo-moya) → nobody

Should this be set back from In Progress to Triaged?

Steffen Röcker (sroecker) wrote :

Still crashing on oneric with file-roller 3.2.1-0ubuntu1. (bug #880879)

tags: added: oneiric
tags: added: bugpattern-needed
Changed in file-roller (Ubuntu):
importance: Medium → High
status: In Progress → Triaged
tags: added: precise rls-mgr-p-tracking
tags: added: apport-request-retrace

Package: file-roller 3.4.0-0ubuntu1
ProcCmdline: file-roller /home/username/Downloads/Roboto_Hinted_20111129.zip

tags: removed: apport-request-retrace
summary: - file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
+ file-roller crashed with SIGSEGV in
+ egg_tree_multi_drag_button_release_event()
tags: added: quantal running-unity
Changed in file-roller (Ubuntu):
assignee: nobody → brian lee buhr (snakefire976)
tags: added: raring
dino99 (9d9) on 2013-07-08
tags: removed: oneiric
tags: removed: maverick
tags: added: saucy
tags: added: trusty
Changed in file-roller:
importance: Medium → Critical
Changed in file-roller (Ubuntu):
status: Triaged → New
Changed in file-roller (Ubuntu):
status: New → Triaged
assignee: brian lee buhr (snakefire976) → nobody
To post a comment you must log in.