[03:40] <ameer> Hey.... any one there
[03:42] <ameer> How to detect filemanager data in qml
[03:42] <ameer> ???
[07:07] <mihir_> Good Morning guys :)
[07:38] <dpm> good morning
[07:41] <mihir_> dpm:  Good morning :)
[07:41] <mihir_> Anyone with device can test this MR on device ?  https://code.launchpad.net/~ravirdv/ubuntu-calculator-app/calculator_label_width_fix
[07:55] <dholbach> good morning
[07:58] <dpm> morning dholbach
[07:59] <dholbach> hey dpm
[07:59] <seb128> hey dpm dholbach
[08:00] <dpm> morning seb128, how's it going today?
[08:01] <dpm> good work with the system settings summary e-mails btw, they're very useful to see what's going on
[08:01] <seb128> dpm, thanks ;-)
[08:36] <mihir_> dpm:  hey , how are you doing ?
[08:41] <dpm> hi mihir_, very well, thanks, and you?
[08:41] <mihir_> yes doing good :) thank you :)
[08:42] <mihir_> dpm:  I have translated calculator app in my native lanungage..the application will automatically take the translation ?
[08:43] <dpm> mihir_, if you translated it in Launchpad, yes. Translations are picked up from there and automatically committed to trunk daily :)
[08:43] <mihir_> dpm:  okay thank you :)
[08:48] <oSoMoN> gusch: good morning
[08:48] <gusch> oSoMoN: hi
[08:48] <oSoMoN> gusch: first MR of the day: https://code.launchpad.net/~osomon/webbrowser-app/lastVisit/+merge/178790
[08:48] <gusch> oSoMoN: you start early ;) - I'm on it ...
[08:54] <oSoMoN> gusch: I’m cheating, I submitted it yesterday :)
[09:01] <gusch> oSoMoN: is there something to test in the UI?
[09:02] <oSoMoN> gusch: it’s not 100% reproducible, but I’ve observed that sometimes the list of domains doesn’t remain sorted chronologically, so if you open a number of different websites while keeping the activity view open, eventually you will see that some domains move to where they shouldn’t be, and this MR fixes it
[09:03] <oSoMoN> gusch: basically, iterating over the list of entries outside of the model itself was unreliable, as there was no guarantee the indexes had been fully updated (most of the time they were half updated, which caused weird issues)
[09:04] <oSoMoN> gusch: doing it inside the model guarantees that when m_lastVisit is assigned, the indexes have been fully updated, and so the first entry is guaranteed to be the one we’re interested in
[09:14] <JamesTait> Good morning all, happy Lighthouse Day! :-D
[09:15] <gusch> oSoMoN: approved
[09:15] <oSoMoN> gusch: thanks!
[09:57] <mihir_> dpm:  could you please help me to review this https://code.launchpad.net/~mihirsoni-123/ubuntu-calculator-app/RemovedOnclick-1207685/+merge/178526 if you get time :)
[10:01] <dpm> mihir_, sure, looking at it now...
[10:09] <dpm> mihir_, done, thanks for the branch!
[10:11] <mihir_> dpm:  Thank you :) I'll look into it :)
[10:14] <dpm> cool
[10:18] <mihir_> dpm: One question I found another scenario ,
[10:18] <mihir_> 2+2 = 4 now what if user tap on the previous result ?? what should be the exepected result ??
[10:20] <nerochiaro> oSoMoN: zsombi: Kaleo: I have been tasked to transform the share-app in a component. do you think it should live inside ubuntu-ui-extras or in a new separate repo ?
[10:20] <nerochiaro> oSoMoN: zsombi: Kaleo: or maybe split share-app in app and component and leave everything in there, and the app will be used only as example or for tests ?
[10:25] <dpm> mihir_, let me get christina in here to ask her
[10:25] <mihir_> dpm:  sure :)
[10:26] <mihir_> dpm: I am unable to review translation done by someother guy in calendar application https://translations.launchpad.net/ubuntu-calendar-app/trunk/+pots/calendar-app/gu/+translate?memo=10&start=10
[10:27] <gusch> nerochiaro: can you do that? https://code.launchpad.net/~schwann/qtubuntu-camera/qtcamera-vp-flash/+merge/178784
[10:30] <nerochiaro> gusch: are you sure that there is no possibility of phones haveing a screen-facing camera and a light ?
[10:30] <dpm> hi christina, thanks for joining! mihir_ had a question on what to do when tapping on the result from a previous calculation. mihir_ could you expand on that?
[10:31] <christina> hi dpm, hi mihir_ - i am just going into a meeting now, but if you leave me some notes i can answer when im back :)
[10:32] <zsombi> nerochiaro :Kaleo: my opinion is to be placed in extras
[10:32] <mihir_> christina: Hi Christina thank you for joining I am working on bug https://code.launchpad.net/~mihirsoni-123/ubuntu-calculator-app/RemovedOnclick-1207685/+merge/178526
[10:32] <oSoMoN> nerochiaro: re-the split of share app, I think it would be a good candidate for ubuntu-ui-extras, but the other option you’re proposing sounds good too
[10:33] <mihir_> It copy result from previous result
[10:33] <mihir_> In following scenario , what should be the exepcted result
[10:33] <mihir_> 2+2 = 4 now what if user tap on the previous result (Without starting new converstation) ?? what should be the exepected result ??
[10:33] <nerochiaro> oSoMoN: zsombi: Kaleo: i'll go with extras then. Will ask to remove the share-app repo later when it's done
[10:34] <mihir_> christina: No issues :) this is a scenario i came across let me know the expected result of this scenario :)
[10:34] <dpm> mihir_, my understanding is that nothing should happen as I described on the merge proposal, but let's see if design has got any other view
[10:35] <mihir_> dpm: so that means untill user start new converstation it shouldn't react right once equal is tapped?
[10:36] <dpm> mihir_, that's what I understand, yeah. Until the user tears off the calculation, tapping on operands or on the result of the current calculation shouldn't do anything
[10:37] <dpm> basically, the same behaviour that the app has at the moment
[10:37] <dpm> (except for the bug)
[10:38] <mihir_> dpm: Okay :)  let me try to implement that :)
[10:38] <dpm> cool, thanks!
[10:39] <dpm> nerochiaro, oSoMoN, gusch, if you're on the latest build and have got a device with you, could you help me and christina determine if the weather app toolbar works as expected? It's basically about loading the weather app on the device and pull the toolbar to see if it's empty or if it contains the toolbar actions as expected
[10:39] <dpm> it shouldn't take more than a few seconds, and would be really helpful :)
[10:40] <oSoMoN> dpm: sure, will do that in a moment once the tests that I’m running on the device are done
[10:40] <dpm> great, thanks!
[10:46] <gusch> nerochiaro: thi si not the to properly detect if the light is available (from android)
[10:46] <oSoMoN> gusch: next MR of the day: https://code.launchpad.net/~osomon/webbrowser-app/fix-crash-collapsing-domain/+merge/178919
[10:46] <nerochiaro> dpm: i need to reflash to the latest. do you want me to test on a regular update or with --pending ?
[10:47] <nerochiaro> gusch: sorry, didn't undersand your last comment
[10:47] <dpm> nerochiaro, a regular update would do
[10:47] <oSoMoN> dpm: I’m not seeing any toolbar in the weather app, when I swipe from the bottom edge I’m getting the HUD icon only
[10:47] <nerochiaro> dpm: ok, flashing, will test in a bit
[10:47] <oSoMoN> dpm: I’ve got ubuntu-weather-app 0.2bzr84saucy0
[10:48] <dpm> oSoMoN, thanks. And you had a location defined in the app, too?
[10:48] <gusch> nerochiaro: about your question "are you sure that there is no possibility of phones haveing a screen-facing camera and a light ?"
[10:48] <gusch> oSoMoN: looking at it
[10:49] <nerochiaro> gusch: ok, but then i'm not sure what the MR is about. you basically remove all the code for reporting the flash/torch modes and replace it with hardcoded results
[10:49] <oSoMoN> dpm: it says "Current location | Lookup location (Dummy)"
[10:50] <oSoMoN> dpm: wait, I was on the "add location" screen which showed up by default when I started the app
[10:50] <gusch> nerochiaro: well - most important here is, that photo and video share the same flash modes
[10:50] <dpm> oSoMoN, ah, you're on the initial screen with the location settings. Could you try to add a location and press confirm, and then see if you can pull the toolbar on the next screen?
[10:50] <dpm> yeah
[10:50] <gusch> nerochiaro: that's needed for flash
[10:50] <gusch> nerochiaro: that's needed for torch
[10:50] <oSoMoN> dpm: now that I chose a city, I’m seeing the toolbar work, it has three actions "refresh", "edit", "settings"
[10:50] <dpm> oSoMoN, perfect, so it seems to work as expected. Thanks!
[10:51] <oSoMoN> yw
[10:51] <oSoMoN> dpm: the app looks pretty neat, first time I’m running it :)
[10:51] <dpm> nice :)
[10:52] <dpm> oSoMoN, if you notice any bugs, feel free to report them on https://bugs.launchpad.net/ubuntu-weather-app/ :)
[10:56] <nerochiaro> gusch: so basically it should be possible to enable also torch while in picture mode ?
[10:56] <oSoMoN> dpm: sure, will do
[10:57] <oSoMoN> dpm: would "the weather is weird around here today" be considered a valid bug? ;)
[10:57] <gusch> nerochiaro: yes, not in the camera, but for the Qt QML Torch component
[10:57] <dpm> oSoMoN, perhaps, but don't expect the developers to fix the weather :-)
[10:58]  * oSoMoN knew it…
[10:58] <dpm> :)
[10:58] <nerochiaro> gusch: well, i'm gonna approve it because it doesn't seem to have any real effect on camera.
[10:58] <nerochiaro> gusch: but i'm still not sure i see the point
[10:59] <gusch> nerochiaro: hmmm - we don't have a torch app, to see that it currently is broken ...
[10:59] <gusch> nerochiaro: but thx
[11:26] <gusch> oSoMoN: approved the crash
[11:27] <oSoMoN> gusch: thanks
[12:02] <nerochiaro> dpm: i got no toolbar on the weather app as well
[12:03] <nerochiaro> greyback: on the latest image have you noticed how the shell isn't showing icons for some apps ?
[12:03] <nerochiaro> greyback: and the converter app appears twice
[12:05] <greyback> nerochiaro: this in apps lens, or launcher?
[12:05] <nerochiaro> greyback: app lens
[12:06] <nerochiaro> greyback: reflashing with --pending as i need to test something else, will let you know if it's still happening
[12:06] <greyback> nerochiaro: that data is coming from an actual apps lens, it's not faked any more. Lens got confused??
[12:07] <nerochiaro> greyback: i guess. let's see if it's still there, if it is we can try to figure out what's happening
[12:07] <greyback> nerochiaro: agreed
[12:09] <dpm> nerochiaro, thanks for testing. And this is after you've added a location?
[12:09] <nerochiaro> dpm: no, didn't try that
[12:09] <dpm> nerochiaro, ah, you'll need to add a location first. The toolbar is only shown on the weather screen
[12:10] <nerochiaro> dpm: i find it confusing that you can't add a location from the toolbar
[12:10] <nerochiaro> dpm: i'm currently reflashing the phone again, will try adding a location when it's finished and let you know
[12:11] <dpm> nerochiaro, that's probably a question for design, but essentially, the "new location" screen is shown if you don't have any locations defined upon start, so there is no need for a toolbar there. Once you've added a location, the weather screen is shown and from there you can manage your locations from the toolbar
[12:11] <nerochiaro> Kaleo: zsombi: timp: oSoMoN: ubuntu-ui-extras is still pending the initial commit, can anyone take care of approving it now that Jenkins has all test passing on the MR: https://code.launchpad.net/~amanzi-team/ubuntu-ui-extras/ubuntu-ui-extras-initial/+merge/171086
[12:12] <nerochiaro> dpm: ok, if that's the way it's been designed let's roll with it
[12:12] <dpm> :)
[12:15] <zsombi> nerochiaro: uhh... that's not that fast to review... hasn't this been reviewed by someone of us months ago?
[12:15] <nerochiaro> zsombi: that's fast because after the last commit there's only a skeleton example left in there
[12:16] <nerochiaro> zsombi: and yeah, you guys started reviewing but never finished
[12:16] <zsombi> nerochiaro: so a proper review has never been done then...
[12:17] <nerochiaro> zsombi: not a full one I guess
[12:17] <zsombi> s/proper/complete
[12:19] <nerochiaro> zsombi: i'm also not sure who should be in charge of that
[12:19] <zsombi> nerochiaro: :) "you are not alone..."
[12:23] <om26er> gusch, ping
[12:23] <gusch> om26er: pong
[12:23] <om26er> hey, this test is specifically failing on mako camera_app.tests.test_focus.TestFocus.test_focus_valid_and_disappear
[12:24] <om26er> gusch, i have seen in a video that the camera goes blank
[12:24] <om26er> gusch, it does not happen always but in most cases (given you have the very latest image) running the whole suite will end up with a failure of that test
[12:25] <gusch> om26er: hmmm - might be https://bugs.launchpad.net/camera-app/+bug/1204260
[12:25] <ubot2`> Ubuntu bug 1204260 in touch-preview-images "[camera-app][mako] switching cameras crashes mm-qcamera-daemon" [High,Confirmed]
[12:25] <gusch> om26er: but I don't have mako, so I can't check it ...
[12:25] <om26er> gusch, its probable, the issue happened while it was switching cameras
[12:26] <om26er> gusch, you should get a nexus 4 :)
[12:27] <gusch> om26er: and a 7, and ... ;)
[12:39] <nerochiaro> zsombi: so any idea what should I do about it ?
[12:39] <zsombi> nerochiaro: checking the MR...
[12:41] <zsombi> nerochiaro: I guess it should be us who should own it, but discuss this with bzoltan
[12:45] <nerochiaro> bzoltan: zsombi: Kaleo was of the idea that the sdk team should own it too, if i recall correctly
[12:45] <nerochiaro> bzoltan: talking about lp:ubuntu-ui-extras
[12:46] <nerochiaro> greyback: still broken (missing icons) in latest image with --pending
[12:46] <bzoltan> nerochiaro: let me see it
[12:47] <nerochiaro> bzoltan: the main branch is empty, there's a branch pending merge into it that contains the current initial code
[12:47] <nerochiaro> bzoltan: it's only a skeleton example for adding a new component in there, at the moment
[12:47] <zsombi> bzoltan: nerochiaro: if we get it under SDK, then my only question is whether we should have a separate project for it, or should we put under the same code base as the current SDK is.
[12:48] <zsombi> bzoltan: nerochiaro: the current branch (the initial one) is based on cmake and our one is on qmake...
[12:48] <nerochiaro> bzoltan: zsombi: separate project, as it doesn't have to match the same standards as the sdk (as evidenced by the description that Kaleo put on the lp project)
[12:48] <nerochiaro> zsombi: i'm fine with either, i just used cmake as it was what i was used to from other projects
[12:49] <zsombi> nerochiaro: then it can live in its own way, with whatever build system it has now
[12:49] <nerochiaro> dpm: with latest image and --pending the weather app shows the toolbar after adding a location. toolbar has refresh, edit and settings buttons
[12:49] <nerochiaro> zsombi: great
[12:49] <dpm> perfect, thanks a lot nerochiaro for testing!
[12:49] <zsombi> nerochiaro: I have nothing else to comment on the MR then :)
[12:49] <bzoltan> nerochiaro:  let me talk with Kaleo about it.
[12:50] <nerochiaro> dpm: you're welcome
[12:50] <nerochiaro> zsombi: then give your comment-approval at least
[12:50] <nerochiaro> bzoltan: ok, thank you
[12:51] <zsombi> nerochiaro: you have it!
[12:52] <bzoltan> nerochiaro:  My inner sense says that if something belongs to the SDK team than the same quality standard applies as to any other project... If that project would be a home for components and APIs we do not officially support or do not consider mature enough then I would suggest to create a Ubuntu.Components-Extras under the UI TK project.
[12:56] <zsombi> bzoltan: +1
[12:59] <nerochiaro> bzoltan: the current organization and repo was discussed with Kaleo and AFAIK approved by him
[12:59] <bzoltan> nerochiaro: Is there a mail, irc log or anything about it?
[12:59] <bzoltan> nerochiaro: I would like to hear Kaleo's idea in details
[13:00] <Kaleo> nerochiaro: do you have the link to the google doc?
[13:00] <nerochiaro> Kaleo: bzoltan: looking for the doc
[13:01] <nerochiaro> Kaleo: bzoltan: https://docs.google.com/a/canonical.com/document/d/1xGmQd1qRMFIHIupybpzFmIZHRGUmRhSJanX62ElG5EA/edit
[13:02] <bzoltan> Guys that document starts with perfect explanation why I would never touch that project :)
[13:02] <bzoltan> QML components that either: - won’t necessarily see much reuse - does not have the necessary level of quality ...
[13:03] <bzoltan> nerochiaro: Kaleo:  Why to move our finger if a component (1)is useless crap (2)
[13:05] <nerochiaro> bzoltan: Kaleo: i don't necessarily agree with that definition. I just want to have a place where to put some components that don't have any other place to go. for example now i need to put the sharing component somewhere, and that seems a pretty good place
[13:05] <Kaleo> nerochiaro: go for it
[13:06] <Kaleo> nerochiaro: however, review wise I would suggest to do what you would do for your app
[13:06] <bzoltan>  nerochiaro:  we need a sharing component. It is on the list....
[13:07] <nerochiaro> Kaleo: yes, but before that I would like to have the pending merge request merged into the trunk of that repo. i'll then have whoever would be responsible to review the share-app review the share component when i propose it for review into the ubuntu-ui-tookit repo
[13:07] <nerochiaro> bzoltan: i was tasked by bfiller to transform share-app into a component. i need a place to put it. that's all i know. if you guys are planning to make a different one, we need to talk about it
[13:08] <bzoltan> nerochiaro:  let's do it the right way than... but I would not suggest to create a shadow UITK where different rules apply than in the real one....I agree that if the community needs components and want to create projects-packages they are free to do.
[13:11] <nerochiaro> bzoltan: i'm not sure what you're suggesting I do
[13:12] <Kaleo> nerochiaro: I see the MR is approved
[13:12] <nerochiaro> Kaleo: thank you
[13:12] <Kaleo> nerochiaro: 20 minutes ago :)
[13:12] <nerochiaro> Kaleo: yeah :)
[13:30] <om26er> nik90, when you get the time https://code.launchpad.net/~om26er/ubuntu-clock-app/fix_autopilot_on_touch/+merge/178443
[13:31] <nik90> om26er: definitely
[13:32] <bzoltan> nerochiaro:  I suggest that if you plan to work on a component what is on the roadmap of the UITK project then just contribute it to the UITK
[13:37] <nerochiaro> bzoltan: i had no idea it was on the roadmap, and i suppose that i can start working on it there and then if you guys think it's ok we can move it to the main UITK ?
[13:38] <nik90> om26er: 3 tests are failing. You can find the output at http://paste.ubuntu.com/5958920/
[13:38] <nerochiaro> zsombi: are the changes in IMA we were discussing yesterday already in the SDK that goes into today's image smoke tests ?
[13:38] <nik90> om26er: you used timer_page and then returned time_page instead
[13:39] <om26er> hah
[13:39] <om26er> nik90, fixing
[13:39] <nik90> om26er: :)
[13:39] <zsombi> nerochiaro: haven't checked, however it got merged into the SDK trunk...
[13:40] <om26er> nik90, done
[13:40] <bzoltan> nerochiaro:  Good that it came out then :) Yes, let's shoot for normal and full integration to the UI TK
[13:40] <zsombi> nerochiaro: this one also sais it's in: https://code.launchpad.net/~ps-jenkins/ubuntu-ui-toolkit/latestsnapshot-0.1.46+13.10.20130807-0ubuntu1/+merge/178920
[13:42] <nerochiaro> zsombi: it seems that we have one test failing and i suspect this to the cause
[13:42] <zsombi> ?
[13:45] <gusch> oSoMoN: to make gallery crop test work with the latest SDK https://code.launchpad.net/~schwann/gallery-app/gallery-close-toolbar-on-edit/+merge/178961
[13:45] <zsombi> nerochiaro: which one?
[13:47] <oSoMoN> nerochiaro: in the tests where you wait for the note to be expanded, are you also verifying that the 'state' property of the note is 'expanded' (or something like that)?
[13:48] <nerochiaro> zsombi: https://jenkins.qa.ubuntu.com/job/saucy-touch-mako-smoke-notes-app-autopilot/47/consoleText
[13:49] <nerochiaro> oSoMoN: i'm not in this specific case, but the property change is what actually triggers the height change, so i thought there was no need to do it
[13:51] <oSoMoN> nerochiaro: agreed, in theory there shouldn’t be any need, but in practice having more checks allows easier debugging of failures, which is why I was asking
[13:51] <nerochiaro> oSoMoN: makes sense,
[14:08] <gusch> oSoMoN: to make gallery crop test work with the latest SDK https://code.launchpad.net/~schwann/gallery-app/gallery-close-toolbar-on-edit/+merge/178961
[14:18] <oSoMoN> gusch: is there a bug associated to your MR?
[14:18] <gusch> oSoMoN: no - I only came across that issue, because I wanted to get this merged... https://code.launchpad.net/~schwann/gallery-app/gallery-uitk-emulators/+merge/178330
[14:19] <oSoMoN> gusch: ok, thanks
[14:43] <nerochiaro> oSoMoN: i'm not really sure what to do to fix that failing test, i doubt adding the extra check or isExpanded will solve the problem, but I can certainl try
[14:44] <oSoMoN> nerochiaro: can you point me to the code of the failing test? I’ll have a look too
[14:49] <oSoMoN> gusch: approved, please see my comment
[14:49] <nerochiaro> oSoMoN: sure, hold on
[14:51] <nerochiaro> oSoMoN: http://bazaar.launchpad.net/~phablet-team/notes-app/trunk/view/head:/tests/autopilot/notes_app/tests/test_parts.py#L55 this is the function that fails in that specific case, but as you can see  it is used other cases that don't fail
[14:56] <gusch> oSoMoN: thx
[15:00] <oSoMoN> nerochiaro: what is the height of a collapsed note?
[15:01] <nerochiaro> oSoMoN: 11 gu
[15:02] <oSoMoN> nerochiaro: ok, so in the failing test the note wasn’t expanded at all, it remained collapsed (as opposed to being expanded halfway or something like that)
[15:03] <nerochiaro> oSoMoN: ok, that means that the click on the note wasn't registered for some reson. but it's a standard click so i'm not sure what can go wrong. self.pointing_device.click_object(note)
[15:34] <mhall119> http://developer.ubuntu.com/2013/08/announcing-the-2013-ubuntu-app-showdown-contest/
[15:34] <mhall119> a new contest for Ubuntu Touch app developers!
[15:34] <WebbyIT> mhall119, \o/
[15:39] <nik90> mhall119: awesome!
[15:45] <WebbyIT> dpm, about bug 1204702 you saw that the music app team as wrote some code, but I'm not able to find it, can you help me?
[15:45] <ubot2`> Launchpad bug 1204702 in Ubuntu Calculator App "ubuntu-calculator-app does no db upgrade to 0.1.1 on first start" [High,In progress] https://launchpad.net/bugs/1204702
[15:45] <WebbyIT> dpm, if you have time, I'll say you what problem I'm finding to fix it
[15:46] <dpm> WebbyIT, let me see
[15:47] <WebbyIT> dpm, I'm searching a way to have more upgrade, one after the other, so I think to a recursive function but...
[15:48] <WebbyIT> ... dpm, db.changeversion doesn't work as I expected, see http://askubuntu.com/questions/327594/db-changeversion-doesnt-work-as-expected
[15:49] <WebbyIT> dpm, I thinking something like http://paste.ubuntu.com/5959364/
[15:50] <WebbyIT> dpm, I can do more cases to avoid intermediate version of db, but in case of future upgrade will be a mess
[15:53] <dpm> WebbyIT, I've just found how they did it at the bottom of the diff for https://code.launchpad.net/~danielholm/music-app/show-tracks-in-playlists/+merge/175333
[15:53] <dpm> however, I'm not sure it's the best way
[15:54] <WebbyIT> dpm, that is a wrong way, because at the first start the db will be create but NOT update to v1.1
[15:55] <dpm> yeah, I didn't look into it in detail, but somehow it didn't look good to me
[15:56] <WebbyIT> dpm, is the same code we are in calc, we have to find a way to have something that can allow to have more than one upgrade
[16:00] <WebbyIT> dpm, I also tried http://stackoverflow.com/questions/11834739/phonegap-android-database-changeversion-not-functioning dut unfortunately doesn't work :(
[16:47] <boiko> om26er: ping
[16:47] <om26er> boiko, pong
[16:47] <boiko> om26er: hi, do you know why on this MR jenkins didn't post the URL for the deb packages? https://code.launchpad.net/~tiagosh/telepathy-ofono/audioflinger-speakermode/+merge/178873
[16:49] <om26er> boiko, the job needs to be changed to post debs
[16:49] <om26er> boiko, I can enable that if you want
[16:50] <boiko> om26er: that would be awesome
[16:55] <boiko> om26er: thanks
[17:06] <om26er> boiko, its good to go, you can re-build to have the debs now
[17:07] <boiko> om26er: thanks!
[17:08] <om26er> boiko, np :)
[17:09] <om26er> oSoMoN, ping
[17:10] <oSoMoN> om26er: pong
[17:10] <om26er> oSoMoN, what was it about in #phablet ? I mean no one even knew the bug number ?
[17:10] <oSoMoN> om26er: looks like there is no bug report, there should be one but I can’t find it
[17:10] <om26er> oSoMoN, so probably we cannot be blamed ;)
[17:11] <oSoMoN> no indeed
[17:32] <nik90> m-b-o: hey the new flip animation looks cool! Nice one!
[17:38] <m-b-o> nik90: yes, neokore did some really nice work
[17:39] <m-b-o> nik90, perhaps the visual design will land this week, so more to come :)
[17:39] <neokore> thank you nik90 m-b-o
[17:39] <nik90> m-b-o: oh wow..looking forward to them
[17:39] <nik90> neokore: nice work :)
[19:20] <iBelieve> nik90, ping
[19:27] <boiko> seb128: is the fix for libgsettings-qt-dev already merged? (if CI is failing, autolanding is going to fail too for the sound settings MR)
[19:28] <seb128> boiko, yes, that landed on friday
[19:29] <boiko> seb128: ah nice, let me trigger CI again then, thanks
[19:29] <seb128> boiko, thanks ;-)
[19:40] <n00b> How do I run just the ubuntu touch os in the sdk
[19:40] <n00b> ?
[19:41] <Guest63986> How do I run just the ubuntu touch os in the sdk?
[20:08] <gatox> hi, i have a question regarding the u1db-qt plugin.... y want to create a db for my app... but i can't use the: "~/.config/db" notation in path.... which would be the proper place to create the db?? i assuming that i don't have write permissions where my app was installed
[21:14] <Davideddu> Is it allowed to use a different library for a Showdown application? I want to write my app in Python and Kivy, which is very good for mobile/touchscreen apps.


