[10:12] <ochosi> hi everyone
[10:13] <ochosi> do we have a testcase for the thunar crashes written down somewhere?
[10:13] <ochosi> (background: a new patch was posted to bugzilla yesterday, i haven't reviewed it but in a quick test i didn't manage to make thunar crash)
[10:14] <flocculant> ochosi: http://packages.qa.ubuntu.com/qatracker/milestones/361/builds/117794/testcases
[10:16] <ochosi> ok nice
[10:16] <ochosi> yeah, so that one doesn't pass either
[10:16] <flocculant> not using it currently though
[10:16] <ochosi> filenames don't change
[10:17] <flocculant> ochosi: yea - that is unfortunately the case - hence my 'do we really have to use thunar' pov :)
[10:19] <ochosi> thunar in yak seems to pass the testcase for me here though
[10:21] <flocculant> ochosi: mmm - well just keep trying the testcase - it will fail in the end :)
[10:21] <ochosi> "the end"? :)
[10:21] <flocculant> that's half the issue from my pov - it doesn't constantly crash :(
[10:21] <ochosi> i've been running it for a few minutes now
[10:22] <flocculant> if it 'always' crashed then fair play
[10:22] <flocculant> it crashed on me about 20 times yesterday 
[10:23] <ochosi> well that's sorta the definition of a race condition...
[10:23] <flocculant> maybe so - didn't know that was the issue ;)
[10:24] <ochosi> btw i was revisiting the wording for notifyd settings dialog again yesterday
[10:24] <ochosi> how about "show or block notifications" for the applications tab?
[10:25] <ochosi> then i could reuse the "block" in the log tab and say "only log blocked applications" or something
[10:25] <flocculant> oh yuk :| ubiquity issue found that's not in ubuntu ...
[10:25] <ochosi> meh, ubiquity...
[10:25] <flocculant> ochosi: let me switch brain :)
[10:25] <ochosi> you have more than oneß
[10:25] <ochosi> ß
[10:25] <ochosi> ?
[10:25] <ochosi> (btw, the testcase for thunar is still running here, it hasn't crashed)
[10:25] <flocculant> yea - one that doesn't have ubuntu in it :D
[10:26] <flocculant> ochosi: :
[10:26] <flocculant> )
[10:26] <flocculant> ochosi: show or block sounds ok to me :)
[10:26] <ochosi> so the wording i've evaluated so far was: hide, block, mute, disable
[10:27] <ochosi> and for the opposites it would be: display, show, enable
[10:27] <flocculant> yea - I really dislike mute for it
[10:27] <ochosi> yup, i remember :)
[10:27] <flocculant> :)
[10:27] <ochosi> to be fair, in the future there may be sound support
[10:27] <ochosi> it's part of the spec at leastt
[10:28] <ochosi> (even though i personally hate sound for notifications...)
[10:28] <flocculant> I suppose from one pov mute works - eg it mutes the signal
[10:29] <flocculant> but berty up the road just running something is unlikely to think of that
[10:29]  * flocculant should reinstall your notifications
[10:34] <flocculant> oh dear - none of the a2 participants have their iso built turned on again :p
[10:34]  * flocculant can't double check this bug ... 
[10:35] <flocculant> ochosi: is it still at logging_rebased?
[10:35] <ochosi> humm, thunar is still running and not crashing...
[10:35] <ochosi> yeah
[10:36] <ochosi> it still is that branch
[10:36] <ochosi> really wanna push it to msater though...
[10:36] <flocculant> ta - I think I lost all that when I managed to kill my install fiddling with light/dm/locking
[10:37] <ochosi> sur
[10:37] <ochosi> e
[10:37] <ochosi> i can also send you some screenhots though
[10:37] <flocculant> sure
[10:38] <ochosi> http://i.imgur.com/401GJaj.png
[10:38] <ochosi> http://i.imgur.com/PIYvHdC.png
[10:39] <flocculant> that's old :)
[10:39] <flocculant> I remember the supermarket delivering :D
[10:39] <ochosi> that's the state of the branch plus some changes that i've incorporated
[10:39] <flocculant> ok - I grabbed it now etc
[10:39] <ochosi> fwiw the screenshots are not the state of the branch
[10:39] <ochosi> i'm a little ahead with string changes
[10:40] <ochosi> e.g. mute vs. block
[10:40] <ochosi> i'm still very unsure about the subtitle of the window
[10:41] <flocculant> not sure what to say about 'show/hide' if it's going to get sound support in the future
[10:41] <flocculant> ochosi: tbh I'm not convinced it needs a subtitle
[10:41] <ochosi> maybe not, but then that looks odd too
[10:42] <ochosi> then you have it in the window frame and in the white title section
[10:42] <flocculant> does it - or is that because you 'expect' subtitle?
[10:43] <flocculant> ochosi: or maybe Customise notifications and logging ?
[10:43] <flocculant> as it stands 'appear' covers 66.6% of what it does now :)
[10:44] <ochosi> you mean "customize how notifications appear"?
[10:44] <ochosi> i think yeah, the subtitle is sorta my (visual) expectation
[10:44] <ochosi> )
[10:45] <flocculant> yup - appear does not work for the log tab
[10:45] <ochosi> "customize your notification settings" :p
[10:45]  * ochosi wanders off to cook
[10:45] <flocculant> that works
[12:16] <ochosi> flocculant: ok, pushed some of the string improvements
[12:22] <flocculant> ochosi: that makes more sense to me now - looks good :)
[12:23] <flocculant> one thing I wonder about now - on app tab because it says show or block - you could maybe lose the on/off words? 
[12:24] <flocculant> or call them show/block instead? 
[12:25] <flocculant> logic - words say show or block - buttons say on and off - is on showing or blocking ...
[12:25] <flocculant> but  I could just be being a bit picky there :)
[12:26]  * flocculant takes his turn wandering off to cook 
[12:32] <ochosi> flocculant: yeah, that would indeed make sense. show/blocked maybe instead of just show/block?
[12:32] <ochosi> cause "block" sorta implies you wanna click if you wanna block...
[13:00] <flocculant> yup
[13:01] <flocculant> ochosi: oh - not sure if this is intentional or not - but if I click on an app in app tab it chnages the on/off state?
[13:02] <flocculant> almost like the whole name + button is the button
[13:09] <flocculant> https://sendvid.com/hkao24te just in case it isn't 
[13:29] <ochosi> flocculant: yes, that is intentional. should help people click an app
[13:29] <ochosi> also means it's not so problematic to drop the switch
[13:29] <ochosi> (hopefully)
[13:30] <ochosi> before though i have to consider whether i change the internal wording in the code and xfconf because atm it's mute everywhere
[13:31] <flocculant> ochosi: ack - just wanted to make sure it was intentional :)
[13:32] <flocculant> by mute everywhere - do you mean everywhere in xfce that this type of thing is - it is called mute?
[13:32] <flocculant> if so then I can understand you ummming and aahing on it :)
[13:33] <flocculant> anyway - back later today
[13:38] <ochosi> no, just in xfce4-notifyd
[13:38] <ochosi> muting is older than logging
[13:38] <ochosi> initially i called it that
[13:38] <ochosi> aka in the current stable release
[13:39] <ochosi> anyway, i think i'll push the current state to master
[13:58] <bluesabre> morning all
[13:59] <flocculant> ochosi: ok - well I hope I helped some :)
[13:59] <flocculant> morning bluesabre 
[13:59] <bluesabre> hey flocculant 
[14:04] <ochosi> hey bluesabre 
[14:04] <ochosi> how's it going?
[14:08] <flocculant> http://i.imgur.com/tHCyoEI.png
[14:08] <bluesabre> hey ochosi 
[14:08] <bluesabre> going pretty well
[14:08] <flocculant> that's confusing - all from this installation - all opened slightly different ways
[14:09] <bluesabre> Releasing new sgt-launcher right now
[14:09] <flocculant> \o/
[14:10] <ochosi> bluesabre: i'm prepping a release for taskman and notifyd atm
[14:10] <bluesabre> ochosi, \o/
[14:11] <ochosi> odd that the xfcetitleddialog doesn't seem to be working for flocculant 
[14:11] <flocculant> bluesabre: you likely to get to gtk3 settings today? 
[14:11] <bluesabre> flocculant, that is the plan
[14:11] <ochosi> bluesabre: maybe we have to cherry-pick a commit of mine from libxfce4ui
[14:11] <ochosi> bbabl
[14:11] <bluesabre> ochosi, alright
[14:11] <flocculant> bluesabre: cool :)
[14:25] <bluesabre> noticed that the new sgt-puzzles package in zesty is using gtk3
[14:26] <bluesabre> as a result, the menu is always faded because the embedded window is always in a non-active state
[14:27] <flocculant> the 'game' menu I assume you mean
[14:27] <bluesabre> yeah
[14:27] <flocculant> I didn't take a lot of notice of that I'm afraid
[14:28] <flocculant> and what's xfcetitleddialog when it's at home?
[14:28] <bluesabre> lazy
[14:28] <flocculant> ha ha 
[14:32] <bluesabre> https://launchpad.net/ubuntu/+source/sgt-launcher/0.2.2-0ubuntu1 uploaded, includes appstream data so it will show in gnome-software :)
[14:35] <flocculant> I might install it to see it showing up then :p
[14:35] <flocculant> not sgt ftr :D
[14:36] <bluesabre> :D
[15:55] <flocculant> bluesabre: it works as well :p
[15:56] <flocculant> knome: re the discussion sometime ago about oem
[15:56] <flocculant> I'd have the same discussion about whether we should test lvm/encryption
[15:57] <flocculant> akxwi-dave bluesabre ^^
[15:58] <akxwi-dave> very good point there flocculant 
[15:59] <flocculant> I'd be inclined to think more people are likely to do that than oem
[16:02] <akxwi-dave> oh yes, you cannot nelieve the size of the fucisha bush she wanted me to dig out
[16:03] <flocculant> sounds like The Great Esacpe then :)
[16:44] <flocculant> \o/ os-prober lost all my other installs 
[16:46] <flocculant> for one horrible minute I'd not just deleted the partition I wanted to ;)
[16:48] <akxwi-dave> ouch
[16:53] <flocculant> downgraded it - reran update-grub then updated it again :p
[16:55] <flocculant> I much prefer finding issues that aren't xubuntu 
[16:58] <akxwi-dave> hehe more fun that way
[17:38] <bluesabre> flocculant, your non-xubuntu-specific bugs are the best ones, keep those coming
[17:39] <bluesabre> flocculant, and yes, we should probably test lvm/encryption, though those will almost never be xubuntu-specific bugs
[17:39] <bluesabre> (but they could be)
[17:40] <flocculant> yea agree on the specificity there
[17:40] <flocculant> bluesabre: I can easily add the tests to our stuff on tracker
[17:41] <bluesabre> Sounds reasonable to me
[17:41] <flocculant> ok
[17:51] <flocculant> bluesabre: added now
[18:36] <knome> flocculant, yeah, why not
[18:37] <knome> flocculant, though i believe there is less (think: none) xubuntu-specific components involved with that
[18:37] <flocculant> well the only why not for this is the same as the why not for oem :p
[18:37] <flocculant> yea - but probably useful to at least test it
[18:37] <knome> because some components in an OEM installation are xubuntu-specific (those in the config)
[18:37] <flocculant> currently set it for mandatory - but we can see how it goes and change that
[18:37] <knome> but yes, maybe they could all be once a cycle or so
[18:38] <knome> but i'm open for all kinds of experiments
[18:38] <flocculant> we'll keep that for -offtopic with the gardening I think 
[18:38] <flocculant> :p
[18:40] <flocculant> knome: trouble with 'once a cycle or so' is when and then - bug might land post 'we checked that'
[18:41] <flocculant> we could change it to run-once - add OEM as run-once than 'forget about worrying' till milestones
[18:41] <flocculant> s/than/then
[18:51] <knome> once likely being later in the cycle
[18:51] <knome> bbl
[19:14] <flocculant> mmm
[19:35] <ochosi> evening all
[19:36] <flocculant> hi ochosi :)
[19:37] <ochosi> alrighty, i think i'll merge the logging_rebased branch to master of xfce4-notifyd now
[19:37] <ochosi> then translators can start their work
[19:37] <ochosi> which will actually be quite a bit this time around
[19:38] <ochosi> thanks for testing and input, flocculant 
[19:38] <flocculant> ochosi: np :)
[19:52] <ochosi> wow, even found and fixed another small bug with the log
[20:13] <flocculant> :)
[21:34] <ochosi> bluesabre: can you take a peek at whether taskmanager from git master is packageable, i.e. just to see whether i forgot any depends or so in the build process
[23:51] <bluesabre> libxfce4ui 4.13.1 added to xfce4-gtk3 ppa, xfce4-settings uploaded to same and currently building