Public bug reported:

nautilus closed all of a sudden

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
Uname: Linux 4.15.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 12 01:54:19 2018
ExecutablePath: /usr/bin/nautilus
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'216'
 b'org.gnome.nautilus.window-state' b'geometry' b"'960x1011+960+27'"
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
 b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency']"
ProcCmdline: /usr/bin/nautilus --gapplication-service
 Segfault happened at: 0x7f66a9b7c207 <__GI___libc_malloc+407>: mov    
 PC (0x7f66a9b7c207) ok
 source "(%rdx)" (0x100000000) not located in a known VMA region (needed 
readable region)!
 destination "%rdi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
 tcache_get (tc_idx=0) at malloc.c:2943
 __GI___libc_malloc (bytes=1) at malloc.c:3050
 g_malloc () from /usr/lib/x86_64-linux-gnu/
 g_strdup () from /usr/lib/x86_64-linux-gnu/
 g_strsplit () from /usr/lib/x86_64-linux-gnu/
Title: nautilus crashed with SIGSEGV in tcache_get()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: nautilus (Ubuntu)
     Importance: Undecided
         Status: New

** Tags: amd64 apport-crash bionic need-amd64-retrace

** Information type changed from Private to Public

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  nautilus crashed with SIGSEGV in tcache_get()

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to