date:20200916

[Expired for ibus (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to
  make backup link of './usr/share/ibus/dicts/emoji-af.dict' before
  installing new version: Input/output error

Status in ibus package in Ubuntu:
  Expired

Bug description:
  I have problems while install ubuntu 20.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: ibus-data 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jul 18 22:43:47 2020
  DuplicateSignature:
   package:ibus-data:1.5.22-2ubuntu2
   Unpacking ibus-data (1.5.22-2ubuntu2.1) over (1.5.22-2ubuntu2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-W4DEHL/31-ibus-data_1.5.22-2ubuntu2.1_all.deb (--unpack):
unable to make backup link of './usr/share/ibus/dicts/emoji-af.dict' before 
installing new version: Input/output error
  ErrorMessage: unable to make backup link of 
'./usr/share/ibus/dicts/emoji-af.dict' before installing new version: 
Input/output error
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: ibus
  Title: package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to 
make backup link of './usr/share/ibus/dicts/emoji-af.dict' before installing 
new version: Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1888092/+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 1893899] Re: update alsa/audio related infomation collection code in apport

2020-09-16 Thread Yuan-Chen Cheng

Is there a quick and clean way to extract alsa-info from output of pa-
info?

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

Title:
  update alsa/audio related infomation collection code in apport

Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  Incomplete
Status in apport source package in Groovy:
  Incomplete

Bug description:
  what need to change

  1. try to use /usr/sbin/alsa-info before try 
/usr/share/alsa-base/alsa-info.sh (weird for me that two copy of alsa-info 
co-exists, but anyway)
  2. add pa-info (exist after focal)
  3. add ucm2 directory. (exist after focal)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893899/+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 1895839] Re: CVE-2020-24977

2020-09-16 Thread Alex Murray

** Information type changed from Private Security to Public Security

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

Title:
  CVE-2020-24977

Status in libxml2 package in Ubuntu:
  New

Bug description:
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24977

  Upstream patch:
  
https://gitlab.gnome.org/GNOME/libxml2/-/commit/8e7c20a1af8776677d7890f30b7a180567701a49

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1895839/+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 1893899] Re: update alsa/audio related infomation collection code in apport

2020-09-16 Thread Hui Wang

the pa-info already includes calling the alsa-info.sh, it is ok to
remove the alsa-info.

But it is better to keep the alsa-info, since the log of alsa-info is
cleaner than the log of pa-info, pa-info includes many pulseaudio level
logs. And If we want to exchange the log with upstream developers, we
often send alsa-info.txt since it is possible that other Linux
distributions don't use pulseaudio as the audio server, they only need a
clean alsa-info.txt without pulseaudio logs.

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

Title:
  update alsa/audio related infomation collection code in apport

Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  Incomplete
Status in apport source package in Groovy:
  Incomplete

Bug description:
  what need to change

  1. try to use /usr/sbin/alsa-info before try 
/usr/share/alsa-base/alsa-info.sh (weird for me that two copy of alsa-info 
co-exists, but anyway)
  2. add pa-info (exist after focal)
  3. add ucm2 directory. (exist after focal)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893899/+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 1895894] Re: Xorg freeze

Next time the problem happens and after rebooting please immediately
run:

  journalctl -b-1 > prevboot.txt

and then attach the resulting text file here.


** Tags added: nouveau

** Summary changed:

- Xorg freeze
+ [nouveau] Xorg freeze

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

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

** Summary changed:

- [nouveau] Xorg freeze
+ [nouveau] Screen freeze

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

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

Title:
  [nouveau] Screen freeze

Status in Ubuntu:
  Incomplete

Bug description:
  Hello team, I'm using chromium, evrything is working well, but
  sometimes the audio is working well but everything is freezes, i can't
  use anything, but the audio is still working, I can't fix it except
  rebbot the system, it's happens a lot recently, i hope you can help
  me, Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 16 22:07:54 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GK106GLM [Quadro K2100M] [103c:2254]
  InstallationDate: Installed on 2020-07-09 (69 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Hewlett-Packard HP ZBook 15 G2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=162424dc-b362-4e3a-8b36-d0389c6bbfee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/23/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M70 Ver. 01.12
  dmi.board.name: 2253
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 03.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM70Ver.01.12:bd09/23/2015:svnHewlett-Packard:pnHPZBook15G2:pvrA3009DD10203:rvnHewlett-Packard:rn2253:rvrKBCVersion03.10:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP ZBook 15 G2
  dmi.product.sku: N6L61UP#ABF
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1895894/+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 1895816] Re: gnome-shell freezing (and gdm restarting) -> xorg crash file found

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) => 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/1895816

Title:
  gnome-shell freezing (and gdm restarting) -> xorg crash file found

Status in Ubuntu:
  Incomplete

Bug description:
  I have a problem with gnome-shell and gdm. My shell sometimes (not
  reproducible atm) freezes. Under some circumstances gdm will be
  restarted and I am logged out and all programs are killed. When
  logging in again, chromium for example, tells me, that the last time
  it was not exited properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 16 11:49:54 2020
  DistUpgraded: 2020-09-09 11:59:44,488 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.4.0-47-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 630 [17aa:505e]
 Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:505e]
  InstallationDate: Installed on 2017-08-28 (1114 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 20J6003DGE
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-47-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-09-09 (6 days ago)
  dmi.bios.date: 04/23/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0FET52W (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20J6003DGE
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0FET52W(1.32):bd04/23/2020:svnLENOVO:pn20J6003DGE:pvrThinkPadT470p:rvnLENOVO:rn20J6003DGE:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470p
  dmi.product.name: 20J6003DGE
  dmi.product.sku: LENOVO_MT_20J6_BU_Think_FM_ThinkPad T470p
  dmi.product.version: ThinkPad T470p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1895816/+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 1895665] Re: PulseAudio automatically switches from HDMI 2 after display sleep

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => 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/1895665

Title:
  PulseAudio automatically switches from HDMI 2 after display sleep

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have an Nvidia based video card that has an HDMI output + a DisplayPort 
output.
  DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output 
is listed as "Digital Stereo (HDMI 2)".

  I prefer to use "Digital Stereo (HDMI 2)".
  But after each display sleep (screen lock for example) audio is switched to 
built in audio

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Sep 15 14:56:58 2020
  InstallationDate: Installed on 2020-06-20 (86 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.name: 0CNDTP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G5 5590
  dmi.product.sku: 08EA
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+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 1894338] Re: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work

2020-09-16 Thread Hui Wang

If you run sudo evtest and choose 11, then press the button on the
headset, does the keycode show in the evtest output steadily?

If it does, it means the driver could work well.

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

Title:
  [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control
  buttons don't work

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  My earphones are the one coming with Samsung Galaxy S8 (here:
  https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung-
  earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04
  (dual-boot with Windows 10, Secure Boot enabled)

  Trying to set the volume from my earphones' controls doesn't work, no
  modification on the volume, the sound bar on Ubuntu doesn't appear in
  order to indicate volume change. I would like to change the master
  volume, or whatever my common laptop controls do when I up/down the
  volume controls on my earphones, like it happens on Windows 10. Why
  does the erroneous behavior of being unable to set volume from my
  earphones happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.10
  ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
  Uname: Linux 4.15.0-115-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jason  3523 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  4 23:29:52 2020
  InstallationDate: Installed on 2018-09-28 (706 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.0
  dmi.board.name: 02P5YY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7570
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-28 (718 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: snd_hda_codec_hdmi snd_hda_codec_realtek 
snd_hda_codec_generic hid_multitouch wmi_bmof dell_wmi snd_hda_intel 
snd_intel_dspcfg soundwire_intel soundwire_generic_allocation snd_soc_core 
dell_laptop ledtrig_audio snd_compress soundwire_cadence soundwire_bus 
dell_smbios snd_hda_codec dell_wmi_descriptor snd_hwdep dcdbas snd_hda_core 
snd_pcm x86_pkg_temp_thermal intel_powerclamp iwlmvm snd_seq_midi 
snd_seq_midi_event iwlwifi snd_rawmidi i915 snd_seq snd_seq_device i2c_algo_bit 
snd_timer drm_kms_helper syscopyarea sysfillrect sysimgblt snd fb_sys_fops drm 
int3403_thermal soundcore wmi intel_lpss_pci int3402_thermal 
processor_thermal_device int3400_thermal int340x_thermal_zone 
intel_soc_dts_iosf acpi_thermal_rel mei_me intel_lpss intel_pch_thermal 
mfd_core mei efivarfs xhci_pci xhci_hcd i2c_hid
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 5.9.0-rc3+ x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894338/+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 1746638] Re: [GeForce 6150SE nForce 430] PC freezes and crashes

2020-09-16 Thread Tim Riker

This happens to me too. Note: when X is NOT running, the kernel still
locks up. This appears to be a kernel driver issue and not an X issue.

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

Title:
  [GeForce 6150SE nForce 430] PC freezes and crashes

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When using the nouveau graphics driver my pc freezes and crashes.

  WORKAROUND: Use the proprietary nvidia driver.

  WORKAROUND: Use PPA from https://launchpad.net/~oibaf/+archive/ubuntu
  /graphics-drivers

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus 
CX3900/DX4000/DX4050]
   Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  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 N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Feb  1 01:34:53 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746638/+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 1895302] Re: groovy debootstrap leaves /e/d/motd-news.wasremoved around

This bug was fixed in the package base-files - 11ubuntu13

---
base-files (11ubuntu13) groovy; urgency=medium

  * Fix handling of /e/d/motd-news.wasremoved (LP: #1895302):
- d/postinst.in: check if ubuntu-server is installed before creating
  the .wasremoved file
- d/postinst.in: re-arrange the cascading conditionals around the
  creation of the .wasremoved file for better clarity
- d/postinst.in: only consider creating the .wasremoved file in upgrades,
  never fresh installs like in debootstrap for example
- d/motd-news-config.postinst: always remove /e/d/motd-news.wasremoved
  if present

 -- Andreas Hasenack   Wed, 16 Sep 2020 10:26:50
-0300

** Changed in: base-files (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  groovy debootstrap leaves /e/d/motd-news.wasremoved around

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  In Progress
Status in base-files source package in Bionic:
  In Progress
Status in base-files source package in Focal:
  In Progress

Bug description:
  [Impact]
  A fresh install of base-files, like done when using debootstrap, using the 
base-files from the -updates repository (in the case of ubuntu stable 
releases), will leave an empty /etc/default/motd-news.wasremoved file. This 
file is an artifact of the mechanism used to handle a corner case in the 
previous SRU where it would signal the motd-news-config package to install 
/etc/default/motd-news with ENABLED=0. See testcases (h) and (i) in the 
previous base-files SRU at 
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888575 for details. 
In test case (i) it was acked that the empty .wasremoved file was lying around, 
but its impact was deemed not relevant (see [other info] item (a)).

  Another case where /etc/default/motd-news.wasremoved would be created
  when it shouldn't be is when you have just base-files installed (and
  no ubuntu-server or motd-news-config) and did a reinstall of base-
  files, or an upgrade. It would again touch /etc/default/motd-
  news.wasremoved.

  The consequence of having /etc/default/motd-news.wasremoved when it's
  unintended is that a follow-up install of ubuntu-server, or motd-news-
  config for that matter, will install /etc/default/motd-news with
  ENABLED=0 instead of ENABLED=1.

  This was the case of the groovy debootstrap which resulted in this bug
  being filed. While debootstrap won't mix multiple repositories (like
  release with updates), and thus this isn't easily a problem in
  released versions of ubuntu, the groovy case was the one that was
  doing a fresh install of base-files with the buggy touch /etc/default
  /motd-news.wasremoved, and a subsequent install of ubuntu-server left
  motd-news disabled in groovy images produced by such a method
  (debootstrap).

  These are the scenarios I was able to come up with in which a stable
  release could be affected by this bug:

  a) debootstrap with release and updates pocket enabled
  There are no config options that I'm aware of that would tell debootstrap to 
use multiple pockets when creating a chroot, but let's say it was done by 
hacking the script or something else. It would then be the same case as groovy 
until this fix: subsequent installations of ubuntu-server or motd-news-config 
would default to having motd-news disabled

  b) A system that has just base-files from the previous SRU installed,
  and no ubuntu-server and no motd-news-config. If base-files were
  updated again and without the fix presented here (let's say, another
  SRU instead of this one), it would create /etc/default/motd-
  news.wasremoved, and again, a subsequent install of ubuntu-server or
  motd-news-config would install motd-news in a disabled state

  c) Any other case where the postinst script of base-files is run again
  without the fix presented here, and when there is no /etc/default
  /motd-news{,.dpkg*} file present.

  To avoid creating /etc/default/motd-news.wasremoved when we shouldn't, the 
maintainer scripts were changed as follows:
  - motd-news-config postinst: always remove the .wasremoved file in configure 
if found, regardless if /etc/default/motd-news was sed'ed or not, or if we are 
upgrading or on a first install
  - base-files postinst: guard the creation of .wasremoved with:
    - Only during an upgrade
    - Only if ubuntu-server is installed (via a dpkg -l check)

  [Test Case]
  * On the system under test, remove motd-news-config and ubuntu-server if they 
are installed, and keep base-files from the update pocket. Something like this:
  sudo apt update && sudo apt dist-upgrade -y
  sudo apt purge motd-news-config ubuntu-server
  apt-cache policy base-files <-- to verify it's from updates

  * In this scenario, you

[Touch-packages] [Bug 1893899] Re: update alsa/audio related infomation collection code in apport

By adding in a call to '/usr/bin/pa-info' in apport/hookutils.py there
ends up being duplicate information in the apport created report as
'/usr/bin/pa-info' calls 'alsa-info' which was already included in the
report. How do you feel about removing the calls to 'alsa-info' and just
using 'pa-info'?

Thanks!

** Changed in: apport (Ubuntu Groovy)
   Status: Confirmed => Incomplete

** Changed in: apport (Ubuntu Groovy)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  update alsa/audio related infomation collection code in apport

Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  Incomplete
Status in apport source package in Groovy:
  Incomplete

Bug description:
  what need to change

  1. try to use /usr/sbin/alsa-info before try 
/usr/share/alsa-base/alsa-info.sh (weird for me that two copy of alsa-info 
co-exists, but anyway)
  2. add pa-info (exist after focal)
  3. add ucm2 directory. (exist after focal)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893899/+subscriptions

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

[Touch-packages] [Bug 1892559] Re: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite

2020-09-16 Thread Seth Arnold

ubuntu-security is now subscribed to pcsc-lite bugs.

Thanks

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

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

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

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

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

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

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

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

  Has a debian/watch file.
  Quilt packaging.

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

  [Dependencies]
  Minimal dependencies, in main

  [Standards compliance]
  Appears to satisfy FHS and Debian policy

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

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

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

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

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

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

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

  Quilt packaging.

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

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

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

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

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

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

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

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

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

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

  Otherwise appears to satisfy FHS and Debian policy.

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

  [Background information]
  Dependency of

[Touch-packages] [Bug 1879980] Re: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

2020-09-16 Thread Guilherme G. Piccoli

** Patch added: "bionic_cryptsetup_lp1879980.debdiff"
   
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5411486/+files/bionic_cryptsetup_lp1879980.debdiff

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

Title:
  Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

Status in cryptsetup package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in mdadm package in Ubuntu:
  Opinion
Status in cryptsetup source package in Xenial:
  Won't Fix
Status in initramfs-tools source package in Xenial:
  Won't Fix
Status in mdadm source package in Xenial:
  Won't Fix
Status in cryptsetup source package in Bionic:
  In Progress
Status in initramfs-tools source package in Bionic:
  In Progress
Status in mdadm source package in Bionic:
  Opinion
Status in cryptsetup source package in Focal:
  In Progress
Status in initramfs-tools source package in Focal:
  Fix Released
Status in mdadm source package in Focal:
  Opinion
Status in cryptsetup source package in Groovy:
  In Progress
Status in initramfs-tools source package in Groovy:
  Fix Released
Status in mdadm source package in Groovy:
  Opinion
Status in cryptsetup package in Debian:
  New

Bug description:
  [Impact]
  * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu 
is currently unable to decrypt the rootfs if the array gets degraded, like for 
example if one of the array's members gets removed.

  * The problem has 2 main aspects: first, cryptsetup initramfs script
  attempts to decrypt the array only in the local-top boot stage, and in
  case it fails, it gives-up and show user a shell (boot is aborted).

  * Second, mdadm initramfs script that assembles degraded arrays
  executes later on boot, in the local-block stage. So, in a stacked
  setup of encrypted root on top of RAID, if the RAID is degraded,
  cryptsetup fails early in the boot, preventing mdadm to assemble the
  degraded array.

  * The hereby proposed solution has 2 components: first, cryptsetup
  script is modified to allow a gentle failure on local-top stage, then
  it retries for a while (according to a heuristic based on ROOTDELAY
  with minimum of 30 executions) in a later stage (local-block). This
  gives time to other initramfs scripts to run, like mdadm in local-
  block stage. And this is meant to work this way according to
  initramfs-tools documentation (although Ubuntu changed it a bit with
  wait-for-root, hence we stopped looping on local-block, see next
  bullet).

  * Second, initramfs-tools was adjusted - currently, it runs for a
  while the mdadm local-block script, in order to assemble the arrays in
  a non-degraded mode. We extended this approach to also execute
  cryptsetup, in a way that after mdadm ends its execution, we execute
  at least once more time cryptsetup. In an ideal world we should loop
  on local-block as Debian's initramfs (in a way to remove hardcoded
  mdadm/cryptsetup mentions from initramfs-tools code), but this would
  be really a big change, non-SRUable probably. I plan to work that for
  future Ubuntu releases.

  [Test case]
  * Install Ubuntu in a Virtual Machine with 2 disks. Use the installer to 
create a RAID1 volume and an encrypted root on top of it.

  * Boot the VM, and use "sgdisk"/"wipefs" to erase the partition table
  from one of the RAID members. Reboot and it will fail to mount rootfs
  and continue boot process.

  * If using the initramfs-toos/cryptsetup patches hereby proposed, the
  rootfs can be mounted normally.

  [Regression potential]

  * There are potential for regressions, since this is a change in 2
  boot components. The patches were designed in a way to keep the
  regular case working, it changes the failure case which is not
  currently working anyway.

  * A modification in the behavior of cryptsetup was introduced: right
  now, if we fail the password 3 times (the default maximum attempts),
  the script doesn't "panic" and drop to a shell immediately; instead it
  runs once more (or twice, if mdadm is installed) before failing. This
  is a minor change given the benefit of the being able to mount rootfs
  in a degraded RAID1 scenario.

  * Other potential regressions could show-up as boot problems, but the
  change in initramfs-tools specifically is not invasive, it just may
  delay boot time a bit, given we now run cryptsetup multiple times on
  local-block, with 1 sec delays between executions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1879980/+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 1879980] Re: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

2020-09-16 Thread Guilherme G. Piccoli

** Patch added: "focal_cryptsetup_lp1879980_V2.debdiff"
   
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5411485/+files/focal_cryptsetup_lp1879980_V2.debdiff

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

Title:
  Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

Status in cryptsetup package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in mdadm package in Ubuntu:
  Opinion
Status in cryptsetup source package in Xenial:
  Won't Fix
Status in initramfs-tools source package in Xenial:
  Won't Fix
Status in mdadm source package in Xenial:
  Won't Fix
Status in cryptsetup source package in Bionic:
  In Progress
Status in initramfs-tools source package in Bionic:
  In Progress
Status in mdadm source package in Bionic:
  Opinion
Status in cryptsetup source package in Focal:
  In Progress
Status in initramfs-tools source package in Focal:
  Fix Released
Status in mdadm source package in Focal:
  Opinion
Status in cryptsetup source package in Groovy:
  In Progress
Status in initramfs-tools source package in Groovy:
  Fix Released
Status in mdadm source package in Groovy:
  Opinion
Status in cryptsetup package in Debian:
  New

Bug description:
  [Impact]
  * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu 
is currently unable to decrypt the rootfs if the array gets degraded, like for 
example if one of the array's members gets removed.

  * The problem has 2 main aspects: first, cryptsetup initramfs script
  attempts to decrypt the array only in the local-top boot stage, and in
  case it fails, it gives-up and show user a shell (boot is aborted).

  * Second, mdadm initramfs script that assembles degraded arrays
  executes later on boot, in the local-block stage. So, in a stacked
  setup of encrypted root on top of RAID, if the RAID is degraded,
  cryptsetup fails early in the boot, preventing mdadm to assemble the
  degraded array.

  * The hereby proposed solution has 2 components: first, cryptsetup
  script is modified to allow a gentle failure on local-top stage, then
  it retries for a while (according to a heuristic based on ROOTDELAY
  with minimum of 30 executions) in a later stage (local-block). This
  gives time to other initramfs scripts to run, like mdadm in local-
  block stage. And this is meant to work this way according to
  initramfs-tools documentation (although Ubuntu changed it a bit with
  wait-for-root, hence we stopped looping on local-block, see next
  bullet).

  * Second, initramfs-tools was adjusted - currently, it runs for a
  while the mdadm local-block script, in order to assemble the arrays in
  a non-degraded mode. We extended this approach to also execute
  cryptsetup, in a way that after mdadm ends its execution, we execute
  at least once more time cryptsetup. In an ideal world we should loop
  on local-block as Debian's initramfs (in a way to remove hardcoded
  mdadm/cryptsetup mentions from initramfs-tools code), but this would
  be really a big change, non-SRUable probably. I plan to work that for
  future Ubuntu releases.

  [Test case]
  * Install Ubuntu in a Virtual Machine with 2 disks. Use the installer to 
create a RAID1 volume and an encrypted root on top of it.

  * Boot the VM, and use "sgdisk"/"wipefs" to erase the partition table
  from one of the RAID members. Reboot and it will fail to mount rootfs
  and continue boot process.

  * If using the initramfs-toos/cryptsetup patches hereby proposed, the
  rootfs can be mounted normally.

  [Regression potential]

  * There are potential for regressions, since this is a change in 2
  boot components. The patches were designed in a way to keep the
  regular case working, it changes the failure case which is not
  currently working anyway.

  * A modification in the behavior of cryptsetup was introduced: right
  now, if we fail the password 3 times (the default maximum attempts),
  the script doesn't "panic" and drop to a shell immediately; instead it
  runs once more (or twice, if mdadm is installed) before failing. This
  is a minor change given the benefit of the being able to mount rootfs
  in a degraded RAID1 scenario.

  * Other potential regressions could show-up as boot problems, but the
  change in initramfs-tools specifically is not invasive, it just may
  delay boot time a bit, given we now run cryptsetup multiple times on
  local-block, with 1 sec delays between executions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1879980/+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 1893899] Re: update alsa/audio related infomation collection code in apport

** Tags removed: rls-gg-incoming

** Also affects: apport (Ubuntu Groovy)
   Importance: Undecided
   Status: Confirmed

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

Title:
  update alsa/audio related infomation collection code in apport

Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Groovy:
  Confirmed

Bug description:
  what need to change

  1. try to use /usr/sbin/alsa-info before try 
/usr/share/alsa-base/alsa-info.sh (weird for me that two copy of alsa-info 
co-exists, but anyway)
  2. add pa-info (exist after focal)
  3. add ucm2 directory. (exist after focal)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893899/+subscriptions

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

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

