** Description changed: Binary package hint: gdm Symptoms: 1. After running "sudo gdmsetup" any changed settings are instantly forgotten on gdmsetup exit. This is the same after restoring gdm.conf with factory-gdm.conf and rebooting. 2. When having added additional servers in gdm.conf-custom and rebooted, these are not listed when issuing: gdmflexiserver -c "GET_SERVER_LIST" + (With the extended issue of not being able to choose between custom servers when running gdmflexiserver) 3. Custom theme settings and settings like "Exclude=nobody,media" in gdm .conf-custom are not active not even after reboot. Btw, gdmsetup complains about the following when running and changing settings: [EMAIL PROTECTED]:~$ sudo gdmsetup gdmsetup[8672]: GLib-CRITICAL: g_key_file_set_string: assertion `key_file != NULL' failed gdmsetup[8672]: GLib-CRITICAL: g_key_file_to_data: assertion `key_file != NULL' failed gdmsetup[8672]: GLib-CRITICAL: g_file_set_contents: assertion `contents != NULL || length == 0' failed gdmsetup[8672]: GLib-CRITICAL: g_key_file_free: assertion `key_file != NULL' failed gdmsetup[8672]: GLib-CRITICAL: g_key_file_set_string: assertion `key_file != NULL' failed gdmsetup[8672]: GLib-CRITICAL: g_key_file_to_data: assertion `key_file != NULL' failed gdmsetup[8672]: GLib-CRITICAL: g_file_set_contents: assertion `contents != NULL || length == 0' failed gdmsetup[8672]: GLib-CRITICAL: g_key_file_free: assertion `key_file != NULL' failed gdmsetup[8672]: GLib-CRITICAL: g_key_file_set_string: assertion `key_file != NULL' failed gdmsetup[8672]: GLib-CRITICAL: g_key_file_to_data: assertion `key_file != NULL' failed gdmsetup[8672]: GLib-CRITICAL: g_file_set_contents: assertion `contents != NULL || length == 0' failed gdmsetup[8672]: GLib-CRITICAL: g_key_file_free: assertion `key_file != NULL' failed gdmsetup[8672]: GLib-CRITICAL: g_key_file_set_string: assertion `key_file != NULL' failed gdmsetup[8672]: GLib-CRITICAL: g_key_file_to_data: assertion `key_file != NULL' failed gdmsetup[8672]: GLib-CRITICAL: g_file_set_contents: assertion `contents != NULL || length == 0' failed gdmsetup[8672]: GLib-CRITICAL: g_key_file_free: assertion `key_file != NULL' failed gdmsetup[8672]: GLib-CRITICAL: g_key_file_set_string: assertion `key_file != NULL' failed gdmsetup[8672]: GLib-CRITICAL: g_key_file_to_data: assertion `key_file != NULL' failed gdmsetup[8672]: GLib-CRITICAL: g_file_set_contents: assertion `contents != NULL || length == 0' failed gdmsetup[8672]: GLib-CRITICAL: g_key_file_free: assertion `key_file != NULL' failed gdmsetup[8672]: GLib-CRITICAL: g_key_file_set_string: assertion `key_file != NULL' failed gdmsetup[8672]: GLib-CRITICAL: g_key_file_to_data: assertion `key_file != NULL' failed gdmsetup[8672]: GLib-CRITICAL: g_file_set_contents: assertion `contents != NULL || length == 0' failed gdmsetup[8672]: GLib-CRITICAL: g_key_file_free: assertion `key_file != NULL' failed I have two versions of glib installed: 1.2.10-17build1 and 2.14.1-1ubuntu1
-- [gutsy] gdm (including gdmsetup) ignores or cannot access gdm.conf-custom https://bugs.launchpad.net/bugs/195296 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
