[00:30] <flexiondotorg> How goes the Xubuntu testing?
[00:43] <knome> doesn't look too bad
[00:46] <flexiondotorg> knome, Great. Thanks for letting me know.
[00:49] <knome> ftr, you could have checked that from the ISO tracker yourself :P
[00:55] <Unit193> So about the same as this morning. :D
[00:56] <knome> Unit193, hello darling.
[00:57] <azzenovic> I want to know abt how to access both please 
[00:57] <knome> azzenovic, you'll need a launchpad account
[00:58] <Unit193> https://iso.qa.ubuntu.com/ lists Xubuntu, and links to bugs on there.
[00:58] <knome> azzenovic, http://open.knome.fi/2014/02/23/logging-in-with-ubuntu-one/ for the detailed information on obtaining one
[01:01] <azzenovic> knome, I already have one what shall i do next ?
[01:02] <knome> you can now login to the ISO tracker in the url Unit193 pasted
[01:02] <Unit193> (Typed)
[01:02] <knome> pastyped
[01:02] <knome> typasted
[01:04] <azzenovic> done
[01:05] <knome> do you need further information?
[01:09] <azzenovic> yeah indeed what's the next step ps I am currently installing willy iso 
[01:09] <knome> which ISO is that? beta1? daily?
[01:11] <azzenovic> the one in the daily-live directoy 
[01:12] <knome> ok... well we're currently testing the beta1 release, so that's a bit unideal.
[01:12] <Unit193> zsync.
[01:15] <azzenovic> no prob I will go with beta
[01:16] <knome> ok, then select "Wily Beta 1" from the milestone list
[01:16] <knome> from that page, select "Xubuntu Desktop your_architecture"
[01:16] <knome> and from THAT page, select the test you are willing to run
[01:17] <knome> eg. for amd64 and entire disk install, you end up at http://iso.qa.ubuntu.com/qatracker/milestones/340/builds/100663/testcases/1300/results
[01:17] <knome> that page has all the information on what steps you need to take to run through the test
[01:17] <knome> (yes, it's basically a regular install, but it's good to run with that page open the first few times)
[01:18] <knome> at the end of the page, you have a form to add a test result - do that when you are ready with the installation
[01:20] <azzenovic> ok thx :)
[01:50] <knome> i'm off to bed
[01:51] <knome> nihty
[01:51] <knome> +g
[07:13] <knome> flocculant, also, this is of course the right channel :P
[07:13] <knome> flocculant, another thing: let's talk with lderan about what data we want to pull from the QA trackers
[07:14] <knome> flocculant, he said he'd be willing to hack a bit on the xml-rpc interface so it would be a bit easier to get the data we need
[07:14] <flocculant> ok
[07:14] <knome> and if you didn't notice - there's now a timeline in the tracker
[07:14] <flocculant> I did ;)
[07:14] <knome> goodie
[07:15] <flocculant> is it going to stay as it is though? 
[07:15] <flocculant> I did read you and ochosi - but didn't get any finished thoughts 
[07:15] <knome> i don't know yet
[07:15] <flocculant> eg day or week or month 
[07:16] <knome> improvement ideas welcome :)
[07:16] <flocculant> :)
[07:16] <knome> it's hard to say whether day/week is better in the long run
[07:16] <knome> since the data isn't naturally scattered now
[07:16] <flocculant> I think that day would be a mightnare
[07:16] <knome> yep, probably
[07:17] <knome> it's easy enough to change later
[07:17] <flocculant> and week would (in a cycle) be a possible 26 sections
[07:17] <flocculant> how about biweekly
[07:17] <knome> i don't know
[07:18] <knome> how works within a biweekly schedule
[07:18] <Unit193> knome: Source in git, btw?
[07:18] <knome> Unit193, nah, i'll push it in cvs
[07:18] <Unit193> Ah, even better.
[07:19] <knome> ^ *who
[07:19] <knome> i mean, it doesn't have a natural rhythm for me
[07:19] <knome> one thing i considered was using week numbers relative to the cycle
[07:19] <flocculant> knome: people that think that 26 is too many, 6 is too few and 190 is silly
[07:20] <knome> so week 1 for the first week of cycle - whether that was in april or october
[07:20] <flocculant> week numbers relative is probably a useful starting point
[07:20] <flocculant> and if we are honest about it - week 1 - 8 or so would be pretty empty :D
[07:20] <knome> mhm
[07:21] <knome> then their headers wouldn't appear
[07:21] <knome> same with date
[07:21] <knome> +s
[07:21] <knome> only ones that have content are listed
[07:21] <flocculant> I don't see that as a problem
[07:21] <knome> no, quite the opposite
[07:23] <knome> i was just meaning that it would make the list not 26 sections :)
[07:23] <knome> but say, 18
[07:24] <flocculant> yep 
[07:24] <knome> which is IMO quite ok
[07:24] <knome> i'm fine with 30ish too
[07:25] <flocculant> I guess as long as it lists from current to eons ago I guess it's not really an issue anyway
[07:25] <knome> we currently have 81 items, so that split in 26 would mean >3 per week
[07:25] <knome> well, ultimately it will still be a long list
[07:25] <flocculant> of course
[07:26] <flocculant> a list with 100 headers with one line each would be a pain to parse
[07:26] <knome> sure
[07:26] <knome> ok, another Q
[07:26] <flocculant> so week at minimum imo
[07:27] <knome> do you see a specific use case for this apart from the obvious "let's see how we've done" ?
[07:27] <flocculant> let me ponder that in the kitchen ... 
[07:27] <knome> sure
[07:30] <flocculant> to be blunt - no I don't
[07:31] <knome> ok, so in that case - does it matter if the output is split into weeks?
[07:31] <knome> one thing i can think of is the monthly team reports
[07:31] <flocculant> I wouldn't be that interested in knowing that foo was done *then* all I'd really be interested in knowing is that it was
[07:31] <knome> but then we didn't do those since april
[07:32] <knome> and the whole system is falling apart - not many teams are doing them altogether
[07:32] <flocculant> right
[07:32] <knome> and finally,
[07:32] <knome> if need be, i can simply add a dropdown for the different choices...
[07:33] <knome> but let's not overcomplicate it if people are happy with one view :)
[07:33] <flocculant> yea
[07:33] <flocculant> one point here
[07:33] <knome> sure
[07:34] <flocculant> *if* the thing is how many rather than what - could the data not be added to the burndown?
[07:34] <flocculant> then you could see at a glance all graphy things in one place
[07:34] <knome> well, it is in the burndown essentially...
[07:34] <knome> just look how many notches the green bar came down
[07:34] <knome> or use the tooltips to figure that out
[07:35] <flocculant> tooltips ... 
[07:35] <knome> hover over the bars
[07:35] <flocculant> just found those :D
[07:35] <knome> \o/
[07:36] <flocculant> from a personal pov - the timeline isn't likely to add much for mine, I'd be more likely to see what others were doing
[07:37] <knome> but the timeline is useful anyway then, right?
[07:37] <flocculant> for that - yes 
[07:37] <knome> one thing that i'm thinking is
[07:37] <flocculant> if it was no use to me - I would say so :)
[07:37] <knome> we don't currently list the work items sorted by status anywhere
[07:38] <knome> i don't know if that's a problem
[07:38] <knome> likely not
[07:38] <knome> a new contributor likely knows which area they want to work in
[07:38] <flocculant> yea
[07:38] <knome> eg. either artwork or QA
[07:38] <knome> but
[07:38] <flocculant> I guess XPL *might* find that useful 
[07:38] <knome> maybe the timeline could have the current WIP work items at the top of the list
[07:38] <knome> "these are up for completion next"
[07:39] <knome> simon told me he was happy with the overview
[07:39] <knome> basically, the overview and the details are very close to each other
[07:39] <knome> in a way
[07:39] <knome> it's just a different sort order
[07:40] <flocculant> knome: perhaps timeline could have WIP/TODO/ done by week (or whatever chunks)
[07:40] <knome> nah, that'd add complexity to the DB
[07:40] <flocculant> ok :)
[07:40] <knome> and "this was todo at week X" isn't useful IMO
[07:40] <flocculant> oh - not what I meant
[07:41] <knome> oh
[07:41] <knome> right, i see what you mean
[07:41] <flocculant> I mean - at the top - this stuff is being done, needs to be done - below the rest
[07:41] <knome> but wouldn't that be beating the dead horse? :P
[07:41] <knome> the details tab could handle that
[07:42] <flocculant> ok - then I see no reason to include WIP either then
[07:42] <knome> so in addition to being able to filter by assignee, enable filtering by specification or status
[07:42] <knome> (see where i'm going? :P)
[07:42] <flocculant> on detail tab? 
[07:42] <knome> yep
[07:43] <flocculant> so we could see ALL the todo stuff if we wanted to? 
[07:43] <flocculant> that what you mean? 
[07:43] <knome> yes
[07:43] <knome> or all the artwork stuff
[07:43] <knome> (like in the overview tab currently...)
[07:44] <flocculant> mmm
[07:44] <flocculant> not sure about that much detail
[07:44] <flocculant> eg my todo or your todo
[07:44] <flocculant> team todo I'd be more likely to read
[07:44] <flocculant> or team WIP etc
[07:45] <knome> well
[07:45] <knome> those are easy enough to get to now
[07:45] <flocculant> not team todo
[07:45] <knome> i mean it's not hard to see what my WIP list is
[07:45] <knome> no?
[07:45] <knome> http://tracker.xubuntu.org/#tab-details/xubuntu-qa
[07:46] <flocculant> ha - so we're describing the same thing from either end
[07:46] <knome> or http://tracker.xubuntu.org/#tab-details/flocculant+teams
[07:46] <flocculant> I mean - there's no way to find out Xubuntu todo or Xubuntu wip
[07:46] <knome> i mean the latter url can be infinitely useful
[07:46] <knome> ah, right
[07:46] <knome> sure
[07:47] <flocculant> that might be more useful
[07:47] <knome> yep
[07:58] <flocculant> bluesabre: ping
[08:09] <flocculant> do a couple of hardware tests and I think we're looking pretty good 
[08:16] <flocculant> biab
[09:01] <ochosi> bluesabre: hey! just a quick status inquiry: xfpanel-switch is uploaded? how about the patch for xfce4-panel?
[09:16] <knome> bluesabre, also if you didn't notice, i developed the timeline to lure you more into making progress to see the tracker changing!
[09:21] <ochosi> :>
[09:21] <knome> so, i finally figured out what i want to do with the overview tab
[09:21] <knome> bumpy ride incoming
[09:22] <ochosi> btw, still planning to integrate this in x.org right?
[09:22] <knome> "in"?
[09:22] <ochosi> well, in terms of making it look integrated there and not a separate page
[09:23] <knome> well, as i said previously, i don't think the overall layouting stuff works for both
[09:23] <knome> i'll probably look into making the headers more integrated looking at some point
[09:23] <ochosi> i think having the header from x.org would be enough
[09:23] <knome> but that requires changes in the website header too
[09:23] <knome> yeah, something like that
[09:23] <ochosi> you can always <iframe> it ;)
[09:23] <knome> one thing that i *don't* want to get from there is the navigation menu
[09:23] <knome> huh!
[09:23] <knome> well, that isn't even the issue
[09:24] <knome> i just don't think that i should squeeze this information to the content are in the website
[09:24] <ochosi> you don't? why not?
[09:24] <knome> *area
[09:24] <ochosi> right
[09:24] <ochosi> well the footer wouldn't be necessary
[09:24] <knome> because i just don't want to ;)
[09:24] <ochosi> heh
[09:24] <ochosi> alllright, mr. web-lead ;)
[09:25] <knome> i'll figure out something at some point
[09:25] <flexiondotorg> ochosi, Do you think Xubuntu will be ready to mark the images ready soon?
[09:26] <ochosi> flexiondotorg: hey! sorry, i was (and still am) fairly afk atm, better ask bluesabre (should be around in a bit) he'll know more i presume
[09:26] <ochosi> also thanks for taking care of b1!
[09:26] <flexiondotorg> bluesabre, ^^^^
[09:26] <flexiondotorg> ochosi, No problem.
[09:32] <flocculant> well that was a barrel of laughs ... 
[09:32] <flocculant> usb failing to boot when created with anything except the gnome disks tool
[09:39] <flocculant> bluesabre: given that we've seen some issues with uefi/partition creation/timezone - should we make note of those in release notes - probably good idea I would say 
[09:46] <bluesabre> hey all
[09:46] <flocculant> hi bluesabre :)
[09:47] <bluesabre> flocculant: I agree about the release notes
[09:48] <flocculant> enough to not mark ready though? 
[09:48] <flocculant> not sure we should do that - these things aren't issues that *we* have control over 
[09:49] <flocculant> I'll add notes to the wiki page
[09:49] <bluesabre> flocculant: I think we can mark ready.  The issues are annoying but the installer does seem to sometimes work
[09:49] <flocculant> :)
[09:50] <flocculant> ok - I'll do that then 
[09:50] <bluesabre> sweet
[09:51] <flocculant> I'll make a start on the x.org note too - then someone can fiddle and publish
[09:51] <bluesabre> not sure what the issue is with ubiquity... these issues are fairly new, but they also affect me when doing vivid installs now too
[09:51] <flocculant> bluesabre: thanks for keeping an eye on things for us and doing most of release notes
[09:52] <bluesabre> flocculant: np
[09:53] <bluesabre> I think I might have written everything that's currently there except what I copied from last release :D
[09:53] <flocculant> ha ha 
[09:53] <flocculant> ok - images marked ready now 
[09:55] <bluesabre> yay!
[09:55] <flexiondotorg> flocculant, Thanks.
[09:58] <knome> thanks everybody, again
[09:59] <flocculant> knome: link to x.org admin thing so I can get draft note started please :)
[10:01] <bluesabre> ochosi: xfpanel-switch is uploaded, patched panel is not yet, and xfpanel-switch also not added to seed yet
[10:02] <flocculant> bluesabre: ok updated wiki notes
[10:02] <bluesabre> flocculant: I bet the last 5 minutes were waiting on login or saving
[10:03] <bluesabre> flocculant: looks good
[10:03] <flocculant> ha ha ha - yea ;)
[10:05] <flexiondotorg> bluesabre, flocculant ochosi All flavours are now marked ready.
[10:05] <bluesabre> flexiondotorg: great
[10:05] <flexiondotorg> How are your release notes?
[10:06] <flocculant> done
[10:06] <bluesabre> good to go
[10:06] <flocculant> that's 2 lies right on top of each other :D
[10:06] <bluesabre> :D
[10:06] <bluesabre> teamwork
[10:06] <flocculant> \o/
[10:08] <flexiondotorg> bluesabre, lol
[10:16] <flocculant> draft done - not sure we really need to be list bugs at x.org as well - so I didn't 
[10:23] <bluesabre> flocculant: I'd agree with that
[10:24] <bluesabre> I'd say that's pretty sufficient for b1 website post
[10:25] <bluesabre> oh
[10:25] <bluesabre> unless we want to link to the wiki page for more details and known issues
[10:25] <knome> yes, link to wiki
[10:26] <flocculant> I thought it is linked ... 
[10:26] <bluesabre> I don't see it in the preview at least
[10:26] <bluesabre> I see where it should be
[10:27] <bluesabre> I'll add it
[10:27] <flocculant> might actually liked it where I was warbling about bugs 
[10:29] <bluesabre> http://xubuntu.org/?p=3430&preview=true
[10:29] <bluesabre> I let go of the edit lock in case you want to tweak anything
[10:30] <bluesabre> knome: maybe we could have just a little more contrast with the completed-by notes on http://tracker.xubuntu.org/#timeline ? 
[10:30] <flocculant> mmm - that looks like the one I did 
[10:31] <flocculant> anyway - happy :)
[10:31] <bluesabre> flocculant: dunno, maybe you didn't save? :)
[10:31] <knome> bluesabre, maybe
[10:40] <flexiondotorg> bluesabre, Does Xubuntu ship Galculator?
[10:40] <flocculant> bluesabre: save? :p
[10:40] <knome> bluesabre, like that?
[10:41] <knome> bluesabre, and yeah, completed is better, thanks
[10:41] <bluesabre> flexiondotorg: we're currently shipping gnome-calculator
[10:41] <flexiondotorg> OK, thanks.
[10:42] <bluesabre> knome: much better, can actually read it now
[10:42] <knome> who cares about reading :D
[10:42] <bluesabre> >.>
[10:42] <knome> and, humm
[10:43] <knome> oh no
[10:43] <knome> nvm :P
[10:43] <knome> good good
[10:43] <bluesabre> lol
[10:43] <knome> i'm just confusing myself
[10:53] <flocculant> we could be a team 
[10:53] <knome> no, nothing is better than messing with yourself
[10:53] <flocculant> ... 
[10:53] <knome> you're not going to take that away from me!
[10:53] <flocculant> ha ha 
[10:54] <flocculant> slickymasterWork: didn't know you'd arrived - thanks for mailing the url to the list :)
[10:54] <knome> dkessel, what's the latest update on the jenkins stuff?
[10:56] <knome> lderan, i just passed a work item about the XML-RPC interface for you; you're welcome ;)
[10:56] <knome> the more (assignees), the merrier
[10:56] <flocculant> I'll gather some thoughts on what I would like for that 
[10:56] <knome> great
[10:57] <flocculant> as far as jenkins goes - pretty sure current state is : hosting physically somewhere, waiting on test/ubiquity fix 
[10:57] <knome> ok
[10:58] <flocculant> balloons was aiming at b2 I think 
[10:58] <knome> aha
[10:58] <flocculant> not sure why though 
[10:58] <knome> :)
[10:59] <bluesabre> cool, so maybe we'll get another ubiquity release this cycle then
[11:00] <flocculant> bluesabre: aah - not quite talking about the same thing here - sorry
[11:00] <bluesabre> ah, darn
[11:00] <bluesabre> guess I'll go back to poking for that soon
[11:00] <flocculant> this is the test failing at ubioquity - so not necessarily a fix at ubiquity, more likely to be a test fix
[11:01] <bluesabre> gotcha
[11:02] <flocculant> it'll be good to be able to get reports daily for image smoketest
[11:03] <flocculant> though that wouldn't find things like icons showing on desktop ofc
[11:09] <flocculant> knome lderan - http://pad.ubuntu.com/trackerpull
[11:09] <flocculant> a start at least
[11:12] <knome> flocculant, i think the from/to stuff should be in the tracker
[11:12] <knome> flocculant, there's no way our status tracker can know the specific dates you want
[11:12] <knome> well, that is, unless you feed it them - but then it is more like manual data mining, and that should be done in the tracker to avoid silly queries
[11:13] <flocculant> then we just end up with a list that's going to be really long given that tracker has 7 entries a week 
[11:13] <slickymasterWork> sure flocculant, np
[11:13] <knome> flocculant, i'm not saying we can't filter the results we get
[11:14] <knome> flocculant, i'm just saying that since we want to do repeated queries that always follow the same pattern, we can simply filter out that pattern ourself
[11:15] <flocculant> what is this for ?
[11:15] <knome> pulling data from the qa tracker to the status tracker
[11:15] <flocculant> because what I'm looking for and what you're looking for are obviously different :)
[11:15] <knome> i don't know how specific data we want to pull to the status tracker
[11:16] <knome> probably not to the level of individual reports
[11:16] <knome> see -
[11:16] <knome> if we want to see which bugs affected, say, beta 1
[11:16] <knome> we always wanted all beta 1 reports
[11:16] <flocculant> if this is just for the tracker - then you probably want to talk to people who only want general info 
[11:17] <knome> we *can* pull more specific info from the tracker too
[11:17] <knome> but i don't want to make the QA tracker just another platform where we simply input the data and then process it elsewhere
[11:17] <knome> i'm sure you agree - many things should work in the tracker itsefl
[11:18] <flocculant> yea 
[11:18] <knome> so from that perspective, i'm trying to figure out what information is useful and sane to pull out
[11:19] <flocculant> I'm not sure our tracker is the right place for any of it tbh
[11:19] <flocculant> I obviously got the wrong end of the stick 
[11:19] <knome> i wouldn't mind some "totals"
[11:19] <knome> like amount of tests
[11:19] <knome> or mentioning testers
[11:20] <flocculant> but over what period? 
[11:20] <knome> per milestone
[11:20] <flocculant> and tomorrow any data about b1 is pointless
[11:20] <knome> of course, the idea would be to show the data in a form that isn't too overflowing
[11:21] <knome> judging by that logic, isn't it useless to know how many items of a total of our items we have completed?
[11:21] <knome> i understand there's a slight difference, but i don't mind showing historical data either
[11:21] <knome> and for taht matter, we can show "active" milestones only
[11:21] <flocculant> I just don't see that numbers from milestones add anything 
[11:22] <flocculant> and generally the active one is daily 
[11:22] <flocculant> so which figures are you going to want to see? 
[11:22] <knome> it adds understanding about the scale of testing
[11:22] <knome> and potentially motivates other people to help
[11:22] <flocculant> today/yesterday/this week/last week/month/cycle 
[11:22] <knome> pass/fail ratio per milestone
[11:22] <knome> that's useul
[11:22] <knome> +f
[11:22] <knome> bugs found per milestone
[11:23] <knome> critical bugs for milestone/cycle
[11:25] <flocculant> I'm just not seeing the usefulness of this 
[11:25] <ochosi> bluesabre: ok thanks, still planning to add it to the seed and upload the patch? (if so, a workitem might be a good idea so we know when it's done)
[11:25] <knome> the usefulness of it is that since we are pulling a lot of progress related data to one place, we would have QA-related stuff too
[11:26] <knome> currently the status tracker doesn't tell anything about how QA is doing
[11:26] <flocculant> yes - but it's too general to be of use to QA
[11:26] <flocculant> maybe to other parts of team
[11:26] <knome> there is no way to check whether the testing is healthy, or if critical bugs are found in a new milestone
[11:26] <knome> sure - as i said, i'm not trying to replace the tracker
[11:26] <knome> and for comparison:
[11:27] <knome> the work item "" Discuss, review and rewrite the technical guidelines under the "Seeds & Composition" chapter in the Strategy Document "" isn't very useful or tell a lot about anything - until you dig up things from other places
[11:27] <flocculant> yea - I see that point
[11:27] <knome> same with listing the bugs in the bugs blueprints - listing the titles alone is useless - the real data is in LP
[11:27] <flocculant> as I said - better perhaps to talk to other people than me :)
[11:28] <knome> i will then
[11:28] <knome> but please follow the progress - so we aren't doing something very silly...
[11:28] <flocculant> not because I don't care - but because I'd want more detail so I only look in one place :)
[11:29] <knome> we'd of course do a lot of linkage so you'd have quickish access to various stuff
[11:29] <flocculant> of course I'll follow progress :D
[11:31] <knome> bookmarking the pad
[11:31] <knome> bbl
[11:32] <flocculant> cya later
[11:34] <bluesabre> ochosi: thats the plan, feel free to add a workitem and assign me, gotta run
[11:35] <ochosi> bluesabre: ok, will do!
[11:35] <flocculant> hi ochosi 
[11:36] <ochosi> bluesabre: done
[11:36] <ochosi> hey flocculant 
[11:37] <flocculant> I assume you know, but images all marked for release
[11:39] <ochosi> yup, just read the backlog
[11:40] <ochosi> good good, thanks for taking care of that
[11:40] <flocculant> well 
[11:40] <flocculant> I just let people get on with it :D
[11:42] <ochosi> :)
[11:43] <flocculant> bbl 
[14:40] <flocculant> knome: published it
[14:40] <flocculant> not on the front page though
[14:40] <flocculant> knome pleia2 - if you could do the honours with twitter etc 
[14:42] <flocculant> flocculant: but I'll remember the extra m for matte when I do this in the future :D
[14:43] <flexiondotorg> flocculant ;-)
[14:44] <akxwi-dave> just a quick one guys and gals.. while testing 15.10 beta 1 - starting mousepad from the whisker menu is fine..  starting from bash,  gives this message but still work.. (mousepad:2554): GLib-GObject-WARNING **: The property GtkSettings:gtk-menu-images is deprecated and shouldn't be used anymore. It will be removed in a future version. 
[14:44] <akxwi-dave> is this expected?
[14:45] <flocculant> akxwi-dave: you get those warnings with a host of different apps starting like that
[14:47] <akxwi-dave> phew thats ok then.. :-)
[14:47] <flocculant> yep - but thanks anyway :)
[16:21] <blaze_> Parole crashes when you try to close by clicking on X,should i report this on launchpad?
[16:22] <blaze_> *it
[16:43] <pleia2> flocculant: done all the social medias
[16:54] <xubuntu68w> Any know problems with Network Monitor plugin in 15.10B1?  Will not accept Network Device (eth0).  Works in 15.04 and all other versions and distros.
[16:57] <xubuntu68w> "Xfce4-Netload-Plugin: Error in initializing: Interface was not found"
[17:09] <flocculant> pleia2: thanks 
[17:12] <flocculant> xubuntu68w: not seen anything myself, can't see any reports of it either
[17:14] <flocculant> oh hang on - didn't read you properly - read network manager
[17:15] <xubuntu68w> Not, NM works fine, just the plugin...just tried with wifi, same problem.
[17:16] <flocculant> well - just added it to this install - not clean install - and it works 
[17:16] <flocculant> let me see what updates I'm missing
[17:18] <xubuntu68w> Had the same problem with B1 (live usb) and 25 Aug daily install.
[17:18] <flocculant> definitely an issue in the vm's I did today
[17:19] <xubuntu68w> so it's confirmed, it's not just me ?
[17:19] <flocculant> seemingly 
[17:19] <flocculant> though it's working fine in this install 
[17:21] <xubuntu68w> Oh goody...it works, it does't work...going to make triage fun.
[17:21] <flocculant> :)
[17:22] <flocculant> more annoyed with clementine being removed and not installable now :|
[17:23] <xubuntu68w> Sorry my darling :)
[17:23] <flocculant> xubuntu68w: can you report that - I'll confirm it 
[17:23] <xubuntu68w> against what?
[17:24] <xubuntu68w> that's always my ing what to report it aganst.ug repost, not knowproblem with b
[17:25]  * xubuntu68w hates web-irc...can't type.
[17:25] <flocculant> xubuntu68w: I would think that it's xfce4-netload-plugin
[17:25] <xubuntu68w> ok, let me drop this live usb and get back to reality
[17:26] <flocculant> :)
[17:31] <flocculant> working in vm now lol
[18:34] <cuzor> I downloaded iso and used yumi to install the iso on usb-stick. When I xubuntu (without installing) it crashes hangs after the first and only message "acpi pcc probe failed"
[18:34] <cuzor> ubuntu gives me 1 more line "starting version 219"
[18:34] <cuzor> pc hangs. reset button doesn't work
[18:36] <knome> cuzor, this isn't the support channel, try #xubuntu 
[18:36] <cuzor> ow ok
[18:36] <cuzor> found this channel on xubuntu site
[18:36] <knome> yes, and the website says this is for development
[18:37] <cuzor> sorry
[18:37] <knome> no problem
[20:09] <dkessel> knome: i don't know if anything new happened regarding the auto image tests. i have been forced offline a lot the last days, and if anything happens, it seems to happen outside the qa mailing list. last thing i knew was that balloons found someone to host the hardware and run the test infrastructure.
[20:09] <dkessel> gotta go afk again, bb
[20:10] <dkessel> oh, and there seems to be some backlog on news in #ubuntu-quality but no time to read now
[20:19] <flocculant> pleia2: you able to edit fridge posts at all? 
[20:19] <pleia2> flocculant: yep, have a fix for me?
[20:20] <flocculant> flexiondotorg: I see now it's not just Xbuntu but also Xubuntu MATE
[20:20] <flocculant> pleia2: yep - our bits of http://fridge.ubuntu.com/2015/08/27/wily-werewolf-beta-1-released/
[20:20] <flocculant> https://wiki.ubuntu.com/WilyWerewolf/Beta1/Xubuntu is link
[20:20] <pleia2> flocculant: oh, I don't like editing those because it's copied from the mailing list announcement
[20:20] <flocculant> meh
[20:20] <pleia2> and the mailing list announcement is what goes into UWN and stuff :\
[20:20] <flocculant> ok 
[20:21] <pleia2> I can, it just doesn't make a huge difference
[20:22] <flocculant> okey doke
[20:23] <flocculant> dkessel: I've been keeping an eye on that stuff as well 
[20:33] <ochosi> yeah, curious mistakes on that announcement
[21:42] <pleia2> flocculant: updated and set up a redirect on the Xbuntu wiki page so it goes to the right one
[21:43] <pleia2> oof, the cdimage link is wrong too
[21:44] <pleia2> they need a Unit193 to do link checking before publishing!
[21:44] <knome> :)
[21:44] <Unit193> Hah!
[21:44] <ochosi> +1
[21:44] <knome> yes, let's appoint Unit193 the link liaison
[21:44] <Unit193> If I get a ping, I do a linkcheck! :P
[21:44] <pleia2> hehe
[21:58] <flocculant> seems like all the cdimage links are wrong
[22:00] <Unit193> That was a great announcement?
[22:00] <pleia2> gosh, we just might have to link to the fridge post in UWN...
[22:00]  * pleia2 fixes them up
[22:01] <knome> heh
[22:01] <drc> So, Xubuntu now has an official XLL (Xubuntu Link Looker) as well as an XPL?
[22:01] <flocculant> ha ha ha 
[22:02] <pleia2> lol
[22:03] <flocculant> is there any point in replying to the -release list mail with correct links? 
[22:04] <flocculant> I don't suppose many people would look there
[22:04] <knome> maybe a good reminder for the future to double-check stuff
[22:04] <flocculant> indeed
[22:04] <flocculant> poor old flexiondotorg 
[22:05] <Unit193> drc: XPL, XTL, XCL, and who knows how many more. ;)
[22:05] <flocculant> I'm just XXL
[22:05] <pleia2> if you know who the person who wrote the announcement is, it would be worth telling him
[22:05] <pleia2> I don't know his irc nick
[22:05] <flocculant> pleia2: it's flexion ^^
[22:05] <pleia2> ah :)
[22:06] <pleia2> I thought you were just spouting out robot names
[22:06] <pleia2> as you do
[22:06] <flocculant> ha ha ha 
[22:20] <flocculant> night all
[22:36] <bluesabre> evening all
[22:37] <Unit193> A wild bluesabre!
[22:39]  * knome fires an arrow towards the wild bluesabre 
[22:40]  * bluesabre dies
[22:40] <knome> well, it didn't hit you
[22:40] <bluesabre> do not pass go
[22:40] <bluesabre> :)
[22:45] <bluesabre> bbabl
[22:49] <knome> i'm off to bed
[22:49] <knome> nighty
[23:33] <Unit193> bluesabre: What about xfdesktop 4.12.3?