Apps sometimes get stuck on splashscreen on the first run after upgrade
Bug #1585127 reported by
Andrea Bernabei
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| qtmir (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| unity8 (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Krillin, rc-proposed, r340
It happened to me with Telegram last evening, but after discussing a bit with other people, it seems I am not the only one to have experience this (even with other apps).
Steps to reproduce:
1) Update an application using System settings
2) As soon as it is updated, go to dash and tap on the application icon to run it
3) If the bug is reproduced, the app will now be stuck on the splashscreen
Run the app a 2nd time to get it working again.
Logs from telegram (the run at 21:40 is the failing one, the run at 22:00 is successful)
https:/
Logs from unity8
http://
syslog has rotated already (due to the high frequency spam on krillin) so I don't have that anymore
| description: | updated |
Revision history for this message
| Gerry Boland (gerboland) wrote | #1 |
To post a comment you must log in.
<davmor2> faenil: well that used to be the case and then the appscope was updated to auto refresh but still takes a little while to do that so the the blue bouncing bar was at the bottom when you tried to open it initially it might of still been updating the appscope which would mean you were using the old .desktop file for app which tends to lead to a spinner and eventually app closure then launching again would of given it
time to complete
<faenil> davmor2: it is a possibility, sure. If it takes that long to update the scope
<davmor2> faenil: it takes as long as it takes to refresh a scope, move to the apps scope pull down to refresh and wait for the blue bouncer to finish that will give you an idea when there are no changes