[Touch-packages] [Bug 1926934] Re: gdb batch calls time out on armhf

2021-05-03 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=27810.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2021-05-03T06:23:31+00:00 Matthias Klose wrote:

seening this with gdb 10.2 and gcc 10.3.0 on Ubuntu 21.04, using glibc
2.33, binutils 2.26.1 and gcc 10.3.0.

A lot of tests in the guality test suite time out after 300 seconds (the
default dejagnu timeout). These tests, like pr36728-1.c run ok on other
architectures (and fail), but timeout on armhf.

for gcc,

RUNTESTFLAGS=guality.exp=pr36728-1.c make -e -C /gcc check-gcc


The last "successful" gcc-10 build is from April, using a gdb snapshot taken 
from the gdb-10 branch on March 05 2021.

Architectures like x86_64, powerpc64le, s390x, aarch64 are not affected.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1926934/comments/1


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

** Changed in: gdb
   Importance: Unknown => Medium

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

Title:
  gdb batch calls time out on armhf

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  New

Bug description:
  seen when trying to build the gcc-10, or gcc-snapshot packages.  A lot
  of tests in the guality test suite time out after 300 seconds (the
  default dejagnu timeout). These tests, like pr36728-1.c run ok on
  other architectures (and fail), but timeout on armhf.

  Seen in impish with gcc-10 and gcc-snapshot.

  Trying to run the gdb 10.2 tests on both hirsute and impish, I see a
  lot of timeouts as well.

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

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


[Touch-packages] [Bug 1926840] Re: Display/Graphics bug

2021-05-03 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1924624 ***
https://bugs.launchpad.net/bugs/1924624

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1924624, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1924624
   After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (Gen7: Haswell/Ivy 
Bridge) a lot of glitches render screen unusable

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

