Comment 59 for bug 1282542

I'm on Mist 17.1 (didn't know there was a 17.2 - I'll have to go take a peek!)

I am disturbed by the repeated comments, both here and other places, that describe this error as a "nuisance".

Unfortunately, I am not a developer so my ability to investigate (fork) such-and-so is painfully limited. However, I *am* a user with at least a moderate amount of "clue", and I like to keep an eye on my logs as well as the messages that occur when I perform updates.

With respect to myself, (and I am sure this is true for many others as well), when I see *ANY* error message that has the word "CRITICAL**" in it, I naturally assume that something has balled-up in a non-trivial way, and it places my system at (at least) severe risk of something drastic happening.

As a QA engineer of some years standing, if I was testing a product, and it threw a "CRITICAL**" error - even if mistaken - I would flag it as at least a Sev-2, (High, but not critical), bug simply based on the violently scary message it presents. With respect to release, I would also rank it as a Severity-2 priority, (must-fix, ASAP), due to the message.

I fully understand - from the development point-of-view - this bug may be a "nuisance" bug, (pissy message, but no real crisis), but the vast majority of us are *NOT* developers, and having "nuisance" bugs flagged as "CRITICAL**" is potentially dangerous., since it tends to dull the user's vigilance - "Oh, another "CRITICAL" bug? Must be another bogus message. . . . since my system *seems* to be OK. . . . ."

Please, please, please re-think the priority and severity of this bug. It may be trivial to *YOU*, but I can absolutely assure you that it is *NOT* trivial to the rest of us.\

What say ye?

Jim (JR)