colord-sane crashed with SIGSEGV in libusb_get_device_list() during quantal to raring upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
colord (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
This crash occurred during quantal to raring desktop auto-upgrades amd64. The crash occurred only once and the consecutive run has passed. A manual upgrade of an updated quantal desktop installation to raring did not produce this crash either.
The testing was done in an automated way and here are the major steps involved.
1. Create a quantal base image using ubuntu-vm-builder and bootstrap it to get the ubuntu standard desktop packages
2. Use do-release-upgrade to perform the upgrade.
The impacted job is,
https:/
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: colord 0.1.23-0ubuntu3
ProcVersionSign
Uname: Linux 3.8.0-7-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Tue Feb 26 00:22:39 2013
ExecutablePath: /usr/lib/
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcEnviron:
SegvAnalysis:
Segfault happened at: 0x7f55512c0d60: cmpb $0x0,(%rsi)
PC (0x7f55512c0d60) ok
source "$0x0" ok
destination "(%rsi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: colord
StacktraceTop:
?? () from /lib/x86_
?? () from /lib/x86_
libusb_
?? () from /usr/lib/
hpmud_
Title: colord-sane crashed with SIGSEGV in libusb_
UpgradeStatus: Upgraded to raring on 2013-02-25 (0 days ago)
UserGroups:
tags: | removed: need-amd64-retrace |
Status changed to 'Confirmed' because the bug affects multiple users.