taking screenshots locks the UI for 4-5seconds on Meizu MX4

[dinamic]

taking screenshots locks the UI for 4-5seconds on Meizu MX4

take a screenshot (volume up + down), count until you can use the UI again (swipe or whatever)

instant would be much better :P

[kevin gunn (kgunn72)]

could you please list what image you are currently on? stable ?
on rc-proposed no one is seeing anything like this.

[dinamic (dinamic6661)]

i'm on stable channel (r4)

[dinamic (dinamic6661)]

<ktatar156> on IRC #ubuntu-mir confirmed this bug (on mx4 ota6), so I AM NOT CRAZY! :P
http://irclogs.ubuntu.com/2015/09/15/%23ubuntu-mir.html

but since this is probably fixed on RC... it doesn't matter any more :D
can you change from incomplete to won't fix? not that i care that much.. but just because I AM NOT CRAZY! (j/k)

[dinamic (dinamic6661)]

ok, so i;m on OTA7 now. same thing, the UI freezes for 5-6 seconds

[dinamic (dinamic6661)]

now i'm on rc-proposed arale/r156 same thing... when taking a screenshot of the apps scope the UI is freezes for 5-6 seconds

[Jean-Baptiste Lallement (jibel)]

system-image-cli -i
current build number: 157
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en

I took a screenshot of the greeter and the UI completely froze and didn't resume (still frozen after 4 minutes)
The clock updated to the right time after 3 minutes then froze again.

After 6 minutes it finally took the screenshot but everything was utterly slow. for example drag down the indicator, and they partially reveal after 1 minute.

The following messages are displayed in unity8.log
void AalMediaPlayerService::play()
Failed to check if source is video: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to check if source is video: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to check if source is video: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to get current playback position: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to get current playback position: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
qtmir.applications: Application::setRequestedState - appId= "unity8-dash" requestedState= running
Failed to get current playback position: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to get current playback position: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to get current playback position: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to get current playback position: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network...

[Jean-Baptiste Lallement (jibel)]

It is likely a duplicate of bug 1508830

[dinamic (dinamic6661)]

can't reproduce this bug any more, currently on arale/rc-proposed/r186

-async

[Jean-Baptiste Lallement (jibel)]

It is still happening after a few successive screenshots on arale/rc-proposed/213. It's worst than before and the phone doesn't recover at all even after several seconds. A reboot is required to recover. media-hub.log attached.