Oh, would you look at that!
This is a combination of colord being insufficiently paranoid - it
assumes that if g_dbus_connection_register_object returns 0 then it has
set error, which is not true; there are a variety of ways that
g_dbus_connection_register_object can return 0 without setting error
(this is arguably a GDBus bug).
The particular way that's easy to hit is if you use a guest session;
colord appends the user's name on to the object path of the xrandr
device it tries to register. For most cases this is fine, but there are
plenty of usernames that aren't valid in a DBus object path - our
“guest-$RANDOM_CHARACERS” is one, as ‘-’ is not valid in an object path.
** Changed in: colord (Ubuntu Quantal)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021374
Title:
colord crashed with SIGSEGV in cd_device_register_object()
To manage notifications about this bug go to:
https://bugs.launchpad.net/colord/+bug/1021374/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
