nautilus crashed with SIGSEGV

Bug #1844026 reported by Sosha
46
This bug affects 10 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

after restart gnome-shell with "alt + F2 and type 'r' in command"

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: nautilus 1:3.34.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 15 05:26:31 2019
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(892, 544)'
InstallationDate: Installed on 2019-07-14 (62 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190701)
ProcCmdline: /usr/bin/nautilus --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7eff95c1a8e2: mov 0x380(%rax),%rax
 PC (0x7eff95c1a8e2) ok
 source "0x380(%rax)" (0x00000380) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
Title: nautilus crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

usr_lib_nautilus:

Revision history for this message
Sosha (soshaw) wrote :
Sosha (soshaw)
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 widget_needs_widget_path (widget=0x5563b43c8840) at ../../../../gtk/gtkcsswidgetnode.c:171
 gtk_css_widget_node_init_matcher (node=0x5563b43d5a20, matcher=0x7fff324e0240) at ../../../../gtk/gtkcsswidgetnode.c:190
 gtk_css_node_init_matcher (matcher=0x7fff324e0240, cssnode=0x5563b43d5a20) at ../../../../gtk/gtkcssnode.c:1416
 gtk_css_node_create_style (cssnode=0x5563b43d5a20) at ../../../../gtk/gtkcssnode.c:370
 gtk_css_node_real_update_style (cssnode=0x5563b43d5a20, change=12884901888, timestamp=0, style=0x5563b4062b90) at ../../../../gtk/gtkcssnode.c:425

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nautilus (Ubuntu):
status: New → Confirmed
Revision history for this message
Tom Reynolds (tomreyn) wrote :

This apparently made it into 19.10 beta1, my UEFI booted 19.04 beta1 VM (running on VirtualBox 6.0.12, Ubuntu 18.04.3 / Linux 5.3 host) reported a duplicate.

tags: added: bionic
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.