[01:20] <CIA-24> partman-base: cjwatson * r83 ubuntu/ (debian/changelog partman):
[01:20] <CIA-24> partman-base: * Backport from trunk:
[01:20] <CIA-24> partman-base:  - Don't emit confusing log messages if partman-lvm or partman-crypto are
[01:20] <CIA-24> partman-base:  already loaded.
[01:22] <CIA-24> partman-base: cjwatson * r84 ubuntu/ (commit.d/parted debian/changelog lib/base.sh):
[01:22] <CIA-24> partman-base: - Allow disable_swap to take a device argument, in which case it only
[01:22] <CIA-24> partman-base:  disables swap on that device rather than on all devices.
[01:22] <CIA-24> partman-base: - Only disable swap on devices that are being changed (LP: #199048).
[01:28] <CIA-24> partman-partitioning: cjwatson * r670 ubuntu/ (debian/changelog lib/disk-label.sh lib/resize.sh):
[01:28] <CIA-24> partman-partitioning: * Backport from trunk:
[01:28] <CIA-24> partman-partitioning:  - Only disable swap on devices that are being changed (LP: #199048).
[01:28] <CIA-24> partman-partitioning:  Requires partman-base (>= 114ubuntu4).
[09:05] <gan_> when i install the ubiquity in my system , the error follows WARNING: Undefined kernel key code for 214
[09:38] <gan_> cjwatson, i am getting when i install from live cd to my harddisk
[09:40] <cjwatson> that is not a fatal error
[09:40] <cjwatson> you can just ignore that
[10:00] <gan_> cjwatson, i ignored then also the error is coming
[10:00] <cjwatson> I can't understand that sentence, I'm afraid
[10:00] <gan_> cjwatson, i am not able to fix the root partitioon
[10:00] <cjwatson> we need a bug report with full logs
[10:01] <gan_> cjwatson, it is giving the error like ????
[10:01] <cjwatson> http://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs; we need /var/log/syslog and /var/log/partman
[10:02] <gan_> cjwatson, ok i will send
[10:02] <cjwatson> (if you've already installed the system and rebooted, those files will be /var/log/installer/syslog and /var/log/installer/partman instead)
[10:03] <gan_> cjwatson, see the link http://pastebin.com/m7bcb2875 syslog file
[10:04] <cjwatson> please file a bug report
[10:04] <cjwatson> I can't look at it right now
[10:04] <cjwatson> that looks just hosed though. Check your CD integrity and that your CD drive is clean
[10:04] <cjwatson> "#
[10:04] <cjwatson> Mar 20 15:06:03 boss ubiquity: /lib/partman/definitions.sh: line 355: /var/lib/partman/outfifo: No such file or directory"
[10:04] <cjwatson> err, not that one
[10:04] <cjwatson> "Mar 20 15:06:10 boss ubiquity: /lib/partman/definitions.sh: line 155: /lib/partman/choose_partition/ : No such file or directory"
[10:05] <cjwatson> don't see how that could happen with a correct CD
[10:06] <gan_> ok , then what to do
[10:06] <cjwatson> also, you appear to be using some derived distribution, not Ubuntu proper
[10:06] <cjwatson> please ask them for help
[10:06] <cjwatson> I don't know what strange things they might have done to their live CD
[10:07] <gan_> cjwatson, actually this ubuntu cd , but i customised
[10:08] <gan_> cjwatson, actually this is ubuntu cd , but i customised with doc how to create a live cd
[10:08] <cjwatson> it would have been polite to say that up-front ;-)
[10:09] <cjwatson> I don't really see how you could get the error above from a line of code that reads (in the standard version) "$dir/${RET%__________*}/do_option ${RET#*__________} "$@" || return $?"
[10:09] <cjwatson> unless $RET contains a space, which it shouldn't there
[10:09] <cjwatson> you'll need to run the installer with 'ubiquity --debug' to get useful debugging on why it's gone mad
[10:10] <gan_> cjwatson, shall i run & send you the output
[10:11] <cjwatson> sure, I guess
[10:11] <cjwatson> if you have any installer customisations, now is the time to reveal them
[10:15] <gan_> cjwatson, yeah i ran but i didnt get any error msg on the console , but still i am not able to fix the root file system
[10:16] <cjwatson> the debug output will be in /var/log/installer/debug
[10:16] <cjwatson> I'm going to be on the phone for the next hour or so
[10:21] <CIA-24> casper: cjwatson * r483 casper/ (2 files in 2 dirs):
[10:21] <CIA-24> casper: * Stop quoting Exec arguments in .desktop files. Apparently this used to
[10:21] <CIA-24> casper:  work but now the system conforms more strictly to the desktop entry
[10:21] <CIA-24> casper:  specification (LP: #204185).
[10:23] <cjwatson> gan_: please don't attempt to DCC send it to me
[10:23] <cjwatson> it won't work, and your DCC request appears to be broken anyway according to my client
[10:24] <gan_> cjwatson, now the patebin is also not working what to do, how to send
[10:24] <cjwatson> I'm pretty sure that "0.0.0.199 port 0" is not a valid source
[10:24] <cjwatson> paste.ubuntu.com
[10:24] <gan_> k
[10:28] <gan_> cjwatson, http://paste.ubuntu.com/5919/ see this debug link
[10:38] <gan_> cjwatson, are you there
[11:58] <cjwatson> I told you I was going to be on the phone
[11:58] <cjwatson> and I was :-)
[12:03] <gan_> ok
[12:03] <gan_> cjwatson, no problem
[12:06] <cjwatson> gan_: ok, so partman threw an exception somewhere, after which ubiquity got very confused. Could you put /var/log/partman on paste.ubuntu.com as well? It should indicate why
[12:06] <cjwatson> seems to be while you were creating a new partition
[12:06] <gan_> ok just a min
[12:07] <cjwatson> now, it's also a bug that ubiquity got confused ...
[12:13] <gan_> cjwatson, see this link http://paste.ubuntu.com/5923/ /var/log/partman
[12:21] <cjwatson> looking
[12:22] <gan_> ok
[12:28] <cjwatson> ok, the reason you're encountering this is that you're using bash as your default /bin/sh
[12:29] <cjwatson> Ubuntu's default is dash, and it appears that dash and bash behave slightly differently on particular shell code in the middle of the installer
[12:29] <cjwatson> I produced a test case to confirm this
[12:31] <gan_> so what i have to do
[12:31] <cjwatson> this appears to be a customisation you've applied yourself
[12:31] <gan_> can i change my bash to dash
[12:31] <cjwatson> so you ought to be able to undo it
[12:31] <gan_> cjwatson, yeah
[12:32] <cjwatson> technically, I think it is a bug in partman-partitioning
[12:32] <gan_> cjwatson, then whats the solution for this
[12:33] <cjwatson> changing the default shell to dash is the safest approach; I can't guarantee that there aren't other areas of the partitioner that depend on the same difference
[12:33] <gan_> how to do it
[12:33] <cjwatson> you must have done it in the first place
[12:34] <cjwatson> assuming you started from an Ubuntu 6.10 live CD or later
[12:34] <cjwatson> you could also apply a patch something like http://paste.ubuntu.com/5925/ to /lib/partman/free_space/50new/do_option
[12:35] <cjwatson> (might not apply directly with the patch command, but it's just a matter of switching the order of two lines
[12:35] <cjwatson> )
[12:36] <gan_> which two lines
[12:36] <cjwatson> read the patch
[12:37] <gan_> it means you are asking me to do manually.
[12:38] <gan_> cjwatson, better i change my bash to dash
[12:38] <cjwatson> sure, that should work
[12:38] <cjwatson> I assumed you had changed it for a reason
[12:38] <cjwatson> what was that reason?
[12:39] <cjwatson> I'll fix the code so that this shouldn't happen in 8.04, at least in that particular case
[12:39] <gan_> cjwatson, why cant you do it for bash
[12:40] <gan_> cjwatson, i always work with bash that is the reason
[12:40] <cjwatson> the patch I gave you should fix it
[12:40] <cjwatson> for bash
[12:41] <cjwatson> if you write shell scripts that make use of special bash facilities, you should put '#! /bin/bash' at the top of them, not '#! /bin/sh'. That way, it doesn't matter what the system default shell is.
[12:41] <cjwatson> Interactive shells are bash anyway, regardless of what /bin/sh points to.
[12:42] <cjwatson> the reason for the difference here is that if you say 'local VARIABLE' in dash (for some value of VARIABLE) and VARIABLE already has a value, then dash uses that as the initial value of the local variable; while bash always initialises VARIABLE to the empty string
[12:43] <gan_> cjwatson, i have to paste this patch under /var/log/partman am i correct
[12:43] <cjwatson> local isn't standardised, so differences are to be expected
[12:43] <cjwatson> uh, no, that's completely wrong
[12:43] <cjwatson> you need to edit the file /lib/partman/free_space/50new/do_option, as I told you
[12:43] <gan_> kk
[12:43] <cjwatson> read the patch - lines beginning with "-" are to be removed, lines beginning with "+" are to be added
[12:44] <gan_> k
[12:45] <gan_> i like to be in bash only, i am getting confuse with dash
[12:47] <gan_> cjwatson, ok thanks i do the thing & i will reply you surely , now i have to go out
[12:47] <cjwatson> but you're confusing the system
[12:48] <cjwatson> you can perfectly well use bash for your own scripts, just by putting /bin/bash at the top
[12:48] <gan_> cjwatson, yeah
[12:48] <cjwatson> the system default doesn't change that at all
[12:48] <gan_> k
[12:48] <cjwatson> this was a fun little installer bug, though, so thanks for reporting it!
[12:48] <gan_> how the dash starts
[12:50] <gan_> ok thanks for your patience
[12:50] <cjwatson> "how the dash starts" -> I don't understand the question
[12:51] <gan_> bash starts /bin/sh like that for dash
[12:52] <cjwatson> I still don't understand. Are you talking about the first line of scripts?
[12:52] <gan_> yeah
[12:53] <cjwatson> If you use bash-specific features, say /bin/bash. If you use dash-specific features (this is very rare - this installer bug is one of the very few cases I've encountered), say /bin/dash. If your script is written to the POSIX shell standard and will work with either, say /bin/sh.
[12:54] <gan_> ok
[15:43] <CIA-24> ubiquity: evand * r2578 ubiquity/ (debian/changelog ubiquity/frontend/gtk_ui.py): * Remove dead code for the old resize widget.
[15:44] <CIA-24> ubiquity: evand * r2579 ubiquity/ (debian/changelog ubiquity/frontend/noninteractive.py): * Fix printing of non-latin text in the noninteractive frontend.
[17:22] <bdmurray> evand: you asked about bug 204133.  do you want to work on debugging it?
[17:22] <ubotu> Launchpad bug 204133 in wubi "wubi install unusable - Buffer I/O error on device loop0" [Undecided,New] https://launchpad.net/bugs/204133
[17:27] <evand> bdmurray: do you still have the image?
[17:27] <bdmurray> evand: yes, I do
[17:29] <evand> can you try running a chkdsk C: /f /r ?
[17:29] <evand> on the host Windows install
[17:29] <evand> then try booting Ubuntu again and see if that fixes it
[17:30] <bdmurray> Do you just use chkdsk in a command prompt or does it require booting into something special?
[17:31] <evand> just in a command prompt
[17:31] <evand> it will say that it cannot run chkdsk at this time because the disk is mounted
[17:31] <evand> and ask you if you want to do it on next boot
[17:31] <evand> say yes, then reboot Windows
[17:31] <bdmurray> okay, I'm on it
[17:31] <evand> thanks, much appreciated
[17:35] <bdmurray> evand: my windows vista foo is really bad.  How do I get in an "elevated mode"?
[17:37] <evand> right click on the application and select run as administrator
[17:38] <evand> you can drag a shortcut on the desktop and right click on that if you don't want to dig for the actual program location
[17:38] <evand> UAC is a mess.
[17:39] <bdmurray> makes me love Ubuntu even more. ;)
[17:40] <evand> hahaha, indeed
[18:02] <bdmurray> evand: still seeing the same "Buffer I/O error on device loop0"
[18:04] <evand> argh, hrm.
[18:05] <evand> I don't suppose you have a serial port and cable from which you can get a full log of whats happeneing?
[18:06] <bdmurray> my laptop has no serial port but I have a usb to serial adapter if that is any help
[18:07] <mario_limonciell> bdmurray, you have a null modem cable to go with that?
[18:07] <mario_limonciell> you should be able to dump to it then
[18:08] <bdmurray> mario_limonciell: somewhere I'm sure
[18:08] <mario_limonciell> on your kernel command line, you can add it as a console output, or you can just redirect the app causing that
[18:08] <evand> if you find it and could set that up and attach a full log to the bug whenever you have some free time, I'd appreciate it
[18:10] <bdmurray> evand: how much of a priority do you think it is?
[18:11] <evand> bdmurray: not too high, I believe.  I haven't seen this bug anywhere else yet.
[18:11] <bdmurray> I'm so special
[18:11] <evand> I asked Agostino if he has, but he's away for the weekend
[18:11] <evand> haha
[18:12] <mario_limonciell> how widespread has testing been going on wubi aside from evand bdmurray and TheMuso?
[18:12] <evand> the Wubi forum on ubuntuforums.org
[18:12] <mario_limonciell> so a fairly sizable number of folks then?
[18:12] <evand> I've seen a handful of people there test it, but those are only the ones who replied
[18:13] <mario_limonciell> ah
[18:17] <bdmurray> okay, I think I've found the cable is there some documentation you point me at for doing this?
[18:18] <mario_limonciell> well so where are those errors coming from, kernel log?
[18:18] <mario_limonciell> syslog or similar?
[18:19] <mario_limonciell> if that's the case, something like this is what you want: http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/configure-kernel.html
[18:19] <bdmurray> kernel, I can boot into single user mode but see those messages
[18:20] <mario_limonciell> depending on how early they pop up you should be able to use that as listed above.  if they are really early (like before usb is loaded ;)), you'll miss them
[18:21] <bdmurray> okay, and what is the best app on the non-broken system to use to catch the messages?
[18:22] <mario_limonciell> i use cutecom/minicom
[18:22] <mario_limonciell> cutecom is for X
[18:22] <mario_limonciell> minicom for a terminal
[18:22] <mario_limonciell> cutecom is a lot easier to configure imo
[18:22] <bdmurray> I've used minicom before just wanted to be sure
[18:23] <bdmurray> thanks!
[18:23] <mario_limonciell> np, best of luck :)
[19:11] <xivulon> evand ping
[19:11] <evand> xivulon: pong
[19:12] <xivulon> so this loop0 thing, I haven't seen that
[19:12] <xivulon> there was something similar when vfat was used
[19:12] <xivulon> since the fs was ro to begin with
[19:13] <xivulon> not sure if that's the case
[19:14] <evand> bdmurray is using Vista, so it's definitely not vfat, but he's working on getting a full log using a serial port.
[19:15] <mario_limonciell> or at least trying to :)
[19:15] <xivulon> is that reproducible?
[19:16] <xivulon> I see bdmurray is here too, hi
[19:17] <bdmurray> getting the full log is proving challenging
[19:17] <xivulon> might it be that 204133 is related to 20080320?
[19:17] <bdmurray> That was a typo on my part it really was 20080319 - I'll update the bug
[19:17] <bdmurray> I did get some pictures of call traces
[19:17] <xivulon> 204128 <-> 204133 that is
[19:18] <xivulon> bdmurray, did you try reinstalling?
[19:18] <bdmurray> No, I was thinking about that next
[19:19] <bdmurray> Do I need to remove the existing install first?
[19:20] <evand> it will force you to, though I'd suggest moving it out of the way in case reinstalling makes the bug disappear.
[19:20] <xivulon> You could move root.disk to a different dir
[19:20] <xivulon> so we could get that back in case the new one works well
[19:21] <mario_limonciell> evand, did you get a chance  to look over that other noninteractive thing I ran into yesterday?
[19:22] <bdmurray> xivulon: where will I find root.disk?
[19:23] <bdmurray> found it
[19:24] <evand> mario_limonciell: I've been looking at it as I work on other things today.  I fixed the immediate problem, but uncovered others when I did, so I'm working on those now.
[19:26] <mario_limonciell> ah i see
[19:30] <xivulon_> back, battery power meter wasn't too reliable...
[19:31] <evand> heh
[19:32] <xivulon_> so bdmurray, if you backup your previous file, I'd suggest to try a reinstallation
[19:32] <xivulon_> at the first reboot, press esc, and select verbose mode, that runs ubiquity with debug flag
[19:34] <xivulon_> evand the other bug you mentioned was about reconnection, was that running off a physical CD
[19:35] <evand> xivulon_: the bug where Wubi cannot install without being connected to the Internet?
[19:36] <xivulon_> I there is a log..
[19:36]  * xivulon_ reading log
[19:36] <evand> Yes, that was running off of the Beta candidate.
[19:38] <xivulon_> apparently the issue is that the md5 check of squashfs failed
[19:38] <xivulon_> md5=b5b8b1f15d1f45797c1f57ba8d0f30d6
[19:38] <evand> indeed, I caught that while pasting the log
[19:38] <xivulon_> if that failed then it is normal that a connection is required
[19:38] <evand> though I believe this was with two different images
[19:38] <evand> I'll verify the CD image and try again though
[19:39] <xivulon_> that should be the md5 of squashfs file only
[19:40] <xivulon_> when using a physical CD and without internet connection the md5 for the individual file is used
[19:41] <xivulon_> taken from md5sum.txt
[19:46]  * xivulon at dinner
[20:05] <evand> xivulon: I checked the md5sum of the squashfs in Ubuntu and it matches the line in md5sum.txt
[20:07] <bdmurray> xivulon: I've updated bug 204128
[20:07] <ubotu> Launchpad bug 204128 in wubi "After install completed bar wasn't all green" [Undecided,New] https://launchpad.net/bugs/204128
[20:09] <evand> heh, at least we know the CD-ROM drive is ejecting for sure now.
[20:09] <bdmurray> evand: my "Ubuntu Setup" window in not responding in Vista.  any ideas?
[20:10] <evand> hrm
[20:11] <evand> attach %TEMP%\Wubi-8.04-alpha-rev449.log to that bug report?
[20:11] <evand> s/?/.
[20:12] <evand> xivulon: have you had reports of successful Vista installs?
[20:18] <evand> outside of VMWare that is, as I tested that successfully.
[20:19] <bdmurray> hmph, I had some information about it not responding and then the window disappeared on me
[20:19] <evand> hrm, though that reminds me that TheMuso had issues with Vista as well, though they disappeared.
[20:19] <evand> odd
[20:23] <bdmurray> I just saw "checking the installation" go past 100% for whatever that is worth
[20:26] <evand> yeah :/, that's my fault
[20:27] <evand> I still need to fix it, it's a long standing bug when using --automatic
[20:28] <bdmurray> okay, at least its known ;)
[20:28] <evand> heh, indeed
[20:29] <bdmurray> I added some pictures to bug 204133 from the first disk image
[20:29] <ubotu> Launchpad bug 204133 in wubi "wubi install unusable - Buffer I/O error on device loop0" [Undecided,New] https://launchpad.net/bugs/204133
[20:36] <evand> iz kernel bug :)
[20:37] <evand> doesn't appear to be the same issue I ran into with VMWare and 64-bit, but we had already assumed that.
[20:37] <evand> hrm, still no luck with the serial console?
[20:41] <bdmurray> not yet
[20:41] <bdmurray> I'm at the same place after a reinstall too
[22:06] <bootlaces> Hey All...has luks/cryptsetup made it's way into ubiquity for HH? Can't see it mentioned in launchpad or ubiquity..
[22:06] <xivulon> evand, just run a successful installation on vista
[22:07] <xivulon> using wubi 449 and ISO 20080318.1
[22:07] <xivulon> amd64
[22:08] <xivulon> bdmurray, re progressbar, I can confirm it finishes when the bar is not 100%, but that does not have any implication
[22:08] <bdmurray> xivulon: I've put up some pictures of the crash at http://people.ubuntu.com/~brian/tmp/
[22:08] <xivulon> the bar progress is calculated by nsis, their algorithm is likely wrong
[22:09] <bdmurray> the ones starting off 20080320-*
[22:10] <xivulon> bdmurray, did  you experienced crashes only with today's ISO?
[22:10] <xivulon> It would take me ages to download that...
[22:10] <bdmurray> I was using 20080319 and that is the only one I've tried wubi on
[22:15] <xivulon> you used amd64 correct?
[22:17] <xivulon> well I started downloading the 19 ISO.
[22:25] <cjwatson> evand: possible hint for you in bug 197887
[22:25] <ubotu> Launchpad bug 197887 in ubiquity "Accessibility non-functional in only-ubiquity mode." [High,Confirmed] https://launchpad.net/bugs/197887
[22:26] <xivulon> bdmurray, I suspect that the nsis algorithm estimates the progress by counting the number of "calls" within the installation function at compile time, but it does not take into account parts of code that are not executed at runtime because of logical conditions.
[22:27] <xivulon> will test that assumption in coming days, I do not think it is very important unless the actual installation is affected
[22:28] <xivulon> which does not seem to be the case
[22:28] <Daviey> mario_limonciell: amd64 alt seems fine
[22:28] <bdmurray> xivulon: yes, I used amd64
[22:31] <evand> ah, thanks cjwatson
[22:31] <evand> xivulon: ack'ed
[22:31] <evand> I'll toy with that tonight
[22:33] <mario_limonciell> Daviey, let slangasek know
[22:33] <mario_limonciell> oh you did
[22:33] <mario_limonciell> okay good :)
[22:34] <xivulon> bdmurray did you try booting with init=/bin/sh
[22:36] <bdmurray> xivulon: no, I did not
[22:36] <xivulon> might be worth a go
[22:37] <xivulon> you could then try the rcS scripts manually
[22:37] <xivulon> first maybe check that the fs is r/w
[22:47] <evand> bootlaces: No, it was a low priority specification for Hardy that was deferred.
[22:47] <bootlaces> evand, thanks for the update
[22:47] <bootlaces> looks like I'll be using the alternative installer :)
[22:48] <xivulon> evand, I'd need to reboot to test the reconnecting issue, but I'd have to interrupt the download then, that would be a post beta fix anyway correct?
[22:49] <evand> yes, the beta is going to be released today, only a very serious issue would postpone it.
[22:49] <evand> Well, today EST.
[22:52] <xivulon> I'd thought so
[22:54] <xivulon> I can push a new rev with an extra debugging line, if you send me the log that should be enough for me
[22:56] <evand> ok
[22:56] <evand> dinner, back in a bit
[22:57] <xivulon> rev 456
[23:58] <xivulon> evand, I can confirm #203998
[23:58] <xivulon> no need to send me the log
[23:58] <xivulon> I will fix that in the coming days, you might want to add a caveat
[23:59] <xivulon> I'll do that...