date:20201022

[Touch-packages] [Bug 1887968] Re: Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter

2020-10-22 Thread Bug Watch Updater

** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => High

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

Title:
  Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD
  laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter

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

Bug description:
  I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
  to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.

  I've been unsuccessful to pair with 2 different bluetooth mice.
  However bluetooth seems to work with other devices. I'm under the
  impression that this problem only happens with Bluetooth LE devices.

  Trying to pair using bluetoothctl fails with the
  org.bluez.Error.AuthenticationCanceled error:

  [bluetooth]# pair E5:5B:67:2A:09:76
  Attempting to pair with E5:5B:67:2A:09:76
  [CHG] Device E5:5B:67:2A:09:76 Connected: yes
  [CHG] Device E5:5B:67:2A:09:76 Connected: no
  Failed to pair: org.bluez.Error.AuthenticationCanceled

  A quick google search for org.bluez.Error.AuthenticationCanceled
  reported nothing relevant.

  Running btmon while trying to pair with the device gives me the
  following:

  Bluetooth monitor ver 5.53
  = Note: Linux version 5.4.0-40-generic (x86_64)   
0.998188
  = Note: Bluetooth subsystem version 2.22  
0.998193
  = New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0) 
 [hci0] 0.998194
  = Open Index: E8:6F:38:9C:2B:3C   
 [hci0] 0.998195
  = Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)   
 [hci0] 0.998197
  @ MGMT Open: bluetoothd (privileged) version 1.14 
   {0x0001} 0.998198
  @ MGMT Open: btmon (privileged) version 1.14  
   {0x0002} 0.998310
  @ MGMT Command: Pair Device (0x0019) plen 8   
{0x0001} [hci0] 8.162442
  LE Address: E5:5B:67:2A:09:76 (Static)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8   
  #1 [hci0] 8.162527
  Own address type: Public (0x00)
  Filter policy: Ignore not in white list (0x01)
  PHYs: 0x01
  Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
  > HCI Event: Command Complete (0x0e) plen 4   
  #2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
  Status: Success (0x00)
  < HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6   
  #3 [hci0] 8.284654
  Extended scan: Enabled (0x01)
  Filter duplicates: Enabled (0x01)
  Duration: 0 msec (0x)
  Period: 0.00 sec (0x)
  > HCI Event: Command Complete (0x0e) plen 4   
  #4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
  Status: Success (0x00)
  > HCI Event: LE Meta Event (0x3e) plen 52 
  #5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
  Num reports: 1
  Entry 0
Event type: 0x0013
  Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
  Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)

[Touch-packages] [Bug 1901117] [NEW] [TUF Gaming FX505GT_FX505GT, Nvidia GPU 94 HDMI/DP, Digital Out, HDMI] Playback problem

2020-10-22 Thread Dhananjaya Kurukulasooriya

Public bug reported:

volume indicators show that the sound is playing but there is no any
playback sound with the system

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  dhananjaya  19109 F pulseaudio
 /dev/snd/controlC0:  dhananjaya  19109 F pulseaudio
 /dev/snd/pcmC0D0c:   dhananjaya  19109 F...m pulseaudio
 /dev/snd/pcmC0D0p:   dhananjaya  19109 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 23 08:58:40 2020
InstallationDate: Installed on 2020-10-22 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: HDA NVidia - HDA NVidia
Symptom_Jack: Digital Out, HDMI
Symptom_Type: None of the above
Title: [TUF Gaming FX505GT_FX505GT, Nvidia GPU 94 HDMI/DP, Digital Out, HDMI] 
Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/22/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FX505GT.308
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: FX505GT
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.:bvrFX505GT.308:bd09/22/2020:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505GT_FX505GT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505GT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: TUF Gaming
dmi.product.name: TUF Gaming FX505GT_FX505GT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T08:16:34.031419

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


** Tags: amd64 apport-bug focal

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

Title:
  [TUF Gaming FX505GT_FX505GT, Nvidia GPU 94 HDMI/DP, Digital Out, HDMI]
  Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  volume indicators show that the sound is playing but there is no any
  playback sound with the system

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dhananjaya  19109 F pulseaudio
   /dev/snd/controlC0:  dhananjaya  19109 F pulseaudio
   /dev/snd/pcmC0D0c:   dhananjaya  19109 F...m pulseaudio
   /dev/snd/pcmC0D0p:   dhananjaya  19109 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 23 08:58:40 2020
  InstallationDate: Installed on 2020-10-22 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: HDA NVidia - HDA NVidia
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [TUF Gaming FX505GT_FX505GT, Nvidia GPU 94 HDMI/DP, Digital Out, HDMI] 
Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX505GT.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX505GT
  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.:bvrFX505GT.308:bd09/22/2020:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505GT_FX505GT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505GT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming
  dmi.product.name: TUF Gaming FX505GT_FX505GT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T08:16:34.031419

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

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

[Touch-packages] [Bug 1901115] Re: package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1

2020-10-22 Thread Daniel van Vugt

I'm not sure we should allow failure to start the daemon to be
classified as an install failure...

