Another posibility is to check whether there is already a crash report file. You can attach it to this bug report.
These files are in the /var/crash directory and their names contain path and name of the executable file which has crashed. In your case /usr/sbin/cupsd has crashed, so the name looks like:
/var/crash/_usr_sbin_cupsd.1000.crash
where the number is different with each crash (probably it is the process ID of the process which has crashed).
List the files with date
ls -l /var/crash/*cups*
and create a bug report with the newest file
apport-bug /var/crash/_usr_sbin_cupsd.1000.crash
or simply try whether the system automatically finds a crash report which fits to this bug:
Another posibility is to check whether there is already a crash report file. You can attach it to this bug report.
These files are in the /var/crash directory and their names contain path and name of the executable file which has crashed. In your case /usr/sbin/cupsd has crashed, so the name looks like:
/var/crash/ _usr_sbin_ cupsd.1000. crash
where the number is different with each crash (probably it is the process ID of the process which has crashed).
List the files with date
ls -l /var/crash/*cups*
and create a bug report with the newest file
apport-bug /var/crash/ _usr_sbin_ cupsd.1000. crash
or simply try whether the system automatically finds a crash report which fits to this bug:
apport-collect 1706052