Comment 25 for bug 1026520

Revision history for this message
DimeDroll (dimdroll) wrote :

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Thu Jan 24 12:47:09 2013
DistroRelease: Ubuntu 12.10
ExecutablePath: /usr/lib/i386-linux-gnu/colord/colord-sane
ExecutableTimestamp: 1349865025
ProcCmdline: /usr/lib/i386-linux-gnu/colord/colord-sane
ProcCwd: /
ProcStatus:
 Name: colord-sane
 State: S (sleeping)
 Tgid: 2033
 Pid: 2033
 PPid: 2030
 TracerPid: 0
 Uid: 114 114 114 114
 Gid: 124 124 124 124
 FDSize: 32
 Groups: 124 125
 VmPeak: 53564 kB
 VmSize: 53460 kB
 VmLck: 0 kB
 VmPin: 0 kB
 VmHWM: 8456 kB
 VmRSS: 8456 kB
 VmData: 32120 kB
 VmStk: 136 kB
 VmExe: 8 kB
 VmLib: 19968 kB
 VmPTE: 84 kB
 VmSwap: 0 kB
 Threads: 3
 SigQ: 0/31104
SegvAnalysis:
 Segfault happened at: 0xb740b3bf: cmpb $0x0,(%edx)
 PC (0xb740b3bf) ok
 source "$0x0" ok
 destination "(%edx)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
SourcePackage: colord
Title: colord-sane crashed with SIGSEGV in opendir()
UpgradeStatus: Upgraded to quantal on 2013-01-17 (6 days ago)

Installed version of colord:
Version: 0.1.21-1ubuntu2
This bug still afects me, should I provide any other information or create new bug as this one is being marked as fixed?