[16:12] <AlanBell> Bug 749702
[16:12] <ubot2> Launchpad bug 749702 in ubiquity ""Try Ubuntu" screen-reads as "Try $RELEASE"" [High,Confirmed] https://launchpad.net/bugs/749702
[16:14] <charlie-tca> We have six more now from beta2 testing
[16:21] <AlanBell> yeah, I don't think that one is still valid though
[16:23] <charlie-tca> That would be good. We can close it with fix-released in Oneiric
[16:25] <AlanBell> just downloading beta2 now, I will do a VM install later, maybe a hardware install too
[16:27] <paul_h1> AlanBell: I didn't have much luck with the beta2 in live session mode. orca starts okay but I couldn't launch any applications
[17:13] <AlanBell> charlie-tca: bug 852583 is me moving in mysterious ways ;)
[17:13] <ubot2> Launchpad bug 852583 in gnome-orca "Orca does not pronounce "Oneiric Ocelot" very well" [High,New] https://launchpad.net/bugs/852583
[17:13] <charlie-tca> I just don't see that as critical when we can't even get the variable names in Ubiquity
[17:13] <AlanBell> I want to get the audio interface to be considered part of the branding of the operating system
[17:14] <charlie-tca> I want to have visually impaired able to know what is happening, too. I think that should be higher priority than a pronounciation of Oneiric
[17:14] <AlanBell> sure, it is
[17:14] <AlanBell> I want to get that too
[17:15] <AlanBell> but I want the visual experience people to include audio as part of their remit
[17:15] <charlie-tca> So, how does oneiric pronunciation get a higher priority than the variable names?
[17:15] <AlanBell> it doesn't
[17:16] <charlie-tca> bug 781385
[17:16] <ubot2> Launchpad bug 781385 in ubiquity "Ubiquity GTK should have useful accessible names set in the Glade .ui files instead of using the variable names" [Medium,New] https://launchpad.net/bugs/781385
[17:16] <AlanBell> what variable names anyway?
[17:18] <AlanBell> eww
[17:19] <charlie-tca> yeah, sitting for months already, and still broken
[17:19] <charlie-tca> now, I got to go cut grass here.
[17:36] <AlanBell> LDTP is only possible because of a11y stuff, not impressed that they broke it all just to make life for LDTP easier
[17:53] <maco> I have updated .ui files from Cheri
[17:53] <maco> but obviously this is a change that if i just shove it in, i'll end up with an angry evan on my hands
[17:53] <maco> and while i *do* have commit access to ubiquity... 
[18:10] <AlanBell> maco: where is the loop you mentioned?
[18:10] <AlanBell> why isn't the test testing against the actual accessible names? is it because of translations?
[18:12] <AlanBell> ls
[18:12] <AlanBell> oops
[18:12] <maco> AlanBell: look around line 200 of gtk_ui.py
[18:13] <maco> its not actually a loop, just a thing that gets called every time a widget is added
[18:13] <maco>             name = gtk.Buildable.get_name(widget)
[18:13] <maco>             widget.set_name(name)
[18:13] <maco>             atk_desc = widget.get_accessible()
[18:13] <maco>             atk_desc.set_name(name)
[18:13] <maco>             self.all_widgets.add(widget)
[18:14] <maco> oh ouch. found something that, if commented out, would make the labels readable by orca too, i think...
[18:14] <maco> just below that there's a comment saying that he's forcing the labels to not be able to take focus because then they become part of the tabbing through the page. if you could tab to a label, though....then orca would read it
[18:15] <AlanBell> it reads the labels though doesn't it?
[18:19] <AlanBell> I will try the beta2 installer later
[18:19] <AlanBell> maco: how do I run ubiquity without going through the installer?
[18:20] <maco> it reads labels on *buttons*
[18:20] <maco> the explanatory text, though? nope
[18:20] <maco> go to the "try" instead of the "Install" then run from a terminal
[18:20] <maco> with sudo, iirc
[18:21] <AlanBell> so I did bzr branch lp:ubiquity
[18:22] <AlanBell> can I run it from the branch?
[18:42] <maco> oh, no
[18:42] <maco> or well, not that i know how to do
[18:43] <maco> if you can figure out how to make it build, sure....
[18:43] <maco> but i have no idea how to build ubiquity
[18:43] <maco> it requires that debian-installer be built first then pulls some pieces from it
[18:43] <maco> ...which is why my testing of UI changes to ubiquity is in the form of poking the python files on a live cd
[18:52] <AlanBell> it does read the explanitory text on the first page
[18:55] <AlanBell> broadly speaking it is useable, if you do the install connected to the internet and let it guess location and keyboard layout
[18:55] <AlanBell> and it would be great to have the button names as they should be
[18:56] <AlanBell> I will be checking for a few bugs and maybe raising new ones
[18:56] <AlanBell> and will probably do a screencast again
[21:51]  * AlanBell closes a heap of bugs
[21:56] <AlanBell> bug 851694 is now at the top of my list of bad bugs
[21:56] <ubot2> Launchpad bug 851694 in unity "application icons in apps lens are all called "button"" [Undecided,New] https://launchpad.net/bugs/851694
[22:25] <AlanBell> charlie-tca: I am not sure where the prepare step is for bug 856782
[22:25] <ubot2> Launchpad bug 856782 in ubiquity "Prepare: Unable to read system requirements with a screen reader" [Undecided,New] https://launchpad.net/bugs/856782
[22:26] <AlanBell> ah, never mind, got it