[02:57] <RikMills> mmikowski: debian are srating the packaging for it I think
[02:57] <RikMills> *stsrting
[02:57] <RikMills> *starting
[02:57] <RikMills> grr
[13:54] <BluesKaj> Hi all
[20:31] <mmikowski> thanks RikMills.  Looks like a winner. Any chance to backport to 22.04?
[20:31] <mmikowski> If so, we could certainly help test.
[20:32] <RikMills> mmikowski: yeah, could be possible if the debian acceptance goes ahead
[20:32] <mmikowski> thanks


[12:01] <thingy> klerfayt: can you try logging as a different(possibly newly created) user and check if its still empty
[12:02] <Linux_Galore> klerfayt: it shouldnt be empty
[12:02] <joe3k> phlegyas_: this could be now more of help http://alioth.debian.org/projects/libpst/, but it's only in beta
[12:02] <Linux_Galore> klerfayt: select a country
[12:03] <PsiKloPx> anyone have any experience with NO_PUBKEY errors in update and synaptic package manager?
[12:05] <Linux_Galore> PsiKloPx: means you need to download one
[12:05] <joe3k> thingy: well nothing "new" in that thread in comparison with the "writing udev rules"
[12:05] <Linux_Galore> PsiKloPx: and set it up
[12:05] <Linux_Galore> PsiKloPx: for the repository you have added
[12:06] <thingy> joe3k: ah so you think the rule is fine but its not being enforced?
[12:06] <fdoving> joe3k: 60-symlinks is also a good reference. that's other symlinking stuff.
[12:06] <joe3k> thingy: if i mess the rule, udevtest complains
[12:07] <joe3k> thingy: and if i write it correctly it just seems to be ignored
[12:08] <joe3k> i gotta be missing something here
[12:08] <Linux_Galore> PsiKloPx: usually its a two stage thing, good example is adding the new amarok repository ( http://kubuntu.org/announcements/amarok-1.4.4.php ) as you can see there is two steps to add a key noted
[12:08] <thingy> joe3k: can i look at the rules file? pastebin it?
[12:09] <thingy> joe3k: i have no experience in it..but just wanna see it
[12:09] <klerfayt> Linux_Galore: ok I created a new user
[12:09] <joe3k> thingy: hmm ok what is pastebin :)
[12:10] <joe3k> thingy: slow paste or what?
[12:10] <thingy> joe3k: hmm i thought the channel topic had a pastebin url...just checking
[12:10] <PsiKloPx> LG: Thanx!  That took care of it!  I just hadda find the right key.
[12:10] <fdoving> joe3k: http://paste.ubuntu-nl.org
[12:11] <thingy> joe3k: you can paste large sections of text to a pastebin service like fdoving said
[12:11] <thingy> joe3k: it will give  a url whcih we can then look at
[12:11] <joe3k> ok
[12:11] <joe3k> thnx
[12:11] <Linux_Galore> PsiKloPx: yeah usually the key files are in the root of the repository
[12:12] <joe3k> thingy: http://paste.ubuntu-nl.org/31075/ is the udevinfo output


