[Touch-packages] [Bug 1660121] Re: LightDM can't use the user background on Mate

[Sai Vinoba]

** Tags added: focal

** Tags added: groovy

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

Title:
  LightDM can't use the user background on Mate

Status in Ubuntu MATE:
  New
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu Mate 16.10 (the issue appears too on 16.04 and 17.04
  alpha 2).

  On Mate, the LightDM Gtk Greeter can't use the user background. It
  works fine on other DEs like Xfce.

  From what I understand, LightDM and/or the Gkt greeter (not sure which
  one handles the background) gets the background path from Gsettings,
  so I assume it can't find the one from Mate, which stores it in
  "org.mate.background picture-filename".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1660121/+subscriptions

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

[Touch-packages] [Bug 1901808] [NEW] no acceleration on Intel HD 4400

[Aidar Khabirov]

Public bug reported:

I have laptop dell  with intel i5-4100U,  intel hd 4400 and geforce 820m on 
board.
I added zotac gtx 960 and one monitor via rizer. 
gtx and monitor worked correctly.
but laptop displays has lags and tearing.
I tried install  
i915
i965-va-drivers


intel config section
Section "Device"
Identifier "Device1"
Driver "intel"
VendorName "Intel Corporation"
Option "TearFree" "true"
Option "DRI" "2"
EndSection

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
.proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
.proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:06: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  455.32.00  Wed Oct 14 22:46:18 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: Deepin
Date: Wed Oct 28 11:03:01 2020
DistUpgraded: 2020-08-20 21:43:47,424 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0652]
 NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GM206 [GeForce GTX 960] [19da:2378]
   Subsystem: Dell GeForce 820M [1028:0652]
InstallationDate: Installed on 2020-07-16 (103 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: Dell Inc. Inspiron 3542
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-52-generic 
root=UUID=ab9e3a31-2ad4-4c5f-a786-92ff7dbde56d ro rootflags=subvol=@ 
nouveau.modeset=0 DEEPIN_GFXMODE= crashkernel=512M-:192M
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-08-20 (68 days ago)
dmi.bios.date: 03/28/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.name: 0926J6
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd03/28/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0926J6:rvrA01:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3542
dmi.product.sku: 0652
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal third-party-packages 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/1901808

Title:
  no acceleration on Intel HD 4400

Status in xorg package in Ubuntu:
  New

Bug description:
  I have laptop dell  with intel i5-4100U,  intel hd 4400 and geforce 820m on 
board.
  I added zotac gtx 960 and one monitor via rizer. 
  gtx and monitor worked correctly.
  but laptop displays has lags and tearing.
  I tried install  
  i915
  i965-va-drivers

  
  intel config section
  Section "Device"
  Identifier "Device1"
  Driver "intel"
  VendorName "Intel Corporation"
  Option   "TearFree" "true"
  Option "DRI" "2"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/dr

[Touch-packages] [Bug 1246981] Re: Bluetooth devices fail to re-connect after sleep.

[Kai-Heng Feng]

If it's a kernel regression, please bisect the kernel:
https://wiki.ubuntu.com/Kernel/KernelBisection

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

Title:
  Bluetooth devices fail to re-connect after sleep.

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This exact harware was working faultlessly in 13.04. Since re-
  installing at 13.10 the mouse consistently failes to reconnect after
  the device either hybernates or ever goes to screen saver sleep.

  I have to remove the dive and re-add it each time (which works well).

  There are other issues with the bluetooth stack as well in that I have
  not found any way to use bluetooth tethering to my mobile which again
  worked well and was easy to configure in 13.04

  Peter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov  1 16:44:37 2013
  InstallationDate: Installed on 2013-10-19 (13 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Dell Inc. Latitude E6530
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 20:16:D8:9C:38:E5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0
TX bytes:37955 acl:131 sco:0 commands:5096 errors:0
  syslog:
   Nov  1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 
0x7f6489f7b450 with :1.582 activated
   Nov  1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command 
complete for opcode 37
   Nov  1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft 
Bluetooth Notebook Mouse 5000 as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 
0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft 
Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5

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

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

[Touch-packages] [Bug 1246981] Re: Bluetooth devices fail to re-connect after sleep.

[Tessa]

Well, that's sort of irrelevant for those of us having this problem. I
just checked, and mine is a Broadcom BCM20702A0, so not exactly a niche
vendor. I'm especially concerned since it seems like it's just not
correctly re-scanning for bluetooth devices after waking from sleep due
to some sort of software screw up since the 20.10 update, and there's
nothing wrong with the controller. For those of us who depend on
bluetooth, this is a major regression.

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

Title:
  Bluetooth devices fail to re-connect after sleep.

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This exact harware was working faultlessly in 13.04. Since re-
  installing at 13.10 the mouse consistently failes to reconnect after
  the device either hybernates or ever goes to screen saver sleep.

  I have to remove the dive and re-add it each time (which works well).

  There are other issues with the bluetooth stack as well in that I have
  not found any way to use bluetooth tethering to my mobile which again
  worked well and was easy to configure in 13.04

  Peter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov  1 16:44:37 2013
  InstallationDate: Installed on 2013-10-19 (13 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Dell Inc. Latitude E6530
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 20:16:D8:9C:38:E5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0
TX bytes:37955 acl:131 sco:0 commands:5096 errors:0
  syslog:
   Nov  1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 
0x7f6489f7b450 with :1.582 activated
   Nov  1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command 
complete for opcode 37
   Nov  1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft 
Bluetooth Notebook Mouse 5000 as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 
0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft 
Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5

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

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

[Touch-packages] [Bug 1901694] Re: [radeon] No hardware acceleration on AMD Seymour [Radeon HD 6400M/7400M Series]

[Timo Aaltonen]

[39.611] (II) AIGLX: Screen 0 is not DRI2 capable
[39.611] (EE) AIGLX: reverting to software rendering

16.04 is just old and you're not getting any (gfx) updates there anymore
at this point

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

Title:
  [radeon] No hardware acceleration on AMD Seymour [Radeon HD
  6400M/7400M Series]

Status in mesa package in Ubuntu:
  New

Bug description:
  Computer HP EliteBook 8460p. It uses hybrid graphics card. Processor Intel 
Core i5-2520M CPU @ 2.50GHz × 4; 2nd generation. The system only runs well with 
llvmpipe (LLVM 6.0, 256 bits) graphic software, AMD Caicos sometimes it's 
charged too, but the graphic display have problems and don't goes fine or fluid.
  Maybe there is no support for the processor graphics because It's a little 
bit old. I don't know how to install AMD proprietary drivers, It maybe solve 
the problem.
  I installed Ubuntu 20.04 LTS but don't works, It don't charge any graphic 
interface, only a black screen. I only uses the system in recovery mode. For 
that reason I returned to Ubuntu 16.04 LTS but my graphics don't have hardware 
acceleration, only software acceleration. When I tried to play (Super Tux Kart 
for example) I expected a berry poor graphic improvement, so I can't play It.
  Thanks for your time and attention!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-122.124~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-122-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.24
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Oct 27 05:47:39 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e]
  InstallationDate: Installed on 2020-10-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 
(20200806)
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcEnviron:
   LANGUAGE=es_CR:es
   PATH=(custom, no user)
   LANG=es_CR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-122-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.60
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.asset.tag: IS09189
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.60:bd03/12/2015:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8460p
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Oct 27 05:43:49 2020
  xserver.configfile: default
  xserver.errors: AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.4
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1766108] Re: Battery indicator crashes when unchecking "Show Percentage in Menu Bar"

[Launchpad Bug Tracker]

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

** Changed in: ayatana-indicator-power (Ubuntu)
   Status: New => Confirmed

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

Title:
  Battery indicator crashes when unchecking "Show Percentage in Menu
  Bar"

Status in Ubuntu MATE:
  New
Status in ayatana-indicator-power package in Ubuntu:
  Confirmed
Status in indicator-power package in Ubuntu:
  Confirmed
Status in mate-indicator-applet package in Ubuntu:
  Confirmed
Status in mate-panel package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:

  1. Click on the battery indicator.
  2. Click "Show Percentage on Menu Bar" to enable it.
  3. Do it again to disable it.
  4. Battery indicator disappears

  
  Output from dmesg:

  [  613.877855] mate-panel[1604]: segfault at 1c ip 7f51b23daa20 sp 
7ffe8df7f5d8 error 4 in libcairo.so.2.11510.0[7f51b236c000+118000]
  [  749.662960] mate-panel[2930]: segfault at 38 ip 7fc98aa82300 sp 
7fffa5290f68 error 4 in libgdk-3.so.0.2200.30[7fc98aa3b000+eb000]
  [  775.815530] mate-panel[3127]: segfault at 1c ip 7fc317b61a20 sp 
7ffea6e1f028 error 4 in libcairo.so.2.11510.0[7fc317af3000+118000]
  [  816.504199] mate-panel[3225]: segfault at 38 ip 7fa314f0e300 sp 
7fffa993f928 error 4 in libgdk-3.so.0.2200.30[7fa314ec7000+eb000]
  [  841.353444] mate-panel[3363]: segfault at 38 ip 7fbc86c4a300 sp 
7ffd6b3a5d58 error 4 in libgdk-3.so.0.2200.30[7fbc86c03000+eb000]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1766108/+subscriptions

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

[Touch-packages] [Bug 1897934] Autopkgtest regression report (alsa-lib/1.2.2-2.1ubuntu2.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted alsa-lib (1.2.2-2.1ubuntu2.1) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#alsa-lib

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [SRU][Intel HDA] The initial sound level is set to zero (muted)

Status in Release Notes for Ubuntu:
  Invalid
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Fail to run '/usr/sbin/alsactl restore' on the HDA-Intel machines, this
  results in the failure on setting the init mixer values for HDA sound
  card, and users experience the mute of audio after installing the 20.10.  

  [Fix]
  Backport a patch from the latest alsa-lib (v1.2.3+)

  [Test]
  Without the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*;
  sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is
  muted.

  Install the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*;
  sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is
  not muted.

  [Regression Potential]
  This could make the ucm audio fail to initialize, but this possibility is
  very low, since this patch is from upstream, and I tested on a ucm based
  machine, the audio is good.

  
  On boot into the live session - or on first install the sound level is muted.

  I have to use GNOME Control Center - Sounds to change to an
  appropriate level.  Once changed the level chosen is correctly
  retained between reboots.

  This appears to be a regression from 20.04 where the sound level was
  set to - I guess - 80% on the live-session/first install

  ProblemType: BugDistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu11
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-budgie   5041 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: Budgie:GNOME
  Date: Wed Sep 30 16:03:08 2020
  LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2016
  dmi.bios.release: 15.31
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.22
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+subscriptions

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

[Touch-packages] [Bug 1246981] Re: Bluetooth devices fail to re-connect after sleep.

[Kai-Heng Feng]

That means the bluetooth controller really wakes up after started a
scanning.

Recent BT 4.0 controllers from Intel or Qualcomm shouldn't have this
bug.

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

Title:
  Bluetooth devices fail to re-connect after sleep.

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This exact harware was working faultlessly in 13.04. Since re-
  installing at 13.10 the mouse consistently failes to reconnect after
  the device either hybernates or ever goes to screen saver sleep.

  I have to remove the dive and re-add it each time (which works well).

  There are other issues with the bluetooth stack as well in that I have
  not found any way to use bluetooth tethering to my mobile which again
  worked well and was easy to configure in 13.04

  Peter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov  1 16:44:37 2013
  InstallationDate: Installed on 2013-10-19 (13 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Dell Inc. Latitude E6530
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 20:16:D8:9C:38:E5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0
TX bytes:37955 acl:131 sco:0 commands:5096 errors:0
  syslog:
   Nov  1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 
0x7f6489f7b450 with :1.582 activated
   Nov  1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command 
complete for opcode 37
   Nov  1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft 
Bluetooth Notebook Mouse 5000 as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 
0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft 
Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5

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

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

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

[Yuan-Chen Cheng]

It exists in queue
https://launchpad.net/ubuntu/focal/+queue?queue_state=1&queue_text=network,
which is network manager 1.22.10-1ubuntu2.2.

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

Title:
  The network manager does not check the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

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

Bug description:
  [Impact]

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

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

   The killer 500s Wi-Fi does not want the network-manger to manager the
  wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set.
  (The driver will manager itself.) When the network-manager managers
  the wake-on-LAN, all of the Wi-Fi functions will be lost after the OS
  resumed from suspend.

  [Test Case]

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

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

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

  [Regression Potential]

   * This patch modifies the wake on lan parameters, please test that
  the corresponding feature still works fine with the different
  configuration values.

   1. Magic packet test:
    Set Wake on Wireless to off
    Send magic packet to the system
    Ensure it does not wake up

    Set Wake on Wirless to on
    Send magic packet to the system
    Ensure it does wake up

   2. Wi-Fi function test after resumed from suspend:
    After resume from suspend, the Wi-Fi should work normally.
    Scan APs.
    Connect to an AP.

  [Other Info]

   * platform: add the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE status
  check (!597) · Merge Requests · NetworkManager / NetworkManager ·
  GitLab -
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/597#note_588639

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

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

[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Hui Wang]

@Marco,

What the bluetooth module on your machine? Could you please upload the
vendor ID:device ID like #49?

thx.

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-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-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1901736] Re: Freeze

[Daniel van Vugt]

This sounds like either bug 1896110 or bug 1874578. Do you think?

** Summary changed:

- Xorg freeze
+ Freeze

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

** Changed in: gnome-shell-extension-ubuntu-dock (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/1901736

Title:
  Freeze

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

Bug description:
  Most of the time Ubuntu boots the  dock seems to freeze and not load
  any icons, sometimes for up to a minute. When this happens the dock
  will not appear when any window is maximized.

  Once in a while Ubuntu loads without a problem. The dock loads
  instantly and has no problem behind a maximized window.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 27 12:35:14 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Iris Plus Graphics 640 [8086:5926] (rev 06) (prog-if 00 
[VGA controller])
 Subsystem: Intel Corporation Iris Plus Graphics 640 [8086:2068]
  InstallationDate: Installed on 2020-09-16 (41 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Intel(R) Client Systems NUC7i5BNK
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=50f7562f-c44b-4a47-b1b4-02bdd6281c08 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0080.2019.0725.1139
  dmi.board.name: NUC7i5BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31144-314
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0080.2019.0725.1139:bd07/25/2019:svnIntel(R)ClientSystems:pnNUC7i5BNK:pvrJ31159-315:rvnIntelCorporation:rnNUC7i5BNB:rvrJ31144-314:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: BN
  dmi.product.name: NUC7i5BNK
  dmi.product.version: J31159-315
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1901736/+subscriptions

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

[Touch-packages] [Bug 1901694] Re: [radeon] No hardware aceleration

[Daniel van Vugt]

It appears the Xorg radeon driver is working. It's only 3D that's not
working so that's Mesa.

** Summary changed:

- No hardware aceleration
+ [radeon] No hardware aceleration

** Summary changed:

- [radeon] No hardware aceleration
+ [radeon] No hardware acceleration

** Tags added: radeon

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

** Summary changed:

- [radeon] No hardware acceleration
+ [radeon] No hardware acceleration on AMD Seymour [Radeon HD 6400M/7400M 
Series]

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

Title:
  [radeon] No hardware acceleration on AMD Seymour [Radeon HD
  6400M/7400M Series]

Status in mesa package in Ubuntu:
  New

Bug description:
  Computer HP EliteBook 8460p. It uses hybrid graphics card. Processor Intel 
Core i5-2520M CPU @ 2.50GHz × 4; 2nd generation. The system only runs well with 
llvmpipe (LLVM 6.0, 256 bits) graphic software, AMD Caicos sometimes it's 
charged too, but the graphic display have problems and don't goes fine or fluid.
  Maybe there is no support for the processor graphics because It's a little 
bit old. I don't know how to install AMD proprietary drivers, It maybe solve 
the problem.
  I installed Ubuntu 20.04 LTS but don't works, It don't charge any graphic 
interface, only a black screen. I only uses the system in recovery mode. For 
that reason I returned to Ubuntu 16.04 LTS but my graphics don't have hardware 
acceleration, only software acceleration. When I tried to play (Super Tux Kart 
for example) I expected a berry poor graphic improvement, so I can't play It.
  Thanks for your time and attention!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-122.124~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-122-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.24
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Oct 27 05:47:39 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e]
  InstallationDate: Installed on 2020-10-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 
(20200806)
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcEnviron:
   LANGUAGE=es_CR:es
   PATH=(custom, no user)
   LANG=es_CR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-122-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.60
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.asset.tag: IS09189
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.60:bd03/12/2015:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8460p
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Oct 27 05:43:49 2020
  xserver.configfile: default
  xserver.errors: AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.4
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1901413] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

** Tags added: focal

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

Title:
  Sound Blaster Audigy 5/Rx cannot be configured as input/output

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

Bug description:
  I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I 
cannot use it as both input and output device: it's working either as output or 
as input but not as input/output.
  I have installed "pavucontrol", when opening it in "configure" there are 
different options:

  Output "Analog Stereo"
  Output "Digital Stereo (IEC958)"
  Output "Surround 5.1"
  Output "Surround 4.1"
  Output "Surround 2.1"
  Output "Surround 7.1"
  Output "Surround 5.0"
  Output "Surround 4.0"
  Input "Analog Stereo"
  Input "Digital Stereo (IEC958)"

  If I pick one of the "output" I can hear the sound but the microphones
  are greyed out in the audio panel and I can't use it in any
  application. Instead if I select "Input "Analog Stereo"" I can record
  the audio but I can't hear any output!

  The volumes are turned up according also to a previous post I did
  related to similar issue I had in the past.

  The only workaround found so far is to execute: "pacmd load-module
  module-alsa-source device=hw:1,0".

  Please find attached "alsa-info" report.

  Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 
20.04):
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  snd_emu10k1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1149 F pulseaudio
   /dev/snd/controlC1:  ale1149 F pulseaudio
   /dev/snd/pcmC1D0p:   ale1149 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-08-29 (59 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  RfKill:
   
  Tags: ulyana third-party-packages
  Uname: Linux 5.4.0-52-generic x86_64
  UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069

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

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

[Touch-packages] [Bug 1882596] Autopkgtest regression report (systemd/245.4-4ubuntu3.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.3) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-hwe-5.8/5.8.0-25.26~20.04.1 (armhf)
python-dbusmock/0.19-1 (armhf)
lxc/1:4.0.2-0ubuntu1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  systemd.unit(5)  incorrectly refers to systemd.syntax(5)

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

Bug description:
  [impact]

  some systemd man pages refer to the wrong man section for some
  references

  [test case]

  e.g.

  $ man systemd.network | grep systemd.syntax
 A plain ini-style text file that encodes network configuration for 
matching network interfaces, used by systemd-networkd(8). See systemd.syntax(5) 
for a general description of the syntax.

  $ man 5 systemd.syntax
  No manual entry for systemd.syntax in section 5

  [regression potential]

  any regression would possibly cause confusion by referencing the wrong
  man section, or possibly cause a build failure, or problem with
  various man pages for systemd

  [scope]

  this is needed for f/g

  there is no systemd.syntax manpage in b or earlier

  [original description]

  In Ubuntu 20.04 LTS there is no systemd.syntax(5) it is actually
  systemd.syntax(7).

  "See systemd.syntax(5) for a general description of the syntax."

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

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

[Touch-packages] [Bug 1861941] Autopkgtest regression report (systemd/245.4-4ubuntu3.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.3) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-hwe-5.8/5.8.0-25.26~20.04.1 (armhf)
python-dbusmock/0.19-1 (armhf)
lxc/1:4.0.2-0ubuntu1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Won't Fix
Status in bcache-tools source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  SRU TEAM: The last 2 commits show a summary for the merges/changes
  I added some specific (to Bionic) notes in the template.
  Thanks!

  [Impact]

   * bcache-tools udev created symlinks might disappear when other udev
  events are processed for the same devices.

   * after mkfs.XXX in /dev/bcacheY you might face a condition where
  /dev/bcache/by-{uuid,label}/zzz symlinks are gone.

   * /dev/bcache/by-{uuid,label}/ symlinks are important so bcache
  devices can be addressed by their UUIDs and not the ordering they were
  assembled (MAAS depends on this feature, for example).

   * it was also discussed in this bug that systemd-udev should *not*
  populate /dev/disk/by-uuid/ with symlinks of disks that were bcache
  backing devices. this was turned into a discussion whether blkid
  should report those or not, and this discussion "died" after sometime.
  This last item is what the systemd update is all about: to disallow
  /dev/disk/by-XXX/ creation for bcache backing devices (a simple
  change that will reduce end users confusion).

  [Test Case]

   * The reproducer script is here:

     https://paste.ubuntu.com/p/37KGy2Smnp/

   * Bionic can't reproduce the issue with the 18.04 kernel, nor with
  the HWE kernel. Nevertheless, it is preferable that Bionic also do the
  same thing: to read bcache superblock and feed environment for
  /dev/bcache/by-{uuid,label} symlinks creation.

  [Regression Potential]

   * We are not depending on bcache device udev events any more when
  creating the /dev/bcache/by-{uuid,label}/ symlinks. Instead, we are
  depending on a wrapper script that heads bcache device superblock. If
  there is a bug in this wrapper the symlinks wouldn't work.

   * Previously we were thinking in asking the kernel team to remove the
  bcache udev event delta script they've done for previous case (LP:
  #1729145). It creates the udev events that were being read and filling
  the symlinks. We decided not to remove those (just from Groovy and on)
  so we don't need to worry on Breaks/Conflicts in between the kernel
  package and bcache-tools (and udev)).

   * Long story short: kernel will continue to emit bcache udev events
  as it did previously but now those events won't be used by anything -
  after installing this SRU - because udev wrapper script is doing this
  job (and doing it properly)

  [Other Info]

  - Original Description:

  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual
  linux-image-virtual:
    Installed: 5.4.0.12.15
    Candidate: 5.4.0.12.15
    Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic
  linux-image-5.4.0-12-generic:
    Installed: 5.4.0-12.15
    Candidate: 5.4.0-12.15
    Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5

[Touch-packages] [Bug 1892358] Autopkgtest regression report (systemd/245.4-4ubuntu3.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.3) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-hwe-5.8/5.8.0-25.26~20.04.1 (armhf)
python-dbusmock/0.19-1 (armhf)
lxc/1:4.0.2-0ubuntu1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

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

Bug description:
  [impact]

  autopkgtests are failing/flaky and prevent other packages from
  migrating to -updates

  [test case]

  check autopkgtest history

  [regression potential]

  in regard to the changed test cases, any regression would likely
  result in either an incorrectly passed test, or an incorrectly failed
  test.

  [scope]

  for systemd, this is needed for x, b, and f.

  tests in g appear to be mostly stable, but I've opened MR (linked from
  this bug) to update the tests there as well.

  i don't plan to update x, as it's reaching ESM in ~6 months, and
  backporting the test fixes is more work than just a simple code copy,
  since there are additional differences/changes needed in the older
  version of systemd (and python3). the failing/flaky tests in x have
  been like that forever, and people have just retried them; we can keep
  retrying them until x moves into ESM next year.

  [original description]

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

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

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

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

