[09:22] <tsdgeos> alf_: are you sure it's not mir leakign those fd's?
[09:22] <tsdgeos> action_queue.cpp creates an eventfd that i don't immediately see being closed
[09:22] <tsdgeos> same for threaded_dispatcher.cpp
[09:23] <alf_> tsdgeos: not 100%, but I ran similar tests with a pure mir server and clients and there were no such leaks
[09:25] <alf_> tsdgeos: @action_queue,threaded_dispatcher the fds are stored in a mir::Fd object which closes the fd on destruction
[09:27] <tsdgeos> k
[09:33] <ktatar156> Hello
[09:33] <ktatar156> According to https://lists.launchpad.net/ubuntu-phone/msg15527.html
[09:34] <ktatar156> could anyone help me asap? It's really important for me to get phone number that I mentioned in emails OTA-6 MX4 big problem
[09:38] <alf_> ktatar156: We are investigating what's going on, but this seems difficult to reproduce.
[09:38] <ktatar156> Ok, working again, after ~20 shutting off and on or restarting.
[09:38] <ktatar156> Is there any information that I can provide?
[09:39] <alf_> ktatar156: Some questions that would be helpful to answer: 1. when touch stops working, can you turn the screen on and off with the power button?
[09:39] <ktatar156> Yes
[09:40] <alf_> ktatar156: 2. When this happens, did you received any messages or other notifications just before?
[09:44] <ktatar156> Yes
[09:44] <ktatar156> But
[09:44] <ktatar156> after call I put my phone into pocket. Checked it after few minutes. Try to unblock phone (entered 3 digits) and after that it stopped working
[09:45] <ktatar156> WiFi off, BT off, GPS on all the time, mobile data off
[09:47] <ktatar156> F###, Again. I had conversation 2 minutes ago
[09:47] <ktatar156> and touch is blocked again
[09:49] <ktatar156> Because It happens so many times, when I will go back into home, I will record video with that and show as many information as can
[09:52] <guest42315> ktatar156, if you take a screenshot of Apps Scope (volume up + down) does the UI freezes for like 5-6 seconds?
[09:53] <ogra_> alf_, there are a lot more input probs on arale ... not as bad as the above, but i often have it that an app doesnt take input at all anymore and it starts working again after i minimally swiped in the spread from the right ... and then there is bug 1494770
[09:53] <ogra_> alf_, the one big difference on arale is the home button and the code to handle it ... i wonder if that causes Mir or unity input issues here
[09:57] <guest42315> ogra_, something weird happened to me yesterday, opened telegram and i got the spinning circle (but not spinning) and the UI froze. i thought it's apport acting silly so i let it finish for 15 minutes. in the first 5 minutes the home button led responded to touch, and i could feel the vibrations when touching the screen with UI still frozen. after 5 minutes the touch input stoped working and i finally rebooted the phone after 15 minutes
[09:58] <guest42315> mx4 stable
[09:59] <ogra_> guest42315, did you try other UI elements (expanding the panel or right swipe) ?
[09:59]  * guest42315 aw-food
[09:59] <guest42315> ogra_,  yes, nothing worked
[09:59] <guest42315> brb
[09:59] <guest42315> food :P
[09:59] <ogra_> enjoy
[10:04] <ktatar156> guest42315, yes.
[10:06] <guest42315> ogra_,  thanks :D grabbed some milk and cookies
[10:08] <guest42315> ktatar156, can you please confirm/mark as it also affects you here https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494480 ?
[10:27] <ktatar156> alf_ do you need another information?
[10:28] <alf_> ktatar156: no, that's enough for now, thanks. A video showing the problem would be helpful if you can get it and attach it to the bug.
[13:40] <desrt> RAOF: don't suppose you're still awake :)
[14:03] <desrt> so... i got this problem from mir
[14:03] <desrt> terminate called after throwing an instance of 'std::out_of_range' what():  _Map_base::at
[14:03] <desrt> Aborted
[14:04] <desrt> and the backtrace is pretty much useless... the abort is on a thread and all i see is pthread calling libstdc++ code which is directly calling the throw/abort stuff
[14:04] <desrt> probably because something nested threw the exception....
[14:04] <desrt> and it got caught by the threading code and aborted from there
[14:04] <desrt> any help?
[14:06] <desrt> ahh... hello gdb "catch throw"