[00:00] * SpamapS installed originally from Xubuntu [00:00] I actually like Unity + Compiz when they work. A lot. Just tired of having to restart them because of some weird issue. [00:00] has been much better the last 2 weeks [00:57] SpamapS: there's always unity-2d [00:58] micahg: indeed, it does seem to survive longer than unity between weirdness/crashing === dendrobates is now known as dendro-afk === dendro-afk is now known as dendrobates [01:46] hi. I am scanning through archive.ubuntulinux.org, and I noticed that some .deb files are fairly small (just a few kb), like http://archive.ubuntulinux.org/ubuntu/pool/multiverse/u/ubuntu-restricted-extras/. why is that? shouldn't they be megabytes given how much software is in them? === rextsai is now known as chihchun [01:52] photon, those are probably pseudo-packages, not containing much information themself, but just dependencies on other packages with the actual stuff. [01:53] That package in partiular is a metapackage, which pulls in other packages. [01:53] I looked into the .deb archive and in /DEBIAN/control, there are only recommendations, not dependencies, and even those are far less than what apt-get install ubuntu-restricted-extras would install. so I'm confused [01:54] maybe I'm looking int he wrong file. [01:55] Yes, recommends are installed by default, so the recommended packages get installed. [01:55] It means that you can remove one or more of the recommended packages, and the rest of the packages don't get removed with them. [01:56] Got it. === dendrobates is now known as dendro-afk === dendro-afk is now known as dendrobates [04:05] Good morning [04:06] doko_: vala FTBFS> looking [05:38] good morning === tilgovi_ is now known as tilgovi [07:30] @pilot out === udevbot changed the topic of #ubuntu-devel to: Beta 1 released | Archive: Feature/UI 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: [07:30] oops [07:30] heh [07:32] could i get a core dev to do me a favor and accept the series nomination on bug #848687? [07:32] Launchpad bug 848687 in linux (Ubuntu) "DRI applications hang after DPMS standby on i965" [Undecided,New] https://launchpad.net/bugs/848687 [07:39] good morning [07:39] broder: done [07:41] pitti, it seems like we need to bring libgdamm4.0 back if we want glom buildable at all [07:41] dholbach: ah, glom isn't in Debian, so they could remove it [07:42] yep [07:42] I guess someone can reupload it [07:42] SpamapS: thanks :) [07:42] pitti, ok - I'll have a look - seems like glom does not build - maybe a more recent version will fix it [07:44] dholbach: upstream commented as such, but one of the build depends was removed [07:44] presumably that very from above, libgdamm [07:44] I think upstream has a PPA - I'll have a look how much of their work we can reuse [07:44] I'll let you know [07:44] sorry, missed that somehow... [07:45] pitti, maybe glom should be part of the please-update-these-desktop-packages overview, so we don't let old versions rot in the archive again :) [07:45] nah, it's in universe [07:45] a lot of universe packages are like that unfortunately :/ [07:46] dholbach: shows up here where it belongs: http://qa.ubuntuwire.com/uehs/no_updated.html, unfortunately, we need more people looking here :) [07:46] ok :) [07:51] * micahg actually thinks that page is out of date... [07:51] * micahg moves this to -motu === vila is now known as babune === babune is now known as vila === dholbach_ is now known as dholbach === doko_ is now known as doko [08:44] I have been trying to unblock glom in Debian for ages :( [08:44] current problem is jsogo refusing to maintain goocanvas properly [08:46] Laney, what's the issue? [08:52] the current releases need a newer goocanvasmm which needs a newer goocanvas [08:54] ah ok, for now, I guess I just get 1.18.3 into Ubuntu which is the latest stable and builds [08:54] for P we can try something new [08:54] is it hard to get a new goocanvas into Debian? [08:54] kind of is if the maintainer doesn't want to do it [08:55] would the 1.18 release work? [08:56] yes, it looks good [08:56] I'm just sorting out a few other small issues while I'm at it [08:57] we just need to get gdamm4.0 added back to the archive [08:57] but I uploaded it already [09:35] can somebody get libgdamm4.0 out of NEW please? it was removed a bit too quickly (glom needs it) === zyga is now known as zyga-afk [10:12] dholbach: done [10:12] thanks pitti [10:13] dholbach, do you still need an armel testbuild ? [10:13] ogra_, no it's all sorted [10:13] thanks ogra_ [10:13] :) [10:39] * doko can't decide if the archive looks like a garbage dump or a mortuary ... [10:40] looks like a big city; shiny center, but some suburbs are really chabby [10:40] "shabby" [10:41] pitti: I like this metaphor :) [10:43] pitti: does this mean that a bulldozer needs to be driven through some suburbs? [10:44] ajmitch: in some cases a bulldozer, in some cases a citizen's initiative with some mortar and paint :) [10:45] hildon or gnome 2 panel applets were definitively in the bulldozer class, but most packages have relatively easy fixes [10:45] it's sad to see the applets go :) [11:06] can somebody bulldoze libgdamm4.0 out of binary new? :-P [11:07] fun ... [11:07] Checking if libc on this machine contains: [11:07] grep: library_contents: No such file or directory [11:07] vsprintf: No, I don't think [11:07] grep: library_contents: No such file or directory [11:07] _doprnt: NO, THIS IS A PROBLEM: NO VSPRINTF AND NO _DOPRNT [11:07] SPIM WILL NOT RUN PROPERLY [11:07] grep: library_contents: No such file or directory [11:07] vfprintf: No, I don't think [11:07] grep: library_contents: No such file or directory [11:07] _doprnt: NO, THIS IS A PROBLEM: NO VFPRINTF AND NO _DOPRNT [11:07] SPIM WILL NOT RUN PROPERLY [11:07] grep: library_contents: No such file or directory [11:07] strtoul: No, I don't think [11:07] grep: library_contents: No such file or directory [11:07] strtol: No, I don't think [11:07] grep: library_contents: No such file or directory [11:07] memcpy: No, I don't think [11:08] doko: I'm guessing multiarch fallout [11:08] sure, I just did "like" the grep approach [11:09] dholbach: one moment [11:09] cjwatson, thanks muchly === zyga-afk is now known as zyga [11:11] cjwatson, ahh, already done [11:12] ah, ok, cool [11:13] fantastic, thanks === ryanakca_ is now known as ryanakca [11:44] nice, we're down from 661 to 560 FTBFS bugs today [11:48] micahg: Congrats \o/ === MacSlow is now known as MacSlow|lunch [12:05] Sweetshark: What are the odds of the LO FTBFS on i386 getting fixed today? FYI, it's breaking amd64 live CD/DVD builds at the moment. [12:06] mvo: I could use help with bug 848907; I don't see why it should have broken recently [12:06] Launchpad bug 848907 in apt (Ubuntu) "apt crashes on initial installation of oneiric" [Undecided,New] https://launchpad.net/bugs/848907 [12:09] ScottK: Im currently building with a fix. but LO has quite some buildtime ... [12:11] siretart, ping [12:11] ScottK: It just went past the critical corner, so its looking good. [12:12] cjwatson: is that reproducable? [12:13] mvo: I reproduced it after seeing a user report of the same thing, which he's experienced both yesterday and today [12:13] mvo: haven't yet figured out how to reproduce it from the command line [12:14] regfree crash suggests memory corruption of some kind, but getting valgrind into d-i is ... painful [12:14] cjwatson: right, but its reproducable by installing kubuntu in a vm with the altnerative CD? [12:15] that's all I did, yes [12:16] thanks, I will rsync me updated images and try it out then [12:16] I would expect Ubuntu to do the same thing; we haven't got to the flavour-specific parts of installation at this point [12:16] I just made a 10G disk image and did a use-entire-disk install [12:16] en_GB locale, otherwise all defaults [12:17] will try it under strace now [12:17] cjwatson: great, the rsync is running. you did the install inside kvm I assume? is there a chance to get a slightly better readable backtrace then from the screenshot ? [12:17] kvm yes; maybe, will try hacking about at base-installer [12:17] cjwatson: I can poke the code in the meantime, there were some changes in the cdrom autodetect code recently (~4 weeks ago) that might be the issue [12:19] mvo: I think this is recent though, I didn't see it when I was preparing the partman-crypto fix this guy was testing [12:19] mvo: I wonder if it's something to do with the recent eglibc upload (and hope it's not) [12:21] I think the backtrace must be being printked or something; I guess I'll just leave it on a sacrificial console [12:27] Laney, did the comment should go to bug 831235? [12:27] Launchpad bug 831235 in gdcm (Ubuntu Oneiric) "gdcm version 2.0.17-3.1 failed to build in oneiric" [High,Confirmed] https://launchpad.net/bugs/831235 [12:28] yes [12:28] ScottK: the fix is uploaded to chinstrap and waiting for sponsoring. [12:28] doko: as in, the Debian version builds fine [12:29] Laney, yes transient build failure, you shouldn't upgrade gcj during a test rebuild ;) [12:29] the current one works? [12:29] mvo: reproduced, but the backtrace goes all over tty1 even if the current console is tty3 :-( [12:30] there were a lot of probems that we helped the maintainer with in Debian [12:30] yes [12:30] * cjwatson extracts the strace [12:30] still running [12:30] arch/indep issues [12:31] is this bugs 847591 still in progress ? or already fix but not release [12:31] Launchpad bug 847591 in packagekit (Ubuntu Oneiric) "Error org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 127" [High,In progress] https://launchpad.net/bugs/847591 [12:34] Sweetshark: Thanks. === zyga is now known as zyga-afk [12:35] mvo: http://people.canonical.com/~cjwatson/tmp/base-installer.trace.xz - probably includes lots of junk, I'm about to start having a look [12:36] that's attaching strace to bootstrap-base.postinst after run-debootstrap has been forked [12:40] I suspect it isn't helping that locale-gen removes /usr/lib/locale/C.UTF-8 which is owned by the libc-bin package [12:40] * cjwatson goes to fix that [12:49] ScottK: uploaded (thanks pitti) [12:54] doko: you are right, it is transient. I can't get on https://buildd.debian.org/status/logs.php?pkg=gdcm&ver=2.0.17-3.1 to remind myself what the problem was. [12:54] get logs from* [12:55] Laney, I had given it back: https://launchpad.net/ubuntu/+archive/test-rebuild-20110816/+build/2693757 [12:55] great [12:55] I just knew 3.1 failed and -4 did not, but, well it's not reproducible so "oh well". [12:56] oh, the red text gives you the log [12:56] that does not look like a link. === zyga-afk is now known as zyga === MacSlow|lunch is now known as MacSlow [13:37] mvo: aha, reinstall libc-bin in /target after the crash and then apt segfaults again [13:38] mvo: better screenshot attached [13:39] so almost certainly due to: [13:39] * debian/patches/localedata/locale-C.diff: Don't include ISO14651 [13:39] collation rules in C.UTF-8 locale. [13:39] but I don't know if this represents an eglibc bug or a wrong assumption in apt [13:41] * cjwatson installs gdb and valgrind to try to dig further [13:42] micahg: can you confirm you are now on the DMB mailing-list? [13:44] nice cjwatson! that is really much more helpful [13:49] mvo: ... and now valgrind output attached [13:52] cjwatson: thanks, I wonder if the compilation error is new or maybe triggering the bug [13:53] pitti: good morning, thanks for sponsoring some of my patches. i see that you created bzr branches... should i have done that on my own to save time? [13:54] achiang: I did? [13:54] mvo: it doesn't happen in LC_ALL=C [13:54] pitti: well, someone created bzr branches. :) see LP: #770862 as an example [13:55] now, I wonder if I can recreate it in an unstable chroot [13:55] cjwatson: *ick* it doesn't? [13:56] mvo: indeed; that's why I was suspecting that localedata change [13:56] if I can recreate it in unstable, I'll ask debian-glibc about it [13:56] there's no rationale for the change [13:57] achiang: presumably the auto-importer [13:57] pitti: ah, interesting. ok, thanks, i won't worry about it then [13:57] does the publisher run every now and then nowadays? seems like libgdamm4.0 still did not make it through binary new [13:58] it's crashing [13:58] ah ok :/ [13:58] I'll escalate === zyga is now known as zyga-afk [13:58] thanks a lot cjwatson [14:00] cjwatson: thanks, what channel? I would like to follow this - fwiw I think there is a potential double free (or delte in this case) in the code that it worth fixing [14:01] mvo: the mailing list [14:01] ok [14:02] WTF? alternate installer from sunday doesn't have a kernel it can install? [14:03] pitti: hi! it just occurred to me that we don't have an equivalent of gdm-guest-session for lightdm [14:03] No. [14:04] hallyn: Look at the newer one. [14:04] jdstrand: no, it's built into lightdm [14:04] pitti: oh? are there docs on that? [14:04] hallyn: see my discussion with mvo immediately above your question [14:04] ScottK: ok, thanks === chuck_ is now known as zul [14:05] jdstrand: docs for what? it's in the indicator and also in the greeter [14:05] ScottK: actually that wasn't really it [14:05] ScottK: that broke something slightly different ... [14:06] Oh? [14:06] pitti: sorry, I was not at all clear. I meant the apparmor profile [14:06] ScottK: the weekend problem was wrong udebs on the CD, but this is apt falling over when trying to install the kernel on the target system [14:07] or actually when trying to detect what to do [14:07] cjwatson: I have some code that may fix the issue, it certainly fixes the double free but I'm not sure if that is enough. it seems to be only triggered (the double free) if there is a error in the regexp compilation [14:07] jdstrand: hm, it ought to, but now that you mention it I can't see it [14:08] pitti: shall I file a bug? [14:08] jdstrand: please [14:08] ok [14:08] jdstrand: I discussed the four bugs you mentioned on Friday with Robert this morning, FYI [14:08] jdstrand: one is fixed, one committed, I just sent an MP for the third [14:09] pitti: I saw. thanks! I have updated our lists accordingly [14:10] cjwatson: (sorry, i'm not sure which you're pointing to, but it sounds covered, so great :) [14:11] provided with say -lzeitgeist-1.0 can I find out to which this shared library it will link to? [14:11] means the actual file path [14:11] or even the name would be enough [14:13] pitti: fyi, bug #849027 [14:13] Launchpad bug 849027 in lightdm (Ubuntu Oneiric) "lightdm does not provide an equivalent to the gdm guest session AppArmor profile" [Undecided,New] https://launchpad.net/bugs/849027 [14:17] jdstrand: thanks, bumped accordingly [14:18] cool, thanks [14:24] cjwatson: if I upload a new version to my PPA will you be able to easy test if my fix is sufficient (assuming the double delete is actually the real problem here) === kentb is now known as kentb-afk [14:26] mvo: I think so [14:26] njpatel, re bug 817691, do you really mean glibc, not glib2.0? [14:26] Launchpad bug 817691 in glibc (Ubuntu) "[Oneric] unity-panel-service crashed with SIGSEGV in getenv()" [Critical,Confirmed] https://launchpad.net/bugs/817691 [14:31] superm1: Would you please look at my comments in bug 816199 and reconsider the fix? [14:31] Launchpad bug 816199 in dkms (Ubuntu) "dkms_packages.py crashed with ValueError in _apt_pkg(): package does not exist" [High,In progress] https://launchpad.net/bugs/816199 [14:32] ScottK: honeyd> ack; would you like me to take this one? [14:32] slangasek: Yes. Please. [14:32] ok, will do [14:32] Thanks. [14:34] cjwatson: I uploaded it to https://launchpad.net/~mvo/+archive/ppa/+packages?field.name_filter=&field.status_filter=published&field.series_filter=oneiric [14:34] cjwatson: its building currently [14:34] doko, yeah, going by what we found on Google and the other bugs in firefox etc with the same trace [14:35] njpatel, I'd rather assume some kind of memory corruption elsewhere. really doesn't look like eglibc's fault [14:37] doko, it might well be, maybe gettext? [14:38] njpatel, then why assign it to eglibc, both ubuntu and upstream? [14:40] doko, because the crash is in getenv and we needed some opinions from people familiar with that? I can guess it's in gettext but it doesn't make it so... [14:41] doko, if you have a better place let me know and I'll change it asap [14:41] doko, did you look at the linked bug list for the other projects? [14:43] njpatel, there is this one new report in unity, the other list are up to years old [14:43] urgh, really? what the hell was I reading then :/ [14:43] * njpatel looks [14:44] njpatel, and the fact that every of these apps is using gtk, is not very assuring [14:45] the top 8 reports are from 2011, most of them after june/july [14:46] doko it does seem gtk is involved in most of them [14:47] njpatel, e.g. bug 278095 is about corruption of the env [14:47] Launchpad bug 278095 in at-spi "MASTER crash in getenv() ... spi_atk_bridge_exit_func()" [High,New] https://launchpad.net/bugs/278095 [14:49] doko, yep, saw that, so unity-panel-service, gnome-keyring from O and evince and gnome-session from N [14:50] doko, thanks, I'll move it back to unity for now and ask upstream gtk if they have any ideas [14:54] pitti, didrocks, mterry, Sweetshark: any idea of the relevance of bug 725250? [14:54] Launchpad bug 725250 in lo-menubar (Ubuntu) "[MIR] lo-menubar" [Undecided,Confirmed] https://launchpad.net/bugs/725250 [14:55] can someone tell me why the notification area seems to have completely disappeared from my panel due to an update sometime in the past couple of weeks? === kentb-afk is now known as kentb [14:56] doko: no, it's too broken for that [14:56] ScottK: fwiw, today's alternate installer is no better :( [14:56] doko, yeah, I don't think it's prime time yet [14:57] doko: bug updated [14:58] hallyn: yeah, on it :-) [15:00] irc admins available? need the bot back on #ubuntu-x [15:00] bugbot that is [15:01] slangasek: bug 553745 has some mention of it occuring again in Oneiric - subsequently I've removed the bugpattern for it so we can get another crash report in [15:01] Launchpad bug 553745 in plymouth (Ubuntu Maverick) "plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()" [High,Triaged] https://launchpad.net/bugs/553745 [15:01] sure bdmurray [15:01] someone with buildd knowledge, is it actually possible to call apt-get source to fetch a source package from ftpmaster.internal on a buildd during a build? [15:02] bdmurray: right, was talking to Jason about that - thanks, will be happy when we can get more info [15:07] cjwatson: great, thanks :) [15:10] pitti: Could you review / merge https://code.launchpad.net/~brian-murray/apport/ubiquity-dupe-sig-improvements/+merge/75050 ? [15:12] bdmurray: merged, thanks [15:17] Riddell: "Give david.wonderly access to upstream docs" is the only remaining WI for desktop-o-kubuntu-documentation-review; is that blocked, or just needs to happen? [15:17] pitti: I've no idea, I'm not working on Kubuntu [15:18] pitti: but David is DarkwingDuck on #kubuntu-devel [15:18] Riddell: right, but that sounded like an ACL issue [15:18] like adding him to a team or so [15:18] Riddell: I'm happy to postpone that one if you want, just reviewing leftover WIs [15:19] I have no opinion, you should ask the kubuntu team [15:19] ok [15:34] cjwatson: any luck with the ppa version? [15:35] doko, hmmm, bug 831256 is a bit weird [15:35] Launchpad bug 831256 in dehydra (Ubuntu Oneiric) "dehydra version 0.9.hg20110609-1ubuntu1 failed to build in oneiric" [High,Confirmed] https://launchpad.net/bugs/831256 [15:35] i don't see how that fails :/ [15:41] mvo: not yet, I was chasing things down in eglibc: see thread at http://lists.debian.org/debian-glibc/2011/09/msg00036.html [15:48] cjwatson: aha, nice! [15:52] but it's true that segfaulting is a bad response to regcomp failing [15:52] just a moment, testing [15:54] mvo: right. that does indeed fix the segfault, thanks, and valgrind is now happy. of course we still need to fix the eglibc bug since now the regexes are incorrectly not recognised, and I suspect this will break other things [15:54] hopefully aurel32 will reply quickly === beuno is now known as beuno-lunch [15:54] hi, could someone please nominate https://bugs.launchpad.net/landscape-client/+bug/813477 for maverick and natty? [15:54] Launchpad bug 813477 in Landscape Client "Update landscape-client to 11.07.1.1" [High,Fix committed] [15:55] ahasenack: done [15:55] I would if the ... oh, never mind [15:56] cjwatson: yeah, much agreed, thanks a bunch for testing, I will upload the fix next [15:58] cjwatson: thanks === paulliu is now known as paulliu_gd === zyga-afk is now known as zyga [16:08] barry: ping re libfsobasics, libfsotransport; I believe these could be synced? [16:14] seems that libfsobasics is blacklisted currently, is there a way for me to see why? [16:14] tjaalton: the blacklist is unfortunately not synced to anything public; let me look for ou [16:14] you [16:14] slangasek: thanks [16:15] i know it ftbfs [16:15] tjaalton: in fact, I don't see it in the blacklist - how did you determine that it's blacklisted? [16:15] https://launchpad.net/ubuntu/oneiric/+localpackagediffs?field.name_filter=libfsobasics&field.package_type=all&field.package_type-empty-marker=1 [16:15] slangasek: I ran syncpackage [16:15] Laney: ooh [16:15] Launchpad autoblacklists when the Ubuntu version deviates AFAIK [16:15] right, so you have to override [16:15] chrisccoulson, given it back, and it did build. thanks [16:16] slangasek: http://people.canonical.com/~ubuntu-archive/sync-blacklist.txt FYI [16:16] cjwatson: oh, ok [16:16] cjwatson: where's the cronjob that syncs that? I have trouble figuring out how things get to that directory [16:16] slangasek: cocoplum:~lp_archive/dak/cron.sync [16:17] but yeah, in this case it's more confusing UI from syncpackage [16:17] got it [16:18] so, are the ffe-rules relaxed when fixing ftbfs bugs? :) [16:18] no [16:18] damn [16:18] exceptions may be more likely to be granted, but there's still a need for due diligence [16:19] (Unless you mean you've JUST fixed the FTBFS bug, which isn't a feature, and not subject to FF) [16:19] But yeah, "I've added 7 new features, and accidentally fixed a build failure at the same time" doesn't fly. :P [16:19] in these cases the packaging has been fixed too, but all our changes could be dropped as well [16:19] i'll file bugs then [16:20] Hi, plymouth is not shown at all on startup, except if I remove "vt.handoff=7" manually (also with CTRL+ALT+F1 during the boot process, it works). it works fine on reboot/shutdown. Any ideas ? [16:20] the system does not switch back to vt 1... it's strange :\ [16:21] how do you mean, "does not switch back to vt1"? [16:26] slangasek: so, the "wait for interfaces" change has ruffled some feathers. It seems that d-i always leaves behind a permanent 'auto ethX' after installation.. which means a lot of people are upgrading and then seeing a 2 minute delay [16:28] slangasek: I just wonder why I don't see anything (nouveau and kms work) [16:29] if I type "CTRL+ALT+F1" during the boot process, I see plymouth, otherwise I see nothing === deryck is now known as deryck[lunch] [16:37] SpamapS: wait for interfaces> yep, caught that the other day in the mail trail. Do you think it's feasible to clean that up on upgrade? Or maybe we should exclude interfaces that are configured as merely auto/dhcp in favor of checking for NM running? [16:37] bambee: you see plymouth during the boot process only when typing Ctrl+Alt+F1, *and* vt.handoff=7 is being passed? [16:38] I still think NM is a red herring; if NM was installed, then 'auto' lines would've been removed at the end of installation [16:38] oh? [16:38] slangasek: If it's relevant, bambee is on Kubuntu and it's not very good about transitions being invisible. [16:39] ScottK: well, so far we're discussing flavor-neutral bits of the boot [16:39] OK. [16:39] cjwatson: ok so there's already some intelligence there in NM's postinst? [16:39] Just mentioning it because he may be seeing stuff that's normally not visible in Ubuntu. [16:39] SpamapS: I gave specifics in the bug [16:39] oh I haven't caught up yet [16:40] * SpamapS reads [16:40] slangasek: exactly [16:40] cjwatson: do you have any suggestions on where to look next with bambee's handoff issue? Sounds like something falling down in the junction between grub, kernel and plymouth [16:42] an interesting info: it works just fine with {kubuntu,ubuntu}-11.10-desktop-amd64 (the livecd), and it does not work on my system [16:42] maybe plymouth:debug=file:/run/plymouth.debug (assuming oneiric) [16:43] bambee: could you try booting with that option, plus vt.handoff=7? [16:43] plymouth is supposed to display on vt7, not vt1 [16:43] indeed [16:43] slangasek: sure [16:43] cjwatson: I agree 100% with the position that a change in behavior at this change would be more harmful than good. I wonder if we can notify users in plymouth that the system is waiting for network configuration so, if nothing else, we know how to tell them to fix it when they report a slow boot. [16:43] (because otherwise the smooth transition from grub to plymouth wouldn't work) [16:43] SpamapS: that sounds straightforward and a good idea, yes [16:43] bambee: two major differences between the live CD and an installed system are the boot loader used, and the fact that plymouth is always started in the initramfs for a liveCD [16:44] that should be easy to do in failsafe.conf [16:44] bambee: you could eliminate one possible source of this noise by installing the cryptsetup package on your installed system, which will cause plymouth to be started from initramfs on the installed system [16:46] slangasek: trying with both (option+package), bbl [16:52] slangasek: well, nothing is generated in /run (/run/plymouth.debug does not exist) [16:52] /proc/cmdline: BOOT_IMAGE=/vmlinuz-3.0.0-11-generic root=UUID=5b2e8c3c-eacf-494b-bb21-2363d0d235f2 ro plymouth:debug=file:/run/plymouth.debug quiet splash vt.handoff=7 [16:53] bambee: blast; that's somewhat consistent with my own experiences trying to get output from plymouth in oneiric, but I was hoping cjwatson had the magic recipe (/run vs. /var/log) [16:54] bambee: so I'll take some time to hack on that today and see if I can figure out what's going on with logging. In the meantime, can you try installing cryptsetup? [16:54] (and rebooting, of course) [16:54] slangasek: sure, trying [16:55] maybe try /run/initramfs/plymouth.debug instead [16:55] historically I used /dev/.initramfs/plymouth.debug, actually, but nowadays somewhere under /run ought to work [16:55] I haven't debugged plymouth since the /run transition [16:55] I thought the log only got written to disk when /etc/init/plymouth-log.conf fired [16:56] cjwatson: one last question.. does d-i call ifblacklist_migrate.sh ? I only see it called in n-m's postinst configure if we're coming from before 0.6.5-0ubuntu12 .. [16:57] cjwatson: trying too [16:57] reboot [16:57] * SpamapS can probably c/o d-i and confirm that if you don't know off the top of your head ;) [16:57] hrmm, no patch pilot atm? [16:57] SpamapS: yes, it does, that was why I mentioned it [16:57] SpamapS: netcfg [16:57] ./finish-install.d/55netcfg-network-manager:11: sh /usr/lib/NetworkManager/ifblacklist_migrate.sh [16:58] cjwatson: ahh ok, thanks. :) [16:58] slangasek: true [16:59] slangasek: but that should happen as soon as the rootfs is writable [16:59] slangasek: actually, I don't think that applies to the debug log [16:59] plymouth-log is about /var/log/boot.log [16:59] cjwatson: ok - I thought it did, I'll have a look at the code a bit later to confirm. Anyway, it doesn't seem to work for me at all, possibly because the job races plymouth-stop [17:00] which interestingly appears to date from 2011-07-13 on mmy system, hmm [17:00] maybe we should make 'plymouth quit' do a last-ditch attempt to write the logs [17:00] hrmm [17:01] should maybe ubuntu-sponsors be subscribed to all merge proposals into lp:~ubuntu-branches owned branches? [17:01] dobey: effectively sponsors are, because they show up in the sponsorship queue [17:02] SpamapS: hi, finally finished the other ubuntu releases for #813477, can you upload the missing Maverick and Natty packages? [17:02] SpamapS: do they get spammed by LP for them though? or do they just show up on the queue page? :) [17:03] dobey: the queue. I don't think I'd want to read all of ubuntu-sponsors' bugmail ;) [17:04] ahasenack: ACK, will take a look later today, in the middle of a few things. [17:04] SpamapS: ok, thanks [17:04] slangasek: even with cryptsetup installed, it does not work [17:05] SpamapS: well this isn't bug mail, it's code review mail. :) [17:05] bambee: thanks, that eliminates one source of difference. The remaining major difference is the bootloader itself, which again points to the grub+kernel vt handoff [17:05] cjwatson: plymouth produces no debug outputs here :\ (even with /var/log) [17:05] SpamapS: hopefully it's not as bad as bugs mail [17:06] dobey: the queue is, IMO, a much better way to approach it, as things are sorted by their age.. so right away you know which thing has been sitting in the queue the longest [17:06] email is an interrupt driven system and favors the squeaky wheels [17:07] slangasek: oh! I still have a 2.6.38 kernel here (just in case) [17:07] I could test with the 2.6.38.... [17:07] bambee: "even with /var/log"> doesn't make sense [17:08] can somebody please get the glom packages out of binary new? [17:09] bambee: sure, that may also be a useful data point - even in the event that it works with the older kernel, this doesn't necessarily point to a kernel bug, but it at least gives us a place to look (i.e., git-bisect) [17:11] SpamapS: i take it you mean https://launchpad.net/ubuntu/oneiric/+queue ? [17:12] dobey: http://reports.qa.ubuntu.com/reports/sponsoring/ [17:13] cjwatson: ah, ok [17:17] slangasek: it does not work with linux-image-2.6.38 [17:18] I don't think it's kernel related... (it worked fine on natty with linux-image-2.6.38) === beuno-lunch is now known as beuno [17:18] cjwatson: http://paste.ubuntu.com/688477/ [17:18] (plymouth.debug) [17:19] dinner trumps plymouth debugging :-) === deryck[lunch] is now known as deryck [17:41] btw, "[ply-utils.c] ply_open_module:Could not load module "/lib/plymouth/renderers/x11.so": /lib/plymouth/renderers/x11.so: cannot open shared object file: No such file or directory" [17:43] bts --mbox show [17:44] arg, sorry === eyes_ is now known as EyesIsServer [18:13] bambee: the X11 plugin isn't intended to be used there [18:14] bambee: so that part is a red herring [18:14] oh ok [18:14] bambee: hmm. there really isn't anything obvious (to me) there. it looks as though plymouth's internal logic is doing all the right things, but it's just talking to nouveau wrongly :-( [18:16] so , is it a problem with nouveau ? don't compute it worked just fine on natty with linux-image-2.6.38... and the kernel is still the same... [18:16] I wouldn't expect so; presumably it's dealing with X just fine [18:17] plymouth has a variety of horrible code to talk to each of the different framebuffer implementations in different ways, since at the time we first put that all together they all had different requirements [18:17] it seems quite plausible that nouveau's requirements have changed and our plymouth package hasn't kept up [18:17] mhhh [18:26] can i bug someone to PLEASE sponsor a critical fix asap? https://code.launchpad.net/~dobey/ubuntu/oneiric/couchdb/fix-780972/+merge/75238 [18:31] dobey: looking at it now [18:31] cyphermox: thanks [18:39] hallyn: do you know what hvm is? (Bug #849224) [18:39]