=== dous__ is now known as suodla [06:35] morning all! === asac_ is now known as asac [09:59] installer crashes on the last step, anyone having those same issues? === marjomercado is now known as marjo [13:08] oi fader|away stop hiding ;) === fader|away is now known as fader_ [13:21] davmor2: Shouldn't you be sleeping? [13:30] davmor2: When you have a moment, can you say "ls -l /usr/share/checkbox/scripts" on your checkbox test system and tell me if they are all +x? [14:03] fader_: Probably but I'm up and at it [14:06] Heh [14:10] fader_: added to the bug dude [14:10] some are some aren't [14:11] davmor2: Aha! Can you please try "sudo chmod a+x /usr/share/checkbox/scripts/*" and then see if you still get the sound recording bug? [14:13] fader_: :) \o/ [14:14] davmor2: I take it that fixed it? [14:14] Yes [14:14] There's already a bug open about this issue, so I'll dupe the bug you're working on to it. I had it assigned to me, but I think it's something cr3 needs to fix as it's a packaging problem [14:15] in fact all the tests that failed dismally now work :) [14:19] Yeah, it's a pretty simple bug. Executable scripts need to be executable. Go figure :) [14:20] If only all bugs were that easy hey [14:21] :) [15:19] cr3: I was trying to run the backend to see if it showed anything up that the frontend didn't. when runing the tests. But as it turns out it was just fader_'s fault [15:19] davmor2: I understand, it's always fader_'s fault [15:20] cr3: I might blame this one on you, or at least try to share it :) [15:20] cr3: but only so he blame you it's our jobs [15:20] The deb needs to have +x on /usr/share/checkbox/scripts/* [15:21] fader_: that's weird, mine are all +x [15:22] cr3: I saw the same thing in my manual testing yesterday... when I installed checkbox from your PPA, many of the scripts were not +x [15:23] fader_: is that in base checkbox or perhaps in -compatibility or -certification? [15:23] cr3: I believe it's just base checkbox, as it's /usr/share/checkbox/scripts (rather than checkbox-compatibility/scripts or checkbox-certification/scripts) [15:24] Nothing else but the vanilla checkbox package writes to /usr/share/checkbox/ does it? [15:24] fader_: right, so it was the base [15:25] hi there [15:26] is it still worth to test the beta? [15:26] unimatrix9: yeap [15:26] cr3: Assigned the bug to you and commented [15:26] 9.10 beta, or should i go for daily build? [15:26] unimatrix9: Please do! [15:26] ok i will thanks [15:27] unimatrix9: there is no daily build till monday probably to allow people to download beta [15:27] hehe [15:27] ok good [15:27] davmor2: And to allow the release team to catch their breath ;) [15:27] ubuntu keeps moving fast [15:27] and let our machines cool down [15:28] put them in the fridge for a while.. [15:28] :) [15:28] * unimatrix9 reading known issue's [15:29] hmm, whats the story, from init.d to upstart, and now a newer way? [15:30] unimatrix9: Not sure what you mean by a newer way... still using upstart [15:31] Some users report that, in connection with the conversion of the base system to native upstart jobs, the system will fail to boot if the root partition has errors. [15:31] i mis read it [15:31] i thought it was a change in upstart.. :P [15:32] Ah :) [15:33] ok thanks for the info, downloading it now , testing it tomorrow, bug reporting the day after... [15:33] bye all [15:33] :) [15:33] take care! === asac_ is now known as asac === jsalisbury_ is now known as jsalisbury === marjomercado is now known as marjo === fader_ is now known as fader|away [22:36] Why does https://wiki.ubuntu.com/Testing/Automation/Roadmap not even list karmic? [22:46] I activated the update manager (this is a new system I installed 9.04 on, copying my /home partition over from my old machine) and it hung for about 5-10 minutes before starting any sort of dialog. [22:46] Any idea what might be causing that? [22:47] I think https://wiki.ubuntu.com/Testing under "Test automation" should say something like: "To run the automated tests, run: aptitude install mago checkbox && mago && checkbox"? [22:56] I'll run the tests, but this is an issue with the updater: it showed the release notes, don't install on production machine, etc. I hit the go button, and then it just hung. The window just kind of went blank and stopped responding to input while it chugged along, and I couldn't see any major CPU activity in top. I ignored it, and it eventually proceeded to show a progress bar and all, but it seems like something sho [22:56] uld be done about the nonresponsive segment. [22:58] FlyingBishop: File a bug. === yofel_ is now known as yofel