[11:06] <sabdfl> hi folks, sorry i'm late
[11:07] <dholbach> oops, I didn't pay attention either, let me ping the rest of the gang
[11:07] <sabdfl> dholbach, agenda is empty
[11:07] <dholbach> mako, technoviking, popey, persia, pleia2: around for CC meeting?
[11:08] <dholbach> one thing I just want to check quickly is how we're doing with the restaffing of various teams
[11:09] <dholbach> I know that a lot of CC members still need to vote for the Americas Board restaffing
[11:09] <dholbach> pleia2 sent a mail about this a while ago
[11:09] <dholbach> and I think the Asia/Oceania board is still looking for nominees
[11:10] <dholbach> the next ones are
[11:10] <dholbach>  - 2011-09-01	Technical Board
[11:10] <dholbach>  - 2011-10-07	Community Council
[11:10] <dholbach> until we luckily still have some time
[11:10] <dholbach> that's all I wanted to bring up
[11:10] <dholbach> sabdfl, do you have anything you'd like to discuss?
[11:10] <dholbach> I'm happy to dig the participants of the Asia/Oceania thread again to see where things stand
[11:11] <dholbach> (and urge everybody else to have a look in their inbox and reply to Liz' email about the Americas Board)
[11:13] <popey> oh hai
[11:13] <sabdfl> hey popey
[11:13] <coalwater> hi all :D mind if i join ? i probably wont be any useful but ill just see what's going on
[11:13] <popey> Afternoon.
[11:14] <dholbach> coalwater, sure, all the meetings in here are public
[11:15] <dholbach> Is there anything else we need to discuss?
[11:16] <sabdfl> dholbach, i didn't have anything else
[11:17] <sabdfl> popey, dholbach, i think we can wrap?
[11:17]  * popey voted
[11:17] <popey> I have nothing else.
[11:17] <dholbach> yes, I think we can - I'll reply to the Asia/Oceania restaffing thread right now
[11:18] <dholbach> thanks a lot everyone
[11:21] <popey> I like quick meetings. Especially at lunchtime!
[11:21] <sabdfl> cheerio
[16:00] <smb> \o
[16:00] <NCommander> \o
[16:00] <cking> \O
[16:00] <Daviey> o/
[16:00] <jamespage> o/
[16:00] <Daviey> <-- OTP
[16:00] <m_3> o/
[16:00] <cking> oops, wrong meeting, sorry
[16:00] <Daviey> (NCommander has requested to go early in the meeting Agenda.)
[16:01] <Daviey> SpamapS: ping?
[16:02] <SpamapS> Daviey: pong
[16:02] <Ursinha> o/
[16:02] <SpamapS> is it my turn?
[16:03] <Daviey> SpamapS: i believe so
[16:03] <SpamapS> #startmeeting
[16:03] <MootBot> Meeting started at 11:03. The chair is SpamapS.
[16:03] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:03] <SpamapS> indeed it is
[16:03] <SpamapS> Welcome!
[16:03] <SpamapS> [TOPIC] Review ACTION points from previous meeting
[16:03] <MootBot> New Topic:  Review ACTION points from previous meeting
[16:03] <SpamapS> sommer and j1mc to look at doc presentation (continued)
[16:04] <SpamapS> neither are here, so we will defer
[16:04] <SpamapS> [ACTION] sommer and j1mc to look at doc presentation (continued x 2)
[16:04] <MootBot> ACTION received:  sommer and j1mc to look at doc presentation (continued x 2)
[16:04] <SpamapS> [TOPIC] Oneiric Development
[16:04] <MootBot> New Topic:  Oneiric Development
[16:04] <SpamapS> git 'r dun
[16:05] <Daviey> o/
[16:05] <Daviey> Full cycle tracking: - http://status.ubuntu.com/ubuntu-oneiric/group/topic-oneiric-server-overview.html
[16:05] <Daviey> We seem to be pretty much on target, with:
[16:05] <Daviey> server-boot-experience - slightly flagging.  However, this is expected to be brought up to state this week.
[16:05] <Daviey> server-o-jenkins - is making good progress but limited by Ubuntu AA review / Debian sponsoring, as i understand it.
[16:05] <Daviey> server-o-postfix-enhancements - Seems to be unstarted, this should probably make progress soon - or consider dropping (ScottK?).
[16:05] <Daviey> server-o-trusted-cloud - Is this the same status? (hallyn?)
[16:05] <Daviey> Bugs currently being tracked for Oneiric Release: - http://people.ubuntu.com/~davewalker/release-bugs.html
[16:05] <Daviey> (For the TL;DR'ers, we are doing OK.  However, please try to keep the bug status of those as updated as possible).
[16:06] <Daviey> If there is a bug you are aware of, or currently working on that isn't on that list - please can you raise it here, or with me afterwards.  Thanks.
[16:06] <Daviey> Sync's/Merges: - http://people.ubuntu.com/~davewalker/server-sid-new.html (We are doing ok!)
[16:06] <serue_> Daviey: trusted cloud shoudl be dropped
[16:06] <Daviey> Ursula will be commenting on incomming bug process in AoB i believe.
[16:06] <Daviey> Thanks!
[16:06] <Daviey> EOM.
[16:06] <Ursinha> yes sir
[16:06] <Daviey> serue_: thanks.
[16:07] <SpamapS> Alright, shall we then?
[16:07] <Daviey> pls
[16:07] <SpamapS> [TOPIC] Ubuntu Server Team Events
[16:07] <MootBot> New Topic:  Ubuntu Server Team Events
[16:07] <SpamapS> o/
[16:08] <SpamapS> I'll be speaking at OSCON 2011 http://www.oscon.com/oscon2011/public/schedule/detail/18367
[16:08] <SpamapS> July 28
[16:08] <SpamapS> in Portland
[16:08] <SpamapS> Any others?
[16:09] <SpamapS> Alright then
[16:09] <SpamapS> [TOPIC] Weekly Updates & Questions for the QA Team (hggdh)
[16:09] <MootBot> New Topic:  Weekly Updates & Questions for the QA Team (hggdh)
[16:09] <SpamapS> hggdh: you're up
[16:10] <hggdh> k
[16:10] <hggdh> we are releasing 10.04.3 this week; help on the testing is welcomed
[16:11] <hggdh> also, a new milestone on Oneiric is approaching...
[16:11] <hggdh> apart from that, life is good
[16:11] <hggdh> ..
[16:12]  * SpamapS is installing a 10.04.3 RAID1 vm right now.. :)
[16:12]  * smb is reminded to go for two more installs ...
[16:12] <SpamapS> [TOPIC] Weekly Updates & Questions for the Kernel Team (smb)
[16:12] <MootBot> New Topic:  Weekly Updates & Questions for the Kernel Team (smb)
[16:12] <smb> hi there
[16:13] <smb> So there seems to be acceptance to take back the changes in xen xvd naming
[16:13] <smb> Though it seems to target 3.1
[16:13] <smb> Which means I will have to pull back that as soon as I think there are no other objections
[16:14] <smb> Apart from that I am trying to get xen hvm running in oneiric. Currently being in contact with citrix on that
[16:14] <smb> But zul probably has some other info too
[16:14] <smb> ..
[16:15] <SpamapS> zul is out this week.. do we need any actions for follow up next week?
[16:16] <smb> No, either I'll contact him next week or I get something from Stefano
[16:16] <SpamapS> ok
[16:16] <SpamapS> [TOPIC] Weekly Updates & Questions regarding Ubuntu ARM Server (NCommander)
[16:16] <MootBot> New Topic:  Weekly Updates & Questions regarding Ubuntu ARM Server (NCommander)
[16:17] <SpamapS> NCommander: ^
[16:17] <NCommander> Hey all
[16:17] <NCommander> ARM Server is currently working towards our first image bringup, with the work on preinstall pool being completed and in the process of deployment
[16:18] <NCommander> in addition, PXE'able images are now available for OMAP3/4, which also works to remove a blocker for ensemble deployment on ARM
[16:18] <SpamapS> NCommander: ogra_ had proposed an optional upstart job that would add a serial console.. is that still needed?
[16:18] <NCommander> As we close in on A3, a lot of effort is going into heavily QAing stuff on ARM, and in general, simply pipecleaning all our mechanisms
[16:18] <NCommander> SpamapS: I think it got implemented post-Dublin (ogra is on vacation so I can't immediatley confirm)
[16:19] <SpamapS> NCommander: ok just checking.
[16:19] <SpamapS> Anything else?
[16:19] <NCommander> Nope, that's it
[16:20] <SpamapS> [TOPIC] Weekly Updates & Questions from the Ubuntu Community
[16:20] <MootBot> New Topic:  Weekly Updates & Questions from the Ubuntu Community
[16:21] <SpamapS> speak now or forever hold your peace. :)
[16:21] <m_3> term
[16:22] <SpamapS> [TOPIC] Open Discussion
[16:22] <MootBot> New Topic:  Open Discussion
[16:22] <SpamapS> Ursinha: nice job on the report!
[16:23] <SpamapS> Ursinha: I love the ubuntu-server-bot idea. :)
[16:23] <Ursinha> cool!
[16:23] <Ursinha> so, we're working on changing the bug triage process and add speed to it
[16:23] <Daviey> \o/
[16:24] <Ursinha> the main proposed change is, in a first moment, to set the importance of the bug, even if we don't have a status to set
[16:24] <Ursinha> this will help us prioritizing what to investigate next.
[16:24] <Ursinha> the report SpamapS mentioned is: http://people.canonical.com/~ursula/triage-report.html
[16:25] <Ursinha> we hope to be able to find and kill duplicates easily, as well
[16:25] <Ursinha> clean the mess so we can be awesome
[16:26] <Ursinha> The changes in the process are described in: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase
[16:27] <SpamapS> [ACTION] All: review new triage process at https://wiki.ubuntu.com/ServerTeam/KnowledgeBase
[16:27] <MootBot> ACTION received:  All: review new triage process at https://wiki.ubuntu.com/ServerTeam/KnowledgeBase
[16:27] <utlemming> Ursinha: how often will the report be updated?
[16:27] <Daviey> Great Stuff!  Thanks Ursinha
[16:27] <Ursinha> stats information to be added in that report soon! we'll be able to tell how many bugs are we triaging daily and weekly, and how new bugs are being handled
[16:27] <Ursinha> utlemming: every ten minutes
[16:28] <utlemming> very cool
[16:28] <Ursinha> enjoy! :)
[16:28] <Ursinha> ..
[16:29] <SpamapS> Alright, anything else?
[16:29] <SpamapS> [TOPIC] Announce next meeting date and time
[16:29] <MootBot> New Topic:  Announce next meeting date and time
[16:30] <SpamapS> Tuesday 2011-07-26 at 1600 UTC here in #ubuntu-meeting
[16:30] <SpamapS> thanks everyone!
[16:30] <SpamapS> #endmeeting
[16:30] <MootBot> Meeting finished at 11:30.
[16:30] <Ursinha> thanks SpamapS and guys
[16:31] <m_3> thanks... sorry for the unitylockup-inspired Tourette's in the middle of the meeting
[16:32] <Ursinha> m_3: lol
[16:32] <Ursinha> :)
[17:00] <bjf> #startmeeting
[17:00] <MootBot> Meeting started at 12:00. The chair is bjf.
[17:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[17:00]  * smb still here
[17:00] <bjf> ##
[17:00] <bjf> ## This is the Ubuntu Kernel Team weekly status meeting.
[17:00] <bjf> ##
[17:00] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Oneiric
[17:00] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Oneiric
[17:00] <bjf> # Meeting Etiquette
[17:00] <bjf> #
[17:00] <bjf> # NOTE: '..' indicates that you are finished with your input.
[17:00] <bjf> #       'o/' indicates you have something you'd like to add (wait until you are recognized)
[17:00] <bjf> #
[17:00] <bjf> [TOPIC] ARM Status (ppisati)
[17:00] <MootBot> New Topic:  ARM Status (ppisati)
[17:00] <ppisati> Kernel development: nothing to report.
[17:00] <ppisati> Oneiric/ti-omap4: got a new BSP drop from agreen, rebased on top of rc7 and rolled out a new kernel. People in the arm team are testing it and so far (besides an audio bug that looks like a pulseaudio issue) it looks good. A kernel package is available here: http://people.canonical.com/~ppisati/ti-omap4-next/ while the source code is available on ppisati@zinc:oneiric-git/ti-omap4-next.
[17:01] <ppisati> ..
[17:01] <bjf> [TOPIC] Release Metrics and Incoming Bugs (ogasawara)
[17:01] <MootBot> New Topic:  Release Metrics and Incoming Bugs (ogasawara)
[17:01] <ogasawara> [17:01] <ogasawara> [LINK] http://reports.qa.ubuntu.com/reports/ogasawara/kt-meeting.txt
[17:01] <MootBot> LINK received:  http://reports.qa.ubuntu.com/reports/ogasawara/kt-meeting.txt
[17:01] <ogasawara> [17:01] <ogasawara>  * 28 linux kernel bugs (up 8)
[17:01] <ogasawara> [17:01] <ogasawara>  * 2 linux kernel bugs (up 2)
[17:01] <ogasawara> [17:01] <ogasawara>  * 0 linux kernel bugs (no change 0)
[17:01] <ogasawara> [17:01] <ogasawara>  * 23 linux kernel bugs (up 1)
[17:01] <ogasawara> [17:01] <ogasawara>  * 3 linux kernel bugs (no change 0)
[17:01] <ogasawara> [17:01] <ogasawara>  * 7 linux kernel bugs (down 1)
[17:01] <ogasawara> [17:02] <ogasawara>  * 0 linux kernel bugs (no change 0)
[17:02] <ogasawara> [17:02] <ogasawara>  * 62 oneiric bugs (up 13)
[17:02] <ogasawara>  * 1420 natty bugs (up 34)
[17:02] <ogasawara>  * 1103 maverick bugs (down 13)
[17:02] <ogasawara>  * 968 lucid bugs (down 45)
[17:02] <ogasawara>  * 33 hardy bugs (down 2)
[17:02] <ogasawara> [17:02] <ogasawara> [17:02] <ogasawara>  * 0 oneiric bugs (no change 0)
[17:02] <ogasawara>  * 6 natty bugs (no change 0)
[17:02] <ogasawara>  * 43 maverick bugs (no change 0)
[17:02] <ogasawara>  * 82 lucid bugs (down 1)
[17:02] <ogasawara>  * 0 hardy bugs (no change 0)
[17:02] <ogasawara> [17:02] <ogasawara>  * 0 oneiric bugs (no change 0)
[17:02] <ogasawara>  * 444 natty bugs (up 1)
[17:02] <ogasawara>  * 242 maverick bugs (down 3)
[17:02] <ogasawara>  * 217 lucid bugs (down 4)
[17:02] <ogasawara>  * 2 hardy bugs (no change 0)
[17:02] <ogasawara> [17:02] <ogasawara>  * 0 oneiric bugs (no change 0)
[17:02] <ogasawara>  * 2 natty bugs (no change 0)
[17:02] <ogasawara>  * 2 maverick bugs (no change 0)
[17:02] <ogasawara>  * 0 lucid bugs (no change 0)
[17:02] <ogasawara>  * 0 hardy bugs (no change 0)
[17:02] <ogasawara> ..
[17:03] <bjf> [TOPIC] Blueprints: Oneiric Delta Review (ogasawara)
[17:03] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/other-kernel-o-ubuntu-delta-review
[17:03] <MootBot> New Topic:  Blueprints: Oneiric Delta Review (ogasawara)
[17:03] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/other-kernel-o-ubuntu-delta-review
[17:03] <ogasawara> apw, lag, ralveti: you have work items to review your set of Ubuntu patches.  I've pushed these out to Alpha-3 for you.  Please take a moment to review when you have a chance. See https://wiki.ubuntu.com/KernelTeam/Specs/KernelOneiricUbuntuDeltaReview for your specific set of patches.  Note, these are the only remaining work items for this blueprint.
[17:03] <ogasawara> ..
[17:03] <bjf> [TOPIC] Blueprints: Oneiric Server Requirements (smb)
[17:03] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/other-kernel-o-server-requirements
[17:03] <MootBot> New Topic:  Blueprints: Oneiric Server Requirements (smb)
[17:03] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/other-kernel-o-server-requirements
[17:03] <smb> No change here. As the remains items are pretty much depending on outcome of something else and either fall off completely or get pushed out as we go, I am not sure it really needs to be on the agenda anymore. Would people mind dropping it?
[17:04] <smb> ..
[17:04] <apw> if there is nothing to report, drop it ..
[17:04] <ogasawara> +1 drop it
[17:04] <jjohansen> +1
[17:04] <smb> ok, will make sure it gets off
[17:04] <smb> ..
[17:04] <bjf> will be done
[17:04] <bjf> [TOPIC] Status: General Oneiric (ogasawara)
[17:04] <MootBot> New Topic:  Status: General Oneiric (ogasawara)
[17:04] <ogasawara> Nothing very exciting this past week.  I plan to do an upload today or tomorrow to get patches on master-next released.  Alpha-3 is Thurs Aug 4th.  I intend to upload our final Alpha-3 kernel next Friday July 29th.  If there are any patches that need to land for Alpha-3, get them sent to the kt-ml asap.
[17:04] <smb> bjf, even better thanks
[17:05] <ogasawara> ..
[17:05] <bjf> [TOPIC] Status: CVE's (apw)
[17:05] <MootBot> New Topic:  Status: CVE's (apw)
[17:05] <apw> [17:05] <apw> [LINK] http://people.canonical.com/~apw/cve/pkg/CVE-linux.txt
[17:05] <MootBot> LINK received:  http://people.canonical.com/~apw/cve/pkg/CVE-linux.txt
[17:05] <apw> We have made good progress recently with most branches only having a single CVE open; CVE-2011-1020 for which the fixes were just identified.
[17:05] <apw> Currently open CVEs for each supported branch:
[17:05] <apw> || Package                                  || Open ||
[17:05] <apw> ||                                          ||      ||
[17:05] <apw> || linux Hardy                              ||    5 ||
[17:05] <apw> || linux Lucid                              ||    1 ||
[17:05] <apw> || linux Maverick                           ||    1 ||
[17:05] <apw> || linux Natty                              ||    1 ||
[17:05] <apw> || linux Oneiric                            ||    1 ||
[17:05] <apw> || linux-ec2 Lucid                          ||    1 ||
[17:05] <apw> || linux-fsl-imx51 Lucid                    ||    4 ||
[17:05] <apw> || linux-mvl-dove Lucid                     ||    1 ||
[17:05] <apw> || linux-mvl-dove Maverick                  ||    1 ||
[17:05] <apw> || linux-ti-omap4 Maverick                  ||    1 ||
[17:05] <apw> || linux-ti-omap4 Natty                     ||    1 ||
[17:06] <apw> || linux-ti-omap4 Oneiric                   ||    1 ||
[17:06] <apw> || linux-lts-backport-maverick Lucid        ||    1 ||
[17:06] <apw> || linux-lts-backport-natty Lucid           ||    1 ||
[17:06] <apw> ..
[17:06] <bjf> [TOPIC] Status: Stable Kernel Team (sconklin)
[17:06] <MootBot> New Topic:  Status: Stable Kernel Team (sconklin)
[17:06] <sconklin> ||== Status of kernels ==
[17:06] <sconklin> ||
[17:06] <sconklin> || Several regressions have been reported in Natty after release last week,
[17:06] <sconklin> || None of these were detected in QA, Certification, or -proposed testing.
[17:06] <sconklin> ||
[17:06] <sconklin> || * [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/810400|Disks not recognized after upgrading to 2.6.38-10]]
[17:06] <sconklin> || * [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/811240|Update to kernel 2.6.38-10 causes hang on startup]]
[17:06] <sconklin> || * [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/809878|Wireless network & graphics card stop working after upgrade to 2.6.38-10]]
[17:06] <sconklin> ||
[17:06] <sconklin> || This is kernel prep week, getting set up to begin a verification cycle next week.
[17:06] <sconklin> || Several kernels have already been built and are in -proposed
[17:06] <sconklin> ||
[17:06] <sconklin> || * [[http://people.canonical.com/~kernel/reports/sru-report.html|Detailed Information Here]]
[17:06] <sconklin> ||
[17:06] <sconklin> ||[17:06] <sconklin> || * [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/812360|Hardy Tracking Bug]]
[17:06] <sconklin> || * A new kernel is in -proposed. Since this kernel contains only CVE fixes, there is no verification to be done, and it is ready for QA
[17:06] <sconklin> ||
[17:07] <sconklin> ||[17:07] <sconklin> || * Previous kernel has been released, but a new one has not been prepared yet
[17:07] <sconklin> ||
[17:07] <sconklin> ||[17:07] <sconklin> || * [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/808934|Maverick Tracking Bug]]
[17:07] <sconklin> || * Kernel in -proposed from the last cycle is awaiting certification and regression testing.
[17:07] <sconklin> ||
[17:07] <sconklin> ||[17:07] <sconklin> || * [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/811180|Natty Tracking Bug]]
[17:07] <sconklin> || * Previous kernel has been released, and a new one is in -proposed.
[17:07] <sconklin> || * Verification has begun for this kernel, and will continue through next week.
[17:07] <sconklin> ||
[17:07] <sconklin> ..
[17:07] <bjf> [TOPIC] Security & bugfix kernels - Maverick/Lucid/Hardy (sconklin)
[17:07] <MootBot> New Topic:  Security & bugfix kernels - Maverick/Lucid/Hardy (sconklin)
[17:07] <sconklin> ||
[17:07] <sconklin> || Current Kernel versions are always available here: http://people.canonical.com/~kernel/reports/versions.html
[17:07] <sconklin> ||
[17:07] <sconklin> || Package                                    || Upd/Sec              || Proposed             ||  TiP || Verified ||
[17:07] <sconklin> ||                                            ||                      ||                      ||      ||          ||
[17:07] <sconklin> || hardy    linux                             || 2.6.24-29.91         || 2.6.24-29.92         ||    0 ||        0 ||
[17:07] <sconklin> || lucid    linux-meta-lts-backport-maverick  || <IP_ADDRESS>.36         || <IP_ADDRESS>.38         ||    0 ||        0 ||
[17:08] <sconklin> || ---      linux-lts-backport-maverick       || 2.6.35-25.44~lucid1  || 2.6.35-30.56~lucid1  ||   22 ||       22 ||
[17:08] <sconklin> || ---      linux-firmware                    || 1.34.7               || 1.34.10              ||    0 ||        0 ||
[17:08] <sconklin> || maverick linux-firmware                    || 1.38.6               || 1.38.8               ||    1 ||        0 ||
[17:08] <sconklin> || ---      linux                             || 2.6.35-30.54         || 2.6.35-30.56         ||    1 ||        1 ||
[17:08] <sconklin> || natty    linux-meta-ti-omap4               ||                      || <IP_ADDRESS>9.7        ||    0 ||        0 ||
[17:08] <sconklin> || ---      linux-backports-modules-2.6.38    || 2.6.38-10.6          || 2.6.38-11.7          ||    0 ||        0 ||
[17:08] <sconklin> || ---      linux-firmware                    ||                      || 1.52.1               ||    0 ||        0 ||
[17:08] <sconklin> || ---      linux                             || 2.6.38-10.46         || 2.6.38-11.47         ||   18 ||        5 ||
[17:08] <sconklin> || ---      linux-ti-omap4                    ||                      || 2.6.38-1209.13       ||   10 ||       10 ||
[17:08] <sconklin> || ---      linux-meta                        || <IP_ADDRESS>.25         || <IP_ADDRESS>.26         ||    0 ||        0 ||
[17:08] <sconklin> ||
[17:08] <sconklin> ..
[17:09] <bjf> [TOPIC] Open Discussion or Questions: Raise your hand to be recognized (o/)
[17:09] <MootBot> New Topic:  Open Discussion or Questions: Raise your hand to be recognized (o/)
[17:09] <bjf> thanks everyone
[17:09] <bjf> #endmeeting
[17:09] <MootBot> Meeting finished at 12:09.
[17:09] <apw> thanks bjf
[17:09] <sconklin> thanks
[17:09] <smb> thanks
[17:09]  * smb wanders off
[17:09] <cking> nice one
[19:57] <Dazed_75> I thought there was a re-approval meeting scheduled for the upcoming hour.  But we got an email that the deadline had passed.  Does anyone know what happened?
[19:57] <Dazed_75> for the Arizona LoCo BTW
[19:59] <czajkowski> Dazed_75: the meeting is on in 2 mins
[19:59] <czajkowski> but we received no application for the team
[19:59] <czajkowski> did you update the bug with the application before today ???
[20:00] <Dazed_75> Hmmm, the team leader sent me an email saying we had been unnapproved because the deadline had passed so he would talk to me tonight.  Let me try calling him
[20:00] <czajkowski> well you've been given 9 months to get the application in
[20:01] <czajkowski> it was due in last cycle
[20:01] <czajkowski> and we gave a further 3 months to get it in
[20:01] <Dazed_75> phone
[20:03] <Dazed_75> he does not answer.  The team leaders basically disappeared.  Todd Cole took over and has been working to get thing organized for this re-approval meeting which is now
[20:03] <czajkowski> well it wasn;t added to the agenda
[20:03] <czajkowski> and we have no application
[20:03] <czajkowski> so perhaps for the next meeting
[20:04] <czajkowski> or add the information to the bug you were added to for re approval
[20:04] <Dazed_75> This is who Todd was workign with: > From<EMAIL_ADDRESS>[20:04] <huats> Dazed_75, the thing that bother me
[20:05] <huats> is that there is no answer regarding the application but we have received an application for free banners for loco teams
[20:05] <Dazed_75> actually, we received the banners a couple days ago and it was a surprise neither Todd or I knew about
[20:06] <czajkowski> Dazed_75: see that's kinda unfair
[20:06] <czajkowski> you were given 9 months to get reapproved
[20:06] <huats> Dazed_75, you received the banners?
[20:06] <Dazed_75> this is the bug we were on: Subject: [Bug 766541] Re: Re-approval, ubuntu-arizona
[20:06] <czajkowski> so up until then we gave it in good faith you would give us the application
[20:07] <Dazed_75> the people in charge 9 months ago basically disappeared.  We had a very hard time communicating anything to/from them
[20:08] <czajkowski> Dazed_75: all I can say is this.
[20:08] <czajkowski> please submit in your application as soon as ye can
[20:08] <czajkowski> but until then ye will remain unapproved
[20:08] <Dazed_75> I think Todd thought that was to be done in this meeting.  Has been very hard to find info on the process (Todd told me, as I just jjoined this past week)
[20:08] <Dazed_75> though I have been involved in events for years
[20:09] <czajkowski> https://wiki.ubuntu.com/LoCoGettingApproved
[20:09] <czajkowski> https://wiki.ubuntu.com/LoCoCouncil/LoCoTeamReApproval
[20:09] <czajkowski> there are wiki pages dedicated to this
[20:09] <czajkowski> there are 6 people on the council to come and ask for help
[20:11] <Dazed_75> Like I said, I just joined and was made co -leader but have no experience with this process.  I know Todd had been working on that wiki approval page but do not know if he knew he had to submit it via a process.  Thanks foor the info
[20:11] <czajkowski> ok
[20:11] <czajkowski> perhaps mail us afterwards ok
[20:11] <itnet7> Dazed_75: As czajkowski has said, put yourself on the agenda for next month. If you need any help reach out to us
[20:12] <itnet7> we'll give you a hand
[20:12] <Dazed_75> Alright.  Thanks itnet7
[20:12] <itnet7> Or I'll give you one
[20:13] <Dazed_75> If no one minds I will capture this log and send it to Todd
[20:13] <popey> o/
[20:13] <popey> sorry, dodgy connection
[20:13] <Dazed_75> huats: Todd tells me we got a box with some bbanners
[20:14] <itnet7> No problem Dazed_75 !
[20:14] <huats> Dazed_75, I'll send an email to Todd then to ask him who he asked to get it then
[20:15] <Dazed_75> I don't think he asked for them, so that will be an interesting answer
[20:15] <czajkowski> indeed
[20:15] <czajkowski> huats: popey itnet7 anything we need to discuss as it's just the 4 of us ?
[20:15] <huats> Dazed_75, well he emailed me at least about it
[20:16] <huats> czajkowski, nope
[20:16] <huats> :)
[20:16] <czajkowski> well we have no agenda
[20:16] <popey> quiet one
[20:16] <czajkowski> and no teams
[20:16] <czajkowski> so unless we need to talk about stuff ??
[20:18] <czajkowski> if that's a no then we can leave it
[20:19] <czajkowski> ok well Good night so
[20:21] <huats> good night too
[20:22] <paultag> Hey, sorry I'm late
[20:23] <huats> paultag, don't worry it is over
[20:23] <paultag> oh joy. Righto
[20:42] <zakame> ping
[20:42] <Knightlust> czajkowski: er... so there won't be any meeting  in a few minute
[20:42] <Knightlust> s/minute/minutes/
[20:43] <czajkowski> Knightlust: meeting started 43 mins ago and ran for 20 mins as we had no agenda
[20:43] <Knightlust> arrggh, timezone
[20:44] <arscariosus> whoa
[20:46] <zakame> hm I was under the impression the meet happens 3rd Tuesday of every month at 21:00 UTC, per LoCoCouncil/Agenda
[20:56] <cody-somerville> 'The LoCo Council meets on the 3rd Tuesday of every month at 21:00 UTC. The next meeting is scheduled for Tuesday 19th July 2011, 20:00 UTC'


