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