slingshot-launcher crashed with SIGABRT in __libc_message()

Bug #1368309 reported by A.R.NARESH
356
This bug affects 82 people
Affects Status Importance Assigned to Milestone
Slingshot
Won't Fix
Undecided
Unassigned

Bug Description

the launcher crashed and the apport automatically collected info about it

ProblemType: Crash
DistroRelease: elementary OS 0.3
Package: slingshot-launcher 0.7.6.1+r452+pkg48~ubuntu0.3.1 [origin: LP-PPA-elementary-os-daily]
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CrashDB: slingshot_launcher
CurrentDesktop: Pantheon
Date: Thu Sep 11 21:16:30 2014
ExecutablePath: /usr/bin/slingshot-launcher
GsettingsChanges:
 b'org.pantheon.desktop.slingshot' b'screen-resolution' b"'1024x768'"
 b'org.pantheon.desktop.slingshot' b'columns' b'4'
InstallationDate: Installed on 2014-08-26 (16 days ago)
InstallationMedia: elementary OS 0.3 "Freya" - Daily amd64 (20140810)
ProcCmdline: slingshot-launcher --silent
Signal: 6
SourcePackage: slingshot-launcher
StacktraceTop:
 __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7f309bb4c668 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
 malloc_printerr (ptr=<optimized out>, str=0x7f309bb4c808 "free(): invalid next size (fast)", action=1) at malloc.c:4996
 _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at malloc.c:3840
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: slingshot-launcher crashed with SIGABRT in __libc_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
A.R.NARESH (naresh14334) wrote :
information type: Private → Public
Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote : Stacktrace.txt
Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote : ThreadStacktrace.txt
Changed in slingshot:
status: New → Invalid
Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote : Crash report cannot be processed
Download full text (4.0 KiB)

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

util-linux version 2.20.1-5.1ubuntu20.1 required, but 2.20.1-5.1ubuntu20.3 is available
no debug symbol package found for libpython3-stdlib
uuid-runtime version 2.20.1-5.1ubuntu20.1 required, but 2.20.1-5.1ubuntu20.3 is available
libsystemd-daemon0 version 204-5ubuntu20.6 required, but 204-5ubuntu20.8 is available
apport version 2.14.1-0ubuntu3.4 required, but 2.14.1-0ubuntu3.5 is available
libdbus-1-3 version 1.6.18-0ubuntu4.1 required, but 1.6.18-0ubuntu4.2 is available
libsystemd-login0 version 204-5ubuntu20.6 required, but 204-5ubuntu20.8 is available
no debug symbol package found for cpio
libgranite2 version 0.3.0~r782+pkg78~ubuntu0.3.1 required, but 0.3.0+r801+pkg78~ubuntu0.3.1 is available
libapt-inst1.5 version 1.0.1ubuntu2.2 required, but 1.0.1ubuntu2.6 is available
dbus version 1.6.18-0ubuntu4.1 required, but 1.6.18-0ubuntu4.2 is available
libssl1.0.0 version 1.0.1f-1ubuntu2.5 required, but 1.0.1f-1ubuntu2.7 is available
udev version 204-5ubuntu20.6 required, but 204-5ubuntu20.8 is available
no debug symbol package found for sed
libmagic1 version 1:5.14-2ubuntu3.1 required, but 1:5.14-2ubuntu3.2 is available
no debug symbol package found for libbz2-1.0
no debug symbol package found for python-minimal
libmount1 version 2.20.1-5.1ubuntu20.1 required, but 2.20.1-5.1ubuntu20.3 is available
no debug symbol package found for libv4l-0
libgee-0.8-2 version 0.14.0-1ubuntu1~14.04~valateam1 required, but 0.10.5-1ubuntu1 is available
libxml2 version 2.9.1+dfsg1-3ubuntu4.3 required, but 2.9.1+dfsg1-3ubuntu4.4 is available
libuuid1 version 2.20.1-5.1ubuntu20.1 required, but 2.20.1-5.1ubuntu20.3 is available
no debug symbol package found for libklibc
apt version 1.0.1ubuntu2.2 required, but 1.0.1ubuntu2.6 is available
no debug symbol package found for gir1.2-glib-2.0
tzdata version 2014e-0ubuntu0.14.04 required, but 2014i-0ubuntu0.14.04 is available
libpam-systemd version 204-5ubuntu20.6 required, but 204-5ubuntu20.8 is available
libgranite-common version 0.3.0~r782+pkg78~ubuntu0.3.1 required, but 0.3.0+r801+pkg78~ubuntu0.3.1 is available
no debug symbol package found for libv4lconvert0
python3-apport version 2.14.1-0ubuntu3.4 required, but 2.14.1-0ubuntu3.5 is available
no debug symbol package found for debianutils
libapt-pkg4.12 version 1.0.1ubuntu2.2 required, but 1.0.1ubuntu2.6 is available
mount version 2.20.1-5.1ubuntu20.1 required, but 2.20.1-5.1ubuntu20.3 is available
libudev1 version 204-5ubuntu20.6 required, but 204-5ubuntu20.8 is available
python3-problem-report version 2.14.1-0ubuntu3.4 required, but 2.14.1-0ubuntu3.5 is available
apt-utils version 1.0.1ubuntu2.2 required, but 1.0.1ubuntu2.6 is available
file version 1:5.14-2ubuntu3.1 required, but 1:5.14-2ubuntu3.2 is available
libgudev-1.0-0 version 1:204-5ubuntu20.6 required, but 1:204-5ubuntu20.8 is available
outdated debug symbol package for libgudev-1.0-0: package version 1:204-5ubuntu20.8 dbgsym version...

Read more...

tags: removed: need-amd64-retrace
Revision history for this message
Thomas Citharel (tcit) wrote :

I'm using up to date packages and it occurs to me as well.

Changed in slingshot:
status: Invalid → New
Revision history for this message
Israel (isra1998isra) wrote :

Same here

Revision history for this message
Tom von Schwerdtner (tvon) wrote :

FWIW: After package update a few minutes ago and a reboot, launched Terminal and (while I didn't notice the crash) the bug reporter popped up after Terminal launched.

Revision history for this message
Murat Ursavas (murat-ursavas) wrote :

Happened here on my up to date Freya Beta 2.

Revision history for this message
Dorzhi T (dorzhi-deactivatedaccount-deactivatedaccount) wrote :

Crashed for like no reason. Chromium and Zim desktop Wiki were active only. System is up-to-date.

Revision history for this message
kerosin (kerosin-osm) wrote :

same here

Revision history for this message
Danielle Foré (danrabbit) wrote :

Clearing out old crashes

Changed in slingshot:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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