I've seen the same 'couldn't get size' message several times on some computers in the past (but admittedly not for a long while, though). As long as there is no noticable effect on operation, you should consider it 'informational' and just live with it it. With some future update, it will probably go away.
You probably know this, but if you run journalctl -b you will see the journal messages generated on startup for the most recent boot. Lots of similar scary chatter in there, some even labeled with ERROR and WARNING. Sometimes some push through the splash barrier.
I just ran that on this computer looking for 'error' in the output:
Code:
[dmn@sydney ~]$ journalctl -b | grep -i error
Aug 02 06:26:45 sydney kernel: RAS: Correctable Errors collector initialized.
Aug 02 06:26:45 sydney kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20190509/psargs-330)
Aug 02 06:26:45 sydney kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20190509/psparse-529)
Aug 02 06:26:45 sydney kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20190509/psargs-330)
Aug 02 06:26:45 sydney kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20190509/psparse-529)
Aug 02 06:26:46 sydney snapd[569]: stateengine.go:108: state ensure error: Get https://api.snapcraft.io/api/v1/snaps/sections: dial tcp: lookup api.snapcraft.io: no such host
Aug 02 06:26:54 sydney lightdm[598]: Error opening audit socket: Protocol not supported
Aug 02 06:27:20 sydney pulseaudio[903]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
---and there is more----
None of this appeared on the screen on startup. Scary, but don't be too alarmed.
Bookmarks