For systems where the bug was not present (if I understood your question correctly), that means where the gconf key was already present, the output is "true".
On affected systems, where a gconf key does not exist (that is valid for any case, not just sudo-mode), gconftool-2 will warn you that there is no defined value for that key. -- Edgy uses gksu instead of gksudo (gconf problem?) https://launchpad.net/bugs/59079 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
