[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 notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sensible-utils in Ubuntu. https://bugs.launchpad.net/bugs/977526 Title: Manpage makes erroneous claim about BROWSER documentation Status in sensible-utils package in Ubuntu: Fix Released Status in sensible-utils package in Debian: Unknown Bug description: sensible-editor(1) (and other programs in sensible-utils) in the ‘SEE ALSO’ section of the manpagesays: Documentation of the EDITOR, VISUAL, PAGER, and BROWSER variables in environ(7) But environ(7) doesn't actually make any mention at all of BROWSER, so looking there is of little help in determining how to set the preferred browser, so that mention should be removed. What would be useful is to document that sensible-browser by default tries gnome-www-browser, x-www-browser, or www-browser (depending on whether it's running under Gnome, X, or neither), and so the browser choice can be set with update-alternatives(8). Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sensible-utils/+bug/977526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[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 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 Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[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 seems like something is the wrong version. Is there any way I can trace which library or packages is truing to load libpng12? Or a way of checking that all Vim's dependencies are at exactly the versions they should be for jammy? Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Incomplete 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[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 required. DNS was specified in /etc/network/interfaces, with dns-nameservers and dns-search lines. Booting brought up the network; /etc/resolve.conf was a symlink to /run/resolvconf/resolv.conf, which was presumably generated by resolvconf; the comments at the top seemed to be from /etc/resolvconf/resolv.conf.d/head. Name-servers could be displayed with systemd-resolve --status. Host-names could be resolved with dig @127.0.0.53. I don't know what was providing that (it just worked, so I didn't question it!), but networkd claimed not to be running: $ sudo systemctl status systemd-networkd ● systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; ve> Active: inactive (dead) Does that help? Are there any other details that would be useful? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1991658 Title: 22.04 upgrade left DNS broken, resolv.conf pointing at resolvconf Status in systemd package in Ubuntu: Incomplete Bug description: I upgraded a server from Ubuntu 20.04.x to 22.04.1. It had originally been installed as 16.04, and upgraded through all the LTS releases. Immediately after upgrade, DNS resolving wasn't working; no names could be resolved. • /etc/resolv.conf was pointing to /run/resolvconf/resolv.conf • That file said not to edit it by hand, gave 127.0.0.53 as the only name-server, and to run systemd-resolve --status to see details about the actual name-servers. • Running systemd-resolve said the command wasn't found. • man resolvconf gave the manual page for resolvectl, which said it had supplanted resolvconf and was only partially backwards compatible, when running systemd-resolved.service. • systemd-resolved didn't appear to be running. systemctl status systemd-networkd said it was dead. To get DNS working, I initially edited /etc/resolv.conf by hand to put our name-server's IP address in there. I then created a netplan config (this server predates netplan, and no previous upgrades had switched anything to use it) in /etc/netplan/eth0.yaml with the IP address and name-server config. netplan apply started a name-server on 127.0.0.53. /etc/resolv.conf was untouched; I removed the IP address I'd manually added and names continued to resolve. But that left /etc/resolv.conf still with the outdated message about systemd-resolve --status in it. I found /run/systemd/resolve/stub- resolv.conf so switched /etc/resolv.conf to symlink to that; it now has a comment to use resolvectl status, a command which actually exists. 1. It would have been preferable if upgrading Ubuntu LTS–LTS didn't break networking such that names no longer resolved. 2. If that breakage was inevitable from the set-up this server had, it would have been much better if the upgrader had detected that and declined to proceed with the upgrade — for instance by saying to switch to netplan and systemd-networkd first. 3. If the upgrade disables resolvconf, then the /etc/resolv.conf symlink should be switched to point to whatever its modern equivalent is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1991658/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[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 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.
** Affects: vim (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "strace of the failure"
https://bugs.launchpad.net/bugs/1991525/+attachment/5620716/+files/vim.gtk3.strace
** Description changed:
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.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
+ 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.
+ 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.
+ 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.
- Here's some strace output leading up to the failure:
-
- openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libwayland-client.so.0",
O_RDONLY|O_CLOEXEC) = 3
- read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 832) = 832
- newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=64776, ...},
AT_EMPTY_PATH) = 0
- close(3)= 0
- openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libXext.so.6", O_RDONLY|O_CLOEXEC)
= 3
- read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 832) = 832
- newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=81640, ...},
AT_EMPTY_PATH) = 0
- close(3)= 0
- openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libthai.so.0", O_RDONLY|O_CLOEXEC)
= 3
- read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 832) = 832
- newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=41152, ...},
AT_EMPTY_PATH) = 0
- close(3)= 0
- openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libpthread.so.0",
O_RDONLY|O_CLOEXEC) = 3
- read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 832) = 832
- newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=21448, ...},
AT_EMPTY_PATH) = 0
- close(3)= 0
- openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libpixman-1.so.0",
O_RDONLY|O_CLOEXEC) = 3
- read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 832) = 832
- newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=694448, ...},
AT_EMPTY_PATH) = 0
- close(3)= 0
- openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libfreetype.so.6",
O_RDONLY|O_CLOEXEC) = 3
- read(3,
[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 default doesn't apply. $ grep HISTFILESIZE ~/.bashrc HISTFILESIZE=2000 That's HISTFILESIZE, not HISTSIZE. They are different variables, to control different (albeit related) things. However, skel.bashrc does also set HISTSIZE, to 1000. But that doesn't make the manpage wrong. Ubuntu gives new users a HISTSIZE variable, but it's still the case that a user who removes that will get a default size of 500. So I think this is invalid. ** Changed in: bash (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1340511 Title: man page contains wrong default history size Status in “bash” package in Ubuntu: Invalid Bug description: man page contains wrong default history size Steps to reproduce: 1.$ man bash 2. Search for HISTSIZE (press /then type HISTSIZE and press ENTER) Actual result: Man page contains the text: --- HISTSIZE The number of commands to remember in the command history (see HISTORY below). The default value is 500. --- Expected result The default value is 2000. Additional information: $ wc -l ~/.bash_history 2000 /home/user/.bash_history $ grep HISTFILESIZE ~/.bashrc HISTFILESIZE=2000 $ apt-get source bash $ cd bash-4.2/ $ grep -nr HISTFILESIZE . ./debian/skel.bashrc:20:HISTFILESIZE=2000 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bash 4.2-5ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 Date: Fri Jul 11 11:41:58 2014 InstallationDate: Installed on 2014-02-18 (143 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Beta i386 (20130926) MarkForUpload: True SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1340511/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[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 running a shell script, yields error messages like: bash: error importing function definition for `BASH_FUNC_-' With a double-nested Bash, each error message is displayed twice. So far as I can tell the error message is spurious: the action function - is being imported correctly. But it's irritating to have the terminal clogged up with these messages, especially when just running utilities which I didn't even know were written in Bash. This is with bash 4.3-7ubuntu1.4. ** Affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1376688 Title: Punctuation-only functions give error messages in subshells Status in “bash” package in Ubuntu: New Bug description: 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 running a shell script, yields error messages like: bash: error importing function definition for `BASH_FUNC_-' With a double-nested Bash, each error message is displayed twice. So far as I can tell the error message is spurious: the action function - is being imported correctly. But it's irritating to have the terminal clogged up with these messages, especially when just running utilities which I didn't even know were written in Bash. This is with bash 4.3-7ubuntu1.4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1376688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[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. https://bugs.launchpad.net/bugs/1376688 Title: Punctuation-only functions give error messages in subshells Status in “bash” package in Ubuntu: New Bug description: 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 running a shell script, yields error messages like: bash: error importing function definition for `BASH_FUNC_-' With a double-nested Bash, each error message is displayed twice. So far as I can tell the error message is spurious: the action function - is being imported correctly. But it's irritating to have the terminal clogged up with these messages, especially when just running utilities which I didn't even know were written in Bash. This is with bash 4.3-7ubuntu1.4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1376688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
