System-update notifications keep re-appearing although update already installed [released]
This morning I manually checked for updates and installed 1.0.2.5. Later today I got a notification that 1.0.2.5 was available although I had installed it already. Based on the comments it seems to have happened to others too.
Edit 8.1.2014: update notifications keep on re-appearing for many still. Checking for updates or opening store seems to clear the notification, but the root cause is not resolved.
Edit 2.2.2014: seems that update notifications erroneously appear for some even after upgrade to 1.0.3.8
EDIT: This doesn't seem to happen any more in 1.0.5.19
I saw that today today too.
arnbak ( 2013-12-28 21:49:47 +0200 )editThis is not an answer. Understand/appreciate the difference between the "Add answer" and "add comment" links! If you can, convert your post to a comment.
Milhouse ( 2013-12-28 22:10:27 +0200 )editToday I received the same notification 3 times
contratto ( 2013-12-28 22:12:12 +0200 )editWell to be fair my question was whether anybody had seen it, so it is an answer to that :) Perhaps the question was not well formulated, but I wanted to know if it was a common problem before reporting a bug.
Bale ( 2013-12-28 22:12:33 +0200 )editWell true I guess, though really a proper answer would also explain why it happened - a "me too" isn't adding any value (and for what it's worth, I too got the system update notification a second time having already updated to 1.0.2.5)
Milhouse ( 2013-12-28 22:16:09 +0200 )editI rephrased since it seems others have seen it too.
Bale ( 2013-12-28 22:18:42 +0200 )editHad the same "problem", the notification disappeared after I forced a check in the system settings.
hardcodes.de ( 2013-12-28 22:55:24 +0200 )editSorry about that, it was my fault; it is indeed just a comment :-)
arnbak ( 2013-12-28 23:02:31 +0200 )editHappens to me also. If there is somebody reading this who could shed some light here, pretty please??
zenzen ( 2013-12-29 00:10:25 +0200 )editHappened to me twice in the last hour. First time it in deed did the update after my confirmation, second time I had notification but when going to the update screen it said "Actual" and dismissed the Update.
ramoth ( 2013-12-29 03:14:17 +0200 )editI just got the same notification, and wonder if it's a coincidence that it happened minutes after midnight UTC 1/1-2014?
Tanghus ( 2014-01-01 02:17:34 +0200 )editLike @Tanghus I've also just had it for the first time today. I updated to1.0.2.5 on the 28th so it went about 3 and a half days before the erroneous notification.
steph ( 2014-01-02 00:39:44 +0200 )editThis is a duplicate of https://together.jolla.com/question/4118/jolla-store-still-shows-system-update-after-phone-was-updated/
Neo ( 2014-01-02 14:33:29 +0200 )editFor me opening and closing the store several times cleared the false notification.
zlatko ( 2014-01-04 08:49:50 +0200 )editHere too !
olli ( 2014-01-07 19:58:21 +0200 )editStill getting this once in a few days. Anyone else? We still do not have any idea about what it is and how to fix it, right? Could someone from Jolla say if this will disappear with the next update?
Neo ( 2014-01-09 00:16:23 +0200 )edit@Neo same here. I received the update notification to 1.0.2.5 just monemnts ago, and I'm been on the latest version since 28.12.2013. This really should be fixed, or at least the root cause investigated.
foss4ever ( 2014-01-09 07:04:38 +0200 )editTo try to get rid of this I went to Settings > System settings > About product > Check updates and the status changed to up-to-date and Notification was cleared. Still we don't know why this keeps happening, to some of us, occasionally..
foss4ever ( 2014-01-09 07:09:56 +0200 )editJust open the Jolla Store and close it again, that usually gets rid of the "System Update" notification. Until the next time.
Milhouse ( 2014-01-09 07:12:04 +0200 )editI'm pretty sure Jolla know about this problem, what is causing it and have a solution, though that's no excuse for not posting an update on this question (which would help put an end to the "me too" comments - just vote if you have this problem, there's no need for a "me too" comment!)
@Milhouse Your suggestion did not fix it for me but only doing.as I wrote i.e. going to.Settings and checking for updates. Also, I.see no problem or harm in ppl commenting here when this problem re-surfaces.. That's how we keep Jolla aware that the issue is still with us.. If you don't care abt these comments, don't read them.
foss4ever ( 2014-01-09 07:20:19 +0200 )editOh and checking the "minor edit" box each time you make a correction to a post also prevents everyone being spammed with even more email each time you correct a spelling or typo in a "me too" post. :)
Milhouse ( 2014-01-09 07:25:40 +0200 )edit@Milhouse I know that button exists, and.I use it a lot. Just wondering why I received your comment 5 times.with no discernible difference in content. So seems you don't do as you tell others to do.;)
foss4ever ( 2014-01-09 07:30:41 +0200 )editNeither of my posts were edited as many as five times, although every edit did have the box ticked - seeing no modifications would suggest a problem with the Askbot email sender, whereas the multiple emails I received for your edits did contain modifications. Unless the "minor edit" box is being ignored (bug in Askbot)? I'll edit this post ONCE more, with the "minor edit" box ticked - let me know if you get an update. Minor edit: Adding this line AGAIN because Askbot lost the last one.
Milhouse ( 2014-01-09 07:36:00 +0200 )edit@Milhouse this is OT and has nothing to do with this issue. Thanks, for understanding ;)
foss4ever ( 2014-01-09 07:39:47 +0200 )edit@jjaone I will try you suggestion next time. For me just opening the Jolla store usually is not enough, so I reboot the phone and go to the Jolla store and then the message is "up to date".
Neo ( 2014-01-09 09:55:26 +0200 )editHad it also a couple of times. Every time I was thinking YES a new update but unfortunately it still is 1.0.2.5.
BonoNL ( 2014-01-12 01:12:28 +0200 )edit@Neo The workaround to clear this notification simply converted to an answer to this question (no explanation for the root-cause still known).
foss4ever ( 2014-01-12 01:22:04 +0200 )editIt just happened to me as well. I was on 1.0.2.5, it said an update is available, which was the same 1.0.2.5. I did the update, and voila... I am still at 1.0.2.5. Weird! It even gave me a nice changelog as expected for version 1.0.2.5, which was correct for this version. Odd! Oh well hopefully the real update is upon is very soon. :-D
avdwoude ( 2014-01-29 23:48:43 +0200 )edit@Neo: for me I have managed to get rid of it by opening the jollastore from the notification menu, as it then will make a check to see if you need it installed. I have seen that some uses the system check update. The problem is that it will reappear from time to time, sometimes multiple times a day, others it can take days in between. I don't reboot mine that often, maybe twice this year.
@jjaone: As far as I know there happened something during the new years eve/day, according to Stskeeps there was no staff on-duty who could fix the issue. I would guess that when that person who know what to fix didn't have any logs to look at when s/he got back to work after the new-years holiday.
Trizt ( 2014-01-31 10:28:41 +0200 )edit@Trizt Yeah, thanks for the info.. seems that these have been happening a lot today (already twice this morning) - maybe in preparation to jan14 upgrade this time.. ;)
foss4ever ( 2014-01-31 10:38:13 +0200 )edit@jjaone: Today I haven't got any, yesterday I got one. Really had been interesting to know how the whole check works, both client and server side.
Trizt ( 2014-01-31 11:24:02 +0200 )edit@Tritzt Yep would be nice to know, cause for the last hours, I've been having them constantly, sometimes disappearing soon, sometimes not.. Also, 'pkcon reftesh' stalls in 'waiting in a queue', and Store suggests downloading the same old 1.0.2.5 still
foss4ever ( 2014-01-31 11:32:24 +0200 )editAs reported this happened a few days ago, and it actually installed. But I noticed yesterday that the release name is misspelled as 'Maadajävri', which should of course be 'Maadajärvi'. The version number is 1.0.2.5 as it was before, but I am not sure if this release name was misspelled before the last update that when from 1.0.2.5 to 1.0.2.5 again (so same version number). Should I be worried that some malicious hacker introduced something that is cunningly masked?
avdwoude ( 2014-01-31 15:42:22 +0200 )editI think not: [Release Notes] Software version 1.0.2.5, Maadajävri
gsalone ( 2014-01-31 17:52:59 +0200 )editMaadajävri (Tyvijärvi) in Lapland/Finland. Also, name of #SailfishOS version 1.0.2.5 http://t.co/TyGf7HMRDk
foss4ever ( 2014-01-31 18:51:28 +0200 )edit