Bug 399981 - Both "check for updates" and "update all" buttons are disabled even when updates are available
Summary: Both "check for updates" and "update all" buttons are disabled even when upda...
Status: RESOLVED FIXED
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: 5.14.5
Platform: Arch Linux Linux
: VHI grave
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords:
: 400026 401482 402537 402718 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-10-18 12:43 UTC by Patrick Silva
Modified: 2019-02-19 14:55 UTC (History)
20 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.15.0


Attachments
screenshot (126.23 KB, image/png)
2018-10-18 12:43 UTC, Patrick Silva
Details
flatpaks size is 0 B (87.53 KB, image/png)
2018-10-18 13:11 UTC, Patrick Silva
Details
gdb plasma-discover where Update button isn't available (7.50 KB, text/plain)
2018-12-31 04:26 UTC, Andras
Details
debug plasma-discover where Update button isn't available (167.01 KB, text/plain)
2018-12-31 04:40 UTC, Andras
Details
debug from my machine (5.24 KB, text/plain)
2018-12-31 09:37 UTC, lega99
Details
debug duzi (140.43 KB, text/plain)
2018-12-31 09:37 UTC, lega99
Details
screenshot plasma-discoveri (6.64 KB, image/png)
2019-01-13 11:00 UTC, lega99
Details
screenshot plasma-discoveri missing buton (5.57 KB, image/png)
2019-01-13 11:01 UTC, lega99
Details
debug plasma-discoveri (163.99 KB, text/plain)
2019-01-13 11:02 UTC, lega99
Details
reinstalled plasma-discover with disabled update button issue crashes at start (29.34 KB, text/plain)
2019-01-16 14:39 UTC, Andras
Details
Notification of updates (1.29 MB, image/png)
2019-02-06 12:47 UTC, lega99
Details
Discover program (109.40 KB, image/png)
2019-02-06 12:49 UTC, lega99
Details
Discover crashed after few minutes with deb packages from comment #99 (22.23 KB, text/plain)
2019-02-06 17:18 UTC, Andras
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2018-10-18 12:43:18 UTC
Created attachment 115722 [details]
screenshot

SUMMARY
Apparently the problem occurs randomly.

STEPS TO REPRODUCE
1. I started plasma session
2. I opened discover by clicking "view updates" button in updates notifier
3. 

OBSERVED RESULT
both "check for updates" and "update all" buttons are disabled. See the screenshot.

EXPECTED RESULT
both "check for updates" and "update all" should be enabled.


SOFTWARE VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.14.1
Qt Version: 5.12.0
KDE Frameworks Version: 5.51.0
Comment 1 Patrick Silva 2018-10-18 13:11:52 UTC
Created attachment 115723 [details]
flatpaks size is 0 B

I have just installed the packages from Arch repos (Opera and Thunderbird) via konsole. Now the size of the remaining packages (all are flatpaks) is 0 B.
And the buttons are still disabled.
Comment 2 Nate Graham 2018-10-18 19:32:20 UTC
Do any of the buttons become un-grayed-out after a few seconds (or minutes)?
Comment 3 Patrick Silva 2018-10-18 20:03:18 UTC
Hi Nate
Discover has been open for ten minutes here.
The buttons are still disabled.
Comment 4 Nate Graham 2018-10-18 20:12:43 UTC
Heh, that's definitely not normal.
Comment 5 Robert Griffiths 2018-10-19 13:26:15 UTC
I didn't see this bug so I created a dupe, this is my info:

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.14.1
KDE Frameworks Version: 5.52.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION
This has happened 3 days in a row after I've booted (with Discover auto-starting) and each time I've manually checked or Discover has auto-checked during the day. Only happened after a Neon Dev Stable Update.

This is me now:
discover/bionic,now 2.1.2-8 amd64 [installed]
discover-data/bionic,bionic,now 2.2013.01.11 all [installed,automatic]
libdiscover2/bionic,now 2.1.2-8 amd64 [installed,automatic]
plasma-discover/bionic,now 5.14.1+p18.04+git20181018.0046-0 amd64 [installed,automatic]
plasma-discover-common/bionic,bionic,bionic,now 5.14.1+p18.04+git20181018.0046-0 all [installed,automatic]
plasma-discover-flatpak-backend/bionic,now 5.14.1+p18.04+git20181018.0046-0 amd64 [installed,automatic]
plasma-discover-private/bionic,now 5.14.1+p18.04+git20181018.0046-0 amd64 [installed,automatic]
plasma-discover-snap-backend/bionic,now 5.14.1+p18.04+git20181018.0046-0 amd64 [installed,automatic]
plasma-discover-updater/bionic,now 5.14.1+p18.04+git20181018.0046-0 amd64 [installed,automatic]

