[00:47] <krytarik> knome: Do you insist on using the larger mouse logo in the header of the scrolled view on smaller screens, or can we just use the usual one with the name included, too?
[00:51] <krytarik> (In case of the latter, I have a solution worked out already.)
[01:12] <krytarik> (→ http://paste.openstack.org/show/fwuL02wo8nQ3d7VPsCSA/ )
[03:00] <bluesabre> late late evening all
[14:00] <flocculant> bluesabre: I did 3 tasks thunar/menulibre and parole - just to confirm new bugs and upstream where it's possible
[14:38] <flocculant> afternoon all 
[14:39] <bluesabre> hey flocculant 
[14:40] <flocculant> hi bluesabre :)
[14:42] <bluesabre> flocculant: anything I need to do with that? I'm at home today, so can help take care of tasks
[14:45] <flocculant> bluesabre: nope - all I did was add them - then wait for people to take it up and possibly some might contact me
[14:46] <flocculant> https://codein.withgoogle.com/dashboard/tasks/5713974762930176/
[14:46] <flocculant> for instance is the thunar one
[14:49] <bluesabre> seems to be private to you
[14:49] <bluesabre> 403 here
[14:49] <flocculant> mmm
[14:49] <Akxwi-dave> hi guys sorry, was away with the fairies there....
[14:50] <flocculant> bluesabre: perhaps because it's not live yet 
[14:50] <bluesabre> probably
[14:50] <flocculant> hi Akxwi-dave :)
[14:51] <flocculant> bluesabre: http://i.imgur.com/aDiCHJ4.png
[14:51] <bluesabre> flocculant: cool, seems reasonable
[14:52] <flocculant> yea - the first link is a newest first listing of thunar new bugs in LP, second is what bugzilla shows for thunar
[14:53] <flocculant> not going to do anything else unless someone in 'team' thinks of something 
[14:53] <flocculant> current thinking is if the few tasks I did for us get finished I'll add similar again :)
[14:54] <bluesabre> cool cool
[14:55] <bluesabre> what sort of tasks do ubuntu proper and kubuntu have listed?
[14:55] <flocculant> not sure about kubuntu
[14:55] <flocculant> ubuntu has a bunch of phone stuff, seen some mir tasks
[14:55] <flocculant> there's 97 listed :D
[14:56] <bluesabre> nice
[14:56] <flocculant> updating doc(s)
[15:04] <flocculant> Akxwi-dave: I've had people asking how to package testing, I think that a session in the new year for that will be useful
[15:07] <Akxwi-dave> Deffo...  I've got 2 weeks off at xmas so will get something better worked out for New Year just for PAckage Testing
[15:08] <flocculant> Akxwi-dave: feb looks best - pointless straight after xmas - feb has 3 package calls in wk 1-3 and then beta 1 in week 4 
[15:09] <Akxwi-dave> what time in feb is the 1st package call?
[15:09] <flocculant> Akxwi-dave: http://tracker.xubuntu.org/#tab-calendar
[15:10] <flocculant> http://pad.ubuntu.com/xubpktesting  - we can use that to work things out 
[15:11] <flocculant> we could run it 30/31 Jan just after alpha 1 perhaps
[15:12] <Akxwi-dave> thats what i was thinking doing it a week before ist call
[15:13] <flocculant> we can always move things about - 1 of the 3 pkg test calls is the run-once/optional stuff - we could bring that back then move the 4th priority call forward a week
[15:18] <Akxwi-dave> leave it with me I'll see what I can come with..   oh and if i try to acess the xubpktesting it says I dont have permission.. :-)
[15:19] <flocculant> oh meh you need adding to the group https://launchpad.net/~ubuntu-etherpad join that team
[15:19] <flocculant> eventually someone will add you then you can use the pad(s) 
[15:19] <flocculant> we use them a lot here 
[15:20] <flocculant> pleia2: can add you probably - don't know where to go ask anymore tbh 
[15:20] <Akxwi-dave> :-)
[16:08] <Akxwi-dave> flocculant, bug https://bugs.launchpad.net/ubuntu/+source/menulibre/+bug/1515184  doesn't seem to affect the MenuLibre on 15.10 with latest packages installed
[16:09] <Akxwi-dave> Just ran the testcases on both 16.04 and 15.10.. only getting the crash on 16.04
[16:09] <flocculant> that's useful for bluesabre 
[16:09] <Akxwi-dave> both have the ppa's installed and uptodate
[16:09] <flocculant> yep
[16:09] <flocculant> add it to the bug for him :)
[16:09] <Akxwi-dave> will do
[16:12] <Akxwi-dave> bug report on Launchpad updated
[17:03] <knome> krytarik, silly one
[17:04] <knome> krytarik, i would probably keep the icon and the regular text as we have now
[17:04] <knome> krytarik, the logo becomes unreadable after a while
[17:04] <knome> krytarik, in the latest updates, when resolution is <600, we're now *always* showing the compact format
[17:13] <flocculant> bluesabre: <balloons> flocculant, the first task taken was to run the manual tests for xubuntu :p
[17:13] <flocculant> back to fighting grub 
[17:30] <pleia2> flocculant: I only could while on the CC, can ask in #ubuntu-community-team now for folks who can approve re: etherpad
[17:32] <pleia2> but someone should approve pretty quickly either way
[17:33] <flocculant> pleia2: okey doke - I did think that ^^ 
[17:33] <flocculant> and I forget things asap nowadays :)
[17:33] <pleia2> hehe
[17:33] <flocculant> he needs to sort it anyway - we all use pads often :)
[17:34] <bluesabre> flocculant: awesome
[17:35] <flocculant> bluesabre: I thought so too :)
[17:43] <knome> hello pleia2 :P
[17:44] <pleia2> o/ knome 
[17:44] <knome> pleia2, maybe you saw - or maybe not - some updates for website pushed into branch, also visible on the staging site
[17:45] <knome> pleia2, http://tracker.xubuntu.org/#tab-details/text=(r+spec=xubuntu-x-web+sort=assignee+sortdir=asc
[17:47] <pleia2> ok
[17:48] <slickymasterWork> bluesabre, I confirmed bug 1511053
[17:49] <knome> wondering if there is something else we want fixed with this batch of updates
[17:51] <slickymasterWork> knome I was thinking that we could start to address the move of the translations of the ubiquity slideshow right after new year
[17:51] <slickymasterWork> is it ok with you
[17:51] <slickymasterWork> ?
[17:51] <knome> slickymasterWork, yes, that works for me, or you can start working on it now as well
[17:52] <slickymasterWork> I won't have much time availabke until then, but if I manage to, I will
[17:52] <slickymasterWork> * available 
[18:05] <bluesabre> slickymasterWork: great, thanks.  I'll tackle that today
[18:05] <slickymasterWork> you're welcome bluesabre :)
[21:43] <pjotter> I was having a little chat with knome on #xbuntu just a while ago about light-locker
[21:43] <pjotter> Light-locker is giving me so many problems with my hardware, that I have given up trying to fix it and just deinstall it.
[21:44] <pjotter> For a casual user like myself, it seems that light-locker doesn't actually add much to the system. Much of the things you can do with light-locker, you can also do in power-manager.
[21:45] <pjotter> Is this true? And can I safely remove light-locker?
[21:45] <pjotter> I have been running Xubuntu for quite some time without light-locker and it seems to work fine now.
[21:46] <Unit193> Lock your computer → Ctrl+Alt+F7
[21:46] <pjotter> I quess my question is: Why is light-locker in the distro?
[21:46] <pjotter> Especially as it causes a lot of problems with many computers (I have seen).
[21:48] <pjotter> Also, why add an application to the system that (in large) overlaps functionality with another application?
[21:49] <pjotter> maybe I'm missing something here?
[21:49] <Unit193> As I said, try locking your computer then hitting Ctrl+Alt+F7.
[21:50] <pjotter> Unit193: That didn;t do much I'm afraid. What is it supposed to do?
[21:51] <Unit193> Seems you logged out?  Anywho, when you use  dm-tool switch-to-greeter, as locking should do now, you can easily get back into your session without entering the password.  That's because lightdm isn't a lock screen, light-locker is.
[21:57] <pjotter> My problems with lightlocker are not so much with how it functions. But when lightlocker is installed, after 10 minutes the screen goes blank. No matter what I set in light-locker. It seems light-locker settings are completely ignored on my system.
[21:58] <pjotter> So what I do: I deinstall light-locker and set the appropriate settings (screen blanking etc) in power-manager.
[21:59] <genii> Sounds like lightlocker might not actually be working at all and then dpms kicks in on the monitor
[22:00] <pjotter> All I know is that everything works as expected when light-locker is removed
[22:01] <pjotter> I don't really have a need for locking the screen so I figured I don;t loose much with light-locker gone.
[22:05] <pjotter> From what I understand from knome, not many users experience these problems with light-locker. Maybe it's just my bad luck. I have installed Xubuntu on many different systems and on nearly all of them I had to disable light-locker to get the screenblanking to work. Could this be an issue that only effects amd64?
[22:12] <pjotter> knome, can I pm you for just a sec?
[22:19] <ochosi> late evening everyone
[22:19] <pjotter> hi ochosi
[22:20] <ochosi> hi