Created attachment 129530 [details]
Computer Hardware Info

Created attachment 129531 [details]
Software Center Version

Created attachment 129532 [details]
Error Splashscreen

Can you check what output you get from PackageKit network state using this command?
qdbus --system org.freedesktop.PackageKit /org/freedesktop/PackageKit org.freedesktop.PackageKit.NetworkState

You should get 2 which corresponds to online:
static const PkEnumMatch enum_network[] = {
        {PK_NETWORK_ENUM_UNKNOWN,               "unknown"},     /* fall though value */
        {PK_NETWORK_ENUM_OFFLINE,               "offline"},
        {PK_NETWORK_ENUM_ONLINE,                "online"},
        {PK_NETWORK_ENUM_WIRED,                 "wired"},
        {PK_NETWORK_ENUM_WIFI,                  "wifi"},
        {PK_NETWORK_ENUM_MOBILE,                "mobile"},
        {0, NULL}
};

Please verify the command I entered:

bluedevil@bluedevil-Aspire-5532:~$ qdbus --system org.freedesktop.PackageKit /org/freedesktop/PackageKit org.freedesktop.PackageKit.NetworkState
2

Came back with the number 2 only.


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, June 20, 2020 8:58 PM, Aleix Pol <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=422432
>
> Aleix Pol aleixpol@kde.org changed:
>
> What |Removed |Added
>
> -----------------------
>
>            Severity|major                       |normal
>
>
> --- Comment #4 from Aleix Polaleixpol@kde.org ---
>
> Can you check what output you get from PackageKit network state using this
> command?
> qdbus --system org.freedesktop.PackageKit /org/freedesktop/PackageKit
> org.freedesktop.PackageKit.NetworkState
>
> You should get 2 which corresponds to online:
> static const PkEnumMatch enum_network[] = {
> {PK_NETWORK_ENUM_UNKNOWN, "unknown"}, /* fall though
> value */
> {PK_NETWORK_ENUM_OFFLINE, "offline"},
> {PK_NETWORK_ENUM_ONLINE, "online"},
> {PK_NETWORK_ENUM_WIRED, "wired"},
> {PK_NETWORK_ENUM_WIFI, "wifi"},
> {PK_NETWORK_ENUM_MOBILE, "mobile"},
> {0, NULL}
> };
>
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> You are receiving this mail because:
> You are on the CC list for the bug.

Is it possible that you're running an http proxy?

The application doesn't seem to be able to fetch this file:
https://autoconfig.kde.org/discover/featured-5.9.json

*** Bug 420941 has been marked as a duplicate of this bug. ***

A few hours ago I saw this error message during ~3 seconds when I opened Discover 5.20.2 on Arch Linux by the first time after login. Apps list was loaded as expected after the delay.

I also see this for 5.20.5-2 (Debian unstable). 
Maybe related: Listing of application also is showing me a spinning wheel for ever.
Sometimes the listing for "Plasma Addons" works.

$qdbus --system org.freedesktop.PackageKit /org/freedesktop/PackageKit org.freedesktop.PackageKit.NetworkState
2

I'll attach two logfiles with QT_LOGGING_RULES="*=true;qt.*=false" plasma-discover.

Created attachment 135508 [details]
QT_LOGGING_RULES="*=true;qt.*=false" plasma-discover default sreen

Run discover wait for some secs and I see this error screen.

Created attachment 135509 [details]
QT_LOGGING_RULES="*=true;qt.*=false" plasma-discover - marble addons section

Start plasma-discover:
* switch to Applications Addons -> Marble

When I start marble and see no issue in listing the addons.

Does running "appstreamcli refresh" before doing so make a difference?

It seems to me like the appstream db is not populated yet.

