** Description changed: + [Impact] + This causes frequent crashes of the colord daemon for some users. For most users, the visible result of this will be an apport popup. For users who have calibrated their monitors, this will unset the calibration, causing the screen colours to change. + + [Test Case] + I'm not able to reproduce this myself. However, this crash (and crashes like it) are pretty much *all* of the colord crash reports for 0.1.16-2 on errors.ubuntu.com. + + This should cook in -proposed until we're reasonably certain that these + crashes no longer show up there. + + [Regression Potential] + Low. The upload adds a single call to dbus_threads_init_default() at the start of main. Given that colord is currently using libdbus without threadsafe support, enabling threadsafe support is unlikely to break anything. + + There is no explicit synchronisation between the dbus-using threads, so + deadlocks are unlikely. + + The colord daemon is run as an unprivileged user, so even in the + incredibly unlikely event that this opens a security hole it's a limited + threat. + + [Development release] + This code is split out of the colord daemon in the development release; the same fix applies to colord-sane, however, and will be uploaded shortly. + + [Original report] crashes at startup ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: colord 0.1.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Sep 7 14:06:00 2011 ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110829.2) ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord ProcEnviron: - + SegvAnalysis: - Segfault happened at: 0x7f15e33888a5: mov (%r12,%rdx,1),%edx - PC (0x7f15e33888a5) ok - source "(%r12,%rdx,1)" (0x0000017a) not located in a known VMA region (needed readable region)! - destination "%edx" ok - Stack memory exhausted (SP below stack segment) + Segfault happened at: 0x7f15e33888a5: mov (%r12,%rdx,1),%edx + PC (0x7f15e33888a5) ok + source "(%r12,%rdx,1)" (0x0000017a) not located in a known VMA region (needed readable region)! + destination "%edx" ok + Stack memory exhausted (SP below stack segment) SegvReason: reading 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 - dbus_message_get_reply_serial () 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 + dbus_message_get_reply_serial () 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 in dbus_message_get_reply_serial() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: scanner
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/844286 Title: colord crashed with SIGSEGV in dbus_message_get_reply_serial() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/844286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