[14:58] <pitti> hello
[14:59] <cjwatson> I didn't screw up the timezone, did I?  I can never remember whether Google Calendar is an hour off or not
[15:00] <pitti> looks fine to me
[15:00] <kees> \o
[15:00] <mdz> cjwatson: hi
[15:01] <cjwatson> Keybuk: around?
[15:02] <cjwatson> I have been having a frustrating day involving elusive VESA BIOS specifications and repeated reboots, so a meeting is almost a welcome relief :P
[15:02] <cjwatson> ok, we have quorum, Keybuk can join in if/when he notices
[15:02] <cjwatson> #startmeeting
[15:02] <MootBot> Meeting started at 09:02. The chair is cjwatson.
[15:02] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[15:02] <cjwatson> [TOPIC] Action review
[15:02] <MootBot> New Topic:  Action review
[15:02] <Keybuk> cjwatson: I'm here
[15:02] <cjwatson> are there any actions?  I saw none in the minutes from last time
[15:02] <Keybuk> IRC client wasn't bouncing loud enough
[15:02] <cjwatson> Keybuk: ah, hello
[15:03] <Keybuk> cjwatson: my day has been less frustrating
[15:03] <Keybuk> and there was christmas pudding
[15:03] <cjwatson> lucky you ;-)
[15:03] <cjwatson> I'll take it that there are no actions then
[15:03] <cjwatson> [TOPIC] Reorganizing drivers/owners/release managers permissions in Launchpad (Matt Zimmerman)
[15:03] <MootBot> New Topic:  Reorganizing drivers/owners/release managers permissions in Launchpad (Matt Zimmerman)
[15:04] <cjwatson> mdz: you have the floor
[15:04] <mdz> cjwatson: ok
[15:04] <mdz> so it's time to throw the switch
[15:04] <mdz> I want to make sure that we've told folks that this is happening, so that if there are rough edges, they know how to get them fixed
[15:05] <mdz> I've passed the word down within Canonical
[15:05] <mdz> but that's obviously not enough
[15:06] <mdz> nothing should actually change in practice
[15:06] <mdz> it's just cleaning up the disorganization in LP
[15:06] <cjwatson> agreed; can we use ubuntu-release for the "release manager" role?
[15:07] <mdz> that sounds appropriate; is that not already what's in the bug report?
[15:07] <pitti> if we can't, there woudl still be something wrong in LP
[15:07] <mdz> [link] https://bugs.launchpad.net/bugs/174375
[15:07] <MootBot> LINK received:  https://bugs.launchpad.net/bugs/174375
[15:07] <mdz> https://bugs.launchpad.net/launchpad-registry/+bug/174375/comments/17
[15:07] <cjwatson> mdz: you said "Create a new team to fill the 'release manager' role, and populate it appropriately (if we don't already have one)"
[15:07] <mdz> [link] https://bugs.launchpad.net/launchpad-registry/+bug/174375/comments/17
[15:07] <MootBot> LINK received:  https://bugs.launchpad.net/launchpad-registry/+bug/174375/comments/17
[15:07] <cjwatson> so I was just filling that in
[15:07] <mdz> cjwatson: right, if ubuntu-release is the right set of people for those permissions, then we just use that
[15:08] <mdz> if there should be some extra people in there for whatever reason, we should create a new team and put ubuntu-release into it
[15:08] <cjwatson> well, ubuntu-release is kind of informational/social, and I don't think it currently occupies any explicit slots in LP
[15:08] <mdz> oh
[15:09] <cjwatson> so if we need to extend that team we can just extend it, IMO
[15:09] <mdz> the other question is what to do with the 'maintainer' slot for Ubuntu
[15:09] <mdz> that's the one which can do things like administer mirrors
[15:09] <cjwatson> given the description in https://bugs.launchpad.net/launchpad-registry/+bug/174375/comments/18, I think it would be appropriate for that to be techboard
[15:09] <mdz> and announcements
[15:10] <mdz> and AdminSpecification and EditSpecificationSubscription which sound like they should be ubuntu-drivers
[15:10] <pitti> hm, u-release actually sounds more appropriate for this to me
[15:10] <cjwatson> hm, well, announcements aren't all techboard
[15:10] <cjwatson> yeah, I agree with pitti on reflection
[15:10] <pitti> for both mirroring and annoucnements
[15:10] <mdz> I think blueprint stuff should -> ubuntu-drivers
[15:10] <pitti> ^ +1
[15:10] <mdz> and announcements -> release manager
[15:10] <pitti> that's tech leads, team managers, track leads, etc.
[15:10] <pitti> the blueprint-fiddling folks
[15:10] <cjwatson> it might also make sense to add techboard to ubuntu-release
[15:11] <mdz> the more I think about it the less ready I feel...
[15:11] <pitti> out of interest, where in LP does one assign the ubuntu-archive team?
[15:11] <pitti> is that hardcoded?
[15:11] <mdz> somebody needs to make another pass over this and write it down in a comprehensible form
[15:11] <mdz> maintainer can do this, release series manager can do that, drivers can do this
[15:11] <cjwatson> pitti: ubuntu-archive has queueadmin privileges on components
[15:12] <cjwatson> you can see that with lp:ubuntu-archive-tools edit_acl.py
[15:12] <pitti> cjwatson: ah, thanks
[15:12] <pitti> mdz: do you still see something where we disagree?
[15:12] <mdz> pitti: who do you think should be the 'maintainer' of ubuntu?
[15:12] <pitti> mdz: ubuntu-release
[15:13] <Keybuk> ubuntu-release seems obvious
[15:13] <pitti> mdz: that's for announcements and mirrors, right?
[15:13] <mdz> pitti: and AdminSpecification and EditSpecificationSubscription  and the other things in https://bugs.launchpad.net/launchpad-registry/+bug/174375/comments/18
[15:13] <cjwatson> -release is the team most naturally involved with that day-to-day; I agree with mdz that the specification stuff there should be moved to drivers
[15:13] <mdz> so apparently people who need to be able to admin blueprints need to go in there
[15:13] <pitti> mdz: those would be ubuntu-drivers IMHO
[15:13] <mdz> pitti: they are currently inseparable
[15:14] <Keybuk> isn't the only admin being the targetting to releases?
[15:14] <pitti> https://launchpad.net/ubuntu has a separate "mirror admins", though
[15:14] <mdz> how about this
[15:14] <pitti> which already seems to be set correctly
[15:14] <mdz> we set it up so that there is a team for each slot
[15:14] <cjwatson> how about we create an ubuntu-maintainer team, which has ubuntu-release and ubuntu-drivers in it
[15:14] <mdz> ubuntu-drivers, ubuntu-maintainers, ubuntu-release-managers
[15:14] <cjwatson> ... is this GMTA?
[15:14] <mdz> write down in the description of each team what it can actually do
[15:14] <mdz> so that it's self-documenting
[15:15] <pitti> mdz: blueprints and announcements are inseparable? wasn't this the very thing that this bug was all about?
[15:15] <cjwatson> pitti: it was more about separating blueprint admin and bug supervision
[15:15] <mdz> pitti: if so, it's not fixed, according to comment #17
[15:15] <mdz> though bdmurray said he thought it was done
[15:16] <mdz> we just passed the 3-year anniversary for this bug *sigh*
[15:16] <mdz> I'd like to withdraw the agenda item until I can work on it some more
[15:16] <mdz> unless someone wants to take it over from me
[15:16] <cjwatson> your suggestion of writing things in the description of each team sounds good to me
[15:17] <mdz> yeah, then all we need to do is get LP fixed...again
[15:17] <cjwatson> ubuntu-maintainers can be a temporary team until the last bits of separation get fixed
[15:17] <cjwatson> and it should be less damaging than the ubuntu-drivers conflation, and we'll actually more or less understand what it's for
[15:17] <mdz> ok, I'll propose that as the first phase then
[15:18] <cjwatson> except perhaps a better name than ubuntu-maintainers, since maintainer == developer for many people
[15:18] <cjwatson> ubuntu-owner
[15:18] <pitti> that might stir some emotional response
[15:18] <mdz> I chose that because the Launchpad page says 'maintainer'
[15:18] <mdz> but we could ask for that to be changed
[15:18] <Keybuk> ubuntu-leads
[15:19] <cjwatson> ubuntu-release-plus-drivers
[15:19] <cjwatson> since that's what it is. :)
[15:20] <pitti> and it's ugly enough to point out that it's a temporary team
[15:20] <mdz> I'll draft an email to t-b and launchpad-dev and turn the crank on this again
[15:20] <pitti> cjwatson: +1 :)
[15:20]  * kees nods
[15:22] <cjwatson> ok, are we done with this item for now then?
[15:22] <mdz> yes
[15:23] <cjwatson> [TOPIC] Appoint Ubuntu Launchpad stake holder
[15:23] <MootBot> New Topic:  Appoint Ubuntu Launchpad stake holder
[15:23] <mdz> there's no name next to this one?
[15:23] <cjwatson> persia
[15:23] <mdz> looks like it was pitti
[15:23] <pitti> it was sent to the ML
[15:23] <cjwatson> persia sent the mail to the list
[15:23] <pitti> and we forgot about it last time
[15:23] <cjwatson> I would like to clarify whether this is in addition to Marjo, or replacing him
[15:24] <pitti> I understood "in addition" when I was talking to him
[15:24] <cjwatson> I spoke to persia about this in Orlando, and we reached agreement then ... but I've forgotten what that agreement was
[15:24] <cjwatson> the few stray neurons I have that remember that conversation think that this was essentially somebody to represent Ubuntu-as-project separately from the Ubuntu platform team
[15:25] <pitti> I proposed Bryce, as he has written tons of scripts for Launchpad, and is also doing massive regular bug triage, and also has experience on LP hacking
[15:25] <mdz> this is for Ubuntu, as opposed to Ubuntu Platform (part of Canonical)
[15:25] <cjwatson> in that case my memory is accurate.  OK.
[15:25] <kees> is it ours to appoint?
[15:25] <kees> should this be TB or CC?
[15:26] <cjwatson> how close an interaction does Bryce have with the wider Ubuntu community, beyond X?
[15:26] <cjwatson> kees: I certainly think the representative should come from the development community; it's not strictly a technical matter but the TB may be better placed to judge
[15:26] <Keybuk> it was definitely persia
[15:27] <pitti> he hangs out in #ubuntu-desktop and discusses integration matters there as well
[15:27] <cjwatson> Keybuk: since you're one of the people persia suggested, do you have any thoughts on this you'd like to share?
[15:27] <Keybuk> I think I got shanghaid on the basis I'm going to shortly be the only TB member who won't be working at Canonical
[15:28] <Keybuk> but I wasn't really clear on why that was important
[15:28] <Keybuk> or indeed, why we needed a new and different stakeholder to LP than the one we already have
[15:28] <pitti> I think the point was to have a strong voice who doesn't have a commercial bias/pressure
[15:28] <Keybuk> I'd vaugely thought that we just needed a bigger stake to stab them with
[15:28] <Keybuk> pitti: everyone has bias or pressure of some sort
[15:29] <cjwatson> my understanding was that the Launchpad stakeholder meetings tend to be somewhat commercial-stake-driven, and that an explicit project representative would find it easier to stand apart from that
[15:29] <pitti> right, they just need to average themselves out
[15:29] <cjwatson> Launchpad certainly used to solicit input from the platform team and the Ubuntu community somewhat separately
[15:30] <kees> is this stake-holder position something the LP team has agreed to having show up? (also, AIUI, such a person would need to sign an NDA due to some of the topics being discussed at the meeting)
[15:31] <cjwatson> https://lists.ubuntu.com/archives/technical-board/2010-November/000571.html says that Francis agreed that this would be appropriate
[15:31] <kees> okay
[15:32] <cjwatson> as overall Launchpad manager I assume that he's authoritative on this :)
[15:32] <cjwatson> do we need to reach agreement on whether this is an appropriate thing to do at all?
[15:33] <mdz> I support it
[15:33] <kees> I think it's reasonable
[15:33] <cjwatson> my view is that I can't easily say whether it will definitely be useful, but since Marjo has asked us to try and Francis is receptive to it it seems worth a go
[15:34] <cjwatson> I would like to hear from each of the suggested candidates before trying to select someone, though.  Does anyone feel that we should issue a wider call for nominations?
[15:35] <kees> seems only fair -- if someone in ubuntu really wants to jump on this, we should give them a chance.
[15:35] <pitti> my gut feeling is that three candidates are enough, and we already confirmed their willingness to act for this role; and as there are no particular hard privileges assigned to this, I don't think we really need a democratic vote of teh community here
[15:35] <pitti> (not that I'd veto one, I just feel it's a bit overkill)
[15:35] <Keybuk> well, except I'm not really sure I'm the right person
[15:35] <kees> I'm fine with that too
[15:35] <Keybuk> yet I ended up on the list ;)
[15:35] <Keybuk> so I'm not so sure about confirmed their willingness
[15:35] <Keybuk> :p
[15:36] <pitti> Keybuk: hmkay -- that's what Emmet wrote, anyway
[15:36] <cjwatson> sounds like a bit of chinese-whispers going on
[15:37] <Keybuk> (not that I'm saying I'd be bad at it, I just suspect ENOTIME for the next several months)
[15:37] <cjwatson> this sounds to me as though it would be worth a quick call for anyone else who's interested, and in parallel ask the existing candidates to send in a short note to technical-board@ describing their plans?
[15:38] <cjwatson> Keybuk: would you like to explicitly excuse yourself, then?
[15:38] <Keybuk> cjwatson: yes, for now
[15:38] <cjwatson> OK
[15:38] <Keybuk> if the position was regularly chosen, I may well put myself up for it in future, for example
[15:38] <cjwatson> fair enough
[15:39] <cjwatson> so shall I do the above as part of writing up minutes for this meeting, then?
[15:39] <mdz> cjwatson: fine by me
[15:39] <mdz> though we shouldn't wait too long
[15:39] <mdz> persia already canvassed and got volunteers
[15:39] <mdz> so we don't really need any more
[15:40] <mdz> but if someone is dying for the job I don't mind them coming forward
[15:40] <cjwatson> I agree, I was thinking no longer than two weeks
[15:40] <kees> sure. could even go 1 week, just to avoid holidays, but yeah, 2 is fine.
[15:41] <cjwatson> one week is OK by me
[15:41] <cjwatson> [TOPIC] Schedule and chair (Matt Zimmerman)
[15:41] <MootBot> New Topic:  Schedule and chair (Matt Zimmerman)
[15:41] <cjwatson> I shall not be here on the 28th
[15:41] <mdz> just some points of order
[15:42] <mdz> I'll just paste from the wiki
[15:42] <mdz> Next meeting is scheduled for 28 December
[15:42] <mdz> Will we have quorum, or should we skip it?
[15:42] <mdz> Mark is unavailable to chair 11 January
[15:42] <mdz> will anyone else be absent the 28th?
[15:42] <pitti> I won't be online
[15:42] <pitti> I'm in a train on that day
[15:43] <cjwatson> will Mark be around on the 28th?
[15:44] <mdz> cjwatson: I don't know
[15:44] <mdz> I've negotiated with clan that she will tell me when he's unavailable for TB
[15:44] <kees> I won't be here the 28th
[15:44] <mdz> so we don't end up without a chair
[15:44] <cjwatson> sounds to me as though we'll be at most barely quorate on the 28th, and probably inquorate
[15:44] <Keybuk> I'm unlikely to be available that day
[15:44] <mdz> so no pitti, no cjwatson, no kees, no keybuk
[15:44] <mdz> no quorum
[15:45] <cjwatson> ok, that's a definite no.  next meeting on the 11th, then?
[15:45] <pitti> sounds like skipping then
[15:45] <mdz> so we just need a chair for the 11th
[15:45] <cjwatson> next in alpha sequence is kees
[15:46] <kees> \o/
[15:46] <cjwatson> I'll take that as a yes :)
[15:46] <kees> :)
[15:46] <cjwatson> [TOPIC] Scan the mailing list archive for anything we missed
[15:46] <MootBot> New Topic:  Scan the mailing list archive for anything we missed
[15:46] <cjwatson> there are a few dangling items regarding SRUs and the like
[15:46] <kees> 11th is the rally.
[15:46] <cjwatson> are any of them currently blocked on TB approval?
[15:46] <cjwatson> kees: I think we can probably manage, maybe with a time adjustment
[15:47] <cjwatson> we have:
[15:47] <cjwatson>   bzr (https://lists.ubuntu.com/archives/technical-board/2010-December/000596.html
[15:47] <cjwatson> )
[15:47] <cjwatson>   xubuntu-docs (https://lists.ubuntu.com/archives/technical-board/2010-December/000599.html)
[15:47] <cjwatson>   linux (https://lists.ubuntu.com/archives/technical-board/2010-December/000597.html)
[15:49] <cjwatson> pitti: do you know which of those if any are outstanding?
[15:49] <pitti> xubuntu and bzr are missing a few more votes
[15:49] <pitti> which could just be sent to the ML (should be straightforward), then I'll add them to the exception page
[15:49] <pitti> the kernel process has by and large been worked out now
[15:49] <pitti> there was some misunderstanding at first
[15:50] <pitti> but now it's by and large what we had before, just that we now copy from teh PPA instead of accepting from -proposed
[15:50] <pitti> although there are still some technical difficulties, it didn't change on a policy level
[15:51] <cjwatson> I will follow up to xubuntu-docs and bzr then
[15:51] <cjwatson> ok
[15:51] <cjwatson> Check up on community bugs: no change from last time
[15:52] <cjwatson> [TOPIC] AOB
[15:52] <MootBot> New Topic:  AOB
[15:52] <mdz> I'd like to make a suggestion
[15:52] <mdz> that we ask for AOB at the start of the meeting, rather than at the end
[15:52] <mdz> so that if someone turns up with an issue, we can get it on the agenda and leave time for it if necessary
[15:52] <Keybuk> you have OB, don't you? ;-)
[15:52] <mdz> just that
[15:53] <Keybuk> doesn't seem unreasonable
[15:53] <cjwatson> I'm fine with that, I'll adjust the agenda
[15:53] <kees> yeah
[15:53] <Keybuk> should be a call for additional points or something
[15:53] <mdz> so the first agenda item becomes "make sure the agenda is complete"
[15:53] <mdz> I've started doing this in my meetings and it's more effective
[15:54] <cjwatson> sounds like that's a wrap, then
[15:55] <cjwatson> #endmeeting
[15:55] <MootBot> Meeting finished at 09:54.
[15:55] <cjwatson> oh, mdz: thanks for organising that brainstorm review, it seems to have been a success
[15:55] <mdz> cjwatson: indeed, the thanks goes to the folks who wrote the responses
[15:57] <pitti> thanks everyone
[15:57] <kees> thanks!
[15:58] <hggdh> ~ô~
[15:59] <hallyn_> \0
[15:59] <Daviey>  /o\
[16:00] <jjohansen> \o
[16:00] <JamesPage> o/
[16:00] <smoser> ok. weell, its that time of day again
[16:00] <RoAkSoAx> o/
[16:00] <SpamapS> \O/
[16:00] <smoser> err... week.
[16:00] <smoser> https://wiki.ubuntu.com/ServerTeam/Meeting
[16:01] <SpamapS> smoser: take us out Mr. Sulu
[16:01] <smoser> how do i "start meeting " ?
[16:02] <SpamapS> you say <pound>startmeeting
[16:02] <SpamapS> or for some.. <hash>startmeeting
[16:02] <zul> mmmm...hash
[16:02] <smoser> #startmeeting
[16:02] <MootBot> Meeting started at 10:02. The chair is smoser.
[16:02] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:02] <robbiew> o/
[16:02]  * robbiew will lurk today....call in 30min
[16:02] <ScottK> \o
[16:02] <smoser> hm.. seems my clever trick to get someone else to scribe has failed.
[16:03] <JamesPage> smoser: nice try :-)
[16:03] <smoser> fyi, https://wiki.ubuntu.com/ScribesTeam/MootBot has such info
[16:03] <smoser> [TOPIC] Review ACTION points from previous meeting
[16:03] <MootBot> New Topic:  Review ACTION points from previous meeting
[16:03] <smoser>  * ALL: please check the SRU tracker for 'needs-verification' bugs  [http://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html]
[16:04] <SpamapS> Imre Gergely has been *heroic* in verifying server SRU's
[16:04] <smoser> it looks like i need to take a look at that.
[16:04] <smoser> and i will.
[16:04] <smoser> thanks to Imre
[16:05] <smoser>  * ACTION: robbiew to review ServerTeam wiki
[16:05] <smoser> robbiew, ?
[16:05] <robbiew> yeah..yeah...slowly but surely
[16:05] <robbiew> keep it
[16:05] <robbiew> damn it!
[16:05] <smoser> [ACTION]: robbiew to review ServerTeam wiki [carried over]
[16:05] <MootBot> ACTION received: : robbiew to review ServerTeam wiki [carried over]
[16:05] <smoser>  * ACTION: Kernel team to follow up on bug 661294
[16:06] <smoser> jjohansen, smb ?
[16:06] <smb> I added some potential debuuging steps today
[16:06] <smb> Though that is the one I am not able to reproduce
[16:07] <SpamapS> smb: there are 2 users who are reproducing it consistently, right?
[16:07] <smb> I think yes. A third one has opened another bug as he thinks it might be a too different setup
[16:08] <smb> bug 688437
[16:08] <Daviey> smb: Would it help if we try and reproduce it?
[16:08] <smb> Daviey, Sure, it helps to know what exactly triggers it
[16:09]  * Daviey will try this.
[16:09] <smb> The second bug seems to have some vmware involved. (at least on a quick look)
[16:09] <smoser> Daviey, you want an action ?
[16:09] <Daviey> smoser: Yeah... i have rouble with committment without an action item.
[16:09] <smoser> [ACTION] Daviey to try to reproduce bug 661294
[16:09] <MootBot> ACTION received:  Daviey to try to reproduce bug 661294
[16:10] <smoser> hope that helps your rouble.
[16:10] <Daviey> smoser: Yeah, that has changed my life for the better... thanks :)
[16:10] <smoser> It sounds to me like smb has a handle on it.  if anyone else can add reproduce, that would be nice.
[16:11] <smoser>  * ACTION: JamesPage to arrange URL for Hudson CI Server
[16:11] <Daviey> ^ done
[16:11] <JamesPage> Done: http://hudson.qa.ubuntu-uk.org:8080
[16:11] <smoser> JamesPage, ^
[16:11] <JamesPage> Cheers Daviey!
[16:11] <smoser> gracias.
[16:11] <Daviey> hah
[16:11] <hggdh> FWIW, I have seen other bugs with a hang on remote FS, and a kernel trace involving sys_sync
[16:12] <SpamapS> JamesPage: any reason that has to run on 8080 ?
[16:12] <JamesPage> SpamapS: only my lack of time to make it run on port 80 - will do by the end of the week
[16:12] <SpamapS> JamesPage: btw, that is amazing. ;)
[16:13] <hggdh> SpamapS: not really, but now we have the firewall set, and I would rather not mess with it
[16:13] <Daviey> to be fair, the subdomain only went live about 30 mins ago... give JamesPage a break :)
[16:13] <hggdh> JamesPage: mind the firewall...
[16:13] <JamesPage> hggdh - will do
[16:13] <smoser>  * ACTION: spamaps to talk to his friend to try and get more info on Bug 684304
[16:13] <smb> btw it is not only cciss that has problems
[16:14] <hggdh> just tried the options given by smb, but no luck (and a kernel trace)
[16:14] <SpamapS> smb: oh?
[16:14] <smb> hggdh, yep just saw it
[16:14] <smb> sadly no luck
[16:14] <SpamapS> I just spoke with him yesterday and he has the hardware in the rack but not hooked up to the network yet.. should be getting a DL360 G5 with ILO support to play with.
[16:14] <smb> SpamapS, Yes, there is something odd going on here, all of the pcie root ports have msi not enabled and no drivers bound
[16:15] <SpamapS> so carry that one forward, but maybe carry it forward as "spamaps to confirm bug #684304 on borrowed DL360 G5"
[16:15] <hggdh> smb: you are aware that you can play with the machines, right?
[16:15] <smoser> [ACTION] spamaps to confirm bug #684304 on borrowed DL360 G5
[16:15] <MootBot> ACTION received:  spamaps to confirm bug #684304 on borrowed DL360 G5
[16:15] <smb> hggdh, No, you probably need to make me aware offline
[16:16] <hggdh> ack
[16:17] <smoser> [ACTION] hggdh to tell smb about how to get at machines
[16:17] <MootBot> ACTION received:  hggdh to tell smb about how to get at machines
[16:17] <smoser> next is
[16:17] <smoser>  * ACTION: zul to request feedback on the install-service blueprint to the mailing list
[16:17] <zul> not done
[16:18] <Daviey> smoser: Is that a topic shift, or a warning what is the next stop?
[16:18] <smoser> topic shift.
[16:18] <smoser> [ACTION] zul to request feedback on the install-service blueprint to the mailing list (carry over)
[16:18] <MootBot> ACTION received:  zul to request feedback on the install-service blueprint to the mailing list (carry over)
[16:18] <smoser> moving on
[16:18] <smoser> [TOPIC] Natty Development
[16:18] <MootBot> New Topic:  Natty Development
[16:18] <smoser> robbiew, are you leading this topic ?
[16:19] <Daviey> I have one thing relevant under that topic....
[16:19] <Daviey> Did everyone see the FTBFS email?
[16:19] <JamesPage> Yep
[16:19] <kirkland> Daviey: yup
[16:19] <robbiew> sure...I'll start with I need someone to represent us in the weekly status meeting
[16:19] <zul> ill do it
[16:20] <Daviey> robbiew: rota? :)
[16:20] <SpamapS> Daviey: indeed, looks like there are a few still left.
[16:20] <kirkland> Daviey: one question about that ... what's difference between that and Lucas Nussbaum's?  that yours focuses on server packages, perhaps?
[16:20] <Daviey> kirkland: mine is JUST the server seed.
[16:20] <kirkland> Daviey: okay
[16:20] <robbiew> zul: thnx
[16:21] <kirkland> robbiew: what does that entail?
[16:21] <smoser> so everyone should take a look at that and see if they can't knock off a few ftbfs.
[16:21] <robbiew> Daviey: as long as the rotation doesn't involve me...I'm fine with it
[16:21] <Daviey> robbiew: heh.
[16:21] <robbiew> kirkland: means keeping https://wiki.ubuntu.com/ServerTeam/ReleaseStatus/Natty up-to-date
[16:21] <Daviey> robbiew: assume this is the release meeting?
[16:21] <Daviey> ah yes.
[16:21] <robbiew> mostly just tracking the bug stuff
[16:21] <kirkland> robbiew: ah
[16:21] <robbiew> https://wiki.ubuntu.com/ServerTeam/ReleaseStatus/Natty/Detail is generated from a script
[16:21] <kirkland> robbiew: okay cool;  zul -- it's all yours :-P
[16:21] <robbiew> and pulls into https://wiki.ubuntu.com/ServerTeam/ReleaseStatus/Natty
[16:22] <robbiew> lol
[16:22] <Daviey> zul: If you want a hand, lemme know. :)
[16:22] <ScottK> Daviey: Server seed or server package set?
[16:23] <SpamapS> robbiew: https://wiki.ubuntu.com/ServerTeam/ReleaseStatus/Natty/Detail doesn't exist
[16:23] <zul> Daviey: ack
[16:23] <smoser> anything else here ?
[16:23] <robbiew> SpamapS: add an "S"
[16:23] <Daviey> ScottK: Seed
[16:24] <kirkland> zul: (yeah, i'm happy to back you up too)
[16:24] <ScottK> OK.  I thought there were Universe packages in there, but OK.
[16:24] <robbiew> SpamapS: https://wiki.ubuntu.com/ServerTeam/ReleaseStatus/NattyDetail
[16:25] <SpamapS> ah
[16:25]  * kim0 knocked off 2 ftbfss
[16:25] <smoser> anything else here ?
[16:25] <smoser> hggdh, you're on
[16:25] <smoser> [TOPIC] Weekly Updates & Questions for the QA Team (hggdh)
[16:25] <MootBot> New Topic:  Weekly Updates & Questions for the QA Team (hggdh)
[16:25] <hggdh> I am still dead in the water re. testing UEC
[16:26] <robbiew> hggdh: is this to do with that kernel bug
[16:26] <hggdh> I have requested two machines to be set local, but right now I simply cannot test any
[16:26] <hggdh> robbiew: yes
[16:26] <robbiew> smb is supposed to be looking at it
[16:26] <hggdh> the only machines I currently have access to -- the UEC test rig have not been working on Nattty
[16:27] <robbiew> was on patch pilot yesterday
[16:27] <hggdh> this is blocking UEC testing
[16:27] <smb> right, robbiew pinged me yesterday and I checked what I could about it
[16:28] <hggdh> apart from that... JamesPage, myself, and others have been adding tests under Hudson. Contributions are welcome (and machines to run them under)
[16:28] <smb> So atm we don't have anything new
[16:28] <smoser> hggdh, i dont think it will affect you (my test was that it did not affect lucid UEC) but bug 688773 affects euca2ools on natty with python2.7
[16:28] <smb> But maybe when I know how to play remotely
[16:28] <hggdh> smoser: I will add it in to test when I can
[16:29] <hggdh> thank you
[16:29] <smoser> hggdh, well, if it fails, it will fail all over the place, as you wont be able to upload images :)
[16:29] <smoser> anything else, hggdh ?
[16:29] <hggdh> heh
[16:29] <hggdh> no, I am done, smoser
[16:30] <smoser> [TOPIC] Weekly Updates & Questions for the Kernel Team (smb)
[16:30] <MootBot> New Topic:  Weekly Updates & Questions for the Kernel Team (smb)
[16:30] <smb> There are more? :)
[16:30]  * smoser claps for smb and bug 651370
[16:31] <smoser> and i'm under the impression that bug 667796 is soon to be fixed
[16:31] <smb> Thanks, though I think that was still jjohansen at work
[16:31] <smb> smoser, right that one is simply the option
[16:31] <smoser> and also that jjohansen is epxecting to push bug 614853 into lucid (with the wonderful patch attached there)
[16:31] <smb> its in the next proposed kernel
[16:32] <smb> I hope so, though we would need to ask him
[16:32] <smoser> all in all, i'm quite happy. i expect to have refreshed maverick images as soon as that one gets into maverick-proposed
[16:32] <smb> I had been tied up severely by a support escalation and another nfs bug
[16:33] <jjohansen> smb: no its not yet, and I believe its likely causing another bug
[16:33] <smoser> and hiping for lucid update this week, which will include lucid images that can be booted with pv-grub
[16:33] <smoser> s/hiping/hoping/
[16:33] <smb> (or to say which was another nfs bug)
[16:33] <smoser> that will make jjohansen and smb's life easier, as pv-grub makes kernel testing much easier.
[16:33] <jjohansen> \o/
[16:33] <SpamapS> I haven't tried natty on ec2 yet.. is it working?
[16:33] <smoser> [ACTION] smoser to write a blog entry on how to use grub 'fallback' with our images.
[16:33] <MootBot> ACTION received:  smoser to write a blog entry on how to use grub 'fallback' with our images.
[16:33] <smb> except micro it should by now
[16:34] <smb> SpamapS, ^
[16:34] <smoser> SpamapS, natty boots on non-t1.micro
[16:34] <smoser> and... possibly (if ami-2470864d works) we have an hvm image now (cluster compute)
[16:35] <smoser> smb, jjohansen the other bug that I see getting hit in maverick is bug 613273
[16:35] <SpamapS> ack
[16:35] <smoser> although my "in system call fastpath" description is probably competely bogus
[16:35] <smb> well it only means in a system call
[16:36] <smoser> right. not generally helpful.
[16:36] <smoser> so thats all from me...
[16:36] <smb> I will update the description when I know more
[16:37] <smb> There was one I was looking at today which had mostly screenshots as jpg which is hard to reassemble in mind
[16:37] <smoser> smb, i can provide more console logs (i think) if necessary from https://code.launchpad.net/~ubuntu-on-ec2/ubuntu-on-ec2/ec2-test-results
[16:37] <smoser> anyone else have anything for kernel team ?
[16:38] <smoser> [TOPIC] Weekly Updates & Questions for the Documentation Team (sommer)
[16:38] <MootBot> New Topic:  Weekly Updates & Questions for the Documentation Team (sommer)
[16:39] <smoser> mr sommer ?
[16:39] <sommer> hey all, don't have anything new this week
[16:39] <sommer> should have time to works on docs soon
[16:39] <sommer> :-)
[16:39] <smoser> any one have questions for the great sommer ?
[16:40] <SpamapS> sommer: wb!
[16:40] <smoser> if not, then we move onto kim0
[16:40] <smoser> [TOPIC] Weekly Updates & Questions for the Ubuntu Community Team (kim0)
[16:40] <MootBot> New Topic:  Weekly Updates & Questions for the Ubuntu Community Team (kim0)
[16:40] <kim0> Hey everyone
[16:40] <kim0> Daviey has agreed himself to be bugged about identifying venues for community contributions to cloud related projects
[16:40] <kim0> Such venues will be featured on the cloud portal, and regularly advertised on our communication channels (blogs, twitter, FB, IRC events ...etc), with the aim of hopefully attracting more contributors
[16:40] <kim0> I think it shouldn't be overly technical, however still fairly challenging
[16:40] <SpamapS> kim0: have you linked to harvest from the cloud portal yet btw?
[16:41] <SpamapS> kim0: last time I looked, harvest was pretty low on server specific stuff to do
[16:41] <kim0> I think I need a good way to link cloud stuff to harvest first
[16:41] <kim0> the portal is only cloud btw ..
[16:41] <SpamapS> the cloud is the server is the cloud ;)
[16:42] <kim0> not sure .. cloud seems to be part of server for me
[16:42] <kim0> anyway, @everyone, if you think something cloudy you're working on, is a good candidate for community contributions, please send suggestions to me<EMAIL_ADDRESS>[16:42] <zul> well....a cloud would be nice if you have something to run in it
[16:42]  * kim0 hugs Daviey for all the help
[16:42] <smoser> for anyone not aware, kim0 is making some really nice blog posts that can be seen there on the http://cloud.ubuntu.com or at http://foss-boss.blogspot.com/
[16:42] <Daviey> kim0: Ubuntu One is personal cloud... covering that? :)
[16:42] <kim0> Daviey: I guess it would count :)
[16:43] <kim0> smoser: and screencasts
[16:43] <kim0> which brings up the other topic
[16:43] <smoser> i really liked http://foss-boss.blogspot.com/2010/11/ubuntu-server-in-ec2-cloud-easy.html
[16:43] <kim0> any suggestions on "trainings" or screencasts
[16:43] <smoser> kim0, one thing... you should be syndicated on "cloud planet" if you are not already
[16:43] <kim0> you guys think would be useful
[16:43] <kim0> please flood me
[16:43] <SpamapS> There is no 'cloud' section of harvest, and the ubuntu-server section has *one* package.. erlang
[16:44] <kim0> smoser: where is that ? isn't that the one on the portal ?
[16:44] <smoser> hm.. i guess you handled it.
[16:44] <kim0> smoser: yep ..
[16:44] <smoser> nijaba, used to have it.
[16:44] <smoser> ok. good.
[16:44] <kim0> aha yeah .. I'm on that
[16:44] <kim0> SpamapS: I can add a cloud section to harvest
[16:44] <kim0> I'd just need you guys to point at some jobs
[16:44] <kim0> the community can help with
[16:44] <kim0> that's really all for me .. don't forget .. flood me :)
[16:45] <smoser> [TOPIC] Open Discussion
[16:45] <MootBot> New Topic:  Open Discussion
[16:45]  * RoAkSoAx has an announcement to make!
[16:45]  * kim0 makes drum roll
[16:45] <RoAkSoAx> The Cluster Stack is Finally in Main!!
[16:45] <kim0> woohooo
[16:45] <nijaba> \o/
[16:45] <SpamapS> oohhhh snap
[16:45] <Daviey> RoAkSoAx: Awesome!!
[16:45] <RoAkSoAx> Next steps are to enable some missing features, update to latest versions, and continue with the research on HA for UEC
[16:46] <nijaba> RoAkSoAx really rocks
[16:46] <RoAkSoAx> and will announce it via blog post and ML later today
[16:46] <kim0> RoAkSoAx: awesome
[16:46] <Daviey> RoAkSoAx: Does it need better docs?
[16:47] <RoAkSoAx> Daviey: well I wanna get docs into the server guide
[16:47] <RoAkSoAx> that's also what I've planned for this cycle
[16:47] <Daviey> RoAkSoAx -> talk with sommer... :)
[16:47] <smoser> [TOPIC] Announce next meeting date and time
[16:47] <MootBot> New Topic:  Announce next meeting date and time
[16:47] <sommer> I'll help definitely
[16:47] <smoser> next meeting: Tuesday 2010-12-21 at 1600 UTC
[16:48] <Daviey> sommer: \o/
[16:48] <smoser> i'm sure it will be well attended, since lots of people will have more time for such things since they'll be taking vacation.
[16:48] <SpamapS> yeah the community will probably show up in droves. ;)
[16:49] <zul> ill be on vacation :)
[16:49] <JamesPage> me too :-)
[16:49] <Daviey> zul: Great... turn up as a community member :)
[16:49] <zul> Daviey: umm....no :)
[16:49] <kim0> hehe
[16:49] <smoser> #endmeeting
[16:49] <MootBot> Meeting finished at 10:49.
[16:49] <SpamapS> quick, shut it down!
[16:49]  * zul is going to go see tron that day
[16:49] <RoAkSoAx> lol
[16:49] <sommer> yay for tron!
[16:50] <RoAkSoAx> i could have watched it yesterday if I haven;t had to graduate
[16:50] <SpamapS> boo for sark!
[16:50] <SpamapS> RoAkSoAx: congrats!
[16:50] <Daviey> RoAkSoAx: priorities!
[16:50] <RoAkSoAx> thanks ;)
[16:54]  * JFo straggles in
[16:55]  * ara waves
[16:55] <JFo> straggling is very tiring
[16:55] <JFo> ara! :)
[16:59]  * smb \o
[17:00]  * cking \o
[17:00] <JFo> o/
[17:00] <sconklin> \o
[17:00] <bjf> #
[17:00] <bjf> # lets "get 'er done"!
[17:00] <bjf> #
[17:00] <bjf> #startmeeting
[17:00] <MootBot> Meeting started at 11:00. The chair is bjf.
[17:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[17:00] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick
[17:00] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick
[17:00] <bjf> #
[17:00] <bjf> # NOTE: '..' indicates that you are finished with your input.
[17:00] <bjf> #
[17:00] <bjf> [TOPIC] ARM Status (bjf)
[17:00] <MootBot> New Topic:  ARM Status (bjf)
[17:01] <bjf>  * Marvel (mvl-dove)
[17:01] <bjf>    * Nothing new this week.
[17:01] <bjf>  * Texas Instruments (ti-omap)
[17:01] <bjf>    * Bug 633227: Native building crash.
[17:01] <bjf>      * Tested with Linaro 2.6.37 kernel which is close to upstream mainline. Native building still fails even with highmem disabled.
[17:01] <bjf>    * X-loader and U-boot update from TI.
[17:01] <bjf>    * Received 1700+ patch update from TI for 2.6.35 based Natty branch. This has been submitted to the mailing list, applied and pushed.
[17:01] <bjf>  * Freescale i.MX51
[17:01] <bjf>    * Bug 605042: Java crash issue.
[17:01] <bjf>      * Due to a lack of FSL HW in the kernel team this has been difficult to diagnose. However, some testing was done on a Babbage 2.0
[17:01] <bjf>        board but was unable to reproduce the issue.
[17:01] <bjf> ..
[17:01] <tgardner> I uploaded ti-omap4 for natty this AM.
[17:01] <tgardner> It includes a new BSP from TI, over 1700 patches since Maverick.
[17:01] <tgardner> ..
[17:02] <bjf> [TOPIC] Release Metrics (JFo)
[17:02] <MootBot> New Topic:  Release Metrics (JFo)
[17:02] <JFo> Release Meeting Bugs (8 bugs, 14 Blueprints)
[17:02] <JFo> [17:02] <JFo>  * 1 linux kernel bugs (no change)
[17:02] <JFo>  * 0 linux-ti-omap bugs (no change)
[17:02] <JFo>  * 0 linux-meta-ti-omap bug (no change)
[17:02] <JFo> [17:02] <JFo>  * 11 linux kernel bugs (up 2)
[17:02] <JFo>  * 0 linux-ti-omap bugs (no change)
[17:02] <JFo>  * 0 linux-meta-ti-omap bug (no change)
[17:02] <JFo> [17:02] <JFo>  * 6 blueprints (Including HWE Blueprints)
[17:02] <JFo> [17:02] <JFo>  * 54 Linux Bugs (up 2)
[17:02] <JFo> [17:02] <JFo>  * 111 Linux Bugs (no change)
[17:02] <JFo> [17:02] <JFo>  * [[https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on | Bugs with Patches]]
[17:02] <JFo>  * [[http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/ | Breakdown by status]]
[17:02] <JFo> ..
[17:03] <bjf> [TOPIC] Blueprints: Natty Bug Handling (JFo)
[17:03] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-bug-handling
[17:03] <MootBot> New Topic:  Blueprints: Natty Bug Handling (JFo)
[17:03] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-bug-handling
[17:03] <JFo> nothing to report.
[17:03] <JFo> ..
[17:03] <bjf> [TOPIC] Blueprints: Enhancements to the firmware test suite (cking)
[17:03] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-firmware-test-suite-enhancements
[17:03] <MootBot> New Topic:  Blueprints: Enhancements to the firmware test suite (cking)
[17:03] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-firmware-test-suite-enhancements
[17:03] <cking> Changes to fwts (natty development branch):
[17:03] <cking>  * Method test - check for null object returns
[17:03] <cking>  * s4 - check for swap before hibernate
[17:03] <cking> ..
[17:04] <bjf> [TOPIC] Blueprints: Handling of Deviations from Standard Kernels (smb)
[17:04] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-frankenkernel-maintenance
[17:04] <MootBot> New Topic:  Blueprints: Handling of Deviations from Standard Kernels (smb)
[17:04] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-frankenkernel-maintenance
[17:04] <smb> The last piece (script) has been started but users, support and other incidents have a tendency of getting into the path of progress *sigh*. Translation: nothing new
[17:04] <smb> ..
[17:04] <bjf> [TOPIC] Blueprints: Review of the Stable Maintenance Process (sconklin / bjf)
[17:04] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-process-review
[17:04] <MootBot> New Topic:  Blueprints: Review of the Stable Maintenance Process (sconklin / bjf)
[17:04] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-process-review
[17:04] <sconklin> Kernels for both Lucid and Maveric had all associated bugs verified last week.
[17:04] <sconklin> This means that it was not necessary to revert any fixes or re-upload the kernels,
[17:04] <sconklin> as described in the stable cadence process:
[17:04] <sconklin> https://wiki.ubuntu.com/Kernel/StableReleaseCadence
[17:04] <sconklin> This means that the kernels currently in -proposed could immediately enter
[17:04] <sconklin> the Testing phase by the Cert and QA teams.
[17:05] <sconklin> Thanks to everyone who tested their bugs promptly. This is the optimal
[17:05] <sconklin> way to run the new process, with fast testing and no reverts. It's been
[17:05] <sconklin> a little chaotic at times, and I'd like to thank the archive admins, members
[17:05] <sconklin> of the cert team, and everyone else who is helping shepard this new process
[17:05] <sconklin> through the first few cycles.
[17:05] <sconklin> All releases other than Lucid and Maverick (except Hardy) have new packages
[17:05] <sconklin> in -proposed, which contain only security CVE fixes. Hardy is delayed due to
[17:05] <sconklin> a problem we encountered in moving to the new non-virtualized build ppa, and
[17:05] <sconklin> should be built by the end of this week.
[17:05] <sconklin> Testing status for these security-only kernels is unknown. They do not follow
[17:05] <sconklin> the same testing process as the Lucid and Maverick stable kernels.
[17:05] <sconklin> Most members of the kernel team are on holiday until after the new year. We
[17:05] <sconklin> plan to try to upload -proposed kernels to begin a new cycle by Friday, Jan 7th.
[17:05] <sconklin> ..
[17:07] <bjf> [TOPIC] Status: Current -proposed testing by cert. team  (ara)
[17:07] <MootBot> New Topic:  Status: Current -proposed testing by cert. team  (ara)
[17:07] <ara> Hello!
[17:07] <ara> Very little to update at this point.
[17:07] <ara> The certifcation testing has started for Lucid proposed kernel, but we cannot report on results yet.
[17:07] <ara> cr3 and brendand are working hard on this and they should be able to have results for both Maverick and Lucid before the end of the week
[17:07] <ara> ..
[17:07] <JFo> welcome to the meeting ara :)
[17:07] <JFo> .
[17:07] <JFo> ..
[17:07] <ara> JFo, thanks
[17:08] <bjf> [TOPIC] Status: Natty (apw)
[17:08] <MootBot> New Topic:  Status: Natty (apw)
[17:08] <tgardner> The Natty kernel is at 2.6.37-9.22 (rebased against 2.6.37-rc5).  Items of interest include:
[17:08] <tgardner> 1) A number of external drivers have been updated: dm-raid4-5, omnibook, ndiswrapper, and iscsitarget.
[17:08] <tgardner> 2) The module RO/NX patches have been re-instated with bug fixes.
[17:08] <tgardner> 3) 2.6.37-rc6 is imminent and will likely be the last kernel version until after the holidays.
[17:08] <tgardner> 4) New firmware files to support new intel wifi adapters in the 6000 and 6050 family.
[17:08] <tgardner> ..
[17:08] <bjf> [TOPIC] Security & bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper (sconklin / bjf)
[17:08] <MootBot> New Topic:  Security & bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper (sconklin / bjf)
[17:08] <sconklin> | Package                                  | Upd/Sec              | Proposed             |  TiP | Verified |
[17:08] <sconklin> |                                          |                      |                      |      |          |
[17:08] <sconklin> | karmic   linux-ec2                       | 2.6.31-307.22        | 2.6.31-307.23        |    0 |        0 |
[17:08] <sconklin> | ---      linux                           | 2.6.31-22.69         | 2.6.31-22.70         |    0 |        0 |
[17:08] <sconklin> |                                          |                      |                      |      |          |
[17:09] <sconklin> | lucid    linux-ec2                       | 2.6.32-310.21        | 2.6.32-311.23        |    3 |        3 |
[17:09] <sconklin> | ---      linux-ports-meta                | <IP_ADDRESS>.19         | <IP_ADDRESS>.20         |    0 |        0 |
[17:09] <sconklin> | ---      linux-lts-backport-maverick     | 2.6.35-22.34~lucid1  | 2.6.35-23.41~lucid1  |    0 |        0 |
[17:09] <sconklin> | ---      linux-backports-modules-2.6.32  | 2.6.32-26.25         | 2.6.32-27.26         |    0 |        0 |
[17:09] <sconklin> | ---      linux                           | 2.6.32-26.48         | 2.6.32-27.49         |    3 |        3 |
[17:09] <sconklin> | ---      linux-meta                      | <IP_ADDRESS>.28         | <IP_ADDRESS>.29         |    0 |        0 |
[17:09] <sconklin> | ---      linux-meta-ec2                  | <IP_ADDRESS>0.11        | <IP_ADDRESS>1.12        |    0 |        0 |
[17:09] <sconklin> |                                          |                      |                      |      |          |
[17:09] <sconklin> | maverick linux-backports-modules-2.6.35  | 2.6.35-23.13         | 2.6.35-24.15         |    0 |        0 |
[17:09] <sconklin> | ---      linux-ports-meta                | <IP_ADDRESS>.17         | <IP_ADDRESS>.18         |    0 |        0 |
[17:09] <sconklin> | ---      linux-meta                      | <IP_ADDRESS>.25         | <IP_ADDRESS>.28         |    0 |        0 |
[17:09] <sconklin> | ---      linux                           | 2.6.35-23.41         | 2.6.35-24.42         |   14 |       14 |
[17:09] <sconklin> |                                          |                      |                      |      |          |
[17:09] <sconklin> ..
[17:09] <bjf> [TOPIC] Incoming Bugs: Regressions (JFo)
[17:09] <MootBot> New Topic:  Incoming Bugs: Regressions (JFo)
[17:10] <JFo> Incoming Bugs
[17:10] <JFo>  38 Natty Bugs (up 6)
[17:10] <JFo>  1127 Maverick Bugs (up 14)
[17:10] <JFo>  1096 Lucid Bugs (down 14)
[17:10] <JFo> Current regression stats (broken down by release):
[17:10] <JFo> [17:10] <JFo>   * 26 maverick bugs (up 1)
[17:10] <JFo>   * 76 lucid bugs (down 7)
[17:10] <JFo>   * 6 karmic bugs (no change)
[17:10] <JFo>   * 0 hardy bugs (no change)
[17:10] <JFo> [17:10] <JFo>   * 177 maverick bugs (up 2)
[17:10] <JFo>   * 198 lucid bugs (no change)
[17:10] <JFo>   * 40 karmic bugs (no change)
[17:10] <JFo>   * 2 hardy bugs (no change)
[17:10] <JFo> [17:10] <JFo>   * 13 maverick bugs (no change)
[17:10] <JFo>   * 3 lucid bugs (down 3)
[17:10] <JFo>   * 1 karmic bug (no change)
[17:10] <JFo> .
[17:10] <JFo> ..
[17:11] <bjf> [TOPIC] Incoming Bugs: Bug day report (JFo)
[17:11] <MootBot> New Topic:  Incoming Bugs: Bug day report (JFo)
[17:11] <JFo> The next bug day will be next week. I'd like for that one to focus on regression-proposed bugs
[17:11] <JFo> since the ones that I have on my list have been there too long to be seriously considered as legitimate
[17:11] <JFo> bugs in the proposed queue. I've decided to use this small segment of bugs due to the majority
[17:11] <JFo> of interested people being on holiday.
[17:11] <JFo> ..
[17:11] <bjf> [TOPIC] Triage Status (JFo)
[17:11] <MootBot> New Topic:  Triage Status (JFo)
[17:11] <JFo> I have begun testing the script that replaces one tag with another. There is a pre-existing script
[17:11] <JFo> that bjf made me aware of, and I am looking at that for some of the other scripts I have/had planned.
[17:11] <JFo> ..
[17:12] <bjf> [TOPIC] Open Discussion or Questions: Raise your hand to be recognized (o/)
[17:12] <MootBot> New Topic:  Open Discussion or Questions: Raise your hand to be recognized (o/)
[17:12] <JFo> o/
[17:13] <bjf> one thing i'd like to point out is that this will be the last irc meeting of this year, the next will likely be Jan. 4, 2011
[17:13] <bjf> JFo, go
[17:13] <JFo> If I don't speak to some of you before the holidays, Happy Holidays!! Hope you enjoy your vacations.
[17:13] <JFo> ..
[17:13] <JFo> :-)
[17:13] <sconklin> +1
[17:13] <kamal> happy holidays all!
[17:13] <ara> Happy holidays!
[17:13] <smb> \o/
[17:13] <smb> and +1
[17:14] <bjf> thanks everyone
[17:14] <bjf> #endmeeting
[17:14] <MootBot> Meeting finished at 11:14.
[17:14] <jjohansen> thanks bjf
[17:14] <kamal> thanks bjf
[17:14] <JFo> thanks bjf
[17:14] <ara> thanks all!
[17:14] <smb> thanks bjf
[17:14] <sconklin> thanks!
[17:14] <ara> you run a fast meeting!
[17:14] <JFo> heh
[17:14] <JFo> we are infamous for that ara :)
[17:14] <smb> ara, we don't like long ones
[22:54] <bioterror> good evening
[22:56] <Emerling> bioterror, good evening hi
[22:59] <JackyAlcine> Good evening, everyone. I'm pretty excited.
[22:59] <ChrisDruif> Your here too JackyAlcine?
[22:59] <Emerling> JackyAlcine, :D congratulation
[22:59] <JackyAlcine> ChrisDruif: Yup.  I trust you are preapred.
[23:11] <JackyAlcine> Fit for what?
[23:11] <JackyAlcine> And time remaining?
[23:11] <ChrisDruif> Thought the same JackyAlcine xD
[23:12] <JackyAlcine> you have a launchpad, ChrisDruif ?
[23:12] <ChrisDruif> I don't think so, sorry...:)
[23:12] <phillw> JackyAlcine: , ChrisDruif https://wiki.ubuntu.com/phillw#Testimonials
[23:12] <ChrisDruif> I'm just here to help....don't wanna fuss with a launchpad page of myself...
[23:13] <JackyAlcine> Oh, okay. :D
[23:18] <ChrisDruif> Did you mean this with launchpad: https://launchpad.net/~chrisdruif
[23:38] <JackyAlcine> I'm not sure if I either missed the meeting or it hasn't started.
[23:39] <bioterror> starts in 20 minutes
[23:39] <bioterror> if you
[23:39] <bioterror> if you're talking about the beginners team
[23:40] <JackyAlcine> Okay, thanks bioterror
[23:58] <UndiFineD> o/
[23:58] <head_victim> \o
[23:59] <JackyAlcine> :D
[23:59] <hajour> \o


