[05:16] <pitti> charles: I had the same question a while ago, upower's test suite now has umockdev-synthesized bt mouse/keyboards
[09:00] <seb128> good morning desktopers!
[09:02] <darkxst> hi seb128
[09:03] <seb128> darkxst, hey, how are you?
[09:04] <darkxst> yeh good, and you?
[09:11] <seb128> I'm good thanks
[09:11] <seb128> nice, unity lock screen finally landed, it was getting late
[09:11] <seb128> bugfix mode now!
[09:11] <seb128> bregma, Trevinho, well done unity team ;-)
[09:45] <charles> pitti: thanks, noted :)
[09:49] <seb128> charles, good "morning"? ;-)
[09:54] <pitti> hey seb128
[09:57] <seb128> pitti, hey, wie gehts?
[09:57] <pitti> seb128: gut, danke! und Dir?
[09:57] <seb128> pitti, auch gut, danke!
[09:57] <pitti> seb128: amazingly tame and constructive systemd UDS discussion yesterday :)
[09:57] <seb128> happy to see the new lock screen landed, so we can focus on bugfixing
[09:57] <seb128> pitti, nice to read
[09:58] <seb128> pitti, I've a difficult time to put myself in postLTS mindset for that vUDS, still trying to get the LTS in shape :/
[09:58] <pitti> seb128: yeah, me too
[09:58] <seb128> timing is not great
[09:58] <pitti> it feels like we are still in the middle of the cycle
[09:59] <seb128> yeah, we are
[09:59] <seb128> well not "middle"
[09:59] <seb128> but we should work on getting the LTS solid atm
[09:59] <seb128> not stop everything to think about next cycle and discuss futur stuff for 3 days
[09:59] <pitti> ok, off to some sponsoring
[09:59] <seb128> oh well, some of the discussions are good to have
[10:00] <seb128> pitti, enjoy!
[10:00] <pitti> wroooooooom!
[10:00] <seb128> queue to 37, that's reasonable
[10:00] <pitti> and most of it < 1 week, indeed
[10:01] <pitti> let's see how much I can churn through today
[10:01] <seb128> yeah, I spend my monday afternoon on it
[10:01] <seb128> there are still some easy ones in there I think
[10:28] <ochosi> larsu: quick question, does the desktop_lockscreen mode do the same as the greeter_mode that indicators had before (or maybe still have)?
[10:29] <larsu> ochosi: apparently some indicators will have different controls on the lock screen than on the greeter
[10:29] <larsu> most of them will be the same, though
[10:30] <ochosi> right, so what's the diff with -power?
[10:30] <ochosi> (with -sound, i can imagine you'd have playback controls in the lockscreen, but not in the greeter?)
[10:30] <larsu> that's what I thought, but apparently not: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1291086/comments/3
[10:30] <ubot2`> Launchpad bug 1291086 in indicator-sound (Ubuntu) "Should only list running players in the greeter" [High,New]
[10:31] <larsu> ochosi: I don't know about -power
[10:31] <ochosi> ah, i see
[10:31] <ochosi> weird
[10:31] <ochosi> ok, i'll just wait and see what you guys do and then decide what to do with lightdm-gtk-greeter
[10:32] <ochosi> (for us greeter=lockscreen)
[10:32] <larsu> yeah
[10:32] <larsu> tbh, I'm not entirely happy with that distinction
[10:32] <ochosi> what would you do?
[10:33] <larsu> I don't have a better solution, which is why I gave in to Trevinho and added the lockscreen profile
[10:33] <larsu> ideally, lock screen and greeter would be the same thing
[10:33] <larsu> but there are some edge cases where that doesn't work
[10:34] <larsu> like, all user-related things, since the greeter is running in its own session
[10:35] <ochosi> yeah
[10:35] <ochosi> it's not really easy
[10:35] <ochosi> finding a sane policy for that
[10:36] <ochosi> especially cause locking the screen is more common for some devices (phones/tablets) than others (desktops @home)
[10:36] <larsu> right
[10:37] <ochosi> anyway, thanks for the heads up larsu
[10:37] <larsu> no problem!
[10:49] <seb128> mlankhorst, is that a known issue (happens when running unity-control-center under valgrind)
[10:49] <seb128> ==1528== Invalid read of size 1
[10:49] <seb128> ==1528==    at 0x402D9BA: strcmp (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
[10:49] <seb128> ==1528==    by 0x9676E1D: stub_find_dynamic (in /usr/lib/i386-linux-gnu/libglapi.so.0.0.0)
[10:49] <seb128> ==1528==    by 0x96769AB: ??? (in /usr/lib/i386-linux-gnu/libglapi.so.0.0.0)
[10:49] <seb128> ==1528==    by 0x9676C3C: _glapi_get_proc_address (in /usr/lib/i386-linux-gnu/libglapi.so.0.0.0)
[10:49] <seb128> ==1528==    by 0x9628826: glXGetProcAddress (in /usr/lib/i386-linux-gnu/mesa/libGL.so.1.2.0)
[10:51] <mlankhorst> not that I'm aware of?
[10:58] <seb128> do you get those as well?
[11:07] <mlankhorst> sec I was doing bug handling all morning, let me try :-)
[11:12] <mlankhorst> seb128: with some looking at valgrind it claims to be freed in cogl_feature_check :/
[11:14] <mlankhorst> hm might be bogus though, I'll try more aggressive options for valgrind
[11:15] <seb128> mlankhorst, hum, it might be https://git.gnome.org/browse/cogl/commit/?h=cogl-1.16&id=fc4f882db70960c615fb8c211ef7d6612a3e2118
[11:15] <seb128> or not
[11:19] <mlankhorst> weird stuff
[11:19] <mlankhorst> oh right, glapi is innocent here, bug is in libcogl
[11:21] <mlankhorst> so it's not a mesa bug afaict, it's because glxGetProcAddress was called with a free'd argument
[11:40]  * mdeslaur <3 new lock screen :)
[11:44] <rickspencer3> hey guys, new lock screen looks really nice
[12:30] <seb128> rickspencer3, hey, thanks, kudos to andyrock and Trevinho
[12:30] <rickspencer3> hey seb128
[12:31] <rickspencer3> seb128, nice that all these updates are landing so cleanly
[12:31] <rickspencer3> you can hardly tell that major updates are happening, everything "just works" when I dist-upgrade :)
[12:31] <seb128> rickspencer3, yeah, though a bit later in the cycle that we would have preferred, but we should be done with changes now
[12:32] <rickspencer3> seb128, you know what I think ... so long as it's ready to land, land it :)
[12:32] <seb128> ;-)
[12:32] <rickspencer3> better land it late and right, than land it early with regressions
[12:32] <rickspencer3> fix it before you land it
[12:33] <rickspencer3> blah blah blah, etc... etc... etc...
[12:33] <didrocks> +1000
[12:33] <didrocks> (just saying)
[12:36] <seb128> yeah, better to land early without regressions though :p
[12:36] <seb128> what, having your cake and eating it too?! ;-)
[12:37] <didrocks> seb128: coffee with my cake please :)
[12:37] <seb128> didrocks, ;-)
[12:37]  * didrocks is serious… and waiting!
[12:37] <didrocks> :)
[12:38] <seb128> didrocks, it's UDS, just go to the table in the conference area, they have the coffee and cake
[12:38]  * didrocks looks around and feels something is wrong… but not sure what… :)
[13:05] <desrt> good morning all
[13:06] <desrt> virtual cake!
[13:06] <seb128> desrt, good morning to you!
[13:06] <seb128> desrt, I saw you got a patch up for your gsettings bug, nice ;-)
[13:06] <desrt> ya
[13:06] <desrt> i'm not happy about it
[13:06] <desrt> but i spent like a week trying to do it 'the right way'
[13:06] <desrt> and ended up with a patch that has no earthly chance of getting merged a week before hard code freeze
[13:07] <seb128> no rewriting of gobject before release!
[13:07] <seb128> or glib
[13:07] <ogra_> both !
[13:07] <xnox> in virt-manager, the global menus stopped working. They are shown (File, edit, etc.) but i can't open anyone of them.
[13:07] <xnox> how / where should I report this?
[13:08] <seb128> xnox, do you use the local integrate menu?
[13:08] <larsu> xnox: works for me
[13:08] <larsu> *cough*
[13:08] <xnox> seb128: i have local integrated menus in gnome-terminal.
[13:09] <desrt> seb128: in any case, timely testing is very much appreciated
[13:09] <seb128> xnox, that was not the question
[13:09] <xnox> seb128: however, i don't think that works with virt-manager, since that grabs focus into inside the virtual-machine.
[13:09] <larsu> xnox: it uses unity-gtk-module, so file a bug against that please (or talk to attente)
[13:09] <xnox> seb128: how do i verify to answer your question?
[13:09] <seb128> xnox, system settings -> appearence -> behaviour
[13:10] <seb128> the "show menu in" option
[13:10] <xnox> it says in the menu bar.
[13:10] <seb128> k, so in the panel like before
[13:10] <seb128> and what's the issue? are the menu items there but not doing anything?
[13:11] <xnox> hm, something is very odd, let me restart my session.
[13:12] <seb128> desrt, do you feel confident enough in the patch to have it pushed to trusty? (that's the best way to get feedback)
[13:12] <seb128> desrt, well, I'm going to test it locally before anyway, but still working for me doesn't mean it's a good idea to push it to trusty ;-)
[13:12] <desrt> seb128: if it works for you, push it
[13:12] <desrt> if not, talk to me :
[13:12] <desrt> :)
[13:12] <seb128> k
[13:13] <seb128> you can sure count on that ;-)
[13:21] <chrisccoulson> hello desktop!
[13:21] <desrt> chrisccoulson: hihi
[13:22] <seb128> chrisccoulson, hey, how are you?
[13:22] <chrisccoulson> hi desrt, seb128
[13:22] <chrisccoulson> seb128, yeah, good thanks. mostly avoided UDS so far ;)
[13:23] <seb128> haha
[13:23] <seb128> chrisccoulson, I'm sure you are going to have at least one session (I saw webbrowser for touch on the schedule)
[13:23]  * chrisccoulson hides
[13:25] <chrisccoulson> seb128, i can't have any more work assigned to me ;)
[13:26] <seb128> chrisccoulson, you sure can, let me show you!
[13:26]  * seb128 assigns bugs to chrisccoulson
[13:26] <chrisccoulson> lol
[13:26] <chrisccoulson> i'll just assign them back to you ;)
[13:26] <seb128> chrisccoulson, joke aside, I hope you fix that firefox url handling issue before release, or I'm going to upload the apturl config hack ;-)
[13:27] <seb128> chrisccoulson, that's where you regret you never code upload rights out of firefox set ;-)
[13:32] <chrisccoulson> seb128, firefox needs fixing properly. can't you get the firefox maintainer to do that? ;)
[13:32] <seb128> chrisccoulson, see, you just got more work assigned, and by yourself! ;-)
[13:33] <chrisccoulson> lol
[13:33] <chrisccoulson> i haven't spent more than 5 minutes on firefox in the last month or so
[13:45] <mdeslaur> xnox: FYI, I now see your virt-manager issue too
[13:47] <seb128> xnox, mdeslaur: when did that start? what happens exactly, the menus are there but not doing anything?
[13:48] <mdeslaur> seb128: yeah, you click on them and nothing happens, the menus don't open
[13:49] <mdeslaur> not sure when it started, as I don't use them often
[13:49] <seb128> does it work with e.g alt-f ?
[13:49] <xnox> seb128: alt-f, triggers hud on alt, and that's the only way i can run any of the menu items
[13:49] <mdeslaur> when the vm is powered off, the menu items display, with a lot of them inactive...when you power on the vm, they won't appear anymore
[13:49] <xnox> seb128: alt-space does work.
[13:50] <mdeslaur> seb128: alt-f doesn't work
[13:50] <xnox> bug #1291370
[13:50] <ubot2`> Launchpad bug 1291370 in virt-manager (Ubuntu) "in virtual-manager, the global-menu or local integrated menus stopped working in the vm-display" [Undecided,New] https://launchpad.net/bugs/1291370
[13:50] <mdeslaur> I think it's when virt-manager tries to make certain menu items active, something goes wrong
[13:50] <xnox> has screenshot.
[13:50] <xnox> no way to open up file, virtual machine, view, send key.
[13:51] <mdeslaur> it of course works well with UBUNTU_MENUPROXY=0, so it's not virt-manager itself
[13:52] <xnox> mdeslaur: well - virt-manager is the last python2 gobject application we use?!
[13:52] <xnox> =)
[13:53] <larsu> this sounds like a unity issue to me
[13:53] <mdeslaur> xnox: quite possibly :)
[13:53] <xnox> mdeslaur: larsu: propose adding it to blacklist? it's not _that_ popular app.
[13:53] <mdeslaur> xnox: uhm, no. this is a new bug
[13:54] <larsu> xnox: you're right! I can also not click the menu items in your screenshot
[13:54] <mdeslaur> xnox: something is busted somewhere
[13:55] <mdeslaur> global menu in gtk2 is a patch, right?
[13:55] <mdeslaur> oh, it's a plugin, huh
[13:55] <xnox> larsu: lol =)
[13:56] <mdeslaur> I'll try reverting unity-gtk-module this afternoon
[14:00] <xnox> hm, i only have unity going from 20140305 -> 0311. I'll check if that's where the regression happened.
[14:13] <kenvandine> seb128, xnox: https://code.launchpad.net/~ken-vandine/ubuntu-wallpapers/14_04_wallpapers/+merge/210616
[14:14] <xnox> kenvandine: excellent, let me review that. I'd like to learn ubuntu-wallpapers packaging.
[14:15] <xnox> i'm hearing rick =)
[14:15] <kenvandine> me too :)
[14:15] <xnox> best hangout ever! =)
[14:15] <kenvandine> haha
[14:15] <xnox> wrong channel as well =)
[14:15] <xnox> kenvandine: but oh well ;-)
[14:15] <xnox> (above is about #ubuntu-uds-core-1)
[14:16] <kenvandine> at least someone here knew what you were talking about
[14:17] <seb128> hangout, technology for the futur :p
[14:18] <xnox> seb128: technology of back to the future =)
[14:24] <kenvandine> xnox, i just pushed another revision to that branch, the upstream version was still 13.04... i guess it's time to update that :)
[14:29] <xnox> kenvandine: good. =)
[14:29] <kenvandine> guess we missed that for 13.10
[14:30] <kenvandine> with daily release updating the versions for us, it's easy to miss
[14:30] <kenvandine> 13.04.0+13.10..... is confusing :)
[14:42] <kenvandine> alesage, i'm getting CI failures that look like jenkins problems
[14:42] <kenvandine> hudson.util.IOException2: remote file operation failed: /iSCSI/storage/jenkins/workspace/ubuntu-wallpapers-trusty-amd64-ci at hudson.remoting.Channel@7ae9b86f:genie
[14:42] <kenvandine> MR is https://code.launchpad.net/~ken-vandine/ubuntu-wallpapers/14_04_wallpapers/+merge/210616
[14:42] <kenvandine> alesage, ^^
[14:42] <alesage> kenvandine, I'll look into, remedy will probably come from CI though
[14:42] <alesage> kenvandine, also hi :)
[14:43] <kenvandine> alesage, hello :)
[14:45] <alesage> kenvandine, btw I'll be helping with content-hub QA, we should chat about at some point
[14:46] <mlankhorst> bah, xorg bugs are exploding :o
[14:46] <mlankhorst> boom!
[14:46] <kenvandine> alesage, sweet!
[14:47] <kenvandine> alesage, yes lets talk soon
[15:06] <pitti> seb128: c'est l'heure de la glace maintenant !
[15:09] <pitti> seb128: nothing to sponsor any more, job done, time for ice and UDS :)
[15:12] <seb128> pitti, good job! enjoy
[15:24] <mlankhorst> --keep-stacktraces=alloc-and-free is my new favorite valgrind option <3
[15:24] <seb128> what does it do?
[15:29] <mlankhorst> guessing it keeps the alloc stacktrace for freed memory too
[15:29] <attente> i can't boot my machine... i keep getting "The disk drive for /dev/mapper/ubuntu--vg-swap_1 is not ready yet or not present" under plymouth :(
[15:30] <seb128> attente, try asking on #ubuntu-devel
[15:30] <seb128> or maybe xnox can help there
[19:33] <robert_ancell> mterry, did you see https://code.launchpad.net/~robert-ancell/unity-greeter/double-authenticate/+merge/210529?
[19:33] <mterry> robert_ancell, yes...  haven't gotten to it.  But now is actually a good time
[19:33] <robert_ancell> fginther, is jenkins asleep? https://code.launchpad.net/~robert-ancell/lightdm/guest-session-type/+merge/210540
[19:35] <mterry> robert_ancell, I assume you tested this?  Code itself looks fine
[19:35] <robert_ancell> mterry, yeah, works here
[19:35] <mterry> robert_ancell, approved!
[19:35] <robert_ancell> mterry, ta!
[19:37] <fginther> robert_ancell, the MP is approved, as a result jenkins will ignore it (this is a consequence of moving to ci-train for merging). If it's set back to needs review, jenkins will test it.
[19:37] <robert_ancell> fginther, we're not on the ci-train unless someone changed something yesterday
[19:38] <robert_ancell> fginther, is there a list of projects on the ci-train somewhere?
[19:39] <fginther> robert_ancell, I saw an MP in the last day or two indicating that everything trusty should be on ci-train now. looking for it
[19:40] <fginther> robert_ancell, https://code.launchpad.net/~robru/cupstream2distro-config/ci-train-everywhere/+merge/210314
[19:41] <fginther> robert_ancell, for the official list of projects on ci-train: https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0Au6idq7TkpUUdC05a2ZQSmgwU2NFYnJQOE9qMDRYa3c&usp=drive_web#gid=1
[19:41] <robert_ancell> humf
[19:46] <robert_ancell> seb128, where is the CI train documentation?
[19:46] <seb128> robert_ancell, there is none
[19:46] <robert_ancell> awesome
[19:46] <robert_ancell> where is the ci train magic spreadsheet?
[19:46] <seb128> robert_ancell, it's ongoing work/moving parts and didrocks said he had spent quite some time previously on documentation the workflow than nobody was reading
[19:47] <seb128> robert_ancell, https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFlCc1VzeVZzWmdBZS11WERjdVc3dmc#gid=0
[19:47] <seb128> if you look for the list of landings in the queue
[19:47] <seb128> robert_ancell, https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0Au6idq7TkpUUdC05a2ZQSmgwU2NFYnJQOE9qMDRYa3c&usp=drive_web#gid=1 if you want the list of projects and their landers
[19:47] <seb128> what's the real question/issue?
[19:48] <seb128> e.g do you try to get something added to it, or to be lander for something, or to get something to land?
[19:48] <robert_ancell> seb128, apparently lightdm is on the train now and I've got some MPs I need to land
[19:48] <seb128> weird
[19:48] <seb128> that seems backward
[19:48] <seb128> but I think didrocks said they want to close the infra for non CI train
[19:49] <robert_ancell> seb128, fginther says https://code.launchpad.net/~robru/cupstream2distro-config/ci-train-everywhere/+merge/210314 is the cause
[19:49] <robert_ancell> not sure if that is correct or not
[19:49] <seb128> likely, they said they want to stop having to maintain 2 infras
[19:49] <seb128> which makes sense
[19:49] <robert_ancell> I can't edit that spreadsheet
[19:49] <seb128> but the way they are doing it might be suboptimal
[19:50] <seb128> right, you didn't get landing training/got added to that group
[19:50] <seb128> but the landing process is reversed
[19:50] <seb128> e.g you need to upload to Ubuntu first and then it gets to trunk
[19:50] <seb128> it's fine for touch, but I'm not sure that you are going to like that for lightdm
[19:51] <robert_ancell> no, that makes absolutely no sense here
[19:51] <seb128> if not I guess you can commit manually to your trunk and argue with didrocks&co later
[19:51] <robert_ancell> I'm just going to manually upload it
[19:51] <robert_ancell> yeah
[19:51] <robert_ancell> But I kind of wanted Jenkins to do the checks for me
[19:51] <seb128> I think that should still be possible, but check with fginther
[19:52] <seb128> looks like something we should provide to any upstream wanting to help us improve quality
[19:52] <seb128> them being in touch landing or not
[19:52] <robert_ancell> seb128, what about unity-greeter? Guess I should do that manually too?
[19:52] <seb128> that seems like more Ubuntu/Unity specific
[19:52] <seb128> I would be happy to have it in CI train, the process is ok
[19:53] <robert_ancell> that codebase will be dead next cycle anyway, so not really worth getting it up to scratch
[19:53] <seb128> you list merge requests, that gives you a ppa to test built with trunk+those, if you hack that uploads to the archive/merge to trunk
[19:53] <seb128> there is nothing to get up to scratch
[19:53] <seb128> they put lightdm in there :p
[19:53] <seb128> I mean you don't have any pre-require on tests or anything
[19:53] <robert_ancell> seb128, but neither lightdm or u-g are automatically uploaded to the archive, they are both manually done
[19:54] <seb128> well, you could decide that from now u-g follows the same landing than most of our stuff
[19:54] <seb128> e.g no release, CI train
[19:54] <robert_ancell> that's what we had before right?
[19:54] <seb128> e.g somebody lists merge requests, press the button and things get merged/uploaded, iterate as often as needed
[19:55] <seb128> no, before we had automerge and regular uploads
[19:55] <seb128> now it's the other way around, with a manual "that component can land" from the people checking the image in between
[19:55] <seb128> e.g you say "I've those 3 changes to land, please give me a silo"
[19:56] <seb128> they give you a "slot", which basically means you click a button and get a ppa with the debs of trunk+<what you asked>
[19:56] <seb128> you test that, if happy you press the upload button, which uploads for you
[19:56] <seb128> once it's in ubuntu proper (out of proposed) you press the merge/clean button which merges to trunk and clean the ppa you had
[19:57] <seb128> in practice it's quite nice, the only real work you have to do is list merge requests in order
[19:57] <seb128> but you get a ppa for free, which includes armhf, which is nice for testing before uploading
[20:00] <robert_ancell> seb128, regarding the face images - we should just drop support for user images from the GUI because that's confusing
[20:00] <robert_ancell> seb128, actually I can't even find the controls to change the image, where are they?
[20:01] <robert_ancell> ah, I found it
[20:01] <seb128> robert_ancell, click on your image?
[20:01] <robert_ancell> I was clicking the one on the left
[20:01] <seb128> well, I don't find them confusing, I picked an icon for each ones of my users
[20:01] <robert_ancell> that doesn't get used anywhere else in the gui
[20:01] <seb128> they are not very fancy but that's better than all the default icon
[20:01] <seb128> it does
[20:02] <robert_ancell> I mean drop all the icons
[20:02] <robert_ancell> oh, where else?
[20:02] <seb128> on the session menu
[20:02] <seb128> indicator-session
[20:02] <robert_ancell> oh, I assumed that was a fixed icon
[20:02] <seb128> the list of users has their icons
[20:03] <robert_ancell> seb128, we should get a set of those face icons from design and ship those with u-c-c then
[20:03] <robert_ancell> the orange ones
[20:03] <robert_ancell> anyone from design awake?
[20:04] <seb128> I doubt it, they are in London for most of them and don't work in evenings
[20:04] <seb128> open a bug, I can ping around tomorrow
[20:04] <robert_ancell> will do
[20:04] <seb128> but otherwise if we think it's not import we can drop the feature, I would be happy to build u-c-c without cheese
[20:04] <robert_ancell> seb128, is the "ping design" thing still open task on ayatanna-design?
[20:04] <robert_ancell> I'd just drop it
[20:05] <seb128> the most bugs we report is user account failing to load due to cogl/clutter issues coming through cheese
[20:05] <seb128> yeah, open a bug and add ayatana-design
[20:05] <seb128> robert_ancell, ok, open a bug, I'm going to follow up on it tomorrow
[20:05] <seb128> on that note I need to go
[20:05] <robert_ancell> bye
[20:06] <seb128> night (or good day to you .au/.nz)