[00:13] <Sarvatt> nvidia compatible with natty is in ppa:ubuntu-x-swat/x-updates now (and this time I made sure it actually worked)
[00:13] <Sarvatt> 6 hour build queue though :(
[00:15] <RAOF> Oh, funky.  That's released?
[00:16] <RoAkSoAx> Sarvatt: \o/
[00:16] <RoAkSoAx> yay!!
[00:17] <TheMuso> Good news, I sware my Apple notebook has almost been cooked from the inside out whilst running nouveau in 2D only. :) I know it will cook with 3D. :)
[00:18] <TheMuso> 7;3~/c
[00:21] <bryce_> RAOF, released and public :-)
[00:22]  * Laney looks forward to minecraft again :-)
[00:24] <bryce_> Laney, so much for your productivity eh?
[00:25] <broder> Sarvatt: whoo!
[01:35] <chrisccoulson_> bug 724678 is the best bug report, ever
[01:35] <ubot2> Launchpad bug 724678 in nautilus "upgrading" [Undecided,New] https://launchpad.net/bugs/724678
[01:39] <broder> wow. that's impressively useless
[03:05] <jwhisnant> looking to change my maverick netbook install desktop back to the the one found in lucid
[03:05] <jwhisnant> but I cant figure out how to do that - any hints, suggestions ?
[03:10] <RAOF> jwhisnant: It's not clear exactly what you want to do.  However, #ubuntu-desktop is unlikely to be the correct forum for answers; this place is for development.
[03:10] <RAOF> !support | jwhisnant
[03:10] <ubot2> jwhisnant: The official ubuntu support channel is #ubuntu. Also see http://ubuntu.com/support and http://ubuntuforums.org and http://askubuntu.com
[03:11] <jwhisnant> RAOF, thanks, I'll ask there ... again ...
[03:11] <RAOF> If #ubuntu isn't helping, then ubuntuforums or askubuntu, although slower, should have a broader audience.
[03:59] <chrisccoulson> w00t, uploaded the last firefox beta to natty now \o/
[04:00] <RAOF> chrisccoulson: Hurray!  So that should be built, what, early next week? :)
[04:00] <chrisccoulson> lol
[04:00] <chrisccoulson> it doesn't take quite that long ;)
[04:00] <chrisccoulson> it's about 2.5 hours, and most of that is the test suite ;)
[04:01] <chrisccoulson> (all but 40 minutes)
[04:05]  * micahg hopes 2 of the remaining build failues disppear
[04:19] <lamalex> bryce_, I am in X dependency hell :\
[04:23] <bryce_> lamalex, oh?
[04:23] <bryce_> raof or tjaalton or I could probably help but we'd need to know more specifics
[04:23] <lamalex> bryce_, yeah I need to know what more specifics to give you before I can give them :P
[04:23] <RAOF> Well, let's start with the error message :)
[04:24] <lamalex> let's move to #distro?
[05:56] <Sweetshark> Morning all!
[05:58] <bryce_> hi Sweetshark
[05:59]  * Sweetshark suspects himself to have put a buildd in an endless loop ...
[05:59] <Sweetshark> *ashamed*
[07:54] <didrocks> good morning
[07:55] <didrocks> waow, 15 minutes blaming first my wifi spot before seeing that dhcp3-client was the cause of not connecting…
[07:57] <didrocks> ok, seems that isc-dhcp (4.1.1-P1-15ubuntu5) fixes it
[07:57] <didrocks> just upgraded at the wrong moment it seems :)
[08:01] <pitti> Good morning
[08:01] <didrocks> hey pitti! How are you?
[08:02] <pitti> hey didrocks
[08:02] <pitti> for some reason terribly tired
[08:02] <pitti> but I'll manage
[08:02] <didrocks> oh? the week-end will be there soon :)
[08:02] <mvo> me too!
[08:02] <didrocks> hey mvo ;)
[08:02]  * mvo yawns and takes a extra ccup of tea
[08:03] <mvo> hey didrocks
[08:03]  * pitti hugs mvo
[08:03]  * mvo hugs pitti
[08:04] <pitti> didrocks: FYI, http://launchpadlibrarian.net/65082307/buildlog_ubuntu-natty-amd64.folks_0.3.6-0ubuntu1_FAILEDTOBUILD.txt.gz used the broken dbus
[08:04] <pitti> didrocks: I uploaded a fix an hour after 1.4.6-1ubuntu1 when I noticed the same issue with avahi
[08:04] <pitti> it can just be given back, doing now
[08:05] <didrocks> pitti: thanks for the notice :)
[08:05] <pitti> so, where did my window decorations go..
[08:05] <didrocks> pitti: is unity-window-decorator running?
[08:05] <didrocks> pitti: have you just upgraded?
[08:05] <pitti> partial upgrde last night
[08:06] <pitti> doing dist-upgrade now
[08:06] <didrocks> did you restart since?
[08:06] <pitti> didrocks: no u-w-d
[08:06] <pitti> didrocks: yes, booted this morning
[08:06] <didrocks> there is an ABI break in compiz, u-w-d has to be restarted after the upgrade
[08:06] <pitti> I'll try a full dist-upgrade first
[08:06] <didrocks> hum…
[08:06] <didrocks> ok :)
[08:06] <pitti> it always takes me a bit to sort out
[08:06] <pitti> X.org has been broken for many days now
[08:06] <didrocks> I'm testing upgrading on my netbook now just to check
[08:06] <pitti> trying to dist-upgrade everything removes ubuntu-desktop
[08:07] <didrocks> Xorg is still hang because of nvidia here :/
[08:07] <didrocks> hum…
[08:07] <didrocks> so, the transition yesterday was quite horrible (I had to update and not just rebuild) 17 packages
[08:07] <didrocks> was some package renaming and such
[08:07]  * pitti hugs didrocks, great job!
[08:08] <didrocks> let me see on my intel box if it's ok
[08:08]  * didrocks hugs pitti back, I hope it's not because of me that ubuntu-desktop wants to be removed :)
[08:08] <didrocks> let's see on my (slow) netbook
[08:11] <didrocks> ok, the places with the new libunity symbols and dee are installed, it kept back unity (and all compiz friends) though
[08:11] <didrocks> ah libindicator transition :)
[08:14] <pitti> hm, dist-upgrade is still horribly broken
[08:15] <didrocks> yeah, confirmed, killall unity-window-decorator && unity just after the upgrade works
[08:15] <didrocks> (removed libindicator2 for forcing the upgrade)
[08:15] <kenvandine> good morning guys
[08:16] <didrocks> hey kenvandine, is it you who told me yesterday evening that it was late, it's time to go to bed, blablabla… ? :-)
[08:16] <kenvandine> hehe
[08:16] <kenvandine> soon :)
[08:16] <pitti> didrocks: upgrade fails because compiz-plugin-mains file conflict with compiz-fusion-plugins-main
[08:16] <didrocks> pitti: argh, the Replaces:
[08:16] <pitti> didrocks: it seems the former doesn't have a strict enough Conflicts: ?
[08:17] <didrocks> pitti: yeah, transitional package, stupid issue from me, fixing
[08:17] <pitti> hm, it doesn't have a C:/R: at all
[08:17] <pitti> didrocks: thanks
[08:17]  * bryce_ waves
[08:17] <didrocks> pitti: yeah, I was interruped when I was doing it and forgot then :/
[08:17] <pitti> didrocks: np; I have to install pacakges one by one, great way to find those :)
[08:17] <mvo> lol
[08:17] <pitti> hey bryce_
[08:17]  * mvo hugs kenvandine
[08:17] <didrocks> pitti: the compiz transition was quite… epic (upstream rolled 6 times the tarball before having something which works)
[08:17] <bryce_> heya pitti
[08:18] <kenvandine> hey mvo
[08:18] <kenvandine> didrocks, ugy
[08:18] <mvo> hey :)
[08:18] <kenvandine> ugh even
[08:18] <didrocks> kenvandine: and imagine I compiled all buggy version :/
[08:18] <didrocks> (or tried to…)
[08:18] <pitti> so why does upgrading libunity3 remove empathy..
[08:18] <bryce_> funny story
[08:18] <kenvandine> pitti, amd64?
[08:18] <pitti> yes
[08:19] <kenvandine> empathy is dep wait
[08:19] <bryce_> now that we FINALLY have binary drivers that work with the latest xserver ABI, guess what
[08:19] <didrocks> pitti: empathy -> folks
[08:19] <kenvandine> bryce_, this isn't going to be funny is it?
[08:19] <pitti> empathy Depends: libunity3 (< 3.4.4)
[08:19] <bryce_> yep, X.org has changed the ABI in xserver again
[08:19] <pitti> bryce_: argh!
[08:19] <kenvandine> pitti, folks had failed to build on amd64 earlier, the dbus pc file thing
[08:19] <pitti> kenvandine: right, retried
[08:20] <kenvandine> pitti, so i just rebuilt that
[08:20] <pitti> kenvandine: sorry about that, we had a broken dbus in the aarchive for just one hour, and it must have caught that
[08:20] <kenvandine> waiting for it to publish so empathy can build
[08:20] <kenvandine> yeah, no worries :)
[08:20] <pitti> kenvandine: out of interest, why would empathy have a < dependency on libunity?
[08:20] <kenvandine> that was libunity's fault
[08:20] <kenvandine> shlib
[08:21] <kenvandine> that changed in today's libunity upload though
[08:21] <kenvandine> right didrocks?
[08:21] <pitti> kenvandine: ah, typo in the shlibs then?
[08:22] <kenvandine> didrocks, can you make sure empathy gets built after folks for amd64 gets published?  i am exhausted...
[08:22] <pitti> file replacement problem in python-aptdaemon, I'll fix that myself
[08:22] <kenvandine> not a typo, i think it as intentional
[08:22] <pitti> kenvandine: how can this be intentional?
[08:22] <pitti> kenvandine: anyway, we'll handhold empathy & co, you should go to sleep
[08:22] <kenvandine> the shlib was >= 3.4.2 and << 3.4.4
[08:23] <kenvandine> something like that
[08:23] <pitti> kenvandine: ok, that disqualifies as a typo, but it's still wrong
[08:23] <kenvandine> it's been a long day :)
[08:23] <didrocks> pitti: it wasn't a typo, let me explain you :)
[08:24] <didrocks> but first, uploading the fix C/R
[08:24] <kenvandine> pitti, didrocks had reasons... but it is history now :)
[08:24] <kenvandine> anyway... thanks guys
[08:24] <kenvandine> time for some sleep
[08:25] <didrocks> good night kenvandine
[08:25] <kenvandine> and good morning to you :)
[08:25]  * kenvandine waves!
[08:25] <pitti> kenvandine: sleep well!
[08:27] <didrocks> pitti: ok, done. sorry about it :(
[08:27] <pitti> didrocks: no problem, thanks for quick fix!
[08:27] <didrocks> I thought about the transition, thought about debian syncing, but got interrupted when doing the transitional package
[08:27] <didrocks> :/
[08:28] <didrocks> pitti: so, on libunity
[08:28] <pitti> aptdaemon collected a fair number of upgrade bugs already
[08:28] <didrocks> we decided with the dx team that the libunity API/ABI was totally unstable until we have "real" consumers and feature freeze is there
[08:28] <didrocks> (unity-places* aren't considered as real consumers)
[08:29] <didrocks> so, they broke a lot ABI/API recently
[08:29] <pitti> didrocks: ah, I see
[08:29] <didrocks> that's why the packaging was >= and <<
[08:29] <pitti> didrocks: so this is just a hack until the final release?
[08:29] <didrocks> right :)
[08:29] <didrocks> since yesterday, it has now proper symbol tracking
[08:30] <didrocks> (note that nux still >= and << as the ABI won't be stable soon, but unity is the only consumer)
[08:30]  * pitti uploads aptdaemon fix
[08:32] <Sweetshark> pitti: There is a 3.3.1-1ubunutu1 in the ppa with human icons and it actually compiled in finite time. \o/
[08:33] <didrocks> bryce_: is it package already or it won't do it?
[08:33] <Sweetshark> pitti: Do you have a minute to discuss the libreoffice 3.3.1 backporting to maverick mess?
[08:35] <pitti> Sweetshark: niiice!
[08:37] <pitti> bryce_, RAOF: I have had a broken x.org upgrade (package removals) for a few days now; is that known?
[08:37] <pitti>  xserver-xorg-input-evdev : Depends: xorg-input-abi-12.1
[08:37] <pitti>  xserver-xorg-input-mouse : Depends: xorg-input-abi-12.1
[08:37] <pitti>  xserver-xorg-input-vmmouse : Depends: xorg-input-abi-12.1
[08:37] <pitti>  xserver-xorg-video-vmware : Depends: xorg-video-abi-9.0
[08:37] <Sweetshark> I had a long at the 30 hours buildlog and found nothing too suspicious. Seems the builder was just too slow for that tiny package LO
[08:38] <pitti> Sweetshark: I  hope the 3.3.1-1ubunutu1 was just an IRC typo, it's not in debian/changelog?
[08:38] <pitti> ubun"u"tu, I mean
[08:38] <pitti> Sweetshark: maverick backport> you mean in a PPA?
[08:40] <didrocks> pitti: do you have on your keyboard some umlaut caracters directly accessible?
[08:40] <didrocks> like ö
[08:40] <didrocks> or do you have to press two keys for that
[08:40] <pitti> didrocks: I normally use US layout, but have German layout configured as well; if I need them, I just switch
[08:41] <pitti> didrocks: in German you have ä, ü, ß, etc.
[08:41] <Sweetshark> pitti: yep, just a typo
[08:41] <didrocks> pitti: and for them, you have a direct key for that (no need for " + o for instance)?
[08:42] <pitti> didrocks: yes
[08:42] <didrocks> pitti: ok, thanks :)
[08:42] <pitti> didrocks: want to learn German?
[08:43] <didrocks> pitti: well, I've done 6 years of German, unfortunately, not a lot of things was kept in my memory :)
[08:43] <didrocks> pitti: I was figuring if bug #724747 was valid
[08:43] <ubot2> Launchpad bug 724747 in unity "Super key shortcut overlay not working with umlauts, greek/cyrillic letters" [Undecided,New] https://launchpad.net/bugs/724747
[08:43] <didrocks> (because a shortcut need a direct key, no key combination :))
[08:43] <tjaalton> pitti: sure your mirror is just stale? here evdev depends on -input-abi-12 which is correct
[08:44] <pitti>      2:1.9.99.902-2ubuntu1 0
[08:44] <pitti>         500 http://archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
[08:44] <pitti>  *** 2:1.9.99.901+git20110131.be3be758-0ubuntu6 0
[08:44] <pitti>         100 /var/lib/dpkg/status
[08:44] <pitti> ooh
[08:44] <pitti> that must be a leftover from the time when I was using the PPA
[08:44] <Sweetshark> pitti: yes, maverick backport in the ppa. Our glorious debian/rules generates the debian/control from debian/control.in. And it does it different for maverick and natty. Thus, my debian tarball for 3.3.1-1ubuntu1 maverick was different from the one for natty, which made dput very angry after the upload.
[08:45] <pitti> Sweetshark: you need to change the version number anyway
[08:45] <pitti> Sweetshark: 3.3.1-1ubuntu1~maverick
[08:46] <pitti> Sweetshark: even if the source package was absolutely identical (which it can't, because changelog has to say natty vs. maverick), the binaries would build against older libraries
[08:46] <kamstrup> dpm: good morning - i registered lp:giraffe if you want to propose a merge
[08:46] <pitti> and thus the .debs wouldn't be identical
[08:46] <dpm> hey kamstrup, good morning, cool, thanks :)
[08:46] <kamstrup> dpm: and I also added you to the giraffe-dev team so you have commit rights
[08:46] <pitti> bryce_, RAOF: unping then, local failure; got it sorted out now
[08:47] <dpm> kamstrup, thanks
[08:48] <kamstrup> dpm: just whipping up an answer to your mail
[08:49] <dpm> great
[08:49] <pitti> Sweetshark: oh, we need a corresponding -l10n package upload as well, don't we? or does the current 1:3.3.0~rc4-1ubuntu3 work with 3.3.1?
[08:50] <pitti> Sweetshark: I'm testing an upgrade to the PPA now to check for the -l10n compat
[08:50] <Sweetshark> pitti: yep, I will need to do a l10n upload for natty.
[08:50] <dpm> hey everyone, what's the best package to file a bug about the notification popups?
[08:52] <pitti> dpm: notify-osd
[08:52] <Sweetshark> although l10n _should_ not have changed from 3.3.0 to 3.3.1, but it might contain fixes.
[08:52] <dpm> thanks pitti
[08:57] <pitti> Sweetshark: it seems to work well with the current -l10n
[08:58] <pitti> Sweetshark: so, I'm happy to sponsor this to natty now, all ok from your side?
[08:58] <Sweetshark> yep
[08:58] <Sweetshark> what about FF?
[09:00] <pitti> Sweetshark: are there so many new features between 3.3.0 and 3.3.1?
[09:00] <pitti> in the past these were bug fixes (mostly anyway)
[09:00] <pitti> Sweetshark: but anyway, we wouldn't want to release natty with a release candidate when there's a newer final bug fix release out
[09:02] <pitti> Sweetshark: I'll spend a minute trying to craft a better source.changes, so that you see all changes since natty, not just the single "merge remaining changes from debian up to 3.3.1-1
[09:02] <xclaesse> bah, empathy can't be installed on natty :(
[09:02] <seb128> hello pitti
[09:02] <pitti> Sweetshark: FYI, you can do that more easily during source package build, next time you do an upload I'll tell you
[09:02] <pitti> hey seb128
[09:02] <pitti> xclaesse: on amd64? being worked on
[09:02] <xclaesse> yeah, amd64
[09:03] <pitti> xclaesse: should be sorted out in about two hours
[09:03] <kamstrup> dpm: you've got mail :-)
[09:03] <xclaesse> pitti, great :D
[09:03] <xclaesse> thx
[09:03] <Sweetshark> pitti: k, will do.
[09:03] <seb128> pitti, how are you?
[09:05] <pitti> seb128: bit tired, but ok otherwise; did you sleep better last night?
[09:05] <Sweetshark> 3.3.1 is really a bugfix release, so it is ok I guess although with LO there is still a lot of change even on the release branch.
[09:05] <seb128> pitti, yeah, I slept well this night and feel better today, thanks
[09:05] <pitti> Sweetshark: oh, we need to sync openoffice.org from Debian for that, right?
[09:05] <pitti> seb128: great!
[09:06] <pitti> dput -u libreoffice_3.3.1-1ubuntu1_source.changes
[09:06] <pitti> wheeee!
[09:07] <pitti> Sweetshark: congratulations! that's your first Ubuntu upload!
[09:07]  * pitti hugs Sweetshark
[09:07] <Sweetshark> pitti: we might even need our own "release" for the openoffice.org transitionals.
[09:08] <pitti> Sweetshark: ah, so we do need Ubuntu changes?
[09:08] <pitti> Sweetshark: should I sync the package for now, or do you want to prepare a custom upload right away?
[09:08]  * Sweetshark jumps around happily and vainly takes a peek at his karma in launchpad.
[09:08] <pitti> Sweetshark: karma will take a bit to catch the upload
[09:09]  * Sweetshark wont get tired of hitting F5
[09:09] <pitti> hehe
[09:09] <seb128> Sweetshark, congrats!
[09:10] <dpm> kamstrup, got it, reading... :-)
[09:10] <Sweetshark> pitti: I would think I take a look the openoffice.org package. We already have the 3.3.0 transitionals in natty, they should do for now, right?
[09:11] <pitti> Sweetshark: I thought you dropped them from the current libo?
[09:11] <rodrigo_> morning
[09:11] <Sweetshark> so no need to sync openoffice.org from debian right now.
[09:11] <pitti> didrocks: ah, window decorations back to normal after full upgrade
[09:12] <pitti> Sweetshark: the old transitional packages from the previous version will be NBS, so it'll do for now
[09:12] <pitti> Sweetshark: oh, "NBS" -- means "not built from source"
[09:12] <pitti> Sweetshark: i. e. the .debs stay in the archive until we clean them up manually, but they do not have any source package which builds them
[09:12] <pitti> Sweetshark: we can't release with NBS packages, but for a limited time period they are ok
[09:12] <didrocks> pitti: nice :)
[09:12] <Sweetshark> pitti: understood.
[09:13] <pitti> Sweetshark: can you please also prepare a matching -l10n?
[09:13]  * pitti disappears for breakfast/shower for a bit
[09:15] <Sweetshark> pitti: will do
[09:19] <bryce_> didrocks, well won't do it for now.  It'd be fairly sadistic to break -nvidia now that we finally have a working driver
[09:20] <didrocks> bryce_: ok :)
[09:21] <bryce_> I think we'll have to digest the abi change at some point though.  But not right now.
[09:21] <didrocks> bryce_: oh btw, did you rememberabout my magnetic effect issue?
[09:21] <didrocks> bryce_: it seems I only have it when I have just one monitor connected
[09:21] <didrocks> bryce_: when I'm using twinview with two monitors, no issue…
[09:21] <bryce_> didrocks, I haven't forgotten, sorry it's still bugging you
[09:22] <bryce_> now that's plain old weird
[09:22] <didrocks> yeah
[09:22] <didrocks> I think we should wait for the next nvidia driver anyway
[09:22] <bryce_> didrocks, ok works for me
[09:23] <bryce_> you've been the only person noticing this bug so far, so might be something quirky with your hw
[09:23] <didrocks> bryce_: loicm as it as well
[09:23] <didrocks> has*
[09:24] <didrocks> and same for him, only with unity enabled
[09:24] <bryce_> didrocks, hm that makes it sound worse
[09:25] <didrocks> right
[09:25] <bryce_> didrocks, I think the next action for the bug is probably to forward it upstream
[09:25] <didrocks> bryce_: yeah, but they will ask to test with the latest nvidia first :-)
[09:25] <bryce_> as it sounds like we're out of ideas on things to try here
[09:25] <bryce_> didrocks, yep
[09:25] <bryce_> so, that's the pre-next action ;-)
[09:26] <didrocks> heh, right :-)
[09:26] <bryce_> meanwhile, you can play with wayland :-)
[09:27] <didrocks> bryce_: hum, I need a working unity you know :-)
[09:27] <didrocks> nice work on wayland btw!
[09:29] <bryce_> didrocks, I hope in natty+1 we maybe can get unity+nouveau to be not such a massive headache
[09:30] <bryce_> nouveau needs a lot of TLC, but maybe we can do it
[09:31] <didrocks> bryce_: oh? you think it's achievable?
[09:32] <bryce_> didrocks, I think it's a worthy goal for us X guys
[09:33] <didrocks> that would be excellent :)
[09:33] <bryce_> didrocks, we need to be able to provide you with a FOSS driver that doesn't suck
[09:34] <bryce_> anyway, nice chatting, cya later!
[09:34] <didrocks> bryce_: yeah, right now, there are a lot of mem leaks on nouveau if I understood correctly
[09:34] <didrocks> bryce_: have a nice evening :)
[09:43] <pitti> Sweetshark: btw, you need to close the human icons bug manually
[09:43] <pitti> (will give you more karma, yummy!)
[09:44] <pitti> Sweetshark: the usual way to do that is to write a line in the changelog like
[09:44] <pitti>  * Add back Human icons. (LP: #123456)
[09:44] <pitti> Sweetshark: the "LP: #xxxx" syntax is magic, and will cause LP to close the bug with the changelog on upload
[09:46] <Sweetshark> pitti: k
[09:46] <pitti> Sweetshark: oh, I'll change the seeds back from libreoffice-style-tango to libreoffice-style-human, ok?
[09:47] <pitti> Sweetshark: (do you know "seeds"?)
[09:48] <Sweetshark> no idea
[09:48] <dpm> The new shortcuts in the unity launcher are awesome! However, I've got a question: the old Super+W and Super+A shortcuts, have now been replaced to show all workspaces and the applications place, respectively. Does anyone know if there are new shortcuts for the old functionality (i.e. Super+w to show all windows in the current workspace, Super+a to show windows in all workspaces)?
[09:48] <pitti> Sweetshark: so, the "seeds" are a list of top-level packages which we want in a default install
[09:48] <Sweetshark> just guessing... just guessed right.
[09:48] <pitti> Sweetshark: a program "germinate" computes the full set of pacakges on the CDs from that, including the transitive dependencies
[09:48] <pitti> Sweetshark: i. e. it says which apps/pacakges we actually "want"
[09:49] <pitti> Sweetshark: we "want" empathy, we don't "want" libc6 or libreoffice-common
[09:49] <Sweetshark> pitti: does that include "suggests"?
[09:49] <pitti> Sweetshark: no, only depends and recommends
[09:49] <pitti> by definition, those ^ are installed by default, suggests aren't
[09:49] <pitti> Sweetshark: http://wiki.ubuntu.com/SeedManagement FYI
[09:50] <pitti> Sweetshark: oh argh, libo doesn't build -- it's waiting on an unavailable build dependency (this is called "depwait")
[09:50] <pitti> https://launchpad.net/ubuntu/+source/libreoffice/1:3.3.1-1ubuntu1/+buildjob/2285894
[09:50] <Sweetshark> ah, ok. Because the libreoffice-gtk integration suggests tango, which still makes IMHO ...
[09:50] <pitti> Sweetshark: apparently it grew a new build dependency to "epm", which is in universe
[09:50] <Sweetshark> meh
[09:50] <pitti> Sweetshark: do we really need epm?
[09:51] <Sweetshark> I just wondered myself.
[09:51] <pitti> Sweetshark: in this case there's two options: (1) drop the dependency, (2) move the package to main, which requires a thorough review, and will only be done for packages which we can sanely support
[09:51] <Sweetshark> we shouldnt, but maybe we do because of the way lo-build/debian does this.
[09:52] <pitti> Sweetshark: is it actually called during package build, or do you only need it to prepare the source pacakge?
[09:58] <Sweetshark> pitti: meh, thats another tricky one. We need epm for the smoketest. And there is code that disables smoketest on buildd builds: that is, it the control file is build on a buildd build, the var ON_BUILDD is set so that rules would generate a control file without epm and without smoketest.
[09:58] <rodrigo_> can someone review/merge/upload this -> https://code.launchpad.net/~rodrigo-moya/ubuntu/natty/gnome-settings-daemon/fix-666806/+merge/51177 please?
[09:59] <pitti> Sweetshark: hang on, it regenerates debian/control on the buildds? uh
[09:59] <Sweetshark> pitti: I wonder how that should work, generating the control file on buildds.
[09:59] <pitti> Sweetshark: if we won't need it anyway then, perhaps the simplest solution is to just drop it
[09:59] <pitti> Sweetshark: it generally doesn't; it's a very bad practice
[10:00] <Sweetshark> pitti: right, thats strange.
[10:00] <pitti> rodrigo_: will do
[10:00] <seb128> pitti, can you upgrade ppa builds score?
[10:00] <rodrigo_> pitti, thanks, it's from the patch pilot thing
[10:01] <seb128> pitti, or does score only work for the main builders?
[10:01] <pitti> seb128: yes
[10:01] <pitti> seb128: and no
[10:01] <seb128> pitti, can you raise the score on https://edge.launchpad.net/~ubuntu-desktop/+archive/ppa/+buildjob/2285941 ?
[10:01] <seb128> pitti, compiz's update crash on start here
[10:01] <Sweetshark> I could just regenerate the control file with "./debian/rules control ON_BUILDD=y", edit the changelog to ubuntu2 and reupload ...
[10:01] <pitti> seb128: done
[10:01] <seb128> pitti, I've uploaded a debug version to the ppa
[10:01] <seb128> pitti, thanks
[10:02] <pitti> Sweetshark: heh, sure
[10:02] <pitti> Sweetshark: btw, you built the previous package with '-sa', right?
[10:02] <pitti> Sweetshark: as we now already have the orig tarballs in Launchpad (and in the PPA), you don't need -sa any more; will be a much smaller/quicker upload then
[10:03] <Sweetshark> i still have not got my head around all the switches. I guess I did a debuild -S.
[10:03] <pitti> Sweetshark: bug 696527 should be "fix released"
[10:03] <ubot2> Launchpad bug 696527 in libreoffice "LibreOffice - Human icons theme disabled, patch needs an update" [High,Fix committed] https://launchpad.net/bugs/696527
[10:04] <pitti> Sweetshark: ok, so debuild -S was clever enough to include the orig then; nevermind
[10:04] <pitti> Sweetshark: "fix committed" is the right state when you put a fix into some git or bzr, but haven't uplaoded yet
[10:04] <pitti> Sweetshark: (sorry about all those new things today..)
[10:05] <Sweetshark> pitti: well, that is exactly the state currently: fixed, but not uploaded
[10:05] <pitti> Sweetshark: hmkay, due to the current "doesn't build"
[10:06] <Sweetshark> pitti: or could I upload a fixed 1ubuntu1? Probably not.
[10:07] <pitti> Sweetshark: no
[10:07] <pitti> once the source is in LP, it is set in stone
[10:07] <Sweetshark> k
[10:07] <pitti> Sweetshark: fortunately there is a sufficient amount of natural numbers :)
[10:16] <htorque> hello everyone! the gnome-terminal can only be resized in fixed-sized steps, thus it's not working well together with the grid plugin. is this something worth a bug report or rather something we have to live with?
[10:18] <Sweetshark> pitti: should use debuild -S again, or is there something better suited?
[10:20] <pitti> Sweetshark: no, that's _the_ command to build a source package (unless you use git-buildpackage and friends)
[10:20] <pitti> htorque: here I can resize it in the steps of the size of a letter -- that seems right to me? you certainly don't want to see half a line somewhere
[10:22] <Sweetshark> pitti: should upload to the ppa again? im not allowed to main?
[10:23] <htorque> pitti: right, it makes sense, it just looks odd when eg. splitting two gnome-terminals to each half of the desktop (you'll get empty space in between)
[10:23] <pitti> Sweetshark: I think the quickest would be if you could scp debian.tar, dsc, and source.changes to chinstrap
[10:24] <htorque> pitti: if you maximize a gnome-terminal, you don't see half lines at the bottom
[10:24] <pitti> Sweetshark: I'll sign the changes there, and upload
[10:24] <pitti> htorque: ah, I never actually wondered how it does that; perhaps just coincidence that it usually looks like it'd just fit
[10:28] <htorque> here's what i'm talking about: http://img.xrmb2.net/images/841674.png - it's not the end of the world, but it's "natty-like" if other windows do completely extent to the borders :)
[10:29] <htorque> *not "natty-like"
[10:31] <Sweetshark> pitti: files are in my ${HOME} on chinstrap, where should I move them?
[10:32] <pitti> Sweetshark: that's fine
[10:32] <seb128> doh
[10:32] <seb128> why can't intel write a driver which doesn't crash when you vt switch
[10:32] <pitti> seb128: you missed the debian.tar.gz
[10:32] <seb128> ;-)
[10:32] <pitti> sorry
[10:32] <seb128> pitti, what?
[10:32] <pitti> Sweetshark: you missed the debian.tar.gz
[10:33] <seb128> oh ok
[10:33] <pitti> Sweetshark: (and the source.build isn't necessary)
[10:34] <pitti> TheMuso: can you please have a look at bug 681412? I've got a question for you there; thanks!
[10:34] <ubot2> Launchpad bug 681412 in at-spi "Can not enter password for Administrative tasks using Onboard Keyboard" [Medium,Triaged] https://launchpad.net/bugs/681412
[10:34] <Sweetshark> pitti: now its there
[10:36] <pitti> Sweetshark: sent launchpadwards
[10:36] <pitti> Sweetshark: thanks!
[10:40] <pitti> dbarth, didrocks: do you know whether https://launchpad.net/ubuntu/+spec/packageselection-dx-n-unity-a11y is up to date? it seems quite behind
[10:41] <didrocks> pitti: let me look
[10:41] <didrocks> I would say atk isn't finished, so all are in progress as it should
[10:41] <didrocks> (well, I mean, reflecting the reality of the code)
[10:42] <pitti> so should we move that to beta-1 then?
[10:42] <pitti> a3 freeze is next Tuesday, seems unlikely to land before that?
[10:43] <didrocks> pitti: still some atk thing will land on monday, so maybe waiting for that?
[10:43] <pitti> ok
[10:43] <didrocks> btw, would be nice if someone can tackle bug #723782
[10:43] <ubot2> Launchpad bug 723782 in gnome-session "Finalize gnome-session fallback detection" [Undecided,New] https://launchpad.net/bugs/723782
[10:44] <pitti> I'm trying to clean up http://people.canonical.com/~platform/workitems/natty/canonical-desktop-team-natty-alpha-3.html as that is despeartely behind
[10:44] <didrocks> I tried to describe everything there
[10:44] <didrocks> as I certainly won't have the time to do it to focus on unity hacking
[10:45] <pitti> didrocks: ok, will have a look at find someone
[10:46] <didrocks> pitti: thanks a lot!
[10:46] <didrocks> if it needs more explanation, I can give them
[10:51] <dbarth> pitti: i'm updating the bp at the moment, this one is not up to date thankfully
[10:51] <pitti> dbarth: *phew* :)
[10:51] <didrocks> dbarth: the branches didn't land
[10:51] <didrocks> just some part of them did
[10:53] <pitti> didrocks: will Alt+F2 land for a3, or should we move to b1?
[10:53] <didrocks> pitti: I moved it already
[10:54] <didrocks> pitti: I'll start working on it after alpha3. I'm tackling today and Monday unity bugs for alpha3
[10:54] <didrocks> pitti: I've refreshed quite a few WI
[10:54] <pitti> ah, cheers
[10:55] <didrocks> alt + F2 will be tricky though, as I have to learn vala very quickly and how to use dee :)
[10:56] <dbarth> didrocks: if the homescreen works well, alt-f2 should be mapped to it instead
[10:56] <didrocks> dbarth: for alpha3 as a workaround? it can
[10:57] <didrocks> dbarth: not for the definitive solution then
[10:57] <pitti> Sweetshark: https://launchpad.net/ubuntu/+source/libreoffice/1:3.3.1-1ubuntu2/+buildjob/2285989 :/
[10:57] <seb128> pitti, you got email
[10:57] <pitti> Sweetshark: seems this got qutie a lot of new dependencies :/
[10:57] <pitti> Sweetshark: to avoid more upload/fix cycles, coudl you please install ubuntu-dev-tools, and run "check-mir" once? and then pastebin the result?
[10:58] <pitti> Sweetshark: run in the unpacked libo source tree
[10:58] <Sweetshark> pitti: meh, I know my mistake
[10:59] <pitti> seb128: cheers; so I guess we postone
[10:59] <seb128> pitti, it's really a shame
[10:59] <pitti> Sweetshark: oh, lucene isn't necessary? or do we need a mir?
[10:59] <seb128> pitti, not sure what we have now is better security wise
[10:59] <seb128> it's just that it got in before there was security reviews
[11:00] <pitti> might be worth talkign to kees about it; if it's no worse, then this shoudln't be a blocker
[11:00] <seb128> so we have a non maintaining buggy choice instead of a working one just because the new one has issues
[11:00] <Sweetshark> pitti: I am rebooted to maverick as I did want to go deaf by a nonthrottled nvidia fan and didnt DISTREL=natty when creating the control file :/
[11:00] <seb128> but the old one is not any better...
[11:00] <seb128> pitti, right, will do that when he's online later today
[11:00] <pitti> seb128: ok, cheers
[11:01] <pitti> Sweetshark: heh; so, take III
[11:01] <pitti> Sweetshark: just to be sure, after you regenerated control, could you please still run check-mir?
[11:02] <chrisccoulson> good morning everyone
[11:02] <pitti> hey chrisccoulson
[11:02] <chrisccoulson> didrocks, you didn't see that i pushed a commit to compiz-plugins-main ;)
[11:02] <chrisccoulson> i was going to just upload it until i realised that i couldn't
[11:02] <didrocks> chrisccoulson: oh? you uploaded it?
[11:02] <didrocks> chrisccoulson: oh bad…
[11:03] <didrocks> chrisccoulson: weird, bzr didn't complain on bzr pull and bzr push…
[11:03] <chrisccoulson> hmmm :/
[11:03] <didrocks> chrisccoulson: sorry for that, it would have been cool if you could have uploaded that!
[11:03] <didrocks> chrisccoulson: you need to apply for core-dev :)
[11:03] <chrisccoulson> heh :)
[11:09] <pitti> dpm: hey, how are yuou?
[11:09] <pitti> dpm: OOI, are there any news wrt. "Talk to Mozilla people about using user provided translations from Launchpad"?
[11:11] <dpm> pitti, doing well, thanks. I'll see if I can get to it today. I wrote the e-mail a while ago, and sent it for review to chriscoulson and rickspencer3. I just need to rewrite it to factor in the recommendations from Rick re: the Mozilla agreement
[11:12] <pitti> ah, thanks
[11:16] <Sweetshark> pitti: I still get epm as dep.
[11:16] <pitti> Sweetshark: hm, I thought that got dropped with ON_BUILDD=y?
[11:19] <rodrigo_> there are several natty packages that need a rebuild with the new GTK3 package names, is anyone working on those?
[11:19] <Sweetshark> pitti: the if is a bit deeper nested, so I got it wrong. If we have java enabled (we do) and have no openjdk (but we have it), the smoketest would be disabled on buildd, but with openjdk we have the smoketest enabled still.
[11:20] <seb128> rodrigo_, which ones?
[11:20] <rodrigo_> seb128, let me pastebin
[11:21] <pitti> Sweetshark: would it be adequate to disable the smoketests on the buildds regardless?
[11:21] <rodrigo_> seb128, http://pastebin.com/qTuMHhuc <- some of them are from the gnome3 ppa, so ignore those
[11:22] <Sweetshark> pitti: not really, as you dont really want a buildd and non-buildd build to have different deps. But I could disable the smoketest for natty by default for now.
[11:22] <rodrigo_> but gnome-applets, indicator*, etc
[11:23] <pitti> Sweetshark: or that
[11:23] <rodrigo_> seb128, I'm preparing a branch for them, if nobody is working on it
[11:23] <pitti> Sweetshark: coudl it be changed to "if epm is installed, run the smoketest"?
[11:24] <seb128> rodrigo_, not sure what your issue is coming from
[11:24] <rodrigo_> oh wait, gnome-applets doesn't need it
[11:24] <seb128> rodrigo_, I just checked on my natty system, only the new libnotify and mousetweak use the old libgtk3 naming
[11:24] <rodrigo_> so I guess it is because of some other dependency
[11:24] <rodrigo_> I'll check on my vm
[11:25] <seb128> rodrigo_, http://paste.ubuntu.com/572136/
[11:25] <seb128> rodrigo_, on a natty system
[11:25] <rodrigo_> yes, I guess it's because of some other dependency
[11:26]  * rodrigo_ looks
[11:27] <pitti> rodrigo_, seb128: do you know whether bug 710901 is fixed in gnome 3? i. e. should we report this upstream, or investigate backporting the gnome 3 yelp?
[11:27] <ubot2> Launchpad bug 710901 in yelp "search not implemented" [High,Triaged] https://launchpad.net/bugs/710901
[11:27] <rodrigo_> pitti, hmm, let me test it
[11:28] <seb128> pitti, we have the GNOME3 version in natty...
[11:28] <pitti> oh
[11:28] <seb128> pitti, it has just patched to build with gtk2
[11:28] <Sweetshark> pitti: later, as currently there is just one var RUN_SMOKETEST, that toggles everything. I would have to do a "even if RUN_SMOKETEST is false, still try one if you find epm" and for that I would have to check if there are other vaild reasons that disable the smoketest. For example the smoketest is disabled on i386/armel because it seems to currently fail there although the product is fine ...
[11:29] <rodrigo_> pitti: seems to not work for me, but that doesn't mean anything, since I'm now with a half-updated system
[11:29] <pitti> Sweetshark: ok, so maybe better disable it by default, and provide an easy way to run it manually locally?
[11:30] <pitti> rodrigo_: I confirmed the bug; I overlooked that we already have the gnome 3 version
[11:30] <rodrigo_> ok
[11:30] <pitti> rodrigo_: would you have some time to report this upstream and perhaps check if it's a missing feature or perhaps just a simple bug?
[11:30] <Sweetshark> pitti: It is pretty easy to run manually, if you know how to find it ;)
[11:31] <pitti> Sweetshark: you know it, which is sufficient from my POV :)
[11:33]  * pitti -> supermarket, bbl
[11:33]  * Sweetshark wonders however, how 3.3.0 for natty did build without epm ...
[12:14] <rodrigo_> is lp too busy? it's not building anything new in the gnome3 ppa
[12:14] <rodrigo_> pitti, yes, doing it now
[12:16] <dpm> pitti chrisccoulson, re: Natty langpacks, do you think we could look at them next week to see if po2xpi builds the Firefox translations correctly? It would be great if we could ship FF translations in A3
[12:16] <dpm> I'll be more than happy to help
[12:16] <chrisccoulson> oh, we're not shipping translations yet?
[12:16] <chrisccoulson> i didn't realise :(
[12:16] <chrisccoulson> i thought that was solved already ;)
[12:17] <dpm> chrisccoulson, you should read your inbox :P
[12:17] <chrisccoulson> heh
[12:17] <dpm> :)
[12:18] <chrisccoulson> dpm - are you referring to bug 715733 ?
[12:18] <ubot2> Launchpad bug 715733 in po2xpi "XPI files are not correctly built for whitelisted languages" [Undecided,New] https://launchpad.net/bugs/715733
[12:21] <dpm> chrisccoulson, yeah, that was one thing we encountered while creating the Lucid langpacks. It happened to be an LP bug, which is now fixed, so I've jsut marked that one as Invalid. For Natty, I think it's just a matter of testing if running the latest po2xpi version which included danilo's changes to adapt to the new upstream xpi layout produces valid FF translations
[12:23] <dpm> this can be done by downloading the FF translations from LP and running po2xpi locally in the same way it is invoked by langpack-o-matic, and see if the produced language tarballs look ok
[12:24] <rodrigo_> pitti, hmm, git seems to have it implemented
[12:26] <rodrigo_> pitti, can't install right now the latest yelp because of webkit broken package, so you see the same message in the terminal than in the bug?
[12:38] <pitti> dpm: yeah, I was planning to
[12:40] <GunnarHj> pitti: Hello, were you notified about this build failure: https://launchpad.net/ubuntu/+source/gdm/2.32.0-0ubuntu9/+buildjob/2282264 ?
[12:42] <pitti> GunnarHj: hi
[12:42] <pitti> GunnarHj: I wasn't actually, because your name is in the changelog; looking
[12:42] <pitti> GunnarHj: seems transient, I'll retry the build
[12:42] <GunnarHj> pitti: Ok.
[12:43] <pitti> GunnarHj: oh, it was already apparently
[12:43] <pitti> ah, no, ubuntu9, not ubuntu8, sorry
[12:44] <rodrigo_> pitti, ok, the bug reporter is running 2.91.10, 2.91.90 does include the implementation, so should I submit a branch for upgrading it to 2.91.90?
[12:44] <pitti> GunnarHj: ah, that's powerpc; i386/amd64/armel built fine
[12:45] <pitti> rodrigo_: that'd be nice; we don't want to ship with a prerelease anyway, but upgrade to 3.0 final eventually
[12:45] <pitti> rodrigo_: thanks!
[12:45] <rodrigo_> pitti, ok, submitting in a while
[12:45] <pitti> rodrigo_: I assigned the bug to you
[12:45] <rodrigo_> ok
[12:45] <GunnarHj> pitti: Right - for a while I was wondering where you read. ;-)
[12:46] <pitti> GunnarHj: I have a script to retry a package build on all arches, and it apparently picked the wrong version
[12:46] <Sweetshark> pitti: check-mir chokes on the LO deps :(
[12:46] <pitti> \o/ empathy is back
[12:46] <pitti> Sweetshark: what else is missing?
[12:46] <pitti> Sweetshark: or do you mean it crashes?
[12:47] <Sweetshark> it crashes
[12:47] <Sweetshark> failing to parse the deps
[12:47] <rodrigo_> pitti, oh, robert_ancell already added 2.91.90 to lp:~ubuntu-desktop/yelp/ubuntu, building it now and if it builds, I guess you can submit that
[12:47] <GunnarHj> pitti: Special script, ok, I see.
[12:48] <pitti> rodrigo_: cool
[12:48] <pitti> Sweetshark: ah, output?
[12:49] <rodrigo_> pitti, well, can't build because of broken libwebkitgtk-1.0-0 :(
[12:49] <Sweetshark> pitti: https://pastebin.canonical.com/43948/
[12:49] <rodrigo_> is libwebkitgtk-1.0-0 broken for anyone else, or is it just me?
[12:50] <pitti> Sweetshark: uh, that's in python-apt, not even in check-mir itself
[12:50] <pitti> rodrigo_: how so?
[12:51] <rodrigo_> pitti,  libwebkitgtk-dev : Depends: libwebkitgtk-1.0-0 (= 1.3.12-0ubuntu1) but it is not going to be installed
[12:51] <pitti> Sweetshark: the Depends: line looks fine to me, hmm
[12:51] <pitti> rodrigo_: hm, just installed libwebkitgtk-dev on amd64, works fine here
[12:52] <pitti> rodrigo_: rodrigo_ do you have libwebkitgtk-1.0-0 installed? which versino?
[12:52] <rodrigo_> pitti, no, not installed
[12:52] <seb128> rodrigo_, what does apt-cache policy libwebkitgtk-1.0-0 says
[12:52] <pitti> rodrigo_: what's "apt-cache policy libwebkitgtk-1.0-0" for you?
[12:53]  * pitti ^5s seb128 and takes a penalty card for snapping
[12:53] <rodrigo_> libwebkitgtk-1.0-0:
[12:53] <rodrigo_>   Installed: (none)
[12:53] <rodrigo_>   Candidate: 1.3.12-0ubuntu1
[12:53] <rodrigo_>   Version table:
[12:53] <rodrigo_>      1.3.12-0ubuntu1 0
[12:53] <rodrigo_>         500 http://archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
[12:53] <seb128> pitti, ;-)
[12:53] <rodrigo_> hmm, I've got no libwebkitgtk packages installed
[12:53] <pitti> rodrigo_: what does this say: sudo apt-get install libwebkitgtk-1.0-0 libwebkitgtk-dev
[12:53] <pitti> it should point out the error more clearly
[12:53] <Sweetshark> pitti: it seems not to like the "[!armel]" stuff
[12:54] <pitti> Sweetshark: in your current control, is lucene and epm gone now?
[12:54] <pitti> Sweetshark: ah, that's be an mvo bug then
[12:54] <rodrigo_> pitti, complains about -common, but 'sudo apt-get install libwebkitgtk-1.0-0 libwebkitgtk-dev libwebkitgtk-1.0-common' works
[12:54] <pitti> werid
[12:54] <rodrigo_> it uninstalls all the libubuntuone packages
[12:54] <pitti> and my typing sucks today
[12:54] <rodrigo_> that's why it was complaining
[12:54]  * rodrigo_ installs
[12:54] <rodrigo_> The following packages will be REMOVED:
[12:54] <rodrigo_>   banshee-extension-ubuntuonemusicstore gir1.2-ubuntuone-1.0
[12:54] <rodrigo_>   libubuntuone-1.0-1 libubuntuone-dev libubuntuone1.0-cil
[12:54] <rodrigo_>   libubuntuone1.0-cil-dev libwebkit-1.0-2 libwebkit-1.0-common libwebkit-dev
[12:55] <rodrigo_> pitti, ok, building the package now
[12:55] <rodrigo_> pitti, seb128: you don't have the u1 packages installed I guess?
[12:55] <pitti> rodrigo_: ah, right
[12:56] <rodrigo_> so, libwebkitgtk is the new name for the packages, right?
[12:56] <pitti> I think they got removed yesterday during dist-upgrade, and I accepted (deliberately)
[12:56] <rodrigo_> :)
[12:56] <pitti> rodrigo_: seems so, yes
[12:57] <rodrigo_> ok, the u1 packages need an upgrade then
[12:58] <seb128> go pitti! \o/
[12:59] <Sweetshark> pitti: with a :%s/\[\!armel\]//g on control in vim it only finds this:
[12:59] <Sweetshark> pitti: https://pastebin.canonical.com/43952
[12:59] <pitti> seb128: ?
[12:59] <seb128> pitti, (I was going to ask if we should try to get the new policykit but I noticed you synced it)
[12:59] <pitti> Sweetshark: cool, that looks fine; go!
[12:59] <pitti> seb128: :)
[13:00] <Sweetshark> pitti: go what? dput it to main and be cruelly denied?
[13:01]  * Sweetshark makes sure to update the copy on chinstrap
[13:01] <pitti> Sweetshark: I mean "let's get this uploaded" :)
[13:01] <pitti> right, chinstrap -> pitti -> dput route again
[13:01]  * pitti thinks this is all just Sweetshark's s3kr1t plan to get 10.000 upload karma in one day
[13:02] <Sweetshark> *hrhr*
[13:02]  * Sweetshark puts finger to the edge of his mouth: ONE MILLION!11!
[13:05] <pitti> uuh /me bows in awe
[13:05] <pitti> Sweetshark: if it's proportional to package size.. :)
[13:07] <Sweetshark> well, since I dput via you arent you stealing all that karma anyway?
[13:09] <Sweetshark> pitti: you should find the files on chinstrap
[13:11] <pitti> Sweetshark: no, I shouldn't
[13:11] <pitti> Sweetshark: I already get tons of false karma because it puts the langpack uploads on my account
[13:12] <pitti> LibO, Take III
[13:13]  * Sweetshark prays for it to work this time.
[13:13] <Sweetshark> ... and tags ubuntu3.
[13:15] <Sweetshark> I wonder what _rene_ will say later about me spamming the debian repo with ubuntu releases.
[13:19] <pitti> Sweetshark: don't you only apply the tags to the ubuntu branch?
[13:19] <pitti> chrisccoulson: can you please help my brain with an update of bug 663294? does this really affect our i386 firefox package, or only if you enable some build options?
[13:19] <ubot2> Launchpad bug 663294 in gcc-4.5 "Firefox built with gcc-4.5 is a non-starter on i386 with -pie" [High,Triaged] https://launchpad.net/bugs/663294
[13:19] <mterry> seb128, tedg is gone today?  when is he back?
[13:20] <seb128> mterry, tuesday
[13:20] <seb128> mterry, he's at scale or something
[13:20] <mterry> seb128, hrm, the datetime prefs didn't get merged because I forgot to bzr add an image file.  I guess we'll do a FF for it
[13:20] <seb128> mterry, hey btw
[13:20] <mterry> FFe that is
[13:20] <chrisccoulson> pitti - it affects the i386 package if we build with -pie (which we did in maverick, and the security team want)
[13:20] <seb128> mterry, talk to dbarth when he's back from lunch, he was talking to klatimmer about that
[13:20] <chrisccoulson> i've disabled it for now though
[13:21] <mterry> seb128, k
[13:21] <seb128> mterry, I would recommend you do a trunk snapshot with your work distro patched today if you can
[13:21] <pitti> Sweetshark: do you know what will happen with oo.o-hyphenation & co? will these be renamed to libo as well?
[13:21] <Sweetshark> pitti: yes, do. but they will show up on the summary page (and on the SCM mailing list) anyway.
[13:21] <seb128> mterry, btw I assigned you a new crasher from yesterday's ted's tarballs
[13:21] <seb128> mterry, not sure if you saw
[13:22] <pitti> Sweetshark: wohoo, building
[13:22] <seb128> mterry, would be nice to try to handle that today as well if you can, with some luck it's easy to fix
[13:22] <mterry> seb128, would still require an FFe, though eh?  And it's a 6k patch, with data files
[13:22] <mterry> 6k line patch that is
[13:22] <mterry> seb128, I saw, I can look at it
[13:22] <pitti> chrisccoulson: doesn't seem realistic for a3, does it? is there any progress on that actually (upstream?)
[13:22] <seb128> mterry, right, but I think the ffe should be easy to get
[13:23] <seb128> mterry, it's just a matter of asking and getting it approved
[13:23] <seb128> mterry, but we can't wait on ted to be back if we want it in a3
[13:23] <Sweetshark> pitti: I have not checked those yet. Those are likely in the *-10n* package right?
[13:23] <chrisccoulson> pitti - no, that's definitely not going to happen for a3. i will look at it again next week though
[13:23] <pitti> Sweetshark: no, these are a separate source
[13:23] <mterry> seb128, ah...  hrm.  OK.  I'll work on that today
[13:23] <mterry> stupid 'bzr add' mistakes....
[13:25] <dbarth> mterry: hi, so you have the missing file?
[13:25] <mterry> dbarth, yeah, updated branch
[13:25] <dbarth> mterry: what's blocking otherwise, a code review? do you want me to get that arranged for you to be able to land the code?
[13:25] <cyphermox> hi
[13:26] <mterry> dbarth, I don't know how much tedg was able to review before giving up on the image.  It's a big patch (6k lines)
[13:26] <dbarth> yeah, i saw
[13:26] <dbarth> i don't think he fully reviewed it
[13:26] <dbarth> he probably wanted to get it running first
[13:26] <seb128> mterry, seems ted worked later yesterday seeing when he did this review
[13:26] <mterry> Yeah.
[13:26] <seb128> mterry, there was a stack of libdbusmenu and other indicator changes to land
[13:27] <dbarth> kamstrup: ping? do you have time for a code review for mterry here?
[13:27] <mterry> dbarth, so a review would be good
[13:27] <seb128> mterry, so I wouldn't be surprised if he didn't review much yours
[13:27] <mterry> seb128, did they not land?
[13:27] <seb128> mterry, they did but it seems ted got his day full with those
[13:27] <mterry> i see
[13:27] <seb128> mterry, so it's likely yours came as a end of day thing
[13:27] <mterry> sure
[13:28] <seb128> mterry, can you start on the crasher while they start the review etc?
[13:28] <dbarth> yeah, he reviewed it pretty late at night and he was probably packaging up for scale
[13:28] <mterry> seb128, yup
[13:28] <seb128> mterry, ideally we would have an upload for monday for datetime, today better if you can
[13:29] <Sweetshark> dbarth: Feel free to comment about my stupid ideas regarding the lo-menubar btw ;-)
[13:30] <seb128> Sweetshark, what idea did you have?
[13:30] <dbarth> Sweetshark: eh, just reading now
[13:30] <chrisccoulson> pitti - is there any way to stop a user from reporting a bug with apport-bug if we detect certain conditions exist on the system?
[13:31] <chrisccoulson> ie, i want my apport hook to stop and tell the user that their system is broken
[13:31] <pitti> chrisccoulson: yes, you can check for the conditions in the package hook, and then set report['UnreportableReason']
[13:31] <pitti> chrisccoulson: grep for Reason in /usr/share/apport/package-hooks, plenty of examples
[13:31] <chrisccoulson> pitti - excellent, thanks!
[13:31] <pitti> chrisccoulson: or have a look at the -- shock!! -- documentation: /usr/share/doc/apport/package-hooks.txt.gz
[13:31] <chrisccoulson> heh :)
[13:32] <chrisccoulson> i thought it would be quicker to ask you first ;)
[13:32] <pitti> oh, that's fine
[13:32] <chrisccoulson> i'm going to reduce the firefox bug count by quite a bit :)
[13:32]  * pitti just is proud that he actually took the time to write some docs about this stuff
[13:33] <pitti> chrisccoulson: what are you going to check for? grepping for "pr0n" in the history? :-)
[13:33] <chrisccoulson> pitti - not quite ;)
[13:33] <chrisccoulson> i want to check if /usr/bin/firefox has been diverted with dpkg-divert
[13:33] <Sweetshark> seb128: LO and Nattys release schedules working together -- and make lo-menubar fit somewhere inbetween there ..
[13:34] <chrisccoulson> installing packages from ubuntuzilla does that, and it's our number 1 reported bug
[13:34] <pitti> chrisccoulson: sounds great
[13:34] <chrisccoulson> i've just added some cleanup code to our postinst script to fix peoples installs
[13:34] <seb128> Sweetshark, hum, aren't those scheduled fixed for a while? ;-)
[13:34] <seb128> schedules
[13:34] <seb128> Sweetshark, the lo-menubar was going to land this week it seems
[13:34] <seb128> kenvandine was on it yesterday
[13:39] <dbarth> Sweetshark: but so 3.4 is not for natty, right?
[13:40] <dbarth> i've asked aruiz to join
[13:41] <Sweetshark> dbarth: no, 3.4 is not for natty as it final is scheduled after the natty release.
[13:42] <dbarth> i'd rather try to get a module running on the version shipped with natty
[13:42] <aruiz> Sweetshark, dbarth, hey hey
[13:42] <dbarth> as i understand getting updates is what the interface doesn't provide
[13:42] <dbarth> aruiz: hi
[13:42] <aruiz> dbarth, yeah, that's the main problem, but there are others issues that it might not be possible to solve
[13:43] <Sweetshark> dbarth: yes, there are some menus that are being populated the moment they popup, so their content is not static
[13:43] <dbarth> polling for changes on user events may be an acceptable solution
[13:43] <dbarth> ie, it's not "dumb" polling
[13:43] <aruiz> dbarth, that's what ted suggested
[13:43] <mterry> seb128, see, I've already fixed the crash
[13:43] <dbarth> ah, see ;)
[13:43] <aruiz> we can use the on-about-to-show event on the appmenu indicator
[13:44] <mterry> seb128, and there's still 3 more hours!
[13:44] <aruiz> dbarth, the problem is that on slow machines it wouldn't work properly
[13:44] <dbarth> ah, ok, in this sense
[13:44] <seb128> mterry, excellent
[13:44] <seb128> mterry, do you need sponsoring for it?
[13:44] <mterry> seb128, only if it's not in desktop suite
[13:44]  * mterry checks
[13:45] <aruiz> dbarth, other than that, there are some minor issues, things won't be perfect but they'll kinda work
[13:46] <mterry> seb128, I'm good
[13:46] <aruiz> I'm working on the shortcuts at the moment
[13:46] <dbarth> ok
[13:46] <seb128> mterry, great! ;-)
[13:46] <seb128> mterry, don't wait on ted's review since he's not there, just upload to natty
[13:46] <dbarth> so, yeah, i'd prefer to secure a solution that would work as a module on the stable release shipping in natty
[13:47] <aruiz> dbarth, I do prefer that as well, from the perspective that I want to deliver something you're happy with within schedule, but keep in mind that there might be some things that will not be possible
[13:47] <dbarth> i feel that the workarounds required for doing that should be adressed in parallel, or post release and target 3.4+
[13:48] <aruiz> dbarth, I'm leaning towards pushing as far as I can with what's available through UNO for natty
[13:48] <aruiz> and making it as decent as possible
[13:49] <dbarth> aruiz: agreed
[13:49] <aruiz> dbarth, I can certainly do that _if_ I don't have to deal with the insides of openoffice in this contract, and if it's okay to ship it even if it's not perfect
[13:50] <cdbs> seb128: sorry for that upload, I should have unsubscribed sponsors instead of just leaving the bug like that
[13:50] <aruiz> dbarth, in the long run I agree with Bjoern's approach
[13:51] <aruiz> Sweetshark, does this make sense to you?
[13:52] <Sweetshark> dbarth aruiz: understood. My point about upstreaming the stuff to master (3.4+) is mostly so that we try to do that as soon as the suff is reasonably stable. Squeezing it in on the last day before (upstream) feature freeze might get a bit hectic.
[13:52] <aruiz> Sweetshark, if I have some time before we try to integrate it, I can clean up the code a bit and document things further, that'll make your work easier if you take it from there
[13:53] <Sweetshark> aruiz dbarth: So going with a module/extension approach for 3.3 which might not be able to satisfy every detail, and going upstream for 3.4 to get the rest fixed sounds good to me.
[13:54] <aruiz> we're all on board
[13:54] <aruiz> nice!
[13:56] <Sweetshark> aruiz: I already had a peek at the repo, the LO stuff was easy to understand, so I would rather need help on the dbus stuff (but that is nothing a little bit of tutorial reading would not fix)
[13:56] <dbarth> Sweetshark: ok, so we're all on the same page
[13:56] <Sweetshark> dbarth aruiz: yep, great!
[13:56] <aruiz> Sweetshark, the dbus stuff is pretty straightforward, I will assist you with that
[13:57] <aruiz> Sweetshark, installing d-feet might help you, it's an instrospection tool for dbus
[13:57] <Sweetshark> aruiz: The minds of longtime LO/OOo hackers can be rather spoiled ;)
[13:58] <aruiz> Sweetshark, tell me about it
[13:58] <aruiz> X-)
[13:58] <Sweetshark> hrhr
[13:59]  * Sweetshark will have a look at d-feet soon
[13:59] <mterry> seb128, OK, did you have other crashers queued up for me?
[13:59] <aruiz> Sweetshark, :-)
[13:59] <seb128> mterry, in indicator-applications? no
[13:59] <mterry> seb128, but elsewhere, I remember you talking about not assigning stuff.
[14:00] <mterry> seb128, did that theme_changed_cb one get fixed?
[14:00] <seb128> mterry, there was some libdbusmenu crashers but quite some fixes landed this week so we need to see how that settle
[14:00] <seb128> oh no
[14:00] <seb128> mterry, https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/708188
[14:00] <ubot2> Launchpad bug 708188 in indicator-application "softwares using libappindicator crash with SIGSEGV in theme_changed_cb()" [High,Triaged]
[14:00] <seb128> mterry, right, this one remains as something to fix for natty
[14:01] <seb128> mterry, you might want to sort indicator-datetime today and switch to crash fixes next week rather
[14:01] <mterry> seb128, sure
[14:01] <seb128> mterry, well, up to you, but I think those can wait a bit, it will also give us the w.e to see what crashes remaining after this week updates
[14:02] <mterry> dbarth, did you find a reviewer for my branch?
[14:02] <seb128> let's get the feature freeze rush to settle and see where we stand
[14:04] <seb128> kenvandine, howdy
[14:06] <dbarth> pfff, my usb headset is not detected anymore
[14:07] <dbarth> oops, wrong channel
[14:09] <chrisccoulson> w00t, just closed out lots of firefox bugs \o/
[14:12] <nessita> hello everyone. QUestion: I made 2 releases yesterday using lp-project-upload, but none is appearing in Launchpad.Any idea how to debug what's wrong?
[14:13] <nessita> pitti: maybe you have a hint about ^?
[14:13] <nessita> (hi btw!)
[14:15] <pitti> hey nessita
[14:16] <pitti> nessita: the script didn't error out, I figure?
[14:16] <nessita> not in stdout/stderr at least. Is there any log file I can look at?
[14:17] <seb128> nessita, hey
[14:18] <nessita> hi seb128, how are you?
[14:18] <seb128> nessita, I'm fine thanks, how are you?
[14:18] <nessita> pretty good! happy that is Friday ;-)
[14:18] <seb128> ;-)
[14:19] <seb128> rodrigo_, does the nautilus patch need a leak fix? cf cosimo comment
[14:20] <seb128> pitti, bah the i386 retracer crashed again, I cleaned in .launchpadlib and restarted, let's see
[14:20] <pitti> hmpf
[14:20] <seb128> ok, works again
[14:20] <nessita> pitti: I ran it twice for the control panel, and the second time it didn't ask if I wanted to create the milestone. So that indicates that the milestone was created the first time, but is not showing in LP either
[14:20] <pitti> seb128: we might just put the rm -r into the cronjob..
[14:20] <seb128> that's a weird issue
[14:20] <seb128> pitti, right, if it keeps doing that we should
[14:20] <pitti> seb128: I wonder if something in the cache file suddenly became arch specific
[14:21] <seb128> well it's a small issue but it's annoying
[14:21] <seb128> pitti, could be
[14:21] <seb128> bah
[14:21] <pitti> nessita: that smells like a LP bug then
[14:21] <seb128> 02/25/11 14:20:54: retracing #723712 failed with status: 99
[14:21] <seb128> 02/25/11 14:20:54: transient error reported; halting
[14:22] <pitti> seb128: gateway timeout? I got those a lot yesterday
[14:22] <chrisccoulson> didrocks, is the launcher meant to appear when i hover over the BFB now?
[14:22] <nessita> pitti: any ideas how to debug? shall I do all the release 'by hand'?
[14:22] <chrisccoulson> or am i meant to click on it?
[14:22] <didrocks> chrisccoulson: no, it's meant to appear, but there is one case it doesn't :)
[14:22] <pitti> nessita: if it doesn't throw any exception, I have no idea to debug :(
[14:22] <didrocks> (it should fade to be honest)
[14:22] <didrocks> I just fixed it in trunk
[14:22] <chrisccoulson> didrocks, oh. it never seems to work here ;)
[14:22] <didrocks> chrisccoulson: hum? really?
[14:22] <didrocks> like, press super
[14:22] <pitti> nessita: you could run the launchpadlib commands in lp-shell and see where it fails
[14:23] <didrocks> release
[14:23] <didrocks> not, hover the bfb
[14:23] <pitti> nessita: and then report a bug against launchpadlib with that (and the command you tried to do)
[14:23] <didrocks> now*
[14:23] <chrisccoulson> didrocks, i didn't try super yet
[14:23] <seb128> chrisccoulson, you need to hit the corner
[14:23] <nessita> pitti: right
[14:23] <chrisccoulson> oh, it's appearing now
[14:23] <seb128> chrisccoulson, it doesn't stick otherwise
[14:23] <didrocks> chrisccoulson: "super" is just a way to reset it :)
[14:23] <chrisccoulson> seb128 - i was hitting the corner. i wasn't even seeing it fade in before ;)
[14:23] <seb128> didrocks, workaround for the win ;-)
[14:23] <didrocks> right :-)
[14:24] <didrocks> will be fixed with Monday's release
[14:24] <didrocks> still working on some false positives :)
[14:24] <chrisccoulson> cool
[14:29] <mterry_> dbarth, sorry, dropped of the net, so I'll risk repeating myself: is there a reviewer lined up for datetime?  I think klattimer has a branch too.  Would you prefer doing a tarball release today or just distropatch everything?
[14:31] <seb128> mterry_, you can add bug #723463 to your list of things to check if you can
[14:31] <ubot2> Launchpad bug 723463 in indicator-appmenu "indicator-applet-appmenu crashed with SIGSEGV in dbusmenu_menuitem_send_about_to_show()" [Medium,New] https://launchpad.net/bugs/723463
[14:31] <seb128> mterry_, he said to me that you should make a tarball earlier
[14:31] <dbarth> mterry_: MacSlow is reviewing your branch now
[14:31] <mterry_> seb128, cool
[14:32] <mterry_> dbarth, k, ( MacSlow, thanks and sorry for size!)
[14:32] <kenvandine> dbarth, how about karls?
[14:32] <MacSlow> mterry_, np yw... everybody has a 6k+ patch to go in... but only per year ;)
[14:32] <kenvandine> ted didn't know the status of that last night
[14:33] <mterry_> MacSlow, guh, it's only Feb
[14:33] <seb128> hey kenvandine
[14:33] <kenvandine> mterry_, guess you get to relax for the rest of the year
[14:33] <kenvandine> :)
[14:33] <kenvandine> hey seb128
[14:33] <MacSlow> mterry_, yeah... used up all you goodie-tokens right at the start ;)
[14:33] <seb128> kenvandine, !!!
[14:33] <seb128> kenvandine, don't tell that to mterry_ ;-)
[14:34] <kenvandine> hehe
[14:34] <seb128> kenvandine, how are you?
[14:34] <mterry_> aw, I already bought a recliner too
[14:34] <kenvandine> tired, very tired
[14:34] <seb128> kenvandine, do you want to do the notify-osd update or should I do it?
[14:34] <kenvandine> i'll do it
[14:34] <seb128> thank
[14:34] <seb128> kenvandine, great work yesterday
[14:34] <seb128> kenvandine, take it easy today, it has been a crazy week and you deserver to relax a bit
[14:35] <kenvandine> seb128, ted's 0.3.99 release of dbusmenu caused every click on every menu item in any of the indicators or appmenu crash unity panel and indicator applet
[14:35] <kenvandine> that was fun to debug last night
[14:35] <seb128> kenvandine, was ted still around when you debugged it?
[14:35] <kenvandine> of course he couldn't reproduce it for several hours
[14:35] <kenvandine> yeah
[14:35] <kenvandine> we fixed it, distro patched it in the upload
[14:36] <kenvandine> it never got uploaded like that
[14:36] <seb128> kenvandine, ok, nice catch ;-)
[14:36] <kenvandine> seb128, he never got a chance to debug the problem with menus for gnome-bt
[14:37] <kenvandine> but he will
[14:37] <seb128> kenvandine, the update seems to work fine, gnome-bt refresh issues seem to be fixed as well
[14:37] <kenvandine> it seems better
[14:37] <seb128> well, seems to work now
[14:37] <kenvandine> but not completely fixed
[14:37] <seb128> there was an indicator-application crasher, mterry just fixed it
[14:37] <kenvandine> if i click turn off bluetooth, the menus change
[14:38] <kenvandine> whoops, i meant they don't change
[14:38] <kenvandine> it turns off
[14:38] <kenvandine> but the menu still says "Turn off bluetooth"
[14:38] <kenvandine> instead of On
[14:38] <kenvandine> and the submenus are still missing
[14:38] <kenvandine> seb128, can you confirm that?
[14:39] <seb128> kenvandine, I will tell you once I get mterry's update
[14:39] <seb128> indicator-application is just crashing now
[14:39] <seb128> on a null variant
[14:40] <seb128> ok, it built
[14:40] <seb128> let me grab the deb on launchpad
[14:41] <kenvandine> seb128, yeah, i got on my desktop box after upgrading it this morning
[14:41] <kenvandine> but not my laptop
[14:43] <seb128> kenvandine, no, refresh works fine
[14:43] <seb128> can't confirm your bug
[14:43] <seb128> when I turn bt off I get 3 lines only in the indicator
[14:43] <seb128> oh, got the issue now and the indicator crashed
[14:44] <seb128>  #0  0x0060a099 in dbusmenu_menuitem_property_set_variant () from /usr/lib/libdbusmenu-glib.so.3
[14:44] <seb128>  No symbol table info available.
[14:44] <seb128>  #1  0x0060a36d in dbusmenu_menuitem_property_set_int () from /usr/lib/libdbusmenu-glib.so.3
[14:44] <seb128> great, new libdbusmenu crash
[14:44] <seb128> it's going to be a fun week tracking those
[14:45] <seb128> kenvandine, so it works a few times then get confused and crahs
[14:46] <kenvandine> yeah, some signal getting missed somewhere
[14:46] <kenvandine> i don't get a crash though
[14:47] <kenvandine> and i couldn't find similar behavior anywhere except gnome-bt
[14:48] <seb128> kenvandine, can you confirm that if you do on off a few times it crashes?
[14:48] <kenvandine> no, no crashes
[14:48] <kenvandine> i've done it dozens of times
[14:48] <seb128> pitti, bah the retracers crash every second retrace
[14:48] <Sweetshark> pitti: is there any convention for naming backports? you proposed 3.3.1-1ubuntu3~maverick while I see older releases following this scheme: 3.3.1-1maverick3.
[14:49] <pitti> seb128: on that weird lp connection bug?
[14:49] <pitti> Sweetshark: append ~maverick or ~maverick1 (which one is a matter of taste)
[14:49] <seb128> pitti, on lp errors, not sure if it's the weird connection, I don't have enough buffer to scroll up after the launchpad noise
[14:50] <pitti> Sweetshark: appending just "maverick" instead of "~maverick" is actively wrong, though
[14:50] <rodrigo_> seb128, yes, it needs it, talking to cosimoc about it, will push to git and submit a new patch for the package
[14:50] <seb128> rodrigo_, ok, I'm not uploading for now then
[14:50] <rodrigo_> seb128, ok, just a second
[14:51] <pitti> rodrigo_: how did the yelp build go now?
[14:51] <seb128> rodrigo_, no hurry, it's just an issue when the svg loader is broken, not in normal use
[14:52] <pitti> seb128: FYI, I commented out MAILTO in retracers; those dchroot messages get on my nerves, let's wait until the RT gets fixed
[14:52] <rodrigo_> pitti, it builds, but seems to not find the docs, so investigating
[14:52] <pitti> and amongst those I won't see actual error messages anyway
[14:52] <seb128> pitti, ok, I didn't notice I set up a filter for those the day they started ;-)
[14:53] <Sweetshark> pitti: teh releases do not have a plain maverick appended, they have ubuntu _replaced_ by maverick
[14:53] <seb128> oh, come on
[14:53] <seb128> pitti, stupid retracers crash every 1 retrace now on launchpad error
[14:53] <pitti> *sigh*
[14:53] <seb128> I keep restarting them manually for now to clean the queue
[14:54] <seb128> but we will need to investigate next week I guess
[14:54] <pitti> seb128: transient? or permanent?
[14:54] <seb128> transient
[14:54] <seb128> it retraces one or two then crash
[14:54] <pitti> I've been getting tons of timeouts in the web ui as well today
[14:54] <seb128> restarting works on one or two and it crashes
[14:58] <mterry> MacSlow, btw, my branch does the UI for the prefs, but some of the preferences themselves don't change anything in the indicator.  That's hopefully largely fixed by klattimer's branch
[14:59] <seb128> pitti, well at least the stacktrace are quite useful since yesterday
[14:59] <seb128> pitti, the new gdb works great it seems
[14:59] <mterry> (only the indicator preferences that deal with showing/hiding parts of the indicator don't work)
[14:59] <pitti> oh, great!
[15:00] <mterry> seb128, indicator-applet-appmenu doesn't even render at all in my gnome-panel...  (looking at that bug).  I assume that's something unique to me
[15:00] <MacSlow> mterry, so how do I best test this then?
[15:00] <seb128> mterry, I'm under unity so not sure
[15:00] <mterry> MacSlow, well, the first panel works fine.  The left half of the second panel works fine.  The right half you'll have to confirm that I'm twiddling gsettings by using the gsettings command
[15:00] <seb128> I don't want to start a guest session now, intel tends to crash on user switching
[15:01] <seb128> ok, I'm out for ~2 hours
[15:01] <seb128> I will read backlog and catchup for a bit when I'm back
[15:02] <MacSlow> mterry, I'll get back to you when I've sorted out the build-dependencies for your branch... atm fighting broken packages on my system
[15:02] <mterry> MacSlow, bummer :(
[15:02] <pitti> mvo: the aptdaemon you re-uploaded to maverick-proposed: all natty tasks are still open for that; is it fixed there?
[15:03] <pitti> bug 665572  even says "incomplete"
[15:03] <ubot2> Launchpad bug 665572 in aptdaemon "Unhandlable programming error (LockFailedError) - lock.status_lock doesn't contain a valid path" [High,Incomplete] https://launchpad.net/bugs/665572
[15:04] <rodrigo_> seb128, https://code.launchpad.net/~rodrigo-moya/ubuntu/natty/nautilus/fix-leak/+merge/51307
[15:04] <mvo> pitti: should be, let me double check
[15:09] <MacSlow> mterry, ok... building works... any chance to install it outside /usr (setting $PREFIX leaves "Indicator Dir" untouched pointing to /usr/lib/indicators/5)
[15:10] <rodrigo_> pitti, ok, can't find the main docs, but have tested 2.91.90 with ghelp:gnumeric and searching works, so I think it's ok to go
[15:10] <pitti> cool, thanks
[15:10] <rodrigo_> pitti, does gnome-open ghelp:gnome-help works for you?
[15:10] <pitti> rodrigo_: did you change anything in the branch? (it's yelp/ubuntu)?
[15:11] <rodrigo_> pitti, no, nothing
[15:11] <pitti> rodrigo_: "The URI ‘ghelp:gnome-help’ does not point to a valid page."
[15:11] <rodrigo_> yeah, seems we are missing that
[15:11] <pitti> rodrigo_: ok, will sponsor that then; thanks for the investigation!
[15:11] <rodrigo_> in what package is the user doc?
[15:11] <mterry> MacSlow, it's probably getting that from libindicate's .pc file or some such.  I haven't tested with it outside of /usr
[15:11] <rodrigo_> gnome-user-guide is installed here, but the docs are not found
[15:12] <rodrigo_> pitti, np
[15:14] <rodrigo_> oh, it's ghelp:user-guide
[15:14] <MacSlow> mterry, ok... "sudo make install"ed it
[15:15] <MacSlow> mterry, so how do I make it reaload with the new one?
[15:15] <pitti> rodrigo_: that works
[15:15] <rodrigo_> no idea then why yelp loads ghelp:gnome-help
[15:15] <rodrigo_> have we changed anything?
[15:16] <mterry> MacSlow, there are two things to do.  One is to restart the unity-panel-service.  The other is to restart the indicator-datetime-service.
[15:16] <mterry> MacSlow, then you run indicator-datetime-preferences to get my sweet prefs dialog (or open it from the indicator)
[15:21] <MacSlow> mterry, I can't start /usr/libexec/indicator-datetime-service...
[15:22] <MacSlow> mterry, https://pastebin.canonical.com/43969
[15:23] <rickspencer3> I know he's not here, but robert_ancel, omg, F1 opens help in the blink of an eye now!
[15:23] <kenvandine> rickspencer3, wow... how in the hell did he do that!
[15:23] <kenvandine> i've always wondered why it was so slow
[15:23] <mterry> MacSlow, oh, huh.  should be /usr/lib/indicator-datetime/indicator-datetime-service.   You may be best served by uninstalling and then building a deb package out of it
[15:24] <mterry> MacSlow, not sure if that's your problem though
[15:24] <MacSlow> there's also no binary "indicator-datetime-preferences" in the build-directory
[15:24] <chrisccoulson> kenvandine, it was slow because it used to use gecko ;)
[15:24] <mterry> MacSlow, hrm...
[15:24] <chrisccoulson> although, i've got no idea why it was *that* slow
[15:25] <kenvandine> chrisccoulson, that was the only reason? geez
[15:25] <mterry> MacSlow, copy the debian directory from natty's package and use that at least.  That way we can rule out build or installation issues
[15:25] <MacSlow> mterry, btw... I don't have a fully updated system, because I'm stuck with nvidia-current, which forces me to hold back a lot of updates
[15:25] <chrisccoulson> kenvandine, yeah, i'm still not sure why it was that slow. it was even slower than firefox, which doesn't make sense ;)
[15:25] <mterry> MacSlow, ok.  well, grab the debian directory from whatever version of indicator-datetime you do have
[15:27] <MacSlow> mterry, you mean using the debian directory with your branch to build a proper .deb?!
[15:28] <mterry> MacSlow, yeah
[15:28] <mterry> MacSlow, that's how I test anyway
[15:28] <mterry> MacSlow, I'm less familiar with the manual method
[15:32] <MacSlow> mterry, I can't build a package with this... I'm getting errors from dpkg-source I've no clue about...
[15:32] <mterry> MacSlow, ok.  well let's continue with the manual way then.  Let me re-examine your pastebin
[15:33] <mterry> MacSlow, I believe I've gotten that before erroneously when testing with restarting services and such.  There's a trick to make it not timeout
[15:34] <MacSlow> mterry, do you know the trick?
[15:34] <mterry> MacSlow, working on it.  I have to look it up
[15:34] <MacSlow> ok
[15:34] <mterry> kenvandine, do you remember the indicator debugging bash profile bits?
[15:35] <kenvandine> mterry, one sec
[15:35] <kenvandine>  . /usr/share/libindicator/80indicator-debugging
[15:36] <mterry> MacSlow, ^
[15:36] <mterry> kenvandine, thanks
[15:36] <kenvandine> no problem
[15:36] <mterry> MacSlow, you may want that in your ~/.profile
[15:36] <MacSlow> kenvandine, mterry: looking...
[15:36] <kenvandine> i don't know how well they work :)
[15:36] <kenvandine> i have mixed experiences
[15:36] <mterry> kenvandine, the not-crashs-when-no-one's-looking one works in my experience
[15:36] <MacSlow> kenvandine, I already did a "sudo  make install" so not much more harm can happen now :)
[15:37] <mterry> MacSlow, with unreviewed code no less!
[15:37] <kenvandine> MacSlow, ugh... i never do that with anything :)
[15:37]  * mterry adds MacSlow's machine to his botnet
[15:37]  * kenvandine always tests from packages!
[15:37]  * MacSlow feels like an idiot
[15:45] <MacSlow> mterry, kenvandine: still getting the same error when trying to start indicator-datetime-service
[15:46] <mterry> MacSlow, you're running the  new indicator (i.e. you restarted unity-panel-service?
[15:46] <MacSlow> yes
[15:46] <MacSlow> mterry, I see a clock in the panel
[15:47] <mterry> k
[15:47] <MacSlow> mterry, and I don't have the normal "indicator-datetime" package from natty installed
[15:48] <mterry> MacSlow, try: killall indicator-datetime-service; INDICATOR_ALLOW_NO_WATCHERS=1 /usr/lib/indicator-datetime/indicator-datetime-service
[15:48] <MacSlow> mterry, there's not binary called /usr/lib/indicator-datetime/indicator-datetime-service
[15:49] <mterry> MacSlow, oh ssorry, forgot your prefix was different
[15:49] <mterry> killall indicator-datetime-service; INDICATOR_ALLOW_NO_WATCHERS=1 /usr/libexec/indicator-datetime-service
[15:49] <mterry> MacSlow, ^
[15:51] <MacSlow> https://pastebin.canonical.com/43972/
[15:52] <MacSlow> mterry, but trying to start /usr/bin/indicator-datetime-preferences gives me...
[15:52] <MacSlow> https://pastebin.canonical.com/43973
[15:52] <pitti> chrisccoulson: I guess there aren't news from mozilla about global menu?
[15:52] <mterry> MacSlow, ah...  you're not using the latest gnome-settings-daemon
[15:53] <mterry> MacSlow, but at least the service is running
[15:53] <chrisccoulson> pitti - not yet, and the guy i've been talking to is not online atm :(
[15:53] <MacSlow> mterry, I guess that's one of the things I can't update to
[15:53] <mterry> MacSlow, is it possible for you to usse the latest g-s-d in natty?
[15:53] <chrisccoulson> in any case, the menu is broken because of dbusmenu, so i wouldn't upload it today ;)
[15:53] <MacSlow> mterry, because I've to stick with nvidia-current
[15:53] <chrisccoulson> but this is so goddamn depressing, having my work just sitting there :(
[15:54] <pitti> chrisccoulson: ok, thanks
[15:54] <mterry> MacSlow, the chain of dependencies for that must be odd then
[15:54] <chrisccoulson> i almost wonder if i should JFDI ;)
[15:54] <MacSlow> mterry, I'm trying to see if I can just grab that one... but I'm also having very odd mouse-click issues here right now
[15:55] <mterry> MacSlow, :-/  not your day
[15:56] <MacSlow> mterry, oh... I have these sort of issue all the time... not just today
[15:56] <mterry> :(
[15:56] <MacSlow> mterry, dev on a in-dev platform is asking for it
[15:57] <mterry> MacSlow, huh?
[15:59] <MacSlow> mterry, ok... was able to pull g-s-d
[15:59] <MacSlow> I'll restart that now
[15:59] <mterry> that didn't go well
[15:59] <fta> is there a way to tell compiz that i don't want windows overlapping workspaces to appear on the next workspace? it's a weird experience coming from metacity and it breaks the unity panel auto-hide
[16:01] <pitti> chrisccoulson: release meeting starting now; I'll ask about swt-gtk
[16:01] <chrisccoulson> pitti - excellent, thanks
[16:01] <Amaranth> fta: No, that is an integral part of the design, it's how viewports work
[16:01] <chrisccoulson> hmmm, what happened to evolution? it's gone crash crazy this afternoon
[16:01] <MacSlow> mterry, success... at last
[16:02] <fta> Amaranth, d'oh! :(
[16:02] <mterry> MacSlow, yay!
[16:02] <Amaranth> fta: We used to have support for virtual desktops (and the code is even still there) but afaik it last worked in 7.04 and you can't get expo, wall, cube, etc with it
[16:03] <pitti> chrisccoulson: would you mind opening a bug against euca to drop swt-gtk? then we can track this better
[16:03] <mterry> MacSlow, I don't know when you grabbed my branch, but I had made one last commit this morning removing the "week starts on" preference (as it won't work at all with current gtk calendar -- they ignore that preference in favor of locale)
[16:03] <pitti> chrisccoulson: (sorry, busy in meeting now); please add a rationale about supportability and xulrunner, etc.
[16:03] <grzesag> Hi everyone. I am looking for anti-virus software for Ubuntu 10.10 Desktop? any suggestion? thanks
[16:03] <chrisccoulson> pitti - yeah, can do. (or move it to universe) ;)
[16:03] <pitti> chrisccoulson: or that :)
[16:04] <MacSlow> mterry, "Show a clock in the panel" has no effect... it's always shown
[16:06] <mterry> MacSlow, yup
[16:06] <mterry> MacSlow, that's one of the 'show preferences' that doesn't have code on the indicator side
[16:07] <fta> Amaranth, hm, i don't want virtual desktops, do I? i often push my windows slightly off screen on the right, or bottom right when i need more visible space on a workspace (been doing that since fvwm 2 decades ago). but now, the off-screen parts appear on the next workspace, beside being ugly, it makes the problem worse, as it's even visible space there, but it also prevents the panel from raising
[16:07] <mterry> MacSlow, some of those are fixed by klattimer's branch (but not the 'show clock' and live updating of locations)
[16:07] <MacSlow> mterry, apart from that everything renders fine and acts correctly on the chagnes I make in ther dialog right away
[16:07] <fta> Amaranth, +less
[16:14] <mterry> MacSlow, afk for like 20m
[16:14] <MacSlow> mterry, still looking through the code... i'll write a summary in the comment on the merge-proposal
[16:29] <mterry> MacSlow, back
[16:38] <mterry> MacSlow, ah, good leak finds, thanks
[16:41] <Sweetshark> pitti: ping?
[16:41] <pitti> Sweetshark: o/
[16:42] <mterry> MacSlow, fixed.  who does the actual merge?
[16:44] <Sweetshark> pitti: we currently separate libreoffice and libreoffice-l10n, but as both are generated from the same source I shouldnt need another branch for l10n, right?
[16:44] <Sweetshark> (apart from control file regeneration)
[16:44] <pitti> Sweetshark: no; AFAIK it's just changing the name in debian/changelog, regenerating control file, debuild -S
[16:45] <pitti> Sweetshark: their orig.tar etc. shoudl be identical
[16:46] <Sweetshark> on a down note: the arm build failed because gcc is too stupid (or too clever) for itself ...
[16:47] <pitti> ?
[16:47] <pitti> I've seen the error, but it looked like an ICE
[16:48] <Sweetshark> pitti: yes
[16:53] <dbarth> mterry: did you get a review, are things all good for sealing a release of i-datetime?
[16:54] <mterry> dbarth, MacSlow approved.  but now I'm looking at getting klattimer's datetime stuff in too
[16:55] <dbarth> mterry: he pushed rev 67 he told me
[16:56] <mterry> dbarth, I guess I don't know what that means
[16:56] <mterry> dbarth, who merges my branch now that it's approved?
[16:57] <mterry> dbarth, klattimer's stuff needs some more baking and moving-parts-settling it seems.  I think mine was the more FF-important bit
[16:57] <dbarth> that's the issue, as foundations is a bit empty today
[16:57] <dbarth> mterry: can you roll a release from trunk now?
[16:58] <dbarth> sorry, merge in your changes
[16:58] <dbarth> i'll ask karl to do the same for his
[16:58] <mterry> dbarth, I'm not in ~indicator-applet-developers
[16:58] <dbarth> ah
[16:58] <pitti> good night everyone, have a nice weekend!
[16:59] <mterry> pitti, by!
[17:00] <didrocks> enjoy pitti
[17:01] <Sweetshark> pitti: have fun!
[17:07] <mterry> dbarth, talking to klattimer, he's fixing up his branch to now apply on top of the new trunk.  his branch also needs a new libido.  is that lined up for release too?
[17:08] <dbarth> mterry: ok, great, njpatel is your man now, as i'll take the road in a minute now
[17:08] <mterry> dbarth, ok
[17:08]  * mterry hugs njpatel
[17:09]  * njpatel hugs mterry
[17:09] <njpatel> Why are we doing this?
[17:09] <mterry> MacSlow, btw, thanks for your review!  I know that was a lot to dump on ya
[17:09] <mterry> njpatel, you just got volunteered to help shepherd the indicator-datetime stuff to release
[17:09] <mterry> njpatel, I just had a giant branch land, and klattimer is fixing up his merge for it too
[17:09] <mterry> njpatel, his merge requires a second merge on libido which will need a release too
[17:10] <mterry> njpatel, and both will need FFe I suppose. I can help with that bit though
[17:14] <mterry> njpatel_, you there?
[17:15] <njpatel_> mterry, hey
[17:16] <njpatel_> sorry, connman decided to crash
[17:16] <mterry> njpatel, how much did you get?
[17:16] <njpatel> the last sentence only :/
[17:16] <njpatel> can you pastebin what you said please?
[17:17] <njpatel> mterry, ^
[17:18] <mterry> njpatel, http://pastebin.ubuntu.com/572261/
[17:19] <mterry> njpatel, FFe bug filed but not yet official: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/725121
[17:19] <ubot2> Launchpad bug 725121 in indicator-datetime "Feature Freeze Exception for indicator-datetime" [Undecided,New]
[17:19] <njpatel> mterry, ah, thanks
[17:19] <njpatel> hold up
[17:20] <mterry> (i didn't subscribe the team yet, just doing paperwork ahead of time)
[17:36] <mterry> seb128, ok, talked to njpatel.  I'm going to fix up klattimer's branch to apply to new trunk, njpatel will review and possibly publish tomorrow.  FFe (started in above link) will hopefully get granted on monday
[17:37] <didrocks> mterry: there is still no more delegation discussed, but yeah, just emphasize on why the FFe is important
[17:37] <didrocks> then, it should be good
[17:38] <mterry> didrocks, delegation?
[17:40] <didrocks> mterry: yeah, the release team is giving FFe
[17:40] <didrocks> mterry: but in the past, for some part of the archive, some non release team member can give FFe
[17:40] <mterry> didrocks, ah
[17:40] <didrocks> like seb128 in GNOME, me in UNE
[17:40] <didrocks> and so on… :)
[17:40] <njpatel> "the good ol' days"
[17:40] <didrocks> right ;)
[18:01] <chrisccoulson> kenvandine, did you break evolution? ;)
[18:01] <kenvandine> chrisccoulson, not that i know of :)
[18:01] <kenvandine> chrisccoulson, what's up?
[18:02] <chrisccoulson> kenvandine, oh, it crashes every couple of minutes since i updated my machine earlier ;)
[18:02] <kenvandine> humm
[18:02] <kenvandine> haven't seen that
[18:02] <kenvandine> all i changed in evolution was the desktop file
[18:02] <kenvandine> but i did change evolution-indicator
[18:03] <chrisccoulson> kenvandine, http://paste.ubuntu.com/572279/
[18:04] <chrisccoulson> i haven't got all the symbols installed just yet though
[18:04] <chrisccoulson> happens pretty much every time it scans for new mail ;)
[18:04] <skaet_> didrocks, dbarth - do you have a nice summary of the actual packages with updates still left to land for A3 (ie FFEs)? - is the bug mterry the only one anticipated?
[18:04] <chrisccoulson> (every 2 minutes)
[18:04] <didrocks> skaet_: there will be nux and unity of course, maybe libunity as well
[18:05] <didrocks> skaet_: but it's not a FFe for alpha3
[18:05] <didrocks> just bug fixes
[18:05] <didrocks> (maybe a small fix to the compiz decoration as well, so compiz to the list)
[18:06] <kenvandine> chrisccoulson, ok, that does look like my fault :)
[18:06] <chrisccoulson> heh :)
[18:07] <kenvandine> not sure why it is using libnotify1 though
[18:07] <kenvandine> so not really my fault :)
[18:07] <kenvandine> chrisccoulson, please file a bug, i'll look at it
[18:07] <chrisccoulson> urgh - Complete report 172.3MB
[18:07] <chrisccoulson> perhaps i won't be submitting it just yet ;)
[18:07] <chrisccoulson> that's surely a joke isn't it?
[18:08] <skaet_> didrocks, thanks.   bug fixes are welcome,  regressions can please stay in local development trees.  ;)
[18:08] <kenvandine> ugh
[18:08] <kenvandine> no idea
[18:08] <kenvandine> :)
[18:08] <didrocks> skaet_: yeah, but there is never the joy of delivering a bug fix without a regression :-) (kidding)
[18:08] <kenvandine> chrisccoulson, i think i know why... sigh
[18:09] <kenvandine> chrisccoulson, just file the small version of the bug :)
[18:09] <skaet_> :)
[18:09] <chrisccoulson> kenvandine, the full version is uploading fairly quickly, i think apport must have been lying ;)
[18:12] <chrisccoulson> kenvandine, oh, bug 725102 :)
[18:12] <ubot2> Launchpad bug 725102 in evolution-indicator "evolution crashed with SIGSEGV in notify_notification_new()" [Medium,New] https://launchpad.net/bugs/725102
[18:13] <kenvandine> chrisccoulson, thx
[18:17] <seb128> re
[18:17] <seb128> mterry, ok great
[18:23] <kenvandine> chrisccoulson, ok, uploading fix now
[18:23] <kenvandine> thx!
[18:23] <chrisccoulson> kenvandine, excellent, thanks :)
[18:26] <kenvandine> chrisccoulson, do you know about the loss of appmenu menus in firefox?
[18:27] <kenvandine> chrisccoulson, says it is incompatible with firefox 4.0b12
[18:27] <chrisccoulson> kenvandine, have you updated globalmenu-extension from my PPA?
[18:27] <kenvandine> i wonder if i disabled your ppa
[18:28] <kenvandine> i guess that explains it :)
[18:28]  * kenvandine adds ppa aain
[18:28] <kenvandine> again
[18:28] <chrisccoulson> heh
[18:28] <chrisccoulson> that should fix it :)
[18:29] <chrisccoulson> of course, if we were shipping it by default, we wouldn't have this issue (as I would just build it from the firefox source tree)
[18:29]  * chrisccoulson sighs
[18:30] <kenvandine> yay, thx chrisccoulson
[18:31] <kenvandine> speak of that... seb128 mind reviewing lo-menubar again?
[18:31] <seb128> kenvandine, it was ok yesterday, do you need another review?
[18:31] <kenvandine> it's in sourceNEW
[18:32] <seb128> kenvandine, ok
[18:32] <kenvandine> thx
[18:32] <kenvandine> seb128, remember you are betting on me being first :)
[18:33] <chrisccoulson> well, i think that's a given now ;)
[18:33] <chrisccoulson> unless I just go ahead and upload it
[18:33] <chrisccoulson> which i'm getting close to doing ;)
[18:34] <kenvandine> chrisccoulson, they said today right?
[18:34] <chrisccoulson> kenvandine, yeah, but that's not going to happen now. i haven't heard anything from the guy i'm talking to and he's not online either
[18:35] <chrisccoulson> if ever we need a reason to switch to chromium, then this is it ;)
[18:36] <kenvandine> :/
[18:41] <seb128> kenvandine, ok, source NEWed
[18:41] <kenvandine> thx
[18:41] <seb128> yw
[18:55] <didrocks> ok, time for dinner her
[18:55] <didrocks> here*
[18:55] <didrocks> see you next week!
[19:05] <cyphermox> if someone wants to review small bugfixes to evolution and evolution-exchange: https://code.edge.launchpad.net/~mathieu-tl/evolution-exchange/lp694884/+merge/51219  and  https://code.edge.launchpad.net/~mathieu-tl/evolution/2011-02-25/+merge/51352
[19:12] <chrisccoulson> does anyone know what's going on with the amd64 builders? everything is failing now
[19:14] <chrisccoulson> oh, it's not just amd64 now
[19:19] <fta_> bryce_,  X crashes on startup (in evdev_drv)
[19:20] <bryce_> fta_, file a bug, we'll investigate when we get time
[19:21] <bryce_> fta_, a full backtrace via gdb or apport is the most useful thing to gather in that case
[19:21] <fta_> bryce_,  difficult, i'm on my tablet right now.. http://pastebin.ubuntu.com/572317/
[19:21] <bryce_> fta_, yeah hard to guess from that limited trace
[19:22] <fta_> i know, but nothing in /var/crash for it
[19:22] <bryce_> fta_, presumably something with the utouch patches that went in earlier this week
[19:22] <bryce_> pid of X ; gdb /usr/bin/Xorg ; # attach <pid> ; bt full
[19:22] <fta_> can't find the evdev-drv dbg deb..
[19:23] <bryce_> xserver-xorg-input-evdev-dbg
[19:24] <fta_> nope, E: Unable to locate package xserver-xorg-input-evdev-dbg
[19:24] <fta_> same for -dbgsym
[19:25] <bryce_> huh, yeah you're right no -dbg for -evdev.  weird
[19:26] <fta_> tried a downgrade, -6 gives me another crash :(
[19:26] <ssk_the_gr8> need help... i'm new to ubuntu
[19:26] <bryce_> well the bug is probably in xserver code actually
[19:26] <ssk_the_gr8> is this the right channel?
[19:27] <bryce_> ssk_the_gr8, sorry, no
[19:27] <bryce_> ssk_the_gr8, you want #ubuntu
[19:27] <ssk_the_gr8> where should i go...
[19:27] <ssk_the_gr8> k thanx
[19:31] <fta_> bryce_, http://paste.ubuntu.com/572320/
[19:35] <bryce_> fta_, ok looks better
[19:38] <bryce_> fta_, not sure offhand, I probably need to show this to cnd since I suspect it's that the input device logic has changed a bit so as to accomodate multitouch devices, and it seems to have adversely affected your particular device
[19:39] <bryce_> oh speak of the devil
[19:39] <cnd> I was tipped off
[19:39] <cnd> you've been had!
[19:40] <bryce_> heh
[19:40] <bryce_> cnd, http://paste.ubuntu.com/572320/
[19:41] <bryce_> fta_, btw I'm assuming this is a system+device that's been running natty for some time, and not just a fresh upgrade or installation?
[19:42] <bryce_> fta_, i.e. it's a recent regression?
[19:42] <fta_> bryce_, yep, removed my wireless mouse, it works
[19:42] <fta_> bryce_, yes, it's a recent regression
[19:42] <fta_> this box is using natty since day 1
[19:42] <cnd> fta_: can you file a bug report: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+filebug
[19:43] <cnd> assign it to me, username "chasedouglas"
[19:43] <bryce_> actually, might be better to use ubuntu-bug xserver-xorg-input-evdev
[19:43] <bryce_> that'll automatically attach logs and such
[19:43] <cnd> bryce_, ahh, sure
[19:43] <fta_> now that i have my desktop back, i guess i can file the bug.. providing i find another mouse somewhere in the house :P
[19:43] <bryce_> fta_, also attach your backtrace for him
[19:43] <cnd> fta_: can you also attach the gdb log file?
[19:44] <cnd> fta_: I will to look at this today
[19:44] <fta_> cool
[19:44] <bryce_> thanks cnd
[19:44] <fta_> give me a minute
[19:45] <fta> ahhh
[19:45] <fta> better than an android virtual keyboard
[19:57] <fta> cnd, bryce_: bug 725202
[19:57] <ubot2> Launchpad bug 725202 in xserver-xorg-input-evdev "X crashes on startup in evdev_drv" [Undecided,New] https://launchpad.net/bugs/725202
[19:58] <cnd> fta: thanks!
[20:30] <fta> cnd, as i said above, the previous version (-6) also crashes, for another reason
[20:31] <cnd> fta, oh!, I missed that
[20:32] <cnd> fta, did this bug occur before monday?
[20:33] <fta> cnd, 1st time today. but i had X held for a while by the nvidia-current driver, which just appeared today
[20:34] <cnd> fta, does that mean you have seen crashes before with the previously held X version?
[20:34] <fta> cnd, nope
[20:34] <cnd> ok
[20:36] <cnd> fta: can you try this:
[20:36] <cnd> switch to a VT
[20:36] <cnd> $ sudo stop gdm
[20:36] <cnd> $ sudo Xorg :0
[20:37] <cnd> see if it crashes
[20:37] <cnd> when you have the device plugged in of course
[20:37] <cnd> $ sudo start gdm
[20:37] <cnd> to get back to X afterwards
[20:38] <fta> cnd, tried that several times already, it always crashed
[20:38] <cnd> fta, ok, that's good for debugging at least
[20:39] <cnd> fta, please install valgrind
[20:39] <cnd> then in the VT, run:
[20:39] <fta> i have it
[20:39] <cnd> $ sudo valgrind --tool=memcheck Xorg :0 > valgrind.log 2>&1
[20:39] <fta> i need to kill my session then..
[20:39] <cnd> attach the file to the bug
[20:39] <cnd> ok
[20:39] <cnd> thanks for the hard work :)
[20:52] <fta> cnd, got it, along with a /var/crash/_usr_lib_valgrind_memcheck-x86-linux.0.crash
[21:00] <fta> chrisccoulson, didn't take long: Title: evolution crashed with SIGSEGV in notify_notification_new()
[21:01] <chrisccoulson> fta - a fix has been uploaded, but the builders are screwed
[21:01] <fta> chrisccoulson, good, which package is that? i'll rebuild it locally, i'm stuck
[21:01] <chrisccoulson> fta - evolution-indicator
[21:02] <fta> chrisccoulson, ok, thanks
[21:04] <fta> chrisccoulson, 0.2.14-0ubuntu3 ?? it ftbfsed on i386 & amd64
[21:04] <bigon> GNOME packages (mutter, gjs,...) get automatic grants for feature freeze?
[21:04] <chrisccoulson> fta - yeah, that's the one
[21:04] <chrisccoulson> bigon - yes, as long as they're already on unstable series i think
[21:04] <chrisccoulson> please don't upload anything right now though :)
[21:05] <bigon> alright
[21:05] <bigon> ah, ok
[21:05] <bigon> why?
[21:05] <chrisccoulson> fta - the failure is because the builders are broken
[21:05] <bigon> that's answer my question I guess
[21:05] <chrisccoulson> bigon - http://identi.ca/launchpadstatus
[21:06] <bigon> alright
[21:07] <fta> cnd, did the valgring logs help?
[21:07] <cnd> fta, hmmm... it really hurts that the archive hasn't generated dbgsym packages for evdev like it's supposed to
[21:07] <cnd> so yes, the logs help
[21:08] <cnd> but I can't correlate the valgrind issue to source code right now
[21:08] <cnd> fta, let me build you a special package for testing
[21:09] <cnd> fta, actually, it does help some
[21:09] <cnd> it kind of looks like a simple off by one error
[21:09] <cnd> let me look back at the code again
[21:18] <fta> chrisccoulson, confirmed, evo crash gone
[21:28] <kenvandine> fta, that was from my fix in evolution-indicator?
[21:28] <kenvandine> fta, ah, i read back... it is... great, thanks for confirming it fixed it
[21:29] <fta> kenvandine, thanks for the fix :)
[21:29] <chrisccoulson> b'ah, couchjs is broken *again*
[21:29] <chrisccoulson> grrrrrrrrrrrrrrrrrrrrrrrrrr
[21:30] <kenvandine> fta, i still don't know why it wasn't crashing here... but it was an obvious problem
[22:03] <chrisccoulson> i think i'm in love with unity 2d
[22:16] <cnd> fta, I've had to fix pkg-create-dbgsym to be able to create test packages for you
[22:16] <cnd> sorry for the delay
[22:20] <lifeless> cnd: what was wrong with it ?
[22:20] <cnd> lifeless, https://bugs.launchpad.net/ubuntu/+source/pkg-create-dbgsym/+bug/725274
[22:20] <ubot2> Launchpad bug 725274 in pkg-create-dbgsym "pkg-create-dbgsym doesn't recognize linux-any architecture" [Undecided,New]
[22:20] <lifeless> ah phew
[22:20] <cnd> I've got a branch pushed, just doing the ffe stuff
[22:20] <lifeless> i thought it might be related to the current incident with the builds farms
[22:22] <cnd> actually, is an ffe needed for a bug fix?
[22:23] <cnd> I don't think it is...
[22:28] <cnd> if I need to upload a package to main, do I still subscribe ubuntu-sponsors?
[22:28] <cnd> or do I subscribe some coredev specific team?
[22:28] <fta> cnd, oh, that's why the deb is an arch all then.
[22:28] <fta> it's weird
[22:28] <cnd> fta: ?
[22:28] <cnd> which deb is an all?
[22:29] <fta> xserver-xorg-input-evdev-dev_2.6.0-1ubuntu6_all.deb
[22:29] <fta> _all
[22:29] <micahg> cnd: are you asking WRT feature freeze?
[22:29] <cnd> fta, that's just the dev package
[22:29] <cnd> not the real one
[22:29] <fta> oh
[22:29] <cnd> micahg, it's a bug fix to pkg-create-dbgsym
[22:29] <micahg> cnd: bug fixes are fine after feature freeze except when frozen for a milestone or past final freeze
[22:30] <cnd> micahg, thanks
[22:30] <fta> n-m, wrong copy/paste
[22:31] <micahg> cnd: and in those cases, you can ask the release team if you think it's urgent
[22:43] <fta> hm, found a regression in unity
[22:44] <fta> mplayer in fullscreen mode no longer accepts keyboard actions
[22:52] <cnd> fta, it doesn't help that you're on i386 either :)
[22:52] <cnd> I had to go find a build resource to get you test packages
[22:55] <cnd> I'm getting there though...
[23:00] <cnd> fta, please install the two evdev packages at http://people.canonical.com/~cndougla/utouch/
[23:00] <cnd> then do the valgrind dance
[23:00] <cnd> and attach the output to the bug again
[23:00] <cnd> thanks!
[23:12] <fta> cnd, ok, will do
[23:34] <cnd> fta, thanks for the logs, it does look like my patches are causing stack corruption
[23:36] <fta> cnd, ok, do you have enough info now?
[23:36] <cnd> fta, I think so
[23:37] <fta> good
[23:37] <fta> on my side, i had some fun controlling my desktop from my android tablet ;)
[23:37] <cnd> fta, I think I know what's wrong
[23:37] <cnd> I'll try to spin a new package for you
[23:38] <fta> it's getting late here (paris)
[23:39] <cnd> fta, ahh, I'll follow up on the bug report
[23:39] <cnd> you can test later
[23:39] <cnd> thanks for your help today though!
[23:39] <fta> sure, thanks