Activities appear to time out, then reappear on donut

[jfuhrer]

OFW: Q2C18 Build: 488

This has happened to me with Web in particular, although other activities have done it as well (Journal does it frequently upon startup). An activity will spend a long time pulsing on the donut while trying to open, then drop off the donut, making it seem as though it has timed out. However, the activity will later start up and then add itself back to the donut. It's better than the activity just timing out, I guess, but when the user thinks the activity has actually timed out and then tries opening the activity again, he'll end up with two copies opening at the same time, which slows down the system a lot.

[marco]

How much time later does it start it up? (I don't need secs, just a vague idea...)

[jfuhrer]

Usually a little after I've decided to open the activity again (though the two aren't related)...10-15 seconds is my guess.

[marco]

So my guess is that the activity is taking too long to startup, around 40 secs. I'm not sure why that's the case, it would be good to keep an eye on cpu usage when this happen.

Anyway for the actual bug, I think we should increase the dbus timeout when launching activities, 25 secs is too short. This dbus-python bug needs to be fixed to make that possible: https://bugs.freedesktop.org/show_bug.cgi?id=11489

[marco]

Reassigning to smcv. We need the timeout bug fixed and (I guess) a release.

[smcv]

Replying to marco:

We need the timeout bug fixed and (I guess) a release.

Fixed in git; I'll release 0.82.1 once I've checked whether there are any other bugs that could do with an immediate fix.

[marco]

I need dbus 0.82.1 in the build...

[jfuhrer]

This isn't happening anymore so far as I can tell.