[Touch-packages] [Bug 1865831] Re: bug

[Daniel van Vugt]

Please describe what kind of problem you are experiencing.

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  bug

Status in Ubuntu:
  Incomplete

Bug description:
  bugbugbugb

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  3 11:05:07 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:062e]
  InstallationDate: Installed on 2020-02-26 (5 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 8087:8001 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E7450
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=bf009119-6b69-4fe9-a305-709e07c8e9fe ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D8H72
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/01/2015:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0D8H72:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.product.sku: 062E
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/1865831/+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 1867066] Re: [Dell XPS M1530] Touchpad issues

[Daniel van Vugt]

I can see two issues:

[54.601] (II) event4  - AlpsPS/2 ALPS GlidePoint: is tagged by udev as: 
Touchpad
[54.602] (II) event4  - AlpsPS/2 ALPS GlidePoint: device is a touchpad
[54.602] (II) event4  - AlpsPS/2 ALPS GlidePoint: device removed

[54.603] (II) event4  - AlpsPS/2 ALPS GlidePoint: is tagged by udev as: 
Touchpad
[54.603] (II) event4  - AlpsPS/2 ALPS GlidePoint: device is a touchpad
[54.604] (II) config/udev: Adding input device AlpsPS/2 ALPS GlidePoint 
(/dev/input/mouse0)
[54.604] (II) No input driver specified, ignoring this device.
[54.604] (II) This device may have been added with another device file.

** Summary changed:

- tuoshpad issues
+ [Dell XPS M1530] Touchpad issues

** Package changed: xorg (Ubuntu) => xserver-xorg-input-libinput
(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/1867066

Title:
  [Dell XPS M1530] Touchpad issues

Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-input-libinput package in Ubuntu:
  Incomplete

Bug description:
  Good evening all
  I just change the laptop from lenovo to dell and can not find out how make 
work the touchpad. Can not use two-finger scroll, pgdn/up, right primary button 
and an external mouse neither. The bluetooth will never work again untill 
re-installing an OS from micro-horror-soft, switching up the bluetooth module 
and re-installing ubuntu back. But I still love Linux ! I will appreciate if 
you help me, in the meantime i keep searching by myself in the ubuntu's forum 
how to fix my issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
  Uname: Linux 4.15.0-88-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 23:49:44 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia-340, 340.107, 4.15.0-88-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G84M [GeForce 8600M GT] [1028:022e]
  InstallationDate: Installed on 2020-03-06 (5 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS M1530
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic 
root=UUID=d2388a4a-3b22-4fb6-af07-913d081f1cab ro quiet splash 
acpi_osi=!Windows 2012 vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0D501F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn0D501F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1530
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1866681] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1866681

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  [HP Pavilion dv9000] Mute toggles on/off while plugged into the
  headphone/speaker jack (19.04+)

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

Bug description:
  I'm on an HP Pavilion dv9000 (https://www.cnet.com/products/hp-
  pavilion-dv9000/specs/) built many years ago.

  
  Whenever I'm using any distro that's based on Ubuntu which was published from 
Version 19.04 onwards, I've been having a major issue with the mute button 
toggling on and off whenever I have something plugged into the audio out jack. 
I know that it's not the fault of XFCE, because I also use the latest version 
of Manjaro with XFCE on this same computer, and it works fine. I also know it's 
not any Red Hat-based distro, because I use Stella (which is a remix of CentOS 
6) also on this exact same computer, and it also works fine. Qubes, Mageia, and 
Fedora 31 also work perfectly fine and don't have this issue.

  My "lsb-release" is:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=19.10
  DISTRIB_CODENAME=eoan
  DISTRIB_DESCRIPTION="Ubuntu 19.10"

  and "apt-cache policy pulseaudio" outputs:
  pulseaudio:
Installed: 1:13.0-1ubuntu1.1
Candidate: 1:13.0-1ubuntu1.1
Version table:
   *** 1:13.0-1ubuntu1.1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  I've uploaded a short video of the problem that I recorded with my phone here:
  https://www.youtube.com/watch?v=GXaHXQA-5uQ

  
  The problem appears with Kali 2019 and 2020, Peppermint 19.04, Lubuntu 19.04, 
Xubuntu 19.04, and Sparky 5.10 and 2020.02.

  
  I've checked pretty much everything I can think of. There's a log for my ALSA 
help diagnostics results on my current computer (which works properly with 
18.04) at:
  http://alsa-project.org/db/?f=4859b85cd7fc32e7f01f8df63591b5a43dbf6829

  
  the result output of lspci is:
  [code]00:00.0 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2)
  00:00.1 RAM memory: NVIDIA Corporation C51 Memory Controller 0 (rev a2)
  00:00.2 RAM memory: NVIDIA Corporation C51 Memory Controller 1 (rev a2)
  00:00.3 RAM memory: NVIDIA Corporation C51 Memory Controller 5 (rev a2)
  00:00.4 RAM memory: NVIDIA Corporation C51 Memory Controller 4 (rev a2)
  00:00.5 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2)
  00:00.6 RAM memory: NVIDIA Corporation C51 Memory Controller 3 (rev a2)
  00:00.7 RAM memory: NVIDIA Corporation C51 Memory Controller 2 (rev a2)
  00:02.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:03.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:04.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:09.0 RAM memory: NVIDIA Corporation MCP51 Host Bridge (rev a2)
  00:0a.0 ISA bridge: NVIDIA Corporation MCP51 LPC Bridge (rev a3)
  00:0a.1 SMBus: NVIDIA Corporation MCP51 SMBus (rev a3)
  00:0a.3 Co-processor: NVIDIA Corporation MCP51 PMU (rev a3)
  00:0b.0 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3)
  00:0b.1 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3)
  00:0d.0 IDE interface: NVIDIA Corporation MCP51 IDE (rev f1)
  00:0e.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1)
  00:0f.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1)
  00:10.0 PCI bridge: NVIDIA Corporation MCP51 PCI Bridge (rev a2)
  00:10.1 Audio device: NVIDIA Corporation MCP51 High Definition Audio (rev a2)
  00:14.0 Bridge: NVIDIA Corporation MCP51 Ethernet Controller (rev a3)
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
Address Map
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
  03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4311 802.11b/g 

[Touch-packages] [Bug 1866933] Re: Xorg freeze

[Daniel van Vugt]

Please run:

  apport-collect 1866933

now that the bug has been assigned to the correct package.

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Summary changed:

- Xorg freeze
+ Gnome Shell freeze

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  Gnome Shell freeze

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  when I click on the Activities button and try to start an application
  my X session freezes. I can move the mouse around and bring up the
  dock on the side of the screen, but no windows will come up. This
  problem does not come up if I open applications from the applications
  menu, dock, or terminal. I can only solve it by logging out and
  logging back in.

  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 10 20:12:16 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.4, 5.4.0-14-generic, x86_64: installed
   virtualbox-guest, 6.1.4, 5.4.0-14-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last few days
  GraphicsCard:
   Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Iris Graphics 540 [8086:2063]
  InstallationDate: Installed on 2017-10-19 (873 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SYSKLi35.86A.0071.2019.0524.1102
  dmi.board.asset.tag:
   �[�
  dmi.board.name: NUC6i5SYB
  dmi.board.vendor: Intel corporation
  dmi.board.version: H81131-505
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSYSKLi35.86A.0071.2019.0524.1102:bd05/24/2019:svn:pn:pvr:rvnIntelcorporation:rnNUC6i5SYB:rvrH81131-505:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  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+git20190815-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/gnome-shell/+bug/1866933/+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 1866682] Re: Mute toggles on/off while plugged into the headphone/speaker jack (19.04+)

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1866681
   [HP Pavilion dv9000] Mute toggles on/off while plugged into the 
headphone/speaker jack (19.04+)

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

Title:
  Mute toggles on/off while plugged into the headphone/speaker jack
  (19.04+)

Status in alsa-utils package in Ubuntu:
  New

Bug description:
  I'm on an HP Pavilion dv9000 (https://www.cnet.com/products/hp-
  pavilion-dv9000/specs/) built many years ago.

  
  Whenever I'm using any distro that's based on Ubuntu which was published from 
Version 19.04 onwards, I've been having a major issue with the mute button 
toggling on and off whenever I have something plugged into the audio out jack. 
I know that it's not the fault of XFCE, because I also use the latest version 
of Manjaro with XFCE on this same computer, and it works fine. I also know it's 
not any Red Hat-based distro, because I use Stella (which is a remix of CentOS 
6) also on this exact same computer, and it also works fine. Qubes, Mageia, and 
Fedora 31 also work perfectly fine and don't have this issue.

  My "lsb-release" is:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=19.10
  DISTRIB_CODENAME=eoan
  DISTRIB_DESCRIPTION="Ubuntu 19.10"

  and "apt-cache policy alsa-utils" outputs:
  alsa-utils:
Installed: 1.1.9-0ubuntu1
Candidate: 1.1.9-0ubuntu1
Version table:
   *** 1.1.9-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  I've uploaded a short video of the problem that I recorded with my phone here:
  https://www.youtube.com/watch?v=GXaHXQA-5uQ

  
  The problem appears with Kali 2019 and 2020, Peppermint 19.04, Lubuntu 19.04, 
Xubuntu 19.04, and Sparky 5.10 and 2020.02.

  
  I've checked pretty much everything I can think of. There's a log for my ALSA 
help diagnostics results on my current computer (which works properly with 
18.04) at:
  http://alsa-project.org/db/?f=4859b85cd7fc32e7f01f8df63591b5a43dbf6829

  
  the result output of lspci is:
  [code]00:00.0 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2)
  00:00.1 RAM memory: NVIDIA Corporation C51 Memory Controller 0 (rev a2)
  00:00.2 RAM memory: NVIDIA Corporation C51 Memory Controller 1 (rev a2)
  00:00.3 RAM memory: NVIDIA Corporation C51 Memory Controller 5 (rev a2)
  00:00.4 RAM memory: NVIDIA Corporation C51 Memory Controller 4 (rev a2)
  00:00.5 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2)
  00:00.6 RAM memory: NVIDIA Corporation C51 Memory Controller 3 (rev a2)
  00:00.7 RAM memory: NVIDIA Corporation C51 Memory Controller 2 (rev a2)
  00:02.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:03.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:04.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:09.0 RAM memory: NVIDIA Corporation MCP51 Host Bridge (rev a2)
  00:0a.0 ISA bridge: NVIDIA Corporation MCP51 LPC Bridge (rev a3)
  00:0a.1 SMBus: NVIDIA Corporation MCP51 SMBus (rev a3)
  00:0a.3 Co-processor: NVIDIA Corporation MCP51 PMU (rev a3)
  00:0b.0 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3)
  00:0b.1 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3)
  00:0d.0 IDE interface: NVIDIA Corporation MCP51 IDE (rev f1)
  00:0e.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1)
  00:0f.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1)
  00:10.0 PCI bridge: NVIDIA Corporation MCP51 PCI Bridge (rev a2)
  00:10.1 Audio device: NVIDIA Corporation MCP51 High Definition Audio (rev a2)
  00:14.0 Bridge: NVIDIA Corporation MCP51 Ethernet Controller (rev a3)
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
Address Map
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
  03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4311 802.11b/g 
WLAN (rev 01)
  05:00.0 VGA compatible controller: NVIDIA Corporation G73M [GeForce Go 7600] 
(rev a1)
  07:05.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
  07:05.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host 
Adapter (rev 19)
  07:05.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter 
(rev 0a)
  07:05.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 
05)[/code]

  and my output for arecord -l is:
  [code] List of CAPTURE Hardware Devices 
  card 0: NVidia [HDA NVidia], device 0: CX20549 Analog [CX20

[Touch-packages] [Bug 1866681] Re: Mute toggles on/off while plugged into the headphone/speaker jack (19.04+)

[Daniel van Vugt]

Please try editing /etc/pulse/default.pa and commenting out the line:

  load-module module-switch-on-connect

and then reboot.

Although regardless of whether that works, this sounds like a model-
specific bug so will probably be assigned to alsa-driver or the kernel.

** Summary changed:

- Mute toggles on/off while plugged into the headphone/speaker jack (19.04+) 
+ [HP Pavilion dv9000] Mute toggles on/off while plugged into the 
headphone/speaker jack (19.04+)

** Also affects: alsa-driver (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  [HP Pavilion dv9000] Mute toggles on/off while plugged into the
  headphone/speaker jack (19.04+)

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

Bug description:
  I'm on an HP Pavilion dv9000 (https://www.cnet.com/products/hp-
  pavilion-dv9000/specs/) built many years ago.

  
  Whenever I'm using any distro that's based on Ubuntu which was published from 
Version 19.04 onwards, I've been having a major issue with the mute button 
toggling on and off whenever I have something plugged into the audio out jack. 
I know that it's not the fault of XFCE, because I also use the latest version 
of Manjaro with XFCE on this same computer, and it works fine. I also know it's 
not any Red Hat-based distro, because I use Stella (which is a remix of CentOS 
6) also on this exact same computer, and it also works fine. Qubes, Mageia, and 
Fedora 31 also work perfectly fine and don't have this issue.

  My "lsb-release" is:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=19.10
  DISTRIB_CODENAME=eoan
  DISTRIB_DESCRIPTION="Ubuntu 19.10"

  and "apt-cache policy pulseaudio" outputs:
  pulseaudio:
Installed: 1:13.0-1ubuntu1.1
Candidate: 1:13.0-1ubuntu1.1
Version table:
   *** 1:13.0-1ubuntu1.1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  I've uploaded a short video of the problem that I recorded with my phone here:
  https://www.youtube.com/watch?v=GXaHXQA-5uQ

  
  The problem appears with Kali 2019 and 2020, Peppermint 19.04, Lubuntu 19.04, 
Xubuntu 19.04, and Sparky 5.10 and 2020.02.

  
  I've checked pretty much everything I can think of. There's a log for my ALSA 
help diagnostics results on my current computer (which works properly with 
18.04) at:
  http://alsa-project.org/db/?f=4859b85cd7fc32e7f01f8df63591b5a43dbf6829

  
  the result output of lspci is:
  [code]00:00.0 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2)
  00:00.1 RAM memory: NVIDIA Corporation C51 Memory Controller 0 (rev a2)
  00:00.2 RAM memory: NVIDIA Corporation C51 Memory Controller 1 (rev a2)
  00:00.3 RAM memory: NVIDIA Corporation C51 Memory Controller 5 (rev a2)
  00:00.4 RAM memory: NVIDIA Corporation C51 Memory Controller 4 (rev a2)
  00:00.5 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2)
  00:00.6 RAM memory: NVIDIA Corporation C51 Memory Controller 3 (rev a2)
  00:00.7 RAM memory: NVIDIA Corporation C51 Memory Controller 2 (rev a2)
  00:02.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:03.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:04.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:09.0 RAM memory: NVIDIA Corporation MCP51 Host Bridge (rev a2)
  00:0a.0 ISA bridge: NVIDIA Corporation MCP51 LPC Bridge (rev a3)
  00:0a.1 SMBus: NVIDIA Corporation MCP51 SMBus (rev a3)
  00:0a.3 Co-processor: NVIDIA Corporation MCP51 PMU (rev a3)
  00:0b.0 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3)
  00:0b.1 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3)
  00:0d.0 IDE interface: NVIDIA Corporation MCP51 IDE (rev f1)
  00:0e.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1)
  00:0f.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1)
  00:10.0 PCI bridge: NVIDIA Corporation MCP51 PCI Bridge (rev a2)
  00:10.1 Audio device: NVIDIA Corporation MCP51 High Definition Audio (rev a2)
  00:14.0 Bridge: NVIDIA Corporation MCP51 Ethernet Controller (rev a3)
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
Address Map
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
  03:00.0 Network controller: Broadcom Inc. and subsidiaries B

