[00:10] <jasoncwarner_> hey chrisccoulson , achiang was wondering if we have a Firefox ESR PPA? I wasn't sure. Last I checked we didn't.
[00:12] <achiang> surely chrisccoulson isn't awake atm?
[01:31] <LLStarks> hi jbicha, did you ever get gnome-boxes working on precise? deb or git, it always segfaults.
[01:35] <jbicha> LLStarks: do you have hardware virtualization
[01:39] <jbicha> because yes, it does work with the Debian packaging on amd64 with hw virtualization, there's some rough edges but that's to be expected for the first release after a few months development
[02:28] <LLStarks> jbicha, i have vt-x
[02:28] <LLStarks> no vt-d
[02:29] <LLStarks> i can also do a bt if you want
[02:30] <LLStarks> seems to fail because of sparql
[02:44] <jbicha> LLStarks: sparql? do you have tracker-0.14 installed? & have you rebooted after installing all that?
[02:45] <jbicha> LLStarks: Boxes doesn't actually work for me on my usual computers, no hw-virt :(
[02:52] <jbicha> LLStarks: oh, and you'll need qemu-kvm-spice on Ubuntu
[02:53] <LLStarks> lemme check
[02:54] <LLStarks> i do have tracker installed
[02:55] <LLStarks> i'll brb with a reboot. if you want a trace, i'll paste it
[02:55] <LLStarks> not sure what symbols i need though
[03:05] <LLStarks> jbicha, http://pastebin.com/Qs5pHLEB
[03:24] <jbicha> LLStarks: perhaps tracker needs to be compiled with iso support
[03:24] <jbicha> like I said, the app doesn't really work for me
[03:25] <jbicha> and because it requires the libvirt from Debian experimental, it's not going to land in Precise
[04:59] <pitti> Good morning
[05:00] <TheMuso> Morning pitti.
[05:00] <TheMuso> pitti: re bug 966845 any suggestions?
[05:00] <ubot2> Launchpad bug 966845 in pyatspi "lucid->precise upgrade wants to remove ubuntu-desktop" [High,Triaged] https://launchpad.net/bugs/966845
[05:01] <pitti> TheMuso: there might be more subtle ways to fix this, but for now the only alternative I know of is to drop the Conflicts:, and have them both installed side by side
[05:01] <pitti> TheMuso: err, I mean
[05:01] <TheMuso> urm.... I don't think they can be installed side by side.
[05:01] <pitti> TheMuso: make the conflicts versioned
[05:02] <pitti> TheMuso: and have transitional at-spi and python-pyatspi packages which depend on their newer counterparts
[05:02] <pitti> TheMuso: when we drop the last "real" reverse depends on the old stack, they can become transitional
[05:04] <TheMuso> Ok, I'll file a removal request for gok.
[05:04]  * TheMuso meant to do that yesterday, but got sidetracked.
[05:04] <pitti> TheMuso: I'll do that immediately then
[05:05] <TheMuso> Ok.
[05:05] <pitti> TheMuso: then the transitional approach seems best to me
[05:05] <TheMuso> yes ok.
[05:09] <TheMuso> pitti: bug 972101
[05:09] <ubot2> Launchpad bug 972101 in gok "Please remove gok from precise." [Undecided,New] https://launchpad.net/bugs/972101
[05:15] <didrocks> good morning
[05:28] <pitti> bonjour didrocks
[05:29] <didrocks> guten morgen pitti :)
[05:30] <pitti> TheMuso: removed and blacklisted from syncing
[05:40] <TheMuso> pitti: So, if I am understanding your suggestion correctly, we also need to remove at-spi package.
[05:40] <pitti> TheMuso: less urgent, but eventually yes
[05:40] <pitti> TheMuso: at-spi2 should build a transitional at-spi package, and similar for pyatspi
[05:41] <TheMuso> But wouldn't that mean we have one binary package from 2 sources? I thought that wasn't possible...
[05:43] <BigWhale> Good Morning.
[05:44] <bkerensa> pitti: Do you know of any bug in 12.04 that would prevent a BT device from showing up in Sound Settings as a profile?
[05:44] <bkerensa> pitti: I tried getting this resolve and slangasek helped some but it ended up just having to be reported as a bug here: https://bugs.launchpad.net/bugs/972063
[05:44] <ubot2> Launchpad bug 972063 in pulseaudio "Bluetooth Headset pairs but does not show up in Sound Settings profile" [Undecided,New]
[05:45] <pitti> didrocks: so, HUD madness is finally gone for me, yay :)
[05:45] <pitti> TheMuso: we still need to remove the old sources afterwards, of cours
[05:45] <didrocks> pitti: *phew*, awesome! :)
[05:45] <pitti> TheMuso: but you can have two binaries from two sources, apt will just install the one with the higher version number
[05:45] <pitti> TheMuso: so we don't need to remove the old sources prior to uploading the new ones
[05:46] <pitti> bkerensa: not off-hand; cyphermox might know
[05:46] <pitti> bkerensa: I have about three BT devices here, and they all show up
[05:47] <bkerensa> pitti: ok yeah its really weird that its not showing up even though it pairs fine
[05:48] <TheMuso> pitti: ah ok.
[05:49] <bkerensa> cyphermox: if you get a chance can you perhaps have a look at that bug ^ and if you have any troubleshooting tips or debugging ideas can you share them? thx
[05:53] <jasoncwarner_> morning pitti and didrocks  :)
[05:57] <didrocks> hey jasoncwarner_, how are you? :)
[05:58] <pitti> hey jasoncwarner_
[05:59] <jasoncwarner_> didrocks, good, thanks, just getting 12.10 stuff ramping up!
[05:59] <didrocks> jasoncwarner_: living on really edge! ;)
[06:02] <jasoncwarner_> didrocks: what time is it for you? 7am or 6am? (daylight savings is messing me up again). Pitti, same? 7am?
[06:03] <didrocks> 8am now :)
[06:03] <pitti> jasoncwarner_: 8 AM
[06:04]  * jasoncwarner_ thinks the world should adopt a standard clock so I don't melt my brain twice a year ;)
[06:06] <smspilla1> didrocks: are you ok if we just distro patch seahorse to fix https://bugs.launchpad.net/seahorse/+bug/931958 ?
[06:06] <ubot2> Launchpad bug 931958 in unity-distro-priority "0.9.7: impossible to click on keyring dialog since the upgrade" [Medium,Fix committed]
[06:07] <smspilla1> I've looked into it for quite some time now and I just don't see a plausible way for compiz to work around this stupid behaviour
[06:07] <didrocks> smspilla1: well, seb128 knows more upstream than I, but they are friendly to us. I think it's doable if it's reasonable
[06:07] <smspilla1> okay, I'll see what I can do
[06:08] <didrocks> "he fact that is works on metacity is a fluke because seahorse is deciding not to take a grab in the particular focus path that metacity uses."
[06:08] <didrocks> smspilla1: you mean that seahose is detecting metacity?
[06:08] <smspilla1> no its just
[06:08] <smspilla1> I'm not really sure what its doing
[06:08] <smspilla1> but it seems to release its grabs somewhat
[06:08] <smspilla1> arbitrarily
[06:09] <smspilla1> the whole fact that its retaining a grab even when the window loses focus makes no sense IMO
[06:10] <smspilla1> could also be a server bug too ... this is hard to track down because I've tried setting breakpoints on XIDeviceGrab and XIDeviceUngrab and it didn't indicate that seahorse is explicitly taking or releasing any grabs here, even though a simple test application shows that something has a grab
[06:10] <smspilla1> maybe its an external process that is taking the grab ?
[06:10] <smspilla1> I'm not sure how well seahorse works ...
[06:10] <smspilla1> well, I'm not entirely sure how seahorse works in that regard, rather
[06:14] <smspilla1> didrocks: ah I see what its doing
[06:14] <smspilla1> it ungrabs the device, pops up a new window
[06:14] <smspilla1> and then if the focus moves away from that window it grabs the device again
[06:15] <smspilla1> but if you give focus to the dialog, it won't release that grab again
[06:15] <smspilla1> at least as far as I can tell
[06:15] <smspilla1> so I think what is happening is that
[06:15] <smspilla1> it ungrabs the device
[06:15] <smspilla1> compiz change sthe focus to something else and then to that window
[06:16] <smspilla1> and then seahorse gets confused
[06:16] <smspilla1> although considering that other wms are also doing this, I think their heurestic is probably broken, and we should just make it ungrab whenever the dialog gets the focus
[06:16] <smspilla1> didrocks: wdyt ?
[06:16] <smspilla1> (its a separate pid too, clever)
[06:17] <didrocks> smspilla1: I have no strong opinion, I would first want upstream to comment on why they are doing it this way
[06:17] <didrocks> smspilla1: maybe it's related to some security concerns
[06:17] <didrocks> smspilla1: so let's wait seb, he knows upstream very well for seahorse
[06:17] <didrocks> smspilla1: thanks for looking into it :)
[06:17] <smspilla1> well like
[06:18] <smspilla1> it would seem to me that it would make sense to release the grab
[06:18] <smspilla1> after the dialog gets focus again
[06:18] <smspilla1> since I'm now pretty sure that
[06:18] <smspilla1> if you open seahorse, pop up the keyring input, cause the modal dialog to open
[06:18] <smspilla1> and then switch focus to something else
[06:18] <smspilla1> and then BACK to seahorse
[06:18] <smspilla1> will break
[06:18] <smspilla1> (or at least, it does on g-s
[06:18] <smspilla1> lets try metacity ...
[06:19] <smspilla1> oh huh
[06:20] <smspilla1> interesting it doesn't re-grab if you move focus away with metacity
[06:20] <didrocks> interesting :)
[06:36] <jasoncwarner_> hey smspilla1 given we are so close to final freeze, we kind of need a fix for this. Maybe not ideal, but something. What would be possible to make it work even if the app is "being stupid"
[06:36] <jasoncwarner_> ?
[06:37] <smspilla1> jasoncwarner_: I am looking into that now
[06:37] <smspilla1> jasoncwarner_: you can't forcibly release grabs, so we need to patch the application
[06:37] <jasoncwarner_> smspilla1: ok...and I assume you are looking at how to patch the application (when you say you are "looking into it")?  :)
[06:38] <smspilla1> yes
[06:38] <jasoncwarner_> smspillaz: sweet!, thanks dude !
[06:38] <smspillaz> np
[06:38] <jasoncwarner_> PERTH FTW!
[06:38] <smspillaz> not really
[06:38] <smspillaz> perth is a pretty miserable city
[06:38] <smspillaz> better than adelaide though
[06:39] <jasoncwarner_> whatever, everyone I know from perth is like "perth is awesome" and "adelaide is stupid" and "math is hard, let's go shopping".
[06:39] <smspillaz> hmm
[06:39] <smspillaz> there are three parts to that statement which are true
[06:40] <jasoncwarner_> wait a minute ;)
[07:05] <BigWhale> The last post on ubuntu-devel-discuss is funny.. The funniest part? I pressed Super-R and I can't unzoom. ;>
[07:09] <pitti> BigWhale: hm, I think there was a trick with Super+Scrollwheel or so
[07:09] <pitti> but indeed that doesn't work now
[07:10] <pitti> a second super+r works, though
[07:10] <pitti> not very reliably so, though
[07:18] <smspillaz> didrocks: ok, I can see whats going on now
[07:18] <smspillaz> (which explains why it is broken under g-s too)
[07:18] <didrocks> BigWhale: pitti: I removed Super-R anyway in the incoming upload :)
[07:18] <BigWhale> pitti, I disabled the Enhanced zoom plugin in CCSM ...
[07:19] <BigWhale> (I often use 16 ton hammers to kill mosquitoes ...)
[07:19] <pitti> didrocks: aka the "trap" key? :-)
[07:19] <smspillaz> it checks when the window state changes and regrabs the keyboard based on that. And because we added _NET_WM_STATE_FOCUSED it will re-grab the keyboard when NET_WM_STATE_FOCUSED is added to _NET_WM_STATE and the window is not Withdrawn, Iconified or _NET_WM_STATE_FULLSCREEN or _NET_WM_STATE_MAXIMIZED
[07:19] <pitti> didrocks: oh, new compiz coming today?
[07:19] <didrocks> pitti: indeed :-) was removed as a distro patch in the past, but well, as all our patches were removed by upstream when they bundled it…
[07:19] <smspillaz> so I think I just need to patch it to store when it was maximized or withdrawn / iconified / whatever
[07:19] <didrocks> pitti: yeah, the one from the ppa
[07:20] <pitti> didrocks: nice
[07:20] <didrocks> pitti: + the keybinding changes
[07:20] <pitti> that's running nicely here
[07:20] <didrocks> smspillaz: ok ;)
[07:20] <pitti> didrocks: ah, I lost track of all the FFEs; I'll just let myself surprise which keys break this time :)
[07:21] <didrocks> heh ;)
[07:36] <smspillaz> didrocks: fixed
[07:36] <smspillaz> didrocks: do you want me to just submit the patch upstream ?
[07:36] <didrocks> smspillaz: nice! yes please ;)
[07:36] <smspillaz> and give your the b.g.o link ?
[07:37] <didrocks> right ;)
[07:37] <didrocks> smspillaz: I guess we'll chceck with him before pushing that to the distro :)
[07:37] <smspillaz> yeah the patch is a bit ugly but I can't think of a "proper" way to do it that doesn't involve subclassing GtkWindow really
[07:38] <didrocks> let's see with upstream ;)
[07:41] <seb128> hey
[07:42] <smspillaz> hey seb128
[07:42] <smspillaz> seb128: I've fixed the gnome-keyring issue you had
[07:42] <smspillaz> seb128: its a bug in gnome-keyring, so I am making a distro patch as the relevant code no longer exists upstream
[07:42] <seb128> smspillaz, hey, you rock, thanks a lot for taking some time to look at it
[07:42] <smspillaz> anything to avoid white windows
[07:42] <smspillaz> I mean
[07:42] <smspillaz> what ?
[07:42] <seb128> smspillaz, ok, just give me the diff and I will handle the packaging
[07:42] <smspillaz> okay
[07:43] <smspillaz> seb128: I can make an mp into it, its cool
[07:43] <seb128> smspillaz, your call, I'm happy to take it from there but I'm happy to review a merge request as well
[07:48] <didrocks> salut seb128 ;)
[07:49] <pitti> bonjour seb128
[07:49] <seb128> hey didrocks, pitti
[07:49] <seb128> how are you?
[07:49] <didrocks> I'm fine, thanks. Yourself?
[07:50] <seb128> I'm good thanks
[07:50] <seb128> robert_ancell, hey!
[07:50] <pitti> seb128: for bug 969569, I agree with chrisccoulson that we should not migrate theme settings from gconf; themes completely changed, we don't have clearlooks etc. any more. WDYT?
[07:50] <ubot2> Launchpad bug 969569 in gsettings-desktop-schemas "lucid to precise: Ugly desktop after upgrade" [Critical,Triaged] https://launchpad.net/bugs/969569
[07:50] <robert_ancell> hello
[07:50] <smspillaz> seb128: https://code.launchpad.net/~smspillaz/gnome-keyring/gnome-keyring.fix_931958/+merge/100563
[07:50] <pitti> hey robert_ancell, howdy?
[07:50] <seb128> robert_ancell, how are you? if the european start talking it's time to call it a day? ;-)
[07:50] <robert_ancell> I reckon!
[07:50] <seb128> robert_ancell, do you have a minute to talk lightdm, bugs, release and precise? ;-)
[07:50] <seb128> smspillaz, thanks, on it
[07:51] <robert_ancell> I had to head out this afternoon so staying a little later.
[07:51] <robert_ancell> yes
[07:51] <seb128> robert_ancell, what bugs do you have still on your list for precise?
[07:52] <seb128> robert_ancell, I've those on my list
[07:52] <seb128> bug #951597
[07:52] <ubot2> Launchpad bug 951597 in lightdm "1.1.7 : breaks xsession-errors, no more rotated" [High,Triaged] https://launchpad.net/bugs/951597
[07:52] <seb128> bug #952185
[07:52] <ubot2> Launchpad bug 952185 in lightdm "~/.pam_environment not parsed when HOME is encrypted" [High,Triaged] https://launchpad.net/bugs/952185
[07:52] <seb128> bug #956848
[07:52] <ubot2> Launchpad bug 956848 in lightdm "pam_mkhomedir.so fails to create homedir in precise" [High,In progress] https://launchpad.net/bugs/956848
[07:52] <seb128>  
[07:52] <robert_ancell> seb128, bug 956848 and bug 951597 but I also need to have a look at bug 952185
[07:52] <seb128> robert_ancell, does that seems right?
[07:52] <seb128> ok, good
[07:52] <seb128> we are in sync it seems ;-)
[07:53] <seb128> robert_ancell, did you make any progress on the .xsession-errors rotation one? it's impacting on debugging of other bugs so I'm eager to see it resolved ... anything I can do to help?
[07:53] <robert_ancell> seb128, provide a patch ;)
[07:53] <robert_ancell> seb128, no, still working on it
[07:53] <seb128> robert_ancell, lol, rrrrright ;-)
[07:54] <pitti> robert_ancell: bug 878184  as well? that looks like it's got a branch ready for merging?
[07:54] <ubot2> Launchpad bug 878184 in unity-greeter "Onscreen Keyboard cannot be used to input password in unity-greeter" [High,In progress] https://launchpad.net/bugs/878184
[07:54] <Saviq> hey guys, what do you think might be responsible for reintroducing bug 878492 ?
[07:54] <ubot2> Launchpad bug 878492 in unity-2d "Keyboard shortcut - F10 shortcut is used to show menu and this is wrong" [High,Confirmed] https://launchpad.net/bugs/878492
[07:54]  * smspillaz starts sending email to himself
[07:55] <seb128> pitti, that's commit to unity-greeter trunk for some weeks
[07:55] <seb128> commited
[07:55] <pitti> ah, good
[07:55] <Saviq> we can confirm gtk apps are affected (but also in gnome-shell, so...)
[07:55] <robert_ancell> pitti, as seb said
[07:55] <seb128> Saviq, try asking on #ubuntu-unity
[07:56] <seb128> robert_ancell, pitti: speaking of unity-greeter I was waiting on an extra fix to land and I wanted to ping mterry about doing a release for it
[07:56] <robert_ancell> seb128, have you happened to hear from mterry about the much duplicated u-g crash?
[07:56] <seb128> robert_ancell, which one? speaking of segfault, bug #902698 still gets duplicates
[07:56] <ubot2> Launchpad bug 902698 in lightdm "lightdm crashed with SIGSEGV in check_stopped()" [High,Triaged] https://launchpad.net/bugs/902698
[07:56] <robert_ancell> bug #946674
[07:56] <ubot2> Launchpad bug 946674 in unity-greeter "unity-greeter crashed with SIGSEGV in background_loader_ready_cb()" [Medium,Confirmed] https://launchpad.net/bugs/946674
[07:57] <robert_ancell> I'll assign it to him
[07:57] <robert_ancell> I saw an indication it might have been due to the glib upgrade
[07:57] <seb128> robert_ancell, I didn't have it on my list but I will check with him today
[07:57] <robert_ancell> have been uncovered that is
[07:59] <robert_ancell> seb128, btw, do you have any opinion on the libgnomekbd/accountsservice we are running?  I had a look at merges for them but they were non-trivial.  Don't know if we're missing out on any important bug fixes though
[07:59] <seb128> robert_ancell, they are good, I think we can sync libgnomekbd from Debian, I meant to ask pitti about that since he's the one who worked on that package the most recently
[08:00] <seb128> robert_ancell, accountsservice, upstream went crazy, we should stay on our version
[08:00] <robert_ancell> oh and libpeas was the same
[08:00] <seb128> we can probably just get the new version of this one
[08:00] <robert_ancell> it has quite some changes, and some important apps depend on it so I wasn't sure
[08:00] <seb128> well if we have no issue with the current version we can as well being conservative
[08:00] <seb128> robert_ancell, btw thanks for breaking shotwell yesterday :p
[08:00] <robert_ancell> seb128, also, I looked at aisleriot - it seems to build fine in precise, not sure why we never took it
[08:01] <robert_ancell> seb128, say what?
[08:01] <robert_ancell> seb128, well that's ok then - you broke webkit :)
[08:01] <seb128> robert_ancell, gexiv 0.4.1 changed soname, you overlooked it seems, you didn't rename the binary and shotwell was bailing out on a missing lib
[08:01] <robert_ancell> ech
[08:01] <seb128> like ld missing
[08:01] <seb128> robert_ancell, well at least mine didn't break users :p
[08:02] <seb128> robert_ancell, but thanks for catching that ;-)
[08:02] <robert_ancell> seb128, whoops.  We really need to automate that better...
[08:02] <seb128> robert_ancell, aisleriot -> jbicha has been looking at it
[08:02] <seb128> I will check with him
[08:02] <seb128> robert_ancell, well lintian warns you, we need to print lintian warnings in red ;-)
[08:03] <seb128> robert_ancell, pitti: ok, btw something that might make you happy, mpt suggested we should drop lpi
[08:03] <seb128> discussion for UDS
[08:03] <robert_ancell> seb128, it would save us a lot of time
[08:03] <robert_ancell> seb128, do we have any metrics on how useful it is?
[08:03] <seb128> robert_ancell, right, and it's limited to some apps and a bit geeky
[08:04] <seb128> robert_ancell, mpt seems to think it's a geek stuff, the answer tracker got superseeded by askubuntu, we hid the bug stuff in release and access to translations are not stuff normal users are interested in finding in their apps
[08:05] <seb128> robert_ancell, not sure we have any metrics, that's why I still want a discussion at UDS
[08:05] <seb128> but yeah, I doubt it's very useful for users
[08:05] <robert_ancell> seb128, I'd be happy to just notify the list, drop it and then see what happens
[08:06] <robert_ancell> we can put the patches back quickly if there is a problem
[08:07] <seb128> robert_ancell, right, I might just mention put a "review delta with upstream and Debian" session for UDS to go through stuff like lpi and control center crazyness and see what we do
[08:07] <robert_ancell> yeah
[08:07] <robert_ancell> it's not worth a whole session
[08:07] <seb128> well, one hour to cover the different topics and maybe worflow etc
[08:07] <seb128> desktop status update or something
[08:07] <seb128> or checkpoint
[08:08] <robert_ancell> seb128, I'd like to tackle UDD again - we need to get to one method of updating packages
[08:08] <seb128> right, I've the feeling it's not getting any better
[08:08] <seb128> not sure how much UDD is being worked on
[08:09] <seb128> like the gvfs import is always outdated and broken and doing those updates a pain still
[08:09] <robert_ancell> seb128, yeah, if we go full UDD it has to be foolproof
[08:09] <robert_ancell> seb128, the packaging branches work really well, but they have permission issues and issues with people uploading without updating
[08:10] <robert_ancell> the full branches have the easily broken issue as you point out
[08:10] <robert_ancell> no branches is a huge waste of time
[08:10] <pitti> seb128: ooh
[08:10] <pitti> seb128: I'll look at libgnomekbd (remaining delta/sync)
[08:10] <seb128> pitti, thanks
[08:11] <pitti> seb128: sorry, was stuck in mutt for a bit
[08:11] <seb128> robert_ancell, my gut feeling is that debian only dirs are still the less painfull for what we do
[08:11] <robert_ancell> jasoncwarner_, ^ perhaps this is something you can negotiate with the LP people.  Packaging is a big timesink for us, and if they can get UDD in an awesome state we would save a lot of time (=$)
[08:11] <seb128> but yeah
[08:11] <seb128> jasoncwarner_, ^ that would be great ;-)
[08:12] <pitti> I have an idea
[08:12] <pitti> how about we invent a command that directly fetches the source from the archive?
[08:12] <pitti> that will _always_ give us the correct version!
[08:12]  * pitti ducks
[08:13] <robert_ancell> pitti, the problem is not getting the correct version - the problem is how to update it in an easy manner that provides good visibility of the changes and a better way of annotating what has changed
[08:13] <pitti> robert_ancell: yes, I know
[08:14] <pitti> robert_ancell: from my POV, people keep screwing up the pre-applied patches
[08:14] <pitti> including me
[08:14] <pitti> this is the single biggest itch I have with those
[08:14] <pitti> I already set
[08:14] <pitti> quilt-commit-policy = applied
[08:14] <pitti> quilt-tree-policy = unapplied
[08:14] <pitti> but that doesn't help
[08:15] <pitti> my other itch is that UDD fixes the exactly wrong problem
[08:15] <pitti> we don't need the upstream bits in bzr, we need our changes in bzr
[08:15] <seb128> then you get the branches that always get outdated for some reason
[08:15] <pitti> but our changes are precisely the ones which are not covered by real revision control, but are stuck in quilt patches
[08:15] <seb128> i.e gvfs currently
[08:16] <pitti> that too, but that only affects some packages
[08:16] <pitti> a lot got broken with the .xz switch, I think
[08:16] <seb128> I'm probably not lucky, I've that every second time I try to deal with a GNOME update in UDD
[08:16] <seb128> could be
[08:16] <pitti> I had used UDD for gvfs until it broke
[08:16] <pitti> since then, classic apt-get soruce and uupdate..
[08:17] <seb128> yeah
[08:18] <pitti> yep, libgnomekbd is syncable, doing
[08:18] <robert_ancell> ok, later guys
[08:18] <pitti> robert_ancell: good night!
[08:19] <pitti> seb128: for bug 969569, I agree with chrisccoulson that we should not migrate theme settings from gconf; themes completely changed, we don't have clearlooks etc. any more. WDYT?
[08:19] <ubot2> Launchpad bug 969569 in gsettings-desktop-schemas "lucid to precise: Ugly desktop after upgrade" [Critical,Triaged] https://launchpad.net/bugs/969569
[08:19] <seb128> pitti, oh sorry forgot to reply to that while catching up with robert ;-)
[08:19] <pitti> seb128: that's fine; I figured you'd rather use the time to talk to Robert
[08:19] <pitti> I can annoy you all day :)
[08:19] <seb128> pitti, I'm fine not migrating the theme, wasn't that distro patch we added? I think upstream doesn't migrate theme, not even the background image
[08:20] <seb128> but +1 from we for the reasons you listed
[08:20] <seb128> we->me
[08:21] <pitti> seb128: ok, so we all agree; I'll have a look at this then
[08:21] <pitti> seb128: migrating bg image is still fine IMHO
[08:21] <seb128> pitti, the main reason I wanted the migration is that users running the light theme would still get it after upgrade
[08:22] <pitti> seb128: yeah, I know, but I don't  think we can do a conditional migration that way :/
[08:22] <seb128> pitti, http://launchpadlibrarian.net/80328425/gsettings-desktop-schemas_3.1.91-0ubuntu1_3.1.92-0ubuntu1.diff.gz
[08:22] <pitti> we could add some additional code
[08:22] <didrocks> yeah, too late for conditional migration :/
[08:22] <seb128> pitti, just drop dont_reset_themes.patch
[08:22] <seb128> pitti, not sure if we want to keep the colors and fonts though
[08:23] <pitti> I'll be conservative and only drop themes
[08:23] <pitti> fonts are fine
[08:23] <seb128> ok
[08:23] <pitti> colors also didn't disappear
[08:23] <pitti> seb128: I'll merge with Debian while I'm at it
[08:23] <seb128> pitti, thanks
[08:24] <seb128> pitti, btw you reintroduce the glib patch for non multiarch gio dir compat when you merged, was that wanted?
[08:24] <pitti> seb128: it seemed harmless, and not a bad idea for third-party apps, and reduced the delta
[08:24] <pitti> seb128: do you see a reason to not have it?
[08:24] <pitti> does it cause error messages or something/
[08:25] <pitti> ?
[08:25] <seb128> pitti, it breaks multiarch, image you have an amd64 install and a leftover x86 binary in the non multiarch dir
[08:25] <seb128> pitti, also it creates confusing leading people to think they can,should use that dir
[08:25] <seb128> pitti, no big deal but desrt pushed for having it dropped before the lts
[08:26] <pitti> how would you have a i386 binary in the non-multiarch path of an amd64 system?
[08:26] <pitti> seb128: ok, I'm fine with dropping it again; I did not have a strong reason for keeping it
[08:26] <seb128> pitti, because you pull in an i386 binary still installing a .so there?
[08:26] <seb128> pitti, but yeah maybe in practice that doesn't happen
[08:26] <seb128> it's just that it's a bit less "clean" and it might lead to confusion to still have that dir listed
[08:27] <pitti> seb128: ah -- if we have such packages still, then the amd64 package would not work any more if we drop it
[08:27] <pitti> ("not a bad idea for third-party apps")
[08:27] <seb128> pitti, no need of an upload for that, I just wanted to check before dropping it, I will drop it again in the next upload then
[08:27] <pitti> seb128: ok; I have no objections to dropping it again
[08:27] <seb128> pitti, we have nothing in the archive still using the compat dir no
[08:27] <seb128> so it's all theoritically and third party discussion ;-)
[08:27] <seb128> pitti, thanks
[08:28] <seb128> (I would argue that Debian should drop it as well btw)
[08:33] <pitti> zgrep usr/lib/gio /tmp/Contents-i386.gz
[08:33] <pitti> seb128: indeed, Debian doesn't have the old paths any more either; I'll commit that
[08:33] <seb128> pitti, thanks
[08:33] <pitti> so we are still at "no ubuntu diff after LTS" :)
[08:33] <seb128> ;-)
[08:35] <pitti> seb128: done
[08:35] <seb128> pitti, danke
[08:37] <seb128> does anyone know if there is a "reverse that diff" utility?
[08:39] <chrisccoulson> good morning everyone
[08:40] <didrocks> seb128: I looked for such one the other day, didn't really find after 5 minutes of looking around
[08:40] <didrocks> chrisccoulson: hey, how are you?
[08:40] <seb128> hey chrisccoulson, how are you?
[08:40] <seb128> didrocks, ok, me neither
[08:41] <chrisccoulson> hi seb128, didrocks. i'm good thanks, how are you?
[08:41] <Laney> interdiff can do it
[08:41] <seb128> chrisccoulson, I'm good thanks
[08:41] <didrocks> chrisccoulson: I'm fine, thanks :)
[08:41] <seb128> Laney, "       To reverse a patch, use /dev/null for diff2."
[08:41] <seb128> oh, nice
[08:41] <Laney> seb128: interdiff foo.
[08:41] <Laney> yes
[08:41] <seb128> Laney, thanks!
[08:41] <Laney> :P
[09:33] <pitti> seb128: so, I guess we can just as well keep the patch
[09:33] <pitti> as it behaves well if the .so is of the wrong arch
[09:33] <pitti> but not very important either way then
[09:34] <seb128> pitti, right, I might still drop it from precise let's see, I read the discussion on #debian-gnome
[09:34] <seb128> it just feels wrong keeping compat for an old dir we don't use which can create confusion
[09:35] <seb128> I would prefer the lts to clearly have one clear dir to use and message it correctly
[09:35] <seb128> though it's a detail at the end
[09:39] <rickspencer3> I think it's taking me longer to port photobomb to using gir than it took me to write it in the first place :/
[09:45] <pitti> nobody reminded me about the meeting reminder!
[09:45] <didrocks> oh!
[09:45] <rickspencer3> pitti, remember the meeting reminder!
[09:45] <didrocks> pitti: I do not see anything obviously wrong on bug #970939, seems pygi or python though?
[09:45] <rickspencer3> and don't do anything like script a cron job, or put an alert in a calendar!

