/srv/irclogs.ubuntu.com/2015/03/11/#ubuntu-unity.txt

=== davidcalle_ is now known as davidcalle
tsdgeosMirv: so Qt 5.4.1 is looking like it can be landed?09:02
Mirvtsdgeos: the ubuntu-keyboard problem was not scary after all, so that was a good thing. we've now new blockers but they are not related to phone so I think I should be able to put the silo forward for QA signoff maybe tomorrow (the qtmir + uitk silos need to land first anyhow)09:06
Mirvtsdgeos: so now it looks like 5.4.1 is a "normal" bugfix release after all, so we should be able to go forward. I've been rebuilding a lot now today in the PPA to get final builds done. gles is also todo still.09:07
SaviqMirv, would it be a good time to backport a thing or two, or would you rather wait?09:07
Mirvtsdgeos: the question is how much time there is before vivid-rtm branches and if 5.4.1 makes it on time to vivid09:07
tsdgeosMirv: right09:07
MirvSaviq: depends. today is a good day to push more builds if you're sure about some patch that is needed. you mean on top of 5.4.1, right?09:08
SaviqMirv, yeah09:08
SaviqMirv, https://codereview.qt-project.org/#/c/103687/09:08
MirvSaviq: yes, mzanetti has given me that already :)09:09
Saviqah ok :)09:09
SaviqMirv, there is also https://codereview.qt-project.org/#/c/107969/09:09
Saviqor we could go for https://codereview.qt-project.org/#/c/103738/ directly09:10
Saviqbut neither is yet merged09:10
tsdgeosSaviq: i'd prefr https://codereview.qt-project.org/#/c/107969/09:12
tsdgeosSaviq: since https://codereview.qt-project.org/#/c/103738/ is not just https://codereview.qt-project.org/#/c/103738/ but all the 5 or 6 leading to it09:12
Saviqtsdgeos, ah, right, and it's getting into 5.4 anyway09:12
tsdgeosyep09:12
tsdgeosi just staged it09:12
tsdgeoshad forgotten it was approved09:12
Mirvtsdgeos: Saviq: ok, so 10796909:22
tsdgeosyeah09:24
=== Malsasa_ is now known as Malsasa
=== MacSlow is now known as MacSlow|lunch
=== alan_g is now known as alan_g|lunch
=== MacSlow|lunch is now known as MacSlow
mterrydandrader, did you never rebase on mine?  I can rebase on yours then13:40
dandradermterry, what branch are you talking about?13:41
mterrydandrader, lp:~mterry/unity8/fix-two-qmluitests and lp:~dandrader/unity8/unifyShellTests13:41
dandradermterry, ah, so you mean that one has to rebase on top of the other so that both can go in the same silo/landing?13:42
mterrydandrader, yeah, that's what I was getting at yesterday.  No worries, I'll rebase13:42
dandradermterry, ah, I didn't get that yesterday13:42
=== alan_g|lunch is now known as alan_g
mterrySaviq, ok resubmitted my qmluitests branch on top of dandrader's, and set to top-approved again14:07
mterrydandrader, could you finish up https://code.launchpad.net/~mterry/unity8/unlock-sim-after-wizard/+merge/251612 ?14:16
Saviqmterry, thanks14:21
SaviqCimi, https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/143081514:21
dandradermterry, sure. somehow I messed your reply14:21
ubot5Ubuntu bug 1430815 in Canonical System Image "grid horizontal scope card has white background" [High,New]14:21
dandraders/messed/missed14:21
mterrydandrader, the reply was not the most satisfying anyway  :)14:22
dandraderSaviq, so what's the fate of silo 006?14:22
Saviqdandrader, waiting for QA sign-off14:22
dandraderhmm14:23
greybackdandrader: got a little time to do a MR? https://code.launchpad.net/~gerboland/qtmir/remove-legacy-notification-support/+merge/25255114:23
dandradergreyback, sure, can do it later today14:23
greybackthanks114:23
dandradergreyback, but it seems mzanetti got it already14:23
greybackdandrader: the MR superseded a much older one which he reviewed. He's not looked at this one14:24
greybackeven though I told LP not to link the old one, it carried over the reviewer14:25
SaviqCimi, it's not clear what the problem is there, can you please find out14:26
Saviqfaenil, meet tsdgeos (if you did not before) - he's our scope master :)14:30
* tsdgeos says hi14:31
tsdgeosfaenil: and welcome14:33
Saviqtsdgeos, faenil just joined the London team as a prototyper14:33
tsdgeosyep saw on twitter ^_^14:33
tsdgeosinternet is an easy stalking machine14:34
mterrydandrader, added comment in unlock-sim-after-wizard14:49
dandradermterry, ok14:49
=== dandrader is now known as dandrader|afk
mterry@unity, is there someone with a spare locked SIM to just give a quick "verified-it-worked" review to https://code.launchpad.net/~mterry/unity8/unlock-sim-after-wizard/+merge/251612 ?15:00
Saviqmterry, /me15:02
mterrySaviq, thanks!  dandrader|afk looked at code already, but you're welcome to do the same  :)15:03
tsdgeosmterry: how hard would it be to make the test of https://code.launchpad.net/~mterry/unity8/cancel-pam-harder/+merge/251174 fail if i remove these lines http://paste.ubuntu.com/10580506/ ?15:08
tsdgeosi.e. if i remove them it passes15:08
tsdgeoswhich i guess it shouldn't, no?15:09
mterrytsdgeos, I would have to add code to verify that all threads are cleaned up at the end of the test.  A valid thing to do, for sure15:09
tsdgeosnot only the threads but also the "responds()" happen, no?15:10
tsdgeosnot sure if that's done together or not15:10
tsdgeosmterry: how hard would it be?15:10
mterrytsdgeos, well the responds cause the threads to go away15:11
mterrytsdgeos, probably not hard, i can add15:11
tsdgeosmterry: cool :)15:11
mterrySaviq, thanks man15:13
tsdgeosmterry: actually from what i can see, in that test no future is ever executed15:17
tsdgeosi.e. i added a debug to authenticateWithPam and it doesn't get there15:18
tsdgeosis it something we may want to add some wait() to get some of the futures getting in it?15:18
mterrytsdgeos, or maybe a second test for that specific bit -- that first test was just to make sure we could even handle quick cancels without side effects (like crashing)15:19
tsdgeosok :)15:19
mterrytsdgeos, huh, on your machine you don't even get to authenticateWithPam?  I definitely do here, but that may be machine-specific15:20
SaviqCimi, oh? so the "scrolls to top-left" is still an issue with your branch?15:20
tsdgeosmterry: on that test?15:21
mterrytsdgeos, testing threads is not my favorite sport  :)15:21
CimiSaviq, yes15:21
mterrytsdgeos, yeah15:21
Saviqmeh15:21
CimiSaviq, that branch is fixing the animation15:21
CimiSaviq, not the zoomable image bug15:21
mterrytsdgeos, or maybe i only did when I had print statements sprinkled throughout  :)15:21
tsdgeosmterry: yeah i don't15:21
CimiSaviq, I am looking now at the card summary bug, then that15:21
tsdgeosi did add qDebug() << "MOOOO"; just to the first line of authenticateWithPam15:22
SaviqCimi, ah now I get it, ok15:22
mterrytsdgeos, I think I'll end up having to put some #ifdef debugging code that will have pieces of the code block.  that way I know I'll be testing the right segments15:23
mterrytsdgeos, but that might be more involved.  Can I make ya a deal?  I'll add the code to check that all threads are cleaned up in this MP now.  But the more intense #ifdef, blocking, synchronizing etc code can be a separate MP?  Which I will put on my todo.  I just don't want to block the crash fix on testing nirvana15:25
tsdgeosmterry: sure15:25
tsdgeosi'm still unhappy about the process events though15:26
tsdgeosbut oh well15:26
tsdgeosmy idea was15:26
mterrytsdgeos, oh hm15:26
tsdgeoswell not idea15:26
tsdgeoswhat i implement15:26
tsdgeoswas15:26
tsdgeosa connect with a lambda15:26
tsdgeosbut then the lambda code was never executed15:26
tsdgeosand then the test still passed15:26
tsdgeosand that's where i decided to back off :D15:26
mterrytsdgeos, :)  when debugging myself, I had qDebug() lines everywhere, in parent and child thread.  And that must have made it more likely that I hid different speeds in the two threads15:27
mterrytsdgeos, a lambda would help because you have the pam_handle in your closure.  But the "this->futures" data is also thread-specific15:28
mterrywould need to fold that into the closure too15:28
=== dandrader|afk is now known as dandrader
greybackpaulliu: http://bazaar.launchpad.net/~phablet-team/platform-api/trunk/view/head:/src/ubuntu/application/testbackend/ubuntu_application_sensors.cpp15:41
greybackpaulliu: you've seen this code, it injects raw input events which platform-api test backend will receive and send up the stack: https://code.launchpad.net/~canonical/unity8/fake_platform_sensors_module/+merge/24733415:43
paulliugreyback: yes. But that doesn't works good. So I'll need to dig into.15:45
CimiSaviq, ping15:45
CimiSaviq, https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/143081515:45
SaviqCimi, pong15:45
greybackpaulliu: ok15:45
ubot5Ubuntu bug 1430815 in Canonical System Image "grid horizontal scope card has white background" [High,Confirmed]15:45
Cimi"category-layout": "horizontal-journal",15:45
SaviqCimi, I think it's more than that15:45
CimiSaviq, in CardCreator, we consider horizontal just template["card-layout"] === "horizontal";15:45
SaviqCimi, per design, if you have art and summary, you have a background15:45
CimiSaviq, for vertical, yes15:46
CimiSaviq, not for horizontal15:46
SaviqCimi, well, yeah, but that's a vertical card15:46
CimiSaviq, I am wondering if they expected the horizontal-journal to be horizontal15:46
CimiSaviq, but they say "grid horizontal scope card"15:47
SaviqCimi, they only have a single item in that category15:47
SaviqCimi, I expect they wanted vertical-journal, to not have the blank white at the bottom15:47
SaviqCimi, but I can't see anything wrong with that - per design we force a background if you have a summary15:48
CimiSaviq, yeah16:00
CimiSaviq, if we have both summary and art, always background16:00
Cimihttps://docs.google.com/a/canonical.com/document/d/1n880Fih5KyGPcoP5chidnHDG_8TxXUgSuij7f4rHpuk/edit#16:00
Cimi"Cards are automatically placed within an ubuntu shape when any of the cards in that category contain a summary and an art. "16:00
SaviqCimi, sounds like we don't have that implemented too well (because it didn't say that before)16:01
Saviqor well, we can only assume there will be a summary if the scope declared it16:02
Saviqso yeah16:02
Saviqwe do that16:02
mterrytsdgeos, OK.  I've added a check at the end of the test for the thread count.  But when testing it, I didn't trigger its failure even if I removed that processEvents block.  I had to add some qDebug statements to actually slow down the parent thread enough to trigger the new failure.  So it's still a valid test, but not necessarily being hit.  For that, we need to intentionally slow down the parent thread in specific points.  Which needs the wh16:06
mterryole #ifdef bits and some more tooling.  I didn't realize how bad a test I'd made because I was always testing with prints  :-/  How about I promise to not only revisit the test situation, but re-examine the explicit calls to processEvents16:06
tsdgeosmterry: sure :)16:07
=== seb128_ is now known as seb128
tsdgeoscan anyone reproduce the Dash::test_close_temp_scope_preview_opening_scope failure?16:47
tsdgeosit's pretty consistent in CI16:47
tsdgeosbut i can't seem to get it here16:47
greybackMirv: hey, you aware of QtCreator crashing with a multimonitor setup and you unplug the monitor that QtC instance is on?16:48
Saviqtsdgeos, I had the 8 failures CI reported, lemme see16:50
tsdgeosSaviq: 1 is fixed in one branch of mine, 5 in one of mterry16:50
tsdgeosbut there's 2 in the dash i can't repro16:50
tsdgeosbut since one is atyend16:50
tsdgeosi'll use the same trick i used in the other one16:51
tsdgeosand see if CI is happy16:51
Saviqtsdgeos, it felt like a candidate for putting in a function, too16:51
tsdgeostotally16:52
tsdgeosbut first let me see if i can make it pass in CI16:52
tsdgeosand then we'll make it prettier16:52
Saviqetoomanytests16:53
tsdgeosyeah16:53
tsdgeosrunning qmluitests takes ages nowadays16:53
Saviqtsdgeos, yeah, can't get it to fail after all16:57
tsdgeoslet's see what CI has to say16:57
cheekoliis there a way to show the unity workspace switcher from within a script? I am working on changing the count on the fly--its all working currently, except when i run it (with a keyboard shortcut) i'd like to pop up the workspace switcher so i can see the current count of workspaces17:08
cheekoliSaviq, thanks for your help yesterday... got it working :)17:09
cheekolithe trickiest part was getting the script to connect to the right display session... luckily i'd been down that road and already had a script for it :)17:11
Saviqcheekoli, I think you just need to inject <Super>+s17:16
Saviqcheekoli, there's no other entry point to get into the spread I don't think17:17
=== dandrader is now known as dandrader|lunch
cheekolithanks for the advice again, seems to work17:45
=== alan_g is now known as alan_g|EOD
dandradermzanetti, you there?19:22
mzanettidandrader, what up?19:23
dandradermzanetti, is it know/expected that it takes two taps/clicks in order to switch focus between windows?19:23
mzanettidandrader, neither19:24
dandradermzanetti, first tap unfocus the previous. second tap focus the new19:24
mzanettidandrader, this used to work. seems a newish issue19:24
dandradermzanetti, that's with shellRotation branch. don't know if other are needed on top ofit19:25
dandradermzanetti, also, this is in make tryOrientedShell. so maybe it only happens there, which would be odd19:25
mzanetticompiling trunk19:29
mzanettidandrader, seems broken in trunk too19:34
dandradermzanetti, ok19:34
dandraderman, playing with the qml tests in a touch screen opens a new dimension, as you can interact with them with actual touch events, not having to emulate them out of mouse input19:36
dandradermzanetti, it might be a clue that you can also drag windows along on when you the first press19:38
dandradermzanetti,  *when you first press them (ie, when they're not focused yet)19:38
mzanettidandrader, yeah... could be19:39
=== dandrader is now known as dandrader|bbl
spaceindaverHi all, I installed the latest nvidia drivers (340) and nvidia-prime (for switching graphics cards on an optimus laptop) and now every time I boot unity fails to start after I log in. I can get it to run again if I delete my .config directory. Any idea what could be causing this?21:40
=== dandrader|bbl is now known as dandrader

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!