/srv/irclogs.ubuntu.com/2008/04/23/#ubuntu-installer.txt

xivuloncjwatson, on #188492 my tests went well and gb layoutcode worked out of the box!00:24
TheMusoxivulon: Anything in particular you want me to target for this round of wubi testing for the ISOs, noting that atm I can only test i386.00:29
xivulonthanks the Muso, as mentioned on #ubuntu-testing:00:34
xivulon1) installation with physical CD (you can use an emulate CD) with and without internet connection00:34
xivulon2) installation with a local ISO in the same folder as wubi.exe and without CD (should not download the ISO, but you must use an ISO with lates daily md5)00:35
xivulon3) no ISO and no CD00:35
xivulon1, 2, 3 only on the windows side no need to reboot00:35
xivuloncheck that the uninstaller works00:35
xivulonthen reboot and go through the linux side installation00:36
xivuloncheck shutdown and suspend and try to install a different kernel00:36
TheMusoOk.00:36
xivulonthat would be great! thanks a bunch in advance00:37
TheMusonp00:39
bdmurrayxivulon: what rev of Wubi is supposed to be on the images now?00:46
xivulon495 (hopefully)00:47
bdmurraySo I've a 20080422.3 KDE4 disc and I ran Wubi and it said 487 and didn't end well but using 'strings umenu.exe' the first thing I find is 495.  Do you have md5sums for umenu.exe or some other way to verify the version?00:58
bdmurrayxivulon: the log is rev 487 too01:10
xivulonarg01:14
xivulonevand does the build: http://people.ubuntu.com/~evand/wubi/01:14
xivulonI guess we can compare with the md5 off the above url01:15
bdmurrayhtm01:16
bdmurraythe md5sum of 495 != the md5sum of wubi off the cd I have01:17
evanduh odd, I did a make clean before the build too.01:17
xivulonyes it 487!!!01:18
bdmurrayyeah, that's the match I get01:18
* xivulon off to ubuntu-release01:19
evandhow on earth did that happen?01:19
evandr495 was linked to stable as of 16:27 British time01:20
=== cr3_ is now known as cr3
xivulonbdmurray thanks a lot for the heads up!02:37
bdmurrayxivulon: no problem, I'm glad it got sorted and early at that02:37
TheMusoYeah its on the latest set of live images now.02:38
xivulonhaven't downloaded them, going to bed now02:39
xivulonrev495 md5 is a96aa69961f3ed80dd7a88fae1e2819602:39
=== foka__ is now known as foka
=== cr3_ is now known as cr3
doug2266778822 im running ubuntu gutsy gnome and i can not get my head phoen jack to work. can anyone help me?09:39
doug2266778822 im running ubuntu gutsy gnome and i can not get my head phone jack to work. can anyone help me?09:52
doug2266778822 im running ubuntu gutsy gnome and i can not get my head phone jack to work. can anyone help me?09:54
grrrregnot me09:55
grrrregnot me09:55
grrrregnot me09:55
sorendoug2266778822: Repeating the same question over and over again will win you no friends.10:21
sorendoug2266778822: Especially when the question doesn't belong in the channel in question.10:21
xivuloncjwatson, evand, for the first kernel upgrade or anything that would involve update-initramfs or update-grub after final, would it possible to have a procedure in place so that the changes are tested on loopinstallation before release?10:30
xivulon(if that is not already in place)10:30
cjwatsonyou'd need to talk to heno, I guess. What would we do if that failed?10:40
xivulonwell the user should be able to boot with an old kernel right?10:41
xivulonso far it seems to have worked, but I'd welcome a few extra tests, at least for the first new kernel10:42
TheMusoxivulon: Well as part of my wubi testing today, I was able to install another kernel alongside the generic kernel, in this instance I used the rt kernel.11:10
TheMusoAnd I had no issues, both kernels were bootable, no errors on package install.11:11
xivulonthanks TheMuso, that is in line with my own testing11:11
xivulonarg bdmurray reopened #20412811:55
james_wHi all.13:00
cjwatsonyo13:00
james_wUnder what circumstances would lilo be chosen over grub?13:00
james_wI just did an alternate install with manual partitioning, and set up LVM, and ended up with lilo.13:01
cjwatsonif /boot is on LVM; if /boot is on DM-RAID; if /boot is on XFS; if you preseeded grub-installer/skip=true13:01
cjwatsonyep, that's expected13:02
cjwatsondid lilo work properly?13:02
james_wyeah13:02
james_w /boot is not on LVM though13:02
james_wI *think*, let me check13:02
TheMusocjwatson: It would not matter if /boot was on dmraid as to whether lilo or grub is used, as at that point, the BIOS is still managing the disks.13:04
TheMusoAs its a BIOS fakeraid.13:04
TheMusoi.e the BIOS is used to set it up.13:04
TheMuso...or you meant device mapper raid... My ad.13:04
TheMusobad13:04
cjwatsonwell, no, I meant fakeraid13:04
TheMusospeech not speaking hyphens in some circumstances.13:04
cjwatsonI'm just explaining the code, though, I didn't write it :-)13:05
* TheMuso nods.13:05
cjwatson  * Add support for installing GRUB to a Serial ATA RAID disk. Currently this13:05
cjwatson    is only possible by using a semi-manual procedure that executes commands13:05
cjwatson    in the grub command environment (grub-install cannot be used).13:05
cjwatson    The current implementation assumes that teh SATA RAID disk will be listed13:05
cjwatson    as the first boot device in the BIOS.13:05
cjwatsonaccording to the changelog13:05
cjwatsonoh, I'm sorry, I misunderstood the code13:05
TheMusoRight. This is the stuff we'll need to look into for intrepid in any case.13:05
cjwatsonscratch the /boot on DM-RAID condition, I missed a negation13:05
james_wok, ext3 /boot, swap, xfs on lvm for /13:09
james_wthat doesn't seem to fit the criteria, but it is similar in places (lvm, xfs), so could it be a bug?13:17
cjwatsonpossibly, if /boot isn't on XFS13:30
cjwatsoner, on LVM13:30
james_wno, it's a separate partition.13:31
james_wWould you like a bug report?13:31
CIA-1apt-setup: cjwatson * r129 apt-setup/ (debian/changelog generators/50mirror.ubuntu):13:38
CIA-1apt-setup: * Remove restricted from cdrom entry if apt-setup/restricted is false13:38
CIA-1apt-setup:  (LP: #220805).13:38
cjwatsonjames_w: yes please, on grub-installer with /var/log/syslog and /var/log/partman attached13:38
james_wI don't have the latter, do I need to do something to make sure they are saved?13:39
cjwatsonif you've completed installation, both of those will be in /var/log/installer/13:40
james_wyup, thanks.13:41
james_w"/boot is an lvm volume, cannot install grub"13:42
james_wI think this may be even more unlikely to be a problem, as this was an installation after I had to reboot the host, and I picked up an existing LVM setup, which I then started again.13:43
isgleashi everybody15:46
isgleashow can I customize profiles on the live cd? I'm trying with sabayon profiling, but it does not work15:47
isgleasit doesn't seem to work with live session user15:48
bdmurrayxivulon: I added some more info to the bug16:23
* xivulon reading16:39
xivulonah I think I know16:41
xivulonthat's probably because the wubi executable is on the CD which you are ejecting16:41
xivulonthe strange part is that the executable should be fully unpacked into the temp folder so there shouldn't be any need to access wubi.exe anymore16:42
xivulonbut I am quite sure this is it, and that is why it is not an issue when you test wubi in stand-alone mode16:44
xivulonwhen you tested 488 successfully that wasn't on the CD was it?16:44
xivulonhmm I have always tested with virtual CD roms16:45
xivuloncan we please have more testing with real CDs?16:45
xivuloncan someone post on #ubuntu-testing?16:46
xivulonbdmurray: ^16:46
xivulona quick workaround would be to have umenu copy wubi on the tmp folder and then run it from there16:48
bdmurrayxivulon: to be clear you want more testing of Wubi off of real CDs correct?16:48
xivulonabsolutely16:48
xivulonbasically I would like to understand if it is a one off or if it affects every real CD installation16:50
xivuloncjwatson ping16:51
xivulonbug #20412816:51
ubotuLaunchpad bug 204128 in wubi "After install completed bar wasn't all green and installer hung" [Low,Confirmed] https://launchpad.net/bugs/20412816:51
xivulonhi evand ^^^17:03
evand|treohowdy.17:03
evand|treowhat's the issue?  im on my mobile and hitting lp would exit me from the irc client.17:03
xivulonit might be that wubi jams on eject when real CDs are used17:04
evand|treough, how on earth could we miss something like that?17:05
evand|treodavmor2 did test with real cds on real hw17:05
xivulonbecause if you run wubi off the CD (e.g. wubi.exe is on C:) then it would work fine17:07
evand|treoI imagine its far too late for a fix.  does this affect all wubi users?17:07
bdmurrayI'm talking to him now and his Vista isn't fully up to date17:07
xivulonevand we do not know yet17:07
xivulonbut it might affect all wubi users off CD17:07
evand|treook17:07
xivulonso it is RC IMO17:07
xivulonunfortunately yesterday I asked all testers to use the binary off your site because the one on the CD was an old version!17:08
xivulonarggg17:08
evandso my understanding is that we're going to release note this.  Is that correct?18:25
cjwatsonit sounds to me like a valid workaround is to tell people with Vista SP3 (or whatever it is) to download wubi from the network and use that?18:38
bdmurrayevand: that's the impression I have18:38
evandcjwatson: sounds right, they just cannot have an Ubuntu CD in the drive18:39
evandat least that's my understanding18:39
evandwubi is supposed to end up on ubuntu.com for the release, so that should make things a little easier18:39
bdmurrayI've found 2 possible workarounds18:39
evandoh?18:40
bdmurrayevand: Well as you mentioned running Wubi off the Vista system works.18:40
cjwatsonevand: my understanding was that it would work provided that you didn't run wubi off the CD18:42
cjwatsonsince xivulon has been saying that copying it to a temporary directory on the hard disk first is a workaround18:42
bdmurrayAnother, messier way, is to reinsert the CD, click the close button in Wubi.  Then choose "Close the program" when you are presented with the Windows dailog that "Wubi is not responding".18:42
evandcjwatson: yeah; just re-read the conversation in -release, I take back what I said.18:42
evand"With only the minimum amount of memory available, the installation process will take longer than normal, but will complete successfully, and the system will perform adequately once installed. Low-memory systems may be able to use the desktop CD to install by adding the only-ubiquity boot option to run just the installer rather than the whole desktop. "18:46
evandShouldn't that instead reference the "Install Ubuntu" option, rather than requesting the user muck around with the kernel command line?18:47
evandfrom w.u.c/HardyReleaseNotes18:47
cjwatsonyes, I'll edit, thanks18:48
bdmurrayI documented my workaround in bug 20412818:52
ubotuLaunchpad bug 204128 in wubi "After install completed bar wasn't all green and installer hung" [Low,Confirmed] https://launchpad.net/bugs/20412818:52
cjwatsonhmm19:52
cjwatson(oops, echan)19:52
bdmurrayevand: I'm experiencing bug 218973 again20:36
ubotuLaunchpad bug 218973 in ubiquity "20080417.1 Guided resize failed" [Low,Confirmed] https://launchpad.net/bugs/21897320:36
evandis it reproduceable?  If so, can you attach partman and syslog20:37
bdmurrayIt fails and in partman I see to run 'e2fsck -f /dev/sda8'.  I ran an fsck after exiting ubiquity, started again and now I'm told to run fsck again.  Should I run the fsck while ubiquity is still open?20:39
cjwatsonthat shouldn't be necessary (or indeed helpful)20:40
bdmurrayI've uploaded the syslog20:45
bdmurrayevand: I've added /var/log/installer/debug to the bug too21:24
evandbdmurray: ok21:27
CIA-1ubiquity: cjwatson * r2674 ubiquity/ (debian/changelog scripts/install.py): * Fix ownership of /home/oem/Desktop in OEM installations (LP: #209683).22:23

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!