[Quantal] Apport launching “AssertionError” when trying to report another bug.

Bug #1065291 reported by Martin Constantino–Bodin
22
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Apport
Confirmed
Medium
Unassigned

Bug Description

Hi,

I’m on Ubuntu Quantal and Compiz crashed. I thus launched Apport in console mode, choosing the option “save report file to send it later”. This worked well. The problem went when I tried to later send this bug repport as Apport crashed each time I tried to send this file.

Here is what I’m doing:
→ I’m typing “ubuntu-bug apport.compiz-core.jk9zbh.apport” in a terminal. Apport-gtk launches and shows me a window. I get those warning in the console, but I think they are not that important:
“Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 14: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 32: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 32: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 32: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 32: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 32: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 32: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 32: Having multiple <family> in <alias> isn't supported and may not works as expected”
→ If I click on the button “Show detail” (which is not written in English as my system is not set to this language, but that’s not the point), it works and show me all the informations I asked.
→ If I click on the “Continue” button, Apport crashes. Here what is writen in the console:
“Traceback (most recent call last):
  File "/usr/share/apport/apport-gtk", line 588, in <module>
    app.run_argv()
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 640, in run_argv
    self.run_crash(self.options.crash_file, False)
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 277, in run_crash
    self.restart()
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 854, in restart
    assert 'ProcCmdline' in self.report
AssertionError”
→ No Apport is launched to catch this crash of Apport (which I guess is better than a looping of Apport’s launches).

I did not know what to do so I declared this bug of Compiz manually in this page: https://bugs.launchpad.net/compiz/+bug/1065286
I’m sending in attachment the file “apport.compiz-core.jk9zbh.apport” generated by Apport the first time.
* Note that this file is not a bug repport generated against Apport * It’s the one that Apport generated against Compiz.

I hope my confuse explanations will help you understanding this bug. If you need any further informations, just ask!
Best,
Martin.

Revision history for this message
Martin Constantino–Bodin (martin-bodin) wrote :
Evan (ev)
Changed in apport:
importance: Undecided → Medium
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.