[08:00] <DanChapman> Good Morning
[12:10] <mihir> hi all
[12:10] <mihir> Have greaet week ahead :)
[13:32] <Aki-Thinkpad> in ubuntu sdk, I notice there are a number of components which do not correspond to context help. Should I be reporting this as a bug?
[13:32] <Aki-Thinkpad> for example, TextArea {}
[13:41] <Elleo> Aki-Thinkpad: sounds like a good idea; iirc TextArea is part of the QtQuick components rather than the Ubuntu.Components, so it might just be that the documentation package for QtQuick is missing or something
[13:41] <Elleo> that's just a guess though
[13:44] <Aki-Thinkpad> Elleo, a bit confused; is the button{} bundled by qml different than the button{} bundled by ubuntu.components?
[13:50] <Elleo> as far as I'm aware there isn't any Button component in QtQuick
[13:51] <Elleo> yep, just checked QtQuick doesn't provide a Button, only QtQuick Controls does (which you probably don't want to be using on Ubuntu Touch, as they'd look out of place)
[17:44] <qtros> popey ping
[19:30] <mhall119> qtros: btw, I passed on the info about your qt 5.2.1 bug to the showdown organizers
[19:33] <qtros> mhall119 hello! Huge thanks!
[19:34] <qtros> mhall119 I owe ;)


[09:16] <pmatulis> i trying to upgrade my controller model. there is no output at all and it's hanging. any hints?
[09:19] <rick_h> pmatulis:  your vpn isn't connected?
[09:19] <rick_h> pmatulis:  sounds like the client isn't reaching the controller and waiting to time out but not sure
[09:24] <pmatulis> rick_h, yeah, it did time out. need to figure this out. ty
[09:55] <jam> simple review: https://github.com/juju/juju/pull/10648
[18:11] <cloudsigma-belos> Hello, how are you?
[18:12] <cloudsigma-belos> Could you please help me with an error which I when I am trying to bootstrap an image with Juju?


