=== EphraimMB is now known as cutie === cutie is now known as cute === bschaefer_ is now known as bschaefer [08:32] mzanetti: Saviq: so do we have the green light on SDK 1.3? should someone actually review/approve the branch? [08:35] I don't know... haven't got any update on the mail thread I asked this a couple of times [08:41] :/ [08:41] once they decide it'll be urgent [08:41] i'm seeing it [08:42] Saviq: mzanetti: Mirv: i guess there's decision on what to do with the audio role patches either, right' [08:42] tsdgeos, I'll talk to Pat today re: 1.3 [08:43] tsdgeos, but yeah, no word on the audio roles yet, mzanetti do you have an idea how public the audioRole property got? [08:43] no, not really [08:44] well, I've seen the patch is being worked on in akerselva. [08:44] but the last status meeting for that was during my holidays. [08:44] Mirv, do you know something? ^ [08:44] mzanetti, I meant in Ubuntu [08:44] as we introduced it before it was upstream [08:44] * Saviq fwds thread [08:45] right, what's the problem with that? [08:45] greyback, I wasn't able to reproduce https://code.launchpad.net/~gerboland/qtmir/multimonitor/+merge/272912/comments/694792 with my finger, but it's quite reliable with autopilot, will you have a look? [08:45] Saviq: ack [08:46] greyback, if I'd have to guess, it's as if it gets tricked on window boundary or some such [08:47] so when the touch ends exactly on window edge, the event is lost [08:47] greyback, did you guys talk with alan_g about the protobuf crash? [08:48] mzanetti: the problem is the api is not the same [08:49] and QML not having ifdefs makes our live interestin [08:49] g [08:49] ack [08:49] Saviq: not yet. qtmir with simpler shell doesn't exhibit that crash, and the dbus error should be fixed first imo [08:51] greyback, do we have a plan of attack (mostly asking if we're trying to fix for silo 22 or not) [08:51] ? [08:52] Saviq: well I am trying to fix it, but it can wait until after silo22. the AP fail will be fixed first [08:53] ack [09:01] tsdgeos: Saviq mzanetti: no decision, I'd appreciate a decision though... but it doesn't seem anyone can define what's "public" or not. I doubt bzoltan_ knows that "SDK" has a audio role API in the first place, but I don't know how it'd be marked as "private" either. if we download all store apps we'd know if anything besides clock uses it though. [09:02] mzanetti: so the problem is that we first patched qtmultimedia in June before submitting it upstream, and it wasn't accepted as is - a good example why upstreaming first should be a priority, but the feature was I guess OTA targeted at the time [09:02] mzanetti: so now we have the upstream API but current vivid-overlay using our obsolete API [09:02] yes, I know that stuff [09:03] Mirv, I think popey could help us with finding out, popey, could you `grep -r audioRole` on all your installed clicks? :) [09:03] Saviq: ah :) [09:04] but if I read saviq's mail correctly, the problem is already happening in unity alone [09:04] and the clock app [09:04] as wily and vivid wouldn't switch at the same time [09:04] mzanetti, yes, but how we deal with it depends on whether it's public or not [09:04] mzanetti, because if it's not, we can make the switch quietly, in one go, when going to new framework [09:05] right.. it's not documented at least... [09:05] indeed [09:05] mzanetti, otherwise we need to support both for a period of time and go through a full deprecation process [09:06] ok. right... so we'd backport the official upstream patch and change unity and clock if noone else uses it [09:06] ok, yes. popey to the rescue here! [09:07] mzanetti, yeah, and when 5.5 is in a framework, we'd transition there and could drop the 5.4 patch if we still cared about it [09:07] yep [09:08] yeah, let's see if our assumption is correct (that noone else uses it) and do the switch quietly if so [09:08] unfortunately unless we get a framework with the 5.4-backported patch, we should support enums both old and new [09:08] otherwise clock will break for people [09:08] wat [09:09] okay [09:09] popey, can you please grep through apps and see if someone uses the role property on Audio or SoundEffect elements [09:09] grep -r audioRole [09:10] mzanetti, you've a commented out line in MvM btw ;) [09:10] I'm sure there are [09:10] mzanetti, tsdgeos, zbenjamin bug #1508363 [09:10] bug 1508363 in unity8 (Ubuntu) "Coordinated migration to UITK 1.3" [Undecided,In progress] https://launchpad.net/bugs/1508363 [09:11] k [09:11] Saviq, yeah... I think I've tried that roles stuff as an outcome of the bug reports but as you know, don't think it makes sense to use in apps [09:12] unless it's the alarm app [09:12] curios how I ended up using the enum... back then it should've been the string version, no? [09:13] Saviq: mzanetti running now, takes a while [09:13] popey, cool, thanks a lot [09:14] mzanetti, we have enums, too, just different ones [09:18] popey, could also use your input on bug #1508363 - whether I've missed an app we should take care of [09:18] bug 1508363 in unity8 (Ubuntu) "Coordinated migration to UITK 1.3" [Undecided,In progress] https://launchpad.net/bugs/1508363 [09:19] haha, you're going to incur the wrath of s eb128 :) [09:20] mzanetti: old patch http://anonscm.debian.org/cgit/pkg-kde/qt/qtmultimedia.git/patch/?id=d5149eefcd093d96be3191d5f8a7f622f788e1f4 new patch http://anonscm.debian.org/cgit/pkg-kde/qt/qtmultimedia.git/plain/debian/patches/Add-audio-role-API-to-QMediaPlayer.patch?h=ubuntu [09:21] Saviq: thx [09:22] Saviq: mzanetti: jhodapp mentioned something about "as long as it maps to same pulseaudio role" (or something), is there something that needs to be takent into account for mapping from old role to new role? I mapped AlertRole -> NotificationRole in my qtubuntu-camera and qtubuntu-media MP:s [09:22] Saviq: mzanetti only 3 apps use audioRole, mvm, clock, dropping letters. [09:22] popey, mvm has it commented out... [09:22] popey: thanks! and isn't mvm's commented out? [09:23] I didn't grep for that [09:23] just for the existence of audioRole anywhere in the source [09:23] dropping letters does use it, as does clock [09:24] dropping letters might be erronous I think [09:24] yes [09:24] popey, is dropping letters in your lordship? [09:24] yeah [09:24] mzanetti: so I could offer an MP to remove the audio role usage? [09:25] yeah, if there's a merge for dl I can deal with it [09:25] ack, we'll drop it from there... [09:25] ok so looks like we've a plan [09:25] * Saviq replies to thread [09:28] popey: https://code.launchpad.net/~timo-jyrinki/dropping-letters/drop_audiorole_usage/+merge/275150 [09:30] that was quick :) [09:31] so that means we've to land unity8, clock and qt in one silo soon. Mirv, are you preparing that too? [09:31] bad timing [09:31] we literally uploaded clock to the store yesterday [09:32] mzanetti, not *that* easy [09:32] heh... popey not happening really soon [09:33] mzanetti, clock is a click, there's no fwork for it to depend on [09:33] oh right... clock is a click [09:33] ok [09:33] * Saviq types an email right now [09:33] mzanetti: regarding silo, also qtubuntu-media and qtubuntu-camera. the clock is the problem. [09:34] I'm actually wondering where the clock uses this role... I thought it uses the Alarms api which would then set the role implicitly... [09:34] I wonder if we could bypass the problem by doing some special trick in Clock where it _does_ detect the API version at runtime [09:34] even thought QML per se doesn't have #ifdef [09:34] yeah... should be possible with a loader I'd think [09:35] ah, it uses it for demoing the alarm ringtone [09:35] because that would skip the need for supporting two API:s at the same time and _still_ not being 100% sure everyone has upgraded to OTA+2 before updating the clock [09:35] fair enough I guess... [09:35] mzanetti: but Alarm api apparently doesn't use the Qt role api anyway? [09:36] mzanetti: hmm.. yeah, I guess it's fair enough if one has phone muted but wants to preview alarm sounds anyway [09:36] actually... thinking of it... I'm not so sure... [09:36] mzanetti, don't think it's possible [09:37] mzanetti, or well, we could try to create a component with 5.5 import [09:37] if I have my phone in silent mode, the preview probably shouldn't ring, while the actual alarm should... but maybe that's just me... there's a discussion on this on the ML [09:37] and fall back to the 5.4 component [09:37] as the new import should fail [09:37] would need to try [09:37] mzanetti, please have a look, that would simplify our lives a lot [09:38] as it's an enum we might could make it might fail compilation [09:38] and catch that with a loader's error state [09:38] will do [09:39] mzanetti, yeah, but one enum is in 5.0/5.4 import, the other on 5.5 [09:39] so this is what we need to hinge on [09:39] whether 5.5 import succeeds [09:42] Saviq: my first thoughts are always a shell script that sed:s the qml file before starting qmlscene :) (not sure if click allows a shell script as the file to execute) [09:43] Mirv, it does, but let's not ;) [09:43] :D [09:57] Saviq: hmm, what about the backport of the patch to qtmultimedia 5.4.2/5.4.1, doesn't the import stay at 5.4 by default? [09:58] Mirv, doesn't really help because clock needs to be able to depend on an appropriate framework [09:58] there's also #define QAudioRoleControl_iid "org.qt-project.qt.audiorolecontrol/5.5" in the new patch [09:58] Saviq: yes, I just mean regarding the detection on which one is in use [09:58] (and Q_MEDIA_DECLARE_CONTROL(QAudioRoleControl, QAudioRoleControl_iid)) [09:59] Mirv, let's see what we can do [09:59] Mirv, but anyway, unless it's in both 5.4 and 5.5 on the same import, doesn't really help us [10:22] Saviq: on the qtmir breaking AP thing, it appears AP is sending input events which are physically impossible: on my arale, it sends x=1048.09,y=1920.35 at the bottom of the gesture. QtMir used to pass that to Qt anyway, and I'll make it do that again. But that would need fixing in the AP test [10:23] s/I'll make it/I can make it/ [10:23] greyback, oh interesting [10:23] I think fixing the AP test would be most correct [10:24] greyback, I actually wonder if that should be "fixing AP", rather than the test [10:24] Saviq: well if you're on desktop, it's ok to drag outside the window. [10:25] greyback, AP deals with screen, not window [10:25] yeah, good point [10:25] greyback, not sure it should ever send events outside the screen [10:26] to emulate the finger better, it should send TouchEnd at screen boundary [10:26] no use comes to mind [10:27] Saviq: I'm going to fix the test and log an AP bug, unless you have objections? [10:27] greyback, +1 [10:27] was that the only AP test I broke? [10:27] greyback, yeah, didn't see any other [10:28] cool [10:35] mzanetti, Mirv, http://pastebin.ubuntu.com/12884817/ seems to work [10:36] ack [10:37] mzanetti, we'd need something like this in u8 too, then [10:37] tsdgeos, #ifdef in QML: http://pastebin.ubuntu.com/12884817/ ;) [10:37] Saviq: he he [10:38] my internet is borked again today :/ [10:38] if something looks stupid but works, it's not stupid [10:38] it just failed when i was donating at https://www.michaeljfox.org/get-involved/donation2.php and then it seems they don't accept spanish cards (or at least i had errors with the three of them) [10:40] mzanetti, it should probably try 5.5 first, as 5.4 import will work in 5.5 too, just not have the audioRole property [10:42] or should actaully assign the role [10:46] tsdgeos, ping [10:46] cimi: hi [10:46] tsdgeos, so I started doing what you said about the toolbar, then I realised why I didn't share the toolbar code at first sight :) [10:47] tsdgeos, I believe we will add other content there, not just sharing [10:47] right [10:47] so more reason to share it? [10:47] tsdgeos, so what I can do is creating a small toolbar, black [10:47] tsdgeos, and then add the sharing button inside [10:47] it will look quite the same of Rect { black } but under a Toolbar name [10:48] cimi: but why not with the button inside? [10:49] tsdgeos, mmm we can do that too [10:49] tsdgeos, indeed [10:49] cimi: also is really the design "always toolbar on overlapping the content"? [10:49] seems a bit intrusive to me [10:50] tsdgeos, designs are changing.. but so far it seems [10:54] ok [10:59] Saviq: ok so technically AP not at fault here, somehow some floating point noise appears between AP requesting an event, and it appearing to qtmir [11:00] Saviq: how about I make quick workaround in qtmir, and allow time to investigate it properly after? [11:03] greyback, wfm [11:11] Saviq: tsdgeos: mzanetti: I went ahead and built qtmultimedia 5.4.2 & 5.4.1 in silo 059 after rebasing the patch to them. I can soon build the qtubuntu-camera and qtubuntu-media MP:s in there, after which it should be testable (by commenting out the two audio role:s in unity8 qml:s) in theory on both wily and vivid. please instruct what needs to be done if you want "5.5" import to work on the 5.4 or som [11:11] ething. [11:12] like, if the backports are just backported to 5.4, then they're available via QtMultimedia 5.4 if I'm not incorrect (although I still don't know what needs to be done to use those "revision: 1" properties) [11:14] ack, thanks [11:14] Mirv, I don't think we should change 5.4 at all in this case [11:15] Mirv, because there's no way for clock app to depend on pre-rebase or post-rebase 5.4 [11:15] Mirv, we should leave 5.4 be, but make all projects work with 5.5 as well [11:15] Saviq: right, I was wondering about this - so you'd mean we'd actually ship the old API until the rebase on 16.04? [11:16] I'll keep the silo there in case you change your mind, but ok :) [11:16] Mirv, until we have a framework for clock app to depend on [11:16] Saviq: 5.5 is unlikely to land in vivid-overlay (not impossible though, I'll provide a PPA once wily+1 landing of 5.5 is done) [11:17] Mirv, yeah, that means it won't ever provide a framework higher than 15.04 IIUC [11:17] Mirv, so yeah, until we have a framework with 5.5, we need to leave 5.4 be [11:18] Mirv, we *could* rebase 5.4 if we publish a new framework with 5.4 at some point [11:18] but that wouldn't change much in the "import 5.4 or 5.5" situation, just the enum renames [11:24] Saviq: right, so those are the options. I guess there's no other downside to waiting for 5.5 than the possibility of some new app(s) starting to use the undocumented API [11:25] so, we need just patched Unity 8 and Clock before 5.5.1 lands to wily+1 [11:25] and it'd be nice if someone could review https://code.launchpad.net/~timo-jyrinki/qtubuntu-camera/support_new_audiorole_api/+merge/273791 + https://code.launchpad.net/~timo-jyrinki/qtubuntu-media/port_to_new_audio_role_api/+merge/273392 so those could be landed too [11:25] probably together with the Unity 8 [11:27] Mirv, yup, I think Jim should do the reviews there, no? [11:28] Saviq: yeah I asked him last week, he said to be doing them "later today" back then :) [11:28] I need to re-ping him [11:28] :) [11:28] hmm... now there's something odd... [11:28] Saviq, so there is "alarm" role and "alert" role [11:28] I would think the actual alarm uses the alarm role [11:28] so why does the preview then use the alert? [11:29] I'd say a bug [11:29] if so, it's not representative for the actual alarm anyways and probably should just use the multimedia role [11:29] alert, alarm, close enough to confuse the two [11:29] mzanetti, I'd say it should use the alarm role [11:29] the new api doesn't even seem to have Alert any more [11:30] mzanetti: I thought the NotificationRole would be the new alert, kind of [11:30] yeah that's == notification or so [11:30] I'm still not sure the preview should actually use the alarm role... [11:31] bzr qblame and see who added it [11:32] nik90 [11:32] who seems to be mostly away nowadays [11:33] so, I removed the qtmultimedia again from 059 and building qtubuntu-camera and qtubuntu-media MP:s there instead... and unity8 can be added. [11:33] Mirv, I think i'd be easiest if we do the switch with 5.4 -> 5.5 [11:33] not backporting the new api to 5.4 [11:33] yeah, we discussed this [11:34] just above [11:34] no change to 5.4 [11:34] mzanetti: it's the easiest, just need runtime detection for Unity 8 + Clock in addition to those qtubuntu-camera/media landings. [11:34] I modified the 059 description accordingly [11:34] mzanetti, the alarm volume is set in the clock app, I'd say it should use that volume when previewing the alarm [11:35] mzanetti, huh, doesn't alert == ringtone? [11:36] is anything using the alert role for real? [11:37] ah [11:37] ok alert == ringtone [11:37] but when previewing, somehow ignores silent mode [11:37] ... [11:37] I tell you... [11:37] :) [11:38] any case, it *should* use the alarm role IMO [11:41] Saviq: https://code.launchpad.net/~gerboland/qtmir/multimonitorAPfix/+merge/275170 - works locally [11:41] greyback, conflicts? [11:41] or at least LP got weird [11:42] Saviq: LP confused [11:42] merges locally just fine [11:42] ugh for the workaround [11:42] I know [11:43] but ok [11:43] it's emulating previous behaviour [11:43] greyback, try the suggestion I posted as a comment, to see if it fixes the test [11:43] * ltinkl is curious about the whole method [11:46] ltinkl: nice idea, but the bug is that the QPoint going in is physically outside the window [11:46] the input coordinates that AP injects comes out to QtMir different [11:47] https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1508415 the bug I logged [11:47] Launchpad bug 1508415 in unity8 (Ubuntu) "AP input events sometimes positioned outside screen geometry" [Undecided,New] === dandrader_ is now known as dandrader [12:50] jhodapp: hey! could you review/top-approve the qtvideo-node, qtubuntu-camera and qtubuntu-media branches that we talked about last week? I'd like to land the last two before-hand already (they have #ifdef:s so nothing changes for 5.4) [12:51] I just updated the qtubuntu-media since there were new changes in trunk [12:52] Mirv, sure thing...been meaning to do that, apologies for the delay. I'll take a look my afternoon today [12:52] ok! [13:13] tsdgeos, fixed both issues btw === dandrader is now known as dandrader|afk [13:17] tsdgeos: Saviq: mzanetti: in other news, ok look that beauty https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-012/+packages (while LP hasn't updated yet the published ones). that is, I got Qt 5.5.1 far enough to run on the phone (with audio role hand edited out) so I'm getting rid of the temporary 5.5.1 PPA - 012 will be 5.5.1 from now on. [13:17] ETOOMANYBUILDS [13:17] oh f*ck, 22.5GB out of 20.0GB used [13:18] that means next builds will fail. hmm, I should either reach out or wait for the old ones to be deleted. [13:25] Saviq: consulting with alan_g, suspect that protobuf crash due to mir & mesa on desktop. It's not happening on phone. [13:25] greyback, oh good [13:25] greyback, you mentioned a dbus error though? [13:26] Saviq: it's non fatal [13:26] greyback, silo 22 is rebuilding right now, unless something else big jumps out at us, I wanna make ready for QA this evening [13:26] Saviq: sounds good to me [13:31] the dependent branches link in launcphad has been fixed \o/ [13:31] and then unfixed :? [13:32] i guess they found a regression :/ [13:37] ok I need food === dandrader|afk is now known as dandrader [14:28] tsdgeos: did you ask once where the "QThread: Destroyed while thread still running" log message was coming from? https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1508485 [14:28] Launchpad bug 1508485 in unity8 (Ubuntu) ""QThread: Destroyed while thread is still running" printed on shutdown" [Low,New] [14:33] greyback: didn't ask, i know where it comes, just saying we should fix it :D [14:33] tsdgeos: lol ok [14:33] well we have a bug now! [14:33] so it's as good as fixed :D [14:33] \o/ [14:34] how do i find unity on my ubuntu desktop computer by chance? [14:35] bloomandivy: what do you mean "by chance"? Had you removed unity, and it was re-installed? [14:35] i don't know, i got the computer from someone and don't know where it would even be located [14:36] bloomandivy: "unity" is the name of the default desktop shell, which is the thing you see after you log in. [14:36] unless your computer was customized to use a different one [14:37] oh that isn't pulling up, maybe it was uninstalled....hmm [14:37] let me see if i can download it from ubuntu software center [14:41] it's possible to have several desktop shells installed (like gnome3, kde...). You get to choose which one at the log-in screen - see here: http://www.linuxnov.com/wp-content/uploads/2012/02/Unity-Greeter-0.2.1-LightDM-Ubuntu-12.04-LTS-Precise-Pangolin.jpg [14:42] thanks [14:52] hmmm, guys what's your opinion on this? https://code.launchpad.net/~aacid/unity8/fix_cropped_image_binding_loop/+merge/275199 [14:52] it fixes the binding loop by removing the binding :D [14:53] i guess it's a bit more performant since it doesn't need to print out stuff [14:53] mzanetti: Saviq: cimi: ↑↑↑ [14:54] well, +1 for removing a warning... not so much for the verbosity of the code... but if it works, I guess I'm ok with it [15:09] tsdgeos, it's a shame, QML should just deal with that [15:09] actaully the old code had a loop indeed [15:10] in which changing one value had the effect of changing that value [15:10] but then i changed the code to [15:10] readonly property bool useHeight: (implicitWidth / implicitHeight) > (width / height) [15:10] which doesn't really loo [15:10] p [15:10] and still complained [15:10] but oh well [15:11] indeed [15:12] dandrader, greyback, I still see a hang on exit in silo 22, maybe not as reproducible, and I think limited to krillin atm, but still happens [15:13] Saviq: logs and a backtrace would be good [15:13] greyback, yeah, as soon as ap completes === dandrader is now known as dandrader|afk [15:18] basically this also has the binding loop warning [15:18] http://paste.ubuntu.com/12886275/ [15:18] which is "true" [15:18] looks like a loop [15:18] but it isn't [15:19] well, yeah, QML treats everything that means it has to recalculate itself as a loop [15:20] so iHeight changes → useHeight changes → iHeight changes →... [15:20] even if not all of those actually changes [15:20] right, i think it should only complain on the actual "it changes" [15:27] greyback: not sure which explanation to add "don't do this it'll create warnings about a binding loop" [15:27] seems kind of weird [15:29] tsdgeos: it is a bit odd, but you see where I'm coming from. [15:29] i do [15:29] but we have logs [15:29] bzr blame and then read the log [15:29] it'll explain the same as the comment [15:31] sure, is a way to see it. I just like non-obvious code to be explained in the code, not in the history. [15:31] Saviq, is it ok when unity8 still wants to remove qtubuntu-sensors when doing ./build.sh? [15:35] ltinkl, not usually [15:35] ltinkl, is that with trunk? [15:35] Saviq, yup [15:35] ltinkl, can you paste apt output? [15:36] Saviq, haha do you really want it? :) (warning, Czech incoming) [15:36] ltinkl, I need a laugh today, hit me ;) [15:36] ltinkl, you can always go $ LANGUAGE=en ./build.sh ;) [15:44] greyback, dandrader|afk, as you were, can't reproduce of course [15:45] Saviq: don't do this shit to me man! [15:45] greyback, wait! [15:46] aaah [15:46] didn't manage to catch it [15:46] stupid upstart [15:46] wonder how am I supposed to prevent upstart from killing it after the timeotu [15:46] timeout, even [15:47] here's hoping apport-cli --hanging will do === dandrader|afk is now known as dandrader [15:57] greyback, http://pastebin.ubuntu.com/12886536/ [15:58] * Saviq gets more symbols [15:59] /usr/lib/arm-linux-gnueabihf/libubuntu_application_api_test.so.3.0.0 <- test mock at fault. Dunno how it's only silo22 that's exposed that [15:59] greyback, how about http://pastebin.ubuntu.com/12886548/ [16:00] a totally different BT. In dbus, ick [16:01] greyback, might very well be it's a AP-only issue [16:02] * Saviq starts u8 normally and sends SIGTERMS [16:02] possibly [16:03] for instance, this could cause a crash, if it's a timing thing: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1508485 [16:03] Launchpad bug 1508485 in unity8 (Ubuntu) ""QThread: Destroyed while thread is still running" printed on shutdown" [Low,New] [16:03] but it's been around for a long while [16:03] it may be qtmir shutting down more correctly is exposing these issues now [16:10] yeah, can't get it to hang on normal run, calling it test-only issue [16:46] @unity, please look through your votes and potential missing top-acks on silo 22 https://requests.ci-train.ubuntu.com/#/ticket/445 [16:49] Saviq: all branches approved capt'n [16:49] this thing is looking good [16:49] *and* it's awesome on an external screen :) [16:51] just mark it ready for QA already! [16:51] yes! :) [16:51] * greyback has bottle opener hovering over beer [16:51] ltinkl, https://code.launchpad.net/~lukas-kde/unity8/liveCaption/+merge/273792/comments/695191 [16:51] argl [16:52] dandrader, meaning, I can remove the property and it would still work? [16:52] dandrader, or, is it broken now? [16:52] ltinkl, I mean that it looks this property is not being used. so you can just remove this change [16:52] yeah, not today though [16:53] ltinkl, dandrader, please MP with the cleanup, won't rebuild/test again due to that [16:53] Saviq, well, you asked for us to check our votes on all MPs, right? :) [16:54] dandrader, sure, I'm just saying what the "fix" is going to be ;) [16:55] mzanetti, care to change your vote https://code.launchpad.net/~unity-team/unity8/mousePointer/+merge/273369/comments/691465 ? [16:56] ltinkl, https://code.launchpad.net/~nick-dedekind/unity8/lp1378821.time-translation/+merge/271452/comments/683878 you're Needs fixin' here [16:57] dandrader, https://code.launchpad.net/~aacid/qtmir/no_double_search/+merge/272707 approve after all? ;) [16:58] Saviq, just abstained [16:58] ack [17:02] Saviq, done, the issue seems to be resolved === alan_g is now known as alan_g|EOD [17:06] dandrader, also the "property var surface: null" in SurfaceContainer.qml seems unused then [17:07] ltinkl, maybe [17:08] dandrader, well it's used in SessonContainer.qml only, not in SurfaceContainer.qml itself === robru is now known as robru|sick [17:13] dandrader, MP updated [17:14] dandrader, looking at it again, this could be simplified too: "title: window.title !== "" ? window.title : model.name" [17:15] dandrader, window.title has already everything we need [17:15] dandrader, ah no, scratch that [17:16] dandrader, if the surface name is empty, it will take the name from the app's .desktop file [17:22] ltinkl, `bzr push -r1953 --overwrite lp:~lukas-kde/unity8/liveCaption` [17:22] ltinkl, and a separate MP for the cleanup, please [17:22] Saviq, ah, ok [17:22] ltinkl, otherwise I need to rebuild unity8 in silo 22, and I really don't wanna [17:22] because [17:22] @unity: silo 22 is a wrap! [17:23] yay \o/ [17:23] Saviq, pushed the revert [17:23] Saviq, will file the cleanup tomorrow, feel like EOD today [17:24] ltinkl, is there an app changing window title, or shall I provide a snippet for testing? [17:24] ltinkl, sure, cleanup tomorrow's fine [17:24] Saviq, browser or system settings [17:24] ack [17:24] Saviq, the latter should change the title when entering a specific module === dandrader is now known as dandrader|bbl [17:43] Saviq, nice! [17:50] hey guys, i was just asking this question in #ubuntu-touch but it seems it's more appropriate here, so i'll ask again: I'm trying to port the multitouch gestures in unity like 3-finger drag + pinch etc. to gnome3/gentoo. So far i have the grail and frame working, but i don't know where to go from here. The launchpad / wiki say that a compiz plugin interacts with the utouch stack to enable the gestures in unity, but the information [17:50] / code on launchpad seems way outdated [17:51] so my question is: how do the gestures actually work in unity currently, and where is the code for it? there doesn't seem to be any up-to-date information on the net [17:56] Trevinho, if you're around, you'll probably know best ↑ [17:58] andyrock, or you ↑ [17:58] reverse, it might be easier if you post to ubuntu-devel mailing list, most of the folk here are in EU timezones, so EOD by now [17:59] wooo [17:59] reverse, alright, I'll just stick around for a while longer though, maybe someone sees it :) thank's for the heads up though [17:59] Saviq: thanks for all your testing [18:01] wasn't useless, that's a plus [18:01] whenever I find an issue after having spent days testing... it's actually a good feeling, to know the time wasn't wasted :P [18:02] kgunn, if you're not highlighting @, silo 22 is QA-ready [18:02] and it's aaaaawesoooome [18:27] Saviq: :) [18:28]