[03:07] <newz2000> hey, will be on a bit later, sorry missed you
[16:54] <newz2000> So I've closed 2 dozen bugs but for the most part they've been obsolete
[16:54] <newz2000> I'm afraid that soon I'm going to have to actually do some work to close them
[20:38] <alitabuger7> newz2000: How long is it going to take<EMAIL_ADDRESS>to even acknowledge the email about SpreadUbuntu. It's been over a week now. Are they considering it? Did they get it? What's going on?
[20:39] <newz2000> alitabuger7: hi, I don't have a good answer for you because I'm not certain of who hadnles that. Let me see if I can get you an answer, do you happen to have the RT number?
[20:39] <leftyfb> newz2000: what ever happened to getting spreadubuntu.org to the spreadubuntu.neomenlo.org website?
[20:40] <newz2000> leftyfb: I think that's what alitabuger7 is referring to. It is in the hands of someone else but I will see if I can find any information.
[20:40] <leftyfb> i just got here, wasn't aware of it being discussed already :)
[20:41] <leftyfb> I came up with the original idea back in March and came here to request it in April .. bad timing since everyone was busy with the Jaunty release
[20:42] <newz2000> I remember. :-)
[20:42] <newz2000> I think it's a good idea personally.
[20:44] <alitabuger7> I run that website, so that's why I'm asking. I did not get a number. I sent an email to<EMAIL_ADDRESS>like you asked me to. I have not gotten any feedback on that yet.
[20:46] <newz2000> oh, you didn't get an auto reply? Hmm
[20:46] <leftyfb> alitabuger7: hi there. I thought your site was great and deserved the unutilized domain name
[20:46] <alitabuger7> nothing
[20:46] <leftyfb> so I took it upon myself to request it back in April
[20:46] <newz2000> alitabuger7: can you give me your email address you used? (you can /msg me if you prefer to keep it private)
[20:46] <alitabuger7> I sent it from<EMAIL_ADDRESS>and signed it with the same key as I have on launchpad.
[20:47] <alitabuger7> on LP my username is edb82189
[20:47] <newz2000> let me look, just a moment
[20:48] <newz2000> alitabuger7: your ticket number is 7336
[20:48] <newz2000> let me ping the IS staff to see if I can get an answer
[20:48] <newz2000> I see that the ticket has been put in a queue but it hasn't been prioritized or assigned yet
[21:02] <newz2000> a sysadmin is looking at it
[21:03] <alitabuger7> yeah, leftyfb, that's kind of why I don't really understand why it took so long. They're paying for that domain anyway, and right now it's not doing nearly as much good as it should be.
[21:03] <alitabuger7> Thank you newz2000
[21:04] <newz2000> Well, the problem is that there are a lot of things to do and sometimes you get so caught up and focused on the big things that it eats up all your time.
[21:05] <alitabuger7> Which is a better primary domain, spreadubuntu.com or spreadubuntu.org? I can change the .htaccess so that it pushes all .com traffic to .org and vice-versa.
[21:05] <alitabuger7> I understand being busy, for sure.
[21:17] <leftyfb> i'd say stick with .org
[21:17] <leftyfb> it's not really a commercial entity
[21:18] <GreySim> But definitely still grab the .com and redirect.
[21:19] <leftyfb> well, that's up to the admins :)
[21:22] <alitabuger7> If they direct them to my server, I can choose between the two.
[21:25] <newz2000> alitabuger7: I think they replied, did you get it?
[21:25] <alitabuger7> I have recieved an email from nick moffitt
[21:25] <newz2000> excellent
[21:25] <alitabuger7> "Please accept my apologies for the delay in replying to you.  We will be in touch shortly with an update on this."
[21:26] <newz2000> Basically they haven't had time to look at it but Nick himself isn't authorized to make a final decission on this
[21:26] <newz2000> but he's very responsible, I expect it will get attention soon
[21:26] <newz2000> it's evening time in Europe which is where the people who need to decide are located
[21:27] <alitabuger7> Thank you for getting things moving again. I'm sure that the ball is rolling now.
[21:28] <newz2000> you're welcome
[22:05] <SiDi> (these damn europeans, they're always somewhere else when we need them :P)
[22:15] <jpds> newz2000: http://webapps.ubuntu.com/employment/canonical_STA/
[22:15] <jpds> newz2000: Job summary: Millbank ?
[22:16] <jpds> I know Millbank's a nice place... but it's not the best thing to put into a job summary ;)
[22:16] <newz2000> Nice catch. Copy and paste error I think
[22:16]  * newz2000 checks
[22:17] <newz2000> all better
[22:18] <newz2000> thanks jpds
[22:18] <jpds> No problems.
[22:21] <SiDi> the kernel dev offer is gone :o
[22:21] <SiDi> did you find someone ?
[22:22] <newz2000> :-/ I guess so
[22:23]  * SiDi waits on a "stupid mascot" job offer to send an application mail !
[22:35] <newz2000> SiDi: I'll make sure to give you notice before I post such a job to the website. :-)
[22:36] <SiDi> thanks, newz2000 !
[23:15] <MadsRH> Any wiki masters here?
[23:17] <MadsRH> I just need help making a table center on the wiki. Does anyone know how to do that?
[23:19] <SiDi> i'm not sure you can
[23:19] <SiDi> you can use the table style to change the inside, but i dont think you can change the positioning :/
[23:20] <MadsRH> SiDi -> :-( ok, thanks
[23:21] <SiDi> i just checked : the table style doesnt care about margin style properties
[23:21] <SiDi> so you cant emulate centering with margins
[23:22] <SiDi> and since i forgot 75% of CSS, i dont remember how else to center stuff
[23:23] <MadsRH> okay, I'll work something out - thanks again
[23:24] <GreySim> I would have to see the markup in question and play with it to be sure, but you *might* be able to set "text-align: center" on the table itself, then "text-align: left" on the table contents.
[23:28] <MadsRH> Perfect GreySim! I created a tablestyle with text-align:center
[23:28] <MadsRH> Thanks
[23:29] <GreySim> No problem, glad it worked. :)


