crash report crashes in 21.04+Mate

Bug #1915776 reported by kneedragon on 2021-02-16
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu MATE
Undecided
Unassigned
apport (Ubuntu)
Undecided
Unassigned

Bug Description

I downloaded an ISO for 21.04 + Mate, (daily build) installed in a VirtualBox. Quite happy with it, works well, but every boot it pops up a box of 'crash report' and 'can I report?' Watching the network traffic, nothing is getting reported and the crashes still happen.
I am looking for somebody I can email the last dozen lines or so of the boot-log to.

My personal email is <email address hidden>.
I would be very happy to help.

kneedragon (kneedragon1962) wrote :

...

Feb 16 15:07:56 ub-mate-21-04 kernel: [ 3690.866584] systemd-sysv-generator[4169]: SysV service '/etc/init.d/hddtemp' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
Feb 16 15:07:56 ub-mate-21-04 systemd[1]: /lib/systemd/system/plymouth-start.service:17: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Feb 16 15:07:56 ub-mate-21-04 systemd[1]: /lib/systemd/system/dbus.service:12: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Feb 16 15:07:56 ub-mate-21-04 systemd[1]: Stopping LSB: automatic crash report generation...
Feb 16 15:07:56 ub-mate-21-04 apport[4180]: * Stopping automatic crash report generation: apport
Feb 16 15:07:56 ub-mate-21-04 apport[4180]: ...done.
Feb 16 15:07:56 ub-mate-21-04 systemd[1]: apport.service: Succeeded.
Feb 16 15:07:56 ub-mate-21-04 systemd[1]: Stopped LSB: automatic crash report generation.
Feb 16 15:07:56 ub-mate-21-04 systemd[1]: Starting LSB: automatic crash report generation...
Feb 16 15:07:56 ub-mate-21-04 apport[4186]: * Starting automatic crash report generation: apport
Feb 16 15:07:56 ub-mate-21-04 apport[4186]: ...done.
Feb 16 15:07:56 ub-mate-21-04 systemd[1]: Started LSB: automatic crash report generation.
Feb 16 15:17:02 ub-mate-21-04 CRON[4885]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

Norbert (nrbrtx) on 2021-04-08
tags: added: hirsute
Brian Murray (brian-murray) wrote :

Could you provide a listing of the contents of the directory '/var/crash' e.g. "ls -lh /var/crash/". Thanks in advance!

mike@UB-mate-2104:~$ ls -lh /var/crash/
total 2.8M
-rw-r----- 1 mike whoopsie 2.8M Apr 3 15:23 _usr_bin_marco.1000.crash
mike@UB-mate-2104:~$
==================
Good morning.
I should perhaps add it stopped doing this about 2 or 3 days ago. Boots now
give a welcome screen and no dialogue box.

Thank you for following up. I don't think in 20+ years anybody's ever done
that before...

Mike.

On Fri, Apr 9, 2021 at 3:10 AM Brian Murray <email address hidden>
wrote:

> Could you provide a listing of the contents of the directory
> '/var/crash' e.g. "ls -lh /var/crash/". Thanks in advance!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1915776
>
> Title:
> crash report crashes in 21.04+Mate
>
> Status in Ubuntu MATE:
> New
> Status in apport package in Ubuntu:
> New
>
> Bug description:
> I downloaded an ISO for 21.04 + Mate, (daily build) installed in a
> VirtualBox. Quite happy with it, works well, but every boot it pops up a
> box of 'crash report' and 'can I report?' Watching the network traffic,
> nothing is getting reported and the crashes still happen.
> I am looking for somebody I can email the last dozen lines or so of the
> boot-log to.
>
> My personal email is <email address hidden>.
> I would be very happy to help.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-mate/+bug/1915776/+subscriptions
>

Brian Murray (brian-murray) wrote :

If the crash file were ready to be uploaded there would be a ".upload" file and after it is uploaded there will be a ".uploaded" file. You can force the process by running "ubuntu-bug /var/crash/_usr_bin_marco.1000.crash".

kneedragon (kneedragon1962) wrote :

That doesn't seem to be doing a great deal...
--------------
mike@UB-mate-2104:~$ "ubuntu-bug
> /var/crash/_usr_bin_marco.1000.crash
>
------------
Look, I'm far less worried about it than I was, because the dialogue box no
longer comes up every boot. I don't know what changed, but something did,
in the last 3 days or so.

Thank you for getting back to me, but the 'issue' seems to have resolved
itself.

Mike

On Fri, Apr 9, 2021 at 9:25 AM Brian Murray <email address hidden>
wrote:

> If the crash file were ready to be uploaded there would be a ".upload"
> file and after it is uploaded there will be a ".uploaded" file. You can
> force the process by running "ubuntu-bug
> /var/crash/_usr_bin_marco.1000.crash".
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1915776
>
> Title:
> crash report crashes in 21.04+Mate
>
> Status in Ubuntu MATE:
> New
> Status in apport package in Ubuntu:
> New
>
> Bug description:
> I downloaded an ISO for 21.04 + Mate, (daily build) installed in a
> VirtualBox. Quite happy with it, works well, but every boot it pops up a
> box of 'crash report' and 'can I report?' Watching the network traffic,
> nothing is getting reported and the crashes still happen.
> I am looking for somebody I can email the last dozen lines or so of the
> boot-log to.
>
> My personal email is <email address hidden>.
> I would be very happy to help.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-mate/+bug/1915776/+subscriptions
>

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers