[00:24] knome, yeah, that fookin' rocks [00:24] micahg, want to do the security thing, i'll be going upstairs in just a minute [00:25] ScottL: dinner, then errands, I won't be available really for another 2.5 hours, let me know if you need the links though [00:26] i played with the web browser one during my lunch (windows machine), i'll download the code in a bit [00:26] i hope it works of off packagsets of similar to make searching easier [00:27] i should still be availabe in 2.5 hours though [00:27] ScottL: it's mostly a data branch [00:28] ScottL: the 3 dirs that interest you are active (open CVEs), retired (fixed or ignored after time CVEs), scripts (pkg_status might be helpful) [00:53] A fix for Bug 955617 has been released so I will try installing tomorrow. [00:53] Launchpad bug 955617 in casper (Ubuntu) "ubiquity hangs (no activity forever) at configuring target system" [High,Fix released] https://launchpad.net/bugs/955617 [02:12] len-nb, did it hang for you again today? [02:46] scott-upstairs, Yes it hung today, but the fix was released after the iso build. [02:47] By about two hours if I read things right. [02:51] I guess it was about the time you left work so you missed it. [02:59] micahg, i'm ready whenever you are [03:09] falktx, are you still interested in working up the theme like we talked [03:09] ? [03:09] * scott-upstairs is about a week behind on sending out emails and working on his list now [03:10] scott-upstairs: I'm wondering what you still need from me :) [03:11] micahg, the security stuff, i'm a little confused about what i'm supposed to do with the 'active', et al directoreis [03:11] scott-upstairs: I was waiting for an email or something [03:11] scott-upstairs: it's hard to tell without knowing how much work is still required [03:11] falktx, just making sure, i'll forward two emails with an quick explanation in the first one [03:11] falktx, are you working with the open octave group? [03:12] scott-upstairs: please send those emails first, then I'll see if I can help there or not [03:12] scott-upstairs: a bit yes, but not too much lately [03:12] falktx, that is super cool! [03:12] I'm woking on the juce-lv2 wrapper right now [03:12] getting close to a release product [03:13] scott-upstairs: what I did for xubuntu was grep in retired for the xubuntu package names [03:13] then you can use ./scripts/pkg_status to check for open issues [03:13] that should give you the history of your packages [03:14] micahg, but i have to do this manually for each package that i am interested in? [03:17] scott-upstairs: no, I'd suggest dumping the packageset list in a file, then using something like 'cat MYFILE | xargs -I{} grep {} retired/* > US_security-history.txt' and something similar to get the pkg_status output [03:18] that's why I said it can be done in a night if the output isn't too bad with a little shell scripting :) [03:19] where can i get the packageset, i seem to remember someone gave me a link once but i don't remember where it is [03:20] scott-upstairs: http://people.canonical.com/~stgraber/package_sets/precise/ubuntustudio [03:20] thanks, added bookmark this time [03:21] scott-upstairs: this version might be a little better for shell scripting minus the initial output: http://paste.ubuntu.com/891684/ [03:22] i started to say, "i've never heard of the 'zhengpeng-hou' package before...what is this???" and then i realized it was a *person* LOL [03:25] hmmm, giving me 'argument list too long' [03:26] yay, got it to work (i think) [03:27] oops, didn't...trying again with some changes [03:28] scott-upstairs: you could diff against this one as well (xubuntu packageset): http://paste.ubuntu.com/891689/ [03:28] micahg, is there somewhere i can read some background about what i'm doing or a defined scope of what the expectations are? [03:29] scott-upstairs: not that I'm aware of, you're trying to ascertain the effort necessary to support the packages in your packageset not supported by anyone else for the duration of your LTS [03:29] in this case specifically, security support [03:33] oh, i did something horribly wrong, the US_security file i outputed was already 5.6 gigs and growing [03:33] but i need to go downstairs and hold my son, he's fussy and it's time for his bed [03:34] yeah, doesn't sound right :) [03:34] OH, maybe i didn't do something wrong, all the lines that i read seem to be related to packages in the set [03:35] here is a sample of what i got: http://paste.ubuntu.com/891699/ [03:36] okay going downstairs hopefully for only thirty minutes or so [03:36] (yes, i called my file 'MYFILE' :P it made it easier) [03:43] scott-upstairs: umm, is it really >5GB? [03:50] scott-upstairs: afaik, the icon theme is a no go [03:51] scott-upstairs: it needs proper docs explaining who made them, which ones are not in the original pack (oxygen), and which are custom made. [03:52] last time I checked Dick just picked icons from several places into a big icon theme [03:52] canonical will not approve this [03:55] I don't know enough about the theme or the wallpaper [07:43] ScottL: sorry, will have to upload stuff in the morning, need some sleep now [09:56] len_: scott-upstairs: ScottL: The ubiquity hang bug should now be fixed in casper version 1.312, so let's look at that on the next images tonight. [11:33] ScottL: I joined the lightdm-gtk-greeter team on LP, so if our project has devel suggestions, I would be happy to act as a proxy towards getting the implemented. I thought it was the most suitable way of getting into actual Ubuntu development for me. [11:37] :) [11:47] micahg, yeah, i'm sure it's a 6gb file: http://imagebin.org/204363 [11:49] i like that username >:) [11:54] which username? [11:54] mine? [11:54] yep, on the shot [11:54] /home/master [11:54] >:) [11:55] Wow, that's insane. scott-upstairs: I could assist you on the CVE tracking in a couple of hours, if you need any help. [11:55] Pretty interested about this topic. [11:56] i think i'm off for a while [11:56] see you :) [11:56] I'm going out for a few now, though. But if you can make a short summary on what has happened thus far, I'd appreciate it. [11:57] knome, oh, lol, well i screwed up and branched in my home directory, just happened to be a /master folder first in there [11:58] astraljava, how far away you want me to start? BCE? [11:58] scott-upstairs, ;) [11:58] astraljava, i'm not really making much progress so far but i can shoot you an email in a bit, right now i'm just making sure i retain the information micah has given me [11:58] * knome is really off now -> [12:00] by knome [12:00] er bye [12:01] astraljava, okay, sent you the same email i was sending myself to help document some of this, it's very loosely (at least chronologically) organized, but may not be very self-explanatory [12:01] knome: The big bang, obviously. And if you have any info on what preceded it, I'd be grateful. [12:01] okay, got to go and start getting kids up [12:02] scott-upstairs: Ok, thanks! See you later. [13:46] hi [14:01] Hi Antoine! [14:10] astraljava, some news about TheMuso and the lowlatency kernel ? [14:13] ttoine: Haven't heard/seen any updates, sadly. [14:14] Yeah, the latest commit is still that of March 9th [14:23] ttoine: I'm cloning the git branch now, and will give it a stab later tonight to try updating the config and roll my own. If it works, I'll upload my own branch somewhere for people to test. [14:24] It's not a lasting solution, though, as I'm afraid there'll be plenty of updates for the ubuntu kernel still. But it'll teach me some kernel hacking, at least. :) [15:07] astraljava, ok. [16:04] ailo: As you know about the lowlatency config, what are the changes to it? I see in Luke's branch there to be a lowlatency config file including turning preempt on, marking hz_1000=y and slab=y. Would those be enough, or are there other settings still? [16:05] If those are enough, then it's probably just a packaging issue, which I will look into next. [16:19] Hmmm... that's a bit confusing. In that Luke's branch, debian/debian.env already points to debian.lowlatency. [16:19] I'm afraid I need more guidance in debugging this. [16:29] ScottL: wow, that's huge, maybe the guys in #ubuntu-hardened would have an easier way to do this :( [16:44] micahg: I'll give it a go as well, just to see whether there was a glitch somewhere. [16:45] ok, will a little more fine tuned scripting, you could output a count of CVEs as opposed to a huge file of all the lines that match [16:47] micahg: I'm suspecting the multiple times of names in that packageset listing (what's with that anyway?) [16:50] ooh, right, I didn't check that, a simple | sort | uniq will fix that [16:51] micahg: Yeah, but when looking into package names, I need to get rid of uploaders anyway, so not a problem. [16:51] micahg: What I think has happened there, is that uploaders have creeped into the dumped file that is then used in getting the information. [16:52] astraljava: I gave a pastebin without that :) [16:52] micahg: Oh! Okay, sorry about that. :) [16:53] micahg: Well, I'll double-check, still, as I want to get a hang of the process anyway. [18:39] how is everyone doing today? we had some wicked storms come through and it knocked the power out at work for a while [18:50] scott-work: Quite ok, I suppose. I'm trying to find out how you managed to get the 6GB file, when I'm failing to get any output at all. [18:50] Chopping the process to pieces, trying to spot the error(s). There are several. [18:51] astraljava: i moved my 'MYFILE' into the \retired directory, then reran the bash command without the '\retired' part [18:51] mabye i already did that in the email, i'll check [18:52] scott-work: micahg: It should be ok to run the pkg_status script in an oneiric machine, right? [18:52] that should be 'retired/' and without the 'retired/' [18:52] that is, explicitly: [18:52] cat MYFILE | xargs -I{} grep {} retired/* > US_security-history.txt [18:52] changed to [18:52] scott-work: How did you come up with the MYFILE in the first place? [18:52] cat MYFILE | xargs -I{} grep {} * >US_secutiry-history.txt [18:53] but spell security properly :P [18:53] it was part of the email [18:53] and it was derived from something micahg sent to me, which was also part fo the email [18:53] Oh, so it was, sorry. :) [18:53] MYFILE is basically a text file that contains all the packages in our packageset [18:53] hehe, np :) [18:58] Yeah, so I worked a similar package-list file, but get nothing when I'm trying to use it. Apparently there is some configuration to be done before you can properly run the pkg_status script. [18:58] Btw. that command won't, obviously, do anything meaningful. [19:03] micahg: Do you have any idea why this happens? http://paste.ubuntu.com/892616/ [19:04] micahg: the pkgs file is a similar listing of packages that is created in pkg_status script when called with `-f' option. [19:09] astraljava: i never tried pkg_status [19:09] only the cat - xargs- grep line [19:13] ailo: Well, I managed to build the kernel packages, but so far I have no idea how to verify what config it uses. [19:14] scott-work: Yes, but there's nothing that processes the output of that file after it has been grepped. [19:14] astraljava: did it create a US_security-history.txt file? [19:15] scott-work: No. [19:15] $ cat ~/Documents/ubuntu/ubuntustudio/MYFILE-U | xargs -I{} grep {} retired/* > ~/Documents/ubuntu/ubuntustudio/US_security-history.txt [19:15] xargs: argument list too long [19:15] huh, this is PART of my output: http://paste.ubuntu.com/891699/ [19:15] I wouldn't imagine it doing so, anyhow. [19:16] astraljava: right! that is why i moved the MYFILE into the retired/ directory and then reran the command with 'retired/' in the command [19:16] scott-work: Can you double-check the command, please? [19:20] so, i moved MYFILE (which is the actual filename) into the /master/retired directory [19:20] then i ran... [19:20] wait...then i cd /master/retired [19:20] THEN i ran... [19:21] i ran so far away....i couldn't get away [19:21] sorry [19:21] cat MYFILE-U | xargs -i{} grep {} * > US_security-history.txt [19:21] (i had forgotten i renamed the file to MYFILE-U for ubuntu studio packages and MYFILE-X for xubuntu packages) [19:23] Uhh... alright, I was a little confused from the steps in the email. Let me try again, hold on. [19:27] * scott-work crosses fingers [19:27] we have a lot of package names in our package set [19:28] * scott-work wonders how large was the Xubuntu_security-history.txt file was micah generated [19:28] astraljava: you should use pkg_status, not ubuntu-table I think [19:29] and --supported won't help for US [19:30] Ok NOW we're talking. :) [19:30] Certainly not a 6GB file, mind you. :) [19:31] astraljava: it took about two minutes to get to that point [19:31] i actually stopped the bash command [19:31] micahg: I was just chopping the problem to pieces, but I didn't actually need to do that. I just misunderstood the instructions. [19:33] http://paste.ubuntu.com/892678/ [19:36] Erhm... wait, I still don't get it. Where does the pkg_status come into picture? [19:36] astraljava: oh, that'll tell you the current state of the packages (open CVEs) [19:36] It wants the packages as arguments. [19:36] micahg: Yeah. [19:36] So... what was it that you actually wanted?! [19:36] unless you grepped active and retired [19:37] astraljava: historical vulnerability and current security status [19:37] astraljava: you basically want to know how much work it'll be to support your packageset over the life of your LTS [19:38] keep in mind security support is one part, there's bug fix support as well [19:38] micahg: Ok. I have to spend a little time on that file, to get an understanding of how it should be interpreted. [19:38] you also want to know the current shape of your packages [19:39] micahg: Right. But that's why I chopped the pkg_status script problem into smaller parts, because it's failing to run on my system. [19:40] hmmm [19:41] micahg: On security support, should someone of us be a member of a team (or something similar) to be informed about the CVEs and other problems, or is it enough to rely on LP bugs? [19:42] nope, the Ubuntu security team will be notifying whoever the derivative contacts are of vulnerabilities, we're going to discuss how best to do this at UDS [19:45] micahg: Gah, you just made me want to apply for sponsoring for the next UDS with that. :D [19:49] astraljava: you pastebin looks very similar to mine, what was the final file size? [19:50] s/you/your [19:50] * micahg is guessing that's the whole thing [19:50] $ ll US_security-history.txt [19:50] -rw-rw-r-- 1 jaska jaska 122548 2012-03-20 21:30 US_security-history.txt [19:50] scott-work: So... 122K [19:50] astraljava: you could also exclude the xubuntu packageset if you like [19:51] micahg: I know, but I tend to want to participate in those as well, so I won't. :) [19:51] scott-work: Are you the security contact for US at the moment? [19:52] scott-work: ...and furthermore, if you are, then are you willing to share responsibilities? [19:52] astraljava: well, for this exercise, it's prudent as, those packages already have been accepted as ok for the LTS, the TB wants to know if you're willing to take on the added maintenance for the new packages that no one else is supporting, you can help with whatever you like [19:52] micahg: Ahh... I understand. [19:53] astraljava: There's three places for configs for lowlatency. The ones in use are in debian.lowlatency/config/i386/config.flavour.lowlatency and debian.lowlatency/config/amd64/config.flavour.lowlatency [19:53] Those need to be changed, and commited [19:54] The one in debian.lowlatency/config/config.flavour.lowlatency is correct but not used [19:54] astraljava: i'm not sure who the contact for US is at the moment, but if it was me i would defintely be willing to share [19:56] astraljava: So, just replace the ones in */i386/* and */amd64/* respectively with the one that is correct [19:56] astraljava: Are you building from git, or from apt source? [19:56] micahg: were you able to update the metas this morning? [19:57] micahg: I assume I have to go through this page before the pkg_status script will run properly: https://wiki.ubuntu.com/SecurityTeam/UbuntuCVETracker [19:57] * scott-work is wondering if the default-settings, et al will be reflected in today's image [19:57] scott-work: Right. Cause that might affect on my decision to file for sponsoring to attend the coming UDS. [19:58] ailo: I'm building Luke's git branch. [19:58] astraljava: After you've installed a kernel, you can check the config for it in /boot, for example do: cat /boot/config-3.2.0-18-lowlatency | grep PREEMPT [19:58] ailo: Ok, thanks! [19:59] ailo: Currently I'm concentrating on the CVE issue, but I'll get back to the kernel thingie after this. [20:01] astraljava: I'm still waiting for Luke to drop by. I've been playing around with the source. Replacing the config is no problem, but I would also like to understand how it is synced with the main ubuntu kernel. There's a short howto in the main dir under "MAINTENANCE", but there's more to it than that. [20:02] scott-work: sorry, still trying to finish something else, default settings needs to go in first or you won't get the live packages [20:02] Been busy today, so I have not had any time to look more into kernel maintenance [20:03] micahg: ack'd [20:04] it's not too big of a deal currently as colin still needs to finish the jack configuration bug as we can't install anyways at this point [20:05] micahg: Apparently I was missing some packages that were listed on that page I just linked to, now the script runs, but the output only has release names. I guess it's possible that no package has an open CVE at the moment, right? Or am I to believe the script still doesn't work? [20:05] astraljava: yes, I'm sure many are like taht [20:06] micahg: Alright, thanks! [20:06] astraljava: what would be useful is package name and count actually [20:07] also, per year would help as well [20:09] micahg: Okay, I'm going to write a python script to help me with this, so I can do it more automatically in the future. [20:39] uh, i wonder what i just got myself into for the slideshow UIFe #959504 [20:39] bug #959504 [20:39] Launchpad bug 959504 in ubiquity-slideshow-ubuntu (Ubuntu) "[UIFe] ubuntu studio slideshow requires update" [Undecided,New] https://launchpad.net/bugs/959504 [20:42] Err... what are 'screen shot requirements'? [20:55] micahg: How's this look? http://paste.ubuntu.com/892802/ [20:56] looks nice for the current status :) [20:56] micahg: That's actually the pkg_status script output. I'll get to the history file now. [20:56] Yeah. [20:56] keep in mind, libav-extra is usually uploaded with libav by the security team [20:56] that's not bad at all [21:02] http://paste.ubuntu.com/892817/ for the history, but I'll get to the grouping now. [21:03] I still don't really understand that file, so it will take a while. :) [21:04] Ahh... I do now. [21:05] But it might take a while to script a better-looking listing of that. [21:06] astraljava: very nice (looking at first paste) [21:07] by the way, what does 'DNE' mean? [21:09] README file explains all, means Does Not Exist [21:09] Does Not Exist? [21:09] Oh. [21:09] micahg: Actually, your requirement for the listing isn't something that's often needed, right? So there's no point in writing such a script, is there? [21:11] no, not really, although I'm going to bring it up at UDS about being able to look at the history of a package [21:12] micahg: Yeah, but just for this LTS application purpose, that's a one-time deal (at least for the next two years/LTS cycle). :) [21:27] micahg: Oh, now I realized what you meant. Ok, I can make such a script later. Will that need more info other than pkgname, year and count? Like the needed/released/not-affected information? [21:28] astraljava: not at the moment, we'll probably develop something more generic after UDS, so I wouldn't spend much time on it [21:31] (sheepishly) uh, i guess i need to look at the README file [21:32] micahg: ACK [21:32] oh, scottk approved the UIFe for the updated slideshow [21:37] \o/ [21:50] micahg: You've got mail. [21:50] astraljava: I always have mail :) [21:51] *smirk* Yeah, but it's such a legendary phrase. :) [21:51] oh yeah, colin had updated casper for the jack -rt debconf, which hopefully prevents the install from hanging...and those builds should have been built already [21:52] astraljava: audacity 11.10 backport building in ppa:micahg/ppa, should be ready in ~1hr, you could file the backport request if you like with requestbackport in precise (from ubuntu-dev-tools) [21:52] micahg: Don't I need to test it first? [21:53] astraljava: yes, you can file the request before you test it, just note that you'll be testing it, or wait until you test it, either way [21:53] micahg: Ok. [21:55] imagemagick is in main, I wonder why that's in your list [22:00] micahg: Ehrm... it should be gem. [22:01] heh :) [22:01] going home [22:01] have a nice way home :) [22:01] astraljava: yes, but I think those CVEs are for imagemagick :) [22:02] knome: eh, it's rainy and i've got to get the kids on the way, it will probably be 1.3 hours until i'm there [22:02] awwh [22:02] * knome wonders if 1.3 means 90 minutes, or something a bit short of 80 mins [22:02] micahg: That might be true, I did see an awful lot of imagemagick in the CVE descriptions, which is probably why I mistook the name for the package. [22:03] knome: It'd be a little less than 80 min., of course. *duh* [22:03] astraljava, if you took it literally. though it's easy to mistake half and hour to .3 [22:04] astraljava: overall, not too bad though, certainly seems manageable [22:04] micahg: Good to hear, thanks! [22:05] micahg: I'd certainly love to come and talk about that with you guys at UDS. [22:06] astraljava, we should start lobbing for UDS R Helsinki. [22:07] astraljava: there's always remote participation [22:07] micahg: True. knome: True. [22:08] Meh, the sponsoring is closed already. :-/ [22:08] long time ago. [22:09] not for UDS R Helsinki though. [22:09] knome: Less than a month. :) [22:09] feels like an eternity. [22:11] Oh well. It might have been too early anyway, if I actually do get a new job soon enough. [22:17] mmh. [22:25] ailo: I see, those files are auto-generated, and empty currently. [22:26] ailo: Spoke too soon, amd64 is empty, i386 is not. [22:28] astraljava: Yes, but I don't think auto-generation is the best choice for those configs. The autogeneration should be kept for -generic [22:29] As these configs are overriding the -generic on a few items, they don't need be update as long as those configs exist [22:30] updated* [22:31] For each new kernel version there might be a few new configs available, or some taken out. There's a script for updating the config for -generic, which I would let UTK deal with [22:34] To be even clearer, the config options for -lowlatency should probably be edited manually, and won't need to be edited as long as there's no change in those few particular config options. One would probably need to keep oneself updated on that however. [22:40] TheMuso: Hi, as I am in the Studio kernel team, I'd love to have some info re: how the lowlatency kernel is updated, and how I can best participate in the maintaining of it. Would you have some pointers to docs on best practices or something similar? [22:41] astraljava: Afaik there is nothing really documented as to how to maintain it. When I do the next rebase, which should hopefully be today, I'll write something up. I am a hopeless doc writer though. [22:42] TheMuso: That's fine, if you have something, I could try and expand it by asking questions and trying to write it down, then. :) [22:42] Thanks a bunch! [22:42] np [22:53] Today's ISO... ls /etc/security/limits.d/ [22:53] audio.conf [22:53] Something has worked :-) [22:56] Let me ask everyone. Who is going to be the main maintainer for the -lowlatency longterm? I have recently offered to do so, and have started putting a lot of effort into that. Some documentation on the subject would indeed be helpful, as well as a clear idea for how it should be done. I remember reading something about putting -lowlatency on github or something like that? [23:00] US slide show still too tall for netbook screens, can't follow install progress. [23:02] The ardour slide says "add Ardour" does that mean we don't ship it? That comment kinda makes it sound that way. [23:14] Install looks like it is going to complete... got to installing grub this time. [23:16] ailo: We have a team for that, now. Talk to Scott about being included in it, he's the owner and it's moderated. [23:16] ailo: I am also interested in creating some docs for helping the maintainers in that team. [23:17] knome: *poke* There's some comments re: slide-show ^^ [23:17] Len-live: Great news, thanks for reporting! [23:18] micahg: Thanks for uploading! :) [23:18] astraljava: what did I upload? [23:18] astraljava, awwh, summary please? :P [23:18] astraljava, install is still going, downloading extra software now [23:19] micahg: Hmmm... I thought theose progresses on images were the result of uploads of -meta. [23:19] The US slide show seems to need to be less tall by the size of the text bar across the top to fit netbook screens. [23:19] i missed the news, Len-live what happened? [23:19] Len-live, right. alt+drag [23:20] micahg: Oh, now I remember, the hanging was not related to -meta, nor any US packages in the first place. Sorry for the fuss. [23:20] astraljava: nope, new one should be in tomorrow if I ever finish what I'm working on :) [23:20] micahg: Gotcha. :) [23:20] * astraljava feels half asleep too [23:20] knome, not a problem for me, I watch less /var/log/syslog anyway. More for new users. [23:20] yeah, hanging was due to 1st casper needing changes to preseed at the right time, and 2nd hooks for the actual configuration [23:21] ScottL: Yeah, I did actually post about that bug earlier, but already forgot. :) [23:21] ScottL , live DVD now has ls /etc/security/limits.d/ [23:21] audio.conf [23:21] Len-live, i'm curious about the slideshow and how it is working [23:21] Len-live, that is out-F'ing-standing news!!! [23:21] Len-live, the xubuntu installer has a same sized slideshow, and we haven't really had reports it being all too tall :) [23:21] i'll go zsync my image and see how it looks [23:22] Slide show works but too tall for short screens... I think by the width of the text bar across the top. [23:22] Len-live, it probably is... but probably acceptable for most too :) [23:22] well after i get the kids food [23:22] The ubuntu slide show fits. [23:23] Len-live, yup. [23:24] ScottL, how willing are you to just let the images but off from the bottom? [23:24] The install takes a while, longer than ubuntu desktop for example. And there are times when the disk is not busy but things are working fine... with no progress bar it looks like the install has hung. [23:24] ScottL, content would work otherwise with 100px less tall windows [23:25] Len-live, even the progress bar might look like the installation is stuck, though... [23:26] It at least tells you I am downloading something... I would prefer a console... in fact I make one. [23:26] Anyway, install complete, going for reboot. [23:26] knome, i think i'd be okay with that, but i would like to look at the install we have before we do anything [23:27] Len-live, good luck :) [23:27] i wonder how the background/text looked? [23:27] it looks good. [23:27] i checked that when i updated the bg [23:27] everything is readable [23:27] i even checked the less tall window size minutes ago, and that seemed to work pretty well too [23:35] ISO install boots ok. I can't see anything really amiss. [23:36] default-settings still hasn't been updated, but I think I knew that. [23:36] knome, sorry, i mean the uqibuity installer background/text...we had a bug without the -live-settings package [23:36] len-1204, that is awesome (and quite relieving) news [23:37] ScottL, right. [23:37] ScottL, do you want me to try another install without going live first? [23:38] like from the boot menu. [23:43] len-1204, that is where the background/text issue manifested, i believe, but i'm going to test tonight too [23:43] OK, enjoy. [23:45] len-1204, you still on your netbook? [23:45] Yes [23:46] could you test something for me? (includes dlding a bzr branch and editing 1 file) [23:46] you would probably have to walk me through it. [23:46] i can [23:47] terminal? [23:47] do you have bzr installed? [23:47] Only if it comes with US, I have it on the other disk. [23:47] i don't think it does [23:47] nope. [23:48] sudo apt-get install bzr :) [23:48] Would it be more helpful if I reboot first? I have 11.10 xubuntu on the otgher disk. [23:48] xubuntu doesn't ship bzr by default either [23:48] it's a developer tool [23:49] I had it on there for playing with our defaulkt setting for menus. [23:50] but whatever works :) [23:50] But I am installing here now anyway [23:50] okay, after that: bzr branch lp:ubiquity-slideshow-ubuntu [23:51] that might take a while, even with faster internet, so poke me when that's done :) [23:51] 'k [23:52] * knome grabs something small to eat+drink along with some painkillers [23:59] knome: You can just say so, if we're too painful for you to endure... *blink* *blink*