The bug didn't get activity/new duplicates for some years and the
nautilus code saw quite some changes since which probably deprecated the
issue so closing it. If it's still a problem in recent Ubuntu/nautilus
version please submit a new report

** Changed in: nautilus (Ubuntu)
       Status: Confirmed => Invalid

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.

  nautilus crashed with SIGSEGV in g_slice_alloc()

Status in nautilus package in Ubuntu:

Bug description:
  crash came on login after reboot.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
  Uname: Linux 3.11.0-9-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Mon Sep 30 02:20:31 2013
  ExecutablePath: /usr/bin/nautilus
   b'org.gnome.nautilus.window-state' b'geometry' b"'723x403+641+336'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'185'
  InstallationDate: Installed on 2012-02-20 (587 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
  MarkForUpload: True
  ProcCmdline: nautilus -n
   Segfault happened at: 0x7f006d31c9c7 <g_slice_alloc+167>:    mov    
   PC (0x7f006d31c9c7) ok
   source "(%rbx)" (0x73756c697475616e) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
   g_slice_alloc () from /lib/x86_64-linux-gnu/
   g_slice_alloc0 () from /lib/x86_64-linux-gnu/
   g_type_create_instance () from /usr/lib/x86_64-linux-gnu/
   ?? () from /usr/lib/x86_64-linux-gnu/
   g_object_newv () from /usr/lib/x86_64-linux-gnu/
  Title: nautilus crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: Upgraded to saucy on 2013-09-21 (8 days ago)
  UserGroups: lpadmin sambashare sudo

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to