[04:04] <lotuspsychje> good morning to all
[05:59] <lotuspsychje> https://extensions.gnome.org/extension/669/wobbly-windows/
[05:59] <lotuspsychje> lol
[06:26] <ducasse> good morning
[07:19] <lotuspsychje> !info ubuntu-unity-desktop
[07:19] <lotuspsychje> ducasse: ^
[10:16] <BluesKaj> Howdy folks
[10:49] <ducasse> hi BluesKaj - all well today?
[10:50] <BluesKaj> hey ducasse , yeah fine here, and you?
[10:51] <ducasse> i'm ok, just come home from shopping groceries
[10:52] <ducasse> raining a bit, although not much
[10:55] <BluesKaj> it's dry as a bone here, no rain for almost 3 weeks
[10:55] <BluesKaj> or very little
[10:58] <BluesKaj> damn uefi, users ar still having trouble , even with auto installs on clean hdd-disks
[10:58] <ducasse> we've had a little bit, but not enough to make a real impact
[10:59] <ducasse> uefi has never given me any problems, but i think i'm lucky enough to have a fairly good implementation
[11:00] <BluesKaj> yeah, had no trouble on my laptop, but I used legacy on the desktop ..still boots very fast less then 10secs from post page to desktop
[11:01] <BluesKaj> counting the login
[11:02] <BluesKaj> to me uefi is useless since I don't use windows anywhere
[11:03] <ducasse> it's nice if you boot more than one distro on one machine
[11:04] <BluesKaj> my laptop had problems without uefi so i finally succumbed and followed a very well written tutorial to install Kubuntu using gpt/eufi
[11:05] <BluesKaj> what's the advantage over legacy with 2 distros on one pc?
[11:09] <ducasse> i just think it's handled in a nicer way, each distro gets a subdir on the efi partition
[11:17] <TJ-> And other OSes don't stamp on the bootloader, so it plays nicely with Windows etc
[11:22] <BluesKaj> no more windows on my machines
[11:22] <lotuspsychje> !info roxterm cosmic
[11:23] <lotuspsychje> BluesKaj: me neither, ubuntu everywhere here
[11:24] <ducasse> !info roxterm xenial
[11:25] <lotuspsychje> aha
[11:25] <BluesKaj> I have 3 Kubuntu machines and one RPI3 with Raspbian
[11:25] <lotuspsychje> little gap
[11:25] <ducasse> lotuspsychje: ^^ that was when it was last in the repos
[11:25] <lotuspsychje> cool ducasse
[11:25] <lotuspsychje> BluesKaj: what purpose has your pi?
[11:28] <BluesKaj> basically a toy at first , then I thought of it as an alternative pc in case my other/older pc died, but then my son gave me a new MSIZ370 board with 15cpu and 16GB Ram m so now the RPI3 is basically idle
[11:29] <lotuspsychje> kk
[11:29] <BluesKaj> so it's just a toy again
[11:33] <BluesKaj> guess I could use it as a Kodi box, but I have Kodi on 2 other machines already
[11:34] <tomreyn> looks like the community wiki's CSS got broken? https://help.ubuntu.com/community/InternetRelayChat/Registration
[11:34] <tomreyn> main page now https://help.ubuntu.com/community/CommunityHelpWiki
[11:35] <lotuspsychje> !register
[11:35] <lotuspsychje> tomreyn: forward it to the ops plz
[11:35] <tomreyn> main page on jan 2 http://web.archive.org/web/20180103071122/https://help.ubuntu.com/community/CommunityHelpWiki
[11:35] <tomreyn> lotuspsychje: which ones?
[11:36] <tomreyn> ircops seems like the wrong place to report it
[11:36] <TJ-> tomreyn: thanks for the bug updates; the reproducer is a pain. I was up until 4am working on it last night. Feeling very frazzled right now :)
[11:37] <tomreyn> guess i'll report the broken css to #canonical-sysadmin although community stuff isn't really their domain.
[11:37] <lotuspsychje> or perhaps wiki team
[11:37] <tomreyn> TJ-: i read over it, was worrying about your sanity ;)
[11:38] <TJ-> LOL yeah, it's a weird one...they named the function well though ..._racy_  ... I'm thinking there's a timing issue somewhere
[11:38] <tomreyn> not really, but you seem to do a good (maybe too good?) job on focussing on issues
[11:39] <tomreyn> i can be the same if i really want to work something out.
[11:39] <TJ-> But I still am annoyed there's no explanation why Ubuntu is still using a 2012 release of polkit and backporting rather than keeping with upstream! Doesn't make sense, and I bet that is where the issue is
[11:39] <tomreyn> yes this strikes me as wrong, too
[11:39] <TJ-> I read through all the commits on upstream and there's been some major changes.
[11:40] <TJ-> so you'd have to know about all of those, and their implications, in backporting. Canonical has never been great at that kind of thing either
[11:41] <TJ-> For those wondering what we're talking about: possible regression due to a CVE patch backport in Policykit. Bug #1784964
[11:42] <tomreyn> debian also got 0.105 everywhere excpet in experimental
[11:42] <TJ-> right, and Ubuntu syncs from debian then backports! What a mess
[11:42] <tomreyn> i guess this can be why, see its all their fault!!11 ;-)
[11:42] <TJ-> I wonder if there's anything in the mailing lists as to why
[11:43] <tomreyn> you'll be all frazzled tomorrow morning.
[11:43] <lotuspsychje> lol
[11:44] <TJ-> I'm trying to have a day off today! Been hard at programming since last Saturday. Crash-course in Ruby/Vagrant to hack vagrant-mutate to fix bugs before I can move on with another project!
[11:51] <tomreyn> Don't get me wrong, I'm glad you're spending this much effort on it, i guess it can and will affect many users.
[11:53] <TJ-> I don't like bugs that can pop up like this at inconvenient moments. That usually then happens at the worst possible time. Like me yesterday - only fired up this PC to access some devices only it has the credentials for... should take 5 minutes... 3 hours later still trying to figure out why I can't read logs :)
[11:53] <BluesKaj> that bot attack just resumed on #ubuntu
[12:01] <lotuspsychje> its all over BluesKaj freenode all channels, other networks
[12:07] <guiverc> couldn't they make the channel +r (at least for a few days), it worked well on the few channels I 'live' in
[12:07] <TJ-> most of the Ubuntu channels were +r yesterday
[12:07] <TJ-> where's hggdh when needed!? :)
[12:08] <lotuspsychje> what a bad timing for .1
[12:08] <TJ-> It's a great way to collect lists of compromised IP addresses that should be blacklisted though :)
[12:09] <guiverc> yeah, was looking back & was done to this channel ... unit193 did it on some channels...
[12:09] <lotuspsychje> this botnet is surely an insider, one of his bots name in #gnome this morning was 'bazhang7'
[12:09] <TJ-> nah, that's just the way it is generating nicknames from those it sees
[12:10] <TJ-> what gets me is the text is generally the same, the servers themselves could k-line any client that sends that text without sending the text onto the network
[12:11] <guiverc> TJ-, i agree; that's the way I'd stop it (until I worked out a smarter way..); though maybe some coder is testing a better fix (just hasn't got it working yet....
[12:12] <TJ-> they must be slower than me learning Ruby then :p
[12:12] <TJ-> I've deployed complex lambdas but got no idea how they achieve what they do :D
[12:13] <TJ-> all because Ruby doesn't have the concept of static local variables in methods
[12:14] <guiverc> :)
[12:30] <TJ-> tomreyn: so, we have another victim... using KDE
[13:01] <hggdh> most of the namespace is under +r; some channels decide for themselves, some other we enforce
[14:05] <pauljw> hi everyone
[14:06] <BluesKaj> Hi pauljw
[14:06] <pauljw> morning BluesKaj
[14:07] <BluesKaj> praying for rain here
[14:07] <daftykins> been a while since the last?
[14:08] <pauljw> :( sorry about that, we've been luck here and have had plenty.
[14:08] <BluesKaj> right
[14:08] <BluesKaj> almost 3 weeks since
[14:08] <pauljw> ouch
[14:10] <BluesKaj> bush is tinder dry ....forest fires all over our region ..not real close to us, but the potential is there
[14:10] <daftykins> that's pretty scary
[14:11] <BluesKaj> 20 min t-storms don't do much except start new fires if the lightning strikes
[14:12] <pauljw> that's not good.
[14:13] <pauljw> i joke about hating mowing the yard, but would much rather have to cut twice a week than to have worry about it catching fire...
[14:14] <BluesKaj> a major hwy might be closed if the fire nearby gets much closer than 3 miles....the smoke is already causing visibility problems
[14:19] <BluesKaj> hope my daughter can get through tomorrow on that hwy without having to do a detour
[16:32] <bolt22> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[16:32] <bolt22> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[16:52] <tomreyn> TJ-: i see, so it's definitely not gnome / gtk related, good to have this ruled out.
[16:55] <TJ-> it's a weird one for sure. obviously related to login procedures. I think it's something to do with systemd session management - something like a lightdm session doesn't associate UID correctly with the user-slice, but console login does. That'd explain why the order of console terminal vs GUI terminal makes a difference
[16:57] <TJ-> i also noticed libpam-kwallet* were updated, and I see lightdm/kwallet error messages in syslog. So far I've not thought of a way that would cause the symptom though
[16:58] <tomreyn> TJ-: does screen locking work for you on the affected system, though?
[16:58] <TJ-> I believe so, but not tried it. I'll test.
[16:58] <tomreyn> my other issues are chromium-browser taking forever to load and the system not shutting down properly becuse session manager fails to shut down my users' session
[16:59] <TJ-> tomreyn: Yes
[16:59] <tomreyn> okay so i guess i do have another issue on 16.04
[16:59] <tomreyn> an additional issue
[16:59] <lotuspsychje> hggdh: im idling in #gnome they just have +cnt, spambots all day
[17:01] <TJ-> do you see "lightdm: pam_kwallet5(lightdm:session): pam_kwallet5: Impossible to write walletKey to walletPipe" in auth.log ?
[17:05] <tomreyn> TJ-: plenty, but it's a couple hours ago now: https://paste.ubuntu.com/p/Rz5PMY4648/
[17:07] <TJ-> tomreyn: right, so just like 16.04 where it used to complain that pam_kwallet.so not found all the time :)
[17:08] <tomreyn> TJ-: this IS 16.04
[17:08] <TJ-> tomreyn: is that a liveISO instance? I notice mine shows "pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket" <--- note the path diff
[17:09] <tomreyn> i dont have an affected 18.04 system at this time.
[17:09] <TJ-> tomreyn: ahhh, 16.04 possibly used /tmp instead. Can't recall seeing that on 16.04 before upgrade though
[17:10] <tomreyn> ~/.xsession-errors contains this line: dbus-update-activation-environment: setting PAM_KWALLET_LOGIN=/tmp/kwallet_user1.socket
[17:10] <tomreyn> and this docket exists.
[17:10] <tomreyn> *socket
[17:21] <TJ-> oh, thanks for making me look! I found something suspicious but launchpad won't accept comments right now.
[17:21] <TJ-> Just noticed in $HOME/.xsession-errors the following:
[17:21] <TJ-> (polkit-gnome-authentication-agent-1:4029): polkit-gnome-1-WARNING **: 15:04:54.498: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
[17:23] <hggdh> lotuspsychje: yes indeed, but it seems the bots are learning, and (for the moment) not getting in channels where they found +r
[17:24] <hggdh> lotuspsychje: since +r is rather restrictive, we would like to take it out as soon as possible, We can set it on again if needed
[17:26] <pragmaticenigma> Suddenly the support question about Hiri makes total sense where it came from
[17:27] <pragmaticenigma> posted yesterday: https://itsfoss.com/hiri-email-review/
[17:27] <tomreyn> i got those in syslog, TJ
[17:28] <tomreyn> but i think those have always been all over the place
[17:35] <nacc> 16.04.5 released
[17:41] <pragmaticenigma> yay!
[17:59] <nacc> pragmaticenigma: oh goodness, good luck
[18:01] <pragmaticenigma> nacc: It's a ... if it's more than a keyboard mapping issue... I'm going to tell them to backup what they can, wipe the machine and start over
[18:05] <nacc> pragmaticenigma: i'm super confused by their symptoms. Are they logged in now? How do they know their password doesn't work, etc?
[18:06] <pragmaticenigma> I think they're local system is set to autologin to GUI, which allows them access right now. I honestly have a feeling they just forgot they changed their password
[18:12] <nacc> right
[18:12] <nacc> could easily be
[18:19] <pragmaticenigma> I wish them the best
[18:46] <tomreyn> https://marc.info/?l=linux-kernel&m=153323015508428&w=2
[21:39]  * hggdh wonders how bad Red Hat is doing with a 3.6 kernel officially supported on RH 6.9
[21:39] <nacc> heh
[21:39] <nacc> they have some good kernel engineers ;)
[21:40] <hggdh> oh, but it is outdated!
[21:40] <nacc> i have no idea how they deal with spectre/meltdown, if they do
[21:40] <hggdh> :-)
[21:40] <nacc> heh
[21:41] <hggdh> they probably backported somehow. Given the size of the kernel teams there, I would not be really surprised
[21:41] <nacc> yeah, I'm just not even sure how you'd backport some of those changes
[21:41] <nacc> they were hard enough to move back a few ubuntu versions
[21:42] <hggdh> I know. But there must have been a LOT of pressure on the kernel team there to Do Something.
[21:42] <nacc> yeah, absolutely
[21:43] <nacc> their customers would have happily paid for it
[21:44] <hggdh> oh, I am sorry, just checked at one of the servers. RH 6.9 running with kernel 2.6
[21:45] <nacc> even better! :)
[21:45] <hggdh> :-)
[22:04] <daftykins> my my, making old android phones look current ;D
[22:07] <mwsb> daftykins: arch is the best thing for serious devops
[22:07] <daftykins> you know it! :)
[22:07] <mwsb> Lol
[22:08] <daftykins> second to a gentoo stage 1 install of course
[22:08] <daftykins> if that was their term for the compile-everything one
[22:08] <mwsb> But you don't understand all the flaws
[22:09] <daftykins> that's true, i must only use something where i know the true extent of broken-ness
[22:09] <mwsb> Lol
[22:09] <daftykins> for the other guys - we had someone arguing that arch should be used on production servers because it's the only distro you can install 'minimal' - and then it's the most stable because they know all if its' flaws
[22:10] <daftykins> xD
[22:14] <daftykins> mwsb: i'm imagining zipper running servers as being a dude spinning plates on sticks now :D
[22:15] <daftykins> "it is ok, because we know all the problems, 1) the plate could crack 2) gravity"
[22:16] <mwsb> Lol
[22:24] <ducasse> \o daftykins - picked up your bike?
[22:24] <daftykins> sure did - and am very disappointed
[22:47] <toto_> hi
[22:48] <daftykins> lo
[22:49] <toto_> i have just finish ubuntu 18 installation on my computer
[22:49] <toto_> and it works perfectly
[22:49] <toto_> so happy
[22:49] <toto_> ;-)
[22:52] <Bashing-om> !yay | toto_
[22:54] <toto_> i'm discovering it and i like everything for the moment
[22:54] <toto_> because usually i install debian or fedora
[22:56] <toto_> i'm french and you?
[22:57] <Bashing-om> toto_: Arkansas ridge runner .
[23:00] <toto_> nick toto_fr
[23:01] <tomreyn> here's a current flash utility for insyde bioses on (amongst other) linux (/Linux/x64/x64/H2OFFT-Lx64): http://download.udoo.org/files/UDOO_X86/UEFI_update/UDOOX86_B02-UEFI_Update_rel104.zip
[23:01] <tomreyn> most acer's require this.
[23:02] <Bashing-om> tomreyn: Noteing :) .. acer. what a pain .
[23:02] <tomreyn> source: https://www.udoo.org/forum/threads/updating-fw.7729/ https://github.com/malaire/misc/tree/master/udoo-x86
[23:02] <tomreyn> it's for udoo's new x86 gear
[23:03] <tomreyn> but the firmware writer is generic
[23:04] <tomreyn> https://www.insyde.com/products/developertools
[23:04] <tomreyn> also worth a bookmark https://firmwaresecurity.com/tag/insyde-software/
[23:05] <toto_fr> exit
[23:06] <Bashing-om> tomreyn: Yup - 'nother good one :)
[23:06] <tomreyn> apparently the proper pronounciation of UEFI and SCPI are the hot topics in insyde firmware development these days
[23:06] <tomreyn> and yes, acer is the pain
[23:07] <daftykins> surely acer do windows utilities :)
[23:08] <Bashing-om> tomreyn: Wifey runs her graphic station on an Acer machine ( Win10) .. I dread if and when she wants ubuntu back .
[23:08] <tomreyn> :)
[23:09]  * tomreyn crosses fingers
[23:10] <daftykins> 10 wfm ^_^
[23:51] <nacc> tomreyn: in case it's relevant, IntelCore is in my /ignore
[23:51] <tomreyn> :) i guess they should be on mine, too
[23:51] <tomreyn> thanks
[23:52] <daftykins> indeed all Core and Core 2 systems should be ignored now too ;)
[23:54] <nacc> daftykins: that was my initial thought months ago when they first started asking non-ubuntu questions in #ubuntu, as well :)
[23:54] <nacc> daftykins: also, no one who is actually associated with Intel would put it in their nick
[23:54] <tomreyn> maybe intel pentium N4000, too
[23:58] <tomreyn> just trying to give them a last reasonable chance before i decide to /ignore