Okt 23 07:08:46 atom systemd[1]: [0;1;39m[0;1;31m[0;1;39mbluetooth.service: 
Killing process 636 (bluetoothd) with signal SIGKILL.[0m
Okt 23 07:08:46 atom systemd[1]: 
[0;1;38;5;185m[0;1;39m[0;1;38;5;185mbluetooth.service: Failed with result 
'exit-code'.[0m
Okt 23 07:08:46 atom systemd[1]: bluetooth.service: Unit process 636 
(bluetoothd) remains running after unit stopped.
Okt 23 07:08:46 atom systemd[1]: [0;1;31m[0;1;39m[0;1;31mFailed to start 
Bluetooth service.[0m
dpkg: error processing package bluez (--configure):
 installed bluez package post-installation script subprocess returned error 
exit status 1
Setting up libwind0-heimdal:amd64 (7.7.0+dfsg-2) ...

** Summary changed:

- package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez 
package post-installation script subprocess returned error exit status 1
+ package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez 
package post-installation script subprocess returned error exit status 1 
[Failed to start Bluetooth service.]

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

Title:
  package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez
  package post-installation script subprocess returned error exit status
  1 [Failed to start Bluetooth service.]

Status in bluez package in Ubuntu:
  New

Bug description:
  package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez
  package post-installation script subprocess returned error exit status
  1

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: bluez 5.55-0ubuntu1
  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
  Date: Fri Oct 23 07:08:46 2020
  ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3180
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8e6f60a5-d013-4d5d-83ed-df27737e1381 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10
  SourcePackage: bluez
  Title: package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago)
  dmi.bios.date: 10/03/2019
  dmi.bios.release: 1.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 05YMV0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd10/03/2019:br1.10:svnDellInc.:pnLatitude3180:pvr:rvnDellInc.:rn05YMV0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3180
  dmi.product.sku: 07B2
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 74:70:FD:58:F6:73  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:2712 acl:0 sco:0 events:305 errors:0
TX bytes:50942 acl:0 sco:0 commands:305 errors:0

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

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

[Touch-packages] [Bug 1901115] Re: package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1

2020-10-22 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez
  package post-installation script subprocess returned error exit status
  1

Status in bluez package in Ubuntu:
  New

Bug description:
  package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez
  package post-installation script subprocess returned error exit status
  1

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: bluez 5.55-0ubuntu1
  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
  Date: Fri Oct 23 07:08:46 2020
  ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3180
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8e6f60a5-d013-4d5d-83ed-df27737e1381 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10
  SourcePackage: bluez
  Title: package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago)
  dmi.bios.date: 10/03/2019
  dmi.bios.release: 1.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 05YMV0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd10/03/2019:br1.10:svnDellInc.:pnLatitude3180:pvr:rvnDellInc.:rn05YMV0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3180
  dmi.product.sku: 07B2
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 74:70:FD:58:F6:73  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:2712 acl:0 sco:0 events:305 errors:0
TX bytes:50942 acl:0 sco:0 commands:305 errors:0

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

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

[Touch-packages] [Bug 1901115] [NEW] package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1

2020-10-22 Thread Akbarbek Musayev

Public bug reported:

package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez
package post-installation script subprocess returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: bluez 5.55-0ubuntu1
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
Date: Fri Oct 23 07:08:46 2020
ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
 Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated Webcam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 3180
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8e6f60a5-d013-4d5d-83ed-df27737e1381 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.5ubuntu2
 apt  2.1.10
SourcePackage: bluez
Title: package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago)
dmi.bios.date: 10/03/2019
dmi.bios.release: 1.10
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.0
dmi.board.name: 05YMV0
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd10/03/2019:br1.10:svnDellInc.:pnLatitude3180:pvr:rvnDellInc.:rn05YMV0:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 3180
dmi.product.sku: 07B2
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 74:70:FD:58:F6:73  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:2712 acl:0 sco:0 events:305 errors:0
TX bytes:50942 acl:0 sco:0 commands:305 errors:0

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


** Tags: amd64 apport-package groovy

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

Title:
  package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez
  package post-installation script subprocess returned error exit status
  1

Status in bluez package in Ubuntu:
  New

Bug description:
  package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez
  package post-installation script subprocess returned error exit status
  1

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: bluez 5.55-0ubuntu1
  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
  Date: Fri Oct 23 07:08:46 2020
  ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3180
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8e6f60a5-d013-4d5d-83ed-df27737e1381 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10
  SourcePackage: bluez
  Title: package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago)
  dmi.bios.date: 10/03/2019
  dmi.bios.release: 1.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 05YMV0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd10/03/2019:br1.10:svnDellInc.:pnLatitude3180:pvr:rvnDellInc.:rn05YMV0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3180
  dmi.product.sku: 07B2
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 74:70:FD:58:F6:73  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:2712 acl:0 sco:0 events:305 errors:0
TX bytes:50942 acl:0 sco:0 commands:305 errors:0

To manage notifications about this bug g

[Touch-packages] [Bug 1901016] Re: APP GRID TOO LARGE

2020-10-22 Thread Daniel van Vugt

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

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3217
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3217

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3217
   Importance: Unknown
   Status: Unknown

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

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Low

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

Title:
  APP GRID TOO LARGE

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When you click on the app button, the icons in the app grid shown is
  way too large.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 22 13:11:04 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2020-10-03 (18 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   LANGUAGE=en_NG:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NG
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=9f6d2f48-a8cd-464f-8ea4-11fec7ad9369 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-focal
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-focal
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/gnome-shell/+bug/1901016/+subscriptions

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

[Touch-packages] [Bug 1900906] Re: Can't use dead keys or input e.g. Chinese characters in GNOME shell

2020-10-22 Thread Daniel van Vugt

** Also affects: ibus (Ubuntu Groovy)
   Importance: Undecided
   Status: Invalid

** Also affects: mutter (Ubuntu Groovy)
   Importance: Medium
   Status: Fix Released

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

** Tags added: fixed-in-3.36.7 fixed-in-3.38.1 fixed-upstream

** No longer affects: ibus (Ubuntu Groovy)

** No longer affects: ibus (Ubuntu)

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

Title:
  Can't use dead keys or input e.g. Chinese characters in GNOME shell

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. 
Under X, if I try to input an accentuated character, such as á or ü, in places 
like the search field in the overview or when writing a folder name in the app 
grid, nothing appears. Under Wayland, it fails each time on the first input of 
an accentuated character, then it works.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-01 (174 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Package: ibus
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (22 days ago)
  UserGroups: sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1025388] Re: Internal mic stops working when plugging in headphones

2020-10-22 Thread Daniel van Vugt

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

Title:
  Internal mic stops working when plugging in headphones

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

Bug description:
  I am currently running Quantal and when I plug headphones into my
  headphone socket (which has an icon of a headset next to it, so I
  presume it can take some kind of headset), the internal mic on my
  laptop stops working. If I unplug the headphones the internal mic
  works as normal.

  I tried this with two different sets of headphones (one of which has a
  mic, and the other I think has a mic too).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: pulseaudio 1:2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
  Uname: Linux 3.5.0-4-generic i686
  ApportVersion: 2.3-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jono   1860 F pulseaudio
   /dev/snd/pcmC0D0c:   jono   1860 F...m pulseaudio
  Date: Mon Jul 16 11:01:32 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET56WW (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4239CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4239CTO
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1901073] Re: Ubuntu 19.10 x86_64 robotic audio sound when using hardware acceleration

2020-10-22 Thread Daniel van Vugt

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.


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

** Tags added: eoan

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

Title:
  Ubuntu 19.10 x86_64 robotic audio sound when using hardware
  acceleration

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  In certain  application I am expiriencing robotic soud. Latest chrome
  works just fine, but discord with hardware acceleration and telegram
  sound robotic.

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

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

[Touch-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)

2020-10-22 Thread Daniel van Vugt

** Changed in: chromium-browser (Ubuntu)
 Assignee: hormoz hatamiyan (hormoz239) => (unassigned)

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

Title:
  Images are washed out or colors are skewed in some apps (particularly
  Image Viewer and Chrome)

Status in GNOME Shell:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in colord package in Ubuntu:
  Confirmed
Status in eog package in Ubuntu:
  Confirmed
Status in inkscape package in Ubuntu:
  Confirmed

Bug description:
  Images are washed out or colors are skewed in some apps, notably
  Chrome/Chromium and Image Viewer (eog).

  Workaround:

  Settings > Devices > Colour >
  and disable or remove your monitor's colour profile

  Originally reported in
  https://bugzilla.gnome.org/show_bug.cgi?id=675645

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/938751/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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

2020-10-22 Thread Bug Watch Updater

** Changed in: ansible
   Status: Unknown => Fix Released

-- 
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:
  New

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 1900906] Re: Can't use dead keys or input e.g. Chinese characters in GNOME shell

2020-10-22 Thread Gunnar Hjalmarsson

It's a regression from mutter 3.36.6. Fixed through:

https://gitlab.gnome.org/GNOME/mutter/-/commit/3536ad08

Fix confirmed via this PPA:

https://launchpad.net/~gunnarhj/+archive/ubuntu/mutter

Upload separately or together with other stuff?

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

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

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

** No longer affects: ibus (Ubuntu Focal)

** Changed in: mutter (Ubuntu Focal)
   Importance: Undecided => Medium

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

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

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1413
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1413

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1413
   Importance: Unknown
   Status: Unknown

** Tags added: regression-update

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

Title:
  Can't use dead keys or input e.g. Chinese characters in GNOME shell

Status in Mutter:
  Unknown
Status in ibus package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Triaged

Bug description:
  I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. 
Under X, if I try to input an accentuated character, such as á or ü, in places 
like the search field in the overview or when writing a folder name in the app 
grid, nothing appears. Under Wayland, it fails each time on the first input of 
an accentuated character, then it works.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-01 (174 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Package: ibus
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (22 days ago)
  UserGroups: sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1900414] Re: sudo[5580]: root : problem with defaults entries ; TTY=unknown ; PWD=/root ; USER=navycat ;

2020-10-22 Thread navycat

Fixed on 20.10 release

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

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

Title:
  sudo[5580]: root : problem with defaults entries ; TTY=unknown ;
  PWD=/root ; USER=navycat ;

Status in sudo package in Ubuntu:
  Fix Released

Bug description:
  sudo[5580]: root : problem with defaults entries ; TTY=unknown ; 
PWD=/root ; USER=navycat ;
  sudo[11487]:  navycat : problem with defaults entries ; TTY=pts/0 ; 
PWD=/home/navycat ; USER=root ;

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: sudo 1.9.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Oct 19 13:03:37 2020
  InstallationDate: Installed on 2020-10-07 (11 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
  SourcePackage: sudo
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1900906] Re: Can't input accents in GNOME shell

2020-10-22 Thread Gunnar Hjalmarsson

I can reproduce the issue on focal but not on groovy. I installed the
groovy version of the ibus binaries on focal, but the issue was still
present, so this seems not to be an ibus bug.

I can type ü with a German keyboard layout, so it seems to be about dead
keys rather than accented letters as such. Furthermore, I can't input
e.g. Chinese characters using IBus at all.

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

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

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

** Summary changed:

- Can't input accents in GNOME shell
+ Can't use dead keys or input e.g. Chinese characters in GNOME shell

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

Title:
  Can't use dead keys or input e.g. Chinese characters in GNOME shell

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in ibus package in Ubuntu:
  Invalid

Bug description:
  I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. 
Under X, if I try to input an accentuated character, such as á or ü, in places 
like the search field in the overview or when writing a folder name in the app 
grid, nothing appears. Under Wayland, it fails each time on the first input of 
an accentuated character, then it works.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-01 (174 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Package: ibus
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (22 days ago)
  UserGroups: sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1901090] [NEW] run-parts: failed to stat component /etc/network/if-post-down.d/avahi-daemon: No such file or directory

2020-10-22 Thread kalvdans

Public bug reported:

avahi-daemon 0.7-4ubuntu7 installs a symlink /etc/network/if-post-down.d
/avahi-daemon -> ../if-up.d/avahi-daemon but doesn't install the symlink
target /etc/network/if-up.d/avahi-daemon

That makes ifdown complain:

$ sudo ifdown enp2s0f3
run-parts: failed to stat component /etc/network/if-post-down.d/avahi-daemon: 
No such file or directory

The problem only occurs if avahi-daemon is installed from scratch; if it
is upgraded from older versions, the missing file is still there
according to this line in /var/lib/dpkg/status:

/etc/network/if-up.d/avahi-daemon 6dbf1a91ab420a99d1205972d6401e67
obsolete

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

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

Title:
  run-parts: failed to stat component /etc/network/if-post-down.d/avahi-
  daemon: No such file or directory

Status in avahi package in Ubuntu:
  New

Bug description:
  avahi-daemon 0.7-4ubuntu7 installs a symlink /etc/network/if-post-
  down.d/avahi-daemon -> ../if-up.d/avahi-daemon but doesn't install the
  symlink target /etc/network/if-up.d/avahi-daemon

  That makes ifdown complain:

  $ sudo ifdown enp2s0f3
  run-parts: failed to stat component /etc/network/if-post-down.d/avahi-daemon: 
No such file or directory

  The problem only occurs if avahi-daemon is installed from scratch; if
  it is upgraded from older versions, the missing file is still there
  according to this line in /var/lib/dpkg/status:

  /etc/network/if-up.d/avahi-daemon 6dbf1a91ab420a99d1205972d6401e67
  obsolete

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

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

[Touch-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)

2020-10-22 Thread hormoz hatamiyan

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => hormoz hatamiyan (hormoz239)

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

Title:
  Images are washed out or colors are skewed in some apps (particularly
  Image Viewer and Chrome)

Status in GNOME Shell:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in colord package in Ubuntu:
  Confirmed
Status in eog package in Ubuntu:
  Confirmed
Status in inkscape package in Ubuntu:
  Confirmed

Bug description:
  Images are washed out or colors are skewed in some apps, notably
  Chrome/Chromium and Image Viewer (eog).

  Workaround:

  Settings > Devices > Colour >
  and disable or remove your monitor's colour profile

  Originally reported in
  https://bugzilla.gnome.org/show_bug.cgi?id=675645

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/938751/+subscriptions

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

[Touch-packages] [Bug 929054] Re: AltGr key doesn't work properly in xfce4-terminal and gnome-terminal with Maori layout, and Hawaiian is not supported

2020-10-22 Thread Launchpad Bug Tracker

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

** Changed in: console-setup (Ubuntu)
   Status: New => Confirmed

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

Title:
  AltGr key doesn't work properly in xfce4-terminal and gnome-terminal
  with Maori layout, and Hawaiian is not supported

Status in console-setup package in Ubuntu:
  Confirmed
Status in vte package in Ubuntu:
  Confirmed

Bug description:
  I just installed xfce4-xkb-plugin in order to select various keyboard
  layout. I soon found out that the AltGr key isn't working properly in
  xfce4-terminal, gnome-terminal and pterm. I am running the 64-bit
  version of xubuntu 11.10 and 12.04 on my Compaq computer, and the
  32-bit version of 12.04 on a Shuttle computer.

  .
  Updated 2012-04-03:
  This also affects 32-bit versions of Ubuntu and Xubuntu 11.10 and 12.04 
beta-2. It also affects the current Linux Mint. ALSO, note that other layouts 
with AltGr now work properly when Maori is not in the list. Also I have added 
lack of Hawaiian support to this bug. I am now updated to the Beta-2 version of 
xubuntu on the Compaq 12.04 system, and Ubuntu 12.04 beta-2 on the shuttle.
  .

  For example, select the Maori keyboard layout. This layout enters
  vowels with macrons like āēīōūĀĒĪŌŪ when the AltGr key is held on.
  (This does work in Firefox, which I'm using to enter this report, and
  also in xterm, but also fails in pterm. It does work in AbiWord).
  Various other layouts use AltGr, for example the US alt-intl layout
  uses AltGr plus the minus key as a dead key for entering vowels with
  macrons - those do not work under xfce4-terminal and pterm, but do
  work in various other apps. These layouts DO work with gvim, which is
  useful to me.

  When I try to enter characters with AltGr + vowel in the shell from
  xfce4-terminal (using the Maori layout), I get little diamonds with
  questions marks. In vim, I get various strange effects, but no vowels
  with macrons.

  This is the 64-bit version of xfce4-terminal:
  $ file /usr/bin/xfce4-terminal
  /usr/bin/xfce4-terminal: ELF 64-bit LSB shared object, x86-64, version 1 
(SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped

  Ubuntu version and kernel version
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=11.10
  DISTRIB_CODENAME=oneiric
  DISTRIB_DESCRIPTION="Ubuntu 11.10"
  Linux compaq 3.0.0-15-generic #26-Ubuntu SMP Fri Jan 20 17:23:00 UTC 2012 
x86_64 x86_64 x86_64 GNU/Linux
  model name: AMD Athlon(tm) 64 Processor 3800+
  cpu MHz   : 1000.000

  $ apt-show-versions xfce4-terminal
  xfce4-terminal/oneiric uptodate 0.4.8-1

  I don't have a computer available to try the 32-bit version of xubuntu
  11.10, unfortunately.

  BTW my main goal is to enter Hawaiian text, which also uses macrons.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xfce4-terminal 0.4.8-1
  ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
  Uname: Linux 3.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Wed Feb  8 10:56:01 2012
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4-terminal
  UpgradeStatus: Upgraded to oneiric on 2011-12-09 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/929054/+subscriptions

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

[Touch-packages] [Bug 929054] Re: AltGr key doesn't work properly in xfce4-terminal and gnome-terminal with Maori layout, and Hawaiian is not supported

2020-10-22 Thread Launchpad Bug Tracker

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

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

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

Title:
  AltGr key doesn't work properly in xfce4-terminal and gnome-terminal
  with Maori layout, and Hawaiian is not supported

Status in console-setup package in Ubuntu:
  Confirmed
Status in vte package in Ubuntu:
  Confirmed

Bug description:
  I just installed xfce4-xkb-plugin in order to select various keyboard
  layout. I soon found out that the AltGr key isn't working properly in
  xfce4-terminal, gnome-terminal and pterm. I am running the 64-bit
  version of xubuntu 11.10 and 12.04 on my Compaq computer, and the
  32-bit version of 12.04 on a Shuttle computer.

  .
  Updated 2012-04-03:
  This also affects 32-bit versions of Ubuntu and Xubuntu 11.10 and 12.04 
beta-2. It also affects the current Linux Mint. ALSO, note that other layouts 
with AltGr now work properly when Maori is not in the list. Also I have added 
lack of Hawaiian support to this bug. I am now updated to the Beta-2 version of 
xubuntu on the Compaq 12.04 system, and Ubuntu 12.04 beta-2 on the shuttle.
  .

  For example, select the Maori keyboard layout. This layout enters
  vowels with macrons like āēīōūĀĒĪŌŪ when the AltGr key is held on.
  (This does work in Firefox, which I'm using to enter this report, and
  also in xterm, but also fails in pterm. It does work in AbiWord).
  Various other layouts use AltGr, for example the US alt-intl layout
  uses AltGr plus the minus key as a dead key for entering vowels with
  macrons - those do not work under xfce4-terminal and pterm, but do
  work in various other apps. These layouts DO work with gvim, which is
  useful to me.

  When I try to enter characters with AltGr + vowel in the shell from
  xfce4-terminal (using the Maori layout), I get little diamonds with
  questions marks. In vim, I get various strange effects, but no vowels
  with macrons.

  This is the 64-bit version of xfce4-terminal:
  $ file /usr/bin/xfce4-terminal
  /usr/bin/xfce4-terminal: ELF 64-bit LSB shared object, x86-64, version 1 
(SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped

  Ubuntu version and kernel version
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=11.10
  DISTRIB_CODENAME=oneiric
  DISTRIB_DESCRIPTION="Ubuntu 11.10"
  Linux compaq 3.0.0-15-generic #26-Ubuntu SMP Fri Jan 20 17:23:00 UTC 2012 
x86_64 x86_64 x86_64 GNU/Linux
  model name: AMD Athlon(tm) 64 Processor 3800+
  cpu MHz   : 1000.000

  $ apt-show-versions xfce4-terminal
  xfce4-terminal/oneiric uptodate 0.4.8-1

  I don't have a computer available to try the 32-bit version of xubuntu
  11.10, unfortunately.

  BTW my main goal is to enter Hawaiian text, which also uses macrons.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xfce4-terminal 0.4.8-1
  ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
  Uname: Linux 3.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Wed Feb  8 10:56:01 2012
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4-terminal
  UpgradeStatus: Upgraded to oneiric on 2011-12-09 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/929054/+subscriptions

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

[Touch-packages] [Bug 929054] Re: AltGr key doesn't work properly in xfce4-terminal and gnome-terminal with Maori layout, and Hawaiian is not supported

2020-10-22 Thread Kendon Bell

I am potentially facing this bug. When I type Alt-a, expecting a with a
macron, I find that the system executes select all, just like Ctrl-a
would.

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

Title:
  AltGr key doesn't work properly in xfce4-terminal and gnome-terminal
  with Maori layout, and Hawaiian is not supported

Status in console-setup package in Ubuntu:
  Confirmed
Status in vte package in Ubuntu:
  Confirmed

Bug description:
  I just installed xfce4-xkb-plugin in order to select various keyboard
  layout. I soon found out that the AltGr key isn't working properly in
  xfce4-terminal, gnome-terminal and pterm. I am running the 64-bit
  version of xubuntu 11.10 and 12.04 on my Compaq computer, and the
  32-bit version of 12.04 on a Shuttle computer.

  .
  Updated 2012-04-03:
  This also affects 32-bit versions of Ubuntu and Xubuntu 11.10 and 12.04 
beta-2. It also affects the current Linux Mint. ALSO, note that other layouts 
with AltGr now work properly when Maori is not in the list. Also I have added 
lack of Hawaiian support to this bug. I am now updated to the Beta-2 version of 
xubuntu on the Compaq 12.04 system, and Ubuntu 12.04 beta-2 on the shuttle.
  .

  For example, select the Maori keyboard layout. This layout enters
  vowels with macrons like āēīōūĀĒĪŌŪ when the AltGr key is held on.
  (This does work in Firefox, which I'm using to enter this report, and
  also in xterm, but also fails in pterm. It does work in AbiWord).
  Various other layouts use AltGr, for example the US alt-intl layout
  uses AltGr plus the minus key as a dead key for entering vowels with
  macrons - those do not work under xfce4-terminal and pterm, but do
  work in various other apps. These layouts DO work with gvim, which is
  useful to me.

  When I try to enter characters with AltGr + vowel in the shell from
  xfce4-terminal (using the Maori layout), I get little diamonds with
  questions marks. In vim, I get various strange effects, but no vowels
  with macrons.

  This is the 64-bit version of xfce4-terminal:
  $ file /usr/bin/xfce4-terminal
  /usr/bin/xfce4-terminal: ELF 64-bit LSB shared object, x86-64, version 1 
(SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped

  Ubuntu version and kernel version
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=11.10
  DISTRIB_CODENAME=oneiric
  DISTRIB_DESCRIPTION="Ubuntu 11.10"
  Linux compaq 3.0.0-15-generic #26-Ubuntu SMP Fri Jan 20 17:23:00 UTC 2012 
x86_64 x86_64 x86_64 GNU/Linux
  model name: AMD Athlon(tm) 64 Processor 3800+
  cpu MHz   : 1000.000

  $ apt-show-versions xfce4-terminal
  xfce4-terminal/oneiric uptodate 0.4.8-1

  I don't have a computer available to try the 32-bit version of xubuntu
  11.10, unfortunately.

  BTW my main goal is to enter Hawaiian text, which also uses macrons.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xfce4-terminal 0.4.8-1
  ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
  Uname: Linux 3.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Wed Feb  8 10:56:01 2012
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4-terminal
  UpgradeStatus: Upgraded to oneiric on 2011-12-09 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/929054/+subscriptions

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

[Touch-packages] [Bug 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties

2020-10-22 Thread Michael Nazzareno Trimarchi

dbus getAll let you to download information of any interface. Each
interface has a reference number inside the wpa_supplicant. In my laptop
my wifi is interface 1. In order to ready wifi interface information I
can use dbus as shown in this example:

sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1
/fi/w1/wpa_supplicant1/Interfaces/1
org.freedesktop.DBus.Properties.GetAll
string:fi.w1.wpa_supplicant1.Interface

The result of the command give you the an answer like:

sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1 
/fi/w1/wpa_supplicant1/Interfaces/1 org.freedesktop.DBus.Properties.GetAll 
string:fi.w1.wpa_supplicant1.Interface
[sudo] password for michael: 
method return time=1603398113.528196 sender=:1.4 -> destination=:1.267 
serial=476 reply_serial=2
   array [
  dict entry(
 string "Capabilities"
 variant array [
   dict entry(
  string "Pairwise"
  variant  array [
string "ccmp"
string "tkip"
 ]
   )
   dict entry(
  string "Group"
  variant  array [
string "ccmp"
string "tkip"
string "wep104"
string "wep40"
 ]
   )
   dict entry(
  string "GroupMgmt"
  variant  array [
string "aes-128-cmac"
 ]
   )
   dict entry(
  string "KeyMgmt"
  variant  array [
string "none"
string "ieee8021x"
string "wpa-eap"
string "wpa-ft-eap"
string "wpa-eap-sha256"
string "wpa-psk"
string "wpa-ft-psk"
string "wpa-psk-sha256"
string "wps"
 ]
...

If one of the value can not reported the entire request just plain fail.
This is not happen on the same version without any addition patch. In
the debian package was added a patch to report the Stations attribue
that is a part of this answer and the fact that this is only valid on ap
mode does not let reply at all of this message. Now in connman for
example this getAll is used to get out the interface information as you
can find in this snipped code:


int supplicant_dbus_property_get_all(const char *path, const char *interface,
supplicant_dbus_property_function function,
void *user_data, gpointer caller)
{
struct property_call_data *property_call = NULL;
DBusMessage *message;
DBusPendingCall *call;

if (!connection)
return -EINVAL;

if (!path || !interface)
return -EINVAL;

property_call = g_try_new0(struct property_call_data, 1);
if (!property_call)
return -ENOMEM;

message = dbus_message_new_method_call(SUPPLICANT_SERVICE, path,
DBUS_INTERFACE_PROPERTIES, "GetAll");
if (!message) {
g_free(property_call);
return -ENOMEM;
}
...


static void interface_added(DBusMessageIter *iter, void *user_data)
{
...
   if (!properties_appended) {
supplicant_dbus_property_get_all(path,
SUPPLICANT_INTERFACE 
".Interface", << this call fail
interface_property, interface,
interface);
return;
}

...


This break all the other call try to access the Interface object in dbus 
dictionary

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

Title:
  Broken dbus GetAll message to wpa supplicant interface properties

Status in wpa package in Ubuntu:
  New

Bug description:
  dbus-send is able to read the properties of interface using GetAll. Those 
information include interface name, status, encryption method, etc. 
  The regression was introduced when someone try to have the Station attribute 
supported

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

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

[Touch-packages] [Bug 1900068] Re: Upgrade to zeitgeist-1.0.3

2020-10-22 Thread Sebastien Bacher

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

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

Title:
  Upgrade to zeitgeist-1.0.3

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

Bug description:
  Please do upgrade zeitgeist from current 1.0.2 to 1.0.3.

  It is required for GNOME Activity Journal to work. GNOME Activity Journal has
  been ported to GTK3. It will be available in GNOME repos shortly.

  For more details:

  https://discourse.gnome.org/t/zeitgeist-gnome-activity-
  journal-1-0/4521

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

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

[Touch-packages] [Bug 1746866] Re: adaptive thresholding - boxfilter

2020-10-22 Thread Sebastien Bacher

Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, I am closing it because the bug has been fixed
in the latest development version of Ubuntu.

This is a significant bug in Ubuntu. If you need a fix for the bug in
previous versions of Ubuntu, please perform as much as possible of the
SRU Procedure [1] to bring the need to a developer's attention.

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

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

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

** Tags removed: upgrade-software-version
** Tags added: upgrade-bionic-version

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

Title:
  adaptive thresholding - boxfilter

Status in opencv package in Ubuntu:
  Fix Released

Bug description:
  Adaptive thresholding tests with opencv 3.2 in bionic yielded a
  different resulting binary region (1 pixel "off") compared to the
  result with trusty and opencv 2.4.9.1. The bug seems to be in
  (boxfilter, in modules/imgproc/src/smooth.cpp) and is already fixed in
  opvencv 3.3 (actually the commit 11c2ffaf1c4eef3508dafc2bf fixed it).
  Any chance to update bionic to 3.3?

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

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

[Touch-packages] [Bug 120375] Re: cannot boot raid1 with only one disk

2020-10-22 Thread Guilherme G. Piccoli

This is a very old LP bug, but for completeness it worth mentioning here
that recently some patches were merged on initramfs-tools and
cryptsetup, that allow a good experience booting with LUKS-encrypted
rootfs on top of a degraded RAID1 array; for details, please check:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1879980

Cheers,


Guilherme

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

Title:
  cannot boot raid1 with only one disk

Status in initramfs-tools:
  Fix Released
Status in grub package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in mdadm package in Ubuntu:
  Fix Released
Status in grub source package in Hardy:
  Fix Released
Status in initramfs-tools source package in Hardy:
  Fix Released
Status in mdadm source package in Hardy:
  Fix Released

Bug description:
  The impact of the bug on users: Systems with root on a RAID array will
  not be able to boot if the array is degraded. Usrs affected by this
  will encounter an unusable system after a reboot (say, a kernel
  upgrade).

  Justification for backporting the fix to the stable release: Hardy is
  a LTS edition. It is expected that people will continue to use this
  version and not upgrade to Intrepid. People who have upgrade from
  Dapper LTS to Hardy LTS are affected too.

  TEST CASE
  Build a clean system with root on RAID, with Ubuntu 8.04 LTS. Degrade the 
root array. Reboot and shiver.

  A discussion of the regression potential of the patch and how users could get 
inadvertently effected. 
  - the only users that could be affected, as fas as  know, are the ones that 
already made a workaround and altered their system files accordingly.

  
  Binary package hint: mdadm

  if i unplug one hd from raid1 i cannot successfully boot because raid
  starts only if all disks are available through

  : "${MD_DEGRADED_ARGS:= --no-degraded}" in /usr/share/initramfs-
  tools/scripts/local-top/mdadm

  my workaround is:

  /etc/initramfs-tools/hooks/startdegradedraid

  #!/bin/sh
  #
  # Copyright  2006 Martin F. Krafft 
  # based on the scripts in the initramfs-tools package.
  # released under the terms of the Artistic Licence.
  #
  # $Id: hook 281 2006-12-08 08:14:44Z madduck $
  #

  set -eu

  PREREQ="udev"

  prereqs()
  {
  echo "$PREREQ"
  }

  case ${1:-} in
prereqs)
  prereqs
  exit 0
  ;;
  esac

  MDADM=$(command -v mdadm 2>/dev/null) || :
  [ -x $MDADM ] || exit 0

  DESTCONFIG=$DESTDIR/conf/md.conf

  echo "MD_DEGRADED_ARGS=' '" >> $DESTCONFIG

  exit 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/120375/+subscriptions

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

[Touch-packages] [Bug 1464876] Re: Please update Game_Music_Emu plugin to 0.6.0

2020-10-22 Thread Sebastien Bacher

** Tags removed: upgrade-software-version

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

Title:
  Please update Game_Music_Emu plugin to 0.6.0

Status in audacious-plugins package in Ubuntu:
  New
Status in game-music-emu package in Ubuntu:
  Fix Released

Bug description:
  Please, can you update the Game_Music_Emu plugin to 0.6.0 version from
  0.5.2?

  That new version supports SegaCD PCM Chip from Sega's console.

  The plugin can be downloaded from here:
  https://code.google.com/p/game-music-emu/downloads/list
  or
  https://bitbucket.org/mpyne/game-music-emu/downloads

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audacious-plugins/+bug/1464876/+subscriptions

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

[Touch-packages] [Bug 1639737] Re: New Version of JasPer JPEG2000 Software Available

2020-10-22 Thread Sebastien Bacher

closing since the package is removed from Ubuntu

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

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

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

Title:
  New Version of JasPer JPEG2000 Software Available

Status in jasper package in Ubuntu:
  Invalid

Bug description:
  I hope that this is not inappropriate to submit as a bug report.

  As best I can tell, it seems that Ubuntu Zesty (as well as other
  versions) is using JasPer version 1.900.1.  This version of the JasPer
  software is very old and numerous bug fixes have been made since the
  time that this old version was released. It is possible to adopt a
  newer version of JasPer the from upstream source?

  The most recent version of JasPer is 1.900.22.  See the JasPer web site for 
details:
  http://www.ece.uvic.ca/~mdadams/jasper

  A link to the 1.900.22 release tarball is as follows:
  http://www.ece.uvic.ca/~frodo/jasper/software/jasper-1.900.22.tar.gz

  Or alternatively you could just pull code from the master branch of the 
official JasPer Git repository on GitHub:
  https://github.com/mdadams/jasper

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

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

[Touch-packages] [Bug 1501219] Re: in ubuntu 14.4.03, package python3.4 version "3.4.3-1ubuntu1~14.04.1" doesn't have the executable pyvenv-3.4

2020-10-22 Thread Sebastien Bacher

closing since the package is removed from Ubuntu

** Changed in: python3.4 (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: python3.4 (Ubuntu)
   Status: New => Invalid

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

Title:
  in ubuntu 14.4.03, package python3.4 version "3.4.3-1ubuntu1~14.04.1"
  doesn't have the executable pyvenv-3.4

Status in python3.4 package in Ubuntu:
  Invalid

Bug description:
  On the python changelog, it doesn't say anything that this executable
  should be missing, on the  contrary.

  The executable is present in the package version "3.4.0-2ubuntu1.1".

  Worth mentioning is that I imported a vagrant virtual machine image from here:
  
https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box

  Previously when I had done that, the version "3.4.0-2ubuntu1.1" was
  installed, but now, the version "3.4.3-1ubuntu1~14.04.1" came up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1501219/+subscriptions

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

[Touch-packages] [Bug 1901020] Re: new upstream release 2020d

2020-10-22 Thread Brian Murray

** Also affects: tzdata (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

** Also affects: tzdata (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: tzdata (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  new upstream release 2020d

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Precise:
  New
Status in tzdata source package in Trusty:
  New
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  New
Status in tzdata source package in Groovy:
  Fix Committed

Bug description:
  New upstream version, affecting the following future timestamps:
- Fiji starts DST later than usual, on 2020-12-20.
- Palestine ends DST earlier than predicted, on 2020-10-24.

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

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

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

[Touch-packages] [Bug 1316634] Re: Does not automatically reconnect to hidden WiFi network

2020-10-22 Thread dr.falken

I have never had this problem on the same laptop (asus f550l) with every
LTS from 14.04 but it appears with 20.04

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

Title:
  Does not automatically reconnect to hidden WiFi network

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Running Lubuntu 14.04 32-bit on a Lenovo 3000 C200 laptop with an
  integrated Broadcom network adapter, I installed
  firmware-b43-installer and then successfully connected to my hidden
  (SSID not broadcast) WiFi net.

  But I see that it will not automatically reconnect.  I don't have to
  re-enter the password, but I do have to click the nm-applet indicator,
  choose 'Connect to Hidden Wi-Fi Network' and then choose my already-
  defined connection, which indeed has been saved but not used to
  automatically reconnect.

  If I edit the connection, I see that on the General tab it is already
  set to 'Automatically connect to this network when it is available.'

  The only way I can get automatic reconnection is to enable SSID
  Broadcast.

  And a similar effect: If I am connected to the network while SSID
  Broadcast is in effect and then disable SSID Broadcast, network-
  manager immediately loses the connection.

  Someone suggested that network-manager would find the hidden network
  if I just waited, but after waiting 15 minutes it had still not
  connected.

  Dual-booting this same laptop with Windows Vista, I see that Windows
  knows how to automatically reconnect to the hidden net.

  I see that https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/295796 describes similar behavior, but that was reported
  back in 2008 and I'm imagining that there should be a separate report
  for the new release.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDesktop: LXDE
  Date: Tue May  6 10:24:32 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-25 (10 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.118  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 1ac7ba941-660f-40c5-9b1f-4d24accc6225   
802-3-ethernet1399385892   Tue 06 May 2014 10:18:12 AM EDTyes   
no /org/freedesktop/NetworkManager/Settings/1
   PRP   d25473c0-98d8-4d93-ab37-3dd070bbd34b   
802-11-wireless   1399386192   Tue 06 May 2014 10:23:12 AM EDTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Touch-packages] [Bug 1879085] Re: update-initramfs can't handle encrypted swap-files

2020-10-22 Thread Steve Langasek

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

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

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

Title:
  update-initramfs can't handle encrypted swap-files

Status in cryptsetup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  OS: Ubuntu 20.04 Mate

  I have an encrypted swap-file, which is working fine:

  # grep cryptswap /etc/fstab
  /dev/mapper/cryptswap none swap  defaults 0 0
  # grep cryptswap /etc/crypttab
  cryptswap /cryptswapfile /dev/urandom swap,cipher=aes-xts-plain64,size=256

  But everytime I update the kernel and update-initramfs is executed, an
  error occurs:

  cryptsetup: ERROR: Couldn't resolve device /cryptswapfile
  cryptsetup: WARNING: Resume target cryptswap uses a key file

  And after the next reboot, the system can't load the cryptswap while
  booting and hangs for several minutes.

  Workaround: Boot into rescue mode and wait until the loading of the
  cryptswapfile timeouts. Go to a shell and comment the lines in the
  fstab and crypttab. Execute # swapoff -a && update-initramfs -u. Now
  uncomment the lines in fstab and crypttab again and reboot. Your
  system should boot fine and you should have an encrypted swapfile.

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

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

[Touch-packages] [Bug 1901020] Re: new upstream release 2020d

2020-10-22 Thread Steve Langasek

Hello Brian, or anyone else affected,

Accepted tzdata into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/tzdata/2020d-1ubuntu1
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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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: tzdata (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-groovy

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

Title:
  new upstream release 2020d

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Groovy:
  Fix Committed

Bug description:
  New upstream version, affecting the following future timestamps:
- Fiji starts DST later than usual, on 2020-12-20.
- Palestine ends DST earlier than predicted, on 2020-10-24.

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

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

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

[Touch-packages] [Bug 1876382] Re: Ubuntu 20.04 Fractional scaling

2020-10-22 Thread Launchpad Bug Tracker

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

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

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

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

Title:
  Ubuntu 20.04 Fractional scaling

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have 2 screens

  1 x 1440 x 2560 (2k)
  1 x 3840 x 2160 (4k)

  I just upgraded to ubuntu 20.04 (From 19.10). I have tried to use the
  fractional scaling option and it seem its not working. When setting
  the fractional scaling on the 4k monitor (to 125% or 150%) it glitches
  out (Goes black) and when it comes back it has set the scaling to 200%
  and changed the screen positions to be on top of one another, Seems
  there is no way for me to set the correct scaling.

  Just for information purposes I am currently using the nvidia-435
  driver (I have also tried with the nvidia-440-driver) to no avail

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  1 22:00:42 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.4.0-28-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6183]
  InstallationDate: Installed on 2020-01-15 (106 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:0892 Logitech, Inc. OrbiCam
   Bus 001 Device 003: ID 1b1c:1b20 Corsair Corsair STRAFE RGB Gaming Keyboard
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. Z370P D3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=bd37a70e-316f-4716-a253-481f8f785d18 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370P D3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/13/2019:svnGigabyteTechnologyCo.,Ltd.:pnZ370PD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370PD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370P D3
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1901073] [NEW] Ubuntu 19.10 x86_64 robotic audio sound when using hardware acceleration

2020-10-22 Thread макс

Public bug reported:

In certain  application I am expiriencing robotic soud. Latest chrome
works just fine, but discord with hardware acceleration and telegram
sound robotic.

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

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

Title:
  Ubuntu 19.10 x86_64 robotic audio sound when using hardware
  acceleration

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  In certain  application I am expiriencing robotic soud. Latest chrome
  works just fine, but discord with hardware acceleration and telegram
  sound robotic.

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

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

[Touch-packages] [Bug 1899621] Autopkgtest regression report (zlib/1:1.2.11.dfsg-2ubuntu1.2)

2020-10-22 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted zlib (1:1.2.11.dfsg-2ubuntu1.2) 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)
libreoffice/1:6.4.6-0ubuntu0.20.04.1 (arm64)
dub/1.19.0-1build2 (s390x, armhf, arm64, amd64)
burp/2.2.18-2 (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#zlib

[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 zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1899621

Title:
  [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on
  z15

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Focal:
  Fix Committed
Status in zlib source package in Groovy:
  Fix Released

Bug description:
  Description:   zlib: inflateSyncPoint() returns an incorrect result on z15
  Symptom:   Certain rsync builds fail with "error in rsync protocol data
     stream" on z15.
  Problem:   inflateSyncPoint() does not take into account the hardware
     compression state and returns an incorrect result.
  Solution:  Make inflateSyncPoint() fail if the hardware compression is on.
     The hardware does not provide enough information in order to
     implement this function.

  [Impact]

   * Certain rsync builds fail with "error in rsync protocol data
  stream" on z15.

   * On ubuntu, rsync normally uses zstd or lz4. But when rsync is
  forced to use non-default zlib compression (-z flag) it uses
  inflateSyncPoint() API. This can also happen when rsync on the the
  other end doesn't support zstd & lz4.

   * inflateSyncPoint() does not take into account the hardware
  compression state and returns an incorrect result.

   * Make inflateSyncPoint() fail if the hardware compression is on. The
  hardware does not provide enough information in order to implement
  this function.

   * Above makes rsync to succeed, when zlib uses hardware compression.

  [Test Case]

  Reproduction:  z15 only: printf 1 >1 && rsync -z 1 2

  [Regression Potential]

   * inflateSyncPoint API is rarely used. Scanning codesearch, there is
  a lot of false positives due to embedded copies of zlib in all the
  things. I do see that both rsync and backuppc-rsync use it. It used
  during a safety check to ensure that algorithm is not at a sync point
  (or that cannot be determined). Nonetheless, returning error is a
  safer implementation for this API call.

  [Other Info]

   * This is a regression introduced by adding & enabling zlib hw
  acceleration by default on z15; and discovering using rsync that one
  API is implemented incorrectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1899621/+subscriptions

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

[Touch-packages] [Bug 1880250] Re: Ctrl-C message displayed without any actual disk check

2020-10-22 Thread Dimitri John Ledkov

installed focal daily with LUKS and plymouth 0.9.4git20200323-0ubuntu6.1
; i could see that on boot the ctrl+c message is there after unlock,
briefly, and then cleared.

Then i downgraded to 0.9.4git20200323-0ubuntu6 and instead of brief
ctrc+c message, it lingers for a lot longer until gdm3 starts.

Thus the plymouth portion of the bug is verified.

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

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

Title:
  Ctrl-C message displayed without any actual disk check

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

Bug description:
  [Impact]

   * fsck messages is shown by plymouth, despite all fscks already
  completed.

  [Test Case]

   * Install Ubuntu Desktop with full disk encryption

   * Observe that fsck messages (press ctrl+c) is shown, and remains
  there on screen for a little while as plymouth transitions to gdm

   * After installing the update, observe that when fsck completes the
  messages are cleared and the transition to gdm is done without
  fsck/ctrl+c message present.

   * After this change lands in -updates, and daily desktop images are
  built with this, double check that casper-md5sum transition is also
  smooth.

  
  [Regression Potential] 

   * plymouth spinner theme is adjusted to clear the footer, at the end
  of fsck, even if systemd-fsckd didn't do that. At the moment there are
  two consumers of the fsck apis systemd-fsckd & casper-md5sum used on
  installed systems and live-isos respectively. If something else pushes
  messages to the footer, they might get cleared at the end of fsck.

  [Other Info]
   
   * Original bug report

  It seems the transition to bgrt lost something with Ubuntu's disk
  check details. The only thing I see on my screen during a long disk
  check is the "press Ctrl-C to stop all in progress disk checks" with
  no progress.

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

-- 
Mailing list: https://launchpad.net/~touch-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

2020-10-22 Thread Executenor

@Javier Ah ok that makes sense, i hope it is really fixed with ubuntu
20.10 then it could be used with the a new hwe for ubuntu 20.04.

-- 
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 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)

2020-10-22 Thread Brian Murray

** Changed in: ubuntu-release-notes
   Status: New => Invalid

-- 
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 1888726] Re: systemd-udevd regression: some renamed network interfaces stuck in "pending" state

2020-10-22 Thread Lukas Märdian

** Changed in: netplan.io (Ubuntu)
   Status: Confirmed => In Progress

-- 
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:
  In Progress
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" - Release

[Touch-packages] [Bug 1888726] Re: systemd-udevd regression: some renamed network interfaces stuck in "pending" state

2020-10-22 Thread Lukas Märdian

I am able to reproduce the problem on Groovy (netplan.io
0.100-0ubuntu5).

Using the "Type=!vlan" filter, which netplan already applies for some
bridge/bond scenarios, I was able to get the vlan20 interface from
'degraded / pending' into 'degraded / configured', state and systemd-
networkd-wait-online.service not timing out, but succeeding.

I'm working on an upstream solution here:
https://github.com/CanonicalLtd/netplan/pull/166

@Foster: would you be able to test if netplan.io from this PPA fixes the 
problem for you, too?
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4315

-- 
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:
  Confirmed
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:

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

2020-10-22 Thread Bill (franksmcb)

This is confirmed working correctly on Ubuntu MATE with 20201022 re-
spin.

-- 
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:
  New
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 1025388] Re: Internal mic stops working when plugging in headphones

2020-10-22 Thread O Gopal

For a fix that worked for me, see
https://askubuntu.com/questions/1218136/internal-microphone-doesnt-work-
when-using-headphones/1285982#1285982.

The fix:

 1. Run

  sudo apt install alsa-tools-gui

  hdajackretask

 2. Select the appropriate sound card up top in Select a codec.

 3. Then make the Black Mic (headphone jack) override Not connected.

 4. Lower right corner, select Install boot override.

 5. Then reboot and test.

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

Title:
  Internal mic stops working when plugging in headphones

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

Bug description:
  I am currently running Quantal and when I plug headphones into my
  headphone socket (which has an icon of a headset next to it, so I
  presume it can take some kind of headset), the internal mic on my
  laptop stops working. If I unplug the headphones the internal mic
  works as normal.

  I tried this with two different sets of headphones (one of which has a
  mic, and the other I think has a mic too).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: pulseaudio 1:2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
  Uname: Linux 3.5.0-4-generic i686
  ApportVersion: 2.3-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jono   1860 F pulseaudio
   /dev/snd/pcmC0D0c:   jono   1860 F...m pulseaudio
  Date: Mon Jul 16 11:01:32 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET56WW (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4239CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4239CTO
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)

2020-10-22 Thread fossfreedom

I can confirm that sound is no longer muted for the ISO and is not muted on
installation.

So thanks and congrats!

On Thu, 22 Oct 2020, 14:30 Launchpad Bug Tracker, <
1897...@bugs.launchpad.net> wrote:

> This bug was fixed in the package alsa-lib - 1.2.3.2-1ubuntu3
>
> ---
> alsa-lib (1.2.3.2-1ubuntu3) groovy; urgency=medium
>
>   * d/p/0001-ucm-add-a-check-for-the-empty-configuration.patch
>   - Fix the failure on init the HDA-Intel sound card, because there
> is no init mixer values in the ucm, the alsa-lib should return
> error and then let alsautils init this sound card in the legacy
> HDA way. (LP: #1897934)
>
>  -- Hui Wang   Thu, 22 Oct 2020 16:46:14 +0800
>
> ** Changed in: alsa-lib (Ubuntu Groovy)
>Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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:
>   New
> 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
>

-- 
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:
  New
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

[Touch-packages] [Bug 1025388] Re: Internal mic stops working when plugging in headphones

2020-10-22 Thread O Gopal

Same issue as #22 etc. Ubuntu 20.04. Lenovo X1 Carbon, 5th generation.
When I plug in earphones that have no microphone, the internal
microphone no longer works.

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

Title:
  Internal mic stops working when plugging in headphones

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

Bug description:
  I am currently running Quantal and when I plug headphones into my
  headphone socket (which has an icon of a headset next to it, so I
  presume it can take some kind of headset), the internal mic on my
  laptop stops working. If I unplug the headphones the internal mic
  works as normal.

  I tried this with two different sets of headphones (one of which has a
  mic, and the other I think has a mic too).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: pulseaudio 1:2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
  Uname: Linux 3.5.0-4-generic i686
  ApportVersion: 2.3-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jono   1860 F pulseaudio
   /dev/snd/pcmC0D0c:   jono   1860 F...m pulseaudio
  Date: Mon Jul 16 11:01:32 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET56WW (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4239CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4239CTO
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1901020] Re: new upstream release 2020d

2020-10-22 Thread Brian Murray

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

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

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

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

Title:
  new upstream release 2020d

Status in tzdata package in Ubuntu:
  In Progress

Bug description:
  New upstream version, affecting the following future timestamps:
- Fiji starts DST later than usual, on 2020-12-20.
- Palestine ends DST earlier than predicted, on 2020-10-24.

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

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

-- 
Mailing list: https://launchpad.net/~touch-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)

2020-10-22 Thread Launchpad Bug Tracker

This bug was fixed in the package alsa-lib - 1.2.3.2-1ubuntu3

---
alsa-lib (1.2.3.2-1ubuntu3) groovy; urgency=medium

  * d/p/0001-ucm-add-a-check-for-the-empty-configuration.patch
  - Fix the failure on init the HDA-Intel sound card, because there
is no init mixer values in the ucm, the alsa-lib should return
error and then let alsautils init this sound card in the legacy
HDA way. (LP: #1897934)

 -- Hui Wang   Thu, 22 Oct 2020 16:46:14 +0800

** Changed in: alsa-lib (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

-- 
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:
  New
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 1901026] [NEW] [GDB] No socket file connection support

2020-10-22 Thread Luis

Public bug reported:

GDB on Ubuntu 18.04 (GNU gdb (Ubuntu 8.1-0ubuntu3.2) 8.1.0.20180409-git)
does not support connecting to a remote target via a socket file.

This is the error we get:

(gdb) target remote /run/user/1000/at-spi2-QTZBS0/socket
/run/user/1000/at-spi2-QTZBS0/socket: No such device or address.

Commit c1168a2f66553cd4730931cf59e3be8378a1a03f enables this in GDB. It
would be nice to have it backported.

Here's the commit link: https://sourceware.org/git/?p=binutils-
gdb.git;a=commit;h=c1168a2f66553cd4730931cf59e3be8378a1a03f

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

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

Title:
  [GDB] No socket file connection support

Status in gdb package in Ubuntu:
  New

Bug description:
  GDB on Ubuntu 18.04 (GNU gdb (Ubuntu 8.1-0ubuntu3.2)
  8.1.0.20180409-git) does not support connecting to a remote target via
  a socket file.

  This is the error we get:

  (gdb) target remote /run/user/1000/at-spi2-QTZBS0/socket
  /run/user/1000/at-spi2-QTZBS0/socket: No such device or address.

  Commit c1168a2f66553cd4730931cf59e3be8378a1a03f enables this in GDB.
  It would be nice to have it backported.

  Here's the commit link: https://sourceware.org/git/?p=binutils-
  gdb.git;a=commit;h=c1168a2f66553cd4730931cf59e3be8378a1a03f

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

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

[Touch-packages] [Bug 1901020] [NEW] new upstream release 2020d

2020-10-22 Thread Brian Murray

Public bug reported:

New upstream version, affecting the following future timestamps:
  - Fiji starts DST later than usual, on 2020-12-20.
  - Palestine ends DST earlier than predicted, on 2020-10-24.

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

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

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

Title:
  new upstream release 2020d

Status in tzdata package in Ubuntu:
  New

Bug description:
  New upstream version, affecting the following future timestamps:
- Fiji starts DST later than usual, on 2020-12-20.
- Palestine ends DST earlier than predicted, on 2020-10-24.

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

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

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

[Touch-packages] [Bug 1901016] [NEW] APP GRID TOO LARGE

2020-10-22 Thread amamdispencer

Public bug reported:

When you click on the app button, the icons in the app grid shown is way
too large.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
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
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 22 13:11:04 2020
DistUpgraded: Fresh install
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 
[VGA controller])
   Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
InstallationDate: Installed on 2020-10-03 (18 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcEnviron:
 LANGUAGE=en_NG:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_NG
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=9f6d2f48-a8cd-464f-8ea4-11fec7ad9369 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.13.0-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-focal
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-focal
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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 groovy ubuntu

** Attachment added: "Screenshot from 2020-10-22 13-05-35.png"
   
https://bugs.launchpad.net/bugs/1901016/+attachment/5425496/+files/Screenshot%20from%202020-10-22%2013-05-35.png

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

Title:
  APP GRID TOO LARGE

Status in xorg package in Ubuntu:
  New

Bug description:
  When you click on the app button, the icons in the app grid shown is
  way too large.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 22 13:11:04 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2020-10-03 (18 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   LANGUAGE=en_NG:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NG
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=9f6d2f48-a8cd-464f-8ea4-11fec7ad9369 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-focal
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-focal
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati

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

2020-10-22 Thread Iain Lane

ah I see, OK - I will upload, thanks!

can you update the test case to say that this version of alsa-utils is
needed please? maybe provide a PPA link for people to install it with,
until that is accepted into focal?

** Changed in: alsa-lib (Ubuntu Focal)
   Status: Incomplete => Fix Committed

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

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

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

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 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)

2020-10-22 Thread Hui Wang

@Iain,

For focal, after we merge this SRU:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1899745, we
will have this bug too. But for focal, the #1899745 will not be in the
iso, so users will not notice this problem. If we merge #1899745 to
20.04.2 iso, users will meet this bug.

So for focal, this fix is not very urgent, even we merge the #1899745,
it will not introduce this issue immediately.

-- 
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:
  New
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Focal:
  Incomplete
Status in alsa-lib source package in Groovy:
  Fix Committed

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 1901000] Re: dmesg need permission after kernel 5.8

2020-10-22 Thread Alex Tu

the followed attached message from  `apport-collect` shows it did ask
permission, but still shows error message in launchpad description.

$ id
uid=1001(ubuntu) gid=1001(ubuntu) groups=1001(ubuntu),27(sudo)

$ apport-collect -p linux-image-5.8.0-25-generic 1901000
 AUTHENTICATING FOR org.freedesktop.policykit.exec ===
Authentication is needed to run `/usr/bin/dmesg' as the super user
Multiple identities can be used for authentication:
 1.  u,,, (u)
 2.  ,,, (ubuntu)
Choose identity to authenticate as (1-2): 2
Password: 
 AUTHENTICATION FAILED ===
 AUTHENTICATING FOR org.freedesktop.policykit.exec ===
Authentication is needed to run `/usr/share/apport/dump_acpi_tables.py' as the 
super user
Multiple identities can be used for authentication:
 1.  u,,, (u)
 2.  ,,, (ubuntu)
Choose identity to authenticate as (1-2): 2
Password: 
 AUTHENTICATION FAILED ===
No journal files were opened due to insufficient permissions. 

Unexcepted message in bug description:
```
CurrentDmesg:
 Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
 Error executing command as another user: Not authorized
```

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

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
   Status: New => Confirmed

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

Title:
  dmesg need permission after kernel 5.8

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

Bug description:
  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  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
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  MachineType: Dell Inc. Precision 5550
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0203K4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 7654321
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.

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

2020-10-22 Thread Alex Tu

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1901000/+attachment/5425473/+files/ProcEnviron.txt

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

Title:
  dmesg need permission after kernel 5.8

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

Bug description:
  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  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
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  MachineType: Dell Inc. Precision 5550
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0203K4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 7654321
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1901000] IwConfig.txt

2020-10-22 Thread Alex Tu

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1901000/+attachment/5425464/+files/IwConfig.txt

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

Title:
  dmesg need permission after kernel 5.8

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

Bug description:
  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  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
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  MachineType: Dell Inc. Precision 5550
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0203K4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 7654321
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.sys.vendor: Dell Inc.

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

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

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

2020-10-22 Thread Alex Tu

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1901000/+attachment/5425476/+files/PulseList.txt

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

Title:
  dmesg need permission after kernel 5.8

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

Bug description:
  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  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
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  MachineType: Dell Inc. Precision 5550
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0203K4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 7654321
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1901000] RfKill.txt

2020-10-22 Thread Alex Tu

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1901000/+attachment/5425477/+files/RfKill.txt

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

Title:
  dmesg need permission after kernel 5.8

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

Bug description:
  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  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
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  MachineType: Dell Inc. Precision 5550
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0203K4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 7654321
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.sys.vendor: Dell Inc.

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

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

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

2020-10-22 Thread Alex Tu

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1901000/+attachment/5425467/+files/Lsusb.txt

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

Title:
  dmesg need permission after kernel 5.8

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

Bug description:
  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  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
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  MachineType: Dell Inc. Precision 5550
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0203K4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 7654321
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.sys.vendor: Dell Inc.

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

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

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

2020-10-22 Thread Alex Tu

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1901000/+attachment/5425478/+files/UdevDb.txt

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

Title:
  dmesg need permission after kernel 5.8

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

Bug description:
  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  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
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  MachineType: Dell Inc. Precision 5550
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0203K4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 7654321
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.sys.vendor: Dell Inc.

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

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

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

2020-10-22 Thread Alex Tu

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1901000/+attachment/5425466/+files/Lspci-vt.txt

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

Title:
  dmesg need permission after kernel 5.8

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

Bug description:
  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  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
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  MachineType: Dell Inc. Precision 5550
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0203K4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 7654321
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.sys.vendor: Dell Inc.

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

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

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

2020-10-22 Thread Alex Tu

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1901000/+attachment/5425468/+files/Lsusb-t.txt

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

Title:
  dmesg need permission after kernel 5.8

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

Bug description:
  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  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
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  MachineType: Dell Inc. Precision 5550
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0203K4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 7654321
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.sys.vendor: Dell Inc.

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

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

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

2020-10-22 Thread Alex Tu

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1901000/+attachment/5425474/+files/ProcInterrupts.txt

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

Title:
  dmesg need permission after kernel 5.8

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

Bug description:
  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  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
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  MachineType: Dell Inc. Precision 5550
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0203K4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 7654321
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.sys.vendor: Dell Inc.

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

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

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

2020-10-22 Thread Alex Tu

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1901000/+attachment/5425465/+files/Lspci.txt

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

Title:
  dmesg need permission after kernel 5.8

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

Bug description:
  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  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
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  MachineType: Dell Inc. Precision 5550
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0203K4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 7654321
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.sys.vendor: Dell Inc.

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

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

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

2020-10-22 Thread Alex Tu

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1901000/+attachment/5425463/+files/Dependencies.txt

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

Title:
  dmesg need permission after kernel 5.8

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

Bug description:
  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  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
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  MachineType: Dell Inc. Precision 5550
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0203K4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 7654321
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1901000] PaInfo.txt

2020-10-22 Thread Alex Tu

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1901000/+attachment/5425470/+files/PaInfo.txt

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

Title:
  dmesg need permission after kernel 5.8

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

Bug description:
  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  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
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  MachineType: Dell Inc. Precision 5550
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0203K4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 7654321
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1901000] ProcCpuinfo.txt

2020-10-22 Thread Alex Tu

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1901000/+attachment/5425471/+files/ProcCpuinfo.txt

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

Title:
  dmesg need permission after kernel 5.8

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

Bug description:
  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  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
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  MachineType: Dell Inc. Precision 5550
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0203K4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 7654321
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1901000] AlsaInfo.txt

2020-10-22 Thread Alex Tu

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1901000/+attachment/5425461/+files/AlsaInfo.txt

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

Title:
  dmesg need permission after kernel 5.8

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

Bug description:
  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  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
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  MachineType: Dell Inc. Precision 5550
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0203K4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 7654321
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.sys.vendor: Dell Inc.

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

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

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

2020-10-22 Thread Alex Tu

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1901000/+attachment/5425469/+files/Lsusb-v.txt

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

Title:
  dmesg need permission after kernel 5.8

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

Bug description:
  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  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
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  MachineType: Dell Inc. Precision 5550
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0203K4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 7654321
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.sys.vendor: Dell Inc.

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

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

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

2020-10-22 Thread Alex Tu

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1901000/+attachment/5425462/+files/CRDA.txt

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

Title:
  dmesg need permission after kernel 5.8

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

Bug description:
  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  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
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  MachineType: Dell Inc. Precision 5550
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0203K4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 7654321
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.sys.vendor: Dell Inc.

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

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

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

2020-10-22 Thread Alex Tu

apport information

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

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

Title:
  dmesg need permission after kernel 5.8

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

Bug description:
  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  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
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  MachineType: Dell Inc. Precision 5550
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0203K4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 7654321
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.sys.vendor: Dell Inc.

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

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

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

2020-10-22 Thread Alex Tu

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1901000/+attachment/5425475/+files/ProcModules.txt

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

Title:
  dmesg need permission after kernel 5.8

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

Bug description:
  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  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
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  MachineType: Dell Inc. Precision 5550
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0203K4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 7654321
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1901000] [NEW] dmesg need permission after kernel 5.8

2020-10-22 Thread Alex Tu

Public bug reported:

apport used to collect dmesg well before kernel 5.8.
But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: apport 2.20.11-0ubuntu50
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
CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 +0800:2020-10-15 
18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
Date: Thu Oct 22 18:54:46 2020
InstallationDate: Installed on 2020-10-15 (7 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
CasperMD5CheckResult: skip
CurrentDmesg:
 Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
 Error executing command as another user: Not authorized
 
 This incident has been reported.
DistroRelease: Ubuntu 20.10
InstallationDate: Installed on 2020-10-15 (7 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
MachineType: Dell Inc. Precision 5550
Package: linux-image-5.8.0-25-generic 5.8.0-25.26
PackageArchitecture: amd64
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-25-generic N/A
 linux-backports-modules-5.8.0-25-generic  N/A
 linux-firmware1.190
Tags:  groovy
Uname: Linux 5.8.0-25-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: sudo
WifiSyslog:
 
_MarkForUpload: True
acpidump:
 Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with 
exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
 Error executing command as another user: Not authorized
 
 This incident has been reported.
dmi.bios.date: 06/01/2020
dmi.bios.release: 1.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.1
dmi.board.name: 0203K4
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: 7654321
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5550
dmi.product.sku: 097E
dmi.sys.vendor: Dell Inc.

** Affects: oem-priority
 Importance: Critical
 Status: Confirmed

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


** Tags: amd64 apport-bug apport-collected groovy

** Tags added: apport-collected

** Description changed:

  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  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
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu50
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDmesg:
+  Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
+  Error executing command as another user: Not authorized
+  
+  This incident has been reported.
+ DistroRelease: Ubuntu 20.10
+ InstallationDate: Installed on 2020-10-15 (7 days ago)
+ InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - B

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

2020-10-22 Thread Sebastien Bacher

(the upload got rejected since it was already uploaded by someone who
didn't bother updating the bug)

-- 
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:
  New
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Focal:
  Incomplete
Status in alsa-lib source package in Groovy:
  Fix Committed

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 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)

2020-10-22 Thread Iain Lane

I don't see the same problem on the Focal ISO - do we need to fix this
in Focal?

** Changed in: alsa-lib (Ubuntu Focal)
   Status: In Progress => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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:
  New
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Focal:
  Incomplete
Status in alsa-lib source package in Groovy:
  Fix Committed

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 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)

2020-10-22 Thread Sebastien Bacher

Thanks Hui, I've sponsored the fix to G, let's see how it goes there

** Changed in: alsa-lib (Ubuntu Groovy)
   Status: In Progress => Fix Committed

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

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

Status in Release Notes for Ubuntu:
  New
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Focal:
  In Progress
Status in alsa-lib source package in Groovy:
  Fix Committed

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 375763] Re: Printer won't print although Ubuntu says that job is completed, also driver won't update

2020-10-22 Thread Ginevra Buratti

@b-azazi-g I had the same problem and this fixed it

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

Title:
  Printer won't print although Ubuntu says that job is completed, also
  driver won't update

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  I have canon LBP3000 laser printer. I have downloaded both versions of driver 
from canon, version 1.6 and 1.8, and followed step by step instructions. I also 
checked all over the net for the solution, but found none.
  My printer is identified, and status is fine, just it wont print. This is in 
detail what happens, and the steps I followed.
  First I made sure that I have removed printer's spooler:

  /usr/sbin/lpadmin -x LBP5000

  
  Then, I installed these provided packages:

  # dpkg -i cndrvcups-common_1.80-1_i386.deb

  # dpkg -i cndrvcups-capt_1.80-1_i386.deb

  I checked for driver version by:

  # dpkg -l | grep cndrvcups

  and it was fine, 1.80

  
  Then I restarted cups and registered:
  /usr/sbin/lpadmin -p LBP3000 -m CNCUPSLBP3000CAPTK.ppd -v ccp:/var/ccpd/fifo0 
-E
  /usr/sbin/ccpdadmin -p LBP3000 -o /dev/usb/lp0

  And started daemon:

  # /etc/init.d/ccpd start

  
  In system/preferences/default printer my printer is set as default

  In system/administration/printing there is LBP3000 with green check

  I click on properties and I noticed that for driver it says 1.5
  version. That was odd, but I tried nonetheless. I did print page, it
  said completed, but no printing occurred. I then tried to changeMake
  and Model by clicking on the button to the right and chosing the right
  ppt file, since from select from database was only that 1.5 version
  driver that probably came with Ubuntu. I am using 9.04, so its a bit
  odd that it has driver so old.

  In previous steps you noticed that in fifo0 I registered my ppt, and
  fifo0 is chosen, but still that 1.5 version, and printer wont print
  anything although status says everything is fine and printing jobs
  compleated.

  It took me hours and hours working on this, but still no solution.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/bin/yelp
  NonfreeKernelModules: fglrx
  Package: yelp 2.25.1-0ubuntu5
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: yelp
  Uname: Linux 2.6.28-11-generic i686

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

-- 
Mailing list: https://launchpad.net/~touch-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)

2020-10-22 Thread Hui Wang

The debdiff for focal, let us wait for groovy to be tested and pass.


** Description changed:

- On boot into the live session - or on first install the sound level is
+ [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

-- 
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:
  New
Status in alsa-lib package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  In Progress
Status in alsa-lib source package in Groovy:
  In Progress

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   50

[Touch-packages] [Bug 1848626] Re: When seeking in VLC playing most videos, sound is choppy for 9s after seek.

2020-10-22 Thread Launchpad Bug Tracker

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

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

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

Title:
  When seeking in VLC playing most videos, sound is choppy for 9s after
  seek.

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  System was working fine in Ubuntu 19.04. After update to 19.10 and
  reboot, videos have audio problems after seeking. The majority of
  videos I tested had trouble, but the severity of the problem varies
  even in the problem videos. The sound cuts in and out inconsistently,
  as if some software is having trouble filling the audio buffer in
  time.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  x  1708 F pulseaudio
   /dev/snd/controlC0:  x  1708 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 21:07:33 2019
  InstallationDate: Installed on 2018-12-09 (313 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful
  Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_Jack: Black SPDIF Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: None of the above
  Title: [To Be Filled By O.E.M., Realtek ALC1220, Black SPDIF Out, Rear] 
Playback problem
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  dmi.bios.date: 04/01/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.20
  dmi.board.name: B450 Gaming-ITX/ac
  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.:bvrP3.20:bd04/01/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

-- 
Mailing list: https://launchpad.net/~touch-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)

2020-10-22 Thread Hui Wang

This is the debdiff for groovy.


** Summary changed:

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

** Patch added: "alsa-lib_1.2.3.2-1ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1897934/+attachment/5425419/+files/alsa-lib_1.2.3.2-1ubuntu3.debdiff

-- 
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:
  New
Status in alsa-lib package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  In Progress
Status in alsa-lib source package in Groovy:
  In Progress

Bug description:
  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 1897934] Re: [Intel HDA] The initial sound level is set to zero (muted)

2020-10-22 Thread Hui Wang

** Also affects: alsa-lib (Ubuntu Groovy)
   Importance: Critical
 Assignee: Hui Wang (hui.wang)
   Status: In Progress

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

** Changed in: alsa-lib (Ubuntu Focal)
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: alsa-lib (Ubuntu Focal)
   Status: New => In Progress

** Changed in: alsa-lib (Ubuntu Focal)
   Importance: Undecided => Critical

-- 
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:
  [Intel HDA] The initial sound level is set to zero (muted)

Status in Release Notes for Ubuntu:
  New
Status in alsa-lib package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  In Progress
Status in alsa-lib source package in Groovy:
  In Progress

Bug description:
  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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

2020-10-22 Thread Javier Paniagua Laconich

@nicktelindert

you're right. I was so happy that I misidentified my own notebook. It's
the one that came right after the 9380: the 7390 (not the 2-in-1) with
the dreaded intel bluetooth/wifi killer ax200.

-- 
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 1897934] Re: [Intel HDA] The initial sound level is set to zero (muted)

2020-10-22 Thread Hui Wang

I reproduced the bug, and this is a alsa-lib's issue, and the latest
alsa-lib already has the fix. Let me test it and backport it to groovy
and maybe focal.


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

** No longer affects: pulseaudio (Ubuntu)

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

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

Status in Release Notes for Ubuntu:
  New
Status in alsa-lib package in Ubuntu:
  In Progress

Bug description:
  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 1897934] ProcModules.txt

2020-10-22 Thread Norbert

apport information

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

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

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  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 1897934] PulseList.txt

2020-10-22 Thread Norbert

apport information

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

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

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  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 1897934] WifiSyslog.txt

2020-10-22 Thread Norbert

apport information

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

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

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  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 1897934] acpidump.txt

2020-10-22 Thread Norbert

apport information

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

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

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  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 1897934] RfKill.txt

2020-10-22 Thread Norbert

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1897934/+attachment/5425388/+files/RfKill.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/1897934

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

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  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 1897934] CRDA.txt

2020-10-22 Thread Norbert

apport information

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

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

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  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 1897934] UdevDb.txt

2020-10-22 Thread Norbert

apport information

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

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

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  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 1897934] ProcCpuinfoMinimal.txt

2020-10-22 Thread Norbert

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1897934/+attachment/5425384/+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/1897934

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

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  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 1897934] ProcInterrupts.txt

2020-10-22 Thread Norbert

apport information

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

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

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  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 1897934] PaInfo.txt

2020-10-22 Thread Norbert

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1897934/+attachment/5425383/+files/PaInfo.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/1897934

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

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  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 1897934] Lsusb-v.txt

2020-10-22 Thread Norbert

apport information

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

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

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  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 1897934] Lspci-vt.txt

2020-10-22 Thread Norbert

apport information

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

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

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  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 1897934] CurrentDmesg.txt

2020-10-22 Thread Norbert

apport information

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

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

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  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 1897934] Lsusb-t.txt

2020-10-22 Thread Norbert

apport information

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

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

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  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 1897934] Lsusb.txt

