This bug was fixed in the package nautilus - 1:3.26.4-0~ubuntu18.04.1
---------------
nautilus (1:3.26.4-0~ubuntu18.04.1) bionic; urgency=medium
* New upstream release: 3.26.4 (LP: #1782681, LP: #1765776)
* debian/patches/query-add-recursive-flags-and-use-it-in-search-engines.patch,
debian/patches/0016-search-engine-add-a-recent-search-engine-listing-Gtk.patch,
debian/patches/0018-search-engine-add-locate-based-search-engine.patch:
- Follow nautilus settings to search only in current folder (LP: #1767027).
This doesn't apply to gnome-shell search provider for indexed searches.
*
debian/patches/0017-recent-add-function-to-update-manager-on-file-rename.patch:
- Updated to respect upstream requested changes
*
debian/patches/nautilusgtkplacesview-show-error-if-volume-is-not-mounted.patch:
- don't crash if selecting a volume that is not mounted (LP: #1764779)
*
debian/patches/file-view-Always-unset-pending_selection-after-freeing-it.patch:
- don't crash when try to select a file multiple times in a single run
(LP: #1713581)
*
debian/patches/Revert-Revert-files-view-Remove-new-empty-folder-name-sug.patch,
debian/patches/Revert-Revert-nautilus-file-Don-t-show-thumbnails-for-the.patch:
- Reverts the reverts introduced in 2.26.3.1 as they are in ubuntu already
* debian/patches/clear_pending_selection.patch,
debian/patches/git_middle_tab.patch,
debian/patches/server_list_segfault.patch:
- Patches removed as they are already applied upstream
-- Marco Trevisan (Treviño) <ma...@ubuntu.com> Fri, 20 Jul 2018
04:52:45 +0200
** Changed in: nautilus (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1713581
Title:
nautilus crashed with SIGSEGV in
g_type_check_instance_is_fundamentally_a()
Status in nautilus package in Ubuntu:
Fix Released
Status in nautilus source package in Bionic:
Fix Released
Bug description:
[ Impact ]
Nautilus crashes when trying to open a folder selecting a file, when
another has already been selected before and the current folder didn't
finish loading.
[ Test case ]
It's not easy to verify this without hacking the code to change the scenario,
but an example could be launching quickly:
nautilus /usr/bin/true &
nautilus /usr/bin/false
At the second command nautilus could crash.
[ Regression potential ]
Calling nautilus with a file argument might not select that file
--
Upstream bug: https://gitlab.gnome.org/GNOME/nautilus/issues/295
Upstream MR: https://gitlab.gnome.org/GNOME/nautilus/merge_requests/277
---
https://errors.ubuntu.com/problem/ef1ce30f6325c683b207fd96a3be93eda5384054
Fixed in
https://gitlab.gnome.org/GNOME/nautilus/commit/b6691821b86460bf9d4caa6391666ae506a743c5
no idea,sorry
ProblemType: CrashDistroRelease: Ubuntu 17.10
Package: nautilus 1:3.25.90-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 29 00:07:44 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2017-08-09 (19 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170807)
ProcCmdline: /usr/bin/nautilus --gapplication-service
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_DIR=<set>
PATH=(custom, no user)
LANG=de_DE.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f8b19a60d27
<g_type_check_instance_is_fundamentally_a+7>: mov (%rdi),%rdx
PC (0x7f8b19a60d27) ok
source "(%rdi)" (0x00000002) not located in a known VMA region (needed
readable region)!
destination "%rdx" ok
SegvReason: reading NULL VMASignal: 11SourcePackage: nautilus
StacktraceTop:
g_type_check_instance_is_fundamentally_a () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_list_copy_deep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? ()
?? ()
Title: nautilus crashed with SIGSEGV in
g_type_check_instance_is_fundamentally_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1713581/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
