Ubuntu
indicator-sound package

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

Bug #641362 reported by Ralf Hildebrandt on 2010-09-17

This bug report is a duplicate of: Bug #640127: indicator-sound-service crashed with SIGSEGV in xcb_setup_vendor_end(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	indicator-sound (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: indicator-sound

The indicator crashed immediately after logging in.

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 x86_64
Architecture: amd64
Date: Fri Sep 17 07:37:03 2010
ExecutablePath: /usr/lib/indicator-sound/indicator-sound-service
ProcCmdline: /usr/lib/indicator-sound/indicator-sound-service
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.utf8
SegvAnalysis:
Segfault happened at: 0x7f39489563c0 <xcb_setup_vendor_end>: movzwl 0x18(%rdi),%eax
PC (0x7f39489563c0) ok
source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
destination "%eax" 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

Tags:

Revision history for this message

Ralf Hildebrandt (ralf-hildebrandt) wrote on 2010-09-17:

XsessionErrors.txt Edit (13.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2010-09-17: 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.