[04:28] <pitti> Good morning
[04:29] <pitti> stgraber: what I didn't understand yet: why do we conceptually need a daemon for the cgroup management anyway? why can't this just be a library which does proper locking to avoid cgroup fs write conflicts?
[04:30] <stgraber> pitti: because it's unsafe to allow a container to mount cgroupfs, so we want to let a container alter only a sub-section of the hierarchy
[04:30] <pitti> stgraber: ah, so the daemon's API would always be "relative" to the calling cgroup?
[04:31] <stgraber> a container wouldn't be able to access cgroupfs directly but would have access to the daemon's socket which will let it write only in its sub-section of the hierarchy
[04:31] <stgraber> pitti: correct
[04:31] <pitti> stgraber: thanks
[04:32] <stgraber> so we can do any level of nesting and user switch (with userns) without ever having to grant access to cgroupfs and therefore preventing any of the containers from escaping their limits
[05:39] <Noskcaj> Can someone look into removing rhythmbox-radio-browser? It is pretty much non-functions due to rhythmbox api changes
[09:43] <asac> 10:40 < jibel> asac, confirmed: apt-get install libc6-amd64 && apt-get remove libc6-amd64
[09:43] <asac> 10:40 < jibel> and get a broken system for free
[09:43] <asac> 10:42 < asac> jibel: thats on i386?
[09:43] <asac> 10:43 < jibel> asac, amd64 with i386 enabled
[09:43] <asac> hmm... doko not around :)
[09:44] <Laney> probably infinity
[09:44] <jibel> asac, doko has issues with his provider this morning
[09:46] <asac> infinity: ^ (in case you are in a eur zone)
[09:47] <didrocks> asac: infinity is sick today
[09:48] <Laney> I guess file a bug and assign him
[09:51] <infinity> asac: There's already a bug for that.  I was just trying to think up a clever fix right now, while I can't sleep.
[09:52] <infinity> (Not a new bug, it's been like this since precise, but it's very rare for people to install libc6:amd64 and libc6-amd64 on the same machine)
[09:52] <didrocks> Laney: yeah, I guess you will volonteer in hosting vUDS session btw as I can't start anything on my machine now :p
[09:52]  * ogra_ would blame the package that installs it ...
[09:52] <seb128> infinity, it was, until the emulator started pulling it in
[09:52] <asac> infinity: right. i think for now didrocks just needs a good idea how to recover (e.g. what exactly is now wrong)
[09:52] <seb128> ogra_, that's the android emulator :p
[09:52] <ogra_> the emulator deps should just be fixed
[09:53] <didrocks> asac: agreed ;)
[09:53] <asac> infinity: maybe just unpack libc6:amd64 ?
[09:53] <Laney> didrocks: have you /seen/ me try to use hangouts?
[09:53] <ogra_> it cant even use any amd64 stuff ...
[09:53] <seb128> didrocks: oh, so you did that to sneak off vUDS hosting!
[09:53] <Laney> :P
[09:53] <infinity> asac: What's wrong is that /lib64/ld-linux-x86-64.so.2 is gone.
[09:53] <seb128> lol
[09:53] <didrocks> seb128: clearly ;)
[09:53] <seb128> Laney, man, you and hangouts don't get along for some reason ;-)
[09:53] <infinity> asac: So no amd64 binaries will run.
[09:53] <asac> yeah
[09:54] <infinity> asac: Recreating the symlink from a rescue CD would do the trick.
[09:54] <infinity> didrocks: ^
[09:54] <didrocks> yeah, no /lib64/ld-2.17.so binary
[09:54] <ogra_> infinity, whats wrong is that a package that can only make use of libc6-i386 pulls in libc6-amd64
[09:54] <didrocks> infinity: the symlink is there, just not /lib64/ld-2.17.so
[09:54] <infinity> didrocks: /lib/x86_64-linux-gnu/ld-2.17.so
[09:54] <infinity> didrocks: The symlink should point to that.
[09:54] <asac> i assume thats in libc6:amd64? so ifyou have that and can unpack it should be ther?
[09:54] <didrocks> ah ok, so lrwxrwxrwx    1 root     root            10 Nov 20 09:41 /lib64/ld-linux-x86-64.so.2 -> ld-2.17.so
[09:55] <didrocks> which points to /lib/x86_64-linux-gnu/ld-2.17.so
[09:55] <didrocks> right?
[09:55] <infinity> didrocks: No, just directly aim the symlink at /lib/x86_64-linux-gnu/ld-2.17.so
[09:55] <didrocks> ok, trying that in my busybox
[09:55] <infinity> didrocks: /lib64/ld-2.17.so is only in libc6-amd64
[09:55] <didrocks> making sense
[09:55] <infinity> ogra_: That makes no sense.  Why is an i386 package pulling in libc6-amd64?
[09:56] <asac> infinity: android :)
[09:56] <ogra_> infinity, thats what i'm saying
[09:56] <didrocks> of course, I need to be root
[09:56] <infinity> (Not saying there isn't a massive glibc bug here, but installing libc6-amd64:i386 on amd64 is never a desired result)
[09:56] <didrocks> and can't in this / busybox
[09:56] <didrocks> so needing to reboot in initrd busybox
[09:56] <ogra_> infinity, its the android-emulator package apparently
[09:56] <asac> http://paste.ubuntu.com/6447333/
[09:56] <asac> thats the stuff in android-emulator
[09:57] <infinity> asac: That doesn't explain why it's forcing this weird set of packages to be installed.  What are its deps?
[09:57] <asac> infinity: it has emulator64 binaries in there
[09:57] <infinity> Oh, it explicitly depends on libc6-amd64 ... FUN.
[09:57] <asac> can the package say: libc6:amd64 | libc6-amd64 ?
[09:58]  * ogra_ has never used the package, i build it from the tree ... which
[09:58] <asac> guess not :)
[09:58] <ogra_> ... requires the i386 libs installed already
[09:58] <infinity> xnox: Want to make android-emulator depend on libc6:amd64 and libstdc++6:amd64 instead, and just make it not work without multiarch?
[09:58] <infinity> Oh, wait.  Can't do that.
[09:58] <infinity> Grr.
[09:59] <infinity> Of course, it could just be an amd64 package, period, which would solve the issue.
[09:59] <infinity> Just make it not available on i386.
[09:59] <seb128> heh, why so much hate for i386 users
[09:59] <infinity> Or if it has i386 and amd64 bits, build one on one, one on the other, and have a metapackage that pulls in -i386 and -amd64 bits.
[10:01] <infinity> pull-lp-source: Downloading android_20131120-0225.orig.tar.xz from archive.ubuntu.com (191.659 MiB)
[10:01] <infinity> Gah.
[10:02] <ogra_> dont cry ... that used to be 500M in the past
[10:02] <infinity> I'm all for people reminding me that I have a glibc bug that really needs fixing, but I'm not sure this was the way to do it. :P
[10:02] <infinity> Quite entertaining if we've been telling people to install this.
[10:03] <ogra_> well ... https://wiki.ubuntu.com/Touch/Emulator
[10:04] <infinity> Okay, so it's already arch-restricted to i386... Splitting it to an i386 and amd64 bit wouldn't be rocket science.  And we already seem to be assuming users of this will have multiarch enabled.
[10:04] <ogra_> we only offer it in trusty
[10:05] <asac> I am pretty sure its not rocket science, but I assume that the android build system will have to be taught to build things separated by archs :)
[10:05] <ogra_> nah. that wouldnt work
[10:05] <asac> I assume ricard tried to avoid carryuing a big delta there for the time being
[10:06] <infinity> asac: No need to tell it to break things up.  Just find the i386 binaries and put them in emulator-i386, do the same for the amd64 binaries, and package it up.
[10:07] <infinity> Aaand, it's an hour-long build.    This means I'd have to build it twice, though.
[10:09] <infinity> Once per arch.
[10:10] <infinity> Oh, wait.  You *can* depend on foo:arch.  crossbuild-essential does it.
[10:16] <asac> didrocks1: managed to get past the point of no command?
[10:16]  * asac assumes that no news is good news for now
[10:16] <didrocks1> asac: well, I need to create an usb stick
[10:16] <infinity> Doing a test build of this blind change: http://paste.ubuntu.com/6447414/
[10:17] <asac> nice one :)
[10:17] <Laney> bahaha, I like that hack
[10:19] <didrocks1> asac: that will teach me to not always have a root terminal opened…
[10:19] <didrocks1> (to start busybox as root)
[10:19] <mlankhorst> sabdfl: hey since we now lack a TB, can you make a decision on the MRE's I requested on<EMAIL_ADDRESS>? https://lists.ubuntu.com/archives/technical-board/2013-October/001737.html
[10:19] <infinity> I'll see if I can fix the actual linker switcheroo mess in 2.18 (I was looking at that earlier anyway), but either way, we shouldn't be encouraging people to install the multilib stuff.
[10:20] <didrocks1> asac: seb128: maybe one of you can annotate the wiki with those infos (to not install the emulator on amd64 for now)? ^
[10:20] <infinity> mlankhorst: A one-time version bump like that isn't really a standing MRE that the TB should have to worry about anyway, the SRU team can probably take that in hand.
[10:21] <didrocks1> especially if people wants to clean up their machine then :p
[10:22] <mlankhorst> infinity: I just want to move things forward soon if possible. Pixman is the one I'm most worried about. But libdrm seems to require a bump every release, so it sort of would need a standing MRE. :P
[10:23] <infinity> mlankhorst: Sure, libdrm could use a standing MRE (or, though the versions make it look like "micro" releases, they're clearly not, and it probably needs something more like the firefox exception), but it's never had one before, so we can live without for a bit.
[10:24] <infinity> mlankhorst: Is this all well tested in a PPA somewhere?  Do you have a placeholder HWE SRU bug that you can attach tasks for all these packages to and detail the testing done and subscribe the SRU team?
[10:25] <mlankhorst> infinity: libdrm is weird, most of the driver stuff is just a c wrapper for the kernel interface
[10:25] <mlankhorst> https://launchpad.net/~ubuntu-x-swat/+archive/s-lts-backport
[10:25] <Saviq> seb128, "don't uninstall libc6-amd64"? or "don't install libc6-amd64"?
[10:25] <infinity> Saviq: Yes.
[10:25] <infinity> Saviq: Don't install it, but if you have, uninstalling it is also dangerous.
[10:25] <seb128> Saviq, don't uninstall it if you have it installed
[10:25] <mlankhorst> I think I created a bug for the pointer barriers specifically, but I didn't make one for pixman and libdrm yet.
[10:25] <Saviq> seb128, so I can still try the emulator on amd64, just never uninstall it? ;D
[10:26] <mlankhorst> ppa with all components at https://launchpad.net/~ubuntu-x-swat/+archive/s-lts-backport
[10:26] <seb128> Saviq, basically, or better wait for infinity to fix those stuff ;-)
[10:26] <infinity> I wonder if I could work around this hackishly by providing a libc6-amd64 on amd64 that just Depends: libc6.
[10:26]  * infinity shudders a bit at the ickiness of that.
[10:27] <mlankhorst> infinity: or finally implement cross-arch depends. :P
[10:27] <infinity> mlankhorst: If you could just do up a meta bug for "lts-s backports" and detail what needs review, and what's been tested and how, then we can point any discussion there.
[10:27] <infinity> mlankhorst: cross-arch deps work.
[10:27] <mlankhorst> ok
[10:28] <mlankhorst> I think I will make the metabug the bug for pixman/libdrm backporting too
[10:28] <infinity> mlankhorst: That doesn't solve this particular issue of people installing libc6-amd64:i386 on amd64.
[10:28] <infinity> Which explodes hilariously.
[10:28] <mlankhorst> why have that? o.O
[10:28] <infinity> Maybe we just need a Multi-Arch: dont-even header.
[10:29] <infinity> Package: libc6-amd64
[10:29] <mlankhorst> I thought that was what the Architecture: field was for, just build it on amd64 only. :P
[10:29] <infinity> Multi-Arch: hahahahano
[10:29] <infinity> mlankhorst: Erm it's only built on i386.
[10:29] <mlankhorst> oh
[10:29] <infinity> mlankhorst: But then people install an i386 package that depends on it.
[10:29] <infinity> On their amd64 system.
[10:29]  * didrocks1 wonders why usb-creator doesn't want to finish the current usb stick creation… will go with dd if this continues…
[10:29] <infinity> didrocks1: Just use dd.  usb-creator is a steaming heap of needs a lot of love.
[10:30] <infinity> (I think there may even be a UDS session about that?)
[10:30] <smb> infinity, was
[10:30] <didrocks1> infinity: yeah, I can testify this right now :)
[10:30] <infinity> Or was. :P
[10:30] <infinity> smb: How did that go?
[10:30] <smb> infinity, I think we use something different
[10:30] <mlankhorst> oh found the pointer barriers bug https://bugs.launchpad.net/ubuntu/+source/x11proto-input/+bug/1242633
[10:30] <pitti> dd wrapped in a GTK dialog?
[10:30] <mlankhorst> I'll open a metabug
[10:31] <infinity> pitti: Well, the reason for usb-creator (the only valid reason, other than the pretty GUI) is that it knew how to set up the weird partition scheme required for persistence.  dd alone can't pull that off.
[10:31] <smb> infinity, Actually there seems to be a more interesting issue on the side about having something that works with uefi and secure boot but not wasting most of your usb key
[10:31] <pitti> infinity: right, was mostly kidding
[10:32] <smb> infinity, Plus I thought there was an issue at least with older bioses of not booting an iso fs on a usb key
[10:32] <infinity> But for 99% of people who just want an installer USB key and don't give a crap about persistence, yeah, usb-creator really could just fork dd.
[10:32] <pitti> I actually successfully used usb-creator in saucy still, it's sad that it broke down so quickly
[10:32] <infinity> pitti: It's been broken for several releases, success rates seem to vary from person to person and moon phase.
[10:33] <smb> amd64 being better that trying to do i386 images in my experience
[10:33]  * infinity shields his eyes from all the code duplication he sees zipping past in this Android build log.
[10:33] <infinity> LA LA LA, CAN'T SEE YOU, HANDWAVE, GOING FOR A DRINK.
[10:34] <smb> Sadly coffee has not the desired effect... and at least its not ktb#1 time for me
[10:35] <infinity> smb: Choice of beverage really doesn't matter to me right now.  I should be either asleep or at a doctor's office, and I'm neither, so I'm failing at life.
[10:35] <smb> infinity, Yeah well, highly depends on your current location which often is hard to guess
[10:36] <infinity> smb: Calgary.  I think.  It's a bit hazy.
[10:38] <smb> infinity, That might be true now but was not last(?) week. Which could probably be part of the issue, too
[10:39] <didrocks> phew
[10:39] <didrocks> thanks infinity, asac (et jibel for testing in a vm)
[10:39] <infinity> didrocks: All gooder?
[10:39] <didrocks> yeah ;)
[10:39] <infinity> I really need to come up with a clever fix for that.
[10:39] <didrocks> the longest was to download/create this usb stick…
[10:40] <infinity> I was going to use dpkg diversions when I first found this issue in precise, but dpkg-divert had a bug that prevented it...
[10:40] <didrocks> I'll build an initramfs dropping me in a busybox for next time :p
[10:40] <infinity> That's now fixed, but it would break on upgrades FROM precise...
[10:40] <infinity> So.  Whee.
[10:40] <didrocks> infinity: oh? interesting
[10:41] <infinity> Only mildly interesting.  Mostly just annoying.
[10:41] <didrocks> (but, can be epic between the version without the fixed dpkg and then)
[10:41] <infinity> I can either bury my head in the sand and pretend the bug doesn't exist until 14.10 and fix it with diversions when I can do it safely.  Or come up with a more clever hack to work around it now.
[10:42] <infinity> And I think I almost mapped out a clever fix in my head about an hour before you broke your computer.
[10:42] <infinity> But that could just be the drugs talking.
[10:42] <infinity> I'll need to commit it to code when I'm more aware of my surroundings and see if I'm drunk.
[10:43] <didrocks> infinity: heh, sounds like a good plan, meanwhile, le'ts put an info in the wiki for the emulator, as I guess it's the main case for people getting into that bug
[10:44] <mlankhorst> infinity: https://bugs.launchpad.net/ubuntu/precise/+source/libdrm/+bug/1253041
[10:45] <infinity> didrocks: I might pull the emulator binaries from the archive for now.
[10:45]  * infinity does that.
[10:45] <infinity> Removing packages from trusty:
[10:45] <infinity> 	android-emulator 20131120-0225-0ubuntu1 in trusty i386
[10:45] <infinity> Comment: High chance of breaking amd64 systems
[10:45] <infinity> Remove [y|N]? y
[10:46]  * infinity waves bubye.
[10:46] <infinity> If my test build goes okay, I'll upload that.
[10:46] <asac> thx. let us know
[10:47] <infinity> With a nasty side-effect that people who *did* install the broken version of the emulator might get libc6-amd64 autoremoved and land in your situation...
[10:47] <infinity> What fun that will be.
[10:50] <didrocks> infinity: TBH, I won't test you hack today :p
[10:50] <seb128> infinity, asac, didrocks: since that was announced on the list (https://lists.launchpad.net/ubuntu-phone/msg05195.html) I guess we can count on quite some people installing/trying it... would be better to not autobrick their systems with the update (e.g maybe fix the libc side if we can before updating the emulator)
[10:50] <didrocks> your*
[10:51] <didrocks> right, I'm going to summarize what to do in case someone is broken?
[10:51] <infinity> seb128: The libc fix will take some more thinking.
[10:51] <seb128> didrocks, is that a question? yes please follow up on the list ;-)
[10:51] <infinity> seb128: And people installing the emulator might be removing it too.  Which already puts them in this situation.
[10:52] <infinity> (Granted, very few people also do autoremove religiously)
[10:54] <asac> isnt update-manager doing autoremove?
[10:55] <infinity> Oh, is it?  Fun.
[10:55] <seb128> asac, not in normal update mode at least, maybe in dist-upgrader mode
[10:55] <asac> not sure... asking :)
[10:55] <infinity> I didn't *think* it did.
[10:56] <asac> (i have to admit that i got stuck in old apt-get habits)
[10:56] <didrocks> I did autoremove religiously, not sure if one of our tool is doing that :)
[10:56] <asac> seb128: right. i think dist upgrading does autoremove
[10:56] <asac> not normal upgrades
[10:56] <asac> dont think thats better though ... just makes the support bomb more intense :)
[10:57] <infinity> Nah, buys me time until April to fix it!
[10:57] <asac> otoh, we can add arbitrary hackery to mitigate such issues in update-manager...
[10:57] <infinity> (I'll make it a priority right after 2.18 is otherwise ready, unless the answer comes to me while I'm at the doctor's in the morning)
[11:04] <tseliot> pitti: sorry to bother you again but the binaries for nvidia-graphics-drivers-304 and its -updates flavour are stuck in NEW (trusty)
[11:04] <tseliot> pitti: they include the same changes that you approved in the 331 series
[11:06] <pitti> tseliot: ah, the new libraries, yes; looking
[11:06] <tseliot> thanks
[11:21] <tseliot> pitti: thanks a lot!
[11:31] <ahasenack> hi guys, I have a recipe (https://code.launchpad.net/~ahasenack/+recipe/juju-deployer-daily) that started failing to build on trusty,
[11:31] <ahasenack>  dpkg-source -i -I -b recipe-{debupstream}+bzr{revno}-0~{revno:packaging}
[11:31] <ahasenack> dpkg-source: error: can't build with source format '3.0 (native)': native package version may not have a revision
[11:31] <ahasenack> but my packaging branch has source format "3.0 (quilt)"
[11:32] <ahasenack> is this an artifact of how recipes are built in launchpad?
[11:32] <ahasenack> the same package builds on saucy, for example
[11:32] <ahasenack> maybe a flag was switched in trusty to make that a fatal error?
[11:36] <infinity>   * Catch mismatches between version strings and format versions in
[11:36] <infinity>     dpkg-source. Ensure that a 3.0 (quilt) package has a non-native version
[11:36] <infinity>     and that a 3.0 (native) package has a native version. Closes: #700177
[11:36] <infinity> ahasenack: New dpkg enforces this, yes.
[11:36] <ahasenack> ok, so it looks like launchpad recipe builds will break if your package is 3.0 (quilt)?
[11:37] <ahasenack> http://bazaar.launchpad.net/~ahasenack/juju-deployer/juju-deployer-packaging/view/head:/debian/source/format is what my recipe uses
[11:37] <StevenK> You need pristine-tar information in the branch for the recipe to construct a tarball, otherwise it will override your recipe to 3.0 (native)
[11:38] <ahasenack> https://launchpadlibrarian.net/156978348/buildlog.txt.gz buildlog
[11:38] <ahasenack> StevenK: what's "pristine-tar information"?
[11:39] <StevenK> ahasenack: pristine-tar allows you to regenerate any tarball you've made from the repository information, 'man pristine-tar'
[11:39] <ahasenack> StevenK: but there is no tarball on my side, it's a launchpad recipe, it builds the package from branches
[11:39] <infinity> StevenK: Oh, does pristine-tar actually allow recipes to DTRT here?  Nice.
[11:40] <StevenK> infinity: Yes
[11:40] <infinity> ahasenack: Yes, but pristin-tar is the glue that allows you to recreate the orig.tar.gz out of your branch.
[11:40] <StevenK> infinity: Do you want to help ahasenack since it's like 2240
[11:40] <ahasenack> infinity: and what do I do with it? I have to upload it to the ppa manually first, then recipes will work, or what's the idea?
[11:40] <infinity> StevenK: Not really, it's 0440 here, and I'm sick. :P
[11:40] <ahasenack> oh boy :)
[11:40] <StevenK> Haha
[11:40] <ahasenack> looks like you both need to be asleep
[11:42] <ahasenack> infinity: that bug number from the changelog snippet you pasted seems wrong, btw, it's about "os-prober failed to detect both Windows bootable partition" ;)
[11:42] <xnox> ahasenack: the answer to your troubles, is to modify the recipe version used for the package, such that it is a native one.
[11:43] <infinity> ahasenack: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700177
[11:43] <xnox> ahasenack: otherwise, you need original tarball, which you say you don't have.
[11:43] <ahasenack> infinity: ah, debian
[11:43] <StevenK> xnox: He can recreate an orig tarball with pristine-tar
[11:43] <ahasenack> xnox: it's a recipe build, I would think that LP would take care of it (generate the tarball)
[11:43] <ahasenack> do you guys use launchpad recipes? Maybe I'm barking at the wrong tree
[11:44] <xnox> StevenK: he wants to daily-build master crap no matter what it is, not generate orig tarball for each commit ;-)
[11:44] <xnox> ahasenack: so in {debupstream}+bzr{revno}-0~{revno:packaging}, remove the "-" =)
[11:45] <ahasenack> xnox: yeah, was going to paste
[11:45] <ahasenack> {debupstream}+bzr{revno}~{revno:packaging} maybe
[11:45] <ahasenack> or s/~/+/
[11:45] <xnox> ahasenack: then your recipe will be native, no original tarball needed, and it will just build.
[11:45] <ahasenack> will have to think about it
[11:45] <xnox> ahasenack: that one will work too.
[11:45] <infinity> Depends: libstdc++6:amd64 (>= 4.1.1), libc6 (>= 2.15), libc6:amd64 (>= 2.15), libgcc1 (>= 1:4.1.1), libgl1-mesa-glx, libstdc++6 (>= 4.6), libx11-6
[11:45]  * ahasenack ponders upgrades and all that stuff
[11:45] <infinity> I win.
[11:46] <xnox> ahasenack: i think "+" will be better.
[11:46] <ahasenack> yep
[11:46] <ahasenack> xnox: thanks
[11:46] <xnox> infinity: enlighten me about your winnings =)
[11:47] <ahasenack> and lp will still add ~ubuntu<release-number> at the end
[11:47] <xnox> yes
[11:47] <ahasenack> ok, let's kick it
[11:47] <ahasenack> thanks again
[11:48] <infinity> xnox: Making your emulator stop pulling in libc6-amd64:i386
[11:49] <xnox> infinity: patches welcome.
[11:49] <xnox> infinity: what should I do? =)
[11:49] <infinity> xnox: You can pull the patch from the archive shortly. :P
[11:49] <xnox> infinity: ah, even better. thanks for that.
[11:50] <infinity> Man, this source takes a while to re-pack on a rotary disk.
[11:50] <xnox> =)
[11:51] <infinity> xnox: http://paste.ubuntu.com/6447754/ FWIW.
[11:52] <infinity> xnox: With bonus guilt-induced tech-debt swap.
[11:52] <infinity> Also, I can't spell dirty.
[11:52]  * infinity doesn't upload.
[11:52] <arun> hello guys I had a question !!! should we ask any sort of permission on developing a distro based on UBuntu named as Obuntu under the support of Obuntu group ?
[11:53] <infinity> arun: Yes.
[11:53] <xnox> arun: yes, "*buntu" is protected.
[11:54] <ogra_> infinity, your patch drops xz compression, doesnt it ?
[11:54] <infinity> arun: https://forms.canonical.com/trademark/
[11:54] <arun> Guys, where can we ask for it ?
[11:54] <xnox> ogra_: xz is default. see changelog entry above.
[11:54] <infinity> ogra_: Reading changelogs is hard?
[11:54] <ogra_> bah, i only looked at the bottom :P
[11:55] <xnox> arun: see link infinity pasted.
[11:55] <infinity> xnox: Uploaded.
[11:55]  * infinity is going to see if he can nap for a few minutes before coughing himself awake again.
[11:56] <xnox> infinity: .... thanks. it doesn't help any other packages that build-depend on gcc-multilib though. Or would this be solved by builders having multiarch enabled?
[11:56] <arun> and by the way , what is  loCo ?/
[11:57] <infinity> xnox: There aren't many packages that actually end up depending on libc6-amd64/libc6-i386, but you're right, this won't help those that do.
[11:57] <infinity> xnox: I still need to fix the libc bug that causes that situation to explode, but depending on biarch libs is generally wrong regardless, IMO.
[11:57] <xnox> arun: LoCo = Local Community, i.e. local community groups representing ubuntu in their region.
[11:58] <arun> xnox: oh
[11:58] <xnox> arun: typically they are known and participate in the Ubuntu community and thus are registered with Ubuntu Project and receiving sponsorship (e.g. free CDs & marketing materials) to promote Ubuntu.
[11:58] <ogra_> https://wiki.ubuntu.com/LoCoTeams
[11:58] <arun> Guys , does Canonical feeds Ubuntu devs ???
[11:59] <brendand> arun, we have to feed ourselves
[11:59] <xnox> arun: there are girls here as well. and these sort of questions you are asking are not related to development of ubuntu core itself. Maybe you can take this conversation to #ubuntu instead?
[12:00] <xnox> arun: i'm sure there are plenty of people who can answer these generic questions about Ubuntu Project.
[12:00] <arun> brendand: oh ok
[12:00] <arun> xnox: ok thanks a lot ; I think I went off topic
[12:02] <arun> Guys, is Unity based on Gnome 3 ?
[12:18] <mlankhorst> hmz
[12:18] <mlankhorst> MismatchError: True != False
[12:18] <mlankhorst> but that statement is true :o
[13:02]  * jpds wonders why we have a super-old util-linux on Ubuntu.
[13:04] <jpds> infinity, lamont: Oh, hi. :)
[13:06] <mitya57> Hi, I see bug 1253003 in the sponsoring queue. Any hint why that has not been auto-synced yet?
[13:12] <mitya57> gilir: Hi, may I ask you to look at https://code.launchpad.net/~m-alaa8/ubuntu/saucy/pcmanfm/fix-for-993996/+merge/195625 please?
[13:49] <pitti> $ LANG= bzr branch ubuntu:systemd-shim
[13:49] <pitti> bzr: ERROR: Revision<EMAIL_ADDRESS>ist nicht in »Graph(StackedParentsProvider(bzrlib.repository._LazyListJoin(([CachingParentsProvider(None)], []))))« vorhanden.
[13:49] <pitti> err, what does that want to tell me?
[13:49] <pitti> any known workaround?
[13:50] <pitti> err, neither LANG, LC_ALL, LANGUAGE help -- says something like "... revision ... isn't present in Graph.."
[13:52] <seb128> pitti, it's telling you "stop using udd"?
[13:52] <mdeslaur> lol
[13:52] <seb128> dunno about the specific error though :/
[13:52] <pitti> seb128: probably :/ I wanted to give it another try for developing some autopkgtests, but I guess I'll just go the classical way
[13:52] <Laney> omg, a lesser spotted wednesday troll
[13:52] <seb128> ups, did I troll again?
[13:52]  * seb128 needs to stop that
[13:53] <ogra_> yeah, not friday yet
[13:53] <Laney> haha
[13:53] <pitti> one of the few packages which don't have patches, and thus would be manageable with UDD>.
[13:53] <ogra_> fix my firefox tooltip instead :P
[13:58] <cjwatson> [New] wxwidgets3.0_3.0.0-1
[13:58] <cjwatson> No previous publications in Ubuntu
[13:58] <cjwatson> OK (Y/n)?  y
[13:58] <cjwatson>  * Trying to add wxwidgets3.0 ...
[13:58] <cjwatson> wxwidgets3.0_3.0.0-1 is trying to override modified binary wx-common_<IP_ADDRESS>-14ubuntu2.  OK (y/N)?  n
[13:58] <cjwatson> mitya57: ^- that's why
[13:59] <cjwatson> mitya57: somebody needs to work out if those two changes need to be forward-ported to 3.0
[13:59] <mitya57> cjohnston: oh thanks, will reject the bug for now then
[14:00] <mitya57> Bad xchat.
[14:02] <cjwatson> I should tee the output of auto-sync to a file on people or something
[14:36] <seb128> roaksoax, hallyn_: hey, did you guys upstream that avahi patch you uploaded to trusty?
[14:46] <smoser> slangasek, around ?
[14:46] <slangasek> smoser: vUDS
[14:46] <smoser> would you think that bug 1235231 is fixable ?
[14:51] <hallyn_> seb128: we could try submitting it to debian...  i'm not sure it's appropriate.  it's a workaround for lack of user namespaces, and i'm not very happy with it
[14:51] <hallyn_> seb128: oh, actually no we can't submit it to debian really, bc it relies on upstart
[14:52] <slangasek> smoser: what do you mean, "fixable"?  I already said in the bug log that the cloud images should just override plymouth to stop it from running
[14:52] <seb128> hallyn_, hum, k, next time it would be nice to put those details in the patch header to make work easier for whoever is looking e.g at merging that package next
[14:53] <hallyn_> agreed
[14:53] <seb128> thanks
[14:55] <smoser> slangasek, i just added a comment there.
[14:55] <smoser> by "fixable" i meant "stop being broken".
[14:55] <smoser> plymouth is explicitly "supposed" to replay content it captures. its a clear bug that it does not do that.
[14:55] <hallyn_> seb128: sorry, it didn't occur to me yesterday that it depended on upstart.
[14:55] <smoser> (as are most dataloss issues :)
[14:56] <seb128> hallyn_, no problem, thanks for the reply to my questions!
[14:57] <slangasek> smoser: don't count on a fix for that any time soon.  Workaround is known, and we don't have resources to fix all the plymouth issues any time soon
[14:57] <smoser> ok. well, then i would appreciate your thoughts as to my comment 19 there, and i'll look to get this in sooner rather than later.
[15:03] <slangasek> smoser: replied
[15:06] <smoser> slangasek, yeah, but you didn't reply the way i wanted.
[15:06] <smoser> i'd much rather have the disabler package close to plymouth, so that when/if a new upstart job is added its obvious it needs ot be fixed.
[15:06] <slangasek> there aren't going to be more upstart jobs
[15:06] <slangasek> and half those overrides are niceties
[15:17] <pitti> ooooh! http://alioth.debian.org/ just came back
[15:18] <tseliot> \o/
[15:19] <mlankhorst> yay
[15:19] <cjwatson> Yeah, it's on its way, I think they're still putting some pieces back together
[15:20] <Laney> ssh vasks works, at least, although the filesystem doesn't seem (fully) restored
[15:20] <cjwatson> Er
[15:20] <cjwatson> vasks is going away
[15:20] <cjwatson> It's being replaced by a new host
[15:20] <roaksoax> seb128: i didn't yet.
[15:21] <pitti> yeah, host key changed (understandably)
[15:21] <pitti> Laney: moszumanska now
[15:21] <cjwatson> I suggest waiting for an announcement from the alioth admins before pushing stuff
[15:21] <Laney> ah
[15:21] <Laney> I've been checking d-i-a
[15:21] <Laney> no news of that there
[15:22] <pitti> might still take a bit until it gets official, but I'm happy to see it alive again after two weeks
[15:34] <shadeslayer> cjwatson: uhm, stupid question, there was this package which had a script to build your own ubuntu live cd ( not live-rootfs ), do you know which one it was?
[15:35] <shadeslayer> oh
[15:35] <shadeslayer> it *is* live-rootfs
[15:35] <cjwatson> livecd-rootfs
[15:36] <cjwatson> but ignore livecd.sh, use the live-build hooks there
[15:36] <cjwatson> https://lists.ubuntu.com/archives/ubuntu-devel/2011-June/033458.html
[15:36] <shadeslayer> *nod*
[16:04] <smoser> mhall119, what circumstances make the 'Join hangout' link appear ?
[16:04] <jcastro> I beleive the person who runs the session needs to provide summit with the link
[16:04] <smoser> http://summit.ubuntu.com/uds-1311/meeting/22045/servercloud-1311-maas/ has hangout details, and i'm logged in, but id ont see it.
[16:05] <smoser> ah. its there now.
[16:05] <smoser> it must only appear after start of session (it should have a grace "join" period)
[16:05] <mhall119> smoser: 1) it's within the slot's start & end times, 2) the user is logged in, 3) the user is marked as attending the UDS
[16:06] <mhall119> also 4) you're not getting a stale page from the caching server sitting in front of summit.u.c
[16:06] <smoser> mhall119, well can i suggest that '1' be tweaked to include 10 or 15 minutes prior ?
[16:07] <slangasek> rbasak, smoser: do you want anyone from the server team to come to the Secure Boot session?
[16:07] <smoser> is that now ?
[16:07] <smoser> :-(
[16:07] <mhall119> smoser: you can if you file a bug for it
[16:07] <mhall119> lp:summit
[16:07] <seb128> tjaalton, tseliot, mlankhorst, coming to the xorg for t vUDS session? https://plus.google.com/hangouts/_/7ecpjg4e7ibk4vghv8fkul3tt8?authuser=0
[16:07] <smoser> k
[16:07] <slangasek> smoser: yep
[16:08] <smoser> k.
[16:08] <seb128> RAOF, ^ up? or is it still night time for you?
[16:09] <smoser> slangasek, joining
[16:11] <smoser> slangasek, can you give me a link ?
[16:11] <slangasek> https://plus.google.com/hangouts/_/72cpj2k5dn4bjr053d5ehn1lpo
[16:20] <smoser> anyone interested, http://pad.ubuntu.com/lower-third
[16:20] <smoser> thats my "howto" for vuds and lower third
[16:21] <josepht> smoser++
[16:26] <tedg> stgraber, I couldn't come to the Upstart session, but do you expect the cgroup to be created for pre-start or only when executing the job.
[16:28] <stgraber> tedg: I think we decided to go with consistency with other limit stanzas, so pre-start would also be put in the cgroup
[16:29] <tedg> stgraber, So then would pre-start be able to configure the cgroup?  i.e. this group can only use 100MB of RAM
[16:29] <stgraber> tedg: yes but it shouldn't cgroup limits should be applied through the cgroup stanza
[16:30] <tedg> stgraber, Ah, okay.  I thought the stanza only created, didn't realize the limits could be there.
[16:31] <stgraber> anyway, I'm planning to send a mail to upstart-devel later today with the suggested implementation
[16:31] <tedg> stgraber, K, I'll wait for that before I get confused :-)
[16:35] <seb128> it seems that powerpc-porter is still down, do we have any alternative solution to debug ppc issues?
[16:36] <cjwatson> I used the "machine in infinity's house" solution last time I needed it
[16:37] <dholbach> jibel, congratulations! finally! :)
[16:37] <pitti> jibel: oh, got your membership?
[16:37] <highvoltage> tedg: it's ok, you can spawn your own upstart session :p
[16:37] <ogra_> jibel, whee !
[16:38] <seb128> jibel, congrats!
[16:38] <seb128> cjwatson, thanks, we did that last time as well for indicators issues, might need to do it again...
[16:39] <seb128> infinity, ^
[16:39] <cjwatson> seb128: or you could get the package cross-building
[16:40] <seb128> I guess that's an option, less easy to set up though
[16:41] <tedg> highvoltage, I'm partially responsible for *everyone's* upstart session ;-)
[16:41] <seb128> would be nice if we had a porter box available :/
[16:41] <tedg> seb128, You can probably get a PlayStation 3 cheap :-)
[16:42] <cjwatson> we desupported those rather a long time ago :)
[16:42] <seb128> tedg, funny that you speak, the issues are indicators one, I could just get you to fix your stuff... ;-)
[16:42] <seb128> tedg, if you buy a ps3 for that, fine by me :p
[16:43] <tedg> seb128, Heh, it's a lot more than just indicators.  Webbrowser, upstart-app-launch, etc.
[16:43] <ogra_> heh
[16:44] <seb128> tedg, do we have an idea if that's a toolchain issue or what?
[16:44] <seb128> cyphermox, ^
[16:44] <tedg> It seems a lot of them are actually dependency waits.
[16:44] <seb128> oh, indicators are failing tests
[16:44] <tedg> So some false positive just looking at the icons.
[16:45] <tedg> I'm curious if it's not starting the X wrapper or something like that.
[16:45] <seb128> google test hiding the output sucks :/
[16:45] <seb128> tedg, e.g https://launchpadlibrarian.net/156991211/buildlog_ubuntu-trusty-powerpc.dbus-test-runner_14.04.0%2B14.04.20131120-0ubuntu1_FAILEDTOBUILD.txt.gz
[16:45] <seb128> the log is pretty much useless
[16:45] <Laney> blame automake not google
[16:46] <seb128> https://launchpadlibrarian.net/156995004/buildlog_ubuntu-trusty-powerpc.hud_13.10.1%2B14.04.20131120-0ubuntu1_FAILEDTOBUILD.txt.gz
[16:46] <seb128> is interesting
[16:46] <seb128> *** stack smashing detected ***
[16:47] <tedg> Yeah, it is odd.
[16:47] <tedg> Seems like a common thread is Python?
[16:47] <seb128> I've seen similar stack smash errors in one of the indicators
[16:47] <tedg> Some of the tests that use python was failing, and the dbusmock tests obviously use python.
[16:48] <seb128> doko, ^ is there a known issue with python3 on ppc on trusty?
[16:49] <tedg> *** stack smashing detected ***: python3 terminated
[16:50] <doko> seb128, updated python3 yesterday, so it could be possible
[16:50] <seb128> didrocks, cyphermox, tedg: when did those tests issues start?
[16:51] <cyphermox> two or three days ago. I'm not sure
[16:51] <cyphermox> I don't think this is python issues
[16:51] <doko> python3 changed yesterday
[16:51] <seb128> ok :/
[16:51] <tedg> Not sure either.  I just updated dbus-test-runner to use dbus-mock, so we've started using more of it as a result.
[16:51] <cyphermox> I'll get the logs shortly, there's a build running for powerpc now
[16:52] <cyphermox> tedg: seb128: https://launchpad.net/~ubuntu-unity/+archive/daily-build/+build/5249058
[16:52] <seb128> cyphermox, well, e.g https://launchpadlibrarian.net/156995004/buildlog_ubuntu-trusty-powerpc.hud_13.10.1%2B14.04.20131120-0ubuntu1_FAILEDTOBUILD.txt.gz has smashed stack python errors
[16:52] <cyphermox> well, yeah, but that might well be something different
[16:52] <cyphermox> I'd like to know for sure, and that we can get with full logs.
[16:58] <marrabld> I have a few questions about packaging.  I used to package an App in my ppa.  But since Ubuntu moved where it keeps the QT libraries my recipes have failed for modern versions of Ubuntu.  So I have to take another look at my packaging scripts.  I am going to separate my packaging scripts from the code repo (currently in the same repo as the code).
[16:58] <marrabld> So my first question is, should I put my debian directory in a separate branch and then get my recipe to merge the branches or should I put them in a separate repo.?
[17:00] <seb128> cyphermox, tedg, doko: https://launchpadlibrarian.net/157024833/buildlog_ubuntu-trusty-powerpc.indicator-messages_13.10.1%2B14.04.20131120.0-0ubuntu2_FAILEDTOBUILD.txt.gz
[17:00] <seb128> *** stack smashing detected ***
[17:01] <seb128> seems like a ppc toolchain issue
[17:01] <seb128> test-gactionmuxer is having the same problem than python
[17:01]  * tedg blames the stack for allowing itself to get smashed
[17:02] <tedg> Yeah, thinking so.
[17:02] <tedg> Not sure what, I guess we'd need a valgrind run to get some clues on what is happening.
[17:02] <seb128> doko, ^ did the ppc toolchain change recently? any idea about that?
[17:05] <smoser> anyone interested, http://paste.ubuntu.com/6449132/
[17:05] <smoser> thats a hacky script that reads a vuds link and makes nicely formated list of links to Hangout, Etherpad, IRC ...
[17:10] <hikenboot> hello I have saucy and am wondering if there is packages for gmp mpfr and mpc (prepackaged version for this version of ubuntu)
[17:11] <hikenboot> trying to consistently compile gcc correctly a package would be helpful
[17:12] <jtaylor> hikenboot: sure all build depends of gcc are packaged
[17:12] <jtaylor> apt-get build-dep gcc
[17:12] <jtaylor> also gets you ppl cloog etc
[17:12] <hikenboot> ah awsome ok didnt see that one coming but should have!
[17:13] <cjwatson> well, "apt-get build-dep gcc-4.8" is more likely to be useful
[17:13] <cjwatson> gcc -> just the defaults links
[17:14] <jtaylor> right different source :/
[17:14] <hikenboot> thanks a bunch..its really appreciated!
[17:45] <pitti> jibel: how difficult is it to fix britney/the test scripts to run newly uploaded autopkgtests?
[17:45] <pitti> jibel: e. g. I just added tests to systemd-shim, and it got promoted without running the new tests
[17:45] <pitti> s/promoted/propagated/
[17:58] <jamespage> doko, hey are you OK to attend at least the first part of the juju activities for trusty session - specifically to discuss golang support in main
[17:58] <doko> jamespage, sorry no
[17:59] <jamespage> mwhudson, ^^ any chance you could attend as doko v2?
[18:04] <doko> seb128, ?
[18:17] <Saviq> Mirv, still around?
[18:23] <Mirv> Saviq: following the sessions for a bit still
[18:23] <Mirv> what's up?
[18:24] <Saviq> Mirv, when you have a minute (doesn't have to be today) - any reason why http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/qtdeclarative-opensource-src/trusty/view/head:/debian/patches/qtquick_delegate_creation_range_itemviews.patch is dropped from 5.2?
[18:24] <seb128> does anyone know how to debug "invoke-rc.d: initscript dbus, action "start" failed." issues (happening in a chroot)
[18:25] <seb128> unping, dbus is not needed to debug that build issue (though still happening when those happen)
[18:25] <Mirv> seb128: /var/lib/dpkg/info/dbus.postscript?
[18:25] <seb128> Mirv, postscript? postinst you mean?
[18:26] <seb128> Mirv, well, ideally the start job wouldn't fail which is real issue
[18:26] <seb128> Mirv, but yeah, it can be hacked around by hacking the postinst or the init job
[18:26] <Mirv> seb128: exactly :) I've removed the failing lines when installing packages in chroot
[18:27] <Mirv> Saviq: probably it didn't apply or I thoight it's merged upstream
[18:27] <seb128> Mirv, ideally we would make the install work in a chroot rather than ask everyone to workaround it though ;-)
[18:28] <Saviq> Mirv, yeah, we'd need to port it, that one is something we're carrying ourselves, unfortunately
[18:28] <Mirv> Saviq: ah, ok
[18:30] <Mirv> seb128: sure.. I've thought it'd probably work with enough bind mounts (/dev, /sys etc) but I haven't bothered to automate those although there are tools for that too
[18:31] <infinity> seb128: My chroots all have a policy-rc.d in them that prevents daemon startup.
[18:31] <infinity> seb128: mk-sbuild does this for you.
[18:40] <seb128> thanks, I was mostly trying to help one of the Debian guys who wants to look at the smashed stack trusty issues
[18:43] <xnox> seb128: mk-sbuild is in debian.
[18:43] <xnox> seb128: "sudo apt-get install ubuntu-dev-tools; mk-sbuild trusty; schroot -u root -c trusty-amd64/i386" works on debian.
[18:43] <seb128> xnox, yeah, I don't know what he's using, he was just hitting dbus not installing because of that error
[18:44] <seb128> but that's fine, he forced over it and that's good enough for debugging the issue
[18:46] <seb128> Laney, mardy: just for info, e-d-s upstream reply about uoa/calendar
[18:46] <seb128> "I think I know what's wrong: I forgot to update the UOA .service files for
[18:46] <seb128> Google's OAuth-based CalDAV interface.  Just need to find time to test it."
[19:04] <pitti> zul: python-misaka tests fail with "ImportError: No module named 'misaka': https://jenkins.qa.ubuntu.com/job/trusty-adt-python-misaka/1;
[19:05] <pitti> zul: sorry, email notifications are broken since the CI lab change, thus playing relay..
[19:06] <zul> pitti:  crap ill fix it up
[19:06] <pitti> zul: thanks (probably just a missing test dep)
[19:07] <zul> pitti:  yeah :(
[19:08] <slangasek> mlankhorst: are you able to join the session for hwe planning for 14.04?
[19:08] <slangasek> mlankhorst: https://plus.google.com/hangouts/_/72cpi5mshd3mujd9pk5te8c50s
[19:14] <lool> cjwatson, slangasek: If either of you feels like joining the Go session, that might be useful for packaging related questions
[19:14] <slangasek> lool: can't, running another session; cjwatson?
[19:15] <cjwatson> yeah
[19:20] <smoser> bdrung, thoughts? https://bugs.launchpad.net/ubuntu/+source/distro-info/+bug/1253208
[19:53] <mwhudson> jamespage: send me email but probably not, i am on leave in an inconvenient timezone :)
[20:33] <ogra_> cjwatson, is there some config file that needs editing to get ubuntu-touch onto http://people.canonical.com/~ubuntu-archive/germinate-output/ ?
[20:54] <cjwatson> ogra_: script, but yes - edited snakefruit:~ubuntu-archive/bin/update-germinate, so that should appear for you on the next run
[20:55] <ogra_> thanks !
[20:55] <ogra_> pmcgowan always asks me weird questions why a package is in the image ... that might help a bit :)
[20:55] <pmcgowan> thanks
[20:55] <cjwatson> Yep, indeed
[20:56] <cjwatson> My oversight that it wasn't there already
[22:21] <bdrung> smoser: hi, i am happy to accept patches.
[22:22] <bdrung> smoser: returning a dict has the drawback that it could be hard to support if we want to change the internal
[22:22] <bdrung> smoser: we could add functions instead that take a series and return the fullname/version/etc
[22:24] <xnox> cjwatson: I get "dpkg-checkbuilddeps: Unmet build dependencies: libdbus-1-dev:native (>= 1.4) libexpat1-dev:native (>= 2.0.0)" when i did $ sbuild --host armhf, on just pushed lp:ubuntu/libnih
[22:25] <xnox> cjwatson: that's using trusty chroot, am I missing something? should i use some specific build-deps resolver in sbuild?
[22:39] <mlankhorst> slangasek: sorry I was eating at that time :(
[22:39] <mlankhorst> and had to be somewhere at 9, evenings are terrible
[22:39] <slangasek> mlankhorst: eating, in the middle of UDS?  surely not
[22:44] <barry> kirkland: LP: #1253458
[22:48] <pero> can anyone help me get back the unity webapps extension in chromium? it somehow disappeared and i'm at a loss on how to get it back
[23:11] <mlankhorst> oh well night


[00:19] <xubuntu18w> just installed kubuntu 1404 now my speaker is a usb hook up no sound ran add drivers nothing came up
[00:21] <knome> xubuntu18w, this is not the kubuntu support channel
[00:27] <GeekDude> Ok, I've solved the graphics problem: Just don't use FF. Though a new problem arises
[00:27] <GeekDude> whenever you unplug the power cord, half the screen backlight turns off
[07:17] <beluga_> can you guys confirm that middle-click copy and paste from LibreOffice to xterm truncates the text: https://bugs.freedesktop.org/show_bug.cgi?id=86416
[13:47] <nvt_> is there a way to get some sort of "toolbar" in xubuntu where I could put some links to documents next to the system tray
[13:49] <GrinchCube> just add a launcher to it, add an empty launcher, add something like "exo-open /path/to/file.extension" and thats all you need
[13:49] <GrinchCube> it will open with its designated default application
[13:49] <knome> or use the places applet if you want to link to all files in a certain directory
[13:50] <GrinchCube> you can make a launcher into a sort of menu too, and add a bunch of launcher to it
[13:50] <nvt_> I would like to have a quick access "toolbar" similar in windows next to the start menu :). so I assume GrinchCube 's solution seems fine
[13:50] <nvt_> afa I can add multiple icons next to each other
[13:51] <knome> you can even add them in a dropdown menu
[13:51] <knome> (even without the places applet)
[13:51] <knome> just create one launcher and add multiple items to it
[13:51] <nvt_> that's not quick access then anymore, >= two clicks with mouse ;)
[13:51] <knome> sure, whatever works for you
[13:51] <nvt_> thanks :)
[13:52] <knome> just pointing out the different options, if somebody else was wondering about the same thing
[13:52] <nvt_> yep, no problem
[13:52] <knome> (or if that would have happened to be the thing you were looking for :))
[13:56] <xubuntu22w> I have no sound issue. where to ask? where to go?
[13:57] <knome> you can ask the question here and if somebody knows the answer, they'll most likely reply
[13:57] <cfhowlett> !sound | xubuntu22w
[13:59] <xubuntu22w> netbook NC11 , intel cel. N2807, codec Valleyview2, only HDMI enabled, no analog... so no sound
[14:00] <xubuntu22w> Xubuntu 14.10 (wi-fi is ok, screen dimming=ok , previously didn't work)
[14:06] <xubuntu22w>  pacmd Welcome to PulseAudio! Use "help" for usage information. >>> list-sinks 1 sink(s) available.   * index: 0 	name: <alsa_output.pci-0000_00_1b.0.hdmi-stereo> 	driver: <module-alsa-card.c> 	flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY 	state: RUNNING 	suspend cause:  	priority: 9950 	volume: 0: 100% 1: 100% 	        0: 0.00 dB 1: 0.00 dB 	        balance 0.00 	base volume: 100% 	             0.00 dB 	volume steps: 6
[14:12] <xubuntu22w> ok, thanx
[14:27] <fnd000> quick q, my computer yesterday booted up fine, today won't boot up without nomodeset set...lightdm starts but no signal is sent to tv...
[14:27] <fnd000> only error in any log I can see...in /var/log/lightdm/x-1.log is (II) [KMS] drm report modesetting isn't supported.
[14:27] <fnd000> everything worked 100% fine before this...any updates were applied a couple of days before this happens without at least a couple of boots in between.
[14:28] <GrinchCube> fnd000: try booting with an older kernel
[14:33] <fnd000> GrinchCube: cool thanks, dpkg.log says 3.13.0-43-generic was installed 2 days before....I'll try that now botting to -40
[14:33] <GrinchCube> good luck
[14:39] <fnd000> that fixed it, many thanks....sorry, fairly ignorant on this, should I submit a bug report and if so should it be to xubuntu or for linux kernel?
[14:44] <GrinchCube> mmm, i would go to the linux kernel through launchpad
[14:44] <fnd000> cool
[16:10] <vyze> Hi all. Do anybody know how to turn off activation of the element of context menu, which was selected by holding LeftMB and  released on the element?
[18:01] <brainacid> yo I love that I can use IRC while installing this sweet distro
[19:02] <Ilhami_> I really like xubuntu :)
[19:32] <Liveinstallation> hello :)
[19:33] <Liveinstallation> i a,m on the way to install xubuntu on my system and firefox works in the live installer (whitout ram boot) :D
[22:01] <xubuntu217> hi
[22:03] <knome> hello
[22:07] <xubuntu217> hello
[22:07] <ochosi> hi
[22:07] <xubuntu217> im italian
[22:07] <knome> do you have a support question?
[22:08] <knome> or would you like to be forwarded to an italian channel?
[22:09] <xubuntu217> ieap  sorry, have try at imput in this
[22:09] <xubuntu217> chat for show converasation | dialogue about ubuntu
[22:10] <Unit193> !it | xubuntu217, maybe try here
[22:10] <xubuntu217> thank
[22:12] <ochosi> xubuntu217: ma se vuoi puoi anche provare in inglese (se hai una domanda)
[22:13] <xubuntu217> thanks but i try at change channel
[22:14] <xubuntu217> bye
[22:14] <Yuriy> Hey guys, I have a problem with sound on my monitor connected thru HDMI. I described the issue here http://ubuntuforums.org/showthread.php?t=2254042 but no one seems to know
[22:16] <drc> If you installed "U"buntu, why are you asking in a "X"ubuntu channel?
[22:18] <Yuriy> The topic is old, im running xubuntu now, same issue


