[Touch-packages] [Bug 1897561] Re: libperl.so.5.30.0 causes nginx to segfault

2021-02-13 Thread peacecop kalmer:
The suggested solution for removing "libnginx-mod-http-perl" doesn't
probably make the situation better but worse because it would uninstall
"onlyoffice-documentserver" which is unwanted:

"kalmer@test:~$ sudo apt remove libnginx-mod-http-perl 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  cabextract libmspack0 libnginx-mod-http-auth-pam 
libnginx-mod-http-cache-purge libnginx-mod-http-dav-ext libnginx-mod-http-echo
  libnginx-mod-http-fancyindex libnginx-mod-http-geoip libnginx-mod-http-geoip2 
libnginx-mod-http-headers-more-filter libnginx-mod-http-lua
  libnginx-mod-http-ndk libnginx-mod-http-subs-filter 
libnginx-mod-http-uploadprogress libnginx-mod-http-upstream-fair 
libnginx-mod-nchan
  ttf-mscorefonts-installer
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  nginx-core
Soovituslikud paketid:
  nginx-doc
EEMALDATAKSE järgnevad paketid:
  libnginx-mod-http-perl nginx-extras onlyoffice-documentserver
Paigaldatakse järgnevad UUED paketid:
  nginx-core
0 uuendatud, 1 värskelt paigaldatud, 3 eemaldada ja 0 uuendamata.
On vaja tõmmata 425 kB arhiive.
Pärast seda tegevust vabaneb 949 MB kettaruumi.
Do you want to continue? [Y/n] n
Katkesta."

I disabled the module instead:
"kalmer@test:/etc/nginx/modules-enabled$ sudo rm 50-mod-http-perl.conf"

So far, "nginx" hasn't crashed after multiple reloading and "onlyoffice-
documentserver" also seems to work.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1897561

Title:
  libperl.so.5.30.0 causes nginx to segfault

Status in perl package in Ubuntu:
  Confirmed

Bug description:
  [Steps to reproduce]

  1) launch a focal container
  $ lxc launch images:ubuntu/focal focal-1897561
  2) enter the container
  $ lxc shell focal-1897561
  3) install libnginx-mod-http-perl
  # apt-get install -y nginx-core libnginx-mod-http-perl
  4) check nginx journal
  # journalctl -fu nginx &
  5) reload nginx 2-3 times
  # systemctl reload nginx

  Eventually you will see this from the journal:

  Oct 13 17:13:34 focal-1897561 systemd[1]: Reloaded A high performance web 
server and a reverse proxy server.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Main process exited, 
code=dumped, status=11/SEGV
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 
(nginx) with signal SIGKILL.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 
(nginx) with signal SIGKILL.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 
(nginx) with signal SIGKILL.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 
(nginx) with signal SIGKILL.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Failed with result 
'core-dump'.

  [Workaround]

  If libnginx-mod-http-perl is not needed, purging it and restarting
  nginx sidesteps the problem.

  [Original bug description]

  Ubuntu 20.04 LTS

  Looks that Perl 5.30 has bug that causes nginx to die, usually occurs
  after "service nginx reload"

  This looks like nginx, but it really is perl issue:
  https://github.com/Perl/perl5/issues/17154

  Fix done in 5.32 (Perl5 commit bf0) and people are asking backport
  to 5.30 to get fix also to nginx.

  Error:
  Sep 28 07:39:43 host kernel: [1340832.811014] nginx[3253005]: segfault at 10 
ip 7fbf3220d593 sp 7ffd6bba6260 error 4 in 
libperl.so.5.30.0[7fbf321a5000+166000]

  Symptom: Nginx terminates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Package: perl 5.30.0-9build1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal uec-images
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1897561/+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 1849886] Re: lightdm does not work on eoan on raspberry pi 4

2021-02-13 Thread Launchpad Bug Tracker
[Expired for lightdm (Ubuntu) because there has been no activity for 60
days.]

** Changed in: lightdm (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1849886

Title:
  lightdm does not work on eoan on raspberry pi 4

Status in lightdm package in Ubuntu:
  Expired

Bug description:
  if you follow the directions on
  https://wiki.ubuntu.com/ARM/RaspberryPi

  sudo apt-get install xubuntu-desktop

  about 20% thru the installation it will ask which window manager you want 
(using dpkg-reconfigure).
  if you select lightdm, you will only get a blank greeter screen after you 
reboot.

  using sudo dpkg-reconfigure gdm3

  resets this to gdm3 and after a reboot, everything is fine.

  this was done on a clean armhf eoan install on a 4gb raspberry pi 4B.

  I have done the install several times.   This bug is repeatable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1849886/+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 881137] Re: UFW does not clean iptables setting from /etc/ufw/before.rules

