nautilus crashed with SIGABRT in __libc_message()

Bug #920662 reported by GNAServicesInc
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Expired
Low
Unassigned

Bug Description

All of the folders on the desktop went away right after booting up,

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.2.1-2ubuntu11
ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
Uname: Linux 3.3.0-rc1-143+ x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Mon Jan 23 15:06:17 2012
ExecutablePath: /usr/bin/nautilus
ExecutableTimestamp: 1326901992
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111212)
ProcCmdline: nautilus -n
ProcCwd: /home/andy
Signal: 6
SourcePackage: nautilus
StacktraceTop:
 __libc_message (do_abort=2, fmt=0x7f52f0998728 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 malloc_printerr (action=3, str=0x7f52f0995859 "realloc(): invalid next size", ptr=<optimized out>) at malloc.c:6283
 _int_realloc (av=0x7f52f0bd41c0, oldp=0x29d20e0, oldsize=4944, nb=<optimized out>) at malloc.c:5238
 __GI___libc_realloc (oldmem=0x29d20f0, bytes=4928) at malloc.c:3821
 ft_mem_qrealloc () from /tmp/tmpESEFDj/usr/lib/x86_64-linux-gnu/libfreetype.so.6
Title: nautilus crashed with SIGABRT in __libc_message()
UpgradeStatus: Upgraded to precise on 2011-12-24 (30 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
GNAServicesInc (gnaservicesinc) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __libc_message (do_abort=2, fmt=0x7f52f0998728 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 malloc_printerr (action=3, str=0x7f52f0995859 "realloc(): invalid next size", ptr=<optimized out>) at malloc.c:6283
 _int_realloc (av=0x7f52f0bd41c0, oldp=0x29d20e0, oldsize=4944, nb=<optimized out>) at malloc.c:5238
 __GI___libc_realloc (oldmem=0x29d20f0, bytes=4928) at malloc.c:3821
 ft_mem_qrealloc (memory=<optimized out>, item_size=<optimized out>, cur_count=<optimized out>, new_count=<optimized out>, block=<optimized out>, p_error=<optimized out>) at /build/buildd/freetype-2.4.8/freetype-2.4.8/src/base/ftutil.c:154

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is that still an issue?
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

visibility: private → public
Changed in nautilus (Ubuntu):
importance: Medium → Low
status: New → Incomplete
Revision history for this message
GNAServicesInc (gnaservicesinc) wrote :

Sorry I just noticed your reply. I just clean installed the daily CD from 2/9/2012. I will report back if it happens again, so far no problems.

I am not sure what I could do to try to reproduce the bug other then rebooting a lot because it just sort of happened after booting. If you have any suggestion I am willing to spend some time trying to run it down, it's just that I really have no idea what to do.

If it dose not happen in the next couple of days I think we can assume it is no longer an issue.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]

Changed in nautilus (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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