https://bugs.kde.org/show_bug.cgi?id=407807
--- Comment #12 from davehill <daveh...@telus.net> --- (In reply to Nate Graham from comment #10) > Yeah, disappointing resolution from the PackageKit side. :/ > > Still, if PK won't work properly in this circumstance, there's nothing > Discover can do about it. You'll need to plead your case to the PK > maintainer or remove NM entirely. FWIW that's what we did in my last job > where I was supporting a lot of Linux boxes; if you're not using NM at all, > just get rid of it. I got this reply to my plea to reopen: Is there anything on the D-Bus interface that tells us to ignore NM? If you work out the library calls we need to do and open a PR I guess we can re-open this. So I'll dig around and see what I can find. Re: removal - yes, sure. I'm not chasing this for me but for the next poor soul who trips across this. It's not exactly obvious what's causing the error. Re: Discover (and Apper) - I agree. They could in theory I suppose trap the "whilst offline" error message and provide more detail, but that'd be as kludgy as can be - as Wikipedia says "clumsy, inelegant, inefficient, difficult to extend and hard to maintain" - so no. -- You are receiving this mail because: You are watching all bug changes.