[09:51] <cimi> pstolowski, dzien dobry
[09:51] <cimi> pstolowski, can you add ~cimi/unity8/bug-1541967 to your silo?
[09:52] <pstolowski> cimi, ciao! sure
[09:57] <cimi> tsdgeos, when you want to start having a look, we still need to test and find bugs in silo https://code.launchpad.net/~cimi/unity8/bug-1541967/+merge/285333
[10:00] <tsdgeos> k
[10:00] <tsdgeos> very quick code read looks reasonable
[10:00] <cimi> tsdgeos, thanks, go back to your studying :) I'll ping you after we tested a bit with the silo
[10:01] <pstolowski> cimi, building
[10:01] <cimi> pstolowski, I hope it got the last version cause there was one stupid bzr conflict, that I fixed
[10:01] <pstolowski> hmm we will see ;)
[10:11] <pstolowski> uh, it didn't ;)
[10:12] <pstolowski> cimi, can you merge https://code.launchpad.net/~aacid/unity8/activtion-progress/+merge/284421 into your branch and set it as prereq?
[10:13] <cimi> pstolowski, yes
[10:16] <cimi> pstolowski, done
[10:18] <pstolowski> cimi, pls also set it as prerequisite in your MP
[10:18] <cimi> pstolowski, I think I did
[10:19] <cimi> no
[10:20] <cimi> I did propose to merge against that
[10:20]  * cimi redoes
[10:20] <cimi> ah no is fine
[10:21] <cimi> E_TOO_MANY_TABS
[10:21] <cimi> pstolowski, https://code.launchpad.net/~cimi/unity8/bug-1541967/+merge/286623
[10:21] <pstolowski> yep
[10:21] <pstolowski> thanks
[10:28] <pstolowski> cimi, hmm is stack interface .h still included by a mock? https://launchpadlibrarian.net/240525440/buildlog_ubuntu-vivid-amd64.unity8_8.11+15.04.20160219-0ubuntu1_BUILDING.txt.gz
[10:30] <cimi> pstolowski, I removed that
[10:30] <cimi> and builds here
[10:32] <cimi> tsdgeos, how is tests/mocks/Unity/Unity.qmltypes updated?
[10:33] <tsdgeos> cimi: it's on its header
[10:33] <cimi> tsdgeos, but I just run it?
[10:33] <tsdgeos> yeah
[10:33] <cimi> tsdgeos, ok, wondering if it was done automatically when landing
[10:34] <tsdgeos> i think it doesn't
[10:35] <pstolowski> cimi, ah, it's a conflict https://ci-train.ubuntu.com/job/ubuntu-landing-076-1-build/8/consoleFull
[10:36] <cimi> tsdgeos, mmm weird, a lot changed it looks like it wasnt updated in  a while, anyway doing it
[10:36] <tsdgeos> yeah we "don't care much" about those files
[10:40] <mzanetti> lpotter, hey ho. have unity8 running with silo 9. works fine now
[10:43] <cimi> pstolowski, my branch is merged with both albert and unity8 branch
[10:43] <cimi> pstolowski, conflicting with what?
[10:45] <pstolowski> cimi, not sure, https://ci-train.ubuntu.com/job/ubuntu-landing-076-1-build/8/consoleFull
[10:45] <cimi> pstolowski, try 2183 version
[10:47] <pstolowski> ok
[10:49] <pstolowski> cimi, i'm going for early lunch.. pls keep an eye on https://requests.ci-train.ubuntu.com/#/ticket/1021 and feel free to kick it again if needed
[10:49] <cimi> pstolowski, smacznego
[10:50] <pstolowski> cimi, your wife taught you well ;) thanks!
[11:21] <cimi> Saviq, tsdgeos some help with bzr? this is the log in jenkins https://ci-train.ubuntu.com/job/ubuntu-landing-076-1-build/9/console my branch that conflicts has merged in both unity8 and albert activation-progress branch, jenkins merges unity8, then activation progress, then complains criss-cross merge with mine
[11:21] <cimi> shall I start from scratch, unity8->activation-progress->my new branch?
[11:22] <temp> hello, new user here with possible bug in unity! :) (or maybe I don't know what I am doing :( ...
[11:22] <cimi> or there is a way to fix without pushing on top of my current branch?
[11:22] <Saviq> cimi, you need to overwrite
[11:22] <Saviq> cimi, because you merged trunk, then prerequisite, then prerequisite merged trunk, too
[11:22] <Saviq> roughly
[11:22] <Saviq> and bzr gets scared when that happens
[11:23] <cimi> Saviq, thanks for explaining
[11:23] <Saviq> temp, it's best if you file a bug on launchpad, using "apport-bug unity"
[11:24] <temp> when I set "focus" in Unity Tweek Tool to "mouse" or  "sloppy" I cannot rename files on the desktop by right click then rename ...
[11:25] <temp> I was actually hoping someone might be able to point out my error before I report something that is not a bug.
[11:26] <temp> wanted to see if anyone might be able to reproduce my problem .... not sure if that is appropriate here.
[11:27] <cimi> Saviq, can you trigger a rebuild of unity8 here https://ci-train.ubuntu.com/job/ubuntu-landing-076-1-build/build ?
[11:27] <cimi> Saviq, I lack permission
[11:28] <Saviq> ack
[11:28] <Saviq> cimi,
[11:28] <Saviq> https://ci-train.ubuntu.com/job/ubuntu-landing-076-1-build/10/console
[11:28] <cimi> Saviq, thanks man
[11:29] <cimi> Saviq, or just give me powers!!! eh eh
[11:29] <Saviq> sil2100, ↑ can add cimi to ci train users please?
[11:30] <sil2100> Saviq: sure
[11:30] <cimi> thanks sil2100
[11:30] <sil2100> cimi: you should have teh powers ;)
[11:32] <cimi> Saviq, merge failed again :(
[11:32] <Saviq> cimi, you need to overwrite the branch, merging from scratch on top of the prerequisite, or trunk, and then prerequisite on top, did you?
[11:33] <Saviq> cimi, you actually need to uncommit, shelve and recommit as applicable
[11:33] <cimi> ah ok
[11:33] <cimi> Saviq, I branched trunk, merged albert branch, merged mine (saw same error of jenkins), solved conflict and pushed to my branch
[11:34] <Saviq> cimi, you just tried to hide the criss-cross in a merge, that doesn't work ;)
[11:35] <cimi> Saviq, so this time I take the prerequisite, merge my branch on top, push?
[11:35] <Saviq> cimi, no
[11:35] <Saviq> cimi, you take the prerequisite, apply the patches from your branch on top (not merge, actually apply by bzr merge -c or bzr diff + patch, or bzr shelve)
[11:36] <cimi> Saviq, ah ok
[11:36]  * cimi tries
[11:36] <Saviq> cimi, you need to lose the merge history
[11:36] <cimi> Saviq, now I finally understood (I think)
[11:37] <cimi> Saviq, when bzr sees two merges somewhere in the history, freaks out
[11:41] <temp_> somehow I got transfered to a page asking me to log into Unity One ... when I ran apport-bug unity in a terminal ... I did but there was no option to actually describe the bug! anyone know what happened to me?
[11:42] <temp_> also wasn't sure if anyone responded to my earlier question as I was logged out of the chat page ..
[11:42] <temp_> chat page = IRC channel
[11:43] <Saviq> temp_, you need to log in to Ubuntu One / Launchpad to be able to find bugs - it's possible that if you had to register the process did not forward you through to the bug reporting page
[11:43] <Saviq> *file, not find
[11:44] <temp_> hmmm I'll try again. thx Saviq
[11:44] <Saviq> temp_, if you're logged in to launchpad now (you can check going to http://launchpad.net/ and see if your name's in the top-right edge, or a "log in" link)
[11:44] <Saviq> temp_, please run apport-bug unity again and things should be good again
[11:47] <cimi> tsdgeos, can you please merge unity8 in your activation progress branch
[11:47] <cimi> ?
[11:47] <tsdgeos> cimi: trunk? sure
[11:48] <tsdgeos> cimi: pushed
[11:49] <cimi> tsdgeos, gracias
[11:53] <cimi> Saviq, can you also please change my branch https://requests.ci-train.ubuntu.com/#/ticket/1021 here to  https://code.launchpad.net/~cimi/unity8/single-preview/+merge/286646 ? (or give me more super powers )
[11:53] <Saviq> cimi, you have the powers now
[11:53] <Saviq> cimi, log in top-right
[11:53] <Saviq> cimi, and edit at the right of the orange bar
[11:54] <cimi> 401 ERROR
[11:54] <cimi> You are not authorized to access this page. Are you logged in? Are you a member of the correct teams?
[11:54]  * cimi logs out and re logins
[11:54] <Saviq> yeah, it probably doesn't know you're in ci-train-users now
[11:55] <cimi> yeah the logout worked
[11:55] <cimi> same had to do in jenkins
[11:56] <cimi> so. much. power.
[11:59] <cimi> Saviq, yay it's building!
[11:59] <cimi> thanks
[12:22] <dandrader> hmm... can't log into a mir-unity8 desktop session anymore. get stuck on a black screen
[12:23] <cimi> Saviq, ^ dandrader
[12:23] <cimi> Saviq, was your issue just silo related?
[12:24] <dandrader> this looks suspicious http://pastebin.ubuntu.com/15130559/
[12:24] <Saviq> dandrader, when were you last logged in with that user on X11?
[12:24] <Saviq> dandrader, bug #1525285
[12:25] <dandrader> Saviq, a day or two ago I think
[12:26] <Saviq> dandrader, try logging in to X11, then to u8 again
[12:27] <Saviq> not that it's certain to work, I've had some vt issues yesterday as well
[12:32] <dandrader> Saviq, that solved it. how come?
[12:34] <Saviq> dandrader, see bug above, gstreamer clutter plugin assumes it will only ever run on X11
[12:34] <Saviq> dandrader, when you start a session, the gstreamer plugin registry gets regenerated, if needed
[12:34] <Saviq> dandrader, if that happens, clutter waits for X11 indefinitely
[12:34] <dandrader> Saviq, ah, so this was the culprit them: http://pastebin.ubuntu.com/15130582/
[12:35] <Saviq> yup
[12:35] <Saviq> dandrader, if you launch an X11 session, the registry gets generated and cached
[12:35] <Saviq> so next time you launch it's ready to go, no need to generate, so clutter pluggin isn't invoked, so no blocking
[12:37] <cimi> Saviq, I'm still very new to jenkins, why did this fail to build? https://requests.ci-train.ubuntu.com/#/ticket/1021
[12:38] <Saviq> cimi, when it says "Failed to build", means it failed in the silo
[12:38] <Saviq> cimi, so you go to https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-076 and click at one of the failed builds on the right
[12:38] <cimi> Saviq, that;s what I did
[12:38] <Saviq> cimi, "--   package 'unity-shell-scopes=11' not found"
[12:39] <cimi> I mised that
[12:39] <Saviq> cimi, https://code.launchpad.net/~stolowski/unity-api/activation-progress/+merge/284424 is still at version 10
[12:39] <Saviq> so is https://code.launchpad.net/~stolowski/unity-scopes-shell/activation-progress/+merge/284425
[12:39] <Saviq> cimi, those likely need merge + bumps now
[12:40] <cimi> Saviq, he needs to bump here I think https://code.launchpad.net/~stolowski/unity-api/single-preview/+merge/286527
[12:40] <Saviq> cimi, or actually, your bump in https://code.launchpad.net/~cimi/unity8/single-preview/+merge/286646 is unnecessary
[12:41] <cimi> Saviq, I was expecting him to bump
[12:41] <Saviq> cimi, no need to bump twice when you're in a single silo
[12:41] <cimi> in that branch I linked
[12:41] <cimi> ok
[12:43]  * cimi retriggered, let's see
[12:48] <Saviq> cimi, easy to verify - `citrain host-upgrade 76`
[12:48] <Saviq> cimi, your branch should build with that
[12:55] <pstolowski> yeah, trunk is on 9, silo has 10, should be fine
[12:55] <cimi> pstolowski, I retriggered
[12:55] <cimi> pstolowski, I did put 11 in my branch originally, thinking you would have bumped in single preview branches
[12:56] <cimi> I changed back to 10 now
[12:57] <dandrader> ltinkl, you reproduced https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1547360 on your laptop or on a phone/tablet?
[12:57] <ltinkl> dandrader, laptop
[12:57] <dandrader> ltinkl, can't reproduce it
[12:57] <ltinkl> dandrader, on laptop?
[12:57] <dandrader> ltinkl, yes
[12:57] <ltinkl> dandrader, hmm, let me try again
[12:58] <dandrader> ltinkl, tried with CursorShapes.qml from lp:~dandrader/+junk/animatedDemos
[12:58] <ltinkl> dandrader, tried with browser? (that's why I said the bug report was vague, it doesn't even mention a reproducer)
[13:00] <dandrader> ltinkl, browser doens't launch from unity8-dash or launcher (or any app for that matter, launcher my test app from terminal)
[13:01] <ltinkl> dandrader, oh it does here
[13:01] <dandrader> ltinkl, and don't feel like spending time digging into other apps. if the test app worked, it means qtubuntu, qtmir and unity8 are ok
[13:01] <ltinkl> dandrader, yeah definitely
[13:02] <dandrader> ltinkl, so it works for you as well?
[13:02] <ltinkl> dandrader, not in browser (that's what I think the BR is about), gonna try your demos
[13:04] <ltinkl> dandrader, to run, qmlscene football.qml?
[13:05] <dandrader> ltinkl, https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1547360/comments/4
[13:05] <dandrader> ltinkl, --desktop_file_hint can point to any .desktop file
[13:13] <ltinkl> dandrader, the demo works fine... so I suspect it's the (browser) app that's broken
[13:14] <dandrader> ltinkl, from my experience, MouseArea.cursorShape is really sensitive to interference from other overlapping MouseAreas etc
[13:15] <ltinkl> dandrader, I second that :) (from the window control buttons experience ;)
[13:15] <dandrader> ltinkl, iirc, the text entry in unity8-dash never caused it to request a different cursor shape from  unity8 for instance
[13:15] <ltinkl> dandrader, oh it did, seen that
[13:16] <ltinkl> hmm
[13:16] <dandrader> ltinkl, not while I was developing the cursor shapes support at least, I think
[13:16] <ltinkl> dandrader, also system setting's filter line edit
[13:17] <dandrader> ltinkl, yeah, that one worked (or used to)
[13:17] <ltinkl> dandrader, now it doesn't :/
[13:17] <dandrader> ltinkl, issue could be in uitoolkit...
[13:18] <ltinkl> dandrader, true
[13:45] <cimi> pstolowski, ok previews seems empty on the real unity8, something is off :)
[13:46] <pstolowski> cimi, hmm, ok, let me see
[13:47] <cimi> pstolowski, might me my bug
[13:47] <cimi> pstolowski, let me see
[13:50] <mterry> dednick, is there something else I can do to help with that occlusion issue?  You really don't see it?
[13:50] <dednick> mterry: i've never seen the issue; but i havent looked in a while. busy with mwc stuff at the moment.
[13:50] <mterry> dednick, ah carry on  :)
[13:51] <dednick> havent checked the stack yet
[14:07] <pstolowski> cimi, i'm getting file:///usr/share/unity8//Dash/PreviewView.qml: File not found in unity8-dash.log
[14:07] <pstolowski> cimi, and nothing happens on tap
[14:07] <cimi> pstolowski, already pushed a new version and retriggered a rebuild
[14:08] <pstolowski> ok
[14:15] <cimi> pstolowski, ok my latest revision is working on my phone, let's wait for the silo
[14:16] <pstolowski> cimi, cool. nb, these changes have great potential for regressions.. we need to check all aspects of previews - column layouts, buttons, input fields etc
[14:16] <cimi> pstolowski, I had to fight few criss cross merges, so I replaced the branch with a new one, and doing so the file naming of the diff got confused, so one file (PreviewListView.qml), wasnt renamed to the new name (PreviewView.qml)
[14:16] <pstolowski> no worries
[15:17] <pstolowski> cimi, hey, have you seen Enwei's reply re content-sharing? this looks like something unity8 side?
[15:25] <cimi> pstolowski, I will read
[15:26] <cimi> pstolowski, yeah saw ken comment
[15:26] <cimi> will fix that next week
[15:27] <pstolowski> cimi, oki, cool
[15:30] <pstolowski> tsdgeos, hey, can you bump unity-api to 7.107 in https://code.launchpad.net/~aacid/unity8/filters/+merge/271616 ?
[15:32] <tsdgeos> pstolowski: sure, give me a minute, standup
[15:37] <pstolowski> cimi, looks like ken has a fix
[15:37] <cimi> pstolowski, #ubuntu-touch
[15:44] <tsdgeos> pstolowski: pushed
[15:44] <pstolowski> tsdgeos, htx
[16:14] <cimi> pstolowski, btw I think I lost reviews with silo 76
[16:15] <pstolowski> cimi, ah, you probably set 'start afresh' when resubmitting the MP
[16:18] <cimi> pstolowski, no, preview reviews :P
[16:18] <pstolowski> cimi, ah :D
[16:18] <pstolowski> cimi, ok, that's weird
[16:18] <pstolowski> cimi, let me update
[16:23] <cimi> pstolowski,  might also be a bug on my side
[16:23] <cimi> I will check
[16:30] <pstolowski> cimi, ok, problem confirmed
[16:30] <cimi> pstolowski, can you see if is on your side too?
[16:30] <pstolowski> cimi, yeah, looking
[16:31] <pstolowski> cimi, file:///usr/share/unity8//Dash/Previews/PreviewRatingDisplay.qml:43:5: Cannot assign to non-existent property "onIsCurrentPreviewChanged"
[16:31] <pstolowski> file:///usr/share/unity8//Components/LazyImage.qml:102:9: QML Image: Cannot open: file:///usr/share/unity8//Dash/Previews/broken_image
[16:31] <pstolowski> file:///usr/share/unity8//Dash/Previews/PreviewRatingDisplay.qml:43:5: Cannot assign to non-existent property "onIsCurrentPreviewChanged"
[16:31] <cimi> what I was looking indeed
[16:31] <cimi> pstolowski, remove line 43 from that file
[16:31] <cimi> and restart unity8-dash
[16:35] <pstolowski> ok
[16:35] <cimi> pstolowski, I confirm the fix
[16:35] <cimi> pstolowski, pushing
[16:35] <pstolowski> cool
[16:36] <pstolowski> cimi, yeah, works
[16:38] <cimi> pstolowski, also tried on the desktop, layout seems to work
[16:45] <pstolowski> cimi, great. i'll do full testing on Monday
[18:58] <dandrader> Saviq, should I also pass -DUSE_OPENGLES=1 to cmake when building qtmir on my laptop?
[18:58] <dandrader> Saviq, my log is getting spammed with: QOpenGLDebugMessage("APISource", 4, "GL_INVALID_OPERATION in unsupported function called (unsupported extension or deprecated function?)", "HighSeverity", "ErrorType")
[19:00] <Saviq> dandrader, no, GLES is only for devices and emulator
[19:01] <Saviq> dandrader, owait, yeah, -DUSE_OPENGLES=1 everywhere
[19:02] <dandrader> Saviq, sounds nuts but that seems to be what debian/rules is doing....
[19:03] <Saviq> indeed
[19:04]  * Saviq looks into build logs
[19:05] <dandrader> dang it. my log is still getting spammed
[19:05] <Saviq> dandrader, that's what package builds are doing... "-- Qt5 determined to be compiled with GLES support"
[19:06] <Saviq> that's the desktop build for amd64
[19:32] <dkessel> when i set unity to scale the UI because of the high resolution screen, and afterwards boot into XFCE, all Qt apps have cropped (too large) tray icons - is there a workaround for that?
[19:32] <dkessel> apart from not setting unity to scale :p
[19:34] <dkessel> for example, clementine's tray icon failes to scale with that setting activated
[19:37] <dkessel> it looks like this: http://imgur.com/F1CF1mw <- ping balloons - know that problem?


