[VROC] Ledmon couldn't be run with latest libsgutils2-2 package - ubuntu 22.04
Bug #1960921 reported by
Kinga Tanska
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ledmon (Ubuntu) |
Fix Released
|
Undecided
|
Woodrow Shen |
Bug Description
In Ubuntu 22.04 new version of package libsgutils2-2 is used (1.46). Earlier, for Ubuntu 20.04, libsgutils2-2 with 1.44 version was used.
This package is dependency of ledmon. Installation of ledmon and libsgutils2-2 packages completes successfully, but ledmon couldn't be started with error message:
ubuntu@ubuntu:~$ sudo ledmon --all
ledmon: error while loading shared libraries: libsgutils2-
Probably ledmon should be recompiled with newer package version.
description: | updated |
description: | updated |
summary: |
- Ledmon couldn't be run with latest libsgutils2-2 package - ubuntu 22.04 + [VROC] Ledmon couldn't be run with latest libsgutils2-2 package - ubuntu + 22.04 |
tags: |
added: vroc removed: jammy |
Changed in ledmon (Ubuntu): | |
status: | New → Incomplete |
assignee: | nobody → Woodrow Shen (woodrow-shen) |
To post a comment you must log in.
ledmon is synced from debian, and both Ubuntu and Debian are using the same version of ledmon from what I can tell:
bladernr@ galactica: ~$ rmadison ledmon updates/ universe | source, amd64, arm64, armhf, i386, powerpc, ppc64el 18.04.1 | bionic- updates/ universe | source, amd64, arm64, armhf, i386, ppc64el, s390x galactica: ~$ rmadison -u debian ledmon
ledmon | 0.79-0.2 | trusty/universe | source, amd64, arm64, armhf, i386, powerpc, ppc64el
ledmon | 0.79-0.2ubuntu0.1 | trusty-
ledmon | 0.79-2 | xenial/universe | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
ledmon | 0.79-2build1 | bionic/universe | source, amd64, arm64, armhf, i386, ppc64el, s390x
ledmon | 0.90-0ubuntu1~
ledmon | 0.94-1 | focal/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
ledmon | 0.95-1 | impish/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
ledmon | 0.95-1 | jammy/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
bladernr@
ledmon | 0.79-2 | oldoldoldstable | source, amd64, armel, armhf, i386
ledmon | 0.79-2 | oldoldstable | source
ledmon | 0.79-2+b2 | oldoldstable | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
ledmon | 0.90-0.1 | oldstable | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
ledmon | 0.95-1 | stable | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
ledmon | 0.95-1 | testing | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
ledmon | 0.95-1 | unstable | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
ledmon | 0.95-1 | unstable-debug | source
From what I can tell, it looks like @woodrow-shen is the debian maintainer for ledmon, so maybe he can help find a solution here.
Debian Import Freeze is next Thursday, Feb 24 so it'll be challenging to get this in before that time.