[09:24] <tsdgeos> greyback_: you killed the space! https://ci-train.ubuntu.com/job/ubuntu-landing-019-1-build/189/console
[09:25] <greyback_> tsdgeos: whoa
[10:39] <tsdgeos> dednick: you can top approve https://code.launchpad.net/~feng-kylin/unity8/adjustColorToHighlightingIndicator/+merge/266837 without CI anywya
[10:39] <tsdgeos> CI is borked and doesn't even compile so..
[10:39] <dednick> tsdgeos: ok
[10:40] <dednick> done
[10:44] <sidi> Hi. I'm running a modified version of the Unity shipped in 15.04, which logs some WM events to Zeitgeist by using libzeitgeist directly. I also have a modified GLib that logs app launches to Zeitgeist. The modified GLib works fine on its own with GTK3 apps, and the modified Unity works fine most of the time. However, if I run my modded unity with my modded glib I get a deadline on GType initialisation code as soon as a call to libzeitgeist is done. Do
[10:44] <sidi>  you guys do anything specific with GLib internals in Unity? Do you overload how type initialisation works in any way?
[12:38] <dandrader> ltinkl, the scripts kept telling me the branch was clean. so I deleted it and pushed again: https://code.launchpad.net/~dandrader/unity8/removeForceActiveFocus/+merge/267020
[12:57]  * a1fa wishes the launcher would not bug out all the time
[13:10] <tsdgeos> cimi: no top approve of my branches?
[13:10] <cimi> tsdgeos, want to see again this tag thingy
[13:11] <tsdgeos> oki
[13:13] <cimi> tsdgeos, branched again I still have to delete this tag
[13:13] <cimi> tsdgeos, you sure you removed it remotely?
[13:13] <tsdgeos> cimi: you can run the script against the remote branch
[13:14] <tsdgeos> if it had to delete something it'd tell you
[13:14] <cimi> ok
[13:14] <cimi> tsdgeos, is clean
[13:15] <cimi> tsdgeos, how do tags work? if I run locally on a freshly branched branch is deletes that tag, remotely is clean
[13:15] <tsdgeos> cimi: beats me :/
[13:15] <tsdgeos> ted: you're a bzr expert :D
[13:15] <greyback> a1fa: you referring to unity7 or 8? Have you logged a bug?
[13:15] <ted> Heh
[13:16] <ted> tsdgeos, You can run something against a remote branch by just specifying it. bzr tags lp:unity
[13:16] <a1fa> greyback: this is an old bug
[13:16] <a1fa> i figured someone reported it already
[13:16] <ted> The issue with tags is that bazaar always adds tags, so they collect.
[13:16] <a1fa> usually happens with chrome and terminal open, when launcher is set to auto-hide, sometimes it does not want to appear
[13:16] <greyback> cimi: you must run it against remote branch too. you can do strip-u8-tags.py :push
[13:17] <a1fa> the only way to get it to re-appear is to refocus windows
[13:17] <a1fa> or SpecKey
[13:17] <ted> Someone, S-a-v-i-q, gets really anal about cleaning them. :-)
[13:17] <cimi> tsdgeos, ^
[13:17] <cimi> read gerry
[13:17] <greyback> a1fa: well, we still actively fix unity7 bugs, so please ensure there's a bug with clear steps to repro, and we can find the rights guys to give it a look
[13:18] <a1fa> another issue i've found is terminal looses the menu bar
[13:18] <a1fa> default settings Terminal. nothing special
[13:18] <a1fa> multiple terminals open, and they will randomly start loosing menu bar
[13:19] <a1fa> refocusing terminals, re-draws the menu bar
[13:19] <greyback> a1fa: you doing anything special like multimonitor? You use workspaces?
[13:19] <a1fa> two gpus, 1 monitor, 2x gtx970
[13:19] <a1fa> no workspaces
[13:19] <a1fa> the launcher issue was present since dawn of time
[13:20] <a1fa> i just started noticing the terminal... so could be related to two gpus
[13:20] <greyback> a1fa: if nobody complains, we won't spend time to fix it.
[13:20] <a1fa> my gpus were also running at 60c, so got that fixed.. now waiting to see if the bug returns
[13:20] <greyback> and we prioritize that based on bug reports and how many people claim they're affected
[13:20] <a1fa> greyback: it's hard for me to reproduce the bug
[13:21] <a1fa> it's like mouse overshoots or undershoots on the edge, and launcher wont expose
[13:21] <a1fa> its not something thats easily reproducable as well
[13:21] <greyback> a1fa: well, even just exaplaining the symptoms and your physical setup might help
[13:21] <a1fa> ok i got it to reproduce
[13:21] <greyback> but if we can't repro, we can fix
[13:21] <a1fa> but its inconsistent
[13:21] <greyback> can't fix
[13:22] <greyback> though sometimes we get hunches :)
[13:22] <greyback> but I can't stress enough, without a good bug, it'll probably never be fixed
[13:23] <a1fa> greyback: wonder how many people use the hide launcher feature
[13:23] <greyback> a1fa: I do, and sadly I've never hit the issues you mentioned (have used unity for 4 year now)
[13:24] <greyback> a1fa: the dual GPU thing might be a critical difference between us tho
[13:24] <a1fa> i just started using the dual gpu
[13:24] <a1fa> do you use chrome?
[13:24] <greyback> yep
[13:24] <a1fa> hm
[13:28] <a1fa> greyback: you know when you get close to the edge, the edge goes blury and shadow appears?
[13:28] <a1fa> sometimes it feels like the mouse pointer gets past the shadow
[13:31] <greyback> a1fa: feels like or visibly achieves that? If you can grab a recording, it would help the bug report you're going to write :)  [https://bugs.launchpad.net/unity/+filebug]
[14:53] <mhall119> tsdgeos: will running unity8 from local build with ./run.sh run it in desktop mode or phone mode?
[14:54] <tsdgeos> mhall119: phone i think, but not sure, haven't really used ./run.sh in a while
[14:55] <mhall119> how do you test-run it?
[14:56] <tsdgeos> i usually just run the dash directly
[14:56] <tsdgeos> ./builddir/src/unity8-dash -mousetouch
[14:56] <mhall119> ah, so you're not running the full shell
[14:57] <tsdgeos> no
[14:57] <tsdgeos> not for my development neeeds
[14:57] <tsdgeos> i'm mostly a dash-man
[14:57] <tsdgeos> so don't need the unity8 part
[14:57] <tsdgeos> you'll need "start smart-scopes-proxy" to get the scopes up and running
[15:24] <ltinkl> mhall119, you can install the unity8 session and run it under a different user
[15:24] <ltinkl> mhall119, that's what I do
[15:24] <mhall119> ltinkl: from a local build?
[15:25] <ltinkl> mhall119, ye, from a local build (when I need to test something I've just written) or from the stable phone overlay PPA
[15:25] <ltinkl> mhall119, unity8-desktop-session-mir
[15:27] <ltinkl> mhall119, also make sure to install mir-graphics-drivers-desktop
[15:28] <ltinkl> mhall119, that was kinda missing from the deps last time I checked
[15:37] <tsdgeos> cimi: this needs reviewing asap please https://code.launchpad.net/~aacid/unity8/dash_activation_no_special_casing/+merge/264024
[15:37] <cimi> tsdgeos, ok
[15:38] <tsdgeos> needs to land coordinated with someothing from pstolowski
[15:38] <cimi> tsdgeos, will review now
[15:38] <cimi> tsdgeos, you have it tomorrow morning then
[15:38] <tsdgeos> cool
[19:04] <mhall119> kgunn: when I run ./run.sh after buildling Unity8, it is prompting for my fingerprint (I assume it's using PAM to get authentication for something) several times, and if I kill the session it always wants to start back up, is this normal or has something gone wrong for me?
[19:06] <kgunn> mhall119: uh...i'm not that familiar with running unity8 that way
[19:06] <kgunn> @unity ^ anyone else know ?
[19:14] <dandrader> mhall119, where are you running it?
[19:14] <dandrader> mhall119, phone or desktop?
[19:14]  * dandrader never uses ./run.sh
[19:14] <mhall119> on my laptop
[19:15] <dandrader> mhall119, just install the unity8-mir session package and then select it from the lightdm greeter
[19:17] <dandrader> mhall119, unity8-desktop-session-mir is the package
[19:29] <mhall119> dandrader: I'm trying to run trunk
[19:30] <mhall119> not at a session, the mock window data is fine, I just want to be able to run the shell and test new features in it
[19:30] <mhall119> so that I can get to where I can contribute code
[19:31] <mhall119> and, more importantly, help other people get to the point where they can contribute code
[19:33] <dandrader> mhall119, I run trunk and devel branches using unity8-desktop-session-mir
[19:34] <dandrader> mhall119, otherwise you can do "make tryOrientedShell"
[19:34] <dandrader> mhall119, which will get you unity8 with a mock environment (mock apps etc)
[19:36] <dandrader> mhall119, and there are "make tryFoo" targets for most components, like "make tryLauncher", "make tryPhoneStage" etc
[19:43] <mhall119> ok, so that should all get documented on https://unity.ubuntu.com/getinvolved/development/unity8/, because right now it says to use run.sh
[19:48] <dandrader> mhall119, CODING mentions those targets. including make testFoo (the automated version of tryFoo).
[19:49] <dandrader> mhall119, the vast majority of tests in unity8 are wrote that way. there's only a tiny percentage in autopilot
[19:50] <dandrader> and UI bugs can usually be reproduced and fixed just by playing with the relevant "make tryFoo" target
[19:52] <dandrader> mhall119, this is also outdated in the wiki: "Add ppa:canonical-qt5-edgers/qt5-proper and ppa:phablet-team"
[19:52] <dandrader> we don't do that anymore
[19:57] <mhall119> dandrader: in which wiki?
[19:58] <dandrader> mhall119, the one you mentioned
[19:58] <mhall119> ah, not a wiki, thats unity.ubuntu.com
[19:59] <dandrader> right
[20:01] <mhall119> dandrader: removed the lines with those 2 PPAs
[20:52] <a1fa> i got it
[20:52] <a1fa> http://i.imgur.com/O7K8KAo.png
[20:53] <a1fa> there is the terminal bug
[20:53] <a1fa> i removed stuff out of the terminal
[20:53] <a1fa> with gimp
[20:53] <a1fa> but you can tell the menu bar is missing