[01:48] <bluesabre> evening all
[01:48] <bluesabre> pleia2: need a hand with anything?
[06:31] <flocculant> https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1572400/comments/2
[06:33] <flocculant> bluesabre: given that we're not going to replace thunar with something else the day before release - or maybe never - we're going to have to include those patches
[06:34] <flocculant> if we can't get them in in time for tomorrow - then I think we should seriously consider not releasing on Thursday and getting help making sure we have patched thunar in image before we release
[06:40] <Unit193> It's in the queue.
[06:40] <flocculant> k
[06:41] <flocculant> not that it fixes the problem - just alleviates it a bit
[06:42] <flocculant> Unit193: got a link or something?
[06:42] <flocculant> only places I know to look are CI and excuses :(
[06:43] <flocculant> probably cos I don't know enough about packaging ...
[06:43] <Unit193> http://launchpadlibrarian.net/254608952/thunar_1.6.10-2ubuntu1_source.changes
[06:48] <flocculant> mmm - meant something more like https://launchpad.net/ubuntu/+source/xubuntu-default-settings/16.04.6
[06:49] <Unit193> It's not accepted yet.
[06:50] <flocculant> ok
[07:14] <flocculant> Unit193: is that lplibrarian thing the one I need to try and chivvy -release with?
[07:19] <Unit193> https://launchpad.net/ubuntu/xenial/+queue?queue_state=1&queue_text=thunar ?
[07:20] <Unit193> 1572400 too?
[08:23] <dkessel> does anybody else have "mouse cursor often disappears after locking screen" in xenial?
[08:25] <dkessel> (on hardware, which might matter...)
[08:36] <knome> dkessel, blinks for me occasionally on intel GPU laptop
[08:37] <knome> dkessel, and once or twice it has disappeared for the login
[08:39] <akxwi-dave> nope... did a big test last week on the locking and hibernating on my thinkpad and everything was fine,, (Nvidia gpu)
[08:40] <knome> never happened to me on the nvidia gpu desktop with proprietary drivers either
[08:40] <akxwi-dave> although, i did notice last night that my menu icon disappeared once, but re-appear when i hovered over it..  just going thru the bug emails as I'm sure i saw someone report that.. and if so.. gunna check it out
[08:41] <knome> note: i'm still running both wily, but since the bug is the same, i think the data is relevant
[08:41] <dkessel> knome: i have it on intel, too. i even needed to switch to vt1 and back multiple times yesterday to get the cursor back.
[08:41] <knome> mhm
[08:42] <knome> i don't think i've ever completely lost the cursor on the login screen though
[08:42] <dkessel> akxwi-dave: that menu icon redraw bug is known.  it was mentioned here one or two days ago i think
[08:42] <dkessel> knome: no, i only loose it on the desktop, not on the login screen.
[08:42] <knome> yeah
[08:42] <knome> i just log out and in
[08:42] <dkessel> and only since some days....
[08:42] <knome> hmm, weird
[08:42] <knome> you're a late adopter of the bug then :P
[08:43] <akxwi-dave> ahhh.. thats maybe where I saw it then.. wierd thing is I've had xenial installed as main on lappy since december and never had it before
[08:43] <akxwi-dave> :-)
[08:44] <akxwi-dave> well Jan actually..
[08:45] <knome> cheater! :)
[08:47] <akxwi-dave> my hard drive died on it so had to rebuild... took 15.10 and updateed with a early build of xenial...
[08:47] <knome> nnope, still a cheater :P
[08:48] <akxwi-dave> sorry...
[08:48] <knome> it's ok
[08:48] <akxwi-dave> i just couldnt help it..
[08:48] <akxwi-dave> i had to have it asap..
[08:48] <knome> you can do 100 tests to compensate this
[08:48] <akxwi-dave> yes boss..
[08:49] <knome> ;)
[08:50] <akxwi-dave> but in all seriousness.. it has ran beautifully on the laptop..  hell of a lot better than earlier releases or other distro's
[08:51] <knome> happy to hear that :)
[08:51] <knome> ...even if i have no idea why
[08:51] <akxwi-dave> same here...
[08:53] <akxwi-dave> saveing up to get a decent ssd for the lappy..  i have an old 80 gig one that i did some tests on.. from post screen to login in 2 seconds with xenial on ssd
[08:53] <knome> yep
[08:53] <knome> i need an SSD for the desktop
[08:53] <knome> in all seriousness i need a new desktop though
[08:53] <knome> but an SSD would give me something with a bit less
[08:54] <knome> and i'm still dreaming of a mini-pc, need to wait for a bit for them to become a bit more powerful
[08:56] <akxwi-dave> snap.. but until they do a powerful one with gaming quality gpu.. it will be my self build in an Antec 900 case..
[08:57] <knome> i don't exactly need gaming quality GPU, but i'd rather still see something else than an integrated one..
[08:57] <knome> there's one mini-pc where you can plug in some cards
[09:03] <akxwi-dave> i also have one of these which are smallish but again intergrated gpu.. its only dual core but reasonably fast..https://www.google.co.uk/search?q=lenovo+m73&espv=2&biw=1920&bih=993&source=lnms&tbm=isch&sa=X&ved=0ahUKEwjNop_F7ZzMAhUGOhoKHfbqBS0Q_AUIBygC#imgrc=eKkD7YRBvfhD_M%3A
[09:03] <akxwi-dave> in fact the power brick is almost bigger that the pc
[09:04] <knome> ah
[09:04] <akxwi-dave> its a fault i have,, never get rid of old hardware.. you just never know when they coem in handy
[09:05] <knome> lol
[09:05] <knome> i used to do that
[09:05] <knome> well, i still have my old shuttle case with some parts
[09:05] <knome> too bad the PSU's were so bad on those
[09:05] <knome> other than that though, i'm pretty much living on actual hardware only
[09:06] <knome> no need for a rented storage space:P
[09:06] <akxwi-dave> blast from the past.. :-) i know what you mean.. had one myself until I put 14.04 on it and gave it to a friend to act as a media centre for him.
[09:06] <flocculant> dkessel: cursor loss after suspend is on rlease note - if it affects just locking guess we need to sya so
[09:06] <akxwi-dave> :-)
[09:07] <akxwi-dave> morning flocculant
[09:07] <flocculant> hi
[09:07] <knome> i've been thinking that once i get the new pc, i'll take a plunge and get a new PSU, return some parts from the desktop to that and make it a gaming pc for the living room
[09:07] <flocculant> akxwi-dave: just popped in - popping right back out again :)
[09:07] <knome> and by gaming PC i don't mean a powerful rig.. i mean something to play dos games on :P :P
[09:08] <akxwi-dave> ... I've got old dos floppy images of Elite, Dungeonmaster and Turbo Pascal if you wan em.. :-)
[09:08] <flocculant> bug 1568604
[09:09] <knome> akxwi-dave, nah, i have my own ;)
[09:09] <knome> not of those though
[09:09] <akxwi-dave> lol
[09:34] <knome> flocculant, i would probably list dropping of gtk themes rather in the "known issues" section :/
[09:35] <knome> or at least i wouldn't call it a "highlight" of the release
[10:02] <bluesabre> flocculant: accepted https://launchpad.net/ubuntu/+source/thunar/1.6.10-2ubuntu1
[10:13] <bluesabre> 06:12	<bluesabre>	infinity: is there any way we can get https://launchpad.net/ubuntu/+source/thunar/1.6.10-2ubuntu1 out of proposed before the full respin? :-)
[10:13] <bluesabre> 06:12	<infinity>	bluesabre: It's on the way.
[10:13] <bluesabre> flocculant: ^
[10:50] <flocculant> knome: I assume you're talking about x.org
[10:50] <flocculant> bluesabre: \o/
[10:51] <flocculant> makes me feel a bit better about it :)
[10:53] <flocculant> knome: I just knocked the x.org draft up from release note - didn't do much else
[10:55] <flocculant> bluesabre: I guess that the existing thunar bugs will get fix release ? in which case we should start a new one to have something for the 'proper' fix later?
[10:55] <bluesabre> flocculant: I did not mark them to auto-fix since we know they don't
[10:55] <flocculant> oh cool
[10:56] <flocculant> I'll make comments on the release notes about the patches and stuff then
[10:58] <flocculant> dkessel: but you def have intel?
[10:59] <knome> flocculant, yeah, indeed
[10:59] <dkessel> flocculant: yup. i have intel + nvidia hybrid, but i know that intel is active, and not nvidia
[10:59] <flocculant> dkessel: cool thanks :)
[10:59] <flocculant> knome: then yup - not a highlight :D
[11:05] <knome> figured out and edited the draft a bit
[11:05] <flocculant> bluesabre: if you could check the thunar note on release note before tomorrow to make sure I'm not lying please :)
[11:05] <flocculant> knome: cheers :)
[11:05]  * flocculant has a butchers ...
[11:06] <knome> ;)
[11:06] <bluesabre> flocculant: "ameliorate" -- fancy!
[11:06] <flocculant> \o/
[11:07] <bluesabre> flocculant: other than that, looks good
[11:07] <flocculant> k - I'll do similar on x.org then :)
[11:09] <flocculant> also changed the cursor lock wording in both
[11:12] <flocculant> bluesabre: I'll leave adding comments to bugs to you :)
[11:13] <flocculant> bug 1572400 can probably be marked as a dupe of one of the other ones
[11:22] <flocculant> and thunar update lands here
[11:28] <bluesabre> flocculant: will take a look tonight
[11:28] <bluesabre> bbl
[11:30] <flocculant> bluesabre: okey doke - I'll try and be about later tonight ;)
[11:30] <flocculant> off again now
[17:19] <Nairwolf> hi ;) I've just seen new wallpapers from the contest ! It's a great choice ;)
[17:34] <flocculant> Nairwolf: :)
[17:43] <flocculant> bluesabre: given that camera's disabled - any need for it on release note?
[17:44] <flocculant> also - if you want to use your mugshot/catfish release notes let me know (or change them yourself)
[19:57] <pavlushka> can I be able to upgrade from beta to final release?
[19:58] <flocculant> pavlushka: have you not been updating when prompted?
[19:59] <pavlushka> flocculant: yes, every time upgrading after updating
[20:00] <flocculant> then you'll have everything
[20:00] <pavlushka> flocculant: thanks a lot, I mean a lot!!!! :)
[20:01] <flocculant> that's ok
[20:01] <flocculant> better to ask today than tomorrow
[20:02] <flocculant> tomorrow I'll be grrr about anything that's not about iso and testing ;)
[20:03] <pavlushka> I am saved then, whew!
[20:03] <davmor2> flocculant: welcome to my world ;)
[20:03] <flocculant> davmor2: :)
[20:03] <pavlushka> Hello davmor2!
[20:04] <davmor2> hello
[20:04] <flocculant> davmor2: I don't like saying "I really really don't care" to people much - but will :D
[20:04] <pavlushka> davmor2: you know I typed the whole nick for you!! ;P
[20:04] <flocculant> just patiently waiting for this respin now
[20:04] <flocculant> we had some late landing things - -release were all super stars for us :)
[20:05] <davmor2> flocculant: well to be fair I think it just dawned on them that the bugs we posted for beta 1 and final beta actually needed fixing, so it's been all hands on deck to get them fixed
[20:06] <davmor2> flocculant: so pain in the arse yes, but if we weren't so good at doing what we do we wouldn't need all these respins
[20:06] <flocculant> which one?
[20:06] <flocculant> and LTS is always so much worse anyway
[20:07] <flocculant> oh buggar ... support for how long?
[20:08] <davmor2> flocculant: one upgrade issue fixed, swap space fixed, oem installer fixed, snappy fixed, mokutils fixed (mostly), and the list goes on
[20:09] <flocculant> oh well oem we don't test - so never much know those issues
[20:09] <flocculant> though I *do* notice them sometimes
[20:09] <davmor2> flocculant: pretty important for lts though :)
[20:10] <flocculant> well for those who claim to make sure it works yes
[20:10] <davmor2> flocculant: so anyway motto of the story we did good :)
[20:10] <flocculant> we have had discussions in the past about it - but not sure of the need
[20:10] <flocculant> davmor2: for sure :)
[20:11] <davmor2> flocculant: and users will never know all the trials and tribulations :)
[20:11] <flocculant> I saw the mokutil fix - checked what I had on our release notes to check progress
[20:11] <flocculant> davmor2: always the way ;)
[20:12] <flocculant> and the swap one too
[20:12] <Unit193> ...What if I don't care about snappy? :3
[20:12] <flocculant> s/I/we
[20:12] <flocculant> :p
[20:12] <davmor2> Unit193: then we have to beat you repeatedly till you do ;) then don't use it no harm :)
[20:13] <flocculant> davmor2: except (afaik) it's been forced on our 'hardly anything installs' core thing ;)
[20:13] <Unit193> davmor2: Actually, to be honest I'm just a bit peeved that it was forced into Core, but yeah don't really plan to.  May poke at it once, buuut. :P
[20:14] <Nairwolf> swap space fixed ? yeah !
[20:14] <knome> davmor2, but Unit193 has a big polearm in his cave, it hurts if he beats you back!
[20:15] <davmor2> knome: haha
[20:21] <davmor2> Unit193, flocculant; so it might prove useful for user within the next two years if people like spotify and steam create and update and maintain their apps as snaps, even if you don't personally like it
[20:22] <Unit193> Right, which is fine for -desktop.
[20:22] <flocculant> davmor2: don't get me wrong on snaps
[20:22] <flocculant> our core is a really basic setup
[20:23] <flocculant> if people want anything - they install it
[20:23] <flocculant> even a browser
[20:23] <Unit193> We're just saying "A time and a place", -core doesn't even have a browser or gnome-software. :P
[20:23] <Nairwolf> flocculant: I'm afraid to tell you that I can't run the option "install xubuntu" from the last final version....
[20:23] <Nairwolf> I've made "check disk" and it said me there is no errors...
[20:23] <Nairwolf> I think my usb keys are weird...
[20:23] <davmor2> Nairwolf: it isn't the final version yet
[20:24] <flocculant> Nairwolf: what are you talking about?
[20:24] <flocculant> the image?
[20:24] <Nairwolf> yes, the image
[20:24] <Nairwolf> xenial final
[20:24] <flocculant> if so - bunch of stuff going on - waiting on a respin
[20:25] <flocculant> Nairwolf: so your 'Install Xubuntu' is from the Try/Install dialogue?
[20:25] <flocculant> if so yes - drops you to the live desktop
[20:27] <Nairwolf> yes, that's right flocculant ;)
[20:27] <flocculant> :)
[20:27] <flocculant> known issue for 2 daYS AT LEAST
[20:27] <Nairwolf> so the option "Install Xubuntu" doesn't work ? You need to chose first "Try Xubuntu" and then install
[20:27] <flocculant> oops
[20:27] <Nairwolf> ok
[20:28] <flocculant> Nairwolf: also - that stuff we can't fix - always good to grab an Ubuntu iso and check there if possible
[20:28] <flocculant> then we can say phew ... Canonical will fix that one :D
[20:29] <Nairwolf> ok
[20:29] <Nairwolf> and where I can find known issues ?
[20:29] <Nairwolf> if you choose to develop wiki.xubuntu.org, it should be writen here, no ?
[20:30] <knome> Nairwolf, depends what you are going to fill it with
[20:30] <Nairwolf> known issues for example
[20:31] <knome> don't, we're tracking them in the release notes in the ubuntu wiki
[20:31] <knome> and on this channel if they are very temporary
[20:32] <flocculant> Nairwolf: once this cycle is done (assuming the Tech Lead doesn't complain) then next cycle the 'release note' will be a rolling one more or less the whole cycle
[20:33] <flocculant> so current issues should - unless they are here and gone very quickly - be visible there
[20:33] <flocculant> knome: talking of wiki.x - made a start on the qa iso page
[20:33] <knome> nice
[20:33] <Nairwolf> okay that's nice
[20:33] <Nairwolf> I've found the page : https://wiki.ubuntu.com/XenialXerus/FinalRelease/Xubuntu
[20:34] <flocculant> yes
[20:34] <flocculant> Nairwolf: next cycle - that will be what the rolling note will look like
[20:34] <flocculant> EXCEPT
[20:34] <Nairwolf> I wanted to say that sometimes, it's not really easy to find what you want ton wiki.ubuntu.com. Maybe you're familiar with this wiki, it's easy, but the search engine isn't really efficient
[20:34] <flocculant> I am not updating changelog often
[20:34] <knome> flocculant, damn, we really either want that menu out of there or make it link to sensible places :D
[20:35] <knome> (fwiw, i'm completely ok with it being gone too)
[20:35] <flocculant> menu?
[20:35] <Nairwolf> that's ok flocculant for the changelog
[20:35] <knome> flocculant, the toolbox banner
[20:35] <flocculant> knome: oh yes
[20:35] <flocculant> yea - caught up in the end :p
[20:35]  * Unit193 tries dropping desktop-common from the seed...
[20:36] <knome> Unit193, make sure it doesn't fall on your toes
[20:36] <flocculant> knome: I think last time I checked it was only 1 or 2 didn't redirect
[20:36] <knome> flocculant, ack, but here's why i think we should rather drop it:
[20:37] <knome> while the release notes are more technical than announcement, it's still mostly a user-facing page; they should be pointed to the most important "start here" pages only (if even those)
[20:37] <Nairwolf> ok, new iso, I will try again
[20:37] <knome> we don't want to sidetrack them to old team reports from the release notes :X
[20:38] <flocculant> nope
[20:38] <flocculant> knome: well easy enough to lose header from notes
[20:38] <knome> yeah
[20:38] <knome> one more thing i can (try to) do if you want
[20:38] <flocculant> and I agree they should be really *just* about what they are
[20:38] <knome> is move the xubuntu logo next to the release name
[20:38] <knome> that would be fancy
[20:39] <flocculant> knome: move it in FRONT of release name
[20:39] <flocculant> and
[20:39] <knome> yep, front indeed :P
[20:39] <flocculant> move that stanza ABOVE the wiki warning
[20:39] <knome> ack
[20:39] <knome> i'll try...
[20:39] <flocculant> so I don't screw it up in the morning :p
[20:39] <knome> hahah
[20:40] <flocculant> lose the banner as well - good with that
[20:40] <flocculant> knome if you can make the logo link to x.org ...
[20:40] <flocculant> and extra cookie :D
[20:40] <knome> mmm
[20:41] <flocculant> \o/
[20:41] <flocculant> a thoughtful mmm :)
[20:41] <Nairwolf> flocculant: ok, it can be installed easily
[20:42] <flocculant> from the desktop icon yes
[20:43] <Nairwolf> no, from the try/install window
[20:44] <flocculant> Nairwolf: you just said it failed?
[20:46] <knome> flocculant, you owe me 2 cookies
[20:46] <Nairwolf> firstly, I said I failed to install Xerial Final by clicking on "Install Xubuntu"
[20:46] <knome> ...once the page saves
[20:46] <Nairwolf> Now, I've succeded
[20:46] <flocculant> knome: impossible
[20:46] <Nairwolf> BUT... did you say (you or someone else) that the swap bug was solved ?
[20:47] <flocculant> I only offered 1 :D
[20:47] <knome> flocculant, and done :d
[20:47] <Nairwolf> Because I've met it again
[20:47] <knome> oh, you said extra cookie
[20:47] <flocculant> davmor2: ^^ swap bug met Nairwolf
[20:47] <flocculant> knome: bah :|
[20:47] <knome> :D
[20:47] <knome> anyway, not sure i copied all the commenty stuff correctly
[20:48] <knome> you might want to check you are okay with the order
[20:48] <knome> the logo is that one table line
[20:48] <knome> ..you'll figure out
[20:48] <davmor2> flocculant: yes it will be fixed in this iso that has been spun up yet
[20:48] <flocculant> knome: I will happily get your address and send you 2 cookies - I might send 3 so you can all have 1 each :)
[20:48] <knome> haha
[20:48] <flocculant> davmor2: oh yea ... sorry matey
[20:48] <knome> you think i'm going to share my hard earned cookies with others?
[20:49] <flocculant> Nairwolf: we're waiting a respin with some fixes in it - including that one
[20:49] <flocculant> knome: yea ofc - sharing is caring ;)
[20:49] <davmor2> Nairwolf: stop testing the broken iso, there will be a new one later that has all the fixes that were worked on today, those fix most of the issue in the image you currently have :)
[20:50] <flocculant> davmor2: thanks :)
[20:51] <Nairwolf> ok, davmor2. Badly, it's too late for me to wait the new build. I will try it tomorrow.
[20:51] <Nairwolf> good night guys
[20:51] <flocculant> Nairwolf: thanks for your help :)
[20:55] <knome> didn't ochosi say the thunar bugs are likely related to glib changing?
[20:55] <knome> we could probably mention that, to make people a bit less angry at thunar
[20:55]  * knome thinks damage management
[20:58] <Unit193> krytarik: Hah!  Fun times in the seed: http://paste.openstack.org/show/ig8AuYEZofhOjUqYuDmS/ :D
[21:00] <krytarik> Unit193: LOL - #fail.
[21:05] <flocculant> knome: you about still?
[21:05] <knome> yup
[21:05] <flocculant> can you double check a rapid send mail to -dev please :)
[21:06] <knome> sure
[21:07] <flocculant> sent
[21:07] <flocculant> it's 1/2/3 I need to ensure
[21:07] <flocculant> pleia2: you about for a last minute social thing?
[21:08] <knome> flocculant, put this in a pad and i'll edit there so you can copy easier
[21:08] <pleia2> flocculant: if you give me something to copy/paste, yes :)
[21:09] <knome> we need another active admin for g+/fb
[21:09]  * knome is not volunteering
[21:09]  * knome only touches fb with a long pole
[21:09] <knome> and even then only from the API side
[21:10] <davmor2> knome: man that is just wrong, I mean at least call him a Tall Pole ;)
[21:10] <knome> flocculant, too late, http://pad.ubuntu.com/J7xon1C6Yz
[21:10] <knome> no edits done yet though
[21:10] <flocculant> oke
[21:11] <flocculant> pleia2: yup - just writing the thing now ...
[21:11] <flocculant> kind of trying to get ahead of -release for a thing or 2
[21:13] <knome> sigh linebreaks
[21:13] <flocculant> knome: just so you know - it was the content of 1 -3 not how it looks : )
[21:14] <Unit193> krytarik: Feature: no-follow-recommends also seems to be a no-op.
[21:14] <knome> flocculant, i know but i can't also do anything about wanting it to look good :D
[21:14] <flocculant> ha ha
[21:14] <knome> isn't 2) really 1b) ?
[21:14] <knome> or
[21:14] <knome> we can put it another way
[21:15] <flocculant> no - really want people to see things I'm lokking for
[21:16] <flocculant> a very specific group would see 2
[21:17] <Unit193> germinate simply isn't flexible enough to do this..
[21:23] <knome> flocculant, happy with it
[21:24] <knome> wait
[21:24] <knome> that one paragraph is still odd
[21:24] <flocculant> ....
[21:24] <knome> ok, goof
[21:24] <knome> hhh
[21:24] <knome> good
[21:24] <knome> if you sent, was no biggie :P
[21:26] <flocculant> pleia2 knome - late social shouts > https://lists.ubuntu.com/archives/xubuntu-devel/2016-April/011133.html
[21:26] <flocculant> frankly - don't care what text you use - but "really urgent last call" in the title works :)
[21:26] <flocculant> thanks and apologies pleia2 :)
[21:27] <knome> and tweeted
[21:27] <knome> https://twitter.com/Xubuntu/status/722899426050596869
[21:27] <flocculant> thanks knome :)
[21:28] <knome> np
[21:28] <flocculant> can't we just support Xubuntu for 1 day?
[21:28] <knome> hah
[21:28] <flocculant> :D
[21:29] <flocculant> my only real issue now is making sure we can SRU thunar fixes
[21:29] <flocculant> if we can't then it makes a mockery of LTS
[21:29] <knome> why couldn'y we?
[21:29] <knome> t too
[21:29] <flocculant> *opinion*
[21:29] <bluesabre> We definitely can
[21:30] <flocculant> bluesabre: hey :)
[21:30] <knome> *onion*
[21:30] <bluesabre> Yay
[21:30] <flocculant> bluesabre: I thought we could - just making QA position completely clear *before* I end up ticking yes :D
[21:30] <knome> hoora
[21:31] <knome> +y
[21:31] <flocculant> bluesabre: and you should get mrsBluesabre to read -offtopic :p
[21:31] <flocculant> bluesabre: Qa getting excuses in early
[21:33] <bluesabre> bbiab
[21:33] <flocculant> bluesabre: or http://www.omgubuntu.co.uk/?s=xubuntu
[21:33] <flocculant> check out the image ;)
[21:33] <pleia2> posted
[21:34] <flocculant> pleia2: awesome - thanks :)
[21:35] <knome> bbluesabiabre
[21:35] <pleia2> the My Nut squirrel is my new desktop image <3
[21:36] <pleia2> knome: if you're still logged in, want to retweet this? https://twitter.com/omgubuntu/status/722722043771297793
[21:37] <knome> pleia2, done
[21:38] <pleia2> ty
[21:39] <flocculant> pleia2: I like the "My Nut by bluesabreWife is the best" especially when " doesn't represent my current work2 -offtopic comment :)
[21:40] <knome> flocculant, she should know better nuts are always fashionable :d
[21:40] <flocculant> :)
[21:41] <flocculant> at least for 49.9999999999% of the population :)
[21:42] <knome> hah
[21:42] <bluesabre> back now
[21:42] <Unit193> bluesabre: ...Is it worth it to try and get them to move bluez and snapd out of desktop-common?
[21:43] <bluesabre> Unit193: could be
[21:43] <flocculant> welcome back bluesabre - I actually appear to be smiling now - cat run off
[21:43] <flocculant> I'd +1 moving bluetooth out
[21:43] <Unit193> Maybe if we can get Lubuntu on board too. :P
[21:44] <flocculant> if I've got to installl a browser - why would I want that
[21:44] <flocculant> Unit193: maybe Mate too
[21:44] <Unit193> Mate wants snapd at least.
[21:44] <flocculant> they're looking at a core thing too
[21:44] <flocculant> mmm
[21:44] <flocculant> bit ambivalent there
[21:45] <flocculant> maybe snapd is useful in core
[21:45] <flocculant> install 'a thing' alone - not loads of 'fluff'
[21:45] <flocculant> *shrug*
[21:46]  * flocculant could of course have the wrong idea on snap and be takne in by adverts
[22:14] <flocculant> knome: added last para
[22:24] <flocculant> !team | assume smoketesting is all cool - please test thunar for us, thanks :)
[22:32]  * genii cheers
[22:34]  * flocculant joins in  cos something built :)
[22:58] <bluesabre> huzzah!
[23:01] <flocculant> ha ha
[23:02] <flocculant> bluesabre: I WILL chek
[23:02] <bluesabre> flocculant is starting the release festivities early
[23:03]  * flocculant is starting the QA can't do sod all now festivities now thing
[23:03] <flocculant> blaming
[23:04] <flocculant> ummm ...
[23:04] <flocculant> website \o/
[23:08] <bluesabre> safe target
[23:08] <flocculant> yup
[23:09] <knome> :P
[23:09] <flocculant> bluesabre: anyway - quilck look at wiki note please, change catfish/mugshot if you want - off now
[23:19] <bluesabre> flocculant: will do
[23:20] <flocculant> bluesabre: ack - sleep for me
[23:20] <bluesabre> nighty
[23:21] <flocculant> bluesabre- ochosi I know that when -release start shouting for acks it's going to be me who has to trigger it
[23:22] <flocculant> so can I please have either a +1 or -1 from bluesabre AND ochosi before I  do that :)
[23:23] <flocculant> I'm pretty much +/-0 atm :)
[23:25] <flocculant> bluesabre ochosi ha - see - release now lol
[23:37] <flocculant> bluesabre: we're about 5 hours ahead here
[23:37] <bluesabre> I'm always a few hours behind ;)
[23:38] <flocculant> bluesabre: I'm cool to tick the box if needed as long as I have an ack from one of you or ochosi
[23:38] <bluesabre> will be sure to at least say go for it
[23:38] <flocculant> ok cool
[23:39] <flocculant> bluesabre: so whoever see's t the request I guess - does it :)
[23:39] <flocculant> ochosi: ^^
[23:42] <bluesabre> sounds good to me
[23:48] <slickymaster> flocculant, are the images on the tracker the ones you want tested?
[23:50] <krytarik> slickymaster: Yep.
[23:50] <slickymaster> ok, just going to download them and hit the bed


