[06:32] <anes>  I got error in package creation as : dpkg-source: error: source package format '3.0 (quit)' is not supported: Can't locate Dpkg/Source/Package/V3/Quit.pm in @INC (you may need to install the Dpkg::Source::Package::V3::Quit module)
[06:32] <anes> How it can fix? please advise
[07:00] <anes> my exact error in deb creation is : debian/rules:6: *** missing separator.  Stop. dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 debuild: fatal error at line 1374: dpkg-buildpackage -rfakeroot -D -us -uc failed
[09:49] <liuxg> does anyone know how to detect the presence of the mouse/touchpad/touchscreen/keyboard? is there any API for the purpose? thanks
[09:50] <zsombi> liuxg: there is an API backported from Qt 5.6 but yet doesn't have any Mir backend
[09:51] <liuxg> zsombi, oh, I have seen that it works for the convergence story. I thought there was an open API for it.
[09:53] <zsombi> liuxg: the API is open, I didn't say that
[09:55] <liuxg> zsombi, alright. I think it is useful for the developers.
[09:55] <zsombi> liuxg: sure, it will be. It already works on X but nothing yet for Mir
[09:56] <jgdx> zsombi, how is the backAction disabled now when Page.head.backAction is deprecated?
[09:56] <liuxg> zsombi, that sounds great!
[09:56] <zsombi> jgdx: you have the same thing in the PageHeader :)
[09:57] <jgdx> zsombi, so Page.header.leadingActionBar something?
[09:57] <jgdx> not very keen on replacing the mainview header
[09:57] <kalikiana> liuxg: depending on what you need, if you need something now, detecting a touchscreen is already possible using QTouchDevice::devices() in C++, but of course it doesn't tell you if a keyboard exists
[09:58] <zsombi> jgdx: it doesn't replavce the mainview header. if your app mixes the main header and the individual page headers, you'll be in trouble
[09:58] <liuxg> kalikiana, what does it really tell?
[09:58] <zsombi> jgdx: t1mp may be more helpful on this
[09:59] <liuxg> zsombi, I will try to play with the API. thanks
[09:59] <jgdx> zsombi, okay
[09:59] <t1mp> jgdx: the default value for Page.header.leadingActionBar.actions is navigationActions, which can contain the back button
[10:00] <t1mp> jgdx: so if you set any other value for leadingActionBar.actions (may be an empty list if you don't want actions on the left), then the back action is gone
[10:01] <kalikiana> liuxg: For the keyboard you need the new InputDeviceModel API. I'd be interested to hear how it goes if you're trying it out on X11
[10:02] <liuxg> kalikiana, which lib does belong to?
[10:04] <kalikiana> liuxg: qml-module-qtsysteminfo
[10:06] <liuxg> kalikiana, on my 15.04 mx4 image, can I try it?
[10:06] <kalikiana> liuxg: See here for an example on how to use it https://codereview.qt-project.org/#/c/101049/23/examples/systeminfo/qml-inputinfo/qml-inputinfo.qml
[10:06] <kalikiana> liuxg: X11 only right now
[10:06] <kalikiana> because the Mir backend is not ready
[10:06] <kalikiana> You need a Vivid+Overlay or Xenial on X11
[10:07] <liuxg> kalikiana, ok. thanks! then I wait for its support on Mir
[10:07] <jgdx> t1mp, the default header is null, no?
[10:08] <liuxg> kalikiana, by the way, do you know if there any way to capture the hardware keys like the volume keys　in QML?
[10:08] <t1mp> jgdx: yes. By default Page.header is null, but when it is null, the "old" application header is activated.
[10:09] <t1mp> jgdx: I wrote an introduction to the new header here https://developer.ubuntu.com/en/blog/2016/02/24/pageheader-tutorial/
[10:10] <kalikiana> liuxg: I don't know - Keys.volumeUpPressed would be the API if apps are allowed to do that
[10:12] <jgdx> t1mp, great writeup, it all makes sense now.
[10:13] <t1mp> jgdx: good to hear :) thanks!
[15:13] <balloons> argh.. popey, I spent yesterday sidelined trying to get reminders to build again. Today now I see docviewer isn't building anymore.. what gives :-(
[15:13] <popey> wat
[15:14] <popey>  file COPY cannot find
[15:14] <popey>   "/var/lib/jenkins/slaves/jenkins-slave-0/workspace/docviewer-app-ci/build_dir/upstream-libs".
[15:14] <popey> also, bzr not found
[15:15] <popey> https://core-apps-jenkins.ubuntu.com/job/docviewer-app-ci/234/console
[15:15] <balloons> yea.. crazy
[15:15] <balloons> seeking as it just checked out the code and said it's installed
[15:15] <balloons> I think it's python related weirdness
[15:16] <balloons> but yesterday reminders suddenly wouldn't build because none of it's many depends were installed, and they wouldn't install
[16:16] <ahayzen> t1mp, o/ i reported bug 1554897 last night, could you take a look. It is the one with the white flicker on startup for an app with a dark background
[16:16] <ahayzen> (with a mini-app, you can see it flicker *very* quickly at startup)
[17:09] <t1mp> ahayzen: thanks for reporting
[17:09] <t1mp> ahayzen: did you happen to try it on a desktop/laptop too?
[17:10] <ahayzen> t1mp, not yet, i cannot test the music-app on desktop/laptop ... i could try the mini-app though..although i fear it'll be *so* quick you won't be able to see it
[17:11] <ahayzen> t1mp, and i'd have to somehow get the branch of the UITK from silo050 ?
[17:13] <t1mp> ahayzen: i think it is this one https://code.launchpad.net/~bzoltan/ubuntu-ui-toolkit/OTA10-landing-2016-01-20
[17:13] <ahayzen> ok i'll try and see
[17:13] <t1mp> cool
[17:13] <t1mp> I think the bug will exist in lp:ubuntu-ui-toolkit/staging too
[17:23] <ahayzen> t1mp, with that branch you can see the flicker probably 1/2 times, so yeah it does happen on the laptop
[17:25] <t1mp> ahayzen: okay, that makes debugging easier for me :) thanks for checking that
[17:25] <ahayzen> t1mp, if you are on Xenial, you can probably run the Music app as well, which will be super visible
[17:25] <ahayzen> t1mp, or if you can somehow slow the startup of the mini-app, like create some really slow JS that may help i guess
[17:26] <t1mp> ahayzen: okay. I am on xenial, so I can give it a try
[17:26] <t1mp> probably not anymore today though
[17:26] <ahayzen> yeah, you'd have to have ms2 setup etc, so may just be worth trying the mini-app first
[17:56] <Landgraf> Hi guys. Are there any plans in the near future to make a standard browser can freely select text? Now only one word can be identified. It is very difficult to use.
[18:05] <t1mp> oSoMoN: ^
[18:08] <Landgraf> there is always so quiet?
[18:18] <t1mp> no, not always.
[18:57] <oSoMoN> darn, he left before I could answer
[18:58] <oSoMoN> for anyone interested in text selection in the browser: it’s in silo 27, expected to land tomorrow, in time for OTA 10
[19:29] <pmcgowan> oSoMoN, yay, did you see the bug mterry entered on the long press for copy/paste
[19:37] <bretth> Hi all, I'm having a problem with loading images in QML, and I can't seem to find an answer in AskUbuntu or any QML forums.  I use the 'source' attribute to name the image, but a "QML QQuickImage: Cannot open" error appears.  I've tried naming the image with a relative path, an absolute path, and a QRC file, but the same error appears.  What do I need to do?
[19:47] <pmcgowan> artmello,or renatu  maybe you can help
[19:49] <artmello> bretth: hi, could you please upload the code you are trying to use (or at least this part specific) somewhere public?
[19:50] <dobey> bretth: i think you need to use full path with file:// prefix for local images perhaps
[19:53] <bretth> Here is the code and the list of things I've tried using:  http://pastebin.com/TBygjVAP
[19:56] <artmello> bretth: this sample code http://paste.ubuntu.com/15336920/ works, the file in case is a sample photo that I took with my device
[20:00] <bretth> So file:// isn't necessary then?  To be clear, header.png is a premade graphic to be included in the click package.
[20:01] <artmello> no, it is not necessary
[20:01] <artmello> bretth: maybe the current path you are running your app is not what you are expecting and so graphics or ../graphics is not mapping to the correct file
[20:02] <artmello> bretth: try using full path just to test
[20:02] <bretth> OK, I'll try it out
[20:03] <artmello> bretth: i need to be away for a while, but will be back later, let me know if it worked to you
[20:03] <bretth> Yep, thank you for the help
[20:03] <artmello> bretth: np
[22:03] <bretth> artmello:  Using the full path worked, and made me realize the relative path was actually a few directories up from where I thought it was.  Thank you again for the help.
[22:36] <artmello> bretth: cool :)