nautilus crashed with SIGSEGV in nautilus_list_model_get_all_iters_for_file() when trying to open a password-protected 7z archive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
== Steps to reproduce ==
1. Create a password protected 7z archive: `echo hello >hello.txt; 7z a hello.7z hello.txt -ppassword`
2. Left-click the archive in Nautilus
== What happens ==
Nautilus shows an empty window, and together with gnome-shell they eat up the CPU until you close the Nautilus window. Alternatively, a crash report prompt appears.
== What I expect to happen ==
Preferably to prompt for a password and then open the archive contents. At the very least to not eat all the CPU, and inform the user that Nautilus is incapable of handling this file format.
== Other info ==
I don't have Dropbox installed unlike in bug #1734891.
Upstream issue: https:/
Red Hat issue: https:/
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.3-0ubuntu1
ProcVersionSign
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 9 15:02:59 2018
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2016-10-13 (542 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcCmdline: /usr/bin/nautilus --gapplication-
ProcEnviron:
XDG_RUNTIME_
SHELL=/bin/bash
PATH=(custom, user)
LANG=fi_FI.UTF-8
SegvAnalysis:
Segfault happened at: 0x55785367f8b8 <nautilus_
PC (0x55785367f8b8) ok
source "0x10(%rbx)" (0xffffffffffff
destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
nautilus_
nautilus_
()
()
g_closure_invoke () at /usr/lib/
Title: nautilus crashed with SIGSEGV in nautilus_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom debian-transmission dip lp lpadmin lxd plugdev sambashare ssh sudo vboxusers
usr_lib_nautilus:
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 #1734891, 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.