[00:02] <RAOF> It'd be neat :)
[00:14] <jbicha> charlie-tca: have you looked to see what edubuntu is doing? I think they only replace the wallpaper but it's at least something
[01:07] <charlie-tca> jbicha: why does everyone except Unity have to make these things happen by little bits? There really should be a way for any of us to have a custom greeter, instead of just Ubuntu.
[01:11] <RAOF> Wasn't that what robert_ancell was saying?  You'd make xubuntu-greeter, and the xubuntu-desktop package would install that, and the postinst would frob lightdm-set-defaults?
[01:13] <charlie-tca> That's what I asked for. Hopefully we can make that happen now
[01:23] <robert_ancell> can a debian pacakge conflict with something that it provides?  I want to make lightdm-gtk-greeter-config-ubuntu provide lightdm-gtk-greeter-config but not allow any other configuration variant to be installed at the same time
[01:24] <micahg> robert_ancell: yes
[01:24] <micahg> robert_ancell: http://www.debian.org/doc/debian-policy/ch-relationships.html#s-conflicts
[01:25] <robert_ancell> charlie-tca, RAOF, micahg: does this look like it might solve the problem? http://paste.ubuntu.com/692688/
[01:25] <charlie-tca> micahg: ??
[01:26] <RAOF> robert_ancell: It wants a Replaces: too, right?
[01:26] <micahg> robert_ancell: you need a replaces as well, that only lets one at a time be installed (like a mail daemon) as opposed to like the display managers
[01:27] <robert_ancell> The replaces always confuses me, shouldn't the conflicts be sufficient?
[01:27] <charlie-tca> robert_ancell: thank you for your efforts
[01:27] <robert_ancell> I guess it replaces the existing one?
[01:27] <micahg> robert_ancell: replaces allows one package to replace a file in another package
[01:27] <robert_ancell> charlie-tca, np, I hate dpkg :)
[01:27] <RAOF> No; Conflicts tells apt to balk at installing it, Conflics+Replaces has special semantics.
[01:27] <RAOF> (As does Replaces+Breaks)
[01:28] <RAOF> Should this fundamentally be a debconf option?
[01:28] <RAOF> Like the x-display-manager doodad?
[01:28] <robert_ancell> RAOF, no, because the GTK greeter can't know how many configurations are out there
[01:29] <robert_ancell> it's like installing gnome-settings-daemon and it asking you "Are you using this with Unity or GNOME or both?"
[01:29] <micahg> robert_ancell: I'd suggest a file like default.conf in a .d which says which one is in use
[01:29] <RAOF> Well, the gtk greeter could grow a capability, like what micahg suggested.
[01:30] <micahg> then a debconf option can write to that file
[01:30] <RAOF> conflicts/replaces on a configuration file might get weird; I'm not sure.
[01:30] <RAOF> But you might start to fight dpkg's conffile handling.
[01:32] <robert_ancell> micahg, do you mean the greeter loads /etc/lightdm/lightdm-gtk-greeter.conf.d?
[01:32] <RAOF> It would be that the postinst scans /etc/lightdm/lightdm-gtk-greeter.conf.d and presents each of the included files as a possible default, then sets that one.
[01:33] <micahg> robert_ancell: it could load whatever greeter that /etc/lightdm/lightdm-gtk-greeter.conf.d/default.conf says to
[01:33] <micahg> or do whatever gdm/lightdm does for its alternatives
[01:33] <robert_ancell> micahg, that's adding layers on layers.  Why doesn't it just load it's one configuration, and a higher level decides what that should be?
[01:34] <micahg> robert_ancell: how does lightdm register as the default dm?
[01:34] <RAOF> You could do that with alternatives; the GL packages do it that way, to provide their appropriate ld.so.conf (among other things).
[01:35] <RAOF> That's also how plymouth themes work, IIRC.
[01:35] <RAOF> (Although with plymouth I don't think you're alternitivesing a conffile)
[01:36] <robert_ancell> micahg, there's a difference between the daemon (lightdm) and the greeters (lightdm-gtk-greeter).  The daemon needs to register with the system to ensure it's the only one on startup, but the greeters are just like applications
[01:36] <micahg> robert_ancell: I understand, but we can reuse the same principle
[01:36] <micahg> only allow one at a time to be primary
[01:37] <micahg> and give users an easy way to switch between them
[01:41] <micahg> that would absolve the need for extra layers
[01:56] <robert_ancell> ok, I can confirm having the two packages works with dpkg conffiles behaviour
[02:10] <robert_ancell> charlie-tca, does bug 845549 make sense?
[02:10] <ubot2> Launchpad bug 845549 in lightdm "Do not ship /etc/lightdm/lightdm-gtk-greeter.conf" [High,Fix committed] https://launchpad.net/bugs/845549
[02:16] <smspillaz> RAOF: question, were we planning to merge in my xserver patch this week ?
[02:17] <RAOF> smspillaz: It's in the xserver git tree.  Does it want to be in before or after beta 2?
[02:17] <smspillaz> preferably before since it fixes a fairly important bug
[02:17] <RAOF> (ie: The next upload will have it.  When would you like it ?)
[02:17] <RAOF> Got a LP handle on that?
[02:17] <smspillaz> sure, hang on
[02:18] <RAOF> Hm:  Qt says ?ConfigureWindow window=0x02400010 values={width=65535 height=65535}?.  This is unlikely to end well.
[02:18] <smspillaz> https://bugs.launchpad.net/ubuntu/+source/unity/+bug/847967
[02:18] <ubot2> Ubuntu bug 847967 in unity "A minimized window 'remains' behind on the desktop if /apps/compiz-1/plugins/unityshell/screen0/options/show_minimized_windows is set to true" [High,In progress]
[02:18] <smspillaz> RAOF: sounds like a stupid application
[02:19] <smspillaz> RAOF: interestingly enough, we should be able to handle that case in compiz now (if the server doesn't BadAlloc)
[02:19] <RAOF> smspillaz: That's bug It's bug #805303
[02:19] <ubot2> Launchpad bug 805303 in xorg-server "Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed with the default qt4 gui" [Critical,Confirmed] https://launchpad.net/bugs/805303
[02:19] <smspillaz> except that I haven't had any luck convincing distro to turn support for windows > max texture size on
[02:19] <RAOF> The server, would you believe it, doesn't particularly like RENDER requests against that window :)
[02:19] <smspillaz> wow
[02:20] <smspillaz> yeah I did notice problems with vlc the other day
[02:20] <RAOF> smspillaz: Doesn't unity break compiz's max texture size support anyway?
[02:20] <smspillaz> RAOF: sort of
[02:20] <smspillaz> RAOF: you can still have windows > mts, but not a screen size > mts
[02:20] <smspillaz> because we didn't get time to implement multiple textures for the framebuffer object
[02:21] <smspillaz> maybe we can do it as part of this week's bugs
[02:21] <RAOF> By "Screen size" you mean "Size of a single RandR display", right?
[02:21] <charlie-tca> robert_ancell: yes, it makes sense to me. Thank you very much.
[02:21] <smspillaz> RAOF: no, DefaultScreen (dpy)->width/height :)
[02:22] <RAOF> smspillaz: So, when you say ?sort of?, what you *actually* mean is ?yes, absolutely? :P
[02:23] <RAOF> Although I guess there may sometimes be a use for a window bigger than the total area of your displays.
[02:23] <smspillaz> RAOF: nope, I meant sort of
[02:23] <smspillaz> RAOF: you can have *windows* larger than your maximum texture size
[02:23] <smspillaz> the total output on your screen will be limited to your max texture size
[02:24] <smspillaz> however, the plugin which provides support for this is off by default
[02:25] <RAOF> Correct me if I'm wrong, but the current ?Unity sort of breaks this? means that having multiple displays, where one axis is > max_texture_size, will still catastrophically fail.  Right?
[02:25] <smspillaz> yes, correct
[02:26] <RAOF> Turning on that plugin before that's fixed doesn't really seem like a huge win :)
[02:26] <smspillaz> next cycle we'll make it so that nux's framebuffer objects support binding over multiple textures
[02:26] <smspillaz> RAOF: well, if some stupid client decides to create a huge window that doesn't hit a BadAlloc then it will work
[02:26] <RAOF> What will currently happen?
[02:27] <RAOF> They'll get a blank app window?
[02:27] <smspillaz> compiz fails to bind the texture and you get a white window
[02:27] <RAOF> I guess that's something that'd be good to be avoided.
[02:27] <smspillaz> oh and the decorator will crash since it pixmap type decorations which exceed your maximum texture size are not supported so it will try to switch to the legacy reparenting mode
[02:28] <smspillaz> except that the legacy mode is ... essentially unmainted
[02:28] <smspillaz> *unmaintained
[02:29] <smspillaz> RAOF: also, I found out that xorg-devel is suprisingly higher traffic than I thought
[02:29] <RAOF> Hah!  Yes.e
[02:30] <smspillaz> RAOF: I get the impression that you are still somewhere where typing is an inconvenience
[02:30] <RAOF> No; I'm just bouncing IRC around the world.
[02:31] <smspillaz> RAOF: oh, still in the states ?
[02:31] <RAOF> No, just using a different IRC bouncer.
[02:31] <smspillaz> ah ok
[02:31] <smspillaz> RAOF: anyways, just came in to poke you about that xserver patch
[02:31] <smspillaz> :)
[02:31] <RAOF> Wow.  Is a 65535x65535x32bpp pixmap *really* 16 GB?
[02:32] <smspillaz> RAOF: 16 GiB more likely
[02:32] <RAOF> Well, yeah.
[02:33] <RAOF> smspillaz: Ok.  I'll finish testing the xserver upload, add that bug reference, and upload.
[02:33] <smspillaz> scwheeeeeeeet
[02:33]  * smspillaz watches the number of bug reports about "OMG INVISIBLE WINDOWS" skyrocket down
[02:33] <smspillaz> RAOF: oh for testing purposes
[02:34] <smspillaz> RAOF: if you have unity compiled from source
[02:34] <smspillaz> if you run unity/tests/test-input-remover/test-input-remover
[02:34] <smspillaz> if it complains about a BadValue
[02:34] <smspillaz> then its not working
[02:34] <RAOF> Thanks for that!
[02:34]  * RAOF goes to compile unity from source, and run that against the old xserver.
[02:34] <smspillaz> well, a BadValue
[02:34] <smspillaz> then it will hang
[02:34] <smspillaz> RAOF: err
[02:35] <smspillaz> RAOF: so you may want to just run the test independently
[02:35] <smspillaz> compiling unity takes a very long time
[02:35] <smspillaz> longer than the X server
[02:35] <smspillaz> so just go into tests/test-input-remover/
[02:35] <RAOF> Fortunately, dual-core sandybridge i5 + a reasonably fresh ccache ;)
[02:35] <smspillaz> and then mkdir build ; cd build ; cmake .. ; make ./test-input-remover
[02:35] <RAOF> Although that sounds easier :)
[02:35] <smspillaz> RAOF: I'm going to fix that at the sprint
[02:36] <smspillaz> err UDS
[02:37] <smspillaz> RAOF: ... you don't want to know the crazy thing I am doing to fix that bug btw :/
[02:38] <smspillaz> in order to avoid abi breaks in compiz ... I'm fixing the server
[02:38] <smspillaz> yeah
[02:38] <smspillaz> we're awesome like that
[02:38] <RAOF> It *sounds* like your XShaping the window away, and then lying to the clients about it?
[02:38] <smspillaz> RAOF: sort of
[02:38] <smspillaz> RAOF: we XShape the input away but disable event generation while we're doing it, since we listen for XShape events ourselves
[02:39] <smspillaz> but then core needs to know when the XShaping actually happened so that it will update the parent window shape correctly if the client resizes itself while hidden
[02:39] <smspillaz> so we tell core about the XShaping and ignore any events that come from send_event on our side
[02:42] <RAOF> Oh, right.  And that's when the client can find out about the XShape change if it wants to.
[02:42] <smspillaz> well
[02:42] <smspillaz> it gets the notification twice'
[02:43] <smspillaz> but its the same notification, so meh
[02:43] <smspillaz> xsendevent is really dangerous though
[02:43] <smspillaz> its only ever safe to send events with values that come directly from the x server itself
[02:44] <smspillaz> I wrote about it on my big braindump on window stacking (http://smspillaz.wordpress.com/2011/09/18/braindump-how-to-get-window-stacking-right/)
[02:44] <RAOF> This is one of many pieces of the X server I'm blissfully unaware of.
[02:44] <smspillaz> RAOF: like many other things, XSendEvent is a hack
[02:44] <smspillaz> the server does no checks whatsoever except on the event type and client message format
[02:45] <smspillaz> you can send *whatever you like* to a client
[02:45] <smspillaz> for example, you can send a DestroyNotify to a client saying one of its windows was destroyed
[02:45] <smspillaz> and the client will probably not know any better
[02:46] <smspillaz> RAOF: even if a client specifically requested not to receive certain events, you can send them anyways
[02:46] <RAOF> Fun!
[02:47] <smspillaz> and the client will still get them
[02:47] <RAOF> What could possibly go wrong!
[02:47] <smspillaz> anyways, I need to study for this class
[02:47] <smspillaz> RAOF: so much possible breakage :/
[02:49] <smspillaz> apparantly java is being stupid again: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/843530
[02:49] <ubot2> Ubuntu bug 843530 in compiz "java6 popup window buttons are obscured in compiz" [Undecided,Confirmed]
[02:57] <RAOF> Yay!
[03:10] <jasoncwarner_> hey robert_ancell ... any luck deciphering what is going on with the lag in Unity-greeter?
[03:11]  * jasoncwarner_ so curious what it could be! :)
[03:11] <robert_ancell> jasoncwarner_, one of the bug reporters seems to have some indication it might be xrandr related
[03:11] <robert_ancell> jasoncwarner_, I'll make you a package with gnome-settings-daemon disabled and let's see if that makes a difference
[03:15] <jasoncwarner_> robert_ancell: ah...ok...send it and I'll give it a shot
[03:17] <RAOF> Huh.  Does this only happen on Intel systems?  Keith was saying that there's a known-regression in the VGA probing which makes it hugely pessimistic (and where the 1sec stop in X server startup comes from).
[03:18] <robert_ancell> jasoncwarner_, ok, sent
[03:19] <robert_ancell> RAOF, people are mentioning intel
[03:19] <robert_ancell> RAOF, have you ever seen the problem?
[03:19] <RAOF> Yes.
[03:19] <robert_ancell> RAOF, can you run your X magic on it to see what the greeter is doing to X?
[03:19] <RAOF> Also, it seems to correlate with the high Xserver CPU usage during the bootchart.
[03:20] <RAOF> robert_ancell:  Where can I insert my shim?
[03:20] <robert_ancell> RAOF, set display-setup-script in SeatDefaults
[03:21] <robert_ancell> I'm not 100% sure it's working in the current version, but it's worth trying.  It definitely works on the next version
[03:21] <RAOF> Actually, I could probably just replate /usr/sbin/unity-greeter with a nice little script?
[03:22] <robert_ancell> RAOF, yes, that would do it
[03:23] <robert_ancell> RAOF, or edit /usr/share/xgreeters/unity-greeter.deskto
[03:23] <robert_ancell> RAOF, or edit /usr/share/xgreeters/unity-greeter.desktop
[03:23] <jasoncwarner_> robert_ancell: got it...be back in a few after testing...
[03:23] <Sarvatt> RAOF: what system did you see it on?
[03:24] <RAOF> Sarvatt: Everyone's favourite GM45!
[03:24] <RAOF> I'm not sure about the sandybridge.
[03:24] <Sarvatt> oh ok, was going to be confused if you said the e6420 because thats fine here
[03:24] <Sarvatt> so yet another lenovo to the mix
[03:29] <jasoncwarner_> hey robert_ancell
[03:29] <jasoncwarner_> http://paste.ubuntu.com/692730/
[03:30] <jasoncwarner_> this was noticeably better, actually...there were still moments where input locked for a split second, but overall experience was quite a bit smoother
[03:31] <robert_ancell> jasoncwarner_, yeah, that looks like it.  So it's something that gnome-settings-daemon is doing, possibly the xrandr interaction with X?
[03:31] <robert_ancell> this is a *lot* better: [+0.74s] DEBUG: user-list.vala:1248: Rendered first frame
[03:32] <RAOF> gnome-settings-daemon *does* have a tendency to probe xrandr multiple times; if it's blocking waiting for that, and VGA probe is taking ~1sec, then that could be our candidate.
[03:42] <jasoncwarner_> robert_ancell: do we lose anything by not having g-s-d starting up there? or did you make it start threaded or something?
[03:43] <robert_ancell> jasoncwarner_, it's already started in the background (it's another process).  we need it for all the power management, X settings etc
[03:44] <robert_ancell> RAOF, the unity-greeter logs just seem to show really slow response times from the X server - could g-s-d be blocking the X server with these requests?
[03:52] <pitti> Good morning
[03:52] <pitti> tremolux: thanks, will sponsor them
[03:52] <tremolux> pitti: hey! thanks :)
[03:53] <pitti> cyphermox: I have no idea what DUID is, I was hoping that cjwatson could review this (as he dealt with IPv6 a bit)
[03:53] <tremolux> pitti: it's tzdata season ;)
[03:55] <pitti> tremolux: indeed, and we skipped a few, too
[03:57] <TheMuso> Morning pitti.
[04:00] <jbicha> good morning
[04:03] <jasoncwarner_> morning pitti
[04:03] <pitti> hey TheMuso, hey jasoncwarner_
[04:03] <jasoncwarner_> how was the weekend?
[04:04] <pitti> jasoncwarner_: pretty nice, but a bit trying as well - lots of sightseeing, museums, etc. with my in-laws :)
[04:09] <pitti> RAOF: do you plan to update gnome-color-manager from 3.1.2 to 3.1.91?
[04:09] <pitti> jbicha: do you want to update gnome-shell, or shall I look into this?
[04:09]  * pitti grabs anjuta for now
[04:12] <pitti> RAOF: ah right, I noted on the pad: it needs colord 0.1.12, do we want that in oneiric?
[04:15] <jbicha> pitti: gshell needs caribou
[04:16] <pitti> ah
[04:16] <jbicha> it doesn't require caribout to actually work, just that it's installed :-)
[04:29] <RAOF> pitti: If something needs colord 0.1.12 I can do that; it's pretty bugfixy.
[04:29] <RAOF> It's pretty much ready to go for Debian already.
[04:33] <pitti> RAOF: the new g-color-mgr does, yes
[04:33] <RAOF> robert_ancell: Oh, hey!  Unity-greeter does some fallback detection now?
[04:34] <robert_ancell> RAOF, no?
[04:34] <RAOF> robert_ancell: Then why is it (a) authenticating as a DRI2 client, and (b) grabbing the list of GL extensions supported?
[04:35] <robert_ancell> RAOF, oh, it runs the nux tester in the background to save time when logging in
[04:36] <RAOF> Ah, ok.
[04:39] <pitti> TheMuso: for bug 836798, would it be possible to somehow make at-spi and at-spi2 coexist?
[04:39] <ubot2> Launchpad bug 836798 in at-spi2-atk "natty to oneiric upgrade failed: Could not perform immediate configuration on 'python-pyatspi2'" [High,Confirmed] https://launchpad.net/bugs/836798
[04:39] <pitti> TheMuso: I guess porting the remaining at-spi apps to 2 is not viable for oneiric, or is it?
[04:41] <TheMuso> pitti: Not viable no. Most of the at-spi v1 and v2 stacks are co-installable, we just need a way to remove at-spi v1 off eople's systems unless they use apps that are not part of the default install.
[04:42] <pitti> TheMuso: the cleanup can't be enforced with a Breaks:/Conflicts: while we still have rdepends
[04:43] <pitti> but cleaning up doesn't matter so much, update-manager will deal with that once they go to universe
[04:43] <pitti> TheMuso: but I thought the two packages shared a file?
[04:43] <TheMuso> pitti: Right, I see that now, so we're going to have to remove all breaks/confclits from at-spi2-core and libatk-adaptor, and remove at-spi v1 another way
[04:43] <TheMuso> pitti: pyatspi is the only package that shares a file.
[04:43] <pitti> TheMuso: right, so we need to solve that one
[04:44] <TheMuso> And pyatspi's API has not changed.
[04:44] <TheMuso> so orca for example can use pyatspi for v1 or v2.
[04:44] <pitti> TheMuso: can you work on that today/tomorrow, so that we can get working upgrades to b2?
[04:44] <pitti> oh, nice
[04:44] <TheMuso> pitti: Yes I can upload fixes today for those.
[04:44] <TheMuso> But the issue of old at-spi on user's systems still remains.
[04:44] <pitti> TheMuso: see above: once they go to universe, u-m will clean them up
[04:45] <TheMuso> oh ok
[04:45] <pitti> but as they are (or will be) co-installable anyway, having them on the system sohuldn't break anything?
[04:45] <TheMuso> So its only at-spi2-atk that needs to be fixed, will do that now.
[04:46] <pitti> TheMuso: do libatk-adaptor and at-spi share any files, like /usr/lib/gtk-[23].0/modules/libatk-bridge.so ?
[04:47] <pitti> but if they are compatible, then I guess libatk-adaptor can just replaces: at-spi, and then the new one will be used
[04:47] <TheMuso> pitti: Oh yes of course. libatk-adaptor and at-spi share /usr/lib/gtk-2.0/modules/libatk-bridge.so
[04:49] <pitti> TheMuso: that was my question -- if libatk-adaptor takes over that one, will at-spi still work?
[04:49] <TheMuso> pitti: no
[04:50] <pitti> TheMuso: does the file name need to be exactly that? or could it be called libatk-bridge-2.so?
[04:50] <TheMuso> pitti: It could be called something else, but then we would need to add extra code to unity to support 2 different modules./
[04:50] <TheMuso> And gnome-shell/clutter as well.
[04:51]  * pitti checks rdepends of at-spi: gok, dasher, python-pyatspi, and python-strongwind
[04:52] <pitti> TheMuso: i. e. mainly gok and dasher; do either of these have GNOME 3 versions or replacements?
[04:54] <TheMuso> pitti: gok is no longer maintained and is replaced by Caribou, however I don't think thats packaged yet.,
[04:54] <TheMuso> As for dasher, its still maintained, but I am not sure if it has any code upstrea to support at-spi v2 yet.
[04:54] <pitti> it's being packaged, but not yet in oneiric
[04:54] <TheMuso> ok
[04:54] <pitti> TheMuso: could we change gok and dasher to look for /usr/lib/gtk-2.0/modules/libatk-bridge-atspi.so instead?
[04:55] <pitti> TheMuso: and rename the module in the old at-spi package?
[04:55] <pitti> TheMuso: then the breaks:/replaces can become versioned
[04:55] <TheMuso> pitti: Its not up to those apps to load the atk module. The atk module is usually dealt with by gtk itself
[04:55] <TheMuso> either via GTK_MODULES env variable or gnome-settings-daemon taking care of it these days
[04:55] <pitti> TheMuso: oh, I thought you said you needed to change unity/shell etc. to look for a changed name
[04:56] <TheMuso> pitti: Yes, because unity and gnome-shell do not use GTK for some of their bits, i.e unity uses nux/compiz, and shell uses clutter.
[04:56] <TheMuso> So they have to load the module manually.
[04:56] <pitti> TheMuso: so if we rename the old module instead, would that be any simpler?
[04:57] <TheMuso> I don't think so, because we would still need code in shell/unity to support the different module name, because if a user still wants to use gok/dasher, they need to use the entire older stack.
[05:00] <broder> RAOF, robert_ancell: i've seen symptoms in the past where an xrandr doing an actual probe will cause the entire UI to hang
[05:01] <broder> primarily on intel systems, though occasionally on other drivers
[05:01] <pitti> TheMuso: hm; so it seems to me we need to push for caribou to get into oneiric, and we need to drop dasher?
[05:02] <TheMuso> pitti: I don't know about dahser, I believe people still use it...
[05:02] <pitti> as the stacks seem to be fundamentally not co-installable then
[05:02] <TheMuso> dasher
[05:02] <TheMuso> Or, we could disable dasher's at-spi support, because afaik its an optional extra.
[05:02] <pitti> right, but unless we can find a way to make them co-installable, there's not much point having rdepends to the old one
[05:03] <pitti> ah, if it's still useful with that, sure
[05:04]  * TheMuso checks that to be sure
[05:05] <RAOF> robert_ancell: http://paste.ubuntu.com/692763 is available for your ponderance, if you wish.  It's a unity-greeter with xtrace running with CLOCK_MONOTONIC timestamps.  http://paste.ubuntu.com/692764 is the accompanying Xorg.0.log; it looks a lot like the ~500ms stutters in X protocol timestamps correspond to the EDID probing in the Xorg.0.log, but unity-greeter (or anything it spawns) does not seem to be doing a lot of XRandR calls.
[05:29] <TheMuso> pitti: Ok got a build of dasher here with at-spi disabled.
[05:29] <TheMuso> So dasher can still be used sans at-spi.
[05:30] <DBO> ping RAOF
[05:30] <RAOF> DBO: Pong
[05:30] <DBO> this week
[05:30] <DBO> the nvidia bug
[05:30] <DBO> must die
[05:30] <DBO> do you have *any* theories on how we might accomplish this task?
[05:31] <RAOF> Didn't you have an incantation like ?recreate all the FBOs? to make it work?
[05:32] <RAOF> Failing anything else, you *could* check for the existence of the NV-GLX extension and just /restart Unity/ when recieving the "resumed" signal!
[05:33] <RAOF> That's totally ugly, but better than the alternative.
[05:34] <RAOF> And has the advantage of not messing things up for !nvidia.
[05:35] <pitti> TheMuso: nice! so do we have a plan now? drop the breaks: to fix upgrades for b2, and finish the caribou packaging to get a gok replacement?
[05:35] <pitti> jbicha: ^ does that seem realistic?
[05:36] <didrocks> good morning
[05:36] <RAOF> DBO: Would I be correct in assuming that it'd be a huge pain in the arse to tear down your GL context on resume and rebuild it? :)
[05:36] <pitti> bonjour didrocks, ca va? had a nice weekend?
[05:36] <DBO> RAOF, yes
[05:37] <DBO> I did rejigger the FBO's on resume
[05:37] <DBO> no help
[05:37] <didrocks> guten morgen pitti. I'm fine thanks. Was the week-end with all monuments opened to the public, so some nice walk in the city (and too much great Lyon's food ;)). And you?
[05:37] <RAOF> DBO: Oh, that's right.  That _used_ to work, but now doesn't?
[05:37] <DBO> actually we're not sure what happened
[05:37] <DBO> didrocks, how did you weekend go?
[05:39] <jbicha> do people depend on gok instead of onboard? because caribou standalone tries to place the keyboard next to text input
[05:39] <TheMuso> pitti: SOunds good to me, and I'll upload dasher sans at-spi support.
[05:39] <didrocks> DBO: was nice, thanks, how was yours? (you shouldn't be working, still on week-end for you BTW :p)
[05:39] <jbicha> which doesn't work for Firefox or full-screen terminals so caribou may be a bit rough
[05:40] <TheMuso> jbicha: Well we already use onboard as the primary OSK.
[05:40] <DBO> didrocks, I want to know how the compiz testing went for you :)
[05:40] <TheMuso> So I tink only people who really need it will use it.
[05:41] <pitti> didrocks: heh, similar; we had our parents as guests since Thursday, so we did long city/sightseeing/museum tours
[05:41] <RAOF> DBO: I was sure you had done some experimentation on how to make things work :/
[05:41] <didrocks> DBO: I didn't get any weird stacking issue (but I didn't get a lot of issues before). I didn't take latest c-p-m though
[05:41] <pitti> brb, breakfast
[05:41] <jbicha> TheMuso: right, I was just wondering if gok was popular or if people were more or less content with onboard
[05:42] <DBO> RAOF, I did
[05:42] <TheMuso> jbicha: TO be honest, I haven't heard either way, but I know onboard is used.
[05:42] <DBO> RAOF, I was sure recreating them worked last cycle
[05:42] <DBO> it doesn't this time
[05:42] <TheMuso> Haven't heard anyone using gok recently
[05:42] <DBO> thats all I know
[05:42] <DBO> didrocks, so PPA today?
[05:43] <didrocks> DBO: yeah, I saw some new branches proposed for merging though by smspillaz, is there a new tarball needed?
[05:43] <DBO> you should ask him I guess
[05:44] <jbicha> pitti: yes, gok has been abandoned upstream so we could drop it & hope that caribou starts working again
[05:54] <smspillaz> didrocks: DBO no new tarball needed
[05:54] <smspillaz> that's just other stuff I was hacking around with
[05:54] <DBO> smspillaz, excellent
[05:54] <DBO> didrocks, roll that shit up :)
[05:54] <didrocks> smspillaz: I heard about the new c-p-m is needed for a change in the animation plugin, is that true?
[05:55] <DBO> yes
[05:55] <didrocks> smspillaz: FYI, we rollbacked the ABI number change you did as it wasn't needed and we don't want free ABI bump at this stage
[05:55] <smspillaz> didrocks: no problem
[05:56] <didrocks> smspillaz: I guess robert carr checked that, but can I have your +1 as well that the window ws switcher change is in the new c-p-m as well?
[05:56] <didrocks> smspillaz: (and finally, cherry on the top, can I get the latest rev commit id from where you make dist? I didn't get them and I prefer that than a date for versionning the package)
[05:57] <DBO> didrocks, thank you sir for your efforts today
[05:57] <DBO> goodnight :)
[05:57] <smspillaz> didrocks: from cpm or core ?
[05:57] <didrocks> DBO: yw! have a good night :)
[05:57] <didrocks> smspillaz: both :-)
[05:58] <smspillaz> ok
[05:58] <RAOF> smspillaz: Is your unity fix for 847967 in the archive?
[05:58] <didrocks> smspillaz: (and +1 on cpm containing the ws switcher change?)
[05:59] <smspillaz> RAOF: yes
[06:00] <didrocks> smspillaz: if so, please change the bug status to fix released for every components
[06:00] <RAOF> smspillaz: Why is the bug not set to ?Fix Released? then, and why does it not appear to work?
[06:00] <smspillaz> RAOF: it doesn't work ?
[06:00] <smspillaz> that's nice
[06:01] <smspillaz> RAOF: does the test result in a BadValue ?
[06:01] <RAOF> smspillaz: test-input-remover works fine; unity still really hates minimising.
[06:01] <smspillaz> :/
[06:01] <smspillaz> RAOF: is this with the version you've compiled ?
[06:01] <smspillaz> since it works fine here
[06:02] <RAOF> smspillaz: This is with the version of unity that's in the archive.
[06:02] <smspillaz> *shrug* ok, maybe it isn't in the archive
[06:02] <RAOF> Which is why I first asked "is the fix for unity in the archive" :)
[06:02] <smspillaz> didrocks: when was unity last updated ?
[06:02] <didrocks> smspillaz: as usually, Thursday evening
[06:02] <RAOF> Because there's not much point fixing the X server for beta2 if unity isn't fixed.
[06:02] <smspillaz> RAOF: can you try compiling unity from source and see if you still get the problem ?
[06:02] <didrocks> smspillaz: can I get the revisions please and the confirmation I'm asking?
[06:03] <smspillaz> didrocks: yes yes, just give me a minute
[06:03] <didrocks> (if the bug status was changed when the fix has been in, we would know for sure if it's in the archive or not…)
[06:04] <RAOF> :)
[06:04] <smspillaz> right, it's more a matter of, I can't remember when I actually merged in the fix for that
[06:04] <smspillaz> RAOF: can you compile from source and check? I need to know whether it's broken or not in the archive
[06:05] <didrocks> smspillaz: hence why I remind everyone for the past 10 month to set the bug as "fix committed" once merging it
[06:05] <smspillaz> if it's broken, well then painful times ahead for me
[06:05] <RAOF> smspillaz: Yup.  Building now.
[06:05] <smspillaz> thanks
[06:06] <smspillaz> didrocks: I need to resync the cpm branch, once that's done I'll get you the revids
[06:06] <didrocks> smspillaz: ok thanks, and please check that the tarball have the ws switcher change
[06:07] <smspillaz> didrocks: did they not have it last time ?
[06:07] <didrocks> smspillaz: not sure what is "last time", just a question if the latest tarball you rolled on Thursday evening contains the ws switcher changed we distro-patch in ubuntu
[06:08] <smspillaz> didrocks: yes, it contains it
[06:08] <didrocks> RAOF: smspillaz: easier than recompiling unity, looking at the trunk:  http://paste.ubuntu.com/692796/
[06:09] <didrocks> this is since last release
[06:09] <didrocks> smspillaz: thanks for the info!
[06:09] <didrocks> seems the smspillaz's branch is indeed released
[06:09] <smspillaz> great
[06:09] <smspillaz> RAOF: which windows does it not work with ?
[06:10] <RAOF> smspillaz: gedit
[06:10] <smspillaz> ok
[06:10] <smspillaz> I'll recompile my x server and see what's happening then
[06:11] <smspillaz> since it got clobbered by the last dist-upgrade I did
[06:11] <RAOF> Or, rather more specifically, *maximised* windows.
[06:11] <pitti> TheMuso: sorry, rejecting at-spi2-atk; the Replaces: is still necessary, otherwise dpkg will break on the file conflict
[06:11] <pitti> TheMuso: can you please reupload?
[06:11] <TheMuso> pitti: whoops of course, thanks.
[06:12] <RAOF> smspillaz: Hm, there also sometimes seems to be some visual corruption left behind; fragments of the minimize animation.
[06:13] <pitti> smspillaz, RAOF: is the unity task in bug 847967 still relevant?
[06:13] <ubot2> Launchpad bug 847967 in unity "A minimized window 'remains' behind on the desktop if /apps/compiz-1/plugins/unityshell/screen0/options/show_minimized_windows is set to true" [High,In progress] https://launchpad.net/bugs/847967
[06:13] <pitti> or is it exclusively an X.org workaround?
[06:13] <RAOF> pitti: This is exactly what we're talking about now :)
[06:13] <pitti> ah, sorry
[06:13] <RAOF> There's a mandatory xorg workaround, but Unity also needs a fix.
[06:13] <pitti> I wonder if we should get this into b2 and accept now
[06:13] <pitti> i. e. more testing vs. regression potential
[06:13] <RAOF> Yeah.
[06:13] <smspillaz> RAOF: it really seems like this branch wasn't merged :/
[06:14] <pitti> the change looks like a workaround, and it's not obvious to me that it wouldn't break other software?
[06:14] <smspillaz> RAOF: are you compiling from source ?
[06:14] <smspillaz> pitti: no, it wont
[06:14] <RAOF> It's a pretty simple patch, been reviewed upstream, and shouldn't result in changing client-visible protocol.
[06:14] <RAOF> smspillaz: Yup, I've just built from source.
[06:15] <pitti> i. e. it essentially disables the 8th bit of the event type; this is kind of a protocol change?
[06:15] <RAOF> That bit is set by XSendEvent.
[06:16] <RAOF> Well, I it *does* change the client-visible protocol.  I guess some software *might* rely on the fact that using XSendEvent for some event types will cause an XError, but I can't imagine why :)
[06:16] <RAOF> So it's a protocol change in that requests which should succeed and previously generated an XError now succeed.
[06:16] <smspillaz> RAOF: great, it broke again, gosh this thing is fragile
[06:17] <RAOF> That's just what we want to hear at beta-2!
[06:17] <smspillaz> who said that minimized window thumbnailing was easy
[06:18] <RAOF> Ah.  Would I be correct in assuming that having minimised windows when starting unity is still a bad idea?
[06:18] <smspillaz> ok, so it s broken for me because dpkg epic failed at configuring my server :/
[06:18]  * smspillaz grabs the source again and recompiles
[06:19] <RAOF> Or, rather, would I be correct in assuming that you are fully cognisant of the fact that starting unity while there are minimised windows results in those windows being entirely inaccessible?
[06:19] <smspillaz> RAOF: that should work fine
[06:20] <RAOF> Ah.  Well, it doesn't.
[06:20] <smspillaz> RAOF: maybe it's fixed on my local verison
[06:20] <smspillaz> *shrug* I don't know, we have like a million branches we're working on in parallel
[06:20] <RAOF> Compiz is *highly* confused; the alt-tab switcher knows that there's a window, but it can't get it, so it presents a big blank window (with the correct title).
[06:20] <RAOF> Selecting it doesn't raise it, cliciking on the launcher icon does nothing, etc.
[06:21] <smspillaz> ok, stop complaining and let me look into this please
[06:23] <RAOF> Wilco.  Give a holler if you'd like some testing.
[06:23] <ricotz> pitti, good morning
[06:24] <ricotz> pitti, while using the pre-generated docs for glib, shouldnt the libglib2.0-doc.install use them directly? http://paste.debian.net/plain/130929
[06:25]  * smspillaz debuilds his xserver again
[06:25] <smspillaz> RAOF: to double check, you don't have a locally installed old version of unity which doesn't have this fix applied ?
[06:26] <RAOF> Well, I do have a locally installed unity, but it should be the unity I just built and installed.
[06:26] <smspillaz> ok
[06:26] <RAOF> Is there an easy way to check?
[06:26] <smspillaz> ls ~/.compiz-1/plugins
[06:26] <RAOF> Yeah, they're all current.
[06:27] <smspillaz> ok, let me have a look into this
[06:27] <smspillaz> this is very strange though, since it was working *fine* like 4 days ago
[06:27] <pitti> ricotz: sorry, I don't understand the question -- it does use dh_install to install them from the source?
[06:30] <RAOF> smspillaz: Sorry to rain on your parade :/
[06:30] <RAOF> Bah!  Unity!  Stack the switcher *above* everything else :(
[06:32] <ricotz> pitti, i mean the libglib2.0-doc.install looks for "installed" docs, not sure why they are got installed after a reconfigure without --enable-gtk-docs
[06:33] <smspillaz> RAOF: .... we should have merged my stacking fixes branch in last week
[06:33] <ricotz> pitti, libgtk-3-doc.install is doing it this way like i pastebined
[06:33] <smspillaz> of course, given the recent trend of events, it will probably fix it for me and nobody else
[06:34] <rickspencer3> RAOF, hey ...
[06:34] <RAOF> rickspencer3: Yo yo!
[06:34] <pitti> ricotz: --enable-gtk-docs was only temporary; it has always been the default, it just temporarily got broken
[06:35] <rickspencer3> RAOF, I think I'm going to buy a new laptop today
[06:35] <pitti> ricotz: upstream makefiles actually install the pre-generated docs into /usr/share/ etc. properly
[06:35] <pitti> hey rickspencer3
[06:35] <rickspencer3> I was planning to get one with a proprietary graphics chip ... to ahve the "real" user experience
[06:35] <RAOF> smspillaz: GAHK!  I seem to be pulling from the Ubuntu branch rather than upstream.  Sorry.
[06:36] <smspillaz> hahahahaahhahahaahahahahahahaaha
[06:36] <didrocks> RAOF: the stacking issue is not a unity issue, it's a compiz one, waiting for the revids to push that in a ppa
[06:36] <didrocks> (some fixes)
[06:36] <RAOF> smspillaz: Building upstream now.
[06:36] <smspillaz> RAOF: by "upstream" what do you mean ?
[06:36] <didrocks> RAOF: unity? did you see my comment above?
[06:36] <smspillaz> unity or compiz ?
[06:37] <RAOF> smspillaz: Unity, lp:unity.  For the minimise issue.
[06:37] <didrocks> :/
[06:38] <didrocks> 08:08:58      didrocks | RAOF: smspillaz: easier than recompiling unity, looking at the trunk:  http://paste.ubuntu.com/692796/
[06:38] <didrocks> 08:09:09      didrocks | this is since last release
[06:38] <didrocks> 08:09:11      didrocks | smspillaz: thanks for the info!
[06:38] <didrocks> 08:09:27      didrocks | seems the smspillaz's branch is indeed released
[06:38] <didrocks> so, as you can see, there is anything more on top of the latest release from smspillaz's
[06:38] <ricotz> pitti, i see, so rules should include --enable-gtk-docs again?
[06:38] <RAOF> Ok.
[06:39] <rickspencer3> RAOF, sorry, I didn't realize that you guys were talking :/
[06:39]  * rickspencer3 backs away slowly
[06:39] <RAOF> rickspencer3: No problem :)
[06:39] <RAOF> rickspencer3: You were after a recommendation?
[06:39] <fredp> robert_ancell: you're coming to montreal, great!
[06:40] <rickspencer3> RAOF, yeah, I wanted to know if I would experience sufficient pain if I bought a new ASUS with radeon graphics
[06:40] <rickspencer3> I could get a different brand with nvidia
[06:40] <pitti> ricotz: no, that would cause regeneration of the docs during build, which we don't need
[06:41] <rickspencer3> oooh, the website advertises that this notebook comes with ...
[06:41] <rickspencer3> USD ports, I'm getting that one
[06:41] <RAOF> HAH!
[06:41] <RAOF> rickspencer3: If you're after maximum pain, make sure you get a muxless system.  Of course, it's easy to determine ahead of time whether it's muxless or not.
[06:42] <ricotz> pitti, ok, thanks :)
[06:42] <RAOF> (And by ?maximum pain? I mean that *at best* you'll only be able to drive the external displays with the discrete card, and the laptop panel with the intel chip)
[06:44] <smspillaz> RAOF: minimization works perfectly here
[06:45] <RAOF> Ok.  I'll perform a unity --reset and see.
[06:45] <smspillaz> ok
[06:45] <smspillaz> I stand corrected
[06:45] <smspillaz> it works perfecltly except for maximized windows
[06:45] <rickspencer3> pitti, how does the current desktop image look for doing a fresh install?
[06:46] <smspillaz> RAOF: ok, so I need to fix the maximized window case
[06:46] <pitti> rickspencer3: I haven't done a test install with yesterday's daily yet, but I did with one of last week's; should be alright, no uninstallables right now
[06:46] <smspillaz> RAOF: other than that, I'd say apply this patch
[06:47] <RAOF> Aaaaaah!  It's probably time to restart the X server; input is now going to invisible windows :)
[06:50] <RAOF> smspillaz: Is ?I'd say apply this patch? going to be followed with a patch to test? :)
[06:50] <smspillaz> RAOF: oh as in
[06:50] <smspillaz> RAOF: you should upload the server with this fix applied
[06:50] <smspillaz> since there's a small corner case which is causing it to not work for maximized windows
[06:50] <RAOF> smspillaz: Already done so.
[06:50] <smspillaz> but my testing shows that it works everywhere else
[06:50] <smspillaz> RAOF: oh, ok, good :)
[06:51] <RAOF> pitti: Do you want anymore paperwork before accepting the xserver upload?
[06:51] <pitti> RAOF: no, I was just asking how you assess the regression potential, and whether the unity task is also valid
[06:52] <smspillaz> pitti: is there a bug status "mostly fixed" ?
[06:52] <smspillaz> that would be kinda useful right now
[06:52] <RAOF> Ok.  I assess the regression potential as minimal; it's a protocol change, but only from "this should work, but doesn't" to "this now works", and the unity task is hella valid :)
[06:53] <didrocks> the unity task is valid but where it the code it needs?
[06:53] <smspillaz> oh I see what's going on
[06:53] <smspillaz> hmm
[06:53] <didrocks> as no branch link to it
[06:53] <didrocks> linked*
[06:53] <pitti> RAOF: ok, tahnks
[06:53] <didrocks> and in trunk right now, nothing new on that since latest release
[06:53] <didrocks> pitti: ^
[06:54] <smspillaz> didrocks: can we take a 1 line distro patch on compiz ?
[06:54] <didrocks> ah, so there is indeed something missing
[06:54] <didrocks> smspillaz: in that case, will be better to get today with stacking bugs fixes?
[06:54] <smspillaz> didrocks: uhhh, weren't people testing them ?
[06:54] <didrocks> I would tell that stacking bugs seems more important for beta2 than this, isn't it?
[06:55] <smspillaz> didrocks: sure, although not being able to interact with anything once you minimize a window is also of ... importance
[06:55] <didrocks> smspillaz: DBO tested locally, I tested locally, I'm still waiting for your rev ids to push to a ppa
[06:55] <smspillaz> right
[06:55] <smspillaz> that
[06:55] <didrocks> but it's only the 5th time I ask for the last hour :)
[06:55] <smspillaz> I'm kinda hoping I didn't interrupt my cpm resync while I was testing this
[06:55] <didrocks> smspillaz: just telling that if we want a new compiz, maybe packing both fixes
[06:56] <didrocks> smspillaz: you can still giving me the compiz core first
[06:56] <didrocks> give*
[06:56]  * smspillaz runs the script again just to be sure
[06:56] <smspillaz> didrocks: so do you want the compiz rev *with* the stacking fix merged in or *without* it ?
[06:56] <didrocks> smspillaz: with, what corresponds to the latest tarballs you gave me
[06:57] <didrocks> better than a "ubu1" you tagged which has no meaning
[06:58] <smspillaz> didrocks: 2805
[07:00] <didrocks> smspillaz: building
[07:00] <didrocks> will poke dbarth to get the bug #
[07:01] <smspillaz> gosh unity panel service is chatty
[07:01] <smspillaz> makes debugging painful
[07:05] <robert_ancell> fredp, sure am
[07:07] <smspillaz> didrocks: cpm is rev 27
[07:08] <didrocks> smspillaz: ok, thanks, and from what I heard there is an API addition in core needed by cpm, right?
[07:10] <and471> hey mpt
[07:10] <smspillaz> didrocks: nope
[07:10] <didrocks> smspillaz: ah, rrcarr was wrong, was nice to ask them :)
[07:10] <didrocks> then*
[07:10] <smspillaz> the api change is needed by the composite plugin but that's in core itself
[07:13] <jasoncwarner_> didrocks , this music lens feels like it does non-obvious things. Took me a minute to figure out what it was doing when I was clicking on a track after searching
[07:14] <jasoncwarner_> didrocks: and when I click on 'available for purchase', nothing seems ot happen at all...
[07:14] <didrocks> jasoncwarner_: indeed, only searches "work" for now
[07:14] <didrocks> smspillaz: ok, great!
[07:14] <jasoncwarner_> didrocks: oh!
[07:15] <didrocks> jasoncwarner_: and seems they merged new icons asset in trunk for it, I'll track them to file an UIFe again (grrr at merging in trunk before the UIFe is acked, even *asked*)
[07:16] <jasoncwarner_> didrocks: who is "they" in the above?
[07:16] <didrocks> jasoncwarner_: seems to be lamalex
[07:16] <jasoncwarner_> didrocks: ok...thanks...
[07:37] <didrocks> smspillaz: dh_install: compiz-plugins-main-default missing files (debian/tmp/usr/*/compiz/*animation.*), aborting
[07:37] <didrocks> smspillaz: no more animation plugin in cpm?
[07:38] <rodrigo_> morning
[07:39] <seb128> hi desktopers
[07:39] <chrisccoulson> hi seb128, how are you?
[07:39] <rodrigo_> hey seb128, had good vacation?
[07:39] <didrocks> salut seb128, bonnes vacances?
[07:39] <seb128> hey chrisccoulson rodrigo_
[07:39] <seb128> lut didrocks
[07:39] <didrocks> hey rodrigo_, chrisccoulson
[07:40] <didrocks> chrisccoulson: nice work on the metacity patch btw :)
[07:40] <seb128> yeah, I had a nice week off
[07:40] <seb128> how did the week go for you guys?
[07:40] <rodrigo_> hi didrocks, chrisccoulson
[07:40] <chrisccoulson> hey didrocks
[07:40] <seb128> where do we stand for beta2 and with the freeze?
[07:40] <chrisccoulson> looks like my gtk patch is good too - (gnome bug 659241)
[07:40] <ubot2> Gnome bug 659241 in gtk "GtkPaned initially allocates space for separator, even if there is only one child" [Normal,Unconfirmed] http://bugzilla.gnome.org/show_bug.cgi?id=659241
[07:41] <seb128> I see that pitti worked yesterday to do some updates
[07:41] <pitti> hey seb128, bonjour
[07:41] <pitti> seb128: enjoyed your holidays?
[07:41] <seb128> hey pitti, how are you?
[07:41] <seb128> pitti, yes, very much, thanks
[07:41] <pitti> seb128: yeah, I updated everything to .92 which got released already (not much yet)
[07:41] <seb128> I enjoy less the email backlog after a week though :p
[07:42] <pitti> seb128: pretty well, thanks! just had a long weekend with my in-laws; we did a lot of sightseeing and museums
[07:42] <seb128> is there any work we should land earlier? I will probably delay emails to after updates
[07:42] <pitti> and we watched the European Championship qualification game between Germany and Switzerland on Sunday, in the stadium here
[07:42] <pitti> was my first time in a soccer stadium, quite exciting!
[07:43] <seb128> nice ;-)
[07:43] <seb128> there was quite some sport this w.e
[07:43] <pitti> seb128: nothing that I can see; vala is uploaded, gtkmm3.0 needs fixing upstream for the gtk font selector API change (i. e. current release FTBFS), pygobject packaged in Debian, but not appropriate for beta (breaks some stuff)
[07:43] <seb128> rugby world cup, tennis davis cup, football, basket ball european championship game
[07:44] <smspillaz> didrocks: ???
[07:44] <smspillaz> didrocks: err, that's ... weird
[07:44] <seb128> pitti, ok
[07:44] <didrocks> smspillaz: this is with the cpm tarball
[07:44] <pitti> seb128: and I updated gtk+ to the latest git head on Thursday; I hope there won't be too many changes in today's release compared to that
[07:44] <rodrigo_> seb128, yes, sorry about the French loss in the basketball final :)
[07:44] <didrocks> chrisccoulson: great on you gtk patch :)
[07:44] <pitti> seb128: I'm currently working on the two retracer crashes
[07:44] <seb128> rodrigo_, we lost in tennis as well, damn you spanishes
[07:44] <pitti> seb128: the dup checker has quite a serious bug
[07:44] <smspillaz> didrocks: the one that I gave you last week ?
[07:44] <seb128> pitti, ok
[07:45] <rodrigo_> seb128, oh, didn't know that
[07:45] <pitti> seb128: btw, I got rid of the consolidation step entirely, it's now done on each visited bug individually
[07:45] <didrocks> seb128: well, I didn't hear about any else :-)
[07:45] <pitti> seb128: so it now does the right thing wrt. marking regressions again
[07:45] <pitti> (or will again, once I fix that bug)
[07:47] <didrocks> smspillaz: no "animation" in the plugins/ folder in cpm
[07:47] <smspillaz> didrocks: which tarball are you looking it. There's one here
[07:47] <smspillaz> https://chinstrap.canonical.com/~smspillaz/releases/0.9.5.94ub1/
[07:47] <smspillaz> compiz-plugins-main_0.9.5.94ub1.orig.tar.gz
[07:47] <smspillaz> I just checked now, that's got the animation plugin in it
[07:48] <didrocks> smspillaz: hum, this one wasn't the one, it was the one in tarballs-oneiric-0.9.5.94ub1.tar.bz2 which was the only one available
[07:48] <smspillaz> *shrug* I'm not sure why its not in there then. At least the ones I tested have that one
[07:49] <didrocks> smspillaz: ok, taking this one then
[07:49] <smspillaz> :)
[07:58] <didrocks> smspillaz: when you approve the branch from external contributor (https://code.launchpad.net/~om26er/unity/unity-fix-852984/+merge/75890), please remember that you need to merge it as well (and change the bug status, target to the milestone), please!
[07:58] <didrocks> smspillaz: can you fix that one?
[07:58] <smspillaz> sure
[07:58] <smspillaz> didrocks: I'm waiting on njpatel actually
[07:58] <smspillaz> forthat
[07:58] <didrocks> smspillaz: ah ok :)
[07:58] <didrocks> as you approved it, I was thinking it was ready to be merged
[07:59] <smspillaz> yeah it looks good and then I realized it would be best to double check
[07:59] <didrocks> (maybe you should not set it in that state :))
[07:59] <smspillaz> I changed it back to needs review
[07:59] <seb128> hey mvo ;-)
[08:00] <didrocks> smspillaz: thanks!
[08:06] <rodrigo_> brb
[08:09] <didrocks> chrisccoulson: good news for you! compiz (compiz and c-p-m) fixes for stacking bugs should be in ubuntu-desktop/ppa. Once it's built you are more welcome to rush to it! (take care that there is an experimental music lens as well which can result in some crash in unity)
[08:11] <didrocks> pitti: I'm testing this version since Friday (just compiz, not c-p-m though), some dx members (3) are testing it for a few extra days, if we can get some positive results from the ppa today do you think there is a windows for upload? (as the stacking bugs are still really ackwards)
[08:11] <pitti> didrocks: yes, today is still ok for selected changes
[08:11] <pitti> didrocks: stacking fixes heavily appreciated indeed; how much change is the new version?
[08:12] <didrocks> pitti: quite a lot of changes though, smspillaz is working exclusively on it for the past few weeks
[08:12] <didrocks> pitti: there is no ABI break, so we can revert easily if needed
[08:12] <pitti> didrocks: I mean, the last compiz upload was last Thursday, did we get so many changes since then?
[08:13] <didrocks> pitti: the last compiz was only a settings upgrade
[08:13] <didrocks> and those branches have been put aside from any other work
[08:15] <didrocks> pitti: some diffstat: http://paste.ubuntu.com/692855/
[08:15] <didrocks> (487 from stackdebugger)
[08:15] <pitti> didrocks: that looks a tad big at this point, can the stacking fixes sensibly be cherry-picked?
[08:16] <didrocks> pitti: as there is an API change inside the same package, I don't think so, smspillaz ? ^
[08:16] <didrocks> pitti: this is
[08:16] <didrocks> pitti: this is *only* stacking fixes
[08:16] <smspillaz> pitti: no, it is either all or nothing
[08:17] <smspillaz> if you try to cherry pick from that branch you'll cause problems :)
[08:17] <pitti> didrocks: ok, if you think it's safe enough and doesn't cause other regressions; but it really needs to happen today
[08:18] <didrocks> pitti: yeah, I'll wait for our chrisccoulson to test the ppa as well for a couple of hours first :)
[08:18] <didrocks> as he's our stacking issue rockstar!
[08:18] <pitti> didrocks: is it in the u-desktop PPA? I'm happy to test that as well
[08:18] <didrocks> pitti: yeah, it's currently building, I can ping you once done
[08:18] <pitti> nice
[08:18] <didrocks> pitti: you will need to logout/login again to restart compiz and xorg in sync for the stacking state
[08:22] <didrocks> smspillaz: is the additional commit needed for RAOF's issue on minimize is in this tarball as well? ^
[08:24] <smspillaz> no, not yet
[08:24] <smspillaz> its complicated
[08:25] <didrocks> smspillaz: how had it worked for you then?
[08:26] <smspillaz> didrocks: it worked but broke other stuff
[08:26] <smspillaz> its a fine balance unfortunately
[08:26] <htorque> didrocks: hi, i got some time to click around. do I need c-p-m as well or is the compiz package from the PPA enough?
[08:26] <didrocks> hum, ok
[08:26] <smspillaz> another one of these "core can stomp on what the server is telling us and then the server stabs us for it" bugs
[08:27] <didrocks> htorque: hum? neither compiz nor c-p-m are built yet in the ppa. I will tell you once both are built, but you need both
[08:27] <didrocks> htorque: and then, logout/login
[08:27] <htorque> didrocks: k, thanks
[08:32] <didrocks> RAOF: do you know about having black squares on the screen with nvidia blob driver?
[08:32] <chrisccoulson> didrocks, thanks, will test that in a bit
[08:33] <chrisccoulson> didrocks, does that mean i have to look at the blurry icons in the dash? ;)
[08:33] <didrocks> chrisccoulson: heh, indeed, feel drunk! :-)
[08:33] <chrisccoulson> lol
[08:33] <chrisccoulson> i wish there was a way i could disable that and have nice, sharp icons like unity 2d :)
[08:35] <didrocks> RAOF: and then, some applications (particularly chromium) is having a hard time: http://people.canonical.com/~didrocks/nvidia_glitches.png
[08:35] <mvo> glatzor: \o/
[08:35] <mvo> hey seb128
[08:37]  * glatzor waves mvo
[08:38]  * glatzor busselt den mvo
[08:42] <chrisccoulson_> is launchpad dead?
[08:42] <chrisccoulson_> https://launchpad.net/~ubuntu-desktop gives an OOPS
[08:42] <htorque> yeah
[08:43] <chrisccoulson_> oh
 In a few minutes we'll be down for a couple of minutes of database upgrades
[08:48] <mvo> glatzor: thanks so much for finding and fixing the dbus hangs, awsome
[08:49] <mvo> glatzor: you made my day :)
[08:50] <chrisccoulson_> didrocks, do i also need compiz-plugins-main from the PPA?
[08:50] <didrocks> chrisccoulson_: yeah, you need both :)
[08:50] <didrocks> (still waiting for publishing)
[08:50] <chrisccoulson_> didrocks, that seems to be an older version compared to what is already in the archive
[08:51] <didrocks> chrisccoulson_: interesting 1:0.9.5.94+bzr20110915-0ubuntu1 > 1:0.9.5.94+bzr27-0ubuntu1~ppa1 ?
[08:52] <chrisccoulson_> didrocks, yeah, seems so
[08:52] <didrocks> (tried to get back to a revid versionning now that I have them)
[08:52] <seb128> didrocks, dpkg --compare-versions is your friend
[08:52] <didrocks> chrisccoulson_: it's too smart :-)
[08:52] <chrisccoulson_> heh
[08:52] <smspillaz> RAOF: hm, ok, almost fixed it
[08:52] <didrocks> seb128: sure, in that one, i was only thinking about trivial char by char
[08:52] <didrocks> ok, reuploading with the date then
[08:53] <didrocks> chrisccoulson: you can still manually downgrade (you need at least -default package)
[08:53] <chrisccoulson> thanks
[08:58] <glatzor> mvo, you pointed me to the direction
[08:59] <didrocks> smspillaz: dbarth found out that the compiz tarball doesn't correspond to rev 2805, can you clarify that out with him please?
[08:59] <glatzor> mvo, but those encodings errors are really nasty ones lp#846044
[09:01] <mvo> glatzor: I initially thought that the blocking was the debfile resolving or somehting like this, but its pretty obvious now what the real cause is :)
[09:02] <chrisccoulson> seb128, do you see bug 852406 on your laptop btw?
[09:02] <ubot2> Launchpad bug 852406 in linux "Phantom battery appears after resume from suspend" [Undecided,Confirmed] https://launchpad.net/bugs/852406
[09:02] <mvo> glatzor: yeah, we have a bunch of them in s-c as well, rather anyoing, did comment #3 help in this bug ? setting the default encoding?
[09:02] <smspillaz> didrocks: ok, hang on
[09:02] <smspillaz> didrocks: i need to finish fixing this first
[09:02] <glatzor> mvo, about the encoding issue. It seems to make sense to workaround the DBusException.get_dbus_message() method by accessing the error string from Exception.message
[09:03] <didrocks> smspillaz: just talk to dbarth about it when you have the time
[09:03] <glatzor> mvo, I cannot reproduce this error here
[09:03] <mvo> glatzor: :/
[09:04] <mvo> glatzor: yeah, dyoing it when calling get_dbus_message() makes most sense I guess
[09:04] <seb128> chrisccoulson, not that I noticed but I'm not uptodate, I didn't upgrade since before my holidays
[09:04] <seb128> chrisccoulson, I will try later once I've upgraded and restarted
[09:12] <htorque> meh, i got a stuck click-through window in gimp
[09:13] <didrocks> htorque: after logging out/logging in?
[09:13] <htorque> yes
[09:13] <didrocks> smspillaz: ^^
[09:13] <htorque> it's gimp with the maximized main window and the toolbox opened. after creating a new image from the "File" menu, that dialog stays opened even after quitting gimp.
[09:22] <smspillaz> known issue
[09:22] <glatzor> mvo, so I will merge the non-blocking-lintian branch
[09:22] <didrocks> is there a bug tracking that?
[09:23] <smspillaz> didrocks: don't know
[09:23] <didrocks> would be nice that "known issues" are filed and tracked
[09:23] <htorque> more stuck stuff: synaptic -> reload package information. the dialog gets stuck the same way just not fully transparent. also, the menu stuck when quitting the application (File -> Quit).
[09:23] <htorque> http://img.xrmb2.net/images/779754.png
[09:23] <smspillaz> htorque: hang on
[09:23] <smspillaz> htorque: you're running the newest c-p-m ?
[09:23] <htorque> yeah
[09:23] <smspillaz> hmm
[09:24] <smspillaz> didrocks: can we make another package of that for testing ?
[09:24] <smspillaz> I'll get you another tarball
[09:24] <glatzor> mvo, i also 'fixed' the encoding error
[09:24] <didrocks> smspillaz: do you have a fix for it? later than rev27?
[09:25] <smspillaz> didrocks: not necessarily, I've just made some changes to the animation plugin
[09:25] <smspillaz> didrocks: is htorque testing the stacking fixes ppa ?
[09:25] <didrocks> smspillaz: yeah
[09:26] <didrocks> smspillaz: would be nice that some changes are tracked and under a bug ref
[09:26] <smspillaz> htorque: I think you'll need an updated animation plugin, hang on
[09:26] <mvo> htorque: oh? hmmm, that part of the code has no changed in a while
[09:26] <smspillaz> didrocks: kind of juggling 4 different branches atm, excuse the errors
[09:27]  * didrocks sees that as a juggle, indeded
[09:27] <didrocks> indeed*
[09:27] <smspillaz> the good news is that I've fixed RAOF's bug
[09:31] <smspillaz> coolio, all fixed
[09:34] <didrocks> smspillaz: ok, so you have two folders with the same packages name
[09:35] <didrocks> smspillaz: https://chinstrap.canonical.com/~smspillaz/releases/0.9.5.94stacking and https://chinstrap.canonical.com/~smspillaz/releases/0.9.5.94ub1/
[09:35] <didrocks> both containing "ubu1"
[09:35] <didrocks> dbarth had a look there
[09:35] <didrocks> seems the second one, which is the one you pointed me about is indeed rev 1805, but doesn't contain stacking fixes
[09:35] <dpm> morning pitti, did you disable the oneiric language packs? I just want to check it wasn't me who did it inadvertently when changing the crontab to adapt to the new LP export times. After language pack exports being broken in LP for a while, I was expecting new langpacks on Friday
[09:36] <pitti> dpm: yes, for beta-2 freeze
[09:36] <didrocks> can you please look at all this mess and get me *one* tarball with *a list of fixed bugs* ensuring we have *what we need and what we need only*?
[09:36] <didrocks> bringing some sanity and rigor there…
[09:36] <smspillaz> didrocks: oh great.
[09:36] <smspillaz> didrocks: this is why I shouldn't upload tarballs at 4am
[09:37]  * didrocks won't comment
[09:37] <smspillaz> I think I was actually delerious by that point
[09:37] <smspillaz> had been working on the stacking bug for .... about 29 hours straight
[09:37] <smspillaz> the moral of the story is don't maintain window managers
[09:37] <dbarth> the stacking directory should contain the right one, i'm checking that now
[09:38]  * didrocks wonders how other people on the dx team +1 the stacking fix over the past few days telling it's fixing everything from the 2nd link then
[09:38] <dpm> pitti, could we have a new delta export before the full one at the end of the week? Due to broken exports in LP translators haven't been able to see any updates for a while
[09:38] <rodrigo_> pitti, the versions page is updated continously now, right?
[09:38] <pitti> seb128: erk, seems my sqlite3 operation under oneiric somehow broke the .db under lucid :/
[09:38] <pitti> rodrigo_: yes
[09:39] <rodrigo_> pitti, as soon as the packages are accepted, or when they are in the queue?
[09:39] <pitti> dpm: too late for beta-2, but we can reenable it on Friday, yes
[09:40] <dpm> pitti, ok
[09:40] <dbarth> didrocks: they're testing by using the source branch
[09:40] <smspillaz> wow, the oneiric and main branches are really diverging
[09:41] <smspillaz> the conflicts are out of control
[09:41] <pitti> rodrigo_: "accepted" I think
[09:41] <pitti> rodrigo_: there is some code to check the unapproved queue, I think, but it doesn't seem to work
[09:41] <pitti> rodrigo_: I updated the pad with stuff that I updated, and of course everyone can check the queue
[09:41] <pitti> rodrigo_: or bzr :)
[09:41] <RAOF> didrocks: Hm, no I don't know anything about those nvidia glitches.
[09:42] <rodrigo_> pitti, ok, it wasn't being updated while my last upload was waiting for approval, that's why I asked
[09:42] <didrocks> RAOF: I guess it's maybe linked to bug #813343
[09:42] <ubot2> Launchpad bug 813343 in unity "nvidia drivers, second monitor covered by black" [High,Confirmed] https://launchpad.net/bugs/813343
[09:42] <didrocks> RAOF: but I get it even when I have one monitor
[09:42] <rodrigo_> I'll leave it in the pad until it is accepted, so that nobody starts working on it
[09:43] <didrocks> pitti: ok, seems we maybe shouldn't get the compiz fixes then for today (as conflicts are out of control)
[09:43] <smspillaz> didrocks: no, we'll be fine
[09:43] <smspillaz> didrocks: I was speaking as in
[09:43] <smspillaz> when I was merging in the fix for raof's branch
[09:43] <chrisccoulson> didrocks, i grabbed the version from the desktop PPA
[09:43] <smspillaz> I got a large number of conflicts but most of them are trivial
[09:43] <chrisccoulson> i got an invisible window after minimizing a window for the first time
[09:43] <smspillaz> chrisccoulson: update your xserver
[09:44] <chrisccoulson> brb, switching back to 2d first
[09:44] <RAOF> didrocks: I wouldn't expect it to be the same as the second-monitor bug, but maybe it is.
[09:45] <chrisccoulson> that's better
[09:46] <didrocks> chrisccoulson: it shouldn't fix the stacking issue, don't spend time trying it, see the discussion above ^
[09:46] <chrisccoulson> smspillaz, update my xserver from where? it's already up-to-date....
[09:46] <didrocks> chrisccoulson: not the right tarball
[09:46] <chrisccoulson> g'ah ;)_
[09:46] <smspillaz> RAOF: new xserver uploaded ?
[09:47] <RAOF> smspillaz: Yes, and accepted.
[09:47] <smspillaz> chrisccoulson: basically you should only ever get that if you minimized a maximized window with the newest xserver
[09:47] <smspillaz> which is something I'm trying to fix now
[09:47] <RAOF> chrisccoulson: You're looking for xserver-xorg-core 1.10.4-1ubuntu2
[09:48] <didrocks> RAOF: however I have those issues: http://people.canonical.com/~didrocks/nvidia_glitches2.png
[09:48] <didrocks> RAOF: who should I ping to track that?
[09:49] <rodrigo_> bbiab
[09:49] <RAOF> didrocks: Hm.  That looks kinda like bad Damage handling.  tselliot is probably who you want to ping.
[09:50] <didrocks> RAOF: ok, will bother him then :)
[09:50] <smspillaz> RAOF: didrocks: ok, I am going to merge the stacking branch upstream now
[09:50] <smspillaz> try and get our branches under control here
[09:51] <didrocks> smspillaz: need as well all bug # attached
[09:52] <didrocks> smspillaz: especially those coming from the current rev 1804, 1805
[09:52] <didrocks> as it's not a stacking fix it seems
[09:54] <smspillaz> didrocks: keep in mind that while I can get bug # for everything, over-cherry-picking is not really a feasible option
[09:55] <didrocks> smspillaz: as usual with compiz… But better to get everything tracked, with fix committed bugs and such…
[09:55] <smspillaz> didrocks: those revisions have been signed off already
[09:55] <smspillaz> I just did a merge, that's all
[09:56] <didrocks> smspillaz: yeah, but can I get the bug numbers as it's the only thing I'm asking for?
[09:56] <smspillaz> didrocks: sure, hang on
[09:56] <didrocks> thanks!
[09:56] <smspillaz> loggerhead needs to be able to show you the full revision tree
[09:59] <smspillaz> didrocks: 2805 is bug 731685 and 2804 is bug 724093
[09:59] <ubot2> Launchpad bug 731685 in compiz "Panel shadow conflicts with Window shadow in Ubuntu Classic Desktop Session" [Undecided,In progress] https://launchpad.net/bugs/731685
[09:59] <ubot2> Launchpad bug 2804 in launchpad "Stop indenting and wrapping bug descriptions in e-mail notifications" [Medium,Invalid] https://launchpad.net/bugs/2804
[09:59] <ubot2> Launchpad bug 724093 in compiz "unity-window-decorator: When switching between windows, Orca does not speak the title of the focused window." [High,Fix committed] https://launchpad.net/bugs/724093
[10:00] <dbarth> smspillaz: i have verified the stacking tarball
[10:00] <dbarth> smspillaz: it corresponds to the lp:~compiz-team/compiz-core/compiz-core.stack_sync_fix branch, modulo those 2 fixes you've just mentionned
[10:00] <didrocks> smspillaz: ok, and then the stacking bug fixes
[10:01] <chrisccoulson> pitti - did you approve the firefox/thunderbird uploads yesterday?
[10:01] <pitti> chrisccoulson: yes; don't tell me they are utterly broken :)
[10:01] <chrisccoulson> pitti - no, i just wanted to say thanks ;)
[10:01] <dbarth> smspillaz: would you have other stacking patches to add on top, or can we just rebuild from this tarball instead
[10:01] <chrisccoulson> pitti - those are the RC's for the 7.0 release too :)
[10:01] <pitti> chrisccoulson: *phew* :) you're welcome; I thought better to start building them early, wrt. arm images and such
[10:01] <smspillaz> dbarth: I'd rather make a new one
[10:02] <chrisccoulson> yeah, i was a bit concerned about that. i was hoping to get them slightly before the freeze ;)
[10:02] <smspillaz> i need to have dinner
[10:02] <chrisccoulson> but mozilla had an all-hands event last week, so things were a bit quiet
[10:02] <didrocks> smspillaz: and c-p-m btw? no new tarball? can I get the bugs # as well?
[10:02] <smspillaz|d> didrocks: yes, that's coming
[10:03] <dbarth> didrocks: i'll give you the rest
[10:03] <didrocks> dbarth: thanks
[10:06] <chrisccoulson> can we not propose blueprints for UDS-P yet? ;)
[10:06] <soren> When a browser (in this instance Google Chrome) complains it's not the default browser... How can it tell? Where does it look this up?
[10:08] <seb128> chrisccoulson, what do you want to work on? ;-)
[10:10] <bryceh> chrisccoulson, perpetual peacock is not open yet for blueprints
[10:14] <pitti> bryceh: you had a spelling error in "perky penguin"
[10:16] <geser> is the codename for P already announced?
[10:17] <seb128> chrisccoulson, nice work on bug #804435
[10:17] <ubot2> Launchpad bug 804435 in unity-2d "Wallpaper is loaded twice with different alignment by gnome-session and nautilus (Oneiric)" [High,In progress] https://launchpad.net/bugs/804435
[10:17] <seb128> chrisccoulson, did you see that upstream "accept commit"-ed it?
[10:17] <seb128> didrocks, ^ btw
[10:18] <didrocks> seb128: I know about it, I asked him to continue the debugging I just had the time to start :)
[10:18] <seb128> didrocks, right, I pointed that the patch got accepted
[10:18] <seb128> chrisccoulson, if you don't have commit access you should say it on the bug so somebody commit it ;-)
[10:18] <didrocks> yeah, I looked at it, chrisccoulson really rocks! :-)
[10:19] <chrisccoulson> seb128, yeah, i've got commit access. i will test in a minute if it still works ;)
[10:21] <chrisccoulson> heh, i did a build of thunderbird on my laptop at the weekend - it took around 35 minutes :)
[10:21] <pitti> chrisccoulson: that sounds fast -- how long did the old one take?
[10:21] <chrisccoulson> or thereabouts. i didn't actually time it, but it wasn't very long
[10:21] <chrisccoulson> pitti - it took around 3.5 hours before ;)
[10:22] <seb128> chrisccoulson, so you are happy about the laptop you picked?
[10:22] <didrocks> chrisccoulson: can I have a dist-cc on your laptop for compiz/nux/unity? :)
[10:22]  * didrocks tries
[10:22] <chrisccoulson> seb128, yeah, it's really fast :)
[10:22] <seb128> ssd?
[10:22] <chrisccoulson> the 8GB or RAM + SSD really helps ;)
[10:22] <seb128> ssd for the win!
[10:23] <chrisccoulson> yeah, i can't believe how much of a difference it makes :)
[10:23] <popey> chrisccoulson: what laptop do you have?
[10:23] <chrisccoulson> popey, it's a dell e6410
[10:23] <popey> zoiks
[10:23]  * popey looks at his laptop and sees Latitude | E6410
[10:23] <chrisccoulson> popey - i actually wanted to buy a thinkpad, but i didn't want to pay for a new docking station ;)
[10:24] <popey> (work supplied laptop)
[10:24] <chrisccoulson> heh :)
[10:24] <popey> they are quite nice, I agree.
[10:24] <smspillaz> RAOF: are you able to kompile kompiz ?
[10:25] <chrisccoulson> yeah, i quite like the new machine :)
[10:27] <smspillaz> dbarth: are you free to test something ?
[10:28] <didrocks> smspillaz: think about the core.h ABI downgrade btw
[10:28] <smspillaz> didrocks: yep, sure
[10:33] <Sweetshark> omg: http://mail-archives.apache.org/mod_mbox/incubator-ooo-dev/201109.mbox/%3C4E7712C9.9060306@gmx.ch%3E
[10:37] <RAOF> smspillaz: Which compiz?
[10:37] <smspillaz> RAOF: lp:~compiz-team/compiz-core/oneiric.stack_sync_fix
[10:37] <smspillaz> if you compile from there you should be able to test if maximized windows are still a problem
[10:38] <smspillaz> RAOF: you may want to change the ABI back (in fact, I might do that now)
[10:39] <RAOF> smspillaz: Actually, is tomorrow early enough?  I need to wander bedwards.
[10:39] <smspillaz> hmm
[10:39] <smspillaz> well, I need someone to test it today, but if you need to go to bed that's fine
[10:39] <smspillaz> dbarth: !! ?
[10:40] <smspillaz> RAOF: will the new xserver appear if you did apt-get update && apt-get install xserver-xorg-core ?
[10:42] <smspillaz> didrocks: actually, are you free to test something ?
[10:42] <didrocks> smspillaz: I already lost 5 hours with compiz this morning, need to catch up on something else. Do you have the tarballs?
[10:42] <smspillaz> nope, I'm waiting on someone to test my branch so that I can make tarballs for you
[10:43] <RAOF> smspillaz: Yes.  The new xserver is published and ready to roll.
[10:43] <smspillaz> RAOF: thanks
[10:43] <smspillaz> didrocks: unless you don't want the fix for https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/853734 (broken maximize)
[10:43] <ubot2> Ubuntu bug 853734 in unity "maximized windows fail to update their input extents when undecorated" [High,Fix committed]
[10:44] <didrocks> smspillaz: all will be in a ppa at this point I guess
[10:44] <smspillaz> ok
[10:44] <didrocks> smspillaz: so you can still roll with it as it's only in a ppa
[10:44] <smspillaz> sure
[10:44] <smspillaz> although I need someone to approve my merge first
[10:44] <didrocks> smspillaz: and get all bug # for stacking (and the c-p-m change)
[10:44] <smspillaz> otherwise rolling tarballs is ... painful
[11:36] <chrisccoulson> w00t, my git access still works - http://git.gnome.org/browse/gtk+/commit/?id=22cd009ef7ae24011aa3c8414c44361133c93d2c :)
[11:42] <smspillaz> didrocks: https://chinstrap.canonical.com/~smspillaz/releases/0.9.5.94ub1/compiz-plugins-main_0.95rev27.orig.tar.gz . The only thing that's changed is that I fixed bug https://bugs.launchpad.net/compiz-plugins-main/+bug/853807
[11:42] <ubot2> Ubuntu bug 853807 in unity "crash when looping paint list in preparePaint (on closing windows)" [High,Fix committed]
[11:43] <didrocks> smspillaz: ok, thanks for this one, redoing the tarballs
[11:43] <didrocks> hum, I will have to cheat with the ppa as the version rev27 was already there
[11:45] <smspillaz> ah
[11:45] <didrocks> smspillaz: 0.95 ?
[11:45] <didrocks> not 0.9.94 ?
[11:45] <smspillaz> or 0.9.5.94
[11:45] <smspillaz> typo
[11:46] <didrocks> ok
[12:13]  * rodrigo_ lunch
[12:17] <smspillaz> didrocks: ok, we got kamstrup|afk to test my branch and he says it works fine
[12:17] <didrocks> smspillaz: ok, so merging and tarball?
[12:17] <didrocks> smspillaz: and bug # for all the stacking fixes
[12:17] <smspillaz> there's only one meta-bug I'm using to track it
[12:17] <smspillaz> didrocks: yeah, he just needs to hit the approve button
[12:18] <didrocks> smspillaz: only one? there is more on the unity target page assigned to you IIRC
[12:18] <ogra_> hmm, is it expected that my shutdown icon does not turn red if need to reboot after an upgrade ?
[12:18] <smspillaz> didrocks: well, I can try to collect them all :/
[12:19] <didrocks> smspillaz: see the latest target
[12:19] <smspillaz> didrocks: ok, I have one request. could you have a look over the code for https://code.launchpad.net/~compiz-team/compiz-core/compiz-core.fix_853734/+merge/75992 and approve it if it looks good ?
[12:20] <didrocks> smspillaz: that's what kamstrup|afk tested, isn't it?
[12:20] <smspillaz> kamstrup|afk didn't approve it since he didn't have time to look at the code
[12:20] <smspillaz> didrocks: yes
[12:20] <smspillaz> but I kinda need this in before I merge stuff
[12:20] <seb128> ogra_, not sure, check with ted when he's online
[12:25] <didrocks> smspillaz: I don't see any insanity in the code, approved
[12:25] <smspillaz> :)
[12:26] <didrocks> smspillaz: bug #805087 is another stacking issue
[12:26] <ubot2> Launchpad bug 805087 in unity "Dash and launcher appear underneath windows" [Critical,In progress] https://launchpad.net/bugs/805087
[12:27] <didrocks> smspillaz: bug #847967 is fixed by this branch as well?
[12:27] <ubot2> Launchpad bug 847967 in unity "A minimized window 'remains' behind on the desktop if /apps/compiz-1/plugins/unityshell/screen0/options/show_minimized_windows is set to true" [High,In progress] https://launchpad.net/bugs/847967
[12:27] <smspillaz> didrocks: sort of. this branch implements a fix for something that wasn't quite working in the original fix
[12:27] <pitti> seb128: hmm, still no new .92 tarballs..
[12:27] <smspillaz> SunFl0wer: rabid nick swapping much ?
[12:27] <seb128> pitti, gnome-screensaver earlier and they just uploaded the evolution stack
[12:27] <didrocks> smspillaz: so, please set it to fix committed
[12:27] <SunFl0wer> smspillaz, we are playing a game
[12:28] <pitti> seb128: oh, versions.html is behind?
[12:28] <pitti> seb128: anything else that I could help with?
[12:28] <seb128> pitti, seems so
[12:28] <seb128> versions being behind
[12:28] <smspillaz> SunFl0wer: I figured :)
[12:28] <seb128> gnome-screensaver was uploaded over an hour ago
[12:29] <smspillaz> didrocks: yep
[12:29] <seb128> pitti, nothing that I know about, I'm about to be done catching up with emails, bugs, updates, etc
[12:29] <pitti> seb128: is anyone working on it? pad doesn't say
[12:29] <seb128> i.e with what happened while I was not there
[12:29] <seb128> pitti, no
[12:29] <seb128> pitti, i.e feel free to claim any of those updates
[12:29] <seb128> rodrigo_ was debugging the proxy bug and is at lunch
[12:30] <seb128> nobody else is set on GNOME updates today I think
[12:30] <pitti> I'm working on apport today, but that's not overly critical
[12:30] <rodrigo_> seb128, I'm cooking, and yes, almost have a fix
[12:30] <pitti> I'm mostly standing by for .92 packaging
[12:30] <seb128> I will start on updates soon as they come
[12:30]  * pitti grabs the screen saver then
[12:30] <seb128> thanks
[12:30] <seb128> let the evolution stack for cyphermox I guess
[12:30] <seb128> out of e-d-s they are not on the CD anyway
[12:31] <seb128> so we don't need to get them in early
[12:31] <pitti> getting e-d-s ASAP would be good, though (unless there's another ABI break, but let's hope not)
[12:32] <seb128> reading the changelog there isn't
[12:32]  * smspillaz merges in the stacking fix
[12:34] <seb128> pitti, gtkmm got an update as well btw
[12:35] <pitti> seb128: yeah, looked in git, but apparently still not udpated to new gtk_font_selector API
[12:35] <seb128> weird
[12:35] <seb128> pitti, it might be worth pinging murrayc on #gnome-hackers about it
[12:36] <seb128> I've not followed the details but it seems weird he rolled a tarball that doesn't work with the current gtk
[12:37] <pitti> ok
[12:37] <pitti> can do, just starting g-s build
[12:37] <seb128> Laney, hey, will you update tomboy? (no hurry, it's only translations updates)
[12:38] <Laney> yeah soon
[12:38] <Laney> didn't think it'd be wanted for b2
[12:44] <Laney> I want to give chipaca and aquarius time to fix U1 if possible
[12:45] <GunnarHj> pitti: Hi Martin, hope you had a nice weekend. Wondering if https://code.launchpad.net/~gunnarhj/language-selector/fontconfig/+merge/75045 possibly qualifies for a b-freeze exception. It includes a couple of dbus related fixes, and since I have been struggling with those for a while, I'm anxious to get it into the archive asap, so there is enough time for further tweaking if we'd get more crash reports.
[12:45] <seb128> Laney, ok, I just write you down on the etherpad for it so nobody duplicate work
[12:48] <smspillaz> didrocks: ok, got that merged upstream \o/
[12:49] <didrocks> smspillaz: great, ping me with a tarball please :)
[12:51] <mterry> didrocks, seb128, smspillaz: morning (for me)!
[12:51] <didrocks> good morning mterry!
[12:52] <seb128> mterry, hey mterry, how are you?
[12:52] <mterry> didrocks, were you talking stacking fix shop with smspillaz?  /me is eager to test out new packages, has all sorts of stacking gremlins in his machine
[12:52] <mterry> seb128, good!
[12:52] <didrocks> mterry: indeed!
[12:52] <pitti> seb128: grabbing gtkmm3.0; seems last time I tried to build .18, my bad
[12:52] <didrocks> mterry: seems you will be a nice guinea pig then ;)
[12:53] <mterry> didrocks, let me know what I can do to help  :)
[12:53] <seb128> pitti, great, thanks
[12:53] <smspillaz> DISCLAIMER: not guarunteed to have fixed it
[12:53] <mterry> pitti, also morning pitti!
[12:53] <didrocks> mterry: sure, will ping you once landed in the ubuntu-dektop ppa
[12:53] <pitti> hey mterry, how are you?
[12:53] <pitti> hey GunnarHj
[12:53] <mterry> good
[12:55] <pitti> GunnarHj: hm, need to review that in-depth, it's quite a large p atch
[12:57] <pitti> rodrigo_: do we need the new folks for anything in b2? it's quite a large update, and doesn't strictly fall under the gnome standing FFE
[13:06] <GunnarHj> pitti: I see. Seeked a sponsor last thursday, but noone had the time before b2. Were probably busy with their own last minute uploads...
[13:06] <smspillaz> didrocks: so bad news
[13:06] <smspillaz> didrocks: libreoffice causes stacking bugs
[13:06] <didrocks> smspillaz: very bad ones?
[13:07] <pitti> ok, all 3.1.92 on http://people.gnome.org/~vuntz/tmp/versions/versions-unstable are in now
[13:08] <smspillaz> didrocks: well it gets above panels somehow
[13:08] <smspillaz> I can't reproduce it now though
[13:08] <smspillaz> something to keep on the radar though
[13:08] <seb128> pitti, I've been putting things to update on the etherpad as they were showing on the ftp list, but good to have versions updated as well ;-)
[13:08] <smspillaz> gosh, I wish we didn't live in a world where there were all these broken applications
[13:08] <smspillaz> #firstworldproblem
[13:09] <pitti> seb128: ah, thanks
[13:22] <pitti> GunnarHj: ok, responded (I used a separate response for separate issues, sorry for multiple mails)
[13:31] <pitti> seb128: accidental double-dput of d-schemas, or does the second one fix something?
[13:32] <seb128> pitti, accidentally called back the wrong command
[13:32] <pitti> seb128: ok
[13:32] <seb128> i.e feel free to drop one of the 2
[13:32] <seb128> sorry about that
[13:33] <cyphermox> ohh, new evo
[13:33] <dobey> grrrrr
[13:33] <pitti> seb128: np, done
[13:33] <pitti> cyphermox: good morning
[13:33] <cyphermox> pitti: hey
[13:33] <dobey> why does gnome-session Depends: unity | unity-2d?
[13:34] <pitti> cyphermox: do you want to package these? if so, starting with e-d-s would be appreciated, as that's on the images
[13:34] <didrocks> dobey: because it contains the session files
[13:34] <cyphermox> pitti: yup yup, getting started nao
[13:35] <seb128> dobey, because that's the sessions it ships, it has also | gnome-shell in oneiric
[13:35] <cyphermox> pitti: not sure if you saw my ping before, but if  you could review/ack https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/849994 it would be much appreciated
[13:35] <ubot2> Ubuntu bug 849994 in network-manager "FFE: add NetworkManager DUID support" [Undecided,New]
[13:35] <dobey> that is broken
[13:35] <pitti> cyphermox: I answered to that actually
[13:35] <cyphermox> you did?
[13:35] <dobey> why are those not Recommends?
[13:36] <seb128> dobey, right, it should | x-session and have all session providers provide it
[13:36] <seb128> Recommends would work as well I guess
[13:36] <pitti> cyphermox: in short, I have next to no idea about ipv6 and what DUID is, I was hoping someone with ipv6 knowledge coudl review this; I think Colin did some ipv6 stuff
[13:36] <cyphermox> yeah
[13:36] <dobey> it shouldn't depend on any of them really. the dependency is backward; unity should require gnome-session, i think
[13:37] <rodrigo_> pitti, the new folks is needed for the upcomping gnome-contacts update
[13:37] <pitti> rodrigo_: how much did you test the new versino with empathy?
[13:37] <cyphermox> most of the issue comes from the fact that having sufficient knowledge of NM, DHCPv6 and what DUIDs are is not very distributed.. we all have little bits of the puzzle :)
[13:37] <dobey> and how do i configure my panels the way i had them in natty, in oneiric?
[13:38] <rodrigo_> pitti, installed it and running empathy with it now
[13:38] <rodrigo_> pitti, will keep testing
[13:39] <pitti> rodrigo_: ah, good; so shouldn't totally break b2 then?
[13:40] <rodrigo_> pitti, AFAICS so far, no
[13:40] <pitti> rodrigo_: ok, can accept if you feel good about it
[13:40] <rodrigo_> pitti, if you want, let's wait for another tester :)
[13:54]  * kenvandine waves
[13:55] <pitti> hey kenvandine, welcome back! how are you?
[13:55] <kenvandine> a bit tired :)
[13:55] <kenvandine> long day of travel yesterday, but vacation was great!
[13:55] <seb128> oh, a kenvandine
[13:55] <seb128> kenvandine, hey!
[13:56] <kenvandine> hey seb128
[13:57] <didrocks> welcome back kenvandine!
[13:57] <kenvandine> thx didrocks
[13:58] <dobey> whee, bug #853886
[13:58] <ubot2> Launchpad bug 853886 in gnome-terminal "Menu bar shown even when it shouldn't be, without Unity" [Undecided,New] https://launchpad.net/bugs/853886
[14:02] <seb128> pitti, hum, you dropped indicator-applet? did you check with ted,dx?
[14:02] <pitti> seb128: if it ever gets fixed, we can trivially reintroduce it
[14:03] <seb128> ok
[14:03] <pitti> and it was holding a lot of cruft in NBS, etc.
[14:03] <pitti> http://people.canonical.com/~ubuntu-archive/nbs.html will be empty again as soon as ltsp built (that was just a temporary glitch in debian/control)
[14:04] <seb128> ok
[14:05] <seb128> I still not like much that we drop support for our techs like that
[14:05] <seb128> let's see if dx fixes it before oneiric or not
[14:06] <pitti> well, actually I think it's the right thing to do
[14:06] <pitti> gnome-shell doesn't support it, and the classic gnome session should now be a bit more "vanilla" upstream, too
[14:11] <dobey> oneiric has been a nightmare for me on my laptop with poulsbo :(
[14:12] <rodrigo_> hey kenvandine, had a good vacation?
[14:12] <kenvandine> rodrigo_, yes i did!
[14:12] <dobey> how can i get my config back?
[14:12]  * kenvandine applies 2 weeks of updates... 
[14:12] <rodrigo_> kenvandine, you've been in Croation, right?
[14:13] <seb128> pitti, right, I don't argue we should have the applet on by default, still would be nice to have it for those who like indicators ;-)
[14:13] <rodrigo_> Croatia
[14:13] <kenvandine> yeah
[14:13] <seb128> pitti, but not worth spending our time on
[14:13] <kenvandine> croatia was pretty incredible
[14:13] <kenvandine> dubrovnik and split
[14:13] <rodrigo_> kenvandine, yeah, I've heard it's a nice place indeed
[14:13] <kenvandine> i wasn't expecting it to be quite that nice
[14:14] <rodrigo_> kenvandine, ok, we expect photos now :)
[14:15] <kenvandine> i'll share what my wife uploads, she is the photographer :)
[14:15] <seb128> kenvandine, oh, and you can bring us our souvenirs at UDS ;-)
[14:15] <seb128> no hurry
[14:15] <kenvandine> hehe :)
[14:15] <kenvandine> brb, reboot
[14:15] <rodrigo_> oh yeah, souvenirs
[14:18] <kenvandine> woot, smooth upgrade :)
[14:19] <seb128> lucky you!
[14:22] <kenvandine> ugh.. maybe not... no dash or quick menus
[14:23] <kenvandine> quick lists.... whatever... i forgot the unity lingo :)
[14:24] <seb128> oh, likely a stacking issue
[14:24] <kenvandine> ah stacking bugs...
[14:24] <seb128> ;-)
[14:24] <kenvandine> works on an empty desktop
[14:25] <seb128> dx should have a fixed compiz out today
[14:25] <seb128> let's see
[14:25] <kenvandine> woot
[14:25] <kenvandine> finally really fixed the stacking bugs?
[14:26] <seb128> that's what they claim at least
[14:26] <didrocks> fixed minus libreoffice though
[14:26] <didrocks> kenvandine: minus libreoffice and gimp
[14:26] <didrocks> (and more to come, I'm afraid)
[14:27] <didrocks> we'll see in the ppa, once I get after 3 trial the right tarball :)
[14:33] <glatzor> pitti, hello, I have got a question about sub classes of gtk widgets. in aptdaemon we use GObject.GObject.__init__(self), but is it correct that this is done implicitely nowadays?
[14:34] <glatzor> pitti, see http://python-gtk-3-tutorial.readthedocs.org/en/latest/introduction.html#extended-example
[14:34] <pitti> glatzor: I don't know off-hand, I'm afraid; better ask in #python on GIMP IRC?
[14:34] <pitti> but I haven't seen that explicit call anywhwere, so it's likely
[14:38] <smspillaz> mterry: did you have the bug number for windows that start iconified not working with compiz ?
[14:39] <mterry> smspillaz, bug 732997
[14:39] <ubot2> Launchpad bug 732997 in unity "Cannot open a window that starts iconified" [High,Confirmed] https://launchpad.net/bugs/732997
[14:39] <smspillaz> coolio, thanks
[14:44] <mterry> smspillaz, I'm honored, but I think you meant mterry, not coolio  ;)
[14:45] <mterry> We need more rap programmers
[14:46] <smspillaz> mterry: ahahah
[14:50] <seb128> pitti, hum, wasn't libgucharmap7 a gtk2 lib?
[14:50] <pitti> didrocks: ah, pulling new compiz from PPA, testing now..
[14:50] <seb128> pitti, with libgucharmap-2-90-7 the gtk3 one?
[14:50] <didrocks> pitti: no, that's the one from this morning
[14:50] <didrocks> pitti: it's one of the three wrong tarball rolled last Thursday, it doesn't contain stacking fix
[14:51] <pitti> didrocks: I see
[14:51] <pitti> seb128: oh, oops
[14:51] <didrocks> pitti: smspillaz will hopefully roll some again soon (at least, supposed to)
[14:51] <pitti> seb128: I guess we need to roll back to 3.0.1 then?
[14:52] <pitti> it still has two rdepends
[14:52] <seb128> pitti, I would just drop the gtk2 build
[14:52] <seb128> pitti, we can probably drop the plugins from the 2 rdepends
[14:52] <pitti> yes, presumably
[14:52] <seb128> or the 2 rdepends
[14:54] <pitti> seb128: noted in pad
[14:54] <seb128> pitti, thanks
[14:55] <didrocks> pitti: didn't notice anything done in that regards, but I get flicker free boot on nvidia today! (thanks for Qt to have killed my laptop to be abled to see that) :)
[14:56] <pitti> didrocks: on the binary driver!?
[14:56] <didrocks> pitti: indeed
[14:56] <didrocks> back to a state similar than lucid one
[14:56] <didrocks> with a not that much ugly plymouth
[14:57] <pitti> eww, tons of shadow windows with new compiz
[14:57] <didrocks> pitti: indeed, but let's wait on the new fixed one to see if it's still there
[14:57] <didrocks> pitti: you mean, black shadow until you click on the application, isn't it?
[14:57] <pitti> so, compiz from PPA seems heavily broken :(
[14:57] <didrocks> (when switching ws)
[14:58] <pitti> didrocks: apport-gtk windows staying around even after the process is gone
[14:58] <pitti> and in the foreground, bah
[14:58] <didrocks> pitti: yeah, this one is from it, with latest c-p-m
[14:58] <pitti> and on all desktops
[14:58] <pitti> didrocks: any workaround known?
[14:58] <didrocks> pitti: restarting unity (no need to logout/login)
[14:58] <didrocks> and stare at smspillaz to get the correct tarball
[15:00] <chrisccoulson> hmmm, i wonder if i should have a go at fixing bug 852406? i can't imagine it would be that hard :/
[15:00] <ubot2> Launchpad bug 852406 in linux "Phantom battery appears after resume from suspend" [Undecided,Confirmed] https://launchpad.net/bugs/852406
[15:01] <seb128> chrisccoulson, have a got at figuring why g-s-d is blocking the session for some seconds rather ;-)
[15:01] <chrisccoulson> heh
[15:03] <didrocks> pitti: sorry, maybe I was unclear: by "flicker free", I meant, there is still a black window between plymouth and lightdm for screen resolution change, but I get no anymore completely ugly logo and text on top of it
[15:06] <ricotz> hi, are there known issues with gnome-keyring, like having multiple instances?
[15:09] <rodrigo_> hmm, in which branch is libcolord-dev? lp:ubuntu/colord doesn't seem to exist
[15:10] <seb128> ricotz, no
[15:11] <seb128> rodrigo_, could be a udd bug, maybe james_w has an idea about it
[15:11] <seb128> rodrigo_, otherwise you can just update the "old" way, i.e without a vcs
[15:11] <rodrigo_> james_w, any idea? ^^
[15:11] <seb128> apt-get source etc
[15:11] <rodrigo_> yeah
[15:11] <ricotz> seb128, ok :), then there is something wrong here :\
[15:22] <mdeslaur> seb128: have you seen issues like I'm getting in bug 848198 ?
[15:22] <ubot2> Launchpad bug 848198 in gconf "Sporadic gconf error messages" [Undecided,New] https://launchpad.net/bugs/848198
[15:23] <seb128> mdeslaur, yes, seems to happen just after I install debs
[15:23] <mdeslaur> seb128: I sporadically get it with a bunch of different apps
[15:26] <mdeslaur> seb128: chrisccoulson had mentioned a problem with dbus getting slammed from one of the indicators, I wonder if that's what's causing it
[15:26] <seb128> mdeslaur, I doubt it, I get often the message from the bug but not often the indicator dbus slamming
[15:27] <mdeslaur> ok
[15:28] <james_w> rodrigo_, http://package-import.ubuntu.com/status/colord.html#2011-08-06%2003:21:19.112776
[15:30] <rodrigo_> james_w, oh :(
[15:31] <pitti> rodrigo_: I thought RAOF wanted to update colord in/through debian
[15:32]  * pitti back in 30
[15:32] <rodrigo_> pitti, yes, I'll wait for him, we need 0.1.12 for the new g-s-d release
[15:32] <rodrigo_> so yes, will wait for him
[15:35] <seb128> rodrigo_, no please don't wait for him
[15:35] <seb128> we need those GNOME updates in now if we want them for beta2
[15:35] <rodrigo_> seb128, why?
[15:35] <rodrigo_> ah ok
[15:35] <seb128> because we already are over beta2 freeze
[15:35] <seb128> it was before the w.e
[15:36] <seb128> we really want the new g-s-d in, there are quite some fixes in this version, would be a shame to beta2 test the old one
[15:46]  * mterry looks into a gvfs crash
[15:47] <seb128> mterry, which one?
[15:47] <mterry> seb128, bug 811761
[15:47] <ubot2> Launchpad bug 811761 in gvfs "gvfsd-dav crashed with SIGSEGV in g_vfs_backend_get_daemon()" [High,Triaged] https://launchpad.net/bugs/811761
[15:47] <seb128> ok ;-)
[15:48] <mterry> seb128, one of the few crash reports I've seen recently that I can actually reproduce, so I'm not letting it go  :)
[15:48] <seb128> hehe
[15:48] <seb128> bug #839828 seems popular as well
[15:48] <ubot2> Launchpad bug 839828 in gvfs "gvfsd-http crashed with SIGSEGV in g_settings_get_child()" [High,Confirmed] https://launchpad.net/bugs/839828
[15:48] <mterry> hadn't seen it yet
[15:49] <mterry> seb128, hrm that looks like a bad use of g_settings api at a quick glance.  I'll look more after gvfs
[15:49] <mterry> I mean, after the first bug
[15:49] <seb128> thanks
[15:57] <pitti> seb128: uh, ABI break in dconf?
[15:58] <seb128> pitti, yes, but libdconf is not used out of dconf itself
[15:58] <seb128> pitti, everything uses gsettings
[15:58] <pitti> ah, ok
[15:58] <pitti> seb128: that's still a rather central library, do you think we should squeeze it into b2?
[15:58] <seb128> desrt, ^
[15:59] <pitti> mterry: ah, assigning the bug to you then, thanks for looking into it
[15:59] <desrt> uhoh.
[15:59] <seb128> hey desrt ;-)
[16:00] <seb128> pitti, it seems fine to me but let's see what desrt says
[16:00]  * pitti grabs empathy
[16:01] <seb128> desrt, how confident are you that the new dconf and its abi break will create no issue? ;-)
[16:02] <desrt> seb128: not so confident.
[16:02] <desrt> seb128: you mean the 3 functions that got removed, right?
[16:02] <seb128> desrt, yes
[16:02] <desrt> nobody is using those
[16:03] <seb128> desrt, what are you not confident in for the update?
[16:03] <desrt> i guess i am confident
[16:03] <seb128> lol
[16:03] <seb128> you just said you were not ;-)
[16:03] <desrt> i'm not confident that it's not an ABI change, becasue it is
[16:03] <didrocks> seb128: the world changes in one minute you know… :-)
[16:03] <desrt> it will probably cause issues with your symbols file, for example
[16:03] <desrt> but in terms of real breaks
[16:04] <seb128> desrt, oh sorry that was not the question, I did the update including .symbols and uploaded
[16:04] <desrt> i think you're fine then
[16:04] <seb128> desrt, we are frozen for beta2 though so pitti is reviewing uploads and was pondering ack-ing it or not
[16:05] <seb128> desrt, reviewers don't like much api breaks around freeze times ;-)
[16:05] <desrt> nobody uses libdconf except to call _reset()
[16:05] <seb128> pitti, ^
[16:05] <seb128> pitti, I would say "go for it", it works fine for me at least
[16:05] <didrocks> desrt: even Qtdconf is fine?
[16:05] <desrt> yes
[16:05] <desrt> qtdconf is particular fine since it doesn't use that library at all
[16:06] <desrt> *particularly
[16:06] <didrocks> ah, indeed, that helps :-)
[16:06] <pitti> seb128: okay :)
[16:10] <mterry> didrocks, which PPA did you put the compiz update in?
[16:11] <desrt> mterry: odd crashes in gvfs
[16:11] <didrocks> mterry: still not the right compiz, hoping to get the new one put in ~ubuntu-desktop/ppa any time soon
[16:11] <mterry> didrocks, k
[16:11] <didrocks> mterry: but don't upgrade from it please! the current compiz in it is bad, I'll ping you
[16:11] <mterry> didrocks, ok!
[16:11] <chrisccoulson> heh, i upgraded from that ;)
[16:11] <chrisccoulson> i didn't notice it to be any worse though
[16:12] <didrocks> mterry: it's just good enough for chrisccoulson
[16:12] <chrisccoulson> lol
[16:12]  * didrocks hugs chrisccoulson :-)
[16:12] <mterry> desrt, those two bugs?  the first is not very surprising after looking at code.  I'll post a patch upstream soon
[16:12] <chrisccoulson> well, i switched to 2d anyway ;)
[16:12] <desrt> mterry: the second one looks like a typical case of incorrectly written/installed schemas
[16:12] <didrocks> chrisccoulson: happy you test it a lot! :-)
[16:12] <chrisccoulson> heh
[16:13] <chrisccoulson> did i mention that the icons in the dash in 2d look really nice? :)
[16:13] <desrt> mterry: these sorts of bugs used to be much more obvious when we aborted straight away...
[16:13] <didrocks> chrisccoulson: you mean, like you can have beers? :-)
[16:13] <chrisccoulson> :)
[16:14] <mterry> desrt, what?  gsettings doesn't abort all the time anymore?
[16:14] <mterry> can barely call it gsettings
[16:15] <desrt> mterry: no.  owen talked me out of it.
[16:15] <desrt> mterry: i think i might turn it on again next cycle.  it's causing more trouble than it's worth
[16:15] <desrt> same story as always -- nobody ever reads g_critical()
[16:15] <rodrigo_> hey desrt, seems glib 2.29.92 fixed the issue
[16:16] <desrt> the other option i'm pondering is to make g_critical() fatal by default :)
[16:16] <desrt> rodrigo_: the gsettings threading crash?
[16:16] <rodrigo_> desrt, fatal, like in logging you out, for instance? :D
[16:16] <rodrigo_> desrt, yes
[16:16] <chrisccoulson> yes, please turn it back on. you don't know the pain i had to go through to protect against aborts in firefox so that upstream would accept adding gsettings support in to the tree ;)
[16:16] <desrt> rodrigo_: excellent.
[16:16] <cyphermox> seb128: e-d-s ready, should I just upload it?
[16:16] <mterry> desrt, you might want to get some patsy to push that into git for you though
[16:16] <chrisccoulson> and now you turn it off, so my work is wasted :P
[16:16] <desrt> rodrigo_: individual apps (and language bindings perhaps) would have the option to turn criticals back down to merely warnings
[16:16] <desrt> i expect that python would turn them into exceptions, actually
[16:17] <rodrigo_> yeah
[16:17] <seb128> cyphermox, yes
[16:17] <mterry> rodrigo_, which gsettings crash bug are you talking about?
[16:19] <pitti> rodrigo_: oh, I see g-s-d landed, I thought that would require new colord?
[16:20] <rodrigo_> pitti, I added colord to the sponshor list -> https://bugs.launchpad.net/ubuntu/+source/colord/+bug/853956
[16:20] <ubot2> Ubuntu bug 853956 in colord "Update to 0.1.12" [Undecided,New]
[16:20] <pitti> rodrigo_: ah
[16:20] <rodrigo_> mterry, crash in threads, there are several bugs for it
[16:20] <desrt> mterry: btw: noticed you were into ido
[16:20] <rodrigo_> mterry, I jsut closed several of them, so you'll get mail for those if you want details
[16:20] <mterry> desrt, yeah, I've not done much with it in a couple years though
[16:20] <pitti> rodrigo_: you don't happen to have a ready .dsc somewhere? (or bzr branch, etc.)
[16:20] <mterry> rodrigo_, cool
[16:21] <htorque> chrisccoulson: sorry to interrupt, but you had a bug reported about the cut off dash icons in unity - i can't seem to find that?
[16:21] <desrt> mterry: my girlfriend is an aspiring esperantist and she's dragging me into it too
[16:21] <mterry> desrt, still the official GNOME translator for it, I think  :)
[16:21] <rodrigo_> pitti, yes, I do
[16:21] <desrt> mterry: ya.  that's how i found out :)
[16:21] <rodrigo_> pitti, do you want me to send them to you?
[16:21] <pitti> rodrigo_: can you put it on people or u1, or anywher?
[16:21] <rodrigo_> pitti, yes, sure, just the .dsc?
[16:21] <didrocks> smspillaz: trying to fetch myself all the bug # for the compiz upload as I didn't get anything yet. is bug #853734 in the tarball you gave me?
[16:21] <ubot2> Launchpad bug 853734 in compiz "maximized windows fail to update their input extents when undecorated" [High,Fix committed] https://launchpad.net/bugs/853734
[16:21] <pitti> rodrigo_: or just attach to the bug (diff.gz and dsc)
[16:21] <rodrigo_> ok
[16:21] <pitti> rodrigo_: debian.tar.gz as wel, of course
[16:21] <chrisccoulson> htorque, i didn't report a bug about cut-off icons. i reported one about blurry icons and ghosting, which i think was closed as "Opinion", and i was told that the blurry icons is by design
[16:22] <rodrigo_> pitti, hmm, no diff.gz
[16:22] <pitti> rodrigo_: .debian.tar.gz, presumably
[16:22] <seb128> rodrigo_, debian.tar.gz is source v3
[16:23] <htorque> chrisccoulson: yeah i left that comment, but you could also see the cut off "ghost icons" in your screenshot (the once at the bottom from "available for download"), not sure *that* is by design.
[16:23] <rodrigo_> pitti, but I have debian.tart.gz and .dsc
[16:23] <rodrigo_> ok
[16:23] <chrisccoulson> htorque, well, cut-off or no cut-off, i still think it looks completely broken
[16:23] <chrisccoulson> and i find it nauseating to look at ;)
[16:23] <rodrigo_> pitti, ok, both attached to https://bugs.launchpad.net/ubuntu/+source/colord/+bug/853956
[16:23] <ubot2> Ubuntu bug 853956 in colord "Update to 0.1.12" [Undecided,New]
[16:24] <desrt> didrocks: hey
[16:24] <didrocks> hey again desrt :)
[16:24] <desrt> didrocks: how reliable is this unity-panel-service crash?
[16:24] <cyphermox> seb128: uploaded.
[16:24] <didrocks> desrt: I never got it myself (fortunaly or unfortunaly), seems to be quite popular though
[16:24] <seb128> thanks
[16:25] <didrocks> desrt: I guess the stacktrace about the race is quite accurate
[16:25] <desrt> didrocks: we're musing about introducing some locks for g_setenv() vs. gettext
[16:26] <rodrigo_> out for a bit, bbl
[16:26] <desrt> didrocks: but i wonder: are those setenv calls at program init time, or is stuff already running?
[16:26] <htorque> chrisccoulson: which *is* an opinion (i agree with :P). however, there being cut-off icons seems like a valid bug why i wanted to subscribe to it, but if that's closed i'll probably open a new one. :)
[16:26] <didrocks> desrt: yeah, I saw the upstream discussion, I'm so surprised it's not thread-safe
[16:26] <didrocks> desrt: let me recheck
[16:26] <chrisccoulson> htorque, yeah, probably best to open a new one
[16:26] <chrisccoulson> good luck!
[16:26] <chrisccoulson> :)
[16:26] <htorque> heh
[16:27] <desrt> didrocks: it's one of those things that's so bloody obvious that you have to wonder how we got into this mess in the first place
[16:27] <mterry> My touchpad settings are not visible in g-c-c anymore?  And my tap-to-click setting got reset?
[16:27] <desrt> didrocks: at the same time, though, you can perfectly understand the process
[16:27] <seb128> mterry, they should be in the mouse capplet
[16:28] <didrocks> desrt: exactly, it's surprising it wasn't triggered before. Confirming, everything is at init time
[16:28] <mterry> seb128, I don't have the 'touchpad' tab in that capplet anymore
[16:28] <seb128> mterry, what config do you have?
[16:28] <seb128> mterry, are you sure it was there before?
[16:28] <didrocks> desrt: some before gtk_init, so I guess it's not triggered, but the a11y part, after it
[16:28] <seb128> mterry, can you pastebin an xinput list log?
[16:28] <desrt> didrocks: the ally part could be the problem
[16:29] <desrt> didrocks: unfortunately, by the time the damage is done in getenv() the thread that called setenv() is probably quite far away from the scene of the crime
[16:29] <seb128> is somebody here using nouveau?
[16:29] <mterry> seb128, I don't remember the last time I checked whether it was there.  It used to be in natty at least...
[16:29] <pitti> rodrigo_: thanks, sponsored
[16:30] <mterry> seb128, xinput list: http://pastebin.ubuntu.com/693160/
[16:30] <seb128> mterry, ok, yours should be there, that's a bug I guess
[16:31] <desrt> didrocks: so what do you want to do?
[16:31] <didrocks> desrt: I like how this sounds. Seems like the perfect crime :-)
[16:31] <seb128> mterry, I just wanted to check that you don't have an alps pad, those are not supported correctly
[16:31]  * mterry reports a bug
[16:31] <seb128> that's what I got on my dell
[16:31] <seb128> ok
[16:31] <seb128> nobody is on nouveau there?!
[16:32] <didrocks> re
[16:32] <seb128> didrocks, is nouveau working for you? ;-)
[16:32] <didrocks> 18:29:16         desrt | didrocks: unfortunately, by the time the damage is done in getenv() the thread that called setenv() is probably quite far away from the scene of the crime
[16:32] <didrocks> 18:29:44      didrocks | desrt: I like how this sounds. Seems like the perfect crime :-)
[16:32] <didrocks> desrt: didn't get anything else
[16:32] <desrt> didrocks: ah.  i said "so what do you want to do?"
[16:33] <didrocks> seb128: hum, didn't try it TBH, seems people are telling its better than last cycle on the french forum
[16:33] <desrt> you can try to go around killing off setenv() calls, or i can try to give seb a hacky vendorpatch for glib to try to workaround the issue
[16:33] <desrt> either by disabling gettext or by trying to lock (and hope that all your setenv calls are via g_setenv() and not straight setenv())
[16:33] <didrocks> desrt: the setend seems quite necessary for the AT binding from what API commented
[16:34] <desrt> we could also try to get someone who knows about these things to patch the libc to be threadsafe for setenv()
[16:34] <seb128> didrocks, they can maybe try bug #849954 for slangasek so we can get ffb in beta2? ;-)
[16:34] <ubot2> Launchpad bug 849954 in plymouth "FFe: enable flicker-free boot with lightdm" [Medium,Incomplete] https://launchpad.net/bugs/849954
[16:34] <didrocks> desrt: they are done by gsetenv
[16:34] <seb128> didrocks, it's a one liner change to an upstart job
[16:34] <desrt> didrocks: you have no idea what random libraries you might be calling that are doing setenv() for themselves
[16:35] <slangasek> seb128, didrocks: if it would help us get testers I'm happy to push to a ppa
[16:35] <didrocks> seb128: as it to be done today? I still need to find myself all compiz bugs as it wasn't done by upstream
[16:35] <didrocks> going to nouveau is the time consumer part I guess
[16:35] <seb128> didrocks, can you ask the forum guys to test if some run nouveau?
[16:35] <slangasek> yes, today is pretty much the last window for getting the plymouth change in for beta2, I think
[16:36] <didrocks> desrt: indeed, I hope it's really our calls doing that, we can maybe try first by killing those call and ask our users to test it from a ppa
[16:36] <mdeslaur> slangasek: give me a moment, and I'll test it with nouveau
[16:36] <didrocks> give me a minute
[16:36] <didrocks> trying to finish compiz
[16:36] <didrocks> and then, on the nouveau part
[16:36] <desrt> okay.  poke me when we can talk about this properly.
[16:36] <didrocks> desrt: yeah, I think it will be tomorrow if you don't mind
[16:37] <desrt> didrocks: that's totally fine
[16:37] <desrt> rodrigo_: you have this locale monitor branch in glib...
[16:37] <slangasek> mdeslaur: yay, thanks
[16:38] <didrocks> ah, if mdeslaur is on it, that's nice :)
[16:38] <seb128> pitti, urg, bug #853973
[16:38] <ubot2> Launchpad bug 853973 in gucharmap "package libgucharmap7 1:3.0.1-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/libgucharmap_2_90.so.7.0.0', which is also in package libgucharmap-2-90-7 1:3.1.92-0ubuntu1" [Undecided,Confirmed] https://launchpad.net/bugs/853973
[16:38] <pitti> seb128: yeah, I guess I'll fix that right now then
[16:38] <seb128> thanks
[16:38] <pitti> just testing empathy update, then sending it queuewards
[16:38] <didrocks> ok, pushed the compiz, ,hoping the bug # are correct, if not, upstream will fix those or not…
[16:40] <smspillaz> didrocks: nope its not
[16:41] <smspillaz> oh
[16:41] <smspillaz> did someone say that nouveau needs testing wtih something ?
[16:41]  * smspillaz runs nouveau
[16:42] <smspillaz> seb128: ^ ?
[16:42] <didrocks> smspillaz: can you get the bug list as you promissed then?
[16:42] <smspillaz> didrocks: yeah, sure
[16:42] <seb128> smspillaz, bug #849954
[16:42] <ubot2> Launchpad bug 849954 in plymouth "FFe: enable flicker-free boot with lightdm" [Medium,Incomplete] https://launchpad.net/bugs/849954
[16:42] <seb128> smspillaz, but get didrocks's bugslist first I guess ;-)
[16:42] <smspillaz> allright
[16:44] <didrocks> smspillaz: list I had right now: http://paste.ubuntu.com/693168/
[16:45] <smspillaz> thanks
[16:47] <didrocks> mdeslaur: can try nouveau now if you are not on it
[16:47] <mdeslaur> didrocks: I'm doing it now
[16:47] <didrocks> mdeslaur: ok, great :)
[16:49] <Sarvatt> isn't the nouveau drm backend for plymouth disabled via a distro patch?
[16:49] <Sarvatt> you have to boot with plymouth:force-drm to enable it I believe
[16:51] <Sarvatt> #ifdef GDM_HANGING_IS_FINE_WITH_ME ha
[16:51] <seb128> slangasek, ^
[16:52] <slangasek> yes, I believe it falls back to the framebuffer interface
[16:52] <slangasek> which we still want to test
[16:52] <slangasek> I'm not asking for testing any weird non-standard scenarios, just to make sure we don't regress on the default path
[16:53] <slangasek> by, for instance, causing lightdm to hang :P
[16:53] <Sarvatt> thought only the drm renderer worked with flicker free
[16:55] <mhr3> cyphermox, ping, hey my NetworkManager doesn't want to start after latest updates
[16:55] <mhr3> it says it can't find libnss3.so
[16:56] <kenvandine> mhr3, i just had that problem too
[16:57] <kenvandine> /usr/lib/x86_64-linux-gnu/libnss3.so was missing
[16:57] <kenvandine> i just re-installed the deb from the cache and it was fine
[16:57] <mhr3> i ended up symlinking it
[16:57] <kenvandine> i thought it was because my laptop died during an upgrade
[16:57] <kenvandine> weird that you hit it too
[16:57] <kenvandine> must not have been related
[16:57] <cyphermox> doesn' t sound good, but it's not NM, but libnss
[16:57] <kenvandine> but the deb seemed fine
[16:58] <cyphermox> let me test with this machine, I should be able to trigger that issue
[16:58] <kenvandine> cyphermox, reinstall of libnss3 fixed it though...
[16:58] <kenvandine> cyphermox, the package was still installed, but the lib was missing
[16:58] <cyphermox> kenvandine: yeah, but what might have triggered libnss to break?
[16:59] <kenvandine> for me, my laptop died during the upgrade so i thought it corrupted it... but that must not be what happened
[16:59] <GunnarHj> pitti: Posted some clarifications at https://code.launchpad.net/~gunnarhj/language-selector/fontconfig/+merge/75045 Awaiting your further comments before I change anything.
[16:59] <kenvandine> the deb i had in my apt cache was fine though
[17:00] <mhr3> i had fresh beta1, i was upgrading ~500 packages, but it went fine
[17:03] <cyphermox> mhr3: check what this outputs:  grep libnss3 /var/lib/dpkg/info/*
[17:05] <didrocks> pitti: chrisccoulson: mterry: seb128: new compiz built and published in the ubuntu-desktop ppa. Don't look at the bug list, it's inaccurate apparently but as I couldn't get an updated one despite the many requests through the day…
[17:05] <seb128> didrocks, ok
[17:06] <chrisccoulson> didrocks, thanks
[17:06] <chrisccoulson> does that fix the stacking issues?
[17:06] <mdeslaur> slangasek: tested with nouveau, bug updated
[17:07] <pitti> seb128: hm, I did the gucharmap update in bzr, but seeing that it affects four packages, like abiword, I think we should better revert to 3.0.1; WDYT?
[17:08] <pitti> hm, abiword doesn't actually seem to require it
[17:08] <didrocks> chrisccoulson: it should
[17:08] <seb128> pitti, revert http://git.gnome.org/browse/gucharmap/commit/?id=1f3b859eb4b59af148a890fa1ee3c4d92e05b709
[17:08] <seb128> pitti, ?
[17:08] <htorque> slangasek: if you still need nouveau feedback - works fine here, still no logo, but the text screen before lightdm is gone.
[17:08] <pitti> seb128: ah, yes, even better :)
[17:08] <chrisccoulson> cool :)
[17:09] <htorque> slangasek: (no cryptsetup)
[17:10] <mdeslaur> htorque: is plymouth corrupted for you?
[17:10] <slangasek> mdeslaur, htorque: you rock, thanks!
[17:11] <htorque> mdeslaur: right before lightdm starts i get a purple/garbled screen, yes, but that was the case before too.
[17:12] <mdeslaur> htorque: ok, same here
[17:12] <mdeslaur> htorque: that's plymouth having a fit :P
[17:12] <mhr3> cyphermox, http://paste.ubuntu.com/693187/
[17:12] <mhr3> maybe you see something weird :)
[17:13] <slangasek> mdeslaur: take it up with the framebuffer implementation, it's not plymouth's fault it doesn't map coherently to your output :)
[17:13] <dobey> pitti: should i bug you for a couple (string/ui) freeze exceptions? :)
[17:13] <pitti> dobey: better discuss with the doc team (mdke/jbicha), release team defers to them anyway
[17:13] <pitti> and for string changes, dpm
[17:14] <mdeslaur> slangasek: hehe
[17:15] <cyphermox> mhr3: nothing jumps out, no.
[17:15] <smspillaz> didrocks: http://paste.ubuntu.com/693192/
[17:15] <dobey> pitti: so on one of them there's a +1 from dpm and jbicha; do i need to wait for release team to say it's good?
[17:15] <didrocks> smspillaz: thanks
[17:15] <pitti> dobey: fine then
[17:15] <mhr3> cyphermox, afaict the libnss3:amd64.list:/usr/lib/x86_64-linux-gnu/libnss3.so just wasn't there
[17:17] <dobey> pitti: also u1 isn't in the ubuntu docs really i think, so not so much an issue for that; the other bug i'm curious about for freeze approval is bug #849494 :)
[17:17] <ubot2> Launchpad bug 849494 in ubuntuone-control-panel "String freeze exception: still offers Evolution plug-in for contact sync in Oneiric" [High,In progress] https://launchpad.net/bugs/849494
[17:18] <dobey> hrmm, and no dpm around :-/
[17:18] <pitti> dobey: already approved, see comment 16
[17:18] <dobey> 16?
[17:18] <dobey> there are only 9 comments
[17:18] <cyphermox> mhr3: kenvandine: weird thing is, I just crashed with a kernel oops in ksoftirq
[17:18] <pitti> sorry, 6
[17:18] <pitti> dobey: ^
[17:18] <dobey> oh right; ok. thanks
[17:19] <dobey> chrisccoulson: ping
[17:19] <jbicha> dobey: if it's a string freeze exception you need to let the translators list know
[17:19] <kenvandine> mhr3, right... the file wasn't there but i checked with dpkg -S and dpkg  knew about the file and the package that owned it
[17:20] <dobey> jbicha: was already done :)
[17:20] <jbicha> oh ok, carry on :)
[17:21] <mhr3> kenvandine, then something deleted it
[17:21] <dobey> i wonder how i am going to fix my laptop after upgrading to oneiric on it
[17:22] <cyphermox> mhr3: however my system still appears fine, and I still have libnss3, although not all configurations are done
[17:23] <mhr3> cyphermox, i really can't say what caused it, i just know it was gone
[17:26]  * didrocks waves good evening, need to run outside to think :)
[17:26] <pitti> didrocks: good night, sleep well!
[17:27] <didrocks> pitti: thanks! keep me posted on how it goes with the ppa :)
[17:28] <dobey> where is thunderbird-couchdb?! :(
[17:28] <seb128> ok, I'm out for dinner, I will be back a bit later to check on GNOME updates
[17:29] <seb128> will do the ones available then
[17:29] <seb128> bbl
[17:31] <mterry> smspillaz, (testing the new compiz from the PPA): stacking issues seem fine, but I got an half-visible window when I closed a dialog that isn't going away (http://ubuntuone.com/7GfdLX3zLT1VoVFIJqZYHj)
[17:31] <pitti> TTFN for me as well, see you tomorrow!
[17:32] <smspillaz> mterry: did you update your plugins-main ?
[17:32] <mterry> smspillaz, yes
[17:33] <smspillaz> hm
[17:33] <smspillaz> ok I'll look into it tomorrow
[17:41] <htorque> mterry: same thing i got, also (context) menus like to get stuck
[17:53] <dobey> gnome-panel is very crashy in oneiric
[17:54] <dobey> and i can't see how to make it have the configuration i had before i upgraded :(
[17:57] <chrisccoulson> hi dobey
[17:58] <chrisccoulson> woah, so, color + power account for 1 second of g-s-d startup here!!
[17:58] <chrisccoulson> i wonder wth is it doing?
[17:58] <chrisccoulson> brb
[17:58] <dobey> chrisccoulson: hey. so thunderbird-couchdb? :)
[17:58] <dobey> doh
[17:59] <ejat> can someone look at bug 854008
[17:59] <ubot2> Launchpad bug 854008 in gucharmap "package libgucharmap7 1:3.0.1-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/libgucharmap_2_90.so.7.0.0', which is also in package libgucharmap-2-90-7 1:3.1.92-0ubuntu1" [Undecided,New] https://launchpad.net/bugs/854008
[18:02] <chrisccoulson> wow, just wow. xrandr plugin - 2.1 seconds!
[18:02] <chrisccoulson> now i see why gsd holds my session up for 5 seconds
[18:07] <dobey> chrisccoulson: hey. so thunderbird-couchdb? :)
[18:08] <chrisccoulson> ah :)
[18:08] <chrisccoulson> yes, will upload that in a moment
[18:08] <chrisccoulson> just trying to figure out why my session takes so long to load ;)
[18:08] <dobey> unity ;)
[18:09] <ejat> :)
[18:16] <jbicha> gnome-shell should depend on gnome fallback? bug 852950
[18:16] <ubot2> Launchpad bug 852950 in gnome-shell "Depend gnome-session-fallback" [Undecided,New] https://launchpad.net/bugs/852950
[18:21] <chrisccoulson> dobey, well, unity is slow
[18:22] <chrisccoulson> but gnome-settings-daemon is terrible
[18:22] <chrisccoulson> bug 854101
[18:22] <ubot2> Launchpad bug 854101 in gnome-settings-daemon "gnome-settings-daemon takes waaaaaaaay too long to start" [Undecided,New] https://launchpad.net/bugs/854101
[18:22] <chrisccoulson> power/color/xrandr plugins account for ~3.1 seconds of session loading
[18:22] <dobey> chrisccoulson: eh, from my pov, oneiric has totally destroyed my configuration on my laptop :(
[18:26] <mterry> smspillaz, when you look at that ghost window tomorrow, note that dpkg apparently wasn't done with "setting up" all my packages, including compiz-plugins-main, so my issue may be junk (though htorque did report similar behavior)
[18:27] <zyga> is mvo still on holiday?
[18:28] <chrisccoulson> zyga, no, but he's likely to have finished for the day already
[18:31] <zyga> chrisccoulson, ok, good news
[18:38]  * kenvandine heads out in search of food, bbiab
[18:41] <pitti> rodrigo_: are you still working on a new control-center upload today, or should we do that post-b2?
[18:41] <rodrigo_> pitti, post-b2 better I think, as it depends on an unreleased network-manager
[18:42] <rodrigo_> desrt, so, what's up with the locale monitor branch in glib?
[18:42] <pitti> rodrigo_: ack
[18:42] <desrt> rodrigo_: you wrote it, right?
[18:42] <htorque> chrisccoulson: maybe connected to output probing? see later comments and charts in bug 828112.
[18:42] <ubot2> Launchpad bug 828112 in unity-greeter "Password field feedback slow at times" [High,Triaged] https://launchpad.net/bugs/828112
[18:42] <rodrigo_> desrt, I think it can be removed, until there's really a way to actually change the lang of apps on the fly
[18:43] <pitti> chrisccoulson, rodrigo_: can you think of any other new gnome upstream release which ought to get into b2? we need to start building images
[18:43] <desrt> rodrigo_: right.  that's what i wanted your opinion on
[18:43] <desrt> how exactly do you envision that working?
[18:43] <rodrigo_> desrt, yes, I did, based on some discussions with mclasen
[18:43] <rodrigo_> desrt, right now, I don't, apart from loging out and back in :)
[18:43] <pitti> I don't see anything else pending on http://people.canonical.com/~platform/desktop/versions.html
[18:44] <pitti> a new gnome-color-manager might be nice, but that's less critical
[18:44] <desrt> rodrigo_: we're having some concurrency issues with gettext at the moment, so i'm sort of curious
[18:44] <chrisccoulson> pitti - i can't think of anything that needs to go in
[18:44] <seb128> re
[18:45] <pitti> new nautilus and gvfs might be nice, but nothing released yet
[18:45] <pitti> wb seb128, just in time
[18:45] <seb128> time for what?
[18:45] <pitti> seb128: can you think of any other new gnome upstream release which ought to get into b2? we need to start building images
[18:45] <chrisccoulson> htorque, yes, it is related to output probing, i'd discovered that already (see my comment on bug 854101)
[18:45] <ubot2> Launchpad bug 854101 in gnome-settings-daemon "gnome-settings-daemon takes waaaaaaaay too long to start" [Undecided,New] https://launchpad.net/bugs/854101
[18:45] <pitti> seb128: control-center is blocked, and versions.html doesn't have other stuff which seems urgent
[18:45] <dobey> rodrigo_: btw, did you figure what was up with e-d-s/couchdb?
[18:45] <seb128> pitti, did you guys package the stack that got released while I was at dinner?
[18:45] <seb128> pitti, g-c-c would be nice
[18:45] <pitti> seb128: I was saying that a new gvfs and nautilus would be nice, but they need releases first?
[18:45] <seb128> pitti, nautilus had one
[18:45] <seb128> I'm on it
[18:45] <pitti> oh
[18:46] <seb128> they got
[18:46] <htorque> chrisccoulson: ah, missed that link. :-)
[18:46] <seb128> - gnome-menus
[18:46] <seb128> - pygobject
[18:46] <seb128> - libwnck
[18:46] <seb128> - nautilus
[18:46] <rodrigo_> dobey, no, I'm about to test the new version and do some debug if it still doesn't work
[18:46] <seb128> - gconf
[18:46] <pitti> seb128: I did pygobject in Debian, breaks stuff; -> post b2
[18:46] <seb128> - gtksourceview3
[18:46] <seb128> - cogl (not on the CD)
[18:46] <dobey> rodrigo_: ah ok
[18:46] <rodrigo_> seb128, I'll do gnome-menus
[18:46] <pitti> seb128: I'll do gnome-menus
[18:46] <chrisccoulson> seb128, i'm going to wish i never started looking at g-s-d soon ;)
[18:46] <seb128> pitti, I'm doing nautilus, gconf, gtksourceview3
[18:46] <seb128> chrisccoulson, ;-)
[18:46] <pitti> rodrigo_: ok, you were first :)
[18:46] <seb128> what is blocking g-c-c?
[18:46] <rodrigo_> pitti, :)
[18:47] <rodrigo_> seb128, new network-manager-applet
[18:47] <seb128> we should really get that one in, it's one of those that have a stack of commits
[18:47] <rodrigo_> libnm-gtk, which is there now
[18:47] <seb128> can't you just revert that commit?
[18:47] <rodrigo_> yes, I can
[18:47] <seb128> can you do this and let gnome-menus to pitti?
[18:47] <seb128> pitti, libwnck3 as well if you want to do it
[18:48] <rodrigo_> yes, sure, pitti gets gnome-menus
[18:48] <pitti> rodrigo_: after all! :-)
[18:48] <pitti> yes, on it
[18:49] <rodrigo_> :)
[18:52] <rodrigo_> well, reverting that patch in g-c-c might need some more reverts
[18:52] <rodrigo_> I'll have dinner and continue later
[18:53] <pitti> meh, lp:ubuntu/libwnck3 is completely f**ed up
[18:56] <jbicha> seb128: the gnome-help links in nautilus should point to ubuntu-help instead
[18:57] <seb128> jbicha, do you have a patch?
[18:57] <jbicha> not yet, I can make one
[18:58] <seb128> jbicha, that would be welcome ;-)
[19:01] <pitti> seb128: did you already start with sourceview3, or want me to take it? my two from above are trivial
[19:01] <seb128> pitti, feel free to take it
[19:01] <pitti> taking then
[19:01] <seb128> still dealing with nautilus which needs some patches updates
[19:02] <pitti> please forgive the dumb question, how do I get the classic 2d gnome-panel session these days?
[19:02] <pitti> (in lightdm, I mean)
[19:03] <seb128> pitti, install gnome-session-fallback
[19:03] <pitti> ah, -fallback, thanks
[19:03] <pitti> was looking for -classic or somethign such
[19:03] <pitti> I know no better way for testing gnome-menus
[19:04] <seb128> pitti, yeah, out of trying a menu editor or the application lens in unity
[19:05] <pitti> oh heck, a classic gnome session with metacity feels OMGFAST!
[19:05] <bryceh> :-)
[19:05] <seb128> to start?
[19:05] <pitti> to anything
[19:06] <pitti> start, menus, clicking, shutdown, etc.
[19:07] <jbicha> seb128: http://paste.ubuntu.com/693258/
[19:07] <seb128> jbicha, can you just commit it to the vcs?
[19:10] <pitti> ooh, pygobject 3.0.0; I was packaging 2.29.4
[19:11] <pitti> will do that in Debian, and fix the breakage over the freeze
[19:12] <jbicha> seb128: done
[19:12] <seb128> jbicha, thanks
[19:15] <pitti> seb128: all done; more to go?
[19:15] <pitti> bah, we outperform versions.html
[19:15] <seb128> jbicha, do you think you can finish the nautilus update? I'm having build issues because my system is not uptodate
[19:15] <seb128> I'm updating but it's going to take some 15 minutes...
[19:19] <jbicha> seb128: I could, do you want to push what you have?
[19:19] <seb128> jbicha, I just did
[19:19] <seb128> rodrigo_, pitti did the vala update
[19:20] <pitti> rodrigo_: yes, it's in unapproved and in bzr
[19:20]  * pitti thinks it's awesome to see our packaging army at work
[19:22] <pitti> jbicha: can you please have a quick look at bug 844049?
[19:22] <ubot2> Launchpad bug 844049 in ayatana-design "UIFe: Indicators - Device indicator icon looks like it has an emblem" [High,Fix released] https://launchpad.net/bugs/844049
[19:22] <pitti> jbicha: the fix is in unapproved, so if this is ok, I'd accept it now, so that we have it for beta; if not, I'll hold it back
[19:26] <seb128> jbicha, did you upload your vino update?
[19:27] <jbicha> pitti: ok, I gave my approval
[19:29] <pitti> jbicha: ah, great
[19:29] <jbicha> seb128: no, but I have now, multi-tasking :-)
[19:29] <seb128> ;-)
[19:31] <seb128> pitti, once nautilus and gedit (which I'm just building) are uploaded I think we are mostly done with interesting ones
[19:32] <seb128> g-c-c would be nice but rodrigo_ had depends issue on it so we should wait on that
[19:35] <geser> which package creates /etc/timezone? For some reason I didn't have that file which resulted in my datetime indicator not working (only displaying the text "Time")
[19:36] <flacoste> hi! i'd like to report a bug against the 'Time & Date' indicator, but I don't know which package is involved
[19:38] <jcastro> flacoste: indicator-datetime
[19:38] <flacoste> thx jcastro!
[19:41] <pitti> seb128: ok, thanks
[19:42] <flacoste> of course, it was already reported
[19:43] <flacoste> and even better, a fix was commited upstream
[19:45] <seb128> pitti,
[19:45] <seb128> http://download.gnome.org/sources/gnome-desktop/3.1/gnome-desktop-3.1.92.tar.bz2
[19:46] <pitti> seb128: on it
[19:46] <seb128> http://download.gnome.org/sources/gnome-power-manager/3.1/gnome-power-manager-3.1.92.tar.bz2
[19:46] <seb128> if somebody wants to grab those
[19:46] <seb128> pitti, we are in low priority ones now I guess so if you guys want to stay stop and start rolling images just say so
[19:46] <pitti> seb128: we are waiting for g-c-c mostly at this point; everything we can do in parallel is still ok
[19:47] <pitti> once g-c-c is in, we'll build
[19:48] <pitti> oh, and naughtylus
[19:49] <seb128> pitti, let's not wait on g-c-c imho
[19:49] <pitti> I thought that was the "interesting" one?
[19:49] <seb128> not sure but I've the feeling it will take a while
[19:49] <pitti> ok, apport, jockey, software-center, software-properties-gtk all work great with pygobject 3.0.0
[19:50] <pitti> just gtimelog breaks
[19:50] <seb128> pitti, right but rodrigo_ said it depends on a new nm-applet version and that he would look at reverting the commit that added the new version but that it could lead to other reverts
[19:50] <seb128> rodrigo_ left for dinner as well
[19:50] <pitti> but I'd like to test 3.0.0 with ubiquity, so still post b2
[19:50] <seb128> so I wouldn't could on it for today
[19:50] <pitti> seb128: ok
[19:50] <seb128> could->count
[19:50] <pitti> seb128: ok, so nautilus and then done?
[19:50] <seb128> yes
[19:50] <seb128> gnome-desktop3 would still be nice if you are on it
[19:51] <pitti> yep, doing now
[19:51]  * jbicha waiting for nautilus to build again
[19:52] <seb128> jbicha, do you know if there are lot of sources to patch for the gnome->ubuntu documentation?
[19:53] <jbicha> seb128: I believe it's just vino & nautilus, most apps provide their own help
[19:53] <seb128> ok, great ;-)
[19:53] <jbicha> I need to update jockey's help button though
[19:53] <seb128> we got bug #853137 today
[19:53] <ubot2> Launchpad bug 853137 in seahorse "The page 'gkr-keyring' was not found in the document 'ghelpseahorse'." [Low,Confirmed] https://launchpad.net/bugs/853137
[19:53] <seb128> but I guess it's a seahorse bug
[19:53] <seb128> nothing to do with the ubuntu documentation
[19:55] <jbicha> seb128: also gnome-control-center but that's already been done
[19:55] <jbicha> *updated for ubuntu-help
[19:56] <seb128> ok
[20:00] <pitti> seb128: gpm and g-desktop3 done, both easy and work fine
[20:02] <seb128> pitti, great
[20:08] <pitti> jbicha: is nautilus making any trouble? i. e. any risk for b2?
[20:09] <jbicha> pitti: looks like my dput got stuck, will try again
[20:09] <pitti> oh, awesome
[20:11] <jbicha> wow, compact view has some major issues though
[20:16] <pitti> jbicha: BTW, if dput is causing you trouble, I'm happy to upload it for you from bzr
[20:17] <jbicha> pitti: please, it keeps timing out at 5547/5548k
[20:17] <pitti> of course; why would it break at 1/5548..
[20:17] <pitti> jbicha: thanks for the update!
[20:18] <pitti> seb128: with nautilus being in now as well, that's it for b2?
[20:19] <pitti> jbicha: upped
[20:19] <seb128> pitti, they will roll random side tarballs until tomorrow but I don't see anything worth delaying images
[20:19] <pitti> agreed
[20:19] <seb128> g-c-c would be nice to get but I don't see that happen today
[20:19] <pitti> gvfs would have been nice, but not the end of the world
[20:19] <pitti> (it fixes a crasher with some dupes)
[20:19] <seb128> gvfs has 2 commits and translations
[20:20] <seb128> oh, which one?
[20:20] <pitti> seb128: bug 447695
[20:20] <ubot2> Launchpad bug 447695 in gvfs "Nautilus cannot write to shared Vista/Win7 folders with desktop.ini file" [Low,Fix committed] https://launchpad.net/bugs/447695
[20:20] <pitti> but nothing that spoils the beta
[20:23] <seb128> right
[20:23] <pitti> so, good night everyone! (again)
[20:26] <rodrigo_> seb128, it's happening, if it builds
[20:26] <rodrigo_> working on it now
[20:28] <chrisccoulson> b'ah, still getting weird issues even with the latest compiz
[20:29] <DBO> define latest compiz
[20:29] <chrisccoulson> this is totally and utterly broken
[20:29] <DBO> and define issues
[20:29] <chrisccoulson> DBO - from the ubuntu-desktop PPA
[20:29] <DBO> are the issues
[20:29] <DBO> windows get stuck on my screen when I close/minimize them?
[20:29] <chrisccoulson> DBO - yes, you beat me to it ;)
[20:29] <DBO> fucking hell
[20:30] <DBO> I need to get a patch in there
[20:30] <DBO> but I dont know
[20:30] <DBO> how
[20:30] <chrisccoulson> DBO, oh, you have a fix already?
[20:30] <DBO> sure
[20:30] <DBO> it was never broken
[20:30] <DBO> the wrong animation plugin got mixed in...
[20:32] <mterry> DBO, what's the patch?  I can put it in the package
[20:32] <mterry> in the PPA
[20:33] <DBO> mterry, there is an animation plugin
[20:33] <DBO> in compiz-plugins-main
[20:33] <DBO> it was supposed to be updated with the new core
[20:33] <DBO> but no new package appears to have been pushed
[20:33] <DBO> https://code.launchpad.net/~compiz-team/compiz-animation-plugin/0.9.5
[20:33] <DBO> that code
[20:33] <DBO> needs to be used with latest core
[20:33] <DBO> or you get ghost windows
[20:33] <DBO> like mad
[20:34] <DBO> so yeah... thats all I got
[20:36] <DBO> mterry, do you want me to tarball it up or you just want to hack it in yourself?
[20:36] <DBO> (seeing as I have no clue what I would be doing really)
[20:37] <mterry> DBO, looking to see if I understand situation (/me looks at what we have in PPA)
[20:40] <mterry> DBO, the package in the PPA says it uses today's bzr snapshot...
[20:42] <DBO> mterry, checking
[20:46] <DBO> mterry, src/animation.cpp is not correct
[20:46] <DBO> they are different in the different versions
[20:47] <DBO> so are the corresponding xml files
[20:48] <mterry> DBO, can you tell if that is all that's missing or did we screw up when making the snapshot in other ways?
[20:48] <DBO> mterry, looks like we grabbed the oneric trunk rather than trunk trunk
[20:48] <DBO> I cant promise about upgrade paths
[20:48] <DBO> since I just dont know what they are
[20:49] <DBO> also I dont know if the diffs in the xml files are from your guys or us
[20:49] <kenvandine> i would imagine we want to stick with the oneiric trunk
[20:49] <DBO> kenvandine, no
[20:49] <DBO> we cant
[20:49] <DBO> the point of this test
[20:49] <DBO> is so we can merge into the oneiric trunk
[20:49] <kenvandine> i see
[20:49] <kenvandine> so the snapshot should have been taken from the other branch
[20:50] <DBO> right
[20:51] <mterry> DBO, https://code.launchpad.net/~compiz-team/compiz-animation-plugin/0.9.5 is trunk-trunk?
[20:52] <kenvandine> DBO, i think smspillaz was creating the tarballs
[20:53] <kenvandine> was my impression, based on the chat i saw between him and didrocks
[20:53] <kenvandine> DBO, so you are sure what was uploaded was wrong?
[20:54] <DBO> yes
[20:54] <kenvandine> ok
[20:54] <DBO> mterry, yes
[20:54] <mterry> DBO, do you know if this is true for all the plugins or just the animation one?
[20:54] <seb128> DBO, sept. 19 13:42:30 <smspillaz>	didrocks: https://chinstrap.canonical.com/~smspillaz/releases/0.9.5.94ub1/compiz-plugins-main_0.95rev27.orig.tar.gz . The only thing that's changed is that I fixed bug https://bugs.launchpad.net/compiz-plugins-main/+bug/853807
[20:55] <ubot2> Ubuntu bug 853807 in unity "crash when looping paint list in preparePaint (on closing windows)" [High,Fix committed]
[20:55] <seb128> mterry, ^
[20:55] <DBO> mterry, just the animation one
[20:55] <seb128> that's what is in the ppa I think
[20:56] <DBO> mterry, the animation plugin is the only plugin with a "critical" change
[20:56] <rodrigo_> ok, g-c-c built
[20:56] <DBO> chrisccoulson, btw
[20:56] <DBO> if you want to fix your system for a bit
[20:56] <kenvandine> rodrigo_, i see that gnome-contacts is more useful now... woot!
[20:56] <DBO> disable the animation plugin
[20:56] <DBO> when the new plugins go up
[20:56] <DBO> turn it back on
[20:56] <rodrigo_> kenvandine, yes, much more :)
[21:01] <mterry> FYI, I'm working on updating the animation plugin in the PPA
[21:01] <mterry> (in case that wasn't clear)
[21:02] <rodrigo_> seb128, g-c-c uploaded, is it in time?
[21:02] <seb128> pitti, ^
[21:03] <rodrigo_> I thought he'd gone :)
[21:03] <seb128> rodrigo_, let's see if they ack it before starting rolling images
[21:03] <rodrigo_> ok
[21:03] <seb128> rodrigo_, yeah, well he will read backlog tomorrow, I doubt any other r-t members will ack it while he's not there
[21:03] <seb128> so let's see tomorrow
[21:03] <seb128> we can probably get it in, it will be on updates and on respins if there is any
[21:04] <seb128> which is likely
[21:04] <rodrigo_> ok
[21:05] <rodrigo_> I'll go watch a film or something, so good night!
[21:05] <kenvandine> good night rodrigo_!
[21:08] <seb128> 'night rodrigo_
[21:11] <seb128> rodrigo_, ok, I pinged them, g-c-c got reviewed and is in
[21:15] <popey> cjwatson: as I recall you did some work on ubiquity in relation to EFI installs. I have done a clean install on an Apple Mac laptop, and I suspect that the install has been done in "EFI mode" rather than "BIOS mode". As a result the nvidia binary driver doesn't work. Which sucks a bit.
[21:15] <popey> cjwatson: citation:-
[21:15] <popey> bah, http://mjg59.dreamwidth.org/2929.html?thread=54129#cmt54129
[21:16] <popey> cjwatson: so my question is, how do I install in "BIOS mode"?
[21:36] <mterry> DBO, (just fyi, I updated the plugins in the PPA)
[21:36] <DBO> mterry, now is the part where I start praying everything is okay...
[21:37] <mterry> DBO, heh, I hope you're in good with $DEITY
[21:38] <DBO> I had a dream last night that I met a flying computer mouse that could talk
[21:38] <DBO> that is my new god
[21:38] <mterry> DBO, damn.  That is reasonable
[21:40] <DBO> mterry, I am known for my rational mind and sound manner of dealing with all rangers of issues
[21:40] <DBO> rangers...
[21:41] <DBO> im way too tired these days
[21:41] <DBO> someone needs to invent a longer day so I can sleep
[21:41] <mterry> DBO, :)
[21:41] <micahg> DBO: xkcd.com/320/
[21:41] <mterry> good night all!
[21:42] <dupondje> sweet :) the Gnome updates
[21:42] <DBO> night mterry
[21:42] <RAOF> Morning DBO :)
[21:43] <DBO> morning RAOF
[21:44] <DBO> micahg, I prefer slowing down the earths rotation personally
[21:45] <DBO> however due to the devastating impacts of the moons gravity
[21:45] <DBO> the days are already getting longer
[21:46] <DBO> so all I really need is a time machine, that goes forward in time, faster than 1x
[21:46] <micahg> DBO: good luck with that :), http://xkcd.com/162/
[21:47] <DBO> micahg, so you're saying that my true object is to build the worlds largest flywheel
[21:47] <DBO> and get it really going
[21:47] <DBO> (and anchor it somewhere witch some decent rooting)
[21:48] <micahg> DBO: sounds like an interesting project for winter vacation
[21:48] <DBO> do we have to take winter vacation?
[21:50] <RAOF> Well, you're welcome to work, but it'll still be taken out of your vacation time :)
[21:50] <DBO> excellent
[22:18] <popey> cjwatson: ignore me, found the issue and how to fix it
[22:21] <jbicha> oh, nautilus isn't even in the desktop set
[22:24] <DBO> chrisccoulson, the issue should be resolved now
[22:25] <cjwatson> popey: hey, do you have that system still available for testing?  I have a test script that needs to be run
[22:26] <popey> cjwatson: I'm currently reinstalling 11.10 on it in 'bios mode', but am happy to do whatever you need
[22:26] <cjwatson> popey: I can forward you a mail; what address?
[22:26] <popey> alan@popey.com
[22:27] <cjwatson> sent
[22:30] <popey> cjwatson: ok, so that mail doesn't say I need to do an install of any kind, just fiddle in a live environment?
[22:31] <popey> the 'fix' I got from mjg59 was 'insert ubuntu cd, hold down alt, boot, at menu choose 'windows' instead of 'efi'.
[22:35] <cjwatson> popey: yes, this is purely live fiddling
[22:36] <cjwatson> popey: that's a fix too, but I'm trying to make things more robust
[22:36] <popey> ok
[22:36] <cjwatson> I mean, that's certainly the best fix for the moment, or you could use the amd64+mac CD
[22:37] <popey> will do the fiddling and let you know
[22:37] <cjwatson> but since I've had reports of bricking systems, I want to take the opportunity for debugging
[22:37] <cjwatson> ta
[22:37] <popey> sure
[22:39] <popey> cjwatson: the cd I have is from beta 1, which is dated 1/9/11, your mail is dated 31/8 and asked for the daily live cd to be used. does it matter?
[22:39] <cjwatson> it doesn't matter
[22:39] <popey> ok
[22:51] <popey> cjwatson: sadly it still says amd64/efi
[22:52] <popey> cjwatson: I am happy to install an ssh server on this box if you want remote access to it.
[23:01] <cjwatson> popey: that would be good, thanks
[23:02] <popey> cjwatson: ok, a live environment sufficient or prefer an install?
[23:05] <cjwatson> preferably live with that build tree available
[23:05] <popey> ok
[23:06] <popey> cjwatson: ok to use your ssh key from launchpad?
[23:09] <cjwatson> yep
[23:09] <cjwatson> I can do IPv6 if that's easier
[23:09] <popey> hehe, i haven't quite got to ipv6 yet :D
[23:09] <cjwatson> I always advertise it just in case; sometimes it saves somebody the effort of poking a hole in NAT
[23:10] <popey> gotcha
[23:14] <chrisccoulson> RAOF, there?
[23:15] <RAOF> Yo yo, ho!
[23:15] <chrisccoulson> hi RAOF
[23:15] <chrisccoulson> did you see bug 854101?
[23:15] <ubot2> Launchpad bug 854101 in ubuntu-boot-speed "gnome-settings-daemon takes waaaaaaaay too long to start" [Undecided,Confirmed] https://launchpad.net/bugs/854101
[23:15] <RAOF> I did indeed.
[23:15] <RAOF> What system are you running on?
[23:15] <chrisccoulson> RAOF, it seems that it's doing XRRGetScreenResources 3 times at startup ;)
[23:16] <chrisccoulson> RAOF, this is an intel system
[23:16] <RAOF> Hah!
[23:16] <RAOF> I suspect that it'd take much less time on a different GPU; there's a VGA probing problem on intel at the moment.
[23:17] <chrisccoulson> ah, ok
[23:17] <chrisccoulson> i think i can reduce it down to one call
[23:17]  * RAOF needs to chase down the mailing list to see if Keith's fixed that yet.
[23:17] <chrisccoulson> i don't see any reason why we couldn't share the same GnomeRRScreen across plugins in g-s-d....
[23:17] <RAOF> Is it actually making 3 X protocol calls?
[23:18] <chrisccoulson> RAOF, yeah. it creates a GnomeRRScreen in 3 different plugins, and that does XRRGetScreenResources each time it initializes
[23:18] <RAOF> Because unity-greeter starts gnome-settings-daemon, doesn't it?  And when I xtraced that I only got 1 (set of) RANDR protocol request(s).
[23:18] <chrisccoulson> RAOF, it doesn't start all of the plugins
[23:18] <broder> chrisccoulson: what plugins other than xrandr?
[23:18] <chrisccoulson> broder, xrandr, power, color
[23:19] <broder> eww, power needs randr? oh right - the brightness interface. blech
[23:19] <RAOF> Yeah; sharing the GnomeRRScreen sounds like a reasonable idea.
[23:19] <chrisccoulson> RAOF, yeah, i'll do that first thing in the morning
[23:19] <chrisccoulson> i don't see a reason why that wouldn't work
[23:19] <chrisccoulson> and that will save a full second on my nice, fast laptop
[23:20] <chrisccoulson> so it should be quite a win
[23:20] <RAOF> Alternatively, could the plugins be loaded in parallel?
[23:20] <broder> alternatively, could you add a boolean to GnomeRRScreen for whether or not to probe, and not probe for color and power?
[23:20] <broder> seems like they wouldn't care that much about up-to-date info
[23:21] <chrisccoulson> broder - well, that's an API change regardless of what we do. but adding that flag means the caller needs to make a decision on whether it thinks the information is up-to-date or not
[23:21] <RAOF> You'd need to add some global caching to gnome-desktop for that to work, right?
[23:21] <chrisccoulson> i think i'd rather do something like ubuntu_gnome_rr_screen_get_default() for now
[23:21] <chrisccoulson> or something like that ;)
[23:22] <broder> RAOF: the backend that gnome_rr_screen_new calls into already takes a boolean for whether or not to trigger a probe (i.e. RRGetScreenResources vs. RRGetScreenResourcesCurrent), it's just always true when coming from gnome_rr_screen_new
[23:23] <RAOF> Ah, funcy.
[23:23] <broder> (gnome_rr_screen_new -> gnome_rr_screen_initable_init -> screen_info_new, which takes a needs_reprobe boolean for which _initable_init always passes TRUE)
[23:25] <chrisccoulson> right, that makes sense though :)
[23:25] <chrisccoulson> in general, that's what you want when you initialize a new context
[23:25] <broder> chrisccoulson: i might care about getting the current state without triggering a probe, which might cause the state to change
[23:26] <broder> e.g. it's annoying sometimes that i can't run "xrandr -q" without it potentially changing what my current configuration is, due to g-s-d picking up the RRChange event
[23:28] <broder> and probing, at least on intel, has been expensive for a while now - at least going back to natty
[23:30] <broder> anyway, i think i've just convinced myself that this boolean flag makes sense, so i'll probably go and send a patch off to gnome-desktop upstream regardless of what you guys decide to do :)
[23:31] <chrisccoulson> broder - how does it make sense? which of the 3 plugins should set the flag true to do a reprobe?
[23:31] <broder> randr
[23:31] <chrisccoulson> and what happens if you disable that plugin?
[23:31] <chrisccoulson> will the other 2 trigger a reprobe?
[23:31] <chrisccoulson> or change the loading order?
[23:32] <broder> why should they? that's not their responsibility
[23:32] <broder> power and color should be reacting to whatever configuration is active, not actively going and seeking out new ones
[23:32] <chrisccoulson> well, then they initialize with information that is not up-to-date?
[23:32] <broder> no, the information is up to date according to the X server's view of the world
[23:32] <broder> it accurately reflects whatever the X server is doing at the point they're initialized
[23:33] <broder> and they listen for randr change events so their view stays up to date
[23:33] <chrisccoulson> so what is the point in the reprobe at all then?
[23:33] <broder> because the randr plugin's responsibility is trying to make sure that the outputs you've connected are active
[23:33] <broder> though when you put it that way, i'm not entirely sure
[23:34] <chrisccoulson> well, it can do that without a reprobe if what you say is true ;)
[23:34] <broder> right
[23:34] <broder> i mean, there's my idealized world, and then there's the real world where you don't always get notified for hotplug events
[23:35] <broder> but even in that case, if we assume that g-s-d is only really started at bootup, the X server's info should be up to date
[23:36] <RAOF> Well, the time between starting X and starting a user session is unbounded.
[23:36] <broder> chrisccoulson: it might make sense for none of the g-s-d plugins to do a probe, but for e.g. the monitors capplet to do one when it starts up