[PLASMA 5] Discover not working

[Grahm]

Discover store is not able to connect to the internet ( I think ) and shows some error. I took a screenshot. Please help me fix it

[Snowhog]

What third-party PPAs/Repositories do you have? Open a konsole and type: ls -la /etc/apt/sources.list.d

Copy and paste the output here.

[Grahm]

Thanks. Please see

$ ls -la /etc/apt/sources.list.d
total 24
drwxr-xr-x 2 root root 4096 May 12 00:28 .
drwxr-xr-x 7 root root 4096 May 12 00:41 ..
-rw-r--r-- 1 root root 189 May 12 00:40 google-chrome.list
-rw-r--r-- 1 root root 189 May 12 00:40 google-chrome.list.save
-rw-r--r-- 1 root root 140 May 12 00:40 inkscape_dev-ubuntu-stable-focal.list
-rw-r--r-- 1 root root 140 May 12 00:40 inkscape_dev-ubuntu-stable-focal.list.save
-rw-r--r-- 1 root root 0 Apr 24 17:13 papirus-ubuntu-papirus-focal.list
-rw-r--r-- 1 root root 0 Apr 24 17:13 papirus-ubuntu-papirus-focal.list.save

[Grahm]

Does apt work from the Konsole?

How can I check ?

[Don B. Cilly]

sudo apt update && sudo apt full-upgrade
will do a full update.
sudo apt update
Will just update the package database.
After which,
apt list --upgradable will list upgradable packages, and sudo apt full-upgrade, update them.

Or, you could get this little script, it will do that and (a little) more.

[Grahm]

Thanks @Don.B.Silly

I have run sudo apt-get update command around a week back and I think it worked.

[chimak111]

sudo apt update && sudo apt full-upgrade
will do a full update.
...

I use that as well without any issue, but there are people who really don't like sudo apt full-upgrade. See Is apt full-upgrade safe?

[Grahm]

I simply love the way we can select apps from a software store. That is why I would like to bring Discover back.

[Don B. Cilly]

Well, the idea was to try and find out what the problem with Discover was.
If apt works, it's not with the apt part of it. Does it work? Even just updating the database?

[Grahm]

Thanks @Don.B.Silly

Here is the output of sudo apt update

Get:1 http://in.archive.ubuntu.com/ubuntu focal InRelease [265 kB]
Get:2 http://dl.google.com/linux/chrome/deb stable InRelease [1,811 B]
Get:3 http://ppa.launchpad.net/inkscape.dev/stable/ubuntu focal InRelease [17.5 kB]
Get:4 http://security.ubuntu.com/ubuntu focal-security InRelease [107 kB]
Get:5 http://in.archive.ubuntu.com/ubuntu focal-updates InRelease [107 kB]
Hit:6 http://archive.canonical.com/ubuntu focal InRelease
Get:7 http://in.archive.ubuntu.com/ubuntu focal-backports InRelease [98.3 kB]
Get:8 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages [1,127 B]
E: Repository 'http://ppa.launchpad.net/inkscape.dev/stable/ubuntu focal InRelease' changed its 'Suite' value from 'focal-updates' to 'focal-security'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N]

[Don B. Cilly]

Well, either say yes or no to the inskcape repo (no reason to say no, IMO), and see if it does update the database... the name change could actually be what blings Discover...

[jglen490]

If that PPA is important to you, then answer "y" and press on. Otherwise, remove that PPA, and press on.

[claydoh]

I use that as well without any issue, but there are people who really don't like sudo apt full-upgrade. See Is apt full-upgrade safe?

That is opinion, though not too long ago running plain 'upgrade' would not fully update an Ubuntu system. This occurs less in very recent times, however.
This above is actually the correct method in Debian. As Ubuntu also installs 'recommended' packages by default (Debian does not), this is iirc a reason why Ubuntu needs full-upgrade over the Debian upgrade.Ubuntu packaging is designed around using full-upgrade, and Ubuntu Software Center and Discover both run updates as 'full-upgrade'.

I do not think in the 15 years I have been running and supporting *butnu based systems that I have ever seen an instance of running 'full-upgrade' or formerly 'dist-upgrade' ever muck up anything where it was not due specifically to faulty packaging. I have seen more instances of NOT using full-upgrade causing errors due to missing deps that running a simple 'upgrade' does not install.

This confusion between the Debian way and the Ubuntu way is a reason, and very possibly the entire reason, why KDE Neon prefers people use pkcon over apt for updating via the cli, and even 'disables' the 'upgrade' option with a warning message. Incomplete upgrades were a very common issue in Neon, particularly those who were not familiar with *buntu's differences from Debian. Pkcon is just the command line interface to packagekit, the distro- agnostic software tool used by Discover and others. When used on a *buntu system, packagekit (correctly) calls apt with the 'full-upgrade' option.

[claydoh]

looking at the error message in the OPs first post, it looks like the Partner repo is causing the issue, probably not a PPA.
This extra repo doesn't have anything useful for most (if anything at all for Focal) and is not enabled by default.

Anyway:
In Discover, go to Settings , then look for Software Sources, and go to the Other Software tab, and make sure to un-check the Canonical Partner repo





The error message is likely temporary, there may have been an issue with that particular server, or perhaps a corrupted file download , so once you have updated etc you can try and re-enable it if you need something from it, and see if it has been fixed.

[Avi512]

Seems like there is a probably a "faulty" source if you go to Discover -> Settings. Try to spot the source mentioned in the error and disable it.