=== chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun [05:55] Good morning :) [06:11] nik90: ping [06:19] nik90: your'e most wanted seems :) [06:19] zsombi: hehehe :D [06:38] good morning [07:17] mihir: just woke up. Give me few mins and we can talk [07:17] dholbach: Morning :) [07:17] hi mihir [07:17] nik90: no issues, just wanted to confirm just Jenkis is not function or not? [07:23] nik90: ok, so the alarm issue is the following: after you edit an enabled alarm and right after that you want to disable it, QOrganizer does not remove neither audio nor visual reminders. So we have a problem with either using QOrganizer or with it itself. [07:23] gooooooooood morning all :) [07:23] :) [07:24] zsombi: oh seems like a serious issue [07:24] nik90: yup, I'll try to remove the reminders in a loop, perhaps we have them in the occurrences somehow still [07:24] zsombi: we are thinking of replacing the old clock with new clock app this evening [07:25] nik90: good thinking :) [07:25] nik90: yet I have a MP with ~400 lines... [07:25] nik90: but this is not solved yet in there... [07:25] Wow [07:25] nik90: only the model update, but at least the flicking is not there anymore :) [07:26] nik90: do U remember the bug still? [07:26] zsombi: the flicker issue or the status bug? [07:26] nik90: both, seems this goes down both to Alarm services... [07:27] zsombi: I haven't created one for the alarm status issue yet [07:28] nik90: ok, please do so, as it seems we have more problems with that... [07:28] OK. Will ping you with both the bug reports [07:30] nik90: ok, the loop seems to fix it :) [07:30] nik90: so we will have a fix for that as well :D [07:31] nik90: nice way to close the week ;) [07:32] zsombi: :D [07:32] zsombi: but now I have to wait for the next promoted image :P [07:33] nik90: yes, but at least you know that will come, right? ;) [07:33] yes indeed :) [07:33] zsombi: okay first bug is at https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1359112 [07:33] Ubuntu bug 1359112 in Ubuntu UI Toolkit "Alarm model is updated after every change causing all the listview items to be repainted" [High,Confirmed] [07:34] nik90: I marked the bug #1359112 for rtm14 as well [07:36] zsombi: bug number 2 https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1360101 [07:36] Ubuntu bug 1360101 in Ubuntu UI Toolkit "Toggling an alarm status right after editing it results in the alarm status being reverted" [Undecided,New] [07:37] nik90: shouldn't this be also tagged as rtm14? [07:37] zsombi: yup, I just added it [07:41] zsombi: let me know when you want me to test it. [07:41] nik90: uhh, damn it! of course it has twice the reminders! I'm adding those every time you modify anything on teh alarm, so if you update the alarm 3 times, you will not be able to disable only after the 3rd time! ASO... damn! [07:42] zsombi: yeah I sort of noticed that but figured I was imagining things [07:42] nik90: so the fix is even easier :) [07:43] woohoo :D [07:50] zsombi: could this be why saving an alarm takes some time? [07:53] nik90: yes, it could [07:53] nik90: so, I have to break the MR in a chain of fixes, so it might take some time to land it [07:54] nik90: but I'l focus on that so we get it done ASAP [07:54] zsombi: ok [07:54] zsombi: I will wait for that to land and the next promoted image before doing the replacement since I think this is a high priority issue. [07:55] nik90: well, as you wish... [07:56] zsombi: I feel that updating a single alarm which causes the whole alarmmodel to be refreshed is rather detrimental to the user experience. Might as well wait since a fix is in sight. [07:58] popey: what do you think I should do? ^^ [08:06] zsombi: can you define "some time" ? [08:07] nik90: ping [08:07] mzanetti: pon [08:07] pong* [08:07] nik90: so there has been some activity on the timezone bug we reported [08:07] nik90: seems this is only an issue in the toString() method [08:08] nik90: I'm inclined to say we should keep clock-reboot updated in the store and switch the apps when we know we won't regress the clock experience. [08:08] nik90: and happens because the JavaScript spec dictates that toString() must print the time in the local timezone [08:08] mzanetti: ah ok [08:09] mzanetti: so what does upstream recommend for our issue? [08:09] nik90: could you test if you get the correct time by not using toString(), e.g. by using time.hours() etc [08:09] nik90: upstream agrees that this isn't good, but not sure if violating the JavaScript spec is better [08:09] nik90: so discussion still ongoing [08:10] mzanetti: ok, I will try this out in another 30 mins and see if that resolves it [08:10] nik90: sure, no rush [08:10] popey: ack [08:10] nik90: if that's really the case, we could write our own toString() method for time [08:11] popey: it won't regress clock since the old clock app also has the issue. But I don't see any harm in waiting. May be next week we can push it out. [08:11] so we could do something like TimeUtils.toString(dataObject) which then takes TZ info into account [08:11] popey: since in the landing email, lucakz mentioned about 2 promoted images per week [08:12] thats the target [08:16] jdstrand, beuno: if you could take a look at https://code.launchpad.net/~dholbach/click-reviewers-tools/1355215/+merge/231569 later on, that'd be nice :) [08:34] The accounts policy is still reserved? Goodness, it's been eons. Is it still reserved in 14.10? [09:02] nik90: https://code.launchpad.net/~akiva/ubuntu-calendar-app/no-upcoming-events-visible-fixed/+merge/231758 [09:02] why jenkis is not triggiring ? [09:02] triggering* [09:02] any problem with it ? [09:03] mihir: not sure.. I checked it as well [09:03] mihir: did you try top approving? [09:03] i thought it might be because of empty commit message, i did seet that too [09:03] nik90: nope , i thought lets Jenkis run and i'll top approve then after. [09:04] Well when u top approve it usually runs the test before merging [09:04] nik90: let me try to do that [09:04] Good morning all; happy Friday, and happy Hug Your Boss Day! :-D [09:05] JamesTait: seriously, Hug your boss day , hehehe [09:06] mihir: nik90 jenkins didn't do it because akiva isn't in the calendar dev team [09:07] popey: but mihir approved it though [09:07] popey: ohhh , is it.. i never noticed this.. [09:07] (not top approve) [09:07] popey: i just did Top Approve. [09:07] nik90, to be fair, whenever I go to a sprint, as soon as I see my boss it's usually the first thing we do. [09:08] popey: i believe even when i push MR to some other app , it does run Jenkis , if I am not wrong..:| [09:08] JamesTait: erm wrong person :P [09:08] dont think so [09:08] nik90, heh, sorry! I meant mihir. [09:09] JamesTait: I got it :) [09:09] mihir, didn't happen in Malta, though. In Malta we were roomies, and he was already in bed when I arrived. That would just have been weird. [09:10] popey: hmmm , so is it mandatory that , user has to be dev group ? [09:10] JamesTait: hehehe , that's nice :) [09:11] mihir: for automatic jenkins yes [09:11] mihir: but jenkins can be triggered manually too [09:12] popey: how can we do that ? [09:12] i dont think you guys can do that, needs auth in jenkins [09:12] if you expect more contributions from akiva then I can add him to the team. [09:13] nik90: popey: "some time"means around a week [09:13] zsombi: thanks [09:13] JamesTait: you changed the format of https://search.apps.ubuntu.com/api/v1/search?q=architecture:armhf&size=1000&page=1 overnight? [09:13] broke my script ☹ [09:14] zsombi: ack. Let me know when you have individual MPs to test. I can test on utopic desktop and comment in the MR. [09:14] popey, we sent out the warning mails over a month ago. ;) [09:14] * popey looks for the mail [09:15] * JamesTait does too. [09:15] found it, thanks. [09:15] ☹ [09:16] * popey disables the cron job till he can fix it [09:16] popey, you have it in a bzr branch somewhere, don't you? I remember you sharing it a while back. [09:17] http://paste.ubuntu.com/8112777/ [09:18] JamesTait: not sure if my boss would like a hug :p [09:40] popey, http://paste.ubuntu.com/8112919/ [09:40] * JamesTait takes a note to do something with lp:~jamestait/+junk/click-support-tools [09:50] nik90: 201 had the popup's that trigger location service some people get fixes easily others don't but we don't have a full location stack currently so that is why it might not look to be working, however in 203 the location trusted service isn't even running so it will never get a location fullstop. [09:51] davmor2: ok, I was trying to use location services in the clock app and test an MP. I will root to 201 and do that [09:52] nik90: I'm pretty sure that tvoss will not be happy about it being broken so it will likely be up and running pretty quickly :) [09:53] davmor2: I am keeping an eye on the bug report as well [09:54] davmor2, did the convo with tvoss continue yesterday? [09:54] davmor2, or did it stop where i left? [09:55] brendand: stopped but I know how tvoss feels about it :) [09:56] davmor2, right. he didn't comment on why the service didn't start? [09:56] brendand: no just thanked me for the bug [10:00] I'm seeing "tcsetattr: Invalid argument" when I try to run application on device. Then deployment fails with code 134. Thoughts? [10:02] Before that, I get: cannot set terminal process group (-1): Invalid argument [10:03] wellsb, grep DEN /var/log/syslog ... [10:03] looks like you miss the right apparmor profiles for your app [10:04] No results for DEN [10:05] Sorry, the failure code is 139 [10:07] Nope, 134 was right. 139 when I tried the 14.10 framework, but I can't do that because I'm on 14.04 [10:07] The apparmor profiles is a possibility, because I've excluded Accounts because it's reserved, but it really should be there [10:21] It's been a while since I've touched this app. It's happening with several other older apps. Perhaps something has changed in QT. This should be fun. [10:21] wellsb: are you using kits to run them on device? [10:21] I am not [10:21] I saw your video earlier, though. Could you shoot me that link again? [10:21] wellsb: http://developer.ubuntu.com/start/ubuntu-sdk/using-device-kits/ [10:22] Thanks [10:22] yw [10:22] mihir: if I fix https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1357315, can you help me fix the AP tests? [10:22] Ubuntu bug 1357315 in Ubuntu Calendar App "Move the Save and Cancel button in the new event page to the header" [Medium,Triaged] [10:23] mihir: I can create a common calendar branch that we both can hack on [10:23] nik90: sure, we can do that , but we need to fix AP wherever it is being used. [10:23] mihir: shouldn't fixing the function which clicks the button in the emulators.py file fix it everywhere? [10:24] nik90: usually it should be , just push that MR, i'll fix that [10:24] mihir: either way let me fix it first, and then do some manual testing before worrying about the AP. [10:24] mihir: thnx [10:24] mihir: will ping you with the MR when finished [10:24] nik90: sure , thanks. [10:40] zsombi: does https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/10-alarm-data/+merge/231847 need review from clock-app devs too? [10:41] t1mp: no, that not [10:41] zsombi: could it break clock-app if the alarms are not stored/loaded correctly? [10:41] t1mp: read the commit message :) [10:42] ahh [10:42] t1mp: it states it only affects memory manager, and that is a fallback only [10:42] t1mp: it easesmanual testing, to see the saved data [10:42] mihir: https://code.launchpad.net/~ubuntu-calendar-dev/ubuntu-calendar-app/move-save-cancel-buttons [10:43] mihir: I tests creating/editing new events [10:43] mihir: worked as expected. No regressions afaik. Let's fix the AP tests now [10:43] nik90: thanks, i'll start working on this once i reach home :) [10:43] mihir: ok [10:45] zsombi: ok, happroving [10:46] t1mp: thx!! [10:46] bzoltan: are we doing a landing? [10:46] t1mp: the next two must be tested by the clock app [10:46] bzoltan: or we wait till monday? [10:46] Does anyone know how I could detect the host arch inside a click chroot. Previously I could run dpkg-architecture -qDEB_HOST_ARCH but that doesn't seem to work anymore [10:47] t1mp: I just requested a silo [10:47] bzoltan: cool [10:47] t1mp: I wish to land as soon as possoble, but we still have like 5 MRs waiting to be merged [10:48] t1mp: I will keep updating the landing MR as the new staging versions happen [10:49] bzoltan: with the new versioning of the packages it is so much easier to see what will be part of the new landing :) [10:49] bzoltan: why land as much as possible? we can do another landing next week [10:49] bzoltan: the landing will already include 15 MRs [10:50] * t1mp gets a bit nervous from huge landings. Smaller ones are easier to find issues in case something is broken [10:50] popey: how do you test calendar app on a device? [10:51] popey: do you install the click manually on a device? I cannot run calendar app on phone using QtC since desktop file is missing apparently. [10:51] adb push foo.click /tmp [10:51] phablet-shell [10:51] pkcon install-local /tmp/foo.click [10:52] ah kk [10:52] nik90: then add a desktop file? [10:52] t1mp: it has 2 .desktop files strangely [10:53] actually it is weird that we require *desktop* files to run something on a *phone* :) [10:53] maybe .desktop is not the best name [10:53] hehe [10:54] ☻ [10:56] popey: http://imgur.com/lCbDpYK [10:57] nik90: OOOH! [10:57] * popey hugs nik90 [10:59] * nik90 hugs back [11:05] t1mp: there was no small landing because nothing went to the staging for 8 days.. all the queued MRs started to land just in the last 2-3 days [11:08] bzoltan: I know. I tried to say that what we don't get in this landing, we'll get in the next one :) [11:09] t1mp: that is why I gave up and started the landing...I still do not have the silo, that is why I said that I will update the landing branch from the staging if it gets new revisions. as it just got the 2006 [11:09] 1206 [11:13] t1mp: and you should not be nervous :) I have run the UITK test suite like 6 times in the last 3 days ...no sign of regression [11:14] nik90: t1mp this file is not required , com.ubuntu.calendar_calendar.desktop.in.in ? [11:15] mihir: no we need it [11:15] mihir: the other .desktop is what we added to temporarily fix the qtc issue. [11:15] nik90: then i can see only one desktop file , [11:15] bzoltan: ok :) [11:16] mihir: there is another com.ubuntu.calendar.desktop [11:16] nik90: okay , i thought that required for the running into desktio [11:16] mihir: Are there any special packages that need to be installed to run calendar app tests? [11:16] desktop* [11:16] mihir: I get AttributeError: 'module' object has no attribute 'ModuleImportFailure' [11:17] ImportError: No module named dateutil [11:18] nik90: on your local machine ? [11:18] mihir: yes [11:19] python-dateutil [11:19] daker: i believe it is by default in python , isn't it? [11:19] no [11:19] apparently not, since it is installing it now [11:20] mihir: this should be added to the debian/control file then [11:20] https://labix.org/python-dateutil [11:21] t1mp: nik90: https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/20-alarm-model-update/+merge/231863 [11:21] * mihir makes note to add in control file [11:21] mihir, daker: anything for File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 628, in useFixture [11:21] fixture.setUp() [11:22] zsombi: quick question. [11:22] nik90: t1mp: lemme resubmit [11:22] zsombi: what signal do I use to update "next alarm in ..hr and .. mins" ? [11:22] zsombi: previously I used onModelReset [11:23] nik90: probably , this https://pypi.python.org/pypi/fixtures [11:23] zsombi: but if that isn't fired after an alarm is modified, then is there any other signal i can track? [11:24] mihir: hmm apparently I already python-fixtures installed [11:24] nik90: python-testtools & python-fixtures [11:24] daker: both installed already [11:24] t1mp: nik90: ok, a bit cleaner MR [11:25] nik90: depends from whom do you want to catch teh signal [11:25] zsombi: I tracked the onModelReset signal in the AlarmModel{} object [11:25] nik90: from model, you get beginModelReset/endModelReset when the whole model is refreshed (item is added/deleted) or dataChanged() if an item data changes [11:26] nik90: the dataChanged() will come after we land the MP above [11:26] zsombi: ok I track onModelReset and dataChanged() signal to track additions/editing to alarms [11:26] onDataChanged() [11:26] nik90: hmmm [11:26] nik90: t1mp: https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/20-alarm-model-update/+merge/231867 [11:27] zsombi: testing [11:27] nik90: we could eventually implement separate signals for additionand removal, as the QAbstractItemModel has such a func! [11:28] nik90: it would be even faster to refresh a model... then to reload teh whole data [11:28] nik90: but that's further optimizations we can do after RTM, not that critical yet, aint it? [11:28] zsombi: well I am just interested in known when the alarm count changes, an alarm is edited (enabled/disabled) so that I can accordingly update my "next active alarm in " string. [11:29] nik90: yup [11:29] zsombi: we can leave the refresh model to after RTM yes [11:29] nik90: now, the last MR for the alarm update ;) [11:29] nik90: you getting any specific error , or it just says what you have mentioned [11:29] nik90: in ~30-40 mins [11:30] mihir: http://paste.ubuntu.com/8113542/ [11:30] zsombi: sweet [11:30] nik90: you need to install dummy service for address book [11:30] nik90: so this won't be needed anymore https://code.launchpad.net/~nik90/ubuntu-clock-app/fix-status-revert/+merge/231690 [11:31] zsombi: yes. I will reject and remove it [11:31] nik90: sorry , it seems you have that too [11:31] mihir: how do you know? [11:31] mihir: I can check on my side if you tell me the package name for it [11:31] nik90: it runs or it never runs any AP ? [11:32] mihir: well it doesn't :) [11:32] ohhhkie [11:33] mihir: actually one sec [11:33] mihir: it seems to be running some of the tests [11:33] nik90: could you check this pacakge , address-book-service-dummy ? [11:33] mihir: like the month scrolling [11:34] mihir: it is testing switching between month view to year view and others..let it finish and see where the failures are [11:34] nik90: not sure it'll resolve issue, but this is must too. [11:34] for new event , it should break when you it tries to add guest. [11:35] mihir: ah ok [11:36] nik90: hmm, if that is the case this should resolve issue. [11:36] mihir: ok so it ran 24 tests, 4 of which failed. I am guessing those were the new event ones [11:36] mihir: yup I didnt have that package [11:36] mihir: ok so 2 packages to add to debian/control [11:37] * mihir mihir updates the list for debian/control [11:39] mihir: hmm same error :/ no worries I will wait until the evening to work with you and balloons on it. [11:40] nik90: ohh [11:44] nik90: it gives same errors , http://paste.ubuntu.com/8113542/ ? [11:44] mihir: oh [11:44] mihir: trunk or my branch? [11:45] nik90: trunk, branch shouldn't work until we make changes to Ap [11:45] mihir: I made a blind change to fix the AP test...here is me hoping that worked :P [11:45] nik90: hahaha okay , [11:45] mihir: I fixed the _save() function in the emulator.py. That should fix it. but let's see what jenkins says [11:47] nik90: yeah, that should. [11:48] zsombi: https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/20-alarm-model-update/+merge/231867 causes clock app to crash when toggling the alarm status. [11:48] zsombi:The Alarm data has been updated with an unregistered item! [11:48] zsombi: The program has unexpectedly finished. [11:48] zsombi: I can get gdb log if you want [11:48] nik90: no need [11:48] nik90: that's a qFatal() causing it [11:48] nik90: intentionally [11:49] zsombi: oh ok [11:49] nik90: but that's bad [11:49] nik90 that means the alarm you update is not registred or has different cookie! [11:49] zsombi: I also noticed that after creating a new alarm, the saved alarm switches reinitialized meaning the entire listview repainted [11:50] zsombi: any insights regarding these bugs , https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1357323 [11:50] Ubuntu bug 1357323 in Ubuntu UI Toolkit "There is no way to control text alignment of the button" [Undecided,Confirmed] [11:50] nik90: well, alarm creation still resetd the whol elist... if we don;t want that, we have to inpmement that as well [11:51] mihir: did not had time for that yet, sorry [11:51] zsombi: ah ok, this is just when updating an existing alarm? [11:51] nik90: yep [11:51] zsombi: this would be enough for now. [11:51] nik90: the rest must be done differently [11:51] zsombi: okay no issues :) [11:52] nik90: but, the failure you get worries me... [11:52] do you get that when you update the alarm? [11:52] zsombi: yup, regardless of what property I updated [11:52] nik90: lemme se with mem manager... [11:53] nik90: ok, we have a problem with EDS backend then!!! [11:54] nik90: could you try it locally with memory backend? [11:54] already trying [11:55] zsombi: no happens with mem manager as well for me [11:55] nik90: huhh? it passes safely 4 me... wth? [11:55] zsombi: I added ALARM_MANAGER=memory to the run environment in QtC project tab [11:56] nik90: and you see the warning from alarm manager that memory will be used? [11:57] nik90: ah, it does not display that if env var is used... [11:57] erm no [11:57] nik90: well, you can see th ediff if you have different alarms in teh different DBs [11:58] meeting... [11:59] bbl [11:59] k [12:03] nik90: that works :D [12:03] mihir: woohoo...blind edits works! [12:04] nik90: hahaha :) let me review that. [12:04] mihir: my fingers are itching to improve the new event design [12:04] mihir: its too cluttered in my opinion :/ [12:04] nik90: we have already asked to designers [12:05] mihir: true, but did popey say you guys would get it before RTM? [12:05] nik90: i know it is too cumbersome [12:05] what are we talking about specifically? [12:06] nik90: nope [12:06] popey: the New Event page design [12:06] I think that'll come with a later calendar redesign, not in the short term [12:15] nik90: i was thinking to bifurcate the repetitions to some other page. [12:16] mihir: I have a revamp in mind. Small minor stuff but I think it will make it look better. [12:16] mihir: I will push it as a common branch again so we both can hack on it together [12:16] nik90: could you do mockup for me ? [12:17] mihir: I will try to create a sample app with just the UI code and show it to you [12:19] wellsb: if it's apparmor you would see denials in the logs (eg, 'grep DEN /var/log/syslog' and look for denials at the time of the failure) [12:20] wellsb: and fyi, the accounts policy group can now be freely used with 14.10 frameworks [12:20] oh, really!? [12:20] yep, you can thank mardy [12:20] time for wellsb to dust off Blackjack [12:21] it now has trust session prompting [12:21] (online accounts that is) [12:21] so I adjusted the click-reviewers-tools earlier in the week and when we came out of traincon-0, I updated the policy (1.2.21) [12:25] dholbach, sorry, will review today [12:26] jdstrand: thanks. [12:38] DanChapman: hey, let me know how it goes with the connectivity-api [12:39] DanChapman: are you planning to use Qt or QML bindings? === renato is now known as Guest21428 [12:54] * dholbach hugs beuno [12:54] :p [12:59] Wellark, hey :-) thanks for getting it in so quickly. I'm planning to use the Qt bindings so i'll let you know how I get on with it. I can test the QML bindings on it as well if that will help test it? [13:02] mordning all [13:04] o/ [13:04] Does anyone familiar with the calendar-app have some time to look at this MP: https://code.launchpad.net/~gerlowskija/ubuntu-calendar-app/fix-for-bug1350605 It's already been reviewed, but the reviewer (Kunal) couldn't test it because of environmental issues and requested someone else take a look. [13:05] nik90: the other bug: https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/30-alarm-update-fix/+merge/231882 [13:05] nik90: I'm still trying to repro the previous failure, unsuccessfully [13:05] zsombi: but you were able to reproduce it on EDS though? [13:05] nik90: not on that, I had not tried it on that yet [13:05] zsombi: if I want to set the ALARM_MANAGER=EDS, would that work? [13:06] nik90: eds, not EDS [13:06] ok. [13:08] zsombi: so whatever run environment options I provides, the alarms shown are the same. Maybe I am not changing the alarm backend properly. Let me try via console [13:08] nik90: then most likelly you are not using teh right backend [13:09] nik90: was the package name qtdeclarative-eds? [13:10] DanChapman: I've tested the service, it works at least for networking status [13:10] zsombi: qtorganizer5-eds [13:10] the bandwith limitation detection is still missing from the backend [13:10] DanChapman: could you file a bug about that? it would help [13:11] DanChapman: if you are going to use the Qt bindings then be aware that the libconnectivity-qt1.pc is broken [13:11] the fix is on it's way [13:11] but might be that we can't get it in today [13:11] depending on how low we are on silos [13:12] nik90: ok, with EDS I'm getting it as well, but not with memory manager [13:12] DanChapman: https://code.launchpad.net/~jpakkane/connectivity-api/pkgconfig/+merge/231834 [13:13] DanChapman: you can work around it by not using the .pc file, but manually adding the necessary flags, if you want to try it out before the fix lands [13:13] zsombi: I did "set ALARM_MANAGER=memory" in the console but it doesn't seem to swtich the backend. [13:13] nik90: btw, I've noticed that no matter what env var I'm setting, it's not gonna use it :/ [13:13] Can I target 14.10 framework if I'm running 14.04? [13:13] nik90: set? not export? [13:13] zsombi: oh [13:14] nik90: how you launch it from console? [13:14] command line pls [13:14] DanChapman: just set -I/usr/include/connectivity-api/qt1 -I/usr/include//qt5/QtDBus -I/usr/include//qt5/QtCore -I/usr/include//qt5 /usr/lib//libconnectivity-qt1.so.1 -lQt5DBus -lQt5Core -fPIC to your build scripts [13:14] zsombi: I create a builddir and then inside it run "cmake .. && make" [13:15] you probably have that arch stuff already [13:15] zsombi: once done, I do "qmlscene ../app/ubuntu-clock-app.qml -I backend/" [13:15] *qt5 stuff [13:15] nik90: ok, then simply do ALARM_MANAGER=memory qmlscene ...... and the rest [13:15] DanChapman: setting -I/usr/include/connectivity-api/qt1 -lconnectivity-qt1 should be enough [13:15] zsombi: ah ok [13:16] zsombi: "ALARM_MANAGER=memory qmlscene ../app/ubuntu-clock-app.qml -I backend/" didnt change it [13:17] nik90: what the heck???! [13:17] zsombi: let me start fresh and see [13:17] daaaaaaaaaaaaaaaaamn!!!!! [13:17] nik90: ALARM_BACKEND=memory [13:19] zsombi: lol that worked [13:19] zsombi: u r right, issue is with EDS ;/ [13:19] nik90: I was affraid of that :( [13:19]