apport does not depend on gdb so it's possible, even likely, that gdb is
not installed on the system reporting the crash. Subsequently,
report.add_gdb_info will fail and the docstring indicates that this
should "Raises ... OSError if calling gdb fails" however the docstring
is currently a liar perhaps because of a change I made. Regardless this
should be sorted out. Here's the Traceback:

Traceback (most recent call last):
  File "/usr/share/apport/whoopsie-upload-all", line 162, in <module>
    stamps = collect_info()
  File "/usr/share/apport/whoopsie-upload-all", line 112, in collect_info
    res = process_report(r)
  File "/usr/share/apport/whoopsie-upload-all", line 79, in process_report
  File "/usr/lib/python3/dist-packages/apport/", line 713, in 
    gdb_cmd, environ = self.gdb_command(rootdir, gdb_sandbox)
  File "/usr/lib/python3/dist-packages/apport/", line 1580, in 
    assert os.path.exists(executable)

** Changed in: apport (Ubuntu)
       Status: New => Triaged

** Changed in: apport (Ubuntu)
   Importance: Undecided => High

** Also affects: apport (Ubuntu Disco)
   Importance: High
       Status: Triaged

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.


To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to