2020-10-22 Thread Norbert

apport information

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

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

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  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 1897934] Lspci.txt

2020-10-22 Thread Norbert

apport information

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

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

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  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 1897934] Dependencies.txt

2020-10-22 Thread Norbert

apport information

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

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

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  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 1897934] IwConfig.txt

2020-10-22 Thread Norbert

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1897934/+attachment/5425377/+files/IwConfig.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/1897934

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

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  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 1897934] Re: [Intel HDA] The initial sound level is set to zero (muted)

2020-10-22 Thread Norbert

Below is apport-collect for Lenovo SL500.

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

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

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  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 1900906] monitors.xml.txt

2020-10-22 Thread Fernando

apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/1900906/+attachment/5425397/+files/monitors.xml.txt

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

Title:
  Can't input accents in GNOME shell

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. 
Under X, if I try to input an accentuated character, such as á or ü, in places 
like the search field in the overview or when writing a folder name in the app 
grid, nothing appears. Under Wayland, it fails each time on the first input of 
an accentuated character, then it works.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-01 (174 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Package: ibus
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (22 days ago)
  UserGroups: sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~touch-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] apport information

2020-10-22 Thread Norbert

ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu-mate   4795 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.455
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.10
LiveMediaBuild: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 (20201021.2)
MachineType: LENOVO 27463ZG
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: pulseaudio 1:13.99.2-1ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed 
maybe-ubiquity quiet splash ---
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-25-generic N/A
 linux-backports-modules-5.8.0-25-generic  N/A
 linux-firmware1.190
Tags:  groovy
Uname: Linux 5.8.0-25-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/01/2010
dmi.bios.release: 6.15
dmi.bios.vendor: LENOVO
dmi.bios.version: 6AET64WW
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: 27463ZG
dmi.board.vendor: LENOVO
dmi.board.version: LENOVO 6AET64WW
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: LENOVO 6AET64WW
dmi.ec.firmware.release: 177.3
dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:br6.15:efr177.3:svnLENOVO:pn27463ZG:pvrThinkPadSL500:rvnLENOVO:rn27463ZG:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
dmi.product.name: 27463ZG
dmi.product.version: ThinkPad SL500
dmi.sys.vendor: LENOVO

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

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

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  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

1 2 >

1 - 100 of 132 matches

Mail list logo