[00:56]  * bluesabre is not sure why mugshot is broken :\
[05:25] <Unit193> bluesabre: Heya, I have a link for you about the whole core <=> desktop thing, http://sigma.unit193.net/~unit193/xubuntu-core.html
[07:27] <Noskcaj> bluesabre, Would you have time to upload the new cpufreq-plugin soon? All that's needed is a version bump
[12:24] <bluesabre> Unit193: thanks, will review that
[12:24] <bluesabre> Noskcaj: sure, will upload that tonight
[12:38] <ochosi> morning bluesabre 
[12:48] <bluesabre> morning ochosi
[12:51] <bluesabre> cool to see progress on the appearance settings :)
[12:52] <ochosi> yup
[12:52] <ochosi> it's working
[12:52] <ochosi> but themes suuuuck :)
[12:52] <ochosi> it might still need quite a bit of cleanup and review though until it can be merged
[12:53] <bluesabre> alrighty, I'll take a look at it myself tonight and see if there is anything I can contribute
[12:55] <ochosi> cool, thanks
[12:55] <ochosi> i definitely need a few pointers (pun intended)
[13:02] <bluesabre> :D
[13:08] <lderan> :P
[13:09] <bluesabre> lderan: wb!
[13:12] <lderan> hello bluesabre :D
[13:13] <bluesabre> gotta run though, bbl
[13:13] <elfy> hi and bye bluesabre :)
[14:54] <gbb> Hi, this is probably a very silly question, but... I've been following the QA testing tut and I have set up the VM and opened the iso image from within the VM dialogue.  If I install Ubuntu, it will only affect the VM and not my actual machine, right?  Or do I need to choose the 'Try Ubuntu' option instead?
[14:55] <knome> gbb, if you're running it in a VM (eg. a window), then it'll only affect your virtual machine
[14:55] <gbb> thanks :)
[14:57] <ochosi> gbb: don't forget to report your results on the tracker ;)
[14:57] <gbb> I'll try to.  Nice tut btw!
[14:59] <knome> gbb, you can always ask for more help here; we don't want missing knowledge to stop you from contributing
[15:00] <gbb> thanks, I will. Never used a VM before and didn't want to get 'unlucky'.
[15:01] <knome> understandable
[15:09] <Unit193> knome: Without +1/-1, I'm good with dat.
[15:11] <knome> on the list? :P
[15:23] <knome> bbl, hf
[15:52] <Unit193> bluesabre: Also, looking to do http://paste.openstack.org/show/DmamzKDWXVslDqIxYX8V/ it syncs core with desktop (drops a few deps to recommends), fixes order, and adds something of a formatting standard.
[16:11] <ochosi> ali1234: quick question, are you planning to fix the remaining issues in orion's gtk3?
[16:11] <ali1234> i don't know how to fix the rest :(
[16:21] <ochosi> oh, hm :/
[16:22] <ochosi> not sure we can ship it as is
[16:51] <gbb> My VM has been stuck forever on booting today's ISO.  I put the detail on a blog here: http://gabrielas-toys.blogspot.ie/2015/02/xubuntu-testing-stuff-stuck-on-swap.html (I'm still trying to step through the tut, so not sure what to do how at this point ;-)
[16:53] <elfy> gbb that looks to me like it is closing down - not booting
[16:54] <elfy> try hitting any key and it should ask you to press enter to remove image and reboot
[16:54] <elfy> but it it's hung - just shut down the vm - won't hurt it
[16:59] <gbb> aha thanks, ye olde 'any key' did the trick.  
[17:05] <elfy> :)
[19:04] <dkessel> hmm is one of our spanish translators on this channel?
[19:04] <dkessel> "us" being the xubuntu-docs package ;)
[19:06] <Unit193> dkessel: And you're sure you're building for vivid?
[19:09] <dkessel> Unit193: no :)
[19:11] <Unit193> (Was the intent to?)
[19:13] <dkessel> Unit193: heh... yeah i intended to. I am using the branch at lp:xubuntu-docs , which is in the "vivid" series and last updates by slickymaster on 2015-02-05
[19:14] <Unit193> bzr clean and don't see any es validation errors.
[19:15] <dkessel> Unit193: did you see the build log?
[19:16] <dkessel> https://launchpadlibrarian.net/197138210/buildlog_ubuntu-vivid-amd64.xubuntu-docs_15.04-201502042312~201502092059~ubuntu15.04.1_FAILEDTOBUILD.txt.gz
[19:19]  * Unit193 scratches head.
[19:24] <knome> Unit193, it's in the translators.xml file
[19:24] <knome> would be nice to see that file at that point of time.
[19:24] <Unit193> knome: I'm building in pbuilder now, will be able to.
[19:25] <knome> great
[19:26] <dkessel> thanks guys
[19:26] <knome> wow, that's a whole lot of people who poked that translation
[19:26] <knome> 17 including at least one who doesn't know spanish
[19:27] <knome> that's more people than who contributed to the source language.
[19:31] <Unit193> root@Sigma:~/xubuntu-docs-15.04# cat desktop-guide/es/translators.xml 


[19:31] <Unit193> root@Sigma:~/xubuntu-docs-15.04# 
[19:32] <knome> you fail
[19:32] <knome> :)
[19:32] <knome> why aren't there items?
[19:32] <Unit193> No, you fail! :P
[19:32] <Unit193> Remember?  Problem with something.
[19:32] <knome> no?
[19:45] <Noskcaj> Looks like we might be moving forward on getting gtk 3.16 in for release? Is there anything xubuntu is missing in terms of support for it?
[19:45] <Unit193> Oh gosh, more breakage. >_<
[19:50] <ochosi> Noskcaj: dah, theme-support? testing?
[19:50] <ochosi> frankly, i'd strongly oppose the move to gtk3.16
[19:50] <ochosi> one gtk3 version jump per cycle is enough
[19:50] <Unit193> Fankly, I'd oppose 4.14...
[19:51] <Noskcaj> ochosi, ubuntu-desktop and ubuntu-quality have a call for testing out
[19:51] <ochosi> larsu only just about finished patching up all lose ends for 3.14
[19:51] <ochosi> since when?
[19:52] <Noskcaj> https://lists.ubuntu.com/archives/ubuntu-quality/2015-February/005841.html
[19:52] <Noskcaj> today
[19:52] <knome> Unit193, fankly?
[19:53] <ochosi> Noskcaj: anyway, thanks for the heads up. i guess i'll test it and discuss it with the folks in u-desktop
[19:53] <ochosi> elky: you've tried the 3.16 ppa already?
[19:54] <knome> Unit193, pushed a small commit for -docs, watch out
[19:54] <Unit193> knome: Ah crap.
[19:54] <Unit193> ochosi: f not k
[19:54] <ochosi> arrrr
[19:54] <knome> why not k
[19:54] <knome> :P
[19:54] <ochosi> sorry elky 
[19:54] <ochosi> elfy: you've tried the 3.16 ppa already?
[19:55] <ochosi> el+tab-stop obviously isn't enough anymore these days... :'(
[19:55] <knome> ochosi, i'm sure another ping makes for the accidental one.
[19:55] <ochosi> yup, that's what i thought
[19:55] <Unit193> ochosi: I use one letter. >_>
[19:55] <elfy> the desktop one? running it currently with the shimmer themes ppa if that helps
[19:55] <ochosi> yes, that helps
[19:55] <elfy> good :)
[19:55] <ochosi> so any circles that aren't entirely circular but elliptical? :D
[19:56] <elfy> hah 
[19:56] <elfy> you type faster than me :D
[19:57] <ochosi> so no visual breakage or stuff?
[19:57] <ochosi> (especially in evince, file-roller, calc etc)
[19:57] <knome> as if elfy would notice 1px being off :P
[19:58] <elfy> I see the errant scrollbar - but everything *looks* the same here to me 
[19:58] <elfy> knome: late in for the joke then :D
[19:58] <ochosi> hehe
[19:58] <elfy> if I typed faster ochosi would have missed it too :D
[19:58] <knome> ;)=
[19:58] <ochosi> yeah, knome isn't known to be fast (see "in development" wallpaper being stuck "in development" for months, ironically ;D)
[19:59] <ochosi> hm, scrollbar
[19:59] <knome> ochosi, it's actually just damn early for 16.04.
[19:59] <elfy> oh nice - new wallpaper \o/ 
[19:59] <ochosi> i guess that is something for larsu to fix
[19:59] <knome> elfy, no, the new wallpaper i haven't even started working with :P
[19:59] <elfy> ochosi: I actually only notice it in synaptic 
[19:59] <elfy> knome: I know ;)
[19:59] <ochosi> yeah, that one is gtk3 too now
[19:59] <ochosi> so the scrollbar is missing?
[19:59] <knome> just to prove my speed..
[19:59] <ochosi> or broken?
[20:00] <ochosi> good thing is that is not really our thing to fix (at least, likely)
[20:00] <knome> brb
[20:00] <elfy> ochosi: not completely broken - but if you stop *needing* it then - it disappears, then when you start scrolling again - it comes back
[20:02] <ochosi> ah
[20:02] <ochosi> that could be a gtk3 feature
[20:02] <elfy> http://i.imgur.com/buVmOhJ.png
[20:02] <elfy> no scrollbar 
[20:02] <elfy> http://i.imgur.com/1x5Mvlq.png
[20:02] <elfy> after scrolling
[20:03] <Unit193> Can you find it with a mouse?
[20:03] <ochosi> so if you hover the edge of the listview, it appears?
[20:03] <ochosi> (yeah, basically what Unit193 said)
[20:03] <elfy> ochosi: no - you have to scroll, then the bar returns
[20:03] <Unit193> >_<
[20:03] <elfy> and "Some known issues which we'll try to fix for the release:"
[20:03] <Unit193> Scumbag GNOME...
[20:04] <elfy> "They hide completely when inactive, meaning that you don't know how far you've scrolled"
[20:04] <elfy> from laney's mail about the ppa
[20:04] <ochosi> Unit193: well, we all know which DE is the only one that really cares about mice!
[20:04] <knome> ochosi, oh my
[20:04] <elfy> https://lists.ubuntu.com/archives/ubuntu-desktop/2015-February/004631.html
[20:07] <ochosi> bbiab
[20:27] <dkessel> knome: if you tried to fix the translators list, you failed ;)
[20:27] <knome> i didn't
[20:32] <dkessel> well - then you didn't fail either
[20:32] <Unit193> Oh he did, just in a different way.
[20:33] <dkessel> heh
[20:33] <knome> better way than the way Unit193 failed
[20:33] <Unit193> knome: Heeey, it "works" just doesn't work. :P
[20:34] <Unit193> ochosi: So, (software-properties-gtk) <=> software-properties-gtk, and xdg-utils <=> (xdg-utils)?
[20:51] <gbb> I'm just about to figure out how to file a bug report, but, I'm not sure if what I found are actual bugs (as such).  Could someone take a look and let me know what, if anything to file?  Thanks :)  See http://apaste.info/0ve
[20:54] <elfy> gbb: not got a lot of time currently, to check all of that - report it here https://bugs.launchpad.net/ubuntu-manual-tests/+filebug
[20:54] <gbb> ok, will do
[20:54] <elfy> Please make sure to make the first line of what you write includes the testcase number 
[20:54] <elky> report everything, let triage figure it out
[20:54] <elfy> which is 
[20:55] <elfy> 1301 :)
[20:55] <elfy> elfy: I am triage more or less for manual testcases :)
[20:55] <knome> gbb, looks good to me, testcase number (as elfy said) is ++
[20:55] <gbb> thanks!  
[20:56] <elfy> thank you ;)
[20:57] <elfy> gbb: you going to report the test itself on the image tracker? 
[20:58] <gbb> erm, I'm not sure.  that's what I was wondering, it's not broken as such, just not what was advertised.  Probably trivial, then again, one can never be sure.
[20:58]  * elky chuckles at elfy talking to himself again
[20:59] <Unit193> Mhmm, saw that.
[20:59] <elky> i like it here, i think i'll stay :P
[20:59] <elfy> I didn't ...
[20:59] <elfy> elky: ha ha ha 
[20:59] <knome> elky, yes, lot's of humiliating situations if you like that kind of humor
[20:59]  * elky send hugs to elfy
[21:00]  * gbb is suitably confused now (even more than before)
[21:00] <knome> gbb, well i keep reading your nick as "gdb"...
[21:00] <gbb> :-D
[21:01] <Unit193> Same here.
[21:01] <elfy> gbb: I tab complete nicks - it's not often I need el<something> so it looks like I keep talking to myself instead of elky 
[21:01] <elky> gbb, if what you saw isn't matching the test case, and it's not actually break in functionality, the test case needs fixing
[21:02] <gbb> ok.  it's just a variation I guess.  I'll 'bug' it.
[21:02] <elfy> and THAT ^^ is something that causes issues - I have to change tracker fails when people fail an image because of a testcase bug 
[21:03] <gbb> ok, not quite following (this is my first testing foray) --- do you want it bugged there or a seprate report then?
[21:04] <elfy> gbb: we're talking about 2 things here, let's deal with them one by one
[21:05] <elfy> do the bug report as I said - making sure to add the testcase number to it 
[21:05] <elfy> because that's the only place the bug exists :)
[21:07] <ochosi> Unit193: sry, just back now. what's that with the seed file again?
[21:08] <gbb> elfy: ok. Will give that a go.
[21:08] <elky> elfy: we hummed and hawed over whether to fail the image on sunday even.
[21:08] <elfy> elky: because ? 
[21:09] <elfy> I was intending to be about for your jam - but forgot you have silly times :D
[21:09] <elky> because it was rather edge case
[21:09] <elfy> I was not staying up until Monday :)
[21:09] <knome> wait... we're releasing 1504, not 1410
[21:09] <knome> oops
[21:09] <elky> its ok, we did well if my screening of the new bugs list yesterday (looking for dupes) indicates anything
[21:09] <elfy> elky: aah right - generally I watch 'our' results - and unfail things that aren't fails 
[21:09] <Unit193> ochosi: I went with asking for forgiveness if you don't like it.  That's the biggest difference that I didn't touch, one depends on software-prop, the other deps on xdg-utils.
[21:10] <elfy> so usually better to err on the side of bad than good as I don't check the passes :)
[21:10] <elky> elfy: yeah, and it does completely prevent trying
[21:10] <ochosi> Unit193: have you pushed it already or where would i look at the changes again?
[21:10] <elky> well actually i didn't check that, tab first might have let try happen, but meh
[21:11] <elfy> elky: oh one of those usb booting issues? 
[21:11] <Unit193> ochosi: Next up, with someones ACK is to clean the blacklist too.  I pushed the other part already, it's just the software-properties-gtk and xdg-utils I wasn't sure which way was better to go.
[21:11] <elky> yeah, the one i raised with the window  hiding
[21:12] <elfy> elky: if you mean 'your' bug - then that's a fail in my opinion - you couldn't install 
[21:12] <elky> we could, if we hit space it took us to the next screen
[21:12] <elky> i did install on the netbook in spite of that bug
[21:12] <elky> works well once you overcome broadcom
[21:13] <ochosi> Unit193: tbh i think you know more about the seed file than me...
[21:14] <elky> elfy: yes i am talking about bug 1419555
[21:14] <elfy> yep - that's fail imo :)
[21:15] <elfy> unless they add - You Might Have To Randomly Hit Keys To Proceed to the installer :)
[21:15] <elky> yep and that's why we failed it
[21:16] <elfy> indeed - generally I think that installer fails should be fairly self evident 
[21:16] <elky> especially after lyz reproduced it on her different netbook
[21:16] <elfy> yep
[21:16] <elfy> gbb: how you getting on?
[21:17] <gbb> slowly.  currently reading the instructions.  But should be submitted soon
[21:17] <elfy> okey doke :)
[21:18] <elfy> which instructions are you reading out of interest? 
[21:19] <gbb> how to submit a bug,  plus cat decided to sidetrack me.  :>
[21:19] <elfy> aah
[21:20] <elfy> not seen how to submit a bug for a long time 
[21:23] <gbb> ok, this is not what I expected.  I thought bugs need to be submitted seperatly and then the report needs to be written.  So, in that case, what is a bug number (as opposed to test case number)?
[21:24] <elfy> gbb: ok - I'm a bit confused now
[21:24] <gbb> jas, let me gather the link.
[21:24] <elfy> what are you trying to do currently? report the testcase bug? 
[21:26] <gbb> I got this page(http://iso.qa.ubuntu.com/qatracker/milestones/326/builds/89073/testcases/1301/results) , which has the report, and then there is a link that says 'submit a bug' which gets me here:  http://iso.qa.ubuntu.com/qatracker/milestones/326/builds/89073/buginstructions
[21:28] <elfy> aah ok - seems you can only report bug against testcases when you visit the 'other' testcase 
[21:28] <elfy> that's a bug - I'll report that :)
[21:29] <elfy> all YOU need to do is go to https://bugs.launchpad.net/ubuntu-manual-tests/+filebug
[21:29] <elfy> and complete the bug
[21:29] <gbb> see why I was suspicious of the VM install not wiping my actual computer?  I am 'lucky' all too often =)
[21:30] <gbb> I also had a bug when trying to login for the first time (will try to reproduce this later on too, I may just be fatfingered).  
[21:36] <elfy> gbb: when you've done your testcase bug - ping me and we'll go through the tracker and it's bugs 
[21:37] <gbb> ok, I just submitted it, nr. 1420983 (I grabbed that from the url, the page could do with the number being displayed (for the lazy))
[21:37] <elfy> bug 1420983
[21:39] <elfy> excellent - some time soon that will land in my mailbox 
[21:39] <gbb> oh, now I see it.  small print!
[21:39] <elfy> gbb: ok so now - the tracker http://iso.qa.ubuntu.com/qatracker
[21:40] <elfy> thats' where *we* report tests and can also link bugs we found 
[21:40] <elfy> some bugs are already known and reported - others you might find 
[21:40] <elfy> now *these* bugs are real ones rather than differences in what you might see against the testcase
[21:41]  * gbb nods
[21:42] <elfy> gbb: so other than the testcase not reading right to you - any other issues that you think are real ones? 
[21:43] <gbb> The issue with the 'press enter' instructions vanishing at some point and it looking like it hangs when it's waiting for me to press enter.  Note I only have 2mb ram, so this is a slooooow operation, and I go away and do something else in the meanwhile, hence I missed it the first time
[21:44] <elfy> aah yes - I'm fairly sure I have seen that reported before 
[21:44] <elfy> that's not so much an install issue as a vm one 
[21:44] <gbb> ok, the display didn't look too healthy, it was overlaying in a funny way
[21:44] <gbb> so that's why i also suspected VM problems
[21:45] <elfy> right - sometimes vm issues are useful to report - I think I must have reported 3 or 4 nasty things last cycle 
[21:46] <elfy> but - did it reboot properly - and was installed? 
[21:46] <gbb> yep, that all worked fine.  have yet to run it though.  (as in log in and so on)
[21:47] <elfy> ok - so let's call that a pass then :)
[21:48] <elfy> gbb: was this vivid from a daily?
[21:48] <elfy> or something else? 
[21:48] <gbb> ok, so I should submit the report as a pass.  Yes it was vivid from daily
[21:48] <elfy> http://iso.qa.ubuntu.com/qatracker/milestones/326/builds
[21:48] <elfy> find the xubuntu items at the bottom
[21:49] <elfy> then click either 64 or 32 bit
[21:50] <gbb> ok got there and added the hardware profile
[21:50] <Unit193> bluesabre / ochosi: Please review changes to the seed: https://code.launchpad.net/~xubuntu-dev/ubuntu-seeds/xubuntu.vivid/ (We can also add some more unity components if we'd like.)
[21:52] <elfy> gbb: so assuming you've got to the right testcase, page down past the writing - right at the bottom you get option to fail/pass/in progress it  - then RIGHT at the bottom submit 
[21:53] <ochosi> Unit193: i guess adding some common unity components might not be a bad idea. might help with stuff like the 14.04.2 mess in the future
[21:53] <gbb> elfy: shipped!  Thank you for your patience :)
[21:53] <elfy> gbb: \o/
[21:54] <elfy> http://iso.qa.ubuntu.com/qatracker/milestones/326/builds/89073/testcases/1301/results
[21:54] <elfy> right to the right hand side - do you see a pencil by the side of your entry there? 
[21:54] <ochosi> nice work guys/gals!
[21:54] <gbb> yep
[21:55] <elfy> gbb: ok, so say that you wanted to report a bug, didn't have time right now - you could edit your result and put the bug in later 
[21:55] <elfy> then update instead of submit appears at the bottom 
[21:56] <elfy> ochosi: yep - nice to see people coming along and finding all this out :)
[21:56] <gbb> ... or correct it? :>
[21:56] <elfy> yep :)
[21:56] <elfy> sometimes you might find that someone like me has come along and changed your result
[21:57] <elfy> this is what I was talking about earlier when people fail for the wrong reasons 
[21:58] <gbb> nod, it's not easy to tell at first I guess.
[21:58] <elfy> yep - as I said to elky - sometimes it's better to err on the side of fail than pass
[21:59] <Unit193> ochosi: Alright, so *-control-center and unity-greeter.
[21:59] <elfy> gbb: but as a general rule - a bug with a testcase is never going to be a reason to fail an image test
[22:00] <gbb> maybe add another option, say 'beauty error'?
[22:02] <ochosi> Unit193: yeah, sounds fair enough to me
[22:02] <Unit193> ochosi: http://paste.openstack.org/show/zqREo6CkdolsOMdeVAX9
[22:05] <gbb> sort of for when you don't know if it's a showstopper or not. To give the reviwer a headsup that this might just be spurious.
[22:05] <ochosi> Unit193: that looks good to me!
[22:05] <Unit193> Great!  Already pushed it. ;P
[22:08] <elfy> gbb: that's kind of taken care of in the grand scheme of things
[22:08] <elfy> gbb: say you find bug X and report it on the tracker and fail the test
[22:09] <elfy> gbb: I could come along and say - that's not a fail, change it to a pass and also change the bug you reported to invalid or wishlist or something else 
[22:12] <gbb> that's also true.  (the one bug tracker I've used before was bit more pedestrian than this)
[22:12] <elfy> does that make sense to you? 
[22:12]  * gbb nods
[22:12] <elfy> :)
[22:12] <elfy> anyway - awesome stuff - thanks a lot :)
[22:12] <gbb> thank you too!  (that was fun)
[22:13] <elfy> gbb: and this is in reference to you pointing a bug on the website "balloons> elfy, nice catch actually"
[22:13] <elfy> elfy> someone I am talking to in #xubuntu-devel brought it to my attention :)
[22:13] <elky> gbb: i believe "papercuts" is the term used for tiny things that detract from the product
[22:13] <elfy> so - \o/ all round
[22:13] <ochosi> Unit193: cool, i like the hands-on-ness ;)
[22:13] <elfy> elky: yep 
[22:13] <Unit193> ochosi: I like review and ACKs. :P
[22:13] <elky> elfy: wasn't sure if it still was ;)
[22:14] <Unit193> ochosi: But thanks, and 'welcome.
[22:14] <ochosi> Unit193: hehe
[22:14] <ochosi> same same
[22:15] <gbb> heh.  now to see if I can reproduce the longin hiccup (it eventually worked, but not before confusing me by claiming repeatedly it's a bug.  I think it's because it asked me for my name and then choked on two words)  -- it did work eventually, but it's not clear why
[22:16] <gbb> name != username 
[22:20] <knome> gbb, it's probably the known bug that stops you from logging in until your ubuntu SSO account is linked with a launchpad one
[22:21] <gbb> ah, ok.  I guess I had better find a new bug then to entertain me.  Thanks all!
[22:23] <elfy> knome: no - they've done tracker report ok 
[22:26] <gbb> that's the bug page I got when trying to login.  Then I clicked on some other link (not sure which by now) and it let me in.  http://iso.qa.ubuntu.com/user/password?name=Gabriela%20Gibson
[22:27] <gbb> I think the misunderstanding was asking me for my name, instead of what username I want too
[22:27] <elfy> oh that's SSO :|
[22:28] <elfy> I really hate SSO :|
[22:28] <knome> elfy, as i said, gbb probably just hit the very known bug
[22:28] <gbb> so now my username is gabriela-gibson (which is ok) but unplanned
[22:28] <knome> the good part is... you can't hit that twice.
[22:28] <knome> gbb, actually you can change that when you log in to launchpad
[22:29] <gbb> yeah, but it might make it tought to get in, I actually had to be persistent here.  I was already trying to figure out where to send mail for help
[22:29] <knome> gbb, i wrote a full blog article on this: http://open.knome.fi/2014/02/23/logging-in-with-ubuntu-one/
[22:29] <knome> gbb, basically go to https://launchpad.net/~/+edit, log in and change the "name" (which is actually the "username" for SSO)
[22:30] <knome> (or if you are logged in, then don't log in again...)
[22:30] <gbb> eh, I don't mind, I use my real name for coding anyway (have a blog with it) but this is a bit of a showstopper for newbies.  if you cannot log in, you cannot play!
[22:30] <knome> we know
[22:35] <gbb> that ancient!  Maybe get your link posted on the log in page till that's fixed? People tend to give up very easily normally, which is a pity.
[22:36] <knome> gbb, well seriously speaking, canonical should just fix that bug.
[22:37]  * gbb hands knome an extra 'n' to make a precise cannonball
[22:37] <knome> hah
[22:37] <knome> ;)
[22:37] <knome> you should join #xubuntu-offtopic where all the rants happen :P
[22:37] <gbb> better not.  or they'll fire me instead :P