** Changed in: json-c (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878723
Title:
Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
T
Can we close this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878723
Title:
Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
To manage notifications about this bug go to:
ht
I have one instance that kernel panicked when it updated to
0.11-4ubuntu2.6 using auto updates.
However I cannot confirm that I actually rebooted that instance after
installing 0.11-4ubuntu2.5
So far none of my other instances panicked.
--
You received this bug notification because you are a me
@pandeyvinod.india: Can you help us try to understand why your instances are
still panicing?
- Do you have a copy of the panic string?
- How did you update to the 0.11-4ubuntu2.6 package?
- Did you reboot the instance after the package was installed?
- Have any of the instances that previously
This package update is still braking few instances hosted on AWS. it is
the same issue what we have seen in version "libjson-c2 0.11-4ubuntu2.1"
and impacted a lot of users.
same issue we are facing in the version libjson-c2/now 0.11-4ubuntu2.6
which caused few aws instances to go in kernel panic
This regression also broke other packages that depend on libjson-c
including the google-compute-engine-oslogin package in both 16.04 and
18.04 (at least). The rollback worked fine for the affected users.
However what we are trying to determine is if the update to the update
works or not. Is there a
@jfirebaugh: According to https://usn.ubuntu.com/4360-2/
The CVE fix is in the latest version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878723
Title:
Kernel panic when used with upstart after
@cnewcomer, can you clarify whether or not 0.11-4ubuntu2.5 contains the
(fixed) security update?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878723
Title:
Kernel panic when used with upstart afte
So if I'm on 20.04, not running Upstart and not experiencing kernel
panics, why would I want to install this 'update', re-introducing known
security issues? Why is it even pushed to systems running 20.04 without
Upstart?
--
You received this bug notification because you are a member of Ubuntu
Bug
Official site released the fix about bionic and xenial:
https://github.com/json-c/json-c/commit/f2b7d0b5cbd0eccf4fb3c1851ec0864952be1057
But above has a problem in lh_table_insert():
if t->count > INT_MAX * LH_LOAD_FACTOR then error return
Thank you.
--
You received this bug notification be
I have a Xenial server with upstart.
I've made patches for CVE-2020-12762.
See:
https://gist.github.com/h-yamamo/61161ea78f3bb7761e508ca531c7
Thank you.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-12762
--
You received this bug notification because you are a member of
FYI, version 0.11-4ubuntu2.5 was recently released. If you are still
experiencing this issue, the following steps will correct it:
1. Remove the postinst file from the affected package (version 0.11-4ubuntu2.1):
sudo rm /var/lib/dpkg/info/libjson-c2\:amd64.postinst
2. Re-run the package configure
> Just want to give a heads up that manual unpack followed by apt
install -f still crashes
as stated in comment 15, you MUST reboot between dpkg --unpack and apt
install -f.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
@cekkent: Did you reboot between the "dpkg --unpack..." and "sudo apt
install -f" steps?
That reboot is incredibly important since it switches out the init
process from the faulty one in 2.1 to the one in the 2.2 package.
The "apt install -f" is intended to run the pre/post install scripts for
th
Just want to give a heads up that manual unpack followed by apt install
-f still crashes, however the VM automatically rebooted this time
(instead of remaining dead) and I was able to proceed with usual apt
update afterwards with no further issues.
root@web1:~# curl -LO
https://launchpad.net/ubun
> Attempts to install libjson-c2_0.11-4ubuntu2.2_amd64.deb result in the
same lockup which can only be recovered with a hard reboot.
The 2.2 version includes only a revert of the patch, so for any system
affected by this, the currently-running init still contains the faulty
code, and the fixed pac
Also see https://github.com/json-c/json-c/pull/610/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878723
Title:
Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
To manage notificat
Sorry, I posted too soon.
Post reboot:
root@HMPBgZ:~# apt-get update
Fetched 51.5 kB in 1s (46.4 kB/s)
Reading package lists... Done
root@HMPBgZ:~# apt-get upgrade
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct
the problem.
root@HMPBgZ:~# dpkg -s libjson-c
This is not fixed with the updated package.
Attempts to install libjson-c2_0.11-4ubuntu2.2_amd64.deb result in the
same lockup which can only be recovered with a hard reboot.
root@HMPBgZ:~# dpkg -i libjson-c2_0.11-4ubuntu2.2_amd64.deb
(Reading database ... 154353 files and directories currently
** Changed in: json-c (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878723
Title:
Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
T
This bug was fixed in the package json-c - 0.12.1-1.3ubuntu0.2
---
json-c (0.12.1-1.3ubuntu0.2) bionic-security; urgency=medium
* Revert the security fixes and rebuild the old version (LP: #1878723)
-- Chris Coulson Fri, 15 May 2020
12:33:56 +0100
** Changed in: json-c (Ubuntu)
This bug was fixed in the package json-c - 0.11-4ubuntu2.2
---
json-c (0.11-4ubuntu2.2) xenial-security; urgency=medium
* Revert the security fixes and rebuild the old version (LP: #1878723)
-- Chris Coulson Fri, 15 May 2020
12:11:57 +0100
** Changed in: json-c (Ubuntu)
This bug was fixed in the package json-c - 0.13.1+dfsg-4ubuntu0.2
---
json-c (0.13.1+dfsg-4ubuntu0.2) eoan-security; urgency=medium
* Revert the security fixes and rebuild the old version (LP: #1878723)
-- Chris Coulson Fri, 15 May 2020
12:33:18 +0100
--
You received this bug
** Tags added: id-5ebe6d95d5ae066b83cac917
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878723
Title:
Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
To manage notifications abou
The updated packages just revert the security fixes which resolves this
immediate issue. Keeping the bug open though because we still want to
resolve the underlying issue so that we can republish an update with the
security fixes in it
** Changed in: json-c (Ubuntu)
Status: Fix Released =>
This bug was fixed in the package json-c - 0.13.1+dfsg-4ubuntu0.2
---
json-c (0.13.1+dfsg-4ubuntu0.2) eoan-security; urgency=medium
* Revert the security fixes and rebuild the old version (LP: #1878723)
-- Chris Coulson Fri, 15 May 2020
12:33:18 +0100
--
You received this bug
This bug was fixed in the package json-c - 0.13.1+dfsg-7ubuntu0.2
---
json-c (0.13.1+dfsg-7ubuntu0.2) focal-security; urgency=medium
* Revert the security fixes and rebuild the old version (LP: #1878723)
-- Chris Coulson Fri, 15 May 2020
12:31:48 +0100
** Changed in: json-c (Ub
Removed the broken version from the archive, and copied back the
previous version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878723
Title:
Kernel panic when used with upstart after 0.11-4ubuntu
** Changed in: json-c (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878723
Title:
Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
To
today's unattended upgrade killed a lot of our hosts running xenial +
upstart, please mark as critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878723
Title:
Kernel panic when used with upstar
Also ran into this. It looks like this bug got backported
https://github.com/json-c/json-c/issues/599. The upstream fix is this:
https://github.com/besser82/json-c/commit/7a4807fe0cdb1d9e20273c79762cbf54833aaae4
** Bug watch added: github.com/json-c/json-c/issues #599
https://github.com/json-c/
I also experienced this bug today. What seems to have happened is that
upstart init filled all of the memory on my machine while libjson-c2 was
updating, leading to oom-killer killing everything. The kernel panic
here would happen if oom-killer tries to act on init. After a reboot my
machine manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: json-c (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/1878723
Title:
Ker
33 matches
Mail list logo