[09:46]  * rickspencer3 is desperate for a break from gi.repository tedium
[09:46] <pitti> rickspencer3: nah, that'd take all the fun out of it
[09:46] <pitti> didrocks: will look in a sec
[09:47] <pitti> hmm, after reading last week's gtimelog I did nothing but bug fixing
[09:47] <pitti> seems for the first time in years I have nothing interesting to put on the weekly report..
[09:48] <seb128> pitti, doh, meeting reminder!
[09:48] <didrocks> pitti: don't read the meeting reminer btw, you will get spoiled with the new key changes :)
[09:49] <didrocks> (once I would write it)
[09:49] <pitti> didrocks: you mean the new report?
[09:49] <didrocks> yeah, the incoming report :)
[09:53] <pitti> didrocks: yeah, not a very useful stack trace; that needs a reproducer
[09:54] <didrocks> pitti: ok, affecting python-gobject + incomplete?
[09:54] <pitti> I can't tell from the trace
[09:54] <pitti> could be a wrong annotation in a library
[09:54] <pitti> that's the most likely reason
[09:55] <didrocks> just putting it as incomplete for now then, sticking in oneconf if you want even if that's not the real component
[09:56] <pitti> didrocks: if you want it off the bug list, just reassign it to pygobjject
[09:56] <pitti> I'll gladly ignore it there, especially if it's "incomplete"
[09:57] <didrocks> pitti: no, I don't really care about incomplete, I open them sometimes to see if the reporter didn't sent anything useful and I missed the mail
[10:18] <Sweetsha1k> pitti: I uploaded a testbuild for bug 969707 btw ...
[10:18] <ubot2> Launchpad bug 969707 in libreoffice "package python-uno 1:3.4.4-0ubuntu1 failed to install/upgrade: sub-processo novo script pre-installation retornou estado de saída de erro 1" [Critical,Fix committed] https://launchpad.net/bugs/969707
[10:22] <pitti> Sweetsha1k: nice, to a PPA?
[10:25] <Sweetsha1k> pitti: jup, for dist-upgrade testing https://launchpad.net/~bjoern-michaelsen/+archive/libreoffice-precisetest-20120327
[10:26] <Sweetsha1k> pitti: lets just hope the build doesnt break again because the ppa buildds have to few disc space.
[10:42] <pitti> Sweetsha1k: for testing it's ceratinly enough to have it build on i386 OR amd64?
[10:58] <chrisccoulson> does anyone else see bug 971800?
[10:58] <ubot2> Launchpad bug 971800 in firefox "Firefox crashes while trying to delete a bookmark" [Undecided,Incomplete] https://launchpad.net/bugs/971800
[10:58] <chrisccoulson> i can't reproduce it, but i fixed a crash yesterday and want to figure out if i fixed that one before i do another upload
[11:04] <pitti> chrisccoulson: just deleting any book mark?
[11:11] <seb128> chrisccoulson, no issue there but I don't have lot of bookmarks
[11:14] <pitti> chrisccoulson: I can delete a bookmark just fine here
[11:17] <chrisccoulson> seb128, pitti, thanks
[11:17] <BigWhale> Are there any conventions I should follow for running applications from their local directories? For example you download foo-12.2.tar.gz, extract it and then what?
[11:17] <chrisccoulson> i'll just assume that he's seeing a crash that i've already fixed then
[11:37] <Riddell> nessita: there's a new Qt in precise, are you able to test the ubuntuone bits with it?
[11:38] <Riddell> and if you want to be ahead of the curve I see Forum Nokia are putting Qt 5 packages into their PPA :)
[11:38] <nessita> Riddell: hi there. Will let our QA team know, thanks for heads up!
[11:41] <dpm> hi pitti, can we re-enable the Precise langpacks now that the beta is out? (I can do it myself, just want to double-check it's ok)
[11:42] <pitti> dpm: ah, sure
[11:42] <pitti> dpm: thanks
[11:43] <Riddell> dpm: enable in which way?
[11:44] <dpm> Riddell, we usually disable automatic language pack uploads during freezes, and re-enable them when they're over
[11:44] <dpm> pitti, cool, done then
[11:50] <Riddell> oh aye
[12:17] <desrt> mumble mumble
[12:17] <cyphermox> seb128: I found out why evolution-dev had a dep on evolution ;)
[12:18] <seb128> desrt, hey, no, google hangout! ;-)
[12:18] <seb128> cyphermox, that's what was preventing those ftbfses? ;-)
[12:18] <desrt> :)
[12:18] <cyphermox> yeah
[12:18] <didrocks> hey hey desrt ;)
[12:18] <seb128> desrt, how are you? get some coffee before mumbling
[12:18] <desrt> seb128: you assigned me a bug that i already fixed last night :p
[12:18] <didrocks> desrt: when you get a chance, I still have one request/question on the alt thingy :)
[12:18] <cyphermox> but I think it would be more correct if it was Depends: libevolution (= $binary:Version) rather than evo
[12:19] <didrocks> so go get your coffee first! ;)
[12:19] <seb128> cyphermox, hum, why is evo needed? are those libs which are missing in the evo binary or is something ld loading the evo lib?
[12:20] <cyphermox> evolution-dev ships the pc files for -leutil and others, which are libraries provided by libevolution
[12:20] <cyphermox> I think it was still at Depends: evolution because the libraries were split out to libevolution but the dep forgotten or something
[12:21] <seb128> cyphermox, hum, so yeah, it seems "Depends: libevolution (= $binary:Version)" is about right
[12:21] <cyphermox> (I mean, in Debian, of course)
[12:27] <bcurtiswx> good morning
[12:40] <htorque> desrt: are there some other small leaks you already fixed that i can report? :P
[12:40] <desrt> yes
[12:41] <desrt> but only ones that happen on exit
[12:41] <desrt> ...which is never
[12:41] <htorque> at least i get some karma points for the report ;-)
[12:47] <jbicha> heh, now I know why my tracker 0.14 evolution miner build's been failing :|
[12:49] <didrocks> desrt: not sure if you saw my ping or if you want for your coffee to brew or mumbling like a mad :p
[12:50] <desrt> i saw your comment
[12:50] <desrt> but i was too lazy to get up and make coffee
[12:50] <desrt> you can tell me now if you want :)
[12:50] <didrocks> ah, dependency issue :)
[12:50] <didrocks> I see ;)
[12:51] <didrocks> so, basically, I think that's linked to your comment you did yesterday about Left and Right Alt
[12:51] <didrocks> basically, if I assign Ctrl + (left) Alt + t to open a terminal
[12:51] <didrocks> the keys are:
t
[12:51] <didrocks> and it indeed, only work with left key
[12:51] <didrocks> however, tapping left alt, will show Alt_l
[12:52] <didrocks> and the same, if we read <Alt> and pass that to the renderer, it will gladly ignore
[12:52] <didrocks> I tried to look at the "Primay" hack that was done in g-c-c (http://git.gnome.org/browse/gnome-control-center/commit/?id=7f5733b454e26c882d4e707b57cd03b104f57dd2)
[12:52] <desrt> so you have a couple of wires crossed
[12:52] <desrt> there are two things going on -- modifiers and keyvals
[12:52] <didrocks> but this moved to gtk/gtkaccelgroup.c in gtk
[12:52] <didrocks> yeah
[12:52] <desrt> 'control' and 'alt' are the name of modifiers
[12:52] <desrt> 'alt l' is the name of a key
[12:53] <didrocks> and the gtk_accelerator_parse_with_keycode only check for modifiers
[12:53] <desrt> well, the X server sets the modifiers according to the history of keypresses
[12:53] <desrt> it knows that pressing altl activates the modifier called 'alt' for example
[12:53] <desrt> (or mod1 i guess it calls it)
[12:53] <didrocks> right, it's mod1
[12:56] <didrocks> desrt: so, the funny story is that if you start to assign Alt_L to the key, it won't detect the keypress anymore
[12:56] <didrocks> it == compiz
[12:56] <desrt> so that's why i was concerned about this patch
[12:56] <desrt> it seems like the process of grabbing alt is pretty... intense
[12:57] <desrt> i mean, from what i've heard of what goes on inside compiz
[12:57] <didrocks> don't tell me, I heard enough about it ;)
[12:57] <desrt> i'm not totally sure this is something that can be easily changed
[12:58] <pitti> seb128: the variety of launchpadlib exceptions in the retracer keeps amazing me :/
[12:58]  * pitti restarts
[12:58] <didrocks> It's interesting though, <Alt_L> will treat it again as a modifier by compiz
[12:58] <didrocks> and seems to work
[12:58] <seb128> pitti, which one did you get today?
[12:59] <didrocks> desrt: apart from a hack to change that on the fly in the g-c-c side, I don't see a better solution right now
[13:00] <pitti> seb128: some httplib error again, unexpected size read
[13:00] <pitti> bbiab
[13:01] <desrt> didrocks: so i'm confused.  you'd rather it report <alt> than <alt l>?
[13:01] <didrocks> desrt: no, I mean, it's reported as Alt_L
[13:01] <didrocks> desrt: <Alt_L> would work
[13:02] <desrt> how is this not a problem with other keystrokes?
[13:02] <didrocks> as it's a keypress and not a modifier, I guess that's why I doesn't get <…>
 is not a modifier mask, though...
[13:02] <desrt> unless compiz has some magic
[13:02] <didrocks> desrt: it seems to have
[13:02] <desrt> so anyway
[13:03] <desrt> one thought i had when doing the patch was to report the modifier mask with a zero keyval instead of reporting the keyval with the modifier mask
[13:03] <desrt> let me test what would happen in this case
[13:03] <didrocks> desrt: ah, that could work, not sure, but it could yeah (maybe won't show "unactivated")
[13:03] <didrocks> in the cell renderer
[13:04] <desrt> disabled, frenchie :p
[13:04] <seb128> jbicha, hey
[13:04] <didrocks> desrt: I'll go doing some sport if you continue :p
[13:04] <desrt> i love it when you and seb do some sport :)
[13:06] <desrt> interesting
[13:06] <desrt> keycode 0 gets reported with the label "0x40"
[13:06] <didrocks> funny value ;)
[13:15] <jbicha> uh, oops
[13:16] <seb128> jbicha, hey
[13:16] <seb128> jbicha, that tracker was not for precise right? ;-)
[13:16] <jbicha> well I was going to request a FFe for tracker 0.14
[13:17] <seb128> yeah, I was wondering for a while why you didn't do that earlier ;-)
[13:17] <seb128> jbicha, I reverted your 2 g-s-d commit btw
[13:17] <seb128> jbicha, we don't want to build the pkgkit plugin in g-s-d
[13:18] <jbicha> seb128: I hadn't requested tracker 0.14 earlier because I couldn't get the evolution miner to build
[13:18] <seb128> jbicha, and the mnemonic changes, that would be changing the strings and resetting translations again, and mpt said mnemonic should be used in menus, he will update the designs next time he work on those
[13:19] <jbicha> seb128: does building pkgkit break anything? without it, gpk-prefs won't start (not that gpk is supported in Ubuntu any way...)
[13:20] <seb128> jbicha, I discussed the gpk-prefs issue with upstream he did recon it was a bug on his side and he would fix it
[13:20] <jbicha> oh ok, thanks for reviewing those changes then
[13:20] <seb128> jbicha, well enabling the option would add a pkgkit plugin loaded a setting start, slowing down loading, adding uis, and duplicating update-notifier features
[13:20] <seb128> setting start->session start
[13:21] <seb128> jbicha, like that code would display bubble about update available and other stuff
[13:21] <jbicha> I haven't seen bubbles here, but it would at least add more dconf strings so that's probably bad at this point
[13:23] <seb128> jbicha, well for sure it does an "apt-get update" for you every hour in the background
[13:23] <seb128> jbicha, i.e see http://git.gnome.org/browse/gnome-settings-daemon/tree/plugins/updates/gsd-updates-refresh.c
[13:23] <seb128> " * at startup, after a small delay, force a GetUpdates call
[13:23] <seb128>  * every hour (or any event) check:
[13:23] <seb128>    - if we are online, idle and on AC power, it's been more than a day
[13:23] <seb128>      since we refreshed then RefreshCache"
[13:23] <desrt> tracking leaks of values created by gdbus is difficult!
[13:24] <seb128> desrt, oh, you received the hud bugs from htorque, good ;-)
[13:24] <desrt> glad to hear that my icon thing was indeed the 'big one'
[13:24] <seb128> hehe
[13:24] <jbicha> every hour, wow! I wonder why they think that's a good idea
[13:25] <chrisccoulson> you need to use up your 3G allowance somehow!
[13:25] <chrisccoulson> :-)
[13:32] <cyphermox> chrisccoulson: 3G allowance?
[13:32] <cyphermox> how come I was never told about this? ;)
[13:33] <desrt> ditto
[13:37] <didrocks> desrt: do you think it worths spending some time on the gtk side or should I just try doing some workaround on g-c-c (with your patch)
[13:37] <desrt> didrocks: maybe we could discuss more about what is actually happening in compiz
[13:38] <desrt> i heard some horrifying story about how you grab all possible key combinations?
[13:38] <didrocks> desrt: well, TBH, the compiz devs are totally under a big load of other stuff to fix, so I don't think they will have time to look at that TBH
[13:39] <desrt> i'm not asking for a fix
[13:39] <desrt> just an explanation about how it's done
[13:39] <desrt> i assume the way in which we do it now at least approximates our idea of what the best thing to do is
[13:39] <didrocks> smspillaz: any opinion? ^
[13:48] <jbicha> didrocks: cool, new compiz :)
[13:49] <didrocks> jbicha: don't talk about the keybinding change, pitti wants to be surprised and will try to discover them :)
[13:49] <pitti> heh
[13:49] <jbicha> lol
[13:49] <pitti> hey jbicha, how are you?
[13:52] <jbicha> pitti: causing trouble, you know, breaking string freeze, breaking feature freeze, etc...
[14:01] <rickspencer3> kenvandine, hey
[14:01] <kenvandine> hey rickspencer3
[14:01] <rickspencer3> kenvandine, do you have any docs for GwibberGtk?
[14:01] <kenvandine> not really, best docs are looking at the gir
[14:01] <kenvandine> i tried to generate them... but failed
[14:02] <rickspencer3> kenvandine, so, you had the microblog panel in old gwibber
[14:02] <kenvandine> i am hoping girafe help there someday
[14:02] <rickspencer3> do you have something like that in new gwibber?
[14:02] <kenvandine> yes
[14:02] <kenvandine> GwibberGtk.Entry
[14:02] <rickspencer3> hmmm
[14:03] <pitti> [regression] Invisible resize border is now only 1px wide (LP: #953839)
[14:03] <kenvandine> rickspencer3, look at entry-python.py in examples/
[14:03] <pitti> didrocks: ^ oh, thanks, thanks, thanks, thanks!
[14:03] <didrocks> pitti: heh, it was in case you didn't install mutter before ;)
[14:04] <kenvandine> rickspencer3, i think that example is a bit broken, but it should point you in the general direction
[14:04] <rickspencer3> kenvandine, where is examples/ ?
[14:04] <pitti> didrocks: oh argh, ctrl+super+cursor up/down?
[14:04] <didrocks> pitti: you cheated!
[14:04] <kenvandine> in the bzr branch
[14:04] <pitti> these design guys really don't use keyboards, do they *sigh*
[14:04]  * desrt loves dbusmenu
[14:04] <didrocks> pitti: long discussion
[14:04] <didrocks> pitti: but there is a tradeoff and a good news!
[14:04] <didrocks> pitti: with those keys, we can keep Ctrl + alt + arrows
[14:05] <didrocks> for ws switching, even next cycle :)
[14:05] <seb128> desrt, found your leak there?
[14:05] <pitti> didrocks: how did super+up prevent us from keeping ctrl+alt+arrows?
[14:05] <pitti> didrocks: or was this part of a bargaining trade? :-)
[14:05] <desrt> seb128: no.  was finally able to reproduce the issue with hud/nautilus/panel-service eating 100% CPU
[14:05] <didrocks> pitti: the second option ;)
[14:05] <seb128> desrt, it's not hard to reproduce, open the properties of a bookmarked folder
[14:06] <desrt> hud-service is an innocent bystander here.  the problem is that nautilus is changing its menus like crazy
[14:06] <seb128> desrt, but I'm curious to know about the issue ;-)
[14:06] <desrt> kill hud-service and the problem continues
[14:06] <desrt> seb128: ya.  i'm on the case
[14:06] <seb128> desrt, great, btw the gedit powerpc user tracked the nautilus issue to start in the "use gresources" version as well
[14:07] <seb128> desrt, so it seems there is something between gresources, appmenu and powerpc
[14:07] <seb128> desrt, that's lower priority that the bug you are on though ;-)
[14:09] <pitti> jbicha, seb128: is anyone on the aisleriot FTBFS? (i. e. update to new upstream version or backport fix)?
[14:09] <pitti> not sure whether we intentionally stayed at 3.2
[14:09] <pitti> but if we do, we can just backport that commit
[14:10] <seb128> pitti, not me, jbicha is the maintainer usually
[14:10] <pitti> our VCS has a 3.3.1 merge stacked up
[14:10] <pitti> jbicha: ^ do you want to do the 3.3.2 update and upload, or want me to handle?
[14:11] <pitti> seb128: Colin also wrote some interesting bit about libical (as that's still on your list)
[14:14] <seb128> pitti, yes it is, but weird, the previous build issue we had was a test failing on armel only, so Colin's comment seem to address another (racy) issue
[14:16] <pitti> seb128: failed on ppc, too
[14:18] <jbicha> pitti: we intentionally are staying at 3.2 as we don't want guile-2.0 and guile-1.8 on the CD, there is a new 3.2 release though which we should probably take
[14:18] <pitti> jbicha: ah, right
[15:21] <seb128> pitti, do you plan to update glib?
[15:23] <pitti> seb128: won't manage today any more, but can do tomorrow if needed
[15:23] <nessita> jbicha: hi there! I just saw your comment on https://bugs.launchpad.net/ubuntuone-control-panel/+bug/956077. I'm a little confused, I thought the doc team was not adding Ubuntu One screenshots to the doc, from another conversation I read regarding a UIFe we asked
[15:23] <ubot2> Launchpad bug 956077 in ubuntuone-control-panel/trunk "[UIFe] Colour changes for the QT control panel" [High,Fix released]
[15:23] <nessita> jbicha: did I got that wrong?
[15:23] <seb128> pitti, I saw you replied about the single include stuff so I was wondering
[15:23] <seb128> pitti, not needed no, I wanted to say just stack stuff in the vcs if you have some, I'm waiting on an upstream powerpc gresource fix that I want to include in the next upload
[15:24] <pitti> ack
[15:24] <nessita> jbicha: I'm happy to provide all the screenshots you need, but I thought you weren't needing them :-/
[15:25] <jbicha> nessita: we don't have any screenshots to update & it's past documentation freeze, maybe next cycle we'll document it more
[15:25] <nessita> jbicha: right, so perhaps I misunderstood your comment in the bug report?
[15:25] <nessita> jbicha: I thought you were pinging about those
[15:43] <jbicha> nessita: right, I wasn't pinging, it was more "by the way, this doesn't end up needing clearance from docs after all"
[15:46] <nessita> jbicha: awesome, thanks for the clarification :-)
[16:25] <kenvandine> popey, your salut bug you filed, seems to be fixed in 0.7.2 but i don't have access to a mac to verify it works with ichat
[16:25] <kenvandine> it does work with 11.04 and 11.10 clients though
[16:25] <popey> kenvandine: i upgraded the kids 11.10 machines to 12.04 ⍨
[16:26] <popey> so now I have no way of testing it with the machines I have
[16:26] <kenvandine> so no ichat anymore?
[16:26] <popey> oh I have ichat
[16:26] <kenvandine> i've tested it with 11.04 and 11.10
[16:26] <kenvandine> and it works
[16:26] <kenvandine> but not with ichat
[16:26] <kenvandine> it isn't built yet, but will be soon
[16:26] <popey> sorry, I'm confused
[16:27] <popey> ☺
[16:27] <kenvandine> understand now?
[16:27] <popey> so between what and what do you want me to test? ☺
[16:27] <popey> ichat and..?
[16:27] <kenvandine> test ichat with 12.04
[16:27] <popey> oh cool, I can test that easy
[16:27] <kenvandine> after you get telepathy-salut 0.7.2
[16:27] <kenvandine> which is building now
[16:27] <popey> will do
[16:27] <kenvandine> thx
[16:28] <kenvandine> today's like the great telepathy release day :)
[16:28] <kenvandine> all the stable releases are coming for the cycle
[16:34] <popey> excellent
[16:36] <pitti> good night everyone!
[16:37] <kenvandine> good night pitti
[17:10]  * didrocks waves good evening
[17:34] <mterry> No meeting I assume?
[17:36]  * mterry goes back to logging in and out
[17:39] <kenvandine> mterry, hehe
[17:39] <kenvandine> fun working on a greeter i guess :)
[17:40] <mterry> kenvandine, :)  stupid crasher, can't always reproduce, so I have to cycle several times
[18:07] <desrt> shame didrocks is gone...
[18:08]  * desrt may have found a much better way of dealing with grabbing alt for the hud...
[18:10] <seb128> desrt, oh?
[18:10] <desrt> seb128: go into the mouse control panel
[18:10] <seb128> desrt, open a bug, duflu might be interested as well
[18:10] <ogra_> you use a stapler ?
[18:11] <desrt> enable the "show position of pointer when the control key is pressed" option
[18:11] <seb128> desrt, that option sucks, it breaks stuff
[18:11] <desrt> seb128: oh.  it does?
[18:11] <seb128> desrt, I was pondering for a while dropping it
[18:11] <desrt> how?
[18:11] <seb128> desrt, bug #9441
[18:11] <ubot2> Launchpad bug 9441 in gnome-control-center "the locate pointer option breaks other keybindings" [Medium,Confirmed] https://launchpad.net/bugs/9441
[18:11] <seb128> desrt, 4 digit bug ;-)
[18:11] <kklimonda> hmm, what can I do to make unity-greeter show a user prompt? setting greeter-hide-users=true in lightdm.conf is not enough - now I only see a guest account
[18:12] <desrt> seb128: breaks mouse stuff...
[18:12] <seb128> kklimonda, it should be enough, maybe hide the guest user as well
[18:12] <kklimonda> ah, greeter-show-manual-login
[18:12] <bcurtiswx> dobey, any  fixes that you would like a test with?
[18:12] <kklimonda> I wonder if that one will work
[18:12] <desrt> seb128: it looks like the code in g-c-c makes no attempt to account for the mouse.  could probably be fixed.
[18:13] <seb128> desrt, not only mouse
[18:13] <seb128> bug #783382
[18:13] <ubot2> Launchpad bug 783382 in gnome-control-center "nautilus malfunctions when using "ctrl-c" to copy a file name with show location of mouse pointer turned on (dup-of: 9441)" [Low,Invalid] https://launchpad.net/bugs/783382
[18:13] <ubot2> Launchpad bug 9441 in gnome-control-center "the locate pointer option breaks other keybindings" [Medium,Confirmed] https://launchpad.net/bugs/9441
[18:13] <seb128> "Select a file in nautilus, press F2, then the file name is automatically selected, press "ctrl-c" to copy the selected file name (not the whole path of file)
[18:13] <seb128> Case 1: open gedit or leafpad what so ever, press "ctrl-v" to paste, the result is the whole path of the selected file, but I just expect the selected file name."
[18:13] <seb128> desrt, ^ that's keyboard
[18:14] <desrt> that's more interesting
[18:14] <desrt> sounds like a nautilus bug though, to be honest
[18:14] <kklimonda> seb128: I was following your comment from some lightdm bug, but there seem to be a new config key  greeter-show-manual-login that you have to use :)
[18:15] <seb128> desrt, or #354790 "default keyboard-shortcut Ctl-Alt-L does not lock screen"
[18:15] <seb128> desrt, or another bug is that it breaks mute button
[18:15] <seb128> desrt, look at the dup, there are a variety of issues
[18:15] <desrt> mute?!
[18:15] <desrt> hum
[18:15] <seb128> desrt, #305246
[18:15] <desrt> you know -- i hate X
[18:15] <seb128> hehe, who doesn't? ;-)
[18:16] <desrt> fwiw, i think a lot of the brokenness is caused by the fact that gnome-settings-daemon has a bug
[18:16] <seb128> kklimonda, hey, maybe you need a new bug, lamont was having similar issues
[18:16] <desrt> the code for grabbing mute is unaware of the code for grabbing the control key
[18:16] <dobey> bcurtiswx: not today. hopefully tomorrow i'll be able to figure it out
[18:16] <desrt> and they have a bad interaction, i bet
[18:16] <desrt> and they're in the same process with a filter on the same window...
[18:16] <seb128> desrt, could be yes, but all those grab stuff are non trivial, there is always an interaction with something
[18:16] <desrt> seb128: i will develop the one true solution :)
[18:16] <seb128> ;-)
[18:17] <seb128> desrt, get ride of X?
[18:17] <bcurtiswx> dobey, OK GL :)
[18:17] <desrt> well, yes :)
[18:17] <seb128> ;-)
[18:17] <seb128> mterry, hey
[18:17] <seb128> mterry, got a minute?
[18:17] <seb128> 3 small questions for you
[18:17] <desrt> the true true solution is that we have an input manager in the same way that we currently have an output (read: compositing) manager
[18:18] <seb128> desrt, like only one piece of code dealing with all grabs and dispatching?
[18:18] <desrt> yes
[18:18] <mterry> seb128, sure
[18:18] <desrt> trouble with X is that all the clients are on equal footing and nobody is ever fully in control
[18:19] <seb128> mterry, hey, how are you?
[18:19] <mterry> seb128, that counts as #1.  :)
[18:19] <mterry> seb128, I'm fine
[18:19] <seb128> mterry, lol, not fair :p
[18:19] <seb128> mterry, ok, easy ones or hard ones first? ;-)
[18:20] <seb128> not 2!
[18:20] <mterry> seb128, hah, easy ones I guess
[18:20] <desrt> seb128: did mterry tell you about what he discovered the other day?
[18:20] <seb128> mterry, ok, the side one was, do you have any clue about kklimonda's question, not the first user I see who disable the user list and get "guest" and no "other" field
[18:21] <seb128> desrt, the earth is round?
[18:21] <kklimonda> seb128: it works when I also disable the guest account (another bug - the lightdm.conf.example setting for doing that is wrong :))
[18:21]  * mterry is a slow learner apparently
[18:21] <kklimonda> seb128: but I'd expect that hiding user list should make the prompt appear
[18:21] <seb128> kklimonda, that option got added recently
[18:21] <mterry> seb128, I didn't see his question, but it's fixed in trunk
[18:21] <seb128> mterry, lol
[18:21] <mterry> seb128, in service of another fix
[18:21] <mterry> seb128, I'm going to patch ubuntu this week
[18:22] <seb128> mterry, is bug #946674 what you work on?
[18:22] <ubot2> Launchpad bug 946674 in unity-greeter "unity-greeter crashed with SIGSEGV in background_loader_ready_cb()" [High,Confirmed] https://launchpad.net/bugs/946674
[18:22] <seb128> mterry, ready recent activity it seems so
[18:22] <mterry> seb128, yeah, I looked at that today.  Have a test package
[18:22] <seb128> mterry, I told robert_ancell I would ping you about it today
[18:22] <seb128> mterry, thanks, that was my main question
[18:22] <mterry> seb128, can't seem to reproduce
[18:22] <seb128> mterry, side ones now
[18:22] <seb128> - can we get an unity-greeter release?
[18:23] <seb128> I want at least the onscreen keyboard fix in
[18:23] <seb128> fixing that segfault would be nice
[18:23]  * desrt comes to a realisation
[18:23] <mterry> seb128, sure, once bug 946674 is resolved, I guess.  I don't know of other bugs extant
[18:23] <seb128> - why do you need to logout and in? isn't the greeter restarted on user switch?
[18:24] <ubot2> Launchpad bug 946674 in unity-greeter "unity-greeter crashed with SIGSEGV in background_loader_ready_cb()" [High,Confirmed] https://launchpad.net/bugs/946674
[18:24] <desrt> i'm writing a program that does experimental things with grabs in X
[18:24] <desrt> well, it was nice knowing you guys
[18:24] <desrt> bye
[18:24] <kklimonda> mterry: can you fix date/lightdm.conf and replace greeter-show-guest with greeter-allow-guest? I've had to grep source to find a correct setting :)
[18:24] <kklimonda> I guess I should report it so the fix goes to precise before release..
[18:24] <seb128> like usually I just keep my session running
[18:24] <seb128> desrt, lol
[18:24]  * desrt fully expects his keyboard to be non-functioning in the next 30 seconds or so
[18:24] <mterry> seb128, yeah, but when it does crash, then things get awkward
[18:24] <seb128> mterry, ok
[18:24] <seb128> mterry, well I will let you work
[18:25] <seb128> mterry, oh, could you also change the "if no user list is showed, rename "other" to "username" or something"
[18:25] <mterry> kklimonda, we have a bad default?
[18:25] <mterry> seb128, I think it's called "Login" right?
[18:25] <seb128> mterry, schools don't like have an "other" entry on their login screen, it makes no sense :p
[18:25] <kklimonda> mterry: no, but the setting from the example.conf does not match what lightdm checks for in the code
[18:25] <seb128> mterry, bug #960177
[18:25] <ubot2> Launchpad bug 960177 in unity-greeter "the entry should be named "username" not "others" when hide-users is used" [High,Confirmed] https://launchpad.net/bugs/960177
[18:25] <kklimonda> mterry: so without actually checking source code I couldn't disable the guest account in lightdm
[18:26] <seb128> mterry, you like screenshots I'm sure, https://launchpadlibrarian.net/97576514/username.png
[18:26] <mterry> kklimonda, k, makes sense
[18:26] <seb128> mterry, you got assigned that bug, thanks ;-)
[18:26] <mterry> that's up to date?
[18:26] <mterry> I coulda sworn it was Login
[18:26] <mterry> ok
[18:26] <seb128> mterry, I didn't check but was reported 10 days ago and I didn't see an unity-greeter upload since
[18:33] <kklimonda> also, could someone take a look at bug 970932? I can't find anyone on #u-unity and it's driving me crazy :(
[18:33] <ubot2> Launchpad bug 970932 in unity "unity treats windows as belonging to multiple workspaces at the same time" [Undecided,New] https://launchpad.net/bugs/970932
[18:34] <seb128> kklimonda, try #ubuntu-unity again, there are not lot of unity hacker on our channel
[18:34] <seb128> kklimonda, but that seems a corner case, why would you put stuff on 2 workspaces to start
[18:35] <kklimonda> seb128: but I don't, unity does it by itself when I use super+arrow to arrange windows :/
[18:35] <kklimonda> seb128: this may not really be an actual byg
[18:36] <kklimonda> bug*
[18:36] <seb128> kklimonda, seems like a compiz bug, try pinging smspillaz when he's around
[18:36] <kklimonda> ok
[18:38] <seb128> mterry, one of the dup description points to https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/971437 in case that useful
[18:38] <ubot2> Launchpad bug 971437 in lightdm "lightdm crash/loop after recent 12.04 beta updates" [Undecided,New]
[18:38] <seb128> mterry, which claims to be a multi monitor issue
[18:39] <tjaalton> kklimonda: for me it's moving a such window to the first workspace from the rightmost one every time the display shuts off or so.. highly annoying
[18:39] <seb128> mterry, could people just confusing a segfault for another one though, I somewhat doubt so many users run dual monitors and the descriptions are inconsistant
[18:40] <mterry> seb128, someone just reported reproduction steps, I'll try thouse
[18:41] <seb128> mterry, seems a bit weird, the greeter doesn't handle xml backgrounds
[18:42] <mterry> seb128, agreed, but maybe just pointing it at an xml file is enough?  the other reproduction steps involved an unreadable file.  so probably something in the path for handling bad backgrounds
[18:45] <seb128> mterry, oh, I managed to trigger it (once)
[18:46] <mterry> seb128, yay
[18:46] <mterry> kklimonda, lightdm.conf fixed, thanks for notice
[18:46] <seb128> mterry, or maybe not :-(
[18:47] <seb128> mterry, http://pastebin.ubuntu.com/913452/ seems different
[18:47] <mterry> seb128, yeah...
[18:48] <mterry> seb128, that's one fear I have about this bug.  The original stack is almost certainly fixed.  I'm working off people's reports of how to reproduce crashers
[18:48] <seb128> mterry, I created a /tmp/nofile, called SetBackgroundFile() in dfeet and give it "/tmp/nofile", deleted the file then and switched user
[18:48] <seb128> mterry, which is cheating but assuring accountsservice has a buggy background info
[18:49] <mterry> sure
[18:49]  * mterry tries
[18:52] <seb128> mterry, no, no luck getting it again
[18:52] <mterry> seb128, no crash for me
[18:52] <seb128> dunno, it's not happening for me
[18:52] <mterry> seb128, I did get a crash earlier today....  once.  Maybe this is some weird one time thing
[18:52] <seb128> mterry, I guess ask on the bug to somebody to replace unity-greeter by a valgrind wrapper calling the real binary
[18:53] <seb128> better to get them to have an unstripped binary though
[18:53] <seb128> maybe do a deb with a unity-greeter.real and a script calling valgrind, do it unstripped, add the deb to the bug
[18:53] <mterry> Or... if this is a one-time thing, try in a VM
[18:53]  * mterry boots one up
[18:58] <seb128> chrisccoulson, that scribus bug, fixing the mimetype would fix the issue, nautilus would still prefer a subtype handler than installing
[18:58] <chrisccoulson> seb128, oh, right. i didn't think of that ;)
[18:58] <seb128> wouldn't*
[18:59] <seb128> chrisccoulson, but I often gets annoyed at firefox claiming being an xml handler ... do anyone really use it like that?
[18:59] <seb128> chrisccoulson, I'm pondering if we should drop that
[18:59] <chrisccoulson> seb128, it's actually pretty good at viewing xml files ;)
[18:59] <seb128> chrisccoulson, well, who views xml files?
[19:00] <seb128> 95% of types are subtypes of xml not meant to be viewed as xml
[19:00] <seb128> like opened a gtkbuilder file as xml, not useful ;-)
[19:00] <seb128> opening
[19:00] <seb128> I would prefer a glade file to be open in gedit as text rather than firefox as xml
[19:01] <seb128> chrisccoulson, same for firefox being a text/plain handler ... are those .desktop mimetype useful for firefox itself or just for i.e nautilus?
[19:01] <seb128> chrisccoulson, like I doubt many users want firefox as a text editor
[19:02] <chrisccoulson> yeah, you couldn't use it as a text editor
[19:04] <desrt> seb128: i think i have a modification that fixes some issues
[19:04] <desrt> no more nautilus crashes, for example
[19:04] <seb128> desrt, context? I was let on grabs but I can't link that to nautilus ;-)
[19:04] <desrt> the key is for the thing doing the keyboard grab to freeze mouse events and acquire a mouse grab when a key grab is established
[19:05] <chrisccoulson> seb128, actually, application/vnd.scribus doesn't sub-class any other type, so if the type existed on the system and scribus wasn't installed, then nautilus wouldn't open it in anything else
[19:05] <desrt> and if you see a button click, immediately release all grabs
[19:05] <desrt> the existing code was not doing that -- so if you continued to use the mouse while holding control you could get yourself into some situations where other things attempted to accquire grabs (like nautilus for its popup menu) and would fail
[19:05] <seb128> chrisccoulson, so it's an easy fix, move the definition to shared-mime-info
[19:06] <chrisccoulson> seb128, yeah, basically that should work
[19:06] <desrt> seb128: although now there are probably issues with touchscreens or something else not covered by pointer grabs...
[19:06] <seb128> chrisccoulson, thanks ;-)
[19:07] <seb128> desrt, could be, I learnt that trying to be smart with grab is harder as it seems ;-)
[19:07] <seb128> desrt, you always have something somewhere doing weird stuff and screwing you
[19:07] <desrt> seb128: there seems to be a complete lack of good documentation about what all of these things mean
[19:08] <seb128> chrisccoulson, btw I need to annoy you about tb one of those days ;-)
[19:08] <chrisccoulson> excellent :)
[19:08] <seb128> chrisccoulson, it's twice recently that he frozen on a "email sent" dialog
[19:08] <seb128> urg, "it froze"
[19:08] <chrisccoulson> seb128, imap?
[19:08] <chrisccoulson> and with 11.0.1?
[19:08] <seb128> chrisccoulson, smtp
[19:09] <chrisccoulson> oh, yeah ;)
[19:09] <seb128> ;-)
[19:09] <seb128> chrisccoulson, weird think is that it wrote "email sent", froze, I forced quited it, and after reopening the email was not in the sent box and only half writen recovered in draft
[19:10] <seb128> chrisccoulson, so maybe I sent the same email twice after rewriten the end I'm not sure :p
[19:10] <chrisccoulson> seb128, has it happened with 11.0.1 yet?
[19:10] <seb128> chrisccoulson, does it ring any bell?
[19:10] <seb128> chrisccoulson, no, but I have it like once a week
[19:10] <chrisccoulson> seb128, hopefully it is bug 962631 then ;)
[19:10] <seb128> if I get it with 11.0.1 I will let it frozen and ping you
[19:10] <ubot2> Launchpad bug 962631 in thunderbird "Thunderbird 11 hangs against Exchange 2007" [Medium,Confirmed] https://launchpad.net/bugs/962631
[19:10] <seb128> chrisccoulson, I don't use exchange ;-)
[19:10] <chrisccoulson> they just did an out-of-band update to fix that
[19:10] <seb128> chrisccoulson, you must confuse me with some ms guy :p
[19:11] <seb128> chrisccoulson, ok, thanks
[19:11] <chrisccoulson> seb128, oh, the title sucks. it doesn't need exchange. it affects anyone with an imap server ;)
[19:11] <chrisccoulson> in fact
[19:11] <chrisccoulson> if you look at the stacktrace there, it locks up in smtp code ;)
[19:12] <chrisccoulson> so, i should correct myself - "it affected anyone using smtp" ;)
[19:12] <chrisccoulson> i'd put money on that being your issue :)
[19:12] <micahg> fixed :)
[19:13] <mterry> seb128, reproduced!  After enabling manual login. Not sure if related yet, but I have a coredump, so I'm going to sit here and spin a bit
[19:13] <seb128> mterry, great
[19:13] <seb128> chrisccoulson, let's see, how much beer do you bet? ;-)
[19:14] <desrt> seb128: warning: the next time you see chrisccoulson will be in the USA and beer bets will be repaid in the local currency.  are you sure you wish to proceed?
[19:14] <chrisccoulson> heh
[19:14] <seb128> desrt, thanks, you just reminded me I need to get a new esta my expired in january
[19:15]  * desrt is so happy to keep his fingerprints to himself at the airport
[19:15] <chrisccoulson> on the subject of beer, i keep waiting for this to be in stock again: http://www.brewdog.com/product/sink-the-bismarck :-)
[19:16] <seb128> lol
[19:16] <seb128> you need to hard stuff to keep up with firefox ;-)
[19:17] <chrisccoulson> yeah :)
[19:21] <chrisccoulson> g'ah, i'm sick of people reporting firefox crashes without any useful information on them
[19:21] <chrisccoulson> do people not read the bug reporting instructions?
[19:21] <desrt> chrisccoulson: hey
[19:21] <desrt> chrisccoulson: i was using firefox earlier and it crashed
[19:21] <desrt> know anything about that?
[19:21] <chrisccoulson> lol
[19:21] <mterry> seb128, already fixed in trunk :)
[19:24] <desrt> seb128: so this bug with copying the full name in nautilus appears to be fixed
[19:25]  * mterry prepares releases of lightdm/unity-greeter
[19:25] <desrt> like, even the existing code on ubuntu seems working fine...
[19:25] <mterry> seb128, is robert still working?
[19:25] <chrisccoulson> oh, wow, only in the UK would "Weed Makes Everything Better" be trending on twitter!
[19:30] <chrisccoulson> oh, scribus has flickering menus too!
[19:31] <desrt> are we too far along now to just cancel dbusmenu entirely? :)
[19:31] <desrt> i mean... we can get a freeze exception for that, right?
[19:31] <chrisccoulson> lol
[19:32] <chrisccoulson> we should replace it with XEMBED
[19:32] <desrt> would probably cause fewer issues
[19:32]  * desrt thinks about that for a moment
[19:32] <desrt> okay.  probably not.
[19:32] <chrisccoulson> oops, what did i do ;)
[19:33] <desrt> actually
[19:33] <desrt> would probably cause fewer issues, indeed
[19:33] <desrt> if we were clever about it...
[20:01] <seb128> mterry, oh, great
[20:03] <seb128> mterry, robert? no he said he got this michael guy doing all the work for him so he can just relax on the beach ;)
[20:03] <mterry> seb128, :)  didn't know if I should roll lightdm for him or if he had short-term plans for it
[20:04] <seb128> mterry, wait, he was still tracking the .xsession-errors rotating bug when I spoke to him this morning
[20:04] <mterry> seb128, ah cool
[20:04] <mterry> seb128, thanks
[20:04] <seb128> mterry, you can do unity-greeter though, I think you won this one by working on it ;-)
[20:04] <seb128> mterry, oh, speaking of which, you won gtk by doing that ubuntu-local patch and revert uploads, enjoy!
[20:04]  * seb128 hudes
[20:04] <seb128> hides
[20:04] <mterry> seb128, yar, I don't think he's active in u-g much
[20:04] <mterry> seb128, dammit
[20:05] <seb128> ;-)
[20:05]  * kenvandine hudes too 
[20:05] <mterry> seb128, if anything, those uploads show I *shouldn't* own gtk+  ;)
[20:05] <seb128> kenvandine, you want bogs? :-P
[20:05] <mterry> seb128, the ol' "do something bad enough, you won't be invited back" strategy
[20:05]  * kenvandine hudes more
[20:05] <seb128> kenvandine, ;-)
[20:05] <seb128> kenvandine, it's not my fault, I got so fan of the hud that I typo it :p
[20:06] <seb128> mterry, hehe, nice try ;-)
[20:06] <kenvandine> hahaha
[20:06]  * mterry still raises the hud accidentally about thrice a day
[20:07] <kenvandine> hehe... mterry said thrice :)
[20:07] <mterry> kenvandine, I'm trying to bring it back  :)
[20:07] <kenvandine> :-D
[20:07] <kenvandine> if anyone can do it... you can!
[20:08] <mterry> people say once and twice all the time.  why not thrice?!
[20:08] <kenvandine> indeed...
[21:46] <Sweetshark> jasoncwarner_: ping?
[22:06] <jasoncwarner_> Sweetshark: hey
[22:09] <Sweetshark> jasoncwarner_: did you see my comment wrt bug 969707?
[22:09] <ubot2> Launchpad bug 969707 in libreoffice "package python-uno uses libreoffice-core in preinst" [Critical,Fix committed] https://launchpad.net/bugs/969707
[22:09] <jasoncwarner_> Sweetshark: wip?
[22:09] <jasoncwarner_> Sweetshark: oh, fix comitted?
[22:09] <jasoncwarner_> nice
[22:11] <Sweetshark> jasoncwarner_: well, a fixed version was uploaded to a ppa today. the build just finished on i386, but still runs on amd64. I will test a dist-upgrade run tommorrow and if successful, will throw it over the fence.
[22:11] <jasoncwarner_> Sweetshark: gotta love those fast builds ;) nice, thanks
[22:14] <Sweetshark> jasoncwarner_: well, local builds are faster (and developer builds are a _lot_ faster), but to test dist-upgrades I try to be as close to the "real thing" as possible.
[22:14] <micahg> Sweetshark: shouldn't those instances be breaks instead of conflicts
[22:19] <Laney> Hm, doesn't the Breaks/Conflicts give you a high enough version to run sync_extensions?
[22:33] <jasoncwarner_> bryceh RAOF TheMuso don't forget about the meeting for today. Add agenda items, if any. https://wiki.ubuntu.com/DesktopTeam/Meeting/2012-04-03
[22:33] <bryceh> jasoncwarner_, ok
[22:33] <jasoncwarner_> Also, please update with your weekly updates...thanks !
[22:34] <bryceh> oops, looks like themuso's editing.  /me waits
[22:35] <TheMuso> bryceh: Done now.
[22:35] <bryceh> anyway nothing exciting from me, just usual bug work
[22:36] <bryceh> jasoncwarner_, anything more needed from RAOF or I on the LTS position hiring front?
[22:40] <jasoncwarner_> bryceh: no, thanks I passed it to veronika (assuming you are both still good with him)
[22:40] <bryceh> yep
[22:53] <achiang> hm, did ubuntu mono change recently? seems... smaller now
[22:57] <jasoncwarner_> bryceh: robert_ancell RAOF and TheMuso FYI...no agenda items....so....keep on hacking :)
[23:00] <RAOF> achiang: You're noticing the new fontconfig, I think.
[23:05] <achiang> RAOF: hm, the changelog for 'fontconfig' isn't really that informative?
[23:27] <achiang> RAOF: or did it come from some other package?
[23:30] <RAOF> achiang: Sorry, it's freetype.
[23:32] <achiang> RAOF: thanks
[23:32]  * achiang reads #972223 but doesn't really grok it
[23:32] <achiang> oh well