[01:31] <IsSnooAnAnimal> Hello there! I booted up my VirtualBox Lubuntu 16.04 VM to a blank screen with only a cursor. I can get into TTY, and I tried just about everything I can think of. Booting to a previous kernel, updating + upgrading, reinstalling lightdm and lubuntu-desktop, executing startx, nothing seems to work.
[04:02] <IsSnooAnAnimal> jesus
[06:52] <qswz> Any of you using chromium?
[06:52] <qswz> you'll notice that each tile you make a browser search, there's a &client=ubuntu querystring
[06:52] <qswz> time*
[06:53] <qswz> it's lubuntu specific, doesn't happen on ubuntu
[06:54] <qswz> https://bugs.launchpad.net/lubuntu-artwork/+bug/1766937 I reported it there
[10:43] <jong> hello?
[10:47] <jong> can anyone help me, why if i installed netbeans7.4 and jdk7  on my laptop with lubuntu my only one browser firefox after the installation the two said software i can no longer open it. it says profile is missing.
[13:22] <antis> dunpeal: IDK, but why don't you check with a live-system? I suspect HiDPI support improved with LXQt.
[14:24] <zleap> hi
[14:25] <zleap> is there a tool in lubuntu for controling the touchpad,  I would like to disable pad while typing in a similar way to how I can do that in xubuntu
[17:58] <n-iCe> hi
[20:52] <antis> zleap: i guess you have a key to disable the touchpad?? This is done via ACPI. Has to be configured in grub (yeah the bootloader).


