[00:11] <altaryBeastiful_> hey got some crash on unity-panel-service at startupt
[00:11] <altaryBeastiful_> would that be the cause of a black screen on startupt?
[00:12] <altaryBeastiful_> oops wrong chan
[00:13] <altaryBeastiful_> keep hacking wisdom felllows
[07:50] <tsdgeos> what's wrong with launchpad?
[07:51] <tsdgeos> now i can't reopen a unity8 bug?
[08:00] <Saviq> tsdgeos, not an ubuntu one
[08:00] <Saviq> tsdgeos, a unity8 one you can
[08:01] <Saviq> we're not ubuntu bug masters ;)
[08:01] <tsdgeos> Saviq: you mean unity8 (ubuntu) i can't?
[08:01] <Saviq> tsdgeos, yup
[08:01] <tsdgeos> i used to can
[08:01] <tsdgeos> i think
[08:01] <Saviq> tsdgeos, not reopen
[08:01] <tsdgeos> ok
[08:01] <Saviq> tsdgeos, you could change its status within a limited set
[08:01] <tsdgeos> Saviq: https://code.launchpad.net/~unity-team/unity8/suru-switch/+merge/207991 <- merge ?
[08:02] <Saviq> tsdgeos, no, https://blueprints.launchpad.net/unity8/+spec/suru-icon-switch
[08:02] <Saviq> ah ok
[08:02] <Saviq> :D
[08:02] <tsdgeos> Saviq: i mean merge the branch with master
[08:02] <Saviq> yeah ;)
[08:02] <tsdgeos> trunk
[08:02] <tsdgeos> head
[08:02] <tsdgeos> or whatever is called the mainline
[08:03] <tsdgeos> Saviq: and then set it to in progress if we're not supposed to merge it?
[08:03] <Saviq> done
[08:13] <paulliu> Saviq: I cannot test my code on phone because porst.ubuntu.com is extreme slow for asia area.
[08:13] <paulliu> Saviq: Should I add an DBusActionGroup in Shell.qml to receive the signal to shutdown the shell?
[08:14] <Saviq> paulliu, no, DBusActionGroup are specific to qmenumodel, ApplicationManager should just have a plain Qt signal to which shell would listen
[08:14] <paulliu> Saviq: ok. got it.
[08:16] <tsdgeos> can't run the autopilot thing now :/
[08:17] <Cimi> Saviq, I temporarly removed the LC_ALL=C from the first set of qmltests cause I don't know the syntax
[08:18]  * tsdgeos kicks upstart
[08:19] <tsdgeos> status is pre-start
[08:19] <tsdgeos> stop tells me it's already stopped
[08:19] <tsdgeos> how do i fix that?
[08:23] <Cimi> tsdgeos, what's the issue?
[08:24] <tsdgeos> Cimi: well since it's in pre-start upstart doesn't want to start a new one
[08:24] <tsdgeos> so i'm basically unable to run unity8
[08:25] <Cimi> tsdgeos, what's in pre start?
[08:25] <tsdgeos> unity9
[08:25] <tsdgeos> 8
[08:26] <Cimi> tsdgeos, well.. debug
[08:26] <tsdgeos> no
[08:26] <tsdgeos> i'm not going to debug upstart
[08:26] <Cimi> tsdgeos, there's log in ~.cache/upstart/unity8/log
[08:26] <Cimi> tsdgeos, debug our script
[08:26] <tsdgeos> there's nothing to debug in our scripty
[08:27] <Cimi> so you want the issue fixed but you don't want to debug it? :)
[08:27] <Saviq> tsdgeos, so upstart got "stuck" in pre-start?
[08:28] <tsdgeos> Saviq: correct
[08:28] <Saviq> tsdgeos, unity8 not running is it?
[08:28] <tsdgeos> Saviq: correct
[08:28] <Saviq> tsdgeos, and that's locally or on phone?
[08:29] <tsdgeos> Cimi: i'm not going to spend my time debugging upstart, there's much more valuable ways of me using the time canonical pays for
[08:29] <tsdgeos> Saviq: laptop
[08:29] <Cimi> tsdgeos, well reading the log might show if we have any bug in the script
[08:30] <tsdgeos> Cimi: since i'm not using any script i don't know how that can be of relevance here
[08:30] <Saviq> tsdgeos, only thing I can think of that might cause that is one of the `initctl emit` blocks
[08:30] <Saviq> tsdgeos, try `initctl emit indicator-services-end`
[08:30] <Saviq> tsdgeos, indicators will die, but hopefully release the pre-start script
[08:31] <Saviq> or `initctl emit indicator-services-start` to maybe kick them again
[08:31] <Cimi> tsdgeos, upstart script that is
[08:33] <tsdgeos> Saviq: nah :/
[08:33]  * tsdgeos reboots to see if that helps
[08:33] <Saviq> restarting the session would be enough....
[08:46] <tsdgeos> so yeah
[08:46] <tsdgeos> didn't help ^_^
[08:46] <tsdgeos> start unity8 is handing there forever
[08:46] <tsdgeos> which i guess if i kill it
[08:46] <tsdgeos> will end up causing the prestart problem
[08:48] <tsdgeos> correct
[08:52] <mhr3> Saviq, are card-optimizations in the latest image?
[08:55] <tsdgeos> mhr3: yes
[08:55] <tsdgeos> mhr3: why?
[08:56] <mhr3> tsdgeos, wondering if i should see any difference
[08:56] <tsdgeos> mhr3: you should
[08:56] <tsdgeos> it's not awesome
[08:56] <tsdgeos> it's less bad
[08:56] <Saviq> mhr3, it's just a first step, ↑
[08:57] <Saviq> tsdgeos, you need to add some debug echos to pre-start in data/unity8.conf
[08:57] <Saviq> tsdgeos, those will end up in ~/.cache/upstart/unity8.conf
[08:57] <Saviq> .log that is
[08:58] <Saviq> tsdgeos, but my bet is that one of the indicators fails to start
[08:58] <tsdgeos> yeah trying to do that
[08:58] <Saviq> tsdgeos, you could check by going `initctl emit indicator-services-start` and see if that returns
[08:58] <Saviq> OTOH we were doing the same, only via library before...
[08:59] <Saviq> but yeah, debug echos in the .conf are the way to go
[08:59] <tsdgeos> yeah that return just fine
[08:59] <Saviq> tsdgeos, make sure to copy the file to ~/.config/upstart
[08:59] <Saviq> tsdgeos, otherwise the system-wide one will be used
[08:59] <tsdgeos> Saviq: sure i was editing the system one ^_^
[08:59] <Saviq> ;)
[08:59] <Saviq> that's an option, too ;D
[09:00] <Saviq> tsdgeos, then make sure you *don't* have a ~/.cache/upstart one, 'cause that will take precedence
[09:00] <tsdgeos> yeah, nothing there
[09:00] <Saviq> tsdgeos, also, it should be enough to log out/in, no need to reboot
[09:01] <tsdgeos> let me do that
[09:01] <tsdgeos> back when i've found something
[09:01] <mhr3> Saviq, i know, it does seem tiny bit better, was hoping for more :)
[09:02] <Saviq> mhr3, we just need to stop displaying thousands of results
[09:02] <Saviq> mhr3, or we need to cache them all
[09:03] <mhr3> Saviq, s/thousand/fifteen/
[09:04] <mhr3> FTFY :)
[09:04] <Saviq> mhr3, depends what you're talking about
[09:12] <Cimi> Saviq, can I review https://code.launchpad.net/~saviq/unity8/split-common/+merge/214907 ?
[09:12] <Saviq> Cimi, sure
[09:21] <tsdgeos> Saviq: so yeah it's actually something wrong with indicator-services-start
[09:21] <tsdgeos> if i restart
[09:21] <tsdgeos> run it
[09:21] <tsdgeos> it will hang forever
[09:22] <tsdgeos> then if i ctrl+c it
[09:22] <tsdgeos> will just "timeout"?
[09:22] <tsdgeos> so i can now start unity8
[09:22] <tsdgeos> btu that's a bit sad :D
[09:22] <Saviq> tsdgeos, right, so one of the indicators has issues for you
[09:22] <tsdgeos> yep
[09:22] <tsdgeos> probably the network2
[09:22] <tsdgeos> which is the only one that unity7 doesn't load?
[09:22] <Saviq> tsdgeos, `grep -r indicator-services-start /usr/share/upstart/sessions`
[09:22] <Saviq> tsdgeos, and try starting them one by one
[09:23] <Saviq> tsdgeos, you'll see which one is the problem
[09:24] <tsdgeos> indicator-network
[09:24] <tsdgeos> tsdgeos_work@xps:~$ start indicator-network
[09:24] <tsdgeos> indicator-network stop/pre-start, process 3507
[09:24] <tsdgeos> all the rest is already running
[09:24] <tsdgeos> let me relogin again to make sure that if i try to start it, it will hang
[09:24] <Saviq> looks like that's it
[09:28] <Saviq> tsdgeos, so a bug in indicator-network
[09:29] <Saviq> tsdgeos, try starting it manually and see where it's hanging?
[09:29] <tsdgeos> Saviq: i guess
[09:29] <tsdgeos> i think it's crashing
[09:30] <tsdgeos> http://paste.ubuntu.com/7266765/
[09:32] <tsdgeos> works if i manually start it :S
[09:32] <tsdgeos> i think the upstart script is not cool
[09:32] <tsdgeos> http://paste.ubuntu.com/7266777/
[09:33] <MacSlow> Saviq, if I have to fix 1306769 (stand-alone pin-unlock) 1308011 becomes invalid
[09:33] <tsdgeos> do you guys can actually start it?
[09:34] <tsdgeos> or am i the only one up to date enough?
[09:34] <tsdgeos> or i'm the unlucky one
[09:35] <tsdgeos> back again
[09:45] <tsdgeos> Saviq: so i open a bug on indicator-network and tell them they're breaking unity8 for us?
[09:45] <Saviq> tsdgeos, works for me...
[09:45] <Saviq> tsdgeos, the upstart script looks fine
[09:46] <Saviq> tsdgeos,
[09:46] <Saviq> > start indicator-network
[09:46] <Saviq> indicator-network stop/pre-start, process 5398
[09:46] <Saviq> > status indicator-network
[09:46] <Saviq> indicator-network stop/waiting
[09:46] <Saviq> which just means it decides not to start in the pre-start script
[09:46] <Saviq> and that's as expected
[09:47] <tsdgeos> ok :/
[09:47] <tsdgeos> then i don't know
[09:47] <Saviq> tsdgeos, does "initctl emit indicator-services-start" hang for you?
[09:47] <tsdgeos> it does
[09:47] <tsdgeos> once
[09:47] <tsdgeos> after i ctrl+c it
[09:47] <tsdgeos> it will just timeotu
[09:48] <Saviq> tsdgeos, so yeah, that's your problem...
[09:48] <Saviq> I go `initctl emit indicator-services-end`
[09:48] <Saviq> all of them go away
[09:48] <Saviq> `initctl emit indicator-services-start`
[09:49] <Saviq> all of them come back, returns straight away
[09:49] <tsdgeos> Saviq: are you totally dist-upgraded?
[09:49] <Saviq> tsdgeos, yes
[09:49] <Saviq> we could still go & at the end of the emit...
[09:50] <Saviq> indicator-sync
[09:50] <Saviq> indicator-printers
[09:50] <Saviq> indicator-sound
[09:50] <Saviq> indicator-network
[09:50] <Saviq> indicator-application
[09:50] <Saviq> indicator-messages
[09:50] <Saviq> indicator-session
[09:50] <Saviq> indicator-bluetooth
[09:50] <Saviq> indicator-power
[09:50] <Saviq> indicator-datetime
[09:50] <Saviq> tsdgeos, start those one by one
[09:50] <Saviq> and see which one of those hangs
[09:51] <tsdgeos> none :/
[09:51] <Saviq> tsdgeos, have you stopped them before?
[09:51] <Saviq> tsdgeos, emit the -end first
[09:52] <tsdgeos> yeah
[09:52] <tsdgeos> let me do it again
[09:52] <tsdgeos> just in case
[09:52] <Saviq> > initctl list | grep indicator
[09:52] <Saviq> ?
[09:53] <tsdgeos> http://paste.ubuntu.com/7266867/
[09:53] <tsdgeos> http://paste.ubuntu.com/7266870/
[09:57] <Saviq> tsdgeos, ok /me no get it
[09:57]  * tsdgeos neither
[09:57] <Saviq> tsdgeos, hotfix: add & at the end of `initctl emit...`
[09:57] <tsdgeos> but let's ignore it for now
[09:57] <tsdgeos> and see if it keeps reproducing
[09:57] <tsdgeos> tx for the help :)
[09:58] <Saviq> tsdgeos, sure
[10:24] <Cimi> Saviq, tsdgeos did we change something? https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-trusty/1706/testReport/junit/(root)/qmltestrunner/tst_listviewwithpageheaderqml__compile/
[10:27] <tsdgeos> Cimi: yes that needs https://code.launchpad.net/~aacid/unity8/card_optimizations/+merge/213660 to be merged again
[10:27] <tsdgeos> sorry
[10:27] <tsdgeos> http://bazaar.launchpad.net/~aacid/unity8/card_optimizations/revision/828
[10:27] <tsdgeos> Saviq: you landing it again?
[10:29] <Saviq> tsdgeos, not sure today (release day) is a good day for that
[10:29] <Saviq> will probably have to wait until tomorrow
[10:29] <tsdgeos> ok
[10:29] <Saviq> I'm not entirely sure how that works until U is open
[10:30] <Saviq> /food
[10:49] <Cimi> Saviq, when this gets merged we need unity branch too https://code.launchpad.net/~cimi/unity-mir/unity-mir.stop-server_wizard/+merge/214983
[10:50] <Cimi> which doesnt work https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-mako/287/?
[10:51] <Cimi> I tried on my device the autopilot test, but weird...
[11:15] <Saviq> Cimi, it doesn't work 'cause -ci does not take the unity-mir branch
[11:16] <Saviq> Cimi, they need to land together, but it's fine - they're marked accordingly in the description
[11:17] <Cimi> Saviq, but I was not able to test them properly here
[11:17] <Cimi> Saviq, I installed unity branch
[11:17] <Cimi> Saviq, and mir
[11:18] <Saviq> Cimi, but it'd be useful to bump versions of both, and in unity-mir add Breaks: unity8 << $old_version, and in unity8 Depends: libunity-mir1 >= $new_version
[11:18] <Saviq> Cimi, so as to force an upgrade
[11:18] <Cimi> I see
[11:18] <Saviq> Cimi, just take the packages from -ci, install them both and it should be fine
[11:19] <Cimi> I tried with sbuild last evening
[11:19]  * Cimi tries again
[11:19] <Saviq> dednick, a small one if you have a moment https://code.launchpad.net/~saviq/unity8-desktop-session/start-indicators-lp1308891/+merge/216261
[11:21] <dednick> Saviq: sure.
[11:21]  * Saviq can't run the desktop session here still :|
[11:22] <dednick> Saviq: i don't have to test that one do i? :)
[11:22] <Saviq> dednick, nah
[11:23] <Saviq> dednick, I will in the silo anyway
[11:25] <Saviq> brb
[11:26] <mhr3> Saviq, i can actually test that
[11:26] <mhr3> was trying it out last week, got it all working then :)
[11:30] <Cimi> Saviq, tested again, works on my mako
[11:32] <mhr3> Saviq, doesn't work, you forgot emits foo
[11:33] <mhr3> Saviq, or something on my computer is broken :)
[11:34] <Cimi> oh damn, dithering on the new wallpaper looks really bad
[11:35] <Cimi> on mako
[11:35] <tsdgeos> Saviq: you do https://code.launchpad.net/~aacid/unity8/filtergrid_bindingloop/+merge/216147 or shall i try to find someone else?
[11:35] <Cimi> tsdgeos, I started
[11:35] <tsdgeos> Cimi: ah, awesome :)
[11:36] <tsdgeos> Saviq: Cimi's doing it
[11:51] <Saviq> mhr3, right, damn
[11:52] <Saviq> mhr3, pushed
[11:52] <mhr3> Saviq, actually, not enough, for some reason adding that event makes unity crash
[11:52] <mhr3> without it, it starts up
[11:52] <mhr3> but with it, it doesn't
[11:54] <mhr3> Saviq, upstart logs shows just http://paste.ubuntu.com/7267488/
[11:56] <Saviq> mhr3, try adding & after the initctl emit please
[11:57] <Saviq> mhr3, tsdgeos reported that emit blocking forever, maybe that? or are you getting an actual crash?
[11:57] <mhr3> Saviq, it would be unity8 itself crashing, right?
[11:57] <Saviq> mhr3, if it would, yes
[11:58] <mhr3> i do have a unity8 crash here from few minutes ago
[11:58] <mhr3> looking
[12:02] <mhr3> Saviq, http://paste.ubuntu.com/7267524/
[12:02] <Saviq> mhr3, that's on stop
[12:04] <mhr3> Saviq, alrighty, & fixes
[12:04] <mhr3> that does make me wonder what sorcery is that
[12:04] <mhr3> initctl emit with noone listening == infinite wait?
[12:05] <mhr3> oh upstart, upstart
[12:06] <Saviq> mhr3, not with noone listening, *something* that's listening takes forever
[12:06] <mhr3> or that :)
[12:07] <mhr3> fwiw the initctl process is just sleeping in poll()
[12:07] <mhr3> poll from deep inside libdbus
[12:09] <mhr3> http://paste.ubuntu.com/7267565/
[12:10] <mhr3> but maybe it's not upstart itself
[13:01] <Saviq> mhr3, can you verify silo 001 for me with the indicator fix?
[13:01] <mhr3> Saviq, k
[13:02] <Saviq> worked fine here
[13:04] <mhr3> Saviq, yep here too, +1
[13:05] <Saviq> mhr3, thanks
[13:32] <Cimi> tsdgeos, you set filtered as readonly, but in dashrenderers you forgot readonly 140	+    property bool filtered: true
[13:33] <tsdgeos> yes
[13:33] <tsdgeos> Dashrenderer is not a FilterGrid
[13:34] <tsdgeos> DashRenderer is just "base common API" for the Dash Renderers
[13:34] <tsdgeos> the thing is matched in qml/Dash/CardFilterGrid.qml
[13:34] <tsdgeos> with
[13:34] <tsdgeos> filtered: filterGrid.filtered
[13:35] <Cimi> yes
[13:35] <Cimi> tsdgeos, but we have readonly
[13:36] <Cimi> in filtergrid
[13:36] <Cimi> don't we want to preserve same api?
[13:36] <tsdgeos> we can't
[13:38] <tsdgeos> since we have the DashRenderer "base item" and CardFilterGrid.qml that "implements it"
[13:38] <tsdgeos> we can't set it readonly in DashRenderer
[13:38] <tsdgeos> and then set it in CardFilterGrid to be filtered: filterGrid.filtered
[13:38] <tsdgeos> i think
[13:38] <tsdgeos> maybe i'm wrong
[13:38] <tsdgeos> let me try :D
[13:38] <tsdgeos> yeah, can't
[13:38] <tsdgeos> CardFilterGrid.qml:31:5: Invalid property assignment: "filtered" is a read-only property
[13:38] <tsdgeos> Cimi: it'd be cool if we could do what you say though
[13:38] <tsdgeos> i agree
[13:38] <Cimi> ok
[13:39] <tsdgeos> Cimi: at least the documentation of filtered makes it clear it's supposed to be used for read only, no?
[13:40] <tsdgeos> or maybe not that much :D
[13:55] <tsdgeos> man, we're not the only ones with CI problems, can't land my Qt fix because their jenkins is foobar'ed too
[14:00] <dandrader> mzanetti, so you're back to work on unity8 trunk now right?
[14:03] <mzanetti> dandrader: well.. I'm trying to implement the animation for the tablet right edge. can do that on either branch I guess. the animation is the same regardless if its images or items.
[14:04] <mzanetti> I'll leave the screenshot updating away for now anyways...
[14:05] <mzanetti> dandrader: the reason why on trunk is that the FakeApplicationManager works there
[14:05] <mzanetti> so I can develop on my laptop instead of using the slow devices
[14:06] <mterry> OMG, I just flashed my actual phone instead of my work phone
[14:06] <mterry> :(
[14:06] <mzanetti> mterry: :D yep. happened to me already too
[14:07] <mzanetti> mterry: were you using android on that or dogfooding ubuntu?
[14:07] <mterry> mzanetti, I even have a case for my work phone so I know not to do this
[14:07] <mterry> mzanetti, dogfooding
[14:07] <mzanetti> mterry: ah ok. then its not that bad I guess, unless you bootstrapped
[14:07] <mterry> mzanetti, I did!
[14:07] <mzanetti> lol
[14:07] <mzanetti> ok, that's a bigger fail then
[14:08] <mterry> :)  Eh, it's OK.  Now that contacts syncing happened, I didn't have much data there I cared about
[14:08] <mterry> Just have to redownload all my apps
[14:08] <mzanetti> true... but contact sync was working for me since day one. (setting it up manually tho)
[14:09] <Cimi> tsdgeos, whas ./run that was not working for u on the desktop?
[14:09] <dandrader> greyback, mind reviewing this one? https://code.launchpad.net/~dandrader/platform-api/window_get_size/+merge/216156
[14:10] <greyback> dandrader: sure. That's an API change, so need to bump the version number
[14:10] <dandrader> greyback, you mean in the debian/changelog?
[14:11] <greyback> dandrader: yep
[14:11] <dandrader> greyback, or set(UBUNTU_PLATFORM_API_VERSION_MINOR 0) ?
[14:11] <tsdgeos> Cimi: correct
[14:12] <tsdgeos> Cimi: it does work if i do some workaround though
[14:12] <greyback> dandrader: both
[14:12] <greyback> ;l
[14:18] <dandrader> greyback, done
[14:19] <greyback> ta
[14:39] <Saviq> paulliu, please push your logout things to bzr and let us know where to look when you EOD today
[14:41] <paulliu> Saviq: yes.
[14:41] <paulliu> I'm testing right now. Will push it soon
[14:41] <Saviq> awesome
[14:44] <Cimi> tsdgeos, cimi@draco:~$ cat .cache/upstart/unity8.log
[14:44] <Cimi> initctl: Connection was disconnected before a reply was received
[14:44] <Cimi> /bin/sh: 1: exec: -mousetouch: not found
[14:44] <tsdgeos> Cimi: that's weird
[14:45] <tsdgeos> it's like the variable for the unity8 path wasn't found
[14:46] <tsdgeos> Cimi: which shell do you use?
[14:46] <Cimi> tsdgeos, unity7
[14:46] <Saviq> Cimi, or you're not in an upstart session there?
[14:46] <Saviq> Cimi, echo $UPSTART_SESSION
[14:46] <tsdgeos> Cimi: as in zsh, bash, foosh, etc
[14:46] <Cimi> bash
[14:46] <Saviq> Cimi, and check if there's no .crash for init in /var/crash
[14:46] <tsdgeos> hmmm, works here
[14:47] <Saviq> Cimi, ./build first?
[14:47] <Saviq> Cimi, is ./builddir/src/unity8 there?
[14:48] <tsdgeos> i guess readlink is failing?
[14:48] <tsdgeos> Cimi: http://paste.ubuntu.com/7268563/ what does it return?
[14:48] <Cimi> nevermind guys, works now
[14:49] <Cimi> I guess I did not run build
[14:49] <Cimi> or simply some debuild or sbuild deleted the dir
[14:50] <Cimi> keeps respawning though
[14:50] <Cimi> unless you ctrl c
[14:51] <tsdgeos> yep
[14:52] <tsdgeos> we agreed with Saviq that it was "good enough" for us
[14:52] <tsdgeos> that are the target group of run
[14:52] <tsdgeos> mostly
[14:52] <tsdgeos> s/us/developers maybe
[14:53] <paulliu> greyback: for applicationmanager can I just call onSessionStopping to stop the apps?
[14:53] <paulliu> greyback: Should I only close the focused app?
[14:54] <greyback> paulliu: that method is called by mir to report that a client (application) is disconnecting (probably shutting down).
[14:54] <greyback> so something else caused that app to shut down
[14:54] <paulliu> greyback: ok.
[14:54] <greyback> paulliu: stopApplication is what you want
[14:55] <paulliu> greyback: ok. got it
[14:55] <greyback> paulliu: this is for log out, yes? In that case, it would be best to close all apps, no?
[14:55] <paulliu> greyback: yeah.. I'll iterator the applist and close all of them
[14:56] <greyback> paulliu: I'm not sure what logout really will do. Does upstart tear down the whole user session?
[14:56] <greyback> but it's nicer to close apps, before mir/unity8 has shut down
[14:57] <greyback> kgunn: have just created lp:unity-mir/devel, who do I poke to get CI and autolanding going?
[14:59] <kgunn> fginther: could you possibly help us ? ^
[14:59] <kgunn> or a designate
[15:00] <fginther> kgunn, ack
[15:09] <paulliu> Saviq: is Qt.quit(); good for end the Shell?
[15:10] <Cimi> paulliu, qt quit sends a signal that we need to connect to
[15:10] <Cimi> in the main.cpp
[15:10] <paulliu> Cimi: ok.
[15:10] <Cimi> paulliu, what u need to do?
[15:10] <paulliu> Cimi: logout and quit the shell.
[15:11] <Cimi> paulliu, so you need to handle it
[15:11] <paulliu> Cimi: got it
[15:12] <Cimi> paulliu, QObject::connect(view->engine(), SIGNAL(quit()), application, SLOT(quit()));
[15:12] <Cimi> paulliu, you can change SLOT(quit()) to your likings
[15:13] <Saviq> paulliu, yeah, and take Cimi's unity-mir branch
[15:13] <Cimi> paulliu, put this like line 127 of main.cpp
[15:14] <Saviq> https://code.launchpad.net/~cimi/unity-mir/unity-mir.stop-server_wizard/+merge/214983
[15:29] <Cimi> Saviq, can we close the greeter when the screen turns off?
[15:29] <Cimi> Saviq, so annoying to turn the screen on and seeing the greeter closing
[15:29] <Saviq> Cimi, bug #1233564
[15:37]  * greyback has to go, happy easter all
[15:37] <tsdgeos> o/
[15:37] <Saviq> o/
[15:38] <dandrader>  \o
[15:38] <Saviq> \o/
[15:38] <dandrader> _o_
[15:38] <Saviq> /o/
[15:38] <Saviq> /away
[15:56] <paulliu> Saviq: https://code.launchpad.net/~paulliu/unity-mir/logout/+merge/216336
[15:56] <paulliu> Saviq: I'm testing the unity8 code now. Will push it later.
[16:43] <didrocks> olli: Saviq: in case you didn't notice, but the indicator startup fix for the unity8 session is available in the release pocket (just in time)
[16:43] <olli> didrocks, most awesome!
[16:48] <dandrader> mzanetti,  you don't animate SpreadDelegates when its correponding model entry is removed, right?
[16:48] <dandrader> mzanetti, they just vanish from the Repeater and that's it
[16:57] <dandrader> mzanetti,  ok, guess you went for your holidays already
[17:16] <paulliu> Saviq: https://code.launchpad.net/~paulliu/unity8/logout/+merge/216373
[17:20] <darklight_> so in 14.04, if one sets the scale and plugins hotcorners they get reset every session BUT if one puts them last in dconf in org->compiz->profiles->unity->plugins->core the settings are remembered, only issue is that then when using meta+w and meta+s unity segfaults
[17:39] <mzanetti> dandrader|lunch: hey, no, I don't do that yet, but I guess that should happen at some point
[18:08] <fginther> kgunn, lp:unity-mir/devel is now setup
[23:12] <josharenson> kgunn are you eod?
[23:24] <kgunn> josharenson: almost
[23:24] <kgunn> what's up?
[23:25] <josharenson> kgunn: I talked with fginther at length today about the CI test. Its getting frustrating rewriting it every time we come up with a new way to run the tests.... However I think we finally nailed down how its going to work.
[23:26] <kgunn> cool
[23:26] <josharenson> kgunn: so I've retracted all my MPs and I'm implementing the solution we discussed. Just wanted to give you an update on progress since its been kinda choppy
[23:27] <kgunn> josharenson: no worries, i know you're hard at it...and its a lot of mucky infra-stuff
[23:43] <darklight_> what's the appropiate way to set up hotcorners in 14.04  ?
[23:44] <darklight_> because the options don't stick and changing the order of expo and scale in dconf makes unity segfaults when using the shortcuts meta+w or meta+s