2021-02-13 Thread Jamie Strandboge
CzBiX, ufw does not yet manage the nat table (though there have been a
couple of false starts). However, it does manage the FORWARD chain with
'ufw route' so it is possible for you to create a chain in the nat table
in /etc/ufw/before.rules, and then use ufw route for other things. This
is described in 'man ufw-framework' in the EXAMPLES section.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/881137

Title:
  UFW does not clean iptables setting from /etc/ufw/before.rules

Status in ufw package in Ubuntu:
  Won't Fix

Bug description:
  Adding some additional settings to /etc/ufw/before.rules is not
  deleted when ufw is stopped.

  I added these lines at top of file /etc/ufw/before.rules

  *nat
  :POSTROUTING ACCEPT [0:0]
  -A POSTROUTING -o eth0 -j MASQUERADE
  COMMIT

  Then I reloaded ufw firewall with command: ufw reload. Output from
  iptables-save

  $ iptables-save -t nat
  *nat
  :PREROUTING ACCEPT [4:478]
  :INPUT ACCEPT [4:478]
  :OUTPUT ACCEPT [0:0]
  :POSTROUTING ACCEPT [0:0]
  -A POSTROUTING -o eth0 -j MASQUERADE 
  COMMIT

  Then I reloaded ufw firewall again:

  $ iptables-save -t nat
  *nat
  :PREROUTING ACCEPT [4:478]
  :INPUT ACCEPT [4:478]
  :OUTPUT ACCEPT [0:0]
  :POSTROUTING ACCEPT [0:0]
  -A POSTROUTING -o eth0 -j MASQUERADE 
  -A POSTROUTING -o eth0 -j MASQUERADE 
  COMMIT

  And ufw reload again

  $ iptables-save -t nat
  *nat
  :PREROUTING ACCEPT [4:478]
  :INPUT ACCEPT [4:478]
  :OUTPUT ACCEPT [0:0]
  :POSTROUTING ACCEPT [0:0]
  -A POSTROUTING -o eth0 -j MASQUERADE 
  -A POSTROUTING -o eth0 -j MASQUERADE 
  -A POSTROUTING -o eth0 -j MASQUERADE
  COMMIT

  And again and postrouting is never deleted when ufw is stopped and
  added again when stared. Same happen if I stop ufw firewall with: $
  stop ufw. nat lines are not cleaned.

  UFW should remove all iptables settings specified in config files
  after ufw is stopped! This can be dangerous if apt-get is updating
  some ufw files and scripts needs to reload ufw (some lines will be
  more times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/881137/+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 1915623] [NEW] package lvm2 2.03.07-1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1

2021-02-13 Thread Raymond Chow
Public bug reported:

Was trying to install on raspi 4

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: lvm2 2.03.07-1ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-1015.18-raspi 5.8.18
Uname: Linux 5.8.0-1015-raspi aarch64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: arm64
CasperMD5CheckResult: skip
Date: Sat Feb 13 16:44:51 2021
ErrorMessage: installed lvm2 package post-installation script subprocess 
returned error exit status 1
ImageMediaBuild: 20201022
Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.5ubuntu2
 apt  2.1.10ubuntu0.2
SourcePackage: lvm2
Title: package lvm2 2.03.07-1ubuntu3 failed to install/upgrade: installed lvm2 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lvm2 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package arm64 groovy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1915623

Title:
  package lvm2 2.03.07-1ubuntu3 failed to install/upgrade: installed
  lvm2 package post-installation script subprocess returned error exit
  status 1

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Was trying to install on raspi 4

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: lvm2 2.03.07-1ubuntu3
  ProcVersionSignature: Ubuntu 5.8.0-1015.18-raspi 5.8.18
  Uname: Linux 5.8.0-1015-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Sat Feb 13 16:44:51 2021
  ErrorMessage: installed lvm2 package post-installation script subprocess 
returned error exit status 1
  ImageMediaBuild: 20201022
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10ubuntu0.2
  SourcePackage: lvm2
  Title: package lvm2 2.03.07-1ubuntu3 failed to install/upgrade: installed 
lvm2 package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1915623/+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 1914816] Re: ufw not logging if it decides to stop all traffic ? Confused

