=== Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === cprov__ is now known as cprov_ === didrocks1 is now known as didrocks [08:46] hmm, looks like someone enabled cron again yesterday [08:47] FYI [08:47] === IMAGE 239 building (started: 20140317-03:05) === [08:47] === IMAGE 239 DONE (finished: 20140317-04:15) === [08:47] ogra_: yeah, seems so. Well we already have one image, so that's ok [08:47] we have a bot? [08:47] (other than ogra_) [08:48] we do have ogra's bot [08:48] which isn't ogra :p [08:48] yes, it is running in #ogra-test [08:48] suh-weet [08:48] i still have an issue with my daily DSL reconnect ... once thats fixed i'll run it here [08:49] (adn will add more features .... i.e. changelog URLs with the success msg and promotion messages too) [08:49] bzoltan: hey, I'll have to do a MP for the toolkit to be unblocked from proposed [08:49] not sure if Mirv noticed it's stuck ;) [08:50] oh, what happened to the meeting time ? [08:50] bzoltan: I have to revert one of balloons's commit which adds a dep on AP [08:50] ogra_: someone removed it… [08:50] at canonical [08:50] yes, and now it is in 10min [08:50] he isn't in UE nor on IRC [08:50] (says my notification) [08:50] ah, I have to repush the new I created [08:50] let me fix that [08:50] didrocks: what was that commit about? But of course OK. [08:51] didrocks: Ohh... that one, sure [08:52] bzoltan: that one: http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/revision/951 [08:52] it adds a dep on python-autopilot [08:52] which isn't in main [08:52] and I don't want to block you on the MIRing :) [08:52] didrocks: thank you [08:53] I've been so far busy cleaning up all the 5.2 related stuff I have lying around... lots of it [08:53] plus starting precise/saucy builds of it [08:54] bzoltan: mind having a look: https://code.launchpad.net/~didrocks/ubuntu-ui-toolkit/unblock-proposed/+merge/211267 [08:54] Mirv: with sil2100 out do you mind focusing on the landing today? [08:54] Mirv: I think precise/saucy can wait for now [08:55] bzoltan: if +1 for you, I'll restack that on the current (stuck) landing) [08:55] didrocks: I am good with it [08:55] great, thanks :) [08:56] didrocks: for the remaining day, sure. what's the current policy, AP fixes only or other successfully tested landings too? [08:56] Mirv: yeah, sounds like a good approach [08:56] didrocks: note the "or"? :) [08:56] AP fixes only + successfully tested landings (safe) [08:56] I would say [08:56] seb128, are you guys doing the tests for system-settings yourself or do i have to contact QA about a change ? [08:57] ok, thanks [08:57] Mirv: and unblocking things that are going to be stuck in proposed due to missing new archs [08:57] ogra_, we are doing it, but QA has engaged on some refactoring/improvements for our tests [08:58] see e.g https://code.launchpad.net/~vrruiz/ubuntu-system-settings/autopilot-emulators-helpers/+merge/210861 [08:58] bzoltan: do you have a safe toolkit landing where we can add that MP? [08:58] ogra_, what's the issue? [08:58] bzoltan: it will unblock a lot of arch deps [08:58] seb128, it would be nice if the IMEI test wouldnt fail when there is no IMEI (like on tablets) [08:58] bzoltan: I'm afraid line 18 is risky AP-wise, right? [08:58] http://ci.ubuntu.com/smokeng/trusty/touch/manta/239:20140317:20140304/7178/ubuntu_system_settings/900882/ [08:59] didrocks: yes, there is a reason I did not turn it on yet [08:59] http://ci.ubuntu.com/smokeng/trusty/touch/flo/239:20140317:20140304/7179/ubuntu_system_settings/901368/ [08:59] ogra_, it works on desktop for me? [08:59] didrocks: let's find a safe one [08:59] seb128, well, it fails on both tablet tests [08:59] ogra_, and I've definitively no imei here [08:59] bzoltan: ok, in case you have nothing else in your luggages, I'll just land that one ;) [08:59] seb128, but you also dont have the interface to ask for one ... perhaps thats the issue [08:59] ogra_, right, just saying, the "when there is no IMEI" is probably a wrong characterization of the issue [08:59] didrocks: that is the safest :) [08:59] ogra_, right, could be [09:00] * ogra_ assumes it uses getprop [09:00] ogra_, patches are welcome, I've no access to those devices [09:00] so I can't really debug/test [09:00] bzoltan: ok, mind if I handle just with that one? (otherwise, everytime we have an app biulding, I have to remove some .debs) [09:01] bzoltan: FYI regarding Qt 5.2 precise/saucy builds, here's where I'm currently https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-beta-proper/+packages [09:01] Mirv: Perfect... I would suggest to slow down :) after the QtC dependencies and the QtC is there [09:02] didrocks: Yes, I thank you for fixing this [09:02] bzoltan: great, dealing with it, no worry :) === wgrant_ is now known as wgrant [09:18] * ogra_ gets new coffee [09:30] hum [09:30] trusty dist-upgrade failed [09:30] Unpacking libaccounts-qt5-dev (1.11+14.04.20140307-0ubuntu1) over (1.10+13.10.20131016.1-0ubuntu1) ... [09:30] dpkg: error processing archive /var/cache/apt/archives/libaccounts-qt5-dev_1.11+14.04.20140307-0ubuntu1_i386.deb (--unpack): [09:30] tentative de remplacement de « /usr/lib/i386-linux-gnu/cmake/AccountsQt/AccountsQtConfig.cmake », qui appartient aussi au paquet libaccounts-qt-dev 1.11+14.04.20140307-0ubuntu1 [09:30] Mirv, ^ known? [09:30] * seb128 removes libaccounts-qt-dev [09:30] didrocks, hmm, the hangout link is gone from the reminder [09:30] oh, another one [09:30] dpkg: error processing archive /var/cache/apt/archives/qtcreator-plugin-cmake_3.0.1-0ubuntu5_i386.deb (--unpack): [09:30] tentative de remplacement de « /usr/lib/i386-linux-gnu/qtcreator/plugins/QtProject/CMakeProjectManager.pluginspec », qui appartient aussi au paquet qtcreator 2.8.1-0ubuntu1 [09:30] good morning [09:30] didrocks, can I get a silo for line 54? [09:30] ogra_: I don't get a reminder [09:30] oh ? [09:31] tvoss: can you ping all EU people please? :p [09:31] * ogra_ always gets mail [09:31] ogra_: look at the calendar, you should have it [09:31] sigh [09:31] Mirv: look at tvoss request, please? [09:31] didrocks: ogra_: the entry has been removed from my calendar as well [09:31] that means i have to have a calendar open for it :/ [09:31] psivaa_: right, but you should have received a request [09:31] psivaa_: someone removed the old one… [09:32] and the old HO link doesnt work :( [09:32] didrocks: ok, looking for the new invite [09:32] ogra_: hum, we are 5 in it [09:32] yes [09:32] psivaa_: did you find it? [09:33] from the calendar it works (and has a name etc) [09:33] but thats really annoying [09:33] didrocks: not yet. could i have the link just for today pls [09:33] sure [09:33] https://plus.google.com/hangouts/_/canonical.com/landing-meeting [09:33] https://plus.google.com/hangouts/_/canonical.com/landing-meeting [09:33] didrocks: tvoss: looking after the meeting or so [09:37] tvoss: landing-017 [09:37] Mirv, thank you [09:40] didrocks: https://bugs.launchpad.net/unity-mir/+bug/1290416 [09:40] Ubuntu bug 1290416 in unity-mir "Mako locks up roughly once a day since R226" [Undecided,New] [09:41] ogra_: what installs /system/bin/netmgrd ? i.e. where should I file bugs in it? [09:41] popey, the android package [09:41] all of /system is owned by it [09:41] which lp project is that? [09:42] if i "ubuntu-bug" will it get relavent data? [09:42] ubuntu [09:42] well, it isnt "installed" as a deb [09:42] ok, i just want to file a bug ☻ [09:43] https://launchpad.net/ubuntu/+source/android/+bugs ? [09:43] and i dont think it will collect any specific data ... you want /system/bin/logcat -d, syslog and kern.log (or dmesg) [09:43] yep [09:43] magic, thanks [09:48] bug 1293459 [09:48] bug 1293459 in android (Ubuntu) "radio consuming a lot of memory on #238 on mako" [Undecided,New] https://launchpad.net/bugs/1293459 [09:54] geez, how big is that kern.log [10:01] didrocks: sorry, doorbell, new microwave arrived. ☻ [10:01] popey: ahah, I see priorities! :) no worry, nothing special :p [10:01] didrocks: there'd be a packaging ack (AP run ok) http://162.213.34.102/job/landing-011-2-publish/lastSuccessfulBuild/artifact/packaging_changes_address-book-service_0.1.1+14.04.20140314.4-0ubuntu1.diff [10:02] btw in case someone is interested http://people.canonical.com/~ogra/touch-bootcharts/ [10:02] yeah, food > phones [10:02] Mirv: have you rerun the calendar app tests? (as they are impacted) [10:02] once the bot is fully active i will let it generate these automatically [10:02] ogra_: oh nice! [10:02] and i also think i can now add symlinks to the changelogs [10:02] didrocks: no, not calendar app. calendar uses address book somehow? [10:03] Mirv: sorry, messaging-app [10:03] so that you can click on the right image id instead of having to look up the cdimage version first [10:03] Mirv: other +1 on the change [10:03] great :) [10:03] ogra_: pretty consistent then at just over a minute :) [10:04] didrocks: not messaging app yet, running now. [10:04] davmor2, huh ? [10:04] ogra_: the bootcharts [10:04] davmor2, unity8 is starting after 20sec ... [10:04] once the indicators are up you have the UI on screen [10:04] davmor2: where to file the volume button bug ‽ [10:04] bootchart is looking for X11 mapping, so dont trust the overall time there ;) [10:05] ogra_: hahah [10:05] its about 30sec [10:05] popey: I have no idea [10:05] ogra_, didrocks^^ where to file the volume key issues [10:05] the first boot is about 1min [10:05] davmor2, no idea, either Mir, unity-mir or android [10:05] * popey picks one [10:06] yeah, put it on Mir + android [10:06] I would say [10:06] kk [10:06] right I'm off shopping [10:07] https://bugs.launchpad.net/ubuntu/+source/android/+bug/1293478 [10:07] Ubuntu bug 1293478 in android (Ubuntu) "Volume buttons no longer function correctly since #238 mako" [Undecided,New] [10:07] Mirv, seems like no packages are arriving in https://launchpad.net/~ci-train-ppa-service/+archive/landing-017 [10:09] tvoss: sorry, I've been so much tied with the 5.2 my CI Train service might not be completely hitch free :) I've understood it's the lander's job to kick the 'build' job after a silo has been assigned? [10:09] Mirv, ah ... didn't know [10:09] Mirv, done [10:10] tvoss: ok. not seeing at http://162.213.34.102/job/landing-017-1-build/ though. [10:10] Mirv, try a refresh :) [10:10] works :) [10:17] didrocks: contrary to what i said in the meeting, the calendar_app failure is not flaky, the same failures are reproduced in the next run too :/ [10:17] psivaa_: oh, ok, well… good news in some way :) [10:18] didrocks: yea, ack :) [10:18] maybe we should summon elopio for those [10:20] Mirv: ok, so it seems we nede to dig why qtdeclarative5-unity-action-plugin isn't available [10:20] as it's blocking the sdk [10:20] and so multiple other archs [10:20] and your recent publications are going to be blocked because of that as well [10:21] it's Architecture: any [10:21] ah, didn't built because of libhud2-dev [10:22] which is arch: any [10:22] failed on arm64 [10:22] some tests [10:22] and dep dee-qt [10:29] yeah I saw on #ubuntu-release that colin had tried to stab dee-qt but did not succeed, and Dimitri was encouraged to do the same [10:34] I'm afraid as well at the hud not passing tests on arm64 [10:38] psivaa_: bug 1293489 for the record [10:38] bug 1293489 in Ubuntu Calendar App "Multiple test failures since move to Qt5.2 #238 on Mako" [Undecided,New] https://launchpad.net/bugs/1293489 [10:38] also bug 1293488 [10:38] bug 1293488 in Ubuntu Music App "Multiple test failures since move to Qt5.2 #238 on Mako" [Medium,New] https://launchpad.net/bugs/1293488 [10:38] popey: ack, thanks [10:46] 13:34 Trying to debug the dee-qt build on ppc64el is making me hallucinate [10:46] 13:34 62 connect(&model_qt, &QAbstractItemModel::rowsInserted, [&num_insertions] (const QModelIndex &parent, int start, int end) { [10:46] 13:34 63 num_insertions++; [10:47] 13:34 64 }); [10:47] 13:34 step into that and I get: [10:47] 13:34 (gdb) p signal [10:47] 13:34 $5 = (void (QAbstractItemModel::*)(QAbstractItemModel * const, const QModelIndex &, int, int, QAbstractItemModel::QPrivateSignal)) 0x10016bf0 [10:47] 13:35 where on earth did it get that function from? [10:47] 13:35 powerpc has the same test failure; and there's actually not *that* much similar between powerpc and ppc64el, they're different word length and different endianness [10:47] that was my last brain-dump on dee-qt [10:47] it's easy to reproduce on porter-ppc64el.canonical.com [10:48] it looks like it's the caller's fault (i.e. disassembling the caller it does seem to be loading the wrong function pointer), but I lack the expertise to work out why [10:48] tsdgeos: as you are on that one as well ^ [10:48] and mhr3 ^ [10:49] well i'm still trying to login into the machine :D [10:51] cjwatson: hey, I'm not sure I'll put the right informations for the framework names on ubuntu-touch metapackage btw, are you doing so or should I just copy the existing entries you added? (then, we have to wait on jdstrand + click store side) [10:52] didrocks: I'll do it [10:52] cjwatson: thanks [10:52] didrocks: I assume I need to leave ubuntu-sdk-14.04-dev1 in place for compatibility? [10:52] cjwatson: yeah, and I propose that we remove it in a week [10:53] *shrug* no rush [10:53] cjwatson: just wanted to clean as soon as possible as it was the deal [10:54] it doesn't matter [10:54] (just updated the seed for the icon theme change btw, I'll let you regenerate the metapackage in the next upload) [10:56] * davmor2 fires manta to test the volume buttons [10:56] Morning all [10:56] hey davmor2 [11:05] cjwatson: seen my query? [11:06] Queries light up just as red as channel highlights :) [11:08] popey: can you have another look at this https://bugs.launchpad.net/indicator-sound/+bug/1283191 I can confirm the volume indicator moves but if you move the slider to %50 and then press the vol up button the indicator increase as does the volume but the slider remains at %50 [11:08] Ubuntu bug 1283191 in The Sound Menu "Sound indicator doesn't change when using hw buttons" [Undecided,Confirmed] [11:08] davmor2: ah, so the volume is changing, but not the indicators? [11:09] didrocks: no that is a separate issue altogether [11:09] davmor2: nope, the indicator never moves for me [11:09] didrocks: this it that the slider seems to be independant of the volume keys and indicator display [11:14] didrocks: I added additional steps to the bug that should I hope make it clearer [11:14] davmor2: sweet, thanks! [11:15] seb128: do you think anyway from the indicator team can have a look? Seems like it can have been impacted by the desktop only changes [11:15] didrocks: but again a separate thing balloons was seeing it in 208 [11:15] yeah [11:15] didrocks, what? [11:15] seb128: https://bugs.launchpad.net/indicator-sound/+bug/1283191 [11:15] Ubuntu bug 1283191 in The Sound Menu "Sound indicator doesn't change when using hw buttons" [Undecided,Confirmed] [11:16] didrocks, that's almost a month old, what desktop only changes? :p [11:16] seb128: hum, that wasn't at the same time than the trigger > 100%? [11:17] * didrocks looks back at history [11:17] didrocks, it was [11:17] didrocks, but looking at http://launchpadlibrarian.net/167019111/indicator-sound_12.10.2%2B14.04.20140207-0ubuntu1_12.10.2%2B14.04.20140220-0ubuntu1.diff.gz I doubt that's it [11:17] well I guess we can check [11:17] seb128: yeah, the date matches perfectly, but it seems really unlikely [11:18] might worth a check if possible :) [11:18] yeah, I'm going to check [11:18] thanks! [11:18] seb128: just be aware there is another bug in latest images [11:18] didrocks, note that popey said it was working on image 206 on mako for him [11:18] seb128: that keys are not working on touch === vrruiz_ is now known as rvr [11:18] how do I test then? [11:18] so better to go back to previous promoted one [11:19] shrug, ok [11:19] seb128: yeah, seems multiple people have different pass/fail :/ [11:19] (didn't try myself TBH) [11:19] I really doubt it's indicator-sound's fault for the record [11:19] but let's see [11:19] sound indicator works with 237 [11:19] thanks [11:19] hum [11:19] dave told the contrary [11:19] * didrocks is puzzled [11:20] so, davmor2 before we all loose time on that, you told they were 2 bugs [11:20] i have a #237 phone in front of me, and i can adjust the sound indicator using the hardware volume buttons [11:20] one on indicator [11:20] one on hw button [11:21] ok [11:21] so let's focus on the hardware button issues first [11:21] and we'll see for the potential second issue next [11:21] once the first is fixed [11:22] didrocks, my device is on r231 and using the hardware keys make the indicator change [11:22] didrocks: Yes 2 bugs, One is the slider in the indicator not moving when the hardware buttons change the volume the actual indicator shows the change, the other is that the volume down button doesn't work on mako and manta and according to ogra_ neither work on flo [11:22] no notification/sound player though, which makes it non obvious they are doing something [11:23] davmor2, well, vol up seems to work with the little speaker icon ... [11:23] I just tested [11:23] davmor2: where is the second bug report already? [11:23] did only notice that now ... i was looking at the slider [11:23] open the sound indicator [11:23] use the hardware keys [11:23] it moves [11:23] (n4) [11:24] yeah, it broken between 237 and 238 it seems [11:24] davmor2, i think i'm seeing the same [11:25] seb128: open the indicator, slide the slider to 50%, close the indicator, press the volume up button then drag the indicator back down and see what the slider is on [11:25] davmor2, it's updated for me [11:26] the icon in the panel is changing as well [11:26] but I'm r231 (e.g no current) [11:26] i can reproduce that on 237 [11:26] popey said 238 has the issue [11:26] or 237 [11:26] there are two issues here. [11:26] (at least) [11:26] did it start on 237 ? [11:26] indeed [11:26] what changed in that image, [11:26] ? [11:26] ogra_: ^ [11:27] well in 237 with the procedure davmor2 just gave I have got the volume slider in the indicator stuck, but it worked fine a few moments ago [11:27] * popey reboots to try again [11:27] if you open the indicator and use the hardware buttons, is the slider moving? [11:27] it was [11:27] but after moving the slider to 50% it no longer does [11:28] ok, there is a bug confirmed [11:28] (on 237) [11:28] \o/ [11:28] i had the issue on 237 here [11:28] if you move the slider manually yes [11:28] I bet it's again a qml issue [11:29] the slider is bind to the sound property [11:31] but if you move it manually qml unset the binding and doesn't restore them [11:32] didrocks: yes so 2 issues :) [11:32] davmor2: so, we do have bug #1283191 [11:32] bug 1283191 in The Sound Menu "Sound indicator doesn't change when using hw buttons" [Undecided,Confirmed] https://launchpad.net/bugs/1283191 [11:32] which isn't new [11:32] yes [11:32] the other "new" one is? [11:33] (with 5.2) [11:33] didrocks: yes and the new one is 52 only and is https://bugs.launchpad.net/ubuntu/+source/android/+bug/1293478 [11:33] Ubuntu bug 1293478 in android (Ubuntu) "Volume buttons no longer function correctly since #238 mako/flo" [Undecided,Confirmed] [11:33] excellent, thanks [11:36] hiya, is it normal if i have the CI train in read-only mode? [11:36] or can someone edit/re-config an MP list for me? [11:38] tsdgeos, looks like some template magic brokeness on those platforms [11:38] tsdgeos, not sure if you managed to figure out something [11:38] no [11:39] i'm still trying to figure out what to do after i log into the porter machine :D [11:39] i tried creating a chroot but as i have no root nor fakeroot can't do that [11:40] yea, i didn't even try porters, last time i checked i didn't have access to them :) [11:41] i asked for it [11:41] and got it [11:41] btu not sure what to do next :D [11:41] and that's why i didn't ask for the access :) [11:44] didrocks, ok to publish row 45? or are we still in no-publish mode? [11:45] I've given tsdgeos advice by /msg [11:45] mhr3: those looks fine & safe enough for me [11:45] Mirv: mind looking in case of packaging changes and so on ^ [11:47] didrocks: http://paste.ubuntu.com/7107703/ [11:47] uploaded [11:48] cjwatson: perfect, thanks! [11:48] now, let's wait for jdstrand to update the click apparmor side [11:49] mhr3: with pete on holidays, only tedg will be able to fix a test failure on arm64 for the hud, I guess? [11:49] arm64 porter boxes are a bit trickier, since the arm64 kit we have isn't IS-managed yet [11:50] But if somebody needs it, ask me and I can point you in the right direction [11:51] didrocks, sounds about right [11:51] didrocks: ping? sorry can you help with that read-only issue? [11:51] didrocks, well.. marcus might be able to too [11:51] dbarth: "that read-only issue"? [11:51] mhr3: didrocks: ok will look [11:51] ci-train spreadsheet is r-o for me [11:52] dbarth: nothing changed, are you sure you are logged in with the right acount? [11:52] account* [11:52] cjwatson: it was the hud issue, Mirv told it built here, so great :) [11:52] doh, was logged out :/ sorry [11:54] didrocks: "the hud issue" not sure what that means, but if it's fixed then marvellous [11:55] cjwatson: yeah, in addition to dep on this dee-qt, there were some test failure on arm64 [11:55] ah, caught up on #ubuntu-devel [11:55] yeah, I know [11:56] yes, tests passed in the version for arm64 which is nice https://launchpadlibrarian.net/169517619/buildlog_ubuntu-trusty-arm64.hud_13.10.1%2B14.04.20140314-0ubuntu1_UPLOADING.txt.gz [11:56] mhr3: mediascanner2 published [11:56] yeah, I just hope it's not flaky [11:57] anyway, so dee-qt is the biggest offender remaining to have a clearer view on the archive [11:58] didrocks: so I guess stabilising 5.2 and then what is the next big thing new scopes? [11:58] mhr3: oh, and you were also the lander for line 26 hud/libdbusmenu-qt. also done, after I did some extra testing myself. [11:59] davmor2: oxide? [11:59] davmor2: yeah, the icon theme change should be minor, so it's building/landing as wel speak [11:59] Mirv: ohhhhh oxide would be nice :) [11:59] the risky transitions happening are, AFAIK: [11:59] - scopes [11:59] - oxyde [11:59] - python3 AP switch [11:59] isnt the latter done yet ? [12:00] ogra_: not enabled yet [12:00] ah, k [12:00] at least, it's easy to disable [12:00] and don't even need an image rebuild [12:00] yeah, i was kind f assuming that xnox had ripped py2 AP out already :) [12:01] Mirv, thx [12:01] heh, not yet! I think we can get that (if ready) as soon as we promote the first 5.2 image [12:01] hmm, sad ... so the unity-system-compositor spinner works ... but only if i start it manually [12:01] seems mterry forgot to add the --spinner option in his code ... [12:02] but at least it works stable and the session comes up fine [12:02] ogra_: maybe that was on purpose? he wanted more testing before enabling it [12:02] (it should use the spinner graphics from recovery though :P ) [12:02] didrocks, well, his MP description talks about a --spinner option ... but there is none in the code [12:02] ah :) [12:03] so fail yeah ;) [12:03] i guess just an oversight [12:03] and it works stable on all devices, so shouldnt be an issue to add it === josepht changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: josepht | CITrain support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone [12:16] * cjwatson files RT#68468 to spruce up our porter box setup a bit [12:22] didrocks, davmor2, popey: https://bugs.launchpad.net/unity8/+bug/1283191 reassigned to unity8/retitled [12:22] Ubuntu bug 1283191 in Unity 8 "Indicator's sliders stop updating after manual interaction" [High,Confirmed] [12:22] seb128: ah, great, thanks! :) [12:22] thanks seb128 [12:22] Saviq, ^ let me know if we are wrong, but that seems an issue on the qml side [12:23] seb128: thanks for looking into it :) [12:23] seb128: hmm? That was about the hardware buttons but you changed it to be about interacting with the qml sliders? [12:23] yw! [12:23] Laney, it's about the slider which stops moving to reflect the actual value [12:23] Laney, it seems the classic "qml undo the property binding if you manually interact with the widget" [12:24]