nautilus crashed with SIGSEGV

Bug #1856696 reported by Mohammad Hizzani
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

crashed with also gnome-shell crashed

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.4-0~ubuntu18.04.4
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 17 14:30:26 2019
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2019-10-06 (71 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcCmdline: /usr/bin/nautilus --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7f7c4aeae628: mov 0x90(%r14),%rsi
 PC (0x7f7c4aeae628) ok
 source "0x90(%r14)" (0x00000090) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 gdk_display_get_event () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: nautilus crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_nautilus:

Revision history for this message
Mohammad Hizzani (moh.hiz) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gdk_x11_device_manager_xi2_translate_event (translator=<optimized out>, display=<optimized out>, event=<optimized out>, xevent=<optimized out>) at ../../../../../gdk/x11/gdkdevicemanager-xi2.c:1711
 _gdk_x11_event_translator_translate (translator=translator@entry=0x55e612017230, display=0x55e611fce0b0, xevent=xevent@entry=0x7ffc4de50880) at ../../../../../gdk/x11/gdkeventtranslator.c:51
 gdk_event_source_translate_event (xevent=0x7ffc4de50880, event_source=0x55e611f8b4f0) at ../../../../../gdk/x11/gdkeventsource.c:230
 _gdk_x11_display_queue_events (display=0x55e611fce0b0) at ../../../../../gdk/x11/gdkeventsource.c:341
 gdk_display_get_event (display=display@entry=0x55e611fce0b0) at ../../../../gdk/gdkdisplay.c:438

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
Sebastien Bacher (seb128) wrote :

Thanks, it's a gtk issue and already reported as bug #1837428

Changed in nautilus (Ubuntu):
status: New → Invalid
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.