** Also affects: apport (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: apport (Ubuntu Groovy)
   Status: New => In Progress

** Changed in: apport (Ubuntu Groovy)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

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

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

Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Groovy:
  In Progress

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

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

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

[Touch-packages] [Bug 1879980] Re: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

2020-09-16 Thread Guilherme G. Piccoli

After the cryptsetup FTBFS investigation (on LP #1891473), coincidentally a 
security fix was released for such package, that included a fix for the FTBFS. 
So, this is a "rebase" on top of the latest version for Focal/Groovy - Bionic 
wasn't affected, but I'm re-uploading its debdiff nevertheless.
Thanks,


Guilherme

** Patch added: "groovy_cryptsetup_lp1879980_V2.debdiff"
   
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5411484/+files/groovy_cryptsetup_lp1879980_V2.debdiff

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

Title:
  Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

Status in cryptsetup package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in mdadm package in Ubuntu:
  Opinion
Status in cryptsetup source package in Xenial:
  Won't Fix
Status in initramfs-tools source package in Xenial:
  Won't Fix
Status in mdadm source package in Xenial:
  Won't Fix
Status in cryptsetup source package in Bionic:
  In Progress
Status in initramfs-tools source package in Bionic:
  In Progress
Status in mdadm source package in Bionic:
  Opinion
Status in cryptsetup source package in Focal:
  In Progress
Status in initramfs-tools source package in Focal:
  Fix Released
Status in mdadm source package in Focal:
  Opinion
Status in cryptsetup source package in Groovy:
  In Progress
Status in initramfs-tools source package in Groovy:
  Fix Released
Status in mdadm source package in Groovy:
  Opinion
Status in cryptsetup package in Debian:
  New

Bug description:
  [Impact]
  * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu 
is currently unable to decrypt the rootfs if the array gets degraded, like for 
example if one of the array's members gets removed.

  * The problem has 2 main aspects: first, cryptsetup initramfs script
  attempts to decrypt the array only in the local-top boot stage, and in
  case it fails, it gives-up and show user a shell (boot is aborted).

  * Second, mdadm initramfs script that assembles degraded arrays
  executes later on boot, in the local-block stage. So, in a stacked
  setup of encrypted root on top of RAID, if the RAID is degraded,
  cryptsetup fails early in the boot, preventing mdadm to assemble the
  degraded array.

  * The hereby proposed solution has 2 components: first, cryptsetup
  script is modified to allow a gentle failure on local-top stage, then
  it retries for a while (according to a heuristic based on ROOTDELAY
  with minimum of 30 executions) in a later stage (local-block). This
  gives time to other initramfs scripts to run, like mdadm in local-
  block stage. And this is meant to work this way according to
  initramfs-tools documentation (although Ubuntu changed it a bit with
  wait-for-root, hence we stopped looping on local-block, see next
  bullet).

  * Second, initramfs-tools was adjusted - currently, it runs for a
  while the mdadm local-block script, in order to assemble the arrays in
  a non-degraded mode. We extended this approach to also execute
  cryptsetup, in a way that after mdadm ends its execution, we execute
  at least once more time cryptsetup. In an ideal world we should loop
  on local-block as Debian's initramfs (in a way to remove hardcoded
  mdadm/cryptsetup mentions from initramfs-tools code), but this would
  be really a big change, non-SRUable probably. I plan to work that for
  future Ubuntu releases.

  [Test case]
  * Install Ubuntu in a Virtual Machine with 2 disks. Use the installer to 
create a RAID1 volume and an encrypted root on top of it.

  * Boot the VM, and use "sgdisk"/"wipefs" to erase the partition table
  from one of the RAID members. Reboot and it will fail to mount rootfs
  and continue boot process.

  * If using the initramfs-toos/cryptsetup patches hereby proposed, the
  rootfs can be mounted normally.

  [Regression potential]

  * There are potential for regressions, since this is a change in 2
  boot components. The patches were designed in a way to keep the
  regular case working, it changes the failure case which is not
  currently working anyway.

  * A modification in the behavior of cryptsetup was introduced: right
  now, if we fail the password 3 times (the default maximum attempts),
  the script doesn't "panic" and drop to a shell immediately; instead it
  runs once more (or twice, if mdadm is installed) before failing. This
  is a minor change given the benefit of the being able to mount rootfs
  in a degraded RAID1 scenario.

  * Other potential regressions could show-up as boot problems, but the
  change in initramfs-tools specifically is not invasive, it just may
  delay boot time a bit, given we now run cryptsetup multiple times on
  local-block, with 1 sec delays between executions.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1895302] Re: groovy debootstrap leaves /e/d/motd-news.wasremoved around

** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/390863

** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/390864

** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/390865

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

Title:
  groovy debootstrap leaves /e/d/motd-news.wasremoved around

Status in base-files package in Ubuntu:
  In Progress
Status in base-files source package in Xenial:
  In Progress
Status in base-files source package in Bionic:
  In Progress
Status in base-files source package in Focal:
  In Progress

Bug description:
  [Impact]
  A fresh install of base-files, like done when using debootstrap, using the 
base-files from the -updates repository (in the case of ubuntu stable 
releases), will leave an empty /etc/default/motd-news.wasremoved file. This 
file is an artifact of the mechanism used to handle a corner case in the 
previous SRU where it would signal the motd-news-config package to install 
/etc/default/motd-news with ENABLED=0. See testcases (h) and (i) in the 
previous base-files SRU at 
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888575 for details. 
In test case (i) it was acked that the empty .wasremoved file was lying around, 
but its impact was deemed not relevant (see [other info] item (a)).

  Another case where /etc/default/motd-news.wasremoved would be created
  when it shouldn't be is when you have just base-files installed (and
  no ubuntu-server or motd-news-config) and did a reinstall of base-
  files, or an upgrade. It would again touch /etc/default/motd-
  news.wasremoved.

  The consequence of having /etc/default/motd-news.wasremoved when it's
  unintended is that a follow-up install of ubuntu-server, or motd-news-
  config for that matter, will install /etc/default/motd-news with
  ENABLED=0 instead of ENABLED=1.

  This was the case of the groovy debootstrap which resulted in this bug
  being filed. While debootstrap won't mix multiple repositories (like
  release with updates), and thus this isn't easily a problem in
  released versions of ubuntu, the groovy case was the one that was
  doing a fresh install of base-files with the buggy touch /etc/default
  /motd-news.wasremoved, and a subsequent install of ubuntu-server left
  motd-news disabled in groovy images produced by such a method
  (debootstrap).

  These are the scenarios I was able to come up with in which a stable
  release could be affected by this bug:

  a) debootstrap with release and updates pocket enabled
  There are no config options that I'm aware of that would tell debootstrap to 
use multiple pockets when creating a chroot, but let's say it was done by 
hacking the script or something else. It would then be the same case as groovy 
until this fix: subsequent installations of ubuntu-server or motd-news-config 
would default to having motd-news disabled

  b) A system that has just base-files from the previous SRU installed,
  and no ubuntu-server and no motd-news-config. If base-files were
  updated again and without the fix presented here (let's say, another
  SRU instead of this one), it would create /etc/default/motd-
  news.wasremoved, and again, a subsequent install of ubuntu-server or
  motd-news-config would install motd-news in a disabled state

  c) Any other case where the postinst script of base-files is run again
  without the fix presented here, and when there is no /etc/default
  /motd-news{,.dpkg*} file present.

  To avoid creating /etc/default/motd-news.wasremoved when we shouldn't, the 
maintainer scripts were changed as follows:
  - motd-news-config postinst: always remove the .wasremoved file in configure 
if found, regardless if /etc/default/motd-news was sed'ed or not, or if we are 
upgrading or on a first install
  - base-files postinst: guard the creation of .wasremoved with:
    - Only during an upgrade
    - Only if ubuntu-server is installed (via a dpkg -l check)

  [Test Case]
  * On the system under test, remove motd-news-config and ubuntu-server if they 
are installed, and keep base-files from the update pocket. Something like this:
  sudo apt update && sudo apt dist-upgrade -y
  sudo apt purge motd-news-config ubuntu-server
  apt-cache policy base-files <-- to verify it's from updates

  * In this scenario, you should have no /etc/default/motd* files:
  $ ll /etc/default/motd*
  ls: cannot access '/etc/default/motd*': No such file or directory

  * reinstall base-files:
  sudo apt install --reinstall base-files

  * Before this SRU, this would create /etc/default/motd-news.wasremoved:
  $ ll /etc/default/motd*
  -rw-r--r-- 1 root root 0 Sep 16 20:24 /etc/default/motd-news.wasremoved

  With the package from

[Touch-packages] [Bug 1895894] [NEW] Xorg freeze

2020-09-16 Thread Abdeldjalil Sefouhi

Public bug reported:

Hello team, I'm using chromium, evrything is working well, but sometimes
the audio is working well but everything is freezes, i can't use
anything, but the audio is still working, I can't fix it except rebbot
the system, it's happens a lot recently, i hope you can help me, Thank
you.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 16 22:07:54 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Continuously
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
 NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company GK106GLM [Quadro K2100M] [103c:2254]
InstallationDate: Installed on 2020-07-09 (69 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Hewlett-Packard HP ZBook 15 G2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=162424dc-b362-4e3a-8b36-d0389c6bbfee ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/23/2015
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M70 Ver. 01.12
dmi.board.name: 2253
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 03.10
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM70Ver.01.12:bd09/23/2015:svnHewlett-Packard:pnHPZBook15G2:pvrA3009DD10203:rvnHewlett-Packard:rn2253:rvrKBCVersion03.10:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP ZBook 15 G2
dmi.product.sku: N6L61UP#ABF
dmi.product.version: A3009DD10203
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal freeze 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/1895894

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello team, I'm using chromium, evrything is working well, but
  sometimes the audio is working well but everything is freezes, i can't
  use anything, but the audio is still working, I can't fix it except
  rebbot the system, it's happens a lot recently, i hope you can help
  me, Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 16 22:07:54 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GK106GLM [Quadro K2100M] [103c:2254]
  InstallationDate: Installed on 2020-07-09 (69 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Hewlett-Packard HP ZBook 15 G2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=162424dc-b362-4e3a-8b36-d0389c6bbfee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/23/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M70 Ver. 01.12
  dmi.board.name: 2253
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 03.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias:

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

Here's one Traceback about this issue:

Traceback (most recent call last):
  File "/usr/share/apport/dump_acpi_tables.py", line 59, in 
dump_acpi_tables('/sys/firmware/acpi/tables', sys.stdout)
  File "/usr/share/apport/dump_acpi_tables.py", line 55, in dump_acpi_tables
dump_acpi_table(pathname, tablename, out)
  File "/usr/share/apport/dump_acpi_tables.py", line 11, in dump_acpi_table
f = open(filename, 'rb')
PermissionError: [Errno 13] Permission denied: '/sys/firmware/acpi/tables/SSDT4'

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

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

Status in apport package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1895302] Re: groovy debootstrap leaves /e/d/motd-news.wasremoved around

** Description changed:

  [Impact]
  A fresh install of base-files, like done when using debootstrap, using the 
base-files from the -updates repository (in the case of ubuntu stable 
releases), will leave an empty /etc/default/motd-news.wasremoved file. This 
file is an artifact of the mechanism used to handle a corner case in the 
previous SRU where it would signal the motd-news-config package to install 
/etc/default/motd-news with ENABLED=0. See testcases (h) and (i) in the 
previous base-files SRU at 
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888575 for details. 
In test case (i) it was acked that the empty .wasremoved file was lying around, 
but its impact was deemed not relevant (see [other info] item (a)).
  
  Another case where /etc/default/motd-news.wasremoved would be created
  when it shouldn't be is when you have just base-files installed (and no
  ubuntu-server or motd-news-config) and did a reinstall of base-files, or
  an upgrade. It would again touch /etc/default/motd-news.wasremoved.
  
  The consequence of having /etc/default/motd-news.wasremoved when it's
  unintended is that a follow-up install of ubuntu-server, or motd-news-
  config for that matter, will install /etc/default/motd-news with
  ENABLED=0 instead of ENABLED=1.
  
  This was the case of the groovy debootstrap which resulted in this bug
  being filed. While debootstrap won't mix multiple repositories (like
  release with updates), and thus this isn't easily a problem in released
  versions of ubuntu, the groovy case was the one that was doing a fresh
  install of base-files with the buggy touch /etc/default/motd-
  news.wasremoved, and a subsequent install of ubuntu-server left motd-
  news disabled in groovy images produced by such a method (debootstrap).
  
  These are the scenarios I was able to come up with in which a stable
  release could be affected by this bug:
  
  a) debootstrap with release and updates pocket enabled
  There are no config options that I'm aware of that would tell debootstrap to 
use multiple pockets when creating a chroot, but let's say it was done by 
hacking the script or something else. It would then be the same case as groovy 
until this fix: subsequent installations of ubuntu-server or motd-news-config 
would default to having motd-news disabled
  
  b) A system that has just base-files from the previous SRU installed,
  and no ubuntu-server and no motd-news-config. If base-files were updated
  again and without the fix presented here (let's say, another SRU instead
  of this one), it would create /etc/default/motd-news.wasremoved, and
  again, a subsequent install of ubuntu-server or motd-news-config would
  install motd-news in a disabled state
  
  c) Any other case where the postinst script of base-files is run again
  without the fix presented here, and when there is no /etc/default/motd-
  news{,.dpkg*} file present.
  
  To avoid creating /etc/default/motd-news.wasremoved when we shouldn't, the 
maintainer scripts were changed as follows:
  - motd-news-config postinst: always remove the .wasremoved file in configure 
if found, regardless if /etc/default/motd-news was sed'ed or not, or if we are 
upgrading or on a first install
  - base-files postinst: guard the creation of .wasremoved with:
    - Only during an upgrade
    - Only if ubuntu-server is installed (via a dpkg -l check)
  
  [Test Case]
  * On the system under test, remove motd-news-config and ubuntu-server if they 
are installed, and keep base-files from the update pocket. Something like this:
  sudo apt update && sudo apt dist-upgrade -y
  sudo apt purge motd-news-config ubuntu-server
  apt-cache policy base-files <-- to verify it's from updates
  
  * In this scenario, you should have no /etc/default/motd* files:
  $ ll /etc/default/motd*
  ls: cannot access '/etc/default/motd*': No such file or directory
  
  * reinstall base-files:
  sudo apt install --reinstall base-files
  
  * Before this SRU, this would create /etc/default/motd-news.wasremoved:
  $ ll /etc/default/motd*
  -rw-r--r-- 1 root root 0 Sep 16 20:24 /etc/default/motd-news.wasremoved
  
  With the package from proposed for this SRU installed, no such file is 
created:
  $ ll /etc/default/motd*
  ls: cannot access '/etc/default/motd*': No such file or directory
  
  [Regression Potential]
  This SRU is further changing maintainer scripts, to address an issue in the 
previous maintainer script. Should there be new regressions or new issues, it 
might get harder and harder to fix them.
  
  I did wonder about the `dpkg -l` call in base-files' postinst. I worried
  about locks, or pre-dependencies, but dpkg was already being used in
  this script, although not with -l (list), just a version comparison. But
  at least it's already installed.
  
  My other worry was with the dpkg -l output and which flags I should
  check to determine if ubuntu-server was installed. "^ii" doesn't work,
  because ubuntu-server might be being upgraded in the

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

2020-09-16 Thread Cody Shepherd

** Description changed:

  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.
  
  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config
  
  Care must be taken to preserve a changed /etc/default/motd-news when the
  upgrade installs the new motd-news-config package. For example, on a
  server that has set ENABLED=0 in /etc/default/motd-news and upgrades to
  the new base-files and ubuntu-server, and gets the new motd-config-news
  package, ENABLED=0 must remain set.
  
  [Test Case]
  a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains, motd-news remains enabled
  
  b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains with the original modification
  
  c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
  apt install base-files
  - upgrades base-files
  - removes /e/d/motd-news
  - motd-news is disabled
  
  d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
  apt install base-files
  - upgrades base-files
  - /e/d/motd-news gets renamed to backup
  - motd-news is disabled
  
  e) removing motd-news-config will also remove ubuntu-server (since it's
  a depends, and not a recommends)
  
  f) upgrading just ubuntu-server should pull motd-news-config in, and
  force-upgrade base-files
  
  g) Removing motd-news-server leaves /e/d/motd-news around; purging motd-
  news-server removes the /e/d/motd-news config file
  
  h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
  - apt install base-files
  - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
  - /e/d/motd-news is installed with ENABLED=0
  
  i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news
  - apt install base-files
  - base-files is upgraded
  - no /e/d/motd-news is installed, motd-news remains disabled
  
  j) Perform a release upgrade from the previous ubuntu release to the one
  being tested while having ubuntu-server NOT installed (or use a desktop
  install). At the end, motd-news should be disabled. Verify with:
  
  $ sudo /etc/update-motd.d/50-motd-news --force
  $ (no output)
+ 
+ k) Test that supporting changes for xenial are in place:
+ 
+   i) verify grub-legacy-ec2 is not in the xenial server seed
+   ii) verify that the rootfs manifest built from the ubuntu-cpc project 
contains the ubuntu-server package
+   iii) verify that images built from the ubuntu-cpc project which purge 
grub-legacy-ec2 have retained ubuntu-server
  
  [Regression Potential]
  This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
  a) /e/d/motd-news config was changed while it belonged to base-files. For 
example, an user could have set ENABLED=0. We need to transfer that change to 
the motd-news-config package when it is installed, otherwise this SRU would 
jsut re-enabled motd-news. This is handled in d/motd-news-config.postinst's 
configure case.
  
  b) /e/d/motd-news config file was *removed* while it belonged to base-files. 
In such a case, a normal upgrade of the package (base-files in this example) 
would not reinstate the file. Much less this upgrade here, which has an 
explicit rm_conffile maintscript-helper for it. But the motd-news-config 
package that could be installed in the transaction would place the default 
config file back, and the default is ENABLED=1. Thus, a system that had 
motd-news disabled via removing the config file would now have it re-enabled 
after the upgrade.
  This was trickier to handle, and we do it in base-files's postinst and 
motd-news-config's  postinst. The drawback is that in one scenario, where just 
base-files is upgraded and /e/d/motd-news was manually removed by the user, 
there will be a /e/d/motd-news.wasremoved leftover empty file (see "other info" 
below for details).
  
  In general, the regression risks here are:
  - have motd-news enabled again on a system where it was previously disabled. 
We tried to envision two ways it would have been disabled (set ENABLED=0, and 
remove the config file). There are probably others
  - differences

[Touch-packages] [Bug 1895302] Re: groovy debootstrap leaves /e/d/motd-news.wasremoved around

** Description changed:

  [Impact]
  A fresh install of base-files, like done when using debootstrap, using the 
base-files from the -updates repository (in the case of ubuntu stable 
releases), will leave an empty /etc/default/motd-news.wasremoved file. This 
file is an artifact of the mechanism used to handle a corner case in the 
previous SRU where it would signal the motd-news-config package to install 
/etc/default/motd-news with ENABLED=0. See testcases (h) and (i) in the 
previous base-files SRU at 
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888575 for details. 
In test case (i) it was acked that the empty .wasremoved file was lying around, 
but its impact was deemed not relevant (see [other info] item (a)).
  
  Another case where /etc/default/motd-news.wasremoved would be created
  when it shouldn't be is when you have just base-files installed (and no
  ubuntu-server or motd-news-config) and did a reinstall of base-files, or
  an upgrade. It would again touch /etc/default/motd-news.wasremoved.
  
  The consequence of having /etc/default/motd-news.wasremoved when it's
  unintended is that a follow-up install of ubuntu-server, or motd-news-
  config for that matter, will install /etc/default/motd-news with
  ENABLED=0 instead of ENABLED=1.
  
  This was the case of the groovy debootstrap which resulted in this bug
  being filed. While debootstrap won't mix multiple repositories (like
  release with updates), and thus this isn't easily a problem in released
  versions of ubuntu, the groovy case was the one that was doing a fresh
  install of base-files with the buggy touch /etc/default/motd-
  news.wasremoved, and a subsequent install of ubuntu-server left motd-
  news disabled in groovy images produced by such a method (debootstrap).
  
  These are the scenarios I was able to come up with in which a stable
  release could be affected by this bug:
  
  a) debootstrap with release and updates pocket enabled
  There are no config options that I'm aware of that would tell debootstrap to 
use multiple pockets when creating a chroot, but let's say it was done by 
hacking the script or something else. It would then be the same case as groovy 
until this fix: subsequent installations of ubuntu-server or motd-news-config 
would default to having motd-news disabled
  
  b) A system that has just base-files from the previous SRU installed,
  and no ubuntu-server and no motd-news-config. If base-files were updated
  again and without the fix presented here (let's say, another SRU instead
  of this one), it would create /etc/default/motd-news.wasremoved, and
  again, a subsequent install of ubuntu-server or motd-news-config would
  install motd-news in a disabled state
  
  c) Any other case where the postinst script of base-files is run again
  without the fix presented here, and when there is no /etc/default/motd-
  news{,.dpkg*} file present.
  
  To avoid creating /etc/default/motd-news.wasremoved when we shouldn't, the 
maintainer scripts were changed as follows:
  - motd-news-config postinst: always remove the .wasremoved file in configure 
if found, regardless if /etc/default/motd-news was sed'ed or not, or if we are 
upgrading or on a first install
  - base-files postinst: guard the creation of .wasremoved with:
    - Only during an upgrade
    - Only if ubuntu-server is installed (via a dpkg -l check)
  
  [Test Case]
  * On the system under test, remove motd-news-config and ubuntu-server if they 
are installed, and keep base-files from the update pocket. Something like this:
- sudo apt update
+ sudo apt update && sudo apt dist-upgrade -y
  sudo apt purge motd-news-config ubuntu-server
  apt-cache policy base-files <-- to verify it's from updates
  
  * In this scenario, you should have no /etc/default/motd* files:
  $ ll /etc/default/motd*
  ls: cannot access '/etc/default/motd*': No such file or directory
  
  * reinstall base-files:
  sudo apt install --reinstall base-files
  
  * Before this SRU, this would create /etc/default/motd-news.wasremoved:
  $ ll /etc/default/motd*
  -rw-r--r-- 1 root root 0 Sep 16 20:24 /etc/default/motd-news.wasremoved
  
  With the package from proposed for this SRU installed, no such file is 
created:
  $ ll /etc/default/motd*
  ls: cannot access '/etc/default/motd*': No such file or directory
  
  [Regression Potential]
  This SRU is further changing maintainer scripts, to address an issue in the 
previous maintainer script. Should there be new regressions or new issues, it 
might get harder and harder to fix them.
  
  I did wonder about the `dpkg -l` call in base-files' postinst. I worried
  about locks, or pre-dependencies, but dpkg was already being used in
  this script, although not with -l (list), just a version comparison. But
  at least it's already installed.
  
  My other worry was with the dpkg -l output and which flags I should
  check to determine if ubuntu-server was installed. "^ii" doesn't work,
  because ubuntu-server might be being

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

2020-09-16 Thread Steve Langasek

** Also affects: livecd-rootfs (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: livecd-rootfs (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: livecd-rootfs (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: livecd-rootfs (Ubuntu Xenial)
   Status: Invalid => Triaged

** Changed in: livecd-rootfs (Ubuntu Focal)
   Status: New => Invalid

** Changed in: livecd-rootfs (Ubuntu Groovy)
   Status: New => Invalid

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

Title:
  Split motd-news config into a new package

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1895302] Re: groovy debootstrap leaves /e/d/motd-news.wasremoved around

** Description changed:

  [Impact]
  A fresh install of base-files, like done when using debootstrap, using the 
base-files from the -updates repository (in the case of ubuntu stable 
releases), will leave an empty /etc/default/motd-news.wasremoved file. This 
file is an artifact of the mechanism used to handle a corner case in the 
previous SRU where it would signal the motd-news-config package to install 
/etc/default/motd-news with ENABLED=0. See testcases (h) and (i) in the 
previous base-files SRU at 
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888575 for details. 
In test case (i) it was acked that the empty .wasremoved file was lying around, 
but its impact was deemed not relevant (see [other info] item (a)).
  
  Another case where /etc/default/motd-news.wasremoved would be created
  when it shouldn't be is when you have just base-files installed (and no
  ubuntu-server or motd-news-config) and did a reinstall of base-files, or
  an upgrade. It would again touch /etc/default/motd-news.wasremoved.
  
  The consequence of having /etc/default/motd-news.wasremoved when it's
  unintended is that a follow-up install of ubuntu-server, or motd-news-
  config for that matter, will install /etc/default/motd-news with
  ENABLED=0 instead of ENABLED=1.
  
  This was the case of the groovy debootstrap which resulted in this bug
  being filed. While debootstrap won't mix multiple repositories (like
  release with updates), and thus this isn't easily a problem in released
  versions of ubuntu, the groovy case was the one that was doing a fresh
  install of base-files with the buggy touch /etc/default/motd-
  news.wasremoved, and a subsequent install of ubuntu-server left motd-
  news disabled in groovy images produced by such a method (debootstrap).
  
  These are the scenarios I was able to come up with in which a stable
  release could be affected by this bug:
  
  a) debootstrap with release and updates pocket enabled
  There are no config options that I'm aware of that would tell debootstrap to 
