[04:08] <R13ose> Hi
[06:39] <lotuspsychje> good morning to all
[06:39] <lotuspsychje> !dirtycow
[07:23] <ducasse> hi all
[07:48] <Bashing-om> Outta here , G nite
[12:13] <pauljw> Hi everyone
[13:05] <BluesKaj> Hiyas all
[13:07] <R13ose> Hi
[13:17] <pauljw> hey BluesKaj
[13:18] <BluesKaj> 'Morning pauljw
[16:16] <Bashing-om> Good morning - 'buntu'n we will go .
[16:25] <daftykins> wb!
[16:26] <Bashing-om> Good to be here . thanks daftykins :)
[23:07] <Bashing-om> R13ose: I had meant to ask earlier .. what is your driver disposition presently ?
[23:07] <R13ose> how do I find out?
[23:08] <daftykins> well you don't need anything besides the kernel for intel
[23:08] <daftykins> though i wasn't 100% convinced on the graphics situation, so wouldn't mind seeing an "lspci | nc termbin.com 9999" :)
[23:09] <Bashing-om> R13ose: Like I mean now functional ? As I recall we could not determine what was not going on .
[23:09] <daftykins> oh my mistake
[23:10] <Bashing-om> daftykins: Naw, ya got it right .
[23:10] <R13ose> I haven't had any problems since I last talked to both of you. I am using Firefox instead of Chrome and haven't had a problem.
[23:10] <R13ose> daftykins: lspci | nc termbin.com 9999
[23:10] <R13ose> oops
[23:10] <R13ose> http://termbin.com/i8tk
[23:11] <daftykins> wow you don't even type it out?
[23:11] <daftykins> yep, barring any physical switches or BIOS options there doesn't seem to be any sign of nvidia in that one
[23:11] <Bashing-om> R13ose: chrome .. who wudda thunk it !
[23:12] <R13ose> I thought I was using AMD
[23:12] <daftykins> i'd be willing to bet the quirks are hardware acceleration related o0
[23:12] <R13ose> graphics most likely
[23:12] <daftykins> AMD? you own an intel system with on-CPU die graphics
[23:13] <daftykins> specifically, a third generation intel Core CPU - aka ivybridge
[23:13] <R13ose> oops right sorry :P
[23:16] <R13ose> anything I need to do?
[23:17] <daftykins> didn't realise the issue was with chrome to begin with, don't really see the need to pursue this any further
[23:19] <R13ose> This might not be chrome alone as firefox has had problems in the past too and the dock application I use too
[23:20] <daftykins> well until you provide such evidence all i can do is repeat my warning against using 16.10
[23:22] <R13ose> it wasn't only 16.10
[23:23] <daftykins> yes, but we haven't had the opportunity to work with that one, plus LTS is always best
[23:25] <R13ose> true
[23:27] <daftykins> from what i remember you said you use this thing at work, so i suppose we'll reconvene in July 2017 when it's upgrade time due to 16.10 going EOL - and it dying :>
[23:28] <R13ose> at work?
[23:29] <daftykins> that's what i remembered being said
[23:30] <daftykins> not directly perhaps
[23:30] <R13ose> I work from my home
[23:34] <daftykins> ok, but using a non-LTS release for work is way up on the inadvisable list
[23:34] <daftykins> gotta go now, laters
[23:34] <R13ose> thanks