Can the affected please run
apport-collect 1979412
If that only works for the original reporter, you can attach
apport-bug --save /tmp/report.log chromium-browser
Also possibly useful would be to know if there is something in journalctl around the time of the crash:
journalctl -r | head -n 1000
And finally, Chromium has a logging mode:
chromium --enable-logging=stderr --v=1 |& tee chromium-stderr.log
You can then attach chromium-stderr.log.
Can the affected please run
apport-collect 1979412
If that only works for the original reporter, you can attach
apport-bug --save /tmp/report.log chromium-browser
Also possibly useful would be to know if there is something in journalctl around the time of the crash:
journalctl -r | head -n 1000
And finally, Chromium has a logging mode:
chromium --enable- logging= stderr --v=1 |& tee chromium-stderr.log
You can then attach chromium- stderr. log.