Ubuntu
nautilus package

nautilus crashed with SIGSEGV in widget_needs_widget_path (shutdown?)

Bug #1857539 reported by Sosha
188
This bug affects 29 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Triaged
High
Unassigned

Bug Description

after turn on pc

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 25 01:52:06 2019
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:

InstallationDate: Installed on 2019-12-22 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221)
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: 0x7f3fb437f962: mov 0x380(%rax),%rax
 PC (0x7f3fb437f962) 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 libvirt lpadmin lxd plugdev sambashare sudo
separator:

usr_lib_nautilus:

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

StacktraceTop:
 widget_needs_widget_path (widget=0x55e4375bb830) at ../../../../gtk/gtkcsswidgetnode.c:171
 gtk_css_widget_node_init_matcher (node=0x55e436d33080, matcher=0x7ffde83d1110) at ../../../../gtk/gtkcsswidgetnode.c:190
 gtk_css_node_init_matcher (matcher=0x7ffde83d1110, cssnode=0x55e436d33080) at ../../../../gtk/gtkcssnode.c:1416
 gtk_css_node_create_style (cssnode=0x55e436d33080) at ../../../../gtk/gtkcssnode.c:370
 gtk_css_node_real_update_style (cssnode=0x55e436d33080, change=12884901887, timestamp=0, style=0x55e437c03c20) 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 : Re: nautilus crashed with SIGSEGV

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

Changed in nautilus (Ubuntu):
status: New → Confirmed
Revision history for this message
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.

Changed in nautilus (Ubuntu):
importance: Medium → Low
status: Confirmed → Incomplete
Revision history for this message
Alex Murray (alexmurray) wrote :

@seb128 - I just noticed this - Apport popped up just after login saying Files (aka nautilus) had crashed - and pointed at this bug report. This was the first time I have seen it so not sure if it is reproducible and I didn't take any particular steps to make it occur.

Revision history for this message
Ljiljan Veselinovic (ljiljan-veselinovic) wrote :

Aftering leaving my computer turned on while Dropbox was uploading 2000 files...

Revision history for this message
Nicolas DERIVE (kalon33) wrote :

@alexmurray: same pattern for me. It probably happened at shutdown according to timestamp, and Apport popped up just after login with Nautilus crash.

Revision history for this message
Sebastien Bacher (seb128) wrote :

looks similar to bug #1726129

Márcio Oliveira Corbolan (marciocorbolan)
Changed in nautilus (Ubuntu):
assignee: nobody → Márcio Oliveira Corbolan (marciocorbolan)
Revision history for this message
arks (arksnorman) wrote :

Me too here. Happened at login

Revision history for this message
wgroiss (wolfgang-groiss-gmx) wrote :

Same for me: Bug happend immediately after login in Ubuntu 20.04.
I only started 3 apps after login:
Files/Nautilus
Thunderbird
Chromium
But no action in the apps before bud appears.
And it is reproducible.

Sebastien Bacher (seb128)
summary: - nautilus crashed with SIGSEGV
+ nautilus crashed with SIGSEGV in widget_needs_widget_path (shutdown?)
Revision history for this message
Ken Wagner (beaucoder) wrote :

Nautilus can't see other wireless computers, or if it can see them it will not connect to them.

No wireless connection happens.

On rare occasions the two computers will connect wirelessly after a half our or hour of waiting.

Revision history for this message
wgroiss (wolfgang-groiss-gmx) wrote :

For me it seems, that bug happens only at login after a kernel update followed by a reboot to finish update.
"normal" (Re)boot without update => no bug.
And i use Dropbox to (Autostart at Login).

Apport retracing service (apport)
tags: added: groovy
Sebastien Bacher (seb128)
Changed in nautilus (Ubuntu):
assignee: Márcio Oliveira Corbolan (marciocorbolan) → nobody
status: Incomplete → Triaged
importance: Low → High
Revision history for this message
Lyubomir (mystiquewolf) wrote :

Saame. After login with no apps started.

Revision history for this message
Edson T. Marques (edsontmarques) wrote :

Noticed here too. Fresh new groovy installation this weekend.

Revision history for this message
haldrik (haldrik) wrote :

I have this same bug in my system even when I had Ubuntu 19.10, the upgrade to Ubuntu 20.04 didn't resolved the problem.

My only clue is that this could be a problem with Dropbox, but I'm not sure because I disabled libnautilus-dropbox.so.bak versions 2.0 and 3.0 renaming the file, that's made the Dropbox menu to disappear of Nautilus, but the crash with SIGSEGV after a clean start of the computer it's still happening.

SegvAnalysis and Strace:
https://i.postimg.cc/FzpCG0Rp/Captura-de-pantalla-de-2020-06-12-09-47-13.png
https://i.postimg.cc/K8wq9GZ6/Captura-de-pantalla-de-2020-06-12-09-47-43.png
https://i.postimg.cc/k4djmTRw/Captura-de-pantalla-de-2020-06-12-09-48-22.png
https://i.postimg.cc/3JbnR8Dk/Captura-de-pantalla-de-2020-06-12-09-48-55.png

Revision history for this message
Mark Lagace (marklagace) wrote :

I don't believe this is related to Dropbox, as I had what appears to be the same bug happen to me (crash with SIGSEGV, very shortly after login) but do not have Dropbox installed. This is a clean install of 20.04.

Revision history for this message
Mohammad Sabbir Hasan (sabbir4world) wrote :

I have the same issue. I do have dropbox installed though. But doesn't look like it is because of dropbox.

Apport retracing service (apport)
tags: added: bugpattern-needed
tags: added: jammy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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