=== Guest12534 is now known as jacky === jacky is now known as jalcine === _salem is now known as salem_ === salem_ is now known as _salem === duflu_ is now known as duflu === iahmad_ is now known as iahmad|afk === iahmad|afk is now known as iahmad [09:42] mzanetti, you fine if I answer to your latest reply publicly. Seems like you only sent it to me instead of the list === tvoss is now known as tvoss|test === tvoss|test is now known as tvoss [10:10] Saviq: damn, my 5 lines patch fixes https://bugreports.qt-project.org/browse/QTBUG-30730 and https://bugreports.qt-project.org/browse/QTBUG-34617 but not https://bugreports.qt-project.org/browse/QTBUG-34651 [10:10] i'll have a look at that one too [10:17] tvoss: oh... yeah, that wasn't intentionally [10:18] mzanetti, ack, can you resend publicly, will answer then [10:19] tvoss: done [10:25] tsdgeos, oh interesting... [10:25] yeah [10:25] similar but not same thing [10:25] tsdgeos, 1 != 1?... [10:25] yep [10:25] kind of [10:25] it probably tries to compare the wrapper against the object or something? [10:25] yeah [10:26] need to find out a comparison that works and then fix this one to go there too :D [10:26] ;) [10:51] Cimi: ping [10:57] woa, adding a debug in qv4runtime_p.h wasn't a good idea :D its recompiling almost everything :S === _salem is now known as salem_ [11:14] Cimi: https://bugs.launchpad.net/unity8/+bug/1250815 [11:14] Ubuntu bug 1250815 in Unity 8 "Carousel click/pressAndHold not working" [Critical,New] [11:36] mhr3, any reason why lp:unity-scopes-shell source package is unity8-plugin-scopes? why can't it be the same name? [11:37] mhr3, also, qtdeclarative5-foo-plugin is the preferred name for QML plugins [11:37] mhr3, OTOH we might want a different naming, 'cause it's meant to be installed in a different import path... [11:38] didrocks, thoughts ↑? where should we install plugins directed at the shell? [11:38] and whether to change the package naming scheme? [11:38] Mirv, I'd like your opinion, too ↑ [11:39] the source package needs to match the project name [11:39] for non confusing reason :) [11:39] are those only unity8 plugins? [11:39] it's not in the standard QML import path? [11:40] Saviq: the preferred naming is actually qtdeclarative5-foo0.1, as decided by kenvandine & co, so that also the install path contains the API version specific path - see for example qtdeclarative5-friends0.2 [11:40] Saviq: the idea is that one can co-install older API package as well, for example than that was released with 13.10 [11:40] (I decided that one actually :p) [11:41] didrocks, yeah, we want to put them on a unity8- (well, shell-) specific path [11:41] didrocks, so that apps don't have access there [11:41] maybe it shouldn't follow that naming scheme then [11:41] didrocks: oh, I never figured out how the decision process went, I only heard the end result :) [11:41] Saviq: will it follow your virtual unity-apis versions? [11:41] didrocks, yes [11:42] so I would say unity8.--plugin [11:42] hoping that one day we can make 8 and API version matching :) [11:43] didrocks, there's no one global API version, though... [11:43] didrocks, or what is that APIversion meant to be? [11:44] didrocks, I mean scopes have different API version than notifications, for examlpe [11:44] as we didn't want people to have to bump if changes were unrelated [11:44] Saviq: well, as long as you are backward compatible [11:44] we should really use semantic versionning [11:45] and "integrating with the shell" is just one version [11:45] being scope or integration with the launcher or indicators [11:45] didrocks, yeah, we're not backwards compatible, remember? ;P [11:46] Saviq: I know… ;) [11:46] didrocks, what would APIversion be, then? unity-api version number? [11:47] when do you think you will ensure backward compatibility? [11:47] that can maybe help shaping the versioning [11:57] didrocks, backwards compatibility of Unity8 with older API versions? [11:57] didrocks, not until 16.04 :P [11:58] didrocks, those are not APIs public enough that it warrants backwards compat for quite some time [12:01] Saviq, i knew the naming will be the primary thing of discussions :) [12:01] anyway, i don't care, just tell me what to change it to [12:02] didrocks, but we'll need to push the scopes plugin as a separate pkg to the distro [12:02] ideally asap :) [12:03] Saviq, though i guess we should bump unity8 minor/micro version [12:04] and then make the scopes plugin break unity8 << that_version [12:04] mhr3, yeah probably [12:10] Saviq: so I would say, let's version it to 0 and handle the breakage manually [12:11] everytime you break the API, you Breaks: all components << version [12:11] didrocks, so, unity.0-scopes-plugin in that instance? [12:11] (I wouldn't want to put the 8 in there) [12:11] Saviq: unity0 then [12:12] no . [12:12] didrocks, Mirv how about the path where we install shell-facing plugins? [12:12] Saviq: same concept to me? [12:12] all unity0- something [12:12] then, the patch itself [12:12] path* [12:13] "unity0-scopes-plugin" [12:13] should be libexec I guess [12:13] looks wrong :P [12:13] yeah, /me no likes either :/ [12:13] mhr3: yeah, we need to prepend [12:13] something [12:13] -scopes- is the name of the extension, right? [12:13] also the plugin seems pretty redundant [12:14] qtdeclarative-unity0-scopes [12:14] mhr3: no [12:14] didrocks, we need a common /usr/lib/*/unity/qml, or similar, path where those will get installed [12:14] mhr3: that sounds like it's an official qt things [12:14] didrocks, we already have dozens of qml plugins like that that aren't official [12:15] Saviq: yeah, sounds good to me (unversionned or unity0 until we have something) [12:15] mhr3: yeah, but it's a plugin of a shell [12:15] not a qt plugin for using without the shell [12:15] well you wanted a prefix :) [12:15] not that one :p === alan_g is now known as alan_g|afk [12:16] or unityplugin0-scope ? [12:16] fine with me [12:16] unity-plugin0-scope? (putting the API version next to plugin) [12:16] +1 [12:17] what if the plugin supports multiple versions of the api? [12:17] mhr3: it's unrelated from a packaging perspective [12:17] ok [12:17] unity-plugin21-scope can provides unity-plugin20-scope [12:17] mhr3: ^ [12:18] ok, renaming to unity-plugin0-scopes [12:18] hum, in fact, we're wrong [12:18] mhr3: you are not providing the plugin [12:18] unity8 is [12:18] so unity8 needs to provides unity-plugin0 [12:18] and you plugin is just unity-plugin-scopes [12:18] your* [12:18] you won't have plugin of your plugin, right? :) [12:18] hm? [12:19] ah, i see what you mean [12:19] will the scopes plugin won't have backward compatibility for the scopes? [12:19] so, basically, do you provide an API in it? [12:20] no [12:20] or is it just an extension like "show battery level" [12:20] ok, so you don't need to version in [12:20] you just need to dep on unity-plugin0 [12:20] which will be provided by unity8 [12:20] huhuh? [12:21] this last part is huh indeed [12:21] didrocks, that package will provide the binary plugin [12:21] ok, I think there is an inception effect :) [12:21] ah ok [12:21] so yeah, versioning is needed [12:21] it will provide an API to scopes? [12:22] didrocks, no [12:22] didrocks, it's the shell side of it [12:22] it will implement interface defined in lp:unity-api, used by unity8 [12:22] * didrocks is lost by what you with "will provide the binary plugin" [12:22] didrocks, will provide the plugin unity8 will use to talk to scopes [12:23] didrocks, not the APIs scopes will use [12:23] * didrocks is probably dumb, but not seeing the difference in those 2 statements [12:24] if the plugin implements the code for unity8 to talke to scopes [12:24] it's exposing/creating the API for scopes, right? [12:24] no [12:24] it's the shell side of that transaction [12:24] the scope side of that transaction will come from lp:unity-scopes-api [12:25] and it will actually dep on libunity-scopes-api... soon [12:25] ah, so basically, this plugin will only decide "this is how I render/handle the signals I'm getting through unity-scopes-api" [12:26] didrocks, scope → unity-scopes-api → unity-scopes-shell → unity8 [12:26] yeah, so that's what I told [12:26] didrocks, yeah, you can think of this as a shell-facing QML wrapper of unity-scopes-api [12:26] unity8 as a private API for its plugins === alan_g|afk is now known as alan_g [12:26] which isn't unity-scopes-api [12:26] has* [12:27] so unity8 should provides a unity-plugins0 package [12:27] that the unity-scopes-shell will depend on [12:27] didrocks, there is nothing like that ;( [12:27] not really private, it's defined in unity-api [12:27] or well, in that sense [12:28] or... will be :) [12:28] unity-api defines the APIs unity8 consumes [12:28] ok, so all will be exposed in unity-api? [12:28] the problem is that there's no compile/link dependency there [12:29] didrocks, unity-api just provides headers [12:29] didrocks, interfaces [12:29] we will probably make a .so of them soon-ish [12:29] right, and that's the interface that the unity-scopes-shell will use? [12:29] didrocks, will expose [12:29] didrocks, unity8 will use [12:30] so there is no need for yet-another-versioning? We have through unity-api what unity8 version the unity-scopes will be compatible with [12:30] didrocks, yes [12:30] and so unity-plugin-scopes is enough [12:30] yay [12:31] (and we can name all those plugins unity-plugin-*) [12:31] didrocks, +1 [12:31] damn it, if i didn't put the 8 there i'd have it already right :P [12:31] ok, nice :) [12:31] lol [12:31] heh mhr3 :) [12:33] mhr3, rename the source, please, too [12:34] Saviq, pushed [12:34] mhr3, and make it Provides: unity-scopes-impl, unity-scopes-impl-0 [12:34] k [12:35] mhr3, and then in the lp:unity8 part, Depends: unity-plugin-scopes | unity-scopes-impl, unity-scopes-impl-0 [12:36] mhr3, and the version bump and Breaks: you mentioned [12:37] eh [12:37] dpkg-source: error: source package has two conflicting values - unity-scopes-shell and unity-plugin-scopes [12:37] are you sure src pkg can be different to the binary pkg name? [12:38] mhr3: it means you changed in either debian/control or debian/changelog but not in both place [12:39] Saviq: this one is a bit more complicated https://codereview.qt-project.org/#patch,all,71155,3 let's see how it goes [12:39] didrocks, i have to use the src pkg name in changelog? [12:40] tsdgeos, lol, so the original code was isEqual() { return false; }? :D [12:40] yea.. ok [12:40] mhr3, just the last entry [12:40] there's just one :) [12:40] Saviq: well, there's lots of classes that reimplement the isEqual [12:40] it just doesn't hit them if you're comparing singletons [12:41] tsdgeos, mhm [12:41] that's why i'm not sure it's the best place to do it [12:41] but here it works [12:41] let them comment :D [12:42] mhr3: in the top one, yeah [12:46] didrocks, since both unity-plugin-scopes and unity8-private provide the same file, do i add Breaks to unity-scopes-shell, or Conflicts/Replaces needed too? [12:47] mhr3: the files are getting removed from unity8-private, right? [12:47] so we need to uninstall it? [12:47] didrocks, yea, latest version of unity8-private won't have them [12:48] mhr3: Breaks/Replaces in that case [12:48] on the version << unity8-private without that file [12:48] thx [12:48] yw! [12:48] * didrocks goes for a run [12:48] seb128, if I run system settings on the desktop, I don't have wifi... do you? [12:50] didrocks, if you could check once you're back http://bazaar.launchpad.net/~unity-team/unity-scopes-shell/trunk/view/head:/debian/control [12:51] Saviq, ^ you too [12:52] Cimi, network uses different indicator backends [12:52] Cimi, on desktop it's nm-applet, not indicator-network [12:52] Cimi, I have it just fine [12:52] Saviq, the package depends on indicator-network so it should be there [12:52] mmm [12:53] seb128, right, if you have two network indicators, yeah [12:53] no wifi here on system settings [12:53] trusty [12:53] is indicator-network running? [12:53] did you restart your session since you installed it? [12:53] mhr3, I don't think you need -dev-tools build-dep, though [12:53] no [12:54] so restart the session === alan_g is now known as alan_g|lunch [12:54] seb128, so 1980's solution! ;D [12:54] Cimi, seb128 restarting unity-panel-service should be enough, no? [12:54] restart unity-panel-service [12:55] Saviq, snap :p [12:55] :) [12:55] Saviq, qmlplugindump [12:55] mhr3, ah [12:55] seb128, ok works now, but I have two [12:55] Cimi, yes, expected [12:55] on unity [12:55] how can I remove one? [12:55] blacklist in unity? [12:55] Saviq, but i wouldn't be surprised if something was missing/extra, didn't try to build it on clean chroot [12:56] Cimi, you'll lose functionality [12:56] can you stop complaining? :p [12:56] mhr3, let me [12:56] Saviq, thx [12:56] seb128, me? :D [12:56] you can edit /usr/share/unity/indicators/com.canonical.indicator.network and delete the desktop profile [12:56] Saviq, no, Cimi [12:56] Saviq, as there's no ci for it yet, you can push fixes directly to trunk ;) [12:56] seb128, ah yeah, no, he can't ;) [12:57] Saviq, seems so ;-) [12:57] Saviq, I'm half polish :) [12:57] Cimi, indeed, that would explain things [12:57] Cimi, btw can you spend some time to fix the GTK themes before the LTS? they have some issues/stuff not looking right on new widgets [12:58] seb128, saw that [12:58] seb128, was actually thinking of doing an ubuntu touch theme [12:59] Cimi, LTS is not about doing new stuff, it's about polishing what we have and shipping a solid product... [12:59] Cimi, thanks for looking at those bugs/fixing the issues [12:59] seb128, depends when polishing is more work [12:59] I doubt fixing a few bugs is that much work [13:00] seb128, then you didn't do gtk theming :) [13:00] mhr3, don't get me started ... can we have a working dash for the LTS? ;-) [13:01] seb128, we don't? [13:01] mhr3, for some value of "working" I guess [13:02] mhr3, I still get the "no result found" empty dash issue several time a week [13:02] hmm, i still don't know what's causing that [13:02] still no idea of what info I could provide to help debugging it? [13:03] seb128, steps to reproduce [13:03] "use the dash" [13:03] works fine... not a bug :P [13:05] mhr3, http://ubuntuone.com/0RPwctnL0nRftR9hWFTMuS [13:06] mhr3, I clear the text by pressing "esc" [13:07] dednick, any steps to repro bug #1243146 ? [13:07] bug 1243146 in Unity 8 "SIGSEGV when clearing message indicators" [Medium,In progress] https://launchpad.net/bugs/1243146 [13:07] mhr3, you need qt5-default [13:07] mhr3, also my homescreen only lists apps, not files atm ... is that normal? [13:07] mhr3, let me add [13:08] seb128, do you have online sources on? [13:08] mhr3, yes [13:08] wonder if that would make difference [13:08] hm, so do i [13:08] Saviq: it's pretty random [13:09] seb128, as for files, check if the category is enabled [13:09] mhr3, oh, fun [13:09] mhr3, only "help" is enabled in the filters, that's why my dash is empty [13:09] Saviq: have a message in the indicator expanded and clear them all. [13:09] mhr3, if I enable applications it works [13:10] solved, yey! :) [13:10] mhr3, is the smart server trying to be too smart and telling my dash to disable apps? [13:10] mhr3, well, it's not happening on session start/by my doing, I didn't even know we had filter in the homescreen [13:11] no, empty search filters are remembered [13:11] and i think there's a bug somewhere where it saves incorrect state of those [13:11] pstolowski, ^ [13:12] dednick, thanks [13:21] pstolowski, maybe, search for "foo" (which takes a while), change filters while it's in progress and quickly press esc can make it confused? [13:29] seb128, as mhr3 said, the only way it can disable apps is when user manually de-selects apps in the filter while the search string is empty. if it happens on any other interactions, then this is a bug [13:29] seb128, if you find any way to reproduce it, then please include the output of 'gsettings get com.canonical.Unity.Lenses home-lens-default-view' in the bug report [13:29] pstolowski, hey, there is a bug then... [13:30] pstolowski, ok, the issue is that I've not been able to find obvious steps to reproduce, but I run into that several time a week [13:30] the dash is not empty all the time, and not on session start, so I doubt it's a buggy config [13:30] it happens a some point during the day [13:31] pstolowski, in that case the filter had "help" only selected [13:31] seb128, but when it's gone, it's gone for good, until you enable it back via filters? [13:31] pstolowski, http://ubuntuone.com/0RPwctnL0nRftR9hWFTMuS is what happens from an user view [13:32] pstolowski, I just noticed, thanks to mhr3, that the homescreen has filters and that only "help" was selected [13:33] seb128, and you're hitting esc on that screencast? [13:33] pstolowski, yes [13:34] easiest way to clean the text entry [13:36] seb128, can you report it? [13:36] pstolowski, sure, is there enough info in that description to make an useful bug? [13:37] pstolowski, I never reported it because I don't know how I land in the buggy state and mhr3 always said he didn't have enough info/a clue how to debug [13:37] i think there are two bugs actually [13:38] one that makes the home scope save an odd state of the filters for empty searches (not requested by the user) [13:38] and another where you're getting results you shouldn't be [13:38] so for example you should have never seen app results if they're disabled [13:39] yet you somehow do from time to time [13:39] (with empty search string) [13:39] right [13:40] seems like doing "one" -> esc was giving me a view ignoring the filters [13:40] yet i can't reproduce that here [13:40] mzanetti, reject https://code.launchpad.net/~unity-team/unity8/fix-1238232/+merge/191424 ? [13:41] Saviq: imo yes === alan_g|lunch is now known as alan_g [13:41] mzanetti, please do [13:41] ajmitch: done [13:42] Saviq: ^ [13:42] sorry ajmitch [13:54] mhr3, pushed tweaks to debian/control - builds in chroot now [13:59] Saviq, great, thx a lot [13:59] didrocks, now we just need to push it in t :) [13:59] well... once the unity branch is merged [14:03] tsdgeos, yay, we got +1 on the bugs :D [14:03] yeah [14:03] i've been wondering were tronical was [14:03] been trying to reach him on irc to no avail [14:04] i randomly remember someone telling me he is/was on paternal leave [14:04] but may be a different guy it was about [14:05] mzanetti: what's the units.gu(5) in lp:~mzanetti/unity8/fix-switching-previews-positioning ? [14:05] tsdgeos: yeah. that sucks. it's the height of the section header. Is there a way to get to it? [14:05] mzanetti: category header? [14:05] should be possible [14:06] let me see [14:07] mzanetti: can't you just use sectionDelegate.height? [14:08] ah no it's a qqmlcomonent [14:08] damnit [14:08] tsdgeos, yeah, you can't get to the delegate [14:08] tsdgeos, mzanetti, only thing I can think of: use a prop on the *view [14:09] dednick, we need https://code.launchpad.net/~nick-dedekind/unity8/StrFTimeFormatter/+merge/192343 so that we support non-qt time format strings? [14:10] mzanetti: are you trying to do with that, is it something regarding the clipping of the top section header? [14:10] seb128, sorry, I was itm. yes, I think whatever you described so far is enough for a bug report, it's important we don't forget about it and try to repro [14:11] tsdgeos: with what exactly? the header height? [14:11] pstolowski, ok, I'm going to file it in a bit [14:11] mzanetti: yep, i see you have that max in there [14:11] tsdgeos: I make sure the split for the openEffect doesn't happen at the top where the content could be hidden by the header [14:11] right [14:11] ok [14:12] tsdgeos: let me add a comment in all places where I use the 5 grid units [14:12] we either need a context property that chaneges all the time (to not actually change) [14:13] or introduce the idea of "i promise i'll be well behaved" and just have one value [14:13] or not sure :D [14:13] but that units.gu(5) looks to fragile tbh [14:13] too [14:13] yes. I agree [14:16] Saviq: yeah, i think it's the alarm indicator that gives time format in gdatetime (strftime) [14:17] tsdgeos: such a context property would be per delegate, right? [14:17] dednick, any idea why it wouldn't give up a preformatted string? [14:17] dednick, same as we expect translated strings and such... [14:17] mzanetti: we can see how to expose it [14:17] one per delegate [14:17] or one just for the top section delegate [14:18] but yeah one per delegate makes sense [14:18] Saviq: tz changes [14:18] possibly [14:18] tsdgeos: just like the other section.* properties probably [14:18] section.headerHeight [14:18] dednick, well, wouldn't the indicator service know? [14:19] mzanetti: we don't really have secion. properties but yes [14:19] we have "section" and "delegateIndex" [14:20] mzanetti: do oyu want to have a look at it? [14:21] tsdgeos: on it [14:21] mhr3: what's going to dep on unity-scopes-impl-0? (priority should be optional btw and I prefer libs just after just after priority) [14:21] Saviq: it would then have to repoll all the calendar events from the source when a change occurs. Plus I think it's better that the view decides how to display the data. I don't even think the dackend supplying the format is right... [14:21] dednick, top-approve https://code.launchpad.net/~aacid/unity8/noModelInSignal/+merge/194672 ? [14:22] dednick, right, it feels weird to get the format string from the backend [14:23] Saviq: yeah.. i know, we will probably override it anyway at some point. [14:24] Saviq: Do you know when CI is going to be back? [14:26] dednick, like... last Tuesday... [14:26] dednick, there were issues, guys are working day/night to get everything back [14:27] Saviq: but there's no jenkins approve right? because services are down... [14:27] ? [14:27] dednick, yes [14:28] So how does CI work with no jenkins? [14:28] dednick, does it? [14:28] Saviq: Do you know when CI is going to be back? [14:29] dednick, I meant it was supposed to be back Tuesday [14:29] dednick, but it's not :) [14:29] oh.. right :) [14:30] guys i need someone to review/topApprove this too https://code.launchpad.net/~aacid/unity8/lvwph_bad_header_position_1240118/+merge/193200 [14:32] Saviq: standip? [14:33] kgunn: ↑↑ [14:33] crap [14:33] greyback, got that cron script yet? ;P [14:33] :) [14:35] tsdgeos: Just testing your branch now [14:36] mterry: how usable is nested mir right now? Can it be used inside xmir? [14:37] greyback, yeah I think so. There are some u-s-c branches that need to land for Touch, but I don't think they'd affect desktop+xmir [14:38] didrocks, unity8 deps on the impl-0 [14:38] mhr3: but the scope plugin deps on unity-api-impl-0 [14:38] which is implemented by unity8 [14:38] seems like a circular dep to me [14:38]