[01:14] <mterry> robert_ancell, I have another patch I'd like to squeeze into lightdm.  This time having it search XDG_DATA_DIRS for config info (to let OEM team customize image)
[01:15] <mterry> robert_ancell, haven't written it yet, but wanted to run idea by you
[01:15] <robert_ancell> mterry, makes sense
[01:15] <mterry> robert_ancell, cool.  Will whip something by your next morning hopefully
[01:15] <robert_ancell> mterry, I was thinking about that at one point - we're supposed to always use XDG_DATA_DIRS now right?
[01:15] <mterry> robert_ancell, ideally
[01:16] <robert_ancell> I was wondering if we should be using $XDG_CONFIG_DIRS as well - I noticed upstart uses that
[01:16] <mterry> oh maybe
[06:54] <GunnarHj> Thanks pitti :)
[06:54] <pitti> hey GunnarHj; yw!
[08:05] <hikiko> mpt, hello :)
[08:05] <hikiko> it seems that marco had already proposed something better than a slider and I wasn't aware
[08:07] <mpt> hikiko, really? Seems like a slider is the right control to use here. Anyway, it’s the layout that’s the issue.
[08:34] <hikiko> hello, the option mirror displays in u-c-c is for any number of displays isn't it?
[08:35] <hikiko> just to get sure
[08:36] <hikiko> ok found :) ignore ^
[08:50] <seb128> good morning desktopers
[08:50] <hikiko> hi seb128 :)
[08:51] <seb128> hikiko, hey, how are you?
[08:51] <hikiko> good, you? :)
[09:03] <Laney> hey
[09:04] <hikiko> hi
[09:06] <seb128> good morning Laney ;-)
[09:06] <ochosi> morning everyone
[09:07] <ochosi> seb128: can i quickly ask you something wrt a FFe we're considering?
[09:07] <seb128> ochosi, hey, sure
[09:07] <Laney> guten morgen seb128
[09:08] <ochosi> seb128: thanks! ok, so we're planning another release of light-locker (1.4.0), which introduces one feature ("late locking") and an option that could almost be considered bugfix ("enable/disable lock on suspend", right now it can't be disabled)
[09:09] <ochosi> seb128: we've already done the last dev release for it and are only waiting for some translations to flow in (maybe until the end of the week). do you think there's a chance for a FFe for this?
[09:10] <ochosi> seb128: (the alternative would be to backport the "disable lock on suspend" option to the 1.2 series)
[09:11] <seb128> ochosi, 1.2 is the serie you have in trusty? what are the other changes in the new serie? (e.g what would you left out if you backport that only)
[09:12] <ochosi> seb128: yes, 1.2 is the series currently in trusty. there are no other changes than the two i mentioned. i know the version step sounds big, but that's all we implemented meanwhile
[09:12] <seb128> if there no other change the "backport to 1.2" option doesn't really make sense
[09:12] <seb128> that's basically the same option than taking the new one
[09:12] <ochosi> well partly we were targetting xubuntu with 1.4, and a small version step for a new feature seemed a bit odd
[09:12] <seb128> I'm not in the release team but that seems fine for a ffe from where I sit
[09:13] <seb128> Laney might have more of an opinion, he's in the release team ;-)
[09:13] <ochosi> sure, thanks your pov :)
[09:13] <Laney> it should be ok if xubuntu wants it in
[09:15] <ochosi> yep, already discussed with project lead and one of our other devs to be sure
[09:19] <seb128> Laney, https://code.launchpad.net/~binli/unity-control-center/1291862/+merge/211258 got updated if you want to give another round of testing
[09:19] <Laney> I saw
[09:19] <Laney> will do
[09:19] <seb128> thanks
[09:20] <ochosi> thanks for the heads-up Laney and seb128 !
[09:20] <seb128> yw!
[09:20] <ochosi> Laney: would it be ok if i asked you for review once the FFe is ready?
[09:21] <Laney> I'll see it come in
[09:21] <ochosi> (you can still say "no" then ;))
[09:21] <ochosi> ok, sure
[10:01] <tsdgeos> seb128: i think lightdm not starting has to do with it trying to find a self-compiled unity-greeter from back when i did some development in unity-greeter, just that i can't find the file where i changed that now :D
[10:02] <seb128> tsdgeos, try looking in /etc/lightdm ?
[10:02] <tsdgeos> did, couldn't find anything, will wait for mterry and ask him
[10:03] <seb128> tsdgeos, look at /var/log/lightdm/lightdm.log it has the "Loading configuration from..." lines
[10:04] <seb128> tsdgeos, or maybe you can share that log file?
[10:05] <tsdgeos> [+4.79s] DEBUG: Session pid=1726: Running command /usr/lib/lightdm/lightdm-greeter-session /home/tsdgeos_work/unity-greeter/src/unity-greeter
[10:05] <tsdgeos> see
[10:05] <tsdgeos> i only need to know where that comes from :D
[10:05] <seb128> can you share the log?
[10:05] <tsdgeos> ah, found it
[10:05] <seb128> where was it?
[10:07] <tsdgeos> so i had changed greeter-session in  /etc/lightdm/lightdm.conf and created a new file under /usr/share/xgreeters/
[10:07] <seb128> k, that makes sense
[10:08] <seb128> so it was in /etc/lightdm :p
[10:08] <tsdgeos> yeah, just the _work grep i was expecting to find was not there
[10:09] <tsdgeos> so PEBKAC
[10:11] <seb128> good that you resolved it in any case ;-)
[10:23] <GunnarHj> Hi seb128, have a minute?
[10:23] <seb128> GunnarHj, hey, sure
[10:23] <GunnarHj> seb128: A proposed "What's new" page: http://people.ubuntu.com/~gunnarhj/whats-new.html
[10:23] <GunnarHj> Could you please review it and let me know if the selection of items is appropriate?
[10:24] <seb128> oh, thanks for working on that!
[10:24] <GunnarHj> seb128: There is a small thread about it on the ubuntu-doc mailing list, starting with https://lists.ubuntu.com/archives/ubuntu-doc/2014-March/018757.html
[10:25] <GunnarHj> seb128: We try to cover the 2 years period 12.04 - 14.04.
[10:26] <seb128> that list seems mostly good
[10:26] <seb128> it would be good to add a bullet point about Hi-DPI monitors support
[10:26] <seb128> the scaling option you listed in 2. is part of that
[10:27] <seb128> but we have scaling support in GTK, libreoffice, chromium as well
[10:27] <GunnarHj> seb128: In that case somebody needs to propose the wording. I simply don't know enough about it.
[10:27] <seb128> not sure if the new lock screen is worth mentioning
[10:28] <seb128> did we add the "disable online sources" for the dash for or after 12.04? (I don't remember)
[10:28] <GunnarHj> seb128: Isn't the lock screen more a thing behind the scenes?
[10:28] <seb128> if that was not in 12.04 it might be worth mentioning
[10:29] <seb128> "behind the scenes" ... well, replacing the grey win95 style password box is quite user visible
[10:29] <seb128> but yeah, it's not a new feature or anything like that
[10:29] <GunnarHj> ok :)
[10:29] <seb128> you can maybe mention work continued to improve the unity look&style
[10:30] <GunnarHj> Ok, that sounds good.
[10:30] <seb128> e.g rounded windows decoration, new lock screen, theme tweaks (borderless windows for example)
[10:33] <GunnarHj> seb128: Anything on the list that you feel is redundant?
[10:35] <seb128> GunnarHj, 6. is already included in the dash section
[10:36] <GunnarHj> seb128: Yes, that's true. I'll drop that.
[10:36] <seb128> you can add a (including music stores, wikipedia, <some useful/popular scopes>) to 4.1. if you feel like highlighting some
[10:36] <seb128> 7. ... we already had some online integration in 12.04 no?
[10:37] <qengho> Hiya. This is a weird problem. Sorry. Two keys, Up and Left, on my USB keyboard stopped working.  Not inside Linux. At all, e.g. at GRUB prompt. I plugged in a PS1 keyboard to same computer and it works. I plug the keyboard into another computer, and it works. So, my question, WTF?
[10:37] <seb128> 9. I think we dropped the remote login from the default installation, so I'm not sure it should be mentioned
[10:37] <seb128> qengho, usb port buggy? can you use another device (music player, key, phone) in it?
[10:38] <GunnarHj> seb128: 7. I 'stole' it from "What's new 12.10".
[10:38] <GunnarHj> seb128: 9. Ok, let's drop remote login.
[10:38] <seb128> 7.. ok, so 12.10, I knew it was some versions old but I didn't remember the specifics ;-)
[10:38] <seb128> that's all the comments I have
[10:39] <GunnarHj> seb128: Thanks! What about the wording of that scaling thing?
[10:39] <qengho> seb128: could be. Four wires carrying HID protocol and exactly two keys not working?  I'll test it, though.
[10:47] <seb128> GunnarHj, I don't really know, "Support added for scaling Unity and the applications, which allows a better experience on Hi-DPI screens"
[10:47] <qengho> Well that is thoroughly unsatisfying. Putting keyboard in original computer, different port worked.  Moving it back to the same USB port, and it works.
[10:47] <seb128> GunnarHj, you can maybe find details in https://wiki.ubuntu.com/Unity/Desktop/14.04/Unity7HighDPI
[10:47] <seb128> qengho, weird :/
[10:49] <GunnarHj> seb128: Ok, that page should give sufficient guidance. Thanks!
[10:49] <qengho> So, having a PS1 plugged in, visiting a different port for a moment, some minutes of cursing, and talking to a frenchman, in aggregate, fixed it.
[10:50] <seb128> GunnarHj, yw!
[10:51] <seb128> qengho, could maybe be a loose wire or something, doing contact sometimes after moving it, still weird that would affect only some keys though
[10:53] <hikiko> seb128, do you know if ff and libreoffice and thunderbird pay attention to text-scaling-factor or scaling-factor or who should I ask?
[10:54] <seb128> hikiko, I don't know, libreoffice -> Sweetsha1k , tb -> chrisccoulson
[10:57] <hikiko> Sweetsha1k, hello! could you please tell me this ^^
[11:00] <Sweetsha1k> LibreOffice has its own font scaling factor see Tools->Options LibreOffice->View->User interface scaling, there is no decision yet on syncing that from Unity (by unity writing in the LibreOffice profile).
[11:02] <hikiko> thanks Sweetsha1k :)
[12:25] <cyphermox> Laney: what's this about modify.own on bug 1116317?
[12:25] <ubot2> Launchpad bug 1116317 in network-manager-applet (Ubuntu Precise) "[ffe] allow option to create user connections by default" [High,Triaged] https://launchpad.net/bugs/1116317
[12:25] <cyphermox> also, I didn't add DEP-3 tags because I took the patch straight from Debian, I want to avoid merging this when it comes to merging from Debian next time, which should be as soon as U opens, pretty much
[12:28] <Laney> cyphermox: It's in the description
[12:28] <Laney> tags let anyone that's not cyphermox see where it came from
[12:29] <Laney> are they hard to merge?
[12:29] <cyphermox> no ;)
[12:29] <cyphermox> just a smaller diff makes my life easier ;)
[12:30] <cyphermox> the modify.own explicitly should not be in the package
[12:30] <cyphermox> it's custom policy for those enterprises that really want to lock down NM
[12:31] <cyphermox> this just allows nm-applet to honor such configurations the right way rather than not allow you to configure the connection at all as the user, since it defaults to system-wide
[12:33] <Laney> ya, I just mean that it's not checked for explicitly in the patch (compared to the old version which did)
[12:33] <Laney> It sounded to me like you had to change that setting but it is actually the default
[12:34] <Laney> headers could go in debian too btw if you can commit there ;-)
[12:34] <Laney> if not, you should probably get that access
[13:10] <GunnarHj> pitti: relaxed dependencies?
[13:10] <pitti> GunnarHj: only recommend it, or perhaps better with [i386 amd64 ...] (i. e. arches where LibO is available)
[13:11] <pitti> [i386 amd64 armhf powerpc]
[13:11] <pitti> GunnarHj: ^ but that list ist a bit icky to maintain, and won't sync to debian
[13:11] <pitti> GunnarHj: hence i was wondering why a thesaurus would need a hard dependency on LibO
[13:12] <pitti> shouldn't that rather be "Enhances:" or Suggests:?
[13:12] <GunnarHj> pitti: Well, it does not need anything. It's just two text files.
[13:12] <pitti> GunnarHj: right, so dropping it to suggests shoudl be ok?
[13:13] <pitti> GunnarHj: oh, and Architecture: should be "all", not "any"
[13:13] <GunnarHj> pitti: Absolutely. Should I do it in Ubuntu only for now?
[13:13] <pitti> GunnarHj: unless these have some binary stuff in there which is arch dependent?
[13:13] <pitti> GunnarHj: no, I think that can go to Debian
[13:13] <GunnarHj> pitti: I understand about "all". Wondered about all those different debs...
[13:14] <pitti> GunnarHj: sorry, I missed that during review
[13:14] <GunnarHj> pitti: Now I'm going to remember it. :)
[13:14] <pitti> GunnarHj: do you want to prep an update? I'll sponsor it right away (you can just send me a pastebin, or via mail, etc.; as easy as possible)
[13:15] <GunnarHj> pitti: Ok, I'll prepare it. Stand by.
[13:16] <pitti> GunnarHj: thanks!
[13:16] <GunnarHj> pitti: Thank *you*.
[13:16] <Laney> oh neat, you got that in
[13:17] <pitti> Laney: yes, we just need to appease britney a bit :)
[13:17] <Laney> ya, looking at that Enhances sounds good
[13:19] <GunnarHj> pitti, Laney: Just a thought... I didn't invent that recommend myself - I copied and pasted from some other mythes-*. Can it possibly be that changing from "any" to "all" is sufficient?
[13:20] <pitti> GunnarHj: yes, I suppose it is
[13:20] <pitti> still curious how that got through britney, as regardless of its arch that dep remains unsatisfiable on those arches
[13:20] <pitti> but presumably britney special-cases that
[13:21] <GunnarHj> pitti: I have no idea.
[13:21] <pitti> GunnarHj: so for now, let's fix it to Arch: all
[13:21] <GunnarHj> pitti: Ok.
[13:23] <Laney> there's some special-casing of arch:all in britney
[13:23] <Laney> so it probably works
[13:33] <mterry> seb128, the new lockscreen in 14.04 doesn't work for me.  It never accepts my password.  Is that a known bug?
[13:34] <seb128> mterry, no
[13:34] <pitti> WFM
[13:34] <seb128> mterry, do you have some weird chars that nux might not like? e.G can you type all the chars from your password in e.g the dash?
[13:34] <GunnarHj> pitti: http://people.ubuntu.com/~gunnarhj/mythes-sv_new-arch.patch.txt
[13:35] <mterry> seb128, yeah
[13:35] <mterry> seb128, everything is on the keyboard
[13:35] <mterry> i.e. no composing
[13:35] <seb128> mterry, your keyboard layout is right (check the indicator)
[13:35] <seb128> ?
[13:36] <seb128> mterry, do you have any error in the .cache/upstart/compiz.log ?
[13:36] <pitti> mterry: is your /etc/shadow root:shadow 640, or did that perhaps get changed?
[13:36] <pitti> mterry: (sometimes happened to me when restoring backups)
[13:37] <pitti> GunnarHj: built/uploaded to sid; I'll sync this evening or tomorrow morning
[13:37] <GunnarHj> pitti: Thank you very much, Martin!
[13:38] <pitti> thanks to yo
[13:40] <mterry> Uh, I'd have to kill my session to double-check it, but I don't remember seeing another layout in there (I do have a second chinese layout for testing configured, so it's possible it screwed that up...)
[13:40] <mterry> seb128, also, how is one supposed to switch to another user from the lockscreen?
[13:40] <mterry> seb128, none of the indicators open for me
[13:40] <pitti> the indicator worked for me, but it's not very discoverable
[13:40] <pitti> it ought to be similar to lightdm, that'd be nicer
[13:41] <seb128> mterry, using the indicators, once they fix the stacking regression issues you just described (which they added when fixed the "dash sometime open in front of the lock screen)
[13:41] <seb128> pitti, similar? like listing different users
[13:41] <seb128> ?
[13:41] <pitti> seb128: perhaps, but at least some directly visible "switch to other user"
[13:41] <pitti> like in the old screen saver
[13:41] <seb128> mterry, you can probably keyboard browse it though :p
[13:42] <seb128> pitti, right, that would be nice. The "list other users" is tricky because you don't want to type your password in a process owned by another user :p
[13:43] <pitti> seb128: right, and you can't even (I even wonder how it does that for your own user -- there must be some setgid shadow helper involved?)
[13:43] <pitti> probably unix_checkpwd
[13:43] <mterry> pitti, seb128: ok, /etc/shadow is good.  Looking at compiz.log
[13:43] <mterry> seb128, I don't have a compiz.log?
[13:44] <seb128> mterry, sorry, it's in gnome-session-ubuntu.log
[13:47] <mterry> seb128, trying to dig through the file.  We don't use gnome-screensaver anymore with this, right?  This is in-shell?
[13:49] <seb128> sort of
[13:49] <seb128> depends for what, the lock screen/unlocking is in unity yes
[13:49] <seb128> we still use gnome-screensaver for idle tracking and starting lock
[13:49] <seb128> e.g we didn't replace those part, we just changed g-s to trigger the unity lock when it was displaying it's gtk dialog before
[13:51] <mterry> seb128, I don't see anything in the log
[13:51] <seb128> k, dunno then :/
[13:52] <seb128> note that you can change the lock screen back to gnome-screensaver in ccsm
[13:52] <seb128> if you want to verify that g-s takes your password fine
[13:54] <mterry> seb128, is that "None"?  (I get lightdm, unity, or none)
[13:56]  * mterry sticks with LightDM, since None is apparently really None
[13:58] <seb128> mterry, lightdm is g-s I think?
[13:58] <mterry> seb128, no it took me right to lightdm itself
[13:58] <mterry> Kinda nice
[13:59] <seb128> hum
[14:00] <seb128> you might be able to run XDG_CURRENT_DESKTOP=GNOME gnome-screensaver-daemon or something
[14:00] <seb128> if you want to test typing your password to g-s
[14:00] <seb128> but otherwise you need to find andyrock to debug unity not take your password I guess
[14:08] <andyrock> actually none should allow you to use g-s
[14:08] <andyrock> g-s should be smart enough to detect that unity is not locking
[14:11] <seb128> andyrock, do you have any hint on how to debug password not being accepted by unity lock screen? seems to happen to mterry
[14:12] <andyrock> seb128, let's start from the lightdm pam
[14:12] <andyrock> maybe he's using a different module?
[14:12] <mterry> andyrock, when I did None and locked screen nothing happened
[14:13] <seb128> andyrock, how do you know which one is being used?
[14:13] <andyrock> mterry, well i added that before Trevinho integrated unity with g-s
[14:13] <seb128> it's likely that mterry tweaked his pam config, he has been working around component using it
[14:13] <mterry> seb128, that's fair...  I don't remember what I would have done, but it's possible
[14:13] <andyrock> we use lightdm pam config file
[14:13] <seb128> andyrock, btw are you working on all those bugs tagged lockscreen? like the "lock again when coming from the greeter"?
[14:14] <andyrock> yep not know
[14:14] <andyrock> during the afternoon
[14:14] <andyrock> *now
[14:15] <andyrock> mterry, can you pastebin the content of  /etc/pam.d/lightdm ?
[14:16] <mterry> andyrock, http://paste.ubuntu.com/7114270/
[14:16] <andyrock> mterry, lightdm works fine?
[14:16] <mterry> andyrock, seems to
[14:17] <andyrock> but it fails to unlock or it says that the password is not correct?
[14:18] <andyrock> mterry, ^^^
[14:18] <mterry> andyrock, the lockscreen does.  It spins for a bit then says invalid password
[14:21] <andyrock> that's weird... i did some tests in the last week (just on my system, not in trunk!) and it happened that nux doubled some chars
[14:22] <andyrock> at the moment there is no way do debug it without building unity
[15:30] <seb128> oh, it's meeting time!
[15:30] <Sweetshark> Hammerzeit!
[15:30] <desrt> can't touch this
[15:30] <seb128> qengho, Sweetshark, mlankhorst, laney, tkamppeter, desrt, larsu, kenvandine: hey
[15:31] <mlankhorst> hey
[15:31]  * kenvandine waves
[15:32] <seb128> I hope everybody is back to bugfixing after ff backlog and vUDS ;-)
[15:32] <seb128> let's get started
[15:32] <seb128> no qengho?
[15:32] <seb128> Sweetshark, ok, you start I guess then ;-)
[15:32] <kenvandine> "bug fixing" :)
[15:33] <qengho> Bah, network flaky.
[15:33] <qengho> My turn?
[15:33] <Sweetshark> qengho: go
[15:33] <Sweetshark> (me still collects bug refs)
[15:33] <qengho> Done: direct-mode touch devices seem to work in Chromium Dev line now. Backporti
[15:33] <qengho> ng it to Beta line, which should be landing at end of month.
[15:33] <qengho> Done: publishing Cr 33.0.1750.152 to security now.
[15:33] <qengho> To-do: gestures don't work for dependent-mode touch devices yet.
[15:33] <qengho> To-do: polish Cr patches so they're accepted upstream.
[15:33] <qengho> EOF
[15:34] <seb128> qengho, is the version that landed recently in trusty including touch support?
[15:34] <qengho> seb128: no. The diffs to that are too big.  I can't backport that far without lots of bugs.
[15:34] <seb128> k
[15:35] <seb128> so it's not going to be in trusty at this point I guess?
[15:35] <seb128> what's the plan? get those upstream and flowing back with some update later on?
[15:35] <qengho> Yes.  End of this month, 34 is promoted to Stable. That will have all.
[15:35] <seb128> great, so maybe even for trusty release ;-)
[15:36] <seb128> qengho, thanks
[15:36] <seb128> Sweetshark, your turn this time!
[15:36] <Sweetshark> k
[15:36] <Sweetshark> - upstream Writer 4.2 regression sweep
[15:36] <Sweetshark> -- fixed table zoom crash fdo#74854
[15:36] <Sweetshark> -- found and triaged table cut-undo and insert row crashes, fixed thanks to Miklos now fdo#75898 fdo#75110
[15:36] <Sweetshark> -- all confirmed, open Writer 4.2 regressions triaged now (5 regressions, 3 inherited from AOO work) => looking good in general
[15:36] <Sweetshark> - looked at some old regressions (introduced in4.1 and older)
[15:36] <Sweetshark> -- fixed cant shrink graphic regression (orgin: AOO again) 	fdo#47355
[15:36] <Sweetshark> -- fixed broken table refs fdo#75492
[15:36] <Sweetshark> - fixed autopkgtests
[15:36] <Sweetshark> -- fixed local running tests first. Unfortunately, that didnt mean they also run happily in the VM.
[15:36] <Sweetshark> -- fixed them there too, should be alright now -- waiting for PPA build to finisto confirm
[15:36] <Sweetshark> - looked at regression count in other apps too
[15:36] <Sweetshark> - Investigated options for HiDPI setting sync from Unity (vUDS session)
[15:37] <Sweetshark> - bumped to upstream 4.2.3~rc1
[15:37] <Sweetshark> - Ongoing: triaging "Send Document as Mail" brokeness -- bug 1217191
[15:37] <ubot2> Launchpad bug 1217191 in libreoffice (Ubuntu) ""Send document as Open Document Text" fails to attach doc when using Thunderbird" [Undecided,Confirmed] https://launchpad.net/bugs/1217191
[15:37] <Sweetshark> - Ongoing: Hackfest Gran Canaria preparations https://wiki.documentfoundation.org/Hackfest/GranCanaria2014
[15:37] <Sweetshark> EOF
[15:37] <Sweetshark> (well, and quite a bit of additional bibisect/triage work in writer)
[15:37] <desrt> Sweetshark: how does one get invited to said hackfest? ;)
[15:37] <seb128> Sweetshark, do you need sponsoring for the 4.2.3~rc1?
[15:37] <seb128> Sweetshark, and yeah, I see how you guys pick your hackfest locations!
[15:38] <Sweetshark> seb128: I want the autopkgtests and the mail issue still in there.
[15:38] <seb128> k
[15:38] <seb128> let me know when you need sponsoring
[15:38] <Sweetshark> seb128: also: its an rc1 -- shouldnt be an issue, but ...
[15:38] <desrt> seb128: aruiz has his name on this list... i suspect this may have something to do with it :)
[15:39] <Sweetshark> desrt: there is still travel sponsoring available. just contribute to LO and ask ;) (that said: europeans have it cheaper to that location, so ...)
[15:39] <seb128> Sweetshark, btw I pinged about the dmb application, bdrung is busy and he didn't want to keep blocking it so he bounced back to them to have it re-evaluated, with some luck it's going to be ok this time!
[15:39] <seb128> desrt, haha
[15:39] <Sweetshark> oh, speaking of which: some GSOC mentoring.
[15:39] <Sweetshark> seb128: cool
[15:40] <seb128> Sweetshark, thanks
[15:40] <seb128> mlankhorst, hey
[15:40] <mlankhorst> bugsquashing, keeping the xorg workqueue from exploding, fixing crash bug on shutdown with optimus, updating wine to 1.6.2 (needs sponsoring), upstream kernel work + testing (ati + snb optimus appears to work again :D), taking a look at all piglit crasher bugs in mesa.git.
[15:40] <mlankhorst> hope that didn't get cut off :P
[15:40] <Sweetshark> desrt: aruiz and the fact that a/ Las Palmas uses LibreOffice, while b/ the rest of GC uses OpenOffice still both have nothing to do with that.
[15:41] <mlankhorst> but piglit has no crashers on my system now, going to look at intel and ati next.
[15:41] <desrt> :)
[15:41] <seb128> that didn't
[15:41] <mlankhorst> ^D
[15:41] <seb128> mlankhorst, I saw quite a fix segfault in the e.u.c daily reports, I guess that's what you are focussing on in the next weeks?
[15:42] <mlankhorst> seb128: the most common one appears to be lack of xv support in fglrx
[15:42] <mlankhorst> at least that's my guess
[15:42] <mlankhorst> was getting 100 dupes of that bug :P
[15:42] <seb128> k
[15:42] <mlankhorst> oh speaking of which another one
[15:42] <seb128> do we have people talking to amd about those?
[15:42] <mlankhorst> https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1279412
[15:42] <ubot2> Launchpad bug 1279412 in fglrx-installer (Ubuntu) "Xorg crashed with SIGABRT in xdl_xs115_atiddxPixmapIsTypeOf()" [Critical,Triaged]
[15:42] <mlankhorst> yeah i poked them
[15:42] <mlankhorst> tseliot: ?
[15:42] <seb128> cool
[15:43] <seb128> we don't have contact at virtualbox by any chance?
[15:43] <seb128> quite some reports in trusty from issues with their gl drivers
[15:43] <mlankhorst> not that I know :s
[15:44] <seb128> k
[15:44] <seb128> mlankhorst, thanks
[15:44] <seb128> laney: your turn (I wonder why my xchat tab complet 2 laneys there)
[15:44] <Laney> you can't have too many laneys
[15:44] <Laney> • Short week due to holidays
[15:44] <Laney> • GNOME updates: glib webkit librsvg
[15:44] <Laney> • cross-building breakage with Qt 5.2; fix building
[15:44] <Laney> • Upload qcreator-plugin-cmake for upgrade failure
[15:44] <Laney> • Review many FFes
[15:44] <kenvandine> because Laney is twice as cool as seb128?
[15:45]  * kenvandine ducks
[15:45] <seb128> kenvandine, I'm going to show you :p
[15:45] <mlankhorst> less than half as cool, which is why you need 2 ;D
[15:45] <kenvandine> mlankhorst, better math then me :)
[15:45] <seb128> haha
[15:45] <seb128> Laney: how are things looking from the FFe front to you? (and for the release)
[15:46]  * seb128 is still a bit nervous about the new lock screen
[15:46] <Laney> I'm just parallelised
[15:46] <seb128> not sure that's going to be good enough for release
[15:46] <Laney> I don't see much for desktop remaining
[15:46] <Laney> cyphermox wants to make NM use user connections
[15:46] <seb128> that, and there is the Ubuntu GNOME ffe for gnome-desktop 3.10 which seems risky as well
[15:46] <Laney> and there's the gnome-desktop one
[15:47] <seb128> right
[15:47] <seb128> laney: no cool utf8 end of list char this week? ;-)
[15:47] <Laney> It feels too risky, I'd probably rather they just do that on unctuous unicorn day 1
[15:48] <Laney> no I was fiddling with glib until the last second :(
[15:48] <seb128> yeah, that's my take too, not going to make the GNOME guys happy though
[15:48] <Laney> you put one in yours though :P
[15:48] <Laney> I usually use this list http://unicodeemoticons.com/cool_text_icons_and_pictures.htm
[15:48] <seb128> laney: thanks (to both of you :p)
[15:49] <tkamppeter> 14.10 will be unctuous unicorn?
[15:49] <ritz> lol
[15:49] <seb128> tkamppeter, who knows ;-)
[15:50] <seb128> tkamppeter, your turn btw ;-)
[15:50] <mlankhorst> pssh unicorns
[15:50] <kenvandine> it's that time in the cycle where everyone has fun speculating
[15:50] <tkamppeter> - Google Summer of Code 2014: Got first student applications, especially IPP-over-USB support for Linux will get done by one or two students who already did several GSoCs successfully for us.
[15:50] <tkamppeter> - cups-filters: 1.0.47 and 1.0.48 with security fixes and several other bug fixes including a crasher in cups-browsed.
[15:50] <tkamppeter> - ghostscript: As there was no new upstream release before FF, backported important upstream fixes to our package.
[15:50] <tkamppeter> - HPLIP: 3.14.3 upstream release with many bug fixes.
[15:50] <tkamppeter> - system-config-printer: Additional fix for driver auto-download.
[15:50] <tkamppeter> - Bugs.
[15:51] <mlankhorst> Laney: I've upgraded my bike to a draft horse btw >:D
[15:51] <seb128> tkamppeter, thanks
[15:51] <seb128> desrt, your turn ;-)
[15:51] <tseliot> mlankhorst: sorry, I'm fighting with a different issue on my amd system
[15:51] <desrt> upstream bug fixing, releases
[15:51] <desrt> reviews, various bits of ubuntu bug hunting
[15:51] <desrt> jhbuild hacking and cleaning up (environment handling, mostly -- fixed debian multiarch, python path issues, finally killing off ACLOCAL_PATH, gnome-common fixes, etc.)
[15:52] <desrt> helped a few potential SoC students find their way
[15:52] <desrt> lots of portability fixes in various projects in the past weeks
[15:52] <desrt> branched glib
[15:52] <desrt> going to start looking at mainloop again
[15:52] <desrt> fin.
[15:52] <desrt> seb128: did we start seeing less of that u-s-d crasher in the past days?
[15:54] <seb128> desrt, I'm trying to check
[15:54] <seb128> but I might just get back to you at the end of the meeting for that :p
[15:54] <desrt> :)
[15:55] <seb128> desrt, thanks
[15:55] <seb128> no attente, he's on holidays until thursday
[15:55] <seb128> larsu, so your turn
[15:55] <larsu> k
[15:55] <larsu> - finished up rhythmbox menus after design input
[15:55] <larsu> - evince: added back secondary keybindings; some other smaller bug fixes related to the menubar patch
[15:55] <larsu> - sound: show a red icon when muted and sound is playing, fix volume notification when allow-amplified is on, fix volume-slider-clicking issues, don't show players on greeter
[15:56] <larsu> - some fixes to the theme
[15:56] <larsu> - we now have lock screen profiles for indicators
[15:56] <larsu> I think that's about it
[15:56] <seb128> larsu, thanks
[15:57] <seb128> good work on the themes and classic menus for those apps ;-)
[15:57] <larsu> thanks
[15:57] <desrt> seb128: yr turn!
[15:57] <seb128> desrt, no, kenvandine's first :p
[15:57] <desrt> oh.  right!
[15:57] <kenvandine> haha :)
[15:57] <larsu> desrt: ts ts ts
[15:57] <kenvandine> Content hub branches are all queued up for review and pending a silo request, hopefully tomorrow.  Some of the packages including in the silo request are locked by other silos right now.
[15:57] <kenvandine>  * Link instead of copy content whenever possible
[15:57] <kenvandine>  * Quiet the debug output by default
[15:57] <kenvandine>  * Fix for handling legacy apps as default instead of only click
[15:57] <kenvandine>  * Fix for app switching on aborted transfers
[15:57] <kenvandine>  
[15:57] <kenvandine> Other stuff:
[15:57] <kenvandine>  * Updated wallpapers for 14.04
[15:57] <kenvandine>  * Precise SRU for gwibber
[15:58] <kenvandine>  * Working on a POC for showing click installed wallpapers in ubuntu-system-settings
[15:58] <kenvandine>  /EOF
[15:59] <seb128> oh, click wallpapers
[15:59] <seb128> I didn't know that's a thing :p
[15:59] <kenvandine> hehe
[15:59] <seb128> I saw your content-hub u-s-s merge request, but I'm unsure how to test it
[15:59] <kenvandine> they want to be able to get click packages for wallpapers into the store
[15:59] <seb128> I think I'm just going to approve it from review and test when it's in the silo
[15:59] <kenvandine> seb128, that'll be in the silo request
[15:59] <seb128> that sounds cool
[15:59] <desrt> silos... trains...
[15:59] <desrt> sometimes i wonder what's going on
[15:59] <seb128> do they also plan to include some by default? ;-)
[16:00] <kenvandine> i sure hope so!
[16:00] <seb128> desrt, didrocks making us love the train (for those who didn't already before)
[16:00]  * kenvandine is an american, what's a train? :-p
[16:00] <didrocks> kenvandine: for Europe only :p
[16:00] <desrt> canada is currently having a problem with too much wheat in silos and not enough trains
[16:00] <seb128> desrt, the new CI basically give you a "silo ppa" with a build of all the things that you asked to land, makes testing on any arch much easier
[16:01] <desrt> neat
[16:01] <kenvandine> seb128, our silo request includes several packages that are currently locked by other silos
[16:01] <kenvandine> so we're waiting on those
[16:01] <seb128> kenvandine, going to be fun, like u-s-s I want to put some land request today as well
[16:01] <kenvandine> we have sooooo many branches queued up
[16:02] <kenvandine> gotta get it landed!
[16:02] <seb128> good luck landing that ;-)
[16:02] <seb128> yeah
[16:02] <seb128> kenvandine, thanks
[16:02] <seb128> ok, this time my turn
[16:02] <seb128> • quite some testing of fixes from others, helped to land those through sponsoring or CI train (eog, nautilus, gnome-icon-theme symbolic, evince, rhythmbox, glib, ubuntu-themes, indicators, ...)
[16:02] <seb128> • quite some bug triage to see what should be fixed for release
[16:02] <seb128> • hosted vUDS client-1 track
[16:02] <seb128> • some ubuntu-system-settings reviews
[16:02] <seb128> • tested new settings icon for touch, started using them in u-s-s
[16:02] <seb128> • desktop bugs fixing (mostly unity-control-center)
[16:02] <seb128> ♖
[16:02] <desrt> rook?
[16:03] <kenvandine> ☃
[16:03] <seb128> desrt, indeed, it's a nice move :)
[16:03] <desrt> seb128: would be nice to hear about the u-c-c accounts and u-s-d gsettings things when you know
[16:04] <seb128> desrt, yeah, I'm on it
[16:04] <seb128> ok, any other topic?
[16:04] <desrt> this was a very short and efficiently-run meeting.  congratulations everyone.
[16:05] <seb128> thanks everyone!
[16:05] <kenvandine> seb128 rocks! :-D
[16:05] <desrt> i think in the future we should have all of our meeting without attente.
[16:05] <seb128> lol
[16:05] <seb128> that's mean :p
[16:05] <desrt> post hoc, baby
[16:06] <kenvandine> mpt, any thoughts on how click installed wallpapers should be shown in uss?  I assume not under Ubuntu Art or Custom
[16:06] <seb128> desrt, https://errors.ubuntu.com/problem/3f51cd3b1862122d4df85b44bf6c30245e8e4a76 suggests there has been no recent report of the gsettings issue, but it's not that frequent/we don't have that many trusty users, so I'm going to keep watching it for a bit
[16:06] <mpt> kenvandine, what is a “click installed wallpaper”?
[16:06] <kenvandine> extra wallpapers installed from the click store
[16:07] <kenvandine> so not part of a default set
[16:07] <mpt> urg
[16:07] <desrt> seb128: k.  thanks.
[16:07] <desrt> lunch time :D
[16:07] <seb128> desrt, enjoy!
[16:08] <mpt> kenvandine, is it possible to delete those individually after the package is installed?
[16:08] <mpt> E.g. if the package installs 20 of them, can you delete 4 of them without things blowing up?
[16:08] <kenvandine> it's just code... i could make that possible :)
[16:08] <kenvandine> however, i think i'd rather guide the user to remove the package...
[16:09] <mpt> kenvandine, it’s just that if the answer was yes, they could go into “Custom”, but if the answer is no, probably they need their own section.
[16:09] <kenvandine> i was thinking each package could provide a "set"
[16:09] <mpt> That makes sense
[16:09] <mpt> with its own heading
[16:09] <kenvandine> maybe collapsed by default, but you could view the set
[16:09] <mpt> yep
[16:10] <kenvandine> so the click package could provide metadata, including a title for their set
[16:10] <kenvandine> and that would show up under some "Extras" section or something
[16:10] <mpt> Or just at the top level
[16:11] <mpt> Ubuntu Art, Foo, Bar, Custom
[16:11] <kenvandine> i worry about noise... my kids must have like 30 of these sets installed in android
[16:11] <mpt> (where Foo and Bar were installed)
[16:11] <kenvandine> that's a lot of sections
[16:12] <kenvandine> most of the android ones include their own UI for setting the wallpaper, but i'd rather that be done in uss
[16:12] <kenvandine> in fact, that has to be done in uss... since confined apps can't change those settings
[16:13] <mpt> kenvandine, even 30 isn’t a long list if they’re all collapsed by default. And if it becomes a problem we can make an “Extras” category with package subcategories later.
[16:13] <kenvandine> mhall119, FYI ^^ specifically the bit about metadata and a title for the set
[16:13] <kenvandine> mpt, ok, maybe Extras should be below custom?
[16:14] <mpt> kenvandine, I don’t think so, they’re more similar to Ubuntu Art than they are to Custom
[16:14] <kenvandine> ok
[16:14] <mpt> And if this is going to be possible, perhaps Custom should be renamed to something more specific (not sure what yet)
[16:14] <kenvandine> mpt, maybe ubuntu art and custom should be collapsable too?
[16:14] <mpt> yes indeed
[16:15] <mpt> good idea
[16:15] <kenvandine> just not by default
[16:15] <kenvandine> ok... great
[16:15] <kenvandine> mpt, mind updating the designs when you have time?
[16:15] <mpt> Can you report a bug for the design changes, please?
[16:15] <kenvandine> sure
[16:15] <mpt> thanks
[16:17] <mhall119> kenvandine: how far back should I start reading?
[16:18] <kenvandine> mhall119, basically we're thinking we'd have the click packages provide a title for the wallpaper "set" which would be a section title in system settings
[16:18] <kenvandine> then you could browse just the wallpapers in that set
[16:19] <mhall119> kenvandine: can the click package's title be used as the "set" name?
[16:19] <mhall119> so "Trusty Wallpapers" in the example click I gave you would be the same of that set
[16:19] <kenvandine> sure
[16:19] <kenvandine> wfm
[16:20] <kenvandine> mpt, bug 1294203
[16:20] <ubot2> Launchpad bug 1294203 in ubuntu-system-settings (Ubuntu) "[backgrounds] Provide UI for handling click installed wallpaper sets" [Undecided,New] https://launchpad.net/bugs/1294203
[16:20] <kenvandine> mhall119, add your 0.02 there too :)
[16:20] <mhall119> kenvandine: also, eventually we'll want a way for users to uninstall these wallpaper packages
[16:20] <kenvandine> yeah
[16:20] <kenvandine> so maybe that could be an action when your viewing one of those sets
[16:20] <mpt> thanks
[16:21] <mhall119> will these packages be shown in and installable from the Applications lens?
[16:21] <kenvandine> mhall119, please comment on that bug so mpt can also think about what the UI would look like for that
[16:21] <kenvandine> mhall119, no idea... i haven't thought about that yet
[16:21] <kenvandine> i know it was discussed during uds...
[16:26] <mpt> Even if it is the first example of the inadvisability of managing all software from an “application lens”, it won’t be the last…
[16:36] <trem> didrocks: ping ?
[16:36] <trem> hi all
[16:37] <didrocks> hey trem
[16:37] <seb128> trem, hey, please state your question rather than using "ping", others might be able to help you (and didrocks might be able to decide if he has spare cycles to reply or not)
[16:38] <didrocks> yeah
[16:38] <didrocks> was going to tell the same thing :)
[16:39] <didrocks> -> back to work
[16:39] <trem> But I don't have a question, I just want to talk to didrocks ;)
[16:41] <seb128> trem, take a ticket, there is a waiting queue, it's like wanting to talk to  the prime minister, those are busy people :p
[16:42] <trem> ohhhhhhhhhh
[16:42] <trem> I wasn't aware that didrocks has the same planning as the prime minister
[16:42] <trem> ;)
[16:43] <seb128> the prime minister might be less busy in fact :p
[16:44] <seb128> desrt, the account change seems to work fine, tested lock/unlock/changing password for one user and another/changing login mode/changing realname
[16:44] <trem> but didrocks works on desktop, is it really complex and difficult ? ;)
[16:44] <desrt> party
[16:44] <desrt> hopefully they sort it out upstrem as well
[16:46] <seb128> yeah, I'm going to comment on there as well
[16:47] <seb128> trem, there are quite some work ongoing, he's also working on ubuntu touch images
[16:47] <seb128> trem, you should just write him what you want to write though ;-)
[16:47] <trem> seb128: it"s not really important, I can wait
[16:48] <trem> I won't bother the prime minister for such thing ;)
[16:48] <seb128> trem, those behaviour are not really helpful, if you have something to say just write it, or you can wait forver
[16:48] <seb128> others might be able to help you as well
[16:48] <trem> seb128: I don't need help, just want to talk (in private) with didrocks
[16:49] <seb128> trem, well, then don't use a channel but /query
[16:49] <trem> otherwise, I agree with you (100%) that I should ask my question on the chan
[16:49] <trem> seb128: a little hello before a query may be nice
[17:00] <cyphermox> Laney: I think you're misunderstanding that bug, it's just allowing people to use a locked down policykit policy, not actually changing any kind of default in the desktop
[17:00] <seb128> trem, yeah, you might never get to talk to him if you insist on your behaviour, anyway I tried to help but seems like you prefer your way so good luck ;-)
[17:01] <Laney> cyphermox: I do
[17:01] <Laney> It lets you create connections if you are denied the modify.system permission
[17:01] <cyphermox> right
[17:01] <cyphermox> which shouldn't happen on desktop normally
[17:02] <cyphermox> don't get me wrong I'm adding the DEP-3 tags now :)
[17:03] <cyphermox> I just get worried when I see "change blah", because it's not really changing anything of the standard behavior on desktop, you'd normally have the permissions you need to create connections. It's only for enterprise locked-down setups
[17:04] <Laney> Who has the modify.system and modify.own privileges by default currently?
[17:05] <Laney> I think it's admin/sudo & active for the former and active for the latter
[17:44] <Laney> (what I was getting at with that is that AFAICS it does change behaviour for the non-admin case)
[17:52] <bjf> bug 1291939 makes using dark backround terminal windows very difficult to use
[17:52] <ubot2> Launchpad bug 1291939 in ubuntu-themes (Ubuntu) "window borders are now missing meaning overlapping windows of the same type have no separation, and no separation from the background" [Undecided,Confirmed] https://launchpad.net/bugs/1291939
[18:07] <cyphermox> Laney: in desktop, you have modify.own active by default and modify.system for sudo, but active via a polkit rule if you're in the admin or sudo group
[18:08] <cyphermox> so all standard installs end up being using the modify.system action
[18:09] <Laney> Until you have another user who isn't an admin
[18:09] <Laney> I don't really think that's an enterprise-only case
[18:09] <cyphermox> it is
[18:09] <cyphermox> on a standard desktop, if you're not admin,
[18:09] <cyphermox> you just will get thrown out by NM
[18:09] <Laney> even after this patch?
[18:10] <cyphermox> not with this patch
[18:10] <Laney> That's what I was getting at
[18:10] <cyphermox> the patch introduces proper behavior
[18:10] <Laney> so it is a change for this use-case
[18:10] <Laney> it's a /good/ change
[18:10] <cyphermox> bugfix there.
[18:10] <Laney> but still, something to look out for
[18:11] <cyphermox> agree, but I really do want to stress that this is what NM should always have been doing, and anything else is absolutely very wrong, even if someone did rely on it before
[18:11] <cyphermox> people who lock down a system and know what they are doing actually change the polkit rules
[18:11] <cyphermox> anything else we can just tell people to not do that
[18:12] <cyphermox> I usually like the make it easy on people, but this is really really wrong not implemented as such, and I've been getting lots of request to fix it, esp. in LTS
[18:12] <Laney> It's fine to fix it, that's why I approved the request
[18:13] <cyphermox> thanks :)
[18:13] <cyphermox> so we're just arguing shmemantics
[18:13] <Laney> but I do not agree that non-admin users is a niche or enterprise or unsupported thing, if that's what you are arguing
[18:13] <cyphermox> no
[18:13] <cyphermox> just that there is a right way to do it
[18:13] <Laney> wifi should work for them, indeed
[18:14] <cyphermox> and that the current behavior is fundamentally broken for enterprise users where we've seen this kind of lock down being done
[18:14] <cyphermox> (with actual bug reports)
[18:14] <cyphermox> I wholeheartedly agree about giving my kids a non-admin account ;)
[18:15] <cyphermox> the bofh in me will assign a user as soon as a nick is decided for the newborn :D
[18:17] <Laney> wait
[18:17] <cyphermox> Laney: also, manual milestone tests?
[18:17] <Laney> there's a newborn?
[18:17] <cyphermox> Laney: no, there isn't
[18:17] <Laney> haha
[18:17] <Laney> i got excited
[18:17] <cyphermox> haha not yet ;)
[18:18] <Laney> http://iso.qa.ubuntu.com/qatracker/testcases/1436/info
[18:18] <Laney> that's what I was referring to
[18:19] <Laney> just a suggestion though
[18:19] <cyphermox> tbh I would like to move to a bigger place first, and that's being planned, and probably soon after
[18:19] <cyphermox> alright
[18:20] <cyphermox> it's kind of involved for a generic post-installation test
[18:20] <cyphermox> maybe more for an OEM kind of install?
[18:20] <cyphermox> not that it's irrelevant, just a more likely use case there
[18:21] <cyphermox> since it involves messing with polkit rules and all
[18:22] <Laney> I mean a test that says "non admin users can add new wifi connections"
[18:22] <Laney> right, I'm offski
[18:22] <Laney> ttyl!
[18:37] <seb128> laney: have fun
[19:30] <seb128> mterry, your pagination branch still gives me a criss-cross merge with a conflict :/
[19:30] <mterry> seb128, :-/
[19:31] <seb128> mterry, the other branch is about to be merged back to trunk, that might make easier to rebase?
[19:31] <mterry> seb128, yeah not sure why that is happening.  I merged in custom-pages again
[19:32] <mterry> Saw and resolved the conflict
[19:32] <seb128> right, it's the bzr
[19:32] <seb128> I don't know :p
[19:41] <ochosi> larsu: gah, you changed the icon-name from "blocking" to "blocked" here, so ubuntu-mono and other icon themes won't show the icon you're expecting: http://bazaar.launchpad.net/~larsu/indicator-sound/lp1291530/revision/422
[19:42] <ochosi> or can anyone on unity with the sound-indicator confirm that this actually works? (without cheating and changing the icon-name ;))
[19:46] <ochosi> seb128: since you reported the bug, for some odd reason i can't seem to be able to find the spec: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1291530
[19:46] <ubot2> Launchpad bug 1291530 in indicator-sound (Ubuntu) "Icon doesn't turn red when sound is played while muted" [Low,Fix released]
[19:46] <ochosi> it seems odd that the spec should refer to "audio-volume-muted-panel" as the icon name for the blocked state (i.e. red icon)
[19:47] <ochosi> when it should be either "audio-volume-muted-blocking-panel" (as ubuntu-mono-icons suggest) or "audio-volume-muted-blocked-panel" (as larsu's patch suggests)
[19:55] <robert_ancell> bregma, are there any plans for unity-greeter and hidpi?
[19:56] <bschaefer> robert_ancell, for the lockscreen? Yes, im almost done with the HiDPI just the dam background is a little tricky :)
[19:56] <robert_ancell> bschaefer, not the lockscreen but the greeter
[19:56] <bschaefer> o the greeter...
[19:57] <bschaefer> hmm, i've not looked at that ;)
[19:57] <robert_ancell> bschaefer, yeah, I figured it had been forgotten about!
[19:57] <robert_ancell> bschaefer, I figure we just need to increase the grid size and the font size when we cross a resolution/dpi threshold
[19:57] <bschaefer> robert_ancell, :(, we weren't able to get scroll bars either....
[19:57] <bregma> robert_ancell, not forgoteen, just postponed
[19:57] <robert_ancell> ok
[19:59] <bregma> HDPI is a feature that went form "don't do anything in 14.04" to "why isn;t everything perfect yet?" in less than 3 months
[20:00] <robert_ancell> bregma, that's never happened at canonical before
[20:03] <bschaefer> robert_ancell, also for hidpi we need to adjust the login user box, and Ill have to look at how the panel is done. (As I think the panel for the greeter comes up before unity?)
[20:03] <robert_ancell> bschaefer, yeah, the greeter shows before unity
[20:03] <bschaefer> it'll be interesting as we'll have to increase the panel + each entry as well
[20:04] <bschaefer> we could also focus on the box + text + background as well
[20:05] <bschaefer> robert_ancell, also the logo image is a png... im not sure how easy it would be to get an svg for that (but it doesn't look good scaled :)
[20:05] <robert_ancell> bschaefer, oh yeah, xnox wanted to fix that
[20:05] <bschaefer> robert_ancell, that would be sweet :)
[20:29] <seb128> ochosi, spec is https://wiki.ubuntu.com/Sound#Title
[20:29] <seb128> "If sound is muted and an application tried to play sound in the past five seconds, a red speaker with a cross (audio-volume-muted-panel). "
[20:30] <seb128> bregma, you guys are working on bugfixing right? ;-)
[20:48] <seb128> robert_ancell, hey
[20:49] <robert_ancell> seb128, hello
[20:49] <seb128> robert_ancell, what's wrong with the indentation in https://code.launchpad.net/~seb128/unity-control-center/users-change-inactive/+merge/211608 ?
[20:49] <seb128> oh, the }
[20:49] <seb128> sorry ;-)
[20:49] <robert_ancell> yep
[21:33] <chrisccoulson> seb128, what are you doing around so late? ;)
[21:34]  * thumper found a real annoying bug last night
[21:34] <thumper> not got around to filing it yet
[21:34] <thumper> I have multiple users on my laptop
[21:35] <thumper> switching users means typing my password in, which is expected
[21:35] <thumper> but immediatly on the session starting, it locks the screen and I have to type the password again
[21:35]  * seb128 slaps chrisccoulson with an old trout
[21:35] <chrisccoulson> hah, thanks ;)
[21:36] <seb128> :p
[21:36] <bschaefer> thumper, with the new lockscreen? If so, check the list we have going here :) https://bugs.launchpad.net/unity/+bugs?field.tag=lockscreen
[21:36] <seb128> chrisccoulson, I'm working! some of us still do ubuntu uploads :p
[21:36] <thumper> bschaefer: yes
[21:36] <seb128> chrisccoulson, though I see you did some today as well ;-)
[21:36] <chrisccoulson> seb128, yeah, i thought it would make a change
[21:36] <bschaefer> thumper, theres one where if you let the lockscreen lock by it self it requires two log ins... soo im guessing its the same type of bug
[21:37] <thumper> bschaefer: bug 1291088
[21:37] <ubot2> Launchpad bug 1291088 in unity (Ubuntu) "Doesn't unlock when coming back from the greeter" [High,Triaged] https://launchpad.net/bugs/1291088
[21:37] <seb128> chrisccoulson, did you fix the firefox url handling? ;-)
[21:37] <bschaefer> thumper, sweet :), ill be sure to poke andyrock extra to look at that one
[21:37] <chrisccoulson> seb128, weren't you writing a patch for that? i told upstream that you were!
[21:37] <chrisccoulson> (j/k)
[21:38] <bschaefer> thumper, if you want to post on the bug how you're reproducing it, i bet that would help andyrock
[21:38] <seb128> chrisccoulson, I've one, it's a 1 liner in apturl that install a file in the directory firefox gives us for those ;-)
[21:38] <bschaefer> as I think hes having problems reproducing it atm
[21:38] <seb128> bschaefer, I think he fixed those by reinstalling gnome-screensaver last week
[21:39] <chrisccoulson> lol
[21:39] <seb128> bschaefer, his local hacked version was different from the one Trevinho got uploaded
[21:39] <thumper> bschaefer: he can get in touch with me if needed, happens every time
[21:39] <thumper> bschaefer: I added a comment about what I do
[21:39] <bschaefer> seb128, i see, interesting
[21:39] <bschaefer> thumper, awesome thanks a lot!
[21:39] <andyrock> hey
[21:39] <thumper> o/
[21:39] <bschaefer> thumper, also hows all that cloud stuff going :)?
[21:39] <andyrock> the problem is in gnome-screensaver :D
[21:39] <thumper> busy busy
[21:39] <bschaefer> sounds just like us :)
[21:39] <thumper> andyrock: don't pass the buck
[21:39] <seb128> andyrock, you better fix those issues before thumper gets angry at you!
[21:39] <bschaefer> haha
[21:40] <andyrock> i will
[21:40] <andyrock> just need some more time :D
[21:40]  * thumper hands andyrock two days
[21:40]  * bschaefer just has a broken gnome-screensaver :(
[21:40] <chrisccoulson> seb128, i'll fix it if you upload oxide in to the archive
[21:40] <chrisccoulson> it needs a debian/copyright file
[21:40] <chrisccoulson> :)
[21:41] <chrisccoulson> (i was only joking about that btw)
[21:41] <seb128> bschaefer, andyrock: joke aside, it would be good if you guys make some progress on unity bugs this week, nothing landing since thursday, we are pondering dropping the new lockscreen for trusty because it looks like we are going to need to make a call between that and getting regressions/bugs in unity fixed
[21:41] <seb128> chrisccoulson, (lol, no way :p)
[21:42] <chrisccoulson> seb128, it's only a 250MB upload
[21:42] <bschaefer> seb128, we have branches! Just waiting to get them landed
[21:42] <bschaefer> seb128, the indicator rendering behind is fixed as well
[21:42] <Trevinho> seb128: no worries, we can fix everything... :P
[21:42] <seb128> bschaefer, well, https://code.launchpad.net/unity/+activereviews ... it has 3 branches added since friday, 3 branches in 3 work days for a team of 4-5 people ...
[21:43] <seb128> Trevinho: ^
[21:43] <seb128> well, nothing against you guys
[21:43] <seb128> but the current trend doesn't give confidence
[21:43] <seb128> so it looks like we might need to drop features to give us budget for regression fixes
[21:45] <seb128> bschaefer, trevinho, andyrock: you guys might be stacking fixes locally, if that's the case it would be better to have regular landing with what is available rather than stacking and then dumping
[21:45] <Trevinho> seb128: there are also other things to focus on... but ok fixes will arrive
[21:45] <bschaefer> seb128, yeah, the silo stuff is still a bit new to us... we can try to pump more out to land quicker
[21:45] <seb128> Trevinho: sorry, nothing against you, and I know there is other work, we just need to make calls at some point, we can't do everything with the resources we have
[21:46] <seb128> so if you guys focus on features/hidpi work still, we need to make on what to do with spare resources
[21:46] <seb128> and for LTS that's going to be "fix the regressions"
[21:46] <seb128> there are quite some bugs with lim
[21:47] <bschaefer> hi-dpi work is pretty much on hold while im helping out andyrock
[21:47] <seb128> some issues with the launcher as well (like the tooltips are buggy, the "pimps/'>'" signs are buggy), with keybindings/tapping
[21:48] <seb128> super-<number> stopped working to focus apps (if you numbers are the top of the keyboard are behind a shift combo at least, like on the french layout)
[21:49] <Trevinho> seb128: mh, weird, but that's probably due to the fact that we support Keypad numbers as well now, but it's going to be probably easy to fix
[21:50] <Trevinho> seb128: anyway therea re lot of things to shape and we know, but still things are much better in general, also I hope that this cycle we won't forget the role of SRUs.
[21:51] <seb128> Trevinho: yeah, it's probably easy, like most of the other stack of small issues/regressions, the issue is that if nobody start focussing on those they are still going to be there in the LTS release and we are going to be getting press on the low quality of our LTS
[21:51] <seb128> we shouldn't rely on stus
[21:51] <seb128> srus
[21:51] <seb128> the release needs to be good, that's what gets most reviews
[21:51] <seb128> it's also what most users try/upgrade to
[21:55] <Trevinho> yes, but srus on release day as it used to be, should be done anyway... And it will hit most of people, allowing us to work till the last day
[21:56] <seb128> Trevinho: not sure about "most of people", it's at least not going to be the first experience for lot of people
[21:56] <seb128> it's still good if we fix bugs in SRUs
[21:56] <seb128> but the first experience is going to be what is on the iso/coming preinstalled for lot of users
[21:57] <seb128> that's usually the release iso, not the iso + surs
[21:57] <seb128> srus
[21:58] <Trevinho> indeed, not that I don't agree... I just hope that this time we'll get proper SRU released, and not like in the past cycle where we have backports ready and still not released
[21:59] <seb128> right
[21:59] <seb128> well, anyway, my point was: now is time to focus on fixing regressions and important bugs
[21:59] <seb128> users are going to be fine if hidpi support is missing in some part of the dash
[22:00] <seb128> they are not going to be if they bindings are not reliable
[22:02] <bschaefer> seb128, agreed!
[22:08] <TheMuso`> Since there are unity folks around, I've got a query. I am working on bug 1066157, and I've determined that there is a race condition of some sort, because whenever I use Orca's flat review mode, I can read the dash icons with Orca like normal. Is there a signal in the dash code somewhere that the a11y code could connect to, so it is notified of dash changes? Bearing in mind that the a11y code can only access either the result icon objects, the dash v
[22:08] <ubot2> Launchpad bug 1066157 in unity (Ubuntu) "dash +orca does not speak the names of application icons" [High,Triaged] https://launchpad.net/bugs/1066157
[22:08] <TheMuso`> If there was a signal, I could then signal at-spi to query unity again and thereby allow dash icons to be navigable and readable with orca.
[22:09] <Trevinho> TheMuso`: a signal when... happens what? :)
[22:12] <TheMuso`> Trevinho: Ok I probably didn't explain that well enough. What I think is happening, is that the at-spi registry ends up having stale information with regards to the dash, such that when an Orca user is trying to navigate the dash, they do not hear what icon has focus when navigating with the keyboard. They hear the group titles, like files and folders etc, but not the results themselves.
[22:13] <TheMuso`> When I mess around with a mode in Orca which allows one to read the screen from top to bottom as things are displayed, this triggers a refresh of the accessibility info in the registry for the dash, and the results are spoken when navigating with the keyboard.
[22:14] <TheMuso`> I am wondering whether there is some way of the accessibility code being notified of dash updates, so it can signal the at-spi registry to update the accessibility tree WRT the dash.
[22:20] <Trevinho> TheMuso`: mh, there are but related to results, not sure if there's a global one... andyrock or bschaefer might know more
[22:21] <bschaefer> I sadly do not know off the top of my head :(
[22:25] <andyrock> TheMuso`, for what i know dash accessibility never worked that well
[22:25] <andyrock> :/
[22:26] <TheMuso`> It works well enough for finding things. The text entry doesn't work I know, but that would require writing too much new code to fix at this late stage. The lenses also are not accessible, but the results at least do work. This is a regression from precise where unity 2d had working results, and as explained, if you use Orca in a particular way, the results are made available.
[22:28] <TheMuso`> I did see the on_realized signal in the dash controller, but unless the accessibility code is specifically passed a pointer to the controller object, it is unable to get a pointer via any other means, and that signal may not even be what I want.
[22:28] <andyrock> TheMuso`, i can take a look once the lockscreen bug list is empty
[22:29] <TheMuso`> I don't mind having a look, since I know you guys have your hands full, I'm just wondering whether you guys know of anything that could help.