[09:51] <thrilla> anybody wanna buy some weed?
[09:51] <thrilla> lol
[09:53] <thrilla> for real though I'm in Dublin, selling weed
[09:53] <thrilla> so if anybody wants to buy some....


[04:41] <Zephyron> hello, anyone there?
[05:48] <ochosi> morning everyone
[09:00] <baizon> any news when xfce 4.10 will land in the xfce-dev ppa?
[09:01] <ochosi> it seems that the build in mr_pouit's ppa is fairly complete, so it won't be too long i guess
[09:01] <ochosi> (i'm using that now and it works great so far)
[09:01] <baizon> ok
[09:01] <baizon> thanks
[09:01] <ochosi> np
[09:04] <mr_pouit> I need to solve an upgrade issue first, apt holds back xfce4-session, xfce4-appfinder and xubuntu-desktop by default
[09:05] <ochosi> true, but on a second upgrade it upgrades these as well
[09:05] <ochosi> (without issues it seems)
[09:05] <mr_pouit> yeah, but that's not optimal ;-)
[09:05] <ochosi> agreed ;)
[09:05] <ochosi> just sayin, it ain't that bad
[09:13] <ochosi> would you guys agree that this is (too) hard to read? http://www.zimagez.com/zimage/screenshot-05072012-111314am.php
[10:37] <knome> ochosi, heh, yeah, it's not optimal
[10:37] <knome> ochosi, readable at least for me, but not optimal
[10:37] <knome> ochosi, same as the orange warning
[11:09] <ochosi> knome: already fixed it in git
[11:09] <knome> mm-hmm
[11:09] <ochosi> i'm wondering though whether i should make the button blend in with the infobar
[11:10] <ochosi> like this: http://www.zimagez.com/zimage/screenshot-05072012-011001pm.php
[11:10] <knome> huh!
[11:10] <knome> no
[11:10] <knome> that's quite ugly
[11:11] <ochosi> not sure i'd really say it's ugly
[11:11] <ochosi> but anyway, i don't have time for this now
[11:15] <knome> well imo it is ;)
[11:16] <ochosi> have you found time to test the social icons on x.org?
[11:16] <knome> not yet :|
[11:16] <knome> maybe soon, but it's still under *huge* caching :<
[11:21] <ochosi> btw, it seems that audience
[11:21] <ochosi> gah
[11:21] <knome> heh
[11:21] <ochosi> audience's use of clutter slows it down quite a bit
[11:21] <knome> :/
[11:21] <ochosi> in average, around 15% more cpu usage than parole
[11:21] <ochosi> even though both use the same backend (gstreamer)
[11:21] <knome> bleh
[11:21] <ochosi> on the plus-side, it has a codec-detection + install dialog
[11:22] <ochosi> which would be desirable for parole as well
[11:23] <knome> 15% more cpu, but about how much in exact numbers
[11:23] <ochosi> that other gnome-project i put on the roadmap also uses clutter iirc, so it might have similar issues
[11:23] <knome> i mean, how much processing power is that
[11:23] <ochosi> that depends on many variables, e.g. whether vdpau was in use with my nvidia-driver
[11:23] <ochosi> so i'm not sure
[11:24] <ochosi> but it was ~15% of one my two cores
[11:24] <ochosi> in total ~40% audience-process and ~20% Xorg
[11:24] <ochosi> with parole: 35% parole-process and 10% Xorg
[11:25] <knome> hmm.
[11:25] <ochosi> that was an "average" video in ~720p
[11:25] <ochosi> avi, but i
[11:25] <ochosi> 'm not sure what compression
[11:25] <ochosi>  /codec
[11:26] <ochosi> btw, i'm wondering whether i should change the fg-color of the infobar to white
[11:27] <ochosi> like this: http://www.zimagez.com/zimage/screenshot-05072012-012708pm.php
[11:27] <ochosi> it's a bit more "in your face" than the dark fg color though
[11:33] <knome> mmhmm
[11:46] <jpff> hi -- just a moment
[11:48] <jpff> Sorry -- wrong window
[20:03] <knome> pleia2, which session are you going to attend one hour later?
[20:07] <knome> oh, wait
[20:07] <knome> crap
[20:07] <knome> nvm...
[20:08] <knome> i mean, 4 hours later
[20:08] <knome> ;)
[20:08] <knome> might be a bit too late for me though...
[21:01] <pleia2> knome: what time? :)
[21:01] <knome> pleia2, 17pdt
[21:02] <knome> pleia2, in 3 hours
[21:02] <pleia2> was planning on App Developer events because I do Classroom stuff, why?
[21:02] <knome> nah, just asking :)
[21:02] <knome> whether i might be able to hear your sweet voice or not
[21:03] <pleia2> hehe
[21:03] <knome> but as i said, 3am might be bit too much for me
[21:04] <knome> at least if i really wanted to contribute to the session
[21:04] <knome> (iso tracker improvements)
[21:04] <Unit193> Ah.
[21:14] <knome> Unit193, googling points to a "suspended" page
[21:16] <Unit193> knome: That's one weird version reply...
[21:18] <knome> have you noticed none of singlerr's or single's questions make sense at first?
[21:19] <Unit193> That's why I left to you after mini.
[21:19] <Unit193> Seems to want openbox, but not sure how to use it. :/
[21:20] <MrMkS> Hi!
[21:21] <knome> MrMkS, hey
[21:21] <MrMkS> I want to host a Xubuntu mirror
[21:21] <knome> MrMkS, you are the one who sent the email?
[21:21] <MrMkS> Right now i host a Ubuntu official mirror
[21:21] <MrMkS> which email ?
[21:21] <Unit193> I'd think not on the GeoIP.
[21:21] <knome> MrMkS, email to the xubuntu-devel mailing list about hosting a xubuntu mirror?
[22:59] <Schrodinger`Cat> hey
[23:00] <SATop> hi
[23:00] <Schrodinger`Cat> i would like to know if there is a ppa to get xfce4.8 stable
[23:00] <Schrodinger`Cat> or need to wait https://launchpad.net/~xubuntu-dev/+archive/xfce-4.10 is up ?
[23:00] <SATop> 4.10 you mean ?
[23:00] <Schrodinger`Cat> yes
[23:01] <Schrodinger`Cat> 4.10
[23:02] <Schrodinger`Cat> because the ppa of mrpouit https://launchpad.net/~mrpouit/+archive/ppa is still with 4.10 beta
[23:04] <SATop> i know there is an empty ppa for 4.10 so i guess they are working on it
[23:04] <knome> it's going to be out "later", but no ETA
[23:05] <SATop> we can make a guess based on the unkown available time of devs and their system abilities
[23:06] <SATop> :P
[23:07] <SATop> you can also try to build it yourself http://docs.xfce.org/xfce/building
[23:07] <SATop>
[23:09]  * knome is off
[23:16] <SATop> schrodinger that ppa says (Please note that packages will be moved to https://launchpad.net/~xubuntu-dev/+archive/xfce-4.10 in a few hours)
[23:27] <Schrodinger`Cat> ok thanks


[07:22] <VladimirShushkov> Hi, mates!  I dont use linux for a long time since the times of kernel 2.6.10 maybe. Now I have installed Ubuntu and I want to rebuild my kernel. I want to compile kernel 3.0. I tried to find ppa for this kernel. I just added ppa:kernel-ppa/ppa to my repository. But after apt-get update and trying to execute "apt-get install linux-headers" I didnt see linux-headers v.3.0, only 2.6.38. Maybe I
[07:24] <ohsix> why do you want to build your own kernel?
[07:24] <ohsix> you can install kernel packages from mainline that are built almost nightly, or you can install something like xorg-edgers which has a 3.0 kernel in it; to support the updated drivers in the same repo
[07:26] <jk-> VladimirShushkov: `apt-get install linux-headers-$version` ?
[07:37] <VladimirShushkov> ohsix: Why do you ask about reasons to build new kernel? Is it bad idea? In the past I used slackware linux and always built my own kernel after linux installation. I built some of kernel features right in kernel but some left in modules. Building of you own kernel give you some definition. Also in the past I found that some of kernel features (e.x. packet filtering features) were not included in kernel nor in modules. Maybe today is diff
[07:41] <VladimirShushkov> jk-: Sorry, I dont understand what do you mean. As I said after typing apt-get install linux-headers- and pressing tab I see all candidates for installation: root@WorkstationX:~# apt-get install linux-headers-
[07:41] <VladimirShushkov> linux-headers-2.6.38-10              linux-headers-2.6.38-8-virtual
[07:41] <VladimirShushkov> linux-headers-2.6.38-10-generic      linux-headers-generic
[07:41] <VladimirShushkov> linux-headers-2.6.38-10-server       linux-headers-lbm-2.6.38-10-generic
[07:41] <VladimirShushkov> linux-headers-2.6.38-10-virtual      linux-headers-lbm-2.6.38-10-server
[07:41] <VladimirShushkov> linux-headers-2.6.38-11              linux-headers-lbm-2.6.38-11-generic
[07:41] <VladimirShushkov> linux-headers-2.6.38-11-generic      linux-headers-lbm-2.6.38-11-server
[07:41] <VladimirShushkov> linux-headers-2.6.38-11-server       linux-headers-lbm-2.6.38-8-generic
[07:41] <VladimirShushkov> linux-headers-2.6.38-11-virtual      linux-headers-lbm-2.6.38-8-server
[07:41] <VladimirShushkov> linux-headers-2.6.38-8               linux-headers-server
[07:41] <VladimirShushkov> linux-headers-2.6.38-8-generic       linux-headers-virtual
[07:41] <VladimirShushkov> linux-headers-2.6.38-8-server
[07:47] <smb> VladimirShushkov, I think it would be linux-headers-<something> while the something is the same as you see when you run uname -r
[07:47] <smb> (like generic or generic-pae or server)
[07:50] <smb> morning .+
[07:51] <VladimirShushkov> ohsix: thanks, xorg-edgers is what i need.  What do you mean saying mainline? Is it kernel.org? Because when I used slackware I just downloaded kernel source in tar.bz2 format and used it.
[08:03] <smb> VladimirShushkov, It is the same, but instead of taking certain tar version, the source is taken from git directly and then compiled with the same configuration options as the released kernel packages. Any ubuntu specific modules are missing, but those are less often needed.
[08:05] <Q-FUNK> howdy! any news on re-enabling vesafb on mainline kernels?
[08:07] <VladimirShushkov> smb: Thanks for your explanation. As I see mainline doesnt contain kernel 3.0 for natty, only for oneiric. If I will use oneiric kernel dont I break depencies?
[08:09] <smb> VladimirShushkov, There are no hard dependencies. The natty or oneiric postfix rather tells you which config options where used to build the kernel. There always may be problems but rather due to the fact that a newer kernel could potentially have changed interfaces to user-space. Though 3.0 in Natty is working
[08:11] <VladimirShushkov> smb: thank you!
[08:11] <smb> Q-FUNK, No (though that merely means "I have no clue whether there are news")
[08:48] <Q-FUNK> smb: ok :)
[09:39] <apw> ppisati, yo ... cve-tracker ?
[09:42] <ppisati> are you and smb mentally connected? :)
[09:42] <smb> ppisati, Didn't you know. ;-P
[09:42] <ppisati> good to know :)
[09:42] <ppisati> anyway
[09:42] <ppisati> https://code.launchpad.net/~ubuntu-security/ubuntu-cve-tracker/master?
[09:42] <ppisati> this one?
[09:43] <smb> Not if you want to change anything
[09:43] <smb> That is the other teams original copy
[09:43] <ppisati> https://code.launchpad.net/~canonical-kernel-team/ubuntu-cve-tracker/kernel-team
[09:43] <ppisati> ok
[09:43] <ppisati> this one
[09:43] <smb> Yup, looks better
[09:44] <smb> ppisati, Anything in special that you need to achieve?
[09:44] <ppisati> no no
[09:45] <ppisati> just flip a cve status
[09:45] <ppisati> seems lp and cve tracker are not connected yet
[09:46] <smb> ppisati, They should be. But its something that apw has to trigger (or any real person). So it probably just runs or ran
[09:47] <apw> ppisati, they are connected but there is security-team latency involved
[09:48] <apw> but there isn't any problem flipping the state if you want to
[09:48] <apw> though other than 'not-affected' there isn't many that make sense to apply manually
[09:49]  * apw watches his upgrade go at 160k/s ... sigh
[09:52] <apw> i presume the mirrors are still being hammered
[10:39] <apw> ppisati, for -2479 do you know which commit added the the huge page support in error ?
[10:41] <ppisati> apw: huge page support was added in 71e3aac0724ffe8918992d76acfe3aad7d8724a5
[10:42] <apw> ppisati, so we can represent when something is added too on the break-fix line and get the not-affected status for free ... /me tries it out on this cve
[11:17] <Kano> hi apw , why are daily builds older than rc9?
[11:20] <apw> older in date or older than commit list
[11:20] <Kano> they are not build
[11:21] <apw> that is not really an answer to the question
[11:21] <Kano> http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/
[11:21] <Kano> 10-04 is older than rc9 date
[11:22] <apw> but by the looks of it linus has not pushed his master bracnh correctly to kernel.org
[11:22] <Kano> but there are much  newer commits there
[11:22] <apw> there == where ?
[11:22] <Kano> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=summary
[11:23] <Kano> what should be wrong there?
[11:24] <apw> Date:   Sun Feb 20 10:15:57 2011 -0800
[11:25] <apw> interesting, the latest commit if you pull the branch from kernel.org is nothing like that in gitweb
[11:25] <Kano> really weird
[11:27] <Kano> well usually i parse web gits to dl snapshots
[11:28]  * apw switches mainline over to github again, we'll see if that changes anything
[11:37] <Kano> any diff there?
[11:45] <apw> Kano, take a while before we know
[12:38] <apw> cking, yo ... i have just confiermed my 35s of black screen is a win7 thing, if i set acpi_osi="!Windows 2009" it no longer occurs :(
[12:39] <Kano> did anybody manage to suspend a system booted via uefi correctly?
[12:40] <apw> what sort of machine is it, ie is it real uefi
[12:40] <apw> and not broken mac near a bit efi
[12:41] <Kano> i7 with q67
[12:41] <apw> you could easily be the first
[12:41] <apw> does the machine suspend if you enable bios emulation?
[12:42] <Kano> it does not even suspend correctly win7 64 bit sp1 via efi
[12:42] <Kano> it works fine booted via mbr
[12:43] <Kano> somehow suspend does not seem to be that easy with efi...
[12:43] <apw> nope, efi is a bit of a disaster at the moment
[12:43] <nusch> Is there avaiable or could someone build for me standard 3.0.0-12-generic with CONFIG_RCU_TRACE option enabled ?
[12:44] <apw> nusch, i doubt there is one available, i might be able to make you one, what you need it for
[12:44] <apw> (and which architectures)
[12:44] <Kano> bbl
[12:44] <nusch> I installed new RAM and got message about RCU detected CPU 0 stall
[12:44] <nusch> trying to examine where exactly it locks
[12:44] <apw> did it come out of the stall ?
[12:45] <nusch> yes
[12:45] <nusch> kernel runs about 30x slower than normally
[12:45] <nusch> looking at tty lines
[12:45] <apw> and you get constant stalls ?
[12:45] <apw> all from adding some new RAM ?
[12:45] <nusch> yes
[12:45] <nusch> 8GB instead of previous 4GB
[12:46] <nusch> this is x86_64
[12:46] <apw> doesn't seem like a change we'd expect to affect the kernel
[12:46] <apw> none of those values are exactly remarkable
[12:46] <smb> If you assume the RAM has no flaw
[12:46] <apw> and you've run a memory check?
[12:47] <nusch> memtest looks ok
[12:47] <nusch> and it boots on another hardware without problems
[12:47] <nusch> some people sugested buggy BIOS, is it correctable by kernel?
[12:47] <apw> i wonder where it got put, in the memory map
[12:47] <apw> if it is a physical layout issue triggered by the bios, not so easy
[12:48] <apw> could you pastebin a dmesg from the kernel with 8G inserted
[12:48] <apw> i wonder if the mtrrs could be wrong
[12:49] <smb> Yeah either that or maybe the timing goes wrong. Some BIOS may decide something bad based on what is in SPD
[12:50] <nusch> I asked people at ##kernel their also suggested mtrr but said it's ok, here is my dmesg https://bugs.launchpad.net/ubuntu/+source/linux/+bug/875655
[12:50] <ubot2> Launchpad bug 875655 in linux "Kernel extremally slow after upgrade from 4 to 8GB RAM on x86_64 machine, "RCU detected CPU0 stall"" [Undecided,Confirmed]
[12:51] <nusch> it was run with kernel mem=3G, becuse otherwise unusable. Here is another http://pastebin.com/YtLNPiCc with 8GB inserted and no kernel mem= option
[13:14]  * smb wished that dmesg would not just print the hard to understand mask format...
[13:15] <smb> Though it feels like only the first 3G and then 1G above 4G are cacheable...
[13:24] <nusch> smb, and what is the reason of such behaviour ?
[13:26] <smb> nusch, Don't know exact. Actually I start to wonder whether it matters that much in 64bit mode... My system here also only has the first 4G declared in mtrrs and does not care that much
[13:27] <nusch> smb, and what about PAT, if PAT is enabled doesn't it mean MTRR don't have to strore correct information ?
[13:28] <smb> Thinking along similar lines. But I am sufficiently in doubt about my knowledge here...
[13:33] <smb> nusch, Theoretically there could also be the problem that the module reports incorrect RAM timing (or the bios fails to make a sense of it). Unfortunately netbooks usually have nothing useful (in the sense of tunable) as a bios
[13:35] <nusch> I hope that's not striclty hardware issue, that's why I want check it with CONFIG_RCU_TRACE
[13:38] <smb> nusch, Maybe you could add the output of "sudo dmidecode" to the bug report. That may contain some more bits of info
[13:43] <nusch> smb, I have no access to this computer at the moment , can send evening, but if it helps I have DSDT dump there
[13:46] <smb> nusch, Don't think the DSDT helps us here. That would be rather static info, while the dmidecode could show some info about what the bios detected/has set up
[13:49] <nusch> ok, will try that this evening, BTW could I pass commands like dmidecode | tee  to kernel init= parameter ? Because it was not possible to boot system to bash prompt anytime. I was only able to sysrq reset or poweroff after few seconds pressing keys
[13:52] <smb> nusch, It should be ok to run the command even with mem=3G. As long as the memory module is present the bios will configure it and dmidecode reports it. Just the kernel make no use of the additional memory
[13:52] <nusch> ok
[14:16]  * ogasawara back in 20
[15:11] <bjf> ogasawara: are you still handling the oneiric kernel or has the batton been passed to stable ?
[15:12] <ogasawara> bjf: should probably pass to stable now
[15:34] <Q-FUNK> who updated the mainline kernel today? :)
[15:56] <evt> Can someone explain the "isra" suffix I see on some symbols via /proc/kallsyms? (ex: do_anonymous_page.isra.40())
[16:46] <nusch> smb: here is my dmicodede you asked http://pastebin.com/bKeT9iuw
[16:53] <nusch> smb, sorry that one was without one module mounted, paste in a moment
[17:35] <pmatulis> jsalisbury: hello sir, do you still need any vm's on kvm-server-2?
[19:55] <DBO> hi, I am having issues with my realtek wireless. rtl8192ce is the wireless driver I am currently using. It seems to randomly stop talking to my access point at which point I have to reconnect to keep talking
[19:56] <DBO> it really makes pushing to bzr a frustrating experience :)
[19:59] <jjohansen> DBO: your lucky it doesn't oops your machine, what kernel version are you using
[19:59] <jjohansen> DBO: I have found the oneiric driver much better than (still not good), the natty one
[20:00] <DBO> oneiric latest
[20:00] <DBO> is there a better driver to use?
[20:00] <DBO> or something I can do to improve its stability and usefulness?
[20:10] <bjf> ogasawara: what's your timeframe on uploading the first precise kernel ?
[20:11] <ogasawara> bjf: am about to send out email for the proposed -generic and -server config flavors.  Assuming I get Acks, I'd like to upload tomorrow.
[20:11] <bjf> ogasawara: cool
[20:12] <Q-FUNK> bjf: we have separate desktop and server flavors, now?  are the desktop ones full preempt?
[20:12] <jjohansen> DBO: try black listing the rtl8192ce driver and see if another of the rtl drivers will handle it
[20:12] <bjf> Q-FUNK: that's a question for ogasawara
[20:13] <Q-FUNK> öö, yes
[20:13] <ogasawara> Q-FUNK: we have separate flavors at the moment, we're proposed merging them.  the desktop uses the voluntary preemption model.
[20:14] <Q-FUNK> ogasawara: why merge them?
[20:14] <DBO> woops, xchat crashed
[20:14] <ogasawara> Q-FUNK: because aside form the preemption model and the scheduler, the configs are almost identical
[20:14] <bjf> Q-FUNK: this is being discussed on the ubuntu kernel team mailing list
[20:14] <Q-FUNK> ogasawara: the preemption model is already a significant factor.
[20:15] <ogasawara> Q-FUNK: that's why we're discussing on the mailing list
[20:15] <ogasawara> Q-FUNK: and I'd like to keep the discussion there rather than having separate discussion on IRC and email
[20:17] <Q-FUNK> ogasawara: ok.  fair enough :)
[20:18] <Q-FUNK> ogasawara: have you and apw had the time to figure out why 'vesafb' is missing from default mainline builds, btw?
[20:19] <ogasawara> Q-FUNK: sorry I haven't looked as I thought you'd discussed with apw
[20:19] <ogasawara> Q-FUNK: as he is the primary care taker of the mainline builds
[20:19] <Q-FUNK> ogasawara: we did.  sorry if the hierarchy of the kernel team seems unclear to me at times.
[20:27] <Q-FUNK> ogasawara: we however never came to a definite answer about it.  I noticed a new mainline build toda, but vesafb was still missing.
[20:27] <DBO> jjohansen, okay I tried that, no joy, blacklisting rtlwifi and rtl8192ce results in no wifi :/
[20:28] <jjohansen> DBO: :(
[20:29] <DBO> is it possible that the driver isn't dealing with network manager doing its "scans"
[20:29] <ogasawara> Q-FUNK: might be best to follow back up with him tomorrow?  I think he reset the mainline builds to point to github earlier today.
[20:34] <Q-FUNK> ogasawara: that's possible. I'm not updated on the situation. I'm merely waiting for vesafb to return so that I can test mainline as jsalisbury requested on several bugs.
[20:38] <jjohansen> DBO: from what I have seen, no its the driver having problems
[20:39] <DBO> jjohansen, is there anything I can do? It kinda makes hacking on Unity hard :P
[20:39] <jjohansen> DBO: I found a usb wifi dongle fixes the proble :/
[20:40] <DBO> jjohansen, are we dependent on a fix from realtek or can we FOSS our way to a win here?
[20:41] <jjohansen> DBO: well FOSS away, but as I hear it the driver is pretty poor and needs a lot of work.  It certainly take someone who knows their way around the wireless driver stack
[20:42] <DBO> jjohansen, I wasn't intending to imply *I* would fix it, more looking for hope :)
[20:42] <DBO> I'll see if I cant order an intel wifi card and just be done with it
[20:42] <DBO> swapping out hardware is fun
[20:43] <jjohansen> DBO: hehe :)  I can give you the hope that I have only seen it crash oneiric once, which is better than natty where it was taking out the machine every 30 min
[20:43] <DBO> jjohansen, I have to admit, I find it a bit discouraging that the driver is in such a poor state
[20:44] <jjohansen> yeah /me too
[20:44] <DBO> jjohansen, I've never done wifi driver work, but I am an experienced hacker, is this a whole other world of pain or could I potentially help out here?
[20:45] <jjohansen> possibly, its just a driver, nothing magical.  You need to learn the wifi driver stack some and maybe have card specs
[20:45] <jjohansen> I've never had the time to chase it
[20:46] <DBO> last one and I promise to leave oyu be: http://www.newegg.com/Product/Product.aspx?Item=N82E16833106061 will that be trouble free?
[22:30] <apw> Q-FUNK (and ogasawara), i know why it is missing at least, it can no longer be a module -- fixing it is on my list


[06:24] <latino> good evening
[06:24] <latino> can any1 help with installing video drivers
[14:01] <zubin71> jcastro, hello, is there any way that there`d be a class on doing unittesting using python?
[14:06] <Pendulum> zubin71: that's something you'd be interested in seeing in a class?
[14:07] <zubin71> Pendulum, yes, im new to python programming.... And i came across this topic pretty recently...
[14:07] <zubin71> we have a small OS community here...
[14:07] <zubin71> we`d love to have classes on unit testing...
[14:08] <zubin71> OSS*
[14:08] <zubin71> typo
[14:10] <zubin71> Pendulum, are you an ubuntu developer? python? If holding classes if difficult , it`d be great if there were at least some ubuntu community documentation...
[14:11] <Pendulum> zubin71: I'm not, but I'm a member of the Ubuntu Classroom team :)
[14:11] <Pendulum> so I'm bringing your suggestion back so we can look for an instructor :)
[14:13] <zubin71> awesome! also, it`d be great if I could help by taking sessions on a subject in a couple of months... maybe on unittesting itself, if im comfortable with it in the near future... :)
[14:25] <zubin71> Pendulum, well, c ya later! have a nice day!
[19:01] <qense> Hello everyone!
[19:01] <qense> This session I will be talking about GTK+ signals.
[19:03] <qense> Signals aren't specific to GTK+, but opportunistic programmers will deal mostly with GTK+ signals.
[19:03] <qense> What are signals?
[19:03] <qense> Signals are a nifty way of allowing an application or library to respond to certain events.
[19:04] <qense> Signals are emitted at all sorts of events, so you can listen to almost anything if you know where to look.
[19:04] <qense> I assume that most of you are using Python, so I'll be mainly using Python examples.
[19:05] <qense> However, since the PyGTK library is generated from the C GTK+ library it is not that different.
[19:05] <qense> Object.connect("signal-name", callback_function) is equal to g_signal_connect(signal_owner, "signal-name", G_CALLBACK (callback_function))
[19:06] <qense> A really good source of information is http://www.pygtk.org/docs/pygtk/
[19:06] <qense> This is the online documentation of PyGTK and you can find, amongst other things, all signals documented here.
[19:07] <qense> It is important to keep in mind that most types in the GTK+ and GObject libraries are derived from other GTK+ and/or GObject types.
[19:07] <qense> All types are derived from gobject.GObject
[19:08] <qense> A type has got all signals it's derived from.
[19:08] <qense> gobject.GObject has got only one signal 'notify'
[19:08] <qense> However, that means that all GTK+ objects have got that signal as well.
[19:09] <qense> The 'notify' signal is emitted whenever an property of the object is changed.
[19:10] <qense> However, this doesn't have to mean the value of those properties has changed, it could have been that someone or something assigned the an identical value to a property
[19:11] <qense> All GTK+ types are derived from gtk.Object (gtk.Object itself is derived from gobject.GObject)
[19:11] <qense> gtk.Object has one signal as well: 'destroy'
[19:11] <qense> This is emitted when the object is destroyed
[19:11] <qense> You use this e.g. when constructing a window.
[19:11] <qense> window = gtk.Window();
[19:11] <qense> window.show();
[19:12] <qense> window.connect("destroy", gtk.main_quit());
[19:12] <qense> gtk_main();
[19:12] <qense> Now, what did I write above?
[19:12] <qense> First I created a new window, then I showed it and then I connected a callback function.
[19:12] <qense> Whoops
[19:12] <qense> I see I connected it wrongly.
[19:13] <qense> This sure would have generated a bug.
[19:13] <qense> It should have been
[19:13] <qense>  window.connect("destroy", gtk.main_quit);
[19:13] <qense> Without the parentheses.
[19:14] <qense> What you do when connecting is first specifying the signal name, then you give the reference to the callback function.
[19:14] <qense> However, if you add the parentheses you invoke the method.
[19:14] <qense> As you can see I connected a method from a library: gtk.main_quit()
[19:14] <qense> That method ends the GTK+ loop.
[19:15] <qense> If you wouldn't connect this to a destroy signal you would have to forcefully quit the application in order for the GTK+ main loop to end.
[19:16] <qense> You can also specify locally defined methods as callback functions.
[19:16] <qense> Any questions about the working of GTK+ signals, or about what I've told so far?
[19:19] <ClassBot> ryzrecreel asked: So the callback function can be the method of another object?
[19:20] <qense> ryzrecreel: Yes, the callback can be any valid method. When connecting signals from inside a class you could e.g. also specify "self.my_wonderful_callback" method as the callback function.
[19:20] <qense> However, you can't assign MyClass.my_callback as the callback function, you need to pass the method of an instance.
[19:21] <qense> OK, lets talk a bit more about the callback function.
[19:22] <qense> Because when a signal is emitted and your well-crafted callback function is called you want to know something more about what happened.
[19:22] <qense> For that a series of arguments are sent to the callback function.
[19:22] <qense> You need to make sure that it can accept those arguments.
[19:23] <qense> Most of those callback functions look the same.
[19:23] <qense> This is what the PyGTK documentation says the callback function for the 'notify' signal should look like:
[19:23] <qense> def callback(gobject, property_spec, user_param1, ...)
[19:24] <qense> If you're defining the callback as a member of a class make sure you add an extra 'self' argument to the beginning
[19:24] <qense> the first argument of the callback function is 'gobject', but of course you can change the names in your own code.
[19:24] <qense> 'gobject' is the GObject that changed and therefore emitted the notify signal
[19:25] <qense> Most of the times you know what object you're getting since you specifically connected your callback to it, but this can be useful when you're connected to multiple objects.
[19:25] <qense> But mostly it's very useful to have a reference to the object by hand
[19:25] <qense> the second argument is 'property_spec'
[19:26] <qense> It provides information about the property that changed so you can access it if you would want  to.
[19:26] <qense> The last is user data; when connecting to a signal you can provide extra userdata as extra arguments at the end of the function.
[19:26] <qense> You'd do this:
[19:27] <qense> window.connect("destroy", gtk.main_quit, "test-window", 123);
[19:27] <qense> and the last two arguments would be the last two arguments for the callback function
[19:29] <ClassBot> lsteeger asked: What happens if the object used for the callback function in 'connect' call is destroyed before the event occurs?
[19:30] <qense> lsteeger: If you didn't disconnect the callback function first you will get an error.
[19:31] <qense> When you connect to a signal using the .connect() function the connect() function returns a handler id.
[19:31] <qense> You can pass that handler id as the sole argument for .disconnect() for disconnecting from the signal.
[19:32] <qense> Naturally, when you remove the object you connected to the callbacks are disconnected automatically.
[19:32] <qense> There are a few very interesting signals.
[19:32] <qense> gtk.Widget has the most, which means all GtkWidgets have got them.
[19:33] <qense> To give you an idea of what you can do with GTK+: all you see happening on screen is mostly done with publicly accessible signals and methods.
[19:34] <qense> There is a 'show' signal that is emitted when the show() method is called.
[19:35] <qense> There is a 'show-help' signal that is emitted when the user presses Ctrl+F1 on his or her keyboard.
[19:37] <qense> An interesting signal is "enter-notify-event", which is emitted whenever a mousebutton enters the widget.
[19:38] <qense> It is used by many widgets like buttons.
[19:38] <ClassBot> lsteeger asked: If I extend a widget, can I define 'new' signals of my own?
[19:38] <qense> lsteeger: Excellent question!
[19:39] <qense> Yes you can, it is exactly what all widgets are doing.
[19:40] <qense> You do that with the "gobject.signal_new()" function since actually signals are provided by GObject.
[19:41] <qense> Lets paste the function from the documentation:
[19:41] <qense> def gobject.signal_new(signal_name, type, flags, return_type, param_types)
[19:41] <qense> The first argument is the name you give to the signal.
[19:41] <qense> This has to be a unique name.
[19:41] <qense> The second is the object (type) you're adding the signal to.
[19:42] <qense> If you want to add a signal to myproject.MyWidget you write myproject.MyWidget there, without quotation marks.
[19:42] <qense> The third argument is an interesting one: there you provide flags.
[19:43] <qense> it goes a bit too far to explain them all, but you can make the signals do more than what I showed with the 'destroyed' signal.
[19:43] <qense> most of the times you provide something like gobject.SIGNAL_RUN_LAST as the flag.
[19:43] <qense> It has got something to do with when you emit the signal.
[19:44] <qense> If you want to provide multiple flags you use |  to separate them
[19:45] <qense> The next argument is the return type of your callback function, which could be something like gobject.TYPE_STRING or gobject.TYPE_NONE if your callback doesn't return anything at all.
[19:45] <qense> The last argument is a tuple of types of the arguments passed to the callback.
[19:46] <qense> e.g. (myproject.MyWidget, gobject.TYPE_BOOL)
[19:46] <qense> You're not finished with just defining a signal, you'll also want to emit it something.
[19:46] <qense> somehwere
[19:47] <qense> You do that with gobject.emit() method.
[19:47] <qense> The first argument is the signal name
[19:47] <qense> The others are the arguments that are sent to the callback
[19:48] <qense> If you want to emit a signal inside your MyWidget class you call self.emit()
[19:49] <ClassBot> lsteeger asked: With multiple subscribers to an object's events, does the emit() infrastructure apply a hierarchy to their invocation?
[19:50] <qense> lsteeger: Yes it does, the first callback that is connected to a signal is the first to be called.
[19:51] <qense> you can use the . stop_emission(signal_name) method to stop the emission, if you wanted to.
[19:51] <qense> lsteeger: yes, First In, First Out indeed
[19:52] <qense> However, the default signal handler is always at the end of the list.
[19:52] <qense> You'll have to use the .connect_after() method to be added after that callback.
[19:53] <qense> Default signal handlere? What is that?
[19:53] <qense> It is the default signal handler, and it's always called.
[19:53] <qense> If it's specified, of course.
[19:54] <qense> You can do that by creating a function in a class with the name "do_signal_name"
[19:55] <qense> If you want to override default signal handlers, make sure you add __gtype_name__ = "MyWidget" as a class property
[19:55] <qense> class MyWidget (gtk.Widget):
[19:55] <qense>     __gtype_name__ = "MyWidget"
[19:56] <qense> Any questions about what I've told this session?
[19:56] <qense> Or other questions?
[19:58] <qense> Remember, if you want to learn what signals there are, go to http://www.pygtk.org/docs/pygtk/ and take a look at the page of the widget you want to know more about.
[19:59] <ClassBot> ryzrecreel asked: when using quickly with glade the connects are made for you. Is there any way to over ride that?
[19:59] <qense> ryzrecreel: In the generated code you can see that the signals are connected using .connect_object()
[20:00] <qense> That means it searches for the callback functions in the object you provide.
[20:00] <qense> The callback functions are provided in Galde
[20:00] <qense> Glade
[20:00] <qense> you can change those there.
 QUESTION: In a multi-core/processor environment, do multiple event handlers get invoked asynchrounously?
[20:01] <qense> lsteeger: That doesn't depend on multi-threading, signal handlers don't get handled asynchronously, but one by one.
[20:01] <qense> OK, thank you for listening, this was all!
[20:01] <qense> This also was the last session of the Ubuntu Opportunistic Developer Week
[20:01] <qense> I hope you enjoyed it.


[10:13] <krgn> good morning
[10:14] <krgn> hey, is there a way to remove certain arches from debian/config/* ? updateconfigs fails because I removed some dir's for arches i don't want to build for
[10:17] <Daviey> krgn: Wouldn't it make more sense to only build for the arches you want to build for?
[10:18] <amitk> krgn: if all you need is a single flavour, just using the binary-<flavour> target
[10:18] <krgn> Daviey: true, but when using updateconfigs target i have to go through tons of configs which I am too lazy to do ;)
[10:18] <amitk> fakeroot debian/rules binary->flavour>, that is
[10:18] <Daviey> ^^ Surely you can do that :)
[10:19] <krgn> I guess I can just switch myself off for a little while
[11:10] <krgn> hey, is there a way to get sources for the mainline kernel anywhere?
[11:12] <Kano> git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
[11:12] <Kano> ?
[11:12] <krgn> Kano: ok ok, but I also need the ubuntu-specific stuff
[11:13] <Kano> well you can use a ubuntu kernel then git pull from that
[11:13] <Kano> that will update it
[11:13] <krgn> you mean, git checkout origin/v2.6.29 or something
[11:13] <krgn> ?
[11:14] <Kano> git clone git://kernel.ubuntu.com/ubuntu/ubuntu-karmic.git
[11:14] <Kano> cd ubuntu-karmic.
[11:15] <Kano> git pull git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git master
[11:15] <Kano> for example
[11:16] <krgn> Kano: great, I'll try this. thanks
[11:17] <Kano> i am waiting for next official sync currently but you can do that to update that whenever you want
[11:30] <krgn> hmm weird, I end up without debian/rules etc...
[11:48] <krgn> hey, are there deb source files for the mainline kernel builds?
[11:49] <amitk> krgn: I pointed those out to you yesterday
[11:49] <krgn> amitk: this page: http://kernel.ubuntu.com/~kernel-ppa/mainline/ ?
[11:49] <amitk> krgn: https://wiki.ubuntu.com/KernelTeam/MainlineBuilds?action=show&redirect=KernelMainlineBuilds
[11:50] <amitk> go to the archive link on this page
[11:50] <amitk> krgn: your link should work too
[11:51] <krgn> amitk: ah but these don't have source debs so I can see how the packaging is done
[11:51] <amitk> krgn: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.31-rc4/linux-source-2.6.31_2.6.31-020631rc4_all.deb <-- this doesnt?
[11:51] <amitk> apw: ^^^
[11:52] <apw> yeah i thought we had source debs in the mainline builds?
[11:53] <krgn> amitk: ah yes, but then I need to use specific version <IP_ADDRESS> as I patch with rt patch and aufs, and the linux-source deb doesn't contain a lot of the files in debian/*
[11:53] <krgn> its quite convoluted :)
[11:53] <apw> krgn?
[11:53] <apw> oh hrm source .debs ...
[11:53] <apw> are we copying the wrong one?
[11:54] <krgn> apw: you mean wrong deb? I think that .31 would be ok, but I can't use that yet since aufs doesn't have a compat patch for rt
[11:55] <apw> well the way they are made is we simply checkout the mainline version, then checkout the debian directory from the tip of the nearest release and run updateconfigs
[11:55] <apw> then build, there is no rocket science involved
[11:57] <krgn> apw: ah yes, thats exactly what I did. then I ran into build failure that only happens with the debian/rules  binary-arch but not when I just put a config and run make
[11:57] <krgn> which is strange to me, since it doen't seem to patch anything
[11:58] <apw> what was the build failure as we don't mod the source
[11:59] <krgn> it fails to build kernel/power/snapshot.c because apparently there is a parse error, but this doesn't happen when I do the build manually
[12:01] <krgn> http://pastebin.ca/1529303
[12:07] <amitk> apw: what was the rune to quickly create a branch? 'git checkout -b foo' takes a while
[12:07] <apw> if you don't need to be on it
[12:08] <apw> then you can make a branch directly with git branch <name> <commitish>
[12:09] <amitk> aaaaaaaah, I do need to be on it.
[12:16] <apw> if you need to be on it i don't know of a quicker way
[13:44] <ukev> hi... did you heared of the linux kernel root exploit?
[13:44] <ukev> I've just tested it, jaunty full patched is vulnerable..
[13:47] <ukev> no one here?
[13:47] <ukev> its important
[13:48] <amitk> ukev: our -security teams are aware of it and kernel updates are being prepared
[13:49] <ukev> ok great :)....
[13:49] <ukev> thanks for all the work!
[13:49] <amitk> ukev: you could join #ubuntu-security to track status
[13:49] <ukev> ok thanks for that hint
[13:58]  * krgn wonders... are any .h / .c files by default in debian/ dir?
[13:58] <krgn> this build error could be related to mismatching source/header files
[13:59] <krgn> for example, there are 3 different files called power.h in debian/ while this also exists in kernel/power/
[15:22] <krgn> sorry for all teh confusing and ... thanks for the help!
[15:58] <amitk> usb oops and apport == fail (atleast in my case)
[15:59] <amitk> lsusb was stuck in a loop and hence apport for stuck
[15:59] <amitk> s/for/was
[17:23] <krgn> is this a common mistake?
[17:23] <krgn> EE: Previous or current ABI file missing!
[17:24] <krgn> I built binary-generic target, and so for this kernel version only one abi exists
[18:08] <jnfuller> can I ask a kernel compilation question here or is this only for development discussion?
[18:16] <jnfuller> mostly what I am wondering is: if I am currently running 2.6.28-14-generic (#47) and I apt-get linux source I end up with 2-6-28-9. If I apply Linus' patch for the null pointer exploit to this tree and then make and install the deb for the custom kernel what sort of issues will I have in relation to the restricted-modules. Will I need to recompile those for the new custom kernel?
[18:17] <jnfuller> Or... is the patch in the works for a new kernel from the offical repos and I shouldn't bother?
[18:21] <rtg> jnfuller, the latter
[18:28] <jnfuller> thanks, rtg, but if I do end up having to apply this kernel (i.e. boss demands it on production systems) I'd have to apply the kernel, reboot and then compile the restricted-modules against the custom kernel in order for the proprietary stuff to work, right?
[18:30] <rtg> jnfuller, any time you change the ABI, then you'll have to recompile all external, 3rd party modules.
[18:30] <jnfuller> ok that's what I thought.
[18:30] <jnfuller> thanks again
[18:33] <krgn> hey, how do I bump the abi? do I do this in the changelog?


[02:12] <dade`> nobody talks here
[02:12] <dade`> why
[03:02] <markginter_24> anyone use Impress for presenations on your laptop?