[00:04] AlanBell, if i try to enlarge the fonts by google mail the fonts go be unreadable [00:04] with using ctrl + [00:36] goodnight all [07:19] natty beta2, after unmuting and loading orca, restarting desktop i got to the slideshow part of isntall using unity and didnt know where to go from there [07:19] any ideas === API is now known as apinheiro [09:23] hey [09:28] hi ubuntu === ubuntu is now known as webczat [09:28] i actually always forget that I don't have webczat nick when starting up [10:19] Hmm, what's the reason for the speakup and speakup-sources package to exist in natty? [10:20] I'll clarify: packages are needless because the speakup module is already included in .28 [10:24] webczat: are they on the CD? [10:25] !info speakup natty [10:25] They are present as kernel modules on the cd. espeakup connector is still needed, but modules are not cause they are already there. it's in drivers/staging/speakup. [10:27] * AlanBell mentions in #ubuntu-kernel [10:27] Speakup is kernel builtin as of .37. [10:27] And I see it. [10:29] I still do. === jackneill is now known as Jackneill [11:04] what can it mean if I dd on the hard disk and after few minutes, the system sometimes freezes for few seconds? [12:12] Hey, I have problems with at-spi2. [12:12] The login screen is inaccessible, also things like a logout/shutdown dialogs aren't. [12:16] hmm wait === apinheiro is now known as apinheiro_lunch [14:08] How do you correctly install at-spi2? like if I do it, some programs speak, but things like a logout or gdm don't. === apinheiro_lunch is now known as apinheiro [15:39] i really don't understand this at-spi2 thing [16:28] Erm, does anyone know why at-spi2 does not read my login screen, and logout/shutdown dialogs? [16:31] they are normally seen as inaccessible [16:31] when at-spi2 is running [16:33] it annoys me [16:34] but I don't know if this is because at-spi is not started when it should, or this if my fault, or what? [16:34] s/if/is [16:42] because I don't know if I need to fill a bug or do something. [16:45] TheMuso: rather than always having to edit orca's package, do you think it'd make sense for the orca scripts for various packages to be included in the packages themselves? that way a package maintainer or an upstream could handle the scripting of that app themself [17:04] maco: i made a qt-at-spi test yesterday === erkan^ is now known as zippo^ [17:34] maco: I think adding them to the application package makes sense for projects that have some person/team that takes care of it (that way PPAs with newer versions also include newer Orca scripts), but what if upstream doesn't care? === zippo^ is now known as erkan^ === jhernandez is now known as jhernandez|gone === erkan^ is now known as zippo === zippo is now known as zippo^ === zippo^ is now known as erkan^ [22:55] maco: Thats not a bad idea actually.