I encountered this same problem. Changing ownership of .config/autostart did fix the problem, but it seems to me that what needs to happen is that gnome-sessions needs to display an error if it is unable to write the updated startup configuration, rather than close as though nothing is wrong. I suggest that we change this to be a bug with gnome-session that it doesn't have any error notification for this problem. What app might be changing the permissions of .config/autostart would then be a separate issue.
-- No programs can be added in the startup list. https://bugs.launchpad.net/bugs/71200 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
