/srv/irclogs.ubuntu.com/2009/09/16/#ubuntu-devel.txt

Keybukyes00:00
Keybukany problems after >1hr are real problems ;)00:00
jonoKeybuk, thanks for your work on this :)00:00
Keybukjono: thank slangasek, cjwatson and lamont more than me00:00
maxbIs there a package we can watch for to know we've got all the updates that are expected to make things work again?00:00
jonothanks slangasek, cjwatson :)00:00
jonoright, gonna go buy an ethernet cable so I can upgrade in a bit :)00:01
* maxb wonders what this means:00:01
maxbSetting up rsyslog (4.2.0-2ubuntu3) ...00:01
maxbrestart: Unknown instance:00:01
Keybukit's upstart's way of saying "not running"00:01
squirrelpimpwill the changes be published on the xy.archive.ubuntu.com mirrors? Or only on some master servers?00:01
Keybuksquirrelpimp: in the usual fashion00:01
squirrelpimpwhich i don't know :(00:02
=== ulrik is now known as engla
Keybuksquirrelpimp: the changes are published to a master archive, from which the primary mirrors sync from00:02
Keybukother mirrors may sync from other mirros00:02
squirrelpimpok00:02
slangasekjono: thank cjwatson and lamont, I'm just watching and waiting to be able to start CD builds :)00:02
squirrelpimpand that master-archive it the one without any country-code in front of it i guess...00:03
Keybukslangasek: I'd like to sneak in a couple of bug fixes before you do that00:03
squirrelpimpi think i'll go to bed and test it in the morning00:03
jonocheers lamont too :)00:03
Keybuk(you can say "no" if you like, and we'll just release note them <g>)00:03
loolslangasek: Do you know at what time livecd-rootfs is updated by any chance?00:03
slangasekKeybuk: what are they?00:03
Keybukslangasek: mountall can run fsck and mount simultaneously on raid devices that change00:04
KeybukX crashes during updates that reload D-Bus00:04
slangasekI still have to get software-store binaries into main before I can rebuild ubuntu-meta before I can start CD builds, so you have a bit of time00:04
Keybukmountall won't work if you don't have /dev/.initramfs/varrun00:04
Keybukok, cool00:04
KeybukI have the uploads ready, just wanted to wait for a full publish and your ok ;)00:04
cjwatsonslangasek: d-i needs to be built against the new linux, which hasn't built yet00:04
Keybukoh, and n-m shouldn't depend on HAL00:04
slangasekKeybuk: heh - yes, go ahead with them00:04
Keybuk(and shouldn't be restarted when HAL is)00:04
slangasekKeybuk: ^^ ah, cjwatson says you've got plenty of time00:04
cjwatsonslangasek: unless you want to relax the rule about d-i being up-to-date with the kenrel00:05
cjwatsonkernel00:05
Keybukgiven that the kernel in question has the ext3/4 fixes ... does that make a difference ?00:05
slangasekcjwatson: would rather not, no :)00:05
cjwatsonKeybuk: that isn't the only change00:05
cjwatsonI confess I don't know what all the others do00:05
cjwatsond-i is also several kernel revisions old, I think00:06
slangasekcjwatson: I can take care of the d-i rebuild once the kernel's available00:07
cjwatsonthanks00:08
slangasekcjwatson: anything else I should put on my todo list so you can have some time away? :)00:08
cjwatsonI think that's actually about it, I cleared up my pending eucalyptus stuff earlier, and did a ubiquity upload00:08
cjwatsonyeah, don't expect me in too early tomorrow :)00:09
* slangasek grins00:09
anderskIs it known that the initscripts upgrade does not actually remove the old init.d scripts (see http://wiki.debian.org/DpkgConffileHandling )?00:11
Keybukandersk: yes, they're still there for now so it's possible to rescue things that way00:13
Keybukbut if you could file a bug to remind me to remove them lest I forget00:13
anderskWill do.00:14
jdubKeybuk: i still have usplash bits in my initramfs00:15
Keybukjdub: possible00:15
Keybuktry the next update00:15
jdubok00:15
jdubalso, there's a fly in my soup.00:15
pochutry the next libsoup00:16
Keybukok00:16
KeybukI'm out of here for a bit, going to chill out while the publisher runs00:16
Keybukwill come back in an hour so, do some testing, and upload the three bug fixes00:16
maxbIs something supposed to remove the old scripts from /etc/init.d/ ?00:17
ionmaxb: Look a few centimeters above this line.00:18
maxbah :-)00:19
maxbSomething weird is happening with karmic for me - supposedly clean shutdowns don't seem to be unmounting my root partition cleanly, and ext3 journal recovery happens on boot00:24
maxbhas anyone else noticed that one?00:24
TheMuso8/c00:25
jpdsmaxb: Maybe bug #427822 ?00:28
ubottuLaunchpad bug 427822 in linux "fsck says last write time in future" [Critical,Fix committed] https://launchpad.net/bugs/42782200:29
maxbNo, that's something that goes wrong in *response* to a dirty unmount, not a cause thereof00:29
* kees wonders when it will be safe to dist-upgrade00:42
slangasekkees: half hour, maybe?00:43
keesslangasek: ok, cool.00:44
chrisccoulsonheh, i probably should have waited00:44
keesi'm curious how apparmor and ufw will turn out.00:44
slangasekchrisccoulson: just don't reboot until the next upgrade :)00:44
chrisccoulsonslangasek - too late, i already did that ;)00:45
* chrisccoulson is glad for live CD's00:45
maxbi386 seems ok already00:46
maxbamd64 looked like it might be, but I don't want to reboot yet00:47
chrisccoulsonmaxb - i run amd64 here;)00:47
squirrelpimpmaxb: i just tried amd64 with no luck00:48
cjwatsonarchive and gb.archive appear to have the complete set noww00:55
cjwatson-w00:55
cjwatsonother mirrors may have to wait longer00:55
cjwatsondepending on network distance etc.00:55
LaserJockugg, edubuntu's livefs build died a horrible death00:56
cjwatsonyes, along with the rest of the world00:57
cjwatsondon't worry about it, it should be fixed tomorrow00:58
chrisccoulsonmy machine is pretty screwed then, it still doesn't boot with the full set of packages00:58
chrisccoulsoni'll have to look at that tomorrow though00:58
squirrelpimpcjwatson: yes, lot's of packages arrived here as well00:58
squirrelpimpstill no booting :(00:58
cjwatsonok, Keybuk will have to follow up on that when he gets back I guess00:59
* cjwatson &00:59
jdubKeybuk: changing initramfs to MODULES=dep is pretty winful too01:04
jdubKeybuk: is that more or less aggressive than your proposed changes?01:05
bgamariNetworkManager seems to fail to start at boot01:05
bgamariOn newly fixed karmic system01:05
bgamariStarting manually works fine01:05
bgamariHow is NetworkManager supposed to be started at this point?01:05
bgamariahh, never mind; init.d01:06
ion/etc/init/network-manager01:07
* Keybuk returns01:12
squirrelpimpwb01:12
* ion gosubs01:15
squirrelpimpstill the last line i get is "/dev/mapper/vg0-root: clean, ... files..."01:17
Keybuksquirrelpimp: you're running an up-to-date karmic system01:19
Keybukamd64?01:19
squirrelpimpyes01:19
Keybukcan you get files from that system to IRC?01:19
Keybuk(without just typing them)01:19
Keybukie. upload them somewhere, or get them to pastebin, etc.01:19
squirrelpimpyes, i can boot it with a livecd01:19
Keybukok01:20
KeybukI need you to try booting with init=/bin/bash01:20
squirrelpimpbefore i do that, shall i copy something from the hung up boot process01:20
squirrelpimpok, i'll try that01:20
Keybukthen at the shell, run mountall --debug > /dev/mountall.log01:20
Keybuk(you may want an & there too)01:20
Keybukthen try running "udevd --daemon" and "udevadm trigger"01:21
Keybukafter that, move the log to the root filesystem if you can, and upload it so I can read it01:21
Keybuk(usb key is another option, btw)01:21
ionIIRC, the last time i tried, mountall refused to start from init=/bin/bash because it failed to connect to Upstart. It’s been a while from that attempt, though.01:22
Keybukoh01:22
Keybukright01:22
Keybukthat will probably happen01:22
Keybukd'oh01:22
Keybukerr01:22
* Keybuk thinks01:22
Keybukyou may have to write an upstart job to give you a shell ;)01:23
Keybukstart on startup01:23
Keybukconsole owner01:23
Keybukexec /bin/bash01:23
Keybuk;-)01:23
squirrelpimpwhere should i place that?01:23
Keybuksquirrelpimp: in /etc/init01:23
squirrelpimpthere's already a script called mountall-shell01:24
Keybukyes, but that will only fire if mountall exits with a failure01:24
Keybukyou're reporting "hanging"01:25
squirrelpimpright01:25
Keybukthat to me implies that mountall is still waiting for something01:25
Keybukanother option, btw01:25
Keybukis to change mountall.conf and put the --debug there01:25
Keybukand if you can, take a photo of the screen at the point it hangs and upload that somewhere01:25
squirrelpimpi'll prefer pastebin if that's ok01:25
Keybuksure01:26
squirrelpimpin the file goes: start on startup\n console owner\n exec /bin/bash\n01:26
ionProbably should also comment out ‘console output’ and remove --daemon, since daemonize^H^Hse reopens std{out,err} to /dev/null IIRC.01:26
ionEr01:26
Keybukion: mountall doesn't use daemonize ;)01:26
ioncomment out ‘expect demon’. Brainfart.01:26
squirrelpimpctrl+d gave me a kernel panic01:27
Keybuksquirrelpimp: yes.01:27
ionAh01:27
squirrelpimpk, reboot01:27
squirrelpimpdo i have to change kernel line?01:27
Keybukshouldn't need to01:27
squirrelpimpk, i have the shell again01:28
Keybuksquirrelpimp: "status mountall" from that shell01:29
=== rickspencer3 is now known as rickspencer3-afk
squirrelpimpok, i started mountall to a logfile with &01:29
squirrelpimprunning 132201:30
squirrelpimpbut pidof gives 2 pids01:30
Keybuksure, because you just started a second copy01:30
Keybukbut that's ok01:30
squirrelpimpyes01:30
Keybukdo "start udevtrigger"01:30
Keybuk(rather than the other udev stuff I mentioned)01:30
squirrelpimpsits there doing nothing01:30
squirrelpimpnot returning to shell01:30
Keybukthe udevtrigger doesn't return to the shell?01:31
squirrelpimpno01:31
Keybukyou should be able to ^C it01:31
squirrelpimpi was01:31
Keybukstatus udevtrigger says?01:31
squirrelpimpudevtrigger start/starting01:32
Keybukthat's weird01:32
Keybukps ax | grep udev01:32
Keybukwhat do you see?01:32
squirrelpimpupstart-udev-bridge --daemon, 3 times udevd --daemon, bluetoothd --udev01:33
Keybukok01:33
Keybukif you run "udevadm trigger" what happens?01:33
squirrelpimpreturns to shell01:33
Keybukanything else?01:33
squirrelpimpexited with 001:33
squirrelpimpnothing alse01:33
Keybukok01:33
Keybuksend your mountall SIGTERM now01:33
Keybukand then copy the log out of /dev01:33
Keybukreboot into your live cd, and upload the log somewhere01:34
squirrelpimpSIGTERM to both mountalls?01:34
squirrelpimpi put it on the usbstick01:35
Keybukif you like01:35
squirrelpimphttp://pastebin.com/d3d904e3e01:35
squirrelpimpthere you go01:36
squirrelpimpKeybuk: how does it look to you?01:42
squirrelpimpas it doesn't seem to be mentioned in that file, my /home is encrypted using luks01:43
Keybukright01:45
Keybukit looks like it's waiting for your /home and /boot to show up01:45
squirrelpimpok01:46
Keybukand they haven't01:46
squirrelpimpi can comment /home and encrypted swap as well01:46
squirrelpimpboot is sda1 ext201:46
Keybukcan you run blkid -p /dev/sda1 for me01:46
Keybukand paste the output01:46
squirrelpimpambivalent result (Probably more filesystems on the device)01:47
Keybukeep01:47
Keybukok01:47
Keybukso that's why it's refusing that01:47
KeybukI've no idea about the LUKS stuff01:47
squirrelpimphow can that happen?01:47
Keybukhow does it work? ?p01:47
squirrelpimpthe volumes are configured in /etc/crypttab and setup by /etc/init.d/cryptdisks-early and /etc/init.d/cryptdisks01:48
slangasekKeybuk: using an init script that's not converted over yet01:48
squirrelpimpafter that they are used like regular devices in /dev/mapper01:48
Keybukthat explains it then01:48
slangasekhmm, this is that use case we discussed in the bug :-P01:49
Keybukhuh?01:49
squirrelpimpso will it help to fix the sda1 problem?01:49
Keybuksquirrelpimp: no01:49
slangasekKeybuk: the "you can use cryptsetup in a way that doesn't actually prompt you for a passhprase" :)01:50
slangasek("but why would you want to")01:50
Keybukslangasek: it still should be a udev rule not an init script ;)  I've been telling them that for years01:50
KeybukI thought they were using udev rules01:50
slangasekKeybuk: oh, absolutely01:50
Keybukin fact, I remember writing them01:50
* slangasek shrugs helplessly01:50
squirrelpimpthere goes my encryption01:50
squirrelpimpwhat can i do to prevent the sda1 error ?01:51
Keybuksquirrelpimp: is your /dev/sda1 secretly part of a RAID?01:51
squirrelpimpnope01:51
squirrelpimpit was created during karmic setup and not changed01:51
squirrelpimpkarmic from sept 1001:52
Keybukstrange that it has multiple signatures01:52
squirrelpimpso for now, karmic won't work with encryption? then i'll copy over the files to unencrypted partitions and leave that for now01:53
squirrelpimpif i can fix the sda1 thing01:53
slangasekit should work for encrypted rootfs; just not for encrypted (separate) /usr01:53
Keybuksda1 you can fix the same way, just copy the files elsewhere, mkfs the device again, and copy back01:53
squirrelpimpok, i'll give that a try01:53
squirrelpimpfirst however i should get some sleep.:)01:54
squirrelpimpI'll come back with my findings01:54
squirrelpimpslangasek: so setting up cryptsetup for the whole physical volume will work?01:54
squirrelpimpKeybuk: thanks for all the help. if you happen to be near karlsruhe germany, i'll make you a pizza.01:55
squirrelpimp:)01:56
Keybuksquirrelpimp: thanks for the testing!01:56
slangaseksquirrelpimp: *should*, yes; I haven't tested yet myself (my test comes after the next publisher run)01:56
Keybukslangasek: I'll look into cryptsetup interaction tomorrow02:01
Keybukdo you think we should RN it or fix it?02:01
slangasekKeybuk: fix it02:02
Keybukok02:02
squirrelpimpHEH..02:04
squirrelpimperr02:04
squirrelpimpheh... the rescue-shell failed on me after mkfs.ext4 /dev/sda102:04
squirrelpimpnow it has to wait till tomorrow02:04
squirrelpimpnight02:04
YokoZarIs mpt on vacation?02:12
Keybukion: thought, for physical disks, specified by name, we shouldn't bother with what udev thinks02:14
Keybukif someone puts /dev/sda1 in their fstab, blkid output should be irrelevant?02:14
Keybuk(probably only true for hdX and sdX though)02:14
=== robbiew-afk is now known as robbiew
chrisccoulsonhmmm, it seems that mountall does not like the bindfs mounts i have in my fstab02:22
slangasekKeybuk, lamont: do you know why util-linux is failing to configure as part of the bootstrap in livefs builds? that seems to be the only thing failing presently04:04
robbiewslangasek: I think Keybuk has passed out for the evening ;)04:06
slangasekyeah04:08
slangasekshot in the dark, but it's going to take me a while to sort through without him04:08
TheMusoslangasek: I have a new RT kernel to upload for studio. The mainline rt patch came out overnight, and I've had to do some test building and running today before I can upload it. Unfortunately its an ABI bump due to being against mainline.04:30
TheMusoUnfortunately this is needed, as the current RT kernel doesn't boot which is why we didn't do alpha 5, and I'd prefer to get this in for alpha 6.04:30
=== Amaranth_ is now known as Amaranth
=== robbiew is now known as robbiew-afk
robbiew-afkslangasek: I suppose karmic is now a little happier of a place ;)04:51
ScottKTheMuso: Sounds like the downside risk of updating is low.04:54
TheMusoScottK: My thoughts as well.04:55
lifelessis there a mips/mipsel machine we can log into ?05:00
lifelessfriend of mine writes some audio codec stuff and has a bug report for mipsel, but he can't reproduce etc...05:00
ScottKlifeless: I think NCommander has some.  Dunno if it can be remotely logged into.05:02
lifelessNCommander: ^05:02
lifelessScottK: thanks05:03
StevenKlifeless: mahler.debian.org ? :-)05:03
lifelessdown?05:04
NCommanderlifeless, at the moment is completely dead, I ripped its HDD out for beta testing ;-)05:12
HenryLokehahah05:42
HenryLokedearest ubuntu chat room05:42
HenryLokeneed your guy help me a bit05:42
slangasekTheMuso: yes, please upload; you don't need to clear such things with me before uploading, the studio-specific packages are frozen for your sake, not mine. :)05:52
dholbachgood morning07:10
TheMusoslangasek: More as a heads up, since binary newnig will be required.07:28
squirrelpimpgood morning07:28
slangasekTheMuso: ok - I'll try to keep an eye out for it, but if the binaries show up in the queue while I'm asleep, don't wait for me :)07:34
TheMusoslangasek: ok07:34
pittiGood morning07:35
TheMusoMorning pitti.07:35
pittihey TheMuso07:37
* slangasek waves07:37
squirrelpimpoh, new packages for upstart and mountall again07:38
dholbachjames_w: what do we do about bug 414298?07:58
ubottuLaunchpad bug 414298 in devscripts "Please merge devscripts_2.10.53 from Debian unstable" [Undecided,Confirmed] https://launchpad.net/bugs/41429807:58
slangasekKeybuk, lamont: util-linux sorted08:07
slangasekKeybuk: wrt debhelper, why is it necessary to diverge from Debian and add an update-rc.d -f remove call?  I can't see how that would be necessary unless there's a bug elsewhere, and that sounds like a bug that'll be a blocker for getting Debian changed over once someone stumbles across it08:09
squirrelpimpwell.. i have the exact same behaviour with unencrypted /home and swap08:25
squirrelpimpKeybuk is still sleeping i guess08:25
* slangasek wonders why netbase only recommends: ifupdown, when it ships an init script that doesn't work without it08:25
slangaseksquirrelpimp: what's the behavior you're seeing?08:26
slangasekI think I only caught part of that conversation before08:27
squirrelpimpthe system hangs during startup, on the console i can see the mount of / and then it stops08:28
slangasekhmm, ok08:28
squirrelpimpKeybuk directed me to run mountall --debug and to make a log of that08:28
squirrelpimpthen he figured out, that it was encrypted swap and /home and a wrongly labeled sda1 on /boot, which prevented mountall from succeeding08:29
squirrelpimpi removed swap, /home and recreated sda108:29
slangasekso what does running mountall --debug now do?08:29
squirrelpimpi made another logfile08:30
squirrelpimphttp://pastebin.com/d5232464d08:30
squirrelpimpare the live-cds already built with the new system btw?08:31
squirrelpimpnot yet it seems08:32
squirrelpimpi copied home to a new volume called "home", which is not encrypted08:32
squirrelpimpi also tried commenting swap, home and tmpfs in fstab, so there was only /root (and the other default stuff) left08:32
squirrelpimpagain, no luck08:32
slangasekhmm, the log doesn't give me any insight08:33
slangasekI guess we'll have to wait for keb08:33
squirrelpimpand the behaviour is the same as last night. "start udevtrigger" does not return to the shell08:33
slangasekfor Keybuk, even08:33
squirrelpimpi'm tempted to just reinstall the box from a live-cd as it was a pretty fresh install and i did a backup before running the update in the first place08:34
squirrelpimpso keybuk or livecd, whoever comes first08:35
squirrelpimp:)08:35
slangasekthe liveCD is about 40 minutes out08:35
squirrelpimp+ download and burn it'd 70 minutes to wait08:38
squirrelpimp:)08:38
pittislangasek: FYI, I cleaned up the translation related mess on http://people.canonical.com/~ubuntu-archive/component-mismatches.txt08:38
squirrelpimpslangasek: now the system bootet to some further point, despite the shell.conf in /etc/init/ still being present08:44
squirrelpimphow can i remove that file, if it boots beyond /bin/bash08:44
squirrelpimp?08:44
squirrelpimpah, i can appent init=/bin/bash in grub08:45
squirrelpimpnever mint08:45
\shKeybuk: start on (filesystem and started hal) (your patch on gdm) but hal and not even dbus is started via upstart...hopefully you or someone is working on that ;)08:46
squirrelpimpslangasek: now it startet including X, which presents an error message from libgconf2-4/gconf-sanity-check-2 and tells me, theres an issue with the configuration server08:47
slangasek\sh: sounds to me like you need to upgrade hal and dbus08:52
pittitseliot: do you know why -vmmouse now wants to go back to universe?08:52
slangaseksquirrelpimp: are all your filesystems mounted?08:52
pittitseliot: in the past it was a dependency of -input-all08:52
squirrelpimpyes... i think it might be a wrong mode in /tmp08:52
pittitseliot: is it obsolete now, or was it a merge error?08:52
squirrelpimpi set that to 1777 to be sure and try again08:52
\shslangasek: apt-get update ; apt-get dist-upgrade should be enough, right? it came after the last dist-upgrade...08:53
\shslangasek: this morning I have to mention08:53
slangasek\sh: both hal and dbus are shipping upstart jobs in the current versions08:53
tseliotpitti: I don't think it's obsolete and I have yet to merge it with debian's version08:53
\shslangasek: I had to manually start hal ; start dbus ; start network-manager ; start gdm08:53
pittitseliot: merge error in -input-all, I mean08:54
=== tkamppeter_ is now known as tkamppeter
squirrelpimpok, i have gdm login08:54
\shslangasek: dbus 1.2.16-0ubuntu3 (the latest upload of dbus e.g.) is on the system08:54
tseliotpitti: oh, it could be. Can you file a bug report about that and assign it to me, please?08:55
pittitseliot: will do; but I wasn't sure whether it was a bug, or deliberate08:55
tseliottjaalton: do you know anything about this ^^ ?08:56
\shslangasek: so I checked the last uploads with scotts updates from yesterday, everything has the correct version on the system..so I'm confused now ;)08:56
slangasek\sh: then perhaps I misunderstood what you were saying, because the jobs are certainly there in the packages08:58
squirrelpimpi get "rc main process" stopped/continued lots of times during reboot08:59
squirrelpimpis that expected?08:59
pittitseliot: done, bug 43053209:00
ubottuLaunchpad bug 430532 in xorg "should depend on -vmmouse?" [Undecided,New] https://launchpad.net/bugs/43053209:00
tseliotpitti: thanks09:00
pittitseliot: I'll test it by installing -vmmouse into the live system once today's images land09:01
pittitseliot: i. e. whether it still actually works09:01
tseliotpitti: ok, let me know09:01
\shslangasek: right...but they are not started .. so after reboot (kernel update) I'm on the console...and "start gdm" doesn't work...and after investigating why it's not started, I realized that hal and dbus are not started, too09:04
tjaaltontseliot: it's fixed in git, and according to the changelog entry it should be uploaded already (on 3rd of August)09:05
squirrelpimpslangasek: it seems, that if i put /dev/vg0/home in fstab, it won't work09:05
squirrelpimpbut if i replace it with /dev/mapper/vg0-home it will09:05
tjaaltontseliot: but looks like it wasn't09:06
slangaseksquirrelpimp: ah; possibly because one is the kernel's "true" name for the device, and one is an alias09:08
squirrelpimpmight be09:09
slangasek\sh: which version of mountall do you have installed?09:09
squirrelpimpbut it would be nice if either worked09:09
slangaseksquirrelpimp: yes - but knowing why is the first step :)09:09
slangaseksquirrelpimp: can you file a bug on lvm2 about this, and drop the bug number here?09:10
squirrelpimpsure09:10
squirrelpimpsuspend to disk doesn't work09:10
\shslangasek: 0.1.409:11
slangasek\sh: and that's the version you had when you booted, too?09:12
\shslangasek: yes09:12
slangasekok09:13
* slangasek doesn't have that version here yet; 0.1.3 looks like it DTRT, but I'll keep looking09:13
\shslangasek: thx :)09:13
=== asac_ is now known as asac
squirrelpimpbug number is 43054209:17
squirrelpimpslangasek: should i worry about the "could not read '...z60_hdparm.rules" from udev?09:22
slangaseksquirrelpimp: probably indicates a dangling symlink for some reason, and probably not a big deal09:23
slangasekwarrants a bug report on whatever left the symlink behind09:23
squirrelpimpdpkg can't find any package the symlink belongs to09:25
TheMusoIf someone would kindly let linux-rt's binary packages through binary new, then I can upload the meta, and disks can be built once all this other stuff is sorted.09:25
slangasekTheMuso: grabbing; go ahead with your meta upload09:27
TheMusoslangasek: Thanks.09:27
tjaaltonpitti: the vmmouse fix was in git, but never uploaded. Ok to upload now or wait after a6?09:31
pittitjaalton: better wait, I think09:32
tjaaltonpitti: sure thing09:32
sorenIs Karmic still knackered? Will I spend the rest of the day regretting it if I "apt-get dist-upgrade"?09:33
* ogra wonders if there is any documentation what to do with the new upstart stuff in all the scripts that use chroots to build stuff and call invoke-rc.d and friends09:33
ograi.e. all our virtual things, my ltsp builders and my armel build scripts09:33
ograsoren, did you get any instructions for the transition ?09:33
sorenogra: Nope.09:34
slangaseksoren: karmic is settling; I don't know whether this means you'll regret it09:37
* soren has a reputation of being a bit of a masochist, so probably not.09:38
pittihey, from time to time we just _need_ to be taught how booting really works09:38
pittihow better to find out than having to fix a completely screwed system :)09:38
sorenExactly!09:39
ttxno pain, no gain.09:40
ttx(I used to run Gentoo)09:40
al-maisan_so how does one fix the "Mount point '/dev/(pts|shm)' does not exist. Skipping mount" problem?09:41
cjwatsonslangasek: ah, good, I was just about to poke at util-linux after reading mail ...09:42
sorenttx: Heheh :)09:44
slangasekcjwatson: yah, sorry it took me so many mails to notice the problem :)09:44
cjwatsonyeah, I ignored most of them until timestamps were such that I could no longer put them down to the known bustedness09:45
dholbachal-maisan_: did a dist-upgrade and reboot help with that?09:53
dholbachal-maisan_: I booted with init=/bin/bash and ran   sudo dhclient &   to get me on the net, then dist-upgraded09:53
al-maisan_dholbach: thanks, will try dist-upgrade, I have done a "sudo apt-get upgrade" so far..09:54
al-maisan_dholbach: cool, the machine boots to the linux console login now :)09:58
dholbachal-maisan_: all the best with completely fixing it!09:59
al-maisan_:)10:00
* soren crosses fingers and goes for a reboot10:04
al-maisan_hmm .. now when attempting "restart gdm" I get: "Unable to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory"10:08
cjwatsonI'm told that's a problem with having done a partial upgrade ...10:10
al-maisan_ah10:12
cjwatsonany out of date packages?10:12
\shcjwatson: no it's not10:12
cjwatson\sh: well, slangasek said it was and I normally believe him - do you have evidence to the contrary?10:12
cjwatson(or details)10:12
\shcjwatson: as discussed with slangasek I checked that everything is in place...no updates are missing...and it doesn't work as expected10:13
dholbach\sh: after a complete upgrade I had two working machines again10:13
slangasekwell, I wouldn't have expected that particular error from a partial upgrade10:13
slangasekI would've expected upstart to refuse to start gdm at all?10:13
cjwatsonok, then I don't know; however of course it is possible that not everyone has the same cause for the same symptom10:13
\shdholbach: I dist-upgraded this morning and it didn't work..I just saw that slangasek uploaded new hal and new gdm10:14
slangasek\sh: all those new uploads do is enforce a versioned dependency10:15
slangasekthey won't work any different than a system that was already up-to-date10:15
sebner\sh: I was able to boot (after a fsck/mountall issue -reboot) but with old mountall/upstart from yesterday evening after the builds were working again10:15
\shI realized that problem when I "dpkg-reconfigure kdm" and selected kdm as default xdm ... after that, no mouse, no keyboard (both usb) were working...(btw...dpkg-reconfigure gdm doesn't work anymore)10:16
\shafter manually "start hal ; start dbus ; start network-manager ; start gdm) it was working again10:17
* al-maisan_ sees a "init: dbus pre-start process (nnnn) terminated with status 1" message scrolling by while booting the machine in question..10:17
sebnerslangasek: should it boot already faster btw?10:18
al-maisan_\sh: that manual start command sequence did the trick, thanks!10:20
slangaseksebner: that's not my department :)10:20
dholbachjames_w is reviewing patches and packages in #ubuntu-reviews10:20
al-maisan_oops, not quite, gdm comes up, but the touchpad and the keyboard are dead..10:21
sebnerslangasek: kk, we should be happy if it boots in general ^^10:21
pittial-maisan_: that would be missing hal then10:21
pittial-maisan_: at startup, X reads the input devices from hal, so hal must be running before X starts10:22
al-maisan_pitti: OK.10:22
pittiI haven't checked how the upstartification ensures this dependency (or whether it does at all)10:22
al-maisan_pitti: I did "start hal" manually so it should have been running.10:22
pittial-maisan_: and afterwards started gdm?10:23
pittiit should have worked then indeed10:23
al-maisan_pitti: yes.10:23
slangasekpitti: gdm "start on [...] started hal"10:23
pittial-maisan_: can you check "lshal" for info.capabilities "input.keys" and "input.mouse"?10:23
sebnerpitti: I'm wondering why we are fiddling with hal. So not soo deprecated yet?10:24
slangasekTheMuso: I'm not tracking linux-rt further at the moment; when you want me to roll an ISO, shout10:25
StevenKsebner: Not quite yet10:25
\shslangasek: hal needs started dbus but dbus wasn't started and dbus wasn't started10:25
StevenKsebner: https://wiki.ubuntu.com/Halsectomy10:26
sebnerheh, k10:26
slangasek\sh: not sure what you're responding to; I was simply addressing pitti's dependency question10:26
sebnerStevenK: ah, only GDM remaining, the rest are just applications :)10:27
cjwatson\sh: if dbus isn't getting started, presumably that's the thing to debug?10:27
\shslangasek: s/and dbus wasn't started/and eventually we see something strange happening with dbus?/10:27
pittisebner: most apps switched over, but not X yet10:27
ograpitti, btw do we keep hal in universe once you are done ? so scripts and tools using it donw need to be ported10:27
\shcjwatson: that's what I wanted to say ;)10:27
ogra*don't10:27
pittiogra: oh, of course, as long as there are still rdepends10:27
sebnerpitti: we can keep breaking the archive with switching to wayland if you are feeling bored :D10:28
pittiogra: but I hope we can throw it out of the default install in LL at least for Ubuntu (when X gets ported)10:28
pittiogra: and I heard that they are porting solid as well, so perhaps Kubuntu can drop it soon, too10:28
ograthats fine, i'm just to lazy to port usb-imagewriter :P10:28
pittisebner: heh10:28
lesshastehi.. I have a firefox problem where it freezes when uploading files... The strace at http://pastebin.com/f118d9b2e seems to actually imply it's an X server problem as firefox is waiting for something from the server which never arrives10:29
lesshasteany tips on how to report this usefully?10:29
StevenKsebner: And X.org input detection. Which is somewhat important10:29
StevenKBut only if you care about mouse movement and typing. And who needs those?10:30
lesshastethe important part starts at line 177010:30
ograStevenK, speech input FTW ?10:30
StevenKogra: Absolutely.10:30
StevenKogra: Then IRC gets filled with "um", "er" and "ar" a lot10:31
sebnerStevenK: cards ftw! or you accept my suggestion moving to wayland *hrhr*10:31
ograStevenK, and my neighbors will be annoyed :)10:31
=== PLaYSTatiON is now known as SuBmUnDo__
al-maisan_pitti: I do see various lshal info.capabilities entries that lists input.keyboard, input.keys and input.mouse10:35
* al-maisan_ tries starting gdm again10:35
pittial-maisan_: ok; can you check /var/log/Xorg.0.log for input device errors?10:36
pitti$ grep hal /var/log/Xorg.0.log10:36
pittiI get ~ 10 lines, like10:36
pitti(II) config/hal: Adding input device AT Translated Set 2 keyboard10:36
pitti(II) config/hal: Adding input device Logitech USB-PS/2 Optical Mouse10:36
Laneysoren: did you come back?10:36
al-maisan_pitti: it works now .. for whatever reason .. so after booting to the console I did: start dbus; start hal; start gdm10:37
TheMusoslangasek: Just role them when things are ready to be roled, i.e when preparation of disks for everything starts. I just wanted to get that kernel in.10:42
pittial-maisan_: I guess "started hal" is not enough; hal needs a second or two to detect everything10:42
pittial-maisan_: I guess "start hal; start gdm" fails, but "start hal; sleep 2; start gdm" works?10:42
sorenLaney: Yes. What's up?10:44
Laneysoren: Just checking - I dist-upgraded and didn't come back...10:44
YokoZarpitti: is it possible hal could get held up for a bit and break when 2 seconds aren't enough?10:44
sorenLaney: but.. you're... here..?10:45
Laneylaptop10:45
pittiYokoZar: I think the correct solution would be for hal to emit an upstart signal when it's done detecting10:45
pittiKeybuk: ^10:45
YokoZarpitti: Yeah that was my thought as well10:45
pittiand then the rest (like gdm) can depend on that/10:45
StevenKstart on hal-ready (or something), right?10:45
pittiKeybuk: is there an example how C code would send an upstart signal that gdm etc. could depend on?10:45
YokoZarAnd if hal fails catastrophically and never releases the signal bootup probably should be blocked...10:46
pittiI guess it's just a d-bus call10:46
slangasekTheMuso: my point is I'm /already/ rolling other images, while the linux-rt kernel is (AFAIK) not ready in the archive yet10:51
slangasekhmm. wasn't really /looking/ to reboot just then, but didn't go too badly all things considered10:52
slangasekbut dbus is definitely a problem here as well10:52
ionkeybuk: What do you mean by not caring about what udev thinks? What would we do differently?10:55
al-maisan_pitti: sorry, was in a phone conversation, yes, there was a pause between "start hal" and "start gdm" since I was doing the lshal checks and queries.10:56
ionogra: Dear aunt, let's set so double the killer delete select all.10:56
al-maisan_pitti re. the /var/log/Xorg.0.log input device errors: I get these as well.10:57
pittial-maisan_: errors?10:57
pittitjaalton: oh, in fact current live systems do have a working "vmmouse" like behaviour; so perhaps -vmmouse is indeed obsolete?10:58
pittitjaalton: oops, ignore me; that was my workaround with "-usb -usbdevice tablet"10:59
tjaaltonpitti: evdev works for the most part, but it doesn't feel "integrated" like with vmmouse, AIUI11:00
al-maisan_pitti: http://pastebin.com/m16b6a3de11:00
pittitjaalton: yes, it works with clicking/releasing the lock11:00
slangasekdoes upstart log things anywhere/11:02
cdE|Woozysometimes kms is failing on intel with the latest updates. it seems that drm is loading before agpgart-intel was loaded: http://pastebin.ubuntu.com/271986/11:02
slangasektjaalton: what's the best way to force modes for a VGA device that's not passing EDID?11:02
pittial-maisan_: hm, if it doesn't work with that, it's out of my knowledge, I'm afraid11:03
al-maisan_pitti: sorry for not being clear enough .. everything works fine after issuing the manual start command sequence from the console. Thank you very much for helping me out!11:07
pittial-maisan_: ok, you're welcome11:07
=== al-maisan_ is now known as al-maisan
slangasekal-maisan, \sh: bug #43061111:10
ubottuLaunchpad bug 430611 in dbus "dbus fails to start on clean boot using upstart job" [Undecided,New] https://launchpad.net/bugs/43061111:10
al-maisanslangasek: thanks!11:13
cjwatsondefinitely a messy startup, but it does at least work for me ...11:14
\shslangasek: bingo :)11:15
cjwatsonpeople having dbus start problems: do you by any chance have /var on a separate filesystem?11:20
cjwatsonjust a hunch, could be wrong11:20
\shcjwatson: nope11:21
slangasekcjwatson: yes11:21
cjwatsondrat11:21
slangasekoh, wait11:21
slangasekno11:21
\shslangasek: do you have also some strange udev messages in /var/log/syslog like udevd[3227]: NAME="%k" is superfluous and breaks kernel supplied names, please remove it from /lib/udev/rules.d/40-ppc.rules:311:21
cjwatsonI was wondering about the pre-start script11:21
slangasekI do have cryptsetup11:21
cjwatson\sh: everybody has those, but they're fairly harmless11:21
cjwatsonfor the moment anyway11:21
\shcjwatson: ok...I never saw them before...so I'm curious :)11:22
cjwatsonit's a new warning in the new upstream release of udev that hasn't been handled in all the rules yet11:22
cjwatsonmentioned in the changelog, even ...11:22
slangasekspeaking of warnings, upstart-job and I are going to be having words11:23
cjwatsonthe whine if you use invoke-rc.d?11:23
slangasekyes11:24
cjwatson\sh: what does 'dbus-uuidgen --ensure; echo $?' say, run as root?11:24
ior3kdo these dbus problems happen only on boot time? Or everytime?11:24
slangasekand the improper emulation of init script "start" - it can obviously do its own darn status check to make the invocation a no-op11:24
slangasekior3k: what other time is there?11:24
\shcjwatson: 011:24
cjwatsonoh well11:25
slangasekior3k: it's a problem with dbus not starting - boot time is about it :)11:25
ior3kslangasek: I mean, dbus may not start on boot, but start manually afterwards11:25
al-maisancjwatson: I do have /var on a separate partition11:25
slangasekior3k: no, it is possible to start it by hand11:25
\shcjwatson: I have to revert my answer to "/var on a separate partition" the correct answer is "yes" and actually it wasn't mounted11:26
ior3kslangasek: is it possible to rig the dbus init script with strace?11:26
ior3kslangasek: would that help debugging?11:26
slangasekior3k: I don't know if it would; since upstart does service supervising, running it under strace changes the parameters11:27
slangasek(not my first choice for debugging something in early boot, but someone can try it if no other fixes present themselves...)11:28
cjwatsonI wonder if mountall needs to emit a special event to say that /var/run has been mounted11:28
cjwatsonor if it would be ok to have dbus 'start on local-filesystems' rather than virtual-filesystems11:29
slangasekwhere are those signals defined?11:30
cjwatsonas in documentation, or as in code?11:30
slangasekdocumentation11:30
cjwatsonthey're emitted by C code in mountall ...11:30
cjwatsonslangasek: *hollow laugh*11:30
squirrelpimpthe mute-button on the thinkpad stopped to work after the last round of updates11:30
squirrelpimpthere are lots of bugreport related to the mute button, but it worked as expected before the updates so i'm note sure against which packge to file the bug11:31
slangasekI wonder whether this is connected to my inability to rebuild mountall due to testsuite failures11:31
slangasekoh, wait11:31
slangasekI need to suppress dh_auto_test :P11:31
squirrelpimpnever mind, i found a workaround11:32
cjwatsonslangasek: that's always reassuring11:32
tjaaltonslangasek: https://wiki.ubuntu.com/X/Config/Resolution has some optional ways to force the resolution11:36
cjwatson/var/run *should* be considered virtual, though11:36
cjwatsonoh, /var/lib/dbus/machine-id11:38
cjwatsonslangasek: try 'start on local-filesystems' in the dbus job?11:39
slangasekcjwatson: in my case that's on the rootfs, though; and dbus-uuidgen appears to only open it for reading11:56
slangasekcjwatson: OTOH, I do have */usr* on a separate partition11:57
slangasekso yeah, I'll test11:58
slangasek(testing with local-filesystems; if that fixes it, is that the right signal to use?  What if /usr is on NFS?)11:59
cjwatsonit's not obvious is it12:00
cjwatsonreally, we ought to make dbus work when only virtual filesystems are available12:02
cjwatsonespecially with upstart depending on it12:02
cjwatsonor quasi-depending anyway12:02
=== MacSlow is now known as MacSlow|lunch
slangasekcjwatson: hah - well, that makes a difference, at least...12:11
slangasekcjwatson: I did another test boot w/o changing first, and I get "dbus died w/ 127, respawn"12:11
slangasekcjwatson: then I changed it to local-filesystems... and I get no attempt to start dbus at all12:11
slangasekbecause mountall never emits the signal, AFAICS12:12
cjwatsonwuh12:12
cjwatson        if ((! local_triggered) && (num_local_mounted == num_local)) {12:12
cjwatson                nih_info ("local finished");12:13
cjwatson                emit_event ("local-filesystems");12:13
slangasekdoes it track noauto filesystems sanely?12:14
slangasekalso: bwuh, what decided to rewrite my fstab yesterday and put UUIDs in place of my already-unique lvm names12:15
cjwatsonit's supposed to, see cleanup12:15
pittimeh, /etc/init/gdm.conf doesn't check for "text" any more12:15
cjwatsonI wonder about remount handling though12:15
cjwatsonmaybe arrange for mountall to run with --debug?12:16
slangasekwhere does it debug to?12:17
slangasekpitti: "text"?12:18
cjwatsonsyslog, if daemonised12:18
slangasekal-maisan: would you be able to help with testing this further?12:20
slangasek4am here, brain not worky12:20
al-maisanslangasek: yes, sure.12:20
* al-maisan fetches the other laptop from the living room12:21
slangasekI can probably do one more test here, but black BIOS screen is making me sleepy12:22
al-maisanslangasek: what package do I need to upgrade in order to perform the test?12:24
davmor2slangasek: sleep they'll be a re-spin12:24
cjwatsonal-maisan: up-to-date everything, edit /etc/init/mountall.conf to add --debug to mountall's command-line parameters, reboot, look in syslog12:24
al-maisancjwatson: thanks12:25
cjwatsonKeybuk: so, for converting the ubiquity init script to upstart - how do I arrange for gdm to *not* start until ubiquity has completed?12:30
cjwatsonKeybuk: also, how do I say "start once service foo has started, but if service foo is not present on the system then don't worry about it"?12:38
* cjwatson wonders how the current set of upstart jobs handle the case where a package is removed but not purged12:42
slangasekcjwatson: aha - ldd /bin/dbus-daemon | grep /usr12:43
al-maisancjwatson: here's the syslog excerpt: http://pastebin.com/m72c830db12:43
cjwatsonslangasek: ah - ok, I can deal with that12:44
slangasekand the reason for not emitting the signal here is that I have a filesystem referenced as /dev/VG/LV syntax instead of /dev/mapper/VG-LV, which isn't getting handled12:45
cjwatsonhmm, nothing from mountall in that syslog12:45
cjwatson(phone)12:45
slangasekI expect the signal will be emitted for people not having that particular problem12:45
slangasekok, sleeping now12:47
slangasek'night12:47
al-maisanslangasek: good night.12:47
al-maisancjwatson: I did add '--debug' after 'exec mountall' in /etc/init/mountall.conf12:48
al-maisanI think there was some extra output but it scrolled by too fast on the console .. sorry12:48
al-maisanShift-PageUp does not work12:50
=== krusaf|bnc is now known as krusaf
=== MacSlow|lunch is now known as MacSlow
cjwatsonKeybuk,lamont: udev successfully built on powerpc now13:13
Keybukoh, neat13:13
lamont\o/13:16
ograKeybuk, is there any documentation how to transition stuff that uses chroots and VMs and invokes initscripts or calls invoke-rc.d to the new model ?13:21
ogra(i have various tools and scripts that will need chnages i guess ... i.e. ltsp, rootstock etc)13:21
kagouhello13:22
ograand i guess our vitual builder tools might need to see some changes too13:22
Keybukupstart doesn't work with chroots13:22
ograbut in vm's i guess13:23
Keybukthis is one main reason I haven't changed anything that you _can_ run in a chroot13:23
ograi.e. in rootstock i fire up a VM after a first stage bootstrap to call the second stage and install whaever the user selected... in this vm i only fire up the bare minimum of initscripts to just make the vm work enough for the task ...13:24
ograis there a way to have something like a "minimal profile" upstart could use in that case13:25
=== abms1116 is now known as binitamshah
ograstgraber, ^^^ the above will massively affect ltsp13:34
dokohmm, boot is somewhat broken: init: sreadahead main process () terminated with status 1, and system hangs13:36
ogradoko, you didnt upgrade today, did you ?13:37
directhexdoko, /topic13:37
dokoogra: I did13:37
ograouch13:37
pittidoko: does it really hang forever? mine just powers down display, and gdm eventually appears after a second13:39
dokopitti: now hangs for 5min13:39
pittiok, so that's not that then13:39
pittierm, s/after a second/after a minute/, of course13:39
lamontcjwatson/Keybuk: does karmic need/want the change for debian bug 546834?  is it even an issue for karmic+1?13:40
ubottuDebian bug 546834 in debootstrap "debootstrap fails when invoked from lh_build" [Grave,Open] http://bugs.debian.org/54683413:40
dokomessages before that are: "Begin: Running /scripts/init-bottom ..." and "Done."13:40
Keybuklamont: shouldn't think so, we don't use insserv13:40
lamontyay13:41
Keybukdoko: try with --debug13:41
dokoKeybuk: as kernel option?13:42
dpmdut13:47
Keybukdoko: yes13:48
lamontKeybuk: and I pulled your branch and pushed my tree.  how much / which of -1ubuntu2 do I need to pull over to debian?13:49
Keybuklamont: which was -1ubuntu2 ?13:50
KeybukI wouldn't pull any of the upstart stuff for now13:50
Keybukyou may want the versionsort() patch though13:50
lamontok.  there was also a "newer glibc" prototype change13:50
lamontah.13:50
lamontyeah that13:50
sebnerKeybuk: can the boot considered faster now after all the bunch of updates?13:50
Keybukbut then that didn't even look like it was used at all13:50
lamontand does that work with older glibc too?  (as in sid?)13:50
Keybuksebner: it seems to depend13:50
Keybuksebner: for me, X comes up 7s faster13:51
Keybukbut for other people, X doesn't come up at all ;)13:51
Keybukand on some HDD-based machines, it's exactly the same speed13:51
Keybuk*but*, and here's the important thing, if this model does work13:51
Keybukit puts us in a better place for karmic+113:51
Keybukbecause this was the "hard change"13:51
sebnerKeybuk: kk, here it seems to be same speed13:52
Keybuksebner: do you have before/after bootcharts ?13:52
sebnerKeybuk: sure but the bootchart from this morning might not be useful since I didn't get all of the updates. I installed some others after the builds worked again (mountall manually from LP), this even booted up ^^13:54
KeybukI mean of your boot before any of the updates13:55
dokoKeybuk: anything special to look for?13:56
sebnerKeybuk: sure, sec13:56
Keybukdoko: can you take a picture and send it me ? :)13:56
Keybukdoko: otherwise the last virtual 4/5 line is useful13:56
dokoKeybuk: ok13:56
ionkeybuk: What do you mean by not caring about what udev thinks? What would we do differently?13:58
sebnerKeybuk: the updates started yesterday right?13:58
Keybukion: mountall checks that ID_FS_USAGE=filesystem13:58
Keybukion: so if there's multiple meta-data in the block device, it ignores it13:59
Keybukion: for "simple" block devices, that's not really necessary13:59
stgraberogra: yeah, I'll need to do some real testing quite soon14:00
mterryIn MainInclusionReportTemplate, there's the sentence "Who is the package bug contact in Ubuntu? (Needs one if its a nontrivial package which does not fully maintain itself through Debian)".  Can we scratch the parenthetical?  Seems like we always want a bug contact14:00
stgraberogra: as soon as my laptop starts working again ;)14:00
cjwatsonmterry: the parenthesis is there for a reason, and should be left in14:00
ograstgraber, i guess we have to drop all the rc.d script mangling14:00
sebnerKeybuk: http://img147.imageshack.us/i/ubuntukarmic200909151.png/  , the day before this log it booted with 39 sec's though. A clean jaunty install boots in 18 secs though. Using karmic since the beginning14:01
mterrycjwatson, that's what I was asking for.  I just couldn't think of a situation where we'd want bug reports being filed that never get looked at14:01
ograstgraber, and i dont know what ltsp-client-setup and ltsp-client-core initscripts have to look like in the new worldorder, but i guess Keybuk can help with them14:01
Keybuksebner: err is this chart the "before" or "after" ?14:01
ionkeybuk: Wouldn’t that mean writing additional special-case code? Now we have a single code path that works for everything. Isn’t that better?14:01
cjwatsonmterry: we'd always *like* a bug contact, but it's not mandatory for main inclusion if the package is trivial and maintained well in Debian14:01
Keybukogra: just leave them as they are?14:01
sebnerKeybuk: should be before14:01
Keybukion: no, just a change to the "if" statement in the udev watcher14:01
ograKeybuk, if they work :)14:01
Keybuksebner: ok, that looks like a before14:01
sebnerheh14:02
* ion looks at the code14:02
sebnerKeybuk: do you also want the "half-upgraded" bootchart from today?14:02
mterrycjwatson, k..14:02
Keybuksebner: if you like14:03
ionSo, if the device name is [hs]d[a-z][1-9], skip the get_property_value stuff?14:03
cjwatsonKeybuk: oh, speaking of which, shouldn't you subscribe to bug mail for mountall? :)14:03
Keybukion: just skip the usage check14:03
Keybukcjwatson: yes14:03
cjwatsonmterry: basically, it's a bug if nobody's subscribed, but not all bugs are critical14:03
sebnerKeybuk: http://img11.imageshack.us/i/ubuntukarmic200909161.png/14:04
Keybuksebner: ok, and the full upgrade chart?14:04
mterrycjwatson, yar.  I've just been influenced by jorge's exhortations to fill those gaps  :)14:04
sebnerKeybuk: haven't rebootet yet14:05
Keybuksebner: coward14:05
sebnerKeybuk: :P14:05
ionkeybuk: I might be missing something, but the usage check doesn’t look very expensive.14:05
ionJust a couple of strcmps14:05
Keybukion: it's not the expense14:05
Keybukion: it's the problem when someone has "/dev/sda1 /boot ext3 defaults 0 2"14:06
Keybukbut blkid can't tell what filesystem is in /boot14:06
Keybuk"multiple results returned" kinda thing14:06
Keybukmountall won't mount it14:06
Keybukeven though it doesn't *really* need to check ID_FS_USAGE, because /dev/sda1 doesn't have "change" events14:06
ionAh, ok14:06
sebnerKeybuk: I'll reboot and if it breaks I'll hunt you :P14:06
Keybuk(we check that because mdX and dmX *do* change, and need to be repeatedly checked until they contain a valid filesystem)14:06
Keybuksebner: take a ticket, join the queue ;)14:07
ionI see14:07
sebnerKeybuk: does that mean that it'll surely break? :P14:07
ionHow about when UUID or LABEL is used and they mean sda1?14:07
Keybuksebner: WFM :)14:07
pittiKeybuk: is it normal/expected that at shutdown I see a series of "rc init SIGSTOP", "sreadahead SIGSTOP", "rc init SIGCONT", "sreadahead SIGCONT"?14:08
Keybukion: then obviously for those we check usage ;)14:08
Keybukpitti: yeah14:08
pittiok14:08
Keybukpitti: sendsigs has been doing that weird shit for a while14:08
sebnerKeybuk: no uplash, loads of udev warnings, but takes longer but it booted up :P14:12
Laneyis the archive stable yet?14:12
* Laney is wondering what the best way to recover is14:13
=== rickspencer3-afk is now known as rickspencer3
sebnerLaney: rockstable :D14:14
Laneyin terms of uploads/publishing14:14
sebnerLaney: the builds are back to normal too afaik14:15
sebnerKeybuk: http://img406.imageshack.us/i/ubuntukarmic200909162.png/14:15
Laneymainly I want to get my system back up ¬_¬14:15
Laneychroot + dist-upgrade?14:15
Keybuksebner: wait a minute for sreadhead to go away (status sreadahead)14:15
Keybukshould say stop/waiting14:16
Keybukthen reboot again14:16
sebnerLaney: yeah14:16
sebnerKeybuk: rebooting14:17
ograKeybuk, fyi, armel imx51 (babbage) still boots fine :)14:17
ograi see a udev message on boot though, but i think that was mentioned here before14:18
ogra("symlink" in a udev rule)14:18
Keybukright14:18
Keybukwe're testing udev GIT HEAD14:18
Keybukkay and I will do a release next week when we're in Portland14:18
ograwell, as long as it works i dont care14:19
ograi'm just sad i cant hide the messages behind a splash atm :P14:19
cjwatsonKeybuk: what's the best way to ask users to get debug information out of mountall? edit /etc/init/mountall.conf and add --debug?14:20
Keybukcjwatson: yes14:20
sebnerKeybuk: http://img193.imageshack.us/i/ubuntukarmic200909163.png/14:21
Keybuksebner: odd, you have a dead sreadahead as well14:22
sebnerKeybuk: that means?14:23
=== marjomercado is now known as marjo
Keybukdon't know yet14:24
sebnerKeybuk: as my system boots this doesn't mean it's purely bad. :P14:27
doko-netbookKeybuk, http://people.canonical.com/~doko/tmp/IMG_0892.JPG14:27
ion40314:27
cjwatsonKeybuk: any reason mountall doesn't just do nih_log_set_logger more or less up top if it's going to daemonise? it'd make debugging rather easier ...14:29
Keybukcjwatson: wouldn't make any difference, surely?14:30
cjwatsonit'd arrange for all the stuff from new_mount, cleanup, etc. to go to syslog14:30
cjwatsonwhich is before daemonisation14:30
ionI wonder if rsyslog could be easily patched so that it could be started before a writable anything, and it would buffer stuff until it can dump them to syslog et al?14:30
ionSimilarly to logsave from e2fsprogs14:31
kagouwith 20090916 daily-live amd64, I install system, but at reboot -> screnn go black and system freeze :( To wich package I report the bug ? Or should I wait for tommorrow iso ?14:31
kagoubug came clearly from new boot system14:32
Keybukcjwatson: except syslog isn't running ;)14:32
cjwatsonKeybuk: oh, heh14:32
Keybukcjwatson: which is why you normally send all that to stderr before you daemonise ;)14:32
cjwatsonfair enough14:33
Keybukion: that's the plan for Upstart itself14:33
Keybukjust buffer stdout/stderr of processes14:34
ionPerhaps a command to dump the rsyslog buffer to stdout, so you could less(1) the so-far logged stuff even before it has been able to save them.14:34
Keybukthen, if they fail, toss the log somewhere useful14:34
Keybukkinda like cron does14:34
ograKeybuk, oh ... http://www.mirror.co.uk/news/technology/2009/08/28/sharp-netwalker-the-future-of-netbooks-115875-21631914/ ... "Sharp reckon that the Ubuntu OS should be able to boot in under 3 seconds"14:34
ionAlright14:34
Keybukapache failed, *and here's what it said*14:34
ograKeybuk, and you still test with a dell mini, tsk14:34
Keybukogra: only if you use a different display engine than X14:34
ograi think its X on framebuffer14:35
ogralike the babbage14:35
Keybukyeah, never going to be 3s then ;)14:35
* Keybuk will dance on X's grave when we get a proper display engine14:35
ograbut their marketing said so, it *must* be true :P14:36
cjwatsonand the Mirror, no less a well-regarded publication filled with superb journalistic standards14:37
sebnerKeybuk: wayland!14:37
ograheh14:37
Keybuksebner: we played with wayland a while back14:37
Keybukdoko: still 40314:37
sebnerKeybuk: really, when? too earler stage I suppose?14:37
Keybuksebner: you can get Dell Mini to boot in 3s with that14:37
sebnerO_o14:37
sebnerwant have!14:38
KeybukI can make an Ubuntu Appliance boot in 1s14:38
Keybukit's just not very interesting14:38
ionBut you can ping localhost!14:38
Keybuk(a device with a hardwired kernel, and a framebuffer, that launches a single framebuffer application)14:38
Keybukbut that's all you need for a tomtom or something14:38
ograwhich you dont boot anyway14:39
ograonly once or if power runs out14:39
ograthe rest of the time you only suspend14:39
ScottKTomTom takes longer than that to start.  Maybe they need lessons.14:40
ograstart or resume ?14:40
sebnerScottK: ahh! pssst or Keybuk gets bought by TomTom!14:40
dokoKeybuk: fixed14:41
ScottKogra: Start.14:41
ogramy gps takes about three minutes to boot (its wince based though) but is instant on/off for suspend/resume14:41
ScottKsuspend/resume is ~2 or 3 seconds.14:41
Keybukogra: of course you boot them14:42
loic-mmvo_: how does one gets an app translated description + screenshot in so they get shown in software-store?14:42
ograonce14:42
Keybukwhy would you suspend a satnav?14:42
mvo_loic-m: screenshot> not at all at this point14:43
ScottKKeybuk: I assume the on/off button does suspend/resume.  It certainly isn't shutdown/start.14:43
Keybukdoko: that's quite odd14:43
loic-mmvo_: you mean this point in Karmic dev cycle, or they're not handled by s-s?14:43
ograKeybuk, mine survives a week if its suspended ... and in car it's attached to the cigarette lighter and recharges ... why would i shut it down ?14:43
mvo_loic-m: translation> via ddtp and the app-install-data template14:43
ScottKdoko: Is there any reason not to make celementtree go away now?14:44
mvo_loic-m: screenshots can not be localized in the karmic cycle14:44
Keybukdoko: that's very odd14:44
dokoScottK: go ahead!14:44
ScottKOK.  I can work on that.14:44
Keybukdoko: it looks like udev isn't running14:44
Keybukdoko: could you add an /etc/init/shell.conf with something like "start on startup" "console owner" "exec /bin/bash" and boot with that14:45
Keybukthat'll give you a shell to do some debugging with14:45
loic-mmvo_: sorry, for the screenshot I wasn't thinking about localised one, but about including one for app where it's missing14:45
mvo_loic-m: oh, sorry. I misunderstood. that can be done via screenshots.debian.net14:45
mvo_loic-m: before the final release we need to move that to scrrenshots.ubuntu.com though14:46
mvo_(but that may be just a re-direct)14:46
loic-mmvo_: and if the app isn't in Debian?14:46
mvo_loic-m: that is not possible right now, I hope to get this resolved in time14:48
mvo_loic-m: but currently we rely on the debian service here, also christop haas expressed willingness to help us14:49
loic-mmvo_: for ddtp, that means translating through launchpad, doesn't it? No way to just include it in the package? And does it work for packages in universe?14:50
mvo_loic-m: for ddtp there is no way to include it in the package itself. it does work for universe, if it does not, let me know, then there is a bug in the code somewhere. but it does for the cases I looked at14:50
loic-mmvo_: Ok. It's just that going through launchpad means you need to hope the locale team ever validates it, which can never happen, and is a shame when you're also upstream translator14:52
dokoKeybuk: is this config file picked up automatically?14:52
mvo_loic-m: oh, hm :( that is bad. there is a way by going via ddtp.debian.net14:52
mvo_loic-m: but that requires review as well, not sure how quickly tha thappens14:53
ogradoko, upstart reads the stuff in /etc/init14:53
dokoahh, it is14:53
mvo_loic-m: is there anything in LP that we can do to make it smoother?14:53
dokoKeybuk: yes, hal is not running14:54
Keybukdoko: yes14:54
Keybukdoko: hal should not be running yet14:54
loic-mmvo_: not sure what you can do. Best would be a way to get this from upstream package, or untill it's possible to grab the email of upstream translator and let him translate ;)14:54
Keybukdoko: could you join #ubuntu-boot, it's too noisy in here14:54
mvo_loic-m: I proposed a new design for this to translations.launchpad.net so that the package descriptio nwould be put alongside the regular translation as a additional pot file. this way the same permission would apply as for the upstream translation. but unfrotunately it did not get implemented (yet?)14:57
loic-mmvo_: didn't know that. Can't find the link, do you have it by any chance?15:02
=== robbiew-afk is now known as robbiew
mvo_loic-m: https://blueprints.launchpad.net/rosetta/+spec/native-package-descriptions-support15:07
loic-mmvo_: thanks a lot, I'll follow it. Best would be a freedesktop thing so upstreams just include a general description in the list of files gettext/whatever proccesses.15:09
cjwatsonWTF, +filebug redirects to help.ubuntu.com?15:10
cjwatsondamnit, there are some cases where ubuntu-bug is no use at all15:10
cjwatsonstupid stupid stupid15:10
james_w+filebug?no-redirect15:11
cjwatsonthanks15:11
* cjwatson smart-bookmarks since obviously the UI has decided that helpfulness is for other people15:11
pitticjwatson: hm, where? I still used +filebug this noon on edge15:12
cjwatsonon edge just now15:13
cjwatsonhttps://edge.launchpad.net/ubuntu/+source/mountall/+filebug15:13
Laneythere was a mail about it to u-d-d but I thought it was just for "Ubuntu"15:22
ogralol15:23
ograKeybuk missed to remove usplash on usplash_down15:23
AnAntI don't understand Keybuk's dh_installinit changes (that was mentioned in last foundations report)15:25
nixternalany idea on what I have to do in order to get my machines with encrypted drives up and running?15:27
al-maisannixternal: that's fairly vague question :)15:44
nixternalnot if you are running karmic it isn't15:44
al-maisannixternal: OK, so.15:46
* ogra humps Keybuk's leg15:58
ograKeybuk, i have never seen a babbage board boot that fast !15:58
ograKeybuk, though dbus crashed on first boot15:58
robbiewlol16:00
ograit works wonderful on second16:00
robbiewogra: does bootchart work on babbage boards?16:02
robbiewwould be cool to see it16:02
kirklandKeybuk: the avahi-daemon upstart job isn't starting the daemon on the alpha6 server16:03
ograits running since 10min16:03
ogragenerating the image is very slow16:03
robbiewah, right16:03
kirklandKeybuk: this is causing the UEC node installs to not detect the cloud-controller on the network16:03
kirklandKeybuk: how do i go about debugging this?16:03
kirklandKeybuk: or is it a known issue?16:03
kirklandKeybuk: actually, i can't get avahi-daemon to start at all, even manually16:10
kirklandKeybuk: the upstart job throws a PID back at me16:10
kirklandKeybuk: but it's gone by the time i look at ps16:10
kirklandKeybuk: and there's no daemon running16:10
ograrobbiew, Keybuk http://people.canonical.com/~ogra/babbage2-karmic-20090916-2.png (down from 90sec)16:12
Keybukogra: you have the strange exe16:13
Keybukogra: if you reboot it again, do you get down to 38s?16:13
ograno, i got from 54 to 45 already16:13
ograand as i said, very first boot after install crashed dbus16:13
ograand i dont have the right keymap atm16:14
ograKeybuk, GEEZ ! http://people.canonical.com/~ogra/babbage2-karmic-20090916-3.png16:22
ograyou are right, it gets faster with every boot16:22
Keybukogra: you *still* have that strange exe though ;)16:25
* Keybuk has no idea what that is16:25
Keybukdon't suppose you have the .tgz from that latest bootchart16:25
ograi have all three :)16:26
Keybukcould you mail me the latest one16:26
ograsure16:26
ograKeybuk, on its way16:28
kirklandKeybuk: hmm, i see a new avahi upload since the last iso spin; i'm upgrading to that now16:28
cagontoonline boxing game http://www.kobox.org/kobox-fande-Nourine.html16:29
Keybukthat looks like a link to my INBOX16:29
kirklandKeybuk: hmm, that seems to have fixed that problem16:29
cjwatson\sh: can you upgrade to current libexpat1 and dbus and see if that fixes things for you?16:34
kirklandcjwatson: i'm installing a UEC node...  it's trying to fetch the node-preseed file by ipv6 address;  is that expected?16:35
cjwatsonal-maisan: ^-16:35
cjwatsonkirkland: I don't know16:35
kirklandcjwatson: okay, thanks.16:35
cjwatsonkirkland: in my last test the cloud controller was only listening on IPv6; I adapted some things to cope, but didn't investigate why16:35
kirklandcjwatson: hmm, my -cc is definitely listening on ipv416:36
mterryKeybuk, so I lied, rsyslog should handle HUPs, but I don't think the current /etc/init.d/rsyslog handles reloads.  It handles restarts...16:36
keesKeybuk: apparmor needs to start much sooner (it's starting after avahi, for example)16:37
al-maisancjwatson: will do.16:37
Keybukkees: we need to work out apparmor16:38
keesKeybuk: same for urandom, looks like it's started after network services that might be using the seed16:39
Keybukshall we look at apparmor next week?16:40
Keybukwe can work it out in person then16:40
keesKeybuk: yes please.  :)16:40
KeybukI think I have something in mind that's quite elegant, but want to make sure it works for you16:40
pittiogasawara: bug 193970 is back (seems this breaks again with each and every release); given its size, should I rather open a new bug or reopen this one?16:42
ubottuLaunchpad bug 193970 in linux "iwl3945 | iwl4965: Wireless can't be activated after disabling kill switch" [Medium,Fix released] https://launchpad.net/bugs/19397016:42
al-maisancjwatson: yep, my machine boots perfectly now!16:42
ogasawarapitti: lets open a new one to minimize the noise16:44
pittiogasawara: ok16:44
pittiogasawara: what should I do to put it back on the radar? is "regression-potential" enough?16:45
pittiogasawara: I guess the old patch still applies, but keeps getting dropped or so..16:45
keesKeybuk: whatcha thinkin'?16:45
ogasawarapitti: yup tag it "regression-potential" and also let me know the bug # and I'll get it on our list16:45
Keybukkees: I'm assuming that you have two groups of apparmor profiles16:45
Keybukprofiles for particular services16:45
Keybukand generic profiles16:46
keeskind of16:46
Keybukfor the generic, we need something that loads them like the init scripts16:46
Keybukbut for service profiles, we could so something clever16:46
Keybuk  start on starting16:46
Keybuk  exec [ -f /etc/apparmor.d/init/$JOB ] && load_ze_profile16:46
Keybukthat way, if you dropped anything in that directory that had the same name as a service in /etc/init16:46
Keybukit would be automatically loaded *before* that service16:46
Keybukif you added an /etc/apparmor.d/init/sreadahead, then it's automatically used, etc.16:47
Keybukmaybe it's not how things work16:47
Keybukbut it's a nice idea if it is16:47
keesinstead of an "init" subdirectory, why not just look for the daemon name?16:47
Keybukthat would work too16:47
superm1pitti, re bug 193970, are you using the dell-laptop kernel module?16:47
ubottuLaunchpad bug 193970 in linux "iwl3945 | iwl4965: Wireless can't be activated after disabling kill switch" [Medium,Fix released] https://launchpad.net/bugs/19397016:47
Keybukthough all you have with "starting" is the $JOB name (filename under /etc/init without the dir or .conf)16:48
pittisuperm1: apparenlty16:48
keesi.e. sreadahead is /sbin/sreadahead, so  exec [ -f /etc/apparmor.d/sbin.sreadahead ] && load_ze_profile16:48
keesKeybuk: hrm16:48
keesKeybuk: I see your point, and an init script could contain all kinds of things to confine16:49
superm1pitti, mjg59 needs to write a patch that inserts an input filter to intercept a keypress of XF86WLAN in dell-laptop kernel module to be able to update dell-laptop's rfkill status16:49
* kees ponders16:49
superm1(he hasn't yet)16:49
pittisuperm1: hm, how did that work before?16:49
superm1pitti, dell-laptop was introduced in karmicish kernels16:50
superm1it's not worked perfectly since introduced because of this deficiency16:50
Keybukkees: right16:50
superm1any other problems with <karmic were different16:50
ScottKLovely.16:51
cjwatsonal-maisan: excellent16:51
keespitti: any thoughts on bug 422392 ?  This will be needed for security update handling too.16:52
ubottuLaunchpad bug 422392 in devicekit-disks "devicekit-disks (and devicekit-power) need to be stopped when new package is installed" [Medium,Confirmed] https://launchpad.net/bugs/42239216:52
pittisuperm1: ah, thanks; I added that info to the bug report16:54
pittiogasawara: it's bug 430809 now, but seems it's not just reapplying the old patch then :-(16:54
ubottuLaunchpad bug 430809 in linux "[Dell Latitude D430, iwl3945] Wireless can't be activated after disabling kill switch" [Undecided,New] https://launchpad.net/bugs/43080916:54
pittikees: looking16:55
superm1pitti, mjg59 said two or three days ago when i pinged him that it's "On his list", but he said that two weeks ago when i pinged him too :(16:55
pittikees: I agree; incidentally, I already did that some days ago in dk-power :)16:55
nixternalKeybuk: need any testing help with the latest changes and encrypted drives? they seem to be the only issue I am facing now with the new upstart stuff16:56
Keybuknixternal: cryptsetup needs to be ported to use udev rather than an init script16:57
nixternalgroovy, so you are all good then16:57
keespitti: oh good!16:58
pittikees: if that's really the cause for bug 403192, you deserve a big big hug :)16:58
ubottuLaunchpad bug 403192 in devicekit-disks "update-notifier crashed with SIGSEGV in gdu_pool_get_devices()" [High,Confirmed] https://launchpad.net/bugs/40319216:59
keespitti: well, it's absolutely the cause of it continuing to crash even after it was fixed.  :)16:59
pittikees: I keep forgetting that some people never reboot ;)16:59
kees(where "absolutely" is defined by "totally went away after I restarted dk-disks)16:59
keespitti: heh16:59
keesspeaking of never rebooting, I'm now going to reboot with my shiny new keybuk-ified boot process...17:06
ccheneyogra: ping17:07
dokoKeybuk: start udev does start, then I get hundreds of messages "UNEXPECTED INCONSISTENCY, Superblock last mount time is in the future". after that I can't enter anything, did the fsck, started udev, and gdm did come up17:08
ccheneyogra: i wonder if the new version of boost could possibly be causing the problem with arm on karmic17:10
ccheneyogra: boost in jaunty is 1.35 but is 1.38 in karmic, perhaps using 1.35 might help with a karmic build?17:10
ccheneyogra: unfortunately 1.35 is not in the archive for karmic but is still in jaunty so maybe could be tested by pulling it from there, if you are doing a manual build17:12
=== yofel_ is now known as yofel
keeshmpf, my resolv.conf was empty.17:13
ScottKccheney: We switched to 1.38 right after UDS, so I doubt it's causing anything new.17:13
mathiazcr3: hey - planning another upload of checkbox before alpha6?17:14
ccheneyScottK: i don't know how long OOo has been busted on arm though17:15
keesKeybuk: so, usplash didn't work, and xsplash didn't work.  how do I fix/debug ?17:15
* ScottK nods.17:16
ccheneyScottK: its not used all that much so unless the mobile team does regular testing it might still be that17:16
ccheneyScottK: and afaik the only dist that uses/tests arm much is us17:16
ccheneyScottK: debian has an arm port but i don't know if anyone actually uses OOo on it17:16
\shkees: I read your blog article about removal of sun-java6 ;) one question: does openjdk have already the security manager of sun-java{5,6} (used e.g by tomcat{5,6})?17:17
kees\sh: dunno -- I think so.17:17
ScottKccheney: Also we got some new patches ~recently.17:17
kees\sh: I don't know how to test it, but I imagine it would stand out if it was missing17:17
\shkees: afaik it doesn't because of some strange licensing issues of sun...I could be wrong, but that's why most people use sun-java6 and tomcat6 app server17:17
ionRemoval of sun-java6, huh? A certain major (...ly sucking) Finnish bank seems to require sun-java6 for their web bank interface, openjdk doesn’t seem to work there.17:18
ccheneyScottK: new patches to boost?17:18
keesion: no worries, I suspect sun-java6 will (unfortunately) be staying17:18
cjwatsonKeybuk: would you mind if I turned usplash on for live CDs?17:19
\shkees: easy testing: vi /etc/default/tomcat6 -> TOMCAT6_SECURITY=yes, if openjdk has this feature, tomcat6 will start, if not it will break horribly and won't start up properly;)17:19
cjwatsonKeybuk: or do you actively prefer it off at the moment?17:19
ScottKccheney: It's a month ago, but a lot more recent than when we switched to it (in May): https://launchpad.net/ubuntu/karmic/+source/boost1.38/1.38.0-6ubuntu317:19
ccheneyScottK: ok17:19
ccheneyScottK: thanks for the pointers, hopefully that will be what caused the problem17:21
kees\sh: yes, tomcat6 loads with TOMCAT6_SECURITY=yes and openjdk-617:26
slangasekcjwatson: fwiw, I tried to turn usplash back on for cryptsetup, and it didn't take; I was going to investigate in a little bit17:26
cjwatsonslangasek: ok, I'll do other more productive things then17:29
jdstrandkees: iirc, and I am no expert on this, but I thought all the security manager stuff was resolved when they released openjdk. ie, that and a few other things were blockers on it being open and functional17:29
jdstrandcertainly by the time we started using it...17:30
keesjdstrand: yeah, that's what I thought too, so \sh's test just confirms that.17:30
sivanghi all17:33
sivangI want to get a dell notebook, it uses intel gma 950 - will it work with future version of ubuntu other then the one preloaded by dell ?17:33
sivangis it an open source driver ?17:33
sivangsorry for the noise, question been answered in #ubuntu17:39
Keybukcjwatson: I think it can go on for live cds17:50
Keybukcjwatson: assuming you've tested mountall and it doesn't hang on them ;)17:50
nixternalnote to those with encrypted drives: once you get to the shell using the shell.conf you can do '/etc/init.d/cryptdisks start' to get where you need to go :)17:51
nixternalif that hasn't been mentioned yet of course17:52
nixternalKeybuk: could I add 'exec /etc/init.d/cryptdisks start' or such to my shell.conf file to automatically continue on instead of having to do it manually?17:57
Keybuknixternal: I'm thinking that a short-term solution would be to simply start "cryptdisks" on stopped udevtrigger17:59
Keybukit wouldn't fix bugs where you had encrypted disks that took longer than a udevsettle to appear17:59
Keybukor encrypted lookback files on NFS17:59
Keybukbut they never worked before anyway17:59
Keybuk(whereas unencrypted versions of the above, which didn't work before, now *do* work)17:59
* nixternal needs to read up on upstart18:00
nixternalI have to say, good work dude under this pressure :)  almost there, and a bit faster too18:00
Keybukthe "bit" seems to vary wildly18:01
Keybukit's 7s faster on the reference hardware18:01
nixternalhehe, true18:02
Keybuksomething ridiculous like 45s faster on ogra's ARM board18:02
nixternalit is quite a bit faster, noticeably on my netbook, but I never ran bootchart on it previously18:02
Keybukbut exactly the same speed on my Dell laptop18:02
ScottKnixternal: Luckily you've got the reference system.18:03
* ScottK recently hit reboot (also on the 10v) and looked over to see how it was going and was suprised to the the login dialogue staring at me)18:04
nixternalya, same here18:04
nixternalI keep rebooting just to see it go fast :)18:04
robbiew:)18:05
nixternalrobbiew: hey, I heard my buddy Yosi's kid and yours go to the same school down there in Austin18:06
nixternalguess your license plate caught his attention :)18:06
jdstrandKeybuk: hi. I feel like I am missing somthing very obvious. is there a wiki page on the proper way to convert from sysv initscript to upstart?18:07
ScottKit would be handy if an archive admin with shell access could look at 364630 and sync libchamplain and pyclutter.  They are tied up in a bit of a transitional mess in Universe.18:07
Keybukjdstrand: no, no wiki page18:07
ScottKjdstrand: You have to crawl into Keybuk's head to find out.18:07
cjwatsonjdstrand: 'man 5 init' might help18:07
nixternalhehe...18:07
Keybukalso man 7 {start,stop}{ing,ed}18:08
=== Yasumoto_ is now known as Yasumoto
jdstrandcjwatson, Keybuk: cool, thanks :)18:08
robbiewnixternal: ;)18:08
Keybukjdstrand: files in packaging are named debian/<package>.upstart18:10
Keybukand installed by dh_installinit18:10
jdstrandexcellent, thanks18:10
cjwatsonScottK: will do when I can get mass-sync.py to stop hating me18:15
ScottKcjwatson: Thanks.18:16
keespitti: in one you used killall, in the other you used pidof + kill.  any reason?18:34
pittikees: for some reason yet unknown to me, killall /usr/lib/devicekit-disks/devkit-disks-daemon fails for me half of the time18:35
jdstrandKeybuk: is 'started on net-device-up lo' a valid way to start something after the loopback device is brought up?18:35
keesoh, ew18:35
pittikees: killall devkit-disks-daemon works, but that's too imprecise for my taste18:35
pittikees: I'll change dk-p to use the same18:35
keespitti: yeah18:35
Keybukjdstrand: it should work18:36
jdstrandKeybuk: really, I just want to start something before networking is started. I looked at networking.conf and network-interfaces.conf and it wasn't immediately apparent how I would want to do it...18:36
jdstrandKeybuk: if that'll work, I'll give it a go then18:37
ccheneyis linux smart enough to not schedule on a ht virtual core if there are idle real cores?18:40
Keybukwhat do you want to start before networking?18:40
jdstrandKeybuk: the firewall18:40
Keybukwhy not just:18:40
* ccheney is trying to decide whether to buy a i5 750 or i7 860, hopefully will help build OOo much faster18:41
Keybuk  start on starting network-interface or starting networking ?18:41
Keybukbut put the stuff to bring the firewall up in pre-start and down in post-stop18:41
Keybukso that "firewall" is up when the rules are loaded18:41
Keybukotherwise it'll get run every time an interface comes up18:41
jdstrandKeybuk: I was thinking about that, but thought network-interface might make it more than I want it to. and wasn't sure that networking was enough18:42
Keybukdepends18:42
Keybuknetwork-interface is each ordinary interface18:42
Keybuknetworking is there because I'm a coward18:43
KeybukI don't think we *need* networking anymore18:43
Keybukifup -a should be a no-op18:43
Keybukas either the interface was brought up by udev18:43
Keybukor the underlying device doesn't exist, so can't be brought up anyway18:43
jdstrandKeybuk: actually, it wouldn't be horribly bad if the start ran slightly more often than desired for corner cases, the 'start' I would use is smart enough to not do anything if the firewall is already started18:45
jdstrandI'll try 'start on starting network-interface or starting networking' then18:45
Keybukit would be bad18:45
Keybukit's expensive18:45
davmor2ccheney: foolish mortal it doesn't speed anything up honest ;)18:46
Keybukhaving lo, eth0 and eth1 is not a corner-case, it's the common case :p18:46
jdstrandKeybuk: that was why I initially thought I wanted to do this after 'lo' came up only18:46
jdstrandKeybuk: is IFACE available to me?18:47
ccheneydavmor2: heh18:48
cjwatsonScottK: done - there's a messy bug in mass-sync.py, I just hacked around it for the moment since I'm out of time18:48
ScottKcjwatson: Thank you.18:49
sorenKeybuk: We don't need the networking job? Do we have new ways to deal with bridges, bonded interfaces, and other "virtual" interfaces?18:53
=== rickspencer3 is now known as rickspencer3-afk
cjwatsonkirkland: is Etienne's comment in bug 430820 about setting eth0 to manual correct?18:55
ubottuLaunchpad bug 430820 in eucalyptus "eucalyptus node install results in broken /etc/network/interfaces" [High,Triaged] https://launchpad.net/bugs/43082018:55
cjwatsonit feels surprising to me18:55
Keybuksoren: they still have entries in /sys/class/net18:56
kirklandcjwatson: i didn't have to do that18:56
sorenKeybuk: I do believe the logic we used to have is horrible. bonded interfaces should be configured when the last of the slave interfaces is configured. Bridges could be created immediately and the related interfaces could get added when they turn up..18:56
kirklandcjwatson: my routing table looks okay18:56
sorenKeybuk: Yes, when they get configured?18:56
kirklandcjwatson: and seems to work, moreover18:56
Keybuksoren: right, I think you're following me though18:56
kirklandcjwatson: well, work meaning my nc get's a dhcp address18:56
Keybukwe should do them on the tail of other interfaces, not in one big drop18:56
sorenKeybuk: Pray tell :)18:56
sorenKeybuk: Oh, yes, indeed.18:57
Keybukif you bond eth0 and eth1, then you should do that when you have eth0 and eth118:57
cjwatsonkirkland: I've asked Etienne to file a separate bug for that, then18:57
sorenKeybuk: I'm just not sure why you think we're there?18:57
sorenKeybuk: Precisely.18:57
kirklandsoren: cjwatson: i have a fix for eucalyptus-cc init script18:57
kirklandcjwatson: did you do the netstat check for the cloud being up?18:57
cjwatsonI wrote it, yes18:57
Keybuksoren: I think we have everything we need to do that18:57
cjwatsonit's a hack of epic proportions18:57
KeybukI'm just not going to change that too :p18:57
kirklandcjwatson: http://paste.ubuntu.com/272265/18:57
kirklandcjwatson: can you take a quick look at the init script portion of that patch18:58
sorenKeybuk: We have the tools, but not the actual scripts... Right? Or do you have something up your sleeve that I don't know about? :)18:58
kirklandcjwatson: i don't think your counter was working18:58
Keybuksoren: right, exactly18:58
sorenKeybuk: Ok.18:58
sorenKeybuk: I would loooove to get that fixed for Karmic+1.18:58
sorenKeybuk: It's been bugging me for ages.18:58
kirklandcjwatson: also, eucalyptus upstream asked for some logic to make sure that a cloud-controller is actually expected on this system18:59
cjwatsonkirkland: oh, that's just because I didn't check it18:59
kirklandcjwatson: hence the -x cehck18:59
sorenKeybuk: I just didn't realise you'd be doing the whole networking thing from upstart, but it makes perfect sense.18:59
cjwatsonkirkland: instead of the if, how about '&& [ "$i" != 0 ]'? :-)18:59
cjwatsonkirkland: upstream weren't reading very closely, then ;-)18:59
cjwatson        if [ ! -e /usr/share/eucalyptus/eucalyptus-cloud-@EUCA_VERSION@.jar ]; then19:00
cjwatson                return # no cloud here19:00
cjwatsonkirkland: further up in the same function19:00
cjwatson        fi19:00
sorenKeybuk: That will also make iscsi a much happier place. Ooh, I can't wait. :)19:00
kirklandcjwatson: ah, i missed that too19:00
cjwatsonkirkland: I think: http://paste.ubuntu.com/272279/19:00
kirklandcjwatson: that looks good by me19:01
kirklandcjwatson: let me test it here19:01
cjwatsoncommitted, as I think that has to be an improvement19:02
cjwatsonand I have to run :)19:02
cjwatsonshould we try to get a new version of eucalyptus into alpha 6?19:02
cjwatsonif so it'll need to be very very soon19:02
kirklandcjwatson: i think so19:03
kirklandsoren: are you planning to roll a new eucalyptus for alpha6?19:04
kirklandsoren: if so, see cjwatson's comment about "very soon" ^19:04
sorenkirkland: I /could/.19:04
LaneyAnyone want to help debug my unbootable system? http://orangesquash.org.uk/~laney/noboot.jpg :)19:06
Laneydid dist-upgrade already19:07
kirklandcjwatson: actually, the network bridging isn't quite right yet ...  i'm debugging19:08
cjwatsonkirkland: ok, if you could fix it when you figure it out then I'd appreciate it - I have to run now19:09
ionlaney: First of all, did you boot without the quiet parameter?19:09
kirklandcjwatson: sure thing19:09
Laneyion: sure did19:09
kirklandcjwatson: i think we're just missing an auto br019:09
KeybukLaney: looks like you're using tux on ice or something?19:10
LaneyI have no idea what that is19:10
Laneymy root partition is on mdadm19:10
ionlaney: ls -l /dev/disk/by-uuid, see what /dev entry the UUID printed on the ‘mounting ... failed’ line points to, run mount /dev/THAT /root. Any output other than ‘...failed: Device or resource busy’? Run dmesg. Anything interesting?19:10
Keybukion: it's probably busy because the kernel things it's resuming maybe ?19:10
Keybukoh, no, different UUID19:10
Keybukignore me19:10
cjwatsonkirkland: makes sense19:10
cjwatsonkirkland: that was in the documentation I was working from, so just a slip on my part19:11
kirklandcjwatson: okay, i can fix it19:11
kirklandcjwatson: goes in that udeb postinst?19:11
kirklandcjwatson: if not, just give me a pointer19:11
LaneySo it seems to be trying to boot from /dev/sda1 instead of /dev/md0p119:11
sorenkirkland: http://bazaar.launchpad.net/~ubuntu-core-dev/eucalyptus/ubuntu/revision/552 you can just create them like that? Really?19:12
LaneyI see "Starting manual resume from disk" in dmesg, too19:12
Laneyion: ^19:12
KeybukLaney: can you run "blkid" from there19:12
cjwatsonkirkland: not the postinst, debian/eucalyptus-udeb.finish-install, setup_bridge_device19:12
Laneyit did bring up the array just fine19:12
Keybukand get a photo of the output19:12
LaneyKeybuk: oh, sure19:12
sorenkirkland: Well... You should probably fix up the permissions, but I mean... They will work as block devices?19:12
Laneymd0p1 and sda1 have the same UUID19:12
kirklandsoren: dude, you asked me to add changelog entries, no?\19:12
Laneyand then there's sda5 and md0p5 which are also the same (swap)19:13
kirklandsoren: oh!  you mean create loop devices :-)19:13
sorenI... did..?19:13
KeybukLaney: yeah19:13
cjwatsonsoren: no reason they shouldn't - and yes, should be mknod -m66019:13
Laneyone second19:13
Keybuknow if you look in /dev/disk/by-uuid where do they point?19:13
sorenand chgrp disk.19:13
kirklandsoren: i thought you were griping at me about creating an unreleased eucalyptus changelog :-)19:13
cjwatsonyes19:13
sorenkirkland: Nono, dude, I do that all the time :)19:13
kirklandsoren: yeah, kernel guys said our kernel is configured with loop=0, which means that 8 will be created by default, more can be created in userspace19:14
cjwatsonkirkland: oh, I think you need to do $(($LOOP_SUG - 1) not $((LOOP_SUG - 1) - there have been shell bugs about the latter19:14
kirklandsoren: otherwise, if it's >=0, then the limit is fixed, can only be overridden with kernel boot options19:14
cjwatsondash at least used to fail to handle the latter as specified by POSIX19:14
sorencjwatson: Well... the loop driver in the kernel allocates a bunch of structures for the 8 loop devices it starts out with. I didn't notice any code to automatically allocate more, but I didn't look that closely.19:14
LaneyKeybuk: http://orangesquash.org.uk/~laney/noboot2.jpg ... looks right?19:14
kirklandcjwatson: thanks, i just saw your $(($i-1)) and had to go test your way to believe you :-)19:14
cjwatsonsoren: I'm fairly sure from past memories that you can just create them19:14
kirklandcjwatson: and then second-guessed my way19:14
sorenOh...19:15
cjwatsonkirkland: yeah, that habit has a reasson behind it :)19:15
cjwatson-s19:15
kirklandsoren: i created them here, worked like a champ19:15
sorenkirkland: Right, I may have only looked at the !=0 code path.19:15
KeybukLaney: in that it's exactly wrong, yes19:15
kirklandsoren: though cjwatson is right about the perms19:15
Laneyhah19:15
kirklandcjwatson: i'll fix those two things now19:15
cjwatsonwell, soren pointed them out first19:15
jdstrandKeybuk: can you peek at http://paste.ubuntu.com/272290/ and let me know if I am going down the right path? this is my first upstart script19:15
sorenkirkland: And ownership.19:15
Laneybug or user error?19:15
sorenkirkland: (group should be disk)19:16
Keybukjdstrand: don't think you want "6" in the stop on19:16
kirklandsoren: btw, should we go ahead and define CLOUD_PORT=8773 in eucalyptus.conf?19:16
sorenkirkland: I really have no opinion on that subject.19:16
kirklandsoren: as that's used in a couple of places now in the init scripts, though perhaps not yet universally supported19:16
jdstrandKeybuk: no. that was intentional. it should not be brought down on restart19:16
cjwatsoncoo, didn't know that upstart scripts were automatically set -e. nice.19:16
Keybukjdstrand: but brought down on halt and entering single user mode?19:17
sorenkirkland: If that fixes something for you, sure.19:17
kirklandsoren: k19:17
cjwatsonKeybuk: BTW the documentation isn't entirely clear on whether -e is used for {pre,post}-{start,stop} script as well as plain script19:17
jdstrandKeybuk: well, single-user yes, halt no. I should add 019:17
Keybukcjwatson: oh, it is ;)19:17
Keybukjdstrand: ok19:17
Keybukjdstrand: you're also missing "end script" after each of the script blocks19:17
Keybukjdstrand: and style says the /lib/ufw/... line should be preceeded by exec19:18
Keybukjdstrand: also, what's with the [ "$IFACE" = "lo" ] bit?19:18
Keybukjdstrand: if you only want to do this on loopback, just do "start on net-device-up IFACE=lo"19:18
cjwatsonKeybuk: I can read it either way, I think :)19:18
Keybukjdstrand: and that should be "start on" not "started on"19:18
Keybukjdstrand: oh, and style: description "Uncomplicated firewall"19:18
jdstrandKeybuk: was not aware of net-device-up IFACE=lo syntax. will adjust19:18
jdstrandKeybuk: ufw-init is a shell script, does that matter wrt style and exec?19:19
ionkeybuk: Interesting. I ran blkid on a jaunty system. I have ext2 on md127 on sd{a,b}1. I also have lvm on md126 on sd{a,b}3. blkid printed the identical UUID="foo" TYPE="ext2" for each of sda1, sdb1 and md127. It printed UUID="bar", TYPE="mdraid" for sd{a,b}3 and UUID="baz", TYPE="lvm2pv" for m126.19:19
Keybukjdstrand: it means that the pid stays the same19:19
Keybukjdstrand: saves you a fork()19:19
Keybuk(and ptrace overhead)19:19
jdstrandKeybuk: ok, will change and test. thanks for the feedback!19:20
Keybukjdstrand: though the comment looks good19:20
Keybukjdstrand: nothing to review in that19:20
Keybuk(having just realised he said something about every single other line)19:21
jdstrandheheh19:21
ionkeybuk: Is it just good luck that /dev/disk/by-uuid/33a915c6-874d-4d17-8de5-02afb786480e points to /dev/md127 here and not /dev/sda1 or /dev/sdb1? :-)19:22
Keybukcjwatson: everything is -e because not using -e kills kittens19:22
jdstrandactually, I think the 'pre-start script' lines and the whitespace was ok...19:22
* Laney bounces19:22
Keybukjdstrand: yes, good whitespace!19:22
jdstrand\o/19:22
* jdstrand strives for good whitespace over everything else19:23
sorenion: md*127*?!? Seriously? Are md0-md126 all in use?19:23
kirklandsoren: okay, mknod fixes pushed19:23
kirklandsoren: using $LOOP_SUG as cjwatson suggested, chowning root:disk, and perm'd 66019:23
kirklandsoren: whoops, push failed, divergence19:24
sorenWhere'd you push it?19:24
sorenah.19:24
sorenYeah, that's me :)19:24
kirklandsoren: uno momento19:24
sorenSure.19:24
ionsoren: When creating the array, i experimented with some mdadm parameter for array name, hoping it would create device names like md-foo. Instead, it gave them numbers beginning from 127 and going down. I didn’t feel like recreating the arrays just to get the numbers lower. :-P19:24
cjwatsonKeybuk: oh, I quite agree19:25
Laneyso who's bug is this? and can I get out of it?19:25
KeybukLaney: unsure19:25
Keybukit's either a blkid bug19:25
Keybukor a udev bug19:25
Laneyhappy to help debug19:26
sorenKeybuk: Did you follow the conversation above about automatically created loop devices?19:26
Keybuksoren: nope19:26
sorenKeybuk: Ok.19:26
sorenKeybuk: Short version: The kernel creates 8 of them on boot, but you can just mknod more of them, and the driver handles allocating the kernel structs and all that jazz.. Is there a way to make udev set the right permissions for them?19:27
kirklandsoren: okay, let me fix the network bridging issue ...19:28
sorenKeybuk: Right now we're mknod'ing them, followed by mknod and chmod, which obviously will not follow changes made in the udev rules.19:28
sorenEr... followed by chgrp and chmod. Not mknod again, obviously.19:29
Keybuksoren: yeah, loop is broken19:29
sorenKeybuk: Heheh :)19:29
Keybuksoren: it should be some kind of /dev/pts-a-like19:29
Keybukor /dev/loopctl19:30
Keybukso you ask for a new one, a kobject appears, and then udev can create the node19:30
sorenYeah.19:30
nixternaldon't call it /dev/nixternal, as it may disappear from time-to-time :p19:30
Keybuknow devtmpfs has gone mainstream, people may actually care19:30
kirklandsoren: okay, pushed /etc/network/interfaces fix too19:30
* hunger had a really strange problem, making it impossible to boot jaunty today.19:31
* Keybuk tries to isolate the electrical/plastic burning smell in his office19:31
ionkeybuk: blkid output with some structure added for clarity: http://pastebin.ca/156867219:31
hungerSomehow I ended up with a partition that the system considers to be LUKS encrypted even though it is not. Yesterday that was no problem, after installing the updates boot broke this morning due to this.19:32
hungerSo if somebody else is seeing boot problems after yesterdays round of updates, it might be worth your while to check your partitions for LUKS encryption:-)19:33
sorenkirkland: How do you update the changelog?19:33
kirklandsoren: dch -e19:34
pochupitti: hey, I've reported Debian #546967, in case you are interested19:34
ubottuDebian bug 546967 in wnpp "RFP: media-player-info -- media player identification files" [Wishlist,Open] http://bugs.debian.org/54696719:34
sorenkirkland: Ah, that explains.19:34
kirklandsoren: as opposed to ...?19:34
kirklandsoren: you're looking at the timestamp/signature that gets updated?19:35
Keybukion: can you join #udev and debug with kzak/kay19:35
sorenkirkland: If you just use "dch 'whatever you want in the changelog'", dch will handle breaking lines and all that stuff.19:35
kirklandsoren: ah19:35
sorenkirkland: Yes, the timestamp thing caught my attention :)19:35
sorenkirkland: dch called like I just said will not touch the timestamp.19:35
kirklandsoren: okay, i'll use that when touching your packages :-)19:35
sorenkirkland: Ta :)19:35
sorenSo, are we all happy with this revision?19:36
kirklandsoren: did you clear the mknod hack with Keybuk ?19:36
kirklandsoren: what was the outcome of that?19:36
sorenkirkland: I think the conclusion was that loop is broken.19:36
slangasekmknod?? <gibber, gibber>19:36
kirklandsoren: okay, then i'm fine with it, several bugs fixed, better than before :-)19:37
kirklandsoren: i pushed rev 55719:37
Keybukkirkland, soren: what was the hack19:37
kirklandsoren: for the record19:37
sorenslangasek: It turns out to be a well documented feature of the loop driver :)19:37
* Keybuk has put out the fire19:37
e-jat_anyone know how to solve this bug 42836519:37
ubottuLaunchpad bug 428365 in ubuntu "Karmic Koala Alpha 5. Desktop does not start, freezes the boot screen" [Undecided,New] https://launchpad.net/bugs/42836519:37
sorenKeybuk: We were hoping you'd provide the hack.19:37
ionkeybuk: What was it? :-)19:37
Keybukion: the US four-gang19:38
KeybukI think it's given up19:38
Keybukit had little flames and everything19:38
sorenslangasek: If you need more loop devices, you just mknod them, and the driver does some magic. We need more loop devices, so we mknod them.19:38
sorenKeybuk: That's /usually/ a sign of giving up.19:38
ionkeybuk: Parse error19:38
slangaseksoren: I'm putting my fingers in my ears and wandering back over to the alpha 6 zone19:40
Keybukuh19:40
Keybukfire started again19:40
Keybukbrb19:40
sorenslangasek: See you there..19:40
Keybukand put out again19:41
* Keybuk has unplugged the gang this time19:41
Keybuk(and put it outside, away from the expensive computers and expensive humans)19:41
nixternalhaha, you are working so hard you are starting fires..that is just scary :)19:41
kirklandsoren: actually, i missed a bug number in the changelog19:42
kirklandsoren: if you want to add 43082019:42
sorenkirkland: Naughty, naughty.19:42
sorenkirkland: Can you do it yourself?19:42
kirklandsoren: doing...19:42
Keybuknixternal: you know you're having a bad day, when ...19:42
mathiazkirkland: could you also add bug 425926?19:43
ubottuLaunchpad bug 425926 in eucalyptus "Eucalyptus 'Store' tab requires appliance store proxy package " [Medium,Triaged] https://launchpad.net/bugs/42592619:43
nixternalhehe19:43
Keybukunfortunately I now have a Michael McIntyre sketch going through my head19:43
mathiazkirkland: to my changelog entry19:43
kirklandsoren: pushed 55819:43
KeybukWhoah-oh, my sex^Wnetbook is on fire!19:43
kirklandmathiaz: sure19:43
mathiazkirkland: I've discovered the bug after I had pushed/merged my branch19:43
sorenkirkland: ta.19:44
kirkland  [ Mathias Gug ]19:44
kirkland  * Recommend python-image-store-proxy for eucalyptus-cloud. The Image Store19:44
kirkland    feature won't work without it, LP: #42592619:44
nixternalthe netbook, the netbook, the netbook is on fire, we don't need no water let the lil bastard burn!19:44
kirklandmathiaz: soren: done, pushed19:47
sorenkirkland: I'll do a test build and upload if it looks decent.19:48
kirklandsoren: thanks, let me know if you want some more testing too19:48
nurmihi all; I was hoping that we might have a quick discussion regarding the Eucalyptus init scripts19:49
sorencjwatson: Did you leave?19:49
kirklandnurmi: sure, shoot19:49
kirklandmathiaz: connectivity issues?19:49
slangaseksoren: he did19:49
sorenDarn it.19:50
mathiazkirkland: well - my X server crashed - but I was using byobu to run irssi19:50
nurmikirkland: i've been trying out the latest package, and found one issue regarding the ordering of installation/init script starting19:50
nurmibug here: 43084119:50
sorenbug 43084119:50
ubottuLaunchpad bug 430841 in eucalyptus "after package install of eucalyptus-cloud, walrus, sc, only cloud service is loaded" [Undecided,New] https://launchpad.net/bugs/43084119:50
mathiazkirkland: however I'm using a the notitication command to send highlights to my desktop, which uses dbus19:51
slytherinwhat all information is needed when filing a bug against pulseaudio?19:51
mathiazkirkland: and the dbus session went away when X crashed and I restarted my gnome session - reconnecting to the existing screen session failed to pick up the dbus session19:51
Treenaksslytherin, doesn't "ubuntu-bug pulseaudio" supply everything now?19:52
nurmisoren: ah, cool :).  I put in a few possible solutions that in the report, but wanted to chat about whether you have other ideas/concerns19:52
kirklandmathiaz: byobu/irssi should have kept you connected, no?19:52
mathiazkirkland: probably the same issue as the ssh-agent socket when you login/logout in  machine and reconnect to an existing machine19:52
slytherinTreenaks: I haven't tried19:52
mathiazkirkland: yes - it kept me connected - but it was using the old dbus session19:52
* Treenaks wonders why his scroll lock led has started blinking 19:52
kirklandmathiaz: hrm, sounds similar to the ssh-agent issue19:53
mathiazkirkland: so highlights would not get sent to my desktop - instead I have an error message printed in my irssi window19:53
mathiazkirkland: which is very annoying19:53
sorenHmm...19:55
sorennurmi: I wonder if upstart would be helpful here at all.19:55
sorennurmi: Or just make matters even more complicated.19:56
nurmisoren: i'm not familiar with upstart, what is the basic idea?19:56
kirklandnurmi: event-based service startup19:56
nurminurmi: oh, right, spaced on the name.19:57
* nurmi talks to himself19:57
nurmisoren: can the event be 'file is in place'?19:57
sorenI'm not sure, to be honest. This is all very, very new to me as well.19:58
sorennurmi: Keybuk knows.19:58
ionnurmi: File notification based events are in TODO, but not with very high priority.19:59
nurmiion: i see, what type of events are currently supported?19:59
kirklandnurmi: soren: Keybuk has spoken to me before about inotify-driven upstart; i don't think we have that in karmic, though20:00
* kirkland could be wrong, however20:00
Keybukno, not yet20:01
Keybukit's on the TODO20:01
ionJust a handful of events sent by Upstart itself (‘startup’, ‘control-alt-delete’ etc.), the starting/started/stopping/stopped events for jobs and anything emitted by system scripts. And perhaps something else i forget.20:01
sorennurmi: This is only a problem at package install time, though, right?20:01
nurmisoren: correct20:01
nurmiion: i see, thanks; i'm also reading about upstart now, very cool :)20:02
nurmisoren: what do you think about the idea of installing the service files as '.disabled' by default?20:02
ttxsoren: any progress on alpha6 image generation ?20:02
nurmisoren: this would ensure that when init scripts 'start' the first time, the service will be loaded20:03
sorennurmi: Where are these service files located?20:03
sorenttx: The UEC images?20:03
ttxsoren: yes20:03
sorenttx: http://uec-images.ubuntu.com/karmic/2009091620:03
sorenttx: With MD5SUMS, manifests and everything.20:03
nurmisoren: /usr/share/eucalyptus/20:04
ttxsoren: they don't show up on the test tracker20:04
sorennurmi: Ungh... Modifying anything in there is not kosher.20:04
sorenttx: Ah.20:04
sorensmoser: Can you take care of that?20:04
nurmisoren: there may be another option, although I havn't tested it much20:05
sorennurmi: Pray tell :)20:05
nurmisoren: each of the eucalyptus-cloud/walrus/sc init scripts ultimately ends up calling '/usr/sbin/eucalyptus-cloud'20:05
nurmisoren: that program is the bootloader for any webservice that exists in /usr/share/eucalyptus20:06
smosercan i take care of what ?20:06
sorensmoser: Make the UEC images turn up in the test tracker.20:06
nurmisoren: the command itself takes disable arguments, for example: --disable-cloud, --disable-walrus, --disable-sc20:06
smoserum.. i can try. do we think its reasonable to believe that these could turn into alpha-6 ?20:06
sorensmoser: We will only know by testing them :)20:06
nurmisoren: so that, even if the service file exists, one can 'disable' it using these options20:07
ttxsmoser: unless we test them, we'll never know20:07
smoserthats not true20:07
sorenbrb20:07
smoserwe can no that they will not be alpha-6 if we know of major issues in the packages they contain20:07
smoserthats what i was asking, if there were any known issues as of an hour ago or so in the archive that would prevent it20:07
ttxsmoser: even in that case, it's good to know if there weren't any other issue, which the tests would unearth20:08
slangaseksmoser: none in the general case20:08
ttxsmoser: respins should be triggered by test failures on the tracker anyway20:08
smoserhow do i add these things ?20:08
smoserto the tracker ?20:08
ttxso it's always good to do it :)20:09
ttxsmoser: if I knew, I wouldn't ask.20:09
=== cprov is now known as cprov-afk
smoserslangasek, ?20:09
slangaseksmoser: you tell me or stgraber what you have available for testing that you want on the tracker20:09
smoserslangasek, http://uec-images.ubuntu.com/karmic/20090916/20:10
ttxsmoser: was this image bundled/uploaded to EC2 ?20:10
smoserand, slangasek i'm in the process of what ttx is asking20:10
slangasekack20:10
slangasekwhoo manifests20:10
ttxand MD5SUMS :)20:10
slangasekare you hand-generating this md5sums file?20:10
smoserso i'll bother you with the ami's later today20:11
smoserslangasek, md5 is part of the tools now20:11
slangasekttx, smoser: there are scripts to do md5sums generation and sign them; we should use those (but blocked on an RT to let our users share files)20:11
slytherinTreenaks: ubuntu-bug helped a lot. :-)20:11
slangaseksmoser: please don't reinvent the wheel here, we should reuse the cdimage toolkit we already have20:11
smoserbut i like inventing wheels20:12
slangasek(yes, md5sum is a very small wheel - but sign-cdimage is less of one)20:12
ttxsmoser: square ones ?20:12
smoserno, but seriously,  i didn't know. i agree, i'll use whatever is available20:12
slangaseksmoser: hmm, let me bounce you the relevant emails then; I thought you'd been cc:ed20:12
smoserslangasek, point me at it and we'll do that for beta20:12
slangaseksmoser: /home/vmbuilder/cdimage20:13
slangasek<handwave>20:13
slangasekemail to follow :)20:13
slangaseksmoser: you were cc:ed on the mail; Message-ID: <20090916005543.GB8869@dario.dodds.net>20:13
smoserok. i'll dig.20:13
LaneyKeybuk: please let me know if you isolate a fix... wouldn't mind a bootable system again20:14
slangasekif you need me to resend, let me know20:14
KeybukLaney: I wouldn't expect me to isolate your fix until at least next week20:14
Keybukit's unrelated to the init transition20:14
Laneyok20:14
Keybukyou could temporarily work around it by booting with root=/dev/md0p120:14
* Laney nods20:15
sorennurmi: Why not just have one init script?20:18
kirklandcjwatson: actually, etienneg is correct, in practice about the "manual" thing20:20
jjardonhello, I have a problem with devhelp: $ devhelp20:20
jjardondevhelp: error while loading shared libraries: /usr/lib/libgstbase-0.10.so.0: file too short20:20
jjardonis this bug already filled?20:21
wasabi_Weird question. Has something odd changed in Karmic that might effect speed and reliability of network connections?20:21
jjardon(karmic here)20:22
wasabi_Specifically, I can now only scp files at around 4k a sec, and all CIFS file transfers fail. Oddly enough, they fail when done by a Windows VM running on karmic.20:22
=== rickspencer3-afk is now known as rickspencer3
wasabi_It's like TCP is just falling over in some way.20:22
slytherinjjardon: not reproducible here20:23
wasabi_Wireshark shows lots of TCP out of order stuff, and lost segments.20:23
wasabi_This is between my machine, and any other machine on the same LAN. =/20:23
* soren cries about not being able to rip cd's.. :(20:25
* soren reboots20:26
cr3in a package, how can I create manpage aliases so that foo-gtk, foo-cli, foo-qt, etc. open the foo manpage?20:29
sorenDo we know when xsplash is supposed to start looking right? I.e. not like a horizontal bar that jitters up and down a bit, but something that looks like it20:31
slytherincr3: symply install symlinks20:31
sorens spinning horizontally.20:31
nurmisoren: we can have one init script, but i'm not clear on how one would be able to control the services independently20:31
sorennurmi: Well, it doesn20:31
sorent do that now anyway.20:31
sorenAt least not when stopping things.20:32
nurmisoren: ?  currently, you can stop/start any of the three services using the init scripts20:32
cr3slytherin: I thought I could simply tell dh_installman to update the mandb with aliases20:32
nurmisoren: granted, it does restart the process, but when the process comes back after, say, a 'walrus stop', then the walrus service is no longer running20:33
sorenHmm..20:34
sorenOh, right, I see what you mean.20:34
nurmisoren: i was thinking that we could maintain a small state file in /var/run/eucalyptus (next to the pid files) that records which services are disabled (i.e. a 'stop' has been called)20:35
sorenWhen would I want to stop them individually?20:36
sorenOr start them individually?20:36
nurmisoren: then, the init script can read that file and decide which services should not be running, and use the '--disable-<service>' flags to 'eucalyptus-cloud'20:36
sorennurmi: Are you still there? :)20:42
nurmisoren: we are going under the assumption that, for each unique 'package' or 'service', there is a way to control it independently20:43
sorennurmi: Yes. And why is that?20:43
nurmisoren: honestly, other than perception, the only reason I can think to start/stop them independently is if something goes wrong20:43
sorennurmi: That sounds reasonable.20:44
nurmisoren: or, if you decide that you want to bring down one sc/cluster for maintain while keeping the other services up20:44
sorennurmi: I'm just not sure having that option available in this way is important enough to warrant the other issues we're seeing.20:50
nurmisoren: i see, the alternative you're suggesting is one init script for all three packages?20:53
ulaashi! how do i add my windows boot to grub2?20:55
sorennurmi: Yes. I haven't thought about this a whole lot, but doing it that way sure would have saved me a few surprises :)20:56
=== sbasuita_ is now known as sbasuita
nurmisoren: i think as long as one can still install the services indepently (i.e., install walrus/sc/cloud alone on their own machines), then a single init script would be fine20:57
sorennurmi: And then perhaps a separate mechanism to disable a particular service.20:58
sorennurmi: Perhaps an explicit "/etc/init.d/eucalyptus-java-stuff disable sc" or something.20:59
nurmisoren: nod; do you forsee confusion around having an init script that is not named the same way as the package/service itself?21:00
nurmisoren: i.e., if one installs 'eucalyptus-walrus', and the init script is called 'eucalyptus-java-stuff', is that an issue?21:01
sorennurmi: A little bit. It depends on the new name, I suppose.21:01
sorennurmi: Hm...21:01
sorennurmi: It's a shame cjwatson isn't here. He seemed to have thought about this a bit.21:01
stgraberKeybuk: hey, I'm currently working on fixing ltsp following the upstart changes. When booting, I don't have dbus and hal running, but they work fine after I manually start them, what should be done to have them start automatically ?21:03
stgraberogra: ^ that's the only issue I saw with yesterday changes (so far)21:03
nurmisoren: we can defer for now and re-fire the conversation when cjwatson is around, if you like; i'm happy to chat anytime :)21:03
sorennurmi: Even during European business hours? :)21:04
nurmisoren: if thats what it takes!21:04
Keybukstgraber: why don't they start automatically?21:04
nurmisoren: init scripts make great 4am conversation :)21:04
sorennurmi: Well, right before our call tomorrow would probably be a good time, actually.21:05
nurmisoren: is 'right after' off the table? I have a meeting the hour before tomorrow21:05
nurmisoren: ah, thats getting late in EU21:06
sorenProbably not. I can't really make appointments on cjwatson's behalf, though :)21:06
nurmisoren: lets see how it goes tomorrow, i'll try to be around as far before and after the call as I can21:06
sorenCool.21:06
c_korncan someone give a comment about bug 428657 ? only a small bug.21:12
ubottuLaunchpad bug 428657 in quilt "Quilt tries to write into series also if it is a directory" [Undecided,New] https://launchpad.net/bugs/42865721:12
stgraberKeybuk: dbus used to started by S12dbus, now it's not there anymore and I'm just wondering what should be done so it gets started at boot time :)21:13
stgraber(I haven't had a chance to look at how upstart works in much details yet)21:13
Keybukstgraber: check /etc/init/dbus.conf21:14
stgraberKeybuk: hmm, what exactly is that "local-filesystems" ? our filesystem is mounted from the initrd in LTSP so that may be the issue ...21:16
Keybukstgraber: filesystems that are not remote21:16
ulaasany ideas abou grub2 windows boot?21:16
stgraberKeybuk: how can I manually check that condition ?21:17
Keybukstgraber: mountall --debug will tell you21:17
Laneyhmm21:20
Laney/etc/udev/rules.d/z60_hdparm.rules is a dangling symlink and a message about that file (z60) is the last thing that is printed before my boot (appears to?) hang21:21
nixternalKeybuk: sorry to bug ya, but do you have any doco somewhere re: upstart? I am messing around with a kdm setup now21:23
Keybukwhat would you like to know?21:23
nixternalcherry picking from /etc/init/ is how I have started piecing a file together21:23
Keybukman 8 init is a reasonable place to start21:23
Keybukthat'll lead you to man 5 init, man 7 {start,stop}{ed,ing} etc.21:23
KeybukI'll happily review anything you come up with ;)21:24
Keybukif you're doing kdm, it'd be neat if you could include the extra events I added to gdm as well21:24
nixternalcool...i will probably pass something in front of you over the next couple of days...i will let you rest and catch up with everything else first :)21:24
Keybukimmediately after xsplash is started I do:21:24
nixternaldon't need any more fires going on there from overworking :)21:24
Keybuk  initctl -q emit login-session-start DISPLAY_MANAGER=gdm21:24
Keybukand after login/auto-login21:25
Keybuk  initctl -q emit desktop-session-start DISPLAY_MANAGER=gdm21:25
nixternalhrmm, I will look at that...i didn't see it in the gdm.upstart file in the package21:25
Keybukit's in /etc/gdm/Init/Default and /etc/gdm/PreSession/Default21:25
nixternalgroovy, thanks for that!21:25
stgraberKeybuk: running mountall basically skips everything as already mounted and doesn't trigger dbus21:27
Keybukyes yes21:27
Keybukit's the log I want ;)21:28
Keybuk--debug outputs lots of opinions about what mountall thinks21:28
stgraberhttp://pastebin.com/f200368f21:28
Laneyboot hangs even with init=/bin/sh21:32
cjwatsonsoren: back now21:34
sorencjwatson: Ooh!21:34
sorennurmi: ^21:34
seb128hum21:35
seb128kees, do you have any details about all the changes you are doing on crash bugs?21:36
seb128kees, you just sent quite some emails in my bugsbox which I don't really know what to do about ;-)21:36
Keybukstgraber: nothing looks wrong here21:38
Keybukstgraber: what was your problem, again?21:39
jdstrandKeybuk: fyi, what was needed was 'start on net-device-added INTERFACE=lo'. 'started' doesn't work21:40
Keybukjdstrand: yeah I said that ;)21:40
stgraberKeybuk: dbus doesn't start on LTSP, so hal doesn't start and I end up with a X without mouse+keyboard21:40
Keybukright, but does mountall finish?21:41
=== cjwatson_ is now known as cjwatson
cjwatsonsoren: back now21:41
cjwatsoncr3: <hat maintainer="man-db">the correct way to get aliases into the manual page database is using symlinks</hat>21:41
stgraberKeybuk: ah, mountall should return at some point ?21:42
Keybukstgraber: it usually does21:42
keesseb128: hi! sure, in karmic I added some segv analysis fields to apport reports, so I'm now going back through old bugs adding them, since they can help narrow down the cause of crashes.21:42
Keybukif mountall is sitting there, and nothing starts, then that's a bigger problem than "no dbus"21:42
=== zul_ is now known as zul
cr3cjwatson: thanks, I created a foo-gtk.links under my debian directory after looking at a few other sample packges21:42
jdstrandKeybuk: I'm having trouble having upstart reflect the true status of ufw. eg, if it is disabled, it still shows that it is 'running'. I'd like to tell upstart it isn't running21:43
seb128kees, I fail to see anything useful in what you added so far to those bugs, do you have any example of what we can do with those lines?21:43
Keybukjdstrand: if it's disabled, exit 121:43
jdstrandKeybuk: right, but it exits with error then21:43
Keybukalternatively21:43
Keybukif it's disabled21:43
Keybuk  stop21:43
Keybuk  exit 021:43
jdstrandI don't think it is an error condition to have ufw disabled21:43
keesseb128: yeah, I can search for "SegvReason: exec" and look for crashes that resulted from misdirected execution flows, which is almost always a security bug.21:43
Keybukbut I would say exiting with an error is correct21:44
Keybukstart ufw21:44
Keybuk*should* exit with an error21:44
Keybukbecause what the sysadmin asked for did not happen21:44
keesseb128: also, it gives a sense for if it was a NULL deref, or a more complex issue.21:44
keesseb128: which should allow for easier triage.21:44
seb128kees, do you have a wikipage or something explaining what errors should be considered as real issues?21:44
cr3cjwatson: I then thought to myself that perhaps setup.py should handle manpages, ie the upstream project, rather than just the debian packaging. however, it seems that handling manpages is a distro thing rather than an upstream thing21:44
Keybukthis is Upstart, not sysvinit ;)21:44
seb128kees, or security issues21:44
keesseb128: no, it's not really real vs unreal, it's just a helpful heuristic to add when triaging crashes.21:44
seb128kees, ie "not located in a known VMA region (needed readable region)!" doesn't speak to me21:44
seb128kees, any wtf for those? ;-)21:45
stgraberKeybuk: strace shows it stuck on a select21:45
seb128or dictionnary or something21:45
Keybukstgraber: so mountall *isn't* finishing?21:45
keesseb128: I can write up a wiki page with some details21:45
stgraberKeybuk: no21:45
seb128kees, that would be nice, thanks21:45
Keybukstgraber: you could've mentioned that bit *first* :p21:45
keesseb128: where would you think such a page would be most discoverable?21:45
seb128kees, just being curious but what "vma" is?21:45
jdstrandKeybuk: maybe I am having a hard time leaving sysv, but if we are in a boot situation, the admin didn't say 'start', the boot process did. should I care that it exits 1 in that case?21:45
keesVirtual Memory Address.21:45
Keybukjdstrand: no, you need not care21:45
stgraberKeybuk: well, I didn't know that thing was supposed to return ;)21:45
Keybuk(Upstart won't care either) :p21:46
jdstrandKeybuk: I wasn't sure if the errors were captured somewhere which might cause later confusion21:46
keesseb128: it's a virtual memory address, which can be compared against the allocated VMAs for a process (the ProcMaps.txt file)21:46
cjwatsoncr3: it's usually/often an upstream thing, but that doesn't necessarily mean that setup.py is smart enough to deal with them21:46
* Keybuk is of the very strong opinion that "start service" in Upstart should never exit 0 if service is not running21:46
Keybukeven if the service is somehow disabled21:46
cjwatsoncr3: setup.py not being the be-all and end-all of upstreams :)21:46
jdstrandKeybuk: if no one will see the error on boot, then I agree that do 'start ufw' should error out if it is disabled21:47
Keybukjdstrand: I think you're worrying about too many things21:47
seb128kees, where? hum, the wiki documentation about apport or how to deal with crash bugs maybe?21:47
Keybukjdstrand: for example, Upstart will have its own first-class way of disabling jobs later21:47
cjwatsoncr3: there is, technically, support for just putting extra comma-space-separated names before the \- in the NAME section of the manual page - but if you use that without providing symlinks, I'll hunt you down :)21:47
Keybukjdstrand: that will disable them from auto-starting, while still allowing sysadmin to do "start job" if they want and actually start it21:48
cr3cjwatson: thanks for the explanation, I've been using setup.py so much more than autotools lately that I started to believe it was the end-all indeed :)21:48
jdstrandKeybuk: quite probably. I tend to fret and be paranoid when I am looking at something for the first time :)21:48
seb128kees, just adding some lines about what informations there could be useful to bug triagers to spot security issues or useful trick you can use from that to track a bug in an easier way would be nice21:48
seb128kees, thanks!21:48
Keybukjdstrand: I think it's abnormal for an Upstart job to have an /etc/default for example21:48
Keybukjdstrand: not in the least because those things can go in the upstart conf itself21:48
Keybukonce we have an Upstart policy, it may even be a bug to have one21:48
stgraberKeybuk: would the content of /proc/mounts help you have an idea of what's wrong ?21:49
Keybukstgraber: no, but /proc/self/mountinfo might21:49
keesseb128: okay, cool.  I will add it here: https://wiki.ubuntu.com/Apport21:49
jdstrandKeybuk: I was thinking about the /etc/default example too, since my issue here is essentially the same21:49
seb128kees, thanks!21:50
jdstrandKeybuk: but, for now, you have eased my mind and my upstart file much easier21:50
stgraberKeybuk: http://pastebin.com/m3cc2caa021:50
jdstrandKeybuk: thanks for the hand holding21:50
Keybukjdstrand: that's ok ;)  I'm still making this up as I go along21:50
Keybukbut Upstart does work in ways that are "surprising" to people used to sysvinit21:50
Keybukbecause Upstart works in ways that *I* think are right :p21:50
cjwatson/etc/default> well, that was true of init scripts as well - the reason /etc/default was split out was because it relieved sysadmins of the necessity to understand the init script while merging21:51
jdstrandhaha21:51
Keybukcjwatson: right - and upstart jobs are supposed to be very simple to read and change - so the rationale goes away21:51
cjwatsonthat *may* be less of an issue with upstart jobs, because they're simpler, but OTOH they're perhaps less familiar, so I don't know that it's a given21:51
jdstrandKeybuk: sure-- fwiw, I see the power, I just don't have a firm feel for it yet21:51
cjwatsonsysadmins are almost certainly more used to writing shell scripts than upstart jobs21:51
cjwatsonI'm not entirely sure I disagree with you, I just haven't yet decided if I agree :)21:52
Keybukcjwatson: plus I'm going on a bit of a "only include configuration options if we test them" crusade21:52
Keybukfor example21:52
KeybukRAMRUN=yes21:52
Keybukthat is an inappropriately named config option in /etc/default/rcS21:53
Keybukit should be named21:53
KeybukDO_I_WANT_THIS_TO_BOOT=yes21:53
Keybukbecause all you're going to get by setting that to "no" is a non-working system21:53
cjwatsonI think /etc/default/rcS is perhaps somewhat exceptional :)21:53
Keybukand thus, it's ignored now21:53
Keybukcjwatson: I think the same holds true for most things in /etc/default21:53
cjwatson/etc/default/console-setup21:53
cjwatsoncomes to mind :)21:54
Keybukcjwatson: should probably be something more like /etc/console-setup21:54
Keybukit's not the "defaults" for an init script, after all21:54
cjwatsontrue21:54
Keybukit's a first class config file21:54
cjwatsonI've often had to change syslog options, and appreciated the default file for that when it was introduced21:54
Keybukstgraber: I wonder whether mountall is expecting that it has to mount /rofs fw ;)21:54
Keybukerr, rw21:54
Keybukcjwatson: it shouldn't be hard to edit the upstart job though21:55
Keybukwith the bonus that you get far better merge context if the options change21:55
cjwatsonyeah, it's not editing it that's hard, it's that it's tedious to merge, and interrupts upgrades more often21:55
Keybukyou'd have to merge the default file if they changed too21:55
cjwatsonthe init script, and probably even the upstart job, change significantly more often than the default file, IME21:55
cjwatsonobviously I don't have relevant E of upstart jobs as time goes on yet21:55
Keybukand then there's the cost of all the default files21:56
Keybukopening them for every job that uses them, and reading them21:56
Keybukand if you edit the default file, should Upstart notice that, and take some action?21:56
Keybuk(as it does with the actual conf file)21:56
Keybukand there's the simple fact that I think that things should be configured in one place, not spread out across the filesystem :p21:56
cjwatsonI'm not saying they're universally good - I'm just not convinced that they're universally bad21:56
cjwatsonanyway, late dinner :)21:56
Keybukstgraber: the mountall --debug output you had was somewhat annoyingly corrupted21:57
Keybukstgraber: could you try without the 2>&1 and see what you get21:57
stgraberKeybuk: http://pastebin.com/m7b3d6ebe21:58
ionIt wouldn’t be tedious to merge at all, if dpkg handled conffile updates sanely. :-P21:58
Keybuk#21:58
Keybuk#21:58
Keybukspawn: mount /rofs [1568]21:58
Keybuk#21:58
Keybukmountall: mount /rofs [1568] terminated with status 121:58
Keybukhah21:58
ionMost of the merges would happen automatically and very few would require manual help.21:59
Keybuk#21:59
Keybuk#21:59
Keybukspawn: mount -f -a -t squashfs /dev/nbd0 /rofs21:59
Keybuk#21:59
Keybukmount: according to mtab, /dev/nbd0 is already mounted on /rofs21:59
Keybukthat's weird21:59
Keybukoh, no21:59
Keybukthat's ok21:59
Keybukstgraber: don't suppose you have a shell right now?21:59
Keybukactually, don't worry22:00
Keybukit's pretty clear what's going on ;)22:00
Keybuk#22:00
Keybukmounted: virtual 14/14 swap 0/0 remote 0/0 local 0/122:00
Keybuk#22:00
Keybukmounted: fhs 12/1222:00
Keybukthat's quite funny22:00
Keybukit thinks / is a virtual filesystem (like proc)22:01
Keybuknot a local filesystem22:01
Keybukand is not going to declare local filesystems done until it can mount /rofs rw22:01
Keybuk(which won't ever happen)22:01
stgraberKeybuk: don't you have a similar issue with the livecd ?22:06
Keybukstgraber: that's what I'm wondering, don't know why that works22:06
stgraberKeybuk: the way LTSP and the LiveCD mounts / should be very similar22:06
Keybukstgraber: can you also do blkid -p /dev/nbd0 for me22:07
stgraber:~# blkid /dev/nbd022:07
stgraber/dev/nbd0: TYPE="squashfs"22:07
Keybukoh, well, that's descriptive ;)22:07
Keybukudevinfo -q all -n nbd0 | grep ID_FS22:07
stgraberroot@22:08
stgraber:~# udevadm info -q all -n nbd0 | grep ID_FS22:08
stgraberroot@22:08
stgraber:~#22:08
stgraberso basically, nothing ;)22:09
stgraberhttp://pastebin.com/m695fde7d22:09
Keybukok that makes sense22:09
Keybukat least it's SUBSYSTEM=block ;)22:10
Keybukok22:10
KeybukI already have a fix for this22:10
KeybukI just need to invert it22:10
stgraberKeybuk: cool22:14
xcdfgkjhgcvikonia: WTF was that for?22:16
ikoniaxcdfgkjhgcv: that is not for discussion in here22:17
=== debfx_ is now known as debfx
sorennurmi: Not around?22:54
=== jon is now known as Guest34566
TheMusoHrm, by the topic, can I assume things are still not sorted?23:27
Laneymy third try at upgrading just resulted in a third different failure ;)23:28
slangasekTheMuso: things are 99% sorted, with the major exceptions being liveCDs and people using cryptsetup on disks other than /23:36
LaneyHave people experienced "no gdm"?23:39
TheMusoah ok23:40
slangasekLaney: commonly so23:40
Laneythat bodes well for there being a fix ;)23:40
slangasekLaney: what version of dbus do you have installed?23:40
cjwatsonand libexpat123:41
* Laney returns to said machine23:41
slangasekcjwatson: should only matter in practice if /usr is on NFS :)23:41
slangasek(otherwise the dbus change is necessary and sufficient)23:41
Laneyslangasek: 1.2.16-0ubuntu423:42
cjwatsontrue23:42
slangasekLaney: ok, then you have the version that fixed the first bug, and have found another bug revealed by that fix23:45
Laney):23:46
Laney:) even23:46
slangasekLaney: edit /etc/init/mountall.conf; add 'bash' before the mountall command; run mountall --debug 2>&1 > /dev/mountall.log from the shell; submit that log in a bug against the mountall package23:46
slangasekLaney: (and subscribe me, so I can try to help triage while Keybuk is snorkeling in bugs)23:47
Laneysure23:47
Laneyslangasek: "bash" before script or in the script block?23:47
slangasekLaney: in the script block23:48
Laneyalright23:48
Laneydo you really mean /dev/mountall.log?23:49
=== bjf is now known as bjf-afk
cjwatsonyes, /dev is writable23:49
cjwatsonwhen running mountall, most other places aren't23:49
Laneyok23:49
Laneywill have to fish it out of there, no networking either23:49
slangasekLaney: you can get gdm up by hand by running 'start dbus && start hal && start network-manager && start gdm'23:51
slangasekLaney: but we'd like the mountall log first, to know why it's not working automatically :)23:51
Laneymountall is still grinding away23:51
Laneyshould it take a while?23:51
slangasekLaney: oh, I would expect it to hang indefinitely; background it and grab the log23:53
slangasekLaney: btw, do you use LVM?23:53
Laneyaha23:53
Laneyslangasek: no, got an mdadm partition though23:53
slangasekkees: I think bug #431042 needs another pair of eyeballs; there've been 4 of these reports now, all of them recent and all of them involving something holding the debconf db open when trying to configure libpam-modules23:54
ubottuLaunchpad bug 431042 in pam "dpkg error code 1" [Undecided,New] https://launchpad.net/bugs/43104223:54
Laneyslangasek: (which didn't get mounted)23:54
keesslangasek: reading...23:54
slangasekLaney: ok - please add that to the bug, that's the exact insight we need :)23:54
LaneyThis exposing bugs lark is fun23:54
cjwatsonslangasek: 431042> mm, I saw that briefly and thought "isn't debconf just the messenger?"23:55
cjwatsonor at least some other dup of it23:55
slangasekcjwatson: yes, I thought that for the first three instances that were filed against pam23:55
slangasekthere's some sort of deeper issue here, but I don't know what23:56
TheMusoIs booting onto an LV a problem as well? If so, I'll hold off upgrading today as well. :)23:57
bodhi_zazenstill working on fixing upstart from yesterday ?23:59
=== robbiew is now known as robbiew-afk

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