[21:07] <bkerensa> MarkDude: what up
[21:12] <MarkDude> Planning for trip to Stumptown
[21:14]  * MarkDude has details set for big party being held at bkerensa house
[21:16] <philipballew_> Ill bring my tux statue bkerensa !!!
[21:16] <philipballew_> Well all dance around it
[21:16] <MarkDude> Yay
[21:16] <MarkDude> Linux cult rocks!
[21:18] <pleia2> I might be seeing you guys up there afterall
[21:18] <pleia2> I seem to have won an award :)
[21:19] <pleia2> need to talk to my boss though, coming back from one vacation to say "yeah, I need some time off next week too" is fun
[21:21] <scientes> oooo, where is party?
[21:21] <scientes> oh, up north
[21:22] <MarkDude> pleia2, you won the Open Source award?
[21:23]  * MarkDude was pretty sure you would win
[21:23] <MarkDude> scientes, party at bkerensa house
[21:23] <MarkDude> Even tho he objects
[21:23] <MarkDude> :D
[21:23] <philipballew_> prteey much like a Nobel price
[21:23] <pleia2> MarkDude: "an" open source award, yeah (I assume there are multiple :))
[21:23] <pleia2> very excited
[21:23] <philipballew_> *pretty
[21:23] <pleia2> and I'm in an airport about to get on a flight
[21:24] <pleia2> I was like "omg omg omg MJ!!!"
[21:24] <pleia2> then I emailed my boss
[21:24]  * scientes is always up for a party, even one coerced out of the host ;)
[21:25]  * MarkDude had someone nominate me for the OSCON Community Award, for me protesting the Distro thing
[21:25] <MarkDude> KNew I would not win.
[21:26] <scientes> MarkDude, what distro thing?
[21:26] <MarkDude> Then pleia2 's name was brought up as likely winner
[21:26] <MarkDude> long story scientes
[21:26]  * MarkDude will type or tell you another time
[21:26] <MarkDude> :)
[21:26] <pleia2> I am quite honored :)
[21:27] <pleia2> bkerensa: btw, I went into a bookstore this week to find the issue of Ubuntu User with your article, but they still had issue 12 out :\
[21:28] <pleia2> ok, airplane #1 now
[21:28] <MarkDude> Gareth, still wins for having his pic on magazine last year
[21:28] <MarkDude> Altgho..... being a SPEAKER at OSCON rocks bkerensa
[21:28] <MarkDude> Congrats
[21:48] <bkerensa> pleia2: yeah I check every Barnes and Noble in Portland and no go =/ I need to e-mail Rikki and see whats up
[21:48] <bkerensa> pleia2: I nominated you ^
[22:01] <bkerensa> MarkDude: easy for you to say :P now I have to come up with a talk since its official and all http://www.oscon.com/oscon2012/public/schedule/speaker/120025
[22:01] <darthrobot> Title: [Speaker: Benjamin Kerensa: OSCON 2012 - O'Reilly Conferences, July 16 - 20, 2012, Portland, OR]
[22:01] <bkerensa> I get roped into to much :P
[22:01]  * MarkDude will be there toask questions
[22:01] <MarkDude> stuff not relevant to your talk also
[22:01] <MarkDude> :D
[22:01] <MarkDude> Do you like pie?
[22:01] <MarkDude> That sorta thing
[22:02] <MarkDude> Tell me about your childhood, etc
[22:05] <bkerensa> What
[22:05] <bkerensa> I have to answer questions too?
[22:05] <bkerensa> I thought it was just a talk :P
[22:06] <bkerensa> MarkDude: soare you confirmed coming? What day do you land and are u bring phillip?
[22:06] <MarkDude> Drving there
[22:06] <MarkDude> talking with people going *right now*
[22:07] <MarkDude> will need to get back to you with details
[22:07] <MarkDude> afk
[22:07] <bkerensa> kk
[22:14] <philipballew_> bkerensa, I imagine with him ill be there thursday or friday, but if he and I dont work out im gonna come up Thursday via greyhound
[22:15] <philipballew_> So all is good in the hood
[22:15] <bkerensa> philipballew_: Ahh of this week right?
[22:15] <philipballew_> I think, cls is this weekend correct?
[22:16] <bkerensa> philipballew_: well good news is that I might be able to give you my 3 day pass + expo if all goes good
[22:16] <bkerensa> but either way you are covered for booth access and expo
[22:16] <philipballew_> Nice!
[22:16] <bkerensa> since I am now speaking I think I get a speaker pass which is all access
[22:16] <bkerensa> :D
[22:16] <bkerensa> Im kind of stoked because the Speakers Lounge is nice
[22:17] <philipballew_> I imagine, the scale speakers one had free food.
[22:17] <philipballew_> got your talk ready yet?
[22:18] <philipballew_> So I should give my pass to someone else then?
[22:18] <bkerensa> LOL
[22:18] <bkerensa> philipballew_: not till I know for sure
[22:18] <bkerensa> :D
[22:18] <bkerensa> philipballew_: nope... I just got told I was speaking this morning... I wasnt planning on it
[22:18] <bkerensa> :D
[22:19] <philipballew_> I trust a few sleepless nights will pump out a solid speech
[22:21] <philipballew_> If am trying to arange a friend from college to give me and kiilhead17 a tour of portland
[22:21] <bkerensa> philipballew_: I have a t-shirt waitingfor u :D
[22:21] <bkerensa> philipballew_: yeah he is worried about his motel... his work put him in a slum
[22:21] <bkerensa> =/
[22:22] <philipballew_> He speaks English well I think
[22:23] <philipballew_> Hopefully they do not take advantage of him. Here in Placer county, people are always takin advantage of, and laughed at when they don't speak English
[22:24] <bkerensa> philipballew_: he speaks it very colorfully ;)
[22:24] <philipballew_> Thats what I recall. I might offer to help him get around and what not
[22:25] <philipballew_> Im pretty good on portland slang after watching Portlandia
[22:26] <bkerensa> philipballew_: good stuff.... I will be somewhere between working.. speaking and sleeping
[22:26] <bkerensa> and maybe some boozing if I find time
[22:27] <philipballew_> I say a minifridge at the booth
[22:27] <philipballew_> you can store all the booz you want!
[22:29] <bkerensa> philipballew_: Bring sticky notes
[22:30] <bkerensa> philipballew_: we will cover Fedora's booth while they are boozing with 10,000 sticky notes that say nice things about Ubuntu
[22:30] <bkerensa> :D
[22:30] <bkerensa> MarkDude: ^ :P
[22:30] <philipballew_> I have 100's actually!
[22:32] <MarkDude> Hmmmm
[22:33] <MarkDude> So will you just say sumthin nice about the Ubuntu drivers 10,00 times
[22:33] <MarkDude> ?
[22:33] <MarkDude> :D
[22:34] <MarkDude> Or just write *awesome Community* that many times?
[22:35] <philipballew_> Maybe ill see if I can snag some ubuntu cola bkerensa and bring it upp
[22:35] <philipballew_> *up
[22:36] <bkerensa> MarkDude: How they just work with every bit of hardware I have?
[22:36] <bkerensa> :D
[22:36] <MarkDude> drivers
[22:37] <bkerensa> MarkDude: What drivers does Ubuntu lack? :)
[22:37] <MarkDude> I figure a debate would be fair, as long as we dont go down the no win Gome 3 / Unity comparison XD
[22:37] <MarkDude> Uh
[22:37] <philipballew_> we have more correct?
[22:37] <MarkDude> bkerensa,  I mean Ubuntu has AWESOME drivers
[22:37] <MarkDude> I mean stellar
[22:38] <philipballew_> I say we have a chair fight at oscon
[22:38] <MarkDude> And that other Distros should not try to compare there
[22:38] <bkerensa> LOL
[22:38] <MarkDude> Since they would LOSE
[22:38] <bkerensa> LOL
[22:38] <bkerensa> MarkDude: so you come up on Friday yes?
[22:38]  * MarkDude was thinking *bar knuckle boxing*
[22:38] <MarkDude> bare
[22:39]  * MarkDude has fake handlebar mustache just for this purpose
[22:39] <bkerensa> MarkDude: you should use fiverrr.... I would pay you to make me a weird video :D
[22:39] <MarkDude> And has also been praciticing his boxing skills with all my servants
[22:39] <MarkDude> Weird?
[22:39] <MarkDude> You mean my specialty?
[22:39] <MarkDude> :D
[22:40] <bkerensa> with cats
[22:40] <bkerensa> and a recliner
[22:40] <bkerensa> :D
[22:40] <MarkDude> Yep
[22:40] <MarkDude> the outakes from my video
[22:40] <MarkDude> Were better than the actual video


