[09:05] <ochosi> hi everyone
[09:05] <ochosi> bluesabre: can we look at lls together today or tomorrow or are you super-busy?
[09:05] <ochosi> just have to whip it in shape a bit before FF creeps up on us
[09:05] <elfy> hi ochosi :)
[09:05] <ochosi> hey elfy 
[09:05] <ochosi> thanks for setting the trello-board public
[09:05] <ochosi> and for checking whether it's in sync
[09:06] <elfy> welcome - I'll check the sync this weekend
[09:06] <ochosi> guess it's important to get an overview now that FF is only a few days away
[09:06] <elfy> yep
[09:33] <ochosi> elfy: anything i can help with to make QA less moribund?
[09:36] <elfy> ochosi: if people aren't testing what can we do - you could mail the dev list perhaps, not sure what else we can do
[09:36] <elfy> there are a couple of people testing images now and again 
[09:36] <elfy> seems that jjfrv8 does some package testing when I call 
[09:37] <elfy> maybe see what happens with the first beta call/test in a week or two
[09:41] <ochosi> ok, i can also do some testing myself
[09:41] <elfy> :)
[09:41] <ochosi> if you have specific things that need more looking at, let me know
[09:41] <elfy> I will
[09:42] <elfy> mostly atm my concern is what happens when we beta test - if I'm the only one testing that - then what's the point in bothering *shrug*
[09:43] <ochosi> well one person testing is significantly better than zero [:
[09:43] <elfy> lol
[09:44] <ochosi> i guess it's hard to make testing more attractive
[09:44] <ochosi> although if you want, we can sit down and think about creating more incentive
[09:45] <ochosi> (and even if it only is that we send ppl who test regularly xubuntu stickers)
[09:46] <ochosi> pleia2: thanks for doing the meeting! if you need input/help with the article for x.org let me know (of if you want me to review it)
[09:46] <elfy> ochosi: yea testing is boring ... especially if you sit there and do 10 at a time 
[09:47] <elfy> might be some mileage in incentivising it (if that's even a word )
[09:47] <elfy> off for a bit now
[09:51] <ochosi> elfy: right, then let's think about that some more. i wouldn't mind investing a few of those bucks left in our "account" held by knome into this (at least i see much more direct benefit for us as a team from that then handing out flyers at conferences etc)
[09:52] <ochosi> (and if incentivising isn't a word, it definitely should be! :))
[10:47] <brainwash> ochosi: does bug 1054299 really affect xfpm directly? any idea?
[10:48] <brainwash> it does call xflock4 from xfce4-session
[12:38] <ochosi> brainwash: haha, well good to read that suspend also didn't work nicely with xscreensaver
[12:38] <ochosi> and what i considered a security threat (i.e. locking only when waking up) is considered normal there
[12:38] <elfy> ha 
[12:39] <ochosi> i would say it has to do with xscreensaver, not with xflock or the power-manager
[12:39] <ochosi> i mean now it
[12:39] <ochosi> 's logind handling that
[12:44] <brainwash> so.. can xfpm be removed from the affects list?
[12:44] <brainwash> closing the report completely is not an option yet, right?
[12:45] <brainwash> because 12.04 is still a supported release
[12:45] <brainwash> and not clue about 14.04
[12:47] <ochosi> i presume that for those using xscreensaver in 14.04, it might still be a problem
[12:47] <ochosi> but no clue, i haven't used xscreensaver in quite a while
[12:50] <brainwash> kinda strange though
[12:50] <elfy> aren't they all ... 
[12:51] <ochosi> suspend is just still a very tricky procedure on linux obviously
[12:51] <brainwash> it's a high priority bug plus security related :/
[12:51] <brainwash> and we cannot get rid of it
[12:51] <elfy> ochosi: re incentivising ... if we think about it till the beta testing - then if it's dead still take it to meeting 
[12:54] <ochosi> elfy: you mean think about it as in make a list of possible options and discuss that after b1 @meeting?
[12:59] <bluesabre> hey guys
[13:00] <elfy> ochosi: yea I think so :p
[13:05] <ochosi> o hey bluesabre 
[13:05] <ochosi> elfy: okeydokey, lemme know if the ideas get too many and you wanna write them down anywhere ;)
[13:07] <elfy> if we manage to get that many we can chuck it on a pad 
[13:08] <ochosi> yup
[13:14] <ochosi> bluesabre: so how's the weekend looking? got time to look into lls with me?
[13:14] <bluesabre> ochosi: so far, looking open for today
[13:14] <bluesabre> what changes need to be made for lls at this point, did we get everything we need with xfpm 1.3.1?
[13:17] <elfy> hi bluesabre 
[13:17] <bluesabre> hey elfy
[13:18] <bluesabre> haven't had a look at your parole issue yet
[13:18] <elfy> no problem - I'd think other things have more priority
[13:19] <ochosi> bluesabre: i would personally add a check for xfpm in lls and if it's running we hide the dpms and blank settings since xfpm handles all of that
[13:20] <bluesabre> ok
[13:20] <ochosi> so basically there aren't that many settings left for lls, but well...
[13:20] <bluesabre> I can also add a button that launches the xfpm settings... does it support specific tab opening?
[13:21] <ochosi> hmm, i think it partly does already
[13:21] <ochosi> because we can open the devices tab
[13:21] <ochosi> but it might need more work to open specific tabs
[13:22] <bluesabre> ok, I'll take a look
[13:22] <ochosi> i think right now we just open the last tab, cause that's always devices
[13:22] <ochosi> but not sure
[13:23] <ochosi> (eric implemented that part)
[19:57] <ochosi> hmpf, splitsville
[20:08] <bluesabre> splitcity
[20:11] <ochosi> bluesabre: oh, you're back
[20:11] <bluesabre> yup, just got back
[20:13] <ochosi> so finalizing catfish now?
[20:13] <bluesabre> yes, want to test it in a bit
[20:13] <bluesabre> ?
[20:13] <ochosi> ah, that question mark was important :)
[20:13] <ochosi> sure
[20:13] <ochosi> lemme know when you're ready
[20:16] <Unit193> Soo, I've been told to tell you when I do personal Xfce things like merges.  I'm merging xfce4-session 4.11.0 from experimental.
[20:19] <bluesabre> sweet
[20:19] <bluesabre> I'll sponsor that for you when you're ready
[20:20] <Unit193> The one in experimental is older than unstable, so kind of did a merge of both.
[20:20] <Unit193> OK, I'll upload a dsc for you.
[20:24] <bluesabre> ok, just committed changes for catfish... "--start" can autostart the search on startup
[20:24] <bluesabre> catfish /home/sean kittens --start
[20:25] <Unit193> bluesabre: dget https://sigma.unit193.net/source/xfce4-session_4.11.0-1ubuntu1.dsc
[20:25] <bluesabre> awesome
[20:26] <Unit193> Don't forget to review, I may have botched it. :D
[20:27] <bluesabre> D:
[20:27] <ochosi> bluesabre: weee, that we should definitely add to whiskermenu!
[20:27] <ochosi> i mean as a default action
[20:28] <Unit193> bluesabre: Thanks, wasn't sure if we were going to go for more 4.11 this cycle.
[20:28] <bluesabre> as much as we can get in before thursday
[20:28] <bluesabre> hopefully nick does the settings release soon
[20:28] <ochosi> maybe something like "search kitten" would do "catfish /home/$user kitten --start" and "search kitten everywhere" could do "catfish / kitten --start"
[20:29] <ochosi> bluesabre: we should remind him and otherwise you can just do the release
[20:29] <bluesabre> yeah
[20:29] <Unit193> libxfce4util?
[20:31] <Unit193> That and xfce4-mixer are the only things experimental has that Ubuntu doesn't.
[20:31] <bluesabre> it would probably make sense to grab them
[20:34] <Unit193> Our delta for -mixer is an epoch. >_x
[20:35] <ochosi> rly?
[20:35] <ochosi> how come?
[20:35] <bluesabre> probably pulseaudio or something
[20:35] <bluesabre> brb
[20:35] <ochosi> i don't think we have pulseaudio support in the mixer in ubuntu
[20:36] <ochosi> wonder how long it'll take until gst0.10 is gone from the repos
[20:36] <ochosi> maybe not too soon though, not sure
[20:36] <Unit193> https://launchpad.net/ubuntu/+source/xfce4-mixer/1:4.2.1-2ubuntu1 That's the first hit in the changelog for it.
[20:41] <bluesabre> wowza
[20:44] <ochosi> holy christ
[20:44] <ochosi> that was a while ago :)
[20:50] <bluesabre> ok, catfish does work as a whiskermenu action
[20:50] <bluesabre> so thats handy
[20:50] <ochosi> you just have to decide what the shortcut will be
[20:51] <ochosi> what did you think about the location substitution?
[20:51] <ochosi> or defaulting to some location like home by default
[20:51] <ochosi> weeee, sorry for that overuse of default
[20:51] <bluesabre> just default to home 
[20:51] <bluesabre> by default
[20:53] <ochosi> :)
[20:54] <ochosi> yup, i think that makes sense for most ppl
[20:54] <bluesabre> notice any issues or have any suggestions?  thinking about letting 1.2.0 out of the gate now
[20:54] <ochosi> lemme test the whisker-action
[20:54] <bluesabre> /path/to/catfish %s --start
[20:55] <ochosi> (also, you didn't say "test it now" before, so i haven't looked yet)
[20:55] <bluesabre> :D
[20:56] <ochosi> hm, the wording of "this process requires.." is not ideal maybe
[20:56] <ochosi> how about "This action requires administrative rights"?
[20:56] <bluesabre> sure, that sounds nicer and to the point
[20:57] <ochosi> mm, nice infobar stuff
[20:57] <ochosi> also the abort-infobar, i like it
[20:57] <Unit193> '...would do "catfish /home/$user kitten...' Ever heard of $HOME?
[20:57] <ochosi> "user aborted authentication." is not very elegantly put though, sounds a bit wooden :)
[20:57] <bluesabre> actually, the code actually works out so home is default, so you don't even have to provide a path
[20:58] <ochosi> Unit193: nope, there's no place like $HOME.
[20:59] <bluesabre> "You gave up trying to remember your password"
[20:59] <bluesabre> "Authentication cancelled" perhaps?
[20:59] <ochosi> yeah, maybe
[21:00] <ochosi> btw, not sure why the "esc" or cancel button don't work as responsively as they used to
[21:00] <bluesabre> possibly because locate is actually being used again... apparently that code got ignored the last few releases :)
[21:00] <ochosi> hm, it also seems to reload the list if i hit cancel
[21:00] <ochosi> ah, hehe
[21:00] <ochosi> so it'
[21:00] <ochosi> s a feature? :)
[21:00] <bluesabre> ;)
[21:02] <bluesabre> "reload the list"?
[21:05] <ochosi> ok, i guess i can reproduce it like this:
[21:05] <ochosi> enter e.g. "kittens", hit search, then after a few results hit cancel
[21:06] <ochosi> then *don't* change the search term, hit search again and then cancel again
[21:06] <ochosi> then it reloads the result-list a few times for me (at least twice)
[21:08] <bluesabre> ahhh
[21:08] <bluesabre> nice catch
[21:19] <bluesabre> fix pushed
[21:19] <ochosi> oh that was quick
[21:19] <ochosi> yup, that works
[21:20] <bluesabre> would have been faster, but http://grammarist.com/spelling/cancel/
[21:20] <ochosi> the fact that the cancelling is still very sluggish sucks a bit
[21:20] <ochosi> but yeah, at least locate is being used again i guess ;)
[21:21] <bluesabre> the app closes quickly even with locate, so thats something :)
[21:21] <ochosi> :D
[21:24] <ochosi> yup, the whiskermenu action rules
[21:24] <ochosi> nice stuff
[21:25] <ochosi> the rest works as planned as far as i can tell
[21:25] <ochosi> btw, i guess instead of a panel-plugin one could also try to pop up catfish (without window-deco) where whiskermenu was
[21:25] <ochosi> maybe there
[21:26] <ochosi> 's some mutual integration that could be done, passing around parameters and all
[21:26] <bluesabre> maybe, I'll have to think about that one
[21:27] <bluesabre> yay, my pbuilder finally built Unit193's package
[21:27] <bluesabre> now to test
[21:27] <ochosi> could also talk to graeme gott
[21:30] <bluesabre> right
[21:31] <ochosi> be back after one episode of sherlock...
[21:31] <Unit193> Wait, new ones or are you way behind?
[21:34] <bluesabre> session
[21:34] <bluesabre> first it was a failed build since pbuilder was out of date
[21:34] <bluesabre> then I had to update and try again
[21:34] <bluesabre> :D
[21:34] <bluesabre> but everything looks ok, uploading now
[21:35] <Unit193> Nono, I meant Sherlock. :P
[21:36] <Unit193> But, glad it's working.
[22:09]  * skellat notes that LP Bug #1297649 plus the linked bits from Debian may bring cause for an archive removal for Trusty and Utopic of twinkle if somebody on our end wants to spearhead such
[22:19]  * bluesabre release catfish 1.2.0 https://launchpad.net/catfish-search/1.2/1.2.0
[22:20] <bluesabre> re: twinkle, yikes
[22:21] <bluesabre> Unit193, Noskcaj, interested ^ ?
[22:21] <Unit193> In paperwork?  Nope.
[22:21] <bluesabre> D:
[22:21] <Noskcaj> paperwork: nope, catfish: Are you going to do the debian package or should i?
[22:22] <bluesabre> Noskcaj, if you want to, go ahead :)
[22:22] <Noskcaj> sure
[22:22] <Unit193> "twinkle's binaries are not seeded."  I see no reason for it to be an Xubuntu problem.
[22:22] <bluesabre> should be straight-forward, no packaging changes should be needed
[22:22] <Noskcaj> Anything non version-bump needed?
[22:22] <Noskcaj> ok
[22:23] <bluesabre> thanks :)
[22:23] <Noskcaj> Did you fix the about dialogue issue?
[22:24] <bluesabre> wrong version number displayed?
[22:24] <Noskcaj> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757828
[22:24] <bluesabre> yeah, that should happen no longer :)
[22:25] <bluesabre> the about dialog was hard-coded in the glade file, and now its smarter
[22:25] <Noskcaj> great
[22:25] <bluesabre> for the next release, I'll go to a python build system and then I won't forget that anymore ;)
[22:32] <Unit193> * Patch aclocal.m4 and configure to build on ppc64el.   We can likely just sync the 4.11 one then.
[22:33] <bluesabre> of which thing?
[22:38] <Unit193> Bleh, looks like a no.
[23:01] <ochosi> Unit193: i was way behind
[23:02] <ochosi> bluesabre: congrats on catfish
[23:02] <ochosi> now let's go and add a custom action to whisker as soon as catfish hits utopic
[23:05] <Unit193> ochosi: Ah, I see.  Didn't think they were due back yet.
[23:07] <ochosi> i still have a bit ahead of (lucky) me
[23:10] <ochosi> bluesabre: still wanting to look at lls?
[23:28] <bluesabre> hey ochosi
[23:28] <bluesabre> yeah, will do that one next
[23:29] <bluesabre> ochosi: careful, if you watch a few sherlocks, you'll have watched them all
[23:29] <Unit193> Hah, indeed.
[23:36] <ochosi> hehe, yeah, that's the worst part of it tbh
[23:38] <bluesabre> ochosi: xfce4-power-manager --version doesn't seem to output any version
[23:39] <ochosi> hah, indeed
[23:39] <ochosi> fun bug
[23:39] <bluesabre> was going to use that to verify versions :)
[23:41] <ochosi> hehe, bad idea
[23:41] <ochosi> i'm looking into it now
[23:41] <bluesabre> cool
[23:42] <bluesabre> I'll add a breaks for xfce4-power-manager << 1.3.0 when I package it, that should make it safe
[23:43] <ochosi> yeah, i think that's better than actually checking xfpm's version
[23:43] <ochosi> i mean it's possible, but obviously it doesn't work :)
[23:43] <bluesabre> it happens
[23:43] <bluesabre> catfish-1.0.3 said it was 1.0.2
[23:44] <ochosi> yeah, the xfpm 1.3.1 release said it was 1.3.0 in the release mail :)
[23:44] <bluesabre> who knows how that even happened ;)
[23:49] <ochosi> bluesabre: heh, try xfce4-power-manager --debug --version
[23:50] <bluesabre> ochosi: haha
[23:51] <ochosi> i'm still in the progress of debugging this
[23:51] <ochosi> not entirely sure what's going on there