[10:27] <willcooke> morning all
[10:41] <pitti> GunnarHj: hey! sorry for the delay, I basically spent the whole weekend travelling; I'm looking at your bug now
[10:47] <GunnarHj> pitti: No problem, Martin.
[12:20] <seb128> good morning desktopers
[12:21] <darkxst> hey seb128, pretty late morning for you?
[12:21] <seb128> hey darkxst
[12:22] <seb128> we are in Washington this week
[12:22] <seb128> it's 8am here ;-)
[12:23] <darkxst> heh there you go, sneaky timezone change ;)
[12:23] <seb128> indeed
[12:24] <pitti> hey darkxst, how are you?
[12:24] <darkxst> hey pitti, good but tired, its probably past my bed time again
[12:35] <didrocks> hey darkxst ;)
[12:35] <darkxst> hey didrocks
[12:35] <darkxst> how are you? your in washington as well?
[12:38] <didrocks> darkxst: yeah, back from Japan on Friday evening, stayed a day in France and in Washington now
[12:39] <didrocks> my body doesn't really know what timezone it is in right now TBH :)
[12:41] <darkxst> didrocks, that happens!
[12:43] <darkxst> maybe you can come visit Ubuntu GNOME Australia next ;) that will whack your timezones!
[12:43] <didrocks> darkxst: indeed, then a stop in south america and back home ;)
[12:49] <darkxst> didrocks, Aus is too large though, Ali just moved here (our non-technical stuff leader) and noskcaj is here, but its like international europe type travel to catch up
[12:49] <darkxst> so you should come to melbourne and not sydnet like ali ;)
[12:50] <didrocks> hehe ;) At least, you have multiple timezones and so have sane light hours, not like China where there is just one timezone for everybody.
[12:51] <darkxst> didrocks, well perth has its own timezone
[12:51] <darkxst> Adelaide don't count, its only half an hour off ours
[12:52] <didrocks> ah, indeed, those 30 minutes timezones…
[12:54] <darkxst> then you have brisbane who refuse to have daylight savings, so they become their own time zone in summer
[12:55] <darkxst> (upsets the cows apparently)
[12:56] <didrocks> interesting… not easy to coordinate on times when you have meetings I guess :)
[13:00] <darkxst> didrocks, organising meeting is a bit of nightmare, but thats more due the international aspect combined with when people are free from their real jobs
[13:01] <didrocks> yeah, that part is quite hard. I remembered before I entered canonical having to hurry up in the evening or leaving slightly early for some ubuntu meetings (even local ones in Paris) or going late
[13:06] <czajkowski> aloha :) just wondering if this bug is on the radar for release this week ? bug 1235567
[13:12] <seb128> happyaron, ^
[13:13] <seb128> czajkowski, hey
[13:13] <seb128> czajkowski, wasn't that fixed with https://launchpad.net/ubuntu/+source/ibus/1.5.8-2ubuntu2 ?
[13:13] <seb128> oh, maybe not
[13:39] <Laney> yo
[14:02] <czajkowski> seb128: nope :( just did updates and restart still the same
[14:16] <willcooke_> seb128, is didrocks with you?  Could you ask him to log in to IRC if he can
[14:16] <seb128> willcooke_, yeah, we are sitting together, he's on the Canonical IRC, joining here
[14:17] <willcooke_> thx seb128
[14:17] <Laney> slacker
[14:17] <willcooke_> :)
[14:17] <seb128> Laney, hey!
[14:17] <seb128> Laney, how is the nautilus upload review going?
[14:18] <Laney> 20/10 15:03:30 <Laney> Where are we with accepting stuff / britney blocks / respins?
[14:18] <seb128> thanks
[14:18] <seb128> wrong tz!
[14:19] <Laney> if not then it can be an SRU
[14:31] <seb128> czajkowski, do you use ibus? how do you trigger the bug?
[14:31] <seb128> running the binary by hand doesn't sigabrt here
[14:33] <czajkowski> seb128: happens on start up and launching chromium
[14:33] <seb128> hum, k
[14:35] <larsu> mvo: software-properties doesn't build. Do you know about that?
[14:35] <mvo> larsu: I don't - do you have a link or does it not build locally for you?
[14:35] <mvo> larsu: did you do bzr-buildpackage? or how did you build it?
[14:36] <larsu> mvo: locally with bzr bd, yes: http://paste.debian.net/127738/
[14:37] <mvo> larsu: hmmm, "(setup.py:1915): Gdk-ERROR **: error: XDG_RUNTIME_DIR not set in the environment." ? is this something in glib that changed?
[14:38] <mvo> larsu: I suspsect this comes from the python-setuptools-extra auto magic
[14:38] <desrt> mvo: more likely something in the login stuff
[14:39] <desrt> this variable should always be set
[14:39] <larsu> I guess it's not set in whatever env python builds stuff?
[14:39] <mvo> desrt: unless its build in a environment with "env -i"
[14:39] <desrt> we fall back to using ~/.cache/ by default
[14:40] <desrt> this error is not coming from gdk.....
[14:40] <desrt> there is no mention of the word RUNTIME anywhere in the source
[14:41] <desrt> (of all of gtk)
[14:41] <mvo> desrt, larsu: "env -i python setup.py build" makes it fail hard
[14:42] <desrt> mvo: can you get a backtrace on the path that causes this error to pop out?
[14:42] <desrt> between larsu and i we can't imagine a way that it could come from gtk/gdk/glib
[14:42] <larsu> mvo: where does this error come from? setup.py doesn't have the lines that the output complains about
[14:42]  * larsu doesn't know anything about python's setup stuff
[14:43] <mvo> http://paste.ubuntu.com/8602545/
[14:43] <mvo> larsu: its much deeper down it seems
[14:43] <desrt> wayland win
[14:43] <mvo> yeah
[14:43] <mvo> my thought exactly
[14:43] <desrt> i bet gdk registers a log output function with wayland
[14:43] <desrt> and verbatim-prints the message as it comes back
[14:44] <desrt> i think i heard before that wayland violates the spec a bit here
[14:44] <desrt> "If $XDG_RUNTIME_DIR is not set applications should fall back to a replacement directory with similar capabilities and print a warning message" -- says desrt in the spec
[14:46] <mvo> larsu, desrt: do you want to take care of this or should I change connect_to_socket() to not fail hard but instead use the glib fallback?
[14:47] <desrt> mvo: already on the case
[14:47] <mvo> desrt: great, thanks
[14:47] <larsu> mvo: thanks :)
[14:47] <mvo> larsu: thanks for brining it up
[14:47] <desrt> mvo: you may try setting GDK_BACKEND=x11
[14:48] <desrt> maybe this won't fail as hard?
[14:48] <desrt> (ie: avoid running the bad code)
[14:49] <mvo> desrt: right, I would really like to fix it in either python-setuptools-extra or wayland itself as it will probably affect everything that uses the setuptools-extra stuff
[14:49] <mvo> desrt: so my inclination would be to add a patch to our wayland to use the same fallback dir that glib is using in this case
[14:49] <desrt> mvo: we need to fix it in wayland or figure out a way to avoid it in gdk....
[14:49] <mvo> desrt: or could wayland simply use glib to get this directory?
[14:49] <mvo> desrt: yeah
[14:49] <desrt> could be as simple as early-aborting init of the gdk wayland backend if we detect this variable unset
[14:50] <mvo> sounds good to me as well
[14:58] <desrt> mvo: https://bugzilla.gnome.org/show_bug.cgi?id=738873
[15:05] <seb128> http://www.markshuttleworth.com/archives/1425
[15:06] <seb128> new name is out!
[15:06] <desrt> robert_ancell: bug list?
[15:07] <robert_ancell> desrt, https://bugs.launchpad.net/bugs/+bugs?field.tag=gtk-mir)
[15:07] <robert_ancell> desrt, https://bugs.launchpad.net/bugs/+bugs?field.tag=gtk-mir
[15:07]  * desrt has a couple of his own
[15:07] <robert_ancell> tag em
[15:08] <Trevinho> marga: hey, have you been able to save some time for checking the SRU bugs you reported?
[15:08] <Trevinho> marga: as SRU is slowing down...
[15:08] <larsu> seb128: cool!
[15:09] <marga> Trevinho, sorry, these past weeks have been awful.
[15:09] <marga> The new NVIDIA drivers were a disaster
[15:09] <Trevinho> marga: oh... I'm sorry for that
[15:17] <Trevinho> marga: anyway, if you can get these verifications done quickly, we can move to the next SRU with more lockscreen fixes (so you don't need that ppa anymore)
[15:35] <mvo> larsu: thanks for your softare-properites branch, is this something we want to upload into utopic at this point ? or is this SRU material? (my gut feeling is SRU)
[15:37] <mvo> larsu: is there a open bug for this already?
[18:44] <GunnarHj> robert_ancell: Hi Robert!
[18:44] <robert_ancell> GunnarHj, hello
[18:45] <GunnarHj> robert_ancell: Have you noticed that lightdm trunk and the Ubuntu branch are out of sync?
[18:45] <robert_ancell> GunnarHj, the ubuntu branch is from lp:lightdm/1.12
[18:46] <robert_ancell> which I think is in sync
[18:46] <robert_ancell> trunk will be used for vivid
[18:46] <GunnarHj> robert_ancell: Then I see. Thanks! :)
[18:47] <robert_ancell> GunnarHj, did you want to propose your change into utopic? We'll have to SRU it if so
[18:47] <GunnarHj> robert_ancell: No, I supposed it was too late anyway.
[18:48] <GunnarHj> robert_ancell: But I'll probably propose SRUs to utopic and trusty.
[18:48] <robert_ancell> ok
[18:49] <GunnarHj> robert_ancell: Btw, do you use respective trunk for SRUs also?
[18:49] <robert_ancell> GunnarHj, yes
[18:50] <GunnarHj> robert_ancell: Ok, then I know.
[18:50] <robert_ancell> GunnarHj, so just do the paperwork for the Launchpad bug, propose it for the appropriate release and do a MP to backport the changes
[18:51] <GunnarHj> robert_ancell: Right, I know what's into it.
[18:53] <GunnarHj> robert_ancell: As a starter, could you please create the tasks at bug #678421?
[18:53] <robert_ancell> GunnarHj, sure
[18:56] <robert_ancell> GunnarHj, all done
[18:56] <GunnarHj> robert_ancell: Thanks!
[20:40] <larsu> attente_: hey, are you around?
[20:40] <soren> The recent files/folders that Unity shows... Where does that come from?
[20:41] <attente_> larsu: hey
[20:41] <attente_> how's washington?
[20:41] <larsu> attente_: we miss you :)
[20:41] <Laney> lonely without you
[20:41] <attente_> :)
[20:42] <larsu> attente_: I hear I should talk to you about input methods :)
[20:42] <larsu> attente_: we've carried this patch for gtk for a long time which disables the 'viqr' im
[20:42] <larsu> apparently more vietnamese people want to use telex
[20:43] <larsu> not sure what kind of input method is selected for vi now, and where I could look
[20:43] <larsu> and also not how stuff like ibus relates to the input methods in gtk
[20:46] <attente_> oh. i don't know anything about vietnamese input. you want to drop the patch or something like that?
[20:46] <larsu> attente_: ideally, yes
[20:47] <larsu> attente_: or apply upstream if we really need it
[20:47] <larsu> but then we have an im module in gtk that isn't used by any language
[20:49] <Laney> by default
[20:49] <Laney> presumably you can turn it on
[22:01] <achiang> hi, while looking to figure out how to make compiz/unity do window shade (title bar rollup), i pressed ctrl-alt-s just to see what might happen... how do i get that window back now? ;)
[22:01] <achiang> oh, alt-tab gets it
[22:01] <achiang> alternatively, how do i actually get window shading to work?