[12:18] <papo> hello, I need some help to change  deps from kdelibs4 to kdelibs4c2 in order to install k3b in breezy. Do you know can I do it?
[12:47] <uniq> not recommended.
[12:47] <uniq> you'll have to rebuild.
[12:47] <uniq> if you rebuild you can change it in the debian/control file.
[03:01] <hunger> Is there any estimation on when the gcc transition will be done?
[03:01] <Riddell> hunger: it's pretty well done already
[03:02] <hunger> I am sure all of you are busy with it and doing their best... I am just curious.
[03:02] <hunger> Riddell: Great!
[03:03] <hunger> I was asking since none of the apps I had deleted to get the new g++ has returned during this week.
[03:04] <hunger> Many are back already, of course.
[03:04] <Riddell> hunger: which are you after?
[03:04] <hunger> Riddell: k3b, some of the koffice things, etc.
[03:05] <hunger> Riddell: and of course I do want to reinstall kubuntu-desktop;-)
[03:05] <hunger> (which is stopped by k3b and ooo-kde IIRC)
[03:05] <Riddell> hunger: k3b is being taken care of by amu, koffice is waiting on kofficce 1.4 to be released
[03:05] <hunger> Riddell: Oh, thanks for that info!
[03:06] <Riddell> I don't do ooo-kde, not sure who does openoffice, but maybe we should just include koffice on the CD
[03:06] <hunger> I do not like OOo too much, I'd love that change.
[03:07] <Riddell> hunger: are you a regular koffice user?
[03:07] <hunger> Riddell: But I am afraid I'd be rather alone with my joy;-)
[03:07] <hunger> Riddell: I am no regular Whatever-office user;-)
[03:07] <Riddell> me neither
[03:08] <hunger> Riddell: But if I need to use some office thing then I try to use koffice... which usually fails for some reason so that I end up OOo anyway.
[03:09] <hunger> By the way: Is somebody looking into the cpu-freq display bug in the ksysguard applet?
[03:09] <Riddell> not that I know of
[03:12] <motaboy> Hi to all!
[03:13] <hunger> hi motaboy
[03:15] <hunger> Their reaction to ubuntu is somewhat hostile for the biggest part:-(
[03:15] <hunger> I am really amazed how mdz keeps calm on the debian-devel list.
[03:18] <Riddell> is that thread still going on?
[03:29] <hunger> Riddell: It is dieing down.
[03:30] <hunger> Hmm... ksysguardd could use an update to sysfs....
[03:31] <Riddell> might cause trouble for BSD users that
[03:32] <hunger> Riddell: Nope, Linux and BSD use a separate set of scanners anyway.
[03:33] <hunger> It would cause problems for linux 2.4 users.
[03:36] <hunger> Riddell: Suddenly the cpufreq works again!
[03:37] <hunger> No idea what I just did!
[05:44] <froud> anyone care to estimate how many users are currently using kubuntu? :-)
[07:20] <Riddell> uniq: you have oper on #kubuntu
[07:21] <Riddell> anyone else think they can control the #kubuntu mobs?
[07:21] <Riddell> haggai: do you have any special privilages over #kubuntu?  I see you're named as contact
[07:23] <\sh> whats up on kubuntu?
[07:24] <Riddell> nothing, it's just incase we get abuse when no oper is around
[07:50] <froud> Riddell: I will be monitoring #kubuntu closely from now I can help with oper when I am there
[07:51] <froud> Riddell: I just help a 73-year old man upgrade from warty to hoary
[07:51] <froud> cant believe it
[07:51] <froud> amazing
[07:51] <froud> quite insightful as to what he does and does not know
[07:54] <froud> Riddell: the images on www.kubuntu.org/documentation.php are broken
[07:55] <froud> seems you linked to my stage when I was getting reviews
[07:55] <froud> Riddell: can you update the links on that page
[07:56] <froud> Riddell: if you dont have the images I will send them to you
[08:53] <uniq> hi.
[08:53] <uniq> riddell: ok. thanks.
[08:54] <uniq> i'll be away for ~ 1 week from tomorrow.
[10:16] <haggai> Riddell: I have op rights but can't grant them to anyone else - dstone registered the channel
[10:51] <uniq> gnite. up at 0500 CEST to catch a flight..  ugh.
[11:01] <uniq> riddell: new kbandwidth uploaded.