[02:03] <basenjis> Hello I have a task to make Ubuntu better for everyone that is new. Have instructions to configure your ufw firewall after the first restart. Some go years not knowing they do not have a firewall configured. Fact #1
[02:23] <basenjis> What no one on this channel..figures..
[03:10] <basenjis> May the log reflect views that are important..!!!!!!!!!!!!!!


[00:29] <chewyTree> hey guys, anyone interested in this bug? https://bugs.launchpad.net/ubuntu/+source/unity/+bug/801363
[00:29] <ubot2> Ubuntu bug 801363 in unity "Win+W won't show minimized windows" [Undecided,New]
[00:30] <chewyTree> seems like it is more of a unity problem/opinion
[06:22] <TheMuso> a/c
[07:18] <pitti> Good morning
[07:18] <TheMuso> Morning pitti.
[07:22] <chrisccoulson> good morning pitti and TheMuso
[07:22] <pitti> hey chrisccoulson
[07:22] <TheMuso> Hey chrisccoulson.
[07:42] <didrocks> good morning
[07:42] <pitti> bonjour didrocks
[07:43] <didrocks> pitti: guten tag! Have you finally succeeded doing some gardening and bikeshedding despite the weather?
[07:43] <pitti> didrocks: some, it got sunny in the evening; but most of the day was pretty lazy admittedly :/
[07:44] <didrocks> pitti: well, when it's the weather forcing you, you can't be guilty :) and some rest is nice as well!
[07:45] <TheMuso> Morning didrocks.
[07:46] <didrocks> good morning TheMuso
[08:11] <chrisccoulson> it's going to be an interesting week at the rally next week
[08:14] <didrocks> hey chrisccoulson!
[08:14] <chrisccoulson> hi didrocks!
[08:43] <seb128> hey
[08:44] <pitti> bonjour seb128
[08:44] <seb128> pitti, guten tag, wie gehts?
[08:52] <seb128> nice, yesterday's iso is down by 10 to 11 mb
[08:52] <seb128> i.e almost in the budget
[08:54] <bigon> seb128: dou you think you could have a look at merging cheese from debian experimental?
[08:55] <didrocks> salut seb128
[08:55] <seb128> bigon, it's somewhat on my list but probably after the rally, it will need a collection of mirs
[08:55] <bigon> indeed
[08:55] <seb128> bigon, not speaking about the gst issue since we can only depends on good
[08:55] <bigon> yeah that's suxxs :/
[08:55] <seb128> bigon, we have work items on the gnome3 specs to mir those or demote cheese
[08:56] <seb128> but since cheese will be used in empathy and maybe ubiquity we need to discuss what to do
[08:56] <bigon> well libcheese-gtk is now on optional dep for empathy
[08:56] <seb128> right
[08:56] <seb128> lut didrocks
[08:57] <seb128> bigon, well we could mir mx, the new clutter libs, etc but we would still be blocked on the gst issue
[08:57] <seb128> hey rodrigo_
[08:57] <rodrigo_> morning
[08:57] <seb128> bigon, do you need cheese for anything?
[08:58] <bigon> well for the empathy integration, but I can live without I guess :)
[08:58] <bigon> don't want to put 100 of pkg in telepathy ppa
[08:58] <pitti> argh @ gnome-shell FTBFS; I forgot that I had a locally hacked glib header
[09:01] <bigon> about gnome-shell I think that some changes should be merged from the gnome3-team ppa
[09:02] <bigon> (like using firefox)
[09:02] <seb128> it shouldn't use firefox
[09:02] <seb128> it should use the standalone libmozjs
[09:02] <pitti> seb128: iso size> cjwatson landed the .pyc cleaning, really great
[09:02] <seb128> the goal of that lib was to avoid breaking things on firefox updates ;-)
[09:02] <seb128> pitti, indeed
[09:02] <seb128> pitti, I'm waiting to see what today's build give with deja-jup etc
[09:03] <pitti> RAOF said that he can do some more dynamic linking of the gallium drivers, and some mono libs will still disappear
[09:03] <pitti> and dropping python 2.6 support should give us some extra MBs, too
[09:03] <bigon> seb128: well I mean adding the firefox icon instead of the epiphany one in the launcher
[09:03] <seb128> bigon, oh ok
[09:04] <seb128> bigon, the nice thing now is that we are on sync with Debian ;-)
[09:04] <bigon> :p but well not for long I guess
[09:05] <seb128> depends if somebody is wanting to maintaing gnome-shell in Ubuntu
[09:05] <seb128> there was no sign of that so far
[09:06]  * bigon leaves the room without making noises
[09:07] <pitti> lol
[09:10] <pitti> seb128: ok with me backporting http://git.gnome.org/browse/clutter/commit/?id=2b81d90dd7399c409cf23d7324ff909351dbefa3 to avoid having to patch gnome-shell?
[09:10] <pitti> or should we go to 1.7.12 right away?
[09:10] <pitti> 1.7.2, sorry
[09:11] <pitti> (it's fixed there)
[09:12] <seb128> pitti, I'm fine either way, if you want to update clutter go for it
[09:12] <seb128> pitti, shouldn't g-s build if you disable the deprecation errors?
[09:12] <pitti> well, "want to" is a bit too much (I don't care at all about it), but do we need to at some point anyway?
[09:12] <seb128> we do I guess
[09:12] <pitti> or should we stay with 1.6. (stable series?) for oneiric?
[09:13] <pitti> seb128: yes, but I'd need to patch the build system for that, and this woudl mean introducing an ubuntu delta
[09:13] <pitti> that's what I want to avoid
[09:13] <pitti> it builds fine in sid, and I'd rather fix the cause than the symptom
[09:13] <seb128> until they update their glib
[09:13] <seb128> pitti, but well pick whatever is easier for you
[09:13] <pitti> right, but it's still not a bug in g-s, it's a bug in clutter
[09:13] <pitti> so it'll hit other packages as well, not just g-s
[09:14] <seb128> pitti, I would just diff clutter 1.6 tarball with -1-6trunk and dump that in a patch
[09:14] <seb128> http://git.gnome.org/browse/clutter/log/?h=clutter-1.6
[09:14] <seb128> the 4 commits
[09:14] <pitti> seb128: oh, right, they backported that
[09:14] <seb128> pitti, I don't want to decide on the new clutter today, we don't have enough visibility for that
[09:14] <pitti> right, doing that then
[09:14] <seb128> pitti, thanks
 about gnome-shell I think that some changes should be merged from the gnome3-team ppa like using firefox
[09:22] <chrisccoulson> huh????!
[09:22] <chrisccoulson> firefox doesn't even provide a shared libmozjs anymore, unless you want to load the entire browser (ie, libxul.so), just to get jsapi....
[09:22] <chrisccoulson> feel free to do that, but i *guarantee* that gnome-shell will break with every single firefox upload i do ;)
[09:23] <bigon> 10:03 < bigon> seb128: well I mean adding the firefox icon instead of the epiphany one in the launcher
[09:23] <chrisccoulson> (in addition to making gnome-shell take a decade to start) ;)
[09:23] <bigon> chrisccoulson: ^
[09:23] <chrisccoulson> oh
[09:23] <bigon> :p
[09:23] <chrisccoulson> i misunderstood there then ;)
[09:23] <chrisccoulson> that sounds better
[09:24] <bigon> well I was only at my 1st coffee when I've posted that :p
[09:24] <chrisccoulson> heh
[09:24] <bigon> that was not really clear
[09:24] <chrisccoulson> i should have read the entire scrollback before commenting ;)
[09:25] <chrisccoulson> i saw your comment and had a "WTF?" moment ;)
[09:25] <bigon> :)
[09:27] <seb128> hey chrisccoulson, how are you?
[09:27] <seb128> chrisccoulson, you alternate late night and early morning days? ;-)
[09:30] <seb128> pitti, danke fur die clutter "fix"? ;-)
[09:32] <pitti> seb128: gern geschehen
[09:32] <pitti> g-s builds fine now
[09:32] <pitti> I'll retry the build when clutter is published
[09:35] <seb128> ok
[09:45] <chrisccoulson> hi seb128, i'm good thanks
[09:45] <chrisccoulson> how are you?
[09:47] <seb128> chrisccoulson, I'm fine thank you
[10:00] <rodrigo_> ok, laptop works after a full upgrade, so ready to go to dublin :)
[10:06] <chrisccoulson> rodrigo_, there's still time for us to break it before dublin!
[10:06] <chrisccoulson> ;)
[10:07] <rodrigo_> chrisccoulson, I won't upgrade anymore :)
[10:07] <rodrigo_> specially if I see a firefox package :)
[10:09] <rodrigo_> well, there are still some kept pack packages, so will install some of those, so yeah, something can break still :)
[10:12] <seb128> hey rodrigo_
[10:13] <chrisccoulson> so, i wonder if people have started to notice yet that Synaptic hasn't actually dropped from the CD? ;)
[10:13] <rodrigo_> hi again, seb128 :)
[10:15] <seb128> rodrigo_, oh, right, I said hello one hour earlier, it's friday, has been a busy week :p
[10:15] <seb128> chrisccoulson, do you wonder if they started to notice the reason is you and your firefox? ;-)
[10:15] <chrisccoulson> lol
[10:16] <chrisccoulson> i've saved everybody! \o/
[10:16] <rodrigo_> seb128, :)
[10:16] <rodrigo_> seb128, don't worry, I like a lot when you tell me 'hi' :D
[10:16] <seb128> ;-)
[10:17] <seb128> rodrigo_, and it's a "hi" coming without bug or anything today!
[10:17] <seb128> just a friendly hello ;-)
[10:17] <pitti> seb128: you recently ran the lucid retracer manually, right?
[10:18] <seb128> pitti, yes, did I screw something?
[10:18] <pitti> seb128: the apport failure in bug 800984 looks like there were no configured apt sources for -updates/-security?
[10:18] <seb128> let's rephrase, I bet I did, "what did I break"? ;-)
[10:19] <rodrigo_> seb128, yeah, those are the ones I like :D
[10:19] <pitti> just weird because usually they get added right from the start
[10:19] <seb128> pitti, that's a natty bug there, not a lucid one?
[10:19] <pitti> seb128: ah, indeed, sorry; misread
[10:19] <pitti> seb128: I'll have a look
[10:19] <seb128> pitti, thanks
[10:20] <seb128> pitti, but yes, I'm pretty sure we usually have -updates and -security
[10:21] <rodrigo_> ok, last reboot hopefully
[10:21] <rodrigo_> brb
[10:22] <pitti> seb128: eww -- it indeed only has maverick-{updates,proposed,security?
[10:23] <seb128> pitti, hum, I probably screwed the sed call in the sources.list, sorry :-(
[10:24] <pitti> I'll check the oneiric one as well while I'm at it
[10:24] <seb128> pitti, oh no, it's not screwed sed
[10:24] <seb128> pitti, it's right for the unstable cycle
[10:24] <pitti> right
[10:24] <seb128> pitti, we just didn't change it where natty-updates opened
[10:24] <seb128> when
[10:25] <seb128> we could keep both -1 and current sources for those in the sources.list to avoid those issues
[10:25] <seb128> I guess they would just error out during the unstable cycle or be empty
[10:25] <seb128> but that should break anything
[10:26] <seb128> "shouldnt"
[10:27] <pitti> yes, I'll add both
[10:28] <seb128> pitti, thanks
[10:29]  * didrocks cries at every bzr bd-do one Qt
[10:29] <didrocks> on*
[10:30] <didrocks> weirdly, if I just dpkg-source -x, or untar the tarball, it's very fast…
[10:49] <Sweetshark> apropos very fast: the ubuntu wiki is not. it takes ~2 minutes to get a freaking login.
[11:01] <chrisccoulson> pitti - oh, you've done a new set of language packs for maverick?
[11:02] <chrisccoulson> ah yes
[11:02] <chrisccoulson> i need to update my firefox-stable PPA then ;)
[11:04] <AlanBell> hi smspillaz, would like to chat about some compiz default settings when you have a sec
[11:18] <pitti> chrisccoulson: dpm did, but yes
[11:18] <pitti> chrisccoulson: what did you change there? drop xpis and add the -locale dependencies?
[11:19] <chrisccoulson> pitti - yeah, for https://launchpad.net/~mozillateam/+archive/firefox-stable i repack them without the xpi's and add the recommends
[11:26] <chrisccoulson> oh, i'd best get them in whilst the PPA build queue is empty :)
[11:33] <njpatel> Does LightDM support automatic logins? Or is that just broken in O?
[11:35] <seb128> njpatel, it does
[11:35] <seb128> njpatel, but you need to edit /etc/lightdm/lightdm.conf
[11:35] <njpatel> seb128, aah
[11:35] <seb128> # default-user = Username of default user to log in as
[11:35] <seb128> # default-user-timeout = Delay before logging in in seconds (use 0 for automatic login)
[11:35] <seb128> njpatel, ^ those keys
[11:37] <rodrigo_> hmm, where can I see the status of the uploaded packages for oneiric?
[11:37] <rodrigo_> once accepted I mean
[11:37] <pitti> seb128: oh, we should probably fix that in casper, to work on the live system?
[11:37] <seb128> rodrigo_, gnome-desktop3 is in binary New due to the soname change if that's the question
[11:37] <njpatel> seb128, also, do you know how to stop all the default locale warnings in the terminal?
[11:37] <seb128> pitti, done previous week
[11:37] <pitti> ah, great
[11:38]  * pitti rsyncs the current ones
[11:38] <seb128> njpatel, no, don't get that here
[11:38] <rodrigo_> seb128, yes, that was the question
[11:38] <njpatel> seb128, is it just for en_GB? ;)
[11:38] <seb128> pitti,
[11:38] <seb128> casper (1.269) oneiric; urgency=low
[11:38] <seb128>   [ Colin Watson ]
[11:38] <seb128>   * Add LightDM autologin support (LP: #797669).
[11:38] <pitti> seb128: thanks
[11:38] <rodrigo_> seb128, so,where do you check that?
[11:38] <seb128> rodrigo_, launchpad, where else? ;-)
[11:38] <seb128> rodrigo_, https://launchpad.net/ubuntu/+source/gnome-desktop3/3.1.2-0ubuntu1
[11:38] <seb128> it says "New"
[11:39] <seb128> rodrigo_, https://launchpad.net/ubuntu/oneiric/+queue is the queue
[11:39] <rodrigo_> seb128, ok, was asking for a page showing the status of all source packages
[11:40] <seb128> rodrigo_, I'm not sure to understand the question, you want a list of 15000 sources with what info onit?
[11:41] <rodrigo_> seb128, no, just a way to know what's been NEW'ed, etc, but I guess checking the package source I'm interested in is enough :)
[11:41] <seb128> rodrigo_, usually just check the queue, i.e the second URL I gave you
[11:41] <seb128> or the launchpad infos for the version you uploaded and are interested in
[11:42] <seb128> rodrigo_, do you need it to be Newed?
[11:42] <rodrigo_> no, just that it didn't show up on the repos, so wanted a way to check why
[11:42] <rodrigo_> but I'll build it locally for my g-s-d build
[11:43] <seb128> rodrigo_, you didn't test build it locally before uploading? ;-)
[11:43] <seb128> rodrigo_, I can new it but I was avoiding to throw a soname change in on friday before traveling
[11:43] <seb128> rodrigo_, I figured it could wait on monday
[11:43] <rodrigo_> seb128, yes, I did, but on my desktop machine, not on the laptop, where I'm now :)
[11:43] <rodrigo_> seb128, oh yes, it can wait
[11:44] <rodrigo_> I won't upload g-s-d until a lot of testing, so it can wait
[11:44] <seb128> rodrigo_, well you can get the binaries from launchpad, the first URL I gave you
[11:44] <seb128> click on the architecture you want
[11:44] <seb128> it has links to the binaries
[11:44] <rodrigo_> no need, just built it here :)
[11:45] <rodrigo_> my question was just to check why it wasn't in the repos
[11:45] <rodrigo_> so never mind :)
[11:46] <seb128> rodrigo_, new binaries go through New and need to be reviewed or approved so you can usually assume that if things are not in they either failed to build or are waiting in New ;-)
[11:46] <rodrigo_> ok
[11:46] <seb128> https://launchpad.net/ubuntu/+source/<source>/<version> has details about the status and is the place to check in any case
[11:47] <seb128> I've a firefox shortcut to "https://launchpad.net/ubuntu/+source/<source>"
[11:47] <seb128> lpsource <source>
[11:47] <seb128> that's handy ;-)
[11:47] <seb128> I've similar ones for bug lists etc
[11:47] <rodrigo_> yeah, adding it
[11:47] <seb128> on bugzilla as well
[11:52] <seb128> hum, lunch time
[11:52] <seb128> bbl
[11:53] <pitti> seb128: indeed, autologin works fine now in kvm
[11:53] <pitti> I just don't get any default launchers in unity-2d, hmm
[11:53] <didrocks> seb128: lpp (LaunchPad Package) here, next to lpb, bg… and "latest crack" (directing to daily live CD build) :)
[11:53] <didrocks> pitti: oh?
[11:54] <pitti> didrocks: just try it
[11:54] <pitti> kvm -m 1024 -vga vmware -cdrom oneiric-desktop-amd64.iso
[11:54] <didrocks> pitti: possible under some condition, let me check something
[11:54] <didrocks> yeah, with fallbacking
[11:54] <pitti> I do get default launchers for a fresh user in the installed system (in -2d), though
[11:54] <pitti> righht, that's the auto-fallback
[11:54] <pitti> in my local testing that's with explicit choice in gdm
[11:54] <didrocks> right, but you are choosing the session for the fresh user?
[11:55] <pitti> right
[11:55] <didrocks> just one sec, confirming :)
[11:55] <didrocks> pitti: so right, it's only applied on the selected session
[11:55] <jibel> pitti, didrocks empty launcher bug 797672. could you please confirm.
[11:55] <ubot2> Launchpad bug 797672 in unity-2d "No default apps on launcher on a live session." [Undecided,New] https://launchpad.net/bugs/797672
[11:55] <didrocks> pitti: still the same issue with gconf path
[11:55] <pitti> jibel: cheers
[11:56] <didrocks> pitti: the correct solution is to choose the right session before login, so implementing the detection at the dm level
[11:56] <didrocks> which I didn't want to do with gdm, but I have a WI for that for lightdm
[11:56] <pitti> didrocks: OOI, what does that have to do with the default launchers? shouldn't they be in gconf or gsettings schemas?
[11:56] <didrocks> it's one of my goal for the sprint, but I need robert next to me :)
[11:57] <pitti> heh, then doing this as a pair indeed makes sense next week
[11:57] <didrocks> pitti: yeah, they can be in the common gconf set
[11:57] <didrocks> but that doesn't fix everything
[11:57] <didrocks> like the gconf option to tell metacity "remove decoration from maximized window"
[11:58] <pitti> oh, the session and gconf defaults are related through the default XDG path setting?
[11:58] <didrocks> you only want that in unity-2d and the guys implemented that as a gconf key, not a dbus call to detect if unity-2d is running
[11:58] <didrocks> pitti: there is a dedicated GCONF path
[11:58] <pitti> ok, now I underfstand
[11:58] <didrocks> DEFAULTS_PATH
[11:58] <didrocks> and MANDATORY_PATH
[11:58] <didrocks> and as we are running gconf before gnome-session…
[11:59] <didrocks> so yeah, all that detection should really be at the dm level to avoid that :)
[11:59] <jibel> didrocks, bug 797676 might be related too.
[11:59] <ubot2> Launchpad bug 797676 in unity-2d "Launcher doesn't autohide" [High,Confirmed] https://launchpad.net/bugs/797676
[12:00] <didrocks> jibel: hum, I don't think so as it should be the default, with or without gconf key
[12:00] <didrocks> jibel: so, if it's not, the code should, in case of no keys present, have that behavior
[12:33] <tseliot> pitti: does jockey have a function to get the current debian arch? Or shall I create one in both fglrx and nvidia's handlers (because of multi-arch)?
[12:57] <pitti> tseliot: not right now; but it's easy to find out with dpkg --print-architecture
[12:58] <pitti> tseliot: I think create it in the handlers for now
[13:28] <tseliot> pitti: maybe I can add it in nvidia-common (as the handlers use it already)
[13:35] <Sweetshark> pitti: I have a nifty little LO 3.3.3 release for natty here (actually there: https://launchpad.net/~bjoern-michaelsen/+archive/libreoffice-nattytest2/+sourcepub/1789243/+listing-archive-extra )
[13:40] <pitti> hey Sweetshark
[13:40] <pitti> Sweetshark: oh, nice!
[13:40] <pitti> Sweetshark: some changes look a bit intrusive for an SRU, though?
[13:41] <Sweetshark> pitti: I did some more changes (translations and icons updates) as 1:3.3.3-1ubuntu1~ppa2 (not uploaded yet). How should I upload that as ~ppa2 to the LO packaging archive or directly as 3.3.3-1ubuntu1, because we will SRU that (will we?) ...
[13:42] <pitti> Sweetshark: ah, it doesn't actually change multiarch bits?
[13:42] <pitti> the Debian changelog makes it sound like it, but your merge changelog says it's conditional?
[13:43] <Sweetshark> the most intrustive changes are the ~30 critical upstream fixes between 3.3.2 and 3.3.3 ...
[13:43] <pitti> these seem fine
[13:43] <pitti> I was just concerned about introducing multiarch in an SRU for the libs
[13:43] <pitti> if the packages don't actually change that, it seems fine
[13:43] <Sweetshark> lemme check a diff of debian/rules
[13:44] <pitti> Sweetshark: for the 30 upstream fixes I think we do want it as an SRU; WDYT?
[13:47] <Sweetshark> pitti: yes, I have not investigated them all that close, but if somebody ports a patch back to 3.3 after 3.3.2, it is likely worth it. (and all those are under code review upstream)
[13:50] <Sweetshark> pitti: is disabling (broken) sdbc-postgresql an issue? It is basically fubar in 3.3, so disabling it is just honest.
[13:50] <pitti> Sweetshark: yes; we can't remove a package from natty
[13:50] <pitti> Sweetshark: that's libreoffice-sdbc-postgresql, right?
[13:51] <pitti> Sweetshark: so removing it from debian/control is a no-go for natty, I'm afraid
[13:51] <pitti> Sweetshark: I'd just not touch it at all if it's broken
[13:51] <pitti> Sweetshark: for oneiric, you can make it an empty transitional package
[13:51] <pitti> (if it won't be fixed any more, ever)
[13:52] <pitti> Sweetshark: if you drop it from debian/control, we'd just introduce an archive inconsistency (NBS), and it wouldn't make the natty final version disappear
[13:53] <Sweetshark> oh, I hope it will be fixed sometime, it is not broken beyond hope.
[13:54] <Sweetshark> pitti: I can explicitly reenable it for natty, so we still explicitly build it on natty (even if broken).
[13:56] <pitti> Sweetshark: sounds better for the SRU
[13:59] <Sweetshark> the multiarch changes seem to be not be about LOs install, but about finding multiarched deps, so that should be ok too.
[14:01] <seb128> hate the retracers
[14:01] <seb128> "    from launchpadlib.errors import HTTPError"
[14:01] <seb128> who does that keep happening? fixing it...
[14:02] <Sweetshark> oh great, rene silently disabled parallel builds with more than 2 jobs (likely because of https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/759704 )
[14:02] <ubot2> Ubuntu bug 759704 in make-dfsg "make crashed with SIGSEGV" [Undecided,Confirmed]
[14:04] <pitti> seb128: meh :/
[14:05] <Sweetshark> although it can still ftbfs with 2 jobs -- its just unlikely.
[14:06] <kenvandine> cyphermox, good morning
[14:06] <kenvandine> cyphermox, working on evolution too?
[14:14] <Sweetshark> pitti: btw for 3.4.X bug 759704 will be a sure build breaker for parallel builds -- does that qualify for importance 'high'?
[14:14] <ubot2> Launchpad bug 759704 in make-dfsg "make crashed with SIGSEGV" [Undecided,Confirmed] https://launchpad.net/bugs/759704
[14:15] <pitti> Sweetshark: oh, sure; but we actually need someone to work on this/a fix, too :)
[14:17] <Sweetshark> pitti: well, there is a complete patch by me in the bug and actually a patched release in the LO ppa.
[14:17] <pitti> oh, did you subscribe sponsors?
[14:18] <pitti> ah, seems fixed upstream, nice
[14:19] <pitti> Sweetshark: (terminology nitpick: you attached a patch, not a debdiff -- there's no debian/changelog, debian/patches/* etc handling)
[14:19] <pitti> Sweetshark: want me to sponsor that for you?
[14:19] <Sweetshark> pitti: I just did not to splash into somebody elses package (esp. since you can break a lot of stuff with tweaking GNU make).
[14:21] <Sweetshark> pitti: please do. And there are changelog entries etc. in the ppa upload: https://launchpad.net/~libreoffice/+archive/ppa/+sourcepub/1733537/+listing-archive-extra
[14:24] <Sweetshark> pitti: I had that bug filed upstream too at debian http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622644 including debdiff (no changelog changes there, as I did not want to mess with debians policies), but there nobody seems to really care.
[14:24] <ubot2> Debian bug 622644 in make "parallel (-j2) make with $(eval) construct segfaults" [Normal,Open]
[14:24] <Sweetshark> (my hope was it would have been tickled donw back to us by now ;)
[14:27] <pitti> Sweetshark: hmm, it has
[14:27] <pitti> https://launchpad.net/ubuntu/+source/make-dfsg/3.81-8.1ubuntu1
[14:27] <pitti> I'm not sure why the bug wasn't auto-closed
[14:27] <pitti> Sweetshark: closed it now
[14:29]  * Sweetshark might not have noticed because of still sticking with natty quite often.
[14:30] <Sweetshark> I need more tasty dogfooding.
[14:31] <pitti> heh
[14:32] <Sweetshark> what that weird (debian) versioning (8.1) there, btw?
[14:33] <pitti> Sweetshark: -8.1 is an NMU in Debian, a Non-Maintainer Uload
[14:33] <pitti> Upload
[14:33] <pitti> it's not weird
[14:33] <davmor2> kenvandine: gwibber on natty seems to of stopped syncing twitter since I signed up to twitter on oneiric last night :(  Anything massively changed?
[14:38] <Sweetshark> pitti: weird in the "havent seen that before" sense ;)
[14:41] <kenvandine> davmor2, not in natty...
[14:41] <kenvandine> davmor2, in a terminal, killall -9 gwibber-service && gwibber-service -d
[14:41] <kenvandine> let it sync, then post the log for me
[14:41] <kenvandine> ~/.cache/gwibber/gwibber.log
[14:47] <rodrigo_> ok, g-s-d 3.1.2 seems to work ok, so pushed to the ubuntu-desktop branch, if someone wants to test it
[14:48] <seb128> rodrigo_, does it conflicts with gpm?
[14:49] <rodrigo_> seb128, no, gpm code is still in patch review, not yet in gsd code
[14:49] <rodrigo_> but it needs to conflict with gcm, checking now with hughsie
[14:49] <seb128> ok
[14:49] <seb128> is gcm going to stay around?
[14:50] <seb128> does it have extra feature or is that merged in gcc?
[14:50] <rodrigo_> all should be merged, checking
[15:02] <seb128> rodrigo_, seems fine from a review, I didn't try it
[15:02] <seb128> rodrigo_, but let's do the 3.1 landings next week as a team goal for the rally
[15:03] <rodrigo_> seb128, running it for a few days myself before uploading
[15:03] <rodrigo_> so yes, won't upload it for now
[15:03] <cyphermox> kenvandine: evo all done,
[15:03] <cyphermox> I had issues pushing last night though :/
[15:06] <kenvandine> cyphermox, cool... point me to it and i'll take a look
[15:06] <kenvandine> i installed eds last night, which of course removed evo :)
[15:07] <cyphermox> yeah
[15:07] <cyphermox> you need gtkhtml 4.1.2 as well
[15:07] <cyphermox> evo: bzr branch lp:~mathieu-tl/evolution/3.1.2-0ubuntu1
[15:07] <cyphermox> gtkhtml: lp:~mathieu-tl/gtkhtml/4.1.2-0ubuntu1
[15:10] <kenvandine> cyphermox, ok, thx
[15:11] <seb128> time for a break and some errands, I'm away for ~2 hours, will read backlog when I'm back
[15:11] <seb128> see you later
[15:11] <kenvandine> later seb128
[15:11] <cyphermox> cya, seb128
[15:11] <seb128> or see you on sunday for those who called it a week before I'm back ;-)
[15:12] <rodrigo_> bye seb128
[15:14] <didrocks> see you seb128
[15:19] <dobey> doh
[15:19] <dobey> hrmm
[15:19] <pitti> bryceh: is https://blueprints.launchpad.net/ubuntu/+spec/desktop-maverick-rootless-x something that you actually want to pursue for oneiric,  or should we just move it to the Q cycle (post-LTS)?
[15:20] <dobey> is there an equivalent to foo.gconf-defaults files for gsettings in packages in oneiric?
[15:22] <pitti> dobey: yes, e. g. /usr/share/glib-2.0/schemas/foopkg.gschema.override
[15:22] <dobey> pitti: so we install one of those files? cool
[15:23] <pitti> dobey: we have some, yes
[15:23] <dobey> great, thanks
[15:25] <Shred00> any ideas on how i can get a stack trace (i.e. from gdb) of a crash in a gnome-panel applet, like the clock?
[15:25] <Shred00> the complication of course being that it's started by the panel and crashes immediately, so no time to attach a gdb to it.
[15:27] <dobey> Shred00: does it keep crashing when you re-add it?
[15:27] <Shred00> yup
[15:28] <pitti> Shred00: enable apport for one time, let it catch the crash, and then use apport-retrace -g /var/crash/gnome-panel.crash ?
[15:28] <dobey> Shred00: when it crashes the first time, run it inside gdb, then re-add it while it's running in gdb
[15:28] <Shred00> well, i don't need to "re-add" it.  i get an error dialog asking if i want to "reload" it
[15:28] <pitti> sudo service apport start force_start=1
[15:28] <pitti> or what dobey says
[15:28] <pitti> for live debugging
[15:28] <dobey> Shred00: right, while that dialog is up, start up gdb with it, and when it's started running in gdb, hit "reload"
[15:30] <rodrigo_> where's the hotel address for the dublin rally?
[15:30] <pitti> rodrigo_: https://wiki.canonical.com/UbuntuPlatform/Rally/Oneiric
[15:31] <dobey> i am both sad and glad i am not going to dublin :)
[15:31] <rodrigo_> pitti, thanks!
[15:31] <Shred00> dobey: i must not be understanding:
[15:31] <Shred00> $ gdb /usr/lib/gnome-panel/clock-applet
[15:31] <Shred00> ...
[15:31] <Shred00> (gdb)
[15:31] <Shred00> then i hit Reload in the dialog and the dialog disappears briefly as it starts a new one which immediately dies.
[15:31] <dobey> Shred00: you need to run the applet inside gdb
[15:31] <dobey> Shred00: not simply load it, it must be running
[15:32] <rodrigo_> pitti, hmm, that page is empty
[15:32] <Shred00> ahhhh. got it.
[15:32] <dobey> Shred00: iow, type "run" and press RET :)
[15:32] <pitti> rodrigo_: sorry, recent mass-renaming; https://wiki.canonical.com/UbuntuEngineering/Rally/Oneiric
[15:32] <Shred00> damn.  pacrunner_webkit again
[15:33] <Shred00> i thought this got fixed in maveric
[15:33] <dobey> wtf is the clock applet using webkit for?!
[15:33] <Shred00> loading weather info
[15:33] <dobey> let me rephrase
[15:33] <dobey> wtf is the clock applet using webkit for?!
[15:33] <dobey> :)
[15:34] <Shred00> the clock loads weather info from the web.  but to do so, it might need to use a proxy and to resolve the proxy configuration it might need to process a proxy "pac" specification, which is javascript, so the webkit JS engine is invoked.
[15:34] <dobey> hrmm, i guess it's probably not actually using it, but soup is using libproxy which has a backend that uses the js engine
[15:34] <Shred00> dobey: you got it
[15:34] <Shred00> this problem existed in maverick also, but was fixed, iirc.  it seems to have leaked back into natty.
[15:35] <Shred00> or maybe i just fixed it here myself.
[15:36] <dobey> which is not webkit, but still; https://twitter.com/#!/dohbee/status/81015987595513857
[15:37] <Shred00> because proxies provide filtering and redirection (and content substitution) abilities that simply changing an IP address cannot.
[15:37] <Shred00> and the ability to authenticate
[15:39] <dobey> a proper network setup doesn't need proxies to do that.
[15:39] <dobey> anyway
[15:42] <dobey> pitti: hrmm, it's been a long time since i've had to install a file from debian/ to the system. and with multiple binary packages. do i put the "debian/foo /usr/share/foo/" bit inside foo.install, or in a generic "install" file, and just include it with /usr/share/foo/foo in the foo.install?
[15:43] <Shred00> dobey: proxies also cache content for reduced bandwidth usage and lower latency for the user.
[15:44] <dobey> you can have a cache without an actual proxy thing without the annoyingly crap "proxy" part
[15:44] <dobey> err, that sentence was horrible
[15:45] <dobey> you can have a cache without the actual annoyingly crap "proxy" part
[15:45] <dobey> that's better :)
[15:45] <Shred00> dobey: are you referring to a transparent proxy?
[15:48] <dobey> i'm referring to properly configuring a network so that users don't have to configure anything on their computers in every other application, to use the internet
[15:50] <Shred00> dobey: i'm all ears (or eyes if you have something to point to, or fingers if you have something for me to google for)
[15:50] <pitti> dobey: debia/nfoo /usr/share/foo/ in foo.install is fine
[15:50] <pitti> dobey: I strongly recommend not to use debian/install; it'll fall on your feet if someone adds a second binary package, or changes the order in debian/control
[15:50] <dobey> Shred00: you're using a proxy on your *personal* network?
[15:51] <dobey> pitti: ok, yeah. we have like 8 binary packages already :)
[15:51] <kenvandine> cyphermox, looking at gtkhtml
[15:51] <Shred00> dobey: our home network, yes, but could just as easily be a corporate network.
[15:51] <kenvandine> they didn't bump the api version, so it still builds a 4.0 .so
[15:52] <dobey> Shred00: well, there's a difference between "i mad a conscious choice to do this" and "the IT dept. at my job requires me to do this"
[15:52] <kenvandine> i am thinking your shlibs change should be libgtkhtml (>= 4.0)
[15:52] <kenvandine> they must not have removed any symbols, so we shouldn't break deps for things that might dep on it
[15:53] <Shred00> dobey: sure.  i am the IT dept.  but you say there are better alternatives than a proxy server to provide (a) caching, (b) authentication and (c) content restriction, so i am asking what is it/are they?
[15:54] <cyphermox> kenvandine: ok
[15:55] <kenvandine> dobey, going to have the u1/sso fix uploaded soon?
[15:55] <dobey> kenvandine: yes, lots of fixes coming today
[15:55] <kenvandine> dobey, good... i am getting harassed constantly about u1 being busted :/
[15:55] <pitti> kenvandine: do you know why indicator-*-gtk2 is on the CD images still?
[15:55] <kenvandine> and i kind of want to let my laptop sync before i travel
[15:56] <dobey> kenvandine: me too :)
[15:56] <kenvandine> pitti, yes... because we still need them
[15:56] <pitti> oh, indicator-session recommends: i-s-gtk2
[15:56] <pitti> why's that?
[15:56] <kenvandine> it is kind of a hack
[15:56] <dobey> kenvandine: nightlies will get you synced
[15:56] <kenvandine> until unity can load the gtk3 indicators
[15:56] <pitti> kenvandine: oh, I thought unity would be gtk3
[15:56] <kenvandine> not yet
[15:56] <kenvandine> almost :)
[15:56] <kenvandine> that is a goal for the rally
[15:57] <pitti> kenvandine: oh, it depends on both 2 and 3
[15:57] <dobey> kenvandine: and you should be running nightlies of u1 :)
[15:57] <didrocks> pitti: some part are
[15:57] <pitti> kenvandine: ah, so the recommends will drop once unity is fully ported over?
[15:57] <kenvandine> pitti, yes
[15:57] <pitti> ah, great; thanks for the heads-up!
[15:57] <kenvandine> np :)
[15:57] <didrocks> pitti: njpatel didn't want to push unity panel in gtk3 until all indicators were ready
[15:57] <didrocks> pitti: which wasn't the case for last release
[15:57] <kenvandine> it was better than changing the recommends in unity everytime i uploaded a ported indicatore
[15:57] <pitti> yeah, understood
[15:58] <kenvandine> i think indicator-sound is the only one left
[15:58] <pitti> kenvandine: si signore!
[15:58] <kenvandine> which ronoc just got merged
[15:58] <kenvandine> we'll upload that on monday
[15:58] <dobey> Shred00: i haven't gone about setting up such a configuration yet, so i don't have exct details. i have lots of bandwidth, so don't really need to. though once i set up vpn i may set up some stuff
[16:05] <Shred00> dobey: i don't mean to be a dick, but you are hardly speaking from a point of experience in telling me to set up my network "properly".
[16:31] <didrocks> mpt: having fun with math? :)
[16:31] <mpt> didrocks, my brain is melting
[16:32] <didrocks> mpt: heh, congrats on your research on that part btw. It's nice to see a "sort by relevancy" dump and that you really explored the problem ;)
[16:32] <mpt> At least when we get to the "Recommended for you" algorithm, I know I will be *completely* out of my league and won't be tempted to figure it out myself
[16:32] <didrocks> I'm quite scared about this algorithm TBH, a lot of research will be needed :)
[16:33] <didrocks> let's try to put that as much as possible server side for easier update and refinement
[16:34] <mpt> Oh, yes, recommendations will definitely be server-side
[16:35] <mpt> If only because the amount of data representing everything that everyone (who has opted in) has installed will be both (a) semi-confidential and (b) large :-)
[16:36] <didrocks> right, and (b) will force a lot of caching :)
[16:42] <pitti> kenvandine: shall I move the entire https://blueprints.launchpad.net/ubuntu/+spec/packageselection-desktop-n-geoclue to the p or q cycle then, and reopen the WIs?
[16:42] <pitti> kenvandine: or is that really meant to mean "DROP"?
[16:43] <kenvandine> i think drop
[16:43] <kenvandine> i think, at least for now, we have done all we are doing
[16:43] <pitti> ok
[16:43] <pitti> [magicfab] community participation to improve osm mapping:
[16:43] <pitti> is that still useful then?
[16:59] <kenvandine> pitti, that was more of a way to help people improve osm
[16:59] <kenvandine> not sure it is really relevant to the desktop
[17:01] <pitti> good night everyone! see you on Sunday evening!
[17:01] <kenvandine> good night pitti
[17:01] <kenvandine> see you soon :)
[17:02] <didrocks> see you on Sunday pitti!
[17:31] <amorphous> Hello. I have a potential bug and I would like to confirm that it should be filed against nautilus. It's miscalculating that /home is full because there are 2 samba shares mounted in /home through fstab
[17:32] <amorphous> the /home partition is ~ 600GB and the 2 shares are totaling ~ 2TB. I get the messahe that the /home is full
[17:32] <amorphous> if I unmount the drives then there's no message
[17:35] <amorphous> I'm not sure against what I should file the bug: nautilus - linux - samba ?
[17:48] <kenvandine> cyphermox, evo and friends all uploaded
[17:56] <bryceh> pitti, I do not have plans around it; RAOF might.  Move it to Q
[17:57] <rodrigo_> eod'ing, so see you all in Dublin on Monday (there were no flights on Sunday so arriving there monday morning)
[17:59] <mterry> amorphous, I'd go with nautilus
[17:59] <mterry> (it can always be moved)
[18:08] <cyphermox> kenvandine: thanks
[18:09] <amorphous> mterry, also...I've forgot to mention: df says /home is 100% when the shares are mounted. So I guess nautilus reports what the kernel says. I'll file the bug against linux
[18:09] <mterry> amorphous, k
[18:09] <amorphous> mterry, also when the drives are not mounted, df shows the reals %.
[18:09] <kenvandine> mterry, i just filed bug 801658
[18:09] <ubot2> Launchpad bug 801658 in duplicity "missing depends for ubuntuone-couch" [Undecided,New] https://launchpad.net/bugs/801658
[18:09] <kenvandine> easy fix :)
[18:11] <mterry> kenvandine, that's not quite a depends on duplicity; better on deja-dup.  But I thought it had a Recommends for it!
[18:11] <mterry> kenvandine, yeah, it does
[18:11] <kenvandine> ah,ok
[18:11] <kenvandine> weird
[18:11] <kenvandine> i just got dejadup installed today in a dist-upgrade
[18:12] <kenvandine> but no ubuntuone-couch
[18:12] <mterry> kenvandine, and it didn't pull in ubuntuone-couch?  hmm.. maybe recommends are not pulled in for a dist-upgrade?  That sounds familiar
[18:13] <kenvandine> maybe... that does sound familiar :/
[18:15] <kenvandine> mterry, just confirmed in a VM... dist-upgrade brought in deja-dup without ubuntuone-couch
[18:15] <kenvandine> bummer
[18:16] <mterry> kenvandine, but a direct apt-get install does bring it in?
[18:16] <kenvandine> it would
[18:16] <mterry> weird
[18:16]  * kenvandine didn't test that :)(
[18:16] <mterry> I assume that's intentional behavior...
[18:17] <kenvandine> yeah, confirmed
[18:17] <kenvandine> a pane though... i guess you shouldn't display U1 as a target if the deps aren't there
[18:18]  * kenvandine goes to get some lunch, bbiab
[18:18] <didrocks> dist-upgrade should, but it's a known issue it doesn't everytime
[18:18] <didrocks> use --fix-policy regularly :)
[18:26] <mterry> kenvandine, we test whether 'ubuntuone' is importable, but not each piece of the ubuntuone puzzle.  probably should
[18:27] <mterry> chrisccoulson, firefox and thunderbird are crashy for me right now.  slow down my machine, then crash
[18:29] <chrisccoulson> mterry, it seems to be ok here, and i don't think anything has changed recently :/
[18:29] <seb128> kenvandine, if you have a box showing the "don't install recommends" please keep it this way
[18:29] <chrisccoulson> got a trace?
[18:29] <seb128> kenvandine, so we can get mvo to debug it next week
[18:32] <mterry> chrisccoulson, hrm, not just those two apps now.  I'm apt to blame compiz or unity
[18:32] <chrisccoulson> heh
[18:32] <chrisccoulson> seb128, so, i'm getting somewhere the indicator issue
[18:32] <seb128> with?
[18:33] <seb128> mterry, turn a11y off :p
[18:33] <mterry> :)
[18:34] <chrisccoulson> seb128, bug 799878 (and the empty messaging indicator) - the indicator is dropping all of the incoming ItemsPropertiesUpdated signals because they have the wrong signature :/
[18:34] <ubot2> Launchpad bug 799878 in dbusmenu/0.5 "Test suite 'glib-test-proxy' failes on GLib 2.29" [Critical,Confirmed] https://launchpad.net/bugs/799878
[18:34] <chrisccoulson> but i'm not sure what changed there
[18:34] <seb128> chrisccoulson, check with dest or davidz on #gnome-hackers maybe?
[18:34] <seb128> chrisccoulson, or wait next week to check with him at the rally
[18:35] <chrisccoulson> seb128, is desrt going to be there?
[18:35] <seb128> I think so
[18:35] <chrisccoulson> cool, i can wait until next week :)
[18:35] <chrisccoulson> m_conley ^^ ;)
[18:39] <didrocks> he will be there, right
[18:40] <didrocks> hum, evolution is crashy there as well now
[18:40] <didrocks> and qt creator!
[18:48] <m_conley> chrisccoulson: hey - nice job narrowing that down! :)
[18:48] <chrisccoulson> m_conley, i still need to figure out exactly what is going on though ;)
[19:33] <evmar> just as a heads-up, we (chrome) are removing global bookmarks support
[19:33] <evmar> http://codereview.chromium.org/7252001/
[19:33] <evmar> i'll file appropriate bugs
[19:38] <evmar> https://bugs.launchpad.net/dbusmenu/+bug/801699
[19:38] <ubot2> Ubuntu bug 801699 in dbusmenu "DBus menu is very slow when using large menu" [Undecided,New]
[20:06] <chrisccoulson> evmar, thanks. how big do the bookmarks menus need to be btw? i didn't hit any issues like this with firefox
[20:06] <chrisccoulson> but then, my bookmarks menu isn't really that big
[20:14] <chrisccoulson> oh, welcome tedg \o/
[20:14] <chrisccoulson> did you see bug 801699?
[20:14] <ubot2> Launchpad bug 801699 in dbusmenu "DBus menu is very slow when using large menu" [Undecided,New] https://launchpad.net/bugs/801699
[20:17] <evmar> chrisccoulson: perhaps we're hitting some pathological behavior in the api?  i see g_list_foreach calls in the call stack, maybe some algo is unintentionally O(n^2)
[20:17] <tedg> chrisccoulson, No, I didn't.  Interesting.
[20:17] <evmar> chrisccoulson: do you have any pointer to how firefox integration works?  (was it implemented by you or by ffox upstream?)
[20:18] <tedg> It is odd.  As it should be only one foreach per level in the hierarchy.
[20:18] <tedg> evmar, Does the chrome bookmark menu have something like tag menus or something?
[20:19] <evmar> i don't think so
[20:19] <tedg> Hmm.
[20:20] <tedg> evmar, If you have the large menu running on a process could you run /usr/lib/libdbusmenu/dbusmenu-dumper on it and attach the JSON to the bug?
[20:20] <tedg> evmar, I can then put it as part of the dbusmenu test suite.
[20:20] <chrisccoulson> evmar, the firefox integration doesn't use GtkMenu (and thus bypasses appmenu-gtk and the GtkMenu parser), although i don't think that would make any difference here
[20:20] <chrisccoulson> evmar, it's sending favicons isn't it?
[20:21] <tedg> chrisccoulson, It wouldn't get the icons on the first pass, and that looks like where it's passing the structure.
[20:23] <dobey> mterry, kenvandine: can i get some sponsorship love for ubuntu-sso-client? :) https://code.launchpad.net/~dobey/ubuntu/oneiric/ubuntu-sso-client/release-1-3-1/+merge/65827
[20:26] <evmar> chrisccoulson: yeah, favicons
[20:26] <evmar> chrisccoulson: back of the envelope calculation says we can be sending 100kb+ over dbus, not sure if that works
[20:29] <mterry> dobey, I'll look at it
[20:30] <tedg> evmar, We ask for the structure with labels in one pass, and then ask for the icons in groups of 100 to limit the impact.
[20:31] <tedg> evmar, So it shouldn't be 100kb at once.
[20:31] <chrisccoulson> evmar, tbh i'm not too sure what the physical limits of dbus are. i had a problem with icon data in thunderbird before though (although admittedly, it was because of an extension sending a 512x400 icon in a menu. but that resulted in thunderbird just being aborted after a couple of minutes of sending so much data that everything just gave up - bug 749440)
[20:31] <ubot2> Launchpad bug 749440 in globalmenu-extension "Incompatibility with Thunderbird addon CuteButtons - Crystal SVG : makes TB crash when reply a mail" [Medium,Fix released] https://launchpad.net/bugs/749440
[20:32] <tedg> chrisccoulson, The limits are set in /etc/dbus-1/session.conf
[20:33] <tedg> chrisccoulson, Though, they say it should be 1G, so it seems unlikely you hit those.
[20:33] <chrisccoulson> tedg, i guess i mean "limits at where things begin to suck", rather than actual physical limits
[20:34] <tedg> chrisccoulson, Heh, the "suck limits".  We should coin that phrase.
[20:34] <chrisccoulson> :-)
[20:34] <tedg> "This is currently operating at 90% suck, so we need to start thinking about optimizing it"
[20:43] <didrocks> see you on Sunday guys!
[20:44] <tedg> 'night didrocks
[20:44] <kenvandine> didrocks, have a good weekend
[20:44] <kenvandine> see ya' soon :)
[20:44] <didrocks> tedg: you should try python on plane! :p
[20:44] <tedg> SNAKES ON A PLANE!
[20:44] <didrocks> thanks, you too tedg, kenvandine!
[20:44] <tedg> ;-)
[20:44] <didrocks> heh
[20:48] <mterry> dobey, uploaded
[20:48] <dobey> mterry: great, thanks!
[20:52] <kenvandine> mterry, dobey awesome... thx!
[21:00] <kenvandine> i love breaking ubuntu on a friday afternoon :)
[21:00]  * kenvandine hopes this dbusmenu upload doesn't cause too much havoc
[21:01] <mterry> kenvandine, if you didn't break things, what would you do during the rally?
[21:01] <bryceh> kenvandine, esp. a friday before international travel :-)
[21:01] <kenvandine> drink beer?
[21:01] <kenvandine> bryceh, exactly :)
[21:01] <kenvandine> mterry, this upload is tricky too... i breaks apps that use libindicate and libunity via GIR
[21:02] <cyphermox> speaking of breaking Ubuntu on a friday afternoon before travelling, I need to upload an update to NM :D
[21:02] <kenvandine> so i added a breaks to make it hold back
[21:02] <kenvandine> cyphermox, ugh ;)
[21:02] <kenvandine> none of us will be able to connect to wifi when traveling :)
[21:02] <cyphermox> pfft, you should know how to use wpasupplicant by itself ;)
[21:03]  * kenvandine hides
[21:03]  * cyphermox says that because he still struggles with that black magic... though less than before
[21:03] <ajvdvegt> Hi all!
[21:03] <kenvandine> although i remember when dbusmenu made nm-applet toggle my interfaces over and over again
[21:03] <cyphermox> kenvandine: right, that was fun
[21:03] <kenvandine> i was not happy about that... while tedg was on some beach in hawaii
[21:04] <ajvdvegt> Is this the right place to inform about gdm 3 issues?
[21:04] <dobey> heh
[21:04] <dobey> ajvdvegt: bugs.launchpad.net/ubuntu/+source/gdm probably is the "right place" :)
[21:04] <cyphermox> ajvdvegt: depends, what kind of issue? also, bugs are great to inform developers of issues ;)
[21:05] <ajvdvegt> :)
[21:05] <ajvdvegt> consistent segfaults count as an issue, I suppose.
[21:05] <cyphermox> yup, the best kind
[21:06] <ajvdvegt> But as GDM suddenly stopped working for me, I suppse I'm not the only one seeing this.
[21:06] <cyphermox> kenvandine: speaking of nm-applet, do you see it in unity ?
[21:06] <ajvdvegt> I'll go file a bug report, tnx.
[21:07] <cyphermox> ajvdvegt: thanks, that will be useful especially if it comes from apport (e.g. with a backtrace and everything)
[21:07] <kenvandine> cyphermox, i do
[21:07] <cyphermox> kenvandine: hrm... so why am I missing it, the power button indicator thing, and the messaging menu?
[21:08] <cyphermox> is this related to the dbusmenu upload you're doing?
[21:08] <kenvandine> cyphermox, can't be...
[21:08] <kenvandine> but
[21:08] <kenvandine> do you have indicator-application-gtk2 installed?
[21:08] <kenvandine> and indicator-session-gtk2?
[21:08] <kenvandine> etc
[21:09] <cyphermox> ah, no. uninstalled, apparently.
[21:09] <kenvandine> ah
[21:09] <kenvandine> i wonder if this is another case of recommends being ignored on a dist-upgrade?
[21:09] <cyphermox> maybe. is that recommended in ubuntu-desktop?
[21:10] <kenvandine> no
[21:10] <kenvandine> indicator-session recommends indicator-session-gtk2
[21:10] <cyphermox> ok
[21:10] <kenvandine> just until unity panel can load gtk3 indicators
[21:10] <kenvandine> but other people noticed them getting installed
[21:10] <dobey> i saw a lot of stuff get uninstalled
[21:10] <ajvdvegt> ok, I activated apport. I'm off crashing gdm now, thanks!
[21:10] <kenvandine> ajvdvegt, have fun :)
[21:11] <dobey> probably related to gnome-panel/libpanelapplet getting removed?
[21:22] <chrisccoulson> oh, dbusmenu broke ABI?
[21:29] <tedg> chrisccoulson, Yeah, we dropped an object no one was using.
[21:29] <tedg> chrisccoulson, Think of it less as "broke" and more as "refined"
[21:33] <dobey> s/no one/no one we care about/ :)
[21:58] <tedg> dobey, I'd be impressed if someone was using it.  It didn't really do anything... I guess not as much impressed as confused :-)
[22:23] <dobey> AND ubuntuone-client 1.7.0 uploaded to ubuntu
[22:24] <dobey> i hope the switch to dh_python2 didn't blow stuff up :)