[07:29] <mhr3> no sil today?
[07:29] <mhr3> no didrocks today?
[07:32] <mhr3> seb128, i have a branch where tests fail on jenkinks, but if i build the pkg locally everything is fine, any ideas what's up with that?
[07:32] <mhr3> talking about
[07:32] <mhr3> https://code.launchpad.net/~mhr3/libunity/scope-result-in-python/+merge/180158
[07:32] <seb128> mhr3, today is a national holiday in France
[07:32] <mhr3> seb128, but you're in germany! :)
[07:33] <seb128> mhr3, yeah, still not going to work :p
[07:33] <seb128> mhr3, how did you try? in a pbuilder?
[07:34] <mhr3> does bzr bd use pbuilder? :)
[07:34] <mhr3> if so then yes :)
[07:34] <seb128> not by default
[07:34] <mhr3> then no :P
[07:34] <seb128> well, build env are different from your env
[07:35] <seb128> they don't have a dbus session, nor xorg, nor internet access
[07:35] <seb128> do you rely on session stuff or on an internet access?
[07:35] <mhr3> i tried it also in a chroot which doesn't have any of that either
[07:35] <mhr3> succeeded there
[07:36] <seb128> mhr3, is that lp:libunity ?
[07:36] <mhr3> well, it does have internet, but we don't need that
[07:36] <mhr3> seb128, link above ^^
[07:36] <seb128> ha
[07:36] <seb128> let me try
[07:41] <seb128> mhr3, http://paste.ubuntu.com/5988032/
[07:41] <seb128> mhr3, that's what I get building on a porter box chroot
[07:41] <mhr3> seb128, exactly what i needed, and now what is a porter box?
[07:42] <seb128> mhr3, ssh porter-amd64.canonical.com
[07:42] <seb128> mhr3, if you have access/your ssh key configured
[07:42]  * mhr3 checks
[07:43] <mhr3> nope, it doesn't like me
[07:43]  * apw is trying to find a good example (preferably in python) of something which is a client of the messaging menu.  i had thought it would be libindicate, but none of the example with that do a thing
[08:00] <Saviq> mzanetti, hey, a small one that will hopefully help with quaternourly release
[08:01] <mzanetti> :D
[08:01] <Saviq> https://code.launchpad.net/~saviq/unity8/ap-passphrase-wait-for-focus/+merge/180293
[08:01]  * Saviq forgot to paste...
[08:02] <Saviq> Mirv, ping
[08:02] <mzanetti> Saviq: looks sane to me. but did we actually have issues with this?
[08:02] <Saviq> mzanetti, http://10.97.0.1:8080/job/autopilot-saucy-daily_release/1010/label=autopilot-ati/artifact/results/autopilot/videos/unity8.shell.tests.test_lock_screen.TestLockscreen.test_can_unlock_pin_screen%20%28Desktop%20Nexus%2010%29.ogv
[08:03] <Saviq> mzanetti, log excerpt http://pastebin.ubuntu.com/5988076/
[08:03] <mzanetti> Saviq: I wonder why there is a unity7 running in this video
[08:03] <Saviq> mzanetti, because that's how the machines are set up there
[08:03] <mzanetti> ah... right... they are not using our vms
[08:04] <Saviq> mzanetti, they're real hardware
[08:04] <mzanetti> and still this sort of performance issues?
[08:04] <Saviq> that's the other way around
[08:04] <Saviq> well, maybe not
[08:04] <mzanetti> not really, no
[08:04] <Saviq> you know, recordmydesktop has its toll
[08:05] <mzanetti> hmm...
[08:09] <Mirv> Saviq: pong
[08:10] <Mirv> Saviq: just filed https://bugs.launchpad.net/unity8/+bug/1212580
[08:10] <Mirv> it seems you're on to it already? :)
[08:10] <Saviq> Mirv, yeah, somewhat
[08:10] <Saviq> Mirv, I hope I have a solution for the unstable test
[08:10] <Saviq> Mirv, but then there's unity8 crashing
[08:11] <Mirv> Saviq: there's another one in addition to the unlock pin screen, test_hide_hud_click
[08:11] <Saviq> Mirv, you think we could get /var/crash out of the machines?
[08:11] <Saviq> Mirv, yup, that's a crash, and we can't seem to reproduce
[08:12] <Mirv> Saviq: I'm on the nvidia machine, where that test consistently fails, but the /var/crash is empty
[08:13] <Saviq> Mirv, can you `ulimit -c unlimited` and see if core is dumped?
[08:14] <Mirv> Saviq: I guess that'd need setting globally somehow, for the next run. trying.
[08:15] <Saviq> Mirv, /etc/security/limits.conf
[08:15] <Saviq> Mirv, can you unhook the machine for some manual debugging?
[08:18] <Mirv> Saviq: ok added, is there some sort of need to reload something?
[08:18] <Mirv> Saviq: sorry, no idea, I haven't ssh:d to the machines before and I don't know what didrocks has used to do
[08:18] <Saviq> Mirv, no, if it crashes it should dump a "core" file in $CWD
[08:19] <Saviq> Mirv, that we can then use to see the crash locally
[08:20] <Mirv> Saviq: after the current test run on normal unity finishes, I can rerun the unity8 tests before 10 UTC when the next run starts
[08:20] <Mirv> Saviq: meanwhile, you don't have any nvidia machines that could possibly bring up the issue?
[08:20] <Saviq> Mirv, I'm running one
[08:20] <Saviq> Mirv, no crashes here
[08:21] <Mirv> ok
[08:24]  * Saviq runs the test 20 times to see if anything comes up
[08:28] <Mirv> meanwhile the intel machine looks to have gone down
[08:29] <Mirv> Saviq: do you happen to know which people have access to fix something like that? I think jibel was perhaps one, but he is also on holiday today
[08:30] <Mirv> trying IS..
[08:32] <Mirv> nope, need QA team people
[08:33] <Saviq> Mirv, got the crash
[08:33] <Saviq> or at least *some* crash
[08:34] <Saviq> with an unusable core ;|
[08:42]  * Mirv progresses on finding people to get intel machine back up
[08:44]  * greyback_ moving to office
[09:44] <jamesh> Mirv: hi.  sil2100 was helping out with getting mediascanner into the archive, but I think he is on holiday today.  Are you able to help, or do you know anyone who could?
[09:52] <Mirv> jamesh: it's starting to look impossible for today for me, but possibly kenvandine / robru when they wake up. sil2100 is also back tomorrow.
[09:52] <jamesh> thanks.
[09:52] <Mirv> jamesh: furthermore, the QA lab is currently broken so we wouldn't progress on getting to saucy archives anyhow.
[09:55] <Saviq> Mirv, can we re-run unity8 to see if the fix we merged has that one issue sorted?
[09:55] <jamesh> thostr_: ^^^ so we might have trouble getting mediascanner in the archive today
[09:56] <Mirv> Saviq: I tried, I got some other error and was just about to try again. I'm not sure if the intel machine being broken could prevent the other machines from being used as well.
[09:58] <Mirv> Saviq: now it runs on the nvidia machine, let's see
[09:59] <Mirv> what a nice day to everything get broken when half of the people is on holiday. the usual :)
[10:09] <Mirv> Saviq: at least the ati machine succeeded without that one error it had earlier (although not everytime). as expected nvidia machine still getting the other error, but I don't see coredump on the machine. but I gathered your hunt for that problem is also progressing?
[10:17] <Saviq> Mirv, :)
[10:51] <Cimi> mzanetti, did you have a look at the issue with autopilot?
[10:51] <Cimi> mzanetti, or can you tell me how to see the bug? (make test what?)
[10:54] <mzanetti> Cimi: I couldn't reproduce yesterday. today I merged trunk and jenkins failed again.
[10:54] <mzanetti> didn't investigate yet
[11:10] <mzanetti> Saviq: I hope this will do https://code.launchpad.net/~mzanetti/unity8/more-robust-lockscreen-tests/+merge/180316
[11:12] <Cimi> who can help me in imports?
[11:12] <Cimi> I'm working on the settings app, I have issues in importing the plugins
[11:22] <mzanetti> Cimi: I think I fixed the autopilot test... lets see if it works on jenkins
[11:22] <mzanetti> Cimi: whats the issue with the imports?
[11:23] <Cimi> mzanetti, I am in settings app
[11:23] <Cimi> mzanetti, from that branch
[11:23] <Cimi> actually, I'll be back in 10
[11:28] <Saviq> Mirv, ok so there's a fix for the crasher https://code.launchpad.net/~mhr3/unity/only-valid-filters
[11:29] <Saviq> Mirv, already approved and autolanding now
[11:30] <Saviq> Mirv, and https://code.launchpad.net/~mzanetti/unity8/more-robust-lockscreen-tests/+merge/180316 should be even more robust for the other issue (even though it passed I saw in the logs in other tests that the issue is still there)
[11:31] <Saviq> Mirv, I assume we need to wait for the intel machine to come up first?
[11:32] <Saviq> greyback_, ping, got a minute?
[11:32] <greyback_> Saviq: yep
[11:32] <Saviq> greyback_, mumble?
[11:32] <greyback_> Saviq: am there
[11:36] <Mirv> Saviq: awesome! yeah, the -intel issue is now breaking up the rest.
[11:36] <Mirv> Saviq: after it hopefully gets fixed kenvandine will be the next one from our team to wake up
[11:36] <Saviq> Mirv, got i
[11:36] <Saviq> t
[11:37] <Saviq> Mirv, did you start working early to cover the gap or something?
[11:38] <Saviq> Mirv, you're just +1 from me, but you sound like you're EOD'ing soon :)
[11:38] <Cimi> mzanetti, so from this https://code.launchpad.net/~cimi/ubuntu-system-settings/welcome-wizard
[11:38] <Cimi> mzanetti, I tried adding
[11:38] <Cimi> import Ubuntu.SystemSettings.Language 1.0
[11:39] <Cimi> for example in Pages/WelcomePage.qml
[11:39] <Cimi> and run qmlscene -I /path/to/plugin/language MeetUbuntu.qml
[11:39] <Cimi> no luck :-\
[11:41] <Saviq> Cimi, for plugins to load
[11:41] <Saviq> Cimi, they have to be on the same path
[11:42] <Saviq> Cimi, that you provide with the "import" statement
[11:42] <Saviq> Cimi, so import Ubuntu.SystemSettings.Language 1.0
[11:42] <Saviq> Cimi, equals "Ubuntu/SystemSettings/Language"
[11:42] <Saviq> or, if versioned
[11:42] <Saviq> "Ubuntu/SystemSettings/Language.1"
[11:42] <Saviq> "Ubuntu/SystemSettings/Language.1.0"
[11:42] <Cimi> mmm valid
[11:42] <Saviq> in reverse priority order
[11:42] <Saviq> Cimi, so without installation, you won't get that path
[11:43] <Cimi> Saviq, but there's the qmldir, no?
[11:43] <Saviq> Cimi, doesn't matetr
[11:43] <Cimi> ok
[11:43] <Saviq> Cimi, it needs to be on the path
[11:43] <mzanetti> if this is located in /home/cimi/foobar/Ubuntu/SystemSettings/Language you'd need to do -I /home/cimi/foobar
[11:43] <Cimi> thought was responsible of registering the name
[11:43] <Saviq> Cimi, the "module" in qmldir is just for protection
[11:44] <Saviq> Cimi, not related to where QML looks for the module
[11:45] <Saviq> Cimi, because .po files don't seem to respect the install prefix
[11:45] <Saviq> Cimi, I'm afraid it's easiest if you just go `bzr bd`
[11:45] <Saviq> build the packages and install whichever ones you need
[11:46] <Cimi> Saviq, but the plugin is private
[11:46] <Saviq> Cimi, so?
[11:46] <Cimi> Saviq, at least that's what web told me
[11:46] <Cimi> *seb
[11:46] <Saviq> Cimi, still has to be installed
[11:46] <Saviq> Cimi, you just need to point QML2_IMPORT_PATH at it
[11:46] <Saviq> or -I if using qmlscene
[11:46] <Saviq> at the private path, that is
[11:46] <Cimi> ah ok
[11:46] <Saviq> Cimi, and you should read http://qt-project.org/doc/qt-5.0/qtqml/qtqml-syntax-imports.html
[11:47] <Saviq> Cimi, if you're not doing anything with the plugins, just install settings-app
[11:47] <Cimi> I need to use them
[11:47] <Cimi> but not changing for the moment
[11:48] <Saviq> ubuntu-system-settings is the package name
[11:49] <Cimi> Saviq, perfect works with  /usr/lib/x86_64-linux-gnu/ubuntu-system-settings/private
[11:50] <Cimi> Saviq, wondering how I get this to be dynamically loaded
[11:50] <Saviq> Cimi, you'll need a c++ main() around it, just as system-settings has
[11:50] <Cimi> Saviq, maybe not using qmlscene but a main.cpp?
[11:50] <Cimi> ok
[11:50] <Saviq> yup
[11:50] <Saviq> Cimi, qmlscene isn't meant to be used "in production"
[11:51] <Cimi> Saviq, thought it was for us
[11:51] <Saviq> Cimi, it's only there for development/debugging purposes
[11:51] <Cimi> Saviq, thought zoltan wanted
[11:51] <Cimi> use qmlscene as much as possible
[11:51] <Cimi> unless c++ is really a requirement
[11:51] <Saviq> Cimi, qmlscene-*like*
[11:51] <Saviq> Cimi, qmlrunner, whatever
[11:51] <Saviq> Cimi, just one that didn't have all the dev/dbg options qmlscene has
[11:51] <Saviq> Cimi, not sure what's the status of it btw
[12:05] <Saviq> Cimi, see #sdk for an explanation on qmlscene
[12:42] <greyback_> Saviq: could you please look: https://code.launchpad.net/~gerboland/unity-mir/fix-platform-api-pkgconfig-change/+merge/180329
[12:42] <greyback_> it would unblock me
[12:43] <Saviq> greyback_, on it
[12:43] <greyback_> ta
[12:44] <Saviq> greyback_, approved, although not sure why that change in platform-api
[12:45] <greyback_> Saviq: thanks!
[12:56] <mhr3> Saviq, did something happen to scrolling? seems jerky now
[12:57] <Saviq> mhr3, apps running?
[12:57] <mhr3> Saviq, on desktop even
[12:57] <mhr3> then again, seeing what my screen is doing it might just as well be the intel driver...
[13:01] <Saviq> mhr3, nope, not seeing that on the desktop
[13:01] <Saviq> mhr3, can you confirm another thing for me, though
[13:01] <Saviq> mhr3, launch unity8
[13:01] <Saviq> mhr3, go to home scope, drag down
[13:02] <Saviq> mhr3, does the first category get stuck 1/2 down the screen for you?
[13:03] <mhr3> Saviq, i've seen it do that a few times... but doesn't right now
[13:04] <Saviq> mhr3, how about in ./run -- -fullscreen ?
[13:04] <Saviq> mhr3, or actually, GRID_UNIT_PX=12 ./run
[13:06] <mhr3> the search bar moved in the middle of the screen, then fixed itself after scrolling
[13:06] <mhr3> but still doesn't get stuck
[13:08] <Saviq> mhr3, bad news, it's category overrides causing that...
[13:08] <mhr3> Saviq, how, what now?
[13:09] <Saviq> mhr3, not sure yet, but reverting it does get rid of the issue
[13:09] <mhr3> no way
[13:10] <mhr3> told you i've seen it long before i even thought about category overrides
[13:11] <Saviq> mhr3, I agree it might just be triggering something
[13:11] <mhr3> but i'm not denying that using actual scopes that give us non-mocked data might trigger it
[13:13] <dednick> mhr3: i think this should get rid of any duplicates. https://code.launchpad.net/~nick-dedekind/unity/scopeview.model.resync/+merge/180335
[13:14] <mhr3> a sec, the screen corruption is getting worse
[13:15]  * mhr3 wants stable intel driver
[13:24] <Saviq> mhr3, sorry, I'm afraid it really is category overrides :/ it must be tricking the proxy model somehow
[13:24] <Saviq> mhr3, it only affects apps and home, too - they're the only ones with overrides
[13:27] <mhr3> Saviq, so you're unable to rep the issue if you comment out the overriding?
[13:27] <Saviq> mhr3, applying http://paste.ubuntu.com/5989012/
[13:27] <Saviq> mhr3, is enough to fix
[13:27] <Saviq> mhr3, let me try commenting in qml
[13:31] <mhr3> plus they're the only ones which don't have static data
[13:31] <Saviq> mhr3, ok, so commenting out in QML isn't enough
[13:32] <Saviq> dednick, standup
[13:32] <mhr3> Saviq, there you go, then it can't be the root cause
[13:32] <Saviq> mhr3, it can
[13:32] <Saviq> mhr3, if the categories themselves are doing tricks
[13:32] <Saviq> mhr3, doing http://paste.ubuntu.com/5989012/ does help
[13:33] <Saviq> mhr3, I'll drill down on it after the standup
[13:33] <Saviq> s/the/our/
[13:33] <mhr3> if nothing calls the method, the code paths you removed are never triggered
[13:33] <mhr3> yea, i have a call now too :)
[13:56] <Saviq> mhr3, http://paste.ubuntu.com/5989111/ fixes
[14:01] <Saviq> mhr3, not sure why, yet, but it does
[14:01] <asac> dednick: your packages didnt help
[14:01] <asac> fwiw
[14:02] <dednick> asac: hm. ok, i'll need to look into the issue some more.
[14:02] <dednick> asac: thanks for testing
[14:02] <asac> i hope i didnt make a mistake
[14:03] <dednick> asac: is there anything specific you were doing to reprocude?
[14:03] <asac> dpkg -i failed first
[14:03] <asac> i ran apt-get install -f to resolve the conflicts after
[14:03] <asac> and then dpkg -i worked, but i got it after reboot again
[14:03] <asac> dednick: it must be pretty easy to reproduce... what i did (without beying systematic) was:
[14:03] <asac> 1. use look at indicators
[14:03] <asac> 2. open two apps without closing each
[14:03] <asac> and then kill them
[14:04] <asac> let me see :)
[14:04] <asac> if i can be better
[14:08] <Saviq> mhr3, don't get me wrong - you might as well be triggering an issue in the dash ListView
[14:08] <mhr3> Saviq, hmm, could you try to change the signal connections to QueuedConnection?
[14:09] <Saviq> mhr3, http://paste.ubuntu.com/5989165/ didn't help
[14:12] <mhall119> thostr_1: Saviq: when will the Click scope be available?  Now that the Click app store is going online, it'd be nice to complete the story
[14:14] <thostr_1> mhall119: mhr3 is working on it, should be any day now
[14:14] <mhr3> Saviq, i still think that the count being present in the model is just wrong
[14:14] <mhall119> awesome
[14:18] <Saviq> mhall119, or you can enable it already
[14:19] <Saviq> mhall119, gsettings get com.canonical.Unity.Dash scopes
[14:19] <Saviq> mhall119, add 'click/click.scope' and `gsettings set com.... scopes "[...]"`
[14:20] <Saviq> mhall119, but yeah, it will show up in the apps scope asap, too
[14:20] <mhall119> cool, let me grab my USB cable and try
[14:20] <Saviq> mhr3, which model would that be? Categories?
[14:20] <mhr3> Saviq, yea
[14:21] <mhr3> Saviq, do you have a moment for hangout?
[14:21] <Saviq> mhr3, sure
[14:21] <mhr3> i want to see what you see
[14:22] <Saviq> mhr3, ah then let me make a video
[14:22] <mhr3> we can also chat about it in the hangout :)
[14:28] <mhall119> Saviq: I'm getting a dbus-launch error when trying to set gsettings from adb shell
[14:28] <Saviq> mhall119, as phablet
[14:29] <mhall119> I was
[14:31] <mhall119> that's okay, the terminal-app on my phone + bash history meant I could easily re-run it from a session with dbus
[14:31] <mhall119> restarting
[14:32] <mhall119> Saviq: mhr3 does click/click.scope pull from the online store, or just already installed click packages?
[14:32] <Saviq> mhall119, search for "*"
[14:33] <mhall119> Saviq: nothing
[14:33] <Saviq> mhall119, works here
[14:33] <mhall119> do I need to login to something?
[14:34] <mhall119> IIRC, anonymous access to the click store was still in discussion
[14:35] <Saviq> mhall119, on staging it's enabled
[14:35] <Saviq> mhall119, alecu should be able to help
[14:36] <mhall119> on a different note, I *love* that indicators are tabs now, makes so much more sens
[14:36] <mhall119> sense
[14:36] <alecu> mhall119: click scope gets results from the click webservice, yes
[14:37] <mhall119> alecu: ok, so I got my xda-developers-app published in the click store yesterday, but searching for it doesn't show any results
[14:37] <mhall119> and, in fact, search only shows the "Installed" category header
[14:37] <Saviq> mhr3, here's videos of the two issues I noticed: http://ubuntuone.com/0y3o0lPEaWsVBEP6gdiJdd http://ubuntuone.com/4AGFEchm7D1QqVvDtrbmZb
[14:37] <alecu> mhall119: if you don't get results from searching for "*", may I ask you for the click scope logs? they are in ~/.cache/unity-scope-click.log
[14:37] <mhr3> Saviq, yep, downloading them, it's super slow
[14:37] <Saviq> mhr3, right.. u1
[14:38] <mhr3> yea...
[14:38] <alecu> mhall119: did you publish it in the production or staging web service? the scope is still using the staging one.
[14:39] <mhall119> alecu: http://paste.ubuntu.com/5989261/
[14:39] <mhall119> alecu: ah, I'm not sure to be perfectly honest, let me ask
[14:40] <alecu> mhall119: it should show up for you in https://developer.staging.ubuntu.com/dev/click-apps/
[14:41] <mhall119> alecu: it's on https://myapps.developer.ubuntu.com/dev/click-apps/3/
[14:41] <mhall119> so I guess that means production
[14:42] <alecu> right
[14:42] <mhall119> any easy way for me to point it at production?
[14:43] <alecu> mhall119: not yet, it means recompilation on the device
[14:43] <alecu> mhall119: I plan to point it to production soon
[14:44] <mhall119> ok
[14:44] <Saviq> oh looks like intel is back
[15:09] <alecu> mhall119: here's the bug to have the scope returning results from production: https://bugs.launchpad.net/unity-scope-click/+bug/1212709
[15:10] <alecu> mhall119: and we'll probably have it fixed in a few hours
[15:13] <mhall119> alecu: that would be great, thanks!
[15:13] <mhall119> alecu: let me know when it's ready for me to test
[15:15] <alecu> sure
[15:17] <alecu> tedg: ping
[15:18] <tedg> alecu, Howdy
[15:18] <alecu> tedg: I see that you've mentioned a few times in the app-devel list the click hooks. May I ask you some question about them?
[15:18] <alecu> I can't find cjwatson today, so that's why I'd like to ask you :-)
[15:20] <mhr3> Saviq, it's interesting that you always get apps after files, it's vice versa for me
[15:20] <tedg> alecu, Ah, he's at debconf
[15:20] <tedg> alecu, Sure
[15:20] <alecu> tedg: so, I need to tell the .desktop files that are generated by the click installer from other .desktop files created by other means
[15:20] <Saviq> mhr3, less files? ;)
[15:21] <alecu> tedg: I was thinking of having the click desktophook add a new X-something field to the .desktop file when it's created on .local/share/applications
[15:22] <alecu> tedg: (all of this may be needed so the click scope can show the right previews for apps that were installed from .clicks)
[15:22] <alecu> tedg: do you think that it makes sense to do it in the click desktophook?
[15:23] <mhr3> alecu, talked with thomas, he's inclined to do the de-dup where both scopes will provide the same results
[15:23] <tedg> alecu, You can create a new one, but that might end up in a race condition with the desktop file creation hook (there's not guarantee on ordering).  Probably best to do it in the hook that creates it.
[15:23] <tedg> alecu, That hook is in upstart-app-launch, it's pretty simple.
[15:25] <tedg> alecu, Though, if you made them with constant names, and didn't modify the desktop file (which makes sense I think for your use-case) you could do an independent hook.
[15:26] <alecu> mhr3: ack
[15:28] <mhr3> alecu, one problem is that it could be racy
[15:28] <mhr3> like if the click scope takes a while to return results
[15:28] <alecu> mhr3: it surely will take a while, since it always needs to hit a webservice
[15:29] <mhr3> alecu, even for the installed apps??
[15:29] <alecu> mhr3: you are right, not for installed apps
[15:30] <alecu> mhr3: right now the slow part will be the spawning of "click list --manifest"
[15:31] <mhr3> yea, i hope we don't need to do that on each keypress :)
[15:32] <alecu> mhr3: yes, I surely cache that :-)
[15:33] <katie> mterry, hello
[15:33] <katie> mterry, you joining our hangout?
[15:34] <mterry> katie, omg, yes
[15:34] <alecu> tedg: looking at desktop-hook.c, I see that X-Ubuntu-Application-ID is being added to .desktops already
[15:35] <alecu> tedg: that should only be present for click packages, right?
[15:37] <tedg> alecu, Yup
[16:09] <Cimi> mzanetti, I have issues with the import here lp:~cimi/ubuntu-system-settings/welcome-wizard_app
[16:09] <Cimi> it's qmake things...
[16:18] <Cimi> anyone could help me on qmake?
[16:18] <mzanetti> Cimi:
[16:18] <mzanetti> re
[16:19] <Cimi> re
[16:19] <mzanetti> Cimi: so. what's the issue?
[16:19] <Cimi> mzanetti, Error: Error while loading page: qrc:/qml/Pages/WelcomePage.qml:19 module "Ubuntu.SystemSettings.LanguagePlugin" is not installed
[16:21]  * mzanetti compiles and installs deps
[16:24] <mzanetti> Cimi: ok... I compiled it and ran system-settings
[16:24] <mzanetti> its a bit empty
[16:25] <mzanetti> what do I need to do to reproduce the issue?
[16:30] <Cimi> mzanetti, not system settings
[16:30] <Cimi> mzanetti, you need to run wizard
[16:31] <mzanetti> Cimi: ok. can see the issue
[16:31] <Cimi> it must be something with the import
[16:31] <Cimi> and the PLUGIN DIR definitions
[16:32] <Cimi> I use in main.cpp
[16:43] <mzanetti> Cimi: so...
[16:43] <mzanetti> If you want to run it with qmlscene, you need to create a directory structure
[16:43] <mzanetti> I created for example: plugins/Ubuntu/SystemSettings/LanguagePlugin/
[16:43] <mzanetti> and copied the lib and the qmldir file into that
[16:43] <Cimi> mzanetti, I want to run with main.cpp
[16:44] <mzanetti> then running qmlscene wizard/qml/main.qml -I plugins/ works
[16:44] <Cimi> mzanetti, because the plugin is private
[16:44] <mzanetti> what you mean with that?
[16:44] <Cimi> mzanetti, that the directory changes
[16:44] <Cimi> it's somewhere in the system
[16:44] <mzanetti> you must have such a directory structure
[16:45] <mzanetti> doesn't matter if its somewhere in the system. it needs to be Ubuntu/SystemSettings/LanguagePlugin
[16:45] <mzanetti> as a directory structure
[16:45] <mzanetti> otherwise you need to link stuff statically and use qmlRegisterType in your main.cpp instead of the plugin.cpp
[16:47] <Cimi> mzanetti, it has this structure
[16:47] <Cimi> mzanetti, but I want to set the path from the main file
[16:47] <Cimi> mzanetti, on my system is /usr/lib/x86_64-linux-gnu/ubuntu-system-settings/private
[16:52] <mzanetti> Cimi: you'd need to export QML2_PLUGIN_DIR=/usr/x86_64-linux/gnu/ubuntu-system-settings/private/
[16:52] <mzanetti> Cimi: then, if it has this directory structure in there it should work
[16:52] <Cimi> mzanetti, I want to set it in main.cpp
[16:52] <Cimi> mzanetti, look at how system settings is doing
[16:52] <mzanetti> you can't. I might differ from system to system
[16:52] <Cimi> mzanetti, no
[16:53] <Cimi> mzanetti, it works for system settings app
[17:14] <mzanetti> Cimi: ok. found it
[17:15] <mzanetti> Cimi:  they add a define in qmake
[17:15] <mzanetti> Cimi: DEFINES += -DPLUGIN_PRIVATE_MODULES=/ubuntu-system-settings/private
[17:15] <mzanetti> and then view.engine()->addImportPath(PLUGIN_PRIVATE_MODULE_DIR); in the main.cpp
[17:16] <mzanetti> which I think is quite ugly
[17:16] <mzanetti> but ok. it works
[17:23] <mzanetti> Cimi: I see you're doing the same. whats the problem actually?
[19:42] <alecu> mhall119: I've just installed the XDA Developers App with the very latest unity-click-scope
[19:43] <alecu> mhall119: but it fails when starting the app, like this:
[19:43] <alecu> [unity-scope-click] - DEBUG: click-scope.vala:171: cannot execute application: No manifest found for app_id: com.ubuntu.developer.mhall119.xda-developers-app
[19:43] <alecu> mhall119: that means that the app id in the webservice does not match what's on the click manifest
[19:44] <alecu> the manifest says "com.ubuntu.developer.mhall119.xda-developers"
[19:45] <alecu> but the webservice says "com.ubuntu.developer.mhall119.xda-developers-app"
[19:46] <alecu> I think changing the manifest and rebuilding the .click is the faster way to fix it
[19:58] <mhall119> ok
[20:43] <Cimi> mzanetti, it is not working for me...
[20:43] <Cimi> mzanetti, indeed the warning
[20:43] <mzanetti> Cimi: works here
[20:43] <Cimi> °_°
[20:43] <mzanetti> Cimi: did you install it?
[20:43]  * Cimi rebuilds
[20:43] <Cimi> mzanetti, installed what?
[20:43] <mzanetti> sudo make install
[20:43] <Cimi> but what?
[20:44] <Cimi> mzanetti, wizard or the app?
[20:44] <mzanetti> everything in that repo
[20:44] <mzanetti> plugins at least
[20:44] <Cimi> they are installed
[20:44] <Cimi> anyway I'll have a look tomo morning
[20:44] <mzanetti> to /ubuntu-system-settings ?
[20:44] <Cimi> yes
[20:44] <mzanetti> hmm... works for me
[20:45] <mzanetti> Cimi: did you run sudo make install?
[20:45] <mzanetti> or did you just copy some files manually?
[21:01] <mhall119> alecu: Changes can not be accepted and published at this time. Please try again later.
[21:01] <mhall119> :(
[21:01] <mhall119> just uploaded 0.1.2 with the corrected package name
[21:02] <Cimi> mzanetti, I installed the package
[21:02] <Cimi> mzanetti, wizard isn't
[21:02] <Cimi> mzanetti, probably.. the plugin definition is not the same
[21:02] <Cimi> the define
[21:02] <Cimi> because the package has /usr/lib somewhere
[21:03] <Cimi> while the local build has a different path, that's why it doesn't work
[21:03] <mzanetti> right. the package has a prefix set
[21:03] <Cimi> (didn't try but makes sense)
[21:03] <mhall119> alecu: btw, the form where I have to approve the change doesn't give me that error message, it just reloads the form with no indication of failure
[21:03] <mhall119> it's not until I go back to the Overview that I see all of those red errors
[21:03] <mzanetti> this is btw why I think its not a good idea to have the path hardcoded this way
[21:04] <mzanetti> Cimi: you can edit the common-project-config.pri and change the prefix to what the package installs to
[21:04] <Cimi> good point
[21:05] <mzanetti> Cimi: or you uninstall the package and install your build with make install