[09:23] mzanetti: you could reproduce the bug with the dash contents being empty until closed again on the desktop? [09:23] yes, 100% [09:24] mzanetti: on unity7 too or just on unity8 as a session? [09:24] just unity8 [09:24] k [09:24] so i'll have to sort that first if i'm supposed to work on the bug :D [09:25] first back to filters [09:25] right... strange it won't work for you [09:25] tsdgeos, but yes, sooner or later you'd need to get that sorted anyways. [09:25] actually it's very funny [09:25] since it throws an exception once i log in inside unity8 [09:25] so unity8 and stuff is already up [09:26] mzanetti: honestly i'm not very keen on going to debug why mir decides to throw expcetions up [09:26] but oh well [09:59] tsdgeos, it must be some setup issue on your machine I think [10:00] mzanetti: i don't knwo i almost removed and reinstalled everything regarding unity8 and mir yesterdya and the same [10:00] i am not sure it may be something lib related [10:01] but maybe [10:01] hmm [10:01] and the exception i get is a runtime one with unity8 running already [10:02] one would think that it it was a lib mismatch it'd fail to start altogether === vrruiz_ is now known as rvr === dandrader is now known as dandrader|bbl [13:19] Ç/back [13:19] wops [13:26] do we have any MR removing this? [13:26] ./Stages/DesktopStage.qml:166: onVisibleChanged: console.log("VISIBLE", model.appId, visible) [13:26] mzanetti: ↑ ? [13:27] tsdgeos, not that I know, but there's chances ltinkl has one [13:32] tsdgeos, yup, it's gone in my new decorations branch [13:32] k [14:08] ltinkl, welcome back :) [14:09] ltinkl, we had the meeting yesterday, only briefly talked about oobe, but looks like mostly they want spacing changes like making text lines taller -- i.e. more spacing between and trying to wrap text lines better [14:09] mterry, I explained in the review document this is not possible to do... sigh did they read it? :) [14:09] ltinkl, I've updated our PPA to be a bit closer to landing-ready. I've made it vivid+xenial. And added a couple other packages associated with my edge intro changes [14:10] ltinkl, oh I talked to them [14:10] mterry, cool, thanks for that [14:10] ltinkl, both seem possible. What's the problem? Don't we have a Text.lineHeight property? [14:10] mterry, they want to alter the linespacing, which isn't possible in QML [14:10] ltinkl, and couldn't we have an invisible Text that we know how long the label width is, so we know where to set its wrap width? [14:10] ltinkl, isn't that Text.lineHeight? [14:11] mterry, hmm right... maybe, will try [14:13] ltinkl, they also mentioned that some account screen they didn't want was still in there [14:13] ltinkl, but then they mentioned that there was some newish requirement to keep the "admin password" (new name for the sudo password) [14:14] ltinkl, I pushed back a little on that [14:14] ltinkl, as you can see in the email -- tried to figure out where that was coming from. It wasn't actually coming from security team, so I dunno why it's a requirement [14:15] mterry, yeah the account screen is still there as I was waiting for the final decision whether it's still needed or not [14:17] mterry, sent an email, let's see [14:32] ltinkl, oh also, I had to disable tests in my branch because your branch failed them. At the least for old imports (non-1.3), but maybe others? [14:32] ltinkl, though I don't think the PPA runs the full qmltest suite [14:33] ltinkl, let me know when you fix that and I can take out the disable line in mine [14:38] mterry, yeah the tests are not fully in shape yet [14:38] ltinkl, that's fine for the qmltests (mine aren't either). But the import-checker tests runs during build [14:38] ltinkl, so the PPA was ftbfs [14:38] ltinkl, so please fjix that at least (it was from your merge from trunk) [14:50] mterry, do you remember what was it failing at? [14:50] ltinkl, yeah bad imports (non-1.3 / qt5.4) [14:51] ltinkl, make tests should show the failure [14:51] mterry, hmm it passes here [14:53] ltinkl, uh I meant "make test" but if that still passes... good? I can remove the test-comment-out-lines [14:53] mterry, hmm that doesn't, a sec [14:53] k === dandrader|bbl is now known as dandrader [14:58] mterry, heh, interesting failure, it chokes on "import Ubuntu.Components.Popups 1.0" [14:58] mterry, the regexp is too greedy [15:00] ltinkl, no, your import should be 1.3 [15:00] mterry, ok, that works [15:01] mterry, I thought this component wasn't bumped [15:03] mterry, alright, pushed the fixes, make test passing [15:03] ltinkl, nic [15:03] e === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader [18:50] dandrader: mzanetti: Any luck on reproducing the dual cursor on Unity 8 desktop? bregma was just able to reproduce. [18:50] ChrisTownsend, dandrader said he couldn't. I didn't find the time to try yet [18:50] ChrisTownsend, no. moved on to work on something else [18:50] let me try now [18:51] mzanetti: dandrader: Ok [18:52] dandrader, hmm... interesting... [18:53] dandrader, so I started gedit, had just one cursor. then I clicked into gedit's menu, the cursor got stuck there and from the top left the second one appeared [18:53] mzanetti, oh, don't do that! [18:53] dandrader, interesting thing is that the second cursor that appears is much faster than the first [18:53] mzanetti, we don't support menus yet [18:53] right [18:53] mzanetti, if will cause a new surface to be created to hold that menu. unity8 should blow up [18:53] mzanetti, s/if/it [18:54] ChrisTownsend, hey, if I see gedit's window decoration, does that mean it runs in libertine? [18:54] I see it when I click inside the gedit window. [18:54] mzanetti: No, not libertine at all. [18:54] mzanetti, gedit is drawing its own window decoration I think. from window manager's point of view it's a chrome-less window [18:55] mzanetti, or should I say GTK [18:55] mzanetti, another todo item: support "frameless" window hint or something like it [18:56] Just clicking inside the gedit window will summon the second cursor. [18:56] had to reboot :D [18:57] ChrisTownsend, hmmmm.... so it's not jsut by running gedit, like the bug report said [18:58] just clicking inside the text editor doesn't get it for me [18:58] dandrader: No, I think I made a comment in the bug that entering the window will cause the second cursor to appear, but I think actually clicking in the window is what triggers it. [18:58] I can select text etc, all fine [18:58] mzanetti: You don't have a second cursor? [18:59] ChrisTownsend, I think Unity8 developers are immune to this bug :) [18:59] ChrisTownsend, not unless I click a menu [18:59] dandrader: lol, you guys! [18:59] mzanetti: Hmm [18:59] I can repro it tho with the menu... [18:59] unity doesn't immediately blow up, it gets me the second cursor... doing some more clicks it eventually blows up then [19:00] Actually, this time, just entering the gedit window brought up the 2nd cursor. [19:09] ChrisTownsend, could it be that it tries to open some tooltip or something? [19:09] mzanetti: No, I don't think so. I just move the regular cursor into the window and move it and then the 2nd appears. [19:11] hmpf... nope, not happening here [19:12] mzanetti: I don't understand.:-( [19:12] mzanetti: I also see this using Vivid+overlay. [19:13] http://i.imgur.com/HfkVqiq.jpg [19:13] I can select text with the mouse just fine [19:14] mzanetti: Hmm, that kind of looks like the original cursor provided by Mir and not the new Unity8 cursor that is larger and fuzzier. [19:14] no, it's the slow one [19:14] high-dpi screen here [19:14] mzanetti: Ah, ok:) [19:15] mzanetti: Are you using a mouse or touchpad? [19:15] ChrisTownsend, speaking of which, can we scale gedit/gtk somehow? [19:15] touchpad [19:15] mzanetti: I'm sure it can be, but I'm not sure how. [19:15] mzanetti: Ok, I'm using touchpad as well. [19:16] I'm on v+o too, daniel is probably on x [19:18] mzanetti: Well, I'm stumped as to why you guys don't see it, but I know of at least 4 different machines that get this issue. [19:18] mzanetti: As dandrader said, I guess you guys are immune. [19:19] ChrisTownsend, how are you running it? starting a session from lightdm? unity8-desktop-session-mir? [19:20] mzanetti: Yes, unity8-desktop-session-mir and using lightdm to login. All packages from the archive. [19:20] same here :/ [19:24] mzanetti: Hmm, something weird. I had my mouse over the window and was moving it slowly and didn't see the 2nd cursor. Then as I was moving it, it showed up on the edge of the window as if it became visible all of a sudden and then stayed visible. I wonder since you're on hi dpi if you keep moving the cursor around until the hidden cursor hits the window. [19:28] mzanetti: dandrader: What code tells Mir to hide it's cursor? [19:29] (I guess it's Mir cursor) [19:29] ChrisTownsend, it's in qtmir [19:29] dandrader: ok [19:30] ChrisTownsend, it's kinda workaround. Mir is buggy when its comes to cursor visibility [19:31] ChrisTownsend, grep for 1502200 [19:31] ChrisTownsend, (it's the bug number associated with the issue) [19:31] dandrader: Ok, will do, thanks [19:32] ChrisTownsend, and the fix (new api for wrapping mir cursor) is also buggy [19:32] I'm not on a high DPI screen when I see the second cursor [19:33] bregma, screen DPI should be orthogonal to this issue [19:33] the supernumerarary cursor looks like a hardware cursor [19:34] maybe GTK is turning that on directly (it likes to take control) and Unity 8 only does software cursors [19:35] bregma: I do get the issue when running X apps as well like LO and FF. [19:36] ChrisTownsend, on Unity 8? Don't those apps use GTK back ends where possible? [19:37] bregma: I mean in a Libertine container, although I want to be clear that Libertine is not the culprit. [19:41] I think screen resolution/DPI does have an effect on when the Mir cursor actually hits the gedit window. [19:42] It's not the cause of the issue, only it hides the issue from occurring. [19:43] Probably something in Mir that says show the cursor over these types of windows. [19:59] ChrisTownsend, thing is, mir has no idea of what's going on in the unity8 qml scene [20:00] ChrisTownsend, unity-system-compositor only knows that it's (hidden) cursor is over the unity8 surface, which takes the entire screen [20:01] ChrisTownsend, the hardware cursor (that little bugger that pops up) is controlled by unity-system-compositor [20:01] dandrader: Ok, thanks for the explanation. [20:04] dandrader: Hmm, doing a quick look through u-s-c code, I don't see any calls to hide()/show() methods for the cursor. Would there be other method names that do the same thing? [20:09] ChrisTownsend, I don't know that code. But I would think it's all in libmir itself [20:09] ChrisTownsend, ie, Mir [20:09] dandrader: Ok [20:10] ChrisTownsend, it can be confusing. Because qtmir/unity8 uses libmir's server API, but it's in reality running as a nested server. It, from u-s-c perspective it's just a client application/surface [20:11] dandrader: Yes, very confusing:) [20:11] ChrisTownsend, so in the nested server code paths you have server API's calling client APIs behind the scenes to talk to unity-system-compositor [20:12] ChrisTownsend, and that pretty much explains why the cursor API works so badly in a nested server [20:12] dandrader: Sheesh, that's kind of messed up. [20:13] ChrisTownsend, I mean, it makes sense. but must be hell to implement :) === dandrader is now known as dandrader|afk [20:28] dandrader|afk: mzanetti: Rebuilding lightdm to disable "--enable-hardware-cursor=true" in it's call to unity-system-compositor no longer brings up the hardware cursor. Not sure what the side effects of that is. [20:31] yeah... I guess if it always loads all the things this can quickly become too memory consuming [20:31] wrong chat :D [20:32] ChrisTownsend, interesting. so when you see both cursors, does it still work fine? it's just a visual thing? [20:33] mzanetti: The Unity 8 cursor is the one that works, the hardware cursor does not. [20:33] mzanetti: I'm going to talk to robert_ancell about removing the hack in lightdm. === dandrader|afk is now known as dandrader [20:52] ChrisTownsend, interesting === ahoneybun is now known as ee === ee is now known as ahoneybun [22:42] hello