Updates shown for pre-installed apps which have been uninstalled

Bug #1314382 reported by dobey on 2014-04-29
56
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Medium
Alejandro J. Cura
click (Ubuntu)
Medium
Unassigned
ubuntu-system-settings (Ubuntu)
Low
Unassigned

Bug Description

I have uninstalled a few of the pre-installed click apps, as I have no intention of ever using them, so don't want them to clutter up the installed apps section of the scope. However, when I go to the Updates page of System Settings, "filemanager Version 0.3.163" is shown to me as an update. If I install it, then the File Manager returns to my installed apps list, though I previously removed it. Then uninstalling it again, and going back to Updates, I am again shown the same update as being available.

Also of note is that the updates page says "filemanager" rather than "File Manager" as the app name.

Changed in ubuntu-system-settings (Ubuntu):
importance: Undecided → Low
status: New → Confirmed
tags: added: updates
tags: added: bq
Pat McGowan (pat-mcgowan) wrote :

Is this still the case? Not sure what layer is the culprint

Changed in canonical-devices-system-image:
assignee: nobody → Alejandro J. Cura (alecu)
importance: Undecided → Medium
milestone: none → backlog
RobertZenz (robert-zenz) wrote :

This is still the case. I'm seeing this on my bq Aquaris 4.5 with Telegram.

Changed in canonical-devices-system-image:
status: New → Confirmed
Changed in click (Ubuntu):
status: New → Confirmed

Another french user reported the same behaviour with TG updates after being uninstalled, should we ask fr any logs about it?, if yes which ones?. We can reproduce it.

forgot to mention that these users are in OTA-8 =)

Changed in ubuntu-system-settings (Ubuntu):
status: Confirmed → Invalid
Changed in click (Ubuntu):
importance: Undecided → Medium
Alejandro J. Cura (alecu) wrote :

I reproduced this bug, and can clearly see that it's a bug in click itself.

steps:
- uninstall some package that's installed in the base image (eg: telegram 1.2)
- install it back from the store (eg: telegram 2.0)
- uninstall it once more
- try to see if the package is registered for the current user with "click list"

what happens:
- the package does not show at all

what should happen:
- the old version (eg: 1.2) of the package is listed

It seems that when it's uninstalling a version that was installed from the store it's not recreating the symlink to @hidden for the base version.

Pat McGowan (pat-mcgowan) wrote :

In my case using the same steps I see 2.0.4 in click list

ls -al /opt/click.ubuntu.com/.click/users/@all/

lrwxrwxrwx 1 root root 49 Nov 23 12:32 com.ubuntu.telegram -> /opt/click.ubuntu.com/com.ubuntu.telegram/2.0.4.0

 ls -l /custom/click/com.ubuntu.telegram/
total 4
drwxr-xr-x 12 root root 4096 Nov 11 23:20 1.3.20.114
lrwxrwxrwx 1 root root 10 Nov 11 23:20 current -> 1.3.20.114

 ls -l /custom/click/.click/users/@all
lrwxrwxrwx 1 root root 44 Nov 11 23:20 com.ubuntu.telegram -> /custom/click/com.ubuntu.telegram/1.3.20.114

I am not clear why the install of 2.0.4 from the store was put in @all rather than phablet like other store installs

Pat McGowan (pat-mcgowan) wrote :

Suspect my device has cruft making it non-standard so ignore last comment

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers