[Touch-packages] [Bug 1898869] Re: System slow on booting

2020-10-07 Thread Daniel van Vugt
Again I can't figure this out, sorry. But it looks like systemd or snapd
people might have some idea.

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** Package changed: ubuntu => snapd (Ubuntu)

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

Title:
  System slow on booting

Status in snapd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I have installed a Kubuntu 20.04.1 for my grandma, the system is slow
  to boot, takes between a minute 30 seconds to two minutes to display
  the Plasma Desktop. I am attaching a journalctl log and a systemd-
  bootchart img.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Wed Oct  7 15:26:27 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-48-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1043:14dd]
  InstallationDate: Installed on 2020-09-22 (14 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b404 Chicony Electronics Co., Ltd USB2.0 HD UVC 
WebCam
   Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. Broadcom 
BCM43142A0 Bluetooth Device
   Bus 001 Device 002: ID 1c4f:0034 SiGma Micro Usb Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X551MA
  ProcEnviron:
   LANGUAGE=ru:en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=bg_BG.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash 
init=/lib/systemd/systemd-bootchart vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X551MA.515
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X551MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX551MA.515:bd04/15/2015:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X551MA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+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 1898878] Re: Ubuntu slow boot

2020-10-07 Thread Daniel van Vugt
I'm not sure what to make of that. Perhaps systemd or snapd people can
help...

** Package changed: linux (Ubuntu) => snapd (Ubuntu)

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: snapd (Ubuntu)
   Status: Confirmed => New

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

Title:
  Ubuntu slow boot

Status in snapd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  My PC takes about 2 minutes till Desktop, it's just slow. I am
  attaching logs in hope of seeing if there is a bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-lowlatency 5.4.0-48.52
  ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60
  Uname: Linux 5.4.0-48-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lyubo  2186 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Oct  7 17:00:19 2020
  InstallationDate: Installed on 2020-02-08 (242 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 1bbb:0195 T & A Mobile Phones Mobilebroadband
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A515-51G
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash 
resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality 
init=/lib/systemd/systemd-bootchart vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-lowlatency N/A
   linux-backports-modules-5.4.0-48-lowlatency  N/A
   linux-firmware   1.187.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-20 (169 days ago)
  dmi.bios.date: 01/03/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.02
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmander_KL
  dmi.board.vendor: KBL
  dmi.board.version: V2.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-51G
  dmi.product.sku: 
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer
  mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898878/+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 1898869] Re: System slow on booting

2020-10-07 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => 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/1898869

Title:
  System slow on booting

Status in Ubuntu:
  New

Bug description:
  I have installed a Kubuntu 20.04.1 for my grandma, the system is slow
  to boot, takes between a minute 30 seconds to two minutes to display
  the Plasma Desktop. I am attaching a journalctl log and a systemd-
  bootchart img.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Wed Oct  7 15:26:27 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-48-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1043:14dd]
  InstallationDate: Installed on 2020-09-22 (14 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b404 Chicony Electronics Co., Ltd USB2.0 HD UVC 
WebCam
   Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. Broadcom 
BCM43142A0 Bluetooth Device
   Bus 001 Device 002: ID 1c4f:0034 SiGma Micro Usb Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X551MA
  ProcEnviron:
   LANGUAGE=ru:en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=bg_BG.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash 
init=/lib/systemd/systemd-bootchart vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X551MA.515
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X551MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX551MA.515:bd04/15/2015:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X551MA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1898869/+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 1691908] Re: fstab binds appear as mounts (x-gvfs-hide is being ignored)

2020-10-07 Thread Peter Goodall
This is occurring in Ubuntu 20.04. All my zfs mounts are appearing in my
desktop file-manager. Screenshot attached. A total nuisance.


** Attachment added: "Screenshot from 2020-10-08 09-41-42.png"
   
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1691908/+attachment/5419210/+files/Screenshot%20from%202020-10-08%2009-41-42.png

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

Title:
  fstab binds appear as mounts (x-gvfs-hide is being ignored)

Status in GLib:
  Expired
Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  glib2 version 2.52.2+1+gb8bd46bc8-1 (possibly the version before it as
  well, I haven't tested) causes fstab binds to appear as mounts in
  Nautilus (and in Deepin Dock - Deepin is based on Gnome).

  Downgrading to glib2 and glib2-docs 2.52.0-1 resolves this behaviour.

  I first noted this bug behaviour here:
  https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/452049

  Details of my particular system and issue with what I tried to resolve
  it can be found here:
  https://bbs.archlinux.org/viewtopic.php?pid=1712030#p1712030

  1. Not using Ubuntu. Deepin Desktop 15.4 (Gnome based) on Arch Linux.

   OS: Arch Linux 
   Kernel: x86_64 Linux 4.10.13-1-ARCH
   Shell: bash 4.4.12
   Resolution: 1920x1200
   DE: Deepin 15.4
   WM: Deepin WM
   WM Theme: Arc-Darker
   GTK Theme: Arc-Darker [GTK2/3]
   Icon Theme: deepin
   Font: Noto Sans 11
   CPU: Intel Core i5-6500 @ 4x 3.6GHz [27.8°C]
   GPU: GeForce GTX 950
   RAM: 2598MiB / 15990MiB

  2. 2.52.2+1+gb8bd46bc8-1 (downgrading to 2.52.0-1 removed the
  problem).

  3. Nautilus to list internal physical drives (my SSD and 1TB HDD)
  only.

  4. Nautilus listed my system disk (as expected) but also listed all of
  my fstab binds as removable drives (Downloads, Music, Pictures, Videos
  and Documents although this was not listed as "Documents" but instead
  listed as the HDD label "Farsight"). Adding x-gvfs-hide did not hide
  those drives.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1691908/+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 1783881] Re: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags added: focal

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

Title:
  ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits
  number of processes

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in systemd source package in Bionic:
  New

Bug description:
  As systemd limits the number of processes, this test will fail because
  it can't fork enough processes. That is limited to when the test is
  run after logging as user 1000, then running sudo. I guess that
  logging as root may not cause this to happen.

  # ./testcases/bin/msgstress03 
  Fork failed (may be OK if under stress)
  Fork failed (may be OK if under stress)
  msgstress031  TFAIL  :  msgstress03.c:157:  Fork failed (may be OK if 
under stress)
  #

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+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 1895865] Re: /usr/share/apport/dump_acpi_tables.py:PermissionError:/usr/share/apport/dump_acpi_tables.py@59:dump_acpi_tables:dump_acpi_table

2020-10-07 Thread Brian Murray
The verification passed as we can see there was no Traceback and it
asked for root permissions to run the command.

