[15:55] <jibel> mvo, on alderamin (lts upgrades), the upgrade-tester now uses the code from https://launchpad.net/auto-upgrade-testing and update-manager is in a separate directory, pulled from bzr
[15:55] <jibel> mvo, I'll update the other servers tomorrow
[16:35] <mvo> jibel: great, so I guess its time to delete code from update-manager
[16:35] <mvo> jibel: is the branch that is used configurable
[16:35] <mvo> ?
[16:36] <jibel> mvo, configurable ?
[16:38] <jibel> mvo, you can change the link AutoUpgradeTester/AutoUpgradeTest/DistUpgrade to the version of update -manager you want if that's what you mean by configurable.
[16:38] <mvo> jibel: aha, so that is how its done, ok
[16:39] <mvo> jibel: I was wondering it would make sense to have a "UseBzrBranch: lp:update-manager" in the config
[16:39] <mvo> jibel: and then on upgrade it would use bzr to pull that in, but maybe that is overkill for now
[16:40] <jibel> mvo, oh yes, that's be better. filing a bug :)
[16:42]  * mvo hugs jibel
[16:42] <jibel> bug 956175
[16:42]  * jibel hugs mvo :)
[16:50] <gema> cyphermox: I am installing precise from today's iso and the network indicator won't show the existing networks until I go to the system Settings and configure the wireless manually
[16:50] <gema> cyphermox: using desktop amd64
[16:50] <gema> cyphermox: this happens on the live session, I haven't installed just yet
[16:51] <gema> cyphermox: off to a meeting now, I will raise a bug afterwards if it haven't been reported yet
[16:51] <cyphermox> gema, wait a little, close the menu and open it again, etc. hallyn has reported something similar earlier
[16:51] <gema> cyphermox: I did wait, I tried to connect, but it wasn't there
[16:51] <cyphermox> let's make sure it does in fact show up after time, I suspect that's something outside nm-applet completely
[16:51] <gema> until I found the network manually
[16:51] <gema> cyphermox: ok, I will try later to boot again and wait and see
[16:52] <gema> if it eventually appears
[16:52] <gema> cyphermox: how long it is a reasonable time for it to appear?
[16:53] <cyphermox> I don't know, but I also don't know why it would take time to appear
[16:53] <gema> cyphermox: you suggested to wait , you tell me :D
[16:53] <cyphermox> otherwise, file a bug and I'll see if that can be matched to a specific driver being broken
[16:53] <gema> cyphermox: ack
[16:54] <cyphermox> 5 minutes top, is the time between background scans
[16:54] <gema> cyphermox: ok
[16:56] <cyphermox> above all, if something is missing from the applet, I'll need a screenshot of it to see exactly what is missing, and the usual apport information
[16:56] <gema> cyphermox: ack, will take a screenshot
[16:57] <gema> it may take me an hour and a half to get there, I have a meeting now
[18:22] <cyphermox> Gema: I think we properly identified what is broken, just need to fix it right.  If you could file a bug for what you're seeing it would be very helpful
[18:24] <cyphermox> There's a bug in wifi event code that seems to be surfacing now,  but it's not something new in the last nm upload
[18:50] <gema> cyphermox: will do
[18:51] <cyphermox> Thx
[19:09] <PaoloRotolo> Hi all!
[19:28] <gema> cyphermox: which package do you want me to run ubuntu-bug with?
[19:31] <cyphermox> network-manager
[19:32] <cyphermox> let's just be extra safe, in case the observed behavior in your case is something different
[19:33] <cyphermox> gema: you might be interested to know I've been ordering 4-5 new devices for testing 3G.
[19:33] <gema> cyphermox: ack
[19:33] <cyphermox> and a cool little gizmo to allow plugging in (supported) devices via USB when they're PCIe (but USB); so one doesn't need to disassemble a computer.
[19:34] <gema> cyphermox: this time the list of networks came up right
[19:34] <gema> cyphermox: I may need some extra time to reproduce
[19:34] <cyphermox> aye. it's a little random
[19:34] <cyphermox> well, we'll wait, I'll report a bug on my end
[19:40] <gema> ok
[19:40] <cyphermox> gema: bug 956349
[19:41] <cyphermox> hopefully we're seeing the same issue