[00:47] <Unit193> ...Did I do anything with that after the testbuild?
[01:00] <bluesabre> You ok Unit193 ?
[01:01] <Unit193> Should I not be?
[01:08] <bluesabre> :)
[01:12] <Unit193> Distracted with supper, packaging something else, and whatnot.
[01:12] <Unit193> Oh yes, backporting backages too.
[01:12] <Unit193> One of those needs a 'p'
[01:13] <bluesabre> That's cool. Currently shopping around.
[01:59] <Unit193> bluesabre: Hey, I meant to ask.  What happens if you have the lightdm config but not numlockx installed?
[02:26] <bluesabre> Unit193: oh
[02:26] <bluesabre> something bad
[02:31] <bluesabre> Suppose the options there are 1) add a wrapper script to which and run, 2) move to core-depends
[02:33] <Unit193> That's what I was thinking, except recommends.
[02:33] <Unit193> How bad?
[02:33] <bluesabre> greeter doesn't start
[03:07] <bluesabre> Unit193: solution! https://bazaar.launchpad.net/~xubuntu-dev/xubuntu-default-settings/trunk/revision/657
[03:08] <Unit193> Interesting way to check for it, but you'll want $@ here I think.
[03:10] <bluesabre> seems like either should be safe, but I'll swap that in
[03:10] <Unit193> $1 only passes the first arg.
[03:10] <bluesabre> numlockx only takes one arg
[03:13] <Unit193> LP #1693032
[03:14] <Unit193> "fixed"
[03:14] <bluesabre> :D
[03:14] <Unit193> That's freaking annoying.
[03:14] <Unit193> Can we get rid of that
[03:15] <Unit193> I honestly don't care what you interpret as 'that' either, the dep or package will do.
[03:16] <bluesabre> Yeah
[03:17] <bluesabre> the package is useful, so guess I'll be submitting a MP soon
[03:17] <Unit193> Thanks.
[03:17] <Unit193> Because gnome-session-quit, the reason for the dep, likely won't do crap in Xfce, LXDE, MATE, etc...
[03:18] <Unit193> I seem to remember someone asking me how one quits the Xfce session, thought it was Brian even...
[03:19] <bluesabre> Correct, it does nothing useful
[03:21] <Unit193> 05/#ubuntu-devel.2017-05-23.log.gz:17:12:53 < Unit193> What precisely does gnome-session-quit do?
[03:21] <Unit193> 05/#ubuntu-devel.2017-05-23.log.gz:17:14:19 < bdmurray> gnome-session-quit - End the current GNOME session
[03:21] <Unit193> 05/#ubuntu-devel.2017-05-23.log.gz:17:14:45 < bdmurray> There's a reboot button in software-properties-gtk that I'm guessing doesn't do anything on Lubuntu or Xubuntu.
[03:21] <Unit193> 05/#ubuntu-devel.2017-05-23.log.gz:17:15:02 < Unit193> xfce4-session-logout --reboot
[03:21] <Unit193> 05/#ubuntu-devel.2017-05-23.log.gz:17:15:29 < bdmurray> Unit193: will there be a prompt too?
[03:21] <Unit193> 05/#ubuntu-devel.2017-05-23.log.gz:17:15:55 < Unit193> If you want that, drop '--reboot'
[03:21] <Unit193> 05/#ubuntu-devel.2017-05-23.log.gz:17:17:24 < bdmurray> Unit193: Thanks
[03:24] <Unit193> I remembered correctly! \o/
[03:24] <bluesabre> nice
[03:25] <bluesabre> was actually commenting on the bug with that info
[03:26] <Unit193> Hah, whoops.  I just asked.  Bug is likely better.
[03:29] <bluesabre> Unit193: actually, https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1693038
[03:29] <Unit193> NIce. :/
[03:32] <bluesabre> added a ping comment to that bug
[03:32] <bluesabre> thanks for the notice Unit193 
[03:33] <Unit193> "Next time don't get so annoyed at GNOME though" I know. :(
[03:33] <bluesabre> Also added to xubuntu-b-bugs
[03:35] <bluesabre> Looks like lp is having some issues now
[03:36] <bluesabre> thanks for the -terminal upload
[03:37] <Unit193> ...I still forgot notifyd didn't I?
[03:37] <bluesabre> Yes
[03:37] <bluesabre> Didn't want to say that outright
[03:37] <bluesabre> :D
[03:37] <Unit193> xfce4-notifyd_0.4.2-0ubuntu1_source.changes in ~/ !
[03:40] <Unit193> OK, I have my newer, shinier terminal.
[03:40] <bluesabre> :)
[03:40] <Unit193> -notifyd dput.
[03:43] <bluesabre> hooray!
[03:43] <bluesabre> thanks Unit193, I'll stop nagging you now for a while
[03:44] <Unit193> bluesabre: Nono, thanks.  I just kept getting distracted by others. :P
[03:45] <bluesabre> anyway, that's everything I had hoped to land by today, so nice to see us where we are
[03:45] <Unit193> https://launchpad.net/~xubuntu-dev/+archive/ubuntu/staging/+packages has the backports, and https://launchpad.net/~unit193/+archive/ubuntu/xfce/+packages has the shiny terminal.
[03:46] <bluesabre> thanks a bunch Unit193 
[03:46] <Unit193> 'Course.
[03:48] <bluesabre> flocculant: going to work on the blog post in the morning so we can get that out for the weekend and prior to b1 testing
[03:54] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: [trunk] r657 * usr/bin/xubuntu-numlockx,... (by Sean Davis)
[03:54] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: [trunk] r658 Replace bash arg param (by Sean Davis)
[03:54] <bluesabre> long day, nighty everyone
[03:56] <Unit193> G'nighty!
[05:54] <flocculant> bluesabre: ok
[07:31] <flocculant> bluesabre: nvm re grub btw - they finally seen it elsewhere - marked mine as a dupe
[07:32] <Unit193> Link?
[07:33] <Unit193> nvm.
[07:33] <flocculant> :D
[10:54] <bluesabre> https://wiki.bluesabre.org/bionic_changes refreshed
[10:54] <Unit193> You're up again?  It's like you do that every day.
[10:55] <bluesabre> Crazy right
[10:55] <Unit193> Hopefully we got everything done in time for FF..
[10:55] <bluesabre> thunar-print might(?) need a FFe
[10:56] <bluesabre> otherwise, I think we're good
[10:58] <Unit193> bluesabre: I helped debug an issue I found with an upstream.  Turns out if one uses --disable-silent-rules, something "breaks".  That's an odd one.
[10:58] <flocculant> morning bluesabre 
[10:58] <bluesabre> morning flocculant 
[10:58] <bluesabre> Unit193: that sounds bad
[11:01] <ochosi> hey morning
[11:01] <ochosi> i have another easy MR for default settings: https://code.launchpad.net/~ochosi/xubuntu-default-settings/default-tiling-shortcuts/+merge/340278
[11:02] <ochosi> just kb shortcuts for stuff we didn't have before (tiling)
[11:02] <ochosi> should be a no-brainer hopefully
[11:02] <Unit193> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751266 \o/
[11:02] <ochosi> i will finalize thunar-print today
[11:04] <bluesabre> thanks ochosi
[11:07] <ochosi> if you wanna add your opinion to the default shortcuts for tiling, that'd be awesome
[11:07] <bluesabre> Added a comment already
[11:07] <bluesabre> I like the idea
[11:07] <ochosi> we can also push that after FF
[11:08] <ochosi> it's fairly straightforward
[11:08] <bluesabre> FF was last night, so anything at this point is after FF :)
[11:08] <ochosi> yeah, just saying :)
[11:08] <ochosi> it's not really a feature
[11:08] <bluesabre> Agreed
[11:08] <bluesabre> Doesn't require FFe
[11:10] <ochosi> there's one more small thing wrt to thunar uca that i would like to propose
[11:10] <ochosi> currently "open terminal here" only works on directories
[11:11] <ochosi> when not using the icon view, but one of the two list views, it's a little hard getting a terminal open in the current directory (with the mouse at least)
[11:11] <ochosi> so enabling it on files too would solve that
[11:11] <ochosi> would simply open the terminal in the folder where the file is located
[11:11] <ochosi> so no string change or anything necessary, just a tiny amendment of the thunar uca
[11:12] <ochosi> (can also propose a MR for that)
[11:12] <bluesabre> That sounds handy
[11:13] <ochosi> very easy fix
[11:13] <ochosi> i can also push it straight if we all agree
[11:13] <ochosi> it's just adding four lines to the uca.xml.in (matching on all files)
[11:14] <bluesabre> Do it
[11:14]  * ochosi does it
[11:18] <flocculant> don't do it
[11:18] <flocculant> :p
[11:18] <ochosi> :D
[11:18]  * ochosi waits patiently
[11:20] <ochosi> actually i just noticed that the behavior changes slightly...
[11:21] <ochosi> currently if you click "open terminal here" on a directory it opens it *inside* that directory
[11:21] <ochosi> with my change, it opens the terminal in the parent directory
[11:21] <ochosi> which may not be what the user wants :/
[11:21] <ochosi> (because you have to change exo-open --working-directory %f to %d)
[11:22] <ochosi> only alternative would be to create a second "open terminal here" custom action for files and show the two selectively in the correct context
[11:22] <ochosi> hmpf
[11:22] <ochosi> could be noted in the description of the custom action that one is for files and one is for directories...
[11:22] <ochosi> thoughts..?
[11:23] <flocculant> well - I'd say if I told it to open terminal in Desktop - that's where I'd want it - are you saying the change doesn't do that?
[11:23] <ochosi> (the workaround described above with two actions works fine btw, already tested it. they only show up in mutually exclusive contexts, so it always works and the user only notices that there are two when going to the "Configure custom actions..." dialog)
[11:24] <ochosi> if you are in e.g. detail view in thunar and right-click a directory (e..g desktop) then currently it'll open the terminal there (~/Desktop)
[11:24] <flocculant> right
[11:24] <ochosi> with the simple patch that behavior would change to opening just ~ instead
[11:25] <ochosi> "~" being the parent of the right-clicked folder
[11:25] <flocculant> I see
[11:25] <ochosi> that's probably not desirable
[11:25] <ochosi> and a change in behavior
[11:25] <flocculant> I assumed as much just checking - I'd say that's not desirable
[11:25] <ochosi> but we can enable "Open terminal here..." on files too with a second, almost identical custom action
[11:26] <flocculant> yup understand that
[11:26] <ochosi> which shows up only on files and uses %d (directory of selected path) instead of %f (full path incl. filename)
[11:26] <ochosi> (sorry, that was all very verbose now :))
[11:26] <flocculant> ha ha 
[11:27] <flocculant> I'd guess that if users don't generally see that - it'd be ok. eg it just works
[11:27] <flocculant> I'd see something in custom actions pretty quick :D
[11:28] <ochosi> yeah, only users playing with custom actions would notice
[11:28] <ochosi> and even then it's not a problem
[11:28] <flocculant> yup
[11:28] <ochosi> we can explain it in the description
[11:28] <flocculant> yea
[11:28] <ochosi> so i guess i'll push that instead :p
[11:28] <flocculant> :)
[11:28] <flocculant> me has 2 open as root options
[11:29] <knome> pleia2, the frontpage looks okay to me :P
[11:30] <ochosi> flocculant: hehe, nice
[11:32] <ochosi> native speakers: is this an ok string? "Open terminal in the folder of the selected file"
[11:33] <ochosi> (just fyi, i'm on my private xfce hackathon today - took a day off from work)
[11:33] <flocculant> oh yea 
[11:33] <flocculant> I wasn't expecting to be home - but Southern England and 'some' snow :|
[11:33] <flocculant> 3 hours and more to do 16 miles yesterday so I didn't bother today ;)
[11:34] <flocculant> that string is ok - bit long winded
[11:34] <flocculant> is all
[11:35] <flocculant> you could s/in the/at selected file's folder
[11:36] <ochosi> yeah, that's nicer indeed
[11:37] <Unit193> "Open terminal in containing directory" :>
[11:38] <flocculant> yea - that sounds better Unit193 
[11:38] <knome> yes, folder is a physical thing too :P
[11:38] <Unit193> Oh, sorry.  I didn't mean to be helpful.
[11:39] <flocculant> Unit193: that's ok - carry on :)
[11:39] <knome> Unit193, haa haa (in Nelson's voice)
[11:40] <flocculant> ochosi: re your xfce hacky thing - actually about till later so I can clone and check things if it helps
[11:40] <ochosi> hehe, alright alright, i'll change the string again :)
[11:40] <flocculant> lol
[11:41] <ochosi> pushed
[11:41] <ochosi> hope you're all happy now :p
[11:41] <flocculant> :)
[11:44] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: [default-tiling-shortcuts] r659 Add default shortcuts for window tiling... (by Simon Steinbeiß)
[11:44] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: [trunk] r659 Additional open-terminal-here custom action for Thunar for f... (by Simon Steinbeiß)
[11:44] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: [trunk] r660 Improve open-terminal-here string... (by Simon Steinbeiß)
[11:44] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: [trunk] r661 Improve string again... (by Simon Steinbeiß)
[11:45]  * flocculant ignores swissbot for the day ...
[11:46]  * Unit193 petpets SwissBot.
[11:46] <Unit193> There, there.
[11:46] <flocculant> ha ha ha 
[11:50] <ochosi> lol
[11:50] <ochosi> bluesabre: still there or did you go to work already? :)
[11:51] <ochosi> Unit193: anything else we need taken care of for 18.04?
[11:51] <Unit193> No idea.
[11:51] <bluesabre> ochosi: still here, doing some blog post writing with floc
[11:51] <ochosi> ah ok
[11:51] <Unit193> I might know tomorrow.
[11:52] <ochosi> bluesabre: xfdesktop4 is still on your list, right?
[11:52] <ochosi> i think it's in no blueprint, is it?
[11:52] <ochosi> if not, i'll at least add it there now
[11:52] <bluesabre> I think I fixed that?
[11:52] <ochosi> ah kewl
[11:52] <ochosi> i didn't check
[11:52] <bluesabre> which xfdesktop thing?
[11:52] <ochosi> just maybe missed the announcement
[11:52] <ochosi> the accountsservice thingy
[11:53] <ochosi> for the greeter
[11:53] <Unit193> Fixed.
[11:53] <ochosi> \o/
[11:53] <bluesabre> Yup, resolved.
[11:53] <Unit193> ochosi: You running xubuntu-dev/staging?
[12:05] <ochosi> Unit193: yes, i just didn't check the greeter/lockscreen recently i guess :p
[12:05] <ochosi> bluesabre: can there really be two keyboard shortcuts bound to the same xfwm4 command?
[12:05] <Unit193> /staging is for Artful.
[12:07] <bluesabre> ochosi: we have multiples already for Xf86* keys and Ctrl+Alt+ version variants
[12:08] <ochosi> oh
[12:08] <ochosi> in that case
[12:08] <ochosi> but i think not for xfwm4, only for "normal" shortcuts
[12:09] <ochosi> that's an unfortunate difference, doesn't seem to work for xfwm4 afaict
[12:33] <bluesabre> ah, darn
[12:33] <bluesabre> ochosi: can you go ahead and submit a FFe for thunar-print so we might get that preapproved today before uploading this weekend?
[12:34] <bluesabre> I would, but I'm ahead to run out the door
[12:34] <bluesabre> *about
[12:34] <bluesabre> :D
[12:40] <ochosi> ok sure
[12:40] <ochosi> i'll do that now
[12:40] <ochosi> just fixing up the script real quick
[12:40] <ochosi> (switching from mimetypes back to extensions, as mimetypes seem to be so broken and inconsistent...)
[12:48] <Unit193> !info shellcheck
[13:09] <ochosi> Unit193: nice, didn't know about that. didn't throw any warnings or stuff with the thunar-print script (as i'll push it in a few mins)
[13:09] <ochosi> so that's a good thing i guess :)
[13:16] <ochosi> Unit193: ok, you can review again, should be all good now: https://code.launchpad.net/~ochosi/xubuntu-default-settings/thunar-uca-print/+merge/340058
[13:18] <ochosi> once you approve, i'll file for FFe
[13:49] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: [thunar-uca-print] r654 Switch from mimetype-matching back to extensions... (by Simon Steinbeiß)
[13:49] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: [thunar-uca-print] r655 Update patterns to match thunar-print script... (by Simon Steinbeiß)
[13:49] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: [thunar-uca-print] r656 Fix small issue in thunar-print extension script... (by Simon Steinbeiß)
[13:49] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: [thunar-uca-print] r657 Note cleaning of whitespace from changelog... (by Simon Steinbeiß)
[15:09] <knome> slickymasterWork, will you announce our sprint on tue on the ml?
[15:20] <slickymasterWork> haven't thought of that
[15:20] <slickymasterWork> do you see it as necessary?
[16:05] <flocculant> slickymasterWork: depends if you want to give people a chance to join in I guess
[16:06] <slickymasterWork> fair enough
[16:06] <slickymasterWork> I'll do it
[21:32] <ochosi> bluesabre: just for your update: i
[21:32] <ochosi> crap
[21:33] <ochosi> bluesabre: just for your update: i've not filed for FFe for thunar-print yet but am waiting for Unit193's final review. so far everything is tested and works, it really was just a switch back from mimetypes (nice dream) to file extensions (at least it works as expected)
[22:27] <Unit193> ochosi: I'll go with sure, but I'll note that the last call isn't guarded.
[22:28] <ochosi> what which where?
[22:28] <ochosi> (sry, i'm somewhere else currently)
[22:28] <ochosi> wanna comment inline again so i can take a look a little later?
[22:28] <ochosi> (or alternatively be more verbose in here so i have an easier time following up)
[22:39] <Unit193> Oh sure, the lpr calls don't check for the command, though one might argue that anyone wanting to print but without cups is a bit on their own.
[22:57] <Unit193> (Also -x $(command -v foo) is a bit redundant as command already checks that.)
[23:01] <ochosi> Unit193: ah you mean "command -v" already checks for executable?
[23:02] <ochosi> added the cups if
[23:08] <ochosi> bluesabre, Unit193: started to prepare FFe https://bugs.launchpad.net/ubuntu/+source/xubuntu-default-settings/+bug/1753015
[23:08] <ochosi> feel free to contribute to the description
[23:09] <ochosi> night y'all
[23:09] <ochosi> (at least nobody can say i was lazy at today's hackathon ;))
[23:10] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: [thunar-uca-print] r658 thunar-pring: Check for CUPS and send a notification if it's... (by Simon Steinbeiß)