[12:03] <Keybuk> ok, how does one install mozilla extensions ?!
[12:04] <hub_> I don't find Colony
[12:04] <hub_> am I blind ?
[12:06] <hub_> found it
[12:06] <hub_> Amaranth: given the time, it won't be mailed before monday
[12:08] <Amaranth> hub_: i don't need it anymore, thanks anyway
[12:09] <hub_> Amaranth: okay. good
[12:09] <Amaranth> i called someone, they'll have it to me on sunday
[12:09] <Amaranth> i just hope i don't lose /home
[12:09] <Amaranth> i don't have another copy of smeg 0.8 anywhere
[12:09] <hub_> :-/
[12:10] <Amaranth> oh shit, i don't have another copy of my work on pymusique anywhere either
[12:10] <Amaranth> jlje reminded me :/
[12:12] <xhaker> i was going to make room to install in another partition hoary server install
[12:13] <xhaker> i'm starting to think i will b0rk my stuff
[12:14] <xhaker> i did it once and Amaranth is not really helping
[12:14] <xhaker> lol
[12:14] <Amaranth> heh
[12:14] <Amaranth> if it works again
[02:49] <Gnobody> hey
[02:50] <Gnobody> is X *still* broken?
[02:52] <lamont-away> Gnobody: you have reminded me of one of my favorite answers
[02:52] <lamont> "yes, signals are broken.  But not that way."
[02:52] <lamont> I think it generally applies to X as well.
[02:52] <Gnobody> damn
[02:52] <lamont> as for whether or not X is sane again, I couldn't say.  But that's a #ubuntu question
[04:01] <daniels> doko: nope
[04:02] <daniels> errr
[04:02] <daniels> infinity: libxt b-ds on libsm >= 1:6.0.4-2, and -3 is in the archive
[04:30] <daniels> infinity: right, I see what happened now.
[04:46] <CarlFK> hey daniels
[04:46] <CarlFK> you do anything with preseed files?
[04:51] <daniels> CarlFK: nope, sorry
[04:56] <CarlFK> no prob
[05:33] <zwnj> where i can find a package building (from scratch) manual from?
[05:33] <bddebian> zwnj: The Debian New Maintainers Guide
[05:33] <zwnj> seems building debian packages is harder that rpm
[05:33] <bddebian> Nah
[05:33] <zwnj> bddebian: thanks :)
[05:34] <bddebian> Anyone know what is up with debdiff all of the sudden???
[06:17] <fabbione> mornign
[06:19] <bddebian> Morning fabbione
[06:34] <trulux> heya guys
[06:35] <trulux> fabbione: morning
[06:35] <bddebian> Hello trulux
[06:38] <trulux> bddebian: hi :)
[06:39] <trulux> anyone knows the time when Jane joins the channel?
[06:39] <bddebian> Not me sorry
[06:39] <Burgundavia> trulux, she is UTC or UTC+1
[06:41] <trulux> Burgundavia: many thanks, I just need to show some more stuff to pitti and her
[07:30] <davyd> daniels: not to sound like a naggy mc nag nag, but what is holding linux-restricted-modules back?
[07:31] <fabbione> davyd: a few things..
[07:31] <fabbione> it will be around soon again
[07:31] <fabbione> 2.6.12 prior the last upload was not exactly stable
[07:32] <fabbione> and adding more instability due to binary driver was going to be only an extra mess for me to get stuff fixed
[07:33] <davyd> so -4 is the go?
[07:34] <fabbione> davyd: it did close a lot of bug...
[07:34] <davyd> rock and roll
[07:34] <davyd> does it look like the home stretch now?
[07:34] <fabbione> i might have to break it again to get some ipw2x00 extra love, but i can do it outside the archive to test
[07:34] <davyd> or is there a heck of a lot of work remaining?
[07:35] <fabbione> it's half way
[07:35] <fabbione> in theory there is a lot of packaging work
[07:35] <fabbione> but the code seems to be pretty stable
[07:35] <fabbione> and in the beginning i had to focus on that
[07:35] <fabbione> (reason why l-r-m isn't around yet)
[07:36] <fabbione> + we had slightly less time than usual to work on l-r-m due to C++ and X transitions all together
[07:36] <fabbione> that clearly are higher priority
[07:36] <fabbione> (if X doesn't work.. you can play pingpong with l-r-m ;))
[07:45] <daniels> yeah, it's just been full-on, and l-r-m hasn't been on my radar due to not being 'urgent holy shit needed last week'
[07:48] <davyd> I don't mind rebuilding the nvidia packages as required, I was mostly wondering if it was a time problem or a technical problem
[07:48] <davyd> I get the impression it's been a time problem
[07:48] <davyd> incidently, "libsexy" now has a spellchecking entry widget
[07:48] <davyd> I wonder how that would look in X-Chat
[07:51] <fabbione> davyd: it's both actually..
[07:51] <fabbione> because X is removing /usr/X11R6
[07:51] <fabbione> or anyway killing part of it
[07:51] <fabbione> that reflects on nvidia and ATI too
[07:52] <fabbione> the gcc transition made impossible to build them
[07:52] <fabbione> + the time
[07:52] <davyd> ok, I didn't notice that compiling nvidia-glx, but ok
[07:52] <davyd> is it going to break with -43?
[07:52] <fabbione> but given that main needs to be stabilized first to build l-r-m properly...
[07:52] <fabbione> i dunno...
[07:52] <fabbione> i didn't upgrade X for a while
[07:52] <davyd> I guess I'll find out the hard way
[07:52] <fabbione> (btw i do compile nvidia myself too...)
[07:53] <fabbione> but to have a stable desktop to work on the kernel i had to stop upgrading X
[07:53] <fabbione> so i dunno
[08:00] <davyd> I picked the wrong day originally to install breezy on my new machine
[08:01] <davyd> and it took until X -43 to get Xv working on my laptop
[08:01] <daniels> well, to be fair, that bug was present in warty and hoary also
[08:01] <davyd> yes
[08:02] <davyd> but that's why I took to upgrading X
[08:03] <daniels> lamont: ... which headers disappeared from dbus, exactly?
[08:06] <lamont> daniels: <sys/signal.h>
[08:06] <lamont> fd_set et al
[08:06] <lamont> pretty sure I called it dbus-signal.patch
[08:07] <lamont> and -ubuntu6 had the arch spec on mono-mcs
[08:08] <daniels> so you added some missing #includes
[08:14] <lamont> I added one missing include
[08:14] <lamont> and all was right with the world again
[08:15] <lamont> clearly it included something that _used_to_ include sys/signal.h
[08:20] <lamont> http://people.ubuntu.com/~lamont/buildLogs/Test/byDate/today.html
[08:20] <lamont> enjoy the pain that is breezy-autotest, folks
[08:21] <lamont>  interesting, amd64 is kicking butt
[08:22] <daniels> heh
[08:24] <lamont> buildLogs/Test/Lists/breezy-autotest.all.amd64:Total 159 package(s) in state Installed.
[08:24] <lamont> buildLogs/Test/Lists/breezy-autotest.all.i386:Total 97 package(s) in state Installed.
[08:24] <lamont> buildLogs/Test/Lists/breezy-autotest.all.ia64:Total 53 package(s) in state Installed.
[08:24] <lamont> buildLogs/Test/Lists/breezy-autotest.all.powerpc:Total 96 package(s) in state Installed.
[08:24] <lamont> hrm... maybe that was semi-spewage
[08:25] <fabbione> does the latest kdelibs fix the uninstallable problem?
[08:25] <fabbione> or do we need to do some kind of magic?
[08:25] <lamont> still no clue... dbus was blocking kdelibs for me
[08:25] <lamont> but that's built now.  cool
[08:26] <fabbione> it's the other way around for me..
[08:26] <fabbione> dbus can't build because of kdelibs..
[08:26] <daniels> fabbione: yeah, you need to break the loop there
[08:26] <fabbione> daniels: how?
[08:26] <bob2> autotest = randomly rebuild already built source packages?
[08:26] <fabbione> daniels: or better.. in what order?
[08:27] <lamont> bob2: use the debs from breezy, and a snapshot of the source from same.  build, and then throw away (well, notreally, but effectively) the resulting debs
[08:27] <bob2> ah, neat
[08:27] <daniels> fabbione: i assume disable dbus support in kdelibs, build dbus off that, and rebuild kdelibs off dbus
[08:27] <daniels> that's if you're bootstrapping
[08:27] <lamont> daniels: or find an older, installable kdelibs
[08:27] <daniels> right
[08:27] <fabbione> hmmmm
[08:27] <fabbione> ok
[08:28] <fabbione> giving the morgue is broken, it's going to be difficult
[08:28] <lamont> my issue right now is that it still isn't installable, since libopenexr-dev isn't available from breezy
[08:29] <lamont> daniels: anything wrong with this list for an xorg-split kind of world??  autotools-dev cdbs debhelper libfltk1.1-dev xlibmesa-gl-dev xlibmesa-glu-dev
[08:30] <daniels> lamont: xlibmesa-gl-dev | libgl-dev, libglu1-xorg-dev | libglu-dev
[08:31] <lamont> ok
[08:31] <lamont> that's openexr, fwiw
[08:31] <daniels> must, must provide alternatives
[08:32] <fabbione> night lamont
[08:33] <daniels> night dude
[08:34] <lamont> daniels: and feel free to look at all the missing X* symbols in imlib2 if you're really looking for something to distract you from xorg proper. :)
[08:35] <daniels> ot
[08:35] <daniels> er
[08:35] <daniels> it's saturday
[08:36] <daniels> lamont: example build log though?
[08:57] <fabbione>
[10:53] <herve> hello
[10:54] <herve> who can I see for bugzilla rights?
[02:29] <Mithrandir> is the morgue broken?
[02:30] <fabbione> Mithrandir: yes.
[02:30] <fabbione> i told elmo already
[02:31] <highvoltage> the morgue?
[02:31] <fabbione> Mithrandir: are you going to be around monday?
[02:31] <Nafallo> highvoltage: morgue.ubuntu.com
[02:32] <Mithrandir> fabbione: sure
[02:33] <fabbione> Mithrandir: we need to talk about Xen, but not now. i am moving al the stuff around the office today and reconfiguring tomorrow
[02:33] <fabbione> Mithrandir: i am on a 80x24 12" monitor atm :)
[02:33] <fabbione> and can't really do much
[02:33] <Mithrandir> fabbione: heh, ok.
[02:34] <fabbione> ok.. i am offline again.. time to switch my ws to 3x21" :)
[02:34] <fabbione> i wonder what resolution can handle the Sun monitor...
[02:37] <siretart> I'd like to have piuparts from unstable included in ubuntu. it seems useful for doing qa of packages. who do I need to ask?
[02:37] <siretart> in universe, that is
[02:38] <ogra> Mithrandir, there obviously is no limit on 65000 files in a ext3 directory ;)
[02:38] <ogra> Mithrandir, (as you told me)
[02:38] <ogra> see http://hwdb.ubuntu.com/
[02:41] <tseng> siretart: email elmo to sync it
[02:41] <tseng> it would be nice if pbuilder could do the same things
[02:41] <tseng> or piuparts use the pbuilder chroot
[02:41] <bob2> (sbuild)
[02:42] <Mithrandir> heh:
[02:42] <Mithrandir> find: WARNING: Hard link count is wrong for .: this may be a bug in your filesystem driver.  Automatically turning on find's -noleaf option.  Earlier results may have failed to include directories that should have been searched.
[02:42] <seb128> hi
[02:42] <seb128> daniels: around?
[02:43] <siretart> tseng: piuparts can use the base.tgz of pbuilder
[02:43] <Mithrandir> ogra: sorry, 32k directories. :-)
[02:43] <tseng> siretart: rock.
[02:43] <Mithrandir> ogra: try seq 40000 | xargs mkdir
[02:44] <bob2> seb128: ELATEONASATURDAYNIGHT
[02:44] <bob2> hah, nice that find can work around some disk corruption
[02:44] <seb128> bob2: just trying to make sure to not conflict with his uploads before upload a xft to drop XOPEN_SOURCE from here
[02:44] <seb128> bob2: if he's away that's fine :)
[02:45] <ogra> Mithrandir, seriously i wont try it on *this* PII 233 ;)
[02:45] <bob2> ah :)
[02:45] <Mithrandir> ogra: get a real computer. ;-)
[02:45] <ogra> Mithrandir, thats a *server* *g*
[02:46] <ogra> Mithrandir, but once i mived all this crap to the DC i'll upgrade the machine ;)
[02:46] <ogra> moved even
[02:46] <Mithrandir> ogra:  :-)
[02:46] <ogra> opteron !
[02:47] <thom> tseng: dude, beagle appears to ftbfs here...
[02:49] <Amaranth> thom: libgmime-cil is out of sync with the thing it's binding
[02:49] <tseng> yes
[02:50] <tseng> gmime 2.1 is a hard dep for 0.12
[02:50] <tseng> 0.12 is not uploaded because it does nothing but explode here
[02:50] <tseng> stay tuned
[02:51] <tseng> thom: want to look at blam/mozilla bug?
[02:51] <thom> tseng: not really :-)
[02:52] <tseng> meh
[02:52] <tseng> sounds like we are at a stand-off
[02:53] <Amaranth> If my HD worked I'd look at blam :)
[02:53] <Amaranth> If grub spits out Error 17 when it's supposed to load the menu of choices it can't read /boot, right?
[02:55] <tseng> can anyone tell me why mono isnt building
[02:57] <slomo> fabbione: will the kernel be built with gcc 3.4 until breezy release?
[02:58] <fabbione> slomo: probably
[02:59] <slomo> fabbione: ok, thanks
[03:25] <bddebian> Morning
[03:32] <highvoltage> morning, bddebian
[03:32] <highvoltage> (or good afternoon, from my timezone)
[03:37] <bddebian> Heya highvoltage
[04:02] <highvoltage> bddebian: do you think canonical/ubuntu will support the hurd kernel and release a ubuntu gnu/hurd, once it hits v1.0?
[04:02] <thom> i doubt canonical will, but ubuntu might if there's community interest
[04:02] <infinity> seb128 : Looks like XOPEN_SOURCE still hasn't been completely purged from the X dependency chain, so you should probably stop uploading things to "fix" it...
[04:03] <seb128> infinity: hum? what package has been b0rked?
[04:03] <HrdwrBoB> not sure there will be interest though
[04:03] <seb128> infinity: xft?
[04:03] <infinity> seb128 : pango still has it in its .pc file.
[04:03] <seb128> infinity: yeah, due to xft
[04:03] <seb128> infinity: that's why I've uploaded xft ... should be fine now
[04:04] <seb128> then I can upload gtk
[04:04] <seb128> then I can work :p
[04:04] <infinity> seb128 : Ahh.  Hrm.  Kay.  Of course, several X libs here still show it as well (sm, xmu, xt, xtrap)
[04:04] <seb128> infinity: pango don't use those
[04:04] <infinity> Heh.  Kay. :)
[04:04] <bddebian> highvoltage: I doubt it but I am working on creating an Ubutnu Hurd derivative
[04:04] <infinity> So, xft, pango, gtk, gdk, PROFIT?
[04:05] <highvoltage> bddebian: ah, that will be nice (at least for testing)
[04:05] <seb128> infinity: that's the plan :)
[04:05] <infinity> And I can sort out the rest of the X libs that still look goofy later.
[04:05] <azeem> bddebian: cool, send me the gcc-4.0 fixes if you do so, then :)
[04:05] <infinity> seb128 : Once you've done those uploads, are we ready for me to do a mass give-back to the buildds again, and see what blows up?
[04:05] <seb128> infinity: do you know how is xorg/xkb nowadays?
[04:05] <seb128> infinity: I still have -33 here
[04:05] <bddebian> Hey any chance one of you "main" types can sync devscripts from Debian unstable?  It's broken in breezy atm
[04:06] <seb128> infinity: yeah
[04:06] <infinity> seb128 : Not sure, I run X in hoary still, my breezy stuff is all chrooted.  Probably should switch this month, though.
[04:06] <infinity> bddebian : Yeah, I was goign to request that sync once the Debian uploads settled down a bit (there've been a few in a row)
[04:06] <tseng> infinity: could you perhaps tell me why mono isnt building?
[04:06] <infinity> bddebian : I assume it's the breakage of "debdiff" you want fixed (same as me)?
[04:06] <bddebian> infinity: Ah, OK, thx
[04:07] <bddebian> infinity: Yes, debdiff :-)
[04:07] <tseng> infinity: or, seeming hasnt entered buildd more specifically
[04:07] <infinity> tseng : Specific package(s)?
[04:07] <tseng> infinity: mono <IP_ADDRESS>
[04:08] <infinity> tseng : dep-wait on mono-classlib-1.0... I assume this is incorrect? :)
[04:08] <tseng> infinity: yes, that must be from my previous upload
[04:08] <tseng> infinity: we managed to get it bootstraping internally
[04:09] <infinity> tseng : Freed up, shold build shortly.
[04:10] <infinity> should, too.
[04:10] <tseng> infinity: cheers
[04:16] <tseng> mdke: you should be able to access my server on port 22 now
[04:30] <infinity> tseng : Built.
[04:31] <mdke> tseng, ah cool, i was just uploading now :D
[04:31] <mdke> tseng, btw we have a docteam linode set up now so as soon as we have a subdomain pointing at it, i'll let you know and you can close our account on your server
[04:32] <tseng> mdke: ok, rock on
[04:32] <tseng> infinity: thanks dude
[04:33] <tseng> wth
[04:33] <Nafallo> http://www.magicalforest.se/tmp/libxaw_7.0.2-3.diff
[04:34] <tseng> infinity: if you still have a few moments, could you look at that buildlog
[04:34] <tseng> infinity: apt cache troubles
[04:35] <Nafallo> builds cleanly on amd64 and should fix xkbutils ftbfs
[04:35] <Nafallo> :-)
[04:36] <herve> Nafallo, my hero!
[04:36] <hunger> Is xkb broken again?
[04:36] <bob2> yup
[04:36] <hunger> bob2 What is the workaround this time?
[04:37] <bob2> I dunno if there is one
[04:37] <Nafallo> hunger: to dep-wait on xkb-utils :-)
[04:37] <bob2> my work around was "not upgrade until breezy went a week without being fucked"
[04:37] <hunger> breezy is basically unusable most of the time:-(
[04:38] <Nafallo> bob2: what's the fun in that? ;-)
[04:38] <tseng> funny that ive been using it the entire time
[04:38] <hunger> bob2: Can't do that... I need the new kernel.
[04:38] <fabbione> is there some known problem with udev?
[04:39] <bob2> tseng: proof that I'm lazier than you
[04:39] <fabbione> bob2: ^^
[04:39] <hunger> bob2: Actually rebuilding the kernel a couple of times would have saved lots of time.
[04:39] <fabbione> it seems that it doesn't start here at all..
[04:39] <hunger> fabbione: Yeap. It does not create /dev/input/mice for me anymore.
[04:39] <fabbione> hunger: exactly...
[04:39] <fabbione> and /dev/input/mice
[04:39] <hunger> fabbione: run udevstart manually and it will be there.
[04:40] <herve> ha, that's why my usb mouse stopped to work some times
[04:40] <herve> I unplugged and replugged it and it was ok
[04:40] <fabbione> hmm
[04:40] <fabbione> no
[04:40] <fabbione> no luck
[04:41] <herve> or maybe that was a X issue
[04:41] <hunger> fabbione: I talked to someone here about that two weeks ago... said it worked for him and that I should debug myself.
[04:42] <Nafallo> dang. does not fix xkbutils *goes back to hack on it*.
[04:42] <fabbione> it's definetely a udev problem
[04:43] <hunger> Any change of getting a xkb fixed soonish? And a "startx" would be nice to have at some point, too;-)
[04:43] <bob2> X will be fixed in the next few days, hopefully
[04:43] <hunger> fabbione: Yeap, that was what we found out 2 weeks ago, too:-)
[04:43] <Nafallo> hunger: installed xinit?
[04:44] <fabbione> mousedev is not modprobed.. so it could either be udev or hotplug
[04:44] <fabbione> if i modprobe that manually.. everything works
[04:44] <hunger> Nafallo: There is no xinit... startx used to be part of xbase-clients, but that is basically empty nowadays.
[04:45] <Nafallo> hmm, xinit has to be NEWed ;-)
[04:45] <Nafallo> hunger: yea, daniels is spliting it.
[04:45] <ogra> hunger, xbase-clients is split
[04:45] <hunger> fabbione: mousedev is loaded here... I do have /dev/input/mouse*, but no /dev/input/mice.
[04:45] <ogra> hunger, it will disappear completely or get converted to as metapackage eventually
[04:46] <ogra> s/as/a
[04:46] <hunger> ogra: Thanks for the info!
[05:17] <infinity> tseng : Which build log?
[05:22] <ogra> hmm, #12888 is a very interesting big
[05:22] <ogra> bug
[05:24] <lamont> buildLogs/Test/Lists/breezy-autotest.all.amd64:Total 729 package(s) in state Building.
[05:24] <lamont> buildLogs/Test/Lists/breezy-autotest.all.amd64:Total 138 package(s) in state Dep-Wait.
[05:24] <lamont> buildLogs/Test/Lists/breezy-autotest.all.amd64:Total 1 package(s) in state Failed.
[05:24] <lamont> buildLogs/Test/Lists/breezy-autotest.all.amd64:Total 618 package(s) in state Installed.
[05:24] <lamont> buildLogs/Test/Lists/breezy-autotest.all.amd64:Total 13 package(s) in state Uploaded.
[05:24] <lamont> buildLogs/Test/Lists/breezy-autotest.all.amd64:Total 1499 package(s)
[05:24] <lamont> oops.
[05:24] <lamont> anyway, it's < 50% of main that has actual build failures on amd64...
[05:25] <tseng> infinity: it worked itself out
[05:25] <lamont> and < 10% that are missing build-depends
[05:25] <ogra> sounds good..
[05:25] <ogra> how is this compared to the other arches ?
[05:32] <Nafallo> ogra: care for a couple of uploads to main? ;-)
[05:33] <ogra> Nafallo, not now... i'm currently busy with other stuff... can you send me a list ?
[05:34] <{Seb}> how is Xorg looking in Breezy?
[05:34] <{Seb}> Broken?
[05:34] <hunger> sebest: yes.
[05:34] <Nafallo> ogra: sure, either that or I nag Tollef after dinner :-).
[05:35] <ogra> Nafallo, youre already there ?
[05:35] <Nafallo> I shall probably test the packages first :-)
[05:35] <ogra> Nafallo, great idea ;)
[05:35] <Nafallo> ogra: yepp, since yesterday evening  :-)
[05:35] <ogra> nice :)
[05:36] <Nafallo> he's hacking dinner, while I'm hacking Xorg ;-)
[05:36] <{Seb}> Nafallo: can you tell me if there are any outstanding issues with Xorg?
[05:36] <HiddenWolf> I'd rather do dinner, really
[05:37] <Nafallo> Seb: xkb is broken.
[05:37] <Nafallo> Seb: hopefully not long though ;-)
[05:37] <{Seb}> when i'm upgrading - what do i need to be careful of then?
[05:37] <{Seb}> upgrading from Colony 2 install i mean
[05:38] <Nafallo> xorg
[05:38] <{Seb}> i guessed that :-)
[05:38] <{Seb}> i mean which packages are broken?
[05:39] <HiddenWolf> seb128, he said, xkb
[05:39] <{Seb}> Nafallo: how do you mean xkb is broken?
[05:40] <Nafallo> Seb: keyboard doesn't work?
[05:40] <HiddenWolf> seb128, I'd imagine it doesn't work without user-side hacking
[05:40] <{Seb}> dang
[05:41] <{Seb}> Nafallo: will Xorg -44 sort it>
[05:41] <{Seb}> *it?
[05:41] <davyd> /set completion_amount 0
[05:41] <Nafallo> yay! keyboard works again :-)
[05:41] <Nafallo> Seb: dunno, ask daniels :-)
[05:42] <Nafallo> daniels /away socializing
[05:42] <davyd> HiddenWolf: assuming you're talking about broken X-chat completion, that was for you
[05:42] <davyd> the option is persistant, and will switch back to the old "readline" style completion
[05:42] <Nafallo> hmm, gone :-)
[05:42] <HiddenWolf> davyd, yeah, xchat seems to autocomplete sometimes without my pressing <tab>
[05:42] <hunger> Nafallo: What do I need to do to get it working here, too?
[05:42] <davyd> HiddenWolf: you may have an autocompletion character set
[05:43] <HiddenWolf> davyd, in english that means?
[05:43] <davyd> which allows you to type dav: and it expands to davyd:
[05:43] <Nafallo> hunger: http://www.magicalforest.se/tmp/libxaw_7.0.2-3.diff
[05:43] <Nafallo> hunger: http://www.magicalforest.se/tmp/xkbutils_7.0-3.diff
[05:43] <Nafallo> now, I'm really gone :-)
[05:43] <davyd> that'd be the second most annoying feature, right after the one where tab matches the first option, rather then matching as much as possible
[05:43] <HiddenWolf> davyd, how do I kill this? I'd rather not have my pc think for itself
[05:44] <davyd> HiddenWolf: the completion character is in the preferences
[05:44] <HiddenWolf> annoying feature -> bug
[05:44] <davyd> for the dumb tab completion you'll need to give the command I gave originally
[05:45] <HiddenWolf> Nah, I like tab completion, it just has to do it when I want to, not at random
[05:46] <davyd> it doesn't turn off tab completion
[05:46] <davyd> it just goes to the old gnu-readline style
[05:46] <davyd> like it used to be
[05:47] <davyd> like it is in zsh
[05:52] <HiddenWolf> nafallo, how soon do you think it'll be before xorg is unbroken?
[06:00] <infinity> HiddenWolf : A week would be a good estimate for X to be mostly happy for most users.
[06:02] <robertj_> after X is happy, is there going to be another colony release/
[06:03] <infinity> You'd have to ask Kamion, who appears to be having himself a weekend away from IRC.  Something I should also do.
[06:07] <HiddenWolf> infinity: thank you. I really need to upgrade to breezy, but I don't feel like messing a lot. :(
[07:02] (CarlFK/#ubuntu-devel) if i hit Scroll lock just right, I can get it to stop with: tail /var/log/syslog - no such file
[07:14] <CarlFK> it seems like the install is still progressing, but the console is just being flooded with that error so I can't see the status of the install
[07:17] <bytee_> hi ubuntites! casper does liveCDs, has anyone thought of, or is anyone working on making it so that casper does USB thumb drive installs ?
[07:43] <thesaltydog> does anybody know if there is a patch available to let gnome-app-install working on Hoary?
[07:50] <lamont> dpkg-shlibdeps: warning: could not find path for libhal.so.1
[07:50] <lamont> bad hal
[07:54] <fabbione> hey lamont
[07:54] <fabbione> lamont: there was no need to bootstrap dbus <-> kdelibs
[07:54] <fabbione> kdelib first, than dbus did it
[07:54] <lamont> fabbione: that's because you had a dbus to install
[07:54] <fabbione> hmm yes, but it was a very old version
[07:55] <lamont> well, maybe in hoary
[07:55] <fabbione> meh
[07:55] <lamont> and what I did was install kdelibs4-dev (with hoary allowed), and then built dbus
[07:55] <fabbione> yeah gotcha
[07:56] <fabbione> food is ready
[07:56] <fabbione> later
[08:05] <thesaltydog> does anybody know if there is a patch available to let gnome-app-install working on Hoary?
[08:07] <scorpix> is there any news about Colony 3?
[08:11] <hunger> scorpix: From what I understand the next colony will be released once xorg gets somewhat more stable.
[08:12] <hunger> scorpix: Someone mentioned something about it being ready in a week or so...
[08:36] <carl> has anyone tried todays install?  mine errors near the beginnig
[08:52] <mdz> seb128: are we going to see xchat-gnome for breezy?
[08:57] <{Seb}> mdz: what advantages does xchat-gnome have over plain xchat?
[09:05] <chrissturm> seb: xchat-gnome is a new frontend for the popular X-Chat IRC client  targeted towards the GNOME platform. Our eventual goals include full desktop integration and HIG compliance.
[09:15] <{Seb}> great
[09:15] <{Seb}> hope it gets into Breezy
[09:16] <chrissturm> doesnt build for me :(
[09:25] <Amaranth> anyone know of a way i can fsck my linux HD from windows?
[09:25] <Amaranth> i know this isn't a -devel question
[09:28] <carl> Amaranth, #ubunto
[09:33] <hunger> Amaranth: Knoppix springs to my mind there...
[09:33] <Amaranth> No CDs.
[09:34] <zyga> Amaranth: ntfs or fat?
[09:34] <Amaranth> hmm, i think fat32
[09:34] <zyga> Amaranth: belay thay---- I've got reading problems
[09:34] <carl> ext2 (/boot part
[09:34] <carl> huh?
[09:34] <Amaranth> i'm on windows
[09:34] <Amaranth> i need to read linux fs
[09:34] <Amaranth> well, fsck it
[09:34] <zyga> Amaranth: that's fscking difficult
[09:34] <Amaranth> no shit
[09:34] <carl> Amaranth, i think you should describe the symptoms
[09:35] <Amaranth> error 17 on grub load
[09:35] <Amaranth> HD overheated, humorously enough, during a fsck
[09:35] <chrissturm> Amaranth, i repaired my hd with spinrite
[09:36] <chrissturm> but its commercial
[09:36] <Amaranth> the other drive was got even hotter and is fine now so i'm hoping its just a silly error like a corrupt superblock
[09:37] <zyga> Amaranth: 1) cool your drive with a good fan 2) put the drive in a linux box 3) don't mess with it on windows, it's difficult already
[09:37] <Amaranth> chrissturm: needs a CD and/or floppy anyway
[09:37] <Amaranth> zyga: 1) i seperated the drives, won't be a problem anymore 2) not possible, this is the only box 3) it's either that or stay on windows
[09:37] <carl> Amaranth, yeah - if you really want to fix it, don't mess around with a win solution - figue out how to get some sort of Linux
[09:38] <Amaranth> i will hopefully have a hoary CD late tomorrow night but i really need to get back to work on smeg
[09:38] <zyga> Amaranth: it's either that or go to a internet caffe and convince the owner to allow you to attach your drive and boot from *nix live cd
[09:38] <Amaranth> I don't have any CDs...
[09:38] <zyga> Amaranth: any friends that can help you?
[09:39] <Amaranth> yeah, late tomorrow night
[09:39] <chrissturm> Amaranth, can you boot over pxe?
[09:39] <carl> Amaranth, what do you use for dhcp?
[09:39] <Amaranth> 34 hours from now
[09:39] <Amaranth> my cable modem
[09:39] <carl> rats.  no pxe stuf then
[09:39] <Amaranth> it's admin interface has one thing on it: a reset button
[09:40] <zyga> Amaranth: hmm
[09:40] <zyga> Amaranth: what about colinux?
[09:40] <zyga> Amaranth: co-something-linux - it boots form windows and uses disk image as it's / fs
[09:40] <Amaranth> will colinux be able to see the drive if windows itself can't?
[09:40] <zyga> Amaranth: maybe it could fsck your partition
[09:41] <zyga> Amaranth: I'm not sure - it has a tiny gentoo image available - it's worth checking
[09:41] <zyga> Amaranth: it does run some windows driver stuff so it *might*
[09:41] <zyga> Amaranth: alhough you'd need admin privilidge on your box
[09:42] <Amaranth> i have that :P
[09:44] <Mez> erm
[09:44] <Mez> keybuk/elmo/lamont ping
[09:45] <sladen> Mez: you could always just ask the question
[09:45] <Mez> Preconfiguring packages ...
[09:45] <Mez> dpkg: configuration error: unknown option log: Success
[09:45] <Mez> it b0rked cause of those test packages
[09:45] <Mez> :D
[09:45] <Mez> from backports
[09:46] <Mez> and /me slaps sladen round a bit
[09:47] <Mez> lamont, you can poke backports to start right?
[09:47] <seb128> mdz: I've not really played with it, but yeah, would be nice to get. No objection to package it for universe now with the UVF?
[09:47] <Mez> it doesnt neccesarily need to be elmo
[09:47] <mdz> seb128: no objection, no
[09:49] <lamont> Mez: I can upload source, I can make buildd's build, but I can't muck with the archive
[09:49] <Mez> fair enough
[09:49] <Mez> buggery
[09:49] <Mez> dpkg = b0rked
[09:52] <mdz> Mez: ?
[09:52] <Mez> sorry - my dpkg = b0rked
[09:53] <Mez> (as in I cant install anything
[09:53] <mdz> then I recommend installing one of the working versions available in the archive
[09:53] <Mez> mdz, that's the problem I can't - i need dpkg to install it
[09:53] <fabbione> Mez: use a livecd to boot and use chroot
[09:54] <mdz> Mez: unpack the .deb with dpkg -x and use the dpkg binary contained therein
[09:54] <fabbione> hi mdz
[09:54] <Mez> ah, good idea
[09:54] <fabbione> mdz: how is going today?
[09:54] <lamont> fabbione: your way is so new-school. :-)
[09:54] <mdz> fabbione: much like yesterday
[09:54] <mdz> only I got a good night's sleep
[09:54] <fabbione> lamont: ain't my fault if you are over 40
[09:54] <mdz> which was nice
[09:54] <fabbione> mdz: sounds good
[09:55] <Mez> mez@apathy:~/dpkg$ dpkg -x *
[09:55] <Mez> dpkg: configuration error: unknown option log: Success
[09:55] <Mez> looks like I'm gonna have to do it manually
[09:56] <fabbione> Mez: dpkg -x dpkg-balbal .
[09:56] <fabbione> it will unpack the dpkg in there...
[09:56] <fabbione> * is not an option
[09:57] <Mez> I'm getting an error with the extracted dpkg too
[09:57] <mdz> Mez: edit /etc/dpkg/dpkg.cfg and comment out the 'log' line
[09:58] <mdz> it sounds like you ended up with a dpkg.cfg written for a newer version of dpkg
[09:58] <Mez> most likely, was downgrading it
[09:58] <mdz> don't do that
[09:58] <mdz> downgrades in general are untested and unsupported; not something to try with an essential package
[09:58] <Mez> mdz, I had an untested version from backports :D
[09:58] <Mez> but hey
[09:59] <Mez> that seems to have fixed it
[09:59] <ogra> Mez, any reason why you backport dpkg ?
[09:59] <Mez> thanks for your help
[09:59] <Mez> ogra - it was lamont's "acid test"
[10:00] <ogra> wohoo... acid test...
[10:00] <Mez> I had the "official" backports repository in my apt list :D
[10:00] <Mez> lol
[10:00] <Mez> and managed to upgrade to that
[10:00] <Mez> once it was purged, I still had it and wanted to know i had a safe version, so tried to downgrade :P
[10:00] <lamont> Mez: not my acid test - I just build stuff
[10:00] <zyga> Mez: could you elaborate on that acid test :> ?
[10:00] <Mez> well, someone used dpkg as the "test" backported package
[10:01] <lamont> zyga: it's good to build some package in a suite before declaring it ready for prime time
[10:01] <ogra> Mez, you should create a chroot for your package tests to not break your system every time
[10:01] <lamont> some days it's dpkg, other days it's ed
[10:01] <ogra> lamont, dont forget the kernel :)
[10:01] <Mez> ogra - I do have a chroot....
[10:02] <Mez> but I had the "official" repository added, and in there was a backport of dpkg (now re-reading the email, it was elmo who used that as the test, so apoliogies lamont)
[10:03] <mdz> lamont: what's difficult to understand about -backports?
[10:03] <mdz> lamont: elmo would have used ed, but it was the same version in hoary and breezy ;-)
[10:03] <Mez> lol
[10:03] <mdz> the next logical candidate was a core piece of package management infrastructure, of course
[10:04] <Mez> anyway, i fixed that now :D
[10:06] <Mez> mdz, is it only elmo who can start packages being backported?
[10:06] <mdz> Mez: yes, please be patient, as he has weekends off
[10:06] <Masoud> Hi
[10:06] <Mez> mdz, I wasn't moaning, was just asking :d
[10:06] <mdz> it will be more automated in the future, but for now this is the most effective way
[10:08] <pitti> Hi
[10:08] <seb128> hey pitti
[10:08] <seb128> pitti: what do you do here on a saturday night? :)
[10:09] <pitti> seb128: we were hiking and on the fair all the day, so my gf fell asleep 1 hour ago :-)
[10:09] <seb128> ah ah
[10:09] <pitti> so I wanted to do some postgresql hacking
[10:09] <pitti> (I can't see Firefox today)
[10:10] <pitti> seb128: and you?
[10:10] <zyga> hey pitti
[10:10] <zyga> pitti: what's up with firefox?
[10:11] <pitti> zyga: YOU SAID THE WORD!!!
[10:11] <pitti> ogra: oh, did he solve it? :-)
[10:11] <ogra> lol
[10:11] <seb128> pitti: just coming back from dinner and having a look on my mail and this XOPEN_SOURCE issue
[10:11] <fabbione> WOW
[10:12] <fabbione> i still had receipts from Oxford's meeting in my wallet!
[10:12] <zyga> pitti: relax it's not like 10^5 users are complainig or anything
[10:12] <pitti> oh, me too :-) some taxi bills
[10:12] <fabbione> no wonder it was so heavy
[10:12] <pitti> zyga: I'll look into the 1.0.6 patches today, but after 60 hours of ffox hacking last week I need a break
[10:12] <pitti> s/today/at monday/ of course
[10:13] <lamont> pitti: it just _feels_ like monday, eh?
[10:13] <zyga> pitti: I'm done working on $$$ apps today, I could help you review those patches tommorow (not on monday)
[10:16] <herve> hey, my firefox works like a charm
[10:16] <pitti> mine too :-)
[10:16] <Mez> backported firefox = uber too
[10:17] <pitti> but nice that there is at least one other person it works for
[10:17] <pitti> well, it does run very well without those damn extensions
[10:17] <Mez> pitti, which extensions?
[10:17] <ogra> bah, extensions
[10:17] <pitti> Mez: well, most
[10:17] <pitti> Mez: I use AdBlock, that works fine
[10:17] <zyga> pitti: /topic #ubuntu extensions are bad, don't use them, simplicity is bliss ;)
[10:18] <zyga> pitti: but really I'd like to help
[10:18] <seb128> bah
[10:18] <herve> hu? I have a dozen extensions
[10:18] <Mez> google toolbar works fine too (well in backported version)
[10:18] <seb128> people you should all use epiphany
[10:18] <seb128> it works fine
[10:18] <ogra> herve, and up to date hoary ?
[10:18] <pitti> zyga: well, I wrote to ubuntu-security-announce, u-devel, and u-users, explaining the issue and workarounds
[10:18] <herve> ogra, s/hoary/breezy
[10:18] <zyga> pitti: checking
[10:18] <ogra> herve, ahh
[10:18] <pitti> zyga: I extracted the ffo 1.0.5 -> 1.0.6 changes, I will port them at Monday (half of the patch doesn't apply)
[10:19] <Mez> pitti: are these problems likely to affect the backport?
[10:19] <Mez> and if so, should I pull the backport
[10:20] <pitti> Mez: yes, one of the patches apparently broke the API
[10:20] <Mez> pitti: does that apply to hoary though? seeing as it has a different API?
[10:21] <pitti> Mez: no, actually all the 1.0.x versions should have the same api
[10:21] <ogra> pitti, ha ha ha
[10:21] <Mez> grr
[10:21] <Mez> nopt API
[10:22] <pitti> yes, right, sorry
[10:22] <Mez> pulls
[10:22] <pitti> yeah, typos :-)
[10:22] <Mez> so, pull it or not?
[10:23] <pitti> Mez: if you want to...
[10:23] <zyga> pitti: hmm did you post that mail as someone else? i can't find it i u-d
[10:24] <Mez> pitti: if the problems are gonna ffect hoary too... then I should
[10:24] <Mez> I was about to ask the same thing zyga
[10:24] <ogra> zyga, he crossposted to -users.... if your filters are as silly as mine, you'll find it there
[10:24] <pitti> zyga: no, as Martin Pitt<EMAIL_ADDRESS>[10:25] <Mez> ah
[10:27] <zyga> it seems that whatever makes u-d archives is equally silly or I'm blind because it's not there
[10:29] <zyga> just a side note, firefox really kills the CPU when it's trying to /search for something that does not exist, evey keystroke laggs begind gui
[10:29] <Mez> pulled from backports
[10:29] <Mez> I couldnt find it in the archive either
[10:30] <{Seb}> after upgrading to the latest Xorg, i get an Xsession box when i login with nothing it in
[10:30] <{Seb}> is this a known bug?
[10:30] <Treenaks> yes
[10:31] <Treenaks> or, you could look on bugzilla.ubuntu.com :)
[10:31] <{Seb}> any way to remove it?
[10:31] <zyga> pitti: is it possible to keep the same API as 1.0.2 had?
[10:31] <zyga> pitti: api/abi whatever's changed?
[10:31] <pitti> zyga: no, one vulnerability really was an API flaw, so it needed to be changed
[10:32] <zyga> pitti: what about api wrapper? I'm not familiar with that flaw so I'm shooting blanks here?
[10:32] <zyga> pitti: that's c++ code change, right?
[10:33] <pitti> zyga: yes
[10:34] <ogra> {Seb}, try to explicitly select a gnome session from gdm
[10:35] <zyga> pitti: did you extract the changes from ff repository or are they availiable somewhere?
[10:36] <pitti> zyga: I took the patches from bugzilla, extracted them from cvs, compared them to each other, and then backported
[10:36] <pitti> zyga: the mozilla advisories point to bug numbers
[10:38] <{Seb}> do you know which bug it is?
[10:38] <{Seb}> there are so many bugs for Xorg (129 actually)
[10:40] <seb128> try #ubuntu maybe?
[10:40] <ogra> {Seb}, no idea... did it work ?
[10:44] <{Seb}> Xorg works yes, and the whole desktop infact
[10:44] <{Seb}> just this annoying box which i have to click OK for GNOME to load
[10:45] <zyga> pitti: okay thanks, I'll talk to you tomorrow
[10:46] <herve> {Seb}, all keyboard keys too?
[10:46] <{Seb}> think so
[10:47] <herve> I had to say gnome to use its layout instead of X's
[10:47] <herve> but now it runs fine
[10:54] <trulux> pitti: nite man :)
[10:54] <pitti> Hi trulux
[10:55] <trulux> pitti: how's it going?
[10:55] <pitti> fine, and you?
[10:56] <trulux> pitti: tired, went out with friends for watching the Four Fantastic
[11:08] <pitti> ah, btw, ajmitch: what's the selinux status? do we still need patches to be applied?
[11:11] <tritium> hi trulux
[11:14] <trulux> hey tritium
[11:18] <lamont> hehe xfree86 is ftbfs: can't find -lXext
[11:18] <lamont> but fixing that probably wants to wait for daniels to finish breaking things...
[11:21] <ogra> tritium, likely, yes
[11:22] <tritium> ogra, seems too good to be true :)
[11:22] <ogra> laptop misson ?
[11:22] <tritium> yes
[11:22] <ogra> enjoy ;)
[11:22] <ogra> (and test indeed)
[11:22] <tritium> Absolutely!
[11:23] <crimsun> ogra: thanks for fixing pymad; I had uploaded -1ubuntu1 and -1ubuntu2, but my key expired. I kept Debian's packages, though, for python2.2 and python2.3.
[11:24] <ogra> crimsun, yes, it caused some confusion, since i suspeted mine was expired (which is impossible) :)
[11:31] <carl> when is the next time breezy/daily will be refreshed?
[11:32] <herve> we should find some solution about those acpi issue
[11:32] <herve> I have to patch the initrd each time I update the kernel


