=== tiheum is now known as tiheum_ [10:27] morning all [10:41] GunnarHj: hey! sorry for the delay, I basically spent the whole weekend travelling; I'm looking at your bug now [10:47] pitti: No problem, Martin. [12:20] good morning desktopers [12:21] hey seb128, pretty late morning for you? [12:21] hey darkxst [12:22] we are in Washington this week [12:22] it's 8am here ;-) [12:23] heh there you go, sneaky timezone change ;) [12:23] indeed [12:24] hey darkxst, how are you? [12:24] hey pitti, good but tired, its probably past my bed time again [12:35] hey darkxst ;) [12:35] hey didrocks [12:35] how are you? your in washington as well? [12:38] darkxst: yeah, back from Japan on Friday evening, stayed a day in France and in Washington now [12:39] my body doesn't really know what timezone it is in right now TBH :) [12:41] didrocks, that happens! [12:43] maybe you can come visit Ubuntu GNOME Australia next ;) that will whack your timezones! [12:43] darkxst: indeed, then a stop in south america and back home ;) [12:49] 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] so you should come to melbourne and not sydnet like ali ;) [12:50] 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] didrocks, well perth has its own timezone [12:51] Adelaide don't count, its only half an hour off ours [12:52] ah, indeed, those 30 minutes timezones… [12:54] then you have brisbane who refuse to have daylight savings, so they become their own time zone in summer [12:55] (upsets the cows apparently) [12:56] interesting… not easy to coordinate on times when you have meetings I guess :) [13:00] 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] 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] aloha :) just wondering if this bug is on the radar for release this week ? bug 1235567 [13:06] bug 1235567 in ibus (Ubuntu) "ibus-ui-gtk3 crashed with SIGABRT" [High,Triaged] https://launchpad.net/bugs/1235567 [13:12] happyaron, ^ [13:13] czajkowski, hey [13:13] czajkowski, wasn't that fixed with https://launchpad.net/ubuntu/+source/ibus/1.5.8-2ubuntu2 ? [13:13] oh, maybe not === m_conley_away is now known as m_conley [13:39] yo === Guest4574 is now known as mfisch [14:02] seb128: nope :( just did updates and restart still the same [14:16] seb128, is didrocks with you? Could you ask him to log in to IRC if he can [14:16] willcooke_, yeah, we are sitting together, he's on the Canonical IRC, joining here [14:17] thx seb128 [14:17] slacker [14:17] :) [14:17] Laney, hey! [14:17] Laney, how is the nautilus upload review going? [14:18] 20/10 15:03:30 Where are we with accepting stuff / britney blocks / respins? [14:18] thanks [14:18] wrong tz! [14:19] if not then it can be an SRU [14:31] czajkowski, do you use ibus? how do you trigger the bug? [14:31] running the binary by hand doesn't sigabrt here [14:33] seb128: happens on start up and launching chromium [14:33] hum, k [14:35] mvo: software-properties doesn't build. Do you know about that? [14:35] larsu: I don't - do you have a link or does it not build locally for you? [14:35] larsu: did you do bzr-buildpackage? or how did you build it? [14:36] mvo: locally with bzr bd, yes: http://paste.debian.net/127738/ [14:37] 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] larsu: I suspsect this comes from the python-setuptools-extra auto magic [14:38] mvo: more likely something in the login stuff [14:39] this variable should always be set [14:39] I guess it's not set in whatever env python builds stuff? [14:39] desrt: unless its build in a environment with "env -i" [14:39] we fall back to using ~/.cache/ by default [14:40] this error is not coming from gdk..... [14:40] there is no mention of the word RUNTIME anywhere in the source [14:41] (of all of gtk) [14:41] desrt, larsu: "env -i python setup.py build" makes it fail hard [14:42] mvo: can you get a backtrace on the path that causes this error to pop out? [14:42] between larsu and i we can't imagine a way that it could come from gtk/gdk/glib [14:42] 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] http://paste.ubuntu.com/8602545/ [14:43] larsu: its much deeper down it seems [14:43] wayland win [14:43] yeah [14:43] my thought exactly [14:43] i bet gdk registers a log output function with wayland [14:43] and verbatim-prints the message as it comes back [14:44] i think i heard before that wayland violates the spec a bit here [14:44] "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] 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] mvo: already on the case [14:47] desrt: great, thanks [14:47] mvo: thanks :) [14:47] larsu: thanks for brining it up [14:47] mvo: you may try setting GDK_BACKEND=x11 [14:48] maybe this won't fail as hard? [14:48] (ie: avoid running the bad code) [14:49] 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] 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] mvo: we need to fix it in wayland or figure out a way to avoid it in gdk.... [14:49] desrt: or could wayland simply use glib to get this directory? [14:49] desrt: yeah [14:49] could be as simple as early-aborting init of the gdk wayland backend if we detect this variable unset [14:50] sounds good to me as well [14:58] mvo: https://bugzilla.gnome.org/show_bug.cgi?id=738873 [14:58] Gnome bug 738873 in Backend: Wayland "wayland backend aborts entire program if XDG_RUNTIME_DIR unset" [Normal,Unconfirmed] [15:05] http://www.markshuttleworth.com/archives/1425 [15:06] new name is out! [15:06] robert_ancell: bug list? [15:07] desrt, https://bugs.launchpad.net/bugs/+bugs?field.tag=gtk-mir) [15:07] desrt, https://bugs.launchpad.net/bugs/+bugs?field.tag=gtk-mir [15:07] * desrt has a couple of his own [15:07] tag em [15:08] marga: hey, have you been able to save some time for checking the SRU bugs you reported? [15:08] marga: as SRU is slowing down... [15:08] seb128: cool! [15:09] Trevinho, sorry, these past weeks have been awful. [15:09] The new NVIDIA drivers were a disaster [15:09] marga: oh... I'm sorry for that [15:17] 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] 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] larsu: is there a open bug for this already? === m_conley is now known as m_conley_away [18:44] robert_ancell: Hi Robert! [18:44] GunnarHj, hello [18:45] robert_ancell: Have you noticed that lightdm trunk and the Ubuntu branch are out of sync? [18:45] GunnarHj, the ubuntu branch is from lp:lightdm/1.12 [18:46] which I think is in sync [18:46] trunk will be used for vivid [18:46] robert_ancell: Then I see. Thanks! :) [18:47] GunnarHj, did you want to propose your change into utopic? We'll have to SRU it if so [18:47] robert_ancell: No, I supposed it was too late anyway. [18:48] robert_ancell: But I'll probably propose SRUs to utopic and trusty. [18:48] ok [18:49] robert_ancell: Btw, do you use respective trunk for SRUs also? [18:49] GunnarHj, yes [18:50] robert_ancell: Ok, then I know. [18:50] 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] robert_ancell: Right, I know what's into it. [18:53] robert_ancell: As a starter, could you please create the tasks at bug #678421? [18:53] bug 678421 in lightdm (Ubuntu) "Error message for a faulty ~/.profile script" [Low,In progress] https://launchpad.net/bugs/678421 [18:53] GunnarHj, sure [18:56] GunnarHj, all done [18:56] robert_ancell: Thanks! [20:40] attente_: hey, are you around? [20:40] The recent files/folders that Unity shows... Where does that come from? [20:41] larsu: hey [20:41] how's washington? [20:41] attente_: we miss you :) [20:41] lonely without you [20:41] :) [20:42] attente_: I hear I should talk to you about input methods :) [20:42] attente_: we've carried this patch for gtk for a long time which disables the 'viqr' im [20:42] apparently more vietnamese people want to use telex [20:43] not sure what kind of input method is selected for vi now, and where I could look [20:43] and also not how stuff like ibus relates to the input methods in gtk [20:46] oh. i don't know anything about vietnamese input. you want to drop the patch or something like that? [20:46] attente_: ideally, yes [20:47] attente_: or apply upstream if we really need it [20:47] but then we have an im module in gtk that isn't used by any language [20:49] by default [20:49] presumably you can turn it on [22:01] 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] oh, alt-tab gets it [22:01] alternatively, how do i actually get window shading to work?