[00:00] <nickrud> yes, a more codified way of handling bans among the various operators
[00:00] <nickrud> not looking for a resolution, but something that I think is a pressing issue for the future
[00:00] <nalioth> nickrud: do you mean "ban resolution" or "ban setting" ?
[00:00] <elkbuntu> something more than the bantracker?
[00:01] <nalioth> i personally think that if the op hasn't commented the bantracker, his/her bans should be able to be released after 24h by by any op with access to the BT
[00:01] <nickrud> resolution. Ban tracker is good, but no one ever comments about grounds for unbanning, if the op is not around. And I've seen more than a handful of bans placed by people in conflicting time zones
[00:02] <elkbuntu> nalioth, even for repeat/chronic offenders?
[00:02] <Flannel> elkbuntu: Those should have comments in the bantracker
[00:03] <nickrud> that issue of repeaters has crossed my mind, so it's no simple matter to find a reasonably flexible but fair mechanism
[00:03] <jussi01> Ok, im off to bed, Ill catch up on backlog in the morning, nini all
[00:03] <elkbuntu> Flannel, those usually have a huge-ass list in the ban tracker of prior bans/removes
[00:03] <nalioth> elkbuntu: repeat offenders will be commented at some time in their pasts, i'd presume and should come up in a BT search
[00:04] <nickrud> I'm definitely not a good bt commenter myself so I can't point at anyone else. But I think it would be a good move for us to start being more consistent about it. Then we'll have more data to mash about while we try to work out some formal scheme
[00:05] <nickrud> or informal, but a scheme none the less
[00:05] <nalioth> nickrud: do we see a wiki page somewhere from you on this?
[00:05] <nickrud> nalioth not yet. I'm still scratching my head. I find good reasons not to do whatever I think up.
[00:06] <elkbuntu> it is worth trying, but i do warn against blindly unbanning people just becuase they have no comment.
[00:06] <nalioth> elkbuntu: a single entry into the BT usually indicates no prior history
[00:06] <PriceChild> Everyone comment on the bt more! :)
[00:06] <nickrud> I think a good first step is simply commenting. And noting in the comment that it's ok to unban.
[00:07] <elkbuntu> agreed
[00:07] <nickrud> no ok, no unban
[00:08] <nalioth> not sure if any of you are familiar with dircbot, but if there is enough interest, perhaps we could do something like that ( iow, you tell the bot your reason for bannning at the time )
[00:08] <Pici> The rule used to be for operators who banned someone to be the person to deal with their unbanning, are we dismissing that rule?
[00:08] <nickrud> Pici only with explicit prior permission in the bt
[00:08] <nalioth> Pici: that has never been a hard rule, it's just come to be "the way things are"
[00:09] <elkbuntu> Pici, that one should really only be enforced for repeat offenders
[00:09] <nickrud> I'm suggesting that, anyway
[00:09] <Pici> Agreed
[00:10] <PriceChild> I think dircbot would be good, and would like to try it out, its quite good at making you add comments so things make sense(ish).
[00:10]  * PriceChild removes some commas
[00:10] <nalioth> somethign like dircbot, anyway
[00:10] <nalioth> okay, any other business?
[00:10] <elkbuntu> couldnt it just be hacked into our current frankenstein?
[00:10] <nalioth> elkbuntu: that option is available to us
[00:11] <elkbuntu> nalioth, one other item. retrieving the name ubotu.
[00:11] <nalioth> we wouldn't be using dircbot, but a clone thereof
[00:11] <elkbuntu> is it at all possible/is seveas willing to part with it?
[00:11] <nalioth> seveas is still active in #ubuntu, why not ask him?
[00:12] <elkbuntu> it gets asked of -ops several times a week, but i havent had time to annoy him abou tit
[00:12] <nalioth> we chose the bot names we have for ease of <tab-complete>
[00:12] <nalioth> but it would be nice to get the other nick(s) back
[00:13] <Flannel> ubotu hasn't logged in for 11 weeks, so even if he doesn't agree, we can technically take the nick back through regular freenode nick stuffs
[00:13] <nalioth> Flannel: yes, but that wouldn't be very friendly
[00:13] <elkbuntu> Seveas, is also here in this channel. maybe he could volunteer to discuss with the ops team at a later time
[00:13] <Pici> Right, but it would be courteous to talk to him about it
[00:14] <Flannel> nalioth: no, which is why I said it was in case it fell through
[00:14] <nalioth> Flannel: noted
[00:14] <nalioth> anything else on anyones plate?
[00:18] <PriceChild> Great well that's it then.
[00:19] <PriceChild> Will get the email sorted, and try to sort out a meeting for in 2 weeks or so, announce it earlier and yes :)
[16:41] <boredandblogging> @now


