[00:47] <chrisccoulson> grrrrr, one of my stupid cats just woke my daughter
[01:00] <TheMuso> Thats not good.,
[01:12] <highvoltage> chrisccoulson: why do you have stupid cats!?
[01:37] <RAOF> Why is it so cold!  Brrr!
[01:37] <highvoltage> because we're so close to the north pole?
[01:40] <cyphermox> highvoltage, yeah :/
[01:52] <TheMuso> RAOF: the joys of Tassy. Its certainly cooler than usual in Sydney today too.
[01:53] <RAOF> Yup :)
[05:36] <micahg> robert_ancell: hi, I remember you were discussing replacing tsclient with remmina earlier in the cycle, is that still planned?
[05:36] <robert_ancell> micahg, well, it's being blocked by your team :P
[05:36] <micahg> robert_ancell: ok, I can bring it up with the team then, is the discussion in the MIR?
[05:36] <robert_ancell> there's some certificate handling code that needs patching, but I don't know enough about it
[05:37] <robert_ancell> (but I believe it's probably just as weak as rdesktop, so it's probably not an increased security risk)
[05:38] <robert_ancell> micahg, bug #673925
[05:38] <ubot2> Launchpad bug 673925 in freerdp "[MIR] freerdp" [Undecided,Incomplete] https://launchpad.net/bugs/673925
[05:39] <RAOF> Who'd like to sponsor a wacom upload to fix a rather annoying SEGV on X server startup?
[05:39] <micahg> robert_ancell: ah, yeah, that's bad :(, you mentioned working with upstream, did they say anything?
[05:40] <robert_ancell> it's not going to be fixed on their side before natty, I started work on a patch which I sent to them for review, no response
[05:40] <robert_ancell> but I don't have a lot of experience with these crypto api's, and they're a little hard to work with :)
[05:43] <micahg> robert_ancell: sorry, I wish I could help, but this is something I haven't gotten into yet
[05:44] <robert_ancell> I've updated the bug with some more info
[06:56] <pitti> Good morning
[06:58] <TheMuso> Hey pitti.
[07:02] <pitti> hey TheMuso, how are you?
[07:11] <TheMuso> pitti: Well thanks, yourself?
[07:11] <pitti> pretty good, thanks!
[07:23] <bryceh> heya pitti
[07:26] <pitti> hey bryceh
[07:26] <pitti> bryceh: sorry for all the trouble with the bad X.org crashes
[07:26] <bryceh> pitti, no prob, thanks for tending to it.
[07:27] <bryceh> fortunately there seems to be just a few crashers in xserver, so the possibility exists we might be able to eliminate them all
[07:28] <bryceh> that'll be  a first for a release :-)
[07:28] <bryceh> pitti, in other news... wayland!
[07:28] <bryceh> pitti, do you/(can you?) do new package approvals for universe?
[07:28] <pitti> bryceh: ... just at the point where you got X.org crash free :)
[07:29] <bryceh> heh, job security!
[07:29] <pitti> bryceh: "can" yes, "do" not very often any more
[07:30] <bryceh> pitti, today I finally got the last bits squared away for wayland, and uploaded it to universe, and I'm hoping it'll get in by FF.
[07:30] <bryceh> pitti, with all the latest mesa/libdrm/cairo/etc. changes, now all of wayland's dependencies are in the repository
[07:31] <bryceh> and it even runs... there is a 'wstart' script which launches the compositor in your X environment, with a variety of demo programs
[07:31] <bryceh> (tested on -intel and -radeon, but not -nouveau yet)
[07:32] <pitti> wow, great work! looking forward to play with it
[07:32] <pitti> bryceh: btw, all packages which land in NEW before FF will be considered (i. e. you don't get penalized for archive admin delays)
[07:33] <bryceh> pitti, ahh, whew
[08:03] <didrocks> good morning
[08:04] <pitti> hey didrocks
[08:05] <didrocks> Guten Morgen pitti
[08:08] <pitti> I'm off for some 3 hours for some errands
[08:12] <didrocks> pitti: see you
[09:13] <glatzor> mvo, huhu
[09:13]  * glatzor hugs mvo
[09:14] <glatzor> I merged a slightly modified version of your path in rev 586 of aptdaemon
[09:15] <chrisccoulson> good morning everyone
[09:18] <chrisccoulson> ha - http://canweshipyet.com/
[09:18] <chrisccoulson> that's a pretty good summary
[09:22] <rodrigo_> morning
[09:46] <didrocks> good morning chrisccoulson, rodrigo_
[09:48] <rodrigo_> hi didrocks
[09:52] <chrisccoulson> hi didrocks, how are you?
[09:52] <didrocks> I'm fine, thanks, you? :)
[10:11] <duanedesign> hello didrocks rodrigo_ . Hope you all are well
[10:11] <didrocks> hey duanedesign, how are you?
[10:19] <duanedesign> didrocks: i am good thank you. Trying to get a few packages ready for Debian.
[10:19] <didrocks> duanedesign: excellent :)
[10:20] <duanedesign> thankfully I have a few people interested in helping on a couple projects. :) Was starting to get overwhelmed. Have not had a change to touch Stipple since...probablly around UDS-N
[10:24] <didrocks> similar here for oneconf :( just updated to new USC API
[10:26] <jibel> rodrigo_, Hi, I'm able to easily reproduce bug 718098, with libgdk-pixbuf2.0-0 2.23.0-1ubuntu1 installed. Aren't you ?
[10:26] <ubot2> Launchpad bug 718098 in nautilus "nautilus crashed with SIGSEGV in g_str_hash()" [Medium,In progress] https://launchpad.net/bugs/718098
[10:26] <jibel> rodrigo_, the easiest way is to install the current iso, which is affected by this issue.
[10:27] <tjaalton> banshee seems broken on natty atm. refuses to play anything
[10:27] <tjaalton> oh filed already
[10:35] <rodrigo_> jibel: no, I'm not
[10:36] <jibel> rodrigo_, do you get bug 719861 on the system you're trying to reproduce ?
[10:36] <ubot2> Launchpad bug 719861 in gdk-pixbuf "After installation icon theme default to gnome-icon-theme and cannot be changed" [High,Fix released] https://launchpad.net/bugs/719861
[10:36] <rodrigo_> jibel: no, neither, that was already fixed iirc
[10:37] <rodrigo_> jibel: are you up to date?
[10:37] <jibel> rodrigo_, yes, today's iso
[10:37] <rodrigo_> hmm
[10:37] <rodrigo_> I'm writing a patch to avoid the crash, although haven't found the real cause, so I'm just adding a check for not calling g_str_hash with NULL
[10:38] <jibel> rodrigo_, build failed on all arch for gdk-pixbuf, that's probably why it's released but not on the iso
[10:38] <rodrigo_> hmm, yes
[10:54] <Riddell> jasoncwarner: ping
[10:56] <seb128> rodrigo_, you don't get the crash even if you screw the svg loader?
[10:57] <seb128> jibel_, right, gdk-pixbuf failed to build due to some gir things, I've pinged pitti and kenvandine last week about it but since they didn't have time for it yet
[10:57] <seb128> we need to get svg support fixed for a3, I will try to fix it again this week if they don't
[11:00] <jibel_> seb128, okay, thanks.
[11:12] <pitti> re
[11:12] <rodrigo_> seb128, right, no crash at all
[11:12] <seb128> rodrigo_, weird
[11:12] <pitti> seb128: gdk-pixbuf FTBFS? hm, I'm not aware of that, but I can have a look
[11:12] <rodrigo_> seb128, I'm writing a patch to avoid calling g_str_hash with NULL though
[11:13] <seb128> pitti, we discussed it briefly on wednesday evening
[11:13] <rodrigo_> seb128, although that's not the real cause, just a symptom
[11:13] <seb128> pitti, but it was just before your w.e and I had to run
[11:13] <seb128> rodrigo_, ok
[11:13] <pitti> seb128: ah, seems I forgot then, sorry
[11:13] <seb128> rodrigo_, you get no theme set and you can't open svg files right?
[11:13] <seb128> pitti, no worry
[11:13] <rodrigo_> seb128, right, and lots of missing icons
[11:14] <rodrigo_> but no crash
[11:14] <rodrigo_> seb128, do you get it with all the latest updates?
[11:14] <seb128> rodrigo_, you nautilus /usr/share/applications and close the dialog?
[11:14] <rodrigo_> seb128, yes
[11:14] <seb128> did you restart your session or nautilus with the broken librsvg?
[11:14] <seb128> well broken loader index
[11:15] <pitti> seb128: opened a tab for it now, will queue it after my current bug fxi
[11:15] <pitti> oh, and sending the meeting reminder :)
[11:15] <seb128> rodrigo_, I didn't try this week but I don't really see what could have fixed it and it seems jibel_ still get it
[11:15] <seb128> pitti, danke
[11:15] <seb128> pitti, oh right I was about to remind you about the reminder :p
[11:16] <pitti> seb128: speaking of meetings, was there any action etc. for us in Friday's release meeting?
[11:16] <seb128> pitti, no
[11:16] <rodrigo_> hmm, what crashes all the time is metacity, when I remove the svg loader
[11:16] <pitti> seb128: thanks for covering
[11:16] <seb128> pitti, no question, no action either
[11:16] <seb128> you're welcome
[11:16] <pitti> "business as usual" then :)
[11:16] <seb128> rodrigo_, didn't try with it since compiz is the default and is working on this box
[11:17] <pitti> didrocks: btw, is that only my configuration, or do the fonts in the unity panel look fuzzy everywhere?
[11:17] <seb128> rodrigo_, well don't bother then if you don't get the crash, it's weird, it seemed like nautilus was getting confused because it's failing to load some of the icons to display
[11:17] <pitti> didrocks: btw, great to see proper theme support now! I finally have a bright panel again with dark text \o/
[11:18] <didrocks> pitti: hum, in the panel No, it should juste use the ubuntu font
[11:18] <seb128> like it's not handling well the case where icons loading is failing
[11:18] <pitti> didrocks: ok, will investigate later then, thanks
[11:18] <didrocks> pitti: yeah, the launcher should be coming once we have a sign of design :)
[11:18] <seb128> pitti, screenshot?
[11:18] <seb128> didrocks, launcher what? themable?
[11:18] <didrocks> seb128: just choose the "radiance" theme
[11:18] <rodrigo_> seb128, yes, but submitting that patch anyway, at least it won't crash until we find the real issue
[11:18] <didrocks> well, it's limited to ambiance and radiance only
[11:19] <seb128> rodrigo_, thanks
[11:19] <seb128> didrocks, heh, I do use the light theme since ever
[11:19] <seb128> screenshot was for the fuzy issue, I don't think I have it but I want to see what pitti is speaking about before saying that
[11:19] <pitti> seb128: doing, hang on
[11:20] <seb128> but I've to admit I liked the non themed version better
[11:20] <seb128> it looks a bit weird now
[11:20] <pitti> http://people.canonical.com/~pitti/tmp/fuzzy-panel.png
[11:21] <seb128> it doesn't fit with the launcher (which was part of my "launcher?" question to know if the launcher will change as well) and I find the junction unity-panel to application not as clear
[11:21] <pitti> seb128, didrocks ^
[11:21] <didrocks> seb128: yeah, the "launcher" is still pending design to ack
[11:21] <pitti> text in the menus is fine
[11:21] <seb128> I think I would be fine if the launcher was forcing the old style with the right icons and let me use a different theme for my applications
[11:21] <pitti> but the "martin", time, and top level menus are fuzzy, looks like not aliased
[11:22] <pitti> reading them makes you feel a bit dizzy
[11:22] <didrocks> pitti: I have this on other monitor which doesn't have the same resolution, hard to compare :)
[11:22] <pitti> I'll file a bug later on then
[11:22] <didrocks> but yeah, maybe you're right, I'll let dx know
[11:22] <seb128> pitti, right, same issue there
[11:22] <pitti> I believe that came with the themed change
[11:23] <pitti> I don't remember it being fuzzy before, but then again that was bright on dark and looked different
[11:23] <seb128> easy to see if run an application with UBUNTU_MENUPROXY set and compare the panel and application menus
[11:23] <seb128> without rather
[11:23] <seb128> pitti, right
[11:24] <didrocks> seb128: hum? pitti is telling that text in the appmenu is fine
[11:24] <seb128> didrocks, no, he says the menu content is fine
[11:24] <pitti> didrocks: in the submenus, not in the top-level names in the panel
[11:24] <seb128> not the menu bar
[11:24] <pitti> didrocks: see the screenshot
[11:24] <didrocks> oh ok, the top-level menu
[11:24] <pitti> "Datei" is fuzzy, the "Neu" entry looks fine
[11:24] <seb128> see the difference between the text in the unity-panel and the text in the open menu
[11:24] <didrocks> yeah, I see it now
[11:25] <didrocks> hum, should be a nux issue IMHO
[11:25] <pitti> I guess it's not using the standard GNOME font rendering with aliasing?
[11:25] <didrocks> more the prossible :)
[11:25] <seb128> didrocks, nux is used for the indicators rendering?
[11:26] <didrocks> seb128: right, all is rendered by nux as nux widgets
[11:26] <seb128> it's weird they don't use gtk directly
[11:26] <seb128> didrocks, just curious but what advantage is nux giving the label rendering in that context?
[11:27] <seb128> it seems something where plain gtk should be just fine
[11:28] <didrocks> seb128: well, all having as nux widgets enables padding and layout in a sane way (as some widgets have to be wrapped by nux)
[11:29] <seb128> didrocks, it's weird, unity-panel-service doesn't use nux it seems
[11:29] <didrocks> then, nux should be using gtk maybe, but as it wants to be platform independent…
[11:29] <seb128> ldd on the binary doesn't list nux
[11:29] <didrocks> seb128: the service doesn't render
[11:29] <didrocks> seb128: the service is a proxy which tell "you need this, that and that"
[11:29] <seb128> I guess I don't understand how the unity-panel is working ;-)
[11:29] <didrocks> very easy
[11:29] <didrocks> unity-panel is part of the unity process
[11:30] <didrocks> then, the unity-panel-service talks to the unity panel, telling it what it should draw
[11:30] <seb128> so the service has all the loading and information dispatching and unity does the rendering?
[11:30] <didrocks> (the "what" beeing strings and data)
[11:30] <didrocks> right
[11:30] <didrocks> all that over dbus
[11:30] <didrocks> so, for the indicators, you basically have:
[11:31] <didrocks> indicator service <-> unit-panel-service <-> unity (compiz)
[11:31] <didrocks> with <-> being dbus protocol
[11:31] <seb128> I know the indicator to service part of the deal
[11:31] <seb128> I've been mostly looking at the indicator stack so far
[11:31] <seb128> I didn't realize the unity-panel rendering was done by unity itself though
[11:31] <seb128> learning every day ;-)
[11:31] <didrocks> right, just telling that for a menu, we have two dbus passerels
[11:32] <didrocks> all the rendering is done by unity, whatever it is
[11:32] <seb128> I guess they have their reasons
[11:33] <didrocks> less X connections is one of them I think (and don't destroying/redrawing the panel on indicator crash is another)
[11:33] <seb128> well I guess it's rather for the things like wm control integration
[11:33] <seb128> because otherwise for the few rendering the unity-panel has to do it would have been easier to do a separate binary
[11:33] <seb128> it would have reduced the potential for indicator to bring unity down or to leak memory etc
[11:34] <didrocks> indicator don't bring unity down, just the service
[11:34] <didrocks> so, unity just "don't refresh" the panel until the service respawn
[11:35] <seb128> right, that's because they redesigned it this way to avoid the issue they had last cycle :p
[11:35] <didrocks> exactly :)
[11:47] <pitti> didrocks: do you know what happened with /desktop/gnome/session/required_components ?
[11:48] <pitti> it doesn't have nautilus any more -- how do I remove nautilus from autostarting now?
[11:48] <pitti> (I need to run it from a local build tree)
[11:48] <seb128> pitti, /usr/share/gnome-session/
[11:48] <seb128> pitti, the sessions are in the sessions directory there
[11:48] <pitti> ah, thanks; learned something new
[11:48] <didrocks> /usr/share/gnome-session/sessions now
[11:49] <pitti> I suppose changing that requires a session restart?
[11:49] <seb128> the /usr/share/xsessions sessions start gnome-session --session=
[11:49] <seb128> which load the corresponding profile in that directory
[11:49] <didrocks> pitti: yeah, it needs a session restart
[11:49] <pitti> there is no per-user override for that any more then?
[11:49] <didrocks> pitti: no
[11:49] <seb128> pitti, yes, was already the case with the gconf key
[11:49] <seb128> yes -> restart
[11:51]  * pitti uses good old sudo mv /usr/bin/nautilus{,.disabled} then
[11:51] <seb128> don't kill nautilus if you do that
[11:51] <seb128> gnome-session tends to crash when you do that
[11:51] <seb128> it tries to respawn it since it's in the session and doesn't like failing to it
[11:51] <pitti> it seems to survive fine right now, I can start/stop it from my build tree now
[11:51] <seb128> ok, last time I tried gnome-session crashed
[11:59]  * Sweetshark builds libreoffice-3.3.1~rc2-1ubuntu1~ppa1 which has good chances to become the unchanged final (and includes the humanity icons)
[11:59] <pitti> whee!
[12:01] <Sweetshark> :_(
[12:02]  * Sweetshark just realizes he builds the human style, but does not package it.
[12:18] <ricotz> seb128, hello
[12:18] <Sweetshark> ... and here we go again (this time with packaging hopefully) ...
[12:24] <seb128> ricotz, hey
[12:29] <Sweetshark> pitti: ping?
[12:29] <pitti> hey Sweetshark
[12:32] <Sweetshark> could you help me along with MIRing ttf-sil-gentium-basic and ttf-sil-gentium as they are recommends for libreoffice
[12:33] <Sweetshark> thats bug 711512
[12:33] <ubot2> Launchpad bug 711512 in libreoffice "[natty] libreoffice uninstallable: depends on ttf-sil-gentium-basic from universe" [High,Triaged] https://launchpad.net/bugs/711512
[12:33] <pitti> Sweetshark: oh, sure; I believe ttf-sil-gentium was in main before, and -basic should be easy (sounds like a splitout)
[12:33] <pitti> ttf-sil-gentium | 1.02+dfsg-4 |         hardy | source, all
[12:33] <pitti> right
[12:34] <pitti> Sweetshark: so, I'll re-promote that one
[12:34] <pitti> Sweetshark: I suggest that you reassign above bug to ttf-sil-gentium-basic
[12:35] <pitti> Sweetshark: https://wiki.ubuntu.com/MainInclusionProcess describes the full process, FYI
[12:35] <nessita> hello everyone. Is there any chance to get an sponsorship for a new package? package branch is https://code.launchpad.net/~nataliabidart/ubuntuone-file-storage-api/ubuntuone-file-storage-api-0.0.1
[12:35] <Sweetshark> pitti: you mean the "affects" field?
[12:35] <pitti> Sweetshark: so in essence you'd subscribe ubuntu-mir to the bug and change title/description accordingly; you need to provide the rationale ("recommended by libreoffice")
[12:36] <pitti> Sweetshark: expand the "natty" task, there you can modify the affected source package
[12:36] <pitti> Sweetshark: it's not a bug in libreoffice
[12:38] <seb128> hey nessita
[12:38] <seb128> nessita, how are you?
[12:38] <pitti> hey nessita
[12:38] <seb128> nessita, subscribe ubuntu-sponsors if you didn't yet so it's on the sponsoring list, I will try to review it later on if nobody picked it up before
[12:38] <nessita> hey seb128, pitti! how are you?
[12:39] <seb128> nessita, I'm fine thanks
[12:39] <seb128> nessita, urg, "Sorry, you don't have permission to access this page. "
[12:39] <pitti> Sweetshark: you can already check some of the MIR requirements for getting a feel for it, but the MIR team will do the packaging checks (as you aren't that experienced with Debian packaging yet)
[12:39] <seb128> nessita, is that a private project or something?
[12:39] <nessita> seb128: makes sense, I didn't realize I could subscribe people to a branch (instead to a merge prop)
[12:40] <pitti> same here
[12:40] <seb128> nessita, well you can ask review from ubuntu-sponsors
[12:40] <nessita> seb128: is not, but somehow LP makes all u1 branches private. Thanks for noticing this, I'll ask a l.o.s.a to make it public
[12:40] <seb128> thanks
[12:40] <nessita> seb128: but, proposing merge against what target, if the package project does not exist?
[12:41] <seb128> hum right, for a new source better to open a bug and subscribe ubuntu-sponsors
[12:42] <Sweetshark> pitti: eh, the title is misleading. I need ttf-... in main as libreoffice is too, right?
[12:42] <pitti> Sweetshark: correct; the standard title is "[MIR] ttf-sil-gentium-basic"
[12:44] <rodrigo_> seb128, https://code.edge.launchpad.net/~rodrigo-moya/ubuntu/natty/nautilus/fix-718098/+merge/50734
[12:44] <rodrigo_> seb128, at least with that it shouldn't crash
[12:44] <seb128> rodrigo_, thanks
[12:44] <rodrigo_> although not much happy about the fix, it's just fixing a symptom, not the real cause
[12:45] <Sweetshark> pitti: do I keep myself in "assigned to" or who should go in there?
[12:46] <seb128> rodrigo_, do you plan to forward the patch upstream as well?
[12:46] <rodrigo_> seb128, not this one, will do as soon as I know the real cause
[12:47] <seb128> rodrigo_, did you try under compiz? not sure why it would make any difference but several users reported having it when clicking on the ubuntu logo under unity and closing it
[12:47] <czajkowski> 12:45 < Pendulum> hey, can anyone here RT this, I don't have many followers and I'm hoping we get some good feedback http://twitter.com/#!/colona13/status/40020405666189312  :)
[12:47] <czajkowski> Can folks help out please :D
[12:47] <seb128> which basically runs nautilus on /usr/share/applications
[12:48] <rodrigo_> seb128, yes, also tried it there, no crash neither
[12:48] <rodrigo_> but yes, seems to be related to using unity
[12:48] <seb128> czajkowski, "rt this"?
[12:48] <seb128> czajkowski, is there something technically that should be done, like is that blocked on some infrastructure changes which are defined?
[12:49] <czajkowski> Pendulum: ^^
[12:49] <seb128> rodrigo_, hum, I'm pretty sure I got it using a daily iso in kvm without d
[12:49] <seb128> 3d
[12:49] <seb128> rodrigo_, in a classic session just running nautilus /usr/share/applications and closing it
[12:49] <rodrigo_> seb128, removing the svg loader, right?
[12:49] <czajkowski> seb128: the idea would be to get more people to the meeting to encourage and examine how we can get more people to UDS as some have conceners about venue and taking part.
[12:49] <seb128> it might that I didn't even wait for it to have loaded the dir
[12:49] <ricotz> seb128, sorry, was away, do you mind looking at my gtk+3.0 3.0.1 merge?
[12:50] <seb128> rodrigo_, the fixed gdk-pixbuf didn't land, daily isos still have the svg loader not registered
[12:50] <Pendulum> seb128: announcement of meeting about making UDS more accessible
[12:50] <rodrigo_> seb128, hmm, ok, I tried with a maverick->natty update, so I guess that got the fix?
[12:50] <seb128> Pendulum, we can do that, it doesn't require a rt though
[12:50] <rodrigo_> although I also tried removing the svg loader
[12:50] <czajkowski> seb128: well some people don't know what to say unless they RT it
[12:51] <seb128> jcastro, can you get http://twitter.com/#!/colona13/status/40020405666189312 advertized on planet etc?
[12:51] <seb128> czajkowski, Pendulum: ^
[12:51] <Pendulum> seb128: I was asking people to pass the word
[12:51] <czajkowski> seb128: where Rt is not logging a RT ticket but retweeting it
[12:51] <Pendulum> there's a blog post on planet about it already :)
[12:51] <seb128> ok, gotcha
[12:51] <seb128> well doesn't hurt to ping jcastro
[12:51] <Pendulum> nope
[12:51] <seb128> the community team is good about letting other know about meetings etc ;-)
[12:52] <Pendulum> yeah
[12:52] <Pendulum> I asked in the community team channel
[12:52] <seb128> rodrigo_, right, that would work
[12:52] <nessita> seb128: thanks, I'll open the bug and link the branch (I'll re push to +junk since l.o.s.a.s are sprinting)
[12:52] <seb128> rodrigo_, the issue is that the cache refresh is not run on first installation
[12:52] <seb128> nessita, ok
[12:53] <rodrigo_> seb128, hmm
[12:53] <seb128> rodrigo_, editing the file in /usr/lib/gdk-pixbuf-2.0/2.10.0 to drop the svg reference should be the same though
[12:54] <rodrigo_> yes
[12:54] <seb128> it leads to have stock GNOME icons in the session and eog refusing to open svg images
[12:56] <seb128> rodrigo_, did you try on natty or on a box with GNOME3?
[12:56] <rodrigo_> seb128, on a vm with natty, upgraded from a maverick iso
[12:57] <rodrigo_> no gnome3
[12:57] <rodrigo_> well, also tried on my box, with gnome3, but no crash neither
[12:57] <seb128> rodrigo_, well I just started a daily iso in kvm, nautilus /usr/share/applications and close the nautilus dialog immediatly
[12:58] <seb128> nautilus crashed, I just tried again now
[12:58] <rodrigo_> hmm, ok
[12:58] <seb128> rodrigo_, maybe try downloading a daily iso and starting in kvm to see?
[12:58] <rodrigo_> yeah
[12:59] <pitti> Sweetshark: please unassign once you subscribe ubuntu-mir, it will be assigned to a member of the MIR team; do stay subscribed, though
[13:03] <Sweetshark> pitti: k
[13:03] <pitti> Sweetshark: looks fine now; still requires a packaging check (by MIR team)
[13:04] <pitti> Sweetshark: but your side is done now; thanks!
[13:05] <Sweetshark> pitti: great, thanks for the walkthrough ;)
[13:09] <Sweetshark> pitti: hmm, there might be another one actually for MIR: libreoffice-nlpsolver, see bug 712725. That one just got into debian unstable in the last days, but we should have it in natty too, I guess. It is one of the unique features of LO which OOo does not have. FWIW we should be able to just use the version by debian as is ...
[13:09] <ubot2> Launchpad bug 712725 in libreoffice "NLPSolver extension not available" [Medium,In progress] https://launchpad.net/bugs/712725
[13:12] <pitti> Sweetshark: is it recommended by the LibO package?
[13:14] <Sweetshark> pitti: hmmm, no. So we would put it in universe?
[13:15] <pitti> Sweetshark: I guess we won't really need it for a standard CD install, but I guess the full "libreoffice" metapackage could certainly depend on it
[13:15] <pitti> Sweetshark: that would need a MIR then, of course
[13:15]  * pitti syncs it into natty
[13:16]  * Sweetshark tries to MIRify the bug then.
[13:17] <pitti> Sweetshark: synced and source NEWed; will take some time to build now, and then needs to get through binary NEW
[13:17] <pitti> Sweetshark: but now you should be able to change the source package task to nlpsolver, i. e. LP now knows about it
[13:17] <Sweetshark> ah, ok
[13:18] <Sweetshark> ... not yet ...
[13:21]  * Sweetshark wonders: at debian the package is called libreoffice-nlpsolver, but here it is nlpsolver?
[13:24] <seb128> Sweetshark, sourcename != binaryname
[13:24] <Sweetshark> seb128: doh! ok. ;)
[13:26] <mterry> seb128, is tedg around today?
[13:26] <seb128> mterry, hey
[13:26] <seb128> mterry, I guess so, he was around yesterday at least
[13:26] <seb128> mterry, he just join a bit later than that usually, like in 1 hour or so
[13:26] <pitti> seb128: I'm about to do a nautilus upload; do you have anything pending?
[13:27]  * pitti got bug 714958 fixed now
[13:27] <ubot2> Launchpad bug 714958 in nautilus "desktop should disable automounting when screen is locked" [Medium,Fix committed] https://launchpad.net/bugs/714958
[13:27] <pitti> it's working quite nicely now
[13:27] <seb128> pitti, let me check
[13:28] <seb128> pitti, lp:~rodrigo-moya/ubuntu/natty/nautilus/fix-718098
[13:28] <seb128> pitti, you might want to merge than
[13:28] <seb128> that
[13:28] <pitti> seb128: will look, thanks
[13:29] <pitti> rodrigo_: is your fix for bug 718098 upstream anywhere? there are no links or patch tag headers
[13:29] <ubot2> Launchpad bug 718098 in nautilus "nautilus crashed with SIGSEGV in g_str_hash()" [Medium,In progress] https://launchpad.net/bugs/718098
[13:30] <rodrigo_> pitti, no, not upstream
[13:30] <pitti> rodrigo_: can you please forward it? or just commit there (looks obvious to me)
[13:30] <seb128> pitti, we just discussed it half an hour ago on the channel
[13:31] <seb128> pitti, he said he wants a real fix rather than a workaround
[13:31] <pitti> ah, ok
[13:31] <rodrigo_> pitti, well, it's just a fix for a symptom, not the real fix, so I'd prefer not to send it upstream for now
[13:31] <seb128> but he fails to get the issue on his install
[13:31] <pitti> ack
[13:31] <rodrigo_> pitti, I'm still looking at what could cause it
[13:31] <rodrigo_> just submitted this branch so that people stop getting crashes
[13:33] <pitti> merged, uploading now; thanks!
[13:51] <pitti> hm, when I press F7, my desktop goes mad
[13:51] <pitti> can't type anything any more, or select menu entries, etc.
[13:51] <seb128> don't do that!
[13:52] <pitti> F8 as well; but that's my pastetoggle key for vim!
[13:52] <seb128> joke aside no issue there
[13:53] <pitti> then again I can't switch to ctrl+alt+f8 from VT1 any more either
[13:53] <pitti> ctlr+alt+f1 to f6 works, though
[13:53] <pitti> so maybe it's somethign new in X
[14:00] <seb128> jibel: bug #723156, is that specific to the liveCD?
[14:00] <ubot2> Launchpad bug 723156 in gnome-control-center "Keyboard layout selection is not preserved after logout/login on liveCD" [Undecided,New] https://launchpad.net/bugs/723156
[14:01] <chrisccoulson> hi pitti
[14:01] <chrisccoulson> if you feel like doing some removals, i have bug 723163 (which closes another WI) ;)
[14:01] <ubot2> Launchpad bug 723163 in prism "Please remove prism source and binaries from natty" [Wishlist,New] https://launchpad.net/bugs/723163
[14:01] <seb128> seems an issue for pitti or GunnarHj
[14:02] <seb128> likely gdm, .dmrc, gnome-settings-daemon thing
[14:02] <jibel> seb128, Idk, I haven't tried to reproduce on real hw yet. I'll do that in the afternoon and update the report.
[14:04] <pitti> didrocks: filed as bug 723167 FTR, I didn't find an existing bug
[14:04] <ubot2> Launchpad bug 723167 in unity "Panel does not use standard GTK/Pango font rendering/antialiasing, causing fuzzy fonts" [Undecided,New] https://launchpad.net/bugs/723167
[14:04] <pitti> hey chrisccoulson
[14:04] <pitti> chrisccoulson: oh, sure
[14:04] <chrisccoulson> hi pitti, how are you?
[14:04] <chrisccoulson> thanks :)
[14:04] <pitti> got a bit of a cold, but good otherwise! how about you?
[14:04] <seb128> jibel: I think it's similar to bug #659512
[14:04] <ubot2> Launchpad bug 659512 in gnome-settings-daemon "USA layout variant cannot exist without standard USA layout" [Medium,Fix released] https://launchpad.net/bugs/659512
[14:06] <pitti> chrisccoulson: *swoosh*
[14:08] <jibel> seb128, that's really close, I'll dup mine, and undup if it's still there once the fix is released.
[14:09] <chrisccoulson> pitti - excellent, thanks! my list is getting smaller now - https://wiki.ubuntu.com/DesktopTeam/Specs/Natty/Firefox4/XULRunner20Transition
[14:09] <chrisccoulson> :-)
[14:10] <pitti> yay
[14:10] <seb128> jibel: thanks
[14:10] <pitti> argh swt-gtk
[14:11] <chrisccoulson> pitti - yeah, that one's a real pain now
[14:11] <didrocks> pitti: ok, perfect, thanks :)
[14:24] <pitti> didrocks: FSVO "perfect" :)
[14:25] <didrocks> heh :)
[14:36] <seb128> tedg, have you seen bugs similar to bug #720895?
[14:36] <ubot2> Launchpad bug 720895 in libdbusmenu "bluetooth-applet crashed with SIGSEGV in g_variant_builder_add_value()" [Undecided,Triaged] https://launchpad.net/bugs/720895
[14:37] <tedg> seb128, In general yes.  They tend to come from using builders without any entries being added to it.
[14:38] <seb128> tedg, so bugs in the applications not in the stack?
[14:38] <tedg> seb128, Well, unfortunately, could be both :-/
[14:38] <tedg> seb128, Though we've fixed a bunch of those in dbusmenu.
[14:38] <seb128> tedg, this one seems to be a common one, what would help? valgrind log?
[14:39] <tedg> seb128, I think we've got all... but...
[14:39] <seb128> tedg, well mdz still get it on current natty
[14:40] <tedg> seb128, Really, a stack trace that can be retraced would probably be enough to identify it...
[14:40] <seb128> tedg, ok, will get you that
[14:40] <tedg> seb128, Why does that happen?  Upgrades after the stacktrace is uploaded but before the retracer can get to it?
[14:40] <seb128> tedg, no, issues on the retracer, I'm debugging that at the moment
[14:42] <seb128> bah
[14:42] <tedg> seb128, Honestly speaking, how much time do you spend fixing the retracer?  It seems like critical but yet unreliable infrastructure?
[14:42] <seb128> the retracing queue is empty
[14:48] <seb128> bah, I need to hurry, kenvandine will ruin my debug work
[14:48] <kenvandine> seb128, ?
[14:48] <seb128> kenvandine, I'm trying to figure why the libdbusmenu symbols don't work on the retracers
[14:49]  * kenvandine is trying to get lo-menubar uploaded in time to get NEW'd and MIR done :)
[14:49] <seb128> but when your upload hit the mirror the ddebs will be out of sync
[14:49] <kenvandine> ugh... sorry
[14:49] <seb128> no worry
[14:49] <seb128> still a bit before it's built and published ;-)
[14:49] <kenvandine> :)
[15:00] <rodrigo_> hmm, the gtk3 packages have been renamed?
[15:01] <pitti> seb128: ok, so gdk-pixbuf FTBFS is due to our local 065_gir_set_packages.patch
[15:01] <pitti> it's all kenvandine's fault :)
[15:01] <seb128> hehe
[15:01] <kenvandine> sigh... again :)
[15:01] <seb128> when I dropped a similar change on gtk kenvandine came complaining the next day
[15:01] <pitti> I think that might be fixed upstream in a better way now
[15:01] <seb128> it seems those are buggy but yet required
[15:01] <pitti> that says
[15:01] <pitti> GdkPixbuf_2_0_gir_EXPORT_PACKAGES = gdk-pixbuf-2.0
[15:02] <pitti> kenvandine: ^ do you know whether that's sufficient? we want "what's the corresponding .pc for this GIR", not "which .pcs do I need to build this GIR", right?
[15:02] <kenvandine> right
[15:02] <kenvandine> it basically adds a <package> to the gir file, with the .pc pkg name
[15:03] <pitti> kenvandine: ok, I'll check that then
[15:03] <kenvandine> thx pitti
[15:04] <pitti> kenvandine: confirmed, above works (the upstream solution)
[15:04] <kenvandine> not having that breaks a bunch of other things
[15:04] <kenvandine> great
[15:04]  * pitti fixes
[15:05] <mvo> hey didrocks! a quick question, is there a chance for a updated simple-ccsm? or is that not needed/desired?
[15:08] <didrocks> mvo: it's not maintained anymore
[15:11] <mvo> didrocks: should we remove it from the archive then?
[15:11] <mvo> didrocks: or is it fine, just not maintained?
[15:11] <mvo> i.e. no 0.9 version etc
[15:12] <didrocks> mvo: I think it should work, I didn't test though
[15:13] <mvo> didrocks: I got a mail bugreport about it, I will just reply to file a bug I guess
[15:15] <didrocks> mvo: yeah, I think it will be good. Thanks :)
[15:15] <mvo> thank you
[15:16] <seb128> pitti, what defines a successful retrace in apport again?
[15:16] <seb128> I though it was 5 correct functions in line
[15:17] <pitti>         The current heuristic is to consider it useless if it either is shorter
[15:17] <pitti>         than three lines and has any unknown function, or for longer traces, a
[15:17] <pitti>         minority of known functions.
[15:17] <pitti> seb128: "5 correct functions" is stronger, and only required for auto-duplication
[15:17] <seb128> ok
[15:17] <pitti> above is "has_useful_stacktrace()" for apport-failed-retrace
[15:17] <seb128> pitti, http://launchpadlibrarian.net/64887641/Stacktrace.txt is counted as correct
[15:17] <seb128> which is somewhat border line
[15:17] <pitti> I know; I'm happy to fine-tune
[15:17] <seb128> no that's ok
[15:17] <pitti> it currently falls un der the "majority of known functions"
[15:18] <seb128> I'm trying to find something which fails retracing to do it by hand ;-)
[15:18] <pitti> they really suck these days in general, though
[15:18] <seb128> 3 on 10 is not really in that category
[15:18] <pitti> seb128: did you try downgrading to 6.8 locally? did that reproduce any of the bad retraces for bluetooth (or whatever you were trying before where you said it works)?
[15:19] <seb128> pitti, not yet, but last time I tried to play with gdb versions the issue happened only in the retracer environment
[15:19] <pitti> ok, so could be fakechroot breakage again
[15:20] <seb128> I will do that now
[15:20]  * pitti sobs quietly
[15:20] <seb128> bah the i386 retracer is busted
[15:20] <seb128> ERROR: connecting to Launchpad failed: <?xml version="1.0"?>
[15:20] <seb128> ...
[15:21] <pitti> awesome; that looks transient, though
[15:21] <pitti> seb128: oh, is that perhaps why the retracer got stuck (lock files) without having anything in the log?
[15:21] <seb128> not really transient
[15:21] <pitti> we really need to file an RT for cron mails; I'll do that now
[15:21] <seb128> the i386 one crash on start
[15:21] <seb128> the amd64 one works though
[15:21] <seb128> I'm driving it by hand right now
[15:21] <seb128> go figure
[15:22] <pitti> amd64 had a lock file and no running retracer as well, though (and no error in the log)
[15:22] <seb128> I'm running it by hand
[15:22] <seb128> it just finished a retracing
[15:22] <pitti> seb128: heh -- check mailq on osageorange
[15:22] <seb128> cf the stacktrace I copied to you
[15:22] <pitti> looks like a firewall issue, I'll RT
[15:22] <seb128> urg
[15:22] <seb128> right
[15:25] <pitti> RT sent
[15:25] <seb128> pitti, do you have any clue about the i386 retracer issue?
[15:25] <seb128> look a debug in the ubuntu-archive dir
[15:25] <seb128> at
[15:25] <pitti> (/me in meeting, lagged)
[15:26] <seb128> or try running the i386 retracer by hand like the cron do
[15:26] <pitti> ugh, NFC :/
[15:26] <pitti> seb128: is that the outside crash digger already, or retrace in the fakechroot?
[15:27] <seb128> pitti, it's doing that in the second you run it
[15:27] <pitti> ok, outside then
[15:27] <seb128> so I guess the first thing which tries to talk to lp
[15:27] <pitti> so, seems it's a difference in the i386 vs. amd64 dchroot
[15:28] <pitti> hm, identical python{launchpad,wadl}lib versions
[15:28] <seb128> do they use the same .lpcookie?
[15:29] <pitti> hm, hang on, there's still a local launchpadlib /checkout
[15:29] <pitti> perhaps one of them is using that
[15:30] <dobey> hmm
[15:31] <pitti> seb128: I removed ~/launchpadlib/ now; nothing should be using that any more, just checked apport-retracer-*/environ
[15:31] <pitti> seb128: does it behave any different now?
[15:31] <pitti> seb128: yes, same cookie
[15:32] <seb128> pitti, no
[15:32] <seb128> You can reset the credentials by removing the file "/home/ubuntu-archive/.lpcookie"
[15:33] <seb128> it has a long error log with that at the end
[15:33] <pitti> seb128: it just prints that out on any HTTPError
[15:33] <seb128> well "log" seems like a launchpad page or something
[15:36] <pitti> seb128: hah - cron spam
[15:36] <seb128> ?
[15:36] <seb128> oh, they fixed it?
[15:36] <pitti> apparently so
[15:37] <pitti> meh, this dchroot noise is annoying
[15:37] <pitti> I always get it locally as well
[15:37] <pitti> dear dchroot, there is no "location" in any of my configuration, STFU
[15:37] <pitti> seb128: https://portal.admin.canonical.com/44183
[15:37] <pitti> just flipped to resolved
[15:38]  * pitti bows to our super fast IT team
[15:38] <GunnarHj> seb128, jibel: Am I guilty to bug 723156? ;-) The issue is indeed similar to the issue with GDM and l-s that didn't play well together, but at GNOME they are now referring to GDM for GNOME 3, where they seem to be dropping the opportunity to set basic session settings from the login screen. If that will happen with Ubuntu as well, is it really worth it to fix the current inconsistency with respect to keyboard layout settin
[15:38] <ubot2> Launchpad bug 723156 in gnome-control-center "Keyboard layout selection is not preserved after logout/login on liveCD (dup-of: 659512)" [Undecided,New] https://launchpad.net/bugs/723156
[15:38] <ubot2> Launchpad bug 659512 in gnome-settings-daemon "USA layout variant cannot exist without standard USA layout" [Medium,Fix released] https://launchpad.net/bugs/659512
[15:38] <GunnarHj> gs?
[15:39] <rodrigo_> so, what's the new name for the gtk3 packages? I still see the same ones in the standard repos
[15:40] <seb128> rodrigo_, libgtk-3-0
[15:40] <seb128> rodrigo_, libgtk-3-dev
[15:40] <rodrigo_> ok
[15:42] <rodrigo_> seb128, but those are not available yet on the repos
[15:43] <seb128> they are here
[15:43] <seb128> I installed them yesterday
[15:43] <seb128> do you use a mirror?
[15:43] <bcurtiswx> seb128, http://ftp.acc.umu.se/pub/GNOME/sources/empathy/2.91/empathy-2.91.90.news  should I add the optional champlain dep ?
[15:43] <seb128> bcurtiswx, no
[15:43] <bcurtiswx> seb128, OK thx
[15:43] <seb128> it's in universe
[15:43] <rodrigo_> seb128, yes, .es
[15:43] <seb128> you're welcome
[15:43] <rodrigo_> ok then
[15:46] <chrisccoulson> how do i turn off the ubuntuone notifications telling me the connection status?
[15:46] <chrisccoulson> i keep getting repeated notifications
[15:48] <chrisccoulson> aha, killing syncdaemon seems to have fixed it :)
[15:48] <kenvandine> chrisccoulson, you should file a bug to get them to quiet those down
[15:48] <chrisccoulson> kenvandine, yeah, it's annoying. i've basically had repeated notifications, one straight after another for the last 15 minutes or so
[15:52] <mdeslaur> chrisccoulson: please tell me the bug number once you've files it so I can go rant in it :)
[15:53] <seb128> pitti, ups, sorry I wanted to reply there
[15:53] <seb128> http://paste.ubuntu.com/570635/
[15:53] <seb128> less noisy
[15:53] <seb128> pitti, so it's a gdb issue
[15:53] <seb128> 6.8 screw the stacktrace
[15:53] <seb128> 7.2 works fine
[15:53] <seb128> both on my natty box
[15:53] <seb128> using on a running indicator with a breakpoint
[15:53] <pitti> seb128: ah, many thanks
[15:53] <rodrigo_> seb128, what repo are you using? archive.ubuntu.com?
[15:54] <seb128> rodrigo_, yes
[15:54] <seb128> rodrigo_, you?
[15:54] <seb128> rodrigo_, try to apt-cache policy libgtk-3-0
[15:54] <seb128> or libgtk3.0-0 as well
[15:55] <rodrigo_> was using .es, but switched to the main archive
[15:55] <rodrigo_> but now I realize I was apt-cache search gtk3
[15:55] <rodrigo_> and it's libgtk-3-0
[15:55] <rodrigo_> ok, there it is indeed
[15:56] <seb128> rodrigo_,
 so, what's the new name for the gtk3 packages? I still see the same ones in the standard repos
 rodrigo_, libgtk-3-0
