date:20181208

*** This bug is a duplicate of bug 1806750 ***
https://bugs.launchpad.net/bugs/1806750

Some users at the Linux Mint forums have that problem because of HP
Printer drivers downloaded directly from HP.
(https://forums.linuxmint.com/viewtopic.php?f=18=273104=40)

Please open the terminal and run this command:

sudo rm /usr/share/python3/runtime.d/hplip-data.rtupdate

Then try the update again.

** This bug has been marked a duplicate of bug 1806750
   package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to 
install/upgrade: problemi con le dipendenze - lasciato non configurato

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

Title:
  package libglib2.0-dev-bin 2.56.2-0ubuntu0.18.04.2 failed to
  install/upgrade: problemi con le dipendenze - lasciato non configurato

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  errore durante upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libglib2.0-dev-bin 2.56.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18
  Uname: Linux 4.15.0-34-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   firefox:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Sep 29 18:41:06 2018
  ErrorMessage: problemi con le dipendenze - lasciato non configurato
  InstallationDate: Installed on 2018-05-03 (148 days ago)
  InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: glib2.0
  Title: package libglib2.0-dev-bin 2.56.2-0ubuntu0.18.04.2 failed to 
install/upgrade: problemi con le dipendenze - lasciato non configurato
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1795172/+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 1805924] Re: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar

*** This bug is a duplicate of bug 1806750 ***
https://bugs.launchpad.net/bugs/1806750

Hi!