[Touch-packages] [Bug 1897744] Autopkgtest regression report (systemd/245.4-4ubuntu3.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.3) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-hwe-5.8/5.8.0-25.26~20.04.1 (armhf)
python-dbusmock/0.19-1 (armhf)
lxc/1:4.0.2-0ubuntu1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  VerifyHostKeyDNS not working due to missing trust-ad flag

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

Bug description:
  [impact]

  without trust-ad resolv.conf option, glibc will strip AD from systemd-
  resolved responses. one thing this will prevent working is ssh
  VerifyHostKeyDNS

  [test case]

  see
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1898590/comments/7

  [regression potential]

  regressions would likely involve DNS lookup failures, probably if
  DNSSEC is enabled but possibly even without, and likely when the
  application requesting the dns lookup processes the response AD.

  [scope]

  this is needed only in focal.

  glibc first stripped the AD in version 2.31, so this is not needed in
  bionic or earlier.

  this was added upstream in commit a742f9828ea which was included in
  v246, so this is fixed already in groovy.

  [original description]

  Hi,

  1)
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  2)
  systemd:245.4-4ubuntu3.2

  3)
  I set VerifyHostKeyDNS to YES and hosts are automatically verified via sshfp.

  4)
  I still get the security question
  Matching host key fingerprint found in DNS.
  Are you sure you want to continue connecting (yes/no/[fingerprint])?

  The issue is known and fixed in systemd v246.
  https://github.com/systemd/systemd/pull/16072

  Best regards
  Daniel

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

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

[Touch-packages] [Bug 1901413] Re: Sound Blaster Audigy 5/Rx cannot be configured as input/output

[Daniel van Vugt]

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

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

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

Title:
  Sound Blaster Audigy 5/Rx cannot be configured as input/output

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

Bug description:
  I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I 
cannot use it as both input and output device: it's working either as output or 
as input but not as input/output.
  I have installed "pavucontrol", when opening it in "configure" there are 
different options:

  Output "Analog Stereo"
  Output "Digital Stereo (IEC958)"
  Output "Surround 5.1"
  Output "Surround 4.1"
  Output "Surround 2.1"
  Output "Surround 7.1"
  Output "Surround 5.0"
  Output "Surround 4.0"
  Input "Analog Stereo"
  Input "Digital Stereo (IEC958)"

  If I pick one of the "output" I can hear the sound but the microphones
  are greyed out in the audio panel and I can't use it in any
  application. Instead if I select "Input "Analog Stereo"" I can record
  the audio but I can't hear any output!

  The volumes are turned up according also to a previous post I did
  related to similar issue I had in the past.

  The only workaround found so far is to execute: "pacmd load-module
  module-alsa-source device=hw:1,0".

  Please find attached "alsa-info" report.

  Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 
