Ubuntu
nautilus package

nautilus crashed with SIGSEGV in magazine_chain_pop_head()

Bug #1196063 reported by ZhengJianhui on 2013-06-29

424

This bug affects 50 people

Affects		Status	Importance	Assigned to	Milestone
	Nautilus	New	Critical	gnome-bugs #711239
	nautilus (Ubuntu)	Invalid	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

Tags:

Revision history for this message

ZhengJianhui (zheng1733) wrote on 2013-06-29:

Dependencies.txt Edit (11.9 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (565 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (302 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (90.6 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (837 bytes, text/plain; charset="utf-8")
Registers.txt Edit (662 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (3.1 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (5.6 KiB, text/plain; charset="utf-8")
usr_lib_nautilus.txt Edit (296 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2013-06-29:

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

Revision history for this message

Apport retracing service (apport) wrote on 2013-06-29: Stacktrace.txt

Stacktrace.txt Edit (8.9 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2013-06-29: ThreadStacktrace.txt

ThreadStacktrace.txt Edit (14.4 KiB, text/plain)

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

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-07-02:

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

Changed in nautilus (Ubuntu):
status:	New → Confirmed

Apport retracing service (apport) on 2013-09-09

tags:

added: bugpattern-needed

Sebastien Bacher (seb128) on 2013-11-01

tags:

added: apport-request-retrace

Sebastien Bacher (seb128) on 2013-11-01

information type:	Private → Public
Changed in nautilus (Ubuntu):
importance:	Medium → High
status:	Confirmed → Triaged

Bug Watch Updater (bug-watch-updater) on 2013-11-01

Changed in nautilus:
importance:	Unknown → Medium
status:	Unknown → New

Bug Watch Updater (bug-watch-updater) on 2013-11-02

Changed in nautilus:
importance:	Medium → Critical

Revision history for this message

Apport retracing service (apport) wrote on 2013-12-04: Updated stack trace from duplicate bug 1257671

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

Revision history for this message

Apport retracing service (apport) wrote on 2013-12-04: Dependencies.txt

Dependencies.txt Edit (12.7 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2013-12-04: ProcMaps.txt

ProcMaps.txt Edit (145.5 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2013-12-04: Stacktrace.txt

Stacktrace.txt Edit (21.7 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2013-12-04: ThreadStacktrace.txt

#10

ThreadStacktrace.txt Edit (30.6 KiB, text/plain)

tags:

removed: apport-request-retrace

Revision history for this message

florin (florin-arjocu) wrote on 2014-02-23:

#11

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...

Apport retracing service (apport) on 2014-02-24

tags:

added: trusty

Andreas Jährig (washuu-de) on 2017-04-12

tags:

added: i686

Revision history for this message

Andreas Jährig (washuu-de) wrote on 2017-04-12:

#12

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

Revision history for this message

Sebastien Bacher (seb128) wrote on 2019-01-15:

#13

The bug is quite old and the code changed since, also there has been no new report of that specific problem nor activity for some years so assuming it has been resolved and closing the ticket. If you still get issues in newer versions feel free to open a new report though.

Changed in nautilus (Ubuntu):
status:	Triaged → Invalid

Revision history for this message

M Ludwig (m-ludwig) wrote on 2019-01-20: Re: [Bug 1196063] Re: nautilus crashed with SIGSEGV in magazine_chain_pop_head()

#14

yes, ok. seems gone annyway

thanks ;-)

michael

On 15/01/2019 17:59, Sebastien Bacher wrote:
> The bug is quite old and the code changed since, also there has been no
> new report of that specific problem nor activity for some years so
> assuming it has been resolved and closing the ticket. If you still get
> issues in newer versions feel free to open a new report though.
>
> ** Changed in: nautilus (Ubuntu)
> Status: Triaged => Invalid
>