Update of today screen messes up scopes layout.

Have not rebooted phone for a while. Still can reproduce this problem. May try to help in collecting more info.

Thanks Alexey!

If possible can you attach the following:
/home/phablet/.cache/upstart/unity8-dash.log
/home/phablet/.cache/upstart/unity8.log
/home/phablet/.cache/upstart/scope-registry.log

Given that step02.png shows the scope header near the bottom of the screen, I think this is a unity8* issue, so I am adding tasks.

(not sure if it is unity8 source pkg, unity-scopes-shell...)

Alexey, Do you have any .crash files in /var/crash/ ? If so, please attach. Thanks.

Nope, no sign of .crash files.

Similar bug from this morning: bug #1546472

Status changed to 'Confirmed' because the bug affects multiple users.

Saviq: The difference is that Alexey is using OTA9 where we know the bug exists and bug #1546472 is using rc-proposed where it should be fixed

Alexey: If you reboot can you get https://launchpadlibrarian.net/240240439/step01.png just by pulling down the today scope to refresh?

Albert: No, after reboot refresh works OK.

On Thursday, February 18, 2016, Albert Astals Cid <
<email address hidden>> wrote:
> Alexey: If you reboot can you get
> https://launchpadlibrarian.net/240240439/step01.png just by pulling down
> the today scope to refresh?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1546733
>
> Title:
> Update of today screen messes up scopes layout.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/today-scope/+bug/1546733/+subscriptions
>

Interesting...

Pawel: Could you please provide a couple of words, why change of status to
invalid?

P.S. Maybe a good idea to always provide a short rationale for change of
status?

On Thu, Feb 18, 2016 at 1:06 PM, Pawel Stolowski <<email address hidden>
> wrote:

> ** Changed in: unity-scopes-shell (Ubuntu)
> Status: Confirmed => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1546733
>
> Title:
> Update of today screen messes up scopes layout.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/today-scope/+bug/1546733/+subscriptions
>

HI Alexey,

I am sure Pawel is asleep so I will answer for him.

He only marked it invalid against unity-scopes-shell.

It is now confirmed against unity8.

This reflects the project where we now think the issue probably exists.

Cheers

The graphical glitch becomes worse each time the "home" button on the Meizu MX4 is pressed (hardware button). For me this only occurs (so far) when there is no data connection it seems. Here are some screenshots. I think it is the same behaviour as described above, although the graphical result of the glitch looks different somewhat.

> The graphical glitch becomes worse each time the "home"
> button on the Meizu MX4 is pressed (hardware button).
> For me this only occurs (so far) when there is
> no data connection it seems.

So you can reproduce it all the time? If so could you write in clear step by step what you exactly do to get it?

@aacid Dave H also reported this issue (bug #1573996). According to him, this problem starts appearing *with a poor slow wifi connection <1.5M*. Is this info useful?

I think it's a red herring, i am hoping the fix for https://bugs.launchpad.net/today-scope/+bug/1569976 also fixes this, since it seems the effects are pretty similar.

just experienced once again, even after updating to OTA-11

+1

On Fri, Jun 3, 2016 at 3:26 AM, Anupam <email address hidden> wrote:

> just experienced once again, even after updating to OTA-11
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1546733
>
> Title:
> Update of today screen messes up scopes layout.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/today-scope/+bug/1546733/+subscriptions
>

Haven't seen this issue even for once after OTA-12

Sorry I still get have this issue on the MX4 with OTA-12 installed. My feeling is it is something to do with a slow internet connection (ours is 1.5M or less).

Thanks for checking

Regards

Dave H

Oops, I spoke too soon! This started appearing again.