[03:40] does anyone know how to configure XF86AudioMicMute? It's not by default configured [03:41] i can detect the button, but it is definitely not configured [09:02] dkessel: I commented on your comment at trello [09:08] use a pad - with a sensible name for it perhaps :) [09:10] elfy: ok, will do [09:26] elfy: http://pad.ubuntu.com/xubuntu-qa-v-autopilot [09:27] ta [10:05] morning folks [10:05] and happy blueprinting day [10:05] is the umbrella blueprint set up already? [10:07] man, i just got up! [10:07] * ochosi needs coffee [10:07] haha, me too, but who knows [10:07] i can set it up as well if you are too lazy [10:09] morning ochosi [10:09] * elfy thinks if the XPL wants team leads to do theirs the least the XPL can do is the main one - and theirs too :D [10:09] ;) [10:10] hmm i found a bug while trying to verify my german translation of the xubuntu-docs.... has any of you tried to do the steps for using ndiswrapper this cycle? :p [10:10] what's ndiswrapper ... [10:10] the configuration tool won't open from the settings manager... "gksu" not found [10:11] elfy, a wrapper that allows you to use windows drivers with linux [10:11] "Xubuntu supports a system known as NDISWrapper. This allows you to use a Windows wireless device driver under Xubuntu." [10:11] better to use polkit [10:12] That tool might need to be repackaged [10:12] dkessel, file a bug against xubuntu-docs and start working on it ;) [10:12] synaptic is an example for how to do that [10:12] (using polkit instead of gksu) [10:12] we've already shipping pkexec policy files for some apps [10:13] *we're [10:13] so you suggest filing a bug against ndisgtk? and then adding a policy file in some package ? [10:13] The policy file should he addeed to the package itself [10:13] ah ok [10:14] and if the documentation tells you to use gksu, then you should file a bug against the docs to change that part too [10:14] knome: no it just tells the user to click the icon, so that's fine I guess :) [10:14] probably the desktop file has a startup command with gksu [10:14] right [10:14] yep. [10:15] and hey zequence :) what's up? [10:16] knome: Not much right now. Thinking about eating breakfast. You? [10:16] sameish thoughts [10:21] aaahh, nice, much betterr now.... [10:21] morning dkessel [10:22] seed gksu ... just saying :p [10:24] i am on trusty currently. does anybody want to verify bug 1385841 for utopic? [10:24] bug 1385841 in ndisgtk (Ubuntu) "ndisgtk should use pkexec instead of gksu" [Undecided,New] https://launchpad.net/bugs/1385841 [10:26] https://blueprints.launchpad.net/ubuntu/+spec/topic-v-flavor-xubuntu [10:26] the report does not mention why gksu should not be used [10:26] team leads, start your engines ^ [10:30] created and linked the sub-blueprint for website [10:31] artwork is done too [10:32] oh, qa too [10:32] nice [10:32] this is going much better than anticpated :) [10:32] i'll set up features next [10:34] and linked [10:36] bug fixes done and linked [10:36] qa blueprint work items added [10:36] and please propose the series goal for vivid [10:37] so once we are ready setting the blueprints up, we can easily ask the release team to accept them to allow them to show up in status.ubuntu.com [10:37] only marketing missing now [10:37] i can set that up [10:38] all of mine are proposed for vivid [10:38] done [10:39] oh, just wanted to propose i do marketing so we're done... :) ty knome [10:40] now send a mail for the -release team and list the blueprints and ask them to approve them [10:40] elfy: what about linking trello in the qa blueprint? that way ppl can find it [10:40] knome: release team or release ml? [10:41] ml [10:41] k [10:41] thought so :) [10:41] yep, sorry for being ambiguous [10:41] np [10:42] ochosi: yep - not sure if you got mail re qa trello - it's public now [10:42] elfy: yeah, i received it, that's why i meant you can actually link to it there too [10:48] thought as much - just checkiing :) [10:52] so while there's a bunch of us mulling about - can we please get some resolution on staging PPA [10:53] if it's staying with what it has - what other PPAs do I need to be as up to date as possible - shimmer etc I'm thinking of here [10:58] ali1234: does bug 1379176 affect the normal Xfce session (xubuntu-free user account)? [10:58] bug 1379176 in xfwm4 (Ubuntu) ""Clear" button has no effect in Settings > Window Manager > Keyboard tab" [Undecided,Confirmed] https://launchpad.net/bugs/1379176 [11:06] ochosi: don't forget to approve the blueprints - at least I assume you should be doing so [11:07] elfy: yeah, shimmer is a good idea for the artwork [11:07] the daily one [11:08] i missed out on the PPA discussion a bit [11:08] :) [11:08] what was the problem with staging exactly? [11:09] balancing doing enough daily builds and not becoming a massive daily buildfest with hundreds of megs of update every day [11:09] not a problem per se , I just really wanted there to be one [11:10] and if not at least some idea of the hundreds of extra PPAs the only person in team that's needing to have to see what's going on [11:10] i'd actually like to set some goals on what apps we're gonna work on [11:10] and then switch on daily builds for those [11:10] but we need bluesabre around for that [11:11] shimmerproject/+archive/ubuntu/daily <- that one? [11:11] really all these other ones should be listed somewhere [11:11] yeah, we should make a list... [11:12] re: blueprints approval: i'm only approving blueprints that have content [11:12] e.g. for marketing there's nothing to approve yet [11:12] eg for QA there is :p [11:12] i think just adding the "approved" tag to any blueprint makes it sorta meaningless [11:12] yeah, and it's approved too ;) [11:13] says approver none :) [11:13] mmm [11:13] not anymore [11:13] but yeah, i didn't look there cause all the other blueprints had that filled out already [11:13] ok - so I'm so quick to set wallpapers and themes and icons to what I normally use [11:14] I'd best set them to default or any changes to shimmer ppa daily will not affect me lol [11:14] probably, yeah ;) [11:14] heh [11:14] although wallpaper doesn't matter [11:14] as long as you use greybird and elementary-xfce-darker, that's it [11:15] yep [11:15] then you should notice any breakage/missing icons [11:16] yep [11:16] installiing that ppa now [11:16] just FYI, as soon as V gets a gtk3 update, the themes will all be broken [11:16] okey doke [11:17] we don't have support for gtk3.14 yet [11:17] you can probably approve https://blueprints.launchpad.net/ubuntu/+spec/xubuntu-v-bugs too - that won't get content till we start filling in bugs [11:18] indeed, done [11:20] awesome - I'll leave you in peace now for a while then :D [11:21] * elfy is off for a bit fiddling with the qa processes rewrite [11:22] knome: did you see http://pad.ubuntu.com/upgrading ping ? [11:22] yes [11:22] cool, well thanks elfy! [11:22] that was a nice sprint [11:22] will have to take a real look at that $some_time [11:22] bookmarked [11:23] yea cool [12:03] http://cdimage.ubuntu.com/xubuntu/daily-live/current/ [12:03] \o/ [12:04] oh nice [12:06] missing from tracker - but so is everything atm [12:13] ...and that image requires switching to vt1 and back to vt7 with virtualbox.... [12:14] dkessel: it will - there's been no fix yet [12:14] elfy: i am installing ;) [12:14] dkessel: I upgraded on Friday morning :) [12:27] i guess i should update soonish [12:27] ...to 14.10 ;) [12:28] heh [12:30] ochosi, how do you plan using https://wiki.ubuntu.com/Xubuntu/Roadmap/ ? [12:38] as a general thing re pkexec - what's going to be our plan here [12:39] ndiswrapper might not have gksu - but if we get involved in each and every thing that might need dealing with - we'll never end [12:39] shouldn't that be a general ubuntu thing to deal with? [12:40] isn't it a general ubuntu thing? [12:40] ubuntu does not install the gksu [12:40] package [12:40] I'd assume so - was just thinking given the discussion earlier [12:42] ideally the gksu package should be removed from the repo completely [12:43] to complete the pkexec transition [12:43] elfy, we can kickstart the process to get it done; eg. file bugs when gksu is used instead of pkexec [12:43] and i think that's where our responsibility ends [12:44] yep [12:44] works for me [12:55] knome: haven't given that much thought tbh [12:55] why, do you have a proposal? :) [12:56] i mean i liked how we did in trusty [12:56] although i also don't mind if ppl put their stuff directly into blueprints === meetingology` is now known as meetingology [12:56] but i guess the spec has the advantage of keeping things on a single page [12:57] just asking [12:57] i don't think there is one right way [12:57] but otoh, if we aren't using it, then let's not pretend we are :) [13:01] sure [13:01] i actually wanted to wait for bluesabre to chip in about features and stuff and then decide what to do with it [13:02] frankly, it's also a bit cumbersome to use and slow, so i'm not entirely sold on the wiki [13:02] amen to that [13:03] good morning folks [13:03] oh wow, speak of the "devil" [13:03] :) [13:04] morning bluesabre [13:04] (:c [13:04] time to catch up on backlog [13:10] ok, caught up [13:11] for any packages we don't ship, but maybe use and should have pkexec policies, make a list somewhere. We can update the packages and get them sponsored... that's relatively painless [13:12] good idea [13:12] I'm going to do a better job of monitoring xubuntu-v-bugs this cycle, so anything that needs a fix (thunar for instance), link it [13:13] could even just submit bugreports and add them to the bugs bp [13:13] I linked 3 to that bluesabre [13:13] also, xfdesktop and thunar both use glib, does this bug affect xfdesktop as well? [13:14] I started this pad for development, we can use it to put together ideas for dev this cycle, http://pad.ubuntu.com/xubuntu-v-dev [13:14] or any other considerations [13:14] bluesabre: you could link to that in the features bp [13:15] just so that we have common places to look when we "lose" links to stuff [13:15] oh, this is just for today. Going to port over to a dev blueprint as we finalize today [13:15] oh right [13:16] wrt upower 0.99, theoretically we should be safe [13:16] elfy, great, thanks [13:16] iirc all xfce components received patches, so theoretically, things should work [13:16] right [13:16] bluesabre: what i mentioned earlier wrt evince, you just have to open it on its own [13:17] without file [13:17] then you see the recent-view [13:17] ok, I'll take a look at that [13:17] it's kinda neat [13:17] haven't checked out the code for it yet though [13:17] ok, I see [13:18] i mean we could also just do an icon-view of all media-files in the recent menu [13:18] or something like that [13:18] yeah [13:18] there might even be a new widget implementing that [13:18] yeah, possibl [13:18] e [13:18] bluesabre: as far as planning what's going to be worked on will affect when we call for testing OR we can just extra call as and when [13:19] I just need to know what *we* would prefer early enough [13:20] right [13:21] I'll probably do some dev releases of some components only to -staging, its hard to give a specific time frame when these will be complete though [13:23] ok so plan B :) [13:23] I'll do a schedule and then we can shove extras in as and when :) [13:24] I'll try to target early milestonesn as much as possible [13:24] won't be doing that till I've seen release schedule [13:24] okey doke [13:25] ochosi: what's the general consensus among xfce-dev about getting 4.12 out by the end of the year? [13:25] bluesabre, aren't you two of the few, and you both want it out :) [13:26] I want it out, but I work on very few components [13:26] if I release xfce4-settings 4.12.0, Nick will return, but only to slap me [13:26] bluesabre: no consensus [13:27] bluesabre, but you should still do that, if that's ready for the 4.12 release [13:27] nick is away a few more weeks he said [13:27] knome: its... almost there [13:27] so i think it's unrealistic to assume a release will happen this year [13:28] is Mir going to start affecting us anytime soon? [13:35] not sure if it's something for -docs actually [13:36] ochosi, there's no docs blueprint!! [13:36] yeah, definitely more docs-y [13:36] slickymaster's surfing ;) [13:36] i'll do that. [13:39] docs blueprint created === xnox_ is now known as xnox === meetingology` is now known as meetingology [13:43] knome: thanks, added some details to the pad, will add more later [14:20] ochosi: what do you suggest as a permanent(ish) home for the QA incentive details? [14:20] elfy, actually I'm actually with a terrible headache and a bit hungover [14:21] slickymaster: lol [14:21] but I see there's already a lot work done [14:21] yea [14:21] let just catch up on what's been made so far [14:21] + me [14:26] do we already have any clue of when the new NetworkManager will land? [14:26] Unit193 ^ [14:42] ochosi: ping [14:45] heh - just about to point somewhere similar :) [14:45] ochosi: tried to make http://pad.ubuntu.com/xubuntu-qa-v-cycle less officialese [14:45] and knome - you could have a look when you've time too [14:46] sure, will do at some point [14:46] (again...) [14:46] yep [14:47] knome: thatnks for covering for me and drafting the docs blueprint [14:48] *thanks [14:54] bluesabre: so basically I assume you're happy that I'll do a testing schedule like normal and then fit things in as and when they need it? [14:55] slickymaster, no problem [14:55] * slickymaster is a bit sick :P [14:55] elfy: yeah, and I'll coordinate with you when there is testing to be done [14:56] where is the team image/hardware/testing page again? [14:56] bluesabre: pong [14:56] * ochosi needs to read up on the backlog [14:56] ochosi: Ubuntu dev folks patch away Headerbars on evince... but why not simple scan? [14:56] pretty sure they ship both [14:56] bluesabre, ask them :) [14:56] good question [14:57] knome is right, we should ask them [14:57] knome: asked ochosi since he seems to be in the know :) [14:58] lol [15:03] bluesabre: https://wiki.ubuntu.com/Xubuntu/Testing/TeamHardware [15:03] elfy, thanks [15:04] wondering if we can extend that with a few specifics... like monitor count [15:05] bluesabre: well ... [15:05] elfy, poked [15:05] given that it takes a thousand attempts to get a simple one done - if you want something more elaborate - please do your own ;) [15:05] knome: thanks :) [15:06] bluesabre: but seriously if you think it's helpful to know - change it :) [15:07] sometimes I suspect it might be helpful to know it it's laptop or desktop too I guess [15:07] if we add monitor count, is it useful to know i can do two-monitor testing on a non-development version? [15:07] yeah, laptop vs desktop, gfx card [15:07] or maybe we should add one more column [15:07] knome: yes, since we develop the portion of xfce4-settings that handles monitors [15:08] for the "hardware id" [15:08] and separate the vbox list [15:08] bluesabre: +1 on monitor/graphics card info [15:09] * bluesabre waits forever for ubuntu wiki to log him in [15:09] elfy, allow me to poke the page in the way i suggested? [15:09] knome, hardware id? you mean something like https://wiki.ubuntu.com/QATeam/Hardware [15:09] slickymaster, no, i mean like [15:10] knome: yea go ahead [15:10] every member should add one line per a hardware configuration [15:10] bluesabre, no poking now then [15:10] but for instance I do dailies on VM, milestones on laptop hence only manual partition [15:10] knome: sure, still logging in [15:10] yep [15:11] but once or twice a cycle I'll do hardware on desktop [15:11] knome: yea - one line per available hardware config would do - but it's getting people to actually do it :) [15:12] elfy, yeah [15:12] that's useful info for lots of us I would think [15:13] I'd like to know I could ask foo to check something on laptop for instance [15:14] cleaned up the dev pad a bit, http://pad.ubuntu.com/xubuntu-v-dev [15:15] bluesabre: ta [15:15] so other than staging and shimmer ppa I've got currently anything else I *need* to add here [15:16] bluesabre: what do you think about just copying over e.g. git versions from parole that we want testers to check out to the staging ppa from the parole-daily PPA? [15:16] and same for themes/icons [15:16] ok, lookie at the wikipage [15:17] elfy, ochosi: you obviously want to change some details... [15:17] elfy: yeah, everything should be in those two [15:17] :) [15:17] ochosiL that makes sense [15:17] bluesabre: ok cool [15:17] maybe other/comments could be combined [15:17] knome: i think we might need >1 line per tester [15:17] I guess I should try and use things like parole a bit more during cycle [15:18] i have desktop @work and laptop @home [15:18] ochosi, yes, then you should add one more line [15:18] ochosi: yea - I'm just going to add one for me [15:18] note the HWID field [15:18] and the note about the HWID field :P [15:18] or will when ochosi tells me I can access it [15:18] ;) [15:18] ochosi, while you're at it, remove the "other HW information" column [15:19] okok [15:20] i'm done [15:20] mostly [15:25] done [15:25] filling that in actually made me realise that I can do 2 monitors for laptop if we need to test something :) [15:26] caq5C4# [15:26] sigh [15:26] lol [15:26] elfy, i'd advise you to change your ubuntu one password [15:27] heh [15:27] ;P [15:27] I had to do that a while back because of similar elsewhere :D [15:27] yep [15:37] added mine [15:37] thanks guys, this will help track down unfortunate people [15:38] lol [15:38] but you could have made it alpabetical :| [15:38] oh dang it [15:38] awesome [15:38] did elsewhere, will do that now [15:38] so - found a bug in vivid ... [15:38] or not [15:38] bluesabre: I'm joking :D [15:39] everyone else will just tag on the bottom :) [15:39] elfy: I'm not... a bit ocd with alphabetizing [15:39] vivid bug already, nice one [15:39] * elfy waits for bluesabre to finish ... [15:39] * bluesabre is finished [15:39] bluesabre: not really - changing machine password - and it's hanging ... [15:40] bluesabre: looks good to me [15:40] Lockerkim though? [15:41] cat hopped on keyboard, wasn't sure what she types [15:41] :D [15:42] elfy, users-admin from terminal... wonder if there is any useful output [15:44] just started it again [15:45] killed existing - hadn't done anything ran it again and it worked ok [15:54] ochosi: can you add any roadmaps that I am missing at the bottom of the pad? [15:55] * bluesabre needs to create some for catfish, menulibre, mugshot [15:57] bluesabre: done [15:57] ochosi: thanks. I'll create and link roadmaps for the other projects, and we can start planning there [15:59] cool [15:59] sounds good to me [15:59] hey all [16:08] ochosi: will expand out from here :) http://wiki.smdavis.us/doku.php?id=development [16:08] hey knosys [16:08] hey :) [16:11] hi knosys [16:18] hey guys, its weird, i can't see translations anymore in launchpad. Why is that? [16:18] no idea - I've enough problems with English [16:19] "is not an active member of any Launchpad teams. " That is show on my profile. Does that means that i can't review translations anymore? [16:20] Oh wait, sorry i was on another different project. I should be looking to "xubuntu documentation" [16:21] my bad! [16:23] bluesabre: cool, good overview there [16:25] ochosi: one other QA thing while I remember - what more to do with qa incentive and then where we going to store that - testing wiki page ? [16:25] last probably makes more sense - then it's just a link elsewhere [16:34] elfy, or since it's an end-user facing thing (mostly) it could also go on the website [16:34] true [16:34] probably even better [16:35] it'll certainly get noticed more there I should think :) [16:35] yep, especially if we advertise that page set [16:36] knome: your requests are now on the menulibre roadmap :) http://wiki.smdavis.us/doku.php?id=development:menulibre [16:37] knome: I'll start finishing that off and get it on a draft page at x.org [16:37] great [16:40] lunchtime, bbl [17:11] ok - so there's a bit at the top of http://pad.ubuntu.com/QAIncentive now destined for x.org [17:11] destine ha ha [17:11] +d too [17:12] :) [17:12] hahah [17:13] gnome minesweeper just crashed [17:13] are the Swedish navy looking for it? [17:13] who knows [17:14] bbl [17:15] hf [17:24] ochosi: please read http://forum.ubuntuusers.de/topic/allgemeine-frage-zu-bugs-in-14-04-lts/ [17:25] I will add a reply later if you don't plan to do so :) [17:30] brainwash: yeah, feel free to add a reply (as long as it's an explanation and not a rant ;)) [17:50] I see people other than team adding to hardware page - that's more useful [17:50] especially akxwi-dave - not sure who he is - but he does a huge amount of testing for us [18:01] I'm back [18:03] Yey! [18:04] :D [18:23] bluesabre, brainwash: I think I need help understanding what the reporter is trying to say in LP Bug 1385863 as it is not clear at all [18:23] Launchpad bug 1385863 in xubuntu-meta (Ubuntu) "Constant minimum load of 1.00 after upgrade to 14.10 (Xubuntu)" [Undecided,New] https://launchpad.net/bugs/1385863 [18:26] skellat, he's saying that top says that his computer is on a huge load, but nothing seems to be the culprit [18:27] so it'd be good to know if his system feels like it's under a huge load or not [18:28] if it's not, then it might be either 1) a bug in top or 2) something that's explainable, but isn't imminently clear/logical [18:29] * skellat does not like bug reports with huge copy pasta dumps in the middle of them [18:31] Alrighty, probing questions left [18:31] Thank you knome [18:31] me neither, the data dump would be much better in an attachment [18:31] maybe you could edit the description to delete that [18:32] and ask to readd it as an attachment (or simply do that yourself) [18:32] and np [18:55] * bluesabre feels like there should be a xubuntu-u-development, but that draws a lot of parallels with new-features [18:56] yeah, i somewhat agree [18:56] we could also s/features/development/ [18:56] after all, we're using features like de [18:56] v [18:57] yeah, I think that would be the way to go [19:01]