[Touch-packages] [Bug 1866616] Re: 2nd display stopped working

[Daniel van Vugt]

** Tags added: amdgpu

** Summary changed:

- 2nd display stopped working
+ [amdgpu] 2nd display stopped working

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

** Also affects: xserver-xorg-video-amdgpu (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: multimonitor

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

Title:
  [amdgpu] 2nd display stopped working

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  The 2nd display (attached to DVI) has stopped being detected but is
  used by bios and grub (output ceases once the spinning boot animation
  starts).  I was away for a week but it was working prior to leaving.
  I've notices that Xorg.0.log shows DVI-D-0 disconnected where the 2nd
  monitor should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  9 06:13:23 2020
  DistUpgraded: 2020-01-31 09:33:31,151 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA 
controller])
     Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470]
  InstallationDate: Installed on 2017-04-21 (1052 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
  MachineType: Micro-Star International Co., Ltd. MS-7A34
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-01-31 (37 days ago)
  dmi.bios.date: 01/23/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.M0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350 TOMAHAWK (MS-7A34)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.M0:bd01/23/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A34
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  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+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Oct 15 10:44:00 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.20.1-3ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866616/+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 1867090] [NEW] IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0

[ytxmobile]

Public bug reported:

When I switch to Chinese input mode (Intelligent Pinyin) and try to type 
Chinese into Atom 1.45.0, it simply doesn't work.
When I type the letters into the window, it shall bring up the candidate list 
for me to pick words. But instead, the letters are directly typed into the 
window, but not Chinese characters.

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


** Tags: chinese

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

Title:
  IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0

Status in ibus package in Ubuntu:
  New

Bug description:
  When I switch to Chinese input mode (Intelligent Pinyin) and try to type 
Chinese into Atom 1.45.0, it simply doesn't work.
  When I type the letters into the window, it shall bring up the candidate list 
for me to pick words. But instead, the letters are directly typed into the 
window, but not Chinese characters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1867090/+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 1867081] Re: Password textbox misaligned with username

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Password textbox misaligned with username

Status in shadow package in Ubuntu:
  New

Bug description:
  When I wake my computer and login the textbox for the password is
  aligned slightly to the right.

  Ubuntu 20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: login 1:4.8.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 21:55:27 2020
  InstallationDate: Installed on 2020-03-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200310)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1867081/+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 1866427] Re: bluetooth mouse wheel not working after suspend/reconnect

[Daniel van Vugt]

** Changed in: bluez (Ubuntu)
   Status: New => Invalid

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

Title:
  bluetooth mouse wheel not working after suspend/reconnect

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  1) Description:   Ubuntu 18.04.4 LTS
  Release:  18.04

  2) bluez:
Installed: 5.50-0ubuntu0ppa1
Candidate: 5.50-0ubuntu0ppa1
Version table:
   *** 5.50-0ubuntu0ppa1 500
  500 http://ppa.launchpad.net/bluetooth/bluez/ubuntu bionic/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.48-0ubuntu3.3 500
  500 http://ftp.daum.net/ubuntu bionic-updates/main amd64 Packages
   5.48-0ubuntu3 500
  500 http://ftp.daum.net/ubuntu bionic/main amd64 Packages

  3) My bluetooth mouse(Surface Precision Mouse) wheel is not working
  after suspended. It's working fine at first. This phenomenon occurs
  after suspended. It's not only for pc suspended but also mouse power
  on/off. Both the mouse cursor and click are normal. Only the wheels do
  not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1866427/+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 1866523] Re: Kernel 5.6-rc4 wont compile with nvidia 440.64

[Daniel van Vugt]

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

** Also affects: nvidia-graphics-drivers-440 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Kernel 5.6-rc4 wont compile with nvidia 440.64

Status in linux package in Ubuntu:
  New
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New

Bug description:
  According to Nvidia 440.64 should compile with kernel 5.6

  Attempted kernel install with UKUU 19.12.1

  make.log attached

  make[1]: Entering directory '/usr/src/linux-headers-5.6.0-050600rc4-generic'
  test -e include/generated/autoconf.h -a -e include/config/auto.conf || (  
\
  echo >&2; \
  echo >&2 "  ERROR: Kernel configuration is invalid.";

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  Uname: Linux 5.5.8-050508-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-23ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Mar  7 21:31:57 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.5.8-050508-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU104BM [GeForce RTX 2080 Mobile] [10de:1ed0] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TU104BM [GeForce RTX 2080 Mobile] 
[1043:135f]
  InstallationDate: Installed on 2020-03-03 (4 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTeK COMPUTER INC. ROG G703GXR_G703GXR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.8-050508-generic 
root=UUID=3fc82c83-da27-480b-a875-214d33bc18e5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G703GXR.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G703GXR
  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.:bvrG703GXR.302:bd07/11/2019:svnASUSTeKCOMPUTERINC.:pnROGG703GXR_G703GXR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG703GXR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: ROG G703GXR_G703GXR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/linux/+bug/1866523/+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 1867081] [NEW] Password textbox misaligned with username

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When I wake my computer and login the textbox for the password is
aligned slightly to the right.

Ubuntu 20.04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: login 1:4.8.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 11 21:55:27 2020
InstallationDate: Installed on 2020-03-11 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200310)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: shadow
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal wayland-session
-- 
Password textbox misaligned with username
https://bugs.launchpad.net/bugs/1867081
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to shadow 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 1866427] Re: bluetooth mouse wheel not working after suspend/reconnect

[Daniel van Vugt]

'5.50-0ubuntu0ppa1' is not part of Ubuntu and is not supported. Please
remove that PPA from your system and then if the problem persists open a
new bug by running:

  ubuntu-bug bluez

or

  ubuntu-bug linux


** Tags added: bionic

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

Title:
  bluetooth mouse wheel not working after suspend/reconnect

Status in bluez package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu 18.04.4 LTS
  Release:  18.04

  2) bluez:
Installed: 5.50-0ubuntu0ppa1
Candidate: 5.50-0ubuntu0ppa1
Version table:
   *** 5.50-0ubuntu0ppa1 500
  500 http://ppa.launchpad.net/bluetooth/bluez/ubuntu bionic/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.48-0ubuntu3.3 500
  500 http://ftp.daum.net/ubuntu bionic-updates/main amd64 Packages
   5.48-0ubuntu3 500
  500 http://ftp.daum.net/ubuntu bionic/main amd64 Packages

  3) My bluetooth mouse(Surface Precision Mouse) wheel is not working
  after suspended. It's working fine at first. This phenomenon occurs
  after suspended. It's not only for pc suspended but also mouse power
  on/off. Both the mouse cursor and click are normal. Only the wheels do
  not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1866427/+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 1854120] Re: Screen contents visible briefly on lock screen on resolution change

[Dushyant]

Hi,

This was very hard to replicate multiple times on my setup later. I also
have a nagging feeling, It could be possibly be an issue with AnyDesk
actually showing my host screen IDE for a fraction of a second which
matched my Ubuntu screen which brought up the confusion.

I myself can't accurately replicate this again, please feel free to close
the issue.


Thanks & Regards,

-Dushyant Min


On Wed, Mar 11, 2020 at 8:21 PM Marc Deslauriers <
marc.deslauri...@canonical.com> wrote:

> ** Changed in: lightdm (Ubuntu)
>Status: New => Triaged
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1854120
>
> Title:
>   Screen contents visible briefly on lock screen on resolution change
>
> Status in lightdm package in Ubuntu:
>   Triaged
>
> Bug description:
>   I am using a remote application to AnyDesk to remote access my Ubuntu
>   16.04 LTS 64 bit. On the application we can resize the screen and have
>   the resolution of the target computer scale up and down when this is
>   done.
>
>   When the computer is locked on the login screen if the screen is
>   resized ( resolution changes ) - For a brief fraction of a second the
>   unlocked screen flashes and the login screen shows up again. I think
>   this is a security breach to be able to peek into the inside contents
>   even though the computer is locked.
>
>   Please feel free to close this issue if this is an already known issue
>   or if its already fixed in later releases.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1854120/+subscriptions
>

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

Title:
  Screen contents visible briefly on lock screen on resolution change

Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  I am using a remote application to AnyDesk to remote access my Ubuntu
  16.04 LTS 64 bit. On the application we can resize the screen and have
  the resolution of the target computer scale up and down when this is
  done.

  When the computer is locked on the login screen if the screen is
  resized ( resolution changes ) - For a brief fraction of a second the
  unlocked screen flashes and the login screen shows up again. I think
  this is a security breach to be able to peek into the inside contents
  even though the computer is locked.

  Please feel free to close this issue if this is an already known issue
  or if its already fixed in later releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1854120/+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 1866712] Re: Graphic glitches with Nvidia 440 on Dell XPS 15 9570

[Daniel van Vugt]

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

** Also affects: nvidia-graphics-drivers-440 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Graphic glitches with Nvidia 440 on Dell XPS 15 9570

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New

Bug description:
  I am experiencing intermittent graphical glitches. I couldn't find
  where this had been reported before so please excuse the duplicate if
  this is a known issue. I tried recording my screen to demonstrate what
  is happening but, although I am seeing the issue on the desktop, it
  does not show up in the video. I am using prime-select in intel mode.

  
  System:Host: rex Kernel: 5.5.7-050507-generic x86_64 bits: 64 Desktop: 
Gnome 3.35.91 
 Distro: Ubuntu 20.04 LTS (Focal Fossa) 
  Machine:   Type: Laptop System: Dell product: XPS 15 9570 v: N/A serial: 
 
 Mobo: Dell model: 0D0T05 v: A00 serial:  UEFI: Dell 
v: 1.15.0 date: 12/25/2019 
  CPU:   Topology: 6-Core model: Intel Core i7-8750H bits: 64 type: MT MCP 
L2 cache: 9216 KiB 
 Speed: 2057 MHz min/max: 800/4100 MHz Core speeds (MHz): 1: 2112 
2: 894 3: 1909 4: 2159 5: 2345 6: 1979 
 7: 1579 8: 2316 9: 1214 10: 988 11: 2344 12: 929 
  Graphics:  Device-1: Intel UHD Graphics 630 driver: i915 v: kernel 
 Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] driver: N/A 
 Display: x11 server: X.Org 1.20.7 driver: modesetting,nvidia 
unloaded: fbdev,nouveau,vesa 
 resolution: 1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 
Mesa 20.0.0 
  Audio: Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel 
 Device-2: Texas Instruments PCM2902 Audio Codec type: USB driver: 
hid-generic,snd-usb-audio,usbhid 
 Sound Server: ALSA v: k5.5.7-050507-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.5.7-050507-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  9 13:20:11 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.59, 5.4.0-14-generic, x86_64: installed
   nvidia, 440.59, 5.5.7-050507-generic, x86_64: installed
   v4l2loopback, 0.12.3, 5.5.7-050507-generic, x86_64: installed
   virtualbox, 6.1.4, 5.5.7-050507-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c]
  InstallationDate: Installed on 2020-03-03 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303)
  MachineType: Dell Inc. XPS 15 9570
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.7-050507-generic 
root=UUID=5490caea-406b-4a4c-afee-178210995fe8 ro quiet splash 
mem_sleep_default=deep
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  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+git20190815-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/linux/+bug/1866712/+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 1866551] Re: software-properties package crashed with desktop on totem launch on ubuntu-mate-1804

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** Changed in: software-properties (Ubuntu)
   Status: New => Incomplete

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

Title:
  software-properties package crashed with desktop on totem launch on
  ubuntu-mate-1804

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  software-properties package crashed with desktop on totem launch on
  ubuntu-mate-1804.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.12
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Mar  8 21:39:01 2020
  InstallationDate: Installed on 2018-05-11 (666 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1866551/+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 1866552] Re: xorg crashed on totem launch on ubuntu-mate-1804

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  xorg crashed on totem launch on ubuntu-mate-1804

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  xorg crashed on totem launch on ubuntu-mate-1804.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Sun Mar  8 21:47:12 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:8694]
   NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:2476]
  InstallationDate: Installed on 2018-05-11 (666 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet 
K-2024 Multimedia Keyboard
   Bus 001 Device 002: ID 09da:c10a A4Tech Co., Ltd. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic 
root=UUID=c14b0e5e-bdb0-4d30-87f0-0879253545d0 ro acpi=force iomem=relaxed 
random.trust_cpu=on initcall_debug console=tty0 console=ttyS0,115200 
earlyprintk=ttyS0,115200
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-E/M.2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4210:bd05/28/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-E/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1866552/+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 1865499] Re: pulseaudio doesn't detect (new) USB headset

[Daniel van Vugt]

FYI, the relevant changes are documented in:

https://launchpad.net/ubuntu/+source/alsa-lib/1.1.3-5ubuntu0.3
https://launchpad.net/ubuntu/+source/alsa-lib/1.1.3-5ubuntu0.4

** Package changed: pulseaudio (Ubuntu) => alsa-lib (Ubuntu)

