So, after I switched from kubuntu 24 to kubuntu 25, I had new problems with plasma-discover. This time, perhaps, I could have done something wrong that broke it, because the program was working out of the box.
First, an error appears when I go to the Updates tab:
E: https://download.docker.com/linux/ubuntu questing InRelease is not (yet) available (Unable to connect to 127.0.0.1:10808:)
E: http://security.ubuntu.com/ubuntu questing-security InRelease is not (yet) available (Unable to connect to 127.0.0.1:10808:)
E: https://ppa.launchpadcontent.net/rael-gc/rvm/ubuntu questing InRelease is not (yet) available (Unable to connect to 127.0.0.1:10808:)
E: http://archive.ubuntu.com/ubuntu questing-backports InRelease is not (yet) available (Unable to connect to 127.0.0.1:10808:)
E: http://archive.ubuntu.com/ubuntu questing-updates InRelease is not (yet) available (Unable to connect to 127.0.0.1:10808:)
E: https://hub.unity3d.com/linux/repos/deb stable InRelease is not (yet) available (Unable to connect to 127.0.0.1:10808:)
E: https://hub.unity3d.com/linux/repos/deb unstable InRelease is not (yet) available (Unable to connect to 127.0.0.1:10808:)
E: https://ppa.launchpadcontent.net/mc3man/xerus-media/ubuntu questing InRelease is not (yet) available (Unable to connect to 127.0.0.1:10808:)
E: http://archive.ubuntu.com/ubuntu questing InRelease is not (yet) available (Unable to connect to 127.0.0.1:10808:)
Well, of course, I can’t update anything through Discover.
Besides, I can’t download anything using the app.Here’s a error:
Package download failed
Here is a description of my system via kinfo:
Operating System: Kubuntu 25.10
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2
Kernel Version: 6.17.0-8-generic (64-bit)
Graphics Platform: Wayland
Processors: 20 × 12th Gen Intel® Core™ i7-12700H
Memory: 40 GiB of RAM (38.9 GiB usable)
Graphics Processor 1: NVIDIA GeForce RTX 3060 Laptop GPU
Graphics Processor 2: Intel® Iris® Xe Graphics
I have everything OK with the Internet, I calmly download what I need through the terminal. I just don’t like that something “native” in the system doesn’t work. I didn’t like this on Windows, so I decided to switch.
For me, in general, it would be a sufficient solution to find some kind of complete replacement for Discover, but I would still like to fix it.
And yes, I have already tried all the tips on similar topics on this forum and others. Reinstallation and other things didn’t help.