[07:57] <ezakimak> raid=noautodetect is being ignored. how can I fix this?
[07:57] <ezakimak> also, how do I edit kernel arguments? (so far I've had to edit grub.cfg)
[13:09] <stgraber> cjwatson: just saw your comment in -release about bank holiday in the UK. I guess that means we aren't very likely to see ev around today?
[13:11] <stgraber> I worked on some bugfixes for ubiquity yesterday that should fix all current release targeteted high priority bugs, was hoping for him to look at what's broken in the unit tests (reason why 2.7.18 didn't build) and release 2.7.19 so we have it early for ISO testing
[13:12] <stgraber> my current test packages build with the unit tests turned off but I really would like to avoid pushing that in the distro (though after an hour of looking at it, I'm not too sure what's broken in there)
[13:13] <cjwatson> gah, why do we keep leaving the build broken over the weekend?
[13:13] <cjwatson> I guess ev won't be around.  nor will I, much, but I'll see if I can have a look in spare moments
[13:15] <cjwatson> I wouldn't be happy with uploading with disabled tests either ...
[13:55] <cjwatson> stgraber: ev SMSed to say he's unavailable
[13:55] <cjwatson> trying to reproduce the failure locally
[14:15] <CIA-31> casper: superm1 * r924 casper.oneiric/ (debian/changelog scripts/casper-bottom/15autologin):
[14:15] <CIA-31> casper: Don't fail to set up autologin on a commented out autologin-user line
[14:15] <CIA-31> casper: in lightdm custom conf. (LP: #836727)
[14:16] <CIA-31> casper: superm1 * r925 casper.oneiric/debian/changelog: releasing version 1.280
[14:49] <cjwatson> stgraber: could you please push your ubiquity changes/
[14:49] <cjwatson> ?
[14:49] <cjwatson> I'm working on the test fixes but would rather base on top of your work rather than needing to merge
[14:51] <stgraber> cjwatson: they are in lp:ubiquity
[14:51] <stgraber> cjwatson: rev 4883 to rev 4888
[14:55] <cjwatson> stgraber: oh.  can you please write debian/changelog entries to go with them, then?
[14:55] <cjwatson> closing whatever bugs are fixed
[14:56] <stgraber> Oops, I have the changelog here but forgot to make it look nice and push it. Will do that once I'm done with my call (~10 minutes).
[15:15] <stgraber> cjwatson: pushed. I'm pretty sure the greeter problem has a bug somewhere on Launchpad but the search function is currently timing out for me...
[15:17] <cjwatson> thanks
[15:18] <CIA-31> ubiquity: cjwatson * r4890 trunk/debian/changelog: typo
[15:18] <CIA-31> ubiquity: cjwatson * r4891 trunk/ (debian/changelog tests/test_timezone.py): Adjust timezone tests for change in timezone changed() signature.
[15:19] <CIA-31> ubiquity: cjwatson * r4892 trunk/ (debian/changelog tests/test_gtkwidgets.py):
[15:19] <CIA-31> ubiquity: Mock ubiquity.misc.drop_privileges and ubiquity.misc.regain_privileges
[15:19] <CIA-31> ubiquity: during test_face_selector_save_to.
[15:20] <cjwatson> that's everything working in a normal system, but the build log indicates more problems, so testing in pbuilder now
[16:14] <CIA-31> ubiquity: cjwatson * r4893 trunk/ (debian/changelog tests/test_gtkui.py):
[16:14] <CIA-31> ubiquity: Mock ubiquity.frontend.base.drop_privileges in GTK frontend tests to
[16:14] <CIA-31> ubiquity: cope with 'from ubiquity.misc import drop_privileges' form.
[16:22] <CIA-31> ubiquity: cjwatson * r4894 trunk/ (debian/changelog tests/test_gtkui.py):
[16:22] <CIA-31> ubiquity: Mock ubiquity.nm.wireless_hardware_present in GTK frontend tests, as it
[16:22] <CIA-31> ubiquity: may not be able to talk to D-Bus.
[16:22] <cjwatson> stgraber: phew, I think that's it passing tests now
[16:22] <cjwatson> will upload in a moment
[16:23] <CIA-31> ubiquity: cjwatson * r4895 trunk/debian/changelog: typo
[16:27] <stgraber> yeah!
[16:33] <CIA-31> ubiquity: cjwatson * r4896 trunk/debian/changelog: releasing version 2.7.19
[16:58] <superm1> i think there might still be a problem with the webcam page actually
[16:58] <superm1> i was noticing that it's trying to write to /var/lib/ubiquity without raising permissions when it writes (directory is owned by root:root and not writable otherwise)
[16:59] <cjwatson> is it causing a runtime crash?
[16:59] <cjwatson> please fix/upload if you can (but make sure tests still pass!) - I have to go for dinner now
[16:59] <superm1> yeah the page hangs
[16:59] <cjwatson> and let #u-r know if you think it's fatal
[17:00] <superm1> i'll do a quick run in sbuild to make sure tests pass with the fix
[17:00] <cjwatson> thanks for noticing
[17:00] <cjwatson> this webcam stuff landed really late :-/
[17:00] <superm1> yeah, and it's hard to catch in VM tests, only real hardware really
[17:00] <cjwatson> hm, I thought save_to raised privileges
[17:01] <superm1> only to create the directory
[17:01] <cjwatson> oh, yes
[17:01] <superm1> not for actually writing out the file
[17:01] <cjwatson> I knew I'd run into it while fixing tests
[17:34] <CIA-31> ubiquity: superm1 * r4897 ubiquity/ (debian/changelog ubiquity/gtkwidgets.py): Raise permissions for writing out webcam picture. (LP: #836802)
[17:34] <CIA-31> ubiquity: superm1 * r4898 ubiquity/debian/changelog: releasing version 2.7.20
[17:40] <stgraber> I'll start poking at the other beta1 targeted bugs in ubiquity. I don't see anything horribly critical in there so I'll just go through them one by one.
[18:09] <stgraber> jibel: I'm currently looking at bug 628970. I tried starting ubiquity with network disabled and in that case the "download updates" option is properly disabled. Then I tried with network turned on but no internet access and ubiquity considers that as being online so I can select to download the updates.
[18:09] <ubot2`> Launchpad bug 628970 in ubiquity "UI Inconsistency: No network detected but checkbox to download updates while installing is active" [Medium,Confirmed] https://launchpad.net/bugs/628970
[18:10] <stgraber> jibel: so I don't seem to be able to reproduce the problem you described. When was the last time you saw it?
[18:22] <jibel> stgraber, I don't remember. I'll try with latest image and let you know
[18:23] <superm1> it might not make so much sense to have the prepare page tell you to connect to a network before you actually get a chance with the wireless page right after no?
[18:23] <jibel> stgraber, if you're on ubiquity may be have a look at bug 830923 , bug 830895 (which affects also the link 'advanced partitioning') I don't know what's the status.
[18:23] <stgraber> jibel: thanks
[18:23] <ubot2`> Launchpad bug 830923 in ubiquity "Create partition: FS and mount point lists not legible" [High,Confirmed] https://launchpad.net/bugs/830923
[18:23] <ubot2`> Launchpad bug 830895 in ubiquity "Unable to show release notes: operation not supported" [High,New] https://launchpad.net/bugs/830895
[18:25] <stgraber> superm1: indeed. Ideally these options should appear after the wireless page.
[18:25] <stgraber> superm1: I'm also not sure I want to disable the "download updates" entry when we don't have "internet" access but have "internal network access" as someone described in the bug report. As in some cases (I had most my customers setup like that) you have access to archive.u.c but not to the rest of the world.
[18:26] <stgraber> so updates will still install fine even though changelogs.u.c (or whatever we poke to check for connectivity) won't answer
[18:26] <stgraber> I guess it's more important to make sure we don't fail to install when "download updates" is selected and we indeed don't have access to archive.u.c
[18:27] <stgraber> jibel: ok, I'll have a look at these two first. I was currently poking at bug 690926.
[18:27] <ubot2`> Launchpad bug 690926 in ubiquity "Installer forces you to install grub somewhere" [Medium,Incomplete] https://launchpad.net/bugs/690926
[18:27] <superm1> so maybe the download updates should really be "Try to Download Updates"
[18:27] <superm1> and if for any reason it doesn't work, it just fails gracefully
[18:28] <stgraber> superm1: yep, renaming it would make sense. I'd let ev do that though as we'd probably need a UIFe + approval from design
[18:35] <stgraber> jibel: confirmed bug 830923 with current ubiquity. Fixing now.
[18:35] <ubot2`> Launchpad bug 830923 in ubiquity "Create partition: FS and mount point lists not legible" [High,Confirmed] https://launchpad.net/bugs/830923
[18:36] <stgraber> doh, I meant bug 830895
[18:36] <ubot2`> Launchpad bug 830895 in ubiquity "Unable to show release notes: operation not supported" [High,New] https://launchpad.net/bugs/830895
[20:17] <kyleN> ev. Hi. After changing focus, I am back to to project I mentioned last week. ubiquity-dm still fails to start x (I have an xorg log with backtrace and can provide any other files if you want). I can start x with 'sudo startx' from another tty. I can launch lightdm from tty. What I cannot do is get oem-config to start on boot (after running 'oem-config-prepare'). Maybe I don't have the proper user configured that is expected? W
[20:17] <kyleN> hat is expected? I do have (on tty7) error msgs that I can't find anywhere else, including ubiquity-dm errors from lines 557 and 245. I can send you a photo of that if you like.
[20:19] <kyleN> ev, so I need a little help to figure out if this is something wrong with my system or not since I have now spent a day on it and have not discovered the root cause.
[20:22] <stgraber> kyleN: what version of ubiquity is that?
[20:23] <kyleN> stgraber, 2.7.17
[20:23] <stgraber> kyleN: I fixed ubiquity -g yesterday which may have fixed your bug. Would be interesting to know if it still happens with 2.7.20
[20:23] <stgraber> kyleN: ok, my fix is in 2.7.19
[20:24] <kyleN> stgraber, what do you mean by ubiquity -g? is that related to the oem-config path?
[20:25] <stgraber> -g is ubiquity in greeter mode which IIRC is called as part of ubiquity-dm. Not sure if that affects your use csae. Anyway, it'd be interesting to test with 2.7.20 as there's been a bunch of bugfixes.
[20:26] <kyleN> interesting
[20:26] <kyleN> 2.7.17 is the latest I get from apt-cache policy
[20:27] <kyleN> i do see 2.7.18 here: http://packages.ubuntu.com/source/oneiric/ubiquity
[20:28] <stgraber> 2.7.18 failed to build, 2.7.19 was uploaded a bit earlier today, followed closely by 2.7.20 (to fix a webcam problem)
[20:28] <kyleN> so probably wehn I test this tomorrow I'll have 2.7.20.
[20:28] <stgraber> jibel: I fixed 830895 and found the problem behind 830923 (though not the solution yet, learning about gtkcss now :))
[20:29] <stgraber> kyleN: yeah, I know we're currently waiting for ubiquity to publish to get a new batch of ISO images for beta1
[20:30] <stgraber> kyleN: https://launchpad.net/ubuntu/+source/ubiquity/2.7.20
[20:30] <kyleN> ok, thx stgraber