file-roller crashed with SIGSEGV in g_action_map_lookup_action()

Bug #1725017 reported by Ersin on 2017-10-19
This bug affects 11 people
Affects Status Importance Assigned to Milestone
File Roller
file-roller (Ubuntu)

Bug Description

Description: Ubuntu 17.10
Release: 17.10

  Installed: 3.26.1-0ubuntu1
  Candidate: 3.26.1-0ubuntu1
  Version table:
 *** 3.26.1-0ubuntu1 500
        500 artful/main amd64 Packages
        100 /var/lib/dpkg/status

Don't know how this happned.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: file-roller 3.26.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 18:23:52 2017
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: file-roller /home/username/Downloads/discord-0.0.2.tar.gz
 Segfault happened at: 0x7f4a0e78271c <g_action_map_lookup_action+28>: mov 0x10(%rax),%rax
 PC (0x7f4a0e78271c) ok
 source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
 g_action_map_lookup_action () from /usr/lib/x86_64-linux-gnu/
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/
Title: file-roller crashed with SIGSEGV in g_action_map_lookup_action()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Ersin (ersin-ertan) wrote :

 g_action_map_lookup_action (action_map=0x55dd7ccb23e0, action_name=0x55dd7c76b0fc "edit-paste") at ../../../../gio/gactionmap.c:87
 fr_window_enable_action (window=0x55dd7ccb23e0, action_name=0x55dd7c76b0fc "edit-paste", enabled=0) at fr-window.c:691
 g_closure_invoke (closure=0x55dd7ce7be90, return_value=0x0, n_param_values=2, param_values=0x7ffeeda4afc0, invocation_hint=0x7ffeeda4af40) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x55dd7cd32e80, detail=detail@entry=0, instance=instance@entry=0x55dd7cd645b0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffeeda4afc0) at ../../../../gobject/gsignal.c:3635
 g_signal_emit_valist (instance=0x55dd7cd645b0, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7ffeeda4b190) at ../../../../gobject/gsignal.c:3391

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

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

information type: Private → Public
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in file-roller (Ubuntu):
status: New → Confirmed
tags: added: bionic
Tom Reynolds (tomreyn) wrote :

Reported upstream on the Gnome projects' new 'bug tracker' (Gitlab) - for which no bug watch exists in Launchpad (to date):

Changed in file-roller:
importance: Unknown → Medium
status: Unknown → Confirmed
Sebastien Bacher (seb128) wrote :


Changed in file-roller (Ubuntu):
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.