[00:01] <JoeJulian> Eh, never mind. I'll just tell him to come here himself.
[00:03] <MrChrisDruif> !patience
[00:03] <ubot2> Don't feel ignored and repeat your question quickly; if nobody knows your answer, nobody will answer you. While you wait, try searching https://help.ubuntu.com or http://ubuntuforums.org or http://askubuntu.com/
[00:03] <MrChrisDruif> Sorry, needed to do that even thou he left (or because he left)
[02:10] <chrisccoulson> hmmm, does anyone know if it is possible to make objdump work properly with a stripped binary and separate debug symbols?
[02:11] <chrisccoulson> disassembling a stripped binary is a little painful
[03:53] <pitti> Good morning
[04:30] <robert_ancell> pitti, is the autosyncing working in quantal?
[04:31] <pitti> robert_ancell: yes, it should; but it coudl be that we are still syncing from testing
[04:31] <robert_ancell> pitti, how would I find out?
[04:31] <pitti> robert_ancell: if you wait for a particular package, find out when it was uploaded to unstable and when to quantal
[04:32] <pitti> in general, I'd say "ask cjwatson", he's driving those
[04:32] <robert_ancell> ok
[05:06] <pitti> Sweetshark: is there a "release calendar" for libreoffice for quantal?
[05:06] <pitti> Sweetshark: I'd like to add the important releases to https://wiki.ubuntu.com/QuantalQuetzal/ReleaseInterlock
[05:14] <pitti> Sweetshark: ah, found http://wiki.documentfoundation.org/ReleasePlan/3.6
[05:26] <pitti> robert_ancell: note that newer gvfs is not blocked by udisks2, it still supports the old gdu monitor
[05:26] <pitti> robert_ancell: but I'll switch it anyway
[05:26] <robert_ancell> pitti, oh cool.  I wasn't sure so I linked them all together :)
[05:27] <robert_ancell> pitti, I guess I'll have to learn this stuff with you being busy with other things :)
[05:27] <pitti> robert_ancell: do you want do do the update?
[05:27] <robert_ancell> pitti, sure
[05:27] <pitti> robert_ancell: ok, then I'll stand by for questions :)
[05:28] <robert_ancell> pitti, question 1) what's a good smoke test to do for gvfs
[05:28] <pitti> robert_ancell: I usually test the following:
[05:28] <pitti> USB stick: insert, verify automounting, safe-eject; reinsert, remount, yank out, check auto-umount
[05:29] <pitti> libgphoto2 camera: insert, check pictures in nautilus
[05:29] <pitti> ssh connection in nautilus (I have a bookmark to my server)
[05:29] <pitti> archive mounter -> open an .iso, verify mount in nautilus
[05:29] <pitti> that should provide pretty good coverage
[05:29]  * robert_ancell takes notes
[05:29] <pitti> robert_ancell: I also have a work item to write automatic tests for those
[05:30] <robert_ancell> pitti, that will be 1000000x better :)
[05:30] <pitti> robert_ancell: perhaps one day I'll have some time to work on upstream tests!
[05:30] <robert_ancell> pitti, heh, still getting stuck doing old job stuff?
[05:31] <pitti> no, just kidding
[05:31] <pitti> well, "yes"
[05:31] <pitti> still working on the jockey bits, and stable+1
[05:31] <pitti> I'll transfer on June 1st
[05:31] <robert_ancell> we have 8 years of reliance to wean ourselves off
[05:39] <BigWhale> Good Morning.
[06:23] <didrocks> good morning
[06:32] <RAOF> Good morning didrocks!
[06:32] <didrocks> hey RAOF, how are you?
[06:33] <RAOF> Good! Having fun reworking the xwayland init sequence to support nouveau :)
[06:35] <pitti> hey didrocks, bonjour BigWhale
[06:35] <pitti> hey RAOF
[06:35] <RAOF> Where today the role of "fun" will be played by staring at the interlinked global state that is the Xserver startup sequence.
[06:35] <RAOF> Hey pitti!
[06:37] <didrocks> guten morgen pitti
[06:37] <RAOF> Also, 8-bit ‘OK Computer’ is much better than 8-bit ‘Kid A’.  Although that might also be due to OK Computer being much better than Kid A :)
[06:37] <didrocks> RAOF: sounds fun ;)
[06:39] <dpm> good morning desktop folk
[06:48] <didrocks> hey dpm
[06:48] <dpm> hey didrocks ;)
[06:49] <rickspencer3> good morning didrocks, dpm, pitti
[06:49] <pitti> hey rickspencer3
[06:49] <didrocks> bonjour rickspencer3 :)
[06:49] <rickspencer3> (and anyone else who is up ;) )
[06:49] <pitti> guten Morgen dpm!
[06:49] <dpm> bonjour rickspencer3
[06:49] <dpm> und morgen pitti
[06:49] <dpm> nice round of goodmornings today :)
[06:51] <dpm> hey pitti, would you have any ideas on how to solve this?: http://askubuntu.com/questions/140552/how-to-make-glade-load-translations-from-opt
[06:51] <dpm> or would anyone else?
[06:52] <dpm> I'm pretty much stuck there, I hadn't realized that translations were not supported in /opt (well, technically in Glade), and it's a bit of a bummer if it's not possible to ship translated apps in our app developer process
[06:54] <pitti> dpm: I don't have an off-hand idea for this; it just seems odd to me that GtkBuilder wouldn't use the normal dgettext() call, which already has been pointed to /opt via bindtextdomain
[06:54] <pitti> that certainly sounds like a bug in GtkBuilder
[06:56] <dpm> pitti, yeah, in fact, the set_translation_domain should not be needed, either and GtkBuilder should just use what gettext uses, but IIRC from a bug long ago, there is no intention upstream to change this
[06:56]  * dpm tried to dig out the bug #
[06:56] <dpm> *tries
[06:57] <pitti> yes, I agree -- in absence of a particular my_builder.set_domain call, it should just call gettext() and be done with it
[06:58] <dpm> bummer, yet another /opt blocker :(
[07:00] <dpm> Here's the upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=574520
[07:00] <ubot2> Gnome bug 574520 in documentation "gtk.Builder translations fail" [Normal,Resolved: notabug]
[07:02] <dpm> From there, I understand that I should use locale.bindtextdomain() but it just feels like unnecessary work. In any case, if it works, I'm happy again
[07:02]  * dpm tries
[07:04] <pitti> ah, that bug was still for the static bindings, which did their own magic
[07:06] <dpm> pitti, I'm not sure I can follow
[07:07] <dpm> I understand the bug is still relevant, right?
[07:07] <pitti> dpm: so does gettext.bindtextdomain() work? I thought the question said it wouldn't
[07:08] <dpm> pitti, no, that does not work
[07:08] <dpm> it works for the non-glade strings
[07:08] <dpm> but all of the UI is untranslated
[07:09] <dpm> there are suggestions in the bug to use locale.bindtextdomain() or libintl.bind_textdomain_codeset(domain, 'UTF-8') - I'm going to try that next
[07:09] <dpm> see if Glade picks it up from there
[07:10] <pitti> these are all exported by gettext, not locale
[07:10] <pitti> dpm: I wonder if it wouldn't be easier to set LOCPATH
[07:11] <mhr3> hey guys, is there some known issues with extras repo signature?
[07:11] <mhr3> i'm getting http://paste.ubuntu.com/1000376/
[07:12] <dpm> pitti, would that not affect other translations that should be loaded from /usr/share/locale (e.g. gtk translations)?
[07:12] <pitti> dpm: err, ignore me; that's for locales, not gettext
[07:13] <dpm> ok, gotcha
[07:13] <pitti> dpm: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=114461#12 -> nice hack :)
[07:13] <ubot2> Debian bug 114461 in gettext "gettext: there is no way to control where message catalogs are found at run time" [Normal,Open]
[07:14] <pitti> dpm: if that works, we should think about hiding this behind something, but it's worth a try
[07:15] <dpm> pitti, oh my, you could press me to say that hack is "clever", but not "nice" :)
[07:15] <dpm> but I'm up for anything that makes translations work
[07:16] <pitti> dpm: yes, I still think that there's something wrong in GtkBuilder
[07:16] <pitti> but if that hack works, we are a step closer to knowing what's wrong
[07:17] <dpm> yes, although upstream seem to make it pretty clear that they're not interested in fixing it https://bugzilla.gnome.org/show_bug.cgi?id=574520#c5
[07:17] <ubot2> Gnome bug 574520 in documentation "gtk.Builder translations fail" [Normal,Resolved: notabug]
[07:18] <pitti> dpm: note that this is pygtk's upstream, not GTK's
[07:18] <pitti> and pygtk had some custom magic about translations, so it does not directly apply to GTK itself
[07:21] <dpm> pitti, right, so you think it'd be worth me filing a new bug against gtk? In any case, the GtkBuilder C API does not seem to have a bindtextdomain method, either http://developer.gnome.org/gtk3/stable/GtkBuilder.html#gtk-builder-set-translation-domain
[07:23] <pitti> If the
[07:23] <pitti>  * "translatable" attribute is set to a true value, GTK+ uses gettext() (or
[07:23] <pitti>  * dgettext() if the builder has a translation domain set)
[07:23] <pitti> dpm: RTFSing..
[07:25] <dpm> oooh, so that in theory it should work
[07:27] <pitti> _gtk_builder_parser_translate() just calls g_dgettext()
[07:27] <pitti> you can set a domain for the GtkBuilder, but it's not necessary
[07:27] <pitti> and you shouldn't if your .ui files use the same domain as your app
[07:28] <pitti> but even if you do set the domain, it still just uses g_dgettext()
[07:28] <pitti> dpm: were you trying this with PyGTK or GI?
[07:28] <dpm> GI
[07:28] <pitti> dpm: I don't see any reason in the code why bindtextdomain() at the beginning of the programm (before opening .ui files) should not work
[07:29] <pitti> dpm: so if it indeed doesn't work, then please file a bug report, preferably with a small demo (using /tmp/ or home etc.)
[07:29] <dpm> I did try commenting out the set_translation_domain call, but that did not make a difference, let me try again
[07:30] <dpm> no joy
[07:30]  * dpm prepares a small demo
[07:32] <chrisccoulson> i think the builders hate me: https://launchpad.net/ubuntu/+source/firefox/13.0~b4+build1-0ubuntu3/+build/3508087
[07:32] <dpm> thanks for your help pitti
[07:32] <chrisccoulson> 6 hours and it's only at the start of the testsuite!
[07:33] <pitti> chrisccoulson: hm, the new i386 builders shoudl be blazingly fast
[07:33] <pitti> chrisccoulson: oh, you caught an old one (palmer)
[07:33] <chrisccoulson> pitti - i turned on PGO
[07:33] <chrisccoulson> do you know how much RAM it has got?
[07:33] <chrisccoulson> the PPA builders just time out when linking too
[07:33] <pitti> I don't
[07:59] <seb128> hey
[07:59] <pitti> seb128: FYI, udisks2 is in quantal, and I talked with Robert about gvfs
[08:00] <pitti> seb128: gvfs 0.13.0 still supports the gdu backend, so udisks2 is not a blocker (but it's in now anyway)
[08:00] <pitti> seb128: he wants to do the update now, and I stand by for questions
[08:00] <seb128> pitti, ok, we should change to udisks2 anyway I guess
[08:00] <pitti> robert_ancell | we have 8 years of reliance to wean ourselves off
[08:00] <pitti> seb128: yes
[08:00] <seb128> pitti, did you talk to him about the gtk update by any chance?
[08:00] <pitti> no, I didn't
[08:01] <seb128> ok, no worry, I will keep following up by email ;-)
[08:02] <seb128> pitti, thanks, I learnt "to wean off" today ;-)
[08:02] <seb128> what was the context for that? udisks?
[08:02] <pitti> updating gvfs
[08:02] <pitti> I was going to do it, but then asked whether he prefers to, as it sounded like he would
[08:03] <pitti> so I told him what I usually test
[08:03] <pitti> hopefully we'll have automatic tests in a few months :)
[08:03] <seb128> ;-)
[08:03]  * seb128 hugs pitti
[08:03] <pitti> at least for a (fake) usb stick, ssh, samba, and archive (.iso/.tar) mounts
[08:04] <pitti> these should all be fairly easy to do
[08:04] <pitti> those are what I usually test manually
[08:04] <pitti> oh, and libgphoto, but that's a pain to virtualize
[08:04] <seb128> I'm looking forward having things like smb tested
[08:04] <seb128> that always breaks at some point in the cycle and we always found about it weeks later
[08:05] <pitti> indeed
[08:05] <seb128> seems like people here don't use smb a lot but users out there do ;-)
[08:06] <pitti> that's why I made it an explict WI in https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-desktop-quality
[08:06] <seb128> oh, speaking of WI, where is didrocks to remind me about the meeting reminder email
[08:07] <seb128> didrocks, dude I count on you for reminding me I need to send those ;-)
[08:07] <didrocks> seb128: I didn't say hello yet ;)
[08:07] <didrocks> seb128: meeting reminder!
[08:07] <didrocks> ;)
[08:07] <seb128> didrocks, 'ci!
[08:07] <seb128> didrocks, salut, en forme ?
[08:07] <didrocks> de rien, toujours un plaisir :)
[08:07] <didrocks> ça va, et toi? ;)
[08:07] <seb128> oui, en forme ;-)
[08:09] <rickspencer3> didrocks, tu as couru deja?
[08:10] <didrocks> rickspencer3: non, je le fais le soir, à 19h :) et toi?
[08:11] <rickspencer3> didrocks, il pleut ce matin
[08:11] <chrisccoulson> hmmm, any volunteers for bug 1002590? ;)
[08:11] <ubot2> Launchpad bug 1002590 in thunderbird "No crashreporter in Firefox or Thunderbird" [High,Triaged] https://launchpad.net/bugs/1002590
[08:11] <seb128> rickspencer3, salut
[08:11] <chrisccoulson> hey seb128 didrocks rickspencer3
[08:11] <seb128> hey chrisccoulson, how are you?
[08:11] <chrisccoulson> seb128, yeah, not too bad thanks. a bit tired though. how are you?
[08:12] <seb128> chrisccoulson, I'm good thanks
[08:12] <seb128> chrisccoulson, build it with gcc-4.6 ;-)
[08:12] <didrocks> rickspencer3: je pense que je ferais de l'exercice un peu plus tôt, entre deux pluies :)
[08:12] <didrocks> hey chrisccoulson
[08:12] <chrisccoulson> seb128, yeah, i might do in a bit. but gcc-4.6 fails to build with PGO on ;)
[08:12] <seb128> il pleut à Toulouse ?!
[08:12] <seb128> où va t'on
[08:12] <rickspencer3> seb128, oui, il pleut beacoup
[08:13] <rickspencer3> je suis très triste
[08:13] <rickspencer3> il pleut pour longtemps
[08:13] <rickspencer3> 2 semaine
[08:13] <rickspencer3> :,(
[08:13] <rickspencer3> j'ai demangé a Seattle deja
[08:14] <seb128> rickspencer3, la météo dit que vendredi il fera beau
[08:14] <seb128> et lundi
[08:14] <rickspencer3> oui, pour 1 jour
[08:14] <rickspencer3> grrrrr
[08:15] <seb128> pas de chance pour le weekend par contre :-(
[08:15] <rickspencer3> je vuex etre bien grillé deja
[08:15]  * rickspencer3 shakes fist at Toulouse weather
[08:16]  * didrocks heard from huats that bad weather didn't exist in Toulouse, weird ;)
[08:16] <pitti> OMG, seb128's threat became true
[08:16] <seb128> ;-)
[08:16] <pitti> Il ne parle que français?
[08:16] <rickspencer3> didrocks, huats was correct until I moved here
[08:17] <didrocks> rickspencer3: I didn't see good weather in Toulouse, didn't see it, don't believe it :)
[08:18] <rickspencer3> didrocks, il fait beau quand tu as visité a Toulouse, non?
[08:18] <seb128> didrocks, yeah, I'm sure it's stories people from the south-west tell to make us feel jealous
[08:18] <seb128> doesn't work
[08:18] <didrocks> rickspencer3: non, il a plu justement et très nuageux
[08:18] <rickspencer3> seb128, it worked for me, and then I *moved* here
[08:18] <didrocks> seb128: completely ;)
[08:19]  * rickspencer3 removes fishhook from cheek
[08:19] <seb128> rickspencer3, you should ask them to pay you back, you paid for sun you deserve some!
[08:19] <rickspencer3> indeed!
[08:20] <huats> pfff
[08:20] <seb128> huats, salut ;-)
[08:20] <seb128> RAOF, hey
[08:20] <huats> I amso disapointed of you rickspencer3...
[08:20] <huats> ;)
[08:20] <RAOF> seb128: Hey!
[08:20] <rickspencer3> huats, fair enough, but c'mon, look outside!
[08:20] <didrocks> huats: I think he is disappointed about the weather :p
[08:21] <seb128> RAOF, how are you?
[08:21] <RAOF> seb128: Good, yourself?
[08:21] <seb128> RAOF, I'm good thanks
[08:22] <seb128> RAOF, looking to http://status.ubuntu.com/ubuntu-quantal/canonical-desktop-team.html you have 44 workitems .... seems like a lot ... make sure to not overload you for the cycle please ;-)
[08:23] <rickspencer3> seb128,  you know what to do
[08:23]  * rickspencer3 waits for whip cracking noises
[08:23] <seb128> lol
[08:23] <pitti> RAOF: seems you earned all the leftovers from https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-color-management-next-steps
[08:23] <pitti> that's probably unintended
[08:23] <pitti> http://status.ubuntu.com/ubuntu-quantal/u/raof.html
[08:24] <seb128> right, that was going to be my next question ;-)
[08:24] <huats> rickspencer3: I agree this year the weather is REALLY bad
[08:24] <seb128> should we even track that spec for this cycle?
[08:24] <huats> and remember when you arrived it was realy great
[08:24] <huats> you told me that :)
[08:24] <pitti> seb128: haha, look at that page more closely -- there is a work item called "Work items"
[08:24] <huats> let's wait till the end of the week :D
[08:25] <pitti> seb128: but it seems to be the only glitch like that on http://status.ubuntu.com/ubuntu-quantal/canonical-desktop-team.html
[08:25] <seb128> pitti, I wonder if that's due to the "Work Items:" at the end of the whiteboard
[08:25] <pitti> seb128: presumably
[08:26] <pitti> seb128, RAOF: Note that a fair number of specs just got moved from o and p to q, but they should be revisited and possibly be moved further to r or be dropped
[08:26] <seb128> huats, meteofrance says weather is going to be nice on friday and monday but rainy during the w.e
[08:26] <huats> seb128: they always lie :)
[08:26]  * didrocks was thinking he would have few WI this cycle after assisting the sessions
[08:26] <RAOF> That does seem like a lot; many of those are bugs from colour-management, and a couple of others are obsolete.
[08:26] <seb128> pitti, right, the rootless-x and color ones seem in this case
[08:26] <pitti> ah, ruthless X
[08:27] <seb128> RAOF, should we track the colormanagement spec for the cycle or just deal with bugs out of the cycle spec tracking?
[08:27] <pitti> seb128: the lcms2 transition would be nice to finish indeed, as the old lcms1 stuff is totally deprecated and buggy; but that's not for one person to do alone
[08:27] <seb128> RAOF, please clean up the obsolete ones when you cross them ;-)
[08:27] <pitti> as long as we can at least use lcms2 only in main, that'd already be good progress
[08:27] <seb128> right
[08:27] <RAOF> Will do.
[08:28] <seb128> thanks
[08:28] <seb128> RAOF, and while you are around, can I try to bribe you again to do unapproved SRU reviews this week? ;-)
[08:29] <RAOF> Tomorrow :)
[08:29] <seb128> RAOF, sorry you are my new ping contact in the SRU team, it used to be pitti :p
[08:29] <seb128> RAOF, thanks
[08:29] <seb128> RAOF, like the gwibber there is a one liner to stop hating users who have a non ascii char in their username, it would be nice to get it in ;-)
[08:29] <RAOF> :)
[08:30]  * pitti yays at http://paste.ubuntu.com/1000413/
[08:30] <pitti> welcome, driver lookups behind a PackageKit interface
[08:31] <mlankhorst> pitti: no nouveau? :s
[08:32] <pitti> mlankhorst: if you make x-x-d-nouveau declare Modalias: fields, it will :)
[08:32] <pitti> mlankhorst: but we'll need to special-case nvidia anyway, for the six different variants that we have for it
[08:32] <mlankhorst> pitti: true
[08:33] <mlankhorst> switch (*(uint32_t)pci->bar0 & 0xff00000) >:-)
[08:33] <pitti> mlankhorst: actually, "modinfo nouveau" does have modaliases
[08:34] <pitti> mlankhorst: so if someone ever provides a DKMS package with a backported/experimental/whatever driver, and uses dh_modalises, it will all Just Work ™
[08:34] <mlankhorst> pitti: probably incomplete, it just attaches to everything of class video with manufacturer nvidia..
[08:34] <pitti> *nod*
[08:42] <dpm> pitti, ok, I filed https://bugzilla.gnome.org/show_bug.cgi?id=676543 for the conversation we were having earlier on
[08:42] <ubot2> Gnome bug 676543 in GtkBuilder "Cannot load translations from a locale dir other than the default" [Normal,Unconfirmed]
[08:42] <pitti> dpm: thanks, will look at that in a bit
[08:43] <pitti> dpm: note that you didn't actually attach something?
[08:43] <dpm> argh, I did not?
[08:44] <dpm> weird, did not seem to upload it the first time. It is there now, thanks for the heads up!
[08:45] <dpm> pitti, I also tried http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=114461#12 but that did not seem to work with my example
[08:45] <ubot2> Debian bug 114461 in gettext "gettext: there is no way to control where message catalogs are found at run time" [Normal,Open]
[08:51] <seb128> pitti, what was the meeting time usually in summer? I never know with DST, I proclaimed 15:30 UTC since I think earlier works better for most of us
[08:51] <pitti> seb128: that's correct
[08:52] <seb128> great
[08:52] <pitti> seb128: https://wiki.ubuntu.com/DesktopTeam/Meeting has that
[08:54] <pitti> mvo: would you mind if I upload the current aptdaemon quantla packaging branch? I'm blocked on getting the test dbus.conf shipped in the package
[08:54] <pitti> mvo: (otherwise my shiny new ubuntu-drivers-common will fail to build)
[08:54] <pitti> mvo: if you are planning to do an upload soon anyway for glatzor's py3 branch, I can wait a day or two, of course
[09:01] <mvo> pitti: not at all ,please go ahead
[09:03] <pitti> mvo: ok, done
[09:04] <mvo> ta
[09:31] <pitti> mvo: oh, to avoid duplicate work: I have most of a Python 3 port for apturl here
[09:31] <pitti> mvo: but I need python3-aptdaemon for that first (see glatzor's mail)
[09:31] <pitti> mvo: so please don't start working on apturl for now
[09:33] <mvo> pitti: ok
[09:33] <mvo> pitti: thanks for the info!
[09:33] <mvo> pitti: iirc there was a test failure in the py3 branch from glatzor
[09:34] <didrocks> Laney: hey
[09:34] <didrocks> Laney: looking at the https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-deprecate-language-selector you just changed the status
[09:34] <Laney> yeah, though I was supposed to as assignee?
[09:34] <didrocks> Laney: not sure if they want to automate the collect of the Goal/other markers, if so:
[09:34] <Laney> or is that for someone else
[09:34] <Laney> if so, move it back :-)
[09:35] <didrocks> no no, it's fine :)
[09:35] <didrocks> - Goal should be in the in the first part for the description
[09:35] <Laney> oh oh
[09:35] <didrocks> - typo (it's Test Plan: and Release Note:)
[09:35] <didrocks> the rest looks good :)
[09:35] <Laney> I didn't know they were going to be automatically processed
[09:35] <didrocks> just in case they want to collect that :)
[09:35] <didrocks> not sure as well, but let's follow the wiki just in case
[09:35] <Laney> ok
[09:36] <didrocks> I'll approve once you do those changes
[09:36] <Laney> should I remove the rest of the description?
[09:36] <didrocks> I guess it's fine, I added those afterwards though with sesssion notes: ------------------
[09:36] <didrocks> but I guess it's rather a "do as you want" :)
[09:41] <Laney> didrocks: like that?
[09:41] <didrocks> Laney: it's Test Plan*s*: IIRC
[09:42] <Laney> ok, got it
[09:42] <didrocks> I would remove the Release Note stenza if it's not applicable
[09:42] <Laney> possibly, I just put it because it was listed as mandatory
[09:43] <didrocks> it's not anymore, is it?
[09:43] <Laney> well, "if user visible feature"
[09:43] <Laney> maybe I should write something
[09:43] <didrocks> maybe just tell that there is a newer language selector
[09:43] <seb128> not sure if the change there is worth release noting
[09:43] <didrocks> but yeah, seems minor
[09:43] <seb128> but seems it could
[09:43] <Laney> that's what I thought, but the wiki says that it should be for any user visible feature
[09:44] <Laney> lets just leave it and see if anyone complains
[09:44] <didrocks> ok, we can change it later if it's automagically collected anyway
[09:44] <didrocks> let's approve it then
[09:44] <didrocks> and done :)
[09:44] <Laney> I think I need to be added to some team to show up on the tracker btw
[09:44] <Laney> thanks!
[09:44] <didrocks> yw
[10:45] <chrisccoulson> wow, nearly 9 hours - https://launchpad.net/ubuntu/+source/firefox/13.0~b4+build1-0ubuntu3/+build/3508084 !
[10:47] <slomo> seb128: what's needed to sync gstreamer1.0, gst-plugins-{base,good,bad,ugly}1.0 and gst-libav1.0 from debian/experimental? :)
[10:47] <seb128> slomo, you asking, I will do it after lunch
[10:48] <seb128> slomo, thanks for pointing those ;-)
[10:48] <slomo> seb128: thanks, will just update gst-plugins-bad and gst-libav then :)
[10:50] <seb128> slomo, yw!
[10:50] <seb128> chrisccoulson, no timeout this time?
[10:50] <seb128> chrisccoulson, didn't firefox use to build in like 3 hours?
[10:51] <chrisccoulson> seb128, yeah, maybe the timeout is shorter on the PPA builders?
[10:51] <seb128> chrisccoulson, oh, build success, congrats! ;-)
[10:51] <seb128> could be...
[10:51] <chrisccoulson> seb128, yeah, the success is without the crash reporter though ;)
[12:09] <cjohnston> mpt: ping
[12:20] <slomo> seb128: ok, gstreamer1.0, gst-plugins-{base,good,bad,ugly}1.0 and gst-libav1.0 0.11.91-1 could be synced from debian/experimental now :) last bad/libav were just uploaded so might not be there yet, but the 0.11.91-1 version is important
[12:20] <seb128> slomo, ok
[12:20] <pitti> slomo: ah, you can't upload them yourself?
[12:21] <pitti> slomo: ... and thanks!
[12:21] <slomo> pitti: i can, sure :) but these are syncs
[12:21] <pitti> slomo: right; I mean when you are able to upload a package, you are also able to call syncpackage for them
[12:21] <pitti> just saying
[12:21] <slomo> pitti: oh, good to know :)
[12:22] <pitti> syncpackage -d experimental <pkgname> (in ubuntu-dev-tools)
[12:22] <seb128> slomo, want to try?
[12:22] <slomo> seb128: yes, trying :)
[12:24] <slomo> seb128: seems to work, now only waiting for bad/libav to appear :)
[12:24] <seb128> slomo, great!
[12:25] <seb128> yeah, they are in NEW
[12:25] <pitti> slomo: indeed, they are in https://launchpad.net/ubuntu/quantal/+queue?queue_state=0 now
[12:25] <pitti> seb128: do we want them in main already for switching over, or universe for now?
[12:26] <seb128> pitti, universe
[12:26] <pitti> done
[12:26] <seb128> we will promote then when something start pulling them in
[12:26] <seb128> pitti, danke
[12:27] <slomo> pitti: shall i sync old versions of bad/libav now already to cause less work for you (you could accept them now already), and just update later?
[12:27] <pitti> slomo: it doesn't matter much either way really
[12:27] <seb128> update later shouldn't be extra work
[12:28] <slomo> pitti: ok, they should be there too now... thanks :)
[12:28] <slomo> seb128: do you know if gnome decided to go with gstreamer 1.0 for next release already?
[12:29] <seb128> slomo, I don't know, that's one of the things we put on the list at UDS, check GNOME plans to determine what version we will use
[12:29]  * pitti is looking forward to an introspectable gstreamer
[12:29] <pitti> slomo: done
[12:31] <slomo> pitti: that's much better with 1.0 already, but some simple changes are still missing in g-i... like being able to specify that struct X, that has struct Y as first member, can be used like any struct Y instance (i.e. simple struct inheritance)
[12:40] <ritz> question on bamf/unity launcher. we tend to combine javaws app under one group
[12:40] <ritz> whereas they might be different instances
[12:41] <ritz> is this is design choice, or something we overlooked ?
[12:41] <seb128> Trevinho, ^
[12:42] <seb128> bug I would say in any case
[12:43] <ritz> seb128, thanks
[12:43] <seb128> yw
[13:02] <hggdh> bryceh: ping
[13:10] <cyphermox> good morning!
[13:10] <asac> i am not sure when it started, but for a few days at least i have the sound settings dialog disppear (crashing?) if i click on the bluetooth headset in the "input" tab
[13:11] <asac> gnome-control-center
[13:11] <asac> (gnome-control-center:9674): sound-cc-panel-CRITICAL **: gvc_mixer_stream_get_port: assertion `stream->priv->ports != NULL' failed
[13:11] <asac> Segmentation fault
[13:11] <asac> precise up to date that is
[13:11] <asac> i can select other input devices though (mic and internal are OK to click on)
[13:12] <seb128> cyphermox, hey, how are you?
[13:12] <seb128> asac, hey
[13:12] <asac> hello seb128
[13:12] <seb128> asac, can you report a bug with a debug stacktrace?
[13:12] <asac> can i do that :)?
[13:12] <asac> hehe
[13:12] <cyphermox> hey, not bad, not bad
[13:12] <asac> have to resurrect the dbgsym stuff i guess
[13:16] <asac> ok running apport-bug i guess
[13:16] <asac> thought there was a way to easily retrace stuff locally
[13:17] <seb128> asac, sudo apport-retrace ...?
[13:18] <asac> that doesnt exist :)
[13:18] <asac> oh nevermind
[13:18] <asac> have to install it :)
[13:18] <asac> let me do that
[13:18] <asac> the apport-bug thing failed
[13:18] <asac> (doesnt do anything after collecting info)
[13:19] <seb128> asac, if you run apport-retrace under sudo it will install the required dbg for you I think
[13:19] <asac> install? and cleanup?
[13:19] <asac> :)
[13:20] <asac> thought it would do a chroot or something
[13:31] <jbicha> good morning
[13:32] <seb128> hey jbicha, how are you?
[13:32] <jbicha> should I upload gnome-disk-utility 3.4 now or wait? it drops libgdu http://paste.ubuntu.com/1000839/
[13:32] <pitti> jbicha: better wait until Robert uploads gvfs 0.13 with switching to udisks2
[13:32] <seb128> jbicha, I though robert_ancell was working on it? see version
[13:33] <pitti> jbicha: but there are more reverse dependencies: ejecter, update-notifier, unity, udisks
[13:33] <desrt> seb128: let's talk overrides
[13:33] <pitti> jbicha: and udisks still has quite a few
[13:34] <pitti> jbicha: sorry, udisks is not an rdep, it's a Breaks:
[13:34] <pitti> jbicha: so just ejecter, update-notifier, and unity
[13:34] <desrt> seb128: it seems that currently the overrides are scattered across quite a number of different packages (ie: mostly the packages themselves, not a super-duper-overrides package)
[13:34] <desrt> do we want to continue in that way when we switch to dconf-based overrides?
[13:34] <desrt> or do we want an overrides package?
[13:35] <pitti> IMHO by-package, as we have now
[13:35] <desrt> imho it would be more manageable to have one package
[13:35] <didrocks> ogra_: hey, just a question, the .armel and .armhf for compiz installs are the same right?
[13:35] <pitti> desrt: that totally doesn't extend to using PPAs, third-party packages, backports, SRUs, etc.
[13:36] <desrt> pitti: definitely not -- but then neither do language packs
[13:36] <pitti> well, of course both could be combined
[13:36] <ogra_> didrocks, they are binary incompatible
[13:36] <desrt> we'd use the one-big-package approach for things we ship on the CD, for example
[13:36] <pitti> i. e. backports etc. could still ship their own overrides
[13:36] <desrt> indeed
[13:36] <didrocks> ogra_: right, I but I mean, the plugins that you build/install are the same?
[13:36] <ogra_> hf binaries wont run on el systems or the other way round
[13:36] <ogra_> build process is identical, yeah
[13:37] <ogra_> its just different compiler options
[13:37] <didrocks> ogra_: ok thanks, that will make my life a little bit less painful in this compiz refactoring :)
[13:37] <desrt> considering that the purpose of this exercise is to allow the overrides to be used conditionally it seems to make sense to also allow them to be uninstalled if people don't care to use them at all
[13:37] <desrt> which is quite a lot harder with multiple packages
[13:37] <desrt> (well, impossible, really... i don't want to uninstall gnome-settings-daemon)
[13:37] <ogra_> didrocks, i thought you were supposed to get a proper upstream tree now
[13:37] <pitti> desrt: that hardly seems to be a question of all or nothing, though?
[13:38] <seb128> desrt, pitti: doh, I don't look to this channel for 5 minutes and get 3 screens of backlog ;-)
[13:38] <chrisccoulson> wow, i'm not sure how we've ever successfully built firefox before :/
[13:38] <seb128> desrt, pitti: I sort of like having an ubuntu-default package with our settings
[13:38] <chrisccoulson> http://paste.ubuntu.com/1000848/ is the fix for bug 1002590
[13:38] <ubot2> Launchpad bug 1002590 in thunderbird "No crashreporter in Firefox or Thunderbird" [High,Triaged] https://launchpad.net/bugs/1002590
[13:38] <desrt> pitti: it's a question of my own obsessive compulsive disorder, i guess :)
[13:38] <kenvandine> chrisccoulson, that is scary :)
[13:39] <didrocks> ogra_: well, one tree with everything merged (compiz, c-p-m, c-p-e, libcompizconfig, python-compizconfig, compizconfig-gconf-backend, ccsm)
[13:39] <chrisccoulson> kenvandine, yeah. i've no idea how this ever worked before
[13:39] <didrocks> ogra_: but I have to do this merge and it's kind of complex tree of Replaces: shuffling things around, transitional packages… :)
[13:39] <ogra_> didrocks, ouch
[13:39] <ogra_> yeah
[13:39]  * didrocks uses this time as well to remove all the old Breaks/Replaces, sprint cleaning!
[13:39] <ogra_> why did they do that ? so you need to upload the whole if someone fixes a single module ?
[13:40] <didrocks> ogra_: yeah, for their test and handling the ABI break in an easier way
[13:40] <ogra_> ah
[13:40] <didrocks> ogra_: TBH, that will avoid waiting for 4 hours if there is an ABI break until we can rebuild unity
[13:40] <didrocks> so quite happy
[13:41] <ogra_> yeah, but quite a lot of work :)
[13:41] <didrocks> the additional build-time is low compared the benefit :)
[13:41] <didrocks> indeed
[13:41] <ogra_> but we all know you are workaholic :)
[13:41] <ogra_> its the french wine i guess :) seb128 is the same way
[13:41] <didrocks> well, I'm more in a red wine area, he's on the white wine side :)
[13:41] <smspillaz> ogra_: fyi: lp:~compiz-linaro-team/compiz/gles2
[13:42] <smspillaz> I am merging in all of the other plugins now
[13:42] <ogra_> smspillaz, awesome !
[13:42] <ogra_> \o/
[13:42] <smspillaz> \o/
[13:42] <smspillaz> ogra_: do you know what our support is like for the zareason tablet ?
[13:42] <ogra_> smspillaz, nope, but if you get bootloader and a recent kernel source it should be trivial
[13:43] <smspillaz> mmmm
[13:44] <ogra_> (or send me one and i can roll a community install image :) )
[13:44] <smspillaz> lol
[13:46] <seb128> pitti, do we have a record somewhere of the end of precise status-wis page?
[13:46] <pitti> seb128: http://status.ubuntu.com/ubuntu-precise/canonical-desktop-team.html ?
[13:47] <seb128> pitti, no, that got screwed up by spec moved over
[13:47]  * didrocks will kill a python script at boot soon
[13:47] <seb128> pitti, like RAOF has only 1 workitems on that page
[13:47] <pitti> seb128: oh, indeed; the graph looks quite funny, too
[13:47] <seb128> pitti, I was mostly trying to figure how much items each team member got done to compare to how many them have for q
[13:48] <pitti> seb128: it might be possible to get the database for that point in time, but I don't have access to status.u.c.; question for cjohnston I think
[13:48] <seb128> pitti, well, if we don't have it that's ok, we can do without it
[13:48] <pitti> seb128: want to update https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AoGTYJ3uqCiMdHQzeUI5akNkS1I0ckJGNXpJbnEwLUE&pli=1#gid=0 ?
[13:48] <seb128> I'm not sure how much we can compare from one cycle to the next one anyway, a lot depends of how much non workitem work is done
[13:49] <seb128> pitti, oh, I didn't remember about that page ... well I would do if I had numbers ;-)
[13:50] <chrisccoulson> heh, i always seem to end up spending my whole cycle doing non-workitem tasks ;)
[13:51] <cjohnston> pitti:  I'm not quite sure what the issue referenced above is.. there does seem to be an issue where all of the lts milestones are now appearing making the graphs look odd
[13:51] <seb128> chrisccoulson, you always seem to end up debugging toolchain bugs for weeks you mean ;-)
[13:51] <chrisccoulson> seb128, yeah. although, in this case, it's not a toolchain bug. i still can't figure out what changed to break it though
[13:51] <chrisccoulson> but i guess that doesn't matter too much :)
[13:52] <seb128> cjohnston, the issue is that the precise graphs are off, i.e http://status.ubuntu.com/ubuntu-precise/canonical-desktop-team.html graph goes until end of 2013?
[13:52] <Trevinho> ritz: java apps thing, it's a bug...
[13:52] <Trevinho> ritz: have you a test case I can work on?
[13:53] <cjohnston> seb128: it is showing all the lts milestones.. 12.4.1 .2 etc
[13:53] <seb128> cjohnston, ok, well I was mostly looking at having a picture of the status at precise release time
[13:54] <seb128> cjohnston, we "screwed" it by moving some specs over to q
[13:54] <seb128> cjohnston, they dropped off the p chart
[13:54] <cjohnston> ya
[13:54] <pitti> just curious why ubuntu-precise is still being updated
[13:54] <pitti> I sort of assumed it would stop updating now
[13:54] <seb128> pitti, because we might still track stuff for .1
[13:54] <pitti> it takes ages to generate all the gazillion precise charts
[13:54] <chrisccoulson> now, armhf build failure to debug. fun!
[13:54] <seb128> I guess
[13:54] <cjohnston> yes, its still running
[13:55] <seb128> but yeah, I would have prefered to have the p charts frozen at release
[13:55] <pitti> with all the quantal ones also being generated, won't that bring this machine to death at some point?
[13:55] <cjohnston> I think we may need to have a sit down and think about how we want status to work
[13:55] <seb128> we typically don't use charts for point releases
[13:55] <cjohnston> right now it runs collect all
[13:56] <cjohnston> if we want that changed id like to have a discussion with the stakeholders and get a written 'policy'
[13:57] <seb128> right
[13:57] <seb128> that makes sense
[13:57] <cjohnston> right now there is no real direction afaik
[13:58] <seb128> that's what I just noticed from that discussion ;-)
[13:58] <seb128> bottom line is that I've no easy access to the numbers of the end of the cycle I wanted to look at, I will do without them no worry
[14:00] <cjohnston> it would be nice to have a set way of doing things.
[14:00]  * pitti waves good bye for today; awake since 5:30 already
[14:01] <didrocks> good evening pitti :)
[14:01] <cjohnston> o/
[14:02] <seb128> pitti, 'night
[14:03] <seb128> pitti, did you have anything you wanted to see discussed during the meeting today? or any recommendation on stuff we should cover?
[14:07] <cjohnston> seb128: I'm leaving tomorrow for Connect, will be out there for 9 days, then come home to have surgery two days later so I will be out for atleast two weeks from now, although, that would provide plenty.of time to make sure all stakeholders are aware and have a chance to come up with what they would like to see.. would you all like to try to.get something setup for mid june to start hashing this out so that we hav
[14:07] <ogra_> highvoltage, ^^^^ didnt you play with a zareason tablet ( smspillaz was intrested in it above)
[14:07] <seb128> cjohnston, that line cut at "so that we hav"
[14:08] <seb128> cjohnston, but yeah, I will mention it to the release team meeting
[14:08] <seb128> cjohnston, thanks
[14:08] <cjohnston> things sorted out prior to the end of 12.10
[14:09] <cjohnston> cool. ty
[14:11] <highvoltage> ogra_: I'm still working on getting mine (will probably have that sorted out this week)
[14:12] <ogra_> ah
[14:12] <highvoltage> cjohnston: hope it goes well! get better soon.
[14:13] <highvoltage> smspillaz: darkwing on #kubuntu-devel might be able to help you with the zatab so long, he has it booting but last I heard the screen just came up black
[14:13] <smspillaz> mmmm
[14:13] <smspillaz> just looking for something to test compiz-gles on really
[14:13] <smspillaz> that isn't a desktop driver
[14:13] <ogra_> smspillaz, test as in "run" ?
[14:14] <ogra_> the only reliable device we have for that atm is the pandaboard
[14:14] <highvoltage> smspillaz: iirc stgraber told me that it works fine now on a pandaboard
[14:14] <highvoltage> (well, I saw it working fine on his pandaboard :) )
[14:14] <ogra_> even on my tegra i cant get the transparency of unity fixed atm
[14:15] <smspillaz> highvoltage: sure, although there are shipping difficulties
[14:16] <smspillaz> highvoltage: also I feel like the panda isn't representative of real world hardware, especially when you run it on 1080p displays
[14:16] <ogra_> smspillaz, it totally is ...
[14:16] <ogra_> what isnt representative is that you run from SD though
[14:16] <smspillaz> that's true
[14:16] <ogra_> wrt GPU and drivers it surely is the state of the art
[14:17] <smspillaz> although I'm still ... skeptical about running a 1080p display from a panda
[14:17] <smspillaz> afaict it really just can't handle the fill rates that well
[14:17] <smspillaz> or maybe that's because compiz is not well optimized ATM :P
[14:17] <ogra_> or because we use a memory hole were none should be ;)
[14:18] <smspillaz> ogra_: oh ?
[14:18] <ogra_> iirc our images still waste something like 64M for the video codec engine
[14:18] <highvoltage> smspillaz: you've never used compiz before!?
[14:18] <ogra_> which, if you dont use it is just a wasted memory hole
[14:18] <ogra_> highvoltage, hahaha
[14:21] <smspillaz> highvoltage: I usually don't get high mem usage on compiz standalone
[14:49] <lotheac> phew, apparently I suck at bzr
[14:51] <highvoltage> at least it's well documented :)
[14:51] <lotheac> which means I can't read ;)
[15:04] <ritz> Trevinho, yes, with javaws
[15:04] <ritz> Trevinho, will raise an lp soon
[15:05] <dobey> is *anyone* able to reliably hit bug #853060 in here?
[15:05] <ubot2> Launchpad bug 853060 in ubuntuone-installer/trunk "ubuntuone-installer crashed with GError in function(): Failed to execute child process "ubuntuone-control-panel-gtk" (No such file or directory)" [Critical,Fix committed] https://launchpad.net/bugs/853060
[15:06] <Trevinho> ritz: javaws -about and javaws -viewer have different apps tough, but I have to study other cases
[15:06] <ritz> javaws <jnlp app1>
[15:06] <ritz> javaws <jnlp app2>
[15:07] <ritz> both are listed as one app
[15:07] <ritz> Trevinho, in the launcher
[15:07] <ritz> I do see, for chrome we use is_web_app. I am thinking of writing something similar is_javaws_app
[15:08] <Trevinho> ritz: what's the output for xprop |grep WM_CLASS for both the windows?
[15:09] <ritz> WM_CLASS(STRING) = "sun-awt-X11-XFramePeer", "net-sourceforge-jnlp-runtime-Boot"
[15:09] <ritz> and WM_CLASS(STRING) = "sun-awt-X11-XFramePeer", "net-sourceforge-jnlp-runtime-Boot"
[15:10] <ritz> the difference being WM_NAME(STRING) = "Draw"
 WM_NAME(STRING) = "Notepad"
[15:17] <hggdh> bryceh: when you are in, please ping me (video/X tests)
[15:17]  * dpm hugs kenvandine
[15:19] <kenvandine> dpm, did that work for you?
[15:19] <seb128> didrocks, chrisccoulson, Sweetshark, bryceh, cyphermox, mlankhorst, pitti, Laney, tkamppeter, mterry, kenvandine: desktop meeting in 10 minutes
[15:20] <dpm> kenvandine, haven't even had the chance to try, just read your e-mail. Thanks for the work on the tutorial!
[15:20] <mlankhorst> pong
[15:20] <seb128> didrocks, chrisccoulson, Sweetshark, bryceh, cyphermox, mlankhorst, pitti, Laney, tkamppeter, mterry, kenvandine: you better get your specs in shape, who is caught but lagging behind will win bugs to fix ;-)
[15:21] <mlankhorst> oh hey, jason's back :)
[15:21] <seb128> mlankhorst, no formal need to pong, just be there for the meeting in 9 minutes ;-)
[15:21] <chrisccoulson> seb128, nice ;)
[15:21] <seb128> chrisccoulson, looking forward fixing some extra bugs? ;-)
[15:22] <chrisccoulson> oh yes
[15:22] <MrChrisDruif> Why aren't you pinging the rest of the 162 people in this channel seb128 ? ;-)
[15:23] <mlankhorst> we want people, not fruits ;-)
[15:23] <MrChrisDruif> mlankhorst; Not even Mr fruits? ;-)
[15:29] <seb128> MrChrisDruif, because I will not tell volunteer what they should do ;-)
[15:30] <seb128> didrocks, chrisccoulson, Sweetshark, bryceh, cyphermox, mlankhorst, pitti, Laney, tkamppeter, mterry, kenvandine: desktop meeting time
[15:30] <MrChrisDruif> Ghehe ^_^
[15:30] <mterry> Hello!
[15:30] <cyphermox> yo!
[15:30]  * kenvandine waves
[15:30] <tkamppeter> hi
[15:30] <Laney> hello
[15:30] <chrisccoulson> w00t
[15:31] <seb128> how is everyone? I hope you all made it up from UDS without issue and without the ubuflu
[15:31] <didrocks> hey
[15:31] <Trevinho> ritz: sorry i got a disconnection...
[15:31] <seb128> it has been a while we didn't have a meeting ;-)
[15:31] <seb128> let's get started
[15:31] <seb128> https://wiki.ubuntu.com/DesktopTeam/Meeting/2012-05-22
[15:31] <Trevinho> ritz: however... the problem is that we can't use WM_NAME to classify apps, java must be fixed
[15:31] <Trevinho> ritz: once java will use a different wm_class instance name per each application, then bamf will work. And since these apps don't share the same PID (as it seems to me), the bamf code should not need any other tweak.
[15:32] <seb128> Trevinho, ritz: we have our meeting starting, can you guys move to #ubuntu-unity maybe?
[15:32] <seb128> thanks ;-)
[15:32] <Ursinha> seb128, I'm here as well, fwiw..
[15:32] <seb128> Ursinha, sorry, I was looking to the team on launchpad and forgot you
[15:32] <Ursinha> no problem :)
[15:32] <Trevinho> seb128: oh... sorry..
[15:32] <seb128> Ursinha, good to see you there ;-)
[15:32] <seb128> Trevinho, no worry
[15:32] <Ursinha> :)
[15:33] <seb128> ok, so agenda topic on the wiki
[15:33] <seb128> but I want to review the specs for the cycle
[15:33] <seb128> so let's go through the team in IRC nick order (if I manage that right)
[15:33] <seb128> bryceh, hey, not sure if you are already around, if not I will catch up with you later
[15:34]  * Sweetshark will do a /nick bjoern when seb128 is past chrisccoulson  ...
[15:34] <chrisccoulson> pmsl
[15:34] <chrisccoulson> :-)
[15:34] <seb128> Sweetshark, nice try :p
[15:34] <mlankhorst> seb128: it might be worth for me to wait for the other x devs then
[15:34] <seb128> mlankhorst, yeah, I might try to catch you guys at a better time or use email
[15:35] <seb128> Sweetshark, hey bjoern :p
[15:35] <mlankhorst> ill go for the late night meeting today then
[15:35] <seb128> you won the right to be second (first)
[15:35] <seb128> mlankhorst, ok
[15:35] <seb128> Sweetshark, I've those blueprints for you on my list
[15:35] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-libreoffice-packaging
[15:35] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-libreoffice-qa-testsuites
[15:35] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-libreoffice-split
[15:35] <seb128> which counts 18 workitems
[15:35] <seb128> Sweetshark, is that correct? anything missing?
[15:36] <seb128> it seems like reasonable workload for the cycle since you have lo to maintain as well
[15:36] <Sweetshark> plus https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-libreoffice-lo-menubar-polish while is still hanging between things ...
[15:36] <seb128> Sweetshark, what is the schedule for the next libreoffice versions? what version will we get in quantal? do you plan to backport stable updates as well?
[15:37] <Sweetshark> 3.6.X will go in quantal
[15:37] <Sweetshark> http://wiki.documentfoundation.org/ReleasePlan/3.6
[15:37] <seb128> Sweetshark, should you have workitems about that?
[15:38] <seb128> or are you fine just tracking it as normal work on the side?
[15:38] <Sweetshark> precise will get 3.5.X SRUs
[15:38] <mlankhorst> the hardware doesn't seem to have changed much, just the software with lumia :S
[15:39] <Sweetshark> I count that as normal work on the side, as since 3.5 we lost libreoffice-build/go-oo, which makes updates less of a pain.
[15:39] <seb128> ok, great
[15:39] <Sweetshark> the overhead for tweaking with workitems is not worth it anymore now.
[15:39] <seb128> Sweetshark, I've added https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-libreoffice-lo-menubar-polish to the q list
[15:39] <seb128> Sweetshark, can you draft it or check with ted when he will?
[15:40] <seb128> it seems mostly ready, just adding a goal and test plans maybe and setting the definition to "review"
[15:40] <seb128> thanks ;-)
[15:40] <seb128> let's get moving so we are not there for hours
[15:40] <seb128> chrisccoulson, hey
[15:40] <Sweetshark> seb128: Im in email contact with tedg and olli r. about that one (and desrt for the fun part).
[15:40] <chrisccoulson> hi!
[15:40] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-mozilla-upgrade-experience
[15:40] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-calendar-integration
[15:40] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-firefox-translations-in-launchpad
[15:40] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/other-desktop-n-firefox-pgo-builds
[15:40] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-thunderbird-enhancements
[15:41] <seb128> 21 work items
[15:41] <chrisccoulson> that's more than i thought ;
[15:41] <seb128> chrisccoulson, does that seem about right? added to the "normal" day to day firefox,tb fun
[15:41] <chrisccoulson> yeah, i think so. some of those are trivial or low priority too
[15:41] <seb128> chrisccoulson, want to get some dropped? which ones? I let the calendar one there because it's only 1 wi but I think realistically we can drop that
[15:42] <chrisccoulson> yeah, i hadn't thought about calendar at all :)
[15:42] <seb128> chrisccoulson, the tb enhancements have an evo importer, I wonder if that's still useful at the lts
[15:42] <chrisccoulson> maybe not
[15:42] <seb128> chrisccoulson, I will drop the calendar, that doesn't need to be tracked
[15:42] <chrisccoulson> cool, thanks
[15:42] <seb128> chrisccoulson, is the firefox translation on lp work still something you want to work on?
[15:42] <chrisccoulson> yeah, but that's something that will happen in my spare time really
[15:43] <chrisccoulson> there's quite a lot of work in the tb-enhancements spec
[15:43] <seb128> do you want it to be tracked as a goal for the cycle?
[15:43] <seb128> I suggest we drop the l10n from our roadmap if that seems like spare time work
[15:43] <chrisccoulson> i don't mind either way :)
[15:43] <seb128> ok, let's keep it for now, we will revisit on time
[15:43] <chrisccoulson> thanks
[15:44] <seb128> is there any spec missing from that list?
[15:44] <chrisccoulson> no, i think that's it
[15:44] <seb128> ok, great
[15:44] <seb128> chrisccoulson, thanks
[15:44] <seb128> cyphermox, hey
[15:44] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/full-proxy-support
[15:44] <seb128> 13 wi
[15:44] <cyphermox> seb128: hey!
[15:44] <seb128> that's what I have on my list, it seems like I'm missing some?
[15:45] <seb128> that's what https://blueprints.launchpad.net/~mathieu-tl/+specs?role=assignee has at least
[15:45] <seb128> cyphermox, oh, I see, your nm work is on a foundation spec
[15:45] <seb128> ok, makes sense then ;-)
[15:45] <cyphermox> right,
[15:45] <cyphermox> https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-graceful-failure
[15:45] <cyphermox> ah, yeah, just a second
[15:45] <cyphermox> https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-networking
[15:45] <seb128> right
[15:46] <cyphermox> https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-desktop-quality
[15:46] <seb128> and you got some of the desktop testing work as well
[15:46] <cyphermox> https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-third-party-driver-installation
[15:46] <seb128> cyphermox, right, I only list specs "assigned" there
[15:46] <seb128> ok
[15:46] <seb128> seems a reasonable workload for the cycle then
[15:46] <seb128> is there anything you plan to work on that is not speced?
[15:46] <cyphermox> that's what I have on my list; with a total of 18 work items
[15:46] <seb128> out of keeping nm uptodate?
[15:46] <cyphermox> not really
[15:47] <cyphermox> the rest is all in the specs, with the most notable in foundations-q-networking
[15:47] <seb128> I had 13 but status didn't have the proxy spec yet at the time it did the counts
[15:47] <cyphermox> (proxy support in NM)
[15:47] <seb128> ok, great
[15:47] <cyphermox> right
[15:47] <seb128> cyphermox, thanks
[15:47] <seb128> didrocks, hey
[15:47] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-upgrade-user-config
[15:47] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-keybindings-health-check
[15:47] <seb128> 18 wi
[15:47] <didrocks> hum
[15:47] <didrocks> there is more, like the oneconf one and the opengles
[15:47] <seb128> and I guess unity,dx cross team work as usual
[15:48] <didrocks> it was on status.ubuntu.com when I check at lunch time
[15:48] <seb128> oh, https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-one-conf
[15:48] <seb128> didrocks, yeah, the opengles is assigned to sam
[15:48] <didrocks> right, but I have some WI on it, that's why :)
[15:48] <seb128> I overlooked the oneconf since I was working from https://blueprints.launchpad.net/~didrocks/+specs?role=assignee and it has a bit of noise
[15:49] <didrocks> indeed, I can't close the older blueprints
[15:49] <seb128> didrocks, yeah, I'm listing only spec assigned to avoid pinging 5 people about the same specs for things like desktop testing ;-)
[15:49] <seb128> didrocks, ok, any other one I'm missing?
[15:49] <didrocks> no, that's the full list :)
[15:49] <seb128> great
[15:49] <seb128> didrocks, thanks
[15:50] <didrocks> not sure about the oneconf one that has been retargeted as it's depending on another team (server side), apart from that, I'm confident :)
[15:50] <seb128> right ;-)
[15:50] <seb128> kenvandine, hey
[15:50] <seb128> kenvandine:
[15:50] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-gwibber
[15:50] <seb128> 11 wi
[15:50] <kenvandine> yup
[15:51] <seb128> and of course dx,indicator, and whatever else they work on cross team work
[15:51] <seb128> I guess the dx side is going to keep you busy for a good part of the cycle
[15:51] <seb128> is there anything else we should track I overlooked?
[15:51] <kenvandine> yeah...
[15:51] <kenvandine> nope
[15:52] <seb128> ok
[15:52] <seb128> kenvandine, thanks
[15:52] <seb128> Laney, hey
[15:52] <seb128> I've https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-deprecate-language-selector for you
[15:52] <seb128> and helping on GNOME,reducing delta with Debian
[15:52] <seb128> seeing that you are part time that seems already plenty for the cycle ;-)
[15:52] <Laney> yeah, sounds about right :-)
[15:53] <Laney> I expect the WIs will be split/changed a bit as I just put what I could think of there
[15:53] <seb128> was there anything else you plan to work on, or that we should track?
[15:53] <seb128> right, I'm a bit unsure of what goes exactly in that spec
[15:53] <seb128> I guess it's one of those "we will know better after trying to current code"
[15:53] <Laney> yeah
[15:54] <seb128> i.e we will figure it on the way
[15:54] <seb128> Laney, thanks
[15:54] <Laney> I'm working on a script to report our patch load over upstream atm, and hope that something will come up from that
[15:54] <Laney> it'll be a per-package summary of the patches we have
[15:54] <seb128> ah, nice
[15:54] <seb128> make sure to mention it on the wiki in the weekly summaries when you get something working
[15:54] <Laney> sure
[15:55] <seb128> thanks
[15:55] <seb128> mlankhorst, hey
[15:55] <Laney> https://code.launchpad.net/~laney/+junk/patch-report atm
[15:55] <Laney> (doesn't do much)
[15:55] <mlankhorst> yes?
[15:55] <seb128> ok
[15:55] <seb128> mlankhorst, https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-xorg-lts-updates
[15:55] <seb128> that's your assigned spec
[15:55] <seb128> I guess you will have plenty of xorg work to keep you busy in any case
[15:56] <mlankhorst> true :-)
[15:56] <seb128> but as you mentioned before we might better discuss xorg plan another time with bryceh and RAOF
[15:56] <seb128> mlankhorst, is there anything else you wanted to mention?
[15:56] <mlankhorst> not at this point in time, plenty of things to work on :-)
[15:57] <seb128> mlankhorst, thanks
[15:57] <seb128> mterry, hey
[15:58] <mterry> Present!
[15:58] <seb128> mterry, did you manage to avoid the flu?
[15:58] <mterry> seb128, yeah, I recommend my strategy of getting sick BEFORE UDS to everyone
[15:58] <seb128> hehe
[15:58] <seb128> note: if you do that, please don't bring the flu leftover at UDS ;-)
[15:58] <mlankhorst> so you can get 2x the sick leave?
[15:58] <seb128> mterry,
[15:58] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-update-manager
[15:58] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-deja-dup
[15:58] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-quickly
[15:58] <seb128> I've those on my list
[15:58] <mterry> Yup, that's right
[15:59] <mterry> Most of the work will be update-manage side I think
[15:59] <seb128> mterry, I noticed https://blueprints.launchpad.net/duplicity/+spec/python3  but that seems rather a "personal" spec for you?
[15:59] <seb128> mterry, I'm asking because it has proper workitems
[15:59] <mterry> Yeah.  Not sure how much I can get done on that one, don't want to track it for quantal yet
[15:59] <mterry> I guess that's an aspirational one rather than a promise  :)
[16:00] <seb128> ok
[16:00] <seb128> mterry, I also noticed  https://blueprints.launchpad.net/ubuntu/+spec/unity-greeter-q untracked
[16:00] <seb128> mterry, do you or robert_ancell have any greeter ui work plans for the cycle?
[16:01] <seb128> or was that design wishing for improvements but it has to find somebody wanting to work on those?
[16:01] <mterry> seb128, we do...  There was a meeting about it, so there must be a more proper blueprint
[16:01] <mterry> seb128, no I signed up for some greeter workitems
[16:01] <seb128> mterry, I failed to found one, I will track that offline with robert and you
[16:01] <mterry> seb128, I'll bug robert_ancell to enter them
[16:01] <seb128> mterry, I will drop you guys an email and you can reply
[16:02] <mterry> sure
[16:02] <seb128> mterry, anything else that I forgot?
[16:02] <mterry> seb128, I'm doing +1 maint, but that's not a workitem.  Not that I can think of
[16:02] <seb128> yeah, several of us will do that as well
[16:02] <seb128> i.e me after my lts.1 3 month
[16:02] <seb128> cyphermox and didrocks as well I think
[16:03] <seb128> mterry, thanks for reminding me about that, I almost forgot to take a month off for those work counts ;-)
[16:03] <seb128> mterry, thanks
[16:03] <seb128> tkamppeter, hey
[16:04] <seb128> tkamppeter, I didn't see any spec assigned to you for the cycle, I guess you will mostly be doing maintenance and bug fixing work?
[16:05] <seb128> ok, no tkamppeter I guess
[16:05] <seb128> did I forget anyone?
[16:06] <jbicha> hi, I had a couple comments
[16:06] <seb128> jbicha, hey!
[16:06] <seb128> sure
[16:06] <tkamppeter> seb128, yes
[16:07] <seb128> jbicha, wait a sec for tkamppeter's reply and it's your turn
[16:07] <tkamppeter> seb128, it is mainly bug fixing and SRUs, optimizing, maintenance, ...
[16:07] <seb128> tkamppeter, is there anything else we should be tracking printing wise?
[16:08] <tkamppeter> There is one thing, which larsu will do, he wants to make the printer setup tool in GNOME Settings feature-complete so that it can replace s-c-p.
[16:08] <seb128> tkamppeter, yeah, we will see how that goes, I discussed it was larsu a bit
[16:08] <seb128> tkamppeter, thanks
[16:09] <seb128> jbicha, your turn ;-)
[16:09] <tkamppeter> AFAIK he is not tracking it with a Blueprint, but there is a Blueprint from P, if needed I can ask larsu to use it.
[16:10] <jbicha> I've got Evolution 3.4 packaged (merged from Debian) and working. I patched out the broken window gconf conversions.
[16:10] <jbicha> EDS 3.4 can just be synced from Debian
[16:10] <jbicha> I don't know how we want to handle that transition?
[16:10] <seb128> jbicha, does it break anything runtime?
[16:10] <seb128> or just change sonames?
[16:11] <jbicha> I don't know; it touches a lot of packages http://paste.ubuntu.com/1001127/
[16:11] <seb128> tkamppeter, it's being tracked in https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-system-config-printer-vs-gnome-3-control-center
[16:12] <seb128> tkamppeter, I already discussed it with larsu so that's fine, you don't need to talk to him again about it, but thanks for the offer
[16:12] <tkamppeter> seb128, OK.
[16:13] <seb128> jbicha, let's discuss it at the end of the meeting, I don't think we need the full time for it
[16:13] <seb128>  
[16:13] <seb128> ok, I think I'm done
[16:13]  * jbicha hoped it *was* the end of the meeting
[16:13] <seb128> is there anything else to discuss? any topic you want to add?
[16:13] <seb128> jbicha, it might well be :p
[16:14] <jbicha> also, I made a seed for gnomebuntu but I can't figure out how to make an iso out of it
[16:14] <seb128> jbicha, I just want to officially end the meeting so people can go back to whatever they have to do ;-)
[16:14] <Laney> seb128: please could you add me to the LP team?
[16:14] <seb128> jbicha, you can maybe check with the xubuntu or lubuntu guys?
[16:14] <Laney> I don't show up on status.u.c and I think that's why
[16:14] <seb128> Laney, done
[16:14] <Laney> ty
[16:14] <seb128> yw
[16:14] <seb128> Laney, sorry for overlooking that
[16:14] <Laney> do I start getting loads of bug mail now? :P
[16:15] <seb128> Laney, no, typically between a few a day and a few a week, mostly bugs escalated to the team
[16:15] <Laney> ah ok, not package subscriptions then
[16:15] <jbicha> julien gave me https://code.launchpad.net/~lubuntu-desktop/+junk/lubuntu-tools but it's a bit out of date as lubuntu doesn't need it any more
[16:16] <seb128> Laney, every now and then a team meeting announce or similar when the launchpad "contact team" is used rather than sending direct email
[16:16] <seb128> Laney, no, we keep the traffic low on purpose ;-)
[16:16] <seb128> ok, seems like a wrap than
[16:16] <seb128> thanks everyone
[16:16] <seb128>  
[16:16] <seb128> END DESKTOP MEETING
[16:16] <seb128> ;-)
[16:16] <Laney> so, does anyone know anything about the new aisleriot?
[16:16] <seb128> jbicha, so
[16:17] <Laney> the bumped guile depends are causing me grief
[16:17] <seb128> Laney, what about it? we didn't take it previous cycle due to that depends
[16:17] <jbicha> Laney: I was thinking it's possible we might stay with aisleriot 3.2 for quantal actually, but we'll see...
[16:17] <Laney> that I guess we wouldn't want two guiles in main so things would need to be ported
[16:17] <Laney> which it seems is a difficult job
[16:18] <Laney> perhaps we should leave it at 3.2 ...
[16:18] <seb128> right
[16:18] <seb128> it's not like it would be a real issue to have card games a bit behind
[16:18] <Laney> yeah
[16:19] <seb128> jbicha, so, e-d-s ... do you know when Debian plans to start the transition?
[16:19] <jbicha> guile-2.0 FTBFS on arm anyway, maybe it's just broken tests but it's been that way a few months
[16:19]  * Laney said so on the pad.
[16:20] <jbicha> seb128: soonish, but I don't see a Debian transition tracker for it yet
[16:20] <Laney> did they request one already? The deadline has passed for transitions before the freeze afaik
[16:21] <seb128> jbicha, do you run that new version? is the calendar still working in indicator-datetime and gnome-shell?
[16:21] <seb128> jbicha, do you still have working contacts in thunderbird?
[16:21] <seb128> jbicha, is nautilus-sendto still working?
[16:22] <seb128> jbicha, if the reply to those 3 is "yes" feel free to upload ;-)
[16:23] <Laney> if you give me a .ben file I'll get it on our transition tracker
[16:23] <seb128> jbicha, ^
[16:23] <seb128> jbicha, can you do that?
[16:24] <jbicha> how do I make a .ben file?
[16:24] <Laney> get lp:~ubuntu-transition-trackers/+junk/transition-tracker and look at ubuntu/monitor for examples
[16:25] <Laney> actually you can probably start from http://release.debian.org/transitions/config/old/evolution2.32.ben
[16:25] <Laney> or http://release.debian.org/transitions/config/old/evolution3.2.ben
[16:35] <tkamppeter> mlankhorst, I have an X problem with Precise.
[16:36] <tkamppeter> mlankhorst, bug 999056
[16:36] <ubot2> Launchpad bug 999056 in xserver-xorg-video-intel "REGRESSION: 1920x1080 (standard HDTV) resolution with Intel graphics not working any more" [High,New] https://launchpad.net/bugs/999056
[16:37] <tkamppeter> My monitor has a 16:9 aspect ratio but X forces a 16:10 resolution onto it, making everything distorted.
[16:37] <tkamppeter> mlankhorst, ^^
[16:39] <mlankhorst> weird o.O
[16:40] <mlankhorst> tkamppeter: xrandr -q for giggles?
[16:40] <mlankhorst> also probably all the default crap like xorg log, dmesg etc
[16:42] <mlankhorst> also interesting to know if it works correctly in console and x changes resolution or not
[16:45] <highvoltage> ogra_: have / seen on of these yet? http://www.geek.com/articles/chips/via-launch-a-49-android-pc-20120522/
[16:45] <highvoltage> (actually let me switch that to the -arm channel)
[16:55] <tkamppeter> mlankhorst, in Oneiric it worked, it stopped working in Precise.
[16:55] <tkamppeter> mlankhorst, what is giggles
[16:55] <mlankhorst> fun
[16:56] <mlankhorst> tkamppeter: normally apport dumps a lot of state into a bug, though
[16:57] <mlankhorst> in any case intel loves to break every release in a new way :-)
[16:57] <tkamppeter> mlankhorst, xrandr -q posted, the bug was not a crasher, so no automatic Apport reporting.
[16:57] <tkamppeter> mlankhorst, how can I attach this info to the already reported bug?
[16:58] <mlankhorst> tkamppeter: what im wondering, if you're in console mode without starting X, is the resolution correct?
[17:00] <seb128> tkamppeter, you can open a bug using "apport-bug xorg"
[17:00] <seb128> tkamppeter, or "ubuntu-bug xorg"
[17:01] <seb128> tkamppeter, to add apport infos to a bug "apport-collect -p xorg NUMBUG"
[17:01] <tkamppeter> mlankhorst, I have apport-collected now.
[17:01] <tkamppeter> mlankhorst, I did not check console mode.
[17:04] <tkamppeter> mlankhorst, checked console mode now, there the resolution is correct: 1920x1080.
[17:07] <mlankhorst> tkamppeter: in that case you could probably limit yourself to bisecting the X driver ;-)
[17:09] <tkamppeter> mlankhorst, I have never bisected a program, perhaps bryceh or RAOF should have a look at this problem.
[17:11] <mlankhorst> tkamppeter: try to see if you can compile the oneiric version of xf86-intel precise, if it works you can confirm if that fixes the problem or not
[17:12] <mlankhorst> actually let me try :s
[17:13] <seb128> Sweetshark, once https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-libreoffice-lo-menubar-polish ... the BLOCKED are blocked on finding "implementors"?
[17:15] <tkamppeter> mlankhorst, perhaps you can reproduce the bug by connecting a TV to a computer with Intel graphics, as a TV has exactly this resolution.
[17:16] <dobey> if it's a 1080p tv anyway
[17:17] <dobey> ignore all those 720p and 768p things ;)
[17:17] <dobey> or CRTs
[17:17] <mlankhorst> tkamppeter: #intel-gfx is on this server though
[17:17] <seb128> chrisccoulson, lol @ENOTENOUGHCAFFEINE ;-)
[17:17] <chrisccoulson> :)
[17:18] <mlankhorst> #define ENOTENOUGHCAFFEINE EAGAIN ? :p
[17:18] <tkamppeter> mlankhorst, there is no xf86-intel package but an xserver-xorg-video-intel one. Is this the correct one?
[17:18] <mlankhorst> yeah
[17:21] <chrisccoulson> ok, armel is rapidly going to take the place of powerpc
[17:21] <mlankhorst> long live armhf?
[17:22]  * ogra_ wouldnt focus to much on armel atm 
[17:22] <ogra_> fix armhf though :)
[17:22] <ogra_> armel might or might not vanish soon
[17:23] <chrisccoulson> oh, the thunderbird build failure is actually my fault anyway. i forgot to include another change
[17:23] <chrisccoulson> never mind ;)
[17:23] <chrisccoulson> it can wait until next week now
[17:23] <seb128> chrisccoulson, what place? the one of the painful arch to work with? or the buggiest one? ;-)
[17:23] <chrisccoulson> seb128, the one i don't care about ;)
[17:23] <seb128> lol
[17:23] <seb128> join the club :p
[17:27]  * bcurtiswx waves to room
[17:28] <seb128> hey bcurtiswx
[17:28] <bcurtiswx> hey seb128 all recovered from UDS by now?
[17:28] <seb128> it seems we did!
[17:28] <bcurtiswx> great
[17:29] <tkamppeter> mlankhorst, I am building Oneiric's Intel driver now ...
[17:30] <bcurtiswx> seb128, i'll get kenvandine to sponsor a empathy  3.4.2.1 SRU sometime today or tomorrow
[17:30] <seb128> bcurtiswx, great, thanks
[17:32] <mlankhorst> tkamppeter: ah k, it is eod for me so im probably going to disappear at a random time :)
[17:33] <bcurtiswx> kenvandine, do I need to wait for 3.4.2 to get out of proposed before 3.4.2.1 can get pushed there?
[17:33] <tkamppeter> mlankhorst, OK, and thank you. More info I will post into the bug report.
[17:34] <bcurtiswx> kenvandine, nvm that
[17:45] <seb128> micahg, hey
[17:47] <bcurtiswx> using bzr merge-upstream --version 3.4.2.1 the file searched for seems wrong  http://ftp.gnome.org/pub/GNOME/sources/empathy/([0-9.]+)/empathy-(.*).tar.xz maybe the watch file specifies this wrong ?
[17:50] <tkamppeter> mlankhorst, I have got it working again.
[17:51] <mlankhorst> tkamppeter: ok so it's a bug in intel somewhere then
[17:52] <tkamppeter> mlankhorst, I had an old xorg.conf which defined only my old 1680x150 Samsung monitor which dies a year ago. Natty and Oneiric happily worked with my new Eizo with 1920x1080 and this file, Precise not. After removing the file and moving my .config away I got back to 1920x1080.
[17:52] <mlankhorst> oh :P
[17:52] <mlankhorst> user error
[17:52] <mlankhorst> please replace user and continue
[17:54] <mlankhorst> marked invalid, have a good day
[17:54] <mlankhorst> :-)
[17:56] <mlankhorst> I added the info to the bug in case anyone finds it on google or something and acts like 'hey this is what happens here'
[17:59] <tkamppeter> mlankhorst, thanks for your help.
[18:19] <chrisccoulson> ah, this builder is much faster. 1 hour in, and it's already done the first build - https://launchpad.net/ubuntu/+source/firefox/13.0~b4+build1-0ubuntu4/+build/3509571 :)
[18:19] <mlankhorst> an hour for firefox ? :O
[18:20] <chrisccoulson> well, it's got to do the build again yet, and run the testsuite too
[18:26] <mlankhorst> ok started build for fun :x
[18:27] <chrisccoulson> building?
[18:27] <mlankhorst> i wanted to see how long it would take locally to build
[18:27] <chrisccoulson> which version are you building, and how much ram have you got?
[18:28] <mlankhorst> the one you uploaded, 16gb
[18:28] <chrisccoulson> ah, that's ok
[18:28] <mlankhorst> enough to build chromium in ram if i force dynamic linking
[18:30]  * dobey wishes he could find someone who is actually hitting this supposed super popular "crasher"
[18:34] <chrisccoulson> right, i'm going to disappear for a whilte
[18:36] <mlankhorst> do I need to pass a flag to force parallel building?
[20:53] <chrisccoulson> i'm glad my update to quantal went well
[20:56] <bcurtiswx> off for the evening, see everyone tomorrow
[21:06] <MrChrisDruif> chrisccoulson; ah, you've joined the club?
[22:33] <TheMuso> /c/c
[22:57] <jasoncwarner_> TheMuso RAOF bryceh robert_ancell https://wiki.ubuntu.com/DesktopTeam/Meeting/2012-05-22
[22:57] <jasoncwarner_> can you guys please put in your items for the week as well as any agenda items.
[22:57] <jasoncwarner_> TheMuso RAOF bryceh and robert_ancell, also, how are you blueprints coming along? any that we need to talk about?
[22:58] <robert_ancell> nothing from me
[22:59] <RAOF> I'd like to talk with robert_ancell, but nothing otherwise from me.
[22:59]  * robert_ancell hides
[22:59]  * RAOF needs to remember that robert_ancell is slighty in the future now.
[23:00] <TheMuso> jasoncwarner_: Just the blueprint that I created for tracking unity 3D a11y work: https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-unity-a11y
[23:00] <jasoncwarner_> thanks TheMuso
[23:01] <TheMuso> np
[23:09]  * bryceh waves
[23:10] <bryceh> RAOF, mlankhorst and I were thinking the three of us should meet tomorrow (first thing your morning) about LTS point update stuff.
[23:11] <RAOF> bryceh: Ho!
[23:11] <RAOF> I can do that.
[23:11] <RAOF> I saw 2100 UTC?
[23:11] <bryceh> yeah, is that doable?
[23:11] <bryceh> later than that and I guess mlankhorst zombifies
[23:12] <RAOF> Yeah, that's doable.
[23:14] <bryceh> nothing else from me; just upgrading hardware and knocking off work items this week
[23:17] <bryceh> RAOF, how's wayland going?
[23:17] <RAOF> I got it bringing up xwayland on nouveau on yesterday.
[23:17] <RAOF> Now I just need to finish off the bits that'll let the same nouveau driver work on xwayland and raw.
[23:17] <bryceh> nice, did it stay up?  ;-)
[23:18] <RAOF> Yeah. Graphical corruption, but I think that's actually a weston problem rather than anything to do with my patches :)
[23:19] <bryceh> RAOF, also wanted to ask if you had a chance to draft up the git cherrypicking techniques you were showing mlankhorst?
[23:19] <RAOF> Not yet.
[23:20] <RAOF> Well, I have had a chance, I just haven't used that chance to *do* it.
[23:20] <bryceh> hehe :-)
[23:20] <RAOF> Today is SRU day. I'll do it after that.
[23:22] <bryceh> speaking of srus, were there any fruitful picks from -intel that you and mlankhorst were looking at last week?  You'd mentioned there was a lack of associated bug reports to hook SRUs onto.
[23:27] <RAOF> Basically all the uxa commits since 2.17 would be worthwhile.
[23:27] <RAOF> There are only 5 or so of them, once you extract the ones related to glamour.
[23:28] <bryceh> RAOF, do you have further plans with that?  If not, stick it in a git tree and I might poke through them when I get some spare time
[23:28] <RAOF> I was kinda waiting for Debian to grab 2.19 to send to quantal, as that's the only release with the commits we want.
[23:29] <bryceh> ah, ok
[23:54] <robert_ancell> RAOF, you wanted to talk?
[23:54] <RAOF> robert_ancell: Yeah, I just wanted to work out what ordering will make us both maximally productive wrt system compositor work.
[23:56] <robert_ancell> RAOF, so I think what I need is to know what to call to start the system compositor (process name and environment) and what to call to start the X servers (process name and environment)
[23:57] <RAOF> And some protocol for communicating with the system compostior, right?
[23:57] <robert_ancell> RAOF, yes, just the switching protocol for now
[23:58] <robert_ancell> If we document that, I can implement that in lightdm and get some regression tests for it
[23:59] <RAOF> It looks like this can be done in weston, so you'll be calling something along the lines of ‘/usr/bin/weston --system-compositor’; starting X will be the same as you currently do, but with an added -wayland flag.