[02:28] <calc> anyone awake?
[02:28] <Scorcher> yo
[02:29] <calc> have you seen an issue during install that lots of various files are created with a gid of 999?
[02:29] <Scorcher> no, have not tried to install yet...  was coming here to see how is been going.   Tring to decide if I am going to install now or wait for final
[02:30] <calc> i did an install of ubuntu desktop amd64 and it made a lot of files with invalid gid's
[02:30] <Scorcher> how do you know?  did you get an error?
[02:31] <calc> i reinstalled my main machine then started looking around while setting it up and saw a lot of files with gid 999
[02:31] <Scorcher> hrm, no idea
[02:31] <calc> i think i will file a 'ubuntu' bug and assign it to colin he'll probably know where to look
[02:32] <calc> i managed to use find to fix them up but that is a bit ugly for the release
[08:05] <davmor2> Good Morning everybody
[08:22] <davmor2> Guys has anyone got Bluetooth on their phone and intrepid machine?
[08:57] <persia> davmor2, I have that combination.  What do you need tested?
[08:58] <davmor2> persia: in beta I could just connect to my phone with very little in the way of problems now in rc I can't at all
[09:00] <davmor2> It will eventually detect my phone but then I don't get the type this number in to pair page and instead get connection failed
[09:00] <persia> davmor2, Hrm.  That's especially bad.
[09:01] <persia> Do you have bluez-compat installed?
[09:01] <davmor2> persia: also in hardy I could send pics from my phone to my pc by default now I can't :( is much glumness
[09:02] <davmor2> persia: default install but will check
[09:05] <persia> Yeah.  phone -> pc is a regression from hardy.  Install gnome-user-share to work around it.  Should be fixed for Jaunty, but fixing it for intrepid would mean apache2 as part of the standard desktop install, which is just wrong.
[09:06] <davmor2> persia: seems to not be installed but also it isn't in main.  As I say in beta it works so something has been done to break it :)
[09:09] <persia> davmor2, Hrm?  phone -> pc worked in beta?  It shouldn't have done.  pairing sounds like a regression from beta though.
[09:10] <davmor2> persia: no sorry pc -> phone worked in beta
[09:10] <davmor2> there are some bluez updates 2 ticks
[09:11] <persia> OK.  You had me worried.  pc -> phone should still work.
[09:11] <davmor2> last time phone -> worked was hardy :)
[09:11] <persia> Hrm.  I thought those bluez changes made RC.  timezones are frustrating.
[09:12] <persia> Some people had phone -> pc working for early intrepid alphas, but keyboards & mice were broken.
[09:19] <davmor2> nope failing
[09:19] <davmor2> bug time
[09:20] <persia> Yep.  Let's hope it's something easy.
[09:20] <davmor2> just revert back to beta for bt
[09:41] <davmor2> persia: can you confirm this please? https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/288613
[09:41] <ubot5`> Launchpad bug 288613 in gnome-bluetooth "Intrepid: RC Regression.  Bluetooth no longer pairs correctly which it did in beta" [Undecided,New]
[09:42] <persia> davmor2, Take me a bit, as I'll have to install beta and then install RC :)  Do you mind if I test with -mobile?  should be the same code, and lets me combine a couple operations.
[09:43] <davmor2> no probs :)
[11:00] <BUGabundo_work> hi
[11:00] <BUGabundo_work> testing RC/daily from USB pen drive
[11:00] <BUGabundo_work> getting into initframfs after squasfs
[11:22] <BUGabundo_work> do I need to spam dev around here?
[11:24] <persia> BUGabundo_work, What are you trying to express?
[11:26] <persia> BUGabundo_work, In case you missed my last comment.  For what would you need to "spam dev"?
[11:27] <BUGabundo_work> I did
[11:27] <BUGabundo_work> pidgin crashed
[11:27] <BUGabundo_work> I was talking to wgrant
[11:27] <BUGabundo_work> on #ubuntu+1
[11:27] <BUGabundo_work> about my suspend prob
[11:27] <BUGabundo_work> so he recommended I testes RC/daily
[11:27] <BUGabundo_work> I resynced my iso, and burned it to a pendrive
[11:28] <BUGabundo_work> when I booted, I got thrown at a initramfs persia
[11:28] <BUGabundo_work> can't see a way to get logs
[11:28] <persia> Hmm.  None of the other testers reported that from what I saw.
[11:29] <persia> How did you burn the ISO to a pendrive?
[11:29] <BUGabundo_work> ok
[11:29] <BUGabundo_work> that's why I'm reporting it
[11:29] <BUGabundo_work> with usb-creator
[11:30] <BUGabundo_work> tested 2 pendrives
[11:30] <BUGabundo_work> both kingston
[11:30] <BUGabundo_work> one 8GiBs and another 4
[11:30] <BUGabundo_work> the first has already too much use
[11:30] <BUGabundo_work> and seem to be failing to get to casper
[11:30] <DistroJockey> the usb creator failed for me with a 2GB PQI flash
[11:30] <BUGabundo_work> but the second is brand new
[11:31] <DistroJockey> failed as in it couldn't find  linux  to boot from
[11:31] <persia> Very odd indeed.  What error did you get on boot?
[11:31] <persia> Especially odd.  What HW?
[11:32] <BUGabundo_work> no error
[11:32] <BUGabundo_work> just sent to busybox
[11:32] <BUGabundo_work> after starting sqashfs
[11:32] <BUGabundo_work> at 13.188889 seconds
[11:32] <BUGabundo_work> its a laptop
[11:32] <DistroJockey> I got syslinux to the  Boot: prompt
[11:32] <BUGabundo_work> asi/asustek s37s
[11:33] <BUGabundo_work> intel C2D 8300 at 2.4GHz
[11:33] <BUGabundo_work> 4GiBs ram
[11:33] <BUGabundo_work> using 64 bits iso
[11:33] <BUGabundo_work> I've booted several times during beta until now from my 8GiBs pen
[11:34] <BUGabundo_work> first busybox I've seen on ibex with this laptop
[11:35] <persia> Does using Alt+arrow keys get you to a console log?  try booting with noquiet.  I'd recommend filing a bug against "linux", but don't know how else to get the logs.  Maybe someone in #ubuntu-bugs would have a better idea.
[11:35] <BUGabundo_work> I can navigate on it, yes
[11:36] <BUGabundo_work> I always clear the splash and quite flag
[11:36] <BUGabundo_work> does noquite do anything diff?
[11:36]  * BUGabundo_work visits #ubuntu-bugs
[11:38] <BUGabundo_work> persia: no answer there either
[11:38] <persia> BUGabundo_work, noquiet prints out the boot messages so you can see what's going on.
[11:38] <persia> Maybe just file a bug then.  I'm fairly certain it's your HW, but don't know how to collect the information.  RC test window is closed, so there's nowhere for testers to report it specifically, other than as bugs.
[11:39] <persia> #ubuntu+1 may also give you ideas.
[16:27] <kabads> hmm - am I the only one who can't see the instructions to  upgrade in the email and release notes and the upgrading  details to upgrade to the pre-release of 8.10? The email  refers to the release notes, which refer to an upgrade page,  which only details upgrades to 8.04.
[16:29] <persia> kabads, Check the bugs against ubuntu-website.  I think that was reported.  If it wasn't, please file.
[20:14] <esac_> hi. does ubuntu have any concept of a stress test. i would like to install ubuntu+1, and then run an automated stress test which simply 'uses' the system non stop. does such a thing exist?
[20:17] <persia> esac, There are a few people working on different sorts of automated testing, but I don't know of any suite that does what you describe.  If I were to put something like that together, I'd probably start with dogtail.
[20:19] <esac> i wish i had the time to put it together. i just have 2 spare computers here i was thinking i could install daily builds on, and hook up a kernel debugger and just let them run non stop to try to catch issues
[20:53] <muibe> hi everybody, it'd be nice to help little bit if it's needed
[20:55] <persia> muibe, Best thing to do now is to grab the RC, test the applications, and file bugs.
[20:57] <muibe> yeah, i've been testing the beta for a while and now I'm upgrading it into the latest RC version
[20:58] <muibe> PulseAudio has been somehow buggy at least.. it worked without any problems in Hardy but I've had to tweak it quite a bit after the beta upgrade
[20:59] <muibe> and the wireless driver of Atheros 5006 wasn't still working as it was the case with Hardy too
[21:00] <muibe> Emerald crashes every now and then too
[21:01] <muibe> problems with nvidia was mentioned already and i knew it before I upgraded..
[21:15]  * esac has to find his system rescue cd so he can partimage his laptop before installing RC