=== mmrazik is now known as mmrazik|moving_t === Tonio_aw is now known as Tonio_ === mmrazik is now known as mmrazik|otp === Tonio_ is now known as Tonio_aw === Tonio_aw is now known as Tonio_ === mmrazik|otp is now known as mmrazik === Tonio_ is now known as Tonio_aw === ogra-cb__ is now known as ogra-cb === mmrazik is now known as mmrazik|lunch === Ursinha is now known as Ursinha-afk === Tonio_aw is now known as Tonio_ === mmrazik|lunch is now known as mmrazik === Quintasan_ is now known as Quintasan === Ursinha-afk is now known as Ursinha === Tonio_ is now known as Tonio_aw === doko_ is now known as doko === Tonio_aw is now known as Tonio_ === mmrazik is now known as mmrazik|afk === Tonio_ is now known as Tonio_aw === Tonio_aw is now known as Tonio_ === mmrazik is now known as mmrazik|otp === mmrazik|otp is now known as mmrazik [16:00] #startmeeting [16:00] Meeting started Fri Nov 16 16:00:10 2012 UTC. The chair is dholbach. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [16:00] Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired [16:00] Welcome everybody to the Ubuntu on Nexus7 meeting! [16:00] hello [16:00] o/ [16:00] Quick show of hands - who do we all have here for the meeting? :) [16:00] moo [16:00] it's been some time since I was here last! o/ [16:00] me [16:00] * barry waves [16:00] * sforshee waves [16:00] MagicFab, ! [16:01] o/ [16:01] hi [16:01] * jodh waves [16:01] * barry might have to exit early though [16:01] o/ [16:01] o/ [16:01] \o [16:01] o/ [16:01] ogra-cb, :) [16:01] Hello [16:01] hi [16:01] \o/ [16:01] victorp: dancing? :) [16:01] o/ [16:01] vanhoof, I am [16:01] nexus7-style! [16:01] /o/ [16:01] great to see so many people turned up here! :-) [16:01] As this is the first meeting of the kind, I thought we'd start with a quick round of introductions of all the people who put some work into getting Ubuntu to work on the Nexus7 [16:02] #topic Introductions === meetingology changed the topic of #ubuntu-meeting to: Introductions [16:02] Can everyone who worked on this give a quick introduction of themselves? :) [16:02] * ogra-cb is oliver grawert and works on image creation ... [16:02] ogra-cb: mfisch janimo cwayne ssweeny don't be shy [16:03] if you have issues with the bootloader or the images, i'm the guy to nag [16:03] * cwayne is chris wayne, initially worked on documenting installing and known issues, have since been working on answering questions and triaging bugs [16:03] * ssweeny is Scott Sweeny, working on general bug fixes and a juju charm to help people get an arm development environment set up [16:03] (and no, i dont plan to work on dual booting) [16:03] * vanhoof is Chris Van Hoof, helped with the one-click installer, and massive amounts of flashing my devices ;) [16:03] I worked on packaging and maintaining the kernel tree before handing it over to the ubuntu kernel team very recently [16:03] * achiang is alex chiang, i help clear obstacles for the team and generally sit back and watch in amazement at how good they are [16:03] * mfisch is Matt Fischer worked on the initial image. Currently doing bug fixes, bug triage, and investigating benchmarking tools [16:04] * victorp victor palau - mainly looking at performance testing [16:04] also, misc bugfixes, will work on sensors most likely [16:04] kyleN is Kyle Nitzsche. flashed, installer, wiki, etc. [16:05] i think that's the core team. we of course have many other people both in canonical and the community who help as well [16:05] and there is our sound magican diwic [16:05] hi [16:05] awesome - I think it's important to put names to faces and everything - so thanks everyone :) [16:06] do we have to bring a photo next week then ? [16:06] +1^ [16:06] that might work, yes :) [16:06] :) [16:06] we have many people who joined into the meeting and I thought it'd be good if we just open the floor for all questions you might have about Ubuntu on the Nexus7 - the experts are all here :) [16:06] #topic Questions and Answers === meetingology changed the topic of #ubuntu-meeting to: Questions and Answers [16:06] please don't be shy - just ask :) [16:06] o/ [16:06] o/ [16:07] Hi, Fabian Rodriguez here - http://ubuntu.magicfab.ca I have one [16:07] gema, please :) [16:07] we are looking into doing power consumption testing on the lab, I wonder if you guys have figured out how to go about that already [16:07] fully automated, of course :) [16:07] * MagicFab stands in line ;) [16:07] gema, smagoun hacked a device to some meters already I think [16:07] Are there any plans to port Ubuntu to other devices? [16:08] that is on our plan but i think we are still trying to figure out a way to do so, and also engage the community [16:08] s/smagoun/sconklin [16:08] victorp, thanks [16:08] cking might also have some insight from the kernel side about what you can do in software [16:08] for next week, we are going to focus on memory benchmarking, but power consumption is up quickly after that [16:08] yep, I am in contact with them already, so no other insights? :D [16:08] one issue we will have is that we do not plan on recommending people rip apart their machines and hooking up probes [16:08] gema - I think the main concern is that measuring overall power usage is not as useful as knowing what the individual components consume [16:08] so we will focus on *relative* measurements [16:09] gema, apart from the fact that power savings in userland tested on x86 likely benefit the nexus too [16:09] hopefully the community can help us gather a lot of data [16:09] victorp, janimo ack [16:09] achiang, but that will be announced separately, right? [16:09] and my team is going to release a testing framework that enables the community to help us collect this data [16:09] gema, I would also suggest to challange conventional wisdom [16:09] cool [16:09] dholbach: yes, announced separately [16:09] unfortunately we need some accurate measurements, so we need some H/W probes do this [16:10] cking, but only once as reference [16:10] I ran the same test twice, the second time I reduce the brightness of screen > 50% and it made little difference [16:10] I was expecting it to make bigger... [16:10] does the Nexus7 has an internal way to measure the power usage? [16:10] I'd like to do some testing and invite other current Android users to do that. However they (and I) use the N7 as their primary device, testing other ROMs after backing up with ClockWork recovery, same to restore. How can we do that? Current instructions assume the device is dedicated to testing Ubuntu and recovery does a *factory* restore - not good to get more geeky testers, at least not the many already with CyanogenMod etc. [16:10] My question was posted on Ask Ubuntu: I posted this on Ask Ubuntu: http://askubuntu.com/questions/216977/how-can-i-install-ubuntu-on-my-nexus-7-while-being-able-to-recover-from-an-nandr [16:10] * cking has calibrated the battery, it is effectively useless for accurate power benchmarking [16:10] MagicFab: I answered you on AskUbuntu I think [16:11] * barry has an offer and a question [16:11] I was talking with ogra_ earlier today about a mad idea I had of adapting Wubi to the Nexus 7 [16:11] Can folks with questions just message me their question? [16:11] mfisch, an official answer from Canonical, yes, I am expecting a bit different outcome here. [16:11] Though it depends on some other stuff in progress [16:11] barry, obounaim: you had questions from what I could see. [16:11] yeah, i'll keep an eye on it and it will also need some testing first [16:12] yes [16:12] cjwatson, That is a mad idea [16:12] (This would in theory avoid having to disturb Android at all in order to test Ubuntu - but I don't know, it's just a mad idea and it may be more trouble than it's worth) [16:12] (Well, not quite, you'd have to interpose a boot loader) [16:13] if it would work it would be cool though [16:13] dholbach: yes. first my offer: i've heard that folks are having some problems w/ python applications on the nexus7. onboard came up at uds-r, although it seems to be working fine for me. please, if you're having problems with python on the nexus7, contact me and i will work with you. or file bugs and assign me and i will take a look. i can help! [16:13] and avoid a lot of trouble we have with arm bootloaders post installation [16:13] \m/ thanks barry ! [16:13] barry - what is your LP id? [16:13] victorp: barry (so creative :) [16:13] victorp, https://launchpad.net/~barry/ [16:13] lol [16:14] everyone assign bugs to barry [16:14] did i say 'barry'? i mean jodh [16:14] haha [16:14] barry: The comments I'd heard were generally that it was just sluggish [16:14] barry, ddi zou trz it with the default ubuntu theme ? [16:14] *try [16:15] ogra-cb: try what? i basically just installed the nexus7 image and began playing [16:15] barry, play with the different onboard themes in its settings, we dont use the ubuntu default because it was unusable slow [16:15] barry, on board [16:15] there is an onboard snapshot with some performance improvements which i will be uploading to the nexus 7 ppa today [16:15] any other questions? :) barry you had one [16:15] ogra-cb: the upstream onboard devs have a proposed fix for performance w/default theme, we are going to test it soon [16:15] cool ! [16:15] ok, have we talked about the power question sufficiently? I have 4 more questions lined up. (everyone else please message me their questions) [16:15] let's get to barry's question [16:16] my question is about progress on making the desktop drivable by touch. maybe my fingers are too fat but i can't seem to operate the desktop at all [16:16] awesome, i will be happy to test it [16:16] bug 1075470 [16:16] Launchpad bug 1075470 in ubuntu-nexus7 "Window titlebar buttons are unusably small for tablets/touchscreens and don't scale with the fonts/titlebar" [Medium,Confirmed] https://launchpad.net/bugs/1075470 [16:16] * barry subscribes [16:16] barry, all set? :) [16:16] barry: specifically not part of our plan for this cycle [16:16] achiang: nod [16:16] but generally a bug that should be fixed (teh above one) [16:17] it *is* nice to ssh into though :) [16:17] it affects everything, not just tablets :) [16:17] * cwayne has taken to vnc'ing into his tablet [16:17] barry: i would say that fixing touch in parts of the unity stack would be welcome, because it is still relevant on touch-screen laptops too [16:17] ogra-cb I think touch needs a holistic approach rather than fixing one bug at the time [16:17] much more that we can cover in the project [16:18] so that would be a great area for motivated community members to dive in [16:18] there are dozens of unimplemented or non-functional gestures [16:18] learning about our opentouch framework [16:18] and the plan is for all of that to be done by 14.04 [16:18] victorp, that bug above breaks on x86 desktop machines as well (bottom of chars gets cut off if you pick the laargest fontsize) [16:18] oh, if i might one other quick question: can the nexus7 be run in multi-user mode? [16:18] mfisch: ^^ [16:18] barry, sure [16:18] just create users [16:18] ogra-cb, agreed , is not arch specific [16:18] ogra-cb: beautiful [16:18] * victorp not saying the bug is not valid [16:18] barry: you just have to turn off lightdm autologin [16:18] barry: yes, you probably also need to disable autologin [16:18] yep [16:18] barry, and disable autologin [16:18] perfect [16:18] I guess that would require a keyboard, or does the onboard show up in lightdm/unity-greeter? [16:19] it is in the panel [16:19] an OTG keyboard [16:19] diwic: I think it's loadable [16:19] excellent [16:19] Why is this project ignoring technical, advanced users that already use/test other ROMs? "Legal concerns" cited are a deal breaker. Ignoring as in CyanogenMod has a huge community and no mention on how to flash Ubuntu the usual, safe, roll-back available way. [16:19] edit /etc/lightdm/lightdm.conf [16:19] i have run it with the little usb hub and keyboard/mouse. it works great [16:20] MagicFab, we welcome people to contribute other boot scenarios to the project [16:20] MagicFab adds: if at least there has been testing where recovery is kept and I can rollback to on of my backups, I'd feel safer doing it. [16:20] canonical staff has clear objectives to scratch :) [16:20] victorp has itchy objectives [16:20] I do I do [16:21] MagicFab, does that answer your question? Do you have any follow-up about it? [16:21] victorp, no, Canonical is citing legal concerns not to tackle the huge CyanogenMod / others community of hackers. [16:21] barry: in /etc/lightdm/lightdm.conf you need to comment out this line to disable autologin: autologin-user=ubuntu [16:21] if it's generally possible, we could add it as a TODO item or a FAQ item to the wiki [16:21] MagicFab, that was so that our installer does not contain clockworkmod and similar but it can still be flashed to the recovery partition [16:21] Not really, it's worse. It means to me it's up to "someone" in the community to take some legal risk that is not clear (implied in the Ask Ubuntu reply). [16:21] MagicFab, we focused on a path that will allow us to distribute roms and to focus on the objective to trim the ubuntu desktop to be efficient on an arm device [16:21] mfisch: thanks! [16:22] MagicFab: personally I dont think there's a legal risk to someone in the community doing it [16:22] mfisch: btw, this seems to me to be a huge benefit of ubuntu on tablets as opposed to certain other proprietary platforms [16:22] MagicFab, can you provide a link to the askubuntu question - maybe somebody can look into clarifying the answer [16:22] MagicFab, If other people want to set up alternative installs, we are hoping all the raring packages are available soon [16:22] MagicFab: I think the issue was that canonical cannot ship or support tools like CWM [16:22] victorp, I understand that. [16:22] MagicFab: if you want to write instructions on how to use CWM, cyanogen, nandroid, etc. i am sure we can help you get publicity for it [16:22] MagicFab: if you are familiary with CWM and nandroid (which it appears you are), its certainly do-able, but not something we're pursuing/endorsing in our installation method [16:23] mfisch, then why would you answer that? http://askubuntu.com/a/217146/4601 [16:23] dholbach: here is the U-A question: http://askubuntu.com/questions/216977/how-can-i-install-ubuntu-on-my-nexus-7-while-being-able-to-recover-from-an-nandr/217146#217146 [16:23] * MagicFab confused [16:23] note that currently the bootloader handling (and thus kernel updating etc) is not very flexible [16:23] MagicFab: Canonical, as a company, is not going to ship or support CWM, if the community wants to write up directions, that's fine [16:23] so the installation is required to be exactly the way the ubuntu image sets it up [16:23] even if you use CWM [16:23] vanhoof, to the extent I risk bricking my only, personal device, no, I am not willing to spend time on that. [16:23] MagicFab: I upvoted your comment even [16:24] ogra-cb, vanhoof, ok, those bits are useful. [16:25] MagicFab: for the people that are able and willing to help now, we welcome their support. if you are not willing/able, we understand [16:25] i'm happy to answer any implementation details in #ubuntu-arm at any time [16:25] we don't expect everyone to take on the risk [16:25] another question? [16:25] Are there any plans to bring Ubuntu on other devices? [16:26] achiang, I know - it was just a surprise being used to *any* other alternative ROM brought to the Android community using the standard "flash this zip, don'tlike it, reflash /recover". Guess I'll wait. [16:26] no plans to bring Ubuntu to other devices. we picked a good reference platform and now we want everyone to rally around it [16:26] MagicFab, point is that we are not targeting the android community [16:26] MagicFab: this is *not* another alternative ROM and this is Ubuntu, not android. [16:27] but the ubuntu one [16:27] obounaim: if you'd like to work on a port we'd all be happy to help though in #ubuntu-arm [16:27] ogra-cb, ok, that's not the tone of the blog posts, etc. I get it now. [16:27] obounaim, some community people seem to work on chromebook support [16:28] achiang, of course :) But you're asking Android users to test on their device. I expected being able to get back to its current state. NP, I see how I confused this. [16:28] MagicFab: happy to discuss in #ubuntu-arm after this meeting. :) [16:28] MagicFab, well, most if not all blog posts say that we want to make the platform fit for small devices ... and platform here means mostly the plumbing layer [16:28] let's move on [16:28] The next question seems to be a pressing one. cjwatson, Riddell and victorp asked the same question in different forms: I would also like to ask about when raring images will be available and how are we doing with triaging/assigning bugs [16:28] obounaim, this is assuming you're talking about tablets. We have a lot of x86 desktops and laptops certified and pre-installed :-) ubuntu.com/certification, and ogra-cb can fill in on other ARM projects [16:29] question: How far are we from being able to run straight raring? I'm running mostly raring now, but still have some bits from the PPA [16:29] mfisch, I am not paid for this. I am willing to test for free but my current involvement is more as a power-user/tester. [16:29] question: what's the state of daily image builds? [16:29] no focus on any desktop funtionality, endusers or android hackers atm [16:29] dholbach, all, tx. [16:29] thanks MagicFab [16:29] back up anroid > install U fro n7 > test > reset android > restore [16:29] dholbach et al: Raring is coming soon [16:29] so, currently we have a few outstanding issues [16:29] we're blocked on a Nux problem currently [16:29] FWIW I pinned the PPA and upgraded rather than worrying about daily builds [16:29] the nux fix should land today [16:29] mfisch: the old drop shadow one? [16:30] once the nux fix lands, it will be safe for people to dist-upgrade to raring [16:30] cwayne: no, thats not a blocker [16:30] Riddell, nonexistent until IS has set up a new builder machine for arm images [16:30] that is different from daily images [16:30] daily images are blocked on new hardware [16:30] oh right, the transparency one, duh [16:30] Yeah, I know about the daily builds issue, since it affects all ARM images [16:30] cjohnston, might probablz help to addd something abotu that to the wiki [16:30] achiang, so apart from nux, everything in https://launchpad.net/~ubuntu-nexus7/+archive/ppa is in raring? do we have a bug number for the nux problem? [16:30] err cjwatson [16:30] silly tab completion [16:31] dholbach: Right, that's what I was getting at [16:31] I think this is the nux bug: #1065638 Unity panels don't display visuals [16:31] Launchpad bug 1065638 in ubuntu-nexus7 "Unity panels don't display visuals" [Critical,Confirmed] https://launchpad.net/bugs/1065638 [16:31] not everything, the settings arent yet (but will come soon) [16:31] There are definitely still packages in the PPA that are not in raring [16:32] and i'm not sure jabout the brcm-patchram stuff [16:32] dholbach: but we do not need to push the PPA packages into raring. the next interim phase will be: 1) install from existing installer 2) dist-upgrade to raring [16:32] as it is clearly the wrong approach for the distro [16:32] action for someone to push ppa pkgs to R? [16:32] victorp: regarding bug triage, we've done an excellent job, I think, of getting stuff upstreamed and then diving back into some bugs to gather more info. Some of the upstream bugs unfortunately are not getting much attention [16:32] the final phase will be to push all the PPA bits into raring, and then we'll have daily images [16:32] victorp: specifically I'd love to have some unity help [16:32] mfisch, I see lots of bugs that are unassigned can we fix that? [16:33] like Ubuntu bugs [16:33] victorp: but also something interesting is that say, 80-90% of our bugs are not specific to the N7 [16:33] victorp: I'd love to get people assigned, but how would I do that? I'm not sure who could help (for example) with Unity bugs [16:33] (Everyone who's interested and has more questions, please message me and I'll queue them up. Please don't be shy. :-)) [16:33] ogra-cb: I'll take the patchram action [16:34] vanhoof, that will likely need patches to bluez to be done right [16:34] ogra-cb: its been something that needs to be sorted out across the board [16:34] or even the kernel [16:34] iirc there are some patches that add kernel support for patchram already but not finished [16:35] achiang: one certainly can already do that, just with apt pinning [16:35] ogra-cb: theres been some preliminary work already which hit the kernel-team lists for quantal and precise a few weeks back [16:35] dholbach: summary is, we hope people can be on raring as soon as the nux fix lands. we will send out an announcement when it is safe to do so, hopefully early next week, say tuesday [16:35] ogra-cb: yup [16:35] the current package rather follows a broken approach [16:35] achiang, perfect [16:35] cjwatson: yeah, but not everyone is good at/competent with apt-pinning [16:35] achiang: is the raring plan just to ask people to change sources and upgrade? [16:35] Yeah, just saying, it's a kind of stage 0 [16:35] mfisch: yes, until we can produce dailies [16:35] In terms of getting bugs looked at - would it help to also send a quick summary of blocker bugs to one of the mailing lists? [16:35] i would say latest mid next week we should have dailies [16:36] $ cat /etc/apt/preferences.d/ubuntu-nexus7-ppa [16:36] Package: * [16:36] Pin: release o=LP-PPA-ubuntu-nexus7 [16:36] Pin-Priority: 600 [16:36] cjwatson: can you post your pinning snippet? we could put it in the FAQ [16:36] FWIW [16:36] psychic! :) [16:36] mfisch lets talk about that we need to find someone in desktop that can drive it [16:36] victorp: great [16:36] can someone take an action to put the pinning stuff above on the wiki for the brave ones [16:37] can do [16:37] dholbach: i think we truly only have 1 blocker. but i would be happy to send a weekly "top X bugs" to ubuntu-devel or wherever is appropriate [16:37] dholbach: sure, we could do that, right now the only major blocker besides nux is that stuck button1 issue. [16:37] I'd love to do that actually if we think it will generate interest [16:37] achiang, that'd be awesome [16:37] achiang: I can drive a report like that [16:37] ok, consider us signed up for it [16:38] vanhoof, mfisch: maybe you'll find https://code.launchpad.net/~dholbach/+junk/nexus7-report interesting - it's something I quickly put together [16:38] fantastic [16:38] preferences on where to send, ubuntu-devel@ work for everyone? [16:38] yes, that should be good [16:38] also, someone from my team will also take the action to post the apt-pinning recipe [16:38] achiang, I was going to do it, but I won't object ;-) [16:38] * mfisch branches dholbach's code [16:39] * achiang adds dholbach to my team, and considers the action taken care of ;) [16:39] haha [16:39] :-) [16:39] so I'd like the report to be more than a buglist, and I claim that cwayne and I have the most knowledge of bug status [16:39] dholbach: thanks for the pointer [16:39] list + some info/status/progress [16:39] mfisch: +1 [16:39] vanhoof: please work w/mfisch and cwayne on the report [16:39] +1 === rsalveti_ is now known as rsalveti [16:40] mfisch: cwayne: ill show you what I had in mind and we can go from there [16:40] ./report (per dholbach branch) [16:40] vanhoof: +1 === Ursinha_ is now known as Ursinha [16:40] Riddell, victorp, cjwatson: did your questions get sufficiently answered? [16:40] Yes [16:40] yes [16:41] shall we do a quick bug review after the questions? [16:41] yes [16:41] cool [16:41] dholbach, report output: http://paste.ubuntu.com/1363002/ [16:41] so I have one question from jcastro_ - he wanted to know if we're moving the FAQ to Ask Ubuntu [16:41] (If any of you have more questions, please message me. The queue is empty right now.) [16:41] cwayne, you might know about the AskUbuntu FAQ situation [16:42] dholbach: jcastro_: I'd like to eventually move it over. Some of the questions may need to be combined or added to.. [16:42] jcastro_: Can I ask a question and answer it myself? How can I get it pinned to the FAQ tab? [16:43] cwayne, for now, maybe add intro to wiki FAQ saying from now on use ask ubuntu (and how) [16:43] kyleN_: well theres nowehere else to ask questions anyway :P [16:44] all of the ?'s in the FAQ were from that one session [16:44] dholbach: jcastro_: yes, as soon as we clean up the FAQ we will definitely move it to AskUbuntu. at the moment, we're just trying to unbury ourselves from incoming bugs [16:44] so that would be a good place for folks to help [16:44] This seems to be all the questions we had - you can of course all ask more questions and get in touch with the team in #ubuntu-arm and get involved there. :-) [16:44] help us get the incoming bugs linked against the proper upstreams (as many of them are not specific to the nexus7 at all) would be a huge help [16:45] One of the more time consuming parts of looking at our bugs is trying the issues on other devices and looking at upstream [16:45] and then duping back [16:45] This nicely leads us to our next topic... :) [16:45] #topic Bug review: https://bugs.launchpad.net/ubuntu-nexus7 === meetingology changed the topic of #ubuntu-meeting to: Bug review: https://bugs.launchpad.net/ubuntu-nexus7 [16:45] if you see an new bug, e.g., you could try to reproduce on your x86 laptop [16:45] cwayne: you can absolutely ask and answer your own, the FAQ part is autogenerated based on votes/traffic, and people linking to it [16:45] in many cases, you will see the same issue [16:46] jcastro_: but I can't trick it to ensure it goes in FAQ? [16:46] well i guess if it doesn't get traffic, it's not really frequently asked is it :P [16:46] right [16:46] * cwayne takes an action to begin the transfer to AU today [16:46] cwayne: if everyone on the team votes on stuff accordingly it'll work itself out [16:46] another triage note: If you find a N7 bug that has an older duplicate in another project, please dupe the new bug, then go to the older bug and mark as affecting N7. Or just find me, achiang, and cwayne and we can help [16:46] awesome [16:46] victorp, you wanted to talk some more about bugs? [16:47] dholbach, nope I am fine [16:47] mfisch answered my question [16:47] if anyone is planning on logging bugs, this may help explain what we're looking for: http://chrismwayne.com/?p=94 [16:47] [16:47] oh, I thought somebody wanted to do a review of the open bugs, blockers, status of assigned bugs and so on? [16:47] dholbach: I have a topic real quick [16:48] sure [16:48] cwayne, that would be good to be *the wiki* [16:48] cwayne, put on wiki [16:48] can achiang or janimo explain the plan for migrating to an official Ubuntu kernel config? [16:48] figure some people would like to know [16:48] mfisch, kernel team will do it :) [16:48] victorp: sure [16:48] the kernel is now maintained by the ubuntu kernel team [16:48] janimo: just the config or will the Ubuntu specific patches also be merged? [16:49] mfisch, hopefully everything [16:49] as long as they can be applied to 3.1 I guess [16:49] janimo: great, that should close out a bunch of bugs when it happens [16:49] well, not everything :) [16:49] we surely dont want all options an ubuntu kernel has by default [16:49] janimo: any ideas when this will happen? [16:49] * ogra-cb doesnt care much about hardware raid controllers on his nexus [16:49] ogra-cb: but we do want more modules enabled [16:50] mfisch: can you take us through a list of the most pressing bugs this week? [16:50] we want everything enabled you can attach [16:50] and we can see if we need help anywhere [16:50] mfisch, no, but it is on the kernel team's (which I am not part of) agenda [16:50] whcih largely means USB and BT [16:50] janimo: thanks [16:50] achiang: sure [16:50] mfisch: that is being worked out atm as we prepare for R [16:50] dholbach: I'll go over the top most pressing bugs [16:50] thanks [16:50] mfisch: as things progress, we can report back status here or in the wiki [16:51] vanhoof: great [16:51] So the top bug is the Nux issue: #1065638 Unity panels don't display visuals [16:51] we have a patch for Q in our PPA [16:51] and apparently a fix in R is landing soon [16:51] i poked jay taoko today, and he says he's preparing a branch for landing "today" [16:52] great [16:52] what about the button 1 thing ? [16:52] the next bug is the bug where the input gets stuck, as if the left button mouse is pressed: #1068994 button1 gets stuck after a while [16:52] * ogra-cb would actually see that as more important [16:52] we have no fix for this in Q or R currently [16:52] 1068994 dandrader button1 gets stuck after a while [16:52] there is a developer working on it, but X is ... huge and hard to debug [16:53] achiang: any updates on this? I know it's being worked but that's all [16:53] ok [16:53] i will poke dandrader on this one [16:53] http://paste.ubuntu.com/1363002/ has a list of currently assigned bugs [16:53] (in the ubuntu-nexus7 project) [16:53] past those 2 bugs, we're in opinion territory for next most critical, but I'm going with this one: #1068804 sound only works after suspend/resume cycle [16:54] rotation ! [16:54] * achiang owns an action to escalate to nvidia on the sound bug, will do today [16:54] diwic did a lot of work on this, but at this point we're asking nVidia for help [16:54] ogra-cb, that's a missing feature not a bug :) [16:54] ogra-cb: I'm smart enough to not rotate my device ;) [16:54] JanC, the feature is there but its buggy :P [16:54] bah [16:54] janimo, ^^ [16:55] so as ogra-cb says we have several rotation bugs [16:55] rotation causes screen corruption [16:55] sometimes doesn't rotate input [16:55] doesn't auto-rotate [16:55] (chrome doesn't rotate on Android JB) [16:55] and the device doesn't autorotate when you physically move it [16:56] kyleN_, it does for me [16:56] is bryceh working on those? [16:56] mfisch: do we have a plan on looking into the accelerometer that you know of? [16:56] i bet bryceh is playing video games 16 hours a day right now ;) [16:56] I believe actually that none of them are being worked [16:57] vanhoof, yes it's on my plate [16:57] achiang, hopefully [16:57]