[11:51] <knome> madnick, how's the plymouth stuff?
[12:19] <knome> astraljava, you had a HP laptop? what wifi? i just installed xubuntu on wife's laptop, and with the broadcom wifi, i needed to use the b43 driver instead of the STA driver, which got installed by default..
[12:41] <astraljava> knome: I'll get back to you about that later, gotta run now.
[15:40] <madnick> knome: pretty much solid, the "problem" I have is that, while I can test it using my own message sequences, I cannot test it using VBox and get the real messages, since I don't see the screen at boot
[15:43] <knome> madnick, then just push it for others to test
[15:45] <madnick> okay
[15:49] <ochosi> hey there
[18:30] <astraljava> knome: What was that again? My freenode server rebooted, and using SSL reconnects in a weird way, and thus I /quit and /connect'ed, thus losing backlog.
[18:34] <knome> 14:19  knome: astraljava, you had a HP laptop? what wifi? i just installed xubuntu on wife's laptop, and with the broadcom wifi, i needed to use the b43 driver instead of the STA driver, which got installed by default..
[18:34] <knome> astraljava, ^ that
[18:37] <astraljava>   *-network
[18:37] <astraljava>        description: Wireless interface
[18:37] <astraljava>        product: BCM4313 802.11b/g/n Wireless LAN Controller
[18:38] <knome> i have bcm4312.
[18:39] <astraljava> configuration: broadcast=yes driver=brcmsmac driverversion=3.0.0-16-generic firmware=N/A latency=0 link=no multicast=yes wireless=IEEE 802.11bgn
[18:39] <astraljava> brcmsmac
[18:40] <astraljava> Huh, nice names for these drivers.
[18:42] <knome> heh
[21:18] <knome> pleia2, you there?
[21:18] <TheMouldyMarsBar> knome: hardly anyone comes here
[21:19] <knome> TheMouldyMarsBar, wrong. many people come here regularly. sometimes they just lurk.
[21:19] <TheMouldyMarsBar> *hardly anyone CHATS here
[21:20] <knome> well, that's wrong too. people chat here when they need to discuss about development
[21:20] <TheMouldyMarsBar> Most just go to #xubuntu
[21:20] <knome> now that we have all freezes ongoing, there's not much to communicate about, except some bugs
[21:21] <knome> well, #xubuntu is for the support. if you need support, that's the correct channel.
[21:22] <knome> we don't specifically discourage random chatter here now and then, but usually people take that to #xubuntu-offtopic or other channels
[22:09] <pleia2> knome: hey
[22:12] <pleia2> no response yet from the trademarks folks :\
[22:13] <knome> pleia2, umph.
[22:13] <knome> pleia2, i was thinking the alternate disc still
[22:13] <pleia2> knome: to drop it?
[22:13] <knome> pleia2, well yeah. isn't there any other way to achieve those certain things?
[22:14] <pleia2> use server alt and install xubuntu-desktop :)
[22:14] <knome> do you think that's something we shouldn't tell people to do?
[22:14] <knome> i mean, testing the alt vs. not testing
[22:15] <knome> and maintaining vs. not
[22:15] <knome> those are the things
[22:15] <pleia2> oh, that, we will keep the alt?
[22:15] <pleia2> gotcha
[22:15] <pleia2> what is the blocker to testing the alt?
[22:15] <knome> is it worth it?
[22:15] <knome> nothing really
[22:15] <knome> time and resources
[22:16] <knome> if we didn't have alt, we'd have more tests on desktop
[22:16] <pleia2> ok, I think desktop has to take precedence
[22:16] <knome> the other choice is to drop anything in the alt-tests to "run-once"
[22:17] <pleia2> I can't help with hardware testing (no spare hardware) but I can help with virtual testing of alt
[22:17] <knome> whatever the case, i think we'd benefit from more testing
[22:17]  * pleia2 has been meaning to help with testing more anyway
[22:17] <knome> and actually reporting and discussing issues sooner
[22:17]  * pleia2 nods
[22:17] <knome> i'm not really pro-drop-alt
[22:18] <pleia2> I love alt
[22:18] <knome> but i'm just wondering if we have the resources for it
[22:18] <pleia2> yeah :\
[22:18] <pleia2> will you be around for a couple hours?
[22:18] <knome> we should maybe take a poll or so in the website on how many people will use alt
[22:18] <knome> probably yeah
[22:18] <knome> as long as my back can take it, yeah
[22:18] <pleia2> ok, I am going to go grab my lunch and then I'll sit down to look at testing stuff
[22:18] <knome> okay, sure
[22:19] <knome> bon appetit :)
[22:19] <pleia2> I did testing before when it was a wiki page list of tests ;) but I haven't used the iso tracker yet
[22:19] <knome> ah
[22:19] <pleia2> oh, I'll start the daily downloads now
[22:19] <knome> well, that's pretty cool
[22:19] <knome> it's really straightforward
[22:19] <knome> and i think just promoting testing could get us easily a few people doing tests now-and-then
[22:19]  * pleia2 nods
[22:19] <knome> but of course, we need continuous contributions :/
[22:19] <pleia2> once I figure out how to do it, I'll write that blog post I've been meaning to write
[22:20] <knome> mm-hmm
[22:20] <pleia2> preference to testing 64 vs 32?
[22:20] <knome> ping me when you get back from lunch
[22:20] <knome> i think it depends on what has been tested
[22:21] <pleia2> and is there a daily alt?
[22:21] <knome> looks like we have 0 tests on everything for 20120310
[22:21] <pleia2> ok
[22:21] <knome> yup
[22:21] <pleia2> ah, /daily vs /daily-live
[22:22] <pleia2> ok, wgets going, I'll ping you when I return :)
[22:24] <knome> good
[22:25] <ochosi> knome: https://bugzilla.xfce.org/show_bug.cgi?id=7381
[22:25] <ochosi> unfortunately it's a bit too late for precise, but for +1 we could make use of this
[22:27] <knome> hmm
[22:27] <knome> right
[22:27] <ochosi> (if you remember the appmenu-button proposal we worked on)
[22:27] <knome> yeah, i do
[22:28] <knome> do you have any opinion on testing?
[22:28] <ochosi> do you mean anything concretely?
[22:28] <ochosi> (haven't had time to read the backlog yet and am about to watch a movie)
[22:29] <knome> astraljava, ?
[22:29] <astraljava> Sorry.
[22:29] <knome> for what? :P
[22:30] <knome> when was the QA meeting again?
[22:30] <astraljava> I think it was on Wednesdays.
[22:30] <knome> "was" ?
[22:30] <astraljava> Haven't participated lately anymore.
[22:31] <knome> right
[22:33] <knome> ubuntu wiki sucks
[22:57] <pleia2> knome: back
[22:58] <knome> pleia2, mmh :)
[22:59] <knome> i just tweeted our next community meeting
[23:00]  * knome gets some tea to drink
[23:01] <pleia2> so https://wiki.ubuntu.com/Testing/ISO/Procedures is the page charlie-tca gave me 
[23:03] <knome> just log into http://iso.qa.ubuntu.com/
[23:03] <knome> i can guide you through
[23:04] <pleia2> done
[23:04] <knome> so, on the first page you have the milestones
[23:04] <knome> you want precise daily, of course
[23:04]  * pleia2 nods
[23:04] <knome> when you click that, you'll have a list of products
[23:04] <knome> you can slim it down by unchecking most stuff on the left pane "filters"
[23:05] <knome> you probably want to leave "upgrade" and "xubuntu" (and statuses "untested" and "partial")
[23:05] <pleia2> cool
[23:05] <knome> when you've done that scroll to the bottom
[23:05] <knome> you can see the xubuntu tests
[23:06] <knome> alt amd64, alt i386, desktop amd64, desktop i386
[23:06]  * pleia2 nods
[23:06] <knome> let's say you want to test desktop amd64
[23:06] <knome> click that
[23:06] <knome> now you can see all the testcases
[23:06] <pleia2> let's say i386, since I actually got that one ;)
[23:06] <knome> hehe, okay ;)
[23:06] <pleia2> ok
[23:06] <knome> there are the testcase-specific results
[23:07] <knome> passed/failed/running, and the bugs column will show links to any bugs that are found
[23:07] <knome> for a working example, look at the desktop amd64 beta1 tests: http://iso.qa.ubuntu.com/qatracker/milestones/208/builds/12681/testcases
[23:07] <pleia2> ah, nice
[23:07] <knome> well anyway, the nicer thing
[23:08] <knome> there's the download info link on top
[23:08] <knome> with rsync/zsync commands
[23:08] <knome> and http of course
[23:08] <knome> with gpg signs and md5 checksums
[23:08] <knome> ALSO
[23:08] <pleia2> oh that is much better than trying to remember the cdimage link :)
[23:08] <knome> you have the document icons with the tool
[23:08] <knome> if you click that, you'll get the procedure for that testcase
[23:09]  * pleia2 nods
[23:09] <knome> now, when you start testing a testcase, you click on the testcase name
[23:09] <knome> let's say live session
[23:09]  * knome logs in
[23:10] <knome> now you have this simple add a result -page
[23:10] <knome> first, you select the outcome
[23:10] <knome> then add bug #s for critical and normal bugs
[23:10] <knome> and you can add a hw profile url and/or a comment, eg "vbox with 512 ram"
[23:11] <knome> i don't think we're using "in progress" -result much now, but i think we could benefit from that if we ever have more testers
[23:11] <pleia2> ok
[23:11] <knome> that way you wouldn't start doing the same test somebody else is on
[23:11] <pleia2> where does the hw profile url come from?
[23:11] <knome> it can be anything
[23:11] <knome> some people add a wikipage for the HW info
[23:11] <pleia2> oh, like a link to a product page for your laptop?
[23:12] <knome> but if you test with vbox, comment would be okay
[23:12] <pleia2> ah
[23:12] <knome> well, that would work as well
[23:12] <knome> i don't know about it, but i suppose it's not clearly specified what that should be :)
[23:12]  * pleia2 nods
[23:12] <knome> but yeah, that simply is it
[23:13] <knome> if you go back to the "precise daily" page, you can see the columns mandatory and run once
[23:13] <knome> those will have the number of testcases run
[23:14] <knome> like a good overview :)
[23:14] <knome> and the bugs too
[23:14] <pleia2> ok cool
[23:14] <pleia2> I'll do a test and ask questions about where my bugs go ;)
[23:14] <knome> again good example; http://iso.qa.ubuntu.com/qatracker/milestones/208/builds
[23:14] <knome> well, bugs should be at LP
[23:15] <knome> in the ISO tracker, you only need their numbers
[23:15] <knome> and the system will fetch the rest
[23:15] <pleia2> yeah, I never know what packages to file stuff against
[23:15] <pleia2> so I'll just ask
[23:15] <GridCube> evening
[23:15] <pleia2> hey GridCube 
[23:15] <knome> ah :) most probably ubiquity ;))
[23:15] <GridCube> say miss pleia2 
[23:15] <GridCube> :)
[23:16]  * knome says: miss pleia2 
[23:16] <GridCube> can i help in anything?
[23:23] <pleia2> ok, so wait
[23:23] <pleia2> Install (auto-resize) in Xubuntu Desktop i386 for Precise Daily links to http://testcases.qa.ubuntu.com/Install/AlternateResize
[23:24] <pleia2> the 64 bit links to http://testcases.qa.ubuntu.com/Install/DesktopResize which I assume is correct
[23:24] <knome> ah, yeah :)
[23:24] <knome> most probably
[23:24]  * pleia2 qas the qa
[23:25] <knome> hehe
[23:27] <pleia2> ah, but I see a prerequisite for that one is actually having something to resize ;)
[23:27] <knome> :)=
[23:27] <knome> run a different test first, then resize
[23:28] <knome> that's another thing that doesn't help getting resize-test-results
[23:31] <pleia2> there is all kind of strange greyness on the screen, not sure if it's just vbox weirdness
[23:32] <knome> pleia2, is it https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/924909 ?
[23:32] <pleia2> I think so, http://princessleia.com/temp/xubuntu_031012.png
[23:32] <pleia2> more grey happens when I move the window
[23:33] <knome> yuuup!
[23:33] <knome> that's it.
[23:33] <pleia2> I have a background at least, not black
[23:34] <pleia2> ah, someone says that
[23:34] <knome> well yeah, that part is fixed
[23:34] <knome> after we uploaded a wallpaper ;))
[23:34] <pleia2> hehe, that helps
[23:34] <pleia2> ok, so this bug still exists, do I list the bug number into day's test?
[23:34] <knome> yeah
[23:34] <pleia2> ok
[23:34] <knome> but it's not critical
[23:34] <knome> since you can still finish the testcase
[23:34] <pleia2> yep
[23:36] <pleia2> tsk, "arch" reports i686 rather than i386
[23:37] <knome> :)
[23:39] <pleia2> alright, that's all done
[23:41] <pleia2> thanks knome :)
[23:41] <knome> no, thank you :)
[23:46]  * knome switches to wife's laptop with newly installed xubuntu over windows vista \o/
[23:46] <pleia2> \o/
[23:52] <pleia2> the alt installer is such a pretty blue, did you guys do that?
[23:52] <pleia2> the debian one is fugly (I use it /all the time/)