** Changed in: alsa-lib (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-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1865499

Title:
  pulseaudio doesn't detect (new) USB headset

Status in alsa-lib package in Ubuntu:
  Fix Committed

Bug description:
  When booting the system (Lenovo Thinkpad L480/L490), all connected USB
  headsets are recognized and can be used, and configured via
  pavucontrol.

  When hot-plugging the USB headset, either the speaker is recognized,
  or the microphone, rarely both. But when both are recognized, the
  microphone is always a "multichannel" device. When both the speaker
  and the "multichannel" microphone are recognized, only one can be used
  - either speaker or microphone. When selecting the speaker, the
  microphone is switched back to any other device available, them same
  goes for the microphone and the speaker - any other speaker is
  selected.

  A workaround is to plug in the USB headset and run "pkill -U $USER
  pulseaudio". Everything works fine until the next hot-plug (eg. a
  second headset).

  Running "lsb_release -a" gives   
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic

  Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
  our users are affected by this bug, all running the same Ubuntu and
  package versions. I activated the proposed repository to check if any
  updates available fix the problem, but to no avail. I also switched
  kernels (from 4.15 to 5.5 mainline from
  https://wiki.ubuntu.com/Kernel/MainlineBuilds).

  I read bug #1325282
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
  and it sounds somewhat very familiar, but instead of "env={}" in
  /usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
  Removing "env=env" doesn't resolve the problem.

  Do you require additional information?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1865499/+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 1866371] Re: Mouse cursor disappears in Ubuntu 20.04 on Wayland since 5th March update

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1867080
   [radeon] No mouse cursor drawn in Wayland session

** No longer affects: wayland (Ubuntu)

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

Title:
  Mouse cursor disappears in Ubuntu 20.04 on Wayland since 5th March
  update

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Hi, I run Ubuntu 20.04 (Gnome Shell) development version.

  Since I made the updates on 5th March, I have no more mouse cursor
  visible, on the login screen nor on the desktop session.

  Mouse is OK, as if I move it I can see some items / buttons
  highlighted, and if I click the mouse, it works well. I tried Yaru and
  DMZ Black themes, no cursor, it's completely invisible.

  I started several times, always no cursor. But if I switch to the Xorg
  (X11) session, mouse cursor is well back and visible.

  My graphic card :

  description: VGA compatible controller
 produit: Cape Verde XT [Radeon HD 7770/8760 / R7 250X]
 fabricant: Advanced Micro Devices, Inc. [AMD/ATI]
 identifiant matériel: 0
 information bus: pci@:01:00.0
 version: 00
 bits: 64 bits
 horloge: 33MHz
 fonctionnalités: pm pciexpress msi vga_controller bus_master cap_list 
rom
 configuration : driver=radeon latency=0

  Thanks !

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1866371/+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 1856884] Re: not proper sound device

[Daniel van Vugt]

Since you have updated now, could you please re-run:

  apport-collect 1856884

** This bug is no longer a duplicate of bug 1847570
   PulseAudio automatically switches to HDMI sound output on login

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

Title:
  not proper sound device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  when i insert or take out my headphones , the system doesn't send signal on 
my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1929 F pulseaudio
   /dev/snd/controlC1:  rob1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (326 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884/+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 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd

[Daniel van Vugt]

I know, I've asked for an update just now. Tracking more generally in:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bugs?field.tag=update-reverted

** Tags added: update-reverted

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

Title:
  pulseaudio now depends on libsnapd-glib1 which recommends snapd

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has
  libsnapd-glib1 as a dependency.

  This is complete and utter nonsense. I do not want cascading
  dependencies that have no business being installed on the systems I
  manage.

  Please rectify this at once.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+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 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen

[Daniel van Vugt]

** Also affects: linux via
   https://gitlab.freedesktop.org/drm/intel/issues/1377
   Importance: Unknown
   Status: Unknown

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

Title:
  [Intel Braswell] Cursor gets stuck on left side of the screen

Status in Linux:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When moving the cursor to the left side of the screen, it stops close
  to the edge. The cursor still moves over in the area but invisible
  until I move it out of the area. When it doesn't do this, glitching
  occurs on the screen where the cursor is until I log out. And on
  screen cast it shows the cursor going to the side of the screen and
  moving.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 09:49:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic 
root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-20-generic
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-408
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1767654/+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 1867079] [NEW] Typo in data/zh_CN/LC_MESSAGES/shadow.po

[Qijia Liu]

Public bug reported:

Correct me if it's not the proper place to point out typos. I can't find a 
Translatable template for this.
In the file data/zh_CN/LC_MESSAGES/shadow.po, every "登陆" should be “登录” in 
Chinese for "login".
I use 19.10, and the package version is 1:19.10+20191010. But this seems to be 
in every release.

** Affects: language-pack-gnome-zh-hans-base (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to language-pack-gnome-zh-
hans-base in Ubuntu.
https://bugs.launchpad.net/bugs/1867079

Title:
  Typo in data/zh_CN/LC_MESSAGES/shadow.po

Status in language-pack-gnome-zh-hans-base package in Ubuntu:
  New

Bug description:
  Correct me if it's not the proper place to point out typos. I can't find a 
Translatable template for this.
  In the file data/zh_CN/LC_MESSAGES/shadow.po, every "登陆" should be “登录” in 
Chinese for "login".
  I use 19.10, and the package version is 1:19.10+20191010. But this seems to 
be in every release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-zh-hans-base/+bug/1867079/+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 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed

[Dimitri John Ledkov]

Expected behaviour is:

$ python

Command 'python' not found, did you mean:

  command 'python3' from deb python3 (3.8.2-0ubuntu1)

Try: sudo apt install 

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

Title:
  Invoking "python" brings inappropriate response from command-not-found
  when python3 installed

Status in command-not-found package in Ubuntu:
  Triaged
Status in python3-defaults package in Ubuntu:
  Triaged
Status in command-not-found source package in Focal:
  Triaged
Status in python3-defaults source package in Focal:
  Triaged

Bug description:
  Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't
  have python 2.7 installed, but have python 3 installed as per default.

  Please see ascii-cast at
  https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 .

  Running `python` brings up text from command-not-found which suggests
  installing `python3` as a solution to the missing command. `python3`
  is already installed, is a later version than the one indicated by
  command-not-found and does not supply a binary or symlink named
  `python`.

  $ apt policy python
  python:
Installed: (none)
Candidate: (none)
Version table:
   2.7.17-1 -1
  100 /var/lib/dpkg/status
  $ apt policy python3
  python3:
Installed: 3.8.0-3
Candidate: 3.8.0-3
Version table:
   *** 3.8.0-3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt policy command-not-found
  command-not-found:
Installed: 19.10.0
Candidate: 19.10.0
Version table:
   *** 19.10.0 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  I don't know whether this is a bug in python3 or command-not-found
  (the latter of which doesn't seem to have been updated for 20.04 yet).
  i don't know if it is intentional that `python3` will not provide a
  binary or symlink named `python`. if that is the case, the output of
  `command-not-found` should be updated to reflect that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.0-3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Feb 17 01:35:16 2020
  InstallationDate: Installed on 2019-10-11 (128 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  SourcePackage: python3-defaults
  UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+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 1867066] [NEW] tuoshpad issues

[stanislav kralik]

Public bug reported:

Good evening all
I just change the laptop from lenovo to dell and can not find out how make work 
the touchpad. Can not use two-finger scroll, pgdn/up, right primary button and 
an external mouse neither. The bluetooth will never work again untill 
re-installing an OS from micro-horror-soft, switching up the bluetooth module 
and re-installing ubuntu back. But I still love Linux ! I will appreciate if 
you help me, in the meantime i keep searching by myself in the ubuntu's forum 
how to fix my issues.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
Uname: Linux 4.15.0-88-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
 GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 11 23:49:44 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia-340, 340.107, 4.15.0-88-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell G84M [GeForce 8600M GT] [1028:022e]
InstallationDate: Installed on 2020-03-06 (5 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. XPS M1530
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic 
root=UUID=d2388a4a-3b22-4fb6-af07-913d081f1cab ro quiet splash 
acpi_osi=!Windows 2012 vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/19/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0D501F
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn0D501F:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: XPS M1530
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  tuoshpad issues

Status in xorg package in Ubuntu:
  New

Bug description:
  Good evening all
  I just change the laptop from lenovo to dell and can not find out how make 
work the touchpad. Can not use two-finger scroll, pgdn/up, right primary button 
and an external mouse neither. The bluetooth will never work again untill 
re-installing an OS from micro-horror-soft, switching up the bluetooth module 
and re-installing ubuntu back. But I still love Linux ! I will appreciate if 
you help me, in the meantime i keep searching by myself in the ubuntu's forum 
how to fix my issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
  Uname: Linux 4.15.0-88-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured

[Touch-packages] [Bug 1867064] Re: Close buttons not rendering correctly

[Paul White]

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

** This bug has been marked a duplicate of bug 1861558
   Snap 'ed applicaitons have garbage on top of the window Close [x] button

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

Title:
  Close buttons not rendering correctly

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm not gonna lie, I'm not sure if this is the correct place to report
  this or not. In the Pick and Calculator Snaps, I noticed the close
  button is rendering incorrectly. I looked online and saw someone else
  is having the issue too and decided to report it. I haven't noticed it
  in any other applications. Nothing major, but worth submitting
  somewhere.

  Here is a screenshot of what I see: https://imgur.com/a/70IcsU6

  Here is the link to the other person's Reddit post:
  https://www.reddit.com/r/gnome/comments/ervfbz/strange_close_button/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Mar 11 16:40:44 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA 
controller])
 Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:085c Logitech, Inc. C922 Pro Stream Webcam
   Bus 001 Device 015: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 04d9:0024 Holtek Semiconductor, Inc. USB Gaming 
Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/fish
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=3ef07817-9408-490b-b7db-828fbd280f54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0410
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0410:bd09/06/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/1867064/+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 1867064] [NEW] Close buttons not rendering correctly

[Phillip Prado]

Public bug reported:

I'm not gonna lie, I'm not sure if this is the correct place to report
this or not. In the Pick and Calculator Snaps, I noticed the close
button is rendering incorrectly. I looked online and saw someone else is
having the issue too and decided to report it. I haven't noticed it in
any other applications. Nothing major, but worth submitting somewhere.

Here is a screenshot of what I see: https://imgur.com/a/70IcsU6

Here is the link to the other person's Reddit post:
https://www.reddit.com/r/gnome/comments/ervfbz/strange_close_button/

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Wed Mar 11 16:40:44 2020
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA 
controller])
   Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353]
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 046d:085c Logitech, Inc. C922 Pro Stream Webcam
 Bus 001 Device 015: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 004: ID 04d9:0024 Holtek Semiconductor, Inc. USB Gaming Keyboard
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/fish
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=3ef07817-9408-490b-b7db-828fbd280f54 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/06/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0410
dmi.board.asset.tag: Default string
dmi.board.name: Z170M-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0410:bd09/06/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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 eoan 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/1867064

Title:
  Close buttons not rendering correctly

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm not gonna lie, I'm not sure if this is the correct place to report
  this or not. In the Pick and Calculator Snaps, I noticed the close
  button is rendering incorrectly. I looked online and saw someone else
  is having the issue too and decided to report it. I haven't noticed it
  in any other applications. Nothing major, but worth submitting
  somewhere.

  Here is a screenshot of what I see: https://imgur.com/a/70IcsU6

  Here is the link to the other person's Reddit post:
  https://www.reddit.com/r/gnome/comments/ervfbz/strange_close_button/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Mar 11 16:40:44 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesme

[Touch-packages] [Bug 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Rafael David Tinoco]

I have created a PPA for this issue:

https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1864992

Please provide feedback if possible. I haven't done Focal yet because
git-ubuntu is facing a small problem importing latest focal source
package to do the merge.. will check it tomorrow.

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in kmod package in Ubuntu:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Disco:
  Won't Fix
Status in kmod source package in Eoan:
  In Progress
Status in kmod source package in Focal:
  In Progress

Bug description:
  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1864992/+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 1794478] Update Released

[Brian Murray]

The verification of the Stable Release Update for network-manager 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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1794478

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  In case creating bond interface, IPv4 address is not automatically
  assigned when IPv6 has manual setting.

  [Test Case]

  1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as 
original description.
  2. ipv6 manual, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses 
fe81::ff:fe97:a27f/64;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5;
  sudo nmcli c s bond0
  ##
  3. ipv6 auto, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method auto;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5

  sudo nmcli c s bond0
  ##

  when run #3, it is working, but with #2, it is not working.

  [Potential Regression]

  Actually nothing special. fix just remove if statement. but it needs
  Network Manager restarted.

  [Other informations]

  After upstream fix, it is working fine with #2 and #3 above.

  * Upstream bug and fix:

  https://bugzilla.redhat.com/show_bug.cgi?id=1575944
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35

  * Only affecting Bionic:

  $ git describe --contains f03ae35
  1.10.8~2

  $ rmadison network-manager
  ==> network-manager | 1.10.6-2ubuntu1.2   | bionic-updates
  network-manager | 1.20.4-2ubuntu2.2   | eoan-updates
  network-manager | 1.22.4-1ubuntu2 | focal

  [Original description]

  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.

  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux

  Machine Type = s390x

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto

  From /var/log/syslo