[12:00] <hal90001> first time using weechat yeah ;o)
[12:02] <knome> congrats.
[12:07] <hal90001> knome: thx
[12:08] <hal90001> i like it. used pidgin before. its nice. but i dont like the fact that it stays active in background when i close it.
[12:10] <crond> Ok that confused me SO much
[12:10] <crond> Cause WeChat, the chinese android app
[12:10] <crond> so you made me doubletake.
[12:12] <hal90001> crond: ;o) no no its weechat client for terminal
[12:13] <crond> lol yeah that makes SO much more sense.
[12:13] <crond> can't say I've ever used it, in ssh I just use irssi
[12:13] <Unit193> Good plan.
[12:14] <crond> I use hexchat in X, though.
[12:15] <hal90001> crond: yeah i thought about using irssi  but weechat i tried first
[12:15] <crond> hey if it works, it works
[12:15] <crond> no point in getting religious about program choice in Linux
[12:15] <crond> unless you use emacs. cause emacs is terrible.
[12:18] <hal90001> i'll try irssi next - not that i care about features - i'll choose what suits me better
[12:19] <Unit193> You'll have to configure it a bit, I'd recommend a newer version that supports SASL.
[12:21] <hal90001> Unit193: like themes or colors?  xubuntu gives me 0.8.19 from official repos
[12:22] <Unit193> That should do.
[12:23] <crond> looks like my debian box has 0.8.17 and it has SASL I do believe
[12:23] <crond> so you'll be fine
[12:25] <hal90002> here i am
[12:25] <hal90002> irssi
[12:25] <Unit193> crond: https://irssi.org/2016/02/29/irssi-0.8.18-released/
[12:26] <hal90002> looks and feels a little bit untidy - nicknames are not in a list on the right side - but i know it can be configured
[12:26] <crond> Unit193, hmm, guess it doesn't.  interesting
[12:27] <Unit193> crond: cap_sasl.pl only.
[12:27] <crond> I just connected to my znc so it hadn't come up
[12:28] <Unit193> hal90001: Yeah irssi isn't the best out of the box, but I'm quite fond of it myself.
[12:29] <hal90002> i think i'll get along with weechat (i'm lazy) but ill keep irssi installed for checking it out a bit more later
[12:29] <Unit193> Sure, use what works (in your case, weechat.)
[12:29] <hal90001> :o)
[12:30] <crond> Just don't use emacs.  it probably can be an irc client, but it's a terrible idea.
[12:30] <knome> crond, didn't you just say there was no reason for getting religious...
[12:30] <crond> knome, except about emacs.
[12:30] <knome> nope, including emacs, if you will
[12:31] <crond> never.  also, it DOES have an irc client.  https://www.emacswiki.org/emacs?action=browse;oldid=EmacsIRCClient;id=ERC
[12:31] <crond> lol
[12:31] <crond> Emacs: "Screw the kitchen sink approach, we toss the entire house at it."
[12:32] <hal90001> i heard about emacs but do not really know what that is - there is "mac" in the name that worries me ^^
[12:32] <Unit193> crond: He was politely asking you to tone down the negativity, actually.
[12:32] <knome> Unit193, yes
[12:32] <Unit193> hal90001: Text editor with extensions.
[12:33] <crond> Unit193, pfft. I'm just playfully taking cracks at emacs, if people don't have enough of a sense of humour to handle some teasing, then they have other issues
[12:33] <crond> also, if they care enough about a text editor to get offended, more issues.
[12:33] <hal90001> nano and mousepad are nice
[12:34] <knome> crond, maybe, but this is also a family-friendly and all-inclusive channel, so let's be nice and not make people go away even if they had problems that made them leave...
[12:34] <crond> emacs is notoriously ...feature rich.  I don't see how on earth making a joke about that could be 'non-inclusive'
[12:35] <crond> it's a text editor, not gender identity
[12:35] <crond> but fair enough
[12:37] <crond> I haven't ever used mousepad
[12:38] <knome> it's a good, simple GUI text editor that does its job
[12:38] <hal90001> I have a question here. There is a MIME Type Editor in Xubuntu. I can assign default programs to open specific file types and change the associations to another program. But there is no option to remove the file type association. That bugs me.
[12:40] <knome> hal90001, ~/.local/share/applications/defaults.list
[12:40] <knome> i think that should do it..
[12:41] <crond> wouldn't it be in  /usr/share/applications/defaults.list or /usr/share/applications/mimeapps.cache ?
[12:41] <crond> Oh, yeah, or for local user.
[12:41] <knome> likely the one i mentioned, unless you want to remove some default defaults...
[12:41] <crond> what knome said
[12:41] <knome> and cache is just what it says - cache - don't trust it :P
[12:41] <crond> I have a tendancy to hamfistedly modify things for my entire system in the wrong places.
[12:42] <knome> unfortunately sometimes you kind of have to, and that's even worse
[12:45] <hal90001> found it. /usr/share/xubuntu/applications/defaults.list seems to be the right one with the unwanted association i was looking for
[12:47] <hal90001> thanks
[12:49] <hal90001> okay have to to some day activities besides hacking linux and chatting with you - see ya and thanks for the help
[13:10] <Arief> someone, can you help me fix audio in XUBUNTU 16.04 ?
[13:11] <cfhowlett> !sound | Arief start here
[13:58] <crond> hmm firefox isn't scaling fonts with my system dpi scaling
[18:40] <anonymous_alias> hello @all
[18:41] <anonymous_alias> today I upgraded vrom 17.04 to 17.10
[18:41] <anonymous_alias> now I have a strange behavior after I closed the lid of my laptop
[18:43] <anonymous_alias> after reopenning the lid the mouse pointer disappeared and when I move the mouse the lower part of the screen up to the line where the mouse pointers "hotspot" schould be flickers balck and white.
[18:44] <anonymous_alias> when I stop moving the mouse the desktop is shown as normal.
[18:45] <anonymous_alias> When I logg of and log in again the behavior is back to normal until I again close thze lid.
[18:45] <anonymous_alias> any hint where to look for the problem?
[18:54] <well_laid_lawn> anonymous_alias:  see if the X log shows a clue
[18:58] <zleap> probably in /var/log
[19:10] <anonymous_alias> well_laid_lawn: something special to look for (except "error")?
[19:12] <well_laid_lawn> I have never seen your issue before so not sure how it would be happening
[19:13] <anonymous_alias> nothing suspecious in  /var/log/Xorg.0.log
[19:13] <well_laid_lawn> what's the vid card ?
[19:13] <anonymous_alias> VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
[19:14] <anonymous_alias> Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
[19:15] <well_laid_lawn> check to see if it is using sna when it needs uxa
[19:15] <anonymous_alias> can you guide me how?
[19:16] <anonymous_alias> on the other hand, it it was such a basic configuration, shouldnt it fail before closing the lid too?
[19:16] <well_laid_lawn> in a terminal   grep -i sna /var/log/Xorg.0.log
[19:17] <anonymous_alias> returns nothing
[19:19] <well_laid_lawn> that was my guess for what's happening
[19:20] <anonymous_alias> looking for uxa in /var/log/Xorg.0.log also returns nothing
[19:20] <anonymous_alias> is that OK?
[19:27] <well_laid_lawn> probably
[19:27] <well_laid_lawn> some things to try - https://wiki.archlinux.org/index.php/intel_graphics#SNA_issues
[19:43] <anonymous_alias> Thanks for the li9nk but none of them seams to e applicapable because they have different failure descriptions. Also they seam to apply for lder GCs before Rev06 whereas I have Rev07.
[19:47] <well_laid_lawn> it does seem to be an odd thing you have happening there anonymous_alias
[19:52] <anonymous_alias> think so too... ;o)
[19:53] <anonymous_alias> the odd thing is that I only made a minor update and now it's broken...
[19:57] <well_laid_lawn> it will be systemd handling the lid closing/opening iirc
[19:57] <well_laid_lawn> something with that might have changed with the update
[20:10] <anonymous_alias> I wonder how to find out what...
[20:54] <anonymous_alias> quite strange: I just figured out that when I switch to a console (<strg><alt><f1>) and back to grphic console (<alt><f7>) the problem disapears (until I close the lid next time...). So at least I have a work around.
[20:55] <anonymous_alias> Thanks well_laid_lawn for your time!
[20:56] <well_laid_lawn> cheers
[21:06] <Atomic_fZQd2> is asking for help with xubuntu appropriate here?
[21:08] <Atomic_fZQd2> welp
[21:09] <krytarik> See the topic, and just ask away.
[21:13] <Atomic_fZQd2> when i boot it up , it shiw the xubuntu logo and the after a few seconds starts flashing and doesn't boot. not a gpu issue.
[21:13] <Atomic_fZQd2> any help is appreciated
[21:14] <Atomic_fZQd2> here's what i tried: chrooting and upgrading the system with apt-get upgrade and also apt-get autoremove
[21:14] <Atomic_fZQd2> i also tried reconfigurong with dpkg
[21:15] <krytarik> !nomodeset | Atomic_fZQd2: Also tried this yet?
[21:16] <well_laid_lawn> from the live cd you should be able to mount the os and check the kernel log too
[21:18] <quantzbeats> well_laid_lawn: where's the kernel log? in /var/log ?
[21:18] <quantzbeats> ubottu: will try that now
[21:19] <well_laid_lawn> yep in /var/log
[21:22] <quantzbeats> ok will check after work.
[21:23] <quantzbeats> gtg
[21:23] <quantzbeats> ttyl
[21:23] <quantzbeats> thanks