[15:56] <seb128>  rodrigo_, libgtk-3-dev
[15:56] <seb128> rodrigo_, not my fault :p
[15:56] <rodrigo_> no, my fault :-)
[16:07] <seb128> GunnarHj, right, I've no real opinion on the logic screen options
[16:07] <seb128> or on whether it will be fine to drop those
[16:07] <seb128> or if we will want to put them back
[16:08] <seb128> or use another dm like lightdm
[16:09] <seb128> pitti,
[16:11] <seb128> pitti, seems there is something wrong with the cookies
[16:12] <pitti> we can regenerate them easily
[16:12] <pitti> seb128: perhaps it helps to purge the LP cache?
[16:13] <seb128> pitti, what cookie is subscribe-triagers.py supposed to try to use?
[16:13] <pitti> seb128: ~/.lpcookie is the general auth file, there is no other
[16:14] <seb128> pitti, no, I think lptools are using .launchpadlib/...
[16:15] <seb128> let me try something
[16:20] <GunnarHj> pitti: Hi Martin, I submitted the backports bug 719815 the other day. Do you have time to think it over and (hopefully) triage it?
[16:20] <ubot2> Launchpad bug 719815 in maverick-backports "Please backport gdm and language-selector to Lucid and Maverick" [Undecided,Confirmed] https://launchpad.net/bugs/719815
[16:20] <pitti> GunnarHj: I'm not in ~ubuntu-backporters
[16:21] <pitti> GunnarHj: we can't just backport the natty l-s package as it is, as this was switched to pygi
[16:21] <pitti> which doesn't yet work on lucid/maverick
[16:21] <pitti> gdm should work fine, though
[16:21] <GunnarHj> pitti: I know, but Scott asked for an opinion.
[16:22] <GunnarHj> pitti: The bransches don't include the pygi stuff.
[16:23] <pitti> bug updated
[16:24] <pitti> GunnarHj: ah, there are branches already? usually backports require that you can build and use the natty package unmodified
[16:24] <pitti> as custom modifications need to be kept in sync and thus require a much larger amount of maintenance
[16:25] <pitti> jasoncwarner: hey Jason, how are you? do you lead the meeting today?
[16:27] <GunnarHj> pitti: I realised that that wouldn't suffice in this case. Thanks for the bug comment.
[16:30] <jasoncwarner> morning, pitti...yeah, I'm here and all!
[16:30] <pitti> ah, awesome
[16:30] <seb128> hey jasoncwarner
[16:30] <jasoncwarner> hey seb128! morning!
[16:31] <pitti> Sweetshark, bryceh, chrisccoulson, didrocks, Riddell, kenvandine, cyphermox, mterry, rodrigo_: meeting
[16:31] <cyphermox> o/
[16:31] <mterry> heyo!
[16:31] <rodrigo_> \o
[16:31]  * Sweetshark reporting in.
[16:31] <jasoncwarner> morning everyone.
[16:31] <pitti> tremolux and tkamppeter seem to be offline
[16:31]  * kenvandine waves
[16:31] <jasoncwarner> https://wiki.ubuntu.com/DesktopTeam/Meeting/2011-02-22
[16:31] <rodrigo_> hey jasoncwarner
[16:32] <chrisccoulson> hi!
[16:32] <didrocks> hey
[16:32] <jasoncwarner> pitti: no problem.
[16:33] <jasoncwarner> good morning everyone...hope everyone is doing well! Should be a good week, I suppose..almost to feature freeze!
[16:33] <jasoncwarner> [TOPIC] Partner Update
[16:33] <kenvandine> yup
[16:34] <kenvandine> UbuntuOne:
[16:34] <kenvandine> they will be needing a FFE for the unity launcher integration
[16:34] <kenvandine> it is still blocked on bug 709240
[16:34] <ubot2> Launchpad bug 709240 in vala "libunity support gobject-introspected languages" [Medium,New] https://launchpad.net/bugs/709240
[16:35] <kenvandine> but that api is so simple, it shouldn't be much work or risky
[16:35] <kenvandine> for DX
[16:35] <kenvandine> we'll finally be getting libreoffice appmenu support
[16:35] <kenvandine> lo-menubar is working, i'll get the package uploaded today
[16:35] <kenvandine> and start an mir
[16:36] <seb128> oh, they will maybe beat chrisccoulson and firefox it seems ;-)
[16:36] <kenvandine> tedg has some feature work landing this week too, but we missed our meeting yesterday... i don't have a good list of that atm
[16:36] <Sweetshark> http://aruiz.synaptia.net/siliconisland/2011/02/introducing-libreoffice-integration-with-unitys-application-menubar.html and http://blog.documentfoundation.org/2011/02/21/a-warm-welcome-to-canonical/ in case anyone missed it ...
[16:36] <kenvandine> i'll get it on the wiki page though
[16:37] <kenvandine> that is all i have
[16:37] <kenvandine> questions?
[16:37] <chrisccoulson> seb128 - oh, we can't have that ;)
[16:37] <kenvandine> chrisccoulson, race!
[16:37] <chrisccoulson> i'm basically blocked on mozilla now, my extension is pretty much finished!
[16:37] <seb128> ok, I bet on kenvandine, let's see!
[16:37] <chrisccoulson> lol
[16:37] <kenvandine> hehe
[16:37] <kenvandine> :-D
[16:38] <jasoncwarner> Awesome, thanks Ken. chrisccoulson, still waiting on mozilla?
[16:38] <chrisccoulson> jasoncwarner, yeah. i'm actually just chasing it up right now
[16:39] <jasoncwarner> :) thanks!
[16:39] <jasoncwarner> Ok, [TOPIC] UNITY
[16:40] <didrocks> hey o/
[16:40] <didrocks> as usual, most of what's important is on the wiki
[16:40]  * kenvandine prays for dash and places
[16:40] <didrocks> kenvandine: it's there already :)
[16:40] <didrocks> still a crash though, will be fixed for next release
[16:40] <didrocks> so, feature-wise, we are almost on top of it
[16:41] <didrocks> just alt + F2 remaining and will need a FFe
[16:41] <didrocks> and another one for resizing windows, will come soon
[16:41] <didrocks> troubles ahead: new compiz tomorrow with ABI break, don't do partial upgrades!
[16:41] <didrocks> all the rest is on the wiki :)
[16:42] <didrocks> (we got also some new tool to deal with unity bug, will blog about at the end of the week)
[16:43] <jasoncwarner> thanks, didrocks...
[16:44] <jasoncwarner> skipping software center...[TOPIC] KUBUNTU
[16:45] <jasoncwarner> Riddell: you around?
[16:45] <Riddell> hi
[16:45] <Riddell>  * owncloud packaged and in
[16:45] <Riddell>  * samba sharing in
[16:45] <Riddell>  * language selector updates working, will be merged & uploaded shortly
[16:45] <Riddell>  * kdebindings still broken on ARM, no resolution from mobile team or upstream, getting worrying
[16:46] <Riddell>  * 14 milestoned bugs for alpha 3 http://goo.gl/yGhJd
[16:46] <Riddell>  * Todo list features pleasingly green ready for feature freeze https://wiki.kubuntu.org/Kubuntu/Todo
[16:47] <jasoncwarner> thanks Riddell...any idea what is holding up the kdebindings?
[16:47] <Riddell> well something to do with qreal!=double which is a typical ARM issue we have
[16:47] <Riddell> but this one is especially difficult and I can't work it out and neither can ncommander
[16:48] <jasoncwarner> hmm...is there hope of a fix in time for FF or is this something that is not going to make it?
[16:48] <Riddell> I can't see it happening in time for FF
[16:48] <Riddell> it's not a feature of course, it's a bug
[16:49] <jasoncwarner> Riddell: ok, thanks ...
[16:49] <jasoncwarner> [TOPIC] Tools and Processes
[16:51] <jasoncwarner> pitti: anything you want to talk about here?
[16:51] <pitti> not from my side
[16:51] <pitti> I walked through our remaining specs/WIs yesterday
[16:51] <pitti> and cleaned up a bit
[16:52] <pitti> there are still a few bits which are feature development, but not too many any more
[16:52] <pitti> http://people.canonical.com/~platform/workitems/natty/canonical-desktop-team.html looks quite ok
[16:52] <seb128> not sure what the tools and processes section is about? is that a call for random topics?
[16:52] <YBinnenweg> Hi guys
[16:52] <pitti> http://people.canonical.com/~platform/workitems/natty/canonical-desktop-team-natty-alpha-3.html looks more concerning, though :)
[16:53] <YBinnenweg> I have problems with installing ubuntu 10.10 on my desktop
[16:53] <seb128> YBinnenweg, hi, try #ubuntu
[16:53] <YBinnenweg> Okay :)
[16:54] <jasoncwarner> thanks, pitti...looks like there are some WIs we need to look at before A3. Anything on that list blocked ?
[16:54] <pitti> it looks like basically all the quickly ones are?
[16:54] <pitti> blocking on LP implementation, I figure
[16:55] <pitti> mterry has 5 of them, didrocks 1
[16:55] <mterry> Yeah, I think we just postpone those
[16:55] <pitti> I guess we can move that to beta-1 for now and live with a FF (should be trivial for quickly)
[16:55] <pitti> and if it still doesn't land, move to octopus?
[16:55] <mterry> True, we can try to FFe them when done
[16:55] <pitti> do you happen to know how soon that will land?
[16:55] <didrocks> right
[16:55] <mterry> I think LP team is targetting A3
[16:56] <pitti> then there's certainly a lot of non-desktop team WIs there
[16:56] <jasoncwarner> mterry: thanks...seems we'll have to wait and see (while simulataneiously putting a tad bit of pressure on the LP folks ;) )
[16:57] <jasoncwarner> Ok...anything else? AOB ?
[16:58] <seb128> not a topic but worth mentionning that the retracers are quite broken at the moment
[16:58] <kenvandine> :(
[16:58] <seb128> so don't rely on those much
[16:58] <pitti> mterry, didrocks: ok, I updated https://blueprints.launchpad.net/ubuntu/+spec/appdevs-desktop-n-quickly accordingly; there's still enough a3 fodder left
[16:58] <seb128> the annoying bits is that they auto invalid and let private bugs which fail retracing
[16:59] <seb128> which seems to concerning libdbusmenu stacktraces
[16:59] <pitti> I have it very high on my list to debug this (in fact, working on it right now)
[17:02] <jasoncwarner> Ok...thanks for the reminder seb128. Anything else or should we get back to getting those WIs completed and finishing off stuff for FF? :)
[17:02] <chrisccoulson> which day is FF?
[17:03] <pitti> Thursday
[17:03] <chrisccoulson> pitti - thanks. will i need a FFe to land my menu bar extension?
[17:03] <chrisccoulson> based on conversations i've just had, it might be friday ;)
[17:03] <pitti> chrisccoulson: yes, but that should be fine
[17:03] <chrisccoulson> thanks
[17:05] <jasoncwarner> alright..if no one has anything else, [END MEETING]. Come back for eastern edition to get latest on X.org/Mesa stuff if interested ;)
[17:05] <kenvandine> :)
[17:05] <chrisccoulson> i'm always around in those meetings ;)
[17:07] <mterry> tedg, heyo, just so you know, I've been working on the datetime preference dialog part of the DateAndTime spec.  It's in lp:~mterry/indicator-datetime/clock-prefs .  Not done yet, but it might be a big merge and a pre-review might be good, especially to correct me if I'm doing anything especially stupid
[17:08] <didrocks> hum, session restart to get a working stacking, brb
[17:08] <tedg> mterry, Makes sense, but I'm sure mpt will find more errors with that than I will ;)
[17:08] <tedg> mterry, I'll take a look.
[17:10] <cyphermox> i've been debugging bug 723166 and bug 722020 which seem to be the same thing, looking at gnome-bluetooth source I see the menus are being set as GtkAction, and I wonder if the fact that dbusmenu then tries to get the new label  from a GtkMenuItem cast of the object doesn't break things?
[17:10] <ubot2> Launchpad bug 723166 in gnome-bluetooth "bluetooth-applet crashed with SIGSEGV in g_atomic_int_exchange_and_add()" [Medium,New] https://launchpad.net/bugs/723166
[17:10] <ubot2> Launchpad bug 722020 in indicator-appmenu "bluetooth-applet crashed with SIGSEGV in g_atomic_int_exchange_and_add()" [Medium,New] https://launchpad.net/bugs/722020
[17:16] <rodrigo_> can someone please review and upload this: https://code.launchpad.net/~rodrigo-moya/ubuntu/natty/gsettings-desktop-schemas/0_1_7_release/+merge/50787 ?
[17:16] <rodrigo_> debian is still at 0.1.5, so I just went ahead and updated it
[17:16] <rodrigo_> it's needed for the new g-c-c
[17:17] <seb128> tedg, mterry, chrisccoulson: ^ you probably have a clue about those crashes, they seem to be due to appmenu code
[17:17] <seb128> rodrigo_, can you just upload to the ppa rather? I will sync the update from debian when pochu does it later
[17:17] <rodrigo_> seb128, yes, sure
[17:18] <seb128> it's less work than doing an upload to reforce a sync behind in the distro
[17:18] <seb128> thanks
[17:21] <tedg> seb128, kenvandine just uploaded a dbusmenu version with a fix that may fix those -- hard to tell for sure, but was a NULL variant unref.
[17:25] <chrisccoulson> pitti - i'm still totally stuck with swt-gtk atm. i don't know what to do with it :/
[17:25] <chrisccoulson> can i kill it? ;)
[17:30] <pitti> chrisccoulson: did Daviey get back to you about dropping it from euca?
[17:30] <chrisccoulson> pitti - not yet, or at least, not that i remember :)
[17:35] <seb128> tedg, it's getting hard to know what bugs are still current or not ;-)
[17:35] <seb128> tedg, thanks
[17:35] <tedg> seb128, I solve that by assuming they're all fixed ;)
[17:35] <seb128> cyphermox, ^ tedg thinks it might be fixed with the upload today
[17:36] <cyphermox> seb128, ah
[17:36] <seb128> tedg, until next week when we notice we keep gettings somes
[17:37] <tedg> seb128, No, really, I'll assume they're fixed even then ;)
[17:38] <seb128> tedg, I'm glad you stop assuming that and review patches when they are coming ;-)
[17:39] <cyphermox> seb128, tedg, that was the upload of what today?
[17:49] <seb128> kenvandine, the libdbusmenu update of yours will not build
[17:49] <seb128> kenvandine, you need to build-depends on libgtk-3-dev (new naming)
[17:50] <seb128> c.f ubuntu-desktop mailing list for details on the renaming
[17:51] <nessita> does anyone know why a package build is started to fail with dh_install: python-ubuntuone-control-panel missing files (debian/tmp/usr/lib/python2.*/*-packages/*/ubuntuone/__init__.py), aborting?
[17:51] <nessita> the source does have a ubuntuone/__init__.py file, but when running bzr bd is not copied to debian/tmp
[17:51] <nessita> it used to work without problems, which puzzles me a lot
[17:52] <seb128> nessita, did they got dropped from the tarball?
[17:52] <nessita> nopes
[17:52] <nessita> I just checked that, the file is in the tarball
[17:52] <seb128> nessita, what is the vcs? can I try from here?
[17:53] <nessita> seb128: I haven't made an official release yet, I was testing a change in the .desktop file. Will it help to send you the tarball?
[17:53] <seb128> nessita, do you get the same issue if you build the current natty source?
[17:53] <seb128> nessita, you can send me a tarball if you want yes
[17:53] <nessita> good point, let's try
[17:53] <seb128> it's hard to debug it without having access
[17:53] <nessita> yeah
[17:54] <nessita> seb128: yeah, I get the same issue using trunk (lp:ubuntu/ubuntuone-control-panel)
[17:57] <seb128> nessita,  let me try
[17:57] <nessita> seb128: I just tested on a clean branch, same error. Yes please :-)
[17:57] <seb128> works fine here
[17:58] <kenvandine> seb128, oh yeah, i hadn't read that email yet when i uploaded that fix
[17:58] <kenvandine> seb128, fixing now
[17:58] <nessita> seb128: what did you do exactly? I did:
[17:58] <nessita>  bzr branch lp:ubuntu/ubuntuone-control-panel; cd ubuntuone-control-panel; bzr bd
[17:59] <nessita> and got the error. This is a new natty install (since yesterday), up to date
[17:59] <seb128> nessita, same
[17:59] <seb128> kenvandine, thanks
[17:59] <seb128> nessita, can you pastebin your build log?
[17:59] <nessita> of course sir!
[17:59] <seb128> or scp it somewhere as you want
[18:00] <nessita> seb128: http://pastebin.ubuntu.com/570700/
[18:06]  * nessita scratches her head
[18:07] <seb128> nessita, can you check what is in ../build-area/u-c-p/debian/tmp/usr/lib?.
[18:09] <Daviey> pitti / chrisccoulson: Sorry, but euca is in a really bad way at the moment - i'm kinda nervous about introducing the potential of more breakage
[18:09] <nessita> seb128: http://pastebin.ubuntu.com/570703/
[18:10] <Daviey> chrisccoulson, I'm hoping to have a chat with upstream later today... but can you remind me of the main rational for removing the need for xulrunner?
[18:10] <nessita> seb128: as you can see, ../build-area/ubuntuone-control-panel-0.8.3/debian/tmp/usr/lib/python2.7/site-packages/ubuntuone-control-panel/ubuntuone/__init__.py is not there :-/
[18:10]  * Daviey goes afk for a bit, but will read scrollback on his return
[18:11] <chrisccoulson> Daviey, we've currently got 2 versions of xulrunner in main, and supporting just 1 version is difficult enough ;)
[18:11] <chrisccoulson> ideally, we don't want to have xulrunner in main at all now
[18:11] <Daviey> chrisccoulson, ideally i'd remove the rdepend you are talking about from the archive altogether :)
[18:12] <chrisccoulson> Daviey, me too. euca doesn't actually use any of the xulrunner parts either. the only things which use it are in universe
[18:13] <seb128> nessita, checking
[18:13] <seb128> nessita, you know about ls -R right? ;-)
[18:14] <nessita> seb128: yeah, but I like complicated :-D
[18:14] <nessita> is more fun (?)
[18:14] <Daviey> chrisccoulson, I'll contact upstream again today.. and hopefully have a better idea.. but if you are sure it doesn't actually use it, then it certainly sounds safe enough
[18:14] <nessita> seb128: and I get to chat with you a little longer ;-)
[18:14] <seb128> ;-)
[18:15] <seb128> nessita, it's weird
[18:16] <seb128> nessita, the build log has "copying build/lib.linux-x86_64-2.7/ubuntuone/controlpanel/__init__.py -> /home/nessita/tmp/build-area/ubuntuone-control-panel-0.8.3/debian/tmp/usr/lib/python2.7/site-packages/ubuntuone-control-panel/ubuntuone/controlpanel"
[18:17] <nessita> seb128: right, but that is not the problematic file
[18:17] <seb128> oh right
[18:17] <nessita> the one is: build/lib.linux-x86_64-2.7/ubuntuone/__init__.py
[18:17] <seb128> let me compare with my build log
[18:18] <seb128> oh
[18:18] <seb128> gotcha
[18:18] <nessita> the __init__.py file is not in ../build-area/ubuntuone-control-panel-0.8.3/build/lib.linux-x86_64-2.7/ubuntuone/
[18:18] <seb128> nessita, you need python-defer
[18:18] <seb128> nessita, see the ERROR line just after configure
[18:19] <seb128> nessita, I guess it's not installed on your box
[18:19] <nessita> is not...
[18:19] <nessita> is a new install
[18:19] <seb128> it lacks a build-depends on it
[18:19] <nessita> I'm adding it right now
[18:20] <seb128> urg
[18:20] <Daviey> chrisccoulson, Which is it 2.0 or 1.9.2 you are trying to drop?
[18:20] <nessita> seb128: thanks!
[18:20] <seb128> nessita, the control has almost no build-depends, is that normal?
[18:20] <chrisccoulson> Daviey, 1.9.2 definitely needs to go, but i'd like to drop 2.0 as well
[18:20] <seb128> nessita, the pkginfo list quite some things, defer, aptdaemon, etc
[18:21] <seb128> oh, I guess those are runtime
[18:21] <nessita> seb128: exactly
[18:21] <nessita> seb128: we don't use any of those to *build*
[18:21] <nessita> anyways, python-defer is not listed in the corresponding binary package, I should fix that
[18:22] <seb128> nessita, well somewhat the build log suggest it tries to use defer at build time
[18:22] <nessita> I'll see if I can debug that
[18:22] <seb128> it's aptdaemon.defer
[18:23] <nessita> seb128: hum?
[18:24] <seb128> it's "aptdaemon.defer not found"
[18:24] <seb128> nessita, you might need python-aptdaemon
[18:24] <nessita> ah, yes, in line 87
[18:25] <nessita> yeah, but I don't understand why that is needed at build time, it makes no sense
[18:25] <seb128> right
[18:26] <seb128> could be a red hearing...
[18:26] <seb128> nessita, if you run python setup.py build in your checkout, does it work?
[18:27] <nessita> yes it does
[18:27] <nessita> without any error
[18:27] <seb128> you get a build/lib.linux-x86_64-2.7/ubuntuone/__init__.py ?
[18:27] <nessita> no...
[18:28] <nessita> but the tar does, I guess that is unrelated
[18:29] <nessita> output is http://pastebin.ubuntu.com/570714/
[18:29] <dobey> nessita: for some reason, it seems setup.py is not installing it on narwhal
[18:30] <nessita> dobey: I think I know what the problem is
[18:30] <dobey> ah
[18:30] <nessita>      87     packages=['ubuntuone.controlpanel', 'ubuntuone.controlpanel.gtk'],
[18:30] <dobey> i see
[18:30] <dobey> yes
[18:30] <nessita> it should be
[18:30] <nessita>      87     packages=['ubuntuone', 'ubuntuone.controlpanel', 'ubuntuone.controlpanel.gtk'],
[18:30]  * nessita fixes
[18:30] <dobey> should be packages=find_packages()
[18:30] <dobey> hrmm, actually no
[18:30] <nessita> dobey: and where does find_packages come from?
[18:30] <seb128> nessita, but why does it fail for you and not for others?
[18:30] <dobey> because then it will install the integrationtests dir too
[18:31] <nessita> seb128: is failing for the natty build as well
[18:31] <dobey> which we don't necessarily want right now
[18:31] <dobey> nessita: so just using the list is the right way for now i think
[18:31] <nessita> seb128: it wasn't failing before because we did another 'magic' with modules -- only one project was installing that __init__ file
[18:31] <dobey> nessita: did you remove ubuntuone from that list at some point?
[18:31] <seb128> nessita, oh ok
[18:32] <seb128> nessita, ok, seems you have it sorted then, or at least you are on track
[18:32] <nessita> dobey: I don't think so, not that I recall
[18:32] <dobey> nessita: that's weird
[18:32] <nessita> seb128: yes, thanks A LOT for your help
[18:32] <seb128> nessita, you're welcome ;-)
[18:33] <nessita> dobey: I'll fix it
[18:33] <dobey> nessita: because it's working fine on maverick, and the 0.8.3 release i made last week built fine on narwhal when i made these changes in ubuntu
[18:33] <gnomefreak> it seems the transition from mutter -> compiz is complete?
[18:33] <dobey> nessita: sure, i'd just like to understand how it broke :)
[18:33] <nessita> dobey: I haven't touched the setup.py till today
[18:33] <dobey> very weird
[18:33] <nessita> indeed
[18:42] <nessita> argh, aptdaemon API changed?
[18:42] <nessita> mvo: ping
[18:46] <nessita> mvo: unping
[18:47] <pitti> . o O { what happens if you unping a person without previously pinging? stack underflow exception? }
[18:47] <nessita> pitti: :-)
[18:47] <pitti> mvo: unping
[18:47] <pitti> *mvo disconnected (segfault)
[18:47] <kenvandine> hehe
[18:48]  * pitti hugs mvo
[18:48] <kenvandine> we should unref
[18:51] <alecu> didrocks, ping
[18:52] <alecu> didrocks, do you know if a new version of gir1.2-unity-3.0 will be packaged soon?
[18:52] <alecu>  It looks like the issue in bug #709240 is fixed on libunity trunk (getting "TypeError: must be an interface" when using libunity from python).
[18:52] <ubot2> Launchpad bug 709240 in vala "libunity support gobject-introspected languages" [Medium,New] https://launchpad.net/bugs/709240
[18:56] <didrocks> alecu: this thursday
[18:56] <didrocks> like every unity releases
[18:56] <alecu> didrocks, great, thanks. I'm adding some comments to that bug.
[18:57] <ricotz> rodrigo_, hi, are you going to upload more things to gnome3-ppa?
[19:14] <rodrigo_> ricotz, yes, not today probably though
[19:16] <ricotz> rodrigo_, ok, new g-s and mutter will be released soon
[19:16] <rodrigo_> ricotz, cool!
[19:16] <ricotz> but g-c-c might be the most important for now
[19:17] <rodrigo_> ricotz, yes, on it myself, just have to deal with some other deps (libxklavier, libgnomekbd), so leave that to me
[19:17] <ricotz> ok, that would be nice
[19:40] <gnomefreak> im guessing desktop team maintains compiz. if so is there any chance that unity and compiz will be compatible in the near future. right now they dont play well with eachother outside of the default settings
[19:40] <seb128> gnomefreak, what do you mean? unity is a compiz option
[19:42] <gnomefreak> seb128: if i use the compiz config and choose to enable water effect. it breaks unity. if i choose to use the desktop cube it wants to disable desktop wall, once desktop wall is disabled it wants you to disable ubuntu unity plugin
[19:42] <seb128> how does the water effect breaks unity?
[19:42] <gnomefreak> those are what i tested so far, since neither worked as expected i figured i would stop there
[19:42] <kenvandine> chrisccoulson, this is impressive, firefox is using 497G of virt mem
[19:44] <gnomefreak> ok that sucked. let me paste it back. i typed it in wrong channel some how
[19:44] <gnomefreak> seb128: all gnome panels disappear, the window  boarders are gone. you cant click on any  window and use it. for example i had 2 terms  open and i can switch between them but i can  not use any commands and such
[19:45] <seb128> oh
[19:45] <seb128> that's compiz crashing which is a known issue
[19:45] <gnomefreak> ah ok
[19:45] <seb128> it tends to crash when enable or disabling options in ccsm
[19:45] <seb128> you can restart it, go to a VT and DISPLAY=:0 compiz
[19:46] <gnomefreak> does that also go with the disabling of options
[19:46] <seb128> yes
[19:46] <seb128> "or disabling options"
[19:47] <gnomefreak> ok cool thanks. i will look for the bug that was filed so i can track it
[19:48] <Daviey> chrisccoulson, Hey... Do you already have a swt-gtk that is built without xulrunner?
[20:56] <pitti> apport-retrace --auth /tmp/auth -guv 721240
[20:58] <seb128> it doesn't give nice result with either version?
[20:58] <seb128> did you try locally?
[20:58] <pitti> seb128: 6.8 gives a reasonable result, 7.2 a broken one (both in retracer fakechroot)
[20:58] <pitti> seb128: local one is running, needs to download awful amount of debs..
[20:59] <seb128> pitti, well, get the deb locally and just unpack and use gdb on the dump but I guess it will give you a decent stacktrace
[21:00] <seb128> pitti, I start thinking we should rework the retracers to use vm images rather
[21:00] <pitti> seb128: ok, local apport-retrace finished
[21:00] <pitti> result is equally poor
[21:01] <seb128> hum
[21:01] <seb128> it doesn't make sense
[21:01] <seb128> like you lack libwnck symbols?
[21:02] <seb128> well maybe that crashdump is buggy
[21:03]  * pitti tries bug 712242
[21:03] <ubot2> pitti: Error: Could not parse data returned by Launchpad: list index out of range (https://launchpad.net/bugs/712242)
[21:25] <cyphermox> smspillaz, ping
[21:28] <Amaranth> cyphermox: he was up late, probably have to try again in a few hours
[21:28] <cyphermox> Amaranth, thanks
[22:02] <jasoncwarner> Easter edition desktopers awake? RAOF TheMuso robert_ancell ?
[22:02] <jasoncwarner> and, of course, bryceh, .... joining us from the US :)
[22:02] <jasoncwarner> https://wiki.ubuntu.com/DesktopTeam/Meeting/2011-02-22
[22:02] <RAOF> So far east he's west :)
[22:02] <jasoncwarner> Well, why don't we get started... RAOF and bryceh, care to update on [TOPIC] X.org ?
[22:02] <RAOF> It's been a fun week in X.org
[22:02] <bryceh> heya
[22:02] <bryceh> Wayland is now uploaded to universe :-)
[22:02] <TheMuso> Hey folks.
[22:02] <jasoncwarner> bryceh: woohoo!
[22:02] <TheMuso> Sweet!.
[22:02] <bryceh> just has to get past archive admins
[22:03] <RAOF> We've landed a fix for nouveau which makes unity work on all supported (hah!) cards, and switched to r600g by default which means that the radeon crashes in alt-tab should be gone.
[22:03] <bryceh> then just apt-get install wayland ; wstart
[22:03] <pitti> RAOF: rockin'!
[22:03] <TheMuso> ...and if its nouveau supported hardware, it will toast your laptop... :)
[22:04] <bryceh> aside from all that, past week has been lots of work on bugs and apport hooks
[22:04] <TheMuso> Not really, but make it rather warm to the touch, so be warned. :)
[22:04] <RAOF> Xserver 1.10RC2 has been released, and is almost ready in git.  This upload will also fold in the Xi 2.1 multitouch work, so have fun, all of you with MT hardware :)
[22:05] <RAOF> Because of some dependency handling changes this will require a rebuild of all the drivers to pick up the new Depends field info, but there isn't an ABI change, so old drivers won't cause the X server to crash :)
[22:05] <jasoncwarner> RAOF: just read the one about nouveau...awesome...will be upgrading later today then!
[22:06] <jasoncwarner> very cool...can't wait for those changes. Anything else from X?
[22:07] <bryceh> if you want a run down on individual bugs we're working on we can do that, but it's probably TMI
[22:07] <bryceh> oh, one worth noting
[22:07] <jasoncwarner> nah
[22:07] <jasoncwarner> k?
[22:07] <bryceh> there seems to be an out-of-memory issue when running on the livecd
[22:08] <bryceh> eventually this causes X to crash, so it gets reported as an X bug, but not sure where the leak actually is in the system
[22:09] <bryceh> it's not at the top of our list to work on, but seems pretty important
[22:09] <jasoncwarner> hmm..ok...keep us posted then....
[22:09] <jasoncwarner> how long after using it as a live cd does it crash?
[22:09] <bryceh> it would be nice if anyone is doing regular livecd testing if they could help narrow down what process is leaking all the memory
[22:09] <jasoncwarner> like...you know...10 hours or 5 minutes
[22:09] <jasoncwarner> well, I guess it probably depends on hardware...nm...
[22:09] <bryceh> it varies but seems to be from 1 minute to less than an hour
[22:10] <jasoncwarner> yeah, that would be pretty important then...
[22:10] <bryceh> what we don't know yet is what steps are needed to reproduce, so that alone would be useful to know
[22:10] <TheMuso> Hrm that could explain a weird crash I had yesterday when testing the installer mode of the live CD with accessibility.
[22:10] <jasoncwarner> bryceh: I'll see if I can get some testing on it...but we should talk to QA as well since they do quite a bit of livecd testing
[22:10] <TheMuso> What is weird is that was on a machine with 2GB RAM.
[22:10] <bryceh> ok cool
[22:11] <jasoncwarner> thanks, bryceh
[22:11] <jasoncwarner> Ok, anything else for eastern edition worth noting?
[22:11] <jasoncwarner> [TOPIC] AOB as it is officially known... :)
[22:11] <RAOF> :)
[22:12] <TheMuso> Was checking the travel related sites from the Aust government this morning, it appears Aussies do not need a VISA for Hungery.
[22:12] <TheMuso> Just thought I'd mention it, in case others hadn't checked.
[22:12]  * RAOF hadn't yet, thanks!
[22:12] <TheMuso> gah typo
[22:13] <jasoncwarner> and americans living here?  ;)
[22:13] <TheMuso> heh I don't know where you stand WRT that.
[22:13] <TheMuso> I guess you are still under the regulations of the US.
[22:14] <jasoncwarner> :)
[22:14] <jasoncwarner> anyway...if there is nothing else...
[22:14] <jasoncwarner> please fill in your details on the wiki
[22:14] <jasoncwarner> https://wiki.ubuntu.com/DesktopTeam/Meeting/2011-02-22
[22:14] <TheMuso> Oh, and since there are a few of us aussies going, we shoudl try and coordinate things such that we are on the same flight, at least if people want to.
[22:14] <jasoncwarner> and don't forget your WIs...getting close to FF and we A3 WIs are a bit sketchy...
[22:14] <jasoncwarner> please give them a look today and clear 'em out as you can.
[22:14] <RAOF> Yeah, that'd be a good idea.  What way are people going?  Syd→Heathrow→Budapest, or via Frankfurt?
[22:15] <pitti> good night everyone
[22:15] <bryceh> night
[22:15] <RAOF> night pitti
[22:15] <jasoncwarner> night pitti
[22:16] <jasoncwarner> yeah, would be intersted in route as well...haven't figured out which way I'm going yet...
[22:16] <jasoncwarner> [END MEETING] btw
[22:16] <TheMuso> Haven't looked myself either, which is why I made the suggestion.
[22:18] <RAOF> I was leaning towards via Heathrow; it's a bit more flight time, but the same total time, and Syd→Heathrow is an A380 rather than a 747.
[22:19] <TheMuso> Ooo that sounds very appealing.
[22:48] <seb128> tedg, bug #719591 seems another libdbusmenu issue which some users ran into
[22:48] <ubot2> Launchpad bug 719591 in libdbusmenu "nautilus crashed with SIGSEGV in g_type_check_instance_cast()" [High,Confirmed] https://launchpad.net/bugs/719591
[22:49] <seb128> tedg, is http://launchpadlibrarian.net/64415930/Stacktrace.txt enough to be useful?
[22:50] <chrisccoulson> seb128 - that looks very much related to your valgrind log :)
[22:50] <seb128> chrisccoulson, ok, feel free to assign this one to you as well if you want to work on it
[22:50] <seb128> or if you think it's the same bug
[22:50] <chrisccoulson> it all looks related to the CACHED_MENUITEM stuff in the new parser code
[22:51] <tedg> Yeah, there's some unref there.  I do think they're similar
[22:51] <chrisccoulson> i think the crash that mdz sees might still be a different issue though :/
[22:51] <seb128> which one? bug #720895
[22:51] <ubot2> Launchpad bug 720895 in libdbusmenu "bluetooth-applet crashed with SIGSEGV in g_variant_builder_add_value()" [High,Triaged] https://launchpad.net/bugs/720895
[22:51] <seb128> is that the similar one or a different?
[22:52] <seb128> oh you mean the crash is different from the valgring log?
[22:52] <chrisccoulson> seb128 - yeah, it looks unrelated at a first glance. but then, if there are memory errors, they could still all be related ;)
[22:52] <didrocks> good night everyone
[22:53] <seb128> 'night didrocks
[22:53] <chrisccoulson> 'night didrocks!
[22:55] <seb128> chrisccoulson, do you think you will have time to have a go at this issue before next week?
[22:55] <chrisccoulson> seb128 - yeah, i'm looking at those now
[22:55] <seb128> great
[22:55] <seb128> would be nice to have corruptions fixed for a3 so we can see what other issues remain
[22:56] <chrisccoulson> one of the nice things about working on firefox is not having to worry about all this reference counting stuff that you have to deal with in C + gobject ;)
[22:59] <robert_ancell> RAOF, did you just update some video stufff?
[22:59] <RAOF> No?
[23:00] <RAOF> Well, there's been a sync of libva recently.
[23:00] <robert_ancell> hmm, my video now crashes about 30s after login in compiz
[23:00] <RAOF> Since when?
[23:00] <robert_ancell> since I did a dist-upgrade this morning
[23:01] <RAOF> Bah.  The unity applications search would be more useful if it didn't always crash compiz :(
[23:02] <RAOF> Got an Xorg.0.log?  Also, describe “crashes” :)
[23:02] <robert_ancell> the same video problem I was describing last time
[23:03] <RAOF> Where Unity crashes when you hit alt-tab?
[23:03] <robert_ancell> no
[23:03] <robert_ancell> the strange lined video problem
[23:03] <robert_ancell> I'll take a photo next time it occurs
[23:04] <RAOF> If you hadn't updated for a while, this may be fallout of switching to r600g?
[23:06] <robert_ancell> did that happen automatically?
[23:06] <robert_ancell> glxinfo says I am running gallium
[23:06] <RAOF> Yes.
[23:08] <robert_ancell> I'm not seeing anything particularly bad in the logs
[23:08] <robert_ancell> I'll trigger it later today after I've got some work done
[23:08] <RAOF> Ta