Ok, thank you very much (sorry for my impatience in the hastily written messages above while I was logging in to vpn).
If I create an empty .d directory, and run "dconf update" it creates 61-byte database files and all is ok. So this bug is similar to the other one mentioned, in that it is a real bug (there should be an error message and not SIGSEGV for an improper database file), but it is not urgent and can wait just like the other for release. I notice that if the file is corrupted, there is all kinds of logic to detect this, and I'd suggest something similar to detect databases in which the initial header information can't be read should produce a warning of some kind and not a crash--much confusion would have been eliminated with that. I'd also strongly urge either writing a manpage for the "dconf" tool, or else some real in-tool documentation via the "help" command. "dconf help update" says only "update the system dconf databases", but if you don't already know what it does, this doesn't explain it. Perhaps "update system database files from information in key file (.d) directories" or something like that at least. -- 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 Unity greeter 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
