[01:00] <crypt-0> https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/448918
[01:40] <slangasek> mdke: status on the wiki> no, I don't think editing a wiki is a good way to keep track of that stuff, I track it locally instead
[02:12] <Darxus> Is there a way to monitor packages in debian type archives for new versions (other than throwing a few lines of perl together myself)?
[02:25] <superm1> pitti, using http://pastebin.com/f95b5c26 and this apport package hook http://pastebin.com/f350d087e I was still redirected into the normal source package area rather than the mythbuntu product on launchpad https://bugs.edge.launchpad.net/ubuntu/+source/mythtv/+bug/449181
[02:25] <superm1> it let me file a bug surprisingly even though it's not a genuine source package though
[03:22] <ScottK> slangasek: I saw your bugmail on emacs23.  Seems at least slightly impolite.
[03:46] <slangasek> ScottK: yes, I'm at least slightly annoyed that no one took responsibility for checking the set of packages emacs23 was generating, and we now have to do stupid version tricks to get emacs installable again
[03:46] <ScottK> I can imagine.
[03:49] <LaserJock> was it assumed that emacs23 was going into Main and taking over for emacs22?
[03:49] <ScottK> LaserJock: No.
[03:49] <slangasek> no, it was explicitly approved as a universe-only FFe
[03:49] <ScottK> Several of us didn't catch it.
[03:50] <LaserJock> hmm, I just wondered as the changelog says that the maintainer was set to Ubuntu Core Developers
[04:05] <stooj> Is the rss feed on planet.ubuntu.com down?
[04:13] <trip0> so i used to be able to auto login from /etc/event.d/tty1 using mingetty.  it doesn't seem to be working now?  Does this have to do with the conversion to upstart?
[04:16] <crypt-0> https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/448918
[04:20] <ScottK> slangasek: If you didn't fix emacs23 already, I'll take it.
[04:45] <vigo> Hello, I am subscribed to this letter/email and wanted to know if I erred in one of the posts?
[04:45] <slangasek> ScottK: hadn't gotten to it yet - feel free (and thanks)
[04:45] <ScottK> OK.  Thanks.
[04:49] <vigo> I did suggest a Debian like install, where the user can choose the applications that they want at this time, MySQL, or not, Browser and so on, I have installed a few systems and I rather like the option to choose what goes in, after all, packages can be added after the initial install, so that makes sense to me?
[04:52] <RAOF> vigo: General consesus has been that the (livecd) installer is the wrong time to choose applications.  For most users it's presenting a choice without any of the information needed for them to make that choice.
[04:52] <vigo> RAOF: Thank you.
[04:52] <RAOF> As you say, it's simple to install & remove software after the install; this allows for experimentation, while also having everything just work out of the box.
[04:55] <vigo> That does make sense.
[04:56] <vigo> It also helps the learning part of it.
[04:58] <RAOF> I forget if the alternate installer lets you choose tasks.  It's been some time since I actually installed :)
[04:59] <vigo> RAOF: Ubuntu does not really give choices like that. It is Language, Name, Partition, GO!
[05:00] <vigo> Wich is neat
[05:00] <geofft> The debian-installer does pop up a tasksel menu, just like Debian's. I netinst; I assume the alternate is the same
[05:05] <vigo> geofft: I will be installing Kdeb later tonight and take notes, if I see anything of note, I will mention it, after that install I will be putting the backup of this dev on to test that.
[05:06] <crypt-0> https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/448918
[05:07] <ScottK> crypt-0: Tossing bug links into the channel less than once an hour is rude and unlikely to improve your chances of getting a fix.
[05:08] <crypt-0> ScottK, sorry, no one even acknowledged it
[05:09] <crypt-0> i hope karmac doesnt plan on using SHA1 to hash its password, when SHA2 and whirlpool are available
[05:09] <ScottK> crypt-0: Odds are the people most likely to do something about it get bugmail for the package.  It's late a night virtually everywhere Ubuntu devs work, so not getting a response on IRC shouldn't be much of a suprise.
[05:09] <RAOF> It's only been 9 hours since you filed the bug.  What sort of response were you expecting?  I'd guess that many of the people who actually handle that sort of core package are still asleep in Europe.
[05:10] <crypt-0> is karmac beta out now?
[05:10] <ScottK> Yes
[05:10] <crypt-0> is it tested on crypted systems?
[05:11] <RAOF> Some people do, yes.
[05:11] <crypt-0> mabye ill try it
[05:12] <crypt-0> thought it want supposed to go beta for a week or so
[05:12] <crypt-0> is there somewhere where i can take a hack at the automated crypto installer?
[05:13] <crypt-0> id like to make one where you can choose the hash, cipher, and cipher mode
[05:13] <RAOF> I'm not sure what, precisely, you mean by "hack" in that context.  "apt-get source cryptsetup" will get you the source + packaging for cryptsetup.
[05:14] <crypt-0> im looking for the gui part in the alternate CD
[05:14] <crypt-0> some sort of ncurses interface?
[05:14] <RAOF> That'd be debian-installer.
[05:16] <crypt-0> ok ill take a look and see if i can make it do what i want it to be able to, i can alread do whatever, with manual cryptsetup, or manual dm crypt etc. , this so the Joe PC user can Choose what to use
[05:17] <crypt-0> i just find the defaults insecure, but then again what defaults aren't? However, when it comes to crypto, the defaults inst something i believe you should use
[05:18] <RAOF> That's not an attitude we'd share around here; the defaults should be the right thing for as many people as possible.  With crypto, that's even more important because naieve fiddling with crypto almost always results in worse security.
[05:21] <crypt-0> true
[05:22] <crypt-0> but the defualts should be the 3 AES finalasts, Whirlpool, or SHA2
[05:22] <crypt-0> essiv-cbc or xts-benbi
[05:22] <crypt-0> any combination of that can not be insecure
[05:23] <geofft> As a user, I have no idea what any of those are, other than a vague idea about SHA2. Is there a single suitable default?
[05:26] <crypt-0> well there have been recent attacks on AES
[05:26] <crypt-0> basically , SHA1 is broken, which is how your password is hashed by default
[05:27] <dtchen> arguably once someone has access to the disk, you're up a creek anyhow
[05:27] <crypt-0> password hash :sha256 cypher mode twofish-cbc-essiv:sha256
[05:27] <geofft> yeah, I tend to treat /etc/shadow as if it contained a crypted pw
[05:28] <crypt-0> dtchen, yeah, but its  better encrypted then not
[05:29] <crypt-0> dtchen, in my bug report i describe a new feature in cryptsetup
[05:29] <crypt-0> that wipes the key from ram on suspend/ sleep
[05:30] <crypt-0> making cold boot less of a problem for laptop users, if your desktop gets cold-booted you have some home security issues to adress :)
[05:31] <crypt-0> it works for desktops also
[05:32] <[reed]> RAOF: *cough* Debian developers *cough*
[05:50] <stooj> Jono, you there?
[06:17] <ScottK> slangasek: emacs23 uploaded.
[06:18] <vigo> ScottK: Ratso, I am still on Emacs22
[06:18] <ScottK> vigo: emacs22 is the default supported emacs for Karmic.  We have 23 in Universe for people that want it.
[06:19] <vigo> ScottK: Thank you, I am on Karmic development branch, I like testing stuff.
[06:26] <slangasek> ScottK: cheers!
[06:41] <crypt-0> Have there been major changes in the Linux Crypto API since juanty?
[06:48] <TheMuso> cd
[06:48] <TheMuso> woops
[06:54] <lifeless> #ubuntu-devel
[06:59] <crypt-0> yep, your here lifeless :P
[07:05] <dholbach> good morning
[07:07] <lifeless> crypt-0: I was reporting TheMuso's cd
[07:08] <crypt-0> not filmilar with his CD, or him
[07:10] <lifeless> crypt-0: read scrollback
[07:10] <pitti> Good morning
[07:10] <pitti> bryce: hi
[07:11] <crypt-0> you thought your IRC client was a shell? :)
[07:11] <crypt-0> its 2AM here and ive had 1 hour of sleep
[07:11] <crypt-0> so im off..
[07:12] <lifeless> crypt-0: no, I was making a joke.
[07:12] <pitti> superm1: the "native package" check isn't applied if you set a custom crash database
[07:12] <superm1> pitti, well shouldn't it have still been put against the product that i asked then?
[07:12] <pitti> superm1: your is_ppa hook could be written much simpler, btw, but that's not the cause
[07:12] <ebroder> Now that bug #429445 has an ubuntu-release ACK, do I need to subscribe the archive admins?
[07:13] <crypt-0> Have there been major changes in the Linux Crypto API since juanty?
[07:14] <lifeless> crypt-0: if you're tired go to sleep. You might want to mail the list you question (not that I'm sure anyone knows ;P)
[07:14] <pitti> superm1: hm, at first sight the crash conf looks fine, let me try
[07:14] <pitti> superm1: where did you put http://pastebin.com/f95b5c26 ?
[07:14] <superm1> /etc/apport/crashdb.conf.d/mythbuntu-crashdb.conf
[07:14] <pitti> superm1: /etc/apport/crashdb.conf.d/something.conf ?
[07:14] <crypt-0> lifeless, ill just shoot a mail to the linux crypt mailing archive
[07:16] <pitti> superm1: just for testing, does it work if you unconditionally set report['CrashDB'] in the hook?
[07:17] <superm1> pitti, not sure, how do I trigger a "crash"?
[07:17] <superm1> i know that report['CrashDB'] ended up in the resultant bug
[07:17] <pitti> superm1: ^ oh!
[07:18] <pitti> superm1: crash trigger> kill -SEGV <some process>
[07:18] <pitti> superm1: but easier is "ubuntu-bug somepackage"
[07:18] <pitti> it should work for bugs as well as for crashes
[07:18] <pitti> superm1: right, bug, it doesn't remove CrashDB from the report
[07:19] <pitti> but that's just a cosmetic issue, and it tells us that the hook worked
[07:19] <superm1> so that's one bug, and the other is it not actually using that crashdb
[07:20] <superm1> pitti, hm using ubuntu-bug got me even worse results
[07:21]  * pitti tests locally
[07:21] <superm1> i'm using apport-cli, and it told me to go to https://bugs.launchpad.net/None/+source/mythtv/+filebug/o0FTrYbT0dwUJEuotA1XXCYZqCy?
[07:21] <superm1> which is certainly wrong
[07:21] <pitti> https://bugs.edge.launchpad.net/none/+source/usplash/+filebug/3aqU0P3yTj1coNm2fS6NFZaF6yE
[07:21] <pitti> indeed
[07:21] <pitti> superm1: thanks, investigating
[07:22] <superm1> cool, thanks
[07:38] <dholbach> pitti: I'll unsubscribe the sponsors from the ibus syncs
[07:40] <mdke> pitti: I've assigned bug 441401 to you because I wanted to get your view on it before making the change - hope that's ok!
[07:41] <pitti> mdke: I'll have a look
[07:42] <pitti> dholbach: they are done?
[07:42] <dholbach> pitti: they have the sponsors ack, no?
[07:42] <pitti> I didn't look
[07:42] <dholbach> pitti: so nothing to do for other reviewers :)
[07:42] <dholbach> you said "release/sponsor ack"
[07:42] <pitti> ah, thanks
[07:42] <dholbach> no worries :)
[07:50] <pitti> superm1: oh argh!
[07:50] <pitti> superm1: s/product/project/, please :)
[07:51] <superm1> pitti, doh.  that could be clearer in documentation for the future :)
[07:51] <pitti> superm1: I'll add an assertion, to point this out earlier
[07:52] <pitti> superm1: I'll add that assertion ("must set distro or project" and add a blurb to doc/crashdb-conf.txt
[07:52] <superm1> pitti, sounds sufficient, thanks
[07:58] <superm1> pitti, while i'm updating, what did you have as a recommendation to simplify is_ppa?
[07:59] <pitti>     if not apport.packaging.is_distro_package(report['Package'].split()[0]):
[07:59] <pitti>     report['CrashDB'] = 'mythbuntu'
[07:59] <superm1> ah, yeah, definitely better
[08:00] <pitti> superm1: this reports bugs against ubuntu/+source/mythbuntu if it's an original ubuntu package, otherwise against a product
[08:00] <pitti> (if that's the behaviour that you want)
[08:00] <superm1> *project :)
[08:00] <pitti> *cough*
[08:00] <pitti> AssertionError: Need to have either "project" or "distro" option
[08:00] <pitti> superm1:  ^ just committed that
[08:06]  * Mirv got permission to attend UDS-L, see you there
[08:07] <liw> Mirv, congratulations
[08:08] <Mirv> liw: thanks
[08:08] <Mirv> too bad it will shorten my FSCONS trip a bit, have to see if I will move my lightning talk on Sunday to an earlier time
[08:09] <mneptok> liw: going to UDS?
[08:09] <liw> mneptok, I doubt it
[08:09] <mneptok> bah.
[08:09]  * mneptok will be there
[08:10] <liw> mneptok, I'm sure you'll have fun there anyway :)
[08:10] <mneptok> need to book travel and hotel this week. going to see who from Montreal might want to share a room.
[08:10] <mneptok> liw: i doubt it. it's Texas. ;)
[08:15] <pitti> superm1: http://bazaar.launchpad.net/%7Eapport-hackers/apport/trunk/revision/1621 FYI
[08:16] <superm1> pitti, thanks, that is definitely much more clear
[08:16] <TheMuso> 1/c
[08:37] <Mirv> hmm, I wonder if it would be ok or not to leave at ca. noon, Friday
[08:37] <Mirv> the other option is Saturday evening which would mean quite late arrival back, on Sunday
[08:39] <Mirv> (ie. noon or a little after from the hotel)
[08:43] <mneptok> TeTeT!
[08:45] <TeTeT> mneptok: Hi Kurt, how are things?
[08:45] <mneptok> TeTeT: very good, thanks! Kristine and i are just completing a home purchase, and she starts a new job here next week. you?
[08:46] <TeTeT> mneptok: currently at the London HQ of Canonical, having a training sprint
[08:46] <mneptok> TeTeT: you're learning to make tea?
[08:47] <TeTeT> mneptok: yeah, I look forward to the eating biscuit class
[08:58] <skar> hi, i've got a patch to be applied to glibc source package. How do I apply the patch and build glibc?
[09:01] <RAOF> skar: dpkg-source -x glibc_whatever_the_version_is.dsc, cd to the unpacked source dir, apply the patch (in some way; this depends on a number of things); debuild
[09:02] <skar> RAOF: ok, i got to that stage. now, how do i make sure the build is done only for i386? it seems to be building for a long time :(
[09:03] <RAOF> It'll only build for your arch (and possibly build a libc-i386 package if your arch is x86-64)
[09:03] <pitti> mbiebl: do you see bug 444915 in linux 2.6.30 in sid, too? IOW, do you want to use "usefree" until this gets fixed again as well, or should I keep this as an Ubuntu specific change?
[09:04] <skar> RAOF: thanks. i was following http://www.cyberciti.biz/faq/rebuilding-ubuntu-debian-linux-binary-package/, so running debuild or "fakeroot debian/rules binary" both should work?
[09:05] <RAOF> skar: Yes, although I doubt many developers actually do the latter.
[09:05] <skar> RAOF: ok, that link i sent, it suggested that. also how do i force make to use "-j5". i've got a quad core machine, so compile would be faster.
[09:07] <RAOF> That's package-dependent; there's no guarantee there's a switch to allow you to do that.  If there were, you'd want to shove something in the DEB_BUILD_OPTS evn variable IIRC.  Check out the debian/rules file for details :)
[09:08] <skar> RAOF: thanks, debian/rules had a NJOBS where it seems to be detecting the no.of cores
[09:38] <tsdgeos> hi, can anyone confirm wheter poppler in ubuntu is built against libopenjpeg or not'
[09:38] <tsdgeos> ?
[09:38] <tsdgeos> missing h somewhere
[09:47] <bigon> could someone sponsor bug 439921 for me?
[09:57] <seb128> bigon, subscribe ubuntu-main-sponsors so it's on the sponsoring queue
[09:57] <seb128> we do sponsoring almost daily during the week
[10:00] <bigon> seb128: ok
[10:00] <ebroder> Is there a Python library that groks the apt repository format? I want to point something at an apt path and be able to poke at things like what version of a given package is in a particular component
[10:01] <ebroder> My current alternatives are parsing the output of reprepro or finding the Sources (or Sources.gz...) file and parsing that with python-debian, and those both kind of suck
[10:08] <skar> hi, i'm trying to apply a patch to glibc source pkg and compile it. now i've got a glibc-2.8~20080505/ dir with some bz2 files in there. how do i unzip them and then apply my patch?
[10:12] <pitti> cjwatson: hm, the recent usplash change doesn't seem to send QUIT to usplash any more, so that it fades out?
[10:12] <pitti> mat_t just complained
[10:12] <pitti> it seems to just stay around until the computer powers off?
[10:12] <cjwatson> pitti: yes, that was a hack to avoid text messages showing up after usplash quits but before shutdown
[10:13] <cjwatson> pitti: if we can make it fade but not actually tear down the graphical vt, that would be better
[10:13] <cjwatson> ebroder: python-apt should be able to do that?
[10:15] <mat_t> pitti: well, that's not really about me complaining, I just think it would be good to keep this effect, which was already very well received in the reviews etc
[10:15] <skar> hi, i'm trying to apply a patch to glibc source pkg and compile it. now i've got a glibc-2.8~20080505/ dir with some bz2 files in there. how do i unzip them and then apply my patch?
[10:17] <joaopinto> when switching to VTs I just get garbage output, it started last week, I see some more people reporting it at #ubuntu+1 could it be related to usplash changes ?
[10:17] <joaopinto> I get the same garbage output before gdm startup
[10:18] <cjwatson> it could, yes
[10:18] <joaopinto> I mean, for a second, I guess during a graphical mode transition
[10:18] <cjwatson> oh, it's not permanent? when you switch back to vt1, does that work ok?
[10:18] <joaopinto> it is permanent, but it also happens during boot, for a second, before gdm starts
[10:19] <joaopinto> it is permanent if I do a manual switch to a VT
[10:19] <joaopinto> I am using fglrx, not sure if that's part of the problem
[10:19] <cjwatson> it usually isn't part of the solution ;-)
[10:20] <cjwatson> usplash is meant to be torn down strictly before X starts
[10:20] <cjwatson> maybe usplash isn't managing to restore the console correctly with fglrx
[10:20] <cjwatson> that said, *that* part of the code hasn't changed recently to my knowledge
[10:20] <skar> how do i unzip glibc's source deb so that i can access the individual files under "build-tree"?
[10:20] <cjwatson> skar: there are usually debian/rules targets that help. (And please don't repeat yourself at five-minute intervals.)
[10:21] <joaopinto> skar, if you need to learn about packaging, #ubuntu-motu is probably a better place
[10:21] <pitti> cjwatson: I'm happy to add a new "FADEOUT" command to do just that, and not QUIT
[10:22] <pitti> mat_t: don't worry, it's justified :)
[10:22] <pitti> mat_t: I should have said "reported a bug"
[10:22] <mat_t> ;)
[10:23] <skar> cjwatson: thanks. i'll look into the source unpacking targets. won't repeat myself :)
[10:24] <skar> joaopinto: thanks, will ask in that channel :)
[10:32] <cjwatson> mat_t: it's a good effect, but I thought the text after usplash was even more likely to result in complaints at the moment ;-) having both is obviously the right answer
[10:33] <mat_t> cjwatson: absolutely :)
[11:22] <evand> pitti: is this indicative of the retracing service failing: https://bugs.edge.launchpad.net/ubuntu/+source/ubiquity/+bug/441709
[11:24] <pitti> evand: indeed, weird; let me check the logs
[11:25] <pitti> evand: hm, it's not even in the logs; I re-tagged it
[11:26] <evand> thanks!
[12:01] <evand> pitti: the retracer removed it again :)
[12:08] <Keybuk>  short read in buffer_copy (backend dpkg-deb during `./usr/lib/openoffice/basis3.1/program/libcuilx.so')
[12:08] <Keybuk> huh
[12:11] <seb128> Keybuk, there is quite some similar bugs on launchpad
[12:12] <Keybuk> seems to be an lzma issue?
[12:12]  * Keybuk is having it with the new linux-source too
[12:15] <Keybuk> that's odd
[12:15] <Keybuk> removing the file and redownloading it seemed to fix it
[12:15] <Keybuk> before:
[12:15] <Keybuk> Preparing to replace openoffice.org-core 1:3.1.1-2ubuntu4 (using .../openoffice.org-core_1%3a3.1.1-4ubuntu1_amd64.deb) ...
[12:15] <Keybuk> Unpacking replacement openoffice.org-core ...
[12:15] <Keybuk> lzma: Decoder error
[12:15] <Keybuk> dpkg-deb: subprocess <decompress> returned error exit status 1
[12:15] <Keybuk> dpkg: error processing /var/cache/apt/archives/openoffice.org-core_1%3a3.1.1-4ubuntu1_amd64.deb (--unpack):
[12:16] <Keybuk>  short read in buffer_copy (backend dpkg-deb during `./usr/lib/openoffice/basis3.1/program/libcuilx.so')
[12:16] <Keybuk> after:
[12:16] <Keybuk> Preparing to replace openoffice.org-core 1:3.1.1-2ubuntu4 (using .../openoffice.org-core_1%3a3.1.1-4ubuntu1_amd64.deb) ...
[12:16] <Keybuk> Unpacking replacement openoffice.org-core ...
[12:16] <Keybuk> kooky
[12:16] <Keybuk> the files were different sizes too
[12:18] <mvo> Keybuk: how much different?
[12:51] <pitti> evand: ah, got it now:
[12:51] <pitti> 10/12/09 10:51:02: retracing #441709
[12:51] <pitti> report file does not contain required fields: CoreDump Package ExecutablePath
[12:51] <pitti> evand: indeed the report doesn't have a Package: field
[12:52] <pitti> I wonder where that went
[12:59] <evand> ah, cool
[13:27] <Laibsch> lool, ArneGoetje: what about kasumi?  Has the window for MIR closed?
[13:27] <seb128> dholbach, joaopinto was wondering if there is any reason you didn't look at bug #439638 again or upload
[13:28] <Laibsch> ArneGoetje, lool: There is a new upstream release.  To avoid duplicate work, I'd like to work on that for Debian and fix what's necessary to finish the MIR for karmic.
[13:29] <dholbach> seb128: no, no reason just that I had a bunch of other stuff to do
[13:30] <dholbach> so if anybody wants to grab it, do it
[13:31] <seb128> dholbach, you touched it, you upload it I would say ;-)
[13:31]  * seb128 hugs dholbach
[13:31] <seb128> I will have a look later otherwise, still fighting my 800 emails backlog from the weekend
[13:31] <dholbach> seb128: lotsofemail: I totally see what you mean
[13:32] <chrisccoulson> seb128 - i don't envy your task of going through 800 e-mails ;)
[13:33] <lool> Laibsch: It's tight IMO
[13:34] <lool> Laibsch: Couldn't we revisit that next cycle?
[13:34] <lool> Laibsch: Does it cause serious issues in karmic?
[13:34] <Laibsch> I don't think so
[13:35] <Laibsch> It's about whether or not scim-anthy will get a bugfix that is in Debian or continue to have a delta explicitly to drop the fix
[13:37] <lool> Laibsch: If you need to merge a new scim-anthy to fix serious bugs, that's still ok at this time; but I wouldn't focus on dropping delta with Debian at this point of the cycle, we usually focus on that at the beginning of the ccyle
[13:37] <Laibsch> Well, I did focus on that around June ;-)
[13:37] <Laibsch> bug 332041
[13:38] <Laibsch> so, not a very serious bug
[13:38] <Laibsch> but one that was fixed in Debian
[13:39] <Laibsch> and we could otherwise sync scim-anthy from Debian (I made sure we can)
[13:39] <Laibsch> if kasumi was in main (or scim-anthy wasn't)
[13:39] <lool> I am not sure I can judge of the severity of this bug; I'd prefer if Arne would comment
[13:41] <Laibsch> it's not serious
[13:41] <Laibsch> scim-anthy is in main
[13:41] <Laibsch> there is a knob to pull up a user dictionary
[13:41] <Laibsch> that calls the kasumi program
[13:42] <Laibsch> currently kasumi is not installed by default, the fix is to recommend it
[13:42] <Laibsch> but kasumi is in univers
[13:42] <Laibsch> e
[13:42] <Laibsch> debian scim-anthy now recommends kasumi
[13:42] <Laibsch> and thus can't be synced
[13:43] <Laibsch> debian does the right thing, ubuntu can't until kasumi is in main
[13:43] <Laibsch> in essence, that is the issue
[13:45] <simon-o> kirkland: Hi, why is the default for byobu the commons keybindings and not the f-keys? Was this changes recently?
[13:47] <lool> Laibsch: I understood that part of the issue, I don't understand how much of a big deal it is to have this feature slightly broken
[13:48] <lool> Laibsch: The issues are relatively easy to fix though; I guess you could easily get a hold on these
[13:48] <Laibsch> It's obviously an easy fix: "sudo aptitude install kasumi"
[13:48] <Laibsch> lool: Actually, the build issues are not that easy for me
[13:48] <Laibsch> lots of new stuff
[13:49] <Laibsch> It will take me some time
[13:49] <lool> Laibsch: Ok; I can help you there
[13:49] <Laibsch> cool
[13:49] <lool> Laibsch: Looking at comment #1 on the MIR bug, which one is the first issue which you can't resolve?
[13:50] <Laibsch> I haven't gone through the comments
[13:50] <lool> Ok; ping me when you're stuck
[13:50] <Laibsch> sure
[13:50] <Laibsch> thanks
[14:31] <jml> hi
[14:32] <Keybuk> seb128: 800 e-mail backlog?
[14:32] <Keybuk> is that why you're only #3 in the bug traffic volume ranks this month? :p
[14:32] <jml> where might I find stats on the number of bugs filed per day against ubuntu?
[14:32] <Keybuk> the apport retracing service is beating you!
[14:35] <ion> keybuk: Any thoughts about what i posted to http://launchpad.net/bugs/432089, btw?
[14:35] <Keybuk> ion: foreground isn't enough
[14:36] <seb128> Keybuk, lol
[14:36] <ion> The bug report is about sreadahead performing poorly on a slow HDD, but my HDD is quite good for a laptop HDD and simply disabling sreadahead makes the system boot more than five seconds faster.
[14:36] <seb128> Keybuk, I can give you some bugs if you want ;-)
[14:38] <Keybuk> ion: how good is quite good?
[14:38] <Keybuk> seb128: I have plenty, I'm personally beating all of the QA team except pedro ;)
[14:40] <ion> keybuk: The laptop’s quite new, the HDD has a capacity of 320 GB and the maximum throughput in bootchart reaches 54 MB/s.
[14:40] <hunger> ion: How do you disable sreadahead?
[14:41] <ion> hunger: By commenting out the ‘start on...’ line.
[14:41] <hunger> Good point:-) I am not used to upstart yet:-)
[14:41] <Keybuk> ion: what's the hDD?
[14:42] <hunger> Keybuk: Hard Disc Drive?
[14:43] <ion> keybuk: http://pastebin.com/f53cf5098
[14:43] <Keybuk> ion: 5400RPM, 12ms seek
[14:44] <Keybuk> that fits the "slow drive" pattern
[14:44] <james_w> jml: ubuntu-bugs mailing list archive?
[14:44] <ion> keybuk: Ah, alright. I expected the ‘slow’ to mean something slower than a typical laptop HDD.
[14:45] <ion> Of course, a 5400 RPM laptop HDD *is* slow compared to a 7200 RPM desktop HDD.
[14:45] <Keybuk> no, I mean that typical laptop HDDs *are* slow
[14:45]  * liw thinks all hard disks are slow
[14:51] <jml> james_w, I was kind of hoping for something more digested than that.
[14:52] <james_w> jml: bdmurray might have stats
[14:52] <jml> james_w, I think that even if he does, Launchpad should track this information also.
[14:56] <james_w> jml: http://people.canonical.com/~brian/graphs/ but it seems to be busted right now
[14:56] <jml> james_w, thanks.
[14:57] <james_w> 10 minutes with http://people.canonical.com/~brian/graphs/bugstats.data could get you the information in the meantime
[14:59] <jml> ta
[15:06] <jdstrand> zul, mathiaz: hi! (I'm not really here) I just noticed bug #449358. The reporter's issue is clearly a dupe of 444479, however, I thought that it was odd that /usr/sbin/mysqld-akonadi was confined (I thought /usr/sbin/mysqld-akonadi was supposed to be a hard link and not a symlink). I'm not at all up on the akonadi packaging, but this sounds like it could be a problem
[15:21] <Riddell> seb128: your sync of poppler from April says "don't use openjpeg it's in universe", why not get openjpeg into main?
[15:23] <seb128> Riddell, I'm not the one who did the change I just reapplied the ubuntu diff we had
[15:23] <seb128> Riddell, it's slangasek who did the change iirc
[15:24] <seb128> Riddell, I've no opinion on the topic
[15:28] <Riddell> seb128: mm, the changelog is incomplete, found the complete changelog on lauchpad
[15:28] <Riddell> slangasek: " Disable openjpeg on all archs for Ubuntu, this lib is in universe
[15:28] <Riddell>     and isn't needed."
[15:28] <Riddell> slangasek: any reason for that?  it is needed if you want to see jpeg2000 decently
[15:30] <seb128> Riddell, right, I don't copy all the changelog entries when resyncing on debian but just summarize the changes
[15:33] <geser> can a core-dev please give-back bacula (FTBFS fixed by recent upload of libbonoboui)
[15:38] <pitti> geser: done, thanks!
[15:39] <seb128> jdstrand, hey, could you look to bug #447292?
[15:39] <seb128> jdstrand, not sure if that's an apparmor or evince issue
[15:40] <seb128> jdstrand, I guess the issue is due to nfs user dir
[15:40] <seb128> jdstrand, bug #449286 too
[15:40] <jdstrand> seb128: that is a dupe of another bug that jjohansen is working on a fix for
[15:41] <jdstrand> seb128: (the first one that is)
[15:41] <jjohansen> jdstrand: building a new test kernel on that one, should have something up soon
[15:41] <jdstrand> seb128: hmm, the second is thornier
[15:43] <jdstrand> seb128: I've assigned ti to me for now-- it can probably be solved in apparmor
[15:44] <jdstrand> seb128: btw, I'm not here today :)
[15:44] <jjohansen> hehe me neither :)
[15:45] <jdstrand> jjohansen: I didn't have a chance to test your nfs fix yet. I won't until tomorrow (at which point I am still 'not here', but can test your kernel)
[15:46] <jjohansen> jdstrand: okay :)
[15:47] <jdstrand> jjohansen: do you have that bug number off-hand?
[15:47] <jdstrand> s/off/on/
[15:48] <jjohansen> jdstrand: Bug #415632
[15:48] <jdstrand> jjohansen: thanks
[15:54] <seb128> jdstrand, ok, thanks for replying, enjoy your holiday ;-)
[15:54] <Keybuk> ugh
[15:54] <Keybuk> trying to figure e2fsck out, every time I think I'm getting close, I get eaten by a grue
[16:24] <tkamppeter> pitti, I have found a big problem in CUPS 1.4.1: It seems that for broadcasts it always uses the host name and never tyhe IP of the server (in 1.3.x it used the IP). This requires that host names in networks are always well-defined and this is not the case in many small networks or for temporarily connected machines.
[16:25] <pitti> tkamppeter: hm, is that configurable?
[16:28] <tkamppeter> pitti, there is a ServerName entry in cupsd.conf where one can set this, by default this is not set.
[16:30] <tkamppeter> pitti, I have tried "cupsctl ServerName=192.168.2.105" now and got a correct entry in cupsd.conf, but the client still gets "ipp://noname:631/printers/b" in lpstat -v (for the printer b on the server).
[16:31] <tkamppeter> pitti, I have even tried to restart CUPS on the server but this does not help.
[16:31] <Keybuk> dear git.  how is not pushing tags by default *useful* ?
[16:32] <pitti> well, it's just consistent
[16:32] <pitti> "1. No command shall do useful things without any arguments."
[16:32] <pitti> tkamppeter: hm, I'm using cupsd from my wife's computer, it seems to get picked up just fine
[16:32] <pitti> ipp://dagobert.local:631/printers/ML-1610
[16:32] <pitti> ah, heh
[16:33] <pitti> .local names FTW
[16:33] <chrisccoulson> Keybuk - do you not like git?
[16:34] <ion> :-D
[16:34]  * pitti sees Keybuk turn red and explode
[16:34] <ebroder> Wait, why is subscribing ubuntu-archive to bug #429445 the wrong thing? It's a sync that's been approved by ubuntu-release...
[16:35] <pitti> ebroder: fixing bug again
[16:35] <sistpoty|work> seb128: what's wrong with the fix in bug #445633?
[16:35] <seb128> sistpoty|work, why do you want to run autotools there?
[16:35] <sistpoty|work> seb128: b-d on autotools-dev?
[16:36] <sistpoty|work> seb128: so config.sub/.guess don't match the current version?
[16:36] <james_w> ebroder: it needs a sponsor check
[16:36] <seb128> sistpoty|work, well, why? I would have went the other way, make sure autotools are not run at build time
[16:36] <seb128> sistpoty|work, but why is there any need to run autotools at all there?
[16:36] <sistpoty|work> seb128: iirc they aren't, but rather run and in the patch
[16:37] <seb128> sistpoty|work, configure && make && make install ought to work from the tarball
[16:37] <tkamppeter> pitti, does your wife have Karmic (or CUPS 1.4.x) on her box?
[16:37] <seb128> why do you want to run autotools in the diff or at build time
[16:38] <sistpoty|work> seb128: due to the version mismatch of autoconf
[16:38] <seb128> sistpoty|work, what mismatch?
[16:38] <tkamppeter> pitti, in addition in your network host names seem to be well defined, but this is not assured in all networks.
[16:38] <sistpoty|work> seb128: "aclocal.m4:16: warning: this file was generated for autoconf 2.63." --> build fail
[16:38] <sistpoty|work> seb128: what would be the better way to fix this?
[16:38] <Keybuk> pitti: I have an apport hooks question
[16:38] <seb128> sistpoty|work, but why are autotools run in the first place during the build?
[16:39] <seb128> sistpoty|work, not run any autotools at all since we don't change any build file there
[16:39] <Keybuk> do you think it would be possible to create a hook that includes the reporter's exact location, address, GPS info, etc. and usual times when they are there
[16:39] <Keybuk> that way the next time someone reports a "last mount time in future" bug, I can go round their house with a shotgun? :p
[16:39] <sistpoty|work> seb128: isn't there a configure script that gets run? (/me looks at pygobject again)
[16:39] <seb128> Keybuk, I though that bug was fixed?
[16:40] <seb128> sistpoty|work, configure && make yes, configure != autotools
[16:40] <Keybuk> seb128: the bug is fixed, the fact that users are idiots is not fixed
[16:41] <liw> Keybuk, you can get the location from LP for many people...
[16:41]  * Keybuk has submitted http://permalink.gmane.org/gmane.comp.file-systems.ext4/15847
[16:41] <seb128> sistpoty|work, the fix would probably be to comment 03_maintainer_mode.patch from the serie
[16:41] <Keybuk> which will probably be refused by upstream ;)
[16:41] <Keybuk> . o O { maybe I just need Ted Tso's location :p }
[16:41] <seb128> sistpoty|work, that's useful only in the case you have an autotools update change
[16:42] <sistpoty|work> seb128: would that build then? the patch-stamp target copies config.sub/.guess from autotools-dev, so these mismatch the other generated files in the build
[16:43] <seb128> sistpoty|work, why a config.sub and config.guess update trigger an autotools run?
[16:43] <seb128> sistpoty|work, and if that's the case why do we need to update those to start?
[16:44] <seb128> sistpoty|work, we don't have an autotools patch in every package doing a config.guess update
[16:44] <Keybuk> seb128: can't see any reason they should
[16:44] <Keybuk> config.guess is used by configure *invocation* not by autoconf
[16:46] <Keybuk> just grepped through automake, they certainly shouldn't
[16:46] <seb128> sistpoty|work, I guess the issue there is the maintainer mode change updating configure.ac and autotools trying to be clever
[16:47] <seb128> sistpoty|work, the fix I guess would be to just comment the unrequired configure.ac from the series
[16:47] <sistpoty|work> seb128: hm... that would make sense, indeed
[16:48] <\sh> moins
[16:49] <ebroder> cjwatson: I looked at python-apt, but I can't figure out a way to point it at an arbitrary repository, as opposed to just examining what's in my sources.list
[16:50] <Keybuk> seb128: why would it update configure.ac ?
[16:50] <Keybuk> ironic if trying to turn off maintainer mode resulted in one last rebuild just for luck <g>
[16:50] <seb128> Keybuk, there is a patch to set the maintainer mode which is useful sometimes
[16:50] <Keybuk> just leave it on - it doesn't hurt
[16:51] <seb128> Keybuk, no, it's setting it on so when we have versions with autoreconf patches things are not run on buildds again
[16:51] <Keybuk> adding autoconf, automake, libtool to build-depends is easier than having to keep an autoreconf patch up to date ;)
[16:51] <Keybuk> we could even have an "autoreconf" meta package that depended on the current versions :)
[16:52] <seb128> running those at build time sucks
[16:52] <seb128> it takes build time and create often issues when different versions are used
[16:53] <seb128> working sources start ftbfsing which lead to extra work
[16:59] <cjwatson> ebroder: you can configure it in much the same way you configure other apt tools, by setting options
[16:59] <cjwatson> apt.conf(5) has details
[16:59] <cjwatson> you may need to write a temporary sources.list file
[17:02] <lool> OMG linux-libc-dev didn't build on armel since the linux-* trees were split
[17:02] <lool> We still have 2.6.31-5.24
[17:02] <lool> apw: ^^  It this known?
[17:03] <cjwatson> oh, yeah, I noticed that myself
[17:03] <cjwatson> seems worth fixing ;-)
[17:03] <lool> That seems a really serious issue to fix before end of week
[17:04] <cjwatson> need to make the linux source build just that binary on armel, presumably
[17:05] <lool> Yeah
[17:05] <lool> With a sensible config
[17:06] <apw> lool, when we were discussing linux-libc-dev earlier in the week it was implied it was architectur eindependant
[17:08] <lool> apw: You mean subarch
[17:08] <apw> actually we were talking about it being built 'only on i386' cause it was 'all'
[17:08] <apw> sounds like its not
[17:08] <lool> apw: We were discussing issues related to subarch specific divergences in linux-libc-dev, how to handle that; but in all cases our armel packages should be built against a standard linux-libc-dev, subarch independent
[17:09]  * apw will have a look at that, that sounds all foobared
[17:09] <lool> apw: I'm not sure whether headers rely on a .config or not, but it seems there's a target to generate all headers at once
[17:09] <lool> bug #449637
[17:09] <lool> apw: make headers_install_all
[17:09] <lool> "The command "make headers_install_all" exports headers for all architectures
[17:10] <lool>  simultaneously.  (This is mostly of interest to distribution maintainers, who create an architecture-independent tarball from the resulting include directory.)
[17:10] <apw> lool, its clearly broken ... will get it discussed shortly
[17:12] <Riddell> ccheney: how much of the fixes from shtylman for bug 424132 are in our packages?
[18:08] <joaopinto> any core dev available that could me help me testing a bug that migh be classified as security vulnerability ?
[18:09] <zul> jdstrand: im not here either Ill take a look at it tomorrow
[18:22] <Darxus> That's odd.  If I run X by itself (no window manager, etc.) I just get a blank screen.  Not even a mouse.  Jaunty though.
[18:31] <lfaraone> Is there a reason that one can no longer "remember this authorization" for administrative actions in Karmic? (ex: setting CPU scaling via the applet)
[18:32] <jcole> happy monday
[18:32] <lfaraone> jcole: you too.
[18:32] <jcole> what would it take to get evolution-mapi functional in ubuntu karmic? if someone would tell me, i'll host a functional version internally
[18:32] <jcole> or even a ppa
[18:34] <jcole> this is bugs 446626 435881 etc.
[18:35] <jcole> the evo guys claim it works in suse
[18:36] <Darxus> Ignore what I said about X.  I don't know why I didn't find the mouse.  The default background should *not* be all black.
[18:38] <jcole> if i was to alien up the suse evolution-mapi rpms to .debs, can those be posted to a ppa? or, are ppa for source only?
[18:40] <chrisccoulson> jcole - no, that won't work
[18:42] <jcole> chrisccoulson: any suggestions?
[18:42] <chrisccoulson> it needs properly packaging as a source package
[18:44] <jcole> chrisccoulson: is there any tools for converting suse source packages to debian/ubuntu
[18:44] <chrisccoulson> i'm not familiar with packaging in suse at all
[18:48] <jcole> chrisccoulson: i know a few guys here running evolution-mapi on suse.. i'll ask them about converting source packages...
[18:49] <chrisccoulson> You would need to make a Debian package from scratch if there isn't one already
[18:49] <jcole> chrisccoulson: there is one already
[18:49] <jcole> chrisccoulson: it just doesnt work
[18:50] <chrisccoulson> you should try and fix the existing package then ;)
[18:50] <fagan> mvo: *ping*
[18:51] <chrisccoulson> evolution-mapi is in karmic anyway. what doesn't work with it?
[18:51] <jcole> chrisccoulson: that is what im trying to do.. if i could figure it out, ill post a working version internally
[18:51] <jcole> chrisccoulson: it crashes when reading a message
[18:51] <mvo> fagan: pong
[18:52]  * james_w hugs mvo 
[18:52] <james_w> good timing
[18:53] <mvo> hey james_w
[18:53] <james_w> mvo: update-notifier has started (in karmic) shipping /var/crash, with standard permissions, which prevents apps running as a non-root user from reporting crashes
[18:53] <james_w> mvo: I guess this isn't intentional?
[18:53] <jcole> chrisccoulson: https://bugs.launchpad.net/ubuntu/+source/evolution-mapi?orderby=-datecreated
[18:53] <james_w> update-notifier-common sorry
[18:55] <jcole> chrisccoulson: last 4 bugs
[18:55] <mvo> james_w: no, not intentional (and odd)
[18:56] <mvo> james_w: I can't remember changing that :/ is there a open bug about this?
[18:56] <james_w> mvo: the fix is probably easy, but I guess we should do something to fix it for current users?
[18:56] <james_w> mvo: I'm just looking for one now
[18:56] <james_w> I just discovered this now with the help of ahasenack
[18:58] <fagan> mvo: im just looking into Bug #438870 could you point me to the part of the software store that deals with installing the software
[18:58] <jcole> chrisccoulson: i tried to install a newer version of evolution-mapi from debian unstable... but its compiled against a newer evolution so dependency fail
[18:59] <mvo> fagan: it does probably need support from aptdaemon, my idea was to start a transaction with --download-only
[19:00] <fagan> mvo: that would work
[19:00] <mvo> fagan: there is a apt config option that can be set if that is all that is required, it may run into issues with multiple locks, in this case its probably best to just create private download dirs and move them into place when all is finished
[19:00] <jcole> chrisccoulson: thre is also a gnome bug for this at https://bugzilla.gnome.org/show_bug.cgi?id=595810 ... but, why does it work in suse? does this bug only apply to the version in karmic?
[19:01] <mvo> fagan: so the transaction would be split into (download, install) and download could be done in parallel
[19:01] <fagan> mvo: yep that would be a lot quicker than the current system too
[19:01]  * wolfe yawns
[19:02] <chrisccoulson> jcole - i'm sorry, but i've no idea why that would be the case. evolution-mapi isn't a package i have any particular interest in, so i don't know much about it ;)
[19:03] <wolfe> :|
[19:03] <james_w> mvo: can't find a bug on either update-notifier or apport, so I'll file one and we can discuss how to do the fixup at the same time as the fix?
[19:03] <mvo> fagan: ideally we would make the daemon so clever that it automatically does that (transparent to the frontend)
[19:03] <mvo> james_w: yes, sounds good to me
[19:04] <james_w> "Package update-notifier-common does not exist"
[19:04] <james_w> oh, typo
[19:06] <fagan> mvo: That would be the ideal solution and it could be done by lucid
[19:07] <mvo> fagan: great, I will not have time to look into it myself before karmic-final, but I'm happy to help and give feedback :)
[19:07] <mvo> james_w: I will have to leave soon for tonight, but I will have a look tomorrow morning
[19:08] <james_w> mvo: sure, I thought you had gone already.
[19:09] <fagan> mvo: ill give it a look :)
[19:09] <mvo> james_w: I was (almost) - but then there was a odd FTBFS that looks like something in python recently broke my setup.py :(
[19:09] <james_w> mvo: you fixed it?
[19:10] <mvo> doko_: could you please have a look at bug #449734 ?
[19:10] <mvo> james_w: no, I don't have a fix yet - is this a known issue ?
[19:11] <james_w> mvo: not that I have heard
[19:12]  * fagan gos back to his super secret project so it can be ready for the UDS
[19:14] <jcole> chrisccoulson: ya, this is not your normal "consumer" package... and, it probably works in suse because they target the "enterprise" desktop whereas ubuntu targets the "consumer" desktop... but, i'd still like to get a working version in ubuntu for those of us that want to run ubuntu... maybe you could direct someone to me who knows about this package and ill create a working version in a ppa :)
[19:14] <chrisccoulson> jcole - do suse use a different upstream version? Do they have any patches that might fix it?
[19:15] <doko_> mvo: looking
[19:17] <james_w> I see a very suspicious hunk in the diff for the last upload
[19:17] <james_w> doko_: http://paste.ubuntu.com/291771/
[19:17] <mvo> doko_: thanks
[19:18] <james_w> mvo: do you have python-pyrex installed in the error case?
[19:18] <mvo> james_w: I'm not sure, but it happens on a pbuilder too
[19:18] <james_w> probably not then
[19:18] <jcole> chrisccoulson: im thinking its not actually evolution-mapi itself (since it just creates the account)... but suspecting the underlying libmapi libraries and/or the evolution email rendering engine
[19:19] <mvo> no pyrex
[19:19] <mvo> james_w: I saw that too, its in tests/ though, this is puzzling
[19:19] <jcole> chrisccoulson: im looking for a way to browse suse source
[19:19] <james_w> mvo: the hunk I pasted?
[19:19] <james_w> python2.6-2.6.4~rc1/Lib/distutils/command/build_ext.py
[19:20] <mvo> james_w: oh, sorry
[19:20] <mvo> james_w: indeed, its in build_ext.py - its pretty certainly the problem :)
[19:20] <mvo> james_w: amazingly quick!
[19:20] <james_w> just looking for the bug that was fixing
[19:21] <james_w> python bug 7064
[19:21] <james_w> no! python!
[19:21] <mvo> heh :)
[19:22] <james_w> http://bugs.python.org/issue7064
[19:23] <jcole> chrisccoulson: whats really stupid about exchange server, is that not only does it save messages on the server as .txt and .html, but also as .rtf ... im wondering if the evolution rendering engine in ubuntu is crapping out on those, because it only crashes on certain messages
[19:27] <james_w> mvo: perhaps it should be "Extension('UpdateManager.fdsend',"?
[19:27] <james_w> that's what the documentation implies?
[19:28] <james_w> i.e. use the dotted module name, not the path to the module dir
[19:28] <jcole> jcole: /j #suse
[19:28] <jcole> bleh
[19:28] <wolfe> ewww, suse ;D
[19:28] <wolfe> lynch him!
[19:28] <james_w> wolfe: easy please
[19:29] <chrisccoulson> jcole - i don't know - you seem to have a better grasp of the issue than me ;)
[19:30] <chrisccoulson> i can't help you much as i'm trying to figure other things out right now
[19:30] <jcole> chrisccoulson: of course, thanks for your time... i'll figure out something for us ubuntu users :)
[19:30] <chrisccoulson> thanks:)
[19:36] <mvo> james_w: thanks, I try that now
[19:51] <samba> hi all - i'm working with a number of chroots that need to include valid kernels and modules (like PXE boot) but when I install updates on the server, DKMS tries to build against the running kernel (via uname) - is there any way to override that?
[19:52] <samba> (i.e. i want it to look at installed kernels - in /lib/modules or so - not at uname)
[19:54] <samba> (I see the options on dkms itself, but i'd like it configurable so DKMS will automatically map to the proper kernel)
[19:57] <slangasek> Riddell: if I said it wasn't needed, I must have consulted someone before dropping the dep, but I don't know who
[20:22] <tkamppeter> pitti, still there?
[20:26] <debfx> slangasek: have you had a chance to look at my updated powerdevil detection for acpi-support (https://code.edge.launchpad.net/~debfx/acpi-support/fix-lp387750/+merge/12466)?
[20:42] <Steeley> Cisco IOS
[20:42] <Steeley> oops, apologies. wrong channel
[21:13] <wamty> having trouble with vnc-viewing my ubuntu desktop, when I single click it almost always translates it into a double click, makes it impossible for me to do anything, any ideas?
[21:14] <lucas_> Hi there, I would like to report a bug with some ruby files but I don't  know  how to find which package the files involved belong to
[21:14] <lucas_> for instance  /usr/lib/ruby/1.8/x86_64-linux/rbgtk.h has some includes of files that are not provided
[21:15] <spaetz> lucas, dpk -S file ???
[21:15] <spaetz> dpkg
[21:15] <wamty> ideas?
[21:16] <lucas_> ok so the culprit is ruby-gnome2-dev
[21:16] <kklimonda> wamty, you would have more luck on #ubuntu channel probably.
[21:16] <wamty> i did
[21:16] <wamty> noone answered there
[21:17] <lucas_> spaetz, I ve seen that it was corrected in debian ? should I report a bug on launchpad ?
[21:18] <spaetz> no clue, i'm no ubuntu dev
[21:18] <spaetz> but reporting a bug can never hurt
[21:19] <lucas_> ok because it seems to prevent me from building a gnome/ruby app
[21:19] <wamty> so?
[21:19] <kklimonda> lucas, yes, you should report that (make sure that it wasn't reported before)
[21:19] <spaetz> lucas, if you report it, do point to the resolution in debian
[21:20] <lucas_> kklimonda, definetly I will, but it is really unlikely that it was, since at that stage such things should have come up. I believe the fix is available form debian packages
[21:20] <spaetz> bug no, etc
[21:20] <lucas_> I will
[21:20] <lucas_> thanks
[21:21] <mdke> pitti: many thanks for looking at that ubuntu-docs issue, I'll fix it accordingly
[21:22] <lucas_> BTW do you guys now a way to report bugs without the command ubuntu-bugs, I find myself unable to find the appropriate menu on launchpad
[21:22] <kklimonda> wamty, you could try ubuntuforums.org, I think that you have the best chance of getting a good answer there (#ubuntu channel is crowded and this one is for development discussion)
[21:23] <kklimonda> lucas, when you are redirected to the wiki page scroll down and you will see a direct link (with ?no-redirect argument) you can use
[21:29] <tgpraveen1> the launc hpad has been made too difficult to file bugs
[21:29] <tgpraveen1> now
[21:33] <ccheney> Riddell: all except the ones sent this morning
[21:42] <chrisccoulson> james_w - have you experienced the hanging policykit dialog recently?
[21:42] <james_w> hey chrisccoulson
[21:42] <james_w> never have
[21:42] <chrisccoulson> hmmm
[21:42] <chrisccoulson> i haven't seen it for a while either
[21:42] <james_w> I'm a bit lost to be honest
[21:42] <chrisccoulson> i wonder if it's magically fixed now? ;)
[21:42] <jdong> chrisccoulson: I've seen it today
[21:42] <chrisccoulson> i hate not understanding why things are broken
[21:42] <jdong> chrisccoulson: happens when I use ENTER to confirm my password entry
[21:43] <jdong> the password textbox disappears
[21:43] <jdong> but the dialog still persists
[21:43] <chrisccoulson> jdong - i wish i could recreate it reliably
[21:43] <jdong> clicking either button is NOACTION
[21:43] <spaetz> the one with no line to enter a passwd? got that dialog today
[21:43] <chrisccoulson> i might try pressing enter and see if it makes a difference
[21:43] <jdong> but clicking the window's X causes update-maanger to work
[21:43] <jdong> chrisccoulson: yeah clicking Authenticate the first time works 100% for me
[21:43] <jdong> chrisccoulson: but pressing ENTER "hangs" the dialog 100%
[21:43] <james_w> enter works for me
[21:43] <james_w> jdong: 100%?
[21:43] <jdong> :-/
[21:43] <james_w> you're just the person we've been looking for!
[21:43] <jdong> james_w: well 4 of the 4 times I've tried in the past 2 days :)
[21:44] <jdong> in fact let me humor myself and do it right now!
[21:44] <james_w> jdong: would you do some debugging for us please?
[21:44] <jdong> sure
[21:44] <jdong> GRR it worked this time
[21:44] <chrisccoulson> lol
[21:44] <jdong> well ok 80% :P
[21:44] <chrisccoulson> it worked here too;)
[21:44] <jdong> so I guess I just need to complain to the right people!
[21:45] <jdong> AH BROKE THIS TIME!
[21:45] <jdong> ok I've got an authenticate dialog without a textbox
[21:45] <jdong> what would you like me to do?
[21:45] <james_w> can you "strace -p $(/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1)"
[21:45] <james_w> oh, with -f as well
[21:45] <james_w> doing that before triggering it would be good
[21:46] <james_w> you know you can drop priveledges with the "keys" icon in the notification area?
[21:46] <jdong> correct
[21:46] <james_w> cool
[21:46] <james_w> you'll want to check that your password isn't in the strace output before you show us
[21:47] <chrisccoulson> i need to learn how the new policykit works:)
[21:47] <james_w> that process runs in your session all the time
[21:48] <james_w> it registers with polkitd when it starts as the agent for your session
[21:48] <james_w> when something requests auth polkitd calls it over D-Bus with the info that it needs
[21:48] <jdong> ok got it to happen
[21:48] <james_w> it then pops up and asks for the passwords
[21:48] <jdong> once thin that I do notice:
[21:49] <james_w> at the same time it runs a suid helper to talk to pam
[21:49] <jdong> when it works, strace just says "pid 65xx attached"
[21:49] <jdong> but when it doesn't work, I get multiple attached and detached messages from strace
[21:49] <jdong> with pid's in the high-25000 region
[21:49] <james_w> once you give the password it gives this to the helper
[21:49] <jdong> seems like it's spawning some new pid repeatedly
[21:50] <james_w> it auths with pam, and then calls back over D-Bus to polkitd to tell it all is well
[21:50] <james_w> chrisccoulson: clear? ;-)
[21:50] <chrisccoulson> james_w - i think so;)
[21:50] <james_w> jdong: interesting, could we see the redacted trace?
[21:50] <jdong> http://jdong.mit.edu/~jdong/broken_polkit_strace.txt
[21:50] <jdong> james_w: this time it didn't even ask me for a password the first time... :-/
[21:50] <james_w> thanks
[21:50] <james_w> really?
[21:52] <jdong> james_w: http://jdong.mit.edu/~jdong/broken_polkit.png
[21:52] <jdong> the dialog looked like that
[21:52] <jdong> and there was no key in the systray either
[21:52] <jdong> neither of the two buttons do anything, and I clicked them a couple times during the strace
[21:52] <wamty> I googled this and can't getr a straight answer. anyone else running ubuntu 9.04 server with wifi? The adapter is listed, I can ifconfig it and it's tx/rx packets, but I have no outside network access.. I explored all avenues at the command line. The *only* thing I noticed is that the listed supported encryption modes do NOT include WEP, which is what i'm using (crucify me for this later please). The onyl ubuntu network manager handled this
[21:52] <jdong> clicking the big X did work
[21:52] <wamty> FWIW, my old version was 6.06 and it worked fine.. also on the post 6.06 releases RADI croaks one of my drives.. but it works fine and is physically configured fine. Hit a brick wall there as well.
[21:53] <jdong> wamty: -> #ubuntu
[21:53] <james_w> polkit-grant-helper-pam: needs t
[21:54] <james_w> "...to be setuid root" I predict
[21:54] <james_w> does strace interfere with suid?
[21:54] <jdong> james_w: I don't think it does when attached to an existing process...
[21:54] <jdong> at least as far as I understand
[21:55] <james_w> well, it's going to be tracing the spawned process, so it might thee
[21:55] <james_w> I think I know what the race is that breaks it in this case
[21:56] <james_w> but I'm not sure that will be what breaks it normally
[21:56] <jdong> I'm gonna be out for 10m to grab dinner but will check back if I can provide any more assistance :)
[21:56] <james_w> thanks
[22:20] <wolfe> how sad, I see 10m and think 10 meters, as in radio frequency :)
[22:22] <directhex> how do i see the current nbs list?
[22:22] <seb128> directhex, http://people.canonical.com/~ubuntu-archive/NBS/
[22:23] <directhex> webkit, thought so
[22:28] <james_w> jdong: some packages put at https://edge.launchpad.net/~james-w/+archive/polkit/+packages
[22:29] <james_w> if you could install libpolkit-agent-1-0 from there and then kill the process you were stracing and launch it again as "strace -f -o /tmp/strace.txt /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1" that would be great
[22:29] <james_w> if I am right you won't be able to trigger the lack of the password to start with any more
[22:30] <james_w> but it will always fail
[22:32] <james_w> so it won't have really got us anywhere, but we might as well fix bugs as we find them
[22:32] <james_w> "man strace" states that if you make the strace binary suid root then you can strace suid programs correctly
[22:33] <james_w> would you be willing to do that while we test
[22:33] <james_w> if so, then please do so and re-run the above, and you should see the prompt as before
[22:33] <james_w> and if you can then trigger it the strace should be useful
[23:03] <Darxus> There's no 2038 bug open?