[00:36] <bluesabre> brainwash: poke
[01:42] <sidi-valencia> can I help you poke brainwash ? :D
[07:59] <ochosi> bluesabre: sidi-valencia is a pro-poker :)
[07:59] <ochosi> brainwash: btw, what daemonize problem? we could fix that in xfpm straight away i guess
[08:55] <brainwash> ochosi: bug 973778
[08:55] <brainwash> and bug 1239014
[08:56] <brainwash> and bug 1314782
[08:56] <brainwash> appfinder 4.11 is not affected anymore, but we still ship 4.10
[08:59] <ochosi> brainwash: meh, that is really long bugreport, why not just link me to the crucial/interesting part?
[08:59] <brainwash> the volumed one is the interesting one I guess
[09:00] <ali1234> ochosi: it's the fork before gtk_init bug
[09:00] <ali1234> if a daemon forks after calling gtk_init it can hang for a variety of reasons
[09:02] <sidi-valencia> ochosi, and they're such bosses that they figured it out straight away
[09:02]  * sidi-valencia pokes himself, for the fun
[09:02] <ochosi> right
[09:02] <ochosi> ali1234: so what would be the ideal solution to that problem?
[09:02] <sidi-valencia> does xfce4-volumed work on the locker screen in Xub?
[09:02] <sidi-valencia> ali1234, fork before gtk_init as instructed by the doc.
[09:03] <ali1234> ochosi: that &
[09:04] <ochosi> sidi-valencia: i guess not, because there's no music playback on the lockscreen in xubuntu
[09:04] <ochosi> so it wouldn't make any sense
[09:04] <brainwash> it's a different vt
[09:04] <ochosi> (remember, it's in a different VT, so your current seat becomes inactive hence music playback stops)
[09:04] <sidi-valencia> ochosi, well when i locked/suspended i had the music on when reopening the lappy
[09:05] <Unit193> ali1234: Seen https://bugzilla.xfce.org/show_bug.cgi?id=10804 ? :)
[09:05] <sidi-valencia> ochosi, my computer is so cool it plays music across VTs
[09:05] <ochosi> sidi-valencia: it continues after unlocking
[09:05] <ochosi> then you're maybe in the audio group
[09:05] <brainwash> or not using pulseaudio at all?
[09:05] <sidi-valencia> not using PA
[09:05] <brainwash> :)
[09:05] <sidi-valencia> and in audio
[09:06] <Unit193> Good choice.
[09:06] <sidi-valencia> you guys are geniuses
[09:06] <sidi-valencia> i was thinking of switching to PA
[09:06] <sidi-valencia> and upgrading xvd
[09:06] <ochosi> then you're an exception rather than the rule ;)
[09:06] <sidi-valencia> maybe i should code some DBus api for light-locker to talk to it?
[09:06] <ali1234> sidi-valencia: the per-seat audio stuff is handled by the console kit stuff and relies on cooperation fro pulseaudio
[09:06] <Unit193> Yey, for another exception.
[09:06] <sidi-valencia> ochosi, i do want to try out PA one day without all the Ubuntu FUD
[09:07] <ochosi> yeah, actually it's not bad
[09:07] <ochosi> i hardly ever use the advantages of PA (being able to individually adjust volumes per app, etc)
[09:07] <ochosi> but it's stable and it works
[09:07] <brainwash> running pulseaudio as system service also works
[09:09] <ochosi> i guess most of our problems would be solved by light-locker 2.0, whenever we get to that
[09:10] <ochosi> (although i remember sidi-valencia making a point against locking on the same VT)
[09:11] <sidi-valencia> http://lists.freedesktop.org/archives/dbus/2007-April/007496.html btw
[09:11] <sidi-valencia> on why you should fork before doing anything else ;P
[09:12] <sidi-valencia> yeah ochosi. i will keep the current branch personally, feels more secure ;)
[09:13] <sidi-valencia> (well my admin password is ridiculously short anyway, *coughs*)
[10:24] <bluesabre> brainwash: so, can you explain exactly what the zoomed branch does?  I'm wondering if it should be included in 1.8.5 or if it will be part of the 1.9 series
[10:30] <brainwash> bluesabre: it implements the resize style "zoom" correctly
[10:31] <brainwash> but the question is, should "zoom" be used in the first place?
[10:32] <brainwash> I vote for including it in 1.9 then
[10:33] <ochosi> yeah, i also wouldn't mind to give this more thought
[10:33] <ochosi> although i think that zoom generally is a good mode, we also use it in xfdesktop by default and it works well there
[10:34] <brainwash> it's nice to have the same resize style for the greeter and xfce desktop (-> seamless transition)
[10:34] <bluesabre> we can also implement different modes that can be control with the conffile
[10:34] <bluesabre> (for 1.9)
[10:34] <brainwash> yes, that was my plan initially
[10:34] <ochosi> yeah, but seems like a bit over the top to me
[10:35] <ochosi> also, these sort of things are tricky, as the greeter is always systemwide
[10:35] <elfy> hello peeps
[10:35] <bluesabre> hey elfy
[10:35] <brainwash> ochosi: but configuring it systemwide is a nice feature
[10:35] <bluesabre> but I do feel zoomed is a sane default :)
[10:36] <brainwash> you should at least test it :P
[10:36] <ochosi> yeah but different users on a system might want different settings
[10:36] <bluesabre> and we can use the code from xfsettings to implement multimonitor in a minimal fashion
[10:36] <ochosi> hence conflict
[10:37] <bluesabre> brainwash: I will when I merge it
[10:37] <bluesabre> just wanted to know *when* to merge it :)
[10:37] <brainwash> they might want different indicators.. or font size.. or..
[10:37] <bluesabre> yeah, login screen is not for users
[10:37] <bluesabre> its for the admin
[10:37] <brainwash> so adding all the different styles does not cause any harm
[10:37] <ochosi> yeah, or for distributors to set defaults
[10:38] <ochosi> brainwash: yeah, point taken
[10:38] <ochosi> so if we stick to zoom by default, we can merge that for 1.8 and put multiple modes on the roadmap for 1.9
[10:39] <ochosi> (also havent had time to test yet though, tbh)
[11:00] <bluesabre> brainwash: great work, finally tested it, it works well
[11:09] <bluesabre> and merged
[11:09] <bluesabre> if there are no complaints by friday, I'll do the 1.8.5 release and then start the 1.9 branch
[11:09] <bluesabre> *sunday
[11:09] <bluesabre> not friday
[11:09] <bluesabre> silly sean
[11:11] <ochosi> awesome
[11:11] <ochosi> yeah, friday is today :)
[15:39] <GridCube> elfy, whenever you have the time can you guide me to understand this trello thing and what im supposed to do with it?
[15:40] <elfy> I've always got time for you :)
[15:40] <elfy> especially about now :p
[15:40] <GridCube> P: alright then
[15:40] <elfy> I'll just go and get a fresh tea ;)
[15:43] <elfy> GridCube: so basically it's a collaborative board 
[15:44] <GridCube> yes, i understand that far
[15:44] <elfy> from the left you can see that I've set up the things I know we'll be doing 
[15:44] <GridCube> i don't understand what the topics are meant to be
[15:44] <elfy> ok - so from left - I've got 2 To Do boards - testing calls and the other
[15:45] <elfy> the testing calls one I've set up against the release schedule - each card is one task - with a date it's due
[15:45] <elfy> do you see that
[15:45] <elfy> or am I misunderstanding what you mean by topic?
[15:47] <GridCube> yes, basically the first to do list is pretty obvious, but the second, i dont understand what im suppose to do 
[15:47] <GridCube> you said you needed someone to grab the version numbers of the testcase applications right? where is that topic to do?
[15:47] <elfy> ok - well pick the 2nd from top - package testcases and open it 
[15:47] <elfy> GridCube: I've removed that 
[15:47] <GridCube> oh
[15:48] <elfy> did you do it?
[15:48] <GridCube> yes
[15:49] <elfy> ok - it's not wasted :)
[15:51] <elfy> GridCube: so in the to do board - there is an autotesting -packages card - open that - there's a link to the spec for autopilot - you can doublecheck the versions of packages there 
[15:52] <elfy> I spoke to balloons yesterday about putting versions on testcases - didn't work for them, but I'm not convinced that it won't work for us yet
[15:54] <elfy> GridCube: when you're ready ping me - I'll talk you through the next task the qa team have to do - this one is date dependent
[15:54] <GridCube> elfy, i dont understand what i have to do
[15:54] <elfy> did you open the wiki linked from the card? https://wiki.ubuntu.com/Xubuntu/Roadmap/Specifications/Utopic/Autopilot
[15:55] <GridCube> i opened that wiki
[15:55] <GridCube> and it has words, i understand some of them
[15:55] <elfy> that has versions - double check the versions on that against what you've got 
[15:55] <elfy> yea - I'm the same with autopilot ... means little to me as well ;)
[15:56] <GridCube> so i set up a 14.04 virtualbox and check those numbers against the ones in the table?
[15:56] <elfy> I thought you had those numbers already?
[15:57] <GridCube> no, as i said, i never understood what you wanted me to do
[15:57] <elfy> ok :)
[15:57] <elfy> forget all about that then for the time being :)
[15:57] <GridCube> ok
[15:58] <elfy> so - let's start again from the to do board - 2'nd card down Package testcases
[15:58] <elfy> click that and you'll see the card back
[15:58] <GridCube> alright
[15:58] <elfy> then there is a check list 
[15:58] <GridCube> card is that popup page
[15:58] <elfy> yep 
[15:59] <GridCube> ok
[15:59] <elfy> took me a while to realise that's the card back ... 
[15:59] <elfy> so - there's 4 tasks - the order matches the order that the calls to the testers will go out 
[16:00] <elfy> (it'll make a whole lot more sense when our package tracker matches that)
[16:01] <elfy> so what we need to do is open a testcase from the tracker and check it against the actual package - should be really quick to do - hopefully any testcase bugs got ironed out last cycle
[16:02] <elfy> but what I am trying to ensure is that when a bug gets reported - it is a real bug - people were good at reporting testcase bugs on the package page
[16:02] <elfy> does that make sense logically so far
[16:03] <GridCube> what tracker is that? iso.qa?
[16:03] <elfy> package.qa
[16:04] <elfy> GridCube: actually look here http://pad.ubuntu.com/5opi9dQG5e
[16:04] <elfy> that matches the trello cards - and is what the package tracker will look like next week
[16:06] <GridCube> im sorry elfy but i really dont understand what any of this means :(
[16:07] <GridCube> i feel really dumb
[16:07] <elfy> that's ok 
[16:07] <elfy> nah 
[16:07] <elfy> I'm often not too good at explaining stuff that I've been thinking about for months
[16:08] <elfy> if you look at the card back checklist - it says check Xubuntu optionals against current version
[16:08] <GridCube> yes
[16:09] <elfy> so - pretending that the pad is the package tracker for the moment - the first one in Xubuntu optionals is Catfish
[16:09] <elfy> so open the actual testcase for catfish and run through it with catfish - just to make sure that the testcase is spot on
[16:10] <elfy> http://packages.qa.ubuntu.com/qatracker/testcases/1559/info
[16:10] <elfy> is the testcase 
[16:11] <elfy> does that make sense?
[16:11] <GridCube> so check that the testcase makes sense, any error in the testcase itself would be the problem at this stage?
[16:11] <elfy> yep
[16:12] <elfy> that's what we need to do - then report testcase bugs so we can fix them before we do any testing calls
[16:12] <GridCube> i do this from a clean 14.04 install?
[16:12] <elfy> 14.10 
[16:13] <GridCube> alright
[16:13] <elfy> I keep one for package testcases
[16:13] <elfy> there are images up for 14.10 now at the iso.qa tracker
[16:14] <GridCube> yes
[16:14] <elfy> we have plenty of time for this package stuff - the first call for any of them is may 12th
[16:15] <elfy> at the moment qa is going to be all about making sure the foundations are solid
[16:15] <GridCube> its the same for 32 and 64?
[16:15] <elfy> yep
[16:15] <GridCube> ok, im fetching the 32b image now :)
[16:15] <elfy> mmm - packages do you mean?
[16:15] <GridCube> yes
[16:15] <elfy> yep - packages are the same 
[16:16] <elfy> many of the cards on trello you'll not do anything with
[16:17] <GridCube> :)
[16:17] <elfy> and if you think of something that's not there that could be you should be able to add it 
[16:18] <elfy> likewise - if there is something on there that you're doing - you can put your name against it - so the work's not done twie
[16:18] <elfy> s/twice
[16:19] <elfy> GridCube: just try to move one of the cards to a different board - as far as I know you should be able to do that
[16:20] <GridCube> done
[16:20] <elfy> cool - just checking - you can leave it there - we're doing it now anyway :)
[16:20] <elfy> now click the card so you see the card back again
[16:21] <GridCube> ok
[16:21] <elfy> then - on the right Members - click that and you get a list of us - click you and me 
[16:21] <GridCube> done
[16:22] <elfy> k - now other people like Unit193 can see we're doing something with that 
[16:22] <GridCube> ok :)
[16:22] <GridCube> bbiab making foods
[16:23] <elfy> ok 
[16:44] <GridCube> knome,
[16:44] <GridCube> sorry
[16:44] <GridCube> elfy, 
[16:44] <GridCube> XD
[16:44] <GridCube> im back
[16:44] <elfy> wb :)
[16:45] <GridCube> theres anything else we need see or i just need to download and check the testcases one by one according that pad
[16:45] <elfy> that's the current job in hand 
[16:45] <GridCube> ok :)
[16:46] <elfy> watch the trello board, if something is important it's have a red label - like the one you added us to
[16:46] <elfy> and date sensitive stuff will have a date :)
[16:47] <GridCube> :) makes sense
[16:47]  * elfy will wait for GridCube to find a testcase bug :)
[16:48] <GridCube> P:
[16:48] <elfy> then elfy will get GridCube to pull the testcase branch and change it :)
[16:49] <GridCube> we will see
[16:51] <elfy> I learnt :)
[16:51] <elfy> and if I can do it ... 
[16:52] <elfy> GridCube: one more thing - can you check that you can add a card 
[16:52] <elfy> I'm sort of afk for a while now
[16:52] <GridCube> done
[16:53] <elfy> GridCube: cool - just wanted to make sure you could - you can delete it now 
[16:53] <GridCube> okay
[16:54] <elfy> or archive - from the card back
[16:54] <GridCube> done
[16:54] <GridCube> deleted :)
[18:49] <GridCube> elfy, if i find a bug in the test case against what should i report it?
[18:49] <elfy> https://bugs.launchpad.net/ubuntu-manual-tests/+filebug
[18:50] <elfy> make sure the testcase number is in the main text area
[18:50] <GridCube> (like in the catfish testcase it says "click the icon right to the search box a menu should appear" the gear menu is at the far right, before it at the rigth of the search box there are two icons that change how the search results are shown
[18:50] <GridCube> )
[18:51] <GridCube> is that worthy of a report?
[18:51] <elfy> yep do the bug - and as much detail as possible - line number in the testcase is an enormous help
[18:51] <elfy> GridCube: absolutely it is - someone would end up putting the bug on the package tracker
[18:52] <elfy> then I end up grinding my teeth a lot sorting real bugs from testcase ones :)
[18:53] <GridCube> elfy, a title like this is ok? testcase for catfish ID 1559 needs to be reworded
[18:53] <elfy> Id' make it simpler - it doesn't matter too much - the detail is in the main text - I'd put error catfish testcase 
[18:54] <GridCube> ok
[18:54] <elfy> when you do the report - at the bottom - there are more options - tag it xubuntu :)
[19:01] <GridCube> elfy, can i suggest to add a test to the testcase?
[19:01] <elfy> which one?
[19:02] <GridCube> creating a screenshot and searching for it should show its thumbnail
[19:03] <GridCube> if you change the way search results are shown
[19:03] <elfy> oic - adding a test to the catfish one 
[19:03] <GridCube> yes
[19:03] <elfy> yea - add it to the bug report :)
[19:03] <GridCube> :D
[19:04] <elfy> I read that as a completely new testcase, was wondering what we'd missed :)
[19:13] <GridCube> :) wooo
[19:16]  * elfy waits for it to drop into his mailbox :)
[19:16] <GridCube> P: i added the link to trello P:
[19:16] <GridCube> https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1315491
[19:17] <elfy> thanks :)
[19:18] <elfy> when you've got your head around all this stuff - then we can look at you fixing testcases :)
[19:18] <elfy> thanks GridCube :)
[19:21] <elfy> GridCube: that's just right as a testcase bug - means whoever fixes it doesn't need to go looking too hard :)
[19:22] <elfy> which generally up to now has been slickymaster and me - and slickymaster is going to have enough on his plate with docs
[21:26] <sidi-valencia> TypeError: can't use a string pattern on a bytes-like object
[21:26] <sidi-valencia> light-locker-settings crashing on this
[21:26] <sidi-valencia> anyone aware of it and what to do?
[21:26] <knome> sidi-valencia, poke ochosi
[21:26] <ochosi> maybe bluesabre will be able to help you with that
[21:27] <knome> :P
[21:27] <ochosi> i'm not as python proficient
[21:27] <ochosi> what python version are you using?
[21:27] <ali1234> it means python 3 ate your lunch
[21:28] <ochosi> i dunno what python version it gets run with in xubuntu as we ship both
[21:28] <ali1234> going to need a full backtrace to fix it though
[21:28] <brainwash> bug 1313838
[21:28] <ali1234> not the same bug
[21:29] <brainwash> I know
[21:29] <brainwash> but a crash too
[21:31] <brainwash> sidi-valencia: you should file a bug report :)
[21:36] <sidi-valencia> 3.,4 i assume?
[21:36] <sidi-valencia> i was hoping someone knew it already
[21:36] <sidi-valencia> didnt do any decent amount of python in 5 years...
[21:37] <sidi-valencia> http://pastebin.com/hDsZaCdb
[21:40] <ali1234> ah, using pipes
[21:42] <ali1234> try changing line 349 to screensaver_output = self.run_command('xset q', check_output=True).encode('utf8')
[21:42] <ali1234> or possibly decode
[21:42] <ali1234> but you're just going to hit more errors. this source is not py3 safe
[21:45] <brainwash> what is the cause then?
[21:46] <brainwash> I mean why is this not a general problem?
[21:56] <sidi-valencia> thats magic ali1234 
[21:56] <sidi-valencia> ali1234, object has no attribute encode
[21:57] <sidi-valencia> i dont really care actually, i was asking just in case
[21:57] <sidi-valencia> if you need me to report tell me n ill do it later
[21:57] <sidi-valencia> watching stuff now
[21:58] <ali1234> brainwash: it is a general problem when you try to run old code in python3, there are several PEPs about it
[22:01] <brainwash> ali1234: but light-locker-settings is not old code
[22:05] <sidi-valencia> ali1234, i see so i could use python2 as a wrapper?
[22:05] <sidi-valencia> or not
[22:06] <ali1234> just use python2, yes
[22:07] <ali1234> that's still the default on ubuntu
[22:07] <brainwash> ah, thought that it's meant to be a python3 app
[22:08] <ali1234> it's not. reading from a pipe and using the result as a string doesn't work in python 3 unless you explicitly specify the encoding
[22:11] <ali1234> 💩
[22:11] <brainwash> ok, but the goal was to port python2 apps to python3, so we can get rid of python2 :)
[22:11] <ali1234> so fix it :)
[22:12] <brainwash> mmh, maybe
[22:12] <ali1234> just throw decode('utf-8') on the end of every byte array, before attempting to use it as a string
[22:12] <brainwash> yes, already read about it
[22:13] <ali1234> python 2 does it implicitly
[22:13] <ali1234> python 3 does not
[22:24] <sidi-valencia> no module named psutil
[22:24] <sidi-valencia> and this is where i stop caring about setting my settings
[22:24] <sidi-valencia> python2.7 isnt even meant to be supported anymore
[22:26] <Unit193> There *may* even be a Python 2.8.
[22:34] <drc> And Guido says "Last release of Python 2.7 (2.7.9) will be in May 2015. Time to move to 3.4, folks"
[22:35]  * Unit193 shrugs.
[22:35] <Unit193> I don't write the stuff, just use.
[22:36] <drc> And the first script is always free....