[Quantal] Apport launching “AssertionError” when trying to report another bug.
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.
“Fontconfig warning: "/etc/fonts/
Fontconfig warning: "/etc/fonts/
Fontconfig warning: "/etc/fonts/
Fontconfig warning: "/etc/fonts/
Fontconfig warning: "/etc/fonts/
Fontconfig warning: "/etc/fonts/
Fontconfig warning: "/etc/fonts/
Fontconfig warning: "/etc/fonts/
→ 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/
app.run_argv()
File "/usr/lib/
self.
File "/usr/lib/
self.restart()
File "/usr/lib/
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:/
I’m sending in attachment the file “apport.
* 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.
Changed in apport: | |
importance: | Undecided → Medium |
status: | New → Confirmed |