[05:40] <fabbione> morning
[05:40] <bderrly> evening
[05:48] <calc> grr wake up hobbsee
[05:48] <calc> rather come back you were here 1hr ago
[05:48] <ajmitch> heh
[05:49] <calc> she has been marking bugs as duplicates that aren't actually due to a misunderstanding of the bug
[05:49] <calc> hopefully she's the only one who has been doing it so that she has a list of them to fix quickly
[05:49] <calc> apparently marking anything that was broken due to new glib/gtk as a duplicate of the openoffice bug
[05:50] <calc> of course i didn't even know what the cause was until the past day or so
[05:50] <calc> so its not her fault
[05:59] <TheMuso> calc: She does idle on here as LongPointyStick as well.
[06:03] <DShepherd> hehe.. nice nick
[06:05] <calc> TheMuso: oh ok
[06:05] <calc> LongPointyStick: hey sarah?
[06:05] <StevenK> Her other client is mainly for logging.
[06:07] <StevenK> calc: So, what is the cause?
[06:07] <calc> StevenK: oh ok
[06:07] <calc> StevenK: improper (or non-existent) initialization of glib/gdk/gtk before calling a function
[06:07] <calc> StevenK: in openoffice case there was a call to gdk_screen without initialization
[06:08] <StevenK> Neat.
[06:08] <StevenK> Are you fixing it with a patch, or is upstream?
[06:10] <calc> StevenK: a guy at redhat has a fix, but i'm not sure if he considers it good enough for general use yet, i sent him an email letting him know it works for ubuntu (its not even really needed on fedora) and to see if he wants to commit it upstream
[06:10] <calc> i should know something in probably 12hr or so
[06:13] <thully> i'm curious if anyone here knows about getting in touch with Ubuntu developers.  I've had many issues (mostly laptop-related, but some having to do w/the general desktop) and I haven't been able to get good developer response...
[06:14] <calc> thully: i'll let you know a secret... you are in the right channel
[06:15] <thully> The thing is - I have filed bugs, and e-mailed devs who have commented on bugs, and I feel like I might as well send my info to /dev/null...
[06:16] <calc> thully: i'm sorry to hear that, people try to get to the reports as quickly as possible but sometimes things get dropped :(
[06:16] <calc> thully: what particular issue?
[06:16] <thully> a few
[06:16] <calc> thully: some developers have many hundreds of bugs to take care of
[06:17] <calc> thully: for example anything involving openoffice is for me, so just ping me and i'll try to look at it
[06:18] <thully> The thing is - I've also been using Debian (I'm actually on Etch now), and I get their bug system fine
[06:18] <thully> You just find the maintainer/team, and they usually answer...
[06:18] <thully> calc: unfortunately none of my issues involve OpenOffice
[06:18] <calc> thully: ok :)
[06:20] <tonyyarusso> Is there a 6.06.2 in the works?  I just saw a debian-installer note in dapper-changes.
[06:20] <calc> tonyyarusso: yes eventually
[06:20] <calc> tonyyarusso: i'm not sure if there is a projected release date yet
[06:21] <tonyyarusso> That upload would seem to suggest it's soon, in my head at least.
[06:22] <thully> Most of my issues have to deal with laptop stuff - suspend to RAM, brightness controls, synaptics touchpad, ACPI C-states, and so on...
[06:22] <calc> https://launchpad.net/ubuntu/+milestone/ubuntu-6.06.2
[06:23] <calc> thully: ah ok you might ask in #ubuntu-kernel if you don't hear anything back, sounds like all of that is probably kernel related
[06:23] <thully> not necessarily synaptics, though - that's an X.org driver...
[06:24] <calc> thully: ah yea
[06:26] <calc> tonyyarusso: apparently the existence of the release isn't public yet, or at least not on wiki.ubuntu.com yet
[06:27] <calc> tonyyarusso: but yea what you see in the upload is correct there will be one
[06:30] <tonyyarusso> calc: interesting
[06:32] <calc> and i think 8.04 will be the next LTS
[06:33] <thully> One thing that has me WAY confused is "triaging".  In Debian (and almost any other project) , you simply report the bug, give enough info, and people look at it.  What is the deal with the triage process?
[06:34] <bderrly> thully, have you ever been to the hospital emergency room? it is the same idea: a nurse will categorize the incoming patients in order of importance
[06:36] <thully> who does this in Ubuntu, anyway?  I've generally had an experience where if I report a bug, it just sits on "new" for months at a time, no matter what information I attach to it...
[06:37] <johanbr> Often done by members of the ubuntu bug squad, I believe.
[06:41] <thully> is it possible to do this myself?  I've been reporting bugs in software for years, so I generally know what I'm doing...
[06:42] <RAOF> thully: You need to be in the ubuntu-qa team to have priority-changing privileges, but you can do all the rest.
[06:43] <thully> sorry, my connection was just reset by that darned Peer :)
[06:51] <StevenK> RAOF: http://www.worldofwarcraft.com/patchnotes/test-realm-patchnotes.html
[06:51] <StevenK> RAOF: Note the top item under General.
[06:52] <RAOF> StevenK: Oh, hell yes!
[06:52] <StevenK> RAOF: So, now you just need to wait for patch 2.2.0 to hit.
[06:53] <RAOF> Wooooooot!
[06:53] <StevenK> ... on fire
[06:54] <thully> OK - what I'm wondering is- how does a Bug go from "Confirmed" to "Triaged"?  I've gone through the triage steps and confirmed some of my bugs in the past, but they don't get marked "Triaged"...
[07:01] <lifeless> thully: #ubuntu-bugs is the right channel for that question, the bug triage team hang out there
[07:11] <LongPointyStick> greetings
[07:12] <ajmitch> hello Hobbsee
[07:15] <Hobbsee> calc: ah, thanks.  i'd suspected the same myself.
[07:35] <StevenK> Morning pitti
[07:35] <pitti> Good morning
[07:35] <ajmitch> morning pitti
[07:38] <Hobbsee> :)
[07:39] <Hobbsee> pitti: do you want to answer a licencing question, or send it to<EMAIL_ADDRESS>[07:39] <pitti> Hobbsee: I'd prefer u-a@, I'm no licensing expert
[07:40] <pygi> pitti, available for a little review?
[07:40] <Hobbsee> pitti: cool, ok
[07:41] <pitti> pygi: review of what?
[07:41] <pygi> pitti, libmtp
[07:41] <pygi> https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/132554
[07:41] <ubotu> Launchpad bug 132554 in libmtp "[needs review]  libmtp 0.2.1 [needs upload] " [Undecided,New]
[07:43] <pitti> pygi: can you please add an URL to the orig.tar.gz?
[07:43] <pygi> pitti, will do so now
[07:43] <Mithrandir> Hobbsee: what's the question?
[07:44] <Hobbsee> Mithrandir: in #ubuntu-motu
[07:44] <pygi> pitti, done!
[07:44] <pitti> pygi: erk, ABI bump
[07:44] <pygi> pitti, yup, I know
[07:45] <pitti> pygi: there are 4 reverse dependencies which need to be rebuilt and tested against this
[07:45] <pygi> pitti, but brings support for new hardware and brings no problems
[07:45] <pygi> pitti, been there, done that
[07:45] <pitti> well, 3 (mtp-tools is in libmtp)
[07:45] <pygi> from the bug report: All rdepends build properly against it. :)
[07:46] <pitti> pygi: debdiff looks good to me
[07:47] <pygi> good sign :)
[07:50] <pitti> pygi: uploaded
[07:50] <pygi> pitti, thanks :)
[07:50] <pitti> np
[07:59] <tonyyarusso> cjwatson: I sent you a message a while back concerning Keyspan driver.  Was wondering a) if you received it, b) if anything's happened on that front
[08:04] <ArneGoetje> tonyyarusso: cjwatson is on vacation this week.
[08:05] <tonyyarusso> cjwatson: I have http://www.keyspan.com/products/usb/USA19HS/, which has firmware and drivers included in the vanilla 2.6 kernel tree, but which have not been included in Debian/Ubuntu due to licensing problems, as explained on http://www.keyspan.com/downloads-files/developer/linux/.  I was wondering if it could be evaluated for inclusion in linux-restricted, per the advice of someone else.
[08:05] <tonyyarusso> ArneGoetje: ah, hrm.  e-mail to -devel better you think?
[08:05] <ArneGoetje> tonyyarusso: probably
[08:23] <\sh> morning all...
[08:23] <\sh> does anyone has a clue how the we determine if a graphics card is able to have "Composite" extension enabled?
[08:24] <\sh> s/the//
[08:25] <pitti> \sh: mvo can tell you stories about it
[08:25] <pitti> \sh: look at /usr/bin/compiz, that does exactly that
[08:28] <mjg59> Composite is supported on all cards
[08:28] <mjg59> But I don't think that's what you're asking
[08:29] <pitti> \sh: yeah, for s/cards/driver/
[08:30] <pitti> ideally it would also blacklist cards, though
[08:30] <pitti> some are just too old and slow to sensibly support it
[08:30] <pitti> (with our drivers anyway)
[08:31] <RAOF> pitti: We do
[08:32] <RAOF> Oh, sorry.  EPARSE.
[08:34] <\sh> pitti, mjg59 : the problem I had was with an ati radeon 9600 card (desktop) (128MB ram) and with the oss ati/radeon driver
[08:35] <pitti> \sh: same here; compiz works OOTB on my radeon 9200, but the ati driver is way too slow
[08:35] <\sh> the little ati radeon m22 (r300 card) works on my laptop nicely with compiz on gutsy, but the desktop card doesn't...desktop effects aren't working
[08:35] <RAOF> Really?  I think that might be a Ubuntu-specific problem then.  People happily run compiz on 9200s
[08:37] <pitti> RAOF: well, as I said it works, but some operations like resizing windows are painfully slow
[08:37] <RAOF> Ah, but not in general?
[08:38] <\sh> could it be, that this is an dist-upgrade issue from feisty to gutsy? I had some troubles with the latest updates from feisty (oofice and ttf-opensymbol package) and after upgrading to gutsy the same problems...
[08:38] <pitti> RAOF: in general it's just a bit sluggish
[08:38] <RAOF> People in #compiz-fusion are probably not quite as performance-sensitive as you :)
[08:39] <pitti> RAOF: I guess you could get used to the speed after a while, but I find it annoying after a while
[08:39] <\sh> I'll do a clean install with gutsy media this evening ... let's see
[08:39] <pitti> RAOF: it's just a poor old G4 800 MHz, that might contribute to the problem :)
[08:39] <RAOF> :)
[08:56] <thully> devs - where would be the best place to discuss a few laptop issues I've been having as of late?  I've reported them (or commented on them) and they've for the most part sat in launchpad limbo...
[08:57] <thully> A few of the issues include 122682, 37234 (granted, more of a feature request - but quite a significant one), and 128653
[09:03] <thully> I've also got 124642, but I just reopened that one - apparently my MacBook likes to make funky noises in some ACPI C-states, but only with certain kernels
[09:10] <thully> I guess I dunno what to do from here - I want to help on these issues, and the whole laptop support area in general, but I haven't been able to find much (I saw a laptop team, but it looked like it mostly consisted of mjg59 and a few people who posted their specs/results).
[09:12] <mdke> thully: you could try the laptop-testing mailing list.
[09:12] <thully> That's as dead as a doornail - check the archives
[09:13] <mdke> seems slightly less dead than laptop-devel
[09:14] <mdke> thully: maybe give it a try, if you don't get anywhere you could try the main development lists
[09:18] <thully> OK
[10:13] <lifeless> where do test-install-reports go these days ?
[10:14] <pitti> lifeless: https://iso.qa.stgraber.org/
[10:15] <lifeless> shame its not a ubuntu.com name
[10:15] <lifeless> hmm
[10:15] <pitti> yeah, but it hopefully will be in the future
[10:15] <lifeless> I have a 36 step-to-install document
[10:15] <lifeless> its not clear what issues are bugs, and what are not.
[10:16] <lifeless> that web site doesn't give me any hint as to what I should do in this situation.
[10:16] <pitti> we usually file bugs and link them in the install reports
[10:17] <lifeless> right, but where do I write up my report ?
[10:17] <pitti> lifeless: if you click on a particular ISO, you'll see the tests you can do with it, and if you click there you can submit your's
[10:19] <lifeless> its hellishly slow
[10:20] <lifeless> slower than launchpad
[10:20] <lifeless> ok, none of the tests match what I did
[10:20] <pitti> weird, it's not any slower than any other webpage (faster than LP in any case for me)
[10:20] <pitti> might be my geographically close location :)
[10:20] <lifeless> its https and lots of separate requests
[10:20] <pitti> I guess that thing is in .de
[10:20] <lifeless> this is known as 'bad'
[10:20] <Hobbsee> it's faster than LP here
[10:21] <Hobbsee> which is weird
[10:22] <pitti> heh, only 6 hops here
[10:31] <StevenK> pitti: libvips10c2a, libvips10-dev, libcgal1, hylafax-doc and hat-ghc6 can be NBS'd out at your leisure.
[10:31] <pitti> yay
[10:31] <lifeless> pitti: my mail has hit ubuntu-devel
[10:32] <lifeless> (if you are interested)
[10:32] <pitti> I am
[10:33] <stgraber> lifeless: about the "I think the ISO testing web pages
[10:33] <stgraber> should include some guidance for adhoc tests"
[10:33] <stgraber> (crappy copy/paste ...)
[10:33] <stgraber> It's possible to add a link to a wikipage for each tests, but we need people to do so :)
[10:34] <pitti> StevenK: hm, ppu-fortran needs a rebuild on i386 and ppc for getting rid of libmpfr1
[10:34] <pitti> StevenK: killed, merci
[10:34] <stgraber> (the Ubuntu Server have a link to what to a test description (if you click on the icon next to the test name))
[10:36] <stgraber> pitti: It's hosted in France with some nice peerings for Germany (and Switzerland by the same)
[10:38] <stgraber> (and yes it'd need more RAM :), 256MB being a bit short but that's what you have when you pay 20 for a server :))
[10:39] <lifeless> stgraber: well, I'm not saying that there need to be links to each test
[10:39] <pitti> stgraber: I also pay 20 for my colo, but I could just buy another gig and have them build it in at no additional monthly cost (just the price for the RAM bar, of course)
[10:39] <lifeless> stgraber: I'm saying that when someone does a test which is not covered, what should they do ?
[10:40] <lifeless> I installed a crypted, lvm'd, desktop.
[10:40] <lifeless> thats not even a minor variation, its a massive variation, because of the impact on partitionining, on whether the right packages *can* be there, of using universe...
[10:41] <Lutin> pitti: can you give-back mgcv and kernsmooth please ?
[10:41] <lifeless> anyone know if gconf database is arch specific?
[10:42] <mvo> mjg59: are you around? I'm writting up the discussion of the techboard meeting now and I wonder if the performance problem for 3d apps in compiz affects all video drivers or only nvidia. I can not see it here on my ati system (in a quick and unscientific test)
[10:43] <pitti> Lutin: done
[10:49] <mvo> pitti: hm, looks like restricted-manager is currently unable to enable the nvidia driver at all :/ did you got a bugreport about this already?
[10:49] <pitti> mvo: hm, no, works quite fine for me; what does it do?
[10:51] <mvo> pitti: if I use it with the apperance capplet (--check-composited) it will give me a message that I need to enable the driver, then I click ok and nothing appears to happen
[10:51] <mvo> pitti: xorg.conf is not rewriten at least
[10:51] <mvo> I think the download worked earlier
[10:51] <mvo> pitti: this is a fresh tribe-4 install
[10:52] <pitti> mvo: oh, can you please try with latest r-m?
[10:53] <mvo> pitti: ok, I will do that in a bit (machine has no network yet)
[10:53] <pitti> mvo: thanks; if it's still broken, please get back to me
[10:53] <mvo> ok, thanks
[10:53] <pitti> mvo: it indeed was broken for very new or very old cards (nvidia-glx-{legacy,new})
[10:53] <mvo> mine is neither :)
[10:53] <mvo> 6600
[11:07] <\sh> mvo, I heard you are the compiz master...upgraded feisty to gutsy, having a ati radeon 9600 card (agp desktop) running xorg with ati oss driver, but enable desktop tells me, that it's not working
[11:07] <\sh> mvo, could it be, that this is an upgrade issue, or is ati radeon 9600 not supported from xorg-ati oss drivers?
[11:08] <mvo> \sh: can you please put the output of ".xsession-errors" to a pastebin? after you tried to enable it?
[11:08] <\sh> mvo, can do it this evening :) because it's my home machine :)
[11:08] <\sh> mvo, but sure will do
[11:08] <mvo> \sh: ok, please do that then :)
[11:08] <mvo> \sh: it has some verbose output that will help me diagnose the issue
[11:09] <mvo> everything else is guesswork
[11:09] <\sh> mvo, better to install gutsy from scratch or just leave my installation like it is (upgraded gutsy from feisty)
[11:12] <mvo> \sh: upgraded should be fine
[11:13] <\sh> mvo, cool...you'll get the output around 20 :)
[11:21] <pitti> infinity: btw, what's the difference between dpkg --print-{,installation-}architecture?
[11:21] <pitti> infinity: I changed that in apport now as per your recommendation a few days ago
[11:21] <pitti> infinity: and I made it DTRT on lpia
[11:39] <Riddell> keescook: are you doing poppler packaging these days?  0.5.91 is out
[11:41] <pitti> Riddell: desktop team usually, but I can look into it, too
[11:41] <pitti> Riddell: maybe it fixes PDF printing again :)
[11:42] <pitti> Riddell: hm, http://poppler.freedesktop.org/ doesn't mention it
[11:43] <pitti> Riddell: ah, download works, though :)
[11:43] <asac> hmmm any idea where i can get a plain ubuntu.{png,xpm} ?
[11:43] <Riddell> :)
[11:44] <Riddell> asac: canonical.com has an artwork page
[11:44] <asac> i knew i was missing the obvious ;) ... thanks!
[11:45] <asac> Riddell: wiki?
[11:45] <Riddell> that too, but the public website had one made recently
[11:46] <asac> hmmm
[11:46] <Riddell> http://www.canonical.com/logos
[11:46] <asac> where is that linked from?
[11:46] <Riddell> irc logs now :)
[11:47] <asac> hmmm i want just the image ... not the text
[11:47] <asac> ... maybe i have to cut it then
[11:47] <Riddell> launchpad.net/ubuntu
[11:47] <Riddell> or, crop
[11:47] <asac> yeah :)
[11:49] <lifeless> is there something to configure which compiz plugins are active?
[11:50] <Fujitsu> lifeless: compizconfig-settings-manager or something similarly named.
[11:50] <mvo> lifeless: what Fujitsu says
[11:50] <lifeless> what package is it in? (its notinstalled )
[11:51] <mvo> lifeless: what HW do you have that made the system freeze when enabling effects? is that a i945?
[11:51] <Fujitsu> lifeless: compizconfig-settings-manager is the package, AFAIK.
[11:51] <mvo> lifeless: compizconfig-settings-manager is the pakcagename (universe)
[11:51] <lifeless> 00:02.0 VGA compatible controller [0300] : Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller [8086:27a2]  (rev 03)
[11:52] <mvo> with the "intel" driver I assume?
[11:53] <lifeless> yes
[12:00] <mvo> lifeless: I wonder if 32bit/64bit makes a difference here
[12:06] <ajmitch> Fujitsu: an impressive package, doesn't even start for me
[12:06] <Fujitsu> ajmitch: WFM
[12:06] <ajmitch> python ImportError
[12:07] <ajmitch> afaik I have the latest compiz crack installed
[12:07] <geser> must be an new error as it worked for me yesterday
[12:07] <ajmitch> or just a broken package on my system
[12:08] <tkamppeter> hi pitti
[12:08] <pitti> hey tkamppeter
[12:09] <pitti> tkamppeter: currently discussing the firmware issue
[12:09] <tkamppeter> pitti, Tim Waugh has modified the add-printer wizard so that it asks for the queue name only after printer and model selection, in time before the UVF. I have packaged it, see your mail.
[12:09] <pitti> tkamppeter: rock!
[12:10] <geser> ajmitch: just upgraded ccsm to 0.5.2+git20070814-0ubuntu1 and it still WFM
[12:10] <pitti> tkamppeter: with a nice default name now, I assume?
[12:10] <ajmitch> geser: it was referring to an undefined symbol in a library
[12:10] <ajmitch> geser: and I'm not using any 3rd party packages either :)
[12:12] <pitti> tkamppeter: will have a look later, currently attacking new poppler version (cross your fingers that it fixes PDF printing :) )
[12:12] <infinity> pitti: To be honest, I'm not sure if there is a difference anymore, I'd have to look at the code.
[12:12] <pitti> infinity: --p-i-a is not even documented
[12:13] <infinity> pitti: I know. :)
[12:15] <infinity> pitti: Ahh, there we go.
[12:16] <infinity> pitti: Okay, --print-architecture used to do the same thing as dpkg-architecture (call a compiler, other silly thing), while --p-i-a just dumped the current dpkg arch.
[12:17] <infinity> pitti: Since 2005 or so, --print-arch was fixed to do what --p-i-a used to do, and then --p-i-a was aliased to --p-a, so they're the same (and both correct) now.
[12:17] <infinity> pitti: I just live in the past, apparently.
[12:17] <ajmitch> geser: I had old libcompizconfig0 installed, I guess it's a bit loose with shlibs
[12:17] <pitti> infinity: ah, good; I guess I'll revert it then to stay on the documented side
[12:20] <geser> ajmitch: bug mvo about it
[12:20] <infinity> pitti: Probably safer, though if a dpkg dev ever drops --p-i-a, there will be an uproar from both the Debian and Ubuntu buildd maintainers who have it hardcoded all over the place (due to the old switch historically not quite doing the right thing)
[12:22] <pitti> tkamppeter, geser: rock! new poppler fixes pdftops
[12:22] <geser> yeah
[12:24] <tkamppeter> pitti, great, then this showstopper is fixed.
[12:25] <pitti> can anyone on current gutsy please test whether opening http://fixnum.org/public/fullcircle/fullcircle-issue01-english.pdf in evince crashes?
[12:27] <geser> pitti: Segmentation fault (core dumped)
[12:28] <geser> on amd64
[12:28] <Mithrandir> pitti: works fine for me on i386
[12:28] <pitti> geser: cool, thanks; with new poppler it works fine
[12:28] <Fujitsu> Works on i386 here.
[12:28] <tkamppeter> pitti, default printer name is derived from the model, and if the model was not auto-detected derived from the selected PPD.
[12:28] <pitti> so seems bug 123116 is fixed as well
[12:28] <ubotu> Launchpad bug 123116 in poppler "evince-thumbnailer crashed with SIGSEGV in Object::fetch()" [Medium,Fix committed]  https://launchpad.net/bugs/123116
[12:28] <pitti> $ evince-thumbnailer -s 128 file:///tmp/fullcircle-issue01-english.pdf  /tmp/xx
[12:28] <pitti> Segmentation fault (core dumped)
[12:29] <pitti> yep, confirmed
[12:35] <pitti> Riddell: updated and tested with evince and pdflatex; it doesn't seem to break ABI this time around, but if you could test it with kpdf and koffice it would be good
[12:37] <Riddell> koffice doesn't use poppler
[12:37] <pitti> oh, right
[12:38] <Riddell> and neither does kpdf in gutsy right now, since it needed the new version, it's high on my list to port the poppler patch to kde 3.5.7
[12:38] <pitti> Riddell: ah, I see; right, I had to do that for texlive, too
[12:38] <pitti> Riddell: some minor things only, though, like UGooString -> GooString
[12:39] <pitti> tkamppeter: please register, so that we can /msg
[12:44] <pitti> tkamppeter: bug 132646 explains the problem
[12:44] <ubotu> Launchpad bug 132646 in hplip "firmware files do not have any license" [Critical,Triaged]  https://launchpad.net/bugs/132646
[12:44] <pitti> tkamppeter: I'll binary-NEW hplip now to make desktop installable again, but this should be sorted out with upstream eventually; can you contact them please?
[12:47] <tkamppeter> pitti, now /msg should work.
[01:00] <\sh> btw...is someone working on those screenlets for c-f?
[01:09] <lifeless> mvo: I have no idea.
[01:10] <Fujitsu> \sh: screenlets?
[01:17] <RAOF> \sh: Not really for c-f :)
[01:17] <\sh> Fujitsu, http://compiz.org/Desktop_Screenlets
[01:25] <gaara> ANY1 HERE READY TO HELP?
[01:26] <ogra> no
[01:26] <ogra> thats not a support channel
[02:00] <Riddell> mvo: if I run /usr/share/update-notifier/notify-reboot-required should update notifer give me a popup saying to reboot?
[02:04] <mvo> Riddell: touch /var/lib/update-notifier/dpkg-run-stamp too
[02:06] <Riddell> mvo: ok, that did something, what is it that touches /var/lib/update-notifier/dpkg-run-stamp ?
[02:06] <mvo> Riddell: a configuration option added from update-notifier
[02:06] <mvo> Riddell: that is dropped into /etc/apt/apt.conf.d
[02:09] <Riddell> mvo: so for adept should I make an update-notifier-common package with notify-reboot-required and that apt option?
[02:10] <mvo> Riddell: yes, that sounds perfect, then it can drop its 10-adept-periodic file too
[02:11] <Riddell> mvo: ok, I'll implement the adept side before playing with u-n packages
[02:11] <mvo> Riddell: ok
[02:12] <Riddell> mvo: does anything delete the dpkg-run-stamp and notify-reboot-required files?
[02:13] <mvo> Riddell: notify-reboot-required lifes on /var/run so it gets autoamtically removed and the dpkg-run-stamp is just a stamp file, no need to remove it, its monitored with inotify
[02:14] <Riddell> right
[02:15] <Riddell> mvo: do you know of anything which currently uses the upgrade hooks?
[02:17] <mvo> Riddell: the kernel I think, hal
[02:31] <Riddell> mvo: they use reboot-required but not the scripted upgrade hook
[02:31] <Riddell> as far as I can tell anyway
[02:32] <\sh> hmm..firefox is using some of those upgrade hooks, isn't it?
[02:32] <Riddell> dunno, asac?
[02:33] <\sh> they are copying things back and forth, at least since i had a look at the source package the last time, during feisty devel end or gutsy devel start, I'm not sure anymore
[02:33] <\sh> and wine should have at least this "reboot needed" notification hook , because of wine-server and mdz' bugreport
[02:34] <asac> \sh: firefox installs restart notification hints ...yse.
[02:34] <\sh> asac: not this update notification for restarted firefox?
[02:34] <\sh> s/ed/ing/
[02:35] <asac> i don't understand your question ;)
[02:35] <asac> its an update notification to restart firefox
[02:35] <\sh> asac, yeah...didn't read properly :(
[02:36] <mvo> Riddell: oh, sorry. firefox uses one of the upgrade-hooks
[02:36] <Riddell> asac: so it does, thanks
[02:37] <asac> but its not perfect that way
[02:37] <asac> its often too late to restart firefox when binaries have been replaced
[02:38] <asac> if user is out of luck he gets notification after firefox crashed ;)
[02:40] <Riddell> "Please execute the asoundconf(1) set-default-card macro" wow, that's not very user friendly
[02:41] <pitti> Riddell: WTH?
[02:41] <ogra> sexy
[02:41] <ogra> Riddell, where do you get that `
[02:41] <ogra> ?
[02:42] <\sh> with a nice blue background, I would say: vista baby vista  ,-)
[02:44] <Riddell> ogra: alsa-lib upgrade hook
[02:45] <ogra> ouch
[02:45] <Riddell> it only runs [ -f ~/.asoundrc.asoundconf ]  so I guess you have to have played around with your sound card settings previously
[02:45] <Riddell> it's not a new script
[02:48] <Riddell> seb128: you're on holiday!
[02:48] <seb128> hi Riddell, yeah I know ;)
[02:49] <Riddell> seb128: but while you're here, does anything in gnome have an update-notifier upgrade hook?
[02:50] <seb128> not that I know, but better to ask mvo, he probably knows about package using hooks
[02:51] <pitti> hey seb128
[02:51] <seb128> hey pitti
[03:14] <pitti> hey Hobbsee
[03:14] <Hobbsee> highvoltage!
[03:14] <Hobbsee> hiya pitti :)
[03:17] <geser> Hi Hobbsee
[03:18] <Hobbsee> hi geser
[03:25] <ogra> meh, since when does evo complain that i didnt add attachments to my mails ...
[03:26] <Riddell> ogra: it might do if your e-mail talks about something being attached?
[03:27] <ogra> Riddell, right, it said something like that ... bad is if someone in a thread added that content... you have the question on every reply then
[03:28] <lifeless> holy crap that would be insane
[03:29] <Hobbsee> i would assume it would detect quoted mail, and know not to ask for that
[03:30] <ScottK> In Kmail you can edit the regex that's used for the function.  I don't know about Evolution.
[03:31] <ogra> lifeless, thanks for the pointer, its indeed a plugin called "Attachment Reminder"
[03:33] <Hobbsee> ogra: thunderbird doesnt do such rubbish.
[03:33] <Hobbsee> thank goodness
[03:34] <ogra> Hobbsee, well its a neat feature if you like it i guess ... and its just one clieck to disable it
[03:34] <Hobbsee> ogra: true, but you're stuffed if you ever use another client, or webmail
[03:34] <Hobbsee> ogra: better to teach yourself to attach the attachments first, then write the email.
[03:34] <ScottK> Hobbsee: I think ogra is searching for a real mail client.    I tried Kmail and just quit looking.
[03:36] <Hobbsee> kmail is the *only* kde app that manages to confuse me.
[03:37] <ScottK> Can evolution use maildir for it's mail store yet?
[03:37] <ogra> Mithrandir, i think in total i'm over 300000 mails atm stored in 45 folders
[03:37] <Hobbsee> ogra: that's seriously too much email....
[03:37] <ogra> it handles that quite well
[03:38] <ogra> Hobbsee, i like complete local mail archives (and oi love evos search options, TB cant cope here)
[03:38] <Hobbsee> ogra: true
[03:38] <ogra> speed is the only issue ...
[03:38] <ogra> but with that amount of mail its an issue with every mail app i guess
[03:40] <ScottK> ogra: I found switching from mbox to maildir helped significantly on speed.
[03:40] <Mithrandir> ogra: I have ~12M across 1400 folders, down from about 6.5k folders which just took too long to check them all.
[03:41] <ogra> ScottK, actually since i switched to evo which offered that as default back then
[03:41] <ScottK> OK.  Didn't know that about evolution.  Maildir/Mbox is a big performance difference application differences aside.
[03:41] <ogra> Mithrandir, oh, i only have one folder on the server that i check and leave sorting to filters ....
[03:41] <Mithrandir> yes, I filter into those folders.
[03:42] <ogra> s/one folder/one incoming folder/
[03:42] <ogra> but server sided i guess ...
[03:43] <ogra> i leave the filtering to evo as well ...
[03:43] <tkamppeter> pitti, ping
[03:44] <pitti> tkamppeter: still here
[03:51] <lifeless> what does 'policy timeout is not valid' when trying to suspend mean?
[03:53] <Kmos> "running /scripts/init-bottom"
[03:53] <Kmos> it's part of which package?
[03:53] <lifeless> many
[03:53] <highvoltage> initramfs-tools
[03:53] <lifeless> its a directory of scripts
[03:54] <highvoltage> (amongs others, yes)
[03:54] <Kmos> bug 132289
[03:55] <ubotu> Launchpad bug 132289 in Ubuntu "[gutsy]  segmentation fault during boot in /scripts/init-bottom" [Undecided,New]  https://launchpad.net/bugs/132289
[03:55] <Kmos> it's about this bug
[03:55] <ogra> Kmos, thats likely not even related to initramfs ...
[03:55] <ogra> something *inside* is having a segfault
[03:56] <ogra> to fix that bug you have to find out what exactly produces it
[03:56] <Kmos> ogra: it's kernel related
[03:56] <Kmos> ?
[03:57] <ogra> unlikely ... its likely an app dying in the initramfs
[03:57] <pygi> xhaker, poke?
[03:57] <xhaker> pygi, rock on
[03:57] <Kmos> ogra: what logs should I ask for ?
[03:57] <Kmos> kernel generala ?
[03:57] <Kmos> *general
[03:58] <stdin> Bug #131961
[03:58] <ubotu> Launchpad bug 131961 in initramfs-tools "segfault when booting 2.6.22-9-generic" [Undecided,Confirmed]  https://launchpad.net/bugs/131961
[03:58] <xhaker> ogra, can it be udevd?
[03:58] <pygi> xhaker, pm
[03:58] <ogra> as i said, i doubt thats kernel related, to debug that you need to enter the initramfs during boot and find out whats dying ...  Kmos, thats a pretty advanced bug
[03:59] <Kmos> :(
[03:59] <Kmos> ogra: can you take care of it ? =)
[03:59] <ogra> Kmos, no
[04:00] <ogra> (i'm working fulltime on other stuff already but i assume the right people have seen it already)
[04:00] <Kmos> i hope so :)
[04:04] <Kmos> stdin: bug 132385 another seg fault
[04:04] <ubotu> Launchpad bug 132385 in Ubuntu "Kubuntu shows three mysterious segfaults on VT1." [Undecided,New]  https://launchpad.net/bugs/132385
[04:04] <stdin> Kmos: same bug
[04:04] <Kmos> :))
[04:05] <Kmos> stdin: dupe done, thx
[04:05] <jdong> but but... that one is for *kubuntu*
[04:05] <ice-phoenix> hi
[04:05] <jdong> ;-)
[04:05] <jdong> lol
[04:05] <ice-phoenix> can someone help me with kubuntu
[04:05] <Hobbsee> !jdong | jdong
[04:05] <ubotu> jdong: jdong is Hobbsee: jdong: yes, but you're FULL OF CRACK!
[04:05] <jdong> :)
[04:05] <Hobbsee> ice-phoenix: you probably want #kubuntu
[04:05] <jdong> how is everyone doing?
[04:05] <ice-phoenix> tnx
[04:07] <lamont> Keybuk: thoughts on 132536?
[04:10] <lamont> pitti: requestsync doesn't like me
[04:11] <Hobbsee> lamont: why?
[04:11] <lamont> because I didn't have a deb-src line, I'm betting
[04:12] <Hobbsee> that'll do it
[04:12] <tkamppeter> pitti, I think we should put the 20_...nonroot... patch back into system-cups-manager. It makes the tool more universal. For example on systems without local CUPS daemon (pointing to a server via client.conf) s-c-p will work only with the patch. We should rename the patch to tell what it really does.
[04:12] <lamont> tkamppeter: as long as the name isn't 20_gaping_security_hole.patch
[04:14] <lamont> Hobbsee: that and the fact that apt-cache madison doesn't seem to find things with ~ in the name or some such
[04:15] <Hobbsee> lamont: it doesnt use apt-cache madison anymore, afaik
[04:15] <Hobbsee> lamont: it uses rmadison -u ubuntu and rmadison
[04:15] <lamont> OTOH, that's just me hacking around the fact that dinstall hasn't run yet, so I'm using the local version, which is a backport to dapper
[04:15] <lamont>  raise Exception('apt-cache madison does not contain %s/%s' % (sourcepkg, release))
[04:15] <lamont> bad requestsync
[04:15] <lamont> lying
[04:16] <jdong> wait, apt-cache madison doesn't find what?
[04:16] <lamont> jdong: it could be requestsync lyiung
[04:16] <jdong> could be
[04:16] <jdong> apt-cache madison has never failed on me
[04:16] <jdong> knock on wood
[04:17] <Hobbsee> lamont: you're using feisty, i take it?
[04:17] <Hobbsee> hiya calc
[04:17] <lamont> -mix.mmjgroup.com 1374: apt-cache madison postfix/2.4.5-3~0.6.06
[04:17] <lamont> -mix.mmjgroup.com 1375: apt-cache madison postfix | grep 2.4.5-3~0.6.06
[04:17] <lamont>    postfix | 2.4.5-3~0.6.06 | http://archive.mmjgroup.com  Packages
[04:17] <lamont>    postfix | 2.4.5-3~0.6.06 | http://archive.mmjgroup.com  Sources
[04:17] <pitti> lamont: hm, I thought it would use rmadison nowadays
[04:17] <Hobbsee> pitti: it does.
[04:17] <pitti> lamont: are you on feisty then? that one still used apt-cache madison IIRC
[04:17] <lamont> pitti: remind me where to freshen requestsync from?
[04:18] <pitti> tkamppeter: alright, makes sense
[04:18] <StevenK> From devscripts
[04:18] <lamont> because I'm running ~/bin/requestsync still...
[04:18] <lamont> and yes, feisty
[04:18] <StevenK> lamont: I can put a copy on a webserver, if you wish
[04:18] <Hobbsee> lamont: http://wedontsleep.org/~sarah/requestsync
[04:18] <lamont> nah
[04:18] <pitti> copying
[04:18] <pitti> lamont http://people.ubuntu.com/~pitti/scripts/requestsync
[04:18] <pitti> tkamppeter: I'll rename it then and put it back
[04:19] <lamont> requestsync postfix 2.4.5-3~0.6.06
[04:19] <lamont> Unknown option: u
[04:19] <lamont> is that bad?
[04:20] <Hobbsee> lamont: why specifying -u?
[04:20] <lamont> Hobbsee: that's the latest requestsync from you and pitti
[04:20] <lamont> running on feisy...
[04:20] <Hobbsee> lamont: sounds like rmadison screwup
[04:20] <pitti> lamont: aah
[04:20] <pitti> lamont: rmadison -u -> you need gutsy's version
[04:21] <tkamppeter> pitti, thanks.
[04:22] <Hobbsee> lamont: i presume you've already got it, but http://wedontsleep.org/~sarah/rmadison FWIW
[04:22] <pitti> tkamppeter: \o/ I mastered to convince s-c-p to print a page size specific custom test page
[04:27] <lamont> I want an option to edit the requestsync message before it gets signed
[04:27] <tkamppeter> pitti, you mean that you have a Ubuntu test page .ps file which prints on any page size like the original CUPS test page?
[04:28] <pitti> tkamppeter: I did it in a rather generic way
[04:28] <pitti> tkamppeter: s-c-p now checks whether there is a file /usr/share/s-c-p/testpage-<papersize>/ps
[04:28] <pitti> tkamppeter: it reads the papersize from the PPD
[04:29] <pitti> tkamppeter: if the papersize is not set, or there is not test page for that papersize, it falls back to the cups default test page
[04:30] <pitti> tkamppeter: http://people.ubuntu.com/~pitti/tmp/04_custom_test_pages.patch -> WDYT?
[04:30] <tkamppeter> I think it is a good idea. Send me the patch and I will apply it upstream.
[04:31] <lamont> and then he forgets to add the text that was why he couldn't use the script.
[04:31] <lamont> the postfix sync request should include the fact that it's currently in incoming...
[04:31] <pitti> tkamppeter: I'll send it to Tim with some explanations
[04:31] <lamont> pitti: my bad. ^^
[04:31] <pitti> lamont: ah :)
[04:31] <pitti> lamont: just send it as a bug followup
[04:32] <pitti> tkamppeter: the nonroot patch should go to upstream then; it didn't look Ubuntu specific at all
[04:35] <tkamppeter> pitti, have upstreamized the 20_... patch now.
[04:36] <pitti> tkamppeter: ah, you have commit access, right :)
[04:36] <tkamppeter> pitti, I am upstream of s-c-p since last week, too. Did I not tell you?
[04:36] <pitti> tkamppeter: you did, but I wasn't aware of that ATM :)
[04:37] <tkamppeter> pitti, so you can send the patch to me and I upstreamize it.
[04:37] <pitti> tkamppeter: is http://people.ubuntu.com/~pitti/tmp/04_custom_test_pages.patch good for you? Or shall I mail you and Tim for comments from him, too? (might be better)
[04:41] <tkamppeter> pitti, I will try it-
[04:42] <tkamppeter> pitti, but note that Tim has fixed a lot of issues after I have done the last package we are 5 SVN revs further now.
[04:43] <pitti> tkamppeter: ok, I'm doing an upload now with the ubuntu test pages and bug 107766 fixed
[04:43] <ubotu> Launchpad bug 107766 in system-config-printer "system-config-printer adds menu item the same as gnome-cups-manager's menu item" [Medium,In progress]  https://launchpad.net/bugs/107766
[04:45] <tkamppeter> pitti, I have applied your test page patch to s-c-p installed into my system and it ptints the original CUPS test page on my A4 laser and on my small 10x15 photo printer.
[04:46] <tkamppeter> Should the A4 laser not print a special test page?
[04:46] <pitti> tkamppeter: right, that's fine
[04:46] <pitti> tkamppeter: of course you need the actual files, too :)
[04:46] <pitti> tkamppeter: I put them into the s-c-p package now
[04:46] <pitti> tkamppeter: just put a .ps file into /u/share/s-c-p/testpage-a4.ps
[04:47] <pitti> tkamppeter: (if your printer paper size is configured as a4)
[04:50] <pitti> tkamppeter: if there's good new stuff upstream, we can look into updating the package a couple of more times, no problem
[04:52] <tkamppeter> pitti, test page patch is upstreamized now.
[04:52] <pitti> \o/
[04:52] <pitti> my first s-c-p patch
[04:52] <tkamppeter> pitti, I really thought about repackaging from upstream now, as Tim has donme a lot:
[04:53] <pitti> tkamppeter: sure, if you feel like it
[04:53] <tkamppeter> Fixed bug 131848
[04:53] <ubotu> Launchpad bug 131848 in system-config-printer "system-config-printer.py crashed with RuntimeError in save_serversettings()" [Undecided,New]  https://launchpad.net/bugs/131848
[04:53] <pitti> tkamppeter: please wait until my current upload hit the mirror (in about 50 minutes)
[04:53] <tkamppeter> fixed bug 132227
[04:53] <ubotu> Launchpad bug 132227 in system-config-printer "Configuring a new printer should be easier and have better defaults" [Wishlist,Fix released]  https://launchpad.net/bugs/132227
[04:53] <pitti> tkamppeter: wow! I filed that only two hours ago
[04:54] <tkamppeter> Fixed redraw issues and added "Please wait" messages.
[04:54] <pitti> oh, no, I mixed that up with the 'default selection' bug
[04:55] <tkamppeter> Improved model matching
[04:57] <tkamppeter> pitti, I do not need to wait for the mirrors, I download the sources directly from the Launchpad. is 0.7.71+-svn1399-0ubuntu2 the newest one.
[04:57] <evand> Hobbsee: https://launchpad.net/~albertomilone/ ?
[04:57] <pitti> tkamppeter: right, that would work
[04:58] <Hobbsee> evand: ah, that one.  thanks
[04:58] <evand> you're welcome
[04:59] <Keybuk> lamont: bogus
[04:59] <Hobbsee> greetings, Keybuk
[05:00] <Keybuk> oh wait, maybe it isn't
[05:00] <pitti> tkamppeter: TTYL, I need to disappear for some two hours
[05:02] <Keybuk> iwj: udev doesn't build, FTBFS in watershed/libnettle somewhere
[05:03] <Keybuk> lamont: why does there need to be a /usr/lib/libvolume_id.so ?
[05:05] <lamont> well, if you want things to use it...
[05:05] <infinity> Keybuk: To link against it..?
[05:05] <Keybuk> what's wrong with /lib/libvolume_id.so :)
[05:05] <lamont> that's not used by ld
[05:06] <lamont> is used by ld.so
[05:06] <infinity> Keybuk: The same thing that would be wrong with shipping /lib/libc6.so
[05:06] <lamont> so the library package delivers /lib/libvolume_id.so, and the -dev package delivers the symlink in /usr/lib/libvolume_id.so
[05:07] <lamont> Keybuk: see "debian-policy 8.4 Development files"
[05:08] <Keybuk> ahh
[05:09] <lamont> interesting, since ubuntu udev versions are all >>>>> debian versions (which have a 0. in front of the ubuntu version)...
[05:10] <Keybuk> yeah I changed the version :)
[05:10] <lamont> any future need I have for versioned depends on udev?  we'll just forget about that
[05:11] <lamont> actually, it'll just mean that I hack debian/rules to notice that we're on ubuntu, and manually verify that a late enough version is installed, or fail.  somehow, I'm not really looking forward to that
[05:11] <iwj> Keybuk: Oh, really ?
[05:12] <Keybuk> iwj: dunno, it builds ok this time
[05:12] <Keybuk> strange thing
[05:12] <iwj> Hrm.
[05:12] <Keybuk> I'll upload if, if LP mails me, I'll bug you again :p
[05:12] <lamont> Keybuk: util-linux currently build-depends: libvolume-id-dev (>=0.113)
[05:13] <lamont> which ubuntu always meets.  since dapper.
[05:13] <lamont> so WTH did we gratuitously make our version >>>> debian?
[05:14] <lamont> it's not like we can go back
[05:14] <Keybuk> because upstream asked us to
[05:14] <Keybuk> and our udev packages are so different anyway that everything that touches it needs to be checked
[05:14] <Keybuk> so it wasn't a bad thing
[05:16] <lamont> ok.  I'll believe you
[05:17] <dobey> hey, does Scott James Remnant ever pop on irc?
[05:17] <Keybuk> no :)
[05:17] <lamont> the .so thing showed up when I was debdiffing the merged util-linux source
[05:17] <lamont> dobey: only his brother does, as Keybuk.
[05:17] <dobey> ah
[05:18] <Hobbsee> Keybuk: you really should change the real name on your client, to fool people.
[05:19] <Hobbsee> it's *far* more fun that way
[05:19] <lamont> although only for about 10 seconds
[05:19] <Hobbsee> lamont: :)
[05:20] <Hobbsee> lamont: it's a good dumping ground.  the server is actually StevenK's, which i have a shell account on.
[05:24] <tkamppeter> doko, ping
[05:28] <doko> tkamppeter: pong
[05:30] <tkamppeter> doko, biff, can you upload the new system-config-printer packages which I mention in my mail? Thanks.
[05:32] <russ_> hi :) Anyone know there way around the file structure for Python on Ubuntu?
[05:37] <russ_> My Question is:  I want to install a Python library, I know how to do this in Windows (c:\Python25\lib\) where do I put it in Ubuntu?
[05:38] <ScottK> russ_: This channel isn't for support.  I'll help you with your problem in #ubuntu-motu if you come over there.
[05:39] <russ_> ah ok, sorry for coming to the wrong place :-S
[05:39] <russ_> thanks
[05:43] <doko> tkamppeter: done
[05:48] <tkamppeter> Thanks, doko, the two bugs got automatically closed now.
[05:49] <slestak_> cjwatson: do you need any testers for your recent putty port?
[05:50] <bddebian> Heya
[05:51] <Hobbsee> slestak_: he's on leave
[05:51] <slestak_> Hobbsee: k, thx.
[06:10] <ScottK> It looks like soyuz fell over on https://launchpad.net/ubuntu/+source/zekr/0.5.1.dfsg-0ubuntu1 - " Failed to upload".  I'd appreciate it if an archive admin would have a look at it.
[06:29] <\sh> mvo, ping
[06:29] <\sh> mvo, you wanted to have the .xsession-logfile for the problem I have with the radeon card: http://de.pastebin.ca/658429
[06:30] <\sh> lspci gives me: 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AQ [Radeon 9600]
[06:30] <\sh> 01:00.1 Display controller: ATI Technologies Inc RV350 AQ [Radeon 9600]  (Secondary)
[06:31] <\sh> brb
[06:35] <\sh> back
[06:36] <mvo> \sh: thanks
[06:37] <Hobbsee> :)
[06:37] <\sh> mvo, i tried just now to use the PCI 1:0:1 (secondary controller) but this doesn't work at all
[06:38] <mvo> \sh: can I have the ouput of glxinfo and "LIBGL_ALWAYS_INDIRECT=1 glxinfo" please as well? it looks like for some reason your card does not support the subset of features that compiz requires. you use the "ati" or "radeon" driver I assume?
[06:38] <\sh> mvo, ati oss driver
[06:39] <\sh> mvo, glxinfo http://de.pastebin.ca/658439
[06:40] <\sh> mvo, glxinfo with libgl_always_indirect setting: http://de.pastebin.ca/658441
[06:41] <mvo> \sh: can you put /var/log/xorg.0.log somewhere too? my current theory is that your card is simply not support with propper 3d
[06:41] <geser> \sh: did the drm module load the r300 microcode? (see in dmesg)
[06:41] <Riddell> mvo: when I compile update-notifier it puts the gconf .schema file in /etc/gconf/schemas/ instead of /usr/share/gconf/schemas/
[06:42] <\sh> mvo, http://de.pastebin.ca/658447 xorg log
[06:43] <\sh> geser, moment I check
[08:33] <attunix> Isn't there a command where if I have multiple boot screens installed, it lets me choose which one? Because I did sudo apt-get install ubuntustudio-desktop. Later, I removed it, but the boot screen (with the loading bar) remained. Please help.
[08:47] <xhaker> doko, eclipse 3.3?
[08:48] <doko> xhaker: go ahead
[08:49] <xhaker> doko, do you have any plans to push it into gutsy?
[08:50] <doko> xhaker: sure, if you have packages ready
[08:52] <xhaker> doko, sorry i don't have any. i was passing my eyes through the archives and checking the packages i use most so i can see if i help there
[08:52] <xhaker> doko, do you think it'd be hard to make a package for eclipse using the previous version sources?
[08:53] <doko> xhaker: talk with man-di on #ubuntu-java
[08:54] <xhaker> thanks :)
[08:54] <iwj> OMG it works and I'm going to upload it.  I wonder where all the bugs are ?
[08:55] <iwj> (it = dpkg-triggers)
[09:06] <Seveas> iwj, scary... :)
[09:17] <ion_> iwj: Yay!
[09:18] <sabdfl> yowser
[09:18] <sabdfl> did we just drop dselect from main or from u-desktop?
[09:18] <attunix> How do I install the ubuntustudio-desktop file? Apt-get gives me "E: Couldn't find package ubuntustudio-desktop."
[09:19] <tkamppeter> pitti, you're back?
[09:20] <pitti> tkamppeter: almost, back in ten
[09:21] <iwj> ion_: It's just tricking me, I think.  I'll upload it and then tomorrow morning there'll be howls of protest in my inbox and irc client.
[09:21] <tkamppeter> pitti, doko has uploaded my newest s-c-p package. Now it is really nice, "Please wait" pop-ups and no non-redrawing freezes.
[09:22] <ion_> iwj: :-)
[09:23] <ion_> Perhaps i should document my thoughts about how the s-c-p UI should be improved.
[09:24] <ion_> just for consideration.
[09:27] <bryce> \sh_away: great to hear - was reinstalling mesa what did it?
[09:27] <tkamppeter> ion_, report your s-c-p improvement suggestions as a bug on Launchpad. Tim Waugh is bug contact of s-c-p and so he will get notified immediately.
[09:30] <tbf> what's the reasoning behind installing .la files
[09:30] <tbf> ?
[09:31] <Mithrandir> none, we should remove them from the face on the planet.
[09:32] <tbf> Mithrandir: well: $ dpkg-query -S libgtk-x11-2.0.la
[09:32] <tbf> libgtk2.0-dev: /usr/lib/libgtk-x11-2.0.la
[09:33] <tbf> does gutsy still install them?
[09:33] <Chipzz> tbf: that's a bug; unfortunately, the .la files have to be removed in a specific order
[09:34] <Chipzz> iirc top-to-bottom
[09:34] <Chipzz> which means that a package like gtk+ which is very low in the stack will be one of the last packages to have that bug fixed
[09:36] <tbf> Chipzz: ah. ok.
[09:37] <verwilst> if i do an apt-get source linux-source-2.6.22, do i need to do a debuild?
[09:37] <verwilst> will that build all the kernels?
[09:43] <pitti> tkamppeter: cool
[09:45] <tkamppeter> pitti, did you already go through the MIR for cups-pdf?
[09:46] <pitti> no, not yet
[09:48] <tkamppeter> pitti, I would like to close this blueprint before the UVF.
[09:55] <xhaker> hmm
[09:55] <xhaker> UVF for main and universe are simultaneous?
[09:56] <shaya> what package does one report bugs in the live cd in
[09:57] <shaya> basically, it wont work reliably on my Abit IP35-Pro motherboard (P35 chipset) if it doesn't boot w/ irqpoll option
[09:57] <mjg59> shaya: kernel
[09:57] <mjg59> linux-source-2.6.22 (assuming you're testing gutsy)
[09:57] <shaya> yes
[09:57] <shaya> it dumps to the initrd shell
[09:57] <shaya> some sata errors that are hard  to catch w/o serial console
[10:00] <shaya> filing
[10:02] <shaya> filed
[10:02] <shaya> if you need more info, feel free to ask
[10:41] <verwilst> is there a way, during a debuild of linux-source, to build only 1 kernel
[10:41] <verwilst> ?
[10:41] <verwilst> now it's building all of them :)
[10:41] <verwilst> which will take ages
[10:42] <mdke> verwilst: maybe try #ubuntu or #ubuntu-kernel for that question
[10:42] <verwilst> okido
[10:42] <ijuz__> you can delete some config files
[10:43] <ijuz__> there is this directory with the config.generic and for other archs/cpu-arch just delete the ones you don't want
[11:02] <alex-weej> mvo: are you sure you merged my patch into the new version of notification-daemon properly? i'm still getting the old pie chart with -ubuntu6
[11:12] <mvo> alex-weej: hrm, it should be in, I can have a look tomorow
[11:12] <alex-weej> i just got the latest source package
[11:12] <alex-weej> changelog entry is there
[11:13] <alex-weej> same old 01_ubuntu_theme.patch
[11:13] <mvo> hmmmm
[11:13] <mvo> is the version on launchpad ok?
[11:13] <alex-weej> the version on launchpad?
[11:14] <alex-weej> i'm sorry i only see a package for feisty on launchpad
[11:17] <mvo> alex-weej: I mean, the patch you added on LP is ok? its different and all?
[11:17] <alex-weej> that would have been a pretty big error on my half if i uploaded the old version... let's see
[11:18] <alex-weej> mvo: no it's right: http://launchpadlibrarian.net/8822330/01_ubuntu_theme.patch
[11:18] <alex-weej> bug is https://bugs.launchpad.net/ubuntu/+source/notification-daemon/+bug/132512
[11:18] <mvo> alex-weej: ok, then it was my bad :( sorry for that, I will do a new version tomorrow
[11:18] <ubotu> Launchpad bug 132512 in notification-daemon "New pie chart code for the Ubuntu Notification Daemon theme" [Undecided,Fix released]
[11:18] <alex-weej> mvo: no problem
[11:46] <bo0bi3> hey ro0m
[11:52] <calc> asac: tested tribe-4
[11:53] <calc> asac: its still hosed, i'm starting to think its the kernel
[11:53] <asac> calc: so wpa psk still doesn't work?
[11:53] <asac> or open net?
[11:53] <calc> asac: i tested using a recompiled version of feisty wireless-tools and wpasupplicant and even then it wouldn't work
[11:53] <calc> on an open net
[11:53] <calc> didn't work for a aes wpa2 either
[11:53] <asac> ok
[11:53] <asac> open net is known to be broken
[11:53] <calc> tribe-4 as is didn't work either
[11:54] <calc> for me to test the kernel though means i will need to actually install it (ugh) ;)
[11:54] <asac> so far i have received just one negative on wpa with broadcast ssid
[11:54] <asac> calc: http://ipw3945.sourceforge.net/
[11:54] <asac> read changes 1.2.1
[11:54] <asac> (we have 1.2.0)
[11:54] <asac> i think that will cure the open net scenario
[11:54] <ajmitch> asac: has this only been with ipw3945 so far?
[11:54] <asac> * Fix driver not make associate request when required
[11:54] <asac> * Fix iwconfig essid any doesn't associate problem
[11:54] <calc> asac: i also completely firmware reset both of my routers today for other reasons, so it shouldn't be an issue with them
[11:54] <asac> ajmitch: most issues we have are ipw3945
[11:55] <ajmitch> asac: ok, my ipw2200 problems may be different then :)
[11:55] <calc> asac: are we able to get an updated ipw3945 driver?
[11:55] <ajmitch> given that I was able to associate & get an ip address a couple of times
[11:55] <asac> ajmitch: i want to hear as much info as possible
[11:55] <calc> ajmitch: maybe... we don't know what is the causing the problem yet though
[11:55] <calc> ajmitch: i can occassionally get an address, but not today
[11:56] <calc> ajmitch: its very uncommon for me to get an address under gutsy though
[11:56] <ajmitch> asac: at one point it was just repeatedly asking for the key, I haven't often been using my laptop at home though
[11:56] <asac> calc: I asked a few days ago in #ubuntu-kernel on how to prepare a test-package, but didn't get an answer
[11:56] <calc> ajmitch: seen that myself under gutsy tribe3 also
[11:56] <ajmitch> it had been very stable until recently
[11:56] <asac> calc: i will try mailing-list after feature-freeze
[11:56] <calc> should i be able to run the old feisty kernel on gutsy still?
[11:56] <calc> if so i can try doing that on this box
[11:56] <ajmitch> though my laptop went about 4-5 weeks without a dist-upgrade
[11:56] <asac> ajmitch: thats hard to say then
[11:57] <ajmitch> asac: I can test again tonight
[11:57] <asac> ajmitch: a tighter regression window would be more helpful
[11:57] <asac> ajmitch: can you try to downgrade if you see the issues with latest?
[11:57] <ajmitch> which part? kernel, n-m?
[11:57] <asac> nm
[11:57] <asac> until you find that it works
[11:57] <ajmitch> ok
[11:57] <calc> too bad there isn't a way to install gutsy at a day granularity to go back and find when it broke
[11:57] <calc> would take a lot of disk space to keep that many debs around though
[11:58] <asac> calc: i think with vmware you could do daily snapshots
[11:58] <stgraber> asac: are you sure we are running 1.2.0 in current Gutsy ? (modinfo tell me : version:        1.2.1mp
[11:58] <stgraber> )
[11:58] <calc> i couldn't compile old nm on gutsy, but it fails with old wireless-tools/wpasupplicant even at the ifup level
[11:58] <stgraber> (and crappy copy/paste as usual)
[11:58] <calc> asac: how would i get the old daily snapshots though?
[11:58] <asac> stgraber: i am not 100% sure ... from what i know we have 1.2.0 + a backport of the security issue fixed in 1.2.1
[11:58] <calc> asac: i mean going back in time and getting old gutsy debs to track it down
[11:59] <asac> calc: you can manually get them from launchpad iirc
[11:59] <stgraber> oh, I would need to give 1.2.2 a try when I have a moment then
[11:59] <calc> asac: that would be very time consuming in case the problem isn't something we think it is
[11:59] <asac> calc: which version did you try to compile?
[11:59] <asac> stgraber: you sure 1.2.1 is 1.2.1?
[11:59] <guignome> a filesystem with versioning could maybe do that
[12:00] <calc> 0.6.4-6ubuntu7 <- i think it was that one
[12:00] <calc> i just recompiled current gutsy against old libiw since it didn't work
[12:00] <stgraber> asac: no, that's what modinfo tell me but the kernel guys can show whatever they want :)
[12:00] <asac> stgraber: yes ... from what source is that shipped from again?
[12:00] <calc> you know i'm going to verify that using ifup works on the feisty cd also
[12:00] <asac> stgraber: let me look into that changelog again
[12:00] <calc> since i haven't tested that yet
[12:01] <mdke> is the current daily-live reasonably usable?
[12:01] <mdke> anyone know?
[12:01] <stgraber> asac: it's in : linux-ubuntu-modules-2.6.22-8-generic
[12:02] <calc> i'll be back in a few minutes, verifying that feisty cd works like i expect it to
[12:02] <asac> stgraber: thanks ... with s/-8-/-9-/ it works :)
[12:03] <asac> stgraber: hmm according to changelog of that its 1.2.1
[12:03] <asac> maybe 1.2.0 fixes things for us ;)
[12:04] <stgraber> asac: with -9 I have no suspend to ram :)
[12:04] <Lure_> asac: anything else I can do to help solve bug 126494 ?
[12:04] <ubotu> Launchpad bug 126494 in network-manager "wired network shown as disabled after boot" [Undecided,New]  https://launchpad.net/bugs/126494
[12:04] <asac> stgraber: if i read the changes for 1.2.1 on http://ipw3945.sourceforge.net/ they just look too much related to be a coincident
[12:05] <asac> 1. Fix driver not make associate request when required
[12:05] <asac> ...
[12:05] <asac> n. Fix hardware/software RF kill switch problem during module loading time
[12:05] <asac> i mean it reads like i read reversed bugs here ;)
[12:06] <stgraber> :)
[12:06] <asac> in about box on that page it reads:
[12:06] <asac> (any version ending in .0 is 'stable')
[12:06] <asac> maybe we are not supposed to use 1.2.1?
[12:08] <stgraber> asac: what's feisty's version ?
[12:08] <stgraber> asac: 1.2.0 ?
[12:09] <asac> 1.2.0mp
[12:09] <asac> however i always received claims that feisty stopped to work with some upgrade
[12:10] <asac> s/always/also/
[12:11] <asac> stgraber: can you try?
[12:12] <stgraber> I'd need a livecd with latest feisty kernel on it to test
[12:12] <asac> maybe you can build modules with old ipw?
[12:13] <asac> in gutsy?
[12:14] <calc> asac: disregard my earlier report, i determined i was doing something wrong with feisty cd, testing on gutsy again now


[20:19] <thumper> morning
[22:15] <veebers> wallyworld, babbageclunk: What else do I need for a test, I'm getting no test to run: https://paste.ubuntu.com/p/ZMWFtBZtkP/
[22:16] <babbageclunk> veebers: is that in a new package?
[22:16] <veebers> babbageclunk: aye
[22:16] <babbageclunk> you'll probably need a package_test.go
[22:17]  * thumper was going to say that
[22:17] <veebers> babbageclunk: ah right, I'll give that a whirl. Cheers
[22:17] <thumper> we started the pattern of doing the setup of tests for packages in their own file
[22:17] <thumper> veebers: there are two different ones
[22:17] <thumper> one if you need mongo, and a different way if you don't
[22:17] <babbageclunk> veebers: look at core/auditlog for a trivial one.
[22:18] <veebers> sweet, cheers guys. Should be pretty simple as there is no deps needed (it's a simple test :-))
[22:20] <veebers> babbageclunk, thumper sweetbix that works. \o/
[22:32] <thumper> veebers: just changed our 1:1 from hangout to meet
[22:32] <veebers> thumper: ack, I'll re-join
[23:51] <thumper> wallyworld: could I get you to triage bug 1778033 as you have been in storge recently?
[23:51] <mup> Bug #1778033: juju stuck attaching storage to OSD <4010> <juju:New> <https://launchpad.net/bugs/1778033>
[23:51] <wallyworld> ok


[00:48] <cvance> I installed mythbuntu 16.04 but cannot get mythbackend to listen on a different ip. In setup, I set the ip to the address of the interface, but according to netstat, it's only listening to <IP_ADDRESS>:6543 and 6544
[01:02] <cvance> solved, it was only binding to the ipv6 address, not ipv4. had to disable ipv6
[13:24] <qwebirc25909> Configuring a new MythBuntu in a VmWare image. The resolution on the desktop is only 800x600, and this is too low to work properly in the MythTv Setup application. Need hints on how to change the resolution