indicator-sound-service crashed with SIGABRT in raise()

[Mike Leitner]

I don't have more. I started banshee and it appeard.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-sound 0.8.4.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-19.31-generic-pae 3.2.12
Uname: Linux 3.2.0-19-generic-pae i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Wed Mar 21 22:14:44 2012
ExecutablePath: /usr/lib/indicator-sound/indicator-sound-service
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
ProcCmdline: /usr/lib/indicator-sound/indicator-sound-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.UTF-8
Signal: 6
SourcePackage: indicator-sound
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so
Title: indicator-sound-service crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-03-21 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 g_assertion_message (domain=0xafade42d <Address 0xafade42d out of bounds>, file=0xafadf36f <Address 0xafadf36f out of bounds>, line=328, func=0xafadf4a0 <Address 0xafadf4a0 out of bounds>, message=<optimized out>) at /build/buildd/glib2.0-2.31.22/./glib/gtestutils.c:1860
 g_assertion_message_expr (domain=0xafade42d <Address 0xafade42d out of bounds>, file=0xafadf36f <Address 0xafadf36f out of bounds>, line=328, func=0xafadf4a0 <Address 0xafadf4a0 out of bounds>, expr=0xafadf380 <Address 0xafadf380 out of bounds>) at /build/buildd/glib2.0-2.31.22/./glib/gtestutils.c:1871
 ?? ()
 ?? ()
 ?? ()

[Apport retracing service (apport)]

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:

libpng12-0 version 1.2.46-3ubuntu2 required, but 1.2.46-3ubuntu3 is available
libdbusmenu-glib4 version 0.5.94-0ubuntu1 required, but 0.5.94-0ubuntu2 is available
libdbusmenu-gtk3-4 version 0.5.94-0ubuntu1 required, but 0.5.94-0ubuntu2 is available
indicator-sound version 0.8.4.1-0ubuntu2 required, but 0.8.4.1-0ubuntu3 is available
libido3-0.1-0 version 0.3.3-0ubuntu2 required, but 0.3.4-0ubuntu1 is available
outdated debug symbol package for libido3-0.1-0: package version 0.3.4-0ubuntu1 dbgsym version 0.3.3-0ubuntu2

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

[Mike Leitner (tecardo)]

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

I have the newest packages.

[Conor Curran (cjcurran)]

Indeed you do Mike, this is a Glib DBus bug which I have seen before.

[Mike Leitner (tecardo)]

Sorry, what do you mean?
Thanks for the reply

[Olli Ries (ories)]

Conor, if valid, then please look into it, if invalid then please close accordingly. Comments 6-8 don't are confusing

[Charles Kerr (charlesk)]

Olli, what's happening is the ticket appears to be valid but doesn't have enough information yet to act on.

The telltale sign in the ThreadStacktrace is the assertion error "assertion failed: (fd_id == data->extra_fd_countx" which has shown up in many other non-isound crashes too <https://www.google.com/search?q=fd_id+site%3Alaunchpad.net>

[Conor Curran (cjcurran)]

Marking incomplete for now because this really needs more information.

[Mike Leitner (tecardo)]

so, what do i need to do? i can install or do any log for you, if it helps you.
PS: it appears on starting an musicplayer, which uses the sound indicator.
novula, banshee, rhytmbox etc.

[Conor Curran (cjcurran)]

Hi Mike,

Any chance you could do this from terminal.

Make sure gdb is installed. (sudo apt-get install gdb)

then run:
sudo ps ax | grep indicator-sound-service

this will find the process for the indicator, you will see something like
 2251 ? Sl 0:00 /usr/lib/indicator-sound/indicator-sound-service
 7911 pts/12 S+ 0:00 grep --color=auto indicator-sound-service

then we want to attach to the sound-service
in this case i would run
sudo gdb -p 2251

Please replace the process number with the one from your machine

once gdb attaches, type 'continue' and hit return
then reproduce the crash which gdb will 'catch'.
type 'bt full'

And attach the full backtrace to this bug report (remember the backtrace will more than likely come in two parts, you will need to hit return to see the second half of it)

Thanks !

[Mike Leitner (tecardo)]

At the moment, the bug isn't appearing anymore.
I think it was Spotify, because it was the only applikation, which was updated by me.
I Update the system in waves, this should reduce system brackage. I update it every 2 Weeks.

I will uplaod the results later, i think tomorow.

[Launchpad Janitor (janitor)]

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