[00:30] <maco> did jake get a ban yet?
[00:30] <maco> he's got one in #ubuntu-women for flooding and he's flooded in #kubuntu and #ubuntu. i saw floodbot hitting him in #ubuntu
[00:30] <Flannel> jake did in #u
[00:30] <maco> ok
[00:31] <Myrtti> he was kicked out of #u, but no ban
[00:31] <Flannel> yeah, he was.
[00:31] <Myrtti> might have been a mispaste though
[00:31] <Flannel> D-B-O hit him
[00:32] <maco> Myrtti: he was holding down a key on teh keyboard hitting enter after every few hundred char so that the screen filled with that letter for about 10 messages then he'd switch letters...
[00:32] <maco> thats what he did in k and u-w before
[00:32] <maco> and then today he was pasting > 50 char of different channels into each other
[00:32] <LjL> given the *number* of times he got muted/kicked...
[00:32] <maco> er, > 50 lines sorry
[00:34] <maco> alright well just wanted to check. buh bye
[00:40] <Myrtti> nini
[00:42]  * genii goes for maco's cookies
[00:42] <Pici> :o
[00:42] <genii> Pici:  :)
[01:09] <Am|Work> @login
[01:09] <Am|Work> yes I am
[01:09] <Am|Work> @login Amaranth
[01:09] <Am|Work> @btlogin
[01:09]  * genii sips
[01:10] <Am|Work> grr
[01:12] <genii> Am|Work: Strangely you're +o in -offtopic too
[01:16] <Pici> Am|Work: I see no ban for 'Traveler', but note, thats the freenode java applet
[01:20] <maco> jake #kubuntu
[01:21] <genii> Got it
[01:21] <maco> i see that
[01:22] <maco> he's ban evading :-/
[01:23] <genii> Bleh
[01:23] <maco><EMAIL_ADDRESS><-- before
[01:24] <genii> Guess we'll see if he re-appears after a while
[01:25] <Pici> I'm going to place a ban on freenode's java client in -offtopic.  Any complaints?
[01:25] <maco> he just came back into ubuntu-women again, but i caught him as soon as he joined. only got two messages in before the kick :)
[01:39] <LjL> ugh, /whowas jake almost flooded me
[01:40] <LjL> Pici: "Traveler" might not have bans on him, but i never thought he was up to any good
[01:41] <Pici> LjL: Agreed. If they want back in, they can use mibbit and be less anonymous.
[01:42] <LjL> Pici: how anonymous is the freenode client?
[01:43] <Pici> LjL: er, I for some reason mistook java with a real web gateway... no matter though,, we have bans placed for that in #ubuntu too
[01:45] <LjL> i'd make that not very permanent if at all possible, keep in mind they can join with the same addresses using real clients, and keep in mind /who *java*user*freenode* has a few people
[01:47] <Pici> LjL: The #ubuntu ban has been in place for as long as I've been an operator
[01:47] <maco> LjL: dont forget jake_ ....which, by the way, has another IP address on it with a later timestamp
[01:47] <LjL> Pici: it's been in place for as long as i've been an operator, too.
[01:47] <LjL> which might be part of why it's never been removed :)
[01:48] <LjL> still anyway, the #ubuntu-proxy-users topic among other things mentions we're less strict about #ubuntu-offtopic access
[01:57] <genii> Hm. /whois I_Hate_Freedom shows #houstonhackerspace . <notes the single # >
[01:57] <Pici> not all hackers are bad
[01:58] <genii> Pici: This is true. Real hackers just want to know how things work.
[02:10] <LjL> uh oh, "another" "anyone need some help" fellow
[02:11] <genii> LjL: I noticed he/she hasn't jumped in with any assistance yet though
[02:12] <LjL> genii: they might be doing it in PM, which is what the last one of these did.
[02:12] <genii> Ah, OK. Yeah that could be bad, if they are inept/malicious
[02:17] <genii> Jake again in #k
[02:17] <genii> Making threats, etc
[02:18] <genii> Do they ever actually come here?
[02:21] <genii> Perhaps I should have just devoiced and referred here but he was 1) making threat to DOS  2)ban evading
[02:22] <LjL> so perhaps not
[02:22] <genii> OK
[02:23] <LjL> hey, i'm no one. i'm just sayin'.
[02:26]  * genii prepares more coffee
[02:27] <maco> genii: in #ubuntu-women, i used *!?=jake@* ...maybe to be slightly more conservative than i am without just leaving it up to a router power cycle, you could<EMAIL_ADDRESS>[02:31] <genii> maco: Done now
[02:31] <maco> maybe that'll slow him down a bit
[02:32] <LjL> who wanna start a "static addresses for the people (and especially the trolls)" campaign?
[02:35] <genii> Where do I sign up?
[02:38] <LjL> genii: on this cheque. wait, it only looks like a cheque, of course
[02:38]  * genii signs his life away
[02:39] <LjL> genii: i'm afraid you've just renounced all ability to buy, possess or consume coffee.
[02:39] <genii> Uhoh
[02:40] <genii> I'll shrivel and die
[04:21]  * genii sneaks some coffee
[04:36] <screamsayonara> hello i was wondering if i can be unbanned from the ubuntu offtopic channel
[04:38] <Madpilot> @login
[04:38] <Madpilot> @btlogin
[04:39]  * genii prods Pici
[04:39] <Madpilot> screamsayonara, what were you banned for?
[04:40] <genii> Repeated swearing :)
[04:41] <screamsayonara> swearing....
[04:41] <screamsayonara> im a linguistics student ok, i like to push the boundaries
[04:42] <screamsayonara> it was a long time ago, im actually a really nice and intelligent girl.....
[04:42] <screamsayonara> i think i understand now that as much as i know about language, archaic attidues still prevail and im fine with that
[04:42] <screamsayonara> i wont swear :\
[04:43] <screamsayonara> and i <3 ubuntu
[04:46] <genii> screamsayonara: The op responsible currently isn't here, unfortunately
[04:49] <screamsayonara> ok thanks anyway...
[05:11] <genii> Well, it's a night for me. <brews a pot of coffee to keep the rest of the channel awake before /away >
[05:35]  * jdong toasts a shot of bourbon to #ubuntu-ops :). You guys are in my heart on my 21st b-day.
[06:42] <ikonia> jdong: best wishes your way, what a great age to be
[06:43] <jdong> ikonia: thanks man. I've heard every b-day from this point on is downhill :)
[06:43] <ikonia> jdong: nonsense
[06:43] <ikonia> it's all good
[06:43] <jdong> and rest assured I'm a good-behaved drunk person ;-)
[06:43] <jdong> ikonia: well I'll take your words and soar with em :)
[06:44] <ikonia> ha, I have /kick jdong aliased ready for typcial druken abuse ;)
[06:44] <ikonia> jdong: are you doing anything special for your big day ?
[06:46] <jdong> ikonia: I'm a tad antisocial. Nothing pleases me more than chatting with a handful of close friends and sipping a bit of whiskey.
[06:46] <ikonia> perfect
[06:46] <jdong> :) it is my idea of a perfect b-day.
[06:46] <Amaranth> wow, no one caught by the exploit attempts
[06:46] <jussi01> mrgh
[06:47] <Amaranth> oh, only on the second one
[06:47] <jussi01> mornings suck
[06:47] <jussi01> why am I awake....
[06:47] <ikonia> yes they do
[06:48] <tsimpson> hmm, where's LjL when you need him
[06:48] <ikonia> Amaranth: only caught after the warning
[06:48] <jussi01> ikonia: you are up early?
[06:48] <ikonia> every day
[06:49]  * Amaranth goes to bed
[06:49] <ikonia> time for work
[06:56] <Madpilot> dealt with
[06:57] <ikonia> !staff theunleet dcc'ing people in multiple channels #math #ubuntu ##windows ##linux
[06:57] <ikonia> !staff |theunleet dcc'ing people in multiple channels #math #ubuntu ##windows ##linux
[06:58] <tritium> Ah, so it was theunleet that took me out, eh?
[06:58] <tritium> Darn this borrowed router...
[06:58] <ikonia> tritium: really ?
[06:59] <nixternal> use port 8001 and you wont' have that problem
[06:59] <tritium> ikonia: yes, I'm now using 8001
[06:59] <nixternal> if only freenode could figure out ssl and offer that already
[06:59] <tritium> My DSL modem/router went out on my last week, so I'm borrowing a WRT54Gs, which evidently is exploitable.
[07:01] <Flannel> tritium: Odd, it shouldn't be.
[07:01] <Flannel> Must be different firmware than what I have.
[07:01] <tritium> Let me check...
[07:01] <tritium>  Firmware Version:  7.2.03 build 007, Nov. 8, 2007
[07:01] <tsimpson> odd, I have WRT54GC, which is not vulnerable
[07:02] <tritium> Perhaps I should update it for the person I'm borrowing it from.
[07:02] <tritium> Well, if it's not the Linksys router, it's the Actiontec DSL modem I'm also borrowing.
[07:03] <tsimpson> I have heard others say the WRT54G is vulnerable, but maybe the 'C' is magic :p
[07:07] <tritium> hmm, don't know
[07:07] <nixternal> 01:05:55 [     jun__] well first of all, i am just looking for mirc for linux, and then foun this konversation thing
[07:08] <nalioth> tritium: 8001 is your friend
[07:09] <tritium> nalioth: agreed
[08:28] <jussi01> popey: ping
[08:29] <jussi01> popey: can has powersave software? jussi01 at ubuntu.com :)
[08:56] <popey> sure jussi01
[08:57] <popey> done
[10:02] <ikonia> CaptainMorgan: hi, what's up?
[10:04] <CaptainMorgan> I'm not sure what's going on, but maybe it's solved now. I couldn't figure out why someone was forcing man pages down my throat -- and I when I agreed they were helpful, they still insisted I needed them... and then others gained up on the issue. Apparently, as it seems resolved, they were contacting the wrong person... still not sure how it happened
[10:05] <CaptainMorgan> I'll leave now though since it appears squashed, thanks.  --Just wanted to make someone aware of it and Flannel didin't appear to be currently active in the regular channel. Thanks again
[10:52] <elky> can someone please fix appeals to alias appeal?
[10:54] <elky> 'forget' still locks the factoid up, unfortunately
[11:06] <jussi01> !appeals
[11:06] <jussi01> !unforget appeals
[11:07] <jussi01> !no, appeals is <alias>appeal
[11:07] <jussi01> elky: ^^
[11:08] <elky> oh.
[11:08] <elky> stupid bot
[11:08] <jussi01> hehe
[11:29] <elky> response fired at flunkbomb
[11:30] <elky> if he comes to complain nobody has responded, tell him to check his inbox
[12:28] <Bacta> Hello
[12:31] <tsimpson> can we help you Bacta?
[12:31] <Bacta> I would like to get my ban dealt with
[12:32] <bazhang> @login
[12:32] <tsimpson> btlogin
[12:32] <tsimpson> @btlogin
[12:33] <Bacta> bt? ;)
[12:35] <elky> ban tracker.
[12:35] <Bacta> Not British Telecom, wayyy off
[12:37] <ikonia> hello
[12:37] <bazhang> hi
[12:37] <Bacta> Evening
[12:37] <ikonia> Bacta: what is your current status with regards to the ban appeal
[12:38] <Bacta> We went through this last night ikonia, I followed the first three steps namely contacting the banning op and discussing it in here
[12:38] <ikonia> Bacta: yes, you did say that, hence why I am asking how you've progressed it since then
[12:39] <Bacta> I do not wish to send an email to the listed addresses as it's likely a mailing list and I would prefer not to have my message put in front of however many hundreds are on it
[12:39] <ikonia> Bacta: it's a small group of the irc council
[12:39] <Bacta> No I have not heard anything
[12:39] <Bacta> How small?
[12:39] <ikonia> Bacta: it really doesn't matter how big/small
[12:39] <ikonia> Bacta: if there is something that private - its best not to say it
[12:39] <Bacta> It does as far as my privacy is concerned
[12:40] <ikonia> Bacta: if you are refering to your pm conversation with me - it will not effect it
[12:40] <Bacta> I also write my emails using my real name
[12:40] <jussi01> Bacta: 6 people. + the communty council (4?) - its a private list.
[12:41] <Bacta> Look I hope you can understand that I'm fairly active in the open source community where I am and I would prefer not to have people coming up to me personally, I know it sounds overly paranoid but maybe you might understand
[12:41] <ikonia> Bacta: no-one is coming up to you personally
[12:41] <ikonia> Bacta: if your active inthe open source community you should know the rules and not make the jokes about masturbating monkeys
[12:41] <ikonia> you knew it was wrong and you - continued to do it
[12:41] <ikonia> you've been banned for it at least twice
[12:42] <ikonia> so that's not really the best example of your activity in the open source or ubuntu community
[12:42] <Bacta> It was a dumb thing to say but "Masturbating Monkey" was a reference to something that came up on one of the security mailing lists I read
[12:42] <Bacta> It was in reference to Torvalds
[12:42] <ikonia> Bacta: you where banned once for it - you where told it was wrong - you did it again
[12:42] <ikonia> so it wasn't dumb - it was intentional
[12:42] <ikonia> the quicker you are honest about it - the easier we can progress
[12:43] <Bacta> Of course it was intentional
[12:43] <ikonia> Bacta: right - so you knew it was wrong and did it again
[12:43] <ikonia> why ?
[12:43] <Bacta> Why wouldn't it have been? I don't just say things like that by accident, there are obvious thought processes around it
[12:43] <Bacta> Because it was a joke but perhaps I misjudged the audience
[12:43] <ikonia> Bacta: ok - so you thought about it, knew it was wrong and still did it
[12:43] <ikonia> Bacta: you where told the first time you said it, it's not appropriate don't do it
[12:43] <ikonia> so again - why did you do it a second time
[12:43] <Bacta> I do remember saying it once before but it would've been quite some time ago
[12:44] <elky> Bacta, our channels are not for trolling, and that is all you ever do in them. Why on earth would we want to let you back in?
[12:44] <ikonia> Bacta: it doesn't matter how long ago it was - you where TOLD don't do it again, you thought about it and did it again
[12:44] <Bacta> elky: I've been in there a number of times to receive help and I have helped a number of people in there as well
[12:44] <ikonia> Bacta: how do I know if I remove the ban you don't do it again
[12:44] <Bacta> I may not know much about Ubuntu but I'm quite happy with the advice I have given people in there
[12:45] <Bacta> You don't, it's a risk
[12:45] <Bacta> All I can say is I'll try my best
[12:45] <ikonia> Bacta: ok it's a risk I'm not prepared to take at this time
[12:45] <elky> and maybe it's a risk we do not want to take.
[12:45] <ikonia> Bacta: so I suggest you come back in a months time when you've had time to think about what you did and how best to control your self
[12:46] <Bacta> Why would I take time out of my day to "think about what I've done"? It was a dumb thing to say, I'm sorry I said it but in the grand scheme of things it means practically nothing
[12:46] <ikonia> Bacta: because I don't want to risk letting you do it again
[12:46] <Bacta> All I can say is I'll take a bit more care in how I conduct myself in future
[12:47] <Bacta> And I think you have far more serious threats to the channel than the occasional bad joke
[12:47] <ikonia> Bacta: because you've done this before and I don't want to risk allowing you back in the channel to do it again
[12:47] <ikonia> Bacta: it's offensive and you've proved you can't control yourself at this time
[12:47] <ikonia> Bacta: so as I've said, come back in a month and we can re-asses it then
[12:50] <ikonia> Bacta: do understand ?
[12:50] <Bacta> Perfectly but I do regret now being so honest with you
[12:50] <ikonia> ?
[12:51] <ikonia> I don't think there is anything you've said that we didn't already know, so you've got nothing to regret
[12:51] <Bacta> I could've come in here and got down on my hands and knees screaming to God how sorry I was
[12:51] <ikonia> Bacta: yeah, that wouldn't have changed anything
[12:51] <ikonia> Bacta: so if you'd like to come back in a month we'll re-asses with you then,
[12:51] <Bacta> My past experience elsewhere has shown otherwise
[12:51] <ikonia> Bacta: well, that wouldn't have made a difference to me
[12:51] <ikonia> Bacta: so lets leave it there and speak again in a month
[12:52] <Bacta> You see we can't say that
[12:52] <ikonia> ?
[12:52] <Bacta> It's done, if I had said things differently there might have been a different result
[12:53] <ikonia> Bacta: I don't want to debate if's/buts - so lets talk again in a month
[12:53] <Bacta> One more thing
[12:53] <ikonia> yes ?
[12:53] <Bacta> where would be my first port of call to get my DVD playback issue sorted?
[12:54] <ikonia> this is not a support channel
[12:54] <ikonia> sorry
[12:54] <ikonia> Bacta: lets speak again in a month
[12:54] <bazhang> serial, iirc
[12:54] <elky> very.
[12:54] <ikonia> @mark #ubuntu-ops bacta review ban on 14/06/09
[12:55] <Pici> Oh, yes.
[12:55] <bazhang> seem to remember him from #freenode
[12:55] <Pici> Indeed. And #defocus
[12:55] <elky> i remember him from the Linuxchix server.
[12:55] <Pici> Ugh.
[12:55] <bazhang> wow
[12:56] <ikonia> he'll be back before a month
[12:57] <ikonia> I'm a little dissapointed freenode didn't remove his cloak for his ban evasion antics, as he seems to value his privicy
[12:57] <ikonia> actions = consiquences
[12:58] <bazhang> in -ot and #k
[12:59] <jussi01> Im watching #k...
[13:01] <ikonia> I'm sure he said he was using ubuntu when he was in #ubuntu
[13:01] <elky> ikonia, i'm pretty sure i dont trust what he says anywhere.
[13:02] <ikonia> oh I know, just wondered if I was genuinly wrong
[13:02] <elky> not worth trying to keep up with that kind of stuff
[13:02] <ikonia> no, just wondered
[13:03]  * Hobbsee waves and issues hugs
[13:03] <ikonia> howdy Hobbsee
[13:03] <bazhang> Hobbsee, !!
[13:03] <elky> Hobbsee, spotted bacta i take it?
[13:03] <Hobbsee> heya :)
[13:03] <bazhang> hehe
[13:03] <Hobbsee> elky: hey, now there's a thought!
[13:04] <Hobbsee> elky: in truth, no.  But that could be extra popcorn material
[13:04]  * Hobbsee is watching what's going on, and is avoiding her assignment
[13:04] <Pici> :)
[13:05] <elky> hehe
[13:12] <ikonia> spoke to hime
[13:12] <ikonia> ime
[13:12] <ikonia> him even
[13:15] <ikonia> can't say he wasn't warning
[13:20] <bazhang> trolling continues in #k I see
[13:24] <ikonia> well, he's just shown it's a hardware issue - so nothing to do with #kubuntu
[13:24] <ikonia> problem solved
[13:33] <Hobbsee> elky:
[13:33] <jussi01> and that was that.
[13:33] <Hobbsee> elky: got some popcorn ready?
[13:33]  * Pici will stay quiet, too many chefs, etc
[13:34] <Pici> or was it chiefs?
[13:34] <jussi01> in pm with bacta
[13:35]  * Pici sighs at -ot
[13:35] <Pici> Hobbsee :P
[13:35] <Hobbsee> Pici: <evil grin>
[13:35]  * ikonia takes his chef's hat off and hands it to pip
[13:35] <ikonia> pici even
[13:38] <jussi01> RE: bacta in #k
[13:38] <jussi01> [15:37:41] <jussi01> Ok, Im going to give you a 24 hour ban, thank you for your immediate apology. you can try join the channel again 24 hours from now.
[13:38] <Pici> I turn away for real work for a few minutes and the conversation turns to pedophiles
[13:38] <jussi01> JUST FYI
[13:39] <ikonia> jussi01: is a troll, using caps now
[13:39] <Pici> jussi01: thanks
[13:39] <jussi01> ikonia: shush
[13:39] <jussi01> so anyone feel free to remove his #kubuntu ban in 24 hours if I forget.
[13:40]  * ikonia makes a note to forget
[13:40] <ikonia> I am kidding of course
[13:41] <jussi01> oh dear
[13:41] <elky> my mum is a dork. she seems to have decided 'lok' is an acceptable way to say 'lol, ok.'
[13:41] <jussi01> elky: all yours in -ot
[13:42] <jussi01> you know its bad when the ot regs say to change the topic....
[13:43] <ikonia> elky: she is l33t
[13:44] <elky> ikonia, dont make me stab you.
[13:45] <ikonia> ok
[13:58] <topyli> lok.
[13:58] <ikonia> topyli: genius
[14:09] <TheFunkbomb> You guys gonna release my ban today?
[14:10] <bazhang> TheFunkbomb, the appeals process is still under way.
[14:10] <TheFunkbomb> I already got my response
[14:10] <TheFunkbomb> Who is Melissa?
[14:11] <TheFunkbomb> actually, scratch that question.  I don't care.
[14:11] <TheFunkbomb> Instead, answer this one.  Why do I have to continue to apologize?
[14:11] <bazhang> TheFunkbomb, coming here repeatedly wont help your case.
[14:11] <TheFunkbomb> but I get better answers here.
[14:13] <TheFunkbomb> I have already apologized for breaking the CoC.  I have apologized for the misunderstanding of the whole ballbusting thing.  What else is there?
[14:13] <Hobbsee> is anyone actually asking you to apologise here?
[14:14] <TheFunkbomb> Yes, that would be the case.
[14:14] <TheFunkbomb> I was told my apology was not sincere enough.
[14:14] <TheFunkbomb> or that my apology was not for what I did.
[14:15] <bazhang> TheFunkbomb, you are on step 4 now, correct?
[14:15] <TheFunkbomb> ??
[14:16] <bazhang> TheFunkbomb, step 4 of the appeals process
[14:16] <TheFunkbomb> I have no idea what that is.
[14:16] <bazhang> !appeal
[14:16] <bazhang> TheFunkbomb, check the above link then
[14:17] <TheFunkbomb> Pretty sure step 4 is over.
[14:17] <bazhang> a single response?
[14:18] <TheFunkbomb> yeah
[14:18] <bazhang> the irc council is more than a single person. give it some time.
[14:18] <ikonia> if I can step in
[14:18] <TheFunkbomb> how many responses should I expect?
[14:18] <ikonia> elky: has responded on behalf of the council
[14:19] <bazhang> aha, then step 5
[14:19] <TheFunkbomb> and who deals with step 5?
[14:19] <ikonia> TheFunkbomb: elky is Mellisa
[14:19] <TheFunkbomb> ikonia, I don't really want to hear from you.
[14:19] <bazhang> the list linked on that page
[14:19] <Pici> This doesn't need to go past the IRCC.....
[14:19] <bazhang> okay sorry Pici
[14:19] <ikonia> again the attitude
[14:20] <TheFunkbomb> You accused me of ban evasion
[14:20] <Pici> TheFunkbomb: Did you read the reply that the Melissa sent to you?
[14:20] <TheFunkbomb> Pici, I did.  I apologized.  I don't know what other kind of apology you want.
[14:20] <Hobbsee> TheFunkbomb: if you are in consultation with the irc council, and dealing with this through that avenue, nothing you say or do here is going to make any difference, in a good way.  You may as well sit back, and continue to take anything else up with them.
[14:21] <TheFunkbomb> It's the same people!
[14:21] <Hobbsee> actually, it's a subset of those here
[14:21] <Pici> TheFunkbomb: The people in this channel are not all privy to the list that you sent your message to, they do not know what was said there.
[14:22] <Hobbsee> it's the equivalent of me calling Pici on a mobile phone, and him replying back by a loudspeaker.
[14:22] <Hobbsee> so, might not be quite what you want
[14:22] <TheFunkbomb> So, if that same subset didn't give a damn here, then why would they give a damn through the email?
[14:23] <Hobbsee> TheFunkbomb: likely because email is asynchronous, and it's not very late night / early morning for most of them.
[14:23] <Hobbsee> when they must reply
[14:23] <Pici> TheFunkbomb: I don't believe that you spoke to anyone here that is on the IRCC in this channel for any length of time.
[14:23] <Pici> Hobbsee: A reply was already sent actually.
[14:24] <TheFunkbomb> You know what?  I don't really care anymore.  I apologized.
[14:24] <Hobbsee> Pici: I meant right now, but yes
[14:24] <TheFunkbomb> You guys have a spectacular day.
[14:25] <Pici> Well then.
[14:25] <jussi01> A spectacular day? nah...
[14:27] <elky> elky was putting soup into the slow cooker
[14:27] <Pici> @mark TheFunkbomb
[14:27] <Pici> @login
[14:27] <Pici> @mark TheFunkbomb
[14:27] <jussi01> sigh... either the listed md5 sums are wrong, or I just cant get a propper download... *grumble*
[14:29] <jpds> jussi01: Or the image is wrong on the server?
[14:30] <Hobbsee> jussi01: which image?
[14:30] <elky> gah, someone needs to bust open another spam racket so i can get slow spam days again
[14:34] <jussi01> Hobbsee: the unr one
[14:37] <Hobbsee> jussi01: known bug
[14:37]  * genii makes more coffee
[14:37] <Hobbsee> jussi01: it's a truncated file names problem, pretty much
[14:37] <jussi01> Hobbsee: any idea of the actual md5 sum?
[14:38] <Hobbsee> jussi01: not offhand.  There's a bug about it somewhere
[14:38]  * Hobbsee sees it mentioend on irc every few days
[14:38] <jussi01> this is what ive got
[14:38] <jussi01> jussi@piru:~$ md5sum ubuntu-9.04-netbook-remix-i386.img
[14:38] <jussi01> ab19c88f7cf8d1d2b3de1aa26fd1c29b  ubuntu-9.04-netbook-remix-i386.img
[14:39] <jussi01> used the torrent for download, so hoping its correct
[14:52] <jussi01> oh ffs
[14:52] <jussi01> it must be wrong md5...
[14:52] <jussi01> I get a boot error
[15:00] <genii> "unsatisfying results" seems to be going around
[15:02] <jussi01> hehe
[15:02] <jussi01> genii: feel like handling that? Ive a splitting headache...
[15:03] <genii> jussi01: I'm not up on flash in 9.04 yet :(
[15:36] <bazhang> night all
[15:37] <LjL> bye
[15:43] <jussi01> yay, finally it worked!!
[16:05] <genii> Work, /away probably 20-25 minutes
[16:27] <Myrtti> anything intresting going on?
[16:28] <jussi01> doesn anyone know if there is a UNR channel?
[16:29] <Myrtti> msg alis search unr ?
[16:31]  * Myrtti pokes popey
[16:31]  * popey pokes Myrtti back
[16:32] <Myrtti> I can haz powersavings plz?
[16:33] <popey> email addy?
[16:34] <Myrtti> me myself and I, that is myrtti meow ubuntu.com
[16:35] <popey> s/meow/@ ?
[16:35] <popey> your l33t code fools me
[16:37] <jpds> jussi01: #ubuntu-mobile ?
[16:38] <Myrtti> popey, yes plz
[16:38] <popey> done
[16:54] <mneptok> do you meow know how meow fast you were meow driving meow?
[17:08] <Myrtti> mrhgmhm. I haz a headache
[17:10] <genii> meow?
[18:05] <genii> I'll be /away again about 20-30 minutes
[18:46] <Pici> ugh
[19:23] <Seeker`> Pici: why do you keep on muting people then just leaving them like that?
[19:24] <Seeker`> (I say "keep on", I've seen at least two like that)
[19:27] <Pici> Seeker`: Because I keep on forgetting about them :/
[19:29] <Seeker`> -21:28:36- ~s~ 233 - #ubuntu: ban<EMAIL_ADDRESS>by Seeker`, 76501 secs ago
[19:29] <Seeker`> Pici: That is one of yours too; I removed it by mistake
[19:37] <Pici> Seeker`: Thats fine
[19:47] <Myrtti> http://paste.ubuntu.com
[19:47] <Myrtti> bollocks
[19:48]  * Myrtti tries again
[19:48] <Seeker`> hi Myrtti
[19:50] <Myrtti> http://paste.ubuntu.com
[19:50] <Myrtti> *sigh*
[19:50] <Myrtti> oh, right
[19:50] <Myrtti> http://paste.ubuntu.com/171846/
[19:51] <Myrtti> there we go
[19:52] <Seeker`> oooh, shiny
[19:52] <Seeker`> @login
[19:57] <Seeker`> @bansearch <IP_ADDRESS>
[19:58] <Seeker`> @bansearch<EMAIL_ADDRESS>[19:58] <Seeker`> that is a complete hostmask!
[19:58] <ikonia> Myrtti: a million chocolates for your scripting of that
[19:58] <ikonia> nice job
[19:59] <Seeker`> one of my bans isn't in the bantracker :/
[20:02] <Myrtti> ikonia: my aim is to make a script that will put all that into an html that would make the banmasks clickable searches to bantracker
[20:06] <ikonia> I think sebsebseb is recruiting in #ubuntu again
[20:10] <ikonia> ok - he has been recruiting again, I've seen him do it a few days ago and made it clear he needed to stop, now he's doing it again, what is the correct course of action to avoid an "emma" situation
[20:11] <ikonia> Pici: jussi01 elky ?
[20:13] <jussi01> ikonia: at very least ask him in for a chat.
[20:13] <ikonia> already done so yesterday
[20:13] <jussi01> and again...
[20:13] <ikonia> chat again ?
[20:14] <ikonia> asked him to join then
[20:15] <jussi01> ikonia: you got access to skype for a min?
[20:15] <ikonia> nothing works on 9.04 on my laptop, I've got access to nothing, I'm burning an 8.10 cd as we speak
[20:15] <ikonia> I've got no mic, no web cam,
[20:16] <sebsebseb> ok
[20:16] <ikonia> hi sebsebseb thanks for joining
[20:16] <jussi01> Hi sebsebseb
[20:16] <sebsebseb> hi
[20:16] <jussi01> sebsebseb: I ve seen you helping a lot in #ubuntu and we thank you for that
[20:17] <jussi01> sebsebseb: However, Im a little concerned. you seem to have started your own channel and are inviting people into it?
[20:17] <sebsebseb> not randomly
[20:18] <jussi01> sebsebseb: this is not something that is allowed in #ubuntu, to invite people to another channel. please dont do it.
[20:19] <sebsebseb> so if someone  starts to pm for help,  and can't really help them in pm,   but  there's another person in another channel that can,   get that person to join #ubuntu ?   and if they don't,  tell the person im pm to try #ubuntu again?
[20:20] <ikonia> sebsebseb: people seem to PM you a lot and you don't seem to be able to help them a lot in PM and there is always someone in your channel that can help
[20:20] <ikonia> considering there are only 2 regulars in your channel I find that unusual
[20:20] <sebsebseb> ikonia: yeah indeed, to small for there always to be someone
[20:21] <ikonia> sebsebseb: so if there isnt someone - why do you point them to your channel for support
[20:21] <jussi01> correct. Or redirect them to a loco channel that suits their locality, or to a specific channel for their issue, for example a quassel issue to #quassel
[20:21] <sebsebseb> ikonia: ,because there was that time
[20:22] <jussi01> sebsebseb: the problem is, we need to redirect people only to official channels - so perhaps join your loco and help there also. If you cant help someone, leave it and try to help who you can.
[20:23] <sebsebseb> jussi01: why is it so important to only redirect to offical channels?   ,because they are monitored properly?
[20:24] <jussi01> sebsebseb: correct.
[20:25] <sebsebseb> ikonia: were you really only stopping by?
[20:25] <ikonia> sebsebseb: yes
[20:25] <sebsebseb> oh
[20:27] <sebsebseb> ikonia: ok  thanks
[20:28] <jussi01> sebsebseb: so is that all clear now?
[20:29] <sebsebseb> jussi01: yep
[20:30] <jussi01> sebsebseb: ok, thanks for understanding and thanks again for helping out. have a nice day :)
[20:32] <jussi01> sebsebseb: Ive nothing more for you at this time, so if you would, Id ask you to part.
[20:32] <sebsebseb> ok
[20:33] <sebsebseb> bye
[20:33] <jussi01> bye
[20:33] <jussi01> Well that went well. lets hope it has the desired effect.
[20:34] <ikonia> almost word for word the conversation I had with him yesterday
[20:34] <genii> Heh
[20:36] <LjL> have to say it's relatively common for people to say "join #blihblah so i'll help you there" when #ubuntu is busy
[20:36] <ikonia> LjL: not for seb it's not
[20:36] <LjL> although it's usually random channels likely created by people who aren't quite familiar with privmsg
[20:36] <ikonia> seb was activly messaging people for help to join his channel
[21:33] <popey> i think he _means_ well
[21:33] <popey> just using a slightly misguided approach
[21:34] <jussi01> popey: exactly my thoughts
[21:35]  * genii throws sebsebseb and eagles0513875 into a cage match with each other!
[21:36] <genii> Sorry, couldn't resist there....
[21:39] <LjL> d3adslave is d3adlin
[21:42] <genii> No egyhptian loco channel, I see
[21:42] <genii> *egyptian
[21:43] <LjL> genii: yes there is
[21:44] <LjL> although for support, -arabic will do fine i'm sure
[21:44] <genii> OK
[22:09] <jussi01> was the funkbomb allowed into #ubuntu ?
[22:11] <Nafallo> was he ever banned from #ubuntu?
[22:11]  * Nafallo thought it was only -ot
[22:11] <jussi01> @bansearch  TheFunkbomb
[22:11] <jussi01> Nafallo: you are correct it seems
[22:12] <jussi01> Just checking
[22:23] <elky> ban evading?
[22:24] <jussi01> elky: nah, no ban it seems
[22:25] <elky> ah. misread. my router got disconnected again by something
[22:38] <elky> gotta go to work now, watch the loonies in -ot please
[22:48] <jussi01> Hiya maco
[22:48] <maco> oops
[22:48] <jussi01> hehe
[23:00] <jussi01> ooh, tuhina has woken up :D
[23:05] <Nafallo> sounds Finnish :-)
[23:07] <mneptok> it's a small Brazilian tuna
[23:07] <jussi01> Nafallo: tuhina is my hedgehog...
[23:07] <jussi01> mneptok: OUT!
[23:07] <mneptok> jussi01: SNUFFLER!
[23:07]  * mneptok snuffles
[23:07]  * jussi01 should go to bed... its 1am...
[23:08] <Nafallo> jussi01: that was... unexpected.
[23:08]  * Nafallo would totally have painted it blue and called it Sonic
[23:08] <jussi01> Nafallo: meh... old joke
[23:09] <Nafallo> that's because it is an old game :-)
[23:09]  * jussi01 ->> bed'
[23:37] <BettyFord_failed> hello
[23:37] <Seeker`> how can we help you?
[23:44] <BettyFord_failed> im drunk
[23:46] <Pici> !moo
[23:49] <Pici> BettyFord_failed: Then may I suggest that you part this channel, as you've been fowarded here from #ubuntu.


[20:03] <rpiNEEDSHELP> Help
[20:03] <rpiNEEDSHELP> !ops
[20:04] <rpiNEEDSHELP> !bot
[20:04] <rpiNEEDSHELP> !list
[20:12] <rpihelpme> help 4 real
[20:12] <rpihelpme> I’m getting mad
[20:13] <rpihelpme> popey.
[20:13] <rpihelpme> this isn’t a prank
[20:13] <rpihelpme> i won’t do !ops anymore
[20:13] <popey> This isn't how to get support
[20:13] <popey> You are abusing people
[20:13] <rpihelpme> am I?
[20:14] <popey> We are volunteer community members
[20:14] <rpihelpme> almost every1 else is afk
[20:14] <popey> Don't demand out attention
[20:14] <popey> Technically so am I. I'm sat on a beach!
[20:14] <rpihelpme> i need help ASAP tho
[20:14] <rpihelpme> oh sorry
[20:15] <rpihelpme> im so sorry!
[20:15] <popey> And having to deal with people pinging me on IRC
[20:15] <rpihelpme> oh
[20:15] <popey> Rather than spend time with my family
[20:15] <rpihelpme> im sad now
[20:15] <popey> I did tell you many times to stop
[20:15] <rpihelpme> ok
[20:15] <rpihelpme> i wont
[20:15] <rpihelpme> i just needed help
[20:16] <popey> If you want immediate support on demand, frankly pay for it.
[20:16] <popey> We are volunteering our time
[20:16] <popey> We don't owe you support
[20:16] <rpihelpme> I’m so soory
[20:16] <rpihelpme> i didn’t know u were volunteers
[20:17] <rpihelpme> can u link me to forums tho?
[20:17] <popey> I recommend askubuntu.com
[20:17] <rpihelpme> Ok
[20:17] <popey> Or ubuntuforums.org
[20:17] <rpihelpme> is there an arm forum?
[20:18] <popey> I don't know
[20:18] <rpihelpme> ok ty for ur time byebye


[06:29] <lordievader> Good morning.
[07:28] <Novice201y> Hello. Where is "update button" in Utopic "about computer"?
[10:18] <nrbrtx> Dear all! Today I have installed Ubuntu Utopic from beta2 CD and discovered that many bugs are still not fixed. These bugs are: 1245137, 1242572, 1263228, 1244090, 1270574, 1270579, 1280759.
[10:32] <bipul> nrbrtx: are you able to install ubuntu 14.10?
[10:32] <bipul> bug 1245137
, yes, I'm writing from 14.10.
[10:36] <bipul> nrbrtx: I am unable to install Ubuntu 14.10 inside my virtualbox
[10:36] <bipul> bug 1374754
, I installed on physical hardware (VAIO F13Z1R on external eSATA HDD).
[10:38] <bipul> humm...
[10:38] <bipul> nrbrtx: Try to install virtualbox on your Ubuntu 14.10 and  see are you able to install ubuntu 14.10 inside virtualbox or not.
[10:39] <nrbrtx> bipul, what virtualbox version do you use, from which repo?
[10:39] <BluesKaj> Hiyas all
[10:39] <lordievader> I've heard Virtualbox is broken. Try kvm ;)
[10:39] <bipul> nrbrtx:  Virtualbox 4.3.10
[10:41] <nrbrtx> bipul, on which system you try to install virtualbox?
[10:42] <bipul> Kubuntu14.04
[10:42] <nrbrtx> bipul, I have 14.04 too.
[10:43] <bipul> Does it works fine from your side? I mean are you able to install ubuntu 14.10 on virtualbox?
[10:44] <nrbrtx> bipul, I have just installed vbox 4.3.16 on Ubuntu 14.10, now creating VDI.
[10:45] <nrbrtx> bipul, vbox from https://www.virtualbox.org/wiki/Linux_Downloads
[10:45] <bipul> oh ok ,
[10:48] <nrbrtx> bipul: on which CPU you try to install vbox? Is VMx/VT-x enabled in BIOS (lscpu | grep Virtualization)?
[10:49] <bipul> Yes, everythings is beiing enabled.
[10:50] <bipul> lscpu | grep Virtualization
[10:50] <bipul> Virtualization:        AMD-V
[10:51] <nrbrtx> bipul: I started Ubuntu 14.10 beta2 livecd in vbox, enable 2D and 3D acceleration with 128 Mb video RAM.
[10:52] <bipul> nrbrtx: is it working?
[10:52] <bipul> Yes i can boot with live cd the problem is i am not able to install it.
[10:52] <nrbrtx> bipul, yes I'm seeing "Preparing to install Ubuntu" graphical CD.
[10:53] <nrbrtx> bipul: now I'm pressing "Install now"
[10:54] <nrbrtx> bipul: seeing "Copying files"
[10:55] <bipul> ok let see
[11:00] <nrbrtx> bipul: now it downloads software (still in installer).
[11:01] <bipul> ok
[11:03] <nrbrtx> bipul: now it suggests to reboot
[11:03] <bipul> let see
[11:04] <bipul> Is it working ??
[11:04] <nrbrtx> bipul: purple background and some vhdd actitivity
[11:05] <bipul> humm
[11:05] <nrbrtx> bipul: I rebooted it and pressed Escape in GRUB
[11:05] <bipul> why?
[11:05] <nrbrtx> bipul: it took too long
[11:05] <bipul> yes
[11:06] <nrbrtx> bipul: now rebooted in rescue mode
[11:06] <bipul> oh ok
[11:06] <nrbrtx> bipul: pressed resume in it, got normal greeter
[11:07] <nrbrtx> bipul: unity loaded
[11:08] <bipul> SO it's workign?
[11:08] <bipul> working!!
[11:08] <nrbrtx> bipul: working only from rescue mode
[11:09] <bipul> ok
[11:10] <nrbrtx> bipul: rebooted it with "verbose noplymouth"
[11:12] <nrbrtx> bipul: could you please try to boot your vbox with Ubuntu 14.10 and press Esc in GRUB?
[11:12] <nrbrtx> bipul: if I press Escape in GRUB and select first row, it boots normally.
[11:13] <bipul> ok let me reinstall it
[11:13] <nrbrtx> bipul: ok
[11:16] <nrbrtx> bipul: what is interesting - it seems that it boots normally, but does not show Unity greeter by default.
[11:16] <bipul> yes.
[11:17] <nrbrtx> bipul: I logged to in from console and now installing latest updates - 'apt-get update && apt-get upgrade'.
[11:23] <nrbrtx> bipul: after installing of all updates still no GUI login.
[11:26] <nrbrtx> bipul: after manually restart of lightdm (sudo service lightdm restart) it boots to GUI at login.
[11:35] <bipul> humm
[11:35] <nrbrtx> bipul: I reporting bug about our issue.
[11:42] <bipul> show me
[12:01] <nrbrtx> bug 1376232
[12:15] <nrbrtx> bipul: any news?
[12:19] <nrbrtx> bug 1376232
[12:22] <bipul> The same problem i have mentioned in my bug
[12:22] <nrbrtx> bipul: where is your bug, so I created a duplicate?
[12:23] <bipul> nrbrtx: Not exactly, But i never loged in grub menue
[12:23] <bipul> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1374754
[12:24] <bipul> 1374754
[12:25] <nrbrtx> bipul: it is great, that your bug is different
[12:25] <nrbrtx> bipul: I booted to Ubuntu 14.04.1 and will try to repeat installation on it.
[12:25] <bipul> what great, i was trying to install ubuntu in a normal way, and i was unable to install it
[12:25] <elfy> but are they dupes - there have been a couple of related bugs
[12:27] <elfy> bug 1375805
[12:28] <elfy> and bug 1371651
[12:29] <elfy> if you don;t get any plymouth crashes then it's likely to be the first of the 2
[12:29] <nrbrtx> dear elfy, where you was before? :)
[12:29] <elfy> working ;)
[12:29] <nrbrtx> elfy: nice
[12:30] <elfy> you can confirm if it's the first bug - there is a .conf file in post 6 - create that and then reboot
[12:30] <elfy> if it is the same bug - please mark your one as a dupe of 1375805 :)
[12:31] <nrbrtx> elfy: you can use my description as well.
[12:32] <elfy> wut?
[12:32] <nrbrtx> elfy: so I agree that mine should be set as duplicate of yours, but you can update the description using mine :)
[12:33] <elfy> I'm not here really - get a short lunch break then I'm off again
[12:33] <nrbrtx> elfy: ok
[12:52] <nrbrtx> elfy: you was too fast in launchpad. I have added file from comment 6 one minute ago - it boots to lightdm with it. So my bug is a really duplicate of yours, thank you!
[12:54] <lordievader> nrbrtx: Then please mark it as such.
[12:54] <lordievader> So people who find your bug will get redirected.
[12:54] <nrbrtx> lordievader: elfy already did it.
[12:55] <nrbrtx> bug 1376232
[12:56] <lordievader> Check
[12:57] <nrbrtx> bipul: any news? have you get to Unity in your virtual Ubuntu?
[12:58] <bipul> Yes after selecting ubuntu.vdi and then i booted it. followed by your instruction.
[13:00] <nrbrtx> bipul: so we can talk about bugs from first message.
[13:01] <bipul> yes
[13:04] <nrbrtx> bipul: could you please paste here my original message (i do not know, how to get my messages history).
[13:04] <bipul> sure.
[13:10] <bipul> nrbrtx: http://paste.ubuntu.com/8472626/
[13:11] <nrbrtx> bipul: how you did it? with which IRC commands&
[13:12] <bipul> no command just cut copy and paste :D
[13:12] <nrbrtx> bipul: ok, I mean my first message with bugs in Utopic. No problem - I'll write new.
[13:13] <lordievader> 01-12:18 < nrbrtx> Dear all! Today I have installed Ubuntu Utopic from beta2 CD and discovered that many bugs are still not fixed. These  bugs are: 1245137, 1242572, 1263228, 1244090, 1270574, 1270579, 1280759.
[13:13] <lordievader> nrbrtx: That one ^?
, you saved my time. Thank you!
[13:14] <nrbrtx> so let's see the bugs.
[13:14] <nrbrtx> bug 1245137
[13:15] <nrbrtx> bug 1242572
[13:15] <nrbrtx> bug 1244090
[13:15] <nrbrtx> bug 1270574
[13:16] <nrbrtx> bug 1280759
[13:17] <nrbrtx> These bugs (1245137, 1242572, 1244090, 1270574, 1280759) are very annoying.
[13:18] <nrbrtx> The less annoying bugs are: bug 1263228 and bug 1280759.
[13:18] <nrbrtx> (i mean bug 1270579 )
[13:19] <nrbrtx> It would be great if these bug will be fixed or confirmed by channel users (or better - ubuntu developers).
[14:34] <whitesn> is it ok to ask for troubleshooting for ubuntu 14.10 here?
[14:35] <lordievader> whitesn: Now until it is released ;)
[14:36] <whitesn> lordievader: you mean until it's stable?
[14:37] <lordievader> No, until it is released.
[14:39] <whitesn> lordievader: um, these aren't counted as releases? http://cdimage.ubuntu.com/ubuntu-desktop-next/daily-live/current/
[14:39] <lordievader> !schedule
[14:39] <lordievader> Release is supposed to be October the 23rd.
[14:40] <whitesn> lordievader: oh alright thanks then :)
[14:48] <BluesKaj> whitesn, you can still ask your question
[14:49] <whitesn> BluesKaj: i don't know how to explain it in a proper way since i'm not fond of linux, but the problem is when i tried to install default ubuntu / gnome 14.10 both of them went to black screen when booting (after install, restart)
[14:50] <whitesn> BluesKaj: now i am trying the guest mode / live session user and it's working for GNOME (haven't tried the default package yet) on VirtualBox
[14:53] <BluesKaj> whitesn, do you intend to use ubuntu on VB rather than a regular install to a linux partition?
[14:54] <whitesn> BluesKaj: i intend to install under VB/VM for now :)
[14:57] <BluesKaj> ok, whitesn, I'm not real familiar with using a windows host with a linux guest installation...what about you lordievader ?
[15:02] <whitesn> BluesKaj: hmm, i guess i'll try the 'temporary' version for now.
[15:04] <lordievader> There are quite a few bugs in regard to VBox + Utopic.
[15:04] <lordievader> bug 1375805
[15:04] <lordievader> bug 1371651
[15:06] <BluesKaj> whitesn, perhaps 14.04 rather than 14.10 would be a better choice, seeing the bugs that lordievader has pointed out could create more problems than it's worth for you
[15:08] <whitesn> well, I already tried the 14.04 before so I'm actually just curious about 14.10
[15:14] <BluesKaj> well, good luck whitesn
[15:19] <whitesn> BluesKaj: noob question: how to switch between workspaces in 14.10? I tried ctrl + alt + arrow keys and it's not working
[15:22] <lordievader> whitesn: What DE?
[15:23] <whitesn> lordievader: GNOME <- is this what it called by DE? I'm not really fond of linux..
[15:24] <lordievader> whitesn: Yes. I don't think BluesKaj or I know the shortcut in GNOME, we are KDE guys ;)
[15:24] <BluesKaj> fond or familiar ?
[15:24] <whitesn> not familiar*
[15:25] <BluesKaj> haven't used gnome in 8 yrs
[15:25] <BluesKaj> not fond means you don't really like something
[15:26] <lordievader> I've tried GNOME3 once, it was horrible. It was trying to be smart. If there's something I hate.... it's things trying to be smart.
[15:27] <whitesn> found it nevermind... hmm i don't even know which are good and what are the differences
[15:27] <whitesn> i just google a bit, and saw gnome has interesting interface and tried it ;)
[15:28] <whitesn> KDE = ubuntu default?
[15:28] <lordievader> whitesn: Kubuntu = Ubuntu + KDE. Ubuntu uses Unity.
[15:28] <BluesKaj> KDE is Kubuntu default desktop environment
[15:29] <elfy> hi lordievader BluesKaj
[15:29] <lordievader> Hey elfy, how are you doing?
[15:29] <BluesKaj> hi elfy , how goes it ?
[15:29] <elfy> good thanks - all done for the day :)
[15:30] <lordievader> elfy: Yayy, congratulations ;)
[15:30] <elfy> really hoping that I see no more vbox bugs this cycle too - it's getting a bit late for more :p
[15:30] <whitesn> which Kubuntu for 14.10 would you recommend to download?
[15:31] <lordievader> whitesn: Err, at this point I don't think a development release is a good option for you. Running a development release means you know what you are doing and you have basic troubleshooting skills.
[15:31] <whitesn> lordievader: so it's better to start from older version?
[15:32] <lordievader> whitesn: 14.04, the current release.
[15:32] <whitesn> i have no idea which distro and which version to start with, i'm not using it for depth development purposes though
[15:32] <whitesn> lordievader: and Kubuntu distro?
[15:33] <BluesKaj> whitesn, 14.10 is still not an official release, kubuntu 14.04 is a good choice
[15:34] <whitesn> alright thanks for the helps, i'll try it out
[15:34] <BluesKaj> whitesn, http://cdimage.ubuntu.com/kubuntu/releases/14.04.1/release/
[15:36] <whitesn> BluesKaj: got it!
[15:37] <BluesKaj> whitesn, have fun :)
[15:58] <creichen> I seem to have an installation of a recent (Unicorn) `Ubuntu Studio' installation now (trying to re-install an MBR on an existing system).  However, I can't run `onboard' from my existing partition, and I don't see any on-screen keyboards for this `Ubuntu Studio' thing either.  Any suggestions for enabling keyboard input?
[15:59] <creichen> (Might be because onboard is (apparently?) a python program?  Not sure.)
[17:12] <BluesKaj> rest the router firmware, had to reset the IPs in ssh and ssh keys in known_hosts
[17:13] <BluesKaj> reset
[17:17] <BluesKaj> anyway gotta take a walk to the mailbox
[18:10] <vitimiti> Hi
[18:11] <elfy> hi vitimiti
[18:11] <lordievader> o/
[18:11] <vitimiti> \o
[18:13] <lordievader> How are you this evening?
[18:14] <vitimiti> For off-topic #ubuntu-offtopic has to be used
[18:15] <lordievader> ... I know it is somewhat offtopic, but some social interaction should be tolerated imo. Improves bonding between testers.
[18:17] <vitimiti> Well, I'm kinda nervous, waiting for an important call from university
[18:17] <lordievader> vitimiti: Good luck ;)
[18:20] <vitimiti> thxc
[18:20] <vitimiti> -c*
[20:58] <AMDPentium> !ops | help channel emergency
[21:01] <lordievader> That seems rather pointless... Calling the ops when your banned...
[21:02] <k1l_> he seeks attention. seems to have a poor life
[21:02] <lordievader> Suppose he does...
[21:22] <jtaylor> hm is the person who had the docker problem recently still here?
[21:22] <jtaylor> now I have it too :(


[10:04] <alan_g> alf_: content with answer? https://code.launchpad.net/~kdub/mir/current-buffer-id-fix/+merge/275986
[10:06] <alf_> alan_g: yes
[11:14] <alan_g> alf_: my kms problem from yesterday. I find that DRM_MODE_DISCONNECTED gets set in reset() after the "connector = resources.connector(connector_id);". Any thoughts?
[12:05] <greyback_> RAOF: http://pastebin.ubuntu.com/13123486/
[12:10] <RAOF> Ta
[12:40] <alf_> alan_g: @kms, this seems normal, it gets the latest state from the hardware
[12:42] <alan_g> alf_: so we're aborting because the hardware state is unexpected?
[12:46] <alf_> alan_g: yes, but the thing is that we shouldn't be trying to set the crtc on a disconnected connector, so the problem may be at a higher level
[12:46] <alf_> alan_g: do the instructions for reproducing this still stand?
[12:47] <alf_> alan_g: (using the two branches over trunk)
[12:47] <alan_g> alf_: yes. Or use your fix-1511798 branch, in which case you also have to stop the nested server before seeing the crash
[12:48] <alan_g> BTW one of those branches has landed
[12:50] <alf_> alan_g: ok, I will give it a go
[12:51] <alan_g> alf_: thanks.
[12:58] <alan_g> alf_: I know this is "wrong" but it seems to workaround problems:
[12:58] <alan_g> -    connector = resources.connector(connector_id);
[12:58] <alan_g> +    if (!connector || (new_connector && new_connector->connection == DRM_MODE_CONNECTED))
[12:58] <alan_g> +        connector = std::move(new_connector);
[13:03] <alan_g> Hmm, missed a "+    auto new_connector = resources.connector(connector_id);"
[13:04] <alf_> alan_g: ack
[14:16] <alan_g> alf_: any thoughts on my kms problem?
[14:21] <alf_> alan_g: with the alternative fix I was able to reproduce only once, further attempts worked fine.
[14:24] <alan_g> Without the patch to reset() I've been getting it consistently.
[14:25] <alf_> alan_g: just to make sure, instructions are: sudo gdb --args bin/mir_demo_server --window-manager system-compositor --display-config sidebyside --vt 1 --arw-file --on-fatal-error-abort --display-report log
[14:25] <alf_> alan_g: plug in screen
[14:25] <alan_g> alf_: oh! I'm testing on V+, are you on Wily?
[14:26] <alf_> alan_g: yes
[14:26] <alf_> alan_g: wily
[14:27] <alf_> alan_g: 3. bin/mir_demo_server.bin --host /tmp/mir_socket --display-config sidebyside
[14:27] <alf_> alan_g: 4. bin/mir_demo_standalone_render_surfaces --no-file --host-socket /run/user/1000/mir_socket --display-config single
[14:27] <alf_> alan_g: Then ctrl-c (4) and (3)
[14:27] <alan_g> step 3 s/.bin//
[14:28] <alan_g> Otherwise yes
[14:31] <alan_g> So it could be specific hardware, or the OS drivers
[14:55] <alf_> alan_g: It's likely that this is HW/driver related problem, because getting DRM_MODE_DISCONNECTED for a screen that is clearly plugged in, is not something Mir could really affect or mess up (unless there is memory error somewhere).
[14:57] <alf_> alan_g: @alternative fix, your concern is that although it passes the tests it doesn't have the desired effect in the above scenario (ctrl-c render surfaces), correct?
[14:58] <alan_g> yes. At least my concern is I don't understand why (yet).
[14:58] <alf_> alan_g: so, I take it that you are investigating this?
[14:59] <alan_g> currently tracing through the code
[15:00] <alf_> alan_g: ok, then I will do something different for now, but let me know if you need me to try something
[15:01] <alan_g> alf_: thanks. You said you also saw the kms issue sometimes? Is it worth MPing my workaround?
[15:08] <alf_> alan_g: I think it may break monitor disconnects in some cases (it won't update the connector if the monitor has been really disconnected), so I am hesitant to include it
[15:09] <alan_g> yeah. I hate having Mir crash as a result though.
[15:21] <alf_> alan_g: We could try to be more forgiving of incorrect set_crtc() calls, e.g., log a warning instead of aborting
[15:21] <alf_> alan_g: (incorrect => failed)
[15:23] <alan_g> alf_: when I've finished handling interrupts and investigating your alternative fix I'll try to find something more plausible.
[15:25] <alf_> alan_g: ack, from a quick look I think 1. logging a warning + returning false in mgm::RealKMSOutput::set_crtc() and 2. not aborting in mgm::DisplayBuffer::set_crtc() should do the trick, but perhaps there are other points we need to update
[15:25] <alf_> alan_g: I would propose the changes myself, but I can't really test if it helps for your use case
[15:27] <alan_g> \o/ alf_: I understand the difference - AbstractShell::focus_next_session() is selecting the dying surface's titlebar. (And that doesn't exist in the core WM that gets tested.)
[15:31] <alf_> alan_g: great
[16:00] <alan_g> alf_: should I start another loop by taking your alternate fix and MPing the changes?
[16:01] <alf_> alan_g: fine with me
[18:32] <mcphail> bschaefer: ping
[18:32] <bschaefer> mcphail, pong
[18:32] <mcphail> Hi - are you still working on SDL2 for mir?
[18:33] <bschaefer> mcphail, when its needed, or when a bug comes up
[18:33] <bschaefer> mcphail, any bugs?
[18:33] <mcphail> do you have a link for a version which works with the current Mir libs on the phone?
[18:33] <bschaefer> mcphail, yeah: https://code.launchpad.net/~brandontschaefer/libsdl/update-mir-new-abi-api/+merge/276578
[18:33] <bschaefer> thats the patch
[18:33] <mcphail> Ta muchly!
[18:33] <bschaefer> for SDL2 to then new mir API
[18:33] <bschaefer> mcphail, here is the the actual branch:
[18:34] <bschaefer> https://code.launchpad.net/~brandontschaefer/+junk/SDL2-new-mir-ABI
[18:34] <bschaefer> so you dont have to apply the patch, its already applied
[18:34] <mcphail> slvn_: ^^
[18:34] <mcphail> bschaefer: you are a hero
[18:34] <bschaefer> np, poke me if theres any issues!
[18:34] <slvn_> thanks !
[18:34] <mcphail> bschaefer: will do
[18:35] <mcphail> bschaefer: slvn_ is going to bring us some new games!
[18:35] <bschaefer> sweet!
[18:35] <bschaefer> slvn_, if it works on arm you can post on that MP that you've tested it and all :)
[18:35]  * bschaefer needs to double check it works on the phone
[18:36] <bschaefer> IIRC it does...but i dont remember
[18:36] <slvn_> what is MP ?
[18:37] <slvn_> bschaefer, a few month ago my games where working with the SDL / mir backend
[18:37] <bschaefer> merge proposal
[18:37] <bschaefer> yup, until mir 0.14 and greater :)
[18:37] <bschaefer> all i did was move to the new API/ABI
[18:37] <bschaefer> https://code.launchpad.net/~brandontschaefer/libsdl/update-mir-new-abi-api/+merge/276578
[18:37] <bschaefer> the MP ^
[18:38] <mcphail> do we still need to --disable-shared-mir when building?
[18:38] <bschaefer> mcphail, you shouldnt
[18:38] <slvn_> Ok ! yes, we found out with mcphail that api function where missing / renamed because of the new api
[18:38] <bschaefer> the only reason that was needed, was because it was broken :)
[18:38] <mcphail> ha!
[18:38] <bschaefer> ie. functions didnt line up
[18:38] <bschaefer> (they kept changing MirBool to bool and back and forth)
[18:38] <bschaefer> and would keep the dynamic loading from not working


[00:46] <Unit193> Hrm, any idea when riscv will be available for PPAs?
[00:56] <sarnold> Unit193: I've got a checkbox on one of my ppas, though maybe I have that due to magic powers
[00:56] <Unit193> My box is all grayed out.
[00:56] <sarnold> oh :(
[00:57] <Unit193> Which normally I don't care about riscv at all, but something is failing only there, and for some silly reason it's not migrating.
[00:57] <sarnold> Unit193: probably the way to find out if you can have it flipped is to file a question on the launchpad questions section
[00:57] <sarnold> Unit193: I think some of the biletto ppas have it enabled too, would that be any help?
[00:57] <Unit193> sarnold: Well...I don't really want special treatment if it's not really ready yet. :3
[00:57] <sarnold> (I've never tried these)
[00:57] <Unit193> I have no idea how to use those either. :D
[00:57] <sarnold> hehe
[01:24] <sarnold> Unit193: heh, was it failing package tests? https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1891686
[01:40] <Trevinho> mwhudson: if it helps, this is the diff of what has been installed in gjs (+ proposed) vs the failing one: https://paste.ubuntu.com/p/VDTQpzVWQT/
[01:40] <Trevinho> mwhudson: gobject-introspection amd64 1.64.1-1build2 looks to be a good candidate
[01:42] <mwhudson> Trevinho: yeah, sounds plausible
[01:43] <Trevinho> mwhudson: you can probably do a build1 with that, or I can but tomorrow
[01:43] <mwhudson> Trevinho: well it's also part of the libffi transition so they will migrate together
[01:43] <Trevinho> yeah, sure,  I mean if we need to have a specific b-d for britney happyness
[01:44] <mwhudson> i don't think so
[01:44] <mwhudson> thanks for checking though!
[02:23] <Unit193> sarnold: FTBFS.
[07:04] <rs2009> Hi, I noticed that the filesystem.squashfs in the Groovy Gorilla daily builds have /boot/vmlinuz and /boot/initrd.img as broken symlinks. They point to initrd.img-* and vmlinuz-*, which do not exist. I was building a custom Ubuntu ISO from an existing Ubuntu 20.10 daily ISO using the chroot method. I copied the initramfs from the /casper/ directory
[07:04] <rs2009> in the custom disk and installed the linux-image in the chroot, as I needed to change the plymouth logo. I then ran update-initramfs -u -k all inside the chroot. I copied /boot/initrd.img to /casper/ and built the ISO. When I booted the ISO in a VM, it showed the plymouth boot screen for one second, after which it dropped to the BusyBox initramfs
[07:04] <rs2009> prompt. Did something change in 20.10? I'm not aware of any change apart from the switch to GRUB for both BIOS and UEFI.
[12:08] <ddstreet> Laney i think the autopkgtest armhf lxd-worker needs to be restarted to pick up a worker.conf change, to make haveged a long_test; it is still running it with the default timeout, though haveged was added to long_tests a week or so ago
[12:08] <ddstreet> could you check it when you have a chance?
[12:08] <Laney> ddstreet: it does, who deployed it?
[12:08] <Laney> they might need some education
[12:08]  * Laney brings out the education stick
[12:08] <ddstreet> Laney you mean who deployed autopkgtest? this is on the official builders https://autopkgtest.ubuntu.com/packages/h/haveged/groovy/armhf
[12:08] <Laney> who merged the config change
[12:09] <ddstreet> oh, i think vorlon
[12:09] <ddstreet> https://git.launchpad.net/autopkgtest-cloud/commit/?id=5763aed3a3a1c1eb3839bf74263f885ae979527e
[12:10] <Laney> right, missed being done on armhf
[12:10] <Laney> done now
[12:10] <ddstreet> thanks!
[15:02] <xnox> rs2009: is this desktop or server?
[15:03] <xnox> rs2009:  did you also specify environmental variable to trigger casper initrd to be generated with uuid checks?
[15:18] <rs2009> xnox: This is the desktop variant. I wasn't building a daily image, rather was chrooting into the ISO and making some changes, and then rebuilding the ISO.
[15:19] <xnox> rs2009:  when rebuilding initrd you must set CASPER_GENERATE_UUID environment variable.
[15:19] <xnox> rs2009:  or have grub.cfg to have boot=casper
[15:19] <xnox> in kernel commandline.
[15:20] <rs2009> xnox: I already have boot=casper in the kernel commandline.
[15:20] <xnox> rs2009:  by default we build initrd for the iso with CASPER_GENERATE_UUID=y set, matching uuid committed on the iso in .disk/, and with clean kernel commandline.
[15:20] <xnox> rs2009:  in that case i don't know why your boot failed. and you do not give enough information for me to suggest antyhing to you.
[15:21] <xnox> rs2009:  it sounds like you have missbuilt your kernel/initrd pair, and it doesn't match the rest of the iso.
[15:23] <rs2009> xnox: I was building a custom Ubuntu ISO from an existing Ubuntu 20.10 daily ISO (using the chroot method) when I saw that /boot/initrd.img and /boot/vmlinuz are broken symlinks in filesystem.squashfs. I copied the initramfs from the /casper/ directory in the custom disk and installed the linux-image in the chroot, as I needed to change the
[15:23] <rs2009> plymouth logo. I then ran update-initramfs -u -k all inside the chroot. I copied /boot/initrd.img to /casper/ and built the ISO. When I booted the ISO in a VM, it showed the plymouth boot screen for one second, after which it dropped to the BusyBox initramfs prompt.
[15:28] <rs2009> xnox: the daily ISO has 5.4.0-42-generic (checked in /lib/modules) and the initrd kernel version corresponds to it.
[15:33] <rs2009> xnox: This issue does not happen with the default initramfs, rather with an initramfs built with update-initramfs
[15:33] <Laney> rbalint: https://launchpadlibrarian.net/495890903/buildlog_ubuntu-groovy-armhf.mozjs78_78.2.0-1~fakesync1_BUILDING.txt.gz does this interest you?
[15:34] <Laney> also, I saw your ping on that autopkgtest-cloud MR, will review this week
[15:34] <xnox> rs2009:  you should have no need to install linux-image.... as that one might be different from the rest of iso.
[15:34] <xnox> rs2009:  and you should restore initrd&vmlinuz from casper into where the broken links point to.
[15:35] <xnox> rs2009:  and you should generate new initrd for that same kernel version, not any other different one.
[15:35] <xnox> rs2009:  calling update-initramfs without environment variables set, and without correct kernel version as installed in the chroot, will not generate a complete nor valid initrd usable for cd boot.
[15:37] <rs2009> xnox: The issue happens without linux-image as well. I had restored the initrd and vmlinuz to where the broken links point to. I was building the initramfs for the kernel in the ISO only. I did not know that it was mandatory to build with CASPER_GENERATE_UUID=y set. I thought it wasn't required if boot=casper was being added to the command line.
[15:39] <xnox> rs2009: and how did you rebuild the initrd? which kernel version did you specify?
[15:40] <xnox> rs2009:  after you build with CASPER_GENERATE_UUID=y you also need to copy out the same uuid into the iso. otherwise there will be uuid-missmatch and you will fail to boot.
[15:41] <rs2009> xnox: I used update-initramfs and specified 5.4.0-42-generic which I found in /lib/modules/.
[15:42] <xnox> rs2009:  yeap that's the right version number, so that should have worked.
[15:42] <rs2009> xnox: I'm trying out CASPER_GENERATE_UUID=y right now
[15:42] <xnox> generate initrd with UUID, copy it out and place it on the iso in .disk/ dir, remaster the iso and hopefully things will start working
[15:43] <xnox> if they don't, edit kernel cmdline and append ignore_uuid to ignore uuid missmatch, to doulbe check if that's what's causing the failure to boot
[15:59] <rs2009> xnox: ignore_uuid works, so it looks to be an issue with the UUID. I couldn't find the UUID in the output of update-initramfs.
[16:33] <xnox> rs2009:  it's inside the initrd.... one has to unpack it to copy it into the .disk/uuid
[16:34] <rs2009> xnox: Yes, I was doing that :) Thank you for your help!
[19:54] <rbalint> Laney, re: MR, thanks! re: mozjs, no, sorry, i'd like to get glibc rounds done first


[10:28] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4628 Needs rebuild due to higher version at destination (impish/u-boot). Proposed pocket (impish/crust-firmware, impish/gcc-or1k-elf). Release pocket (impish/binutils-or1k-elf)
[12:32] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4632 Proposed pocket
[15:10] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4630 Needs building (focal/evdi). UNAPPROVED queue (focal/lttng-modules)
[15:50] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4630 Diff missing (focal/evdi). UNAPPROVED queue (focal/lttng-modules)
[16:11] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4630 UNAPPROVED queue
[16:52] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4631 Pending binary packages
[16:59] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4618 Proposed pocket (focal/bcmwl). Updates pocket (focal/rtl8812au)
[17:11] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4631 Successfully built
[17:25] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4631 Generating diffs
[17:25] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4631 Successfully built
[21:07] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4607 Needs rebuild due to higher version at destination
[21:29] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4608 Needs rebuild due to higher version at destination (focal/evdi). Proposed pocket (focal/backport-iwlwifi-dkms). Ready to build (focal/xtables-addons). Security pocket (focal/openafs)
[21:31] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4630 Proposed pocket (focal/evdi). UNAPPROVED queue (focal/lttng-modules)
[23:10] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4630 Proposed pocket (focal/evdi). REJECTED queue (focal/lttng-modules)
[23:50] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4630 Proposed pocket (focal/evdi). UNAPPROVED queue (focal/lttng-modules)


[05:06] <mborzecki> morning
[05:25] <zyga> Hey
[05:25] <zyga> mborzecki: I found a hell of a bug yesterday
[05:26] <zyga> Working >12 hours but was worth it
[05:29] <mborzecki> zyga: hey, what bug?
[05:31] <zyga> Mount namespaces are seriously busted
[05:32] <zyga> This explains all the odd reports I got
[05:32] <zyga> I am tired a bit, still in bed
[05:33] <mborzecki> zyga: nice that you found it :)
[05:34] <zyga> I spent half of yesterday trying to nail what was going on
[05:34] <zyga> There are several bugs
[05:34] <zyga> I know of two for sure because those got fixed in my branch
[05:35] <zyga> The third one I know where it is but I was too tired to figure out where it is past 23:00
[05:35] <zyga> Hehe
[05:35] <zyga> To figure out exactly where it is
[05:43] <zyga> Those are all serious enough I think we should do .2
[06:11] <zyga> Hey mvo
[06:11] <zyga> I found a naaaasty bug last night
[06:12] <mvo> hey zyga ! good morning
[06:12] <mvo> zyga: uh, that sounds bad - can you tell me more please?
[06:14] <zyga> Mvo: mount namespaces have three bugs that cripple content sharing
[06:14] <zyga> 1) we unshare one too many times, this was fixed about 6 months ago but not merged, lost in a feature branch
[06:15] <zyga> 2) sharing is broken so user mount namespace does not get propagation correctly, breaking on refresh or reconnect depending on use
[06:15] <zyga> 3) ordering of mount operations is wrong, causing shadowing of past mounts
[06:16] <zyga> Lots of craze last night
[06:16] <zyga> I had a call with Jamie to discuss some of this
[06:16] <zyga> 1 is simple
[06:17] <zyga> 2 is todo, didn’t debug as I realized this was broken after 23:00
[06:17] <zyga> 3 is complex and requires some algorithm work
[06:18] <zyga> Together those break gnome runtime sharing, theme sharing and perhaps other cases
[06:18] <mvo> zyga: uh, that sounds nasty
[06:19] <mvo> zyga: lets talk some more in some minutes, I make a cup of tea
[06:19] <zyga> Excellent idea :-)
[06:27] <mborzecki> mvo: morning
[06:39] <mvo> hey mborzecki
[06:44] <zyga> mvo: back in the office
[06:52] <zyga> slowly waking up
[07:03] <pedronis>  morning
[07:03] <pedronis> could we get a 2nd review of #6775
[07:03] <mup> PR #6775: devicestate: make Remodel() return a state.Change <Created by mvo5> <https://github.com/snapcore/snapd/pull/6775>
[07:11] <pstolowski> morning
[07:12] <pedronis> pstolowski: hi, I have a question in #6793
[07:12] <mup> PR #6793: cmd/snap: support for --ensure argument for snap debug timings <Created by stolowski> <https://github.com/snapcore/snapd/pull/6793>
[07:16] <mborzecki> pedronis: pstolowski: hey
[07:17] <pstolowski> pedronis: yes... you're right, i forgot about those
[07:18] <pstolowski> i mean about nesting them visually
[07:24] <mup> PR snapd#6790 closed: interfaces: add login-session-control interface <Created by AlanGriffiths> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/6790>
[07:26] <mvo> zyga: was wondering about 6751, it seems it just misses a unit test to go into master, can I help you with that? I would love to land this before lyon
[07:26] <zyga> mvo: perhaps, I will try to devote an hour to it today
[07:26] <zyga> sorry for taking so long, yesterday was a marathon of debugging
[07:27] <mvo> zyga: I can look at it, I understand you are looking at important bugs
[07:33] <pedronis> pstolowski: thanks, so  I wasn't confused, I think we do the same with ^ as for the change.
[07:33] <pstolowski> pedronis: yes
[07:33] <pedronis> pstolowski: let me make a comment in the PR itself
[07:34] <pedronis> mborzecki: made a couple of comments in 6750
[07:34] <pedronis> one is not of immediate relevance
[07:34] <mborzecki> pedronis: thanks, reading through them now
[07:36] <pedronis> pstolowski: for Ensure, is the label of level 0 usually the same as the "ensure" tag, or is just for some ?
[07:37] <mup> Bug #1828175 opened: Lack of proxy support for snap prepare-image <Snappy:New> <https://launchpad.net/bugs/1828175>
[07:40] <pstolowski> pedronis: using refresh catalogs as an example: we have "ensure": "refresh-catalogs", then two nested measurements under it: with "get-sections" and "write-catalogs" labels
[07:41] <pedronis> pstolowski: thx, noticed the same
[07:41] <pedronis> pstolowski: I was thinking a bit about what to put in ID, but given that we don't want to make lines too long
[07:41] <pedronis> "ensure" seems fine  (it's a debugging thing and one should know what they asked)
[07:42] <mvo> zyga: I will push something shortly
[07:48] <mborzecki> pstolowski: if we can tweak the formatting of timing entries a bit, may we use ---^ or --- to fill the line before ^ sign?
[08:05] <mborzecki> pstolowski: http://paste.ubuntu.com/p/7dWSfRbTrc/ this is what i mean, the ^ dashes feel a bit hard to follow
[08:05] <pstolowski> pedronis: actually, we won't see "^" nesting for ensures right now, the refresh-catalogs is the root node with tags, then get-sections and write-catalogs are at level 0. for tasks level 0 measurements appear nested visually because we put them under task line
[08:06] <mborzecki> Chipaca: welcome back
[08:06] <Chipaca> mborzecki: :)
[08:08] <pstolowski> mborzecki: yep, i tend to agree, but i'd leave it for a potential followup, this had already been disputed about in one of the first PR in these series ;)
[08:09] <mborzecki> pstolowski: mhm, sounds good to me, i don't have an immediate suggestion now either, but maybe we'll come up with something once people start using it
[08:11] <Chipaca> pedronis: you around?
[08:14] <mborzecki> got a quick errand to run, back in ~30
[08:43] <pstolowski> pedronis: pushed some changes + reply to your comment
[08:45] <pstolowski> pedronis: also, i need to discuss with you some aspects of snap unset implementation that i touched breifly with mvo yesterday in the standup; would be great to meet (three of us) today
[09:05] <mborzecki> re
[09:21] <pedronis> pstolowski: sorry was in meetings,  interesting about the 0 level, maybe we should have an articial one
[09:21] <pedronis> though maybe is just a wasted line, but it would clarify things
[09:23] <pstolowski> pedronis: yes, i can add this
[09:24] <pstolowski> pedronis: nb, can you merge master into your PRs? i'm about to do reviewing, will make diffs smaller
[09:24] <pstolowski> pedronis: eg #6822 (and it has a conflict)
[09:25] <mup> PR #6822: overlord/devicestate: introduce registrationContext <Created by pedronis> <https://github.com/snapcore/snapd/pull/6822>
[09:29] <pedronis> pstolowski: basically the articial line should contain  "ensure" and somewhere the ensure tag
[09:29] <pedronis> pstolowski: can also be a follow up a this point though
[09:30] <pedronis> pstolowski: yes, need a little break after the meetings but will look at my PRs, I'm also doing reviews
[09:30] <pedronis> of some team PRs
[09:41] <pedronis> pstolowski: btw you can review mvo 6775 and 6776 if you are wating to review mines
[09:46] <pstolowski> pedronis: ok. yep i'd prefer a followup
[09:46] <pstolowski> pedronis: did you see my message about the need of discussing snap unset?
[09:50] <mborzecki> anyone up for a 2nd review of https://github.com/snapcore/snapd/pull/6798 ?
[09:51] <mup> PR #6798: gadget: introduce checkers for sanitizing structure updates <Gadget update> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/6798>
[09:51]  * zyga woke up again
[09:51] <zyga> sorry everyone, had a rough night
[09:52] <zyga> mvo: thank you for the tests
[09:52] <pedronis> pstolowski: yes, are you blocked?  I can do after lunch or immeditately after standup, but not sure when mvo can
[09:53] <pstolowski> pedronis: a bit blocked yes, but i'm doing reviews so it can wait for later today
[10:24] <mup> PR snapd#6826 closed: tests: enable tests on centos 7 again <Created by sergiocazzolato> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/6826>
[10:33]  * Chipaca afk for a while
[11:26] <zyga> man that's so darn annoying
[11:26] <zyga> I'm staring the bug in the face
[11:26] <zyga> I see it's wrong
[11:27] <zyga> but yet WHY eludes me
[11:35] <cachio> mvo, hey
[11:36] <cachio> mvo, could you please merge #6694 to 2.39? I need that to finish snapd validation
[11:36] <mup> PR #6694: tests: improve how snaps are cached <Created by sergiocazzolato> <Merged by sergiocazzolato> <https://github.com/snapcore/snapd/pull/6694>
[11:42] <mvo> cachio: uh, 27 commits, let me see how we can do this
[11:42] <mvo> I can't cherry pick this indivudally
[11:43] <mvo> cachio: lets talk after (my) lunch, we get this in I might need to do it with conflicts instead of as cherry-picks
[11:43] <cachio> mvo, sure
[11:43] <cachio> thanks
[11:45] <zyga> brb
[11:45] <zyga> uhhhh
[11:49] <zyga> re
[11:56] <pedronis> pstolowski: we could chat now but maybe you and mvo are having lunch atm
[12:10] <pstolowski> pedronis: works for me if mvo is around
[12:10] <pedronis> pstolowski: do we need mvo?
[12:11] <pedronis> pstolowski: I'm in the standup channel
[12:11] <pstolowski> pedronis: ok, coming
[12:12] <mup> PR snapcraft#2560 opened: meta: do not wrap commands by default <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/2560>
[12:23]  * Chipaca goes in quest of food
[12:35] <mup> PR snapd#6821 closed: many: make which store to use contextual  <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/6821>
[12:39] <pedronis> Chipaca: ^ that provoked conflicts in your PRs I fear
[12:39] <pedronis> I can look into that myself in a bit
[12:46] <cmatsuoka> niemeyer: do you prefer adapter: none or no adapter line at all in the gnome extension?
[12:47] <cmatsuoka> (sergiusens is changing that now and we can do it in either way)
[12:47] <cachio> q
[12:52] <pedronis> #6828 can be reviewed  (because of later pushes 6822 comes later in the chain now)
[12:52] <mup> PR #6828: many: use a fake assertion model in the device contexts for tests <Created by pedronis> <https://github.com/snapcore/snapd/pull/6828>
[12:52] <mup> PR snapd#6840 opened: gadget: fix handling of positioning constrains for structures of MBR role <Gadget update> <Simple 😃> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/6840>
[12:53] <mborzecki> simple PR ^^ cmatsuoka pstolowski maybe?
[12:54] <cmatsuoka> mborzecki: checking that
[12:54] <mborzecki> cmatsuoka: thanks
[12:56] <mvo> pedronis, pstolowski sorry, had lunch indeed
[12:57] <pstolowski> mvo: np, i think the solution is uncontroversial, we will brief you in a momentr
[12:59] <Chipaca> pedronis: conflict is life
[12:59] <mvo> pstolowski: \o/
[13:20] <niemeyer> cmatsuoka: none or none at all seem similar
[13:21] <cmatsuoka> niemeyer: ack
[13:22] <niemeyer> cmatsuoka: But I'm still not sure I get what's going on there.. does adapter: full really mean no adapter?
[13:22] <niemeyer> That seems pretty absurd
[13:22] <cmatsuoka> From what I see there adapter: none means no adapter, "full" means command chain and "legacy" means wrappers
[13:23] <cmatsuoka> but sergiusens is changing the default to command chain
[13:27] <cmatsuoka> (I do agree that the choice of words isn't very clear)
[14:03] <mborzecki> off to school
[14:10]  * zyga is onto something!
[14:11] <niemeyer> cmatsuoka: Yeah, the command chain isn't an adapter.. it's also under the control of the command-chain field itself, so there's no need to say anything else
[14:20] <pedronis> cachio: we got this:  https://api.travis-ci.org/v3/job/529764900/log.txt
[14:20] <pedronis> internal error: a core16 snap is installed, earlier test cleanup did not work
[14:22] <sergiusens> niemeyer: as absurd as it feels now, it is was we concluded with kyrofa on https://forum.snapcraft.io/t/proposal-add-command-chain-to-apps-instead-of-generating-opaque-wrappers/6018 ... I'll see how we can get out of that, but it won't be as easy
[14:29] <mvo> cachio: I looked at 6694 but cherry-picking it in isolation to release/2.39 shows conflicts on the first patch already so I think there is another PR before that that modified this part of the prepare.sh. do you remember which one that might be? did we had something similar before? we may need to cherry-pick both
[14:30] <pedronis> mvo: I'll do the small fix pstolowski asked in your #6775
[14:30] <mup> PR #6775: devicestate: make Remodel() return a state.Change <Created by mvo5> <https://github.com/snapcore/snapd/pull/6775>
[14:32] <niemeyer> sergiusens: We discussed that when introducing bases
[14:33] <niemeyer> sergiusens: We added the command chain concept at the same time so we would  not break compatibility in the future
[14:34] <niemeyer> sergiusens: So I hope at least with a base, the default is no adapter.. is that the case?
[14:36] <niemeyer> Small? Large?
[14:37] <mvo> pedronis: thank you
[14:37] <pedronis> mvo: done
[14:37] <cachio> pedronis, checking
[14:37] <mvo> pedronis: \o/
[14:38] <cachio> pedronis, this is on master right?
[14:38] <cachio> because that should be fixed
[14:39] <pedronis> cachio: one of my PRs
[14:39] <cachio> mvo, checking
[14:39] <pedronis> but I had merge with master today I think
[14:40] <cachio> pedronis, in that case I'll need to take a look, that should be fixed, which is the PR?
[14:41] <pedronis> cachio: this one:  https://github.com/snapcore/snapd/pull/6828  (doesn't touch spread stuff)
[14:42] <mup> PR #6828: many: use a fake assertion model in the device contexts for tests <Remodel :train:> <Created by pedronis> <https://github.com/snapcore/snapd/pull/6828>
[14:42] <cachio> pedronis, thanks
[14:42] <pedronis> it's actually all unit tests changes I think
[14:48] <ijohnson> hi folks, what's the status of building core18 snaps on travis (especially with respect to using build-snaps)? is launching a docker container still the thing to do on travis?
[14:48] <cachio> mvo, this is giivng conflicts?  git cherry-pick 2e10db98657923a58fd7461586d150cfa97fc5b2
[14:52] <cachio> mvo, I could cherry pick all of them
[14:53] <mvo> cachio: this one looks fine, let me see if that is the one I was missing
[14:54] <cachio> mvo, the problem with this PR is that I tried many alternative during time until the last one was choosend
[14:54] <mvo> cachio: ohhhh, so only the last one is relevant? and that applies cleanly?
[14:54] <mvo> cachio: in this case we are good :)
[14:55] <cachio> mvo, no
[14:55] <cachio> mvo, it is a mix
[14:56] <mvo> zyga: a re-review of 6820 would be great, it already has a +0.9 from you :)
[14:56] <cachio> mvo, let me check which are needed
[14:56] <cachio> I'll give you a list
[14:57] <mvo> cachio: thanks
[14:57] <mvo> cachio: alternatively, feel free to branch off releae/2.39 and cherry-pick as needed
[14:57] <mvo> cachio: it seems like we just have to live with some conflicts when merigng back but thats ok
[15:00] <sergiusens> niemeyer: it is not, we can discuss the reasons next week; we did discuss this with bases, but at the end of last cycle, command-chain had not made the release cut in snapd ...
[15:01] <zyga> mvo: looking
[15:03] <zyga> mvo: +1
[15:03] <cachio> pedronis, this seems to be new, I'll try to reproduce it locally, thanks for the log
[15:07] <niemeyer> sergiusens: This is extremely unfortunate.. the whole point of command-chain was to avoid breaking compatibility in the future after bases were introduced
[15:08] <niemeyer> sergiusens: What's your plan now to make them the default and adapters gone without breaking people?
[15:08] <niemeyer> There's zero gain in command-chain if everybody has adapters
[15:08] <niemeyer> :/
[15:10] <sergiusens> niemeyer: I will bring a proposal to discuss with you for next week, migrating is something we already discussed with kyrofa
[15:17] <pstolowski> mvo, pedronis hotplug mystery wrt core18 solved
[15:18] <pstolowski> mvo, pedronis serial-port interface doesn't contain hotplug changes in 2.38.1. hotplug subsystem is triggered, just 0 interfaces support it. i have no idea how that happened that it didn't land in release brach :(
[15:19] <ijohnson> sil2100: hey where is the "official" repository for pi gadgets these days? is it https://github.com/snapcore/pi-gadget ?
[15:20] <mvo> pstolowski: so 2.39 fixes it?
[15:20] <mvo> ijohnson: this looks correct
[15:21] <ijohnson> mvo: cool thanks, we need to add the bt-serial interface back to the gadget there for uc18
[15:22] <mvo> ijohnson: oh, that got lost? yeah, totally
[15:22]  * mvo wonders why :(
[15:22] <mvo> ijohnson: are you looking into this or sil2100 ?
[15:22] <ijohnson> I was just wondering because the snapcore repo is more active but there's also github.com/CanonicalLtd/pi-gadget
[15:23] <ijohnson> mvo: I'm actually looking into this because I wasn't able to use hotplug for the bluetooth adapter serial port, then learned that the gadget is supposed to include a slot for that and it's missing from the gadget on uc18 for some reason
[15:23] <ijohnson> mvo: I was just going to file a PR to quick add it since it's 3 lines
[15:24] <ijohnson> mvo: but I'm not sure which repo is watched for PR's :-)
[15:24] <mvo> ijohnson: it should show up here :)
[15:24] <pstolowski> mvo: 2.39 has the serial-port changes so yes, should work. i'm going to verify that
[15:24] <mvo> ijohnson: mup should tell us
[15:24] <mvo> pstolowski: it will work once the gagdet is fixed? or today?
[15:25] <pedronis> pstolowski: did you look whether system snap setting up is correct overall?
[15:28] <pstolowski> pedronis: yes, it looks ok (mapper says it's "snapd"). however i haven't checked seeding etc. i'm not sure how my manual testing affects it
[15:34] <pedronis> pstolowski: ok, I'll try to look at that myself (I don't remember the details)
[15:41] <sil2100> ijohnson: yes, that's the right repository
[15:41] <sil2100> ijohnson: (snapcore)
[15:41] <ijohnson> sil2100: great thanks for confirmation
[15:42] <sil2100> ijohnson: I need to remove the CanonicalLtd ones, I created those when Foundations had no powers to manage the snapcore ones ;)
[15:42] <ijohnson> ah I see that makes sense
[15:42] <sil2100> (sorry for the confusion)
[15:42] <ijohnson> np
[15:42] <sil2100> ijohnson: just in case https://wiki.ubuntu.com/UbuntuCore/Development should be up-to-date with this things
[15:43] <ijohnson> thanks sil1200 that's really helpful I wasn't aware of that page
[15:44] <ogra> should be promoted on the forum and snapcraft docs
[15:44] <ijohnson> +1
[15:47] <ijohnson> also, question for mvo and pedronis if it's quick (if it's not quick/easy let me know and I'll start a forum post instead), how does snapd handle gadget slots for devices like a serial port that doesn't actually exist?
[15:48] <ijohnson> the idea here being that we declare a serial port slot on a gadget for pi2 and pi3, but the serial port actually only exists on the pi3 and not on the pi2
[15:49] <ogra> yeah, specifically with interfaces that define a device path in their interface declaration, is snapd checking the device actually exists before exposing the interface ?
[15:49] <pedronis> ijohnson: I don't think we check/supress atm, we do trust the dgadget
[15:49] <ogra> (thats what i would expect actually)
[15:49] <pedronis> it could be considered a bug
[15:49] <pedronis> but that's current behavior
[15:49] <ogra> ouch
[15:49] <ijohnson> ok, do you want me to start a conversation on the forum for this?
[15:50] <pedronis> yes
[15:50] <ijohnson> ack thanks
[15:55] <cachio> mvo, change cherry picked to 2.39
[15:57] <cachio> mvo, pushed to branch on snapcore, is it ok or I should push to my own copy and then create a PR?
[15:58] <mvo> cachio: thanks! doing in a PR would be ideal but if travis is happy thats fine. thanks for doing this
[15:58] <cachio> mvo, ok, sorry, lets see if it works
[15:59] <mvo> cachio: aha, nice! it looks like it all merges back into master nicely, no conflict afaict. cool
[15:59] <mvo> cachio: yeah, I wasn't clear in my original question/request so no worries
[16:00] <cachio> mvo, I found another improvement to implement by reviewing the change :)
[16:00] <pstolowski> mvo, pedronis: there is a bug though with core18 related to snapd transition and hotplug; serial-port hotplug slot doesn't pass sanitization because of "if slot.Snap.Type != snap.TypeOS && slot.Snap.Type != snap.TypeGadget" check
[16:00] <pedronis> ah
[16:00] <mvo> cachio: nice
[16:01] <mvo> pstolowski: ha! good catch
[16:01] <ijohnson> pedronis: posted as https://forum.snapcraft.io/t/gadget-slots-for-devices-that-dont-exist/11278
[16:01] <pedronis> thx
[16:01] <pedronis> pstolowski: does this come from the base declaration or so something else?
[16:02] <pedronis> I thought we made core mean snapd or core at that level
[16:03]  * cachio lunch
[16:04] <pstolowski> pedronis: no, we have a few helpers (sanitizeSlotReservedForOSOrGadget, sanitizeSlotReservedForOS...) that various interfaces call in their sanitize methods, they check SlotInfo.Snap.Type
[16:05] <pedronis> ah, I think we should drop those if I understand things correctly
[16:05] <pedronis> that job is done by the base declaration now
[16:05] <pstolowski> pedronis: hmm, interesting
[16:05] <Chipaca> ok, I'm going offline, ttfn ttyl
[16:06] <pstolowski> pedronis: right, slot-snap-type: in base decl does that
[16:06] <pedronis> yes
[16:06] <pedronis> I mean there might be reason to keep them
[16:06] <pstolowski> pedronis: does it treat "snapd" special though?
[16:06] <pedronis> yes
[16:06] <pedronis> as I said there is code to make core mean (core or snapd)
[16:07] <pedronis> you can find it in policy I think
[16:07] <pedronis> we should maybe sanitize that at some point but is not trivial
[16:07] <pedronis> I mean switch to something like system instead of core
[16:09] <pstolowski> pedronis: i don't see a point in keeping these helpers anymore then
[16:10] <pstolowski> or they should special-case "snapd" if we want to keep them for a while
[16:17] <pedronis> pstolowski: that might be a smaller change?
[16:17] <pedronis> for now
[16:17] <pedronis> not sure
[16:21] <pstolowski> pedronis: around 12 interface files call them, but then over 80 test files are affected too (because of common interface). the change should be pretty mechanical though, as long as base declarations for them are complete in that regard
[16:23] <pstolowski> pedronis: for 2.39 though might be better to make a simple fix in the helpers, and then a followup which removes them all
[16:24] <pedronis> pstolowski: yes
[16:24] <pstolowski> ok, will do
[16:33] <pstolowski> ok, i've a tentative fix, need to test it on pi3 though to see if that's the only issue, will do that tomorrow morning
[16:38] <mup> PR snapd#6775 closed: devicestate: make Remodel() return a state.Change <Remodel :train:> <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/6775>
[16:39] <mvo> 6776 is now a very simple review :)
[16:52] <mup> PR snapcraft#2556 closed: cli: snapcraft promote <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2556>
[18:17] <mup> PR snapd#6820 closed: snap-confine: improve error when running on a not /home homedir <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/6820>
[18:26] <mup> PR snapd#6840 closed: gadget: fix handling of positioning constrains for structures of MBR role <Gadget update> <Simple 😃> <Created by bboozzoo> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/6840>
[18:27] <mup> PR snapd#6828 closed: many: use a fake assertion model in the device contexts for tests <Remodel :train:> <Created by pedronis> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/6828>
[20:14] <cachio> zyga, hey this is interesting https://paste.ubuntu.com/p/tG5MmWSH8n/
[20:14] <cachio> base snaps mounted after snap remove
[20:14] <cachio> in the tests
[20:36] <mup> PR snapd#6841 opened: overlord: make changes conflict with remodel <Created by pedronis> <https://github.com/snapcore/snapd/pull/6841>
[20:44] <cachio> zyga, I already fixed the issue
[21:07] <mup> PR snapd#6842 opened: tests: fix how the base snap are deleted when there are multiple to deleted on reset <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/6842>
[22:20] <mup> PR snapcraft#2559 closed: manifest: expose snapcraft-started-at <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2559>
[22:23] <mup> PR snapd#6843 opened: tests: avoid removing snaps which are cached to speed up the prepare on boards <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/6843>


[12:40] <stickupkid> achilleasa, bundle diff and charmhub charms https://github.com/juju/juju/pull/12318
[12:58] <achilleasa> stickupkid: so the charmAdaptor is in fact a BundleResolverFactoryFactoryInvoker ;-)
[12:58] <stickupkid> yeah, I think that charmAdaptor can die soon'ish
[12:59] <stickupkid> i'd rather model dependencies closer to where they're run, but it is what it is
[13:18] <achilleasa> stickupkid: got some comments on ^^
[14:11] <stickupkid> achilleasa, done
[14:16] <achilleasa> stickupkid: I am looking into store/charmadapter.go. Would it be possible to have two adaptors (one for V3+ and one for older API versions) and instantiate the appropriate one from the diff code where you already check the Charm API version?
[14:16] <stickupkid> ho?
[14:16] <achilleasa> sure
[16:22] <stickupkid> achilleasa, https://github.com/juju/juju/pull/12318 <-- updated
[16:22] <stickupkid> that was fun...
[16:27] <achilleasa> stickupkid: got 2 meetings back to back, can look again in ~1h
[16:27] <stickupkid> achilleasa, maybe
[16:27] <stickupkid> achilleasa, of course, i'll pick it up tomorrow morning
[16:27] <stickupkid> :p