nautilus crashed with SIGSEGV in nautilus_query_matches_string()

Bug #1761532 reported by alex cuellar on 2018-04-05
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Medium
Unassigned

Bug Description

Nautilus error

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 5 10:38:47 2018
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'238'
 b'org.gnome.nautilus.window-state' b'geometry' b"'890x543+95+55'"
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
InstallationDate: Installed on 2018-03-11 (24 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
ProcCmdline: /usr/bin/nautilus --gapplication-service
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=es_PE:es
 PATH=(custom, user)
 LANG=es_PE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x5611943fb070 <nautilus_query_matches_string>: cmpq $0x0,0x18(%rdi)
 PC (0x5611943fb070) ok
 source "$0x0" ok
 destination "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 nautilus_query_matches_string ()
 ()
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 start_thread (arg=0x7f62f70c5700) at pthread_create.c:463
 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Title: nautilus crashed with SIGSEGV in nautilus_query_matches_string()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_nautilus:

alex cuellar (puca-sunqu) wrote :

StacktraceTop:
 nautilus_query_matches_string (query=0x0, string=0x7f62f0059180 "2015-02-27 12.46.21.jpg") at ../src/nautilus-query.c:370
 recent_thread_func (user_data=<optimized out>) at ../src/nautilus-search-engine-recent.c:148
 g_thread_proxy (data=0x7f62f002ae80) at ../../../../glib/gthread.c:784
 start_thread (arg=0x7f62f70c5700) at pthread_create.c:463
 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Changed in nautilus (Ubuntu):
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
Sebastien Bacher (seb128) wrote :

Still happening with 3.30 in Fedora, https://retrace.fedoraproject.org/faf/reports/2418334/

information type: Private → Public
Changed in nautilus (Ubuntu):
assignee: Marco Trevisan (Treviño) (3v1n0) → nobody
status: New → Confirmed
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

I think I've fixed this upstream (https://gitlab.gnome.org/GNOME/nautilus/merge_requests/335) but it has not been released in 3.30.x branches, while will be fixed in first 3.31.x we release.

tags: added: fixed-3.31.x fixed-upstream
Changed in nautilus (Ubuntu):
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers