[Touch-packages] [Bug 977526] Re: Manpage makes erroneous claim about BROWSER documentation

This was fixed a decade ago, in sensible-utils 0.0.8, as documented in the resolution of Debian bug 567250, and confirmed in sensible-utils's changelog.gz entry, dated 2013 June 6th. ** Changed in: sensible-utils (Ubuntu) Status: Confirmed => Fix Released -- You received this bug

[Touch-packages] [Bug 1991525] Re: vim.gtk3 won't run after 22.04 upgrade: “libpng12.so.0: cannot open shared object file”

Thank you! The ldd output included: libcairo-gobject.so.2 => /usr/local/lib/libcairo-gobject.so.2 (0x7f960720) 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

[Touch-packages] [Bug 1991525] Re: vim.gtk3 won't run after 22.04 upgrade: “libpng12.so.0: cannot open shared object file”

> Can you make sure all of your packages are up to date? apt update and apt upgrade claim so. And: $ apt-show-versions | grep -v 'not installed\|uptodate' doesn't list any packages as being out of date. > it may be some dependency of vim that is out of date trying to read it. It certainly

[Touch-packages] [Bug 1991658] Re: 22.04 upgrade left DNS broken, resolv.conf pointing at resolvconf

I'm pretty sure it was set up however Ubuntu 16.04 installed it, followed by any changes made by the 16.04–18.04 and 18.04–20.04 upgrades. Those first 2 upgrade were seamless in terms of the networking working, so either they didn't make any changes or they updated things automatically as

[Touch-packages] [Bug 1991525] [NEW] vim.gtk3 won't run after 22.04 upgrade: “libpng12.so.0: cannot open shared object file”

Public bug reported: 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

[Touch-packages] [Bug 1340511] Re: man page contains wrong default history size

Man page contains the text: HISTSIZE The number of commands to remember in the command history (see HISTORY below). The default value is 500. I think that means that if HISTSIZE isn't set at all, then Bash will act as though HISTSIZE had been set to 500. If you have HISTSIZE set, then the

[Touch-packages] [Bug 1376688] [NEW] Punctuation-only functions give error messages in subshells

Public bug reported: I have Bash functions defined with punctuation-only names, such as - and .., which now give errors when starting nested shells. After a recent Shellshock patch, env shows these functions as having names like BASH_FUNC_-(), and starting a second Bash in some way, such as

[Touch-packages] [Bug 1376688] Re: Punctuation-only functions give error messages in subshells

Intentional temporary regression: http://lists.gnu.org/archive/html/bug- bash/2014-09/msg00256.html Sounds like an upstream fix will be forthcoming. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu.