Bug 366536

Summary:	Updater says packages available - discover reports up to date
Product:	[Applications] Discover	Reporter:	pmb <s093x6f6>
Component:	discover	Assignee:	Aleix Pol <aleixpol>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	5.7.3
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description pmb 2016-08-08 20:08:00 UTC

I am using neon 5.7.3 which is up to date.

An icon in the system tray advises me that 13 updates plus 1 security update are available.

Discover appears after clicking icon and reports, system up to date - no further activity

Using my update script I download 13 plus packages.

I cannot find a report about this issue, one or two close but nothing exact.


Reproducible: Always

Steps to Reproduce:
1. Click system tray update available icon when updates become available
2.
3.

Actual Results:  
Discover reports that my system is up to date

Expected Results:  
Discover should display the updates and allow me to download

One of the close reporters mentioned that they tried Muon and it worked. I have not done that but I will try it next time and report back. My updater script and Muon should be spot on. They both worked in the past.

Comment 1 Aleix Pol 2016-08-09 00:06:48 UTC

Hi,
Is it possible that you upgraded using apt-get? Such as "apt-get dist-upgrade"?

Comment 2 pmb 2016-08-09 00:23:27 UTC

Yes
My updater script uses
apt-get update
apt-get -y --force-yes dist-upgrade
apt-get -y --force-yes autoremove
apt-get clean
apt-get autoclean
then
/var/run/reboot-required (if required)

I have used it for years without any problems.

Hope this didn't screw you/me up?

Thanx

Comment 3 Aleix Pol 2016-08-09 23:49:51 UTC

No, no no. No problem with mixing packagekit and apt-get, other than the problem described here. I'll see what I can do.

You might be wondering, in Kubuntu we use QApt which talks directly to apt, so this problem doesn't happen.

Comment 4 Aleix Pol 2016-09-14 10:59:37 UTC


*** This bug has been marked as a duplicate of bug 366196 ***