[02:33] <parallax> Anyone having an odd red and white screen during the boot up process?
[07:00] <Cusoon959> What's the new Ubuntu release called? (next one, not Hardy...)
[07:00] <persia> Intrepid Ibex
[07:00] <Cusoon959> Thanks persia :)
[09:00] <davmor2> Morning Everyone
[09:01] <ara> morning davmor2
[09:01] <davmor2> ara: don't try using yesterday's iso for tests they will all fail :(
[09:03] <ara> davmor2: thanks for the advice. bad bad news :(
[09:04] <davmor2> alternative has missing kernel modules and live has broken x that may or may not have something to do with the missing kernel modules
[09:05] <persia> No, it was outdated hal.
[09:05] <persia> (or at least it was for me, who upgraded a system to intrepid yesterday)
[09:16] <davmor2> persia: I can only tell you the warning message I received for the alternative cd that said there are missing kernel modules......
[09:17] <persia> davmor2: Right.  There was that.  I think the non-working X was about hal, but it could also have been a side effect of kernel modules.
[09:17] <davmor2> :)
[09:18] <davmor2> I think that the error message for kernel bugs best sums up yesterdays iso.....  Ooooopps
[10:39] <davmor2> apachelogger: Morning dude :)
[10:40] <apachelogger> morning
[10:41]  * apachelogger needs to get coffee
[10:47] <davmor2> ara: don't use today's alternatives either :)
[10:47] <ara> davmor2: :)
[14:34] <cr3> schwuk: welcome back! dude, I'd like to bounce a problem with you. got a minute?
[14:35] <cr3> ara: I started the hwtest-ldtp integration yesterday and I ran into a problem: there needs to be a way to run some tests as root and some not as root
[14:35] <cr3> ara: unless you might've found a way to run the desktop tests as root
[15:17] <ara> cr3: why is necessary to run the test as root?
[15:27] <cr3> ara: some tests require access to devices, such as /dev/sda, and some tests require information which is only available to root such as provided by lshw
[15:28] <cr3> hm, I just noticed that lshw describes by machine as a "Computer" when run as non-root and "Laptop" when run as root.
[15:28] <ara> cr3: yes, for hw that's true, but for desktop testing?
[15:28] <cr3> ara: well, I'm hoping that the whole suite could be run at once
[15:29] <ara> cr3: well, the problem is that we try to mimic as much as possible the end user behaviour
[15:29] <cr3> ara: for example, I would like desktop tests to be their own suite which people could choose to run in the same way they might choose to run wireless testing
[15:30] <ara> cr3: yes, i understand, but  I think that we could maybe split between end-user suites & root suites
[15:31] <ara> cr3: update manager tests, in example, we could test the gksu dialog
[15:31] <ara> cr3: just an example
[15:32] <ara> cr3: but we have to try as much as possible to avoid relying on root privileges when running desktop tests
[15:47] <heno> IMO hwtest should always run as the user and use policy kit to elevate access only for select commands to gather hw info
[16:11] <cr3> heno: my concern is that it then becomes necessary for each test to potentially define whether they should run as root or not
[16:12] <cr3> heno: (sorry for the lag, I was on the phone with schwuk discussing the next great features in the website)
[16:13] <cr3> heno: however, I don't think that's an unreasonable requirement, so I'll start playing with the idea of using the policy kit. in principle, I agree that it would be the right thing to do
[17:59] <heno> QA meeting about to start in #ubuntu-meeting