[12:41] <jerry760poip_>  hi i got a question not sure if this is were to ask
[12:41] <jerry760poip_> i have had 6 days ago F.B.I. call me.
[12:41] <jerry760poip_> they said i have been having to much net activity.
[12:41] <jerry760poip_> from torrented movies i told them i did not do it.
[12:41] <jerry760poip_> and for the past 5 days they went to my uncle's and two cousin's work asking about me.
[12:41] <jerry760poip_> and showing them my picture.
[12:41] <jerry760poip_> now they have the home number to where i am so why havent they just come straight to me?
[12:41] <jerry760poip_> one i do not have a hdd i'm always running live cd so of course i did not
[12:41] <jerry760poip_> do it now what should i do?
[12:41] <jerry760poip_> i called attorneys none around here know what to do or where i should go.
[02:11] <mpt> Keybuk, no desktop team meeting today?
[02:11] <Keybuk> mpt: public distro team meeting later
[02:14] <mpt> Keybuk, do they alternate weeks?
[02:15] <Keybuk> public entire development team meeting is monthly
[02:15] <cjwatson> well, four-weekly
[02:16] <mpt> ok
[04:21] <evand> @schedule New_York
[04:21] <ubotu> Schedule for America/New_York: 11 Oct 11:00: Community Development Team | 16 Oct 12:00: Kernel Team | 17 Oct 12:00: QA Team | 23 Oct 11:00: Server Team | 23 Oct 12:00: Kernel Team | 30 Oct 12:00: Kernel Team
[04:59] <calc> hi
[04:59] <pitti> hey calc
[04:59] <Riddell> hi
[04:59] <ArneGoetje> hi
[04:59] <calc> pitti: there is the final ooo upload in progress, it was supposed to have completed last night but i had some sort of computer/network trouble, looked at it today and it was just hung in the middle
[05:00] <Riddell> not RC critical I hope :)
[05:00] <pitti> calc: ah, great; the one which disables java on powerpc? any other changes?
[05:00] <pitti> calc: (changes must be minimal at this point)
[05:00] <pitti> calc: fixing sparc would be awesome, but I understand that's more luck than engineering?
[05:00] <calc> pitti: yea disables java on ppc, disables portaudio v19, and has translation update for menu items
[05:00] <davmor2> Riddell: not on your own :)
[05:01] <pitti> ah
[05:01] <pitti> hi slangasek
[05:01] <calc> pitti: seems to be, according to doko it seems to ICE on one box nearly every time but works on a different one
[05:01] <mdz> good afternoon folks
[05:01] <evand> hi
[05:02] <doko> pitti: it's not reproducible. point.
[05:02] <mdz> we didn't do much preparation for this meeting, as I think many of us forgot about it due to the release crunch :-)
[05:02] <mdz> #startmeeting
[05:02] <MootBot> Meeting started at 16:02. The chair is mdz.
[05:02] <MootBot> Commands Available: [TOPIC] , [IDEA] , [ACTION] , [AGREED] , [LINK] , [VOTE] 
[05:02] <pitti> doko: right, so some buildd prodding might help (that's what I meant with 'luck' :) )
[05:02] <doko> pitti: with the next upload, stop the buildd on sejong so it goes to another buildd
[05:02] <pitti> doko: noted
[05:02] <mdz> so there isn't an agenda, and I suggest that we use this time to put our heads together regarding any outstanding issues for the release
[05:02] <pitti> Ian has one topic
[05:03] <mdz> what is it?
[05:03] <pitti> disabling auto-cryptsetup IIRC
[05:03] <pitti> but ++ for RC/final release planning, too
[05:04] <mdz> Ian doesn't seem to be here
[05:04] <cjwatson> I volunteered to make secure erase not the default, which seemed like the worst outstanding problem
[05:04] <ogra> he's next door
[05:04] <cjwatson> pitti: iirc Ian raised a cryptsetup item too; did you look at it?
[05:05] <pitti> cjwatson: I looked at his bugs briefly
[05:05] <dholbach> iwj: we are just talking about disabling auto-cryptsetup
[05:05] <pitti> of those, the erase and the 'low contrast' ones seem easy targets for final
[05:05] <cjwatson> 16:04 <cjwatson> I volunteered to make secure erase not the default, which seemed like the worst outstanding problem
[05:05] <iwj> dholbach: Aha.
[05:05] <pitti> the usability bugs are too intrusive IMHO
[05:05] <cjwatson> 16:04 <cjwatson> pitti: iirc Ian raised a cryptsetup item too; did you look at it?
[05:06] <iwj> Getting rid of the secure erase will help.
[05:06] <cjwatson> I thought we might talk about what the basic set of things we need to fix is, and from there whether that's doable
[05:06] <iwj> I think the passphrase prompt lack of prominence is quite serious actually.
[05:07] <iwj> I mean, it doesn't actually stop you but the visibility of the bug is very high (unlike that of the prompt).
[05:07] <cjwatson> bug 151264?
[05:07] <ubotu> Launchpad bug 151264 in partman-crypto "passphrase entry screen needs work" [Undecided,New]  https://launchpad.net/bugs/151264
[05:07] <iwj> Bug 64408.
[05:07] <ubotu> Launchpad bug 64408 in usplash-theme-ubuntu ""Urgent" text is poorly readable due to low contrast (blue on black)" [Medium,Confirmed]  https://launchpad.net/bugs/64408
[05:07] <cjwatson> ah
[05:07] <pitti> iwj: I mentioned that of your bugs the 'low contrast' one seems relatively easy to fix at first sight, the others are too intrusive IMHO
[05:07] <cjwatson> damnit, we've fixed that about three times already
[05:07] <iwj> 151264 is easy to fix well enough for this case - just change the text.
[05:07] <iwj> cjwatson: No, no.
[05:07] <pitti> since it also applies to all other texts
[05:07] <pitti> like the CD check results
[05:07] <cjwatson> that also bites casper
[05:07] <mdz> bug 149511 is milestoned but appears invalid
[05:07] <iwj> cjwatson: You misunderstand.  Bug 64408 isn't that there is actually something going wrong.
[05:07] <ubotu> Launchpad bug 149511 in ubuntu-meta "[Gutsy]  hplip is not installed by default" [Critical,Confirmed]  https://launchpad.net/bugs/149511
[05:08] <cjwatson> iwj: we have, it keeps coming back with different themes and such
[05:08] <cjwatson> iwj: I'm familiar with the bug
[05:08] <iwj> cjwatson: AFAICT it has never done anything differently to what it does now.
[05:08] <cjwatson> iwj: sladen swore he'd fixed it
[05:08] <cjwatson> a release or two ago
[05:08] <iwj> There was a different bug which was some kind of driver problem.
[05:08] <iwj> Which made it even worse.
[05:09] <cjwatson> well, it doesn't matter. I think this one is trivial and should be on the list for final.
[05:09] <pitti> so, the general question here is whether we consider the usability bugs bad enough to disable the feature post-RC, right?
[05:09] <pitti> if we assume that we fix erase and contrast
[05:09] <iwj> pitti: Yes, I think so.
[05:09] <iwj> The prompt lacking feedback is annoying.  Can it be easily fixed ?
[05:10] <cjwatson> iwj: sorry, which prompt lacking feedback?
[05:10] <iwj> I don't think it's essential.  I think improving the passphrase setup wording is essential to stop users blowing their torso off.
[05:10] <iwj> Bug 151305
[05:10] <ubotu> Launchpad bug 151305 in cryptsetup "passphrase prompt at boot-time lacks feedback" [Medium,Confirmed]  https://launchpad.net/bugs/151305
[05:10] <iwj> You hit return and it does nothing to say "yes, that's fine".
[05:10] <cjwatson> that ought to be a trivial matter of another usplash message
[05:10] <pitti> it should probably just delete the prompt
[05:10] <cjwatson> text-urgent ok or some such
[05:10] <pitti> or that
[05:11] <iwj> The bit of code that's actually doing the work has the ability to send the message at the right point ?
[05:11] <mdz> I don't think our time is well spent arguing this particular class of bugs, given that this is an infrequently-used non-default option on the alternate CD
[05:11] <mdz> I expect we have bigger fish to fry
[05:12] <iwj> So of the ones in my activity report I think we should fix 151244 (secure erase), 151264 (partiallly, improve the wording), 151305 (feedback) and 64408 (colour).
[05:12] <cjwatson> mdz: it's also a relatively long-awaited new feature that ISTR hearing the marketing team mentioning
[05:12] <doko> linux-source did fail to build on sparc, and I'm unsure if the smp lock problem is fixed
[05:12] <cjwatson> I think it behooves us to put a bit more effort into polishing it
[05:12] <iwj> 151266 can wait.
[05:12] <ArneGoetje> Bug 66104 needs escalation I think. Apparently there is a fix available from Redhat.
[05:12] <ubotu> Launchpad bug 66104 in scim "scim: input freezes in various applications under XIM mode" [Medium,Confirmed]  https://launchpad.net/bugs/66104
[05:12] <cjwatson> especially since the fixes in question seem fairly trivial
[05:13] <mdz> cjwatson: it's not in any of the communications that I've seen
[05:13] <pitti> so AFAICS, the only real bad bugs are 145226 (Kubuntu OEM broken) and 147943 (panel not visible sometimes under compiz, until after clicking on it), and 151351 (xorg-video-intel/kernel desync)
[05:13] <mvo> #147943 <- that one should be fixed with latest compiz
[05:13] <mdz> the milestone list certainly still is hard to read
[05:13] <mvo> (not on the CD though)
[05:14] <Riddell> cjwatson has done good things on the Kubuntu OEM problem
[05:14] <ogra> pitti, lool is working on 151351
[05:14] <cjwatson> ArneGoetje: what do you need - a sponsor, approval, ...?
[05:14] <pitti> right, compiz is in the archive, but didn't make it to the CD
[05:14] <pitti> lool tests a fix for -intel
[05:14] <ArneGoetje> cjwatson: actually the bug is in X11... how to proceed?
[05:14] <pitti> and the Kubuntu OEM one seems to boil down to a chown (I didn't check, though)
[05:14] <cjwatson> pitti: it's not actually broken, you just get a stupid error
[05:14] <pitti> cjwatson: oh, even better
[05:14] <cjwatson> it works if you acknowledge it and move on
[05:14] <cjwatson> but yes, it's fixed in bzr now
[05:15] <pitti> fine for release-noting it then
[05:15] <mvo> ogra: that would be network-manager
[05:15] <ogra> is that something from NM ?
[05:15] <ogra> ah, right
[05:15] <ogra> pretty bad if you have bound services to static devices :)
[05:16] <highvoltage> (like LTSP servers?)
[05:16] <asac> ogra: static devices are not changed
[05:16] <ogra> highvoltage, or local webservers, samba servers etc
[05:16] <ogra> asac, ah, good
[05:16] <asac> ogra: and actually i haven't received any of those complains as a bug
[05:17] <ogra> well, i talked to people that needed it working, all three i spoke to had fixed it manually
[05:17] <ogra> and i didnt see it here yet
[05:18] <asac> ogra: tell them to report a bug
[05:18] <asac> :)
[05:18] <ogra> indeed :)
[05:18] <asac> or ping me directly
[05:18] <ogra> yup
[05:18] <bdmurray> I seem to recall one from yesterday but it was a desktop system they were using as a server
[05:18] <Riddell> bug 151311 is pretty serious, I don't know how many video cards it affects but if it's all intel ones that's bad
[05:18] <ubotu> Launchpad bug 151311 in xserver-xorg-video-intel "DPI in kubuntu incorrect on xorg-video-driver-intel" [High,Confirmed]  https://launchpad.net/bugs/151311
[05:18] <mdz> shouldn't matter; the behaviour doesn't change
[05:18] <ogra> bdmurray, well, thats what i actually meant ...
[05:18] <mdz> ogra: auto DHCP interfaces are treated the same by network manager as by ifupdown
[05:19] <ogra> many people use their ubuntu install as webservers or fileservers in their lan, but if static interfaces arent touched its fine
[05:19] <evand> Does compiz leak memory like a sieve for anyone else?  It's using about 1GB here after a day.  I think it may be related to the nvidia driver fixing the "I've run out of memory, but here's a black window for your troubles" issue.
[05:19] <ogra> as i siad i couldnt reproduce it at all yet
[05:19] <davmor2> Riddell:  I think bryce has done something with it but I dont know how far he got
[05:20] <mdz> ogra: probably they were just confused because the change isn't documented in the file
[05:20] <mdz> asac: if it isn't already, it should be added to the release notes just so that users aren't surprised
[05:20] <asac> mdz: maybe we should add a comment?
[05:21] <mvo> evand: I haven't see this behavior but my main workstation is not a nvidia - I have reports from people runing it on their laptop for weeks and it is fine. the trouble is that the nvidia driver changes very frequently
[05:21] <ogra> yeah
[05:21] <mvo> evand: and each release seem to have a new set of problems
[05:21] <ogra> comment++
[05:21] <mdz> asac: wish we'd thought of it before
[05:21] <MacSlow> evand, I've not witnessed this on my nvidia-box here (gf 8800)
[05:21] <Riddell> davmor2: if not, we should look at adding a workaround to guidance, it wouldn't be hard
[05:22] <MacSlow> evand, what card/driver-version do you use_
[05:22] <MacSlow> ?
[05:22] <Keybuk> compiz is only one tenth the size of firefox for me
[05:22] <evand> MacSlow: nVidia Corporation G70 [GeForce 7300 GT]  (rev a1)
[05:23] <mvo> ArneGoetje: I think if it is not super-duper-safe we should put it into a StableReleaseUpdate
[05:23] <Keybuk> admittedly, this is damning praise, but it's certainly not of the order you've found
[05:23] <Keybuk> uptime is quite high
[05:23] <mvo> evand: that is not a mobile one, is it?
[05:23] <cjwatson> ArneGoetje: unfortunately bryce is away at the moment
[05:23] <asac> do we have a release notes drafting page in wiki where i can add that info?
[05:23] <evand> mvo: correct, this is a iMac
[05:23] <cjwatson> ArneGoetje: the upstream bug report seems to indicate that the patch doesn't really fix it though?
[05:23] <cjwatson> asac: http://wiki.ubuntu.com/GutsyGibbon/ReleaseNotes
[05:23] <evand> ii  nvidia-glx-new         100.14.19+2.6.22.4-13.6
[05:24] <ArneGoetje> cjwatson: yes, but it lowers the problem for now.
[05:24] <davmor2> Riddell: there are a couple of work rounds on the bug itself.  but bryce has put in a link and was making some deb.diff's it's all in the bug :)
[05:24] <mvo> evand: I have a testbox with the same generation of card (7600) I can give it a go
[05:24] <evand> thanks mvo.  Let me know if you need anything from me.
[05:25] <ArneGoetje> mvo: should we then change scim back to scim-immodule instead of xim?
[05:25] <cjwatson> ArneGoetje: it sounds like a possible post-release update to me
[05:25] <MacSlow> hi Amaranth
[05:26] <Amaranth> howdy
[05:26] <slangasek> mdz: "treated the same by network manager as by ifupdown" - that doesn't seem accurate to me, IME NM never brings up the network interface until user login?
[05:26] <cjwatson> I'm just looking over the patch
[05:26] <pitti> ArneGoetje: does it only affect upgrades or also fresh installs? in the former case, an SRU is almost as good as pressing it into the archive
[05:26] <mvo> ArneGoetje: I'm hesitant to change anything that is not a scim showstopper at this stage of the release, but then you know about this better than me
[05:26] <mdz> slangasek: that's only the case for authenticated networks, which require additional configuration in /etc/network/interfaces, which means they aren't touched on upgrade
[05:26] <pitti> ArneGoetje: since upgrades will directly upgrade to whatever is in -updates
[05:26] <ArneGoetje> cjwatson: ok, fine for me. but then we should probably change the default setting back to scim-immodule and put a note in the Release Notes.
[05:27] <cjwatson> https://bugs.freedesktop.org/attachment.cgi?id=7606&action=view is the patch for this bug, btw
[05:27] <ArneGoetje> mvo: this is a show stopper... :(
[05:27] <mvo> oh :(
[05:27] <cjwatson> ArneGoetje: what are the consequences of going back to scim-immodule?
[05:27] <slangasek> mdz: ah, ok
[05:27] <asac> slangasek: NM brings up interfaces that don't need keyring access
[05:28] <doko> ArneGoetje: weren't there problems with scim-immodule and OOo?
[05:28] <ArneGoetje> cjwatson: third party software that many users want, like skype, acroread, etc. will not work if they depend on libstdc++5
[05:28] <ArneGoetje> doko: I'm not sure about OOo... let me test.
[05:28] <mvo> ArneGoetje: what about scim-bridge (probably for hardy)? shouldn't that solve this issue?
[05:29] <doko> ArneGoetje: iirc there was a workaround to hide libstdc++5 ...
[05:29] <cjwatson> the patch seems fairly isolated to the xim bits of libx11, which is something
[05:29] <ArneGoetje> mvo: need to test if it fixes all the problems. not enought information in the bug report about this.
[05:30] <cjwatson> I'm concerned that switching scim configuration is much harder to fix in a post-release update than doing something like this libx11 patch
[05:30] <cjwatson> if we switch back to scim-immodule, I think that's the way it needs to stay for the lifetime of gutsy
[05:30] <cjwatson> whereas if we stick with xim we can fix this before or after release at RM discretion
[05:31] <mvo> evand: Amaranth just pointed me to bug #151168 (filed yesterday) about a similar problem with nvidia
[05:31] <ubotu> Launchpad bug 151168 in compiz "memory leak in compiz w/ nvidia [gutsy] " [Undecided,Incomplete]  https://launchpad.net/bugs/151168
[05:31] <ArneGoetje> cjwatson: what's your suggestion?
[05:33] <cjwatson> ArneGoetje: put the libx11 fix in a PPA and get as many users as possible (both xim-requiring and not) to test it over the next few days
[05:33] <cjwatson> then it'll be easier to decide whether it can go in post-rc pre-final
[05:33] <ArneGoetje> cjwatson: ok, will do.
[05:34] <evand> mvo: ah, thanks for pointing me to that
[05:34] <cjwatson> ok, anything else on the release agenda?
[05:35] <pitti> let's get this damn thing out :)
[05:35] <ogra> :)
[05:35] <cjwatson> mvo: do you think 151168 is fixable?
[05:35] <highvoltage> yay!
[05:35] <mvo> bug #151168
[05:35] <ubotu> Launchpad bug 151168 in compiz "memory leak in compiz w/ nvidia [gutsy] " [Undecided,Incomplete]  https://launchpad.net/bugs/151168
[05:35] <heno> Extra testing contributions are appreciated!
[05:35] <Amaranth> cjwatson: I can't even reproduce it
[05:35] <MacSlow> Amaranth, #151168 does not affect my 8800GTS either
[05:35] <mvo> cjwatson: not if its really a bug inside the nvidia driver
[05:35] <heno> Results can be filed in https://iso.qa.stgraber.org
[05:35] <cjwatson> who is going to fix that usplash theme bug?
[05:36] <pitti> the blueness?
[05:36] <Amaranth> MacSlow: That guy even has the same 7400 Go as me
[05:36] <mvo> compiz feedback welcome! if you system freeze or your keys do not work, talk to me
[05:36] <dholbach> I can't reproduce with nVidia Corporation GeForce 7100 GS (rev a1) either :-/
[05:36] <Amaranth> Maybe it's a plugin
[05:36] <mvo> Amaranth: do you see it with vlc neither? watching video is fine?
[05:36] <pitti> cjwatson: I have about zero knowledge about usplash, but with slangasek taking over release matters I have some time to look into it now
[05:36] <Amaranth> mvo: Everything is fine
[05:36] <mvo> evand: do you use any fancy plugins?
[05:37] <evand> mvo: ugh, ring switcher?  I don't believe that's used anymore by default, is it?
[05:37] <cjwatson> iwj: or perhaps you could fix that usplash bug, since you noticed it? :)
[05:37] <iwj> cjwatson: OK :-).  Not that I've ever touched usplash but I can give it a go.
[05:37] <Amaranth> evand: ring is enabled if you use 'extra effects'
[05:37] <cjwatson> I suspect pitti is still going to be jammed pretty solid
[05:37] <cjwatson> iwj: should be in usplash-theme-ubuntu though note that there are also corresponding themes for other derivatives
[05:37] <Amaranth> evand: Do you use cube?
[05:38] <iwj> cjwatson: Right.
[05:38] <evand> odd, I thought I enabled extra effects on my girlfriend's laptop and she ended up with the iTunes switcher
[05:38] <evand> Amaranth: no
[05:38] <evand> well, what's the shortcut for it
[05:38] <iwj> Any objection to me just making it white ?
[05:38] <Keybuk> Amaranth: shift switcher is prettier than ring for extra effects
[05:38] <lool> Make it pink!
[05:38] <MacSlow> Amaranth, no... shift not ring is used
[05:38] <Amaranth> evand: If you don't know if you're using cube you aren't using cube
[05:39] <Amaranth> MacSlow: Oh, since when?
[05:39] <pitti> iwj: in dapper we had that beautiful yellowish tone which matched the logo
[05:39] <MacSlow> Amaranth, hm... a week or so
[05:39] <pitti> iwj: but at that point we shouldn't be picky
[05:39] <Keybuk> Shift Switcher made our Apple fanatic in the office explode with joyous delight
[05:39] <evand> heh
[05:39] <Amaranth> Well the guy with the problems is using ring too...
[05:39] <Amaranth> So I suppose that could be
[05:39] <ogra> lool++
[05:39] <Keybuk> he was literally bouncing around with a huge grin on his face saying how wonderful gutsy is
[05:39] <mvo> HAHA
[05:39] <Amaranth> Keybuk: Which one is that? :)
[05:40] <iwj> I'll make it be white and someone else can find a nicer colour if they really want, provided it isn't 000080.
[05:40] <Keybuk> Amaranth: Mark Murphy, not sure whether you met him or not?
[05:40] <Amaranth> evand: Disable ring, see if the problem goes away
[05:40] <Amaranth> Keybuk: hmm, I don't think so
[05:40] <evand> Amaranth: will do
[05:41] <pitti> iwj: kwwii might have an opinion and a magic tuple :)
[05:41] <cjwatson> I have no problem with white for TEXT-URGENT
[05:41] <cjwatson> it's rather guaranteed to be visible
[05:41] <pitti> ++
[05:42] <mvo> evand: and if it goes away, make sure to mention this on the bugreport :)
[05:42] <evand> mvo: will do :)
[05:42] <kwwii> iwj: I don't quite get the problem
[05:42] <cjwatson> kwwii: dark blue on black is hard to read
[05:43] <kwwii> cjwatson: what is dark blue?
[05:43] <cjwatson> kwwii: colour used for textual messages in usplash
[05:43] <cjwatson> which are still used for certain prompts that require user feedback
[05:43] <kwwii> ouch, that is really freaky - I thought it dipped into the palette for the color, and I do not remeber every putting blue into the pic
[05:44] <pitti> kwwii: this blue is haunting us; noone put it in, and it keeps appearing
[05:44] <pitti> must be some default deeply engraved in some corner of the VGA BIOS, or so
[05:44] <Hobbsee> pitti: sabbotage by kubuntu, more likely.
[05:44] <kwwii> iwj: let me know if I can help in any way
[05:44] <pitti> Hobbsee: Right!
[05:44] <kwwii> Hobbsee: shhhh! don't tell them!
[05:44] <Hobbsee> ahem!
[05:45] <Hobbsee> pitti: it's just telling you to get more attention given to kubuntu for hardy.
[05:45] <pitti> iwj, cjwatson: so, I'm happy to look into cryptsetup and add this [OK]  confirmation
[05:45] <mdz> what's the bug number for the usplash blue text bug?
[05:45] <cjwatson> and I'll do the partman-crypto work
[05:45] <mdz> ah, bug 64408
[05:45] <ubotu> Launchpad bug 64408 in usplash-theme-ubuntu ""Urgent" text is poorly readable due to low contrast (blue on black)" [Medium,Confirmed]  https://launchpad.net/bugs/64408
[05:46] <pitti> 64408
[05:46] <cjwatson> Arne is to put the libx11 fix into a PPA and follow up with the release team once we have testing of it
[05:47] <cjwatson> lool is fixing the xorg intel breakage
[05:47] <mdz> pitti mentioned bug 145226, bug 147943, bug 151351
[05:47] <ubotu> Launchpad bug 145226 in oem-config "Kubuntu OEM DCOP error" [High,Confirmed]  https://launchpad.net/bugs/145226
[05:47] <ubotu> Launchpad bug 147943 in compiz "[MASTER]  broken initial stacking (was: compiz hides quick loading windows at login)" [High,Fix released]  https://launchpad.net/bugs/147943
[05:47] <ubotu> Launchpad bug 151351 in xserver-xorg-video-intel "Corrupted screen on G33 with -14 kernel; regression from -13" [High,Fix released]  https://launchpad.net/bugs/151351
[05:47] <ubotu> Launchpad bug 151305 in cryptsetup "passphrase prompt at boot-time lacks feedback" [Medium,In progress]  https://launchpad.net/bugs/151305
[05:47] <pitti> mdz: right
[05:47] <cjwatson> mdz: I'm doing 145226, mvo said 147943 was fixed, 151351 is the xorg intel breakage I mentioned
[05:47] <pitti> so, compiz is in the archive
[05:48] <pitti> -intel is uploaded and should be in the queue
[05:48] <pitti> kubuntnu oem is in bzr
[05:48] <mdz> cjwatson: right, of those, only bug 151351 is milestoned for 7.10 at the moment
[05:48] <ubotu> Launchpad bug 151351 in xserver-xorg-video-intel "Corrupted screen on G33 with -14 kernel; regression from -13" [High,Fix released]  https://launchpad.net/bugs/151351
[05:48] <Keybuk> heh, kubuntnu
[05:48] <pitti> mdz: the others are still at -rc, I think
[05:48] <mdz> sounds like 145226 should be marked fix committed
[05:49] <pitti> -intel hit -changes
[05:49] <pitti> meh, it didn't have a bug number in the changelog
[05:49] <cjwatson> mdz: done
[05:50] <davmor2> cjwatson: will that fix 151311 too or not?
[05:50] <cjwatson> same code as is causing 145226 is in ubiquity, though is only relevant if you do an automatic install
[05:50] <mdz> pitti,slangasek: so https://edge.launchpad.net/ubuntu/+milestone/ubuntu-7.10 is believed complete and accurate now?
[05:50] <cjwatson> davmor2: err, no idea
[05:50] <davmor2> ok
[05:50] <cjwatson> davmor2: looks totally separate to me
[05:51] <pitti> mdz: there might be some stuff left over from -rc which is in unapproved and needs to be checked
[05:51] <pitti> uploads have trickled in like mad
[05:52] <mdz> pitti: :-/  hard to know where we stand when we don't have a single list of targets
[05:52] <slangasek> mdz: I expect there are a number of bugs still milestoned under RC and actively worked on that should be transferred over; that makes for a nice bit of busywork
[05:52] <cjwatson> the sooner that's done the better
[05:53] <mdz> slangasek: it's time to make the final call on what gets actively worked on and what falls out
[05:53] <slangasek> yes
[05:53] <bdmurray> bug 135319 didn't seem fixed to me yesterday
[05:53] <ubotu> Launchpad bug 135319 in usplash "Usplash progress bar not centered on the monitor" [Medium,Triaged]  https://launchpad.net/bugs/135319
[05:53] <cjwatson> slangasek: i.e. we also need to sit down and work out what goes to post-release updates
[05:53] <mdz> so only the things which are showstoppers should move to the final milestone
[05:53] <cjwatson> bdmurray: gah, not again
[05:53] <pitti> ^ that would be the 'later' milestone, right?
[05:53] <cjwatson> I was contemplating a gutsy-updates milestone
[05:53] <pitti> or that
[05:54] <cjwatson> though mdz seemed unsure that that was kosher
[05:54] <mdz> slangasek: a good rule of thumb is that things which need to be fixed on the ISOs should get priority, since other things may be straightforward to fix in updates
[05:54] <pitti> oh, btw, another thing: we need to upload new langpacks, if possible in any way
[05:54] <mdz> cjwatson: we're abusing milestones, but I don't mind
[05:54] <pitti> ETA is on Friday evening
[05:54] <mdz> pitti: will that langpack upload fix the launchpad issue?
[05:54] <mdz> urgh, unknown
[05:55] <pitti> mdz: "the launchpad issue"?
[05:55] <MacSlow> mvo, what would the Alt-TAB issue of bug #122549 be under?
[05:55] <ubotu> Launchpad bug 122549 in compiz "[gutsy]  unredirect-fullscreen-windows option breaks gnome-screensaver locking behavior" [High,Confirmed]  https://launchpad.net/bugs/122549
[05:55] <mdz> pitti: where lots of translations are missing from the export
[05:55] <cjwatson> gutsy-updates exists as a milestone now
[05:55] <pitti> mdz: I'll manually correct the useless per-country translations which often bring bad results, yes
[05:55] <mvo> MacSlow: it used to be critical, I consider it only high now, but we definitely should try to fix it for final
[05:56] <pitti> mdz: I wasn't told about missing translations, apart from the missing ones from restricted
[05:56] <MacSlow> mvo, ok... just wanted to be verified
[05:56] <pitti> (restricted-manager, mainly); this will be fixed
[05:56] <Keybuk> mvo: I had that bug today
[05:57] <pitti> slangasek: when should we absolutely close the door for uploads? should we project the final CDs for Monday evening?
[05:57] <Keybuk> my passphrase was being typed into a web browser hidden behind the screensaver
[05:57] <Keybuk> all I could do with the unlock dialog was click the buttons
[05:57] <Keybuk> *except* I was running metacity at the time
[05:57] <Keybuk> not compiz
[05:57] <Amaranth> joy
[05:57] <Amaranth> I wonder why gnome-screensaver needs to be override-redirect
[05:57] <Amaranth> gksu does the same thing and isn't (iirc)
[05:57] <Amaranth> and that seems to be at least part of the problem
[05:58] <slangasek> pitti: by Monday evening you mean the 15th?
[05:58] <MacSlow> Keybuk, what? you had that with metacity?! Uff!
[05:58] <mdz> slangasek: the only Monday before the final release ;-)
[05:58] <Amaranth> gnome-screensaver is broken :P
[05:58] <pitti> slangasek: right
[05:58] <slangasek> pitti: if it's logistically sound that the CDs should be finalized three days before the release date, then I'm not going to disagree
[05:58] <mvo> Keybuk: holly cow, really? this happend with metacity?
[05:59] <pitti> slangasek: I was just estimating the time we need for testing them all
[05:59] <MacSlow> Amaranth, maybe we should replace gnome-screensaver with a purely plugin-based screensaver?
[05:59] <cjwatson> slangasek: it should be; certainly aiming for any later than that is a bad plan, imo
[05:59] <slangasek> ok, Monday it is ):
[05:59] <slangasek> :)
[05:59] <Amaranth> MacSlow: haha
[05:59] <pitti> slangasek: so, let's say when you wake up you build the final images?
[05:59] <slangasek> sounds good
[05:59] <pitti> slangasek: fixing a rough date and time and announcing it would be good for the team, I think
[05:59] <cjwatson> slangasek: are you in active touch with both Jonathan and Oliver for Kubuntu and Edubuntu respectively?
[06:00] <mdz> that's all the time we allocated for this meeting, if you have important work to do for the release, feel free to wander off
[06:00] <mdz> release discussion can continue here
[06:00] <mvo> Keybuk: the good news is that we used the sledgehammer and this kind of behavior should not happen with compiz. the bad news is the screengrab does not work and people can still switch workspaces (from one black/locked one to the next)
[06:01] <asac> mdz: can you bump prio for rt.admin ticket #29154 ?
[06:01] <slangasek> cjwatson: active, if infrequent to date
[06:01] <Keybuk> mvo: I think it had something to do with epiphany refreshing a web page, and having to pop up a dialog about security issues
[06:01] <Keybuk> since there was a dialog that wasn't there before
[06:01] <cjwatson> slangasek: they should be the ones to give the go for their derivatives
[06:01] <slangasek> ok
[06:01] <MacSlow> Keybuk, so the popup was stealing gnome-screensavers focus?!
[06:01] <asac> if all goes well, firefox security updates will be out on the day we release ... will gutsy security infrastructure be in place to roll that update on the same day?
[06:01] <asac> keescook: ^^ ?
[06:01] <Keybuk> MacSlow: dunno, that's my theory *shrug*
[06:02] <pitti> asac: it has been requested from the soyuz/IS teams anyway
[06:02] <mdz> asac: I can, and it's appropriate for me to do so, but it seems unlikely anything will happen before the final release
[06:02] <mvo> MacSlow: that makes sense actually, the focus behavior was what broke it with compiz too
[06:02] <mdz> asac: where is it hosted currently?
[06:02] <asac> mdz: ok ... i posted the ticket back then because elmo asked me to do so ... he felt a bit unhappy about it being hosted on people.ubuntu.com
[06:03] <mdz> asac: oh, so at least it's on a production server
[06:03] <Amaranth> oh, gksu is override-redirect
[06:03] <Amaranth> and uses basically the same code as gnome-screensaver (the important bits are actually copied from gnome-screensaver)
[06:03] <Amaranth> but gksu doesn't have this problem, ever
[06:03] <cjwatson> I would be happier with ubufox moving post-release, I think
[06:03] <asac> mdz: problem is that cannot include upstream plugin results because i am not allowed to call pfs.mozilla.org from peope.ubuntu.com
[06:03] <cjwatson> seems a bit late now to be sure that the new service is working
[06:04] <asac> mdz: e.g. due to firewall rules
[06:04] <slangasek> asac: the information I've gotten so far indicates that there's a logistics problem with trying to have gutsy-security live day-one because of the dak one-time import
[06:04] <pitti> last time it took three days...
[06:04] <mdz> asac: it seems to include upstream plugin results for me...are you working around it?
[06:04] <cjwatson> slangasek is correct
[06:04] <cjwatson> usually takes a few days
[06:04] <pitti> we continuously get promised that -security moves to LP, but it seems to take a while still
[06:05] <mdz> slangasek: is there an RT open for that import?
[06:05] <asac> mdz: no you see only results that are packaged ... but not the pristine upstream .xpi result
[06:05] <slangasek> mdz: #29225
[06:05] <cjwatson> if we freeze the archive solid a couple of days before release, the import could start early
[06:05] <mdz> asac: eek...
[06:05] <mdz> asac: seems like this should have been raised earlier
[06:06] <pitti> cjwatson: that would be nice indeed
[06:06] <slangasek> cjwatson: which seems to only be a question of moving the window during which gutsy security updates aren't possible?
[06:06] <mdz> slangasek: that's not even in a queue yet; I can't view it
[06:06] <pitti> calc: do you think we can get the new OO.o by tomorrow, so that it can shake out over the weekend?
[06:06] <slangasek> mdz: er, ok; it's been responded to by elmo
[06:07] <cjwatson> slangasek: in practice they're more or less out of the question in the day before release anyway
[06:07] <cjwatson> since the buildds need to quiesce
[06:07] <slangasek> sure
[06:07] <mdz> slangasek: he probably forgot to put it in the distribution queue
[06:09] <slangasek> cjwatson: so timeline here would be: final images Monday evening, freeze the archive at the same time; testing starts; if there are no showstoppers by Tuesday, begin the gutsy-security dak import?
[06:09] <slangasek> (and if there are showstoppers after Tuesday, abort & restart?)
[06:09] <cjwatson> I think the dak import is resumable to some extent
[06:09] <Hobbsee> slangasek: main and universe at that point, i take it?
[06:09] <cjwatson> (though best check that with James, I only have a sketchy knowledge of what's involved)
[06:10] <asac> mdz: sorry ... thought i had a screenshot that shows you how upstream results would look like ... anyway, i think its unfortunate, but not a big issue. afaik upstream database just has adobe flash for linux.
[06:10] <slangasek> Hobbsee: yes
[06:10] <Hobbsee> slangasek: and, as the RM, do you plan to actually notify ubuntu-motu ML about the timelines?
[06:10] <slangasek> Hobbsee: this question seems to have only one right answer ;)
[06:10] <Hobbsee> s/actually//
[06:11] <mdz> asac: oh, I thought there was more thene
[06:11] <mdz> asac: there
[06:11] <Hobbsee> slangasek: well, yes, it does have an effect on whether you'll have a lot of people angry at you and canonical, and whether you'll get poked with the Long Pointy Stick of DOOM!!!!!!!!!!!!!!! 
[06:11] <mdz> asac: if they have the same plugins we do, then it's nothing to worry about
[06:12] <cjwatson> Hobbsee: (last I checked, final-week uploads even in universe required approval ...)
[06:12] <mdz> Hobbsee: assuming the wiki docs include the necessary notifications, I'm sure he will remember
[06:12] <Hobbsee> mdz: they didnt last time, so i'm just double checking
[06:12] <cjwatson> oh, damn, I still need to move ReleaseCandidateProcess and ReleaseProcess to wiki.ubuntu.com
[06:12] <cjwatson> I'll do that today
[06:12] <Hobbsee> cjwatson: oh right, i wasnt aware.  somewhat scary, seeing as i'm on that too.
[06:13] <cjwatson> Hobbsee: end of https://wiki.ubuntu.com/FreezeExceptionProcess
[06:13] <asac> mdz: yes ... but we should definitly implement it ... if not now then through a SRU at some point. upstream asked us to keep their preferred result in the list.
[06:13] <sladen> bdmurray: will you be my guinea pig if we go back to the off centre issie?
[06:13] <cjwatson> but I agree it's not clear on when the hard lockdown is
[06:13] <Hobbsee> cjwatson: i'llb et MOTU-uvf doesnt know about that.  but OK.
[06:14] <bdmurray> sladen: I'll be your huckleberry
[06:14] <asac> mdz: http://people.ubuntu.com/~asac/pfs/screens/pfs3.png ... the blue earth is "install from internet"
[06:17] <pitti> ok, seems we're done here? release stuff should go to #u-release
[06:18] <seb128> thanks
[06:18] <pitti> thanks all
[06:39] <mdz> #endmeeting
[06:39] <MootBot> Meeting finished at 17:39.
[06:40] <cjwatson> mootbot should garbage-collect meetings
[06:42] <Keybuk> cjwatson: don't the scribes take care of that?
[06:43] <kraut> @schedule berlin
[06:43] <ubotu> Schedule for Europe/Berlin: 16 Oct 18:00: Kernel Team | 17 Oct 18:00: QA Team | 23 Oct 17:00: Server Team | 23 Oct 18:00: Kernel Team | 30 Oct 17:00: Kernel Team | 08 Nov 16:00: Community Development Team
[06:43] <kraut> hmmm, the kernel team seems to be busy ;)