nautilus crashed with SIGSEGV in widget_needs_widget_path

Bug #1726129 reported by Bob Pok
54
This bug affects 15 people
Affects Status Importance Assigned to Milestone
Nautilus
Fix Released
Unknown
gtk+3.0 (Ubuntu)
Confirmed
Undecided
Unassigned
nautilus (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

https://gitlab.gnome.org/GNOME/gtk/issues/2457

---

https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea

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
CrashCounter: 1
CurrentDesktop: Budgie:GNOME
Date: Sun Oct 22 15:30:05 2017
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2017-10-19 (3 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
ProcCmdline: nautilus --new-window
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fe0115bd2a4: mov 0x380(%rax),%rax
 PC (0x7fe0115bd2a4) 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 /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/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

Revision history for this message
Bob Pok (78luphr0rnk2nuqimstywepozxn9kl19tqh0tx66b5dki1xxsh5mkz9gl21a5rlwfnr8jn6ln0m3jxne2k9-8hkfclc5t-a811i2i3ytqlsztthjth0svbccw8inm65tmkqp9sarr553jq53in4xm1m8wn3o4rlwaer06ogwvqwv9mrqo) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 widget_needs_widget_path (widget=0x5632e928d2e0) at ././gtk/gtkcsswidgetnode.c:171
 gtk_css_widget_node_init_matcher (node=0x5632e9253c30, matcher=0x7ffe9fcbf120) at ././gtk/gtkcsswidgetnode.c:190
 gtk_css_node_init_matcher (matcher=0x7ffe9fcbf120, cssnode=0x5632e9253c30) at ././gtk/gtkcssnode.c:1412
 gtk_css_node_create_style (cssnode=0x5632e9253c30) at ././gtk/gtkcssnode.c:370
 gtk_css_node_real_update_style (cssnode=0x5632e9253c30, change=12884967264, timestamp=0, style=0x5632e92a4e80) 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
Sebastien Bacher (seb128) wrote : Re: nautilus crashed with SIGSEGV

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.

Changed in nautilus (Ubuntu):
importance: Medium → Low
status: New → Incomplete
summary: - nautilus crashed with SIGSEGV
+ nautilus crashed with SIGSEGV in widget_needs_widget_path
Revision history for this message
Sebastien Bacher (seb128) wrote :
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]

Changed in nautilus (Ubuntu):
status: Incomplete → Expired
description: updated
tags: added: eoan
description: updated
Revision history for this message
El jinete sin cabeza (ejsc) wrote :

This still happens in eoan.

Changed in nautilus (Ubuntu):
status: Expired → Confirmed
description: updated
Changed in nautilus (Ubuntu):
status: Confirmed → Triaged
Changed in nautilus:
status: Unknown → New
tags: added: focal
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gtk+3.0 (Ubuntu):
status: New → Confirmed
Changed in nautilus:
status: New → Fix Released
Revision history for this message
El jinete sin cabeza (ejsc) wrote :
description: updated
no longer affects: nautilus
Changed in nautilus:
status: Unknown → New
tags: added: groovy
Revision history for this message
Sebastien Bacher (seb128) wrote :

upstream believes the gtk4 version in kinetic should resolve the issue

Changed in nautilus (Ubuntu):
status: Triaged → Fix Released
Changed in nautilus:
status: New → Fix Released
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Indeed there are no crashes after version 42.x

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This is now the #1 crash in jammy.

tags: added: jammy
tags: removed: artful eoan groovy
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.