file-roller crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu GNOME |
New
|
Undecided
|
Unassigned | ||
file-roller (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Crash occurs when selecting two or more zip files for extraction using the context menu. Once the files are extracted two confirmation dialogue boxes are presented but one is above the second one that says "Extraction completed successfully".
Clicking on Close on the first one dismisses the dialogue box, with the second one now visible. When clicking on Close for the second one, it hangs for a short while (1-2 seconds) and afterwards a crash report is ready to be submitted.
This issue is reproducible on my end. Only tested with zip files, not sure if other archiving formats are affected as well.
Old bug report: bug 350289
Upstream bug report, which can be re-opened for GNOME >= 3.0.1: https:/
ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: file-roller 3.22.3-1ubuntu1
ProcVersionSign
Uname: Linux 4.10.0-14-generic x86_64
ApportVersion: 2.20.4-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Apr 4 18:23:06 2017
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2017-04-02 (2 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
ProcCmdline: file-roller --extract-here --notify file://
ProcEnviron:
XDG_RUNTIME_
SHELL=/usr/bin/zsh
LANGUAGE=en_ZA:en
PATH=(custom, user)
LANG=en_ZA.UTF-8
Signal: 11
SourcePackage: file-roller
StacktraceTop:
?? ()
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
g_signal_emit () from /usr/lib/
Title: file-roller crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to zesty on 2017-04-02 (1 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
description: | updated |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1603324, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.