[00:08] Bug #272576 [00:08] Launchpad bug 272576 in revu "Provide alternate login method" [Undecided,New] https://launchpad.net/bugs/272576 === blueyed_ is now known as blueyed [00:55] grr seems like launchpad is always going down for maintainance [00:56] * calc thought he was going to be doing bug triage but apparently not [00:56] * NCommander watches REVU die [00:57] I can understand shutting down edge for maintance, but is it really necessary to completely kill everything? [00:57] calc: did you get the updated icons and license info into OOo? [00:58] kwwii, what are yu doing up at 2am ? [00:58] calc: I know what you mean, as it generally lands smack bang in the middle of my work day, so I have to find other things to do. [00:58] * ogra can blame the glenvilet and RichEd but whats your excuse :P [00:59] NCommander: did that kill revu due to the openid hooks? [00:59] TheMuso: hey, no boogs! [00:59] zaroo boogs. [00:59] iz gtk boog? [00:59] crimsun: heh [00:59] ajmitch, yup [01:01] ogra: waiting to come kassel for release :) [01:01] hehe [01:02] feel free [01:02] hehe [01:03] time for sleep here [01:03] yeah [01:03] * ogra did his final upload ... [01:04] crimsun: Any luck with that pulse sink stuff? I'm going to start again in a bit since LP is down. Am happy to go from where you have left off. [01:05] kirkland: still around? [01:05] slangasek: yessir [01:05] TheMuso: been chasing ALSA and PA stuff concurrently, and honestly, didn't have time to look at the latter. Sorry. [01:05] crimsun: np [01:05] gar when lp goes down all hosted things go with it [01:05] kirkland: hmmm. are you going to be around until the end of the LP maintenance window? :-) [01:06] they really need to make lp more robust if they are going to keep bringing it down (what seems like) every week for several hours [01:06] slangasek: :-) probably, how much longer is that? [01:06] I just got done smoke-testing my pam fix, and there goes LP, whoops :) [01:06] kirkland: up to but not to exceed 2 hours [01:06] * calc can't even run bzr log on one of his checkouts [01:06] slangasek: i'll probably have my laptop with me, watching the debate [01:06] ok [01:11] oh well as long as i can't get anything done right now i might as well upgrade to intrepid, lol [01:15] * NCommander sleeps soundly waiting for LP to return :-) [01:16] calc: Unbind it [01:17] yeah, bzr unbind [01:17] grmbl [01:17] calc: Maybe 'bzr log --local' works too [01:17] you can bzr push and bzr bind again later [01:17] i uploaded at 23:52 UTC ... no trace that LP got it in time [01:18] it won't have vanished, it'll be in the queue [01:18] yeah, indeed [01:18] even if you had got an acceptance it wouldn't have been published anyway [01:18] but i wont know if it built [01:18] ogra: If you're worried, one of us can poke on cocoplum [01:18] I imagine they'd just taken the cron jobs down in preparation [01:18] yeah [01:19] * StevenK runs to the doctors [01:19] * ogra watxhes "blow up" on tv ... [01:19] ah ok [01:20] bzr log --local doesn't seem to work for me, maybe after i finish upgrade to intrepid though [01:21] slangasek: launchpad just started responding for me, fwiw [01:21] kirkland: ok, please test lp:~ubuntu-core-dev/pam/ubuntu :) [01:22] yeah working here too. [01:22] yipee it works for me again too :) [01:22] edge is at least. [01:24] Lauchpad returns [01:24] SHort downtime [01:25] NCommander: wow that was impressive [01:25] bryce, what is? [01:26] NCommander: the shortness [01:26] its always good to be early ;) [01:26] augh, why did cracklib break [01:26] * slangasek shoots the cracklib packges [01:30] * directhex offers a convenient c# version of cracklib [01:31] * NCommander shoots C# [01:32] * directhex hands NCommander vb.net instead [01:32] * NCommander bursts into flames [01:37] oh, geez; this is the worst bashism I've ever seen [01:37] [ /usr/share/dict/words -nt non-existent-file ] [01:37] true in bash and false in dash \o/ [01:38] with #!/bin/sh ? [01:38] ew [01:38] add it to DashAsBinSh? [01:39] i thought intel were bad. do they still "support" ubuntu for their compilers as long as you replace the /bin/sh symlink? === spm changed the topic of #ubuntu-devel to: 8.10 beta released | archive: Feature Freeze | Development of Ubuntu (not support, not app development on Ubuntu) | #ubuntu for support and general discussion for dapper-hardy, #ubuntu+1 for intrepid | #ubuntu-motu for getting involved in development | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs [01:42] cjwatson: adding, thanks [01:47] ogra: what do you think of the patch in bug #222164? Looks simple enough to me but I'm not sure what its implications are so have held off applying it [01:47] Launchpad bug 222164 in xf86-input-evtouch "evtouch works incorrectly when the screen is left or right rotated" [High,Triaged] https://launchpad.net/bugs/222164 [01:49] slangasek: hmm [01:49] ? [01:50] slangasek: i pulled that tree, did a build, installed the debs, but I'm still getting the 'success' messages [01:50] slangasek: is that supposed to be fixed? [01:50] kirkland: post me your /etc/pam.d/common-password, please [01:51] slangasek: http://pastebin.com/f7ea2568d [01:52] kirkland: hmm [01:52] kirkland: please run grep -vE 'pam_unix.so|pam_ecryptfs.so' /etc/pam.d/common-password | md5sum for me [01:54] slangasek: 86180c1552203d9b58582cf547309d01 [01:55] kirkland: you built with -b and installed libpam-runtime, right? [01:55] * TheMuso grumbles at being pointed to an ubunt forums thread in a bug, and not being told on which page at the very least may be helpful. [01:55] that md5sum matches the one I have listed [01:55] slangasek: i just did "debuild" (no -b) [01:56] slangasek: libpam-runtime 1.0.1-4ubuntu5 [01:56] kirkland: can you confirm that you see 86180c1552203d9b58582cf547309d01 in /usr/sbin/pam-auth-update? [01:57] slangasek: negative [01:57] hmm [01:57] kirkland: what bzr revision do you have? [01:57] let me check my bzr branch [01:58] slangasek: -- Steve Langasek Thu, 09 Oct 2008 16:35:46 -0700 [01:58] slangasek: Tree is up to date at revision 760. [01:59] I have revision 763 here [02:00] slangasek: have you pushed? [02:00] yes [02:00] "This bug doesn't affect me (change)" what does that mean? [02:00] i don't think i have seen that before on a bug page [02:00] slangasek: let me try pulling again [02:00] kirkland: checking whether I can pull it here as well [02:00] slangasek: i did "bzr branch lp:~ubuntu-core-dev/pam/ubuntu" [02:01] kirkland: right. I see revision 763 when I pull here, so perhaps we had a race condition there :) [02:01] slangasek: i blew away my copy, pulling again now [02:03] slangasek: okay, now i got 763 revisions [02:05] calc: it's the new "me too" feature of LP, you probably are on edge [02:06] greetings [02:07] stgraber: ok [02:07] hi Hobbsee [02:07] hey nxvl! [02:07] * Hobbsee celebrates that the uni has unblocked some of their ports again [02:07] i saw you are going to UDS this time! [02:07] Hobbsee: oh, as in 6667 ? :) [02:08] * nxvl is at the university using an open 21 for ssh connections and ssh tunnels [02:08] stgraber: nah. 993, etc. [02:08] stgraber: i have an irc proxy, so don't use 6667 from my laptop. [02:08] kirkland: ok, let me know how that goes :) [02:08] ok [02:09] nxvl: indeed! [02:09] nxvl: oh, they let ftp go through their firewalls, that's good :) (for you) [02:10] slangasek: aha! [02:10] slangasek: that's looking together [02:10] @yay [02:10] slangasek: looking better [02:10] nxvl: I used to connect on a Windows network with everything blocked except the proxy server ... so I had to use ntlmaps to connect to the ISA proxy (using NTLM), then use ssh over https on port 443 and finally openvpn over tcp going through a ssh tunnel to get complete internet access :) [02:11] (all that scripted, it's not that difficult to setup and quite fast actually) [02:11] yeah [02:11] slangasek: but now quite there yet [02:11] slangasek: checking the current password now does the right thing [02:11] i have no proxy, just port blocking, so it's some steps less [02:12] slangasek: it fails immediately, with the wrong password [02:12] huzzah [02:12] slangasek: but hit 6 times for the new password [02:12] "No password supplied" x 3 [02:12] i just need an ssh running on 21, 80 or 443, and a lot of tunnels (on my .ssh/config) [02:12] then "password updated successfully" === emma is now known as joe-the-plumber [02:12] stgraber: these guys were allowing 22, 443, and 80 for a while. Only. [02:12] and i'm done === joe-the-plumber is now known as emma [02:13] emma: :-) [02:13] crimsun: Did you try my interim Xsession.d fix to reduce the race condition's possibility? [02:13] emma: $1000 says he lives on "Main Street" [02:13] emma: "Not Wall Street" [02:13] TheMuso: yes, and it helps. I haven't been able to trigger the race yet. [02:13] Hobbsee: for a geek it's only needed some imagination and patience [02:14] crimsun: Ok. [02:14] nxvl: that's true. [02:14] Hobbsee: there is no no-geek sysadmin that can make us be quiet [02:14] hehe [02:14] and even some geek sysadmins that can't [02:15] TheMuso: OTOH, with current pulseaudio packages (i.e., no interim Xsession.d fix), the race on my machine is, at best, very difficult to trigger. Seems it nondeterministically triggers once every twenty or so logins. [02:15] crimsun: Right. [02:15] crimsun: I am the same, but I can never trigger it. [02:15] kirkland: ok, wheels turning in the noggin'; I may have to wait until after dinner to fix that [02:15] (if I'm right about how to fix it at all, that is) [02:16] slangasek: k [02:16] Laney: how many audio devices are in your computer (experiencing the pulseaudio race on session login)? [02:18] nxvl: well, the only thing that could have stopped my hack is some packet analysing (basicalling detecting that I'm not sending http over SSL but something else) that needs quite a powerful firewall to do and a lot of tweaking [02:18] nxvl: so not really an option on a big network :) [02:20] slangasek: It's been a couple of hours, so I'm asking again about kdepim in hardy-backports. [02:20] stgraber: or a real proxy rejecting non http traffic, but for that we have http tunneling :P [02:20] ScottK: right, looking :) [02:21] stgraber: or a traffic analyzer and someone reading the logs and seeing what's going on and rejecting that connection, which is hard for any network [02:21] slangasek: Thanks. [02:23] nxvl: well, I was over HTTPS so the "rejecting non http traffic" is not possible as it only sees HTTPS (and the purpose of https is to not have man in the middle thing possible) :) [02:23] So Canonical loves REVU [02:23] nxvl: so a very well configured traffic analyser can detect that from the packet size and some other parameters (I remember reading about that) but it's not that easy to do and a real wast of CPU in most case [02:23] http://revu.ubuntuwire.com/ - try logging in and look at the login page [02:24] ScottK: accepted [02:24] stgraber: that's why you need a real geeky sysadmin [02:24] slangasek: Thanks. [02:24] NCommander: :) [02:30] crimsun: ping [02:30] calc: pong [02:31] crimsun: i see you followed up to 77435 but wasn't quite sure what you meant by 0.6/0.7/0.8 and another user claims it works fine [02:31] nxvl: Looks fine to me [02:32] calc: sorry, I should have been more specific; those versions refer to xmonad. [02:32] StevenK: what did i did now/ [02:32] ? [02:32] Er. NCommander, rather than nxvl [02:32] oh [02:32] nxvl: Sorry :-) [02:32] StevenK, look closely at the text [02:32] There is a thankyou on behalf of Canonical [02:32] crimsun: oh ok [02:32] (and the new working men image) [02:33] Oooh, I see that [02:33] It was an added bonus when I got REVU added to the trustroot so we can get full openid support [02:33] which lead to this: https://bugs.edge.launchpad.net/launchpad/+bug/284133 [02:33] Launchpad bug 284133 in launchpad "GPG over OpenID" [Undecided,New] [02:45] cody-somerville: the xubuntu instaler is livecd too? [02:45] yes [02:46] cody-somerville: just as the ubuntu installer? [02:46] Right [02:46] cody-somerville: so i can run the livecd and install from there [02:46] yes [02:46] awesome [02:46] thanks [02:51] no problem [02:56] slangasek: another pam question for you when you come back from dinner [02:58] slangasek: i have some people complaining that their ~/Private directories are being unmounted by their cronjobs [02:59] slangasek: pam_ecryptfs is in the common-session stack, and cron opens/closes a session [02:59] slangasek: the close session unmounts ~/Private [03:01] slangasek: the current work-around is for those users to rm ~/.ecryptfs/auto-umount, which umount.ecryptfs_private checks for [03:01] slangasek: but that disables automatic unmounting across the board [03:03] slangasek: that's not ideal [03:04] slangasek: a counter, has been suggested, but i'm not sure that's the best approach [03:29] crap my upgrade to intrepid now won't boot [03:30] calc: no more bugs, then! [03:33] mrooney: yea sorta [03:35] looks like i will need to download and completely reinstall [03:40] calc: :-( [03:40] try the live CD just as a checkpoint? [03:41] it'd be odd if a boot failure was due to upgrade vs. fresh install, though it's not unheard of [03:41] slangasek: actually, i'm wondering, perhaps we should drop pam_ecryptfs from common-session? would common-auth and common-password suffice? [03:41] though if it is due to upgrade vs. fresh install, then it should be rectifiable in-place [03:42] I'm trying to get a custom kernel going and currently hang at the initrd-creation-step ... [03:43] yaird gives me an error like: "yaird error: bad device link in /sys/block/sda (fatal)" [03:43] yaird -vd --output=initrd.img-2.6.27-rc9 2.6.27-rc9 [03:43] is the command I use [03:44] but neither the "verboseness" nor the debug-output of yaird help me getting further clues what might be the cause of the error [03:46] but neither the "verboseness" nor the debug-output of yaird help me getting further clues what might be the cause of the error [03:46] hm... my connection crapped out [04:01] TheMuso: have you settled on patching pulseaudio instead of libcanberra0.6? I'm wondering if it doesn't make sense to touch the latter instead for intrepid... [04:01] i managed to revive it [04:01] i booted off 8.04 cd and remade the initramfs and that seemed to fix it [04:01] crimsun: I am unsure as to what we could do with libcanberra. [04:01] it originally had hung right after loading the wifi driver (3945 card) [04:01] libcanberra as in the city? [04:02] calc: iwl3945? [04:02] StevenK: yea [04:02] calc: known bug. just kepe trying tob oot [04:02] calc: https://bugs.launchpad.net/bugs/263059 [04:02] Hobbsee: oh lovely [04:02] Launchpad bug 263059 in linux "[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)" [High,In progress] [04:02] calc: davidm has been having problems with it too [04:02] StevenK: ok [04:03] i thought it was a more local problem. apaprently not. [04:03] so maybe the initramfs did nothing then, just trying to reboot probably fixed it [04:03] TheMuso: perhaps I'm hitting a different bug, but all of my crashes have been with "GNOME Login", which would be from libcanberra-login-sound.desktop's canberra-gtk-play invocation [04:03] crimsun: crash as in segfault? [04:04] TheMuso: apparently, and it seems to be caused by the same race [04:04] crimsun: Right, I am not sure how to solve that, there is a bug filed about it. Let me dig it up. [04:04] crimsun: 275233 [04:05] how do you see the me-too status of a bug? [04:06] or is it just a feel good button? :) [04:06] calc: you can't. [04:06] calc: eventually, they say they'll do something with it - but not actually let you see the raw numbers. [04:06] hmm ok, so its turned on but of no use at all [04:07] lol [04:08] it has the aim of making people not write "me too" and such in bug reports. [04:09] Hobbsee: and instead since no one can see the stats a developer has no idea how widespread the bug is [04:09] especially if users actually start using this placebo button ;-) [04:10] kirkland: I have no idea whether pam_ecryptfs should be dropped from common-session; it would have no effect on this bug, and I don't think it's a great idea to make changes there at this point if we don't have a specific bug in mind [04:10] kirkland: oh, you said that earlier, sorry :) - I don't know if it should be dropped from common-session, then [04:11] Hobbsee: the main usefulness of such a button would be to get the info out of the comment log, it is still very useful to know their launchpad id's and the overall number (raw number whatever) [04:11] calc: you'd have thought so, but... [04:11] calc: i just heard this. I don't have much to do in LP development. [04:12] doing it the way it currently is useful to no one really at all [04:12] less comments in a bug without any way to see its due to this button is actually worse than before [04:15] calc: you could try to get that POV across to #lp, in a few hours, if you wanted. No guesses on your chance of success, though [04:17] crimsun: do you get that crash even with the pulse Xsession.d fix? [04:17] Hobbsee: probably would be easier to just do it at UDS [04:18] its only about 6 weeks from now [04:19] slangasek: okay, i need to think more about this later [04:23] calc: This button got discussed at the last UDS. They seem to have proceeded anyway. [04:24] calc: Currently it's pre-production. If you wait until UDS it'll be "Everyone is used to it now, we can't change it". [04:25] kirkland: ok, I don't seem to be able to reproduce the earlier bug with other optional modules besides ecryptfs, testing now with ecryptfs [04:25] ScottK: a button that does nothing or a button that can collect data? [04:25] ScottK: i don't recall them planning on a useless button at the last UDS [04:26] calc, ScottK, it should soon start showing up in listings as an icon, for the most user-affected bugs. I don't know what the exact status of that branch is. I also know there are plans to figure out what the best way to provide that information for bug triagers is, probably through the API. [04:26] slangasek: it also works with current = (correct), new1 = foo, new2 = bar [04:26] please, file bugs with what would make it more useful for you guys :) [04:26] kirkland: "works", or "triggers the bug"? [04:27] calc: Trying to have a 'me too' button instead of having people comment. Next step in the master plan is to have Confirmed disappear as a status. [04:27] slangasek: triggers the "password updated successfully" report [04:27] beuno: will the bugs be looked at promptly? [04:27] beuno: or will they wait 6+ months? [04:28] Hobbsee, don't be mean! they will be looked at soon, and something will be done to make the feature more useful for you guys, which is why it was done in the first place [04:28] the implementation is just being made in smaller steps [04:28] beuno: ok, it would be very useful to have some way to get at the names/total number from the page as well [04:28] beuno: right. And i'm not being mean, i'm more just used to reality. I'm pleased to see the bug I filed in sevilla (april 07, iirc) about an implemented feature has finally been triaged. [04:29] ScottK: then just get rid of bug reporting entirely :) [04:29] calc: That's the best way to get the count to zero. [04:29] ScottK: heh [04:29] kirkland: ok - it seems to be pam_ecryptfs specifically that returns PAM_SUCCESS in this case when no password token has been set [04:29] calc, right, there are some concerns that the feature may be used to blackmail developers into fixing certain bugs, so we want to be careful with it [04:29] kirkland: why doesn't pam_ecryptfs return PAM_IGNORE? [04:29] beuno: In most projects 'having something useful' is something you do before fielding it. [04:30] slangasek: ignorance on our (ecryptfs-devel) part, probably [04:30] calc, so, we want to make it useful, but be careful not to shoot ourselves in the foot [04:30] slangasek: i'll look at that tomorrow [04:30] ScottK, sure. I guess this isn't most projects [04:30] beuno: blackmail? [04:30] That's for sure. [04:30] beuno: ah you mean vote stuffing, i guess? [04:30] * RAOF presumes "blackmail" means "gaming the system for fun and profit" [04:31] calc, yes. "1103 users voted for this, you should fix it!" [04:31] heh [04:32] beuno: now that sounds like brainstorm. [04:32] i'm sure large numbers of users would vote for put OOo 3.0 in intrepid, but its not happening :) [04:32] right, so, I think the proposed solution is to show in the listings, with an icon, the top 5% or so [04:32] beuno: could make the number only visible by bug squad or something if that is a concern [04:32] and maybe provide actual counts or something similar through the API [04:33] calc: Is there a PPA for OO.o 3? [04:33] but, please, take with a grain of salt, I'm not 100% sure where the discussion is [04:33] tedg: yes ~openoffice-pkgs [04:33] beuno: It sounds like a very elaborate attempt to hide information that's actually useful. [04:33] calc: Cool, thanks. [04:33] tedg: will most likely go into backports around the beginning of Dec [04:33] calc: I'm working on making my system unstable before the jaunty archive opens ;) [04:34] ScottK, I'm with you in the elaborate part [04:34] there's a lot of things to consider [04:34] I'm sure we'll work out something [04:34] tedg: heh :) [04:35] kirkland: ok. I think that's the reason for this behavior; I'm going to have a closer look at pam_ecryptfs code, and if that conclusion stands, I'll go ahead and upload these pam changes and we can look at ecryptfs tomorrow [04:36] calc, Hobbsee, so, if you guys can file bugs with your concerns, or even ideas, it would be great, and I promise to chase up answers for them if you don't get any soon [04:36] beuno: ok, cool. [04:36] we have a big 2 week sprint coming up from next week on [04:37] so response times may vary a bit [04:37] beuno: another long flight for you? :) [04:37] but I'll keep an eye out for bugs on this, feel free to subscribe me [04:37] ajmitch, heh, yeah. But it's only 16hs this time! [04:37] beuno: is it possible to make something only visible on a bug page by a certain group? [04:38] beuno: so we could have the stat there but only by eg bug squad or something like that, then have it available via api for whoever wants it there as well [04:39] calc, I suspect that it would involve special-casing a team in LP, and would be very hard to convince anyone to do something like that. APIs are less user-visible, so it's less of a risk. [04:39] I'm not saying no [04:39] and, in no way do I decide any of this [04:39] so give it shot [04:39] beuno: ok [04:39] there's already special-casing on changing bugs [04:39] beuno: I already gave my feedback at UDS. No reason to waste time on it now. [04:40] beuno: oh another feature i want is the ability to delete packages from a bug [04:40] :) [04:40] is it christmas already? :p [04:40] oh, now there's an idea... [04:40] well i found a real bug that could be fixed by allowing that [04:40] calc: you can already do that, though. entirely obtuse, though [04:40] I know that's a common headache, not sure why it's still there [04:41] or if there's a bug open for it, which I suspect it is [04:41] for eg openoffice.org any bug assigned to openoffice.org2 gets autoreassigned to openoffice.org but it fails if it already is assigned to openoffice.org as well via a separate package entry [04:41] Hobbsee: how do you delete it? [04:42] calc: edit it, take out the package field. then it just gets assigned to ubuntu. [04:42] Hobbsee: ugh that isn't a real solution [04:43] Hobbsee: i'm sure bdmurray would like to remind you about that ;-) [04:43] calc: it's a workaround :) [04:43] calc: ah well. Maybe he needs more agressive mail filtering :P [04:43] in this particular case it caused a hardy task to get opened and i couldn't even mark it invalid becaue it would try to rename the package entry which won't work [04:44] ah yes, there's no way back from nominate for release. [04:45] i didn't even nominate it for openoffice.org2, i nominated it on the other package entry for openoffice.org [04:46] and i wasn't trying to remove it, i can't even mark the bug as invalid under openoffice.org2 because it tries to rename it to openoffice.org and fails [04:46] er i mean remove it from nomination [04:46] * calc can't recall the bug number atm but i mentioned the number earlier today [04:46] bug 173090 [04:46] Launchpad bug 173090 in openoffice.org2 "[upstream] [hardy] Special characters are not displayed correctly, fonts dissappear from the menu" [Undecided,New] https://launchpad.net/bugs/173090 [04:47] thats it [04:47] and is the reason why i think we should be able to delete package entries, or at have the option via restricted access (bug squad?) [04:48] * beuno agrees [04:48] i have quite a few bugs that are screwed up like that overall [04:48] or at least used to [04:48] actually in this case i can't even close the bug entirely, lol [04:51] * calc headed for bed, bbl [05:22] Hmmm. What's the graphical tool that give you a device-manager-esque thing from HAL? [05:22] hal-device-manager? [05:24] It's actually gnome-device-manager these days. [05:25] And is apparently no longer installed by default. [05:25] * StevenK is trying to track down the wireless device in this device [05:27] Can I please attack forum users if they suggest to alter /var/lib/dpkg/status and the local Packages files in order to resolve dependency issues? [05:29] wgrant: I'd say yes go ahead. :p [05:30] Wow. That's a disturbing concoction of cluelessness and knowledge. [05:30] Exactly. [05:30] If they know enough to be able to do that, they should know enough to realise that's its stupid and wrong. [05:31] Hmph. Can't find the network device or the touchscreen in hal-device [05:34] StevenK: what about lshal? [05:35] wgrant: Either that our they're Automatix devs and it's the way things are done. [05:35] lshal for 'touch' gives nothing, and 'network' only the shows the USB Ethernet I plugged in [05:37] ScottK: Indeed, that's a good theory. === lacqui_ is now known as lacqui [06:03] hi all. any idea when mono 2.0 will be released for hardy? [06:03] kirkland: ok, pinned down the ecryptfs issue; yeah, it's an ecryptfs bug [06:04] r_rehashed: it might be backported, but that is a huge amount of work, given all the mono apps that would require rebuilding and testing [06:06] since hardy is an LTS release i thought it will be backported. but i hope ibex uses 2.0 instead of 1.9 [06:07] LTS also means "don't break everybody's systems" [06:07] And backporting mono is a sure way to do that. [06:12] r_rehashed: Intrepid won't have 2.0 [06:12] :-/ [06:12] On the basis that there aren't actually any packages available yet, despite the work of the Debian mono team. [06:13] i see [06:13] And also the horrible risk of regressions in the tiny, tiny time available to test. [06:13] yes, i understand [06:58] good morning [06:58] morning dholbach [06:58] dholbach, hi here too [06:58] hey Burgundavia [06:58] hiya Burgundavia [06:58] any yaird expert here? [06:59] MacSlow: how goes the banging at GDM? [07:00] I get the error "bad device link in /sys/block/sda (fatal)" when trying to execute "yaird --output=initrd.img-2.6.27-rc9 2.6.27-rc9" [07:00] Burgundavia, coming along [07:02] There are three symlinks in /sys/block/sda all of which seem to be find (I can "cd" to them) [07:02] good morning [07:04] Is there any other way/tool to create a initrd.img under intrepid? The old mkinitrd seems to be gone. [07:05] MacSlow: mkinitrd is long dead. "update-initramfs -u" [07:05] StevenK, that'll work with a self-compiled kernel? [07:06] MacSlow: update-initramfs -u -k [07:06] * MacSlow assumes that uses some assumptions regarding special ubuntu package actions done before it [07:07] StevenK, does that do anything besides creating /boot/initrd.img-version.bla ? [07:07] StevenK, it's not touching any of /boot/grub/menu.lst or the like? [07:07] MacSlow: None, just creates the initramfs [07:08] StevenK, ok ... seems to work sofar === tkamppeter_ is now known as tkamppeter [07:42] Riddell: do you have the source of example-content/kubuntu-leaflet.png somewhere? It still mentions powerpc [08:01]