[08:55] Cimi, morning! did you have a chance to test fix-temp-scopes branch of shell plugin? [09:12] Saviq: so what do we do with https://code.launchpad.net/~ted/unity8/delay-indicator-start/+merge/241124 ? ask ted for improvements? approve? discard [09:12] ? [09:13] Cimi: what's missing for a top approval in https://code.launchpad.net/~mterry/unity8/tutorial-refactor/+merge/239874 ? [09:15] tsdgeos, I think we can discard, will talk to Ted later today [09:15] oki [09:26] pstolowski, all looks fine [09:26] thanks :) [09:27] tsdgeos, I need to re-review the latest changes [09:27] tsdgeos, it was on hold for design [09:27] i see [09:30] seb128, bug #1415141 and bug #1417773 [09:30] bug 1415141 in unity8 (Ubuntu RTM) "Dash frozen while the rest of unity8 still functional (can't change scopes)" [Undecided,New] https://launchpad.net/bugs/1415141 [09:30] bug 1417773 in unity8 (Ubuntu RTM) "Unity8 completely frozen (unable to unlock, receive calls, etc)" [Undecided,New] https://launchpad.net/bugs/1417773 [09:32] Saviq, not sure, have a "t a a bt" rather than "bt" would be more useful [09:32] rsalveti, ^ [09:32] mine had libqnmbearer.so in the bt [09:32] https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1417525 btw [09:32] Launchpad bug 1417525 in telephony-service (Ubuntu) "Unity8 desktop lockscreen hangs on ofono issues" [Undecided,New] [09:38] tsdgeos, hey [09:38] tsdgeos, about lp:~dandrader/unity8/indicatorsBarEatsAllInput [09:38] tsdgeos, you mean that you open the indicators (on a tablet) [09:38] tsdgeos, then tap several times on the greyed out area [09:38] tsdgeos, the first tap will make the indicators panel close [09:38] no no [09:39] not the greyed out area [09:39] the top bar [09:39] tsdgeos, and the subsequent ones will make the foreground app blink [09:39] basically if you press just in the between of the top bar and the greyed area [09:39] but since that's hard that i do is start pressing in the middle of the top bar and then go slowly done [09:39] down [09:39] so eventually i get to the right place [09:40] greyback, https://launchpadlibrarian.net/196557582/buildlog_ubuntu-vivid-amd64.unity8_8.02.4%2Bbzr1570~ubuntu15.04.1_FAILEDTOBUILD.txt.gz [09:41] dandrader: does that make sense? or want a video? [09:44] tsdgeos, video [09:44] tsdgeos, but its it the same thing as what I explained? do you also get this issue? isn't it the same thing? [09:44] it is the same thing [09:44] tsdgeos, like just tapping in the center of the greyed-out area [09:45] there's just one pixel instead of whole area from before [09:45] tsdgeos, so what you're hitting is just the very edge of the greyed out are I guess [09:45] guess so yes [09:45] tsdgeos, its very first, top, row of pixes [09:47] dandrader: let me try to record the video [09:54] dandrader: it's uploading, will tell you once my poor upload link is done [09:56] dandrader: https://www.youtube.com/watch?v=zfsdVA1ZyC8 [10:02] tsdgeos, would you get the very same behavior (and bug) if you tapped right in the middle of the app area not covered by the indicators bar? [10:03] you mean "over the app"? [10:03] tsdgeos, yes [10:04] no, over the app is fine [10:04] just hides the indicators and that's it [10:04] tsdgeos, weird. that's not what I get [10:05] tsdgeos, even if you tap fastly, multiple times ? [10:05] ah you're right, it does happen ^_^ [10:05] * dandrader wonders if the bug is more evident in the shellRotation branch... [10:05] so it's not just one pixel, it's just pressing fast two times [10:06] so you're right this may be a different bug [10:06] tsdgeos, so it's the indicator's darkened area that lets input go through while the closing animation is playing [10:06] dandrader: do you want me to check if this happened before and we treat it as a different bug or want to fix it together? [10:07] tsdgeos, also the flicker is more evident if you have only unity8-dash running [10:07] tsdgeos, as it will flicker between the white dash ui and the black background [10:08] lol yeah [10:09] duflu, dandrader http://doc.qt.io/qt-5/qml-qtquick-propertyanimation.html#easing.type-prop [10:09] tsdgeos, so will you approve the branch then? :-) [10:10] dandrader: sure i'll have another look and open a separate bug for the other thing [10:10] tsdgeos, ok, thanks! === snadg3 is now known as snadge [11:29] damn this internal compiler error [11:29] Saviq: i guess it's making us unlandeable? [11:29] tsdgeos, yes [11:29] tsdgeos, people are working on it [11:29] :/ [11:29] :) [12:01] Cimi: ping [12:02] Cimi: unping [12:02] tsdgeos, lol === marcusto_ is now known as marcustomlinson_ [12:19] tsdgeos, https://code.launchpad.net/~cimi/unity8/fix-open-new-scope-from-tmp/+merge/248538 [12:20] * tsdgeos clicks the button === Cimi_ is now known as Cimi === MacSlow is now known as MacSlow|lunch === marcustomlinson_ is now known as marcustomlinson [12:40] larsu, just so you know https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1385331/comments/9 [12:40] Launchpad bug 1385331 in Canonical System Image "Notification LED stays on when no messages in notification center" [High,In progress] [12:40] thanks === alan_g is now known as alan_g|lunch [13:20] @unity: I've a workaround for the armhf compile error, want to just check it in to trunk so that no one has to wait, any opposition http://paste.ubuntu.com/10053410/ ? [13:21] +1 [13:21] Saviq, +1 [13:21] Saviq, make sure you don't have tags ;) [13:21] mterry, ;) [13:21] mterry, I actually do (thanks to colo), but I'll strip them right after [13:23] @unity: we're back in (unity8 on armhf) building business [13:23] nice [13:40] olli, FYI, got a workaround from doko+slangasek for the unity8 build issue, we're unblocked [13:40] saweet, what was the issue? [13:40] sumding in the toolchain? === Malsasa_ is now known as Malsasa [13:40] Saviq, ^ [13:41] olli, yeah, new gcc release [13:42] olli, would've known that yesterday already if I realized that silos have proposed enabled (and I was having trouble reproducing, because the new gcc was in proposed still, is moved to release now) [13:42] s/realized/remembered/ [13:46] Saviq, thx [13:46] * olli takes notes === alan_g|lunch is now known as alan_g === MacSlow|lunch is now known as MacSlow === Malsasa_ is now known as Malsasa [14:43] MacSlow, Hi! [14:43] om26er, hey there [14:43] MacSlow, is there a way to disable the OSD during testing ? [14:44] om26er, the tests themselves or the daemon? [14:44] I am trying to fix an Autopilot test for messaging-app and the notifications block the searchbar [14:44] MacSlow, the daemon [14:45] om26er, hm... [14:46] om26er, can you recompile? [14:46] MacSlow, ahm, no the tests are supposed to run on production [14:47] MacSlow, can't I just stop the notifications service ? [14:47] om26er, that would probably be the best idea [14:47] but it's a plugin in unity8... [14:48] om26er, so it's different from the regular (old-school) desktop notify-osd [14:48] MacSlow, right, I'll try to find other solutions then. [14:48] om26er, wait there's a way... once sec [14:50] great :) [14:51] om26er, hm... getting rid of /usr/share/dbus-1/services/org.freedesktop.Notifications.service (move it some where else) and restart dbus [14:51] om26er, I think that should do the trick [14:52] om26er, wait... [14:54] om26er, the first idea just disables (old) notify-osd... [14:54] om26er, I imagine you're talking about an automated, reliable way to do this? [14:55] Saviq, I'm wondering if one can disable a single unity8 plugin at runtime [14:55] MacSlow, I'd say that's the wrong direction [14:55] Saviq, yeah, something like that. Perhaps a gsetting key or some kind of thing [14:55] om26er, that sounds like we want an autopilot emulator for notifications, where you can actually verify the notification is showing up, and wait for it to close (or interact with it) [14:56] Saviq, I know of nothing in unity-notifications that would allow it being disabled at runtime... just uninstaling it, but that's not an option for om26er's needs [14:56] Saviq, that can take a while in cases where we rush 5-6 notifications together. But yes, sounds like a solution in the end. [14:57] initctl stop unity8-notifications :D *dreams* [14:59] om26er, but you want something that works for now right [15:00] MacSlow, indeed. [15:00] Saviq, I guess that "initctl stop unity8-notifications" is another bullet-point on the nice-to-have list then?! [15:03] MacSlow, not really, we don't (and I don't imagine we will) have a notification daemon [15:04] om26er, that helper might have an option to disable it for a while if you need it [15:04] Saviq, well in the long run... but currently we kind of still have [15:04] om26er, or just "consume" them all as they come in [15:04] MacSlow, no, it's part of the shell [15:05] om26er, btw... you just want them to now show up (and block input to surfaces below), right? [15:05] s/now/not [15:05] MacSlow, and it will remain that, even if we'll get the post office in between [15:05] in which case it might be possible to stop the post office, but that still feels like the bad solution to me ;) [15:06] Saviq, yes I think if we can disable it for a few seconds our purpose will fulfill [15:06] MacSlow, exactly. [15:06] om26er, if you don't care about the process, couldn't you just prepare the history db before starting the test? [15:07] Saviq, thats one option I was going to look into. [15:07] or create messages before the app starts. [15:08] om26er, I think there's other, better solutions for this issue indeed :) [15:10] om26er, I currently can't think of a way to disable the notifications without messing around with the sourcecode. [15:11] MacSlow, that's fine, I'll discuss with the messaging-app devs for a solution at the history service's end. [15:11] om26er, one could change the dbus-interface name and recompile unity-notifications... or - on the unit8-side/QML - make the notification-renderer swallow all notifications [15:12] om26er, sorry for the touble [15:36] MacSlow, has there been a design review of swipe-to-dismiss? [15:37] Saviq, yes... that happened looong ago [15:38] * Saviq hopes that we'll get the ability to dismiss sds just as well (i.e. dismiss, not reject, in terms of an incoming call) [15:39] Saviq, an expanded snap-decision can't be dismissed (closed)... that's by design... collapsed snap-decisions can though [15:39] oh ok [15:40] Saviq, and that's also covered in the qmltest for them [16:07] tsdgeos, how do I get rid of this silliness? paste.ubuntu.com/10055796/ [16:08] export LC_ALL=C ? [16:08] it's the most diehard qmltest failure we have [16:08] * dandrader tries [16:08] or en_US [16:08] or something don't remember [16:08] i usually just run with -i -k [16:08] and then serach for the fail! and if they're this i ignore them :D [16:09] lazy man [16:16] MacSlow, testNotifications fails for me fairly often: http://paste.ubuntu.com/10055920/ [16:16] (the new one) [16:17] MacSlow, looks like that failure https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-vivid/360/testReport/junit/%28root%29/qmltestrunner/NotificationRendererTest__test_NotificationRenderer/ [16:17] Saviq: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1411748 doesn't affect rtm since the code it's fixing is not part of rtm (or wasn't last time i checked) [16:17] Launchpad bug 1411748 in unity8 (Ubuntu) "[Arale] News aggregator scope has a white scope background in cards" [Critical,In progress] [16:18] tsdgeos, hmm hmm... news scope on arale, though, not there outside of rtm? [16:18] arale is vivid-based i've been told [16:18] tsdgeos, ok then I've no way to see that bug [16:19] Saviq: why not? just install vivid on a krillin? [16:19] and well, there is an rtm channel for it (I'm using... trying to...) [16:19] tsdgeos, no news scope [16:19] or is there? [16:19] Saviq, yeah... I will look into that. [16:19] don't think there is [16:19] maybe not [16:19] Saviq: what i did was just get krillin rtm, add the patch that breaks this and then add the patch that fixes it [16:20] ^_^ [16:20] tsdgeos, ;) [16:26] kdub: libevdev2 libmirplatform6 libmirserver29 mir-platform-graphics-android mir-platform-graphics-mesa [16:26] sorry... should have been kgunn.. [16:26] :) [17:12] Saviq, qtmir update in vivid today? ;-) [17:12] I could use a working desktop daily tomorrow [17:13] seb128, out of my hands, camako and racarr are landing new mir with qtmir now... [17:13] k [17:13] seb128, let me know if you want just a fixed qtmir package [17:13] well, depending when the other set lands [17:14] I would like to see the gtk fix to land this week [17:14] it would make some of our testing/work easier [17:14] up to you what form that landing takes [17:15] seb128, I'll find out how the guys are doing and land it myself if needed, before the end of the week [17:15] thanks === alan_g is now known as alan_g|EOD [18:24] I am using Unity on ubuntu, since I am more a terminal user than a gui-user. No I wonder what desktop environment is best for people who prefer to use a mouse and a gui interface? === mterry_ is now known as mterry [23:39] Is anyone familiar with what differences exist between tryTest and testTest? I've got this problem where a DirectionalDragArea isn't working in testTest but does in tryTest... :(