[10:28] <Mikaela> what is wrong with at least TOPICLOCK and +t flags?
[16:00] <rbasak> #startmeeting ubuntu-server-team
[16:00] <meetingology> Meeting started Tue Aug 30 16:00:16 2016 UTC.  The chair is rbasak. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:00] <meetingology> Available commands: action commands idea info link nick
[16:00] <rbasak> #topic Review ACTION points from previous meeting
[16:00] <rbasak>     powersj to coordinate updating of triaging section in https://wiki.ubuntu.com/ServerTeam/KnowledgeBase
[16:00] <cpaelzer> o/
[16:00] <powersj> o/
[16:00] <rbasak> powersj: how's that going?
[16:00] <powersj> done! please add action item for rbasak and cpaelzer to review
[16:00] <rbasak> Excellent, thanks!
[16:01] <rbasak> #action cpaelzer and rbasak to review new triaging section in https://wiki.ubuntu.com/ServerTeam/KnowledgeBase
[16:01] <meetingology> ACTION: cpaelzer and rbasak to review new triaging section in https://wiki.ubuntu.com/ServerTeam/KnowledgeBase
[16:01] <rbasak> #link https://wiki.ubuntu.com/YakketyYak/ReleaseSchedule
[16:01] <rbasak> #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-y-tracking-bug-tasks.html#ubuntu-server
[16:01] <rbasak> Any updates or work that needs wider communication?
[16:01] <rbasak> I sent an email about ntpdate to the ML earlier.
[16:02] <cpaelzer> I'll come to the ML with some discussion about what we face with qemu machine types
[16:02] <rbasak> Great!
[16:02] <rbasak> Anything else?
[16:02] <cpaelzer> but I'm still writing use cases and examples and discuss with more peers - so nothing for now
[16:02] <jgrimm> o/
[16:03] <rbasak> #topic Server & Cloud Bugs (caribou)
[16:03] <rbasak> caribou: o/
[16:03] <caribou> rbasak: nothing much
[16:03] <caribou> rbasak: working on a sosreport subordinate charm
[16:03] <caribou> rbasak: and normal bugfixing investigation
[16:03] <rbasak> Sounds good!
[16:04] <rbasak> #topic Weekly Updates & Questions for the QA Team (powersj)
[16:04] <powersj> Investigated Yakkety ISO oversize issue and determined root cause to be due to GCC 6 transition. GCC 6 binaries are significantly larger than GCC 5. Fix is planed before Yakkety release.
[16:04] <rbasak> Any updates from powersj, or questions for powersj?
[16:04] <powersj> Continuing to work with robie, cpaelzer, nacc on server bug triage. Made updates to documentation, but still need to continue documenting process and procedure as we continue to evolve it. See: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase
[16:04] <powersj> Automated ISO tests are getting better. Goal is to complete triage of remaining failing tests and build action plan for final tests. These final issues are quite a bit more complicated and may require removing or revamping the tests entirely due to nature of the changes.
[16:04] <powersj> Thanks to cpaelzer have access to torkoal. RT ticket is closed, so up to us to complete the setup. May be able to get it up on Jenkins this week. Cross your fingers. Finally, getting lxctest + curtin ipv6 tests prototype working before heading out this week.
[16:05] <rbasak> Thank you powersj!
[16:05] <rbasak> #topic Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges)
[16:05] <rbasak> Anything to/from thje kernel team?
[16:05] <smb> nothing new since last week
[16:06] <smb> as to "to" if tehre are questions?
[16:06] <rbasak> I guess not. Thank you smb!
[16:06] <rbasak> #topic Upcoming Call For Papers
[16:07] <rbasak> Any upcoming CfPs?
[16:08] <rbasak> Any upcoming events?
[16:08] <rbasak> #topic Open Discussion
[16:08] <rbasak> Any other comments?
[16:09] <rbasak> #topic Announce next meeting date, time and chair
[16:09] <rbasak> The next meeting will be on Tue 6 Sep 16:00:00 UTC 2016. gaughen will chair.
[16:10] <rbasak> #topic Assign daily bug triage for week (powersj, rbasak, nacc, cpaelzer)
[16:10]  * gaughen avoids eye contact
[16:10] <rbasak> gaughen: :)
[16:10] <powersj> yea! my new topic
[16:10] <rbasak> powersj: would you mind taking this topic please?
[16:10] <powersj> yes
[16:10] <rbasak> Ah :)
[16:10] <powersj> so point of this is to make sure we have coverage each week for bug triage
[16:11] <powersj> cpaelzer took Monday + weekend, I'll be taking tuesday and wednesday
[16:11] <powersj> rbasak, would you be able to triage thursday/friday?
[16:11] <powersj> we don't have nacc this week so just 3 of us
[16:11] <rbasak> Sure
[16:11] <rbasak> So when should I triage what?
[16:11] <rbasak> Are you talking about the day I triage, or the days I must cover?
[16:11] <powersj> excellent and by day I mean the day you do triage. So if you are triaging thursday/friday means you will be covering the bugs that came in wednesday/thursday
[16:12] <rbasak> OK.
[16:12] <powersj> I tried to put this on the wiki as well
[16:12] <powersj> but may need to be called out a bit better :)
[16:13] <rbasak> OK
[16:13] <rbasak> #topic Assigned merges/bugwork (rbasak)
[16:13] <jgrimm> rbasak, i updated my bugs
[16:13] <rbasak> Thank you!
[16:13] <jgrimm> closed 1, still have 1 assigned
[16:13] <rbasak> Does anyone else have any updates?
[16:14] <cpaelzer> I updated directly in the sheet
[16:14] <cpaelzer> and rbasak already covered the open wound that is the stalled ntp bugs with his mail
[16:14] <cpaelzer> thanks
[16:14] <jgrimm> :)
[16:14] <rbasak> Does anyone have capacity to take more bugs?
[16:15] <jgrimm> rbasak, i'll take one
[16:15] <cpaelzer> I'll add those that I already work on to the list without taking any on top
[16:15] <jgrimm> rbasak especially if you have other bite-sized
[16:16] <rbasak> jgrimm: how about bug 1580731? Looks like a straightforward SRU.
[16:16] <jgrimm> rbasak, sure!
[16:16] <rbasak> Great! Anyone else?
[16:17] <rbasak> OK, so I guess we're done.
[16:17] <rbasak> Thanks all!
[16:17] <rbasak> #endmeeting
[16:17] <meetingology> Meeting ended Tue Aug 30 16:17:44 2016 UTC.
[16:17] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-08-30-16.00.moin.txt