/srv/irclogs.ubuntu.com/2011/10/11/#ubuntu-devel.txt

=== dendro-afk is now known as dendrobates
=== dendrobates is now known as dendro-afk
mdeslaurinfinity, slangasek: I've put some test packages that enable amd64 flash here, and would really appreciate your invaluable comments, especially for the oneiric version : https://launchpad.net/~mdeslaur/+archive/64bitflash01:58
=== dendro-afk is now known as dendrobates
=== dendrobates is now known as dendro-afk
pittiGood morning04:14
ajmitchmorning pitti04:15
pittiev: congrats, bcmwl wifi is now rather painless indeed!05:17
pittiev: seems it's one tiny step away from perfection :) (bug 872119)05:17
ubottuLaunchpad bug 872119 in ubiquity (Ubuntu) ""Error occurred while copying the network settings" on bcmwl machine" [Undecided,New] https://launchpad.net/bugs/87211905:17
micahg@pilot in05:52
=== udevbot_ changed the topic of #ubuntu-devel to: Beta 2 Released | Archive: Final Freeze | Development of Ubuntu (not support, not app development) | build failures -> http://bit.ly/or6CHJ | #ubuntu for support and general discussion for hardy -> oneiric | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: micahg
=== tkamppeter__ is now known as tkamppeter
dholbachgood morning07:07
evpitti: argh. that one is entirely my fault and will take all of two seconds to fix08:00
pittiev: not a dealbreaker; it makes it a whole lot more easy to use broadcom cards :)08:00
pittiev: does that only affect bcmwl, or other wifi (such as intel), too?08:01
evpitti: the copying of network-manager's brain to the installed system is broken, so it'll affect any card08:03
evso the user will have to re-enter their wifi password08:03
evand they'll all see that error dialog08:03
pittiev: that more or less just copies /etc/NetworkManager/system-connections/*, or is there more to it?08:04
evpitti: correct08:08
micahg@pilot out09:21
=== udevbot_ changed the topic of #ubuntu-devel to: Beta 2 Released | Archive: Final Freeze | Development of Ubuntu (not support, not app development) | build failures -> http://bit.ly/or6CHJ | #ubuntu for support and general discussion for hardy -> oneiric | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
ev@pilot in09:22
=== udevbot_ changed the topic of #ubuntu-devel to: Beta 2 Released | Archive: Final Freeze | Development of Ubuntu (not support, not app development) | build failures -> http://bit.ly/or6CHJ | #ubuntu for support and general discussion for hardy -> oneiric | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: ev
=== MacSlow is now known as MacSlow|lunch
=== Riddelll is now known as Riddell
tumbleweedcan someone in ubuntu-branches please reject https://code.launchpad.net/~bones/ubuntu/natty/radiotray/fix-for-722886/+merge/7010711:08
tumbleweedand mark https://code.launchpad.net/~jtaylor/ubuntu/natty/meld/meld-sru/+merge/72410 as merged (or whatever we do for SRUs targetted at the release branch)11:08
=== dholbach_ is now known as dholbach
tumbleweedhttps://code.launchpad.net/~jtaylor/ubuntu/natty/pycryptopp/sru-811721/+merge/75850 is also uploaded11:15
tumbleweedhttps://code.launchpad.net/~rye/ubuntu/natty/bindwood/update-firefox-6-compat-fix/+merge/76055 appears to be rejected11:18
dokoLaney, did you sort out the cairo-dock debian/upstream miscommunication?11:22
tumbleweedcjwatson / james_w: two more to mark Merged: https://code.launchpad.net/~brunoqc/ubuntu/natty/lfm/lfm-fix-786491/+merge/77859 https://code.launchpad.net/~jtaylor/ubuntu/natty/singularity/fix-576504/+merge/7828611:28
tumbleweedthat's it11:28
Laneydoko: no, we should get on that as well11:39
=== dendro-afk is now known as dendrobates
=== MacSlow|lunch is now known as MacSlow
=== Zic_ is now known as Zic
=== dendrobates is now known as dendro-afk
=== plars-holiday is now known as plars
=== dendro-afk is now known as dendrobates
=== dholbach_ is now known as dholbach
pittitumbleweed: done all but the bindwood one; what's with that one?14:19
tumbleweedpitti: I guess micahg is the pbest person to answer that one, but I'm assuming the fix is going into a different sourcepackage...14:34
=== kancerman_ is now known as kancerman
slangasekjamespage: before setting plymouth:debug, were you able to reproduce bug #849414 consistently?14:41
ubottuLaunchpad bug 849414 in plymouth (Ubuntu Precise) "plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()" [High,Incomplete] https://launchpad.net/bugs/84941414:41
jamespageslangasek: I was able to; however I appear to have stopped hitting that issue14:42
slangasekjamespage: so reverting plymouth:debug doesn't cause it to reappear either? :(14:42
jamespageslangasek, I running with it off now with no issues14:43
jamespageslangasek, so I was thinking about what had changed; I was getting an ugly text based splash when I saw the issue14:43
slangasekah14:44
jamespagesetting debug turned that off - and the issue went away14:44
slangasekthat's helpful info :)14:44
slangasekright, I don't think setting debug turned it off, I think something else I did turned it off :)14:44
slangasekand your debug change just happened to coincide with other initramfs fixes14:44
jamespageslangasek, quite possibly14:44
slangasekjamespage: you could try re-breaking the graphics display by removing the plymouth-theme-ubuntu-logo package14:46
jamespageslangasek, sure - give me a couple of minutes14:46
jamespageslangasek, do you want me to turn debug on as well?14:47
slangasekjamespage: I'd try first without turning on debug (in case it's timing-sensitive), then if that reproduces the issue, turn on debug14:48
jamespageslangasek, ack14:48
=== Girly-Girl is now known as GirlyGirl
=== sagaci_ is now known as sagaci
jamespageslangasek, hmm - not able to reproduce14:54
slangasekjamespage: and it was 100% reproducible before?14:55
jamespageslangasek, yes - I turned debug mode on an off and the came and went14:55
slangasekjamespage: can I get apt logs, plus a big "here's where I turned on debugging" arrow, to try to work out what else changed on your system?14:55
slangasekjamespage: also, what's your video?14:55
jamespageslangasek, video is ATI Mobility Radeon HD 5400 Series15:00
slangasekjamespage: binary video drivers?15:01
jamespageslangasek, digging logs now15:05
jamespageslangasek, not sure whether its relevant but when I got the issues I had a really low res text based splash as well15:05
jamespagewhen I just tested it was much higher res15:05
jamespageslangasek, http://paste.ubuntu.com/706151/15:05
jamespageslangasek, I think I first saw this issue on the 04/11 (indeed that is the date of the crash file that jhunt and I looked at earlier)15:06
jamespageI turned debug mode on then  - and did a few reboots and could not reproduce15:06
slangasekoh heh15:06
slangasekhigher res> so you've got vesafb loading and a framebuffer console, that's going to change things for sure15:07
jamespageslangasek, thats what I figured15:07
slangasekjamespage: this is with the cryptsetup package installed, right?15:07
jamespageslangasek, no15:07
slangasekhmm15:07
slangaseknot sure why you would have gotten plymouth text without vesafb in that case15:08
slangasekare you using binary drivers?15:08
jamespageslangasek, yes15:08
jamespageslangasek, just to prove it - https://launchpadlibrarian.net/81898994/firegl-crash.jpg15:09
slangasek:-)15:10
jamespagethats from a diff bug15:10
jamespagelooking at what i wrote on bug 86598415:11
ubottuLaunchpad bug 865984 in Ubuntu "firegl_sig_notifier crash on shutdown or reboot" [Undecided,New] https://launchpad.net/bugs/86598415:11
hallyn_slangasek: if you get a moment, can smoser and I ping you about a glibc bug and the likelyhood of it being considered fixable by upstream?15:12
jamespageI appear to have had a vesafb/framebuffer console until shortly before the 04/1115:12
jamespageI raised that bug the same day I did the plymouth debug stuff15:13
slangasekhallyn_: just ask directly please :-)15:17
cndseb128, is there still time to get the libgrip fix into oneiric? or should it be an sru?15:19
seb128cnd, sru15:20
cndok15:20
seb128cnd, which is fine we already got a stack of srus uploaded15:20
seb128including compiz15:20
cndok15:20
cndI'll prepare an sru upload then15:20
pittiLaney: wow, I wouldn't have expected breezy to top the upload score -- we had way fewer devs back then15:21
pittiLaney: well, maybe we uploaded 25 sets of langpacks :)15:21
Laneyyeah, not sure what that is about15:22
Laneylet me do the last query but s/oneiric/breezy/15:22
pittiactually, it would be interesting to filter out all language-pack-* stuff15:22
Laneythe data is all in udd ;-)15:22
tseliotslangasek: I'm seeing a lot of complaints on arm from apps such as gconf and metacity looking for gconfd-2 in /usr/lib/i386-linux-gnu/libgconf2-4/ instead of using /usr/lib/arm-linux-gnueabi/libgconf2-4/. There must be something wrong with my multi-arch setup here. Any ideas? (not a symlink works around the problem)15:23
hallyn_mdeslaur: Bug 871847, I assume needs to wait for an SRU at this point?  :)15:24
ubottuLaunchpad bug 871847 in virt-viewer (Ubuntu) "Bad port '0' upon connect qemu+ssh" [High,Confirmed] https://launchpad.net/bugs/87184715:24
hallyn_slangasek: ok, i'm about to be afk for a few mins, but the problem basically is that grantpt in glibc starts out with a check for whether /dev/pts/{ptnum} is a valid slave.  WIth /dev/pts being hardcoded.  So if you call grantpt on /chroot/dev/pts/0, and /dev/pts/0 does not exist, the call will fail.15:25
mdeslaurhallyn_: yep, universe just went into freeze15:25
hallyn_mdeslaur: zounds!15:25
hallyn_ok, thanks :)15:25
Laneypitti: I don't think langpacks appear in -changes?15:25
pittiLaney: they don't15:26
Laneythen they wouldn't be in these stats15:26
pittiLaney: ah, it's based on -changes@, not soyuz15:26
hallyn_slangasek: this is only a problem when using a newly cloned devpts, so i'm not sure if glibc will deem that valid?15:26
Laneyright15:26
Laneymaybe autosyncs were announced back then?15:26
slangasektseliot: uh? i386-linux-gnu vs. arm-linux-gnueabi, what's that about?  You're saying you have an arm system, with i386 packages installed?15:26
pittiLaney: was just going to say :)15:26
hallyn_slangasek: the workaround is doable but hacky - gotta fork, unshare a new mounts ns (with privilege), bind-mount /dev/pts, and then do the grantpt15:26
pittiLaney: right, see https://lists.ubuntu.com/archives/breezy-changes/2005-April/thread.html15:27
bdmurraystgraber: should bug 813065 be Fix Released - comment 9 leads me to think no15:27
ubottuLaunchpad bug 813065 in ubiquity (Ubuntu Oneiric) "Live session switches to VT console briefly" [High,Fix released] https://launchpad.net/bugs/81306515:27
slangasekhallyn_: why do you call grantpt against a chroot?15:27
pittifor the other months, too15:27
slangasekI don't think I understand the problem, sorry15:27
Laneylet me exclude that then15:27
tseliotslangasek: no, they're all for arm15:27
hallyn_slangasek: libvirt's parent process sets up /dev/pts/0 in the container's rootfs as a console for 'virsh console' to connect to15:27
Laneya much different picture emerges15:28
stgraberbdmurray: comment #9 was before Steve sent me a merge proposal fixing it properly which got merged and uploaded (comment #10)15:28
hallyn_slangasek: though in any case, since thamanpage doesn't mention anything, glibc definately is *wrong*.15:28
Laneypitti: http://paste.debian.net/135733/15:28
slangasektseliot: but you said "There must be something wrong with my multi-arch setup here" - have you *done* some special multiarch setup?15:28
bdmurraystgraber: okay then what is going on with bug 871936?15:28
ubottuLaunchpad bug 871936 in ubiquity (Ubuntu) "Live session switches to VT console [nvidia]" [Undecided,New] https://launchpad.net/bugs/87193615:29
pittiLaney: still respectable, compared to warty and hoary15:29
hallyn_slangasek: (but glibc might demand the manpage fix rather than the code fix :)15:29
Laneyit's actually remaining fairly steady15:29
stgraberbdmurray: I'm not sure, maybe slangasek has an idea but AFAIK ubiquity-dm now does the right thing, it may simply be an nvidia specific flicker bug15:29
tseliotslangasek: no, I did nothing at all to set up multiarch. It's just that somehow apps are looking for that path15:29
Laneybut oneiric moves up to fifth :-)15:29
slangasekhallyn_: heh, indeed... I don't know, sorry15:30
hallyn_slangasek: nm, i guess i should join the m-l rather than bug you about it :)  thanks15:30
slangasektseliot: what's the exact error message?15:31
tseliotslangasek: "failed to activate configuration server: Failed to execute program /usr/lib/i386-linux-gnu/libgconf2-4/gconfd-2: Success15:31
bdmurraystgraber: okay the patch didn't seem hardware specific to me15:31
tseliotslangasek: this comes from gnome-settings-daemon, metacity, etc.15:31
stgraberbdmurray: indeed, it fixes flickerless for any graphic card that does work correctly with flickerless15:32
stgraberbdmurray: which AFAIK isn't the case of nvidia15:32
hallyn_heh, i see, there really is no m-l15:33
slangasektseliot: does i386-linux-gnu show up anywhere in config files under $HOME?15:33
hallyn_libc-alpha it is.  (weird name)15:33
seb128slangasek, tseliot: I know what it is15:34
slangasekseb128: oh?15:34
seb128slangasek, well, maybe not15:34
seb128slangasek, /usr/share/dbus-1/services/org.gnome.GConf.service is in gconf2-common which is arch all15:34
seb128but "Exec=/usr/lib/libgconf2-4/gconfd-2" there15:35
slangasekjamespage: when you said "04/11", you meant "04/10", right?15:35
slangasekseb128: hmm15:35
jamespageslangasek, hrm - yep15:36
tseliotseb128, slangasek: but then how would it look for i386-linux-gnu ?15:36
seb128tseliot, the arch all is built on i38615:36
seb128so it would have the i386 path15:36
slangasektseliot: I don't know; and I've not seen such an error on amd6415:36
seb128but that doesn't seem to be it15:36
seb128the .service has non multiarch paths15:36
seb128that was just an idea, ignore me ;-)15:36
tseliotseb128, slangasek: having a hardcoded path shouldn't be too good anyway15:36
ogra_slangasek, i think i saw the same issue being discussed in #linaro this weekend15:38
ogra_there must be a bug open for it already15:38
seb128tseliot, ogra_, slangasek: is linaro or somebody shipping a multiarched version of gconf?15:38
seb128our libgconf is not on multiarch15:38
tseliotthat's a good question15:39
seb128but it seems the service in arch all binary would lead to that question if somebody did a multiarch build without changing it to arch any15:39
ogra_seb128, no idea, i think they are still working on switching their image builds to oneiric15:39
seb128that's the only way I could explain it15:39
ogra_(linaro is one release behind since they do monthly releases)15:39
seb128question->error15:39
seb128ogra_, well, we need multiarched gconf15:40
seb128so that's not being "behind"15:40
tseliotslangasek: and no, I can't find any references to i386 in $HOME15:40
slangasekjamespage: are you sure you don't have cryptsetup installed?15:40
seb128it seems somebody has a custom multiarch version of gconf15:40
ogra_the error showed up for them after switching to oneiric15:40
slangasektseliot: hmm15:40
seb128ogra_, can you ask them their version of gconf?15:40
ogra_i didnt follow that deeply, but i know they opened a bug15:40
jamespageslangasek, yes - http://paste.ubuntu.com/706181/15:40
slangasekseb128: what do you mean by "multiarched gconf"?  We should only have one copy of the daemon running...15:41
tseliotogra_: right, I can only reproduce the problem in oneiric15:41
seb128slangasek, the service is dbus activated, if the path was multiarch specific but they have a .service in arch:all that would lead to such issues15:41
slangasekok15:41
seb128slangasek, dbus would be trying to spawn the i386 location15:41
slangasekright; so when multiarching gconf, the daemon should be split out of the library package...15:42
seb128or the .service should be in an arch:all binary15:42
seb128so it gets the right location for each arch15:42
tseliotthe latter sounds easier15:43
seb128slangasek, the daemon is already splitted out of the library15:43
seb128the issue is that the dbus service which has the service location is in gconf2-common arch:all15:43
seb128we should just move the .service with the daemon when we multiarch it15:43
seb128well, that's just guess work on what their issue is, but "/usr/lib/i386-linux-gnu/libgconf2-4/" doesn't make sense if gconf has not been changed for multiarch15:44
seb128so I guess somebody did that work in a ppa or something15:44
seb128ogra_, tseliot, slangasek:15:46
seb128https://blueprints.launchpad.net/linaro-ubuntu/+spec/multiarch-porting-11.0915:46
seb128"Convert to multiarch, gconf: DONE"15:46
seb128so yeah, "linaro bug" I guess15:47
ogra_seb128, i dont see that bug here and have no issues15:47
ogra_i just saw it being discussed by the linaro gusy15:47
seb128ogra_, well that didn't land in Ubuntu for sure15:47
ogra_*guys15:47
seb128ogra_, their workitem is DONE so I guess they have their own version somewhere15:47
seb128in any case not an Oneiric issue ;-)15:47
ogra_oh, its a linaro spec15:47
* ogra_ missed that15:47
ogra_there it is15:49
ogra_bug 87189215:49
ubottuLaunchpad bug 871892 in Linaro "org.gnome.GConf.service contains i386 pathname" [Undecided,New] https://launchpad.net/bugs/87189215:49
tseliotogra_, seb128, slangasek: that's the exact bug that I'm seeing here15:50
seb128tseliot, what do you use? linaro or Ubuntu?15:50
ogra_it was actually discussed yesterday ...15:51
tseliotseb128: ubuntu15:51
seb128tseliot, dpkg -l | grep gconf15:51
ogra_seb128, linaro builds their oneiric images from our archive plain, no additions but HW bits yet15:51
ogra_they only start to work on oneiric this week15:51
seb128ogra_, that doesn't make sense, gconf is not multiarch in Ubuntu, if it was I would knew it15:52
ogra_seb128, right15:52
tseliotseb128: it doesn't seem to return anything15:52
seb128tseliot, you don't have gconf installed? how did you do your install?15:52
ogra_seb128, i dont kno wabout multiarch, what i know is that linaro only starts working on a release once ubuntu released it15:52
seb128we still have a stack of things in the default install using it15:52
ogra_so atm what they use should be plain ubuntu15:52
ogra_since they only switched image builds to oneiric this week15:53
seb128ogra_, well with their own layer or ppa on top I guess15:53
ogra_for kernel and bootloaders,. yep15:53
seb128ogra_, seeing  https://blueprints.launchpad.net/linaro-ubuntu/+spec/multiarch-porting-11.09 they need multiarch conversions over what oneiric has15:53
ogra_but no desktop bits yet15:53
ogra_right, that might be, i can only comment on what i observed ... i dont work in linaro :)15:54
tseliotseb128: apt-cache show gconf shows the installed size among other things15:54
tseliotseb128: err... gconf215:54
seb128tseliot, how did you do your install? it's puzzling that you don't have gconf installed... are you sure you didn't type dpkg -l | grep gconf?15:54
seb128type->typo15:55
tseliotseb128: yes, I typed it 3 times. I used our installer (which is probably the same as linaro)15:56
ogra_no15:56
ogra_linaro doesnt use any installer, they just install a metapackage in a chroot and tar that up15:57
tseliotogra_: we're doing something similar, through the usual live-helper though15:57
ogra_well, ubuntu installs tasks etc ... might get you minimally different results15:58
seb128slangasek, just for the record it's indeed a linaro ppa with a multiarched version which has the .service in the arch all binary16:16
seb128slangasek, i.e not an Ubuntu bug (tseliot get the issue on a custom build, not on an Ubuntu install)16:17
* tseliot nods16:17
slangasekseb128: ah, heh16:25
slangasekjamespage: did you for any reason set FRAMEBUFFER=y manually in your initramfs config?16:25
jamespageslangasek: no - I've not touched it16:26
slangasekjamespage: mmk16:27
stgraberSpamapS: I just posted the generate /etc/network/interfaces to bug 87021416:27
ubottuLaunchpad bug 870214 in open-iscsi (Ubuntu Oneiric) "iSCSI root installation creates manual eth0 configuration + long boot" [High,New] https://launchpad.net/bugs/87021416:27
stgraberSpamapS: is it normal that the boot waits for 2 minutes with a /etc/network/interfaces like this one?16:27
slangasekjamespage: oh - could you try setting 'gfxpayload=text' manually in your /boot/grub/grub.cfg, instead of the default gfxpayload=$linux_gfx_mode?16:28
jamespageslangasek: OK16:28
SpamapSstgraber: it is normal that it would be waited on if eth0 doesn't exist16:28
SpamapSstgraber: since we're waiting for the full configuration of eth0. While its waiting, has eth0 been initialized by the kernel?16:29
stgraberSpamapS: hmm, I don't know for jamespage's setup, but I'm pretty sure eth0 existed in his case16:29
stgraberSpamapS: it's netboot with root on iscsi, so yes eth0 is initialized by ipconfig in the initramfs16:29
SpamapSHm, so is it possible that we never get an 'ifup eth0' for that?16:30
SpamapSI would have thought 'ifup -a' would catch it in /etc/init/networking.conf16:30
stgrabersadly my test environment here lets me install over iscsi but not boot from it (I'm missing my usual PXE server ;))16:32
stgraberoh, actually I guess I can extract the kernel and initrd and have kvm boot that directly16:32
jamespagestgraber, SpamapS: I still have one of the test images locally if you want me to poke it in any way16:32
slangasekSpamapS, stgraber: there should still be a network-device-add event which should still cause upstart to trigger an 'ifup eth0' - but what happens if you run 'ifup eth0' for this?16:33
SpamapSI'd guess then that the problem is ifup -a doesn't, for whatever reason, see eth0 as needing to come up.. and so doesn't execute the if-up.d jobs.16:33
slangasekit's not even an ifup -a16:33
slangasekit's /etc/init/network-interface.conf16:33
SpamapSOh so you still get the network-device-added ?16:33
slangasekof course16:33
slangasekthat comes from udev from coldplugging16:33
SpamapSwell then wtf :)16:33
SpamapSis it possible thats happening before virtual-filesystems ?16:34
slangasekno16:34
SpamapSah right, udev starts on virtual filesystems16:34
stgraberjamespage: is commented the two lines for eth0 in /etc/network/interfaces fixing the issue for you?16:37
stgraber(looking for a workaround)16:38
jamespagestgraber: rings a bell - lemme try16:38
stgraberslangasek, SpamapS, jamespage: Current discussion here (with Daviey) is that we could probably just release note the workaround for now, then SRU a fix if that doesn't involve changing /etc/network/interfaces, otherwise just have it fixed for P16:39
stgraberassuming commenting these lines workarounds the issue for jamespage16:40
jamespagestgraber: I don't think that its an issue thats going to impact alot of people so thats prob fine16:40
jamespageslangasek, just tried gfxpayload=text == no seg fault16:41
stgraberjamespage: yeah, it's also a case where if you boot a server, you'll already wait 5 minutes for your BIOS, waiting 2 minutes for your first boot shouldn't be too bad (assuming you know the workaround and apply it then)16:41
slangasekjamespage: did you get the 640x480 text again?16:41
=== deryck is now known as deryck[lunch]
jamespageslangasek, I think so - ssd so boots fast - lemme double check16:42
jamespagestgraber: commenting the entries in /etc/network/interfaces works around the issue for me16:43
stgraberSpamapS: ok, so we at least have a workaround16:44
slangasekstgraber: why do we want this 'manual' entry in /e/n/i?16:45
stgraberslangasek: I can't think of a good reason for that, though I still think "inet manual" should work as it's valid syntax16:47
slangasekshould work, but it's meant for interfaces where you're going to actually *do* something via up/down rules16:48
slangasekAFAICS this is a misuse of it; so if we can fix the bug by dropping that generated entry...16:48
jamespageslangasek: double checked - did boot in 640x480 text mode16:48
slangasekjamespage: and still no crash?  Great, I'll mark the bug as fixed ;P16:48
jamespageslangasek: no crash16:49
stgraberslangasek: well, then I'll be happy to file another bug when I upgrade my servers where I have "inet manual" with a post-up and pre-down entry16:49
stgraberas they'll be affected by the same bug with a config that actually does something16:49
slangasekstgraber: or open an ifupdown task to go with the open-iscsi one16:49
slangasekand we can fix open-iscsi pre-release, and fix ifupdown post-release16:50
SpamapSslangasek: agreed on that, an empty manual entry is a place holder we don't need16:50
SpamapSCould it be that ifupdown agrees, and ignores it?16:50
slangasekdunno, testing16:51
andreasnjcastro, ping16:52
jcastroandreasn: hi16:52
slangasekSpamapS: I do see if-up.d scripts being run for my ifup of a manual interface, anyway16:52
slangasekSpamapS: and 'ifup foo' gets me a static-network-up event, so... dunno16:59
slangasekstgraber: ^^16:59
SpamapSwhat about the upstart udev bridge16:59
slangasekstgraber: I'd suggest throwing some debugging into /etc/network/if-up.d/upstart to dump to a per-interface log file and see what's going on17:00
SpamapSis it racing with udev ?17:00
SpamapSlike..17:00
SpamapSit starts on starting udev ..17:00
stgraberjamespage: can you try that ^17:00
SpamapSbut does it return before its actually bridging?17:00
slangasekSpamapS: no, it always starts *before* udev and sits waiting on the netlink socket17:00
slangaseker17:00
slangasekSpamapS: I hope not :P  I guess I can look17:00
* SpamapS peeks at it too17:00
stgraberslangasek: still working on getting my laptop back into a usable stage (for some reason my last reboot broke something) and then I'll try to get a complete iscsi setup for testing17:00
slangasekstgraber: ok :)17:01
SpamapSslangasek: no, as I would have expected, it adds the udev monitor before daemonizing17:02
slangasekSpamapS: right - I think we would be hearing about more things broken than just this, otherwise :)17:03
SpamapSif booting with --verbose , do we see the network-device-added event ?17:04
slangasekstgraber, SpamapS: I've changed my mind; there are legitimate corner case reasons why we want the entry for the interface... so network-manager doesn't even try to touch it :P17:11
slangasekstgraber: so I don't think we should change open-iscsi for release, but instead just SRU ifupdown (once we figure out what the problem is!)17:11
stgraberslangasek: sounds good. I'll mark the bug as invalid for open-iscsi, we already have a task for ifupdown and the release notes17:12
hallyn_smoser: I emailed the glibc-alpha m-l about the grantpt issue.  We'll see what they say17:16
jamespagestgraber, I logged some debug output with the manual entry in /e/n/i present and commented - neither generates any log data for eth0 from  /etc/network/if-up.d/upstart17:16
hallyn_(I'm expecting a spanking, tbh, but hopefully not)17:16
jamespageonly get a file for lo17:16
stgraberSpamapS: ^17:17
smoserhallyn_, link ?17:17
hallyn_smoser: http://www.cygwin.com/ml/libc-alpha/2011-10/msg00008.html17:19
SpamapSjamespage: can you boot with --verbose and look in /var/log/boot.log for the net-device-added event ?17:24
jamespageSpamapS, sure17:24
slangasekstgraber, jamespage, SpamapS: I notice that open-iscsi installs an if-up.d hook of its own17:24
slangasekwhich sorts lexically before upstart17:24
slangasekI wonder if it's broken?17:25
SpamapSthe lo hook fired...17:25
slangasekwell, the hook special-cases lo ;)17:26
stgraberslangasek: oh, actually, the upstart script shipped by open-iscsi looks like it could break the boot17:26
slangasekoh excellent17:26
slangasekOh dear17:27
stgraberI didn't even notice that thing before but that can explain a lot of things ;)17:27
stgraberhttp://paste.ubuntu.com/706245/17:27
stgraberI'm guessing that as the interface is already in /run/network/ifstate, it's going to be entirely ignored by ifupdown and so we won't get the event...17:28
slangasekyes, it forcibly bypasses if-up.d, it writes to /run/network/ifstate without locking, and it fails to use a proper 'instance' declaration for network-interface17:28
stgraberI'm wondering if just removing it would be enough17:29
slangasekstgraber: so it looks like an open-iscsi-specific failure after all17:29
stgraberjamespage: can you try that? ^17:29
jamespagestgraber: just doing the verbose boot - one second17:29
slangasekcjwatson: you seem to have written /etc/init/iscsi-network-interface.conf; do you recall why you were trying to prevent /etc/network/if-up.d scripts from being run for an iscsi interface?17:30
stgraberslangasek: we are going for dinner now, if it's confirmed that it works fine without the upstart job, I'll just remove it and upload to -proposed17:31
slangasekbug #45776717:31
ubottuLaunchpad bug 457767 in partman-iscsi (Ubuntu Karmic) "karmic: iSCSI root: boot hangs on starting iscsid" [High,Fix released] https://launchpad.net/bugs/45776717:31
slangasekstgraber: enjoy :)17:31
SpamapSslangasek: I would concurr with stgraber's assessment, this script does look like its our culprit.17:31
SpamapSslangasek: or, your assessment, somebody's17:32
slangasekSpamapS: yep - question is how we fix it... we shouldn't just drop it without taking care on upgrade to make sure users don't have configuration for the interface in /etc/network/interfaces that's going to cause the system to blow up on next boot17:32
SpamapSyeah this bug-ectomy requires some delicate scalpel work17:33
SpamapSI'm not sure why the author wanted to avoid the *.d scripts17:34
slangasek"the author" being cjwatson17:34
SpamapSok, so we can ask him. :)17:34
SpamapSbecause that is precisely the issue we have, is that they were avoided17:35
slangasekyep17:35
=== deryck[lunch] is now known as deryck
jamespageSpamapS, stgraber, slangasek: --verbose boot - http://paste.ubuntu.com/706249/17:37
=== dendrobates is now known as dendro-afk
slangasekjamespage: yep, that's consistent with our theory.  kill /etc/init/iscsi* and try again?17:38
jamespageslangasek, appears to be much happier17:39
jamespagestgraber: ^^17:40
jamespageno network failsafe and I can see log data for eth0 as well as lo17:40
slangasekjamespage: thanks; can you send that info to the bug?17:43
jamespageslangasek, done17:46
slangasekjamespage: cheers :)17:46
jamespagenp17:46
SpamapSslangasek: I don't see anything in the default server install that would be "bad" during if-up.. I was thinking though, don't we need to make sure eth0 is never brought down?17:51
slangasekSpamapS: certainly17:52
SpamapSI don't think it will be brought down but wondering if maybe some scripts down/up the interface.17:53
slangaseknothing should for interfaces not explicitly configured to have such things done17:55
slangasek(e.g., bridge interfaces)17:55
SpamapSjust trying to reason why we'd want to avoid those scripts17:55
SpamapSa lot of them make some pretty strong assumptions17:55
SpamapSthough one might be able to argue that most iSCSI root boxes don't share the iscsi interface with the general network connection... it should still be possible17:56
slangasekwell, as cjwatson admits in his comment, this is a layering violation... and now it's biting us :)17:57
slangasekjamespage: I've struck out as far as finding anything in your apt log that will explain it; the only relevant change I see is fglrx, and the only effect that had should have been reproducible with the gfxpayload change.  Could you try downgrading fglrx to version 2:8.881-0ubuntu3, to see if it does bring back the segfault?18:44
hallyn_smoser: do you mind if i fwd your testcase for the libvirt pty probelm to the m-l?18:52
smoseroh sure, they'll have a field day.18:56
smoser:)18:56
hallyn_do you have your latest version somewhere?18:57
hallyn_otherwise i can just use the first version, that's fine.18:59
smoseri ended up trashing the instance that had your iprovements19:00
smoserhttps://gist.github.com/1251979 is where ih ad what i had.19:01
hallyn_smoser: thanks much19:01
micahgpitti: what was the question for me, I seem to have missed it?19:09
=== yofel_ is now known as yofel
=== Quintasan_ is now known as Quintasan
=== dendro-afk is now known as dendrobates
=== SanbarCo1puting is now known as SanbarComputing
micahgpitti: it seems that librpc-xml-perl was demoted prematurely20:18
micahgpitti: oh, nevermind..20:19
=== chrisccoulson_ is now known as chrisccoulson
=== plars is now known as plars-afk
micahgcjwatson: when we merge dpkg for P, are we going to get the hardening flags emitted like Debian is doing?20:47
=== dendrobates is now known as dendro-afk
cjwatsonslangasek,SpamapS,stgraber: all I can really say from this vantage is that it caused a problem at the time, as noted in the comment in the script; I'm having trouble parsing my comment about /etc/network/*.d/ scripts, so it's entirely possible I was just confused20:50
cjwatsonmicahg: I intend to keep the flags in the environment for precise, because otherwise we'll have to convert too many packages to avoid lossage20:51
micahgcjwatson: i.e. different behavior than Debian?20:51
cjwatsonmicahg: for P, yes20:51
cjwatsonalthough packages that have been converted to the new scheme in Debian shouldn't break; at worst, they'll have the flags specified twice20:52
micahgcjwatson: is this for stuff we already have in our environment or everything?  My concern is that Debian is starting to abandon hardening-wrapper usage and starting to use the dpkg buildflags20:52
cjwatsonmicahg: packages that ask for dpkg-buildflags output will get it, don't worry20:53
micahgcjwatson: awesome, thanks :)20:53
cjwatsonI'm just not going to remove stuff that wew already have in our environment20:53
cjwatsonnot until Q20:53
micahgyeah, that makes sense for an LTS20:53
cjwatsonstgraber: it's possible I regarded manual as a hack and didn't want to depend on it20:54
cjwatsonbut I don't appear to have recorded my thought process very clearly, sorry20:54
micahgcjwatson: maybe we should just leave it in the env unless it'll break stuff, ideally we do want hardening by default (but we can save that discussion for UDS Q :))20:54
cjwatsonstgraber: I am a little concerned that there may be upgraded systems around that don't use the manual method20:54
cjwatsonmicahg: the things in the environment at the moment aren't hardening20:54
micahgah20:55
cjwatsonthey're default optimisation settings and -Wl,-Bsymbolic-functions20:55
cjwatsonwe want to migrate to dpkg-buildflags in the long term because it offers more flexibility20:55
cjwatsonfor example it will make it easier to test-build the world with different compiler flags without having to use a compiler wrapper20:56
SpamapScjwatson: its probably worth a review of the other methods and if-up.d scripts to see if they do anything we might perceive as dangerous to an iSCSI root.. if we can't find anything.. maybe just axe the upstart job.20:57
cjwatsonactually20:59
cjwatsonso the problem was that if you did an install with the installer acquiring its network settings by DHCP, before my hack in partman-iscsi, it got 'iface eth0 inet dhcp'21:00
cjwatsonthen when you did 'ifup eth0', it ran dhclient, which tore the interface down and set it back up again21:00
cjwatsonand the world imploded21:00
cjwatsonI think you should ignore my comment about .d scripts, it seems to be a red herring21:00
keesmicahg: yeah, the trick is watching for packages that convert from hardening-wrapper/-includes to dpkg-buildflags to make sure they include +pie,+bindnow21:01
cjwatsonso what this upstart job does is force ifup to do nothing for that interface, even if /etc/network/interfaces is misconfigured21:01
cjwatsonremoving that *might* be safe, but I would prefer to have say an 'ifpretendup' interface in ifupdown21:01
cjwatsonor 'ifup --pretend' or whatever21:02
micahgkees: right, that's what I was asking about in my meek way :)21:02
cjwatsonwhich would force the interface to be considered up (in ifstate) but not actually do any work21:02
cjwatsonthen we could use that in the upstart job (and fix the instance bug) and it would then be able to emit the right upstart event21:03
cjwatsonalthough a temporary hack that might do the job for now would be to emit that event by hand21:04
cjwatsonnot the right fix but it would kill the delay21:04
cjwatsonand should be no worse than what was there before21:04
keesmicahg: I'd like to figure out some way to do build regression testing in Debian and Ubuntu that would alert when a package suddely stopped building with a flag or something, but it's seriously non-trivial to get right21:05
* jdstrand waves to kees21:06
keeshi jdstrand! :)21:06
micahgkees: emit the build flags at build time, then have LP parse the logs and fail if there's a regression?21:06
jdstrand:)21:06
keesmicahg: yeah, but right now the bulk of that isn't visible in ubuntu's builds since we enforce it in the compiler without flags21:06
ajmitchyou'd want to build the same source both with & without flags to narrow the cause of build failures down21:07
stgrabercjwatson: http://paste.ubuntu.com/706334/ for the workaround?21:08
slangasekstgraber: that doesn't solve the issue.  If we're going to try to use this as a workaround, we ought ta have this job just call /etc/network/if-up.d/upstart with the right args21:10
slangasek(net-device-up is not the event we care about, it's static-networking-up)21:10
hallyn_smoser: well...  resposne was not unexpected but still unfortunate :)   pls let me know if my patched libvirt worked for you21:10
cjwatsonyeah, may as well not add *more* layering violations I guess21:11
cjwatsondoes my proposed interface extension to ifup sound reasonable longer-term though?21:11
cjwatson(static-network-up not static-networking-up ...)21:12
slangasekcjwatson: what does "pretend" give you that just getting the interface properly set as "manual" would not?21:12
slangasekbecause the upstart hook may not be the only one we care about running21:12
slangasekI dunno, would we want avahi-autoipd to run?21:13
cjwatsonmay be misnamed, what I want it to do is not actually do the main body of manipulating the interface21:13
cjwatsonI'm happy for it to run all the hook scripts21:13
cjwatson(as I say I think my two-year-old comment was misleading)21:13
slangasekwell, perhaps not unless we FIX that hook.. again... since it's adding a stupid route instead of bringing up an address21:14
stgrabercjwatson, slangasek: http://paste.ubuntu.com/706338/21:14
cjwatsonuseless use of env :-)21:14
stgraberoh, indeed ;)21:14
slangasek:)21:14
slangasekotherwise, provided that works I think it looks good21:14
cjwatsondo we need to handle ipv6?21:14
cjwatsonappreciating the irony of me asking stgraber this21:15
slangasek:-)21:15
slangasekthe hook doesn't distinguish by addrfam21:15
cjwatsonI'm guessing open-iscsi is far too stupid to handle ipv621:15
stgraberhaven't seen any hardware doing IPv6 PXE yet21:15
* ajmitch didn't think PXE was specced yet for ipv621:15
cjwatsonit is21:15
cjwatsonwell, ish21:15
ajmitchoh? that's useful21:15
cjwatsonit is in uefi, I'm not sure about bios21:15
cjwatsonalthough only a uefi version nobody has yet21:16
cjwatsonso still chocolate teapot level of usefulness21:16
stgraberjamespage: still around?21:16
slangasekregardless, the upstart hook fires once for each interface and doesn't care about address family; no point trying to make the open-iscsi job fancy21:17
jamespagestgraber, yep - running iscsi root tests :-)21:17
stgraberjamespage: awesome. Can you move the upstart script back into /etc/init, revert the changes to /etc/network/interfaces (so we have the inet manual in there) and apply this diff: http://paste.ubuntu.com/706339/?21:17
jamespagestgraber, just cooking one now - no problem21:18
stgraberjamespage: then try again but with "inet dhcp" instead of "inet manual" and check that it works too and finally with the two lines commented again21:18
stgraberthat should cover most of the use cases ;)21:18
jamespagestgraber: all three of those test cases work great with the patch applied21:27
jamespage\o/21:27
stgraberyeah!21:29
smoserhallyn_, tested your suggested patch21:31
smoserhttp://paste.ubuntu.com/706342/21:31
smoseris what i get21:31
stgraberskaet, slangasek, cjwatson: Should I push that fix to -proposed and if Daviey really wants it we copy it and rebuild server?21:31
smoseryou should be able to easily recreate this now that we know how to make it so that /dev/pts/0 wont be availalble.21:31
cjwatsonstgraber: yes please21:34
cjwatson22:26 <slangasek> stgraber: ^^ so open-iscsi to -proposed please :)21:34
cjwatson(#ubuntu-release)21:34
bdrung_andersk: mozilla-devscripts fixed21:36
ev@pilot out21:43
=== udevbot_ changed the topic of #ubuntu-devel to: Beta 2 Released | Archive: Final Freeze | Development of Ubuntu (not support, not app development) | build failures -> http://bit.ly/or6CHJ | #ubuntu for support and general discussion for hardy -> oneiric | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
anderskbdrung_: Alright, trying that.21:44
hallyn_smoser: ok, don't know why, that's gonna be lower priority21:45
bdrung_andersk: how long will your test take?21:45
anderskbdrung_: Almost done, I think.21:45
anderskI recompiled xul-ext-lightning after adding ‘Breaks: ${xpi:Breaks}’ to all its debian/control stanzas, and ended up with what appears to be the right thing.21:46
anderskAnd the result installs and works.21:47
bdrung_andersk: last chance to prevent the upload of m-d 0.2921:48
anderskI say ship it!  :-)21:49
achiangwhen does DIF usually occur relative to opening the archive?21:50
micahgachiang: 7-9 weeks in21:52
achiangmicahg: ok, thanks21:52
achiang7-9 weeks to get a new package in then. :-/21:53
micahgachiang: no, you can request new stuff up to feature freeze, DIF is the automatic sync21:53
achiangoh, how long is feature freeze?21:53
micahgachiang: 2 months before release21:54
achiangmicahg: ok thanks21:54
micahgachiang: the earlier the better though :)21:54
achiangmicahg: yes, it's a somewhat tricky package, and i'm going the debian route21:54
achiangmicahg: if i can't get it into debian before feature freeze, is there an ubuntu way to get it into universe?21:55
micahgachiang: sure, REVU is still open for the moment21:56
bdrung_but the debian way is the easier way21:56
achiangbdrung_: yes, i got my package's dependency into debian just last week21:57
achiangbdrung_: but that took a while. i'm concerned about this new package i'm working on21:57
bdrung_achiang: what package?21:57
achiangbdrung_: https://forge.betavine.net/scm/?group_id=76 -- wader-core is a drop-in, API compatible replacement for ModemManager21:58
achiangbdrung_: it supports Vodafone modems really well21:58
Laneyyou can probably ask the same sponsor to look at this one21:58
achiangLaney: yes, that was my plan21:59
sammyanyone using auth-update-config and authing from ldap?22:07
sammysupposedly its changes to common-password in pam.d should allow using passwd to change ldap passwords. everything else is running smoothly22:08
sammynm google is my friend :)22:09
bdrung_andersk: released :)22:21
anderskCool.  How are we going to handle rebuilding the extension packages against the new version?22:24
bdrung_andersk: it requires manual work (adding ${xpi:Breaks})22:26
bdrung_andersk: m-d will be synced to precise. for which release do you need this feature?22:26
anderskbdrung_: I dunno, is oneiric likely to see Firefox 8 or Thunderbird 8 as an SRU?22:27
bdrung_yes22:28
anderskThe status quo seems to be that a Thunderbird 8 SRU in oneiric will break Lightning, like Thunderbird 7 did during the dev cycle, and it would be nice to have the package manager detect that before it causes a real problem.22:31
micahgandersk: we'll be SRUing lightning at the same time22:32
bdrung_micahg: will you SRU mozilla-devscripts too?22:33
bdrung_micahg: or just patch the heavy stuff in?22:33
micahgbdrung_: not planning on it22:33
chrisccoulsonWhat feature in mozilla-devscripts?22:43
bdrung_chrisccoulson: m-d 0.29 adds a ${xpi:Breaks}23:42
=== dendro-afk is now known as dendrobates

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