Absence of updates is labelled a critical error in syslog
Bug #1830183 reported by
ALinuxUser
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Triaged
|
Low
|
Unassigned | ||
snapd (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
My syslog contains, regularly:
storehelpers.
That log entry is labelled 'critical' and I see the entry flash by when I shutdown the computer. Yet, this is hardly a critical problem or indeed a problem at all. What should happen is that at most an event logged as informational should occur.
Snapd 2.38+18.04
Linux Mint 19.1 Cinnamon
EDITED to fix a typo.
Changed in snapd: | |
importance: | Medium → Low |
tags: | added: papercut |
Changed in snapd (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Low |
description: | updated |
Changed in snapd: | |
status: | Incomplete → Triaged |
Changed in snapd (Ubuntu): | |
status: | Incomplete → Triaged |
To post a comment you must log in.
I agree this should not be a critical error in any way. It's just a side effect of, if I understand this correctly, how we interact with the journal.