[02:12] <phillw> Hi, who should I 'nag' about comments for a draft replacement for help document?
[02:14] <phillw> nhandler: are you available for a quick chat on the LAMP documentation I did?


[02:47] <duflu> Why is it every time I look, Ubuntu is using a kernel that upstream has end-of-life'd ? :)
[02:47] <duflu> https://www.kernel.org/
[02:48] <duflu> We never seem to be using the long term supported ones
[09:32] <greyback_> alan_g: network dropped, have you a link to the HO?
[09:32] <alan_g> https://plus.google.com/hangouts/_/canonical.com/mir-qtmir?authuser=0
[09:37] <alan_g> tvoss: ^
[09:37] <tvoss> alan_g, ack
[14:07] <kdub> its gotten tricky to be sure whats the source of a CI failure
[14:15] <kdub> hmm, anyone know anything about glmark breaking with abi changes? I've found https://bugs.launchpad.net/mir/+bug/1341490, but what I see seems slightly different
[14:15] <kdub> because i shouldnt be bumping or breaking anything in https://code.launchpad.net/~kdub/mir/multiple-bufferstream-api/+merge/261123
[14:28] <alan_g> kdub: the most recent problem with glmark was that the version of libmirclient8 from 0.12 loaded libmircommon3 but the 0.14 drivers that were loaded also loaded libmircommon4
[14:28] <alan_g> Once 0.13 hit archive that "went away"
[14:31] <kdub> hmm, dunno if thats what i'm hitting in this problem
[14:33] <alan_g> I doubt it.
[15:30] <AlbertA> kdub: another MP is also hitting the same glMark issue... https://code.launchpad.net/~raof/mir/input-methods-can-specify-foreign-parents/+merge/258001
[15:31] <kdub> AlbertA, right, and that one adds another function to the mir_surface api too....
[16:03] <kdub> so the glmark definitely is a loading mirclient8 when mirclient9 should be loaded
[16:03] <kdub> issue
[16:05] <AlbertA> kdub: oh is it loading libmirclient8 then using the built libmirprotobuf.so.0 from the cI build?
[16:06] <kdub> possibly, have been able to get a backtrace
[16:06] <kdub> http://pastebin.ubuntu.com/11690920/
[16:08] <AlbertA> kdub: but in any case, do we even want a libmirclient8 talking to a server released with libmirclient9?
[16:09] <kdub> probably not
[16:09] <kdub> maybe we need to bump the protobuf number?
[16:09] <AlbertA> kdub: seems like we need to disable glmark for now since we bumped client ABI until release...
[16:10] <kdub> AlbertA, because we don't build glmark against the code that's being landed?
[16:11] <AlbertA> kdub: right. it's just a package dep
[16:13] <AlbertA> kdub: or rather I guess it's just a package installed by the mir mako runner scripts
[16:23] <kdub> hmmm
[16:28] <AlbertA> kdub: so looking at RAOF's branch - protobuf seems like the only suspect to cause the glmark crash...
[16:30] <AlbertA> probably stack protobuf objects that are now a different size in the new libmirprotobuf.so.0....
[16:31] <AlbertA> do we have libmirprotobuf as an .so to share between client and server?
[16:32] <AlbertA> it does seem like we need to bump the protobuf ABI then....
[16:33] <AlbertA> or at least when we bump libmirclient ABI
[16:33] <AlbertA> and there's been a protobuf change
[16:46] <kdub> AlbertA, right, that seems sensible to me too
[17:16] <racarr> whee...all my tests passing now and working on device for touch stream rewriter...just code cleanup now.
[17:17] <alan_g> You enjoy cleaning up code?
[17:23] <racarr> alan_g: I feel like you are kind of pointlessly mean to me sometimes
[17:23] <racarr> (e.g. above)
[17:24] <racarr> sorry I'm sure you consider it as having intent
[17:24] <racarr> and are trying to communicate something to me
[17:24] <alan_g> racarr: actually I'm glad you are not tempted to skip the "clean up" bit.
[17:24] <racarr> but I don't really appreciate it when it's phrased like that
[17:25] <alan_g> I was just amused by your phrasing
[17:25] <alan_g> Sorry that it read differently
[17:25] <racarr> lol I understand sorry.....
[17:25] <racarr> no, my fault lol
[17:26] <conyoo> o_O
[17:28] <alan_g> no, no, my fault. I was careless in my phrasing.
[17:29] <racarr> such is our internet life.
[18:07] <bschaefer> mterry, would deb2snap work on armhf?
[18:07]  * bschaefer only saw x86/x64 libs on it
[18:08]  * bschaefer tests it out
[18:11] <mterry> bschaefer, heyo -- it would work, but you may have to do it inside an armhf machine
[18:11] <mterry> s/may//
[18:12] <bschaefer> mterry, right, its what i was thinking i would have to do
[18:12] <mterry> bschaefer, it *should* work
[18:12] <bschaefer> mterry, as it looks like it does some fun ldd work :)
[18:12] <bschaefer> haha yeah :)
[18:12] <bschaefer> *should* work is usually worth a try
[18:12] <bschaefer> mterry, thanks!
[19:48] <kgunn> mterry: hey before i let the day get away from me....again...i'm going through review comments on my attempt to upload mir snap to store
[19:48] <mterry> kgunn, oooh OK
[19:49] <kgunn> and one question was about the global socket vs user
[19:49] <kgunn> i mean on one hand i guess you could argue it doesn't matter for the type of device
[19:49] <kgunn> e.g. it's probably not gonna have multiple apps
[19:50] <kgunn> but just wondering, was there something troubling about using the var/run/user/*/mir_socket
[19:51] <kgunn> ?
[19:52] <kgunn> mterry: ^
[19:52] <kgunn> or is that just what mir_demos* use...
[19:52] <mterry> kgunn, didn't try it, but I thought compositors were expected to be per-device, not per-user
[19:53] <kgunn> mterry: i guess that is true for a "system compositor"
[19:54] <kgunn> altho in ubuntu touch i think u-s-c is actually per user....?
[19:54] <mterry> kgunn, no even there it's run as root for the whole system
[19:54] <mterry> kgunn, (otherwise it'd be hard to do the split greeter, which runs as a separate user)
[19:54] <mterry> kgunn, unity8 is its own compositor of course (for the user).  But u-s-c is system wide
[19:55] <kgunn> holy crap...just grabbed krillin, it's been on for 3 days idling hardly any battery gone...impressive
[19:55] <mterry> kgunn, I'm .. pleasantly shocked?   :)
[19:55] <kgunn> me too
[19:56] <kgunn> mterry: ok, thanks...i think i've got the ammo to argue that one away now
[19:59] <kgunn> mterry: one last one...i got dinged on confinement, so doing a lot of reading....is it just "work" ? or is there some mystery there....
[19:59] <kgunn> guessing you know from being a snappy dude now :)
[19:59] <mterry> kgunn, can you explain that a bit?
[19:59] <racarr> Lunch!
[20:00] <mterry> kgunn, I can explain the current Mir confinement a bit?  Or are you talking about something else?
[20:00] <kgunn> mterry:  security_template_valid (meta/system-compositor.apparmor)
[20:00] <kgunn> 	(MANUAL REVIEW) 'unconfined' not allowed
[20:00] <kgunn> Why is this running unconfined? Framework services and binaries should also all run under confinement.
[20:01] <mterry> kgunn, ah yes
[20:01] <mterry> kgunn, that was laziness on my part
[20:01] <mterry> kgunn, so just "work"
[20:01] <kgunn> you lazy so and so
[20:01] <mterry> kgunn, there needs to be some investigation on what exactly u-s-c needs
[20:01]  * kgunn keeps reading hoping for a payoff...
[20:01] <mterry> kgunn, so basically that's likely just running it confined and seeing what DENIED comments you get in syslog
[20:02] <mterry> kgunn, and then crafting an apparmor file with exceptions
[20:02] <mterry> kgunn, similar to the apparmor file for clients
[20:02] <kgunn> ok
[20:02] <mterry> kgunn, in meta/framework-policy/
[20:02] <kgunn> mterry: yep...i'm familiar :)
[20:02] <kgunn> i've already made some mods
[20:02] <mterry> kgunn, that one I did put some thought into and worked with jdstrand a bit to tighten it as possible
[20:02] <mterry> kgunn, oh good
[20:03] <mterry> kgunn, I figured it was more important to get that right than worry about the server side of things, which is something we wrote
[20:03] <mterry> kgunn, but I guess the store reviewers/admins didn't see it that way  ;)
[20:03] <kgunn> which btw, are you ok for me to just push changes to snappy-packaging ?....or, should i keep a seperate branch
[20:03] <mterry> kgunn, naw that's fine.  I put it under mir-team so that it could be edited as needed
[20:03]  * kgunn has been known to tear up steele balls with rubber hammers


[08:08] <Unit193> knome: US mirror! \o/
[10:11] <ochosi> Unit193: the us mirror doesn't seem to have vivid images though
[10:12] <Unit193> Yeah, noticed that bit...
[10:29] <bluesabre> yay! awwwww
[12:11] <bluesabre> Unit193: releasing an updated exo this week, re #d-xfce
[12:11] <bluesabre> bbl
[12:11] <ochosi> nice
[12:11] <Unit193> Niiice.
[12:11] <ochosi> and hi and bye bluesabre :)
[12:45] <ochosi> Unit193: hmm, i wonder where we should put these sort of todo's down, the blueprints aren
[12:45] <ochosi> t the right place
[12:45] <ochosi> maybe we should put it on the WIP trello that sean put up
[12:46] <Unit193> That'd work, and man I must be tired.
[12:47] <ochosi> yeah, i have a hard time deciding whether it's late or early for you :p
[12:47] <Unit193> This time, so do I.
[12:48] <ochosi> ok, i put it down there
[12:49] <ochosi> if you can prep the package, i guess bluesabre can upload it
[12:49] <ochosi> but yeah, doesn't have to happen now that you're tired ;)
[12:49] <Unit193> Well, I'd rather the merge than an SRU. :P
[12:50] <ochosi> elfy: i still haven't caught up with all my emails, but i'm planning on replying to all xubuntu related ones tomorrow, incl the QA incentive one, what's your stance on that btw?
[12:50] <Unit193> s/Backport/sru/
[12:50] <ochosi> Unit193: totally agreed :)
[12:50]  * ochosi rephrases
[12:52] <Unit193> Hah. :P
[12:55] <Unit193> !MRE
[12:58] <Unit193> ochosi: Hah, didn't mean you had to rename again. :P
[12:58] <ochosi> sure sure ;)
[12:58] <Unit193> But, that'll help.
[13:28] <micahg> someone need an upload?
[13:28] <Unit193> We're looking to merge xfwm .3 then MRE it to vivid.
[13:29] <micahg> why MRE?
[13:29] <micahg> oh, right, we have that :)
[13:30] <micahg> well, do you want to do the merge?  is bluesabre doing it? should I do it?
[13:31] <Unit193> I was going to later, unless you were good to.
[13:31] <Unit193> Sean is at work.
[13:31] <micahg> do we know if he started it
[13:31] <micahg> do we have an MRE bug already?  it would be trivial for me to do both uploads
[13:31] <Unit193> He hasn't been here for the discussion, so I highly doubt it since it's easy.
[13:38] <micahg> Unit193: if you want to file the MRE bug, I can do the upload
[15:47] <elfy> ochosi: my stance is "I spent hours for little gain"
[16:05] <lderan> will have to help out with QA more
[16:05] <elfy> you helping out wouldn';t have made any difference to that particular thing :D
[16:06] <lderan> maybe :P
[16:07] <elfy> you could have done it - but I would have double checked it - so no gain :)
[16:09] <lderan> fair enough
[16:09] <lderan> time for me to flee work and get started on xubuntu'y dev work this evening \o/
[16:09] <elfy> no slur intended - just one of those things that lead should have done is all
[16:09] <elfy> woohoo
[17:13] <ochosi> elfy: that's not how i see it, but anyway, i'll reply
[17:14] <elfy> yep - it's all rather subjective anyway however we look at it :)
[19:31] <Unit193> Hrm, is the QA trello restricted?
[19:32] <elfy> public viewable
[19:33] <elfy> only people on the 'list' can post
[19:34] <Unit193> Hrm, OK.
[19:34] <elfy> why?
[19:35] <Unit193> Weird, first time I clicked the link about the jenkins fail, I got a "You're logged out", but now it worked.
[19:35] <elfy> ok
[19:36] <elfy> maybe you were doing that while I was editing it just a while back and there's an issue with it
[20:36] <Unit193> micahg: Ah, ochosi assigned bluesabre to that part, at least.
[20:36]  * micahg feels like he's missing some magical tracking place
[20:37] <Unit193> No that was (mostly) all in here, just the note about new xfwm was in #xfce-dev.
[20:38] <micahg> ok, well, please let me know if I need to merge/upload something
[20:43] <ochosi> Unit193, micahg: actually, if either of you wanna work on xfwm4 .3, i totally approve
[20:43] <ochosi> i'm sure sean will use the time to work on/release exo, so please don't hold back
[20:47] <micahg> well, I have the merge ready to upload to wily...
[20:47] <Unit193> https://sigma.unit193.net/source/xfwm4_4.12.3-1ubuntu1.dsc whoops..
[20:48] <micahg> haha
[20:48] <ochosi> :D
[20:49] <micahg> Unit193: should I upload mine or are there other things that need to be fixeD?
[20:49] <Unit193> micahg: None that I know of.
[20:49] <ochosi> oh, also, there were some other releases recently (thunar, xfdesktop) that might be good to go to wily (if they aren't there already)
[20:49] <micahg> ok
[20:49] <ochosi> plus xfburn with gst1.0
[20:50] <Unit193> micahg: I presume you have a link to https://sigma.unit193.net/~unit193/xfce412.html and the much less useful https://sigma.unit193.net/~unit193/xfce.html ?
[20:50] <micahg> nope
[20:50] <micahg> nice :)
[20:51]  * micahg will add more pins
[20:51] <ochosi> Unit193: we should really link to that some place where people can find it
[20:51] <micahg> could probably publish on Ubuntuwire
[20:53] <Unit193> :3
[20:53] <Unit193> micahg: I stole it!
[20:54] <micahg> what did you steal?
[20:54] <Unit193> https://code.launchpad.net/ppa-versions
[20:55] <micahg> haha
[20:55] <micahg> ok, well, let me know how I can help without stepping on toes
[20:55] <Unit193> (And updated it so it'd fine more stuff.)
[20:56] <Unit193> micahg: Hey, however you like at least works for me.
[20:56] <micahg> there's this as well which is nice for Debian: http://pet.alioth.debian.org/
[20:56] <Unit193> I use dmd.
[21:02] <micahg> I can sync diskperf
[21:03] <Unit193> I think a few of those could be, but I didn't check further since we can't access them. :3
[21:04] <micahg> hrm?
[21:06] <micahg> I think we can sync fsguard also
[21:07] <Unit193> xfce4-mpc-plugin too?
[21:08] <Unit193> xfpm, think we're going to drop the tray icon.
[21:08] <micahg> I'll test that next
[21:11] <micahg> yep
[21:11] <micahg> Unit193: want credit for that
[21:12] <Unit193> Sure! :D
[21:13] <Unit193> I need to find a workable meeting for packageset. :3
[21:13] <micahg> sync'd
[21:13] <micahg> and credited
[21:13] <micahg> I won't be at the Monday meeting
[21:14] <Unit193> Right, we talked.  I can't either.
[21:15] <micahg> ok, going back to other things now
[21:16] <ochosi> sorry, was afk there for a bit
[21:16] <ochosi> what got synced/updated/merged exactly now?
[21:17] <ochosi> (and yay, always good to see you guys at work :))
[21:17] <micahg> https://lists.ubuntu.com/archives/wily-changes/2015-May/thread.html
[21:18] <micahg> | tail -n4 :)
[21:19] <ochosi> nice work :)
[21:19] <micahg> sync's are relatively painless, especially when the test builds are quick
[21:20] <ochosi> the MRE for xfwm4 to 15.04 is still up for grabs, right?
[21:21] <micahg> I can do the upload (it's just a backport, but I need the bug number)
[21:23] <ochosi> k, either bluesabre or someone else can file the bugreport tonight or i can work on that tomorrow and whoever does it can then ping you with the bug#
[21:23] <micahg> sure
[21:23] <ochosi> great, thanks a bunch micahg!
[21:24] <micahg> I think i've done more uploads for wily that I have for utopic + vivid
[21:24] <ochosi> :]
[21:24] <micahg> ochosi: np, nice to be useful
[21:24] <ochosi> really good to see you around more again, can't stress that enough
[21:25] <ochosi> i also hope that means your job situation has loosened up a bit
[23:04] <bluesabre> ping ping ping ping
[23:04] <bluesabre> :D
[23:04] <bluesabre> hi everyone!
[23:05] <Unit193> Howdy, bluesabre.  Have fun filing the MRE! :D
[23:05] <bluesabre> oh
[23:05] <bluesabre> bye everyone!
[23:05]  * bluesabre makes his escape
[23:05] <bluesabre> j/k
[23:05] <bluesabre> MRE time, yay
[23:07] <bluesabre> xfwm for vivid, alrighty
[23:12] <Unit193> Suppose someone should pickup the new timeout and eyes plugins...
[23:42] <bluesabre> Unit193: from what I can tell, this should be sufficient... do you agree? http://paste.ubuntu.com/11253336/
[23:44] <Unit193> bluesabre: .2 is already in as a patch, IIRC.
[23:52] <bluesabre> ah, even better


[15:53] <ian_brasil> is it possible to change the screen size in kvm ..i am trying to install to a second hd but it defaults to 1024x768 so the buttons are missing
[15:54] <ian_brasil> i am using the beta mid image - is this solved in the later images?


[16:08] <JoshX> Hi! I have multiple ubuntu 14.04.5LTS systems running on the same hardware with the same kernel producing the same kernel crashes..
[16:09] <JoshX> crashlogs are here: https://pastebin.com/xnGmtLNg and https://pastebin.com/0vQX9fKz for example
[16:10] <JoshX> kernels are  Linux pc7-1428 4.4.0-116-generic #140~14.04.1-Ubuntu SMP Fri Feb 16 09:25:20 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
[16:10] <JoshX> on all systems
[16:10] <JoshX> every time this happens, the machine is under medium IO load, low memory load
[16:11] <JoshX> and after the crash behaves very eratic.. random crashing processes, reboot and shutdown fail
[16:11] <JoshX> so far we've had this on 9 systems running identical hardware and software
[16:12] <JoshX> doing mainly writing ffmpeg -> h264 stream -> pipeline -> to JPG frames to disk (disks are connected via USB in a mirror MD0)
[16:14] <TJ-> JoshX: looks like it could be due to fragmented memory allocations
[16:14] <JoshX> TJ-: is this something I can do anything about?
[16:14] <JoshX> we're running stock 14.04.5LTS with no exciting software on average hardware
[16:15] <JoshX> Intel(R) Core(TM) i7-5550U CPU @ 2.00GHz CPU With 16Gb DDR3L ram
[16:15] <TJ-> JoshX: I'm only guessing, but if the processes are requesting many smaller allocations (I infer due to the strack trace showing compaction_alloc) it's posisble that eventually the kernel cannot create a block large enough for a request
[16:16] <JoshX> I understand, but am i running out of memory or out of large enough fragments?
[16:16] <TJ-> you'll notice the strack trace passes through do_huge_pmd_anonymous, try_to_compact_pages etc
[16:17] <TJ-> so I suspect fragmentation has ended up in a situation where even compaction cannot handle things (possibly there's a bug there that ought not to be as well)
[16:18] <TJ-> I think there are some kernel 'knobs' you can twiddle to influence these things (sysctl)
[16:19] <JoshX> perhaps I can add a PPA and try a upstream/newer/beta kernel?
[16:19] <JoshX> of enable something to produce more/better logging?
[16:19] <JoshX> the crashes are so random I have yet to reproduce them at will
[16:21] <TJ-> JoshX: do they happen after the systems have been working for some time ?
[16:21] <JoshX> well these 2 systems crashed after 200k sec and 400k sec if i see the logs
[16:22] <JoshX> so 2.5 and 4 days or so
[16:22] <JoshX> not too long
[16:22] <TJ-> JoshX: if those processes are fragmenting memory that's about what I'd expect - I wouldn't expect this immediately after boot
[16:23] <JoshX> but we're running some nodejs processes, rabbitmq, ffmpeg
[16:23] <JoshX> and ionotify on file close events
[16:23] <JoshX> on ~40 files / sec
[16:24] <JoshX> so we're handeling tons of IO events on file closes to move files to the right place
[16:24] <JoshX> and we're queuing stuff in rabbitmq..
[16:25] <JoshX> could be erlang/rabbitmq messing things up
[16:25] <JoshX> could be nodejs
[16:25] <JoshX> but the end result is always the same, an unstable machine that is pingable and accessible via ssh
[16:26] <JoshX> but which does not work anymore.. (so monitoring this sucks since all seems normal)
[16:27] <JoshX> can i perform a command on these machines to see how bad fragmentation is at this moment?
[16:28] <JoshX> so I could log things over time and keep a graph or something to see if the problem is slowly getting worse?
[16:29] <TJ-> JoshX: try "echo m > /proc/sysrq-trigger"
[16:29] <TJ-> JoshX: then check dmesg
[16:30] <JoshX> https://pastebin.com/Xu6130pW
[16:30] <TJ-> JoshX: oh, forget that, we have buddy now! "cat /proc/buddyinfo"
[16:30] <JoshX> root@pc7-1428:/var/log# cat /proc/buddyinfo
[16:30] <JoshX> Node 0, zone      DMA      1      1      1      0      2      1      1      0      1      1      3
[16:30] <JoshX> Node 0, zone    DMA32    325    115     59     36     10      8     50     44     26      0      0
[16:31] <JoshX> Node 0, zone   Normal     20     22      4     12      5      3    101     84     44      0      0
[16:31] <JoshX> 'erm..'
[16:31] <JoshX> is this good? bad? :)
[16:32] <TJ-> the numbers are blocks of 4KiB, 8KiB, 16KiB....
[16:33] <TJ-> you might to read the docs in ./Documentation/ directory of the kernel source for the detail of that
[16:33] <JoshX> I have a system in stress test now thats reporting higher numbers
[16:34] <JoshX> root@pc7-1422:~# cat /proc/buddyinfo
[16:34] <JoshX> Node 0, zone      DMA      1      1      1      0      2      1      1      0      1      1      3
[16:34] <JoshX> Node 0, zone    DMA32    283     94     18     16      7     10     10     38     39      2      0
[16:34] <JoshX> Node 0, zone   Normal    209   3879     31      9     11     19     23      7      4     10      1
[16:35] <JoshX> and the memory info from dmesg: https://pastebin.com/q6iZC3Sk
[16:35] <TJ-> you might try adjusting the memory overcommit settings
[16:37] <JoshX> how might I do that?
[17:00] <apw> it seems unreasonable for it to panic like that there