20.04):
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  snd_emu10k1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1149 F pulseaudio
   /dev/snd/controlC1:  ale1149 F pulseaudio
   /dev/snd/pcmC1D0p:   ale1149 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-08-29 (59 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  RfKill:
   
  Tags: ulyana third-party-packages
  Uname: Linux 5.4.0-52-generic x86_64
  UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069

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

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

[Touch-packages] [Bug 1895418] Autopkgtest regression report (systemd/245.4-4ubuntu3.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.3) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-hwe-5.8/5.8.0-25.26~20.04.1 (armhf)
python-dbusmock/0.19-1 (armhf)
lxc/1:4.0.2-0ubuntu1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  systemd-resolved default config for Caching is still "yes"

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

Bug description:
  [impact]

  /etc/systemd/resolved.conf file indicates the default value for
  'Cache=' is 'yes', but the actual default is 'no-negative'

  [test case]

  $ grep Cache /etc/systemd/resolved.conf
  #Cache=yes

  With the version of the package from -proposed it'll be "#Cache=no-
  negative".

  [regression potential]

  any regression would likely result in a mismatch between the commented
  default value of the Cache parameter and the actual build-time default
  value, or possibly a problem while systemd-resolved is parsing the
  resolved.conf file.

  [scope]

  this is needed only in focal.

  this was changed already in groovy as indicated in comment 1.

  bionic and earlier still use 'yes' as the default value of Cache=,
  which matches the resolved.conf file.

  [original description]

  Back in December, the default for systemd-resolved caching in Ubuntu
  systemd was changed to "no-negative" from the upstream default "yes"
  [0]

  In this change, the default value in the resolved.conf file was
  missed. As the defaults in this file are commented, the effective
  default is still "no-negative", however when viewing the config file,
  the commented default "yes" is at odds with the man page
  resolved.conf(5), which correctly states the default as "no-negative".

  This was an issue for me as I set DNSSEC to "yes", and expected
  Caching to also be "yes". Running DNSSEC with the default "no-
  negative" Caching is detrimental to performance resolving unsigned
  zones, as the non-existence of DNSSEC RRs must be looked up every
  time.

  The issue with the intersection of DNSSEC and Caching is for upstream,
  but the least that needs to be done here is updating the resolved.conf
  template with "Caching=no-negative" to match the man page and
  behaviour, and perhaps even adding a note to the "DNSSEC=" section of
  resolved.conf(5) that Caching should be enabled. Now that I'm looking
  at that man page, the default for DNSSEC is also listed as "allow-
  downgrade", whereas the default for Ubuntu is "no".

  [0] https://git.launchpad.net/~ubuntu-core-
  
dev/ubuntu/+source/systemd/commit/?id=b42658843a9496d6b6bb68ac159f2a9f0a8ba9db&h
  =ubuntu-focal

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

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

[Touch-packages] [Bug 1246981] Re: Bluetooth devices fail to re-connect after sleep.

[Tessa]

i just had a bug for 20.10 merged into this one. note that in my case,
this just started happening since upgrading to 20.10, and it happens
with multiple different brands of bluetooth adaptor. as well, if use my
keyboard to open the bluetooth settings panel in gnome, then everything
immediately reconnects as soon as the settings load, so it doesn't
appear to be anything to do with hardware, but instead a bug in terms of
what gnome services do when the system resumes.

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

Title:
  Bluetooth devices fail to re-connect after sleep.

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This exact harware was working faultlessly in 13.04. Since re-
  installing at 13.10 the mouse consistently failes to reconnect after
  the device either hybernates or ever goes to screen saver sleep.

  I have to remove the dive and re-add it each time (which works well).

  There are other issues with the bluetooth stack as well in that I have
  not found any way to use bluetooth tethering to my mobile which again
  worked well and was easy to configure in 13.04

  Peter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov  1 16:44:37 2013
  InstallationDate: Installed on 2013-10-19 (13 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Dell Inc. Latitude E6530
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 20:16:D8:9C:38:E5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0
TX bytes:37955 acl:131 sco:0 commands:5096 errors:0
  syslog:
   Nov  1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 
0x7f6489f7b450 with :1.582 activated
   Nov  1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command 
complete for opcode 37
   Nov  1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft 
Bluetooth Notebook Mouse 5000 as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 
0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft 
Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5

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

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

[Touch-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

[Kreaninw]

I'm using Acer Swift SF514-52T (Intel 8th Gen Core i5) on Ubuntu 20.10 -
Linux kernel 5.8.

The default configuration has no sound working at all. I believe it uses
the SOF driver (I could be wrong) which doesn't support the Kaby Lake
platform, as the issues for supporting this platform have been closed (
https://github.com/thesofproject/sof/issues/1899 ). And the proposed
workaround to support this platform have been discarded also (
https://github.com/thesofproject/sof/issues/2256 ). Therefore installing
the latest version or any version of the SOF driver will not solve the
issue.

Force enable the HDA driver (snd_hda_intel) in /etc/modprobe.d/alsa-
base.conf with options snd-intel-dspcfg dsp_driver=1, the sound output
works fine but the internal mic (DMIC) doesn't work. And I believe we're
moving to the SOF driver which doesn't support my device. Therefore I
don't expect any fix will be done in HDA driver.

I tried to use Intel's SST driver as it's the only solution left. I
enabled it with options snd-intel-dspcfg dsp_driver=2 but both the sound
output and the internal mic (DMIC) don't work.

I also report this bug in
https://bugzilla.kernel.org/show_bug.cgi?id=201251

Here is my alsa-info (with options snd-intel-dspcfg dsp_driver=2): http
://alsa-project.org/db/?f=db024ae3c924d318bda813f73c73e76df36bbca2

I attached my full dmesg also.

** Bug watch added: github.com/thesofproject/sof/issues #1899
   https://github.com/thesofproject/sof/issues/1899

** Bug watch added: github.com/thesofproject/sof/issues #2256
   https://github.com/thesofproject/sof/issues/2256

** Bug watch added: Linux Kernel Bug Tracker #201251
   https://bugzilla.kernel.org/show_bug.cgi?id=201251

** Attachment added: "dmesg on Acer Swift SF514-52T running Ubuntu 20.10"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+attachment/5428164/+files/dmesg_messages

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

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

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

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
 

[Touch-packages] [Bug 1895418] Re: systemd-resolved default config for Caching is still "yes"

[Cameron Steel]

Testing systemd 245.4-4ubuntu3.3 on Focal, I can verify that the default
value of the "Cache" directive is "no-negative" in the man page, default
config file, and actual program behaviour.

While doing this, I was reminded that the default value of the "DNSSEC"
directive is "no" in both the default config file and program behaviour,
however the man page lists the default as "allow-downgrade". As a user
looking to change this setting would do so by editing the config file
anyway, I don't personally think this is of great importance to fix.

** 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1895418

Title:
  systemd-resolved default config for Caching is still "yes"

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

Bug description:
  [impact]

  /etc/systemd/resolved.conf file indicates the default value for
  'Cache=' is 'yes', but the actual default is 'no-negative'

  [test case]

  $ grep Cache /etc/systemd/resolved.conf
  #Cache=yes

  With the version of the package from -proposed it'll be "#Cache=no-
  negative".

  [regression potential]

  any regression would likely result in a mismatch between the commented
  default value of the Cache parameter and the actual build-time default
  value, or possibly a problem while systemd-resolved is parsing the
  resolved.conf file.

  [scope]

  this is needed only in focal.

  this was changed already in groovy as indicated in comment 1.

  bionic and earlier still use 'yes' as the default value of Cache=,
  which matches the resolved.conf file.

  [original description]

  Back in December, the default for systemd-resolved caching in Ubuntu
  systemd was changed to "no-negative" from the upstream default "yes"
  [0]

  In this change, the default value in the resolved.conf file was
  missed. As the defaults in this file are commented, the effective
  default is still "no-negative", however when viewing the config file,
  the commented default "yes" is at odds with the man page
  resolved.conf(5), which correctly states the default as "no-negative".

  This was an issue for me as I set DNSSEC to "yes", and expected
  Caching to also be "yes". Running DNSSEC with the default "no-
  negative" Caching is detrimental to performance resolving unsigned
  zones, as the non-existence of DNSSEC RRs must be looked up every
  time.

  The issue with the intersection of DNSSEC and Caching is for upstream,
  but the least that needs to be done here is updating the resolved.conf
  template with "Caching=no-negative" to match the man page and
  behaviour, and perhaps even adding a note to the "DNSSEC=" section of
  resolved.conf(5) that Caching should be enabled. Now that I'm looking
  at that man page, the default for DNSSEC is also listed as "allow-
  downgrade", whereas the default for Ubuntu is "no".

  [0] https://git.launchpad.net/~ubuntu-core-
  
dev/ubuntu/+source/systemd/commit/?id=b42658843a9496d6b6bb68ac159f2a9f0a8ba9db&h
  =ubuntu-focal

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

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

[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Marco Giovinazzi]

Same problem using Aeropex by AfterShokz (AVRCP) headset on 20.04
(xps9310).

Quick-and-dirty workaround:
- download the 1.190 firmware package 
(http://mirrors.edge.kernel.org/ubuntu/pool/main/l/linux-firmware/linux-firmware_1.190.tar.gz)
- copy the relevant ibt firmware and parameters (sfi, ddc) to 
/usr/lib/firmware/intel (ibt-19-0-4 in my case) - backup of the old files 
highly recommended ;)
- reboot, reconnect.

My headset is now working both in A2DP and HFP/HSP modes.

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-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-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1899745] Re: [SRU] alsa-utils: let alsactl support _boot section defined in ucm

[Brian Murray]

Hello Hui, or anyone else affected,

Accepted alsa-utils into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/alsa-
utils/1.2.2-1ubuntu2 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.

** 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 alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1899745

Title:
  [SRU] alsa-utils: let alsactl support _boot section defined in ucm

Status in HWE Next:
  New
Status in alsa-utils package in Ubuntu:
  Fix Released
Status in alsa-utils source package in Focal:
  Fix Committed

Bug description:
  This patchset was backported from mainline alsa-utils 1.2.3, and
  groovy already integrated alsa-utils 1.2.3, there is no need to SRU
  this patchset to groovy, so only for focal.

  [Impact]
  We enabled 2 Dell soundwire audio machines, these machines depend on
  ucm to make the audio work, and in the ucm, the _boot section defined
  some amixers values for the 1st booting, these amixer values should
  be set to audio driver at the 1st booting, otherwise the whole audio
  doesn't work.

  [Fix]
  Backport some patches from mainline v1.2.3, these patches make the
  alsactl support _boot section in the ucm, then the systemd will call
  alsactl init after booting, the alsactl init will setting all amixers
  defined in the _boot section of ucm.

  [Test Case]
  On the Dell soundwire audio machines, After booting up, run 'amixer
  contents | less' to check all amixer values defined in the _boot
  section of ucm, all values read from driver are same as the ones in
  the ucm, test speaker/microphone/headset, all work well.

  [Regression Risk]
  This could introduce failure on runing 'alsactl init' for some machines,
  then the amixers will not be initialized correctly, users will experience
  all audio can't work like speaker doesn't output sound or microphone can't
  record sound. But this regression possibility is very low, since We have
  tested it both on soundwire machines and non-soundwire machines, all worked 
well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1899745/+subscriptions

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

[Touch-packages] [Bug 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)

[Brian Murray]

Hello fossfreedom, or anyone else affected,

Accepted alsa-lib into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/alsa-
lib/1.2.2-2.1ubuntu2.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.

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

Title:
  [SRU][Intel HDA] The initial sound level is set to zero (muted)

Status in Release Notes for Ubuntu:
  Invalid
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Fail to run '/usr/sbin/alsactl restore' on the HDA-Intel machines, this
  results in the failure on setting the init mixer values for HDA sound
  card, and users experience the mute of audio after installing the 20.10.  

  [Fix]
  Backport a patch from the latest alsa-lib (v1.2.3+)

  [Test]
  Without the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*;
  sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is
  muted.

  Install the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*;
  sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is
  not muted.

  [Regression Potential]
  This could make the ucm audio fail to initialize, but this possibility is
  very low, since this patch is from upstream, and I tested on a ucm based
  machine, the audio is good.

  
  On boot into the live session - or on first install the sound level is muted.

  I have to use GNOME Control Center - Sounds to change to an
  appropriate level.  Once changed the level chosen is correctly
  retained between reboots.

  This appears to be a regression from 20.04 where the sound level was
  set to - I guess - 80% on the live-session/first install

  ProblemType: BugDistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu11
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-budgie   5041 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: Budgie:GNOME
  Date: Wed Sep 30 16:03:08 2020
  LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2016
  dmi.bios.release: 15.31
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.22
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+subscriptions

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

[Touch-packages] [Bug 1892643] Update Released

[Brian Murray]

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

Title:
  [SRU] Update libgweather to 3.36.1

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

Bug description:
  [Impact]

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

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

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

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

  
  [Test case]

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

  
  [Regression potential]

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

  
  [Other]

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

  
https://launchpad.net/~amribrahim1987/+archive/ubuntu/ppa/+packages?field.name_filter=libgweather&field.status_filter=published&field.series_filter=

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

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

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

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

[Launchpad Bug Tracker]

This bug was fixed in the package libgweather - 3.36.1-1~ubuntu20.04.1

---
libgweather (3.36.1-1~ubuntu20.04.1) focal; urgency=medium

  * No-change backport to focal (LP: #1892643)

libgweather (3.36.1-1) unstable; urgency=medium

  * Team upload
  * New upstream release
- This version works around the unavailability of the NOAA weather
  services by using very short-term forecasts as current weather
  conditions. (Closes: #968909)

 -- Amr Ibrahim   Fri, 11 Sep 2020 18:32:10
+0200

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

Title:
  [SRU] Update libgweather to 3.36.1

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

Bug description:
  [Impact]

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

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

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

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

  
  [Test case]

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

  
  [Regression potential]

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

  
  [Other]

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

  
https://launchpad.net/~amribrahim1987/+archive/ubuntu/ppa/+packages?field.name_filter=libgweather&field.status_filter=published&field.series_filter=

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

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

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

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

[Lyubomir]

As this bug is set to incomplete, is there any other information that i
need to provide?

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

Title:
  System slow on booting

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

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

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

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

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

[Touch-packages] [Bug 1849406] Re: Ubuntu 19.10: "Cdrom" to "Physical media"

[Julian Andres Klode]

Renamed to installation medium in https://salsa.debian.org/apt-team
/python-apt/-/commit/a228b5800d7850d1c7bfa9224cad87f6edbdd44f to match
live disc messaging.

** Changed in: python-apt (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Ubuntu 19.10: "Cdrom" to "Physical media"

Status in python-apt package in Ubuntu:
  Fix Committed

Bug description:
  Do this: open the app Software & Updates > select first tab named
  Ubuntu Software (if not already by default) > observe section
  Installable from CD-ROM/DVD

  In those good ol' days, Ubuntu was installable only from a CD and
  later from a DVD. Nowadays, USB thumb drives are superceding this,
  which makes the whole string wrong, even the title.

  So, I propose this:
  Installable from physical media
  Physical media with Ubuntu [...]

  This makes it future-proof as well, since god-knows-what is going to
  exist in the future to boot Ubuntu from, but it will be physical media
  for sure.

  Care to fix this? Also, I would gladly make a PR request to speed up
  the process (provided you tell me how).

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

-- 
Mailing list: https://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 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory

[Steve Langasek]

On Tue, Oct 27, 2020 at 03:49:30AM -, Zach H wrote:
> Hi, just to confirm that this may be a bigger issue than first
> anticipated - on Ubuntu Server 20.04 this is causing issues with logins
> via sftp/ftp.

Why do you believe your issue is caused by this bug?  The only known effect
of this bug is the extraneous log entries; it is not known to cause pam
modules to return different results.

You can test this by temporarily editing /etc/pam.d/common-auth to list
'nullok' instead of 'nullok_secure'.  If your problem persists, then it is
unrelated to this bug.

-- 
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 1727470] Re: [RFE] Automatically update the Ubuntu version strings in python-apt

[Julian Andres Klode]

Released upstream as python-apt 2.1.15

** Changed in: python-apt (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  [RFE] Automatically update the Ubuntu version strings in python-apt

Status in Ubuntu Translations:
  Triaged
Status in python-apt package in Ubuntu:
  Fix Committed

Bug description:
  Every time there is a new Ubuntu release, some strings need to be
  manually translated although the only thing that is changing is the
  Ubuntu version and code name. Please, consider updating these strings
  automatically based on a translated template. It would help many
  translators.

  These strings are:
  Ubuntu xx.yy 'Code Name'
  Cdrom with Ubuntu xx.yy 'Code Name'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1727470/+subscriptions

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

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

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Most of the time Ubuntu boots the  dock seems to freeze and not load
  any icons, sometimes for up to a minute. When this happens the dock
  will not appear when any window is maximized.

  Once in a while Ubuntu loads without a problem. The dock loads
  instantly and has no problem behind a maximized window.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 27 12:35:14 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Iris Plus Graphics 640 [8086:5926] (rev 06) (prog-if 00 
[VGA controller])
 Subsystem: Intel Corporation Iris Plus Graphics 640 [8086:2068]
  InstallationDate: Installed on 2020-09-16 (41 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Intel(R) Client Systems NUC7i5BNK
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=50f7562f-c44b-4a47-b1b4-02bdd6281c08 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0080.2019.0725.1139
  dmi.board.name: NUC7i5BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31144-314
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0080.2019.0725.1139:bd07/25/2019:svnIntel(R)ClientSystems:pnNUC7i5BNK:pvrJ31159-315:rvnIntelCorporation:rnNUC7i5BNB:rvrJ31144-314:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: BN
  dmi.product.name: NUC7i5BNK
  dmi.product.version: J31159-315
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

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

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Most of the time Ubuntu boots the  dock seems to freeze and not load any
icons, sometimes for up to a minute. When this happens the dock will not
appear when any window is maximized.

Once in a while Ubuntu loads without a problem. The dock loads instantly
and has no problem behind a maximized window.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 27 12:35:14 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Iris Plus Graphics 640 [8086:5926] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation Iris Plus Graphics 640 [8086:2068]
InstallationDate: Installed on 2020-09-16 (41 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Intel(R) Client Systems NUC7i5BNK
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=50f7562f-c44b-4a47-b1b4-02bdd6281c08 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2019
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BNKBL357.86A.0080.2019.0725.1139
dmi.board.name: NUC7i5BNB
dmi.board.vendor: Intel Corporation
dmi.board.version: J31144-314
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0080.2019.0725.1139:bd07/25/2019:svnIntel(R)ClientSystems:pnNUC7i5BNK:pvrJ31159-315:rvnIntelCorporation:rnNUC7i5BNB:rvrJ31144-314:cvnIntelCorporation:ct35:cvr2.0:
dmi.product.family: BN
dmi.product.name: NUC7i5BNK
dmi.product.version: J31159-315
dmi.sys.vendor: Intel(R) Client Systems
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 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 false-gpu-hang focal freeze ubuntu wayland-session
-- 
Xorg freeze
https://bugs.launchpad.net/bugs/1901736
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1901752] [NEW] Can’t connect to a specific Wi-Fi network with wpa_supplicant

[Arseny]

Public bug reported:

This is the error I get if I try to connect to a specific Wi-Fi network
on Ubuntu 20.10 with wpa_supplicant:

Error: Connection activation failed: (7) Secrets were required, but not
provided.

If I use iwd instead, everything works fine.

I also can connect to other networks with wpa_supplicant.

I had the same issue with the Live USB.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: wpasupplicant 2:2.9-1ubuntu8
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: i3
Date: Tue Oct 27 20:55:39 2020
InstallationDate: Installed on 2020-10-26 (1 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy

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

Title:
  Can’t connect to a specific Wi-Fi network with wpa_supplicant

Status in wpa package in Ubuntu:
  New

Bug description:
  This is the error I get if I try to connect to a specific Wi-Fi
  network on Ubuntu 20.10 with wpa_supplicant:

  Error: Connection activation failed: (7) Secrets were required, but
  not provided.

  If I use iwd instead, everything works fine.

  I also can connect to other networks with wpa_supplicant.

  I had the same issue with the Live USB.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: wpasupplicant 2:2.9-1ubuntu8
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: i3
  Date: Tue Oct 27 20:55:39 2020
  InstallationDate: Installed on 2020-10-26 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1824260] Re: wrong kerning in SS-5 PDF form fields

[Gunnar Hjalmarsson]

Ok, I changed the Ubuntu patch in accordance with your suggestion. Maybe
a bit better...

As regards your upstream issue, you probably increase the chances that
it gets attention if you submit a merge request.

** Patch removed: "fontconfig_lp1824260.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1824260/+attachment/5427587/+files/fontconfig_lp1824260.debdiff

** Patch added: "fontconfig_lp1824260.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1824260/+attachment/5428033/+files/fontconfig_lp1824260.debdiff

** Also affects: fontconfig via
   https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/262
   Importance: Unknown
   Status: Unknown

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

Title:
  wrong kerning in SS-5 PDF form fields

Status in Fontconfig:
  Unknown
Status in Poppler:
  New
Status in fontconfig package in Ubuntu:
  In Progress

Bug description:
  What I expected to happen:

  I am filling out the SS-5 Social Security Administration form (see
  attached). I entered "John Jacob Smith" into the "First", "Full Middle
  Name", and "Last" fields on page 5.

  What happened instead:

  I can enter the text without issue, but some of the letters are
  wrongly positioned, i.e. the kerning is wrong. For example, the letter
  "i" overlaps with the letter "m" in "Smith" (see attached image). It
  looks like the font in the fields might be displaying a variable width
  font when it is supposed to be a fixed-wdith font.

  Discussion:

  Since this bug is also present in xpdf and Okular (but not mupdf), I'm
  guessing this isn't a bug in Evince itself. However, I am reporting it
  here as a courtesy to other users (since Evince is the default PDF
  reader) and because I'm not sure which dependency is responsible. (I'm
  also not sure if it's a direct dependency problem or if it's something
  else like a font configuration issue.)

  Here is the output for pdffonts ss-5.pdf:

  name type  encoding emb 
sub uni object ID
   -  --- 
--- --- -
  IHPIKC+ArialMT   CID TrueType  Identity-H   yes 
yes yes824  0
  ArialMT  TrueType  WinAnsi  no  
no  no 826  0
  Arial-BoldMT TrueType  WinAnsi  no  
no  no 828  0
  CourierStd   Type 1WinAnsi  no  
no  no 145  0
  HelveticaType 1WinAnsi  no  
no  no 197  0
  MyriadPro-RegularType 1WinAnsi  no  
no  no 198  0
  ZapfDingbats Type 1ZapfDingbats no  
no  no 199  0

  I asked about this in an Ask Ubuntu question nearly a year ago, but
  received no response, so I am reporting a bug now instead:

  https://askubuntu.com/questions/1031235/wrong-letter-positioning-and-
  font-in-pdf-form

  Ubuntu version:

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  evince version:

  $ apt-cache policy evince
  evince:
    Installed: 3.28.4-0ubuntu1
    Candidate: 3.28.4-0ubuntu1
    Version table:
   *** 3.28.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 10 21:27:11 2019
  InstallationDate: Installed on 2018-12-12 (119 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1901173] Re: Updating focal to groovy fails

[Mario Camou]

** Package changed: python-defaults (Ubuntu) => update-manager-core
(Ubuntu)

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

Title:
  Updating focal to groovy fails

Status in update-manager-core package in Ubuntu:
  New

Bug description:
  Running `do-release-upgrade` from focal to groovy, I got the following
  crash after the packages were downloaded:

  ```
  apt_pkg.Error: E:Could not configure 'libc6:amd64'. , E:Could not perform 
immediate configuration on 'libnss-nis:amd64'. Please see man 5 apt.conf under 
APT::Immediate-Configure for details. (2)
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/problem_report.py", line 477, in 
add_to_existing
  self.write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 430, in write
  block = f.read(1048576)
File "/usr/lib/python3.8/codecs.py", line 322, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: 
invalid start byte

  Original exception was:
  apt_pkg.Error: E:Could not configure 'libc6:amd64'. , E:Could not perform 
immediate configuration on 'libnss-nis:amd64'. Please see man 5 apt.conf under 
APT::Immediate-Configure for details. (2)
  Error in function: install

  apt_pkg.Error: E:Could not perform immediate configuration on 
'libffi8ubuntu1:amd64'. Please see man 5 apt.conf under 
APT::Immediate-Configure for details. (2)
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/problem_report.py", line 477, in 
add_to_existing
  self.write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 430, in write
  block = f.read(1048576)
File "/usr/lib/python3.8/codecs.py", line 322, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: 
invalid start byte

  Original exception was:
  apt_pkg.Error: E:Could not perform immediate configuration on 
'libffi8ubuntu1:amd64'. Please see man 5 apt.conf under 
APT::Immediate-Configure for details. (2)

  Could not install the upgrades

  The upgrade has aborted. Your system could be in an unusable state. A 
  recovery will run now (dpkg --configure -a). 

  
  Upgrade infeasible 

  The upgrade could not be completed, there were errors during the 
  upgrade process. 
  ```

  I tried adding an /etc/apt/99temp-release-upgrade file with the
  following contents:

  ```
  APT::Immediate-Configure "false"
  ```

  which resulted in:

  ```
  # do-release-upgrade 
  Traceback (most recent call last):
File "/usr/bin/do-release-upgrade", line 11, in 
  from UpdateManager.Core.MetaRelease import MetaReleaseCore
File "/usr/lib/python3/dist-packages/UpdateManager/Core/MetaRelease.py", 
line 25, in 
  import apt
File "/usr/lib/python3/dist-packages/apt/__init__.py", line 35, in 
  apt_pkg.init_config()
  apt_pkg.Error: E:Syntax error 
/etc/apt/apt.conf.d/99temp-for-release-upgrade:3: Extra junk at end of file
  ```

  This was detected by someone during the beta, but it seems that no one
  took the time to fix it: https://bugs.launchpad.net/ubuntu/+source
  /ubuntu-release-upgrader/+bug/1899272

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

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

[Touch-packages] [Bug 1727470] Re: [RFE] Automatically update the Ubuntu version strings in python-apt

[Julian Andres Klode]

https://salsa.debian.org/apt-team/python-apt/-/merge_requests/52

** Changed in: python-apt (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  [RFE] Automatically update the Ubuntu version strings in python-apt

Status in Ubuntu Translations:
  Triaged
Status in python-apt package in Ubuntu:
  In Progress

Bug description:
  Every time there is a new Ubuntu release, some strings need to be
  manually translated although the only thing that is changing is the
  Ubuntu version and code name. Please, consider updating these strings
  automatically based on a translated template. It would help many
  translators.

  These strings are:
  Ubuntu xx.yy 'Code Name'
  Cdrom with Ubuntu xx.yy 'Code Name'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1727470/+subscriptions

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

[Touch-packages] [Bug 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]

[Brian Murray]

Actually, please make sure that you the following package installed.

(focal-amd64)root@impulse:~/bind9-libs-9.11.16+dfsg# apt-cache policy 
libisc-export1105
libisc-export1105:
  Installed: 1:9.11.16+dfsg-3~ubuntu1
  Candidate: 1:9.11.16+dfsg-3~ubuntu1
  Version table:
 *** 1:9.11.16+dfsg-3~ubuntu1 500
500 http://192.168.10.7/ubuntu focal-updates/main amd64 Packages
100 /var/lib/dpkg/status

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

Title:
  isc-dhcp-server crashing constantly [Ubuntu 20.04]

Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in isc-dhcp source package in Focal:
  Confirmed

Bug description:
  isc-dhcp-server crashing constantly (sometimes within seconds or minutes, 
sometimes within hours) with the following error messages:
  Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service.
  Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ??
  Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ??
  Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ??
  Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ??
  Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ??
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872106/+subscriptions

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

[Touch-packages] [Bug 1901742] Re: systemd-modules-load.service fails to start because it can't understand module arguments in /etc/modules, which it shouldn't even be reading

[Adam Novak]

This is an interaction between a symlink that systemd ships (as
mentioned in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=627949#10) and the kmod package (which ships the
now-inaccurate /usr/share/man/man5/modules.5.gz).

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

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

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

Title:
  systemd-modules-load.service fails to start because it can't
  understand module arguments in /etc/modules, which it shouldn't even
  be reading

Status in kmod package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  My systemd-modules-load.service fails to start like this:

  ● systemd-modules-load.service - Load Kernel Modules
 Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; 
vendor preset: enabled)
 Active: failed (Result: exit-code) since Tue 2020-10-27 10:24:52 PDT; 4s 
ago
   Docs: man:systemd-modules-load.service(8)
 man:modules-load.d(5)
Process: 23683 ExecStart=/lib/systemd/systemd-modules-load (code=exited, 
status=1/FAILURE)
   Main PID: 23683 (code=exited, status=1/FAILURE)

  Oct 27 10:24:52 octagon systemd[1]: Starting Load Kernel Modules...
  Oct 27 10:24:52 octagon systemd-modules-load[23683]: Failed to find module 
'vfio vfio_iommu_type1 vfio_pci vfio_virqfd'
  Oct 27 10:24:52 octagon systemd[1]: systemd-modules-load.service: Main 
process exited, code=exited, status=1/FAILURE
  Oct 27 10:24:52 octagon systemd[1]: systemd-modules-load.service: Failed with 
result 'exit-code'.
  Oct 27 10:24:52 octagon systemd[1]: Failed to start Load Kernel Modules.

  It looks like it's trying to interpret a whole module-and-arguments
  string as just a module name, and failing to load this.

  By recursive grep of /etc, the only place it can be getting that
  string is /etc/modules:

  $ sudo ag vfio_iommu_type1
  [sudo] password for anovak: 
  modules
  5:vfio vfio_iommu_type1 vfio_pci vfio_virqfd

  The manpage for /etc/modules clearly says that the file may contain
  module names *and* arguments:

  [anovak@octagon ~]$ man modules | grep Arguments
 The /etc/modules file contains the names of kernel modules that are to 
be loaded at boot time, one per line. Arguments can be given in the same line 
as the module name. Lines beginning with a

  The manpage for systemd-modules-load.service doesn't mention
  /etc/modules, and says to see the manpage for modules-load.d(5). That
  manpage says that it only reads files from specific directories:

  SYNOPSIS
 /etc/modules-load.d/*.conf

 /run/modules-load.d/*.conf

 /usr/lib/modules-load.d/*.conf

  The manpage is clearly lying, and systemd-modules-load.service is
  clearly also reading /etc/modules. Moreover, it's misreading it, and
  not interpreting it according to the documented semantics of
  /etc/modules.

  I was induced to create an /etc/modules like this by
  https://mathiashueber.com/windows-virtual-machine-gpu-passthrough-
  ubuntu/ but I'm not sure that it's actually getting used by anything,
  because lsmod shows some but not all of the options I specified.

  [anovak@octagon etc]$ lsmod | grep "^vfio "
  vfio   28672  2 vfio_iommu_type1,vfio_pci

  Can systemd be made to stop reading /etc/modules so that it doesn't
  report failure when it doesn't understand lines with options? And is
  that file being read by something else in the system, or should I just
  remove it as a workaround to stop upsetting systemd?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.42
  ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18
  Uname: Linux 4.15.0-122-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 27 10:33:50 2020
  InstallationDate: Installed on 2017-08-06 (1177 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-122-generic 
root=UUID=5219a3ae-e14c-4f63-8f62-17cebc1af57a ro modprobe.blacklist=amdgpu 
usb_storage.quirks=0bc2:ab38: amd_iommu=on vfio-pci.ids=1002:67df
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2018-05-29 (882 days ago)
  dmi.bios.date: 12/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4207
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X370-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.

[Touch-packages] [Bug 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]

[Brian Murray]

This looks like a duplicate of bug 1872118 which is purportedly fixed
with a change to bind9-libs. However, I don't see the relationship
between bind9-libs and isc-dhcp. Regardless, it might be worth trying to
install bind9-libs and see if that resolves the issue.

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

Title:
  isc-dhcp-server crashing constantly [Ubuntu 20.04]

Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in isc-dhcp source package in Focal:
  Confirmed

Bug description:
  isc-dhcp-server crashing constantly (sometimes within seconds or minutes, 
sometimes within hours) with the following error messages:
  Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service.
  Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ??
  Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ??
  Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ??
  Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ??
  Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ??
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872106/+subscriptions

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

[Touch-packages] [Bug 1901742] [NEW] systemd-modules-load.service fails to start because it can't understand module arguments in /etc/modules, which it shouldn't even be reading

[Adam Novak]

Public bug reported:

My systemd-modules-load.service fails to start like this:

● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-10-27 10:24:52 PDT; 4s ago
 Docs: man:systemd-modules-load.service(8)
   man:modules-load.d(5)
  Process: 23683 ExecStart=/lib/systemd/systemd-modules-load (code=exited, 
status=1/FAILURE)
 Main PID: 23683 (code=exited, status=1/FAILURE)

Oct 27 10:24:52 octagon systemd[1]: Starting Load Kernel Modules...
Oct 27 10:24:52 octagon systemd-modules-load[23683]: Failed to find module 
'vfio vfio_iommu_type1 vfio_pci vfio_virqfd'
Oct 27 10:24:52 octagon systemd[1]: systemd-modules-load.service: Main process 
exited, code=exited, status=1/FAILURE
Oct 27 10:24:52 octagon systemd[1]: systemd-modules-load.service: Failed with 
result 'exit-code'.
Oct 27 10:24:52 octagon systemd[1]: Failed to start Load Kernel Modules.

It looks like it's trying to interpret a whole module-and-arguments
string as just a module name, and failing to load this.

By recursive grep of /etc, the only place it can be getting that string
is /etc/modules:

$ sudo ag vfio_iommu_type1
[sudo] password for anovak: 
modules
5:vfio vfio_iommu_type1 vfio_pci vfio_virqfd

The manpage for /etc/modules clearly says that the file may contain
module names *and* arguments:

[anovak@octagon ~]$ man modules | grep Arguments
   The /etc/modules file contains the names of kernel modules that are to 
be loaded at boot time, one per line. Arguments can be given in the same line 
as the module name. Lines beginning with a

The manpage for systemd-modules-load.service doesn't mention
/etc/modules, and says to see the manpage for modules-load.d(5). That
manpage says that it only reads files from specific directories:

SYNOPSIS
   /etc/modules-load.d/*.conf

   /run/modules-load.d/*.conf

   /usr/lib/modules-load.d/*.conf

The manpage is clearly lying, and systemd-modules-load.service is
clearly also reading /etc/modules. Moreover, it's misreading it, and not
interpreting it according to the documented semantics of /etc/modules.

I was induced to create an /etc/modules like this by
https://mathiashueber.com/windows-virtual-machine-gpu-passthrough-
ubuntu/ but I'm not sure that it's actually getting used by anything,
because lsmod shows some but not all of the options I specified.

[anovak@octagon etc]$ lsmod | grep "^vfio "
vfio   28672  2 vfio_iommu_type1,vfio_pci

Can systemd be made to stop reading /etc/modules so that it doesn't
report failure when it doesn't understand lines with options? And is
that file being read by something else in the system, or should I just
remove it as a workaround to stop upsetting systemd?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.42
ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18
Uname: Linux 4.15.0-122-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 27 10:33:50 2020
InstallationDate: Installed on 2017-08-06 (1177 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-122-generic 
root=UUID=5219a3ae-e14c-4f63-8f62-17cebc1af57a ro modprobe.blacklist=amdgpu 
usb_storage.quirks=0bc2:ab38: amd_iommu=on vfio-pci.ids=1002:67df
SourcePackage: systemd
UpgradeStatus: Upgraded to bionic on 2018-05-29 (882 days ago)
dmi.bios.date: 12/08/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4207
dmi.board.asset.tag: Default string
dmi.board.name: PRIME X370-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4207:bd12/08/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
mtime.conffile..etc.systemd.journald.conf: 2018-05-28T15:25:25.223494
mtime.conffile..etc.systemd.resolved.conf: 2017-09-24T15:57:22.768472

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


** Tags: amd64 apport-bug bionic

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

Title:
  systemd-modules-load.service fails to start because 

[Touch-packages] [Bug 1901413] Re: Sound Blaster Audigy 5/Rx cannot be configured as input/output

[Alessio]

@Daniel van Vugt: thanks for checking my bug request. I apologise for
the missing information: I've just executed the apport-collect and I
wish all the necessary information to be attached.

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

Title:
  Sound Blaster Audigy 5/Rx cannot be configured as input/output

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I 
cannot use it as both input and output device: it's working either as output or 
as input but not as input/output.
  I have installed "pavucontrol", when opening it in "configure" there are 
different options:

  Output "Analog Stereo"
  Output "Digital Stereo (IEC958)"
  Output "Surround 5.1"
  Output "Surround 4.1"
  Output "Surround 2.1"
  Output "Surround 7.1"
  Output "Surround 5.0"
  Output "Surround 4.0"
  Input "Analog Stereo"
  Input "Digital Stereo (IEC958)"

  If I pick one of the "output" I can hear the sound but the microphones
  are greyed out in the audio panel and I can't use it in any
  application. Instead if I select "Input "Analog Stereo"" I can record
  the audio but I can't hear any output!

  The volumes are turned up according also to a previous post I did
  related to similar issue I had in the past.

  The only workaround found so far is to execute: "pacmd load-module
  module-alsa-source device=hw:1,0".

  Please find attached "alsa-info" report.

  Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 
20.04):
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  snd_emu10k1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1149 F pulseaudio
   /dev/snd/controlC1:  ale1149 F pulseaudio
   /dev/snd/pcmC1D0p:   ale1149 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-08-29 (59 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  RfKill:
   
  Tags: ulyana third-party-packages
  Uname: Linux 5.4.0-52-generic x86_64
  UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069

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

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

[Touch-packages] [Bug 1901413] Lspci-vt.txt

[Alessio]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1901413/+attachment/5427971/+files/Lspci-vt.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/1901413

Title:
  Sound Blaster Audigy 5/Rx cannot be configured as input/output

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I 
cannot use it as both input and output device: it's working either as output or 
as input but not as input/output.
  I have installed "pavucontrol", when opening it in "configure" there are 
different options:

  Output "Analog Stereo"
  Output "Digital Stereo (IEC958)"
  Output "Surround 5.1"
  Output "Surround 4.1"
  Output "Surround 2.1"
  Output "Surround 7.1"
  Output "Surround 5.0"
  Output "Surround 4.0"
  Input "Analog Stereo"
  Input "Digital Stereo (IEC958)"

  If I pick one of the "output" I can hear the sound but the microphones
  are greyed out in the audio panel and I can't use it in any
  application. Instead if I select "Input "Analog Stereo"" I can record
  the audio but I can't hear any output!

  The volumes are turned up according also to a previous post I did
  related to similar issue I had in the past.

  The only workaround found so far is to execute: "pacmd load-module
  module-alsa-source device=hw:1,0".

  Please find attached "alsa-info" report.

  Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 
20.04):
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  snd_emu10k1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1149 F pulseaudio
   /dev/snd/controlC1:  ale1149 F pulseaudio
   /dev/snd/pcmC1D0p:   ale1149 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-08-29 (59 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  RfKill:
   
  Tags: ulyana third-party-packages
  Uname: Linux 5.4.0-52-generic x86_64
  UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069

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

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

[Touch-packages] [Bug 1901413] PulseList.txt

[Alessio]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1901413/+attachment/5427979/+files/PulseList.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/1901413

Title:
  Sound Blaster Audigy 5/Rx cannot be configured as input/output

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I 
cannot use it as both input and output device: it's working either as output or 
as input but not as input/output.
  I have installed "pavucontrol", when opening it in "configure" there are 
different options:

  Output "Analog Stereo"
  Output "Digital Stereo (IEC958)"
  Output "Surround 5.1"
  Output "Surround 4.1"
  Output "Surround 2.1"
  Output "Surround 7.1"
  Output "Surround 5.0"
  Output "Surround 4.0"
  Input "Analog Stereo"
  Input "Digital Stereo (IEC958)"

  If I pick one of the "output" I can hear the sound but the microphones
  are greyed out in the audio panel and I can't use it in any
  application. Instead if I select "Input "Analog Stereo"" I can record
  the audio but I can't hear any output!

  The volumes are turned up according also to a previous post I did
  related to similar issue I had in the past.

  The only workaround found so far is to execute: "pacmd load-module
  module-alsa-source device=hw:1,0".

  Please find attached "alsa-info" report.

  Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 
20.04):
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  snd_emu10k1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1149 F pulseaudio
   /dev/snd/controlC1:  ale1149 F pulseaudio
   /dev/snd/pcmC1D0p:   ale1149 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-08-29 (59 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  RfKill:
   
  Tags: ulyana third-party-packages
  Uname: Linux 5.4.0-52-generic x86_64
  UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069

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

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

[Touch-packages] [Bug 1901413] UdevDb.txt

[Alessio]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1901413/+attachment/5427980/+files/UdevDb.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/1901413

Title:
  Sound Blaster Audigy 5/Rx cannot be configured as input/output

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I 
cannot use it as both input and output device: it's working either as output or 
as input but not as input/output.
  I have installed "pavucontrol", when opening it in "configure" there are 
different options:

  Output "Analog Stereo"
  Output "Digital Stereo (IEC958)"
  Output "Surround 5.1"
  Output "Surround 4.1"
  Output "Surround 2.1"
  Output "Surround 7.1"
  Output "Surround 5.0"
  Output "Surround 4.0"
  Input "Analog Stereo"
  Input "Digital Stereo (IEC958)"

  If I pick one of the "output" I can hear the sound but the microphones
  are greyed out in the audio panel and I can't use it in any
  application. Instead if I select "Input "Analog Stereo"" I can record
  the audio but I can't hear any output!

  The volumes are turned up according also to a previous post I did
  related to similar issue I had in the past.

  The only workaround found so far is to execute: "pacmd load-module
  module-alsa-source device=hw:1,0".

  Please find attached "alsa-info" report.

  Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 
20.04):
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  snd_emu10k1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1149 F pulseaudio
   /dev/snd/controlC1:  ale1149 F pulseaudio
   /dev/snd/pcmC1D0p:   ale1149 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-08-29 (59 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  RfKill:
   
  Tags: ulyana third-party-packages
  Uname: Linux 5.4.0-52-generic x86_64
  UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069

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

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

[Touch-packages] [Bug 1901413] ProcModules.txt

[Alessio]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1901413/+attachment/5427978/+files/ProcModules.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/1901413

Title:
  Sound Blaster Audigy 5/Rx cannot be configured as input/output

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I 
cannot use it as both input and output device: it's working either as output or 
as input but not as input/output.
  I have installed "pavucontrol", when opening it in "configure" there are 
different options:

  Output "Analog Stereo"
  Output "Digital Stereo (IEC958)"
  Output "Surround 5.1"
  Output "Surround 4.1"
  Output "Surround 2.1"
  Output "Surround 7.1"
  Output "Surround 5.0"
  Output "Surround 4.0"
  Input "Analog Stereo"
  Input "Digital Stereo (IEC958)"

  If I pick one of the "output" I can hear the sound but the microphones
  are greyed out in the audio panel and I can't use it in any
  application. Instead if I select "Input "Analog Stereo"" I can record
  the audio but I can't hear any output!

  The volumes are turned up according also to a previous post I did
  related to similar issue I had in the past.

  The only workaround found so far is to execute: "pacmd load-module
  module-alsa-source device=hw:1,0".

  Please find attached "alsa-info" report.

  Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 
20.04):
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  snd_emu10k1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1149 F pulseaudio
   /dev/snd/controlC1:  ale1149 F pulseaudio
   /dev/snd/pcmC1D0p:   ale1149 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-08-29 (59 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  RfKill:
   
  Tags: ulyana third-party-packages
  Uname: Linux 5.4.0-52-generic x86_64
  UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069

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

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

[Touch-packages] [Bug 1901413] Lspci.txt

[Alessio]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1901413/+attachment/5427970/+files/Lspci.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/1901413

Title:
  Sound Blaster Audigy 5/Rx cannot be configured as input/output

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I 
cannot use it as both input and output device: it's working either as output or 
as input but not as input/output.
  I have installed "pavucontrol", when opening it in "configure" there are 
different options:

  Output "Analog Stereo"
  Output "Digital Stereo (IEC958)"
  Output "Surround 5.1"
  Output "Surround 4.1"
  Output "Surround 2.1"
  Output "Surround 7.1"
  Output "Surround 5.0"
  Output "Surround 4.0"
  Input "Analog Stereo"
  Input "Digital Stereo (IEC958)"

  If I pick one of the "output" I can hear the sound but the microphones
  are greyed out in the audio panel and I can't use it in any
  application. Instead if I select "Input "Analog Stereo"" I can record
  the audio but I can't hear any output!

  The volumes are turned up according also to a previous post I did
  related to similar issue I had in the past.

  The only workaround found so far is to execute: "pacmd load-module
  module-alsa-source device=hw:1,0".

  Please find attached "alsa-info" report.

  Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 
20.04):
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  snd_emu10k1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1149 F pulseaudio
   /dev/snd/controlC1:  ale1149 F pulseaudio
   /dev/snd/pcmC1D0p:   ale1149 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-08-29 (59 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  RfKill:
   
  Tags: ulyana third-party-packages
  Uname: Linux 5.4.0-52-generic x86_64
  UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069

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

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

[Touch-packages] [Bug 1901413] WifiSyslog.txt

[Alessio]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1901413/+attachment/5427981/+files/WifiSyslog.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/1901413

Title:
  Sound Blaster Audigy 5/Rx cannot be configured as input/output

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I 
cannot use it as both input and output device: it's working either as output or 
as input but not as input/output.
  I have installed "pavucontrol", when opening it in "configure" there are 
different options:

  Output "Analog Stereo"
  Output "Digital Stereo (IEC958)"
  Output "Surround 5.1"
  Output "Surround 4.1"
  Output "Surround 2.1"
  Output "Surround 7.1"
  Output "Surround 5.0"
  Output "Surround 4.0"
  Input "Analog Stereo"
  Input "Digital Stereo (IEC958)"

  If I pick one of the "output" I can hear the sound but the microphones
  are greyed out in the audio panel and I can't use it in any
  application. Instead if I select "Input "Analog Stereo"" I can record
  the audio but I can't hear any output!

  The volumes are turned up according also to a previous post I did
  related to similar issue I had in the past.

  The only workaround found so far is to execute: "pacmd load-module
  module-alsa-source device=hw:1,0".

  Please find attached "alsa-info" report.

  Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 
20.04):
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  snd_emu10k1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1149 F pulseaudio
   /dev/snd/controlC1:  ale1149 F pulseaudio
   /dev/snd/pcmC1D0p:   ale1149 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-08-29 (59 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  RfKill:
   
  Tags: ulyana third-party-packages
  Uname: Linux 5.4.0-52-generic x86_64
  UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069

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

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

[Touch-packages] [Bug 1901413] ProcCpuinfoMinimal.txt

[Alessio]

apport information

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

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

Title:
  Sound Blaster Audigy 5/Rx cannot be configured as input/output

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I 
cannot use it as both input and output device: it's working either as output or 
as input but not as input/output.
  I have installed "pavucontrol", when opening it in "configure" there are 
different options:

  Output "Analog Stereo"
  Output "Digital Stereo (IEC958)"
  Output "Surround 5.1"
  Output "Surround 4.1"
  Output "Surround 2.1"
  Output "Surround 7.1"
  Output "Surround 5.0"
  Output "Surround 4.0"
  Input "Analog Stereo"
  Input "Digital Stereo (IEC958)"

  If I pick one of the "output" I can hear the sound but the microphones
  are greyed out in the audio panel and I can't use it in any
  application. Instead if I select "Input "Analog Stereo"" I can record
  the audio but I can't hear any output!

  The volumes are turned up according also to a previous post I did
  related to similar issue I had in the past.

  The only workaround found so far is to execute: "pacmd load-module
  module-alsa-source device=hw:1,0".

  Please find attached "alsa-info" report.

  Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 
20.04):
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  snd_emu10k1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1149 F pulseaudio
   /dev/snd/controlC1:  ale1149 F pulseaudio
   /dev/snd/pcmC1D0p:   ale1149 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-08-29 (59 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  RfKill:
   
  Tags: ulyana third-party-packages
  Uname: Linux 5.4.0-52-generic x86_64
  UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069

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

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

[Touch-packages] [Bug 1901413] ProcEnviron.txt

[Alessio]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1901413/+attachment/5427976/+files/ProcEnviron.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/1901413

Title:
  Sound Blaster Audigy 5/Rx cannot be configured as input/output

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I 
cannot use it as both input and output device: it's working either as output or 
as input but not as input/output.
  I have installed "pavucontrol", when opening it in "configure" there are 
different options:

  Output "Analog Stereo"
  Output "Digital Stereo (IEC958)"
  Output "Surround 5.1"
  Output "Surround 4.1"
  Output "Surround 2.1"
  Output "Surround 7.1"
  Output "Surround 5.0"
  Output "Surround 4.0"
  Input "Analog Stereo"
  Input "Digital Stereo (IEC958)"

  If I pick one of the "output" I can hear the sound but the microphones
  are greyed out in the audio panel and I can't use it in any
  application. Instead if I select "Input "Analog Stereo"" I can record
  the audio but I can't hear any output!

  The volumes are turned up according also to a previous post I did
  related to similar issue I had in the past.

  The only workaround found so far is to execute: "pacmd load-module
  module-alsa-source device=hw:1,0".

  Please find attached "alsa-info" report.

  Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 
20.04):
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  snd_emu10k1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1149 F pulseaudio
   /dev/snd/controlC1:  ale1149 F pulseaudio
   /dev/snd/pcmC1D0p:   ale1149 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-08-29 (59 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  RfKill:
   
  Tags: ulyana third-party-packages
  Uname: Linux 5.4.0-52-generic x86_64
  UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069

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

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

[Touch-packages] [Bug 1901413] acpidump.txt

[Alessio]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1901413/+attachment/5427982/+files/acpidump.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/1901413

Title:
  Sound Blaster Audigy 5/Rx cannot be configured as input/output

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I 
cannot use it as both input and output device: it's working either as output or 
as input but not as input/output.
  I have installed "pavucontrol", when opening it in "configure" there are 
different options:

  Output "Analog Stereo"
  Output "Digital Stereo (IEC958)"
  Output "Surround 5.1"
  Output "Surround 4.1"
  Output "Surround 2.1"
  Output "Surround 7.1"
  Output "Surround 5.0"
  Output "Surround 4.0"
  Input "Analog Stereo"
  Input "Digital Stereo (IEC958)"

  If I pick one of the "output" I can hear the sound but the microphones
  are greyed out in the audio panel and I can't use it in any
  application. Instead if I select "Input "Analog Stereo"" I can record
  the audio but I can't hear any output!

  The volumes are turned up according also to a previous post I did
  related to similar issue I had in the past.

  The only workaround found so far is to execute: "pacmd load-module
  module-alsa-source device=hw:1,0".

  Please find attached "alsa-info" report.

  Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 
20.04):
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  snd_emu10k1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1149 F pulseaudio
   /dev/snd/controlC1:  ale1149 F pulseaudio
   /dev/snd/pcmC1D0p:   ale1149 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-08-29 (59 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  RfKill:
   
  Tags: ulyana third-party-packages
  Uname: Linux 5.4.0-52-generic x86_64
  UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069

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

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

[Touch-packages] [Bug 1901413] Lsusb-v.txt

[Alessio]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1901413/+attachment/5427974/+files/Lsusb-v.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/1901413

Title:
  Sound Blaster Audigy 5/Rx cannot be configured as input/output

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I 
cannot use it as both input and output device: it's working either as output or 
as input but not as input/output.
  I have installed "pavucontrol", when opening it in "configure" there are 
different options:

  Output "Analog Stereo"
  Output "Digital Stereo (IEC958)"
  Output "Surround 5.1"
  Output "Surround 4.1"
  Output "Surround 2.1"
  Output "Surround 7.1"
  Output "Surround 5.0"
  Output "Surround 4.0"
  Input "Analog Stereo"
  Input "Digital Stereo (IEC958)"

  If I pick one of the "output" I can hear the sound but the microphones
  are greyed out in the audio panel and I can't use it in any
  application. Instead if I select "Input "Analog Stereo"" I can record
  the audio but I can't hear any output!

  The volumes are turned up according also to a previous post I did
  related to similar issue I had in the past.

  The only workaround found so far is to execute: "pacmd load-module
  module-alsa-source device=hw:1,0".

  Please find attached "alsa-info" report.

  Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 
20.04):
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  snd_emu10k1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1149 F pulseaudio
   /dev/snd/controlC1:  ale1149 F pulseaudio
   /dev/snd/pcmC1D0p:   ale1149 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-08-29 (59 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  RfKill:
   
  Tags: ulyana third-party-packages
  Uname: Linux 5.4.0-52-generic x86_64
  UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069

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

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

[Touch-packages] [Bug 1901413] ProcInterrupts.txt

[Alessio]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1901413/+attachment/5427977/+files/ProcInterrupts.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/1901413

Title:
  Sound Blaster Audigy 5/Rx cannot be configured as input/output

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I 
cannot use it as both input and output device: it's working either as output or 
as input but not as input/output.
  I have installed "pavucontrol", when opening it in "configure" there are 
different options:

  Output "Analog Stereo"
  Output "Digital Stereo (IEC958)"
  Output "Surround 5.1"
  Output "Surround 4.1"
  Output "Surround 2.1"
  Output "Surround 7.1"
  Output "Surround 5.0"
  Output "Surround 4.0"
  Input "Analog Stereo"
  Input "Digital Stereo (IEC958)"

  If I pick one of the "output" I can hear the sound but the microphones
  are greyed out in the audio panel and I can't use it in any
  application. Instead if I select "Input "Analog Stereo"" I can record
  the audio but I can't hear any output!

  The volumes are turned up according also to a previous post I did
  related to similar issue I had in the past.

  The only workaround found so far is to execute: "pacmd load-module
  module-alsa-source device=hw:1,0".

  Please find attached "alsa-info" report.

  Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 
20.04):
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  snd_emu10k1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1149 F pulseaudio
   /dev/snd/controlC1:  ale1149 F pulseaudio
   /dev/snd/pcmC1D0p:   ale1149 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-08-29 (59 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  RfKill:
   
  Tags: ulyana third-party-packages
  Uname: Linux 5.4.0-52-generic x86_64
  UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069

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

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

[Touch-packages] [Bug 1901413] Lsusb-t.txt

[Alessio]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1901413/+attachment/5427973/+files/Lsusb-t.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/1901413

Title:
  Sound Blaster Audigy 5/Rx cannot be configured as input/output

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I 
cannot use it as both input and output device: it's working either as output or 
as input but not as input/output.
  I have installed "pavucontrol", when opening it in "configure" there are 
different options:

  Output "Analog Stereo"
  Output "Digital Stereo (IEC958)"
  Output "Surround 5.1"
  Output "Surround 4.1"
  Output "Surround 2.1"
  Output "Surround 7.1"
  Output "Surround 5.0"
  Output "Surround 4.0"
  Input "Analog Stereo"
  Input "Digital Stereo (IEC958)"

  If I pick one of the "output" I can hear the sound but the microphones
  are greyed out in the audio panel and I can't use it in any
  application. Instead if I select "Input "Analog Stereo"" I can record
  the audio but I can't hear any output!

  The volumes are turned up according also to a previous post I did
  related to similar issue I had in the past.

  The only workaround found so far is to execute: "pacmd load-module
  module-alsa-source device=hw:1,0".

  Please find attached "alsa-info" report.

  Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 
20.04):
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  snd_emu10k1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1149 F pulseaudio
   /dev/snd/controlC1:  ale1149 F pulseaudio
   /dev/snd/pcmC1D0p:   ale1149 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-08-29 (59 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  RfKill:
   
  Tags: ulyana third-party-packages
  Uname: Linux 5.4.0-52-generic x86_64
  UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069

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

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

[Touch-packages] [Bug 1901413] Lsusb.txt

[Alessio]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1901413/+attachment/5427972/+files/Lsusb.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/1901413

Title:
  Sound Blaster Audigy 5/Rx cannot be configured as input/output

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I 
cannot use it as both input and output device: it's working either as output or 
as input but not as input/output.
  I have installed "pavucontrol", when opening it in "configure" there are 
different options:

  Output "Analog Stereo"
  Output "Digital Stereo (IEC958)"
  Output "Surround 5.1"
  Output "Surround 4.1"
  Output "Surround 2.1"
  Output "Surround 7.1"
  Output "Surround 5.0"
  Output "Surround 4.0"
  Input "Analog Stereo"
  Input "Digital Stereo (IEC958)"

  If I pick one of the "output" I can hear the sound but the microphones
  are greyed out in the audio panel and I can't use it in any
  application. Instead if I select "Input "Analog Stereo"" I can record
  the audio but I can't hear any output!

  The volumes are turned up according also to a previous post I did
  related to similar issue I had in the past.

  The only workaround found so far is to execute: "pacmd load-module
  module-alsa-source device=hw:1,0".

  Please find attached "alsa-info" report.

  Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 
20.04):
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  snd_emu10k1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1149 F pulseaudio
   /dev/snd/controlC1:  ale1149 F pulseaudio
   /dev/snd/pcmC1D0p:   ale1149 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-08-29 (59 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  RfKill:
   
  Tags: ulyana third-party-packages
  Uname: Linux 5.4.0-52-generic x86_64
  UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069

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

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

[Touch-packages] [Bug 1901413] Dependencies.txt

[Alessio]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1901413/+attachment/5427969/+files/Dependencies.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/1901413

Title:
  Sound Blaster Audigy 5/Rx cannot be configured as input/output

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I 
cannot use it as both input and output device: it's working either as output or 
as input but not as input/output.
  I have installed "pavucontrol", when opening it in "configure" there are 
different options:

  Output "Analog Stereo"
  Output "Digital Stereo (IEC958)"
  Output "Surround 5.1"
  Output "Surround 4.1"
  Output "Surround 2.1"
  Output "Surround 7.1"
  Output "Surround 5.0"
  Output "Surround 4.0"
  Input "Analog Stereo"
  Input "Digital Stereo (IEC958)"

  If I pick one of the "output" I can hear the sound but the microphones
  are greyed out in the audio panel and I can't use it in any
  application. Instead if I select "Input "Analog Stereo"" I can record
  the audio but I can't hear any output!

  The volumes are turned up according also to a previous post I did
  related to similar issue I had in the past.

  The only workaround found so far is to execute: "pacmd load-module
  module-alsa-source device=hw:1,0".

  Please find attached "alsa-info" report.

  Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 
20.04):
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  snd_emu10k1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1149 F pulseaudio
   /dev/snd/controlC1:  ale1149 F pulseaudio
   /dev/snd/pcmC1D0p:   ale1149 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-08-29 (59 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  RfKill:
   
  Tags: ulyana third-party-packages
  Uname: Linux 5.4.0-52-generic x86_64
  UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069

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

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

[Touch-packages] [Bug 1901413] CurrentDmesg.txt

[Alessio]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1901413/+attachment/5427968/+files/CurrentDmesg.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/1901413

Title:
  Sound Blaster Audigy 5/Rx cannot be configured as input/output

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I 
cannot use it as both input and output device: it's working either as output or 
as input but not as input/output.
  I have installed "pavucontrol", when opening it in "configure" there are 
different options:

  Output "Analog Stereo"
  Output "Digital Stereo (IEC958)"
  Output "Surround 5.1"
  Output "Surround 4.1"
  Output "Surround 2.1"
  Output "Surround 7.1"
  Output "Surround 5.0"
  Output "Surround 4.0"
  Input "Analog Stereo"
  Input "Digital Stereo (IEC958)"

  If I pick one of the "output" I can hear the sound but the microphones
  are greyed out in the audio panel and I can't use it in any
  application. Instead if I select "Input "Analog Stereo"" I can record
  the audio but I can't hear any output!

  The volumes are turned up according also to a previous post I did
  related to similar issue I had in the past.

  The only workaround found so far is to execute: "pacmd load-module
  module-alsa-source device=hw:1,0".

  Please find attached "alsa-info" report.

  Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 
20.04):
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  snd_emu10k1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1149 F pulseaudio
   /dev/snd/controlC1:  ale1149 F pulseaudio
   /dev/snd/pcmC1D0p:   ale1149 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-08-29 (59 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  RfKill:
   
  Tags: ulyana third-party-packages
  Uname: Linux 5.4.0-52-generic x86_64
  UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069

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

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

[Touch-packages] [Bug 1901413] Re: Sound Blaster Audigy 5/Rx cannot be configured as input/output

[Alessio]

apport information

** Tags added: apport-collected third-party-packages ulyana

** Description changed:

  I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I 
cannot use it as both input and output device: it's working either as output or 
as input but not as input/output.
  I have installed "pavucontrol", when opening it in "configure" there are 
different options:
  
  Output "Analog Stereo"
  Output "Digital Stereo (IEC958)"
  Output "Surround 5.1"
  Output "Surround 4.1"
  Output "Surround 2.1"
  Output "Surround 7.1"
  Output "Surround 5.0"
  Output "Surround 4.0"
  Input "Analog Stereo"
  Input "Digital Stereo (IEC958)"
  
  If I pick one of the "output" I can hear the sound but the microphones
  are greyed out in the audio panel and I can't use it in any application.
  Instead if I select "Input "Analog Stereo"" I can record the audio but I
  can't hear any output!
  
  The volumes are turned up according also to a previous post I did
  related to similar issue I had in the past.
  
  The only workaround found so far is to execute: "pacmd load-module
  module-alsa-source device=hw:1,0".
  
  Please find attached "alsa-info" report.
  
  Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 
20.04):
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  snd_emu10k1
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.10
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ale1149 F pulseaudio
+  /dev/snd/controlC1:  ale1149 F pulseaudio
+  /dev/snd/pcmC1D0p:   ale1149 F...m pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux Mint 20
+ InstallationDate: Installed on 2020-08-29 (59 days ago)
+ InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
+ IwConfig:
+  enp3s0no wireless extensions.
+  
+  lono wireless extensions.
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu]
+ PackageArchitecture: amd64
+ ProcFB: 0 VESA VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash
+ ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-52-generic N/A
+  linux-backports-modules-5.4.0-52-generic  N/A
+  linux-firmware1.187.3
+ RfKill:
+  
+ Tags: ulyana third-party-packages
+ Uname: Linux 5.4.0-52-generic x86_64
+ UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 03/06/2018
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: P2.80
+ dmi.board.name: Z97 Extreme6
+ dmi.board.vendor: ASRock
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: To Be Filled By O.E.M.
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
+ dmi.product.family: To Be Filled By O.E.M.
+ dmi.product.name: To Be Filled By O.E.M.
+ dmi.product.sku: To Be Filled By O.E.M.
+ dmi.product.version: To Be Filled By O.E.M.
+ dmi.sys.vendor: To Be Filled By O.E.M.
+ modified.conffile..etc.pulse.default.pa: [modified]
+ mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1901413/+attachment/5427966/+files/AlsaInfo.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/1901413

Title:
  Sound Blaster Audigy 5/Rx cannot be configured as input/output

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I 
cannot use it as both input and output device: it's working either as output or 
as input but not as input/output.
  I have installed "pavucontrol", when opening it in "configure" there are 
different options:

  Output "Analog Stereo"
  Output "Digital Stereo (IEC958)"
  Output "Surround 5.1"
  Output "Surround 4.1"
  Output "Surround 2.1"
  Output "Surround 7.1"
  Output "Surround 5.0"
  Output "Surround 4.0"
  Input "Analog Stereo"
  Input "Digital Stereo (IEC958)"

  If I pick one of the "output" I can he

[Touch-packages] [Bug 1901413] CRDA.txt

[Alessio]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1901413/+attachment/5427967/+files/CRDA.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/1901413

Title:
  Sound Blaster Audigy 5/Rx cannot be configured as input/output

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I 
cannot use it as both input and output device: it's working either as output or 
as input but not as input/output.
  I have installed "pavucontrol", when opening it in "configure" there are 
different options:

  Output "Analog Stereo"
  Output "Digital Stereo (IEC958)"
  Output "Surround 5.1"
  Output "Surround 4.1"
  Output "Surround 2.1"
  Output "Surround 7.1"
  Output "Surround 5.0"
  Output "Surround 4.0"
  Input "Analog Stereo"
  Input "Digital Stereo (IEC958)"

  If I pick one of the "output" I can hear the sound but the microphones
  are greyed out in the audio panel and I can't use it in any
  application. Instead if I select "Input "Analog Stereo"" I can record
  the audio but I can't hear any output!

  The volumes are turned up according also to a previous post I did
  related to similar issue I had in the past.

  The only workaround found so far is to execute: "pacmd load-module
  module-alsa-source device=hw:1,0".

  Please find attached "alsa-info" report.

  Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 
20.04):
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  snd_emu10k1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1149 F pulseaudio
   /dev/snd/controlC1:  ale1149 F pulseaudio
   /dev/snd/pcmC1D0p:   ale1149 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-08-29 (59 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  RfKill:
   
  Tags: ulyana third-party-packages
  Uname: Linux 5.4.0-52-generic x86_64
  UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069

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

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

[Touch-packages] [Bug 1895418] Re: systemd-resolved default config for Caching is still "yes"

[Brian Murray]

Hello Cameron, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.3 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: systemd (Ubuntu Focal)
   Status: In Progress => 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1895418

Title:
  systemd-resolved default config for Caching is still "yes"

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

Bug description:
  [impact]

  /etc/systemd/resolved.conf file indicates the default value for
  'Cache=' is 'yes', but the actual default is 'no-negative'

  [test case]

  $ grep Cache /etc/systemd/resolved.conf
  #Cache=yes

  With the version of the package from -proposed it'll be "#Cache=no-
  negative".

  [regression potential]

  any regression would likely result in a mismatch between the commented
  default value of the Cache parameter and the actual build-time default
  value, or possibly a problem while systemd-resolved is parsing the
  resolved.conf file.

  [scope]

  this is needed only in focal.

  this was changed already in groovy as indicated in comment 1.

  bionic and earlier still use 'yes' as the default value of Cache=,
  which matches the resolved.conf file.

  [original description]

  Back in December, the default for systemd-resolved caching in Ubuntu
  systemd was changed to "no-negative" from the upstream default "yes"
  [0]

  In this change, the default value in the resolved.conf file was
  missed. As the defaults in this file are commented, the effective
  default is still "no-negative", however when viewing the config file,
  the commented default "yes" is at odds with the man page
  resolved.conf(5), which correctly states the default as "no-negative".

  This was an issue for me as I set DNSSEC to "yes", and expected
  Caching to also be "yes". Running DNSSEC with the default "no-
  negative" Caching is detrimental to performance resolving unsigned
  zones, as the non-existence of DNSSEC RRs must be looked up every
  time.

  The issue with the intersection of DNSSEC and Caching is for upstream,
  but the least that needs to be done here is updating the resolved.conf
  template with "Caching=no-negative" to match the man page and
  behaviour, and perhaps even adding a note to the "DNSSEC=" section of
  resolved.conf(5) that Caching should be enabled. Now that I'm looking
  at that man page, the default for DNSSEC is also listed as "allow-
  downgrade", whereas the default for Ubuntu is "no".

  [0] https://git.launchpad.net/~ubuntu-core-
  
dev/ubuntu/+source/systemd/commit/?id=b42658843a9496d6b6bb68ac159f2a9f0a8ba9db&h
  =ubuntu-focal

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

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

[Touch-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

[Brian Murray]

Hello Christian, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.3 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: systemd (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

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

Bug description:
  [impact]

  autopkgtests are failing/flaky and prevent other packages from
  migrating to -updates

  [test case]

  check autopkgtest history

  [regression potential]

  in regard to the changed test cases, any regression would likely
  result in either an incorrectly passed test, or an incorrectly failed
  test.

  [scope]

  for systemd, this is needed for x, b, and f.

  tests in g appear to be mostly stable, but I've opened MR (linked from
  this bug) to update the tests there as well.

  i don't plan to update x, as it's reaching ESM in ~6 months, and
  backporting the test fixes is more work than just a simple code copy,
  since there are additional differences/changes needed in the older
  version of systemd (and python3). the failing/flaky tests in x have
  been like that forever, and people have just retried them; we can keep
  retrying them until x moves into ESM next year.

  [original description]

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

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

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

  groovy
    amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services  (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-smoke (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  logind (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  storage(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  upstream   (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFBFF.B.F.F..FFBF
  udev   (F  0% S  0% B 10% => P 87%/) 
B.

[Touch-packages] [Bug 1882596] Re: systemd.unit(5) incorrectly refers to systemd.syntax(5)

[Brian Murray]

Hello Brian, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.3 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: systemd (Ubuntu Focal)
   Status: In Progress => 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1882596

Title:
  systemd.unit(5)  incorrectly refers to systemd.syntax(5)

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

Bug description:
  [impact]

  some systemd man pages refer to the wrong man section for some
  references

  [test case]

  e.g.

  $ man systemd.network | grep systemd.syntax
 A plain ini-style text file that encodes network configuration for 
matching network interfaces, used by systemd-networkd(8). See systemd.syntax(5) 
for a general description of the syntax.

  $ man 5 systemd.syntax
  No manual entry for systemd.syntax in section 5

  [regression potential]

  any regression would possibly cause confusion by referencing the wrong
  man section, or possibly cause a build failure, or problem with
  various man pages for systemd

  [scope]

  this is needed for f/g

  there is no systemd.syntax manpage in b or earlier

  [original description]

  In Ubuntu 20.04 LTS there is no systemd.syntax(5) it is actually
  systemd.syntax(7).

  "See systemd.syntax(5) for a general description of the syntax."

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

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

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Brian Murray]

Hello Ryan, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.3 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: systemd (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags removed: verification-done verification-done-focal
** 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1861941

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Won't Fix
Status in bcache-tools source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  SRU TEAM: The last 2 commits show a summary for the merges/changes
  I added some specific (to Bionic) notes in the template.
  Thanks!

  [Impact]

   * bcache-tools udev created symlinks might disappear when other udev
  events are processed for the same devices.

   * after mkfs.XXX in /dev/bcacheY you might face a condition where
  /dev/bcache/by-{uuid,label}/zzz symlinks are gone.

   * /dev/bcache/by-{uuid,label}/ symlinks are important so bcache
  devices can be addressed by their UUIDs and not the ordering they were
  assembled (MAAS depends on this feature, for example).

   * it was also discussed in this bug that systemd-udev should *not*
  populate /dev/disk/by-uuid/ with symlinks of disks that were bcache
  backing devices. this was turned into a discussion whether blkid
  should report those or not, and this discussion "died" after sometime.
  This last item is what the systemd update is all about: to disallow
  /dev/disk/by-XXX/ creation for bcache backing devices (a simple
  change that will reduce end users confusion).

  [Test Case]

   * The reproducer script is here:

     https://paste.ubuntu.com/p/37KGy2Smnp/

   * Bionic can't reproduce the issue with the 18.04 kernel, nor with
  the HWE kernel. Nevertheless, it is preferable that Bionic also do the
  same thing: to read bcache superblock and feed environment for
  /dev/bcache/by-{uuid,label} symlinks creation.

  [Regression Potential]

   * We are not depending on bcache device udev events any more when
  creating the /dev/bcache/by-{uuid,label}/ symlinks. Instead, we are
  depending on a wrapper script that heads bcache device superblock. If
  there is a bug in this wrapper the symlinks wouldn't work.

   * Previously we were thinking in asking the kernel team to remove the
  bcache udev event delta script they've done for previous case (LP:
  #1729145). It creates the udev events that were being read and filling
  the symlinks. We decided not to remove those (just from Groovy and on)
  so we don't need to worry on Breaks/Conflicts in between the kernel
  package and bcache-tools (and udev)).

   * Long story short: kernel will continue to emit bcache udev events
  as it did previously but now those events won't be used by anything -
  after installing this SRU - because udev wrapper script is doing this
  job (and doing it properly)

  [Other Info]

  - Original Description:

  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual
  linux-image-virtual:
    Installed: 5.4.0.12.15
    Candidate: 5.4.0.12.15
    Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Pac

[Touch-packages] [Bug 1897744] Re: VerifyHostKeyDNS not working due to missing trust-ad flag

[Brian Murray]

Hello Daniel, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.3 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: systemd (Ubuntu Focal)
   Status: In Progress => 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1897744

Title:
  VerifyHostKeyDNS not working due to missing trust-ad flag

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

Bug description:
  [impact]

  without trust-ad resolv.conf option, glibc will strip AD from systemd-
  resolved responses. one thing this will prevent working is ssh
  VerifyHostKeyDNS

  [test case]

  see
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1898590/comments/7

  [regression potential]

  regressions would likely involve DNS lookup failures, probably if
  DNSSEC is enabled but possibly even without, and likely when the
  application requesting the dns lookup processes the response AD.

  [scope]

  this is needed only in focal.

  glibc first stripped the AD in version 2.31, so this is not needed in
  bionic or earlier.

  this was added upstream in commit a742f9828ea which was included in
  v246, so this is fixed already in groovy.

  [original description]

  Hi,

  1)
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  2)
  systemd:245.4-4ubuntu3.2

  3)
  I set VerifyHostKeyDNS to YES and hosts are automatically verified via sshfp.

  4)
  I still get the security question
  Matching host key fingerprint found in DNS.
  Are you sure you want to continue connecting (yes/no/[fingerprint])?

  The issue is known and fixed in systemd v246.
  https://github.com/systemd/systemd/pull/16072

  Best regards
  Daniel

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

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

[Touch-packages] [Bug 1895418] Re: systemd-resolved default config for Caching is still "yes"

[Brian Murray]

** Description changed:

  [impact]
  
  /etc/systemd/resolved.conf file indicates the default value for 'Cache='
  is 'yes', but the actual default is 'no-negative'
  
  [test case]
  
- $ grep Cache /etc/systemd/resolved.conf 
+ $ grep Cache /etc/systemd/resolved.conf
  #Cache=yes
+ 
+ With the version of the package from -proposed it'll be "#Cache=no-
+ negative".
  
  [regression potential]
  
  any regression would likely result in a mismatch between the commented
  default value of the Cache parameter and the actual build-time default
  value, or possibly a problem while systemd-resolved is parsing the
  resolved.conf file.
  
  [scope]
  
  this is needed only in focal.
  
  this was changed already in groovy as indicated in comment 1.
  
  bionic and earlier still use 'yes' as the default value of Cache=, which
  matches the resolved.conf file.
  
  [original description]
  
  Back in December, the default for systemd-resolved caching in Ubuntu
  systemd was changed to "no-negative" from the upstream default "yes" [0]
  
  In this change, the default value in the resolved.conf file was missed.
  As the defaults in this file are commented, the effective default is
  still "no-negative", however when viewing the config file, the commented
  default "yes" is at odds with the man page resolved.conf(5), which
  correctly states the default as "no-negative".
  
  This was an issue for me as I set DNSSEC to "yes", and expected Caching
  to also be "yes". Running DNSSEC with the default "no-negative" Caching
  is detrimental to performance resolving unsigned zones, as the non-
  existence of DNSSEC RRs must be looked up every time.
  
  The issue with the intersection of DNSSEC and Caching is for upstream,
  but the least that needs to be done here is updating the resolved.conf
  template with "Caching=no-negative" to match the man page and behaviour,
  and perhaps even adding a note to the "DNSSEC=" section of
  resolved.conf(5) that Caching should be enabled. Now that I'm looking at
  that man page, the default for DNSSEC is also listed as "allow-
  downgrade", whereas the default for Ubuntu is "no".
  
  [0] https://git.launchpad.net/~ubuntu-core-
  
dev/ubuntu/+source/systemd/commit/?id=b42658843a9496d6b6bb68ac159f2a9f0a8ba9db&h
  =ubuntu-focal

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

Title:
  systemd-resolved default config for Caching is still "yes"

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  /etc/systemd/resolved.conf file indicates the default value for
  'Cache=' is 'yes', but the actual default is 'no-negative'

  [test case]

  $ grep Cache /etc/systemd/resolved.conf
  #Cache=yes

  With the version of the package from -proposed it'll be "#Cache=no-
  negative".

  [regression potential]

  any regression would likely result in a mismatch between the commented
  default value of the Cache parameter and the actual build-time default
  value, or possibly a problem while systemd-resolved is parsing the
  resolved.conf file.

  [scope]

  this is needed only in focal.

  this was changed already in groovy as indicated in comment 1.

  bionic and earlier still use 'yes' as the default value of Cache=,
  which matches the resolved.conf file.

  [original description]

  Back in December, the default for systemd-resolved caching in Ubuntu
  systemd was changed to "no-negative" from the upstream default "yes"
  [0]

  In this change, the default value in the resolved.conf file was
  missed. As the defaults in this file are commented, the effective
  default is still "no-negative", however when viewing the config file,
  the commented default "yes" is at odds with the man page
  resolved.conf(5), which correctly states the default as "no-negative".

  This was an issue for me as I set DNSSEC to "yes", and expected
  Caching to also be "yes". Running DNSSEC with the default "no-
  negative" Caching is detrimental to performance resolving unsigned
  zones, as the non-existence of DNSSEC RRs must be looked up every
  time.

  The issue with the intersection of DNSSEC and Caching is for upstream,
  but the least that needs to be done here is updating the resolved.conf
  template with "Caching=no-negative" to match the man page and
  behaviour, and perhaps even adding a note to the "DNSSEC=" section of
  resolved.conf(5) that Caching should be enabled. Now that I'm looking
  at that man page, the default for DNSSEC is also listed as "allow-
  downgrade", whereas the default for Ubuntu is "no".

  [0] https://git.launchpad.net/~ubuntu-core-
  
dev/ubuntu/+source/systemd/commit/?id=b42658843a9496d6b6bb68ac159f2a9f0a8ba9db&h
  =ubuntu-focal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/

[Touch-packages] [Bug 1899100] Re: whoopsie assert failure: double free or corruption (fasttop)

[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 whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1899100

Title:
  whoopsie assert failure: double free or corruption (fasttop)

Status in whoopsie package in Ubuntu:
  Confirmed

Bug description:
  Apport popped up saying whoopsie had crashed (I assume during a
  previous crash report upload?)

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AssertionMessage: double free or corruption (fasttop)
  CasperMD5CheckResult: skip
  CrashCounter: 1
  Date: Fri Oct  9 08:08:56 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2019-11-18 (325 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  RelatedPackageVersions: apport-noui N/A
  Signal: 6
  SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption 
(fasttop)") at malloc.c:5389
   _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at 
malloc.c:4298
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: double free or corruption (fasttop)
  UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago)
  UserGroups: N/A
  separator:

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

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

[Touch-packages] [Bug 1901694] Re: No hardware aceleration

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  No hardware aceleration

Status in xorg package in Ubuntu:
  New

Bug description:
  Computer HP EliteBook 8460p. It uses hybrid graphics card. Processor Intel 
Core i5-2520M CPU @ 2.50GHz × 4; 2nd generation. The system only runs well with 
llvmpipe (LLVM 6.0, 256 bits) graphic software, AMD Caicos sometimes it's 
charged too, but the graphic display have problems and don't goes fine or fluid.
  Maybe there is no support for the processor graphics because It's a little 
bit old. I don't know how to install AMD proprietary drivers, It maybe solve 
the problem.
  I installed Ubuntu 20.04 LTS but don't works, It don't charge any graphic 
interface, only a black screen. I only uses the system in recovery mode. For 
that reason I returned to Ubuntu 16.04 LTS but my graphics don't have hardware 
acceleration, only software acceleration. When I tried to play (Super Tux Kart 
for example) I expected a berry poor graphic improvement, so I can't play It.
  Thanks for your time and attention!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-122.124~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-122-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.24
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Oct 27 05:47:39 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e]
  InstallationDate: Installed on 2020-10-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 
(20200806)
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcEnviron:
   LANGUAGE=es_CR:es
   PATH=(custom, no user)
   LANG=es_CR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-122-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.60
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.asset.tag: IS09189
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.60:bd03/12/2015:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8460p
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Oct 27 05:43:49 2020
  xserver.configfile: default
  xserver.errors: AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.4
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1901723] Re: backport Refactor BN_R_NO_INVERSE logic in internal functions

[Launchpad Bug Tracker]

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

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

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

Title:
  backport Refactor BN_R_NO_INVERSE logic in internal functions

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  backport Refactor BN_R_NO_INVERSE logic in internal functions

  
https://github.com/openssl/openssl/commit/35bb0e44c6168facbb3acedbc7d4f2dcbdd65224

  https://github.com/openssl/openssl/issues/12129

  https://github.com/pyca/cryptography/issues/5521#issuecomment-717293145

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

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

[Touch-packages] [Bug 1901694] [NEW] No hardware aceleration

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Computer HP EliteBook 8460p. It uses hybrid graphics card. Processor Intel Core 
i5-2520M CPU @ 2.50GHz × 4; 2nd generation. The system only runs well with 
llvmpipe (LLVM 6.0, 256 bits) graphic software, AMD Caicos sometimes it's 
charged too, but the graphic display have problems and don't goes fine or fluid.
Maybe there is no support for the processor graphics because It's a little bit 
old. I don't know how to install AMD proprietary drivers, It maybe solve the 
problem.
I installed Ubuntu 20.04 LTS but don't works, It don't charge any graphic 
interface, only a black screen. I only uses the system in recovery mode. For 
that reason I returned to Ubuntu 16.04 LTS but my graphics don't have hardware 
acceleration, only software acceleration. When I tried to play (Super Tux Kart 
for example) I expected a berry poor graphic improvement, so I can't play It.
Thanks for your time and attention!

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-122.124~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-122-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.24
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Oct 27 05:47:39 2020
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] 
[1002:6760] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e]
InstallationDate: Installed on 2020-10-25 (1 days ago)
InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806)
MachineType: Hewlett-Packard HP EliteBook 8460p
ProcEnviron:
 LANGUAGE=es_CR:es
 PATH=(custom, no user)
 LANG=es_CR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-122-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/12/2015
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SCF Ver. F.60
dmi.board.name: 161C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 97.4E
dmi.chassis.asset.tag: IS09189
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.60:bd03/12/2015:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN
dmi.product.name: HP EliteBook 8460p
dmi.product.version: A0001D02
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Oct 27 05:43:49 2020
xserver.configfile: default
xserver.errors: AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.4
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial
-- 
No hardware aceleration
https://bugs.launchpad.net/bugs/1901694
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support

[Sebastien Bacher]

the issue is on the top of e.u.c 20.10 now

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

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

Title:
  gi.repository.GLib.GError: pk-client-error-quark: could not do
  untrusted question as no klass support

Status in packagekit package in Ubuntu:
  Triaged
Status in packagekit source package in Eoan:
  Won't Fix
Status in packagekit source package in Focal:
  Confirmed

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

  [Back trace]
  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 86, in on_pktask_finish
  results = self._pktask.generic_finish(result)
  gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted 
question as no klass support (8)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 89, in on_pktask_finish
  Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in 
__init__
  self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in 
__init__
  _window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
  TypeError: could not convert value for property `transient_for' from 
DialogCacheOutdated to GtkWindow

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

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

[Touch-packages] [Bug 1900812] Re: pulseaudio crashed with SIGSEGV in pa_sink_move_streams_to_default_sink() from report_jack_state() from mixer_class_event() from hctl_elem_event_handler() from snd_h

[Sebastien Bacher]

The autopkgtest issue got retried and cleared off now, there is one
error on e.u.c from the new version but it seems rather a report glitch
(still old version active at the time of reporting) so I'm going to tag
verified

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

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

Title:
  pulseaudio crashed with SIGSEGV in
  pa_sink_move_streams_to_default_sink() from report_jack_state() from
  mixer_class_event() from hctl_elem_event_handler() from
  snd_hctl_elem_throw_event()

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  * Impact

  There is a segfault issue started with the recent update

  * Test case

  We don't have specific steps to trigger the issue so test for regression and 
verify that reports stop on
  https://errors.ubuntu.com/problem/31c6bfaf0ac65939a763307ca3d3a4f27f38e9f0

  * Regression potential

  The regression was created by a fix for gnome-control-center device
  selection issues, check that the settings still work correctly,
  allowing to change devices and showing the active one as selected

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

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

[Touch-packages] [Bug 1901723] [NEW] backport Refactor BN_R_NO_INVERSE logic in internal functions

[Dimitri John Ledkov]

Public bug reported:

backport Refactor BN_R_NO_INVERSE logic in internal functions

https://github.com/openssl/openssl/commit/35bb0e44c6168facbb3acedbc7d4f2dcbdd65224

https://github.com/openssl/openssl/issues/12129

https://github.com/pyca/cryptography/issues/5521#issuecomment-717293145

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


** Tags: rls-ff-incoming rls-gg-incoming rls-hh-incoming

** Tags added: rls-ff-incoming rls-gg-incoming rls-hh-incoming

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

Title:
  backport Refactor BN_R_NO_INVERSE logic in internal functions

Status in openssl package in Ubuntu:
  New

Bug description:
  backport Refactor BN_R_NO_INVERSE logic in internal functions

  
https://github.com/openssl/openssl/commit/35bb0e44c6168facbb3acedbc7d4f2dcbdd65224

  https://github.com/openssl/openssl/issues/12129

  https://github.com/pyca/cryptography/issues/5521#issuecomment-717293145

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

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

[Touch-packages] [Bug 1901611] Re: can't launch focal container on bionic (TIOCGPTPEER)

[Kyle Nitzsche]

My kernel was stuck on 4.4. I had to manually update /boot/grub/grub.cfg
with 'sudo grub-mkconfig -o /boot/grub/grub.cfg' to get the 4.15 kernel
to be available in grub to boot from. After that, and booting from 4.15
kernel, I can get bash into focal lxd container. Marking invalid.

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

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

Title:
  can't launch focal container on bionic (TIOCGPTPEER)

Status in lxc package in Ubuntu:
  Invalid

Bug description:
  I cannot get a bash shell into a focal container on my bionic host.
  stdout shows TIOCGPTPEER unavailable message.
  `lxc ls` shows it is running, and I can ping it's IP address.

  $ lxc exec focal-NOTREAL -- bash
  Error: TIOCGPTPEER required but not available
  $ uname -a
  Linux timbre 4.4.0-164-generic #192-Ubuntu SMP Fri Sep 13 12:02:50 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
  $ uname -a
  Linux timbre 4.4.0-164-generic #192-Ubuntu SMP Fri Sep 13 12:02:50 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
  $ lxc config show focal-NOTREAL
  architecture: x86_64
  config:
image.architecture: amd64
image.description: ubuntu 20.04 LTS amd64 (release) (20201014)
image.label: release
image.os: ubuntu
image.release: focal
image.serial: "20201014"
image.type: squashfs
image.version: "20.04"
volatile.base_image: 
e81943d409153d0962e3855b7d9e6c60640571529f47b16eec2da5b4f2ad77ff
volatile.eth0.host_name: veth0ad5a93b
volatile.eth0.hwaddr: 00:16:3e:72:ed:8d
volatile.idmap.base: "0"
volatile.idmap.current: 
'[{"Isuid":true,"Isgid":false,"Hostid":100,"Nsid":0,"Maprange":10},{"Isuid":false,"Isgid":true,"Hostid":100,"Nsid":0,"Maprange":10}]'
volatile.idmap.next: 
'[{"Isuid":true,"Isgid":false,"Hostid":100,"Nsid":0,"Maprange":10},{"Isuid":false,"Isgid":true,"Hostid":100,"Nsid":0,"Maprange":10}]'
volatile.last_state.idmap: 
'[{"Isuid":true,"Isgid":false,"Hostid":100,"Nsid":0,"Maprange":10},{"Isuid":false,"Isgid":true,"Hostid":100,"Nsid":0,"Maprange":10}]'
volatile.last_state.power: RUNNING
  devices: {}
  ephemeral: false
  profiles:
  - default
  stateful: false
  description: ""

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

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

[Touch-packages] [Bug 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4

[Martin Wimpress]

** Changed in: pi-bluetooth (Ubuntu)
 Assignee: (unassigned) => Dave Jones (waveform)

** Changed in: pi-bluetooth (Ubuntu Groovy)
 Assignee: (unassigned) => Dave Jones (waveform)

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

Title:
  Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on
  Raspberry Pi 4

Status in bluez package in Ubuntu:
  Confirmed
Status in linux-raspi package in Ubuntu:
  Confirmed
Status in pi-bluetooth package in Ubuntu:
  Confirmed
Status in bluez source package in Groovy:
  New
Status in linux-raspi source package in Groovy:
  New
Status in pi-bluetooth source package in Groovy:
  New

Bug description:
  Raspberry pi 4 4Gb ram
  Ubuntu desktop 20.10 64 bit
  After reboot no Bluetooth devices connect, scanning Bluetooth devices works, 
results with same device name (duplicated and with not set up status).
  Sometimes after several reboots it works.
  If I use power off and cycle power then it works fine each time.

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

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

[Touch-packages] [Bug 1901295] Re: python3-chardet breaks install of python-chardet

[Christian Ehrhardt ]

Maintainers are free to remove python2 if there are no reverse dependencies 
left for the obvious unsupportability.
This happened here in [1] to resolve [2]

There also is no installation candidate left in a recent archive. Maybe
replaces/breaks was a bit too much (as users like you could be happy to
keep the old one around on an upgrade). But I'm unsure about the policy
on such cleanups, maybe it was intentional to remove old no more
supported bits. If you read the Debian bug I linked that makes sense.

This isn't jsuta n Ubuntu/Debian decision, also all upstream archives/support 
for 2.x have ended.
I'm unsure what to do here, asking you to get your application that depends on 
it upgraded?

[1]: 
https://salsa.debian.org/python-team/packages/chardet/-/commit/5b4be98c3c408e1b73f94f8fb133bb7ceadec81f
[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936289

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

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

Title:
  python3-chardet breaks install of python-chardet

Status in python3-chardet package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to install python-chardet (for python-2.7), but it fails
  because latest python3-chardet breaks python-chardet. I fail to
  understand why the python3 version of chardet would break the
  python2.7 version of the same module.

  PS: I know that python2.7 is not supported anymore, but I have an
  application that depends on it, and I need to install it, and that's
  now impossible because of this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-chardet/+bug/1901295/+subscriptions

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

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

[Rex Tsai]

Added upstream issue link in the description for referenc - platform:
add the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE status check (!597) ·
Merge Requests · NetworkManager / NetworkManager · GitLab -
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/597#note_588639


** Description changed:

  [Impact]
  
   In some cases, the wow is not configured and the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
  management of wake-on-LAN in NetworkManager).
  
   The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE 
bit.
   But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
   So, the management of wake-on-LAN still is done by NetworkManager.
  
   The killer 500s Wi-Fi does not want the network-manger to manager the
  wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set. (The
  driver will manager itself.) When the network-manager managers the wake-
  on-LAN, all of the Wi-Fi functions will be lost after the OS resumed
  from suspend.
  
  [Test Case]
  
   On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
   Step 1. Enter suspend (s2idle)
   Setp 2. Resume from suspend
  
   After resume from suspend, the Wi-Fi function still is normal.
  
   You can download the kernel and linux-firmware that backport the Qucalcomm's 
dirver fro focal from below link:
   https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633
  
  [Regression Potential]
  
   * This patch modifies the wake on lan parameters, please test that the
  corresponding feature still works fine with the different configuration
  values.
  
-  1. Magic packet test:
-   Set Wake on Wireless to off
-   Send magic packet to the system
-   Ensure it does not wake up
+  1. Magic packet test:
+   Set Wake on Wireless to off
+   Send magic packet to the system
+   Ensure it does not wake up
  
-   Set Wake on Wirless to on
-   Send magic packet to the system
-   Ensure it does wake up
+   Set Wake on Wirless to on
+   Send magic packet to the system
+   Ensure it does wake up
  
-  2. Wi-Fi function test after resumed from suspend:
-   After resume from suspend, the Wi-Fi should work normally.
-   Scan APs.
-   Connect to an AP.
+  2. Wi-Fi function test after resumed from suspend:
+   After resume from suspend, the Wi-Fi should work normally.
+   Scan APs.
+   Connect to an AP.
  
  [Other Info]
  
-  * None
+  * platform: add the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE status
+ check (!597) · Merge Requests · NetworkManager / NetworkManager · GitLab
+ -
+ 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/597#note_588639

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

Title:
  The network manager does not check the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

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

Bug description:
  [Impact]

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

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

   The killer 500s Wi-Fi does not want the network-manger to manager the
  wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set.
  (The driver will manager itself.) When the network-manager managers
  the wake-on-LAN, all of the Wi-Fi functions will be lost after the OS
  resumed from suspend.

  [Test Case]

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

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

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

  [Regression Potential]

   * This patch modifies the wake on lan parameters, please test that
  the corresponding feature still works fine with the different
  configuration values.

   1. Magic packet test:
    Set Wake on Wireless to off
    Send magic packet to the system
    Ensure it does not wake up

    Set Wake on Wirless to on
    Send magic packet to the system
    Ensure it does wake up

   2. Wi-Fi function test after resumed from suspend:
    After resume from suspend, the Wi-Fi should work normally.
    Scan APs.
    Connect to an AP.

  [Other Info]

   * platform: add the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE status
  check (!597) · Merge Requests · NetworkManager / NetworkManag

[Touch-packages] [Bug 1901295] Re: python3-chardet breaks install of python-chardet

[Christian Ehrhardt ]

I can confirm the behavior

** Changed in: python3-chardet (Ubuntu)
   Status: New => Confirmed

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

Title:
  python3-chardet breaks install of python-chardet

Status in python3-chardet package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to install python-chardet (for python-2.7), but it fails
  because latest python3-chardet breaks python-chardet. I fail to
  understand why the python3 version of chardet would break the
  python2.7 version of the same module.

  PS: I know that python2.7 is not supported anymore, but I have an
  application that depends on it, and I need to install it, and that's
  now impossible because of this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-chardet/+bug/1901295/+subscriptions

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

[Touch-packages] [Bug 1896073] Re: SRU the current 2.3.6 stable update

[Martin Wimpress]

** Changed in: tracker (Ubuntu Focal)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  SRU the current 2.3.6 stable update

Status in tracker package in Ubuntu:
  Fix Released
Status in tracker source package in Focal:
  Fix Committed

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

  The update add a 'tracker export' command, that's new and not used
  into any integration so has no real regression potential. It's an
  optional new option that can be used to export the data to migrate
  them to the incoming tracker3.

  * Test case

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

  Check that file search works correctly from the command line, shell
  and nautilus

  * Regression potential

  There is no specific change or feature to test in that update

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

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

[Touch-packages] [Bug 1896073] Re: SRU the current 2.3.6 stable update

[Sebastien Bacher]

** Changed in: tracker (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  SRU the current 2.3.6 stable update

Status in tracker package in Ubuntu:
  Fix Released
Status in tracker source package in Focal:
  Fix Committed

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

  The update add a 'tracker export' command, that's new and not used
  into any integration so has no real regression potential. It's an
  optional new option that can be used to export the data to migrate
  them to the incoming tracker3.

  * Test case

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

  Check that file search works correctly from the command line, shell
  and nautilus

  * Regression potential

  There is no specific change or feature to test in that update

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

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

[Touch-packages] [Bug 1460362] Re: "a week ago last thu" wrong

[gregrwm]

** Tags added: bionic focal xenial

** Tags added: amd64

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

Title:
  "a week ago last thu" wrong

Status in coreutils package in Ubuntu:
  New

Bug description:
  $ cal
May 2015
  Su Mo Tu We Th Fr Sa
  1  2
   3  4  5  6  7  8  9
  10 11 12 13 14 15 16
  17 18 19 20 21 22 23
  24 25 26 27 28 29 30
  31
  $ date +"%F %a" -d"today"
  2015-05-30 Sat
  $ date +"%F %a" -d"yesterday"
  2015-05-29 Fri
  $ date +"%F %a" -d"last thu"
  2015-05-28 Thu
  $ date +"%F %a" -d"7 days ago"
  2015-05-23 Sat
  $ date +"%F %a" -d"a week ago"
  2015-05-23 Sat
  $ date +"%F %a" -d"7 days ago yesterday"
  2015-05-22 Fri
  $ date +"%F %a" -d"a week ago yesterday"
  2015-05-22 Fri
  $ date +"%F %a" -d"7 days ago last thu"
  2015-05-21 Thu
  $ date +"%F %a" -d"a week ago last thu"
  2015-05-20 Wed

  shouldn't "7 days ago last thu" and "a week ago last thu" be the same?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: coreutils 8.23-3ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic i686
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: i386
  Date: Sat May 30 21:50:10 2015
  InstallationDate: Installed on 2015-01-14 (136 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1899100] Re: whoopsie assert failure: double free or corruption (fasttop)

[Marc Deslauriers]

Here's a proposed fix, not sure if this is the exact cause of the
double-free or if duplicate keys are acceptable or not.

** Patch added: "Proposed Fix"
   
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1899100/+attachment/5427819/+files/whoopsie_0.2.73~test1.debdiff

** Information type changed from Private to Public

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

Title:
  whoopsie assert failure: double free or corruption (fasttop)

Status in whoopsie package in Ubuntu:
  Confirmed

Bug description:
  Apport popped up saying whoopsie had crashed (I assume during a
  previous crash report upload?)

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AssertionMessage: double free or corruption (fasttop)
  CasperMD5CheckResult: skip
  CrashCounter: 1
  Date: Fri Oct  9 08:08:56 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2019-11-18 (325 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  RelatedPackageVersions: apport-noui N/A
  Signal: 6
  SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption 
(fasttop)") at malloc.c:5389
   _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at 
malloc.c:4298
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: double free or corruption (fasttop)
  UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago)
  UserGroups: N/A
  separator:

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

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

[Touch-packages] [Bug 1899347] Re: whoopsie assert failure: double free or corruption (fasttop)

[Marc Deslauriers]

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

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1899100
   whoopsie assert failure: double free or corruption (fasttop)

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

Title:
  whoopsie assert failure: double free or corruption (fasttop)

Status in whoopsie package in Ubuntu:
  New

Bug description:
  whoopsie assert failure: double free or corruption (fasttop)

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AssertionMessage: double free or corruption (fasttop)
  CasperMD5CheckResult: skip
  CrashCounter: 1
  Date: Sun Oct 11 14:20:14 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2016-07-01 (1562 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=pl_PL.UTF-8
   PATH=(custom, no user)
  RebootRequiredPkgs:
   libc6
   libc6
   dbus
   dbus
  RelatedPackageVersions: apport-noui N/A
  Signal: 6
  SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f806f9fc128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f806f9fe5d8 "double free or corruption 
(fasttop)") at malloc.c:5389
   _int_free (av=0x7f806fa2eba0 , p=0x555bfe91aa20, have_lock=0) at 
malloc.c:4298
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_remove_all () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: double free or corruption (fasttop)
  UpgradeStatus: Upgraded to groovy on 2020-09-18 (22 days ago)
  UserGroups: N/A
  separator:

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

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

[Touch-packages] [Bug 1899100] Re: whoopsie assert failure: double free or corruption (fasttop)

[Launchpad Bug Tracker]

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

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

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

Title:
  whoopsie assert failure: double free or corruption (fasttop)

Status in whoopsie package in Ubuntu:
  Confirmed

Bug description:
  Apport popped up saying whoopsie had crashed (I assume during a
  previous crash report upload?)

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AssertionMessage: double free or corruption (fasttop)
  CasperMD5CheckResult: skip
  CrashCounter: 1
  Date: Fri Oct  9 08:08:56 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2019-11-18 (325 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  RelatedPackageVersions: apport-noui N/A
  Signal: 6
  SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption 
(fasttop)") at malloc.c:5389
   _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at 
malloc.c:4298
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: double free or corruption (fasttop)
  UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago)
  UserGroups: N/A
  separator:

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

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

[Touch-packages] [Bug 1901603] Re: Couldn't connect to my nextcloud account (GOA)

[Sebastien Bacher]

Thanks, https://gitlab.gnome.org/GNOME/gnome-online-
accounts/-/issues/149

** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues #149
   https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/149

** Package changed: gnome-control-center (Ubuntu) => gnome-online-
accounts (Ubuntu)

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Triaged

** Also affects: gnome-online-accounts via
   https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/149
   Importance: Unknown
   Status: Unknown

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

Title:
  Couldn't connect to my nextcloud account (GOA)

Status in gnome-online-accounts:
  Unknown
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  Connection to my nextcloud account with Gnome-Online-Accounts is not possible
  This happened after upgrading Ubuntu to 20.10.
  It worked fine with 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 26 20:37:07 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-10-15 (10 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1901603/+subscriptions

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

[Touch-packages] [Bug 1824260] Re: wrong kerning in SS-5 PDF form fields

[xiota]

> How do you make it replace CourierStd with Ubuntu Mono?
> Do you have custom font configuration which affect it?

I created custom config files to define the fallback fonts after
having issues with strange fallback font selection a few years ago.  
The  problem is associated with the generic font families including 
fonts of the wrong type (described in my previous comment #17).

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

Title:
  wrong kerning in SS-5 PDF form fields

Status in Poppler:
  New
Status in fontconfig package in Ubuntu:
  In Progress

Bug description:
  What I expected to happen:

  I am filling out the SS-5 Social Security Administration form (see
  attached). I entered "John Jacob Smith" into the "First", "Full Middle
  Name", and "Last" fields on page 5.

  What happened instead:

  I can enter the text without issue, but some of the letters are
  wrongly positioned, i.e. the kerning is wrong. For example, the letter
  "i" overlaps with the letter "m" in "Smith" (see attached image). It
  looks like the font in the fields might be displaying a variable width
  font when it is supposed to be a fixed-wdith font.

  Discussion:

  Since this bug is also present in xpdf and Okular (but not mupdf), I'm
  guessing this isn't a bug in Evince itself. However, I am reporting it
  here as a courtesy to other users (since Evince is the default PDF
  reader) and because I'm not sure which dependency is responsible. (I'm
  also not sure if it's a direct dependency problem or if it's something
  else like a font configuration issue.)

  Here is the output for pdffonts ss-5.pdf:

  name type  encoding emb 
sub uni object ID
   -  --- 
--- --- -
  IHPIKC+ArialMT   CID TrueType  Identity-H   yes 
yes yes824  0
  ArialMT  TrueType  WinAnsi  no  
no  no 826  0
  Arial-BoldMT TrueType  WinAnsi  no  
no  no 828  0
  CourierStd   Type 1WinAnsi  no  
no  no 145  0
  HelveticaType 1WinAnsi  no  
no  no 197  0
  MyriadPro-RegularType 1WinAnsi  no  
no  no 198  0
  ZapfDingbats Type 1ZapfDingbats no  
no  no 199  0

  I asked about this in an Ask Ubuntu question nearly a year ago, but
  received no response, so I am reporting a bug now instead:

  https://askubuntu.com/questions/1031235/wrong-letter-positioning-and-
  font-in-pdf-form

  Ubuntu version:

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  evince version:

  $ apt-cache policy evince
  evince:
    Installed: 3.28.4-0ubuntu1
    Candidate: 3.28.4-0ubuntu1
    Version table:
   *** 3.28.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 10 21:27:11 2019
  InstallationDate: Installed on 2018-12-12 (119 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1901603] [NEW] Couldn't connect to my nextcloud account (GOA)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Connection to my nextcloud account with Gnome-Online-Accounts is not possible
This happened after upgrading Ubuntu to 20.10.
It worked fine with 20.04.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-control-center 1:3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 26 20:37:07 2020
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2020-10-15 (10 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-online-accounts (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: amd64 apport-bug groovy third-party-packages
-- 
Couldn't connect to my nextcloud account (GOA)
https://bugs.launchpad.net/bugs/1901603
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gnome-online-accounts 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 1824260] Re: wrong kerning in SS-5 PDF form fields

[xiota]

The following config would be better than the one I proposed earlier:


  CourierStd
  
  Courier
  



  CourierStd
  monospace


I submitted a request to fontconfig:

https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/262

-

What one person considers sane isn't necessarily so.
*Assuming* sane defaults isn't really sensible.

Here are some examples, not directly related to the issue at hand:

  * In a "sane" configuration, we'd expect a list of monospace fonts 
when requesting the generic monospace font family.  Similarly for 
the generic serif and sans-serif families.  However, the following 
commands show that fonts of all three types are included in all of 
the generic families.

   fc-match -s monospace
   fc-match -s sans-serif
   fc-match -s serif

Normally, it doesn't cause problems because fonts of the right 
type are at the beginning of the list.  However, if a specific font 
is requested, an obviously incorrect substitution can be made 
(eg, sans-serif font shown when serif was requested) because fonts 
of all types are in all of the lists.

 Maybe developers in the past thought it was fine because some 
 config further along could be assumed to have sane defaults?  
 Or maybe they thought it was just a theoretical problem that 
 wouldn't ever occur?  But it's not just theoretical. I have 
 encountered real issues, which is why I know of it at all.

  * Many people believe that if they request a font that isn't 
installed, Ubuntu will substitute a font it "thinks" looks 
similar.  They don't realize that it has to be defined in the 
config files.

So if they request a font that's not defined, like CourierStd, 
Ubuntu will fallback to sans-serif, even though every human 
immediately knows the Courier substitutions should be used – 
and that would be the sane default.  But here, we're explicitly 
deciding *not* to, even knowing there is a theoretical risk of 
problematic substitutions in the future.


** Bug watch added: gitlab.freedesktop.org/fontconfig/fontconfig/-/issues #262
   https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/262

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

Title:
  wrong kerning in SS-5 PDF form fields

Status in Poppler:
  New
Status in fontconfig package in Ubuntu:
  In Progress

Bug description:
  What I expected to happen:

  I am filling out the SS-5 Social Security Administration form (see
  attached). I entered "John Jacob Smith" into the "First", "Full Middle
  Name", and "Last" fields on page 5.

  What happened instead:

  I can enter the text without issue, but some of the letters are
  wrongly positioned, i.e. the kerning is wrong. For example, the letter
  "i" overlaps with the letter "m" in "Smith" (see attached image). It
  looks like the font in the fields might be displaying a variable width
  font when it is supposed to be a fixed-wdith font.

  Discussion:

  Since this bug is also present in xpdf and Okular (but not mupdf), I'm
  guessing this isn't a bug in Evince itself. However, I am reporting it
  here as a courtesy to other users (since Evince is the default PDF
  reader) and because I'm not sure which dependency is responsible. (I'm
  also not sure if it's a direct dependency problem or if it's something
  else like a font configuration issue.)

  Here is the output for pdffonts ss-5.pdf:

  name type  encoding emb 
sub uni object ID
   -  --- 
--- --- -
  IHPIKC+ArialMT   CID TrueType  Identity-H   yes 
yes yes824  0
  ArialMT  TrueType  WinAnsi  no  
no  no 826  0
  Arial-BoldMT TrueType  WinAnsi  no  
no  no 828  0
  CourierStd   Type 1WinAnsi  no  
no  no 145  0
  HelveticaType 1WinAnsi  no  
no  no 197  0
  MyriadPro-RegularType 1WinAnsi  no  
no  no 198  0
  ZapfDingbats Type 1ZapfDingbats no  
no  no 199  0

  I asked about this in an Ask Ubuntu question nearly a year ago, but
  received no response, so I am reporting a bug now instead:

  https://askubuntu.com/questions/1031235/wrong-letter-positioning-and-
  font-in-pdf-form

  Ubuntu version:

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  evince version:

  $ apt-cache policy evince
  evince:
    Installed: 3.28.4-0ubuntu1
    Candidate: 3.28.4-0ubuntu1
    Version table:
   *** 3.28.4-0ubuntu1 500
  500 htt

[Touch-packages] [Bug 1888726] Re: systemd-udevd regression: some renamed network interfaces stuck in "pending" state

[Łukasz Zemczak]

** Changed in: netplan.io (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  systemd-udevd regression: some renamed network interfaces stuck in
  "pending" state

Status in netplan.io package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Invalid
Status in netplan.io source package in Focal:
  New
Status in systemd source package in Focal:
  Invalid

Bug description:
  Summary:

  In Ubuntu Server 20.04 LTS and newer, using netplan.io and systemd-
  networkd, in certain network configurations, renamed network
  interfaces get stuck in "pending" state and are not configured
  properly. On boot, system is stuck on "Wait for Network to be
  Configured" for 2 minutes.

  
  How to reproduce:

  1. Configure a machine (for example, a virtual machine) with two Ethernet 
network cards. Make note of MAC addresses of these network cards.
  2. Set up netplan with a single configuration file, contents are in the 
attached "00-static.yaml" file. Replace the MAC addresses to match your setup. 
IP address configuration is omitted and is not necessary to reproduce the bug.
  3. Reboot the system.

  
  Expected outcome:

  1. System boots in a reasonable time
  2. First network interface (wan) is brought up, is not renamed, and is marked 
as configured by networkd
  3. Second network interface (lan) is brought up, renamed, configured for 
MTU=9000, and is marked as configured by networkd
  4. VLAN interface (vlan20) is brought up, renamed, configured for MTU=9000, 
and is marked as configured by networkd

  
  Actual outcome:

  1. System boot is delayed by 2 minutes
  2. First network interface (wan) is configured as expected
  3. Second network interface (lan) is configured as expected
  4. VLAN interface (vlan20) seems to be configured as expected, but is stuck 
in "pending" state according to networkctl list

  
  Test environment:

Hardware:

Virtual machine with the following configuration

* 4 amd64 CPU cores (also tested with a single core)
* 1 GB RAM
* 8 GB disk
* 2 network cards (vmxnet3 in VMware, virtio in Parallels)

Working as expected:

* [1] Ubuntu Server 19.10, kernel 5.3.0-62, netplan.io
  0.99-0ubuntu3~19.10.2, systemd+udev 242-7ubuntu3.11

Broken:

* [2] Ubuntu Server 19.10, kernel 5.3.0-62, netplan.io 
0.99-0ubuntu3~19.10.2, systemd 242-7ubuntu3.11, udev 245.4-4ubuntu3.1
* [3] Ubuntu Server 20.04 LTS, kernel 5.4.0-42, netplan.io 
0.99-0ubuntu3~20.04.2, systemd+udev 245.4-4ubuntu3.1
* [4] Ubuntu Server 20.04 LTS, kernel 5.4.0-42, netplan.io 
0.99-0ubuntu3~20.04.2, systemd+udev vanilla upstream git e9769453
* [5] Ubuntu Server 20.04 LTS, kernel 5.4.0-42, netplan.io 
0.99-0ubuntu3~20.04.2, systemd+udev vanilla upstream git v242
* [6] Ubuntu Server 20.10 daily-live, kernel 5.4.0-26, netplan.io 
0.99-0ubuntu5, systemd+udev 245.6-3ubuntu3

  [2] As noted above, issue was reproduced in 19.10 by upgrading ONLY
  udev and libudev1 to ones shipped in focal-updates.

  [4] It was also reproduced in vanilla upstream systemd, git master
  commit e9769453. Just installed on top of existing systemd using "sudo
  ninja -C build install".

  [5] Interestingly enough, issue also seems to exist in vanilla v242.
  Either that, or the installation didn't replace the packaged systemd
  properly. This may hint at some distribution-specific patch that got
  removed before 20.04.

  This issue was reproduced in VMware ESXi 6.7U3, VMware Fusion 11.5.5
  and Parallels Desktop 15.1.4. This leads me to believe that network
  card drivers or virtualisation engines do not play part in the issue.

  
  Extra observations:

  To make the example configuration (00-static.yaml) not get stuck in
  "pending" state, any one of the following options helps:

  * Remove "set-name" parameter for "lan" interface
  * Remove "mtu" parameter for "lan" interface
  * Remove "wan" interface entirely

  I got some data/logs for each of these scenarios for eoan [1] and
  focal [3], as well as the original broken config, and put them
  together in the attached "parallels.tar.gz".

  
  Note about Apport:

  Attached apport report was generated for test environment [2] above.

  
  Attachments:

  * 00-static.yaml: minimalistic broken netplan configuration example
  * parallels.tar.gz: various logs for eoan [1] and focal [3], as described in 
"Extra observations" above

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: udev 245.4-4ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18
  Uname: Linux 5.3.0-62-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.9
  Architecture: amd64
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Thu Jul 23 18:54:58 2020
  InstallationDate: Installed on 2020-07-22 (1 days ago)
  InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Re

[Touch-packages] [Bug 1899745] Re: [SRU] alsa-utils: let alsactl support _boot section defined in ucm

[Hui Wang]

Don't know

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

Title:
  [SRU] alsa-utils: let alsactl support _boot section defined in ucm

Status in HWE Next:
  New
Status in alsa-utils package in Ubuntu:
  Fix Released
Status in alsa-utils source package in Focal:
  Fix Committed

Bug description:
  This patchset was backported from mainline alsa-utils 1.2.3, and
  groovy already integrated alsa-utils 1.2.3, there is no need to SRU
  this patchset to groovy, so only for focal.

  [Impact]
  We enabled 2 Dell soundwire audio machines, these machines depend on
  ucm to make the audio work, and in the ucm, the _boot section defined
  some amixers values for the 1st booting, these amixer values should
  be set to audio driver at the 1st booting, otherwise the whole audio
  doesn't work.

  [Fix]
  Backport some patches from mainline v1.2.3, these patches make the
  alsactl support _boot section in the ucm, then the systemd will call
  alsactl init after booting, the alsactl init will setting all amixers
  defined in the _boot section of ucm.

  [Test Case]
  On the Dell soundwire audio machines, After booting up, run 'amixer
  contents | less' to check all amixer values defined in the _boot
  section of ucm, all values read from driver are same as the ones in
  the ucm, test speaker/microphone/headset, all work well.

  [Regression Risk]
  This could introduce failure on runing 'alsactl init' for some machines,
  then the amixers will not be initialized correctly, users will experience
  all audio can't work like speaker doesn't output sound or microphone can't
  record sound. But this regression possibility is very low, since We have
  tested it both on soundwire machines and non-soundwire machines, all worked 
well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1899745/+subscriptions

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

[Touch-packages] [Bug 1899745] Re: [SRU] alsa-utils: let alsactl support _boot section defined in ucm

[Kai-Chuan Hsieh]

@hui.wang

hello,

Do you know what blocks it?

Thanks,

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

Title:
  [SRU] alsa-utils: let alsactl support _boot section defined in ucm

Status in HWE Next:
  New
Status in alsa-utils package in Ubuntu:
  Fix Released
Status in alsa-utils source package in Focal:
  Fix Committed

Bug description:
  This patchset was backported from mainline alsa-utils 1.2.3, and
  groovy already integrated alsa-utils 1.2.3, there is no need to SRU
  this patchset to groovy, so only for focal.

  [Impact]
  We enabled 2 Dell soundwire audio machines, these machines depend on
  ucm to make the audio work, and in the ucm, the _boot section defined
  some amixers values for the 1st booting, these amixer values should
  be set to audio driver at the 1st booting, otherwise the whole audio
  doesn't work.

  [Fix]
  Backport some patches from mainline v1.2.3, these patches make the
  alsactl support _boot section in the ucm, then the systemd will call
  alsactl init after booting, the alsactl init will setting all amixers
  defined in the _boot section of ucm.

  [Test Case]
  On the Dell soundwire audio machines, After booting up, run 'amixer
  contents | less' to check all amixer values defined in the _boot
  section of ucm, all values read from driver are same as the ones in
  the ucm, test speaker/microphone/headset, all work well.

  [Regression Risk]
  This could introduce failure on runing 'alsactl init' for some machines,
  then the amixers will not be initialized correctly, users will experience
  all audio can't work like speaker doesn't output sound or microphone can't
  record sound. But this regression possibility is very low, since We have
  tested it both on soundwire machines and non-soundwire machines, all worked 
well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1899745/+subscriptions

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

[Touch-packages] [Bug 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4

[Juerg Haefliger]

** Package changed: linux-raspi2 (Ubuntu) => linux-raspi (Ubuntu)

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

** Also affects: pi-bluetooth (Ubuntu Groovy)
   Importance: Undecided
   Status: New

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

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

Title:
  Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on
  Raspberry Pi 4

Status in bluez package in Ubuntu:
  Confirmed
Status in linux-raspi package in Ubuntu:
  Confirmed
Status in pi-bluetooth package in Ubuntu:
  Confirmed
Status in bluez source package in Groovy:
  New
Status in linux-raspi source package in Groovy:
  New
Status in pi-bluetooth source package in Groovy:
  New

Bug description:
  Raspberry pi 4 4Gb ram
  Ubuntu desktop 20.10 64 bit
  After reboot no Bluetooth devices connect, scanning Bluetooth devices works, 
results with same device name (duplicated and with not set up status).
  Sometimes after several reboots it works.
  If I use power off and cycle power then it works fine each time.

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

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

[Touch-packages] [Bug 1899232] Re: ansible fails with systemd 245.4

[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/1899232

Title:
  ansible fails with systemd 245.4

Status in ansible:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ansible 2.10.2 fails when determining state of a service on systemd
  245.4 in Ubuntu 20.04. It's related to this bug
  [https://github.com/systemd/systemd/pull/16424]. This bug has been
  fixed in systemd 245.7. Is there plans to release a fix with this?
  Without this fix, ansible fails when attempting to manage services on
  Ubuntu 20.04.

  Ubuntu release: Ubuntu 20.04
  Package: 245.4-4ubuntu3.2 amd64

  What I expected to happen
  Service marked as started when it is stopped.

  What happened instead
  Got 'failed: [127.0.0.1] (item=ssh) => {"ansible_loop_var": "item", 
"changed": false, "item": "ssh", "msg": "Service is in unknown state", 
"status": {}}' 

  
  Thank you.

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

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

[Touch-packages] [Bug 1901585] Re: Ubuntu 20.04 LTS Desktop Screen blinking/flickering black and side menu bar turn upsidedown

[Daniel van Vugt]

** Tags added: nvidia

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-450
(Ubuntu)

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

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

** Changed in: nvidia-graphics-drivers-450 (Ubuntu)
   Importance: Undecided => High

** Summary changed:

- Ubuntu 20.04 LTS Desktop Screen blinking/flickering black and side menu bar 
turn upsidedown
+ [nvidia] Ubuntu 20.04 LTS Desktop Screen blinking/flickering black and side 
menu bar turn upsidedown

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

Title:
  [nvidia] Ubuntu 20.04 LTS Desktop Screen blinking/flickering black and
  side menu bar turn upsidedown

Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  New

Bug description:
  Sometimes after I change the used account to the not pirivleged user account 
and clik to side menu bar the (Xorg/Gnome) screen randomly start turn black and 
back to normal while i move the mouse, somtimes just stay black but if there is 
an opened window (used to be nautilus or FireFox) and is move over the mause 
cursor over its is start partially show the right content.
  Paralelly the side menu turn upside down randomly.

  I never experienced this with root account and find that if I lock the
  screen and relese it is used to solve the problem for a while.

  The problem raised after upgrade Ubuntu from 18.04 LTS to 20.04 LTS

  The computer is a desktop so there no accelerometer giroscope.
  The screen is a 4K montior with 3840×2160 resolution and work on 29,97 Hz
  The graphics card is an ASUS NVIDIA GeForce GTX 1060 6GB

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Ez egy könyvtár: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Ez egy könyvtár: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ez egy könyvtár: 
'/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  450.80.02  Wed Sep 23 
01:13:39 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 26 18:13:01 2020
  DistUpgraded: 2020-10-07 15:58:42,341 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Nem sikerült a gyermekfolyamat 
(„./xorg_fix_proprietary.py”) végrehajtása (Nincs ilyen fájl vagy könyvtár) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-51-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106 [GeForce GTX 1060 6GB] [1043:85ab]
  InstallationDate: Installed on 2017-01-03 (1391 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=74c33349-7cf3-4ced-8462-62ad4c43832d ro quiet splash 
crashkernel=512M-:192M vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-10-07 (19 days ago)
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3504
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/29/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Prod

[Touch-packages] [Bug 1901561] Re: night light not working

[Daniel van Vugt]

It looks like the Nvidia driver also is not working for you... Try
removing and reinstalling the Nvidia driver via the 'Additional Drivers'
app.

Failing that, I think this should be merged into one of: bug 1880739,
bug 1890957

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

Title:
  night light not working

Status in Ubuntu:
  Incomplete

Bug description:
  I'm using ubuntu in a laptop with dual boot. Last week, I did an
  update in my bios through windows and since then the night light in
  ubuntu is not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 26 12:32:17 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-51-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] [10de:1f11] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TU106M [GeForce RTX 2060 Mobile] [17aa:3ffd]
  InstallationDate: Installed on 2020-08-17 (70 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  LightdmDisplayLog: xf86EnableIOPorts: failed to set IOPL for I/O (Operation 
not permitted)
  MachineType: LENOVO 81SX
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=5ed3584d-a0d4-44d4-a253-f2da8672df17 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 06/23/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y540-15IRH
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN39WW:bd06/23/2020:svnLENOVO:pn81SX:pvrLegionY540-15IRH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY540-15IRH:
  dmi.product.family: Legion Y540-15IRH
  dmi.product.name: 81SX
  dmi.product.sku: LENOVO_MT_81SX_BU_idea_FM_Legion Y540-15IRH
  dmi.product.version: Legion Y540-15IRH
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1901563] Re: Kernel panic - Xorg tainted - i915

[Daniel van Vugt]

Your kernel log mentions:

[  618.131916] i915 :00:02.0: [drm] *ERROR* Atomic update failure on
pipe B (start=36634 end=36635) time 217 us, min 1431, max 1439, scanline
start 1421, end 1440

which I think can only happen in Xorg sessions.

Try selecting 'Ubuntu on Wayland' from the login screen before you enter
your password.

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

Title:
  Kernel panic - Xorg tainted - i915

Status in linux package in Ubuntu:
  New

Bug description:
  I've just upgraded to 20.10. After logging in and using PyCharm for a
  while, the system froze, and I had to do a REISUB. It turned out to be
  a kernel panic and seems related to Xorg and the i915 driver.

  This has now happened multiple times, and not all crashes have
  happened while using PyCharm.

  I've tried using the ppa:canonical-kernel-team/ppa to install a new
  kernel (5.8.0-26-generic) but that did not help.

  [ 1620.425014] general protection fault, probably for non-canonical address 
0xe296718293aa0a0a:  [#1] SMP PTI 
  [ 1620.425017] CPU: 2 PID: 1749 Comm: Xorg Tainted: GW 
5.8.0-26-generic #27-Ubuntu
  [ 1620.425018] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.2.1 
02/21/2018
  [ 1620.425023] RIP: 0010:kmem_cache_alloc+0x7e/0x230
  [ 1620.425025] Code: 95 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 a0 59 33 
4d 4d 8b 20 4d 85 e4 0f 84 81 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 
48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb
  [ 1620.425026] RSP: 0018:b1f6c19e79b0 EFLAGS: 00010286
  [ 1620.425028] RAX: e296718293aa0a0a RBX:  RCX: 
0002
  [ 1620.425029] RDX: 7d5e RSI: 0dc0 RDI: 
441461604a80
  [ 1620.425031] RBP: b1f6c19e79e0 R08: d1f6bfc84a80 R09: 

  [ 1620.425032] R10:  R11: 8de1eca2f6c2 R12: 
e296718293aa08b2
  [ 1620.425033] R13: 0dc0 R14: 8de2488364c0 R15: 
8de2488364c0
  [ 1620.425034] FS:  7fe9c3b52a40() GS:8de25e68() 
knlGS:
  [ 1620.425035] CS:  0010 DS:  ES:  CR0: 80050033
  [ 1620.425037] CR2: 7f6c1433c000 CR3: 000488622001 CR4: 
003606e0
  [ 1620.425038] Call Trace:
  [ 1620.425087]  ? vma_create+0x30/0x460 [i915]
  [ 1620.425122]  vma_create+0x30/0x460 [i915]
  [ 1620.425124]  ? mutex_lock+0x13/0x40
  [ 1620.425157]  i915_vma_instance+0xd2/0xe0 [i915]
  [ 1620.425187]  eb_lookup_vma+0xd7/0x1c0 [i915]
  [ 1620.425217]  eb_lookup_vmas+0x79/0x200 [i915]
  [ 1620.425247]  eb_relocate+0x18/0x1b0 [i915]
  [ 1620.425275]  i915_gem_do_execbuffer+0x265/0x8d0 [i915]
  [ 1620.425278]  ? enqueue_task_fair+0x159/0x590
  [ 1620.425282]  ? __radix_tree_replace+0x4a/0xe0
  [ 1620.425285]  ? _cond_resched+0x1a/0x50
  [ 1620.425287]  ? kmem_cache_alloc_trace+0x168/0x240
  [ 1620.425290]  ? __kmalloc_node+0x201/0x300
  [ 1620.425320]  i915_gem_execbuffer2_ioctl+0x237/0x4a0 [i915]
  [ 1620.425348]  ? intel_engines_add_sysfs+0x150/0x150 [i915]
  [ 1620.425350]  ? radix_tree_lookup+0xd/0x10
  [ 1620.425379]  ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915]
  [ 1620.425395]  drm_ioctl_kernel+0xae/0xf0 [drm]
  [ 1620.425406]  drm_ioctl+0x238/0x3d0 [drm]
  [ 1620.425434]  ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915]
  [ 1620.425437]  ? fput+0x13/0x15
  [ 1620.425440]  ? __sys_recvmsg+0x94/0xb0
  [ 1620.425442]  ksys_ioctl+0x8e/0xc0
  [ 1620.425444]  __x64_sys_ioctl+0x1a/0x20
  [ 1620.425447]  do_syscall_64+0x49/0xc0
  [ 1620.425449]  entry_SYSCALL_64_after_hwframe+0x44/0xa9

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Mon Oct 26 16:33:28 2020
  DistUpgraded: 2020-10-23 13:15:10,351 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: groovy
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Dell UHD Graphics 620 [1028:07e6]
  InstallationDate: Installed on 

[Touch-packages] [Bug 1901561] Re: night light not working

[Daniel van Vugt]

It also looks like the BIOS is hiding the Intel GPU, which your old Xorg
logs seem to suggest is required to drive the screen, and night light.

Please look in your BIOS to try and re-enable the integrated Intel GPU.

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

Title:
  night light not working

Status in Ubuntu:
  Incomplete

Bug description:
  I'm using ubuntu in a laptop with dual boot. Last week, I did an
  update in my bios through windows and since then the night light in
  ubuntu is not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 26 12:32:17 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-51-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] [10de:1f11] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TU106M [GeForce RTX 2060 Mobile] [17aa:3ffd]
  InstallationDate: Installed on 2020-08-17 (70 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  LightdmDisplayLog: xf86EnableIOPorts: failed to set IOPL for I/O (Operation 
not permitted)
  MachineType: LENOVO 81SX
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=5ed3584d-a0d4-44d4-a253-f2da8672df17 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 06/23/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y540-15IRH
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN39WW:bd06/23/2020:svnLENOVO:pn81SX:pvrLegionY540-15IRH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY540-15IRH:
  dmi.product.family: Legion Y540-15IRH
  dmi.product.name: 81SX
  dmi.product.sku: LENOVO_MT_81SX_BU_idea_FM_Legion Y540-15IRH
  dmi.product.version: Legion Y540-15IRH
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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