nautilus crashed with SIGSEGV

Bug #1748256 reported by Guillem Solivellas
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Medium
Unassigned

Bug Description

When trying to copy files. But I know it's the use of wayland fault..

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 8 19:04:11 2018
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'249'
 b'org.gnome.nautilus.window-state' b'geometry' b"'913x598+36+32'"
InstallationDate: Installed on 2018-01-10 (29 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcCmdline: /usr/bin/nautilus --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, user)
 LANG=ca_ES.UTF-8
SegvAnalysis:
 Segfault happened at: 0x561a837cebf0: mov 0x38(%r13),%rdi
 PC (0x561a837cebf0) ok
 source "0x38(%r13)" (0x00000038) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ()
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV
UpgradeStatus: Upgraded to bionic on 2018-01-31 (8 days ago)
UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare sudo video
usr_lib_nautilus:

Revision history for this message
Guillem Solivellas (garriguer) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 stop_cache_selection_list (drag_info=0x0) at ../src/nautilus-canvas-dnd.c:385
 nautilus_canvas_container_receive_dropped_icons (y=<optimized out>, x=<optimized out>, context=0x561a8582cb70, container=0x561a8605efa0) at ../src/nautilus-canvas-dnd.c:1234
 drag_data_received_callback (widget=widget@entry=0x561a8605efa0, context=0x561a8582cb70, x=<optimized out>, y=<optimized out>, data=<optimized out>, info=<optimized out>, time=0, user_data=0x0) at ../src/nautilus-canvas-dnd.c:1856
 _gtk_marshal_VOID__OBJECT_INT_INT_BOXED_UINT_UINT (closure=0x561a869ed640, return_value=<optimized out>, n_param_values=<optimized out>, param_values=0x7ffda147a820, invocation_hint=<optimized out>, marshal_data=<optimized out>) at ../../../../gtk/gtkmarshalers.c:5566
 g_closure_invoke (closure=0x561a869ed640, return_value=0x0, n_param_values=7, param_values=0x7ffda147a820, invocation_hint=0x7ffda147a7a0) at ../../../../gobject/gclosure.c:804

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
information type: Private → Public
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.