[01:31] <liuxg> does anyone know how to capture a screenshot from M10 device?
[01:38] <ogra_> Press both volume keys
[01:43] <liuxg> ogra_, thanks. how about  phablet-screenshot, it is not working.
[08:52] <t1mp> mardy: I read the code you attached to https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1572525
[08:52] <ubot5`> Launchpad bug 1572525 in ubuntu-ui-toolkit (Ubuntu) "[regression] Double header height is set as flickable topMargin" [High,In progress]
[08:52] <t1mp> mardy: the solution can work (I haven't tested it yet). But it still leaves the question what we want the behavior to be
[08:53] <t1mp> and in the case of your app, perhaps we should lock the header. Did you manage to talk to a designer about it?
[08:54] <t1mp> mardy: I have seen some designs for animations when switching between "sections" in the header. They do something similar, so I'll talk to the designers to clear up how that would work together with the header
[09:27] <mardy> t1mp: hi! Sorry, didn't hear the pings
[09:38] <mardy> t1mp: the thing I disagree about, is the order of how to proceed: first, I think we should try to fix the bugs we have, without changing behaviour; then *if* we have a solid reason to change behaviour, we do that
[09:38] <t1mp> mardy: we considered the old behavior to be a bug, because it ignores the existing topMargin
[09:39] <mardy> t1mp: yes, because you developed this component so you know about its drawbacks; but I would argue that other developers won't notice it (and so far, they didn't)
[09:40] <mardy> t1mp: noone uses that topMargin property :-)
[09:40] <t1mp> nobody could because it was broken
[09:41] <mardy> t1mp: true, but nobody reported it...
[09:41] <t1mp> mardy: for Ubuntu.Components 2.0 we are considering the Header not to touch the margins at all, so then the app developer would always have to add topMargin: header.height explicitly in the code
[09:41] <t1mp> just fyi :)
[09:41] <t1mp> the disadvantage, of course, is that maybe this will have to be done for each Flickable.
[09:42] <t1mp> mardy: if nobody reports it does that mean we should leave it "broken"?
[09:43] <mardy> t1mp: why not add a property to the header? ("bindToFlickable: true" or something like that)
[09:44] <mardy> t1mp: I think so... it's documented to be like this, and if you don't like the word "broken" you can say that it's a current limitation :-)
[09:47] <t1mp> adding properties to components is possible, but we like to keep the API basic, so as few properties as needed, because adding that property means extra maintenance (of the property and two different behaviors), and less clean API
[09:47] <t1mp> and UITK 1.3 is still considered under development, so if we have behavior that we think is a "current limitation" ;) then we can fix it
[09:49] <t1mp> zsombi: stop me if you think I am speaking nonsense :)
[09:53] <mardy> t1mp: well, AFAICR noone told me that 1.3 is under development
[09:54] <mardy> t1mp: here it's listed as current: https://developer.ubuntu.com/api/apps/qml/
[10:00] <t1mp> mardy: well the PageHeader was introduced quite recently, see https://developer.ubuntu.com/en/blog/2016/02/01/ui-toolkit-ota9/ and https://developer.ubuntu.com/en/blog/2016/02/24/pageheader-tutorial/
[10:01] <t1mp> let me see if I can find the blog post about the UITK versions
[10:01] <t1mp> the API docs don't always show the correct information w.r.t. stable/in-development versions as far as I know
[10:07] <davidcalle> t1mp: this should be fixed afaik
[10:08] <davidcalle> t1mp: if you see a mistake there, please keep me updated :)
[10:09] <t1mp> davidcalle: ah, right. :)
[10:09] <t1mp> maybe what we need is to add a description of our policy, to make clear what is stable and what is under development
[10:14] <davidcalle> t1mp: indeed. In any case, if there is a change needed, we have a way to quickly change what's tagged as current and development.
[10:15]  * davidcalle -> lunch
[10:19] <kalikiana> mardy: Current means that it's in stable images. That doesn't contradict the API changing. And UITK isn't the only one affected.
[14:17] <JeanLuc__> hi, has anyone any idea why my gtk-app does not have a shadow around the window when running in 16.04? Just received this bug report and have no idea why this is happening: https://github.com/jangernert/FeedReader/issues/85
[22:02] <Orphis> Hey, anyone here? I'm from Spotify, just upgraded to 16.04 and the sound on my HTPC is all broken with kernel 4.4. Using 4.2 from wily is alright. I'm worried that users might have similar issues when using a similar setup
[22:03] <Orphis> So, is anyone aware of sound issues on 16.04 with hda-intel audio and various popular apps like Spotify, Chrome or Kodi?
[22:28] <JanC> Orphis: this channel is for Ubuntu (Touch) app development
[22:28] <JanC> maybe search on launchpad to see if there are any bugs about that
[22:29] <Orphis> This channel is read by actual Ubuntu engineers and in the past, it's the only way I could reach them!
[22:29] <popey> Orphis: hello
[22:29] <Orphis> popey: Hello!
[22:29] <popey> Orphis: interesting. I use spotify with 16.04 on intel with 4.4
[22:29] <JanC> and there should be developers/engineers in more appropriate channels too  :)
[22:30] <popey> the only reason engineers aren't about is because it's release day and ~midnight in europe
[22:30] <Orphis> JanC: Well the "customer" support in #ubuntu is full of random people having issues, some a bit more knowledgeable but it's rare to have a proper fix
[22:30] <popey> Orphis: how is it broken?
[22:31] <popey> other audio apps work but spotify doesn't?
[22:31] <Orphis> popey: I cannot get any sound at all through Pulseaudio using hda-intel and hdmi output. Default configuration. It used to work with 4.2 and doesn't with 4.4
[22:31] <Orphis> I confirm the same packages work when I use older kernel
[22:31] <Orphis> Kodi doesn't work either
[22:31] <popey> ah, I'm not doing hdmi audio here
[22:31] <Orphis> I can fiddle in vlc and get audio if I point to alsa and not pulse
[22:32] <Orphis> Chrome doesn't work
[22:32] <JanC> Orphis: there is also -devel and -desktop and -kernel etc.  :)
[22:32] <JanC> is pulseaudio running?
[22:32] <Orphis> I'm worried that users complain that Spotify is failing
[22:32] <Orphis> Yes, it is
[22:32] <popey> ok, can you file a bug - "ubuntu-bug linux" and ping me the bug number and I'll speak to someone tomorrow
[22:33] <popey> put in the bug which 4.2 kernel and 4.4 kernel you tried
[22:33] <Orphis> popey: Great, thanks. I'm available for debugging the issue if needed
[22:33] <popey> oh, and you've been in to the mixer and fiddled?
[22:33] <JanC> and I assume you also checked all the volumes
[22:34] <popey> like system settings -> audio and chosen output and made sure you can play a test sound over hdmi?
[22:35] <Orphis> popey: Yes, nothing is muted. I can play sounds in the "test sound" panel, but if I start any other app, then it stops working
[22:35] <popey> how odd
[22:35] <popey> I'm gonna blame intel right off the bat :)
[22:36] <popey> (I kid)
[22:36] <Orphis> Also, fun bug, it doesn't play the "front" part of "front left/right" the first time I click on the button
[22:36] <Orphis> As if i takes a second to initialize / log the sound
[22:36] <popey> Orphis: https://bugzilla.redhat.com/show_bug.cgi?id=1313434
[22:36] <ubot5`> bugzilla.redhat.com bug 1313434 in kernel "No audio with kernel 4.4" [High,New]
[22:36] <popey> worth a look
[22:38] <JanC> did they change how ALSA represents the audio device?
[22:39] <JanC> IIRC there were some changes with how it represents surround that can confuse PulseAudio?
[22:39] <Orphis> Interesting. Looking into that br
[22:39] <JanC> remember reading something about that on the PA mailing list some time ago
[22:40] <Orphis> popey: So I should recompile my kernel with the option enabled?
[22:41] <Orphis> That's going to be a fun one
[22:42] <popey> I don't know
[22:42] <popey> first I've heard of it is you saying it and a quick google
[22:42] <Orphis> But it could definitely be related
[22:49] <Orphis> popey: So the option seems to have been compiled in
[22:52] <popey> Orphis: ok, sorry, I don't know more. I'd file a bug.
[22:54] <Orphis> popey: It's quite late over here, I'll do that tomorrow
[23:08] <popey> Orphis: kk
[23:09] <Orphis> Sure!