[00:57] <KernelKlick> ﻿I would like to install ubuntu on an older machine...the problem is that the installation CD doesnt work on the machine because it does not have a coproc.  Can I make a kernel that will work with math emulation and then install ubuntu?
[00:57] <KernelKlick> not sure if I should ask here or in desktop
[00:58] <KernelKlick> or installer
[00:58] <KernelKlick> LOL
[01:22] <LaserJock> sommer: around?
[03:31] <sommer> LaserJock: yo
[03:36] <bddebian> lool: You around by any chance? (gdebi)
[07:12] <nxvl> Pici: when you have time please take a look at Bug #248605 for pbuilder to build
[07:12] <nxvl> err
[07:12] <nxvl> pitti: when you have time please take a look at Bug #248605 for pbuilder to build
[07:12] <nxvl> Pici: sorry!
[07:12] <nxvl> pitti: Thanks!
[08:27] <Iulian> Good morning.
[09:20] <Riddell> asac: https://bugs.edge.launchpad.net/ubuntu/+source/network-manager/+bug/248630
[09:22] <asac> Riddell: can you add your type https://wiki.ubuntu.com/NetworkManager/Hardware/3G as well?
[09:27] <slytherin> Is this a right channel to ask about chippit?
[09:27] <slytherin> /chippit/shippit
[09:28] <slytherin> Will shipit now ship 8.04.1?
[09:28] <TheMuso> I'm looking at making use of some X protocol bits in python. According to http://x-python.sourceforge.net/ there is an X extension for python, however I am unable to find it in Ubuntu anywhere. python-xlib is not it, and while python-xlib implements some of what I need, it doesn't implement everything. Thoughts/suggestions welcome.
[09:29] <gnomefreak> slytherin: not likely
[09:29] <slytherin> gnomefreak: any particular reason?
[09:30] <gnomefreak> slytherin: they cut down on amount you can order, they didnt do it for dapper
[09:30] <gnomefreak> theres 2 off top of head
[09:30] <cjwatson> gnomefreak: err, I'm pretty sure shipit *will* ship 8.04.1
[09:30] <cjwatson> gnomefreak: do you have authoritative information to the contrary?
[09:30] <gnomefreak> cjwatson: to people that already order cds?
[09:31] <gnomefreak> cjwatson: no just what has been done over the last few releases
[09:31] <cjwatson> obviously there needs to be some kind of cut-off where they start with the new set
[09:31] <slytherin> gnomefreak: Sorry for bein unclear. I was talking about orders henceforth.
[09:31] <cjwatson> gnomefreak: would prefer if you didn't give non-authoritative answers, thanks
[09:31] <cjwatson> I'm fairly sure that 8.04 shipit was stopped following the openssl vulnerability
[09:32] <slytherin> cjwatson: I was assuming that shipit will ship 8.04.1. But the website still says 8.04. Do you know anyone I can ask for confirmation?
[09:32] <cjwatson> correct answer coming along shortly ...
[09:33]  * slytherin waits
[09:34] <slangasek> slytherin: so the situation is that shipit is trying to exhaust their rather extensive existing inventory of 8.04.0 CDs before switching over to 8.04.1
[09:34] <slangasek> slytherin: any 8.04.0 CDs that are still being sent out are being given an insert that explains that the upgrades are needed
[09:35] <slangasek> slytherin: and in practice, the demand for 32-bit CDs is such that I'm told they've already switched over to 8.04.1 (with new cover art &c)
[09:36] <slytherin> slangasek: Ok. That is fair enough. Thanks for official word.
[09:36] <slangasek> n/p
[09:37] <tseliot> ﻿TheMuso: Python bindings for XCB, perhaps? http://xcb.freedesktop.org/XcbPythonBinding/
[09:37] <TheMuso> tseliot: thanks, I'll take a look.
[09:39] <bryce_> mvo: forwarded the two bugs
[09:40] <TheMuso> tseliot: Hrm at a glance there is nothing related to python and xcb in the archive. However I'll take a look at the link you posted.
[09:41] <bryce_> TheMuso: what are you looking for specifically?
[09:43] <TheMuso> bryce_: I need access to PriorityNotify, XInternAtom, and defining atoms. Basically I have some C code in one project that I need to rewrite in python.
[09:44] <TheMuso> bryce_: The code is used in gnome-session to detect at-spi-registryd startup, using PropertyNotify, and some other stuff I'd need to read again to be sure what it does.
[09:44] <TheMuso> bryce_: Basically I need to implement the same code for ubiquity's accessibility code, to make the same check, that at-spi-registryd starts correctly.
[09:45] <bryce_> hmm
[09:45] <bryce_> looking
[09:45] <mvo> bryce_: execellent, thansk a lot !
[09:47] <TheMuso> bryce_: Thanks.
[09:47] <mvo> TheMuso: you could use the ctypes module if there is nothing else available (also this is of course a bit ugly)
[09:47] <bryce_> TheMuso: http://python-xlib.sourceforge.net/doc/html/python-xlib_13.html looks the right direction
[09:48] <TheMuso> bryce_: Hrm ok, must have not looked hard enough at that. I will take another look, thanks.
[09:49] <bryce_> TheMuso: both PropertyNotify and XInternAtom are xlib functionality, so I think the ordinary python-xlib binding would be enough
[09:51] <bryce_> fwiw, 'xcb' == 'X11 C Binding' and is just an alternative binding for the X11 protocol, like xlib.  In fact, it aims to replace it (there is also an xcb-xlib package that implements the xlib APIs using xcb to communicate with the server)
[09:53] <TheMuso> bryce_: Ok the only thing that looks odd to me, is that it appears that the intern_atom method for pythonx-lib only takes two arguments, whereas the code I am porting calls XInternAtom with three arguments. See http://python-xlib.sourceforge.net/doc/html/python-xlib_16.html however I could be reading that incorrectly.
[09:54] <bryce_> what's the code you're porting?
[09:55] <jcristau> TheMuso: it's a method for a Display object, so there's your third argument
[09:55] <bryce_> ah nevermind, I got it
[09:55] <bryce_> yeah the python lib seems to be OO, so 'display' is an internal property of that and doesn't need passed in
[09:56] <bryce_> TheMuso: so you should be safe to use that
[09:58] <TheMuso> bryce_: Thanks a bunch.
[09:59] <TheMuso> bryce_: If you rae interested in the code I need to port if youare interested, its in the gnome-session package, gnome-session/gsm-at-startup.c, the first couple of functions in that file.
[09:59] <TheMuso> gah typing
[10:18] <poningru> quick question what is valusofts relationship with canonical?
[10:18] <poningru> how much profit does canonical derive from valusoft?
[10:19] <Mithrandir> poningru: I doubt you'll find any information about Canonical's revenue streams in here.
[10:19] <poningru> hehe
[10:20] <poningru> I should probably just use email
[10:20] <poningru> thanks anyway
[10:24] <cjwatson> you shouldn't necessarily expect to get an answer to questions about commercial relationships anyway; *some* things are sensitive ...
[10:24] <cjwatson> and, by default, questions of the form "how much money" are likely to be sensitive unless and until Canonical becomes a publicly traded company
[10:25] <poningru> cjwatson: true
[10:26] <tjaalton> bryce_: fixing 15477 would only reveal 14441, and I thought it wasn't worth it for alpha2
[10:26] <tjaalton> damn builtin 3G, broke just in time for my vacation..
[10:28] <bryce_> heya tjaalton
[10:28] <bryce_> tjaalton: yes I passed both bugs along to mvo
[10:29] <tjaalton> hi bryce_.. because of the aforementioned problem my connectivity is below average ;)
[10:30] <poningru> oh I did have a question that is answerable
[10:30] <poningru> so there is a new chipset in acer aspire one ( a new netbook) of atheros, madwifi just added it to their mainline
[10:31] <poningru> should I just bug someone to bring it into intrepid or should I package it up myself and offer it on my ppa or something?
[10:31] <poningru> same goes for a new realtek chipset though the rtl people have yet to add it to their mainline
[10:32] <poningru> both seem to be done correctly with ieee80211 drivers
[10:32] <poningru> I can post links if someone wants to take a look at them
[10:33] <bryce_> tjaalton: ok I filled mvo in; he may play with it anyway since there's interest
[10:35] <mvo> tjaalton: thanks for the info, I got a bunch of people asking me about this, so I would like to check it out
[10:35] <mvo> tjaalton: it seems like comment 9 in the 14... bugreport is promising
[10:37] <tjaalton> mvo: it's just a workaround and probably would affect other setups
[10:41] <tjaalton> gotta run again, but will get back later today ->
[10:41] <bryce_> cya tjaalton
[10:46] <bryce_> asac: http://releases.ubuntu.com/7.10/
[10:52] <Mirv> mvo: yep, the comment 9 works, but I'd be interested in hearing if there are any possible side effects from it or not. developers haven't commented on the bug since April, but maybe now that the 15xxx bug is fixed it'll get attention.
[10:53] <bryce_> mvo, Mirv, you might ping on that bug just in case
[10:56] <Mirv> bryce_: well it's mentioned as 7.1 blocker anyway, but I now pinged it by asking if anyone has information about possible side effects
[10:58] <bryce_> Mirv, excellent, thanks
[11:04] <bryce_> mdz: http://people.ubuntu.com/~bryce/Testing/xserver/
[11:08] <mvo> Mirv, bryce_: right, thanks
[11:08] <wgrant> Since there seem to be X folks around... is there a fix for Compiz+Intel == blinding yet?
[11:19] <jcristau> Mirv: the side effect is to break !i965, aiui...
[11:25] <norsetto> bryce: re. bug 248657, do you have any pointer on how I could patch the app to replace the obsoleted xrgb.txt?
[11:29] <pitti> thekorn: hm, I get "ImportError: cannot import name parse_error" from html_bug.py:17 ("from exceptions import parse_error")
[11:29] <pitti> thekorn: that doesn't work locally either
[11:29] <thekorn> pitti: och, which version of py-lp-bugs are you using?
[11:29] <pitti> thekorn: main head
[11:30] <pitti> -from launchpadbugs import parse_error
[11:30] <pitti> +from exceptions import parse_error
[11:31] <pitti> from rev 62.1.45
[11:31] <thekorn> phew,
[11:31] <pitti> thekorn: it seems you did some renaming there, and it conflicts with the standard exceptions module?
[11:33] <thekorn> pitti: I did some renaming, but I thought I fixed all issues,
[11:33] <thekorn> do you also have a package or something installed, so it conflicts there?
[11:33] <pitti> how do you mean?
[11:34] <thekorn> nevermind, I think I found the problem,
[11:35] <thekorn> let me have a closer look
[11:35] <emgent> moin
[11:41] <tseliot> ﻿pitti: I have adapted the debconf script to the new pattern in the modalias files (see revision ubuntu11 in my PPA). Just FYI
[11:43] <pitti> tseliot: nice!
[11:43] <pitti> tseliot: I still have a bunch of unreplied emails from you, sorry (conference...)
[11:44] <thekorn> pitti: hmm, sorry, I just don't understand the problem right now, can't even reproduce it,
[11:44] <hunger> pitti: I reported hal requireing /usr to be rw mounted as bug no. 248649.
[11:44] <thekorn> will have a closer look later today
[11:45] <tseliot> ﻿pitti: there's no hurry ;) I have yet to talk to mvo about the Update-Manager part
[11:45] <pitti> thekorn: I guess at some point it prefers the system "exceptions" module over the one in launchpadbugs/
[11:45] <pitti> brb
[11:45] <pitti> hunger: thanks
[11:46] <thekorn> pitti: right, I think the naming is bad here
[11:48] <norsetto> bryce: btw, I guess you may want to remove the /usr/share/X11/rgb.txt symlink too. Its dangling now.
[11:49] <emgent> heya tseliot :)
[11:49] <tseliot> hi emgent :-)
[11:51] <norsetto> asac: not to bee pushy, but the freeze for Debian is approaching
[11:55] <sebner> tseliot: ping
[11:55] <tseliot> ﻿sebner: hi
[11:56] <sebner> tseliot: buh a wonder that I meet you :D Sry, stupid question. Can you tell me what's the difference between nvidia-173 and -177? (though both aren't working xD)
[11:56] <tseliot> ﻿sebner: both of them work here. What card are you using?
[11:57] <sebner> bryce: Are you planning to merge freetype 2.3.7 from Debian?
[11:57] <sebner> tseliot: 8400GS
[11:57] <tseliot> ﻿sebner: seeing your /var/log/Xorg.0.log would help
[11:57] <sebner> tseliot: I think I once broke my system with coping nvidia files ^^ though the official driver is working. but what's the difference between these 2?
[11:58] <tseliot> ﻿sebner: the 173 is a legacy driver while 177 is the latest (experimental) driver which supports the latest (next-gen) cards.
[11:59] <sebner> tseliot: though experimental is still stable?
[11:59] <tseliot> ﻿sebner: make sure you uninstall the nvidia driver from the nvidia installer before you install my packages otherwise nothing will work. Furthermore they work only with 2.6.26 kernels
[12:00] <tseliot> ﻿sebner: experimental is experimental ;) I haven't had problems with it though
[12:01] <sebner> tseliot: yeah I know but as I said I think I broke the system with coping nvidia files around ^^ nvm. thanks for your answers. I'm off for 2 weeks so I'll look at that later (though I think a ubuntu reinstall will this that)
[12:01] <asac> norsetto: right. ping me on Thu please. i am currently into doing ffox security update. is that ok?
[12:01] <norsetto> asac: as long as we don't miss the deadline, it would a pity
[12:06] <asac> norsetto: when is freeze?
[12:15]  * calc is glad it only takes 1hr to rebuild OOo on his machine
[12:16] <calc> the cleanup i was doing turned up some other minor issues
[12:16] <calc> so have to rebuild it again
[12:23] <thekorn> pitti: FYI, just filed bug 248675
[12:23] <pitti>  thekorn: thanks, subscribing
[12:23] <thekorn> super
[12:30] <fabbione> 716922 build (dist-f10, devel:cluster-2_99_06-1_fc10) completed successfully
[12:30] <fabbione> ops
[12:30] <fabbione> sorry
[12:56] <pitti> fabbione: EDIST :)
[12:56] <pitti> fabbione: hey dude, how are you?
[12:58] <fabbione> pitti: ahha yeah .. ubuntu uploads are in the queue already :))
[12:58] <fabbione> pitti: all good thanks and you?
[12:58]  * doko waves to fabbione 
[12:58] <fabbione> hey doko
[12:59] <doko> fabbione: still doing sparc stuff?
[12:59] <pitti> fabbione: splendid! currently being in London again
[12:59] <fabbione> doko: not that much no... very little time atm
[12:59] <fabbione> pitti: oh great.. sprinting?
[12:59] <pitti> fabbione: indeed!
[13:00] <fabbione> i am actually hoping for somebody to take over my last 2 packages in ubuntu
[13:00] <fabbione> but i doubt somebody has the guts to maintain cluster stuff :)
[13:00] <thom> or the hardware ;)
[13:00] <fabbione> thom: 2 virtual machines aren't that expensive ;)
[13:05] <fabbione> doko: what are you looking for sparc?
[13:05] <thom> fabbione: where's the fun in that?
[13:06] <fabbione> thom: a lot more than you can think of :)
[13:06] <fabbione> thom: but you are spoiled by tons of server toys
[13:06] <fabbione> so you don't count! :P
[13:07] <doko> fabbione: building a biarch compiler defaulting to 32bit v9 by default. v9 is tightly coupled to 64bit ...
[13:07] <fabbione> doko: i guess that's based on davem patches to gcc, right?
[13:08] <fabbione> iirc he did some cleanup in that area not too long ago
[13:09] <doko> fabbione: yes, but --enable-targets=all --default-cpu=v9 still doesn't work.
[13:09] <fabbione> doko: bug worth reporting?
[13:11] <doko> yeah, maybe ... I'll have to check for one more thing before
[13:15] <norsetto> asac: looks like it is NOW: http://lists.debian.org/debian-devel-announce/2008/06/msg00000.html
[13:46] <jr_> siretart: another name change for ffmpeg?
[13:48] <Riddell> siretart: ah, we were insulting upstream
[13:49]  * calc wants one of the new (not yet released) quadcore centrino 2 laptops
[13:53] <bryce_> tjaalton: btw mvo says that the 14441 fix plus the newer mesa makes the issues resolve
[13:55] <asac> jcastro: https://wiki.ubuntu.com/NetworkManager/Hardware/3G
[13:55] <siretart> Riddell: yes, I gave a verbose explanation in README.Debian
[13:56] <siretart> Riddell: I wanted to delay that rename until after lenny release, but upstream pushed me
[13:56] <siretart> Riddell: if you accept it, could you please remove ffmpeg-free along with it? I'll file a bug otherwise..
[13:57] <norsetto> bryce_: what do you think about bug 248657 ?
[13:57] <Riddell> siretart: ok, can do
[13:59] <Riddell> siretart: done
[14:00] <jcristau> norsetto: add a local copy of rgb.txt in your source package?
[14:01] <norsetto> jcristau: already done, but I guess pixmap won't be the only one broken by this change?
[14:01] <bryce_> norsetto: hmm
[14:02] <bryce_> is it enough to have an empty /etc/X11/rgb.txt, or will apps expect valid data in it?
[14:02] <norsetto> jcristau: I think I was just luky that it ftbfs on the buildd because of it  ;-)
[14:02] <norsetto> bryce_: can't say for all the apps that use it, but pixmap really is using data from it
[14:04] <norsetto> bryce_: its an old file (from 2000) so I don't expect that the maintenace burden will be on us, is just to avoid breaking legacy apps which expect/use it
[14:07] <bryce_> well, I've no objection to including it.  jcristau?
[14:07] <jcristau> yeah i suppose it can come back
[14:08] <calc> ok OOo 2.4.1-6ubuntu1 is uploaded now, i guess i will look at mono since i didn't get a response from its last uploader
[14:08] <norsetto> bryce_: jcristau: thanks guys
[14:13] <siretart> Riddell: thanks!
[14:13] <mathiaz> slangasek: around for an openldap discussion ?
[14:15] <jcristau> norsetto: although really i don't think it's used that much..
[14:16] <slangasek> mathiaz: let me grab something to drink, then yes
[14:20] <TheMuso> Could anybody please have a look at this mdadm merge in my PPA? I'm not worried about the merge itself, but the error I get when test building. It seems like something that has been introduced in a recent gcc version, but I'm not sure how best to address it.
[14:20] <TheMuso> Package: http://ppa.launchpad.net/themuso/ubuntu/pool/main/m/mdadm/mdadm_2.6.7-3ubuntu1~ppa1.dsc - Build log: http://launchpadlibrarian.net/16035089/buildlog_ubuntu-intrepid-i386.mdadm_2.6.7-3ubuntu1%7Eppa1_FAILEDTOBUILD.txt.gz
[14:23] <sistpoty|work> TheMuso: looks like the fault of -D_FORTIFY_SOURCE
[14:25] <TheMuso> sistpoty|work: Ok, how does that affect the warning that is being treated as an error?
[14:26] <mathiaz> TheMuso: check out https://wiki.ubuntu.com/CompilerFlags
[14:26] <jcristau> TheMuso: that might add warnings, and you have -Werror in CFLAGS
[14:26] <sistpoty|work> TheMuso: it produces the warning in the first place
[14:27] <TheMuso> sistpoty|work: Right. mathiaz thanks, I'll take a look.
[14:28] <slangasek> mathiaz: hiyo
[14:29] <TheMuso> I guess my only concern is that the code is not written to use the asprintf function like it should, i.e a variable used to receive the return value. I guess it would be safer for upstream to correctly make use of this value returned from asprintf.
[14:29] <kirkland> doko: ping
[14:31] <doko> kirkland: contentless pong
[14:31] <norsetto> jcristau: I really wouldn't know, there are 162 depends of x11-common, many of those libraries
[14:31] <kirkland> doko: regarding bug #247400, you say "debian-security" ... did you mean "ubuntu-security" ?
[14:32] <doko> kirkland: yes, of course :-/
[14:33] <kirkland> doko: fyi, kees and pitti reviewed that setuid program extensively
[14:33] <kirkland> doko: kees said he'd add a comment as such, once I clarified that you meant "ubuntu-security" ;-)
[14:34] <sistpoty|work> TheMuso: I just took a glimpse at the code. looks safe to me, it will go wrong when out of memory (and then segfault0
[14:35] <TheMuso> sistpoty|work: Right, thats safe? :)
[14:35] <TheMuso> I would have thought not.
[14:37] <sistpoty|work> TheMuso: heh, I guess it's saner to do s.th. like "ret = asprintf(..); assert(ret >= 0);"
[14:38] <TheMuso> sistpoty|work: Hrm ok.
[14:45] <kees> kirkland: comment added :)
[15:02] <slangasek> TheMuso: yes, if you look at the manpage for asprintf, you'll see that the contents of the pointer asprintf() is supposed to fill on success are undefined in the event of a failure, so the only way to know whether asprintf failed is by checking the return value
[15:02] <TheMuso> slangasek: yeah I am aware of that. its just how to handle it sanely.
[15:03] <slangasek> TheMuso: right; sistpoty|work's solution is ok
[15:10] <TheMuso> ...and adding assert.h makes things blow up in more spectacular ways...
[15:10] <StevenK> TheMuso: "Feature"
[15:11] <TheMuso> StevenK: Oh yeah. ;)
[15:14] <sistpoty|work> TheMuso: how about if (ret < 0) { abort(); }?
[15:15] <TheMuso> sistpoty|work: Yeah I guess thats also an option. We'll see what happens this time.
[15:17] <bryce_> interesting article summarizing current state of X in intrepid - http://www.phoronix.com/scan.php?page=article&item=ubuntu_810_xorg&num=1
[15:22] <Hobbsee> bryce_: i look forward to having a working X to see it :)
[15:22] <bryce_> Hobbsee: how's your X broken?
[15:23] <Hobbsee> bryce_: after disabling usplash, i get a white screen after attmepting to log in.
[15:23] <bryce_> Hobbsee: ah, intel graphics
[15:23]  * Hobbsee hears something about logging in with metacity, instead of compiz, solving thep roblem.
[15:23] <bryce_> Hobbsee: mvo is uploading the mesa fix presently
[15:23] <Hobbsee> bryce_: yup
[15:23] <Hobbsee> \o/
[15:23] <Hobbsee> bryce_: how presently?
[15:23] <bryce_> Hobbsee: workaround is chmod a-x /usr/bin/compiz
[15:24] <TheMuso> sistpoty|work: Hrm it seems it has  more to do with the abort function causing errors than assert.h itself. I'll post a build log in a minute.
[15:24] <tseliot> ﻿bryce_: would disabling Composite in the xorg.conf help as a temporary fix?
[15:24] <Hobbsee> hm, it's fallen in depwait.
[15:24] <bryce_> Hobbsee: I wouldn't be surprised to see it uploaded today within a few hours.
[15:24] <bryce_> tseliot: that might do it too
[15:24] <Hobbsee> bryce_: 7.1~rc3-1~ppa1?
[15:25] <bryce_> Hobbsee: no, that was an accident
[15:25] <Hobbsee> ah
[15:25] <sistpoty|work> TheMuso: s.th. with "attribute noreturn" in it?
[15:25] <bryce_> Hobbsee: that one failed to build
[15:25] <TheMuso> sistpoty|work: Not sure, hang on.
[15:25] <Hobbsee> bryce_: it says it's in depwait.
[15:26] <Hobbsee> so it hasn't quite failed.
[15:26] <mvo> Hobbsee: please ignore it for now, I'm fixing it
[15:26] <mvo> (or better, I'm in the process of doing that :)
[15:26] <bryce_> right, raw mesa depends on something which is in universe for security reasons, so it'll never build
[15:27] <TheMuso> sistpoty|work: gah hang on, caused bya typo of all things. :)
[15:27] <sistpoty|work> heh
[15:28] <Hobbsee> mvo: by 'ignore', i've deprio'd them, so the buildds won't waste time on them
[15:28] <Hobbsee> at least, the ones taht hadn't had a shot at building
[15:28] <mvo> Hobbsee: aha, thanks for this!
[15:28] <Hobbsee> mvo: you're welcome
[15:29] <tseliot> Hobbsee: (if you want) you can add this to your xorg.conf as a temporary fix and try to restart the xserver: http://pastebin.com/m7927ff80
[15:30] <Hobbsee> tseliot: 'ive been on hardy for days - another one won't matter much.  but thanks :)
[15:30] <Hobbsee> besides, intrepid seems to hate my proxy, for some reason
[15:36] <TheMuso> sistpoty|work: Ok, typos fixed, assert works as expected, on my way. Thanks a bunch.,
[15:36] <sistpoty|work> TheMuso: you're welcome
[15:39] <pitti> seb128: /etc/X11/Xsession.d/90-console-kit
[16:10] <rick_h_> asac: ping, jorge wanted me NM testing asap and get the following: http://paste2.org/p/48932
[16:13] <asac> rick_h_: are there two wpa_supplicant processes running?
[16:14] <rick_h_> asac: no, only one pulls up
[16:14] <rick_h_> /sbin/wpa_supplicant -u -f /var/log/wpa_supplicant.log
[16:14] <asac> rick_h_: ok.
[16:14] <asac> intrepid or hardy?
[16:14] <rick_h_> hardy
[16:23] <hungerTest> pitti: I worked around the "/usr must be rw for hal" issue I reported in LP #248649 and added a note on what I did. Maybe that helps with fixing the issue.
[16:37] <pitti> hungerTest: thanks
[16:39] <pitti> hungerTest: I just wonder why that actually fails... rm -f should just ignore it
[16:40] <pitti> but apparently it doesn't
[16:41] <pitti> hungerTest: fixed in trunk, thanks
[16:44] <mdz> bryce: is xresprobe obsolete?
[16:49] <Riddell> tjaalton: ping
[16:50] <Riddell> tjaalton: I've synced everything in bug 247556, can you close all the entries please
[16:50] <pitti> Riddell: syncbugbot should do that; are you using that?
[16:52] <Riddell> pitti: I am not, where do I find it?
[16:52] <pitti> Riddell: ~lp_archive/bin
[16:52] <pitti> Riddell: where are you, I'll show you
[16:54] <cjwatson> Riddell: will KDE display notes dropped into /var/lib/update-notifier/user.d/ in the usual way?
[16:55] <cjwatson> Riddell: ah - Arne tells me that Command: isn't supported?
[16:56] <Riddell> pitti: south side
[17:00] <calc> http://www.engadget.com/2008/07/14/build-your-own-bluetooth-handgun-handset-or-dont/
[17:05] <Riddell> cjwatson: no I don't think we implemented that, although we did do the reboot notification
[17:06] <cjwatson> Riddell: it'd be awfully useful for bug 9392
[17:07] <Riddell> cjwatson: it wouldn't be hard to do and ought to have been done a while ago
[17:07] <calc> once a package is 'DONE' it is available for buildds to use, right?
[17:10] <cjwatson> Riddell: is there a bug to track it?
[17:10] <cjwatson> calc: not quite
[17:10] <slangasek> Mithrandir: you don't want to fix Debian bug #398610 by any chance, do you? :)
[17:10] <cjwatson> calc: DONE means (at least) that process-accepted has munched it and that the publisher is about to write it out to disk
[17:11] <cjwatson> calc: but until it's been written out to disk and Packages regenerated, buildds won't see it
[17:11] <cjwatson> calc: buildds *can* see it a little before archive.ubuntu.com gets updated, though
[17:11] <cjwatson> (which in practice means that they don't have to wait for cron.germinate)
[17:13] <calc> cjwatson: is there an easy way to tell when it is safe to use, or just look at a.u.c to find out?
[17:17] <bryce_> ogasawara: I'm bumping 154647 over to 'linux' since it is sounding like a kernel / wireless driver issue, rather than an -intel issue.  It's an old bug, but please take a look when you get a chance
[17:18] <Riddell> cjwatson: bug 248753
[17:18] <cjwatson> calc: the latter
[17:18] <ogasawara> bryce_: sure
[17:18] <cjwatson> Riddell: thanks
[17:27] <calc> cjwatson: ok
[17:27] <calc> cjwatson: how often (or lag) do things go from done to the archive?
[17:27] <bddebian> mvo: You around by any chance? (about gdebi)
[17:28] <mvo> bddebian: yes (but a bit busy)
[17:28] <bddebian> mvo: Just curious if you intend to put 0.3.11 in Debian?
[17:29] <mvo> bdmurray: I do not maintain it in debian, I would be interessted in someone taking care of it there, if I can not find someone, I may do it myself
[17:29] <tjaalton> Riddell: excellent, will do
[17:30] <bddebian> mvo: Amaya has asked me to look at it for Debian but there are so many hands in it I'm a bit confused on which way to go.
[17:31] <bddebian> Maybe lool is a better person to bug? :)
[17:31] <cjwatson> calc: hourly
[17:31] <calc> cjwatson: ok
[17:31] <cjwatson> calc: the publisher starts at :03
[17:31] <cjwatson> it does take most of the hour to run though :-(
[17:32] <calc> oh btw lenovo announced their new thinkpad line recently
[17:32] <calc> cjwatson: ok
[17:32] <calc> the X200 looks pretty nice and is relatively cheap (compared to the X300 anyway)
[17:32] <mvo> bddebian: if you have any specific questions, I'm happy to help, but it should be possible to use it pretty much unmodified on debian
[17:34] <bddebian> mvo: Well it's more about deltas.  There is an added Turkish translation and she wants me to remove the -kde package :-(
[17:37] <mvo> bddebian: oh? why removing the kde package?
[17:38] <bddebian> mvo: Well there are some LP bugs about it but apparently theres an Ubuntu patch for KDE that isn't in Debian so it doesn't work?
[17:38] <subzero__> ciao raga
[17:38] <subzero__> qualcuno conosce le qt?
[17:39] <subzero__> ce nessunoooooooooooo?
[17:40] <mvo> bddebian: hm, there is a patch for konsole that is required for it to work correctly. we could do it in a different way, but that is not available yet
[17:42] <mdz> asac: did you get vmware-server working?
[17:43] <bddebian> mvo: Is anyone actively developing/maintaining it? I only ask because of LP #153943
[17:47] <asac> mdz: unfortunately not. did you get the error mail?
[17:48] <mdz> asac: no..
[17:49] <asac> urgh
[17:50] <asac> mdz: its sent according to my mailer ... anyway: http://paste.ubuntu.com/27512/
[17:50] <asac> mdz: if you have an idea which old lib might provide it I would give it a try
[17:54] <mdz> asac: try moving /usr/lib/vmware-server/lib/libgcc_s.so.1 out of the way
[17:55] <doko> mdz: is this in the partner archive?
[17:55] <asac> doko: yeah
[17:55] <asac> gutsy
[17:55] <asac> doko: i try to install that in hardy ;)
[17:56] <asac> doko: http://archive.canonical.com/pool/partner/v/vmware-server/vmware-server_1.0.4-1gutsy2_i386.deb
[17:57] <mdz> doko: yes
[17:57] <doko> asac, mdz: not the first time I do see this. can we disable / fix this for hardy/intrepid?
[17:58] <asac> doko: there is no hardy package available :(
[17:58] <asac> mdz: is anyone working on that?
[18:00] <mdz> ogra: what does ltsp-client-core use xresprobe for?
[18:00] <mdz> doko: the package is only in gutsy, and it presumably works there
[18:00] <mdz> doko: it just doesn't seem to work on hardy for asac (it worked for me)
[18:01] <mdz> asac: I do not think anyone is working on a hardy package; partner packages are very inconsistently updated
[18:01] <ogra> mdz, nothing anymore debian uses it for xdebconfigurator
[18:01] <mdz> ogra: can you remove the dependency?
[18:01] <ogra> mdz, if you want it gone, i can drop it
[18:02] <ogra> sure
[18:02] <mdz> ogra: it should move to universe
[18:02] <ogra> goo, i'll remove it in the next upload, how urgent is that ?
[18:02] <ogra> *good even
[18:02] <mdz> ogra: not urgent at all
[18:02] <mdz> ogra: I just noticed it was still in main despite being removed from the seeds in hardy, and noticed it's due to ltsp-client-core
[18:02] <ogra> oki, i'm at the ltsp hackfest next week, so i'll have an upload pending then anyway
[18:03] <ogra> removed in my bzr tree ...
[18:03] <laga> ogra: ah, then you'll get a patch from me, too..
[18:03] <ogra> laga, feel free :)
[18:05] <asac> mdz: ok. moving this away indeed helps. great. (except that i am left with a forced depends state, but i can deal with that)
[18:06] <asac> mdz: will use it tomorrow for final QA then. thanks
[18:08] <asac> hmm ... unfortunately i cannot start a VM ... it gives me "end of error message" - how helpful.
[18:31] <mdz> asac: maybe the server side is broken; I didn't test starting a VM
[18:32] <mdz> asac: you can ssh in using the same username and password and sudo
[18:32] <mdz> asac: but maybe it is not worth your trouble at this point
[18:34] <geser> Riddell: re bug #247630 and bug #247712: did you perhaps need a extra flag to overwrite the ubuntu changes?
[18:34] <asac> mdz: most likely not. ill try to workaround somehow. if you find a spare machine in the office i would be greatful ;)
[18:34] <pitti> geser: can you please reopen the bugs?
[18:34] <geser> sure
[18:34] <mdz> asac: you are welcome to butcher norman.local
[18:34] <asac> ;)
[18:34] <mdz> asac: but I don't have a spare monitor for it
[18:35] <mdz> asac: just preserve /var/lib/vmware-server
[18:35] <asac> mdz: ok. ill see how much feedback i got on QA this night and do that tomorrow
[19:43] <Mithrandir> slangasek: sure, I can do that.
[19:48] <slytherin> Riddell: FYI ... Changes in Ubuntu for statcvs can be dropped. geser has already verified it.
[21:20] <philsf> is there a way, when installing/removing lots of kernel images, to update-grub only once, after all packages are processed?
[21:21] <philsf> or, perhaps the question is: should there be a way (or is it some sort of policy)?
[22:24] <calc> my wife managed to turn off the breaker to my computer, lol
[22:25] <norsetto> calc: its a good excuse to ask her about that new UPS you have been dreaming about
[22:29] <calc> norsetto: i have an ups just too lazy (really forgetful) to buy a new battery for it
[22:29] <calc> OOo 1:2.4.1-6ubuntu1 built on amd64/i386/lpia so far
[23:38] <MTecknology> hi buddies
[23:38] <MTecknology> somebody wanna help me out with something?.....
[23:39] <Lynet> Multiboot hardy install dvd, how to make?
[23:40] <MTecknology> Lynet, pretty much
[23:40] <MTecknology> Lynet, you already ask about it?
[23:40] <Lynet> I'm asking now. ;-p
[23:41] <MTecknology> o
[23:44] <MTecknology> I have ubuntu iso's put into a cdshell iso. I can use "diskemu ubuntu.iso" to launch the iso. It looks like it's going to work ok, but then this happens. http://img135.imageshack.us/my.php?image=screenshottestrunningviav2.png  I think what I need to do is make ubuntu look at the iso of itself instead of the cd drive itself.
[23:44] <MTecknology> any ideas for how to do that?
[23:47] <Lynet> I suspect it would be fairly straight forward if one could tell isoinux to read an alternate lisolinux.cfg, would just require a .cfg to select which 'cd' to use and then change the initrd for each dvd to tell the installer to look in a directory instead of the dvd root.
[23:48] <Lynet> But isolinux does not support that, afacit.
[23:48] <MTecknology> afacit??
[23:51] <MTecknology> http://ubuntuforums.org/showthread.php?t=73384