(In reply to Aleix Pol from comment #12)
> Does running "appstreamcli refresh" before doing so make a difference?
> 
> It seems to me like the appstream db is not populated yet.

(as root)

# LANG=C appstreamcli refresh 
AppStream cache update is not necessary.
# LANG=C appstreamcli refresh --force
AppStream cache update completed successfully.

(as normal user)
$ LANG=C appstreamcli status
AppStream Status:
Version: 0.14.0

Distribution metadata:
 /usr/share/app-info
  - Empty.

 /var/lib/app-info
  - YAML: 0
  - Iconsets:
     debian-sid-main
     debian-sid-non-free
     debian-sid-contrib
     debian-stretch-main
     debian-stretch-non-free
     debian-stretch-contrib

 /var/cache/app-info
  - Empty.

Metainfo files:
  - Found 250 components.
  - Found 4 components in legacy paths.

Summary:
We have information on 250 software components.

$ appstreamcli search konsole
Identifier: org.kde.konsole.desktop [desktop-application]
Name: Konsole
Summary: Terminal
Homepage: https://konsole.kde.org/
Icon: utilities-terminal
---
Identifier: org.kde.yakuake.desktop [desktop-application]
Name: Yakuake
Summary: Drop-down Terminal
Homepage: https://kde.org/applications/system/org.kde.yakuake
Icon: yakuake

At least for me this seems fine. Doesn't have changed anything for discover.

Btw. other users on Debian unstable can happily use Discover:

[13:03] <myself> Did someone checked discover? For me it does takes ages before listing anything and often timeout
[13:03] <myself> my inet should be fast enough
[13:07] <other> works for me in a couple of seconds
[13:07] <other> ~40 Mbps down so not really slow
[13:08] <myself> also the different categories?
[13:08] <other> when you say anything, I get direct view of the highlighted apps
[13:08] <myself> for me only show updates works ;)

*** Bug 437058 has been marked as a duplicate of this bug. ***

Created attachment 138982 [details]
plasma-discover.log

part of the system log

*** Bug 438054 has been marked as a duplicate of this bug. ***

*** Bug 438028 has been marked as a duplicate of this bug. ***

*** Bug 438054 has been marked as a duplicate of this bug. ***

*** Bug 438054 has been marked as a duplicate of this bug. ***

*** Bug 439247 has been marked as a duplicate of this bug. ***

*** Bug 440404 has been marked as a duplicate of this bug. ***

*** Bug 443617 has been marked as a duplicate of this bug. ***

With 5.23.3:
* I can now successfully browse the Addons for KDE software.
* It list me the Debian packages that can be upgraded and I can see the information /changelog etc. for those packages.
* "Installed" only listing the installed Addons.

but I still get  when opening Discover the error message: "Unable to load applications. Please verify internet connectivity.".
Every section and subsection inside "Applications" is empty.

@Sandro is it possible that your system just doesn't have any appstream information available for some reason?

