[04:09] <guiverc> i just tried a qa-test (live) on an dell inspiron 6400 (c2d-t2450) expecting it to run, it reported x86_64 is required - a look at https://ark.intel.com/content/www/us/en/ark/products/42841/intel-core-2-duo-processor-t6570-2m-cache-2-10-ghz-800-mhz-fsb.html i read as saying it should run (Instruction Set: 64-bit) - any suggestions?
[04:10] <guiverc> (if required, using lubuntu 19.04 x86_64 daily)
[04:14] <guiverc> ignore my last; tried two other random usb's (older ubuntu & a opensuse), both reported x86 need 64bit
[04:49] <OerHeks> yes, how odd .. it should run fine, even vt-x available
[05:18] <tomreyn> no SSE 4.2, VT yes, but not VT-d, no AES-NI, no AVX
[05:19] <tomreyn> but i'd also expect it to work with amd64 / x86_64
[06:17] <guiverc> tomreyn & OerHeks or anyone, i've ignored it - should I go & look again, raise lp.bug report  -- c2d-t2450 fails x86_64 test though intel's site^ says 64bit?
[06:18] <guiverc> sorry, it was supposed to be Thanks tomreyn & OerHeks 
[06:20] <guiverc> however one of my random thumb-drives was opensuse; so it's kernel rejection & likely a valid answer (bios 32bit hurdle maybe?)
[06:23] <tomreyn> this thning is from 2006. i guess if you need it working, report a bug. otherwise, i guess i'd just accept it, assuming the bar for what is still considered x86_64 was slightly raised during the past 13 years, causing this.
[06:27] <guiverc> not having it useful for x86_64 testing means I can ditch [recycle] it :)   (I think it got drawn back from that pile only because of recent 16.04.6 x86 testing..)
[06:35] <tomreyn> i guess it is bad if it's an undocumented change in policies ("what is supported?"), but so far i don't know whether that's actually a change which happened, or whether it's undocumented. so... ymmv
[06:41] <guiverc> it very well may have been documented and I just forgot (was awhile ago I suspect).  i was last using it for testing xubuntu & lubuntu 19.04 (x86) but got piled for recycle last december when they dropped x86..  as it was dual-core unlike others in the pile, I assumed it was in the pile in error (obviously not)
[06:41] <guiverc> (assumed in pile in error, when dragged some out for x86 16.04.6 qa-testing)
[06:43] <lotuspsychje> also not sure core2duo are safe anymore for meltdown
[06:45] <guiverc> don't say that lotuspsychje - `lscpu` gives my current box as "Intel(R) Core(TM)2 Duo CPU     E8300  @ 2.83GHz"
[06:46] <guiverc> (it was a crappy centrino laptop that reported itself as c2d, which I think was it's problem)
[06:46] <lotuspsychje> aha
[06:51] <guiverc> but :(  you were right on this boxes e8300  (& the unusued q9400 I could currently replace it with)
[06:52] <guiverc> lotuspsychje, ^   and thanks for making me look !
[06:52] <lotuspsychje> np guiverc think there was a tool to test meltdown, forgot its name
[06:53] <lotuspsychje> !info spectre-meltdown-checker
[06:53] <ubottu> spectre-meltdown-checker (source: spectre-meltdown-checker): Spectre & Meltdown vulnerability/mitigation checker. In component universe, is optional. Version 0.40-3 (disco), package size 39 kB, installed size 173 kB
[07:07] <isomari> i keep getting this error on tuptime whenever I install or upgrade anything: *** update-locale: Error: invalid locale settings:  LANGUAGE="en_USA:en" LANG=en_US.UTF-8 LC_ALL="en_US"
[07:07] <isomari> oh. I'm using kubuntu disco dingo
[07:12] <guiverc> isomari, you might find this useful https://askubuntu.com/questions/162391/how-do-i-fix-my-locale-issue
[07:12] <isomari> guiverc: thanks. I'll check it now.....
[07:17] <isomari> guiverc: All the locales I'm using, "en_US.UTF-8", are listed correctly in /etc/locale.gen. I don't know why I'm getting that error.
[07:24] <guiverc> isomari, sorry I can't help, i believe they more warnings, only impacting programs that actually use those values (which may be few/none), but you'll have to wait for someone else if you need more sorry
[07:28] <isomari> guiverc: thanks. It's not that big of a deal. It doesn't seem to affect anything.
[07:32] <isomari> the other major issue I'm having with disc is that my Lan just doesn't work though it's configured right with no errors. I can't ping anything on my network. I've tried  netplan, NetworkManager. networkd and I even tried connman. I can only use my wlan but even it goes down smetimes and I have to reconnect.
[07:32] <isomari> s/disc/disco