[08:05] <tsdgeos> pstolowski: ping
[08:25] <tsdgeos> ltinkl: ping
[11:55] <dandrader> greyback_, qtmir part of the mouse pointer work is pretty much done. only some optional polishing left.
[11:56] <dandrader> greyback_, unfortunately I had to come up with our own cursor API as Qt's is not expressive enough :(
[11:56] <dandrader> greyback_, but I'm supporting both
[11:57] <greyback_> dandrader: hey. What is Qt's API lacking?
[11:57] <dandrader> more shapes in its cursor shape enum
[11:57] <greyback_> dandrader: also, could you please run the unity8 strip-tags on your qtmir branches, it's got infected somehow
[11:57] <dandrader> greyback_, for resizing we use 8 different cursors
[11:58] <dandrader> greyback_, but Qt's enum has only 4
[11:59] <greyback_> naturally
[11:59] <greyback_> oh well, your approach sounds like the best thing to do
[11:59] <greyback_> have you tested it on the nexus7, i.e. the rotated scene?
[12:00] <dandrader> greyback_, so far tested only in my touchscreen laptop with qml-demo-shell. Added a rotation button there
[12:00] <dandrader> greyback_, next step is unity8
[12:00] <greyback_> cool
[12:01] <dandrader> greyback_, how is the app lifecycle silo going?
[12:02] <greyback_> dandrader: landed a precursor, now trying to get it going. the gcc5.0 transition complicates things
[12:03] <dandrader> greyback_, so you said that some qtmir branch of mine got bogus tags from unity8?
[12:03] <greyback_> dandrader: not just yours, seems they've been in there for a while
[12:04] <greyback_> for i in `ls`; do cd $i && strip-tags.py . && strip-tags.pg :push && cd ..; done
[12:04] <greyback_> might help
[12:04] <greyback_> oops, typo
[12:05] <dandrader> wow, even some compiz tags...
[12:06] <dandrader> greyback_, so, do you have an ETA for landing them?
[12:07] <greyback_> dandrader: hope to get silo in working order soon, then will test. ETA maybe Thurs
[13:16] <kgunn> davmor2: hey, on this gcc5 bug you just logged, i better ask  - how exactly are you testing ? e.g. is this a "special" unity8 that's been built against gcc5 ?
[13:17] <kgunn> cause the real unity8 built against gcc5 is stuck in migration (like everything else :-/ )
[13:17] <kgunn> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#unity8
[13:17] <davmor2> kgunn: there is a chnnel
[13:18] <kgunn> davmor2: where is that channel coming from ?
[13:18] <kgunn> i guess, i'm questioning it, since gcc5 is turned on in wily and migration is borked...shouldn't we be focused on the wily channel ?
[13:19] <davmor2> kgunn: see pm
[14:02] <tsdgeos> ltinkl: ping
[14:02] <tsdgeos> cimi: to unittests changes for you!
[14:02] <tsdgeos> https://code.launchpad.net/~aacid/unity8/expandable_test_fixes/+merge/266875
[14:02] <tsdgeos> https://code.launchpad.net/~aacid/unity8/testExpandableHeights/+merge/266876
[14:13] <mhall119> kgunn: if I wanted to keep up with the daily development of Unity8, can I do that on vivid or do I need to upgrade to wily?
[14:14] <mhall119> by "keep up" I mean build and run the latest trunk for dev/testing, not daily use
[14:23] <kgunn> mhall119: for latest, it would be vivid+o, so ubuntu-touch/rc-proposed/ubuntu(or something.en whatevah)
[14:24] <kgunn> mhall119: also unity8 source code is the same in wily and vivid+o today...but all the devices on the horizon are targeting vivid+o
[14:28] <tsdgeos> yeah vivid won't work, you need vivid+ppa
[14:29] <tsdgeos> anyone know why the CI can't compile anymore? https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-wily/171/console
[14:29] <tsdgeos> sil2100: Mirv: ↑ ?
[14:30] <sil2100> tsdgeos: you'd have to poke cihelp on #ubuntu-ci-eng
[14:30] <tsdgeos> k
[14:30] <tsdgeos> looks more like a "wily is borked" to me
[14:30] <tsdgeos> trying to install a wily chroot to check
[14:31] <greyback_> tsdgeos: yep, I suspect the gcc4.9/5.0 transition is the blame. It's not done yet
[15:06] <ltinkl> greyback_, tsdgeos: doesn't Ubuntu use a "mass rebuild" from time to time?
[15:06] <tsdgeos> i think it does yeah
[15:07] <greyback_> ltinkl: yep, but it tends to happen after debian does it, so there's an intermediary stage where stuff can be broken
[15:08] <mhall119> kgunn: so I can run the vivid overlay PPA on my laptop?
[15:09] <tsdgeos> mhall119: yes
[15:09] <kgunn> mhall119: afaik you should be able to...
[15:09] <tsdgeos> at least it works for me :D
[15:09] <kgunn> there you go :)
[15:11] <mhall119> cool, will give that a try when I get home, I'd like to get to where I can contribute code and help others get setup to do the sae
[15:11] <mhall119> same
[15:12] <tsdgeos> mhall119: https://unity.ubuntu.com/getinvolved/development/unity8/ should be uptodate
[15:13] <mhall119> tsdgeos: should be, but since I'm usually the one who updates it, I wouldn't count on it :)
[15:13] <tsdgeos> mhall119: since i updated it 2 weeks ago
[15:13] <tsdgeos> you're wrong and it should be fine
[15:13] <tsdgeos> but yeah don't count on anything you don't do yourself! it's the rule i follow
[15:13] <tsdgeos> that's why i'm single :D
[15:13] <tsdgeos> :(
[15:14] <mhall119> lol
[15:15] <mhall119> tsdgeos: thanks of updating to include the overlay PPA info :)
[15:16] <greyback_> dandrader: hey, can I get this added to your todo list: https://bugs.launchpad.net/qtubuntu/+bug/1481389
[15:16] <greyback_> shouldn't take long
[15:18] <dandrader> greyback_, high priority?
[15:18] <greyback_> dandrader: not as high as your current cursor work
[15:18] <dandrader> greyback_, ok
[15:45] <greyback_> cimi: hey, on your bluetooth problems, have you pinged seb128 for help? Don't give up!
[15:45] <greyback_> I know we have a bluez expert who can help too
[15:46] <cimi> greyback_, yeah, normal bluetoothd doesn't give me anything
[15:46] <cimi> greyback_, what I should try now is to patch system settings source code to spit out debug info from somewhere in the stack
[15:46] <cimi> greyback_, but I suppose this is something I should not spend time doing...
[15:47] <greyback_> cimi: no, that's not your job ;)
[15:47] <greyback_> but there are people who should be able to investigate on your behalf
[15:47] <seb128> if you don't do it nobody else is going ot
[15:47] <seb128> to
[15:47] <seb128> without access to the hwd I doubt
[15:47] <greyback_> seb128: aren't there debug info he can give you that would help?
[15:47] <greyback_> hcitool etc
[15:48] <seb128> I guess, much easier with access to the hwd though
[15:48] <seb128> and everybody is overbusy
[15:48] <seb128> so I doubt we are going to do much for a device specific issue atm
[15:48] <greyback_> fair. I'd just like a way for someone to be able to report useful info to us tho
[15:49] <cimi> yeah, buying a device and being asked to recompile debug info inside some services in order to help...
[15:50] <cimi> I am saying that we need an easy way to debug bluetooth devices and such
[15:50] <cimi> or at least be able to collect info we need so if other people buy kbd that don't work we can fix them without having the device
[15:53] <greyback_> cimi: have you tried pairing it with any other device?
[16:02] <cimi> greyback_, works on desktop, android, ios
[16:02] <cimi> greyback_, it's probably a system settings touch issue
[16:04] <greyback_> cimi: ok. Well sounds like nobody is going to fix it for you right now
[20:06] <dandrader> ltinkl, ping
[20:12] <dandrader> ltinkl, sent you an e-mail instead
[20:51] <mhall119> kgunn: running silo0 on my phone, it keeps freezing up with unity-system-compositor using 100% CPU
[20:54] <mhall119> is this a known problem and is there a way to fix it without re-flashing?
[20:54] <kgunn> mhall119: yep, it's got a fix on the way...prolly tomorrow
[20:54] <mhall119> ok, reflashing it is then
[20:55] <kgunn> well...you could apt-get update with that silo still in your apt sources list
[20:55] <kgunn> we're just fixing that silo in place
[20:55] <mhall119> oh, is it in the PPA?
[20:58] <mhall119> apt-get update && upgrade only shows 4 oxide packages to be upgraded
[21:01] <mhall119> kgunn: is there a way to get that fix now? If not, I'll reflash and try again tomorrow
[21:02] <kgunn> mhall119: best to try again tomorrow....
[21:02] <kgunn> mhall119: and yeah...silo 0 is where we'll keep working, until we land everything
[21:02] <kgunn> we have a goal to eventually not use silo 0
[21:03] <mhall119> will do, thanks
[23:19] <a1fa> has anybody noticed a bug with the terminal, where terminal border, and top menu would dissapear?
[23:20] <a1fa> literally leaving terminal window on its own, unmovable but focusable
[23:23] <a1fa> 2nd issue is unity launcher fails to appear, mostly when working with terminals and chrome browser, going back and forth between the two