use multiple pockets when creating a chroot, but let's say it was done by 
hacking the script or something else. It would then be the same case as groovy 
until this fix: subsequent installations of ubuntu-server or motd-news-config 
would default to having motd-news disabled
  
  b) A system that has just base-files from the previous SRU installed,
  and no ubuntu-server and no motd-news-config. If base-files were updated
  again and without the fix presented here (let's say, another SRU instead
  of this one), it would create /etc/default/motd-news.wasremoved, and
  again, a subsequent install of ubuntu-server or motd-news-config would
  install motd-news in a disabled state
  
  c) Any other case where the postinst script of base-files is run again
  without the fix presented here, and when there is no /etc/default/motd-
  news{,.dpkg*} file present.
  
  To avoid creating /etc/default/motd-news.wasremoved when we shouldn't, the 
maintainer scripts were changed as follows:
  - motd-news-config postinst: always remove the .wasremoved file in configure 
if found, regardless if /etc/default/motd-news was sed'ed or not, or if we are 
upgrading or on a first install
  - base-files postinst: guard the creation of .wasremoved with:
    - Only during an upgrade
    - Only if ubuntu-server is installed (via a dpkg -l check)
  
  [Test Case]
  * On the system under test, remove motd-news-config and ubuntu-server if they 
are installed, and keep base-files from the update pocket. Something like this:
  sudo apt update
  sudo apt purge motd-news-config ubuntu-server
  apt-cache policy base-files <-- to verify it's from updates
  
  * In this scenario, you should have no /etc/default/motd* files:
  $ ll /etc/default/motd*
  ls: cannot access '/etc/default/motd*': No such file or directory
  
  * reinstall base-files:
  sudo apt install --reinstall base-files
  
  * Before this SRU, this would create /etc/default/motd-news.wasremoved:
  $ ll /etc/default/motd*
  -rw-r--r-- 1 root root 0 Sep 16 20:24 /etc/default/motd-news.wasremoved
  
  With the package from proposed for this SRU installed, no such file is 
created:
  $ ll /etc/default/motd*
  ls: cannot access '/etc/default/motd*': No such file or directory
  
+ [Regression Potential]
+ This SRU is further changing maintainer scripts, to address an issue in the 
previous maintainer script. Should there be new regressions or new issues, it 
might get harder and harder to fix them.
  
- [Regression Potential]
+ I did wonder about the `dpkg -l` call in base-files' postinst. I worried
+ about locks, or pre-dependencies, but dpkg was already being used in
+ this script, although not with -l (list), just a version comparison. But
+ at least it's already installed.
  
-  * discussion of how regressions are most likely to manifest as a result
- of this change.
- 
-  * It is assumed that any SRU candidate patch is well-tested before
-    upload and has a low overall

[Touch-packages] [Bug 1895302] Re: groovy debootstrap leaves /e/d/motd-news.wasremoved around

** Description changed:

  [Impact]
  A fresh install of base-files, like done when using debootstrap, using the 
base-files from the -updates repository (in the case of ubuntu stable 
releases), will leave an empty /etc/default/motd-news.wasremoved file. This 
file is an artifact of the mechanism used to handle a corner case in the 
previous SRU where it would signal the motd-news-config package to install 
/etc/default/motd-news with ENABLED=0. See testcases (h) and (i) in the 
previous base-files SRU at 
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888575 for details. 
In test case (i) it was acked that the empty .wasremoved file was lying around, 
but its impact was deemed not relevant (see [other info] item (a)).
  
  Another case where /etc/default/motd-news.wasremoved would be created
  when it shouldn't be is when you have just base-files installed (and no
  ubuntu-server or motd-news-config) and did a reinstall of base-files, or
  an upgrade. It would again touch /etc/default/motd-news.wasremoved.
  
  The consequence of having /etc/default/motd-news.wasremoved when it's
  unintended is that a follow-up install of ubuntu-server, or motd-news-
  config for that matter, will install /etc/default/motd-news with
  ENABLED=0 instead of ENABLED=1.
  
  This was the case of the groovy debootstrap which resulted in this bug
  being filed. While debootstrap won't mix multiple repositories (like
  release with updates), and thus this isn't easily a problem in released
  versions of ubuntu, the groovy case was the one that was doing a fresh
  install of base-files with the buggy touch /etc/default/motd-
  news.wasremoved, and a subsequent install of ubuntu-server left motd-
  news disabled in groovy images produced by such a method (debootstrap).
  
  These are the scenarios I was able to come up with in which a stable
  release could be affected by this bug:
  
  a) debootstrap with release and updates pocket enabled
  There are no config options that I'm aware of that would tell debootstrap to 
use multiple pockets when creating a chroot, but let's say it was done by 
hacking the script or something else. It would then be the same case as groovy 
until this fix: subsequent installations of ubuntu-server or motd-news-config 
would default to having motd-news disabled
  
  b) A system that has just base-files from the previous SRU installed,
  and no ubuntu-server and no motd-news-config. If base-files were updated
  again and without the fix presented here (let's say, another SRU instead
  of this one), it would create /etc/default/motd-news.wasremoved, and
  again, a subsequent install of ubuntu-server or motd-news-config would
  install motd-news in a disabled state
  
  c) Any other case where the postinst script of base-files is run again
  without the fix presented here, and when there is no /etc/default/motd-
  news{,.dpkg*} file present.
  
  To avoid creating /etc/default/motd-news.wasremoved when we shouldn't, the 
maintainer scripts were changed as follows:
  - motd-news-config postinst: always remove the .wasremoved file in configure 
if found, regardless if /etc/default/motd-news was sed'ed or not, or if we are 
upgrading or on a first install
  - base-files postinst: guard the creation of .wasremoved with:
-   - Only during an upgrade
-   - Only if ubuntu-server is installed (via a dpkg -l check)
- 
+   - Only during an upgrade
+   - Only if ubuntu-server is installed (via a dpkg -l check)
  
  [Test Case]
+ * On the system under test, remove motd-news-config and ubuntu-server if they 
are installed, and keep base-files from the update pocket. Something like this:
+ sudo apt update
+ sudo apt purge motd-news-config ubuntu-server
+ apt-cache policy base-files <-- to verify it's from updates
  
-  * detailed instructions how to reproduce the bug
+ * In this scenario, you should have no /etc/default/motd* files:
+ $ ll /etc/default/motd*
+ ls: cannot access '/etc/default/motd*': No such file or directory
  
-  * these should allow someone who is not familiar with the affected
-    package to reproduce the bug and verify that the updated package fixes
-    the problem.
+ * reinstall base-files:
+ sudo apt install --reinstall base-files
+ 
+ * Before this SRU, this would create /etc/default/motd-news.wasremoved:
+ $ ll /etc/default/motd*
+ -rw-r--r-- 1 root root 0 Sep 16 20:24 /etc/default/motd-news.wasremoved
+ 
+ With the package from proposed for this SRU installed, no such file is 
created:
+ $ ll /etc/default/motd*
+ ls: cannot access '/etc/default/motd*': No such file or directory
+ 
  
  [Regression Potential]
  
   * discussion of how regressions are most likely to manifest as a result
  of this change.
  
   * It is assumed that any SRU candidate patch is well-tested before
     upload and has a low overall risk of regression, but it's important
     to make the effort to think about what ''could'' happen in the
     event of a regression.
  
   * This both shows the SRU team

[Touch-packages] [Bug 1895302] Re: groovy debootstrap leaves /e/d/motd-news.wasremoved around

** Description changed:

  [Impact]
- A fresh install of base-files, like done when using debootstrap, using the 
base-files from the -updates repository (in the case of ubuntu stable 
releases), will leave an empty /etc/default/motd-news.wasremoved file. This 
file is an artifact of the mechanism used to handle a corner case in the 
previous SRU where it would signal the motd-news-config package to install 
/etc/default/motd-news with ENABLED=0. See testcases (h) and (i) in the 
previous base-files SRU at 
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888575 for details. 
In test case (i) it was acked that the empty .wasremoved file was lying around, 
but its impact was deemed low (see [other info] item (a)).
+ A fresh install of base-files, like done when using debootstrap, using the 
base-files from the -updates repository (in the case of ubuntu stable 
releases), will leave an empty /etc/default/motd-news.wasremoved file. This 
file is an artifact of the mechanism used to handle a corner case in the 
previous SRU where it would signal the motd-news-config package to install 
/etc/default/motd-news with ENABLED=0. See testcases (h) and (i) in the 
previous base-files SRU at 
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888575 for details. 
In test case (i) it was acked that the empty .wasremoved file was lying around, 
but its impact was deemed not relevant (see [other info] item (a)).
  
  Another case where /etc/default/motd-news.wasremoved would be created
  when it shouldn't be is when you have just base-files installed (and no
  ubuntu-server or motd-news-config) and did a reinstall of base-files, or
  an upgrade. It would again touch /etc/default/motd-news.wasremoved.
  
  The consequence of having /etc/default/motd-news.wasremoved when it's
  unintended is that a follow-up install of ubuntu-server, or motd-news-
  config for that matter, will install /etc/default/motd-news with
  ENABLED=0 instead of ENABLED=1.
  
  This was the case of the groovy debootstrap which resulted in this bug
  being filed. While debootstrap won't mix multiple repositories (like
- release with updates), and thus this isn't strictly a problem in
- released versions of ubuntu, the groovy case was the one that was doing
- a fresh install of base-files with the buggy touch /etc/default/motd-
+ release with updates), and thus this isn't easily a problem in released
+ versions of ubuntu, the groovy case was the one that was doing a fresh
+ install of base-files with the buggy touch /etc/default/motd-
  news.wasremoved, and a subsequent install of ubuntu-server left motd-
  news disabled in groovy images produced by such a method (debootstrap).
  
- For stable releases, the impact is lessened because debootstrap will
- grab the release pocket for its job, and base-files from that pocket, in
- all ubuntu releases other than groovy, does not have the code that
- creates /etc/default/motd-news.wasremoved.
- 
- There are two ways this can affect a stable release of ubuntu:
+ These are the scenarios I was able to come up with in which a stable
+ release could be affected by this bug:
  
  a) debootstrap with release and updates pocket enabled
- There are no config options that I'm aware of that would tell debootstrap to 
use multiple pockets when creating a chroot, but let's say it was done. In this 
case, it would be the same case as groovy was until this fix: subsequent 
installations of ubuntu-server or motd-news-config would default to having 
motd-news disabled
+ There are no config options that I'm aware of that would tell debootstrap to 
use multiple pockets when creating a chroot, but let's say it was done by 
hacking the script or something else. It would then be the same case as groovy 
until this fix: subsequent installations of ubuntu-server or motd-news-config 
would default to having motd-news disabled
  
  b) A system that has just base-files from the previous SRU installed,
  and no ubuntu-server and no motd-news-config. If base-files were updated
- again, and without the fix presented here, it would create /etc/default
- /motd-news.wasremoved, and again, a subsequent install of ubuntu-server
- or motd-news-config would install motd-news in a disabled state
+ again and without the fix presented here (let's say, another SRU instead
+ of this one), it would create /etc/default/motd-news.wasremoved, and
+ again, a subsequent install of ubuntu-server or motd-news-config would
+ install motd-news in a disabled state
  
  c) Any other case where the postinst script of base-files is run again
  without the fix presented here, and when there is no /etc/default/motd-
  news{,.dpkg*} file present.
+ 
+ To avoid creating /etc/default/motd-news.wasremoved when we shouldn't, the 
maintainer scripts were changed as follows:
+ - motd-news-config postinst: always remove the .wasremoved file in configure 
if found, regardless if /etc/default/motd-news was sed'ed or not, or if we are 
upgrading or on a

[Touch-packages] [Bug 1895302] Re: groovy debootstrap leaves /e/d/motd-news.wasremoved around

** Description changed:

  [Impact]
  A fresh install of base-files, like done when using debootstrap, using the 
base-files from the -updates repository (in the case of ubuntu stable 
releases), will leave an empty /etc/default/motd-news.wasremoved file. This 
file is an artifact of the mechanism used to handle a corner case in the 
previous SRU where it would signal the motd-news-config package to install 
/etc/default/motd-news with ENABLED=0. See testcases (h) and (i) in the 
previous base-files SRU at 
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888575 for details. 
In test case (i) it was acked that the empty .wasremoved file was lying around, 
but its impact was deemed low (see [other info] item (a)).
  
  Another case where /etc/default/motd-news.wasremoved would be created
  when it shouldn't be is when you have just base-files installed (and no
  ubuntu-server or motd-news-config) and did a reinstall of base-files, or
  an upgrade. It would again touch /etc/default/motd-news.wasremoved.
  
  The consequence of having /etc/default/motd-news.wasremoved when it's
  unintended is that a follow-up install of ubuntu-server, or motd-news-
  config for that matter, will install /etc/default/motd-news with
  ENABLED=0 instead of ENABLED=1.
  
  This was the case of the groovy debootstrap which resulted in this bug
  being filed. While debootstrap won't mix multiple repositories (like
  release with updates), and thus this isn't strictly a problem in
  released versions of ubuntu, the groovy case was the one that was doing
  a fresh install of base-files with the buggy touch /etc/default/motd-
  news.wasremoved, and a subsequent install of ubuntu-server left motd-
  news disabled in groovy images produced by such a method (debootstrap).
  
  For stable releases, the impact is lessened because debootstrap will
  grab the release pocket for its job, and base-files from that pocket, in
  all ubuntu releases other than groovy, does not have the code that
  creates /etc/default/motd-news.wasremoved.
  
- This would affect a stable release anytime the postinst script from
- base-files from the previous SRU is run and there are no /etc/default
- /motd-news{,.dpkg*} files present. This could be a system which just
- doesn't have ubuntu-server or motd-news-config installed, in which case
- creating the .wasremoved file is wrong. Or a system which has those
- packages installed, and the user erroneously, in an attempt to disable
- motd-news, removed /etc/default/motd-news, in which case it's correct to
- create /etc/default/motd-news.wasremoved.
+ There are two ways this can affect a stable release of ubuntu:
  
- If debootstrap is somehow coached into using the release and updates
- pocket, then the stable release it's bootstrapping would suffer from
- this bug in the same way that groovy did: base-files would be installed
- without ubuntu-server or motd-news-config, and an empty /etc/default
- /motd-news.wasremoved file would be creating, disabling motd-news in any
- future installation of motd-news-config or ubuntu-server.
+ a) debootstrap with release and updates pocket enabled
+ There are no config options that I'm aware of that would tell debootstrap to 
use multiple pockets when creating a chroot, but let's say it was done. In this 
case, it would be the same case as groovy was until this fix: subsequent 
installations of ubuntu-server or motd-news-config would default to having 
motd-news disabled
  
+ b) A system that has just base-files from the previous SRU installed,
+ and no ubuntu-server and no motd-news-config. If base-files were updated
+ again, and without the fix presented here, it would create /etc/default
+ /motd-news.wasremoved, and again, a subsequent install of ubuntu-server
+ or motd-news-config would install motd-news in a disabled state
+ 
+ c) Any other case where the postinst script of base-files is run again
+ without the fix presented here, and when there is no /etc/default/motd-
+ news{,.dpkg*} file present.
  
  [Test Case]
  
   * detailed instructions how to reproduce the bug
  
   * these should allow someone who is not familiar with the affected
     package to reproduce the bug and verify that the updated package fixes
     the problem.
  
  [Regression Potential]
  
   * discussion of how regressions are most likely to manifest as a result
  of this change.
  
   * It is assumed that any SRU candidate patch is well-tested before
     upload and has a low overall risk of regression, but it's important
     to make the effort to think about what ''could'' happen in the
     event of a regression.
  
   * This both shows the SRU team that the risks have been considered,
     and provides guidance to testers in regression-testing the SRU.
  
  [Other Info]
  
   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance
  
  [Original

[Touch-packages] [Bug 1889059] Re: [Ubuntu 20.04] zlib on s390x may produce incomplete raw (but not gzip/zlib) streams

This bug was fixed in the package zlib - 1:1.2.11.dfsg-2ubuntu2

---
zlib (1:1.2.11.dfsg-2ubuntu2) groovy; urgency=medium

  * Update d/patches/410.patch to current state. LP: #1882494, #1889059,
#1893170

 -- Michael Hudson-Doyle   Thu, 20 Aug 2020
11:52:59 +1200

** Changed in: zlib (Ubuntu Groovy)
   Status: New => Fix Released

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

Title:
  [Ubuntu 20.04] zlib on s390x may produce incomplete raw (but not
  gzip/zlib) streams

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Focal:
  New
Status in zlib source package in Groovy:
  Fix Released

Bug description:
  zlib on s390x may produce incomplete raw (but not gzip/zlib) streams

  ---uname output---
  Linux t35lp56.lnxne.boe 5.8.0-20200703.rc3.git0.52a479d42203.300.fc31.s390x 
#1 SMP Fri Jul 3 00:46:20 CEST 2020 s390x s390x s390x GNU/Linux
   
  Machine Type = z15 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Create a raw (negative windowBits value) stream with zlib. EOBS might be 
missing or truncated.


  This affects all distro levels that contain hardware acceleration
  (DFLTCC) patch. I've attached the preliminary fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889059/+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 1882494] Re: [UBUNTU 20.04] zlib not working on all s390x systems configurations

This bug was fixed in the package zlib - 1:1.2.11.dfsg-2ubuntu2

---
zlib (1:1.2.11.dfsg-2ubuntu2) groovy; urgency=medium

  * Update d/patches/410.patch to current state. LP: #1882494, #1889059,
#1893170

 -- Michael Hudson-Doyle   Thu, 20 Aug 2020
11:52:59 +1200

** Changed in: zlib (Ubuntu Groovy)
   Status: New => Fix Released

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

Title:
  [UBUNTU 20.04] zlib not working on all s390x systems configurations

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Eoan:
  Won't Fix
Status in zlib source package in Focal:
  New
Status in zlib source package in Groovy:
  Fix Released

Bug description:
  Pull request (https://github.com/madler/zlib/pull/410) and tagged
  https://github.com/iii-i/zlib/tree/dfltcc-20200511.

  The new code contains the following improvements:
  * Added support for switching between software and hardware compression.
  * Added --dfltcc configure flag (the old way of building it still works).

  Switching between software and hardware compression is not simply a
  nice-to-have feature, but is actually required by Java - that's why we
  are requesting an update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882494/+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 1798369] Re: Reinstall Ubuntu (with preserving existing data) shows error message due to "Could not get lock /target/var/cache/apt/archives/lock"

This bug was fixed in the package ubiquity - 20.10.10

---
ubiquity (20.10.10) groovy; urgency=medium

  [ Didier Roche ]
  [ Jean-Baptiste Lallement ]
  * AD integration for GTK UI.
  * bump KDE_SESSION_VERSION to 5 to fix xdg-open on Kubuntu (LP: #1890173)

  [ Brian Murray ]
  * Do not try to keep installed software when reinstalling Ubuntu as the
process was error prone (LP: 1152399) and did not provide a quailty
experience. (LP: #1798369)

 -- Jean-Baptiste Lallement   Tue,
15 Sep 2020 17:06:15 +0200

** Changed in: ubiquity (Ubuntu)
   Status: Won't Fix => Fix Released

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

Title:
  Reinstall Ubuntu (with preserving existing data) shows error message
  due to "Could not get lock /target/var/cache/apt/archives/lock"

Status in APT:
  New
Status in ubiquity:
  New
Status in apt package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Fix Released
Status in apt source package in Eoan:
  Invalid
Status in ubiquity source package in Eoan:
  Won't Fix

Bug description:
  When trying to reinstall an existing Ubuntu cosmic installation using
  latest 18.10 desktop images, the install shows an error dialog around
  the end of the installation with an "Error restoring installed
  applications". Looking at the syslog such a traceback can be seen:

  apt_pkg.Error: E:Could not get lock
  /target/var/cache/apt/archives/lock - open (11: Resource temporarily
  unavailable), E:Unable to lock directory
  /target/var/cache/apt/archives/

  After reproducing this on a live session, after chrooting into /target
  indeed any apt-get install operations result in the same lock-file
  error. The whole syslog of the reinstall attached to the bug.

  Test case:
   * Download latest cosmic image
   * Install cosmic on the whole disk (can be on a VM)
   * (optional) Boot into the system and leave a file in the home directory (to 
leave a trace, just in case)
   * Reboot and install cosmic using the first option in ubiquity: Reinstall 
Ubuntu
   * Finish configuration

  The install itself doesn't fail, but around the end of the
  installation process the error dialog appears. System is still
  bootable but left with old packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apt/+bug/1798369/+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 1893170] Re: [Ubuntu 20.10] zlib: DFLTCC compression level switching issues

This bug was fixed in the package zlib - 1:1.2.11.dfsg-2ubuntu2

---
zlib (1:1.2.11.dfsg-2ubuntu2) groovy; urgency=medium

  * Update d/patches/410.patch to current state. LP: #1882494, #1889059,
#1893170

 -- Michael Hudson-Doyle   Thu, 20 Aug 2020
11:52:59 +1200

** Changed in: zlib (Ubuntu Groovy)
   Status: New => Fix Released

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

Title:
  [Ubuntu 20.10] zlib: DFLTCC compression level switching issues

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Focal:
  New
Status in zlib source package in Groovy:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * This SRU fixes a combination of multiple issues:

   * zlib DFLTCC compression level switching can corrupt data because
  hardware and software compression states become desynchronized. (LP
  1893170)

   * Since zlib is not working on all s390x system configurations
  support for switching between software and hardware compression is
  required especially for Java. (LP 1882494)

   * zlib on s390x may produce incomplete raw streams (but not
  gzip/zlib). (LP 1889059)

  [Test Case]

   * Since especially DFLTCC requires a s390x generation z15 or LinuxONE
  III the tests need to be done by IBM.

   * IBM has a set of tests available, that exercise public zlib APIs by
  calling them in different sequences with different buffer sizes and
  flush modes.

  * Partially these come from the IBM z/OS team, who developed their own
  zlib support for the hardware accelerator, and partially they are
  developed by the IBM Linux team based on issues encountered during
  development as well as fuzzing.

  * IBM also uses the zlib-ng test-suite as well as squash and stress-
  ng.

   * Compress data using zlib/DFLTCC with different compression level
  and verify state and if data got corrupted or not. (LP 1893170)

   * On a system with patched zlib package, switch between hardware and
  software compression and use zlib via the java.util.zip package
  (http://java.sun.com/developer/technicalArticles/Programming/compression/).
  (LP 1882494)

  * On a z15 system with hardware acceleration compression (DFLTCC)
  enabled, create a raw (negative windowBits value) stream with zlib.
  Then check if EOBS is missing or truncated. (LP 1889059)

  [Regression Potential]

   * There is a certain risk for regressions with the modifications that
  are introduced by the four LP bugs.

   * In case the package fails entirely, it will have (in worst case) an
  impact on all zlib, gzip and DFLTCC compression/decompression
  functions, that are very wide spread (gzip, tar cfz, everything with
  zlib) in Linux and would virtually make the system unusable.

   * If potential issues are limited to hardware assisted compression
  (which is more likely, since these patches are mostly about hw
  assisted compression), then issues would be limited to systems that
  provide this feature (latest s390x generation only).

  * A switch back to software got introduced (by setting DFLTCC=0
  environment variable) that will help to mitigate a potential negative
  impact of the hw assisted compression.

   * Only the latest s390x generation (z15 and LinuxONE III) supports
  hardware assisted DFLTCC and is potentially affected.

   * A patched test package was made available and got successfully
  tested by IBM. All four bugs were finally considered as solved with
  zlib (1:1.2.11.dfsg-2ubuntu2~ppa2) available here:
  
https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+packages?field.name_filter=zlib

  __

  Description:   zlib: DFLTCC compression level switching issues
  Symptom:   Switching compression levels corrupts data
  Problem:   Hardware and software compression states become desynchronized.
  Solution:  Improve compression state synchronization. Since zlib project
     does not accept patches at the moment, the fix has been
     integrated into the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is 992a7afc3edfa511dff0650d1c545b11bf64e655.
  Reproduction:  Not possible with popular command line tools. The issues were
     discovered using example_call_fuzzer from:
     https://github.com/iii-i/zlib-ng/tree/fuzz/test/fuzz/

  This needs also be applied against 20.04 !

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1893170/+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 1895302] Re: groovy debootstrap leaves /e/d/motd-news.wasremoved around

** Description changed:

  [Impact]
+ A fresh install of base-files, like done when using debootstrap, using the 
base-files from the -updates repository (in the case of ubuntu stable 
releases), will leave an empty /etc/default/motd-news.wasremoved file. This 
file is an artifact of the mechanism used to handle a corner case in the 
previous SRU where it would signal the motd-news-config package to install 
/etc/default/motd-news with ENABLED=0. See testcases (h) and (i) in the 
previous base-files SRU at 
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888575 for details. 
In test case (i) it was acked that the empty .wasremoved file was lying around, 
but its impact was deemed low (see [other info] item (a)).
  
-  * An explanation of the effects of the bug on users and
+ Another case where /etc/default/motd-news.wasremoved would be created
+ when it shouldn't be is when you have just base-files installed (and no
+ ubuntu-server or motd-news-config) and did a reinstall of base-files, or
+ an upgrade. It would again touch /etc/default/motd-news.wasremoved.
  
-  * justification for backporting the fix to the stable release.
+ The consequence of having /etc/default/motd-news.wasremoved when it's
+ unintended is that a follow-up install of ubuntu-server, or motd-news-
+ config for that matter, will install /etc/default/motd-news with
+ ENABLED=0 instead of ENABLED=1.
  
-  * In addition, it is helpful, but not required, to include an
-explanation of how the upload fixes this bug.
+ This was the case of the groovy debootstrap which resulted in this bug
+ being filed. While debootstrap won't mix multiple repositories (like
+ release with updates), and thus this isn't strictly a problem in
+ released versions of ubuntu, the groovy case was the one that was doing
+ a fresh install of base-files with the buggy touch /etc/default/motd-
+ news.wasremoved, and a subsequent install of ubuntu-server left motd-
+ news disabled in groovy images produced by such a method (debootstrap).
+ 
+ For stable releases, the impact is lessened because debootstrap will
+ grab the release pocket for its job, and base-files from that pocket, in
+ all ubuntu releases other than groovy, does not have the code that
+ creates /etc/default/motd-news.wasremoved.
+ 
+ This would affect a stable release anytime the postinst script from
+ base-files from the previous SRU is run and there are no /etc/default
+ /motd-news{,.dpkg*} files present. This could be a system which just
+ doesn't have ubuntu-server or motd-news-config installed, in which case
+ creating the .wasremoved file is wrong. Or a system which has those
+ packages installed, and the user erroneously, in an attempt to disable
+ motd-news, removed /etc/default/motd-news, in which case it's correct to
+ create /etc/default/motd-news.wasremoved.
+ 
+ If debootstrap is somehow coached into using the release and updates
+ pocket, then the stable release it's bootstrapping would suffer from
+ this bug in the same way that groovy did: base-files would be installed
+ without ubuntu-server or motd-news-config, and an empty /etc/default
+ /motd-news.wasremoved file would be creating, disabling motd-news in any
+ future installation of motd-news-config or ubuntu-server.
+ 
  
  [Test Case]
  