[04:24] <ubotu> New bug: #146142 in xorg (main) "gnome-mouse-properties: Horizontal Scrolling is useless" [Low,Fix released]  https://launchpad.net/bugs/146142
[04:39] <ubotu> New bug: #85746 in xorg (main) "feisty kubuntu installer - X started but nothing shown" [Undecided,Incomplete]  https://launchpad.net/bugs/85746
[04:52] <ubotu> New bug: #128526 in xresprobe (main) "probing for X, causes scrambled Frame Buffer" [Undecided,New]  https://launchpad.net/bugs/128526
[06:46] <ubotu> New bug: #149260 in mesa (main) "wine-git/google earth crashes with DRM_I830_CMDBUFFER: -22 on Thinkpad X60" [Undecided,New]  https://launchpad.net/bugs/149260
[08:15] <tepsipakki> bryce: hey, seems that tormod has been doing great work with -ati
[08:15] <bryce> :-)
[08:15] <bryce> tepsipakki: what in particular?
[08:15] <tepsipakki> hopefully there'll be a new release soon, or should we upload his version?
[08:16] <tepsipakki> tracking upstream changes and asking people test his ppa
[08:16] <bryce> I was looking at the changelog from upstream and noticed a lot of fixes it would be nice to have
[08:16] <bryce> including bug 86072
[08:16] <ubotu> Launchpad bug 86072 in xserver-xorg-video-ati "ATI ES1000 515e not recognized" [Medium,In progress]  https://launchpad.net/bugs/86072
[08:17] <bryce> hmm, well it would be a shame to waste his hard work - if you're comfortable with how it looks, I would favor uploading it as well
[08:18] <tepsipakki> if RC is next Thursday, we should act soon I think
[08:18] <bryce> agreed
[08:18] <bryce> tepsipakki: yesterday it was decided to postpone the freeze until Friday
[08:18] <bryce> (maybe it's friday for you already?)
[08:18] <tepsipakki> yep, 09:18 here :)
[08:18] <tepsipakki> AM
[08:18] <bryce> heh
[08:19] <bryce> btw, I packaged up a snapshot of the intel git head for testing:  http://people.ubuntu.com/~bryce/Testing/intel/
[08:20] <tepsipakki> oh, something happening there too :P
[08:57] <ubotu> New bug: #148686 in xserver-xorg-video-intel (main) "screen blinks a lot during boot " [Undecided,New]  https://launchpad.net/bugs/148686
[09:12] <tepsipakki> bryce: I'll merge -ati by tormod and ask his opinion if it should be uploaded when he shows up
[09:21] <bryce> great
[09:50] <ubotu> New bug: #149297 in xserver-xorg-video-intel (main) "xserver-xorg-video-intel package missing changelog" [Undecided,Confirmed]  https://launchpad.net/bugs/149297
[10:05] <ubotu> New bug: #149304 in xorg (main) "Use of "next" instead of "continue" in bash script failsafeXServer" [Undecided,New]  https://launchpad.net/bugs/149304
[12:40] <ubotu> New bug: #149367 in xrandr (main) "plug my HD tv makes xrandr display wrong resolution for my active screen" [Undecided,New]  https://launchpad.net/bugs/149367
[01:01] <ubotu> New bug: #149377 in xrandr (main) "window title stuck where gnome panel was if moved while using dual head with xrandr " [Undecided,New]  https://launchpad.net/bugs/149377
[03:10] <ubotu> New bug: #138079 in dell "Dell Inspiron 1520 nVidia 8600M GT doesn't work" [Medium,Confirmed]  https://launchpad.net/bugs/138079
[03:45] <ubotu> New bug: #149430 in xserver-xorg-video-intel (main) "No DMPS on DVI port of ADD2 card" [Undecided,New]  https://launchpad.net/bugs/149430
[06:03] <ubotu> New bug: #149490 in xserver-xorg-video-intel (main) "X crashes on suspend" [Undecided,New]  https://launchpad.net/bugs/149490
[07:25] <ubotu> New bug: #97637 in compiz (main) "Beryl/Emerald won't allow gnome-screensaver screen-unlock dialog to have input focus (dup-of: 122549)" [Undecided,New]  https://launchpad.net/bugs/97637
[08:50] <tepsipakki> tormod: looks like there is going to be a new -ati this weekend :)
[08:50] <tormod> the 6.7.195?
[08:51] <tepsipakki> probably yes, since pci-rework isn't complete yet afaik
[08:52] <tormod> will you push it into Gutsy as soon as it is out?
[08:53] <tepsipakki> well, I asked someone to take a look at the debdiff of a merger with your package, but apparently it had too many changes already..
[08:53] <tormod> but all the changes are good :)
[08:53] <tepsipakki> so, why not upload a version with a subset of them
[08:53] <tepsipakki> I know :)
[08:54] <tepsipakki> but then the delta between a shipping driver and the new upstream would be smaller :)
[08:54] <tepsipakki> cunning plan, eh? :)
[08:54] <tormod> wicked :)
[08:55] <tormod> but many of alex's commits depend on each other
[08:55] <tepsipakki> true..
[08:56] <tormod> those you asked, did they see a debdiff between 194-1ubuntu1 and -tv6 ?
[08:58] <tepsipakki> basically, yes
[08:59] <tepsipakki> http://users.tkk.fi/~tjaalton/dpkg/ati/ati.debdiff
[09:01] <tormod> if the fixed bugs would be triaged properly with high,important etc it would maybe be easier to slip it through the release managers?
[09:01] <tormod> X not starting is pretty critical. But I don't have the triaging magic power.
[09:02] <tepsipakki> you should join ubuntu-bugs then :)
[09:09] <tormod> qa-team? that sounds like... work :)
[09:10] <tormod> seems like many people have tested the -tv6 and are happy. maybe we should make a list of hardware tested?
[09:11] <tepsipakki> actually, bugsquad is the team name I think
[09:11] <tormod> I think it would be scandalous to release gutsy with the current gutsy ati, especially when fixes are available.
[09:11] <tepsipakki> I agree
[09:13] <tepsipakki> but, the freeze is not yet effective, so _technically it could be uploaded :)
[09:13] <tormod> when's the freeze
[09:14] <tepsipakki> later today..
[09:14] <tepsipakki> bryce: ping?
[09:14] <bryce> hi tepsipakki
[09:15] <tepsipakki> bryce: hi, we were just discussing the ati situation
[09:15] <bryce> sorry, was caught up in email discussion about agenda items for uds
[09:15] <tormod> we could take out the "remove cruft and dead code" commits, if that would help some release manager
[09:16] <bryce> if you point me at bugs, I can take care of marking them triaged/high/-rc candidates, etc.
[09:16] <tepsipakki> me too
[09:16] <tepsipakki> I have the list in front of me
[09:17] <bryce> tepsipakki: who did you talk to that said the delta was too much?
[09:17] <tepsipakki> if we mark all the "fix committed" bugs as high/critical and milestone rc?
[09:17] <tepsipakki> bryce: mdz, but he didn't say it quite like that.. a sec
[09:18] <bryce> the angle I've been working is to demonstrate it fixes 86072.  James Troup is the guy in charge of all of Canonical's IT infrastructure
[09:18] <bryce> so if the newest -ati solves his problem, it gives us a LOT of weight
[09:18] <tepsipakki> 17:43 < mdz> tepsipakki: I won't speak for the release team, but "works for someone" is not  very compelling.  wouldn't you prefer to upload something better tested after  release, rather than pushing in something less tested before release?
[09:19] <bryce> ah
[09:19] <tepsipakki> bryce: I think it does fix that
[09:19] <bryce> yeah sounds like we just need to tighten up our story a bit, with good evidence of proven things it fixes, etc.
[09:19] <bryce> ideally, associating each change with a specific high priority bug would help
[09:20] <tepsipakki> yes, I didn't do that.. easily fixed
[09:21] <bryce> I've been taking that approach with some of my other changes.  sort of a PITA, but reviewers are getting more strict, so I find it helps a lot
[09:21] <bryce> in any case, the extra triaging work helps clear more bugz :-)
[09:21] <tepsipakki> sure. I did point out those three "fix committed" bugs which all had the same issue; no X
[09:22] <tormod> could we work out this together on a wiki page or using gobby?
[09:22] <tepsipakki> heck, I'll mark those as critical :)
[09:22] <bryce> no, let's save critical for nuclear bomb situations... High should be sufficient
[09:23] <tepsipakki> hrm, ok :)
[09:23] <tormod> critical is only for bugs reaching a good portion of the users.
[09:23] <tepsipakki> right
[09:28] <bryce> also at some point here, maybe next week, we should go through the whole xserver-xorg-video-ati bug list and close out all the ones that are fixed now, and ask folks to re-test the ones we're not sure about
[09:30] <bryce> (unless you feel it's all already covered - but I think a top-to-bottom review focused on -ati could be a big help going into Hardy since so much has changed.)
[09:32] <tepsipakki> absolutely
[09:32] <tepsipakki> I've now marked those bugs we talked about as high
[09:38] <tepsipakki> bryce: so, do you think we could upload 194-1ubuntu2 with fixes for these bugs, or wait for .195 and file a FFe request?
[09:38] <tepsipakki> or do both
[09:39] <bryce> tepsipakki: I think your strategy of uploading an intermediate, to make the delta between it and the release smaller, is quite wise
[09:39] <bryce> it'll also help for testing
[09:44] <bryce> so, for Hardy it sounds like the focus will be for "shoring up old features"
[09:46] <bryce> colin says that in our past releases, sometimes features were completed for the release, and folks moved on; some of those features need additional polish or rework based on findings since then
[09:46] <tepsipakki> bryce: ok, I'll re-merge and upload then :)
[09:46] <bryce> for X, really the only thing that came up was discover-data
[09:47] <bryce> what I've proposed doing for Hardy is for us to extract the pci id list from discover-data, so discover can finally be dropped entirely
[09:47] <tepsipakki> upstream&debian are going to do that from the drivers
[09:47] <bryce> I think we still need something like the pci id list, in order to do overrides, but in general I think we can rely more on X to autodetect stuff, and try to minimize the size of it
[09:48] <tepsipakki> what about new upstream versions, any chance of xserver-1.5?
[09:48] <tepsipakki> scheduled for February I think
[09:49] <bryce> the discussion was focused only on ubuntu-specific things
[09:49] <bryce> well, definitely definitely 1.4 of course
[09:49] <tepsipakki> ah
[09:50] <bryce> since Hardy is a LTS, I'm a bit iffy on putting in 1.5 at the last minute
[09:51] <tepsipakki> is it going to be LTS right from the start, or later (like 8.04.1 or so)
[09:51] <tepsipakki> ?
[09:51] <bryce> on the other hand, I'm a lot more comfortable with what the process is now, so if we have to do it, it scares me less than 1.4 for gutsy
[09:51] <bryce> I assume from the start
[09:51] <tepsipakki> ok
[09:53] <tormod> tepsipakki: by "re-merge" do you mean you will take out some patches?
[09:54] <tepsipakki> tormod: yes..
[09:55] <tormod> which ones?
[09:56] <tepsipakki> I guess only 02 and 04 can be safely removed?
[09:56] <tepsipakki> haven't tried
[10:02] <tormod> and the "cruft" part of 09
[10:03] <tepsipakki> well, 02 needs to be there, otherwise 03 won't apply
[10:04] <tormod> are you sure 02 can be removed .ok
[10:04] <tepsipakki> can't be removed
[10:04] <tormod> it's basically one piece of work, that Alex commited bitwise.
[10:06] <tepsipakki> the cruft part of 09 is self-explanatory, so that can stay IMHO
[10:06] <tormod> we could do 08 separately/later but that would just be kind of ridiculous.
[10:06] <tepsipakki> 04 is big though
[10:06] <tepsipakki> right
[10:08] <tormod> 04 is big in lines, but it's removing an unused function...
[10:08] <tepsipakki> I was just coming to that :)
[10:08] <tormod> (two unused functions)
[10:09] <tormod> the question is if the release managers have put on their "manager" hats :)
[10:17] <tepsipakki> well, if the idea was to upload this intermediate version first then they need not to bother.. :)
[10:19] <tepsipakki> ok, new debdiff with bug-closers (?) http://users.tkk.fi/~tjaalton/dpkg/ati/ati.debdiff
[10:22] <tepsipakki> now tv for awhile->
[10:23] <tormod> tepsipakki: so same patches, but with LP links?
[10:25] <tormod>  /(LP: #86072. #144011)/s/./,  (if that matter, not sure)
[10:42] <tepsipakki> oh, right
[10:42] <bryce> too bad we don't have more LP ID's
[10:43] <tepsipakki> well, bug #139241 should be easy :)
[10:43] <ubotu> Launchpad bug 139241 in xserver-xorg-video-ati "DRI hangs on radeon Xpress 200M [1002:5975] " [High,Confirmed]  https://launchpad.net/bugs/139241
[10:44] <bryce> I might suggest rephrasing things a little, so that for instance if patch 02 is a pre-req for another patch that fixes a LP issue, to describe it as "pre-requisite for patch X, which fixes LP NNN"
[10:45] <tepsipakki> sounds good
[10:59] <tepsipakki> I think bug 141547 is another candidate that this version should fix
[10:59] <ubotu> Launchpad bug 141547 in xserver-xorg-video-ati "[Gutsy]  after ati driver update, only a black screen (light is on)" [Undecided,Incomplete]  https://launchpad.net/bugs/141547
[11:00] <tepsipakki> oh, that's fixed already
[11:00] <tormod> 139241 needs a patch though
[11:00] <tepsipakki> yep
[11:03] <tepsipakki> that's also a big strange, since I think he had a different card when he reported that
[11:12] <tormod> I think the pci id list has changed in between
[11:12] <tepsipakki> RS482 is 10025974, RS485 is 10025975 :)
[11:12] <tormod> are you sure?
[11:13] <tepsipakki> yes
[11:13] <tepsipakki> looking at current discover-data
[11:13] <tormod> I saw the same in another bug
[11:16] <tormod> bug #144760 also made me pretty confused with pci ids
[11:16] <ubotu> Launchpad bug 144760 in xorg "compiz/DRI crashes on Xpress200M/AMD64 [1002:5975]  (dup-of: 139241)" [Undecided,Confirmed]  https://launchpad.net/bugs/144760
[11:16] <ubotu> Launchpad bug 139241 in xserver-xorg-video-ati "DRI hangs on radeon Xpress 200M [1002:5975] " [High,Confirmed]  https://launchpad.net/bugs/139241
[11:18] <tepsipakki> ah, ok
[11:18] <tormod> http://launchpadlibrarian.net/9504887/vvnn clearly shows 482=5975 at the time
[11:18] <tepsipakki> yes, maybe that has been since fixed
[11:19] <tepsipakki> so it really is 485
[11:19] <tormod> yes I guess so
[11:19] <tormod> I try to put the confirmed pci id in the summary when I can
[11:21] <tormod> however in the driver source you'll find PCI_CHIP_RS482_5975 !
[11:23] <tepsipakki> lovely
[11:35] <bryce> http://people.ubuntu.com/~brian/testing_graphs/xserver-xorg-video-ati.html - nice to see the big drop over the past week
[11:39] <tormod> tepsipakki: you saw my upstream bug for 139241?
[11:39] <tormod> bryce: yes, I take some of the honour :)
[11:40] <tepsipakki> tormod: yes, that patch should do it?
[11:40] <tormod> tepsipakki: yes it looks simple enough
[11:41] <tormod> tepsipakki: you could ask upstream anyway, why they haven't committed it?
[11:41] <tepsipakki> hmm, alex is not online
[11:45] <tormod> tepsipakki: maybe because there was no upstream reports about RS485
[11:46] <tepsipakki> but that's the one :)
[11:47] <tepsipakki> you just said that the source lists both 5974 and 5975 as RS482
[11:47] <tepsipakki> when in fact 5975 should be RS485
[11:51] <tormod> the source just uses it as macros
[11:52] <tormod> it will report them as ATI Radeon XPRESS 200 5974 (PCIE) and  ATI Radeon XPRESS 200M 5975 (PCIE)
[11:59] <tormod> nobody complained about 5974, so I guess 5974 cards work and 5975 cards fail. Probably all "mobility" versions fail.
[11:59] <tepsipakki> ok
[12:02] <bryce> tormod yes good work!  :-)
[12:02] <tepsipakki> but the point was that 5975 is RS485, and 5974 is RS482 :) so, the source should be updated to reflect that like the current pci-ids :)
[12:02] <tepsipakki> but that's not important now
[12:03] <tepsipakki> I'll mention that in the changelog though..