=== superm1` is now known as superm1 [04:11] hey [04:11] i have a problem when the instaler gets to the user screen [04:12] with ubuntu 10.10 [04:12] the next button will not allow me to press it [04:12] any ideals [04:13] trying to instal from cd already burnned disk 2 times and downloaded iso twice both times it stoped in the same spot [09:52] we would like to add geolocation to the timezone screen for the installation - ----> "[X] Automatically detect my timezone (using my internet connection" something like that ;) [09:53] for what packages we would have to commit patches? [09:55] mvk, other than casper (which i mentioned before), ubiquity looks to be related (based on its description) it might be worth having a poke in there [09:56] thank you :) [09:59] mvk, I believe it already tries to do that. I may be mistaken, but probably saner to just go ahead and do it rather than force the user to make a choice. [09:59] well, what about having the option - and making it 'checked' [09:59] you gotta think about privacy here as well [10:00] Considering that the install already makes a couple network calls to known services, I don't think it would be meaningfully different. [10:00] im funding people to get this done, what geolocation system will be used, im not sure about atm [10:00] i cant simply assume that it would be ok, so i wont [10:00] Things like using ntp to set the time correctly, pulling fresh updates from a hardcoded set of URLs, etc. [10:01] mvk, Indeed, it does already do this, based on geonames and the Olsen DB. [10:01] are you sure!? [10:02] It's in the changelog for maverick. [10:02] ' and automatic timezone selection via an GeoIP location service present in the upcoming Ubuntu 10.10 (' [10:03] Seems to be bug #229884 [10:03] Launchpad bug 229884 in ubiquity (Ubuntu) (and 1 other project) "use geoip for default location (heat: 3)" [Wishlist,Fix released] https://launchpad.net/bugs/229884 [10:04] And theres any number of updates and bugfixes to the functionality since that was committed. [10:06] so it should actually work [10:06] For IPs that geolocate. [10:06] The geoip stuff could be buggy, of course. [10:40] mvk: the kde frontend acts differently from the gtk frontend in that regard [10:41] at least I think it does [10:41] don't remember the details [10:42] anyway to work on the installer you need a virtual machine such as virtualbox-ose (or a computer you don't mind reformatting every time) [11:00] Riddell, Significant changes seem to be in tzsetup rather than ubiquity, so there's a decent chance that the kde frontend can do it (although I'm unsure if it does) [11:01] it does some geolocation which as put in during lucid cycle but I think not the same as what ev put in during maverick [11:02] Looks to me like the geolocation timezone stuff was supposed to hit in lucid, but the ubiquity bit was buggy until maverick. Quite possible the kde frontend still has some bugs (or a sufficiently different UI to not expose the geoip stuff) [11:02] right, there are two things at play here and they do two things [11:03] My memory is that the install experience for the gtk and kde frontends is rather different. [11:03] tzsetup, the debian-installer component as used in both the alternate and desktop CDs hits http://geoip.ubuntu.com/lookup [11:03] this gives it a geoip based default, but does not force the user to use it [11:04] this was added in lucid, as Riddell suggests [11:04] the geonames stuff that landed for 10.10 and only exists in the Ubuntu (gtk) desktop CD installer allows the user to type a place name in a box below the timezone map [11:05] it then sends this to http://geoname-lookup.ubuntu.com/?query=%s which then returns a set of results that are displayed in a drop down box in the interface [11:06] But the default is still set based on geoip regardless of the frontend? The kde environment just doesn't have the geoname entry box? [11:06] using the results as you type stuff in gtk entries [11:06] persia: correct [11:06] Ah, good. Then mvk would do well to test&verify, and probably fund some other useful installer work rather than geoip-based timezone selection. [11:07] if the user selects one of these results, the latitude / longitude pair is taken and converted into an olsen db location using a color coded image (much like how the hit detection is done in the graphical map) [11:07] persia: indeed, I agree [11:09] Note that if privacy is of concern, the user or distributor can set the debconf key tzsetup/geoip_server to null in a preseed [11:09] mvk, So, whilst the lead installer developer (ev) is here: what else is on your installer wishlist? I'm sure we can find something that needs a bit of work. [11:09] this will disable the geoip autodetection [11:09] hi [11:09] hi [11:10] persia: proper SSD device detection is missing [11:10] ev [11:10] mvk: can you elaborate on what's missing? [11:10] with other words >> noatime,discard, should be added for the appropriate devices [11:11] while noatime (no access time updates for files that are red) is second [11:11] the discard option (to invoke usage of TRIM support) should definitly be there [11:13] noatime is already there [11:14] i was a bit shocked actually to notice 'discard' was not there after using 'use my whole drive', during installation [11:14] alignment with the drive is done properly now i heard ........ [11:15] ev: this is how i made it > # / was on /dev/sda1 during installation [11:15] UUID=afe246d9-b0f7-4cc5-abcb-9d7bc1100ee7 / ext4 discard,noatime,errors=remount-ro 0 1 [11:15] but after installation, it looked like > # / was on /dev/sda1 during installation [11:15] UUID=afe246d9-b0f7-4cc5-abcb-9d7bc1100ee7 / ext4 errors=remount-ro 0 1 [11:15] so, no atime nor discard [11:19] as I understand it, discard has not gone through the rigors of proper testing yet and will be made the default when its ready. [11:22] ok [21:25] hey have an instal problem [21:26] when i get to the user set up page the next button doesnt allow me to press it and below just tells me whenever im ready