[00:01] <krytarik> Then I'll go to bed now and let you plug along with the list. :)
[00:01] <krytarik> I've been awake for 24 hours now...
[00:03] <krytarik> Mainly just because it's also a rather unfortunate time to get at 2 AM in the night though.. :P
[00:06] <Wild_Man> night
[00:07] <Bashing-om> krytarik: Thanks heaps for your guidance and hand holding - this day :)
[00:07] <krytarik> Ugh, in fact it also carried over the full history of the template page though, so maybe just copy the stuff from the raw view and create a new page with it.
[00:08] <krytarik> Sure, you two also do lots of things I hope I can build on. :)
[00:12] <pleia2> did you copy the IssueTemplate or use the wiki template feature?
[00:12] <pleia2> copying will bring in history, built in template feature will not
[00:13] <pleia2> Wild_Man: btw, where the wiki page says "Welcome to the Ubuntu Weekly Newsletter, Issue ### for the week of April 8 - 14, 2018." you want to replace ### with the issue number, some of the scripts rely upon this
[00:13] <krytarik> Wild_Man: So guess the proper workflow from now is: delete the current page, visit  https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue523  where it then asks if you want to create a new page, and the select the page template we have from there.
[00:14] <pleia2> ++
[00:14] <krytarik> pleia2: Yeah, I also just figured out how the template system works there. :P
[00:14] <pleia2> :D
[00:15] <Wild_Man> okay, thanks pleia2
[00:17] <krytarik> And yes, indeed a missing issue number would be horrible on many ways and that too. :P
[00:18] <krytarik> Eh, can't speeell anymore..
[00:19] <krytarik> Wild_Man: Seriously, please recreate the page following the steps I outlined, rather than editing the current one any further.
[00:21] <Wild_Man> I just deleted it
[00:24] <Wild_Man> krytarik, even with it delete when I click on the address and it brings it up it shows revision history for everyone all the way back to 2009
[00:25] <pleia2> hold down ctrl and shift when you refresh
[00:25] <pleia2> it's just cached
[00:25] <pleia2> (it is gone)
[00:25] <Wild_Man> okay
[00:27] <Wild_Man> pleia2, what he wants to get rid of I believe is the edit history so it looks clean but I see edit history going way back, do you see the same when you click on info?
[00:27] <krytarik> I don't see an option to pull in a template on creating a new page now though - other than copy-pasting from the template yourself.. :P
[00:28] <Wild_Man> I do not either
[00:28] <pleia2> when you load up the empty page, just search for "IssueTemplate"
[00:28] <pleia2> then click on "UbuntuWeeklyNewsletter/IssueTemplate"
[00:28] <pleia2> that will copy the issue template into a new, empty page
[00:29] <pleia2> you do this instead of selecting "Create new empty page"
[00:29] <Wild_Man> thanks please that worked
[00:29] <Wild_Man> pleia2,
[00:29] <krytarik> Oh heh!  On the page where you are also just offered to create an empty page at the top.. >_>
[00:30]  * pleia2 nods
[00:30] <krytarik> I never paid particular attention to the list there.. :P
[00:30] <pleia2> hehe
[00:37] <krytarik> Wild_Man abandoned the page creation for now it seems.. :P
[00:38] <Bashing-om> If nothing else I can do, going back to my regularly scheduled support :)
[00:41] <krytarik> Multitask between #ubuntu & co and lending Wild_Man a hand when he reappears, I'd think would be nice. :)
[00:42] <Wild_Man> I have it recreated I think, I have to eat real quick
[00:44] <Bashing-om> krytarik: Wild_Man I pop back up "on demand" :P
[00:44] <Wild_Man> Bashing-om, ok, you can see this right https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue523
[00:45] <Bashing-om> Wild_Man: Yepper .. page loaded .
[00:45] <krytarik> Heh, it doesn't actually kill the history even now though, it just refilled the page content back up.. >_>
[00:47] <krytarik> Wild_Man: So sorry for trying the obvious route first, now we'll just have to live with what we got. :P
[00:47] <Wild_Man> history goes back to like 2009
[00:47] <Wild_Man> np
[00:47] <Bashing-om> Wild_Man: History ? All I see is the template and "contents" .
[00:47] <pleia2> if the template was indeed used this time, it could be because of the deletion/recreation cycle, it just kept it :(
[00:47] <Wild_Man> wiki is a strange animal
[00:48] <pleia2> if you look at past issues, it worked fine
[00:48] <pleia2> just be sure to use the template on the first try with the next issue ;)
[00:49] <Wild_Man> I did this time I just messed up the title and had to rename it
[00:50] <Wild_Man> krytarik, was hoping to not show that history of renaming
[00:53] <Wild_Man> Bashing-om, ok
[00:53] <Bashing-om> Wild_Man: loaded https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue523 and I do not see a history .. should I login to see an effect ?
[00:53] <krytarik> Well, apparently the shuffling of the page location wasn't logged there either.
[00:54] <Wild_Man> Bashing-om, no that is fine I just wanted to make sure the page showed up
[00:54] <krytarik> Bashing-om: Click on "Info" at the top.
[00:54] <Bashing-om> Wild_Man: K .. back in lurk mode .
[00:55] <Wild_Man> you will have to be logged in to see the info i think
[00:55] <krytarik> No.
[00:55] <krytarik> I know because I'm usually never logged in and always see the history. :P
[00:56] <Wild_Man> I am always logged in so I just thought we had to be to see it
[00:57] <krytarik> Heh, "always logged in to the wiki" is not something I hear often.. :P
[00:58] <Bashing-om> sounds like Wild_Man is addicted :)
[00:58] <krytarik> Anyway, enough screwing up at the wiki for now - g'night!
[00:58] <krytarik> Sounds like he is editing the wiki all the time. :D
[00:59] <krytarik> So should have tons of experience by now! \o/
[01:03] <Wild_Man> What I mean is when I click on a wiki page I am logged in but I do not click on them very often
[01:16] <Wild_Man> pleia2, under in this issue, so I list just one of the topics in the general community section or all of them?
[01:17] <Wild_Man> so/do
[01:37] <Bashing-om> Wild_Man: No news is good news .. any way I can help ?
[01:37] <Wild_Man> tsimonq2, you around?
[01:38] <Wild_Man> Bashing-om, I am afraid for us both to be editing the wiki at the same time, I do not think it works as well as gdocs
[01:38] <Wild_Man> if you want to give it a go I will take a break that is for sure
[01:39] <Bashing-om> Wild_Man: That is why I did not signin .. as had that same thought .
[01:39] <Wild_Man> I can save it and you can take over a few minutes is you want too
[01:39] <Bashing-om> Wild_Man: What is it that "we" are then doing ? I am all for learning what to do .
[01:40] <Wild_Man> right now I am adding what will be in this issue, I am comparing it to older issues to get a better understanding
[01:41] <Wild_Man> once that is done it will be pretty eassy to copy and paste
[01:41] <Bashing-om> Wild_Man: Sure .. I do as I can . Not much going on in support .
[01:41] <Wild_Man> I was thinking about coping and pasting from gdocs then go back to what is in this issue
[01:44] <Wild_Man> I have saved it, look at an old news letter for reference, I click on the edit of the old one to help with syntax, like for bullets use the * but you have to indent it four spaces
[01:44] <Wild_Man> brb
[01:46] <Bashing-om> Wild_Man: You mean that we are manually c/p from https://docs.google.com/document/d/18ZbtFHQq6uMj7iuRLd11VH8V5Uc_FA0IfgiRUcbMbQk/edit to wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue523 ???
[01:50] <Wild_Man> Bashing-om, yes but you have to use an old one and compare the two to make sure the formatting is correct for each piece you paste, I would paste a small piece then preview it and make sure is is formatted correctly
[01:52] <Wild_Man> I know moin does not like more then one person at a time editing it
[01:53] <Bashing-om> Wild_Man: And again ,, I have no experience with formatting in the wiki .. will be a slow learning process :(
[01:54] <Wild_Man> me to basically, I just learn as I go
[01:56] <Bashing-om> Wild_Man: Trying to signin now .. not looking good for the home team :(
[01:58] <Bashing-om> Wild_Man: OK ! I am at the ubuntu wiki HOME page. what to do to load the working template ?
[02:00] <Wild_Man> Bashing-om, it is here https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue523 give me a minute I am going to post the loco events I ran the script and have the results
[02:01] <Bashing-om> Wild_Man: When I go to https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue523 ; I have a blank document in my browser .
[02:04] <Wild_Man> Bashing-om, try now!
[02:04] <Bashing-om> Wild_Man: ack .. will advise .
[02:04] <Wild_Man> I was working on it, I think that is why
[02:04] <Wild_Man> I am doing pretty good
[02:06] <Wild_Man> Bashing-om, how you doing?
[02:07] <Bashing-om> Wild_Man: I am so lost ! .. I still have a blank template . Do I not need to signin and go through the ubuntu wiki HOME page ??
[02:07] <Wild_Man> no you should be able to just click the link you posted, that is what I did and it worked
[02:08] <Wild_Man> Bashing-om, may clear the cache on that page by going to more actions
[02:08] <Bashing-om> Wild_Man: My well being .. I have a pounding headache .. and my back hurts :(
[02:10] <Wild_Man> Bashing-om, do not worry about it tonight I will continue, I am doing good at the moment
[02:12] <Bashing-om> Wild_Man: After the cache clear ,,, I now have "loco events" of 18.04 .. I presune as the result of a script -- but that is all .
[02:13] <Bashing-om> presume*
[02:15] <Bashing-om> aspirin ! will be good for the effort .
[02:15] <Wild_Man> that is because I am working the page I think give me a minute I will save it then clear cache and try
[02:15] <Wild_Man> Bashing-om, I saved it and stopped working try now please
[02:17] <Bashing-om> Wild_Man: ack
[02:17] <Wild_Man> Bashing-om, did not work?
[02:18] <Wild_Man> I do not understand all these shot three letters
[02:18] <Wild_Man> shot/short
[02:20] <Bashing-om> Wild_Man: What I see in a screen shot : http://i.imgur.com/q6suOv6.png .
[02:21] <Wild_Man> Bashing-om, that is it, you have to remember it is a work in progress
[02:22] <Wild_Man> I have added all that so far
[02:23] <Bashing-om> Wild_Man: But -- you had advised you had been copying and pasteing from gdoc .. I see nothing from gdoc .
[02:24] <Wild_Man> Bashing-om, no I said I was thinking about it and when you said you were going to take over I said you can copy and paste from gdoc
[02:25] <Wild_Man> I will take a break a few minutes and you can do that, look at my messages above to see how I suggested you do it
[02:26] <Wild_Man> I will be right here
[02:29] <Bashing-om> Wild_Man: I give it my best.
[02:29] <Wild_Man> Bashing-om, good enough
[02:36] <Bashing-om> Wild_Man: Still to this time I can not login (immutable page) . click sighin and that takes me to the ubuntu wuku home page .. on this page I am lost as to how to get to the wiki we are editing .
[02:36] <Bashing-om> wiki*
[02:41] <Wild_Man> Bashing-om, it should sign you in, it always directs you away from the page you were on now go to https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue523
[02:42] <Bashing-om> Wild_Man: there .
[02:42] <Wild_Man> You will still be logged in after you click on that link
[02:42] <Wild_Man> moin is something but it gets easier
[02:43] <Wild_Man> Bashing-om, you are signed in and on that page right?
[02:44] <Bashing-om> Wild_Man: Nope .. have " Immutable Page " . and if I cloik on signin takes me eventually to the ubuntu wiki HOME page . what other action than clicking signin is there ?
[02:45] <Wild_Man> it you go to the home page are you sign in
[02:46] <Wild_Man> it/when
[02:46] <Wild_Man> Bashing-om, ^^
[02:46] <Bashing-om> Wild_Man: Yes, ok .. so I ask again .. from the home page how to I get the wiki page we are editing ??
[02:49] <Wild_Man> leave that page open then just click on the link above to the wiki page we are working on and you should stayed signed in. You should see your name close to the top of the page that means you are signed in
[02:51] <Bashing-om> Wild_Man: trying :)
[02:52] <Bashing-om> Wild_Man: Yepper !  Making progress .
[03:00] <Wild_Man> Bashing-om, you doing okay?
[03:27] <Bashing-om> Wild_Man: Up to;; .. the LoCo News section in the wiki . Moving real slow .. not checked my work to this time .
[03:27] <Wild_Man> Bashing-om, preview it and let me know
[03:37] <Bashing-om> Wild_Man: Ouch ! A lot of " Edit conflict - other version:" . Not seen what I can do about it !
[03:37] <Wild_Man> Bashing-om, that is why I said do one little piece at a time the check it
[03:38] <Wild_Man> bhave you saved it yet?
[03:45] <Bashing-om> Wild_Man: No O have not saved it .. this is the 3rd section .
[03:45] <Bashing-om> no I have not *
[03:49] <Wild_Man> Bashing-om, is it looking better? I can not see it until it is saved but if it is real bad you can cancel it before it is saved
[03:49] <Bashing-om> Wild_Man: click cancel or try and see what the issue is ?
[03:50] <Wild_Man> If you want me to look save it
[03:50] <Wild_Man> but then it can not be canceled but I am sure we can fix it
[03:51] <Bashing-om> Wild_Man: At this point I am the more comfortable to cancel .. is no big deal to redo the c/p . family dramma at this time .. lemme attend to family . canceling out.
[03:52] <Wild_Man> ok thanks Bashing-om
[03:57] <Bashing-om> Wild_Man: and now logged out of the wiki
[03:58] <Wild_Man> Bashing-om, okay, you going to hang around?
[04:02] <Bashing-om> Wild_Man: Yeah ,, back when things here settle out .
[04:03] <Wild_Man> Bashing-om, I have a lot of done now
[04:18] <Bashing-om> Wild_Man: You the man :) Moving right on along .. I be back at your back .
[04:37] <Wild_Man> Bashing-om, I am done for the night if you are up to it will you check all the links and make sure they work
[04:38] <Bashing-om> Wild_Man: That I can do :)
[04:40] <Wild_Man> Bashing-om, Thanks!
[04:40] <Bashing-om> Wild_Man: A quick look and looks good . checking links now .
[04:41] <Wild_Man> It still needs a little work, what is in this issue needs to be finished but I am to tired tonight
[04:44] <Wild_Man> Krytarik the wiki is mostly done, "what is in this issue needs finished"
[04:45] <Wild_Man> Info from askubuntu and I could not find unconfirmed bugs info, I did not try to compare previous +- bugs because the last news letter 17.10 was in dev or just released
[04:47] <Bashing-om> Wild_Man: http://loco.ubuntu.com/events/ubuntu-ko/3733-ubuntu-18.04-lts-release-party-@-busan/ does not complete .
[04:49] <Wild_Man> Bashing-om, can you remove and save?
[04:50] <Wild_Man> If not just post the ones that do not work here and krytarik or I will remove them tomorrow
[04:51] <Bashing-om> Wild_Man: Yeah will do  ..#2 http://loco.ubuntu.com/events/ubuntu-ko/3729-ubuntu-18.04-lts-release-party-@-seoul/ . ) does not like the @ ??
[04:52] <Wild_Man> Bashing-om, without glasses I can barely see so I it needs removed please do so.
[04:53] <Wild_Man> Bashing-om, I copied them right out of the terminal after running the command
[04:54] <Wild_Man> Bashing-om, be my guess that some of those loco teams no longer exist
[04:59] <Wild_Man> Bashing-om, the other links or working with the @ so it is not that
[05:12] <Wild_Man> or/are
[05:21] <Bashing-om> Wild_Man: Is a long process to verify the links .. am up to "Ubuntu 16.04 Updates" and taking a short finger rest break .
[05:23] <Wild_Man> Bashing-om, I know, there is a lot of them
[05:24] <Wild_Man> I think there will be less next time since we are doing weekly
[05:24] <Bashing-om> Wild_Man: So far with 3 DNE's .. loco all .. maybe I see what is up prior to removing the loco entries .
[05:25] <Wild_Man> okay thanks
[05:25] <Bashing-om> Wild_Man: Meeds to be done anyway .. just dewww eeeett .
[05:27] <Wild_Man> if I could not run a script to get them they would not be there at all
[05:27] <Wild_Man> soooo many!
[05:33] <Bashing-om> Wild_Man: That's a good idea ! back to verifying .
[06:04] <Bashing-om> links verified up to "Ubuntu 17.10 Updates" Break time !
[06:05] <Wild_Man> Bashing-om, thanks good work!
[06:09] <Bashing-om> Wild_Man: thought you had called it for this session :P
[06:11] <Wild_Man> Bashing-om, I am relaxing with my wife, no more work, going to bed soon
[06:14] <Bashing-om> Wild_Man: My other half has hit the sheets . I got to be up at OH dark thirty but will finish what is on the plate !
[06:20] <Wild_Man> Bashing-om, thanks! do not over do it.
[06:53] <Bashing-om> Fixed the 3 Korean loco links and all links are all verified ! - NEXT - ??
[07:25] <Bashing-om> Calling it a night and catching 2 Zs - will pick this back up in about 5 hours .
[09:39] <krytarik> Bashing-om: Yeah, there is something funky about the '@' in the Korean LoCo's event links, nice you could figure it out too.  And I don't think we're supposed to check all the update links.. :D
[09:47] <krytarik> ...Well, at least not manually anyway.
[09:49] <krytarik> Heh, looks like Wild_Man accidentally killed the template. :D
[09:55] <krytarik> Reverted.
[11:05] <krytarik> Oh, forgot the camelCase check..
[12:11] <Bashing-om> krytarik: making progress ... moving on along . next for me ?
[12:13] <krytarik> Morning.  Nothing yet I guess, the wiki page is ready so far, and publishing is a bit later today.
[12:15] <Bashing-om> krytarik: HoKay :)
[12:16] <krytarik> Could have a look at the changes I've done there though. :)
[12:18] <krytarik> Basically a bunch of formatting fixes, and then the issue summary.
[12:19] <Bashing-om> krytarik: Got to run to towm .. a few minutes will and look soon .
[12:58] <Bashing-om> Looking now at what we have produced.
[13:11] <Bashing-om> By Golly ! .. I think we dooodd it . I am proud for us .
[15:12] <Wild_Man> hello krytarik, it is published correct? I can put it on the forum now?
[15:14] <krytarik> No, it's not published yet - I just dropped the 'work in progress' bit already because the wiki page is basically done.
[15:15] <krytarik> Otoh, I'm not sure why we shouldn't just start now.. :)
[15:16] <Bashing-om> krytarik: Wild_Man Me not know much .. but looked good to me .
[15:17] <Bashing-om> Wild_Man: By the way ,, I found the errors in those 3 Korea links and fixed .
[15:17] <Wild_Man> krytarik, okay! I left this in Security Team - 12 October 2017 - https://insights.ubuntu.com/2017/10/12/security-team-weekly-summary-october-12-2017 even though it is old so we could move it to the gdoc so we can find it next time, do we leave it in the wiki or paste it to gdoc then remove ti?
[15:17] <Wild_Man> Bashing-om, nice! Thanks
[15:18] <Wild_Man> I assume it was not an error because of the copy and paste?
[15:19] <Bashing-om> Wild_Man: No .. upstream from there .. As it is a party notice, do not know that is worth the time to find out where it breaks .
[15:20] <krytarik> Wild_Man: Ugh, I didn't notice you carried those old ones over.. so please drop off the wiki, yes - not sure we want the March ones either, that is.
[15:21] <Bashing-om> krytarik: I failed there also to note old info :(
[15:22] <Wild_Man> krytarik, I did not carry it over they are already present so we can find the links easier next time. I just did not remove that one because it is not present in the gdoc
[15:23] <Wild_Man> Bashing-om, my thought is it is on the person that maintain the link to make sure it works on there end and not ours
[15:24] <Wild_Man> A lot of notes and some links are present in the template krytarik that is why it is there
[15:24] <Bashing-om> Wild_Man: Quite possiblly .. we "could" drop an email to the originator .
[15:25] <krytarik> Wild_Man: Ah yeah, they seem to be in the template too - so yes, those that aren't in the Google Doc too, please copy over.
[15:25] <Wild_Man> Bashing-om, do you have time to copy that link I posted above to the gdoc?
[15:25] <Bashing-om> Wild_Man: I can sure make the time .. is gdoc cleared for the next issue ?
[15:26] <Wild_Man> I have to get my morning meal and take my vitamins.
[15:26] <Wild_Man> Bashing-om, I do not think so I think it is left in place and we create a new one every time
[15:28] <Bashing-om> Wild_Man: I can move the insight link to gdoc and make a note to leave it .
[15:32] <Wild_Man> Bashing-om, there is a note in that section that says leave these links already
[15:37] <Bashing-om> Wild_Man: Done .. awaiting however to set the date for the security team .
[15:45] <Wild_Man> krytarik, I was going to move all the links to the end if the wiki last night I just got to tired by the time I got it all put there
[15:45] <Wild_Man> it is looking ggod
[15:45] <Wild_Man> good
[15:46] <Wild_Man> Bashing-om, you can leave the old dates for that link in place but you have to copy them from the wiki if the link is still in the wiki, it was October 2017
[15:47] <krytarik> Wild_Man: Oh btw, you did pretty good work there. :)
[15:48] <Bashing-om> Wild_Man: K .. but my idea was to make it obvious there was OLD info in place .
[15:48] <Wild_Man> krytarik, thanks! since it is a template does it still go live when it is saved or is there something else that has to be done to publish it?
[15:49] <Wild_Man> Bashing-om, okay
[15:49] <krytarik> Wild_Man: That is, I was impressed it was almost all done when got up and looked at it.  Oh, and wrt the 'Unconfirmed' bug stats, I just did what the comments in the template say - search for all bugs with the 'New' status.
[15:50] <Bashing-om> Wild_Man: Mind ya I do not know the re-new gdocs process if ya say but the date in .. I for sure will .
[15:51] <Wild_Man> krytarik, okay
[15:51] <krytarik> Wild_Man: You seem to be confusing the template with the actual issue right now - anyway, the issue wiki page is already live of course.
[15:51] <Wild_Man> krytarik, most of it was an way copy and paste from gdoc, I left that part to the last
[15:52] <Wild_Man> krytarik, I do not quite understand that
[15:52] <tsimonq2> This Week in Lubuntu Development #3 is coming out as soon as I'm done with it. Can I sneak it in? ;)
[15:52] <krytarik> Nope!
[15:52] <tsimonq2> :))
[15:52] <Wild_Man> krytarik, it is published?
[15:54] <krytarik> Wild_Man: Ok, well let's be even more clear and say 1.) the wiki page is already published, and just has to be linked in the various places, but 2.) it's not published to e.g. the Fridge either yet, similar to all the mail and social stuff.
[15:55] <Wild_Man> krytarik, right I just meant I can now post it to the forum?
[15:55] <krytarik> Yeah, I figure.
[15:56] <krytarik> Have got to start somewhere! :)
[15:56] <Wild_Man> I tsimonq2 is going to do the social media this time since I do not have access
[15:56] <Wild_Man> I/and
[15:57] <tsimonq2> Can y'all hold off for just like 30 minutes, unless you started the process already? ;)
[15:57] <Wild_Man> krytarik, to be honest linking it to other places I am not sure of those places
[15:58] <Wild_Man> I can wait
[15:58] <Wild_Man> not sure about krytarik it may be to late
[16:00] <tsimonq2> As long as you haven't done email yet, it's fine.
[16:00] <Wild_Man> no I do not think I have access to that, I my understanding you plan to do that this time
[16:01] <krytarik> Wild_Man: Well, it's barely evening here too. :)  And I still have got to go out even!  Also, all the stuff generated by the publishing script, plus the wiki pages mentioned here: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/EditingPolicies - could start with that.
[16:02] <krytarik> Also, I've just overhauled the update scripts too.. >_>
[16:06] <Wild_Man> krytarik, I have to leave soon as well, I have a couple of appointments
[16:07] <krytarik> Yes, since I'm just done with the above, I'm about to leave for a bit now too. :)
[16:52] <Wild_Man> tsimonq2, do you leave some of the letter out when you post to the forum because of the issue sometimes the posts are to long and can not be posted? I knew this could happen but I thought for the letter it was not an issue anymore
[16:54] <Wild_Man> tsimonq2, I think I figured it out
[16:54] <tsimonq2> OK
[16:54] <tsimonq2> whoops
[16:54] <tsimonq2> https://lubuntu.me/this-week-in-lubuntu-development-3/
[16:57] <krytarik> Somebody could already start over on the Google Doc with this.. :)
[16:58] <Wild_Man> tsimonq2, does not work in source mode either
[16:59] <Wild_Man> tsimonq2, suggestions? I posted to ask the admins but I am doubt they have an answer
[16:59] <tsimonq2> Wild_Man: I can take care of it if you give me a min.
[16:59] <krytarik> Wild_Man: You did run the publishing script on it yet however, didn't you?
[17:00] <Wild_Man> krytarik, yes I did
[17:00] <krytarik> And what error message do you get there now?
[17:01] <Wild_Man> it looks good but the forum has rules against posts that are to long
[17:01] <Wild_Man> the script is working perfect
[17:01] <Wild_Man> forum security software is the issue
[17:01] <krytarik> I thought you'd circumvent those by being a staff member though?
[17:02] <Wild_Man> no the rules apply to me too
[17:02] <Wild_Man> that is why we post the wireless script to pastebin most of the time
[17:03] <Wild_Man> I could leave out some links in the letter then it would probably post
[17:03] <Wild_Man> I am curious how tsimonq2 will get it done
[17:03] <Wild_Man> he has been able to do it in the past
[17:04] <krytarik> Wild_Man: You haven't dropped the Oct 2017 link from the meeting section yet though.
[17:04]  * tsimonq2 cracks knuckles
[17:04] <krytarik> And like I said, I'd drop the March ones too.
[17:04] <tsimonq2> What issue is this?
[17:04] <tsimonq2> (number)
[17:04] <krytarik> 523
[17:05] <Wild_Man> I thought Bashing-om did it ooops!
[17:05] <tsimonq2> kthx
[17:05] <Wild_Man> do I have time before tsimonq2 runs the script
[17:05] <Bashing-om> Wild_Man: Sorry . I be a gofer, you did not direct me to take that action :)
[17:06] <tsimonq2> Wild_Man: I can rerun it.
[17:06] <tsimonq2> Do you need me to after you make an edit?
[17:06] <tsimonq2> krytarik: Pushed a helpful commit. Git pull, pl0x.
[17:08] <Wild_Man> tsimonq2, give me a minute, after I remove the links it might be small enough to go on the forum
[17:09] <krytarik> tsimonq2: Hehe yeah, that's a good idea.. :D
[17:10] <krytarik> tsimonq2: Also just noticed in this context, we should make the 'code' page default to the Git repos.. :)
[17:11] <tsimonq2> krytarik: code> doeeeeeeeetttttttttttt :)
[17:11] <tsimonq2> Wild_Man: OK.
[17:11] <tsimonq2> Wild_Man: Actually... wait wat O_o
[17:11] <tsimonq2> Wild_Man: Can you not, please :)
[17:12] <Wild_Man> tsimonq2, sorry I just removed the one link already.
[17:12] <tsimonq2> I haven't regenerated it yet.
[17:12] <Wild_Man> krytarik, I did not see any links from March
[17:13] <krytarik> Wild_Man: Well, it's right there..
[17:13] <Wild_Man> tsimonq2, you can regenerate it now, I just removed one link but krytarik says there are links from March he may want to remove it
[17:14] <tsimonq2> OK
[17:14] <tsimonq2> gaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaah
[17:14] <tsimonq2> Your submission could not be processed because a security token was missing.
[17:14] <tsimonq2> If this occurred unexpectedly, please inform the administrator and describe the action you performed before you received this error. If possible, please include the error page URL plus the date and time the error occured.
[17:14] <Wild_Man> Like I said not eye glasses so I am having trouble seeing at the moment
[17:14] <tsimonq2> Tip : Please shorten long posts by using https://paste.ubuntu.com/ for terminal and log output and link to it in your posts.
[17:14] <tsimonq2> Ubuntu Forums
[17:14] <Wild_Man> I know but we do not do that for the letter do we?
[17:14] <krytarik> "Sorry about that, Ubuntu Forums." :D
[17:15] <Wild_Man> I know this was an issue for liz for a while
[17:16] <krytarik> Wild_Man: Tbh, if you can't see the two March links right above where you just removed the Oct 2017 one, I'm fine with that too..  At least they're from this year! :P
[17:16] <Wild_Man> krytarik, I totally did not see them
[17:17] <krytarik> And we didn't do any issue this year so far, soo.. :)
[17:19] <Wild_Man> tsimonq2, I know about pastebin but I did not think we do that for the letter when we post it
[17:20] <Wild_Man> I have looked for my glasses every where I can think of but they have been missing for six weeks
[17:22] <Wild_Man> krytarik, is there a way for the scripts that we use to get all those links to confirm they are working links otherwise they do not print them?
[17:23] <Bashing-om> Wild_Man: Behind the seat of the Pick-Up :)
[17:23] <krytarik> I'd just drop the 'updates' section with the billions of link and put a note there instead.
[17:23] <Wild_Man> Bashing-om, LOL
[17:24] <Wild_Man> krytarik, you mean to post it on the forum?
[17:25] <krytarik> Wild_Man: Well, I was going to mention earlier, at least the ones in the 'updates' section are pulled directly from the mailing list archive pages, so they should be fine.
[17:25] <krytarik> Yes, I mean to get over the security hurdle there - I mean they are a lot! :P
[17:26] <Bashing-om> Wild_Man: Sitting before this diaplay, I manage nicely to see with "readers" from the Dollar Store .
[17:26] <Wild_Man> Yes there is!
[17:26] <Bashing-om> display*
[17:27] <Wild_Man> I bought a pair from the store here but I guess I bought the wrong ones I have to hold the laptop in a certain place to see it so it is not feasible
[17:28] <Wild_Man> Bashing-om, I get free glasses from the VA so I just have to wait for my appointment
[17:30] <krytarik> Wild_Man: So one could instead just link there to e.g.: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue523#Updates_and_Security_for_14.04.2C_16.04.2C_and_17.10 - or even do that for the subsections.
[17:31] <Wild_Man> krytarik, we might have to do that, tsimonq2 is working on it so we will see what he comes up with
[17:34] <krytarik> Or only do it for the normal updates, and leave the security ones there.
[17:37] <Wild_Man> I have to go I will check on the progress when I get back
[18:39] <Bashing-om> I am starting to work up sources for next week's letter .
[21:51] <Wild_Man> krytarik, is there a way to make the link I add for to the forum go to Updates for 17.10 only and I can leave the rest of the links in ?
[21:55] <Wild_Man> What I tried failed
[21:55] <Wild_Man> Bashing-om, you here?
[21:57] <Bashing-om> Wild_Man: Here :)
[21:58] <Wild_Man> Bashing-om, Rick just replied to my pm he is going to help us starting about the 1st of May
[22:00] <Bashing-om> Wild_Man: Good man Rick .. Real glad he feels up to it . We need all the help we can get ,
[22:00] <Wild_Man> Bashing-om, I am glad too
[22:07] <krytarik> Wild_Man: Yes, like I suggested, keep the security updates as it is, but drop the direct links off all three sections for the normal updates, and replace them each with e.g.: "Please see: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue523#Ubuntu_14.04_Updates"
[22:16] <Wild_Man> krytarik, I did not really want to drop all of them they help to fill out the letter even though I think they are ugly, I did drop 17.10 and added the link you suggested that was the best I could, I think it is good enough, next time I do not think it will be as long since it will only be a week worth of updates
[22:16] <Wild_Man> I have it posted to the forum
[22:16] <Bashing-om> Look'n !!
[22:16] <Wild_Man> I have to fix something to eat real quick I missed my meal
[22:18] <Bashing-om> \o/
[22:22] <krytarik> Wild_Man: No, the way the scripts work anyway, is that they always pull the updates from the whole month so far - no idea if it was amended in the past issues though.  And you decided to just drop the updates on the most recent release, yes..? :D
[22:31] <Wild_Man> krytarik, I am trying to leave as much content as possible so it will have a fuller look if I remove all the update section it is going to look bare
[22:33] <Wild_Man> I am not really happy with either option
[22:39] <krytarik> Well yeah, thinking about it this way, I guess an empty section in the middle would look a bit odd indeed. :P
[22:41] <Wild_Man> No good option in my opinion
[22:52] <krytarik> Wild_Man: So do you want to do steps 20-24 on EditingPolicies with me in the meantime then? :)  I already looked at what that really means.
[22:52] <Wild_Man> krytarik, to do you have access to the mailing list?
[22:53] <Wild_Man> I am looking now
[22:53] <Wild_Man> I have the page open reviewing
[22:53] <krytarik> I'm not subscribed to either mailing list yet, no.
[22:53] <krytarik> Basically it refers all to: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter
[22:57] <Wild_Man> krytarik, yes I can do 20 and 21 or if you are busy I can do them all
[22:58] <krytarik> I'd like the second option. :D  I'm also taking dinner right now.
[22:58] <Wild_Man> krytarik, okay!