-  * detailed instructions how to reproduce the bug
+  * detailed instructions how to reproduce the bug
  
-  * these should allow someone who is not familiar with the affected
-package to reproduce the bug and verify that the updated package fixes
-the problem.
+  * these should allow someone who is not familiar with the affected
+    package to reproduce the bug and verify that the updated package fixes
+    the problem.
  
  [Regression Potential]
  
-  * discussion of how regressions are most likely to manifest as a result
+  * discussion of how regressions are most likely to manifest as a result
  of this change.
  
-  * It is assumed that any SRU candidate patch is well-tested before
-upload and has a low overall risk of regression, but it's important
-to make the effort to think about what ''could'' happen in the
-event of a regression.
+  * It is assumed that any SRU candidate patch is well-tested before
+    upload and has a low overall risk of regression, but it's important
+    to make the effort to think about what ''could'' happen in the
+    event of a regression.
  
-  * This both shows the SRU team that the risks have been considered,
-and provides guidance to testers in regression-testing the SRU.
+  * This both shows the SRU team that the risks have been considered,
+    and provides guidance to testers in regression-testing the SRU.
  
  [Other Info]
-  
-  * Anything else you think is useful to include
-  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
-  * and address these questions in advance
  
+  * Anything else you think is useful to include
+  * Anticipate questions from users, SRU, +1

[Touch-packages] [Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default

FYI: builds complete - Running the test builds of network-
manager_1.26.2-1ubuntu1.dsc in groovy against the proposed and the PPA
version.

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

Title:
  [2.82 regression] router announcements have 'forever' lifetime by
  default

Status in dnsmasq package in Ubuntu:
  Triaged

Bug description:
  The default lifetime was changed to 1 day in 2.82 in the change
  corresponding to this changelog entry:

  Change default lease time for DHCPv6 to one day.

  Fine, but the same commit also did this:

Alter calculation of preferred and valid times in router
advertisements, so that these do not have a floor applied
of the lease time in the dhcp-range if this is not explicitly
specified and is merely the default.

  And that change is buggy and causes advertisements to have infinite
  lifetime, when you are using the default.

  See this thread

http://lists.thekelleys.org.uk/pipermail/dnsmasq-
  discuss/2020q3/014341.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+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 1895302] Re: groovy debootstrap leaves /e/d/motd-news.wasremoved around

** Description changed:

+ [Impact]
+ 
+  * An explanation of the effects of the bug on users and
+ 
+  * justification for backporting the fix to the stable release.
+ 
+  * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+ 
+ [Test Case]
+ 
+  * detailed instructions how to reproduce the bug
+ 
+  * these should allow someone who is not familiar with the affected
+package to reproduce the bug and verify that the updated package fixes
+the problem.
+ 
+ [Regression Potential]
+ 
+  * discussion of how regressions are most likely to manifest as a result
+ of this change.
+ 
+  * It is assumed that any SRU candidate patch is well-tested before
+upload and has a low overall risk of regression, but it's important
+to make the effort to think about what ''could'' happen in the
+event of a regression.
+ 
+  * This both shows the SRU team that the risks have been considered,
+and provides guidance to testers in regression-testing the SRU.
+ 
+ [Other Info]
+  
+  * Anything else you think is useful to include
+  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
+  * and address these questions in advance
+ 
+ 
+ [Original Description]
+ 
  When debootstrapping groovy, we see an empty /etc/default/motd-
  news.wasremoved file.
  
  - groovy: base-files 11ubuntu12
  -rw-r--r-- 1 root root 0 set 11 10:20 /etc/default/motd-news.wasremoved
  
  If motd-news-config is later installed, maybe via ubuntu-server, then
  the presence of this file will disable motd-news by default, which is
  unintended as it's meant to be enabled on a server.

** Also affects: base-files (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: base-files (Ubuntu Focal)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

** Changed in: base-files (Ubuntu Focal)
   Status: New => In Progress

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

Title:
  groovy debootstrap leaves /e/d/motd-news.wasremoved around

Status in base-files package in Ubuntu:
  In Progress
Status in base-files source package in Focal:
  In Progress

Bug description:
  [Impact]

   * An explanation of the effects of the bug on users and

   * justification for backporting the fix to the stable release.

   * In addition, it is helpful, but not required, to include an
 explanation of how the upload fixes this bug.

  [Test Case]

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  [Regression Potential]

   * discussion of how regressions are most likely to manifest as a
  result of this change.

   * It is assumed that any SRU candidate patch is well-tested before
 upload and has a low overall risk of regression, but it's important
 to make the effort to think about what ''could'' happen in the
 event of a regression.

   * This both shows the SRU team that the risks have been considered,
 and provides guidance to testers in regression-testing the SRU.

  [Other Info]
   
   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance


  [Original Description]

  When debootstrapping groovy, we see an empty /etc/default/motd-
  news.wasremoved file.

  - groovy: base-files 11ubuntu12
  -rw-r--r-- 1 root root 0 set 11 10:20 /etc/default/motd-news.wasremoved

  If motd-news-config is later installed, maybe via ubuntu-server, then
  the presence of this file will disable motd-news by default, which is
  unintended as it's meant to be enabled on a server.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1895302/+subscriptions

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

[Touch-packages] [Bug 1892643] Re: [SRU] Update libgweather to 3.36.1

2020-09-16 Thread Amr Ibrahim

Please sponsor libgweather 3.36.1 in my PPA to Focal:

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

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

Title:
  [SRU] Update libgweather to 3.36.1

Status in libgweather:
  Unknown
Status in libgweather package in Ubuntu:
  New
Status in libgweather package in Debian:
  Unknown

Bug description:
  [Impact]

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

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

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

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

  
  [Test case]

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

  
  [Regression potential]

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

  
  [Other]

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

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

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

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

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

[Touch-packages] [Bug 1892643] Re: [SRU] Update libgweather to 3.36.1

2020-09-16 Thread Amr Ibrahim

** Description changed:

- Please update libgweather to 3.36.1 to fix the unavailability of current
- temperature in some locations.
+ [Impact]
+ 
+ libgweather 3.36.1 is a bug-fix release as part of GNOME 3.36.
  
  https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS
  
- ==
- Version 3.36.1
- ==
+ This version works around the unavailability of the NOAA weather
+ services by using very short-term forecasts as current weather
+ conditions.
  
- This version works around the unavailability of the NOAA weather services
- by using very short-term forecasts as current weather conditions.
+ Sometimes the current weather is not available because the NOAA weather
+ servers aren't working correctly. Version 3.36.1 fixes the
+ unavailability of current temperature in some locations.
+ 
+ 
+ [Test case]
+ 
+ Make sure that gnome-weather is still working properly and the weather
+ in gnome-shell is shown when gnome-weather is installed.
+ 
+ 
+ [Regression potential]
+ 
+ The regression potential is low since the changes in version 3.36.1 are
+ small.
+ 
+ 
+ [Other]
+ 
+ libgweather 3.36.1 has been successfully built as a no-change backport
+ from Groovy to Focal in my PPA and runs fine:
+ 
+ 
https://launchpad.net/~amribrahim1987/+archive/ubuntu/ppa/+packages?field.name_filter=libgweather_filter=published_filter=
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgweather-3-16 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 23 19:05:21 2020
  InstallationDate: Installed on 2020-04-26 (119 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libgweather
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  [SRU] Update libgweather to 3.36.1

Status in libgweather:
  Unknown
Status in libgweather package in Ubuntu:
  New
Status in libgweather package in Debian:
  Unknown

Bug description:
  [Impact]

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

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

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

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

  
  [Test case]

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

  
  [Regression potential]

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

  
  [Other]

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

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

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

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

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

[Touch-packages] [Bug 1893899] Re: update alsa/audio related infomation collection code in apport

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

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

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

Title:
  update alsa/audio related infomation collection code in apport

Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  what need to change

  1. try to use /usr/sbin/alsa-info before try 
/usr/share/alsa-base/alsa-info.sh (weird for me that two copy of alsa-info 
co-exists, but anyway)
  2. add pa-info (exist after focal)
  3. add ucm2 directory. (exist after focal)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893899/+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 1895294] Re: Fix Raccoon vulnerability (CVE-2020-1968)

2020-09-16 Thread Marc Deslauriers

It's not feasible to stop the affected ciphers from re-using secrets,
it's in the specification.

Removing the ciphers is what was done in later releases of openssl,
including the 1.0.2w version that was released specifically to address
this issue:

https://www.openssl.org/news/secadv/20200909.txt

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

Title:
  Fix Raccoon vulnerability (CVE-2020-1968)

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Xenial:
  Fix Released

Bug description:
  Xenial's current OpenSSL (1.0.2g-1ubuntu4.16) seems to not have been
  patched yet against the Raccoon Attack (CVE-2020-1968):

  - https://www.openssl.org/news/secadv/20200909.txt
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1968
  - https://raccoon-attack.com/

  Ubuntu's CVE tracker still lists this as NEEDED for Xenial:

  - https://people.canonical.com/~ubuntu-security/cve/2020/CVE-2020-1968.html
  - https://people.canonical.com/~ubuntu-security/cve/pkg/openssl.html

  Other supported Ubuntu releases use versions of OpenSSL that are not
  affected.

  Indeed:

    $ apt-cache policy openssl
    openssl:
  Installed: 1.0.2g-1ubuntu4.16

    $ apt-get changelog openssl | grep CVE-2020-1968 || echo "Not patched"
    Not patched

  What is the status?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1895294/+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 1895294] Re: Fix Raccoon vulnerability (CVE-2020-1968)

2020-09-16 Thread Nils Toedtmann

Thank you very much for fixing swiftly!

Please forgive me for pointing this out though:

I note that rather than stopping the affected cipher suites from re-
using secrets across connections, you chose to declare the suites as
weak and disabled them altogether.

I appreciate that this is an elegant way to close this vulnerability, in
particular in the absence of an upstream patch.

However, this solution introduces the risk that when trying to establish
a connection with some legacy client or server, they can no longer agree
on a shared cipher, and the TLS handshake fails. That is not in the
spirit of a LTS, which is often elected and used precisely because it
makes it easier to to support legacy products reliably.

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

Title:
  Fix Raccoon vulnerability (CVE-2020-1968)

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Xenial:
  Fix Released

Bug description:
  Xenial's current OpenSSL (1.0.2g-1ubuntu4.16) seems to not have been
  patched yet against the Raccoon Attack (CVE-2020-1968):

  - https://www.openssl.org/news/secadv/20200909.txt
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1968
  - https://raccoon-attack.com/

  Ubuntu's CVE tracker still lists this as NEEDED for Xenial:

  - https://people.canonical.com/~ubuntu-security/cve/2020/CVE-2020-1968.html
  - https://people.canonical.com/~ubuntu-security/cve/pkg/openssl.html

  Other supported Ubuntu releases use versions of OpenSSL that are not
  affected.

  Indeed:

    $ apt-cache policy openssl
    openssl:
  Installed: 1.0.2g-1ubuntu4.16

    $ apt-get changelog openssl | grep CVE-2020-1968 || echo "Not patched"
    Not patched

  What is the status?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1895294/+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 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

2020-09-16 Thread Kelsey Margarete Skunberg

Thank you @christian. I marked the Xenial test cases under this same
bug, though can open a new bug and update the hint bug references if
needed. I'll check back to see when/if ddstreet/rbalint have a chance to
review.

For the test results you're posting, I was wondering where you're
getting those results from and an explanation of the results?

xenial
  amd64
boot-and-services (F 45% f 0% S 0% B 5% => P 50%/) .FF...BFF.F.
boot-smoke (F 80% f 0% S 0% B 5% => P 15%/) F.FF..BF
systemd-fsckd (F 65% f 0% S 0% B 5% => P 30%/) FF.FFF.F..B.FF.F
  ppc64el
no failures
  s390x
no failures

In the above, what does the F, f, B, & . stand for? Am I correct to
assume the P *% is the pass rate? F for fail?

Thank you!

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in build-essential package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid
Status in iputils package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Invalid
Status in ntpsec package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Invalid
Status in linux-meta source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in build-essential source package in Focal:
  Confirmed
Status in linux-meta source package in Focal:
  New
Status in qemu source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in util-linux source package in Focal:
  Confirmed

Bug description:
  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services  (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-smoke (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  logind (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  storage(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  upstream   (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFBFF.B.F.F..FFBF
  udev   (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  systemd-fsckd  (F 37% S  0% B 10% => P 50%/) 
BFFFB.FF...FB.F..B.
  root-unittests (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
ppc64el
  tests-in-lxd   (F 25% S  0% B  0% => P 75%/) 
FFFFF.F.
  systemd-fsckd  (F 35% S  0% B  0% => P 65%/) 
FFF...FFFFF.F..F
  root-unittests (F  2% S  0% B  0% => P 97%/) 
..F.
s390x
  tests-in-lxd   (F 52% S  0% B  0% => P 47%/) 
FFF.FFF.FF....F.
  timedated  (F  2% S  0% B  0% => P 97%/) 
...F
  upstream   (F 17% S  0% B  0% => P 82%/) 
.F..F.F.FFF...F.
  systemd-fsckd  (F 32% S  0% B  0% => P 67%/) 
FFF..FF..F.FF..F
  root-unittests (F 10% S  0% B  0% => P 90%/) 
FFF...F.
arm64
  tests-in-lxd   (F 40% S  0% B  2% => P 57%/) 
F.B...FFF.FF..F..F.FFF.F
  logind (F  2% S  0% B  2% => P 95%/) 
..B...F.
  upstream   (F 22% S  0% B  2% => P 75%/) 
...F.FB.F.F.F..FFF.F
  root-unittests (F 12% S  0% B  2% => P 85%/) 
..B.F...F.FF...F

  (I'm sure LP will make this

[Touch-packages] [Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

2020-09-16 Thread Iain Lane

I've uploaded, thanks.

But the regression potential section needs improving, "None" isn't
enough. Please improve it to discuss where people should focus their
attention / testing.

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

Title:
  The network manager does not check the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  Invalid
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Focal:
  In Progress

Bug description:
  [Impact]

   In some cases, the wow is not configured and the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
  management of wake-on-LAN in NetworkManager).

   The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE 
bit.
   But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
   So, the management of wake-on-LAN still is done by NetworkManager.

  [Test Case]

   On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
   Step 1. Enter suspend (s2idle)
   Setp 2. Resume from suspend

   After resume from suspend, the Wi-Fi functiall still is normal.

   You can download the kernel and linux-firmware that backport the Qucalcomm's 
dirver fro focal from below link:
   https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633

  [Regression Potential]

   * No potential regressions.

  [Other Info]
   
   * None

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1891632/+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 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

2020-09-16 Thread Iain Lane

** Also affects: oem-priority/focal
   Importance: Undecided
   Status: New

** Changed in: oem-priority/focal
   Status: New => Invalid

** Also affects: network-manager (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Changed in: network-manager (Ubuntu Focal)
   Status: New => In Progress

** Changed in: network-manager (Ubuntu Focal)
 Assignee: (unassigned) => Leon Liao (lihow731)

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

Title:
  The network manager does not check the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  Invalid
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Focal:
  In Progress

Bug description:
  [Impact]

   In some cases, the wow is not configured and the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
  management of wake-on-LAN in NetworkManager).

   The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE 
bit.
   But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
   So, the management of wake-on-LAN still is done by NetworkManager.

  [Test Case]

   On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
   Step 1. Enter suspend (s2idle)
   Setp 2. Resume from suspend

   After resume from suspend, the Wi-Fi functiall still is normal.

   You can download the kernel and linux-firmware that backport the Qucalcomm's 
dirver fro focal from below link:
   https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633

  [Regression Potential]

   * No potential regressions.

  [Other Info]
   
   * None

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1891632/+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 1761096] Re: dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed

2020-09-16 Thread Sergio Durigan Junior

Verifying that the bug is fixed.

First, reproducing the bug.  After firing up the container, while
running "apt install squid dnsmasq -y", I see:

# apt install squid dnsmasq -y
...
Setting up dnsmasq (2.75-1ubuntu0.16.04.5) ...
Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl 
status dnsmasq.service" and "journalctl -xe" for details.
invoke-rc.d: initscript dnsmasq, action "start" failed.
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
   Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: 
enabled)
  Drop-In: /run/systemd/generator/dnsmasq.service.d
   └─50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf
   Active: failed (Result: timeout) since Wed 2020-09-16 15:43:01 UTC; 11ms ago
  Process: 1565 ExecStartPost=/etc/init.d/dnsmasq systemd-start-resolvconf 
(code=killed, signal=TERM)
  Process: 1554 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, 
status=0/SUCCESS)
  Process: 1553 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, 
status=0/SUCCESS)
 Main PID: 1564 (code=exited, status=0/SUCCESS)

Sep 16 15:41:31 squid-bug1761096 dnsmasq[1564]: started, version 2.75 cachesize 
150
Sep 16 15:41:31 squid-bug1761096 dnsmasq[1564]: compile time options: IPv6 
GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC 
loop-detect inotify
Sep 16 15:41:31 squid-bug1761096 dnsmasq[1564]: DNS service limited to local 
subnets
Sep 16 15:41:31 squid-bug1761096 dnsmasq[1564]: read /etc/hosts - 7 addresses
Sep 16 15:41:31 squid-bug1761096 dnsmasq[1564]: reading 
/var/run/dnsmasq/resolv.conf
Sep 16 15:41:31 squid-bug1761096 dnsmasq[1564]: using nameserver 10.101.133.1#53
Sep 16 15:43:01 squid-bug1761096 systemd[1]: dnsmasq.service: Start-post 
operation timed out. Stopping.
Sep 16 15:43:01 squid-bug1761096 systemd[1]: Failed to start dnsmasq - A 
lightweight DHCP and caching DNS server.
Sep 16 15:43:01 squid-bug1761096 systemd[1]: dnsmasq.service: Unit entered 
failed state.
Sep 16 15:43:01 squid-bug1761096 systemd[1]: dnsmasq.service: Failed with 
result 'timeout'.
...

We also see the bug happening while restarting the dnsmasq.service:

# systemctl restart dnsmasq.service 
Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl 
status dnsmasq.service" and "journalctl -xe" for details.
# systemctl status dnsmasq.service 
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
   Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: 
enabled)
  Drop-In: /run/systemd/generator/dnsmasq.service.d
   └─50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf
   Active: failed (Result: timeout) since Wed 2020-09-16 15:47:22 UTC; 17s ago
  Process: 1744 ExecStop=/etc/init.d/dnsmasq systemd-stop-resolvconf 
(code=killed, signal=TERM)
  Process: 1808 ExecStartPost=/etc/init.d/dnsmasq systemd-start-resolvconf 
(code=killed, signal=TERM)
  Process: 1799 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, 
status=0/SUCCESS)
  Process: 1798 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, 
status=0/SUCCESS)
 Main PID: 1807 (code=exited, status=0/SUCCESS)

Sep 16 15:45:52 squid-bug1761096 dnsmasq[1807]: compile time options: IPv6 
GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC 
loop-detect inotify
Sep 16 15:45:52 squid-bug1761096 dnsmasq[1807]: DNS service limited to local 
subnets
Sep 16 15:45:52 squid-bug1761096 dnsmasq[1807]: no servers found in 
/var/run/dnsmasq/resolv.conf, will retry
Sep 16 15:45:52 squid-bug1761096 dnsmasq[1807]: read /etc/hosts - 7 addresses
Sep 16 15:45:52 squid-bug1761096 dnsmasq[1807]: reading 
/var/run/dnsmasq/resolv.conf
Sep 16 15:45:52 squid-bug1761096 dnsmasq[1807]: using nameserver 10.101.133.1#53
Sep 16 15:47:22 squid-bug1761096 systemd[1]: dnsmasq.service: Start-post 
operation timed out. Stopping.
Sep 16 15:47:22 squid-bug1761096 systemd[1]: Failed to start dnsmasq - A 
lightweight DHCP and caching DNS server.
Sep 16 15:47:22 squid-bug1761096 systemd[1]: dnsmasq.service: Unit entered 
failed state.
Sep 16 15:47:22 squid-bug1761096 systemd[1]: dnsmasq.service: Failed with 
result 'timeout'.

Now, installing the package containing the proposed fix, and testing
that it works.  After installing, restarting dnsmasq.service multiple
times and verify that it always succeeds:

# systemctl restart dnsmasq.service && echo $?
0
# systemctl restart dnsmasq.service && echo $?
0
# systemctl restart dnsmasq.service && echo $?
0
# systemctl restart dnsmasq.service && echo $?
0
# systemctl restart dnsmasq.service && echo $?
0

Therefore, tagging the bug as verified for Xenial.

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

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

Title:
  dnsmasq starts with error on Ubuntu Xenial amd64

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

2020-09-16 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

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


** Tags: focal groovy

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

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

Status in apport package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1895833] Re: unblock restrictions on alsa (max id of card and sample rate for alsa Loopback)

