[Bug 1389357] Re: whoopsie reuses CRASH_DB_IDENTIFIER on next run

Launchpad Bug Tracker 1389357 at bugs.launchpad.net
Thu Oct 8 11:26:57 UTC 2015


This bug was fixed in the package whoopsie - 0.2.49

---------------
whoopsie (0.2.49) wily; urgency=medium

  [ Evan Dandrea ]
  * Helper to create recoverable problem reports. Thanks Ted Gould!

  [ Brian Murray ]
  * Switch build-depends from transitional libgcrypt11-dev to libgcrypt20-dev.
    Thanks to Robert Ancell.
  * Only publish the CRASH_DB_IDENTIFIER on the file system if it was not
    set via an environmental variable. (LP: #1389357)

 -- Brian Murray <brian at ubuntu.com>  Wed, 07 Oct 2015 10:09:03 -0700

** Changed in: whoopsie (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1389357

Title:
  whoopsie reuses CRASH_DB_IDENTIFIER on next run

Status in whoopsie package in Ubuntu:
  Fix Released

Bug description:
  On Vivid, Ubuntu 15.04, I observed the following behavior.

  bdmurray at blacklightning:~/Downloads$ sudo stop whoopsie
  [sudo] password for bdmurray: 
  whoopsie stop/waiting
  bdmurray at blacklightning:~/Downloads$ sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com CRASH_DB_IDENTIFIER=deadbeefbd89cc5da1f045978a550ad4b38782c1390ccd8c265c5ddc803be1d8bc0d0d5657350ce06c611975d77dac5a28db5e78921476be5430e0b6c1a44dfd APPORT_REPORT_DIR=/var/crash/ whoopsie -f
  [11:07:17] Using lock path: /var/crash/whoopsie_lock
  [11:07:18] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/39
  [11:07:18] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/39
  [11:07:18] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/39
  [11:07:18] online
  bdmurray at blacklightning:~/Downloads$ sudo cat /var/lib/whoopsie/whoopsie-id 
  deadbeefbd89cc5da1f045978a550ad4b38782c1390ccd8c265c5ddc803be1d8bc0d0d5657350ce06c611975d77dac5a28db5e78921476be5430e0b6c1a44dfd
  bdmurray at blacklightning:~/Downloads$ sudo start whoopsie
  whoopsie start/running, process 9083
  bdmurray at blacklightning:~/Downloads$ sudo cat /var/lib/whoopsie/whoopsie-id 
  deadbeefbd89cc5da1f045978a550ad4b38782c1390ccd8c265c5ddc803be1d8bc0d0d5657350ce06c611975d77dac5a28db5e78921476be5430e0b6c1a44dfd

  Notice, how the same CRASH_DB_IDENTIFIER was used by whoopsie when
  starting up, rather than calculating the system identifier. This may
  lead to crashes being reported under the wrong system-identifier if
  people switch from setting the environmental variable to just running
  whoopsie.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1389357/+subscriptions



More information about the foundations-bugs mailing list