nautilus crashed with SIGABRT

Bug #1774193 reported by Cristian Aravena Romero on 2018-05-30
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)

Bug Description


I do not know why it happened.

Cristian Aravena Romero (caravena)

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: nautilus 1:3.26.3-0ubuntu4
Uname: Linux 4.16.12-041612-generic x86_64
ApportVersion: 2.20.10-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed May 30 09:42:46 2018
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2017-10-13 (228 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
ProcCmdline: /usr/bin/nautilus --gapplication-service
Signal: 6
SourcePackage: nautilus
 wl_proxy_marshal_array_constructor_versioned () at /usr/lib/x86_64-linux-gnu/
 wl_proxy_marshal_constructor () at /usr/lib/x86_64-linux-gnu/
 () at /usr/lib/x86_64-linux-gnu/
 () at /usr/lib/x86_64-linux-gnu/
Title: nautilus crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo

 wl_abort (fmt=fmt@entry=0x7f5415b59032 "Error sending request: %s\n") at ../src/wayland-util.c:417
 wl_proxy_marshal_array_constructor_versioned (proxy=proxy@entry=0x55939a53b4f0, opcode=opcode@entry=0, args=args@entry=0x7ffc4797bba0, interface=interface@entry=0x7f5415d5c220 <wl_surface_interface>, version=3) at ../src/wayland-client.c:754
 wl_proxy_marshal_array_constructor (proxy=proxy@entry=0x55939a53b4f0, opcode=opcode@entry=0, args=args@entry=0x7ffc4797bba0, interface=interface@entry=0x7f5415d5c220 <wl_surface_interface>) at ../src/wayland-client.c:694
 wl_proxy_marshal_constructor (proxy=0x55939a53b4f0, opcode=opcode@entry=0, interface=0x7f5415d5c220 <wl_surface_interface>) at ../src/wayland-client.c:828
 wl_compositor_create_surface (wl_compositor=<optimized out>) at /usr/include/wayland-client-protocol.h:1195

Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Sebastien Bacher (seb128) wrote :

It looks like a wayland error and upstream closed it because they need more details, doing the same here

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

Other bug subscribers