[05:48] <mborzecki> morning
[06:02] <mardy> mborzecki: hi!
[06:02] <mborzecki> mardy: hey
[06:50] <mborzecki> mvo: hey
[06:51] <mvo> good morning mborzecki
[06:53] <zyga-mbp> good morning
[06:58] <mvo> good morning zyga-mbp
[06:59] <mvo> fwiw, 10287 needs a second review
[07:03] <pstolowski> morning
[07:07] <mvo> good morning pstolowski !
[07:07] <zyga-mbp> pstolowski nice work!
[07:08] <zyga-mbp> oh wait, that was actually ian!
[07:08] <zyga-mbp> sorry ian and pawel
[07:08] <zyga-mbp> I'm a bit sleepy still
[07:08] <pstolowski> hey zyga-mbp  :)
[07:08] <mborzecki> mvo: reviewed, there seems to be some race in the test, google:centos-8-64:tests/main/snap-quota-groups failed and there's more than 1 task in the cgroup
[07:08] <mborzecki> pstolowski: zyga-mbp: hey
[07:10] <mvo> mborzecki: oh, interessting, thanks, looking
[07:21] <mvo> mborzecki: I think I do a followup, this is strange
[07:22] <mborzecki> mvo: that's fine, let's land it and we can tweak the test later
[07:22] <mborzecki> at least the whole feature will progress
[07:32] <mvo> 10329 should now also be unblocked
[07:51] <mborzecki> another one merged, we're down to 65 PRs
[08:12] <mborzecki> mvo: i've added some comments to https://github.com/snapcore/snapd/pull/10329 i can address those once i push out an rfc with serial & remodel, unless you want to have a go at it first
[08:13] <mvo> mborzecki: go wild, I'm looking at spread things right now
[08:24] <pedronis> mborzecki: does it mean the task count is always 0 on centos ?
[08:29] <mborzecki> pedronis: it's not, https://paste.ubuntu.com/p/R487f3RGRy/, disabling TasksAccounting makes system not create a group for the slice under the pids controller
[08:29] <mborzecki> pedronis: at least that what i determined through experimentation
[08:30] <mborzecki> pedronis: oh and when there's no cgroup, that's the current tasks count i get: TasksCurrent=18446744073709551615 so fun again
[08:31] <mborzecki> otoh, the value of MemoryCurrent is 0, so not sure what's really happening there
[08:32] <pedronis> mborzecki: I suspect we shoild just not support this there for now, it seems need a lot of attention and we don't really know what other bugs might hide there
[08:32] <mborzecki> it's only high when there's no memory controller at all, i.e. no memory limit set for given slice
[08:32] <mborzecki> where high == exabytes ian saw
[08:37] <pstolowski> mvo, pedronis there's an interesting old comment from zyga-mbp on a download gettng stuck bug here: https://bugs.launchpad.net/snapd/+bug/1891618/comments/2
[08:38] <pedronis> mborzecki: mvo: it sounds like we would need a lot spread tests to be sure things actually work
[08:39] <pedronis> mborzecki: mvo: anyway I don't think it makes sense to block the chain of PRs on this, it's probably best to not support these systems and reconsider later
[08:39] <mvo> pstolowski: that is interessting indeed
[08:39] <mvo> pedronis: +1 for not supporting these old systemds
[08:39] <zyga-mbp> mvo is it possible to move snapd to latest go?
[08:39] <mborzecki> pedronis: mvo: added one more comment with more explanation and a pastebin
[08:42] <mborzecki> pedronis: postponing support for older systems sounds like a good call, we can always revisit this once we've done more experiments
[08:43] <mborzecki> wondering if systemd somehow reports that memory controller is available at all
[08:43] <pedronis> zyga-mbp: we plan to move to 1.13 but not latest
[08:43] <mborzecki> zyga-mbp: do you recall anything like that in systemd? ^^
[08:43] <zyga-mbp> mborzecki like what exactly?
[08:44] <mborzecki> zyga-mbp: whether it's possible to find out if memory controller is even available
[08:44] <zyga-mbp> hmmm
[08:44] <zyga-mbp> isn't that visible in mountinfo in v1?
[08:45] <mborzecki> iirc it doesn't need to be mounted if memory accounting is disabled globally, and then you can always disable it in the kernel
[08:45] <zyga-mbp> (in v2 you have to consult what's enabled in the part you belong to
[08:45] <mborzecki> zyga-mbp: it is ;) but i'm more into poking systemd to know if that's doable
[08:45] <zyga-mbp> I see
[08:45] <zyga-mbp> I don't recall _but_ systemd has extensive dbus apis
[08:45] <zyga-mbp> perhaps it's somewhere there
[08:45] <zyga-mbp> I'd have to look
[08:46] <mborzecki> zyga-mbp: hm yeah, i should take a quick look
[08:47] <zyga-mbp> there is a property
[08:47] <zyga-mbp> MemoryAccounting
[08:47] <zyga-mbp> bool
[08:47] <zyga-mbp> on org.freedesktop.systemd1.Service
[08:47] <zyga-mbp> but I'd double check how it is implemented to know it is what you want
[08:50] <zyga-mbp> mborzecki https://github.com/systemd/systemd/blob/7dbc38db509f153256d3a3bfe6cbb26e2731c741/man/systemd.resource-control.xml#L269
[08:52] <mborzecki> zyga-mbp: mhm, thanks, looking at it
[10:21] <mardy> pstolowski: does this line look totally correct to you? https://github.com/snapcore/snapd/blob/master/overlord/servicestate/service_control_test.go#L295
[10:21] <mardy> shouldn't the action name be "test-snap.foo"?
[10:22] <pstolowski> looking
[10:31] <pstolowski> mardy: correct. it works because makeControlChange test helper creates apps out of it and current implementation of servicestate.Control() doesn't care about inst.Names anymore and uses apps. So it's confusing but test-only issue afaict
[10:32] <mardy> pstolowski: good! Then I guess it's fine if I make a small change to makeControlChange and to the tests, to use the fill names, right?
[10:32] <mardy> s/fill/full/
[10:33] <pstolowski> mardy: yes, sounds fine
[10:46] <mborzecki> pedronis: opened https://github.com/snapcore/snapd/pull/10330 with the check for serial assertion in remodel, need to sort out the spread tests still
[10:47] <pedronis> mborzecki: thx, I will look in a bit
[11:00] <mborzecki> thanks
[11:29] <mborzecki> hm i think i got the tests runnig now
[12:01] <pstolowski> mborzecki: do you have some time for a 2nd review of https://github.com/snapcore/snapd/pull/10261 ?
[12:02] <mborzecki> pstolowski: yes, i can take a look in a bit
[12:03] <pstolowski> thx
[12:36] <mborzecki> meh the remodel spread tests
[13:38] <mborzecki> pedronis: quick questions, even if i don't put my account & account key assertions in the seed, will they be automatically pulled from the store?
[13:39] <pedronis> mborzecki: they are needed for first seeding, prepare-image puts them there for you, but  I don't know what the test does
[13:39] <pedronis> mborzecki: without first seeding can't validate the model
[13:39] <mborzecki> pedronis: ok, i need to drop them there then
[13:40] <mborzecki> pedronis: the remodel tests, clean all of state from /var/lib/snapd and kick off first boot again
[13:45] <GunnarHj> pedronis: Hi Samuele! Apparmor fixes are needed to make fcitx5 (bug #1928360) and to some extent ibus (bug #1890905) work as expected in the snaps. (The fcitx5 task is higher priority.) Any chance you can take it on?
[13:46] <GunnarHj> https://launchpad.net/bugs/1928360
[13:46] <GunnarHj> https://launchpad.net/bugs/1890905
[13:53] <mardy> pedronis: I forgot to ask you to put https://github.com/snapcore/snapd/pull/10282 back into your review queue :-)
[13:55] <ijohnson> GunnarHj: you might want to also try pinging jamesh about such issues those bugs smell very desktopy to me
[13:56] <pedronis> GunnarHj: apparmor fixes in which sense? fixes to apparmor or to our apparmor rules?
[13:59] <GunnarHj> pedronis: The fcitx5 issue is about our apparmor rules, but the ibus one is about improving apparmor itself to start with.
[14:00] <GunnarHj> ijohnson: Thanks for the tip. Yeah, the bugs are indeed desktop'ish.
[14:08] <mborzecki> dumped the assertions into a single file, wondering if that will work
[14:15] <mborzecki> wooo, remodel-base workd
[15:03] <mborzecki> and pushed, remodel spread tests should work again
[15:10] <mvo> mborzecki: \o/
[15:50] <ijohnson> mvo: pedronis: can you land https://github.com/snapcore/snapd/pull/10099 ? the failure on debian-10 are unrelated
[15:55] <ijohnson> mvo: also I noticed you cherry picked https://github.com/snapcore/snapd/pull/10324 to release/2.51, so I added the cherry-picked label to that PR for you
[16:01] <pedronis> ijohnson: I think mvo beat me to it
[16:01] <ijohnson> yeah, no worries thanks for checking on it though
[16:09] <mvo> ijohnson: thanks! I keep forgetting this
[16:09] <ijohnson> it will become habit and save us much time in the future :-)
[16:16] <mvo> yeah, it's good!
[18:12] <ijohnson> pedronis: can you merge 10331 then ? I will open up our two alternatives after that so you can decide in the AM what direction we want to go
[18:12] <ogra> did anyone tak to iemeyer yet about mup ?
[18:13] <ogra> (i see it re-connecting in a 30sec loop in the old channel ... FWIW)
[18:14] <ijohnson> ogra: I thought mvo did already, I assume Gustavo's been a bit busy lately to move it over
[18:14] <pedronis> ijohnson: how can you open the alternatives if we don't have spread tests about current memory usage?
[18:14] <ogra> ijohnson, ah
[18:14] <pedronis> ijohnson: we probably want to fix the CLI first
[18:15] <ijohnson> pedronis: well now that the daemon is reporting memory usage, regardless of whether the CLI displays it, if there are problems the CLI dies
[18:15] <pedronis> ijohnson: yes, but not dying is not a criteria enough to decide on the workarounds
[18:17] <ijohnson> I mean yeah I guess if you want to do the CLI changes first then we can, but we can't really measure the memory usage specifically in the spread test
[18:17] <ijohnson> the spread test update I had in the CLI change PR just sees that there are numbers in the output, it doesn't actually confirm that the numbers make sense
[18:18] <ijohnson> it would be hard to check that the numbers make sense given that memory usage is not predictable in exact terms, I guess I could compare to make sure the number is under 100 megabytes or something obvious like that
[18:18] <pedronis> ijohnson: there's probably a min and max that can be applied
[18:19] <ijohnson> I guess in other words, I'm just not sure what the threshold is to decide on the workaround
[18:19] <ijohnson> alright I guess I can write a min/max detection snippet for the functional spread test
[18:22] <pedronis> ijohnson: do we have a test where we see processes hit the OOM ?
[18:22] <ijohnson> yes that's `tests/main/snap-quota-groups`
[18:22] <pedronis> I see one where they don't start, it that the OOM or something else?
[18:22] <ijohnson> yes that's checking the OOM
[18:22] <ijohnson> well indirectly checking that the service fails due to oom
[18:22] <ijohnson> we check that the service starts properly with a large limit, then we check that it doesn't start with a small limit
[18:26] <pedronis> it seems interfaces-packagekit-control has started failing consistently on arch
[18:27] <pedronis> ijohnson: I merged that PR, please consider my comment in the next, anyway I still think we want to fix the CLI first thing, before considering the corner case distros
[18:28] <ijohnson> pedronis: ok yes I have that change implemented in the CLI PR, which I will open shortly after adding this min / max logic to the snap-quota-groups spread test for that PR
[18:29] <ijohnson> pedronis: also yeah I saw that test has started to fail, I will try to have a look this afternoon, if I don't get to it, I left a comment about it with logs in the SU doc for someone to look at
[18:29] <pedronis> ijohnson: I suppose it might be something for Maciej to look at
[18:30] <ijohnson> yeah nothing obvious came up when I looked at it
[18:30] <ijohnson> to me at least
[19:04]  * cachio afk