[10:36] <cjwatson> Could I have a review of a small build system fix?  https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/382990
[10:41] <cjwatson> (Might fix CSS on qastaging, not sure if it's the only thing)
[10:45] <cjwatson> Not to mention CSS on staging and API on (qa)staging, I think
[10:45] <cjwatson> ilasc: ^- maybe?
[10:46] <ilasc> cjwatson: looking at it as we speak :)
[10:47] <cjwatson> Ta
[10:48] <ilasc> cjwatson: looks good to me
[10:48] <cjwatson> Thanks
[10:55] <ilasc> cjwatson: on the Edit OCI Push Rules screen, looks like with the current approach (replace credentials part of the rule with a link to the appropriate OCIRegistryCredentials:+edit view - screenshot on page 12) if User has no Push Rule defined there is no way for user to edit their Credentials
[10:55] <ilasc> might need to do something different than just the link per rule
[10:57] <cjwatson> ilasc: Aren't we still planning a tab on the person's index page too?
[11:01] <ilasc> yes, that's still there (Display Creds only), allow Edit Creds there was part of the first version, but we said we want to keep Edit Creds with Edit rules. Are you thinking go back to enabling Edit Creds on the Person's index page ? (that's what I'm thinking at the moment)
[11:03] <cjwatson> ilasc: I was expecting both
[11:03] <cjwatson> credentials views accessible from your index page, and also the ability to edit credentials directly from a push rule if they're linked to one
[11:04] <cjwatson> I don't think I intended to say that credentials editing should *only* be accessible from push rules
[11:04] <cjwatson> if I implied that, I apologise
[11:04] <ilasc> ok, makes sense to do it that way
[11:04]  * ilasc implements both
[11:05] <cjwatson> Should just be a matter of the list view having some edit links
[14:12] <cjwatson> https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/383000 (Fix determination of bug target roles)
[14:13] <pappacena> This is what you were discussing on #launchpad some minutes ago?
[14:13] <cjwatson> Yep
[14:14] <pappacena> Awesome. Let me review it
[14:23] <cjwatson> Thanks
[14:23] <cjwatson> And I must owe you at least one review, so let's see
[14:25] <pappacena> hahaha! Thanks! :)
[14:47] <cjwatson> pappacena: Speaking of which, were you planning on landing https://code.launchpad.net/~pappacena/launchpad/+git/launchpad/+merge/382233 ?  Looks like it's ready to go
[14:51] <pappacena> Is the DB patch applied to production already?
[14:51] <cjwatson> It is
[14:51] <pappacena> Ok! I'll top-approve it. Thanks
[15:05] <cjwatson> pappacena: Conflict again, by the looks of it
[15:06] <pappacena> Yep. Merging master into the branch here.
[17:58] <SpecialK|Canon> pappacena: (Implicit) question in Freenode/#ubuntu-release ("whoever is accepting NEW packages") - is that something your archive admin audit work should be able to answer, out of interest?
[17:59] <pappacena> uhm, I'll join this channel. Anyway, I guess this information is present at the archive admin audit trail, yes.
[18:02] <SpecialK|Canon> pappacena: How could I view that for a given package?
[18:04] <pappacena> At the publishing history page of that package (like https://launchpad.net/ubuntu/+source/man-db/+publishinghistory)
[18:06] <pappacena> At the main page of the package, it shows as "Publishing details" when you click on the arrows at the bottom part too
[18:06] <pappacena> like this https://usercontent.irccloud-cdn.com/file/67n2jGD1/image.png
[18:11] <SpecialK|Canon> pappacena: Ok thanks will take a look!
[19:06] <cjwatson> In this case it would actually be on the queue pages (https://launchpad.net/ubuntu/groovy/+queue)
[19:35] <cjwatson> pappacena: FWIW the error on buildbot is easily reproducible locally with bin/test -vvc --layer=AppServerLayer
[19:35] <cjwatson> ValueError: In version devel, IOCIRecipeBuildRequestEntry_devel.builds is a collection of IOCIRecipeBuild, but version devel of the web service does not publish IOCIRecipeBuild as an entry. (It may not be published at all.)
[19:35] <cjwatson> is the key bit
[19:36] <cjwatson> i.e. essentially the problem is that IOCIRecipeBuildRequest.builds is exported but the interface type that it's exporting a collection of isn't
[19:37] <pappacena> Ah, got it. I'll take a look in a minute
[19:37] <pappacena> Thanks!
[19:41] <cjwatson> wgrant: Could you DB-review https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/383021 please?


[00:58] <twb> lilstevie: have you seen this? http://paste.ubuntu.com/770683/
[00:58] <twb> "fakeroot, while creating message channels: Function not implemented This may be due to a lack of SYSV IPC support."
[00:59] <lilstevie> that I have not
[00:59] <lilstevie> twb: also, LP0 fixed
[00:59] <twb> coo
[00:59] <twb> ...l
[01:00] <twb> lilstevie: does "fakeroot pwd" work for you?
[01:01] <infinity> I would hope so...
[01:01] <twb> WTF have I done
[01:01]  * lilstevie doesn't even have fakeroot installed
[01:02] <twb> lilstevie: it's mainly used when building packages
[01:02] <lilstevie> yeah I know
[01:02] <lilstevie> I have it on the trim
[01:02] <lilstevie> where I build my packages
[01:02] <infinity> Who's sending me a trim for Christmas?
[01:02] <infinity> Anyone? :)
[01:02]  * infinity hears crickets.
[01:02] <lilstevie> lol
[01:04] <twb> lilstevie: it works if I update-alternatives and change it to use fakeroot-tcp instead
[01:05] <lilstevie> lol
[01:05] <twb> Which is Bad Juju because IIRC that breaks something else
[01:05] <lilstevie> I currentlly have no wifi on my tf101 so I cant install fakeroot to tell you my result
[01:05] <twb> k
[01:57] <twb> lilstevie: FYI, guy next to me can reproduce fakeroot-sysv issue on his tf101
[01:59] <lilstevie> ok
[02:01] <infinity> twb: Kernel built without sysvipc?
[02:01] <infinity> CONFIG_SYSVIPC=y
[02:01] <infinity> CONFIG_SYSVIPC_SYSCTL=y
[02:02] <infinity> CONFIG_SYSVIPC_COMPAT=y
[02:02] <infinity> Probably want all of those for fakeroot to not be a sad panda.
[02:03] <twb> infinity: I didn't build the kernel
[02:03]  * twb points at lilstevie!
[02:03] <twb> scary monkey style
[02:04] <twb> There's no /boot/config either :-(
[02:04] <doko> \o/ it's done: https://launchpad.net/builders:  armhf	11	empty
[02:04] <twb> Aha, /proc/config.gz tho
[02:04] <twb> Yep, sysvipc is off.  FAIL.
[02:04] <lilstevie> not set
[02:04] <lilstevie> will fix later
[02:04] <twb> No rush, fakeroot-tcp works for now
[02:05] <lilstevie> I really don't give an f right now :)
[02:05] <infinity> doko: \o/
[02:05] <twb> I will have to ring up your girlfriend and tell her bad things about you so she leaves you and you have more time for work
[02:05] <infinity> doko: I'll see if there are any obvious things I can unsnag tomorrow.  And keep an eye on stuff here and there while I'm on VAC.
[02:06] <lilstevie> twb: lol. I don't give an f because I am working on something else on the project right now so that would acomplish nothing
[02:07] <twb> Okey dokey
[02:07]  * twb puts down the phone
[02:08] <twb> No more underground boxing matches with baby seal pups for you
[05:23] <twb> 16:20 <twb> mikef: battery stats per hour, gave it power just after penultimate entry http://paste.debian.net/149276/
[05:24] <twb> So the TF101 (running Ubuntu) has a discharge rate of 12% to 14% per hour (of the onboard battery).  That works out to be about 7.14 hours of life.  The dock is half as much battery again, so that comes to about 10.7 hours of life with my current config.
[05:24] <twb> *without* sleeping or screen blanking on inactivity
[05:25] <twb> brightness is at 157/255 (default at boot time)
[05:33] <twb> lilstevie: ^^
[05:33] <twb> Anybody riced up stuff to save power on the TF yet?  powertop doesn't look to be very helpfu
[05:36] <lilstevie> twb: my average consumption is 10% per hour
[05:36] <twb> The only thing it recommends that I can see is /proc/sys/vm/dirty_writeback_centisecs
[05:36] <twb> Which is 6000 and it thinks 1500 is better, but it isn't
[05:36] <twb> lilstevie: hum
[05:37] <twb> lilstevie: well, I am using an offboard keyboard, and wifi
[05:38] <twb> http://www.lesswatts.org/tips/disks.php et al
[05:38] <lilstevie> I get 19hours 40 with no power management
[05:38] <lilstevie> wifi on
[05:38] <lilstevie> but using the dock keyboard
[05:38] <twb> Be interesting to know what else is different
[05:39] <lilstevie> with LP0 suspend to ram though :p
[05:39] <twb> There is autosuspend for the keyboard power, but if you turn it on, the keyboard won't wake from sleep :-(
[05:39] <lilstevie> you probably don't want to know
[05:40] <lilstevie> also my wake is based off the dock "lid open switch"
[05:40] <twb> Surely the 19.6 hrs doesn't count the hours that it's suspended to ram
[05:40] <twb> In which case suspend to ramdoesn't matter
[05:41] <lilstevie> 19.6hours was without LP0
[05:42] <twb> The dock battery is half the size of the tablet battery, right?
[05:42] <lilstevie> no
[05:42] <lilstevie> same size
[05:42] <lilstevie> identical
[05:42] <twb> Oh, OK
[05:42] <twb> In that case I should get ~14 hours atm
[05:43] <lilstevie> last 4.4h used 1% battery
[05:43] <lilstevie> :)
[05:45] <lilstevie> only issue with LP0 I can see at the moment is the battery does not charge from the dock while in that mode
[05:45] <twb> so you think it's like a car, where the "empty" mark is WAY above the actual empty level?
[05:46] <lilstevie> the dock does not drain past 3%
[05:46] <twb> Well yeah, not counting that
[05:46] <lilstevie> and not "way above"
[05:46] <lilstevie> but still a little bit above
[05:47] <lilstevie> just not all batterys are created equal
[05:48] <lilstevie> batteries even
[05:56] <twb> Is irqbalance useful on tf?
[05:57] <twb> Also for some reason my load average never drops below 1
[06:01] <cmcmanis> Greetings ubuntu-arm, is it a known bug that the current build has EXT4 journal corruption bugs?
[06:01] <twb> cmcmanis: current build on what platform?
[06:01] <cmcmanis> sorry pandaboard
[06:01] <cmcmanis> Got a new Pandaboard-ES and put the current Ubuntu on it
[06:02] <cmcmanis> It corrupts the EXt4 journal and then I have to reboot. I can reproduce by just dding from /dev/zero to a file
[06:04] <infinity> cmcmanis: Define "current Ubuntu".
[06:05] <infinity> cmcmanis: But I have no such issues on my Panda.  Is this running on an SD card?
[06:05] <infinity> cmcmanis: (If so, I'd suspect your SD is dying)
[06:05] <cmcmanis> sorry, the build that is referenced off the pandaboard.org site one sec
[06:06] <cmcmanis> ubuntu-11.10-preinstalled-server-armel+omap4.img.gz
[06:06] <cmcmanis> SD is brand new, kingston class 10
[06:06] <infinity> New doesn't mean much. :/
[06:07] <infinity> I can tell you for sure that a fresh install of oneiric shows no such weirdness on any Pandas here.
[06:07] <cmcmanis> fair enough
[06:08] <infinity> I actually only have on card I've never managed to kill.  And I suspect that's more luck than anything else.
[06:08] <infinity> SD and random access don't really get along.
[06:08] <cmcmanis> true that
[06:08] <infinity> (If you have a USB HDD for your Panda, I'd recomend grabbing a netboot image, stuffing that on an SD, and installing to a hard drive)
[06:09] <cmcmanis> Hmmm that is an interesting idea.
[06:16] <twb> 17:02 <cmcmanis> It corrupts the EXt4 journal and then I have to reboot. I can reproduce by just dding from /dev/zero to a file
[06:16] <twb> That sounds to me more like the filesystem is bigger than the disk or something
[06:16] <twb> Or the blocks where teh journal lives aer toast
[06:17] <lilstevie> twb: it would be the latter rather than the former
[06:17] <lilstevie> cause unless the SD card is <2GB that wouldn't happen
[06:17] <cmcmanis> aye, that would cause it but I've checked the partition multiple times, and can read and write both the first and last blocks (tested using dd)
[06:18] <twb> I just prefer to blame users, not hw :P
[06:18] <cmcmanis> Its and 8g card btw
[06:18] <cmcmanis> It came in a twin pack and I'm putting Android ICS on the other one we'll see if it has a similar issue
[09:22]  * ogra_ scratches head about the eglibc build
[09:25] <ogra_> i wonder why the same package is built on two different builders
[09:36] <ppisati> ogra_: becasue you keep hammering those poor builders and they are revolting againt you now! :)
[09:37] <ogra_> haha
[09:37] <ppisati> ogra_: stop harassing the builders!
[09:37] <ogra_> the hammering seems to have stopped last night
[09:37] <ogra_> queue is largely empty
[09:43] <ppisati> ogra_: btw, did you sort out the ac100 "non booting kernel" problem? i read it could be toolchain related
[10:18] <ogra_> ppisati, well, in the package we have there are some issues with devices having hynix RAM, the micron ones seem to work fine ... with the new checkout that was rolled with gcc 4.6.2 it seems everything is broken
[10:26] <ppisati> ogra_: crap
[10:26] <ogra_> yeah
[13:17] <ogra> hmm, lubuntu-desktop isnt installable yet on armhf
[14:56] <ogra_> ************* REMINDER ARM meeting in #ubuntu-meeting in 5min ******************
[14:57] <infinity> But I don't wanna go to school today mom.
[14:57] <lilstevie> heh
[14:58]  * ogra_ swings the cane
[14:58] <ogra_> :)
[14:59] <doko> infinity, could you run a check for universe packages not present on armhf, but present on armel?
[15:00] <infinity> suit-diff should work...
[15:00] <infinity> suite, too.
[15:00] <infinity> But meeting time.
[15:03] <infinity> doko: http://lucifer.0c3.net/~adconrad/universe-armel-armhf_differences
[21:07] <kyleN> my oneiric sys has now hung twice, even after scheduler


[19:54] <thebwt> Funny, I mainly watch the channel from 8-5 (work time) I guess most people don't once-off an IRC room in those hours


[16:13] <nigelb> Wait, what.
[16:14] <nigelb> I just got an email, that at first claims to be from bac. But it's spam.
[16:14] <nigelb> But very creatively titled "For nigel"