[Touch-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.10.6-2ubuntu1.4

---
network-manager (1.10.6-2ubuntu1.4) bionic; urgency=medium

  * d/p/start-ip-conf-when-master-carrier-goes-up.patch: device: start IP
configuration when master carrier goes up (LP: #1794478)

network-manager (1.10.6-2ubuntu1.3) bionic; urgency=medium

  * d/t/control: nm test requires dnsmasq-base (LP: #1850267)
  * d/t/killswitches-no-urfkill, d/t/urfkill-integration,
d/t/wpa-dhclient, d/t/nm, d/t/control:
- skip tests on s390 due to missing wireless kernel support
  (LP: #1855009)

 -- Seyeong Kim   Wed, 19 Feb 2020 14:59:10
+0900

** Changed in: network-manager (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  In case creating bond interface, IPv4 address is not automatically
  assigned when IPv6 has manual setting.

  [Test Case]

  1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as 
original description.
  2. ipv6 manual, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses 
fe81::ff:fe97:a27f/64;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5;
  sudo nmcli c s bond0
  ##
  3. ipv6 auto, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method auto;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5

  sudo nmcli c s bond0
  ##

  when run #3, it is working, but with #2, it is not working.

  [Potential Regression]

  Actually nothing special. fix just remove if statement. but it needs
  Network Manager restarted.

  [Other informations]

  After upstream fix, it is working fine with #2 and #3 above.

  * Upstream bug and fix:

  https://bugzilla.redhat.com/show_bug.cgi?id=1575944
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35

  * Only affecting Bionic:

  $ git describe --contains f03ae35
  1.10.8~2

  $ rmadison network-manager
  ==> network-manager | 1.10.6-2ubuntu1.2   | bionic-updates
  network-manager | 1.20.4-2ubuntu2.2   | eoan-updates
  network-manager | 1.22.4-1ubuntu2 | focal

  [Original description]

  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.

  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux

  Machine Type = s390x

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

[Touch-packages] [Bug 1850267] Update Released

[Brian Murray]

The verification of the Stable Release Update for network-manager 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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1850267

Title:
  autopkgtest 'nm' fails because it can't find dnsmasq

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Released

Bug description:
  [impact]

  test 'nm' fails because dnsmasq-base isn't installed

  [test case]

  see test results
  http://autopkgtest.ubuntu.com/packages/network-manager/bionic/amd64

  [regression potential]

  low, test fix only

  [other info]

  The d/t/control file 'nm' test section, for bionic, needs to include
  dnsmasq-base in its dep list.

  disco and later already include dnsmasq-base in test dep packages, and
  in xenial network-manager directly depends on dnsmasq-base.  So this
  is needed only for bionic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850267/+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 1855009] Re: autopkgtests all fail on s390x

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.10.6-2ubuntu1.4

---
network-manager (1.10.6-2ubuntu1.4) bionic; urgency=medium

  * d/p/start-ip-conf-when-master-carrier-goes-up.patch: device: start IP
configuration when master carrier goes up (LP: #1794478)

network-manager (1.10.6-2ubuntu1.3) bionic; urgency=medium

  * d/t/control: nm test requires dnsmasq-base (LP: #1850267)
  * d/t/killswitches-no-urfkill, d/t/urfkill-integration,
d/t/wpa-dhclient, d/t/nm, d/t/control:
- skip tests on s390 due to missing wireless kernel support
  (LP: #1855009)

 -- Seyeong Kim   Wed, 19 Feb 2020 14:59:10
+0900

** Changed in: network-manager (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  autopkgtests all fail on s390x

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager source package in Bionic:
  Fix Released
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Fix Released
Status in network-manager source package in Focal:
  Fix Released

Bug description:
  [impact]

  all autopkgtests fail on s390x

  [test case]

  check autopkgtest logs, e.g.
  http://autopkgtest.ubuntu.com/packages/network-manager

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/s390x/n/network-
  manager/20191130_001946_a5512@/log.gz

  autopkgtest [00:19:32]:  summary
  wpa-dhclient FAIL non-zero exit status 1
  nm.pyFAIL non-zero exit status 1
  killswitches-no-urfkill FAIL non-zero exit status 1
  urfkill-integration  FAIL non-zero exit status 1

  [regression potential]

  this essentially skips all the autopkgtests for network-manager on
  s390x, so regressions could occur now or in the future due to lack of
  testing on s390x.  However, all the tests already fail on s390x and
  have since xenial (or earlier), so there hasn't been any useful test
  coverage on s390x before; this doesn't change that.

  [other info]

  as mentioned in comment 2, wireless networking is specifically
  excluded on s390 systems:

  menuconfig WIRELESS
  bool "Wireless"
  depends on !S390
  default y

  The 'wpa-dhclient' test is specific to wireless, and both
  'killswitches-no-urfkill' and 'urfkill-integration' require rfkill
  which requires wireless, so none of those tests are valid on s390x,
  since it doesn't have any wireless support.

  However the 'nm.py' test does have some test cases that don't rely on
  wireless capability, but it would be much more intrusive to update the
  test to split out wired vs. wireless testing, and that might introduce
  test regressions on other archs.  The use case for network-manager on
  s390x in general is questionable, since s390x has no wireless support
  and obviously is never 'mobile', which are 2 main reasons to use
  network-manager instead of systemd-networkd.  Additionally, all tests
  are currently skipped on armhf due to the requirement for machine
  isolation (and armhf tests run in containers), so s390x is not the
  first arch to simply skip all network-manager autopkgtests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+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 1850267] Re: autopkgtest 'nm' fails because it can't find dnsmasq

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.10.6-2ubuntu1.4

---
network-manager (1.10.6-2ubuntu1.4) bionic; urgency=medium

  * d/p/start-ip-conf-when-master-carrier-goes-up.patch: device: start IP
configuration when master carrier goes up (LP: #1794478)

network-manager (1.10.6-2ubuntu1.3) bionic; urgency=medium

  * d/t/control: nm test requires dnsmasq-base (LP: #1850267)
  * d/t/killswitches-no-urfkill, d/t/urfkill-integration,
d/t/wpa-dhclient, d/t/nm, d/t/control:
- skip tests on s390 due to missing wireless kernel support
  (LP: #1855009)

 -- Seyeong Kim   Wed, 19 Feb 2020 14:59:10
+0900

** Changed in: network-manager (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  autopkgtest 'nm' fails because it can't find dnsmasq

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Released

Bug description:
  [impact]

  test 'nm' fails because dnsmasq-base isn't installed

  [test case]

  see test results
  http://autopkgtest.ubuntu.com/packages/network-manager/bionic/amd64

  [regression potential]

  low, test fix only

  [other info]

  The d/t/control file 'nm' test section, for bionic, needs to include
  dnsmasq-base in its dep list.

  disco and later already include dnsmasq-base in test dep packages, and
  in xenial network-manager directly depends on dnsmasq-base.  So this
  is needed only for bionic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850267/+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 1865504] Re: hwclock reports incorrect status in audit message

[Mauricio Faria de Oliveira]

** Tags added: sts-sponsor-mfo

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

Title:
  hwclock reports incorrect status in audit message

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Bionic:
  In Progress
Status in util-linux source package in Eoan:
  In Progress
Status in util-linux package in Debian:
  Unknown

Bug description:
  [Impact]

  hwclock reports incorrect status in audit message:
  - hwclock calls audit_log_user_message(3) to create an audit entry.
  - audit_log_user_message(3) result 1 is "success" and 0 is "failed".
  - hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse status.
  - Thus reports its status incorrectly in audit message.

  It is a requirement for Common Criteria Certification that hwclock
  reports correct status in audit message.

  This has been fixed upstream in https://github.com/karelzak/util-
  linux/commit/189edf1fe501ea39b35911337eab1740888fae7a

  [Test Steps]

  Steps to test:
  1. Install auditd
  2. Run following testcase,

  # hwclock
  2020-03-02 15:03:03.280351+

  # hwclock --set --date "1/1/2000 00:00:00"
  # echo $?
  0
  # hwclock
  2000-01-01 00:00:05.413924+

  # hwclock --utc --systohc
  # echo $?
  0
  # hwclock
  2020-03-02 15:07:00.264331+

  Following audit messages from /var/log/audit/audit.log,

  Note that last field in each audit record produced when hardware clock
  was modified has, "res=failed". Although, testcase shows no* failure
  occurred.

  type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0
  auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
  hostname=bionic-fips addr=? terminal=pts/0 res=failed'

  type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0
  auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
  hostname=bionic-fips addr=? terminal=pts/0 res=failed'

  [Regression Potential]

  Changes limited to the result value passed to audit_log_user_message(3),
  so the audit messages will change the 'res=' field (to correct result.)

  There should not be any regression to fix the status given to auditd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865504/+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 1865504] Re: hwclock reports incorrect status in audit message

[Mauricio Faria de Oliveira]

** Patch added: "lp1865504_eoan_util-linux.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865504/+attachment/5335833/+files/lp1865504_eoan_util-linux.debdiff

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

Title:
  hwclock reports incorrect status in audit message

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Bionic:
  In Progress
Status in util-linux source package in Eoan:
  In Progress
Status in util-linux package in Debian:
  Unknown

Bug description:
  [Impact]

  hwclock reports incorrect status in audit message:
  - hwclock calls audit_log_user_message(3) to create an audit entry.
  - audit_log_user_message(3) result 1 is "success" and 0 is "failed".
  - hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse status.
  - Thus reports its status incorrectly in audit message.

  It is a requirement for Common Criteria Certification that hwclock
  reports correct status in audit message.

  This has been fixed upstream in https://github.com/karelzak/util-
  linux/commit/189edf1fe501ea39b35911337eab1740888fae7a

  [Test Steps]

  Steps to test:
  1. Install auditd
  2. Run following testcase,

  # hwclock
  2020-03-02 15:03:03.280351+

  # hwclock --set --date "1/1/2000 00:00:00"
  # echo $?
  0
  # hwclock
  2000-01-01 00:00:05.413924+

  # hwclock --utc --systohc
  # echo $?
  0
  # hwclock
  2020-03-02 15:07:00.264331+

  Following audit messages from /var/log/audit/audit.log,

  Note that last field in each audit record produced when hardware clock
  was modified has, "res=failed". Although, testcase shows no* failure
  occurred.

  type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0
  auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
  hostname=bionic-fips addr=? terminal=pts/0 res=failed'

  type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0
  auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
  hostname=bionic-fips addr=? terminal=pts/0 res=failed'

  [Regression Potential]

  Changes limited to the result value passed to audit_log_user_message(3),
  so the audit messages will change the 'res=' field (to correct result.)

  There should not be any regression to fix the status given to auditd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865504/+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 1865504] Re: hwclock reports incorrect status in audit message

[Mauricio Faria de Oliveira]

Test/Bionic:
===

$ lsb_release -cs
bionic

Before: (audit.log has res=failed)
---

$ dpkg -s util-linux | grep ^Version:
Version: 2.31.1-0.4ubuntu3.5

$ sudo hwclock --set --date "1/1/2000 00:00:00"
$ echo $?
0

$ sudo hwclock --utc --systohc
$ echo $?
0

$ grep hwclock /var/log/audit/audit.log | tail -n2
type=USYS_CONFIG msg=audit(1583956487.134:64): pid=3463 uid=0 auid=1000 ses=5 
msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic addr=? 
terminal=pts/0 res=failed'
type=USYS_CONFIG msg=audit(1583956490.498:70): pid=3465 uid=0 auid=1000 ses=5 
msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic addr=? 
terminal=pts/0 res=failed'

After: (audit.log has res=success)
---

$ sudo add-apt-repository ppa:mfo/lp1865504
$ sudo apt install -y util-linux

$ dpkg -s util-linux | grep ^Version:
Version: 2.31.1-0.4ubuntu3.6

$ sudo hwclock --set --date "1/1/2000 00:00:00"
$ echo $?
0

$ sudo hwclock --utc --systohc
$ echo $?
0

$ grep hwclock /var/log/audit/audit.log | tail -n2
type=USYS_CONFIG msg=audit(1583956532.257:81): pid=3827 uid=0 auid=1000 ses=5 
msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic addr=? 
terminal=pts/0 res=success'
type=USYS_CONFIG msg=audit(1583956535.497:87): pid=3829 uid=0 auid=1000 ses=5 
msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic addr=? 
terminal=pts/0 res=success'

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

Title:
  hwclock reports incorrect status in audit message

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Bionic:
  In Progress
Status in util-linux source package in Eoan:
  In Progress
Status in util-linux package in Debian:
  Unknown

Bug description:
  [Impact]

  hwclock reports incorrect status in audit message:
  - hwclock calls audit_log_user_message(3) to create an audit entry.
  - audit_log_user_message(3) result 1 is "success" and 0 is "failed".
  - hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse status.
  - Thus reports its status incorrectly in audit message.

  It is a requirement for Common Criteria Certification that hwclock
  reports correct status in audit message.

  This has been fixed upstream in https://github.com/karelzak/util-
  linux/commit/189edf1fe501ea39b35911337eab1740888fae7a

  [Test Steps]

  Steps to test:
  1. Install auditd
  2. Run following testcase,

  # hwclock
  2020-03-02 15:03:03.280351+

  # hwclock --set --date "1/1/2000 00:00:00"
  # echo $?
  0
  # hwclock
  2000-01-01 00:00:05.413924+

  # hwclock --utc --systohc
  # echo $?
  0
  # hwclock
  2020-03-02 15:07:00.264331+

  Following audit messages from /var/log/audit/audit.log,

  Note that last field in each audit record produced when hardware clock
  was modified has, "res=failed". Although, testcase shows no* failure
  occurred.

  type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0
  auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
  hostname=bionic-fips addr=? terminal=pts/0 res=failed'

  type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0
  auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
  hostname=bionic-fips addr=? terminal=pts/0 res=failed'

  [Regression Potential]

  Changes limited to the result value passed to audit_log_user_message(3),
  so the audit messages will change the 'res=' field (to correct result.)

  There should not be any regression to fix the status given to auditd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865504/+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 1865504] Re: hwclock reports incorrect status in audit message

[Mauricio Faria de Oliveira]

Joy,

Great work on the debdiff, specially on the DEP3 headers in the patch,
and on the steps to reproduce, which are concise and clear.

I slightly modified the changelog entry to include the d/p/file.patch
path, and clarified its purpose. I also ran 'quilt refresh' to remove
offsets when applying the patch. Attaching the debdiffs for reference.

The version numbers are OK (not used in the archive) / followed rules,
and ensure upgrade path across releases.

The packages for Eoan and Bionic built successfully on all archs with
debug symbols enabled (ppa:mfo/lp1865504).

I have successfully tested the packages on Eoan and Bionic (pasting.)

Having verified that util-linux is not in the upload queue for E/B
nor have any SRU in progress in eoan/bionic-proposed; uploading it.

cheers,
Mauricio

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

Title:
  hwclock reports incorrect status in audit message

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Bionic:
  In Progress
Status in util-linux source package in Eoan:
  In Progress
Status in util-linux package in Debian:
  Unknown

Bug description:
  [Impact]

  hwclock reports incorrect status in audit message:
  - hwclock calls audit_log_user_message(3) to create an audit entry.
  - audit_log_user_message(3) result 1 is "success" and 0 is "failed".
  - hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse status.
  - Thus reports its status incorrectly in audit message.

  It is a requirement for Common Criteria Certification that hwclock
  reports correct status in audit message.

  This has been fixed upstream in https://github.com/karelzak/util-
  linux/commit/189edf1fe501ea39b35911337eab1740888fae7a

  [Test Steps]

  Steps to test:
  1. Install auditd
  2. Run following testcase,

  # hwclock
  2020-03-02 15:03:03.280351+

  # hwclock --set --date "1/1/2000 00:00:00"
  # echo $?
  0
  # hwclock
  2000-01-01 00:00:05.413924+

  # hwclock --utc --systohc
  # echo $?
  0
  # hwclock
  2020-03-02 15:07:00.264331+

  Following audit messages from /var/log/audit/audit.log,

  Note that last field in each audit record produced when hardware clock
  was modified has, "res=failed". Although, testcase shows no* failure
  occurred.

  type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0
  auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
  hostname=bionic-fips addr=? terminal=pts/0 res=failed'

  type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0
  auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
  hostname=bionic-fips addr=? terminal=pts/0 res=failed'

  [Regression Potential]

  Changes limited to the result value passed to audit_log_user_message(3),
  so the audit messages will change the 'res=' field (to correct result.)

  There should not be any regression to fix the status given to auditd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865504/+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 1865504] Re: hwclock reports incorrect status in audit message

[Mauricio Faria de Oliveira]

** Patch added: "lp1865504_bionic_util-linux.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865504/+attachment/5335834/+files/lp1865504_bionic_util-linux.debdiff

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

Title:
  hwclock reports incorrect status in audit message

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Bionic:
  In Progress
Status in util-linux source package in Eoan:
  In Progress
Status in util-linux package in Debian:
  Unknown

Bug description:
  [Impact]

  hwclock reports incorrect status in audit message:
  - hwclock calls audit_log_user_message(3) to create an audit entry.
  - audit_log_user_message(3) result 1 is "success" and 0 is "failed".
  - hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse status.
  - Thus reports its status incorrectly in audit message.

  It is a requirement for Common Criteria Certification that hwclock
  reports correct status in audit message.

  This has been fixed upstream in https://github.com/karelzak/util-
  linux/commit/189edf1fe501ea39b35911337eab1740888fae7a

  [Test Steps]

  Steps to test:
  1. Install auditd
  2. Run following testcase,

  # hwclock
  2020-03-02 15:03:03.280351+

  # hwclock --set --date "1/1/2000 00:00:00"
  # echo $?
  0
  # hwclock
  2000-01-01 00:00:05.413924+

  # hwclock --utc --systohc
  # echo $?
  0
  # hwclock
  2020-03-02 15:07:00.264331+

  Following audit messages from /var/log/audit/audit.log,

  Note that last field in each audit record produced when hardware clock
  was modified has, "res=failed". Although, testcase shows no* failure
  occurred.

  type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0
  auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
  hostname=bionic-fips addr=? terminal=pts/0 res=failed'

  type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0
  auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
  hostname=bionic-fips addr=? terminal=pts/0 res=failed'

  [Regression Potential]

  Changes limited to the result value passed to audit_log_user_message(3),
  so the audit messages will change the 'res=' field (to correct result.)

  There should not be any regression to fix the status given to auditd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865504/+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 1865504] Re: hwclock reports incorrect status in audit message

[Mauricio Faria de Oliveira]

Test/Eoan:
===

$ lsb_release -cs
eoan

$ sudo apt update
$ sudo apt install -y auditd

Before: (audit.log has res=failed)
---

$ dpkg -s util-linux | grep ^Version:
Version: 2.34-0.1ubuntu2.3

$ sudo hwclock --set --date "1/1/2000 00:00:00"
$ echo $?
0

$ sudo hwclock --utc --systohc
$ echo $?
0

$ grep hwclock /var/log/audit/audit.log | tail -n2
type=USYS_CONFIG msg=audit(1583956148.236:82): pid=2380 uid=0 auid=1000 ses=1 
msg='op=change-system-time exe="/usr/sbin/hwclock" hostname=eoan addr=? 
terminal=pts/0 res=failed'
type=USYS_CONFIG msg=audit(1583956151.496:89): pid=2382 uid=0 auid=1000 ses=1 
msg='op=change-system-time exe="/usr/sbin/hwclock" hostname=eoan addr=? 
terminal=pts/0 res=failed'

After: (audit.log has res=success)
---

$ sudo add-apt-repository ppa:mfo/lp1865504
$ sudo apt install -y util-linux

$ dpkg -s util-linux | grep ^Version:
Version: 2.34-0.1ubuntu2.4

$ sudo hwclock --set --date "1/1/2000 00:00:00"
$ echo $?
0

$ sudo hwclock --utc --systohc
$ echo $?
0

$ grep hwclock /var/log/audit/audit.log | tail -n2
type=USYS_CONFIG msg=audit(1583956232.963:108): pid=3432 uid=0 auid=1000 ses=1 
msg='op=change-system-time exe="/usr/sbin/hwclock" hostname=eoan addr=? 
terminal=pts/0 res=success'
type=USYS_CONFIG msg=audit(1583956238.499:115): pid=3434 uid=0 auid=1000 ses=1 
msg='op=change-system-time exe="/usr/sbin/hwclock" hostname=eoan addr=? 
terminal=pts/0 res=success'

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

Title:
  hwclock reports incorrect status in audit message

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Bionic:
  In Progress
Status in util-linux source package in Eoan:
  In Progress
Status in util-linux package in Debian:
  Unknown

Bug description:
  [Impact]

  hwclock reports incorrect status in audit message:
  - hwclock calls audit_log_user_message(3) to create an audit entry.
  - audit_log_user_message(3) result 1 is "success" and 0 is "failed".
  - hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse status.
  - Thus reports its status incorrectly in audit message.

  It is a requirement for Common Criteria Certification that hwclock
  reports correct status in audit message.

  This has been fixed upstream in https://github.com/karelzak/util-
  linux/commit/189edf1fe501ea39b35911337eab1740888fae7a

  [Test Steps]

  Steps to test:
  1. Install auditd
  2. Run following testcase,

  # hwclock
  2020-03-02 15:03:03.280351+

  # hwclock --set --date "1/1/2000 00:00:00"
  # echo $?
  0
  # hwclock
  2000-01-01 00:00:05.413924+

  # hwclock --utc --systohc
  # echo $?
  0
  # hwclock
  2020-03-02 15:07:00.264331+

  Following audit messages from /var/log/audit/audit.log,

  Note that last field in each audit record produced when hardware clock
  was modified has, "res=failed". Although, testcase shows no* failure
  occurred.

  type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0
  auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
  hostname=bionic-fips addr=? terminal=pts/0 res=failed'

  type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0
  auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
  hostname=bionic-fips addr=? terminal=pts/0 res=failed'

  [Regression Potential]

  Changes limited to the result value passed to audit_log_user_message(3),
  so the audit messages will change the 'res=' field (to correct result.)

  There should not be any regression to fix the status given to auditd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865504/+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 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/kmod/+git/kmod/+merge/380578

** Merge proposal linked:
   
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/kmod/+git/kmod/+merge/380579

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in kmod package in Ubuntu:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Disco:
  Won't Fix
Status in kmod source package in Eoan:
  In Progress
Status in kmod source package in Focal:
  In Progress

Bug description:
  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1864992/+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 1865504] Re: hwclock reports incorrect status in audit message

[Mauricio Faria de Oliveira]

** Description changed:

- [IMPACT]
- hwclock reports incrorect status in audit message
+ [Impact]
  
- hwclock calls audit_log_user_message(3) to create an audit entry.
- audit_log_user_message(3) result 1 is "success" and 0 is
- "failed", hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse
- status. Thus reports it's status incorrectly in audit message. 
+ hwclock reports incorrect status in audit message:
+ - hwclock calls audit_log_user_message(3) to create an audit entry.
+ - audit_log_user_message(3) result 1 is "success" and 0 is "failed".
+ - hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse status.
+ - Thus reports its status incorrectly in audit message.
  
  It is a requirement for Common Criteria Certification that hwclock
  reports correct status in audit message.
  
  This has been fixed upstream in https://github.com/karelzak/util-
  linux/commit/189edf1fe501ea39b35911337eab1740888fae7a
  
- [TEST]
+ [Test Steps]
  
  Steps to test:
  1. Install auditd
  2. Run following testcase,
  
  # hwclock
  2020-03-02 15:03:03.280351+
+ 
  # hwclock --set --date "1/1/2000 00:00:00"
  # echo $?
  0
  # hwclock
  2000-01-01 00:00:05.413924+
+ 
  # hwclock --utc --systohc
  # echo $?
  0
  # hwclock
  2020-03-02 15:07:00.264331+
  
  Following audit messages from /var/log/audit/audit.log,
  
- type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0 auid=1000 
ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic-fips 
addr=? terminal=pts/0 res=failed'
- type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0 auid=1000 
ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic-fips 
addr=? terminal=pts/0 res=failed'
+ type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0 auid=1000
+ ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic-
+ fips addr=? terminal=pts/0 res=failed'
+ 
+ type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0 auid=1000
+ ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic-
+ fips addr=? terminal=pts/0 res=failed'
  
  Note that last entry in each audit record produced when hardware clock
- was modified has, "res=failed". Although, testcase shows no failure
+ was modified has, "res=failed". Although, testcase shows no* failure
  occurred.
  
  [Regression Potential]
+ 
+ Changes limited to the result value passed to audit_log_user_message(3),
+ so the audit messages will change the 'res=' field (to correct result.)
+ 
  There should not be any regression to fix the status given to auditd.

** Description changed:

  [Impact]
  
  hwclock reports incorrect status in audit message:
  - hwclock calls audit_log_user_message(3) to create an audit entry.
  - audit_log_user_message(3) result 1 is "success" and 0 is "failed".
  - hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse status.
  - Thus reports its status incorrectly in audit message.
  
  It is a requirement for Common Criteria Certification that hwclock
  reports correct status in audit message.
  
  This has been fixed upstream in https://github.com/karelzak/util-
  linux/commit/189edf1fe501ea39b35911337eab1740888fae7a
  
  [Test Steps]
  
  Steps to test:
  1. Install auditd
  2. Run following testcase,
  
  # hwclock
  2020-03-02 15:03:03.280351+
  
  # hwclock --set --date "1/1/2000 00:00:00"
  # echo $?
  0
  # hwclock
  2000-01-01 00:00:05.413924+
  
  # hwclock --utc --systohc
  # echo $?
  0
  # hwclock
  2020-03-02 15:07:00.264331+
  
  Following audit messages from /var/log/audit/audit.log,
  
+ Note that last field in each audit record produced when hardware clock
+ was modified has, "res=failed". Although, testcase shows no* failure
+ occurred.
+ 
  type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0 auid=1000
  ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic-
  fips addr=? terminal=pts/0 res=failed'
  
  type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0 auid=1000
  ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic-
  fips addr=? terminal=pts/0 res=failed'
  
- Note that last entry in each audit record produced when hardware clock
- was modified has, "res=failed". Although, testcase shows no* failure
- occurred.
- 
  [Regression Potential]
  
  Changes limited to the result value passed to audit_log_user_message(3),
  so the audit messages will change the 'res=' field (to correct result.)
  
  There should not be any regression to fix the status given to auditd.

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

Title:
  hwclock reports incorrect status in audit message

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Bionic:
  In Progress
Status in util-linux source package in Eoan:
  In Progress
Status in util-linux package 

[Touch-packages] [Bug 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Rafael David Tinoco]

@cascardo did a MR for focal and added you as a reviewer. will do the
other MR for eoan and bionic now.

** No longer affects: curtin

** No longer affects: subiquity

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in kmod package in Ubuntu:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Disco:
  Won't Fix
Status in kmod source package in Eoan:
  In Progress
Status in kmod source package in Focal:
  In Progress

Bug description:
  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1864992/+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 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Rafael David Tinoco]

Reason for keeping verbose_missing_bin patch was because of test case
described at:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684901

(k)root@fkmodissue:.../5.4.0-18-generic$ sudo mv modules.alias.bin
modules.alias.bin.old

(k)root@fkmodissue:.../5.4.0-18-generic$ sudo modprobe hehe
modprobe: FATAL: Module hehe not found in directory 
/lib/modules/5.4.0-18-generic

and it doesn't apply any longer with kernels 5.4 in focal.

Testing Bionic for the same test case:

(k)rafaeldtinoco@bkmodissue:.../5.3.0-42-generic$ sudo mv
modules.alias.bin modules.alias.bin.old

(k)rafaeldtinoco@bkmodissue:.../5.3.0-42-generic$ sudo modprobe hehe
modprobe: FATAL: Module hehe not found in directory 
/lib/modules/5.3.0-42-generic

and with 5.0 kernels:

(k)rafaeldtinoco@bkmodissue:.../5.0.0-43-generic$ sudo mv
modules.alias.bin modules.alias.bin.old

(k)rafaeldtinoco@bkmodissue:.../5.0.0-43-generic$ sudo modprobe hehe
modprobe: FATAL: Module hehe not found in directory 
/lib/modules/5.0.0-43-generic

I think its safe to drop it since that Debian bug (from 2012) doesn't
exist today.

Will re-do this test with patch dropped to make sure we solve this issue
and don't cause regression in to that one.

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in kmod package in Ubuntu:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Disco:
  Won't Fix
Status in kmod source package in Eoan:
  In Progress
Status in kmod source package in Focal:
  In Progress

Bug description:
  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-14-generic x86_6

[Touch-packages] [Bug 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/kmod/+git/kmod/+merge/380577

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in kmod package in Ubuntu:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Disco:
  Won't Fix
Status in kmod source package in Eoan:
  In Progress
Status in kmod source package in Focal:
  In Progress

Bug description:
  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1864992/+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 1867029] Re: Package ifupdown breaks network configuration by cloud-init

[Ryan Harper]

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

** Tags added: uec-images

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

Title:
  Package ifupdown breaks network configuration by cloud-init

Status in cloud-init:
  Confirmed
Status in ifupdown package in Ubuntu:
  New

Bug description:
  It appears the `ifupdown` package breaks networking configuration that
  cloud-init would normally handle (?) on both providers. The result, if
  you image an instance with the `ifupdown` package installed, is that
  the image is not bootable by Azure/AWS. I'm not familiar with how
  Azure/AWS/etc use cloud-init for network start up however. I'm filing
  here for now, in case `cloud-init` needs to be more defensive against
  `ifupdown`.

  To reproduce with Packer (I confirmed this method):

  * Add necessary Azure subscription env vars from `ifupdown-bug.json`
  * `packer build ifupdown-bug.json`
  * Try to boot an instance with resulting image
  * Instance will never boot -- more specifically, networking never comes up. 
See `boot.log` for an example boot

  To reproduce manually (only a guess, I did not confirm):

  * Boot 18.04 ubuntu instance
  * Install ifupdown
  * Image the instance
  * Try to boot instance using new image
  * Instance won't boot

  I hit this with Packer, creating new images for booting instances in
  scaling groups -- `ifupdown` is brought in by `salt`. If this is
  reproducible via manual installation, there could be some backup
  images/snapshots that are unable to boot though.

  This appears to be because cloud-init network start up operations are
  broken by whatever `ifupdown` sysv/systemd scripts perform on boot.
  With `ifupdown` installed on Azure, `eth0` does not get an IP address,
  the instance never fully boots according to Azure, and it will enter
  an error state. On AWS, the instance boots, but network operations
  like SSH fail.

  The `boot.log` is from Azure. Eventually `cloud-init` gives an
  exception (see `exception.log`), but this seems like a secondary issue
  related to networking being down.

  I did try to upgrade cloud-init using nightly PPAs (version 20.1 I
  believe), but no luck. This is on Ubuntu 18.04 instances from Azure
  marketplace and AWS Canonical AMI, cloud-init version
  `19.4-33-gbb4131a2-0ubuntu1~18.04.1`.

  Related: https://github.com/Azure/WALinuxAgent/issues/1612

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1867029/+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 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Rafael David Tinoco]

** Also affects: kmod (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: kmod (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: kmod (Ubuntu Focal)
   Importance: Medium
 Assignee: Rafael David Tinoco (rafaeldtinoco)
   Status: In Progress

** Also affects: kmod (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Changed in: kmod (Ubuntu Disco)
   Status: New => Won't Fix

** Changed in: kmod (Ubuntu Focal)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: kmod (Ubuntu Eoan)
   Status: New => In Progress

** Changed in: kmod (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: kmod (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: kmod (Ubuntu Eoan)
   Importance: Undecided => Medium

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in curtin:
  Invalid
Status in subiquity:
  Invalid
Status in kmod package in Ubuntu:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Disco:
  Won't Fix
Status in kmod source package in Eoan:
  In Progress
Status in kmod source package in Focal:
  In Progress

Bug description:
  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bv

[Touch-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd

[Bill Miller]

Still stuck on version 7.5 3 months later.

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

Title:
  pulseaudio now depends on libsnapd-glib1 which recommends snapd

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has
  libsnapd-glib1 as a dependency.

  This is complete and utter nonsense. I do not want cascading
  dependencies that have no business being installed on the systems I
  manage.

  Please rectify this at once.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+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 1863261] Re: modinfo prints an error message if modules.builtin.bin is missing

[Rafael David Tinoco]

** Also affects: initramfs-tools (Ubuntu Focal)
   Importance: Medium
 Assignee: Rafael David Tinoco (rafaeldtinoco)
   Status: Fix Released

** Changed in: initramfs-tools (Ubuntu Eoan)
   Status: New => In Progress

** Changed in: initramfs-tools (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: initramfs-tools (Ubuntu Focal)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: initramfs-tools (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: initramfs-tools (Ubuntu Eoan)
   Importance: Undecided => Medium

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

Title:
  modinfo prints an error message if modules.builtin.bin is missing

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  In Progress
Status in initramfs-tools source package in Disco:
  Won't Fix
Status in initramfs-tools source package in Eoan:
  In Progress
Status in initramfs-tools source package in Focal:
  Fix Released

Bug description:
  Running a simple "update-initramfs -u" in a system with kmod version
  26+20191223-1ubuntu1 (from focal-proposed)

  will result into a bunch of:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/var/tmp/mkinitramfs_FLkEYb/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  errors. That happens because:

  modinfo prints an error message if modules.builtin.bin is missing and
  it was fixed upstream (Debian) in:

  commit 835d584
  Author: Ben Hutchings 
  Date:   Sat Jan 18 15:44:32 2020

  mkinitramfs: Copy modules.builtin.bin into initramfs

  modinfo now prints an error message if modules.builtin.bin (created
  by depmod) is missing.  Copy it in early if it's present.

  Closes: #948257
  Signed-off-by: Ben Hutchings 

  and reported in bug:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948257

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261/+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 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Rafael David Tinoco]

Sorry @cascardo, forgot to update there. I'll revert half of Debian
patch... (the could not open builtin file).. turning it back to DBG()
only message. This "fixes" the issue. We can solve implement whatever
Debian decides later.. but getting rid of those messages now is good or
we will have many bugs popping up. Let me suggest a small MR for this.

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in curtin:
  Invalid
Status in subiquity:
  Invalid
Status in kmod package in Ubuntu:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Disco:
  Won't Fix
Status in kmod source package in Eoan:
  In Progress
Status in kmod source package in Focal:
  In Progress

Bug description:
  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1864992/+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 1525628] Re: tracker needs to be killed on every boot

[Felix Köhler]

Just to confirm: this is still very relevant in 2020 :-(

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

Title:
  tracker needs to be killed on every boot

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  At every boot, tacker-miner-fs and tracker-extract uses all of the
  processor and needs to be killed manually for computer to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: tracker 1.6.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Dec 13 13:02:58 2015
  InstallationDate: Installed on 2015-04-24 (232 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: tracker
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1525628/+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 1862797] Re: Systemd does not allow hibernation when Chrome/chromium is running

[Dan Streetman]

can you please update the bug description to accurately describe how to
reproduce the bug; then you should check your logs to see why the first
hibernate attempt fails.

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

Title:
  Systemd does not allow hibernation when Chrome/chromium is running

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  1/ Linux Mint 19.3/Ubuntu Bionic 18.04 LTS
  2/ systemd: Installed: 237-3ubuntu10.38
  3/ & 4/ Problem: hibernation stops working as soon as you start Chromium

  Steps to reproduce

  $ busctl call org.freedesktop.login1 /org/freedesktop/login1 
org.freedesktop.login1.Manager CanSuspend
  s "yes"
  $ busctl call org.freedesktop.login1 /org/freedesktop/login1 
org.freedesktop.login1.Manager CanHibernate
  s "yes"

  start chromium
  $ busctl call org.freedesktop.login1 /org/freedesktop/login1 
org.freedesktop.login1.Manager CanHibernate
  s "na"

  $ sudo systemctl hibernate
  Failed to hibernate system via logind: Sleep verb not supported

  When this happens Cinnamon/Gnome no longer show hibernate buttons of
  course.

  $ systemd-inhibit --list 
   Who: ecotech (UID 1000/ecotech, PID 1607/csd-media-keys)
  What: handle-power-key:handle-suspend-key:handle-hibernate-key
   Why: Cinnamon handling keypresses
  Mode: block

   Who: ModemManager (UID 0/root, PID 996/ModemManager)
  What: sleep
   Why: ModemManager needs to reset devices
  Mode: delay

   Who: ecotech (UID 1000/ecotech, PID 1656/csd-power)
  What: sleep
   Why: Cinnamon needs to lock the screen
  Mode: delay

   Who: ecotech (UID 1000/ecotech, PID 1656/csd-power)
  What: handle-lid-switch
   Why: Multiple displays attached
  Mode: block

   Who: NetworkManager (UID 0/root, PID 1012/NetworkManager)
  What: sleep
   Why: NetworkManager needs to turn off networks
  Mode: delay

   Who: UPower (UID 0/root, PID 1279/upowerd)
  What: sleep
   Why: Pause device polling
  Mode: delay

  Systemd-inhibit does not mention anything Chrome/Chromium related
  Stop Chromium and hibernation works again.

  Similar issues found:
  https://bugzilla.redhat.com/show_bug.cgi?id=1346908

  $ cat /sys/power/state
  freeze mem disk

  $ cat /sys/power/disk
  [platform] shutdown reboot suspend test_resume 

  Tried logind.conf default (all commented out) and below. No difference.
  $ cat /etc/systemd/logind.conf
  [Login]
  #NAutoVTs=6
  #ReserveVT=6
  #KillUserProcesses=no
  #KillOnlyUsers=
  #KillExcludeUsers=root
  #InhibitDelayMaxSec=5
  HandlePowerKey=poweroff
  HandleSuspendKey=suspend
  HandleHibernateKey=hibernate
  #HandleLidSwitch=suspend
  #HandleLidSwitchDocked=ignore
  PowerKeyIgnoreInhibited=no
  #SuspendKeyIgnoreInhibited=no
  HibernateKeyIgnoreInhibited=no
  #LidSwitchIgnoreInhibited=yes
  #HoldoffTimeoutSec=30s
  #IdleAction=ignore
  #IdleActionSec=30min
  #RuntimeDirectorySize=10%
  #RemoveIPC=yes
  #InhibitorsMax=8192
  #SessionsMax=8192
  #UserTasksMax=33%

  
  Can also not file a bug @ https://github.com/systemd/system since my version 
is more than 2 versions older than the last version (2.44.1).

  Thanks in advance

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1862797/+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 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Thadeu Lima de Souza Cascardo]

https://lore.kernel.org/lkml/20200311170120.12641-1-j...@kernel.org/T/#u

This patch just caught my attention. I didn't do any investigation, but
as I recall seeing something about namespaces, maybe this is related.

Cascardo.

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in curtin:
  Invalid
Status in subiquity:
  Invalid
Status in kmod package in Ubuntu:
  In Progress

Bug description:
  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1864992/+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 1866625] Re: OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit Integers.

[Christoph Reiter]

"int" maps to the same underlying type in Python 2 and Python 3. This
wasn't changed when pygobject was ported to Python 3 and can't really be
changed now. If you want be sure your numbers fit use the suggested
"GObject.TYPE_*", or just use "object" which means the Python int object
is stored as is, assuming you don't need to access it in C code
somewhere else.

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

Title:
  OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit
  Integers.

Status in pygobject package in Ubuntu:
  New

Bug description:
  import gi
  gi.require_version('Gtk', '3.0')
  from gi.repository import Gtk

  This works in Python 2:

  mystore = Gtk.ListStore(long)
  mystore.insert_with_valuesv(-1, [1], [long(1330400507426)])

  This does not work in Python 3:

  mystore = Gtk.ListStore(int)
  mystore.insert_with_valuesv(-1, [1], [int(1330400507426)])

  OverflowError: Item 0: out of range for int property

  

  lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  apt-cache policy python3-gi
  python3-gi:
Installed: 3.26.1-2ubuntu1
Candidate: 3.26.1-2ubuntu1
Version table:
   *** 3.26.1-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.26.1-2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  python3 -V
  Python 3.6.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1866625/+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 1862264] Re: Browsing smb share is painfully slow when mounted via "gio" (compared with "mount")

[Pablo Copissa]

Reported upstream as issue 2062
(https://gitlab.gnome.org/GNOME/glib/issues/2062)

** Bug watch added: gitlab.gnome.org/GNOME/glib/issues #2062
   https://gitlab.gnome.org/GNOME/glib/issues/2062

** Description changed:

+ Reported upstream as issue 2062
+ (https://gitlab.gnome.org/GNOME/glib/issues/2062)
+ 
  Ubuntu 18.04 LTS here, fully updated (as of late Jan 2020).
  TEST #1:
  To establish a baseline/expected behavior, we first mount an SMB share via 
mount.cifs and time an ls command:
  $ sudo mount -t cifs -o username=pablo //myserver.example.com/share 
~/mnt/share
  $ cd ~/mnt/share/some/dir
  $ time ls
  ... approx 320 files ...
  real  0m1,080s
  user  0m0,008s
  sys   0m0,005s
  $ sudo umount ~/mnt/share
  
  TEST #2
  Now we do the same via gio mount:
  $ gio mount smb://myserver.example.com/share
  cd 
/run/user/1000/gvfs/smb-share\:server\=myserver.example.com\,share\=share/some/dir
  $ time ls
  ... same 320 files ...
  real  0m28,999s
  user  0m0,013s
  sys   0m0,032s
  
  Enumeration of files is about 29 times slower when mounted via gio mount
  than via mount -t cifs.
  
  TEST #3
  Now for the real weird: while using the gio-mounted folder, we now time ls IN 
COMBINATION WITH SOMETHING ELSE (can be strace ls, ls|wc etc...):
  $ time ls | wc
     321 3239804
  
  real  0m0,546s
  user  0m0,006s
  sys   0m0,004s
  
  Note that this is almost TWICE AS FAST than the "fast" mount of test #1
  and about 53 times faster than "slow" test #2 !
  
  The expectation is that Tests 1 and 2 should have similar timings, not
  differing by a factor of 30 or so. More disturbing, there is no good
  reason why tests 2 and 3 differ by an even bigger factor of 53: They use
  the same underlying infrastructure which test 3 proves is adequately
  fast. And yet, we get this slow down in test 2.
  
  As a final note, these benchmarks are a distilled version of the original 
real-life motivating scenario where a Java-based program would simply take tens 
of minutes to display the same list of 320 files when mounted via gio mount and 
a second or so when mounted via mount -t cifs.
  The same timing difference is of course visible in any file manager.
  
  Hope this helps
  
  PS: several old/ancient bug reports exist for a similar issue and I
  deliberately copied the title from one of them (#259771)
  
  PS2: may or may not be relevant: The remote server is a VM running
  Windows 7 (yes, I know...) and the connection was made via VPN (Ubuntu
  stock SSTP).
  
  PS3: Another data point (server is now a Synolgy NAS, not a Win7 VM)
  
  $ gio mount smb://nas.example.com/share2
  
  $ cd /run/user/1000/gvfs/smb-
  share\:server\=nas.example.com\,share\=share2/another/path
  
  $ time ls
  
  ... 528 subdirs approximately ...
  
  real  0m45,075s
  user  0m0,013s
  sys   0m0,058s
  
  $ time ls | wc
- 5281631   10893
+ 5281631   10893
  
  real  0m0,911s
  user  0m0,003s
  sys   0m0,005s
  
  Factor is about 50.

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

Title:
  Browsing smb share is painfully slow when mounted via "gio" (compared
  with "mount")

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Reported upstream as issue 2062
  (https://gitlab.gnome.org/GNOME/glib/issues/2062)

  Ubuntu 18.04 LTS here, fully updated (as of late Jan 2020).
  TEST #1:
  To establish a baseline/expected behavior, we first mount an SMB share via 
mount.cifs and time an ls command:
  $ sudo mount -t cifs -o username=pablo //myserver.example.com/share 
~/mnt/share
  $ cd ~/mnt/share/some/dir
  $ time ls
  ... approx 320 files ...
  real  0m1,080s
  user  0m0,008s
  sys   0m0,005s
  $ sudo umount ~/mnt/share

  TEST #2
  Now we do the same via gio mount:
  $ gio mount smb://myserver.example.com/share
  cd 
/run/user/1000/gvfs/smb-share\:server\=myserver.example.com\,share\=share/some/dir
  $ time ls
  ... same 320 files ...
  real  0m28,999s
  user  0m0,013s
  sys   0m0,032s

  Enumeration of files is about 29 times slower when mounted via gio
  mount than via mount -t cifs.

  TEST #3
  Now for the real weird: while using the gio-mounted folder, we now time ls IN 
COMBINATION WITH SOMETHING ELSE (can be strace ls, ls|wc etc...):
  $ time ls | wc
     321 3239804

  real  0m0,546s
  user  0m0,006s
  sys   0m0,004s

  Note that this is almost TWICE AS FAST than the "fast" mount of test
  #1 and about 53 times faster than "slow" test #2 !

  The expectation is that Tests 1 and 2 should have similar timings, not
  differing by a factor of 30 or so. More disturbing, there is no good
  reason why tests 2 and 3 differ by an even bigger factor of 53: They
  use the same underlying infrastructure which test 3 proves is
  adequately fast. And yet, we get this slow down in test 2.

  As a final note, these benchmarks are a distilled version of the original 
real-life m

[Touch-packages] [Bug 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Rafael David Tinoco]

@cascardo brought to us that there is on-going discussion about this in:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948257#95

which I missed...

Debian has this patch:

+ debian/patches/verbose_missing_bin

Description: Report an error when some .bin files do not exist
Author: Marco d'Itri 
Bug-Debian: http://bugs.debian.org/684901
---

--- a/libkmod/libkmod.c
+++ b/libkmod/libkmod.c
@@ -503,7 +503,7 @@ static char *lookup_builtin_file(struct

idx = index_file_open(fn);
if (idx == NULL) {
-   DBG(ctx, "could not open builtin file '%s'\n", fn);
+   ERR(ctx, "could not open builtin file '%s'\n", fn);
return NULL;
}

@@ -575,7 +575,7 @@ char *kmod_search_moddep(struct kmod_ctx

idx = index_file_open(fn);
if (idx == NULL) {
-   DBG(ctx, "could not open moddep file '%s'\n", fn);
+   ERR(ctx, "could not open moddep file '%s'\n", fn);
return NULL;
}
   
Changing DBG to ERR... that changes the involved print logic.

I'm still playing with this as I want to check what is changing
verbosity when execution path comes from depmod.

** Bug watch added: Debian Bug tracker #684901
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684901

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in curtin:
  Invalid
Status in subiquity:
  Invalid
Status in kmod package in Ubuntu:
  In Progress

Bug description:
  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade l

[Touch-packages] [Bug 1867001] Re: ibus-x11 crashed with SIGSEGV in __GI___poll()

[Gunnar Hjalmarsson]

Thanks for your report!

Can you please clarify which steps preceded the crash?

I see that the current desktop is "GNOME-Greeter:GNOME", while standard
Ubuntu is "ubuntu:GNOME". Which desktop environment are you using?

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

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

Title:
  ibus-x11 crashed with SIGSEGV in __GI___poll()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  the Ubuntu presents an error

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-1~exp1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Mar 11 08:51:28 2020
  ExecutablePath: /usr/lib/ibus/ibus-x11
  InstallationDate: Installed on 2020-03-07 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
  ProcCmdline: /usr/lib/ibus/ibus-x11 --kill-daemon
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7fab42711b86 <__run_exit_handlers+198>:  mov
0x10(%rax),%rdx
   PC (0x7fab42711b86) ok
   source "0x10(%rax)" (0xb1ac969e3c4a0) not located in a known VMA region 
(needed readable region)!
   destination "%rdx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   __GI___poll (fds=0x7fff598bf188, nfds=1, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
   ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
   ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
   xcb_wait_for_reply64 () from /lib/x86_64-linux-gnu/libxcb.so.1
   _XReply () from /lib/x86_64-linux-gnu/libX11.so.6
  Title: ibus-x11 crashed with SIGSEGV in __GI___poll()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1867001/+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 1866012] Re: depmod ERROR during Setting up linux-modules-5.4.0-17-generic

[Rafael David Tinoco]

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

https://bugs.launchpad.net/curtin/+bug/1864992/comments/34
https://bugs.launchpad.net/curtin/+bug/1864992/comments/35
https://bugs.launchpad.net/curtin/+bug/1864992/comments/36

Issue is in verbosity level of kmod.

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

Title:
  depmod ERROR during Setting up linux-modules-5.4.0-17-generic

Status in kmod package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Deploy Focal on a KVM ndoe, enable proposed
  2. Run sudo apt dist-upgrade

  The console will be flushed with:
  Setting up libisc1105:amd64 (1:9.11.16+dfsg-3~build1) ...
  Setting up linux-modules-5.4.0-17-generic (5.4.0-17.21) ...
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  
  Setting up apt-utils (1.9.12) ...
  Setting up libselinux1-dev:amd64 (3.0-1build2) ...
  Setting up libglib2.0-0:amd64 (2.64.0-1) ...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: User Name 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  4 08:29 seq
   crw-rw 1 root audio 116, 33 Mar  4 08:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar  4 09:06:42 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=36e162f3-41b5-4487-a6dc-09ba4e37d3bf ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux-5.4
  StagingDrivers: exfat
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1866012/+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 1866012] Re: depmod ERROR during Setting up linux-modules-5.4.0-17-generic

[Rafael David Tinoco]

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

Im marking this bug as a duplicate of:

https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1864992

** This bug has been marked a duplicate of bug 1864992
   depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

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

Title:
  depmod ERROR during Setting up linux-modules-5.4.0-17-generic

Status in kmod package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Deploy Focal on a KVM ndoe, enable proposed
  2. Run sudo apt dist-upgrade

  The console will be flushed with:
  Setting up libisc1105:amd64 (1:9.11.16+dfsg-3~build1) ...
  Setting up linux-modules-5.4.0-17-generic (5.4.0-17.21) ...
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  
  Setting up apt-utils (1.9.12) ...
  Setting up libselinux1-dev:amd64 (3.0-1build2) ...
  Setting up libglib2.0-0:amd64 (2.64.0-1) ...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: User Name 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  4 08:29 seq
   crw-rw 1 root audio 116, 33 Mar  4 08:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar  4 09:06:42 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=36e162f3-41b5-4487-a6dc-09ba4e37d3bf ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux-5.4
  StagingDrivers: exfat
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1866012/+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 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Rafael David Tinoco]

Here is the thing...

log_setup_kmod_log() is the function controlling verbocity level. When
called from do_modprobe() execution path, it has a way to control the
"log priority", being able to control how verbose the execution should
be. Meanwhile, when log_setup_kmod_log() is called from do_depmod().. it
has no way to control how verbose the rest of execution will be.

#define DEFAULT_VERBOSE LOG_WARNING
static int verbose = DEFAULT_VERBOSE;

and then:

depmod():
...
case 'v':
  verbose++;
  break;
...
  log_setup_kmod_log(ctx, verbose);
...

since we have:

#define LOG_EMERG   0   /* system is unusable */
#define LOG_ALERT   1   /* action must be taken immediately */
#define LOG_CRIT2   /* critical conditions */
#define LOG_ERR 3   /* error conditions */
#define LOG_WARNING 4   /* warning conditions */
#define LOG_NOTICE  5   /* normal but significant condition */
#define LOG_INFO6   /* informational */
#define LOG_DEBUG   7   /* debug-level messages *

Something is bumping the verbose from "warning" into "debug"
automatically.

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in curtin:
  Invalid
Status in subiquity:
  Invalid
Status in kmod package in Ubuntu:
  In Progress

Bug description:
  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: Q

[Touch-packages] [Bug 1867001] Re: ibus-x11 crashed with SIGSEGV in __GI___poll()

[Gunnar Hjalmarsson]

** Information type changed from Private to Public

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

Title:
  ibus-x11 crashed with SIGSEGV in __GI___poll()

Status in ibus package in Ubuntu:
  New

Bug description:
  the Ubuntu presents an error

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-1~exp1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Mar 11 08:51:28 2020
  ExecutablePath: /usr/lib/ibus/ibus-x11
  InstallationDate: Installed on 2020-03-07 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
  ProcCmdline: /usr/lib/ibus/ibus-x11 --kill-daemon
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7fab42711b86 <__run_exit_handlers+198>:  mov
0x10(%rax),%rdx
   PC (0x7fab42711b86) ok
   source "0x10(%rax)" (0xb1ac969e3c4a0) not located in a known VMA region 
(needed readable region)!
   destination "%rdx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   __GI___poll (fds=0x7fff598bf188, nfds=1, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
   ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
   ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
   xcb_wait_for_reply64 () from /lib/x86_64-linux-gnu/libxcb.so.1
   _XReply () from /lib/x86_64-linux-gnu/libX11.so.6
  Title: ibus-x11 crashed with SIGSEGV in __GI___poll()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1867001/+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 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink

[Launchpad Bug Tracker]

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

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

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

Title:
  gdb doesn't search in debug-file-directory for .gnu_debugaltlink

Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  As far as I can tell gdb version 8.2.90 isn't searching the debug-
  file-directory, which I set, for the '.gnu_debugaltlink' which is in
  the debug symbols. Here's the error I'm seeing:

  Type "apropos word" to search for commands related to "word".
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
  could not find '.gnu_debugaltlink' file for 
/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
  (No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)

  Here's part of an strace of what's going on behind the scenes:

  lstat("/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
 {st_mode=S_IFREG|0644, st_size=839744, ...}) = 0 
  openat(AT_FDCWD, 
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

  This is the only time "/usr/lib/debug" is searched, generally
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox/usr/lib/debug/" is used. I'll attach the full strace though.

  For completeness here's the gdb command I'm using:

  Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
  /report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
  --ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
  prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
  --ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
  -linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
  dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox//usr/bin/gnome-calculator"' --ex 'core-file
  /tmp/apport_core_1b6dn6np'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1818918/+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 1850820] Re: idhclient

[Marc Deslauriers]

** Information type changed from Private Security to Public Security

** Changed in: isc-dhcp (Ubuntu Focal)
   Status: New => In Progress

** Changed in: isc-dhcp (Ubuntu Focal)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

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

Title:
  idhclient

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Eoan:
  New
Status in isc-dhcp source package in Focal:
  In Progress

Bug description:
  In eon dhclient is running without confinement

  $ ps aux -Z | grep dhclient
  unconfined  root  1004  0.0  0.1   9604  5796 ?  
  Ss   16:48   0:00 dhclient

  This is because the profile is defined with

  /sbin/dhclient flags=(attach_disconnected) {

  but the binary is now at

  /usr/sbin/dhclient

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1850820/+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 1854120] Re: Screen contents visible briefly on lock screen on resolution change

[Marc Deslauriers]

** Changed in: lightdm (Ubuntu)
   Status: New => Triaged

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

Title:
  Screen contents visible briefly on lock screen on resolution change

Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  I am using a remote application to AnyDesk to remote access my Ubuntu
  16.04 LTS 64 bit. On the application we can resize the screen and have
  the resolution of the target computer scale up and down when this is
  done.

  When the computer is locked on the login screen if the screen is
  resized ( resolution changes ) - For a brief fraction of a second the
  unlocked screen flashes and the login screen shows up again. I think
  this is a security breach to be able to peek into the inside contents
  even though the computer is locked.

  Please feel free to close this issue if this is an already known issue
  or if its already fixed in later releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1854120/+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 1856494] Re: system program problem detected

[Marc Deslauriers]

** Information type changed from Private Security to Public

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

Title:
  system program problem detected

Status in apport package in Ubuntu:
  New

Bug description:
  "System program problem detected" "Do you want to report the problem
  now?" When I select yes it prompts for a password and pops back up. Is
  there a resolution that is obvious that I am overlooking?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1856494/+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 1865504] Re: hwclock reports incorrect status in audit message

[Mauricio Faria de Oliveira]

Working on the stable releases E/B as discussed w/ Marc on IRC.

** Changed in: util-linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: util-linux (Ubuntu Bionic)
 Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)

** Changed in: util-linux (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: util-linux (Ubuntu Eoan)
   Status: New => In Progress

** Changed in: util-linux (Ubuntu Eoan)
 Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)

** Changed in: util-linux (Ubuntu Eoan)
   Importance: Undecided => Medium

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

Title:
  hwclock reports incorrect status in audit message

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Bionic:
  In Progress
Status in util-linux source package in Eoan:
  In Progress
Status in util-linux package in Debian:
  Unknown

Bug description:
  [IMPACT]
  hwclock reports incrorect status in audit message

  hwclock calls audit_log_user_message(3) to create an audit entry.
  audit_log_user_message(3) result 1 is "success" and 0 is
  "failed", hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse
  status. Thus reports it's status incorrectly in audit message. 

  It is a requirement for Common Criteria Certification that hwclock
  reports correct status in audit message.

  This has been fixed upstream in https://github.com/karelzak/util-
  linux/commit/189edf1fe501ea39b35911337eab1740888fae7a

  [TEST]

  Steps to test:
  1. Install auditd
  2. Run following testcase,

  # hwclock
  2020-03-02 15:03:03.280351+
  # hwclock --set --date "1/1/2000 00:00:00"
  # echo $?
  0
  # hwclock
  2000-01-01 00:00:05.413924+
  # hwclock --utc --systohc
  # echo $?
  0
  # hwclock
  2020-03-02 15:07:00.264331+

  Following audit messages from /var/log/audit/audit.log,

  type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0 auid=1000 
ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic-fips 
addr=? terminal=pts/0 res=failed'
  type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0 auid=1000 
ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic-fips 
addr=? terminal=pts/0 res=failed'

  Note that last entry in each audit record produced when hardware clock
  was modified has, "res=failed". Although, testcase shows no failure
  occurred.

  [Regression Potential]
  There should not be any regression to fix the status given to auditd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865504/+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 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Rafael David Tinoco]

Kmod source shows:

idx = index_file_open(fn);
if (idx == NULL) {
DBG(ctx, "could not open builtin file '%s'\n", fn);
return NULL;
}

and this is continuously called.

I'll check if DBG should be enabled in our case OR we should patch
upstream.

** Changed in: subiquity
   Status: New => Invalid

** Changed in: kmod (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in curtin:
  Invalid
Status in subiquity:
  Invalid
Status in kmod package in Ubuntu:
  In Progress

Bug description:
  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1864992/+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 1865474] Re: sysytemd-resolved automatically use an ipv6 dns server on lan

[Marc Deslauriers]

** Information type changed from Private Security to Public

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

Title:
  sysytemd-resolved automatically use an ipv6 dns server on lan

Status in systemd package in Ubuntu:
  New

Bug description:
  lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  i installed focal from the netboot version mini.iso.

  i encountered some problem on dsn configuration and i found that
  systemd-resolved was using an ipv6 dns address

  this is my netplan configuration:

  network:
    version: 2
    renderer: networkd
    ethernets:
  ens3:
    addresses:
  - 192.168.1.1/24
    gateway4: 192.168.1.212
    nameservers:
    search: [xxx.com]
    addresses: [192.168.1.191, 192.168.1.206]

  this is the output of "systemd-resolved --status"

  Global
     LLMNR setting: no
  MulticastDNS setting: no
    DNSOverTLS setting: no
    DNSSEC setting: no
  DNSSEC supported: no
    DNSSEC NTA: 10.in-addr.arpa
    16.172.in-addr.arpa
    168.192.in-addr.arpa
    17.172.in-addr.arpa
    18.172.in-addr.arpa
    19.172.in-addr.arpa
    20.172.in-addr.arpa
    21.172.in-addr.arpa
    22.172.in-addr.arpa
    23.172.in-addr.arpa
    24.172.in-addr.arpa
    25.172.in-addr.arpa
    26.172.in-addr.arpa
    27.172.in-addr.arpa
    28.172.in-addr.arpa
    29.172.in-addr.arpa
    30.172.in-addr.arpa
    31.172.in-addr.arpa
    corp
    d.f.ip6.arpa
    home
    internal
    intranet
    lan
    local
    private
    test

  Link 2 (ens3)
    Current Scopes: DNS
  DefaultRoute setting: yes
     LLMNR setting: yes
  MulticastDNS setting: no
    DNSOverTLS setting: no
    DNSSEC setting: no
  DNSSEC supported: no
    Current DNS Server: fe80::6670:2ff:feb5:d9c8
   DNS Servers: 192.168.1.191
    192.168.1.206
    fe80::6670:2ff:feb5:d9c8
    DNS Domain: xxx.com

  --
  as you can see systemd is using the ipv6 dns server.

  i found that such ip was the address of my openwrt wifi router. dnsmasq is 
disabled for ipv4 lan interface on the router and i never configured an ipv6 
network. Anyway i disabled all the ipv6 dnsmasq feature on the router and after 
a restart this fixed the problem.
  But i think that this is a bug.
  In my netplan i never configured an ipv6 dns nor a ipv6 network; furthermore 
none of my other ubuntu bionic servers showed such a behaviour.
  Also another focal netboot installation i made three weeks ago didn't show 
this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1865474/+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 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Rafael David Tinoco]

Alright, afaict what is happening is this:

In Focal I first faced this issue when upgrading kmod to
26+20191223-1ubuntu1.. but my reproducer was "update-initramfs" only.
The issue is that both: mkinitramfs (initramfs-tools) needs a patch to
work with recent 5.x kernels:

# mkinitramfs (initramfs-tools)

# Copy in modules.builtin and modules.order (not generated by depmod)
# and modules.builtin.bin (generated by depmod, but too late to avoid
# error messages as in #948257)
for x in modules.builtin modules.builtin.bin modules.order; do
if [ -f "${MODULESDIR}/${x}" ]; then
cp -p "${MODULESDIR}/${x}" "${DESTDIR}${MODULESDIR}/${x}"
fi
done

All other Ubuntu versions that might use a HWE kernel will need a SRU of
that patch.

But thats not the only way to trigger the issue as it seems...

I was able to reproduce the issue when doing:

(k)rafaeldtinoco@kmodissuefocal:~$ apt-get install linux-
image-5.4.0-14-generic linux-headers-5.4.0-14-generic linux-modules-
extra-5.4.0-14-generic

while I had kernel 5.4.0-18-generic installed.

Setting up linux-modules-5.4.0-14-generic (5.4.0-14.17) ...
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' 

The same happened when installing linux-modules-5.4.0-9-generic AND when
uninstalling and re-installing 5.4.0-18-generic. So now I'll reproduce
this second issue.. and I'm marking LP: #1863261 that SRU is needed for
that case.

For this case.. it turns out that postinst script for linux-modules is
executing:

$ sudo depmod -a -F /boot/System.map-5.4.0-18-generic 5.4.0-18-generic

for the first time when
/lib/modules/5.4.0-18-generic/modules.builtin.bin DOES NOT exist yet.

an easy way to reproduce is this:

$ sudo rm /lib/modules/5.4.0-18-generic/modules.builtin.bin

and then:

$ sudo depmod -a -F /boot/System.map-5.4.0-18-generic 5.4.0-18-generic  
   
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-18-generic/modules.builtin.bin'
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-18-generic/modules.builtin.bin'
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-18-generic/modules.builtin.bin'
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-18-generic/modules.builtin.bin'

the second time you run same command, it will not have these errors
messages because "modules.builtin.bin" file will already have been
created.

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in curtin:
  Invalid
Status in subiquity:
  New
Status in kmod package in Ubuntu:
  Confirmed

Bug description:
  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/c

[Touch-packages] [Bug 1864982] Re: Ubuntu desktop computer doesn't seem to lock correctly

[Marc Deslauriers]

What desktop environment are you using?

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

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

Title:
  Ubuntu desktop computer doesn't seem to lock correctly

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu desktop computer doesn't seem to lock correctly if I click "Lock 
Screen" it does lock if I use shortcut. If I use the "lock screen" button then 
anyone can unlock it by merely pressing "ctrl+alt+f7".
  The problem is not that I cannot lock my screen, the problem is I was under 
the impression that my computer was being locked when it was not.
  now that I know that the "Lock Screen" button doesn't work correctly I know 
of other ways to lock my computer still the lock screen button should work and 
it looks like it locked my screen,but if I press "ctrl+alt+f7" then it 
magically unlocks

  So it is a security incident.

  Thanks in Advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1864982/+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 1865831] Re: bug

[Marc Deslauriers]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  bug

Status in xorg package in Ubuntu:
  New

Bug description:
  bugbugbugb

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  3 11:05:07 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:062e]
  InstallationDate: Installed on 2020-02-26 (5 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 8087:8001 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E7450
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=bf009119-6b69-4fe9-a305-709e07c8e9fe ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D8H72
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/01/2015:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0D8H72:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.product.sku: 062E
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/1865831/+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 1863261] Re: modinfo prints an error message if modules.builtin.bin is missing

[Rafael David Tinoco]

Disco is EOL. All other supported versions need same patch for HWE
kernels.

** Also affects: initramfs-tools (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: initramfs-tools (Ubuntu Disco)
   Status: New => Won't Fix

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

Title:
  modinfo prints an error message if modules.builtin.bin is missing

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  New
Status in initramfs-tools source package in Disco:
  Won't Fix
Status in initramfs-tools source package in Eoan:
  New

Bug description:
  Running a simple "update-initramfs -u" in a system with kmod version
  26+20191223-1ubuntu1 (from focal-proposed)

  will result into a bunch of:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/var/tmp/mkinitramfs_FLkEYb/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  errors. That happens because:

  modinfo prints an error message if modules.builtin.bin is missing and
  it was fixed upstream (Debian) in:

  commit 835d584
  Author: Ben Hutchings 
  Date:   Sat Jan 18 15:44:32 2020

  mkinitramfs: Copy modules.builtin.bin into initramfs

  modinfo now prints an error message if modules.builtin.bin (created
  by depmod) is missing.  Copy it in early if it's present.

  Closes: #948257
  Signed-off-by: Ben Hutchings 

  and reported in bug:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948257

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261/+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 1865504] Re: hwclock reports incorrect status in audit message

[Launchpad Bug Tracker]

This bug was fixed in the package util-linux - 2.34-0.1ubuntu8

---
util-linux (2.34-0.1ubuntu8) focal; urgency=medium

  * hwclock: fix audit exit status (LP: #1865504)

 -- Joy Latten   Thu, 05 Mar 2020 11:23:23
-0600

** Changed in: util-linux (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  hwclock reports incorrect status in audit message

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Bionic:
  New
Status in util-linux source package in Eoan:
  New
Status in util-linux package in Debian:
  Unknown

Bug description:
  [IMPACT]
  hwclock reports incrorect status in audit message

  hwclock calls audit_log_user_message(3) to create an audit entry.
  audit_log_user_message(3) result 1 is "success" and 0 is
  "failed", hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse
  status. Thus reports it's status incorrectly in audit message. 

  It is a requirement for Common Criteria Certification that hwclock
  reports correct status in audit message.

  This has been fixed upstream in https://github.com/karelzak/util-
  linux/commit/189edf1fe501ea39b35911337eab1740888fae7a

  [TEST]

  Steps to test:
  1. Install auditd
  2. Run following testcase,

  # hwclock
  2020-03-02 15:03:03.280351+
  # hwclock --set --date "1/1/2000 00:00:00"
  # echo $?
  0
  # hwclock
  2000-01-01 00:00:05.413924+
  # hwclock --utc --systohc
  # echo $?
  0
  # hwclock
  2020-03-02 15:07:00.264331+

  Following audit messages from /var/log/audit/audit.log,

  type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0 auid=1000 
ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic-fips 
addr=? terminal=pts/0 res=failed'
  type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0 auid=1000 
ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic-fips 
addr=? terminal=pts/0 res=failed'

  Note that last entry in each audit record produced when hardware clock
  was modified has, "res=failed". Although, testcase shows no failure
  occurred.

  [Regression Potential]
  There should not be any regression to fix the status given to auditd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865504/+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 1866012] Re: depmod ERROR during Setting up linux-modules-5.4.0-17-generic

[Thadeu Lima de Souza Cascardo]

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948350#20

In particular, this seems to come to a Debian specific patch on kmod
that turns that message from a DEBUG message to an ERROR message.

As there has been no responses from the patch's author, we could do a
quick diligence investigation in order to drop it. Or we should just
simply drop it. That way, we get rid of spurious bug reports, and can
work on real bugs, in case there is any, and we should get reports for
those.

Cascardo.

** Bug watch added: Debian Bug tracker #948350
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948350

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

Title:
  depmod ERROR during Setting up linux-modules-5.4.0-17-generic

Status in kmod package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Deploy Focal on a KVM ndoe, enable proposed
  2. Run sudo apt dist-upgrade

  The console will be flushed with:
  Setting up libisc1105:amd64 (1:9.11.16+dfsg-3~build1) ...
  Setting up linux-modules-5.4.0-17-generic (5.4.0-17.21) ...
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  
  Setting up apt-utils (1.9.12) ...
  Setting up libselinux1-dev:amd64 (3.0-1build2) ...
  Setting up libglib2.0-0:amd64 (2.64.0-1) ...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: User Name 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  4 08:29 seq
   crw-rw 1 root audio 116, 33 Mar  4 08:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar  4 09:06:42 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=36e162f3-41b5-4487-a6dc-09ba4e37d3bf ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux-5.4
  StagingDrivers: exfat
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1866012/+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 1866012] Re: depmod ERROR during Setting up linux-modules-5.4.0-17-generic

[Rafael David Tinoco]

Related bugs:

https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1866012
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1864992

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

Title:
  depmod ERROR during Setting up linux-modules-5.4.0-17-generic

Status in kmod package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Deploy Focal on a KVM ndoe, enable proposed
  2. Run sudo apt dist-upgrade

  The console will be flushed with:
  Setting up libisc1105:amd64 (1:9.11.16+dfsg-3~build1) ...
  Setting up linux-modules-5.4.0-17-generic (5.4.0-17.21) ...
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  
  Setting up apt-utils (1.9.12) ...
  Setting up libselinux1-dev:amd64 (3.0-1build2) ...
  Setting up libglib2.0-0:amd64 (2.64.0-1) ...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: User Name 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  4 08:29 seq
   crw-rw 1 root audio 116, 33 Mar  4 08:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar  4 09:06:42 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=36e162f3-41b5-4487-a6dc-09ba4e37d3bf ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux-5.4
  StagingDrivers: exfat
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1866012/+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 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Rafael David Tinoco]

Related bugs:

https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1866012
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1864992

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in curtin:
  Invalid
Status in subiquity:
  New
Status in kmod package in Ubuntu:
  Confirmed

Bug description:
  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1864992/+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 1863261] Re: modinfo prints an error message if modules.builtin.bin is missing

