When we crash, table->data is in fact null. I presume this is the expected behavior of g_mapped_file_get_contents for an empty file.
Fixing the erroneous extra * will turn this into a check whether table->data is null. But that's still going to have a bug. If it returns zero, then dconf_engine_refresh_system will deconfigure that table, and that's wrong, because we want to use the .d directory for a textual definition. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/981053 Title: Creating system dconf configuration crashes lightdm To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/981053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
