[07:43] <tsdgeos> Saviq: mhr3: in https://bugs.launchpad.net/unity8/+bug/1229144 when you say "Missing scope views" you mean that there is something in the scope bar but that switching to it renders and empty screen?
[07:50] <tsdgeos> unity7/compiz guys, you aware taking screenshots renders a black screen?
[07:51] <hyperair> no?
[07:51] <hyperair> works for me in raring.
[08:02] <tsdgeos> hyperair: saucy here
[08:03] <hyperair> =\
[08:05] <tsdgeos> i guess i shall report a bug
[08:07] <Cimi> mzanetti, hey :)
[08:07] <mzanetti> Cimi: ciao
[08:07] <mzanetti> Cimi: I solved your issue
[08:07] <Cimi> \o/
[08:07] <Cimi> what was
[08:08] <mzanetti> Cimi: http://paste.kde.org/pec03cfc0
[08:08] <mzanetti> Cimi: this patch should apply to your branch and just make it work... its easy enough to understand I'd say
[08:08] <tsdgeos> ah
[08:08] <tsdgeos> the old drag doesn't drag :D
[08:08] <tsdgeos> didn't we have code for it already?
[08:08] <mzanetti> tsdgeos: yeah... autopilot itself actually does
[08:09] <mzanetti> tsdgeos: calling drag() from autopilot would work
[08:09] <mzanetti> tsdgeos: but drag also does the mousePress and mouseRelease
[08:09] <tsdgeos> ahhh
[08:09] <Cimi> mzanetti, yeah indeed
[08:09] <mzanetti> tsdgeos: in this test we're doing mouseMove()
[08:09] <Cimi> mzanetti, but you said you already tried this, isn't it?
[08:09] <tsdgeos> i c
[08:09] <mzanetti> Cimi: yeah... I did... apparently some mistake which broke it in the first try
[08:10] <Cimi> mzanetti, ah ok ;)
[08:10] <Cimi> well, great!
[08:10] <mzanetti> Cimi: you still need to adjust the tests for the new values tho...
[08:10] <mzanetti> but that shouldn't be a bit issue now I guess
[08:17] <mhr3> tsdgeos, yep
[08:17] <tsdgeos> mhr3: oki tx
[08:30] <tsdgeos> mzanetti: one line code fix with a test case! https://code.launchpad.net/~aacid/unity8/bug1229851_fix_list_overshoot_on_height_equals_content_height/+merge/187463 can you review?
[08:32] <tsdgeos> Saviq: how does milestoning work? to what milestone do i assign https://bugs.launchpad.net/unity8/+bug/1229851 ?
[08:35] <Saviq> tsdgeos, if you expect it to land within 13.09, milestone it to that
[08:35] <tsdgeos> hmmm ok
[08:36] <Saviq> tsdgeos, but it's not really needed if you're already working on it
[08:36] <Saviq> tsdgeos, it's more of a planning feature
[08:36] <tsdgeos> ah
[08:36] <tsdgeos> ok
[08:36] <tsdgeos> i thought it had those autoclose and whatnot features
[08:36] <Saviq> tsdgeos, re "missing scope views", I've seen just completely blank scope pages - no header - no nothing
[08:36] <Saviq> tsdgeos, it will autoclose regardless
[08:36] <tsdgeos> but still an entry in the dashbar
[08:36] <tsdgeos> right?
[08:37] <Saviq> tsdgeos, yes yes
[08:37] <tsdgeos> ok
[08:37] <Saviq> tsdgeos, it's all *there*, just that it's completely blank
[08:38] <Saviq> brb reboot
[08:49] <Saviq> tsdgeos, ah! so it had to be *exactly* the same size to hit the issue?!
[08:49] <Saviq> crazy
[08:50] <tsdgeos> Saviq: yep
[08:50] <tsdgeos> it's what flickable does
[08:50] <tsdgeos> which tbh is a bit strange of a default behaviour if you ask me
[08:50] <Saviq> indeed
[09:05] <tsdgeos> should i worry about the lot of
[09:05] <tsdgeos>  /build/buildd/glib2.0-2.37.93/./gobject/gsignal.c:2475: signal 'changeset-started' is invalid for instance '0x7f0bdc008720' of type 'DeeSharedModel'
[09:05] <tsdgeos> i'm getting?
[09:06] <Saviq> mhr3, pstolowski ↑?
[09:12] <pstolowski> tsdgeos, Saviq : looks like you haven't updated dee
[09:12] <mhr3> tsdgeos, ... yea ^
[09:12] <tsdgeos> not distro released?
[09:13] <mhr3> yet somehow you have updated dee-qt?
[09:13] <tsdgeos> i've dist-upgraded
[09:13] <tsdgeos> nothing to update
[09:13] <tsdgeos> i'm clean
[09:13] <tsdgeos> which dee, dee-qt versions should i have?
[09:13] <mhr3> tsdgeos, apt-cache policy libdee-1.0-4?
[09:14] <tsdgeos> 1.2.6+13.10.20130904-0ubuntu1 both installed and candidate
[09:14] <mhr3> you need 1.2.7
[09:15] <mhr3> tsdgeos, and what qtdeclarative...dee-plugin do you have?
[09:15] <tsdgeos> i guess it isn't in the distro yet?
[09:15] <Saviq> 3.3+13.10.20130924.2-0ubuntu1 here
[09:15] <tsdgeos> 3.3+13.10.20130924.2-0ubuntu1
[09:15] <tsdgeos> same
[09:15] <Saviq> tsdgeos, mhr3 https://launchpad.net/ubuntu/+source/dee
[09:16] <Saviq> not yet in distro - it's in -proposed
[09:16] <mzanetti> Saviq: pushed the switching preview branch. flickering is gone.
[09:16] <Saviq> mzanetti, cool
[09:16] <mhr3> of course.. stuck in proposed
[09:16] <mzanetti> Saviq: I tried with the darker background in the reviewplaceholder... doesn't work visually
[09:16] <Saviq> mzanetti, I just need tests and will MR the LazyImage
[09:16] <Saviq> mzanetti, ok
[09:16] <mhr3> yet dee-qt was released
[09:17] <mhr3> tsdgeos, anyway, i'm awesome an the code will work even with this mismatch
[09:17] <mzanetti> Saviq: I'd say I'll try to make it context aware now, ok? is there anything more important I should handle?
[09:17] <mhr3> tsdgeos, so just ignore it
[09:17] <mzanetti> Saviq: i.e. scrolling the items behind the openeffect etc
[09:17] <tsdgeos> ok
[09:19] <Saviq> mzanetti, not according to https://launchpad.net/~mzanetti/+upcomingwork ;)
[09:20] <Saviq> mzanetti, just added https://bugs.launchpad.net/unity8/+bug/1226514 for you
[09:21] <tsdgeos> ah there's a new bug i found, at least in the desktop
[09:21] <tsdgeos> if you go to applications, expand the first category and then click on search
[09:21] <Saviq> tsdgeos, just filing
[09:21] <Saviq> tsdgeos, and it's not new
[09:21] <tsdgeos> something goes unhappy
[09:21] <Saviq> tsdgeos, told you about it Monday ;)
[09:21] <tsdgeos> sure
[09:21] <tsdgeos> i meant new as not unfiled ;-)
[09:28] <Saviq> tsdgeos, bug #1230187
[09:29] <tsdgeos> Saviq: tx
[09:40] <mzanetti> tsdgeos: sorry... just wanted to get started on your review, noticed Saviq is done with it already
[09:45] <Saviq> mzanetti, slacker
[09:45] <mzanetti> :D
[09:48] <Cimi> mzanetti, whats assCleanup ?
[09:48] <Cimi> *add
[09:48] <Cimi> ahah
[09:48] <Cimi> nice typo
[09:53] <mzanetti> lol
[09:53] <mzanetti> where?
[09:53] <mzanetti> rofl. did I make that typo?
[09:53] <mzanetti> Cimi: ^
[09:54] <Cimi> mzanetti, no I did
[09:54] <Cimi> self.addCleanup(self._maybe_release_finger)
[09:54] <mzanetti> yeah... typo of the month
[10:01] <mzanetti> do you know what should be on them?
[10:01] <mzanetti> err. wrong channel :D
[10:18] <Cimi> mzanetti, so what does addCleanup do?
[10:21] <mzanetti> Cimi: this is called when the object is destroyed.
[10:21] <Cimi> mzanetti, ok!
[10:22] <mzanetti> Cimi: in this particular case it does the release() for the mousePress in case the test would abort
[10:22] <mzanetti> Cimi: because we're doing press(), move(), assert(), release()
[10:22] <mzanetti> Cimi: so it could happen that the assert() bails out before reaching the release() and it would mess up with the mouse state for the next test
[10:23] <tsdgeos> Saviq: bug 1229144 *is* weird, even replacing Dash/GenericScopeView.qml with a red Rectangle it only appears in some of the scopes :-S http://paste.ubuntu.com/6153890/
[10:24] <Saviq> tsdgeos, yeah, mhr3 suspected a relation to https://bugs.launchpad.net/unity8/+bug/1227242
[10:24] <tsdgeos> oh
[10:24] <tsdgeos> so we got a real lockup in the scene graph renderer?
[10:25] <tsdgeos> nice
[10:25] <tsdgeos> go and tell all of those that don't want 5.1 in :D
[10:25] <mhr3> the good is that there's 3 more weeks to re-integrate it, right? :)
[10:29] <Cimi> mzanetti, how can I test if something happens instantaneously ?
[10:29] <Cimi> mzanetti, I want to test that a tap outside the hud button dismisses immediately the hud button
[10:29] <Cimi> mzanetti, but there's the timeout too which dismisses the hud in 1 second in any case
[10:29] <Cimi> I want to test that it dismisses immediately
[10:30] <mzanetti> Cimi: don't use Eventually() in that case
[10:30] <mzanetti> Cimi: but be aware that immediately really means immediately in that case...
[10:31] <mzanetti> Cimi: you could use Eventually with timeout=1 to make sure it happens in at max 1 second. maybe you could even use timeout=0.5, but I havent tried that yet
[10:31] <Cimi> mzanetti, syntax for timeout of 0.5?
[10:32] <mzanetti> Cimi: self.assertThat(someVariable, Eventually(Equals(0), timeout=0.5))
[10:32] <Cimi> mzanetti, grazie
[10:33] <mzanetti> Cimi: per niente
[10:33] <mzanetti> Cimi: as I said... I've no idea if 0.5 works in here of if it expects integers.
[10:44] <Cimi> mzanetti, I can do a wait or a sleep if 500ms and check?
[10:44] <Cimi> without eventually?
[10:45] <mzanetti> Cimi: I guess this is a valid exception to my "no sleep policy"
[10:46] <mzanetti> Cimi: but not sure how that will behave on jenkins... if the ui stutters for half a second we're doomed
[10:47] <mzanetti> Cimi: ah... actually. in that case, make sure to check if the according property immediately goes to whatever triggers the hiding of the button, but not check if the hiding animation is actually completed yet
[10:47] <Cimi> mzanetti, it works
[10:47] <Cimi> the 0.5
[10:47] <mzanetti> ok. nice
[10:47] <Cimi> mzanetti, I added it to the release without tap (where there's a timeout in the code of 1000ms)
[10:47] <Cimi> mzanetti, and indeed it fails with 0.5
[10:51] <mhr3> Saviq, one quickie pls - https://code.launchpad.net/~mhr3/unity8/accept-image-uris-from-scopes/+merge/187487
[10:51] <mzanetti> tsdgeos: can I expand a category in the LVWPH without moving it?
[10:52] <tsdgeos> LVWPH doesn't do expansion
[10:52] <tsdgeos> so yeah
[10:52] <tsdgeos> look at
[10:52] <tsdgeos> GenericScopeView
[10:52] <tsdgeos> item.filter = false
[10:53] <tsdgeos> mzanetti: ↑
[10:54] <Cimi> mzanetti, tsdgeos Saviq branches are ready https://bugs.launchpad.net/unity8/+bug/1224480
[10:55] <Saviq> greyback, hey, can you have a look at the trace in https://bugs.launchpad.net/unity8/+bug/1229888
[10:55] <Saviq> greyback, and see if it's an obvious fix?
[10:55] <mzanetti> tsdgeos: thanks... seems to do what I need
[10:56] <mzanetti> Cimi: lets see what jenkins thinks of your timeout=0.5
[10:56] <Cimi> mzanetti, hah
[10:57] <Cimi> mzanetti, if you can think of a better way...
[10:57] <mzanetti> Cimi: no, not really
[10:58] <mzanetti> Cimi: in theory its great that you test this. but I'm afraid we're going to hit infrastructure limits with this
[10:58] <Cimi> mzanetti, my goal is to make sure that the hud button disappears in 999ms from the tap
[10:58] <mzanetti> Cimi: but lets see...
[10:58] <Cimi> mzanetti, I can change it to 0.9 ?
[10:58] <pstolowski> mzanetti: hey! the method for manual cancellation of activation/preview requests from the shell should cancel everything (both action activation and preview), right? or you just need to cancel actions?
[10:58] <Cimi> mzanetti, 0.99?
[10:58] <Cimi> or 0.7
[10:58] <Cimi> it has to be quick though
[10:59] <mzanetti> pstolowski: both I'd say. it will be called when closing the preview screen
[10:59] <pstolowski> mzanetti: or perhaps two methods to cancel, so you can pick what's needed?
[11:00] <mzanetti> pstolowski: right now won't need to be able to distinguish. if you think its more future proof we can have both
[11:00] <greyback> Saviq: ok
[11:00] <pstolowski> mzanetti: ok
[11:00] <mzanetti> Cimi: hmm... need to try
[11:00] <Cimi> mzanetti, so what you say is, let's see if 0.5 is fine
[11:00] <Cimi> ?
[11:00] <mzanetti> Cimi: obviously the shorter the better for the quality of the test, but also more risk for failures in jenkins
[11:00] <Cimi> in case we can do 0.9?
[11:00] <greyback> Saviq: I'm assuming it happened at random
[11:00] <Saviq> greyback, of course it did
[11:01]  * Saviq runs 20 runs of ap tests on mako to see if I get a crash out of unity8
[11:01] <greyback> Saviq: my favourite kind of crash. Ok, will see if there's anything suspicious in that codepath
[11:01] <Saviq> greyback, thanks
[11:08] <dednick> larsu: ping
[11:08] <larsu> dednick: hey
[11:09] <dednick> larsu: hey. having an interesting issue with the messaging menu. What format are the icon/appIcon supposed to come in? string or serialised?
[11:09] <larsu> dednick: serialized, but the simplest form of serialization is just the icon name
[11:09] <larsu> (in the case of themed icons without fallbacks)
[11:10] <dednick> larsu: g_menu_item_set_attribute (item, "x-canonical-app-icon", "s", app_icon);
[11:10] <dednick> larsu: g_menu_item_set_attribute (item, "icon", "s", iconstr);
[11:12] <dednick> larsu: but they're still coming as (sv) which is the serialised gvariant format.
[11:12] <larsu> dednick: I can't find either of those in trunk. Are you working off the right version?
[11:13] <larsu> ah, there's still one iconstr thing left, in im-phone-menu.c
[11:13] <larsu> but that shouldn't bother you, as its only for sources, which we don't show on the phone
[11:13] <larsu> *it's
[11:13] <dednick> larsu: ah.crap .i pulled wrong branch
[11:14] <dednick> sorry
[11:14] <larsu> dednick: no worries. Are you working on getting the unitymenumodel/messaging branch landed in unity8?
[11:14] <larsu> we're getting quie a few bugs reported that would be fixed by that
[11:15] <dednick> larsu: somewhat. it's been done for about 2 weeks... just waiting review
[11:15] <larsu> dednick: please ping someone to do that... the release isn't far away and it could really use some testing
[11:16] <larsu> and I'm annoyed by people pinging me all the time that it doesn't work :P
[11:21] <mzanetti> dednick: I can review it...
[11:21] <dednick> mzanetti: just trying to fix the icons. :)
[11:22] <mzanetti> dednick: should this make the messaging icon in the panel work again?
[11:24] <dednick> mzanetti: well that should work with trunk. but i dont think it's landed on image yet
[11:25] <mzanetti> dednick: what exactly should I pay attention on when testing this branch?
[11:26] <dednick> mzanetti: that it operates exactly the same as the previous one.
[11:26] <mzanetti> heh, ok
[11:27] <dednick> mzanetti: yeah, most of my work involves absolutely nothing changing. yay
[11:27] <dednick> yet still ends with thousands of lines changing
[11:29] <dednick> mzanetti: ok, icons are fixed up. you can review now.
[11:41] <mzanetti> Saviq: how this this happen? https://bugs.launchpad.net/unity8/+bug/1229888
[11:42] <Cimi> I have to go to the dentist, yuppie
[11:42] <mzanetti> Saviq: did you use the UI or during a test run?
[11:42] <Saviq> mzanetti, just found a crash in /var/crash
[11:42] <Saviq> mzanetti, no more details I'm afraid
[11:42] <Cimi> pls have a look at the branches :)
[11:42] <mzanetti> Saviq: I found one on friday where the DDA would crash randomly. luckily I got a good trace.
[11:45]  * Saviq has problems wrapping his head around the sizes of images I need to test the LazyImage... food, then...
[11:48] <mzanetti> dednick: is the legacy stuff still needed? for example the DefaultIndicatorsPage.qml (without the 2) ?
[11:49] <dednick> mzanetti: removed in another MP
[11:49] <mzanetti> ok
[13:09] <kgunn_> Saviq, MacSlow hey guys...jdstrand just pinged me on an item to address soon after oct, https://bugs.launchpad.net/unity-mir/+bug/1230091
[13:09] <Saviq> kgunn_, MacSlow is probably not involved - greyback is
[13:10] <Saviq> kgunn_, "soon after oct"?
[13:10] <MacSlow> kgunn_, Saviq: yeah... I hope so too
[13:10] <Saviq> kgunn_, sounds like low priority then...
[13:10] <kgunn_> Saviq, yeah...let me check on timing
[13:10] <kgunn_> he's got it marked against saucy...
[13:10] <kgunn_> but his wording sounds like post oct
[13:13] <kgunn_> Saviq, yeah...so high priority for 13.10 (read as strongly desired), then critical for 14.04
[13:14] <Saviq> kgunn_, right, what I thought
[13:14] <Saviq> kgunn_, I already asked greyback to look into it
[13:15] <Saviq> at least in terms what's there, what still needs doing etc.
[13:34] <Saviq> greyback, hangout
[13:34] <greyback> yep, trying
[13:55] <davidcalle> sil2100, ping
[13:57] <sil2100> davidcalle: pong
[13:58] <davidcalle> sil2100, hi ! Do you have a minute for a quick mp ? https://code.launchpad.net/~davidc3/cupstream2distro-config/more-server-scopes/+merge/187519
[14:01] <sil2100> davidcalle: hm, but let me understand it more correctly - those were moved to the server side?
[14:02] <sil2100> davidcalle: since if those are server side, I guess we don't want to release them to ubuntu archives, right? ;)
[14:03] <davidcalle> sil2100, aaand I'm realizing it's the wrong file
[14:04]  * davidcalle moves the changes to no-dailies/unity
[14:05] <greyback> dammit my mic must be dead
[14:08] <sil2100> ;)
[14:08] <sil2100> davidcalle: right!
[14:09] <sil2100> davidcalle: anyway, sorry about that - since when I removed them from the dailies I probably forgot adding them to no-dailies instead
[14:11] <davidcalle> sil2100, nevermind we do have a *lot* of scopes to manage, mp fixed ;)
[14:14] <Saviq> mzanetti, I got the LazyImage, want me to propose it itself, or integrate with the previews?
[14:14] <Saviq> mzanetti, feels like it could conflict with your stuff?
[14:15] <mzanetti> Saviq: uh... why? did you change the old previews to make use of it?
[14:15] <Saviq> mzanetti, not yet
[14:15] <Saviq> mzanetti, that's what I'm asking
[14:15] <Saviq> mzanetti, I just have the component + tests right now
[14:15] <mzanetti> Saviq: so don't... just propose the component. once its landed I'll make use of it
[14:15] <Saviq> mzanetti, yup, cool
[14:18] <kgunn> just curious, quick pole....when you guys flash/test....are you using cdimage or system ?
[14:22] <dednick> larsu: ping
[14:22] <larsu> dednick: ...
[14:22]  * larsu never knows what to say when someone pings him with "ping"
[14:23] <dednick> larsu: pong maybe ? or hi?
[14:24] <dednick> larsu: :) anyway. having issues with messaaging items. phone app doesnt seem to be activating when touching the app icon. i seem to be sending off the activation signal though
[14:24] <larsu> dednick: I already said hi this morning ;)
[14:25] <dednick> larsu: this is with the new messaging branch btw
[14:25] <larsu> dednick: did it work with the old one?
[14:26] <Saviq> mzanetti|food, https://code.launchpad.net/~unity-team/unity8/lazy-image/+merge/187525
[14:26] <dednick> larsu: well, the very old one i think so. but it hasnt since we moved to new. because the actions changed and couldnt do with qmenumodel
[14:27] <larsu> dednick: okay. The messaging menu doesn't really do much besides sending a message to the application that the message originated from.
[14:27] <larsu> dednick: which is then responsible for presenting itself
[14:28] <larsu> I have no clue if this even works anymore with the new application story
[14:28] <dednick> larsu: i'm getting a bunch of warning messages when i start up
[14:28] <dednick> (process:3645): Indicator-Messages-WARNING **: an application with id 'phone-app-sms.desktop' is not installed
[14:28] <dednick> larsu: what registers the apps? themselves?
[14:28] <larsu> dednick: do you have an application with that desktop id installed?
[14:28] <larsu> dednick: yes.
[14:29] <dednick> larsu: nope.
[14:29] <larsu> dednick: you'll get this warning for non-existing app ids in the gsettings key com.canonical.indicator.messages applications
[14:29] <larsu> you can remove those apps manually
[14:29] <dednick> ah. gsettings
[14:29] <larsu> we decided to not remove them from the settings in case a user uninstalls/installs
[14:30] <larsu> (apps keep all other settings in that case, too)
[14:30] <dednick> crap. now to remember how to gsettings from commandline
[14:30] <larsu> but yeah, that warning should be removed
[14:30] <larsu> dednick: gsettings get com.canonical.indicator.messages applications
[14:30] <larsu> and then "set" with an additional argument of the value
[14:31] <larsu> you can also jut clear it - applications will re-register themselves when they restart
[14:34] <dednick> larsu: ok, so you have to have started the application for it to register itself
[14:35] <larsu> yes
[14:35] <larsu> also, it needs to be running in order to show anything in the messaging menu
[14:35] <dednick> hm. thats interesting
[14:35] <larsu> why?
[14:36] <larsu> we need some way to tell the app that a message was clicked on or responded to
[14:36] <dednick> i just started the phone and messaging app and the setting is still empty after clearing and rebooting phone
[14:36] <dednick> might help if i started the messaging service though
[14:37] <larsu> I don't know much about that app
[14:37] <larsu> it won't appear in there until it calls messaging_menu_app_register()
[14:37] <dednick> oh. it is started.
[14:37] <larsu> which it must do if it wants to add messages
[14:37] <larsu> so if you see messages, it definitely registered
[14:37] <dednick> ok, maybe i need to trigger a message first
[14:38] <larsu> if so, the app doesn't behave according to conventions (but it would still work)
[14:39] <Saviq> fginther, hey, any idea why -3 is X? http://s-jenkins:8080/label/ps-saucy-server-amd64-1||ps-saucy-server-amd64-2||ps-saucy-server-amd64-3/?
[14:40] <dednick> larsu: ok, it added. i think it only does it when it needs to.
[14:41] <fginther> Saviq, yes, I needed it offline for some work list night. I'll get it added back
[14:41] <Saviq> fginther, thanks
[14:41] <Saviq> fginther, we got kinda screwed by mir-ci and mir-autolanding ;)
[14:41] <larsu> dednick: okay. does indicator-messages send a bus message to the app when you activate the menu item?
[14:42] <fginther> Saviq, the load was pretty light the last few days, but yes, two hosts presents a bottleneck
[14:44] <dednick> larsu: i have no idea. havent got that far yet
[14:45] <larsu> dednick: you have a message in the menu, right?
[14:45] <dednick> larsu: yep
[14:45] <larsu> dednick: click on it while running `dbus-monitor sender=com.canonical.indicator.messages`
[14:45] <Saviq> greyback, can you please update the status / affects on bug #1228345, too
[14:45] <larsu> s/click/tap/ I guess
[14:46] <greyback> Saviq: ack
[14:46] <fginther> Saviq, back online
[14:47] <Saviq> fginther, thanks
[14:48] <Saviq> greyback, mzanetti|food, tsdgeos, kgunn, gotta run early, will be back later (7pm UTC or something) if you need me
[14:48] <tsdgeos> ok
[14:48] <kgunn> o/
[15:01] <tsdgeos> yahooo, i found why bug 1229144 happens
[15:02] <tsdgeos> it is a Qt bug
[15:02] <tsdgeos> now need to see if it was fixed in 5.1 or 5.2
[15:02] <tsdgeos> or fix it myself
[15:02] <kgunn> greyback: i was triaging this mornin, can you live w/o a mir query for composition state till post-v1 ? or need that now...
[15:02] <dednick> larsu: no dbus message for missed call, only for sms. Notifications seem to stop coming in after attempting to activate the dialer from the menu item.
[15:02] <kgunn> greyback: carr is going thru the api distillation process anyway
[15:02] <larsu> dednick: what do you mean by "notifications"?
[15:03] <dednick> larsu: sorry, i meant the menu items dont get added
[15:04] <greyback> kgunn: can live without
[15:04] <larsu> dednick: sounds like a bug in the app to me :D  Do you see the same without your branch?
[15:04] <greyback> dammit firefox, why did you throw away my big LP comment
[15:04] <dednick> larsu: but the dbus message isn't being sent
[15:05] <dednick> larsu: we dont have app activations in trunk.
[15:05] <larsu> dednick: yeah I'm trying to figure that one out right now (I was commenting about the "menu items dont get added" part)
[15:05] <larsu> dednick: app activations?
[15:06] <dednick> larsu: well the menu items only seem to stop being added after we attempt the activation.
[15:06] <dednick> larsu: opening the app by tapping the app icon.
[15:07] <larsu> dednick: there's no such thing. Tapping anywhere in the message should lead you to the app
[15:07] <larsu> dednick: more precisely: the screen in the app that contains the referenced message
[15:08] <larsu> dednick: I don't understand what you mean by "stop being added". When you receive a text for the second time, it doesn't get added to the menu if you've activated the first one?
[15:11] <dednick> larsu: yes. but i'm not sure. it might just be randomly doing it now
[15:21] <stgraber> hey there, anyone from the Unity team who could help me figure out why the dash is completely busted on Edubuntu?
[15:21] <stgraber> it's kinda critical for us to get it back to working order for Beta 2 which is due out tomorrow :)
[15:22] <sil2100> bregma, andyrock: ^
[15:22] <sil2100> bregma, andyrock: could you guys give stgraber a hand?
[15:22] <stgraber> and by that I mean that Unity looks like it's working, the launcher, panel, hud, ... all work as expected but none of the lens or scopes are loaded and the dash simply never shows anything
[15:22] <sil2100> Then mhr3 as well ^
[15:23] <stgraber> Edubuntu is a superset of Ubuntu, so as far as I can tell all the packages are there, all the binaries are there too, they just don't happen to get started and I have no clue why
[15:24] <bregma> stgraber, maybe check the logs in ~/.cache/upstart for some kind of error?
[15:26] <stgraber> bregma: I did have a quick look and all I'm seeing is unity complaining it can't talk to the dbus services (as the daemons aren't running) but I haven't yet found a clue as to why they aren't getting spawned
[15:27] <mhr3> sil2100, oh you're here, we have a question
[15:27] <stgraber> bregma: http://paste.ubuntu.com/6154922
[15:28] <mhr3> sil2100, i have a branch that bump unity-core abi, ie does libunity-core-6.0-7 -> libunity-core-6.0-8
[15:28] <mhr3> sil2100, can we make it so that unity8 will keep working with -7 and unity7 will be linked with -8?
[15:28] <mhr3> sil2100, or should we just request unity8 rebuild against -8?
[15:29] <bregma> stgraber, I think you will need help from mhr3
[15:29] <sil2100> uuuuh, is this ABI bump completely necessary?  I think a request to rebuild unity8 is needed, since we generally don't like when things depend on different versions
[15:30] <dednick> larsu: looks like it must be the app. i got a dbus message going to path=/com/canonical/indicator/messages/telephony_service_call_desktop , but it didnt do anything
[15:30] <mhr3> stgraber, your unity-scope-home isn't working... beats me why
[15:31] <dednick> larsu: it's flaky as all hell though. randomly stops responding to message adds/removes
[15:31] <stgraber> mhr3: hmm, hold on a sec, I think I know why :)
[15:31] <mhr3> sil2100, i'm afraid it is
[15:32] <stgraber> mhr3: ok found the issue, that one wasn't installed (unity-scope-home) so all the lenses were there but nothing was there to display them...
[15:32] <mhr3> stgraber, yea, that would explain it :)
[15:33] <sil2100> mhr3: :<
[15:34] <mhr3> sil2100, any other ideas?
[15:34] <stgraber> mhr3: ok, confirmed that's the problem. edubuntu had a conflict with the -shopping-lens package which got merged into the home scope (the home scope "provides" it) which resulted in a removal of the home scope
[15:34] <larsu> dednick|lunch: what's flaky — the app or the messaging menu?
[15:34] <sil2100> mhr3: I guess we need to bump the ABI and rebuild all dependend packages - no other clean way
[15:35] <mhr3> didrocks will kill me soon
[15:35] <sil2100> mhr3: yes, he will!
[15:35]  * didrocks aims
[15:36] <mhr3> didrocks, but, but, it's c++ fault!
[15:36] <didrocks> can you sum that up in one line?
[15:37] <mhr3> didrocks, we need to do abi bump to libunity-core, so need to rebuild unity8 (and other libunity-core deps, but afaik unity8 is the only one)
[15:37] <mhr3> besides unity7 of course
[15:37] <didrocks> so unity7 + unity8
[15:37] <mhr3> yea
[15:38] <didrocks> if the release team is happy to take whatever is in unity trunk as well, we can handle that
[15:38] <didrocks> stgraber: please look at the unity stack (unity component), there are other stuff that will be bundled in: http://people.canonical.com/~platform/cu2d/results
[15:40] <mhr3> i see just 6 other commits, mostly fixes
[15:41] <mhr3> bregma, fyi ^
[15:41] <bregma> we're _only_ doing fixes right now
[15:42] <stgraber> didrocks: looks to me like it's only bugfixes for those packages that aren't specific to touch (the mediascanner scope appears to have a small feature change), so I'm not against getting those in but it'll have to wait till after Beta 2
[15:42] <didrocks> stgraber: well, it's the only way to have the tests running if you want your ABI breakage fix
[15:43] <didrocks> as we run tests on trunk
[15:43] <didrocks> and we want to validate what we push to distro
[15:44] <stgraber> didrocks: and did anyone say we needed that before beta2 is out? (sorry, I'm not running the Beta 2 release, infinity is, so I only have limited knowledge about what's going on at the moment)
[15:44] <didrocks> stgraber: didn't you mention that your edubuntu unity dash was empty?
[15:44] <didrocks> and so you needed that ABI breakage?
[15:44] <didrocks> maybe I'm mixing 2 conversations, more than possible ;)
[15:45] <stgraber> didrocks: you're mixing
[15:45] <stgraber> didrocks: edubuntu indeed had an empty dash but that was because we didn't have the home scope installed due to an old conflict against a now deprecated package that's provided by the new home scope package
[15:45] <didrocks> stgraber: ah phew! I was afraid it was linked to mhr3-that-I-need-to-kill :)
[15:45] <stgraber> didrocks: the fix there is for me to drop the conflict from the edubuntu-live package and instead push a gsettings key in edubuntu-artwork to disable remote scopes (instead of conflicting with them)
[15:46] <didrocks> stgraber: ok, perfect then! sure for the rest, after beta2 ;)
[15:46] <mhr3> didrocks, so we shouldn't top-approve that branch yet?
[15:47] <didrocks> mhr3: not yet please, as unity7 will stage in proposed and unity8 will then be blocked
[15:47] <didrocks> mhr3: let's do that once the gate is opened again for everything
[15:48] <mhr3> didrocks, meaning, tomorrow?
[15:49] <didrocks> mhr3: yeah, if all moons align ;)
[15:49] <mhr3> didrocks, ok, will you ping me if they do? or perhaps just approve the branch right away then
[15:49] <didrocks> mhr3: yeah, let's plan for a smooth transition, mind adding that to the landing ask?
[15:50] <didrocks> (with not merge yet as a comment)
[15:50] <didrocks> so that we don't loose track
[15:50] <mhr3> sure, thostr_ pls ^ don't think i have edit rights there
[15:51] <didrocks> mhr3: AHAH, I do, I'll write mean things on you for sure on that line! ;)
[15:52] <mhr3> didrocks, that's why i wanted thostr_ to do it, he's nice compared to you :P
[15:52] <didrocks> :p
[15:52] <thostr_> thostr_: so, what am I supposed to screw up?
[15:55] <mzanetti> mzanetti: don't screw anything up :P
[15:57] <didrocks> didrocks: everything will be fine :)
[16:20] <eean> hey is there a Qt 5 library for using the system tray protocol of Unity?
[16:21] <eean> yo mzanetti o/
[16:21] <mzanetti> hi eean
[16:21] <mzanetti> eean: unity7?
[16:22] <eean> well something compatible with unity around now :)
[16:22] <mzanetti> dednick: do you know?^
[16:22] <eean> currently my app uses KNotifications, but the unity system tray dbus api is different enough from KDE's that it's sort of the worse of all worlds
[16:23] <mzanetti> I think its the standard notification spec with unity specific extensions
[16:23] <eean> well yea, last I tried it doesn't work without the extensions
[16:24] <eean> so it sees the API exists and tries to use it... and then it doesn't show anything
[16:24] <mzanetti> oh..
[16:24] <mzanetti> I don't know any specifics. larsu, I guess you know about this ^
[16:24] <eean> whereas the 10-line python app using the unity apis works out-of-the-box
[16:25] <eean> so I'm wondering if I should rebuild my Qt 5 with glib support and use this api or if you have a Qt 5 library already :)
[16:27] <mzanetti> I'm quite sure there is one... but haven't used it myself
[16:28] <eean> ah well I got time to try it out
[16:30] <eean> https://www.hipchat.com/linux is the app I work on btw :)
[16:30] <mzanetti> cool :)
[16:30] <eean> judging by the crash reports (which includes uname -a) the vast majority of our users use Ubuntu so I need to get it working correctly.
[16:30] <eean> of our Linux users
[16:31] <mzanetti> eean: uses Qt5 already?
[16:33] <eean> mzanetti: yep
[16:33] <mzanetti> eean: but QWidget still I assume?
[16:33] <eean> yea. at first I tried to use QML, but that was last year and components didn't exist yet really :)
[16:34] <mzanetti> yep... last year was too early for QML on desktop
[16:34] <mzanetti> eean: are there many users which use such a thing on their phone?
[16:34] <eean> actually I stil use QtDeclarative. QtQuick 2 + QWidget doesn't seem to play nice.
[16:34] <eean> well the phone hipchat clients are using native android and ios apis
[16:35] <mzanetti> sure. but I'm wondering if such group chats are actually used a lot on phones
[16:35] <mzanetti> irc on my phone would drive me mad
[16:35] <eean> ah. yea I use it, obviously to not carry on conversations, but to respond to pings
[16:36] <mzanetti> interesting... guess an ubuntu touch app is next then ;)
[16:36] <mzanetti> still a little bit early for this kind of stuff tho
[16:37] <eean> ha yea... well if Qt WinRT port happens, then I could make a QML version of hipchat, then obviously sailfish and Ubuntu Touch is trivial
[16:37] <eean> I've been watching the WinRT branch, Digia has a least two people working on it
[16:38] <eean> I bet they announce the timeline for WinRT at the Qt conference in Berlin that's coming up
[16:39] <mzanetti> mhm... we'll see
[16:45] <eean> looks like they solved the DirectX 11 problem, which was their main blocker, now it's just the grind of porting win32->winrt
[16:45] <eean> anyways
[16:45] <eean> mzanetti: my google for libappindicator qt5 gives me nothing, any suggestions for where to look for qt5 unity libraries in general? otherwise I'll pop by here tomorrow early enough to talk to more europeans :)
[16:46] <mzanetti> eean: Saviq will be back soon. He might know
[16:46] <eean> ah cool
[16:52] <eean> hm yea so libappindicator uses Gtk3 so I probably can't use it. I wonder why it does, the code looks mostly concerned with dbus stuff.
[16:53] <eean> ah it's for the fallback code
[17:05] <mzanetti> eean: there is qtdeclarative5-notifications-plugin which might contain some hints
[17:07] <eean> cool
[17:10] <eean> though notifications are trivial to do with org.freedesktop.Notifications, it's just one d-bus call. but maybe it's related to the systray stuff.
[17:12] <eean> awesome you guys use cmake? somehow assumed you would be building qt5 apps with autofoo :D
[17:14] <mzanetti> yep. sometimes qmake too. but autotools is mostly gone
[17:37] <Rookie> hi
[19:00] <mzanetti> Saviq: yay! success :) Check out the swiping previews branch :)
[20:33] <Saviq> mzanetti, checking
[20:34] <Saviq> eean, what can I help with?
[20:41] <eean> Saviq: ah yea, getting a system tray icon in Unity with a Qt application :)
[20:41] <eean> Saviq: so I was wondering if there was a libappindicator-qt5 yet
[20:44] <eean> currently I use KNotifications but this doesn't work at all in Unity afaict
[20:45] <Saviq> eean, yeah, we've a custom lib for it indeed, and I'm not sure if there is something... Skype has an indicator menu, and it's Qt, but I don't think there are any "official" Qt libs for that
[20:47] <eean> Saviq: hm. are there any docs for it? how did Skype manage it? there's no code Unity-side to help Skype do it?
[20:47] <kgunn> mterry: we're going to try to land kdub's flicker fix...which means another bump, mind reviewing https://code.launchpad.net/~kgunn72/unity-system-compositor/bump-build-dep12/+merge/187601
[20:47] <Saviq> eean, no, nothing specific to Skype
[20:48] <eean> not even a white list? I was wondering how Amarok managed to do it, I assumed a white list. but there's a whole API for music apps so maybe that's it.
[20:48]  * eean isn't developing a music app
[20:48] <Saviq> eean, https://unity.ubuntu.com/projects/appindicators/ is a start
[20:48] <mterry> kgunn, mir version doesn't look bumped to 12 in its trunk?
[20:48] <eean> well I need docs for the dbus side of things
[20:49] <eean> I don't even understand why KNotifications doesn't work
[20:49] <kgunn> mterry: correct...its not yet
[20:49] <kgunn> mterry: plus didrocks kind of spanked me last time and told me your mp's should be ta'd first
[20:49]  * kgunn didn't understand...but complies with almight didrocks
[20:49] <Saviq> eean, we don't support the "standard" way of doing systray, for design reasons
[20:50] <Saviq> eean, and you shouldn't do DBus directly, you should wrap libappindicator instead
[20:50] <eean> Saviq: do you think that's possible for a Qt app? libappindicator links to Gtk directly for menu stuff.
[20:50] <mterry> kgunn, ta'd?
[20:50] <kgunn> mterry: top approved
[20:50] <Saviq> eean, pretty sure it's possible
[20:51] <eean> Saviq: cause yea using libappindicator was my first thought, until I looked a bit into the code
[20:51] <tedg> eean, For app indicators in Qt you can just use sni-qt
[20:51] <mhall119> Saviq: ping
[20:51] <kgunn> mterry: at any rate...won't top approve until we're all ready to go
[20:51] <Saviq> eean, right! that
[20:51] <Saviq> eean, tedg will be able to help
[20:51] <eean> aah :D
[20:51] <mterry> kgunn, ok, I commented/approved with that same comment
[20:51] <Saviq> eean, that's what Skype is using
[20:51] <kgunn> mterry: nothing gets in w/o ask mode anyway :)
[20:52]  * Saviq was just meant to say he's not the best to talk to about this stuff
[20:52]  * Saviq is all about unity8 ;P
[20:52] <eean> what is unity8 doing?
[20:52] <eean> for this
[20:52] <eean> that's not so far away
[20:52] <tedg> Saviq, Yeah, that Unity8 thing, when can I use it on my desktop?  ;-)
[20:52] <eean> hopefully sni-qt works for that
[20:52] <mhall119> Saviq: can you and I have a call tomorrow to discuss Unity plans for the 14.04 cycle and what the community team can to to help/promote it?
[20:52] <eean> heh
[20:52] <Saviq> tedg, what do you need a desktop for!
[20:52] <tedg> eean, It'll use the same stuff eventually, we just haven't ported yet as it wasn't a priority for phone.
[20:53] <eean> yea for sure is isn't :D
[20:53] <tedg> Saviq, Ubuntu Edge failed :-(
[20:53] <eean> *it
[20:53] <Saviq> tedg, true, true
[20:53] <Saviq> mhall119, you should probably target higher up :) → kgunn
[20:54] <Saviq> mhall119, but yeah, I can be there
[20:54] <Saviq> mhall119, but I won't have any concrete data
[20:54] <mhall119> kgunn: ^^ are you available tomorrow for a call?
[20:54] <eean> anyways this won't solve my issue with the Qt5 systray not working on Gnome3. the linux desktop is effed :) but one thing at a time.
[20:55] <kgunn> mhall119: actually...what might be interesting is to have a call with me & john lea (we try to do every monday)
[20:55] <kgunn> mhall119: he's got a lot of information about design feedback etc, might be able to leverage community there
[20:55] <kgunn> mhall119: as i think we'll probably undergo some design tweaks...
[20:56] <mhall119> kgunn: ok, I was hoping to do it this week, it's time for me to put together my goals for the next cycle for jono
[20:56] <mhall119> kgunn: it can be high level, like what info, resources, outreach ideas we might want
[20:56] <kgunn> mhall119: i do talk to john on friday's too...but its more execution oriented
[20:56] <mhall119> kgunn: ok, monday works for me then, what time?
[20:57] <kgunn> mhall119: i'll add you
[20:57] <mhall119> thanks
[20:57] <kgunn> mhall119: can you shot john a note as well...maybe outline the highlevel aspect and other thots
[21:01] <mhall119> good idea, thanks
[21:07] <eean> tedg: FYI, forked to here, going to port to Qt 5 and make it a normal library instead of a system tray plugin https://bitbucket.org/hipchat/hipchat-sni-qt
[21:08] <tedg> eean, Why not leave it a system tray plugin?
[21:08] <eean> doesn't that require some magic on the Qt side?
[21:08] <tedg> eean, Then when for instance Skype goes Qt5 it'll work.
[21:08]  * tedg has no clue
[21:09] <tedg> Qt *is* magic
[21:09] <tedg> :-)
[21:09] <eean> Skype not wrking is fine with me :)
[21:09] <eean> I guess ideally this code would be relicensed as LGPLv2 and then it could be integrated into KNotifications
[21:09] <eean> and made part of KDE 5 Frameworks
[21:10] <eean> or I guess submitted to Qt itself
[21:26] <eean> hm yea the included Qt patch is massive
[21:30] <eean> it implements the same d-bus api as KNotifications o.o
[21:30] <tedg> Yup.
[21:31] <eean> so why doesn't KNotifications work for me
[21:31] <tedg> Hmm, not sure.  Perhaps because it doesn't export a menu?
[21:31] <tedg> We require a menu.
[21:32] <eean> a libdbusmenu menu?
[21:32] <eean> that's possible
[21:32] <tedg> Yes
[21:32] <tedg> We do want to migrate to a GMenu menu.  But, eh, work and all that.
[21:32] <tedg> Since dbusmenu is deprecated
[21:33] <eean> gmenu doesn't have a documented dbus api
[21:34] <eean> well I already load libdbusmenu to export the normal window menu, so I maybe I just need to add it to knotifications and then I'd be set
[21:34] <tedg> In both cases you shouldn't really implement the DBus API (dbusmenu and GMenu)
[21:34] <tedg> The DBus API is considered private, and the libs wrap it.
[21:34] <eean> well how is a Qt application supposed to use GMenu? :| it's a gtk library, not just a glib library, afaik
[21:34] <tedg> It is a GIO library, which only uses GLib
[21:34] <tedg> No GTK or anything like that.
[21:35] <eean> Gnome 3 has that annoying application menu that says "Quit Application" for all apps that don't implement a gmenu for it to use
[21:35] <tedg> Yeah, we tried that.  It didn't work well.
[21:35] <eean> and then it just closes the window, it doesn't actually quit anything. my app actually has special code to quit-on-window-close for Gnome 3
[21:36] <tedg> I think it's disabled now, but really should be killed.
[22:34] <eean> hm KNotifications already exports a dbusmenu
[23:00] <eean> actually I can't even find a org.kde.StatusNotifierItem for skype, how does it work? :S
[23:21] <eean> found it and I guess I see why it doesn't work for KNotifications. the functions are the same, but the paths are totally different