[Touch-packages] [Bug 1843812] [NEW] apt info "please use the '-a' switch"
Public bug reported: When getting info about a package, I see a notice asking me to "Please use the '-a' switch", but the apt program does not accept an '-a' switch. Steps to reproduce: $ apt info docker.io ... N: There is 1 additional record. Please use the '-a' switch to see it $ apt -a info docker.io $ apt info -a docker.io $ apt info docker.io -a Expected outcome: same output as `apt info docker.io` but with the 1 additional record. Seen outcome: E: Command line option 'a' [from -a] is not understood in combination with the other options. Also seen: `apt info $pkg` gives the same output as `apt show $pkg` including the Notice message, but where `apt info -a $pkg` fails, `apt show -a $pkg` succeeds. Workaround: Use `apt show -a $pkg` instead. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: apt 1.8.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Sep 12 14:16:09 2019 InstallationDate: Installed on 2018-10-30 (316 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: apt UpgradeStatus: Upgraded to disco on 2019-04-18 (147 days ago) modified.conffile..etc.logrotate.d.apport: [modified] modified.conffile..etc.logrotate.d.apt: [modified] mtime.conffile..etc.logrotate.d.apport: 2018-12-13T12:13:33.355709 mtime.conffile..etc.logrotate.d.apt: 2018-12-13T12:13:41.355709 ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1843812 Title: apt info "please use the '-a' switch" Status in apt package in Ubuntu: New Bug description: When getting info about a package, I see a notice asking me to "Please use the '-a' switch", but the apt program does not accept an '-a' switch. Steps to reproduce: $ apt info docker.io ... N: There is 1 additional record. Please use the '-a' switch to see it $ apt -a info docker.io $ apt info -a docker.io $ apt info docker.io -a Expected outcome: same output as `apt info docker.io` but with the 1 additional record. Seen outcome: E: Command line option 'a' [from -a] is not understood in combination with the other options. Also seen: `apt info $pkg` gives the same output as `apt show $pkg` including the Notice message, but where `apt info -a $pkg` fails, `apt show -a $pkg` succeeds. Workaround: Use `apt show -a $pkg` instead. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: apt 1.8.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Sep 12 14:16:09 2019 InstallationDate: Installed on 2018-10-30 (316 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: apt UpgradeStatus: Upgraded to disco on 2019-04-18 (147 days ago) modified.conffile..etc.logrotate.d.apport: [modified] modified.conffile..etc.logrotate.d.apt: [modified] mtime.conffile..etc.logrotate.d.apport: 2018-12-13T12:13:33.355709 mtime.conffile..etc.logrotate.d.apt: 2018-12-13T12:13:41.355709 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1843812/+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 1833801] [NEW] initctl: invalid command: rotate
Public bug reported: rsyslog 8.16.0-1ubuntu3.1 , Ubuntu 16.04.6 LTS the logrotate for rsyslog is a bit awry. The /etc/logrotate.d/rsyslog has this in the postrotate block: /usr/lib/rsyslog/rsyslog-rotate But when invoked (either by logrotate or manually) I get: initctl: invalid command: rotate Try `initctl --help' for more information. invoke-rc.d: initscript rsyslog, action "rotate" failed. The workaround is to change the postrotate block to what I saw in a much earlier version: postrotate service rsyslog rotate > /dev/null endscript ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rsyslog 8.16.0-1ubuntu3.1 Uname: Linux 2.6.32-042stab127.2 x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Jun 22 00:24:52 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: Upgraded to xenial on 2016-06-15 (1101 days ago) mtime.conffile..etc.logrotate.d.rsyslog: 2019-06-22T00:24:05.675752 ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1833801 Title: initctl: invalid command: rotate Status in rsyslog package in Ubuntu: New Bug description: rsyslog 8.16.0-1ubuntu3.1 , Ubuntu 16.04.6 LTS the logrotate for rsyslog is a bit awry. The /etc/logrotate.d/rsyslog has this in the postrotate block: /usr/lib/rsyslog/rsyslog-rotate But when invoked (either by logrotate or manually) I get: initctl: invalid command: rotate Try `initctl --help' for more information. invoke-rc.d: initscript rsyslog, action "rotate" failed. The workaround is to change the postrotate block to what I saw in a much earlier version: postrotate service rsyslog rotate > /dev/null endscript ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rsyslog 8.16.0-1ubuntu3.1 Uname: Linux 2.6.32-042stab127.2 x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Jun 22 00:24:52 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: Upgraded to xenial on 2016-06-15 (1101 days ago) mtime.conffile..etc.logrotate.d.rsyslog: 2019-06-22T00:24:05.675752 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1833801/+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 1786391] Re: libasan0 : AddressSanitizer CHECK failed
er, libasan0 Version: 4.8.5-4ubuntu9 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1786391 Title: libasan0 : AddressSanitizer CHECK failed Status in gcc-4.8 package in Ubuntu: Confirmed Bug description: Code that worked in Ubuntu 16.04 LTS does not work in Ubuntu 18.04.1. (I tried to report this bug for package "libasan0" but bugs.launchpad.net sends me hto gcc-4.8) $ mp3gain --help ==8893== AddressSanitizer CHECK failed: ../../../../src/libsanitizer/asan/asan_rtl.cc:411 "((!asan_init_is_running && "ASan init calls itself!")) != (0)" (0x0, 0x0) #0 0x7f287806d0cd (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x120cd) #1 0x7f2878073eb3 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x18eb3) #2 0x7f287806e088 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x13088) #3 0x7f2878063fb9 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x8fb9) #4 0x7f28780701f2 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x151f2) #5 0x7f287b001aa7 (/lib/x86_64-linux-gnu/ld-2.27.so+0x17aa7) #6 0x7f287aff53eb (/lib/x86_64-linux-gnu/ld-2.27.so+0xb3eb) #7 0x7f2877a32da5 (/lib/x86_64-linux-gnu/libc-2.27.so+0x166da5) #8 0x7f28774aa0e3 (/lib/x86_64-linux-gnu/libdl-2.27.so+0x10e3) #9 0x7f2877a332de (/lib/x86_64-linux-gnu/libc-2.27.so+0x1672de) #10 0x7f2877a3336e (/lib/x86_64-linux-gnu/libc-2.27.so+0x16736e) #11 0x7f28774aa734 (/lib/x86_64-linux-gnu/libdl-2.27.so+0x1734) #12 0x7f28774aa165 (/lib/x86_64-linux-gnu/libdl-2.27.so+0x1165) #13 0x7f2878078b3b (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x1db3b) #14 0x7f287806bff3 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x10ff3) #15 0x7f287806da3a (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x12a3a) #16 0x7f287affa805 (/lib/x86_64-linux-gnu/ld-2.27.so+0x10805) #17 0x7f287afeb0c9 (/lib/x86_64-linux-gnu/ld-2.27.so+0x10c9) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libasan0 4.8.5-4ubuntu8 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Aug 9 23:04:04 2018 Dependencies: gcc-4.8-base 4.8.5-4ubuntu8 gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 InstallationDate: Installed on 2016-06-05 (795 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gcc-4.8 UpgradeStatus: Upgraded to bionic on 2018-04-27 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1786391/+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 1786391] Re: libasan0 : AddressSanitizer CHECK failed
Still a problem in Ubuntu 18.10, mp3gain version 1.5.2-r2-6 ii mp3gain1.5.2-r2-6 amd64Lossless mp3 normalizer with stat moses@jolyne:~$ mp3gain --help ==16547== AddressSanitizer CHECK failed: ../../../../src/libsanitizer/asan/asan_rtl.cc:411 "((!asan_init_is_running && "ASan init calls itself!")) != (0)" (0x0, 0x0) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1786391 Title: libasan0 : AddressSanitizer CHECK failed Status in gcc-4.8 package in Ubuntu: Confirmed Bug description: Code that worked in Ubuntu 16.04 LTS does not work in Ubuntu 18.04.1. (I tried to report this bug for package "libasan0" but bugs.launchpad.net sends me hto gcc-4.8) $ mp3gain --help ==8893== AddressSanitizer CHECK failed: ../../../../src/libsanitizer/asan/asan_rtl.cc:411 "((!asan_init_is_running && "ASan init calls itself!")) != (0)" (0x0, 0x0) #0 0x7f287806d0cd (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x120cd) #1 0x7f2878073eb3 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x18eb3) #2 0x7f287806e088 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x13088) #3 0x7f2878063fb9 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x8fb9) #4 0x7f28780701f2 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x151f2) #5 0x7f287b001aa7 (/lib/x86_64-linux-gnu/ld-2.27.so+0x17aa7) #6 0x7f287aff53eb (/lib/x86_64-linux-gnu/ld-2.27.so+0xb3eb) #7 0x7f2877a32da5 (/lib/x86_64-linux-gnu/libc-2.27.so+0x166da5) #8 0x7f28774aa0e3 (/lib/x86_64-linux-gnu/libdl-2.27.so+0x10e3) #9 0x7f2877a332de (/lib/x86_64-linux-gnu/libc-2.27.so+0x1672de) #10 0x7f2877a3336e (/lib/x86_64-linux-gnu/libc-2.27.so+0x16736e) #11 0x7f28774aa734 (/lib/x86_64-linux-gnu/libdl-2.27.so+0x1734) #12 0x7f28774aa165 (/lib/x86_64-linux-gnu/libdl-2.27.so+0x1165) #13 0x7f2878078b3b (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x1db3b) #14 0x7f287806bff3 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x10ff3) #15 0x7f287806da3a (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x12a3a) #16 0x7f287affa805 (/lib/x86_64-linux-gnu/ld-2.27.so+0x10805) #17 0x7f287afeb0c9 (/lib/x86_64-linux-gnu/ld-2.27.so+0x10c9) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libasan0 4.8.5-4ubuntu8 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Aug 9 23:04:04 2018 Dependencies: gcc-4.8-base 4.8.5-4ubuntu8 gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 InstallationDate: Installed on 2016-06-05 (795 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gcc-4.8 UpgradeStatus: Upgraded to bionic on 2018-04-27 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1786391/+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 1318975] Re: /usr/bin/host utility cannot change port for DNS querires
for what it's worth, `nslookup` can also set the port for a query: dig @localhost -p 8600 mysql.service.consul nslookup -po=8600 mysql.service.consul localhost ... but both "nslookup" and "dig" come from package "dnsutils", which brings in six other packages and 512kB of diskspace for amd64 packages. Would any but the smallest of embedded systems be burdened? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1318975 Title: /usr/bin/host utility cannot change port for DNS querires Status in iputils package in Ubuntu: Confirmed Bug description: This is not a bug report. It is request for missing feature... /usr/bin/host utility to check DNS is limited to send DNS queries to port 53. There is no option to change port for DNS queries. Other utilities, like dig, can change port. I can change DNS server but port is always 53. I found this missing feature while I was troubleshooting my DNS. My ISP is hijacking port 53 and I found I cannot use host utility to diagnose this problem... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1318975/+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 1786391] [NEW] libasan0 : AddressSanitizer CHECK failed
Public bug reported: Code that worked in Ubuntu 16.04 LTS does not work in Ubuntu 18.04.1. (I tried to report this bug for package "libasan0" but bugs.launchpad.net sends me hto gcc-4.8) $ mp3gain --help ==8893== AddressSanitizer CHECK failed: ../../../../src/libsanitizer/asan/asan_rtl.cc:411 "((!asan_init_is_running && "ASan init calls itself!")) != (0)" (0x0, 0x0) #0 0x7f287806d0cd (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x120cd) #1 0x7f2878073eb3 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x18eb3) #2 0x7f287806e088 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x13088) #3 0x7f2878063fb9 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x8fb9) #4 0x7f28780701f2 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x151f2) #5 0x7f287b001aa7 (/lib/x86_64-linux-gnu/ld-2.27.so+0x17aa7) #6 0x7f287aff53eb (/lib/x86_64-linux-gnu/ld-2.27.so+0xb3eb) #7 0x7f2877a32da5 (/lib/x86_64-linux-gnu/libc-2.27.so+0x166da5) #8 0x7f28774aa0e3 (/lib/x86_64-linux-gnu/libdl-2.27.so+0x10e3) #9 0x7f2877a332de (/lib/x86_64-linux-gnu/libc-2.27.so+0x1672de) #10 0x7f2877a3336e (/lib/x86_64-linux-gnu/libc-2.27.so+0x16736e) #11 0x7f28774aa734 (/lib/x86_64-linux-gnu/libdl-2.27.so+0x1734) #12 0x7f28774aa165 (/lib/x86_64-linux-gnu/libdl-2.27.so+0x1165) #13 0x7f2878078b3b (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x1db3b) #14 0x7f287806bff3 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x10ff3) #15 0x7f287806da3a (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x12a3a) #16 0x7f287affa805 (/lib/x86_64-linux-gnu/ld-2.27.so+0x10805) #17 0x7f287afeb0c9 (/lib/x86_64-linux-gnu/ld-2.27.so+0x10c9) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libasan0 4.8.5-4ubuntu8 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Aug 9 23:04:04 2018 Dependencies: gcc-4.8-base 4.8.5-4ubuntu8 gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 InstallationDate: Installed on 2016-06-05 (795 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gcc-4.8 UpgradeStatus: Upgraded to bionic on 2018-04-27 (104 days ago) ** Affects: gcc-4.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1786391 Title: libasan0 : AddressSanitizer CHECK failed Status in gcc-4.8 package in Ubuntu: New Bug description: Code that worked in Ubuntu 16.04 LTS does not work in Ubuntu 18.04.1. (I tried to report this bug for package "libasan0" but bugs.launchpad.net sends me hto gcc-4.8) $ mp3gain --help ==8893== AddressSanitizer CHECK failed: ../../../../src/libsanitizer/asan/asan_rtl.cc:411 "((!asan_init_is_running && "ASan init calls itself!")) != (0)" (0x0, 0x0) #0 0x7f287806d0cd (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x120cd) #1 0x7f2878073eb3 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x18eb3) #2 0x7f287806e088 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x13088) #3 0x7f2878063fb9 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x8fb9) #4 0x7f28780701f2 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x151f2) #5 0x7f287b001aa7 (/lib/x86_64-linux-gnu/ld-2.27.so+0x17aa7) #6 0x7f287aff53eb (/lib/x86_64-linux-gnu/ld-2.27.so+0xb3eb) #7 0x7f2877a32da5 (/lib/x86_64-linux-gnu/libc-2.27.so+0x166da5) #8 0x7f28774aa0e3 (/lib/x86_64-linux-gnu/libdl-2.27.so+0x10e3) #9 0x7f2877a332de (/lib/x86_64-linux-gnu/libc-2.27.so+0x1672de) #10 0x7f2877a3336e (/lib/x86_64-linux-gnu/libc-2.27.so+0x16736e) #11 0x7f28774aa734 (/lib/x86_64-linux-gnu/libdl-2.27.so+0x1734) #12 0x7f28774aa165 (/lib/x86_64-linux-gnu/libdl-2.27.so+0x1165) #13 0x7f2878078b3b (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x1db3b) #14 0x7f287806bff3 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x10ff3) #15 0x7f287806da3a (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x12a3a) #16 0x7f287affa805 (/lib/x86_64-linux-gnu/ld-2.27.so+0x10805) #17 0x7f287afeb0c9 (/lib/x86_64-linux-gnu/ld-2.27.so+0x10c9) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libasan0 4.8.5-4ubuntu8 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Aug 9 23:04:04 2018 Dependencies: gcc-4.8-base 4.8.5-4ubuntu8 gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 InstallationDate: Installed on 2016-06-05 (795 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd6
[Touch-packages] [Bug 1547466] Re: grep switches into binary mode while processing a text file under the C locale
I just tripped over something like this with grep v3.1-2 (Ubuntu 17.10 "artful"). the LC_ALL setting did not make a difference, and grep 3.1 passes the "test case" described in the bug description. I have many text files, but one of them had a string of 49 \x00 chars. What confused me was the switch into binary mode happens on line 1,128,254, but the string of nulls is on line 1,128,436. My method to find the triggering data was : `split -n 2 events.log` repeatedly: testing each half, discarding the half that passes and repeating until I had a failing text file I can manually examine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1547466 Title: grep switches into binary mode while processing a text file under the C locale Status in grep package in Ubuntu: Fix Released Status in grep source package in Xenial: Fix Released Status in grep source package in Yakkety: Fix Released Status in grep package in Debian: Fix Released Bug description: I noticed this staring to happen in Xenial about two days ago. When running sbuild (or now the buildd, too), the build breaks when trying to compile a generated file. I traced the problem down to grep suddenly acting weird. When not having any language set (or a non-UTF8 mode) it will start printing some lines of a source file and then suddenly end that by printing "Binary file ... matches". With the attached file, the difference can be observed (running Xenial): LANG=C grep -v xxx grant_table.h and LANG=C.UTF-8 grep -v xxx grant_table.h SRU INFORMATION === Upstream fixes: - http://git.savannah.gnu.org/cgit/grep.git/commit/?id=d8a366218 (but depends on previous patches and is not sufficient by itself) - http://git.savannah.gnu.org/cgit/grep.git/commit/?id=d8a366218 (tests+doc) Test case: Call grep on a file or a string with non-ASCII characters in the C locale: $ echo 'héll☺ ≥x' | LC_ALL=C grep . In xenial this just shows "Binary file (standard input) matches", with the fix it should show the actual input string (with some garbled output of course as the UTF-8 chars cannot be displayed in C) Regression potential: grep is being used in tons of places; during xenial we had to fix/put a "use grep -a" workaround into a lot of packages to fix the fallout from grep 2.23 which introduced this. That said, as a result of "Binary file matches" does not give any more information than the actual string match, and scripts which get along with this answer most likely just check the exit code anyway (which does not change), the risk is bearable. We will soon do a test rebuild in yakkety with gcc-6 and grep 2.25, and will sift through the results to identify new FTBFS that are due to grep 2.25. This SRU should not be released until this happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1547466/+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 1674869] [NEW] package qtbase5-dev 5.7.1+dfsg-2ubuntu4~1 failed to install/upgrade: unable to open '/usr/include/x86_64-linux-gnu/qt5/QtConcurrent/QtConcurrent.dpkg-new': Operati
Public bug reported: while installing ProblemType: Package DistroRelease: Ubuntu 17.04 Package: qtbase5-dev 5.7.1+dfsg-2ubuntu4~1 ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Wed Mar 22 08:18:13 2017 DuplicateSignature: package:qtbase5-dev:5.7.1+dfsg-2ubuntu4~1 Unpacking qtbase5-dev:amd64 (5.7.1+dfsg-2ubuntu4~1) over (5.7.1+dfsg-2ubuntu3~2) ... dpkg: error processing archive /tmp/apt-dpkg-install-xZbwtA/073-qtbase5-dev_5.7.1+dfsg-2ubuntu4~1_amd64.deb (--unpack): unable to open '/usr/include/x86_64-linux-gnu/qt5/QtConcurrent/QtConcurrent.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/include/x86_64-linux-gnu/qt5/QtConcurrent/QtConcurrent.dpkg-new': Operation not permitted InstallationDate: Installed on 2016-12-10 (101 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161210) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4~rc2 SourcePackage: qtbase-opensource-src Title: package qtbase5-dev 5.7.1+dfsg-2ubuntu4~1 failed to install/upgrade: unable to open '/usr/include/x86_64-linux-gnu/qt5/QtConcurrent/QtConcurrent.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1674869 Title: package qtbase5-dev 5.7.1+dfsg-2ubuntu4~1 failed to install/upgrade: unable to open '/usr/include/x86_64-linux- gnu/qt5/QtConcurrent/QtConcurrent.dpkg-new': Operation not permitted Status in qtbase-opensource-src package in Ubuntu: New Bug description: while installing ProblemType: Package DistroRelease: Ubuntu 17.04 Package: qtbase5-dev 5.7.1+dfsg-2ubuntu4~1 ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Wed Mar 22 08:18:13 2017 DuplicateSignature: package:qtbase5-dev:5.7.1+dfsg-2ubuntu4~1 Unpacking qtbase5-dev:amd64 (5.7.1+dfsg-2ubuntu4~1) over (5.7.1+dfsg-2ubuntu3~2) ... dpkg: error processing archive /tmp/apt-dpkg-install-xZbwtA/073-qtbase5-dev_5.7.1+dfsg-2ubuntu4~1_amd64.deb (--unpack): unable to open '/usr/include/x86_64-linux-gnu/qt5/QtConcurrent/QtConcurrent.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/include/x86_64-linux-gnu/qt5/QtConcurrent/QtConcurrent.dpkg-new': Operation not permitted InstallationDate: Installed on 2016-12-10 (101 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161210) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4~rc2 SourcePackage: qtbase-opensource-src Title: package qtbase5-dev 5.7.1+dfsg-2ubuntu4~1 failed to install/upgrade: unable to open '/usr/include/x86_64-linux-gnu/qt5/QtConcurrent/QtConcurrent.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1674869/+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 955675] Re: openssl s_client's '-ssl2' option no longer works in 12.04
Still here in Ubuntu 14.04.4 LTS and openssl 1.0.1f-1 Expecting 1.0.1g to arrive soon after the announcement of the DROWN exploit. The cheap fix would be to remove '-ssl2' from the usage string and man pages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/955675 Title: openssl s_client's '-ssl2' option no longer works in 12.04 Status in openssl package in Ubuntu: Confirmed Bug description: the s_client(1) man page describes -tls1, -ssl3 and -ssl2. The latter isn't recognised by openssl in 12.04: aj@aj-Vostro-260:~$ openssl version OpenSSL 1.0.0g 18 Jan 2012 aj@aj-Vostro-260:~$ openssl s_client -ssl2 unknown option -ssl2 usage: s_client args aj@aj-Vostro-260:~$ openssl s_client -ssl3 connect: Connection refused connect:errno=111 aj@aj-Vostro-260:~$ openssl s_client -tls1 connect: Connection refused connect:errno=111 aj@aj-Vostro-260:~$ This option should still continue to work, please do not leave disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/955675/+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 559331] Re: Permanent "Printer-out-of-paper" message.
Ubuntu 14.10 , CUPS 1.7.2, DeviceURI "hp:/usb/HP_LaserJet_Professional_P1102w" and I just ran into this problem myself. Rebooted the printer, printed a test page with the printer to make sure there's no paperjam or bad mechanical sensor. Ubuntu still refuses to sent print jobs to the printer because "out-of-paper." Tried he workaround mentioned in #2 above, and CUPS automatically resumed the print jobs without my prompting. It seems CUPS doesn't query the printer for its status, or doesn't query the printer often enough. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/559331 Title: Permanent "Printer-out-of-paper" message. Status in cups package in Ubuntu: Confirmed Bug description: Binary package hint: cups This probably has to do with CUPS. Version: 1.4.1- 4ubuntu2.4 (latest on Karmic). I was printing a document when the printer was out of paper and got a message that "The printer is out of paper". I went to reload it and clicked resume on the printer and printing carried on normally. From this point on, the message "The printer is out of paper" is permanently stuck on the printer. - Every time i print, i get the message "The printer is out of paper", but the printing occurs without errors. - The configuration tool (system-config-printer 1.1.12) shows the printer with the red error sign. When viewing the properties of said printer, in the "Ink/Toner Levels" section, i have the "Status Message": "Printer HP-Officejet-Pro-k550 is out of paper". If i click refresh then i get a "CUPS server error": "There was an error during the CUPS operation: 'client-error-document-format-not-supported'." (Not sure this is relevant). Removing and reinstalling the printer fixes this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/559331/+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 1386721] Re: Graphics Slow After Upgrade 14.04 - 14.10
This bug also affects me, just updated from 14.04 to 14.10 this morning after getting in to work on my Dell XPS M1530, and development has become impossible. Eclipse Juno has become almost totally non- responsive. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386721 Title: Graphics Slow After Upgrade 14.04 - 14.10 Status in xorg package in Ubuntu: Confirmed Bug description: Using Gnome Ubuntu 14.10, Dell XPS 13, intel 915 Graphics After upgrading from 14.04 to 14.10 there are a lot of places where the graphics are working much slower than they were before: - Gnome Shell Interface is very sluggish, visible "chops" (redrawing) when pressing the [Super] key. - Selecting text in Gedit takes a full second pr. line Experiences some subjective improvement when I booted kernel 3.13.0-37 instead of 3.16.0-23, but that may be my imagination as the problem persists. I've searched google, forums, found a couple of relevant links that point to the issue being the Intel drivers. http://askubuntu.com/questions/53962...E2%86%92-14-10 http://www.webupd8.org/2014/10/ubunt...ent-1652086424 But the drivers currently in 14.10 should be newer than those supplied by Intel to 14.04 so that doesn't make sense to me. As one Intel developer wrote: "I would like to point out that since what we do is bring more ecent versions of the software to the target distributions than they ship with, a 14.04 targeted installer is unlikely to bring much to a 14.10 installation, which most likely has the same or more recent versions already anyway." Source: https://01.org/linuxgraphics/node/375 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Oct 28 15:24:30 2014 DistUpgraded: 2014-10-25 20:59:36,052 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2014-06-14 (135 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=105bbbd1-365e-4063-bdca-fc5431faf5dc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-10-25 (2 days ago) dmi.bios.date: 12/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Oct 28 13:44:57 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386721/+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