[02:47] <asarch> What is the name of software center binary?
[02:47] <asarch> In Ubutun is "software-center"
[02:49] <Andrio> apt
[02:50] <asarch> I mean, the same for the graphical environment
[02:50] <asarch> I need to reconfigure the mirror for the repository
[02:50] <asarch> And this is a blind system
[02:50] <asarch> So I can ssh -X to it
[02:51] <asarch> But I need the name of the binary file
[02:51] <asarch> In order to configure the mirror address (to pick the best one)
[02:53] <asarch> The name of the app you can find in: Applications->System->Software Sources
[02:54] <asarch> (Its binary file name)
[02:54] <krytarik> "software-properties-gtk"
[02:55] <asarch> Thank you krytarik
[02:55] <asarch> Thank you very much :-)
[02:55] <krytarik> Sure.
[10:00] <natsu> hello?
[10:02] <fiet> \o
[12:49] <dipnlik> hi, anyone has tips on how to tile windows in a 66/33 split instead of 50/50?
[14:43] <crond> Hi, should I be concerned about the script I ran to test if my system was vulnerabole to meltdown/spectre saying it still is, even after I've done all updates?
=== xqb` is now known as xqb
[19:21] <cicdc> Does anybody know what happened to xfce4-hamster-plugin in 17.10? It seems it's no longer in the 'Extras' PPA
=== genius3k is now known as genius3000
[22:42] <Unit193> cicdc: You used it?  Huh.  Well there seemed to be very little interest, so we let it fade away.
[22:42] <cicdc> :(
[22:43] <Unit193> crond: I presume you ran spectre-meltdown-checker?  Meltdown should be addressed, but Spectre isn't really.
[22:43] <cicdc> Well I'll try the old fashion way and build from source
[22:43] <cicdc> Thanks for the info
[22:44] <Unit193> https://code.launchpad.net/~xubuntu-dev/+git/xfce4-hamster-plugin the packaging is all still there.
[22:52] <crond> Unit193, yeah
[22:53] <Unit193> You on 32bit?
[22:54] <crond> No, 64bit
[22:55] <crond> Linux 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:13:46 UTC 2018
[22:56] <crond> > STATUS:  VULNERABLE  (IBRS hardware + kernel support OR kernel with retpoline are needed to mitigate the vulnerability)
[22:56] <Unit193> That's spectre.
[22:56] <crond> Looks like 1 & 3 are not vulnerable, but 2 is.
[22:57] <Unit193> Expected.
[22:57] <crond> Anything I can do, or am I waiting on a BIOS update from Dell or CPU microcode or something?
[22:58] <Unit193> That, or compiler updates and everything recompiled.
[22:58] <crond> so basically it's all upstream one way or the other, i.e. nothing else I can do at the moment
[22:58] <Unit193> Pretty much, yeah.  Intel had a microcode update, but it caused issues.
[22:59] <crond> yeah I heard about that, but had never applied it to this machine
[22:59] <crond> well, I don't even know if it was pushed out for Linux in any case
[23:00] <Unit193> (It was, Debian updated, then reverted because of the issues and recall.)
[23:01] <crond>  Ah okay
[23:01] <crond> guess I'm waiting on Intel then, 2 of 3 are patched, nothing else to be done at the moment
[23:02] <crond> thanks Unit193
[23:02] <Unit193> Sure thing.
=== xqb` is now known as xqb