nautilus crashed with SIGSEGV in magazine_chain_pop_head()

Bug #1196063 reported by ZhengJianhui on 2013-06-29
426
This bug affects 50 people
Affects Status Importance Assigned to Milestone
Nautilus
New
Critical
nautilus (Ubuntu)
High
Unassigned

Bug Description

I don't know what happen.
I am using the Ubuntu Software Center and Firefox while the error occur.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
Uname: Linux 3.10.0-1-generic x86_64
ApportVersion: 2.10.2-0ubuntu3
Architecture: amd64
Date: Sat Jun 29 23:33:41 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'839x550+309+129'"
InstallationDate: Installed on 2013-04-26 (63 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x7fb13c83c095: mov 0x8(%rdx),%rax
 PC (0x7fb13c83c095) 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/libpangoft2-1.0.so.0
Title: nautilus crashed with SIGSEGV in g_slice_free1()
UpgradeStatus: Upgraded to saucy on 2013-06-29 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark

ZhengJianhui (zheng1733) wrote :

StacktraceTop:
 magazine_chain_pop_head (magazine_chunks=<synthetic pointer>) at /build/buildd/glib2.0-2.37.3/./glib/gslice.c:550
 magazine_chain_prepare_fields (magazine_chunks=0x0) at /build/buildd/glib2.0-2.37.3/./glib/gslice.c:625
 magazine_cache_push_magazine (ix=13, magazine_chunks=<optimized out>, count=7) at /build/buildd/glib2.0-2.37.3/./glib/gslice.c:697
 thread_memory_magazine2_unload (ix=<optimized out>, tmem=<optimized out>) at /build/buildd/glib2.0-2.37.3/./glib/gslice.c:815
 g_slice_free1 (mem_size=<optimized out>, mem_block=0x1ba6e50) at /build/buildd/glib2.0-2.37.3/./glib/gslice.c:1106

Changed in nautilus (Ubuntu):
importance: Undecided → Medium
summary: - nautilus crashed with SIGSEGV in g_slice_free1()
+ nautilus crashed with SIGSEGV in magazine_chain_pop_head()
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nautilus (Ubuntu):
status: New → Confirmed
tags: added: bugpattern-needed
tags: added: apport-request-retrace
information type: Private → Public
Changed in nautilus (Ubuntu):
importance: Medium → High
status: Confirmed → Triaged
Changed in nautilus:
importance: Unknown → Medium
status: Unknown → New
Changed in nautilus:
importance: Medium → Critical

Package: nautilus 1:3.8.2-0ubuntu2.1
ProcCmdline: nautilus -n

tags: removed: apport-request-retrace
florin (florin-arjocu) wrote :

Too bad these bugs still exist after 8-9 months as I could see (I just reported https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1283623 and it seems to be a duplicate of this one). I guess nothing will happen very soon as in 2 months there will be a new Ubuntu with newer Nautilus & kernel...

tags: added: trusty
tags: added: i686
Andreas Jährig (washuu-de) wrote :

Happens only on instances of nautilus which I started with gksu. Maybe I shouldn't do that.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.