[07:26] <ara> morning!
[08:24] <jibel> Good morning!
[09:25] <ara> mvo, morning
[09:25] <ara> mvo, what kind of test you want me to do in the mini9?
[09:26] <ara> mvo, installing 10.04 and check the time to upgrade open office?
[09:32] <mvo> ara: yeah and if ahci mode in the bios makes a difference
[09:33] <mvo> ara: for my system (lenovo s12) it does make a big difference, with ahci I get the 6h upgades times you have, but with it its much better (~1.5h)
[09:33] <mvo> ara: but that may specific to the lenovo HW or even my machine/bios or something like that
[09:33] <mvo> so we may have two bugs here
[09:45] <ara> mvo, OK, I will try that and will post results as bug comments
[11:13] <ara> mvo, what chipset does your netbook have?
[11:16] <mvo> ara: ICH7/N10 is what lspci tells me
[11:17] <ara> well, mine is an  i945
[11:17] <ara> and I don't have a ahci option in the bios
[12:37] <davmor2> cyphermox, ara: I've added a quick screencast showing the wifi issue I have to https://bugs.launchpad.net/ubuntu/+source/pm-utils-powersave-policy/+bug/649357 there is also now a semi-fix for it
[12:37] <ubot4> Launchpad bug 649357 in pm-utils-powersave-policy (Ubuntu) "network-manager on une will not connect (affects: 1) (heat: 8)" [Undecided,New]
[12:38] <cyphermox> oh, cool
[12:40] <cyphermox> davmor2, I'll take a look at pm-utils-powersave-policy then, it should be fairly easy to figure out where the issue lies
[12:40] <davmor2> cyphermox: I'm assuming it the policy one.
[12:41] <cyphermox> let's see. I have touched pm-utils a bit before so maybe I can find what's wrong
[12:44] <davmor2> cyphermox: so something change between this version of pm-utils and the last version (from last week) that has broken this
[12:45] <cyphermox> possible.
[12:47] <cyphermox> looks to me like -policy would be only in lucid, not in maverick, so it would really be pm-utils instead; but I'll take a look at the code shortly (just want to finish up something else first)
[12:49] <davmor2> cyphermox: np's
[12:49] <davmor2> I was guessing at policy as it had powersave in the title
[12:51] <cyphermox> right, it did make sense; I just looked at the publishing history and it's not in maverick "pm-utils 1.4 integrates the scripts now, and more"
[12:52] <davmor2> ah :)
[14:47] <davmor2> cyphermox: nice catch :)
[14:47] <cyphermox> davmor2, there is a BIOS setting?
[14:48] <davmor2> is there what is it?
[14:48] <cyphermox> the what what?
[14:48] <cyphermox> I see my testing this broke my irc connection, hold on
 davmor2, the only thing that would be interesting to check now re: bug 649357 would be to check whether in the BIOS the wifi device has special settings for power saving.
[14:48] <ubot4> Launchpad bug 649357 in bcmwl (Ubuntu) "bcmwl doesn't handle powermanagement on/off properly, turns device on or off (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/649357
[14:53] <davmor2> cyphermox: the bios on this thing is really restrictive there are hardly any settings you can modify at all
[14:54] <cyphermox> ok
[18:30] <sujiths80> hi friends ..my name is sujith ..I wish to enroll for ubuntu testing...how can I start...please help me
[18:38] <GrueMaster> One place to start is to look at http://qa.ubuntu.com.  Testing can be tracked at http://iso.qa.ubuntu.com.   Even though RC testing is now finished, you can look through there and get ready for release testing next week.
[18:38] <GrueMaster> And welcome to the fold.
[20:45] <jibel> bladernr, did you try to upgrade wubi from 10.04 to 10.10 ?
[20:45] <bladernr> jibel:  I didn't get to it.
[20:46] <bladernr> jibel:  if you'd like me to though, I can right now.
[20:47] <jibel> bladernr, yes, that would be great, there's something that needs to be cleared see bug 653134, another user is seeing that too. we need more tests.
[20:47] <ubot4> Launchpad bug 653134 in wubi "Can't boot Ubuntu after an upgrade from 10.04.1 to 10.10 (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/653134
[20:48] <bladernr> ok... I'll have something in about an hour
[20:48] <jibel> bladernr, I can reliably reproduce the failure, I first though it was due to the gnome-keyring failure, but I retried today and I can't boot ubuntu.
[20:48] <jibel> bladernr, I tried amd64 and i386, same failure.
[20:51] <bladernr> hrmm... ok
[20:51] <bladernr> I may be able to try both... I'll see what I can do
[20:52] <jibel> bladernr, cool, thank you