2020-09-16 Thread Erich Eickmeyer

Bugs in Ubuntu are never filed against the distribution as a whole, but
rather, individual components/packages. Removed affecting Ubuntu.

** No longer affects: ubuntu

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

Title:
  unblock restrictions on alsa (max id of card and sample rate for alsa
  Loopback)

Status in ALSA Libraries:
  New
Status in Alsa utilities:
  New
Status in alsa-lib package in Ubuntu:
  New
Status in alsa-utils package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact] kernel, alsa-lib, alsa-utils
  We are using more and more cards recognized as sound peripherals. When the 
number of loopback and hardware cards exceeds 32, we can no longer use them.
  Also some new devices are already using 384khz but the limitation is for alsa 
Loopback.

  I thinks we must increse CONFIG_SND_MAX_CARDS to 256 and change 192000
  sample rate value fixed in aloop.c to 384000 or 768000 to provide an
  additional margin in alsa Loopback.

  [Test Case]

  sudo add-apt-repository -y universe
  apt-get update && sudo apt-get upgrade -y
  sudo apt-get install alsa alsa-*

  shutdown -r now

  sudo modprobe snd-aloop
  sudo echo snd-aloop >> /etc/modules
  sudo adduser $(whoami) audio

  shutdown -r now

  sudo apt-get install -y apt-get install alsa alsa-utils libasound2-dev
  sudo apt-get install -y screen build-essential initramfs-tools fakeroot 
debconf-utils dpkg-dev debhelper bin86 flex bison pkgconf dkms python3-docutils 
\
  libudev-dev mt-st cpufrequtils libpci-dev libssl-dev libiberty-dev libcap-dev 
asciidoc default-jdk libncurses-dev \
  kernel-package kernel-wedge libnvpair1linux libuutil1linux libzfs2linux 
libzpool2linux zfs-dkms zfs-zed zfsutils-linux \
  crash makedumpfile  libncurses5 libncurses5-dev libelf-dev  binutils-dev 
kexec-tools 

  screen

  mkdir ~/megamod
  cd ~/megamod
  git clone git://kernel.ubuntu.com/ubuntu/ubuntu-focal.git
  cd ubuntu-focal
  sed -i 's/SNDRV_PCM_RATE_CONTINUOUS | 
SNDRV_PCM_RATE_8000_192000,/SNDRV_PCM_RATE_CONTINUOUS,/g' 
./sound/drivers/aloop.c
  sed -i 's/192000/768000/g' ./sound/drivers/aloop.c
  grep -rnl './' -e "CONFIG_SND_MAX_CARDS=32" | xargs -i@ sed -i 
's/CONFIG_SND_MAX_CARDS=32/CONFIG_SND_MAX_CARDS=256/g' @

  search and replace 32 by 256 in  and
  ./debian.master/config/annotations  for  CONFIG_SND_MAX_CARDS

  fakeroot debian/rules clean
  fakeroot debian/rules binary


  dpkg -i ../linux*5.4.0-*.deb

  shutdown -r now

  sudo systemctl disable hv-kvp-daemon.service

  

  echo "options snd-aloop \"  >> /etc/modprobe.d/alsa-base.conf
  echo 
"index=10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45
 \"  >> /etc/modprobe.d/alsa-base.conf
  echo 
"id=lp0,lp1,lp2,lp3,lp4,lp5,lp6,lp7,lp8,lp9,lp10,lp11,lp12,lp13,lp14,lp15,lp16,lp17,lp18,lp19,lp20,lp21,lp22,lp23,lp24,lp25,lp26,lp27,lp28,lp29,lp30,lp31,lp32,lp33,lp34,lp35
 \"  >> /etc/modprobe.d/alsa-base.conf
  echo 
"enable=1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1 
\"  >> /etc/modprobe.d/alsa-base.conf
  echo 
"pcm_substreams=2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2"
  >> /etc/modprobe.d/alsa-base.conf

  sudo su
  sudo mkdir /usr/src/alsa
  cd /usr/src/alsa
  git clone git://git.alsa-project.org/alsa-lib.git alsa-lib
  cd /usr/src/alsa/alsa-lib
  ./gitcompile --with-max-cards=256
  make install

  cp /usr/lib/libasound* /usr/lib/x86_64-linux-gnu/
   
  cd /usr/src/alsa
  git clone git://git.alsa-project.org/alsa-utils.git alsa-utils
  cd /usr/src/alsa/alsa-utils
  ./gitcompile --with-max-cards=256
  make install

  shutdown -r now

  [Regression Potential]

  * The regression can be considered as low, because this is because
  it's functional since 16.04

  [Other]

  * This requires a patch to be included into the kernel, alsa-lib and
  alsa-utils package.  - please see [Test Case] description for more
  details.

  * changes can be made independently and have no impact on others

  [Patch]

  In /sound/drivers/aloop.c:
  L555  .rates =SNDRV_PCM_RATE_CONTINUOUS | SNDRV_PCM_RATE_8000_192000,
  to
  L555  .rates =SNDRV_PCM_RATE_CONTINUOUS,

  In /sound/drivers/aloop.c:
  L557  .rate_max = 192000,
  to
  L557  .rate_max = 768000,

  
  In /sound/drivers/aloop.c:
  L557  uinfo->value.integer.max = 192000;
  to
  L557  uinfo->value.integer.max = 768000;

  In /debian.master/config/config.common.ubuntu
  L9069 CONFIG_SND_MAX_CARDS=32
  to
  L9069 CONFIG_SND_MAX_CARDS=256

  and update debian.master/rules.d/hooks.mk

  For alsa-lib and alsa-util, package can be simply update with
  ./gitcompile --with-max-cards=256

  Thanks everybody

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-lib/+bug/1895833/+subscriptions

-- 
Mailing

[Touch-packages] [Bug 1895833] Re: unblock restrictions on alsa (max id of card and sample rate for alsa Loopback)

2020-09-16 Thread SCHMITT Olivier

** Also affects: alsa-lib
   Importance: Undecided
   Status: New

** Also affects: alsa-utils
   Importance: Undecided
   Status: New

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

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

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

Title:
  unblock restrictions on alsa (max id of card and sample rate for alsa
  Loopback)

Status in ALSA Libraries:
  New
Status in Alsa utilities:
  New
Status in Ubuntu:
  New
Status in alsa-lib package in Ubuntu:
  New
Status in alsa-utils package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact] kernel, alsa-lib, alsa-utils
  We are using more and more cards recognized as sound peripherals. When the 
number of loopback and hardware cards exceeds 32, we can no longer use them.
  Also some new devices are already using 384khz but the limitation is for alsa 
Loopback.

  I thinks we must increse CONFIG_SND_MAX_CARDS to 256 and change 192000
  sample rate value fixed in aloop.c to 384000 or 768000 to provide an
  additional margin in alsa Loopback.

  [Test Case]

  sudo add-apt-repository -y universe
  apt-get update && sudo apt-get upgrade -y
  sudo apt-get install alsa alsa-*

  shutdown -r now

  sudo modprobe snd-aloop
  sudo echo snd-aloop >> /etc/modules
  sudo adduser $(whoami) audio

  shutdown -r now

  sudo apt-get install -y apt-get install alsa alsa-utils libasound2-dev
  sudo apt-get install -y screen build-essential initramfs-tools fakeroot 
debconf-utils dpkg-dev debhelper bin86 flex bison pkgconf dkms python3-docutils 
\
  libudev-dev mt-st cpufrequtils libpci-dev libssl-dev libiberty-dev libcap-dev 
asciidoc default-jdk libncurses-dev \
  kernel-package kernel-wedge libnvpair1linux libuutil1linux libzfs2linux 
libzpool2linux zfs-dkms zfs-zed zfsutils-linux \
  crash makedumpfile  libncurses5 libncurses5-dev libelf-dev  binutils-dev 
kexec-tools 

  screen

  mkdir ~/megamod
  cd ~/megamod
  git clone git://kernel.ubuntu.com/ubuntu/ubuntu-focal.git
  cd ubuntu-focal
  sed -i 's/SNDRV_PCM_RATE_CONTINUOUS | 
SNDRV_PCM_RATE_8000_192000,/SNDRV_PCM_RATE_CONTINUOUS,/g' 
./sound/drivers/aloop.c
  sed -i 's/192000/768000/g' ./sound/drivers/aloop.c
  grep -rnl './' -e "CONFIG_SND_MAX_CARDS=32" | xargs -i@ sed -i 
's/CONFIG_SND_MAX_CARDS=32/CONFIG_SND_MAX_CARDS=256/g' @

  search and replace 32 by 256 in  and
  ./debian.master/config/annotations  for  CONFIG_SND_MAX_CARDS

  fakeroot debian/rules clean
  fakeroot debian/rules binary


  dpkg -i ../linux*5.4.0-*.deb

  shutdown -r now

  sudo systemctl disable hv-kvp-daemon.service

  

  echo "options snd-aloop \"  >> /etc/modprobe.d/alsa-base.conf
  echo 
"index=10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45
 \"  >> /etc/modprobe.d/alsa-base.conf
  echo 
"id=lp0,lp1,lp2,lp3,lp4,lp5,lp6,lp7,lp8,lp9,lp10,lp11,lp12,lp13,lp14,lp15,lp16,lp17,lp18,lp19,lp20,lp21,lp22,lp23,lp24,lp25,lp26,lp27,lp28,lp29,lp30,lp31,lp32,lp33,lp34,lp35
 \"  >> /etc/modprobe.d/alsa-base.conf
  echo 
"enable=1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1 
\"  >> /etc/modprobe.d/alsa-base.conf
  echo 
"pcm_substreams=2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2"
  >> /etc/modprobe.d/alsa-base.conf

  sudo su
  sudo mkdir /usr/src/alsa
  cd /usr/src/alsa
  git clone git://git.alsa-project.org/alsa-lib.git alsa-lib
  cd /usr/src/alsa/alsa-lib
  ./gitcompile --with-max-cards=256
  make install

  cp /usr/lib/libasound* /usr/lib/x86_64-linux-gnu/
   
  cd /usr/src/alsa
  git clone git://git.alsa-project.org/alsa-utils.git alsa-utils
  cd /usr/src/alsa/alsa-utils
  ./gitcompile --with-max-cards=256
  make install

  shutdown -r now

  [Regression Potential]

  * The regression can be considered as low, because this is because
  it's functional since 16.04

  [Other]

  * This requires a patch to be included into the kernel, alsa-lib and
  alsa-utils package.  - please see [Test Case] description for more
  details.

  * changes can be made independently and have no impact on others

  [Patch]

  In /sound/drivers/aloop.c:
  L555  .rates =SNDRV_PCM_RATE_CONTINUOUS | SNDRV_PCM_RATE_8000_192000,
  to
  L555  .rates =SNDRV_PCM_RATE_CONTINUOUS,

  In /sound/drivers/aloop.c:
  L557  .rate_max = 192000,
  to
  L557  .rate_max = 768000,

  
  In /sound/drivers/aloop.c:
  L557  uinfo->value.integer.max = 192000;
  to
  L557  uinfo->value.integer.max = 768000;

  In /debian.master/config/config.common.ubuntu
  L9069 CONFIG_SND_MAX_CARDS=32
  to
  L9069 CONFIG_SND_MAX_CARDS=256

  and update debian.master/rules.d/hooks.mk

  For alsa-lib and alsa-util, package can be simply update with
  ./gitcompile

[Touch-packages] [Bug 1895294] Re: Fix Raccoon vulnerability (CVE-2020-1968)

2020-09-16 Thread Marc Deslauriers

This has now been fixed:

https://ubuntu.com/security/notices/USN-4504-1

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

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

Title:
  Fix Raccoon vulnerability (CVE-2020-1968)

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Xenial:
  Fix Released

Bug description:
  Xenial's current OpenSSL (1.0.2g-1ubuntu4.16) seems to not have been
  patched yet against the Raccoon Attack (CVE-2020-1968):

  - https://www.openssl.org/news/secadv/20200909.txt
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1968
  - https://raccoon-attack.com/

  Ubuntu's CVE tracker still lists this as NEEDED for Xenial:

  - https://people.canonical.com/~ubuntu-security/cve/2020/CVE-2020-1968.html
  - https://people.canonical.com/~ubuntu-security/cve/pkg/openssl.html

  Other supported Ubuntu releases use versions of OpenSSL that are not
  affected.

  Indeed:

    $ apt-cache policy openssl
    openssl:
  Installed: 1.0.2g-1ubuntu4.16

    $ apt-get changelog openssl | grep CVE-2020-1968 || echo "Not patched"
    Not patched

  What is the status?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1895294/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

2020-09-16 Thread Vlad V.

Hi!

I had the same problem with JBL TUNE500BT Headphones on Ubuntu 20.04. I
did a kernel update to 5.8.9-050809-generic version using ubuntu-
mainline-kernel.sh script [1]. I also uninstalled ofono and ofono-
phonesim which I installed earlier when trying to fix this problem and
reverted any changes I did to the default.pa file. It seems to be
working now, but audio quality is awful when using HSP/HFP, which is
related to another bug [2]. I don't know if it's a good solution, but
maybe it will help someone.

[1]:
https://raw.githubusercontent.com/pimlie/ubuntu-mainline-kernel.sh/master/ubuntu-mainline-kernel.sh
[2]: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1838151

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

Title:
Refused to switch profile to headset_head_unit: Not connected

Status in PulseAudio:
Unknown
Status in pulseaudio package in Ubuntu:
Confirmed

Bug description:
I'm trying to connect a bluetooth-speaker-with-microphone (Mi
Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
use it as a headset with microphone.

The device doesn't list in the "Input Devices" by default, and using
the sound settings to change the profile of the device to HSP/HFP
results in this log message:

W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
headset_head_unit: Not connected

I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

pulseaudio:
Installed: 1:8.0-0ubuntu3

bluez:
Installed: 5.37-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1576559/+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 1895850] [NEW] UI is not very helpful, let's talk about improvements?

2020-09-16 Thread Bruno Maximilian Voss

Public bug reported:

Hello,

I already asked a question here

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

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

Thanks for reading.

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

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


** Tags: amd64 apport-bug focal

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

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

Status in apport package in Ubuntu:
  New

Bug description:
  Hello,

  I already asked a question here

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

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

  Thanks for reading.

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

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

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

[Touch-packages] [Bug 1895302] Re: groovy debootstrap leaves /e/d/motd-news.wasremoved around

** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/390766

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

Title:
  groovy debootstrap leaves /e/d/motd-news.wasremoved around

Status in base-files package in Ubuntu:
  In Progress

Bug description:
  When debootstrapping groovy, we see an empty /etc/default/motd-
  news.wasremoved file.

  - groovy: base-files 11ubuntu12
  -rw-r--r-- 1 root root 0 set 11 10:20 /etc/default/motd-news.wasremoved

  If motd-news-config is later installed, maybe via ubuntu-server, then
  the presence of this file will disable motd-news by default, which is
  unintended as it's meant to be enabled on a server.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1895302/+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 1895664] Re: evince can't start local installation of vivaldi browser

2020-09-16 Thread Sebastien Bacher

** Summary changed:

- problem in apparmor configuration of evince
+ evince can't start local installation of vivaldi browser

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

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

Title:
  evince can't start local installation of vivaldi browser

Status in apparmor package in Ubuntu:
  New
Status in evince package in Ubuntu:
  Invalid

Bug description:
  evince 3.28.4-0ubuntu1.2 running on bionic.  I cannot call the
  vivaldi-browser by clicking on a link.  Instead an error is shown
  "Failed to execute child process “/usr/bin/vivaldi-stable” (Permission
  denied)".  Some lines from syslog:

  Sep 15 14:28:28 work kernel: [46945.893234] audit: type=1400 
audit(1600172908.761:241): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:29 work kernel: [46946.523153] audit: type=1400 
audit(1600172909.393:242): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:29 work kernel: [46946.716721] audit: type=1400 
audit(1600172909.585:243): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:29 work kernel: [46946.748450] audit: type=1400 
audit(1600172909.617:244): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:53 work kernel: [46970.973331] audit: type=1400 
audit(1600172933.841:256): apparmor="DENIED" operation="exec" 
profile="/usr/bin/evince" name="/opt/vivaldi/vivaldi" pid=5390 comm="evince" 
requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895664/+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 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default

Ok changed MP and PPA to work for 1.0 source

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

Title:
  [2.82 regression] router announcements have 'forever' lifetime by
  default

Status in dnsmasq package in Ubuntu:
  Triaged

Bug description:
  The default lifetime was changed to 1 day in 2.82 in the change
  corresponding to this changelog entry:

  Change default lease time for DHCPv6 to one day.

  Fine, but the same commit also did this:

Alter calculation of preferred and valid times in router
advertisements, so that these do not have a floor applied
of the lease time in the dhcp-range if this is not explicitly
specified and is merely the default.

  And that change is buggy and causes advertisements to have infinite
  lifetime, when you are using the default.

  See this thread

http://lists.thekelleys.org.uk/pipermail/dnsmasq-
  discuss/2020q3/014341.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+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 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default

Arrr 1.0 source, need to apply differently 

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

Title:
  [2.82 regression] router announcements have 'forever' lifetime by
  default

Status in dnsmasq package in Ubuntu:
  Triaged

Bug description:
  The default lifetime was changed to 1 day in 2.82 in the change
  corresponding to this changelog entry:

  Change default lease time for DHCPv6 to one day.

  Fine, but the same commit also did this:

Alter calculation of preferred and valid times in router
advertisements, so that these do not have a floor applied
of the lease time in the dhcp-range if this is not explicitly
specified and is merely the default.

  And that change is buggy and causes advertisements to have infinite
  lifetime, when you are using the default.

  See this thread

http://lists.thekelleys.org.uk/pipermail/dnsmasq-
  discuss/2020q3/014341.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+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 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default

BTW I randomly picked the latter patch of the two as no one seems to
have jumped on the first one and said "yes let us apply it".

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

Title:
  [2.82 regression] router announcements have 'forever' lifetime by
  default

Status in dnsmasq package in Ubuntu:
  Triaged

Bug description:
  The default lifetime was changed to 1 day in 2.82 in the change
  corresponding to this changelog entry:

  Change default lease time for DHCPv6 to one day.

  Fine, but the same commit also did this:

Alter calculation of preferred and valid times in router
advertisements, so that these do not have a floor applied
of the lease time in the dhcp-range if this is not explicitly
specified and is merely the default.

  And that change is buggy and causes advertisements to have infinite
  lifetime, when you are using the default.

  See this thread

http://lists.thekelleys.org.uk/pipermail/dnsmasq-
  discuss/2020q3/014341.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+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 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default

The patch suggested at 
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2020q3/014346.html 
isn't applied yet.
I guess this waits for feedback if it worked before they apply it.

To get this going here a PPA and an associated MP:
PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4266
MP: 
https://code.launchpad.net/~paelzer/ubuntu/+source/dnsmasq/+git/dnsmasq/+merge/390832

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

Title:
  [2.82 regression] router announcements have 'forever' lifetime by
  default

Status in dnsmasq package in Ubuntu:
  Triaged

Bug description:
  The default lifetime was changed to 1 day in 2.82 in the change
  corresponding to this changelog entry:

  Change default lease time for DHCPv6 to one day.

  Fine, but the same commit also did this:

Alter calculation of preferred and valid times in router
advertisements, so that these do not have a floor applied
of the lease time in the dhcp-range if this is not explicitly
specified and is merely the default.

  And that change is buggy and causes advertisements to have infinite
  lifetime, when you are using the default.

  See this thread

http://lists.thekelleys.org.uk/pipermail/dnsmasq-
  discuss/2020q3/014341.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+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 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default

** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/dnsmasq/+git/dnsmasq/+merge/390832

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

Title:
  [2.82 regression] router announcements have 'forever' lifetime by
  default

Status in dnsmasq package in Ubuntu:
  Triaged

Bug description:
  The default lifetime was changed to 1 day in 2.82 in the change
  corresponding to this changelog entry:

  Change default lease time for DHCPv6 to one day.

  Fine, but the same commit also did this:

Alter calculation of preferred and valid times in router
advertisements, so that these do not have a floor applied
of the lease time in the dhcp-range if this is not explicitly
specified and is merely the default.

  And that change is buggy and causes advertisements to have infinite
  lifetime, when you are using the default.

  See this thread

http://lists.thekelleys.org.uk/pipermail/dnsmasq-
  discuss/2020q3/014341.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+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 1895664] Re: problem in apparmor configuration of evince

2020-09-16 Thread Sebastien Bacher

Thank you for your bug report, vivaldi isn't a known webbrowser though
and is a locally installed software in /opt so probably something you
need to handle locally

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

Title:
  problem in apparmor configuration of evince

Status in apparmor package in Ubuntu:
  New
Status in evince package in Ubuntu:
  New

Bug description:
  evince 3.28.4-0ubuntu1.2 running on bionic.  I cannot call the
  vivaldi-browser by clicking on a link.  Instead an error is shown
  "Failed to execute child process “/usr/bin/vivaldi-stable” (Permission
  denied)".  Some lines from syslog:

  Sep 15 14:28:28 work kernel: [46945.893234] audit: type=1400 
audit(1600172908.761:241): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:29 work kernel: [46946.523153] audit: type=1400 
audit(1600172909.393:242): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:29 work kernel: [46946.716721] audit: type=1400 
audit(1600172909.585:243): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:29 work kernel: [46946.748450] audit: type=1400 
audit(1600172909.617:244): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:53 work kernel: [46970.973331] audit: type=1400 
audit(1600172933.841:256): apparmor="DENIED" operation="exec" 
profile="/usr/bin/evince" name="/opt/vivaldi/vivaldi" pid=5390 comm="evince" 
requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895664/+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 1895816] Re: gnome-shell freezing (and gdm restarting) -> xorg crash file found

This is the journalctl output just before starting gimp until I was
logged in again and able to create this log file.

** Attachment added: "gimp-crash.log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1895816/+attachment/5411311/+files/gimp-crash.log.txt

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

