https://bugs.kde.org/show_bug.cgi?id=409220

--- Comment #24 from Alan <alangdun...@outlook.com> ---
I literally had to strip the entire KDE framework from my system, as this issue
still hasn't been resolved.

Even with the latest updates and revisions to KDE & Plasma, Discover still is
still causing many system issues, connectivity issues, inability to use any of
the Application Back-ends (Snap, Flathub) & screws up the delivery of
notifications ( they self populate after an attempt is made to close them down,
growing in volume until system resources are used up)

Its a mess... Maybe the option is to pull Discover in the interim until these
showstopper bugs are fixed?



-----Original Message-----
From: Wolfgang Bauer
<bugzilla_nore...@kde.org<mailto:wolfgang%20bauer%20%3cbugzilla_nore...@kde.org%3e>>
Reply-To: bug-cont...@kde.org<mailto:bug-cont...@kde.org>
To: alangdun...@outlook.com<mailto:alangdun...@outlook.com>
Subject: [Discover] [Bug 409220] Discover says "Check Connectivity" instead of
displaying content with AppStream 0.12.7
Date: Wed, 07 Aug 2019 20:55:15 +0000

<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.kde.org%2Fshow_bug.cgi%3Fid%3D409220&amp;data=02%7C01%7C%7Ca435a44aedef4e3e8f8808d71b798de7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637008081187720348&amp;sdata=Rad2%2FdwPFWn3ucVTUjp0NqSePUIxm9qZzncMzr6ve3s%3D&amp;reserved=0>

https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.kde.org%2Fshow_bug.cgi%3Fid%3D409220&amp;data=02%7C01%7C%7Ca435a44aedef4e3e8f8808d71b798de7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637008081187720348&amp;sdata=Rad2%2FdwPFWn3ucVTUjp0NqSePUIxm9qZzncMzr6ve3s%3D&amp;reserved=0



--- Comment #23 from Wolfgang Bauer <

<mailto:wba...@tmo.at>

wba...@tmo.at

> ---

(In reply to Frank Kruger from comment #21)

The issue is solved for me with the fix discussed here:

<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fximion%2Fappstream%2Fissues%2F243&amp;data=02%7C01%7C%7Ca435a44aedef4e3e8f8808d71b798de7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637008081187720348&amp;sdata=Z%2FOkss6N%2FXgfjDRM2bYWe2YI9gY2fbgJ3MSXvjx7nrI%3D&amp;reserved=0>

https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fximion%2Fappstream%2Fissues%2F243&amp;data=02%7C01%7C%7Ca435a44aedef4e3e8f8808d71b798de7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637008081187720348&amp;sdata=Z%2FOkss6N%2FXgfjDRM2bYWe2YI9gY2fbgJ3MSXvjx7nrI%3D&amp;reserved=0

.


I don't think this fixes anything in regards to *this* bug.


FWIW, I just noticed this error message today, with openSUSE's AppStream 0.12.7

package that includes that fix.

Running "appstreamcli refresh" manually made it go away.


No idea where the problem lies though.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to