Some users at the Linux Mint forums have that problem because of HP
Printer drivers downloaded directly from HP.
(https://forums.linuxmint.com/viewtopic.php?f=18=273104=40)

Please open the terminal and run this command:

sudo rm /usr/share/python3/runtime.d/hplip-data.rtupdate

Then try the update again.

** This bug has been marked a duplicate of bug 1806750
   package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to 
install/upgrade: problemi con le dipendenze - lasciato non configurato

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

Title:
  package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to
  install/upgrade: problemas de dependencias - se deja sin configurar

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  I tried to install the actualization pack, and every time it star tu
  run the download, pop's up a notification that says "there has an
  error occurred"

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   libssh-4:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Nov 29 22:21:33 2018
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2018-09-08 (82 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: glib2.0
  Title: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1805924/+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 1807510] Re: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to install/upgrade: problèmes de dépendances - laissé non configuré

*** This bug is a duplicate of bug 1806750 ***
https://bugs.launchpad.net/bugs/1806750

Some users at the Linux Mint forums have that problem because of HP
Printer drivers downloaded directly from HP.
(https://forums.linuxmint.com/viewtopic.php?f=18=273104=40)

Please open the terminal and run this command:

sudo rm /usr/share/python3/runtime.d/hplip-data.rtupdate

Then try the update again.


** This bug has been marked a duplicate of bug 1806750
   package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to 
install/upgrade: problemi con le dipendenze - lasciato non configurato

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

Title:
  package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to
  install/upgrade: problèmes de dépendances - laissé non configuré

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  i have no detail sorry

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   libssh-4:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Dec  2 10:56:15 2018
  DpkgHistoryLog:
   Start-Date: 2018-12-02  10:56:11
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: libssh-4:amd64 (0.8.0~20170825.94fa1e38-1ubuntu0.1, 
0.8.0~20170825.94fa1e38-1ubuntu0.2)
  ErrorMessage: problèmes de dépendances - laissé non configuré
  InstallationDate: Installed on 2018-11-04 (34 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: glib2.0
  Title: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to 
install/upgrade: problèmes de dépendances - laissé non configuré
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1807510/+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 1805978] Re: ubuntu_lxc test is failed with lxc-utils package not installed

2018-12-08 Thread Stéphane Graber

Well, the adt setup in this case just can't work, you can't tell apt to
install lxc-utils from -updates and liblxc1 from -proposed when they
have strict dependencies between them, you're just going to be getting
an apt failure.

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

Title:
  ubuntu_lxc test is failed with lxc-utils package not installed

Status in ubuntu-kernel-tests:
  Confirmed
Status in lxc package in Ubuntu:
  Invalid

Bug description:
  On Bionic since Nov.29,
  the ubuntu_lxc test is failing with:

   Running 'apt-get install --yes automake autopkgtest build-essential 
cloud-image-utils dh-autoreconf lxc texinfo gcc-multilib liblxc1'
   [stdout] Reading package lists...
   [stdout] Building dependency tree...
   [stdout] Reading state information...
   [stdout] liblxc1 is already the newest version (3.0.3-0ubuntu1~18.04.1).
   [stdout] Some packages could not be installed. This may mean that you have
   [stdout] requested an impossible situation or if you are using the unstable
   [stdout] distribution that some required packages have not yet been created
   [stdout] or been moved out of Incoming.
   [stdout] The following information may help to resolve the situation:
   [stdout]
   [stdout] The following packages have unmet dependencies:
   [stdout] lxc : Depends: lxc-utils (>= 3.0.2-0ubuntu1~18.04.1) but it is not 
going to be installed
   [stderr] E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1805978/+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 1806399] Re: package python3-minimal 3.6.7-1~18.04 failed to install/upgrade: installed python3-minimal package post-installation script subprocess returned error exit status 127

** Changed in: python3-defaults (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  package python3-minimal 3.6.7-1~18.04 failed to install/upgrade:
  installed python3-minimal package post-installation script subprocess
  returned error exit status 127

Status in python3-defaults package in Ubuntu:
  Incomplete

Bug description:
  lkjhgfdsazASDERTYUIOP'/;.LKJHGFDSZ

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-minimal 3.6.7-1~18.04
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   python3-minimal:amd64: Configure
   python3:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Dec  3 23:48:46 2018
  DpkgTerminalLog:
   Setting up python3-minimal (3.6.7-1~18.04) ...
   /var/lib/dpkg/info/python3-minimal.postinst: 5: 
/var/lib/dpkg/info/python3-minimal.postinst: py3compile: not found
   dpkg: error processing package python3-minimal (--configure):
installed python3-minimal package post-installation script subprocess 
returned error exit status 127
  DuplicateSignature:
   package:python3-minimal:3.6.7-1~18.04
   Setting up python3-minimal (3.6.7-1~18.04) ...
   /var/lib/dpkg/info/python3-minimal.postinst: 5: 
/var/lib/dpkg/info/python3-minimal.postinst: py3compile: not found
   dpkg: error processing package python3-minimal (--configure):
installed python3-minimal package post-installation script subprocess 
returned error exit status 127
  ErrorMessage: installed python3-minimal package post-installation script 
subprocess returned error exit status 127
  InstallationDate: Installed on 2018-01-05 (332 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Python3Details: /usr/bin/python3.6m, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: python3-defaults
  Title: package python3-minimal 3.6.7-1~18.04 failed to install/upgrade: 
installed python3-minimal package post-installation script subprocess returned 
error exit status 127
  UpgradeStatus: Upgraded to bionic on 2018-09-27 (67 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1806399/+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 1719004] Re: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.

17.10 is EOL and this is fixed in 18.04 and up.

** Changed in: glibc (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368:
  __spawnix: Assertion `ec >= 0' failed.

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Released

Bug description:
  1. Error: Package/cups-daemon2.2.4-7 (mutilated)
  2. compiz-core/tmp/apport_core_q_vnqis (corrupted)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cups-daemon 2.2.4-7
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AssertionMessage: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: 
Assertion `ec >= 0' failed.
  Date: Fri Sep 22 22:16:18 2017
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2017-05-27 (118 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=el_GR.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups
  Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: 
__spawnix: Assertion `ec >= 0' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 10/23/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0503
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-K D3
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0503:bd10/23/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-KD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1719004/+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 1807499] Re: 30 seconds boot delay when root fs is on lvm

2018-12-08 Thread Eduard Hasenleithner

A the moment I can see following solutions:

(1)
Make the lvchange_activate function in 
/usr/share/initramfs-tools/scripts/local-top/lvm2 a while loop which executes 
the "lvchange" command repeatedly until the root LV appears

(2)
Utilize udevd to create the LV devices while wait-for-root is waiting for the 
root LV to appear. A hack for doing so is to replace in 
/lib/udev/rules.d/69-lvm-metad.rules the line 96
  ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm 
pvscan --cache $major:$minor --activate ay", GOTO="lvm_end"
with
  ACTION!="remove", RUN+="/sbin/lvm pvscan --cache $major:$minor --activate ay"

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

Title:
  30 seconds boot delay when root fs is on lvm

Status in lvm2 package in Ubuntu:
  New

Bug description:
  On my system the root filesystem is located on a logical volume. I
  have constant boot delay of 30 seconds. My current conclusion is that
  this problem exists due to lvm performing the initramfs-tools local-
  top initialization incorrectly.

  According to initramfs-tools(8):
  local-top OR nfs-top After these scripts have been executed, the root  device 
 node is expected to be present (local) or the network interface is expected to 
be usable (NFS).

  But what /usr/share/initramfs-tools/scripts/local-top/lvm2 is simply
  try to activate the requested root volume by means of scanning the (at
  that moment) available block devices. What happens on my system is
  that local-top/lvm2 is executed before the pv block device (SATA-SSD)
  shows up. Then initramfs-tools calls the wait-for-root executable
  which waits for the root device node notification via udev.

  This has a (minimum) timeout of 30 seconds configured. This timeout is
  exceeded since nothing will make the root volume device to be created.
  Then later (I guess in local-block) the root volume device is created
  (since the pv is available).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lvm2 2.02.176-4.1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  8 13:52:06 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1807499/+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 1725333] Re: do-release-upgrade broke WSL

17.04 and 17.10 are both EOL and no further updates can or will be made
there.  For people still attempting to upgrade WSL, the best option is
probably just to start fresh with an 18.04 WSL install.

** Changed in: bash (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: glibc (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  do-release-upgrade broke WSL

Status in GLibC:
  Fix Released
Status in Gnu Bash:
  Fix Released
Status in bash package in Ubuntu:
  Won't Fix
Status in glibc package in Ubuntu:
  Won't Fix

Bug description:
  I had Ubuntu 17.04 installed in WSL and decided to upgrade it to
  17.10, so I had run do-release-upgrade, as I did before to upgrade to
  17.04. Everything was fine before script started upgrading packages.
  It's started from bash updating, and somehow there is a problem
  revealed that locale files is missing, and locale-gen can't be run
  (because of bug in WSL). I've tried to install language-pack-en as was
  suggested, but problem haven't resolved, any attempt to update leads
  to this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: bash 4.4-2ubuntu1.1
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Fri Oct 20 18:03:30 2017
  Dmesg:
   
  DpkgTerminalLog:
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  DuplicateSignature:
   package:bash:4.4-2ubuntu1.1
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  ErrorMessage: subprocess new pre-installation script was killed by signal 
(Aborted), core dumped
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: bash
  Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: subprocess new 
pre-installation script was killed by signal (Aborted), core dumped
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1725333/+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 1746995] Re: regression in 2.23-0ubuntu10: rsync in glusterfs's georeplication fails

** Bug watch added: Samba Bugzilla #6422
   https://bugzilla.samba.org/show_bug.cgi?id=6422

** Also affects: glibc via
   https://bugzilla.samba.org/show_bug.cgi?id=6422
   Importance: Unknown
   Status: Unknown

** Project changed: glibc => rsync

** Package changed: glibc (Ubuntu) => rsync (Ubuntu)

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

Title:
  regression in 2.23-0ubuntu10: rsync in glusterfs's georeplication
  fails

Status in rsync:
  Unknown
Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  Since somewhere in the Jan 14-18 range my glusterfs georeplication
  reports Faulty. Georeplication uses rsync internally, and tracking
  this this down leads to an exit code 3 out of rsync.

  I have no stacktraces myself, but I found this report about the same
  problem:

  https://www.spinics.net/lists/gluster-users/msg33568.html

  with traces:

  
  strace rsync :

  30743 23:34:47 newfstatat(3, "6737", {st_mode=S_IFDIR|0755, st_size=4096, 
...}, AT_SYMLINK_NOFOLLOW) = 0
  30743 23:34:47 newfstatat(3, "6741", {st_mode=S_IFDIR|0755, st_size=4096, 
...}, AT_SYMLINK_NOFOLLOW) = 0
  30743 23:34:47 getdents(3, /* 0 entries */, 131072) = 0
  30743 23:34:47 munmap(0x7fa4feae7000, 135168) = 0
  30743 23:34:47 close(3) = 0
  30743 23:34:47 write(2, "rsync: getcwd(): No such file or directory (2)", 46) 
= 46
  30743 23:34:47 write(2, "\n", 1)= 1
  30743 23:34:47 rt_sigaction(SIGUSR1, {SIG_IGN, [], SA_RESTORER, 
0x7fa4fdf404b0}, NULL, 8) = 0
  30743 23:34:47 rt_sigaction(SIGUSR2, {SIG_IGN, [], SA_RESTORER, 
0x7fa4fdf404b0}, NULL, 8) = 0
  30743 23:34:47 write(2, "rsync error: errors selecting input/output files, 
dirs (code 3) at util.c(1056) [Receiver=3.1.1]", 96) = 96
  30743 23:34:47 write(2, "\n", 1)= 1
  30743 23:34:47 exit_group(3)= ?
  30743 23:34:47 +++ exited with 3 +++

  
  The Changelog of glibc mentions that getcwd has been changed:

* SECURITY UPDATE: Buffer underflow in realpath()
  - debian/patches/any/cvs-make-getcwd-fail-if-path-is-no-absolute.diff:
Make getcwd(3) fail if it cannot obtain an absolute path
  - CVE-2018-101

  and downgrading glibc to (2.23-0ubuntu3) indeed fixes my
  georeplication problem. 0ubuntu3 is the latest version that is
  available in the repositories, other than 0ubuntu10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/rsync/+bug/1746995/+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 1746995] [NEW] regression in 2.23-0ubuntu10: rsync in glusterfs's georeplication fails

You have been subscribed to a public bug:

Since somewhere in the Jan 14-18 range my glusterfs georeplication
reports Faulty. Georeplication uses rsync internally, and tracking this
this down leads to an exit code 3 out of rsync.

I have no stacktraces myself, but I found this report about the same
problem:

https://www.spinics.net/lists/gluster-users/msg33568.html

with traces:


strace rsync :

30743 23:34:47 newfstatat(3, "6737", {st_mode=S_IFDIR|0755, st_size=4096, ...}, 
AT_SYMLINK_NOFOLLOW) = 0
30743 23:34:47 newfstatat(3, "6741", {st_mode=S_IFDIR|0755, st_size=4096, ...}, 
AT_SYMLINK_NOFOLLOW) = 0
30743 23:34:47 getdents(3, /* 0 entries */, 131072) = 0
30743 23:34:47 munmap(0x7fa4feae7000, 135168) = 0
30743 23:34:47 close(3) = 0
30743 23:34:47 write(2, "rsync: getcwd(): No such file or directory (2)", 46) = 
46
30743 23:34:47 write(2, "\n", 1)= 1
30743 23:34:47 rt_sigaction(SIGUSR1, {SIG_IGN, [], SA_RESTORER, 
0x7fa4fdf404b0}, NULL, 8) = 0
30743 23:34:47 rt_sigaction(SIGUSR2, {SIG_IGN, [], SA_RESTORER, 
0x7fa4fdf404b0}, NULL, 8) = 0
30743 23:34:47 write(2, "rsync error: errors selecting input/output files, dirs 
(code 3) at util.c(1056) [Receiver=3.1.1]", 96) = 96
30743 23:34:47 write(2, "\n", 1)= 1
30743 23:34:47 exit_group(3)= ?
30743 23:34:47 +++ exited with 3 +++


The Changelog of glibc mentions that getcwd has been changed:

  * SECURITY UPDATE: Buffer underflow in realpath()
- debian/patches/any/cvs-make-getcwd-fail-if-path-is-no-absolute.diff:
  Make getcwd(3) fail if it cannot obtain an absolute path
- CVE-2018-101

and downgrading glibc to (2.23-0ubuntu3) indeed fixes my georeplication
problem. 0ubuntu3 is the latest version that is available in the
repositories, other than 0ubuntu10.

** Affects: rsync
 Importance: Unknown
 Status: Unknown

** Affects: rsync (Ubuntu)
 Importance: Undecided
 Status: Confirmed

-- 
regression in 2.23-0ubuntu10: rsync in glusterfs's georeplication fails
https://bugs.launchpad.net/bugs/1746995
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to rsync in Ubuntu.

-- 
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 1807262] Re: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp

This bug was fixed in the package cinder -
2:14.0.0~b1~git2018120609.2cd694046-0ubuntu1

---
cinder (2:14.0.0~b1~git2018120609.2cd694046-0ubuntu1) disco; urgency=medium

  * d/tests/control, d/tests/cinder-daemons, d/tests/cinder-volume: Switch to
using mysql-server databases in autopkgtests.
  * New upstream snapshot for OpenStack Stein.
  * d/control: Align (Build-)Depends with upstream.
  * d/control: Ensure python3-migrate version is compatable with sqlite>=3.26
(LP: #1807262).

 -- Corey Bryant   Thu, 06 Dec 2018 09:27:58
-0500

** Changed in: cinder (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  stein unit tests fail with sqlalchemy.exc.NoSuchTableError:
  migration_tmp

Status in sqlalchemy-migrate:
  New
Status in cinder package in Ubuntu:
  Fix Released
Status in migrate package in Ubuntu:
  Fix Released
Status in nova package in Ubuntu:
  Fix Released
Status in sqlite3 package in Ubuntu:
  Invalid

Bug description:
  Several tests that use sqlite fail with:
  "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently
  hitting this with nova and cinder packages in disco.

  Note this started sometime after 11/19 when nova
  2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built
  successfully at the time).

  After doing some digging this appears to occur with libsqlite3-0
  3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some
  more details on that, shown by running a failing unit test from the
  cinder package: https://paste.ubuntu.com/p/hsnQFQD572/

  Update: The test in the paste above also works successfully with
  libsqlite3-0 3.25.3-2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sqlalchemy-migrate/+bug/1807262/+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 1774857] Re: sort doesn't sort and uniq loses data for many non-Latin scripts on UTF-8 locales

Using the first test case, this does appear to be fixed in cosmic (glibc
2.28) and beyond, and only affect bionic (glibc 2.27), which certainly
implies either an upstream or Debian fix slipped in between the two.
I'm not sure I'll have the bandwidth to dig into it this SRU cycle, but
I'll try to look again when I can and.

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

Title:
  sort doesn't sort and uniq loses data for many non-Latin scripts on
  UTF-8 locales

Status in coreutils package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New

Bug description:
  I’ve found out that sort doesn’t sort strings for many non-Latin
  scripts at all if the locale you’re using is one of en_US.UTF-8,
  fr_FR.UTF-8 or fi_FI.UTF-8 (probably others, too, but these are the
  ones I have tested). For locales ”C” and ko_KR.UTF-8, things work as
  expected. Here’s a test case:

  Open xterm, launch sort and input some lines of Syriac, Ethiopic,
  Korean, Japanese (Hiragana or Katakana, not Han) or Thai text
  repeating one of the lines twice. Here’s an example in Syriac:

  ܡܠܬܐ
  ܒܝܬܐ
  ܒܪܢܫܐ
  ܡܠܬܐ

  Sort produces the following:

  ܡܠܬܐ
  ܒܝܬܐ
  ܡܠܬܐ
  ܒܪܢܫܐ

  Here strings are ordered only according to their length but not
  characters. Even the two instances of the word ܡܠܬܐ are found on non-
  adjacent lines (1 and 3). The expected sort order based on Unicode
  points would be:

  ܒܝܬܐ
  ܒܪܢܫܐ
  ܡܠܬܐ
  ܡܠܬܐ

  If you further pass sort’s output to uniq, it produces the following:

  ܡܠܬܐ
  ܒܪܢܫܐ

  Here the word on line 2 ܒܝܬܐ is completely lost since, like sort, uniq
  seems to consider all Syriac strings of equal length as the same.

  Although this issue affects locale, I think it is not a locale issue
  per se, since perl seems to handle similar cases expectedly. For
  instance, the following command produces the expected result:

  perl -CDS -e 'use locale; use utf8; @str = ("ܡܠܬܐ", "ܒܝܬܐ", "ܒܪܢܫܐ",
  "ܡܠܬܐ"); foreach $i (sort @str) { print "$i\n"; }'

  Curiously enough, codepoints in Plane 1 seem to count as two
  codepoints of the basic plane, so that if you sort | uniq the
  following (six codepoints of Syriac and three codepoints of
  Phoenician):

  ܥܠܝܟܘܢ
  ँउक

  you get ”ܥܠܝܟܘܢ" as the result whereas ”ँउक” is lost. This is of
  course due to the UTF-8 representation of Plane 1 characters as two
  surrogate characters on the basic plane.

  Also curiously, LTR scripts seem to conflate with each other and RTL
  scripts among themselves but not across the directionality line, so
  that if you sort | uniq the following (three codepoints each in
  Ethiopic, Hangul, Syriac, Hiragana and Thai):

  ዘመን
  스물셋
  ܐܢܐ
  わたし
  ฟ้า

  you are left with:

  ܐܢܐ
  ዘመን

  That’s one line of Syriac and one line of Ethiopic; everything else
  was lost. This issue does not seem to affect most Indic scripts
  (Devanagari, Bengali, Telugu etc.) or Arabic. For CJK, things work as
  expected for the main Unicode block (4E00..9FFF) but not for Extension
  A (3400..4DBF, such as 㗖 or 㡘 or 㰋). For Greek, monotonic accents work
  fine but all polytonic letters are conflated (αὐλὸς and αὐλῆς conflate
  to αὐλῆς). For Hebrew, letters and vowel marks work fine but
  cantillation marks are conflated.

  
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  coreutils:
Installed: 8.28-1ubuntu1
Candidate: 8.28-1ubuntu1
Version table:
   *** 8.28-1ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: coreutils 8.28-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  3 10:13:06 2018
  InstallationDate: Installed on 2017-02-13 (474 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: coreutils
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1774857/+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 1585084] Re: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner)

2018-12-08 Thread R

Nope, the same issue reappeared on my machine on the next day. So it was
not due to the cabling. Ubuntu 18.04 by the way.

It persisted across multiple reboots, but disappeared when I turned the
machine off and then immediately turned it back on again. Hardware
issue? I guess hdajackretask is the way to go.

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

Title:
Volume notification keeps popping up constantly (the notify-OSD bubble
on top-right corner)

Status in pulseaudio package in Ubuntu:
Confirmed

Bug description:
I upgraded to Ubuntu 16.04 yesterday, I did a clean install while
preserving the home directory which is mounted in a separate
partition. Even during the installation I had constant volume
notification bubble appearing on the top-right corner of my screen, it
would come and go about twice every minute. I just thought it was due
to installing hardware drivers or something but the problem persisted
even when I booted into the freshly installed system. I did some
searching and two users reported the exact problem. And one more
suggested this happens because constant disconnect and reconnect of
the sound card which makes sense as the sound settings flashes briefly
during every popup. Someone on IRC suggested to kill pulseaudio and
thus restart it, that does not fix the issue. I also tried the Live
environment thinking it might be due to some old config files in home
partition (which was preserved during upgrade), but this problem
happens in the live environment as well, which makes sense because it
was present during installation as well.

Users with the same issue:
http://ubuntuforums.org/showthread.php?t=2323815
http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04

http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: sidd 1651 F pulseaudio
/dev/snd/controlC0: sidd 1651 F pulseaudio
/dev/snd/controlC1: sidd 1651 F pulseaudio
CurrentDesktop: Unity
Date: Tue May 24 12:31:12 2016
InstallationDate: Installed on 2016-05-23 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/23/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0705
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+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 1807516] [NEW] package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

2018-12-08 Thread Laryx Decidua

Public bug reported:

This happened when I tried to upgrade from 16.04.4 LTS to 18.04.1 LTS
using the `do-release-upgrade` command on a Rock64 board (arm64
architecture, see https://www.pine64.org/?page_id=7147). I rebooted
afterwards and the board claims that it was upgraded to 18.04.1 LTS.
Appears to function normally.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3.5
Uname: Linux 4.4.132-1075-rockchip-ayufan-ga83beded8524 aarch64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: arm64
Date: Sat Dec  8 14:12:29 2018
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-12-08 (0 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package arm64 bionic

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

Title:
  package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  This happened when I tried to upgrade from 16.04.4 LTS to 18.04.1 LTS
  using the `do-release-upgrade` command on a Rock64 board (arm64
  architecture, see https://www.pine64.org/?page_id=7147). I rebooted
  afterwards and the board claims that it was upgraded to 18.04.1 LTS.
  Appears to function normally.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3.5
  Uname: Linux 4.4.132-1075-rockchip-ayufan-ga83beded8524 aarch64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: arm64
  Date: Sat Dec  8 14:12:29 2018
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-12-08 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1807516/+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 1807262] Re: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp

This bug was fixed in the package nova -
2:19.0.0~b1~git2018120609.c9dca64fa6-0ubuntu1

---
nova (2:19.0.0~b1~git2018120609.c9dca64fa6-0ubuntu1) disco; urgency=medium

  * d/tests/control, d/tests/nova-daemons: Switch to using mysql-server
databases in autopkgtests.
  * New upstream snapshot for OpenStack Stein.
  * d/control: Ensure python3-migrate version is compatable with sqlite>=3.26
(LP: #1807262).

 -- Corey Bryant   Thu, 06 Dec 2018 09:31:17
-0500

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

Title:
  stein unit tests fail with sqlalchemy.exc.NoSuchTableError:
  migration_tmp

Status in sqlalchemy-migrate:
  New
Status in cinder package in Ubuntu:
  Triaged
Status in migrate package in Ubuntu:
  Fix Released
Status in nova package in Ubuntu:
  Fix Released
Status in sqlite3 package in Ubuntu:
  Invalid

Bug description:
  Several tests that use sqlite fail with:
  "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently
  hitting this with nova and cinder packages in disco.

  Note this started sometime after 11/19 when nova
  2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built
  successfully at the time).

  After doing some digging this appears to occur with libsqlite3-0
  3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some
  more details on that, shown by running a failing unit test from the
  cinder package: https://paste.ubuntu.com/p/hsnQFQD572/

  Update: The test in the paste above also works successfully with
  libsqlite3-0 3.25.3-2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sqlalchemy-migrate/+bug/1807262/+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 1807262] Re: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp

This bug was fixed in the package migrate - 0.11.0-3ubuntu1

---
migrate (0.11.0-3ubuntu1) disco; urgency=medium

  * d/p/use-legacy-alter-sqlite.patch: Cherry-picked from upstream
gerrit review (https://review.openstack.org/#/c/623564/) to ensure
compatability with sqlite >= 3.26 (LP: #1807262).

 -- Corey Bryant   Fri, 07 Dec 2018 14:16:59
-0500

** Changed in: migrate (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: nova (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  stein unit tests fail with sqlalchemy.exc.NoSuchTableError:
  migration_tmp

Status in sqlalchemy-migrate:
  New
Status in cinder package in Ubuntu:
  Triaged
Status in migrate package in Ubuntu:
  Fix Released
Status in nova package in Ubuntu:
  Fix Released
Status in sqlite3 package in Ubuntu:
  Invalid

Bug description:
  Several tests that use sqlite fail with:
  "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently
  hitting this with nova and cinder packages in disco.

  Note this started sometime after 11/19 when nova
  2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built
  successfully at the time).

  After doing some digging this appears to occur with libsqlite3-0
  3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some
  more details on that, shown by running a failing unit test from the
  cinder package: https://paste.ubuntu.com/p/hsnQFQD572/

  Update: The test in the paste above also works successfully with
  libsqlite3-0 3.25.3-2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sqlalchemy-migrate/+bug/1807262/+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 1799947] Re: [radeon] Application windows in 18.04.01 go black but launcher is still visible

2018-12-08 Thread Paul Chambre

I saw what looks like the same issue under Wayland today. It was
slightly different than what I had seen before in that I had one window
(Chrome) that wasn't black. All others were. The issue started when I
clicked to upload a file to a web page. The Chrome window went subdued,
which it normally will do when it's launching the file chooser to select
a file to upload, but the file chooser came up all black, and Chrome
remained subdued and unresponsive (at least in that tab). Other
application windows were also all black, including newly launched ones
(tried another Files and also a Terminal window).

Logging out and logging back in corrected the behavior.

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

Title:
  [radeon] Application windows in 18.04.01 go black but launcher is
  still visible

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Intermittently and randomly, all application windows will go black.
  They are still there, and can be interacted with with keyboard
  shortcuts or if you know where to click with the mouse, but they are
  not drawn.

  The launcher itself is still displayed.

  Clicking Show Applications briefly draws the application window before
  switching to the background and application icons. The application
  icons are shown correctly. Selecting one switches to a black window
  for that application. The application window is again briefly
  displayed when dismissing the application icons by again clicking Show
  Applications.

  TTYs work normally.

  Killing gnome (from another TTY) and allowing it to relaunch results
  in a normal display again.

  This is being seen on an hp 6910p. This system also exhibits a
  corrupted lock screen since upgrade to 18.04.01. Neither of these
  behaviors were seen during two years running 16.04.01.

  Chrome is being used. Current 70.00.3538.77 (64-bit). Chrome is the
  most commonly used application on this machine, so it is possible that
  the behavior is being triggered by Chrome, however, the behavior
  affects all applications, including system applications like software
  update and terminal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799947/+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 1807510] [NEW] package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to install/upgrade: problèmes de dépendances - laissé non configuré

2018-12-08 Thread Stephane SAINTILLAN

Public bug reported:

i have no detail sorry

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
AptOrdering:
 libssh-4:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sun Dec  2 10:56:15 2018
DpkgHistoryLog:
 Start-Date: 2018-12-02  10:56:11
 Commandline: /usr/bin/unattended-upgrade
 Upgrade: libssh-4:amd64 (0.8.0~20170825.94fa1e38-1ubuntu0.1, 
0.8.0~20170825.94fa1e38-1ubuntu0.2)
ErrorMessage: problèmes de dépendances - laissé non configuré
InstallationDate: Installed on 2018-11-04 (34 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: glib2.0
Title: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to 
install/upgrade: problèmes de dépendances - laissé non configuré
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to
  install/upgrade: problèmes de dépendances - laissé non configuré

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  i have no detail sorry

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   libssh-4:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Dec  2 10:56:15 2018
  DpkgHistoryLog:
   Start-Date: 2018-12-02  10:56:11
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: libssh-4:amd64 (0.8.0~20170825.94fa1e38-1ubuntu0.1, 
0.8.0~20170825.94fa1e38-1ubuntu0.2)
  ErrorMessage: problèmes de dépendances - laissé non configuré
  InstallationDate: Installed on 2018-11-04 (34 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: glib2.0
  Title: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to 
install/upgrade: problèmes de dépendances - laissé non configuré
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1807510/+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 1804330] Re: seccomp preventing package installs

2018-12-08 Thread Charles Baillie

This was fixed by removing microsoft scep software. Nothing to do with
seccomp in the end.

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

Title:
  seccomp preventing package installs

Status in libseccomp package in Ubuntu:
  New

Bug description:
  I'm not sure exactly what the problem is but on our 18.04 server installing 
packages has become an issue. For apt packages the workaround is:
  sudo MAN_DISABLE_SECCOMP=1 apt install 

  But I recently tried to install rstudio server with and without
  passing the seccomp environment:

  sudo MAN_DISABLE_SECCOMP=1 gdebi rstudio-server-1.1.463-amd64.deb

  and keep getting this error:

   error[4e0c]: Cannot connect to /tmp/scep.sock: Permission denied

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1804330/+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 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

This bug was fixed in the package cups - 2.2.9-4

---
cups (2.2.9-4) unstable; urgency=medium

  * Cherry-pick from upstream:
- Fix handling of MaxJobTime 0
  (Issue #5438, LP: #1804576, Closes: #915724)

 -- Didier Raboud   Thu, 06 Dec 2018 19:05:22 +0100

** Changed in: cups (Ubuntu Disco)
   Status: In Progress => Fix Released

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

Title:
  MaxJobTime=0 results in jobs being cancelled immediately instead of
  never

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Trusty:
  Invalid
Status in cups source package in Xenial:
  In Progress
Status in cups source package in Bionic:
  In Progress
Status in cups source package in Cosmic:
  In Progress
Status in cups source package in Disco:
  Fix Released
Status in cups package in Debian:
  Fix Released

Bug description:
  [Impact]

   Setting the cupsd option MaxJobTime to 0 should make the server wait 
indefinitely for the job to be ready for print. Instead, after updating 
job-cancel-after option with MaxJobTime=0 value it results in immediate 
cancelling.
  This leads to problems with using filters that take some time to process - 
the user needs to set MaxJobTime to a ridiculously high value to ensure the job 
is not going to get cancelled instead of just disabling the cancelling timeout.

  [Test Case]

   1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf.
   2. Setup a filter that takes at least several seconds to process.
  (please find a sample imagetopdf wrapper introducing 5s delay)
   3. Submit a print job matching the filter, e.g.
  lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper

  Expected result:
  The job is printed after the 5s delay.

  Actual result:
  The job is cancelled.

  [Regression Potential]

   The scope of the change is limited to fixing the MaxJobTime handling
   in scheduler/job.c and scheduler/printers.c. There should be no
   difference in behavior except for the special value of MaxJobTime=0.

  [Other Info]
  Original bug description:

  When using CUPS filters, these filters can take a few seconds to
  complete.

  In this case no documents are allowed to be lost on printing failures,
  so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu
  14.04.

  With cups on 18.04, you get the following message in /var/log/cups/error_log 
whenever the filter takes a little longer:
  I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds.

  Then, the job is deleted and lost.

  "MaxJobTime 0" is documented as "indefinite wait", but apparently cups
  treats is as "wait almost not at all".

  This issue appears to have also been filed upstream:
  https://github.com/apple/cups/issues/5438

  Temporary workaround is to set the MaxJobTime to a very large value
  instead (e.g. 3 years)

  Trusty is not affected by this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1804576/+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 1804330] Re: seccomp preventing package installs

2018-12-08 Thread Norbert

** Tags added: bionic

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

Title:
  seccomp preventing package installs

Status in libseccomp package in Ubuntu:
  New

Bug description:
  I'm not sure exactly what the problem is but on our 18.04 server installing 
packages has become an issue. For apt packages the workaround is:
  sudo MAN_DISABLE_SECCOMP=1 apt install 

  But I recently tried to install rstudio server with and without
  passing the seccomp environment:

  sudo MAN_DISABLE_SECCOMP=1 gdebi rstudio-server-1.1.463-amd64.deb

  and keep getting this error:

   error[4e0c]: Cannot connect to /tmp/scep.sock: Permission denied

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1804330/+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 1458204] Re: removing kernels should not require a restart afterward

2018-12-08 Thread Barry Kolts

@tjaalton

My 16.04 server doesn't have update-notifier installed but does have
update-notifier-common installed. If I install update-notifier from
propose it will install a slew of other packages. If I install update-
notifier-common from propose it just installs the new update-notifier-
common version 3.168.10. So should i test update-notifier-common instead
of update-notifier?

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

Title:
  removing kernels should not require a restart afterward

Status in unattended-upgrades:
  New
Status in update notifier:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in update-notifier source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Won't Fix
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in update-notifier source package in Artful:
  Won't Fix

Bug description:
  [Impact]

  The rationale behind the SRU to Xenial is that with latest unattended-
  upgrades SRU it starts removing unused kernels, but all older kernels
  are not removed in a single run. With update-notifier and u-u not
  fixed they place /var/run/reboot-required asking for a reboot when it
  is not needed.

  
  [Test Case]

  1. Perform a kernel upgrade normally via "apt-get dist-upgrade".
  2. Reboot.
  3. Run "apt-get autoremove" to delete the old kernel packages.
  4. "System Notification Helper" now reports that the computer requires a 
reboot.

  The "autoremove" operation shouldn't require a reboot, logically
  speaking, because it's just removing files that are unused by the OS.

  [ Regression Potential ]

  If the check for skipping placing the /var/run/reboot-required file is too 
broad it may make kernel upgrades fail to ask for reboot. The fix changes a 
hook called by maintainer scripts and a failure in the hook can make kernel 
package installations fail.
  The fix is simple and was tested in several releases thus regressing in these 
ways is unlikely.

  [ Original Bug Text ]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May 23 12:47:15 2015
  InstallationDate: Installed on 2013-08-31 (629 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago)
  ---
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308
  InstallationDate: Installed on 2013-08-31 (632 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-53-generic N/A
   linux-backports-modules-3.13.0-53-generic  N/A
   linux-firmware 1.127.12
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago)
  UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 08/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   :

[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)

2018-12-08 Thread Bug Watch Updater

** Changed in: debian-installer
   Status: Unknown => Fix Released

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

Title:
  installer stock images fail to validate any HTTPS certificates (ca-
  certificates missing)

Status in debian-installer:
  Fix Released
Status in ca-certificates package in Ubuntu:
  Invalid
Status in debian-installer package in Ubuntu:
  Fix Released
Status in ca-certificates source package in Trusty:
  In Progress
Status in debian-installer source package in Trusty:
  In Progress
Status in ca-certificates source package in Xenial:
  In Progress
Status in debian-installer source package in Xenial:
  In Progress
Status in ca-certificates source package in Bionic:
  Invalid
Status in debian-installer source package in Bionic:
  Fix Committed
Status in ca-certificates source package in Cosmic:
  Invalid
Status in debian-installer source package in Cosmic:
  Fix Committed
Status in ca-certificates source package in Disco:
  Invalid
Status in debian-installer source package in Disco:
  Fix Released
Status in debian-installer package in Debian:
  Fix Released

Bug description:
  [Impact]

   * The installer stock images fail to validate any HTTPS
     certificates because ca-certificates is not available
     in the installer environment.

   * This causes wget/download errors for preseed files on
     HTTPS servers (or HTTP servers that redirect to HTTPS,
     which are increasingly common nowadays - e.g., GitHub)
     and theoretically any other files that are downloaded
     with d-i-utils/fetch-url/wget.

   * The fix is to ship ca-certificates-udeb in installer
     stock images.

   * Debian already ships ca-certificate-udeb in the stock
     installer images; the fix is applied since Jan 2017.
     (reference: Debian Bug #842040 / d-i commit 2f00c51a [1])

  [Test Case]

   * In the installer shell:

     ~ # wget http://github.com  # or https://github.com

     - FAIL if ca-certificates-udeb is missing:
   "ERROR: cannot verify github.com's certificate, <...>'

     - PASS if ca-certificates-udeb is available
   "Saving to: 'index.html'"

   * Test steps with virt-install and netboot images
     are provided in the comments, for each release.

  [Regression Potential]

   * Low. This just adds the ca-certificates files in
     /etc/ssl/certs and symlink in /usr/lib/ssl/certs,
     so only tools looking for that would be affected.

   * Apparently only wget checks for/uses those files,
     and the difference in behavior is download errors
     no longer occur.

  [Notes]

   * The ca-certificates-udeb is not currently present
     in the Ubuntu 'main' component, but in 'universe',
     despite the normal deb being in 'main'.

     However, when rebuilding in a PPA it goes into
     'main' accordingly, and can be used by default
     by debian-installer (otherwise, UDEB_COMPONENTS
     has to be modified to include universe/d-i).

   * So this fix includes a no-change-rebuild for the
     ca-certificates package, in order to publish the
     udeb in the archive (at least in PPA for testing).

     Hopefully that can be sorted out for this fix
     to work out.

   * The ca-certificates and debian-installer builds
     have been done in a PPA using all architectures,
     and testing has been done with the amd64 images.

   * This fix is requested for Bionic, Cosmic, Disco
 at least.

   * The fix for Trusty and Xenial needed a little
     bit more work to build/ship the (new) udeb.
 (reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])

     It would be good to have them too if at all possible.

  [1] 
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
  [2] 
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4

  [Debugging]

  For debugging purposes, one can install strace-udeb in the installer
  to verify wget's stat() calls to /usr/lib/ssl/certs.

  ~ # anna-install strace-udeb

  ~ # strace -e stat wget -O- https://github.com >/dev/null
  ...
  Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, 
st_size=20, ...}) = 0
  140.82.118.3, 140.82.118.4
  Connecting to github.com|140.82.118.3|:443... connected.
  stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such 
file or directory)
  stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such 
file or directory)
  stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such 
file or directory)
  ERROR: cannot verify github.com's certificate, issued by 'CN=DigiCert SHA2 
Extended Validation Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US':
    Unable to locally verify the issuer's authority.
  To connect to github.com insecurely, use `--no-check-certificate'.
  +++ exited with 5 +++
  ~ #

[Touch-packages] [Bug 1807504] Re: Evince segfaults when opening PDF

2018-12-08 Thread Lou

All pdf files are NOT affected by this bug.

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

Title:
  Evince segfaults when opening PDF

Status in poppler package in Ubuntu:
  New

Bug description:
  After a recent poppler update neither Evince nor Qpdfview will open
  pdf files that opened before the update.  These files open properly
  using gv (which uses Ghostview instead of poppler).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libpoppler73 0.62.0-2ubuntu2.4
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Dec  8 08:48:01 2018
  InstallationDate: Installed on 2016-08-25 (834 days ago)
  InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: poppler
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (116 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1807504/+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 1807504] [NEW] Evince segfaults when opening PDF

2018-12-08 Thread Lou

Public bug reported:

After a recent poppler update neither Evince nor Qpdfview will open pdf
files that opened before the update.  These files open properly using gv
(which uses Ghostview instead of poppler).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libpoppler73 0.62.0-2ubuntu2.4
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic i686
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: i386
CurrentDesktop: XFCE
Date: Sat Dec  8 08:48:01 2018
InstallationDate: Installed on 2016-08-25 (834 days ago)
InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: poppler
UpgradeStatus: Upgraded to bionic on 2018-08-14 (116 days ago)

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


** Tags: apport-bug bionic i386

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

Title:
  Evince segfaults when opening PDF

Status in poppler package in Ubuntu:
  New

Bug description:
  After a recent poppler update neither Evince nor Qpdfview will open
  pdf files that opened before the update.  These files open properly
  using gv (which uses Ghostview instead of poppler).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libpoppler73 0.62.0-2ubuntu2.4
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Dec  8 08:48:01 2018
  InstallationDate: Installed on 2016-08-25 (834 days ago)
  InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: poppler
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (116 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1807504/+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 1807502] [NEW] hello

2018-12-08 Thread stevan

Public bug reported:

hello

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec  8 14:45:56 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:832a]
InstallationDate: Installed on 2018-12-08 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: HP HP 250 G6 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/25/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.24
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 832A
dmi.board.vendor: HP
dmi.board.version: 23.40
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd09/25/2017:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn832A:rvr23.40:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5336AN HP 200
dmi.product.name: HP 250 G6 Notebook PC
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  hello

Status in xorg package in Ubuntu:
  New

Bug description:
  hello

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  8 14:45:56 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:832a]
  InstallationDate: Installed on 2018-12-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP 250 G6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 832A
  dmi.board.vendor: HP
  dmi.board.version: 23.40
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd09/25/2017:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn832A:rvr23.40:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN HP 200
  dmi.product.name: HP 250 G6 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:

[Touch-packages] [Bug 1793410] Re: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working

2018-12-08 Thread James Pollock

Hi Sebastien,

Yes I would be happy to manually patch the driver. Is it just a case of
replacing my existing patch_realtek.c file with the one in the branch
and adding that line? Or is the patching process more involved?

Thanks,

James

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

Title:
  [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal
  microphone not working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Recently bought a new Acer Swift 3 laptop and installed Ubuntu 18.04
  on it. Everything works except the internal microphone. I have also
  tested with an external microphone and this didn't work either.

  I have worked my way through all the suggested solutions I could find,
  including trying to reconfigure the pins using hdajacketask. In
  pavucontrol I have options for Internal Microphone and Microphone
  (unplugged) but the internal mic only captures static noise.

  The latest HD-Audio Codec-Specific Models has configurations for
  alc255-acer and alc256 for some other models, but setting options snd-
  hda-intel model=MODEL in /etc/modprobe.d/alsa-base.conf does not solve
  the issue with any of these.

  Some info -

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-
  LP HD Audio (rev 21)

  
  cat /proc/asound/cards:

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xdf1a8000 irq 127

  
  dmesg | grep snd:

  [3.944593] snd_hda_core: loading out-of-tree module taints kernel.
  [3.956337] snd_soc_skl: Unknown symbol snd_hdac_display_power (err 0)
  [3.956422] snd_soc_skl: Unknown symbol snd_hdac_i915_exit (err 0)
  [4.000880] snd_hda_intel :00:1f.3: Probing card using HDA DKMS, 
version 0.201808050301~ubuntu18.04.1
  [4.000895] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [4.013061] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [4.013063] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [4.013065] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [4.013068] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
  [4.013069] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12

  
  info on node 12 from cat /proc/asound/card*/codec\#*:

  Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In
Control: name="Internal Mic Boost Volume", index=0, device=0
  ControlAmp: chs=3, dir=In, idx=0, ofs=0
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals:  [0x02 0x02]
Pincap 0x0020: IN
Pin Default 0x4000: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0x0, Sequence = 0x0
Pin-ctls: 0x20: IN
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0

  Let me know if you need any other information.

  James

  ---

  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True
  dmi.bios.date: 06/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Default string
  dmi.board.name: Erdinger_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd06/22/2018:svnAcer:pnSwiftSF315-52:pvrV1.04:rvnKBL:rnErdinger_KL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF315-52
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793410/+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 1807499] [NEW] 30 seconds boot delay when root fs is on lvm

2018-12-08 Thread Eduard Hasenleithner

Public bug reported:

On my system the root filesystem is located on a logical volume. I have
constant boot delay of 30 seconds. My current conclusion is that this
problem exists due to lvm performing the initramfs-tools local-top
initialization incorrectly.

According to initramfs-tools(8):
local-top OR nfs-top After these scripts have been executed, the root  device  
node is expected to be present (local) or the network interface is expected to 
be usable (NFS).

But what /usr/share/initramfs-tools/scripts/local-top/lvm2 is simply try
to activate the requested root volume by means of scanning the (at that
moment) available block devices. What happens on my system is that
local-top/lvm2 is executed before the pv block device (SATA-SSD) shows
up. Then initramfs-tools calls the wait-for-root executable which waits
for the root device node notification via udev.

This has a (minimum) timeout of 30 seconds configured. This timeout is
exceeded since nothing will make the root volume device to be created.
Then later (I guess in local-block) the root volume device is created
(since the pv is available).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lvm2 2.02.176-4.1ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec  8 13:52:06 2018
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
SourcePackage: lvm2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lvm2 (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 lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1807499

Title:
  30 seconds boot delay when root fs is on lvm

Status in lvm2 package in Ubuntu:
  New

Bug description:
  On my system the root filesystem is located on a logical volume. I
  have constant boot delay of 30 seconds. My current conclusion is that
  this problem exists due to lvm performing the initramfs-tools local-
  top initialization incorrectly.

  According to initramfs-tools(8):
  local-top OR nfs-top After these scripts have been executed, the root  device 
 node is expected to be present (local) or the network interface is expected to 
be usable (NFS).

  But what /usr/share/initramfs-tools/scripts/local-top/lvm2 is simply
  try to activate the requested root volume by means of scanning the (at
  that moment) available block devices. What happens on my system is
  that local-top/lvm2 is executed before the pv block device (SATA-SSD)
  shows up. Then initramfs-tools calls the wait-for-root executable
  which waits for the root device node notification via udev.

  This has a (minimum) timeout of 30 seconds configured. This timeout is
  exceeded since nothing will make the root volume device to be created.
  Then later (I guess in local-block) the root volume device is created
  (since the pv is available).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lvm2 2.02.176-4.1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  8 13:52:06 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1807499/+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 1803059] Re: Nullpointer dereference

2018-12-08 Thread Miguel

I am getting reproducible crashes after update from poppler
0.62.0-2ubuntu2.2 to poppler 0.62.0-2ubuntu2.4

Test PDF file attached.

Crashed experiences since following upgrades:
libpoppler-cpp-dev (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4
libpoppler-cpp0v5 (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4
libpoppler-dev (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4
libpoppler-glib8 (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4
libpoppler-private-dev (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4
libpoppler-qt5-1 (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4
libpoppler73 (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4
poppler-utils (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4

Reverting to previous versions fixes the crashes.

System: 18.04.1 LTS bionic (32 bit)
Linux 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:32:10 UTC 2018 i686 i686 
i686 GNU/Linux
PC

gdb trace:
Starting program: /usr/bin/evince 
Bureau/evince/test_CGV_FORFAIT_hors_opt_20170308.pdf
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xb5b82b40 (LWP 6602)]
[New Thread 0xb51ffb40 (LWP 6603)]
[New Thread 0xb47ffb40 (LWP 6604)]
warning: Error reading shared library list entry at 0x6840
warning: Error reading shared library list entry at 0x5a60
[New Thread 0xb3c77b40 (LWP 6608)]
warning: Error reading shared library list entry at 0x75e0
[New Thread 0xb1356b40 (LWP 6609)]
warning: Error reading shared library list entry at 0x5130
warning: Error reading shared library list entry at 0x97b0

Thread 6 "EvJobScheduler" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb1356b40 (LWP 6609)]
0xb096a379 in Parser::makeStream(Object&&, unsigned char*, CryptAlgorithm, int, 
int, int, int, bool) () from /usr/lib/i386-linux-gnu/libpoppler.so.73


** Attachment added: "With poppler 0.62.0-2ubuntu2.4, evince and other PDF 
readers will immediately crash on my system"
   
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1803059/+attachment/5220277/+files/test_CGV_FORFAIT_hors_opt_20170308.pdf

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

Title:
  Nullpointer dereference

Status in poppler package in Ubuntu:
  Fix Committed
Status in poppler source package in Bionic:
  Fix Released
Status in poppler source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  Evince segfaults on some pdf documents

  * Test case
  Download and try to open 
https://bugs.freedesktop.org/attachment.cgi?id=138927 with evince, it shouldn't 
segfault

  * Regression potential
  Nothing special to test, make sure evince still opens pdfs without issue

  -

  System Info: Linux zero 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10
  10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  Evince version: GNOME Document Viewer 3.28.4

  While fuzzing evince v3.28.4, on linux 4.15.0-38-generic (Ubuntu 18.04
  LTS), a null-pointer dereference was observed, initially this was
  reported to evince but the evince team advised that the issue is in
  poppler, the library used by evince to render PDF, poppler version:
  0.62.0-2ubuntu2.2 is vulnerable to null-pointer dereference, however
  the issue is already fixed in poppler 0.70, but this will still crash
  your evince v3.28.4 in ubuntu if poppler is not updated to v.0.70.

  Fuzzing result showing a very important vulnerability in a package
  currently shipped by a major Linux distribution is still of interest,
  even if that Linux distribution does not package the latest released
  upstream version. I think Ubuntu is still using,

  Source: poppler
  Version: 0.62.0-2ubuntu2.2

  So, most of the systems will be affected to this issue.

  Upstream: https://gitlab.freedesktop.org/poppler/poppler/issues/664

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1803059/+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 1368411] Re: Cannot insert IPV6 rule before IPV4 rules

2018-12-08 Thread Bug Watch Updater

** Changed in: ufw (Debian)
   Status: Fix Released => New

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

Title:
  Cannot insert IPV6 rule before IPV4 rules

Status in ufw:
  New
Status in ufw package in Ubuntu:
  Confirmed
Status in ufw package in Debian:
  New

Bug description:
  I am unable to insert any rules concerning IPV6 before IPV4 rules. Thus, when 
IPV4 rules are numbered 1 to 5 and IPV6 rules are numbered  6 to 10,  the 
following command:
  [code]
  ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1
  [/code]
  errors with "ERROR: Invalid position '1'".

  However, the command
  [code]
  ufw insert 6 deny from 2a02:2210:12:a:b820:fff:fea2:25d1
  [/code]
  succeeds.

  In my case, this poses a problem, since I am trying to insert rules
  from a script against brute force attacks. The script needs to insert
  blocking rules before a number of other rules that open up some ports
  (since the order of rules is important in ufw). However since the
  number of IPV4 rules will be changing all the time, the position of
  the first available number for an IPV6 address is hard to determine.

  Proposed solution: either allow IPV6 rules to precede IPV4 rules, or
  implement a keyword defining the first available position; e.g. "ufw
  insert first deny from 2a02:2210:12:a:b820:fff:fea2:25d1".

  BTW: this was all figured out with ufw version 0.31.1-1, Ubuntu
  12.04.5 LTS,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ufw/+bug/1368411/+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 1404172] Re: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory

2018-12-08 Thread Gannet

Still on 18.04 (Xubuntu Linux i386).

** Tags added: bionic

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

Title:
  lightdm: PAM unable to dlopen(pam_kwallet.so):
  /lib/security/pam_kwallet.so: cannot open shared object file: No such
  file or directory

Status in One Hundred Papercuts:
  Confirmed
Status in Light Display Manager:
  Confirmed
Status in systemd:
  New
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  auth.log complaints:

  Dec 19 07:24:42 u32 lightdm: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Dec 19 07:24:42 u32 lightdm: PAM adding faulty module: pam_kwallet.so
  Dec 19 07:24:42 u32 lightdm: pam_unix(lightdm-greeter:session): session 
opened for user lightdm by (uid=0)
  Dec 19 07:24:42 u32 systemd-logind[656]: New session c1 of user lightdm.
  Dec 19 07:24:42 u32 systemd: pam_unix(systemd-user:session): session opened 
for user lightdm by (uid=0)
  Dec 19 07:24:46 u32 lightdm: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Dec 19 07:24:46 u32 lightdm: PAM adding faulty module: pam_kwallet.so
  Dec 19 07:24:46 u32 lightdm: pam_succeed_if(lightdm:auth): requirement "user 
ingroup nopasswdlogin" not met by user "oem"
  Dec 19 07:24:53 u32 lightdm: pam_unix(lightdm-greeter:session): session 
closed for user lightdm
  Dec 19 07:24:53 u32 lightdm: pam_unix(lightdm:session): session opened for 
user oem by (uid=0)

  
  As per lp:1309535 #18 comment such 'warnings' should be silenced (as they 
scared unawared users about the both needs of pam's gnome/kde)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.13.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-7.8-generic 3.18.0
  Uname: Linux 3.18.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Fri Dec 19 10:47:07 2014
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1404172/+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 1788520] Re: multiple boot problems if /usr is on a logical volume