nautilus crashed with SIGSEGV in nautilus_file_get_search_fts_snippet()

Bug #1724699 reported by shemgp on 2017-10-18
104
This bug affects 13 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
High
Unassigned

Bug Description

Searched something in nautilus and tried to drag an item from the list to a folder in the list and this crash showed up.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-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: GNOME
Date: Wed Oct 18 21:49:08 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2015-09-28 (750 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/bin/nautilus --gapplication-service
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_PH:en
 PATH=(custom, user)
 LANG=en_PH.UTF-8
SegvAnalysis:
 Segfault happened at: 0x55c069d25660 <nautilus_file_get_search_fts_snippet>: mov 0x18(%rdi),%rax
 PC (0x55c069d25660) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 nautilus_file_get_search_fts_snippet ()
 ()
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_hash_table_foreach () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: nautilus crashed with SIGSEGV in nautilus_file_get_search_fts_snippet()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker fuse kismet libvirt libvirtd lp lpadmin lxd mail mythtv netdev plugdev sambashare sbuild scanner sudo video

shemgp (shemgp) wrote :

StacktraceTop:
 nautilus_file_get_search_fts_snippet (file=0x0) at ../src/nautilus-file.c:6215
 filename_cell_data_func (column=<optimized out>, renderer=0x7f2c20015100, model=0x55c06b9fc6f0, iter=0x55c06a73eb40, view=0x55c06ada73c0) at ../src/nautilus-list-view.c:1616
 apply_cell_attributes (renderer=0x7f2c20015100, info=0x55c06baaa6c0, data=0x7fffae056660) at ././gtk/gtkcellarea.c:1257
 g_hash_table_foreach (hash_table=0x55c06ba69d80, func=func@entry=0x7f2c439a4010 <apply_cell_attributes>, user_data=user_data@entry=0x7fffae056660) at ../../../../glib/ghash.c:1614
 gtk_cell_area_real_apply_attributes (area=<optimized out>, tree_model=0x55c06b9fc6f0, iter=0x55c06a73eb40, is_expander=<optimized out>, is_expanded=<optimized out>) at ././gtk/gtkcellarea.c:1286

Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

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

Changed in nautilus (Ubuntu):
status: New → Confirmed
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 https://wiki.ubuntu.com/Bugs/Upstream/GNOME. 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
Changed in nautilus (Ubuntu):
importance: Medium → High
Download full text (3.2 KiB)

Hello Seb,
I'm sorry if I'm not so tech-savvy, but I think the bug has already been
reported here (as you surely already know) :
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1724699
I tried to follow the instructions but I see here
https://bugzilla.gnome.org/enter_bug.cgi?classification=__all that Nautilus
has been moved to GitLab.
I don't really understand what I'm supposed to do.

On Mon, Oct 23, 2017 at 11:12 PM, Sebastien Bacher <email address hidden>
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
> https://wiki.ubuntu.com/Bugs/Upstream/GNOME. 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 changed from Private to Public
>
> ** Changed in: nautilus (Ubuntu)
> Importance: Medium => High
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1725438).
> https://bugs.launchpad.net/bugs/1724699
>
> Title:
> nautilus crashed with SIGSEGV in
> nautilus_file_get_search_fts_snippet()
>
> Status in nautilus package in Ubuntu:
> Confirmed
>
> Bug description:
> Searched something in nautilus and tried to drag an item from the list
> to a folder in the list and this crash showed up.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 17.10
> Package: nautilus 1:3.26.0-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: GNOME
> Date: Wed Oct 18 21:49:08 2017
> EcryptfsInUse: Yes
> ExecutablePath: /usr/bin/nautilus
> InstallationDate: Installed on 2015-09-28 (750 days ago)
> InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
> ProcCmdline: /usr/bin/nautilus --gapplication-service
> ProcEnviron:
> XDG_RUNTIME_DIR=<set>
> SHELL=/bin/bash
> LANGUAGE=en_PH:en
> PATH=(custom, user)
> LANG=en_PH.UTF-8
> SegvAnalysis:
> Segfault happened at: 0x55c069d25660 <nautilus_file_get_search_fts_snippet>:
> mov 0x18(%rdi),%rax
> PC (0x55c069d25660) ok
> source "0x18(%rdi)" (0x00000018) not located in a known VMA region
> (needed readable region)!
> destination "%rax" ok
> SegvReason: reading NULL VMA
> Signal: 11
> SourcePackage: nautilus
> StacktraceTop:
> nautilus_file_get_search_fts_snippet ()
> ()
> () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> g_hash_table_foreach () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
> () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> Title: nautilus crashed with SIGSEGV in nautilus_file_get_search_fts_
> snippet()
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip docker fuse kismet libvirt libvirtd lp lpadmin
> lxd mail mythtv netdev plugdev sambashare sbuild scanner sudo video
>
> To manage notifications about this bug go to:
> ...

Read more...

shemgp (shemgp) wrote :

Launchpad doesn't support the new gitlab instance of Nautilus bugtracker, so here's the link: https://gitlab.gnome.org/GNOME/nautilus/issues/82

Ok, then it's all set. Thanks!

On Tue, Oct 24, 2017 at 4:33 PM, shemgp <email address hidden> wrote:

> Launchpad doesn't support the new gitlab instance of Nautilus
> bugtracker, so here's the link:
> https://gitlab.gnome.org/GNOME/nautilus/issues/82
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1725438).
> https://bugs.launchpad.net/bugs/1724699
>
> Title:
> nautilus crashed with SIGSEGV in
> nautilus_file_get_search_fts_snippet()
>
> Status in nautilus package in Ubuntu:
> Confirmed
>
> Bug description:
> Searched something in nautilus and tried to drag an item from the list
> to a folder in the list and this crash showed up.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 17.10
> Package: nautilus 1:3.26.0-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: GNOME
> Date: Wed Oct 18 21:49:08 2017
> EcryptfsInUse: Yes
> ExecutablePath: /usr/bin/nautilus
> InstallationDate: Installed on 2015-09-28 (750 days ago)
> InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
> ProcCmdline: /usr/bin/nautilus --gapplication-service
> ProcEnviron:
> XDG_RUNTIME_DIR=<set>
> SHELL=/bin/bash
> LANGUAGE=en_PH:en
> PATH=(custom, user)
> LANG=en_PH.UTF-8
> SegvAnalysis:
> Segfault happened at: 0x55c069d25660 <nautilus_file_get_search_fts_snippet>:
> mov 0x18(%rdi),%rax
> PC (0x55c069d25660) ok
> source "0x18(%rdi)" (0x00000018) not located in a known VMA region
> (needed readable region)!
> destination "%rax" ok
> SegvReason: reading NULL VMA
> Signal: 11
> SourcePackage: nautilus
> StacktraceTop:
> nautilus_file_get_search_fts_snippet ()
> ()
> () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> g_hash_table_foreach () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
> () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> Title: nautilus crashed with SIGSEGV in nautilus_file_get_search_fts_
> snippet()
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip docker fuse kismet libvirt libvirtd lp lpadmin
> lxd mail mythtv netdev plugdev sambashare sbuild scanner sudo video
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/
> 1724699/+subscriptions
>

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

Other bug subscribers