[02:55] <TheMuso> crimsun: Any more feedback re the moving of the pulseaudio Xsession.d script to an earlier start point?
[02:56] <crimsun> TheMuso: a couple more positive acks, but I'd like additional testing.  In a few minutes, I'm going to send an e-mail to u-d-d and u-u
[02:56] <TheMuso> crimsun: ok
[02:57] <TheMuso> at this stage it will probably have to ben an SRU.
[02:57] <crimsun> TheMuso: sure
[03:47] <superm1> crimsun, what about that g-s-r patch? you mentioned about pushing it to a PPA to test w/ pulseaudio some time last week
[03:49] <crimsun> superm1: no, I was referring to an alsa-plugin patch.  I'll dig it up now.
[03:50] <superm1> crimsun, ah
[03:50] <crimsun> alsa-plugins*
[04:29] <superm1> pitti, given https://bugs.edge.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/263097/comments/23, perhaps it would be worthwhile to add a third type of quirk to handle this behavior at some point
[06:35] <pitti> Good morning
[06:35] <StevenK> Morning pitti!
[06:35] <pitti> hey StevenK!
[06:36]  * StevenK waits for i386 to dip below 50 builds
[06:36] <pitti> wow, it built faster than I thought
[06:37]  * slangasek waves
[06:40] <wgrant> Wow, it looks like it's going to not finish too late.
[06:44] <pitti> superm1: oh, thanks for pointing out
[06:44] <pitti> superm1: but didn't you say that loading b44 and wl wouldn't work at the same time?
[06:50] <superm1> pitti, strictly because of the order it's loaded
[06:50] <pitti> superm1: I just posted a followup question; but if that actually works, it would be much better, yes
[06:50] <superm1> pitti, if you load wl before ssb and b44, you can apparently have it functional
[06:50] <pitti> superm1: so for that we should put wl into /etc/modules then
[06:50] <pitti> superm1: and could forget about all the blacklisting stuff?
[06:50] <superm1> pitti, well unfortunately that wouldn't solve it
[06:51] <superm1> pitti, ssb still loads from initramfs
[06:51] <pitti> superm1: doesn't /etc/modules either?
[06:51] <pitti> ah, maybe not
[06:51] <superm1> pitti, wl isn't available in the initramfs since it's restricted anyhow
[06:52] <superm1> I think the workaround that should work in this case would be in jockey when detecting b44 on the system, still blacklist ssb/b43/b44, but have a modprobe option to reload b44 after inserting wl
[06:53] <superm1> that's similar to what i've seen in the various forum postings that i've seen talking about it at least
[06:53] <pitti> ah, good idea
[07:01] <lool> Morning
[07:02] <StevenK> Ah ha. i386 has less builds than hppa
[07:02] <lool> hppa had many give backs, it's laging a lot
[07:02] <pitti> hey lool
[07:04] <StevenK> lool: hppa has been at 20/21 builds for the majority of the day, i386 has been dealing with a ~ 400-odd backlog of langpacks
[07:07] <StevenK> I think kohnen has choked on gstreamer0.10, too
[07:14] <dholbach> good morning
[07:16] <StevenK> Woot. i386 is all done
[07:18] <persia> Does that mean it's time for the big shiny red button?
[08:05] <pitti> lool: are you more happy with obm now?
[08:06] <lool> pitti: I don't know for sure; I'd be more confortable if some security people could have a quick look
[08:06] <lool> pitti: You qualify though :)
[08:07] <lool> PHP isn't particularly well seen these days, and even if at some places the coding was ok or even nice, some things were quite surprizing
[08:19] <pitti> dendrobates, zul: do you want to have obm in main for intrepid? is the server team committing to invest the necessary maintenance into it? (eww PHP webapp)
[08:26] <slangasek> pitti: isn't it a bit late to be making such changes?
[08:27] <pitti> slangasek: that, too
[08:29] <dholbach> seb128: boohoooooooo, they rejected the epiphany-extensions upload I sponsored :'-(((
[08:29] <seb128> dholbach: oh, why?
[08:29] <dholbach> no idea
[08:29] <slangasek> because it's past the deadline
[08:29] <seb128> it's not on the CD
[08:30] <slangasek> is it on the DVD?
[08:30] <seb128> dunno
[08:30] <seb128> so it's too late for any upload now?
[08:30] <slangasek> any non-critical uploads, yes
[08:31] <seb128> slangasek: http://bugzilla.gnome.org/attachment.cgi?id=121349&action=view to fix a frequent evolution crasher would be accepted?
[08:32] <slangasek> how frequent?  I don't see a targeted bug for it in Ubuntu
[08:32] <seb128> slangasek: bug #287136
[08:34] <seb128> does anybody know how the xorg default keymap is set?
[08:35] <slangasek> in /etc/default/console-setup
[08:36] <seb128> slangasek: but is upstream xorg using that or do we have some trick calling setxkbmap using the values there?
[08:36] <slangasek> oh
[08:36] <slangasek> no idea
[08:36] <seb128> slangasek: I'm trying to debug bug #275957
[08:37] <seb128> slangasek: that happens 100% of the time on french installations
[08:38] <slangasek> 275957 does?
[08:38] <seb128> yes
[08:38] <slangasek> ...gar
[08:38] <lool> Indeed, I just got a crash, but then was able to type password and unlock ss
[08:38] <seb128> slangasek: I've been discussing it with upstream on gnome bug #553915
[08:39] <seb128> he thinks the xorg config is really weird and I was asking how we are setting the keyboard config if it's not in xorg.conf
[08:39] <seb128> lool: luck you, for most people the dialog is not showed
[08:39] <slangasek> seb128: bug #287136> if that's a confirmed fix for the bug and you can upload in the next 30 minutes, yes
[08:39] <seb128> slangasek: ok doing that now then
[08:40] <seb128> slangasek: are you sure e-e can't be accepted in the basis it's a GNOME 2.24.1 update and is not on the CD? ;-)
[08:40] <seb128> weird
[08:40] <seb128> calling "setxkbmap -model pc105 -layout fr -variant oss -option ''" workaround the crasher
[08:41] <seb128> it should be the same config than the default one
[08:41] <pitti> hey mvo, good morning
[08:42] <pitti> mvo: any idea about bug 135752 ?
[08:44] <slangasek> seb128: grmbl; accepted, since we're waiting for evolution anyway
[08:44] <mvo> pitti: this should be fixed with the latest upload in the sense that a dialog will pop up and ask for a network update
[08:44] <slangasek> (which doesn't make me happy, either)
[08:44] <seb128> slangasek: thanks
[08:44] <mvo> pitti: but let me test
[08:44] <slangasek> mvo: you saw the latest follow-up, reopening that bug?
[08:46] <pitti> slangasek: ok, I'll reject human-theme then and reupload as an SRU
[08:47] <slangasek> pitti: I think that's better for the case of a theme change this late, yes
[08:47] <mvo> slangasek: hrm, that is bad :(
[08:47] <slangasek> yep
[08:48] <slangasek> if it was good, we wouldn't need to talk about it on release week ;)
[08:49] <asac> superm1: could you set your nm branch to "merged" so it disappears from the active branch list? thanks!
[08:54] <seb128> slangasek: evolution uploaded now
[08:56] <mvo> Mirv: are you there? could you give me the output of "ls -l /var/lib/apt/lists/" on a fresh networkless install please?
[09:01] <mvo> slangasek: in my artificial test setup the dialog comes up jsut fne, I'm doing a fresh install now to figure out what is wrong
[09:01] <slangasek> ok
[09:01] <Mirv> mvo: not fresh since I did apt-get update already
[09:02] <mvo> thanks Mirv
[09:14] <seb128> cjwatson: hi, do you know how the xorg keymap is set exactly?
[09:19] <cjwatson> seb128: /etc/default/console-setup and a hal thingy that reads from it
[09:20] <seb128> cjwatson: whatever is setting the keymap is xorg upstream code or some ubuntu trick?
[09:20] <cjwatson> seb128: this is different from upstream; I wouldn't expect them to be familiar with it
[09:20] <seb128> cjwatson: trying to debug gnome bug #553915
[09:20] <cjwatson> seb	/usr/share/hal/fdi/policy/10osvendor/10-x11-keymap.fdi
[09:20] <seb128> cjwatson: svu who is the upstream for xkeyboard-config, libgnomekbd would like to get details on how we set the keymap because he says there is something weird there
[09:21] <cjwatson> and /usr/lib/hal/debian-setup-keyboard
[09:22] <cjwatson> it's just a bunch of hal-set-property calls to make the console and X keymaps sync up
[09:22] <seb128> looks like that will not be easy to debug
[09:22] <seb128> using setxkbmap works correctly and fixes the crash
[09:22] <cjwatson> you should be able to replicate the same thing by putting equivalent Xkb* settings in xorg.conf
[09:22] <cjwatson> unless it's a bug in the hal glue in X itself I suppose
[09:23] <seb128> well, passing the same options to setxkbmap doesn't lead to a broken config
[09:23] <seb128> I'll try to edit xorg.conf directly
[09:23] <seb128> the issue leads to bug ##275957
[09:23] <seb128> which is gnome-screensaver-dialog crashing in some locales
[09:24] <seb128> which means you can't unlock your screen
[09:24] <seb128> anyway thanks for the info, will try to continue debugging based on that
[09:25] <fta> seb128, is it too late for a bug fix ? (totem-plparser)
[09:25] <Mirv> mvo: http://paste.ubuntu.com/63164/
[09:25] <dendrobates> pitti: let me talk to zul.  The push for obm in main isn't coming from me.
[09:25] <Mirv> I've now also a snapshot saved straight after install
[09:26] <seb128> fta: likely, you can ask to slangasek but only bugs important for the CD images now should be fixed, I guess a totem-pl-parser fix is rather sru material now
[09:26] <fta> seb128, ok, thanks
[09:26] <seb128> fta: what is the fix about exactly?
[09:27] <fta> seb128, bug 251669
[09:27] <seb128> fta: right, not an intrepid blocker issue
[09:27] <fta> very low risk, but high annoyance if not fixed
[09:27] <mvo> slangasek: fix is ready, will upload in 5min
[09:27] <slangasek> mvo: ok, thank you
[09:28] <slangasek> fta: --> SRU, sorry
[09:28] <slangasek> pitti: I thought the justification for allowing openoffice.org-emailmerge into main was that python-uno was already on the CDs?
[09:29] <slangasek> pitti: it wasn't on the CD for RC
[09:31] <slangasek> pitti: can we trim that back out again and reclaim 100K?
[09:35] <fta> slangasek, so nomination to intrepid-updates + sub ubuntu-sru ?
[09:35] <slangasek> pitti: hmm, need more drastic cuts than that though, so let's skip that one for now
[09:36] <slangasek> fta: https://wiki.ubuntu.com/StableReleaseUpdates
[09:37] <pitti> slangasek: hm, I checked the manifest files and found it there, weird
[09:38] <pitti> slangasek: but yes, if it causes any trouble, let's cut it
[09:38] <slangasek> pitti: ah, it might have been there for desktop but not for alternate
[09:38] <slangasek> that's fine, it's alternate that's oversized and we have langpacks to play with there
[09:38] <pitti> slangasek: right, I just checked desktops; but weird
[09:39] <pitti> slangasek: let's hope that the new langpacks don't grow the next desktops...
[09:39] <slangasek> we can hope that it really was just KDE stuff missing
[09:39] <pitti> slangasek: alternates> want me to look for a package which lzma's well? or just cut langpacks?
[09:40] <mvo> Mirv: when you select finish as default language, are there any language packs/language-support packages installed (I guess not because they are not on the CD)?
[09:42] <slangasek> pitti: just cut langpacks; it's late to be rebuilding packages
[09:44] <mvo_> Mirv: hm, did my last msg made it to you before I disconnected?
[09:46] <pitti> mvo_: yes
[09:46] <pitti> mvo_: no answer from Mirv yet
[09:46] <pitti> hey robbiew
[09:47] <robbiew> howdy
[09:50] <pitti> slangasek: hm, you did zh->ja for i386, but didn't cut amd64; I'll drop -de from amd64, ok?
[09:50] <slangasek> pitti: already done && committing
[09:50] <pitti> ah, good
[09:52] <directhex> hm, intrepid's wallpaper is less neat than the vector heron for hardy
[10:14] <directhex> oh, wait, the eta wallpaper sucked. running a dist-upgrade, it suddenly looks neato
[10:23] <cjwatson> seb128: does bug 288494 need a hardy task, while we remember?
[10:32] <seb128> cjwatson: right, I added an hardy task now
[10:34] <cjwatson> thanks
[10:43] <pitti> sistpoty|work: hey
[10:44] <geser> Hi sistpoty|work
[10:44] <pitti> sistpoty|work: I threw away your u-d-a@ email, since it is not relevant any more, FYI; if you send something to u-d-a@, please ping a moderator immediately
[10:46] <pitti> mvo: I figure we can bin bug 241431 now?
[10:51] <mvo> pitti: I think so :)
[10:51] <pitti> mvo: sorry, seems you are the target of all my woes today ... u-n complains about package information being 10 days old; howver, I have the daily cronjob, and did an explicit update 10 minutes ago; want a bug report for that? or known?
[10:51] <pitti> mvo: 241431> yep, closed
[10:51] <mvo> pitti: do you have a entry in your sources.list that causes it to issue a warning or a error?
[10:51] <mvo> pitti: it only updates if the update is complettely successful
[10:52]  * pitti does an apt-get update by hand
[10:52] <mvo> pitti: (there is a bug about this open that it should print both the last successful one and the last not-fully successful one
[10:52] <mvo> )
[11:09] <sistpoty|work> hi pitti and geser
[11:09] <sistpoty|work> pitti: ah, k... thanks... didn't know you were a moderator as well
[11:11] <pitti> sistpoty|work: a bunch of people are; cjwatson, mdz, me, slangasek, probably more
[11:11] <sistpoty|work> pitti: good to know, thanks... back then I only pinged the first two
[11:12] <pitti> sistpoty|work: ah, so you did? ok; wasn't sure whether you were aware of moderation at all
[11:14] <Mirv> mvo: hi. only English langpacks, no else.
[11:16] <Mirv> (and English language-support-en)
[11:17] <jibel> Hi all, has anyone bug 289091 on it's radar ?
[11:17] <jibel> doko: You're around ?
[11:17] <cjwatson> jibel: you aren't the first to raise it
[11:18] <jibel> s/it's/his/
[11:18] <cjwatson> it's on the release team's radar
[11:18] <jibel> cjwatson: ok, just worrying because dups are increasing quickly.
[11:19] <slangasek> jibel: under what circumstances did you encounter this bug?
[11:22] <cjwatson> liw: what happened to moving system-cleaner to system->administration?
[11:23] <cjwatson> liw: does this just need sponsorship?
[11:23] <jibel> slangasek: referring to duplicates, most of them occurs when installing ca-certificates-java during a dist-upgrade.
[11:23] <slangasek> jibel: a dist-upgrade from what?  A previous version within intrepid?
[11:24] <jibel> slangasek: sorry, hardy to intrepid
[11:24] <slangasek> ok
[11:24]  * Hobbsee notes those files exist in the hardy version of ca-certificates (whcih is a dep), but not the intrepid version
[11:25] <liw> cjwatson, it's part of a set of changes I'll want to include in intrepid, the others being the name change and translations; I'm reviewing all the new bugs that came during the weekend to see if there's anything else, and then I'll prepare a package and ask for review+sponsorship
[11:25] <cjwatson> liw: if you want to include it in intrepid, it needs to be RIGHT NOW
[11:25] <cjwatson> make a fuss if you need something included
[11:25] <liw> cjwatson, ack
[11:27] <cjwatson> liw: what can I do to make this go faster?
[11:28] <liw> cjwatson, give me 15 minutes?
[11:28] <cjwatson> ok
[11:30]  * Hobbsee offers cjwatson a lighter
[11:32] <cjwatson> Hobbsee: ?
[11:34] <Hobbsee> cjwatson: setting people on fire can make them go faster?
[11:34] <cjwatson> oh :)
[11:34] <Hobbsee> cjwatson: no, i know you don't smoke :)
[11:37] <mvo> Mirv: thanks, that will be jaunty material, but should be fixed early IMO - please nag me about it
[11:49] <pitti> mvo: oh, as for your question, apt-get update doesn't complain about anything; I have some PPAs, though
[11:52] <mvo> pitti: could you give me the output of "ls -l /var/lib/apt/periodic" please ?
[11:53] <pitti> -rw-r--r-- 1 root root 0 2008-10-26 09:58 update-stamp
[11:53] <pitti> -rw-r--r-- 1 root root 0 2008-10-17 08:40 update-success-stamp
[11:54] <mvo> pitti: and the output (full) of "sudo apt-get update -o Debug::acquire::http=true" please?
[11:54] <pitti> mvo: is anyone using ubuntu-vm-builder in hardy-proposed? there's a plethora of pending fixes in the current SRU
[11:54] <pitti> mvo: coming
[11:55] <mvo> pitti: not sure, the trouble iwht it was that one of the previous versions had a regression, but I fixed that
[11:55] <C0p3rn1c> ﻿would it be possible to develop a open driver standard that all operating system could use and incorperate into there OS?
[11:55] <pitti> mvo: http://pastebin.com/f3a1c6b0
[11:56] <cjwatson> C0p3rn1c: we're very close to release and dealing with urgent issues here. I'm afraid this is not the place for bluesky discussions
[11:56] <pitti> C0p3rn1c: not all OSes, but we are working on establishing one for the Linux world
[11:58] <C0p3rn1c> pitti, nice! but most drivers are available on windows and the EU could force microsoft to join this standard
[11:58] <C0p3rn1c> hypothetically speaking
[11:59] <wgrant> I don't think 4 days before the release is the time for hypothesising about such things.
[12:00] <C0p3rn1c> ﻿imho this is the only reason that linux in general hasnt really breaked though to the main public
[12:00] <Hobbsee> and still, completely the wrong place and time for this discussion.
[12:01] <C0p3rn1c> k sorry to disturb you
[12:01] <pitti> seb128: argh, bug 204770 was still not applied to intrepid :(
[12:01] <danbh_intrepid> C0p3rn1c: join #ubuntu-offtopic, and Ill try to dredge up a link
[12:03] <seb128> pitti: ups
[12:08] <mvo> pitti: could you please check if you have a file "/etc/apt/apt.conf.d/20packagekit" ? I think that kills it
[12:08] <mvo> pitti: it == the update-stamp
[12:08] <pitti> mvo: yes, I have that
[12:09] <slangasek> liw: how's system-cleaner coming?
[12:09] <mvo> pitti: ok, if you remove that, it should work again, I check now for a fix
[12:09] <pitti> mvo: if I run that command from a shell, it succeeds
[12:09] <liw> slangasek, running into packaging problems, but should be done momentarily
[12:09] <slangasek> ok
[12:10] <pitti> mvo: right, if I move it away, update-success-stamp is current
[12:10] <pitti> mvo: rock, thanks
[12:23] <liw> cdbs isn't running my makefile by default in build; how can I make it happen?
[12:23] <StevenK> Are you including makefile.mk?
[12:23] <liw> no
[12:23] <StevenK> Then that's probably why it isn't. :-)
[12:24] <liw> debian/rules:5: /usr/share/cdbs/1/rules/makefile.mk: No such file or directory
[12:24] <liw> oh, class
[12:24] <StevenK> It's a class
[12:24] <StevenK> liw: :-)
[12:25] <pitti> ogra: is bug 199675 fixed in intrepid? (was a hardy SRU)
[12:26] <ogra> pitti, well, throught not using an xorg.conf by default anymore, but parts of the breakage are usolvable by design in the script ... some of these parts are not yet replaced completely in new Xorg so in some circumstances you still have to use the script and have to deal with the issues
[12:27] <pitti> ogra: but is the fix which got applied in hardy-proposed applied to intrepid, too?
[12:28] <liw> bzr: ERROR: Pack 'ed385405e56c3ed9703f02a0f2638f20' already exists in <bzrlib.repofmt.pack_repo.RepositoryPackCollection object at 0x324ce90> -- hrmphgh
[12:29] <ogra> pitti, apart from the xkb options (which are used via a different way anyway now by using xsetxkbmap in the login manager after X is up), yes
[12:30] <pitti> ogra: so, so it can be closed in intrepid, too? (or if there is still an issue, the hardy task be reopened as well)
[12:30] <ogra> pitti, it should be closed and if only to make jwz file separate bugs :P
[12:31] <pitti> ogra: ok, please do that then :)  thanks for the update
[12:32]  * ogra sets it to wontfix in intrepid
[12:35] <slangasek> liw: is that bzr error blocking your upload?
[12:35] <liw> slangasek, no, just pushing it
[12:36] <liw> ok, it's on my PPA, now I need a sponsor and a release team acceptance
[12:37] <slangasek> can you give me a full url for grabbing it?
[12:37] <liw> slangasek, cjwatson: ping -- 1.10.4-0ubuntu1 on https://launchpad.net/~liw/+archive (https://launchpad.net/%7Eliw/+archive/+files/system-cleaner_1.10.4-0ubuntu1.dsc)
[12:37] <liw> that was a very long fifteen minutes :(
[12:37] <slangasek> yoink
[12:42]  * directhex claps
[12:43] <directhex> intel wifi link 5100 support in intrepid?
[12:43] <directhex> i thought those drivers only existed about 3 weeks ago in a private git tree
[13:00] <slangasek> liw: what's this line?  Not mentioed anywhere in the changelog, that I can tell: +       self.apt_cache._depcache.ReadPinFile("/var/lib/synaptic/preferences")
[13:02] <liw> slangasek, oh. that reads in Synaptics "Lock package" settings, in an effort to have cruft-remover not remove locked packages; it doesn't seem to have any effect either way, though; probably should not have been included in trunk yet
[13:02]  * liw goes review the entire commit log since the previous release
[13:02]  * wgrant curses people confusing package managers with touchpad manufacturers.
[13:03] <liw> s/cs/c's/
[13:04]  * liw notices himself typing Internetese, where apostrophes are optional
[13:04] <wgrant> Ah.
[13:04] <slangasek> liw: have you tested what happens if /var/lib/synaptic/preferences doesn't exist?
[13:05] <liw> slangasek, I think I did (=> nothing happens), but let me make sure
[13:06] <liw> slangasek, works fine
[13:06] <slangasek> ok
[13:07] <slangasek> sponsoring
[13:09] <liw> slangasek, whew
[13:10] <slangasek> liw: uploaded; now, do you want me to tell you about the bug I think I found that I didn't stop to let you fix, or would you prefer to not know? ;)
[13:10] <liw> slangasek, do tell
[13:10] <slangasek> liw: no upgrade handling to migrate /var/lib/system-cleaner to /var/lib/cruft-remover
[13:11] <liw> slangasek, oh, you're right. should I fix that for the release? the minimal change would be to move the file in question in postinst, I guess
[13:11] <slangasek> not for release
[13:12] <slangasek> I think it should be cleaned up down the line; at this point it might as well be an rm -rf /var/lib/system-cleaner on upgrade, once this version hits people's systems
[13:12] <liw> slangasek, ok, I'll file a bug so I don't forget
[13:13] <slangasek> (example of why not to change names around at the last minute, though...)
[13:13] <liw> slangasek, yeah
[13:23] <abogani> superm1: Are you around? May i disturb you for a minute about bug 286961?
[13:34] <cjwatson> top tip: turns out that if you try to zero out the boot sector by zeroing the first 512 bytes of a disk, it zeroes the partition table too. who'd'a thunk it.
[13:34]  * cjwatson hits self
[13:37] <liw> cjwatson, heh, to zero out the partition table is the usual reason why I do that
[13:38] <cjwatson> in this case it was because there was an old boot sector interfering with usb-creator
[13:38] <cjwatson> (I speculate)
[13:38] <mok0> cjwatson: what tool did you use? dd? Just curious
[13:38] <cjwatson> yes
[13:39] <mok0> uh-uh
[13:39] <cjwatson> (I don't need help, I was just being an idiot)
[13:39]  * Hobbsee hands cjwatson a large cup of coffee
[13:39] <Hobbsee> or should that be beer?
[13:39] <liw> is there another non-interactive command line tool for zeroing out the partition table (and just that)?
[13:39] <mok0> cjwatson: did you save a copy of the 512 bytes?
[13:39] <ogra> Hobbsee, to early for beer yet :)
[13:40] <cjwatson> mok0: no. it's not hard to just rerun usb-creator
[13:40] <Hobbsee> ogra: but it's gone lunchtime!
[13:40] <ScottK> ogra: It's always after 5PM somewhere.
[13:40] <ogra> Hobbsee, true, but we need cjwatson sober in that pre-release wrangling ;)
[13:40] <Hobbsee> ogra: that depends.  Does he make better decisions when sober?
[13:40] <Hobbsee> ;)
[13:41] <cjwatson> history suggests yes
[13:41] <cjwatson> for which I am rather grateful
[13:41] <mok0> cjwatson: usb-creator?
[13:41] <Hobbsee> hmm, OK, better be the coffee, then.
[13:41] <cjwatson> mok0: apt-cache show usb-creator
[13:41] <cjwatson> i.e. the tool I am currently testing
[13:41] <mok0> cjwatson: hmm, not in hardy
[13:41] <cjwatson> mok0: indeed
[13:41] <cjwatson> that's sort of why I'm testing it
[13:42]  * mok0 is chicken not to update production workstation
[13:44] <ScottK> mok0: If it's Kubuntu then you're not chicken.  I recommend working with the live CD to see if KDE4 has what you need (I find it does, but some won't).
[13:45] <directhex> my boss now has a fresh intrepid RC on his new laptop
[13:45] <mok0> ScottK: I've been running kde4 for some time, now. I like it a lot
[13:45] <directhex> it worked better than hardy did
[13:45] <abogani> superm1: The fourth comment is sufficient to put the fix for 286961 into SRU queue?
[13:45] <ScottK> mok0: Great.  I just warn people because there are still some things that KDE3 can do that KDE4 doesn't.  I like it a lot too.
[13:46] <mok0> ScottK: Is the intrepid kde4 version newer than the ppa version?
[13:47] <ScottK> mok0: They are both 4.1.2, but there are differences in the packaging.  I've never run the Hardy KDE4, so I can't tell you what.
[13:47] <ScottK> mok0: We could do with PPA -> Intrepid upgrade testing if you want to join us in #kubuntu-devel.
[13:47] <mok0> ScottK: Oh? I thought the ppa was a "preview" of the intrepid packages
[14:16] <Plagman> hi there
[14:17] <Plagman> do you guys know how to get the exact CFLAGS that were used to compile the repo binaries from the source packages?
[14:17] <Plagman> I got the source package, now I guess there's some kind of script to build it exactly as it was built for the repositories?
[14:19] <directhex> Plagman, there are no global cflags. anything not explicitly set in the debian/rules of a given package is just gcc default
[14:21] <Plagman> cool; debian/rules is what I was looking for
[14:21] <Plagman> thanks, directhex
[14:21] <directhex> debian/rules is the makefile used for package building
[14:25] <Plagman> alright
[14:25] <Plagman> thanks a lot
[14:27] <NCommander> hey directhex
[14:27] <directhex> mornin' NCommander
[14:28] <directhex> well. afternoon
[14:28] <directhex> close enough
[14:31] <superm1> abogani, have you gotten verification that actually will work (other than just compile)?
[14:32] <abogani> superm1: No
[14:32] <superm1> abogani, can you post the results of that debdiff to a ppa and ask the reporter to test it?
[14:33] <abogani> superm1: Ok
[14:33] <superm1> abogani, i'd prefer that we know it will be working
[14:33] <superm1> thanks
[14:33] <abogani> superm1: I understand. Thanks to you, Mario.
[14:37] <Plagman> I need a word with whoever is maintaining the X server package
[14:40] <Mirv> liw: jipii, now it works: https://translations.launchpad.net/ubuntu/intrepid/+source/system-cleaner/+imports
[14:41] <liw> Mirv, cool
[14:41] <Mirv> liw: it means that full translations can eventually be supplied via updated language packs
[14:41] <liw> Mirv, very cool
[14:42] <superm1> Plagman, you'd be best off joining #ubuntu-x and posing your question there.  they might be afk right now, but idle in there and they will see it eventually
[14:42] <Plagman> alright, thanks
[14:43] <slangasek> superm1: mythbuntu alternate candidates for final are posted
[14:43] <superm1> slangasek, okay great thx
[14:47] <superm1> pitti, re that comment i made earlier, here's the exact workaround that has been posted a few times for when b44 is in the mix: http://ubuntuforums.org/showpost.php?p=6042421&postcount=13
[15:18] <heno> *** alternate and some desktop candidate images (for 8.10 final) are up on http://iso.qa.ubuntu.com/ Please help test them - join us in #ubuntu-testing to coordinate ***
[15:28] <rtg> superm1: no joy with 'alsamixer -c0'. Though it shows the discrete controls, adjusting them has no effect on audio output.
[15:32] <Keybuk> I finally fix xchat-gnome's most annoying misfeature (that the notification icon goes away when you focus, even if you don't read the message) and I can't test because the network is down :o(
[15:45] <Keybuk> asac: why does NM always pick exactly the wrong network in Millbank
[15:46] <Keybuk> does it rste by signal strength, or just pick alphabetically?
[15:47] <Company> so who here is at fault for ubuntu getting slower?
[15:48] <broonie> It's certainly not alphabetic from the looks of it.
[15:50] <ogra> Company, i heard its all swfdec's fault
[15:50] <Company> ogra: ha, i made sure it's none of my software
[15:50] <Company> ogra: apart from the gtk benchmarks, the radiobuttonthing might have been...
[15:51] <ogra> Company, truely i think its the kernel and its an upstream thing ... i'm pretty sure they'll find the same comparing FC7 with FC10
[15:51] <Company> ogra: yeah, i'm not blaming you guys - i just thought you'd have an idea who we should kick
[15:52]  * Company only kicks cairo people all the time
[15:53] <ogra> i heard something about linus' scheduler implemntation decisions a while ago that were known to make it a bit slower but had more stable code or some such
[15:54] <ogra> but i might be wrong
[16:03] <NCommander> ogra, I remember hearing that too
[16:14] <asac> Keybuk: i think the heuristic is a bit more advanced, but in general it should to be a mix of signal strength and some hash order
[16:43] <Riddell> pitti: jockey works so well on today's Kubuntu CDs is manages to download and install the broadcom driver without even an internet connection
[16:44] <davmor2> Riddell: that's cause it is already there just needs switching on ;)
[16:46] <ogra> davmor2, it doesnt need the firmware anymore ?
[16:50] <davmor2> ogra: It's worked for me each time with the new broadcom driver in I'm guessing restricted
[16:50] <mvo> Riddell: that sounds like pure magic :)
[16:51] <davmor2> what package do you need to install in order to get dbgsym's working it says yelp-dbgsym but the package doesn't seem to be in the repo's
[16:55] <mvo> davmor2: there is "deb http://ddebs.ubuntu.com/ intrepid main" for this
[16:55] <davmor2> mvo: thanks
[16:58] <superm1> Riddell, yeah its a bit of a misnomer that it's "downloading and installing".  if your hardware supports only wl, it's already activated (I filed a bug on that), if it supports wl and b43, it will blacklist b43 and then claim wl is activated
[17:05] <blackbird> hello everybody
[17:05] <blackbird> guess i'm the bug whore. found another one ;)
[17:06] <blackbird> guess the problems with the iwl3945 driver are known here, but apparently they got a lot worse with intrepid
[17:06] <pitti> Riddell: broadcom wl? yes, that's expected :)
[17:06] <blackbird> friend of mine is kicked out of vpn (cisco concentrator) because of bad performance and the connection goes down to less than 500kb
[17:16] <seb128> doko: do you know if there is some uptodate subversion backports for hardy somewhere?
[17:17] <doko> seb128: there must be ;) I got bug reports about python-setuptools not supporting 1.5 in hardy
[17:17] <doko> but I didn't do one
[17:17] <seb128> doko: and you don't know where, ie which ppa for example?
[17:17] <NCommander> seb128, there is
[17:18] <NCommander> 1.5.1 was backported to hardy
[17:18] <doko> something like "show me all duplicate packaged subversion packages in the PPAs" would be nice
[17:18] <seb128> NCommander: right, that's not uptodate though
[17:18] <NCommander> seb128, yes it is. 1.5.1~hardy2 and 1.5.1 I think
[17:19] <seb128> ok, not interested
[17:19] <seb128> there is a GNOME sysadmin who is using that and is trying to update to the current version based on this backport
[17:20] <seb128> would have been easier to point him to a current version if there was one somewhere rather than explain him how to do packaging
[18:14] <Keybuk> bryce: bug #285323
[18:14] <Keybuk> why would the apparent patch that broke it cause keyboard and mouse to stop working?
[18:15] <Keybuk> that patch looks to me like it just makes g-p-m ignore key presses without keycodes
[18:15] <bryce> hmm
[18:15] <Keybuk> is it returning something that makes X a doofus?
[18:17] <bryce> Keybuk: well, what I'm wondering is if something is causing the keyboard to be stolen away from X
[18:17] <Keybuk> that sounds plausible
[18:18] <bryce> I know on some hardware the hotkeys are provided via a separate device from the regular keyboard; in other cases they're combined; in some there is an overlap
[18:18] <Keybuk> could g-p-m not processing the key be ticking another bug where something else grabs it?
[18:18] <bryce> possibly yeah
[18:18] <Keybuk> how would someone debug that?
[18:19] <bryce> well, looking at 'xinput list' would show what devices are present and might indicate how the hotkeys are mapped in
[18:19] <Keybuk> could you sugget that on the bug?
[18:19] <jdong> note to self: ext4dev doesn't boot. shame on me.
[18:21] <ogra> bryce, if thats how xinput list is how its supposed to be, mine is broken ... for me that lists all devices that were ever plugged in, it doesnt clear them on removal here
[18:21] <ScottK> doko: Speaking of Pyhon 3.0, is there going to be a Python3.0 python-central anytime soon?
[18:21] <bryce> Keybuk: sure, although I'd really like to see someone more skilled in gnome-power-manager look into this
[18:22] <doko> ScottK: yes, prepared, although I hope it won't be necessary mid-term
[18:22] <Keybuk> tedg: ? :P
[18:23] <tedg> Keybuk: Could it be compiz trying to show the brightness up down graphic thingy?
[18:23] <ScottK> doko: So if I want to do porting work to support upstream on Python3.0 transition, do you recommend using disutils installs and not Debian packages for now?
[18:23] <Keybuk> tedg: dunno, have you read through the bug?
[18:23] <doko> ScottK: we'll have 2.6 and 3.0 packages in some PPA for intrepid, in about two weeks
[18:24] <ScottK> doko: Great.  A new Python Interest Group just started up in my area and I'm hoping to get some porting work going there.  A signficant fraction of the people at the first meeting use Ubuntu.
[18:27] <tedg> Keybuk: Haddn't gotten to the end.  Basically working keysym code seems to have broken it?  Otherwise the keysymbols wouldn't work.
[18:27] <Keybuk> it's odd to me that it breaks all keyboard and mouse after
[18:28] <tedg> I'm betting that it was ignoring those keys before, and responding to them is the problem.
[18:30] <Keybuk> ?
[18:30] <bryce> ogra: probably you should file a bug upstream about that.  I'd guess it's a hal issue rather than X since xinput unplugs properly for me.
[18:31] <ogra> bryce, well, i only see it with my wireless kbd, it doesnt go away even if i remove teh dongle, probably related to that specific hw
[18:31] <bryce> probably
[18:32] <tedg> Keybuk: I commented on the bug, but basically that by removing the code GPM doesn't see the keypresses.  Not that it fixes it, it just makes no more code execute.
[18:34] <bryce> ogra: in that case, could also be a kernel issue or something.
[18:35] <ogra> yeah
[18:35] <ogra> not critical anyway
[18:35] <ogra> i was just noticing that i still see the wireless kbd when i tried your command above and i unplugged the dongle yesterday already
[18:38] <superm1> Keybuk, isn't that the same problem that keyrelease events aren't showing up when pressing FN+some key
[18:39] <superm1> and hence causing GPM to hang on focus?
[18:39] <bryce> ogra: ah, gotcha.  xinput's codebase is pretty minimal, and really just prints stuff reported by deeper layers
[18:40] <bryce> maybe wireless devices get "held onto" longer since by nature they're not as definitively connected.  but you'd think if the dongle was removed, it'd clear it out.
[18:40] <ogra> yeah
[18:44] <infinito> is still possible to fix this before release? https://bugs.launchpad.net/ubuntu/+source/bluez-gnome/+bug/280679
[18:44] <ogra> pitti, you give proper upstream docs for CK and PK ... where is the one for SecurityHole ? :P
[18:45] <calc> jcastro: ping
[18:45] <calc> shouldn't the wiki still list dapper and gutsy on the (Current + Stable) section?
[18:45] <ogra> infinito, its not like that here on any of my systems ...
[18:45] <superm1> infinito, not in time for release, but it can be done shortly after as an SRU
[18:45] <superm1> infinito, in the meanwhile, can you submit it upstream?
[18:45] <infinito> superm1: sure
[18:46] <ogra> superm1, ?? all my installs have "display when adapter is present" ...
[18:46] <jcastro> calc: pong
[18:46] <superm1> ogra, that option is available, but from reboot to reboot i believe it doesn't stick because of that bug
[18:46] <calc> jcastro: the wiki changed and seems to be missing some important data
[18:47] <jcastro> calc: whereat?
[18:47] <calc> jcastro: not sure if it was intentional or if someone 'defaced' it ;-)
[18:47] <ogra> superm1, weird, its always been like that for me
[18:47] <calc> jcastro: the main page: https://wiki.ubuntu.com/
[18:47] <jcastro> calc: ! Let me find out
[18:47] <calc> jcastro: it only lists Hardy and Intrepid now, not the other two supported dists
[18:47] <calc> jcastro: not sure if the rest of the changes are ok or not, but it looks quite a bit different from what i remember
[18:48] <jcastro> calc: yes it is
[18:48] <jcastro> let me ask around
[18:49] <calc> "With the launch of the "release candidate", I have now replaced the home page with the version developed under Home/PageDiscussion"
[18:49] <calc> so it looks like it was discussed but maybe not well enough ;-)
[18:50] <calc> the main change happened on Oct 25 (change #187)
[18:51] <jcastro> calc: yeah it doesn't look very finished at all
[18:52] <calc> i can't seem to pull up the discussion page about it either
[18:52] <calc> though i might be doing something wrong
[18:52] <calc> i assumed it would be: https://wiki.ubuntu.com/Home/PageDiscussion due to how the change described it
[18:53] <pitti> ogra: that's s3kr1t
[18:53] <ogra> haha
[18:53] <calc> ah its there its just that is the exact same page copied to the main page (or looks like it)
[18:54] <jcastro> yeah
[18:54] <bdmurray> pitti: bug 280931 seems to be a duplicate of bug 283316 but interestingly it has a workaround
[18:54] <jcastro> calc: I'm all for cleanup but this seems a bit too unfinished to roll out to the live page, try pinging mdke or something.
[18:54] <jcastro> calc: I can follow up later once I get some openweek scheduling out of the way
[18:55] <calc> ok
[18:55] <infinito> superm1: is fixed upstream http://git.kernel.org/?p=bluetooth/bluez-gnome.git;a=commitdiff;h=4d56f10dc2a065d60724ccce8496d173fa0dc85a
[18:55] <calc> mdke: ping ^
[18:55] <apw> superm1: hey ... i hear you are intrested in experience of intrepid on dell studio 15's
[18:55] <superm1> infinito, okay great thx
[18:55] <jcastro> calc: while I have your attention: https://wiki.ubuntu.com/UbuntuOpenWeek
[18:55] <superm1> apw, yeah kirkland just mentioned you were having a single issue with it.  could you poke me later in the week though?
[18:55] <superm1> apw, say like thur or fri
[18:56] <calc> jcastro: i'll be in Beijing all next week
[18:56] <apw> yeah sure ..
[18:56] <jcastro> calc: ah right.
[18:56] <superm1> apw, okay thanks.  sorry just busy week :)
[18:56] <calc> i'll be back Nov 11 :)
[18:56] <calc> er which is a US holiday
[18:56] <calc> so Nov 12 :)
[18:57] <apw> superm1: i wonder why that is :)
[19:52] <pitti> tseliot: still remember http://launchpadlibrarian.net/18215648/jockey-gtk.png ? I can reproduce it \o/
[19:53]  * directhex adds pitti to a gtk liststore a few times
[19:54] <pitti|pitti|pitt> hello|hello|hello :)
[19:54] <mvo> that looks like a gtktreeview setup is run multiple times :)
[19:55] <liw> is there a reason why #268803 isn't marked "Confirmed"?
[19:56] <doko> hmm, do we set LC_ALL by default during the install somewhere?
[19:56] <liw> doko, one would hope not
[19:56] <doko> liw: see #ubuntu-bugs
[19:56] <tseliot> pitti: how?
[19:56] <pitti> tseliot: I updated bug 278071
[19:57] <pitti> tseliot: clicking on the tray icon multiple times while the app is open
[19:57] <tseliot> aah
[19:57] <tseliot> pitti: does it affect the kde version too?
[19:57] <mvo> pitti: if you could have a look at the srus for bug #289855 and bug #255545 that would be much appreciated
[19:58] <pitti> mvo: retroactively done 2 hours ago
[19:59]  * mvo hugs pitti
[19:59]  * mvo hands pitti the rockstar award
[20:00]  * pitti hugs mvo and handles him the bug squash gold star
[20:00] <tseliot> pitti pitti pitti: I'll see if I can reproduce it (and fix it) with the kde version here :-P
[20:01] <pitti> tseliot: "install three drivers in parallel"
[20:02] <tseliot> pitti: too bad apt won't allow us to do it. Damn lock...
[20:02] <tseliot> ;)
[20:05] <pitti> bdmurray: thanks for digging out, I'll have a look
[20:10] <superm1> ah pitti|pitti|pitti, i've seen that too, but could never reproduce it either, so I didn't file a bug : )
[20:19] <superm1> tedg, bryce, bug 285323 sounds like possibly effects of bug 261721
[20:22] <pitti> tseliot: just gotta love crashes like this: http://launchpadlibrarian.net/18645982/Traceback.txt
[20:23] <bryce> superm1: interesting, so is 285323 a dupe of 261721?
[20:23] <tseliot> pitti: LOL -> Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success
[20:24] <superm1> bryce, not necessarily, I think you need to look at a 2.6.24 kernel with the newer gpm pieces to verify gpm isn't at fault too
[20:29] <bryce> superm1: ok added a comment to that effect
[20:47]  * lool waves 'night
[20:47] <calc> did pdf printing get dropped with intrepid?
[20:47] <calc> er the pdf printer, print to pdf option is what i am talking about
[20:49] <sbeattie> calc: there should be a print-to-file option now that replaces the pdf target
[20:52] <calc> sbeattie: oh just in gnome apps, ok
[20:52]  * calc reinstalled cups-pdf
[20:52] <superm1> bryce, what other pieces sit in the chain for those key press and release events though?  oddly enough adding 2.6.24-21-generic i'm not getting key releases, but I do off of a hardy disk
[20:53] <superm1> this is going as far back as running showkey in a console
[20:56] <bryce> superm1: hmm, I mapped that out at one point, let me check my notes
[20:58] <bryce> Traditionally - in the kernel, it maps raw scancodes to internal keycodes.  hotkey-setup does a mapping (now replaced by HAL IIUC).  At that point you can see what X is seeing via xev
[20:59] <superm1> bryce, another platform close to the one that I sent you (done by the same ODM and BIOS teams) exhibits the problem along with a whole slew of others, perhaps can you see if you reproduce it there too?
[20:59] <bryce> from there, there's an xmodmap mapping
[20:59] <superm1> so this is all happening before you even get to X though
[20:59] <bryce> yeah
[21:00] <superm1> if you boot into "recovery mode" and choose root, showkey shows it there
[21:00] <bryce> which hardware is this again?
[21:05] <bryce> ok, I'm able to reproduce it
[21:09] <bryce> hmm, showkey doesn't show any output for the brightness keys
[21:10] <bryce> superm1: is that what you're referring to?  It does set the brightness correctly, and doesn't seem to steal the keyboard
[21:11] <superm1> bryce, oh you need to manually setkeycode in recovery mode
[21:12] <superm1> bryce, since hal hasn't done that for you
[21:12] <bryce> ah, what's the command for that?
[21:13] <superm1> bryce, setkeycodes e006 NUMBER
[21:14] <bryce> hmm, no go
[21:19] <kirkland> slangasek: so are your Europish hours over yet today?
[21:20] <slangasek> kirkland: yes, I'm now in "Europish workaholic afterhours"
[21:21] <kirkland> slangasek: okay, here's a heads up....
[21:21] <superm1> bryce, not seeing the problem with no keyrelease or not seeing anything?
[21:21] <superm1> e006 only maps to brightness up
[21:21] <kirkland> slangasek: we're testing a fix for https://bugs.edge.launchpad.net/ubuntu/+source/open-iscsi/+bug/289470 that would require an upload of open-iscsi
[21:22] <superm1> bryce, e005 is for brightness down
[21:22] <kirkland> slangasek: soren is done for the day, and asked me to find another core-dev and release team member to sponsor
[21:22] <kirkland> slangasek: mathiaz is our server man in London, but also done for the day
[21:23] <slangasek> kirkland: first question is, if this breaks iscsi, why wasn't this detected sooner than yesterday?
[21:23] <kirkland> slangasek: if you can't do it, can you point me to someone else
[21:23] <bryce> superm1: maybe I'm picking NUMBER incorrectly; what should I be using there?
[21:23] <superm1> bryce, i just put 200 or so
[21:24] <superm1> bryce, its just a keycode you are assigning to it
[21:24] <superm1> you can always just start hal instead and let it do it for you (unless of course hal is at fault!)
[21:24] <bryce> aha (I'd picked 255)
[21:25] <bryce> superm1: ok, with that set, brightness is no longer changing.  the keyboard seems to still be functioning fine.  What am I looking for here?
[21:25] <superm1> bryce, so now run showkey
[21:25] <slangasek> kirkland: can I do the upload - yes.  Am I willing to include this as a last-minute change a full day after the drop-deadline - less certain
[21:26] <superm1> and you'll see that keypress events show up
[21:26] <superm1> but keyrelease dont
[21:26] <bryce> superm1: ahhh, yes
[21:27] <kirkland> slangasek: understood.
[21:28] <slangasek> kirkland: that debdiff really looks unhappy with all of its packaging changes.  is there something we can cherry-pick here, or is that not known?
[21:29] <kirkland> slangasek: i have not uploaded my debdiff
[21:29] <slangasek> sorry, s/debdiff/diffstat/
[21:29] <slangasek> let's see your debdiff then :)
[21:29] <kirkland> slangasek: i have spent the last 8 hours on this basically.  the current debian package is a mess
[21:29] <kirkland> slangasek: what i did was rebase on upstream (above debian)
[21:29] <kirkland> slangasek: and applied our ubuntu changes to that
[21:30] <kirkland> slangasek: plus 2 lines of build fixes
[21:30] <kirkland> http://people.ubuntu.com/~kirkland/open-iscsi/
[21:30] <kirkland> slangasek: as i said, EtienneG is testing it for regression, and that it fixes that kernel/userspace alignment issue
[21:31] <slangasek> how confident are we that we have any meaningful coverage of regression testing, when this bug went unnoticed as it did in the first place?
[21:32] <bryce> superm1: interesting, so it sounds like from one of the bug commenters that the fix for 280646 exposes this bug
[21:32] <superm1> bug 280646
[21:32] <bryce> superm1: which indicates g-p-m is not being smart about handling lack-of-key-release situations or something?
[21:33] <superm1> bryce, well this lack of keyrelease doesn't only affect brightness though
[21:33] <superm1> eject and battery status should be effected too
[21:33] <kirkland> slangasek: EtienneG is regression testing it with the scenarios that he's familiar with, from a Canonical-support perspective
[21:33] <bryce> superm1: hmm true
[21:37] <bryce> superm1: ok I see that killing g-p-m does indeed make the issue go away
[21:38] <kirkland> slangasek: <EtienneG> kirkland, I cannot promise no regression; my test case is very simple: does the iscsi disk show up?  Can we mount a file system on it?  Can we write to the filesystem?  So far, it is yes to all three, but that's it
[21:41] <superm1> bryce, yesish, the hang is gone but the key events keep firing until you press another key
[21:44] <wgrant> And if you turn off key repeat, it works fine.
[21:44] <slangasek> kirkland: I'm reviewing the debdiff now; is there any sense at all in looking for a cherry-pick fix for this issue, or does tht just increase our risk of regression?
[21:45] <kirkland> slangasek: hrm, i went by: http://www.open-iscsi.org/index.html#download
[21:45] <kirkland> The current devel release: open-iscsi-2.0-870-rc3.tar.gz   ... This adds support for 2.6.26 and 2.6.27
[21:46] <slangasek> ... wait, seriously?  There's a CONFIG_SYSFS_DEPRECATED option available in the kernel, and we're not setting it?
[21:46] <slangasek> correction, CONFIG_SYSFS_DEPRECATED_V2
[21:47] <kirkland> kirkland@t61p:/tmp/open-iscsi.debian$ grep CONFIG_SYSFS_DEPRECATED /boot/config-2.6.27-7-generic
[21:47] <kirkland> # CONFIG_SYSFS_DEPRECATED_V2 is not set
[21:47] <slangasek> "the previous semi-stable release" - "semi-" is only an acceptable modifier for the sweetness of chocolate used in baking
[21:48] <kirkland> slangasek: :-D
[21:48] <kirkland> LoL
[21:51] <superm1> wgrant, well fine in the sense that the events dont keep firing as repeats, but gpm still steals focus and hangs onto it
[21:56] <wgrant> superm1: True.
[21:57] <EtienneG> hey slangasek!
[21:57] <EtienneG> slangasek, kirkland tell me you are looking at the new open-iscsi package; I have helped test, if you have any question ...
[22:01] <bryce> superm1: so I'm getting fairly convinced this is due to quirky logic in g-p-m's code
[22:01] <bryce> superm1: IIRC the code that handles this is relatively fresh, so perhaps this is just a corner case they didn't account for
[22:08] <slangasek> kirkland: looking at the diff, would it not be sufficient to pull in kernel/2.6.26_compat.patch and avoid all the other development changes
[22:08] <slangasek> ?
[22:09] <slangasek> i.e., I think this is the commit that adds compatibility with 2.6.27: http://git.kernel.org/?p=linux/kernel/git/mnc/open-iscsi.git;a=commitdiff;h=55896174c0242e6a68ff4e91173acab8d1be8a7c
[22:09] <kirkland> slangasek: hmm, i can try to test that
[22:10] <slangasek> kirkland: ok, thanks - if that works, it would seem to let us contain the delta much better
[22:10] <kirkland> slangasek: understood
[22:10] <slangasek> I'm afk for a bit now
[22:22] <crimsun> bdmurray: regarding your query for bug 289621, about 18 hours ago I committed a fix in my PPA
[22:23] <crimsun> bdmurray: I've since commented in the master bug and asked people to use the fixed one
[22:26] <crimsun> superm1: ^
[22:27] <TheMuso> crimsun: probably a pulse alsa plugin issue, I know about it and alsa-plugins git has a fix for it which I intend to apply as an SRU.
[22:27] <crimsun> TheMuso: that's what's in my PPA
[22:27] <TheMuso> crimsun: Right.
[22:33] <bdmurray> TheMuso: so that bug should be targetted to intrepid-updates?
[22:34] <TheMuso> bdmurray: Well there are actually a few bugs reporting similar issues, so whatever bug is actually filed against alsa-plugins should be.
[22:35] <crimsun> bdmurray: the master bug mistakenly has a gnome-media task; I added the appropriate culprit (alsa-plugins)
[22:35] <YokoZar> Whoa massive failure trying to install 8.10 for me: Ubiquity didn't display any partitions when it got to the partition step  (using the RC image)
[22:36] <seb128> crimsun: you should rather change the component when it's incorrect than adding a new one
[22:36] <crimsun> seb128: yes, I probably should have, but I hadn't read /all/ the duplicates
[22:38] <seb128> ok, just saying it in case, some people close the task as invalid and add new one but that means that people subscribed to the component which has the close task still get mails
[22:42]  * TheMuso wishes that component changing could be done via email... Unless it can and I don't know about it yet. :)
[22:48] <bdmurray> TheMuso: I don't think it can, however you might be able to script it with python-launchpad-bugs
[22:51] <ScottK> TheMuso: /me suggest filing bugs.
[22:51] <TheMuso> ScottK: Yeah I think I will once I've checked to make sure there is not a bug already about that.
[22:51]  * TheMuso finds the email interface 10 times more efficient.
[22:52]  * ScottK may have already filed that one.  Don't recall for sure.
[23:00] <slangasek> kirkland: how goes it?
[23:00] <kirkland> slangasek: i just got it to build
[23:00] <kirkland> slangasek: frigging limits.h
[23:01] <kirkland> slangasek: that's bitten me one too many times this dev cycle
[23:01] <slangasek> heh
[23:01] <kirkland> slangasek: i had to modify the Makefile too, obviously
[23:01] <slangasek> right
[23:03] <kirkland> slangasek: you reckon this bit of the makefile is necessary?
[23:03] <kirkland> +dpkg_divert:
[23:03] <kirkland> +       for module in $(ko) ; do \
[23:03] <kirkland> +               dpkg-divert --rename /lib/modules/$(KERNELRELEASE)/$(INSTALL_MOD_DIR)/$$module ; \
[23:03] <kirkland> +       done
[23:05] <slangasek> uh
[23:05] <kirkland> slangasek: i left it out
[23:06] <NCommander> kirkland, what are you trying to build specifically?
[23:06] <slangasek> absent a specific rationale, please do
[23:06] <kirkland> slangasek: looked kinda forceful, inappropriate
[23:06] <kirkland> NCommander: open-iscsi
[23:06] <slangasek> dpkg-divert --rename without --divert is nasty and probably incorrect here
[23:07] <kirkland> slangasek: another question ...
[23:07] <kirkland> slangasek: this package does not currently have a patch system
[23:07] <kirkland> slangasek: shall I add one?  it's already carrying one minor bashism fix in the diff.gz (nasty, again)
[23:08] <slangasek> If there are already upstream changes in the diff.gz, I wouldn't bother adding a patch system
[23:08] <slangasek> besides, the kernel/ directory effectively *is* a patch system :)
[23:08] <kirkland> slangasek: yeah
[23:09] <kirkland> slangasek: current state is http://people.ubuntu.com/~kirkland/open-iscsi/
[23:10] <kirkland> slangasek: i'm moving on to testing it now
[23:14] <slangasek> kirkland: hrm, I'm looking closer and suddenly fearful that nothing in that directory is used if we're not building the kernel modules, which we aren't
[23:14] <slangasek> so I may have led you on a wild goose chase :P
[23:15] <kirkland> slangasek: empirical testing of this deb has confirmed that it is re-broken again
[23:15] <slangasek> right :/
[23:16] <kirkland> slangasek: okay, how about I leave my -870 package for Mathiaz's regression testing tomorrow.  he's in London for the release sprint
[23:16] <kirkland> so he's also one your pseudo-Europish time
[23:17] <slangasek> ok
[23:18] <kirkland> slangasek: i'm going to inform dendrobates that i've taken it as far as I can
[23:18] <kirkland> slangasek: and that I'm going to leave it for mathiaz to pick up tomorrow; and it'll be up to the release team as to whether or not it's accepted
[23:18] <slangasek> right, thanks
[23:19] <slangasek> I'll putz around with the package itself a bit more; to see if I can either isolate the key fix, or come to terms with the whole diff
[23:25] <bdmurray> apachelogger: mvo recently added a quirk to update-manager that might handle bug 289611 if I understand it correctly.
[23:25] <NCommander> lamont, ping