Having same error after boot. Checked log and the program listed chromium-browser with errors.
Removed Chromium-Browser and restarted. Again same error message.
Shutdown system, after boot still same error and log still listed Chromium as the app and errors same as the other posts on this thread.
Currently have a HP laptop Pavillion Dv6000 32bit. Ubuntu-Mate 18.04.2.
As a side note also have a System 76 laptop 64 bit with Ubuntu 18.04.2 installed and no errors with Chromium-Browser. Looks like Mate is the common OS involved.
Hopefully cause can be resolved!
Try opening /var/crash as superuser and deleting all the files within. I suspect that the errors previously reported will cease. Good luck all.
2 Likes
Thanks. That cleared the issue for me.
I would try it tomorrow. How do I open this crash folder as superuser?
Sorry for asking but Iām new to Linux.
I'm somewhat surprised...
To open a folder as a superuser (in MATE 18.04) use the following command - pkexec caja and then navigate to /var/crash (in this case.) Good luck Newhere.
Good news also from my side. When I turned on the system this morning, I was missing something ... the error message was gone.
I used pkexec caja in Terminal to access /var/crash. There was no lightdm log, and I deleted the Photomatix crash log file.
Whoever made that change, thanks for repairing it.
I 
my Ubuntu Mate.
1 Like
I got my problem back this morning:
ERROR: apport (pid 9154) Wed Jul 17 06:11:47 2019: called for pid 1129, signal 11, core limit 0, dump mode 2
ERROR: apport (pid 9154) Wed Jul 17 06:11:47 2019: not creating core for pid with dump mode of 2
ERROR: apport (pid 9154) Wed Jul 17 06:11:47 2019: executable: /usr/sbin/lightdm (command line "lightdm --session-child 13 16")
ERROR: apport (pid 9154) Wed Jul 17 06:11:47 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 9154) Wed Jul 17 06:11:47 2019: wrote report /var/crash/_usr_sbin_lightdm.0.crash
One question: Can a change of icons cause such error?
The only thing that rally changed yesterday was that I played around with a set called Obsidian. 20.04 will be released next year and my favourite NixOS icon set won't work since the changes in 19.04, so I have to get used to a new set.
I have exactly the same error like checkmate
So I tried what mdooley mentioned :
I removed the 2 files in /var/crash as superuser (root)
Result :
I got the same error again after rebooting ...
AND : Those 2 files were back again in /var/crash
Here is the last fragment of my apport.log :
ERROR: apport (pid 4031) Wed Jul 20 01:33:16 2022: called for pid 2814, signal 5, core limit 0, dump mode 1
ERROR: apport (pid 4031) Wed Jul 20 01:33:16 2022: executable: /opt/google/chrome/chrome (command line "/opt/google/chrome/chrome\ --enable-crashpad\ https://ubuntu-mate.community")
ERROR: apport (pid 4031) Wed Jul 20 01:33:16 2022: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 4031) Wed Jul 20 01:33:21 2022: wrote report /var/crash/_opt_google_chrome_chrome.1000.crash
ERROR: apport (pid 1103) Wed Jul 20 01:34:21 2022: called for pid 1090, signal 11, core limit 0, dump mode 1
ERROR: apport (pid 1103) Wed Jul 20 01:34:21 2022: executable: /usr/lib/cups/backend/gutenprint53+usb (command line "gutenprint53+usb")
ERROR: apport (pid 1103) Wed Jul 20 01:34:21 2022: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1103) Wed Jul 20 01:34:21 2022: wrote report /var/crash/_usr_lib_cups_backend_gutenprint53+usb.7.crash
P.S. : I also clicked "Report Problem", and my Ubuntu MATE 22.04 is brand new .