severity 930168 important
tags 930168 moreinfo
Alexander Kernozhitsky - 12.06.19, 19:05:
> I just tried to install fresh Debian Buster on a VM and tried to
> reproduce the bug. It appears that Discover works fine on a clean
> As I mentioned before, I am able to reproduce this with AppStream
> metadata manually disabled in APT configs. So this may be the reason.
> Please lower the severity.
Thanks, Alexander. Doesn’t happen here either on a highly customized
Debian Sid installation.
P D, thank you for your report. "renders package unusable" is not the
right severity if the package is just unusable for you. It is the right
severity if it makes the package unusable on most of all Debian
installations. This is certainly not the case here.
So please do not use a release critical bug severity if it is not
Also please note that Kali Linux is not Debian GNU/Linux. So please
retest any issue you have with Kali Linux with a pure Debian GNU/Linux
install before reporting it here.
So please retest with a pure Debian GNU/Linux installation. If you
cannot reproduce the issue there, I'd close it.
Martin Steigerwald - 12.06.19, 22:01:
> Also please note that Kali Linux is not Debian GNU/Linux. So please
> retest any issue you have with Kali Linux with a pure Debian GNU/Linux
> install before reporting it here.
> So please retest with a pure Debian GNU/Linux installation. If you
> cannot reproduce the issue there, I'd close it.
If its reproducible on a Debian GNU/Linux installation even when it does
not happen all of the time, the bug will stay open of course.
In that case I kindly ask you to research upstream bug tracker for
similar issues. There has been a lot of bug fixes regarding discover
since version 5.14.5. So it would help if you could find the bug there if
its reported and if there is a fix for it, tell us about it. That way you
can help the understaffed Debian Qt/KDE team fix the bug by adding a patch
for the 5.14.5 version currently packaged in Debian.