[01:59] <StevenK> persia: Hm. Not sure where to add it.
[02:14] <persia> StevenK.  I'm thinkining "Home" is the right place, just for prominnence.
[02:18] <StevenK> persia: Which gives us 13 icons for a live system, and 12 for an installed system
[02:19] <persia> StevenK: OK.  You've convinced me.  Preferences.
[02:19] <StevenK> persia: Preferences doesn't sound like the right place, either ..
[02:19] <StevenK> persia: But, it sounds like the best solution currently
[02:19] <persia> Those are the only two places over which we currently have hardcodig control.
[02:20] <StevenK> Exactly why I said "best solution currently"
[02:20] <persia> Well, I suppose we could change merge.menu, and have a special "Install" for Install.
[02:20] <StevenK> We could. Less work to add ubiquity.desktop or something to Preferences
[02:21] <persia> Yeah.  Did you have any plans to do anything with settings.menu, or just point vaguely at preferences.menu and wave your hands until Jaunty?
[02:22] <StevenK> The latter, really, given how late we are
[02:22] <persia> Sounds good to me.  I just wanted to check :)
[02:24] <StevenK> It's ubiquity.desktop?
[02:25] <persia> Yep.  /usr/share/applications/ubiquity.desktop.
[02:25] <persia> There's also a /home/ubuntu/Desktop/ubiquity.desktop, but I think we can ignore that one.
[02:25] <StevenK> Will <Include> cry if the .desktop doesn't exist?
[02:26] <persia> Hrm.  No idea.
[02:26]  * persia checks
[02:29] <persia> When I add <Filename>santa.desktop</Filename> to the Include set in the applications.menu in -mobile, running xdg.Menu.parse() doesn't complain.
[02:30] <persia> I also remember that when I installed kourou on -desktop, it only had three items in Home, but worked.
[02:30] <persia> Conclusion: it's safe to <Include> stuff that isn't there.
[02:34] <persia> StevenK: Next question: for setting --automatic: I was thinking that adding a sed call to scripts/casper-bottom/10adduser within an if clause would be the best way to tweak the ubiquity.desktop file.  Would that make sense to you, or do you think it belongs somewhere else?
[02:38] <StevenK> persia: To do what?
[02:41] <persia> To change "ubiquity --desktop %k gtk_ui" into "ubiquity --automatic --desktop %k gtk_ui"
[02:42] <persia> Also, it appears I misled you earlier.  It's "/usr/share/applications/ubiquity-gtkui.desktop".  Sorry about that.
[02:42] <StevenK> I was going to throw a diff first
[02:43] <StevenK> Hm. That strikes me as non-elegant
[02:44] <persia> I thought it might.  How would you recommend solving it?
[02:45] <StevenK> Nothing springs to mind, so I think it's it
[02:45] <persia> OK.  My other thoughts were things like a special ubiquity binary package or a ubuntu-mid-install-helper binary package, but lool pointed out that both of those needed NEW, and were ugly anyway.
[02:46] <persia> For Jaunty, I'd like someone to hit ubiquity with glade and make a UI that works at 640x480 or 800x480, but I failed in my attempts to do that in July.
[02:48] <persia> The *SUPER DIRTY QUICK HACK* way to do it is to have a special casper-rw overlay with a different file, but that strkes me as even more inelegant.
[02:49] <StevenK> Shiver
[02:50] <StevenK> persia: Just do the sed hackery :-P
[02:50] <StevenK> persia: --automatic works now?
[02:50] <persia> Yeah, I didn't think you'd like that.  It was one of those ideas that came to me right before I decided not to be in front of the computer for a few hours.
[02:51] <persia> Well, for some definitions of "work".  With ubiquity 0.10.1 or later, it does the install, but since there is currently no support for preseeding blank passwords, it doesn't achieve the effect I want.
[02:52] <StevenK> 1.10.1?
[02:52] <persia> Mind you, due to foolishness on my part, we need ubiquity 0.10.2 for grub to be installed with the result.
[02:53] <persia> Yeah, 1.10.1 includes the fixes for bug #182004
[02:53] <StevenK> \o/
[02:54] <persia> That was the blocker on using --automatic at all.  Of course, since that was broken, I didn't discover that user-setup doesn't support preseeding blank passwords until recently.  I'm expecting to find a solution to that today, and have it agressively tested tomorrow, but I don't consider it important for beta: we'll just have passwords.
[03:14] <StevenK> persia: Are you going to patch casper?
[03:15] <persia> StevenK: I've already done so, but there's no benefit unless I can patch user-setup, and make sure both work together, so it lives locally.
[03:17] <persia> Essentially, the only screen we want --automatic to hide can't be hidden until we can preseed blank passwords.
[03:17] <StevenK> persia: http://paste.ubuntu.com/52692/
[03:18] <persia> Those both look sane to me.  Does the icon appear for you in the Preferences menu if you use that?
[03:18] <StevenK> Like I tested it :-P
[03:18] <StevenK> Let me do that
[03:18]  * persia is currently testing beta candidates, but can boot -mid to check if needed.
[03:35] <StevenK> rsync, I thought you were supposed to be fast
[04:06] <seps1816> does anyone know if i can get this to work on a sidekid id?
[04:09] <persia> seps1816: From a brief look, I can't tell what chipset that uses.  I suspect it's not x86 compatible, which at least means porting stuff if you really want to get it installed.  If someone already has a HOWTO about getting linux on there, that's probably a good place to start.
[04:10] <persia> That said, it appears to have 240x160 resolution, which is below the lowest anyone has ever considered for Ubuntu MID.
[04:12] <seps1816> ya thats what i figured i'd like to try out ubuntu mobile but it seems all i can get my hands on are sidekicks
[04:13] <seps1816> do u have an suggestions on a phone that would work well 
[04:14] <persia> I only know of one "phone" on which it can be installed, and that has an optional accessory handset that is larger than some phones to use instead of using this "phone" as a phone.  You don't want to install Ubuntu MID on a phone (I've done this: really you *don't* want to).
[04:15] <persia> Ubuntu MID is designed for little handhelds.  Examples would be the Aigo MID or the Sharp D4.
[04:16] <seps1816> ya i hear ya 
[04:16] <persia> Ubuntu Mobile is designed for slightly larger systems, like the newer Eees, or the Samsung Q1U, or the Kohjinshas.
[04:16] <seps1816> probably better off messing around with android 
[04:16] <persia> Yeah, for that form factor.  Maybe someday there will be a flavour of Ubuntu for phones, but not today.
[04:17] <seps1816> ya that would be pretty sweet 
[04:19] <persia> Well, if you're really interested, and you can get ubuntu-minimal running on some phone that's worth calling a "phone" rather than a "small laptop with a voice network access device", you'd be 60% of the way there.  Until someone does that, it's very unlikely that any more work can be done.
[04:20] <persia> (An example of the sort of thing I consider a "small laptop with a voice network access device" would be the HTC Shift)
[04:22] <seps1816> ya its been something ive recently started to look into 
[04:23] <seps1816> with all the new cell phones coming out
[08:15]  * lool waves
[11:18] <rhp_> Today I installed 8.04.1 in an effort to be able to create modified images. However also here I get an error wihle building squashfs. Somehow it made gdm crash (I was suddenly confronted with the login screen), so I tried on a console instead.
[11:19] <rhp_> After running for a while I get the error "qlzma_in: ZLIB data error   FATAL_ERROR:get_fragment:1258: res -3".
[11:19] <rhp_> that's the end of it.
[11:20] <rhp_> I'm slowly beginning to get the feeling that the problem might lie in my computer overheating, or something similar...
[11:29] <rhp_> This seems to be confirmed by the fact that it happens at random times during the process.
[11:29] <rhp_> *sigh*
[11:32] <lool> rhp_: Not pretty
[11:32] <lool> rhp_: What's your goal?  create modified images?
[11:32] <lool> Of mobile?
[11:33] <lool> rhp_: There are scripts to edit squashfs images, is that what you were using?
[11:58] <ogra> it is dveloped on 8.10 though ... no idea if it will work with hardy
[11:59]  * ogra doesnt think anyone ever tested that
[15:01] <crevette> wow, bluez 4.x and related are a moving target
[15:02] <crevette> a new release every 2 days 
[19:12] <rhp_> lool: yes, that was my purpose.
[19:12] <rhp_> ogra: it seems to work just fine with hardy.
[19:13] <rhp_> The problem with gutsy is that squashfs-tools isn't recent enough. But it is in hardy.
[19:14] <rhp_> Now only if my system would stop overheating...
[19:26] <ogra> ah, great to hear
[19:26]  * ogra headdesks ... stupid typos
[19:27] <lool> headdesk?
[19:29] <ogra> yeah
[19:29] <ogra> i made a silly typo ...
[19:30] <ogra> now it takes another 2h to get the gconf change in
[19:31] <ogra> heddesking, like banging your head on your desk to beat out the stupidity :)
[19:31] <ogra> *head even
[20:02] <rhp_> A question: is it also possible to extract the right stuff from the image and boot that directly, instead through a union / squashfs? I'm now using pxeboot, but it is dragging everything over the network, which is a bit much..
[20:03] <rhp_> That would also solve the problems with building the new squashfs image.
[20:06] <rhp_> A question: is it also possible to extract the right stuff from the image and boot that directly, instead through a union / squashfs? I'm now using pxeboot, but it is dragging everything over the network, which is a bit much..
[20:06] <rhp_> That would also solve the problems with building the new squashfs image.
[21:23] <lool> StevenK, persia: hey
[21:23] <lool> StevenK, persia: The beta images are being rerolled due to some langpack issues and as a side effect will include the ubiquity fixes
[21:23] <lool> StevenK, persia: however this means heno and team are now lagging in terms of testing as they need to retest the iamges
[21:24] <lool> StevenK, persia: Could you please spend some time today testing the new ISO if you have some spare cycles?  Thanks!
[21:24] <lool> persia: Well you might not have time with your work
[21:44] <lool> persia: I've tested the xorg changes to allow startx from upstart, they work with </dev/console >/dev/console 2>&1 but NOT without; I don't recall what you changed in the rc boot sequence to fix startup of Xorg in kvm, could we discuss this as to allow us to drop openvt soon?
[21:52] <rhp_> Yeah! _Finally_ I got a working custom image, with fpit and the necessary changes included... and it works! (well... sorta)
[21:53] <rhp_> At least it recognises the touch screen device, but the scale is completely wrong.
[21:54] <rhp_> However... (why is there always one?) also the default xorg.conf does not include the fpit driver and when I modify xorg.conf, it complains about the powermanager being configured wrong.
[21:54] <rhp_> I can just do /etc/init.d/gdm restart, right?