** Changed in: whoopsie-preferences (Ubuntu)
Assignee: (unassigned) = Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1412719
Title:
wait-for-state restarts whoopsie
This bug was fixed in the package whoopsie-preferences - 0.14
---
whoopsie-preferences (0.14) vivid; urgency=medium
* Now use service status (upstart and systemd) to notify if crash reporting
is enabled (LP: #1412719)
* Default file for whoopsie settings (only used for
Fixed, I added as well Michael's upstart job enhancement in this upload
(even if that doesn't fix the real issue, still a nice addition). Didn't
merge into upstream trunk as I don't have access right, but Brian would
merge them back.
** Changed in: upstart
Status: Confirmed = Invalid
**
This bug was fixed in the package whoopsie - 0.2.47
---
whoopsie (0.2.47) vivid; urgency=medium
[ Didier Roche ]
* Remove /etc/default/whoopsie conffile and avoid upgrade prompt:
(LP: #1431432)
- debian/whoopsie.maintscript: get it removed on upgrade
-
** Branch linked: lp:ubuntu/vivid-proposed/whoopsie
** Branch linked: lp:ubuntu/vivid-proposed/whoopsie-preferences
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1412719
Title:
wait-for-state
** Also affects: whoopsie-preferences (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1412719
Title:
wait-for-state restarts whoopsie every 30sec
** Branch linked: lp:~mjblenner/whoopsie/whoopsie
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1412719
Title:
wait-for-state restarts whoopsie every 30sec
To manage notifications about this bug
@didrocks, I see this bug on my laptop. Ping me if you want testing or
info.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1412719
Title:
wait-for-state restarts whoopsie every 30sec
To manage
Tail of dmesg..
[ 4517.664355] init: wait-for-state (whoopsienetwork-manager) main process
(7481) terminated with status 100
[ 4517.720627] init: whoopsie main process (7492) terminated with status 1
[ 4517.720645] init: whoopsie main process ended, respawning
** Attachment added: full dmesg
@Steve: I think I understand what happens.
On package upgrade, if the job is disabled, then, there is an upstart .override
file written to disable it and so, that behavior shouldn't be triggered. I
guess this case happens currently if you disable through ubuntu-control-center
after a new
Michael, agree that 'started' is the wrong thing to look for and has
probably caused a few confusing things through the years since wait-for-
state has been in use. I think the patch should be merged.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: whoopsie (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1412719
Title:
wait-for-state restarts whoopsie every 30sec
To manage notifications
** Changed in: upstart (Ubuntu)
Importance: Undecided = High
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Status: New = Confirmed
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
** Changed in:
The second part of the patch proposed to upstart's wait-for-state job is
reasonable, but has nothing to do with the behavior shown here. And the
first part of the patch is wrong. It's not appropriate to change the
default wait-for-state behavior that other packages are relying on.
This is a regression introduced in the last whoopsie upload in vivid.
Prior to this, the upstart job included deliberate handling in
/etc/init/whoopsie.conf to ensure that if whoopsie were disabled in the
config, the job would be stopped without triggering upstart's respawn
behavior. Assigning
Looking at man 8 init, there is no job state started, so having
WAIT_STATE=started is exactly equal to WAIT_STATE=foobar, since they
both don't exit.
So you may as well change it to something sensible.
Also, the reason that whoopsie exits as soon as it is respawned is that
there is already
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: upstart (Ubuntu)
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/1412719
Title:
The attachment Fix for wait-for-state seems to be a patch. If it
isn't, please remove the patch flag from the attachment, remove the
patch tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
This patch changes the defaults for wait-for-state.conf to something
sensible for WAIT_STATE.
** Patch added: Fix for wait-for-state
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1412719/+attachment/4302214/+files/wait_fix.patch
** Tags added: trusty
--
You received this bug
19 matches
Mail list logo
