[Bug 1991525] Re: vim.gtk3 won't run after 22.04 upgrade: “libpng12.so.0: cannot open shared object file”
Smylers
1991525 at bugs.launchpad.net
Wed Oct 5 10:19:45 UTC 2022
Thank you! The ldd output included:
libcairo-gobject.so.2 => /usr/local/lib/libcairo-gobject.so.2
(0x00007f9607200000)
It turns out that back in Ubuntu 16.04 we needed a newer libcairo to run
some external software (WeasyPrint), so libcairo 1.16.0 was installed
under /usr/local/. Deleting that makes vim.gtk work perfectly.
The libcairo now included in Ubuntu 22.04 is also version 1.16.0, but the Ubuntu-compiled one uses libpng16 (which still exists) rather than libpng12 (which doesn't).
Sorry for the incorrect bug report, and thank you for helping me to get
a working system.
** Changed in: vim (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1991525
Title:
vim.gtk3 won't run after 22.04 upgrade: “libpng12.so.0: cannot open
shared object file”
Status in vim package in Ubuntu:
Invalid
Bug description:
After upgrading a system running Ubuntu 20.04 to 22.04, vim.gtk3 no
longer runs:
$ vim.gtk3
vim.gtk3: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory
(vim.basic still runs fine).
These are the vim packages we have installed, and their versions:
vim:amd64/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
vim-common:all/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
vim-gtk3:amd64/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
vim-gui-common:all/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
vim-runtime:all/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
vim-tiny:amd64/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
Previously I did have a PPA of Vim installed from
http://ppa.launchpad.net/jonathonf/vim/ubuntu — but that has been
purged, and as you can see all the vim packages now installed are
official Ubuntu jammy versions.
libpng12 isn't in Ubuntu any more, so I think the problem is that vim
is trying to use it, not that it's missing.
Attached is strace output of the failure.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1991525/+subscriptions
More information about the foundations-bugs
mailing list