[01:23] <popey> hmm. i have the "battery gauge doesn't update in the panel" issue again on saucy
[01:23] <popey> i suspect this is suspend/resume related
[01:24] <popey> i suspeneded when i was on power, and the indicator showed it was charging. I woke the laptop up just now, off power, and it still shows charging
[03:37] <pitti> Good morning
[03:42] <RAOF> pitti: Uh, what! Are you up super-duper early?
[03:43] <pitti> RAOF: yeah, couldn't sleep any more after my wife got up
[06:37] <ricotz> chrisccoulson, hi :), i hope you like to update firefox to 23b9 while saucy still is on b4, or maybe you have it in a ppa somewhere already
[07:14] <tkamppeter> mlankhorst, hi
[07:22] <sil2100> didrocks: hi! I guess I can safely publish the misc stack, as the changes recommended were approved by you, right? ;)
[07:25] <sil2100> didrocks: and in the case of, for instance, indicators where the build job failed because armhf failed to build of a chroot problem - should I re-run just the 'publish' job once its built or can I do it differently not to trigger the tests again?
[07:26] <didrocks> sil2100: sure sure, no need to double ack if it's the changes I approved :)
[07:26] <didrocks> sil2100: better rebuilding in the ppa
[07:27] <didrocks> sil2100: and rerun the whole stack with "foo"
[07:27] <sil2100> didrocks: ok, too bad it will trigger the check job again, but well ;)
[07:27] <didrocks> sil2100: right, but at least, we know if there is a manual publicaiton in progress
[07:33] <jibel> good morning
[07:36] <didrocks> salut jibel
[07:36] <didrocks> jibel: FYI, the jenkins node was down on ati, I restarted it
[07:37] <jibel> didrocks, salut didrocks
[07:37] <didrocks> sil2100: jibel: I won't have the time at all to debug anything today, there is a delivery for IoM and I need to concentrate on that
[07:37] <jibel> didrocks, ah, that's probably becaue the machine has been restarted yesterday evening while debugging mir failures
[07:37] <sil2100> didrocks: ACK!
[07:38] <jibel> didrocks, I'll investigate why it doesn't start automatically
[07:38] <jibel> as it should
[07:38] <didrocks> jibel: thanks!
[07:38] <sil2100> jibel: yep, I guess well be doing some more of that today as well - can I poke you around for advice ;)
[07:38] <sil2100> ?
[07:40] <jibel> sil2100, just poke and if I can advise I'll do :)
[07:41] <chrisccoulson> good morning
[07:42] <seb128> good morning desktopers
[07:42] <seb128> hey didrocks chrisccoulson jibel sil2100, how is everyone?
[07:43] <didrocks> hey seb128!
[07:43] <chrisccoulson> seb128, yeah, good thanks. how are you?
[07:45] <jibel> Salut seb128 , I'm fine thanks, you?
[07:46] <seb128> I'm good thanks
[07:51] <sil2100> seb128: morning!
[07:55] <larsu> seb128: happy Friday!
[07:56] <seb128> larsu, hey, happy friday to you too!
[07:58]  * larsu had one of those put-laptop-into-bagpack-even-though-it-was-not-suspended situations yesterday
[07:58] <larsu> now I'm paranoid about it again ... it used to work so reliably :(
[08:03] <lan3y> morning
[08:03] <lan3y> arg
[08:04] <seb128> Laney, hey
[08:04] <seb128> Laney, you fall off the internet again during the night?
[08:04] <Laney> just this network apparently
[08:05] <seb128> k
[08:05] <seb128> Laney, happy friday in any case ;-)
[08:05] <Laney> yeah! that came around fast
[08:05] <Laney> happy friday
[08:19] <rickspencer3> hi pitti
[08:19] <pitti> hey rickspencer3
[08:20] <rickspencer3> pitti, I'm watching your mails about autopackging testing
[08:20] <rickspencer3> do I understand correctly, that these are tests that in run in proposed?
[08:20] <rickspencer3> and then packages don't get copied into the release pocket if they don't pass?
[08:20] <pitti> rickspencer3: correct; we use them as a gatekeeper for what is allowed to propagate to suacy
[08:20] <rickspencer3> wow, we have a lot of CI
[08:21] <rickspencer3> :)
[08:21] <pitti> rickspencer3: in general, yes; not just the packages themselves, also any of its rdepends
[08:21] <pitti> rickspencer3: i. e. if we upload a new gtk and that breaks ubiquity's tests, gtk won't propagate
[08:21] <rickspencer3> pitti, right
[08:21] <seb128> (which is the case atm, it's blocked by a notify-osd test issue)
[08:21] <rickspencer3> so we have gates in place at the developer level, at the team level (for Canonical developed upstreams)
[08:21] <rickspencer3> then we have proposed, then we have the smoke tests
[08:22] <rickspencer3> then we have phased updates
[08:22] <jibel> seb128, which started failing with latest gtk+3.0 upload
[08:23] <seb128> jibel, it doesn't seem so
[08:23] <jibel> seb128, not latest but 3.8.2-3ubuntu1
[08:23] <pitti> notify-osd is rather broken indeed; I tried some things yesterday (adding at-spi2-core dep, running under d-bus), but nothing helps; that needs someone who actually understands notify-osd
[08:24] <seb128> notify-osd didn't change in years
[08:24] <seb128> did those test ever work reliably?
[08:24] <jibel> they did until July 8th
[08:24] <seb128> jibel, https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy-adt-notify-osd/ suggest it broke around jul 16
[08:24] <seb128> but there was no gtk update around that date
[08:24] <rickspencer3> thanks pitti
[08:25] <rickspencer3> pitti, so I guess we can't run auto-pilot tests as part of autopackage?
[08:25] <seb128> jibel, https://launchpad.net/ubuntu/+source/gtk+3.0/+changelog
[08:25] <pitti> seb128: it's complaining about not being able to connect to at-spi, so it might be somewhere else in the stack
[08:25] <seb128> jibel, uploads were on the 8 and on the 23 ... tests started failing in between
[08:25] <pitti> rickspencer3: we can
[08:26] <pitti> rickspencer3: I even run ap tests as part of the package build now, in autopilot-gtk
[08:26] <pitti> rickspencer3: apparently I was the first one to try that, but it's working quite well
[08:26] <Laney> yeah #35 passed with -3ubuntuX
[08:26] <rickspencer3> pitti, any reason we shouldn't run all the tests that we use for smoke tests in -proposed?
[08:27] <pitti> rickspencer3: won't work for unity and other stuff that needs 3D
[08:27] <pitti> rickspencer3: this can only be xvfb
[08:27] <rickspencer3> ah
[08:27] <pitti> rickspencer3: for 2D stuff it should work just fine
[08:27] <rickspencer3> that seems like, long term, we could crack that problem
[08:27] <rickspencer3> and then if we were running the tests there, our smoke tests would almost always be green
[08:27] <rickspencer3> because we would be catching many more failures before even making the image
[08:28] <pitti> rickspencer3: well, ideally these wouldn't even land in -proposed nowadays as we run them on the upstream side already?
[08:28] <rickspencer3> pitti, right
[08:28] <rickspencer3> so at each step, there is more integration
[08:28] <rickspencer3> so some chance of a breakage
[08:29] <rickspencer3> but at each step, 99% of the problems should be filtered out
[08:29] <jibel> seb128, right, and run on the 16th has been triggered by an upload of dbus
[08:29] <rickspencer3> so, from the developer to the teams trunk to -proposed to the image
[08:29] <seb128> pitti, jibel, Laney: https://launchpad.net/ubuntu/+source/at-spi2-core/+changelog changed on the 16 ... maybe trying downgrading at-spi would be useful
[08:31]  * seb128 is going to let that to the Ubuntu GNOME guys to debug though, no time to spend trying to debug gtk atm, too much ubuntu touch work to do
[08:31] <pitti> seb128: yeah, that one sounds plausible
[08:32] <seb128> pitti, there were changes around upstart session as well: http://launchpadlibrarian.net/143250524/at-spi2-core_2.9.3-1_2.9.3-1ubuntu1.diff.gz
[08:32] <pitti> if notify-osd's test was fixed to use VERBOSE=yes, you could see the error (which is failing to start up at-spi)
[08:32] <seb128> though that doesn't disable dbus activation or anything, so that should break
[08:32] <seb128> *shouldn't*
[08:32] <pitti> seb128: the autopkgtest doesn't even start a d-bus
[08:32] <pitti> seb128: I tried that too, but when I run it under a session bus it hangs forever
[08:32] <pitti> at that point I gave up
[08:32] <seb128> hum
[08:34] <seb128> jibel, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html has the notify-osd test as RUNNING is that normal?
[08:34] <seb128> pitti, https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy-adt-notify-osd/ARCH=i386,label=adt/ ... the most recent run worked out on i386
[08:35] <jibel> seb128, no it is not. looking
[08:35] <pitti> yes, indeed
[08:35] <pitti> seb128: I'll retry amd64 as well, just for fun
[08:35] <seb128> pitti, thanks
[08:35] <seb128> can I retry those myself in some way?
[08:36] <pitti> seb128: if you have VPN access to the lab?
[08:36] <seb128> pitti, yes
[08:36] <pitti> seb128: the "private jenkins" URL in the autopkgtest fail mails point to it
[08:36] <seb128> but I only used it for cu2d stuff so far
[08:36] <pitti> http://10.98.0.1:8080/view/Saucy/view/AutoPkgTest/job/saucy-adt-notify-osd/
[08:36] <pitti> #40 -> matrix reloaded -> do it
[08:36] <seb128> pitti, ok, that shows amd64 as running atm
[08:37] <pitti> seb128: yes, I kicked it
[08:38] <seb128> pitti, ok, so the "rebuild matrix" button on there?
[08:38] <pitti> seb128: oui
[08:38] <seb128> (/me just looked on another job that is not building)
[08:38] <seb128> pitti, merci!
[08:38] <pitti> seb128: or "build now", but matrix is if you only want to build one arch
[08:39] <pitti> seb128: you can watch it in realtime on http://10.98.0.1:8080/view/Saucy/view/AutoPkgTest/job/saucy-adt-notify-osd/ARCH=amd64,label=adt/40/console FYI
[08:39] <seb128> pitti, yeah, I've it on screen
[08:39] <seb128> that's using otto right?
[08:40] <pitti> seb128: no
[08:40] <pitti> seb128: lp:auto-package-testing
[08:40] <seb128> oh ok, I though the real time log was added by didrocks/jibel with the switch to otto
[08:40] <pitti> seb128: i. e. prepare-testbed and run-adt-rest, just what everybody else should be using
[08:40] <pitti> seb128: but a  mere apt-get source notify-osd, build, make check reproduces it, too
[08:42] <jibel> seb128, we switched daily-release testing from utah to otto, this is different from package testing in proposed which uses autopkgtest
[08:42] <seb128> jibel, right, I got slightly confused by the jenkins side ;-)
[08:43] <jibel> np, jenkins confuses me too :)
[08:43] <seb128> nice to have real time log displayed in any case
[08:43] <seb128> pitti, \o/ notify-osd # PASS:  1
[08:43] <seb128> # FAIL:  0
[08:43] <seb128> Finished: SUCCESS
[08:44] <pitti> nice
[08:44] <seb128> green we are
[08:44] <seb128> so maybe it was just the missing depends on at-spi which got added yesterday
[08:44] <pitti> so, something got fixed in the past two days :)
[08:44] <seb128> pitti, https://launchpad.net/ubuntu/+source/notify-osd/0.9.35+13.10.20130725-0ubuntu1
[08:44] <seb128> "  * Have the tests depend on at-spi2-core."
[08:44] <pitti> ah, indeed
[08:44] <seb128> I guess something else was pulling it in before
[08:45] <pitti> seb128: but that sounds a bit wrong -- shouldn't the notify-osd binary depend on at-spi2-core instead, not just the test?
[08:46] <darkxst> seb128, pitti: Hey!
[08:46] <seb128> darkxst, hey
[08:46] <pitti> hey darkxst
[08:46] <seb128> pitti, well, at-spi is only for a11y, I'm not sure it's an hard depends to use notify-osd
[08:48] <darkxst> for alpha 2, we had two crashes that seem to be related to missing indicator packages bug 1204289 and 1204290
[08:48] <ubot2`> Launchpad bug 1204289 in network-manager-applet (Ubuntu) "nm-applet crashed with SIGSEGV" [Undecided,Invalid] https://launchpad.net/bugs/1204289
[08:48] <ubot2`> Launchpad bug 1204290 in ubiquity (Ubuntu) "panel crashed with SIGSEGV in indicator_object_get_entries()" [Undecided,Confirmed] https://launchpad.net/bugs/1204290
[08:49] <darkxst> ok to add dependencies to ubiquity?
[08:49] <seb128> darkxst, that's not going to solve it
[08:49] <darkxst> why not?
[08:50] <seb128> larsu, ^ we need to teach ubiquity about new indicators, it's trying to load the old .so
[08:50] <seb128> darkxst, ^
[08:50] <seb128> darkxst, because that files doesn't exist anymore
[08:50] <darkxst> seb128, we don't ship any indicators
[08:50] <seb128> well, shipping some wouldn't help
[08:50] <seb128> it tries to load a .so that doesn't exist anymore in the indicator-ng code
[08:50] <seb128> (e.g the gmenu based one)
[08:51] <seb128> ubiquity needs to learn the new format, same as unity-panel-service and indicator-applet
[08:51] <darkxst> ok i see, figured it was ubuntu GNOME specific, but perhpas not
[08:51] <seb128> likely not
[08:53] <larsu> seb128: which indicators does ubiquity use? (I'm guessing at least network and sound?)
[08:53] <larsu> and datetime
[08:53] <larsu> and session?!
[08:53] <seb128> static const char* indicators[] = {
[08:53] <seb128> 	"/usr/lib/indicators3/7/libsession.so",
[08:53] <seb128> 	"/usr/lib/indicators3/7/libapplication.so",
[08:53] <seb128> 	"/usr/lib/indicators3/7/libsoundmenu.so",
[08:53] <seb128> 	NULL
[08:53] <seb128> larsu, ^
[08:54] <darkxst> seb128, I didnt see any other reports from other flavours though
[08:54] <seb128> larsu, they basically indicator_object_new_from_file() those
[08:54] <seb128> darkxst, I guess there is not so many testers of a2
[08:54] <seb128> darkxst, and ubiquity-kde might not be impacted
[08:55] <seb128> darkxst, but my reading of the code is that the session menu can't work atm
[08:55] <seb128> it should be missing on all ubiquity-gtk flavors
[08:55] <larsu> seb128: thanks. Do you think it makes sense to have a ubuiquity profile instead of a static list in ubiquity?
[08:56] <seb128> xnox, ^ opinion ?
[08:57] <seb128> larsu, I would just go for the easiest, e.g hardcode the new filenames
[08:57] <seb128> larsu, libindicator still work the same way? e.g you can call indicator_object_get_entries() etc on those?
[08:58] <larsu> seb128: I'm leaning towards that as well, but I don't like it...
[08:58] <seb128> larsu, if you want to look at the code it's lp:ubiquity src/panel/panel.c
[08:58] <larsu> seb128: yes, the only thing that's different is that you need to parse the indicator file (with indicatorng, which is a subclass of indicatorobject)
[08:58] <seb128> larsu, well, my understanding is that ubiquity is going to be rewritten in qml at some point
[08:58] <seb128> larsu, so I wouldn't spend too much time on it making the code nice
[08:59] <larsu> seb128: well but then we'll carry the hack into the qml version, because we don't have proper profiles for it
[08:59] <larsu> also, we might want different menus on there
[08:59] <seb128> larsu, let's see I'm all for proper installer profile, but ETOOMUCHTODO and let's get the phone profiles done first
[08:59] <seb128> larsu, well your call if you want to do it the proper way
[08:59] <seb128> but it's more important to land unitymenumodel
[09:00] <seb128> maybe let's do the hack to unbreak it
[09:00] <larsu> seb128: HAHA first time I've seen ETOOMUCHTODO :)
[09:00]  * larsu loves that
[09:00] <seb128> and keep a bug about doing it the proper way in some weeks when we are over the "need to land stuff to unblock other people"
[09:00] <seb128> larsu, ;-)
[09:00] <larsu> seb128: it's not that much work really, just many MRs (for the indicators, we only need 3 extra lines in the indicator files)
[09:01] <seb128> larsu, do you want to do it (you are probably going to be the most efficient to do it since you know the libindicator changes best here)
[09:01] <seb128> larsu, e.g should I assign it to you?
[09:02] <larsu> seb128: yes. I'll do it today. Prepare for some code reviews :P
[09:02] <seb128> ;-)
[09:02] <seb128> larsu, danke
[09:05] <seb128> larsu, https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1204290 re-titled and assigned to you
[09:05] <ubot2`> Ubuntu bug 1204290 in ubiquity (Ubuntu) "ubiquity needs to be updated for the new indicators" [High,Confirmed]
[09:07] <larsu> seb128: merci
[09:07] <darkxst> seb128, or I guess we could just disable the panel? obviously qml not going to work with our images
[09:07] <seb128> darkxst, the qml stuff is not going to happen this cycle anyway ... disabling the panel doesn't seem great, it's easy enough to fix
[09:08]  * larsu wonders why we have so many implementations of the panel...
[09:08] <seb128> larsu, because we didn't have profiles in indicators to start :p
[09:09] <seb128> also because neither ubiquity nor lightdm run unity (and they are used in flavor that don't want those depends)
[09:09] <seb128> but yeah, it's suboptimal :/
[09:10] <larsu> ah right
[09:10] <larsu> well, a library or something would have been cool
[09:10] <larsu> oh well, too late to fix now :)
[09:10] <seb128> yeah :/
[09:11] <seb128> sil2100, hey, any reason the settings stack is still not published?
[09:11] <darkxst> seb128, ok
[09:11] <seb128> sil2100, we are going to miss today's image if it's not waved through soon, that would be annoying
[09:17] <seb128> hum, no sil2100 today?
[09:19] <sil2100> seb128: here
[09:19] <sil2100> seb128: hmm, ah
[09:19] <sil2100> I know what happened
[09:19] <seb128> sil2100, we have packaging changes, it's in manual publishing for sure
[09:19] <seb128> sil2100, but aren't you guys supposed to review those early so they can make it on the image of the day?
[09:19] <sil2100> seb128: dealing with that, it was green in the morning, but it seems it was blocked on something then ;/
[09:19] <Laney> where are the stack statuses?
[09:20] <seb128> Laney, https://jenkins.qa.ubuntu.com/view/cu2d/view/Head/
[09:20] <seb128> https://jenkins.qa.ubuntu.com/view/cu2d/view/Head/view/Settings/
[09:20] <Laney> cool
[09:20] <sil2100> seb128: I was reviewing and releasing what I could in the morning, seems like I did it too early
[09:20] <sil2100> seb128: as these are your changes, publishing
[09:20] <seb128> sil2100, thanks
[09:21] <sil2100> hmm, what the heck?
[09:21] <Laney> It'd be nice if all uploaders could do that
[09:22] <seb128> sil2100, issue?
[09:27] <seb128> sil2100, hello?
[09:27] <Laney> Just got the email - I guess it's working
[09:27] <sil2100> seb128: had some tool issue, but not with sttings
[09:27] <sil2100> *settings
[09:27] <seb128> ok, good
[09:27] <seb128> sil2100, thanks
[09:27] <sil2100> Settings should be published
[09:28] <seb128> yeah, what Laney said
[09:42] <sil2100> seb128: you think you can approve a cu2d-config branch for me?
[09:42] <seb128> sil2100, let me see the diff, depends if I understand what the change is about I guess ;-)
[09:42] <sil2100> https://code.launchpad.net/~sil2100/cupstream2distro-config/phone_extra_pkgs/+merge/177114 <- a missing extra pkg to install ;p
[09:46] <seb128> sil2100, seems like that list  is in alphabetic order ... should you keep it this way?
[09:47] <seb128> or not really
[09:47] <seb128> seems it was and stuff got added in different order?
[09:47] <sil2100> seb128: it doesn't have a particular order, I just added one package to the front
[09:48] <sil2100> seb128: since we're usually adding it in the order the requirement pops up ;)
[09:48] <seb128> ok
[09:48] <seb128> sil2100, approved
[09:48] <sil2100> seb128: thank you! Redeploying to unblock Phone
[09:49] <sil2100> Although we're still blocked on SDK
[09:49] <mhr3_> seb128, do you know how do i take non-black screenshots in s?
[09:50] <seb128> mhr3_, take the phone out of your pocket, press the take a picture button?
[09:50] <sil2100> ;)
[09:50] <mhr3_> i know that ubuntu edge is black, but somehow i still like colors in my screenshots... i'm just oldfashioned
[09:50] <seb128> mhr3_, screenshots work for me, not sure what's the issue for you
[09:50] <seb128> mhr3_, do you run mir or system compositor or fancy stuff?
[09:51] <mhr3_> seb128, no, all regular s
[09:51] <mhr3_> seb128, no screenshots, no videocasts... aaah
[09:51] <mhr3_> soon clipboard will stop working
[09:52] <seb128> mhr3_, does it happen in a guest session? I had some issues after docking/undocking/changing screen layouts
[09:52] <seb128> but it works atm
[09:53] <mhr3_> let me check
[09:53] <mhr3_> seb128, hmm, yea works in guest session
[09:54] <mhr3_> seb128, the indicators don't though :)
[10:03] <larsu> seb128: same issue here
[10:06] <larsu> woah, sometimes logging out of the guest session drops me back into my session, not the lock scree
[10:06] <seb128> not nice
[10:07] <seb128> unlocked session?
[10:07] <larsu> yes
[10:07] <seb128> :-(
[10:07] <larsu> but only about 1 i 3 times
[10:07] <seb128> you should open a lightdm bug
[10:07] <seb128> I saw that once yesterday but I was unsure
[10:07] <seb128> robert_ancell has been doing refactoring recently, he probably broke something
[10:11] <larsu> ah! It's a different issue
[10:11] <larsu> sometimes logging out takes a long time, so I switch to a VT to check if my computer is still reacting
[10:11] <larsu> switchig back to X drops me into my session, instead of the guest session
[10:12] <seb128> yeah; logout delays are annoying
[10:13] <seb128> it takes often minutes for me and I end up killing gnome-session
[10:13] <larsu> still, switching to a VT as guest and switching back should put you back into the guest session, right?
[10:15] <seb128> larsu, how do you "switch back"?
[10:15] <seb128> larsu, typically your session is vt7 (ctrl-alt-f7), guest is f8
[10:16] <seb128> larsu, there is no "X", there is one vt by user, starting at 7 for xorg, so first user 7, second 8, third 9
[10:16] <seb128> Laney, "I'd rather it was a property of whatever component it will come from in the end"
[10:17] <seb128> Laney, you mean I should add the property declaration to UbuntuStorageAboutPanel{} in my case?
[10:17] <Laney> Yeah, rather than having it top-level
[10:18] <larsu> seb128: ah okay. I meant switching back to vt7, which is n't right apparently. But still, shouldn't my session be locked?
[10:18] <seb128> Laney, do you think it's fine to do backend.string ? backend.string : "fallback"?
[10:18] <Laney> yes
[10:19] <seb128> larsu, it should, that's an indicator-session bug if it's not locked, the indicator is supposed to call gnome-screensaver --lock between starting the guest
[10:19] <seb128> larsu, bug charles I guess ;-)
[10:19] <seb128> between->before
[10:19] <larsu> seb128: okay, will do. Thanks for clearing this up
[10:19] <seb128> larsu, yw
[10:20] <seb128> Laney, ok, I'm going to drop the property, the only reason I used it was to avoid calling the get-er twice
[10:20] <Laney> I'd expect the QML engine to cache it
[10:20] <Laney> or at least your cpp code
[10:20] <seb128> ok, the cost in any case is low enough
[10:21] <seb128> my cpp code does the usual if empty or null; then; else; return value
[10:21] <Laney> seems fine
[10:27] <larsu> seb128: filed a bug for charles (bug #1205273)
[10:27] <ubot2`> Launchpad bug 1205273 in Session Menu "Session is not locked when switching to guest session" [Undecided,New] https://launchpad.net/bugs/1205273
[10:27] <seb128> larsu, thanks
[10:46] <darkxst> seb128, how is the ibus testing going?
[10:47] <seb128> darkxst, I'm fine upload the new version, jbicha was supposed to see with the unity guys for a failing test though, dunno if that happened
[10:48] <darkxst> ok will chat with jbicha tomorrow then.
[10:49] <seb128> ok, I will ping him later if he gets online today
[10:49] <seb128> I want that one uploaded as well
[10:49] <seb128> Laney, https://code.launchpad.net/~seb128/ubuntu-system-settings/about-real-update-date/+merge/177128 btw (dropping the extra property we discussed earlier)
[10:49]  * seb128 lunch, brb
[10:49] <Laney> seb128: I got two MPs?
[10:50] <Laney> I guess you cancelled one
[11:07] <seb128> Laney, yeah, I had an unwanted change in there, I clean and resubmitted
[11:07] <seb128> cleaned
[11:08] <Laney> ok
[11:22] <sil2100> seb128: can you do the same review for another stack? https://code.launchpad.net/~sil2100/cupstream2distro-config/fix_extra_pkgs_webapp/+merge/177135 ;) ?
[11:35] <seb128> sil2100, oh, done (sorry I did it and forgot to reply on IRC)
[11:39] <sil2100> seb128: thank you!
[11:57] <Laney> seb128: did you look into getting the last update data on desktop too?
[11:57] <seb128> Laney, no, should I?
[11:57] <seb128> that's a good point, I'm focussing on making those stuff work on the phone
[11:58] <Laney> might be nice
[11:58] <seb128> but I guess it would be nice
[11:58] <Laney> I think you can get the mtime of /var/cache/apt
[11:58] <Laney> or maybe /var/lib/apt/lists
[12:16] <desrt> morning, peeps
[12:20] <Laney> saluton desrt. feliĉa vendredo :-)
[12:20] <desrt> Laney: bona homo!  vi lernis!
[12:20] <desrt> estas bona lingvo, ĉu ne?
[12:22] <seb128> desrt, hey
[12:22] <Laney> mi ne komprenas vin
[12:22] <Laney> (thanks wikipedia :P)
[12:22] <desrt> Laney: "dankon"
[12:23] <Laney> :-)
[12:23] <desrt> i'm starting to notice that esperanto is a gateway drug
[12:23] <desrt> i spent a bit of time yesterday deciding whether i should learn shavian or toki pona next
[12:23] <desrt> seriously....
[12:23] <ogra_> do vulcan
[12:25] <desrt> afaik, nobody ever speced out a vulcan language
[12:25] <desrt> if you like pointy ears, there is elvish from lord of the rings, though
[12:25] <ogra_> http://home.comcast.net/~markg61/vlif.htm
[12:26] <desrt> oh dear lord
[12:26] <ogra_> The Vulcan Language Institute® originally began in 1980 to
[12:26] <ogra_> explore the languages of Vulcans on their homeworld and colonies.
[12:27] <ogra_> the page looks like it hasnt been updated since
[12:27] <desrt> i guarantee it's been updated more recently than 1980...
[12:27] <davmor2> desrt: I think you mis-spelt espresso there, in which case it's definitely a gateway drug man ;)
[12:27] <desrt> but ya... the look says 'not by much'
[12:27] <desrt> davmor2: i got a pot of the real stuff brewing now :)
[12:28] <desrt> davmor2: (incidentally, in my case... you're exactly correct.... i never drank coffee until a european friend convinced me to try espresso... now i drink all sorts of coffee)
[12:28] <Laney> soon you'll graduate to English Breakfast
[12:28] <Laney> the real real stuff
[12:28] <ogra_> uuh
[12:29] <desrt> english breakfast is like earl grey taken down a notch
[12:29] <desrt> aint nobody got time for that
[12:30] <Laney> I save the fancy stuff for special occasions
[12:30] <sil2100> I need to drive home now, be back pretty soon!
[12:30] <davmor2> desrt: I hope thanked them :)
[12:30] <desrt> in canada, we're fancy daily :)
[12:31] <Laney> just remembered there's some lapsang souchong downstairs
[12:31] <desrt> davmor2: actually, he was upset
[12:31] <desrt> davmor2: the slightly longer story is that he was living in canada for a couple of years and found the coffee here to be atrocious.  particularly tim hortons.
[12:31] <davmor2> Laney: Truck Stop English Breakfast is full graduation :)
[12:31] <desrt> he was german and he used some long-german-word for "dirty water left in the sink after you do the dishes" to describe this kind of coffee
[12:32] <desrt> i told him that i didn't like coffee and he said "no wonder you don't.  coffee in this country sucks.  you need to try the real thing..."
[12:32] <Laney> davmor2: yeah! The teaspoon has to stand up on its own
[12:32] <desrt> so the fact that by the end of it all, i was drinking the normal coffee..... he was a bit upset
[12:33] <davmor2> Laney: :)
[13:00] <seb128> Laney, reviewed your datetime changed, there is a tiny details on a string and bonus point if you rebase/make pot it
[13:35] <Laney> seb128: w00t, thanks
[13:41] <doomlord> how hard would it be to modify 'scale' to navigate desktops. basically i want to be able to do all window/desktop navigation with *one* hotkey+cursor keys
[13:42] <doomlord> eg activate 'scale', if you try to move offscreen, when walking the windows, it switches desktops. or make one hotkey toggle between expo/scale.. there are many ways it could be done
[13:43] <doomlord> mac osx mission control (without window-bundles) is perfect but relies on multitouch
[13:54] <tkamppeter> mlankhorst, hi
[14:39] <fginther> tedg, FYI, the pbuilderhook universe hook is available to use now
[14:44] <tedg> fginther, Great, thanks!
[15:02] <seb128> larsu, do you know why qtcreator doesn't recognise GSettings ?
[15:02] <seb128> it underlines it in red when you do GSettings {}
[15:03] <larsu> seb128: oh, no clue, I don't use qtcreator. Does it give you an error message?
[15:03] <seb128> "Unknown component. (M300)"
[15:04] <larsu> hm, how helpful
[15:04] <seb128> larsu, don't bother about it
[15:04] <seb128> I will have a look
[15:04] <seb128> I wanted to check if that's a known issue before spending time looking at it
[15:04] <larsu> seb128: thanks. I've just started with the ubiquity work... it was a crazy day
[15:05] <seb128> larsu, are there other days at Canonical? ;-)
[15:05] <larsu> seb128: ya, weekends :D
[15:05] <seb128> ;-)
[15:56] <jbicha> hmm, that notify-osd worked today and not yesterday is rather suspicious, build 39 should have been the same as build 40
[15:58] <jbicha> oh, it looks like #39 passed on i386 but not amd64; that makes a bit more sense
[15:58] <Laney> https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy-adt-notify-osd/39/ARCH=amd64,label=adt/
[15:58] <Laney> it ran against the old version
[15:59] <jbicha> it shouldn't work that way...
[16:00] <larsu> darkxst: do you know how I can test ubiquity's panel? Starting it gives me a grey window over half my screen
[16:05] <jbicha> seb128: for the ibus unity tests, see bug 1203106
[16:05] <ubot2`> Launchpad bug 1203106 in unity (Ubuntu) "Rewrite ibus test for ibus 1.5" [High,In progress] https://launchpad.net/bugs/1203106
[16:08] <seb128> jbicha, good work on fixing notify-osd
[16:09] <seb128> jbicha, seems like we need bschaefer to fix https://bugs.launchpad.net/unity/+bug/1204210 before updating ibus then?
[16:09] <ubot2`> Ubuntu bug 1204210 in unity (Ubuntu) "Refactor unity/nux to the new ibus 1.5 changes" [Medium,Triaged]
[16:09] <seb128> bregma, bschaefer: hey, is ^ correct?
[16:10] <seb128> tedg, ^ btw, you were watching the status
[16:10] <bschaefer> seb128,yup!  I have a branch, but its getting a bit hard to be consistent
[16:10] <bschaefer> seb128, well that bug can wait
[16:10] <seb128> bschaefer, is that going to create user visible problems?
[16:10] <bschaefer> seb128, mainly I need to fix up the tests, which once they are passing, ibus is working fine
[16:11] <bschaefer> seb128, nope, the only visible problems are addressed in the moving unity tests to ibu 1.5
[16:11] <seb128> bschaefer, what about the refactoring/signal? is that tests only?
[16:11] <seb128> ok, great
[16:11] <seb128> do you have any eta on that?
[16:11] <bschaefer> seb128, it needs to be refactor and there is a big error/warning I want to comment out in nux, but it doesn't create much of a problem
[16:12] <bschaefer> seb128, im hoping by today but getting someone to test it always take a bit of time
[16:12] <bschaefer> as it'll fail on one machine for no reason :(
[16:12] <seb128> ok
[16:12] <jbicha> bschaefer: do we need to land ibus in -proposed before your merges will work?
[16:13] <bschaefer> jbicha, hmm if ibus is not 1.5 with the change I make might cause them to fail on current ibus...
[16:15] <bschaefer> as I've had to change lp:autopilot to not restart ibus each time we switch engines...as ibus is always on in 1.5 (which is a bit of a big change in behaviour)
[16:20] <jbicha> ok, would Monday be good for uploading ibus 1.5? we could hold it in -proposed for a few days if necessary
[16:21] <bschaefer> yeah, that would sounds good, but right now ibus 1.5 works well with unity
[16:22] <bschaefer> jbicha, the only regression I saw is a super minor one
[16:29] <jbicha> nux will need to be rebuilt against the new ibus (soname bump) so its autopkgtest will have to pass before ibus migrates out of proposed
[16:44] <bschaefer> alright, which I should get that branch merged for nux soon as well
[16:44]  * Laney cuts qt
[16:44] <Laney> sort the model! SORT IT!
[16:47] <didrocks_busy> mpt: hey!
[16:47] <seb128> Laney, didn't you master sorting earlier in the week?
[16:47] <seb128> Laney, oh, no, that was filtering
[16:47] <didrocks_busy> mpt: so, I just somewhat build a demo for the update system panel for the phone
[16:47] <didrocks_busy> mpt: I would appreciate a real mpt design if possible (with an awesome font ;))
[16:47] <czajkowski> didrocks_busy: as you do in your spare time :)
[16:47] <didrocks_busy> I guess we'll talk about it on the IoM
[16:48] <didrocks> czajkowski: yeah, that was the part that made my buffer overflowed today :p
[16:48] <mpt> jbicha, awesome. :-) Seems we need to reconsider that rule. Perhaps show only the ~3 most-recently-used players?
[16:48] <czajkowski> didrocks: your reward is the weekend off!
[16:49] <mpt> didrocks, will you be at the sprint?
[16:49] <didrocks> czajkowski: not a full week-end as travelling!
[16:49] <didrocks> mpt: yeah, I'll take some fresh air ;)
[16:49] <mpt> didrocks, ok, let's look at it there
[16:49] <didrocks> agreed :)
[16:54] <czajkowski> didrocks: no rest for the wicked!
[16:54] <didrocks> heh
[16:54] <jbicha> mpt: I don't use the sound menu (or webapps) enough to really have an opinion on that
[17:03]  * didrocks waves good evening and good week-end!
[17:06] <jbicha> seb128: is Sunday night/Monday morning ok for ibus or do you want to discuss it more next week?
[17:07] <seb128> jbicha, feel free to upload when you feel it's ready, it's going to stay in proposed until we get an unity landing next week anyway
[17:13] <jbicha> and we'll need indicator-keyboard MIR'ed
[17:19] <jbicha> seb128: do you still need the normal mir paperwork for pre-mir stuff?
[17:20] <Laney> bah I can't make this stupid thing sort
[17:20] <Laney> I'll try again on Monday
[17:20] <Laney> it calls sort() but the view doesn't get updated
[17:24] <seb128> jbicha, define "pre-mir" stuff?
[17:25] <seb128> Laney, is that the tz list?
[17:25] <Laney> yeah
[17:25] <Laney> I made it fetch the data in a worker thread
[17:25] <Laney> so I want it to sort as they come in
[17:26] <Laney> QSortFilterProxyModel is supposed to do that but I can't get it to
[17:27] <seb128> I've no experience with that
[17:27] <seb128> I guess it works if you load/fill the model and then sort it?
[17:28] <jbicha> seb128: for the phone stuff, y'all have done quite a few pre-new and pre-mir checks, right?
[17:29] <Laney> yes that's what it does currently
[17:32] <seb128> jbicha, right, they still need Mir bugs
[17:32] <seb128> MIR rather
[17:32] <seb128> we didn't review the keyboard indicator I think
[17:32] <seb128> not for MIR for sure
[17:33] <chrisccoulson> it's nearly the weekend!
[17:33] <Laney> it already is :P
[17:33] <Laney> stop working
[17:34] <chrisccoulson> heh
[17:35] <chrisccoulson> i wish it was *that* easy to stop working
[17:35] <chrisccoulson> perhaps i should go and get some beer?
[17:35] <sarnold> beer beer beer steak steak steak
[17:36] <Laney> spoken like a desktop team member
[17:37] <chrisccoulson> lol
[17:56] <attente> mterry, hey
[17:56] <attente> i'm wondering if you have anything to comment about https://code.launchpad.net/~attente/unity-gtk-module/unset-ubuntu-menuproxy/+merge/172624
[17:57] <mterry> attente, hello
[17:57] <attente> mainly re: what the right thing to do is when UBUNTU_MENUPROXY is unset
[17:59] <mterry> looking
[18:01] <mterry> attente, uh...  do we have instances of people being bit by an unset UBUNTU_MENUPROXY?  Or docs floating in wild that suggest unsetting it?
[18:01] <mterry> attente, I've always seen "export UBUNTU_MENUPROXY=0 or UBUNTU_MENUXPROXY="
[18:02] <attente> mterry, there's nothing documenting the behaviour of an unset UBUNTU_MENUPROXY right now
[18:02] <mterry> attente, sure, nothing official.  But I didn't know if it was a common thing for people to do, like some website somewhere recommended it
[18:02] <mterry> attente, I thought we wanted UBUNTU_MENUPROXY to die?  This would make that harder
[18:03] <attente> mterry, yes, that's true
[18:03] <attente> i don't think it's a common thing, but charles seems to be getting bit by it
[18:04] <mterry> attente, charles?
[18:04] <mterry> attente, if it's just something he's doing, maybe correct him.  But if it's something he's doing because of an omgubuntu.co.uk article, maybe we should support this
[18:05] <attente> sorry, charles in #systems
[18:05] <attente> mterry, ok
[18:05] <mterry> attente, I'm just leery of putting ourselves in a position where we have to set UBUNTU_MENUPROXY to some dummy value for our stuff to work, rather than gracefully sunsetting the variable
[18:05] <mterry> attente, but ::shrug::
[18:06] <attente> mterry, ok, thanks :)
[19:10] <jbicha> xnox: are you going to guadec?
[21:38] <darkxst> larsu, you can run ubiquity-dm from a vt, then you will get a new X session just like at boot