Affects (at least) 71 people and masses of bug reports which duplicate this. Nothing changed since June 2012.
I am getting a little tired of this error myself, any danger of a fix in the next decade? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/840123 Title: colord crashed with SIGSEGV Status in “colord” package in Ubuntu: Confirmed Bug description: it showed that it crashed ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: colord 0.1.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 Date: Sat Sep 3 08:23:57 2011 ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord ProcEnviron: SegvAnalysis: Segfault happened at: 0x7fdd47d7757e: cmpq $0x0,0x70(%rdi) PC (0x7fdd47d7757e) ok source "$0x0" ok destination "0x70(%rdi)" (0x00000071) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: colord StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 Title: colord crashed with SIGSEGV UpgradeStatus: Upgraded to oneiric on 2011-09-02 (0 days ago) UserGroups: scanner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/840123/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
