=== asac__ is now known as asac [00:16] Can I ask for help with packaging here? [00:16] Hillshum, #ubuntu-motu [00:16] ok [00:22] kirkland - regarding bug 390504 (you were wondering when the fix was going to be released) [00:22] Launchpad bug 390504 in gnome-settings-daemon "gnome-settings-daemon should keep its opinions about my disk management to itself" [Low,Fix committed] https://launchpad.net/bugs/390504 [00:22] we're probably not going to bother waiting for the tarball now [00:23] chrisccoulson: yeah? [00:23] chrisccoulson: so sooner rather than later? [00:23] so the answer is "probably straight after A3" [00:23] hopefully;) [00:23] the current behaviour is quite annoying === rickspencer3_ is now known as rickspencer3-afk === tkamppeter_ is now known as tkamppeter [05:09] slangasek: ping [05:26] ccheney: hi [05:27] slangasek: did you buy your train ticket yourself or some other way? [05:27] slangasek: i just got an email apparently yesterday mentioning for me to get it done since the travel agency couldn't do it [05:27] * ccheney was out of town until tonight [05:28] ccheney: I bought mine myself on-line, through much toil [05:28] ccheney: the problem is that when you search for tickets, their website shows all kinds of tickets for trains that are sold out :P [05:29] how do you determine they are sold out? [05:29] by trying to buy it, and getting an error message [05:39] cjwatson: any chance you're around yet? [06:07] * liw notices that the gnome audio volume control widget's mute doesn't actually mute headphones [06:09] Godo morning [06:09] superm1: did you just do it? [06:10] pitti, no as it turns out it wasn't just a single commit that needed backporting [06:10] pitti, so once i realized it would be multiple i opted to just wait until after a3 when we can merge the new snapshot from debian [06:13] btw, whats up with the google plugin in firefox 3.5? [06:13] the search/sherlock plugin [06:14] it takes me to a google custom search page that is horrible [06:14] meh, no firefox for me this morning? [06:14] Starting program: /usr/lib/firefox-3.0.12/firefox [06:14] [Thread debugging using libthread_db enabled] [06:14] Program exited with code 01. [06:14] asac: ^ any idea? [06:14] it still worked last night [06:16] asac: ah, nevermind, it's a kirkland bug [06:16] pitti: howdy [06:16] kirkland: since yesterday's karmic, my ~/Private isn't automounted on login any more; did anything change in ecryptfs recently? [06:16] kirkland: good morning [06:16] pitti: yes, and i uploaded a fix for that about 5 minutes ago [06:17] kirkland: retroactive fixing, splendid! [06:17] pitti: upgrade to 77-0ubuntu1 and you should be fixed again [06:17] pitti: in the mean time, run ecryptfs-mount-private by hand [06:17] right, that's what I was doing [06:17] I just don't immediately realize it [06:17] and thus ssh hangs, firefox doesn't start, etc. [06:17] kirkland: thanks! [06:17] pitti: you bet, thanks for your alpha-patience :-) [06:31] is there a known issue with lost sound today? [06:37] superm1: are you in ~ubuntu-installer? [06:37] I just uploaded ubiquity, and then noticed that I cannot push the branch [06:38] ubiquity needed Yet Another Upload? [06:38] pitti, yeah i am [06:38] point me at a branch and i'll mege it [06:38] merge even [06:39] pushing right now [06:41] oh, perhaps I failed to upload after building it here, sigh [06:41] pitti: sorry [06:41] I think I got sidetracked in the middle, trying to figure out why gnome-keyring-daemon wasn't acting as a gpg agent [06:43] slangasek: no prob, uploaded now [06:44] I think it's the first time I uploaded ubiquity [06:44] slangasek: it's not supposed to, that's seahorse [06:44] slangasek: but gpg was fixed with last Friday's gdm, I think, it still fails for you? [06:44] hm, what's the point of "Using default stacking branch" if bzr push uploads the entire 46 MB again? [06:45] pitti: I may not have upgraded gdm prior to my unplanned reboot [06:45] i heard seahorse was split up and you needed seahorse-plugins installed to get gpg-foo too [06:45] I have seahorse-plugins [06:45] anyway, it's probably the bug pitti says [06:46] slangasek: with yesterday's gdm upload, both ssh and gpg should work again [06:46] if not, please let me know [06:47] ok [06:51] superm1: can you please bzr pull lp:~pitti/ubiquity/fix-402707 ? [06:51] superm1: (pull -> cleaner history than merge) [06:53] pitti, okay done [06:53] superm1: thanks! [06:53] no prob. good call on the pull rather than merge, makes sense [07:02] pitti: Am I okay to upload ekiga, or shall I wait? It's only on the DVD, and it allows me to pull out about 8 NBS packages [07:02] StevenK: go ahead [07:11] hi, nvidia quadro 160m is supporte in jaunty? [07:11] supported [07:27] hah; apport's test suite fails now [07:27] AssertionError: 'eglibc' != 'glibc' [07:28] yay me for assuming too much :) === WelshDragon is now known as Fluffles [08:57] pitti: ok ;) [09:14] since ugprading to jaunty breaks every machine with fglrx (due to xorg-1.6), why did you upgrade to xorg-1.6? Or, why not provide 1.5 for the poor souls with an ATI card? [09:15] dfaure, try #ubuntu-x maybe but I expect the choices are not made based on closed source driver users [09:15] dfaure, especially if they consider the ati opensource driver to be good enough for most users nowadays [09:15] it is? when I tried it on the other machine nothing worked. But let me try again, then. [09:16] I don't really care if it's open source or closed source, but I'd like something else than red dots on my display ;) [09:16] well you might have no luck and have a card not working fine with ati [09:16] but it's not an issue for any ati user [09:17] are packages supposed to install scripts into /etc/pm/sleep.d? isn't the right place /usr/share/pm-utils/sleep.d? [09:18] seb128: at least the jaunty upgrade should have made xorg use ati, then. It's the job of the distro to make upgrades painless.... [09:18] dfaure, well I don't know about specifics but I though they got a working fglrx version before jaunty [09:18] ? [09:18] dfaure, do you use the fglrx ubuntu package or an upstream version you got somewhere? [09:19] ubuntu package [09:19] dunno then, ask in #ubuntu-x they will know better [09:20] seb128, ATI dropped support for most of their hardware [09:20] directhex, well that's not an xserver 1.6 issue then but a fglrx ati one [09:20] seb128, so even though a driver with support for modern xorg was released, it only supports current & last gen (and maybe the one before too) [09:20] seb128: well it's related, since the older fglrx for xorg-1.5 obviously still works [09:20] seb128, well, the point is the previous driver can't be included in parallel due to xserver 1.6. i assume [09:21] dfaure, I expect the issue there is that we can't make package depends be dynamic according to the hardware [09:21] dfaure, but agreed that's an issue, xorg should at least try to fallback on ati in such cases [09:22] yes [09:22] dfaure: didn't the upgrade tell you that your graphics driver didn't exist in jaunty? update-managet warned my sister on her dell laptop with ATi that she'd have a worse experience [09:22] the issue is as often in opensource lack of manpower to get everything changed [09:22] Ng: ok, I used apt-get dist-upgrade, no warnings. [09:23] dfaure: don't do that ;) [09:23] dfaure, if you're going to stand outside the safety barrier (update-manager), then that happens [09:23] ok, point taken there. [09:23] dfaure: do-release-upgrade works for shell upgrades if you don't want to use the graphical tool (although I haven't checked if it displays such warnings) [09:24] * dfaure wishes the debian package stuff didn't have so many layers on top of each other, but that's another discussion [09:24] dfaure, ubuntu doesn't real has, users should use update-manager in a consistent way [09:24] real -> really [09:24] X: symbol lookup error: /usr/lib/xorg/modules/extensions//libdri.so: undefined symbol: atiddxAbiDixLookupPrivate [09:24] Ng: do-release-upgrade will perform the same kind of checks as update-manager (including the warning about fglrx) [09:25] mvo_: I figured it might, ta :) [09:25] :) [09:26] any idea about the undef symbol? X won't start... [09:26] dfaure: is fglrx still installed? IIRC it diverts libdri so that might be the problem [09:26] looks like the lib is incompatible with something (the server ?) [09:27] mvo_: thanks, works now [09:28] np [09:29] well, sort of. X starts, kde starts, but no mouse and no keyboard... [09:30] sigh [09:48] cking: do you still have the oem install from bug 402918 to collect logs and files? [09:48] Launchpad bug 402918 in gdm "Karmic Alpha3, OEM login cycles round and around" [Undecided,Incomplete] https://launchpad.net/bugs/402918 [09:48] (just followed up) [09:49] pitti, nope, but I can re-install and let you know within the hour [09:49] cking: thanks [09:52] installing again... :-) [09:57] cking: btw, I'm currently building new desktop images, which have a new ubiquity; I see some oem related fixes in the changelog [09:57] * pitti crosses fingers [10:00] any archive-admin around that could please take a look at bug #402710 ? [10:05] Launchpad bug 402710 in ocaml "[3.11.1 transition][round 1/6] Please synchronize ocaml 3.11.1-2 from Debian sid in Karmic" [Undecided,Confirmed] https://launchpad.net/bugs/402710 [10:06] gaspa: added sponsor ack and followup [10:08] pitti: thanks ;) I wasn't sure about the right procedure. [10:13] presumably contributions to launchpad require copyright assignment? [10:14] yes [10:18] and it's pretty explicit on the dev wiki's page on submitting a patch that the assignment paperwork needs to be done. okay, just checking [10:24] for small patches as well? [10:24] for my own projects I just chase this if someone adds completely new files with a (C) line for himself [10:24] I'm not worried about patches which don't add a copyright line [10:24] but that's for my own projects, LP's policy might be different [10:30] Hi. Anyone knows why packages is not working so often [10:30] nikolam, people make mistakes [10:30] liw, :) [10:31] Nevermind, Just to see it online again [10:31] I ment packages.ubuntu.com Btw [10:36] nikolam, ah, then I have no idea [10:39] nikolam: Seems to have been offline for a while now. [10:40] Omahn, `for a while` is less then 1 day [10:40] it worked yesterday [10:40] and not working the day before [10:40] True [10:41] pitti, log files attached to bug report. [10:42] cking: splendid, thanks [10:42] shall I keep this OEM version installed for a while if you need anything else? [10:50] cking: no, the logs should do fine; also, we have new CDs with a new ubiquity now [10:50] shall I stop further ISO testing then and wait for the new ISOs? [10:50] cking: they are already there [10:51] cking: and on the tracker [10:51] doh [10:51] I'm done with wrestling with xubuntu CDs, looking at bug now [10:52] cking: hang on [10:52] cking: can you please attach /etc/gdm/custom.conf ? [10:52] OK.. gimme 5 [10:53] gdm-simple-greeter[2852]: DEBUG(+): GdmGreeterClient: Received TimedLoginRequested (ubuntu 0) [10:54] gdm-simple-greeter[2852]: DEBUG(+): GdmGreeterLoginWindow: requested automatic login for user 'ubuntu' in 0 seconds [10:54] so it tries to auto-login as "ubuntu", which doesn't exist [10:54] * pitti follows up in bug report [10:55] pitti, yep, log attached, indeed, logging in as ubuntu [10:55] cking: thanks; you can kill the install now [10:55] cool [10:56] cking: I'm pretty sure it's already fixed on the current isos [10:56] I'll find out in 20 mins === yofel_ is now known as yofel [11:48] hello mvo_, do you know why in softwareproperties.AptAuth gpg is used instead of apt-key? [11:53] glatzor: probably a oversight, let me have a look [11:53] glatzor: good to see you btw :) [12:38] mbiebl: which criteria did you use for syncing/merging the zopepackages? which ones and which ones not? [12:39] doko: wrong person ;-) [12:40] ahh, same initials ... [12:40] geser: ^^^ [12:43] mdz: so, we found out why the apport retracers produce useless results; some fakechroot regression in karmic [12:43] doko: I'm trying to get a complete turbogears2 stack synced to karmic. So I just look at the packages needed for it (depends and recommends) [12:43] mdz: I applied a workaround now [12:43] and we'll re-tag recent crash reports [12:43] pitti, oh, great, thanks [12:43] pitti, is there a bug filed for the regression? [12:43] mdz: not yet, I haven't really pinpointed it yet [12:44] mdz: "file /usr/bin/gnome-volume-control" -> no such file [12:44] cd /; gdb ... ; file usr/bin/gnome-volume-control" -> works [12:44] but only in gdb [12:44] geser: yes, and breaking zope3 ... anyway, will now try to do the complete zope3 split. although it's not yet completely in unstable :-/ [12:44] pitti, very weird [12:45] "works" [12:45] doko: oh, sorry, missed it [12:45] but next it fails to load the debug file [12:45] mdz: I strace'd it, and for e. g. open('/usr/bin/gnome-mount') it works, and for open('/usr/bin/gnome-volume-control') it fails [12:45] very ominous [12:45] seb128: oh, that too? [12:45] meh [12:45] seb128: if so, let's shut down them again [12:45] pitti, I was not speaking about your workaround sorry for the confusion [12:46] ah [12:46] rather about the " /usr/bin/../lib/debug//usr/bin/gnome-volume-control: No such file or directory." this morning [12:46] doko: zope3 is main, and the zope.* package are in universe. How did they manage to break zope3? [12:48] geser: they'll replace zope3, and currently are incomplete to replace it === MacSlow is now known as MacSlow|lunch [12:52] eek, sudo is segfaulting here [12:53] use root :P [12:53] cjwatson, in a normal environment? [12:53] yes [12:53] Jul 22 12:08:55 sarantium kernel: [ 6924.741810] <6>sudo[16106]: segfault at 48 ip 001616a6 sp bfc0d288 error 4 in libc-2.9.so[110000+15a000] [12:53] I had a run of segfaults and panics and suchlike when I first updated my laptop to 2.6.31, but they went away after updates [12:53] cjwatson, reproducible? [12:53] I just upgraded, which included a libc6 upgrade [12:53] yes, every time [12:53] ouch [12:54] no crash report and I'd probably need root to get at it anyway :) [12:54] running current karmic, not seeing sudo segfaults [12:54] here as well (amd64) [12:55] so hopefully not an alpha-3 release breaker? [12:55] same here (i386) [12:55] I'm on i386 [12:55] . o O (easy rollbacks with dead-man's-handles would be really cool) [12:55] cking: *phew*, thanks for testing again [12:56] sorry, I tell a lie, no libc6 upgrade involved [12:56] I was confused by the trigproc stuff in dpkg.log [12:56] http://people.ubuntu.com/~cjwatson/tmp/dpkg.log [12:57] apparmor ? [12:58] sudo strace sudo ... erm, fail [12:58] apparmor was installed in this upgrade, yes [12:58] but I don't know why that would cause a segfault [12:59] libpam-ck-connector maybe? [12:59] hang on [12:59] $ sudo true [12:59] works [12:59] $ sudo aa-status [12:59] Segmentation fault [12:59] $ sudo true [12:59] Segmentation fault [12:59] WTF? [13:00] nothing in dmesg, though, except the crash itself [13:01] sudo -K [13:01] still works [13:02] libpam-ck-connector shouldn't have broken [13:02] there were no code changes [13:02] ah [13:02] there were two uploads yesterday :-) === dyfet` is now known as dyfet [13:03] nothing jumps out from the changelog though [13:03] it happened after just this dist-upgrade [13:03] upstart and ecryptfs are the two likely candidates [13:03] and ecryptfs is PAMish, too [13:04] the rest was gstreamer, ekiga, and a gdm postinst fix, none of which even come near sudo [13:04] pitti, the system now gives me a blank screen at step uoi-003 in the test case: http://testcases.qa.ubuntu.com/Install/DesktopOem [13:05] libgcc1 was updated as well [13:05] not in my run 5 minutes ago [13:05] and before that I was working with sudo all the time [13:05] I'll downgrade ecryptfs after lunch, when I can reboot the box into rescue mode [13:06] arghl [13:06] I can't even log in any more [13:06] [25302.085252] <6>login[31054]: segfault at 88 ip 00007f92286fec11 sp 00007fff23fa6e40 error 4 in libc-2.9.so[7f92286a6000+166000] [13:06] [25231.246453] <6>mount.ecryptfs_[31021]: segfault at 88 ip 00007f59a3bbcc11 sp 00007ffff66b0a70 error 4 in libc-2.9.so[7f59a3b64000+166000] [13:07] I'm up for a bet that it's today's ecryptfs upload [13:08] should we get the deb blocked from download? [13:08] plenty of PAM stuff in the changelog [13:08] lpsp [13:09] I'll reboot into rescue mode, downgrade, and check [13:09] mdz, pitti: should we get the deb blocked from download? [13:09] yes, after confirming that it's ecryptfs [13:09] ok [13:09] need some help? [13:09] I didn't upgrade yet, I can upgrade just it and try sudo or something [13:10] I don't have any *ecryptfs* installed [13:12] mdz, well, do you currently see segfaults ? [13:12] ogra, no, I have no troubles right now [13:12] with my Ubuntu system anyway [13:12] I just installed the latest updates, which included: gdm groff-base offlineimap pbuilder upstart [13:12] same here [13:14] I have libpam-ck-connector 0.3.0-2ubuntu7 [13:15] apparmor should be disabled, so i'd not expect it to be that [13:15] free(f); [13:15] asprintf(&f, [13:15] is that legal? [13:15] doesn't look like the best plan to me [13:16] hrm, actually i don't know what asprintf does ... so ignore me [13:16] oh they allocate, so that does seem appropriate [13:17] cjwatson, are you using ecryptfs as well? === dyfet` is now known as dyfet [13:21] confirmed [13:22] I downgraded ecryptfs-utils, and it works again [13:23] elmo: can you please chmod 0 ecryptfs-utils_77-0ubuntu1_*.deb on the mirrors? [13:24] Ng: ^ or you? [13:26] * pitti apports _bin_login.0.crash [13:28] cjwatson: bug 403011 FYI [13:28] kirkland: ^ halp [13:30] pitti: private bug ? :) [13:31] dupondje, bugs are private until being retraced [13:31] hang on [13:32] public now, and attached local stack trace [13:33] I see it I think [13:33] meh, and of course this crept into the xubuntu builds [13:33] which _just_ finally built, after oh-so many attempts :/ === MacSlow|lunch is now known as MacSlow [13:33] I really need to grab some food, I'm falling off my chair [13:34] can someone please followup with IS to disable the package? [13:34] but you wont get fat := [13:34] :) [13:34] flockfile(NULL) really seems unhappy [13:35] pitti, ok [13:36] pitti, enjoy your lunch [13:36] asked #is [13:36] http://paste.ubuntu.com/224351/ [13:36] seb128: thanks [13:36] james_w: that makes a lot of sense [13:37] look good to upload? [13:37] james_w: you already tested it, etc.? [13:37] if so, please go ahead [13:38] still building [13:38] what's the test case [13:38] install and run sudo? [13:38] james_w: install it, and try to login and sudo [13:38] if that fixes it, don't hesitate [13:38] it can't get _any_ worse [13:39] * james_w opens a root terminal [13:39] * pitti hands seb128 the baton for looking in #is and coordinating, in case followup questions turn up [13:39] james_w: you better do :) [13:39] pitti, ok, no worry [13:41] seems I need to wait for another 15 minutes [13:41] so I'll spend the time to weed out the alpha-3 images where the new ecryptfs slipped in [13:42] I can't make the problematic package segfault [13:43] * mvo_ hugs james_w [13:43] james_w: you can't reproduce the original crash, you mean? [13:43] yeah [13:43] let me try your patch then [13:43] don't want to test the fix until I have a broken system [13:43] do I need to restart all my sessions? [13:44] james_w: no, it just happens [13:44] install new ecryptfs-utils, and suddenly login and sudo go boom [13:44] I actually use ecryptfs, though [13:45] james_w: building your fixed package now [13:47] ah [13:47] you need libecryptfs0 as well [13:47] otherwise you get a symbol lookup error [13:47] james_w: confirmed, that fixed the problem [13:47] presumably the dependencies need to be tightened [13:47] kirkland: ^ [13:48] pitti: shall I upload? [13:48] james_w: can you upload this, or shall I? [13:48] please do [13:48] I'll bump build score [13:48] 403 on the broken package to test now :-) [13:48] I hope we can make the :03 publisher run === dyfet`` is now known as dyfet [13:48] uploaded [13:50] building everywhere [13:50] ok, finally food [13:50] bbl [13:50] james_w: thanks! [13:51] thanks Pici [13:51] and pitti :-) [13:51] :) [13:55] * ogra wonders why makedev got so slow [13:56] (the package stalls debootstrap for quite a while) [13:56] all ACCEPTED except for armel, which should make it [13:56] and there it is [13:57] pitti: should be in the next publisher run for you [13:57] * james_w -> food as well [13:57] mdz: ecryptfs> yes [13:57] I wonder if I can move .ecryptfs aside or something to get sudo back ... [13:58] aha! yes [13:58] thanks guys :) [13:59] cjwatson: is that just "mv /home/username/.ecryptfs /home/username/.ecryptfs.save" ? [14:00] james_w, sorry, I may have just clobbered your wiki edit. I clicked save before I noticed, and I canceled, but I think it was too late [14:00] james_w: yeah [14:01] mdz: np [14:02] meh [14:02] could someone promote udhcpc to main ? [14:02] it has an approved MIR and stgraber made ltsp-client-core depend on it [14:03] which means ltsp installs currently break due to udhcpc missing on the CD [14:04] (the MIR is bug 383177) [14:04] Launchpad bug 383177 in udhcp "Main inclusion request for udhcpc" [Undecided,Fix committed] https://launchpad.net/bugs/383177 [14:06] should we have instructions for escaping the problem posted somewhere? [14:10] james_w: ubuntu-devel-announce maybe? === rickspencer3-afk is now known as rickspencer3 [14:28] hi all [14:28] Is there a reason why firefox-3.0 comes without all the gnome dependencies but firefox-3.5 not? [14:29] So it is possible without the whole mess to use Firefox 3.0 with KDE but not with 3.5 while it works fine if I download and install it locally without any further dependencies. [14:56] question about *buntu-restricted-extras, why it is needed to have xubuntu and ubuntu in separate metapackages, since their content is roughly the same. This can create confusion? [14:57] for KDE I understand the need for it's own, but the other two are making me wonder.. [14:57] * ScottK would find ubuntu-restricted-extras for Xubuntu confusing. [14:58] I thought about the naming convention, since it would be easier to understand what package to install, vbased on what enviroment is running [15:02] pitti: i'm here now [15:02] hey kirkland [15:02] kirkland: you missed all the action :) [15:02] pitti: should i read the backlog? [15:02] pitti: yeah, sorry :-) [15:02] but I guess james_w didn't spend much time on forwarding bug/patch upstream, etc. [15:03] oops, forgot about that [15:03] james_w: no worries; you rocked! [15:03] kirkland: so could you please take a look at the bug, perhaps clean up the fix, and sort out the upstream comimt, etc.? [15:04] it was pretty much a shot from the hip to unbreak karmic [15:04] pitti: sure thing [15:07] pitti: james_w: whoa boy [15:07] cjwatson found a much better workaround, I actually dived into init=/bin/bash, etc. :) [15:07] james_w: good find [15:08] twas an easy spot once pitti had the stacktrace [15:08] pitti: what was cjwatson's workaround? [15:08] temporarily move aside ~/.ecryptfs [15:08] james_w: yeah, i did make that change late yesterday :-/ [15:08] * pitti rebuilds alpha 3 images which had the broken version, since we offer it in the installer [15:08] pitti: sorry man [15:08] kirkland: no problem [15:09] james_w: i'll commit this upstream now [15:09] thanks [15:09]