[00:00] <Unit193> bluesabre: Merge request or direct push?
[00:00] <bluesabre> Unit193: feel free to direct push
[00:01] <Unit193> Done.
[00:01] <bluesabre> good sir
[00:01] <bluesabre> nice work
[00:07] <Unit193> That just leaves gmb and lightdm stuff.
[00:07] <bluesabre> Unit193: that's kind of my general stance with a lot of things, if you're in -dev I feel as though you should be able to commit changes and poke me after, or make merge requests and throw rocks at me
[00:08] <Unit193> bluesabre: Heey, I already passed you the patch in Jan! :P
[00:08] <bluesabre> I usually open up branches and whatnot as they are shared, but lose them when my browsers crash
[00:08] <Unit193> Hah. :D
[00:08] <bluesabre> Unit193: yup, and I failed to follow up quickly on it (as above) ;)
[00:08] <Unit193> And yeah, would do gmb myself but not sure if you want to replace it with parole.
[00:09] <bluesabre> can you share the gmb one again? I can take care of that one
[00:09] <bluesabre> (also gives me a chance to test that parole works)
[00:09] <bluesabre> ;D
[00:09] <Unit193> Eh, http://bazaar.launchpad.net/~xubuntu-dev/xubuntu-default-settings/trunk/view/head:/etc/xdg/xdg-xubuntu/xfce4/xfconf/xfce-perchannel-xml/xfce4-keyboard-shortcuts.xml#L26 just showed what two lines.
[00:10] <bluesabre> oh right
[00:10] <bluesabre> just need to do some grepping :D
[00:10] <Unit193> http://paste.openstack.org/show/M8PGeFpA5F2yqGGfgYSA/ was just an indication of what needed done, as well as modify the maintscript to remove the old file.  (One move is just from debian/ to usr/share/blah, doesn't actually move it on the filesystem.)
[00:10] <bluesabre> I'm going to get xenial on here full time this week so I start noticing more
[00:11] <Unit193> ...I didn't notice it in Xenial, but when I diffed the package to my forked version. :P
[00:11] <bluesabre> gotcha
[00:11] <bluesabre> yay, xenial vm is updated
[00:12] <Unit193> And, IIRC you didn't want to look into elementary-xfce-themes this cycle, understandably.
[00:14] <bluesabre> yes, let's plan to start that migration at the start of yappy
[00:15] <bluesabre> yappy... yak
[00:15] <bluesabre> calling it
 quick question, in the kernel version, 4.4.0-2  ==  4.4.1 vanilla ?