2021-02-13 Thread Jamie Strandboge
Hi. A few things: ufw is capable of logging (see 'man ufw' the part
about 'ufw logging' as well as per rule logging with 'ufw ... log' or
'ufw ... log-all'. It is also capable of ipv6 (see /etc/default/ufw.
Also, gufw is a different project than ufw, but it sounds like the issue
you saw may be seeing is another firewall is in place.

What is the output of 'sudo /usr/share/ufw/check-requirements'?

** Changed in: ufw (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1914816

Title:
  ufw not logging if it decides to stop all traffic ?  Confused

Status in ufw package in Ubuntu:
  Incomplete

Bug description:
  Sorry, this is going to be a very bad report.  Here's what I did:
  - installed gufw and enabled it, no rules, just default incoming=deny 
outgoing=accept
  - rebooted
  - Ethernet says it connected
  - no network access; ping 1.1.1.1 fails
  - launch gufw, and it says it's disabled (the whole firewall)
  - I think eventually I figured out that iptables had been emptied and INPUT 
chain set to DROP

  After many travails, I captured a piece of dmesg output as the system
  was booting, and I think it shows ufw trying to check IPv6 status and
  deciding to stop everything.  At least logging (which was set to full
  in gufw) suddenly stops.

  In network manager, I've tried to say "ignore IPv6".  I'm not sure if
  this trouble is related to fiddling with the "only work if IPv4 is
  enabled" check-box, which seems to have a ToolTip that is exactly
  backwards.  My ISP does not give IPv6 service.  I've tried many
  settings of the IPv6 drop-down in System Settings / Network GUI,
  setting and clearing the IPv4 and IPv6 required check-boxes, etc.

  So, I'm totally confused, but I think the log shows that logging
  suddenly stops (from full to zero), which must mean ufw detected some
  condition that made it empty out the iptables and set everything to
  DROP ?  If so, ufw should have logged a message saying it was doing
  so, and I don't see such a message.  So, if I'm right, at least this
  is a feature request that ufw should log a message when it decides to
  stop all IPv4 or IPv6 traffic and/or stop logging and/or wipe out all
  rules.

  Sorry about the mess of a report.

  I'm using Kubuntu 20.10, gufw 20.10.0-0ubuntu1, ufw 0.36-7

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ufw (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Feb  5 20:35:18 2021
  InstallationDate: Installed on 2021-02-03 (2 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1914816/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

2021-02-13 Thread Steve Langasek
** Changed in: ubuntu-cdimage
 Assignee: Samaun Parvez (parvez1) => (unassigned)

-- 
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/1871268

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  In Progress
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in apt package in Debian:
  Unknown

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  We have two changes that help address this:

  * The first one stops immediately configuring multi-arch siblings
  (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
  necessary, and caused all the libc6:i386 failures here.

  * The second change sort of also supersedes the first one: It just
  ignores any errors from immediate configuration, relying on the fact
  that it's checked and rectified at a later point if there are
  unconfigured packages (which is what made all those failures happen
  spuriously after having successfully installed everything).

  [Test case]
  We have one test case in EIPP format in the Debian bug 973305 which was only 
helped by the second change, not the first one. Run /usr/lib/apt/planners < 
eipp.log and check there are no errors.

  TODO: It's unclear if the APT from proposed installed in the live
  session will fix the installer, needs investigation, but would make a
  useful test case.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 

[Touch-packages] [Bug 1782342] Re: mawk memory corruption on recent tzdb data

2021-02-13 Thread Paul Eggert
This bug is fixed in Ubuntu 20.10 (and probably earlier versions), as
Ubuntu 20.10 uses mawk 1.3.4 20200120. So you can close the bug report.
(I'd close the bug report myself but don't seem to have the bits to do
that.)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mawk in Ubuntu.
https://bugs.launchpad.net/bugs/1782342

Title:
  mawk memory corruption on recent tzdb data

Status in mawk package in Ubuntu:
  Triaged

Bug description:
  mawk corrupts memory and dumps core when processing recent tzdb
  releases. Although Ubuntu users can work around the problem by using
  'make AWK=gawk', it would be better if ordinary 'make' worked (where
  AWK defaults to awk, and awk on Ubuntu defaults to mawk.

  Since this is memory corruption there may well be a security
  vulnerability in mawk. I have not checked for this, though.

  A simple fix would be to upgrade mawk to the current upstream release.
  I see that there's already a request to do that; see Bug#1332114. I
  don't know why Debian and Ubuntu are wedged on an ancient upstream
  version.

  To reproduce the problem, download the most recent tzdb release and
  run 'make AWK=mawk vanguard.zi'. A shell transcript follows. I ran
  this on Ubuntu 16.04.4 LTS x86-64; 'dpkg -s mawk' reports 'Version:
  1.3.3-17ubuntu2'. The shell commands I ran were:

  wget https://www.iana.org/time-zones/repository/releases/tzdb-2018e.tar.lz
  tar xf tzdb-2018e.tar.lz
  cd tzdb-2018e
  make AWK=mawk vanguard.zi

  Here's the behavior I observed:

  $ wget https://www.iana.org/time-zones/repository/releases/tzdb-2018e.tar.lz
  --2018-07-18 04:09:59--  
https://www.iana.org/time-zones/repository/releases/tzdb-2018e.tar.lz
  Resolving www.iana.org (www.iana.org)... 192.0.32.8, 2620:0:2d0:200::8
  Connecting to www.iana.org (www.iana.org)|192.0.32.8|:443... connected.
  HTTP request sent, awaiting response... 302 FOUND
  Location: https://data.iana.org/time-zones/releases/tzdb-2018e.tar.lz 
[following]
  --2018-07-18 04:10:00--  
https://data.iana.org/time-zones/releases/tzdb-2018e.tar.lz
  Resolving data.iana.org (data.iana.org)... 72.21.81.189, 
2606:2800:11f:bb5:f27:227f:1bbf:a0e
  Connecting to data.iana.org (data.iana.org)|72.21.81.189|:443... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 437679 (427K) [application/x-tar]
  Saving to: ‘tzdb-2018e.tar.lz’

  tzdb-2018e.tar.lz   100%[===>] 427.42K  --.-KB/sin
  0.06s

  2018-07-18 04:10:00 (6.49 MB/s) - ‘tzdb-2018e.tar.lz’ saved
  [437679/437679]

  $ tar xf tzdb-2018e.tar.lz
  $ cd tzdb-2018e
  $ make AWK=mawk vanguard.zi
  mawk -v DATAFORM=`expr vanguard.zi : '\(.*\).zi'` -f ziguard.awk \
  africa antarctica asia australasia europe northamerica southamerica 
etcetera systemv factory backward  >vanguard.zi.out
  *** Error in `mawk': malloc(): memory corruption: 0x01ebc4f0 ***
  === Backtrace: =
  /lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7fb09870f7e5]
  /lib/x86_64-linux-gnu/libc.so.6(+0x8213e)[0x7fb09871a13e]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x54)[0x7fb09871c184]
  mawk[0x40ff0f]
  mawk[0x405dff]
  mawk[0x40e1e0]
  mawk[0x406b6e]
  mawk[0x40185d]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7fb0986b8830]
  mawk[0x40188d]
  === Memory map: 
  0040-0041b000 r-xp  08:01 268
/usr/bin/mawk
  0061a000-0061b000 r--p 0001a000 08:01 268
/usr/bin/mawk
  0061b000-0061d000 rw-p 0001b000 08:01 268
/usr/bin/mawk
  0061d000-00621000 rw-p  00:00 0 
  01ea-01ec1000 rw-p  00:00 0  
[heap]
  7fb09400-7fb094021000 rw-p  00:00 0 
  7fb094021000-7fb09800 ---p  00:00 0 
  7fb098482000-7fb098498000 r-xp  08:01 3019293
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb098498000-7fb098697000 ---p 00016000 08:01 3019293
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb098697000-7fb098698000 rw-p 00015000 08:01 3019293
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb098698000-7fb098858000 r-xp  08:01 3018864
/lib/x86_64-linux-gnu/libc-2.23.so
  7fb098858000-7fb098a58000 ---p 001c 08:01 3018864
/lib/x86_64-linux-gnu/libc-2.23.so
  7fb098a58000-7fb098a5c000 r--p 001c 08:01 3018864
/lib/x86_64-linux-gnu/libc-2.23.so
  7fb098a5c000-7fb098a5e000 rw-p 001c4000 08:01 3018864
/lib/x86_64-linux-gnu/libc-2.23.so
  7fb098a5e000-7fb098a62000 rw-p  00:00 0 
  7fb098a62000-7fb098b6a000 r-xp  08:01 3018856
/lib/x86_64-linux-gnu/libm-2.23.so
  7fb098b6a000-7fb098d69000 ---p 00108000 08:01 3018856
/lib/x86_64-linux-gnu/libm-2.23.so
  7fb098d69000-7fb098d6a000 r--p 00107000 08:01 3018856

[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

2021-02-13 Thread Samaun Parvez
** Changed in: ubuntu-cdimage
 Assignee: (unassigned) => Samaun Parvez (parvez1)

-- 
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/1871268

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  In Progress
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in apt package in Debian:
  Unknown

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  We have two changes that help address this:

  * The first one stops immediately configuring multi-arch siblings
  (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
  necessary, and caused all the libc6:i386 failures here.

  * The second change sort of also supersedes the first one: It just
  ignores any errors from immediate configuration, relying on the fact
  that it's checked and rectified at a later point if there are
  unconfigured packages (which is what made all those failures happen
  spuriously after having successfully installed everything).

  [Test case]
  We have one test case in EIPP format in the Debian bug 973305 which was only 
helped by the second change, not the first one. Run /usr/lib/apt/planners < 
eipp.log and check there are no errors.

  TODO: It's unclear if the APT from proposed installed in the live
  session will fix the installer, needs investigation, but would make a
  useful test case.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 

[Touch-packages] [Bug 1915590] [NEW] gnome-shell closed unexpectedly but it did not crash, just now power on but it shws the incorrect message

2021-02-13 Thread Balashanmugam
Public bug reported:

gnome-shell closed unexpectedly but it did not crash, just now power on
but it shws the incorrect message

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: apport-gtk 2.20.11-0ubuntu27.16
ProcVersionSignature: hostname 5.8.0-43.49~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 13 15:07:03 2021
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2021-02-05 (7 days ago)
InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
InterpreterPath: /usr/bin/python3.8
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: apport (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1915590

Title:
  gnome-shell closed unexpectedly but it did not crash, just now power
  on but it shws the incorrect message

Status in apport package in Ubuntu:
  New

Bug description:
  gnome-shell closed unexpectedly but it did not crash, just now power
  on but it shws the incorrect message

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport-gtk 2.20.11-0ubuntu27.16
  ProcVersionSignature: hostname 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 13 15:07:03 2021
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2021-02-05 (7 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1915590/+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 1859353] Re: software-properties-gtk not working

2021-02-13 Thread vitaly ven
I found the same message with journalctl, I try reinstall six and certify, it 
did not works.
Then try to run code from requests_unixsocket docs with python3 interactive 
console.

   import requests_unixsocket

   requests_unixsocket.monkeypatch()

   r = requests.get('http+unix://%2Fvar%2Frun%2Fdocker.sock/info')
   assert r.status_code == 200

it can't import requests.

Works again with software properties and livepatch tab after reinstall
requests for me.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1859353

Title:
  software-properties-gtk not working

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  Additional Drivers /Software & Update not working

  Hello,

  I am running :-
  Description: Ubuntu 19.10
  Release: 19.10

  software-properties-gtk:
  Installed: 0.98.5
  Candidate: 0.98.5
  Version table:
  *** 0.98.5 500
  500 http://ca.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  500 http://ca.archive.ubuntu.com/ubuntu eoan/main i386 Packages
  100 /var/lib/dpkg/status



  I am trying to run Additional Drivers /Software & Update . But it opened once 
and froze and never opened again.
  When I try running the command:-
  $ sudo software-properties-gtk

  Did a remove and reinstall of the same, but did not work.

  It returns:-

  
  ERROR:dbus.proxies:Introspect error on :1.2559:/: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message 
recipient disconnected from message bus without replying
  Traceback (most recent call last):
  File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 175, in __init__
  self.backend.Reload();
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__
  return self._proxy_method(*args, **keywords)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 147, in __call__
  **keywords)
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 653, in 
call_blocking
  message, timeout)
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The 
name :1.2559 was not provided by any .service files

  
  Also, the syslog says:-
  name='com.ubuntu.SoftwareProperties' requested by ':1.2455' (uid=1000 
pid=2267 comm="/usr/bin/python3 /usr/bin/software-properties-gtk " 
label="unconfined") (using servicehelper)
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: Unable to init 
server: Could not connect: Connection refused
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: Unable to init 
server: Could not connect: Connection refused
  Jan 12 11:58:55 gillZ dbus-daemon[2192]: [system] Successfully activated 
service 'com.ubuntu.SoftwareProperties'
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: Traceback (most 
recent call last):
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: File 
"/usr/lib/software-properties/software-properties-dbus", line 68, in 
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: server = 
SoftwarePropertiesDBus(bus, datadir=datadir)
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: File 
"/lib/python3/dist-packages/softwareproperties/dbus/SoftwarePropertiesDBus.py", 
line 66, in __init__
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: 
self._livepatch_service = LivepatchService()
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: File 
"/lib/python3/dist-packages/softwareproperties/LivepatchService.py", line 93, 
in __init__
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: self._session = 
requests_unixsocket.Session()
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: NameError: name 
'requests_unixsocket' is not defined
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: 
ERROR:dbus.proxies:Introspect error on :1.2457:/: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message 
recipient disconnected from message bus without replying
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: Traceback 
(most recent call last):
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File 
"/usr/bin/software-properties-gtk", line 100, in 
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: app = 
SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file)
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 175, in __init__
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: 
self.backend.Reload();
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File