Title:
  gnome-shell freezing (and gdm restarting) -> xorg crash file found

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a problem with gnome-shell and gdm. My shell sometimes (not
  reproducible atm) freezes. Under some circumstances gdm will be
  restarted and I am logged out and all programs are killed. When
  logging in again, chromium for example, tells me, that the last time
  it was not exited properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 16 11:49:54 2020
  DistUpgraded: 2020-09-09 11:59:44,488 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.4.0-47-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 630 [17aa:505e]
 Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:505e]
  InstallationDate: Installed on 2017-08-28 (1114 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 20J6003DGE
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-47-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-09-09 (6 days ago)
  dmi.bios.date: 04/23/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0FET52W (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20J6003DGE
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0FET52W(1.32):bd04/23/2020:svnLENOVO:pn20J6003DGE:pvrThinkPadT470p:rvnLENOVO:rn20J6003DGE:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470p
  dmi.product.name: 20J6003DGE
  dmi.product.sku: LENOVO_MT_20J6_BU_Think_FM_ThinkPad T470p
  dmi.product.version: ThinkPad T470p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1895816/+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 1895816] Re: gnome-shell freezing (and gdm restarting) -> xorg crash file found

apt-cache policy "gimp*"

gimp-refocus:
  Installed: (none)
  Candidate: (none)
  Version table:
gimp-help-common:
  Installed: 2.8.2-2ubuntu1
  Candidate: 2.8.2-2ubuntu1
  Version table:
 *** 2.8.2-2ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages
100 /var/lib/dpkg/status
gimp-dds:
  Installed: (none)
  Candidate: 3.0.1-1build1
  Version table:
 3.0.1-1build1 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
gimp-plugin-registry:
  Installed: (none)
  Candidate: 9.20180625ubuntu2
  Version table:
 9.20180625ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
gimp-help:
  Installed: (none)
  Candidate: (none)
  Version table:
gimp-gap:
  Installed: (none)
  Candidate: 2.6.0+dfsg-5ubuntu1
  Version table:
 2.6.0+dfsg-5ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
gimp1.2-cbmplugs:
  Installed: (none)
  Candidate: (none)
  Version table:
gimp-data:
  Installed: 2.10.18-1
  Candidate: 2.10.18-1
  Version table:
 *** 2.10.18-1 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages
100 /var/lib/dpkg/status
gimp-texturize:
  Installed: (none)
  Candidate: 2.1-9build1
  Version table:
 2.1-9build1 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
gimp-gluas:
  Installed: (none)
  Candidate: 0.1.20-1.1build1
  Version table:
 0.1.20-1.1build1 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
gimp:
  Installed: 2.10.18-1
  Candidate: 2.10.18-1
  Version table:
 *** 2.10.18-1 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status
gimp-svg:
  Installed: (none)
  Candidate: (none)
  Version table:
gimp-dcraw:
  Installed: (none)
  Candidate: 1.32-1
  Version table:
 1.32-1 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
gimp-normalmap:
  Installed: (none)
  Candidate: 1.2.3-0ubuntu6
  Version table:
 1.2.3-0ubuntu6 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
gimp-gmic:
  Installed: (none)
  Candidate: 2.4.5-1.1
  Version table:
 2.4.5-1.1 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
gimp-helpbrowser:
  Installed: (none)
  Candidate: (none)
  Version table:
gimp-resynthesizer:
  Installed: (none)
  Candidate: (none)
  Version table:
gimp-gutenprint:
  Installed: (none)
  Candidate: 5.3.3-4
  Version table:
 5.3.3-4 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
gimp1.3-cbmplugs:
  Installed: (none)
  Candidate: (none)
  Version table:
gimp-lensfun:
  Installed: (none)
  Candidate: 0.2.4-1.1
  Version table:
 0.2.4-1.1 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
gimp-cbmplugs:
  Installed: (none)
  Candidate: 1.2.2-1build1
  Version table:
 1.2.2-1build1 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
gimp-help-ca:
  Installed: (none)
  Candidate: 2.8.2-2ubuntu1
  Version table:
 2.8.2-2ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages
gimp-help-de:
  Installed: 2.8.2-2ubuntu1
  Candidate: 2.8.2-2ubuntu1
  Version table:
 *** 2.8.2-2ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages
100 /var/lib/dpkg/status
gimp-help-el:
  Installed: (none)
  Candidate: 2.8.2-2ubuntu1
  Version table:
 2.8.2-2ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages
gimp-help-en:
  Installed: 2.8.2-2ubuntu1
  Candidate: 2.8.2-2ubuntu1
  Version table:
 *** 2.8.2-2ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages
100 /var/lib/dpkg/status
gimp-help-es:
  Installed: (none)
  Candidate: 2.8.2-2ubuntu1
  Version table:
 2.8.2-2ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages
gimp-help-fr:
  Installed: (none)
  Candidate: 2.8.2-2ubuntu1
  Version table:
 2.8.2-2ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages
gimp-help-it:
  Installed: (none)
  Candidate: 2.8.2-2ubuntu1
  Version table:
 2.8.2-2ubuntu1

[Touch-packages] [Bug 1895816] Re: gnome-shell freezing (and gdm restarting) -> xorg crash file found

I started gimp on the command line with:

gimp -c --verbose image.png

The attached file is the result.

** Attachment added: "gimp.log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1895816/+attachment/5411310/+files/gimp.log.txt

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

Title:
  gnome-shell freezing (and gdm restarting) -> xorg crash file found

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a problem with gnome-shell and gdm. My shell sometimes (not
  reproducible atm) freezes. Under some circumstances gdm will be
  restarted and I am logged out and all programs are killed. When
  logging in again, chromium for example, tells me, that the last time
  it was not exited properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 16 11:49:54 2020
  DistUpgraded: 2020-09-09 11:59:44,488 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.4.0-47-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 630 [17aa:505e]
 Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:505e]
  InstallationDate: Installed on 2017-08-28 (1114 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 20J6003DGE
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-47-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-09-09 (6 days ago)
  dmi.bios.date: 04/23/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0FET52W (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20J6003DGE
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0FET52W(1.32):bd04/23/2020:svnLENOVO:pn20J6003DGE:pvrThinkPadT470p:rvnLENOVO:rn20J6003DGE:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470p
  dmi.product.name: 20J6003DGE
  dmi.product.sku: LENOVO_MT_20J6_BU_Think_FM_ThinkPad T470p
  dmi.product.version: ThinkPad T470p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1895816/+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 1895816] Re: gnome-shell freezing (and gdm restarting) -> xorg crash file found

It seems to be a problem with gimp and images because I can reproduce
the problem when opening gimp with any image file.

** Attachment added: "1"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1895816/+attachment/5411309/+files/1

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

Title:
  gnome-shell freezing (and gdm restarting) -> xorg crash file found

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a problem with gnome-shell and gdm. My shell sometimes (not
  reproducible atm) freezes. Under some circumstances gdm will be
  restarted and I am logged out and all programs are killed. When
  logging in again, chromium for example, tells me, that the last time
  it was not exited properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 16 11:49:54 2020
  DistUpgraded: 2020-09-09 11:59:44,488 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.4.0-47-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 630 [17aa:505e]
 Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:505e]
  InstallationDate: Installed on 2017-08-28 (1114 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 20J6003DGE
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-47-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-09-09 (6 days ago)
  dmi.bios.date: 04/23/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0FET52W (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20J6003DGE
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0FET52W(1.32):bd04/23/2020:svnLENOVO:pn20J6003DGE:pvrThinkPadT470p:rvnLENOVO:rn20J6003DGE:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470p
  dmi.product.name: 20J6003DGE
  dmi.product.sku: LENOVO_MT_20J6_BU_Think_FM_ThinkPad T470p
  dmi.product.version: ThinkPad T470p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1895816/+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 1895664] Re: problem in apparmor configuration of evince

2020-09-16 Thread Sebastien Bacher

** Changed in: evince (Ubuntu)
   Importance: Undecided => Low

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

Title:
  problem in apparmor configuration of evince

Status in apparmor package in Ubuntu:
  New
Status in evince package in Ubuntu:
  New

Bug description:
  evince 3.28.4-0ubuntu1.2 running on bionic.  I cannot call the
  vivaldi-browser by clicking on a link.  Instead an error is shown
  "Failed to execute child process “/usr/bin/vivaldi-stable” (Permission
  denied)".  Some lines from syslog:

  Sep 15 14:28:28 work kernel: [46945.893234] audit: type=1400 
audit(1600172908.761:241): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:29 work kernel: [46946.523153] audit: type=1400 
audit(1600172909.393:242): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:29 work kernel: [46946.716721] audit: type=1400 
audit(1600172909.585:243): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:29 work kernel: [46946.748450] audit: type=1400 
audit(1600172909.617:244): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:53 work kernel: [46970.973331] audit: type=1400 
audit(1600172933.841:256): apparmor="DENIED" operation="exec" 
profile="/usr/bin/evince" name="/opt/vivaldi/vivaldi" pid=5390 comm="evince" 
requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895664/+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 1895060] Re: [FFe] apparmor 3 upstream release

2020-09-16 Thread Jamie Strandboge

FYI, we're looking at the autopkgtest dbus issue now.

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

Title:
  [FFe] apparmor 3 upstream release

Status in apparmor package in Ubuntu:
  New

Bug description:
  As per the draft upstream release notes[1]:

  AppArmor 3.0 is a major new release of the AppArmor user space that makes
  an important change to policy development and support. Its focus is
  transitioning policy to the new features ABI and as such other new features
  have been limited.

  Apprmor 3.0 is a bridge release between older AppArmor 2.x policy and the
  newer AppArmor 3 style policy which requires the declaration of a features
  abi. As such AppArmor 3.0 will be a short lived release, and will not
  receive long term support. The following AppArmor 3.1 feature release is
  planned to be a regular release, please take this into account when
  including AppArmor 3.0 into a distro release.

  As such, Ubuntu 20.10 provides a great opportunity to introduce AppArmor3
  to Ubuntu and provide these new capabilities to users and system
  administrators. The short support lifespan of Ubuntu 20.10 ensures that
  there is alignment with the limited support lifetime of AppArmor 3.0 from
  upstream, whilst giving good exposure and opportunity to test and exercise
  the new features in AppArmor 3.x on the road to Ubuntu 22.04. A highlight
  of new features provided by AppArmor 3.0 include:

  - Policy now must declare the feature abi it was developed for if it is to
    use any new features. This ensures that old policy will not become
    incompatible with new kernels that support additional AppArmor features.
  - The use of profile names that are based on pathnames are deprecated.
  - Support for new kernel features (requires appropriate features abi
    tagging in policy)
    - upstream v8 network socket rules
    - xattr attachment conditionals
    - capabilities PERFMON and BPF
  - Improved compiler warnings and semantic checks
  - aa-status rewritten in C (previously was python) with additional features
    - supports use in systems/images where python is not available
    - supports kill, unconfined and mixed profile modes
  - Rewritten aa-notify (previously was perl, now python3)
    - shared backend with other python tools
    - support use of aa.CONFDIR instead of hard coded /etc/apparmor
    - improved message layout
  - Improved support for kernels that support LSM stacking
  - New utility aa-features-abi to extract and work with kernel abi features
  - New utility aa-load to load binary policy without calling the
    apparmor_parser
  - Support for profile modes
    - enforce (default when no mode flag is supplied)
    - kill (experimental)
    - unconfined (experimental)

  The use of the new AppArmor profile feature ABI includes a default
  configuration (for the Ubuntu packaged version of AppArmor proposed in this
  FFE) for the AppArmor features within the 5.4 Linux kernel - this ensures
  that all profiles provided in AppArmor3 for groovy will conform to this
  feature set and that upgrades to the kernel version (say to 5.8) that may
  include newer AppArmor confinement features will not result in additional
  policy denials as a result (since say the existing profile did not specify
  a rule for a new AppArmor feature which is now supported by the upgraded
  kernel). This ensures that there will be no regressions in application
  behaviour as a result of AppArmor kernel feature upgrades.

  TESTING

  This has been extensively tested by the security team - this includes
  following the documented Ubuntu merges test plan[2] for AppArmor and the
  extensive QA Regression Tests[3] for AppArmor as well. This ensures that the
  various applications that make heavy use of AppArmor (LXD, docker, lxc,
  dbus, libvirt, snapd etc) have all been exercised and no regressions have
  been observed. All tests have passed and demonstrated both apparmor and the
  various applications that use it to be working as expected.

  BUILD LOGS

  This is currently uploaded to groovy-proposed, build logs can be found on
  Launchpad at:
  https://launchpad.net/ubuntu/+source/apparmor/3.0.0~beta1-0ubuntu1

  INSTALL LOG

  See attached
  
(https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895060/+attachment/5411197/+files
  /groovy-proposed-apparmor-install.log) for a log showing install of
  the packages from groovy-proposed

  [1] https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_3.0
  [2] https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor
  [3] 
https://git.launchpad.net/qa-regression-testing/tree/scripts/test-apparmor.py

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

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

[Touch-packages] [Bug 1892559] Re: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite

Sorry, I forgot to update one section for pcsc-lite on packaging:

- important open bugs (crashers, etc) in Debian or Ubuntu

There are quite some:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bugs?field.searchtext=crash=Search%3Alist=NEW%3Alist=INCOMPLETE_WITH_RESPONSE%3Alist=INCOMPLETE_WITHOUT_RESPONSE%3Alist=CONFIRMED%3Alist=TRIAGED%3Alist=INPROGRESS%3Alist=FIXCOMMITTED=_reporter=_dupes=on_patch=_no_package==-date_last_updated=0

Also this one should be fixed or at least checked
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930530

I have already had that in my overall summary, just the details were
missing.

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

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

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

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

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

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

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

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

  Has a debian/watch file.
  Quilt packaging.

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

  [Dependencies]
  Minimal dependencies, in main

  [Standards compliance]
  Appears to satisfy FHS and Debian policy

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

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

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

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

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

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

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

  Quilt packaging.

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

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

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

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

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

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

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

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

  [Dependencies]

[Touch-packages] [Bug 1892559] Re: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite

## pcsc-lite ##

[Summary]
Mir Team ACK under the condition that the required TODOs are resolved.
While the owning Team should look at that security can already start
a review.

This does need a security review, so I'll assign ubuntu-security

list specific binary packages to be promoted to main: pcscd,
libpcsclite1

Clarifications:
- @Seth - the filing is done as if one would only need libpcsclite1 but Joy
  said in comment #12 that pcscd is also needed.
  Could you clarify which is true as the security risk increases if we add
  the daemon as well.
  For now I'll go on as if the daemon would be part of it.

Required TODOs:
- The package has no team bug subscriber - please fix
- Please look into open bugs and crashes before we promote.
  Do a bug-scrub and ensure we know what is outdated and no more true
  and what else is still an issue. This can be seen as preview to the
  latter maintenance - so don't skip all of them due to "don't have
  the HW" :-)

[Duplication]
There is no other package in main providing the same functionality.
Note: Joy checked if the other bits can do it without but it is required.
See comment #12.

[Dependencies]
OK:
- no other Dependencies to MIR due to this
- one -dev package that will be auto-promoted but no bad deps from there

[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking

[Security]
OK:
- history of CVEs does not look too concerning
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop

Problems:
- does parse data formats
- does open a port
- does deal with system authentication (eg, pam), etc)

This needs a security review, before doing so please clarify if the daemon
pcscsd is part of the scope.

[Common blockers]
OK:
- does not FTBFS currently
- no translation present, but none needed for this case (user visible)?
- not a python/go package, no extra constraints to consider int hat regard

Problems:
- does not have a test suite that runs at build time
- does not have a test suite that runs as autopkgtest
  We have talked about tests before, no reason to re-iterate
- The package has no team bug subscriber - please fix

[Packaging red flags]
OK:
- Ubuntu does not carry a delta
- symbols tracking is in place
- d/watch is present and looks ok
- Upstream update history is good
- Debian/Ubuntu update history is good
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
  maintained the package
- no massive Lintian warnings
- d/rules is rather clean
- Does not have Built-Using

[Upstream red flags]
OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (as far as I can check it)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH
- no use of user nobody
- no use of setuid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- no embedded source copies
- not part of the UI for extra checks

** Changed in: pcsc-lite (Ubuntu)
 Assignee: Christian Ehrhardt  (paelzer) => Ubuntu Security Team 
(ubuntu-security)

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

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

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

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

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

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

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

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

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

  Has a debian/watch file.
  Quilt packaging.

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

  [Dependencies]
  Minimal dependencies, in main

  [Standards

[Touch-packages] [Bug 1895640] Re: BlueZ 5.55 release

This bug was fixed in the package bluez - 5.55-0ubuntu1

---
bluez (5.55-0ubuntu1) groovy; urgency=medium

  * New upstream release 5.55 (LP: #1895640)
- Fix issue with handling security level for HoG.
- Fix issue with handling HIDSDPDisable attribute.
- Fix issue with handling HID virtual cable unplug.
- Fix issue with handling HID channel disconnect order.
- Fix issue with handling AVDTP delay reporting states.
- Fix issue with handling AVRCP notification events.
- Fix issue with handling AVRCP list player attributes.
- Fix issue with handling AVRCP category 1 player settings.
- Fix issue with handling AVRCP media player passthrough bitmask.
- Fix issue with handling HFP 1.7 default features.
- Fix issue with handling GATT disconnecting handling.
- Fix issue with handling GATT database hash.
- Fix issue with handling service changed characteristic.
- Fix issue with handling read of multiple characteristic values.
- Fix issue with handling Just-Works auto-accept pairing.
- Fix issue with handling authentication of bonded devices.
- Fix issue with handling L2CAP streaming mode for AVDTP.
- Fix issue with handling SysEx parser for MIDI support.
- Fix issue with handling configured scan parameter values.
- Fix issue with handling temporary devices removal.
- Fix issue with handling advertising flags.

 -- Daniel van Vugt   Tue, 15 Sep 2020
17:17:32 +0800

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

Title:
  BlueZ 5.55 release

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.55.tar.xz

  https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?h=5.55

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1895640/+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 1800836] Re: systemd-networkd doesn't process IPv6 RA properly

2020-09-16 Thread Kjetil Torgrim Homme

This is still happening with 237-3ubuntu10.42 in Bionic.  RA routes
announced with lifetime of 0s are not removed.  It is the firewall which
used to be the default router which (continously) announce these 0s
lifetimes to make sure there are no issues with failover.

$ ip -6 route show default
default proto ra metric 100 
nexthop via fe80::21b:21ff:febc:97e6 dev eth0 weight 1 
nexthop via fe80::21b:21ff:febc:9416 dev eth0 weight 1 

$ sudo rdisc6 eth0
Soliciting ff02::2 (ff02::2) on eth0...

Hop limit :   64 (  0x40)
Stateful address conf.:   No
Stateful other conf.  :   No
Mobile home agent :   No
Router preference :   medium
Neighbor discovery proxy  :   No
Router lifetime   :0 (0x) seconds
Reachable time:  unspecified (0x)
Retransmit time   :  unspecified (0x)
 Recursive DNS server : 2a02:c0::1
  DNS server lifetime :  2419200 (0x0024ea00) seconds
 from fe80::21b:21ff:febc:9416

Hop limit :   64 (  0x40)
Stateful address conf.:   No
Stateful other conf.  :   No
Mobile home agent :   No
Router preference :   medium
Neighbor discovery proxy  :   No
Router lifetime   :0 (0x) seconds
Reachable time:  unspecified (0x)
Retransmit time   :  unspecified (0x)
 Recursive DNS server : 2a02:c0::1
  DNS server lifetime :  2419200 (0x0024ea00) seconds
 from fe80::21b:21ff:febc:9416

Hop limit :   64 (  0x40)
Stateful address conf.:   No
Stateful other conf.  :   No
Mobile home agent :   No
Router preference :   medium
Neighbor discovery proxy  :   No
Router lifetime   :   30 (0x001e) seconds
Reachable time:  unspecified (0x)
Retransmit time   :  unspecified (0x)
 Prefix   : 2a02:c0:900:113::/64
  On-link :  Yes
  Autonomous address conf.:  Yes
  Valid time  :86400 (0x00015180) seconds
  Pref. time  :14400 (0x3840) seconds
 Recursive DNS server : 2a02:c0::1
  DNS server lifetime :  2419200 (0x0024ea00) seconds
 from fe80::21b:21ff:febc:97e6

Hop limit :   64 (  0x40)
Stateful address conf.:   No
Stateful other conf.  :   No
Mobile home agent :   No
Router preference :   medium
Neighbor discovery proxy  :   No
Router lifetime   :   30 (0x001e) seconds
Reachable time:  unspecified (0x)
Retransmit time   :  unspecified (0x)
 Prefix   : 2a02:c0:900:113::/64
  On-link :  Yes
  Autonomous address conf.:  Yes
  Valid time  :86400 (0x00015180) seconds
  Pref. time  :14400 (0x3840) seconds
 Recursive DNS server : 2a02:c0::1
  DNS server lifetime :  2419200 (0x0024ea00) seconds
 from fe80::21b:21ff:febc:97e6


** Changed in: systemd (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  systemd-networkd doesn't process IPv6 RA properly

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The gateways/firewalls in our DC are highly available and when there
  is a failover their IPv6 VIP (fe80::1) moves from the master to the
  backup one.

  We found that only our Bionic VMs behind those gateways had issues
  after a failover. Those Bionic VMs were all running systemd-networkd
  (from netplan) and before the failover they had:

  $ ip -6 route
  ...
  default via fe80::1 dev eth0 proto ra metric 1024 pref medium

  But after a failover:

  $ ip -6 route
  ...
  default proto ra metric 1024
  nexthop via fe80::1 dev eth0 weight 1
  nexthop via fe80::210:18ff:febe:6750 dev eth0 weight 1

  And after another failover:

  $ ip -6 route
  ...
  default proto ra metric 1024
  nexthop via fe80::1 dev eth0 weight 1
  nexthop via fe80::210:18ff:febe:6750 dev eth0 weight 1
  nexthop via fe80::210:18ff:fe77:b558 dev eth0 weight 1

  
  This is problematic as those then use fe80::210:18ff:fe77:b558%$IFACE as 
their default gateway even when this gateway is unavailable:

  $ ip -6 route get ::
  :: from :: via fe80::210:18ff:fe77:b558 dev eth0 proto ra src 
fe80::a800:ff:fe51:8c37 metric 1024 pref medium

  
  We concluded it was a systemd-networkd bug after checking that the following 
combinations were NOT affected:

  1) Xenial+4.4 kernel
  2) Xenial+4.15 kernel
  3)

Re: [Touch-packages] [Bug 1895665] Re: PulseAudio automatically switches from HDMI 2 after display sleep

2020-09-16 Thread Andrii Puhalevich

Right. I just tested:
Selected digital device.
Selected HDMI 2 for digital device.
Disconnected HDMI 2 from laptop (digital device automatically switched to
HDMI 1, sound automatically switched to internal analog audio).
Connected HDMI 2 to laptop (digital device automatically switched to HDMI 2
- this resolves the main part of the issue, but sound still left on
internal analog audio).

On Wed, Sep 16, 2020 at 12:30 PM Hui Wang <1895...@bugs.launchpad.net>
wrote:

> Do you mean even did the change of #2, the output device still changes
> to internal analog audio after sleep? Before sleep, you select the hdmi-
> output-2 manually?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1895665
>
> Title:
>   PulseAudio automatically switches from HDMI 2 after display sleep
>
> Status in pulseaudio package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I have an Nvidia based video card that has an HDMI output + a
> DisplayPort output.
>   DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI
> output is listed as "Digital Stereo (HDMI 2)".
>
>   I prefer to use "Digital Stereo (HDMI 2)".
>   But after each display sleep (screen lock for example) audio is switched
> to built in audio
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: pulseaudio 1:13.99.1-1ubuntu3.6
>   ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
>   Uname: Linux 5.4.0-47-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.20.11-0ubuntu27.8
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: XFCE
>   Date: Tue Sep 15 14:56:58 2020
>   InstallationDate: Installed on 2020-06-20 (86 days ago)
>   InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   SourcePackage: pulseaudio
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 11/11/2019
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.11.1
>   dmi.board.name: 0CNDTP
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A01
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr:
>   dmi.product.family: GSeries
>   dmi.product.name: G5 5590
>   dmi.product.sku: 08EA
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+subscriptions
>

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

Title:
  PulseAudio automatically switches from HDMI 2 after display sleep

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have an Nvidia based video card that has an HDMI output + a DisplayPort 
output.
  DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output 
is listed as "Digital Stereo (HDMI 2)".

  I prefer to use "Digital Stereo (HDMI 2)".
  But after each display sleep (screen lock for example) audio is switched to 
built in audio

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Sep 15 14:56:58 2020
  InstallationDate: Installed on 2020-06-20 (86 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.name: 0CNDTP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G5 5590
  dmi.product.sku: 08EA
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+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 1895757] Re: Terminal hangs running sudo when "use_pty" is set in /etc/sudoers

2020-09-16 Thread Alejandro Santoyo Gonzalez

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

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

Title:
  Terminal hangs running sudo when "use_pty" is set in /etc/sudoers

Status in sudo package in Ubuntu:
  New
Status in sudo source package in Bionic:
  New

