[11:41] <oSoMoN> Saviq, should I request a silo for https://code.launchpad.net/~osomon/qtubuntu/qkeyevent-native-virtual-key/+merge/282515 , or do you prefer to add it to an existing/future silo along with other qtubuntu changes?
[13:58] <Saviq> oSoMoN, I'll land it
[14:23] <oSoMoN> Saviq, thanks
[15:29] <dandrader> greyback, got a qtmir crash in MirBufferSGTexture::bind() while running uitk AP tests with *trunk*
[16:03] <oSoMoN> Saviq, greyback: looking at bug #1534682, it seems that when connecting an external monitor to a phone via slimport the screen information is not updated, could you guys help me debug/fix that issue?
[16:09] <greyback> dandrader: eek
[16:09] <greyback> are you investigating?
[16:09] <dandrader> greyback, no yet....
[16:09] <dandrader> *not
[16:10] <greyback> oSoMoN: have you plugged USB power into the slimport cable?
[16:11] <oSoMoN> greyback, I don’t know as I’m waiting for my slimport adapter to arrive, the issue was reported by bfiller, let me get him here to comment
[16:13] <greyback> oSoMoN: how is UA string chosen?
[16:13] <greyback> the Qt Screens info is not being updated currently
[16:13] <greyback> if you're relying on that, then that's the problem
[16:13] <greyback> I'm working on that code right now
[16:13] <oSoMoN> greyback, based on screen diagonal size
[16:14] <oSoMoN> greyback, well that’s good news, do you have an ETA for a fix?
[16:14] <greyback> oSoMoN: about 1-2 weeks
[16:15] <oSoMoN> would that qualify for OTA-9.5 ?
[16:15] <oSoMoN> or too late?
[16:15] <greyback> that's what I'm trying for
[16:16] <oSoMoN> excellent!
[16:17] <oSoMoN> bfiller, greyback was asking earlier whether you had plugged USB power into the slimport cable?
[16:17] <greyback> nah, ignore that. I misunderstood the issue
[16:17] <bfiller> oSoMoN, greyback: no I didn't
[16:17] <greyback> you're getting the external display working, so that's fine
[16:17] <greyback> main issue is that qt isn't being told the screen changed
[16:18] <bfiller> greyback: interesting though when launching the browser while the external display is connected it doesn not report the correct screen dimenions
[16:18] <bfiller> dimensions
[16:20] <greyback> bfiller: qt just giving you dimensions of one display, not necessarily the right one. Also, many displays fail to report their correct physical dimensions
[16:21] <bfiller> greyback: ok
[17:09] <mterry> tedg, when using your app-object branch, imports are a little weird
[17:09] <mterry> tedg, #include <application.h> isn't very descriptive
[17:09] <mterry> tedg, and I have to do that because it's not included from the main ubuntu-app-launch.h one
[17:10] <tedg> mterry: Shouldn't it be "ubuntu-app-launch/application.h" ?
[17:11] <mterry> tedg, it should be, but you don't have that extra directory.  You have libubuntu-app-launch-2... But that's not for import lines, that's just for the .pc file to set -I for ya
[17:11] <tedg> mterry: Ah, okay, so it needs to install a layer deeper.
[17:11] <mterry> tedg, yeah that could work
[17:30] <mterry> tedg, what's this TypeTagger situation with AppID::package and such?  How do I treat those as strings?
[17:31] <tedg> mterry: foo.value()
[17:32] <mterry> tedg, ah thanks
[20:42] <Saviq> mzanetti, bug #1521518
[21:42] <cimi> tsdgeos, Saviq https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1536372
[22:25] <faenil> mzanetti: let me know if you need anything to fix the "no apps start" or if I have to setup usertesting laptop using vivid..
[22:26] <mzanetti> faenil, I've saw it on cimi's laptop yesterday
[22:26] <faenil> cool
[22:27] <faenil> does that mean you'll fix it soon? :D
[22:27] <cimi> faenil, va' a letto
[22:27] <cimi> è tardi
[22:27] <cimi> :D
[22:27] <faenil> cimi: eh c'hai ragione... :P
[22:29] <mzanetti> isn't it just half past 10?
[22:29] <faenil> yep
[22:29] <cimi> that's when mzanetti usually starts hacking indeed :)
[22:29] <faenil> fighting kernel issues on  nokia n950 :P
[22:29] <mzanetti> 10... that's when I put the baby to bed
[22:31] <faenil> just moved gcc to a new versions...and it doesn't boot anymore..(same kernel!)
[22:31] <faenil> version*
[22:32] <faenil> mzanetti: anyway, let me know...I don't care about black screen on logout, but not being able to start any app at all is a real blocker
[22:32] <faenil> usertesting lead wanted the laptop ready tomorrow...
[22:32] <faenil> of course that's not possible now, but the sooner the better
[22:34] <mzanetti> faenil, you are usertesting the desktop?
[22:34] <faenil> mzanetti: yeeeeeees :P
[22:34] <mzanetti> ok, next time let us know like, say, a week beforehand at least :D
[22:34] <faenil> mzanetti: I knew it like 3 days ago
[22:34] <faenil> and I reported that bug, when, 2 days ago? :P
[22:35] <faenil> the usertesting is next week
[22:35] <faenil> but the lady has to play with the stuff to write the test plan I guess
[22:54] <aaronraimist> I am on 16.04 and I am trying to build unity8 but when I do ./run.sh it says "Unity8 is already running, please stop it first"
[23:00] <mzanetti> aaronraimist, hmm... the run.sh is probably broken... what are you trying to do? just playing around with it, or intending to fix some specific thing?
[23:01] <aaronraimist> mzanetti: I am trying to fix a task as part of the Google Code-in program.
[23:02] <mzanetti> aaronraimist, ah ok, what/where?
[23:03] <aaronraimist> mzanetti: https://bugs.launchpad.net/ayatana-design/+bug/1066963, maybe I should actually be trying to build unity7?
[23:04] <mzanetti> aaronraimist, right... that bug is about unity7
[23:05] <aaronraimist> mzanetti: OK, thanks, I'll try to build unity7