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

Bug #642400 reported by SilverBlade
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-sound (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: indicator-sound

10.10 Ubuntu 10.10
                - the Maverick Meerkat
at start up i have the crash and the sound was disable

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: indicator-sound 0.4.7-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.32-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Sun Sep 19 00:07:03 2010
ExecutablePath: /usr/lib/indicator-sound/indicator-sound-service
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100322)
ProcCmdline: /usr/lib/indicator-sound/indicator-sound-service
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=it_IT.utf8
SegvAnalysis:
 Segfault happened at: 0x1ab8fa <xcb_setup_vendor_end+10>: movzwl 0x18(%edx),%ecx
 PC (0x001ab8fa) 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

Revision history for this message
SilverBlade (lucagallu) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #640127, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-retrace
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.