[00:00] <nagappan> TheMuso, BTW, the combo box bug have been fixed by mgorse - FYI
[02:28] <robert_ancell> RAOF, wow, alt-tab is super crashy now...  See bug 740648
[02:29] <RAOF> robert_ancell: Yeah.  I'm back in the classic session now.
[02:29] <robert_ancell> RAOF, are you using ATI or other?
[02:29] <RAOF> There seem to be at least three separate crashers in alt-tab now, none of which are in the driver code.
[02:30] <RAOF> ATI and intel.
[02:30] <robert_ancell> why is alt-tab so flaky?  It doesn't seem like that complicated a feature
[02:30] <RAOF> But the crashers are in a glib closure that's not touching the driver stack.  Apart from the one which was in free() (!).
[02:32] <RAOF> I presume that someone's hooked some handlers up to alt-tab that aren't particularly tested.
[02:33] <RAOF> Notably this seems to only occur when unity's loaded.
[07:04] <pitti> Good morning
[07:11] <chrisccoulson> good morning pitti!
[07:21] <pitti> hey chrisccoulson
[07:21] <chrisccoulson> hi pitti, how are you?
[07:22] <didrocks> good morning
[07:22] <chrisccoulson> hi didrocks
[07:22] <didrocks> hey chrisccoulson
[07:31] <pitti> bonjour didrocks
[07:31] <didrocks> Guten Morgen pitti
[07:37] <kmanzoor> hello
[07:49] <pitti> back in ~ 1 h
[07:52] <kmanzoor> ping()
[08:24] <jasoncwarner> hey didrocks, around at all?
[08:24] <didrocks> jasoncwarner: sure
[08:24] <jasoncwarner> didrocks: morning :)
[08:25] <jasoncwarner> hey...pitti and I were talking about what happens with ATI if the card/driver the person has won't run and what the default experience would be...figured we could talk through it if you didn't mind...
[08:26] <didrocks> jasoncwarner: shouldn't be the same than nvidia? (in theory)
[08:26] <didrocks> jasoncwarner: like the testing tool is failing
[08:27] <jasoncwarner> so, my question was this...what happens if someone has an a card/driver combo that doesn't work...what will happen on boot for that person?
[08:27] <didrocks> so, we fallback to the classic mode
[08:27] <didrocks> oh
[08:27] <didrocks> this is more a Xorg thing, right?
[08:27] <didrocks> I know that currently, on nvidia, it's ackward
[08:27] <didrocks> black screen
[08:27] <jasoncwarner> well, I would think that if they can't run unity, yes, we would fallback to classic mode...but I was wondering about order of oeprations as well as initial experience for them
[08:27] <didrocks> like, you need the -96 driver for your card
[08:28] <jasoncwarner> like...do we try to boot unity...compiz crashes a couple of times and then we fall back'
[08:28] <didrocks> and you forced to the current
[08:28] <jasoncwarner> ?
[08:28] <didrocks> xorg doesn't start
[08:28] <didrocks> jasoncwarner: no, that was planned, but unfortunately nobody had the time to tackle it
[08:28] <didrocks> I harrass the dx team for a month to at least, with have unity_support_test --compiz
[08:28] <didrocks> which exist
[08:29] <didrocks> but just trigger the same test than unity itself
[08:29] <didrocks> (alone)
[08:29] <jasoncwarner> so perhaps it is worth talking through a scenario, just so I can get my head wrapped around it.
[08:29] <jasoncwarner> 1. from talkign to people, I hear there is a nux test that will tell us if they can run compiz/unity...is that right?
[08:30] <didrocks> right, now, it just tell if you can run unity
[08:30] <didrocks> so it's either unity / metacity
[08:30] <jasoncwarner> ok
[08:30] <didrocks> it's either unity - compiz / metacity - gnome-panel
[08:30] <didrocks> to be exact :)
[08:31] <didrocks> jasoncwarner: TBH, first test, I think we should ensure the testing tool is working fine
[08:31] <didrocks> which isn't the case
[08:31] <jasoncwarner> so lets say someone has an ATI card and fglrx. It happens that this combo doesn't run unity. What happens at boot?
[08:31] <didrocks> and nobody has time to finish it
[08:31] <didrocks> so, the testing tool should report "can't run unity"
[08:31] <didrocks> (or crash even…)
[08:32] <didrocks> in that case gnome-session go on "let's fallback"
[08:32] <didrocks> and the guy should have metacity and gnome-panel started
[08:32] <didrocks> the thing to access that and ensure we have the exact same level
[08:32] <jasoncwarner> do they get a blank screen? a flicker? or does it appear to _try_ to load something and then fall back to GDM with a message saying "select classic desktop"?
[08:33] <didrocks> is that the unity test tools really test every requirement
[08:33] <jasoncwarner> or does it do it automaticallY?
[08:33] <didrocks> jasoncwarner: no, it's automatic
[08:33] <didrocks> ok, let's me sum up
[08:33] <didrocks> there are multiple case that I implemented :)
[08:33] <jasoncwarner> :)
[08:33] <didrocks> so stock installation:
[08:33] <didrocks> let's say the the testing tool is perfect, it can detect unity/compiz/metacity
[08:34] <didrocks> you log in
[08:34] <didrocks> the testing tool tries unity
[08:34] <didrocks> "it can't" (crash/timeout or return 1)
[08:34] <didrocks> gnome-session fallback in compiz and gnome-panel
[08:35] <didrocks> fallback to a different UI, gnoeme-session knows that and prompt a message (will copy the message later)
[08:35] <didrocks> tghen the testing tool tries compiz (<---- this is what is missing currently)
[08:35] <didrocks> "let's say it can't"
[08:35] <didrocks> so, we fallback to metacity + gnome-panel
[08:36] <didrocks> (no message here as the ui is exactly the same)
[08:36] <didrocks> let me show you the message
[08:36] <jasoncwarner> so we really have three diff combos? Unity + compiz. Compiz + gnome-panel and metacity + gnome-panel?
[08:37] <didrocks> "It seems that you do not have the hardware required to run Unity. Please choose the Ubuntu Classic Desktop at the login screen and you will be using the traditional environment.
[08:37] <didrocks> "
[08:37] <didrocks> even more :)
[08:37] <chrisccoulson> pitti - well, i sort-of have swt-gtk working locally with webkit
[08:37] <didrocks> because if you install unity-2D
[08:37] <chrisccoulson> but i had to hack the binary ;)
[08:37] <didrocks> (which isn't on the cd by default)
[08:37] <didrocks> it will try unity + compiz
[08:37] <didrocks> if it can't
[08:37] <didrocks> it will fallback to unity2D + metacity
[08:37] <chrisccoulson> i still haven't figured out why i'm seeing this problem
[08:37] <didrocks> (which is always supported)
[08:37] <didrocks> jasoncwarner: no warning message in this case as we have the same ui
[08:38] <jasoncwarner> ok...so (recapping myself :) )
[08:38] <chrisccoulson> hi jasoncwarner
[08:38] <chrisccoulson> how are you?
[08:38] <jasoncwarner> hey chrisccoulson...pretty good thanks! :0
[08:38] <chrisccoulson> pitti - if i replace the cltq instruction in http://paste.ubuntu.com/584176/ with 2 nop's, then swt-gtk magically works
[08:39] <jasoncwarner> didrocks: if they can't run unity, try compiz + gnome. If can't run compiz, enable metacity + gnome.
[08:39] <chrisccoulson> which i think proves my point. now to figure out why gcc puts it there
[08:39] <jasoncwarner> if Unity2d is installed, it becomes
[08:39] <jasoncwarner> try Unity3d. If not, try Unit2d and then we are done b/c that will always work
[08:39] <jasoncwarner> ?
[08:40] <didrocks> jasoncwarner: right, the only missing piece today is "testing compiz without unity"
[08:40] <didrocks> not on gnome-session in the test tool
[08:40] <jasoncwarner> and that is missing b/c we just haven't had time to finish/test it?
[08:41] <jasoncwarner> so if that doesn't work/get tested, can we just default to "if not unity3d, if not unity2d, use metacity + gnome"?
[08:41] <didrocks> jasoncwarner: only dx opengl guys knows what's opengl req. for unity and compiz
[08:42] <didrocks> jasoncwarner: also, that requires that we are sure that all opengl req. are tested so that we don't get then a crash believing that the card support unity which isn't the case
[08:42] <jasoncwarner> ok...so we'll need to check with dbarth to see about getting that looked at..
[08:42] <didrocks> jasoncwarner: so testing there :)
[08:42] <didrocks> jasoncwarner: yes please :-)
[08:42] <jasoncwarner> about how long would the rpocess take, start to finish
[08:43] <jasoncwarner> if someone had to fall all the way back?
[08:43] <didrocks> jasoncwarner: the test tool has a bug that it can take 4s on some machine in the live session (I had to put the timeout for 5s)
[08:43] <didrocks> jasoncwarner: on my installed machine, it takes 0.7s
[08:44] <didrocks> so, in the worst case, it's 2x0.7s
[08:44] <didrocks> in the live, it's more of course
[08:44] <jasoncwarner> about 8-10s...ok...
[08:44] <didrocks> on a live of course :)
[08:44] <jasoncwarner> yeah :)
[08:45] <didrocks> I tested on a netbook, can be quite embarrassing, 2x2s approx
[08:45] <jasoncwarner> ok...I think I have a handle on it now...
[08:45] <jasoncwarner> btw...that message you gave me earlier...where does the user see that? when they finally get into a desktop session?
[08:45] <jasoncwarner> or at gdm?
[08:46] <didrocks> jasoncwarner: right now, only in the desktop session
[08:46] <didrocks> jasoncwarner: that's a way we can explore later for OO I guess to get those sessions/fallback integated in the DM
[08:47] <jasoncwarner> I like it better that they get to a desktop rather than make them select something in gdm first time in...no worries there...thanks!
[08:48] <dbarth> didrocks, jasoncwarner: which additional gl reqs do you want us to test?
[08:49] <didrocks> dbarth: just that the --compiz option is wired up
[08:49] <didrocks> jasoncwarner: just not really possible today with gdm unfortunately
[08:50] <didrocks> dbarth: and ensuring that the tests in the unity initilization are the same than in the testing tool (not the case today)
[08:53] <pitti> didrocks, jasoncwarner: I think our concern was what happens if the testing tool says "thumbs up" (e. g. the driver claims to have the capabilities), but compiz keeps crashing due to a bug
[08:54] <pitti> chrisccoulson: *bowing to your assembly sk1llz*
[08:54] <didrocks> pitti: well, not really differently than today if compiz is crashing because it's not supported
[08:54] <jasoncwarner> pitti: yeah, good case... didrocks, what happens there?
[08:55] <didrocks> jasoncwarner: ^^
[08:55] <pitti> chrisccoulson: that's "convert long to quad"?, i. e. destroys the upper 32 bits?
[08:55] <didrocks> meaning you will see (still needs testing, respawn is under work and don't work with latest version as announced) compiz respawning/crashing
[08:55] <didrocks> but that's already the case today
[08:55] <chrisccoulson> pitti - yeah, i'm losing the upper 32 bits of the pointer, which is making it crash later on
[08:55] <pitti> chrisccoulson: do you know how that got in there, i. e. from which C operation? sounds like a typecast of some way?
[08:56] <pitti> didrocks: right; I think it's a corner case really, it just came up in discussion
[08:56] <chrisccoulson> pitti - i'm not too sure yet, as the function is pretty much identical to all the others in that object file (and it's the only one which ends up with that cltq instruction)
[08:56] <didrocks> pitti: TBH, I really want to address that in the long term. It just seems the ETOOMUCH for this cycle :)
[08:57] <pitti> didrocks: no worries
[08:58] <dbarth> didrocks: the --compiz is still not there?
[08:58] <chrisccoulson> pitti - bug 740815 :)
[08:58] <ubot2> Launchpad bug 740815 in xulrunner-2.0 "[FFe] Updates to enable us to drop xulrunner from main" [Undecided,New] https://launchpad.net/bugs/740815
[08:58] <chrisccoulson> it's actually quite a bit of work :(
[08:59] <chrisccoulson> i might need a bit of help with some of that
[08:59] <didrocks> dbarth: it's there, but it's fake. it has the same test req. than unity
[09:00] <dbarth> didrocks: ahhhhh
[09:00] <didrocks> dbarth: well, basically, it's not that bad with the test that way
[09:01] <didrocks> dbarth: it's just that the user has either compiz + unity or metacity + gnome-panel
[09:01] <pitti> chrisccoulson: quite a long list :)
[09:01] <chrisccoulson> pitti - yeah, it's longer than i thought ;)
[09:01] <pitti> chrisccoulson: that's for xulrunner-2.0, not for -1.9.2, right?
[09:01] <chrisccoulson> pitti - that's for both
[09:03] <pitti> chrisccoulson: would it be a significant win to only get it half-done for natty? I. e. less porting work when we switch to ffox 5?
[09:04] <chrisccoulson> pitti - the only issue is if we ship with it in main, we are sort-of committed to supporting it (and that would mean porting everything really, so we don't break universe)
[09:04] <chrisccoulson> hmmm, is it only gwibber which keeps gnome-python-extras in main?
[09:05] <chrisccoulson> it certainly looks like it
[09:05] <seb128> what is gwibber using from it?
[09:05] <chrisccoulson> seb128 - python-gtkspell
[09:05] <pitti> chrisccoulson: thanks for the analysis -- it is quite some work indeed, but it seems feasible; and it's nicely parallelizable
[09:05] <pitti> chrisccoulson: g-p-e is pretty much obsolete by itself
[09:05] <pitti> chrisccoulson: in oneiric, when we switch to gtk 3, we need to get rid of it anyway
[09:06] <chrisccoulson> seb128 - the issue with having gnome-python-extras in main is that it keeps xulrunner in main (with python-gtkmozembed), and the only things using it are in universe
[09:06] <chrisccoulson> which is the same situation i have with swt-gtk
[09:06] <chrisccoulson> pitti - oh, that's cool that it is going away then :)
[09:06] <seb128> if you want to get ride of it in main for natty duplicate the source
[09:06] <pitti> confirmed, no other build/binary depends in main
[09:06] <seb128> stop building -mozembed from g-p-e
[09:07] <seb128> then add a g-p-e-universe which builds only that
[09:07] <seb128> it's a small cost
[09:07] <pitti> so for gwibber we'd need to build a .gir for libgtkspell, and then use that instead of the python binding
[09:07] <chrisccoulson> yeah, i guess we could do that
[09:07] <seb128> pitti, you can mix pygtk and gi?
[09:07] <seb128> pitti, gwibber is not using gi
[09:08] <pitti> seb128: depends
[09:08] <pitti> you can't mix gi.repository.Gtk with pygtk
[09:08] <seb128> well in any case that seems a next cycle sort of thing
[09:08] <pitti> you can certainly mix e. g. gi.repository.GUdev with pygtk
[09:08] <seb128> it would require building the .gir and porting gwibber
[09:08] <pitti> gtkspell links with libgtk, so it might be an issue
[09:08] <seb128> we better duplicate the source for natty
[09:09] <rodrigo_> morning
[09:09] <seb128> hey rodrigo_
[09:09] <pitti> seb128: i. e. build a python-gtkspell source?
[09:09] <pitti> and drop g-p-e to universe?
[09:09] <seb128> pitti, what I just wrote 15 lines before
[09:10] <pitti> ah, sorry
 if you want to get ride of it in main for natty duplicate the source
 stop building -mozembed from g-p-e
[09:10] <seb128>  then add a g-p-e-universe which builds only that
[09:10] <pitti> or that way around
[09:10] <seb128> I've no strong preference which way it's done, as long as things needed in main are still built from the main source
[09:11] <pitti> note:
[09:11] <pitti> try:
[09:11] <seb128> well I would go for that rather than starting porting things to gi for this cycle
[09:11] <pitti>   import gtkspell
[09:11] <pitti> except:
[09:11] <pitti>   gtkspell = None
[09:11] <pitti> so in the simplest case we could just drop the spell check :)
[09:11] <pitti> (... dependency)
[09:12] <seb128> we could, be still it seems we have no reason
[09:12] <pitti> hmm
[09:12] <seb128> there is no issue with python-gtkspell
[09:12] <pitti>         self.spell = util.gtkspell.Spell(self, None)
[09:12] <pitti> that's the only call to gtkspell ever in gwibber
[09:12] <pitti> and self.spell is not used anywhere !?
[09:12] <pitti> dpkg -L gwibber|xargs grep spell
[09:13] <seb128> https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/451374
[09:13] <ubot2> Launchpad bug 451374 in gwibber "gwibber is not spellchecking" [Low,Fix released]
[09:13] <pitti> same for grepping the entire source
[09:13] <seb128> suggests that spell checking is working though
[09:14] <pitti> ah, it probably attaches itself to the gtk.TextView, nevermind
[09:15] <pitti> seb128: anyway, its API is tiny
[09:15] <chrisccoulson> pitti - do you think you'd be able to fix that then? :)
[09:16] <pitti> chrisccoulson: building a .gir should be easy
[09:16] <chrisccoulson> excellent, thanks :)
[09:16] <pitti> chrisccoulson: but it requires porting gwibber to gtk gi as well
[09:16] <chrisccoulson> oh, that's a bit of a pain i guess ;)
[09:16] <pitti> so it's not for natty, I'm afraid, we have to go with the source split
[09:16] <chrisccoulson> ok, that shouldn't be too much of an issue
[09:17] <pitti> chrisccoulson: it's not a separate API, it basically provides an extension of Gtk.TextView
[09:17] <chrisccoulson> is Sweetshark not around today?
[09:18] <seb128> the split is tiny cost
[09:18] <seb128> it's not like g-p-e had weekly uploads and those would need to stay in sync
[09:18] <pitti> *nod*
[09:18] <pitti> seb128: I doubt that it will get a lot more releases in the first place
[09:18] <pitti> upstream has certainly ceased to work on it
[09:18] <seb128> right, I would really got the split in natty
[09:18] <seb128> we will go gi next cycle
[09:19] <seb128> seems that ported gwibber to gi now is calling for extra work and issues
[09:19] <seb128> that "porting"
[09:19] <pitti> gwibber is quite large, porting would be quite an issue
[09:19] <pitti> and it's a lot harder to port to PyGI gtk2 than to gtk3
[09:19] <pitti> gtk3 pretty much just works now, but gtk2 is still a bit of a pain
[09:20] <pitti> just one week ago I committed http://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=6e178a69fc73b45f66fc511f7a274b8fefc2e2e7 which fixes more stuff (not even in natty yet), but we'll keep running into those
[09:21] <pitti> chrisccoulson: so, I'm happy to help out with some bits
[09:22] <pitti> just not today; I really need to take "off" today to catch up with bureaucracy, I need to do the brainstorm review for tech board and the performance review stuff
[09:23] <pitti> chrisccoulson: for gtk-vnc and friends, do you think it's cleaner to build against ffox-dev or copy headers? the latter sounds very .. unelegant
[09:24]  * pitti fixes a broken crash bug and restarts the amd64 retracer
[09:36] <chrisccoulson> pitti - we can build againt firefox-dev, but other npapi plugins (eg, totem) already include their own headers
[09:36] <chrisccoulson> npapi is cross-browser, so depending on firefox or xulrunner is quite a heavy dependency just to build a browser plugin
[09:36] <chrisccoulson> (a plugin which will work in any browser, too)
[09:36] <pitti> chrisccoulson: what happens if e. g. ffox 5 changes the API/ABI? with firefox-dev it would fail to build, with header copies it would crash; the former seems better?
[09:37] <pitti> or is npapi basically stable?
[09:37] <chrisccoulson> pitti - npapi is pretty stable (i don't think it's changed for a long time)
[09:37] <chrisccoulson> that would break things like flash
[09:37] <pitti> chrisccoulson: ok; my gut feeling is still that ffox-dev is better, if for nothing else than to avoid code copies?
[09:37] <chrisccoulson> yeah, we can do
[09:38] <chrisccoulson> as long as people are aware that we don't need to rebuild these plugins when we do a major firefox update
[09:42] <pitti> chrisccoulson: ah, you forgot to subscribe -release, so my first few comments went into the void
[09:43] <chrisccoulson> pitti - oops :/
[09:43] <pitti> (no worries)
[09:43] <chrisccoulson> sorry about that ;)
[09:45] <pitti> chrisccoulson: I'll leave the evaluation of the libreoffice tasks to Sweetshark
[09:45] <pitti> chrisccoulson: libmozjs is also a stable sub-API of xulrunner? i. e. it's by and large just a splitout?
[09:45] <chrisccoulson> pitti, cool, thanks
[09:46] <chrisccoulson> pitti - libmozjs isn't terribly stable, which is the motivation for decoupling it from the firefox release schedule (and upstream are even going to provide release tarballs for that too)
[09:46] <chrisccoulson> the official release tarballs just won't get the same frequency of updates as firefox
[09:47] <chrisccoulson> ie, we'll be able to support it for a LTS without needing to upgrade it
[09:47] <pitti> chrisccoulson: for icedtea, that sounds like it wouldn't need the firefox bits at all, and just globally disable the xpcom stuff (which happens now anyway?)
[09:47] <chrisccoulson> pitti - mozilla bug 628723 for the libmozjs stuff
[09:47] <ubot2> Mozilla bug 628723 in JavaScript Engine "Create JS 1.8.5 source release" [Normal,Assigned] http://bugzilla.mozilla.org/show_bug.cgi?id=628723
[09:48] <chrisccoulson> pitti - yeah, icedtea still needs the npapi headers though (but it looks like that's all it needs)
[09:48] <GunnarHj> pitti: Hi Martin,
[09:48] <GunnarHj> pitti: Struggling with bug 740754 and C syntax. A helping hand from you - or somebody else you suggest - would be much appreciated.
[09:48] <ubot2> Launchpad bug 740754 in gdm "Language selection for newly created user confusing" [Undecided,New] https://launchpad.net/bugs/740754
[09:49] <pitti> GunnarHj: can you please subscribe me? I'm afraid I won't get to it today, but I'm happy to review the bug tomorrow
[09:49] <pitti> (or just ping other people, lots of folks here should be proficient with C)
[09:57] <GunnarHj> pitti: Ok, just subscribed you. Maybe I ask somebody else later, as well.
[10:06] <chrisccoulson> pitti - oh, turning on -Wall in swt-gtk helps a bit ;)
[10:07] <chrisccoulson> webkitgtk.c: In function ‘Java_org_eclipse_swt_internal_webkit_WebKitGTK__1webkit_1get_1default_1session’:webkitgtk.c:775:2: warning: implicit declaration of function ‘webkit_get_default_session’
[10:07] <chrisccoulson> i should have done that  at the start ;)
[10:07] <pitti> chrisccoulson: oh, might that be the reason for the invalid conversions?
[10:07] <chrisccoulson> pitti - yeah, i guess so
[10:07] <pitti> chrisccoulson: as C implicitly assumes an int f(int) signature?
[10:08] <chrisccoulson> yeah, i think that's going to be the problem :)
[10:08] <chrisccoulson> phew
[10:08] <chrisccoulson> :)
[10:08] <pitti> chrisccoulson: wow, that seems serious enough to always warn about, not just with -Wall..
[10:08] <chrisccoulson> i almost thought i wasn't going to be able to figure that out ;)
[10:08]  * pitti ^5s chrisccoulson
[10:08]  * chrisccoulson ^5s pitti too
[10:24] <chrisccoulson> pitti - http://paste.ubuntu.com/584212/
[10:24] <chrisccoulson> fixed \o/
[10:25] <pitti> awesome!
[10:25] <pitti> chrisccoulson: this is the kind of error which really should just abort compilation entirely :(
[10:25] <pitti> I see little point of assuming an ABI for an unknown function
[10:25] <chrisccoulson> yeah, i'm surprised that it doesn't already
[10:25] <pitti> the fun of C
[10:25] <chrisccoulson> heh
[10:34] <seb128> the buildds fail the build on implicit declaration warnings
[10:34] <seb128> well they grep the build log for those and fail the build if there is some
[10:34] <chrisccoulson> seb128 - the issue here is that there wouldn't have been any in the log
[10:34] <chrisccoulson> (as it's built without -Wall)
[10:35] <seb128> right, I was just pointing it ;-)
[10:35] <chrisccoulson> well, it's not built with any warnings enabled
[10:35] <chrisccoulson> that's probably a bug ;)
[11:06] <Daviey> chrisccoulson, if it compiles, ship it!  That is my mantra :)
[11:13] <chrisccoulson> heh :)
[11:36] <GunnarHj> seb128: Hi Sebastien, do you possibly have time to help with a C syntax problem in GDM?
[11:37] <seb128> GunnarHj, yes?
[11:37] <seb128> mterry, hey
[11:37] <mterry> seb128, hi!
[11:37] <seb128> mterry, how busy are you today? ;-)
[11:37] <GunnarHj> seb128: The attachment to bug 740754 explains the problem, I think.
[11:37] <ubot2> Launchpad bug 740754 in gdm "Language selection for newly created user confusing" [Undecided,New] https://launchpad.net/bugs/740754
[11:39] <mterry> seb128, I can become busier. I was just about to dump eclipse (it's got too much to work on for natty, I believe -- will leave brain dump in bug)
[11:39] <seb128> mterry, ok, so https://launchpad.net/ubuntu/+source/indicator-datetime/+bugs
[11:40] <seb128> mterry, mtp just opened quite some bugs, especially the location dynamic list is not working great
[11:40] <seb128> mterry, like it doesn't use translations, doesn't match things correctly
[11:40] <seb128> bug #740870
[11:40] <ubot2> Launchpad bug 740870 in indicator-datetime ""Location" auto-complete menu doesn't understand "london"" [Undecided,New] https://launchpad.net/bugs/740870
[11:40] <seb128> bug #740874
[11:40] <ubot2> Launchpad bug 740874 in indicator-datetime ""Location" auto-complete menu doesn't know about San Francisco, USA" [Undecided,New] https://launchpad.net/bugs/740874
[11:40] <seb128> bug #740884
[11:40] <ubot2> Launchpad bug 740884 in indicator-datetime ""Location" auto-complete menu often offers duplicate suggestions" [Undecided,New] https://launchpad.net/bugs/740884
[11:40] <seb128> mterry, etc
[11:40] <mterry> seb128, yup, those look like my bugs  :)(
[11:40] <seb128> mterry, karl seems to be busy enough with what is assigned to him
[11:41] <kmanzoor> hello
[11:41] <seb128> mterry, could you maybe try to tackle some of those today?
[11:41] <seb128> mterry, just pick anything in the list you feel like doing
[11:41] <seb128> mterry, the idea is to improve a bit the indicator ;-)
[11:41] <mterry> seb128, yup  :)  I'm on it
[11:41] <seb128> mterry, thanks
[11:41] <seb128> dbarth, ^
[11:44] <kmanzoor> today upgraded from 7.10 to 8.4 - it was a great experience
[11:44] <mterry> seb128, what is this 'sniffles' tag?  :)
[11:44] <seb128> mterry, it's a design thing I think
[11:44] <seb128> you can try asking mpt
[11:45] <seb128> but seems like what design guys spot when they do a review
[11:46] <dbarth> seb128, mterry: cool, thanks; karl is also doing the triaging of the bug list at the same time; he's taking the string changes as a priority
[11:50] <kmanzoor> is Hardy Heron still supported ? i checked this on wikipedia. On kubuntu page it said it is not spported but on the ubuntu page it is mentioned that it is still supported.  I want to install the restricted extra - meaning i want to have the adobe flash. Should i upgrade all the way to 9.10 or i can keep on running Hardy Heron ?
[11:58] <mterry> kmanzoor, it is still supported on Desktop until April
[11:58] <mterry> kmanzoor, server for longer
[11:59] <kmanzoor> i am using desktop
[11:59] <rodrigo_> hmm, just upgraded and I get 'C++ compiler cannot create executables' error on configure
[11:59] <mterry> kmanzoor, but if you were to upgrade, I wouldn't recommend 9.10, you can jump right to 10.04, the new LTS
[11:59] <rodrigo_> any idea if g++ is broken or something?
[12:00] <mterry> kmanzoor, but this isn't the best channel anyway.  for support questions like that, try #ubuntu
[12:00] <rodrigo_> 'Unrecognized option -qversion'
[12:01] <kmanzoor> ok i joined #ubuntu
[12:05] <rodrigo_> pitti, just got your mail about the nautilus folder view thing, so just to say that yes, I'm willing to do it :-)
[12:05] <rodrigo_> pitti, I'll read it in more detail in a bit
[12:09] <dbarth> seb128: pitti: i've updated the FFE request at https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/730740
[12:09] <ubot2> Launchpad bug 730740 in gtk+2.0 "Provide support for dynamically loading the new overlay scrollbar feature" [Wishlist,Confirmed]
[12:12] <chrisccoulson> pitti - ok, i think i've got all swt-gtk packages ready
[12:12] <chrisccoulson> Daviey, are you able to test euca, or is it broken to the point of not being testable?
[12:13] <Daviey> chrisccoulson, I think it might be possible actually... The breakage we have now is starting an instance, but i don't think swt-gtk is related to that!
[12:13] <Daviey> It's the web ui... so yes... should be able to test that
[12:13] <chrisccoulson> cool, thanks
[12:14] <Daviey> chrisccoulson, will keep you posted, thanks.
[12:17] <seb128> re
[12:17] <seb128> rodrigo_, no clue about the gcc error
[12:18] <cyphermox> good morning!
[12:19] <seb128> hey cyphermox
[12:19] <seb128> how are you?
[12:19] <cyphermox> seb128, doing alright
[12:20] <seb128> cyphermox, did you get any upstream comment about your gnome-media work? I noticed the merge request but I'm not sure to understand enough about it to have an opinion
[12:20] <cyphermox> seb128, no I didn't yet. I should go poke somebody on gimpnet I guess
[12:21] <seb128> did you file it on gnome-media or gnome-control-center?
[12:21] <seb128> did that code move to g-c-c this cycle?
[12:21] <cyphermox> I think so yes
[12:22] <seb128> did you file it on g-c-c?
[12:22] <cyphermox> seb128, the best way to understand what is going on is to start mumble without an external mic, then plug one in and try to switch the input device from gnome-volume-control, not mumble
[12:22] <seb128> it's likely that nobody is reading gnome-media bugs, they do read g-c-c ones though
[12:22] <cyphermox> no, you're right, I filed it against gnome-media, 2.32 or whatever
[12:22] <seb128> try moving it to g-c-c
[12:22] <cyphermox> seb128, yeah
[12:23] <cyphermox> I'm getting a 500 now though ;)
[12:23] <seb128> or ping hadess on IRC
[12:23] <seb128> right, seems bgo is down since yesterday evening
[12:23] <cyphermox> ah
[12:23] <GunnarHj> seb128: Will be away for an hour or so. Pls submit possible questions to the bug in the meantime.
[12:23] <seb128> ok, I noticed the mumble issue
[12:23] <seb128> GunnarHj, sorry I had it open in a tab but I had to run for lunch
[12:23] <seb128> GunnarHj, I will
[12:24] <GunnarHj> seb128: No problem, see you later.
[12:24] <seb128> GunnarHj, the issue is obvious in your example
[12:25] <seb128> GunnarHj, *language is a pointer pointing to nothing
[12:25] <seb128> GunnarHj, you need to allocate some memory and point to it
[12:27] <GunnarHj> seb128: Well, nothing about C is obvious to me. ;-)  How could it work in the separate script then?
[12:28] <seb128> GunnarHj, the small example segfaults there
[12:28] <seb128> you might be lucky and get the pointer hitting a memory address you can use
[12:29] <seb128> but that's only luck
[12:36] <seb128> chrisccoulson, bug #739497 is not a g-c-c issue right?
[12:36] <ubot2> Launchpad bug 739497 in gnome-control-center "firefox 4.0 is not default by default" [Low,Invalid] https://launchpad.net/bugs/739497
[12:37] <cyphermox> seb128, I pinged hadess, I'll see when I get a response
[12:37] <seb128> ok
[12:37] <seb128> GunnarHj, hey again, did you see my comments before timeouting?
[12:37] <pitti> rodrigo_: ah, great, thanks!
[12:37] <GunnarHj> seb128: No, I didn't.
[12:37] <chrisccoulson> seb128 - the issue is that firefox is expecting to be default in gio and gconf, and we aren't setting /desktop/gnome/url-handlers/http to firefox by default anymore
[12:37] <chrisccoulson> although
[12:38] <chrisccoulson> that check is meant to be disabled in firefox anyway
[12:38] <seb128>  GunnarHj, the small example segfaults there
[12:38] <seb128>  you might be lucky and get the pointer hitting a memory address you can use
[12:38] <seb128>  but that's only luck
[12:38] <chrisccoulson> not sure why it's enabled
[12:38] <seb128> chrisccoulson, why do we stopped setting the key?
[12:38] <GunnarHj> seb128: Ok, I'll try your idea and come back. Thanks!
[12:38] <seb128> chrisccoulson, I though we said we would still set both for compatibility reasons
[12:38] <seb128> that's what the capplet does
[12:39] <chrisccoulson> seb128 - actually, i'm wondering whether we ever did. perhaps we only see it now because the default browser check is enabled
[12:39] <seb128> we did for sure
[12:39] <seb128> there was a .gconf-defaults changing the default
[12:39] <seb128> oh that's in gnome-vfs and got dropped
[12:40] <chrisccoulson> yeah, it's now sensible-browser by default
[12:40] <chrisccoulson> so, we should probably re-add that then
[12:40] <seb128> right
[12:40] <seb128> if you want to do it please do it
[12:40] <seb128> since you own gnome-vfs now ;-)
[12:40] <chrisccoulson> sure, no problem
[12:41] <chrisccoulson> i'll disable the check in firefox too
[12:41] <chrisccoulson> it used to always be turned off
[12:44] <pitti> chrisccoulson: great work! now hoping that it'll actually work with euca :)
[12:50] <pitti> smspillaz: thanks for fixing the edge snapping and the shadow spillover!
[12:50] <pitti> smspillaz: --geoemtry placement works as well again
[12:50] <pitti> I now lost all my compiz pet bugs!
[12:50] <smspillaz> pitti: :)
[12:50] <pitti> (except for the crashes :) )
[12:51] <smspillaz> pitti: the crashes?
[12:51] <smspillaz> pitti: there's one more which will drive you insane if you aren't careful
[12:51] <pitti> got bug 740757 twice this morning after login
[12:51] <ubot2> Launchpad bug 740757 in nux "compiz crashed with SIGSEGV in __libc_free()" [Medium,New] https://launchpad.net/bugs/740757
[12:51] <smspillaz> oh, that's a nux bug
[12:51] <pitti> smspillaz: we already have a workaround for the gvfs related one
[12:51] <pitti> i. e. crash when plugging in a usb drive
[12:51] <pitti> that was the other one which wreaked havoc
[12:51] <smspillaz> pitti: open gedit, open a find window, close it, notice invisible window
[12:51] <pitti> (but that was in unity)
[12:52] <pitti> smspillaz: ah, indeed -- I haven't stumbled over that one at all yet (can reproduce, though)
[12:52] <pitti> smspillaz: it doesn't happen with vi in the terminal :-P
[12:58] <pitti> I need to run out for about two hours; friend of mine defends his diploma thesis :)
[12:58] <Amaranth> pitti: actually --geometry and those other bugs are probably only fixed because we're using gtk-window-decorator again
[12:59] <didrocks> Amaranth: no, we are not with laltest upload
[13:00] <didrocks> pitti: ensure you have the latest version with the unity-window-decorator
[13:00] <Amaranth> didrocks: Oh, you already uploaded another one?
[13:00] <didrocks> Amaranth: 5 hours ago approx :)
[13:01] <didrocks> smspillaz was quick to fix the issue
[13:03] <Amaranth> didrocks: Ah well unless he fixed more then the bugs pitti talked about should still apply with the latest upload then since they are unity-window-decorator bugs
[13:03] <didrocks> Amaranth: there are some fixes in it
[13:03] <Amaranth> I reopened the bug report about it but I couldn't reopen the unity task so I dunno if it was on your radar
[13:04] <didrocks> Amaranth: hum? the snap taking the shadow?
[13:04] <Amaranth> yeah
[13:04] <Amaranth> That would be the reason --geometry doesn't work right too
[13:13] <smspillaz> Amaranth: .... --geometry works fine here
[13:33]  * bcurtiswx waves to room
[13:33] <bcurtiswx> kenvandine, sorry I couldn't get tp-glib out quick enough :-\
[13:44] <dobey> mvo: hey. the thing that PackageKit and sessioninstaller don't handle is adding a new repository, right?
[13:45] <rodrigo_> a couple of branches up for review/merge/upload: https://code.launchpad.net/~rodrigo-moya/ubuntu/natty/evolution/fix-717971/+merge/54526 and https://code.launchpad.net/~rodrigo-moya/ubuntu/natty/nautilus/fix-662194/+merge/54337 so, can someone have a look please?
[13:46] <mvo> dobey: yeah, that needs the normal aptdaemon system interface
[13:46] <dobey> ok
[13:46]  * rodrigo_ lunch
[13:49] <seb128> rodrigo_, will do
[13:49] <seb128> rodrigo_, did you get cosimoc to review the nautilus one? did you fix the default value thing we discussed yesterday?
[14:00] <chrisccoulson> is there any equivalent of DEB_SRCDIR from cdbs in dh7?
[14:00] <cdbs> chrisccoulson: check out man dh, maybe you can modify it in the call to dh $@ ?
[14:01] <ricotz> seb128, hi, i had a look at the new mutter source
[14:01] <chrisccoulson> cdbs - man dh doesn't really say anything
[14:01] <ricotz> seb128, is it possible to enable arm builds in the gnome3 ppa?
[14:01] <cdbs> chrisccoulson: dh $@ --builddirectory=DIR is what you need?
[14:01] <seb128> ricotz, not that I know about
[14:02] <seb128> ricotz, the virtual ppa don't do armel I think
[14:02] <cdbs> chrisccoulson: ah, got it, its --sourcedirectory=
[14:02] <chrisccoulson> cdbs, i'm not sure. i can try, but if that is the equivalent of DEB_BUILDDIR, then it won't work
[14:02] <chrisccoulson> oh, thanks
[14:02] <cdbs> chrisccoulson: dh $@ --sourcedirectory=DIR
[14:02] <kenvandine> bcurtiswx, sorry i took it over.. :)
[14:02] <kenvandine> bcurtiswx, but i needed it
[14:02] <ricotz> seb128, there are some "ppa like" which have this support
[14:02] <ricotz> seb128, ok
[14:03] <seb128> ricotz, non virtual ppas like the security team ones right
[14:03] <seb128> but those have higher security constrains
[14:03] <ricotz> seb128, yes
[14:03] <seb128> they don't set such ppas for random team builds
[14:03] <bcurtiswx> kenvandine, im guessing you didn't notice my bug report on it, sicne IIRC the bug report's still open
[14:03] <ricotz> ok wasnt aware there are more types of ppas
[14:04] <kenvandine> bcurtiswx, oh... no i didn't
[14:04] <chrisccoulson> cdbs - thanks, that looks like what i want
[14:05] <chrisccoulson> there's a reason i still use cdbs in firefox, this stuff is just so much easier there :)
[14:11] <seb128> kenvandine, can you review https://code.launchpad.net/~marcelstimberg/indicator-me/translator-comments/+merge/52346 ? it's pending for some weeks
[14:12] <kenvandine> seb128, yeah, it's on my todo list
[14:12] <seb128> kenvandine, bug #739319 might be worth putting on your natty list, it got 3 duplicates, seems for some reason the indicator fails to get the username sometimes, could be a race on session start
[14:12] <ubot2> Launchpad bug 739319 in indicator-me "unity-panel-service crashed with SIGABRT in g_simple_async_result_complete()" [Medium,New] https://launchpad.net/bugs/739319
[14:12] <seb128> kenvandine, one easy way would be to not g_error but to return when that happens
[14:13] <kenvandine> seb128, ok
[14:18] <seb128> kenvandine, thanks
[14:20] <GunnarHj> seb128: Tried your suggestion, but ...  I posted the latest code as a comment on bug 740754.
[14:20] <ubot2> Launchpad bug 740754 in gdm "Language selection for newly created user confusing" [Undecided,New] https://launchpad.net/bugs/740754
[14:22] <seb128> kenvandine, no hurry for the crash but I will assign it to you
[14:22] <kenvandine> thx
[14:22] <seb128> GunnarHj, no clue what is wrong, does it still crash?
[14:22] <seb128> mterry, not sure if you work on that but the location completion is suboptimal
[14:23] <mterry> seb128, k
[14:23] <seb128> mterry, like typing "Lon" lists "Kūh-e Sālon" first
[14:23] <mterry> seb128, you saying you didn't want that one?  :)
[14:23] <seb128> or "Pari" lists "Gioúpari"
[14:23] <seb128> mterry, ;-)
[14:23] <seb128> it should perhaps matches thing that start with what you type first?
[14:24] <mterry> seb128, probably
[14:24] <mterry> I believe ubiquity has same issue
[14:24] <mterry> except it will give london first for that particular query because of a different quirk
[14:24] <seb128> mterry, is that your reply to all issues in that code? ;-)
[14:24] <seb128> let's just blame it all on ev :p
[14:24] <mterry> seb128, yup!   spec said "do it like ubiquity"
[14:26] <GunnarHj> seb128: It depends on how you define "crash", but it freezes, and the field for typing the pw does not appear.
[14:27] <seb128> GunnarHj, sorry today is a bit busy with the beta freeze being tomorrow
[14:27] <seb128> GunnarHj, I don't really have time for that now but ping me again tomorrow if you didn't figure it out by then
[14:28] <GunnarHj> seb128: No problem; I'll get back to either you or Martin tomorrow, then.
[14:30] <seb128> nessita, hey
[14:30] <nessita> seb128: hi there!
[14:30] <nessita> seb128: how is it going?
[14:30] <seb128> nessita, I noticed that a new sso tarball got rolled yesterday, let me know if you need sponsoring
[14:30] <seb128> nessita, I'm fine thanks, what about you?
[14:31] <nessita> pretty, pretty good :-)
[14:31] <nessita> seb128: and yes, you're a great magician, I need a sponsorship: https://code.launchpad.net/~nataliabidart/ubuntu/natty/ubuntu-sso-client/ubuntu-sso-client-1.1.12/+merge/54531
[14:31] <seb128> nessita, on it ;-)
[14:31] <nessita> :-)
[14:31] <seb128> nessita, well my magic trick is http://people.canonical.com/~platform/desktop/versions.html
[14:31] <nessita> I know, I have to apply for upload right
[14:31] <seb128> nessita, but don't tell anybody :p
[14:32]  * nessita bookmarks
[14:33] <rickspencer3> seb128, not sure who to mention this to, but I did a dist-upgrade yesterday ... yesterday everything was fine, but this morning I had to manual start Unity
[14:34] <rickspencer3> kenvandine, it seems that Gwibber did not start for me when I started up today
[14:34] <seb128> rickspencer3, did you get a .crash?
[14:34]  * rickspencer3 looks
[14:35]  * kenvandine waits
[14:35] <seb128> rickspencer3, did you switch to french locale? it might be a strike day
[14:35] <seb128> i.e things refusing to start
[14:35] <seb128> ;-)
[14:36] <rickspencer3> seb128, no, but I did log in as a different user last night, and in that user I use the classic desktop
[14:38] <kenvandine> rickspencer3, not of that should matter
[14:38] <kenvandine> ~/.cache/gwibber/gwibber.log
[14:38] <seb128> rickspencer3, can you copy your .xsession-errors online?
[14:38] <seb128> rickspencer3, if you are still in the session where you had the issues
[14:38] <cdbs> didrocks: Hi, looks like gimp doesn't have any internal mechanism to start the new image window from the command line. So should I make a dynamic quicklist?
[14:39] <rickspencer3> seb128, kenvandine bear with me, I'll get a chance to look at that soon
[14:39] <kenvandine> rickspencer3, no worries
[14:39] <kenvandine> :)
[14:40] <didrocks> cdbs: dynamic quicklists aren't wired in unity, so not for gimp
[14:40] <rickspencer3> seb128, there is a crash dump for compiz
[14:40] <rickspencer3> where do .xsession-errors go?
[14:41] <cdbs> didrocks: but ultimately they will be, right?
[14:41] <didrocks> cdbs: not for natty though
[14:41] <cdbs> didrocks: wha? Dynamic quicklists won't work in Natty ? :(
[14:41] <seb128> rickspencer3, it's a file in your user dir
[14:41] <seb128> rickspencer3, please ubuntu-bug -c .crash
[14:41] <didrocks> cdbs: patch welcomed :)
[14:42] <didrocks> if the crash is the one from this morning
[14:42] <didrocks> rickspencer3: ensure the crash is the one from this morning, first, ls -l /var/crash/*compiz*crash
[14:42] <cdbs> didrocks: That's a nice Canonical way to get contributors to work on stuff :) That's the 3rd time someone has said that to me
[14:42] <rickspencer3> didrocks, yeah, I checked that
[14:42] <didrocks> cdbs: heh, just jump in then :)
[14:43] <rickspencer3> dang it:
[14:43] <cdbs> didrocks: okay, then
[14:43] <rickspencer3> Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers.
[14:43] <rickspencer3> ?
[14:43] <rickspencer3> lol
[14:43] <cdbs> rickspencer3: I get that frequently
[14:43] <rickspencer3> not my morning
[14:43] <cdbs> looks like apport hogs up a lot of memory?
[14:43]  * cdbs needs more ram btw
[14:43] <rickspencer3> seb128, shall I manually upload?
[14:43] <rickspencer3> I could ubuntu-bug compiz and then attach the crash file
[14:44] <kenvandine> weird, just tested a guest session and got no window decorations at all... but window management still worked fine
[14:45] <rickspencer3> kenvandine, that makes sense if just the decorator crashed
[14:45] <seb128> kenvandine, that's a known bug
[14:46] <kenvandine> usually i only get that when compiz crashes... then nothing works
[14:46] <kenvandine> seb128, ok
[14:46] <seb128> https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/730495
[14:46] <ubot2> Launchpad bug 730495 in compiz "unity-window-decorator doesn't start on secondary X session" [High,Confirmed]
[14:46] <seb128> kenvandine, ^
[14:46] <kenvandine> ah
[14:46] <kenvandine> seb128, man you are always so fast with the bug urls :)
[14:46] <cdbs> seb128 is seb128
[14:47]  * Amaranth tries to think of why that would happen
[14:48] <Amaranth> The detection of other decorators and such uses properties on the X root window so that should be per-session
[14:49] <seb128> kenvandine, well, the awesome bar in firefox works great ;-)
[14:49]  * kenvandine must not use it right :)
[14:49] <seb128> but yeah, you need so spend some time going through bugs and to had those open before to get them listed
[14:49] <bcurtiswx> you'll all have to let me know if ffx4 > google, seems to still have java rendering problem
[14:49] <seb128> then you only need to remember keywords from the title ;-)
[14:49] <bcurtiswx> no no flash i meant
[14:50] <seb128> nessita, uploaded
[14:51] <nessita> seb128: awesome, thanks
[14:51] <nessita> tedg: hey there, would you have some minutes to follow up in the messaging menu icon conversation from yesterday?
[14:51] <tedg> nessita, Sure.
[14:52] <rickspencer3> seb128, bug #741030
[14:52] <ubot2> Launchpad bug 741030 in compiz "compiz crash on startup" [Undecided,New] https://launchpad.net/bugs/741030
[14:52] <nessita> tedg: so, you were saying we would need to patch something to have different icons, right?
[14:52] <dobey> yes
[14:53] <tedg> nessita, Yeah, we need to patch indicator-messages so that it would auto-add the "-panel" name on the icon string so that they'd get replaced by the theme if available.
[14:53] <tedg> nessita, I think that makes sense to do overall.
[14:53] <nessita> tedg: is that doable or is that our of the question at this point in the cycle?
[14:53] <nessita> out*
[14:53] <didrocks> rickspencer3: btw, there is a new compiz available since your update
[14:53] <rickspencer3> natch ;)
[14:54] <tedg> nessita, It's probably doable, but we'd need some freeze requests.  Should be a small patch though.
[14:55] <tedg> nessita, It's probably something we should convince the desktop team is important enough to grant those requests before spending time on.  (you know how they are ;) )
[14:55] <nessita> :-)
[14:55] <nessita> I know they are awesome! :-D
[14:55]  * nessita prepares the field
[14:56] <rickspencer3> didrocks, I thought I saw a new Unity in  my change mail yesterday
[14:57] <rickspencer3> is that *the* Unity for B1, or are you still planning a releast late tonight?
[14:57] <tedg> seb128, kenvandine, thoughts on adding "-panel" to application icons in the messaging menu and enabling fallback support there? ^
[14:57] <seb128> rickspencer3, release this night
[14:57] <didrocks> rickspencer3: no, it's not. We still plan for a late release
[14:57] <didrocks> rickspencer3: the new compiz is breaking the ABI of all plugins
[14:58] <didrocks> rickspencer3: so, I had to reupload all plugins to rebuild with the new compiz
[14:58] <kenvandine> tedg, no strong opinions
[14:58] <seb128> tedg, not before beta1
[14:58] <ogra_> .oO( and doesnt build on arm )
[14:58] <rickspencer3> so is the Unity tonight just a rebuild, or are there new features/bugs as well?
[14:58] <seb128> tedg, let's merge was is pending today and deal with crashers
[14:58] <rickspencer3> didrocks ^
[14:58] <nessita> seb128: I would need your input on the following: you mentioned a while ago that the control panel should have a monochromatic icon in the messaging menu. Turns out that, after some input from tedg, we realized we can't set specific icons for the messaging menu (the same, colorful icon defined in the .desktop file is used for the main menu, the launcher and the messaging entry). tedg says we could do something about it but that 
[14:58] <nessita> ahead with that?
[14:58] <seb128> tedg, we can do a ffe for that next week
[14:58] <didrocks> rickspencer3: juste a rebuild
[14:58] <didrocks> just*
[14:58] <seb128> nessita, ^ what I just replied to ted
[14:59] <rickspencer3> didrocks, so, theoretically, not too many bugs to fix in Unity before B1?
[14:59] <tedg> seb128, Yeah, I wasn't thinking for B1, just that we'd need the FFe and whether you'd be open to it.  The patch should be small.
[14:59] <didrocks> ogra_: the doesn't build on arm is because a kde dep is broken on arm
[14:59] <nessita> seb128: awesome. tedg, shall I file a bug?
[14:59] <seb128> rickspencer3, no, the one you got was a rebuild, they plan on rolling a new version at end of the day and didrocks will upload early tomorrow
[14:59] <tedg> nessita, Yes, please.
[14:59] <didrocks> ogra_: I relaunched it this morning, still broken
[14:59] <seb128> nessita, yes
[14:59] <ogra_> didrocks, yeah, i saw that :/
[14:59] <didrocks> rickspencer3: well, the list is still opens
[14:59] <rickspencer3> I see
[14:59] <rickspencer3> didrocks, yeah, so new features and bugs
[14:59] <ogra_> (not the rebuild attempt but the kdelibs stuff)
[14:59] <didrocks> seb128: I wasn't clear enough on my explanation? :)
[15:00] <didrocks> rickspencer3: right
[15:00] <rickspencer3> didrocks, if there are too many bugs, can we roll back to what we got last night rather than trying to cram in lots of bug fixes at the last minute?
[15:00] <rickspencer3> (for the beta, I mean)
[15:00] <seb128> didrocks, <rickspencer3> so is the Unity tonight just a rebuild, or are there new features/bugs as well? -> <didrocks> rickspencer3: juste a rebuild
[15:00] <seb128> didrocks, no, that wasn't clear
[15:01] <didrocks> rickspencer3: we can reupload the current version, yeah, that will be a shame so
[15:01] <seb128> didrocks, tonight's is a new tarball, not a rebuild right?
[15:01] <didrocks> seb128: yeah
[15:01] <rickspencer3> didrocks, seb128 thanks
[15:01] <didrocks> rickspencer3: both nux and unity
[15:01] <rickspencer3> and didrocks, right, I don't *want* to roll back, obviously
[15:01] <rickspencer3> :)
[15:03] <ogra_> didrocks, seems the majority of kde stuff vanished from http://qa.ubuntuwire.org/ftbfs/, should work now
[15:04] <didrocks> ogra_: ok
[15:04] <ogra_> and someone apparently has given it back already
[15:12] <cdbs> chrisccoulson: there?
[15:14] <cdbs> chrisccoulson: With your next FF upload could you kindly incorporate debdiff attached to bug #741046 ? thanks!
[15:14] <ubot2> Launchpad bug 741046 in firefox "Please add unity quicklist item for 'new tab'" [Wishlist,Triaged] https://launchpad.net/bugs/741046
[15:14] <pitti> Amaranth, didrocks: ah, that's right, I don't have unity-window-decorator, but compiz-decorator and gtk-window-decorator running now
[15:14] <chrisccoulson> it's not translated ;)
[15:14] <didrocks> pitti: only in -0ubuntu1
[15:14] <cdbs> chrisccoulson: That's a roadblock? :(
[15:15] <pitti> didrocks: running dist-upgrade again then
[15:15] <didrocks> pitti: I uploaded this morning -0ubuntu2 as I got a fix for u-w-d crashes. So I resetted u-w-d by default
[15:15] <chrisccoulson> cdbs - at this stage, yes. and i still need to think about what to do with launcher integration
[15:15] <pitti> didrocks: (too bad, it works quite well with g-w-d :) )
[15:15] <didrocks> heh :)
[15:15] <chrisccoulson> also, you shouldn't use "firefox" in the desktop.in file. that will break in the nightlies
[15:15] <rodrigo_> seb128, yes, pinged cosimoc about the patch, he was going to review it, but bgo is down today, and yes, I fixed the default value thing and the removal of the description in the patch
[15:16] <cdbs> chrisccoulson: I used it on the final one
[15:16] <cdbs> chrisccoulson: I mean the -final.desktop.in
[15:16] <pitti> didrocks: right, new compiz coming in now
[15:16] <chrisccoulson> cdbs, yeah. it should be in all the desktop.in files really, and it shouldn't use "firefox" anywhere in those ;)
[15:17] <cdbs> chrisccoulson: well, it has to
[15:17] <seb128> rodrigo_, ok thanks
[15:17] <chrisccoulson> cdbs, it doesn't. we run all of those files through a preprocessor to substitute the correct values in
[15:17] <chrisccoulson> cdbs, have a look at the Exec= line ;)
[15:17] <cdbs> chrisccoulson: yes, got it
[15:18] <cdbs> @APPNAME@
[15:18] <cdbs> chrisccoulson: so, after this change you'll accept the debdiff? The translations issue?
[15:19] <chrisccoulson> cdbs, the translations issue really needs to be resolved. we don't get many contributors for the desktop file (it's not translated in launchpad)
[15:19] <chrisccoulson> so, if we upload an untranslated version now, it will almost certainly remain untranslated for final
[15:19] <chrisccoulson> (and in any case, i don't want to be doing dozens of firefox uploads to add new translations every couple of days)
[15:20] <pitti> rodrigo_: thanks for fixing the evo bug! I can sponsor this
[15:20] <rodrigo_> pitti, ok, thanks
[15:20] <cdbs> chrisccoulson: okay, fine. I am withdrawing the debdiff. Feel free to close the bug
[15:20] <cdbs> didrocks: ^
[15:20] <pitti> rodrigo_: meh, bugzilla.gnome.org is down; I guess you already closed the upstream bug?
[15:20] <chrisccoulson> cdbs, don't do that ;)
[15:20] <rodrigo_> pitti, no, it's been down all day
[15:20] <chrisccoulson> the idea is fine in principle
[15:20] <seb128> pitti, can you sponsor the nautilus one as well while you are at it?
[15:20] <cdbs> chrisccoulson: why?
[15:21] <seb128> pitti, I'm dealing with some fixes still I want to land before freeze
[15:21] <chrisccoulson> dpm - how do we get people adding translations to the firefox desktop file?
[15:21] <pitti> seb128: sure, it's in the sponsoring queue? I'll look
[15:21] <nessita> tedg: which project shall I file the bug in? (I'm with some delay due to concurrent conversations :-))
[15:21] <cdbs> chrisccoulson: okay, then. I'll make the exec change
[15:21] <chrisccoulson> thanks
[15:21] <seb128> pitti, they are on top of http://people.canonical.com/~platform/desktop/versions.html
[15:21] <dpm> chrisccoulson, https://wiki.ubuntu.com/Translations/Wanted/FirefoxDesktop
[15:22] <cdbs> chrisccoulson: And, the change has to go to all the desktop.ins?
[15:22] <chrisccoulson> dpm - thanks
[15:22] <dpm> np :)
[15:22] <chrisccoulson> cdbs - yes please. also see dpm's link there
[15:23] <tedg> nessita, indicator-messages
[15:23] <pitti> seb128: I only see a nautilus SRU on http://reports.qa.ubuntu.com/reports/sponsoring/
[15:23] <seb128> pitti, cf 9 lines before
[15:23] <seb128> ;-)
[15:23] <pitti> seb128: I looked at versions.html, but it doesn't have branches or bugs or anything!?
[15:23] <rickspencer3> seb128, pitti, whoever knows GNOME programming - totally unrelated questions ... is there an API that I can use to modify the contents of the recently used files file, or should I parse and edit the XML?
[15:24] <seb128> pitti, click on the bzr icons
[15:24]  * rickspencer3 wants to create a book marks editor 
[15:24] <pitti> ooh, there
[15:24] <pitti> sorry
[15:24] <seb128> pitti, np ;-)
[15:24] <seb128> pitti, the issue is that those are against team vcs so they are not showing up on  the sponsoring queue
[15:24] <seb128> it's another side issue of not using udd
[15:24] <pitti> seb128: shall I do the others as well?
[15:25] <seb128> pitti, if you want that would be great, thanks!
[15:25] <pitti> seb128: ah, eog adds multitouch, I'll skip that (FFE, and previously discussed to only go in PPA)
[15:26] <seb128> pitti, ok, they raised it yesterday, they had a dual binary build which added a new variant for universe
[15:26] <pitti> or that
[15:26] <seb128> pitti, but we agreed on either getting a ffe and patching the main binary or use a ppa for natty
[15:26] <seb128> pitti, no, not "or that"
[15:27] <seb128> pitti, they need the build-depends in main anyway, so they need it promoted
[15:27] <pitti> ah, ok; so PPA then for natty, as before
[15:27] <seb128> pitti, if they do we can as well upload was in the merge request today
[15:27] <seb128> otherwise it's the ppa
[15:29] <seb128> rickspencer3, http://library.gnome.org/devel/gtk/unstable/GtkRecentManager.html
[15:29] <rickspencer3> thanks seb128!
[15:30] <seb128> rickspencer3, yw
[15:32] <didrocks> pitti: FYI, DBO just added some info on bug #737601
[15:32] <ubot2> Launchpad bug 737601 in unity "Restore MT support in Unity" [Medium,In progress] https://launchpad.net/bugs/737601
[15:32] <pitti> didrocks: tahnks
[15:32] <didrocks> yw
[15:32] <rodrigo_> pitti, ugh, seems I've removed the mail about the nautilus thing, can you please forward it?
[15:33] <pitti> rodrigo_: bounced
[15:33] <rodrigo_> ok thanks
[15:34] <cdbs> chrisccoulson: Okay, posted question about it on ubuntu-translations, attached improved debdiff
[15:34] <chrisccoulson> cdbs, excellent, thanks
[15:34]  * cdbs g2g
[15:35] <nessita> tedg: https://bugs.launchpad.net/indicator-messages/+bug/741068
[15:35] <ubot2> Launchpad bug 741068 in indicator-messages "Please support the use of a specific icon" [Undecided,New]
[15:38] <rodrigo_> pitti, ah, I didn't remove it, just evolution couldn't find it, but anyway, thanks for forwarding :)
[15:38] <pitti> rodrigo_: no problem :)
[15:48] <pitti> seb128: ok, all branches on versions.html handled, except eog
[15:48] <seb128> pitti, thanks a lot
[15:48] <pitti> np
[15:56] <seb128> ok, it's mterry's fault, I knew it! ;-)
[15:56] <mterry> seb128, wait what?  :)
[15:57] <seb128> mterry, gnome-panel clock's broken
[15:57] <seb128> mterry, seems because your backports in g-s-d changed the polkit interface
[15:57] <mterry> seb128, hah
[15:57] <seb128> mterry, I'm fixing it ;-)
[15:57] <mterry> whoops
[15:57] <mterry> seb128, thanks
[15:57] <seb128> np
[16:14] <chrisccoulson> ha, my daughter has just discovered that felt-tipped pins make pretty patterns on the sofa
[16:15] <pitti> seb128: looking at the xulrunner transition bug, I can claim some bits (like gtk-vnc); did you want to work on the g-p-e split?
[16:15] <pitti> or want me to look at that as well?
[16:16] <seb128> pitti, I can do but probably not today
[16:17] <chrisccoulson> pitti - hopefully i will have a libmozjs source package later
[16:17] <chrisccoulson> will i need to do a MIR for that?
[16:17] <pitti> seb128, chrisccoulson: if you want I can tackle this right now
[16:17] <chrisccoulson> pitti - sure, feel free to take any items from there :)
[16:17] <pitti> I'll move the performance review stuff to Friday, in the freeze
[16:18] <pitti> chrisccoulson: ok, starting with that then
[16:18] <chrisccoulson> excellent, thanks :)
[16:18] <m4n1sh> pitti: check your mail. Mailed you my initial reply
[16:18] <seb128> pitti, well if you want feel free
[16:19] <seb128> pitti, i'm still fixing gnome-panel issues I want to land before the freeze
[16:19] <pitti> seb128: yes, that's great
[16:19] <pitti> seb128: just coordinating :)
[16:19] <pitti> I've got spare cycles now, so checking what to work on now
[16:20] <pitti> m4n1sh: wow that was fast :) looking forward to the discussion
[16:20] <m4n1sh> yeah, looks possible except we need to patch gtk probably
[16:21] <m4n1sh> not sure
[16:21] <m4n1sh> gtk patching should be avoidable
[16:26] <pitti> chrisccoulson: MIR> it's not new code, is it? just taking out the js bits from xulrunner and dropping the rest?
[16:28] <chrisccoulson> pitti - yeah, it's just basically the js/src folder from firefox
[16:29] <pitti> chrisccoulson: so, no MIR necessary -- in fact, it's a De-MIR :)
[16:32] <Sweetshark> pitti: I just uploaded a version 3.3.2-1ubuntu1~ppa1 to my personal ppa. debian has not yet released it (although it is already tagged in SCM), and it needs one package update (which I circumvented by using LOs own version for now).
[16:32] <kenvandine> seb128, can you sync tp-logger?
[16:32] <seb128> kenvandine, yes
[16:32] <kenvandine> thx
[16:32] <kenvandine> was just uploaded this morning
[16:32] <pitti> Sweetshark: (on phone, bbl)
[16:34] <seb128> kenvandine, where?
[16:34] <kenvandine> probably experimental
[16:34] <seb128> kenvandine, there is nothing in http://packages.qa.debian.org/t/telepathy-logger.html and http://incoming.debian.org/
[16:36] <seb128> kenvandine, it seems it's not uploaded yet
[16:36] <kenvandine> seb128, ok, i'll check with sjoerd
[16:36] <kenvandine> he told me it was
[16:36] <seb128> kenvandine, pochu just tagged it in the debian git half an hour ago
[16:36] <seb128> kenvandine, so I guess it will be soon
[16:36] <kenvandine> ok
[16:36] <seb128> kenvandine, I will sync it when it hits the upload queue
[16:37] <didrocks> pitti: thanks for the FFe
[16:37] <kenvandine> maybe he jumped the gun a little :)
[16:39] <pochu> should be in by the next dinstall, yes
[16:39] <kenvandine> thx pochu
[16:39] <pochu> np
[16:44] <pitti> Sweetshark: do you want me to sponsor that then?
[16:51] <Sweetshark> pitti: lets see: is this critical for the ui freeze tommorrow? if not, maybe its better to wait for debian as it wont be long.
[16:52] <seb128> mterry, ok, stupid question but do you see why the code in http://paste.ubuntu.com/584370/ stopped working?
[16:53] <seb128> I don't get a org.gnome.SettingsDaemon.DateTimeMechanism on the system bus in d-feet
[16:53] <pitti> Sweetshark: does it change UI?
[16:53] <pitti> Sweetshark: tomorrow is also (by and large) beta freeze
[16:53] <mterry> seb128, we might be emitting an error now?
[16:53] <mterry> seb128, print out the contents of error->message
[16:53] <mterry> seb128, unless you're saying it doesn't even get that far?
[16:53] <mterry> seb128, it appears on demand and then goes away
[16:54] <mterry> seb128, so you won't see it on d-feet unless you talked to it recently
[16:54] <seb128> oh ok
[16:54] <seb128> mterry, let me try that
[16:54] <Sweetshark> pitti: it reenables the launchpad integration (which is adding 3 menupoints).
[16:56] <seb128> mterry, thanks, now it's obvious :p
[16:56] <seb128> Error: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.gnome.settingsdaemon.datetimemechanism.settime is not registered
[16:56] <seb128> so it's indeed the patch in gsd
[16:56] <mterry> not registered?
[16:56] <pitti> Sweetshark: as it builds for about 3 days on armel, it's "by tomorrow morning" or "not for beta"
[16:56] <seb128> mterry, settime got dropped
[16:57] <seb128> mterry, it's org.gnome.settingsdaemon.datetimemechanism.configure now
[16:57] <mterry> seb128, oh right, all integrated into one
[16:57] <seb128> mterry, I just need to figure what refers to settime still
[16:57] <seb128> mterry, seems a gsd bug
[16:58] <seb128> mterry, I'm back on track thanks
[16:58] <mterry> np
[16:58] <Sweetshark> pitti: in that case, I would say: lets see if it builds in the ppa on x86/amd64 and sponsor it then. Sounds good?
[17:18] <Riddell> hello ubuntu desktop people, please pick a preferred way to get appmenu-qt support  bug 733309
[17:18] <ubot2> Launchpad bug 733309 in qt4-x11 "Qt applications are not able to use the AppMenu." [Undecided,New] https://launchpad.net/bugs/733309
[17:27] <pitti> Sweetshark: deal :)
[17:28] <seb128> Riddell, hum, I vote for having qt to recommends it
[17:29] <seb128> Riddell, it's the only pratical thing to do if we don't want to pull libqt in the default ubuntu installation
[17:29] <seb128> since appmenu-qt depends on qt
[17:29] <Riddell> ok, I can add that in the next upload
[17:29] <seb128> thanks
[17:29] <Riddell> seb128: should gtk recommend appmenu-gtk then?
[17:30] <seb128> I'm fine doing that
[17:30] <seb128> hum, though we might check with xubuntu and others
[17:31] <seb128> Riddell, what happen to qt applications if appmenu-qt is installed but there is no appmenu renderer
[17:31] <seb128> like if you use xfce
[17:33] <Riddell> seb128: then the normal inline menu is used
[17:39] <seb128> mterry, http://paste.ubuntu.com/584398/ is the fix to my issue for the record
[17:40] <mterry> seb128, isn't there already a patch 34_* that does that?
[17:40] <seb128> mterry, if there was I wouldn't have been tracking the bug on natty :p
[17:40] <cdbs> chrisccoulson: I've modified the debdiff on the bug according to a capitalization suggestion from dpm . Just notifying you, in case you've already downloaded it
[17:41] <seb128> mterry, the 34- fixed check_polkit_for_action ()
[17:42] <chrisccoulson> cdbs, thanks
[17:42] <chrisccoulson> maaan, i hate debian/copyright
[17:42] <seb128> mterry, that's another similar issue, anyway patch fixes it confirmed, I will upload and upstream that
[17:42] <cdbs> chrisccoulson: should I give dpm the go-ahead for translations? or should I do that after the upload?
[17:42] <chrisccoulson> cdbs, you can do that now
[17:43] <seb128> rodrigo_, hey
[17:43] <rodrigo_> hi seb128
[17:43] <seb128> rodrigo_, is gnome code frozen yet?
[17:43] <rodrigo_> seb128, yes, I think 2.91.92 was code freeze
[17:43] <rodrigo_> let me check
[17:44] <seb128> ok
[17:44] <mterry> seb128, awesome, thanks
[17:44] <seb128> rodrigo_, I've just fixed gnome-panel clock applet can_set_time now working, it was due to g-s-d, see http://paste.ubuntu.com/584398/
[17:45] <seb128> now->not
[17:45] <seb128> rodrigo_, I will bugzilla the fix for now then
[17:45] <rodrigo_> seb128, well, that can go in I guess
[17:45] <rodrigo_> seb128, let me know the bug # when you file it please
[17:50] <seb128> rodrigo_, https://bugzilla.gnome.org/show_bug.cgi?id=645603
[17:50] <ubot2> Gnome bug 645603 in plugins "incorrect polkit action for can_set checks" [Normal,New]
[17:50] <rodrigo_> seb128, ok
[17:51] <pitti> python-gtkspell_2.25.3-7ubuntu2_amd64.deb
[17:51] <pitti> there
[17:51] <pitti> seb128: ^ so we'll also get rid of the libgnomeui-dev, libbonoboui2-dev, and other stuff :)
[17:52] <seb128> pitti, great
[18:01] <kamusin> folks, do you know if there is an issue with some formats of current documentation.. seems like yelp is doing something wrong with some packages (for example banshee - nautilus if you press F1)
[18:16] <nessita> seb128: is your crystal ball telling you something about me needing a new sponsorship? :-)
[18:16] <nessita> https://code.launchpad.net/~nataliabidart/ubuntu/natty/ubuntuone-control-panel/ubuntuone-control-panel-0.9.3/+merge/54576
[18:16] <seb128> nessita, ok, I can see that, yes!
[18:16] <nessita> and that would cover all UI changes to the control panel
[18:17] <pitti> seb128: bah, gnome-python-extras doesn't even build any more :/
[18:17] <seb128> pitti, did some apis changed?
[18:17] <pitti> /home/martin/ubuntu/build-area/gnome-python-extras-2.25.3/./gtkmozembed/gtkmozembedmodule.cpp:10:32: fatal error: gtkmozembed_glue.cpp: Datei oder Verzeichnis nicht gefunden
[18:17] <pitti> apparently
[18:18] <pitti> or that isn't getting built any more
[18:19] <seb128> why am I not surprised?
[18:19] <seb128> it probably needs to be updated for a recent xulrunner
[18:19] <pitti> seb128: it already has a patch from chrisccoulson for porting to xulrunner-2.0
[18:21] <pitti> http://launchpadlibrarian.net/62959641/buildlog_ubuntu-natty-amd64.gnome-python-extras_2.25.3-7ubuntu1_BUILDING.txt.gz says that this was in /usr/include/xulrunner-2.0b10/gtkmozembed_glue.cpp
[18:22] <pitti> chrisccoulson: ^ does that ring a bell? seems to have disappeared
[18:22] <pitti> chrisccoulson: is that a packaging bug, or is it actually gone?
[18:22] <chrisccoulson> pitti - heh, that will probably be a packaging bug
[18:23] <chrisccoulson> pitti - where is that included from?
[18:24] <pitti> chrisccoulson: gnome-python-extras python-gtkmozembed module
[18:24] <pitti> chrisccoulson: I just made a comment to the bug
[18:24] <chrisccoulson> thanks
[18:25] <pitti> chrisccoulson: it's not that urgent, I can demote g-p-e without dropping the binary as well, but it would be cleaner
[18:25] <pitti> chrisccoulson: at least the splitout is uploaded now
[18:26] <chrisccoulson> thanks, that's awesome :)
[18:28] <pitti> chrisccoulson: I'll take gtk-vnc as well if you want, but not today any more -- time for Taekwondo
[18:29] <chrisccoulson> pitti - thanks for your help :)
[18:29] <chrisccoulson> i've nearly got a libmozjs package ready \o/
[18:30] <pitti> cool
[18:30] <pitti> chrisccoulson: will you discuss the libreoffice bit with Sweetshark?
[18:30] <chrisccoulson> pitti - yeah, sure
[18:35] <pitti> bah, gtk-vnc package is busted -- robert forgot bzr merge-upstream
[18:36] <jcastro> pitti: we have a nice community contrubution here that we forgot about but ken assures me that it's low risk: https://bugs.launchpad.net/indicator-me/+bug/741163
[18:36] <ubot2> Launchpad bug 741163 in indicator-me "Add support for Emesene2 chat client" [Undecided,New]
[18:36] <jcastro> an FFe for this would be highly appreciated!
[18:36] <seb128> kenvandine, mterry, tedg: I'm not sure I like this ubuntu-geoip server thing
[18:36] <seb128> seems like half the issue are due to it
[18:37] <seb128> pitti, he did screw gvfs the same way this week
[18:37] <seb128> pitti, the new version diff was reverted by the source v3 patch
[18:37] <mterry> seb128, you mean geonames (different than geoip)
[18:38] <seb128> ups, yes
[18:38] <seb128> mterry, I especially don't like the "don't have any translated name"
[18:38] <seb128> it's just screwed
[18:38] <mterry> seb128, yeah.  :(  I'm surprised that so many issues exist, since we introduced this in 10.10's installer
[18:38] <mterry> Thought they'd have been shaken out
[18:39] <seb128> I'm wondering if we should switch to use libgweather
[18:39] <seb128> but it seems late in the cycle to do that
[18:39] <kenvandine> seb128, so the issue is the result the server gives us?
[18:40] <seb128> kenvandine, yes
[18:40] <kenvandine> i thought we postponed using geonames?
[18:41] <seb128> kenvandine, https://bugs.launchpad.net/ubuntu-geonames
[18:41] <seb128> kenvandine, those are the issues mterry reassigned to geonames today
[18:42] <seb128> bug #729022 is the one which makes me unsure if we should switch
[18:42] <ubot2> Launchpad bug 729022 in indicator-datetime "Locations in the settings are not localized" [Medium,Confirmed] https://launchpad.net/bugs/729022
[18:42] <seb128> not sure who is maintaining geonames and how well
[18:42] <kenvandine> oh
[18:42] <seb128> but seems a design flaw there
[18:42] <kenvandine> for populating the selector
[18:42] <kenvandine> i see
[18:43] <mterry> seb128, I believe the data exists, it's just a matter of grabbing it from our server.  evan dandrea wrote the code we use, and IS pushes it live
[18:44] <seb128> mterry, ok, so it's not relying on launchpad that's something ;-)
[18:44] <seb128> not that I don't trust the launchpad guys to get work done, but if you wait on them you might wait a bit
[18:44] <mterry> seb128, I talked to ev about it earlier today, we're not sure how easy it would be to fix the translation thing
[18:44] <kenvandine> hehe
[18:44] <mterry> seb128, should we assign to him?
[18:44] <seb128> mterry, I'm pinging him on #ubuntu-devel, not sure if he's still around
[18:44] <seb128> mterry, yes please
[18:48] <pitti> chrisccoulson: oh, gtk-vnc was easier than I thought, uploading :)
[18:48] <chrisccoulson> pitti - cool, thanks
[18:49] <pitti> oh, packagekit is already taken
[18:49] <pitti> ok, gotta run now -- see you tomorrow!
[18:55]  * bryceh waves bye to pitti
[19:04] <Gortu> Hello everybody!
[19:06] <Gortu> I have a question. I'm one of the authors of libpolo, an educational graphics library (http://code.google.com/p/libpolo/). I've read the packaging guide, but it is still unclear how to become a MOTU. Could somebody please help me out?
[19:36] <tedg> In Launchpad lib how do you turn a link into an Entry?
[19:36] <tedg> bryceh, ? ^
[19:37] <tedg> Gortu, Well, you need to do some packaging.  Probably best to talk to the folks in #ubuntu-motu as they can help you get started.
[19:37] <Gortu> thnx a lot! :D
[19:39] <seb128> Gortu, hi, try #ubuntu-motu
[19:40] <seb128> ups, that was mentioned before
[19:50] <ari-tczew> Gortu: you don't need to be MOTU to create a Debian package for libpolo.
[19:51] <Gortu> tedg and ari-tczew: I got that! Thanks. I'm working on the package, and then I'll see what comes next!
[19:52] <bryceh> tedg, not sure I follow the question
[19:52] <ari-tczew> Gortu: for packaging question you can look for help on #ubuntu-motu or #ubuntu-packaging
[19:52] <bryceh> tedg, do you mean like if you have a link to a bug report, how to get the corresponding launchpadlib Bug object?
[19:52] <tedg> bryceh, I've got an Entry that has an attribute "milestone_link" but I really want an milestone object.
[19:53] <bryceh> ahh
[19:53] <bryceh> tedg, just ignore the "_link" bit, and call my_entry.milestone
[19:53] <bryceh> it'll automagically transmorgraphy it into a milestone object
[19:53] <tedg> bryceh, Oh, okay.
[19:54] <bryceh> tedg, don't forget to check for None
[19:55] <tedg> bryceh, Well this is a release.  It can't not have a milestone or there's a DB error :-)
[19:56] <bryceh> fair enough; I've seen enough LP weirdness that I'd put the check in anyway, but it's your script ;-)
[19:57] <tedg> bryceh, Actually I'm going to propose this to be merged into ubuntu-dev-tools...
[19:58]  * tedg notes to not put bryceh on the review
[20:00] <bryceh> heh
[22:23] <seb128> robert_ancell, hi
[22:26] <pitti> hey robert_ancell
[22:26] <pitti> seb128: ah, want to talk about --merge-upstream? :-)
[22:26] <seb128> pitti, I had that on my list, I wanted to send an email the other day about gvfs and I forgot
[22:27] <seb128> I also wanted to point bug #729150
[22:27] <ubot2> Launchpad bug 729150 in libappindicator "libappindication crashes in gtkstatusicon code on update" [High,Fix released] https://launchpad.net/bugs/729150
[22:27] <seb128> there is a patch from ted that needs sponsoring, would be nice to get in beta because some indicator behaviour relies on it
[22:27] <seb128> (though it's fallback only)
[22:27]  * pitti unscrews gtk-vnc
[22:27] <didrocks> merge-upstream? mu for lazy people ;)
[22:27] <seb128> it's just that it's getting late and I will probably not build and test it before going to bed
[22:28] <seb128> didrocks, you are the only lazy around it seems ;-)
[22:28] <robert_ancell> seb128, pitti, hey
[22:28] <pitti> robert_ancell: how are you?
[22:28] <pitti> long time no see!
[22:28] <robert_ancell> pitti, indeed!
[22:29] <robert_ancell> must be getting near release, 'cause you guys are awake at crazy times
[22:29] <pitti> hehe
[22:29] <seb128> pitti, I did uncommit and push --overwrite for gvfs
[22:29] <pitti> seb128: ack
[22:29] <seb128> robert_ancell, ^ if you have a gvfs checkout do pull --overwrite
[22:29] <seb128> robert_ancell, you screwed it by not using merge-upstream, the new version diff got reverted in the packaging by the source v3
[22:30] <pitti> robert_ancell: same for gtk-vnc; I fixed the branch now
[22:30] <seb128> robert_ancell, and yeah, having a few sources in different format is confusing
[22:30] <robert_ancell> seb128, you always have to do a pull --overwrite?
[22:31] <seb128> robert_ancell, not always, but for gvfs merge-upstream wouldn't run on your broken commit so I did uncommit, revert and did it properly
[22:31] <seb128> robert_ancell, but it means the official vcs diverted from your version
[22:31] <seb128> if you just pull it will get confused
[22:31] <pitti> robert_ancell: same for gtk-vnc, please pull --overwrite, as I had to do the same
[22:31] <robert_ancell> well, I'm certainly confused
[22:32] <seb128> robert_ancell, you handled it like it was debian dir only in the vcs
[22:32] <pitti> robert_ancell: about --merge-upstream or --overwrite?
[22:32] <seb128> where it's full source
[22:32] <robert_ancell> I'm a little worried how flaky UDD seems to be
[22:32] <seb128> robert_ancell, in full source checkouts you need to bzr merge-upstream tar.gz
[22:32] <robert_ancell> I always just (intend to) do a merge-upstream
[22:32] <pitti> it's actually not flaky, just different
[22:32] <seb128> robert_ancell, bzr merge-upstream ../gvfs... --version ...
[22:33] <seb128> robert_ancell, it will commit the code update in your checkout
[22:33] <seb128> robert_ancell, your commit had only a debian dir update
[22:33] <pitti> (not actually commit yet, just update)
[22:33] <robert_ancell> pitti, it seems very easy to confuse it - I tried to do a merge-upstream on libnotify4, and it complained there was no upstream-*oldversion* tag.  But the log showed there was
[22:33] <pitti> after that you do dch, and debcommit the thing
[22:33] <seb128> robert_ancell, well, not all checkout are using merge-upstream format
[22:33] <pitti> robert_ancell: I think it relates that to the pristine-tar branch
[22:33] <seb128> like autoimports are not
[22:34] <pitti> seb128: they do
[22:34] <seb128> ok, I ran into broken cases as well then
[22:34] <pitti> all lp:ubuntu/pkgname branches have pristine-tar, full source, and thus --merge-upstream
[22:34] <pitti> seb128: yeah, sometimes
[22:34] <seb128> we had cases were we had to tag it manually to start or to convert them to work
[22:35] <didrocks> seb128: sorry, was testing compiz respawn in a guest session
[22:35] <seb128> but those were old dx vcs I think; so maybe not autoimports
[22:35] <didrocks> seb128: we'll rediscuss the "lazy" term once you will use bzr merge-upstream 10 times a week :p
[22:36] <seb128> ;-)
[22:36] <seb128> robert_ancell, can you handle sponsoring of bug #729150 today?
[22:36] <ubot2> Launchpad bug 729150 in libappindicator "libappindication crashes in gtkstatusicon code on update" [High,Fix released] https://launchpad.net/bugs/729150
[22:37] <seb128> robert_ancell, it's a patch from ted, should be ok, it's just that it's late now for me to start a gtk build
[22:37] <robert_ancell> seb128, sure
[22:37] <seb128> robert_ancell, thanks
[22:37] <seb128> bah, I forgot about bug #703230
[22:38] <ubot2> Launchpad bug 703230 in pango1.0 ""rm: cannot remove `/usr/share/doc/libpango1.0-0': Is a directory" when updating to 1.28.3-4" [Unknown,Fix released] https://launchpad.net/bugs/703230
[22:38] <seb128> ^ if someone wants to pick that one today feel free
[22:38] <seb128> I will do it tomorrow otherwise
[22:38] <seb128> it should be a matter to add a if [ -d ... ] rmdir in the preinst
[22:39] <chrisccoulson> pitti - https://launchpad.net/~chrisccoulson/+archive/xulrunner-universe-transition/+buildjob/2340284 :)
[22:39] <pitti> chrisccoulson: yay you!
[22:39] <chrisccoulson> pitti - xulrunner-1.9.2 should drop from main now ;)
[22:39] <seb128> robert_ancell, btw, shotwell build-depends on libgnomevfs2-dev, wth? it's 2011! ;-)
[22:39] <robert_ancell> seb128, yeah, one of the plugins
[22:39] <pitti> chrisccoulson: sorry, gtk-vnc upload was rejected, your latest upload didn't make it into bzr; all fixed up now
[22:39] <chrisccoulson> robert_ancell, the above link might be interesting to you too (for the board)
[22:40] <pitti> chrisccoulson: still shepherding the python-gtkspell build on armel
[22:40] <chrisccoulson> pitti - oops, sorry about that
[22:40] <pitti> it failed on powerpc because apparently gtk isn't installable on ppc
[22:40] <chrisccoulson> ah
[22:40] <seb128> robert_ancell, you won bug #740274 as well btw, it's low priority though
[22:40] <ubot2> Launchpad bug 740274 in shotwell "on Natty, resize grip overlaps zoom icon" [Undecided,New] https://launchpad.net/bugs/740274
[22:40] <pitti> bah, armel as well
[22:40] <pitti> gtk fail
[22:41] <chrisccoulson> these resize grips are a bit of a pain aren't they? i keep seeing windows where they overlap other UI elements
[22:41] <pitti> speaking of overlapping, the unity launcher doesn't go away any more :/
[22:41] <pitti> I keep running into that
[22:42] <seb128> kenvandine, btw did you see my xchat-gnome ping yesterday?
[22:42] <kenvandine> no
[22:43] <seb128> kenvandine, http://git.gnome.org/browse/xchat-gnome/commit/?id=be95811135169b16d108448117c71dbe7386f254
[22:43] <seb128> kenvandine, you could be interested to backport that one
[22:43] <seb128> kenvandine, in case you get bored and want to try that, it could be nice
[22:43] <kenvandine> ah
[22:43] <kenvandine> cool
[22:44] <kenvandine> well i did just mention i was done for the day
[22:44] <kenvandine> so i am wide open to do it now :)
[22:45] <seb128> RAOF, howdy
[22:46] <pitti> ah, atk didn't build on armel/powerpc yet, that might explain my trouble
[22:47] <seb128> pitti, do you have any opinion bug #725434
[22:47] <ubot2> Launchpad bug 725434 in nvidia-graphics-drivers "something (libcairo2) causes a significant 'across the board' memory use increase with -nvidia loaded" [Medium,Confirmed] https://launchpad.net/bugs/725434
[22:47] <RAOF> seb128: 'ello.
[22:47] <seb128> pitti, see comment #15 for a summary
[22:47] <seb128> RAOF, hey, how are you?
[22:47] <kenvandine> sigh... compiz keeps crashing everytime i try to download that patch
[22:47] <TheMuso> pitti: afaik there is not that hard a dependency on atk from gtk...
[22:47] <seb128> RAOF, ^ I want to chat about that bug
[22:48] <kenvandine> the nice thing is compiz restarts now :)
[22:48] <seb128> kenvandine, does it? it doesn't work for didrocks or me
[22:48] <kenvandine> it is for me right now
[22:48] <RAOF> seb128: I'm ok.  A bit tired, really.  Time for coffee :)
[22:48] <didrocks> seb128: it did some time for now, but really not reliably
[22:48] <pitti> TheMuso: arch all/any desync -- see http://launchpadlibrarian.net/67121987/buildlog_ubuntu-natty-armel.python-gtkspell_2.25.3-7ubuntu2_FAILEDTOBUILD.txt.gz
[22:48] <kenvandine> 3 times i've tried to copy the url so i can paste it into wget
[22:48] <didrocks> seb128: on some sigsegv
[22:48] <kenvandine> and it goes boom
[22:48] <pitti> TheMuso: it makes libgtk2.0-dev uninstallable
[22:48] <seb128> didrocks, ok
[22:48] <TheMuso> pitti: ah of course.
[22:48] <RAOF> seb128: What do you want to know about that bug?
[22:48] <didrocks> the new patch I just uploaded works way better now
[22:49] <pitti> TheMuso: it has a hard dependency on the arch:all -data package
[22:49] <TheMuso> right
[22:49] <pitti> (I guess it wouldn't need to)
[22:49] <seb128> RAOF, I guess 1- would be "do you think that's something that need to be adressed for natty"
[22:49] <pitti> I rescored the builds now
[22:49] <TheMuso> Worth looking into.
[22:49] <seb128> RAOF, and if the reply is "yes" the second would be "what do you recommend doing"
[22:50] <seb128> pitti, ^ interested by your opinion as well
[22:50] <pitti> seb128: I read the summary, but I'm afraid I know too little about this stuff to have an opinion?
[22:51] <seb128> pitti, well it's basically due to cairo being built with the unstable gl backend for wayland
[22:51] <seb128> pitti, so one option would be to roll that out and keep wayland in a ppa for natty
[22:51] <seb128> pitti, though bryceh put efforts to get it in universe and didn't seem happy about the though
[22:51] <TheMuso> pitti: Actually, libatk1.0-data is interesting, as it only contains locale data, which of course is stripped out to be included in language packs.
[22:52] <TheMuso> So at the end of all that, libatk1.0-data only contains doc files.
[22:52] <pitti> TheMuso: so we probably could drop the dependency altogether
[22:53]  * TheMuso ponders whether its worth dropping libatk1.0-data, and carrying that change in ubuntu.
[22:53] <RAOF> Woah!  IRC lag!
[22:53] <TheMuso> pitti: Right, I'm pondering that now.
[22:53] <pitti> TheMuso: as long as we have some other delta anyway, it might
[22:53] <pitti> TheMuso: but don't worry too much about it now
[22:53] <TheMuso> I'm not, but certainly something to ponder in the future.
[22:53] <TheMuso> I'd say that will be the last atk upload for this cycle.
[22:54] <RAOF> seb128: So, it depends on how much we want the gl backend enabled.  I don't think it'd be feasible to work-around this problem for natty.
[22:54] <TheMuso> Atk atm doesn't get very frequent upstrea releases.
[22:55] <RAOF> seb128: As for whether we should do something about it - it's pretty obnoxious to needlessly bloat the memory size of every process that links to cairo by 5MiB (on amd64 - on i386 apparently this can be as big as 15MiB).
[22:56] <RAOF> seb128: So it's “how much do we care about the nvidia binary drivers vs. how much do we care about cairo-gl”
[22:56] <seb128> RAOF, do you have any better suggestion than roll back on cairo gl and put wayland in a ppa for natty?
[22:56] <walters> RAOF: 5MiB writable?
[22:56] <seb128> RAOF, well my view on our numbers of nvidia users against wayland users is easy
[22:57] <seb128> RAOF, but I don't want to undermine the efforts put on wayland or get in the way of other people work
[22:57] <seb128> so it turns to be rather a political decision than a technical one to me now
[22:57] <RAOF> seb128: Longer term this could probably be solved by having cairo dynamically load backends on use, but that's not feasible for natty.
[22:57] <seb128> like the technical decision seems obvious
[22:58] <pitti> I agree
[22:58] <seb128> RAOF, right, I'm just suggesting rolling back on cairo-gl for natty and putting back when we open next cycle
[22:58] <pitti> bryceh: as this touches you most, what do you think?
[22:58] <bryceh> :-(
[22:58] <RAOF> Yeah.  I think that's the most sensible solution.
[22:59] <pitti> bryceh: it's a pretty big setback, I agree, but if we can't solve that :(
[22:59] <RAOF> walters: 5MiB dirty.
[22:59] <walters> ouch
[23:00] <bryceh> pitti, it seems like throwing the baby out with the bathwater
[23:00] <RAOF> More ouch is someone reported 15MiB dirty (for *gnome-terminal* )
[23:01] <bryceh> for as much effort as it took to get this in, it's really disappointing.  It's going to make people think, "Oh, yeah wayland really isn't ready, I won't look at it for another 6 months"
[23:01] <pitti> bryceh: that's why I'm asking -- better ideas much welcome
[23:01] <RAOF> Well, we *could* ask nvidia why they're dirtying so much memory in their libGL.
[23:01] <pitti> could we build two libcairo libraries, one with gl, the other without, and have wayland depend on the gl-enabled one?
[23:02] <jcastro> kenvandine: test
[23:02] <jcastro> kenvandine: test
[23:02] <jcastro> kenvandine: test
[23:02] <jcastro> (sorry guys, helping ken test)
[23:02] <seb128> jcastro, you know you can test in query right?
[23:02] <jcastro> he told me in here
[23:02] <seb128> ok ;-)
[23:02] <kenvandine> ok, that patch doesn't work
[23:02] <seb128> :-(
[23:02] <kenvandine> i tried in a query first
[23:03] <kenvandine> i'll look at it a bit more later, i need to eat
[23:03] <kenvandine> later folks...
[23:03] <kenvandine> seb128, you get some rest!
[23:03] <seb128> see you kenvandine
[23:03] <seb128> yeah, I will in a bit
[23:03] <kenvandine> we'll have fallout to deal with tomorrow :-D
[23:03] <bryceh> pitti, it seems like a chicken and egg situation...  before anyone will start porting gtk and making apps work, you have to show wayland works and is packaged and ready; but we're kicking it out because there's no apps to use on it
[23:03]  * kenvandine hopes not
[23:04] <kenvandine> jcastro, thx for testing
[23:04] <bryceh> pitti, anyway, I guess if no one else cares about wayland, just kick it out.  Some day we can look at wayland again I guess.
[23:04] <pitti> bryceh: two cairo variants wouldn't work for that?
[23:04] <bryceh> pitti, afaik it would
[23:04] <RAOF> Can we actually make two cairo variants work?
[23:05] <seb128> bryceh, it's not that no one care, it just seems the cost is higher than the benefit for natty
[23:05] <bryceh> I was maintaining a forked libcairo in a ppa previously but it was a PITA to keep it up to date with libcairo changes in trunk.  I don't really want to have to do that
[23:05] <RAOF> Actually, I guess we could quite easily.
[23:05] <pitti> we would need a libcairo2 (without GL) and a libcairo2-gl, and update the shlibs accordingly
[23:05] <pitti> $ apt-cache rdepends libcairo2|wc -l
[23:05] <pitti> 1185
[23:05] <seb128> well the issue is that gtk etc depends on libcairo2
[23:05] <pitti> hm, that's a whole lot of package rebuilds, though :/
[23:05] <seb128> that and provides are not versionned
[23:06] <pitti> seb128: another trick would be libcairo2-gl depending on libcairo2, and diverting the library
[23:06] <pitti> that would avoid a mass rebuild
[23:06] <seb128> bryceh, well maintaining a ppa during an unstable cycle or for a stable distro is not the same work, natty will not likely got a lot of cairo uploads
[23:06] <RAOF> We could throw libcairo2-gl somewhere else; it's only used for wayland at the moment.
[23:06] <seb128> we will put it back when next cycle start
[23:07] <pitti> RAOF: wouldn't the actual apps need it as well?
[23:07] <pitti> RAOF: I can't believe that _only_ wayland would need libcairo
[23:07] <pitti> bryceh: no, I don't mean a separate source package, just an additional binary
[23:07] <RAOF> pitti: Yeah, but it'd be a matter of LD_LIBRARY_PATHing for binaries in a single package.
[23:08] <RAOF> pitti: For natty, and then we fix it properly for O.
[23:09] <seb128> right, having wayland sessions tweaking the LD_LIBRARY_PATH or doing some LD_PRELOAD should work
[23:10] <pitti> seb128: i. e. libcairo-gl would install an /etc/ld.so.conf.d/00-libcairo-gl.conf ?
[23:10] <pitti> (to ensure that it comes first)
[23:10] <seb128> pitti, wayland would
[23:10] <seb128> or libcairo-gl
[23:10] <pitti> seems more robust than setting LD_LIBRARY_PATH
[23:10] <seb128> either would work
[23:11] <pitti> seb128: I think libcairo-gl, as it knows where it installs itself
[23:11] <seb128> pitti, well, you don't want to preload the gl backend under xorg
[23:11] <seb128> do you?
[23:11] <pitti> seb128: well, it'd only happen if you install libcairo-gl, and then you actually might want it?
[23:12] <seb128> hum, fair enough
[23:12] <seb128> that would work for me
[23:12] <pitti> but I'm not fussed about wayland setting LD_LIBRARY_PATH or using ld.so.conf.d
[23:12] <RAOF> Yeah.  It's quite concievable that X apps might want to use cairo-gl for their own nefarious purposes.
[23:12] <seb128> well the easier would be to keep in a ppa for this cycle, maintaining a stable ubuntu ppa is not a lot of work
[23:13] <seb128> it's likely less work that changing cairo to double build binary and wayland to preload things
[23:13] <Amaranth> RAOF: latest mesa uploads to edgers appear to have fixed my issues with sandy bridge and unity
[23:13] <seb128> then to revert in a few weeks when next cycle open
[23:13] <RAOF> Amaranth: Yay!  Hurray for Sarvatt!
[23:13] <Amaranth> still no EGL/GLES love though :/
[23:14] <Amaranth> oh, also, smspillaz, I love you
[23:15] <Amaranth> unity-window-decorator doesn't break my OCD snapping anymore :)
[23:16] <seb128> RAOF, bryceh: could someone mention the nvidia issue to the nvidia guys to start?
[23:16] <pitti> chrisccoulson: I take mozvoikko as well
[23:16] <chrisccoulson> pitti - cool, thanks
[23:16] <chrisccoulson> i'm not sure how well you will get on with that, as i might need to make changes to the firefox-sdk for that
[23:17] <chrisccoulson> (although, i'm not too sure yet)
[23:17] <chrisccoulson> i'll add bits to the SDK as and when we need them ;)
[23:17] <chrisccoulson> (like pkg-config files etc)
[23:18] <chrisccoulson> pitti - are you still working? ;)
[23:19] <pitti> chrisccoulson: I wanted to get gtk-vnc out of the way, and now at least ensure that atk builds everywhere, to unblock python-gtkspell, gnome-media, and other uploads
[23:19] <RAOF> seb128: Yeah, we should do that.  bryceh - you've got more direct contact with the nvidia guys, want to do that?  Or should we ask Alberto to mention it?
[23:19] <pitti> chrisccoulson: my wife's away, and I can just sleep in tomorrow :)
[23:19] <chrisccoulson> heh :)
[23:19] <chrisccoulson> i'm just about to test couchdb against libmozjs now
[23:20] <pitti> bryceh, seb128, RAOF: so are we in agreement with the libcairo-gl multi-build solution? (and adding that new dependency to wayland)
[23:20] <bryceh> RAOF, alberto works with them a bit more closely but yeah I can take care of sending a notice about it
[23:21] <seb128> pitti, I'm fine with it, I think it would be easier to just have a cairo build in a ppa for natty than rewritting the packaging to drop it in a few weeks but I can understand some people prefer to keep wayland in universe
[23:21] <bryceh> pitti, I think that sounds like a great compromise
[23:21] <seb128> i.e I will be ok with anything that solve the issue for the default install
[23:23] <RAOF> bryceh: We could probably leave it up to Alberto; it's not urgent.
[23:23] <bryceh> RAOF, ok, then I'll take the action to give him the background on the issue
[23:23] <Sarvatt> RAOF: that means he was hitting the amd64 tls problem
[23:23] <seb128> bryceh, RAOF, pitti: thanks
[23:24] <bryceh> seb128, pitti, RAOF, thanks
[23:24] <RAOF> Sarvatt: Ah, ok.  Well, that should get fixed when the patches get applied upstream then pulled back into edgers, I guess.
[23:25]  * Sarvatt nodw
[23:26] <Sarvatt> it'll be nice not to have a 24MB usr/lib/nvidia-current/libnvidia-glcore.so.270.30 in my initrd because of cairo-gl if that gets reverted :)
[23:26] <Sarvatt> (thanks cairo and plymouth)
[23:27] <pitti> chrisccoulson: I need to call /usr/lib/firefox-devel-4.0/sdk/bin/xpidl for that; do I get /usr/lib/firefox-devel-4.0/sdk/ from any pkg-config-ish thing?
[23:27] <pitti> chrisccoulson: or shoudl I hardcode the path?
[23:27] <pitti> chrisccoulson: ah, nevermind; pkg-config --variable=sdkdir firefox-plugin
[23:28] <chrisccoulson> pitti - ah, yeah, that should work
[23:33] <bryceh> RAOF, emailed alberto
[23:34] <bryceh> RAOF, I'll let the wayland guys know too
[23:35] <robert_ancell> what package provides the bluetooth indicator?
[23:37] <TheMuso> gnome-bluetooth
[23:39] <pitti> chrisccoulson: right, it's a lot harder than gtk-vnc, but at least there's progress ;)
[23:43] <bryceh> seb128, I've sent notification to wayland and to NVIDIA (via alberto).  Can you also forward the bug to libcairo, in case it happens to be a bug in the gl implementation?
[23:44]  * bryceh shuts down for some hardware futzing
[23:45] <RAOF> It's not a bug in cairo-gl.
[23:46] <RAOF> *Any* app which links against nvidia's libGL gets the memory usage.
[23:48] <pitti> chrisccoulson: did you happen to see this before? http://paste.ubuntu.com/584545/
[23:49] <pitti> chrisccoulson: I can't make head or tail of it, as all the line numbers there are totally bogus
[23:50] <pitti> chrisccoulson: mozVoikko.cpp:28 is #include "mozVoikkoSpell.hxx", which is still correct; but mozVoikko.hxx:25 is "#define NOCAP   0"..
[23:50] <pitti> and /usr/include/firefox-4.0/nsStringAPI.h:1058 is an assertion about sizeof(wchar_t)
[23:51] <pitti> chrisccoulson: if not, I'll try to dig deeper, but maybe that's a common trap
[23:51] <chrisccoulson> pitti - hmm, i've not seen that one before
[23:51] <pitti> chrisccoulson: ok, thanks
[23:53] <pitti> chrisccoulson: ah, bug 515872  :)
[23:53] <ubot2> Launchpad bug 515872 in firegpg "firegpg FTBFS: xulrunner.../nsStringAPI.h: size of array 'arg' is negative" [Undecided,Fix released] https://launchpad.net/bugs/515872
[23:53]  * pitti shamelessly steals from Kamal's branch then
[23:54] <chrisccoulson> pitti - oh, was mozvoikko using one of the xulrunner pkg-config files before?
[23:54] <pitti> chrisccoulson: yes
[23:54] <chrisccoulson> we define -fshort-wchar there ;)
[23:54] <pitti> pkg-config --cflags libxul (and --libs)
[23:55] <pitti> chrisccoulson: ah, but not in firefox-plugin.pc
[23:55] <chrisccoulson> yeah, firefox-plugin (and mozilla-plugin) only really exist for finding the npapi headers
[23:57] <pitti> ok, one step further, to the next failure
[23:57] <pitti> at least I'm in the link stage now :)
[23:58] <pitti> pkg-config --libs firefox-plugin
[23:58] <pitti> ah, that's empty