[00:02] <flocculant> nairwolf - all good thanks, none of those appear to be xubuntu issues though :)
[00:02] <flocculant> all you can hope is someone somewhere cares
[07:13] <knome> good day
[07:58] <nairwolf> Hi, why there is no build for 20160911 ? 
[07:58] <nairwolf> Usually, it happens on the morning
[08:11] <flocculant> no idea - rebuilding now
[08:21] <nairwolf> okay
[08:21] <nairwolf> the build is automatic, right ? 
[08:21] <flocculant> yep - unless someone triggers it manually - like I just did :)
[08:22] <nairwolf> okay
[08:23] <nairwolf> If the build couldn't be done this morning, does it mean there is an issue with the build ? 
[08:24] <flocculant> http://people.canonical.com/~ubuntu-archive/cd-build-logs/xubuntu/yakkety/
[08:24] <flocculant> https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/yakkety/xubuntu
[08:26] <nairwolf> thank you for the links
[08:26] <nairwolf> I'm going to bookmarks them
[08:26] <nairwolf> so, I have time to have a breakfast during the build
[08:27] <flocculant> oh yea - be a while till they get to the tracker 
[08:36] <nairwolf> ok
[08:38] <nairwolf> flocculant: do you have some issues when you try to come back from "sleep mode" with yakkety ?
[08:38] <nairwolf> In fact, I have this issue on my actual computer, and I've verified that yesterday with the test computer
[08:38] <nairwolf> I should test it more precisely to write a bug report
[08:47] <flocculant> no issues here - never suspend
[08:47] <flocculant> but I can try :)
[08:48] <nairwolf> maybe it happens only with real hardware
[08:48] <nairwolf> I never tried on a VM
[08:49] <flocculant> nairwolf: so what issues do you see?
[08:54] <nairwolf> A black screen. It's simple, I can't recover from the sleep mode
[08:54] <flocculant> yup 
[08:54] <nairwolf> but, I will test it more accurately to try to understand what happens
[08:54] <flocculant> can confirm that
[08:55] <nairwolf> I don't wnat to do it on my actual computer
[08:55] <flocculant> I got unlock screen, then got a lock screen I couldn't escape from
[08:55]  * flocculant blames power manager and bluesabre today :p
[08:56] <nairwolf> I should have said that earlier
[08:56] <nairwolf> because I've seen that since I've installed yakkety on my actual computer (and we talked about my installation few days ago)
[08:56] <flocculant> right
[08:57] <nairwolf> I wanted to confirm that on a second computer, but I forget to do it
[08:57] <flocculant> this is exactly why I've been trying to get people to run the dev install :)
[09:00] <flocculant> it's not suspend - it's an issue with locking
[09:02] <flocculant> nairwolf: you can see the same thing just by locking screen
[09:04] <nairwolf> the fact is my computer has sometimes his own problem related to hardware...
[09:05] <nairwolf> sorry ^^
[09:05] <nairwolf> by the way, I have also something weird when I boot
[09:05] <nairwolf> It's really really slow
[09:05] <nairwolf> and there is a message which says "check partitions"
[09:05] <nairwolf> but maybe it's related to my dual-boot
[09:15] <flocculant> bluesabre: bug 1622303
[09:21] <nairwolf> thank you
[09:59] <bluesabre> hey flocculant 
[09:59] <bluesabre> I just saw that bug and tested it out... seems related to light-locker
[10:00] <flocculant> bluesabre: so you see it too I assume
[10:00] <flocculant> yea - did think afterwards should have been light locker :)
[10:06] <Unit193> debhelper 10 uploaded.
[10:06] <bluesabre> flocculant, can you switch to VT1 and run "killall light-locker", then back to VT8 and try to unlock and see if that works for you?
[10:06] <flocculant> poor old debhelper 9 - no-one cares :(
[10:06] <flocculant> bluesabre: yep - trying now
[10:09] <flocculant> bluesabre: yup killing light-locker does it
[10:09] <flocculant> however
[10:10] <flocculant> had music playing when I locked - when I 'unlocked' could hear music again, so it appears to be unlocking 
[10:14] <bluesabre> so, it gets you back to the desktop fine?
[10:14] <flocculant> killall does yes
[10:15] <flocculant> what I'm trying to say is that while there's no desktop without - it appears to have unlocked as the music is back 
[10:16] <bluesabre> what happens for me is that I am unable to unlock from the login screen even after, but I can switch back to vt7 manually fine
[10:16] <flocculant> I can't manually switch (without killall) to vt7 - it's blank screen 
[10:16] <bluesabre> right
[10:17] <bluesabre> I think there's bugs with light-locker and lightdm
[10:17] <flocculant> I think that too :p
[10:18] <bluesabre> I'll look into that bug further
[10:18] <flocculant> okey doke
[10:39] -SwissBot:#xubuntu-devel- ::xubuntu-docs:: [yakkety] r617 Launchpad automatic translations update. (by Launchpad Translations on behalf of ubuntu-core-doc)
[10:54] <nairwolf> the daily build is still not available ? 
[11:26] <flocculant> nope - looks like something up with archive
[11:26] <flocculant> won't get looked at today
[11:30] <flocculant> nothing is getting finished - not just us
[11:34] <nairwolf> hum..
[11:35] <nairwolf> by the way, I will be afk during the beta test...
[12:31] <Unit193> flocculant: Someone said that last night-ish.
[12:44] <flocculant> Unit193: image build fails?
[12:45] <flocculant> oh yea - see it in -release now
[12:46] <Unit193> The "built but didn't publish to cdimage.ubuntu.com" remark.
[12:47] <flocculant> yea
[13:15] <nairwolf> That's weird
[13:15] <nairwolf> Does it happen often ? 
[13:16] <nairwolf> Is it because, it's sunday, and servers decided to not to work ? 
[13:19] <flocculant> doesn't happen often - but because it's Sunday then people who can do anything are not working
[13:21] <flocculant> nairwolf: just going to see if I can confirm your "Editable box is too small" bug
[13:22] <flocculant> I'll be a while though - want to confirm on ubuntu as well 
[13:25] <nairwolf> ok ;)
[13:26] <flocculant> hopefully it'll show in ubuntu - then it's not greybird :)
[13:34] <nairwolf> what I don't understand is I can't confirm on my actual machine
[13:40] <flocculant> nairwolf: can't confirm the partition size issues?
[13:53] <flocculant> ochosi: please don't shoot me - I'm just the messenger here ... nairwolf found another greybird/ubiquity issue bug 1622258
[13:53] <flocculant> basically the box for you to enter a partition size during install when you're creating a new partition is too small
[13:57] <nairwolf> flocculant: yes, that's right
[13:57] <nairwolf> I don't know if it's normal or not
[13:58] <nairwolf> the hard drive size is 500 Go, so in Mo it's 500 000 Mo, it's long, but, I'm not sure same thing happened before
[13:59] <nairwolf> I can test with 16.04 to see the "normal" behaviour if you want
[13:59] <flocculant> already done that ;)
[14:00] <nairwolf> but you see no difference, or you're unable to see what I saw ? 
[14:01] <flocculant> 16.04 is fine, ubuntu 16.10 is fine, xubuntu 16.10 isn't - you'll see at the bug I've confirmed it - also changed it from ubiquity to greybird
[14:01] <flocculant> bbl
[14:02] <nairwolf> I don't understand why you said firstly "can't confirm the partition size issues"
[14:05] <nairwolf> and with libreoffice calc ? 
[14:06] -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: xfce4-volumed-pulse 0.2.1 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-xfce4-volumed-pulse-0-2-1-released-tp48250.html (by Sean Davis-6)
[14:53] <flocculant> nairwolf: that was a question to you - what can't you confirm? 
[14:53] <flocculant> and calc is fine here - but I think I updated from -proposed
[14:54] <flocculant> nope - same version should be
[16:00] <nairwolf> oh, I can't confirm the issue about libreoffice calc
[16:27] <nairwolf> I've seen this issue on the daily build (10th September), but I don't see that on my computer running the devel version
[17:05] <flocculant> not seen it
[17:06] <nairwolf> I need to test it again
[21:45] <ochosi> bluesabre: ok, about the visual nuisance of the CSD/headerbar toolbars, e.g. in evince or file-roller, i have now submitted a merge-request to fix it: https://code.launchpad.net/~ochosi/evince/add_toolbar_class/+merge/305423
[21:45] <ochosi> bluesabre: note that this would have to be done for every app we care about
[22:08] <ochosi> flocculant: fwiw, the ubiquity "progress dots" are also broken with adwaita. yay.
[22:20] <Unit193> ochosi: http://lists.alioth.debian.org/pipermail/pkg-xfce-devel/2016-September/021903.html
[22:21] <ochosi> nice
[22:22] <Unit193> Isn't it still experimental though?
[22:27] <ochosi> not really
[22:27] <ochosi> at least i wouldn't consider it very experimental
[22:27] <knome> Bump strandards-version to 3.9.8.
[22:27] <ochosi> :'( somehow ubiquity doesn't seem to understand margin: -1px
[22:27] <knome> strandards?
[22:30] <ochosi> somehow i can't seem to be able to launch the gtk inspector on ubiquity
[22:31] <ochosi> stupid pkexec seems to get in the way
[22:31] <knome> yeah. blame others.
[22:31] <knome> (:
[22:37] <ochosi> so yeah, seems i've inherited that problem from adwaita
[22:56] <ochosi> meh, that'll be harder to fix...
[22:56] <ochosi> i hope i manage before 16.10 gets released
[22:58] <nairwolf> ochosi: are you talking about the bug I've found ? 
[22:59] <ochosi> that's not a very specific hint
[22:59] <ochosi> or did you only find one bug so far?
[23:03] <ochosi> nairwolf: wanna just post the link to the bug..?
[23:11] <nairwolf> This one : https://bugs.launchpad.net/ubuntu/+source/greybird-gtk-theme/+bug/1622258
[23:11] <nairwolf> ochosi: I thought you talked about that
[23:12] <ochosi> nope
[23:12] <nairwolf> Because, if I remember correctly, flocculant pinged you few hours ago
[23:13] <ochosi> yeah, well i get pinged a lot about these things :]
[23:13] <nairwolf> sorry for that...
[23:13] <ochosi> no worries