[00:08] <CIA-33> ubiquity: evand * r3464 ubiquity/ (debian/changelog ubiquity/frontend/gtk_ui.py): Suppress Pango warning about not being able to open /root/.pangorc.
[00:18] <rgreening> evand: https://blueprints.launchpad.net/ubuntu/+spec/usb-creator-console
[00:19] <evand> rgreening: cool idea!
[00:19] <rgreening> :P
[00:19] <rgreening> think that will help me get to go to UDS again :)
[00:19] <evand> :)
[00:20] <rgreening> hehe
[00:20] <rgreening> It should be relatively easy compared to the rest of what we have done
[00:21] <rgreening> and will work with may rescue CD (if one chooses to make a rescue CD/Partition for Ubuntu
[00:21] <rgreening> which would be another cool spec... hmm...
[00:23] <evand> rgreening: can you implement a KDE retry dialog (see my recent commit for the GTK side)
[00:23] <evand> it's existed for ages in the Windows frontend, I just forgot about it for the rest :)
[00:23] <rgreening> evand: yeah, I have to review your last 4 or 5 commits...
[00:24] <evand> I imagine this will require a UI Freeze Exception, but I think it's necessary
[00:24] <evand> heh
[00:24] <rgreening> but my usb stuff is broken atm.. debating on a re-install...
[00:24] <evand> yikes
[00:24] <rgreening> evand: any idea what would cause usb auto detection to not work? I see /dev/sdc1 and can manually mount.. but that's as far as it goes.
[00:25] <rgreening> no autodetection...
[00:25] <evand> is devicekit running?
[00:25] <rgreening> evand: your good in that area...
[00:25] <rgreening> hmm... should be 1 sec
[00:25] <evand> err actually, I'm not sure what the KDE stack uses
[00:25] <rgreening> devkit-disks-daemon:
[00:25] <rgreening> hal
[00:26] <evand> rgreening: is this Karmic?  Have you been upgrading over the past few days?
[00:26] <rgreening> oh yeah. and thens when it broke
[00:26] <rgreening> I had to recover via a chroot
[00:26] <evand> yeah, Keybuk broke the universe
[00:26] <evand> are you completely up to date?
[00:26] <rgreening> yep
[00:26] <evand> hrm
[00:26] <rgreening> evand: I even installed ubuntu-desktop and tested there
[00:27] <rgreening> same issue.
[00:27] <rgreening> I opened a bug... 1 sec...
[00:27] <evand> if you run udevadm monitor, do you get events for the usb key insertion/deletion?
[00:27] <rgreening> bug 431878
[00:27] <evand> err yeah, I imagine you would if you can manually mount it
[00:27] <evand> ah
[00:28] <rgreening> I attached some output there
[00:28] <rgreening> dmesg shows the drive insertion and removal fine... shows up in the /dev dir fine.
[00:30] <evand> probably either broken KDE or broken Hal
[00:31] <evand> so yeah, ouch
[00:31] <rgreening> udevadm monitor sow the device removal and insertion fine...
[00:31] <rgreening> not KDE
[00:31] <rgreening> remember I tried ubuntu desktop too
[00:31] <evand> that's quite perplexing
[00:31] <rgreening> I installed and launched a gnome session
[00:31] <rgreening> here's what udevadm shows...
[00:31] <rgreening> UDEV  [1253230189.832105] change   /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.0/host18/target18:0:0/18:0:0:0 (scsi)
[00:31] <rgreening> KERNEL[1253230189.898774] add      /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.0/host18/target18:0:0/18:0:0:0/block/sdc (block)
[00:31] <rgreening> KERNEL[1253230189.898885] add      /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.0/host18/target18:0:0/18:0:0:0/block/sdc/sdc1 (block)
[00:31] <rgreening> KERNEL[1253230189.898997] add      /devices/virtual/bdi/8:32 (bdi)
[00:32] <rgreening> UDEV  [1253230189.899238] add      /devices/virtual/bdi/8:32 (bdi)
[00:32] <evand> oh, I have no doubt that udev (and by extension devicekit-disks) see the device
[00:33] <rgreening> so why did gnome hate me too
[00:33] <rgreening> :)
[00:33] <rgreening> or is gnome still using hal for those bits
[00:34] <rgreening> evand: hal is reporting it as dev/sg3 and not /dev/sdc
[00:34] <evand> KVM to the rescue?  If you have a block device to work with, you can always run sudo kvm -m 512 -hda /dev/sdc -cdrom $path_to_cd -usb, and then ctrl-alt-2 to the kvm console, type info usbhost, then usb_add host:whatever_id
[00:34] <rgreening> you lost me at rescue
[00:34] <rgreening> haha
[00:35] <evand> assuming the CD is not equally broken (shouldn't be, the latest is working for me), you'll at least have an environment to work in
[00:35] <evand> haha
[00:35] <rgreening> Im booted and running fine.. its just that one issue I cant fix.
[00:36] <evand> incidentally, if devicekit-disks can see it (as it does, given your logs), usb-creator will work just fine :)
[00:36] <rgreening> evand: that's just it... it doesn't
[00:36] <rgreening> neither the gtk nor the kde
[00:36] <rgreening> which boggles me
[00:36] <evand> does devicekit-disks --enumerate show the disk?
[00:37] <rgreening> I have gremlins in my computer
[00:37] <rgreening> 1 sec
[00:37] <evand> clearly :)
[00:37] <evand> err devkit-disks
[00:37] <rgreening> /org/freedesktop/DeviceKit/Disks/devices/sdc1
[00:37] <rgreening> yep
[00:37] <rgreening> Ah evand, I was mistaken....
[00:38] <rgreening> evand: it does show up in creator.. but the Free is empty and it says you must format this device (which it doesn't need too)
[00:38] <rgreening> evand: clearly /dev/sdc1 is not being presented to devkit correctly
[00:39] <rgreening> which points to messed up udev symlinks or such
[00:39] <evand> devkit-disks --mount /dev/sdc1
[00:39] <rgreening> yeah, not it works as expected in creator
[00:40] <evand> shtylman: did you ever hear back from the release team on that ubiquity merge?
[00:40] <rgreening> so, normally, the code would auto mount the device.. which appratnly is being skipped
[00:40] <rgreening> because of the way it's being detected evand...
[00:40] <evand> I'm lost.
[00:41] <rgreening> haha
[00:41] <evand>  /dev/sdc1 does or does not show up in usb-creator
[00:41] <rgreening> evand: ok, so, normally creator will detect and mount the partitions
[00:42] <shtylman> evand: no I didn't...
[00:42] <rgreening> yes, it shows up in creator, but Free was empty and it would let me use it (said it needs format). Running the devkit mount manually shows the partition correctly and allows me to interact
[00:42] <shtylman> Riddell did say that he could approve it... but I havn't merged... what do you think?
[00:42] <evand> shtylman: I'd file a bug against ubiquity, include the branch, and subscribe ubuntu-release
[00:42] <evand> oh, if he's fine pushing that through it's fine with me
[00:42] <shtylman> evand: ok...sounds good, I will do that... it will be more official that way :)
[00:43] <evand> just make sure you follow the Provides: mangled-version stuff
[00:43] <evand> ah, sure thing
[00:43] <shtylman> noted
[00:44] <evand> rgreening: were there any tracebacks in ~/.usbcreator.log (assuming an up-to-date bzr trunk)?
[00:44] <rgreening> 1 sec... I'll look at /tmp/...
[00:44] <evand> rgreening: if you're running from trunk it will be in /home now
[00:45] <rgreening> yeah, not trunk yet
[00:46] <rgreening> evand: it shows no error. It detect /dev/sdc as 0 byte disk (which I don't think was happening before).. that should be a clue
[00:47] <rgreening> evand: before /dev/sdc would simply have 0 free not be a 0 byte disk...
[00:47] <rgreening> and I only see /dev/sdc1 and not /dev/sdc and /dev/sdc1 like before...
[00:47] <evand> are you sure it's detecting it as that, and not just setting that in its data structure (devkit-disks --dump can tell you)
[00:48] <rgreening> Im reading from the log in creator
[00:48] <rgreening> backend.py:187: not adding device: 0 byte disk.
[00:48] <rgreening> backend.py:67: device_added: /org/freedesktop/DeviceKit/Disks/devices/sdc1
[00:48] <rgreening> backend.py:122: partition added: /org/freedesktop/DeviceKit/Disks/devices/sdc1
[00:52] <rgreening> evand: Im soo not happy :(
[00:52] <rgreening> a reinstall is going to kill my productivity
[00:53] <evand> so just to confirm, devkit-disks --dump reports a 0 B size for sdc?
[00:53] <rgreening> evand: devkit-disks dump reports size 0
[00:53] <rgreening> ya
[00:54] <evand> heh, read my mind
[00:54] <evand> yikes
[00:55] <rgreening> lol
[00:55] <rgreening> evand: here's the dump output for sdc http://paste.ubuntu.com/273167/
[00:56] <rgreening> i think by-id, by-path stuff missing? bad? incorrect?
[01:02] <rgreening> evan had media 0 is wrong too
[01:02] <rgreening> evand ^
[01:03] <rgreening> and partition scheme should be mbr
[01:03] <evand> indeed
[01:04] <rgreening> evand: so what provides this to devkit... udev correct?
[01:07] <evand> yes
[01:07] <rgreening> so I have a buggered udev...
[01:07] <evand> probably
[01:07] <rgreening> hmm.. wonder how best to make it clean
[01:07]  * rgreening hears evand say reinstall
[01:07]  * rgreening preemptively reaches for lart
[01:08] <evand> not sure, Keybuk or pitti might have a better idea of what's going wrong
[01:09] <rgreening> pitti said to file the bug... and I did.. of course it didn't help that apport-kde it foobar
[01:09] <rgreening> and hence ubuntu-bug
[01:09] <rgreening> lol
[01:09] <rgreening> not my week
[01:10] <evand> haha
[01:13] <rgreening> this is so bizarre oh well...
[01:13] <rgreening> might as well go cut my heart out with a spoon, it will be less painful :P
[01:15] <evand> haha
[01:15] <rgreening> im heading home... Ill decide by then if I reinstall
[01:15] <rgreening> heh
[01:15] <rgreening> l8r
[01:18] <evand> cheers
[09:14] <davmor2> cjwatson: thanks for the showmounts tip that is what matt wanted it just threw me with the title :)
[09:14] <davmor2> looks better now than it did thought looking at it :)
[09:25] <CIA-33> usb-creator: evand * r210 trunk/ (3 files in 3 dirs): Fix a deadlock when the failed dialog runs.
[10:36] <ogra> cjwatson, http://paste.ubuntu.com/273343/ i suspenc i miss something that adds the do_symlinks entry to kernel-img.conf, which piece of d-i does that ?
[10:36] <ogra> *suspect
[10:38] <ogra> mn, i think i found it
[10:38] <ogra> *nm even
[10:41] <ogra> Sep 17 17:56:27 base-installer: info: Setting link_in_boot='yes'
[10:41]  * ogra scratches head
[12:23] <CIA-33> ubiquity: evand * r3465 ubiquity/ (debian/changelog ubiquity/frontend/gtk_ui.py):
[12:23] <CIA-33> ubiquity: * Use the page name instead of the new step name when considering both
[12:23] <CIA-33> ubiquity:  partitioning pages.
[12:23] <CIA-33> ubiquity: * Fix broken conditional statement that prevented
[12:23] <CIA-33> ubiquity:  process_autopartitioning and info_loop from being called.
[13:16] <CIA-33> ubiquity: evand * r3466 ubiquity/ (3 files in 2 dirs):
[13:16] <CIA-33> ubiquity: Disable the forward button for the usersetup page when coming from
[13:16] <CIA-33> ubiquity: both the automatic and manual partitioning pages, rather than just
[13:16] <CIA-33> ubiquity: the latter.
[13:24] <CIA-33> ubiquity: evand * r3467 ubiquity/ubiquity/frontend/kde_ui.py: Repeat r3465 for kde_ui.py
[14:26] <CIA-33> usb-creator: evand * r211 trunk/usbcreator/frontends/gtk/frontend.py: Always return something from get_gnome_drive.
[14:44] <evand> cjwatson: what was the reasoning behind making mtools a recommends of syslinux rather than a firm dependency?  It appears to be completely non-functional without it.
[14:46] <gunsofbrixton> hi, I am a kubuntu user and I noticed that the installer selects a keyboard depending on the language and not on the time zone. if the two don't match I would think that it's more frequent that someone uses a foreign language than a foreign keyboard... am I overlooking something or should I report a wish somewhere?
[14:49] <evand> gunsofbrixton: I believe you're mistaken.  The installer bases its keyboard selection on both the language and time zone.
[14:51] <gunsofbrixton> evand: ah interesting. I always choose english language and german time zone, and get an english keyboard selected... is this how it's supposed to work?
[14:52] <evand> gunsofbrixton: yes, I do believe so.
[14:52] <evand> Selecting Spanish with a timezone selection in Mexico and one in Spain give different keyboard suggestions.
[14:54] <gunsofbrixton> evand: ok that makes complete sense. but consider my scenario where there is no correlation between language and time zone. I would think that german keyboard should be selected and not english, what do you think?
[14:57] <gunsofbrixton> evand: and in the spain/mexico example why consider the language in the first place? couldn't you just use the location?
[14:57] <gunsofbrixton> I am just a dumb user asking :)
[14:59] <evand> There are countries that speak more than one language.
[15:00] <evand> I am not sure on the exact details of why this approach was taken, and I cannot think of an example offhand that would invalidate your suggestion
[15:00] <evand> cjwatson would know, though
[15:02] <evand> s/speak more than one language/have more than one common keymap/
[15:02] <cjwatson> evand: mtools> it's needed for the syslinux binary itself but not for other uses of the syslinux package like building CDs, so I downgraded it to reduce the delta with Debian
[15:03] <cjwatson> gunsofbrixton: in the Mexico case, we do in fact use only the location
[15:03] <cjwatson> all we can do is heuristics that are as good as we can manage, though
[15:03] <cjwatson> without reading the user's mind, there's no way to be sure about it, so I don't think it's worth stressing too much
[15:04] <cjwatson> file a bug on console-setup if it does obviously the wrong thing :)
[15:04] <cjwatson> I'm not sure I agree with the hypothesis that location is more likely to match than language; I think you would need data for that rather than guesswork
[15:05] <cjwatson> for instance, I could easily say that if somebody's preferred language doesn't match their location, there's a decent chance that they emigrated from somewhere else, and that they may well have brought their old computer with them or at the very least be used to the keymap in the country they come from
[15:05] <cjwatson> if I moved to France, for instance, I don't think you could ever convince me to type on a French keymap :)
[15:07] <evand> cjwatson: ah, noted on syslinux
[15:08] <cjwatson> but basically we use the language when the upstream xkeyboard-config layout files are structured such that there's a layout for the language and then some variants depending on the location (e.g. German), but we use the location when the files are structured such that there's a layout for the location and then some variants depending on the language (e.g. Belgium)
[15:08] <cjwatson> this tends to mean that plausible alternatives are closer to hand in case we guessed wrong
[15:09] <cjwatson> davmor2: do you have the machine to hand where I might be able to debug this grub menu generation thing, then?
[15:10] <davmor2> cjwatson: I can have a machine with xp or vista on in a matter of minutes but I'm just working on install and debuggin' a kernel issue on my nvidia box.  so 30 minutes-ish
[15:11] <gunsofbrixton> cjwatson: evand: good points, thanks for clearing that up. would indeed be interesting though to know if language or location is the better match
[15:12] <CIA-33> usb-creator: evand * r212 trunk/debian/ (changelog control):
[15:12] <CIA-33> usb-creator: Explicitly depend on mtools, just in case someone removes it and
[15:12] <CIA-33> usb-creator: expects usb-creator to still work.
[15:12] <cjwatson> davmor2: thanks
[15:13] <CIA-33> usb-creator: evand * r213 trunk/debian/changelog: LP bug reference for the previous commit.
[15:22] <rgreening> evand: does failed_dialog_label ever show the "see usbcreator.log" message? I can't see anywhere where it would. Seems the _fail def overrides that message.
[15:22] <rgreening> so its superfluous at best to have it in the gtk ui.
[15:23] <evand> ah, I guess not.
[15:23] <rgreening> :)
[15:23] <davmor2> cjwatson: have you seen the bug apparently os-prober isn't installed, is that still needed? https://bugs.launchpad.net/bugs/430141
[15:25] <davmor2> meh it's installed here
[15:26] <CIA-33> usb-creator: rgreening * r214 trunk/ (debian/changelog usbcreator/frontends/kde/frontend.py): * Add the missing retry dialog to the KDE frontend.
[15:28] <cjwatson> davmor2: they're hijacking your bug. ignore them
[15:28] <cjwatson> I've told them off in a comment already :)
[15:29] <davmor2> cjwatson: change the title on me and everything :)
[15:34] <ogra> cjwatson, not sure you saw my d-i error paste this morning, http://paste.ubuntu.com/273343/ ... i tracked it down to a line in mkinitramfs that apparenly parses the output of mount (instead of using /proc/mounts) which doesnt output anything here under armel if i run it in /target, you dont happen to have seen similar errors on other arches, do you ?
[15:34] <davmor2> Right then cjwatson do you need any info off the vista install before I start on the ubuntu auto resize?
[15:36] <cjwatson> ogra: there's a known debootstrap problem
[15:36]  * ogra wonders if it's arch specifc that mount doesnt output anything in that environment or if there is just something missing in the way imx51 uses d-i 
[15:36] <cjwatson> ogra: I've just been holding off on the sync because something went wrong when I fixed it in Debian and I need to remind myself of what
[15:36] <ogra> ah, sweet ...
[15:36] <cjwatson> davmor2: don't think so
[15:37] <davmor2> right ubuntu along side then
[15:55] <CIA-33> usb-creator: rgreening * r215 trunk/TODO: * Update TODO
[15:59] <CIA-33> usb-creator: rgreening * r216 trunk/ (debian/changelog man/usb-creator-gtk.8 man/usb-creator-kde.8): * Update man pages to reflect new location of log file
[16:09] <evand> good call
[16:13] <cjwatson> evand: do you think you could look at fixing bug 419796? it seems to have bounced back onto the foundations team's list
[16:13] <evand> oh, I did fix that
[16:13] <evand> I've just been waiting for davidz to review the patch
[16:16] <cjwatson> aha
[16:16] <cjwatson> I'll assign it to you then
[16:16] <cjwatson> could you reference that in the bug?
[16:16] <evand> absolutely
[16:16] <cjwatson> ah, there's a bug link
[16:17] <evand> there's another one that I've filed upstream that I haven't filed a bug in LP for
[16:17] <evand> is something else other than usb-creator being affected by devicekit-disks being broken?
[16:17] <davmor2> cjwatson: right up
[16:17] <evand> https://bugs.freedesktop.org/show_bug.cgi?id=23926
[16:18] <cjwatson> evand: not afaik
[16:18] <davmor2> cjwatson: lets try that again so it makes sense.  Right,  up
[16:18] <evand> okay
[16:20] <rgreening> evand: so.. close to getting the format re-enabled then?
[16:20] <evand> rgreening: there's just one bug that stands in my way, but I've been focused on other things as of late
[16:20] <evand> 23926, as mentioned above
[16:21] <rgreening> yeah, I see that... just saying.. it's close now :)
[16:37] <davmor2> cjwatson: okay what do you need me to do?
[16:39] <evand> rgreening: ah, sure, though depends how you define close
[16:39] <evand> davidz did just tell me that he's fine with my existing patch and that he's going to do a run over the existing bugs and make a new release of devicekit-disks today
[16:39] <evand> the property names are changing from property-name to PropertyName, but that will be an easy fix
[16:41] <cjwatson> davmor2: sorry, in the intervening time the release meeting started; give me a bit ...
[16:41] <davmor2> no probs
[16:59] <evand> rgreening: FYI: https://bugs.edge.launchpad.net/ubuntu/+source/usb-creator/+bug/432542
[17:00] <rgreening> evand: awesome
[17:01] <rgreening> evand: I assume uploading new devicekit wont be an issue either...
[17:02] <rgreening> oh and evand, my usb issues are apparantly specific to this Acer 6930. I tried several iso's on this system and on my other laptops, the others all work except this one regardless of the iso (unless I use an Alpha5 which worked).
[17:03] <rgreening> so something wrt to firmware, ios or kernel maybe...
[17:11] <rgreening> but as a side note, my battery indicator has seemingly started to work now... hah
[17:13] <evand> haha
[17:16] <rgreening> brb reboot
[17:50] <cjwatson> davmor2: ok, control data first: can you show me /boot/grub/grub.cfg, and the output of 'sudo update-grub'
[17:54] <davmor2> cjwatson: both on bug
[17:56] <davmor2> would you like a new look grub.cfg after running update-grub?
[17:57] <cjwatson> davmor2: is it different?
[17:58] <cjwatson> davmor2: if so, yes please
[17:58] <davmor2> cjwatson: on the bug looks like it might be listing it now
[17:58] <cjwatson> now that's just WEIRD
[17:59] <cjwatson> how am I supposed to debug this when the bug goes away when I look at it? :-/
[18:00] <davmor2> cjwatson: want me to reboot and see if it is in the menu and boots on reboot?
[18:01] <cjwatson> no need
[18:01] <cjwatson> what was the version of ubiquity on the image you did this most recent test with?
[18:03] <davmor2> I second
[18:07] <davmor2> cjwatson: 1.99.21
[18:07] <cjwatson> ok, can I have an updated installer syslog?
[18:08] <davmor2> yeap need to reboot again
[18:10] <cjwatson> bah, grub2 throws away errors from os-prober, how unhelpful
[18:10] <cjwatson> I have a suspicion
[18:11] <cjwatson> davmor2: if you have time to start a fresh install, could you try that, but before you start the installer, run:  sudo apt-get install patch; wget -O- http://paste.ubuntu.com/273623/ | sudo patch /usr/share/ubiquity/install.py
[18:11] <cjwatson> err, sorry, amend that
[18:11] <cjwatson> sudo apt-get install patch; wget -q -O- http://paste.ubuntu.com/273623/plain/ | sudo patch /usr/share/ubiquity/install.py
[18:12] <davmor2> syslog up
[18:13] <davmor2> re-install on it's way
[18:14] <cjwatson> you're a star
[18:40] <davmor2> cjwatson: no joy :( want the logs?
[18:41] <cjwatson> drat. yeah
[18:41] <cjwatson> dinnertime anyway
[18:42] <cjwatson> I suspect I might have to go and reproduce it myself; if it's anything like I think it is that might not be too hard
[18:42] <davmor2> cjwatson: yeap I'm off out for a bit but can help out again latter
[18:43] <cjwatson> I'm going to upload a grub2 package that is less militantly unhelpful about errors from os-prober
[18:45] <davmor2> syslog up off now
[23:19] <davmor3> kirkland: On Monday I'll do an encrypted home and show you the dialogue box you get.  Then you will understand why I type ecryptfs-unwrap-passphrase
[23:24] <kirkland> where did davmor3 go?