bdmurray@clean-focal-amd64:~$ dpkg -l apport
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---==
ii  apport 2.20.11-0ubuntu27.10 all  automatically generate 
crash reports for debugging
bdmurray@clean-focal-amd64:~$ /usr/share/apport/dump_acpi_tables.py 
bdmurray@clean-focal-amd64:~$ ubuntu-bug udev

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
... AUTHENTICATING FOR org.freedesktop.policykit.exec ===
Authentication is needed to run `/usr/share/apport/dump_acpi_tables.py' as the 
super user


** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

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

Title:
  
/usr/share/apport/dump_acpi_tables.py:PermissionError:/usr/share/apport/dump_acpi_tables.py@59:dump_acpi_tables:dump_acpi_table

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Released

Bug description:
  Impact
  --
  Users running /usr/share/apport/dump_acpi_tables.py will receive a Traceback 
unless it is called by root.

  Test Case
  -
  1) Run /usr/share/apport/dump_acpi_tables.py
  2) Observe the Traceback in comment #1

  Additionally, running 'ubuntu-bug' about a package which calls
  attach_hardware (which then calls dump_acpi_tables.py) will have a
  Traceback in acpidump.

  1) Run 'ubuntu-bug udev'
  2) Save the report
  3) View the report and see the Traceback from comment #1 in it

  With the version of the package from -proposed you will not receive a
  Traceback in either situation.

  Regression Potential
  
  If the python is bad we could have a different crash.

  Original Description
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu45, the problem page at 
https://errors.ubuntu.com/problem/ad705c1a5e4068bcae9d4261519bac8fac5cb57f 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1895865/+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 1898944] [NEW] package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

2020-10-07 Thread Malcolm Durie
Public bug reported:

Installation gave and error about intramfs-tools and repository being
out of date when upgrading from 18.04LTS to latest 20.04.01.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.3
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Oct  7 23:01:56 2020
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2016-01-11 (1731 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to focal on 2020-10-07 (0 days ago)

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


** Tags: amd64 apport-package focal

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

Title:
  package initramfs-tools 0.136ubuntu6.3 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:
  Installation gave and error about intramfs-tools and repository being
  out of date when upgrading from 18.04LTS to latest 20.04.01.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.3
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Oct  7 23:01:56 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-01-11 (1731 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-10-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1898944/+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 1898944] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2020-10-07 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package initramfs-tools 0.136ubuntu6.3 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:
  Installation gave and error about intramfs-tools and repository being
  out of date when upgrading from 18.04LTS to latest 20.04.01.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.3
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Oct  7 23:01:56 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-01-11 (1731 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-10-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1898944/+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 1892559] Re: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite

2020-10-07 Thread Seth Arnold
Christian, Joy has gone through the bugs and either closed old ones or
made some progress on still-relevant ones. How does it look to you now?
Thanks Joy!

Thanks

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

Title:
  [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite

Status in ccid package in Ubuntu:
  New
Status in opensc package in Ubuntu:
  Incomplete
Status in pam-pkcs11 package in Ubuntu:
  New
Status in pcsc-lite package in Ubuntu:
  New
Status in pcsc-perl package in Ubuntu:
  Invalid
Status in pcsc-tools package in Ubuntu:
  Invalid

Bug description:
  ==> ccid <==
  [Availability]
  ccid is in universe, and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs for ccid are listed in our database.
  Doesn't appear to bind to a socket.
  No privileged executables, but does have udev rules.
  Probably needs a security review.

  [Quality assurance]
  No test suite.
  Does require odd hardware that we'll probably need to buy.
  I don't see debconf questions.
  ccid is well maintained in Debian by upstream author.
  One open wishlist bug in BTS, harmless.

  One open bug in launchpad, not security, but looks very frustrating
  for the users. The upstream author was engaged but it never reached
  resolution.  https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465

  Has a debian/watch file.
  Quilt packaging.

  P: ccid source: no-dep5-copyright
  P: ccid source: package-uses-experimental-debhelper-compat-version 13

  [Dependencies]
  Minimal dependencies, in main

  [Standards compliance]
  Appears to satisfy FHS and Debian policy

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  ccid provides drivers to interact with usb-connected smart card readers.

  ==> libpam-pkcs11 <==
  [Availability]
  Source package pam-pkcs11 is in universe and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs in our database.
  Doesn't appear to bind to sockets.
  No privileged executables (but is a PAM module).
  As a PAM module this will require a security review.

  [Quality assurance]
  The package does not call pam-auth-update in its postinst #1650366
  Does not ask questions during install.
  One Ubuntu bug claims very poor behaviour if a card isn't plugged in.
  No Debian bugs.
  Occasional updates in Debian by long-term maintainer.
  Does require odd hardware that we'll probably need to buy.
  Does not appear to run tests during build.
  Has scary warnings in the build logs.
  Has a debian/watch file.

  Ancient standards version; other smaller lintian messages, mostly
  documentation problems.

  Quilt packaging.

  [Dependencies]
  Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1
  All are in main.

  [Standards compliance]
  The package does not call pam-auth-update in its postinst #1650366
  Otherwise looks to conform to FHS and Debian policies

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  This PAM module can use CRLs and full-chain verification of certificates.
  It can also do LDAP, AD, and Kerberos username mapping.

  ==> libpcsc-perl <==
  [Availability]
  Source package pcsc-perl is in universe, builds for all architectures,
  plus i386

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  There are no cves for pcsc-perl in our database.
  No privileged executables.
  Doesn't appear to bind to sockets.
  Probably needs a security review.

  [Quality assurance]
  Library package not intended to be used directly.
  No debconf questions.
  No bugs in Debian.
  No bugs in Ubuntu.
  Does require odd hardware that we'll probably need to buy.
  Tests exist, not run during the build; probably can't run during the build.
  Includes debian/watch file.
  A handful of lintian issues
  Quilt packaging.

  [Dependencies]
  libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0.
  All are in main.

  [Standards compliance]
  One oddity, Card.pod is stored in 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Chipcard/PCSC/
  Many other perl packages have .pod files in these directory trees so maybe
  it's fine, but it seems funny all the same.

  Otherwise appears to satisfy FHS and Debian policy.

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  

[Touch-packages] [Bug 1731410] Re: package pcscd 1.8.14-1ubuntu1.16.04.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

2020-10-07 Thread Joy Latten
Hi, Is this still an issue? Changing the status to incomplete.

** Changed in: pcsc-lite (Ubuntu)
   Status: New => Incomplete

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

Title:
  package pcscd 1.8.14-1ubuntu1.16.04.1 failed to install/upgrade:
  подпроцесс установлен сценарий post-installation возвратил код ошибки
  1

Status in pcsc-lite package in Ubuntu:
  Incomplete

Bug description:
   sudo apt-get install openvpn easy-rsa
  [sudo] пароль для max: 
  Чтение списков пакетов… Готово
  Построение дерева зависимостей   
  Чтение информации о состоянии… Готово
  Будут установлены следующие дополнительные пакеты:
libccid libpkcs11-helper1 opensc opensc-pkcs11 pcscd
  НОВЫЕ пакеты, которые будут установлены:
easy-rsa libccid libpkcs11-helper1 opensc opensc-pkcs11 openvpn pcscd
  обновлено 0, установлено 7 новых пакетов, для удаления отмечено 0 пакетов, и 
1 пакетов не обновлено.
  Необходимо скачать 1 544 kБ архивов.
  После данной операции, объём занятого дискового пространства возрастёт на 4 
993 kB.
  Хотите продолжить? [Д/н] y
  Пол:1 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 libpkcs11-helper1 
amd64 1.11-5 [44,0 kB]
  Пол:2 http://ru.archive.ubuntu.com/ubuntu xenial/universe amd64 opensc-pkcs11 
amd64 0.15.0-1ubuntu1 [708 kB]
  Пол:3 http://ru.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
libccid amd64 1.4.22-1ubuntu0.1 [85,8 kB]
  Пол:4 http://ru.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 pcscd 
amd64 1.8.14-1ubuntu1.16.04.1 [55,7 kB]
  Пол:5 http://ru.archive.ubuntu.com/ubuntu xenial/universe amd64 opensc amd64 
0.15.0-1ubuntu1 [212 kB]
  Пол:6 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 openvpn 
amd64 2.3.10-1ubuntu2.1 [421 kB]
  Пол:7 http://ru.archive.ubuntu.com/ubuntu xenial/universe amd64 easy-rsa all 
2.2.2-2 [17,4 kB]
  Получено 1 544 kБ за 0с (1 946 kБ/c)
  Предварительная настройка пакетов ...
  Выбор ранее не выбранного пакета libpkcs11-helper1:amd64.
  dpkg: предупреждение: список файлов пакета «resolvconf» отсутствует; 
предполагаем, что на данный момент у пакета нет установленных файлов
  (Чтение базы данных … на данный момент установлен 246061 файл и каталог.)
  Подготовка к распаковке …/libpkcs11-helper1_1.11-5_amd64.deb …
  Распаковывается libpkcs11-helper1:amd64 (1.11-5) …
  Выбор ранее не выбранного пакета opensc-pkcs11:amd64.
  Подготовка к распаковке …/opensc-pkcs11_0.15.0-1ubuntu1_amd64.deb …
  Распаковывается opensc-pkcs11:amd64 (0.15.0-1ubuntu1) …
  Выбор ранее не выбранного пакета libccid.
  Подготовка к распаковке …/libccid_1.4.22-1ubuntu0.1_amd64.deb …
  Распаковывается libccid (1.4.22-1ubuntu0.1) …
  Выбор ранее не выбранного пакета pcscd.
  Подготовка к распаковке …/pcscd_1.8.14-1ubuntu1.16.04.1_amd64.deb …
  Распаковывается pcscd (1.8.14-1ubuntu1.16.04.1) …
  Выбор ранее не выбранного пакета opensc.
  Подготовка к распаковке …/opensc_0.15.0-1ubuntu1_amd64.deb …
  Распаковывается opensc (0.15.0-1ubuntu1) …
  Выбор ранее не выбранного пакета openvpn.
  Подготовка к распаковке …/openvpn_2.3.10-1ubuntu2.1_amd64.deb …
  Распаковывается openvpn (2.3.10-1ubuntu2.1) …
  Выбор ранее не выбранного пакета easy-rsa.
  Подготовка к распаковке …/easy-rsa_2.2.2-2_all.deb …
  Распаковывается easy-rsa (2.2.2-2) …
  Обрабатываются триггеры для libc-bin (2.23-0ubuntu9) …
  Обрабатываются триггеры для man-db (2.7.5-1) …
  Обрабатываются триггеры для systemd (229-4ubuntu21) …
  Обрабатываются триггеры для ureadahead (0.100.0-19) …
  ureadahead will be reprofiled on next reboot
  Настраивается пакет libpkcs11-helper1:amd64 (1.11-5) …
  Настраивается пакет opensc-pkcs11:amd64 (0.15.0-1ubuntu1) …
  Настраивается пакет libccid (1.4.22-1ubuntu0.1) …
  Настраивается пакет pcscd (1.8.14-1ubuntu1.16.04.1) …
  insserv: warning: script 'K10runmbbservice' missing LSB tags and overrides
  insserv: warning: script 'runmbbservice' missing LSB tags and overrides
  insserv: There is a loop between service plymouth and urandom if started
  insserv:  loop involving service urandom at depth 4
  insserv:  loop involving service hwclock at depth 3
  insserv: There is a loop between service runmbbservice and udev if started
  insserv:  loop involving service udev at depth 1
  insserv: Starting runmbbservice depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting runmbbservice depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting runmbbservice depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting runmbbservice depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting runmbbservice depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: Starting runmbbservice depends on plymouth 

[Touch-packages] [Bug 1683378] Re: package libpcsclite1:amd64 1.8.14-1ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

2020-10-07 Thread Joy Latten
Hi, Is this still an issue? Changing the status to incomplete.

** Changed in: pcsc-lite (Ubuntu)
   Status: New => Incomplete

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

Title:
  package libpcsclite1:amd64 1.8.14-1ubuntu1.16.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in pcsc-lite package in Ubuntu:
  Incomplete

Bug description:
  kernel panic

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpcsclite1:amd64 1.8.14-1ubuntu1.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sat Apr 15 16:04:43 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
  DuplicateSignature:
   package:libpcsclite1:amd64:1.8.14-1ubuntu1.16.04.1
   Setting up libc6-dev:amd64 (2.23-0ubuntu7) ...
   dpkg: error processing package libpcsclite1:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-01-06 (101 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: pcsc-lite
  Title: package libpcsclite1:amd64 1.8.14-1ubuntu1.16.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1683378/+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 1690543] Re: package libpcsclite1 1.8.14-1ubuntu1.16.04.1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libpcsclite1/changelog.Debian.gz' partilhado, que é di

2020-10-07 Thread Joy Latten
Hi, Is this still an issue? Changing the status to incomplete.

** Changed in: pcsc-lite (Ubuntu)
   Status: New => Incomplete

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

Title:
  package libpcsclite1 1.8.14-1ubuntu1.16.04.1 failed to
  install/upgrade: a tentar sobreescrever
  '/usr/share/doc/libpcsclite1/changelog.Debian.gz' partilhado, que é
  diferente de outras instâncias do pacote libpcsclite1:amd64

Status in pcsc-lite package in Ubuntu:
  Incomplete

Bug description:
  Isso acontece quando eu ligo a máquina

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpcsclite1 1.8.14-1ubuntu1.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri May 12 20:35:07 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
  DpkgHistoryLog:
   Start-Date: 2017-05-12  20:35:07
   Commandline: apt-get -f install
   Upgrade: libpcsclite1:amd64 (1.8.5-1ubuntu1, 1.8.14-1ubuntu1.16.04.1)
  DpkgTerminalLog:
   A preparar para desempacotar 
.../libpcsclite1_1.8.14-1ubuntu1.16.04.1_amd64.deb ...
   A descompactar libpcsclite1:amd64 (1.8.14-1ubuntu1.16.04.1) sobre 
(1.8.5-1ubuntu1) ...
   dpkg: erro ao processar o arquivo 
/var/cache/apt/archives/libpcsclite1_1.8.14-1ubuntu1.16.04.1_amd64.deb 
(--unpack):
a tentar sobreescrever '/usr/share/doc/libpcsclite1/changelog.Debian.gz' 
partilhado, que é diferente de outras instâncias do pacote libpcsclite1:amd64
  ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libpcsclite1/changelog.Debian.gz' partilhado, que é diferente 
de outras instâncias do pacote libpcsclite1:amd64
  InstallationDate: Installed on 2017-01-13 (120 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: pcsc-lite
  Title: package libpcsclite1 1.8.14-1ubuntu1.16.04.1 failed to 
install/upgrade: a tentar sobreescrever 
'/usr/share/doc/libpcsclite1/changelog.Debian.gz' partilhado, que é diferente 
de outras instâncias do pacote libpcsclite1:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1690543/+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 1570359] Re: pcscd crashed with SIGSEGV in __elf_set___libc_thread_subfreeres_element___rpc_thread_destroy__()

2020-10-07 Thread Joy Latten
Hi, Is this still an issue? Changing the status to incomplete.

** Changed in: pcsc-lite (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  pcscd crashed with SIGSEGV in
  __elf_set___libc_thread_subfreeres_element___rpc_thread_destroy__()

Status in pcsc-lite package in Ubuntu:
  Incomplete

Bug description:
  crashed when login

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pcscd 1.8.14-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Mon Apr  4 17:29:56 2016
  Disassembly: => 0x7f7da881b64c:   Cannot access memory at address 
0x7f7da881b64c
  ExecutablePath: /usr/sbin/pcscd
  InstallationDate: Installed on 2016-03-06 (39 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  ProcCmdline: /usr/sbin/pcscd --foreground --auto-exit
  SegvAnalysis:
   Segfault happened at: 0x7f7da881b64c:Cannot access memory at address 
0x7f7da881b64c
   PC (0x7f7da881b64c) not located in a known VMA region (needed executable 
region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: pcsc-lite
  StacktraceTop:
   ?? ()
   __elf_set___libc_thread_subfreeres_element___rpc_thread_destroy__ () from 
/lib/x86_64-linux-gnu/libc.so.6
   ?? ()
  Title: pcscd crashed with SIGSEGV in 
__elf_set___libc_thread_subfreeres_element___rpc_thread_destroy__()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1570359/+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 1539999] Re: Omnikey Cardreader not working

2020-10-07 Thread Joy Latten
Is this still an issue? Changing to incomplete.

** Changed in: pcsc-lite (Ubuntu)
   Status: New => Incomplete

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

Title:
  Omnikey Cardreader not working

Status in pcsc-lite package in Ubuntu:
  Incomplete

Bug description:
  On my desktop & sony vaio laptop, Alpha 2 Ubuntu-mate does not start my usb 
Omnikey 3121 card reader.
  The 3121 is listed in terminal when I perform 'lsusb'. The reader does work 
under concurrent devuan 1. I have installed pcscd (which drags in libccid 
correctly) & pcsc-tools but this hasn't corrected the problem even with a 
reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/153/+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 1366152] Re: System crash when Vasco-card-reader is plugged in at powerup

2020-10-07 Thread Joy Latten
This bugreport has had no activity and has eol. Closing.

** Changed in: pcsc-lite (Ubuntu)
   Status: New => Won't Fix

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

Title:
  System crash when Vasco-card-reader is plugged in at powerup

Status in pcsc-lite package in Ubuntu:
  Won't Fix

Bug description:
  I'm using VASCO Data Security International Digipass 905 SmartCard Reader 
which is working fine. However if the device is plugged in at power-up, the 
device isn't handled well. Although the device is in the ilisted usb-devices, 
pcsc-scan doesn't find the device at all (Which is normal as the green-led is 
going out after the kernel starts). If one tries to remove the card-reader,
  a system-crash happens. After that the pcscd-service seems to be halted :
  pcsc_scan
  PC/SC device scanner
  V 1.4.22 (c) 2001-2011, Ludovic Rousseau 
  Compiled with PC/SC lite version: 1.8.10
  SCardEstablishContext: Service not available.

  One can recover from this problem by
  1. Unplugging the reader
  2. Manually starting the service again by sudo service pcscd start 
  3. Plugging back the reader in (green led stays on, red led goes on when a 
card is put in)

  The bug is not related to a 64-bit architecture as it happens also
  with 32-bit machines.

  Info about the device
  Bus 001 Device 005: ID 1a44:0001 VASCO Data Security International Digipass 
905 SmartCard Reader
  Couldn't open device, some information will be missing
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   1.10
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize0 8
idVendor   0x1a44 VASCO Data Security International
idProduct  0x0001 Digipass 905 SmartCard Reader
bcdDevice1.02
iManufacturer   1 
iProduct2 
iSerial 0 
bNumConfigurations  1
Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   93
  bNumInterfaces  1
  bConfigurationValue 1
  iConfiguration  0 
  bmAttributes 0x80
(Bus Powered)
  MaxPower   50mA
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting   0
bNumEndpoints   3
bInterfaceClass11 Chip/SmartCard
bInterfaceSubClass  0 
bInterfaceProtocol  0 
iInterface  0 
ChipCard Interface Descriptor:
  bLength54
  bDescriptorType33
  bcdCCID  1.00
  nMaxSlotIndex   0
  bVoltageSupport 3  5.0V 3.0V 
  dwProtocols 3  T=0 T=1
  dwDefaultClock   3700
  dwMaxiumumClock  3700
  bNumClockSupported  1
  dwDataRate   9946 bps
  dwMaxDataRate  318280 bps
  bNumDataRatesSupp. 53
  dwMaxIFSD 254
  dwSyncProtocols  0007  2-wire 3-wire I2C
  dwMechanical  
  dwFeatures   000404BE
Auto configuration based on ATR
Auto activation on insert
Auto voltage selection
Auto clock change
Auto baud rate change
Auto PPS made by CCID
Auto IFSD exchange
Short and extended APDU level exchange
  dwMaxCCIDMsgLen   272
  bClassGetResponseecho
  bClassEnvelope   echo
  wlcdLayout   none
  bPINSupport 0 
  bMaxCCIDBusySlots   1
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes3
Transfer TypeInterrupt
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0004  1x 4 bytes
  bInterval  32
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x02  EP 2 OUT
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0010  1x 16 bytes
  bInterval   0
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x83  EP 3 IN
  bmAttributes2
Transfer TypeBulk

[Touch-packages] [Bug 1700104] Re: package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2020-10-07 Thread Joy Latten
Fixed in subsequent release. Closing.

** Changed in: pcsc-lite (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 pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1700104

Title:
  package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in pcsc-lite package in Ubuntu:
  Won't Fix

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: pcscd 1.8.10-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-81.104~14.04.1-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.24
  AptOrdering:
   pcscd: Install
   pcscd: Configure
  Architecture: amd64
  Date: Fri Jun 23 12:21:31 2017
  DuplicateSignature: package:pcscd:1.8.10-1ubuntu1.1:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-28 (177 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: pcsc-lite
  Title: package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1700104/+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 1868407] Re: PCI/internal sound card not detected

2020-10-07 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1868319 ***
https://bugs.launchpad.net/bugs/1868319

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After the most recent Ubuntu update to kernel 5.3.0-42-generic, built-in 
sound card is no longer detected. I have no sound at all. Booting  Ubuntu with 
the previous kernel 5.3.0-40-generic restores everything to normal (as a 
temporary fix I set GRUB_DEFAULT="1>2").
  Configuration:
  Dell G3 3590 laptop with i7-9750H intel CPU.
  Ubuntu 18.04.
  Realtek built in sound (I'll add details later after I reboot with the older 
kernel).
  Wiht the current (newest kernel) the output of aplay -l is:
  -
  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  -

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2833 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 21 21:28:58 2020
  InstallationDate: Installed on 2019-07-27 (238 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.3
  dmi.board.name: 0NK0C0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.3:bd07/01/2019:svnDellInc.:pnG33590:pvr:rvnDellInc.:rn0NK0C0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G3 3590
  dmi.product.sku: 0949
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868407/+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 1161882] Re: ACR38U Does not work on 12.10

2020-10-07 Thread Joy Latten
This bug was not applicable to pcsc-lite package. Closing since no
activity and eol.

** Changed in: pcsc-lite (Ubuntu)
   Status: New => Invalid

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

Title:
  ACR38U Does not work on 12.10

Status in pcsc-lite package in Ubuntu:
  Invalid

Bug description:
  I have ACR38U CCID reader and it works great under Ubuntu 10.10
  but it doesn't work under 12.10

  
  here's log from Ubuntu 10.10 (it works there)
  -
  0336 ifdhandler.c:1565:init_driver() DriverOptions: 0x
  0013 ifdhandler.c:82:IFDHCreateChannelByName() lun: 0, device: 
usb:072f/90cc:libusb:005:002
  0674 ccid_usb.c:285:OpenUSBByName() Manufacturer: Ludovic Rousseau 
(ludovic.rouss...@free.fr)
  0301 ccid_usb.c:295:OpenUSBByName() ProductString: Generic CCID driver
  0294 ccid_usb.c:301:OpenUSBByName() Copyright: This driver is protected 
by terms of the GNU Lesser General Public License version 2.1, or (at your 
option) any later version.
  00053062 ccid_usb.c:501:OpenUSBByName() Found Vendor/Product: 072F/90CC (ACS 
ACR 38U-CCID)
  0016 ccid_usb.c:503:OpenUSBByName() Using USB bus/device: 005/002
  2747 ccid_usb.c:893:get_data_rates() IFD does not support GET_DATA_RATES 
request: Success
  8994 ifdhandler.c:364:IFDHGetCapabilities() tag: 0xFB0, 
usb:072f/90cc:libusb:005:002 (lun: 0)
  0020 readerfactory.c:249:RFAddReader() Using the pcscd polling thread
  2025 ifdhandler.c:364:IFDHGetCapabilities() tag: 0xFAE, 
usb:072f/90cc:libusb:005:002 (lun: 0)
  0014 ifdhandler.c:418:IFDHGetCapabilities() Reader supports 1 slot(s)
  3935 ifdhandler.c:1043:IFDHPowerICC() action: PowerUp, 
usb:072f/90cc:libusb:005:002 (lun: 0)
  00152050 Card ATR: 3B 6D 00 00 80 31 80 65 B0 87 27 01 BC 83 08 90 00
  --
  but doesn't on Ubuntu 12.10

  5311 ccid_usb.c:649:OpenUSBByName() Found Vendor/Product: 072F/90CC (ACS 
ACR38U-CCID)
  0019 ccid_usb.c:651:OpenUSBByName() Using USB bus/device: 004/007
  2590 ccid_usb.c:1366:get_data_rates() IFD does not support GET_DATA_RATES 
request: Success
  1979 ifdhandler.c:220:IFDHCreateChannelByName() dwFeatures: 0x00010030
  0047 ifdhandler.c:221:IFDHCreateChannelByName() wLcdLayout: 0x
  0034 ifdhandler.c:222:IFDHCreateChannelByName() bPINSupport: 0x00
  0050 ifdhandler.c:223:IFDHCreateChannelByName() dwMaxCCIDMessageLength: 
271
  0045 ifdhandler.c:224:IFDHCreateChannelByName() dwMaxIFSD: 247
  0044 ifdhandler.c:225:IFDHCreateChannelByName() dwDefaultClock: 4000
  0033 ifdhandler.c:226:IFDHCreateChannelByName() dwMaxDataRate: 344100
  0045 ifdhandler.c:227:IFDHCreateChannelByName() bMaxSlotIndex: 0
  0043 ifdhandler.c:228:IFDHCreateChannelByName() bCurrentSlotIndex: 0
  0044 ifdhandler.c:229:IFDHCreateChannelByName() bInterfaceProtocol: 0x00
  0033 ifdhandler.c:230:IFDHCreateChannelByName() bNumEndpoints: 3
  0038 ifdhandler.c:231:IFDHCreateChannelByName() bVoltageSupport: 0x07
  0041 ifdhandler.c:536:IFDHGetCapabilities() tag: 0xFB3, 
usb:072f/90cc:libudev:0:/dev/bus/usb/004/007 (lun: 0)
  0040 readerfactory.c:327:RFAddReader() Using the pcscd polling thread
  1538 ifdhandler.c:536:IFDHGetCapabilities() tag: 0xFAE, 
usb:072f/90cc:libudev:0:/dev/bus/usb/004/007 (lun: 0)
  0028 ifdhandler.c:630:IFDHGetCapabilities() Reader supports 1 slot(s)
  3888 ifdhandler.c:1354:IFDHPowerICC() action: PowerUp, 
usb:072f/90cc:libudev:0:/dev/bus/usb/004/007 (lun: 0)
  00152081 eventhandler.c:256:EHStatusHandlerThread() powerState: 
POWER_STATE_POWERED
  0047 Card ATR: 3B 6D 00 00 80 31 80 65 B0 87 27 01 BC 83 08 90 00 
  00404960 ifdhandler.c:1354:IFDHPowerICC() action: PowerDown, 
usb:072f/90cc:libudev:0:/dev/bus/usb/004/007 (lun: 0)
  00098010 eventhandler.c:446:EHStatusHandlerThread() powerState: 
POWER_STATE_UNPOWERED

  syslog 
  ---
  Mar 29 18:55:07 ubuntu12 kernel: [ 1959.368178] usb 4-1: USB disconnect, 
device number 7
  Mar 29 18:55:11 ubuntu12 kernel: [ 1963.700087] usb 4-1: new full-speed USB 
device number 9 using uhci_hcd
  Mar 29 18:55:11 ubuntu12 kernel: [ 1963.876838] usb 4-1: New USB device 
found, idVendor=072f, idProduct=90cc
  Mar 29 18:55:11 ubuntu12 kernel: [ 1963.876851] usb 4-1: New USB device 
strings: Mfr=1, Product=2, SerialNumber=0
  Mar 29 18:55:11 ubuntu12 kernel: [ 1963.876859] usb 4-1: Product: CCID USB 
Reader
  Mar 29 18:55:11 ubuntu12 kernel: [ 1963.876867] usb 4-1: Manufacturer: ACS
  Mar 29 18:55:11 ubuntu12 mtp-probe: checking bus 4, device 9: 
"/sys/devices/pci:00/:00:1d.0/usb4/4-1"
  Mar 29 18:55:11 ubuntu12 mtp-probe: bus: 4, device: 9 was not an MTP device

  what can be a reason?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1161882/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages

[Touch-packages] [Bug 1090238] Re: pcscd hangs after ejecting Rutoken ECP making some comunication with token

2020-10-07 Thread Joy Latten
This was fixed in subsequent release. Closing.

** Changed in: pcsc-lite (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  pcscd hangs after ejecting Rutoken ECP making some comunication with
  token

Status in pcsc-lite package in Ubuntu:
  Fix Committed

Bug description:
  Im running any example from rutoken sdk after ejecting Rutoken. Pcscd
  got an error and nothing happens him to continue working only daemon
  restart helps. If im not using rutokenecp library all works ok.

  This error is fixed in pcscd 1.8.7 please upgrade
  pcscd,libpcsclite1,ccid pac kages.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: pcscd 1.8.5-1ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Uname: Linux 3.5.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  Date: Fri Dec 14 10:24:57 2012
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-10-11 (63 days ago)
  InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120822.1)
  MarkForUpload: True
  SourcePackage: pcsc-lite
  UpgradeStatus: Upgraded to quantal on 2012-10-29 (45 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1090238/+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 1061947] Re: pcscd (auto)starting and permission troubles

2020-10-07 Thread Joy Latten
This is most likely fixed via pcscd starting from systemd in current
releases. Closing this since it has had no activity and has eol.

** Changed in: pcsc-lite (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  pcscd (auto)starting and permission troubles

Status in pcsc-lite package in Ubuntu:
  Fix Committed

Bug description:
  Kernel: Linux 3.2.0-31-generic-pae (i686)
  Distribution  : Ubuntu 12.04.1 LTS
  Desktop   : XFCE 4
  pcscd : 1.7.4-2ubuntu2

  Information on how to start pcscd the right way is very limited. What
  I found out after digging in for some days ... : --help and man pcscd
  are not really helpful. After installing the packet, pcscd doesn't
  launch itself.

  After a while I found out there is a script /etc/init.d/pcscd (not mentioned 
in man) that is supposed to start the daemon at startup, but it has a line 
'exit 0' in it preventing it from running ..., and a comment that is not very 
helpful for an average Linux user. So I think ok, it doesn't need to run at 
startup. Let me try to start the daemon myself ...
  essAnd then troubles begin. It's easy mess to it up: As I found out (and it 
took me a while, believe me...) running pcscd as simple  user (not as root) 
hangs further well behaviour of the daemon. Only if you use it with the -x 
option, it will kill itself after 60s. Otherwise it just states it is already 
running but can't access a card reader.

  So please, state clearly in man that you have to run pcscd as root to
  start it as a daemon !  Or, alternatively, make the timeout of 60 s
  the default so that you can get out of a blocking situation !

  To check the good working of a card reader, pcsc_scan can be used. But
  also here, if you start it as a regular user and pcscd isn't launched
  yet, it launches the daemon for you, but hey, you are not root, so
  bingo, blocked again. Luckily, it seams to be launched with the -x
  option, so (only) after 60s you can try again, as root this time ...
  To make the whole a little more confusing, once the daemon is running,
  you can launch pcsc_scan as regular user without problem. But that's
  good, I think, after all, since it means (as far as I understand) that
  applications can get to the card reader without any augmented
  permissions.

  So stays the question: how do I start the daemon the right way ?  I haven't 
found out yet ...
  I could use /etc/init.d/pcscd and comment out the 'exit 0'. But I fear the 
daemon will be very diligent to do its work, probing my machine for the heck of 
it (as I noted running sudo pcscd -x -d and watching syslog).

  Ideally, the daemon would be started on startup, with the right
  permissions, but without it probing constantly for some reader. Then
  an application that wants to get access to a reader, could 'tickle'
  the daemon so it starts probing for some time, the application does
  its thing, and the daemon stops probing when not needed anymore.

  If someone knows this is possible, or if there is another preferred scenario, 
I would be glad to hear about it !  Read also that a new version of pcscd will 
use another mean to start automatically, but it's not supported (yet?) on 
Ubuntu ?
  Meanwhile, I hope this info can already help someone taming this one ...

  Bart.

  The technical stuff:

  After boot (daemon not running) executing 'sudo pcsc_scan' -- it's working !
  Information for reader is displayed. Even if after that (within 60s) I just 
run
  'pcsc_scan', the information is displayed again.
  syslog messages (had some logging enabled in my driver):
    Oct  4 16:31:22 BP-LIN pcscd: debuglog.c:269:DebugLogSetLevel() debug 
level=debug
    Oct  4 16:31:22 BP-LIN kernel: [ 3379.177470] OZSCRLX ozscr_open: called
    Oct  4 16:31:22 BP-LIN kernel: [ 3379.177489] OZSCRLX ozscr_ioctl: 
OZSCR_STATUS
    ...
    Oct  4 16:32:28 BP-LIN kernel: [ 3445.597205] OZSCRLX ozscr_ioctl: 
OZSCR_STATUS
    Oct  4 16:32:28 BP-LIN kernel: [ 3445.997318] OZSCRLX ozscr_ioctl: 
OZSCR_STATUS
    Oct  4 16:32:29 BP-LIN kernel: [ 3446.398025] OZSCRLX ozscr_close: called

  Ok, now relaunching 'pcsc_scan' as regular user. The daemon just keeps waiting
  for a reader, no information for the reader displayed.
  syslog states:
    Oct  4 16:34:26 BP-LIN pcscd: dyn_unix.c:81:DYN_GetAddress() 
IFDHCreateChannelByName: /usr/local/o2micro/lib_OZSCR.so: undefined symbol: 
IFDHCreateChannelByName
    Oct  4 16:34:26 BP-LIN pcscd: readerfactory.c:965:RFInitializeReader() Open 
Port 0xF1 Failed (/dev/o2scr0)
    Oct  4 16:34:26 BP-LIN pcscd: readerfactory.c:275:RFAddReader() O2Micro 
SmartCardBus Reader init failed.

  Escaping and trying to run 'pcsc_scan' again. No luck ...
  syslog states:
    Oct  4 16:36:38 BP-LIN pcscd: pcscdaemon.c:342:main() file 

[Touch-packages] [Bug 1860930] Re: [Asus GX531GX] Internal speakers are sometimes noisy - distorted audio

2020-10-07 Thread Adam Niedling
This audio problem seem to be only happening when I reboot from Windows to 
Ubuntu. To fix it I have turn off the computer and turn it on again. Rebooting 
doesn't fix it.
If I turn it off after using Windows and cold start it to boot to Ubuntu there 
is no problem.

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

Title:
  [Asus GX531GX] Internal speakers are sometimes noisy - distorted audio

Status in PulseAudio:
  Unknown
Status in alsa-driver package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have an Asus Zephyrus S GX531GX laptop and a pair of Asus Delta USB
  headphones. When the headphones are plugged in during boot the
  internal speakers won't work. There is only crackling sound coming
  from them. It doesn't help in I unplug the headphones. There is no
  problem if they are not plugged in during boot. I'm using Ubuntu
  19.10.

  Please let me know if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Jan 26 19:26:35 2020
  InstallationDate: Installed on 2019-12-19 (38 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GX531GXR.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GX531GXR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGX531GXR.304:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnZephyrusSGX531GXR_GX531GXR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX531GXR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: Zephyrus S
  dmi.product.name: Zephyrus S GX531GXR_GX531GXR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1860930/+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 796893] Re: Rutoken Magistra init fails in natty

2020-10-07 Thread Joy Latten
This bugreport has had no activity and has eol. Closing.

** Changed in: pcsc-lite (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Rutoken Magistra init fails in natty

Status in pcsc-lite package in Ubuntu:
  Won't Fix

Bug description:
  After upgrade 10.10 -> 11.04 i have permanent problems with rutoken.
  This is syslog after each usert of token to USB:

  
  Jun 13 20:11:56 sportmac pcscd: ccid_usb.c:441:OpenUSBByName() Can't 
libusb_open(2/11): -3
  Jun 13 20:11:56 sportmac pcscd: ifdhandler.c:101:IFDHCreateChannelByName() 
failed
  Jun 13 20:11:56 sportmac pcscd: readerfactory.c:965:RFInitializeReader() Open 
Port 0x20 Failed (usb:0a89/0060:libudev:0:/dev/bus/usb/002/011)
  Jun 13 20:11:56 sportmac pcscd: readerfactory.c:275:RFAddReader() Aktiv 
Rutoken Magistra init failed.
  

  If i stop pcscd service & run it manually in debug mode (pcscd -fd),
  then everything works. Never had such problem in ubuntu 10.10. My
  hardware is mac-mini with nvidea (previous to 'unibody')

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/796893/+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 1004683] Re: pcscd fails to access Reiner SCT CyberJack card reader

2020-10-07 Thread Joy Latten
This bugreport has had no activity and has eol. Closing.

** Changed in: pcsc-lite (Ubuntu)
   Status: New => Invalid

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

Title:
  pcscd fails to access Reiner SCT CyberJack card reader

Status in pcsc-lite package in Ubuntu:
  Invalid

Bug description:
  I tried to access my banking card for the first time since upgrading to 
Precise Pengolin, but the system behaved somewhat strange:
  When i plug the reader into the USB port I usually get a LED flashing a few 
times and some info about the device and its firmware version. I saw this today 
as well, but instead of waiting for actions from the banking software the 
display fell dead again and I couldn't do my banking.
  I investigates a bit and found this in syslog every time I plugged in the 
reader:

  May 25 21:50:00 host kernel: [ 8119.920068] usb 2-2: new full-speed USB 
device number 9 using uhci_hcd
  May 25 21:50:01 host mtp-probe: checking bus 2, device 9: 
"/sys/devices/pci:00/:00:1d.0/usb2/2-2"
  May 25 21:50:01 host mtp-probe: bus: 2, device: 9 was not an MTP device

  Scanning through udev rules I found the device in /lib/udev/rules.d/40
  -libifd-cyberjack6.rules:

  ATTR{idVendor}=="0c4b", ATTR{idProduct}=="0400", MODE="660",
  GROUP="pcscd"

  Looks good to me, so I'm a bit lost for now.
  Maybe this is a udev problem, not pcscd's ?

  
  My setup information:
  Description:Ubuntu 12.04 LTS
  Release:12.04

  pcscd:
Installiert: 1.7.4-2ubuntu2
Kandidat:1.7.4-2ubuntu2
Versionstabelle:
   *** 1.7.4-2ubuntu2 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/universe i386 
Packages
  100 /var/lib/dpkg/status

  
  Please let me know if and how I can be of any help to solve this.

  Thanks for your hard work, I love working with Ubuntu every day, as it
  fits my needs.

  Friedemann

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1004683/+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 776082] Re: pcscd spams syslog whenever mozilla is running and CAC card is not inserted/present

2020-10-07 Thread Joy Latten
This bugreport has had no activity and has eol. Closing.

** Changed in: pcsc-lite (Ubuntu)
   Status: New => Won't Fix

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

Title:
  pcscd spams syslog whenever mozilla is running and CAC card is not
  inserted/present

Status in pcsc-lite package in Ubuntu:
  Won't Fix

Bug description:
  pcscd spams syslog whenever mozilla firefox 4.0.1 is running.  This was not 
present in Ubuntu 10.04 with its version of firefox.  I have a SCR3340 
ExpressCard54 card reader. Following 2 messages are continuously asserted in 
syslog  occur whenever CAC is not present and Firefox is running.  Created a 
13GB syslog overnight!
  May  2 22:12:27 simple-laptop pcscd: winscard.c:290:SCardConnect() Card Not 
Inserted
  May  2 22:12:27 simple-laptop pcscd: winscard_svc.c:447:ContextThread() 
CONNECT rv=0x801C for client 6

  Occurs once whenever CAC (smart card) is removed
  May  2 22:12:19 simple-laptop pcscd: winscard_svc.c:555:ContextThread() 
STATUS rv=0x80100069 for client 6

  Following 2 messages are continuously asserted in syslog when card reader is 
removed from the ExpressCard slot
  May  2 22:31:27 simple-laptop pcscd: winscard_svc.c:447:ContextThread() 
CONNECT rv=0x8019 for client 6
  May  2 22:31:28 simple-laptop pcscd: winscard.c:241:SCardConnect() Reader SCM 
SCR 3340 ExpressCard54 [CCID Interface] (21220827700942) 00 00 Not Found

  I have tried to suppress the messages with DAEMON_ARGS="--critical" in
  the '/etc/default/pcscd' file to no avail.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: pcscd 1.7.0-2ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  Architecture: amd64
  Date: Mon May  2 22:23:10 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pcsc-lite
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/776082/+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 790502] Re: If OS has started the pcscd service won'n start up

2020-10-07 Thread Joy Latten
This bugreport has had no activity and has eol. Closing.

** Changed in: pcsc-lite (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 pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/790502

Title:
  If OS has started the pcscd service won'n start up

Status in pcsc-lite package in Ubuntu:
  Won't Fix

Bug description:
  Kern.log shows lipthread error:
  May 30 13:17:38 mar kernel: [  366.715760] pcscd[2114]: segfault at 10 ip 
7f8e25f74394 sp 7f8e2478cb00 error 4 in 
libpthread-2.13.so[7f8e25f6b000+18000]

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: pcscd 1.7.0-2ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  Architecture: amd64
  Date: Tue May 31 09:38:47 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pcsc-lite
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/790502/+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 795540] Re: package pcscd 1.7.0-2ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

2020-10-07 Thread Joy Latten
This bugreport has had no activity and has eol. Closing.


** Changed in: pcsc-lite (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 pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/795540

Title:
  package pcscd 1.7.0-2ubuntu2 failed to install/upgrade: ErrorMessage:
  subprocess installed post-installation script returned error exit
  status 1

Status in pcsc-lite package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: pcscd

  jadler@server:~$ lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04
  jadler@server:~$ apt-cache policy pcsc
  pcscada-dbg   pcscd pcsc-omnikey  pcsc-tools
  jadler@server:~$ apt-cache policy pcsc-lite
  N: Unable to locate package pcsc-lite
  jadler@server:~$ apt-cache policy pcscd 
  pcscd:
Installed: 1.7.0-2ubuntu2
Candidate: 1.7.0-2ubuntu2
Version table:
   *** 1.7.0-2ubuntu2 0
  500 http://se.archive.ubuntu.com/ubuntu/ natty/universe amd64 Packages
  100 /var/lib/dpkg/status

  Upgrading 10.10 to 11.04

  ProblemType: Package
  DistroRelease: Ubuntu 11.04
  Package: pcscd 1.7.0-2ubuntu2
  ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11
  Uname: Linux 2.6.35-28-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Fri Jun 10 08:17:33 2011
  ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 1
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: pcsc-lite
  Title: package pcscd 1.7.0-2ubuntu2 failed to install/upgrade: ErrorMessage: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to natty on 2011-06-09 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/795540/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

2020-10-07 Thread Steve Langasek
** Changed in: debconf (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: aptdaemon (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Fix Released
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Invalid
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptdaemon/+bug/349469/+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 336815] Re: Aladdin etoken pro not supported anymore with pcscd

2020-10-07 Thread Joy Latten
This bug appears to have been fixed in an update. Closing.

** Changed in: pcsc-lite (Ubuntu)
   Status: New => Fix Released

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

Title:
  Aladdin etoken pro not supported anymore with pcscd

Status in pcsc-lite package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: pcscd

  Aladdin etoken pro usb (ID 0529:0620 Aladdin Knowledge Systems ) used
  to work with the pcscd version in hardy, but does not works anymore
  with pcscd 1.4.102-1ubuntu1

  The token is not anymore visible in Aladdin's middleware, while i can
  still read an eToken smarcard in another smart card reader.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/336815/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

2020-10-07 Thread Rayden Joshua Britto
ibpam0g

** Changed in: debconf (Ubuntu)
   Status: Triaged => Confirmed

** Changed in: aptdaemon (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Fix Released
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Confirmed
Status in debconf package in Ubuntu:
  Confirmed

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptdaemon/+bug/349469/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

2020-10-07 Thread Rayden Joshua Britto
ibpam0g

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Fix Released
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Confirmed
Status in debconf package in Ubuntu:
  Confirmed

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptdaemon/+bug/349469/+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 1895865] Re: /usr/share/apport/dump_acpi_tables.py:PermissionError:/usr/share/apport/dump_acpi_tables.py@59:dump_acpi_tables:dump_acpi_table

2020-10-07 Thread Robie Basak
Hello errors.ubuntu.com, or anyone else affected,

Accepted apport into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu27.10 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: apport (Ubuntu Focal)
   Status: Incomplete => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  
/usr/share/apport/dump_acpi_tables.py:PermissionError:/usr/share/apport/dump_acpi_tables.py@59:dump_acpi_tables:dump_acpi_table

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Released

Bug description:
  Impact
  --
  Users running /usr/share/apport/dump_acpi_tables.py will receive a Traceback 
unless it is called by root.

  Test Case
  -
  1) Run /usr/share/apport/dump_acpi_tables.py
  2) Observe the Traceback in comment #1

  Additionally, running 'ubuntu-bug' about a package which calls
  attach_hardware (which then calls dump_acpi_tables.py) will have a
  Traceback in acpidump.

  1) Run 'ubuntu-bug udev'
  2) Save the report
  3) View the report and see the Traceback from comment #1 in it

  With the version of the package from -proposed you will not receive a
  Traceback in either situation.

  Regression Potential
  
  If the python is bad we could have a different crash.

  Original Description
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu45, the problem page at 
https://errors.ubuntu.com/problem/ad705c1a5e4068bcae9d4261519bac8fac5cb57f 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1895865/+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 1898023] Re: [ThinkPad Helix 2nd] No more sound after upgrade 18.04->20.04

2020-10-07 Thread udippel
I would put this on hold until further notice. Probably me not
understanding pulse-audio settings correctly. After a lot of fiddling
and wild guess it would work, stop with some other settings, and stop,
when removing the tablet part off the convertible.

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

Title:
  [ThinkPad Helix 2nd] No more sound after upgrade 18.04->20.04

Status in alsa-driver package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  (title says it in principle:)

  Upgraded from 18.04 to 20.04 yesterday. Now my sound is mum. It is
  kind of visible, but not as speakers in the tablet part of my
  convertible. So when removing the tablet from the dock, there is no
  sound. Shouldn't be a hardware problem, since W10 (dual-boot) plays
  musics.

  (The files are with dock attached, since the tablet on its own has -
  and that's a bug of *buntu - no right click. So the 'USB ' shown
  as audio device is the device in the keyboard dock.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1580 F pulseaudio
   /dev/snd/controlC0:  udippel1580 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Oct  1 11:40:36 2020
  InstallationDate: Installed on 2019-03-14 (566 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898023/+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 1888575] Re: Split motd-news config into a new package

2020-10-07 Thread Steve Langasek
** Changed in: livecd-rootfs (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  Invalid
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in livecd-rootfs source package in Focal:
  Invalid
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
Status in livecd-rootfs source package in Groovy:
  Invalid
Status in ubuntu-meta source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.

  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config

  Care must be taken to preserve a changed /etc/default/motd-news when
  the upgrade installs the new motd-news-config package. For example, on
  a server that has set ENABLED=0 in /etc/default/motd-news and upgrades
  to the new base-files and ubuntu-server, and gets the new motd-config-
  news package, ENABLED=0 must remain set.

  [Test Case]
  a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains, motd-news remains enabled

  b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains with the original modification

  c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
  apt install base-files
  - upgrades base-files
  - removes /e/d/motd-news
  - motd-news is disabled

  d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
  apt install base-files
  - upgrades base-files
  - /e/d/motd-news gets renamed to backup
  - motd-news is disabled

  e) removing motd-news-config will also remove ubuntu-server (since
  it's a depends, and not a recommends)

  f) upgrading just ubuntu-server should pull motd-news-config in, and
  force-upgrade base-files

  g) Removing motd-news-server leaves /e/d/motd-news around; purging
  motd-news-server removes the /e/d/motd-news config file

  h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
  - apt install base-files
  - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
  - /e/d/motd-news is installed with ENABLED=0

  i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news
  - apt install base-files
  - base-files is upgraded
  - no /e/d/motd-news is installed, motd-news remains disabled

  j) Perform a release upgrade from the previous ubuntu release to the
  one being tested while having ubuntu-server NOT installed (or use a
  desktop install). At the end, motd-news should be disabled. Verify
  with:

  $ sudo /etc/update-motd.d/50-motd-news --force
  $ (no output)

  k) Test that supporting changes for xenial are in place:

    i) verify grub-legacy-ec2 is not in the xenial server seed
    ii) verify that the rootfs manifest built from the ubuntu-cpc project 
contains the ubuntu-server package
    iii) verify that images built from the ubuntu-cpc project which purge 
grub-legacy-ec2 have retained ubuntu-server
iv) verify that the base ubuntu-cpc image continues to have grub-legacy-ec2 
installed.

  [Regression Potential]
  This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
  a) /e/d/motd-news config was changed while it belonged to base-files. For 
example, an user could have set ENABLED=0. We need to transfer that change to 
the motd-news-config package when it is 

[Touch-packages] [Bug 1888575] Re: Split motd-news config into a new package

2020-10-07 Thread Steve Langasek
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  Invalid
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in livecd-rootfs source package in Focal:
  Invalid
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
Status in livecd-rootfs source package in Groovy:
  Invalid
Status in ubuntu-meta source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.

  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config

  Care must be taken to preserve a changed /etc/default/motd-news when
  the upgrade installs the new motd-news-config package. For example, on
  a server that has set ENABLED=0 in /etc/default/motd-news and upgrades
  to the new base-files and ubuntu-server, and gets the new motd-config-
  news package, ENABLED=0 must remain set.

  [Test Case]
  a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains, motd-news remains enabled

  b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains with the original modification

  c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
  apt install base-files
  - upgrades base-files
  - removes /e/d/motd-news
  - motd-news is disabled

  d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
  apt install base-files
  - upgrades base-files
  - /e/d/motd-news gets renamed to backup
  - motd-news is disabled

  e) removing motd-news-config will also remove ubuntu-server (since
  it's a depends, and not a recommends)

  f) upgrading just ubuntu-server should pull motd-news-config in, and
  force-upgrade base-files

  g) Removing motd-news-server leaves /e/d/motd-news around; purging
  motd-news-server removes the /e/d/motd-news config file

  h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
  - apt install base-files
  - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
  - /e/d/motd-news is installed with ENABLED=0

  i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news
  - apt install base-files
  - base-files is upgraded
  - no /e/d/motd-news is installed, motd-news remains disabled

  j) Perform a release upgrade from the previous ubuntu release to the
  one being tested while having ubuntu-server NOT installed (or use a
  desktop install). At the end, motd-news should be disabled. Verify
  with:

  $ sudo /etc/update-motd.d/50-motd-news --force
  $ (no output)

  k) Test that supporting changes for xenial are in place:

    i) verify grub-legacy-ec2 is not in the xenial server seed
    ii) verify that the rootfs manifest built from the ubuntu-cpc project 
contains the ubuntu-server package
    iii) verify that images built from the ubuntu-cpc project which purge 
grub-legacy-ec2 have retained ubuntu-server
iv) verify that the base ubuntu-cpc image continues to have grub-legacy-ec2 
installed.

  [Regression Potential]
  This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
  a) /e/d/motd-news config was changed while it belonged to base-files. For 
example, an user could have set ENABLED=0. We need to transfer that change to 
the motd-news-config package 

[Touch-packages] [Bug 1888575] Re: Split motd-news config into a new package

2020-10-07 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-meta - 1.361.6

---
ubuntu-meta (1.361.6) xenial; urgency=medium

  * Refreshed dependencies; LP: #1888575.
  * Added motd-news-config to server (via germinate now rather than
hard-coding, since germinate has managed to pick it up)
  * Removed grub-legacy-ec2 from server [amd64 arm64 armhf i386 powerpc
ppc64el]

 -- Steve Langasek   Wed, 16 Sep 2020
22:00:18 +

** Changed in: ubuntu-meta (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  Invalid
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in livecd-rootfs source package in Focal:
  Invalid
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
Status in livecd-rootfs source package in Groovy:
  Invalid
Status in ubuntu-meta source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.

  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config

  Care must be taken to preserve a changed /etc/default/motd-news when
  the upgrade installs the new motd-news-config package. For example, on
  a server that has set ENABLED=0 in /etc/default/motd-news and upgrades
  to the new base-files and ubuntu-server, and gets the new motd-config-
  news package, ENABLED=0 must remain set.

  [Test Case]
  a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains, motd-news remains enabled

  b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains with the original modification

  c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
  apt install base-files
  - upgrades base-files
  - removes /e/d/motd-news
  - motd-news is disabled

  d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
  apt install base-files
  - upgrades base-files
  - /e/d/motd-news gets renamed to backup
  - motd-news is disabled

  e) removing motd-news-config will also remove ubuntu-server (since
  it's a depends, and not a recommends)

  f) upgrading just ubuntu-server should pull motd-news-config in, and
  force-upgrade base-files

  g) Removing motd-news-server leaves /e/d/motd-news around; purging
  motd-news-server removes the /e/d/motd-news config file

  h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
  - apt install base-files
  - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
  - /e/d/motd-news is installed with ENABLED=0

  i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news
  - apt install base-files
  - base-files is upgraded
  - no /e/d/motd-news is installed, motd-news remains disabled

  j) Perform a release upgrade from the previous ubuntu release to the
  one being tested while having ubuntu-server NOT installed (or use a
  desktop install). At the end, motd-news should be disabled. Verify
  with:

  $ sudo /etc/update-motd.d/50-motd-news --force
  $ (no output)

  k) Test that supporting changes for xenial are in place:

    i) verify grub-legacy-ec2 is not in the xenial server seed
    ii) verify that the rootfs manifest built from the ubuntu-cpc project 
contains the ubuntu-server package
    iii) verify that images built from the ubuntu-cpc project which purge 
grub-legacy-ec2 have retained ubuntu-server
iv) verify that the base ubuntu-cpc image continues to have 

[Touch-packages] [Bug 1888575] Re: Split motd-news config into a new package

2020-10-07 Thread Cody Shepherd
All parts of case k) verified by repeating the steps described above
against -proposed.

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  Invalid
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in livecd-rootfs source package in Focal:
  Invalid
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
Status in livecd-rootfs source package in Groovy:
  Invalid
Status in ubuntu-meta source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.

  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config

  Care must be taken to preserve a changed /etc/default/motd-news when
  the upgrade installs the new motd-news-config package. For example, on
  a server that has set ENABLED=0 in /etc/default/motd-news and upgrades
  to the new base-files and ubuntu-server, and gets the new motd-config-
  news package, ENABLED=0 must remain set.

  [Test Case]
  a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains, motd-news remains enabled

  b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains with the original modification

  c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
  apt install base-files
  - upgrades base-files
  - removes /e/d/motd-news
  - motd-news is disabled

  d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
  apt install base-files
  - upgrades base-files
  - /e/d/motd-news gets renamed to backup
  - motd-news is disabled

  e) removing motd-news-config will also remove ubuntu-server (since
  it's a depends, and not a recommends)

  f) upgrading just ubuntu-server should pull motd-news-config in, and
  force-upgrade base-files

  g) Removing motd-news-server leaves /e/d/motd-news around; purging
  motd-news-server removes the /e/d/motd-news config file

  h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
  - apt install base-files
  - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
  - /e/d/motd-news is installed with ENABLED=0

  i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news
  - apt install base-files
  - base-files is upgraded
  - no /e/d/motd-news is installed, motd-news remains disabled

  j) Perform a release upgrade from the previous ubuntu release to the
  one being tested while having ubuntu-server NOT installed (or use a
  desktop install). At the end, motd-news should be disabled. Verify
  with:

  $ sudo /etc/update-motd.d/50-motd-news --force
  $ (no output)

  k) Test that supporting changes for xenial are in place:

    i) verify grub-legacy-ec2 is not in the xenial server seed
    ii) verify that the rootfs manifest built from the ubuntu-cpc project 
contains the ubuntu-server package
    iii) verify that images built from the ubuntu-cpc project which purge 
grub-legacy-ec2 have retained ubuntu-server
iv) verify that the base ubuntu-cpc image continues to have grub-legacy-ec2 
installed.

  [Regression Potential]
  This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
  a) /e/d/motd-news config was changed while it belonged to base-files. For 
example, an user could have set ENABLED=0. We need to transfer that change to 
the motd-news-config package when it is 

[Touch-packages] [Bug 1895865] Re: /usr/share/apport/dump_acpi_tables.py:PermissionError:/usr/share/apport/dump_acpi_tables.py@59:dump_acpi_tables:dump_acpi_table

2020-10-07 Thread Brian Murray
** Description changed:

+ Impact
+ --
+ Users running /usr/share/apport/dump_acpi_tables.py will receive a Traceback 
unless it is called by root.
+ 
+ Test Case
+ -
+ 1) Run /usr/share/apport/dump_acpi_tables.py
+ 2) Observe the Traceback in comment #1
+ 
+ Additionally, running 'ubuntu-bug' about a package which calls
+ attach_hardware (which then calls dump_acpi_tables.py) will have a
+ Traceback in acpidump.
+ 
+ 1) Run 'ubuntu-bug udev'
+ 2) Save the report
+ 3) View the report and see the Traceback from comment #1 in it
+ 
+ With the version of the package from -proposed you will not receive a
+ Traceback in either situation.
+ 
+ Regression Potential
+ 
+ If the python is bad we could have a different crash.
+ 
+ Original Description
+ 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu45, the problem page at 
https://errors.ubuntu.com/problem/ad705c1a5e4068bcae9d4261519bac8fac5cb57f 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

Title:
  
/usr/share/apport/dump_acpi_tables.py:PermissionError:/usr/share/apport/dump_acpi_tables.py@59:dump_acpi_tables:dump_acpi_table

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Incomplete
Status in apport source package in Groovy:
  Fix Released

Bug description:
  Impact
  --
  Users running /usr/share/apport/dump_acpi_tables.py will receive a Traceback 
unless it is called by root.

  Test Case
  -
  1) Run /usr/share/apport/dump_acpi_tables.py
  2) Observe the Traceback in comment #1

  Additionally, running 'ubuntu-bug' about a package which calls
  attach_hardware (which then calls dump_acpi_tables.py) will have a
  Traceback in acpidump.

  1) Run 'ubuntu-bug udev'
  2) Save the report
  3) View the report and see the Traceback from comment #1 in it

  With the version of the package from -proposed you will not receive a
  Traceback in either situation.

  Regression Potential
  
  If the python is bad we could have a different crash.

  Original Description
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu45, the problem page at 
https://errors.ubuntu.com/problem/ad705c1a5e4068bcae9d4261519bac8fac5cb57f 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1895865/+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 1895865] Re: /usr/share/apport/dump_acpi_tables.py:PermissionError:/usr/share/apport/dump_acpi_tables.py@59:dump_acpi_tables:dump_acpi_table

2020-10-07 Thread Brian Murray
Regarding comment #2 this was fixed in apport version 2.20.11-0ubuntu46
but that was likely stuck in -proposed for some reason and didn't
migrate. Then ubuntu47 did migrate and this got closed but the janitor
only comments with the most recent changelog entry.

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

Title:
  
/usr/share/apport/dump_acpi_tables.py:PermissionError:/usr/share/apport/dump_acpi_tables.py@59:dump_acpi_tables:dump_acpi_table

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Incomplete
Status in apport source package in Groovy:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu45, the problem page at 
https://errors.ubuntu.com/problem/ad705c1a5e4068bcae9d4261519bac8fac5cb57f 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1895865/+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 1898869] Re: System slow on booting

2020-10-07 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (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/1898869

Title:
  System slow on booting

Status in xorg package in Ubuntu:
  New

Bug description:
  I have installed a Kubuntu 20.04.1 for my grandma, the system is slow
  to boot, takes between a minute 30 seconds to two minutes to display
  the Plasma Desktop. I am attaching a journalctl log and a systemd-
  bootchart img.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Wed Oct  7 15:26:27 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-48-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1043:14dd]
  InstallationDate: Installed on 2020-09-22 (14 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b404 Chicony Electronics Co., Ltd USB2.0 HD UVC 
WebCam
   Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. Broadcom 
BCM43142A0 Bluetooth Device
   Bus 001 Device 002: ID 1c4f:0034 SiGma Micro Usb Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X551MA
  ProcEnviron:
   LANGUAGE=ru:en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=bg_BG.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash 
init=/lib/systemd/systemd-bootchart vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X551MA.515
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X551MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX551MA.515:bd04/15/2015:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X551MA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1898869/+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 1898869] [NEW] System slow on booting

2020-10-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have installed a Kubuntu 20.04.1 for my grandma, the system is slow to
boot, takes between a minute 30 seconds to two minutes to display the
Plasma Desktop. I am attaching a journalctl log and a systemd-bootchart
img.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Wed Oct  7 15:26:27 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 5.4.0-48-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1043:14dd]
InstallationDate: Installed on 2020-09-22 (14 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04f2:b404 Chicony Electronics Co., Ltd USB2.0 HD UVC 
WebCam
 Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. Broadcom BCM43142A0 
Bluetooth Device
 Bus 001 Device 002: ID 1c4f:0034 SiGma Micro Usb Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X551MA
ProcEnviron:
 LANGUAGE=ru:en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=bg_BG.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash 
init=/lib/systemd/systemd-bootchart vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X551MA.515
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X551MA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX551MA.515:bd04/15/2015:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X551MA
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu
-- 
System slow on booting
https://bugs.launchpad.net/bugs/1898869
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 1895850] Re: UI is not very helpful, let's talk about improvements?

2020-10-07 Thread Thomas Ward
Marking as Opinion/Wishlist because this isn't really a bug.

** Changed in: apport (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: apport (Ubuntu)
   Status: New => Opinion

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

Title:
  UI is not very helpful, let's talk about improvements?

Status in apport package in Ubuntu:
  Opinion

Bug description:
  Hello,

  I already asked a question here

  https://answers.launchpad.net/apport/+question/692912

  Someone on IRC suggested I file a bug report too/instead.

  Thanks for reading.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.8
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed Sep 16 15:42:24 2020
  InstallationDate: Installed on 2019-07-24 (419 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to focal on 2020-09-15 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1895850/+subscriptions

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


[Touch-packages] [Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected

2020-10-07 Thread Tim Wetzel
I already used the daily image; and yes I got the (re)installation to
complete without crashing. BUT the freshly (re)installed Ubuntu system
remained unstable and therefore unusable due to other bugs that were
introduced or re-introduced by the two Ubuntu Updater packages pushed
out since mid-September. Even with the fresh re-installation from the
daily image, I still have:

-there are problems with the new compression algorithm for initramfs
-there are issues with startup hanging with a spinning Ubuntu logo, forcing 
hard power down
-there are issues with startup going into suspend as soon as the login password 
is entered

These were why I did a full erase and re-install of Ubuntu to start
with: these bugs had, in the week or two prior, made Ubuntu
frighteningly unstable. I too hope that this all gets solved soon.

There are bug reports on all of these: see bugs #1872159, 1835660,
1897185. There are related and/or duplicates of some of these also.

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

Title:
  Installation fails when  "Install Third-Party Drivers" is selected

Status in GLibC:
  New
Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  Invalid

Bug description:
  Please use the latest daily installer images if you would like to enable 
third-party drivers during installation:
  http://www.cdimage.ubuntu.com/focal/daily-live/current/

  [Original Bug Text]

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

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  

[Touch-packages] [Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected

2020-10-07 Thread Tim Wetzel
I should add that, in researching old posts on these issues, I gather
that nVidia driver(s) have been a factor; so note that the last Ubuntu
Updater package prior to all this did also include an update to the
nVidia driver package.

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

Title:
  Installation fails when  "Install Third-Party Drivers" is selected

Status in GLibC:
  New
Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  Invalid

Bug description:
  Please use the latest daily installer images if you would like to enable 
third-party drivers during installation:
  http://www.cdimage.ubuntu.com/focal/daily-live/current/

  [Original Bug Text]

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

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1871268/+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 1888575] Re: Split motd-news config into a new package

2020-10-07 Thread Cody Shepherd
Ok, I wasn't building from -proposed, I'll try again.

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  Invalid
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in livecd-rootfs source package in Focal:
  Invalid
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
Status in livecd-rootfs source package in Groovy:
  Invalid
Status in ubuntu-meta source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.

  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config

  Care must be taken to preserve a changed /etc/default/motd-news when
  the upgrade installs the new motd-news-config package. For example, on
  a server that has set ENABLED=0 in /etc/default/motd-news and upgrades
  to the new base-files and ubuntu-server, and gets the new motd-config-
  news package, ENABLED=0 must remain set.

  [Test Case]
  a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains, motd-news remains enabled

  b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains with the original modification

  c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
  apt install base-files
  - upgrades base-files
  - removes /e/d/motd-news
  - motd-news is disabled

  d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
  apt install base-files
  - upgrades base-files
  - /e/d/motd-news gets renamed to backup
  - motd-news is disabled

  e) removing motd-news-config will also remove ubuntu-server (since
  it's a depends, and not a recommends)

  f) upgrading just ubuntu-server should pull motd-news-config in, and
  force-upgrade base-files

  g) Removing motd-news-server leaves /e/d/motd-news around; purging
  motd-news-server removes the /e/d/motd-news config file

  h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
  - apt install base-files
  - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
  - /e/d/motd-news is installed with ENABLED=0

  i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news
  - apt install base-files
  - base-files is upgraded
  - no /e/d/motd-news is installed, motd-news remains disabled

  j) Perform a release upgrade from the previous ubuntu release to the
  one being tested while having ubuntu-server NOT installed (or use a
  desktop install). At the end, motd-news should be disabled. Verify
  with:

  $ sudo /etc/update-motd.d/50-motd-news --force
  $ (no output)

  k) Test that supporting changes for xenial are in place:

    i) verify grub-legacy-ec2 is not in the xenial server seed
    ii) verify that the rootfs manifest built from the ubuntu-cpc project 
contains the ubuntu-server package
    iii) verify that images built from the ubuntu-cpc project which purge 
grub-legacy-ec2 have retained ubuntu-server
iv) verify that the base ubuntu-cpc image continues to have grub-legacy-ec2 
installed.

  [Regression Potential]
  This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
  a) /e/d/motd-news config was changed while it belonged to base-files. For 
example, an user could have set ENABLED=0. We need to transfer that change to 
the motd-news-config package when it is installed, otherwise this SRU would 

[Touch-packages] [Bug 1888575] Re: Split motd-news config into a new package

2020-10-07 Thread Cody Shepherd
My initial guess at why this has failed is that the ubuntu-server
package appears to still depend on grub-legacy-ec2 [1].

[1] https://packages.ubuntu.com/xenial/ubuntu-server

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  Invalid
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in livecd-rootfs source package in Focal:
  Invalid
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
Status in livecd-rootfs source package in Groovy:
  Invalid
Status in ubuntu-meta source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.

  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config

  Care must be taken to preserve a changed /etc/default/motd-news when
  the upgrade installs the new motd-news-config package. For example, on
  a server that has set ENABLED=0 in /etc/default/motd-news and upgrades
  to the new base-files and ubuntu-server, and gets the new motd-config-
  news package, ENABLED=0 must remain set.

  [Test Case]
  a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains, motd-news remains enabled

  b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains with the original modification

  c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
  apt install base-files
  - upgrades base-files
  - removes /e/d/motd-news
  - motd-news is disabled

  d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
  apt install base-files
  - upgrades base-files
  - /e/d/motd-news gets renamed to backup
  - motd-news is disabled

  e) removing motd-news-config will also remove ubuntu-server (since
  it's a depends, and not a recommends)

  f) upgrading just ubuntu-server should pull motd-news-config in, and
  force-upgrade base-files

  g) Removing motd-news-server leaves /e/d/motd-news around; purging
  motd-news-server removes the /e/d/motd-news config file

  h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
  - apt install base-files
  - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
  - /e/d/motd-news is installed with ENABLED=0

  i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news
  - apt install base-files
  - base-files is upgraded
  - no /e/d/motd-news is installed, motd-news remains disabled

  j) Perform a release upgrade from the previous ubuntu release to the
  one being tested while having ubuntu-server NOT installed (or use a
  desktop install). At the end, motd-news should be disabled. Verify
  with:

  $ sudo /etc/update-motd.d/50-motd-news --force
  $ (no output)

  k) Test that supporting changes for xenial are in place:

    i) verify grub-legacy-ec2 is not in the xenial server seed
    ii) verify that the rootfs manifest built from the ubuntu-cpc project 
contains the ubuntu-server package
    iii) verify that images built from the ubuntu-cpc project which purge 
grub-legacy-ec2 have retained ubuntu-server
iv) verify that the base ubuntu-cpc image continues to have grub-legacy-ec2 
installed.

  [Regression Potential]
  This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
  a) /e/d/motd-news config was changed while it belonged to base-files. For 
example, an user could have set 

[Touch-packages] [Bug 1888575] Re: Split motd-news config into a new package

2020-10-07 Thread Cody Shepherd
Also as to verification of k.i), I've verified that the "deployed"
server seed [1] matches the seed configuration in VCS linked in the last
comment.

[1] https://people.canonical.com/~ubuntu-
archive/seeds/ubuntu.xenial/server

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  Invalid
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in livecd-rootfs source package in Focal:
  Invalid
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
Status in livecd-rootfs source package in Groovy:
  Invalid
Status in ubuntu-meta source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.

  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config

  Care must be taken to preserve a changed /etc/default/motd-news when
  the upgrade installs the new motd-news-config package. For example, on
  a server that has set ENABLED=0 in /etc/default/motd-news and upgrades
  to the new base-files and ubuntu-server, and gets the new motd-config-
  news package, ENABLED=0 must remain set.

  [Test Case]
  a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains, motd-news remains enabled

  b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains with the original modification

  c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
  apt install base-files
  - upgrades base-files
  - removes /e/d/motd-news
  - motd-news is disabled

  d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
  apt install base-files
  - upgrades base-files
  - /e/d/motd-news gets renamed to backup
  - motd-news is disabled

  e) removing motd-news-config will also remove ubuntu-server (since
  it's a depends, and not a recommends)

  f) upgrading just ubuntu-server should pull motd-news-config in, and
  force-upgrade base-files

  g) Removing motd-news-server leaves /e/d/motd-news around; purging
  motd-news-server removes the /e/d/motd-news config file

  h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
  - apt install base-files
  - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
  - /e/d/motd-news is installed with ENABLED=0

  i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news
  - apt install base-files
  - base-files is upgraded
  - no /e/d/motd-news is installed, motd-news remains disabled

  j) Perform a release upgrade from the previous ubuntu release to the
  one being tested while having ubuntu-server NOT installed (or use a
  desktop install). At the end, motd-news should be disabled. Verify
  with:

  $ sudo /etc/update-motd.d/50-motd-news --force
  $ (no output)

  k) Test that supporting changes for xenial are in place:

    i) verify grub-legacy-ec2 is not in the xenial server seed
    ii) verify that the rootfs manifest built from the ubuntu-cpc project 
contains the ubuntu-server package
    iii) verify that images built from the ubuntu-cpc project which purge 
grub-legacy-ec2 have retained ubuntu-server
iv) verify that the base ubuntu-cpc image continues to have grub-legacy-ec2 
installed.

  [Regression Potential]
  This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
  a) /e/d/motd-news config was changed while it belonged to 

[Touch-packages] [Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected

2020-10-07 Thread Balint Reczey
@mahdish The daily image as recommended at the first line of the bug
description?

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

Title:
  Installation fails when  "Install Third-Party Drivers" is selected

Status in GLibC:
  New
Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  Invalid

Bug description:
  Please use the latest daily installer images if you would like to enable 
third-party drivers during installation:
  http://www.cdimage.ubuntu.com/focal/daily-live/current/

  [Original Bug Text]

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

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1871268/+subscriptions

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


[Touch-packages] [Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected

2020-10-07 Thread Balint Reczey
@errantscientist Please read the first line of the bug description...

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

Title:
  Installation fails when  "Install Third-Party Drivers" is selected

Status in GLibC:
  New
Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  Invalid

Bug description:
  Please use the latest daily installer images if you would like to enable 
third-party drivers during installation:
  http://www.cdimage.ubuntu.com/focal/daily-live/current/

  [Original Bug Text]

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

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1871268/+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 1898879] [NEW] /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@442:parse_arguments:print_usage:_print_message

2020-10-07 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.1-0ubuntu2.25, the problem page at 
https://errors.ubuntu.com/problem/2b6a1637e787b93e9c46b3b2e981d83c6b571e06 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: xenial

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@442:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.1-0ubuntu2.25, the problem page at 
https://errors.ubuntu.com/problem/2b6a1637e787b93e9c46b3b2e981d83c6b571e06 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1898879/+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 1896224] Re: [UX550VD, Realtek ALC295, Black Headphone Out, Front] No sound at all

2020-10-07 Thread Mohammadreza Saed
Got it working by disabling Windows 10 fast startup.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Fix Committed

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

Title:
  [UX550VD, Realtek ALC295, Black Headphone Out, Front] No sound at all

Status in alsa-driver package in Ubuntu:
  Fix Committed

Bug description:
  I just installed Ubuntu 18.04.5 LTS on Asus Zenbook UX550VD laptop. Speakers 
work fine, but I have no sound when I plug in headphones to the audio jack.
  Ubuntu recognizes headphones as I can seen it in settings. Tried alsamixer 
and Unmuted everything, still no sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset wl nvidia
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mrs1540 F pulseaudio
   /dev/snd/pcmC0D0p:   mrs1540 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 18 16:19:16 2020
  InstallationDate: Installed on 2020-09-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1071 F pulseaudio
mrs1540 F pulseaudio
   /dev/snd/pcmC0D0c:   mrs1540 F...m pulseaudio
   /dev/snd/pcmC0D0p:   mrs1540 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [UX550VD, Realtek ALC295, Black Headphone Out, Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550VD.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX550VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1896224/+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


Re: [Touch-packages] [Bug 1898729] Re: shim can end up being removed

2020-10-07 Thread Steve Langasek
On Wed, Oct 07, 2020 at 10:10:57AM -, Julian Andres Klode wrote:
> We could mark bootloader packages as Protected: yes (Important: yes
> before groovy). That would not only prevent autoremoval, it would also
> add another step to manual removal as it triggers the same removal
> prompts as essential packages.

> Arguably top-level kernel packages, oem metapackages should have those
> set too.

I'm not sure it's a good idea to use this for kernel packages since it makes
it more difficult to change kernel flavors.  It would definitely have
knock-on effects on various image build infrastructure.

But setting this for shim-signed and grub-pc sounds like a good idea to
me.

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

Title:
  shim can end up being removed

Status in apt package in Ubuntu:
  New
Status in shim package in Ubuntu:
  New

Bug description:
  I just did a set of package updates in focal that ended up with shim
  shim-signed mokutil being autoremoved.

  I rebooted without noticing, and had to manually recover the system
  thereafter. :(

  Julian says there was a period of time where these were marked auto. I
  suppose that I installed during this window, and now some dependency
  change meant that as far as apt was concerned they weren't required
  any more.

  Can we please consider never proposing these packages for autoremoval?
  apt has NeverAutoRemove for this which could be used, or some other
  appropriate method.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898729/+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 981461] Re: Network interfaces are not correctly brought down on halt, disrupting Wake-on-LAN

2020-10-07 Thread no!chance
no wake-on-lan with Ubuntu 20., too!

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

Title:
  Network interfaces are not correctly brought down on halt, disrupting
  Wake-on-LAN

Status in ifupdown package in Ubuntu:
  Triaged
Status in upstart package in Ubuntu:
  Confirmed
Status in ifupdown source package in Precise:
  Triaged

Bug description:
  I found the workaround (and proof) for this bug is posted here:
  
http://confoundedtech.blogspot.com/2011/06/enable-wol-on-ubuntu-hp-microserver.html

  The relevant info is below
  =
  To get WOL to work the ethernet interface must be properly brought down as 
part of the system shutdown. This should be performed as part of run levels rc0 
and rc6, noting that Linux typically has 7 different run levels (or operating 
modes):
  rc0.d - System Halted
  rc1.d - Single User Mode
  rc2.d - Single User Mode with Networking
  rc3.d - Multi-User Mode - boot up in text mode
  rc4.d - Not yet Defined
  rc5.d - Multi-User Mode - boot up in X Windows
  rc6.d - Shutdown & Reboot
  A simple script can be created to bring the ethernet interface down properly 
at shutdown:
  sudo vi /etc/rc6.d/wol_poweroff.sh

  
  It may contain:
  #!/bin/bash
  ifconfig eth0 down
  poweroff

  
  Change the script's permissions to make it executable:

  sudo chmod 755 /etc/rc6.d/wol_poweroff.sh

  
  Copy the script to work on system halt as well:

  sudo cp /etc/rc6.d/wol_poweroff.sh /etc/rc0.d/wol_poweroff.sh

  
  Change permissions to make it executable:

  sudo chmod 755 /etc/rc0.d/wol_poweroff.sh

  
  Job done. 

  
  To test power down the machine, sudo shutdown now or sudo poweroff , and use 
your favourite WOL tool to send a magic packet. Thanks to rockafeller and 
everyone else who have commented with various solutions.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: ifupdown 0.7~beta2ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 14 05:12:38 2012
  ProcEnviron:
   TERM=xterm
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/981461/+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 1866974] Re: The Diffie-Hellman prime sent by the server is not acceptable

2020-10-07 Thread Adolf Ruf
*** This bug is a duplicate of bug 1872778 ***
https://bugs.launchpad.net/bugs/1872778

After i upgraded to Ubuntu 20.04 the Evolution cannot send more E-Mails.
Failurmessesge: (in German)
Die Fehlremeldung war >> Fehler bei der Ausführung des TLS-Handshake: Die vom 
Server gesendete Diffie-Hellmann-Primzahl wurde nicht akzeptiert (zu kurz).<<.

Translate:
The error message was >> Error while executing the TLS handshake: The 
Diffie-Hellmann prime number sent by the server was not accepted (too short).<<.

Wat can i do now?

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

Title:
  The Diffie-Hellman prime sent by the server is not acceptable

Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  I can no longer connect to my ISP mail server.
  Works in previous version 19.10

  "The reported error was “Failed to get capabilities: Error performing
  TLS handshake: The Diffie-Hellman prime sent by the server is not
  acceptable (not long enough).”."

  I've tried finding a workaround but so far no luck.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: evolution 3.35.92-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 11:07:01 2020
  InstallationDate: Installed on 2020-03-03 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974/+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 1895865] Re: /usr/share/apport/dump_acpi_tables.py:PermissionError:/usr/share/apport/dump_acpi_tables.py@59:dump_acpi_tables:dump_acpi_table

2020-10-07 Thread Robie Basak
This needs SRU information please.

I'm also puzzled by comment 2, which doesn't seem to describe the same
issue as the upload in Focal. Did some bug numbers get confused?

** Changed in: apport (Ubuntu Focal)
   Status: In Progress => Incomplete

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

Title:
  
/usr/share/apport/dump_acpi_tables.py:PermissionError:/usr/share/apport/dump_acpi_tables.py@59:dump_acpi_tables:dump_acpi_table

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Incomplete
Status in apport source package in Groovy:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu45, the problem page at 
https://errors.ubuntu.com/problem/ad705c1a5e4068bcae9d4261519bac8fac5cb57f 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1895865/+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 1898729] Re: shim can end up being removed

2020-10-07 Thread Iain Lane
That does sound useful and worth scheduling I think. I didn't know about
that until now!

I'll try to find some time soon to go back to the release I installed
from and take a look there, per Steve's suggestion.

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

Title:
  shim can end up being removed

Status in apt package in Ubuntu:
  New
Status in shim package in Ubuntu:
  New

Bug description:
  I just did a set of package updates in focal that ended up with shim
  shim-signed mokutil being autoremoved.

  I rebooted without noticing, and had to manually recover the system
  thereafter. :(

  Julian says there was a period of time where these were marked auto. I
  suppose that I installed during this window, and now some dependency
  change meant that as far as apt was concerned they weren't required
  any more.

  Can we please consider never proposing these packages for autoremoval?
  apt has NeverAutoRemove for this which could be used, or some other
  appropriate method.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898729/+subscriptions

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


[Touch-packages] [Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected

2020-10-07 Thread Alex
I've just used the 20.04.1 installer. Connected to the internet during
installation, chose full installation, upgrade during installation and
third-party drivers. I'm on an old intel and Nvidia, 650 TI as far as I
remember. Crashed in about 85% of completion. My first Ubuntu
installation, so would like to know if I should reinstall with different
settings or fix it as is. Don't expect anyone to answer tho...

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

Title:
  Installation fails when  "Install Third-Party Drivers" is selected

Status in GLibC:
  New
Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  Invalid

Bug description:
  Please use the latest daily installer images if you would like to enable 
third-party drivers during installation:
  http://www.cdimage.ubuntu.com/focal/daily-live/current/

  [Original Bug Text]

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

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1871268/+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 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected

2020-10-07 Thread Mohammad Mahdi Sharafi
I used the latest ubuntu installer but it happened again!!!

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

Title:
  Installation fails when  "Install Third-Party Drivers" is selected

Status in GLibC:
  New
Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  Invalid

Bug description:
  Please use the latest daily installer images if you would like to enable 
third-party drivers during installation:
  http://www.cdimage.ubuntu.com/focal/daily-live/current/

  [Original Bug Text]

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

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1871268/+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 1898729] Re: shim can end up being removed

2020-10-07 Thread Julian Andres Klode
APT still needs to offer a better experience for removing protected
packages with an extra --allow-remove-protected flag instead of
(re)using --allow-remove-essential, but it's still a useful feature.

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

Title:
  shim can end up being removed

Status in apt package in Ubuntu:
  New
Status in shim package in Ubuntu:
  New

Bug description:
  I just did a set of package updates in focal that ended up with shim
  shim-signed mokutil being autoremoved.

  I rebooted without noticing, and had to manually recover the system
  thereafter. :(

  Julian says there was a period of time where these were marked auto. I
  suppose that I installed during this window, and now some dependency
  change meant that as far as apt was concerned they weren't required
  any more.

  Can we please consider never proposing these packages for autoremoval?
  apt has NeverAutoRemove for this which could be used, or some other
  appropriate method.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898729/+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 1898729] Re: shim can end up being removed

2020-10-07 Thread Julian Andres Klode
We could mark bootloader packages as Protected: yes (Important: yes
before groovy). That would not only prevent autoremoval, it would also
add another step to manual removal as it triggers the same removal
prompts as essential packages.

Arguably top-level kernel packages, oem metapackages should have those
set too.

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

Title:
  shim can end up being removed

Status in apt package in Ubuntu:
  New
Status in shim package in Ubuntu:
  New

Bug description:
  I just did a set of package updates in focal that ended up with shim
  shim-signed mokutil being autoremoved.

  I rebooted without noticing, and had to manually recover the system
  thereafter. :(

  Julian says there was a period of time where these were marked auto. I
  suppose that I installed during this window, and now some dependency
  change meant that as far as apt was concerned they weren't required
  any more.

  Can we please consider never proposing these packages for autoremoval?
  apt has NeverAutoRemove for this which could be used, or some other
  appropriate method.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898729/+subscriptions

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


[Touch-packages] [Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected

2020-10-07 Thread Julian Andres Klode
** Changed in: glibc (Ubuntu)
 Assignee: Harsh Dudhat (dudhat-harsh) => (unassigned)

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

Title:
  Installation fails when  "Install Third-Party Drivers" is selected

Status in GLibC:
  New
Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  Invalid

Bug description:
  Please use the latest daily installer images if you would like to enable 
third-party drivers during installation:
  http://www.cdimage.ubuntu.com/focal/daily-live/current/

  [Original Bug Text]

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

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1871268/+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 1841023] Re: [Strix 15 GL503GE, Realtek ALC295, Black Headphone Out, Left] No sound at all

2020-10-07 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [Strix 15 GL503GE, Realtek ALC295, Black Headphone Out, Left] No sound
  at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  sometimes headphone working, but sometimes are not working
  if not working, im restart my laptop, sometimes fix this problem, but 
sometimes are not fix

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sycloner  11744 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 22 11:42:04 2019
  InstallationDate: Installed on 2019-08-14 (7 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sycloner  11744 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [Strix 15 GL503GE, Realtek ALC295, Black Headphone Out, Left] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503GE.316
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503GE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503GE.316:bd07/19/2019:svnASUSTeKCOMPUTERINC.:pnStrix15GL503GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503GE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: Strix
  dmi.product.name: Strix 15 GL503GE
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1841023/+subscriptions

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


[Touch-packages] [Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected

2020-10-07 Thread Harsh Dudhat
** Changed in: glibc (Ubuntu)
 Assignee: (unassigned) => Harsh Dudhat (dudhat-harsh)

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

Title:
  Installation fails when  "Install Third-Party Drivers" is selected

Status in GLibC:
  New
Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  Invalid

Bug description:
  Please use the latest daily installer images if you would like to enable 
third-party drivers during installation:
  http://www.cdimage.ubuntu.com/focal/daily-live/current/

  [Original Bug Text]

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

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1871268/+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 1884514] Re: [FFe][20.10 FEAT] zlib/gzip hardware compression enablement

2020-10-07 Thread Frank Heimes
The changes landed in groovy proposed:
zlib1g | 1:1.2.11.dfsg-2ubuntu3   | groovy-proposed | s390x
hence updating status to Fix Committed.

** Changed in: zlib (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

** No longer affects: gzip (Ubuntu)

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

Title:
  [FFe][20.10 FEAT] zlib/gzip hardware compression enablement

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in zlib package in Ubuntu:
  Fix Committed

Bug description:
  [Feature Freeze Exception]

  1. Feature:

  The latest s390x hardware comes with a new concept for hardware
  assisted compression/decompression, based on a 'Next Accelerator
  Function unit' (NXU). This is an on-chip concept, a co-processor for
  compression available to all cores on the same chip. It provides
  functions as normal 'problem state' instructions (in other words user
  space instructions that are directly consumable by libraries and
  applications) and supports DEFLATE compliant compression/decompression
  + GZIP CRC/ZLIB Adler.

  To enable this hardware support for zlib and gzip, zlib needs to be compiled 
with CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e".
  The value of 0x7e enables hardware compression for the compression levels 1-6 
(out of 0-9).
  There is a significant business value of having the enablement active by 
default, since tests on a system with 4 IFLs and hardware compression enabled 
this way offered (especially for DEFLATE as best case) a speed up of more than 
40x.

  2. Changes

  Adding CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" attributes/macro
  during build of zlib and gzip.

  3. Regression risk

  The concept is new and comes with IBM z15 and LinuxONE III only and is with 
that specific and limited to s390x.
  Hence a potential regressions of this late addition would be limited to s390x 
and there again with the above changes to zlib (and gzip).
  In case of unforeseen issues with the NXU hardware component, a fallback to 
software is done.
  On top a modified zlib package was build and made available in a PPA for 
further testing.
  This change should have been included earlier, but was blocked by other zlib 
tickets/bugs that needed to be fixed and integrated first (like LP 1893170), 
hence this request for late addition.
  __

  HW Compression need to be enabled with Default-Compression-Level 6.

  Adding following CFLAGS attributes during build of zlib and gzip
  "-DDFLTCC_LEVEL_MASK=0x7e"

  CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" ./configure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1884514/+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 1867157] Update Released

2020-10-07 Thread Łukasz Zemczak
The verification of the Stable Release Update for python3.8 has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Improve command-not-found package headers

Status in python-defaults package in Ubuntu:
  Fix Released
Status in python2.7 package in Ubuntu:
  Fix Released
Status in python3-defaults package in Ubuntu:
  Fix Released
Status in python3.8 package in Ubuntu:
  Fix Released
Status in python3.8 source package in Focal:
  Fix Released

Bug description:
  Improve command-not-found package headers

  
  command-not-found uses package metadata, and to improve the UX of the 
misspelled commands / proposed packages.

  python2.7-minimal should gain XB-Cnf-Visible-Pkgname: python2.7

  python3.8-minimal should gain XB-Cnf-Visible-Pkgname: python3.8

  python2-minimal should gain XB-Cnf-Visible-Pkgname: python2

  python3-minimal should gain XB-Cnf-Visible-Pkgname: python3

  This will then improve these messages from:

  """
command 'python2.7' from deb python2.7-minimal (2.7.17-1)
command 'python3.8' from deb python3.8-minimal (3.8.0-5)
command 'python2' from deb python2-minimal (2.7.17-2)
command 'python3' from deb python3-minimal (3.7.5-1ubuntu1)
  """

  To

  """
command 'python2.7' from deb python2.7 (2.7.17-1)
command 'python3.8' from deb python3.8 (3.8.0-5)
command 'python2' from deb python2 (2.7.17-2)
command 'python3' from deb python3 (3.7.5-1ubuntu1)
  """

  
  python3 should drop
  XB-Cnf-Extra-Commands: python
  XB-Cnf-Priority-Bonus: 5

  Such that it stops suggesting that somehow python is available from
  python3 package, which is a lie.

  There is a special case for "python" command hint in command-not-found
  already, which simply points people to "python3".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1867157/+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 1867157] Re: Improve command-not-found package headers

2020-10-07 Thread Launchpad Bug Tracker
This bug was fixed in the package python3.8 - 3.8.5-1~20.04

---
python3.8 (3.8.5-1~20.04) focal-proposed; urgency=medium

  * SRU: LP: #1889218. Backport Python 3.8.5 to 20.04 LTS.

python3.8 (3.8.5-1) unstable; urgency=medium

  * Python 3.8.5 release.
- Fix issue 41295, regression on __setattr__ in multiinheritance with
   metaclasses. Closes: #965069.

python3.8 (3.8.4-1) unstable; urgency=medium

  * Python 3.8.4 release.
  * Update VCS attributes in the control file.

python3.8 (3.8.4~rc1-1) unstable; urgency=medium

  * Python 3.8.4 release candidate 1.

python3.8 (3.8.3-1) unstable; urgency=medium

  * Python 3.8.3 release.
  * Add XB-Cnf-Visible-Pkgname header on the python*-minimal package to
point command-not-found at the full one. LP: #1867157

python3.8 (3.8.3~rc1-1) unstable; urgency=medium

  * Python 3.8.3 release candidate 1.
- Issue #38576, CVE-2019-18348: Disallow control characters in hostnames
  in http.client.
- Issue #39503, CVE-2020-8492: Denial of service in
  urllib.request.AbstractBasicAuthHandler.

 -- Matthias Klose   Tue, 28 Jul 2020 14:59:40 +0200

** Changed in: python3.8 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-18348

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8492

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

Title:
  Improve command-not-found package headers

Status in python-defaults package in Ubuntu:
  Fix Released
Status in python2.7 package in Ubuntu:
  Fix Released
Status in python3-defaults package in Ubuntu:
  Fix Released
Status in python3.8 package in Ubuntu:
  Fix Released
Status in python3.8 source package in Focal:
  Fix Released

Bug description:
  Improve command-not-found package headers

  
  command-not-found uses package metadata, and to improve the UX of the 
misspelled commands / proposed packages.

  python2.7-minimal should gain XB-Cnf-Visible-Pkgname: python2.7

  python3.8-minimal should gain XB-Cnf-Visible-Pkgname: python3.8

  python2-minimal should gain XB-Cnf-Visible-Pkgname: python2

  python3-minimal should gain XB-Cnf-Visible-Pkgname: python3

  This will then improve these messages from:

  """
command 'python2.7' from deb python2.7-minimal (2.7.17-1)
command 'python3.8' from deb python3.8-minimal (3.8.0-5)
command 'python2' from deb python2-minimal (2.7.17-2)
command 'python3' from deb python3-minimal (3.7.5-1ubuntu1)
  """

  To

  """
command 'python2.7' from deb python2.7 (2.7.17-1)
command 'python3.8' from deb python3.8 (3.8.0-5)
command 'python2' from deb python2 (2.7.17-2)
command 'python3' from deb python3 (3.7.5-1ubuntu1)
  """

  
  python3 should drop
  XB-Cnf-Extra-Commands: python
  XB-Cnf-Priority-Bonus: 5

  Such that it stops suggesting that somehow python is available from
  python3 package, which is a lie.

  There is a special case for "python" command hint in command-not-found
  already, which simply points people to "python3".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1867157/+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 1892643] Re: [SRU] Update libgweather to 3.36.1

2020-10-07 Thread Didier Roche
Hey Amr and thanks for making ubuntu better.
Do you mind double checking your patch?

Trying to apply it on 3.36.0-1, I get those chunks failing to apply
(tried both your .diff and .diff.gz):

patching file debian/changelog
patching file libgweather/gweather-weather.c
patching file libgweather/weather-metar.c
patching file meson.build
patching file NEWS
patching file po/lv.po
Hunk #1 FAILED at 6.
Hunk #2 FAILED at 830.
Hunk #3 FAILED at 849.
Hunk #4 FAILED at 944.
Hunk #5 FAILED at 1056.
5 out of 5 hunks FAILED -- saving rejects to file po/lv.po.rej
patching file po/nb.po
Hunk #1 succeeded at 1 with fuzz 2.
Hunk #2 FAILED at 17.
Hunk #3 FAILED at 246.
Hunk #4 FAILED at 537.
Hunk #5 FAILED at 843.
Hunk #6 FAILED at 932.
Hunk #7 FAILED at 1045.
Hunk #8 succeeded at 1074 with fuzz 2.
Hunk #9 succeeded at 1087 with fuzz 2.
Hunk #10 succeeded at 1101 with fuzz 2.
Hunk #11 succeeded at 1117 with fuzz 2.
6 out of 11 hunks FAILED -- saving rejects to file po/nb.po.rej
patching file po/uk.po
Hunk #1 FAILED at 1.
Hunk #2 FAILED at 455.
Hunk #3 FAILED at 544.
Hunk #4 FAILED at 726.
4 out of 4 hunks FAILED -- saving rejects to file po/uk.po.rej
patching file po-locations/nb.po
Hunk #1 succeeded at 1 with fuzz 2.
Hunk #4 FAILED at 1748.
Hunk #5 succeeded at 1757 with fuzz 1.
Hunk #6 FAILED at 2094.
Hunk #10 succeeded at 5624 with fuzz 1.
Hunk #12 FAILED at 6455.
Hunk #15 FAILED at 6532.
Hunk #16 FAILED at 6547.
Hunk #18 FAILED at 7011.
Hunk #20 succeeded at 7566 with fuzz 2.
Hunk #24 FAILED at 7946.
Hunk #27 succeeded at 8879 with fuzz 1.
Hunk #28 FAILED at 9175.
Hunk #32 FAILED at 9750.
Hunk #33 FAILED at 10098.
Hunk #34 FAILED at 10319.
Hunk #35 FAILED at 10361.
Hunk #36 FAILED at 10459.
Hunk #37 succeeded at 10491 with fuzz 2.
Hunk #38 FAILED at 10535.
Hunk #39 FAILED at 10871.
Hunk #40 FAILED at 10887.
Hunk #41 FAILED at 10915.
Hunk #43 FAILED at 11159.
18 out of 50 hunks FAILED -- saving rejects to file po-locations/nb.po.rej
patching file po-locations/ro.po
Hunk #1 FAILED at 9.
Hunk #4 FAILED at 10310.
Hunk #5 FAILED at 10352.
Hunk #6 FAILED at 10450.
Hunk #7 FAILED at 8.
5 out of 10 hunks FAILED -- saving rejects to file po-locations/ro.po.rej
patching file po-locations/sk.po
Hunk #1 succeeded at 10 with fuzz 1.
Hunk #2 succeeded at 1767 with fuzz 2.
Hunk #7 FAILED at 7278.
Hunk #8 FAILED at 7628.
Hunk #9 FAILED at 7673.
Hunk #10 succeeded at 7713 with fuzz 2.
Hunk #12 succeeded at 8882 with fuzz 2.
Hunk #13 FAILED at 10322.
Hunk #14 FAILED at 10364.
Hunk #15 FAILED at 10462.
Hunk #16 succeeded at 10500 with fuzz 2.
6 out of 18 hunks FAILED -- saving rejects to file po-locations/sk.po.rej
patching file po-locations/uk.po
Hunk #3 FAILED at 5066.
Hunk #4 FAILED at 17519.
2 out of 4 hunks FAILED -- saving rejects to file po-locations/uk.po.rej

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

Title:
  [SRU] Update libgweather to 3.36.1

Status in libgweather:
  Unknown
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Focal:
  New
Status in libgweather package in Debian:
  Unknown

Bug description:
  [Impact]

  libgweather 3.36.1 is a bug-fix release as part of GNOME 3.36.

  https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS

  This version works around the unavailability of the NOAA weather
  services by using very short-term forecasts as current weather
  conditions.

  Sometimes the current weather is not available because the NOAA
  weather servers aren't working correctly. Version 3.36.1 fixes the
  unavailability of current temperature in some locations.

  
  [Test case]

  Make sure that gnome-weather is still working properly and the weather
  in gnome-shell is shown when gnome-weather is installed.

  
  [Regression potential]

  The regression potential is low since the changes in version 3.36.1
  are small.

  
  [Other]

  libgweather 3.36.1 has been successfully built as a no-change backport
  from Groovy to Focal in my PPA and runs fine:

  
https://launchpad.net/~amribrahim1987/+archive/ubuntu/ppa/+packages?field.name_filter=libgweather_filter=published_filter=

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgweather-3-16 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 23 19:05:21 2020
  InstallationDate: Installed on 2020-04-26 (119 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libgweather
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/1892643/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to 

[Touch-packages] [Bug 1657625] Re: pulseaudio crashed with SIGABRT in pa_hook_slot_free() from pa_dynarray_free() from pa_module_load() from pa_cli_command_load() from pa_cli_command_execute_line_stat

2020-10-07 Thread Daniel van Vugt
** Tags removed: artful yakkety zesty
** Tags added: focal

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

Title:
  pulseaudio crashed with SIGABRT in pa_hook_slot_free() from
  pa_dynarray_free() from pa_module_load() from pa_cli_command_load()
  from pa_cli_command_execute_line_stateful()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/d769d435e3909253da5742ef109befab0758706e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1657625/+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