[Rafael David Tinoco]

Related bugs:

https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1866012
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1864992

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

Title:
  modinfo prints an error message if modules.builtin.bin is missing

Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  Running a simple "update-initramfs -u" in a system with kmod version
  26+20191223-1ubuntu1 (from focal-proposed)

  will result into a bunch of:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/var/tmp/mkinitramfs_FLkEYb/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  errors. That happens because:

  modinfo prints an error message if modules.builtin.bin is missing and
  it was fixed upstream (Debian) in:

  commit 835d584
  Author: Ben Hutchings 
  Date:   Sat Jan 18 15:44:32 2020

  mkinitramfs: Copy modules.builtin.bin into initramfs

  modinfo now prints an error message if modules.builtin.bin (created
  by depmod) is missing.  Copy it in early if it's present.

  Closes: #948257
  Signed-off-by: Ben Hutchings 

  and reported in bug:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948257

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261/+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 1863261] Re: modinfo prints an error message if modules.builtin.bin is missing

[Rafael David Tinoco]

** No longer affects: kmod (Ubuntu Focal)

** No longer affects: kmod (Ubuntu)

** No longer affects: initramfs-tools (Ubuntu 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/1863261

Title:
  modinfo prints an error message if modules.builtin.bin is missing

Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  Running a simple "update-initramfs -u" in a system with kmod version
  26+20191223-1ubuntu1 (from focal-proposed)

  will result into a bunch of:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/var/tmp/mkinitramfs_FLkEYb/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  errors. That happens because:

  modinfo prints an error message if modules.builtin.bin is missing and
  it was fixed upstream (Debian) in:

  commit 835d584
  Author: Ben Hutchings 
  Date:   Sat Jan 18 15:44:32 2020

  mkinitramfs: Copy modules.builtin.bin into initramfs

  modinfo now prints an error message if modules.builtin.bin (created
  by depmod) is missing.  Copy it in early if it's present.

  Closes: #948257
  Signed-off-by: Ben Hutchings 

  and reported in bug:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948257

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261/+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 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Juerg Haefliger]

There seem to be multiple issues related to these benign errors:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948257
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949444

Just to be clear, it's not a kernel (linux) package problem.

** Bug watch added: Debian Bug tracker #948257
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948257

** Bug watch added: Debian Bug tracker #949444
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949444

** No longer affects: linux (Ubuntu)

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in curtin:
  Invalid
Status in subiquity:
  New
Status in kmod package in Ubuntu:
  Confirmed

Bug description:
  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1864992/+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 1866959] [NEW] Password - No Place

[Rudra Saraswat]

Public bug reported:

In all Ubuntu versions, sometimes, I'd type, but the input would not be
visible. This is urgent since people might type wrong passwords and then
think that they have forgotten the password.

Description:Ubuntu 18.04.4 LTS
Release:18.04

lightdm:
  Installed: 1.26.0-0ubuntu1
  Candidate: 1.26.0-0ubuntu1
  Version table:
 *** 1.26.0-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status

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

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

Title:
  Password - No Place

Status in lightdm package in Ubuntu:
  New

Bug description:
  In all Ubuntu versions, sometimes, I'd type, but the input would not
  be visible. This is urgent since people might type wrong passwords and
  then think that they have forgotten the password.

  Description:Ubuntu 18.04.4 LTS
  Release:18.04

  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1866959/+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 1866955] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[vjl]

after receiving this error I ran:

wget http://security.ubuntu.com/ubuntu/pool/main/c/ca-certificates/ca-
certificates_20170717~16.04.1_all.deb

Then I ran:

dpkg -i ca-certificates_20170717~16.04.1_all.deb

and finally:

dpkg --configure -a

which unpacked 20180409 over 20170717~16.04.1

However, I do not believe my server is in a good state. Postfix/dovecot
are running fine, but an attempt to start apache 2:

Failed to start apache2.service: Unit apache2.service is masked.

I am unsure if I should reboot the server or not...

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Doing a 'do-release-upgrade', I received this error near the end. The
  install/upgrade did not finish as a result.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211
  Uname: Linux 4.4.0-174-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  Date: Wed Mar 11 02:20:32 2020
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-07-27 (1688 days ago)
  InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2020-03-11 (0 days ago)

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