[01:18] <skellat> Unit193: Alrighty, I think it should look a little better now: https://code.launchpad.net/~skellat/xubuntu-docs/xubuntu-docs/+merge/154236
[01:42] <Unit193> I just think it's odd having "back at the disconnected computer" twice, but it does clearify where you should be.  --update --upgrade is default, but that's pedantic. You really need to do --update twice?  Wow...  As a workaround for flash,  you can enable the partner repo and install adobe-flashplugin.  Looks pretty good!
[02:02] <Unit193> skellat: For some of my data, I've just been going off the manpage http://man.cx/apt-offline so it's not first hand.  Thanks for taking an interest in getting this in.
[02:11] <skellat> Unit193: Doing --update twice is just a safety measure
[02:11] <skellat> You don't *have* to do it
[02:11] <skellat> It is the **safe** thing to do
[02:12] <Unit193> That works for me.
[02:13] <skellat> The one thing I don't mention in the direction is that there may be significant time that passes before you get to a connected computer
[02:15] <skellat> Considering how Time Warner Cable has been swinging from .3 Mbps down to 1.8 Mbps down even though we're paying for 2 Mbps down as of late...the directions aren't mere abstractions to me but things I have to keep in mind
[02:15] <skellat> Pardon me, that should be "oscillating" between .3 Mbps down *or less* and 1.8 Mbps down
[02:23] <skellat> Unit193: That man page is very old as it has a caveat even the man page in *Precise* doesn't have
=== yofel_ is now known as yofel
[14:03] <lderan> time to see what bugs I can fix 
[17:18] <lderan> well hopefully i can find a bug which i can help with lol
[17:58] <GridCube> lderan, why dont you check http://status.ubuntu.com/ubuntu-raring/group/topic-raring-flavor-xubuntu.html and see if there's anything there you can do :)
[18:00] <lderan> will do GridCube 
[18:00] <GridCube> :D
[19:14] <lderan> well i can look into making the meetingology bot output wiki friendly, also have no issues with helping with documentation until i am upto speed with x/ubuntu bug fixing
[19:18] <pleia2> I think ochosi can chime in here too, but I believe bug fixing upstream in debian (the xfce packages) is pretty important too
[19:19] <skellat> The sooner Wheezy gets done, the better
[19:19] <pleia2> err, not ochosi, mr_pouit!
[19:19] <pleia2> skellat: for sure
[19:20] <skellat> The 100 bug wall finally got cracked so the Debian folks need help making it across the finish line
[19:20] <pleia2> I'm on this list http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-xfce-devel
[19:20] <pleia2> yeah, 93 was it? woo
[19:20] <lderan> will see what i can do to help, probably not much lol
[19:21] <pleia2> heh, I'm a sysadmin by trade - programming is not my forte :) so you can certainly help more than I!
[19:22] <pleia2> I'm mostly on that list to keep an eye on bugs that I know will pop up and bother people (and me)
[19:25] <lderan> fair enough
[19:45] <skellat> pleia2: I think this is ready for you to take a look at: https://code.launchpad.net/~skellat/xubuntu-docs/xubuntu-docs/+merge/154236
[19:45] <pleia2> skellat: running out to door now, but I'll take a look later
[19:46] <pleia2> thanks for working on this <3
[19:46] <skellat> Not a problem
[20:28] <knome> lderan, if you want to look at the meetingology output, AlanBell can help you with the meetingology side, and i can help you with the side what kind of output we want
[20:29] <lderan> sounds good to me
[20:30] <knome> lderan, for that, you want to join #meetingology :)
[20:31] <lderan> :P
[20:41] <knome> looks like the IS "fixed" ubuntu wiki tables
[21:54] <Cheri703> I know it's too late for 13.04, but I noticed something today that seems like it should be in place for 13.10 (or whatever the next one is)
[21:54] <Cheri703> the login screen doesn't have access to on-screen keyboard from the accessibility menu
[22:13] <Noskcaj> Cheri703, yeah, the login screen needs improvement
[22:14] <knome> the thing is, accessibility isn't working well anyway
[22:34] <Cheri703> It'd be great to have it for people who are unable to use a normal keyboard, but I just needed it because my bluetooth one wasn't being recognized. If I didn't have a backup USB one floating around, I would have been locked out of my computer due to lack of a shortcut to onboard. which isn't great.
[22:46] <knome> as i said, accessibility in general isn't working well. if it all worked as expected, we'd probably put more effort in getting the login screen to work
[22:46] <knome> it doesn't help much to be able to log in to an unaccessible desktop
[22:46] <Cheri703> it does if the reason you need it isn't accessibility per se
[22:47] <Cheri703> once I was in, I could troubleshoot why my bluetooth wasn't connecting. but without being able to log in, I had no way to do that
[22:47] <Cheri703> I'd think it couldn't hurt to add one shortcut to the login screen, regardless of anything else being "fixed". but I'm not a dev, so who knows
[22:47] <knome> the reality is that we either fix the login screen so you can login when your bluetooth kb isn't working or do 10, 20 or 30 other things
[22:48] <Cheri703> yeah, I totally have no idea how much of an ordeal it is to fix that, or if that ONE fix will apparently keep work from happening on up to 30 other things, but it was just something I figured I'd point out as a lacking feature that at least vanilla ubuntu has.
[22:49] <knome> i reality i don't know the real workload either, but that's definitely not our main focus
[22:49] <knome> vanilla ubuntu has lots of features we don't
[22:49] <Cheri703> well yes, but it's pretty standard across operating systems to have a keyboardless option for logging in. it's pretty basic
[22:49] <knome> some of them are design decisions, some of them are limitations by xfce/other things we use and some of them are limitations from developer time/motivation
[22:50] <Cheri703> *it's a pretty basic expectation that it'd be there
[22:59] <knome> maybe