4

I have done this many times before and it has always worked so I don't know what the problem is now, I even had a look at this but still can't get it working. virt-manager had a crash, it created a .crash file in /var/crash, but it wasn't convenient at the time to file a report so I cancelled reporting it through the GUI.

However now I do want to report it so I have tried running:

sudo apport-cli -p virt-manager --crash-file=_usr_sbin_libvirtd.0.crash

I also tried it initially without specifying the -p option. But the same happens every time, when I answer this it just exits:

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (3.5 MB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): S

And nothing comes of it, the only seemingly noticeable change is that .upload and .uploaded files get created in the same location as the .crash file, but nothing actually comes of it. I have tried running it in a TTY, it would normally give me a URL to go to where it has uploaded the data to, but it just exists which is very odd and has never happened before.

So now I am at a loss of how to report it, I tried through the GUI, through the CLI... So how can I file this report on this crash with the .crash file? What am I doing wrong? I am running Ubuntu GNOME 16.04 with GNOME 3.20.

Information Update:

Just checked and found that both the .upload and the .uploaded files are completely blank.

Also, when running the above command I find that this is logged in my syslog:

Jul  5 21:01:43 <Computer-Name> whoopsie[834]: [21:01:43] Parsing /var/crash/_usr_sbin_libvirtd.0.crash.
Jul  5 21:01:43 <Computer-Name> whoopsie[834]: [21:01:43] Uploading /var/crash/_usr_sbin_libvirtd.0.crash.
Jul  5 21:01:45 <Computer-Name> whoopsie[834]: [21:01:45] Sent; server replied with: No error
Jul  5 21:01:45 <Computer-Name> whoopsie[834]: [21:01:45] Response code: 400
Jul  5 21:01:45 <Computer-Name> whoopsie[834]: [21:01:45] Server replied with:
Jul  5 21:01:45 <Computer-Name> whoopsie[834]: [21:01:45] Crash already reported.

1 Answers1

2

Just prior to Release Apport crashes opening a LP report is disabled. All Apport crash reports then go to a Db via whoopsie. In the current dev LP reports from crashes is turned back on a couple of months or so from the start of dev.

If you want to open a LP report in a Release version of Ubuntu then you'll need to use ubuntu-bug packagename.

Otherwise they only way in these cases is to re-enable LP reports in Apport, generally that's not appreciated though on occasion I'll do just that. But in order to do so do the following:

1. Run:

sudo vim /etc/apport/crashdb.conf

2. Add a # to the beginning of the 'problem_types': ['Bug', 'Package'], line in order to comment it out.

3. Save the changes and Apport should report bugs to LP as you requested.

Non-security-related bugs in a Release version should be first checked if they also exist in the current dev, if so the LP report should be against the dev package. That's the first step in a possible SRU (stable release update ), for the Release version.

doug
  • 17,212