date:20200720

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

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

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

Title:
  Administrators are not added to adm group

Status in accountsservice package in Ubuntu:
  Expired

Bug description:
  Currently administrators are only added to the sudo group. This was
  fixed a long time ago by https://bugs.launchpad.net/ubuntu/+source
  /gnome-control-center/+bug/810907, but there has likely been a
  regression.

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

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

[Touch-packages] [Bug 1743095] Re: update impossible

Please explain what kind of problem you are experiencing.

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

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

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

Title:
  update impossible

Status in Ubuntu:
  Incomplete

Bug description:
  vandalisme

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CasperVersion: 1.376.2
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Jan 13 12:04:05 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0534]
  LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
  MachineType: Dell Inc. Latitude E6430
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.asset.tag: HHGMBW1
  dmi.board.name: 0X6W22
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: HHGMBW1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd10/08/2012:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0X6W22:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1888337] Re: Display Issue

Please explain the problem you are experiencing in more detail. If you
can attach a photo of the issue then please do.


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

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

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

Title:
  Display Issue

Status in Ubuntu:
  Incomplete

Bug description:
  Cant see icon when login

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228
  Uname: Linux 4.4.0-186-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jul 21 08:53:58 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21e2]
  InstallationDate: Installed on 2016-10-13 (1376 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 1143AM1
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-186-generic 
root=UUID=8cfb78ef-b7c8-4c97-be06-7f457553374b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/13/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8HET41WW(1.23)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 1143AM1
  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:bvr8HET41WW(1.23):bd01/13/2012:svnLENOVO:pn1143AM1:pvrThinkPadE520:rvnLENOVO:rn1143AM1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 1143AM1
  dmi.product.version: ThinkPad E520
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Jul 21 08:36:35 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 739 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Touch-packages] [Bug 1888326] Re: Bluetooth device not found QCA9565

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

It appears bug 1475639 already exists for this issue.

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

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

** This bug has been marked a duplicate of bug 1475639
   Atheros QCA9565 bluetooth hardware not detected

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

Title:
  Bluetooth device not found QCA9565

Status in linux package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Hello,
  I run Ubuntu 20.04 LTS on my Acer Aspire E5-573G and Ubuntu can't found my 
bluetooth device.

  I have a QCNFA335 (QCA9565) which can normally support both wifi and
  bluetooth

  I can use both wifi and bluetooth on windows 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 20:24:58 2020
  InstallationDate: Installed on 2020-07-17 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: bnep btusb bluetooth
  MachineType: Acer Aspire E5-573G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=eec36b7b-bbf9-463c-80a6-6ec698a4d655 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.37
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BDW
  dmi.product.name: Aspire E5-573G
  dmi.product.sku: Aspire E5-573G_098A_1_37
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer
  hciconfig:

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

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

[Touch-packages] [Bug 1888316] Re: Corrupted gridlines on Dslstats on Intel HD 5500 (Dell Latitude E7250)

This looks like an aliasing problem. Aliasing may be slightly different
between graphics drivers but mostly it's the job of the application to
avoid it. So please report the bug to Dslstats instead.

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

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

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

Title:
  Corrupted gridlines on Dslstats on Intel HD 5500 (Dell Latitude E7250)

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  On Ubuntu MATE 20.04 (and other releases of Ubuntu) I've noticed a problem 
with Dslstats (http://dslstats.me.uk/). I see corrupted gridlines as it is 
shown here.
  https://i.postimg.cc/Fz6TJ8pc/corrupted-gridlines.png

  On Intel Xorg driver I don't see this problem.
  https://i.postimg.cc/zv4kfWDF/normal-gridlines.png

  Configurations when the problem occurs:
  Dell Latitude E7250 (Intel HD 5500 graphics card) on Xorg with modesetting 
driver
  Dell Latitude E7250 (Intel HD 5500 graphics card) on Wayland

  Configurations when the problem does not occur:
  Dell Latitude E7250 on Xorg with intel driver
  Dell Optiplex 745 with AMD Radeon HD6450 graphis card
  Dell Optiplex 745 with integrated Intel GMA 3000 on Xorg with modesetting 
driver
  Dell Optiplex 745 with integrated Intel GMA 3000 on Xorg with intel driver

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Mon Jul 20 20:13:44 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:062d]
  InstallationDate: Installed on 2020-06-05 (44 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  MachineType: Dell Inc. Latitude E7250
  ProcEnviron:
   LANGUAGE=pl
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=a072e6bc-e343-4720-9683-3754537c1cc5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A24
  dmi.board.name: 0V8RX3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA24:bd04/10/2020:svnDellInc.:pnLatitudeE7250:pvr:rvnDellInc.:rn0V8RX3:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7250
  dmi.product.sku: 062D
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  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-server/+bug/1888316/+subscriptions

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

[Touch-packages] [Bug 1888337] [NEW] Display Issue

2020-07-20 Thread Irfan

Public bug reported:

Cant see icon when login

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228
Uname: Linux 4.4.0-186-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.23
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Jul 21 08:53:58 2020
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21e2]
InstallationDate: Installed on 2016-10-13 (1376 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 1143AM1
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-186-generic 
root=UUID=8cfb78ef-b7c8-4c97-be06-7f457553374b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/13/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 8HET41WW(1.23)
dmi.board.asset.tag: Not Available
dmi.board.name: 1143AM1
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:bvr8HET41WW(1.23):bd01/13/2012:svnLENOVO:pn1143AM1:pvrThinkPadE520:rvnLENOVO:rn1143AM1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 1143AM1
dmi.product.version: ThinkPad E520
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Jul 21 08:36:35 2020
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 739 
 vendor LGD
xserver.version: 2:1.18.4-0ubuntu0.8

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  Display Issue

Status in xorg package in Ubuntu:
  New

Bug description:
  Cant see icon when login

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228
  Uname: Linux 4.4.0-186-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jul 21 08:53:58 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21e2]
  InstallationDate: Installed on 2016-10-13 (1376 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 1143AM1
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-186-generic 
root=UUID=8cfb78ef-b7c8-4c97-be06-7f457553374b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/13/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8HET41WW(1.23)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 1143AM1
  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:

[Touch-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

2020-07-20 Thread alex-mobigo

Ouch, I missed this commit:
https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34/diffs?commit_id=8b45f9589b3eb1ff46d16c774b017794e553db8e

I Will try again.

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

Title:
Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
applications

Status in libx11 package in Ubuntu:
Confirmed
Status in pcmanfm package in Ubuntu:
Triaged

Bug description:
STEPS TO REPRODUCE
==
The bug seems to occur when clicking on a file or folder. It is random and
difficult to provide clear steps to reproduce. It is, however, a common
situation.

EXPECTED RESULTS

pcmanfm works without problem.

ACTUAL RESULTS
==
All pcmanfm windows become unresponsive, though background processes (e.g.
copying) may continue without problem. with the same error message in
~/.cache/lxsession/LXDE/run.log:

[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not
been called
[xcb] Aborting, sorry about that.
pcmanfm: xcb_io.c:259: poll_for_event: Assertion
`!xcb_xlib_threads_sequence_lost' failed.
** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

(note the timestamp on the message will vary)

AFFECTED VERSIONS
=
1.2.5-3ubuntu1
NOT 1.2.4-1ubuntu0.1

UPSTREAM BUG

https://sourceforge.net/p/pcmanfm/bugs/1089/

ADDITIONAL NOTES

Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad)
seem to have the same problems. This is probably at least rooted in a GTK2 bug:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710

To further assert this, note that there is a SpaceFM file manager that
is available in GTK2 and GTK3. The GTK2 version displays the behavior.
The GTK3 version does not. Same with LibreOffice.

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

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

[Touch-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

2020-07-20 Thread alex-mobigo

I would like to add some info that may help to narrow the problem.
I have had this crash in PCManFM since i upgraded ubuntu from 16.04 to 18.04 
but the same bug manifest in Geany and Chromium as well. The bug could hit 
PCManFM within a few clicks opening directories and then clicking on a file or 
can take hours to show up. In the case of Chromium it usually hit at the launch 
of the browser.

I rebuilt the LibX11 with the supposedly fix mentioned by Tycho Kircher
and apparently this has not fixed the problem but the crash is now
without the Assertion `!xcb_xlib_threads_sequence_lost' failed.

I installed only these packages:

* libx11-xcb1_1.6.4-3ubuntu0.2_amd64.deb
* libx11-xcb-dev_1.6.4-3ubuntu0.2_amd64.deb

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

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Confirmed
Status in pcmanfm package in Ubuntu:
  Triaged

Bug description:
  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  
  Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) 
seem to have the same problems. This is probably at least rooted in a GTK2 bug:
  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710

  To further assert this, note that there is a SpaceFM file manager that
  is available in GTK2 and GTK3. The GTK2 version displays the behavior.
  The GTK3 version does not. Same with LibreOffice.

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

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

[Touch-packages] [Bug 1888041] Re: default output is ignored and reset after reboot

Christoph, please report your issue to the developers at:

  https://gitlab.freedesktop.org/groups/pulseaudio/-/issues

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

Title:
  default output is ignored and reset after reboot

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have lots of possible outputs, like speakers, wireless headset, and
  HDMI output. I select speakers as default, but on reboot it always
  select the wireless headset.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 18 01:59:22 2020
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7803
  dmi.board.asset.tag: Default string
  dmi.board.name: CROSSHAIR VI HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7803:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1888326] [NEW] Bluetooth device not found QCA9565

2020-07-20 Thread Frédéric Annequin

Public bug reported:

Hello,
I run Ubuntu 20.04 LTS on my Acer Aspire E5-573G and Ubuntu can't found my 
bluetooth device.

I have a QCNFA335 (QCA9565) which can normally support both wifi and
bluetooth

I can use both wifi and bluetooth on windows 10.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 20 20:24:58 2020
InstallationDate: Installed on 2020-07-17 (3 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: bnep btusb bluetooth
MachineType: Acer Aspire E5-573G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=eec36b7b-bbf9-463c-80a6-6ec698a4d655 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/16/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.37
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: ZORO_BH
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: BDW
dmi.product.name: Aspire E5-573G
dmi.product.sku: Aspire E5-573G_098A_1_37
dmi.product.version: V3.72
dmi.sys.vendor: Acer
hciconfig:

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


** Tags: amd64 apport-bug focal

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

Title:
  Bluetooth device not found QCA9565

Status in bluez package in Ubuntu:
  New

Bug description:
  Hello,
  I run Ubuntu 20.04 LTS on my Acer Aspire E5-573G and Ubuntu can't found my 
bluetooth device.

  I have a QCNFA335 (QCA9565) which can normally support both wifi and
  bluetooth

  I can use both wifi and bluetooth on windows 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 20:24:58 2020
  InstallationDate: Installed on 2020-07-17 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: bnep btusb bluetooth
  MachineType: Acer Aspire E5-573G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=eec36b7b-bbf9-463c-80a6-6ec698a4d655 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.37
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BDW
  dmi.product.name: Aspire E5-573G
  dmi.product.sku: Aspire E5-573G_098A_1_37
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer
  hciconfig:

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

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

[Touch-packages] [Bug 1888318] [NEW] dhclient exit hooks aren't guaranteed to run

2020-07-20 Thread Ray Link

Public bug reported:

ntp-systemd-netif.path contains the following:

[Install]
WantedBy=network-pre.target

However, network-pre.target is a passive systemd target.  It is used
only for ordering, and is not guaranteed to be pulled in unless
something else calls for it explicitly.

On a host where nothing pulls in network-pre.target, the ntp-systemd-netif path 
monitoring never gets started, and so changes in
/run/systemd/netif/leases never trigger the dhclient exit hooks for ntp.

Instead, the systemd unit that starts the path monitoring should be
configured with something like:

[Unit]
Wants=network-pre.target
Before=network-pre.target

[Install]
WantedBy=network.target

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

** Description changed:

  ntp-systemd-netif.path contains the following:
  
  [Install]
  WantedBy=network-pre.target
  
+ However, network-pre.target is a passive systemd target.  It is used
+ only for ordering, and is not guaranteed to be pulled in unless
+ something else calls for it explicitly.
  
- However, network-pre.target is a passive systemd target.  It is used only for 
ordering, and is not guaranteed to be pulled in unless something else calls for 
it explicitly.
- 
- On a host where nothing pulls in network-pre.target, the ntp-systemd-
- netif path monitoring never gets started, and so changes in
+ On a host where nothing pulls in network-pre.target, the ntp-systemd-netif 
path monitoring never gets started, and so changes in
  /run/systemd/netif/leases never trigger the dhclient exit hooks for ntp.
  
  Instead, the systemd unit that starts the path monitoring should be
  configured with something like:
  
  [Unit]
  Wants=network-pre.target
  Before=network-pre.target
  
  [Install]
  WantedBy=network.target

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

Title:
  dhclient exit hooks aren't guaranteed to run

Status in ntp package in Ubuntu:
  New

Bug description:
  ntp-systemd-netif.path contains the following:

  [Install]
  WantedBy=network-pre.target

  However, network-pre.target is a passive systemd target.  It is used
  only for ordering, and is not guaranteed to be pulled in unless
  something else calls for it explicitly.

  On a host where nothing pulls in network-pre.target, the ntp-systemd-netif 
path monitoring never gets started, and so changes in
  /run/systemd/netif/leases never trigger the dhclient exit hooks for ntp.

  Instead, the systemd unit that starts the path monitoring should be
  configured with something like:

  [Unit]
  Wants=network-pre.target
  Before=network-pre.target

  [Install]
  WantedBy=network.target

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

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

[Touch-packages] [Bug 1873961] Comment bridged from LTC Bugzilla

2020-07-20 Thread bugproxy

--- Comment From z...@us.ibm.com 2020-07-20 17:09 EDT---
I download iproute2-4.19.0.tar.gz from this upstream url:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git

Build and tested on my existing ppc64 Genesis OS (4.15.0-1039-ibm-gt),
I do see it now reports correct tcp_flags mask.

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

Title:
  tc filter show tcp_flags wrong mask value

Status in The Ubuntu-power-systems project:
  Triaged
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Triaged

Bug description:
  ---Problem Description---
  Problem Descriptions
  "tc" utility does not show correct TC rule's tcp_flags mask correctly in 
current "iproute2" package shipped on Genesis.
  # dpkg -l |grep iproute2
  ii  iproute2  4.15.0-2ubuntu1  ppc64el  networking and traffic control 
tools

   
  ---Steps to Reproduce---
   Steps to reproduce the problem:
  1) Add a tc rule to the testing VF (i.e. p0v2_r):
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2  
skip_sw action mirred egress redirect dev p0v0_r
   
  2) Validate the added TC rule:
  # tc filter show dev p0v2_r root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 22   /* <--- Wrong */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen
   
  3) If we add the tcp_flags using explicit mask 0x7:
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 
 skip_sw action mirred egress redirect dev p0v0_r
   
  After that, using "tc filter show dev p0v2_r root" to verify, we still see 
the same output (tcp_flags 22) as shown in 2) above, which is wrong.
   
  Userspace tool common name: tc 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace package: iproute2

  ==
  Fixes:
  There are 2 patches to fix the issue:
  patch 1:
  commit b85076cd74e77538918d35992b1a9cd17ff86af8
  Author: Stephen Hemminger 
  Date:   Tue Sep 11 08:29:33 2018 -0700
  lib: introduce print_nl
  Common pattern in iproute commands is to print a line seperator
  in non-json mode. Make that a simple function.
  /* This patch declares global variable "const char *_SL_ = "\n";" in 
lib/utils.c to be used by 2nd patch */
   
  patch 2:
  commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc
  Author: Keara Leibovitz 
  Date:   Thu Jul 26 09:45:30 2018 -0400
  tc: fix bugs for tcp_flags and ip_attr hex output
  Fix hex output for both the ip_attr and tcp_flags print functions.
   
  With the above 2 patches pull in, the new "tc" utility will show the correct 
tcp_flags mask:
  # tc filter show dev p0v2 root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 0x2/7   /* <--- Correct */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen

  
  This bug affects tc in Ubuntu 18.04.1 stock image.

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

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

[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

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

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

-- 
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 bluez package in Ubuntu:
  Confirmed

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)
Data length: 0x1a
  03 19 c2

[Touch-packages] [Bug 1888316] [NEW] Corrupted gridlines on Dslstats on Intel HD 5500 (Dell Latitude E7250)

2020-07-20 Thread Konrad Kołodziejczyk

Public bug reported:

On Ubuntu MATE 20.04 (and other releases of Ubuntu) I've noticed a problem with 
Dslstats (http://dslstats.me.uk/). I see corrupted gridlines as it is shown 
here.
https://i.postimg.cc/Fz6TJ8pc/corrupted-gridlines.png

On Intel Xorg driver I don't see this problem.
https://i.postimg.cc/zv4kfWDF/normal-gridlines.png

Configurations when the problem occurs:
Dell Latitude E7250 (Intel HD 5500 graphics card) on Xorg with modesetting 
driver
Dell Latitude E7250 (Intel HD 5500 graphics card) on Wayland

Configurations when the problem does not occur:
Dell Latitude E7250 on Xorg with intel driver
Dell Optiplex 745 with AMD Radeon HD6450 graphis card
Dell Optiplex 745 with integrated Intel GMA 3000 on Xorg with modesetting driver
Dell Optiplex 745 with integrated Intel GMA 3000 on Xorg with intel driver

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: MATE
Date: Mon Jul 20 20:13:44 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 5500 [1028:062d]
InstallationDate: Installed on 2020-06-05 (44 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
MachineType: Dell Inc. Latitude E7250
ProcEnviron:
 LANGUAGE=pl
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=a072e6bc-e343-4720-9683-3754537c1cc5 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/10/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A24
dmi.board.name: 0V8RX3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA24:bd04/10/2020:svnDellInc.:pnLatitudeE7250:pvr:rvnDellInc.:rn0V8RX3:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7250
dmi.product.sku: 062D
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Corrupted gridlines on Dslstats on Intel HD 5500 (Dell Latitude E7250)

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu MATE 20.04 (and other releases of Ubuntu) I've noticed a problem 
with Dslstats (http://dslstats.me.uk/). I see corrupted gridlines as it is 
shown here.
  https://i.postimg.cc/Fz6TJ8pc/corrupted-gridlines.png

  On Intel Xorg driver I don't see this problem.
  https://i.postimg.cc/zv4kfWDF/normal-gridlines.png

  Configurations when the problem occurs:
  Dell Latitude E7250 (Intel HD 5500 graphics card) on Xorg with modesetting 
driver
  Dell Latitude E7250 (Intel HD 5500 graphics card) on Wayland

  Configurations when the problem does not occur:
  Dell Latitude E7250 on Xorg with intel driver
  Dell Optiplex 745 with AMD Radeon HD6450 graphis card
  Dell Optiplex 745 with integrated Intel GMA 3000 on Xorg with modesetting 
driver
  Dell Optiplex 745 with integrated Intel GMA 3000 on Xorg with intel driver

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Mon Jul 20 20:13:44 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:062d]
  InstallationDate: Installed on 2020-06-05 (44 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64

[Touch-packages] [Bug 1872000] Re: 2020'Q1 Intel new media release

2020-07-20 Thread Sebastian Ramacher

** Changed in: intel-media-driver (Ubuntu)
   Status: New => Fix Released

** Changed in: intel-media-driver-non-free (Ubuntu)
   Status: New => Fix Released

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

Title:
  2020'Q1 Intel new media release

Status in intel:
  Fix Released
Status in intel-gmmlib package in Ubuntu:
  Fix Released
Status in intel-media-driver package in Ubuntu:
  Fix Released
Status in intel-media-driver-non-free package in Ubuntu:
  Fix Released
Status in intel-mediasdk package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Fix Released
Status in libva-utils package in Ubuntu:
  Fix Released

Bug description:
  Description:

  Open Source Media Stack 2020’Q1 release is available for customers with below 
improvements.
  1.Capability extension. Enabled HEVC SCC Decoding and Tile mode support 
for TGL, added AYUV/ARGB10/Y410 format support in HEVC VDEnc.
  2.SW modularity & extendibility enhancement by refactoring VP SFC, 
MediaOS and MSDK HEVC encoding.
  3.Better performance, by enabling VP9 VDEnc scalability and HEVC VDEnc 
DirtyROI.
  4.New MSDK API and features: Media SDK API v1.32 added SCC HEVC decoding, 
VP mirroring, Tile mode support, and Sliding Window/Weighted Prediction/Fade 
Detection support for HEVC encoding.

  • Media driver: intel-media-20.1.1
  • Media SDK: intel-mediasdk-20.1.0
  • Libva: 2.7.0
  • Libva-utils: 2.7.1
  • Gmmlib: intel-gmmlib-20.1.1

  Target Release: 20.04

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

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

[Touch-packages] [Bug 1883880] Re: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic

2020-07-20 Thread Bug Watch Updater

** Changed in: binutils (Debian)
   Status: Unknown => Confirmed

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

Title:
  fix non-8-bit x86 displacements breaking AVX512 builds on Bionic

Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Bionic:
  Fix Committed
Status in binutils package in Debian:
  Confirmed

Bug description:
  [Impact]

   * the assembler scales non 8 bit cases which was identified
 to break e.g. some AVX512 code. It is nasty as it isn't a compile/link/ 
 time error. Instead the instructions might silently be corrupted until 
 running. Things might even work on some but fail on other systems if 
 e.g. the AVX code paths only run on newer chips.

* The fix is upstream for a while and not re-changed again. Furthermore 
  it is in several Ubuntu releases without bugs due to that, which should 
  make the backport rather safe.

  [Test Case]

   * Simple example to trigger the bug:

  echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d
  avx.o | grep vmovaps

  The expected output is that the objdump output matches the vmovaps
  instruction input. When using binutils with the bug, the initial 0x40
  will be incorrect.

  Working:
  $ echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d avx.o | 
grep vmovaps
 0: 62 f1 7c 48 28 04 05 vmovaps 0x40(,%rax,1),%zmm0
  Failing:
  $ echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d avx.o | 
grep vmovaps
 0: 62 f1 7c 48 28 04 05 vmovaps 0x1(,%rax,1),%zmm0

  [Regression Potential]

   * Well, this is a double edged sword. On one hand this is fortunately a 
 small change and only affects something formerly clearly broken. So it 
 should be good and only change cases formerly being bad.
 But OTOH binutils areused in so many cases that I feel unable to say
 "nothing will happen". The change goes to the gnu assembler, so that is 
 the place to look out for regressions.

  [Other Info]
   
   * needs a sponsor experienced with binutils to check potential pitfalls


  
  ---

  
  Hi,
  DPDK has run into some issues in the past
   https://bugs.dpdk.org/show_bug.cgi?id=97
   https://bugs.dpdk.org/show_bug.cgi?id=249

  Eventually the issues got resolved in binutils via
   https://sourceware.org/bugzilla/show_bug.cgi?id=23465

  After binutils is fixed people rebuilding DPDK themselve can use
   http://patches.dpdk.org/patch/71679/
  to gain more performance while on Bionics bintuils level.

  Note: Bionic is on DPDK 17.11.x which will not get further stable release 
afaik. But quite often people build their own DPDK. In fact this came up as a 
request from Openvswitch upstream/Intel to allow such builds on Bionic.
  I'd ping those people about the bug and ask them to participate in the 
verification if this becomes an SRU.

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

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

[Touch-packages] [Bug 1857036] Re: `sudo --login --user USERNAME` throws `setrlimit(RLIMIT_CORE): Operation not permitted` error when run inside a container.

Thanks Bryce for the PPA. I can confirm it does work:

# reproduce the problem:
root@sudo-sru-lp1857036-test:~# sudo true
sudo: setrlimit(RLIMIT_CORE): Operation not permitted

# get the fix from the PPA:
root@sudo-sru-lp1857036-test:~# apt-add-repository -yus 
ppa:bryce/sudo-sru-lp1857036-setrlimit-in-lxc
Get:1 http://security.ubuntu.com/ubuntu focal-security InRelease [107 kB]
Get:2 http://ppa.launchpad.net/bryce/sudo-sru-lp1857036-setrlimit-in-lxc/ubuntu 
focal InRelease [17.6 kB]   
Hit:3 http://archive.ubuntu.com/ubuntu focal InRelease  

Get:4 http://archive.ubuntu.com/ubuntu focal-updates InRelease [111 kB]
Get:5 http://ppa.launchpad.net/bryce/sudo-sru-lp1857036-setrlimit-in-lxc/ubuntu 
focal/main Sources [864 B]
Get:6 http://ppa.launchpad.net/bryce/sudo-sru-lp1857036-setrlimit-in-lxc/ubuntu 
focal/main amd64 Packages [756 B]   
Get:7 http://ppa.launchpad.net/bryce/sudo-sru-lp1857036-setrlimit-in-lxc/ubuntu 
focal/main Translation-en [528 B]
Get:8 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [261 
kB]
Get:9 http://archive.ubuntu.com/ubuntu focal-updates/main Translation-en [102 
kB]
Get:10 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages 
[28.4 kB]
Get:11 http://archive.ubuntu.com/ubuntu focal-updates/restricted Translation-en 
[7,560 B]
Fetched 637 kB in 2s (389 kB/s)
Reading package lists... Done
root@sudo-sru-lp1857036-test:~# apt-get install -V sudo
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be upgraded:
   sudo (1.8.31-1ubuntu1 => 1.8.31-1ubuntu2~focal1)
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,320 kB of archives.
After this operation, 1,849 kB of additional disk space will be used.
Get:1 http://ppa.launchpad.net/bryce/sudo-sru-lp1857036-setrlimit-in-lxc/ubuntu 
focal/main amd64 sudo amd64 1.8.31-1ubuntu2~focal1 [1,320 kB]
Fetched 1,320 kB in 3s (495 kB/s)
(Reading database ... 16712 files and directories currently installed.)
Preparing to unpack .../sudo_1.8.31-1ubuntu2~focal1_amd64.deb ...
Unpacking sudo (1.8.31-1ubuntu2~focal1) over (1.8.31-1ubuntu1) ...
Setting up sudo (1.8.31-1ubuntu2~focal1) ...

# confirm the fix:
root@sudo-sru-lp1857036-test:~# sudo true
root@sudo-sru-lp1857036-test:~#

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

Title:
  `sudo --login --user USERNAME` throws `setrlimit(RLIMIT_CORE):
  Operation not permitted` error when run inside a container.

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

Bug description:
  [Impact]
  Logging in as a sudo user in a Ubuntu Focal Linux container displays a
  warning:

    sudo: setrlimit(RLIMIT_CORE): Operation not permitted

  The warning is entirely unnecessary - the container is trying to adjust
  RLIMIT_CORE, but this isn't allowed inside a container anyway.

  While this is "just" a warning, logging into a container as sudo is a
  very common practice, so this warning risks creating confusion for LTS
  users.

  [Test Case]
  $ lxc launch ubuntu:20.04/amd64 sudo-sru-lp1857036-test
  $ lxc shell sudo-sru-lp1857036-test

  # sudo --login --user ubuntu
  sudo: setrlimit(RLIMIT_CORE): Operation not permitted
  To run a command as administrator (user "root"), use "sudo ".
  See "man sudo_root" for details.
  $ logout

  Install the PPA
  # apt-add-repository -yus ppa:bryce/sudo-sru-lp1857036-setrlimit-in-lxc
  # apt-get install sudo

  # sudo --login --user ubuntu
  $

  [Regression Potential]
  As this only affects printing of a couple warnings, the only behavioral
  change is in stderr output.

  [Discussion]
  This changes a couple warnings into equivalent debug printfs, which
  brings the sudo behavior in-line with the behavior in groovy, bionic,
  etc. and should cause no troubles.

  This patch originates from upstream, and is already in groovy's sudo
  package (which thus can be seen not to exhibit the issue).

  The upstream patch includes some new debug prints which should be
  harmless but are unnecessary to the fix so they've been removed.

  [Original Report]
  When using `sudo --login --user USERNAME` with Ubuntu Focal currently, it 
will correctly operate but it will also throw the following error before 
continuing with the logon process (which completes successfully except for the 
stated error):

  sudo: setrlimit(RLIMIT_CORE): Operation not permitted

  A full run of this was tested in a Focal LXD container after dropping
  to a root shell to reproduce (arstotzka is the host system, focal-test
  is the test container):

  teward@arstotzka:~$ lxc shell focal-test
  root@focal-test:~# sudo --login --user ubuntu
  sudo:

[Touch-packages] [Bug 1867799] Re: Focal: sudo: setrlimit(RLIMIT_CORE): Operation not permitted

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

** This bug has been marked a duplicate of bug 1857036
   `sudo --login --user USERNAME` throws `setrlimit(RLIMIT_CORE): Operation not 
permitted` error when run inside a container.

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

Title:
  Focal: sudo: setrlimit(RLIMIT_CORE): Operation not permitted

Status in juju:
  Invalid
Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  When bootstrapping to focal and using debug output, we get the
  following outputted to the stderr.

  sudo: setrlimit(RLIMIT_CORE): Operation not permitted

  I'm unsure what it's attempting to do at that point, but others have
  also run into this with a suggested workaround.

  https://gitlab.alpinelinux.org/alpine/aports/issues/11122
  https://bugzilla.redhat.com/show_bug.cgi?id=1773148

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

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

[Touch-packages] [Bug 1868456] Re: "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo in 20.04 LXD container

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

** This bug has been marked a duplicate of bug 1857036
   `sudo --login --user USERNAME` throws `setrlimit(RLIMIT_CORE): Operation not 
permitted` error when run inside a container.

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

Title:
  "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when
  using sudo in 20.04 LXD container

Status in lxd package in Ubuntu:
  Invalid
Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  I fired up a LXD container using ubuntu-daily:f on my machine and
  every time I issue a comment inside the container using sudo, I get
  this error:

  sudo: setrlimit(RLIMIT_CORE): Operation not permitted

  I did some digging online and found this was reported against Fedora last 
fall which lead me to this bugzilla report:
  https://bugzilla.redhat.com/show_bug.cgi?id=1773148

  which seems to tie this to a change in sudo between 1.8.28 and 1.8.29.

  Focal has 1.8.31:
  bladernr@focal-builder:~/development/kernels-ubuntu/focal$ apt-cache policy 
sudo
  sudo:
    Installed: 1.8.31-1ubuntu1
    Candidate: 1.8.31-1ubuntu1
    Version table:
   *** 1.8.31-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  This is not an issue on Bionic:
  bladernr@galactica:~/development/kernels-upstream/mainline$ apt-cache policy 
sudo
  sudo:
    Installed: 1.8.21p2-3ubuntu1.2
    Candidate: 1.8.21p2-3ubuntu1.2
    Version table:
   *** 1.8.21p2-3ubuntu1.2 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.8.21p2-3ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  From the redhat bug, the described workaround does clear these
  messages up:

  # set disable_coredump false

  Once I've done that, the error messages go away.

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

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

[Touch-packages] [Bug 1856428] Re: Disable TLS below 1.2 by default

** Merge proposal unlinked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/nss/+git/nss/+merge/387608

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

Title:
  Disable TLS below 1.2 by default

Status in gnutls28 package in Ubuntu:
  Fix Released
Status in golang-1.13 package in Ubuntu:
  New
Status in nss package in Ubuntu:
  Fix Released
Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  Disable TLS 1.0, TLS1.1, DTLS1.0

  As part of focal commitment, we shall disable obsolete protocols by
  default.

  Users can override this behaviour with a config file.

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

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

[Touch-packages] [Bug 1885562] Re: [fips] freebl_fipsSoftwareIntegrityTest fails in FIPS mode

** Merge proposal unlinked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/nss/+git/nss/+merge/387608

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

Title:
  [fips] freebl_fipsSoftwareIntegrityTest fails in FIPS mode

Status in nss package in Ubuntu:
  Fix Released
Status in nss source package in Bionic:
  In Progress
Status in nss source package in Focal:
  In Progress
Status in nss source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * Prevents using some parts of nss in FIPS mode - e.g.
  libfreeblpriv3.so (failed asserts). The library during initialization
  tries to verify it's own binaries against signatures in chk files
  shipped along with it (created at build time). They are installed at
  /usr/lib/$(DEB_HOST_MULTIARCH)/nss while it tries to look for them at
  /usr/lib/$(DEB_HOST_MULTIARCH).

  [Test Case]

   * Setup Ubuntu 18.04 in FIPS mode.
   * sudo apt install chrony
   * sudo chronyd -d
   * chronyd: util.c:373 UTI_IPToRefid: Assertion `MD5_hash >= 0' failed.

  [Regression Potential]

   * Fix introduces 2 new artifacts to the filesystem (symlinks to the
  chk files). It may cause alerts in e.g. CI systems.

  [Other Info]
  Original bug description:

  In FIPS mode there are some additional checks performed.

  They lead to verifying binaries signatures. Those signatures are
  shipped in the libnss3 package as *.chk files installed in
  /usr/lib/$(DEB_HOST_MULTIARCH)/nss. Along with those files are the
  libraries themselves (libfreebl3.so  libfreeblpriv3.so  libnssckbi.so
  libnssdbm3.so  libsoftokn3.so).

  Those libraries are symlinked to be present in /usr/lib/$(DEB_HOST_MULTIARCH):
  ls -l /usr/lib/x86_64-linux-gnu/libfreeblpriv3.so
  lrwxrwxrwx 1 root root 21 Jun 10 18:54 
/usr/lib/x86_64-linux-gnu/libfreeblpriv3.so -> nss/libfreeblpriv3.so

  The client binaries are linked against the symlinks, so when the verification 
happens (lib/freebl/shvfy.c) the mkCheckFileName function takes path to the 
symlink to the shlib and replaces the .so extension with .chk.
  Then it tries to open that file. Obviosly it fails, because the actual file 
is in /usr/lib/$(DEB_HOST_MULTIARCH)/nss.

  [Test case]
  sudo apt install chrony
  sudo chronyd -d
  chronyd: util.c:373 UTI_IPToRefid: Assertion `MD5_hash >= 0' failed.

  Potential solutions:
  Solution A:
  Drop the /usr/lib/$(DEB_HOST_MULTIARCH)/nss directory and put all signatures 
and libs in /usr/lib/$(DEB_HOST_MULTIARCH).

  Solution B:
  Create symlinks to *.chk files in /usr/lib/$(DEB_HOST_MULTIARCH) (like it is 
done for *.so).

  Solution C:
  Implement and upstream NSS feature of resolving symlinks and looking for 
*.chk where the symlinks lead to.

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

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

[Touch-packages] [Bug 1887577] Re: DEP8: Invalid capability setuid

2020-07-20 Thread Andreas Hasenack

** Tags added: update-excuses

** Tags added: update-excuse

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

Title:
  DEP8: Invalid capability setuid

Status in apparmor package in Ubuntu:
  New

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  groovy/groovy/amd64/a/apparmor/20200713_202347_dd214@/log.gz

  Excuses is showing apparmor failing dep8 tests when they are triggered
  by another package.

  last time apparmor was uploaded was on May 14th, and this is the
  package under test:

  https://launchpad.net/ubuntu/+source/apparmor/2.13.3-7ubuntu6

  
  The errors are like this:
  FAIL: test_profile_newer_rewrites_cache (__main__.AAParserAltCacheTests)
  --
  Traceback (most recent call last):
File "/tmp/tmp.40nJ4LqRYT/parser/tst/testlib.py", line 50, in 
new_unittest_func
  return unittest_func(self)
File "./caching.py", line 448, in test_profile_newer_rewrites_cache
  self._generate_cache_file()
File "./caching.py", line 257, in _generate_cache_file
  self.run_cmd_check(cmd)
File "/tmp/tmp.40nJ4LqRYT/parser/tst/testlib.py", line 73, in run_cmd_check
  self.assertEqual(rc, expected_rc, "Got return code %d, expected 
%d\nCommand run: %s\nOutput: %s" % (rc, expected_rc, (' '.join(command)), 
report))
  AssertionError: 1 != 0 : Got return code 1, expected 0
  Command run: ../apparmor_parser --config-file=./parser.conf --base 
/tmp/aa-caching-s3l9wndt --skip-kernel-load --cache-loc 
/tmp/aa-caching-s3l9wndt/cache --cache-loc 
/tmp/aa-caching-s3l9wndt/aa-alt-cachezi43qt78 -q --write-cache -r 
/tmp/aa-caching-s3l9wndt/sbin.pingy
  Output: AppArmor parser error for /tmp/aa-caching-s3l9wndt/sbin.pingy in 
/tmp/aa-caching-s3l9wndt/suid-abstraction at line 3: Invalid capability setuid.

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

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

[Touch-packages] [Bug 1887744] Re: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798

2020-07-20 Thread Dan Streetman

> Sorry, turns out the /etc/systemd/system service file needs to be a
> symlink to trigger the bug. This will do it:

aha! and not only a symlink, but the target of the symlink needs to be
outside the normal systemd service path locations, or it will reject
loading it:

root@lp1887744-f:/etc/systemd/system# ls -l test*
lrwxrwxrwx 1 root root 13 Jul 20 18:17 test.service -> test@.service
-rw-r--r-- 1 root root 76 Jul 20 18:14 test@.service

root@lp1887744-f:/etc/systemd/system# journalctl --no-pager -q -b --grep 
test.service
Jul 20 18:17:33 lp1887744-f systemd[1]: /etc/systemd/system/test.service: 
symlink target name type "test@.service" does not match source, rejecting.



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

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

Title:
  systemd dumps core on starting service: Assertion 'u->instance' failed
  at src/core/load-fragment.c:4798

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  On an Ubuntu 20.04 server, when I started a newly installed systemd
  service 'systemctl start testemail2jira.service', systemd trips on an
  assertion (from journalctl):

  Jul 16 13:49:12 pangolin-jiraconf systemd[1]: Assertion 'u->instance' failed 
at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting.
  Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Caught , dumped core as 
pid 2906637.
  Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Freezing execution.

  apport generates a core dump which I trust is attached.

  The server still works, but my terminal keeps showing:

  Failed to get properties: Failed to activate service
  'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)

  and pauses for 25s after each command.

  In case it's relevant, the  i was trying to start had just
  been symlinked into /etc/systemd/system/:

  root@pangolin-jiraconf # ls -la /etc/systemd/system/testemail2jira.service
  lrwxrwxrwx 1 root root 82 Jul 16 13:48 
/etc/systemd/system/testemail2jira.service -> 
/opt/atlassian/jira/current/emailprocessing/testemail2jira/testemail2jira@.service

  File contents:

  [Unit]
  Description=Check that email to %i JIRA works

  [Service]
  #Type=oneshot
  # Note: I keep the config file, testemail2jira.json5 and rsa.* files in 
emailprocessing/, one directory below testemail2jira/, so that they can be 
version-controlled independently.
  # If you want testemail2jira.json5 and rsa.* within testemail2jira/, then add 
testemail2jira/ to WorkingDirectory and remove it from the ExecStart command
  WorkingDirectory=/opt/atlassian/%i/current/emailprocessing
  
ExecStart=/opt/atlassian/%i/current/emailprocessing/testemail2jira/venv/bin/python
 testemail2jira/testemail2jira.py
  User=root

  [Install] 
  WantedBy=multi-user.target

  
  Perhaps the problem is that my service file is a template 
(testemail2jira@.service), but I symlinked it as a regular 
'testemail2jira.service'.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jul 16 14:13:06 2020
  InstallationDate: Installed on 2020-05-27 (49 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=/dev/sda ro 
console=ttyS0,19200n8 net.ifnames=0
  SourcePackage: systemd
  SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 
'Error:'] failed with exit code 1: Failed to get properties: Failed to activate 
service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-3.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-3.1
  dmi.sys.vendor: QEMU

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

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

[Touch-packages] [Bug 1875708] Re: Truncated messages in journald since systemd v244

Reproducing the issue *before* the patch:

root@foo:~# dpkg -l| grep -wF ' systemd '
ii  systemd 245.4-4ubuntu3.1  amd64system 
and service manager
root@foo:~# systemctl status test.service
● test.service - Test Truncate
 Loaded: loaded (/etc/systemd/system/test.service; enabled; vendor preset: 
enabled)
 Active: active (exited) since Mon 2020-07-20 18:08:56 UTC; 53s ago
Process: 228 ExecStart=/usr/lib/test.sh long-test-for-start (code=exited, 
status=0/SUCCESS)
   Main PID: 228 (code=exited, status=0/SUCCESS)

Jul 20 18:08:56 foo systemd[1]: Starting Test Truncate...
Jul 20 18:08:56 foo test.sh[229]: This will
Jul 20 18:08:56 foo test.sh[228]: T
Jul 20 18:08:56 foo test.sh[230]: T
Jul 20 18:08:56 foo test.sh[230]: sually fai
Jul 20 18:08:56 foo test.sh[228]: s
Jul 20 18:08:56 foo test.sh[231]: s
Jul 20 18:08:56 foo test.sh[231]: nd be truncate
Jul 20 18:08:56 foo test.sh[228]: n
Jul 20 18:08:56 foo systemd[1]: Finished Test Truncate.


Upgrading to focal-proposed version:

root@foo:~# apt-get dist-upgrade -V
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
   ...
   libnss-systemd (245.4-4ubuntu3.1 => 245.4-4ubuntu3.2)
   libpam-systemd (245.4-4ubuntu3.1 => 245.4-4ubuntu3.2)
   libseccomp2 (2.4.3-1ubuntu3.20.04.2 => 2.4.3-1ubuntu3.20.04.3)
   libsystemd0 (245.4-4ubuntu3.1 => 245.4-4ubuntu3.2)
   libudev1 (245.4-4ubuntu3.1 => 245.4-4ubuntu3.2)
   systemd (245.4-4ubuntu3.1 => 245.4-4ubuntu3.2)
   systemd-sysv (245.4-4ubuntu3.1 => 245.4-4ubuntu3.2)
   systemd-timesyncd (245.4-4ubuntu3.1 => 245.4-4ubuntu3.2)
   udev (245.4-4ubuntu3.1 => 245.4-4ubuntu3.2)
   ...
17 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

root@foo:~# reboot

Verifying the bug is fixed:

root@foo:~# systemctl status test.service
● test.service - Test Truncate
 Loaded: loaded (/etc/systemd/system/test.service; enabled; vendor preset: 
enabled)
 Active: active (exited) since Mon 2020-07-20 18:12:09 UTC; 1s ago
Process: 139 ExecStart=/usr/lib/test.sh long-test-for-start (code=exited, 
status=0/SUCCESS)
   Main PID: 139 (code=exited, status=0/SUCCESS)

Jul 20 18:12:09 foo systemd[1]: Starting Test Truncate...
Jul 20 18:12:09 foo test.sh[140]: This will
Jul 20 18:12:09 foo test.sh[141]: usually fail
Jul 20 18:12:09 foo test.sh[142]: and be truncated
Jul 20 18:12:09 foo systemd[1]: Finished Test Truncate.


It is so marking as such, thanks!

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

Title:
  Truncated messages in journald since systemd v244

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

Bug description:
  [Impact]

   * since 09d0b46a "journal: refresh cached credentials of stdout streams"
 in ~244 output may be trincated.

   * Upstream has a fix in https://github.com/systemd/systemd/pull/15685

   * Backporting the fix will avoid truncation of log output to journald

  [Test Case]

   * This could happen in any case, but is more likely when a program that 
 has output going to journald is spawning short-lived sub-programs often.
 Therefore the test emphasizes on that:

 - Use a test service like /etc/systemd/system/test.service:
  [Unit]
  Description=Test Truncate
  After=network.target

  [Service]
  ExecStart=/usr/lib/test.sh long-test-for-start
  ExecStop=/usr/lib/test.sh long-test-for-stop
  Type=oneshot
  RemainAfterExit=yes
  StandardOutput=journal+console
  TimeoutStopSec=0

  [Install]
  WantedBy=multi-user.target

 - And a test script like /usr/lib/test.sh:
  #!/bin/sh
  gettext "This will"
  echo
  gettext "usually fail"
  echo
  gettext "and be truncated"
  echo 

  Start/Stopping that service without the fix will look like:
  Apr 30 18:56:40 f systemd[1]: Stopping Test Truncate...
  Apr 30 18:56:40 f test.sh[1165]: T
  Apr 30 18:56:40 f test.sh[1167]: T
  Apr 30 18:56:40 f test.sh[1167]: sually fai
  Apr 30 18:56:40 f test.sh[1165]: s
  Apr 30 18:56:40 f test.sh[1168]: s
  Apr 30 18:56:40 f test.sh[1168]: nd be truncate
  Apr 30 18:56:40 f test.sh[1165]: n
  Apr 30 18:56:40 f systemd[1]: test.service: Succeeded.
  Apr 30 18:56:40 f systemd[1]: Stopped Test Truncate.

  
  [Regression Potential] 

   * The patches are rather small, but there might be a slightly increased 
 memory consumption of journald for output buffers. 
   * Issues (if any and I couldn't find any so far) should be only

[Touch-packages] [Bug 1888133] Re: package libpam-systemd:amd64 204-5ubuntu20.24 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100

2020-07-20 Thread Dan Streetman

unfortunately, Ubuntu 14.04 reached the end of standard support in April
2019, and is now only receives ESM support, which provides only security
patches. You should get a newer version of the CD you are using.

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

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

Title:
  package libpam-systemd:amd64 204-5ubuntu20.24 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 100

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  This happened immediately after booting a Live CD for GNUradio.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libpam-systemd:amd64 204-5ubuntu20.24
  ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  CasperVersion: 1.340.2
  Date: Sat Apr 22 23:25:15 2017
  Df:
   Filesystem 1K-blocks  Used Available Use% Mounted on
   udev 1992364 0   1992364   0% /dev
  DuplicateSignature: package:libpam-systemd:amd64:204-5ubuntu20.24:subprocess 
installed post-installation script returned error exit status 100
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 100
  LiveMediaBuild: LilacSats 14.04 - Release amd64
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 204-5ubuntu20.24 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 100
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1877088] Comment bridged from LTC Bugzilla

2020-07-20 Thread bugproxy

--- Comment From niklas.schne...@ibm.com 2020-07-20 12:57 EDT---
(In reply to comment #19)
> On Fri, 26 Jun 2020 at 15:01, bugproxy <1877...@bugs.launchpad.net> wrote:
> >
> > (In reply to comment #17)
> > > Eoan and later d-i, new installer, curtin do not install
> > > /etc/kernel-img.conf.
> > > Upgraded systems keep having it (ie. installed with bionic or xenial, and
> > > upgraded).
> > >
> > > Can you please let me know if _removing_ /etc/kernel-img.conf breaks $ 
> > > sudo
> > > make install, and if adding /etc/kernel-img.conf back fixes $ sudo make
> > > install?
> > >
> > > Cause the expectation is that `/etc/kernel-img.conf` should not be there,
> > > yet everything should still work correctly.
> > >
> > > I think somewhere something is reading "link_in_boot=yes" and was not
> > > updated with the new implicit default to always assume that on recent 
> > > ubuntu.
> >
> > For me the installkernel script (including in the current case "sudo
> > make install" from a mainline Linux tree) doesn't update the
> > /boot/initrd.img symlink.
> >
> > Interestingly a package upgrade for linux-generic does overwrite this
> > symlink.
>
> .deb package uses very different maintainer scripts / codepath, and is
> not the same operation as "sudo make install".
>
> I personally always build my kernels as debs, and install debs, rather
> than doing "sudo make install". But I am a distribution developer, and
> I care for .debs to work right. Kernel developers, I guess, are
> inverse, and care for "upstream" $ sudo make install to work.
>
> >
> > Not with the /etc/kernel-img.conf[0] and not without it either.
> > As before the /boot/vmlinuz link is always updated.
> >
>
> That is slightly concerning, as to how $ sudo make install, ever
> worked before. Or what has changed since.
>
> Normally, $ sudo make install, should lookup if /sbin/installkernel is
> available, and call that to "do what it has to do, on a given
> distribution", and that script is shipped by the debianutils package
> which is required and must be installed always. And it hasn't been
> touched in ages.
>
> I wonder which arguments are passed to /sbin/installkernel by $ sudo
> make install. And whether the 4th argument is passed, and if it is
> empty, /, or /boot. It should be either empty, or /boot.
>
> --
> Regards,
>
> Dimitri.
So when I built on a beefy development server I usually copy a tar of the 
modules + bzImage + System.map and e.g.:

# sudo tar -xavf 5.8.0-rc6-06703-g93c67d794cfc.tar -C /usr/
# sudo installkernel 5.8.0-rc6-06703-g93c67d794cfc bzImage System.map /boot

that works well on RHEL, Fedora, SUSE and I'm pretty sure it worked on Ubuntu 
only a week prior to me opening this Bugzilla. I also looked in the history
and didn't find anything so yeah I'm pretty confused how that
used to work on Ubuntu but I've even bisected like that (on Ubuntu) so have 
used that approach dozens of times.

Of course for us working with multiple distros there's a lot of value in
this working the same on all of them and I think that's the main point
of the installkernel script.

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

Title:
  [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img
  which is required with the default zipl.conf

Status in Ubuntu on IBM z Systems:
  Triaged
Status in debianutils package in Ubuntu:
  New
Status in linux-base package in Ubuntu:
  New

Bug description:
  When testing development kernels I usually rely on the installkernel
  script either through the "make install" target of the Kernel source
  or manually. This used to work great on Ubuntu on Z.

  On Ubuntu 20.04 (freshly installed up to date) this fails however because
  /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the
  wrong kernel/initrd combination rendering the system unbootable.

  (with the correct modules already copied to 
/usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/)
  # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasda (3844).
  Done.
  run-parts: executing /etc/kernel/postinst.d/zz-zipl 
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)

[Touch-packages] [Bug 1888041] Re: default output is ignored and reset after reboot

2020-07-20 Thread Christoph

I am also affected. I have a monitor with audio output via HDMI/DP
connected to my Ubuntu 20.04 system. After reboot, default sink is set
back to other (USB audio) device automatically. Have to manually switch
it back to the HDMI/DP device in the settings manually. Editing
/etc/pulse/default.pa in any way (even the proposed one by vanvugt) has
no effect/is ignored at restart.

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

Title:
  default output is ignored and reset after reboot

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have lots of possible outputs, like speakers, wireless headset, and
  HDMI output. I select speakers as default, but on reboot it always
  select the wireless headset.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 18 01:59:22 2020
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7803
  dmi.board.asset.tag: Default string
  dmi.board.name: CROSSHAIR VI HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7803:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

2020-07-20 Thread Marian Gasparovic

Just for the record, last week I tried mitigation/workaround as
described in https://paste.ubuntu.com/p/JTB6vYbbkV/ on focal. It failed
exactly the same as without those changes. I reported back to Rafael.

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in linux-signed source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in bcache-tools source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Invalid
Status in linux-signed source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in bcache-tools source package in Groovy:
  Triaged
Status in linux source package in Groovy:
  Incomplete
Status in linux-signed source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Fix Released

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+subscriptions

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

[Touch-packages] [Bug 1886300] Re: rename.ul refuses to rename links that don't resolve (regression)

2020-07-20 Thread Mauricio Faria de Oliveira

Hi Seyeong!

Thank you for taking this LP bug. 
I'm setting myself as sponsor for once you have the debdiffs ready.

Please note that Eoan is EOL now, so please feel free to adjust it.

And it would be great to have this reported to Debian as well, since
it's an upstream bug/fix.

Please let me know if you'd like pointers about the procedure to report
bugs to the Debian Bug Tracking System (BTS).

cheers,
Mauricio

** Changed in: util-linux (Ubuntu Groovy)
   Status: In Progress => Confirmed

** Changed in: util-linux (Ubuntu Groovy)
 Assignee: Mauricio Faria de Oliveira (mfo) => Seyeong Kim (seyeongkim)

** Tags removed: sts-sponsor-volunteer
** Tags added: sts-sponsor-mfo

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

Title:
  rename.ul refuses to rename links that don't resolve (regression)

Status in util-linux package in Ubuntu:
  Confirmed
Status in util-linux source package in Eoan:
  Confirmed
Status in util-linux source package in Focal:
  Confirmed
Status in util-linux source package in Groovy:
  Confirmed

Bug description:
  rename.ul refuses to rename links that don't resolve.

  bionic rename.ul renames links whether or not they resolve (util-linux
  2.31.1-0.4ubuntu3.6).

  focal rename.ul refuses to rename links that don't resolve
  (regression) (util-linux 2.34-0.1ubuntu9).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: util-linux 2.34-0.1ubuntu9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jul  4 20:38:06 2020
  InstallationDate: Installed on 2020-04-05 (90 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  ProcEnviron:
   LC_TIME=en_DK.utf8
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code

sorry for bad habit that I miss-understanded before.
I revised it and put detail information there.

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

Title:
  [bionic]blutoothd segfault when you cancel the keyboard pairing during
  the dialog for pairing code

Status in OEM Priority Project:
  In Progress
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  In Progress
Status in bluez source package in Eoan:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in bluez source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  This patch is for this issue:
  steps: 
  1. pair bluetooth keyboard 
  2. see the dialog asking user input the code for pairing. 
  3. press "esc" to cancel it. 
  4. blutoothd segfault shows in dmesg after a while. 
  5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 
978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 
7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000]

  
  [Test Case]

   1. pair bluetooth keyboard
   2. see the dialog asking user input the code for pairing.
   3. press "esc" to cancel it.
   4. the bluetooth should still work to pair another bluetooth device.

  [Regression Potential]

   * This patch workaround the case that a queue node was created but
  not yet assigned function before user input pairing keycode. If the
  user cancel the paring before inputting pairing keycode then assign
  the function pointer a dummy 'direct_match'.

  * Bluetoothd responses to Bluetooth functions and "queue" is a shared
  common data structure, so in case of regression happens then blutoothd
  systemd service would be crashed.

   * We can verify this by operating add/remove BT devices to trigger
  queue operations.

   * I verified on target machine BIOS ID:0983 on BT mouse, keyboard,
  headset on pairing, remove and functionality checking.

  [Other Info]

   * NO.

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

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

[Touch-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code

** Description changed:

  [Impact]
  
-  * only impact Bionic machines because series after Bionic already
- included this patch.
+ This patch is for this issue:
+ steps: 
+ 1. pair bluetooth keyboard 
+ 2. see the dialog asking user input the code for pairing. 
+ 3. press "esc" to cancel it. 
+ 4. blutoothd segfault shows in dmesg after a while. 
+ 5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 
978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 
7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000]
+ 
  
  [Test Case]
  
   1. pair bluetooth keyboard
   2. see the dialog asking user input the code for pairing.
   3. press "esc" to cancel it.
   4. the bluetooth should still work to pair another bluetooth device.
  
  [Regression Potential]
  
-  * low, because the same patch from upstream is already there on Groovy,
- Focal and Eoan.
+  * This patch workaround the case that a queue node was created but not
+ yet assigned function before user input pairing keycode. If the user
+ cancel the paring before inputting pairing keycode then assign the
+ function pointer a dummy 'direct_match'.
+ 
+ * Bluetoothd responses to Bluetooth functions and "queue" is a shared
+ common data structure, so in case of regression happens then blutoothd
+ systemd service would be crashed.
+ 
+  * We can verify this by operating add/remove BT devices to trigger
+ queue operations.
+ 
+  * I verified on target machine BIOS ID:0983 on BT mouse, keyboard,
+ headset on pairing, remove and functionality checking.
  
  [Other Info]
  
   * NO.

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

Title:
  [bionic]blutoothd segfault when you cancel the keyboard pairing during
  the dialog for pairing code

Status in OEM Priority Project:
  In Progress
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  In Progress
Status in bluez source package in Eoan:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in bluez source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  This patch is for this issue:
  steps: 
  1. pair bluetooth keyboard 
  2. see the dialog asking user input the code for pairing. 
  3. press "esc" to cancel it. 
  4. blutoothd segfault shows in dmesg after a while. 
  5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 
978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 
7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000]

  
  [Test Case]

   1. pair bluetooth keyboard
   2. see the dialog asking user input the code for pairing.
   3. press "esc" to cancel it.
   4. the bluetooth should still work to pair another bluetooth device.

  [Regression Potential]

   * This patch workaround the case that a queue node was created but
  not yet assigned function before user input pairing keycode. If the
  user cancel the paring before inputting pairing keycode then assign
  the function pointer a dummy 'direct_match'.

  * Bluetoothd responses to Bluetooth functions and "queue" is a shared
  common data structure, so in case of regression happens then blutoothd
  systemd service would be crashed.

   * We can verify this by operating add/remove BT devices to trigger
  queue operations.

   * I verified on target machine BIOS ID:0983 on BT mouse, keyboard,
  headset on pairing, remove and functionality checking.

  [Other Info]

   * NO.

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

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

[Touch-packages] [Bug 1861177] Re: seccomp_rule_add is very slow

2020-07-20 Thread Ioanna Alifieraki

# autopkgtest regression in EOAN

There is an autopkgtest regression in EOAN on ppc64el for systemd package.
The regression is caused by the 'upstream' test.
As it's shown here 
http://autopkgtest.ubuntu.com/packages/s/systemd/eoan/ppc64el this test
has always been failing since systemd version 240-6ubuntu5 and can be ignored.

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

Title:
  seccomp_rule_add is very slow

Status in snapd:
  Invalid
Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Xenial:
  Fix Committed
Status in libseccomp source package in Bionic:
  Fix Committed
Status in libseccomp source package in Eoan:
  Fix Committed
Status in libseccomp source package in Focal:
  Fix Committed
Status in libseccomp source package in Groovy:
  Fix Released

Bug description:
  [IMPACT]
  There is a known and patched issue with version 2.4 of libseccomp where 
certain operations have a large performance regression. This is causing some 
packages that use libseccomp such as container orchestration systems to 
occasionally time out or otherwise fail under certain workloads.

  Please consider porting the patch into the various Ubuntu versions
  that have version 2.4 of libseccomp and into the backports. The
  performance patch from version 2.5 (yet to be released) applies
  cleanly on top of the 2.4 branch of libseccomp.

  For more information, and for a copy of the patch (which can also be
  cherry picked from the upstream libseccomp repos) see the similar
  Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913

  Upstream issue : https://github.com/seccomp/libseccomp/issues/153
  Upstream fix : https://github.com/seccomp/libseccomp/pull/180/

  [Test Case]

  For this test case we use Docker on Ubuntu Groovy (20.10) :

  --> Current libseccomp version
  #dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu3 
 amd64high level interface to Linux seccomp filter

  ## pull ubuntu image
  # docker pull ubuntu
  ## create a container
  # docker run --name test_seccomp -it 74435f89ab78 /bin/bash

  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m10,319s
  user  0m0,018s
  sys   0m0,033s

  
  --> Patched libseccomp version

  # dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu4 
 amd64high level interface to Linux seccomp filter

  # docker start test_seccomp
  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m3,650s
  user  0m0,025s
  sys   0m0,028s

  [Regression Potential]

  The first of the 2 patches cleans up the code that adds rules to a
  single filter without changing the logic of the code. The second patch
  introduces the idea of shadow transactions. On a successful
  transaction commit the old transaction checkpoint is preserved and is
  brought up to date with the current filter. The next time a new
  transaction starts, it checks is the a shadow transaction exist and if
  so the shadow is used instead of creating a new checkpoint from
  scratch [1]. This is the patch that mitigates the performance
  regression. Any potential regression will involve the parts of the
  code that add rules to filters and/or the code that creates and checks
  the shadow transactions.

  
  [Other]

  Affected releases : Groovy, Focal, Eoan, Bionic, Xenial.

  [1]
  
https://github.com/seccomp/libseccomp/pull/180/commits/bc3a6c0453b0350ee43e4925482f705a2fbf5a4d

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

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

[Touch-packages] [Bug 1861177] Re: seccomp_rule_add is very slow

2020-07-20 Thread Ioanna Alifieraki

#VERIFICATION EOAN

---> Old version
# dpkg -l | grep libseccomp
ii  libseccomp2:amd64  2.4.3-1ubuntu3.19.10.2amd64  high level interface to 
Linux seccomp filter


# for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
MAX TIME : 9.374s

---> New version

# dpkg -l | grep libseccomp
ii  libseccomp2:amd64 2.4.3-1ubuntu3.19.10.3  amd64   high level interface to 
Linux seccomp filter


# for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
MAX TIME : 2.009s

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

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

Title:
  seccomp_rule_add is very slow

Status in snapd:
  Invalid
Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Xenial:
  Fix Committed
Status in libseccomp source package in Bionic:
  Fix Committed
Status in libseccomp source package in Eoan:
  Fix Committed
Status in libseccomp source package in Focal:
  Fix Committed
Status in libseccomp source package in Groovy:
  Fix Released

Bug description:
  [IMPACT]
  There is a known and patched issue with version 2.4 of libseccomp where 
certain operations have a large performance regression. This is causing some 
packages that use libseccomp such as container orchestration systems to 
occasionally time out or otherwise fail under certain workloads.

  Please consider porting the patch into the various Ubuntu versions
  that have version 2.4 of libseccomp and into the backports. The
  performance patch from version 2.5 (yet to be released) applies
  cleanly on top of the 2.4 branch of libseccomp.

  For more information, and for a copy of the patch (which can also be
  cherry picked from the upstream libseccomp repos) see the similar
  Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913

  Upstream issue : https://github.com/seccomp/libseccomp/issues/153
  Upstream fix : https://github.com/seccomp/libseccomp/pull/180/

  [Test Case]

  For this test case we use Docker on Ubuntu Groovy (20.10) :

  --> Current libseccomp version
  #dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu3 
 amd64high level interface to Linux seccomp filter

  ## pull ubuntu image
  # docker pull ubuntu
  ## create a container
  # docker run --name test_seccomp -it 74435f89ab78 /bin/bash

  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m10,319s
  user  0m0,018s
  sys   0m0,033s

  
  --> Patched libseccomp version

  # dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu4 
 amd64high level interface to Linux seccomp filter

  # docker start test_seccomp
  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m3,650s
  user  0m0,025s
  sys   0m0,028s

  [Regression Potential]

  The first of the 2 patches cleans up the code that adds rules to a
  single filter without changing the logic of the code. The second patch
  introduces the idea of shadow transactions. On a successful
  transaction commit the old transaction checkpoint is preserved and is
  brought up to date with the current filter. The next time a new
  transaction starts, it checks is the a shadow transaction exist and if
  so the shadow is used instead of creating a new checkpoint from
  scratch [1]. This is the patch that mitigates the performance
  regression. Any potential regression will involve the parts of the
  code that add rules to filters and/or the code that creates and checks
  the shadow transactions.

  
  [Other]

  Affected releases : Groovy, Focal, Eoan, Bionic, Xenial.

  [1]
  
https://github.com/seccomp/libseccomp/pull/180/commits/bc3a6c0453b0350ee43e4925482f705a2fbf5a4d

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

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

[Touch-packages] [Bug 1888077] Re: No startup sound played with gnome-session-canberra

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

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

Title:
  No startup sound played with gnome-session-canberra

Status in libcanberra package in Ubuntu:
  New

Bug description:
  Tested on Xubuntu 20.04 with gnome-session-canberra and yaru-theme-
  sound packages installed

  The gnome-session-canberra package has a /usr/share/gnome/autostart
  /libcanberra-login-sound.desktop but it will not run. I disabled all
  of the below entries in the file and it still wouldn't run.

  OnlyShowIn=GNOME;Unity;
  AutostartCondition=GSettings org.gnome.desktop.sound event-sounds
  X-GNOME-Autostart-Phase=Application
  X-GNOME-Provides=login-sound
  X-GNOME-Autostart-enabled=false
  NoDisplay=true

  The shutdown script /usr/share/gnome/shutdown/libcanberra-logout-
  sound.sh in the same package worked fine.

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

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

[Touch-packages] [Bug 1888091] Re: Deform switch in the Livepatch tab

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Deform switch in the Livepatch tab

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  When the user isn't signed in, the switch looks deform / squeezed. See
  the attached screenshot.

  Maybe the blue spinner is somehow calculated into the padding and when
  the spinner is gone (after "Checking availability"), the padding does
  not match and the switch gets squeezed.

  This is only a visual bug, non critical, but should be low hanging
  fruit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1888091/+subscriptions

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

[Touch-packages] [Bug 1847597] Re: gnome-control-center cannot access google account

GNOME isn't the default desktop on Ubuntu 16.04 and there is only one
bug with 3 affected users, which means it's low priority for a fix in
that serie

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

Title:
  gnome-control-center cannot access google account

Status in gnome-online-accounts:
  New
Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  Good morning,

  If I run "gnome-control-center online-accounts" from the terminal and
  trying to add a Google account, I get this error: "Sign in with Google
  is temporarily disabled for this app. This app has not been verified
  yet by Google in order to use Google sign in". On the web, Google
  suggests to contact you, so here I am. Can you fix please? I would use
  my drive folders on my ubuntu 16.04. Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1847597/+subscriptions

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

[Touch-packages] [Bug 1837318] Re: Cannot store password. Password prompt never ends

Thank you for your bug report and sorry for the lack of response, there
is no dedicated maintainer for that component on Ubuntu, you would
probably have a better chance by reporting directly upstream
https://gitlab.gnome.org/GNOME/libsecret/

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

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

Title:
  Cannot store password. Password prompt never ends

Status in libsecret package in Ubuntu:
  Confirmed

Bug description:
  Cannot store password using secret-tool.

  I do the following:

  $ secret-tool store --label='MyService' service myservice
  Password: 
  sf
  ^C

  The thing is when I hit ENTER and inserting the password, the password
  prompt never end. So I have to hit Ctrl+C to quit the program, and
  hence the password is not saved.

  Here are my system details:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  $ apt-cache policy libsecret-tools
  libsecret-tools:
Installed: 0.18.6-1
Candidate: 0.18.6-1
Version table:
   *** 0.18.6-1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code

Alex, did you read comment 7? 'low' isn't responding to what the
regression potential should provide, it's there to describe what impact
the change could have to know on what to focus the testing

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

Title:
  [bionic]blutoothd segfault when you cancel the keyboard pairing during
  the dialog for pairing code

Status in OEM Priority Project:
  In Progress
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  In Progress
Status in bluez source package in Eoan:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in bluez source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * only impact Bionic machines because series after Bionic already
  included this patch.

  [Test Case]

   1. pair bluetooth keyboard
   2. see the dialog asking user input the code for pairing.
   3. press "esc" to cancel it.
   4. the bluetooth should still work to pair another bluetooth device.

  [Regression Potential]

   * low, because the same patch from upstream is already there on
  Groovy, Focal and Eoan.

  [Other Info]

   * NO.

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

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

[Touch-packages] [Bug 1886300] Re: rename.ul refuses to rename links that don't resolve (regression)

2020-07-20 Thread Seyeong Kim

** Changed in: util-linux (Ubuntu Eoan)
 Assignee: (unassigned) => Seyeong Kim (seyeongkim)

** Changed in: util-linux (Ubuntu Focal)
 Assignee: (unassigned) => Seyeong Kim (seyeongkim)

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

Title:
  rename.ul refuses to rename links that don't resolve (regression)

Status in util-linux package in Ubuntu:
  In Progress
Status in util-linux source package in Eoan:
  Confirmed
Status in util-linux source package in Focal:
  Confirmed
Status in util-linux source package in Groovy:
  In Progress

Bug description:
  rename.ul refuses to rename links that don't resolve.

  bionic rename.ul renames links whether or not they resolve (util-linux
  2.31.1-0.4ubuntu3.6).

  focal rename.ul refuses to rename links that don't resolve
  (regression) (util-linux 2.34-0.1ubuntu9).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: util-linux 2.34-0.1ubuntu9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jul  4 20:38:06 2020
  InstallationDate: Installed on 2020-04-05 (90 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  ProcEnviron:
   LC_TIME=en_DK.utf8
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1887964] Re: VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume group vg01 Volume group "vg01" not found

2020-07-20 Thread veribaka

I thought so too initially, but the proposed solution doesn't work in my
case, and also I get a different error message booting up.

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

Title:
  VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume
  group vg01 Volume group "vg01" not found

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

Bug description:
  After upgrading a laptop configured with LVM from 18.04 to 20.04 the volume 
group is no longer found.
  During boot the console shows

  Volume group "vg01" not found
  Cannot process volume group vg01
  Gave up waiting for suspend/resume device
  ALERT! /dev/mapper/vg01-root does not exist. Dropping to a shell!

  Attached dist-upgrade logs and console output.

  Tried the "vgck --updatemetadata vg01" recommended on this bug report:
  https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381

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

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

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

This looks like a hardware or driver problem with the Radeon Pro WX
7100. Your logs show two issues:

1. Xorg logs that the monitor is being repeatedly redetected. So it
sounds like the monitor is not plugged in properly. Maybe try a new
monitor cable.

2. The kernel is logging more serious issues:

[  107.569355] amdgpu :0a:00.0: GPU fault detected: 146 0x0c38480c for 
process mksReplay pid 2764 thread main-mks pid 2772
[  107.569358] amdgpu :0a:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   
0x0030C387
[  107.569359] amdgpu :0a:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
[  107.569360] amdgpu :0a:00.0: VM fault (0x0c, vmid 4, pasid 32785) at 
page 3195783, read from 'TC4' (0x54433400) (72)
[  107.569365] amdgpu :0a:00.0: GPU fault detected: 146 0x0c38880c for 
process mksReplay pid 2764 thread main-mks pid 2772
[  107.569366] amdgpu :0a:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   
0x0030C38E
[  107.569367] amdgpu :0a:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0808400C
[  107.569368] amdgpu :0a:00.0: VM fault (0x0c, vmid 4, pasid 32785) at 
page 3195790, read from 'TC7' (0x54433700) (132)
[  107.597584] amdgpu :0a:00.0: GPU fault detected: 146 0x0c38480c for 
process mksReplay pid 2764 thread main-mks pid 2772
[  107.597587] amdgpu :0a:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   
0x0030C387
[  107.597588] amdgpu :0a:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0E04800C
[  107.597590] amdgpu :0a:00.0: VM fault (0x0c, vmid 7, pasid 32785) at 
page 3195783, read from 'TC4' (0x54433400) (72)
[  107.597595] amdgpu :0a:00.0: GPU fault detected: 146 0x0c38880c for 
process mksReplay pid 2764 thread main-mks pid 2772
[  107.597596] amdgpu :0a:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   
0x0030C38D
[  107.597597] amdgpu :0a:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0E04400C
[  107.597598] amdgpu :0a:00.0: VM fault (0x0c, vmid 7, pasid 32785) at 
page 3195789, read from 'TC5' (0x54433500) (68)
[

** Tags added: amdgpu

** Summary changed:

- Xorg freeze
+ [amdgpu] Xorg freeze

** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)

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

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

Title:
  [amdgpu] Xorg freeze

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

Bug description:
  I have Radeon Pro WX 7100. It hangs twice a day.

  I narrow-downed this issue to the fan speed lock. After reboot, it
  always runs on 18%, no matter of the load. If I install Radeon Profile
  and force fan to 100% and then turn auto fan configuration, then fan
  reacts on the load.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-62-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 09:15:03 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 7100] 
[1002:67c4] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 
7100] [1002:0b0d]
  InstallationDate: Installed on 2020-06-29 (20 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=2b68d049-e85f-47ab-97d9-5632f225b71b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7803
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7803:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1

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

2020-07-20 Thread Maksym Wezdecki

Public bug reported:

I have Radeon Pro WX 7100. It hangs twice a day.

I narrow-downed this issue to the fan speed lock. After reboot, it
always runs on 18%, no matter of the load. If I install Radeon Profile
and force fan to 100% and then turn auto fan configuration, then fan
reacts on the load.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-62-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 20 09:15:03 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Very infrequently
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 7100] 
[1002:67c4] (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 
7100] [1002:0b0d]
InstallationDate: Installed on 2020-06-29 (20 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=2b68d049-e85f-47ab-97d9-5632f225b71b ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/17/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 7803
dmi.board.asset.tag: Default string
dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7803:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic freeze ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I have Radeon Pro WX 7100. It hangs twice a day.

  I narrow-downed this issue to the fan speed lock. After reboot, it
  always runs on 18%, no matter of the load. If I install Radeon Profile
  and force fan to 100% and then turn auto fan configuration, then fan
  reacts on the load.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-62-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 09:15:03 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 7100] 
[1002:67c4] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 
7100] [1002:0b0d]
  InstallationDate: Installed on 2020-06-29 (20 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=2b68d049-e85f-47ab-97d9-5632f225b71b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7803
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string

[Touch-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code

Sorry, 
the debugging and debdiff was done on the target machine so that the email ID 
was missed.

This attached new debdiff also included the patch and lp number
information in the changelog.

And also updated the truncated description.

** Patch added: "bluez_5.48-0ubuntu3.5.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1887910/+attachment/5394261/+files/bluez_5.48-0ubuntu3.5.debdiff

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

Title:
  [bionic]blutoothd segfault when you cancel the keyboard pairing during
  the dialog for pairing code

Status in OEM Priority Project:
  In Progress
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  In Progress
Status in bluez source package in Eoan:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in bluez source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * only impact Bionic machines because series after Bionic already
  included this patch.

  [Test Case]

   1. pair bluetooth keyboard
   2. see the dialog asking user input the code for pairing.
   3. press "esc" to cancel it.
   4. the bluetooth should still work to pair another bluetooth device.

  [Regression Potential]

   * low, because the same patch from upstream is already there on
  Groovy, Focal and Eoan.

  [Other Info]

   * NO.

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

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

[Touch-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code

** Description changed:

  [Impact]
  
-  * only impact Bionic machines because series after Bionic already
+  * only impact Bionic machines because series after Bionic already
  included this patch.
  
  [Test Case]
  
-  1. pair bluetooth keyboard
-  2. see the dialog asking user input the code for pairing.
-  3. press "esc" to cancel it.
-  4. the bluetooth should still work to pair another bluetooth device.
+  1. pair bluetooth keyboard
+  2. see the dialog asking user input the code for pairing.
+  3. press "esc" to cancel it.
+  4. the bluetooth should still work to pair another bluetooth device.
  
  [Regression Potential]
  
-  * low, becuase
+  * low, because the same patch from upstream is already there on Groovy,
+ Focal and Eoan.
  
  [Other Info]
  
-  * NO.
+  * NO.

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

Title:
  [bionic]blutoothd segfault when you cancel the keyboard pairing during
  the dialog for pairing code

Status in OEM Priority Project:
  In Progress
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  In Progress
Status in bluez source package in Eoan:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in bluez source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * only impact Bionic machines because series after Bionic already
  included this patch.

  [Test Case]

   1. pair bluetooth keyboard
   2. see the dialog asking user input the code for pairing.
   3. press "esc" to cancel it.
   4. the bluetooth should still work to pair another bluetooth device.

  [Regression Potential]

   * low, because the same patch from upstream is already there on
  Groovy, Focal and Eoan.

  [Other Info]

   * NO.

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

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

[Touch-packages] [Bug 1888167] Re: Unable to Login

You seem to be describing multiple problems. Please choose a single
problem for this bug to be about.

** Tags added: amdgpu

** Summary changed:

- Unable to Login
+ [amdgpu] Unable to Login

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

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

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

Title:
  [amdgpu] Unable to Login

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Currently I'm using a 4K AOC monitor on 20.04 LTS with a DisplayPort
  cable.

  Normally, there is a gear widget in the lower right corner of the
  screen that allows me to select between XServer and Wayland. This gear
  is missing. Switching to an HDMI cable corrects the issue but doesn't
  allow the display to work at higher than 30hz.

  Additionally, attempting to login throws a session error which hangs.
  You need to switch to a separate tty to do anything.

  The specific error is a popup right after entering your password.

  This is the text:

  Error found when loading /home/user/.xprofile:
  warning: output HDMI-A-1 not found: ignoring
  X Error of failed request: BadRROutput (invalid Output parameter)
  Major opcode of failed request: 140 (RANDR)
  Minor opcode of failed request: 15 (RRGetOutputProperty)
  Serial number of failed request: 37
  Current serial number in output stream: 37

  As a result the session will not be configured correctly.
  You should fix the problem as soon as feasible. 

  Mouse and Keyboard are fully unresponsive except for the magic keys
  (switching TTY and various other kernel functions).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 19 17:55:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 
450/455/460/555/555X/560/560X] [1002:67ef] (rev e5) (prog-if 00 [VGA 
controller])
 Subsystem: XFX Pine Group Inc. Polaris 21 XL [Radeon RX 560D] [1682:956d]
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c6) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Raven Ridge [Radeon Vega Series / Radeon 
Vega Mobile Series] [1043:876b]
  InstallationDate: Installed on 2020-04-26 (84 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=/dev/mapper/hostname--vg-base ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2202
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2202:bd07/14/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  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/mutter/+bug/1888167/+subscriptions

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

[Touch-packages] [Bug 1888120] Re: Headphones detected like Speakers and Volume Problem

Please choose a single problem for this bug to be about and open a new
bug for the other.

Please also clarify what you mean by "headphones like speakers"?

** Tags added: focal

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

** Package changed: gnome-shell (Ubuntu) => 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/1888120

Title:
  Headphones detected like Speakers and Volume Problem

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I bought a Kyus Headphones, this model exactly:
  https://www.pccomponentes.com/krom-kyus-auriculares-gaming

  and when I go to Settings/Sound in Ubuntu 20.04 LTS, I can watch
  Speakers - USB Audio Device, not Headphones.

  In Windows if the system detect the headphones like speakers, the
  sound is louder and upset, I think that Ubuntu should have a similar
  problem.

  Another problem is the control volume. When I change the volume using
  a key combination to up volume and down volume. If I up the volume
  when I have got 0 level, the volume doesn't ear in the two first steps
  that I pulsed UP volume. Other problem is, that if I press up volume
  it change a lot with only one press of up volume. This generate the
  situation of volume too low and when press up, the volume is too high.

  
  Thanks for your time.

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

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

[Touch-packages] [Bug 1888142] Re: notification for some apps cannot be disabled in ubuntu 20.04 release

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

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

Title:
  notification for some apps cannot be disabled in ubuntu 20.04 release

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I tried to disable the pop-up notification for Dropbox, which shows
  some files were changed once I saved my file in an app (that sits
  inside Dropbox folder).

  Turning off the notification in the notification center does not stop
  the pop-ups from showing. Turning on do not disturb does help,
  however.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: rcraid
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 01:58:10 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   rcraid, 8.1.0, 5.4.0-37-generic, x86_64: installed
   rcraid, 8.1.0, 5.4.0-39-generic, x86_64: installed
   rcraid, 8.1.0, 5.4.0-40-generic, x86_64: installed
   xpad, 0.4, 5.4.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XTX [Radeon Vega Frontier 
Edition] [1002:6863] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XTX [Radeon Vega 
Frontier Edition] [1002:6b76]
  InstallationDate: Installed on 2020-04-25 (85 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. X570 I AORUS PRO WIFI
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=a46fdd55-3a51-4c71-b5a5-cb35298c18e9 ro quiet splash 
modprobe.blacklist=ahci vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12e
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 I AORUS PRO WIFI
  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.:bvrF12e:bd03/06/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570IAORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570IAORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 I AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: -CF
  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.1.3~kisak1~f
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.1.3~kisak1~f
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  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/gnome-shell/+bug/1888142/+subscriptions

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

[Touch-packages] [Bug 1888119] Re: Problem with USB Headset (Headphones + Micro)

Also, if you want each application to use a different sound card then
it's the responsibility of the application to offer settings for that.
And you must configure it in the application.

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

Title:
  Problem with USB Headset (Headphones + Micro)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I bought a Kyus Headphones, this model exactly:
  https://www.pccomponentes.com/krom-kyus-auriculares-gaming

  and when I connect the USB Headphones to my computer, the sound of
  Ubuntu 20.04 disappear.

  The problem is that Ubuntu 20.04 is not detecting correctly the Sound
  Card. I haven't got any option in Settings to change the Sound Card I
  am using.

  I needed to install the program PulseAudio to configure which sound
  card I want to choose in each applications.

  We want an option to watch an advanced settings menu to solve this
  problems in Ubuntu.

  Another option is that Ubuntu detects correctly the sound card in each
  moment and if I connect my headphones, the sound card change to USB
  Audio Controller. Currently when I connect my headphones, the sound
  card selected is Family 17h Audio controller (I think that this is the
  Jack Audio controller), and that is not the correct sound card because
  I am not using Jack, I am using USB connection.

  I have got another audio controller HDMI Audio Controller (GPU Audio
  controller of Nvidia).

  Thanks for your help.

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

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

[Touch-packages] [Bug 1888119] Re: Problem with USB Headset (Headphones + Micro)

You can change the sound card in use via Settings > Sound.

And if you want connecting of USB to not automatically change the
settings then you will need to edit /etc/pulse/default.pa and comment
out:

  load-module module-switch-on-connect

Then restart.

Is there any problem remaining after you do that?

** Tags added: focal

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

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

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

Title:
  Problem with USB Headset (Headphones + Micro)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I bought a Kyus Headphones, this model exactly:
  https://www.pccomponentes.com/krom-kyus-auriculares-gaming

  and when I connect the USB Headphones to my computer, the sound of
  Ubuntu 20.04 disappear.

  The problem is that Ubuntu 20.04 is not detecting correctly the Sound
  Card. I haven't got any option in Settings to change the Sound Card I
  am using.

  I needed to install the program PulseAudio to configure which sound
  card I want to choose in each applications.

  We want an option to watch an advanced settings menu to solve this
  problems in Ubuntu.

  Another option is that Ubuntu detects correctly the sound card in each
  moment and if I connect my headphones, the sound card change to USB
  Audio Controller. Currently when I connect my headphones, the sound
  card selected is Family 17h Audio controller (I think that this is the
  Jack Audio controller), and that is not the correct sound card because
  I am not using Jack, I am using USB connection.

  I have got another audio controller HDMI Audio Controller (GPU Audio
  controller of Nvidia).

  Thanks for your help.

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

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

[Touch-packages] [Bug 1888120] [NEW] Headphones detected like Speakers and Volume Problem

You have been subscribed to a public bug:

I bought a Kyus Headphones, this model exactly:
https://www.pccomponentes.com/krom-kyus-auriculares-gaming

and when I go to Settings/Sound in Ubuntu 20.04 LTS, I can watch
Speakers - USB Audio Device, not Headphones.

In Windows if the system detect the headphones like speakers, the sound
is louder and upset, I think that Ubuntu should have a similar problem.

Another problem is the control volume. When I change the volume using a
key combination to up volume and down volume. If I up the volume when I
have got 0 level, the volume doesn't ear in the two first steps that I
pulsed UP volume. Other problem is, that if I press up volume it change
a lot with only one press of up volume. This generate the situation of
volume too low and when press up, the volume is too high.


Thanks for your time.

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


** Tags: focal
-- 
Headphones detected like Speakers and Volume Problem
https://bugs.launchpad.net/bugs/1888120
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio in Ubuntu.

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

[Touch-packages] [Bug 1888119] [NEW] Problem with USB Headset (Headphones + Micro)

You have been subscribed to a public bug:

I bought a Kyus Headphones, this model exactly:
https://www.pccomponentes.com/krom-kyus-auriculares-gaming

and when I connect the USB Headphones to my computer, the sound of
Ubuntu 20.04 disappear.

The problem is that Ubuntu 20.04 is not detecting correctly the Sound
Card. I haven't got any option in Settings to change the Sound Card I am
using.

I needed to install the program PulseAudio to configure which sound card
I want to choose in each applications.

We want an option to watch an advanced settings menu to solve this
problems in Ubuntu.

Another option is that Ubuntu detects correctly the sound card in each
moment and if I connect my headphones, the sound card change to USB
Audio Controller. Currently when I connect my headphones, the sound card
selected is Family 17h Audio controller (I think that this is the Jack
Audio controller), and that is not the correct sound card because I am
not using Jack, I am using USB connection.

I have got another audio controller HDMI Audio Controller (GPU Audio
controller of Nvidia).

Thanks for your help.

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


** Tags: focal
-- 
Problem with USB Headset (Headphones + Micro)
https://bugs.launchpad.net/bugs/1888119
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio in Ubuntu.

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

[Touch-packages] [Bug 1888108] Re: Fresh install 20.04

** Changed in: xorg (Ubuntu)
   Status: Fix Released => Invalid

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

Title:
  Fresh install 20.04

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  My Graphics are like a slide show.

  Its almost as if the display drivers are not installed?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sat Jul 18 22:08:11 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v3/4th Gen Core Processor Integrated 
Graphics Controller [17aa:30a3]
  InstallationDate: Installed on 2020-07-17 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 10AB004DUS
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=cd7df6ea-b877-481a-9eee-6d5e2b5d770a ro quiet splash nomodeset 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTB9AUS
  dmi.board.name: SHARKBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  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:bvnLENOVO:bvrFBKTB9AUS:bd11/13/2015:svnLENOVO:pn10AB004DUS:pvrThinkCentreM93p:rvnLENOVO:rnSHARKBAY:rvrSDK0E50510WIN:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ThinkCentre M93p
  dmi.product.name: 10AB004DUS
  dmi.product.sku: LENOVO_MT_10AB
  dmi.product.version: ThinkCentre M93p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 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/1888108/+subscriptions

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

[Touch-packages] [Bug 1888065] Re: Screen dies/black after changing display orientation or enabling fractional scaling

This sounds like bug 1873403 and you probably just needed to update the
system:

  sudo apt update
  sudo apt full-upgrade
  Reboot.

Does comment #2 mean the issue is gone for good?


** Tags added: nvidia xrandr-scaling

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

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

** Summary changed:

- Screen dies/black after changing display orientation or enabling fractional 
scaling
+ [nvidia] Screen dies/black after changing display orientation or enabling 
fractional scaling

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

Title:
  [nvidia] Screen dies/black after changing display orientation or
  enabling fractional scaling

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to 20.04 over a month ago and it's been working fine. I
  have one monitor (external). I tried turning on fractional scaling in
  the display settings and the screen immediately turned black. I
  waited, expecting the "confirm changes" prompt to timeout and restore
  the display. It never did.

  Next I hard rebooted, but as soon as I'd entered my password to login,
  the screen went black again. Tried this a few more times. I then
  booted to a root console and `apt update/upgrade` to get all updates.
  Rebooting, I had the same issue on logging in. I then used Ctrl+Alt+F1
  to get a virtual console, then back to F2, and a few other things. At
  some point I was able to log back in.

  Foolishly I assumed the issue was just with fractional scaling, and
  back in Display settings I for some reason decided to experiment
  further and flipped the display orientation to portrate. Immediately I
  got a black screen and ended back in the same reboot loop, always
  getting a black screen as soon as I tried to log back in. Searching
  online I couldn't seem to find a way to revert the display
  orientation. From another virtual console I was unable to run xrandr
  or start a wayland session to get to the settings panel. To do that I
  was trying to run:

dbus-run-session -- gnome-shell --display-server --wayland

  But that's just something I found on the Web, I have no idea what I'm
  doing there. It just gave the error:

  (gnome-shell:) mutter-warning: **:  Failed to 
open gpu 'dev/dri/card0 Failed to activate universal planes: Operation not 
permitted
  (gnome-shell:) mutter-warning: **:  Failed to 
create backend: No GPUs found

  Eventually I found a suggestion on the Web to unplug the cable to the
  display, and after experimenting with that a bit and switching between
  virtual consoles, at some point it was logged in with a working
  display ... well, sort of. The colors and icons are weird like it's
  lost theming or something. Going into the Display settings it seems
  that the orientation has also been reset to landscape.

  I'm filing this bug before restarting the machine so I can report the
  system scan it has taken. At this point I've no idea whether I'll be
  able to log back in again after a reboot. I'll try that now.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..21.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:21: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.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Jul 18 17:21:56 2020
  DistUpgraded: 2020-04-29 16:04:33,258 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.4.0-37-generic, x86_64: installed
   nvidia, 435.21, 5.4.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP107GL [Quadro P400] [10de:1cb3] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GP107GL [Quadro P400] [1028:11be]
  InstallationDate: Installed on 2019-11-03 (257 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Z4 G4 Workstation
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=9586ebe6-be5f-4a32-b960-e129e9d98eb9 ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to focal on 2020-04-29 (80

[Touch-packages] [Bug 1888088] Re: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling