This is a slightly different bug then bug 161226, as nagios2 is now terminated
when nagios2 reload is called.
It is again due to a bug in lsb-base. Below lines are the cause of the problem.
Any signal passed to killproc (from /lib/lsb/init-functions) is treated as
SIGTERM.
This bug in lsb-base
+1
tested in amd64 kvm VM.
with php5-recode 5.2.4-2ubuntu5 php recode-test.php segfaulted
with php5-recode 5.2.4-2ubuntu5.1 it printed Hello World!Hello World! without
any error message.
--
[SRU] recode function segfaults
https://bugs.launchpad.net/bugs/219528
You received this bug notification
Please note this is actually a bug in lsb, which doesn't properly handle
signals passed to killproc.
This has been fixed in Debian (lsb 3.2-12), so a merge of lsb will fix this in
Intrepid.
See bug 228460.
--
'/etc/init.d/nagios2 reload' causes nagios to exit (sends SIGTERM not SIGHUP)
+1
Created a dangling symlink (/var/www/index.html - /home/ubuntu/fake,
cat: /var/www/index.html: No such file or directory) and tried to
upgrade from gutsy to hardy. The upgrade failed with -proposed disabled
and succeeded with -proposed enabled. Tested in kvm VM.
--
package apache2.2-common
Public bug reported:
Binary package hint: qemu-kvm
On my karmic test system kvm has been kept back for some time now.
As this seems to be a potential problem for jaunty to karmic upgrades, I tested
an upgrade in a pbuilder chroot.
- start jaunty pbuilder
- install kvm
- install
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/33904688/XsessionErrors.txt
--
kvm is not updated in a jaunty to karmic upgrade
https://bugs.launchpad.net/bugs/454733
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
*** This bug is a duplicate of bug 455114 ***
https://bugs.launchpad.net/bugs/455114
** This bug has been marked a duplicate of bug 455114
builds uninstallable package 'kvm'
--
kvm is not updated in a jaunty to karmic upgrade
https://bugs.launchpad.net/bugs/454733
You received this bug