[00:31] <sergio-br2> nobody answered me in ubuntu+1
[00:49] <sergio-br2> found the info
[00:52] <bluesabre> looks like the greeter is getting confused (explaining the missing wallpaper)
[00:52] <bluesabre> http://archive.ubuntu.com/ubuntu/pool/universe/l/lightdm-gtk-greeter/lightdm-gtk-greeter_2.0.1-2ubuntu2.dsc
[00:52] <bluesabre> woops
[00:53] <bluesabre> well, it's in a copy buffer in my vm, and its long, so take my word for it
[00:53] <bluesabre> :D
[00:55] <bluesabre> or it could just be that things have moved around
[00:55] <bluesabre> anyway, a fix is on the way!
[01:58] <bluesabre> Unit193: https://bazaar.launchpad.net/~xubuntu-dev/xubuntu-default-settings/trunk/revision/594 look good to you?
[02:18] <Unit193> bluesabre: Heh, well should work, though *.maintscript is a bit easier and bzr mv is a bit cleaner diff/history.  I wonder though, how that works with the moved config right above, eg from trusty to xenial?
[02:35] <bluesabre> Unit193: yeah, used to git handling that for me, forgot that bzr is a bit inferior
[02:35] <bluesabre> Unit193: good good question
[02:36] <bluesabre> I'll test it tonight, and try a package upgrade in trusty and see what happens
[03:44] <bluesabre> ochosi: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1542927
[03:49] <bluesabre> bed time, bbl
[07:36] <flocculant> knome: ty - I've scrubbed them from my list of things to after the gci stuff :)
[07:36] <flocculant> bluesabre: \o/
[07:52] <flocculant> knome: imagemagick turned up quite early with something, I did mention it at the time - I hid them both in the menu
[08:29] <Noskcaj> bluesabre, menulibre and mugshot have RC bugs in debian for FTBFS. Should i be patching them or will you have the next stable releases out soon?
[09:13] <dkessel> i'm taking this from offtopic to here... what do you guys think about implementing a "low disk space" monitor as some kind of default process that gets configured for users? upon reaching "0 bytes" (or some other value), a notification might be shown periodically...?
[09:14] <flocculant> well
[09:14] <flocculant> 0 bytes is a bit late perhaps :)
[09:14] <dkessel> sure ;)
[09:15] <pleia2> I think that instead it would just be making one of the disk space tracking panel items a default component
[09:15] <pleia2> they change color as the disks get fuller
[09:15] <pleia2> but it would be terribly annoying if you had a disk you knew was near/full, or it was tracking another partition that is intentially full
[09:15] <flocculant> pleia2: I didn't even know they existed
[09:16] <dkessel> i have those on my laptop to watch space.
[09:16] <dkessel> that might work
[09:17] <dkessel> oh, no default package it seems...
[09:19] <dkessel> i am using "xfce4-fsguard-plugin" - are you using any, pleia2?
[09:21] <pleia2> that's the one
[09:22] <pleia2> shows up as "Free Space Checker" in the panel-add-stuff dialog
[09:22] <pleia2> but you're right, I had to install it, it's not a default package
[09:23] <dkessel> i will install it on all those systems next time i am on them... hopefully somebody will call me then before everything stops working next time...
[09:23] <dkessel> this time, printing stopped suddenly... last time it was something else...
[09:55] <Akxwi-dave> morning all
[10:41] <flocculant> hi Akxwi-dave 
[10:42] <Akxwi-dave> morning
[11:11] <bluesabre> Noskcaj: feel free to make the changes. I'm guessing the fix is probably this, https://bazaar.launchpad.net/~catfish-search/+junk/catfish-daily-debian/view/head:/debian/rules#L7
[11:20] <flocculant> bluesabre: I will do the testing call for 14.04 as soon as I see the images land at week end
[11:21] <flocculant> then we'll have a couple of days before 16.04 beta
[11:24] <bluesabre> flocculant: cool, I'll have a new xubuntu-default-settings and catfish uploaded by the end of the week for 16.04
[11:24] <bluesabre> doing some package upgrade tests
[11:25] <flocculant> nice
[11:26] <flocculant> we need really to make a call for some specific package tests I guess, after b1 would be best - be a mission to do that in between the two milestones
[11:28] <bluesabre> yeah
[11:28] <Akxwi-dave> sounds good..
[11:28] <bluesabre> and some 14.04->16.04 upgrade tests, guessing we probably have those
[11:28] <flocculant> we do 
[11:28] <Akxwi-dave> Was there any problems with the ppa's yesterday?  
[11:28] <flocculant> we don't need to worry about 12.04 to 14.04 at least \o/
[11:29] <bluesabre> Akxwi-dave: what sort of problems?
[11:29] <Akxwi-dave> tried updating my lappy but the ppas couldn't connect
[11:30] <Akxwi-dave> when doing the apt-get update
[11:30] <flocculant> I had that momentarily on Monday I thought - though it could have been yesterday
[11:30] <bluesabre> could be some canonical server issues
[11:30] <bluesabre> just try again after a while
[11:30] <Akxwi-dave> I'll check again later
[11:30] <Akxwi-dave> cheers
[11:30] <bluesabre> :)
[11:32] <Akxwi-dave> Incidentally, I upgrade my daily laptop from 15.10 to 16.04 a wekek or too ago, and its running really good
[11:32] <Akxwi-dave> not come across any major problems.
[11:32] <Akxwi-dave> In fact Civ 5 seems to run a lot better..  :-)
[11:33] <bluesabre> sweet
[11:33] <bluesabre> amd, nvidia, or intel gpu?
[11:33] <Akxwi-dave> Intel/Nividia 630M
[11:34] <bluesabre> using prime, or just one of those?
[11:34] <Akxwi-dave> tend to use the Nvidia using the Nvidia drivers
[11:36] <bluesabre> cool
[11:36] <bluesabre> I'm usually wary to upgrade at the early parts of the cycle, usually have to blacklist nvidia to get anything to show up
[11:37] <bluesabre> since the kernel tends to move faster than the nvidia folks :)
[11:40] <Akxwi-dave> :-) Well as there was nothing on Tv, I thought I'd give it a bash...  I haave another hard drive with xubuntu on for the lappy if thing went wrong
[12:00] <bluesabre> Unit193: putting this here sort of as a note to myself, also need to move the 01_ubuntu.conf provided by the lightdm-gtk-greeter package for the moved xubuntu config to work
[12:01] <Unit193> Fun..
[12:01] <bluesabre> this will probably affect any other lightdm-gtk-greeter config files
[12:01] <bluesabre> if anybody else ships them :)
[12:02] <Unit193> !find /etc/lightdm/lightdm-gtk-greeter.conf.d/ xenial
[12:02] <Unit193> !find /etc/lightdm/lightdm-gtk-greeter.conf.d/ xenial
[12:03] <bluesabre> oh boy
[12:03] <bluesabre> and I've forgotten the reason, why are we moving configs out of etc?
[12:05] <Unit193> Wouldn't it not affect them if you put lightdm-gtk-greeter in usr?  It shouldn't affect the ones in etc as they should be higher priority anyway, no
[12:05] <Unit193> ?
[12:06] <bluesabre> ah
[12:06] <bluesabre> thats a good point
[12:06] <bluesabre> I'll test that as well
[12:06]  * bluesabre gives Unit193 a bag of cookies
[12:06] <Unit193> :D
[12:08] <Unit193> Small things like 01_xubuntu.conf aren't really made to be edited (session=xubuntu) as they can just either be selected on the greeter, or overridden by a config file in /etc/lightdm/
[12:08] <Unit193> Avoids marking them config and going through the purge vs remove thing, and upgrade questions.
[12:09] <bluesabre> cool, that's the good answer I was looking for
[12:10] <Unit193> I wonder if 30_xubuntu.conf should be trimmed down, though. :P
[12:12] <bluesabre> I'll take a look at it while cleaning it up and tidying up the ubuntu conf at the same time
[12:21] <bluesabre> looks like I'll have to tweak the scripts a bit, 14.04 with customized greeter config does not migrate to 16.04
[12:22] <bluesabre> but I'll work on that later
[12:22] <bluesabre> time to get ready for work, bbl
[12:25] <Unit193> Have fun.
[14:58] <slickymasterWork> !team | Next community meeting, Wednesday, 17 February 2016 22:00 UTC
[15:04] <flocculant> thanks ubottu ... 
[15:04] <slickymasterWork> :P
[15:06] <flocculant> slickymasterWork: now, are you completely sure which day it is on :D
[15:06] <slickymasterWork> now I am, flocculant :D
[15:06] <slickymasterWork> but it took me a minute :P
[15:07] <flocculant> ha ha 
[15:07] <slickymasterWork> :)
[15:07] <slickymasterWork> anyway calendar and https://wiki.ubuntu.com/Xubuntu/Meetings updated
[15:08] <slickymasterWork> team calendar, that is
[15:08] <flocculant> yep 
[15:09] <flocculant> was looking to see why ^^ that wasn't showing up - it wouldn't - it wasn't on trello yet :p
[15:17] <dkessel> thanks for scheduling slickymasterWork :) good choice of day/time, too
[15:17] <slickymasterWork> sure dkessel 
[22:31] <flocculant> ochosi: hopefully you saw the same with gnome-software, I'd be surprised if you didn't - could you confrim bug 1544325
[22:31] <flocculant> or indeed anyone who might have had a look :D
[22:36] <flocculant> bluesabre: perhaps you could look and confirm it :p
[22:36] <flocculant> if you've got brave enough yet 
[22:36] <bluesabre> flocculant: can check in a vm at least
[22:37] <bluesabre> plenty of snapshots recently :)
[22:37] <Unit193> Not in stock repos.
[22:37] <flocculant> bluesabre: yea - fails in vm - I'm not losing printer in my working xenial :D
[22:37] <bluesabre> oh? thought I saw it pop up today
[22:37] <Unit193> Just refreshed caches and no installation candidate.f
[22:38] <flocculant> ppa still afaik 
[22:38] <flocculant> https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/gnome-software
[22:38] <bluesabre> alrighty then
[22:38] <flocculant> cheers m'dear
[22:43] <bluesabre> flocculant: I don't have system-config-printer installed (I do have -gnome installed though)
[22:43] <flocculant> yea
[22:44] <flocculant> well
[22:44] <bluesabre> looks like system-config-printer-gnome replaces it
[22:44] <flocculant> mmm
[22:44] <flocculant> I couldn't see any printer tools when I looked
[22:45] <knome> pleia2, you likely saw my bug about the flavours (download) page?
[22:45] <pleia2> alphabetical?
[22:45] <knome> pleia2, just wanting to check with you if you are fine with that too - and if it's ok to replace the ubuntu wiki wikipage to that description too
[22:45] <bluesabre> flocculant: https://i.imgur.com/OGu9gme.png
[22:45] <bluesabre> :)
[22:45] <knome> alphabetical, and the xubuntu description
[22:45] <pleia2> knome: yeah all good
[22:45] <knome> pleia2, good good :)
[22:46] <flocculant> bluesabre: so how you starting that? 
[22:46] <knome> bluesabre, "Software", what a nice app name :P
[22:46] <bluesabre> flocculant: searching for it in whisker
[22:46] <flocculant> printer?
[22:47] <bluesabre> knome: welcome to gnome3 apps, killing off the proper name for generic name
[22:47] <knome> bluesabre, ugh
[22:47] <bluesabre> knome: and ignoring GenericName in the XDG spec
[22:47] <bluesabre> FUTUREEEEE
[22:47] <knome> bluesabre, i'm ok with the menu name being dumb, and the window title being dumb, but the about windowm REALLY?
[22:47] <knome> s/m/,/
[22:47] <flocculant> bluesabre: http://i.imgur.com/u0mEQcR.png
[22:48] <knome> are the settings manager items still hidden in whisker?
[22:48] <bluesabre> flocculant: is that an older install?
[22:48] <bluesabre> knome: nope, present and accounted for
[22:48] <knome> mmh
[22:48] <flocculant> bluesabre: yea - but updated etc
[22:48] <knome> i'm sure flocculant is running the y ISO already
[22:48] <knome> ;))
[22:48] <bluesabre> flocculant: probably got lost at some point when that transition happened
[22:49] <flocculant> bluesabre: I'll redo it all now then
[22:52] <flocculant> bluesabre: I hope it is :)
[22:52] <flocculant> though I still don't like the usc replacement :p
[22:54] <bluesabre> it might just be difficult to love a software center in general
[22:54] <flocculant> I guesas
[22:55] <flocculant> I can cope with synaptic 
[22:55] <bluesabre> it will probably be better once its patched up
[22:55] <bluesabre> hopefully
[22:56] <bluesabre> doesn't take much to be better than USC ;)
[22:56] <flocculant> well
[22:56] <flocculant> does it see packages yet?
[22:57] <bluesabre> running pkcon to see if I can make it see packages
[22:57] <bluesabre> pkconf update -d
[22:57] <bluesabre> is what I found on google anyway :D
[22:58] <bluesabre> *pkcon
[22:58] <flocculant> :)
[23:35] <flocculant> really not going to add this to my daily xenial just yet :)
[23:38] <bluesabre> I wouldn't recommend this at this point
[23:40] <flocculant> nope 
[23:41] <flocculant> that's two of us :)
[23:41] <flocculant> I suppose tomorrow I could grab a random (other than kde) flavour and see what goes on there
[23:42] <flocculant> though I suppose anyone's fresh add-apt will fail - not just for us
[23:43] <bluesabre> mine worked, and it wasn't very long before yours
[23:44] <flocculant> yup
[23:45] <flocculant> I'll wait till some have got updated builds in the morning - then critical fail all over the iso tracker :p
[23:47] <flocculant> I do like it when - *buntu fail
[23:47] <flocculant> we can wait :)
[23:47] <bluesabre> mhm
[23:48] <flocculant> oh noes
[23:48] <bluesabre> :|
[23:52] <flocculant> bluesabre: so yet another 14.04 xfpm thing - what's the best course of action here - try the ppa?
[23:52] <bluesabre> :(
[23:52] <bluesabre> now what's wrong?
[23:53] <flocculant> who know's :|
[23:54] <flocculant> incoming
 why when i close the cover of my laptop the login screen appear i login then the screen keep being black.  i have to reboot,. but when he goes on sleep with cover up he recover perfecly ? is there a solution for that problem. in fact if when i close the cover the screen only go off it will do the job. i don't want it to sleep
[23:54] <flocculant> [23:48:40] <Guillaume2> xubuntu 14.04
[23:54] <flocculant> bluesabre: that ^^
[23:54] <bluesabre> ah that
[23:54] <flocculant> I just give up with pm stuff
[23:54] <bluesabre> easiest solution
[23:55] <flocculant> that'd be good 
[23:56] <bluesabre> "We are aware of some hardware/driver incompatabilities that were discovered after the release of 14.04. With limited resources, we are not able to test all combinations, and would recommend installing xscreensaver until the issue is addressed"
[23:56] <bluesabre> is probably what I would write
[23:57] <bluesabre> and/or some other locker software, gnome-screensaver as one
[23:57] <bluesabre> being unable to recreate the issue, we're really limited in fixing it
[23:58] <bluesabre> and some things just don't handle the VT switch well
[23:58] <flocculant> right
[23:59] <flocculant> I could go 'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaagh' 
[23:59] <bluesabre> lol
[23:59] <bluesabre> I did that at "bluesabre: so yet another 14.04 xfpm thing - what's the best course of action here - try the ppa?"
[23:59] <flocculant> about releasing when we have had 4 or 5 people telling us things :D