Title:
  Display/Graphics bug

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu was perfect before updating it.

  I ran the command sudo apt update. After that, my computer graphics
  have become choppy. I have attached a screenshot of the problem.

  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200
  v2/3rd Gen Core processor Graphics Controller (rev 09)

  Intel® HD Graphics 2500 (IVB GT1)
  GNOME version 3.36.8
  Windowing system X11

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  1 19:20:51 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.8.0-48-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[1028:0577]
  InstallationDate: Installed on 2021-02-09 (80 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. OptiPlex 7010
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=8e9a679a-a7d5-4d98-8a50-1e4ab130a8d4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 12/21/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 0WR7PY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd12/21/2015:br4.6:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0WR7PY:rvrA03:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 7010
  dmi.product.sku: OptiPlex 7010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/+bug/1926840/+subscriptions

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


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

2021-05-03 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1924624 ***
https://bugs.launchpad.net/bugs/1924624

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1924624, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1924624
   After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (Gen7: Haswell/Ivy 
Bridge) a lot of glitches render screen unusable

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  the screem freezes and when i open a couple programs many bugs start
  to show up

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 30 01:09:02 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback, 0.12.3, 5.8.0-48-generic, x86_64: installed
   v4l2loopback, 0.12.3, 5.8.0-50-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:1b7d]
  InstallationDate: Installed on 2020-12-11 (139 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:b725 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. USB Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. Z450LA
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=5f3995ba-8da9-4c41-9bf9-e59240f2ca6c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2015
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Z450LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Z450LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrZ450LA.204:bd08/12/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnZ450LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ450LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: Z
  dmi.product.name: Z450LA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/+bug/1926688/+subscriptions

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


[Touch-packages] [Bug 1926248] Re: display scrambled - all packages

2021-05-03 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1924624 ***
https://bugs.launchpad.net/bugs/1924624

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1924624, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1924624
   After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (Gen7: Haswell/Ivy 
Bridge) a lot of glitches render screen unusable

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

Title:
  display scrambled - all packages

Status in xorg package in Ubuntu:
  New

Bug description:
  shortly after switching to kernel 5.8.0-50 on Apr 16, I got progressively 
worse display scrambling on all programs. Wrote to ubuntuforums.org Apr 19 but 
found no resolution. Thinking it was that kernel, I ran on 5.8.0-49 for a day 
without problem, then it too started the same display glitches. The problem 
progressed so far that I did a fresh system re-install on Apr 23. After, with 
the default kernel, 5.8.0-50, scrambling was worse than ever, almost unusable. 
Fortunately, the second kernel offered was 5.8.0-43. I have run on that kernel 
for 3 days now with no sign of the scrambling issue. 
  The attached png shows static image corruption examples. The more dramatic 
strobing, spontaneous jumping from window to window, window re-mapping, video 
corruption etc., I was unable to capture.
  Running Ubuntu 20.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 21:48:37 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [1028:0622]
  InstallationDate: Installed on 2021-04-23 (3 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Inspiron 3847
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic 
root=UUID=0fa2ade9-fdd6-4cfa-a153-0de2be1f39ae ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/29/2015
  dmi.bios.release: 65.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 088DT1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd06/29/2015:br65.8:svnDellInc.:pnInspiron3847:pvr:rvnDellInc.:rn088DT1:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 3847
  dmi.product.sku: 0622
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/+bug/1926248/+subscriptions

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


[Touch-packages] [Bug 1926333] Re: [nvidia] System freeze after power saving mode

2021-05-03 Thread Daniel van Vugt
Thanks for the bug report. Next time the problem happens please run:

  journalctl -b0 > journal.txt

or if you had to reboot then run:

  journalctl -b-1 > prevjournal.txt

and attach the resulting text file here.


** Summary changed:

- Xorg freeze
+ [nvidia] System freeze after power saving mode

** Tags added: nvidia

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

Title:
  [nvidia] System freeze after power saving mode

Status in Ubuntu:
  Incomplete

Bug description:
  Xorg / Gnome freeze after enabling Intel Speed Shift in UEFI. Desktop
  doesn't respond to key combinations like Ctrl + Alt + F3 to go into
  the console. Only SysRq + R and SysRq + E let the system awake again.
  This bug occurs when the system want to go into Power Saving Mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.73.01  Thu Apr  1 
21:40:36 UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/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: Tue Apr 27 19:58:04 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 460.73.01, 5.4.0-72-generic, x86_64: installed
   virtualbox, 6.1.16, 5.4.0-71-generic, x86_64: installed
   virtualbox, 6.1.16, 5.4.0-72-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last few days
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2070 Rev. A] [10de:1f07] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TU106 [GeForce RTX 2070 Rev. A] 
[1043:875c]
  InstallationDate: Installed on 2019-11-10 (534 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic 
root=UUID=454b3874-3032-4cb6-9e5c-92a00ed53afb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.40
  dmi.board.name: Z390 Phantom Gaming 4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.40:bd12/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/+bug

[Touch-packages] [Bug 1925318] Re: [QCA9565] bluetooth just turning off and on and also disconnecting

2021-05-03 Thread Daniel van Vugt
** Summary changed:

- bluetooth just turning off and on and also disconnecting
+ [QCA9565] bluetooth just turning off and on and also disconnecting

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

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

Title:
  [QCA9565] bluetooth just turning off and on and also disconnecting

Status in linux package in Ubuntu:
  New

Bug description:
  bluetooth just turning off and on and also disconnecting.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 21 14:53:05 2021
  InstallationDate: Installed on 2020-12-22 (119 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 3521
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=e7fbb5e3-519a-41d2-94fd-6b2a0305a65d ro text
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0JYTX5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd10/25/2013:efr1.1:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rn0JYTX5:rvrA00:cvnDellInc.:ct8:cvrA12:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Inspiron 3521
  dmi.product.sku: Inspiron 3521
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   
  rfkill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

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

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


[Touch-packages] [Bug 1926936] [NEW] A complete stall in functions

2021-05-03 Thread Fons
Public bug reported:

I don know. The screen just froze. I had to hard boot the computer.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
Uname: Linux 5.4.0-72-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Mon May  3 09:39:45 2021
DistUpgraded: 2020-10-04 14:11:29,457 DEBUG icon theme changed, re-reading
DistroCodename: focal
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard: NVIDIA Corporation GF106 [GeForce GTS 450] [10de:0dc4] (rev a1) 
(prog-if 00 [VGA controller])
InstallationDate: Installed on 2016-05-13 (1815 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: System manufacturer System Product Name
ProcEnviron:
 PATH=(custom, no user)
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic 
root=UUID=448f82f2-4fcd-4a13-8d07-76aef408bab1 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-10-04 (210 days ago)
dmi.bios.date: 02/28/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1102
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4N68T
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd02/28/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N68T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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
xserver.bootTime: Tue Oct 24 08:45:57 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.3
xserver.video_driver: nouveau

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

Title:
  A complete stall in functions

Status in xorg package in Ubuntu:
  New

Bug description:
  I don know. The screen just froze. I had to hard boot the computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon May  3 09:39:45 2021
  DistUpgraded: 2020-10-04 14:11:29,457 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: NVIDIA Corporation GF106 [GeForce GTS 450] [10de:0dc4] (rev a1) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-05-13 (1815 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic 
root=UUID=448f82f2-4fcd-4a13-8d07-76aef408bab1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-10-04 (210 days ago)
  dmi.bios.date: 02/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4N68T
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd02/28/2011:svnSystemmanufacturer:pnSystemP

[Touch-packages] [Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]

2021-05-03 Thread Daniel van Vugt
Unfortunately the fix is still only in Mesa version 21.

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

Title:
  gnome-shell/gnome-session-check-accelerated-gl-helper crashed with
  SIGSEGV in cso_destroy_context() [r300_dri.so]

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa package in Fedora:
  Confirmed

Bug description:
  Graphical user interface is not coming up upon start. Only SSH is
  possible.

  lsb_release -rd:

  Description:  Ubuntu 20.10
  Release:  20.10

  dmesg:

  [   11.985343] gnome-session-c[1013]: segfault at 0 ip  sp 
7fff7679ca48 error 14 in 
gnome-session-check-accelerated-gl-helper[56020e238000+2000]
  [   11.985352] Code: Unable to access opcode bytes at RIP 0xffd6.
  [   14.216117] gnome-shell[1094]: segfault at 0 ip  sp 
7ffeddff9f88 error 14
  [   14.216122] Code: Unable to access opcode bytes at RIP 0xffd6.
  [   15.316292] gnome-shell[1109]: segfault at 0 ip  sp 
7ffc70716198 error 14
  [   15.316297] Code: Unable to access opcode bytes at RIP 0xffd6.

  apt-cache policy:

  gnome-session:
Installed: (none)
Candidate: 3.38.0-1ubuntu1
Version table:
   3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages
  gnome-session-bin:
Installed: 3.38.0-1ubuntu1
Candidate: 3.38.0-1ubuntu1
Version table:
   *** 3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-session-common:
Installed: 3.38.0-1ubuntu1
Candidate: 3.38.0-1ubuntu1
Version table:
   *** 3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages
  100 /var/lib/dpkg/status

  /var/crash: see attachment

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

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


[Touch-packages] [Bug 1892559] Re: [MIR] ccid opensc pcsc-lite

2021-05-03 Thread Ludovic Rousseau
opensc-pkcs11.so is a PKCS#11 lib so the its API conforms to the
standard defined in https://docs.oasis-
open.org/pkcs11/pkcs11-base/v2.40/os/pkcs11-base-v2.40-os.html

If you are looking for .h header files you can use:
https://www.oasis-open.org/committees/document.php?document_id=55655&wg_abbrev=pkcs11
https://www.oasis-open.org/committees/document.php?document_id=55656&wg_abbrev=pkcs11
https://www.oasis-open.org/committees/document.php?document_id=55657&wg_abbrev=pkcs11

pkcs11-spy.so is a spy/debug library. It uses the same API.

A PKCS#11 library is, in general, dynamically loaded using dlopen(3). So
the dependency is not visible from an application using the library (for
example Firefox).

If you really need to move opensc-pkcs11.so & pkcs11-spy.so in a subdir
I would recommand to use /usr/lib/*/pkcs11/ as it is already the case.

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

Title:
  [MIR] ccid opensc pcsc-lite

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

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

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

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

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

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

  Has a debian/watch file.
  Quilt packaging.

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

  [Dependencies]
  Minimal dependencies, in main

  [Standards compliance]
  Appears to satisfy FHS and Debian policy

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

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

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

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

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

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

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

  Quilt packaging.

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

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

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

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

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

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

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

  [Quality assurance]
  Library package not intended to be used directly.
  No debconf questions.
  No bugs in Debian.
  No bugs in Ubuntu.
  Does require odd hardware that we'll probably need to buy.
  Te

[Touch-packages] [Bug 1925344] Re: Session not started after reboot (black screen) - requires switching tty back and forth

2021-05-03 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Tags added: nvidia

** Tags added: dualgpu hybrid

** Also affects: gdm3 (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/1925344

Title:
  Session not started after reboot (black screen) - requires switching
  tty back and forth

Status in gdm3 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New
Status in nvidia-prime package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  After installation, the first boot works as expected - the system
  boots into a graphical shell login screen. However all subsequent
  reboots end up with a black screen with a blinking cursor in the top-
  left corner of the screen. To get to the login screen, one has to
  switch to a different tty (like tty2 with ctrl+alt+f2) and then to
  tty1.

  Running `prime-select query` shows `nvidia`.

  Interesting enough, when I change the nvidia-prime settings at least
  once, like to on-demand via `prime-select on-demand` - then everything
  starts working as expected. Even when I switch back to `nvidia`.

  Not sure which package I should fill this under.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xserver-xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.67  Thu Mar 11 00:11:45 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 21 15:20:15 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Dell UHD Graphics [1028:09e1]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TU116M [GeForce GTX 1660 Ti Mobile] [1028:09e1]
  InstallationDate: Installed on 2021-04-21 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. G3 3500
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=5b38428b-60e8-4741-8b7f-0e60094a80f7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2020
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 06ND9G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd12/04/2020:br1.7:svnDellInc.:pnG33500:pvr:rvnDellInc.:rn06ND9G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G3 3500
  dmi.product.sku: 09E1
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

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


[Touch-packages] [Bug 1925088] Re: [ASUS ROG STRIX Z590-E] Headphones don't work when speakers work

2021-05-03 Thread Daniel van Vugt
** Summary changed:

- Headphones don't work when speakers work
+ [ASUS ROG STRIX Z590-E] Headphones don't work when speakers work

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

Title:
  [ASUS ROG STRIX Z590-E] Headphones don't work when speakers work

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hi!

  I have problem with front panel audio output connector. Speakers still
  work after my headphones is connected. Everything correctly works on
  windows 10.

  I selected headphones in Settings -> Sound -> Output, but speakers
  were continuing working.

  PulseAudio Volume Control didn't help too. I've tried to change
  configuration and select headphones as output devices.

  When i disconnected speakers, headphones weren't still working.

  I've done all list from
  https://help.ubuntu.com/community/SoundTroubleshooting and haven't
  found any problems.

  pacmd - https://pastebin.com/Jkfqt4ft
  aplay - https://pastebin.com/NGq37fVb
  snd   - https://pastebin.com/7bS0GKzc
  lspci - https://pastebin.com/Z6CYmRU2
  alsa  - http://alsa-project.org/db/?f=b5701e36e1510cb211fd3047c36598da27fef2d9

  My hardware:

  CPU - Intel i9 10900k
  Mobo - Asus z590-e with the latest bios.
  GPU - Nvidia RTX 3070

  If you need some additional information, I will provide it.

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

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


[Touch-packages] [Bug 1902768] Re: [ASUS ROG STRIX B550-F] headphone not correctly detected on 20.10

2021-05-03 Thread Daniel van Vugt
I wonder if this is bug 1897965 (again)? That's only fixed in 21.04

** Summary changed:

- headphone not correctly detected on 20.10
+ [ASUS ROG STRIX B550-F] headphone not correctly detected on 20.10

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

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

Title:
  [ASUS ROG STRIX B550-F] headphone not correctly detected on 20.10

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  In 20/04 sound worked via headphones worked fine. After upgrade no
  sound is heard and the audio output device list only has HDMI and
  S/PDIF as possible choices. Windows 10 on the same machine works
  without problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Nov  3 20:39:59 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-09-19 (44 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to groovy on 2020-11-02 (0 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-12-10 (137 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: pulseaudio 1:13.99.2-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Tags:  groovy
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1004
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B550-F GAMING
  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.:bvr1004:bd08/13/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-FGAMING: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: ASUS

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

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


[Touch-packages] [Bug 1925993] Re: chrome browser don't load gpu

2021-05-03 Thread Daniel van Vugt
Thanks for the bug report. Your system seems to be experiencing a lot of
kernel crashes in the 'rtl8821ce' driver. Please try uninstalling that
and using the built-in driver (if available).

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

** Changed in: rtl8821ce (Ubuntu)
   Status: Invalid => 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/1925993

Title:
  chrome browser don't load gpu

Status in rtl8821ce package in Ubuntu:
  Incomplete

Bug description:
  while using chrome browser and playing video in youtube it lag and i
  have check whats wrong about then its gpu error .

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 24 13:49:16 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8821ce, 5.5.2.1, 5.8.0-48-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.8.0-50-generic, x86_64: installed
   rtlwifi-new, 0.6: added
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) 
[103c:852e]
  InstallationDate: Installed on 2021-02-15 (67 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b00a Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 002: ID 04f2:b65d Chicony Electronics Co., Ltd HP TrueVision 
HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 14-cf1xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=e5488d7f-3bf1-42c7-a5db-14fdf4c8ae09 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2019
  dmi.bios.release: 15.53
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.53
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 852E
  dmi.board.vendor: HP
  dmi.board.version: 16.21
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 16.21
  dmi.modalias: 
dmi:bvnInsyde:bvrF.53:bd12/13/2019:br15.53:efr16.21:svnHP:pnHPLaptop14-cf1xxx:pvrType1ProductConfigId:rvnHP:rn852E:rvr16.21:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 14-cf1xxx
  dmi.product.sku: 5GN86UAR#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 
2:1.20.9-2ubuntu1.2~20.04.2ubuntu1ppa6
  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/rtl8821ce/+bug/1925993/+subscriptions

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


Re: [Touch-packages] [Bug 1892559] Re: [MIR] ccid opensc pcsc-lite

2021-05-03 Thread Christian Ehrhardt 
On Mon, May 3, 2021 at 10:20 AM Ludovic Rousseau
<1892...@bugs.launchpad.net> wrote:
>
> opensc-pkcs11.so is a PKCS#11 lib so the its API conforms to the
> standard defined in https://docs.oasis-
> open.org/pkcs11/pkcs11-base/v2.40/os/pkcs11-base-v2.40-os.html

Thanks Ludovic for adding the expert details!
And that makes me re-consider this to "yes we should add .symbols".

> If you really need to move opensc-pkcs11.so & pkcs11-spy.so in a subdir
> I would recommand to use /usr/lib/*/pkcs11/ as it is already the case.

Well, since there are external users it will be much harder to move things.
As they all need to be compatible (or adapted) to the new place.
Still worth having a look to move them, but more complex and more
potential impact than what I expected before your explanation.

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

Title:
  [MIR] ccid opensc pcsc-lite

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

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

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

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

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

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

  Has a debian/watch file.
  Quilt packaging.

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

  [Dependencies]
  Minimal dependencies, in main

  [Standards compliance]
  Appears to satisfy FHS and Debian policy

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

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

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

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

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

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

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

  Quilt packaging.

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

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

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

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

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

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

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

  [Quality assurance]
  Library package not intended to be used directly.
  No debconf questions.
  No bugs in Debian.
  No bugs in Ubuntu.
  Does require odd hardware that we'll probably need to buy.
  Tests exist, not run during the build; probably can't ru

[Touch-packages] [Bug 1926936] Re: A complete stall in functions

2021-05-03 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** Tags added: nouveau

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

Title:
  A complete stall in functions

Status in Ubuntu:
  Incomplete

Bug description:
  I don know. The screen just froze. I had to hard boot the computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon May  3 09:39:45 2021
  DistUpgraded: 2020-10-04 14:11:29,457 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: NVIDIA Corporation GF106 [GeForce GTS 450] [10de:0dc4] (rev a1) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-05-13 (1815 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic 
root=UUID=448f82f2-4fcd-4a13-8d07-76aef408bab1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-10-04 (210 days ago)
  dmi.bios.date: 02/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4N68T
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd02/28/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N68T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  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
  xserver.bootTime: Tue Oct 24 08:45:57 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1.3
  xserver.video_driver: nouveau

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

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


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

2021-05-03 Thread Daniel van Vugt
Thanks for the bug report. It appears there was a kernel update a couple
of days before this bug was opened so I would investigate that first.

Please use the Escape key to access the boot menu and try selecting an
older kernel. Or try a different kernel version from here:

https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D


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

** Summary changed:

- Xorg freeze
+ System freeze

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

Title:
  System freeze

Status in Ubuntu:
  Incomplete

Bug description:
  Since a week or two, videos started to freeze on Youtube. The video
  jam, the audio repeating the last quarter of a second of material,
  just like an audio CD that stays hooked. At this point, the mouse and
  the keyboard don't respond in any way and I have to depress the ON/OFF
  key and hold it a few seconds to do a forced stop. The computer
  restart normally, and Firefox open with a screen that says:"sorry we
  cannot restore your previous tabs". This bug happens again and again,
  each time 15 or 20 minutes after starting a video. I thought maybe it
  is a problem related to Youtube, but I tried watching a video on
  another site, DailyMotion, and the same thing happened, again after 15
  minutes.

  I didn't upgrade or add any software recently, nor change any setting.
  This thing really appeared out of a blue sky.

  Thanks for your attention,

  RB

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262
  Uname: Linux 4.4.0-210-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.30
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr 22 14:53:35 2021
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller 
[8086:2592] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: IBM ThinkPad X41 [1014:0582]
 Subsystem: IBM ThinkPad X41 [1014:0582]
  InstallationDate: Installed on 2018-08-14 (982 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  MachineType: IBM 1875M2U
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=fr_CA:fr
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-210-generic 
root=UUID=596f4e0f-deb0-4de7-973b-8259f928fbe9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2007
  dmi.bios.vendor: IBM
  dmi.bios.version: 70ET69WW (1.29 )
  dmi.board.name: 1875M2U
  dmi.board.vendor: IBM
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: IBM
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnIBM:bvr70ET69WW(1.29):bd05/29/2007:svnIBM:pn1875M2U:pvrThinkPadT43:rvnIBM:rn1875M2U:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
  dmi.product.name: 1875M2U
  dmi.product.version: ThinkPad T43
  dmi.sys.vendor: IBM
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  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.12
  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: Thu Apr 22 10:09:47 2021
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.12

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

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

[Touch-packages] [Bug 1926547] Re: Add Dell Privacy Mic Mute Key mapping

2021-05-03 Thread Balint Reczey
** Changed in: systemd (Ubuntu)
   Status: New => Triaged

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

Title:
  Add Dell Privacy Mic Mute Key mapping

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
     GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

  [Other Info]

   * The change can only work with kernel commit on some specific hardware, ex. 
Latitude 9520. The commit series is 
"hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree.
     https://patchwork.kernel.org/project/alsa-devel/list/?series=465445
   * This change has been verified on Dell machine.

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

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


[Touch-packages] [Bug 1926316] Re: lxappearance crashes on launch

2021-05-03 Thread Sebastien Bacher
** Tags added: rls-hh-incoming

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

Title:
  lxappearance crashes on launch

Status in glib2.0 package in Ubuntu:
  Fix Committed

Bug description:
  Backtrace of the segmentation fault

  Program received signal SIGSEGV, Segmentation fault.
  0x7790c79d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  (gdb) bt
  #0  0x7790c79d in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #1  0x7790ccc1 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x7790cf41 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #3  0x7790d079 in g_key_file_load_from_file () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #4  0x55407072 in load_icon_themes_from_dir ()
  #5  0x554073dd in icon_theme_init ()
  #6  0x55404c92 in main ()

  Strace shows that the programs borks while trying to load the icon
  theme "/usr/share/icons/gnome/index.theme".

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: lxappearance 0.6.3-1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Config_System_openbox: Error: [Errno 2] No such file or directory: 
'/etc/xdg/lxsession/openbox/desktop.conf'
  CurrentDesktop: lxde
  Date: Tue Apr 27 21:47:03 2021
  Icons_Default: No icons theme configured by default
  InstallationDate: Installed on 2021-01-12 (105 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: lxappearance
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1926316/+subscriptions

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


[Touch-packages] [Bug 1925530] Re: Backport Metro Exodus Mesa fix into Hirsute

2021-05-03 Thread AsciiWolf
This will be fixed when mesa 21.0.x is backported (see #1925434).
Closing this ticket.

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

** Changed in: hundredpapercuts
   Status: New => Invalid

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

Title:
  Backport Metro Exodus Mesa fix into Hirsute

Status in One Hundred Papercuts:
  Invalid
Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Please, consider backporting an important fix for "memory leak on
  descriptor pool reset with layout_size=0" into Ubuntu 21.04 Mesa.
  Without this fix, Metro Exodus and possibly other games cause system
  to hang or crash after playing for some time.

  Here is a MR with the fix:
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10317

  It is already staged to be backported into current stable Mesa
  releases and so it should be fine to apply it as a downstream patch
  for Mesa 21.0.1 in Ubuntu Hirsute.

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

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


[Touch-packages] [Bug 1922937] Autopkgtest regression report (apport/2.20.11-0ubuntu50.6)

2021-05-03 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted apport (2.20.11-0ubuntu50.6) for groovy 
have finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-release-upgrader/1:20.10.15 (armhf)


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

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

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

Thank you!

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

Title:
  reading casper-md5check.json fails

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Committed
Status in apport source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  Bugs reported by apport are not including information about the results of 
the md5 check of the installation media used. Additionally, users are presented 
with a traceback regarding the ubuntu hook which is used with all bug reports.

  [Test Case]
  1) Boot an Ubuntu 20.04 LTS or Ubuntu 20.10 install
  2) Create the file /var/log/installer/casper-md5check.json with mode 0600.
  3) Run 'ubuntu-bug coreutils'

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in 
_run_hook
  symb['add_info'](report, ui)
    File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info
  apport.hookutils.attach_casper_md5check(report,
    File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 995, in 
attach_casper_md5check
  with open(location) as json_file:
  PermissionError: [Errno 13] Permission denied: 
'/var/log/installer/casper-md5check.json'

  [Where problems could occur]
  We are switching to reading the file with attach_root_command_outputs which 
is a well tested function in apport so the only problem would be a result of 
the new code being added. This works well in Hirsute so there is little chance 
of their being an error.

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

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


[Touch-packages] [Bug 1920837] Autopkgtest regression report (apport/2.20.11-0ubuntu50.6)

2021-05-03 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted apport (2.20.11-0ubuntu50.6) for groovy 
have finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-release-upgrader/1:20.10.15 (armhf)


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

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

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

Thank you!

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

Title:
  apport bugs from official raspi or riscv images are not identified

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

Bug description:
  It would be helpful if bugs reported from images for Raspberry Pi's or
  RISCV systems were tagged so that one could search for bugs from
  systems running those images e.g. 'raspi-image'.

  [Test Case]
  After installing a preinstalled image of Ubuntu for Raspberry Pi do the 
following:
  1) run 'ubuntu-bug apport'
  2) view the bug report and check the Tags field

  With the current version of apport you will not see the tag 'raspi-image'.
  With the version of apport in -proposed you will see the tag 'raspi-image'.

  [Where problems could occur]
  If the code being added is syntactically incorrect then we'd see a Traceback 
which would be bad as it could affect all bug / crash reports.

  [Other Info]
  Since there aren't any Groovy images for RISC-V there will be nothing to test 
there.

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

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


[Touch-packages] [Bug 1821415] Autopkgtest regression report (apport/2.20.11-0ubuntu50.6)

2021-05-03 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted apport (2.20.11-0ubuntu50.6) for groovy 
have finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-release-upgrader/1:20.10.15 (armhf)


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

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

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

Thank you!

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in policykit-1 package in Ubuntu:
  Won't Fix
Status in apport source package in Focal:
  Fix Committed
Status in policykit-1 source package in Focal:
  Won't Fix
Status in apport source package in Groovy:
  Fix Committed
Status in policykit-1 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]
  The plymouth apport source package hooks wants to gather log files as the 
root user and apport provides a policy kit policy for collecting that 
information. This works fine in a graphical environment but not in a 
non-graphical one.

  [Test Case]
  1) ssh into an Ubuntu Desktop install of Ubuntu 20.04 LTS or Ubuntu 20.10
  2) sudo touch /var/log/plymouth-debug.log
  3) ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  With the version of apport from -proposed you will not see the
  "AUTHENTICATION FAILED" error and the plymouth-debug.log file will be
  collected.

  [Where Problems Could Occur]
  It's possible that the spawned pkttyagent process does not get cleaned up 
properly and could be left running. When testing the SRU we should confirm it 
is not still running.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1821415/+subscriptions

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


[Touch-packages] [Bug 1838890] Re: Suspected memory leak in xenial backport of fix for CVE-2019-13012

2021-05-03 Thread Launchpad Bug Tracker
This bug was fixed in the package glib2.0 - 2.32.4-0ubuntu1.4

---
glib2.0 (2.32.4-0ubuntu1.4) precise-security; urgency=medium

  * SECURITY REGRESSION: regression in last security update (LP: #1838890)
- debian/patches/CVE-2019-13012-regression.patch: fix a
  memory leak introduced by the last security update while
  not properly handled the g_file_get_patch function in
  gio/gkeyfilesettingsbackend.c.

 -- leo.barb...@canonical.com (Leonidas S. Barbosa)  Mon, 05 Aug 2019
12:54:19 -0300

** Changed in: glib2.0 (Ubuntu Precise)
   Status: In Progress => Fix Released

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

Title:
  Suspected memory leak in xenial backport of fix for CVE-2019-13012

Status in glib2.0 package in Ubuntu:
  In Progress
Status in glib2.0 source package in Precise:
  Fix Released
Status in glib2.0 source package in Trusty:
  In Progress
Status in glib2.0 source package in Xenial:
  Fix Released

Bug description:
  (This is only from source code inspection, not tested in real use - I
  don't actually use Ubuntu.)

  The upstream fix for CVE-2019-13012 included this change:

  -  g_file_make_directory_with_parents (kfsb->dir, NULL, NULL);
  +  g_mkdir_with_parents (g_file_peek_path (kfsb->dir), 0700);

  However, g_file_peek_path() was only introduced in GLib 2.56. The
  backport in the xenial package has this instead:

  -  g_file_make_directory_with_parents (kfsb->dir, NULL, NULL);
  +  g_mkdir_with_parents (g_file_get_path (kfsb->dir), 0700);

  This is not equivalent. The difference between g_file_peek_path() and
  the older g_file_get_path() is that g_file_get_path() makes a copy,
  which must be freed with g_free() after use. As a result, there is now
  a memory leak.

  A non-leaky backport would look something like this, which is what
  I've done in a proposed backport for Debian 9 'stretch':

  + char *dir;
  ...
  -  g_file_make_directory_with_parents (kfsb->dir, NULL, NULL);
  +  dir = g_file_get_path (kfsb->dir);
  +  g_mkdir_with_parents (dir, 0700);
  +  g_free (dir);

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1838890/+subscriptions

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


[Touch-packages] [Bug 1834494] Re: latest bzip2 reports crc errors incorrectly

2021-05-03 Thread Launchpad Bug Tracker
This bug was fixed in the package bzip2 - 1.0.6-1ubuntu0.2

---
bzip2 (1.0.6-1ubuntu0.2) precise-security; urgency=medium

  * SECURITY REGRESSION: bzip2 update for CVE-2019-12900 causes some files 
raises
incorrect CRC error. (LP: #1834494)
- debian/patches/Accept-as-many-selectors-as-selectors*.patch

 -- leo.barb...@canonical.com (Leonidas S. Barbosa)  Thu, 04 Jul 2019
08:37:58 -0300

** Changed in: bzip2 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  Fix Released
Status in bzip2 package in Ubuntu:
  Fix Released
Status in bzip2 source package in Xenial:
  Fix Released
Status in bzip2 source package in Bionic:
  Fix Released
Status in bzip2 source package in Cosmic:
  Fix Released
Status in bzip2 source package in Disco:
  Fix Released
Status in bzip2 package in Debian:
  Fix Released

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

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

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


[Touch-packages] [Bug 1913482] Re: Update tzdata to version 2021a

2021-05-03 Thread Launchpad Bug Tracker
This bug was fixed in the package tzdata - 2021a-0ubuntu0.12.04

---
tzdata (2021a-0ubuntu0.12.04) precise; urgency=medium

  * New upstream version (LP: #1913482), affecting the following future 
timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.

 -- Brian Murray   Wed, 27 Jan 2021 14:10:24 -0800

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

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

Title:
  Update tzdata to version 2021a

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Xenial:
  Fix Released
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Groovy:
  Fix Released

Bug description:
  New upstream version affecting the following timestamp:

  - South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.

  $region/$timezone = Africa/Juba

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

  [Test Case for all releases]
  1) zdump -v Africa/Juba | grep 2021

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba')); 
print(str(tz.utcoffset(datetime(2021, 2, 1'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

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

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


[Touch-packages] [Bug 1676117] Re: tzdata-java 2017a package required

2021-05-03 Thread Launchpad Bug Tracker
This bug was fixed in the package tzdata - 2021a-0ubuntu0.12.04

---
tzdata (2021a-0ubuntu0.12.04) precise; urgency=medium

  * New upstream version (LP: #1913482), affecting the following future 
timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.

 -- Brian Murray   Wed, 27 Jan 2021 14:10:24 -0800

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

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

Title:
  tzdata-java 2017a package required

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Trusty:
  Fix Released

Bug description:
  Mongolia no longer observes DST. I can't find tzdata-java_2017a
  package.

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

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


[Touch-packages] [Bug 1913810] Re: restart doesn't test for syntax errors

2021-05-03 Thread Athos Ribeiro
Ideally, this should be supported by systemd somehow. There is this
(old) discussion upstream, which is relevant here:
https://github.com/systemd/systemd/issues/2175

If we introduced the desired behavior by including an ExecStop script to
the systemd unit configuration file, we would introduce a regression
since stopping the service for erroneous configuration files would not
be allowed (this was not the behavior for sysV).

** Bug watch added: github.com/systemd/systemd/issues #2175
   https://github.com/systemd/systemd/issues/2175

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

Title:
  restart doesn't test for syntax errors

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  Tested openssh on bionic and groovy, same issue.

  The switch to systemd lost the ability to do a sanity check on the
  config file (via sshd -t) before attempting to restart sshd. This was
  originally bug #624361 in the SySV days, fixed in the initscript back
  then.

  The sysv script still does it, but it's not used anymore:
   restart)
  check_privsep_dir
  check_config
  log_daemon_msg "Restarting OpenBSD Secure Shell server" "sshd" || true

  
  And:
  check_config() {
  if [ ! -e /etc/ssh/sshd_not_to_be_run ]; then
  /usr/sbin/sshd $SSHD_OPTS -t || exit 1
  fi
  }

  
  The systemd service file has only ExecStartPre, which doesn't let it start if 
there is an error, but will happily stop it:
  [Unit]
  Description=OpenBSD Secure Shell server
  After=network.target auditd.service
  ConditionPathExists=!/etc/ssh/sshd_not_to_be_run

  [Service]
  EnvironmentFile=-/etc/default/ssh
  ExecStartPre=/usr/sbin/sshd -t
  ExecStart=/usr/sbin/sshd -D $SSHD_OPTS
  ExecReload=/usr/sbin/sshd -t
  ExecReload=/bin/kill -HUP $MAINPID
  ...

  Example:
  # sshd -t 
  
  # systemctl restart sshd  
  
  # telnet localhost 22 
  
  Trying 127.0.0.1...   
  
  Connected to localhost.   
  
  Escape character is '^]'. 
  
  SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3   
  
  ^]
  
  telnet> quit  
  
  Connection closed.
  

  
  # echo "syntax error" >> /etc/ssh/sshd_config 
  
  # sshd -t 
  
  /etc/ssh/sshd_config: line 123: Bad configuration option: syntax  
  
  /etc/ssh/sshd_config: terminating, 1 bad configuration options
  

  
  # systemctl restart sshd  
  
  Job for ssh.service failed because the control process exited with error 
code.  
  See "systemctl status ssh.service" and "journalctl -xe" for details.  
  

  
  # telnet localhost 22 
  
  Trying 127.0.0.1...   
  
  telnet: Unable to connect to remote host: Connection refused  
  
  #

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

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


[Touch-packages] [Bug 1902768] Re: [ASUS ROG STRIX B550-F] headphone not correctly detected on 20.10

2021-05-03 Thread Sebastien Bacher
@Jussi could you check if you have pipewire installed and if you do try
to uninstall it to see if that makes a difference?

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

Title:
  [ASUS ROG STRIX B550-F] headphone not correctly detected on 20.10

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  In 20/04 sound worked via headphones worked fine. After upgrade no
  sound is heard and the audio output device list only has HDMI and
  S/PDIF as possible choices. Windows 10 on the same machine works
  without problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Nov  3 20:39:59 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-09-19 (44 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to groovy on 2020-11-02 (0 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-12-10 (137 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: pulseaudio 1:13.99.2-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Tags:  groovy
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1004
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B550-F GAMING
  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.:bvr1004:bd08/13/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-FGAMING: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: ASUS

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

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


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

2021-05-03 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2021-05-03 10:12 EDT---
@Canonical, any updates available here? Many thx in adbvance

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

Title:
  test -x fails inside shell scripts in containers

Status in Ubuntu on IBM z Systems:
  New
Status in docker.io package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  Opinion
Status in libseccomp package in Ubuntu:
  Fix Committed
Status in runc package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in docker.io source package in Xenial:
  New
Status in libseccomp source package in Xenial:
  New
Status in runc source package in Xenial:
  New
Status in systemd source package in Xenial:
  Invalid
Status in docker.io source package in Bionic:
  New
Status in libseccomp source package in Bionic:
  New
Status in runc source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in docker.io source package in Focal:
  New
Status in libseccomp source package in Focal:
  New
Status in runc source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in docker.io source package in Groovy:
  New
Status in libseccomp source package in Groovy:
  New
Status in runc source package in Groovy:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released
Status in docker.io source package in Hirsute:
  New
Status in libseccomp source package in Hirsute:
  Fix Committed
Status in runc source package in Hirsute:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  (SRU template for systemd)

  [impact]

  bash (and some other shells) builtin test command -x operation fails

  [test case]

  on any affected host system, start nspawn container, e.g.:

  $ sudo apt install systemd-container
  $ wget 
https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz
  $ mkdir h
  $ cd h
  $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz
  $ sudo systemd-nspawn

  Then from a bash shell, verify if test -x works:

  root@h:~# ls -l /usr/bin/gpg
  -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg
  root@h:~# test -x /usr/bin/gpg || echo "fail"
  fail

  [regression potential]

  any regression would likely occur during a syscall, most likely
  faccessat2(), or during other syscalls.

  [scope]

  this is needed for b/f

  this is fixed upstream by commit
  bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so
  this is fixed in h

  this was pulled into Debian at version 246.2 in commit
  e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g

  in x, the entire systemd seccomp code is completely different and the
  patch doesn't apply, nor does it appear to be needed, as the problem
  doesn't reproduce in a h container under x.

  [other info]

  this needs fixing in libseccomp as well

  [original description]

  glibc regression causes test -x to fail inside scripts inside
  docker/podman, dash and bash are broken, mksh and zsh are fine:

  root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail
  root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/#

  root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail

  The -f flag works, as does /usr/bin/test:
  # bash -c "test -f /usr/bin/gpg  || echo Fail"
  # bash -c "/usr/bin/test -x /usr/bin/gpg  || echo Fail"
  #

  [Original bug report]
  root@84b750e443f8:/# lsb_release -rd
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  root@84b750e443f8:/# dpkg -l gnupg apt
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version Architecture Description
  
+++-==-===--==
  ii  apt2.1.20  amd64commandline package manager
  ii  gnupg  2.2.20-1ubuntu2 all  GNU privacy guard - a free 
PGP replacement

  Hi,
  for 3 days our CI pipelines to recreate Docker images fails for the Hirsute 
images. From comparison this seems to be caused by apt 2.1.20.

  The build fails with:

  0E: gnupg, gnupg2 and unupg1 do

[Touch-packages] [Bug 1913810] Re: restart doesn't test for syntax errors

2021-05-03 Thread Andreas Hasenack
yeah, it's specifically restart that we want to check

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

Title:
  restart doesn't test for syntax errors

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  Tested openssh on bionic and groovy, same issue.

  The switch to systemd lost the ability to do a sanity check on the
  config file (via sshd -t) before attempting to restart sshd. This was
  originally bug #624361 in the SySV days, fixed in the initscript back
  then.

  The sysv script still does it, but it's not used anymore:
   restart)
  check_privsep_dir
  check_config
  log_daemon_msg "Restarting OpenBSD Secure Shell server" "sshd" || true

  
  And:
  check_config() {
  if [ ! -e /etc/ssh/sshd_not_to_be_run ]; then
  /usr/sbin/sshd $SSHD_OPTS -t || exit 1
  fi
  }

  
  The systemd service file has only ExecStartPre, which doesn't let it start if 
there is an error, but will happily stop it:
  [Unit]
  Description=OpenBSD Secure Shell server
  After=network.target auditd.service
  ConditionPathExists=!/etc/ssh/sshd_not_to_be_run

  [Service]
  EnvironmentFile=-/etc/default/ssh
  ExecStartPre=/usr/sbin/sshd -t
  ExecStart=/usr/sbin/sshd -D $SSHD_OPTS
  ExecReload=/usr/sbin/sshd -t
  ExecReload=/bin/kill -HUP $MAINPID
  ...

  Example:
  # sshd -t 
  
  # systemctl restart sshd  
  
  # telnet localhost 22 
  
  Trying 127.0.0.1...   
  
  Connected to localhost.   
  
  Escape character is '^]'. 
  
  SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3   
  
  ^]
  
  telnet> quit  
  
  Connection closed.
  

  
  # echo "syntax error" >> /etc/ssh/sshd_config 
  
  # sshd -t 
  
  /etc/ssh/sshd_config: line 123: Bad configuration option: syntax  
  
  /etc/ssh/sshd_config: terminating, 1 bad configuration options
  

  
  # systemctl restart sshd  
  
  Job for ssh.service failed because the control process exited with error 
code.  
  See "systemctl status ssh.service" and "journalctl -xe" for details.  
  

  
  # telnet localhost 22 
  
  Trying 127.0.0.1...   
  
  telnet: Unable to connect to remote host: Connection refused  
  
  #

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

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


[Touch-packages] [Bug 1926964] [NEW] missing libapt-pkg4.12 dependency

2021-05-03 Thread Frederic Van Espen
Public bug reported:

It seems python-apt from ubuntu precise ESM made it into the old
precise-security repo. Unfortunately, it depends on libapt-pkg4.12 (>=
0.8.16~exp12ubuntu10.28), which is not available.

The following packages have unmet dependencies:
 python-apt : Depends: libapt-pkg4.12 (>= 0.8.16~exp12ubuntu10.28) but 
0.8.16~exp12ubuntu10.27 is to be installed

** Affects: python-apt (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  missing libapt-pkg4.12 dependency

Status in python-apt package in Ubuntu:
  New

Bug description:
  It seems python-apt from ubuntu precise ESM made it into the old
  precise-security repo. Unfortunately, it depends on libapt-pkg4.12 (>=
  0.8.16~exp12ubuntu10.28), which is not available.

  The following packages have unmet dependencies:
   python-apt : Depends: libapt-pkg4.12 (>= 0.8.16~exp12ubuntu10.28) but 
0.8.16~exp12ubuntu10.27 is to be installed

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

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


[Touch-packages] [Bug 1902768] Re: [ASUS ROG STRIX B550-F] headphone not correctly detected on 20.10

2021-05-03 Thread Jussi Pakkanen
I actually updated to Hirsute and the issue seems to be gone.

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

Title:
  [ASUS ROG STRIX B550-F] headphone not correctly detected on 20.10

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  In 20/04 sound worked via headphones worked fine. After upgrade no
  sound is heard and the audio output device list only has HDMI and
  S/PDIF as possible choices. Windows 10 on the same machine works
  without problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Nov  3 20:39:59 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-09-19 (44 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to groovy on 2020-11-02 (0 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-12-10 (137 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: pulseaudio 1:13.99.2-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Tags:  groovy
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1004
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B550-F GAMING
  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.:bvr1004:bd08/13/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-FGAMING: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: ASUS

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

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


[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers

2021-05-03 Thread Sergio Durigan Junior
Hello!  The kernel team has applied the fix to their pre-release branch.
They have a 5-week release cycle, so we should be seeing a new Bionic
Linux kernel with the fix in the following 3-4 weeks.  Thanks.

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

Title:
  test -x fails inside shell scripts in containers

Status in Ubuntu on IBM z Systems:
  New
Status in docker.io package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  Opinion
Status in libseccomp package in Ubuntu:
  Fix Committed
Status in runc package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in docker.io source package in Xenial:
  New
Status in libseccomp source package in Xenial:
  New
Status in runc source package in Xenial:
  New
Status in systemd source package in Xenial:
  Invalid
Status in docker.io source package in Bionic:
  New
Status in libseccomp source package in Bionic:
  New
Status in runc source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in docker.io source package in Focal:
  New
Status in libseccomp source package in Focal:
  New
Status in runc source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in docker.io source package in Groovy:
  New
Status in libseccomp source package in Groovy:
  New
Status in runc source package in Groovy:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released
Status in docker.io source package in Hirsute:
  New
Status in libseccomp source package in Hirsute:
  Fix Committed
Status in runc source package in Hirsute:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  (SRU template for systemd)

  [impact]

  bash (and some other shells) builtin test command -x operation fails

  [test case]

  on any affected host system, start nspawn container, e.g.:

  $ sudo apt install systemd-container
  $ wget 
https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz
  $ mkdir h
  $ cd h
  $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz
  $ sudo systemd-nspawn

  Then from a bash shell, verify if test -x works:

  root@h:~# ls -l /usr/bin/gpg
  -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg
  root@h:~# test -x /usr/bin/gpg || echo "fail"
  fail

  [regression potential]

  any regression would likely occur during a syscall, most likely
  faccessat2(), or during other syscalls.

  [scope]

  this is needed for b/f

  this is fixed upstream by commit
  bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so
  this is fixed in h

  this was pulled into Debian at version 246.2 in commit
  e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g

  in x, the entire systemd seccomp code is completely different and the
  patch doesn't apply, nor does it appear to be needed, as the problem
  doesn't reproduce in a h container under x.

  [other info]

  this needs fixing in libseccomp as well

  [original description]

  glibc regression causes test -x to fail inside scripts inside
  docker/podman, dash and bash are broken, mksh and zsh are fine:

  root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail
  root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/#

  root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail

  The -f flag works, as does /usr/bin/test:
  # bash -c "test -f /usr/bin/gpg  || echo Fail"
  # bash -c "/usr/bin/test -x /usr/bin/gpg  || echo Fail"
  #

  [Original bug report]
  root@84b750e443f8:/# lsb_release -rd
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  root@84b750e443f8:/# dpkg -l gnupg apt
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version Architecture Description
  
+++-==-===--==
  ii  apt2.1.20  amd64commandline package manager
  ii  gnupg  2.2.20-1ubuntu2 all  GNU privacy guard - a free 
PGP replacement

  Hi,
  for 3 days our CI pipelines to recreate Docker images fails for the Hirsute 
images. From comparison this seems to be caused by apt 2

[Touch-packages] [Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]

2021-05-03 Thread Timo Aaltonen
Update for groovy? Not likely at this point, focal will get it via
1925320

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

Title:
  gnome-shell/gnome-session-check-accelerated-gl-helper crashed with
  SIGSEGV in cso_destroy_context() [r300_dri.so]

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa package in Fedora:
  Confirmed

Bug description:
  Graphical user interface is not coming up upon start. Only SSH is
  possible.

  lsb_release -rd:

  Description:  Ubuntu 20.10
  Release:  20.10

  dmesg:

  [   11.985343] gnome-session-c[1013]: segfault at 0 ip  sp 
7fff7679ca48 error 14 in 
gnome-session-check-accelerated-gl-helper[56020e238000+2000]
  [   11.985352] Code: Unable to access opcode bytes at RIP 0xffd6.
  [   14.216117] gnome-shell[1094]: segfault at 0 ip  sp 
7ffeddff9f88 error 14
  [   14.216122] Code: Unable to access opcode bytes at RIP 0xffd6.
  [   15.316292] gnome-shell[1109]: segfault at 0 ip  sp 
7ffc70716198 error 14
  [   15.316297] Code: Unable to access opcode bytes at RIP 0xffd6.

  apt-cache policy:

  gnome-session:
Installed: (none)
Candidate: 3.38.0-1ubuntu1
Version table:
   3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages
  gnome-session-bin:
Installed: 3.38.0-1ubuntu1
Candidate: 3.38.0-1ubuntu1
Version table:
   *** 3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-session-common:
Installed: 3.38.0-1ubuntu1
Candidate: 3.38.0-1ubuntu1
Version table:
   *** 3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages
  100 /var/lib/dpkg/status

  /var/crash: see attachment

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

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


[Touch-packages] [Bug 1926976] [NEW] during mouse drag operations I'm getting undesired/unprompted dropping and potentially picking up of something else

2021-05-03 Thread buchs
Public bug reported:

I am not really sure this is an Xorg problem. Since my last system
update (upon the system prompting), I think less than a week ago, I have
noticed this troubling intermittent behavior. I go to drag (mouse-
initiated) a window across some screen distances (between external
monitors and my laptop's builtin monitor) the window will get dropped
without me releasing the mouse button before arriving at my desired drop
point. More than half the times this happens, something will immediately
be picked up in a drag operation. Sometimes it is another window that
begins being moved. Other times it is a window resize operation that is
picked up. A third option is the selection of text.

I have noticed that most of the time it is triggered when I am moving
rapidly (though no more rapidly than I have done successfully in the
past). Sometimes it happens when I pause during the drag operation. It
even happens infrequently when I am dragging slowly.

Often I can just go back and pick up the window and complete the
operation. However, sometimes the problem just keeps happening until I
give up and go away for 5 minutes or so.

I have a stock configuration of 20.04. I keep it updated and haven't
changed anything significant about X, Gnome, etc. I have done a few
tweaks, but nothing I can think of that would relate to this problem. My
laptop, a Dell XPS 13, uses a USB 3.1 hub and through that drives two
monitors via HDMI. My mouse is bluetooth - Logitech MX Vertical. I don't
believe I have installed any proprietary drivers. My 3 displays are
arranged into an inverted "L" shape, as the laptop display is "below"
and identically sized to the 27" monitor "above" it. The other 27"
monitor is to the left of the first one.

Some, potentially useful, debugging info:

$ lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04
$ apt-cache policy xorg
xorg:
  Installed: 1:7.7+19ubuntu14
  Candidate: 1:7.7+19ubuntu14
  Version table:
 *** 1:7.7+19ubuntu14 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status


$ bluetoothctl --version
bluetoothctl: 5.53
$ hciconfig -a
hci0:   Type: Primary  Bus: USB
BD Address: 9C:B6:D0:99:27:2C  ACL MTU: 1024:8  SCO MTU: 50:8
UP RUNNING
RX bytes:21743080 acl:954252 sco:0 events:141080 errors:0
TX bytes:6895 acl:169 sco:0 commands:208 errors:0
Features: 0xff 0xfe 0x8f 0xfe 0xd8 0x3f 0x5b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF
Link mode: SLAVE ACCEPT
Name: 'kbuchs'
Class: 0x0c010c
Service Classes: Rendering, Capturing
Device Class: Computer, Laptop
HCI Version: 4.2 (0x8)  Revision: 0x0
LMP Version: 4.2 (0x8)  Subversion: 0x25a
Manufacturer: Qualcomm (29)

$ bluetoothctl
Agent registered
[CHG] Controller 9C:B6:D0:99:27:2C Pairable: yes
[MX Vertical]# show
Controller 9C:B6:D0:99:27:2C (public)
Name: kbuchs
Alias: kbuchs
Class: 0x000c010c
Powered: yes
Discoverable: no
DiscoverableTimeout: 0x00b4
Pairable: yes
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0535
Discovering: no
Advertising Features:
ActiveInstances: 0x00
SupportedInstances: 0x05
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
[MX Vertical]# devices
Device D4:51:67:AF:3D:FF MX Vertical
[MX Vertical]# info D4:51:67:AF:3D:FF
Device D4:51:67:AF:3D:FF (random)
Name: MX Vertical
Alias: MX Vertical
Appearance: 0x03c2
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: Device Information(180a--1000-8000-00805f9b34fb)
UUID: Battery Service   (180f--1000-8000-00805f9b34fb)
UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
UUID: Vendor specific   (0001--1000-8000-011f246d)
Modalias: usb:v046

[Touch-packages] [Bug 1926964] Re: missing libapt-pkg4.12 dependency

2021-05-03 Thread Julian Andres Klode
** Changed in: python-apt (Ubuntu)
 Assignee: (unassigned) => Steve Langasek (vorlon)

** Package changed: python-apt (Ubuntu) => apt (Ubuntu)

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

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

Title:
  missing libapt-pkg4.12 dependency

Status in apt package in Ubuntu:
  Triaged

Bug description:
  It seems python-apt from ubuntu precise ESM made it into the old
  precise-security repo. Unfortunately, it depends on libapt-pkg4.12 (>=
  0.8.16~exp12ubuntu10.28), which is not available.

  The following packages have unmet dependencies:
   python-apt : Depends: libapt-pkg4.12 (>= 0.8.16~exp12ubuntu10.28) but 
0.8.16~exp12ubuntu10.27 is to be installed

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

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


[Touch-packages] [Bug 1926912] [NEW] 21.10 Impish gdebi Programm fehlt Paket?

2021-05-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Hallo
Programm gdebi fehlen Pakete?
Sieh Bild
Gruß

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


** Tags: bot-comment
-- 
21.10 Impish gdebi Programm fehlt Paket?
https://bugs.launchpad.net/bugs/1926912
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gdebi 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 1926912] Re: 21.10 Impish gdebi Programm fehlt Paket?

2021-05-03 Thread Hans Joachim Desserud
** Package changed: ubuntu => gdebi (Ubuntu)

** Tags added: impish

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

Title:
  21.10 Impish gdebi Programm fehlt Paket?

Status in gdebi package in Ubuntu:
  New

Bug description:
  Hallo
  Programm gdebi fehlen Pakete?
  Sieh Bild
  Gruß

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

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


[Touch-packages] [Bug 1926964] Re: missing libapt-pkg4.12 dependency

2021-05-03 Thread Steve Langasek
Apologies, it seems this was a copy that was missed.  apt will be
publishing shortly.

Also, if you noticed this problem, you are running an unsupported
release of Ubuntu and should upgrade.

** Changed in: apt (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  missing libapt-pkg4.12 dependency

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  It seems python-apt from ubuntu precise ESM made it into the old
  precise-security repo. Unfortunately, it depends on libapt-pkg4.12 (>=
  0.8.16~exp12ubuntu10.28), which is not available.

  The following packages have unmet dependencies:
   python-apt : Depends: libapt-pkg4.12 (>= 0.8.16~exp12ubuntu10.28) but 
0.8.16~exp12ubuntu10.27 is to be installed

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

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


[Touch-packages] [Bug 1926989] [NEW] lpoptions command won't create a new printer instance

2021-05-03 Thread Darren Croft
Public bug reported:

Running the following command :
sudo lpoptions -p Letters/test -o InputSlot=Tray5

returns without error

sudo lpoptions -p Letters/test -l
Shows that the the above command had no effect InputSlot=Auto

After running the commands, there is no file /etc/cups/lpoptions

Even if an lpoptions file is created manually, it has no effect.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups 2.3.1-9ubuntu1.1
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CupsErrorLog:
 W [27/Apr/2021:13:43:24 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id \'PDF-Gray..\' already 
exists
 W [27/Apr/2021:13:43:24 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id \'PDF-RGB..\' already 
exists
 W [03/May/2021:11:20:51 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id \'Letters-Gray..\' 
already exists
 W [03/May/2021:11:20:51 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id \'Letters-DeviceN..\' 
already exists
Date: Mon May  3 11:39:40 2021
InstallationDate: Installed on 2021-04-27 (5 days ago)
InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Lpstat: device for Letters: 
dnssd://HP%20LaserJet%20600%20M602%20%5B66D356%5D._ipp._tcp.local/?uuid=a9f85a02-21b1-11e3-9d3a-1556bd6228ad
MachineType: LENOVO 10ST00A6US
Papersize: letter
PpdFiles: Letters: HP LaserJet 600 M602, driverless, cups-filters 1.27.4
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=abf53fc0-1910-4d2d-b58d-2e356575d519 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/17/2020
dmi.bios.release: 1.80
dmi.bios.vendor: LENOVO
dmi.bios.version: M1UKT50A
dmi.board.name: 312A
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305279232807
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias: 
dmi:bvnLENOVO:bvrM1UKT50A:bd02/17/2020:br1.80:efr1.24:svnLENOVO:pn10ST00A6US:pvrThinkCentreM720s:rvnLENOVO:rn312A:rvrSDK0J40697WIN3305279232807:cvnLENOVO:ct3:cvrNone:
dmi.product.family: ThinkCentre M720s
dmi.product.name: 10ST00A6US
dmi.product.sku: LENOVO_MT_10ST_BU_Think_FM_ThinkCentre M720s
dmi.product.version: ThinkCentre M720s
dmi.sys.vendor: LENOVO
modified.conffile..etc.cups.snmp.conf: [deleted]

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


** Tags: amd64 apport-bug focal third-party-packages

** Summary changed:

- lptoptions command won't create a new instance
+ lpoptions command won't create a new instance

** Summary changed:

- lpoptions command won't create a new instance
+ lpoptions command won't create a new printer instance

** Description changed:

  Running the following command :
- lpoptions -p Letters/test -o InputSlot=Tray5
+ sudo lpoptions -p Letters/test -o InputSlot=Tray5
  
  returns without error
  
  sudo lpoptions -p Letters/test -l
  Shows that the the above command had no effect InputSlot=Auto
  
  After running the commands, there is no file /etc/cups/lpoptions
  
- Even if an lptoptions file is created manually, it has no effect.
+ Even if an lpoptions file is created manually, it has no effect.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CupsErrorLog:
-  W [27/Apr/2021:13:43:24 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id \'PDF-Gray..\' already 
exists
-  W [27/Apr/2021:13:43:24 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id \'PDF-RGB..\' already 
exists
-  W [03/May/2021:11:20:51 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id \'Letters-Gray..\' 
already exists
-  W [03/May/2021:11:20:51 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id \'Letters-DeviceN..\' 
already exists
+  W [27/Apr/2021:13:43:24 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id \'PDF-Gray..\' already 
exists
+  W [27/Apr/2021:13:43:24 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id \'PDF-RGB..\' already 
exists
+  W [03/May/2021:11:20:51 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id \'Letters-Gray..\' 
already exists
+  W [03/May/2021:11:20:51 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id \'Letters-DeviceN..\' 
already exists
  Date: Mon

[Touch-packages] [Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall

2021-05-03 Thread Sergio Durigan Junior
Thanks for following up.

It is hard to say what might be happening and whether switching to MDB
will help or not.  I'm still puzzled that you're seeing this hang on a
relatively new version of OpenLDAP.  The fact that it didn't happen on
Trusty may be helpful when diagnosing the issue, but I can't say for
sure.

I will wait until you are able to provide a backtrace or more
information.  I will see about talking to other OpenLDAP experts here
and see if this bug rings any bells for them.

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

Title:
  slapd enter in infinite loop on sched_yield syscall

Status in openldap package in Ubuntu:
  Incomplete

Bug description:
  On a production server, sometimes slapd become unbresponsive, some threads 
loops in sched_yield syscall and consumme all CPU.
  To recover, slapd needs to restart.
  No related information is reported in log file.
  All same issues in OpenLDAP upstream project are old and fixed.
  So maybe this issue affects only Ubuntu package.
  It occurs randomly, so I have no steps to reproduce.

  
  OS : Bionic

  Openldap version:

  libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10
 
  libldap-common 2.4.45+dfsg-1ubuntu1.10
 
  slapd  2.4.45+dfsg-1ubuntu1.10
 

  Modules loaded:

  olcModuleLoad: {0}back_bdb
  olcModuleLoad: {1}syncprov
  olcModuleLoad: {2}back_monitor
  olcModuleLoad: {3}memberof.la
  olcModuleLoad: {4}refint.la
  olcModuleLoad: {5}rwm
  olcModuleload: {6}back_ldap

  
  Backend is BDB. slapd run in (single) master - (multi) slave mode.

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

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


[Touch-packages] [Bug 1925730] Re: Dell XPS 17 (Ubuntu 21.04) - No sound AT ALL upon fresh installation

2021-05-03 Thread edurenye
This also happens in Ubuntu 21.04 installed from scratch and with Kernel
5.11.0-16-generic, so this issue is not fixed by updating the kernel to
5.11.

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

Title:
  Dell XPS 17 (Ubuntu 21.04) - No sound AT ALL upon fresh installation

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  New laptop - Dell XPS 17, bought in 2020. Upon installation of Ubuntu
  21.04 sound does not work at all. System settings only show one audio
  output - "Dummy output". Audio input does not have even that, just an
  empty drop-down list.

  Issue can be fixed if we load a custom sound driver as described here:
  https://blog.fts.scot/2020/07/04/dell-xps-2020-how-to-get-audio-
  working-on-linux/

  That poses a security risk however and according to the author of the
  article is not necessary since mainline Kernel release 5.11 now has
  required device headers included.

  ...

  lspci output:

  user@MYPC:~$ lspci -v | grep -i -A 10 audio
  00:1f.3 Multimedia audio controller: Intel Corporation Comet Lake PCH cAVS
Subsystem: Dell Comet Lake PCH cAVS
Flags: bus master, fast devsel, latency 64, IRQ 229, IOMMU group 16
Memory at 609b218000 (64-bit, non-prefetchable) [size=16K]
Memory at 609b10 (64-bit, non-prefetchable) [size=1M]
Capabilities: 
Kernel driver in use: sof-audio-pci
Kernel modules: snd_hda_intel, snd_sof_pci
  --
  01:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio 
Controller (rev a1)
Subsystem: Dell TU106 High Definition Audio Controller
Flags: bus master, fast devsel, latency 0, IRQ 17, IOMMU group 1
Memory at 7300 (32-bit, non-prefetchable) [size=16K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  Looked around for soundwire drivers, found this:

  user@MYPC:~$ lsmod | grep soundwire
  soundwire_intel40960  2 snd_sof_intel_hda_common,snd_intel_dspcfg
  soundwire_generic_allocation16384  1 soundwire_intel
  soundwire_cadence  32768  1 soundwire_intel
  soundwire_bus  77824  7 
regmap_sdw,soundwire_intel,snd_soc_rt715,soundwire_generic_allocation,soundwire_cadence,snd_soc_rt711,snd_soc_rt1308_sdw
  snd_soc_core  294912  8 
soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_rt715,snd_soc_hdac_hda,snd_soc_rt711,snd_soc_dmic,snd_soc_rt1308_sdw
  snd_pcm   118784  14 
snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_sof_intel_ipc,snd_soc_rt715,snd_compress,snd_soc_core,snd_soc_rt711,snd_soc_rt1308_sdw,snd_hda_core,snd_pcm_dmaengine

  Maybe using the soundwire_intel driver would fix the problem? Need to
  keep digging. Will post an update if I have any progress.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  iamarkadyt   1593 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 23 00:18:15 2021
  InstallationDate: Installed on 2021-04-23 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: TU106 High Definition Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  iamarkadyt   1593 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA NVidia, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2020
  dmi.bios.release: 1.4
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0YK6XT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd09/03/2020:br1.4:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0YK6XT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 17 9700
  dmi.product.sku: 098F
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925730/+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 1926547] Re: Add Dell Privacy Mic Mute Key mapping

2021-05-03 Thread Balint Reczey
I've picked up the fix for the next upload to Impish, then it can be
SRUd together with other fixes.

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

Title:
  Add Dell Privacy Mic Mute Key mapping

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
     GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

  [Other Info]

   * The change can only work with kernel commit on some specific hardware, ex. 
Latitude 9520. The commit series is 
"hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree.
     https://patchwork.kernel.org/project/alsa-devel/list/?series=465445
   * This change has been verified on Dell machine.

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

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


[Touch-packages] [Bug 1926976] Re: during mouse drag operations I'm getting undesired/unprompted dropping and potentially picking up of something else

2021-05-03 Thread buchs
One more bit of description, though it is rare, this problem does happen
when I am dragging a text selection. In my most recent example of that,
the text selection jumped to a window move. I also didn't mention the
detail that the location of the unrequested drop will be offset from the
location of the unrequested pick up a new drag.

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

Title:
  during mouse drag operations I'm getting undesired/unprompted dropping
  and potentially picking up of something else

Status in xorg package in Ubuntu:
  New

Bug description:
  I am not really sure this is an Xorg problem. Since my last system
  update (upon the system prompting), I think less than a week ago, I
  have noticed this troubling intermittent behavior. I go to drag
  (mouse-initiated) a window across some screen distances (between
  external monitors and my laptop's builtin monitor) the window will get
  dropped without me releasing the mouse button before arriving at my
  desired drop point. More than half the times this happens, something
  will immediately be picked up in a drag operation. Sometimes it is
  another window that begins being moved. Other times it is a window
  resize operation that is picked up. A third option is the selection of
  text.

  I have noticed that most of the time it is triggered when I am moving
  rapidly (though no more rapidly than I have done successfully in the
  past). Sometimes it happens when I pause during the drag operation. It
  even happens infrequently when I am dragging slowly.

  Often I can just go back and pick up the window and complete the
  operation. However, sometimes the problem just keeps happening until I
  give up and go away for 5 minutes or so.

  I have a stock configuration of 20.04. I keep it updated and haven't
  changed anything significant about X, Gnome, etc. I have done a few
  tweaks, but nothing I can think of that would relate to this problem.
  My laptop, a Dell XPS 13, uses a USB 3.1 hub and through that drives
  two monitors via HDMI. My mouse is bluetooth - Logitech MX Vertical. I
  don't believe I have installed any proprietary drivers. My 3 displays
  are arranged into an inverted "L" shape, as the laptop display is
  "below" and identically sized to the 27" monitor "above" it. The other
  27" monitor is to the left of the first one.

  Some, potentially useful, debugging info:

  $ lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  $ apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu14
Candidate: 1:7.7+19ubuntu14
Version table:
   *** 1:7.7+19ubuntu14 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  $ bluetoothctl --version
  bluetoothctl: 5.53
  $ hciconfig -a
  hci0: Type: Primary  Bus: USB
BD Address: 9C:B6:D0:99:27:2C  ACL MTU: 1024:8  SCO MTU: 50:8
UP RUNNING
RX bytes:21743080 acl:954252 sco:0 events:141080 errors:0
TX bytes:6895 acl:169 sco:0 commands:208 errors:0
Features: 0xff 0xfe 0x8f 0xfe 0xd8 0x3f 0x5b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF
Link mode: SLAVE ACCEPT
Name: 'kbuchs'
Class: 0x0c010c
Service Classes: Rendering, Capturing
Device Class: Computer, Laptop
HCI Version: 4.2 (0x8)  Revision: 0x0
LMP Version: 4.2 (0x8)  Subversion: 0x25a
Manufacturer: Qualcomm (29)

  $ bluetoothctl
  Agent registered
  [CHG] Controller 9C:B6:D0:99:27:2C Pairable: yes
  [MX Vertical]# show
  Controller 9C:B6:D0:99:27:2C (public)
Name: kbuchs
Alias: kbuchs
Class: 0x000c010c
Powered: yes
Discoverable: no
DiscoverableTimeout: 0x00b4
Pairable: yes
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0535
Discovering: no
  Advertising Features:
ActiveInstances: 0x00
SupportedInstances: 0x05
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
  [MX Vertical]# devices
  Device D4:51:67:AF:3D:FF MX Vertical
  [MX Vertica

[Touch-packages] [Bug 1861408] Re: firefox apparmor messages

2021-05-03 Thread Launchpad Bug Tracker
** Branch linked: lp:~mozillateam/firefox/firefox-beta.groovy

** Branch linked: lp:~mozillateam/firefox/firefox-beta.focal

** Branch linked: lp:~mozillateam/firefox/firefox-beta.bionic

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

Title:
  firefox apparmor messages

Status in apparmor package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
  19.3.

  i see there is newer ubuntu version in
  
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
  , 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
  apparmor.

  i have not found a page for firefox bugs in linux mint sites, so i
  belive i should report here. but i have also asked about that in linux
  mint's irc and then github.

  i have enabled apparmor for firefox and see these types of messages in
  syslog:

  Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
  [system] Activating via systemd: service
  name='org.freedesktop.hostname1' unit='dbus-
  org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
  pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")

  Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5525.077960] audit: type=1400 audit(1580226276.440:27):
  apparmor="DENIED" operation="capable"
  profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
  comm="firefox" capability=21  capname="sys_admin"

  Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
  uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/RealtimeKit1"
  interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
  name="org.freedesktop.RealtimeKit1" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
  member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/Private/RemoteVolumeMonitor"
  interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
  mask="send" name=":1.35" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
  member="ListMounts2" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
  member="LookupMount" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
  [system] Activating via systemd: service
  name='org.freedesktop.hostname1' unit='dbus-
  org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
  pid=15948 comm="/usr/lib/firefox/firefox "
  label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")

  Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
  uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/hostname1"
  interface="org.freedesktop.DBus.Properties" member="GetAll"
  mask="send" name=":1.120" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177
  peer_label="unconfined"

  Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
  member="Change" mask="send" name="ca.desrt.dconf" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1370
  peer_label="unconfined"

  Jan 28 21:51:30 dinar-HP-Pavilion-g7-Notebook-PC kernel:
  [10131.880788] audit: type=1400 audit(1580237490.777:123):
  apparmor="DENIED" operation="open"
  profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
  name="/home/dinar/.cache/mesa_shader_cache/index" pid=19720
  comm="firefox" requested_mask="wrc"

[Touch-packages] [Bug 1754140] Re: Gnome gets stuck in overview mode

2021-05-03 Thread Iiro Ullin
I have started getting this very bug after upgrade to hippo (21.04).
Happens much more often when the "Activities" hot corner extension is
enabled. But also happens without it...

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

Title:
  Gnome gets stuck in overview mode

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 17.10, and I have repeatedly had a problem with the
  desktop environment getting stuck in overview mode.  When stuck, I can
  close and select windows, and access the menus at on the top bar, but
  I cannot exit overview mode.  The only solution I've found is to log
  out and log back in.  I'm not exactly sure what combination of
  circumstances causes it to happen, but it seems to happen more often
  if invoked via the corner hover point.  It also happens in both
  Wayland and Xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-desktop 1.404.1
  Uname: Linux 4.14.15-041415-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Mar  7 11:02:02 2018
  InstallationDate: Installed on 2017-05-04 (307 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to artful on 2017-10-29 (129 days ago)

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

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


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

2021-05-03 Thread sacha
Public bug reported:

Ubuntu 21.04 Freeze sometime ( using wayland ) . A black screen appear from top 
to bottom and ubuntu doesn't react to any keyboard shortcut.  It's appears, 
maybe after 2 hours of work.
I didn't see this bug with my previous ubuntu 20.10.
My computer is a new DELL XPS 13 - intel core i7. I disabled the 4K screen and 
I am using a resolution 1920x1080. I enabled the night mode.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue May  4 00:10:39 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
   Subsystem: Dell Iris Xe Graphics [1028:0a5c]
InstallationDate: Installed on 2021-04-30 (3 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: Dell Inc. XPS 13 9305
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/usr/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=37473b6f-8714-4a48-91c1-f6964b09347d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/13/2021
dmi.bios.release: 1.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.1
dmi.board.name: 0PPYW4
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.1:bd01/13/2021:br1.0:svnDellInc.:pnXPS139305:pvr:rvnDellInc.:rn0PPYW4:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9305
dmi.product.sku: 0A5C
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.104-1build1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: amd64 apport-bug freeze hirsute ubuntu

** Description changed:

- Ubuntu 21.04 Freeze sometime ( using wayland ) . A black screen appear from 
top to bottom and ubuntu doesn't react to any keyboard.  It's appears, maybe 
after 2 hours of work. 
- I didn't see this bug with my previous ubuntu 20.10. 
+ Ubuntu 21.04 Freeze sometime ( using wayland ) . A black screen appear from 
top to bottom and ubuntu doesn't react to any keyboard shortcut.  It's appears, 
maybe after 2 hours of work.
+ I didn't see this bug with my previous ubuntu 20.10.
  My computer is a new DELL XPS 13 - intel core i7. I disabled the 4K screen 
and I am using a resolution 1920x1080. I enabled the night mode.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  4 00:10:39 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
-  Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
-Subsystem: Dell Iris Xe Graphics [1028:0a5c]
+  Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
+    Subsystem: Dell Iris Xe Graphics [1028:0a5c]
  InstallationDate: Installed on 2021-04-30 (3 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. XPS 13 9305
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=fr_FR.UTF-8
-  SHELL=/usr/bin/zsh
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SH

[Touch-packages] [Bug 1926254] Re: x509 Certificate verification fails when basicConstraints=CA:FALSE, pathlen:0 on self-signed leaf certs

2021-05-03 Thread Seth Arnold
Matthew, thanks so much! sounds good to me.

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

Title:
  x509 Certificate verification fails when
  basicConstraints=CA:FALSE,pathlen:0 on self-signed leaf certs

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Focal:
  In Progress
Status in openssl source package in Groovy:
  In Progress
Status in openssl source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  In openssl 1.1.1f, the below commit was merged:

  commit ba4356ae4002a04e28642da60c551877eea804f7
  Author: Bernd Edlinger 
  Date:   Sat Jan 4 15:54:53 2020 +0100
  Subject: Fix error handling in x509v3_cache_extensions and related functions
  Link: 
https://github.com/openssl/openssl/commit/ba4356ae4002a04e28642da60c551877eea804f7

  This introduced a regression which caused certificate validation to
  fail when certificates violate RFC 5280 [1], namely, when a
  certificate has "basicConstraints=CA:FALSE,pathlen:0". This
  combination is commonly seen by self-signed leaf certificates with an
  intermediate CA before the root CA.

  Because of this, openssl 1.1.1f rejects these certificates and they
  cannot be used in the system certificate store, and ssl connections
  fail when you try to use them to connect to a ssl endpoint.

  The error you see when you try verify is:

  $ openssl verify -CAfile CA/rootCA_cert.pem -untrusted CA/subCA_cert.pem 
user1_cert.pem
  error 20 at 0 depth lookup: unable to get local issuer certificate
  error user1_cert.pem: verification failed

  The exact same certificates work fine on Xenial, Bionic and Hirsute.

  [1] https://tools.ietf.org/html/rfc5280.html

  [Testcase]

  We will create our own root CA, intermediate CA and leaf server
  certificate.

  Create necessary directories:

  $ mkdir reproducer
  $ cd reproducer
  $ mkdir CA

  Write openssl configuration files to disk for each CA and cert:

  $ cat << EOF >> rootCA.cnf
  [ req ]
  prompt  = no
  distinguished_name  = req_distinguished_name
  x509_extensions = usr_cert

  [ req_distinguished_name ]
  C  = DE
  O  = Test Org
  CN = Test RSA PSS Root-CA

  [ usr_cert ]
  basicConstraints= critical,CA:TRUE
  keyUsage= critical,keyCertSign,cRLSign
  subjectKeyIdentifier= hash
  authorityKeyIdentifier  = keyid:always
  EOF

  $ cat << EOF >> subCA.cnf
  [ req ]
  prompt  = no
  distinguished_name  = req_distinguished_name
  x509_extensions = usr_cert

  [ req_distinguished_name ]
  C  = DE
  O  = Test Org
  CN = Test RSA PSS Sub-CA

  [ usr_cert ]
  basicConstraints= critical,CA:TRUE,pathlen:0
  keyUsage= critical,keyCertSign,cRLSign
  subjectKeyIdentifier= hash
  authorityKeyIdentifier  = keyid:always
  EOF

  $ cat << EOF >> user.cnf
  [ req ]
  prompt  = no
  distinguished_name  = req_distinguished_name
  x509_extensions = usr_cert

  [ req_distinguished_name ]
  C  = DE
  O  = Test Org
  CN = Test User

  [ usr_cert ]
  basicConstraints= critical,CA:FALSE,pathlen:0
  keyUsage= critical,digitalSignature,keyAgreement
  extendedKeyUsage= clientAuth,serverAuth
  subjectKeyIdentifier= hash
  authorityKeyIdentifier  = keyid:always
  EOF

  Then generate the necessary RSA keys and form certificates:

  $ openssl genpkey -algorithm RSA-PSS -out rootCA_key.pem -pkeyopt 
rsa_keygen_bits:2048
  $ openssl req -config rootCA.cnf -set_serial 01 -new -batch -sha256 -nodes 
-x509 -days 9125 -out CA/rootCA_cert.pem -key rootCA_key.pem -sigopt 
rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1

  $ openssl genpkey -algorithm RSA-PSS -out subCA_key.pem -pkeyopt 
rsa_keygen_bits:2048
  $ openssl req -config subCA.cnf -new -out subCA_req.pem -key subCA_key.pem 
-sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1
  $ openssl x509 -req -sha256 -in subCA_req.pem -CA CA/rootCA_cert.pem -CAkey 
rootCA_key.pem -out CA/subCA_cert.pem -CAserial rootCA_serial.txt 
-CAcreateserial -extfile subCA.cnf -extensions usr_cert -days 4380 -sigopt 
rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1
  $ c_rehash CA

  $ openssl genpkey -algorithm RSA-PSS -out user1_key.pem -pkeyopt 
rsa_keygen_bits:2048
  $ openssl req -config user.cnf -new -out user1_req.pem -key user1_key.pem 
-sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1
  $ openssl x509 -req -sha256 -in user1_req.pem -CA CA/subCA_cert.pem -CAkey 
subCA_key.pem -out user1_cert.pem -CAserial subCA_serial.txt -CAcreateserial 
-extfile user.cnf -extensions usr_cert -days 1825 -sigopt rsa_padding_mode:pss 
-sigopt rsa_pss_saltlen:-1

  Now, let's try verify the generated certificates:

  $ openssl version
  OpenSSL 1.1.1f  31 Mar 2020
  $ openssl verify -CAfile CA/rootCA_cert.pem -untrusted CA/subCA_cert.pem 
user1_cert.pem
  error 20 at 0 depth lookup: unable to get

[Touch-packages] [Bug 1902768] Re: [ASUS ROG STRIX B550-F] headphone not correctly detected on 20.10

2021-05-03 Thread Daniel van Vugt
Alright, maybe it was bug 1897965 but Fix Released regardless.

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

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

Title:
  [ASUS ROG STRIX B550-F] headphone not correctly detected on 20.10

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  In 20/04 sound worked via headphones worked fine. After upgrade no
  sound is heard and the audio output device list only has HDMI and
  S/PDIF as possible choices. Windows 10 on the same machine works
  without problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Nov  3 20:39:59 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-09-19 (44 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to groovy on 2020-11-02 (0 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-12-10 (137 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: pulseaudio 1:13.99.2-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Tags:  groovy
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1004
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B550-F GAMING
  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.:bvr1004:bd08/13/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-FGAMING: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: ASUS

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

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


[Touch-packages] [Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]

2021-05-03 Thread Daniel van Vugt
^^^ Bug 1925320

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

Title:
  gnome-shell/gnome-session-check-accelerated-gl-helper crashed with
  SIGSEGV in cso_destroy_context() [r300_dri.so]

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa package in Fedora:
  Confirmed

Bug description:
  Graphical user interface is not coming up upon start. Only SSH is
  possible.

  lsb_release -rd:

  Description:  Ubuntu 20.10
  Release:  20.10

  dmesg:

  [   11.985343] gnome-session-c[1013]: segfault at 0 ip  sp 
7fff7679ca48 error 14 in 
gnome-session-check-accelerated-gl-helper[56020e238000+2000]
  [   11.985352] Code: Unable to access opcode bytes at RIP 0xffd6.
  [   14.216117] gnome-shell[1094]: segfault at 0 ip  sp 
7ffeddff9f88 error 14
  [   14.216122] Code: Unable to access opcode bytes at RIP 0xffd6.
  [   15.316292] gnome-shell[1109]: segfault at 0 ip  sp 
7ffc70716198 error 14
  [   15.316297] Code: Unable to access opcode bytes at RIP 0xffd6.

  apt-cache policy:

  gnome-session:
Installed: (none)
Candidate: 3.38.0-1ubuntu1
Version table:
   3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages
  gnome-session-bin:
Installed: 3.38.0-1ubuntu1
Candidate: 3.38.0-1ubuntu1
Version table:
   *** 3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-session-common:
Installed: 3.38.0-1ubuntu1
Candidate: 3.38.0-1ubuntu1
Version table:
   *** 3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages
  100 /var/lib/dpkg/status

  /var/crash: see attachment

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

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


[Touch-packages] [Bug 1925739] Re: Strange sound when speaker is muted

2021-05-03 Thread Daniel van Vugt
If the problem was /sys/module/snd_hda_intel/parameters/power_save then
this should be assigned to the kernel.

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

** Summary changed:

- Strange sound when speaker is muted
+ [Dell Vostro 3668] Strange sound when speaker is muted

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

Title:
  [Dell Vostro 3668] Strange sound when speaker is muted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  when everything is off even sound is muted I am getting sound like connecting 
3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming 
unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin 
when I upgrade pkgs.
  ubuntu 20.10 all updated.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bapi   1453 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2021-04-22 (2 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.2-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Tags:  groovy
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/30/2020
  dmi.bios.release: 1.14
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.1
  dmi.board.name: 0VFD52
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.1:bd09/30/2020:br1.14:svnDellInc.:pnVostro3668:pvr:rvnDellInc.:rn0VFD52:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3668
  dmi.product.sku: 0760
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1925824] Re: [Avita NS14A2] Screen doesn't display on warm boot and turning on after Suspend (i915 0000:00:02.0: [drm] *ERROR* failed to enable link training)

2021-05-03 Thread Daniel van Vugt
** Summary changed:

- Display Error (hardware bug: Screen doesnt display on warm boot and  turning 
on after Suspend)
+ [Avita NS14A2] Screen doesn't display on warm boot and  turning on after 
Suspend (i915 :00:02.0: [drm] *ERROR* failed to enable link training)

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

** Tags added: regression-update

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

Title:
  [Avita NS14A2] Screen doesn't display on warm boot and  turning on
  after Suspend (i915 :00:02.0: [drm] *ERROR* failed to enable link
  training)

Status in linux package in Ubuntu:
  New

Bug description:
  I have Avita NS14A2 laptop where i dual boot windows 10 and Ubuntu
  20.04. In past few days might be after installing updates I am facing
  issue where my screen dont display at all when i first boot it and
  after multiple force shut down and then boot in it work, even on doing
  Suspend and then opening it, screen didnt not display for about 5-6
  minutes, and then shows login screen.

  
  On checking logs software i got these line on those time stamp when display 
doesnt shows 

  this is the line:

  (Hardware) i915 :00:02.0: [drm] *ERROR* failed to enable link
  training

  
  this line continues for about 30-40 times on average during time when screen 
doesnt display anything on turing on. So I think there is some issue with it.

  
  As I primarily use Ubuntu 20.04 so didnt check it with windows 10

  
  but on doing cold boot it didnt even shows the boot menu where i can choose 
between Ubuntu 20.04 and Windows 10. 

  But once screen starts displaying i dont see that error in logs
  software anymore and screen doesnt freezes or hangs. It only happen
  when i either open after suspend or do cold boot.

  
  Please consider this issue on urgent basis, as it takes a lot of time and 
efforts to make screen display something. :(

  
  And please let me know whether I should do fresh installation of ubuntu 20.04 
again.

  
  Sorry for any grammatical mistakes. :)

  
  Thank you,
  Bipul Harsh
  bipulharsh...@gmail.com

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 23 20:36:38 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation UHD Graphics 620 [8086:5917]
  InstallationDate: Installed on 2020-11-22 (151 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: AVITA NS14A2
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=011d61ba-ef72-40ed-9957-25830622d9c7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2019
  dmi.bios.release: 0.22
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: BSR5IPHK-14UF80-AVI-V22
  dmi.board.asset.tag: Default string
  dmi.board.name: 6614UFWC80
  dmi.board.vendor: AVITA
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: AVITA
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 0.22
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrBSR5IPHK-14UF80-AVI-V22:bd04/19/2019:br0.22:efr0.22:svnAVITA:pnNS14A2:pvrDefaultstring:rvnAVITA:rn6614UFWC80:rvrDefaultstring:cvnAVITA:ct10:cvrDefaultstring:
  dmi.product.family: CN6614
  dmi.product.name: NS14A2
  dmi.product.sku: CN6614F56U1IN-MB
  dmi.product.version: Default string
  dmi.sys.vendor: AVITA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/linux/+bug/1925824/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch

[Touch-packages] [Bug 1926009] Re: Incomplete display of text

2021-05-03 Thread Daniel van Vugt
It appears 'amdgpu' is the wrong driver for this system. 'radeon' is the
correct driver. Maybe you had a config file that was forcefully loading
the wrong one?

** Summary changed:

- Incomplete display of text
+ [amdgpu] Incomplete display of text

** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (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/1926009

Title:
  [amdgpu] Incomplete display of text

Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid

Bug description:
  Ubuntu release: 20.04.1

  * What is expected to happen.

  All gui text elements to display complete words.

  * What actually happens.

  Since a recent update, gui text displays incompletely.

  I'm posting this with some difficulty from the affected system, but
  have noted similar issues being experienced by others and I share
  links below:

  https://askubuntu.com/questions/1328937/ubuntu-20-04-only-shows-half-text
  https://askubuntu.com/questions/1329312/xubuntu-20-04-incomplete-words
  
https://askubuntu.com/questions/1329059/on-the-desktop-xfce-displays-text-incorrectly
  https://askubuntu.com/questions/1332354/ubuntu-20-04-is-showing-a-bad-text

  The issues above seem to suggest the the issue may lie with the AMD
  graphics driver, although in my case I think I am using the 'radeon'
  open source driver.

  The issue occurs regardless of me use the current or previous kernel
  version installed.

  Please let me know if there is any more information that I can
  provide, and I will do my best to get it to you.

  Many thanks,
  Mark.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Apr 24 12:07:35 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] 
[1002:990e] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8570D] [1043:8526]
  MachineType: NOVATECH LTD MBB-66004G
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55-M LK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6102:bd05/03/2013:svnNOVATECHLTD:pnMBB-66004G:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnNOVATECHLTD:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MBB-66004G
  dmi.product.sku: SKU
  dmi.product.version: 1.0
  dmi.sys.vendor: NOVATECH LTD
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-1ubuntu1~f~mesarc2
  version.libgl1-mesa-dri: libgl1-mesa-dri 
21.1.0~rc2+git2104212235.09d505a3ab7~f~mesarc2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/xserver-xorg-video-amdgpu/+bug/1926009/+subscriptions

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


[Touch-packages] [Bug 1926023] Re: display broken on logout

2021-05-03 Thread Daniel van Vugt
** Tags added: nvidia

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

** Package changed: xorg-server (Ubuntu) => nvidia-graphics-drivers-460
(Ubuntu)

** Summary changed:

- display broken on logout
+ [nvidia] display broken on logout

** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
   Status: Incomplete => 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/1926023

Title:
  [nvidia] display broken on logout

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New

Bug description:
  I can login and use the system, but when I logout, the monitor
  complains that it can't display the video mode.  Pressing various keys
  and clicking randomly doesn't help, I have to press the hard reset
  button to login again.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:07: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  460.73.01  Thu Apr  1 
21:40:36 UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 24 18:13:51 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] TU106 [GeForce RTX 
2060 SUPER] [1462:c752]
  InstallationDate: Installed on 2021-04-24 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=901be83b-8764-4544-acd9-b13439d1ab8f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/01/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: B450M Pro4-F
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/01/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4-F:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1926023/+subscriptions

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


[Touch-packages] [Bug 1926032] Re: Screen "disconnects" when updating screen buffer

2021-05-03 Thread Daniel van Vugt
This sounds like an HDMI connection/signalling problem. Please check to
see if a direct connection (no receiver), and even a new cable, exhibits
the same problem.

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

** Summary changed:

- Screen "disconnects" when updating screen buffer
+ [i915] Screen "disconnects" when updating screen buffer

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

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

** Changed in: xorg-server (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/1926032

Title:
  [i915] Screen "disconnects" when updating screen buffer

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have a problem in which the screen will behave as if I pulled the
  HDMI or turned the computer off (no source) for a few seconds until
  the screen comes back on again. This happens a lot when I open a new
  window, moves the mouse after it has been still for a while or I open
  a new window or move the current window.

  I can watch a whole movie without this problem but as soon as I pause
  or touch the controls of VLC or move the mouse the problem reocurr. It
  seems to be after a certain idle period most of the time, but not
  always. Sometimes it happens many times in a row.

  The setup is my home built media PC with intel integrated graphics
  (i5-9400) connected to a philips 55" TV (55POS901F) through a Pioneer
  AV receiver.

  I have tried probably every possible resolution and screen update
  frequency and the problem is still there.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 24 21:57:54 2021
  DistUpgraded: 2020-12-01 07:11:08,428 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation UHD Graphics 630 (Desktop 9 Series) 
[1849:3e98]
  InstallationDate: Installed on 2020-12-01 (144 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-66-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-12-01 (144 days ago)
  dmi.bios.date: 05/14/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.10
  dmi.board.name: H310CM-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.10:bd05/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH310CM-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/linux/+bug/1926032/+subscriptions

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


[Touch-packages] [Bug 1926050] Re: Web benchmark freezing and crashing the system

2021-05-03 Thread Daniel van Vugt
Next time the problem happens, after rebooting please run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

Please also follow these instructions to check for application crashes:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

** Package changed: linux (Ubuntu) => linux-hwe-5.8 (Ubuntu)

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

** Summary changed:

- Web benchmark freezing and crashing the system
+ [radeon] Web benchmark freezing and crashing the system

** No longer affects: mesa (Ubuntu)

** No longer affects: wayland (Ubuntu)

** No longer affects: xorg-server (Ubuntu)

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

Title:
  [radeon] Web benchmark freezing and crashing the system

Status in linux-hwe-5.8 package in Ubuntu:
  Incomplete

Bug description:
  Expected behavior: perform the "Basemark Web 3.0" benchmark (Firefox
  87 and 88), at most a loss of performance.

  Real behavior: the benchmark completely crashes the system in one of
  the initial stages (4). The screen presents graphical distortion (it
  never happens), intense crashes and sometimes it is solved with the
  automatic suspension of the computer (which remains on at times). But
  it doesn't usually come back from the crash.

  The problem happens with the onboard ATI RADEON 3000 (RS780 driver)
  and it happens in both xorg and wayland. Ubuntu and kernel duly
  updated to the present date.

  Crash moment: WebGL 1.0.2 Test (test 4/20); "Loading
  scene_uv2.DAE"

  Benchmark website: https://web.basemark.com/
  Motherboard: GA78LMT
  Ubuntu 20.04.2 LTS
  Kernel 5.8.0-50-generic
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  poe1860 F pulseaudio
   /dev/snd/pcmC2D0p:   poe1860 F...m pulseaudio
   /dev/snd/controlC0:  poe1860 F pulseaudio
   /dev/snd/controlC1:  poe1860 F pulseaudio
  BootLog: Error: [Errno 13] Permissão recusada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2021-03-25 15:17:02,784 DEBUG /openCache(), new cache size 67025
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] 
(prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000]
  InstallationDate: Installed on 2021-03-04 (51 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
  Package: xorg-server (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash radeon.audio=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.11
  Tags:  focal wayland-session wayland-session ubuntu
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: Upgraded to focal on 2021-03-25 (30 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare
  _MarkForUpload: True
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: SEx
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/linux-hwe-5.8/+bug/1926050/+subscriptions

-- 
Mailing list: https://launchpad.net/~t

[Touch-packages] [Bug 1927026] [NEW] Monitor Display problem

2021-05-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Dual boot OS Windows 7x64 & Ubuntu 20.04 64-bit.While booting everything
is OD. But as soon as password is entered, brightness of the screen is
so blurred that it is practically impossible to work. Further the
problem is common for all programs run on the system.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
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: Tue May  4 06:49:21 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 5.8.0-49-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 5.8.0-50-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Foxconn International, Inc. Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller [105b:0d93]
InstallationDate: Installed on 2021-01-24 (99 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: DIGILITE DL-H61MXP.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=d6ed0705-777b-4a1a-9121-6963b7c2d394 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/16/2014
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: C36DLS09
dmi.board.name: DL-H61MXP
dmi.board.vendor: DIGILITE
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC36DLS09:bd01/16/2014:br4.6:svnDIGILITE:pnDL-H61MXP.:pvrTobefilledbyO.E.M.:rvnDIGILITE:rnDL-H61MXP:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: DL-H61MXP.
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: DIGILITE
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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 third-party-packages ubuntu
-- 
Monitor Display problem
https://bugs.launchpad.net/bugs/1927026
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


[Touch-packages] [Bug 1926145] Re: bluetooth disconnects and reconnects on 21.04

2021-05-03 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1926084 ***
https://bugs.launchpad.net/bugs/1926084

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1926084, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1926084
   Bluetooth speakers reconnect randomly

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

Title:
  bluetooth disconnects and reconnects on 21.04

Status in bluez package in Ubuntu:
  New

Bug description:
  Bluetooth speaker disconnects randomly and reconnects again. Problem
  occurred after upgrade to Ubuntu 21.04 ( -d ).

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

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


[Touch-packages] [Bug 1926084] Re: Bluetooth speakers reconnect randomly

2021-05-03 Thread Launchpad Bug Tracker
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/1926084

Title:
  [hirsute] Bluetooth speakers reconnect randomly

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth speakers reconnect randomly.
  The onlt workaround that seems to work is to remove speakers from paired 
devies, restart buetooth service and connect them once again. Once these stepss 
are performed connection become stable until reboot or hibernation.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluez 5.56-0ubuntu4
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sun Apr 25 17:22:11 2021
  InstallationDate: Installed on 2021-04-13 (12 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera
   Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth
   Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard 
and Mouse Combo
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO F0FA0066UA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-18 (6 days ago)
  dmi.bios.date: 03/31/2021
  dmi.bios.release: 1.32
  dmi.bios.vendor: LENOVO
  dmi.bios.version: O4VKT32A
  dmi.board.asset.tag: INVALID
  dmi.board.name: 371F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN 3424143288435
  dmi.chassis.type: 13
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.13
  dmi.modalias: 
dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1:
  dmi.product.family: IdeaCentre AIO 5 27IMB05
  dmi.product.name: F0FA0066UA
  dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05
  dmi.product.version: IdeaCentre AIO 5 27IMB05
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 44:AF:28:F7:A9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:2239397 acl:225 sco:0 events:318945 errors:0
TX bytes:207283666 acl:315238 sco:0 commands:3564 errors:0

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

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


[Touch-packages] [Bug 1926084] Re: [hirsute] Bluetooth speakers reconnect randomly

2021-05-03 Thread Daniel van Vugt
** Summary changed:

- Bluetooth speakers reconnect randomly
+ [hirsute] Bluetooth speakers reconnect randomly

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

Title:
  [hirsute] Bluetooth speakers reconnect randomly

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth speakers reconnect randomly.
  The onlt workaround that seems to work is to remove speakers from paired 
devies, restart buetooth service and connect them once again. Once these stepss 
are performed connection become stable until reboot or hibernation.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluez 5.56-0ubuntu4
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sun Apr 25 17:22:11 2021
  InstallationDate: Installed on 2021-04-13 (12 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera
   Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth
   Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard 
and Mouse Combo
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO F0FA0066UA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-18 (6 days ago)
  dmi.bios.date: 03/31/2021
  dmi.bios.release: 1.32
  dmi.bios.vendor: LENOVO
  dmi.bios.version: O4VKT32A
  dmi.board.asset.tag: INVALID
  dmi.board.name: 371F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN 3424143288435
  dmi.chassis.type: 13
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.13
  dmi.modalias: 
dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1:
  dmi.product.family: IdeaCentre AIO 5 27IMB05
  dmi.product.name: F0FA0066UA
  dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05
  dmi.product.version: IdeaCentre AIO 5 27IMB05
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 44:AF:28:F7:A9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:2239397 acl:225 sco:0 events:318945 errors:0
TX bytes:207283666 acl:315238 sco:0 commands:3564 errors:0

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

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


[Touch-packages] [Bug 1927026] Re: Monitor Display problem

2021-05-03 Thread Ubuntu Foundations Team Bug Bot
*** This bug is a duplicate of bug 1924624 ***
https://bugs.launchpad.net/bugs/1924624

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

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

Title:
  Monitor Display problem

Status in xorg package in Ubuntu:
  New

Bug description:
  Dual boot OS Windows 7x64 & Ubuntu 20.04 64-bit.While booting
  everything is OD. But as soon as password is entered, brightness of
  the screen is so blurred that it is practically impossible to work.
  Further the problem is common for all programs run on the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  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: Tue May  4 06:49:21 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.8.0-49-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.8.0-50-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Foxconn International, Inc. Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller [105b:0d93]
  InstallationDate: Installed on 2021-01-24 (99 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: DIGILITE DL-H61MXP.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=d6ed0705-777b-4a1a-9121-6963b7c2d394 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C36DLS09
  dmi.board.name: DL-H61MXP
  dmi.board.vendor: DIGILITE
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC36DLS09:bd01/16/2014:br4.6:svnDIGILITE:pnDL-H61MXP.:pvrTobefilledbyO.E.M.:rvnDIGILITE:rnDL-H61MXP:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: DL-H61MXP.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: DIGILITE
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/+bug/1927026/+subscriptions

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


[Touch-packages] [Bug 1927026] Re: Monitor Display problem

2021-05-03 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1924624 ***
https://bugs.launchpad.net/bugs/1924624

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1924624, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1924624
   After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge) 
graphics a lot of glitches render screen unusable

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

Title:
  Monitor Display problem

Status in xorg package in Ubuntu:
  New

Bug description:
  Dual boot OS Windows 7x64 & Ubuntu 20.04 64-bit.While booting
  everything is OD. But as soon as password is entered, brightness of
  the screen is so blurred that it is practically impossible to work.
  Further the problem is common for all programs run on the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  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: Tue May  4 06:49:21 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.8.0-49-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.8.0-50-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Foxconn International, Inc. Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller [105b:0d93]
  InstallationDate: Installed on 2021-01-24 (99 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: DIGILITE DL-H61MXP.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=d6ed0705-777b-4a1a-9121-6963b7c2d394 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C36DLS09
  dmi.board.name: DL-H61MXP
  dmi.board.vendor: DIGILITE
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC36DLS09:bd01/16/2014:br4.6:svnDIGILITE:pnDL-H61MXP.:pvrTobefilledbyO.E.M.:rvnDIGILITE:rnDL-H61MXP:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: DL-H61MXP.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: DIGILITE
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/+bug/1927026/+subscriptions

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


[Touch-packages] [Bug 1905472] Re: aoetools initramfs hooks starts dhcclient for every intrface on boot

2021-05-03 Thread Launchpad Bug Tracker
[Expired for aoetools (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  aoetools initramfs hooks starts dhcclient for every intrface on boot

Status in aoetools package in Ubuntu:
  Expired
Status in ifupdown package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Expired
Status in netplan.io package in Ubuntu:
  Invalid

Bug description:
  After upgrade frpm 18LTS to 20LTS I've lost the network.

  Network is managed by ifupdown
  Netplan is not installed
  Network manger is disabled (masked)

  Yet, at boot, SOMETHING starts dhclient for every network interface.
  This has disastrous results - dhcp request succeeds on physical
  interface that is a base for a vlan-based interface, causing real dhcp
  request on to fail on vlan interface.

  Expected behavior - dhclient starts only for interfaces marked as dhcp
  in /etc/network/interfaces .

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: isc-dhcp-client 4.4.1-2.1ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-29.31~20.04.1-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Nov 25 00:07:45 2020
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1905472] Re: aoetools initramfs hooks starts dhcclient for every intrface on boot

2021-05-03 Thread Launchpad Bug Tracker
[Expired for initramfs-tools (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: initramfs-tools (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  aoetools initramfs hooks starts dhcclient for every intrface on boot

Status in aoetools package in Ubuntu:
  Expired
Status in ifupdown package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Expired
Status in netplan.io package in Ubuntu:
  Invalid

Bug description:
  After upgrade frpm 18LTS to 20LTS I've lost the network.

  Network is managed by ifupdown
  Netplan is not installed
  Network manger is disabled (masked)

  Yet, at boot, SOMETHING starts dhclient for every network interface.
  This has disastrous results - dhcp request succeeds on physical
  interface that is a base for a vlan-based interface, causing real dhcp
  request on to fail on vlan interface.

  Expected behavior - dhclient starts only for interfaces marked as dhcp
  in /etc/network/interfaces .

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: isc-dhcp-client 4.4.1-2.1ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-29.31~20.04.1-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Nov 25 00:07:45 2020
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1926770] Re: Bluetooth switches back on each reboot

2021-05-03 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1926770

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

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

Title:
  Bluetooth switches back on each reboot

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  
  Dear,

  When switching off Bluetooth in the settings menu, after each reboot
  and login into GNOME, the Bluetooth radio stack seems to be switched
  on again.

  Could this setting made by persistent over reboots?

  Thanks,

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

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


[Touch-packages] [Bug 1926121] Re: After suspending, no video signal appears after waking up

2021-05-03 Thread Daniel van Vugt
** Tags added: regression-release

** Tags added: amdgpu

** Summary changed:

- After suspending, no video signal appears after waking up
+ [amdgpu] After suspending, no video signal appears after waking up

** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (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/1926121

Title:
  [amdgpu] After suspending, no video signal appears after waking up

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

Bug description:
  No video signal appears after waking up my computer from suspending it
  and leaving it in this state for a while.

  This issue has appeared after upgrading from Ubuntu 20.10 (where
  suspending and waking up worked flawlessly) to 21.04. The computer in
  question is a HP Desktop - M01-F0230ng with a Ryzen 5 3400G processor.

  A similar issue exists with a Lenovo Desktop and a Ryzen 7 4600G.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 07:12:31 2021
  DistUpgraded: 2021-04-22 20:20:35,886 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-io-error-quark: Konnte Unterprozess 
"./xorg_fix_proprietary.py" nicht ausführen: Failed to execve: Datei oder 
Verzeichnis nicht gefunden (1))
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Picasso [103c:8643]
  InstallationDate: Installed on 2020-03-28 (393 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200328)
  MachineType: HP HP Desktop M01-F0xxx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=8fc8c49e-2944-4e22-9137-fd8870710ea3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (3 days ago)
  dmi.bios.date: 11/26/2019
  dmi.bios.release: 15.17
  dmi.bios.vendor: AMI
  dmi.bios.version: F.11
  dmi.board.name: 8643
  dmi.board.vendor: HP
  dmi.board.version: SMVB
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 52.38
  dmi.modalias: 
dmi:bvnAMI:bvrF.11:bd11/26/2019:br15.17:efr52.38:svnHP:pnHPDesktopM01-F0xxx:pvr:rvnHP:rn8643:rvrSMVB:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53311M HP Desktop PC
  dmi.product.name: HP Desktop M01-F0xxx
  dmi.product.sku: 8KX18EA#ABD
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1926121/+subscriptions

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


[Touch-packages] [Bug 1926062] Re: [RTL8821A][ideapad_bluetooth] I am unable to open/close/connect/scan bluetooth

2021-05-03 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1926095, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Summary changed:

- [RTL8821A][ideapad_bluetooth] I am unable to open/close/connect/scan bluetooth
+ [hirsute] Can't turn bluetooth on again after turning it off

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

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

Title:
  [hirsute] Can't turn bluetooth on again after turning it off

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

Bug description:
  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
DOWN 
RX bytes:744804 acl:76 sco:0 events:105989 errors:0
TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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

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


[Touch-packages] [Bug 1926095] Re: The bluetooth toggle is not working properly. Switching it on does not turn on the bluetooth. It remains off permanently.

2021-05-03 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1926062 ***
https://bugs.launchpad.net/bugs/1926062

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1926062, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1926062
   [hirsute] Can't turn bluetooth on again after turning it off

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

Title:
  The bluetooth toggle is not working properly. Switching it on does not
  turn on the bluetooth. It remains off permanently.

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I have described the issue here with screenshots
  https://askubuntu.com/q/1333848/1022606. Please have a look at the
  screenshots. Turning on the Bluetooth toggle has no effect. The system
  doesn't turn on the Bluetooth and does no scan for devices. Turning it
  on just moves the toggle, even the system doesn't acknowledge by
  showing that Bluetooth is on. The status remains off. It happened only
  after the upgrade I did yesterday. It was working fine before that.
  Please look into it. I cannot connect my Bluetooth earphones to my PC.
  This poses a lot of problems since my classes and courses are all
  online.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 00:09:35 2021
  InstallationDate: Installed on 2019-12-05 (507 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to hirsute on 2021-04-24 (1 days ago)
  VarLogDistupgradeTermlog:

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

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


[Touch-packages] [Bug 1926783] Re: [MSI MS-7B98] Sound is faster, high-pitched and distorted

2021-05-03 Thread Daniel van Vugt
Since you say the current kernel for Ubuntu 20.04 does not have the
problem then it is considered Fix Released.

If there is a newer kernel that does still have the bug then you should
report it upstream, not here.

** Summary changed:

- [USB-Audio - Saffire 6 USB, playback] Sound is faster, high-pitched and 
distorted
+ [MSI MS-7B98] Sound is faster, high-pitched and distorted

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

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

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

Title:
  [MSI MS-7B98] Sound is faster, high-pitched and distorted

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  It works normally when playing youtube videos, only audio files on PC are a 
problem.
  Also, kernel 5.8.0-50-generic does not have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.10
  ProcVersionSignature: Ubuntu 5.11.0-7614.15~1618626693~20.04~ecb25cd-generic 
5.11.13
  Uname: Linux 5.11.0-7614-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michal 1518 F pulseaudio
   /dev/snd/controlC2:  michal 1518 F pulseaudio
   /dev/snd/controlC1:  michal 1518 F pulseaudio
   /dev/snd/pcmC1D0p:   michal 1518 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Fri Apr 30 17:05:38 2021
  InstallationDate: Installed on 2021-01-31 (89 days ago)
  InstallationMedia:
   
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: TU104 HD Audio Controller - HDA NVidia
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [USB-Audio - Saffire 6 USB, playback] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.80
  dmi.board.asset.tag: Default string
  dmi.board.name: Z390-A PRO (MS-7B98)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd12/25/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7B98
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Touch-packages] [Bug 1926976] Re: during mouse drag operations I'm getting undesired/unprompted dropping and potentially picking up of something else

2021-05-03 Thread Daniel van Vugt
It sounds like you are getting spurious mouse button (or even keyboard)
events from one of your input devices, which will randomly break drag
operations. This does happen to people occasionally and in every case
(so far) it turns out to be a broken input device.

Please try unplugging all input devices from the machine and then adding
them back in one-by-one. Please also try a different mouse if you can,
and hit all the keys on your keyboard in case one of them is sticking or
causing unwanted events.


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

Title:
  during mouse drag operations I'm getting undesired/unprompted dropping
  and potentially picking up of something else

Status in Ubuntu:
  Incomplete

Bug description:
  I am not really sure this is an Xorg problem. Since my last system
  update (upon the system prompting), I think less than a week ago, I
  have noticed this troubling intermittent behavior. I go to drag
  (mouse-initiated) a window across some screen distances (between
  external monitors and my laptop's builtin monitor) the window will get
  dropped without me releasing the mouse button before arriving at my
  desired drop point. More than half the times this happens, something
  will immediately be picked up in a drag operation. Sometimes it is
  another window that begins being moved. Other times it is a window
  resize operation that is picked up. A third option is the selection of
  text.

  I have noticed that most of the time it is triggered when I am moving
  rapidly (though no more rapidly than I have done successfully in the
  past). Sometimes it happens when I pause during the drag operation. It
  even happens infrequently when I am dragging slowly.

  Often I can just go back and pick up the window and complete the
  operation. However, sometimes the problem just keeps happening until I
  give up and go away for 5 minutes or so.

  I have a stock configuration of 20.04. I keep it updated and haven't
  changed anything significant about X, Gnome, etc. I have done a few
  tweaks, but nothing I can think of that would relate to this problem.
  My laptop, a Dell XPS 13, uses a USB 3.1 hub and through that drives
  two monitors via HDMI. My mouse is bluetooth - Logitech MX Vertical. I
  don't believe I have installed any proprietary drivers. My 3 displays
  are arranged into an inverted "L" shape, as the laptop display is
  "below" and identically sized to the 27" monitor "above" it. The other
  27" monitor is to the left of the first one.

  Some, potentially useful, debugging info:

  $ lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  $ apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu14
Candidate: 1:7.7+19ubuntu14
Version table:
   *** 1:7.7+19ubuntu14 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  $ bluetoothctl --version
  bluetoothctl: 5.53
  $ hciconfig -a
  hci0: Type: Primary  Bus: USB
BD Address: 9C:B6:D0:99:27:2C  ACL MTU: 1024:8  SCO MTU: 50:8
UP RUNNING
RX bytes:21743080 acl:954252 sco:0 events:141080 errors:0
TX bytes:6895 acl:169 sco:0 commands:208 errors:0
Features: 0xff 0xfe 0x8f 0xfe 0xd8 0x3f 0x5b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF
Link mode: SLAVE ACCEPT
Name: 'kbuchs'
Class: 0x0c010c
Service Classes: Rendering, Capturing
Device Class: Computer, Laptop
HCI Version: 4.2 (0x8)  Revision: 0x0
LMP Version: 4.2 (0x8)  Subversion: 0x25a
Manufacturer: Qualcomm (29)

  $ bluetoothctl
  Agent registered
  [CHG] Controller 9C:B6:D0:99:27:2C Pairable: yes
  [MX Vertical]# show
  Controller 9C:B6:D0:99:27:2C (public)
Name: kbuchs
Alias: kbuchs
Class: 0x000c010c
Powered: yes
Discoverable: no
DiscoverableTimeout: 0x00b4
Pairable: yes
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0535
Discovering: no
  Advertising

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

2021-05-03 Thread Daniel van Vugt
Thanks for the bug report. Next time the problem happens please reboot
and then run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

Although I notice the attached logs already show your SSD is
experiencing hardware errors. You might need to replace the SSD:

[ 1633.238345] pcieport 1:e0:06.0: AER: Corrected error received: 
1:e1:00.0
[ 1633.238381] nvme 1:e1:00.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
[ 1633.238384] nvme 1:e1:00.0:   device [15b7:5006] error 
status/mask=0001/e000
[ 1633.238387] nvme 1:e1:00.0:[ 0] RxErr  (First)

** Summary changed:

- Xorg freeze
+ System freeze

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

** Changed in: linux (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/1927019

Title:
  System freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 21.04 Freeze sometime ( using wayland ) . A black screen appear from 
top to bottom and ubuntu doesn't react to any keyboard shortcut.  It's appears, 
maybe after 2 hours of work.
  I didn't see this bug with my previous ubuntu 20.10.
  My computer is a new DELL XPS 13 - intel core i7. I disabled the 4K screen 
and I am using a resolution 1920x1080. I enabled the night mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  4 00:10:39 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
     Subsystem: Dell Iris Xe Graphics [1028:0a5c]
  InstallationDate: Installed on 2021-04-30 (3 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. XPS 13 9305
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=37473b6f-8714-4a48-91c1-f6964b09347d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/13/2021
  dmi.bios.release: 1.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.1
  dmi.board.name: 0PPYW4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.1:bd01/13/2021:br1.0:svnDellInc.:pnXPS139305:pvr:rvnDellInc.:rn0PPYW4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9305
  dmi.product.sku: 0A5C
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

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


[Touch-packages] [Bug 1926062] Re: [hirsute] Can't turn bluetooth on again after turning it off

2021-05-03 Thread Aman Kumar
I was facing the same problem. My toggle was not at all working, neither
from the top bar dropdown menu nor from the settings window. Switching
on the toggle did not have any effect. I had also reported this bug.
Someone in the comments had suggested a workaround to type this command
in the terminal:

systemctl restart Bluetooth

This command kind of hard restarts the Bluetooth service and works for
me for the time being until the bug is fixed. It might also help someone
else.

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

Title:
  [hirsute] Can't turn bluetooth on again after turning it off

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

Bug description:
  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
DOWN 
RX bytes:744804 acl:76 sco:0 events:105989 errors:0
TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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

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


[Touch-packages] [Bug 1925705] Re: 100% cpu

2021-05-03 Thread Daniel van Vugt
Which process is using 100% CPU?

I also wonder if this is related to bug 1924624...

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

Title:
  100% cpu

Status in Ubuntu:
  Incomplete

Bug description:
  my spek i5 gen3
  ram 8Gb
  ssd 512

  fresh install and my cpu always 100% when open and run apps, like
  firefox, chrome

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Fri Apr 23 07:15:41 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3]
  InstallationDate: Installed on 2021-04-20 (2 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 2349CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=6e403edb-143d-4aa1-8a31-b84abf6175a9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2019
  dmi.bios.release: 2.82
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETC2WW (2.82 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2349CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2349CTO:pvrThinkPadT430:rvnLENOVO:rn2349CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2349CTO
  dmi.product.sku: LENOVO_MT_2349
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/+bug/1925705/+subscriptions

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


[Touch-packages] [Bug 1924184] Re: drive not showing

2021-05-03 Thread Daniel van Vugt
Sounds like this is about graphics drivers. This system has an Intel GPU
so there are no additional graphics drivers. There is no bug here.


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

** Changed in: ubuntu
   Status: Incomplete => 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/1924184

Title:
  drive not showing

Status in Ubuntu:
  Incomplete

Bug description:
  i coudnt find graphic drive

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 15 03:35:34 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0844]
 Subsystem: Dell Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] 
[1028:0844]
  InstallationDate: Installed on 2021-04-13 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Vostro 3578
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic 
root=UUID=7cf915de-bb29-49e2-a9cc-0079efc75ed1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2020
  dmi.bios.release: 1.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 01Y7V4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd01/09/2020:br1.10:svnDellInc.:pnVostro3578:pvr:rvnDellInc.:rn01Y7V4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3578
  dmi.product.sku: 0844
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/+bug/1924184/+subscriptions

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