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