nautilus-desktop crashed with SIGSEGV in queue_background_change()

Bug #1804506 reported by Gonçalo Marrafa
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Crashes randomly!

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: nautilus 1:3.26.4-0ubuntu7
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 21 17:29:25 2018
ExecutablePath: /usr/bin/nautilus-desktop
InstallationDate: Installed on 2017-12-14 (342 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: nautilus-desktop
SegvAnalysis:
 Segfault happened at: 0x55a3f6053bbd: mov 0x48(%rbx),%edi
 PC (0x55a3f6053bbd) ok
 source "0x48(%rbx)" (0x55a30000004d) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_by_name () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus-desktop crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to cosmic on 2018-10-19 (33 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
mtime.conffile..etc.apport.crashdb.conf: 2018-11-21T09:13:30.219492
usr_lib_nautilus:

Revision history for this message
Gonçalo Marrafa (goncalo-marrafa) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 queue_background_change (self=0x55a3f78ac5a0) at ../nautilus-desktop/nautilus-desktop-background.c:443
 g_closure_invoke (closure=0x55a3f789cde0, return_value=0x0, n_param_values=1, param_values=0x7ffdc28ac420, invocation_hint=0x7ffdc28ac3a0) at ../../../../gobject/gclosure.c:810
 signal_emit_unlocked_R (node=node@entry=0x55a3f7046010, detail=detail@entry=0, instance=instance@entry=0x55a3f70480c0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffdc28ac420) at ../../../../gobject/gsignal.c:3635
 g_signal_emit_valist (instance=instance@entry=0x55a3f70480c0, signal_id=signal_id@entry=94, detail=detail@entry=0, var_args=var_args@entry=0x7ffdc28ac618) at ../../../../gobject/gsignal.c:3391
 g_signal_emit_by_name (instance=0x55a3f70480c0, detailed_signal=<optimized out>) at ../../../../gobject/gsignal.c:3487

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
summary: - nautilus-desktop crashed with SIGSEGV in g_closure_invoke()
+ nautilus-desktop crashed with SIGSEGV in queue_background_change()
tags: removed: need-amd64-retrace
information type: Private → Public
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
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. Do you have any idea what you are doing to trigger the issue?
There are a bug on reports on the error tracker about that
https://errors.ubuntu.com/problem/85bc1f0a0712ba9b943f1d4adbf05b41c58872f0

Changed in nautilus (Ubuntu):
status: Confirmed → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

The desktop view has been removed now in disco/nautilus 3.30 which deprecates that issue

Changed in nautilus (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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