indicator-sound-service crashed with SIGSEGV in xcb_setup_vendor_end()

Bug #640127 reported by Dan Scott
510
This bug affects 96 people
Affects Status Importance Assigned to Milestone
pulseaudio (Ubuntu)
Fix Released
High
Luke Yelavich

Bug Description

Binary package hint: indicator-sound

Booted into desktop edition

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: indicator-sound 0.4.6-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-21.31-generic 2.6.35.4
Uname: Linux 2.6.35-21-generic i686
Architecture: i386
Date: Wed Sep 15 17:26:37 2010
ExecutablePath: /usr/lib/indicator-sound/indicator-sound-service
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Beta i386 (20100318)
ProcCmdline: /usr/lib/indicator-sound/indicator-sound-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x3f28fa <xcb_setup_vendor_end+10>: movzwl 0x18(%edx),%ecx
 PC (0x003f28fa) ok
 source "0x18(%edx)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-sound
StacktraceTop:
 xcb_setup_vendor_end () from /usr/lib/libxcb.so.1
 xcb_setup_pixmap_formats_iterator () from /usr/lib/libxcb.so.1
 xcb_setup_roots_iterator () from /usr/lib/libxcb.so.1
 pa_x11_get_prop () from /usr/lib/libpulsecommon-0.9.21.so
 ?? () from /usr/lib/libpulse.so.0
Title: indicator-sound-service crashed with SIGSEGV in xcb_setup_vendor_end()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1337): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:1335): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

Revision history for this message
Dan Scott (danieljamesscott) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 xcb_setup_vendor_end () from /usr/lib/libxcb.so.1
 xcb_setup_pixmap_formats_iterator ()
 xcb_setup_roots_iterator () from /usr/lib/libxcb.so.1
 pa_x11_get_prop (xcb=0x3fc700,
 pa_client_conf_from_x11 (c=0x8842dd8, dname=0x0)

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 indicator-sound (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Neil J. Patel (njpatel)
visibility: private → public
Revision history for this message
Conor Curran (cjcurran) wrote :

this looks like a pulse problem no ?

affects: indicator-sound (Ubuntu) → pulseaudio (Ubuntu)
Omer Akram (om26er)
Changed in pulseaudio (Ubuntu):
status: New → Confirmed
Revision history for this message
Luke Yelavich (themuso) wrote :

A simple work-around is to back out a recent change in pulseaudio stable queue to start using xcb, however that was put in to fix stability with other software. A better fix is to fix the segfault of course.

I'll look at this myself, but have also contacted upstrea to get further assistance with this one, and hope to have a patch ASAP.

Changed in pulseaudio (Ubuntu):
assignee: nobody → Luke Yelavich (themuso)
Daniel T Chen (crimsun)
Changed in pulseaudio (Ubuntu):
importance: Medium → High
status: Confirmed → In Progress
Revision history for this message
Daniel T Chen (crimsun) wrote :

A proposed fix for this bug is building in ppa:crimsun/pulseaudio; please confirm whether it resolves this symptom.

Revision history for this message
MaxNegro (maxnegro) wrote :

ppa:crimsun/pulseaudio appears empty, while ppa:crimsun/ppa seems to contain an update package. Daniel, can you please confirm which repo/packet/version is supposed to fix the problem?

Revision history for this message
Daniel T Chen (crimsun) wrote : Re: [Bug 640127] Re: indicator-sound-service crashed with SIGSEGV in xcb_setup_vendor_end()

On Sat, Sep 18, 2010 at 10:24 AM, MaxNegro <email address hidden> wrote:
> ppa:crimsun/pulseaudio appears empty, while ppa:crimsun/ppa seems to
> contain an update package. Daniel, can you please confirm which
> repo/packet/version is supposed to fix the problem?

Sigh, it looks like my ~/.dput.cf is borked. Anyhoo, it does appear
to be ppa:crimsun/ppa. Sorry for the confusion!

tags: added: bugpattern-needed
Revision history for this message
Daniel T Chen (crimsun) wrote :

For everyone being added to this bug report via duplicates, please see comment #9 for a test package.

Revision history for this message
MaxNegro (maxnegro) wrote :

I've installed the test package, and so far I've seen no more crashes. Sadly, I've not been able to reproduce reliably even before installing the test package, so I'm not sure how much this report is meaningful. :)

Revision history for this message
Luke Yelavich (themuso) wrote :

Given we are out of time, I am going to upload these changes to ubuntu proper, based on the last comment in this bug.

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

This bug was fixed in the package pulseaudio - 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu20

---------------
pulseaudio (1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu20) maverick; urgency=low

  * 0093-backport-fixes-stable-queue-head.patch: Backport the following
    changesets from the stable-queue branch:
    + 2c564f2 (xcb: Ensure the XCB connection is valid before using it.)
    + 5c0bc09 (xcb: xcb_get_setup() can return 0, so make sure we check it before using)
    + 165cb87 (x11: Use the default screen for X11 properties.)
    (LP: #640127)
 -- Daniel T Chen <email address hidden> Sat, 18 Sep 2010 08:46:31 -0400

Changed in pulseaudio (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Nick Flyer (nickflyerspam) wrote :

it happened again.... after i installed the update

Revision history for this message
Luke Yelavich (themuso) wrote :

Was your machine restrated between installing the update and getting the crash?

Revision history for this message
Carlos Alexandro Becker (caarlos0) wrote :

here, sometimes, the sound become to a noise..

Revision history for this message
Nick Flyer (nickflyerspam) wrote :

I'm pretty sure it was. I will let you know if it logs out again....

Revision history for this message
Nick Flyer (nickflyerspam) wrote :

It did it again... this is SOOOO annoying.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Please attach a backtrace.

Revision history for this message
Nick Flyer (nickflyerspam) wrote :

I starting using Ubuntu a week ago.... from years of windows. Backtrace? https://wiki.ubuntu.com/Backtrace
*confusion*

Revision history for this message
Kitemare (max-haggaard) wrote :

To be honest I cant really remember. But it is quite unlikely that I
haven’t restarted since you normally are prompted to do so if needed.

On Wed, 2010-09-29 at 00:05 +0000, Luke Yelavich wrote:
> Was your machine restrated between installing the update and getting the
> crash?
>

Revision history for this message
Nick Flyer (nickflyerspam) wrote :

I tried to collect a stacktrace. I hope this is what you are looking for...

Revision history for this message
Sven Mueller (smu-u) wrote :

According to #13, this was fixed in September 2010, but the fixed package version (1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu20) is still not available in Lucid (only somewhere in lucid-proposed). Any chance to get the fix into lucid?

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

@Sven Mueller (smu-u)
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, this bug is closed because it was fixed in the development release at the time.

This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

For you information:
pulseaudio in lucid-release is:1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14

in lucid-proposed there is: 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14.1 which is still pending verification, see bug 445849 and please help to verify that one. As that SRU should be completed before starting a new one for lucid.

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.