*** This bug is a duplicate of bug 1196063 ***
    https://bugs.launchpad.net/bugs/1196063

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1196063, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1229963/+attachment/3839011/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1229963/+attachment/3839013/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1229963/+attachment/3839014/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1229963/+attachment/3839015/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1229963/+attachment/3839016/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1229963/+attachment/3839017/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1229963/+attachment/3839018/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1196063

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1229963

Title:
  nautilus crashed with SIGSEGV in g_slice_free1()

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  64-bit 1310 3.11.0-8-generic #15-Ubuntu SMP Fri Sep 20 04:11:26 UTC
  2013

  Attempted to close a nautilus window via the close icon.  Window froze.
  Temporary workaround Control Alt L to lock the screen then move the mouse, 
unlock the screen.
  Desktop is blank, but will be refreshed if nautilus is executed.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Sep 24 14:41:09 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'840x550+65+24'"
  InstallationDate: Installed on 2013-09-23 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130923.1)
  MarkForUpload: True
  ProcCmdline: nautilus -n
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f8d85047405:        mov    0x8(%rdx),%rax
   PC (0x7f8d85047405) ok
   source "0x8(%rdx)" (0x00000008) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slice_free1 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_type_free_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGSEGV in g_slice_free1()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1229963/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to