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.
** Changed in: whoopsie (Ubuntu Quantal)
Status: Fix Committed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs,
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 e...@ubuntu.com Fri, 26 Jul 2013
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 e...@ubuntu.com Mon, 29 Jul
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 0x70334700 (LWP 6876)]
Program received signal SIGTRAP, Trace/breakpoint trap.
0x7758dc7f in g_logv () from
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.
** Tags added: verification-done-precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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: G_DEBUG=fatal-criticals gdb --args
whoopsie -f
r
bt full
And attach the output here. Thanks!
--
You received this bug notification
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)
** Description changed:
process_existing_files is supposed to fire every two hours. However,
because the function doesn't return a boolean value, glib stops
processing the two hour timeout event after the first run.
TEST CASE:
Terminal 1:
sudo stop whoopsie
- sudo
I tested this whoopsie version 0.2.15.1 from raring-proposed and
observed a second attempt to upload the crash.
** Tags added: verification-done-raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
** Branch linked: lp:ubuntu/quantal-proposed/whoopsie
** Branch linked: lp:ubuntu/raring-proposed/whoopsie
** Branch linked: lp:~ubuntu-branches/ubuntu/precise/whoopsie-daisy
/precise-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: whoopsie (Ubuntu Raring)
Status: Confirmed = Fix Committed
** Changed in: whoopsie (Ubuntu Quantal)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: whoopsie (Ubuntu Precise)
Status: Confirmed = Fix Committed
** Description changed:
process_existing_files is supposed to fire every two hours. However,
because the function doesn't return a boolean value, glib stops
processing the two hour timeout event after the
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 e...@ubuntu.com Fri, 26 Jul 2013 16:17:31 +0100
**
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: whoopsie (Ubuntu Raring)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205374
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: whoopsie (Ubuntu Quantal)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205374
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: whoopsie (Ubuntu Precise)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205374
** Also affects: whoopsie (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: whoopsie (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: whoopsie (Ubuntu Saucy)
Importance: Critical
Assignee: Evan Dandrea (ev)
Status: Confirmed
** Branch linked: lp:whoopsie
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205374
Title:
Only attempts to retry the existing crash reports once, after two
hours.
To manage notifications about
** Branch linked: lp:~ubuntu-branches/ubuntu/saucy/whoopsie/saucy-
proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205374
Title:
Only attempts to retry the existing crash reports once,
20 matches
Mail list logo
