Apport sees the username as a substring in bug report, and transforms it to the string 'username'

[Edward Donovan]

I was reporting a bug with apport, while logged in with the username "ed" on my local machine. Apport started automatically when a process crashed, and provided a title including the word "crashed".

The bug title that apport passed to Launchpad had "crashusername" in place of the word "crashed".

I was able to reproduce it.

I don't have time to look into the apport source, right now, to look at the parsing and substitution code that must be doing this. Maybe I can later. Thanks.

(I know, I know -- you will say I should just switch to a reasonable user name, like "george", or "Nebuchadnezzar", or "rumpelstiltskin899091". I'm set in my ways; maybe that's the problem.)

[Martin Pitt (pitti)]

Heh, another one of those.. Will fix, thanks for the report!

[Martin Pitt (pitti)]

Regression from previous upload, bumping to high.

[Martin Pitt (pitti)]

Fixed in trunk r2256.

[Edward Donovan (edward.donovan)]

Thanks so much. And what a speedy fix! :)

[Launchpad Janitor (janitor)]

This bug was fixed in the package apport - 2.0-0ubuntu1

---------------
apport (2.0-0ubuntu1) precise; urgency=low

  * New upstream release: This is the final 2.0 release, featuring the
    overhauled and simplified GUI, support for whoopsie-daemon, and
    client-side duplicate checking.
    - report.py, anonymize(): Only replace whole words, not substrings.
      (LP: #966562)
    - apport_python_hook.py: Fix filtering of
      org.freedesktop.DBus.Error.NoReply exceptions. (LP: #958575)
    - crashdb.py: When publishing the crash database, cut hash file names
      after quoting, to avoid that the quoting causes them to become too long.
      (LP: #968070) This also uncovered that known() did not actually find any
      signature which contained an URL-quoted character, therefore breaking
      client-side duplicate checking in a lot of cases. Double-quote the file
      name now, as urlopen() unquotes it.
    - Add a new crash database option "problem_types" and a CrashDatabase
      method "accepts(report)". This can be used to stop uploading particular
      problem report types to that database. E. g. a distribution might decide
      to not get "Crash" reports any more after release. Document the new
      option in doc/crashdb-conf.txt.
    - ui.py: Do not upload a report if the crash database does not accept the
      report's type. This behaviour is not really correct, but necessary as
      long as we only support a single crashdb and have whoopsie hardcoded.
      Once we have multiple crash dbs, we need to not even present the data if
      none of the DBs wants the report. See LP #957177 for details.
      (LP: #968121)
    - ui.py: Do not short-circuit information collection if report already has
      a "DistroRelease" field, as the GUIs add that in some cases. Check for
      "Dependencies" instead. This fixes information collection for kernel
      problems (which now has a full GTK GUI test case). (LP: #968488)
  * Merge from trunk:
    - test_ui_gtk.py: Disable package hooks for the tests, as they might ask
      for sudo passwords and other interactive bits, and thus make the tests
      hang.
 -- Martin Pitt <email address hidden> Fri, 30 Mar 2012 12:38:02 +0200