[00:10] <hoss> apport question: I work on an OSS project (lucene) that, as part of our automated tests, kills processes to then verify data integrity.   When devs use ubuntu, this causes apport to ask about sending in a bug report (for java) ... is there any sort of ENV variable we can set on these processes to tell apport "don't freak out if this proc dies horribly" ?
[09:23] <mivoligo> I'm trying to build Terminal app but I got this error: http://paste.ubuntu.com/11707033/
[13:02] <mario__> hey....I am developing a scope and I would like to know if I can make my PreviewWidget to perform a different action from simply opening an url
[13:03] <mario__> is it possible?
[14:16] <kalikiana> mhall119: would you know where the phone manual comes from? The Manual_Aquaris_E4.5_ubuntu_EN.pdf doesn't describe how to pick up a call correctly, see Re: [Ubuntu-phone] BQ4.5 damage, first report. from yesterday
[14:16] <kalikiana> no idea where to report that
[15:40] <mhall119> kalikiana: I have no idea, have you asked PES?
[20:26] <meles_> whats the easiest way to make ubuntu-clock-app run with ubuntu-sdk?
[20:27] <nik90> meles_: just open the cmakelist file with qtcreator and then run it
[20:27] <nik90> meles_: no other extra step required
[20:30] <nik90> meles_: does it work?
[20:32] <meles_> nik90 opening yes. running not yet. I just shows me the desktop not the phone emulator.
[20:33] <nik90> meles_: any errors or warnings/
[20:33] <nik90> ?
[20:33] <nik90> meles_: wait what only shows the desktop and not the phone emulator?
[20:33] <nik90> meles_: go to the Projects Tab on the left and then add the phone emulator kit
[20:34] <nik90> which should the i386 14.10 or 15.04 kit
[20:34] <nik90> meles_: then in the run target you can choose to run it on the phone emulator
[20:35] <meles_> nik90 I did that, the error now is make: *** No rule to make target 'all'.  Stop.
[20:36] <nik90> hmm
[20:36] <nik90> meles_: can you take a screenshot and share it here..I might get a better idea
[20:38] <meles_> http://pasteboard.co/1cqVyfPx.png
[20:40] <meles_> nik90 ^
[20:41] <nik90> meles_: curious but does any other app compilation work for you?
[20:41] <nik90> meles_: also did you manually add the ubuntu-clock-app.config, .includes and .files?
[20:42] <meles_> i didn't try it yet on this machine. I had to change because on the other one I had problems with kernel 4.0 and the computer doesn*t work properly with a lower version.
[20:42] <meles_> nnik90: no i did not
[20:42] <nik90> meles_: could you try lp:podbird and check?
[20:42] <nik90> meles_: somehow I feel this isn't ubuntu-clock-app specific
[20:44] <meles_> ok i will try podbird. i was just about to get dekko
[20:44] <mzanetti> popey, hey, you about?
[20:49] <Elleo> meles_: try going to "Build -> Run CMake" and then try building again
[20:49] <Elleo> (and see if you get any errors during the cmake run)
[20:52] <nik90> meles: <Elleo> meles_: try going to "Build -> Run CMake" and then try building again
[20:52] <nik90> meles: <Elleo> (and see if you get any errors during the cmake run)
[20:53] <meles> nik90: just having issues with the qtcreator. it's stuck.
[20:53] <nik90> meles: is this ubuntu 14.04 with the SDK PPA installed?
[20:55] <meles> nik90: yes
[20:55] <nik90> hmm strange..that's the same system configuration I am using
[20:56] <meles> just a second, it's running again
[21:00] <meles> nik90: after running CMake it works now
[21:01] <nik90>  meles: podbird or clock?
[21:03] <meles> clock, but i just saw it still gives me some errors with an incompatible Qt library
[21:03] <nik90> meles: which kit version are you using and also what emulator image/channel is this?
[21:06] <nik90> somehow your sdk setup is messed up
[21:07] <meles> GCC i386-ubuntu-sdk-15.04-vivid. emulator is 0.4+15.04.20141125-0ubuntu1
[21:07] <meles> i m updating it
[21:08] <nik90> Elleo: do you know how to close a dialog from the outside? I tried PopupUtils.close(dialogComponent) but that fails
[21:08] <nik90> meles: I am not sure what is happening..you need to first confirm that this is not localized to clock app.
[21:08] <nik90> meles: if its your system I am afraid you will need to check with the sdk devs
[21:08] <Elleo> nik90: you need to call close on the dialog itself, not on the dialogComponent; when you run PopupUtils.open() it'll return the actual dialog that gets created from the component, and you can call close on that
[21:08] <meles> nik90 alright i try podbird again
[21:09] <Elleo> nik90: at least I think that's the case
[21:09] <nik90> Elleo: I am trying to show a loading dialog without a close button..the dialog should autoclose when the loading is done..so I am calling the close() function inside the refreshModel() function.
[21:10] <nik90> Elleo: will try calling close on the actual component returned by open()
[21:11] <nik90> Elleo: yup that worked..thnx.. although it closes the dialog before the freeze is actually gone..might need to search for the listview creation signal
[21:12] <Elleo> cool
[21:15] <meles> nik90 same issue with podbird: ... plugin cannot be loaded for module "Podbird": The plugin .... uses incompatible Qt library (5.41) [released]
[21:16] <nik90> meles: its your ubuntu sdk that is at fault..which version of qt do you have installed?
[21:16] <nik90> meles: do you install qt 5.4 or something?
[21:17] <nik90> meles: what I don't get is how you're running into this issue on a standard ubuntu 14.04 setup..surely u installed something that shouldn't have been ;)
[21:19] <mivoligo> I also have a problem. With Terminal app. When I try to run it from SDK to the phone I get this error: http://paste.ubuntu.com/11707033/
[21:19] <meles> probably its easier to set up the whole environment freshly in a VM
[21:20] <nik90> mivoligo: that could involve you missing a package in your chroot where you build it. Does the terminal-app contain any build readme?
[21:20] <mivoligo> nik90: let me check, I never read them anyway :P
[21:21] <meles> nik90 btw qt5.4 is not installed. i have 5.2
[21:22] <SturmFlut> It has finally happened, somebody created a Telegram webapp ("Sommergram") that sends all communication through a man-in-the-middle website located at http://julienmcjay.github.io/sommergram/
[21:22] <nik90> mivoligo: apt-get install libpam0g-dev:armhf (as mentioned in the readme ;)
[21:25] <mivoligo> nik90: I'm reading this but I don't understand where should I install it. On my phone or on my desktop?
[21:25] <nik90> mivoligo: in the chroot
[21:25] <nik90> mivoligo: Tools->Options->Ubuntu->Maintain kit chroot
[21:26] <mivoligo> nik90: got it, thanks :)
[21:27] <nik90> mivoligo: just a tip, whenever you need to install a dependency it is almost 99% always in the chroot since that is where you're building your app for various architectures like armhf, i386, amd64 etc.
[21:28] <mivoligo> nik90: thanks, I never done that before
[21:31] <daker> SturmFlut: maybe contact The review team or beuno
[21:47] <mivoligo> nik90: do you maybe know how can I clear the clipboard on the phone?
[21:48] <meles> nik90 I m setting up a VM now. Thanks for your great help!
[21:48] <nik90> mivoligo: no..within the app I think there was a SDK function afaik
[21:48] <nik90> meles: no worries, feel free to ping me about clock app. I am the maintainer of it.
[21:52] <nik90> mivoligo: it seems I was wrong
[21:52] <nik90> mivoligo: the sdk provides a so called clear() function that may be used to clear the system clipboard.
[21:52] <mivoligo> nik90: how can I use it?
[21:53] <nik90> mivoligo: https://developer.ubuntu.com/api/apps/qml/sdk-14.10/Ubuntu.Components.Clipboard/
[21:53] <mivoligo> nik90: that's not what I'm looking for :)
[21:54] <mivoligo> nik90: I just want to clear it from my phone
[21:54] <nik90> mivoligo: not sure how to do it in UT...to be honest you can't even do that in Ubuntu desktop without a clipboard indicator.
[21:55] <mivoligo> nik90: ok, thanks, I'll try to reboot
[21:58] <mivoligo> BTW I'm hoping pasting selected text with mouse wheel click will be present in the Ubuntu Next desktop :)
[21:58] <mivoligo> nik90: cleared after reboot :)
[21:59] <nik90> same
[22:01] <meles> nik90 ok great to know. I was wanting to find out more about bug #1442518. I posted some informations.
[22:06] <nik90> meles: I am unable to find the fault in the underlying logic which schedules alarm when you press the switch.
[22:07] <nik90> meles: the main issue here is that testability of a patch since the conditions necessary to reproduce the bug are difficult to achieve
[22:08] <meles> nik90 doesn't the bug affect you personally?
[22:08] <nik90> meles: it does..at the moment I workaround by editing the alarm and then saving it.
[22:09] <nik90> meles: I can reproduce it..but somehow it happens only after midnight
[22:09] <nik90> I am looking into the logic hoping to find the solution
[22:11] <meles> nik90 i tried a lot today and it seemed that it always sets the alarm for the next day. But when you had the alarm activated on one day and you deactivate it again, the day after it will work as it should. so to me it seems that the date is somehow saved wrong.
[22:12] <meles> nik90: i thought that the bug might be in app/alarm/AlarmDelegate.qml around line 100
[22:13]  * nik90 looks
[22:19] <nik90> meles: I just noticed something...right now when I enabled an old alarm I had that was set to 11:00 AM..it showed as "in 1d 10h 41m" which is obviously wrong
[22:19] <nik90> meles: however it shows up correctly scheduled in the indicator
[22:20] <nik90> meles: meaning the "time to alarm" delta value is incorrect..so may be the fault function is alarmUtils.get_time_to_next_alarm)_
[22:20] <nik90> alarmUtils.get_time_to_next_alarm()
[22:21] <nik90> meles: actually ignore what I said...
[22:21] <meles> nik9: :-) ok.
[22:22] <meles> nik09 I checked the mentioned function but I couldn't find anything weired
[22:22] <nik90> meles: yeah that function is fine..I miscalculated..
[22:23] <meles> I set the time manually today. Created an alarm every two hours and changed the date till I was at the 21st. Now when I wanted to check what you said. I activated an alarm for 10:15. And it says: 7 d 9h 52 m
[22:24] <meles> its also wrong in the indicator-applet
[22:24] <nik90> yup
[22:24] <nik90> so line 103 in alarmDelegate.qml is the culprit
[22:24] <nik90> I am trying out a different logic atm..lets see if that works
[22:28] <nik90> nope that failed
[22:29] <meles> nik90 is that good or bad
[22:29] <nik90> meles: well bad since I don't have a solution to the bug
[22:30] <nik90> too tired now..I will try to take a closer look tomorrow
[22:32] <meles> nik90 ok just thought the same, but one last suggestione even though my mind is not to clear anymore
[22:32] <nik90> shhot
[22:32] <nik90> shoot*
[22:33] <meles> nik90 if alarmData.date < new Date() then it sets it to tomorrow
[22:33] <meles> which is past midnight, 1d Xh
[22:34] <meles> if I set the alarm yesterday this is true and it will shedule the alarm for tomorrow
[22:35] <nik90> well it will schedule the alarm for tomorrow only if alarmData.date.getTime() <= currentTime.getTime()
[22:35] <nik90> otherwise it should set it for today
[22:36] <nik90> the alarmData.date < new Date() is only there to check if this is an alarm from the past...since alarm created to ring in another 2 days don't need all this logic and can be enabled directly
[22:36] <meles> just stumbled about this part
[22:37] <meles> getTime just returns the clocktime?!
[22:38] <nik90> I would expect so
[22:38] <nik90> you think that's at fault?
[22:38] <meles> could be. If it returns a datetime.
[22:39] <nik90> http://www.w3schools.com/jsref/jsref_gettime.asp
[22:39] <nik90> I think it returns datetime
[22:39] <meles> just checking
[22:41] <nik90> meles: may be instead of checking the time which seems to also include the date, I should specifically check the hour, minute and second alone
[22:42] <nik90> if alarm.time < new time then set it for today or tomorrow accordingly
[22:43] <meles> nik90 yes
[22:44] <nik90> meles: if I send you a click package in about 15 mins would you be able to test?
[22:44] <meles> nik90 yep! than i just go for a shower meanwhile
[22:45] <nik90> cool
[22:45] <meles> how woud you implement the test hours*3600+minutes*60*+seconds?
[22:47] <nik90> I am thinking about it now
[22:53] <nik90> meles: I did http://paste.ubuntu.com/11710946/
[22:53] <nik90> meles: does it look good to you?
[22:53] <nik90> meles: I did preliminary testing and it doesn't seem to break anything
[22:56] <meles> yes if alarmData.date.getHours() returns the hours of the day and not since 1970 or something like that
[22:57] <nik90> bah it didnt work :/
[22:57] <nik90> I manually changed the date to tomorrow and checked
[22:57] <meles> :-|
[22:59] <nik90> anyways I am off to sleep meles
[22:59] <nik90> tty later
[23:00] <meles> nik90 ok me too. maybe i get my testing environment working tomorrow.