[13:53] <akira_> Hello. I am running artificial intelligence heuristic tests at the kernel level on a virtual machine and I was wondering if there was a way to make it so that my user's account doesn't require me entering the sudo password all the time. Is this possible in any way?
[13:54] <jtaylor> akira_: man sudoers, support is in #ubuntu
[13:55] <akira_> jtaylor, in #ubuntu I was discouraged from doing this...
[13:55] <akira_> Also I have added the line "myuser ALL=(ALL:ALL) NOPASSWD:ALL" to /etc/sudoers, but to no avail.
[13:56] <_heimdall> " _heimdall: possible, not recommended."
[14:04] <teward> _heimdall: you were discouraged from editing if you don't know what you're doing
[14:05] <_heimdall> teward, that's so derogatory...
[14:05] <_heimdall> Of them I mean.
[14:06] <teward> _heimdall: some of those people are also here mind you
[14:06] <teward> _heimdall: on the Security / Sysadmin side, I agree with them - people who don't know how to edit sudoers by reading manpages shouldn't be editing things.  However, I also understand the other side why you would want this
[14:07] <teward> _heimdall: support is still in #ubuntu though
[14:07] <teward> sorry
[14:08] <_heimdall> Hurg.
[14:18] <siretart> _heimdall: you should try to find out why they discourage you from doing that. by then, you'll have found out how to achieve exactly what you want.
[14:18] <_heimdall> Thank you, old wizard :|
[14:19] <_heimdall> I mean I did that already, found out that root was locked, I unlocked root, didn't work.
[14:19] <_heimdall> work/do what I wanted to achieve
[14:39] <TJ-> I've just noticed that after adding a keyring in /etc/apt/trusted.gpg.d/ and confirming the keys contained are reported by "apt-key list", that "apt{,-get}" report 'public key not available' for those keys. What am I missing?
[16:03] <maxb> I'm experiencing a bluetooth regression in xenial, can someone suggest where I can go for some assistance in refining a useful bug report?
[16:05] <TJ-> maxb: support is generally in #ubuntu
[16:10] <maxb> I feel I'm more looking for assistance helping combat a regression rather than user support, but I can see how that could be a matter of opinion
[16:10] <TJ-> that's what we do in #ubuntu too
[16:12] <TJ-> re: the apt 'public key not available' issue - just found out that the processes must be running as a user other than UID 0 when checking, because "chmod -R o+r /etc/apt/trusted.gpg.d/" solved it
[16:30] <infinity> maxb: Just file a bug ('ubuntu-bug linux'), provide as much descrition of the problem as you can, and iterate there.
[16:31] <infinity> maxb: If it feels like it'd be a pretty widespread issue, perhaps ping jsalisbury to help you triage it.
[16:31] <TJ-> I'm done some in-depth BT debugging and fixing but I keep the triage process in #ubuntu
[16:31] <infinity> TJ-: It likely is running as the _apt user at that point.
[16:32] <maxb> Interesting, I would not have thought to report it against the kernel package
[16:33] <infinity> maxb: Well, depends on if it's a driver issue or userspace tools.  Report the bug where it seems most plausible?
[16:33] <TJ-> infinity: ahhh... that makes sense. I've got a system set up so I have a portable /usr/local/... for multiple machines that then gets various content either symlinked or bind-mounted into the regular package file-system, and I'd got /usr/local/etc/apt/trusted.gpg.d bind mounted to /etc/apt/trusted.gpg.d and thought it was something to do with that!
[16:34] <infinity> TJ-: Yeah, I believe trusted.gpg switched from 600 to 644 when apt moved to dropping privs in most of its subprocesses.  To be fair, 600 was always silly anyway, since they're public keys. :P
[16:36] <infinity> Oh, actually, trusted.gpg was always (correctly) 644, it's trustdb.gpg that used to be 600, and is now just gone.
[16:36] <infinity> Good riddance, silly trustdb.
[16:38] <TJ-> yeah, I vaguely remembered that and was wondering if I'd accidentally deleted it :D
[16:41] <TJ-> anyone know where I should be focusing my attention to figure out how to get touchscreen gesture support working? aside from the xserver mtrack driver I've not been able to find any clear indication of where the action is. All the ubuntu-touch related packages in the archive confused the issue too
[22:44] <lfaraone> xnox: I see you grabbed LP #1387908 -- are you actively working on it, or would a patch to import the ``70-u2f.rules`` from Yubico's libu2f-host be useful?