(In reply to Aleix Pol from comment #25)
> @Sandro is it possible that your system just doesn't have any appstream
> information available for some reason?

See my comment #13. This is still true for the current version too. If you have any other check how to make sure, that appstream information are available, than give me a hint. I'm not familiar with appstream data

May be it help.
Look at the conflict between appstream-data and appstream-data-pamac.

(In reply to Misha from comment #27)
> May be it help.
> Look at the conflict between appstream-data and appstream-data-pamac.

There is no appstream-data or appstream-data-pamac neither in Debian nor in Ubuntu. What distro you are using?

So you forgot. I was first who open this theme(issue). My distro - Arch.

@Sandro Can you do `appstreamcli search blender` or any application that you don't have installed?
There's a chance that those you find are the ones from the apps you have installed already.

Created attachment 144256 [details]
1638792661187blob.jpg

 Hola, imagen antes de buscar cualquier aplicación en Discover.

Imagen al buscar Filezilla.


Imagen la darle clic en Aplicaciones.

El problema es al abrir Discover, muestra el error de conexión pero ese no es el problema porque al buscar alguna aplicación o al darle clic en alguna opción del menú si muestra las aplicaciones.
Gracias


    El viernes, 3 de diciembre de 2021 07:08:11 p. m. GMT-5, Aleix Pol <bugzilla_noreply@kde.org> escribió:  
 
 https://bugs.kde.org/show_bug.cgi?id=422432

--- Comment #30 from Aleix Pol <aleixpol@kde.org> ---
@Sandro Can you do `appstreamcli search blender` or any application that you
don't have installed?
There's a chance that those you find are the ones from the apps you have
installed already.

Created attachment 144257 [details]
1638792739149blob.jpg

Created attachment 144258 [details]
1638792821728blob.jpg

I tried the commandline:

$ appstreamcli search blender
Unable to find component matching blender!
$ appstreamcli search marble
Identifier: org.kde.marble.desktop [desktop-application]
Name: Marble
Summary: Virtual Globe
Homepage: https://marble.kde.org/
Icon: marble
---
Identifier: org.kde.ksame.desktop [desktop-application]
Name: KSame
Summary: KSame is a game mode of the game Klickety, which is an adaptation of the "clickomania" game
Homepage: https://games.kde.org/games/klickety
Icon: ksame

blender is not installed on my system, marble and klickety are both installed. But if I search in Discover I don't find them. The search results are only wallpapers, not the app.

Right, we ask discover to only search in the system-wide database. Supporting locally installed files like that brings these weird cases.

The only solution I see is to get Parrot Linux (or whichever you are using) to support appstream information. It's well supported by Debian so there must be something going on there: https://wiki.debian.org/AppStream

Agreed that the error message is confusing, we already addressed it by Plasma 5.24.

(In reply to Aleix Pol from comment #35)
> Right, we ask discover to only search in the system-wide database.
> Supporting locally installed files like that brings these weird cases.
>
> The only solution I see is to get Parrot Linux (or whichever you are using)
> to support appstream information. It's well supported by Debian so there
> must be something going on there: https://wiki.debian.org/AppStream

I can understand, that discover is not able to find blender, as AppStream does not give anything back. But krita and klickery are both installed locally but still I cannot find them in discover, if I search or browse the categories. From my point of view it seems like, discover not even ask AppStream at all.

I run strace to look if any library is missing, but the only appstream related library is found: 
   openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/libappstream.so.4", O_RDONLY|O_CLOEXEC) = 3

That means discover loads the library, I expect  that is also request appstream directly via libappstream and that there is no kio involved.

Okay now I looked even deeper into how Debian is handling the Appstream stuff. Finally I found out that my local metadata file was not updated since a very long time, as the update process was failing. I fixed that and with a fresh Appstream cache I can successfully find all three applications independent, of the installations status.

Maybe this needs to be reported to the Debian folks? There should probably be a background thing that syncs appstream data.

(In reply to Nate Graham from comment #38)
> Maybe this needs to be reported to the Debian folks? There should probably
> be a background thing that syncs appstream data.

It is very likely that this was my own failure as I manually disabled it to reduce the download data two years ago. Normally AppStream data is updated in Debian, when you refresh the package list.

So these are the "specs" of my system:

Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.2.0-33-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Celeron® J4105 CPU @ 1.50GHz
Memory: 7.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 600

On this machine I have this bug too. On my laptop I don't and it's the same system.
I just installed the whole Neon system again, it didn't help, I made a fresh user (with administrator rights) this fresh user had the same problem.
I started up "plasma-discover" from the console and it gave me this output:

(command in konsole) pieter@neon-user:~$ plasma-discover
(output konsole) fetch ratings! false
adding empty sources model QStandardItemModel(0x5573f5c573a0)
QObject::startTimer: Timers cannot have negative intervals
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/BasicListItem.qml:288:18: QML QQuickItem*: Binding loop detected for property "implicitWidth"
no component found for "org.kde.neon.neon"
took really long to fetch KNSBackend(0x5573f5bbb6c0, name = "/usr/share/knsrcfiles/kwineffect.knsrc")
took really long to fetch KNSBackend(0x5573f5bc0200, name = "/usr/share/knsrcfiles/lookandfeel.knsrc")
took really long to fetch KNSBackend(0x5573f5bcdaa0, name = "/usr/share/knsrcfiles/k3btheme.knsrc")
took really long to fetch KNSBackend(0x5573f5bd0d60, name = "/usr/share/knsrcfiles/plymouth.knsrc")
took really long to fetch KNSBackend(0x5573f5bc8d70, name = "/usr/share/knsrcfiles/plasmoids.knsrc")
took really long to fetch KNSBackend(0x5573f5bd1d50, name = "/usr/share/knsrcfiles/plasma-themes.knsrc")
took really long to fetch KNSBackend(0x5573f5bcbda0, name = "/usr/share/knsrcfiles/window-decorations.knsrc")
took really long to fetch KNSBackend(0x5573f5bd2cc0, name = "/usr/share/knsrcfiles/kpat.knsrc")
took really long to fetch KNSBackend(0x5573f5bdd300, name = "/usr/share/knsrcfiles/xcursor.knsrc")
took really long to fetch KNSBackend(0x5573f5be4980, name = "/usr/share/knsrcfiles/servicemenu.knsrc")
took really long to fetch KNSBackend(0x5573f5bdeb60, name = "/usr/share/knsrcfiles/konsole.knsrc")
took really long to fetch KNSBackend(0x5573f5be6ef0, name = "/usr/share/knsrcfiles/kwinswitcher.knsrc")
took really long to fetch KNSBackend(0x5573f5bef2a0, name = "/usr/share/knsrcfiles/wallpaper-mobile.knsrc")
took really long to fetch KNSBackend(0x5573f5be9150, name = "/usr/share/knsrcfiles/icons.knsrc")
took really long to fetch KNSBackend(0x5573f5bdb240, name = "/usr/share/knsrcfiles/gtk_themes.knsrc")
took really long to fetch KNSBackend(0x5573f5bebfb0, name = "/usr/share/knsrcfiles/kcardtheme.knsrc")
took really long to fetch KNSBackend(0x5573f5bf5110, name = "/usr/share/knsrcfiles/wallpaper.knsrc")
took really long to fetch KNSBackend(0x5573f5bffdd0, name = "/usr/share/knsrcfiles/krunner.knsrc")
took really long to fetch KNSBackend(0x5573f5bfa450, name = "/usr/share/knsrcfiles/kfontinst.knsrc")
took really long to fetch KNSBackend(0x5573f5bff210, name = "/usr/share/knsrcfiles/comic.knsrc")
took really long to fetch KNSBackend(0x5573f5c0a450, name = "/usr/share/knsrcfiles/aurorae.knsrc")
took really long to fetch KNSBackend(0x5573f5c051d0, name = "/usr/share/knsrcfiles/ksplash.knsrc")
took really long to fetch KNSBackend(0x5573f5c0b570, name = "/usr/share/knsrcfiles/wallpaperplugin.knsrc")
took really long to fetch KNSBackend(0x5573f5c0ec40, name = "/usr/share/knsrcfiles/systemmonitor-faces.knsrc")
took really long to fetch KNSBackend(0x5573f5c0fb50, name = "/usr/share/knsrcfiles/systemmonitor-presets.knsrc")
took really long to fetch KNSBackend(0x5573f5c08910, name = "/usr/share/knsrcfiles/plasma-systemmonitor.knsrc")
took really long to fetch KNSBackend(0x5573f5c0c580, name = "/usr/share/knsrcfiles/sddmtheme.knsrc")
took really long to fetch KNSBackend(0x5573f5c1acb0, name = "/usr/share/knsrcfiles/colorschemes.knsrc")
took really long to fetch KNSBackend(0x5573f5c200c0, name = "/usr/share/knsrcfiles/kwinscripts.knsrc")
took really long to fetch FwupdBackend(0x5573f5b92d10)
packagekitqt.transaction: Unknown Transaction property: "Sender" QVariant(QString, ":1.232")
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight"

By the way: my Plasma 6 installation on another partition of this machine (Neon experimental) doesn't seem to have the problem.