Bug description:
  An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs
  running a command using 'sudo' when 'use_pty' is set in /etc/sudoers.

  Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):

  1) Log in into an Ubuntu server (tested on 18.04.5 using SSH)
  2) Ensure that /etc/sudoers has the following line (add this line if not 
present)
  Defaults  use_pty
  3) Execute the following (test 'sudo' command):
  for i in {1..10}; do sudo -- cat /var/log/syslog; done

  The terminal hangs and the following backtrace is obtained:

  (gdb) bt
  #0  0x7f751d5c8cc4 in __GI___poll (fds=0x55d0159917b0, nfds=1, 
timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
  #1  0x7f751d8b146a in poll (__timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
  #2  sudo_ev_scan_impl (base=base@entry=0x55d015990dc0, flags=flags@entry=0) 
at ../../../lib/util/event_poll.c:155
  #3  0x7f751d8aa74d in sudo_ev_loop_v1 (base=base@entry=0x55d015990dc0, 
flags=flags@entry=0) at ../../../lib/util/event.c:617
  #4  0x55d01570597a in del_io_events (nonblocking=nonblocking@entry=false) 
at ../../src/exec_pty.c:1537
  #5  0x55d015707b97 in pty_close (cstat=0x7ffd074d6110) at 
../../src/exec_pty.c:697
  #6  exec_pty (details=details@entry=0x55d01591e0e0 , 
cstat=cstat@entry=0x7ffd074d6110) at ../../src/exec_pty.c:1412
  #7  0x55d015701178 in sudo_execute (details=0x55d01591e0e0 
, cstat=0x7ffd074d6110) at ../../src/exec.c:391
  #8  0x55d01570e15b in run_command (details=0x55d01591e0e0 
) at ../../src/sudo.c:968
  #9  0x55d0156ff9a0 in main (argc=, argv=, 
envp=) at ../../src/sudo.c:294

  A similar (most likely the same) bug has been reported here
  https://access.redhat.com/solutions/3404401.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1895757/+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 1895816] [NEW] gnome-shell freezing (and gdm restarting) -> xorg crash file found

Public bug reported:

I have a problem with gnome-shell and gdm. My shell sometimes (not
reproducible atm) freezes. Under some circumstances gdm will be
restarted and I am logged out and all programs are killed. When logging
in again, chromium for example, tells me, that the last time it was not
exited properly.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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.100  Fri May 29 08:45:51 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 16 11:49:54 2020
DistUpgraded: 2020-09-09 11:59:44,488 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 440.100, 5.4.0-47-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 630 [17aa:505e]
   Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:505e]
InstallationDate: Installed on 2017-08-28 (1114 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 20J6003DGE
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-47-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-09-09 (6 days ago)
dmi.bios.date: 04/23/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: R0FET52W (1.32 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20J6003DGE
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR0FET52W(1.32):bd04/23/2020:svnLENOVO:pn20J6003DGE:pvrThinkPadT470p:rvnLENOVO:rn20J6003DGE:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470p
dmi.product.name: 20J6003DGE
dmi.product.sku: LENOVO_MT_20J6_BU_Think_FM_ThinkPad T470p
dmi.product.version: ThinkPad T470p
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  gnome-shell freezing (and gdm restarting) -> xorg crash file found

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a problem with gnome-shell and gdm. My shell sometimes (not
  reproducible atm) freezes. Under some circumstances gdm will be
  restarted and I am logged out and all programs are killed. When
  logging in again, chromium for example, tells me, that the last time
  it was not exited properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME

[Touch-packages] [Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

2020-09-16 Thread Leon Liao

** Merge proposal linked:
   
https://code.launchpad.net/~lihow731/network-manager/+git/network-manager/+merge/390544

** Merge proposal unlinked:
   
https://code.launchpad.net/~lihow731/network-manager/+git/network-manager/+merge/388865

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

Title:
  The network manager does not check the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  [Impact]

   In some cases, the wow is not configured and the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
  management of wake-on-LAN in NetworkManager).

   The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE 
bit.
   But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
   So, the management of wake-on-LAN still is done by NetworkManager.

  [Test Case]

   On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
   Step 1. Enter suspend (s2idle)
   Setp 2. Resume from suspend

   After resume from suspend, the Wi-Fi functiall still is normal.

   You can download the kernel and linux-firmware that backport the Qucalcomm's 
dirver fro focal from below link:
   https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633

  [Regression Potential]

   * No potential regressions.

  [Other Info]
   
   * None

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1891632/+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 1894338] Re: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work

The result of my experiments using that testing kernel was: the headset
volume up/down button worked, but only when a manual keyboard volume
up/down stroke preceded. I speculate that this has got to do with some
auto-disabling of the internal laptop port after some time (probable,
because a very slight hissing sound when no sound is playing on system
stops after ~30sec of such a "no sound" on Windows too and then the same
required manual keyboard up/down stroke is required before the jack gets
"re-enabled" (I guess?) and receiving headset up/down volume controls
successfully). However, you may know better of such stuff.

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

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

Title:
  [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control
  buttons don't work

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  My earphones are the one coming with Samsung Galaxy S8 (here:
  https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung-
  earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04
  (dual-boot with Windows 10, Secure Boot enabled)

  Trying to set the volume from my earphones' controls doesn't work, no
  modification on the volume, the sound bar on Ubuntu doesn't appear in
  order to indicate volume change. I would like to change the master
  volume, or whatever my common laptop controls do when I up/down the
  volume controls on my earphones, like it happens on Windows 10. Why
  does the erroneous behavior of being unable to set volume from my
  earphones happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.10
  ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
  Uname: Linux 4.15.0-115-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jason  3523 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  4 23:29:52 2020
  InstallationDate: Installed on 2018-09-28 (706 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.0
  dmi.board.name: 02P5YY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7570
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-28 (718 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: snd_hda_codec_hdmi snd_hda_codec_realtek 
snd_hda_codec_generic hid_multitouch wmi_bmof dell_wmi snd_hda_intel 
snd_intel_dspcfg soundwire_intel soundwire_generic_allocation snd_soc_core 
dell_laptop ledtrig_audio snd_compress soundwire_cadence soundwire_bus 
dell_smbios snd_hda_codec dell_wmi_descriptor snd_hwdep dcdbas snd_hda_core 
snd_pcm x86_pkg_temp_thermal intel_powerclamp iwlmvm snd_seq_midi 
snd_seq_midi_event iwlwifi snd_rawmidi i915 snd_seq snd_seq_device i2c_algo_bit 
snd_timer drm_kms_helper syscopyarea sysfillrect sysimgblt snd fb_sys_fops drm 
int3403_thermal soundcore wmi intel_lpss_pci int3402_thermal 
processor_thermal_device int3400_thermal int340x_thermal_zone 
intel_soc_dts_iosf acpi_thermal_rel mei_me intel_lpss intel_pch_thermal 
mfd_core mei efivarfs xhci_pci xhci_hcd i2c_hid
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 5.9.0-rc3+ x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894338/+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 1894338] Re: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work

apport information

** Tags added: apport-collected

** Description changed:

  My earphones are the one coming with Samsung Galaxy S8 (here:
  https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung-
  earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04
  (dual-boot with Windows 10, Secure Boot enabled)
  
  Trying to set the volume from my earphones' controls doesn't work, no
  modification on the volume, the sound bar on Ubuntu doesn't appear in
  order to indicate volume change. I would like to change the master
  volume, or whatever my common laptop controls do when I up/down the
  volume controls on my earphones, like it happens on Windows 10. Why does
  the erroneous behavior of being unable to set volume from my earphones
  happen?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.10
  ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
  Uname: Linux 4.15.0-115-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jason  3523 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  4 23:29:52 2020
  InstallationDate: Installed on 2018-09-28 (706 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.0
  dmi.board.name: 02P5YY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7570
  dmi.sys.vendor: Dell Inc.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.17
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-09-28 (718 days ago)
+ InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
+ NonfreeKernelModules: snd_hda_codec_hdmi snd_hda_codec_realtek 
snd_hda_codec_generic hid_multitouch wmi_bmof dell_wmi snd_hda_intel 
snd_intel_dspcfg soundwire_intel soundwire_generic_allocation snd_soc_core 
dell_laptop ledtrig_audio snd_compress soundwire_cadence soundwire_bus 
dell_smbios snd_hda_codec dell_wmi_descriptor snd_hwdep dcdbas snd_hda_core 
snd_pcm x86_pkg_temp_thermal intel_powerclamp iwlmvm snd_seq_midi 
snd_seq_midi_event iwlwifi snd_rawmidi i915 snd_seq snd_seq_device i2c_algo_bit 
snd_timer drm_kms_helper syscopyarea sysfillrect sysimgblt snd fb_sys_fops drm 
int3403_thermal soundcore wmi intel_lpss_pci int3402_thermal 
processor_thermal_device int3400_thermal int340x_thermal_zone 
intel_soc_dts_iosf acpi_thermal_rel mei_me intel_lpss intel_pch_thermal 
mfd_core mei efivarfs xhci_pci xhci_hcd i2c_hid
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=el_GR.UTF-8
+  SHELL=/bin/bash
+ Tags:  bionic
+ Uname: Linux 5.9.0-rc3+ x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1894338/+attachment/5411272/+files/ProcCpuinfoMinimal.txt

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

Title:
  [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control
  buttons don't work

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  My earphones are the one coming with Samsung Galaxy S8 (here:
  https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung-
  earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04
  (dual-boot with Windows 10, Secure Boot enabled)

  Trying to set the volume from my earphones' controls doesn't work, no
  modification on the volume, the sound bar on Ubuntu doesn't appear in
  order to indicate volume change. I would like to change the master
  volume, or whatever my common laptop controls do when I up/down the
  volume controls on my earphones, like it happens on Windows 10. Why
  does the erroneous behavior of being unable to set volume from my
  earphones happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.10
  ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
  Uname: Linux 4.15.0-115-generic x86_64

[Touch-packages] [Bug 1894338] Re: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work

And output of "sudo evtest" with me selecting the 11 device (yes, I
booted it by temporarily disabling SecureBoot)

No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:  Lid Switch
/dev/input/event1:  Power Button
/dev/input/event2:  Sleep Button
/dev/input/event3:  Power Button
/dev/input/event4:  AT Translated Set 2 keyboard
/dev/input/event5:  SynPS/2 Synaptics TouchPad
/dev/input/event6:  Dell WMI hotkeys
/dev/input/event7:  DELL07EA:00 06CB:7E92 Mouse
/dev/input/event8:  DELL07EA:00 06CB:7E92 Touchpad
/dev/input/event9:  Video Bus
/dev/input/event10: Video Bus
/dev/input/event11: HDA Intel PCH Headset Jack
/dev/input/event12: HDA Intel PCH Headphone Mic
/dev/input/event13: HDA Intel PCH HDMI/DP,pcm=3
/dev/input/event14: HDA Intel PCH HDMI/DP,pcm=7
/dev/input/event15: HDA Intel PCH HDMI/DP,pcm=8
/dev/input/event16: HDA Intel PCH HDMI/DP,pcm=9
/dev/input/event17: HDA Intel PCH HDMI/DP,pcm=10
Select the device event number [0-17]: 11
Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "HDA Intel PCH Headset Jack"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
Event code 114 (KEY_VOLUMEDOWN)
Event code 115 (KEY_VOLUMEUP)
Event code 164 (KEY_PLAYPAUSE)
Event code 582 (KEY_VOICECOMMAND)
  Event type 5 (EV_SW)
Event code 2 (SW_HEADPHONE_INSERT) state 0
Event code 4 (SW_MICROPHONE_INSERT) state 0
Properties:
Testing ... (interrupt to exit)

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

Title:
  [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control
  buttons don't work

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  My earphones are the one coming with Samsung Galaxy S8 (here:
  https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung-
  earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04
  (dual-boot with Windows 10, Secure Boot enabled)

  Trying to set the volume from my earphones' controls doesn't work, no
  modification on the volume, the sound bar on Ubuntu doesn't appear in
  order to indicate volume change. I would like to change the master
  volume, or whatever my common laptop controls do when I up/down the
  volume controls on my earphones, like it happens on Windows 10. Why
  does the erroneous behavior of being unable to set volume from my
  earphones happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.10
  ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
  Uname: Linux 4.15.0-115-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jason  3523 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  4 23:29:52 2020
  InstallationDate: Installed on 2018-09-28 (706 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.0
  dmi.board.name: 02P5YY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7570
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-28 (718 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: snd_hda_codec_hdmi snd_hda_codec_realtek 
snd_hda_codec_generic hid_multitouch wmi_bmof dell_wmi snd_hda_intel 
snd_intel_dspcfg soundwire_intel soundwire_generic_allocation snd_soc_core 
dell_laptop ledtrig_audio snd_compress soundwire_cadence soundwire_bus 
dell_smbios snd_hda_codec dell_wmi_descriptor snd_hwdep dcdbas snd_hda_core 
snd_pcm x86_pkg_temp_thermal intel_powerclamp iwlmvm snd_seq_midi 
snd_seq_midi_event iwlwifi snd_rawmidi i915 snd_seq snd_seq_device i2c_algo_bit 
snd_timer drm_kms_helper syscopyarea sysfillrect sysimgblt snd fb_sys_fops drm 
int3403_thermal soundcore wmi intel_lpss_pci int3402_thermal 
processor_thermal_device int3400_thermal int340x_thermal_zone 
intel_soc_dts_iosf acpi_thermal_rel mei_me intel_lpss intel_pch_thermal 
mfd_core mei

[Touch-packages] [Bug 1895794] Re: Plugging an external monitor on USB-C port does not show up. Need to reboot each time

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

** Summary changed:

- Plugging an external monitor on USB-C port does not show up. Need to reboot 
each time
+ [i915] Plugging an external monitor on USB-C port does not show up. Need to 
reboot each time

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

Title:
  [i915] Plugging an external monitor on USB-C port does not show up.
  Need to reboot each time

Status in linux package in Ubuntu:
  New

Bug description:
  Whenever I plug an external monitor (Dell P2720DC) on my ThinkPad X1
  (8th gen.) with Ubuntu 20.04, it is not directly recognized. I need to
  reboot the system so that it can find the monitor. Here is an extract
  of dmesg:

  [87389.923632] usb 1-5: new high-speed USB device number 33 using xhci_hcd
  [87390.072891] usb 1-5: New USB device found, idVendor=413c, idProduct=8442, 
bcdDevice= 1.00
  [87390.072897] usb 1-5: New USB device strings: Mfr=0, Product=0, 
SerialNumber=1
  [87390.072901] usb 1-5: SerialNumber: E9021071FBE1
  [87390.073934] hub 1-5:1.0: USB hub found
  [87390.074047] hub 1-5:1.0: 6 ports detected
  [87390.367780] usb 1-5.5: new high-speed USB device number 34 using xhci_hcd
  [87390.472473] usb 1-5.5: New USB device found, idVendor=0451, 
idProduct=82ff, bcdDevice= 2.00
  [87390.472479] usb 1-5.5: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
  [87390.475022] hid-generic 0003:0451:82FF.0014: hiddev0,hidraw1: USB HID 
v1.11 Device [HID 0451:82ff] on usb-:00:14.0-5.5/input0

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Wed Sep 16 09:40:10 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics [17aa:22be]
  InstallationDate: Installed on 2020-08-24 (22 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 20U9004PFR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=4a93b148-f388-4849-9a18-9e0e4d32c97a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9004PFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9004PFR:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9004PFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9004PFR
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895794/+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 1895665] Re: PulseAudio automatically switches from HDMI 2 after display sleep

2020-09-16 Thread Hui Wang

Do you mean even did the change of #2, the output device still changes
to internal analog audio after sleep? Before sleep, you select the hdmi-
output-2 manually?

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

Title:
  PulseAudio automatically switches from HDMI 2 after display sleep

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have an Nvidia based video card that has an HDMI output + a DisplayPort 
output.
  DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output 
is listed as "Digital Stereo (HDMI 2)".

  I prefer to use "Digital Stereo (HDMI 2)".
  But after each display sleep (screen lock for example) audio is switched to 
built in audio

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Sep 15 14:56:58 2020
  InstallationDate: Installed on 2020-06-20 (86 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.name: 0CNDTP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G5 5590
  dmi.product.sku: 08EA
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+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 1895382] Re: Ability to install 2 or more versions at once

2020-09-16 Thread Colin Watson

@skiphopjump, it's not OK to make personal attacks on other Launchpad
users this way (see https://ubuntu.com/community/code-of-conduct, but
also basic common courtesy).  Julian already warned you (I thought
rather mildly in the circumstances) that your language was
inappropriate, but you've been continuing to make aggressive comments
anyway.

I'm therefore suspending your Launchpad account.  It can be reactivated
if you commit to behaving civilly (you'll get a contact address when you
next try to log in) and to retracting your attacks on individual
developers here.

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

Title:
  Ability to install 2 or more versions at once

Status in apt package in Ubuntu:
  Invalid

Bug description:
  1) do not ask questions with two identical answers in a row
  2) ask user every time if multiple versions are present
  3) if the same answer was given twice in a row - remember choice

  The ideal solution should serve as an umbrella for all packaging
  tools.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1895382/+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 1894338] Re: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work

@hui.wang I cannot boot that kernel, since GRUB tells me that it "has
invalid signature".

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

Title:
  [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control
  buttons don't work

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  My earphones are the one coming with Samsung Galaxy S8 (here:
  https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung-
  earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04
  (dual-boot with Windows 10, Secure Boot enabled)

  Trying to set the volume from my earphones' controls doesn't work, no
  modification on the volume, the sound bar on Ubuntu doesn't appear in
  order to indicate volume change. I would like to change the master
  volume, or whatever my common laptop controls do when I up/down the
  volume controls on my earphones, like it happens on Windows 10. Why
  does the erroneous behavior of being unable to set volume from my
  earphones happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.10
  ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
  Uname: Linux 4.15.0-115-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jason  3523 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  4 23:29:52 2020
  InstallationDate: Installed on 2018-09-28 (706 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.0
  dmi.board.name: 02P5YY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7570
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894338/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-09-16 Thread dgoosens

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

hey guys
had a kernel update just a few minutes ago...
at first, suddenly bluetooth stoped working
rebooted still nothing (almost drove me nuts)
then, don't know why, figured, I'd shut down and boot up again

and guess what...
bluetooth was back
AND THE HSP/HFP IS NOW WORKING !

OS: PopOS 20.04
kernel: 5.4.0-7642-generic
laptop: Dell XPS15
headset: Bose QC (first edition)

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1895665] Re: PulseAudio automatically switches from HDMI 2 after display sleep

2020-09-16 Thread Andrii Puhalevich

After #2 it prefers HDMI 2 when its connected, thanks @hui.wang.
But seems that anyway it prefers internal analog audio instead of digital audio.
Will observe more to understand new behavior after reboots, suspends and locks.

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

Title:
  PulseAudio automatically switches from HDMI 2 after display sleep

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have an Nvidia based video card that has an HDMI output + a DisplayPort 
output.
  DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output 
is listed as "Digital Stereo (HDMI 2)".

  I prefer to use "Digital Stereo (HDMI 2)".
  But after each display sleep (screen lock for example) audio is switched to 
built in audio

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Sep 15 14:56:58 2020
  InstallationDate: Installed on 2020-06-20 (86 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.name: 0CNDTP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G5 5590
  dmi.product.sku: 08EA
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+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 1895794] [NEW] Plugging an external monitor on USB-C port does not show up. Need to reboot each time

2020-09-16 Thread Hai NGUYEN VAN

Public bug reported:

Whenever I plug an external monitor (Dell P2720DC) on my ThinkPad X1
(8th gen.) with Ubuntu 20.04, it is not directly recognized. I need to
reboot the system so that it can find the monitor. Here is an extract of
dmesg:

[87389.923632] usb 1-5: new high-speed USB device number 33 using xhci_hcd
[87390.072891] usb 1-5: New USB device found, idVendor=413c, idProduct=8442, 
bcdDevice= 1.00
[87390.072897] usb 1-5: New USB device strings: Mfr=0, Product=0, SerialNumber=1
[87390.072901] usb 1-5: SerialNumber: E9021071FBE1
[87390.073934] hub 1-5:1.0: USB hub found
[87390.074047] hub 1-5:1.0: 6 ports detected
[87390.367780] usb 1-5.5: new high-speed USB device number 34 using xhci_hcd
[87390.472473] usb 1-5.5: New USB device found, idVendor=0451, idProduct=82ff, 
bcdDevice= 2.00
[87390.472479] usb 1-5.5: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
[87390.475022] hid-generic 0003:0451:82FF.0014: hiddev0,hidraw1: USB HID v1.11 
Device [HID 0451:82ff] on usb-:00:14.0-5.5/input0

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: Unity
Date: Wed Sep 16 09:40:10 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics [17aa:22be]
InstallationDate: Installed on 2020-08-24 (22 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: LENOVO 20U9004PFR
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=4a93b148-f388-4849-9a18-9e0e4d32c97a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N2WET19W (1.09 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20U9004PFR
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9004PFR:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9004PFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon Gen 8
dmi.product.name: 20U9004PFR
dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
dmi.product.version: ThinkPad X1 Carbon Gen 8
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal thinkpadx1 ubuntu usbc

** Tags added: thinkpadx1 usbc

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

Title:
  Plugging an external monitor on USB-C port does not show up. Need to
  reboot each time

Status in xorg package in Ubuntu:
  New

Bug description:
  Whenever I plug an external monitor (Dell P2720DC) on my ThinkPad X1
  (8th gen.) with Ubuntu 20.04, it is not directly recognized. I need to
  reboot the system so that it can find the monitor. Here is an extract
  of dmesg:

  [87389.923632] usb 1-5: new high-speed USB device number 33 using xhci_hcd
  [87390.072891] usb 1-5: New USB device found, idVendor=413c, idProduct=8442, 
bcdDevice= 1.00
  [87390.072897] usb 1-5: New USB device strings: Mfr=0, Product=0, 
SerialNumber=1
  [87390.072901] usb 1-5: SerialNumber: E9021071FBE1
  [87390.073934] hub 1-5:1.0: USB hub found
  [87390.074047] hub 1-5:1.0: 6 ports detected
  [87390.367780] usb 1-5.5: new high-speed USB device number 34 using xhci_hcd
  [87390.472473] usb 1-5.5: New USB device found, idVendor=0451, 
idProduct=82ff, bcdDevice= 2.00
  [87390.472479] usb 1-5.5: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
  [87390.475022] hid-generic 0003:0451:82FF.0014: hiddev0,hidraw1: USB HID 
v1.11 Device [HID 0451:82ff] on usb-:00:14.0-5.5/input0

  ProblemType: Bug
  DistroRelease: Ubuntu

[Touch-packages] [Bug 1895757] Re: Terminal hangs running sudo when "use_pty" is set in /etc/sudoers

2020-09-16 Thread Alejandro Santoyo Gonzalez

** Description changed:

  An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs running
  a command using 'sudo' when 'use_pty' is set in /etc/sudoers.
  
  Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):
  
  1) Log in into an Ubuntu server (tested on 18.04.5 using SSH)
  2) Ensure that /etc/sudoers has the following line (add this line if not 
present)
  Defaults  use_pty
- 3) Execute the following:
+ 3) Execute the following (test 'sudo' command):
  for i in {1..10}; do sudo -- cat /var/log/syslog; done
  
  The terminal hangs and the following backtrace is obtained:
  
  (gdb) bt
  #0  0x7f751d5c8cc4 in __GI___poll (fds=0x55d0159917b0, nfds=1, 
timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
  #1  0x7f751d8b146a in poll (__timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
  #2  sudo_ev_scan_impl (base=base@entry=0x55d015990dc0, flags=flags@entry=0) 
at ../../../lib/util/event_poll.c:155
  #3  0x7f751d8aa74d in sudo_ev_loop_v1 (base=base@entry=0x55d015990dc0, 
flags=flags@entry=0) at ../../../lib/util/event.c:617
  #4  0x55d01570597a in del_io_events (nonblocking=nonblocking@entry=false) 
at ../../src/exec_pty.c:1537
  #5  0x55d015707b97 in pty_close (cstat=0x7ffd074d6110) at 
../../src/exec_pty.c:697
  #6  exec_pty (details=details@entry=0x55d01591e0e0 , 
cstat=cstat@entry=0x7ffd074d6110) at ../../src/exec_pty.c:1412
  #7  0x55d015701178 in sudo_execute (details=0x55d01591e0e0 
, cstat=0x7ffd074d6110) at ../../src/exec.c:391
  #8  0x55d01570e15b in run_command (details=0x55d01591e0e0 
) at ../../src/sudo.c:968
  #9  0x55d0156ff9a0 in main (argc=, argv=, 
envp=) at ../../src/sudo.c:294
  
  A similar (most likely the same) bug has been reported here
  https://access.redhat.com/solutions/3404401.

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

Title:
  Terminal hangs running sudo when "use_pty" is set in /etc/sudoers

Status in sudo package in Ubuntu:
  New

Bug description:
  An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs
  running a command using 'sudo' when 'use_pty' is set in /etc/sudoers.

  Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):

  1) Log in into an Ubuntu server (tested on 18.04.5 using SSH)
  2) Ensure that /etc/sudoers has the following line (add this line if not 
present)
  Defaults  use_pty
  3) Execute the following (test 'sudo' command):
  for i in {1..10}; do sudo -- cat /var/log/syslog; done

  The terminal hangs and the following backtrace is obtained:

  (gdb) bt
  #0  0x7f751d5c8cc4 in __GI___poll (fds=0x55d0159917b0, nfds=1, 
timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
  #1  0x7f751d8b146a in poll (__timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
  #2  sudo_ev_scan_impl (base=base@entry=0x55d015990dc0, flags=flags@entry=0) 
at ../../../lib/util/event_poll.c:155
  #3  0x7f751d8aa74d in sudo_ev_loop_v1 (base=base@entry=0x55d015990dc0, 
flags=flags@entry=0) at ../../../lib/util/event.c:617
  #4  0x55d01570597a in del_io_events (nonblocking=nonblocking@entry=false) 
at ../../src/exec_pty.c:1537
  #5  0x55d015707b97 in pty_close (cstat=0x7ffd074d6110) at 
../../src/exec_pty.c:697
  #6  exec_pty (details=details@entry=0x55d01591e0e0 , 
cstat=cstat@entry=0x7ffd074d6110) at ../../src/exec_pty.c:1412
  #7  0x55d015701178 in sudo_execute (details=0x55d01591e0e0 
, cstat=0x7ffd074d6110) at ../../src/exec.c:391
  #8  0x55d01570e15b in run_command (details=0x55d01591e0e0 
) at ../../src/sudo.c:968
  #9  0x55d0156ff9a0 in main (argc=, argv=, 
envp=) at ../../src/sudo.c:294

  A similar (most likely the same) bug has been reported here
  https://access.redhat.com/solutions/3404401.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1895757/+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 1895576] Re: boot-and-services in tests-in-lxd autopkgtest fails in groovy on s390x

The retries were reproducible failing as well.

[09:20]  rbalint: btw the test on s390x really seems still broken
[09:20]  we need either a fix or a test hint
[09:21] --> falcojr (~falcojr@184.55.64.152) has joined this channel.
[09:24]  cpaelzer, i'm ok with the hint and i've retriggered the tests 
with cryptsetup and glibc to see if they still help
[09:25]  ok rbalint, given you are the maintainer and you agree I 
think I'll prep a hint and once you ack there (for an audit trail) we can push 
it
[09:27]  cpaelzer, thanks, i'm also working on the next systemd point 
release but it shows regressions so it will take a few days

Here it is:
https://code.launchpad.net/~paelzer/britney/hints-ubuntu-groovy-systemd-s390x-fails/+merge/390809

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

Title:
  boot-and-services in tests-in-lxd autopkgtest fails in groovy on s390x

Status in systemd package in Ubuntu:
  New

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  groovy/groovy/s390x/s/systemd/20200903_184028_2bbdf@/log.gz

  ...
  test_rsyslog (__main__.ServicesTest) ... FAIL
  test_tmp_cleanup (__main__.ServicesTest) ... ok
  test_tmp_mount (__main__.ServicesTest) ... ok
  test_udev (__main__.ServicesTest) ... skipped 'udev does not work in 
containers'

  ==
  FAIL: test_rsyslog (__main__.ServicesTest)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.15TVnz/build.ZVh/real-tree/debian/tests/boot-and-services", 
line 120, in test_rsyslog
  self.assertRegex(log, 'systemd.*Reached target Graphical Interface')
  ...

  Interestingly it does not fail locally on an s390x Focal VM running 
boot-and-services in LXD.
  Kernel:
  Linux juju-d7a408-generic-21 5.4.0-14-generic 

  Also interestingly it is passing with cryptsetup/2:2.3.3-1ubuntu5
  glibc/2.32-0ubuntu2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895576/+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 1895576] Re: boot-and-services in tests-in-lxd autopkgtest fails in groovy on s390x

Old hints we only had:

# failing due to multiple reasons LP: #1892358
force-badtest systemd/246-2ubuntu1
# failing due to livecd-rootfs creating broken LXD images LP: #1877078
force-reset-test systemd/246.2-1ubuntu1

But was then removed in
revno: 4988
committer: Steve Langasek 
branch nick: hints-ubuntu
timestamp: Fri 2020-09-11 13:38:38 -0700
message:
  drop unused hints; fix typo in package name


Maybe that rule let the packages pass that I wondered about, but it is unclear 
what made 246.4-1ubuntu1 itself pass as there was no good run of that either 
?!?.

Overall for now it seems to me that we'd have to add:
force-badtest systemd/246.4-1ubuntu1/s390x

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

Title:
  boot-and-services in tests-in-lxd autopkgtest fails in groovy on s390x

Status in systemd package in Ubuntu:
  New

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  groovy/groovy/s390x/s/systemd/20200903_184028_2bbdf@/log.gz

  ...
  test_rsyslog (__main__.ServicesTest) ... FAIL
  test_tmp_cleanup (__main__.ServicesTest) ... ok
  test_tmp_mount (__main__.ServicesTest) ... ok
  test_udev (__main__.ServicesTest) ... skipped 'udev does not work in 
containers'

  ==
  FAIL: test_rsyslog (__main__.ServicesTest)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.15TVnz/build.ZVh/real-tree/debian/tests/boot-and-services", 
line 120, in test_rsyslog
  self.assertRegex(log, 'systemd.*Reached target Graphical Interface')
  ...

  Interestingly it does not fail locally on an s390x Focal VM running 
boot-and-services in LXD.
  Kernel:
  Linux juju-d7a408-generic-21 5.4.0-14-generic 

  Also interestingly it is passing with cryptsetup/2:2.3.3-1ubuntu5
  glibc/2.32-0ubuntu2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895576/+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 1895576] Re: boot-and-services in tests-in-lxd autopkgtest fails in groovy on s390x

Also please do note that while almost all of the recent tests failed - almost 
all of the packages already migrated. Why is that - there is no test hint in 
place.
For example gdm3/3.37.90-1ubuntu1 and iptables/1.8.4-3ubuntu3 (but more than 
just those, policykit-1, dpdk, util-linux, ...) NEVER had a valid test [1], but 
they migrated to groovy-release.
That seems even more wrong, any idea why/how that happened?

There might be a follow up issue of people using tools that "retry
everything that had no good run" but since somehow things magically
migrated the recent long retry-lists mostly contain packages that are
already migrated.

For the sake of seeing if it might be "blunt retries" and since the s390x test 
queue is empty I'm retrying it multiple times (hopefully those won't be 
coalesced).
The last not-yet weird-migrated entry is apparmor.

[1]: https://autopkgtest.ubuntu.com/packages/s/systemd/groovy/s390x

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

Title:
  boot-and-services in tests-in-lxd autopkgtest fails in groovy on s390x

Status in systemd package in Ubuntu:
  New

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  groovy/groovy/s390x/s/systemd/20200903_184028_2bbdf@/log.gz

  ...
  test_rsyslog (__main__.ServicesTest) ... FAIL
  test_tmp_cleanup (__main__.ServicesTest) ... ok
  test_tmp_mount (__main__.ServicesTest) ... ok
  test_udev (__main__.ServicesTest) ... skipped 'udev does not work in 
containers'

  ==
  FAIL: test_rsyslog (__main__.ServicesTest)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.15TVnz/build.ZVh/real-tree/debian/tests/boot-and-services", 
line 120, in test_rsyslog
  self.assertRegex(log, 'systemd.*Reached target Graphical Interface')
  ...

  Interestingly it does not fail locally on an s390x Focal VM running 
boot-and-services in LXD.
  Kernel:
  Linux juju-d7a408-generic-21 5.4.0-14-generic 

  Also interestingly it is passing with cryptsetup/2:2.3.3-1ubuntu5
  glibc/2.32-0ubuntu2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895576/+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 1895789] [NEW] rfkill hangs when turn on/off bluetooth

2020-09-16 Thread Taiten Peng

Public bug reported:

Turn on/off leads to a kernel panic related to rfkill

Hardware ID: 201712-26024

OS: 20.04 Desktop
Kernel: 5.4.0-48-generic

Step to reproduce: 
1. Click on/off in the bluetooth settings for a few time
2. Oberserve kernel message as following 

[  126.914032] [ cut here ]
[  126.914034] kernel BUG at mm/slub.c:306!
[  126.914041] invalid opcode:  [#1] SMP PTI
[  126.914044] CPU: 6 PID: 4741 Comm: gsd-rfkill Tainted: P   OE 
5.4.0-48-generic #52-Ubuntu
[  126.914045] Hardware name: Dell Inc. XPS 13 9370/0173S1, BIOS 1.13.1 
07/08/2020
[  126.914050] RIP: 0010:__slab_free+0x189/0x330
[  126.914052] Code: 00 48 89 c7 fa 66 0f 1f 44 00 00 f0 49 0f ba 2c 24 00 72 
65 4d 3b 6c 24 20 74 11 49 0f ba 34 24 00 57 9d 0f 1f 44 00 00 eb 9f <0f> 0b 49 
3b 5c 24 28 75 e8 48 8b 44 24 28 49 89 4c 24 28 49 89 44
[  126.914054] RSP: 0018:b46f42d73c90 EFLAGS: 00010246
[  126.914056] RAX: 9c6931960a00 RBX: 80200015 RCX: 9c6931960a00
[  126.914057] RDX: 9c6931960a00 RSI: e19511c65800 RDI: 9c695bff9340
[  126.914058] RBP: b46f42d73d28 R08: 0001 R09: a4d1b6be
[  126.914059] R10: 9c6931960a00 R11: 0001 R12: e19511c65800
[  126.914060] R13: 9c6931960a00 R14: 9c695bff9340 R15: 9c695bff9340
[  126.914062] FS:  7fbd905bf840() GS:9c695e58() 
knlGS:
[  126.914063] CS:  0010 DS:  ES:  CR0: 80050033
[  126.914064] CR2: 7fc51ed2 CR3: 0003e6012002 CR4: 003606e0
[  126.914066] DR0:  DR1:  DR2: 
[  126.914067] DR3:  DR6: fffe0ff0 DR7: 0400
[  126.914068] Call Trace:
[  126.914072]  ? finish_wait+0x59/0x70
[  126.914075]  ? wait_woken+0x80/0x80
[  126.914078]  ? kfree_skbmem+0x4e/0x60
[  126.914080]  kmem_cache_free+0x288/0x2b0
[  126.914085]  ? btusb_shutdown_intel_new+0x36/0x60 [btusb]
[  126.914087]  kfree_skbmem+0x4e/0x60
[  126.914089]  kfree_skb+0x3a/0xa0
[  126.914092]  btusb_shutdown_intel_new+0x36/0x60 [btusb]
[  126.914108]  hci_dev_do_close+0x40c/0x520 [bluetooth]
[  126.914121]  hci_rfkill_set_block+0x56/0xa0 [bluetooth]
[  126.914124]  rfkill_set_block+0x9b/0x150
[  126.914127]  rfkill_fop_write+0x136/0x1e0
[  126.914130]  __vfs_write+0x1b/0x40
[  126.914131]  vfs_write+0xb9/0x1a0
[  126.914134]  ksys_write+0xb1/0xe0
[  126.914136]  __x64_sys_write+0x1a/0x20
[  126.914139]  do_syscall_64+0x57/0x190
[  126.914142]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  126.914144] RIP: 0033:0x7fbd9097021f
[  126.914146] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 59 65 f8 ff 48 
8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 8c 65 f8 ff 48
[  126.914147] RSP: 002b:7fffd6047f00 EFLAGS: 0293 ORIG_RAX: 
0001
[  126.914149] RAX: ffda RBX: 7fbd905bf7c0 RCX: 7fbd9097021f
[  126.914150] RDX: 0008 RSI: 5581c4fe4dd0 RDI: 0008
[  126.914151] RBP: 7fffd6047f50 R08:  R09: 000b
[  126.914152] R10: 5581c4fd3dc8 R11: 0293 R12: 0001
[  126.914153] R13: 7fffd6047fb0 R14:  R15: 5581c4fd6020
[  126.914155] Modules linked in: thunderbolt veth nft_masq nft_chain_nat uhid 
rfcomm vboxnetadp(OE) xt_CHECKSUM vboxnetflt(OE) xt_MASQUERADE xt_tcpudp 
vboxdrv(OE) bridge stp llc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) 
znvpair(PO) spl(O) zlua(PO) ebtable_filter ebtables ip6table_raw 
ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_raw 
iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
libcrc32c iptable_filter bpfilter nf_tables nfnetlink ccm aufs cmac algif_hash 
algif_skcipher af_alg overlay bnep hid_logitech_hidpp typec_displayport 
hid_logitech_dj hid_apple binfmt_misc ftdi_sio usbserial snd_usb_audio 
snd_usbmidi_lib mei_hdcp intel_rapl_msr snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_intel_dspcfg 
snd_hda_codec x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_core 
dell_laptop ledtrig_audio snd_hwdep kvm_intel joydev snd_pcm snd_seq_midi 
snd_seq_midi_event dell_wmi kvm crct10dif_pclmul dell_smbios
[  126.914188]  dcdbas snd_rawmidi nls_iso8859_1 cdc_ether ghash_clmulni_intel 
usbnet aesni_intel r8152 crypto_simd mii snd_seq iwlmvm cryptd glue_helper 
snd_seq_device intel_wmi_thunderbolt wmi_bmof dell_wmi_descriptor rapl 
snd_timer intel_cstate mac80211 btusb btrtl btbcm uvcvideo input_leds btintel 
libarc4 videobuf2_vmalloc bluetooth serio_raw videobuf2_memops videobuf2_v4l2 
videobuf2_common videodev iwlwifi ecdh_generic cdc_acm mc ecc i915 snd cfg80211 
soundcore rtsx_pci_ms mei_me memstick drm_kms_helper hid_multitouch mei 
ucsi_acpi typec_ucsi i2c_algo_bit fb_sys_fops processor_thermal_device 
intel_xhci_usb_role_switch syscopyarea

[Touch-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones

2020-09-16 Thread Tanguy

Same issue here on HP Pavilion Gaming Laptop 15-cx0xxx
5.8.6-1-MANJARO x86_64

With low quality earphone, don't have crackling
With high quality earphone, have crackling in left side
This high quality earphone doesn't have any crackling on other devices.

Robertjjoynt's solution fixed the problem.

Thanks.

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  New
Status in alsa-driver package in Arch Linux:
  New
Status in Fedora:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+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 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-16 Thread Rocko

Doesn't systemd normally stop trying to start a service if it fails too
often? That's clearly not happening here, though.

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

Title:
  systemd 100% cpu usage apport-autoreport.service: Failed with result
  'start-limit-hit'

Status in apport package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in apport source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  New

Bug description:
  after upgrade from Ubuntu 20.04 to 20.10  
  seeing systemd use 100% cpu forever


  top

top - 10:16:19 up 20 min,  1 user,  load average: 3.91, 4.28, 3.39
Tasks: 332 total,   2 running, 330 sleeping,   0 stopped,   0 zombie
%Cpu(s): 18.7 us,  6.4 sy, 11.9 ni, 62.2 id,  0.0 wa,  0.0 hi,  0.8 si, 
 0.0 st
MiB Mem :  15917.6 total,   8553.4 free,   2604.3 used,   4759.9 
buff/cache
MiB Swap:   2048.0 total,   2048.0 free,  0.0 used.  12633.7 avail 
Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ 
COMMAND  
  1 root  20   0  177316  12252   8684 R 100.0   0.1  15:01.25 
systemd  
   4636 kush  39  19  633796 176152  16360 S  98.3   1.1  17:51.56 
tracker-miner-f  
820 message+  20   0   10740   6452   4212 S  39.8   0.0   6:19.06 
dbus-daemon  
316 root  19  -1  535916 322896 320824 S  15.3   2.0   3:16.41 
systemd-journal  
844 syslog20   0  221136   5840   3920 S  13.6   0.0   2:14.52 
rsyslogd 
858 root  20   0   83708  74124   7568 S  12.7   0.5   2:06.98 
systemd-logind   
  5 root  20   0   0  0  0 I   3.4   0.0   0:05.01 
kworker/0:0-events   
  35566 kush  20   0 3850088 588344 262192 S   2.5   3.6   0:30.48 
MainThread   
   5626 kush  20   0 5004788 260876  93400 S   1.7   1.6   3:05.19 
gnome-shell  
   7033 kush  20   0  869792  66440  44272 S   1.7   0.4   0:06.05 
gnome-terminal-  
  36790 kush  20   0 2525432 156636  98568 S   1.7   1.0   0:04.99 
Web Content  
957 root  20   0 1556196  45044  24284 S   0.8   0.3   0:02.48 
containerd   
   1038 root  20   0   10460   4412   3300 S   0.8   0.0   0:00.16 
fancontrol   



  
sudo tail -n 100 /var/log/syslog
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17

[Touch-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

And on Bionic we only need to do so for amd64
Here is a new MP for Bionic:
https://code.launchpad.net/~paelzer/britney/hints-ubuntu-bionic-disable-systemd-v2/+merge/390793

** Branch linked: lp:~paelzer/britney/hints-ubuntu-bionic-disable-
systemd-v2

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in build-essential package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid
Status in iputils package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Invalid
Status in ntpsec package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Invalid
Status in linux-meta source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in build-essential source package in Focal:
  Confirmed
Status in linux-meta source package in Focal:
  New
Status in qemu source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in util-linux source package in Focal:
  Confirmed

Bug description:
  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services  (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-smoke (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  logind (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  storage(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  upstream   (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFBFF.B.F.F..FFBF
  udev   (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  systemd-fsckd  (F 37% S  0% B 10% => P 50%/) 
BFFFB.FF...FB.F..B.
  root-unittests (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
ppc64el
  tests-in-lxd   (F 25% S  0% B  0% => P 75%/) 
FFFFF.F.
  systemd-fsckd  (F 35% S  0% B  0% => P 65%/) 
FFF...FFFFF.F..F
  root-unittests (F  2% S  0% B  0% => P 97%/) 
..F.
s390x
  tests-in-lxd   (F 52% S  0% B  0% => P 47%/) 
FFF.FFF.FF....F.
  timedated  (F  2% S  0% B  0% => P 97%/) 
...F
  upstream   (F 17% S  0% B  0% => P 82%/) 
.F..F.F.FFF...F.
  systemd-fsckd  (F 32% S  0% B  0% => P 67%/) 
FFF..FF..F.FF..F
  root-unittests (F 10% S  0% B  0% => P 90%/) 
FFF...F.
arm64
  tests-in-lxd   (F 40% S  0% B  2% => P 57%/) 
F.B...FFF.FF..F..F.FFF.F
  logind (F  2% S  0% B  2% => P 95%/) 
..B...F.
  upstream   (F 22% S  0% B  2% => P 75%/) 
...F.FB.F.F.F..FFF.F
  root-unittests (F 12% S  0% B  2% => P 85%/) 
..B.F...F.FF...F

  (I'm sure LP will make this unreadable, but is is nice in monospace)

  Whatever the root cause is - the success rate of these has reduced so
  much that the (even formerly questionable) practice of retry-until-
  success won't work anymore.

  
  I have run the two tests in a local VM and systemd-fsckd works there while 
tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services".

  We had the discussion in the past, but I think I need to again bring
  up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until

[Touch-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

The problem with Xenial is that there it isn't just flaky "systemd-
fsckd" much more seems to be broken. I'll revise my Bionic MP, but for
Xenial I'd like to hear from ddstreet/rbalint how they think we should
go on there ...

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in build-essential package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid
Status in iputils package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Invalid
Status in ntpsec package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Invalid
Status in linux-meta source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in build-essential source package in Focal:
  Confirmed
Status in linux-meta source package in Focal:
  New
Status in qemu source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in util-linux source package in Focal:
  Confirmed

Bug description:
  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services  (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-smoke (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  logind (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  storage(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  upstream   (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFBFF.B.F.F..FFBF
  udev   (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  systemd-fsckd  (F 37% S  0% B 10% => P 50%/) 
BFFFB.FF...FB.F..B.
  root-unittests (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
ppc64el
  tests-in-lxd   (F 25% S  0% B  0% => P 75%/) 
FFFFF.F.
  systemd-fsckd  (F 35% S  0% B  0% => P 65%/) 
FFF...FFFFF.F..F
  root-unittests (F  2% S  0% B  0% => P 97%/) 
..F.
s390x
  tests-in-lxd   (F 52% S  0% B  0% => P 47%/) 
FFF.FFF.FF....F.
  timedated  (F  2% S  0% B  0% => P 97%/) 
...F
  upstream   (F 17% S  0% B  0% => P 82%/) 
.F..F.F.FFF...F.
  systemd-fsckd  (F 32% S  0% B  0% => P 67%/) 
FFF..FF..F.FF..F
  root-unittests (F 10% S  0% B  0% => P 90%/) 
FFF...F.
arm64
  tests-in-lxd   (F 40% S  0% B  2% => P 57%/) 
F.B...FFF.FF..F..F.FFF.F
  logind (F  2% S  0% B  2% => P 95%/) 
..B...F.
  upstream   (F 22% S  0% B  2% => P 75%/) 
...F.FB.F.F.F..FFF.F
  root-unittests (F 12% S  0% B  2% => P 85%/) 
..B.F...F.FF...F

  (I'm sure LP will make this unreadable, but is is nice in monospace)

  Whatever the root cause is - the success rate of these has reduced so
  much that the (even formerly questionable) practice of retry-until-
  success won't work anymore.

  
  I have run the two tests in a local VM and systemd-fsckd works there while 
tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services".

  We had the discussion in the past, but I think I need to again bring
  up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until
  they are on reasonable

[Touch-packages] [Bug 1895576] Re: boot-and-services in tests-in-lxd autopkgtest fails in groovy on s390x

@Rbalint - hi the two most recent tests confirm that it still seems broken.
Maybe the good run was a one-off lucky run ... :-/

I'd ask you to look into that a bit deeper as it will again hold back
plenty of things in groovy soon.

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

Title:
  boot-and-services in tests-in-lxd autopkgtest fails in groovy on s390x

Status in systemd package in Ubuntu:
  New

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  groovy/groovy/s390x/s/systemd/20200903_184028_2bbdf@/log.gz

  ...
  test_rsyslog (__main__.ServicesTest) ... FAIL
  test_tmp_cleanup (__main__.ServicesTest) ... ok
  test_tmp_mount (__main__.ServicesTest) ... ok
  test_udev (__main__.ServicesTest) ... skipped 'udev does not work in 
containers'

  ==
  FAIL: test_rsyslog (__main__.ServicesTest)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.15TVnz/build.ZVh/real-tree/debian/tests/boot-and-services", 
line 120, in test_rsyslog
  self.assertRegex(log, 'systemd.*Reached target Graphical Interface')
  ...

  Interestingly it does not fail locally on an s390x Focal VM running 
boot-and-services in LXD.
  Kernel:
  Linux juju-d7a408-generic-21 5.4.0-14-generic 

  Also interestingly it is passing with cryptsetup/2:2.3.3-1ubuntu5
  glibc/2.32-0ubuntu2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895576/+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 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration