[07:00] <dholbach> good morning
[07:20] <davidcalle> Morning
[11:23] <dubstar_04> Is anyone able to have a look at this: http://paste.ubuntu.com/11863268/ and let me know when the page disappears under the header when the keyboard pops out? I want the label to resize when the keyboard is out.
[12:34] <nnarol> Hi! I have made a small app in Python as a small present for someone, but I cannot figure out how to make it work on another computer.
[12:34] <nnarol> The target machine has Ubuntu installed, my machine has an Ubuntu-based distro called Zorin OS 9 Core.
[12:35] <nnarol> I set the permissions for the file to be allowed to be executed as a program and I made a soft link to it.
[12:35] <nnarol> I put the whole thing into a folder and compressed it into a zip file.
[12:36] <nnarol> Now the person I sent this over to reported that it just won't start.
[12:37] <nnarol> Oh yeah, first I compiled the .py file into a .pyc and made it into an executable with cx-freeze, *then* I did what I just described.
[12:37] <nnarol> Also, it worked just fine on my machine.
[13:31] <nnarol> Good bye!
[14:18] <karni> alecu: hey buddy o/ Do you know where's the thumbnailer documented?
[14:19] <karni> alecu: I'd like to know if I can also pass the output path to the thumbnailer.get_thumbnail(video, size) call
[14:19] <alecu> hi karni! let me find it.
[14:20] <karni> alecu: just found this, looking at http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/thumbnailer/vivid/files/head:/src/
[14:20] <karni> path, size, policy :(
[14:20] <alecu> karni: why do you need the path?
[14:21] <karni> alecu: for start, I have no idea where it puts the thumbnail (from the docs, I know it returns the path). am I expected to take the path and copy the file? it would be so much easier to just pass it in.
[14:22] <alecu> karni: the thumbnailer returns a path to its cache
[14:22] <alecu> karni: you should not make a copy, just point your qml component to that
[14:22] <karni> I see, okay
[14:22] <karni> alecu: question still holds - do we have this documented anywhere?
[14:23] <karni> I think it would be nice, if we had such a useful component documented
[14:23] <karni> I wasn't able to find it (my search skills may have failed)
[14:24] <alecu> karni: ah, I see the problem.
[14:25] <alecu> karni: my team has been working on a rewrite for the thumbnailer, but since it was deferred from landing in ota-5, it seems that the docs have not been deployed either.
[14:25] <karni> I see
[14:25] <karni> alecu: also, to answer your question - I needed the path mostly to fit a thumbnailer call in an external library, who's signature is (QString video, QString output, QString ffmpegPath) (ignore the last argument)
[14:26] <karni> hence, the path is given where the thumb is expected
[14:26] <alecu> karni: I expect that you'll need a copy then :-(
[14:27] <alecu> karni: but please open a bug for that: https://launchpad.net/thumbnailer
[14:27] <karni> alecu: lucky me, the output is a non const reference, and from the source I see I can simply swap out the path from the inner method (which I would patch). cool
[14:28] <karni> alecu: for the docs, or for that path use case?
[14:28] <alecu> karni: for your use case of specifying the path
[14:28] <karni> okay
[14:30] <alecu> karni: hmmm... now that I'm watching the code, I recalled that the client api has not changed for the new thumbnailer, only the backend.
[14:30] <alecu> karni: so I expect that there would be no changes on the docs. Or the lack thereof
[14:30] <karni> alecu: I simply meant lack of thereof :(
[14:30] <alecu> karni: I'll open that bug
[14:30] <karni> thanks
[14:31] <alecu> karni: thank you for pointing it out!
[14:31] <karni> sure
[14:34] <karni> alecu: https://bugs.launchpad.net/thumbnailer/+bug/1474021
[15:19] <alecu> karni: thanks! I've opened this for the missing docs: https://bugs.launchpad.net/thumbnailer/+bug/1474035
[15:20] <karni> thank you
[15:28] <rickspencer3> hey, I notice that after I run a dialog from a page, when the dialog closes, the header for the page is gone
[15:28] <rickspencer3> anyone see anything like this before?
[15:31] <karni> jhodapp: any idea what that might be? ** Media playback error:  2
[15:32] <jhodapp> karni, take a look at the media-hub log, I print out the specific error to stderr
[15:32]  * karni nods
[15:32] <jhodapp> karni, /home/phablet/.cache/upstart/media-hub.log
[16:03] <ahoneybun> are there any plans to add the option to change the icon row number? (ie current way is 3 icons across
[16:04] <ogra_> no, its four :P
[16:05] <ahoneybun> noope
[16:05] <ahoneybun> its 3 on mako
[16:06] <ogra_> 4 on arale :)
[16:06] <ogra_> get a device with a biger screen then :)
[16:06] <ogra_> *bigger
[16:06] <ahoneybun> ogra_: no options in the US
[16:06] <ogra_> works fine in the US
[16:07] <ogra_> (well, on HSPA+)
[16:07] <ahoneybun> arale?
[16:07] <ogra_> yeah
[16:07] <ahoneybun> what is that?
[16:07] <ogra_> MX4
[16:07] <ahoneybun> oh
[16:07] <ogra_> Meizu
[16:07] <ahoneybun> I did not know the codename
[16:07] <ahoneybun> I have the OPO
[16:08] <ogra_> i think the opo ubuntu images even uses 5 icons per row (because they drive the resolution a bit to hih)
[16:08] <ogra_> *high
[16:08] <ahoneybun> it does not work fully yet to be a daily driver sadly
[16:09] <ogra_> yeah
[16:09] <ahoneybun> mario is working very hard on it
[16:10] <ahoneybun> and once he gets it Sailfish will be much easier as well
[17:30] <ahayzen> zsombi, thanks for looking at those listitem issues, we have another issue in music where because we have a dark bg when you drag the trailing actions to far you get a white background instead of the dark colour, note this doesn't happen on the leading actions as that is red from the action itself. Is there anyway i can specify this overflow colour for the trailing actions? or even better should it be transparent ?
[17:53] <pmcgowan> bfiller, is there still no way to turn off or mute calendar events
[17:54] <zsombi> ahayzen: in 1.3, you could use StyleHints to configure this, however this should be taken from the style. Yet, we don't have ListItemStyle for SuruDark, so I'd file a bug against toolkit so we can get that sorted out as well.
[17:55] <bfiller> pmcgowan: don’t think so
[17:55] <ahayzen> zsombi, i don't think we are using SuruDark per say ... but should the colour of the overflow not just be transparent ?
[17:55] <ahayzen> zsombi, instead of white, then it would solve the issue
[17:56] <pmcgowan> bfiller, do you know if design covers this?
[17:56] <zsombi> ahayzen: the panel color was explicitly set to red/white, so... but if you're setting a dark color, doesn't that change the theme to SuruDark?
[17:56] <bfiller> pmcgowan: I have not seen any updated designs that cover it, but it’s possible they exist
[17:56] <bfiller> I know we’ve discussed it
[17:57] <pmcgowan> bfiller, ok might be worth a bug, its very annoying
[17:58] <ahayzen> zsombi, maybe if i write a small demo it will be clearer ;-) the actions themselves are the correct colour its when you pull too far
[17:58] <pmcgowan> bfiller, where would I file it
[17:58] <zsombi> ahayzen: ok, pls do so, and eventually a screenshot attached would also be helpful!!
[17:58] <bfiller> pmcgowan: ubuntu-system-settings and ubuntu-ux projects
[17:59] <ahayzen> zsombi, cool i'll ping them across after dinner :-)
[18:00] <zsombi> ahayzen: I'll be away in a minute, but I'll get the logs anyway, so just drop the link here, I'll check it tomorrow
[18:00] <ahayzen> zsombi, will do thanks
[18:38] <snwh> A new icon for Files: https://github.com/snwh/suru-icons/blob/master/Suru/512x512/apps/filemanager-app.png
[18:40] <snwh> there’s a merge proposal for it :)
[18:51] <akiva-thinkpad> balloons: ping
[18:51] <ahoneybun> I like the new icon snwh
[18:51] <ahoneybun> :)
[18:51] <balloons> akiva-thinkpad, hey!
[18:51] <snwh> thanks. the old one was incredible dated
[18:51] <balloons> akiva-thinkpad, been some time. Lovely to hear from you!
[18:52] <akiva-thinkpad> balloons: Is Jenkins on Vivid yet? My tests for filemanager app are failing :P
[18:53] <akiva-thinkpad> balloons: heh, thanks~
[18:53] <akiva-thinkpad> https://code.launchpad.net/~akiva/ubuntu-filemanager-app/img-thumbnail-support/+merge/264241/comments/662638
[18:54] <balloons> akiva-thinkpad, sadly it is not. Did popey explain things to you? Perhaps a mail letting everyone know what's happening might be useful
[18:55] <balloons> akiva-thinkpad, in a nutshell, there's a bug with vivid and we can't move to it. CI is working on an alternative solution for us at the moment.
[18:55] <akiva-thinkpad> I gathered from popey that this was the issue
[18:55] <akiva-thinkpad> ah okay
[18:55] <akiva-thinkpad> so just hold on for the time being?
[18:55] <balloons> akiva-thinkpad, if this needs to land, we can test and land outside of jenkins if needde
[18:55] <balloons> I don't want to hold things up
[18:56] <akiva-thinkpad> balloons: meh, not really; I just want to figure out what is wrong with my autopilot
[18:56] <balloons> sadly Alan is away; so I'm not sure what was decided for file manager. Clock for instance has tests off on jenkins in the interim
[18:56] <akiva-thinkpad> balloons: for example, the trunk in ubuntu-filemanager-app fails 10 tests, but passes on jenkins
[18:57] <balloons> akiva-thinkpad, fails locally, but passes on jenkins?
[18:57] <akiva-thinkpad> balloons: yep.
[18:58] <akiva-thinkpad> balloons: anyways, I can wait. Being a bit free from the sdk project; is there any core apps that specifically need some polish? I was thinking maybe even contributing to unity8~
[19:11] <balloons> akiva-thinkpad, did you have plans to do more to the autopilot plugin?
[19:11] <balloons> akiva-thinkpad, I was hoping to discuss some ideas with you
[19:11] <akiva-thinkpad> balloons: honestly I wanted to do some work on the core apps to get a feel as to what would be most useful for improving the autopilot plugin
[19:12] <balloons> I also filed some bugs as you some :-)
[19:12] <balloons> *saw
[19:12] <balloons> akiva-thinkpad, ahh, that makes sense too
[19:12] <akiva-thinkpad> balloons: sec, let me double check
[19:12] <akiva-thinkpad> I remember some of your bugs were from an older version that was obsolete.
[19:13] <akiva-thinkpad> ah I see
[19:13] <akiva-thinkpad> for the phone... planned feature, once I actually get a phone :P
[19:14] <akiva-thinkpad> definitely on the fence whether I should just grab a nexus 4
[19:15] <akiva-thinkpad> balloons: oh and the other bug was fixed!
[19:15] <akiva-thinkpad> I just coincidently changed the dimensions to 400x600
[19:20] <ahoneybun> in the US then akiva-thinkpad?
[19:20] <akiva-thinkpad> ahoneybun: Canada
[19:20] <ahoneybun> oh ok
[19:20] <akiva-thinkpad> eh
[19:24] <balloons> akiva-thinkpad, did you really change the resolution?
[19:24] <balloons> hehe
[19:25] <akiva-thinkpad> balloons: yep; i'll grab the diff for you
[19:26] <balloons> ahh.. the other part of that bug can't be solved just yet, unless we incorporate the script ourselves
[19:26] <balloons> that is, using a window manager during test runs. Without it, clock tests will fail
[19:26] <balloons> akiva-thinkpad, also, it's been noted proprietary drivers don't like Xephyr. Have you noticed this?
[19:27] <balloons> I need to file a bug about it, but we should fallback to Xfvb in those cases I think
[19:27] <akiva-thinkpad> I can't say. Not enough experience with this yet.
[19:28] <akiva-thinkpad> balloons: https://code.launchpad.net/~akiva/qtcreator-plugin-autopilot/fix-segfault-fix-winsize/+merge/263616
[19:29] <balloons> akiva-thinkpad, ok, let me file the bug based on the driver issue
[19:29] <balloons> do you think you could change your call to a custom script instead of autopilot3-sandbox-run?
[19:30] <akiva-thinkpad> balloons: actually one question on dimensions; I was wondering whether any of those tests will actually require greater dimensions than 320x600? If yes, I was thinking of adding some options in the runconfiguration
[19:30] <akiva-thinkpad> balloons: yessish? For the locator, it will be a bit tougher.
[19:30] <balloons> 400x600 actually. And it's a reasonable default, but an option would be nice if for some reason someone wanted to run at tablet resolution for instance
[19:30] <akiva-thinkpad> balloons: yeah okay fair enough.
[19:32] <balloons> if you could do a custom script, we could add the window management now. It's been stuck waiting on the autopilot release
[19:32] <balloons> if it's work though, it's probably not worth it.. we'll get it soon enough
[19:32] <balloons> the Xephyr / xfvb issue with non-free drivers is a bigger concern
[19:33] <akiva-thinkpad> brb, battery issues
[19:39] <akiva-thinkpad> balloons: sorry back
[19:40] <balloons> no worries akiva-thinkpad
[19:40] <akiva-thinkpad> So I added the abilities to change the dimensions to the wishlist. You want the ability to change the default script added? Anything else?
[19:41] <balloons> akiva-thinkpad, I'm thinking making a custom script instead of the ap-sandbox-run call is overkill and needless
[19:41] <balloons> I'll just be more patient and push that team to update it on their end :-)
[19:41] <akiva-thinkpad> okay will do then
[19:42] <akiva-thinkpad> balloons: I'm thinking of also placing failed autopilot tests into the issues pane, and getting them to direct to the code in question
[19:42] <akiva-thinkpad> what do you think?
[19:44] <balloons> akiva-thinkpad, mmm.. even if you output in std format, you'd also have to parse the python traceback
[19:44] <balloons> might also be a bit overkill atm
[19:44] <akiva-thinkpad> balloons: I was thinking of just grepping for the string in the python file.
[19:44] <akiva-thinkpad> balloons: one thing I do want though is a easier way to parse and identify failed tests.
[19:45] <balloons> that's fair enough. I'm also curious if you had any ideas about selecting which tests to run
[19:45] <akiva-thinkpad> I don't like the way the logs currently output the failure.
[19:45] <balloons> are you happy with the run config now?
[19:46] <akiva-thinkpad> balloons: It needs memory, and some intelligence as to which ones failed
[19:46] <akiva-thinkpad> balloons: what about you?
[19:57] <balloons> akiva-thinkpad, what do you mean memory?
[19:58] <akiva-thinkpad> balloons: uncheck a bunch of boxes, change active projects, and return
[19:58] <balloons> bug 1474108
[19:58] <akiva-thinkpad> all the boxes will be checked again.
[19:59] <balloons> akiva-thinkpad, ahh.. yes, that makes sense
[19:59] <balloons> does select all / unselect all option make sense?
[20:00] <akiva-thinkpad> balloons: yeah, should put it in there
[20:00] <akiva-thinkpad> good idea
[20:01] <balloons> also this is what I was talking about: https://bugs.launchpad.net/qtcreator-plugin-autopilot/+bug/1474108. So my thought is to run autopilot-sandbox-run without the -X in those cases
[20:01] <balloons> that will stop the window from spawning and should work on non-free systems
[20:01] <balloons> do we want to detect this automagically, or simply offer it as an option or ?
[20:01] <balloons> I don't want to get too many options !
[20:02] <akiva-thinkpad> balloons: automatically may be an issue if you update tests...
[20:03] <balloons> what do you mean update tests?
[20:04] <akiva-thinkpad> balloons: there is a refresh button that allows you to update your list of tests when you make changes to your autopilot tests in the python file.
[20:04] <balloons> akiva-thinkpad, yes, right. So why would detecting if you have non-free drivers be an issue?
[20:05] <akiva-thinkpad> oh nvm, i thought we were speaking of something else
[20:06] <akiva-thinkpad> balloons: a bit tired atm, so apologies, but from what I understand, this issue only affects nvidia users?
[20:08] <balloons> akiva-thinkpad, affects me with an amd card; if I use non-free drivers
[20:08] <balloons> so it's fair to say it's all non-free drivers
[20:08] <balloons> has to do with how Xephyr works
[20:09] <akiva-thinkpad> okay so we just need a bool to check if non free drivers are activated, and then change the command to... what?
[20:09] <akiva-thinkpad> balloons: ^
[20:10] <balloons> akiva-thinkpad, the difference in runs is with -X and without it. autopilot3-sandbox-run -X runs under Xephyr. autopilot3-sandbox-run runs under Xfvb
[20:11] <akiva-thinkpad> balloons: so then if you have those drivers, you will just have to suffer from not being able to do anything else while the tests run?
[20:11] <balloons> akiva-thinkpad, no, it will run in the background. No windows will spawn at all
[20:11] <balloons> it will be truly nested
[20:11] <balloons> you could run it on a server :-)
[20:11] <akiva-thinkpad> balloons: oh okay
[20:12] <balloons> right.. so the experience only suffers in that you can't visually see the test runs
[20:12] <akiva-thinkpad> balloons: so do you want automagically then, or just a checkbox on the run config ?
[20:12] <balloons> akiva-thinkpad, I think automagically would more or less be best. But I'm curious about how to convey that to the user
[20:13] <akiva-thinkpad> balloons: well trouble is; if they fix this, will we remember to take the patch out?
[20:13] <akiva-thinkpad> balloons: oh to convey it, we can just put it in the issues pane
[20:19] <akiva-thinkpad> Well okay then. If you file a bug for it, I'll make sure it gets in there. I'll leave it to your discretion as you would know better than I if the drivers will be fixed eventually.
[20:28] <ahayzen> balloons, o/ did anything happen about the idea of a common appdev highlight? https://lists.launchpad.net/ubuntu-phone/msg13474.html as both me and nik both thought it was a good idea as well ?
[20:35] <ahayzen> zsombi, for when your back, this is the code http://pastebin.ubuntu.com/11874253/ and the screenshot https://drive.google.com/file/d/0B3XynHVKfrvMWXM2MlJZM0pNQkE even a workaround just for the 1.2 period would be nice until we get proper theming for 1.3. Otherwise if we land these listitems it does look quite odd having this white area in the generally dark music-app
[20:35] <ahayzen> zsombi, ..can it not take the colour of the last trailing action and just continue that ?
[21:16] <balloons> ahayzen, basically we simply need to update the title to reflect the highlight. The implementation is up to everyone to implement
[21:16] <balloons> I think it's a great idea.
[21:16] <balloons> let me see if I can change the title :-p
[21:16] <balloons> akiva-thinkpad, yea, the bug won't be fixed in the drivers
[21:17] <balloons> akiva-thinkpad, so it's totally safe for us to do. It's been that way for some time now
[21:17] <balloons> akiva-thinkpad, the bug is: https://bugs.launchpad.net/qtcreator-plugin-autopilot/+bug/1474108. I'll add a comment on how to fix
[21:32] <ahayzen> balloons, hehe what highlight are you thinking? coreappdevs? appdevs ?
[21:33] <balloons> ahayzen, appdevs probably. So long as it's uniform it's fine
[21:33] <ahayzen> i'd agree
[21:33] <balloons> yea, no op powers here
[21:33] <balloons> probably should revive the thread and Alan can make the official switch when he's back
[21:34] <ahayzen> i'll poke him when he is back from his holiday/beer drinking
[21:48] <balloons> ahayzen, good plan :-)
[21:48] <ahayzen> meanwhile time to remember how to write AP tests/mocking :-)
[21:57] <ahayzen> balloons, so the old weather app replaces the database to 'mock' theweatherchannel, is it best todo that rather than trying to mock a Http requests ?