Public bug reported:

I had a distribution upgrade crash when I was trying to upgrade from
18.04 to 19.10 and a .crash was generated. I didn't want to report it
from the system which crashed so I ran apport (to do the data
collection) and saved the information in the report. I then copied it
over to another system which is running Ubuntu 19.04 and I could not
report the crash as I received the following crash.

 $ ubuntu-bug tmp/_usr_bin_do-release-upgrade.0.crash      
Traceback (most recent call last):
  File "/usr/share/apport/apport-gtk", line 597, in <module>
    app.run_argv()
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 704, in run_argv
    self.run_crash(self.options.crash_file, False)
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 291, in run_crash
    if not self.report and not self.load_report(report_file):
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 1375, in load_report
    self.report.load(f, binary='compressed')
  File "/usr/lib/python3/dist-packages/problem_report.py", line 144, in load
    block = base64.b64decode(line)
  File "/usr/lib/python3.7/base64.py", line 87, in b64decode
    return binascii.a2b_base64(s)
binascii.Error: Incorrect padding

I've attached the problematic crash file, although I don't really think
it is the crash file that is the issue.

** Affects: apport (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: disco

** Attachment added: "_usr_bin_do-release-upgrade.0.crash"
   
https://bugs.launchpad.net/bugs/1833795/+attachment/5272236/+files/_usr_bin_do-release-upgrade.0.crash

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833795

Title:
  unable to report an 18.04 crash from a 19.04 system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1833795/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to