[01:27] <lifeless> bryceh: btw - 803012
[01:27] <lifeless> bug 803012
[01:27] <ubot2> Launchpad bug 803012 in xserver-xorg-video-intel "Intel driver incorrectly renders some UI elements" [Medium,Fix released] https://launchpad.net/bugs/803012
[01:27] <lifeless> bryceh: I just saw the same symptoms on my natty nvidia machine
[01:27] <lifeless> bryceh: dunno what that means.
[01:34] <RAOF> lifeless: Presumably with nouveau?
[01:35] <lifeless> RAOF: nup
[01:35] <lifeless> proprietary foo
[01:37] <RAOF> That's almost certainly a different bug, then?
[01:37] <lifeless> dunno
[01:37] <lifeless> same symptoms
[01:37] <lifeless> wondering if its a userspace issue at heart (classic mode fail?)
[01:38] <bryceh> lifeless, so little X code is shared between -nvidia and anything else that if it is the same bug, that points to perhaps something non-X/non-kernel involved
[01:39] <bryceh> lifeless, X bugs frustratingly often show identical symptoms on two different drivers but are ultimately very different bugs underneath
[01:39] <bryceh> lifeless, probably the right thing to do would be to test oneiric (or a backport of this -intel fix).  That would be more definitive.
[01:40] <lifeless> k
[01:40] <lifeless> hows oneiric fs stability atm ?
[01:40] <bryceh> the /run bugs from last week were fairly bad, but that should be solved now
[01:46] <RAOF> I haven't hit any fs bugs (barring the /run amazement).  AFAIK the ecryptfs bug is gone.
[01:48] <bryceh> I put the patch in for natty sru as well, so if you don't want to upgrade yet, should be available in natty-proposed whenever the buildd's are done
[03:11] <jasoncwarner_> bryceh and RAOF ... saw x come down today and I decided to be brave. so far no problems...anything I should be looking for?
[03:12] <jasoncwarner_> and RAOF, I've been using nouveau ever since the rally...no problems to mention...
[03:12] <RAOF> jasoncwarner_: Not really; that was just the xorg metapackage.
[03:12] <RAOF> jasoncwarner_: Cool.
[03:13] <jasoncwarner_> RAOF nouveau was such a non-issue I forgot I was using it ;)
[03:14] <RAOF> The xorg package updated fine?  It didn't hit a file conflict in xorg-server?
[03:16] <jasoncwarner_> RAOF: no, everything seemed to go just fine..rebooted and everything...though now I hvae to reboot because I wanted to test nvidia driver again...
[03:16] <jasoncwarner_> be back
[03:17] <RAOF> I wonder if that makes my local problem self inflicted :)
[03:25]  * RAOF heads off for a run and lunch.
[04:33] <TheMuso> RAOF: hrm seems I got the conflict when updating a chroot here.
[04:33] <TheMuso> RAOF: trying to overwrite '/usr/share/doc/xorg', which is also in package xserver-xorg 1:7.6+7ubuntu2
[04:45] <pitti> Good morning
[04:51] <jbicha> hi, could I have someone look at https://code.launchpad.net/~jbicha/ubuntu/oneiric/transmission/transmission-2.32/+merge/67772
[04:59] <pitti> jbicha: ah, can do
[05:00] <pitti> jbicha: hm, current source package's Vcs-Bzr: says that it uses lp:ubuntu/transmission, not the old ubuntu-desktop branch any more
[05:01] <pitti> but *shrug*, as long as that one is up to date.. the ubuntu:transmission one will be auto-updated
[05:02] <pitti> jbicha: no, lp:~ubuntu-desktop/transmission/ubuntu is outdated, it's for maverick
[05:03] <jbicha> pitti: oh, then I think there might be changes I've missed then
[05:04] <pitti> I can't remove the old ubuntu-desktop branch unfortunately
[05:04] <jbicha> pitti: hmm?
[05:05] <jbicha> so I should rebranch off ubuntu:transmission, right?
[05:06] <jbicha> the ubuntu-desktop branches are more convenient, except that Launchpad doesn't expect them
[05:06] <didrocks> good morning
[05:07] <jbicha> didrocks: howdy
[05:07] <RAOF> Morning didrocks
[05:07] <didrocks> hey jbicha, RAOF!
[05:07] <TheMuso> Morning pitti, didrocks.
[05:07] <pitti> jbicha: right
[05:08] <didrocks> morning TheMuso
[05:08] <pitti> hey didrocks
[05:08] <didrocks> guten morgen pitti :)
[05:08] <pitti> jbicha: sorry for the wasted time :/
[05:08] <pitti> hey TheMuso, how are you?
[05:14] <TheMuso> pitti: Not too bad thanks, yourself?
[05:15] <pitti> pretty good, thanks
[05:27] <bryceh> hey, there's a bug with the xorg metapackage
[05:27] <bryceh> looks like the version we got from debian does some symlinking magic which breaks when it gets updated
[05:28] <bryceh> https://bugs.edge.launchpad.net/ubuntu/+source/xorg/+bug/812665
[05:28] <ubot2> Ubuntu bug 812665 in xorg "package xorg 1:7.6 7ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/doc/xorg', which is also in package xserver-xorg 1:7.6 7ubuntu2" [Undecided,New]
[05:54] <didrocks> session restart, brb
[05:56] <RAOF> pitti: bug 812665 looks to be a result of the documentation-linker having a namespace clash.
[05:56] <ubot2> Launchpad bug 812665 in xorg "package xorg 1:7.6 7ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/doc/xorg', which is also in package xserver-xorg 1:7.6 7ubuntu2" [Undecided,New] https://launchpad.net/bugs/812665
[05:57] <RAOF> The xserver-xorg now ships the documentation in /usr/share/doc/xorg, but the auto-linker has kindly symlinked /usr/share/doc/xorg (in the xorg package) to x11-common.
[05:57] <RAOF> With hilarious consequences!
[05:58] <pitti> uh, eww indeed
[05:59] <pitti> RAOF: but we never symlink entire directories
[05:59] <pitti> is that something the xorg package does itself?
[05:59] <pitti> because dpkg handles directories specially, pkgbinarymangler only symlinks individual files
[05:59] <pitti> lrwxrwxrwx 1 root root 10 2011-03-03 18:16 /usr/share/doc/xorg -> x11-common
[05:59] <pitti> this isn't pkgbinarymangler's doing
[06:02] <RAOF> Ah, ok.
[06:03] <RAOF> So now I get to work out what *is* symlinking that directory!
[06:04] <RAOF> Oh, my.
[06:06] <pitti> RAOF: I get teh symlink when building locally without any mangling
[06:06] <RAOF> Yeah, it's some crazy-arse preinst magic.
[06:06] <pitti> RAOF: how about this:
[06:06] <pitti>         for p in $$(dh_listpackages -i -N$$t); do \
[06:06] <pitti>           rm -rf debian/$$p/usr/share/doc/$$p; \
[06:06] <pitti>           ln -s $$t debian/$$p/usr/share/doc/$$p; \
[06:06] <RAOF> Indeed, you have found ite :)
[06:06] <pitti> :)
[06:08] <RAOF> Hah.  With the even more hilarious consequences that dpkg now thinks /usr/share/doc/xorg actually exists!
[06:09] <pitti> one should avoid shipping directory symlinks like the plage
[06:10] <pitti> platue
[06:10] <pitti> plague
[06:10] <pitti> (gosh)
[06:10] <pitti> at some point they *will* shoot you into the foot
[06:10] <RAOF> Because dpkg gets all narky on you.
[06:10] <RAOF> Although, to be fair, the problem's not the symlink in this case.  The problem is the namespace conflict.
[06:10] <pitti> and you need all sorts of black preinst magic if you ever want to get rid of them again :)
[06:10] <pitti> yes, right
[06:11] <RAOF> Preinst magic like “is this a link?  If so, rm -rf it.”? :)
[06:11] <pitti> "rm" should be enough, but yes
[06:11] <pitti> and checking that it points to the right place, handling aborted package upgrades and put it back then, etc.
[06:12] <RAOF> Yeah.  xorg doesn't do any of that pansy sanity checking.
[06:12] <pitti> but I'm not suggesting to actually remove the link now
[06:12] <RAOF> If someone's stupid enough to symlink /usr/share/doc/xorg to /, they deserve all they get!
[06:12] <pitti> I guess it's easiest to just drop the duplicate file?
[06:12] <RAOF> That's what it does *right now*
[06:16] <RAOF> Hm.  That doesn't seem to have come from debian.  Are we dancing the ‘I hope you haven't symlinked /usr/share/doc/{x11-common,xorg,xserver-xorg} anywhere you care about’ fandango in Ubuntu diff?
[06:16] <pitti> I think we can safely assume that the user didn't tamper with these links
[06:17] <pitti> /usr/share/doc/ must have the property that users can rm -rf it entirely without anything breaking
[06:17] <RAOF> Yeah.  It'd suck to have accidentally replaced a symlink in there at some point in the distant past, though.
[06:18] <RAOF> Ah, yes.  This *is* Ubuntu diff.  In fact, it's an oldschool pre-pkgbinarymangler symlink-the-docs hack.
[06:18] <pitti> ah
[06:18] <RAOF> From brave-old 2007
[06:19] <RAOF> When men were real men, and symlinking doc directories was real men's work. :)
[06:19] <pitti> so either we do the preinst bits of removing the links and drop all the manual symlinking
[06:19] <pitti> lol
[06:19] <pitti> and let the mangler figure it out
[06:19] <RAOF> I'm super-inclined to let pkgbinarymangler take this problem off my hands.
[06:19] <pitti> erm, no either
[06:20] <pitti> we can't ship the same symlink in two packages, period
[06:20] <pitti> RAOF: my gut feeling is "drop all this, remove all symlinks in preinst, and drop the preinst bits after the next LTS"
[06:21] <RAOF> That's what I'm thinking, too.
[06:43] <jbicha> is it safe for me to remove .pc, drop in the new upstream source, and then quilt push the patches I want?
[06:44] <didrocks> jbicha: depends if you have applications/libraries dependending on your .pc file
[06:45] <jbicha> I'm working on transmission and I've not done much with .pc stuff
[06:45] <jbicha> I tried quilt pop but it said it couldn't remove cleanly
[06:46] <pitti> jbicha: don't just remove .pc
[06:46] <pitti> jbicha: I suggest theh following:
[06:46] <pitti> check out ubuntu:pkgname
[06:46] <pitti> quilt pop -a
[06:46] <pitti> and then rm -r .pc (which should now be empty)
[06:46] <pitti> you can commit that as "unapply patches"
[06:47] <pitti> applied patches in bzr are excruciatingly hard to maintain, and against common practice IMHO
[06:47] <pitti> so in my branches I don't apply them
[06:47] <pitti> (they also break merge-upstream)
[06:48] <jbicha> well I had like 200 something conflicts when I tried to merge with the Debian bzr
[06:48] <jbicha> what if quilt pop complains about not being able to remove cleanly?
[06:50] <didrocks> mvo: hey, how are you?
[06:50] <jbicha> is quilt pop -a -f ok?
[06:50] <jbicha> -f fixes everything!
[06:51] <pitti> jbicha: if quilt pop -a in a cleanly checked out tree doesn't work, then something has gone seriously wrong :(
[06:51] <pitti> jbicha: did you try this _after_ merging with debian?
[06:52]  * didrocks looks for a wiki page to show jbicha quilt best practices
[06:52] <jbicha> well I did bzr revert and I hadn't made any commits
[06:52] <jbicha> but I'll do a bzr branch again to make sure
[06:52] <pitti> jbicha: if it gets too complicated, just use apt-get source and merge the old way with diffing debian/ ..
[06:53] <jbicha> pitti: well quilt pop -a -f worked, I just didn't know if it was a good idea
[06:53] <pitti> I don't know either
[06:54] <pitti> if the patches don't apply, they need to be fixed either way
[06:54] <pitti> but then the bzr branch is horribly inconsistent, as in this case you couldn't even have built the source package for uploading
[06:54] <jbicha> pitti: I guess something has gone seriously wrong :-)
[06:54] <didrocks> jbicha: if you like to read some documentation to understand how quilt works, you can have a look there, it seems quite nice: http://www.shakthimaan.com/downloads/glv/quilt-tutorial/quilt-doc.pdf
[06:55] <mvo> didrocks: hey, good morning
[06:56] <jbicha> pitti: but all I really need to do is to get a clean source tree, it doesn't matter whether I use quilt pop or do it manually, right?
[06:56] <pitti> jbicha: right, but how do you get it if the patches don't unapply?
[06:57] <jbicha> just plopping in the source & removing .pc :-)
[07:19] <Sweetshark> Morning all!
[07:25] <didrocks> hey Sweetshark
[07:30] <chrisccoulson> good morning everyone
[07:31]  * bryceh waves
[07:32] <didrocks> hey chrisccoulson! good evening bryceh
[07:33] <bryceh> heya didrocks
[07:33] <RAOF> Hey hey chrisccoulson!
[07:34] <chrisccoulson> hi RAOF and didrocks, how are you?
[07:34] <didrocks> chrisccoulson: I'm fine thanks! Yourself?
[07:35] <chrisccoulson> didrocks, yeah, good thanks, but a bit tired
[07:39] <pitti> hey chrisccoulson
[07:39] <pitti> morning bryceh
[07:39] <RAOF> I'm pretty good.  Going for a run before lunch has offset the 7:30 start :)
[07:40] <chrisccoulson> hi pitti, how are you?
[07:40] <bryceh> hi pitti
[07:41] <pitti> chrisccoulson: I'm great, thanks!
[08:04] <didrocks> jibel: hey, FYI, with the new compiz, I tagged the regression to 0.9.5.0: https://bugs.launchpad.net/ubuntu/+source/compiz/+bugs?field.tag=0.9.5.0
[08:10] <pitti> didrocks: can you please fix "achuni" in https://launchpad.net/ubuntu/+spec/desktop-o-oneconf?
[08:10] <didrocks> pitti: ok, should have mispelled the launchpad name, taking a look in a sec
[08:16] <seb128> hey
[08:16] <pitti> bonjour seb128
[08:16] <seb128> hey pitti, how are you?
[08:16] <pitti> I'm fine, thanks! how about yourself?
[08:17] <seb128> pitti, I'm fine thanks, a bit tired, got used to go late to bed and I have difficulties to get started in the mornings ;-)
[08:18] <didrocks> hey seb128
[08:19] <seb128> didrocks, hey, nothing like a compiz abi break to start the day? ;-)
[08:19] <didrocks> seb128: exactly! Where is the fun otherwise? :-)
[08:23] <jbicha> pitti: round 2 https://code.launchpad.net/~jbicha/ubuntu/oneiric/transmission/transmission-2.32/+merge/68347
[08:24] <pitti> jbicha: did I mention that I hate UDD branches? :-)
[08:25] <rodrigo_> morning
[08:25] <pitti> hey rodrigo_
[08:26] <jbicha> pitti: I was going to do it as a ~ubuntu-desktop branch... ;-)
[08:27] <chrisccoulson> hey seb128, how are you?
[08:27] <jbicha> actually the end result was the same except for the changelog entries & dropping a lot of upstreamed patches
[08:29] <seb128> chrisccoulson, hey, I'm starting being awake and I think I'm good thanks, how are you?
[08:29] <chrisccoulson> seb128, pretty much the same, but i feel less awake ;)
[08:30] <seb128> you know what you need right...
[08:30] <seb128> coffee!!!
[08:31] <chrisccoulson> heh :-)
[08:31] <chrisccoulson> and bacon!
[08:31] <seb128> jono: ^
[08:31] <chrisccoulson> lol
[08:31] <seb128> ;-)
[08:32] <seb128> I wouldn't have done it if he was around don't worry ;-)
[08:32] <seb128> you didn't get breakfast yet? you should start with that ;-)
[08:32] <seb128> rules 1- get breakfast before starting IRC
[08:32] <seb128> or you might still be typing on IRC an hour later without coffee and starving
[08:33] <chrisccoulson> heh
[08:37] <geser> an IRC diet?
[08:39] <didrocks> seb128: btw, my server down while at Dublin was due to the power supply which died…
[08:42] <seb128> didrocks, oh ok
[08:44] <seb128> pitti, thanks for doing desktop sponsoring! ;-)
[08:44] <pitti> no worries :)
[08:47] <jbicha> pitti: thank you
[08:47] <pitti> jbicha: thanks to you!
[08:47] <huats> morning
[08:48] <didrocks> salut huats
[08:48] <huats> salut  didrocks
[08:51] <seb128> lut huats
[08:51] <huats> salut seb128
[09:16] <rodrigo_> man, this g-o-a package doesn't want to build
[09:20] <jbicha> pitti: looks like transmission needs a mir for libminiupnpc and libnatpmp
[09:21] <seb128> rodrigo_, need help with it?
[09:26] <seb128> extra mirs again...
[09:30] <seb128> jbicha, do you know if those are optional or mandatory depends?
[09:30] <seb128> jbicha, is there any chance you would like to write the mirs for those? ;-)
[09:32] <jbicha> seb128: those libs are actually in the transmission tarball & Debian is using a patch to override them with distro-maintained versions
[09:32] <seb128> yeah, security team doesn't like much bundled copy of system libraries
[09:32] <jbicha> and I can write the mirs probably tomorrow
[09:32] <seb128> it means you have to track and fix all copies when there is an issue, which doesn't really make sense
[09:32] <seb128> jbicha, thanks!
[09:33] <seb128> jbicha, no hurry for those, but we better use the system libs if we can
[09:33] <chrisccoulson> seb128, the security team must hate me then ;)
[09:34] <seb128> ups
[09:35] <seb128> don't ctrl-W in xchat :p
[09:35] <chrisccoulson> lol
[09:35] <seb128> they probably hate all the web browsers maintainers indeed
[09:35] <chrisccoulson> heh :)
[09:35] <seb128> security team is just a bunch of haters :p
[09:36] <seb128> but still we are glad to have them ;-)
[09:38] <chrisccoulson> g'ah, i wish that linking thunderbird wasn't so painful
[09:39] <chrisccoulson> my machine just grinds to a halt every time
[09:39] <chrisccoulson> i need more RAM :)
[09:43] <rodrigo_> seb128, yeah, will probably push for a review, as I don't know what's making it fail
[09:43] <seb128> rodrigo_, ok
[09:44] <rodrigo_> seb128, I'll try a little bit more 1st, as the error it is showing is supposed to be fixed with the patch I added, so not sure what's wrong really
[09:44] <seb128> rodrigo_, ok, but feel free to push, I can have a glance maybe I spot something
[09:44] <rodrigo_> seb128, ok
[09:46] <rodrigo_> seb128, lp:~rodrigo-moya/gnome-online-accounts/3_1_1_release
[09:47] <rodrigo_> seb128, it gives an error about undefined symbols, which all are in libgoa-1.0.la, that's why I add the 01_git... patch
[09:48] <seb128> rodrigo_, your rules doesn't use autoreconf.mk
[09:48] <seb128> rodrigo_, so the patch will be useless, you need to run automake to update the makefile.in
[09:48] <rodrigo_> hmm, does it need to if you don't patch configure.ac?
[09:49] <seb128> rodrigo_, well, you patch makefile.am
[09:49] <seb128> you need a makefile.am->makefile.in
[09:49] <seb128> which is automake
[09:49] <rodrigo_> ok, trying...
[09:50] <seb128> rodrigo_, yeah, builds fine with it
[09:51] <rodrigo_> seb128, ok, that was it :)
[09:51] <rodrigo_> ok then, I thought autoreconf was only needed if you patched configure, but I understand it better now :)
[09:51] <rodrigo_> seb128, thanks!
[09:51] <seb128> rodrigo_, yw
[09:52] <seb128> rodrigo_, usually autoreconf is useful if you patch any configure.in,ac or makefile.am
[09:52] <seb128> it does run autoconf, automake, aclocal, etc
[09:52] <rodrigo_> right, makes sense
[09:52] <seb128> ./configure && make use configure and makefile.in
[09:53] <seb128> the other option is to patch the makefile.in in your patch
[09:53] <seb128> but usually those are less fun since the makefile.in is autogenerated it's likely that the patch will be less trivial and not apply to new versions
[09:54] <seb128> rodrigo_, your changelog version needs a revision
[09:55] <rodrigo_> seb128, ok
[09:59] <pitti> jbicha: or disable upnp?
[10:00] <jbicha> pitti: I haven't looked to see what those libraries do, but isn't UPNP important for torrents working across NAT?
[10:01] <pitti> jbicha: ah, so the previous version used the internal libs, but already had the functinoality?
[10:01] <pitti> that would make the MIRs easier
[10:06] <njpatel_> mvo, meet bschaefer, he's the awesome dude that has added CJK support to xapian (or is adding), he has some questions for  Software Centre
[10:08] <bschaefer> mvo: Hello, my question is that it looks like the software center uses the term generator along with the parse query, but does it use the same libxapian as unity-place-applications?
[10:10] <mvo> bschaefer: hello! yes it does use the same libxapian, but its using the python bindings when unity-places-application is using the c++ lib
[10:10] <mvo> bschaefer: should not make a difference though of course
[10:10] <mvo> bschaefer: hello btw :)
[10:10] <mvo> bschaefer: I'm just leaving for lunch, I will be back in ~45min or so
[10:11] <bschaefer> mv: Alright I might have to email you then, as it is late here haha, ( -8 PST )
[10:11] <bschaefer> mvo:*
[10:12]  * mvo nods and vanishes
[10:13] <didrocks> (the xapian testsuite is huge)
[10:14] <bschaefer> didrocks: only the xapian-core matters
[10:14] <didrocks> bschaefer: right, but the package runs everything :-)
[10:15] <bschaefer> didrocks: yeah I never liked compiling it at first haha, but it seems error free so far :)
[10:16] <seb128> re
[10:16] <seb128> bah, new compiz is really slow to display things
[10:16] <didrocks> wb seb128
[10:17] <didrocks> seb128: ah, it's not only me swapping then
[10:17] <seb128> like my session takes 15 seconds to get a background when it was taking 3 seconds before
[10:17] <seb128> I restarted several times thinking it was stucked
[10:17] <didrocks> never get any stuck session, but I have the impression that compiz is slower, yeah
[10:17] <seb128> opening anything display a dialog with wrong geometry and no decoration for 2-3 seconds
[10:17] <seb128> then it gets updated as it should
[10:18] <didrocks> 12:17:43        seb128 | opening anything display a dialog with wrong geometry and no decoration for 2-3 seconds
[10:18] <seb128> happens for anything, apport dialog, gedit, nautilus
[10:18] <didrocks> -> half a second here, I reported it
[10:18] <seb128> well here it's 2-3 seconds on a modern i5 box
[10:18] <didrocks> seb128: want to confirm bug #812711 ?
[10:18] <ubot2> Launchpad bug 812711 in compiz "Some dialogs jumps before appearing" [Undecided,New] https://launchpad.net/bugs/812711
[10:18] <seb128> but using intel, I guess video matters over cpu for that issue
[10:18] <didrocks> seb128: see, for once, my box is better than yours :)
[10:20] <seb128> didrocks, done
[10:20] <didrocks> thanks :)
[10:20] <didrocks> 2-3s is scary though
[10:21] <didrocks> do you want to file one with the general slowiness?
[10:21] <seb128> didrocks, I've updated the title and raised the setting
[10:22] <seb128> didrocks, it's not slow otherwise, like workspace switch etc have no issue
[10:22] <didrocks> seb128: looks good
[10:22] <didrocks> hum, the slowliness at startup you get?
[10:22] <seb128> I just think something is resources expensive in the mapping and where a dialog takes 3 seconds the background takes 15 seconds
[10:22] <seb128> well imho it's the same issue
[10:22] <didrocks> but there is no dialog at session login?
[10:22] <seb128> just proportional to how much there is to render
[10:23] <seb128> no, but it's not specific to dialogs
[10:23] <didrocks> hum, that will do it with the wall window otherwise
[10:23] <didrocks> which doesn't seem to be the case
[10:23] <seb128> well, let's wait for smspillaz to comment, if he thinks it's a different issue I will open a new bug
[10:23] <seb128> or DBO
[10:23] <didrocks> as you wish :)
[10:24] <didrocks> seb128: we stopped adding unity master tag btw
[10:24] <seb128> but I think the background is just a nautilus ui element and getting the same issue
[10:24] <didrocks> maybe, anyway, windows are slow to drag in the expo mode as well
[10:24] <seb128> didrocks, oh ok, well I don't do it in a systematic way, I just want a bug showing up on unity lists
[10:25] <didrocks> seb128: I added the 0.9.5.0 tag on compiz bugs for all regression from this upgrade
[10:25] <seb128> ok
[10:25] <didrocks> should be easy to find them back
[10:25] <didrocks> https://bugs.launchpad.net/ubuntu/+source/compiz/+bugs?field.tag=0.9.5.0 (current list)
[10:26] <seb128> ok
[10:27] <seb128> is there a spec describing the unity dialog behaviour somewhere?
[10:27] <seb128> like what should happen in the file-selector too small to be used case
[10:27] <didrocks> seb128: nothing from what I know, I just saw some screenshots and I would like to know for that case as well
[10:27] <didrocks> I filed bug #812712 for that one so that we don't loose this issue
[10:28] <ubot2> Launchpad bug 812712 in compiz "Can't get normal modal dialog size" [Undecided,New] https://launchpad.net/bugs/812712
[10:29] <seb128> right, I noticed
[10:29] <seb128> the issue is not new with 0.9.5 though
[10:29] <seb128> well maybe the fixed size is new
[10:29] <didrocks> no, see my comment :)
[10:29] <seb128> but opening the dialog is a too small to be used geometry is buggy and was already buggy in the previous version
[10:29] <seb128> is->in
[10:30] <didrocks> "This isn't linked to 0.9.5.0 properly, but from the new unity dialog, just  keeping it there to see if a solution is possible"
[10:30] <seb128> but I didn't find a spec say if the unity dialog should go out of the container in those case
[10:30] <seb128> or if the geometry should get updated
[10:30] <didrocks> as this is part 2 of unity dialogs (the u-w-d side), I think it's fine to track it there
[10:30] <didrocks> anyway, the current behavior is buggy, and we need design feedback
[10:31] <seb128> didrocks, it's sort of bug #805975
[10:31] <ubot2> Launchpad bug 805975 in unity "Modal dialog size too small if it belongs to other modal window" [Undecided,New] https://launchpad.net/bugs/805975
[10:31] <didrocks> yeah, same issue in nested dialogs, not sure it should be fixed the same way, pointing to it on the bug report
[10:32] <didrocks> done
[10:32] <seb128> thanks
[10:32] <didrocks> thanks for finding the ref :)
[10:37] <didrocks> bschaefer: some test failed. Trying without the patches to ensure it's the cause of the issues
[10:38] <didrocks> tests*
[10:42] <bschaefer> didrocks: hmm, which ones failed?
[10:43] <didrocks> bschaefer: Running test: flintdatabaseformaterror3... FAILED
[10:44] <didrocks> in apitest
[10:44] <didrocks> bschaefer: but let me confirm first it's the patch creating an artifact in the API there
[10:44] <bschaefer> Yeah I went to straight to testing on dash I am running them right now. I knew I was forgetting something..
[10:44] <didrocks> will be long, the testsuite is long :-)
[10:44] <bschaefer> yeah haha
[10:45] <seb128> bah
[10:46] <seb128> smspillaz, didrocks: u-w-d segfaulted
[10:46] <seb128>  #0  0x0805cabf in remove_frame_window ()
[10:46] <seb128>  No symbol table info available.
[10:46] <seb128>  #1  0x0805cde7 in window_closed ()
[10:46] <didrocks> seb128: I won my personal bet! I was sure you will get a crash within a day :)
[10:47] <rodrigo_> didrocks, :)
[10:49] <seb128> will open the bug with a debug stacktrace
[10:49] <seb128> but after lunch
[10:49] <seb128> bbl
[10:49] <didrocks> seb128: enjoy
[10:56] <bschaefer> didrocks: well I am going to let this run, I am pretty tired right now so I cant help much anyway. If you could send me email about any other fails I will spend tomorrow trying to fix it
[10:57] <bschaefer> didrocks: @ brandontschaefer@gmail.com
[10:57] <didrocks> bschaefer: sure, will do! Thanks again for your work there! Have a good night :-)
[10:58] <bschaefer> didrocks: You too, and hopefully everything works out haha.
[10:59] <didrocks> bschaefer: let's hope so :)
[11:09] <seb128> oh, new decorator segfault
[11:10] <chrisccoulson> seb128, oh, i just realized that i can turn off gconf support in firefox at build time already
[11:10] <chrisccoulson> http://bazaar.launchpad.net/~mozillateam/firefox/firefox-trunk.head/revision/925
[11:10] <chrisccoulson> :-)
[11:10] <seb128> chrisccoulson, \o/
[11:10] <seb128> chrisccoulson, what about gnomevfs? ;-)
[11:10] <seb128> oh, in the same commit
[11:10] <chrisccoulson> seb128, i turned that off last cycle ;)
[11:11] <didrocks> seb128: no decorator segfault?
[11:11] <didrocks> oh new*
[11:11]  * didrocks will soon buy glasses
[11:11] <seb128> didrocks, yeah, it did it again
[11:11] <didrocks> seb128: oh do you get it?
[11:12] <seb128> didrocks, yes, the stacktrace before was from me already
[11:12] <seb128> got it twice since I upgraded
[11:12] <didrocks> is there any special way for you to trigger it or it's just random?
[11:12] <seb128> didrocks, but I learn something on the way
[11:13] <seb128> starting unity-window-decorator makes compiz hang for quite some seconds
[11:13] <seb128> so maybe the slowness issue is a decorator one
[11:13] <didrocks> seb128: yeah, more than possible as it's all linked to the unity dialog part 2
[11:14] <didrocks> seb128: can you try with gtk-w-d ?
[11:14] <didrocks> just to ensure
[11:14] <seb128> didrocks, rather random but not totally, I got it first on an apport dialog autoopening and now when doing send&receive in evolution
[11:14] <seb128> so maybe it has to do with dialogs autoopening or focus stealing prevention or something, will try to figure if I find a reliable way to trigger it
[11:15] <rodrigo_> seb128, ok, I think g-o-a is now ready for a review, so feel free to look at lp:~rodrigo-moya/gnome-online-accounts/3_1_1_release
[11:15] <rodrigo_> I'll do some g-c-c building with it in the mean time
[11:15] <didrocks> hum, interesting :)
[11:15] <seb128> didrocks, g-w-d doesn't hang compiz for a while
[11:15] <seb128> and compiz seems snappier again
[11:15] <seb128> so yeah, I bet it's unity dialog's updat
[11:15] <seb128> e
[11:15] <seb128> rodrigo_, ok, looking
[11:15] <didrocks> ok, will make sense, the core didn't change that much otherwise
[11:16] <seb128> great, I will keep the gtk decorator for now ;-)
[11:16] <didrocks> seb128: come on, come to play the slow game! :-)
[11:17]  * didrocks tries to build xapian in a pbuiler just in case…
[11:17] <seb128> is that a drinking game? ;-)
[11:17] <didrocks> I fear it's not that fun :)
[11:17] <seb128> what about xapian? is compiz using it for something?
[11:17] <didrocks> no, the cjk support we were discussing above with bschaefer and njpatel
[11:17] <seb128> oh ok
[11:17] <seb128> who is bschaefer?
[11:18] <seb128> is he new around?
[11:18] <didrocks> yeah, he's a contributor who worked on that with the help of Mikkel, it's awesome :)
[11:18] <seb128> nice
[11:19] <didrocks> apart from the testsuite, he told there is no regression and we get cjk support for free in unity-place-applications
[11:19] <seb128> \o/
[11:19] <didrocks> (and then, software-center)
[11:19] <didrocks> step 2 will be zg of course
[11:30] <seb128> rodrigo_, seems mostly fine
[11:30] <seb128> the lib should probably be named libgao-1.0-0 rather to match the soname
[11:30] <rodrigo_> seb128, oh, ok
[11:30] <seb128> standards-version is 3.9.2
[11:31] <seb128> you don't need the clean-la.mk line in the rules since we just don't ship the .la for new binaries
[11:31] <seb128> that's only useful for transitions for packages that used to ship one
[11:34] <rodrigo_> seb128, ok fixing that
[11:34] <rodrigo_> seb128, btw, works fine with control center, just a missing icon which I'm fixing
[11:34] <seb128> rodrigo_, libgoa1.0-dev should Depends on glib dev since its .pc requires gio
[11:35] <rodrigo_> seb128, right
[11:35] <seb128> rodrigo_, ok, great ;-)
[11:35] <seb128> rodrigo_, you need to build-depends on dh-autoreconf
[11:36] <seb128> rodrigo_, you can drop the quilt build-depends since you use source v3
[11:36] <seb128> rodrigo_, why the dpkg-dev build-depends?
[11:37] <rodrigo_> seb128, hmm, don't remember why I added, but there was a reason iirc
[11:37] <seb128> ok, I was rather curious about this one, usually that's not needed
[11:37] <rodrigo_> removing it, the reason will show up for itself if there is one :)
[11:37] <seb128> ;-)
[11:37] <seb128> otherwise looks good, great work
[11:38] <seb128> the copyright format is the old one also, not sure how picky other reviewers will be on this one
[11:39] <seb128> see sni-qt for a recent example using the new format
[11:40] <jbicha> I converted a copyright file & the Debian dev said it was basically a waste of time, lol
[11:41] <seb128> rodrigo_, oh, you should have a compat file with a version in it and the corresponding version in the in build-depends
[11:41] <rodrigo_> seb128, ok
[11:41] <seb128> rodrigo_, that's it I think ;-)
[11:42] <rodrigo_> seb128, hmm, what's the "corresponding version in the in build-depends"?
[11:42] <seb128> jbicha, yeah, different people have different perspective on those ;-) I tend to not bother much with those cleaning usually but for a new source as well doing it right ;-)
[11:42] <jbicha> I tried goa today on Fedora rawhide; it made setting up gmail on evolution super easy
[11:43] <rodrigo_> jbicha, yeah
[11:43] <seb128> rodrigo_, if you use version 5 you build-depends on debhelper (>= 5..) is fine
[11:43] <rodrigo_> seb128, ah, ok
[11:43] <seb128> jbicha, email or calendar or both?
[11:43] <rodrigo_> ah, already have debhelper (>= 5.0.0) on BuildDepends
[11:43] <jbicha> rawhide's scary though, I find it breaks a lot worse than Ubuntu devel
[11:44] <seb128> hehe
[11:44] <seb128> jbicha, how many distros do you run? ;-)
[11:44] <jbicha> seb128: calendar didn't seem to work for me :-(
[11:44] <seb128> jbicha, evolution-settings (when it worked) made already that super easy, it was basically "enter your email"
[11:44] <rodrigo_> seb128, ok, pushing all fixes, so what needs to be done to upload this?
[11:44] <seb128> it figures the server imap, smtp, user name, etc for you
[11:45] <jbicha> seb128: for several months it was just Ubuntu but now I have Arch & Fedora around
[11:45] <seb128> seems to segfault in 3.1 though
[11:45] <seb128> jbicha, oh, arch, you like building things ;-)
[11:45] <seb128> rodrigo_, you are not a motu right?
[11:45] <jbicha> seb128: maybe, I don't do much with it
[11:46] <seb128> oh
[11:46] <jbicha> Fedora at least is useful since it's closely aligned with Gnome and it's useful to verify if some bug affects them too
[11:46] <seb128> rodrigo_, I forgot one thing, you probably want a .symbols
[11:46] <seb128> jbicha, yeah, indeed
[11:46] <rodrigo_> seb128, yeah, right I thought about it, but forgot
[11:46] <rodrigo_> adding it
[11:46] <seb128> rodrigo_, mterry will block mirs on having one of those if you run into him ;-)
[11:47] <rodrigo_> yeah :)
[11:47] <rodrigo_> seb128, no, I'm not a motu
[11:47] <seb128> ok
[11:47] <seb128> so you need a sponsoring bug or to find a sponsor
[11:47]  * rodrigo_ looks for sponsor-seb128 :)
[11:47] <seb128> mterry, hey, do you care about the copyright file being in a recent format for new packages you review for mir?
[11:48] <seb128> rodrigo_, yeah, I can sponsor it once I'm happy with it ;-) i.e add the .symbols and maybe update the copyright and we are good I think
[11:49] <rodrigo_> seb128, ok
[11:49] <seb128> Package: libgoa-1.0-0
[11:49] <seb128> ..*
[11:49] <seb128>  This package contains the files needed to build applications that access
[11:49] <seb128>  the service.
[11:49] <seb128>  
[11:49] <seb128> rodrigo_, description copy error?
[11:52] <rodrigo_> seb128, yes
[11:56] <seif> didrocks, when do you have time
[11:59] <rodrigo_> seb128, ok, all fixed and pushed to the branch, so feel free to sponsor :)
[11:59] <seb128> rodrigo_, ok, will do that in a bit
[12:00] <seb128> just finishing something else I'm on first
[12:00] <rodrigo_> seb128, no hurry, I'll fix the g-c-c bug in the meanwhile (the missing icon)
[12:00] <seb128> rodrigo_, ok, is that one we ship in the wrong gnome-icon-theme binary maybe? or is that an upstream bug?
[12:01] <rodrigo_> well, and I'll go out for lunch first, now that pedro_ is here, so that I can avoid listening to him for a while :-)
[12:01] <pedro_> rodrigo_, that'd be perfect so i can assign thousand of bugs to you while you're not around :-)
[12:01] <rodrigo_> seb128, it's an icon in g-c-c sources, so it doesn't get installed when building g-c-c with g-o-a
[12:01] <seb128> oh ok
[12:01] <rodrigo_> pedro_, no please, I'm not the top on the list anymore, feel free to harass someone else :D
[12:01] <seb128> pedro_, ola!
[12:02] <pedro_> salut seb128 :-)
[12:02] <seb128> pedro_, don't listen to rodrigo_, he can take on some extra bugs, he likes g-s-d and g-c-c bugs
[12:02] <rodrigo_> pedro_, heh, there you have a person to harass now, seb128 :)
[12:04] <pedro_> heh :-)
[12:04] <rodrigo_> ok, lunch now, bbl
[12:13] <meborc> Hi all
[12:14] <meborc> is the current way the bar and indicator area is displayed on multiple monitors the intended way?
[12:15] <meborc> What I mean is that if I have 2 monitors, I have top-bars on both of them including the indicator area?
[12:16] <meborc> That is major showstopper for me. I have been used to having more screen real-estate on the second monitor
[12:16] <meborc> any ideas? blueprints? plans? in that regard      - Thanks!
[12:19] <jbicha> meborc: design issues are discussed in #ayatana but yes the design decision is that the "indicator" system menus show on all monitors
[12:20] <meborc> jbicha: ok, thank you! I will go there and at least try to make a case for a change :) have a nice day
[12:23] <didrocks> seif: John is sick today, so probably later this week?
[12:28] <mpt> jasoncwarner_, hi, was it you who JohnLea discussed with about disabling Suspend and Hibernate by default on uncertified hardware?
[12:29] <mpt> Or was it someone else?
[12:32] <pitti> this seems like throwing out the baby with the bathwater
[12:32] <pitti> we break 99% of machines because 1% have trouble with suspend?
[12:33] <seb128> it seems it could be discussed for hibernate
[12:33] <seb128> but yeah, suspends works nowadays so no need to break that
[12:34] <mterry> seb128, no, I don't care about copyright format
[12:34] <pitti> I really doubt that we can do something about the hibernate certification
[12:34] <seb128> mterry, ok, great ;-)
[12:34] <pitti> I think in most cases it's specific to the swap space you configure, or whether you plug in a particular usb device or what not
[12:35] <pitti> we enable it by default or we don't, but by-machine doesn't seem practical to me
[12:35] <seb128> pitti, well, we could opt out hibernate by default with a g-c-c settings to turn it on
[12:35] <pitti> seb128: I agree; but not by-machine
[12:35] <seb128> right
[12:35] <seb128> well "by machine" in the sense of some oem could decide to turn it on on their image
[12:36] <pitti> right, I meant having large white/blacklists in pm-utils
[12:36] <seb128> but yeah, let's not do an hardware detection or an hardware list in ubuntu
[12:36] <pitti> hibernation isn't really hardware/platform specific
[12:36] <pitti> it sucks everywhere equally :)
[12:37] <seb128> ;-)
[12:39] <seb128> pitti, btw is your indicator still not turning blue on new messages?
[12:39] <seb128> it works there
[12:39] <pitti> I don't think so
[12:39] <pitti> seb128: ping me on jabber again?
[12:46] <seb128> ok
[12:47] <seb128> so it was not kenvandine's fault but mvo's one ;-)
[12:47] <mvo> hm?
[12:47] <kenvandine> hey seb
[12:47] <seb128> pitti, one other case of "recommends didn't get installed on upgrade"
[12:47] <kenvandine> what didn't i do :)
[12:47] <pitti> hey kenvandine
[12:47] <mvo> ha! thats fixed with the new apt
[12:47] <seb128> kenvandine, pitti didn't have telepathy-indicator installed
[12:47] <pitti> kenvandine: I got blue envelopes back!
[12:47] <kenvandine> haha
[12:48] <kenvandine> mvo, that is pretty frustrating :)
[12:48] <seb128> mvo, right, I was mostly teasing you ;-)
[12:48] <seb128> kenvandine, he said that should be fixed for a week, apt blocks those updates now
[12:48] <seb128> like put them on hold
[12:48] <kenvandine> oh, good
[12:48] <seb128> the same way as if you have a new depends
[12:50] <seb128> kenvandine, wasn't bug #257190 supposed to be fixed?
[12:50] <ubot2> Launchpad bug 257190 in telepathy-gabble "Setting status to 'Hidden' changes status to 'Busy' instead" [Low,Fix released] https://launchpad.net/bugs/257190
[12:50] <seb128> pitti, ^
[12:50] <pitti> I still get it here
[12:50] <seb128> do you get it from the empathy ui as well?
[12:50] <seb128> or only from the indicator?
[12:51] <pitti> seb128: same bug from the ui
[12:51] <seb128> ok
[12:51] <seb128> pitti, are you connected only to jabber?
[12:51] <pitti> seb128: no, also google talk, some sip services, etc.
[12:51] <seb128> I think part of the issue is due to protocols which don't handle hidden
[12:51] <seb128> the status is not by protocol
[12:51] <pitti> trying
[12:52] <seb128> like if you are connected to jabber only it should work
[12:52] <kenvandine> i think that is tricky, depending on accounts
[12:52] <kenvandine> the indicator tries to set it to the best match for all accounts
[12:52] <kenvandine> there is a tp api for that
[12:52] <pitti> right, it flips to invisible, and .3 s later it goes back to busy
[12:52] <seb128> kenvandine, right, it's not specific to the indicator since the empathy ui has the same issue
[12:53] <kenvandine> pitti, killall telepathy-indicator
[12:53] <kenvandine> see if it still does that
[12:53]  * kenvandine hopes he didn't do something bad
[12:53] <kenvandine> i doubt that would make a difference though
[12:53] <kenvandine> tp-indicator just listens and does things as needed
[12:54] <pitti> kenvandine: confirmed it's gtalk -- if I disable the account, and leave bonjour and the sips ones, it works
[12:54] <kenvandine> pitti, so gtalk might not support it
[12:55] <pitti> kenvandine: the fun thing is, if I flip gtalk back on, status changes from invisible to busy, but in the accounts dialog, gtalk is shown as invisible :)
[12:55] <kenvandine> hehe
[12:56] <seb128> pitti, https://bugzilla.gnome.org/show_bug.cgi?id=550502
[12:56] <ubot2> Gnome bug 550502 in General "Invisible Status Is Not Working Correctly" [Normal,New]
[12:57] <seb128> or https://bugs.freedesktop.org/show_bug.cgi?id=30765
[12:57] <ubot2> Freedesktop bug 30765 in tp-glib "Add most-available-requested-presence" [Normal,New]
[12:57] <pitti> seb128: thanks
[12:59] <kenvandine> they have an old branch for that
[12:59] <kenvandine> but never merged
[12:59] <pitti> hm, gnome-icon-theme FTBFSes now, configure fails with "configure: error: Could not find gtk-update-icon-cache"
[12:59] <pitti> seems there's only -3.0 these days
[13:00] <pitti> oh, libgtk-3-bin diverts it to update-icon-caches.gtk2
[13:00] <pitti> err, no, what?
[13:01] <pitti> /usr/bin/gtk-update-icon-cache -> ../lib/i386-linux-gnu/libgtk2.0-0/gtk-update-icon-cache
[13:01] <pitti> c'est ne pas i386
[13:01] <seb128> lol
[13:01] <seb128> works for me on i386 :p
[13:01] <seb128> but it's quite weird
[13:01] <pitti> you and your pre-medieval architectures
[13:02] <seb128> it's coming from the stone age, it's solid and tested ;-)
[13:02] <didrocks> mpt: hey, small question about usc redesign, I'm ready to do the OneConf ui part, did you get a chance to work on that?
[13:02] <mpt> didrocks, I did not, sorry
[13:02]  * pitti backs out from fixing gnome-icon-theme, and looks into fixing gtk2 then
[13:03] <didrocks> mpt: do you think you'll have time soon or that we can experiment something? all the rest is almost finished and it's the only thing blocking putting OneConf by default AFAIK
[13:03] <seb128> pitti, it's weird there was no recent gtk2 or 3 updates
[13:03] <didrocks> mpt: btw, I made the screenshot icon preview :)
[13:03] <pitti> seb128: last g-i-t upload was June 29
[13:04] <pitti> seb128: last gtk+2.0 upload was June 30, with "Build for multiarch"
[13:04] <seb128> pitti, well, for sure gtk-update-icon-cache is used out of the g-i-t build
[13:04] <seb128> like for anybody installing an icon theme or upgrading one
[13:04] <seb128> or a package installing an icon in the icon theme dir
[13:05] <seb128> pitti, when was that symlink updated?
[13:05] <seb128> on your disk
[13:05] <pitti> lrwxrwxrwx 1 root root 55 2011-06-30 16:19
[13:05] <pitti> sounds like the time of the most recent gtk+2.0 upload
[13:05] <seb128> hum ok
[13:06] <seb128> weird that nobody notice it during this time, I though that was called to update icon indexes when installed a package shipping one
[13:07] <pitti> but that broken symlink is in the actual .deb
[13:07] <seb128> oh
[13:07] <pitti> seb128: presumably we are using the -3.0 version now?
[13:07] <seb128> the trigger uses the versionned name
[13:07] <seb128> pitti, right
[13:07] <seb128> that explains it
[13:07] <pitti> lrwxrwxrwx root/root         0 2011-06-30 16:19 ./usr/bin/gtk-query-immodules-2.0 -> ../lib/i386-linux-gnu/libgtk2.0-0/gtk-query-immodules-2.0
[13:07] <pitti> same problem with that one
[13:08] <pitti> ^ from less libgtk2.0-bin_2.24.5-0ubuntu3_all.deb
[13:08] <seb128> liking an error in the rules
[13:08] <pitti> oh, wait
[13:08] <pitti> _all.deb ??
[13:08] <seb128> arf
[13:08] <pitti> Package: libgtk2.0-bin
[13:08] <pitti> Section: misc
[13:08] <pitti> Architecture: all
[13:08] <pitti> indeed
[13:09] <pitti> so weird that we never caught this
[13:09] <seb128> same for libgtk-3-bin
[13:09] <seb128> oh
[13:09] <seb128> -bin only has symlinks
[13:09] <pitti> bzr blame is for rev 1
[13:09] <seb128> the actual binaries are in the lib
[13:09] <seb128> -bin is only symlinks and manpages
[13:10] <pitti> lrwxrwxrwx 1 root root 43 2011-07-15 21:05 /usr/bin/gtk-update-icon-cache-3.0 -> ../lib/libgtk-3-0/gtk-update-icon-cache-3.0
[13:10] <pitti> for -3.0 the symlinks aren't platform specific
[13:10] <pitti> but for 2.0 they seem to be
[13:10] <seb128> pitti, gtk3 is not multiarched yet
[13:10] <seb128> it was not out when slangasek started his work
[13:10] <pitti> seb128: ok, fixing gtk2.0 for now
[13:10] <seb128> pitti, just make the -bin arch any I guess
[13:10] <pitti> right
[13:12] <pitti> building
[13:14] <pitti> didrocks, njpatel: what's the standard icon size for launcher icons? something like 48x48?
[13:15] <didrocks> pitti: right, 48x48
[13:15] <pitti> merci
[13:24] <mpt> didrocks, do you mean installing it in Ubuntu by default?
[13:24] <seb128> kenvandine, do you want to do a round of testing and sponsor https://code.launchpad.net/~rodrigo-moya/gnome-online-accounts ?
[13:24] <seb128> kenvandine, it seems fine to me, I can NEW it if somebody else do the upload ;-)
[13:24] <kenvandine> seb128, sure
[13:24] <mpt> didrocks, sorry, what screenshot icon preview is that?
[13:24] <kenvandine> i'll do it now
[13:24] <seb128> kenvandine, i.e I already did a review from a NEW perspective so it just needs an uploader, if you want to give it a round of testing as well you are welcome though
[13:25] <seb128> kenvandine, thanks
[13:27] <seb128> oh, if somebody is interested by packaging a new source: http://p11-glue.freedesktop.org/p11-kit.html
[13:27] <seb128> next gnome-keyring will depends on it
[13:27] <seb128> I've added it to the etherpad
[13:30] <didrocks> mpt: right, the plan was to put OneConf by default this cycle. For the preview, it's putting a preview of the wallpaper for each computer/device registered in OneCon
[13:30] <didrocks> OneConf*
[13:31] <mpt> didrocks, ah, nice
[13:35] <kenvandine> seb128, is there no UI in the goa package?
[13:35] <kenvandine> i expected it to be in the control-center
[13:36] <seb128> kenvandine, it's in g-c-c, it needs a rebuild with goa once that one is in
[13:36] <kenvandine> ah
[13:36] <kenvandine> ok
[13:36] <seb128> kenvandine, we patched g-c-c to disable it since that was not packaged
[13:36] <seb128> kenvandine, you can probably rebuild gcc and drop the patch rodrigo added to disable it
[13:36]  * kenvandine uploads goa in the mean time
[13:48] <rodrigo_> kenvandine, oh, uploaded already?
[13:49] <kenvandine> rodrigo_, yup
[13:49] <rodrigo_> ok, so now we need a MIR
[13:49]  * rodrigo_ MIR's
[13:49] <kenvandine> rodrigo_, cool
[13:49] <rodrigo_> kenvandine, btw, no need to drop the patch, just rebuild it with libgoa-dev installed
[13:50] <kenvandine> rodrigo_, will do
[13:50] <rodrigo_> but I'll submit a package with the part of the patch for disabling the onlñine accounts panel, as soon as g-o-a is in main
[13:51] <seb128> rodrigo_, you need to mir for some of the depends also it seems
[13:51] <rodrigo_> seb128, yes, was looking at the build failure
[13:52] <seb128> rodrigo_, that's yet something else
[13:52] <seb128> rodrigo_, you lack a build-depends as well indeed it seems
[13:57] <smspillaz> seb128: backtrace ?
[14:01] <seb128> smspillaz, I will get one with debug symbols next time it happen, I didn't have debug symbols and the one I got was pretty useless
[14:03] <seb128> smspillaz, btw running u-w-d "blocks" compiz for at least 5 seconds there
[14:03] <smspillaz> seb128: right, it's generating a bunch of default decorations I need to optimize it
[14:03] <seb128> ok
[14:03] <smspillaz> (I needed that to make dialogs work, but it's not efficient)
[14:04] <smspillaz> seb128: I need to work on this settings key override stuff now
[14:04] <smspillaz> (for didrocks)
[14:04] <seb128> smspillaz, btw is the wanted behaviour speced on the wiki or somewhere?
[14:04] <desrt> didrocks: ping
[14:05] <seb128> smspillaz, like is there a spec describing what is supposed to happen in different scenarios, with interaction models etc?
[14:05] <smspillaz> seb128: I think there is some somewhere
[14:06] <seb128> will ask john when he's back, thanks
[14:08] <desrt> smspillaz: so i talked to matthias about GSettings key names
[14:08] <desrt> smspillaz: i plan to lift to 1024 chars.  will that make you happy forever?
[14:09] <didrocks> 32 to 1024, waow :)
[14:09] <seb128> bah
[14:09] <smspillaz> desrt: can we lift the restriction requiring no use of "_", "?" etc and make them CaSeSeSiTiVe?
[14:09] <seb128> pitti, did you clean all the i386 retracer logs?
[14:10] <smspillaz> :p
[14:10] <pitti> seb128: I moved the amd64 ones to ../log-archive/
[14:10] <desrt> i think you can have caps already
[14:10] <seb128> pitti, he had an empty log, no rotated log and a lock file, I just removed the lock
[14:10] <pitti> seb128: I didn't touch the i386 ones
[14:10] <smspillaz> desrt: nope
[14:10] <seb128> pitti, doh, I meant amd64
[14:10] <seb128> pitti, thanks ;-)
[14:10] <desrt> ah.  sorry about that.
[14:10] <desrt> i'd prefer not to lift those.
[14:10] <pitti> seb128: a few hours ago I noticed that i386 was working, and amd64 was broken, and I fixed/cleaned the amd64 one
[14:10] <smspillaz> desrt: though, there's only one key with caps :)\
[14:10] <smspillaz> so I can just change it
[14:11] <seb128> pitti, ups, it's still busy on the dup consolidation
[14:11] <seb128> pitti, that takes ages nowadays
[14:11] <pitti> oh, I thought we commented it out
[14:11] <pitti> because it crashed
[14:11] <pitti> so it's actually running now?
[14:11] <pitti> it hasn't run for ages, so it'll certainly take a while to review all the crash bugs of the last weeks
[14:12] <seb128> pitti, well I didn't change anything, the crontab line is not commented and there is a dupcheck job in the processes list
[14:13] <pitti> seb128: I mean the consolidation part
[14:13] <seb128> pitti, the log has
[14:13] <seb128> 07/19/11 14:10:01: Initializing crash digger, using chroot map None
[14:13] <seb128> 07/19/11 14:10:01: Consolidating duplicate database...
[14:13] <pitti> but I recently updated bzr, I guess I might have reverted that
[14:13] <pitti> seb128: as long as it's running, that's fine
[14:13] <seb128> pitti, it's sitting there
[14:13] <pitti> if that actually stopped crashing now, then let's have it catch up
[14:13] <seb128> hum
[14:13] <seb128> in fact the log has
[14:13] <seb128> 07/19/11 12:00:01: Initializing crash digger, using chroot map None
[14:13] <seb128> 07/19/11 12:00:02: Consolidating duplicate database...
[14:13] <seb128> 07/19/11 14:10:01: Initializing crash digger, using chroot map None
[14:14] <seb128> 07/19/11 14:10:01: Consolidating duplicate database...
[14:14] <seb128>  
[14:14] <pitti> oh, it did crash silently then?
[14:14] <seb128> pitti, so I'm wondering it if took 2 hours to crash
[14:14] <seb128> pitti, I will run it by hand
[14:14] <pitti> ah, was just about to do that
[14:14] <pitti> but yes, fine if you do
[14:14] <pitti> please run in screen
[14:14] <seb128> pitti, don't bother, I'm on it
[14:15] <seb128> ok
[14:15] <pitti> if it still fails, I'll comment out the consolidation again
[14:15] <rodrigo_> kenvandine, just pushed a build fix to lp:~rodrigo-moya/gnome-online-accounts/3_1_1_release, so if you can sponsor that to fix the build problems o my 1st package?
[14:15] <kenvandine> rodrigo_, sure
[14:15] <seb128> rodrigo_, you can move it to ~ubuntu-desktop btw
[14:15] <rodrigo_> seb128, ok
[14:16] <kenvandine> seb128, i did already
[14:16] <kenvandine> i'll merged rodrigo's branch
[14:17] <rodrigo_> kenvandine, ah, sorry, just pushed it also
[14:17] <kenvandine> rodrigo_, no worries
[14:17] <rodrigo_> can it also be added to the desktop packageset?
[14:17] <rodrigo_> I guess a mail to cjwatson is needed? :)
[14:17] <seb128> rodrigo_, indeed
[14:18] <rodrigo_> sent
[14:19]  * rodrigo_ writes MIR report
[14:19] <desrt> smspillaz: okay.  limit is now 1024 upstream.
[14:25] <smspillaz> desrt: lovely
[14:28] <mvo> chrisccoulson: what is a good name for the flag in the debian/control file for e.g. firefox to prevent unattended inplace upgrades. XB-Upgrade-Requires: {app-restart,session-restart,system-restart} ?
[14:28] <dobey> pitti, seb128: the plan is to not have gtk2 on the CD, right?
[14:28] <seb128> dobey, that's the goal
[14:28] <seb128> dobey, not sure we will get there this cycle but we are trying to
[14:28] <pitti> dobey: not necessarily for oneiric, but hopefully in the next few cycles
[14:29] <dobey> ah ok
[14:29] <rodrigo_> of these deps: http://pastebin.com/2gWTXHcE <- only librest needs to be MIR'ed, right?
[14:29] <dobey> i guess banshee and tomboy are the big blockers for getting gtk2 off the disc?
[14:29] <seb128> rodrigo_, yes
[14:29] <seb128> dobey, and firefox and libreoffice
[14:29] <rodrigo_> ok, another MIR needed
[14:30] <dobey> seb128: oh, right. :(
[14:30] <seb128> dobey, well apparently firefox has a gtk3 patch which is somewhat working
[14:39] <ronoc> rodrigo_, hey, just plugging together that new indicator. 'gnome-control-centre bluetooth' call fails to raise the bluetooth dialog, it just brings up the control centre
[14:39] <ronoc> is that call correct ?
[14:39] <rodrigo_> ronoc, yes
[14:39] <ronoc> just a bug ?
[14:40] <rodrigo_> ronoc, works for me, so do you have /usr/lib/control-center-1/panels/libbluetooth.so ?
[14:40] <seb128> works for me as well
[14:40] <seb128> ronoc, is gnome-bluetooth installed?
[14:40] <rodrigo_> ronoc, or any output if you run from the terminal?
[14:41] <mvo> hey mpt - Im working on the unattended-upgrades stuff currently, there is a workitem about asking if the user should get any sort of notification about upgrades getting installed in the background.  I can't find anything about this in the SoftwareUpdater spec, does that mean that the answer is "no" (i.e. just no notifications of any sort that something is going on)?
[14:42] <ronoc> seb128, rodrigo_ its installed, the .so is in the right place. gnome-bluetooth though is not in my path
[14:43] <seb128> ronoc, can you pastebin what you typed and the command line log?
[14:44] <ronoc> seb128, gnome-bluetooth: command not found
[14:44] <seb128> ronoc, it should be "gnome-control-center bluetooth"
[14:44] <seb128> not gnome-bluetooth
[14:44] <seb128> it's a control center panel
[14:45] <ronoc> seb128, gnome-control-center bluetooth brings up the control centre but not the actual bluetooth panel
[14:45] <ronoc> thats the problem
[14:45] <seb128> ronoc, can you pastebin the command line log when you run that?
[14:46] <seb128> ronoc, does "gnome-control-center background" work?
[14:46] <seb128> or sound
[14:46] <ronoc> seb128, display and sound work
[14:46] <ronoc> http://paste.ubuntu.com/647343/
[14:46] <ronoc> seb128, ^
[14:47] <ronoc> seb128, background works
[14:47] <seb128> ronoc, $ strace gnome-control-center bluetooth 2>&1 | grep bluetooth.so
[14:47] <seb128> what does that say?
[14:48] <ronoc> seb128, no trace
[14:48] <ronoc> grep couldnt find anything
[14:48] <seb128> ok
[14:48] <seb128> if you drop .so?
[14:49] <seb128> $ strace gnome-control-center bluetooth 2>&1 | grep bluetooth
[14:49] <seb128> then pastebin it
[14:49] <mpt> mvo, correct, no notifications
[14:49] <jibel> didrocks, with latest compiz everything becomes sluggish after using the desktop for few hours. To the point I'll reboot in a minute. Is it known or just me ?
[14:50] <cdbs> didrocks: pingw
[14:50] <didrocks> jibel: hum, slowliness at start is known
[14:50] <didrocks> cdbs: hey
[14:50] <didrocks> jibel: become slower and slower isn't the case here (didn't restart since 9am)
[14:50] <mvo> mpt: great, thanks
[14:50] <cdbs> didrocks: Wouldn't mind if I transfer over 3 WIs on the spec over to you or <insert someone here> ?
[14:50] <seb128> jibel, did you increased memory usage from the compiz process?
[14:50] <cdbs> where the spec is the unity integration spec
[14:51] <didrocks> jibel: please open a bug if it's a regression and tag it 0.9.5.0. It's not the same than before the upgrade with just unity
[14:51] <didrocks> cdbs: no, do not hesitate, the sooner is the better
[14:51] <didrocks> cdbs: which one in particular?
[14:51] <ronoc> seb128, http://paste.ubuntu.com/647348/
[14:51] <cdbs> didrocks: the wm class matching one, and the nautilus ones
[14:52] <cdbs> I'll do the SC integration
[14:52] <seb128> ronoc, ls -l /usr/lib/control-center-1/panels/libbluetooth.so ?
[14:52] <didrocks> cdbs: "wm class" matching?
[14:53] <jibel> seb128, no, and the process doesn't seem to use an unreasonable amount of memory (162MB)
[14:53] <jibel> didrocks, ok will do
[14:53] <cdbs> didrocks: err, wmclass matching
[14:53] <didrocks> cdbs: what the WI title exactly, can you paste them there, please?
[14:53] <cdbs> didrocks: "wmclass matching in desktop files for getting quicklists even if you don't pin the right one"
[14:54] <didrocks> cdbs: I don't remember writing that one or what it is about, sounds more a bamf WI
[14:54] <ronoc> seb128, http://paste.ubuntu.com/647352/
[14:54] <cdbs> didrocks: yeah, even I didn't get it well. bamf should deal with it. DBO ?
[14:55] <seb128> ronoc, that's puzzling
[14:55] <ronoc> indeed
[14:55] <didrocks> cdbs: and the nautilus is just the quicklist one, isn't it?
[14:55] <ronoc> its seems to be there and everything but just not showing up
[14:55] <ronoc> its a new install this machine so shouldn't be an upgrade problem
[14:55] <cdbs> didrocks: yeah, and I'll do the copy progress
[14:56] <cdbs> didrocks: only the quicklist one, and the wmclass one, whatever it is :)
[14:56] <seb128> ronoc, does it show up in the gnome-control-center shell?
[14:56] <ronoc> yes
[14:56] <ronoc> but I'll test it
[14:56] <seb128> can you open it?
[14:56] <seb128> rodrigo_, ^ help there ;-)
[14:56] <ronoc> seb128, no
[14:56] <ronoc> that's it
[14:57] <seb128> ronoc, I bet it's your broken pulse install again
[14:57] <seb128> rodrigo_, unping
[14:57] <ronoc> maybe
[14:57] <didrocks> cdbs: I won't do the wmclass if I don't understand what it is, just land it over to DBO for now :) give me the quicklist one
[14:57] <seb128> ronoc, is there any way you could try with the ubuntu pulse?
[14:57] <cdbs> didrocks: alright, making the changes
[14:57] <didrocks> thanks
[14:57] <ronoc> I can but for now I would rather leave the hookie pulse in place in order to test a feature Harry, diwic and I are working no
[14:58] <ronoc> on even
[14:58] <ronoc> seb128, i trust it works :)
[14:58] <seb128> ronoc, ok, so just assume the call will work on a non hacked system like yours ;-)
[14:58] <ronoc> seb128, exactly
[14:58] <ronoc> fingers, toes and eye lashes crossed :)
[14:58] <cdbs> didrocks: Done. You have the quicklist one, and DBO has the *ahem* one :)
[14:58] <DBO> ahem?
[14:59] <DBO> link?
[14:59] <seb128> brb
[15:01] <cdbs> DBO: https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-default-apps-unity-integration
[15:02] <cdbs> DBO: See the WI assigned to you
[15:02] <DBO> cdbs, I dont see any
[15:02] <DBO> ah
[15:03] <DBO> I see it now
[15:03] <cdbs> DBO: Check clearly, you're jassmith right?
[15:03] <DBO> yeah sorry
[15:03] <DBO> I was expecting Jason Smith
[15:07] <seb128> rodrigo_, do you know if g-c-c specify things like the login shell to use to accountsservice?
[15:07]  * cdbs leaves
[15:07] <seb128> rodrigo_, default seems to be sh rather than bash, is that a g-c-c or accountsservice bug?
[15:10] <rodrigo_> seb128, hmm, I think it's accountsservice
[15:11] <rodrigo_> yes, g-c-c does not tell it which shell to use
[15:12] <chrisccoulson> seb128, accountsservice doesn't specify a shell either, it just uses the default, determined by useradd
[15:12] <chrisccoulson> (which is defined in /etc/default/useradd)
[15:12] <chrisccoulson> SHELL=/bin/sh
[15:13] <chrisccoulson> mvo - XB-Upgrade-Requires looks ok (sorry, i only just saw your message)
[15:13] <seb128> chrisccoulson, shouldn't it use adduser rather than useradd?
[15:14] <seb128> "       useradd is a low level utility for adding users. On Debian,
[15:14] <seb128>        administrators should usually use adduser(8) instead.
[15:14] <seb128> "
[15:14] <seb128> it's from the useradd manpage
[15:14] <chrisccoulson> seb128, i'm not sure. it seems that adduser sets a different login shell by default too
[15:15] <seb128> no
[15:15] <chrisccoulson> i'm not sure which is the correct one to use though
[15:15] <seb128> adduser uses bash by default
[15:15] <seb128> it doesn't make sense to use dash as an user shell
[15:16] <seb128> $ grep sh adduser.conf
[15:16] <seb128> # The DSHELL variable specifies the default login shell on your
[15:16] <seb128> DSHELL=/bin/bash
[15:16] <chrisccoulson> seb128, it doesn't look like it would be difficult to use adduser, but is that more correct than changing the default in /etc/default/useradd to bash?
[15:16] <seb128> well the useradd manpage recommends using adduser
[15:17] <seb128> the useradd default should probably be fixed on ubuntu as well yes
[15:18] <seb128> but still if useradd documentation recommends it to not be used it should perhaps not be ;-)
[15:18] <chrisccoulson> seb128, is adduser debian/ubuntu specific?
[15:19] <seb128> seems so
[15:19] <seb128> google says that on redhat it's a symlink to useradd
[15:19] <pitti> jasoncwarner, Sweetshark, bryceh, chrisccoulson, didrocks, tremolux, Riddell, kenvandine, cyphermox, mterry, rodrigo_, seb128, tkamppeter, pedro_: meeting reminder in 10 mins
[15:19] <seb128> chrisccoulson, http://serverfault.com/questions/218993/whats-the-difference-between-useradd-and-adduser says
[15:19] <seb128> "On Ubuntu, useradd simply creates an entry in the user database (/etc/passwd etc.).
[15:20] <seb128> adduser on the other hand also creates a home directory for the user, populates it with the content of /etc/skel and lets you set the password interactively."
[15:21] <seb128> let me move that to #ubuntu-devel
[15:21] <seb128> it's a bit out of desktop discussions ;-)
[15:21] <chrisccoulson> sure :)
[15:22] <pitti> kenvandine: do you want to put the partner update to https://wiki.ubuntu.com/DesktopTeam/Meeting/2011-07-19 before the meeting?
[15:22] <kenvandine> pitti, doing it now :)
[15:29]  * pedro_ waves
[15:30] <seb128> hey
[15:31] <seb128> pitti, meeting ;-)
[15:31]  * kenvandine waves
[15:31] <pitti> oops
[15:31] <pitti> jasoncwarner, Sweetshark, bryceh, chrisccoulson, didrocks, tremolux, Riddell, kenvandine, cyphermox, mterry, rodrigo_, seb128, tkamppeter, pedro_: meeting now
[15:31] <pitti> https://wiki.ubuntu.com/DesktopTeam/Meeting/2011-07-19
[15:31] <pitti> hello everyone!
[15:32] <didrocks> hey
[15:32] <tremolux> hiya
[15:32] <rodrigo_> hi all
[15:32] <mterry> hi
[15:33] <pitti> so, let's dive right in
[15:33] <pitti> kenvandine: thanks for the partner update on the wiki
[15:33] <pitti> kenvandine: so the new icon/name thing in the panel without a menu is now not the me menu any more?
[15:33] <kenvandine> pitti, right
[15:33] <kenvandine> that is provided by indicator-session
[15:34] <kenvandine> and is only displayed if you have more than one user
[15:34] <pitti> kenvandine: let me guess, wasting 15% of your panel to show your own name was a design decision? :-)
[15:34] <kenvandine> https://wiki.ubuntu.com/MessagingMenu
[15:34] <kenvandine> for the design
[15:34] <kenvandine> :-D
[15:34] <pitti> kenvandine: is the absense of a menu a bug, or by design?
[15:34] <kenvandine> by design
[15:34] <kenvandine> however
[15:35] <kenvandine> it means guest session is missing if you only have one account
[15:35] <pitti> then breaking the menu structure certainly is a bug
[15:35] <tkamppeter> hi
[15:35] <pitti> kenvandine: well, it's missing now, too
[15:36] <pitti> kenvandine: the session menu only has the logout/reboot stuff, and there's no change user/guest session etc. anywhere
[15:36] <pitti> or a link to your personal settings
[15:36] <kenvandine> rightt
[15:36] <kenvandine> that stuff is in the "User menu"
[15:36] <kenvandine> which is only displayed if you have more than one account
[15:36] <pitti> but didn't you just say that it's designed to not have a menu?
[15:36] <kenvandine> so no way to get to the guest session unless you have multiple accounts
[15:36]  * pitti has three accounts on this machine
[15:37] <seb128> the menu not showing is an unity bug
[15:37] <kenvandine> oh, you see your name and no menu right?
[15:37] <kenvandine> that is a bug
[15:37] <seb128> njpatel said he would fix it for this week unity update
[15:37] <pitti> ah, ok
[15:37] <seb128> it works in the unity greeter
[15:37] <kenvandine> tedg is supposed to be working out what we are supposed to do about the lack of a menu for guest session, etc
[15:37] <kenvandine> for single users
[15:37] <seb128> something is wrong in the unity panel loader
[15:37] <pitti> seb128: not really -- I get an [Invalid UTF-8] there :)
[15:38] <pitti> anyway, not meeting fodder at this point any more
[15:38] <pitti> but I was interested in the general direction
[15:38] <seb128> pitti, same bug it displays a menu when clicking on it ;-)
[15:38] <pitti> thanks for the update
[15:38] <kenvandine> np
[15:38] <pitti> still ugh@ full user name
[15:38] <pitti> kenvandine: whom can we talk to for changing this back to the login name?
[15:39] <pitti> on a netbook screen, "Jean-Baptiste Lallement" would take a third of the screen, leaving not enough room for menus
[15:39] <pitti> we should totally require designers to have four names!
[15:39] <kenvandine> mpt i think
[15:39] <kenvandine> haha
[15:39] <kenvandine> mpt ^^
[15:39] <pitti> "Matthew-Paul Thomas" isn't exactly short either
[15:39] <kenvandine> mpt,  lets change your name
[15:41] <seb128> it's displaying seb128 here
[15:41] <seb128> but that's probably because I didn't put my full name with my user account ;-)
[15:41] <kenvandine> hehe
[15:41] <didrocks> it's displaying nothing there, and I have two users…
[15:42] <pitti> didrocks: anything to discuss for unity?
[15:42] <pitti> yay for indicator-gtk3
[15:42] <didrocks> pitti: nothing more than what the report said :)
[15:42] <pitti> cool
[15:43] <pitti> tremolux: thanks for the s-c report, anything to discuss there?
[15:43] <pitti> tremolux: do you think the new design branch will land for alpha-3, so that we can get some bigger feedback?
[15:43] <tremolux> pitti: nope, mainly trying to catch up some work items this week
[15:44] <tremolux> pitti: still to early to tell for sure, but I would tend to think it won't
[15:44] <tremolux> pitti: as default, I mean
[15:44] <pitti> tremolux: so it'll be a perky penguin thing then?
[15:45] <tremolux> pitti: heh, well, it's not ruled out yet for O, but..
[15:45] <tremolux> pitti: it's a lot of changes
[15:45] <tremolux> pitti: probably perky, I guess I'm saying
[15:46] <pitti> ok, thanks for the heads-up
[15:46] <pitti> tremolux: well, the current s-c works, so we aren't "under the gun" here, right?
[15:46] <pitti> tremolux: or did we get regressions under gnome 3?
[15:47] <tremolux> pitti: exactly, and we are pulling in some 5.0 features still
[15:47] <tremolux> pitti: no, it seems in good shape
[15:47] <pitti> good to hear; thanks for the update!
[15:47] <tremolux> pitti: thanks!
[15:47] <pitti> which brings us to ... http://status.ubuntu.com/ubuntu-oneiric/canonical-desktop-team-oneiric-alpha-3.html :)
[15:47] <pitti> chrisccoulson: what's the current word on the tbird integration?
[15:48] <pitti> chrisccoulson: seems some are actually done, like charline's user testing
[15:48] <chrisccoulson> yeah, that one is done now
[15:48] <pitti> and the "Discuss strategy for creating new Ubuntu One address book" is actually three WIs
[15:48] <pitti> did that come up in the last meeting?
[15:48] <chrisccoulson> the launcher integration is done too
[15:49] <chrisccoulson> oh, i don't think we mentioned that one in the end
[15:49] <pitti> chrisccoulson: can you put it on tomorrow's agenda?
[15:49] <pitti> strategic discussion is already quite late at this point
[15:49] <chrisccoulson> pitti - yeah, will do
[15:49] <pitti> thanks
[15:50] <pitti> bryceh, RAOF: should we move https://blueprints.launchpad.net/ubuntu/+spec/multimedia-desktop-n-xorg-multihead-defaults to p at this point, or do you still want to work on this for o?
[15:50] <pitti> (^ for eastern edition)
[15:51] <pitti> kenvandine: new gwibber landed, great! looks like the remaining things on https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-gwibber-gtk3 are now "nice to have" extra features?
[15:51] <pitti> or do they represent regressions?
[15:51] <kenvandine> both
[15:51] <kenvandine> and there are some regressions not listed there
[15:52] <kenvandine> working through them though!
[15:52] <kenvandine> :)
[15:52] <kenvandine> will land another release tomorrow
[15:52] <pitti> nice
[15:52] <pitti> seb128: for https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-screensaver, do we actually have cycles to reintegrate hacks?
[15:53] <pitti> seb128: or should we perhaps just slightly patch the top bar to not look so shell specific?
[15:53] <seb128> it's going to be difficult
[15:53] <pitti> that's what I thought
[15:53] <seb128> we will probably have extra GNOME3 work still with new things like the online account or contacts browser work
[15:53] <seb128> not counting some design changes suggestion that should come as well
[15:53] <pitti> over to perky then?
[15:54] <seb128> let's make it not look like g-s at least yes
[15:54] <chrisccoulson> we can just turn off the top bar can't we?
[15:54] <seb128> chrisccoulson, you said you would maybe be interested to bring the hack code back, do you think you will cycles for it?
[15:54] <pitti> well, having a clock isn't too bad
[15:54] <rodrigo_> yes, I think so
[15:54] <seb128> chrisccoulson, or is tb going to keep you busy full time for the cycle?
[15:54] <chrisccoulson> seb128, i was going to look at it, but there was talk at the rally about using lightdm to lock the screen. is that still the case?
[15:55] <seb128> good point
[15:55] <seb128> well that doesn't change that if we want hacks support we should still have a renderer for them and a config ui
[15:55] <seb128> but worth checking with robert_ancell if he thinks he will have time to make lightdm the lock screen
[15:56] <pitti> kenvandine: discussion in parallel, the avatar thing is done in the current version for https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-telepathy-indicator ? or is that something else still?
[15:56] <kenvandine> that is blocked by libindicate and gtk3
[15:56] <kenvandine> i'll followup with tedg on that
[15:57] <pitti> seb128: so how about I file an alpha-3 bug about improving the gnome-screensaver panel, and we move that spec to p?
[15:57] <seb128> pitti, well realistically move the hacks work to next cycle and keep the "redesign the lock screen" to this cycle
[15:57] <pitti> nice :)
[15:58] <seb128> the goal was to use the same design for login and lock screen I think
[15:58] <seb128> but we should check
[15:58] <seb128> - if lightdm is going to be used or if we need a lightdm like screen for gnome-screensaver
[15:58] <seb128> - if robert_ancell will have time for it
[15:58] <seb128> - otherwise fallback to minimal tweaking
[15:58] <seb128> like not displaying a top bar or something
[15:58] <seb128>  
[15:59] <seb128> pitti, does it make sense?
[15:59] <pitti> sounds good to me
[15:59] <seb128> ok, that's a plan then
[15:59] <pitti> cyphermox: https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-desktop-network-enhancements -> switching to automatic and optional IPv6 sounds like a small change we shoudl get in as fast as possible; is it actually small, or blocked on something?
[15:59] <seb128> we can move on
[16:00] <pitti> I need to catch Robert in the morning, but didn't see him yesterday or today
[16:00] <seb128> he's usually around but not talking if you don't ping him ;-)
[16:00] <pitti> cyphermox: porting indicator-network to current NM: is i-network required by OEM or other projects, or could we safely defer that?
[16:00] <seb128> but it's possible that login manager hacking and testing make it no easy to stay on IRC as well
[16:01] <pitti> seb128: yes, I checked that; he wasn't on IRC, but I got up a little later than usual today
[16:01] <seb128> drop him an email I guess
[16:01] <pitti> ok
[16:01] <seb128> during the rally he was often on a vt for lightdm hacking
[16:01] <pitti> will do that then
[16:01] <seb128> so it's likely that he's not on IRC a lot nowadays
[16:01] <pitti> while I wait for cyphermox's answer, public announcement:
[16:02] <pitti> I'll be on holiday in the next two weeks
[16:02] <pitti> so if you need me to do something urgent, please speak up this week
[16:02] <pitti> does someone feel like doing the team and release meeting in these two weeks?
[16:02] <seb128> can do
[16:02] <pitti> seb128: would be great if you could take the release meeting, you have most experience with it
[16:02] <seb128> ;-)
[16:03] <pitti> and someone else perhaps the desktop meeting
[16:03] <seb128> I can do both
[16:03] <seb128> desktop meeting is easy
[16:03] <pitti> (which is mostly preparing the wiki template and copying the log back to it
[16:03] <pitti> seb128: merci
[16:03] <seb128> de rien ;-)
[16:03] <kenvandine> pitti, have a great vacation!
[16:03] <seb128> pitti, enjoy you time off and crossing finger that you have nice weather ;-)
[16:03] <pitti> thanks!
[16:03] <cyphermox> pitti: we can safely defer porting indicator-network (AFAIK)
[16:03] <pitti> cyphermox: thanks
[16:04] <cyphermox> pitti: as for ipv6; I'm working on it right now. It's basically all already on, but we get delays in connections; that's a little bad; but it's more a bug than anything else
[16:04] <pitti> cyphermox: ah, good to hear; thanks for the heads-up
[16:04] <cyphermox> so I'll just clean up the work items there to make this clearer
[16:04] <pitti> that's it from me; does anyone have further discussion topics?
[16:05] <pitti> cyphermox: I sent you a review of usb-modeswitch, btw
[16:05] <pitti> looking forward to seeing this land
[16:05] <cyphermox> pitti: yes, I saw. Thanks a lot.. just haven't looked at it yet on account of being deep in NM code to figure out the connection delays ;)
[16:05] <pitti> cyphermox: yes, no hurry
[16:06] <pitti> cyphermox: I'll try to get to the second half of it this week still
[16:06] <cyphermox> will look and merge today hopefully
[16:06] <pitti> cyphermox: it'll take some time, I mostly just added comments :)
[16:06] <pitti> so, no AOB?
[16:06] <seb128> pitti, so feature freeze is in a bit less a month, can we land things on the CD while you are not there?
[16:06] <seb128> we have some pending things I've on my list we need to track
[16:06] <seb128> - sort the clutter depends
[16:06] <pitti> seb128: sure; you will be the acting release engineer for the desktop team :)
[16:07] <seb128> - sort the cheese new requirement and the fact that empathy will use it
[16:07] <pitti> I don't have a personal lock on the CDs :)
[16:07] <seb128> - get gnome-online-account installed
[16:07] <kenvandine> cheese, yummy
[16:07] <pitti> just see my note about CD size on the wiki page
[16:07] <seb128> - look at packaging the GNOME 3.2 addressbook
[16:07] <pitti> we lost our potential 15 MB savings
[16:08] <seb128> hum :-(
[16:08] <seb128> do we still have a pending "drop python 2.6"?
[16:08] <seb128> well I guess it's smaller since we cleaned the pyc
[16:08] <rodrigo_> how much space are we at?
[16:08] <seb128> we need to win at least 11mb it seems
[16:09] <pitti> so as for the meeting, thanks everyone!
[16:09] <pitti> right
[16:09] <seb128> that's not counting that we will need to add libcheese, clutter, clutter-gst, gnome-online-account, the addressbook
[16:09] <pitti> well, 8 MB, as we should have 703 MB images
[16:09] <seb128> thanks pitti
[16:09] <pitti> seb128: I thought we'll drop cheese from ubiquity's depends, and move it to universe?
[16:10] <seb128> pitti, 11mb on i386 still
[16:10] <pitti> ah, right
[16:10] <seb128> pitti, empathy will depends on it
[16:10] <seb128> or optionally depends
[16:10] <seb128> we might get away with cheese
[16:10] <seb128> but it will bring clutter and clutter-gst in
[16:11] <pitti> seems we need to find some time to get rid of that second webkit
[16:11] <pitti> and until then, keep the current empathy?
[16:12] <chrisccoulson> the blocker on the second webkit is banshee though isn't it?
[16:12] <pitti> and shotwell
[16:13] <seb128> ubuntu-sso-client
[16:13] <pitti> and libubuntuone-1.0-1, but that might be related to banshee only, too
[16:13] <seb128> software-center
[16:13] <seb128> I don't see us dropping a webkit this cycle
[16:13] <pitti> oh, python-webkit
[16:14] <pitti> seb128: so what will bring in the clutter stuff? new totem?
[16:14] <seb128> empathy, totem
[16:14] <seb128> cheese -> libcheese -> empathy,ubiquity
[16:14] <pitti> could we patch out the new requirements?
[16:14] <pitti> ubiquity can drop cheese AFAICS
[16:15] <seb128> not easily apparently
[16:15] <seb128> ubiquity can yes, though ev wanted to use it this cycle to take a picture during the installation
[16:15] <seb128> but I guess we could do some small direct python and gst hacking for that
[16:15] <pitti> well, we have to say no at some point
[16:15] <seb128>  
[16:15] <seb128> empathy is an issue
[16:15] <seb128> clutter and clutter-gst will be used for video rendering
[16:15] <pitti> we could keep the current empathy, or patch it out again from 3.2, or go back to 3.0?
[16:16] <seb128> that's the only way to put controls over the video or that sort of things, that they want to do
[16:16] <seb128> kenvandine, ^
[16:16] <kenvandine> upstream really wants that...
[16:17] <pitti> I didn't see any work on downsizing the kernel, or downsizing libo, or the other bits on https://launchpad.net/ubuntu/+spec/desktop-o-cdspace, so I guess we can't rely on that any more for o
[16:17]  * kenvandine runs to lunch, bbiab
[16:17] <seb128> pitti, it's hard to bring empathy down to 3.0 especially with the new contact integration work in GNOME 3.2 I guess
[16:18] <seb128> well we could probably patch the new video code using clutter out if needed
[16:30]  * rodrigo_ needs to run, bbl
[16:42] <pitti> good night everyone!
[16:42] <seb128> 'night pitti
[16:48] <tremolux> goodnight pitti!
[18:21] <Ampelbein> hi there, the latest gtk+2.0 upload only ships the symlink /usr/bin/gtk-update-icon-cache in the i386 package, bug 810747 is a result of this.
[18:21] <ubot2> Launchpad bug 810747 in gtk+2.0 "package indicator-weather 11.05.31-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127" [High,Triaged] https://launchpad.net/bugs/810747
[18:33] <cyphermox> Ampelbein: thanks
[18:38] <cyphermox> Ampelbein: the issue should alreday be fixed in -0ubuntu4; could you please check the revision of libgtk2.0-bin you have?
[18:38] <Ampelbein> cyphermox: it is -0ubuntu4 that has the problem, see my comment on the bug (I used dpkg-deb -c to display the contents)
[18:39] <Ampelbein> cyphermox: -0ubuntu3 and before was arch: all, so the symlink was pointing at the wrong place.
[18:39] <Ampelbein> cyphermox: but -0ubuntu4 is arch:any and only has the symlink in the i386 package.
[18:40] <seb128> pitti, ^
[18:40] <cyphermox> ah I see
[18:41] <Ampelbein> I would have tried fixing myself, but gtk+2.0 is a 2 hour build on my system, so... no. ;-)
[18:41] <cyphermox> :)
[18:49] <seb128> should be fixed in gtk but the indicator is buggy as well, it shouldn't call the update command in its postinst, that's done by a trigger
[18:54] <cyphermox> this is a pretty cool bug; very interesting  :)
[18:54] <cyphermox> seb128: testing a build now
[18:56] <Ampelbein> cyphermox: from looking at the source it could be that the -bin is still listed in BINARY_INDEP_PKGS (in debian/rules).
[18:56] <cyphermox> yup
[19:31] <james_w> seems gnome-keyring-daemon is in caps mode, not setuid mode in oneiric?
[20:09] <cyphermox> hmm. 42 minutes to build gtk
[20:09] <cyphermox> seb128:  still around?
[20:11] <seb128> cyphermox, sort of
[20:12] <seb128> on a box with IRC but not on oneiric box, why?
[20:12] <cyphermox> well, I filed a merge request anyway
[20:12] <cyphermox> for the gtk thing
[20:12] <seb128> isn't get in the desktop set?
[20:12] <cyphermox> ah, I thought it would be in core
[20:12] <cyphermox> given the relative importance and all :)
[20:13] <seb128> well I think it's in desktop, try uploading
[20:13] <cyphermox> sure, I'll check
[20:13] <seb128> if it's not ask kenvandine if he can do sponsoring, otherwise I will do it tomorrow morning when  I'm on a box with my keys
[20:14] <cyphermox> ah, it seems it is, my bad
[20:14] <cyphermox> I really should have checked before
[20:14] <seb128> no worry ;-)
[20:20] <cyphermox> seb128: Ampelbein: done, thanks
[20:20] <seb128> thank you
[20:22] <micahg> cyphermox: kees is piloting if you need something
[20:24] <cyphermox> micahg: thanks, but I actually could upload that, just didn't expect to ;)
[20:27] <dobey> can i bug someone for a quick sponsoring?
[20:29] <dobey> https://code.launchpad.net/~dobey/ubuntu/oneiric/ubuntuone-control-panel/use-dhpython2/+merge/68459
[20:31] <seb128> dobey, try pinging kees he's patch pilot today
[20:32] <seb128> will do it when I'm on box with my keys tomorrow otherwise
[20:32] <dobey> ok, thanks
[20:46] <seb128> kenvandine, could you make gwibber not use python-wnck?
[20:46] <seb128> kenvandine, it seems there is a one line get screen call, should be easy to use gtk or the wnck gir instead?
[20:47] <seb128> kenvandine, it's one of the few things keeping the old libwnck in ;-) do you want a bug about it?
[20:47] <kenvandine> sure
[20:47] <kenvandine> must be gwibber-accounts using it still
[20:47] <seb128> yes
[20:47] <kenvandine> i'll do it now :)
[20:47] <kenvandine> no bug needed
[20:47] <seb128> thanks
[20:48] <ejat> hi .. will compiz 0.9.5 backport to natty soon ?
[20:48] <seb128> ejat, not sure it will be backported at all
[20:49] <seb128> it's not a bug fix update and it has already a bunch of known issues
[20:49] <seb128> speed issues and bugs
[20:50] <ejat> owh okie thanks ..
[20:50] <ejat> u mean the 0.9.5 got bunch of known issues?
[20:50] <seb128> ejat, yes
[20:51] <ejat> ic .. noted
[21:09] <kenvandine> seb128, actually, can you file a bug about dropping wnck?  the kids are  calling me and i might forget if i wait until tonight :)
[21:09] <seb128> kenvandine, sure
[21:09]  * kenvandine runs... bbl
[21:09] <seb128> kenvandine, see you ;-)
[21:10] <kenvandine> have a good night seb128!
[21:10] <seb128> thanks
[21:25] <seb128> kenvandine, bug #813182
[21:25] <ubot2> Launchpad bug 813182 in gwibber "should stop using the old wnck static binding" [Low,Confirmed] https://launchpad.net/bugs/813182
[21:55] <seb128> mterry, is there a way to open the datetime preferences in current oneiric?
[22:30] <RenatoSilva> http://pastie.org/2239582. The onboard audio is selected as default output. However, the front audio (headphone) only starts working after I "stimulate" it by plugging in some connector in the onboard hear jack. Doesn't happen in Windows. Worth to file a bug?
[22:54] <jbicha> RenatoSilva: yes, ubuntu-bug audio
[22:54] <RenatoSilva> jbicha: ubuntu-bug audio? tags to the bug?
[22:55] <jbicha> RenatoSilva: no, run that command and it will help you report the bug
[22:55] <RenatoSilva> jbicha: oh cool! let me see
[22:56] <jbicha> you can also run just ubuntu-bug to get other choices
[23:03] <jasoncwarner_> RAOF TheMuso bryceh robert_ancell ready for the meeting?
[23:03] <jasoncwarner_> https://wiki.ubuntu.com/DesktopTeam/Meeting/2011-07-19
[23:03] <RenatoSilva> jbicha: it's collecting data since minutes
[23:03] <TheMuso> Morning jasoncwarner_.
[23:03] <RAOF> Like a fox!
[23:03] <TheMuso> Its a rather unpleasant day in Sydney today.
[23:04] <jasoncwarner_> TheMuso: so in other words, you have nothing better to do?  ;)
[23:04] <jbicha> TheMuso: too cold?
[23:05] <TheMuso> jasoncwarner_: lol
[23:05]  * RAOF is pondering moving to in front of the fire to defrost his arse.
[23:05] <TheMuso> jasoncwarner_: Not at all, got plenty to do, but its a day thats an inside day.
[23:05] <TheMuso> jbicha: No, very windy and rainy.
[23:05] <jasoncwarner_> TheMuso: :)
[23:05] <TheMuso> The cold I can deal with, wind, is another story.
[23:06] <RAOF> Yeah.  It's pretty miserable here, too.
[23:06] <RAOF> Although not windy.
[23:06] <jasoncwarner_> ready to get crackin'? [TOPIC] X update
[23:07] <RenatoSilva> apport it's collecting data since minutes, what do I do?
[23:07] <bryceh> heya
[23:07] <jasoncwarner_> hey bryceh ... you or RAOF  want to update us on X?
[23:07] <jbicha> RenatoSilva: please ask in #ubuntu-bugs
[23:07] <bryceh> sure
[23:08]  * RAOF deferrs to bryceh 
[23:08] <bryceh> for wayland, I've filed a MIR which we're waiting on.
[23:08] <RenatoSilva> jbicha: thanks
[23:08] <bryceh> once that's in we can put libwayland-egl support in mesa and move ahead with things there.
[23:08] <bryceh> for now we're in a holding pattern waiting on the mir.
[23:09] <bryceh> bug report situation is looking quite good for X right now
[23:09] <bryceh> either things are really stable, or few people are running oneiric
[23:09] <RenatoSilva> jbicha: thanks anyway
[23:09] <bryceh> there's a few gpu lockups reported for intel, but upstream says a newer mesa snapshot would fix
[23:10] <bryceh> I'm cherrypicking one patch for a confirmed fix and will upload it after the meeting
[23:10] <bryceh> I've stuck a new xdiagnose in the archive, which brings improved apport hook functionality
[23:10] <jasoncwarner_> is there any risky or tricky planned for mesa or x the rest of the cycle? Any landmines we should be watching out for?
[23:10] <jasoncwarner_> we are coming up on A3, so after that I would like it to be bugs bugs bugs!
[23:10] <bryceh> yes, raof will probably do some additional mesa updates as 7.11 matures
[23:11] <bryceh> and probably updates to -ati and -intel
[23:11]  * RAOF has mesa rc1 waiting in git, pending wayland MIR.
[23:11] <bryceh> the only major change we're contemplating is turning on Intel's new SNA architecture
[23:11] <jasoncwarner_> timing on those?
[23:11] <bryceh> RAOF, ah cool.  maybe I'll chuck it in a ppa if the MIR doesn't go through soon.
[23:12] <bryceh> jasoncwarner_, SNA is available now if we wish to turn it on.  So it's just a matter of having a firm decision on direction
[23:12] <RAOF> But the mesa updates will not be particularly dangerous; we're tracking the 7.11 release branch, so avoid the major crack.
[23:12] <bryceh> yeah 7.11 appears to be in bugfix mode.  Who knows though, mesa can  be crazy sometimes.  But I agree it's probably going to be smooth here on out.
[23:13] <jasoncwarner_> bryceh: great, thanks.
[23:13] <jasoncwarner_> anything else x related?
[23:13] <bryceh> the trade-off with SNA we face is if we don't update NOW, we're faced with being forced to update for the LTS
[23:13] <bryceh> however, if we adopt SNA NOW, we also risk more bugginess than if we wait.
[23:14] <RAOF> Assuming someone else adopts SNA before we do :)
[23:14] <bryceh> oh one other thing with xdiagnose
[23:14] <bryceh> I notice that some reports appear to be coming in still without xdiagnose having been installed
[23:15] <bryceh> so I'm wondering if we should consider making xorg depends on xdiagnose rather than recommends.  RAOF, thoughts?
[23:16] <RAOF> I think xdiagnose should be a Depends rather than a Recommends.  apt will only complain a bit when upgrading removes Recommends, and then that system will forevermore not have xdiagnose installed.
[23:16] <bryceh> alright, I'll make that change.
[23:16] <bryceh> all from me.  RAOF, anything I missed?  What are you working on?
[23:17] <RAOF> Finishing off mesa rc1 and enabling the wayland-egl stuff.
[23:17] <RAOF> Also, colord.  It's *vaguely* X related :)
[23:17] <bryceh> oh also we had that xorg symlink bugaboo yesterday
[23:18] <RAOF> Yeah.  2007 escaped from its cage and bit us.
[23:18] <RAOF> That should be fixed now, and in the future.
[23:19] <bryceh> jasoncwarner_, guess that's it.  Oh should also note I could be disappearing for paternity leave any day now.
[23:19] <bryceh> I'll send a note
[23:19] <jasoncwarner_> bryceh: could you tell the lovely wife this just isn't a good time? maybe in early november would be better?
[23:19] <jasoncwarner_> see how that goes over
[23:19] <RAOF> There's also some scope for slimming down the X server packages should a couple of tens of kilobytes be required on the CD.
[23:19] <bryceh> hehe
[23:20] <jasoncwarner_> RAOF: I'm pretty sure Pitti would be excited to hear about any 10s of kilobytes at this point ;)
[23:20] <jasoncwarner_> thanks, bryceh and RAOF
[23:20] <jasoncwarner_> TheMuso: anything you wanted to update?
[23:21] <RAOF> And finally from me, colord is ready in alioth git.  It requries a review and upload - preferably to Debian.
[23:21] <TheMuso> jasoncwarner_: Unfortunately no, been fighting infrastructure changes thsi week and have een less productive as a result, but all seems well now so hopefully things can move forward quickly for me.
[23:21] <jasoncwarner_> how are we doing accessibility wise? ubiquity? 2d? 3d?
[23:23] <TheMuso> jasoncwarner_: Unity a11y no change, doesn't help when DX are revamping nux's architecture. 2D is no change either, but I am keeping an eye on QT a11y patches and unity-2d dev work itself for things to try.
[23:23] <TheMuso> ubiquity well I'm still working on that, the infrastructure change stuff affected my work on that a bit, but that should be behind now.
[23:24] <jasoncwarner_> cool
[23:25] <jasoncwarner_> thanks, TheMuso
[23:25] <jasoncwarner_> robert_ancell, around?
[23:25] <jasoncwarner_> ok
[23:25] <jasoncwarner_> AOB? I have a couple of things
[23:26] <jasoncwarner_> if no one else
[23:26] <jasoncwarner_> ok...#1 from me. A3 is coming up, after which I want us to be focusing on bugs, as I've said...I'd like to see us really hammering every aspect of the system and making sure this thing is awesome.
[23:27] <jasoncwarner_> no bug is too big, no bug too small :)
[23:27] <jasoncwarner_> and those quirky ones thta are all about usability...
[23:27] <jasoncwarner_> and don't get me started on Unity related stuff...hammer Unity to death!
[23:27] <jasoncwarner_> Ok...#2 unity update yesterday/today. Anyone update yet?
[23:28] <TheMuso> No, that unity update was for the new compiz ABI.
[23:28] <RAOF> I updated last night.
[23:28] <jasoncwarner_> did anyone update to that, though? with new compiz?
[23:28] <jasoncwarner_> ok
[23:28] <RAOF> Yeah, I'm running the new compiz now.
[23:29] <RAOF> Nothing particular to report.
[23:29] <RAOF> Were there meant to be user-visible changes?
[23:29] <jasoncwarner_> I'm having a terrible morning with window lag and I was wondering if anyone else was having that as well. Switching between windows has a perceptible 1s or so lag
[23:29] <RAOF> Ah, yeah.  That.
[23:29] <jasoncwarner_> it is most noticable switching between firefox tabs
[23:29] <jasoncwarner_> RAOF: so I'm not going crazy ;)
[23:29] <RAOF> Oh, no.  That's not what I'm seeing.
[23:29] <RAOF> At least, I don't think so.
[23:30] <jasoncwarner_> RAOF: what are you seeing?
[23:30] <RAOF> Alt+Tab is supremely unresponsive under system load.
[23:30] <jasoncwarner_> ok..might be related
[23:30] <RAOF> As in: the switcher window can take upwards of 10s to appear when something's using the CPU.
[23:31] <jasoncwarner_> just wondering if anyone else saw it...I'll check with smspillaz
[23:31] <RAOF> Given we're getting a new alt-tab shortly, I'm not sure how much to care.
[23:31] <jasoncwarner_> RAOF: wow...
[23:31] <jasoncwarner_> uh, that probably isn't good
[23:31] <jasoncwarner_> thanks, RAOF I'll track it down...Anyone else have anything or AOB? if not we can end the meeting.
[23:31] <TheMuso> Between now and FF, DX wil dump a lot of stuff on us that will likely be broken.
[23:31] <jasoncwarner_> TheMuso: NEVAR!
[23:32] <chrisccoulson> RAOF, indicator-datetime-service and e-calendar-factory go crazy here and spam the session bus, causing dbus-daemon to use lots of CPU
[23:32] <bryceh> ...and will get reported as X.org bugs
[23:33] <chrisccoulson> when that happens, i see the same behaviour as you
[23:33] <chrisccoulson> (with alt+tab)
[23:33] <bryceh> well, either X.org or Yelp
[23:33] <chrisccoulson> but, also, everything seems to grind to a halt
[23:33] <RAOF> chrisccoulson: That could well be what I'm seeing.
[23:33] <chrisccoulson> it can take me in excess of 5 seconds or so just to switch workspaces when that happens too
[23:34] <jasoncwarner_> you guys reporting bugs to smspillaz and dbo/jason?
[23:34] <RAOF> Somewhat informally, yes.
[23:35] <jasoncwarner_> ok...thanks...i'm going to find smspillaz when he wakes up and poke him a bit...he likes to be asked about compiz performance issues first thing in the morning ;)
[23:35] <DBO> jasoncwarner_, you'll be happy to know I am working on Unity performance now
[23:36] <DBO> now go file some paperwork or whatever it is your job mandates :P
[23:36] <jasoncwarner_> DBO: I am happy to know that. Though, I'd like smspillaz to work on it as well so we can have someone with skillz on the job too...
[23:36] <jasoncwarner_> DBO: :P
[23:36] <jasoncwarner_> thanks everyone! [END MEETING]
[23:41] <jbicha> bryceh: so just curious, wayland might happen for, what, 12.10?
[23:41] <bryceh> jbicha, depends on what is meant by "happen"
[23:42] <bryceh> jbicha, but no, there's no specific dates written down for anything
[23:42] <jbicha> how about usable by the omgubuntu crowd, but not necessarily default
[23:44] <bryceh> not sure what that means
[23:45] <bryceh> jbicha, if you're asking when will unity run on wayland... well have to ask the unity guys, I've no idea.
[23:48] <jbicha> bryceh: thank you
[23:50] <RAOF> jbicha: At this point I'd be unsurprised to have lightdm, at least, as a wayland server in 12.10.  It's unclear to me how a full transition would go.