[08:15] <larsu> dednick: morning. We stumbled across https://bugreports.qt.io/browse/QTBUG-32859 again (with gsettings-qt). Do you know if there's any activity towards fixing that?
[08:20] <dednick> larsu: don't think there's any activity on it.
[08:20] <larsu> too bad - this might hit us in more places
[08:21] <dednick> larsu: ya. i don't doubt it.
[08:22] <dednick> I'll bump the bug report for an update.
[08:22] <larsu> thanks
[08:22] <larsu> do we have a downstream bug as well?
[08:25] <dednick> larsu: I don't think so
[08:25] <larsu> dednick: I'll make one
[08:25] <dednick> larsu: ta
[08:25]  * larsu wonders if launchpad knows about the qt bug tracker as well
[08:26] <seb128> it doesn't
[08:26] <seb128> larsu, https://bugs.launchpad.net/launchpad/+bug/157488
[08:27] <larsu> seb128: wow you're quick. This is almost mpt-level in bug-finding skill
[08:27] <seb128> haha
[08:27] <seb128> larsu, well, I knew about that bug/looked at it in the past
[08:27] <larsu> seb128: what's the launchpad project for qt?
[08:27] <larsu> lp:qt doesn't have bugs
[08:28] <seb128> larsu, what part of qt?
[08:28] <seb128> larsu, https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+filebug
[08:28] <seb128> for qtbase
[08:28] <larsu> weird. Thanks seb128!
[08:28] <seb128> qtdeclarative is another source though
[08:29] <larsu> ya this is base
[08:36] <larsu> dednick: http://pad.lv/1460970
[08:41] <dednick> larsu: ta
[08:58] <ltinkl> dednick, larsu: will adjust the merge request
[08:59] <dednick> ltinkl: which merge request?
[08:59] <ltinkl> dednick: https://code.launchpad.net/~lukas-kde/gsettings-qt/queued-processing/+merge/259883
[09:00] <dednick> ltinkl: ah.
[09:00] <larsu> ltinkl: thanks (and sorry for being a bit padantic)
[09:00] <ltinkl> dednick: to mention the QT bug report
[09:00] <ltinkl> larsu: no problems
[09:14] <dednick> ltinkl larsu: i've commented on the MP
[09:22] <larsu> dednick: ah I wasn't aware that deleteLater is defined as delete-in-idle. mzanetti favors that approach as well. Fine by me
[09:23] <ltinkl> larsu: I think dednick is afk
[09:23] <mzanetti> I think dednick has an issue with IRC notifications :)
[09:24] <ltinkl> [11:15] * dednick brb. doc appt.
[09:24] <mzanetti> ah ok
[09:24] <ltinkl> this time not :)
[09:24] <larsu> meh, I'm commenting on the mr as well
[09:24] <larsu> didn't know you could force queued connections
[09:24] <larsu> that's pretty neat
[09:25] <ltinkl> larsu: pretty much identical to the first solution
[09:25] <larsu> ltinkl: no, because it fixes it for every user of qgsettings as well
[09:25] <larsu> the first solution was qml-only
[09:25] <mzanetti> right. yeah, +1 for doing it one level down
[09:25] <ltinkl> right, this is the C++ iface
[09:26] <larsu> ltinkl: people use that as well somewhere
[09:26] <larsu> dunno where, but I remember people asking for it early on
[09:26]  * larsu had planned a qml-only library before
[09:26] <ltinkl> didn't know that, the project says "qml bindings" ;)
[09:26] <mzanetti> yeah... launcher's model uses it in c++, just one example
[09:26] <mzanetti> also in QtMir
[09:26] <larsu> now it might stop leaking memory *cough*
[09:27] <mzanetti> haha
[09:27]  * larsu hopes it's not actually doing that
[09:28] <larsu> mzanetti, ltinkl: speaking of qt, do you know what could possibly be the cause for this library to need the QObjectPrivate() symbol? pad.lv/1426335
[09:29] <mzanetti> need to dig the code
[09:30] <mzanetti> now that's odd... grepping through it, it only gives results in the binary, not in the code
[09:30] <larsu> ya
[09:30] <larsu> might be in one of those macros
[09:31] <mzanetti> ltinkl, can you have a look please? I need to jump to a meeting
[09:31] <mzanetti> otherwise I can do in half an hour
[09:31] <larsu> no worries, just thought this might be something you stumbled onto before
[09:33] <ltinkl> mzanetti: sure
[10:00] <dednick> mzanetti: i have a problem with noticing IRC notifications ;)
[10:00] <mzanetti> :)
[10:00] <dednick> i think i need a forhorn
[10:00] <mzanetti> lol
[10:00] <dednick> foghorn
[10:00] <mzanetti> or a vuvuzela
[10:01] <dednick> haha. good idea. unfortunately i normally have laptop sound muted so might not help
[10:06] <mzanetti> you could always use a USB rocket launcher to shoot you on IRC notifications
[10:06] <ltinkl> or a red alarm LED sitting on your laptop's lid
[10:07] <mzanetti> led is not intrusive enough
[10:07] <ltinkl> ye or some effect that will start shaking all the windows
[10:07] <ltinkl> wobbly on steroids
[10:09] <dednick> ouch. the foghorn is quite annoying.
[10:12] <ltinkl> larsu, dednick: review updated, I guess we'll also have to rollback the descriptions now :)
[10:13] <larsu> and I found that symbol problem
[10:13] <dednick> ltinkl: tests still work?
[10:13] <larsu> qqmlpropertymap dereferences a QObjectPrivate in its protected constructor
[10:13] <larsu> I don't even know what that is public?!
[10:14] <larsu> I could not use that protected constructor, but the docs explicitly say to do so
[10:16] <larsu> ah, that doesn't work indeed (tests fail because the type isn't registered correctly)
[10:30] <ltinkl> dednick: yup
[10:31] <dednick> ltinkl: ok. if you're ready can you mark as "ready for review" ?
[10:32] <ltinkl> dednick: ah right
[10:37] <dednick> larsu: is g_settings_set_value synchornous?
[10:38] <dednick> i'm concerned that set + get in same mainloop cycle won't work anymore.
[10:38] <dednick> (if it did before)
[10:39] <larsu> dednick: mh? this is about change events, no?
[10:39] <dednick> larsu: the qml componnent for gsettings updates the internal value only when the change event comes in.
[10:43] <larsu> dednick: I thought qqmlpropertymap set the value from the return value of updateValue()
[10:44] <larsu> dednick: the change event always comes in later, because _set_value() is async (and it might not even come at all for the gsettings object that originated the change)
[10:45] <dednick> larsu: possible. ok, it's fine in that case.
[10:46] <dednick> +1
[10:46] <dednick> ltinkl: you confirmed the deleteLater is being effected with the queued invoking?
[10:47] <dednick> perhaps we should add a unit test for it.
[10:47] <larsu> dednick: I think we have a test that sets/gets during the same iteration
[10:47] <larsu> at least i hope so... :)
[10:47] <ltinkl> yup, there is one
[10:47] <ltinkl> function test_changed()
[10:48] <ltinkl> and test_write()
[10:48] <dednick> ltinkl: how about a test for the delete later?
[10:48] <ltinkl> dednick: using the loader+component reproducer?
[10:48] <dednick> or "posted events" even
[10:49] <ltinkl> dednick: this one http://paste.ubuntu.com/11494214/
[10:50] <dednick> ltinkl: as long as it uses deleteLater in the loader. Not sure the garbage collection for qml is entirely reliable.
[10:51] <larsu> it does
[10:51] <larsu> (for me *cough*)
[10:52] <dednick> :) might be better as a Qt C++ test
[10:52] <ltinkl> ye
[12:56] <ltinkl> larsu, dednick: added the requested C++ testcase for the MP
[12:57] <larsu> thanks, will have a look after lunch
[12:58] <dednick> ltinkl: ta
[12:59] <dednick> ltinkl: can you change the file name? test2.cpp isn't very descriptive! :)
[12:59] <dednick> test_gsettings or something
[13:00] <ltinkl> dednick: well the qml test is called test.cpp so... :)
[13:08] <dednick> ic. do you need the other pro file?
[13:08] <dednick> ltinkl: ?
[13:09] <ltinkl> dednick: umm, I guess so; it's a different target
[13:09] <ltinkl> dednick: QML vs. C++ testcase
[13:16] <dednick> ltinkl: ok. can you rename the target and testfile to cpptests at least?
[13:17] <ltinkl> dednick: ok
[13:39] <ltinkl> dednick: done
[13:41] <MacSlow> yes... yes... yes...
[13:41]  * MacSlow does _the_ dance
[13:41] <MacSlow> ...and wonders how he can avoid having to dring alcohol
[13:42] <MacSlow> dandrader|afk, we have to do the dance I guess :)
[13:43] <kgunn> ummm, MacSlow i thot the bet was before the end of sprint :)
[13:44] <kgunn> altho...you could blame mir guys for sabotage :-P
[13:44] <MacSlow> kgunn, technically yes... thanks for reminding me :)
[13:44] <MacSlow> kgunn, nah... they were just worried about my health ;)
[13:47] <kgunn> brb
[13:54] <dednick> ltinkl: approved
[13:57] <ltinkl> dednick: ty
[14:01] <dandrader> MacSlow, what? it has landed?
[14:01] <MacSlow> dandrader, well... approved at least... not fully landed yet... still I feel like funky-dancing :)
[14:02] <MacSlow> dandrader, tutorial available here https://www.youtube.com/watch?v=Zdz88MBWomo
[14:03] <dandrader> :)
[14:46] <josharenson> So re yesterday: what is the correct way to generate  a .qmltypes file using qmlplugindump... I keep getting an error
[15:09] <dandrader> It's been ages since I last used qmlplugindump. I think dednick used it recently
[15:20] <dednick> josharenson: you should just be able to call make qmltypes
[15:21] <dednick> if you're using unity8 i mean
[15:21] <dednick> it updates everything
[15:22] <dednick> josharenson: otherwise, take a look at the unity8/cmake/modules/QmlPlugins.cmake file for the correct usage.
[17:00] <popey> kgunn: is there a list of video drivers that unity8/mir supports? (specifically I am using https://wiki.ubuntu.com/Unity8inLXC )
[17:01] <kgunn> popey: so you can think of unity8/mir running on any android driver set and any mesa driver set
[17:01] <popey> nouveau?
[17:02] <kgunn> popey: in theory yes
[17:02] <popey> :)
[17:02] <kgunn> popey: well, it does work, but we also hear alot about a variety of bugs that come and go
[17:03] <kgunn> as nouveau isn't really backed by nvidia.....the result is kinda just that
[17:03] <popey> ok, just tried and it doesn't work at all, drops back to a login screen
[17:03] <popey> oh, no, it froze
[17:04] <kgunn> popey: so is this unity8 desktop session ?
[17:04] <popey> yes
[17:04]  * balloons listens
[17:04] <kgunn> before doing that, you could just install mir demos, and do the vt dance just to see if the mir+nouveau is ok
[17:04] <popey> the vt dance?
[17:04] <popey> sorry, I'm new to this
[17:05] <kgunn> popey: under "running mir natively" http://unity.ubuntu.com/mir/using_mir_on_pc.html
[17:05] <popey> ok
[17:05] <kgunn> might be better to pop over to #ubuntu-mir also
[17:06] <popey> ok
[17:09] <balloons> kgunn, ohh so someone is still using unity.ubuntu.com.. interesting
[17:10] <kgunn> balloons: only b/c someone helped with some automagic to upload our .md files to that....
[17:15] <balloons> probably an old CI job
[17:15] <balloons> good to know however