SUMMARY STEPS TO REPRODUCE 1. I checked my wifi is working and can downloads packages from terminal 2. I tried reinstalling plus the dependancy 3. Nevertheless my effort does not successed OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Can you share a screenshot?
Created attachment 121211 [details] screen capture I am having the same issue on Arch, KDE version 15.6.2. See attached screen capture.
Created attachment 121217 [details] attachment-21665-0.html The problem went away after reinstalling the app.. On Fri, Jun 28, 2019, 2:48 PM jr <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=409220 > > jr <jroll@purdue.edu> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |jroll@purdue.edu > > --- Comment #2 from jr <jroll@purdue.edu> --- > Created attachment 121211 [details] > --> https://bugs.kde.org/attachment.cgi?id=121211&action=edit > screen capture > > I am having the same issue on Arch, KDE version 15.6.2. See attached screen > capture. > > -- > You are receiving this mail because: > You reported the bug.
Seems like it's transient, but not uncommon.
*** Bug 409227 has been marked as a duplicate of this bug. ***
Created attachment 121249 [details] attachment-20739-0.html So far I have not seen the error. I cannot repeat an anymore so just mark it as solved On Sun, Jun 30, 2019, 1:20 PM Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=409220 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |alangdunbar@outlook.com > > --- Comment #5 from Nate Graham <nate@kde.org> --- > *** Bug 409227 has been marked as a duplicate of this bug. *** > > -- > You are receiving this mail because: > You reported the bug.
Created attachment 121250 [details] Discover 5.16.2 Screenshot No Connection I am still experiencing this issue on openSUSE Tumbleweed 20190628.
FYI: The issue is gone when downgrading AppStream to version 0.12.6.
Can you 100% confirm that? When you re-upgrade to 0.12.7, does the issue return?
(In reply to Nate Graham from comment #9) > Can you 100% confirm that? When you re-upgrade to 0.12.7, does the issue > return? Going back to AppStream 0.12.7, Discover does not even start. In fact, it crashes as described in bug#409195.
Created attachment 121373 [details] attachment-5994-0.html Frank, iafter reinstalling plasma-meta under tty1 suggests that you can install three or four more dependencies related to discover software package. I installed all those dependencies the problems go away. The web states that are dependencies which makes it a little bit confusing. Not only that packagekit-qt5 is enough to make it stable. Nevertheless it's still way better than gnome 3.32! On Sun, Jul 7, 2019, 2:17 PM Frank Kruger <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=409220 > > --- Comment #10 from Frank Kruger <fkrueger@mailbox.org> --- > (In reply to Nate Graham from comment #9) > > Can you 100% confirm that? When you re-upgrade to 0.12.7, does the issue > > return? > > Going back to AppStream 0.12.7, Discover does not even start. In fact, it > crashes as described in bug#409195. > > -- > You are receiving this mail because: > You reported the bug.
Yikes, looks like Discover has some problems with AppStream 0.12.7. We'll investigate. Thanks for your patience, folks. *** This bug has been marked as a duplicate of bug 409195 ***
(In reply to Nate Graham from comment #12) > Yikes, looks like Discover has some problems with AppStream 0.12.7. We'll > investigate. Thanks for your patience, folks. > > *** This bug has been marked as a duplicate of bug 409195 *** I'm not sure this is a duplicate though. Bug#409195 is about a *crash*... (which I think meanwhile is actually a problem in AppStream itself)(In reply to Nate Graham from comment #12) > Yikes, looks like Discover has some problems with AppStream 0.12.7. We'll > investigate. Thanks for your patience, folks. > > *** This bug has been marked as a duplicate of bug 409195 ***
(In reply to Wolfgang Bauer from comment #13) > (In reply to Nate Graham from comment #12) > > Yikes, looks like Discover has some problems with AppStream 0.12.7. We'll > > investigate. Thanks for your patience, folks. > > > > *** This bug has been marked as a duplicate of bug 409195 *** > > I'm not sure this is a duplicate though. > > Bug#409195 is about a *crash*... (which I think meanwhile is actually a > problem in AppStream itself)(In reply to Nate Graham from comment #12) > > Yikes, looks like Discover has some problems with AppStream 0.12.7. We'll > > investigate. Thanks for your patience, folks. > > > > *** This bug has been marked as a duplicate of bug 409195 *** It might be a coincidence that the issue described here does not show up with AppStream 0.12.6.
Created attachment 121450 [details] attachment-6833-0.html This is still apparent even with the update to KDE 5.16.3.. Also this bug crashing KDE5 and notifications are spawning multiple times when Discover is closed down... You are basically playing whack-a-mole with them until they use up all system resources It needs fixed!! -----Original Message----- From: Frank Kruger <bugzilla_noreply@kde.org<mailto:Frank%20Kruger%20%3cbugzilla_noreply@kde.org%3e>> Reply-To: bug-control@kde.org<mailto:bug-control@kde.org> To: alangdunbar@outlook.com<mailto:alangdunbar@outlook.com> Subject: [Discover] [Bug 409220] Discover says check connectivity Date: Wed, 10 Jul 2019 19:15:33 +0000 <https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.kde.org%2Fshow_bug.cgi%3Fid%3D409220&data=02%7C01%7C%7C0b70da7b92a34997be6108d7056afdce%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636983829383158932&sdata=az95miAxr%2ByazAVJnV5qDxoIdurz2c2Z4MLisT6FUvg%3D&reserved=0> https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.kde.org%2Fshow_bug.cgi%3Fid%3D409220&data=02%7C01%7C%7C0b70da7b92a34997be6108d7056afdce%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636983829383158932&sdata=az95miAxr%2ByazAVJnV5qDxoIdurz2c2Z4MLisT6FUvg%3D&reserved=0 --- Comment #14 from Frank Kruger < <mailto:fkrueger@mailbox.org> fkrueger@mailbox.org > --- (In reply to Wolfgang Bauer from comment #13) (In reply to Nate Graham from comment #12) Yikes, looks like Discover has some problems with AppStream 0.12.7. We'll investigate. Thanks for your patience, folks. *** This bug has been marked as a duplicate of bug 409195 *** I'm not sure this is a duplicate though. Bug#409195 is about a *crash*... (which I think meanwhile is actually a problem in AppStream itself)(In reply to Nate Graham from comment #12) Yikes, looks like Discover has some problems with AppStream 0.12.7. We'll investigate. Thanks for your patience, folks. *** This bug has been marked as a duplicate of bug 409195 *** It might be a coincidence that the issue described here does not show up with AppStream 0.12.6.
*** Bug 409458 has been marked as a duplicate of this bug. ***
So I have AppStream 0.12.7 and Discover 5.16.2 on Manjaro and I don't see this issue. For the people who are experiencing the issue, what distros are you using?
(In reply to Nate Graham from comment #17) > So I have AppStream 0.12.7 and Discover 5.16.2 on Manjaro and I don't see > this issue. > > For the people who are experiencing the issue, what distros are you using? openSUSE Tumbleweed (TW20190704).
Using Ubuntu 19.04 with KDE Plasma Desktop 5.16.3 Also tested on a new profile to see if this was the issue, however still the same result with "Check Connectivity" and playing whack-a-mole with notifications, when I close Discover. The only way to stop the notifications from multiplying is to reboot, as they will not stop. (Notification issue only happens with the closing of Discover)
Created attachment 121578 [details] attachment-13447-0.html I noticed that while installing Arch specifically plasma-meta I received a unusual error message. Related to archlinux-appstream-data and appstream-qt. I don't have a screenshot of this particular message but it is reproducible. So I will take a picture of it eventually and send it to you. Just to see if it would help I reinstalled both items archlinux-appstream-data and app stream-qt. As a result, connectivity issue with Discover software center disappeared. Yay! On Mon, Jul 15, 2019, 3:07 PM Alan <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=409220 > > --- Comment #19 from Alan <alangdunbar@outlook.com> --- > Using Ubuntu 19.04 with KDE Plasma Desktop 5.16.3 > > Also tested on a new profile to see if this was the issue, however still > the > same result with "Check Connectivity" and playing whack-a-mole with > notifications, when I close Discover. > > The only way to stop the notifications from multiplying is to reboot, as > they > will not stop. > > (Notification issue only happens with the closing of Discover) > > -- > You are receiving this mail because: > You reported the bug.
The issue is solved for me with the fix discussed here: https://github.com/ximion/appstream/issues/243.
Makes sense. Thanks for confirming!
(In reply to Frank Kruger from comment #21) > The issue is solved for me with the fix discussed here: > https://github.com/ximion/appstream/issues/243. 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.
Created attachment 122024 [details] attachment-5215-0.html 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_noreply@kde.org<mailto:Wolfgang%20Bauer%20%3cbugzilla_noreply@kde.org%3e>> Reply-To: bug-control@kde.org<mailto:bug-control@kde.org> To: alangdunbar@outlook.com<mailto:alangdunbar@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&data=02%7C01%7C%7Ca435a44aedef4e3e8f8808d71b798de7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637008081187720348&sdata=Rad2%2FdwPFWn3ucVTUjp0NqSePUIxm9qZzncMzr6ve3s%3D&reserved=0> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.kde.org%2Fshow_bug.cgi%3Fid%3D409220&data=02%7C01%7C%7Ca435a44aedef4e3e8f8808d71b798de7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637008081187720348&sdata=Rad2%2FdwPFWn3ucVTUjp0NqSePUIxm9qZzncMzr6ve3s%3D&reserved=0 --- Comment #23 from Wolfgang Bauer < <mailto:wbauer@tmo.at> wbauer@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&data=02%7C01%7C%7Ca435a44aedef4e3e8f8808d71b798de7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637008081187720348&sdata=Z%2FOkss6N%2FXgfjDRM2bYWe2YI9gY2fbgJ3MSXvjx7nrI%3D&reserved=0> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fximion%2Fappstream%2Fissues%2F243&data=02%7C01%7C%7Ca435a44aedef4e3e8f8808d71b798de7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637008081187720348&sdata=Z%2FOkss6N%2FXgfjDRM2bYWe2YI9gY2fbgJ3MSXvjx7nrI%3D&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.