But it started happening after the previous update (not yesterday's).
Comment 6 Robert Griffiths 2018-10-19 13:26:53 UTC
*** Bug 400026 has been marked as a duplicate of this bug. ***
Comment 7 Patrick Silva 2018-10-21 15:03:29 UTC
I have just noticed that the problem does not occur when I start plasma using another user account.
Comment 8 Robert Griffiths 2018-10-23 08:10:43 UTC
This seems solved on my system Neon Dev Stable. Worked ok starting yesterday and has worked 3 times in a row, including this morning before the update to these below (I wanted to try 2 days in a row before reporting so I'm not sure what/when fixed it):

discover/bionic,now 2.1.2-8 amd64 [installed]
discover-data/bionic,bionic,now 2.2013.01.11 all [installed,automatic]
libdiscover2/bionic,now 2.1.2-8 amd64 [installed,automatic]
plasma-discover/bionic,now 5.14.1+p18.04+git20181022.1711-0 amd64 [installed,automatic]
plasma-discover-common/bionic,bionic,bionic,now 5.14.1+p18.04+git20181022.1711-0 all [installed,automatic]
plasma-discover-flatpak-backend/bionic,now 5.14.1+p18.04+git20181022.1711-0 amd64 [installed,automatic]
plasma-discover-private/bionic,now 5.14.1+p18.04+git20181022.1711-0 amd64 [installed,automatic]
plasma-discover-snap-backend/bionic,now 5.14.1+p18.04+git20181022.1711-0 amd64 [installed,automatic]
plasma-discover-updater/bionic,now 5.14.1+p18.04+git20181022.1711-0 amd64 [installed,automatic]
Comment 9 Nate Graham 2018-11-28 18:09:34 UTC
*** Bug 401482 has been marked as a duplicate of this bug. ***
Comment 10 Omar 2018-11-30 10:11:29 UTC
Doesn't work also here. This is new, normal Discover would take minute/seconds to refresh available updates, but today I left it open and focused overnight and buttons sill greyed out. Seems like a recent regression to me.

Distro: Neon Dev Stable

Relevant Packages:
plasma-discover/bionic,now 5.14.4+p18.04+git20181127.1756-0 amd64 [installed]
plasma-discover-common/bionic,bionic,bionic,now 5.14.4+p18.04+git20181127.1756-0 all [installed,automatic]
plasma-discover-private/bionic,now 5.14.4+p18.04+git20181127.1756-0 amd64 [installed,automatic]
plasma-discover-updater/bionic,now 5.14.4+p18.04+git20181127.1756-0 amd64 [installed,automatic]
Comment 11 Wyatt Childers 2018-12-20 15:53:34 UTC
Can confirm, this is happening for me as well.

I had to discover hang, and then killed it during an update process. I wonder if this is the result of some state file getting corrupted?
Comment 12 Wyatt Childers 2018-12-20 15:55:30 UTC
Probably worth noting updating through flatpak, pkcon, and apt via the command line is working without issue.
Comment 13 Elmas 2018-12-23 10:17:20 UTC
I use KDE neon when I install calligra app, it makes discover update button disappear.
doesnt metter you uninstall calligra, discover checking update button still doesnt show .Kde discover says fetching update but no update chacking.
Comment 14 Elmas 2018-12-23 10:20:54 UTC
I use KDE neon when I install calligra app, it makes discover update button disappear.
doesnt matter you uninstall calligra, discover checking update button still doesnt show .Kde discover says fetching update but no update checking.
Comment 15 Brian Wright 2018-12-24 22:14:46 UTC
I'm also experiencing the same issue - "Check for Updates" and "Update Now" buttons are greyed out on version 5.14.4 on KDE Neon, based on Ubuntu 18.04.
Comment 16 Patrick Silva 2018-12-25 12:27:54 UTC
*** Bug 402537 has been marked as a duplicate of this bug. ***
Comment 17 Elmas 2018-12-25 13:07:35 UTC
(In reply to Brian Wright from comment #15)
> I'm also experiencing the same issue - "Check for Updates" and "Update Now"
> buttons are greyed out on version 5.14.4 on KDE Neon, based on Ubuntu 18.04.

Don't install Calligra. I dont know why but after I install Calligra app, it fail discover to update.
Comment 18 lega99 2018-12-30 15:24:39 UTC
For some reason, the update now button in discover isn't showing ?
It says there are updates available but i cant download them ?
Neon user edition on Ubuntu 18.04LTS
Comment 19 lega99 2018-12-30 15:28:33 UTC
I don't install Calligra in my Neon user edition and have problem with update buttons is grayed
Comment 20 Elmas 2018-12-30 18:09:18 UTC
(In reply to lega99 from comment #19)
> I don't install Calligra in my Neon user edition and have problem with
> update buttons is grayed

Somehow, KDE neon has such problem but not Debian testing KDE+nonefree, Kubuntu 19.04 - 18.10, Fedora KDE spins.

What about using Kubuntu! Kubuntu distro seems better than KDE neon. Give a try.
Comment 21 Patrick Silva 2018-12-30 18:15:14 UTC
I was affected on Arch Linux and calligra is not installed here.
Currently discover is completely unusable here because it crashes at startup (bug 402562).
Comment 22 Elmas 2018-12-30 19:32:30 UTC
(In reply to Patrick Silva from comment #21)
> I was affected on Arch Linux and calligra is not installed here.
> Currently discover is completely unusable here because it crashes at startup
> (bug 402562).

I haven't seen discovery update issue in this distros ; Debian testing KDE+ nonefree ( I use this distro) , Kubuntu , Fedora 29 KDE spins.
Comment 23 Elmas 2018-12-30 19:33:09 UTC
(In reply to Patrick Silva from comment #21)
> I was affected on Arch Linux and calligra is not installed here.
> Currently discover is completely unusable here because it crashes at startup
> (bug 402562).

I haven't seen discover update issue in this distros ; Debian testing KDE+ nonefree ( I use this distro) , Kubuntu , Fedora 29 KDE spins.
Comment 24 lega99 2018-12-30 23:55:43 UTC
(In reply to Patrick Silva from comment #0)
> Created attachment 115722 [details]
> screenshot
> 
> SUMMARY
> Apparently the problem occurs randomly.
> 
> STEPS TO REPRODUCE
> 1. I started plasma session
> 2. I opened discover by clicking "view updates" button in updates notifier
> 3. 
> 
> OBSERVED RESULT
> both "check for updates" and "update all" buttons are disabled. See the
> screenshot.
> 
> EXPECTED RESULT
> both "check for updates" and "update all" should be enabled.
> 
> 
> SOFTWARE VERSIONS
> Operating System: Arch Linux 
> KDE Plasma Version: 5.14.1
> Qt Version: 5.12.0
> KDE Frameworks Version: 5.51.0

I do not understand why update in the Arch system with the discover when the Octopi or Pacman program works. I use Octopi or Pacman in Manjaro.
Comment 25 lega99 2018-12-31 00:00:26 UTC
(In reply to Elmas from comment #20)
> (In reply to lega99 from comment #19)
> > I don't install Calligra in my Neon user edition and have problem with
> > update buttons is grayed
> 
> Somehow, KDE neon has such problem but not Debian testing KDE+nonefree,
> Kubuntu 19.04 - 18.10, Fedora KDE spins.
> 
> What about using Kubuntu! Kubuntu distro seems better than KDE neon. Give a
> try.

Kubuntu 18.10 and 19.04 versions are transient and only exist for 9 months. 20.04 will be a new LTS version
Comment 26 lega99 2018-12-31 00:03:41 UTC
(In reply to Elmas from comment #20)
> (In reply to lega99 from comment #19)
> > I don't install Calligra in my Neon user edition and have problem with
> > update buttons is grayed
> 
> Somehow, KDE neon has such problem but not Debian testing KDE+nonefree,
> Kubuntu 19.04 - 18.10, Fedora KDE spins.
> 
> What about using Kubuntu! Kubuntu distro seems better than KDE neon. Give a
> try.

Neon is the author of plasma and discover program and it would be logical to have a program that works, but not so
Comment 27 Andras 2018-12-31 01:55:39 UTC
(In reply to Elmas from comment #20 and all others)
Please STOP and STOP using bug report for social media like comments, I mean it!!! If there is any personal note how you tried to solve it then ok place it here in very short limited sentences however there is no place here for assumptions and other OS contents. If you don't have backtrace or other worthy information about background processes about the bug then don't make bug reports everlasting with such an attitude, THANK YOU!
Comment 28 Andras 2018-12-31 04:26:52 UTC
Created attachment 117194 [details]
gdb plasma-discover where Update button isn't available

SOFTWARE/OS VERSIONS
KDE neon 5.14
KDE Plasma Version: 5.14.4
KDE Frameworks Version: 5.53.0
QT Version: 5.11.2
Kernel Version: 4.15.0-43-generic
OS Type: 64-bit

I try to make backtrace
gdb plasma-discover 2>&1 | tee ~/gdb_plasma-discover.txt
(gdb) r
(gdb) quit

As I heard there is no huge amount of help to develop discovery however if there is someone who could answer let me know if my backtrace is worthless and what else should affected users try to do for proper backtrace with actual helpful debug symbols. Thanks!
Comment 29 Andras 2018-12-31 04:40:29 UTC
Created attachment 117195 [details]
debug plasma-discover where Update button isn't available

This one is also a long shot only and also possibly unnecessarily too long.

LD_DEBUG=files plasma-discover 2>&1 | tee ~/debug_plasma-discover.txt
Comment 30 lega99 2018-12-31 09:34:23 UTC
SOFTWARE/OS VERSIONS
KDE neon 5.14
KDE Plasma Version: 5.14.4
KDE Frameworks Version: 5.53.0
QT Version: 5.11.2
Kernel Version: 4.20.0-042000-generic
OS Type: 64-bit

I had all versions of the kernel from version 4.14-4.20 and tried with all versions. Plasma-Discover did not work properly. Before updating to version 5.14.4, Plasma-Discover was working properly
Comment 31 lega99 2018-12-31 09:37:04 UTC
Created attachment 117201 [details]
debug from my machine

SOFTWARE/OS VERSIONS
KDE neon 5.14
KDE Plasma Version: 5.14.4
KDE Frameworks Version: 5.53.0
QT Version: 5.11.2
Kernel Version: 4.20.0-042000-generic
OS Type: 64-bit

I had all versions of the kernel from version 4.14-4.20 and tried with all versions. Plasma-Discover did not work properly. Before updating to version 5.14.4, Plasma-Discover was working properly
Comment 32 lega99 2018-12-31 09:37:52 UTC
Created attachment 117202 [details]
debug duzi

SOFTWARE/OS VERSIONS
KDE neon 5.14
KDE Plasma Version: 5.14.4
KDE Frameworks Version: 5.53.0
QT Version: 5.11.2
Kernel Version: 4.20.0-042000-generic
OS Type: 64-bit

I had all versions of the kernel from version 4.14-4.20 and tried with all versions. Plasma-Discover did not work properly. Before updating to version 5.14.4, Plasma-Discover was working properly
Comment 33 Nate Graham 2018-12-31 12:45:44 UTC
*** Bug 402718 has been marked as a duplicate of this bug. ***
Comment 34 Nate Graham 2018-12-31 13:43:05 UTC
Fixed with these two changes to the KNewStuff backend's library:
- https://phabricator.kde.org/D17593
- https://phabricator.kde.org/D17594

The fixes will be available in KDE Frameworks 5.54, which is scheduled to be released in a little under two weeks: https://community.kde.org/Schedules/Frameworks

Brave souls can compile the fixes themselves and report back regarding whether or not it fixes the issue for them.

I've done so and can no longer reproduce the issue.
Comment 36 lega99 2018-12-31 19:12:37 UTC
(In reply to Nate Graham from comment #34)
> Fixed with these two changes to the KNewStuff backend's library:
> - https://phabricator.kde.org/D17593
> - https://phabricator.kde.org/D17594
> 
> The fixes will be available in KDE Frameworks 5.54, which is scheduled to be
> released in a little under two weeks:
> https://community.kde.org/Schedules/Frameworks
> 
> Brave souls can compile the fixes themselves and report back regarding
> whether or not it fixes the issue for them.
> 
> I've done so and can no longer reproduce the issue.

I do not have libkf5newstuff I have libkf5newstuff-dev and it's not installed. There are 4:4.14.38-0ubuntu3 libknewstuff2-4 and 4:4.14.38-0ubuntu3 libknewstuff3-4 and I assume by default that these are some old libraries.

LSB Version:    core-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
Distributor ID: neon
Description:    KDE neon User Edition 5.14
Release:        18.04
Codename:       bionic
Comment 37 Andras 2019-01-01 20:48:43 UTC
(In reply to lega99 from comment #36)
> I do not have libkf5newstuff I have libkf5newstuff-dev and it's not
> installed.
It's already fixed, you don't have to assume anything and additional packages won't be necessary to install. Report back after KDE Frameworks 5.54 arrives on your system and your plasma-discovery still won't work regarding to this bug.
Its release expected around January 12th, 2019 (now I'm assuming :) that 2018 is a typo on frameworks schedules page):
https://community.kde.org/Schedules/Frameworks
Comment 38 lega99 2019-01-13 10:16:29 UTC
Again, the 2 update programs gimp-gmic gmic , the plasma-discoveri show but the update button is invisible.
libkf5newstuff is install I visual check
SOFTWARE/OS VERSIONS
KDE neon 5.14
plasma 5.14.5
KDE Frameworks Version: 5.54
QT Version: 5.11.2
Comment 39 lega99 2019-01-13 11:00:44 UTC
Created attachment 117433 [details]
screenshot  plasma-discoveri
Comment 40 lega99 2019-01-13 11:01:30 UTC
Created attachment 117434 [details]
screenshot plasma-discoveri missing buton
Comment 41 lega99 2019-01-13 11:02:32 UTC
Created attachment 117435 [details]
debug plasma-discoveri
Comment 42 Nate Graham 2019-01-13 14:43:46 UTC
:(
Comment 43 Thomas Pfeiffer 2019-01-15 10:57:15 UTC
I can confirm that the problem still persists in neon user edition, with Discover 5.14.5, KF 5.54.0 and Qt 5.11.2
Comment 44 Andrés R. 2019-01-15 11:28:36 UTC
Same, bug still happens on plasma-discover version 5.14.5, KDE Frameworks version 5.54.0 and Qt version 5.11.2, KDE Neon User edition
Comment 45 lega99 2019-01-15 15:43:33 UTC
(In reply to Andrés R. from comment #44)
> Same, bug still happens on plasma-discover version 5.14.5, KDE Frameworks
> version 5.54.0 and Qt version 5.11.2, KDE Neon User edition

I'm disappointed when somebody promises that the problem will be serious with frameworks 5.40. Indirectly suggest that I'm not trying to compile with updates. Everything is like a trial and everything will be okay just to reach January 12th.
Comment 46 Nate Graham 2019-01-15 22:48:10 UTC
Back to Discover this goes...
Comment 47 Gabor Körber 2019-01-16 10:02:47 UTC
I have this bug since last year November. It never resolved. Updating through apt or other means works fine.
I kinda find it disgusting. The software updater should be top priority, folks.

SOFTWARE VERSIONS
Operating System: KDE Neon, updated daily.
KDE Framework Version: 5.54.0
Qt: 5.11.2
Discover: 5.14.5
Comment 48 Andras 2019-01-16 14:39:23 UTC
Created attachment 117488 [details]
reinstalled plasma-discover with disabled update button issue crashes at start

Oh for God's sake, you should expect promises from Microsoft maybe and call it disgusting after you paid thousands of dollars for their faulty software. Don't be rude, it's not that paid service even if you're donating. Yes, these systems also works only if users are satisfied however you shouldn't use here such a wording above because there is a lot developers who works for free after they working hours. Anyways it's a bug tracking system not a service for claims. Still won't work, report, done.

Yes, plasma-discover still doesn't work under 5.54 KDE Frameworks. I tried to reinstall it and since then, it crashes every time I try to open it. I place the result for that crash here if it helps with this bug maybe. Let me know if I should open a new case for that, thanks.
Comment 49 Rex Dieter 2019-01-16 14:40:42 UTC
Yes, sepearate issues (like crashess) should have separate bugs.  thanks.
Comment 50 lega99 2019-01-16 19:57:55 UTC
(In reply to Andras from comment #48)
> Created attachment 117488 [details]
> reinstalled plasma-discover with disabled update button issue crashes at
> start
> 
> Oh for God's sake, you should expect promises from Microsoft maybe and call
> it disgusting after you paid thousands of dollars for their faulty software.
> Don't be rude, it's not that paid service even if you're donating. Yes,
> these systems also works only if users are satisfied however you shouldn't
> use here such a wording above because there is a lot developers who works
> for free after they working hours. Anyways it's a bug tracking system not a
> service for claims. Still won't work, report, done.
> 
> Yes, plasma-discover still doesn't work under 5.54 KDE Frameworks. I tried
> to reinstall it and since then, it crashes every time I try to open it. I
> place the result for that crash here if it helps with this bug maybe. Let me
> know if I should open a new case for that, thanks.

I did not see anyone writing about Microsoft. I do not understand what Microsoft has to do with this problem. I do not understand how Microsoft is currently blamed because the problem is not resolved. All that was requested from the diagnostic and repair data was delivered.
Comment 51 Nate Graham 2019-01-16 21:15:34 UTC
We know that it doesn't work. We know that this sucks. We're trying to fix it, and we're investigating what happened to let it get this way in the first place.
Comment 52 Andras 2019-01-16 21:21:39 UTC
(Not in reply but a note related to lega99 from comment #50 that I'm sorry)
I tried. Actually I was about to explaining things in the hope that redundant rows will decrease however what happened is that what usually happens in similar situations, it fell on deaf ears so I write this because I'm sorry I also increased the number of utterly unnecessary lines.
Comment 53 Wyatt Childers 2019-01-17 15:54:52 UTC
I'm on KDE Neon, the package updates for Discover 5.14.90 seem to have fixed this issue. 

Though, I'm not totally sure if it's Discover 5.14.90 that fixed this, or that I had to reinstall `neon-desktop` after pkcon update, well, pretty much purged my system of plasma.
Comment 54 lega99 2019-01-17 17:45:47 UTC
(In reply to Wyatt Childers from comment #53)
> I'm on KDE Neon, the package updates for Discover 5.14.90 seem to have fixed
> this issue. 
> 
> Though, I'm not totally sure if it's Discover 5.14.90 that fixed this, or
> that I had to reinstall `neon-desktop` after pkcon update, well, pretty much
> purged my system of plasma.

Discover 5.14.90
discover 2.1.2-8
hardware identification system

plasma-discover 5.14.5-0xneon+18.04+bionic+build35
Utility for browsing, installing and removing software

neon-desktop
KDE neon Plasma Desktop system 4+p18.04+git20181030.2058

Operating System: KDE neon 5.14
Издање КДЕ Плазме: 5.14.5
Издање КуТ‑а: 5.11.2
Издање Радних оквира КДЕ‑а: 5.54.0
Врста ОС‑а: 64‑битно
Процесори: 6 × AMD FX(tm)-6100 Six-Core Processor
Меморија: 7,7 GiB РАМ‑а

Let's be precise and we do not make a mess.
Discover and plasma-discover are 2 different programs. What version of Neon distribution do you have, I use the regular version
Comment 55 lega99 2019-01-18 00:52:36 UTC
(In reply to Wyatt Childers from comment #53)
> I'm on KDE Neon, the package updates for Discover 5.14.90 seem to have fixed
> this issue. 
> 
> Though, I'm not totally sure if it's Discover 5.14.90 that fixed this, or
> that I had to reinstall `neon-desktop` after pkcon update, well, pretty much
> purged my system of plasma.

Discover 5.14.90
discover 2.1.2-8
hardware identification system

plasma-discover 5.14.5-0xneon+18.04+bionic+build35
Utility for browsing, installing and removing software

neon-desktop
KDE neon Plasma Desktop system 4+p18.04+git20181030.2058

Operating System: KDE neon 5.14
Издање КДЕ Плазме: 5.14.5
Издање КуТ‑а: 5.11.2
Издање Радних оквира КДЕ‑а: 5.54.0
Врста ОС‑а: 64‑битно
Процесори: 6 × AMD FX(tm)-6100 Six-Core Processor
Меморија: 7,7 GiB РАМ‑а

Let's be precise and we do not make a mess.
Discover and plasma-discover are 2 different programs. What version of Neon distribution do you have, I use the regular version


Now I found you are using an unstable version and there is a source called discovery
KDE Plasma 5.14.90, Beta Release
Comment 56 Valter Mura 2019-01-19 08:29:47 UTC
Ok, after having updated to Plasma 5.14.90 / Frameworks 5.54.0 / Qt 5.11.2 *and with* Kernel 4.15.0.38, now the Update button *is working again*

*KDE neon Developer Edition (Stable)*

Thanks for the efforts to solve it
Comment 57 Nate Graham 2019-01-21 19:32:37 UTC
Dug a bit. Turns out this also needed a fix in Discover itself (https://cgit.kde.org/discover.git/commit/?id=7f6caf385809ce8c8087d8e56e9f3c6bd8c9170a) which unfortunately only went into Plasma 5.15.

So the current state is:

Upcoming Plasma 5.15.x with KDE Frameworks 5.54 or newer: working
Released Plasma 5.14.5 with KDE Frameworks 5.54 or newer: broken

Unfortunately Plasma 5.14 has exhausted its typical buxfix releases, i.e. there will be no 5.14.6.

I am investigating our options for 5.14.5 users. Meanwhile, distros can cherry-pick https://cgit.kde.org/discover.git/commit/?id=7f6caf385809ce8c8087d8e56e9f3c6bd8c9170a until we figure something out.
Comment 58 Nate Graham 2019-01-21 19:45:13 UTC
For anyone hitting this problem, please let me know if you can fix it by deleting /etc/xdg/cgcicon.knsrc on your system.
Comment 59 Patrick Silva 2019-01-21 20:07:51 UTC
(In reply to Nate Graham from comment #58)
> For anyone hitting this problem, please let me know if you can fix it by
> deleting /etc/xdg/cgcicon.knsrc on your system.

Such file does not exist on my system.
Comment 60 Nate Graham 2019-01-21 20:10:20 UTC
Darn. I guess for you it's caused by another one of those files, not that one.

I guess we can rule out deleting that file as a magic bullet workaround. :(
Comment 61 lega99 2019-01-21 20:23:48 UTC
I have this file on the system but deleting this file does not solve the problem. I did the rename file, I added the extension .old
Comment 62 lega99 2019-01-21 22:13:00 UTC
(In reply to Nate Graham from comment #57)

> 
> Upcoming Plasma 5.15.x with KDE Frameworks 5.54 or newer: working
> Released Plasma 5.14.5 with KDE Frameworks 5.54 or newer: broken
> 
> Unfortunately Plasma 5.14 has exhausted its typical buxfix releases, i.e.
> there will be no 5.14.6.
We are waiting for the 5.15.x, unfortunately I think it's a bad policy to gain new Neon distribution users. Now you have not specified a deadline when you can expect a new version.
Comment 63 Nate Graham 2019-01-21 22:17:11 UTC
Not sure what you mean. Our schedules are public, available at https://community.kde.org/Schedules/.
Comment 64 Andras 2019-01-22 02:33:09 UTC
(In reply to Nate Graham from comment #58)
Maybe it's late but I also don't have cgcicon.knsrc file in given directory however I tried cgcgtk3.knsrc and cgctheme.knsrc also, issue still persist. Let me now if there are any other suspicious files as possible culprit and erasing them can resolve this or something, thanks.
Comment 65 lega99 2019-01-22 09:03:58 UTC
(In reply to Nate Graham from comment #63)
> Not sure what you mean. Our schedules are public, available at
> https://community.kde.org/Schedules/.

Thanks for the link, now I know :)
Comment 66 lega99 2019-01-22 09:24:30 UTC
(In reply to Andras from comment #64)
> (In reply to Nate Graham from comment #58)
> Maybe it's late but I also don't have cgcicon.knsrc file in given directory
> however I tried cgcgtk3.knsrc and cgctheme.knsrc also, issue still persist.
> Let me now if there are any other suspicious files as possible culprit and
> erasing them can resolve this or something, thanks.

I have cgcgtk3.knsrc, i have cgcicon.knsrc, cgctheme.knsrc, colorschemes.knsrc, comic.knsrc. I did the rename cgcgtk3.knsrc and cgcicon.knsrc to the .old and restart machine.
Nothing happened, I think these suggestions are just a noise in trying to change something. :)
Comment 67 Gabor Körber 2019-01-22 09:58:37 UTC
I do not have that file either, only the ones for gtk3 and gtk2 themes.

Thank you very much Nate, and all helpers, for the good news however, I suppose I personally can wait until next release. 

As for the "non tech user" basic functionality like upgrades are theoretically quite crucial, even if it might look like a minor feat, so it is unfortunate it can't be fixed upstream; however, since that user would not be able to install the upgrade anyway, as his button does not work, I guess it makes little difference :)

Will confirm once the fix takes effect.
Comment 68 Nate Graham 2019-01-30 14:23:30 UTC
If anyone here is experiencing this issue in Plasma 5.14.5 and has the ability to compile from source and test a patch, could that person/those persons try building Discover from the Plasma/5.14 branch with this commit reverted: https://cgit.kde.org/discover.git/commit/?h=Plasma/5.14&id=2bd91b93357318c4f7dd96b2f6e7a07dd74494c8

I have a hunch that this commit caused the issue by making a pre-existing issue much worse. We've fixed the pre-existing issue in Plasma 5.15, but that's no help for 5.14 users, so reverting this commit might be the best alternative.

Could I get some volunteers to help test this theory?
Comment 69 lega99 2019-01-30 23:02:06 UTC
(In reply to Nate Graham from comment #68)


I would compile, but I do not know. I tried to compile the last corrected correction but I failed. I worked in a way that Dr.Calsav Ilic showed me when I successfully compiled a correction of the holidays in the Serbian calendar. Now it can not be compiled in this way. A new plasma is coming out in 12 days, we waited for the first updates, failed, we are waiting for a new plasma, says Aldin in the cartoon: patience Siago
Comment 70 Nate Graham 2019-01-30 23:06:29 UTC
The stakes are a good bit higher than just you not being able to use Discover for 12 more days: the next version of Debian Stable is going to ship with Plasma 5.14.5, which means Discover 5.14.5, which means that all the Debian users are going to be exposed to this issue if we can't provide a hotfix. That's why I'm asking for testing--so we can know if the proposed fix works.



I will reiterate my call for testing: if anyone here is experiencing this issue in Plasma 5.14.5 and has the ability to compile from source and test a patch, could that person/those persons try building Discover from the Plasma/5.14 branch with this commit reverted: https://cgit.kde.org/discover.git/commit/?h=Plasma/5.14&id=2bd91b93357318c4f7dd96b2f6e7a07dd74494c8
Comment 71 Patrick Silva 2019-01-30 23:11:56 UTC
The problem persists on my system but unfortunately I don't know how to compile source code reverting a commit. :(
Comment 72 lega99 2019-01-31 00:56:20 UTC
(In reply to Nate Graham from comment #70)
> The stakes are a good bit higher than just you not being able to use
> Discover for 12 more days: the next version of Debian Stable is going to
> ship with Plasma 5.14.5, which means Discover 5.14.5, which means that all
> the Debian users are going to be exposed to this issue if we can't provide a
> hotfix. That's why I'm asking for testing--so we can know if the proposed
> fix works.
I am a retired but I remember when Kali Distribution users were begging to be allowed to work with Dolphin as root, they were rejected, as we all know Kali is based on Debian. Then Kali users got advice from Plasma developer to do it themselves.
Comment 73 Wyatt Childers 2019-01-31 01:15:19 UTC
(In reply to lega99 from comment #72)
> (In reply to Nate Graham from comment #70)
> > The stakes are a good bit higher than just you not being able to use
> > Discover for 12 more days: the next version of Debian Stable is going to
> > ship with Plasma 5.14.5, which means Discover 5.14.5, which means that all
> > the Debian users are going to be exposed to this issue if we can't provide a
> > hotfix. That's why I'm asking for testing--so we can know if the proposed
> > fix works.
> I am a retired but I remember when Kali Distribution users were begging to
> be allowed to work with Dolphin as root, they were rejected, as we all know
> Kali is based on Debian. Then Kali users got advice from Plasma developer to
> do it themselves.

What?

> The stakes are a good bit higher than just you not being able to use
> Discover for 12 more days: the next version of Debian Stable is going to
> ship with Plasma 5.14.5, which means Discover 5.14.5, which means that all
> the Debian users are going to be exposed to this issue if we can't provide a
> hotfix. That's why I'm asking for testing--so we can know if the proposed
> fix works.

Unfortunately I can't, no longer have the issue as I got the updated packages from neon developer edition.

> The problem persists on my system but unfortunately I don't know how to compile source code reverting a commit. :(

Do you know how to compile from source? If it's just the reverting a commit part, that's relatively simple. You just go to the directory where you've got a copy of the source code and run `git revert <commit>` or in this case `git revert 2bd91b93357318c4f7dd96b2f6e7a07dd74494c8`.
Comment 74 Nate Graham 2019-01-31 03:01:40 UTC
(In reply to lega99 from comment #72)
> (In reply to Nate Graham from comment #70)
> I remember when Kali Distribution users were begging to
> be allowed to work with Dolphin as root, they were rejected
You have old information. I fixed that last year: Bug 387974

For anyone who wants to give this a shot, we have fairly good documentation: https://community.kde.org/Get_Involved/development

It's not that much more than this:

mkdir -p ~/kde
cd ~/kde
git clone git://anongit.kde.org/kdesrc-build.git
cd kdesrc-build
kdesrc-build --initial-setup
- Ubuntu/Kubuntu/Neon: sudo apt build-dep plasma-discover
- Fedora: sudo dnf builddep plasma-discover
- Arch & openSUSE: can't remember, sorry
kdesrc-build discover --include-dependencies
cd ~/kde/src/*/*/discover
git checkout plasma/5.14
kdesrc-build discover --resume-from discover
source ~/kde/build/*/*/discover/prefix.sh
plasma-discover
Comment 75 Andras 2019-01-31 05:00:25 UTC
(In reply to Nate Graham from comment #74)
(Ignore, not question but I hove to note what is it that some still assumes this place is a miserable playground? So ridiculous LMAO.)
It's nothing serious, I write this because it's just so absurd that I'd gladly try to build it as you kindly described although believe it or not, for 5 hours already http://archive.neon.kde.org/user currently isn't available. Obviously the server is down, unbelievable. Anyhow I'll try later. Also thank you for the guidance.

"E: The repository 'http://archive.neon.kde.org/user bionic Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details."

Let me know if it's possibly not the server but something locally on my (two) system though.
Comment 76 Andras 2019-01-31 05:24:24 UTC
Also at kdesrc-build --initial-setup I got

Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/(\${ <-- HERE MODULE})|(\$MODULE\b)/ at /usr/bin/kdesrc-build line 4759.

Let me know how should I proceed.
Comment 77 lega99 2019-01-31 08:18:12 UTC
(In reply to Nate Graham from comment #74)
> (In reply to lega99 from comment #72)

> You have old information. I fixed that last year: Bug 387974
> 
I does not want a political discussion, I have not written anything now, I wrote about the past time. It was begged by people who work like pen testers and not black hackers. I know well when it's enabled Dolphin to run in root mode in Kali. I offered to compile, I wrote that I do not know, because the method I worked with previously did not work. Debian users will have to stand up and have Synaptic, apt, Appper, Muon while Debina does not get the correct Discovery. Great respect for the deceased author Debian, it's the first distribution I've ever heard of in my life. Otherwise, I managed the most modern computer center in Europe with the then most modern mainframe machines that did not work in Linux, after which I managed the IT department and designed the information system of the municipal administration. All the best and I wish you success :)
Comment 78 lega99 2019-01-31 09:21:49 UTC
I tried to compile but there is a damaged package or a non-existent package and I do not know how to solve it

dragan@Neon-MS-7693:~$ sudo apt-get clean
dragan@Neon-MS-7693:~$ mkdir -p ~/kde
dragan@Neon-MS-7693:~$ cd ~/kde
dragan@Neon-MS-7693:~/kde$ git clone git://anongit.kde.org/kdesrc-build.git
Cloning into 'kdesrc-build'...
remote: Counting objects: 8838, done.
remote: Compressing objects: 100% (3852/3852), done.
remote: Total 8838 (delta 5598), reused 7145 (delta 4527)
Receiving objects: 100% (8838/8838), 3.07 MiB | 10.07 MiB/s, done.
Resolving deltas: 100% (5598/5598), done.
dragan@Neon-MS-7693:~/kde$ cd kdesrc-build
dragan@Neon-MS-7693:~/kde/kdesrc-build$ kdesrc-build --initial-setup
given is experimental at /usr/bin/kdesrc-build line 877.
when is experimental at /usr/bin/kdesrc-build line 878.
when is experimental at /usr/bin/kdesrc-build line 884.
when is experimental at /usr/bin/kdesrc-build line 893.
when is experimental at /usr/bin/kdesrc-build line 898.
when is experimental at /usr/bin/kdesrc-build line 902.
given is experimental at /usr/bin/kdesrc-build line 2181.
when is experimental at /usr/bin/kdesrc-build line 2182.
when is experimental at /usr/bin/kdesrc-build line 2183.
when is experimental at /usr/bin/kdesrc-build line 2184.
given is experimental at /usr/bin/kdesrc-build line 4110.
when is experimental at /usr/bin/kdesrc-build line 4111.
when is experimental at /usr/bin/kdesrc-build line 4112.
when is experimental at /usr/bin/kdesrc-build line 4113.
when is experimental at /usr/bin/kdesrc-build line 4114.
when is experimental at /usr/bin/kdesrc-build line 4115.
when is experimental at /usr/bin/kdesrc-build line 4116.
Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/(\${ <-- HERE MODULE})|(\$MODULE\b)/ at /usr/bin/kdesrc-build line 4759.
dragan@Neon-MS-7693:~/kde/kdesrc-build$ sudo apt build-dep plasma-discover
Читам спискове пакета... Урађено
Читам спискове пакета... Урађено
Правим стабло међузависности       
Читам информацију о стању... Урађено
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) libkf5kdelibs4support-dev:amd64 < none -> 5.54.0-0xneon+18.04+bionic+build20 @un uN Ib >
Broken libkf5kdelibs4support-dev:amd64 Зависи on libssl-dev:amd64 < none | 1.1.0g-2ubuntu4.3 @un uH >
  Considering libssl-dev:amd64 1 as a solution to libkf5kdelibs4support-dev:amd64 0
  Holding Back libkf5kdelibs4support-dev:amd64 rather than change libssl-dev:amd64
Investigating (1) builddeps:plasma-discover:amd64 < none -> 1 @un puN Ib >
Broken builddeps:plasma-discover:amd64 Зависи on libkf5kdelibs4support-dev:amd64 < none | 5.54.0-0xneon+18.04+bionic+build20 @un uH > (>= 5.18.0~)
  Considering libkf5kdelibs4support-dev:amd64 0 as a solution to builddeps:plasma-discover:amd64 9998
    Reinst Failed early because of libssl1.1:amd64
    Reinst Failed because of libssl-dev:amd64
  Considering libkf5kdelibs4support-dev:amd64 0 as a solution to builddeps:plasma-discover:amd64 9998
  Considering libkf5kdelibs4support-dev:amd64 0 as a solution to builddeps:plasma-discover:amd64 9998
  Considering libkf5kdelibs4support-dev:amd64 0 as a solution to builddeps:plasma-discover:amd64 9998
  Considering libkf5kdelibs4support-dev:amd64 0 as a solution to builddeps:plasma-discover:amd64 9998
  Considering libkf5kdelibs4support-dev:amd64 0 as a solution to builddeps:plasma-discover:amd64 9998
Done
Не могу да инсталирам неке пакете. Ово може значити да сте
захтевали немогућу ситуацију или да користите нестабилну
дистрибуцију у којој неки тражени пакети нису направљени
још увек или су премештени са списка.
Следеће информације могу помоћи решавању проблема:

Следећи пакети имају незадовољене међузависности:
 builddeps:plasma-discover : Зависи: libkf5kdelibs4support-dev (>= 5.18.0~) али неће бити инсталиран
E: Не могу да исправим проблеме, задржали сте оштећене пакете.
Comment 79 Gabor Körber 2019-01-31 09:42:03 UTC
I had no problems with installing the packages, however, as András, my main issue was that it got stuck at kdesrc-build --initial-setup and also at kdesrc-build discover --include-dependencies:

Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/(\${ <-- HERE MODULE})|(\$MODULE\b)/ at /usr/bin/kdesrc-build line 4759.

which leads to ~/kde/src not existing, so i can't continue.

Nate, did your step-by-step guide include ignoring that one commit? as i do not really see that in particular.

I am happy to test this otherwise, i will try to restrain myself from upgrading apt too frequently, so I have some packages in the queue. Otherwise I AM a bit puzzled the release policies do not allow bugfix releases to be included into an older release branch, but I am also pretty sure, the deb folks can do their own hotfix packages, given the fix is in some branch / diff / sth.
Comment 80 Rik Mills 2019-01-31 09:48:07 UTC
(In reply to Nate Graham from comment #68)
> If anyone here is experiencing this issue in Plasma 5.14.5 and has the
> ability to compile from source and test a patch, could that person/those
> persons try building Discover from the Plasma/5.14 branch with this commit
> reverted:
> https://cgit.kde.org/discover.git/commit/?h=Plasma/5.
> 14&id=2bd91b93357318c4f7dd96b2f6e7a07dd74494c8

Hi Nate & all.

Might take me a day or 2, but I can likely build some discover .deb packages for Neon user edition in a Neon chroot/pbuilder env with that patch/revert applied, then place the .debs somewhere where people can grab them. Would that be helpful if I can make that work?

Note: I can see the issue in Neon user edition iso, but cannot replicate in Kubuntu 18.10 backports build of 5.14.5
Comment 81 Dan Leinir Turthra Jensen 2019-01-31 09:53:22 UTC
> Hi Nate & all.
> 
> Might take me a day or 2, but I can likely build some discover .deb packages
> for Neon user edition in a Neon chroot/pbuilder env with that patch/revert
> applied, then place the .debs somewhere where people can grab them. Would
> that be helpful if I can make that work?

  That would be very handy, yes! Sooner, of course, is better, but definitely be good to be able to have more people be able to test it out :)
Comment 82 lega99 2019-01-31 10:37:41 UTC
libkf5kdelibs4support-dev depends on the libssl-dev,
libssl-dev not installed
If I try to install libssl-dev it requires to destroy 
the regular version of libssl1.1 (= 1.1.0g-2ubuntu4.3) 
and instead install this libssl1.1 (= 1.1.0h-2)
This can be a continuous game of dependent packages.
Comment 83 Rik Mills 2019-01-31 18:02:19 UTC
(In reply to Dan Jensen from comment #81)
> > Hi Nate & all.
> > 
> > Might take me a day or 2, but I can likely build some discover .deb packages
> > for Neon user edition in a Neon chroot/pbuilder env with that patch/revert
> > applied, then place the .debs somewhere where people can grab them. Would
> > that be helpful if I can make that work?
> 
>   That would be very handy, yes! Sooner, of course, is better, but
> definitely be good to be able to have more people be able to test it out :)

I have placed the built .debs on my ubuntu members webspace:

http://people.ubuntu.com/~rikmills/debs/plasma-discover/

They have been built in a clean pbuilder chroot using the official Neon repos and build packaging, with just a single patch added to revert the commit Nate was interested in testing.
Comment 84 Nate Graham 2019-01-31 18:05:28 UTC
Thanks so much Rik!
Comment 85 Andrés R. 2019-01-31 18:07:51 UTC
Hi! Tried compiling following nNate's instructions and the buttons do appear and function as they should. Neon User edition. https://i.imgur.com/z8ObMlz.png
Comment 86 Nate Graham 2019-01-31 18:14:47 UTC
The good news is that you successfully compiled Discover! The bad news is that you compiled the 5.15 version, which we know has the fix. You need to compile the 5.14 version + patch. Right after you do `git checkout plasma/5.14`, do this:

- git revert 2bd91b93357318c4f7dd96b2f6e7a07dd74494c8
- kdesrc-build --resume-from discover
- Then source prefix.sh and run plasma-discover like you already did

...Or just use Rik's package. :)
Comment 87 Thomas Pfeiffer 2019-01-31 22:19:46 UTC
I can confirm that the patched build fixes the problem for me.
Comment 88 Gabor Körber 2019-02-01 09:01:18 UTC
I can also confirm, that Rik's packages fix the issue for me in 5.14.5
Comment 89 lega99 2019-02-01 09:11:35 UTC
I can also confirm, that Rik's packages fix the issue for me in 5.14.5
Comment 90 Andras 2019-02-02 02:30:14 UTC
Probably I did something wrong or my system is awkward compromised somehow but for me it won't work, in short there are dependency issues. I hope it's only for me and it's really solved basically, I use mainly other other stuff to upgrade anyway.
Comment 91 lega99 2019-02-02 08:40:41 UTC
(In reply to Andras from comment #90)
> Probably I did something wrong or my system is awkward compromised somehow
> but for me it won't work, in short there are dependency issues. I hope it's
> only for me and it's really solved basically, I use mainly other other stuff
> to upgrade anyway.

The problem of addiction is solved by the command sudo apt install -f. First of all, copy all .deb files that have been locked on the net to a separate directory, position themselves on the directory where the files are corrected, type sudo dpkg -i plasma-discover *, the system will tell you that some files are missing, type sudo apt install -f
Comment 92 Andras 2019-02-03 19:52:20 UTC
It wasn't what simple comment #91. Anyhow it'd be awesome if sudo apt install -f would all the addictions :)
I made several other steps to solve my system's issues also related to this https://bugs.kde.org/show_bug.cgi?id=402328 such as fwupdmgr refresh/fwupdmgr update. Now, apparently it works for me too.
Comment 93 Dan Leinir Turthra Jensen 2019-02-05 13:02:14 UTC
(In reply to Rik Mills from comment #83)
> (In reply to Dan Jensen from comment #81)
> > > Hi Nate & all.
> > > 
> > > Might take me a day or 2, but I can likely build some discover .deb packages
> > > for Neon user edition in a Neon chroot/pbuilder env with that patch/revert
> > > applied, then place the .debs somewhere where people can grab them. Would
> > > that be helpful if I can make that work?
> > 
> >   That would be very handy, yes! Sooner, of course, is better, but
> > definitely be good to be able to have more people be able to test it out :)
> 
> I have placed the built .debs on my ubuntu members webspace:
> 
> http://people.ubuntu.com/~rikmills/debs/plasma-discover/
> 
> They have been built in a clean pbuilder chroot using the official Neon
> repos and build packaging, with just a single patch added to revert the
> commit Nate was interested in testing.

If i could be an absolute pest and ask you to rebuild the package, this time directly from the 5.14 branch, without reverting that commit, but ensuring that you do include the most recent commit to said branch, i would be most grateful.

This is an attempt to ensure that we don't end up in the situation that no-longer-reverted commit is supposed to fix, at the cost of a slight increase in startup time, and hopefully that patch alone should do the trick. The differential revision for the patch is https://phabricator.kde.org/D18724 for those who want to keep up with that, or want to try and build it themselves.
Comment 94 lega99 2019-02-06 10:26:01 UTC
Discovei registers 13 update files, and when the opening has 11 update files, yesterday was the same situation
Comment 95 lega99 2019-02-06 12:47:05 UTC
Created attachment 117870 [details]
Notification of updates

Notification of updates
Comment 96 lega99 2019-02-06 12:49:51 UTC
Created attachment 117871 [details]
Discover program

Discover program
Comment 97 zhustec 2019-02-06 13:24:11 UTC
Same issues here, 

Operating System: Arch Linux 
KDE Plasma Version: 5.14.5
Qt Version: 5.12.1
KDE Frameworks Version: 5.54.0
Kernel Version: 4.20.6-arch1-1-ARCH
OS Type: 64-bit
Processors: 4 × Intel® Core™ i7-6500U CPU @ 2.50GHz
Memory: 15.6 GiB of RAM
Comment 98 lega99 2019-02-06 15:17:27 UTC
Missing update button in discoveri,update is not even started and discoveri does not work.
506 notification for the new update
506 file discoveri
Operating System: Kali GNU/Linux 2019.1
KDE Plasma Version: 5.14.3
Qt Version: 5.11.2
KDE Frameworks Version: 5.51.0
Kernel Version: 4.19.0-kali1-amd64
OS Type: 64-bit
Processors: 6 × AMD FX(tm)-6100 Six-Core Processor
Memory: 7.7 GiB of RAM

apt update
apt upgrade
After update, Discoveri update button not hidden
Operating System: Kali GNU/Linux 2019.1
KDE Plasma Version: 5.14.5
Qt Version: 5.11.3
KDE Frameworks Version: 5.54.0
Kernel Version: 4.19.0-kali1-amd64
OS Type: 64-bit
Processors: 6 × AMD FX(tm)-6100 Six-Core Processor
Memory: 7.7 GiB of RAM
Comment 99 Rik Mills 2019-02-06 15:44:43 UTC
(In reply to Dan Jensen from comment #93)
> If i could be an absolute pest and ask you to rebuild the package, this time
> directly from the 5.14 branch, without reverting that commit, but ensuring
> that you do include the most recent commit to said branch, i would be most
> grateful.
> 
> This is an attempt to ensure that we don't end up in the situation that
> no-longer-reverted commit is supposed to fix, at the cost of a slight
> increase in startup time, and hopefully that patch alone should do the
> trick. The differential revision for the patch is
> https://phabricator.kde.org/D18724 for those who want to keep up with that,
> or want to try and build it themselves.

debs can be found here:

http://people.ubuntu.com/~rikmills/debs/plasma-discover-fix/

Built as before, but now instead with a patch applying that commit to the pristine 5.14.5 tarball source.
Comment 100 Nate Graham 2019-02-06 16:05:18 UTC
(In reply to Rik Mills from comment #99)
> debs can be found here:
> 
> http://people.ubuntu.com/~rikmills/debs/plasma-discover-fix/
> 
> Built as before, but now instead with a patch applying that commit to the
> pristine 5.14.5 tarball source.
Thanks so much, Rik.

Please test this, everyone!
Comment 101 Nate Graham 2019-02-06 16:23:01 UTC
With that latest build, here's what you're testing: if both buttons are grayed out, wait for more than one minute. After that, one or both of them should be enabled again.

Thereafter it should work.
Comment 102 lega99 2019-02-06 16:24:49 UTC
(In reply to Nate Graham from comment #100)
> (In reply to Rik Mills from comment #99)
> > debs can be found here:
> > 
> > http://people.ubuntu.com/~rikmills/debs/plasma-discover-fix/
> > 
> > Built as before, but now instead with a patch applying that commit to the
> > pristine 5.14.5 tarball source.
> Thanks so much, Rik.
> 
> Please test this, everyone!

Uf, it hurts my head, I have now installed the update from the attached link and Dicover has no buttons yet, and there are 3 update files. The number of files in the notification and the program itself is the same
Comment 103 lega99 2019-02-06 17:09:13 UTC
I have nothing to test, update 3 files myself with pkcon update. While there were 3 file updates, I started the program Discover, immediately appeared the names of files and sizes in the Discover program. The number of files in the notification was identical in the program. After that, I wait for 3 minutes for sure, or even more, and there is no button that allows the update.
Comment 104 Andras 2019-02-06 17:18:49 UTC
Created attachment 117899 [details]
Discover crashed after few minutes with deb packages from comment #99

#102 get some advil then and relax instead. Otherwise I also tried to restart my system and it won't work on my side either. Moreover it crashed after a minute or so and I placed the bug report here, ignore if it's useless. Thanks for all the hard work so far! Obviously I know nothing however it seems something just still not clear what could be the actual problem really. So let me know if there is any possible option to help by simple user with back trace or anything.
Comment 105 Andras 2019-02-06 18:11:59 UTC
Who SORRY wait, it happened right after the installation only. Now after a while it works like a charm. Interesting. I don't what's happening but sorry if previous info of mine is misleading.
Comment 106 Patrick Silva 2019-02-12 17:05:17 UTC
Bug persists after upgrade to Plasma 5.15.
Can anyone else confirm?

Operating System: Arch Linux 
KDE Plasma Version: 5.15.0
KDE Frameworks Version: 5.55.0
Qt Version: 5.12.1
Comment 107 lega99 2019-02-13 10:12:30 UTC
(In reply to Patrick Silva from comment #106)
> Bug persists after upgrade to Plasma 5.15.
> Can anyone else confirm?
> 
> Operating System: Arch Linux 
> KDE Plasma Version: 5.15.0
> KDE Frameworks Version: 5.55.0
> Qt Version: 5.12.1

I did an upgrade to 5.15.0 plasma, but with the command pkcon. Now I'm waiting for an update to come up so that I can check if it works properly
Comment 108 lega99 2019-02-13 17:50:05 UTC
(In reply to Patrick Silva from comment #106)
> Bug persists after upgrade to Plasma 5.15.
> Can anyone else confirm?
> 
> Operating System: Arch Linux 
> KDE Plasma Version: 5.15.0
> KDE Frameworks Version: 5.55.0
> Qt Version: 5.12.1

Discoveri works OK?
Operating System: KDE neon 5.14
KDE Plasma Version: 5.15.0
KDE Frameworks Version: 5.55.0
Qt Version: 5.12.0
Comment 109 Patrick Silva 2019-02-13 17:56:28 UTC
Thanks.
Here bug persists when I start plasma using my main user account,
but Discover works as expected when I use another user account.
Comment 110 Andras 2019-02-13 19:25:29 UTC
(In reply to Patrick Silva from comment #109)
Did you tried $ rm ~/.config/discoverrc && rm -R ~/.cache/discover or something similar standard solution for this?
Comment 111 Patrick Silva 2019-02-13 19:38:19 UTC
(In reply to Andras from comment #110)
> Did you tried $ rm ~/.config/discoverrc && rm -R ~/.cache/discover or
> something similar standard solution for this?

I tried your commands right now.
Unfortunately the bug persists.
Comment 112 lega99 2019-02-13 21:55:29 UTC
(In reply to Patrick Silva from comment #109)
> Thanks.
> Here bug persists when I start plasma using my main user account,
> but Discover works as expected when I use another user account.

I use the Manjaro and there is no update yet. It's not clear to me why you use Discoveri in Arch sistem when there is Octopi. I tried Discoveri from my account and work ok. I have 2 of the same versions, one is new on Btrfs file system and the other is on ext4 and it is updated from Ubuntu base 16.04 to 18.04.
Comment 113 Patrick Silva 2019-02-13 22:05:13 UTC
I use Discover to help improve it :(
While Discover is still broken, I use command line to update my system.
Comment 114 lega99 2019-02-13 22:49:52 UTC
(In reply to Patrick Silva from comment #113)
> I use Discover to help improve it :(
> While Discover is still broken, I use command line to update my system.

Manjaro is Arch only with a GUI installer, when I have a problem I solved it by reading Arch wiki. I have no offer in Aur so I can install Discoveri
Comment 115 Nate Graham 2019-02-14 16:01:36 UTC
(In reply to Patrick Silva from comment #111)
> I tried your commands right now.
> Unfortunately the bug persists.

Does `rm ~/.config/atticarc` help at all?
Comment 116 Patrick Silva 2019-02-14 16:09:02 UTC
(In reply to Nate Graham from comment #115)
> Does `rm ~/.config/atticarc` help at all?
yes, Discover is finally working again! \o/
Comment 117 Ionut Adrian Ciolan 2019-02-15 15:42:01 UTC
It does, i posted this solution yesterday https://forum.kde.org/viewtopic.php?f=309&t=155987#p410788 after few hours of trial and error. For me it worked.
Comment 118 lega99 2019-02-15 17:52:20 UTC
(In reply to Ionut Adrian Ciolan from comment #117)
> It does, i posted this solution yesterday
> https://forum.kde.org/viewtopic.php?f=309&t=155987#p410788 after few hours
> of trial and error. For me it worked.

https://forum.kde.org/viewtopic.php?f=309&t=155987#p410866
Comment 119 Ionut Adrian Ciolan 2019-02-16 11:18:27 UTC
(In reply to lega99 from comment #118)
> https://forum.kde.org/viewtopic.php?f=309&t=155987#p410866

I don't really get what i should be looking for.
Comment 120 lega99 2019-02-16 12:43:59 UTC
(In reply to Ionut Adrian Ciolan from comment #119)
> (In reply to lega99 from comment #118)
> > https://forum.kde.org/viewtopic.php?f=309&t=155987#p410866
> 
> I don't really get what i should be looking for.

Sorry, deaf phones, you sent this https://bugs.kde.org/show_bug.cgi?id=399981#c117 where you are invited to the link on forum, i have also posted what's written there.
Comment 121 gcjuan 2019-02-19 14:55:02 UTC
The solution mentioned on comment 117 (https://bugs.kde.org/show_bug.cgi?id=399981#c117) worked also for me.

Just delete ~/.config/atticarc (backup it with "cp atticarc{,.bak}" if you want). This fixed my Discover updates button issue on KDE neon 5.15 and now I'm able to press all buttons and to select/deselect the updates check boxes.