Only attempts to retry the existing crash reports once, after two hours.

Status changed to 'Confirmed' because the bug affects multiple users.

This bug was fixed in the package whoopsie - 0.2.16

---------------
whoopsie (0.2.16) saucy; urgency=low

  * Continue to process the existing crash reports every two hours, not
    just once after two hours (LP: #1205374).
 -- Evan Dandrea <email address hidden> Fri, 26 Jul 2013 16:17:31 +0100

Hello Evan, or anyone else affected,

Accepted whoopsie-daisy into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/whoopsie-daisy/0.1.33 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Evan, or anyone else affected,

Accepted whoopsie into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/whoopsie/0.2.7.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Evan, or anyone else affected,

Accepted whoopsie into raring-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/whoopsie/0.2.15.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

I tested this whoopsie version 0.2.15.1 from raring-proposed and observed a second attempt to upload the crash.

When trying to verify this on quantal in the terminal running whoopsie version 0.2.7.2 I see the following:

(whoopsie:5169) Glib-CRITICAL **: g_dir_open: assertion `path != NULL' failed

(whoopsie:5169) Glib-CRITICAL **: g_dir_read_name: assertion `dir != NULL' failed

(whoopsie:5169) Glib-CRITICAL **: g_dir_close: assertion `dir != NULL' failed

Hi Brian,

I can't see why this would happen. Could you do me a favour and run the following in your quantal environment:
sudo CRASH_DB_URL=http://localhost:6666 G_DEBUG=fatal-criticals gdb --args whoopsie -f
r
bt full

And attach the output here. Thanks!

tarting program: /usr/bin/whoopsie -f
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff0334700 (LWP 6876)]

Program received signal SIGTRAP, Trace/breakpoint trap.
0x00007ffff758dc7f in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#0 0x00007ffff758dc7f in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#1 0x00007ffff758de42 in g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x00007ffff7572c02 in g_dir_open () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3 0x0000000000403eda in process_existing_files (report_dir=0x0) at src/whoopsie.c:657
        dir = 0x0
        file = 0x0
        ext = 0x0
        upload_file = 0x0
        crash_file = 0x0
#4 0x00007ffff758763b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5 0x00007ffff7586ab5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#6 0x00007ffff7586de8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#7 0x00007ffff75871e2 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#8 0x0000000000402c41 in main (argc=1, argv=0x7fffffffe6b8) at src/whoopsie.c:908
        err = 0x0

Testing this with whoopsie version 0.1.33 on Ubuntu 12.04, I observed a second attempt to upload the .crash file related to bash.

This bug was fixed in the package whoopsie-daisy - 0.1.33

---------------
whoopsie-daisy (0.1.33) precise-proposed; urgency=low

  * Continue to process the existing crash reports every two hours, not
    just once after two hours (LP: #1205374).
 -- Evan Dandrea <email address hidden> Mon, 29 Jul 2013 17:16:42 +0100

This bug was fixed in the package whoopsie - 0.2.15.1

---------------
whoopsie (0.2.15.1) raring-proposed; urgency=low

  * Continue to process the existing crash reports every two hours, not
    just once after two hours (LP: #1205374).
 -- Evan Dandrea <email address hidden> Fri, 26 Jul 2013 16:15:42 +0100

quantal has seen the end of its life and is no longer receiving any updates. Marking the quantal task for this ticket as "Won't Fix".