[05:08] <mem11> darkxst, I've verified the AutoLogin issue from yesterday. Your comments about custom.conf being commented out by default is valid, sometimes. When user chooses "Login automatically" on install, those comments are removed, thus enabling AutoLogin and TimedLogin. And when you turn off the auto login, TimedLogin stays on...
[06:41] <darkxst> mem11, file a bug
[06:48] <mem11> darkxst, where?
[06:53] <mem11> https://launchpad.net/ubuntu-gnome This address is nowhere to be found on the webpage and wiki
[06:58] <darkxst> mem11, use ubuntu-bug command
[06:59] <darkxst> probably those settings are handled by gnome-settings-daemon
[06:59] <mgedmin> not gdm?
[07:00] <darkxst> mgedmin, I think he is talking about changes that are occuring via g-c-c?
[07:00] <mgedmin> oh right, gdm reads these; something else writes them
[07:00] <mgedmin> not gnome-control-center itself?
[07:01] <mem11> darkxst, ubuntu-bug <package-name> : what should I file against?
[07:01] <darkxst> mgedmin, could be either really, didnt actually check
[07:02] <darkxst> mem11, I just told you!
[07:03] <mem11> all right. i'll do it later, as i'm on a different machine
[07:04] <mem11> isn't there a web-based tracker somewhere?
[07:05] <mgedmin> https://bugs.launchpad.net/ubuntu-gnome, but ubuntu-bug attaches various bits of relevant system information such as package versions and config settings
[07:05] <mgedmin> so it's better to use the tool
[07:06] <mgedmin> (in theory you can file a bug now and then use apport-collect to collect and upload the extra info later)
[07:06] <darkxst> accountsservices edits the config file
[07:07] <darkxst> however I can't find any code that would enable TimedLogin
[07:08] <darkxst> unless its a regex in ubiquity
[07:10] <mem11> I think it's only during installation. When you don't select "Login Auto..." during install and then modify AutoLogin=False, the commented sections are all there and my change is appended in the file. Hope I'm being clear.
[07:11] <mem11> Nevermind, I'll make a proper bug report later on. Thanks people.
[07:13] <darkxst> yes its ubiquity
[07:13] <darkxst> AutologinParameters="AutomaticLoginEnable=true\n\
[07:13] <darkxst> AutomaticLogin=$USER\n\
[07:13] <darkxst> TimedLoginEnable=true\n\
[07:13] <darkxst> TimedLogin=$USER\n\
[07:13] <darkxst> TimedLoginDelay=10"
[07:14] <darkxst> mem11, if you disable autologin in gnome-control-center is it still broken?
[07:15] <darkxst> my guess is that wont touch the "TimedLogin" keys either though
[07:15] <mem11> Yes, that's it.
[07:16] <mem11> TimedLogin isn't changed back.
[07:16] <darkxst> mem11, ok, file bug against ubiquity, TimedLogin probably doesnt need to be ever set
[07:17] <darkxst> its probably old code from GNOME2 days
[07:17] <mem11> Ok, ubiquity. Thanks.
[07:20] <mem11> Looks like it's been reported couple of months ago actually: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1412791
[07:22] <mem11> Someone responded that "it's not a security bug" :-/ He probably knows better huh?
[07:24] <darkxst> mem11, physical access to a machine does not count as a security bug
[07:24] <darkxst> (its ridiculously easy to get root access on any linux machine)
[07:25] <darkxst> unless its an encrypted system
[07:25] <mem11> When /home is encrypted, you need password anyway...
[07:26] <darkxst> you can still get at the root filesystem then
[07:30] <darkxst> hmm I don't know where that code comes from, seems to be imported into ubiquity at build time
[07:37] <darkxst> seens to be user-setup
[07:40] <darkxst> this is crap, ubuntu patch the upstream code directly in that package
[07:40] <darkxst> it has completely diverged from the debian source
[07:45] <mem11> how do you track all those sources?
[07:59] <darkxst> mem11, track what? codesearch.debian.org is useful
[07:59] <darkxst> normally ubuntu patches are applied over debian code with quilt