Old crashdb.conf.d entries with bug_pattern_base (even if it is None) cause crash in apport.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Application Menu Indicator |
Invalid
|
Undecided
|
Unassigned | ||
Apport |
Fix Released
|
High
|
Martin Pitt | ||
Indicator Applet |
Invalid
|
Undecided
|
Unassigned | ||
apport (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
Natty |
Fix Released
|
High
|
Martin Pitt | ||
ubuntuone-client (Ubuntu) |
Opinion
|
Low
|
Unassigned | ||
Natty |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: apport
Right now ubuntuone-client in natty suffers from a broken unity library.
Upon adding the bugpattern to the bugpatterns.xml and testing it with test-local with positive results I found that apport reporting tool started to crash.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: apport-gtk 1.19-0ubuntu2
ProcVersionSign
Uname: Linux 2.6.38-5-generic x86_64
NonfreeKernelMo
Architecture: amd64
CrashReports:
600:1000:
600:1000:
Date: Tue Mar 8 20:45:37 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/share/
PythonArgs: ['/usr/
SourcePackage: apport
Title: apport-gtk crashed with KeyError in get_crashdb(): 'bug_pattern_url'
UpgradeStatus: Upgraded to natty on 2010-12-05 (93 days ago)
UserGroups: adm admin audio cdrom dialout libvirtd lpadmin mythtv plugdev sambashare
Changed in indicator-applet: | |
status: | New → Invalid |
Changed in indicator-appmenu: | |
status: | New → Invalid |
Changed in ubuntuone-client (Ubuntu): | |
assignee: | Roman Yepishev (rye) → nobody |
Changed in ubuntuone-client (Ubuntu): | |
status: | Triaged → Incomplete |
status: | Incomplete → Opinion |
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #625259, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.