[03:26] <sgo11> hi, I heard unity 8 is faster. will that be faster than lxde? thanks.
[06:59] <didrocks> Saviq: hey, mind doing a special unity8 delivery containing the cleanup socket fix?
[09:16] <davidcalle> Saviq or tsdgeos, ping
[09:16] <tsdgeos> davidcalle: hi
[09:17] <davidcalle> tsdgeos, hey ! Do you have an ETA for header attributes and emblem?
[09:17] <tsdgeos> you're going to need Saviq for that sorry :D
[09:17] <tsdgeos> i mean for the ETA
[09:19] <davidcalle> tsdgeos, thanks :)
[09:25] <Saviq> didrocks, will do
[09:26] <didrocks> Saviq: thanks! please stick that in your landing :)
[09:36] <vini> hi, how can i update unity to the most recent release?
[09:37] <Saviq> vini, how do you usually update software in ubuntu?
[09:37] <vini> hi Saviq
[09:38] <vini> i mean beta and early versions, not final
[09:38] <Saviq> vini, you'll have to update to the ubuntu development release (trusty)
[09:38] <vini> ok
[09:39] <vini> need fresh install?
[09:39] <Saviq> vini, no, http://askubuntu.com/questions/12909/how-do-i-upgrade-to-the-development-release-aka-ubuntu1
[09:40] <Saviq> mzanetti, are you in a state to review / test https://code.launchpad.net/~saviq/unity8/drop-stale-socket/+merge/196917 ?
[09:40] <vini> thanks Saviq
[09:40] <Saviq> didrocks, icanhassilo for row 28?
[09:41] <Saviq> didrocks, actually, since you wrote I can get the other things...
[09:41] <Saviq> let me
[09:42] <Saviq> didrocks, or actually... you didn't comment on row 17? does the comment for 16 apply?
[09:49] <vini> Saviq, there is an option to update only unity? not the whole distro
[09:50] <Saviq> vini, you could try, but that's not guaranteed to work - unity has quite some dependencies that would have to be pulled in anyway
[09:51] <vini> ok thank you
[09:51] <Saviq> vini, https://wiki.debian.org/AptPreferences#Pinning has some info on how to do that
[09:52] <Saviq> vini, or https://help.ubuntu.com/community/PinningHowto for more ubuntu-style docs
[09:53] <vini> 2nd link is more preffered, thanks
[10:10] <didrocks> Saviq: so, yeah, if you want to stich more in, it's now or never! :)
[10:10] <Saviq> didrocks, !!!
[10:10]  * Saviq does
[10:10] <didrocks> Saviq: line 17 can land, after discussing with xnox, it's not activated until line 16 lands
[10:10] <Saviq> didrocks, ah, so let me stick all that into line 16
[10:11] <Saviq> erm
[10:11] <Saviq> 17
[10:11] <didrocks> Saviq: sure
[10:11] <didrocks> Saviq: please do take care of the landing as per my email
[10:11] <didrocks> when testing
[10:11] <Saviq> didrocks, will do
[10:11] <didrocks> we really need to be extra cautious
[10:11] <didrocks> thanks :)
[10:15] <Saviq> didrocks, ok, row 17 ready
[10:15] <didrocks> sil2100: I'm assigning it ^
[10:15] <didrocks> Saviq: "exterminating" the other line?
[10:16] <Saviq> didrocks, already did
[10:16] <Saviq> or not
[10:16] <Saviq> now dii
[10:16] <Saviq> did
[10:16] <didrocks> Saviq: mind being a little bit more descriptive than "Unity8 update"?
[10:16] <Saviq> didrocks, right
[10:17] <Saviq> didrocks, done
[10:18] <didrocks> Saviq: silo 008 is yours
[10:18] <Saviq> didrocks, \o/
[10:18] <didrocks> :)
[10:18] <Saviq> didrocks, no it isn't :/
[10:18] <Saviq> #REF?
[10:19] <Saviq> oh now it updated
[10:19] <didrocks> hum?
[10:19] <Saviq> ignore
[10:19] <didrocks> ah, be patient :)
[10:19] <Saviq> I even refreshed!
[10:19] <didrocks> GAS are taking some times to recompute ;)
[10:25] <tsdgeos> guys
[10:25] <tsdgeos> anyone not using qt5.2
[10:25] <tsdgeos> can you run unity8 on the desktop
[10:25] <tsdgeos> and tell me if you get
[10:25] <tsdgeos> file:///home/tsdgeos_work/phablet/unity8/unity8/qml/Shell.qml:761:5: QML Binding: Binding loop detected for property "target"
[10:25] <tsdgeos> on startup?
[10:26] <Saviq> tsdgeos, upgrading
[10:26] <tsdgeos> Saviq: upgrading? i said "not" using 5.2
[10:26] <Saviq> tsdgeos, ah
[10:27] <tsdgeos> ok, ignore, that's not the binding that is breaking the phone
[10:28] <Saviq> tsdgeos, yes, it's there
[10:28] <tsdgeos> ok, tx
[10:28] <Saviq> huh, btw
[10:28] <Saviq> target: i18n
[10:29] <Saviq> binding loop!
[10:29] <Saviq> ?
[10:29] <tsdgeos> i guess i18n is not defined by whoever defines it until a later stage
[10:29] <tsdgeos> maybe should be in Component.onCompleted
[10:29] <tsdgeos> as a Qt.binding() thing
[10:29] <Saviq> tsdgeos, maybe
[10:30] <Saviq> dednick, you around?
[10:30] <dednick> Saviq: yarp
[10:31] <Saviq> dednick, you in a state you could test https://code.launchpad.net/~saviq/unity8/drop-stale-socket/+merge/196917 ?
[10:31] <Saviq> i.e. do you have a device running unity8? ;)
[10:31] <dednick> Saviq: think i can manage it
[10:31] <Saviq> dednick, would be enough to copy /usr/share/upstart/sessions/unity8.conf into ~/.config/upstart/
[10:32] <Saviq> dednick, applying the patch
[10:32] <Saviq> dednick, stop unity8; start unity8; pkill -9 unity8
[10:32] <Saviq> if it recovers, we're good
[10:49] <dednick> Saviq: mako test failures normal on jenkins?
[10:49] <Saviq> dednick, yeah, random?
[10:50] <Saviq> dednick, we've a Qt crasher that got worse with android 4.4.2 - we're running away from it to Qt 5.2... but then there's two other crashers tsdgeos is looking into
[10:50] <dednick> Saviq: ok.
[10:50] <Saviq> dednick, if it says that "process not found" or so - that's it
[10:51] <dednick> Saviq: mmm. doesnt say that. but unity8 did crash
[10:51] <didrocks> you can quickly get the crash
[10:51] <didrocks> and check that frame0 address finish with d8f8
[10:51] <didrocks> it's the signature :)
[10:52] <Saviq> dednick, which job on jenkins?
[10:52] <dednick> Saviq: https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/5574/console
[10:52] <Saviq> dednick, "NoSuchProcess: no process found with pid 6296"
[10:53] <dednick> ah. looking for wrong text.
[10:54] <dednick> Saviq: approved
[10:54] <Saviq> dednick, thanks!
[10:55] <Saviq> yup, d8f8
[11:10] <vini> hi, there is a plugin for file manger to "open terminal" in specific location?
[11:13] <Saviq> didrocks, hum, silo failed on armhf https://launchpadlibrarian.net/167968584/buildlog_ubuntu-trusty-armhf.unity8_7.84%2B14.04.20140228-0ubuntu1_FAILEDTOBUILD.txt.gz any idea?
[11:13] <Saviq> shall I just kick it again?
[11:13] <didrocks> Saviq: ah, I guess it's time to chdist
[11:14] <didrocks> let me check if I can get that easy
[11:28]  * didrocks wonders why it's trying to fetch i386 on his new created chdist armhf
[11:28] <didrocks> Saviq: meanwhile, retry to see if that was transient
[11:28] <didrocks> I keep looking
[11:29] <Saviq> didrocks, can you kick "retry" on https://launchpad.net/~ci-train-ppa-service/+archive/landing-008/+build/5645715
[11:29] <Saviq> didrocks, I don't have the rights
[11:29] <didrocks> oh right
[11:30] <didrocks> done
[11:30] <Saviq> thanks
[11:33] <tsdgeos> no daniel?
[11:37] <Saviq> tsdgeos, yeah, national holiday for him
[11:38] <Saviq> the whole week, according to cadmin ;D
[11:38] <tsdgeos> ah
[11:38] <tsdgeos> carnival
[11:38] <tsdgeos> makes sense
[11:43] <didrocks> Saviq: was an archive skew
[11:43] <Saviq> didrocks, whatever that means, but transient, yeah :)
[11:43] <didrocks> yeah
[11:56] <Saviq> xnox, hey, I tried to x-build unity8 with qt5.2 from canonical-qt5-edgers/qt5-beta2, got http://pastebin.ubuntu.com/7009939/ - any ideas?
[11:58] <xnox> Saviq: that spec file is gone in 5.2, no?
[11:58] <xnox> (or the other way around, this _is_ the new spec)
[12:01] <Saviq> xnox, hmm wait, I might've confused my chroots
[12:01] <didrocks> Saviq: then, you know you can just relaunch "build" with "watch only" to only watch the ppa and not rebuilding
[12:02] <Saviq> didrocks, ah, doing
[12:05] <Saviq> xnox, hmm seems legit http://pastebin.ubuntu.com/7009976/
[12:05]  * Saviq is worried they broke x-compilation again
[12:09] <Saviq> xnox, so... seems set(_qt5_corelib_extra_includes "${_qt5Core_install_prefix}/lib/arm-linux-gnueabihf/qt5//mkspecs/linux-g++") is a new addition to the cmake module
[12:10] <Saviq> xnox, looks like qt5-base-dev would have to start depending on qt5-qmake to get those... or we need to install the mkspecs in some other way
[12:10] <Saviq> Mirv, ↑
[12:12] <xnox> Saviq: Mirv: oh, that looks wonderful! if mkspecs are not in multiarch locations it's execellent! and knowing _qt5Core_install_prefix also helps a lot!
[12:13] <xnox> Saviq: so we need more deps. and qt5-qmake should be multiarch-same, i think it is/was. if not that's easy to fix.
[12:13] <Saviq> xnox, yup, that's what I thought
[12:14] <Mirv> I have no idea of the CMake speficics you're talking about, but mkspecs moved from /usr/share/mkspecs to /usr/lib/{multiarch}/qt5/mkspecs in 5.2 and some sources might need changes accordingly (known so far and with patches maliit-framework, pyqt5)
[12:14] <Saviq> xnox, fyi https://qt.gitorious.org/qt/qtbase/commit/6fa9394c
[12:14] <tsdgeos> larsu: https://code.launchpad.net/~aacid/qmenumodel/fix_uninit/+merge/208783
[12:15] <xnox> Mirv: i'm so happy for that move! =)
[12:15]  * xnox schedules some time to enable cross-compilation with qmake
[12:15] <Mirv> xnox: ah, you meant s/not/now/, so it's good news like I though :)
[12:15] <Mirv> +t
[12:16] <Saviq> uh oh
[12:16] <Saviq> xnox, that's worse http://pastebin.ubuntu.com/7010023/ :/
[12:16] <xnox> Saviq: Mirv: correct =))) bad typpo. It's all good news all around! =)
[12:16] <Mirv> Saviq: that binary is probably somewhere in tools
[12:17] <Mirv> qtbase5-dev-tools
[12:17] <larsu> tsdgeos: the patch looks good to me, but I didn't write that code...
[12:17]  * larsu approves anyway
[12:17] <xnox> Mirv: Saviq: when cross-compiling, that's the wrong path. But that's easy to fix.
[12:17] <tsdgeos> larsu: who do you want me to nag?
[12:18] <tsdgeos> larsu: ah thanks :)
[12:18] <xnox> Saviq: i'll fix things up for 5.2. Let me just finish up with android i686 cross-toolchain.
[12:18] <Saviq> xnox, ok thanks
[12:18] <larsu> tsdgeos: it's trivial enough I think
[12:18] <larsu> tsdgeos: would be dednick or renato I guess
[12:20] <tsdgeos> oki
[12:21] <dednick> tsdgeos: um, dont think thats right...
[12:21] <tsdgeos> dednick: why not?
[12:21] <dednick> tsdgeos: oh, it's in constructor. no, it's fine then
[12:22] <dednick> thought the signal wasn't getting emitted
[12:22] <tsdgeos> it won't anyway
[12:22] <tsdgeos> you can't emit signals from a constructor
[12:22] <tsdgeos> well you can
[12:22] <tsdgeos> but nobody will be listening
[12:22] <dednick> tsdgeos: yeah :) i didn't realise the code was in the constructor
[12:22] <tsdgeos> since noone has had time to connect to you yet
[12:23] <tsdgeos> oki :)
[12:28] <Saviq> Mirv, did you notice on qt5.2 that you have to press twice to wake the screen when it's timed out?
[12:29] <Saviq> Mirv, ignore
[12:29] <Saviq> Mirv, I've powerd-cli in a terminal ;)
[12:31] <Mirv> Saviq: hmm, no I have not. maybe I've just ignored it but I don't remember having to press twice.
[12:31] <Saviq> Mirv, ignore me, I had it locked with powerd-cli
[12:31] <Mirv> Saviq: the good thing was that the waking started to work with 5.2.1. maybe it was even some qtbase 5.2.0 bug or such, the original one there were.
[12:31] <Mirv> ok :)
[12:31] <Saviq> Mirv, :)
[12:34] <Saviq> didrocks, can you reconfigure silo 008 please? we've a fix for the unity8 5.2 crash in store
[12:34] <Saviq> tsdgeos FTW!
[12:34] <Saviq> tsdgeos, looking good, halfway through ap run and /var/crash clean!
[12:35] <tsdgeos> \o/
[12:35] <tsdgeos> one down!
[12:35] <tsdgeos> the other should not be that hard
[12:35] <tsdgeos> hopefully
[12:35] <tsdgeos> seems one of those "dude you removed the stuff under my feet"
[12:36] <tsdgeos> Saviq: do you have bluetooth in your desktop and qt 5.2? does the crash happen in there?
[12:36] <Saviq> tsdgeos, upgrading to 5.2
[12:36] <tsdgeos> maybe using dednick's branch of desktop indicators
[12:37] <tsdgeos> Saviq: waaaaaaaaaai
[12:37] <tsdgeos> Saviq: new scopes won't work
[12:37] <tsdgeos> in case you need that
[12:37] <Saviq> tsdgeos, nw
[12:37] <tsdgeos> though you can always rollback
[12:37] <Saviq> tsdgeos, should work without dednick's branch I think
[12:38] <Saviq> tsdgeos, and why wouldn't new-scopes work, btw?
[12:38] <Saviq> tsdgeos, they're rebuilt for 5.2 no?
[12:38] <tsdgeos> sure, it's just the fact i don't have bluetooth
[12:38] <tsdgeos> but if you can get it to crash
[12:38] <Saviq> tsdgeos, yup, gimme 10
[12:38] <tsdgeos> i'll find a bluetooth dongle
[12:38] <tsdgeos> Saviq: were are they rebuild for 5.2?
[12:38] <Saviq> tsdgeos, in the qt5.2 repo, no?
[12:38] <tsdgeos> it's regular unity8 i think
[12:38] <tsdgeos> no new-scopes
[12:39] <tsdgeos> wait
[12:39] <Saviq> tsdgeos, https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-beta2/+packages?field.name_filter=scopes&field.status_filter=published&field.series_filter=
[12:39] <tsdgeos> new scopes may be
[12:39] <tsdgeos> what is not there
[12:39] <tsdgeos> is the toolkit stuff
[12:39] <Saviq> tsdgeos, ah
[12:39] <tsdgeos>  Cannot assign to non-existent property "nativeOrientationAngle"
[12:39] <Saviq> tsdgeos, ah right, so it's not new-scopes, but mwc
[12:39] <Saviq> anyway
[12:39] <Saviq> it's fine
[12:40] <tsdgeos> running valgrind on the phone is a party of warnings :D
[12:40] <Saviq> ;0
[12:41] <Saviq> sil2100, can you reconfigure silo 008 for me please?
[12:41] <tsdgeos> i haven't even started
[12:41] <tsdgeos> and i have this
[12:41] <tsdgeos> http://paste.ubuntu.com/7010119/
[12:42] <Saviq> yay
[12:43] <tsdgeos> the dlopen ones may be "ok"
[12:43] <didrocks> Saviq: should we delay the landing for that? maybe 2 landings will be better?
[12:43] <tsdgeos> but there's some uninit memory that definitely may be worth fixing
[12:43] <didrocks> Saviq: as I want to kick an image with the unlock screen fix asap
[12:43] <Saviq> didrocks, ok
[12:43] <didrocks> thanks :)
[12:44] <Saviq> didrocks, will take me twice the time to land, but OHKAY :P
[12:45] <didrocks> Saviq: well, I'm sure you will have also good fixes on Monday :)
[12:45] <Saviq> didrocks, Monday!?
[12:46] <didrocks> and it's taking double time for us as well, do not forget :)
[12:46] <Saviq> didrocks, we want the two crashers in today! ;P
[12:46] <didrocks> ah, well, if you are quick enough, that's doable :)
[12:46] <Saviq> (fixes for them, even)
[12:46] <sil2100> Saviq: sure
[12:46] <Saviq> sil2100, nope
[12:46] <Saviq> sil2100, didrocks overridden my request
[12:46] <sil2100> Saviq: un-sure
[12:47] <Saviq> sil2100, thanks
[12:47] <sil2100> ;)
[12:51] <Saviq> tsdgeos, +1!
[12:51] <tsdgeos> \o/
[12:52] <Saviq> tsdgeos, you get sixpack of beer ;D
[12:53] <tsdgeos> but how do i fix the other bug if i'm drunk?
[12:53] <tsdgeos> luch time now, after taht i really need a way to create an indicator that mimics the bluetooth behaviour for the desktop
[12:54] <tsdgeos> dednick: if you have any pointers in that ↑↑↑ i'll be terribly happy
[13:02] <Saviq> tsdgeos, yeah, crashes on desktop
[13:02] <Saviq> bregma, do we have any other indicator than bluetooth that hides itself?
[13:03] <Saviq> didrocks, 212 doesn't boot, known? seems the container doesn't start
[13:05] <didrocks> Saviq: it does boot for popey though?
[13:05]  * didrocks flashes
[13:05] <Saviq> maybe it failed to flash correctly, /me tries again
[13:05] <Saviq> looks I'm missing system.img
[13:06] <didrocks> hard to boot without it :p
[13:06] <popey> !wfm
[13:06] <popey> ☻
[13:06] <didrocks> ahah :)
[13:06] <Saviq> ☺
[13:07] <Saviq> popey, obviously you spend more time in the sun...
[13:07] <Saviq> slacker!
[13:08] <popey> :D
[13:08] <davmor2> Saviq: You know popey is in England right?  There is no sun :P
[13:09] <popey> There might not be in the smelly north where you live.
[13:09] <Saviq> davmor2, right, just tar-like rain? ;)
[13:09] <popey> But down here in the tropical south it's lovely ☻
[13:09] <popey> http://popey.com/webcam/ ignore this
[13:09] <didrocks> Saviq: beautiful starting system.img here :)
[13:09] <Saviq> didrocks, k, let's see
[13:09] <Saviq> popey, ouch ;D
[13:10] <davmor2> popey: haha yeah there are no massive storms hitting the uk again at all :P
[13:10] <Saviq> sunny 13° here :)
[13:10] <Saviq> in FEBRUARY, no less
[13:12] <Saviq> larsu, maybe you know - any indicator other than bluetooth that would hide itself? or maybe a way to trick the bluetooth one to think there is a bt device when there isn't?
[13:14] <larsu> Saviq: sound has a gsettings key to show/hide itself, but that seems to be broken right now
[13:14] <Saviq> uh
[13:14] <larsu> Saviq: bluetooth has a visible key as well
[13:14] <larsu> but you're not seeing it because you don't have any devices...
[13:14] <larsu> Saviq: keyboard works
[13:14] <larsu> gsettings set com.canonical.indicator.keyboard visible false
[13:15]  * Saviq tries
[13:17] <Saviq> didrocks, yeah, booted now, not sure what happened there :/
[13:17] <didrocks> Saviq: do you have anything in /cache/recovery?
[13:17] <didrocks> there are the logs of different flashing, would be interesting to see if something failed
[13:18] <Saviq> didrocks, only one install log it seems, let me pastebin them all
[13:19] <Saviq> larsu, hmm, keyboard not showing up in unity8 under the desktop profile :/
[13:19] <seb128> Saviq, larsu: battery and datetime also has a show key
[13:19] <seb128> have
[13:19] <larsu> Saviq: what seb128 says :)
[13:20] <seb128> larsu, btw, I was pondering doing https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/829648 next week
[13:21] <larsu> seb128: apparently that gsettings key doesn't work right now. I can fix that though, should be quick
[13:21] <seb128> larsu, there was design disagreement over those UIs back then but we ended up adding the option for the other indicators, so for consistency we should probably do it for sound as well
[13:22] <larsu> I agree
[13:22] <seb128> thanks
[13:23] <Saviq> ok so... it must be that the state is changing while it's being queried or something
[13:23] <Saviq> as no disappearing indicator causes the crash - not unless the change comes from the indicator UI itself
[13:25] <Saviq> http://paste.ubuntu.com/7010320/
[13:25] <Saviq> http://paste.ubuntu.com/7010321/
[13:25] <Saviq> http://paste.ubuntu.com/7010324/
[13:25] <Saviq> http://paste.ubuntu.com/7010325/
[13:25] <Saviq> http://paste.ubuntu.com/7010325/
[13:25] <Saviq> http://paste.ubuntu.com/7010329/
[13:26] <Saviq> didrocks, ↑ all the logs from /cache/recovery, I'm not sure what I'm looking for but nothing stands out
[13:26] <didrocks> Saviq: 2 links are the same, wanted?
[13:27] <Saviq> didrocks, dupe, sorry
[13:27] <Saviq> didrocks, 5 logs is all I have
[13:27] <didrocks> ok ;)
[13:27]  * didrocks looks
[13:29] <dandrader> Saviq, do you know if zanetti's right-edge branch also works on tablet mode?
[13:30] <dandrader> (with side stage)
[13:30] <Saviq> dandrader, the branch should work, yes
[13:30] <Saviq> dandrader, not right edge, of course - it "switches" to old behaviour on tablet
[13:30] <Saviq> -""
[13:30] <Saviq> dandrader, I haven't tried though - it is meant to work
[13:32] <Saviq> /food, too
[13:44] <tsdgeos> Saviq: it does? awesome!
[13:44]  * tsdgeos starts looking for a bluetooth dongle
[13:45] <Saviq> tsdgeos, data point: it has something to do with you interacting with the indicator panel when it's going away
[13:45] <tsdgeos> Saviq: what do you mean?
[13:45] <Saviq> tsdgeos, or maybe the checkbox still wants to animate but is destroyed
[13:45] <tsdgeos> Saviq: i think it's the checkbox thing
[13:45] <Saviq> tsdgeos, I mean that if you hide the indicator from outside
[13:46] <tsdgeos> larsu: you do indicator stuff, right?
[13:46] <Saviq> tsdgeos, it will not crash
[13:46] <greyback> hey folks, any sbuild user ever get this fail on creating an armhf chroot: http://pastebin.ubuntu.com/7010432/
[13:47] <tsdgeos> i wonder what's easier, finding someone close to me with bluetooth adaptor or coding a similar indicator :D
[13:47] <tsdgeos> i guess i can just fork indicator-bluetooth and fake the backend part...
[13:47]  * tsdgeos tries
[13:48] <larsu> tsdgeos: what are you trying to do?
[13:48] <larsu> and why don't you have a laptop with bluetooth :P
[13:48] <tsdgeos> larsu: i'm trying to get an indicator with a checkbox that when i click on it the indicator disappears from the indicators, like the bluetooth one does
[13:48] <tsdgeos> larsu: that is indeed a good question :D
[13:49] <larsu> tsdgeos: datetime and power have such a check (see the discussion we jut had a bit earlier in this channel)
[13:50] <tsdgeos> larsu: where is that checkbox? i can't see it
[13:50] <larsu> tsdgeos: settings / time and date / clock / "Show a clock in the menu bar"
[13:51] <seb128> larsu, he wants a control in the indicator menu to disable the indicator I think
[13:51] <tsdgeos> yes
[13:51] <seb128> larsu, they seem to think their bug happen when you turn off the indicator from its own UI
[13:52] <tsdgeos> what bluetooth does
[13:52] <larsu> wtf?
[13:52] <seb128> larsu, you can turn bluetooth off from the bluetooth indicator
[13:52] <larsu> bluetooth does this?
[13:52] <seb128> yes
[13:52] <larsu> when I turn it off, I still see it
[13:52] <seb128> it has a on/off toggle
[13:52] <larsu> oh, this is phone
[13:52] <seb128> right
[13:52] <seb128> unity8 issue
[13:53] <tsdgeos> let's call it QML issue for now ;-)
[13:53] <seb128> it should be easy to patch e.g power to add a checkbox that toggle the gsettings show key
[13:53] <larsu> I can hardly believe that the reason for it crashing is that the toggle is in the indicator ui
[13:55] <tsdgeos> larsu: well, you can find it hard to belive, but it is what it is
[13:56] <tsdgeos> you can trust my informed opinion or not
[13:56] <tsdgeos> that's up to you
[13:56] <tsdgeos> i'm asking you not for help in fixing my bug but in creating an indicator that behaves like the indicator one
[13:56] <tsdgeos> if you can do that, cool, if not i'll do it myself
[13:58] <larsu> tsdgeos: fair enough. Quickest way is proabably to add a fake device in the bluetooth indicator
[13:59] <tsdgeos> yep, i'm trying that
[13:59] <larsu> tsdgeos: something like this should be enough: http://paste.debian.net/84568/
[14:00] <seb128> did you try asking pitti if he has some mock you could use to fake a bluetooth device?
[14:00] <larsu> tsdgeos: oh wait, which profile are you using?
[14:00] <seb128> the phone one I guess
[14:01] <tsdgeos> not sure tbh
[14:01] <Saviq> larsu, seb128, we have a patch to use the desktop profile optionally
[14:01] <Saviq> tsdgeos, yeah, phone is default
[14:01] <tsdgeos> problem is, it bails out earlier
[14:01] <seb128> the desktop profile doesn't hide the indicator when bluetooth is off iirc
[14:01] <tsdgeos> since it can't find anything in bluez
[14:01] <tsdgeos> need to find out where that's happening
[14:01] <seb128> easier option "go out, buy a bluetooth dongle"
[14:03] <larsu> seb128: on the phone it seems to be always visible when bluetooth is enabled
[14:03] <larsu> ah, I guess the toggle disables bluetooth instead of just hiding the indicator?
[14:04] <seb128> right
[14:04] <seb128> the indicator hides by a side effect of bluetooth turning off
[14:06] <Saviq> didrocks, so, only failure I got was the StateNotFound one, is that ok?
[14:07] <didrocks> Saviq: can you check on that one with elopio? He told StateNotFound is normally because of badly written tests
[14:07] <tsdgeos> seems to be working
[14:07] <didrocks> and can help fixing them :)
[14:07] <Saviq> didrocks, ah no
[14:07] <Saviq> didrocks, I had my bluetooth disabled
[14:08] <didrocks> oh ;)
[14:08] <didrocks> that can explain
[14:10] <Saviq> didrocks, yeah, it's fine
[14:10] <didrocks> great ;)
[14:10] <didrocks> sil2100: can you test unity8 as well? Maybe that can still make it for that image ^
[14:13] <tsdgeos> crash \o/
[14:14] <tsdgeos> larsu: thanks for the pointers :)
[14:14]  * tsdgeos starts debugging in a proper environment (i.e. !phone)
[14:22] <mhr3> Saviq, if you have a sec - https://code.launchpad.net/~mhr3/unity-scopes-shell/category-order/+merge/208806
[14:23] <sil2100> didrocks: once I finish frying I'll move on to unity8 ;)
[14:23] <didrocks> sil2100: taking a break? lucky you :p
[14:25] <Saviq> didrocks, kick the button on silo 008 please!
[14:26] <didrocks> Saviq: we are doing a second check to protect any bad things happening as long as we are in this flaky world, which is what sil2100 is going to do
[14:27] <Saviq> didrocks, sure
[14:33] <tsdgeos> @unity: standup
[14:39] <Saviq> Mirv, I could try and help from unity PoV for the landing, unless you need someone from the landing team
[14:45] <tsdgeos> dednick: easy one https://code.launchpad.net/~aacid/unity8/importcomponents/+merge/208822
[14:45] <tsdgeos> Saviq: ↑↑↑
[14:46] <Saviq> tsdgeos, yeah, saw that yesterday
[14:46] <Saviq> tsdgeos, seems like 5.2 cleans the scope somewhat?
[14:47] <Saviq> tsdgeos, that doesn't fix the crash, does it?
[14:47] <Mirv> Saviq: it needs mostly landing team I think, but for all CI Train packages we'll need a merge request to use anyhow. the landing line for Qt 5.2 is 24, I guess MR:s can be piled up there but only in the order of the pad.ubuntu.co
[14:48] <Mirv> Saviq: the order in which stuff will be landed to the PPA is at http://pad.ubuntu.com/qt52-dependencies
[14:48] <tsdgeos> Saviq: unfortunately not :D
[14:50] <Mirv> Saviq: so to be short probably not needed aside from fixing bugs and if some Qt 5.2 fix can't be merged before landing it'll be needed to be known. otherwise landing team will probably just do an empty MR for each package.
[14:51] <Saviq> Mirv, yup, works for us
[14:53] <Saviq> uh oh, looks like findInvisibleChild stopped working with 5.2 :/
[14:55] <elopio> Saviq, kgunn, can we meet next week to talk about the test plan for the release? set dates for the testing activities, and things like that.
[14:56] <Saviq> elopio, sure
[14:57] <kgunn> elopio: is there a plan that the testing will be different in terms of actually ux/scripting vs what we have today ?
[14:59] <elopio> kgunn: well, that's what we should talk about. We need to make sure that all the experiences involving unity and mir are tested, hopefully automatically.
[15:00] <elopio> what we have are some general guidelines, that we need to discuss with you, and make sure the test plans make everybody happy.
[15:01] <elopio> kgunn, Saviq: what about monday after the stand up?
[15:01] <Saviq> elopio, works for me
[15:01] <kgunn> sure
[15:06] <tsdgeos> dednick: what provides Indicators.RootActionState ?
[15:07] <tsdgeos> larsu: do you know? ↑
[15:08] <larsu> tsdgeos: the indicator service
[15:08] <tsdgeos> larsu: launchpad project?
[15:08] <tedg> Okay bregma, the reason I couldn't login is your fault :-)
[15:08] <larsu> tsdgeos: indicator-*
[15:08] <larsu> tsdgeos: every indicator has one of those
[15:08] <tsdgeos> larsu: i mean the qml code for Indicators.RootActionState
[15:08] <tsdgeos> or c++ code
[15:08] <larsu> tsdgeos: err, libqmenumodel I guess?
[15:09] <tsdgeos> can't find it in there
[15:09] <tedg> bregma, Something in the unity8 demo session installed a file: /etc/lightdm/lightdm.conf.d/55-unity8.conf
[15:09] <tsdgeos> ah wait we do in unity8
[15:09] <tsdgeos> ^_^
[15:09] <tedg> bregma, But when it got removed, it didn't delete it, because, well /etc
[15:10] <tedg> bregma, That file needs to get installed in: /usr/share/lightdm/lightdm.conf.d
[15:10]  * greyback finally able to build packages in cross compiling chroots
[15:10] <bregma> tedg, yeah, that's gotta be a bug (we can;t remove it because /etc, but it should not stop the world either)
[15:11] <tedg> bregma, I think if it's in /usr it should be fine.  I'm guessing that's why the usr directory exists :-)
[15:14]  * greyback regretting using cross compiling chroot to compile mir as a test
[15:21] <dednick> tsdgeos: it's the indicators plugin in unity8
[15:21] <tsdgeos> dednick: thanks fount it :)
[15:28] <Saviq> greyback, congratz!
[15:29] <Saviq> greyback, and yeah, mir still takes probably quite some time ;)
[15:30] <greyback> Saviq: it failed :(
[15:30] <Saviq> greyback, how?
[15:30] <Saviq> greyback, you get the full log in a file symlinked from a .build file in wherever you built it (or ..)
[15:32] <greyback> Saviq: I know. http://pastebin.ubuntu.com/7010931/ is the message.
[15:36] <Saviq> greyback, interesting, this looks like a legit error
[15:37] <greyback> Saviq: yep. Am gonna try compiling unity8 before trusting the chroot, just in case
[15:37] <Saviq> greyback, I'll kick one here, too
[15:56]  * Saviq loves it how VBox asks ~6 times whether you want to upgrade the extension pack
[16:03] <Saviq> Mirv, so we have row 28 in CI train that fixes the unity8 crasher, maybe it'd make sense to just include it in your silo
[16:03] <Saviq> Mirv, want me to list it somewhere?
[16:04] <Saviq> Mirv, looks like Qt is almost complete in there \o/
[16:04] <Saviq> sil2100, any word on the Unity8 landing? found any issues?
[16:08] <Saviq> tsdgeos, one unfortunate result of 5.2 is that try* stops working - «module "Qt.test.qtestroot" is not installed», we'll have to see how we can work around that
[16:08] <tsdgeos> oh :/
[16:08] <sil2100> Saviq: no issues, published
[16:10] <Saviq> tsdgeos, worst thing is, it's actually only exported in qmltestrunner
[16:10] <Saviq> tsdgeos, so yeah, we'll need some trickery
[16:10] <tsdgeos> Saviq: didn't we have our own testrunner? maybe we can just fake it?
[16:10] <Saviq> tsdgeos, we have something, but it's not always used
[16:10] <Saviq> tsdgeos, but yeah, some faking needs to happen
[16:11] <Saviq> sil2100, oh great, thanks!
[17:52] <tedg> greyback, I'm confued by this: http://bazaar.launchpad.net/~mir-team/unity-mir/trunk/view/head:/debian/com.canonical.Unity.conf
[17:52] <tedg> greyback, It seems like we're setting up a user process to get a well known name on the system bus?
[17:54] <greyback> tedg: yes, is wanted by powerd
[17:54] <greyback> tedg: not a long term solution obviously
[17:54] <tedg> greyback, Yeah, it breaks my desktop :-)
[17:54] <tedg> Well not breaks, causes errors to be generated everytime dbus restarts.
[17:55] <tedg> Why isn't powerd talking to the system compositor for that?
[18:15]  * greyback EODs
[18:57] <ChrisTownsend> mhr3: Hey, are you around?  I have a question about a home scope behavior.
[20:32] <mhr3> ChrisTownsend, hey
[20:33] <ChrisTownsend> mhr3: Hi
[20:35] <ChrisTownsend> mhr3: What is the expected behavior when you do a search and get "More suggestions", close the Dash, then open the Dash and havea clear Search bar?  Should the previous "More suggestions" still be there?
[20:35] <mhr3> no
[20:36] <ChrisTownsend> mhr3: Ok, then we have a bug.  I take it that you don't know of an already existing bug for this.
[20:37] <mhr3> nope
[20:37] <ChrisTownsend> mhr3: Ok.  Thanks for confirming the expected behavior.
[20:39] <ChrisTownsend> mhr3: One last question.  Would you say that is a home scope issue?  I'm trying to figure out what to report this bug against.
[20:50] <mhr3> maybe
[20:50] <mhr3> maybe some caching race
[20:52] <ChrisTownsend> mhr3: It's quite easy to reproduce and an AP test fails almost every time because of it.
[20:53] <mhr3> how are you supposed to clear the search?
[20:54] <mhr3> cause doing that resets everything here
[20:54] <ChrisTownsend> mhr3: I would think an empty Search Bar would be enough to clear the search.
[20:55] <mhr3> yea, but how do you do that
[20:55] <mhr3> just backspace the previous search after opening the dash?
[20:55] <ChrisTownsend> Yeah, that's how the AP does it.
[20:56] <mhr3> works fine here
[20:56] <ChrisTownsend> Hmmm
[20:56] <ChrisTownsend> So if I type something like playstation, I get More suggestions for stuff.
[20:57] <ChrisTownsend> Then I close the Dash and then reopen and Backspace the search bar and More suggestions is still there.
[20:57] <ChrisTownsend> Maybe my machine is borked????
[21:03] <Saviq> ChrisTownsend, I think I get the same, looks like the scopes are waiting for the network
[21:03] <Saviq> ChrisTownsend, if you wait a bit (a few seconds), do the results get reset?
[21:03] <ChrisTownsend> bschaefer cannot reproduce and I have another machine that cannot reproduce the issue.
[21:04] <ChrisTownsend> Saviq: Nope More suggestions stays there on this one machine.
[21:05] <ChrisTownsend> I'm running a locally built version of Unity on this machine though.  I wonder if some env is getting screwed up.  I'll try the version from main and see what happens.
[21:05] <bschaefer> ChrisTownsend, very odd indeed, im running trunk compiz/unity/nux
[21:07]  * ChrisTownsend Shrugs
[21:07] <ChrisTownsend> Sorry for the false alarm
[21:10] <ChrisTownsend> Using Unity from main on the same machine does not reproduce the issue.
[21:10] <ChrisTownsend> I'll go quietly back to my corner:)
[21:17] <bschaefer> ChrisTownsend, let me upgrade first :)