nautilus crashed with SIGSEGV in mount_cb()

Bug #1756521 reported by starkus
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Low
Unassigned

Bug Description

After updating and upgrading the system (18.04 without proposed updates enabled), I opened up some programs to check how they react. nautilus, gnome-tweak-tool, gnome-software, firefox, thunderbird, gnome-control-center,gnome-disk-utility... In nautilus I decided to mount all my hard drives. (8 partitions). After mounting the third and trying to mount the fourth nautilus crashed, while in the background the other programs were opened or were still loading...

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.2-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Mar 17 11:19:26 2018
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
 b'org.gnome.nautilus.window-state' b'geometry' b"'890x547+652+84'"
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
InstallationDate: Installed on 2017-12-27 (79 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/nautilus --gapplication-service
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x55f45f325dbe: andb $0xfd,0xc0(%rbx)
 PC (0x55f45f325dbe) ok
 source "$0xfd" ok
 destination "0xc0(%rbx)" (0xfffffffffffffec0) not located in a known VMA region (needed writable region)!
SegvReason: writing 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 () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to bionic on 2018-02-24 (20 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_nautilus:

Revision history for this message
starkus (starkus) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 mount_cb (item=<optimized out>, row=0x55f460b9c570) at ../src/gtk/nautilusgtkplacesview.c:1584
 g_closure_invoke (closure=0x55f460a33660, return_value=0x0, n_param_values=1, param_values=0x7ffc643260f0, invocation_hint=0x7ffc64326070) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x55f460117050, detail=detail@entry=0, instance=instance@entry=0x55f46064b4f0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffc643260f0) at ../../../../gobject/gsignal.c:3635
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7ffc643262b0) at ../../../../gobject/gsignal.c:3391
 g_signal_emit (instance=instance@entry=0x55f46064b4f0, signal_id=<optimized out>, detail=detail@entry=0) at ../../../../gobject/gsignal.c:3447

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 crashed with SIGSEGV in g_closure_invoke()
+ nautilus crashed with SIGSEGV in mount_cb()
tags: removed: need-amd64-retrace
information type: Private → Public
Changed in nautilus (Ubuntu):
importance: Medium → Low
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.