[06:21] <flocculant> knome: ok - I'm happy with that now I've proved to myself it works like you said it would :p
[06:22] <flocculant> !team | I've removed the image tests from the tracker now - people can see that we have a bootable iso at http://dev.xubuntu.org/#tab-qa
[06:22] <flocculant> meh
[06:23] <Unit193> Eh?  No more image tests?
[06:24] <flocculant> Unit193: it was 1 test which was just the image boot test - the other's are still there
[06:24] <flocculant> low tea count sentence that was 
[06:24] <Unit193> I see.
[06:25] <flocculant> s/image tests/image boot test 
[06:25] <flocculant> :)
[06:44] <dkessel> flexiondotorg: regarding raspberry pi xubuntu images for testing - do you build images regularly? or just for releases?
[06:45] <flocculant> dkessel: morning :)
[06:45] <dkessel> just checking that i would not set up stuff that already exists ;) i have already built images using the script
[06:45] <dkessel> morning flocculant !
[07:54] <flexiondotorg> dkessel, Mostly for releases, but sometimes if there is good reason to update. Like adding Pi 3 support to the 15.10 images.
[08:16] <pjotter> Have any changes been made recently regarding samba and/or cifs? I suddenly have all sorts of problems  with file-locking on my clean install of 14.04.4. Especially Libreoffice fails to lock and unlock files on a cifs mounted nas properly.
[08:19] <pjotter> Disabling file locking, either in fstab or in Libreoffice itself solves the problem but leaves the system vulnarable to errors.
[10:46] <bluesabre> flocculant: the thunar test cases look fine to me... and yup what an annoying bug :D
[11:40] <flocculant> bluesabre: indeed ... you want me to have the "i in $(seq 1 10); do touch "$i.txt"; done" bnits in there too? 
[11:41] <flocculant> or have seperate testcases - easy to do 2 
[11:47] <flocculant> bnits being code for bits 
[12:36] <knome> awesome
[12:36] <knome> \o/
[12:36] <knome> i have a version of the tracker that can update work items internally
[12:39] <knome> and updating is as easy as - double click a row, change stuff and press enter
[12:39] <knome> or esc to cancel
[15:02] <ochosi> knome: weee
[16:20] <flocculant> knome: nice :)
[16:21] <flocculant> does it update LP at the same time? 
[16:38] <nairwolf> Hi flocculant ;) I've seen your bug report : https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1577540
[16:38] <ubottu> Launchpad bug 1577540 in ubiquity (Ubuntu Yakkety) "ubi-console-setup failing on yakkety images" [Undecided,Confirmed]
[16:39] <nairwolf> It's weird that I blocked you the installation
[16:39] <nairwolf> Because I could continue the installation yesterday
[16:43] <flocculant> nairwolf: I could have continued too - didn't because I wanted the syslog
[16:47] <nairwolf> oh, ok ;)
[17:15] <flocculant> bluesabre: almost as boring writing these as it will be to run them ...
[17:30] <flocculant> bluesabre: ok - written 2, not live on tracker yet - nor merged, could you have a look at them before I do > http://bazaar.launchpad.net/~flocculant/ubuntu-manual-tests/Thunar/revision/339?start_revid=339
[17:30] <flocculant> thanks :)
[17:57] <knome> flocculant, no, my vision is that we basically ignore LP for the blueprints in the future...
[18:40] <flocculant> knome: mmm 
[18:41] <flocculant> not so sure about reinventing a wheel
[18:42] <flocculant> and how will this vision of yours deal with external things - like Launchpad? 
[18:44] <flocculant> hi akxwi-dave 
[18:44] <akxwi-dave> evening
[21:07] <knome> flocculant, bugs can be attached to the tracker as you can attach them to the blueprints
[21:08] <knome> flocculant, and believe me - this isn't really reinventing the wheel - this is doing some of the work ourself to make sure we can do what we want with the data
[21:08] <flocculant> knome: ok - you knew what I meant then :p
[21:08] <knome> or tbe, they can't be - yet
[21:08] <flocculant> knome: ack - just donning the devil's advocate hat here ;)
[21:08] <knome> i haven't implemented any "add" functions yet
[21:09] <knome> but it's more or less trivial once i go there...
[21:10] <flocculant> slickymaster: sent you and Dave (cc'd knome) mail about it now
[21:12] <slickymaster> seeing it now, flocculant 
[21:12] <slickymaster> and evening knome 
[21:12] <knome> hello slickymaster 
[21:13] <flocculant> knome: bah - meant to say that ... 
[21:13] <knome> np
[21:14] <slickymaster> fine by me
[21:14] <slickymaster> I'll look see at expresso time, before leaving to work
[21:14] <slickymaster> + and
[21:14] <flocculant> well
[21:14] <flocculant> if that's before I do it ... 
[21:15] <slickymaster> exactly, if it's unconfirmed, I'll do it
[21:15] <slickymaster> if not, I'll just have my expresso
[21:15] <flocculant> :)
[21:16] <knome> it's espresso btw
[21:16] <knome> :P
[21:16] <flocculant> lol
[21:17] <slickymaster> well, over here it's expresso :P
[21:19] <flocculant> well - love the company and all that :)
[21:19] <flocculant> night night
[21:19] <knome> night flocculant 
[21:20] <slickymaster> night flocculant 
[21:40] <ochosi> meh, ubuntu 16.04's kernel broke my wifi :'(
[21:40] <Unit193> Oh?
[21:40] <ochosi> older kernel in 16.04 worked, but 4.4.0-21 is evil
[21:40] <ochosi> (-18 worked)
[21:41] <genii> You have some home-compiled wifi driver or something?
[21:41] <ochosi> genii: no, broadcom
[21:41] <Unit193> ochosi: Oh, garcon, xfce4-appfinder, -taskmanager, git xfconf and git tumbler are the only ones ported to gdbus/gtk3, right?
[21:41] <ochosi> https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1572659
[21:41] <ubottu> Launchpad bug 1572659 in bcmwl (Ubuntu) "bcmwl driver does not work with kernel 4.4.0-21 when secure boot enabled" [Undecided,Confirmed]
[21:41] <ochosi> Unit193: no, there are several panel plugins now too
[21:41] <Unit193> Hah, secure boot strikes again! :P
[21:42] <ochosi> unless you're looking for the combination of gdbus/gtk3
[21:42] <Unit193> ochosi: Yeah, didn't list those because boring. :P
[21:42] <ochosi> well then at least the power-manager is missing
[21:43] <Unit193> Ah right, OK.
[22:15] <ochosi> anyway, disabled stupid secure boot and now things are fine again..
[22:17] <Unit193> ochosi: You see my comments about the nice broken xfconf port?  I don't know who 'ali' is so can't ping.
[22:29] <Unit193> slickymaster: No, but FYI copied the functional packages from unit193/xfce4-gtk3 to xubuntu-dev/
[22:30] <slickymaster> hmmm url Unit193, please
[22:32] <Unit193> https://launchpad.net/~xubuntu-dev/+archive/ubuntu/xfce4-gtk3/+packages this one?
[22:32] <Unit193> (This is my personal tracker: https://sigma.unit193.net/~unit193/docs/xfce4.14.html )
[22:33] <slickymaster> ok
[22:33] <slickymaster> thanks for the heads up
[22:33] <Unit193> It's upstream stuff, not ours yet though.
[22:34] <slickymaster> they build successfully but they haven't been published
[22:35] <slickymaster> is that why you say they're still not ours?
[22:37] <Unit193> No I just copied them from my PPA.
[22:37] <slickymaster> got it
[22:41] <bluesabre> evening all
[22:42] <Unit193> Howdy, bluesabre.
[22:44] <slickymaster> hey bluesabre 
[22:46] <bluesabre> hey Unit193 slickymaster
[22:52] <bluesabre> flocculant: those test cases look good (http://bazaar.launchpad.net/~flocculant/ubuntu-manual-tests/Thunar/revision/339?start_revid=339)
[23:06] <flocculant> bluesabre: ok - thanks for looking - I'll get those self-approved on to the tracker then :p
[23:08] <Unit193> bluesabre: FWIW, testing the gtk/gdbus stuff then moving it to the team PPA.
[23:09] <Unit193> So port more and we'll fill it up. :D
[23:15] <flocculant> bluesabre: all done on tracker now, I guess the next thing is either get people to test and report the fails and wait for something to land and retest
[23:15] <flocculant> or wait then test