On Wed, 23 Dec 2020 16:00:59 +0100, H0Iger SchuIz wrote:

> paul lee  wrote:
>
>> sudo apt update sudo apt upgrade
>
> Did that, didn't help.
>
Obvious questions:

- what was written to /var/log/messages when you attempted to view a
  video with Chromium?

- does Firefox write the same set of messages to /var/log/messages?

These are, or should be, obvious because when something like this
happens, that's the first place to look when an application fails without
showing the detail of what went wrong: IMHO displaying an unexplained
error code doesn't count as 'showing what went wrong'.

As well looking in /var/log/messages you should also:

- look at any other logs in /var/log which carry the same 'last updated'
  timestamp as when the error occurred.

- take a look in the directory where Chromium and Firefox stash data in
  case they wrote anything useful there. In this case:

  - Google Earth writes crashlogs to ~/.googleearth/crashlogs

  - Firefox writes crashlogs to '~/.mozilla/firefox/Crash Reports'

  so its very likely that Chromium does something similar.

You can see the exact time to loog for in logs by causing the crashes
again, but this time after opening a console window and running the
command:

   sudo tail -f /var/log/messages

in it. This will show you the timestamped log messages as the error
actually occurs. When you're finished with it, stop 'tail' by typing Ctrl/
C in the console window.



--
--
Martin    | martin at
Gregorie  | gregorie dot org

--- SoupGate-Win32 v1.05