[Touch-packages] [Bug 1875026] Re: video playback is laggy

[Daniel van Vugt]

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

Title:
  video playback is laggy

Status in Ubuntu:
  Incomplete

Bug description:
  i installed Ubuntu 20.04 yesterday and now i am facing laggy video.
  please help me to solve it

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 25 19:59:23 2020
  DistUpgraded: 2020-04-24 14:50:39,367 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: anbox, 1, 4.15.0-96-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:3672]
  InstallationDate: Installed on 2017-06-28 (1032 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP 430 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=6635d7b9-b7dc-4e2a-a268-064452e04423 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-04-24 (1 days ago)
  dmi.bios.date: 12/18/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.39
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3672
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 23.4B
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.39:bd12/18/2011:svnHewlett-Packard:pnHP430NotebookPC:pvr058A10004C1000260:rvnHewlett-Packard:rn3672:rvr23.4B:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=430
  dmi.product.name: HP 430 Notebook PC
  dmi.product.sku: LX031PA#UUF
  dmi.product.version: 058A10004C1000260
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101+git2004241830.bf63f8~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.1~git2004250730.a64d26~oibaf~f
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.1~git2004250730.a64d26~oibaf~f
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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: Sat Jun  9 08:31:29 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 745 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

-- 
Mailing list: https://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 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red

[Paul Collinsworth]

I replaced the Nvidia video card in my system and the problem seems to 
have gone with it.

I had seen an improvement with the Nvidia card after switching from the 
digital video output to the on-card VGA output, but over a period of a 
couple of weeks or so, the video degraded again.

The new card is a VisionTek Radeon 5450.


On 4/28/20 1:42 PM, Tim Hockin wrote:
> I just filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712
> which feels like it might be similar?
>

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

Title:
  [nouveau, GeForce 7300 LE] screen background overlaid with scan type
  artifact in red

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  My desktop has both it's usual items in place; toolbar on left and
  desktop icons distributed around the screen. Then there's what appears
  to be a bunch of scan line, raster line artifacts, in red, laid over
  my normal background, which is a star field photo on what is
  ordinarily a black field.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 21 13:04:20 2020
  DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405]
  InstallationDate: Installed on 2016-08-19 (1249 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 531
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago)
  dmi.bios.date: 11/09/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0RY206
  dmi.board.vendor: Dell Inc.
  dmi.board.version: ���
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion:
  dmi.product.name: Inspiron 531
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct  3 10:41:28 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard KEYBOARD, id 8
   inputLogitech USB Trackball MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1869368] Re: ubuntu_qrt_apparmor fails on ADT bionic/linux i386

[Po-Hsu Lin]

** Tags added: 4.15 i386 ubuntu-qrt-apparmor

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

Title:
  ubuntu_qrt_apparmor fails on ADT bionic/linux i386

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid
Status in apparmor source package in Bionic:
  New
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Testing failed on:
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/l/linux/20200326_224620_0dd01@/log.gz

  Kernel version: bionic/linux 4.15.0-94.95

  The ubuntu_qrt_apparmor.test-apparmor.py fails intermittently on
  bionic/linux i386 ADT tests. It has failed some releases in the past
  and I'm seeing the failure in the current release as well. I have not
  seen this failure on other architectures.

  These are the last messages on the test log:
  20:12:39 ERROR| [stderr] Test mediation of file based SOCK_STREAM connect ... 
ok
  20:12:39 ERROR| [stderr] test_libapparmor_testsuite 
(__main__.ApparmorTestsuites)
  20:14:18 DEBUG| [stdout]   unconfined_user can access confined_user's file
  20:14:18 DEBUG| [stdout]   unconfined_user can access default_user's file
  20:14:18 DEBUG| [stdout]   unconfined_user can access unconfined_group's file
  20:14:18 DEBUG| [stdout] 
  20:15:42 ERROR| [stderr] Run libapparmor testsuite ... (Applying patch 
0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying 
patch 0001-usr-merge-fixups.patch) ok
  20:15:42 ERROR| [stderr] test_libapparmor_testsuite3 
(__main__.ApparmorTestsuites)
  20:15:52 DEBUG| [stdout]   preparing apparmor_2.12-4ubuntu5.1.dsc...  done
  20:15:52 DEBUG| [stdout] 
  20:17:10 ERROR| [stderr] Run libapparmor testsuite (with python3) ... 
(Applying patch 
0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying 
patch 0001-usr-merge-fixups.patch) ok
  20:17:10 ERROR| [stderr] test_old_trusty_parser_testsuite 
(__main__.ApparmorTestsuites)
  20:17:10 DEBUG| [stdout]   preparing apparmor_2.12-4ubuntu5.1.dsc...  done
  20:17:10 ERROR| [stderr] Run parser regression tests from 14.04's 
apparmor_2.8.95~2430-0ubuntu5.3 ... (skipped: This test is only for 14.04 
systems with the apparmor 2.10.95 SRU or newer installed) ok
  20:17:10 ERROR| [stderr] test_old_trusty_regression_testsuite 
(__main__.ApparmorTestsuites)
  20:17:10 ERROR| [stderr] Run kernel regression tests from 14.04's 
apparmor_2.8.95~2430-0ubuntu5.3 ... (skipped: This test is only for 14.04 
systems with the apparmor 2.10.95 SRU or newer installed) ok
  20:17:10 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites)
  20:17:19 DEBUG| [stdout] 
  20:52:35 ERROR| [stderr] Run parser regression tests ... (Applying patch 
0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying 
patch 0001-usr-merge-fixups.patch) ok
  20:52:35 ERROR| [stderr] test_regression_testsuite 
(__main__.ApparmorTestsuites)
  20:52:42 DEBUG| [stdout]   preparing apparmor_2.12-4ubuntu5.1.dsc...  done
  20:52:42 DEBUG| [stdout] 
  21:01:56 INFO | ERROR   ubuntu_qrt_apparmor.test-apparmor.py  
  ubuntu_qrt_apparmor.test-apparmor.pytimestamp=1585256516localtime=Mar 
26 21:01:56   Test subprocess failed rc=9

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1869368/+subscriptions

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

[Touch-packages] [Bug 1875189] Re: Screen Flickers when it wakes from suspend/sleep.

[Daniel van Vugt]

The link provided is a crash in the kernel's SSD code. I don't think
it's related to this bug at all.

** Tags added: amdgpu flicker

** Summary changed:

- Screen Flickers when it wakes from suspend/sleep.
+ [amdgpu] Screen Flickers when it wakes from suspend/sleep.

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

Title:
  [amdgpu] Screen Flickers when it wakes from suspend/sleep.

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  I got some laptop having optimus/hybrid GPUs setup : AMD Vega 8 (
  Raven Ridge ) + Nvidia GTX 1650 GPUs and  a display having refresh
  rate of 120Hz.

  Whenever I shut the laptop lid or it auto-suspends it catches screen
  flickers when it wakes up.

  I think it's some kernel issue some deadlock maybe.

  I already filed a bug on fedora bugzilla forum for the same aswell.

  Here is the link for the same :

  https://bugzilla.redhat.com/show_bug.cgi?id=1748042

  I hope it gets' fixed this time :)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.6.0-7.1-liquorix-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 20:33:46 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TU117M [GeForce GTX 1650 Mobile / Max-Q] 
[1043:109f]
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:18f1]
  InstallationDate: Installed on 2020-04-26 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT
  ProcKernelCmdLine: audit=0  
BOOT_IMAGE=/@/boot/vmlinuz-5.6.0-7.1-liquorix-amd64 
root=UUID=c6a5aea4-fe87-480e-9b59-d3b0077d5842 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX505DT.310
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX505DT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX505DT.310:bd12/24/2019:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DT_FX505DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming
  dmi.product.name: TUF Gaming FX505DT_FX505DT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1875189] Re: [amdgpu] Screen Flickers when it wakes from suspend/sleep.

[Daniel van Vugt]

Please try selecting 'Ubuntu on Wayland' on the login screen, then log
in and tell us if the problem still occurs there.

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

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

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

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

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

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

Title:
  [amdgpu] Screen Flickers when it wakes from suspend/sleep.

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  I got some laptop having optimus/hybrid GPUs setup : AMD Vega 8 (
  Raven Ridge ) + Nvidia GTX 1650 GPUs and  a display having refresh
  rate of 120Hz.

  Whenever I shut the laptop lid or it auto-suspends it catches screen
  flickers when it wakes up.

  I think it's some kernel issue some deadlock maybe.

  I already filed a bug on fedora bugzilla forum for the same aswell.

  Here is the link for the same :

  https://bugzilla.redhat.com/show_bug.cgi?id=1748042

  I hope it gets' fixed this time :)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.6.0-7.1-liquorix-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 20:33:46 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TU117M [GeForce GTX 1650 Mobile / Max-Q] 
[1043:109f]
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:18f1]
  InstallationDate: Installed on 2020-04-26 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT
  ProcKernelCmdLine: audit=0  
BOOT_IMAGE=/@/boot/vmlinuz-5.6.0-7.1-liquorix-amd64 
root=UUID=c6a5aea4-fe87-480e-9b59-d3b0077d5842 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX505DT.310
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX505DT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX505DT.310:bd12/24/2019:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DT_FX505DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming
  dmi.product.name: TUF Gaming FX505DT_FX505DT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1875628] Re: getting white and purple blocks on top of some texts

[Daniel van Vugt]

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

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 1867668, 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 1867668
   Visual artifacts in Gnome Shell when using the 'intel' Xorg driver

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

Title:
  getting white and purple blocks on top of some texts

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Everytime I start Ubuntu, I get gren blocks all of the home screen,
  which is solved by changing the wallpaper. But I also get white &
  purple blocks over texts like my wifi name, "Night Light On" and Time
  on the top bar (see attached photo). This is not solved.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 17:01:19 2020
  DistUpgraded: 2020-04-25 20:54:39,691 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-46-generic, x86_64: installed
   nvidia, 435.21, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fc]
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TU117M [GeForce GTX 1650 Mobile / 
Max-Q] [103c:85fc]
  InstallationDate: Installed on 2019-08-26 (245 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b627 Chicony Electronics Co., Ltd HP Wide Vision 
HD Camera
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=e82ecf26-25d1-4191-8a15-74a3ab24420c ro acpi_backlight=vendor
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-25 (2 days ago)
  dmi.bios.date: 11/22/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.20
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 85FC
  dmi.board.vendor: HP
  dmi.board.version: 42.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.20:bd11/22/2019:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FC:rvr42.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx
  dmi.product.sku: 7LG86PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1875067] Re: [MS-7788, Realtek Generic, Green Line Out, Rear] Pulseaudio fails to detect card

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1692793
   [MS-7788, Realtek ALC887-VD, Green Line Out, Rear] No sound at all

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

Title:
  [MS-7788, Realtek Generic, Green Line Out, Rear] Pulseaudio fails to
  detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  NO sound, just dummy output

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 01:09:21 2020
  InstallationDate: Installed on 2018-05-14 (712 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Green Line Out, Rear
  Title: [MS-7788, Realtek Generic, Green Line Out, Rear] Pulseaudio fails to 
detect card
  UpgradeStatus: Upgraded to focal on 2020-04-23 (1 days ago)
  dmi.bios.date: 01/10/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-P20 (G3) (MS-7788)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd01/10/2013:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P20(G3)(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7788
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Touch-packages] [Bug 1692793] Re: [MS-7788, Realtek ALC887-VD, Green Line Out, Rear] No sound at all

[Launchpad Bug Tracker]

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

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

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

Title:
  [MS-7788, Realtek ALC887-VD, Green Line Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I recently upgraded my system from 14.04LTS to 16.04LTS. 
  But now I cannot hear any sound from any player or youtube.

  executing the command

  aplay -l

  I get the harware information like

   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ronem  1986 F...m pulseaudio
   /dev/snd/controlC0:  ronem  1986 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 23 10:54:00 2017
  InstallationDate: Installed on 2016-01-05 (503 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ronem  1986 F...m pulseaudio
   /dev/snd/controlC0:  ronem  1986 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [MS-7788, Realtek ALC887-VD, Green Line Out, Rear] No sound at all
  UpgradeStatus: Upgraded to xenial on 2017-05-22 (0 days ago)
  dmi.bios.date: 01/10/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-P20 (G3) (MS-7788)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd01/10/2013:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P20(G3)(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7788
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Touch-packages] [Bug 1692793] Re: [MS-7788, Realtek ALC887-VD, Green Line Out, Rear] No sound at all

[Daniel van Vugt]

** Tags added: focal

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

Title:
  [MS-7788, Realtek ALC887-VD, Green Line Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I recently upgraded my system from 14.04LTS to 16.04LTS. 
  But now I cannot hear any sound from any player or youtube.

  executing the command

  aplay -l

  I get the harware information like

   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ronem  1986 F...m pulseaudio
   /dev/snd/controlC0:  ronem  1986 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 23 10:54:00 2017
  InstallationDate: Installed on 2016-01-05 (503 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ronem  1986 F...m pulseaudio
   /dev/snd/controlC0:  ronem  1986 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [MS-7788, Realtek ALC887-VD, Green Line Out, Rear] No sound at all
  UpgradeStatus: Upgraded to xenial on 2017-05-22 (0 days ago)
  dmi.bios.date: 01/10/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-P20 (G3) (MS-7788)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd01/10/2013:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P20(G3)(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7788
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Touch-packages] [Bug 1875649] Re: Screen flickering in Kubuntu 20.04 on Lenovo Yoga C940 14-IIL

[Daniel van Vugt]

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

It sounds like you're reporting both bug 1873587 and something like bug
1874010. So we should probably use those reports for now.

** Tags added: ice-lake-flicker

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

** Summary changed:

-  Screen flickering in Kubuntu 20.04 on Lenovo Yoga C940 14-IIL 
+ [Ice Lake] Screen flickering in Kubuntu 20.04 on Lenovo Yoga C940 14-IIL

** This bug has been marked a duplicate of bug 1873587
   [Ice Lake] Display flickers a lot DURING plymouth animations

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

Title:
  [Ice Lake] Screen flickering in Kubuntu 20.04 on Lenovo Yoga C940
  14-IIL

Status in linux package in Ubuntu:
  New

Bug description:
  Screen flickering in Kubuntu 20.04 on Lenovo Yoga C940 14-IIL

  I am filing this bug again in accordance with: 
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875073/comments/3
  I've deleted the repository and checked again, and the bug still persists.
  Old bug report: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875073

  My screen flickers on Kubuntu 20.04LTS.
  See: https://imgur.com/a/FoWI1sp

  Also affected:
  Kubuntu 19.10
  Fedora 31

  System:
  inxi -Gxxx
  Graphics:  Device-1: Intel Iris Plus Graphics G7 vendor: Lenovo driver: i915 
v: kernel bus ID: 00:02.0 chip ID: 8086:8a52
     Display: x11 server: X.Org 1.20.8 driver: modesetting compositor: 
kwin_x11 resolution: 1920x1080~60Hz
     OpenGL: renderer: Mesa Intel Iris Plus Graphics (ICL GT2) v: 4.6 
Mesa 20.0.4 direct render: Yes

  Reproduction scenario's:
  1) Starting Kubuntu, screen flickers a couple of times during startup and 
turns black for multiple seconds.
  2) Start a youtube video, near-constant flickering. Audio works fine.
  3) Open up various applications. Screen starts flickering every now and then.
  4) Leave pc unattended for a long time, screen starts flickering sporadically.

  Things I tried:
  * Use various kernels
  * linux kernel 3.4, 3.5, 3.6, 3.7rc2
  * Ubuntu port of linux kernel 3.4.0-26-generic + patch 
https://gitlab.freedesktop.org/jkrzyszt/i915/-/commit/1ee48a61aa57dbdbc3cd2808d8b28df40d938e44
  * intel-drm-next (kernel panic)
  * Oibaf PPA
  * various kernel parameters

  What does work:
  * When using windows, the screen works. So no hardware error.
  * When using "nomodeset" kernel parameter Kubuntu 20.04 works, but then 
there's no sound or hardware acceleration.

  What I think is happening:
  i915 is apperantly an unstable driver for eDP 1.4 screens.
  That, in combination with a 10'th gen intel cpu is not a good combination.
  According to dmesg the firmware of sof-audio-pci is restarting.

  [  324.775087] sof-audio-pci :00:1f.3: error: no reply expected, 
received 0x0
  [  324.866267] sof-audio-pci :00:1f.3: firmware boot complete

  Could the audio part of the eDP connection be breaking because of
  an issue similar to the patch that is mentioned earlyer?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Tue Apr 28 15:31:27 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
     Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3801]
  InstallationDate: Installed on 2020-04-25 (3 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81Q9
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-26-generic 
root=UUID=5d977dfa-1fa5-412b-9d83-644cef18af6e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AUCN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga C940-14IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL:
  dmi.product.family: Yoga C940-14IIL
  dmi.product.name: 81Q9
  dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL
  dmi.product.version: Lenovo Yoga C940-14IIL
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  

[Touch-packages] [Bug 1875037] Re: Display Bug

[Daniel van Vugt]

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

** Summary changed:

- Display Bug
+ Turning off high contrast does not revert the desktop icons' appearance

** Also affects: gnome-shell-extension-desktop-icons (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Turning off high contrast does not revert the desktop icons'
  appearance

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Confirmed

Bug description:
  When going to Settings -> Universal Access and selecting "High
  Contrast" to view the difference in appearance, then switching "High
  Contrast" to off, the icons do not return to their normal appearance.
  I did not find a place in this bug submission interface to submit
  attachments or I would show you screen capture of the changes in the
  icon appearance.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 25 10:48:21 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA 
controller])
 Subsystem: Gigabyte Technology Co., Ltd UHD Graphics 630 (Desktop) 
[1458:d000]
  InstallationDate: Installed on 2020-03-31 (24 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330)
  MachineType: Gigabyte Technology Co., Ltd. H370 WIFI
  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.4.0-26-generic 
root=UUID=8d24e3f8-c08c-444a-8467-4f9473fa4a22 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F14
  dmi.board.asset.tag: Default string
  dmi.board.name: H370N WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF14:bd06/05/2019:svnGigabyteTechnologyCo.,Ltd.:pnH370WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: H370 WIFI
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1874980] Re: Screen not responding after shut down

[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.


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

Title:
  Screen not responding after shut down

Status in Ubuntu:
  Incomplete

Bug description:
  I had several problems after my PC turned off, after login, I was able
  to move the mouse, but taping on the keyboard or click with the mouse
  had no effect. Another time, I only had the cursor over a black or
  grey screen

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  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: GNOME
  Date: Sat Apr 25 09:10:43 2020
  DistUpgraded: 2020-04-22 14:29:57,005 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:3986]
  InstallationDate: Installed on 2018-05-14 (711 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 174f:241a Syntek EasyCamera
   Bus 001 Device 002: ID 0bc2:2321 Seagate RSS LLC Expansion Portable
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80X4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=0ff3bd04-0e33-4b67-b2db-f559244a8448 ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-22 (2 days ago)
  dmi.bios.date: 11/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4QCN51WW(V2.15)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320S-14IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4QCN51WW(V2.15):bd11/19/2019:svnLENOVO:pn80X4:pvrLenovoideapad320S-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320S-14IKB:
  dmi.product.family: ideapad 320S-14IKB
  dmi.product.name: 80X4
  dmi.product.sku: LENOVO_MT_80X4_BU_idea_FM_ideapad 320S-14IKB
  dmi.product.version: Lenovo ideapad 320S-14IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1733321] Autopkgtest regression report (network-manager/1.10.6-2ubuntu1.5)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted network-manager (1.10.6-2ubuntu1.5) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/237-3ubuntu10.39 (i386)
netplan.io/0.98-0ubuntu1~18.04.1 (ppc64el)


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/bionic/update_excuses.html#network-manager

[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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1733321

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Bionic:
  Fix Committed
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Fix Committed
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  [Test Case]

  Assume that test vm and host are ppc64

  1. deploy ppc64 vm instance ( with 1 cpu )
  2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
  3. apt install network-manager rfkill
  4. modify /etc/netplan/[conf], renderer as NetworkManager
  5. netplan apply
  6. run below command
  - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli 
radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi

  enabled
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  enabled
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  enabled

  second 'enabled' should be 'disabled' but not updated properly.

  Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
  rfkill block/unblock and nmcli radio wifi will help updating status changes 
after rfkill block/unblock.

  [Regression Potential]

  This fixes testcase only, so any regression would cause incorrect test
  pass/fail, and might cause other missed bugs.

  [scope]

  this is needed for all releases.  Debian does not include this
  autopkgtest, and so does not need this fix.

  [Other Info]

  this is caused by the 'systemd-rfkill.socket' listening to rfkill, and
  starting up 'systemd-rfkill.service' for any change.  On a 1-cpu
  system (which all autopkgtest instances for network-manager are), this
  service startup sometimes blocks the uevent from reaching network-
  manager before the autopkgtest proceeds to call nmcli to check the
  rfkill status.  This causes the test case to fail.

  There are (at least) 2 options to fix this:
  1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest
  2) call udevadm settle between the rfkill block/unblock and the nmcli call to 
check status

  This does not need to be fixed outside the test case, as normal nmcli
  use should be not done by users in a script immediately after changing
  rfkill state, nor is there anything that either rfkill or nmcli could
  

[Touch-packages] [Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem

[Hui Wang]

the -25 kernel was successfully installed, but according to log, there
is some driver issues not fixed, so please try this v2 kernel:

sudo dpkg -r --force-all linux-image-unsigned-5.4.0-25-generic
(uninstall the -25 kernel installed yesterday)

download the v2 kernel:
https://people.canonical.com/~hwang4/25skipi915/v2/

sudo dpkg -i *.deb (the v2 kernel deb)

and please upload dmesg rather than alsa-info.txt this time.

thx.

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

Title:
  [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left]
  Recording problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy
  output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa-
  base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that
  now "snd-hda-intel" is loaded instead of sof-audio-pci. While the
  speakers are working fine, I do not have the internal microphone
  working (suspect a digital array).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wittawat   2063 F pulseaudio
   /dev/snd/controlC0:  wittawat   2063 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 12:42:32 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Mic, Left
  Symptom_Type: None of the above
  Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] 
Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8600
  dmi.board.vendor: HP
  dmi.board.version: 44.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dh0xxx
  dmi.product.sku: 7JX54EA#ABD
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996

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

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

[Touch-packages] [Bug 1875779] Re: Screen Flicking

[Daniel van Vugt]

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

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 1867668, 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 1867668
   Visual artifacts in Gnome Shell when using the 'intel' Xorg driver

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

Title:
  Screen Flicking

Status in xorg package in Ubuntu:
  New

Bug description:
  Having screen flick. App broken icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 29 09:32:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Generation Core Processor Family 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2020-04-27 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=f1af71e1-f15e-4a27-a89d-dedadf139bfd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3602
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-P
  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.:bvr3602:bd03/26/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-P:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1875782] Re: tracker-store and tracker-extract using 100% CPU

[Daniel van Vugt]

** Tags added: focal

** Package changed: gnome-control-center (Ubuntu) => tracker (Ubuntu)

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

Title:
  tracker-store and tracker-extract using 100% CPU

Status in tracker package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu 18.04 to Ubuntu 20.04, tracker-store and
  tracker-extract processes are using 100% CPU. CPU temperature goes
  above 80 degrees celsius.

  This is causing fan spinning and computer is very loud because of it.

  I've tried removing tracker package, but it wants to remove the whole
  desktop with it.

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

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

[Touch-packages] [Bug 1875782] [NEW] tracker-store and tracker-extract using 100% CPU

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After upgrading from Ubuntu 18.04 to Ubuntu 20.04, tracker-store and
tracker-extract processes are using 100% CPU. CPU temperature goes above
80 degrees celsius.

This is causing fan spinning and computer is very loud because of it.

I've tried removing tracker package, but it wants to remove the whole
desktop with it.

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


** Tags: focal
-- 
tracker-store and tracker-extract using 100% CPU
https://bugs.launchpad.net/bugs/1875782
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to tracker 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 1874941] Re: lag and hangs

[Daniel van Vugt]

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

Title:
  lag and hangs

Status in Ubuntu:
  Incomplete

Bug description:
  Since upgrading from ubuntu 18.04 I have not been able to stream video
  from youtube without the video freezing for a second or two every 30
  seconds. Also when filling out this form the text lag. This has not
  been the case on this computer when using 18.04, 19.04 or 19.10.

  This performance issue renders the computer hard to use for work and I
  am almost completly certain that it is xorg or some other graphics
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 25 01:52:12 2020
  DistUpgraded: 2020-04-23 23:49:11,187 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04]
  MachineType: HUAWEI MACH-WX9
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=e5a15015-60f2-4474-a116-bd9e25289d5f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-23 (1 days ago)
  dmi.bios.date: 03/15/2019
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.28
  dmi.board.name: MACH-WX9-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M13
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:svnHUAWEI:pnMACH-WX9:pvrM13:rvnHUAWEI:rnMACH-WX9-PCB:rvrM13:cvnHUAWEI:ct10:cvrM13:
  dmi.product.family: MateBook X
  dmi.product.name: MACH-WX9
  dmi.product.sku: C189
  dmi.product.version: M13
  dmi.sys.vendor: HUAWEI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  [SRU] Load ucm on Lenovo notebooks based on bios version

Status in HWE Next:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Fix Released
Status in alsa-lib source package in Eoan:
  Fix Released
Status in alsa-lib source package in Focal:
  Invalid

Bug description:
  This SRU is not backported from upstream of alsa-lib and this SRU is
  not going to be submitted to upstream. That is because the latest
  alsa-lib already supports ucm2, and with ucm2 all machines could share
  one ucm, so latest alsa-lib does not have this problem. This problem
  is only specific to the alsa-lib in Bionic and Eoan.

  [Impact]
  On some Lenovo notebooks, UCM files are not loaded and mic can't be used.

  [Fix]
  UCM was loaded based on cardlongname, but that can't cover all configs of the 
same model. Lenovo suggested to load  ucm by the first 3 letters of 
/sys/devices/virtual/dmi/id/bios_version, so that all configs could use just 
one ucm.

  [Test Case]
  After applying this patch, install the testing alsa-lib on Lenovo X1C7 and 
Dell vostro 5390, which are all machines with the DMIC connected to PCH. After 
system bootup, check the /usr/share/alsa/ucm/ for the presence of 
LENOVO-BIOSID-xxx directories.

  Lenovo X1C7 should load the N2H/*.conf and verify the audio
  functionalities. The Dell machine should still load the ucm by
  cardname, and it should work as good as before.

  [Regression Potential]
  low, just add some new UCMs and let Lenovo machine find the UCM by 
bios_version if it fails by cardlongname. I've already tested the change on 
Lenovo and Dell machines.

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

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

[Touch-packages] [Bug 1875781] [NEW] Unable to verify self signed certificate

[Taiten Peng]

Public bug reported:

See the upstream bug background
https://github.com/openssl/openssl/issues/1418

The issue initially was caught in a case when developers works behind
company firewall and requires install company self signed certificate on
Ubuntu host in order to access via company proxy.

This is also causing problems for snapcraft developers who work behind
proxy servers unable to build snap packages.

There is a fix going into openssl upstream apparently
https://github.com/openssl/openssl/pull/10587

Just create a bug here to track this issue in Ubuntu in order to make
sure we merge upstream fixes ultimately.

Similar case reported by other users:
[1] 
https://serverfault.com/questions/966846/cannot-trust-development-https-self-signed-certificate-in-ubuntu-18-04-2-lts
[2] 
https://stackoverflow.com/questions/55485511/how-to-run-dotnet-dev-certs-https-trust/59702094#59702094

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

** Description changed:

  See the upstream bug background
  https://github.com/openssl/openssl/issues/1418
  
- 
- The issue initially was caught in a case when developers works behind company 
firewall and requires install company self signed certificate on Ubuntu host in 
order to access via company proxy.
+ The issue initially was caught in a case when developers works behind
+ company firewall and requires install company self signed certificate on
+ Ubuntu host in order to access via company proxy.
  
  This is also causing problems for snapcraft developers who work behind
  proxy servers unable to build snap packages.
  
  There is a fix going into openssl upstream apparently
  https://github.com/openssl/openssl/pull/10587
  
  Just create a bug here to track this issue in Ubuntu in order to make
  sure we merge upstream fixes ultimately.
  
- 
  Similar case reported by other users:
  [1] 
https://serverfault.com/questions/966846/cannot-trust-development-https-self-signed-certificate-in-ubuntu-18-04-2-lts
- [2]
+ [2] 
https://stackoverflow.com/questions/55485511/how-to-run-dotnet-dev-certs-https-trust/59702094#59702094

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

Title:
  Unable to verify self signed certificate

Status in openssl package in Ubuntu:
  New

Bug description:
  See the upstream bug background
  https://github.com/openssl/openssl/issues/1418

  The issue initially was caught in a case when developers works behind
  company firewall and requires install company self signed certificate
  on Ubuntu host in order to access via company proxy.

  This is also causing problems for snapcraft developers who work behind
  proxy servers unable to build snap packages.

  There is a fix going into openssl upstream apparently
  https://github.com/openssl/openssl/pull/10587

  Just create a bug here to track this issue in Ubuntu in order to make
  sure we merge upstream fixes ultimately.

  Similar case reported by other users:
  [1] 
https://serverfault.com/questions/966846/cannot-trust-development-https-self-signed-certificate-in-ubuntu-18-04-2-lts
  [2] 
https://stackoverflow.com/questions/55485511/how-to-run-dotnet-dev-certs-https-trust/59702094#59702094

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

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

[Touch-packages] [Bug 1874862] Re: [WinBook TW102] Touch inputs not detected

[Daniel van Vugt]

** Summary changed:

- Touch inputs not detected
+ [WinBook TW102] Touch inputs not detected

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

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

** Changed in: libinput (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/1874862

Title:
  [WinBook TW102] Touch inputs not detected

Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  touch inputs are not detected by Ubuntu on this tablet. I'm not sure
  the touch screen hardware is detected at all by Ubuntu. I tried cat
  /dev/input/eventX (replacing X with every option listed) and not once
  got any reaction to touching the screen.

  I can provide more information and troubleshooting if asked, I just
  need to know what to look for.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.5.0-050500-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 13:27:45 2020
  DistUpgraded: 2020-01-26 15:24:00,462 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
  InstallationDate: Installed on 2020-01-22 (92 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0603:0002 Novatek Microelectronics Corp. 
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 480M
   |__ Port 4: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
   |__ Port 2: Dev 5, If 0, Class=Human Interface Device, 
Driver=usbhid, 1.5M
   |__ Port 2: Dev 5, If 1, Class=Human Interface Device, 
Driver=usbhid, 1.5M
  MachineType: MicroElectronics TW102
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.0-050500-generic 
root=UUID=20dd837f-ba9a-469c-bba4-45bb6e2370db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-01-26 (88 days ago)
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 8.17
  dmi.board.asset.tag: Default string
  dmi.board.name: H8811C
  dmi.board.vendor: EMDOOR
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 17
  dmi.chassis.vendor: EMDOOR
  dmi.chassis.version: 1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr8.17:bd03/22/2018:svnMicroElectronics:pnTW102:pvr1:rvnEMDOOR:rnH8811C:rvr1.0:cvnEMDOOR:ct17:cvr1:
  dmi.product.family: WinBook
  dmi.product.name: TW102
  dmi.product.sku: 585497
  dmi.product.version: 1
  dmi.sys.vendor: MicroElectronics
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

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

[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.


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

Title:
  Xorg freeze

Status in Ubuntu:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center

  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

  
  3) What you expected to happen

  Being able to switch between "Frequent" and "All" within GNOME App
  menu

  4) What happened instead

  
  The screen froze
  The screen not to freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 13:18:07 2020
  DistUpgraded: 2020-04-24 12:33:58,057 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:179b]
  InstallationDate: Installed on 2019-06-09 (319 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Hewlett-Packard HP EliteBook 8470p
  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.4.0-26-generic 
root=UUID=5523994d-c0c4-49a7-8e11-4d2ce9de39d9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  dmi.bios.date: 07/16/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ICF Ver. F.43
  dmi.board.name: 179B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 42.36
  dmi.chassis.asset.tag: CNU2250G4C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.43:bd07/16/2013:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1029CD1:rvnHewlett-Packard:rn179B:rvrKBCVersion42.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 8470p
  dmi.product.sku: B8Q56UP
  dmi.product.version: A1029CD1
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1875779] [NEW] Screen Flicking

[Khan Ahammed Jubayer]

Public bug reported:

Having screen flick. App broken icon.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 29 09:32:47 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 4th Generation Core Processor Family 
Integrated Graphics Controller [1043:8534]
InstallationDate: Installed on 2020-04-27 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=f1af71e1-f15e-4a27-a89d-dedadf139bfd ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/26/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3602
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-P
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.:bvr3602:bd03/26/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-P:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

Title:
  Screen Flicking

Status in xorg package in Ubuntu:
  New

Bug description:
  Having screen flick. App broken icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 29 09:32:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Generation Core Processor Family 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2020-04-27 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=f1af71e1-f15e-4a27-a89d-dedadf139bfd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3602
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-P
  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.:bvr3602:bd03/26/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-P:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 

[Touch-packages] [Bug 1874856] Re: Unwanted mouse trail

[Daniel van Vugt]

Please try switching to nouveau and then log into 'Ubuntu on Wayland'.
Does that avoid the problem?

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

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

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Unwanted mouse trail

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

Bug description:
  Moving mouse leaves a trail of squares for a few seconds on a fresh
  20.04 install. This happens with proprietary nvidia 440 drivers as
  well as nouveau on my GeFOrce GTX 1050 mobile.

  Could be related to my submission
  https://bugs.launchpad.net/ubuntu/+source/software-
  properties/+bug/1874819

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:59:48 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1a10]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:1a10]
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. X580VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=5df76c33-718b-436b-8b59-9a33dafbff4a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X580VD.315
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X580VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX580VD.315:bd03/08/2018:svnASUSTeKCOMPUTERINC.:pnX580VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX580VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X580VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Fri Apr 24 16:45:55 2020
  xserver.configfile: default
  xserver.errors:
   NVIDIA(G0): GPU screens are not yet supported by the NVIDIA driver
   NVIDIA(G0): Failing initialization of X screen
   systemd-logind: failed to release device: Device not taken
   systemd-logind: failed to release device: Device not taken
   modeset(0): failed to set mode: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.8-2ubuntu2
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1874821] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

[Daniel van Vugt]

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

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 1550779, 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.


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

** This bug has been marked a duplicate of bug 1550779
   [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO 
underrun

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

Title:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

Status in linux package in Ubuntu:
  New

Bug description:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

  I have screen flashing and some tearing on HP Elitebook Folio G1. Had
  the same problem on 16.04 and 18.04. Previously was able to use
  "i915.enable_rc6=0" on 16.04 and then "intel_idle.max_cstate=4" on
  18.04 as workarounds. I'd like to help get to the bottom of this
  rather than a work-around, but will need guidance to participate.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 10:16:32 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 515 [8086:191e] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 515 [103c:8170]
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b58e Chicony Electronics Co., Ltd HP IR Camera
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b58f Chicony Electronics Co., Ltd HP HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteBook Folio G1
  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.4.0-26-generic 
root=UUID=3ef2b246-80ee-47da-ba11-fdfc1eef2362 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/05/2020
  dmi.bios.vendor: HP
  dmi.bios.version: N91 Ver. 01.45
  dmi.board.name: 8170
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 29.73
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN91Ver.01.45:bd01/05/2020:svnHP:pnHPEliteBookFolioG1:pvr:rvnHP:rn8170:rvrKBCVersion29.73:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook Folio G1
  dmi.product.sku: P2C88AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1874716] Re: Changing screen brightness fails

[Daniel van Vugt]

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

I think this is close enough to bug 1861532 that we should use that.

** This bug has been marked a duplicate of bug 1861532
   brightness control not working [Lenovo Legion Y540]

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

Title:
  Changing screen brightness fails

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Lenovo Legion with Nvidia card:

  FN+F5/F6 shows brightness changes, but the screen actually doesn't
  change at all.

  01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce
  GTX 1650 Mobile / Max-Q] (rev a1)

  nvidia  20430848  538 nvidia_uvm,nvidia_modeset
  nvidia_drm 45056  8
  nvidia_modeset   1114112  12 nvidia_drm
  nvidia_uvm966656  0
  nvme   49152  2
  nvme_core 102400  4 nvme

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 06:23:22 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:3ffb]
  InstallationDate: Installed on 2020-03-12 (42 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
  MachineType: LENOVO 81T2
  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.4.0-26-generic 
root=UUID=51068ea2-6b38-4cfc-a75f-4f404cd04685 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN35WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN35WW:bd11/23/2019:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
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/1874716/+subscriptions

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

[Touch-packages] [Bug 1875730] Re: Gnome Shell wallpaper corruption

[Daniel van Vugt]

** Summary changed:

- Ubuntu 19.10+ screen corruption
+ Gnome Shell wallpaper corruption

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

Title:
  Gnome Shell wallpaper corruption

Status in mutter package in Ubuntu:
  New

Bug description:
  Last week-end, after restarting my T470s running Ubuntu 19.10, I
  experienced a lot of visual glitches that didn't occur before.
  However, I had already noticed that some applications were
  unexpectedly freezing for about 5-10 seconds.

  I have already tried reinstalling xorg, without success. Then, I tried
  running Ubuntu 20.04 from a USB stick, and the problem doesn't occur.
  Today, I have upgraded Ubuntu to version 20.04 to see if it would fix
  it, but without success again.

  Note that when I restart the display server (Alt-F2 -> r -> Enter), it
  fixes the problem (sometimes I have to restart it several times).

  I would be happy to give you more information if you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 21:06:33 2020
  DistUpgraded: 2020-04-28 18:36:07,244 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.6, 5.3.0-46-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed
   virtualbox-guest, 6.1.6, 5.3.0-46-generic, x86_64: installed
   virtualbox-guest, 6.1.6, 5.4.0-26-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo HD Graphics 620 [17aa:224b]
  InstallationDate: Installed on 2019-09-19 (221 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20HGS14X00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=66402066-cedd-46a8-ba1a-67104f3abff7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-28 (0 days ago)
  dmi.bios.date: 02/27/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET58W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HGS14X00
  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: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET58W(1.37):bd02/27/2020:svnLENOVO:pn20HGS14X00:pvrThinkPadT470s:rvnLENOVO:rn20HGS14X00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HGS14X00
  dmi.product.sku: LENOVO_MT_20HG_BU_Think_FM_ThinkPad T470s
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101+git2004261830.fd7f37~oibaf~e
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.1~git2004280730.b4cc11~oibaf~e
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.1~git2004280730.b4cc11~oibaf~e
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1870088] Re: xz-utils ftbfs in focal

[Chris Halse Rogers]

Adding block-proposed tag, as this doesn't have any user-visible impact.

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

Title:
  xz-utils ftbfs in focal

Status in xz-utils package in Ubuntu:
  Confirmed
Status in xz-utils source package in Focal:
  Fix Committed
Status in xz-utils package in Debian:
  New

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18988321/+files/buildlog_ubuntu-focal-amd64.xz-utils_5.2.4-1_BUILDING.txt.gz

  dh build --parallel 
  make[2]: Leaving directory '/<>'
 dh_testroot -O--parallel
 dh_prep -O--parallel
 debian/rules override_dh_auto_install
  make[2]: Entering directory '/<>'
  dh_auto_install --builddirectory debian/xzdec-build
  dh_auto_install --builddirectory debian/normal-build
  dh_auto_install --builddirectory debian/static-build
  set -e; arch=$(dpkg-architecture -qDEB_HOST_MULTIARCH); \
  install -d debian/tmp/lib/$arch; \
  mv debian/tmp/usr/lib/$arch/liblzma.so.* debian/tmp/lib/$arch/; \
  dso=$(basename $(readlink debian/tmp/usr/lib/$arch/liblzma.so)); \
  ln -s -f /lib/$arch/$dso debian/tmp/usr/lib/$arch/liblzma.so
  mv: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*': No such 
file or directory
  make[2]: *** [debian/rules:34: override_dh_auto_install] Error 1
  make[2]: Leaving directory '/<>'
  make[1]: *** [debian/rules:4: install] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:4: binary] Error 2

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

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

[Touch-packages] [Bug 1870088] Re: xz-utils ftbfs in focal

[Chris Halse Rogers]

Hello Matthias, or anyone else affected,

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

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

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

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

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

** Changed in: xz-utils (Ubuntu Focal)
   Status: Confirmed => Fix Committed

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

** Tags removed: verification-needed verification-needed-focal
** Tags added: block-proposed-focal

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

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

Title:
  xz-utils ftbfs in focal

Status in xz-utils package in Ubuntu:
  Confirmed
Status in xz-utils source package in Focal:
  Fix Committed
Status in xz-utils package in Debian:
  New

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18988321/+files/buildlog_ubuntu-focal-amd64.xz-utils_5.2.4-1_BUILDING.txt.gz

  dh build --parallel 
  make[2]: Leaving directory '/<>'
 dh_testroot -O--parallel
 dh_prep -O--parallel
 debian/rules override_dh_auto_install
  make[2]: Entering directory '/<>'
  dh_auto_install --builddirectory debian/xzdec-build
  dh_auto_install --builddirectory debian/normal-build
  dh_auto_install --builddirectory debian/static-build
  set -e; arch=$(dpkg-architecture -qDEB_HOST_MULTIARCH); \
  install -d debian/tmp/lib/$arch; \
  mv debian/tmp/usr/lib/$arch/liblzma.so.* debian/tmp/lib/$arch/; \
  dso=$(basename $(readlink debian/tmp/usr/lib/$arch/liblzma.so)); \
  ln -s -f /lib/$arch/$dso debian/tmp/usr/lib/$arch/liblzma.so
  mv: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*': No such 
file or directory
  make[2]: *** [debian/rules:34: override_dh_auto_install] Error 1
  make[2]: Leaving directory '/<>'
  make[1]: *** [debian/rules:4: install] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:4: binary] Error 2

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

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

[Touch-packages] [Bug 1875369] Re: recording device won't change

[Daniel van Vugt]

Hmm, maybe that's part of the problem. Please try:

1. Log out.

2. Ctrl+Alt+F4 and lot into a text console

3. rm -rf .config/pulse
   exit

4. Ctrl+Alt+F1 and log in again.

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

Title:
  recording device won't change

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  installed from lubuntu .iso
  fully updated as of yesterday
  fresh boot this morning

  some of these details are most likely irrelevant, but it's what i do to keep 
things simple:
  ignore graphical login screen, change to VT2
  startx /usr/bin/xterm

  in the xterm:
  /opt/firefox/firefox&  #(nightly)
  openbox&
  pavucontrol-qt&
  pavucontrol&#results are the same regardless which of the pavucontrols is 
invoked

  in firefox:
  voice.google.com
  start a call

  in either of the pavucontrols:
  try to change the recording device:
  the menu opens, select the desired device, but it just doesn't change.
  doesn't matter which of the two pavucontrols was invoked

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Apr 27 07:49:12 2020
  InstallationDate: Installed on 2020-03-15 (42 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314)
  ProcEnviron:
   LC_TIME=en_DK.utf8
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/20/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ETA2WW (2.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C6008SUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C6008SUS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6008SUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Edge E540
  dmi.product.name: 20C6008SUS
  dmi.product.sku: LENOVO_MT_20C6_BU_Think_FM_ThinkPad Edge E540
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1873658] Proposed package upload rejected

[Chris Halse Rogers]

An upload of desktop-file-utils to focal-proposed has been rejected from
the upload queue for the following reason: "Please add an SRU-
appropriate bug description (particularly calling out the other flavour
test cases) and re-upload. Thanks!".

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

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

Status in desktop-file-utils package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Invalid
Status in desktop-file-utils source package in Focal:
  Confirmed
Status in gdebi source package in Focal:
  Invalid

Bug description:
  When you download a DEB file within 20.04 Ubuntu Beta and you double
  click it the file is opened by the archive manager.  I would expect
  the installer to open the file just like in previous versions of
  Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+subscriptions

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

[Touch-packages] [Bug 1875645] Re: Graphics corruption on shell on login screen and session screen

[Daniel van Vugt]

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

Thanks for the bug report. It appears at least half the problem was
using an old unsupported graphics driver, which makes this a duplicate
of bug 1867668.

To be sure you have removed that so we can focus on the remaining issues
more clearly, please now open a new bug by running:

  ubuntu-bug xorg

and then tell us the new bug ID.

** This bug has been marked a duplicate of bug 1867668
   Visual artifacts in Gnome Shell when using the 'intel' Xorg driver on 
8th/9th gen Intel hardware

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

Title:
  Graphics corruption on shell on login screen and session screen

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading from 19.10 to 20.04 I am seeing blocky green and
  purple artefacts on icons, background images and text. This is visible
  on the login screen and once logged in.

  Only the "shell" is corrupted and any subsequent changes, such as
  changing the background image, are displayed without corruption. The
  corruption is random but it is predictable that it will appear on the
  launcher icons, background image and shell menu icons and text.

  I've tried swapping between available graphics drivers but it makes no
  difference.

  Text corruption in menus is on particular glyphs selected at random.
  In the screen shots, for example, all upper-case and lower-case 'O's
  are currupted but on a subsequent reboot the affected glyphs will
  vary. On filing this bug I also notice that the pop-up modal password
  requests also displayed the corrupted glyphs. No programms run
  subsequently will display any problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 14:29:39 2020
  DistUpgraded: 2020-04-24 15:49:16,469 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0905]
 Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905]
  InstallationDate: Installed on 2019-12-05 (144 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 15 7590
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-26-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-24 (3 days ago)
  dmi.bios.date: 02/06/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0VYV0G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd02/06/2020:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing 

[Touch-packages] [Bug 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red

[Launchpad Bug Tracker]

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

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

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

Title:
  [nouveau, GeForce 7300 LE] screen background overlaid with scan type
  artifact in red

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  My desktop has both it's usual items in place; toolbar on left and
  desktop icons distributed around the screen. Then there's what appears
  to be a bunch of scan line, raster line artifacts, in red, laid over
  my normal background, which is a star field photo on what is
  ordinarily a black field.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 21 13:04:20 2020
  DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405]
  InstallationDate: Installed on 2016-08-19 (1249 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 531
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago)
  dmi.bios.date: 11/09/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0RY206
  dmi.board.vendor: Dell Inc.
  dmi.board.version: ���
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion:
  dmi.product.name: Inspiron 531
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct  3 10:41:28 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard KEYBOARD, id 8
   inputLogitech USB Trackball MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red

[Launchpad Bug Tracker]

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

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

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

Title:
  [nouveau, GeForce 7300 LE] screen background overlaid with scan type
  artifact in red

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  My desktop has both it's usual items in place; toolbar on left and
  desktop icons distributed around the screen. Then there's what appears
  to be a bunch of scan line, raster line artifacts, in red, laid over
  my normal background, which is a star field photo on what is
  ordinarily a black field.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 21 13:04:20 2020
  DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405]
  InstallationDate: Installed on 2016-08-19 (1249 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 531
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago)
  dmi.bios.date: 11/09/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0RY206
  dmi.board.vendor: Dell Inc.
  dmi.board.version: ���
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion:
  dmi.product.name: Inspiron 531
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct  3 10:41:28 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard KEYBOARD, id 8
   inputLogitech USB Trackball MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red

[Launchpad Bug Tracker]

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

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: New => Confirmed

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

Title:
  [nouveau, GeForce 7300 LE] screen background overlaid with scan type
  artifact in red

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  My desktop has both it's usual items in place; toolbar on left and
  desktop icons distributed around the screen. Then there's what appears
  to be a bunch of scan line, raster line artifacts, in red, laid over
  my normal background, which is a star field photo on what is
  ordinarily a black field.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 21 13:04:20 2020
  DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405]
  InstallationDate: Installed on 2016-08-19 (1249 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 531
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago)
  dmi.bios.date: 11/09/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0RY206
  dmi.board.vendor: Dell Inc.
  dmi.board.version: ���
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion:
  dmi.product.name: Inspiron 531
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct  3 10:41:28 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard KEYBOARD, id 8
   inputLogitech USB Trackball MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)

[Daniel van Vugt]

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

Since it's the same GPU generation and same driver I think we should
group this in with bug 1860483.

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

** This bug has been marked a duplicate of bug 1860483
   [nouveau, GeForce 7300 LE] screen background overlaid with scan type 
artifact in red

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

Title:
  Unusable graphics, nouveau + G73 (GEForce 7600)

Status in mesa package in Ubuntu:
  New

Bug description:
  This is an older card, but it worked well on ubuntu 12.x :)

  Booting "Try Ubuntu" on 20.04 get the correct resolution and 2
  displays, but the video glitches and shows all sorts of noise.  It is
  largely unusable (which makes filing this bug very hard).

  Safe Graphics works in low-res.

  The nvidia proprietary driver seems to not support this device any
  more.  I like this card because it has no fan (and I don't do a lot of
  graphics-intense stuff).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 18:13:48 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd G73 [GeForce 7600 GT] [1458:3417]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd  
---  priority=low
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: X58 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd12/30/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme6: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.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1875742] Re: Screen tearing shows when resizing windows

[Daniel van Vugt]

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

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 1835521, 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 1835521
   [regression] Windows flicker to black when resizing (Intel Apollo Lake)

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

Title:
  Screen tearing shows when resizing windows

Status in xorg package in Ubuntu:
  New

Bug description:
  When resizing terminator (terminal emulator) and the file browser the
  contents of the window disappears and I see various different
  corruption. Some horizontal lines and some that looks like old
  fashioned static on the TV

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 21:07:42 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 500 [8086:5a85] (rev 0b) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphics 500 [8086:2212]
  InstallationDate: Installed on 2020-04-23 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper Ezbook X3
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rz1ysp@/vmlinuz-5.4.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_rz1ysp ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Jumper10x.WP313P.1809100.NHNAUHL03
  dmi.board.asset.tag: Default string
  dmi.board.name: P313P
  dmi.board.vendor: Jumper
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.WP313P.1809100.NHNAUHL03:bd11/05/2019:svnJumper:pnEzbookX3:pvrDefaultstring:rvnJumper:rnP313P:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Ezbook
  dmi.product.name: Ezbook X3
  dmi.product.sku: 1809100
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1875751] Re: Fractional scaling options do not appear in wayland session

[Daniel van Vugt]

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

Wayland uses a different setting which the Settings GUI does not control
(bug 1871864). You can set it manually:

gsettings set org.gnome.mutter experimental-features "['scale-monitor-
framebuffer', 'x11-randr-fractional-scaling']"


** This bug has been marked a duplicate of bug 1871864
   Toggle "Fractional Scaling" does nothing on wayland

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

Title:
  Fractional scaling options do not appear in wayland session

Status in xorg package in Ubuntu:
  New

Bug description:
  When in a Wayland session, the options display the button to enable
  fractional scaling, but no options appear. Only 100% and 200% show

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 21:27:39 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 500 [8086:5a85] (rev 0b) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphics 500 [8086:2212]
  InstallationDate: Installed on 2020-04-23 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper Ezbook X3
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rz1ysp@/vmlinuz-5.4.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_rz1ysp ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Jumper10x.WP313P.1809100.NHNAUHL03
  dmi.board.asset.tag: Default string
  dmi.board.name: P313P
  dmi.board.vendor: Jumper
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.WP313P.1809100.NHNAUHL03:bd11/05/2019:svnJumper:pnEzbookX3:pvrDefaultstring:rvnJumper:rnP313P:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Ezbook
  dmi.product.name: Ezbook X3
  dmi.product.sku: 1809100
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1875759] Re: keeps crashing

[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.


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

Title:
  keeps crashing

Status in Ubuntu:
  Incomplete

Bug description:
  not sure it's a bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-96.97~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Apr 28 18:10:36 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems RS880M [Mobility Radeon HD 
4225/4250] [1179:ff1f]
  InstallationDate: Installed on 2020-04-19 (9 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: TOSHIBA Satellite L505D
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic 
root=UUID=4e2c2708-04af-4c97-ae5b-247752b16fe1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2009
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.00
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: AMD
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.00:bd09/07/2009:svnTOSHIBA:pnSatelliteL505D:pvrPSLV6U-01F009:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone:
  dmi.product.family: Type1Family
  dmi.product.name: Satellite L505D
  dmi.product.version: PSLV6U-01F009
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Apr 28 17:50:45 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1837914] Autopkgtest regression report (systemd/229-4ubuntu21.28)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (229-4ubuntu21.28) for xenial 
have finished running.
The following regressions have been reported in tests triggered by the package:

udisks2/2.1.7-1ubuntu1 (amd64)
multipath-tools/0.5.0+git1.656f8865-5ubuntu2.5 (armhf)
nplan/0.32~16.04.7 (amd64)


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

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

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

Thank you!

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

Title:
  restart systemd-jounald fails

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

Bug description:
  [impact]

  in some situations, restarting journald causes assertion failure.

  [test case]

  intermittently, when restarting journald.  See upstream bug for repro
  details.

  [regression potential]

  this adjusts the journal file destructor, so any regression would
  likely occur when cleaning up journal files and/or
  stopping/restarting.

  [scope]

  this is fixed by commit c377a6f3ad3d9bed4ce7e873e8e9ec6b1650c57d which
  is included in Focal.  This is needed for Eoan and earlier.

  [original description]

  While restarting systemd-jounald, the following error message occurs:

  systemd-journald[28007]: Assertion 'f' failed at ../src/journal
  /journal-file.c:143, function journal_file_close(). Aborting.

  release: Ubuntu 16.04.5 LTS
  systemd version: 229-4ubuntu21.22

  This issue is reported at
  https://github.com/systemd/systemd/issues/12400 and solved at
  https://github.com/systemd/systemd/pull/12679

  Please cherry-pick this fix to the ubuntu16.04 package.

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

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

[Touch-packages] [Bug 1867421] Autopkgtest regression report (systemd/229-4ubuntu21.28)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (229-4ubuntu21.28) for xenial 
have finished running.
The following regressions have been reported in tests triggered by the package:

udisks2/2.1.7-1ubuntu1 (amd64)
multipath-tools/0.5.0+git1.656f8865-5ubuntu2.5 (armhf)
nplan/0.32~16.04.7 (amd64)


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

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

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

Thank you!

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

Title:
  Microsoft Classic IntelliMouse moves way too fast

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

Bug description:
  [impact]

  Microsoft Classic IntelliMouse moves way too fast to be usable.

  [test case]

  on a bionic system, connect affected mouse and attempt to move
  pointer, note it moves too fast.

  [regression potential]

  as this adds a hwdb entry for a mouse using vendor/product id and name
  matching, any regression would likely involve incorrectly setting dpi
  on a different mouse than intended.

  [scope]

  fixed by upstream commit 26d7cf3daf08b279bdd2e484936268e1e88648d4
  which is included starting in v240, so this is already fixed in Eoan
  and later.

  This is needed only for Xenial and Bionic.

  [original description]

  Microsoft Classic IntelliMouse moves way too fast to be usable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.39
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 14 17:12:25 2020
  InstallationDate: Installed on 2019-01-02 (436 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 
4000 V1.0
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 045e:0823 Microsoft Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 10M7CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=e226e89e-7b9d-4135-a662-4829015a56f0 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M16KT47A
  dmi.board.name: 3102
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259627060531
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060531:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710s
  dmi.product.name: 10M7CTO1WW
  dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s
  dmi.product.version: ThinkCentre M710s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1862657] Autopkgtest regression report (systemd/229-4ubuntu21.28)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (229-4ubuntu21.28) for xenial 
have finished running.
The following regressions have been reported in tests triggered by the package:

udisks2/2.1.7-1ubuntu1 (amd64)
multipath-tools/0.5.0+git1.656f8865-5ubuntu2.5 (armhf)
nplan/0.32~16.04.7 (amd64)


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

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

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

Thank you!

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

Title:
  systemd autopkgtest 'logind' fails when running with linux-kvm

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

Bug description:
  [impact]

  the logind autopkgtest tries to access /sys/power/state, but because
  linux-kvm has CONFIG_PM unset, there is no /sys/power/state file

  [test case]

  check autopkgtest, e.g.:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/systemd/20200210_144351_da247@/log.gz

  autopkgtest [13:48:53]: test logind: ---]
  autopkgtest [13:48:53]: test logind:  - - - - - - - - - - results - - - - - - 
- - - -
  logind   FAIL stderr: grep: /sys/power/state: No such file or 
directory
  autopkgtest [13:48:53]: test logind:  - - - - - - - - - - stderr - - - - - - 
- - - -
  grep: /sys/power/state: No such file or directory

  [regression potential]

  regressions would likely involve incorrectly skipped logind test.

  [scope]

  this fails for all releases; Xenial, Bionic, Eoan, and Focal.

  [other info]

  it's unclear if linux-kvm should have CONFIG_PM (and other config)
  enabled or not.

  However, it's not the intention of systemd's autopkgtests to look for
  missing config in the kernel; the test already skips if 'mem' isn't in
  /sys/power/state, so it should also skip if /sys/power/state isn't
  present at all.

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

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

[Touch-packages] [Bug 1858412] Autopkgtest regression report (systemd/229-4ubuntu21.28)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (229-4ubuntu21.28) for xenial 
have finished running.
The following regressions have been reported in tests triggered by the package:

udisks2/2.1.7-1ubuntu1 (amd64)
multipath-tools/0.5.0+git1.656f8865-5ubuntu2.5 (armhf)
nplan/0.32~16.04.7 (amd64)


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

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

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

Thank you!

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

Title:
  systemd vacuuming does not work for remote journals

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Committed

Bug description:
  [impact]

  attempting to vacuum journals using -D with the 'root' (in journald
  terms) journal directory fails to perform any vacuuming.  This can
  lead to journal files continually increasing in size and filling up
  the filesystem.

  [test case]

  see original description below.

  [regession potential]

  this removes a check in the code when iterating journal directories
  during vacuuming, so any regression would likely occur during
  vacuuming, possibly causing failure to vacuum.

  [scope]

  this is fixed upstream by commit
  c488660e6edb3c1375ab62514a8df035c3d712bf which is included starting in
  version 244, so this is already included in Focal.  This is needed for
  Eoan, Bionic, and Xenial.

  [original description]

  systemd has an issue in regard to vacuuming remote journals:
  https://github.com/systemd/systemd/issues/2376 - this affects 18.04 as
  this version still has this problem.

  Steps to reproduce on "Description: Ubuntu 18.04.3 LTS":

  root@1:~# du -hs /var/log/journal/remote/
  8.6G  /var/log/journal/remote/
  root@1:~# journalctl -D /var/log/journal/remote --vacuum-size=100M
  root@1:~# du -hs /var/log/journal/remote/
  8.6G  /var/log/journal/remote/

  Would it be possible to backport this trivial patch
  https://github.com/systemd/systemd/pull/13924 into 18.04?

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

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

[Touch-packages] [Bug 1831459] Autopkgtest regression report (systemd/229-4ubuntu21.28)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (229-4ubuntu21.28) for xenial 
have finished running.
The following regressions have been reported in tests triggered by the package:

udisks2/2.1.7-1ubuntu1 (amd64)
multipath-tools/0.5.0+git1.656f8865-5ubuntu2.5 (armhf)
nplan/0.32~16.04.7 (amd64)


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

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

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

Thank you!

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

Title:
  'storage' test needs to wait for systemd-cryptsetup to be active
  before stopping it

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [impact]

  test case fails because it does not wait for the service to become
  active before stopping it, resulting in failure to rmmod the
  scsi_debug module because it's still in use.

  [test case]

  check 'storage' test results for systemd in autopkgtest logs, e.g.:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/ppc64el/s/systemd/20190601_160043_a5281@/log.gz

  [regression potential]

  low; test case fix only.

  [other info]

  detected and reported by @cascardo in bug 1814373 comment 4 and 5, but
  separate (non-test) systemd bugfix uploaded for that bug so opening
  this bug to track fixing the test case.

  larger fixes/improvements to 'storage' testcase in bug 1829347, but
  those rejected.

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

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

[Touch-packages] [Bug 1839290] Autopkgtest regression report (systemd/229-4ubuntu21.28)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (229-4ubuntu21.28) for xenial 
have finished running.
The following regressions have been reported in tests triggered by the package:

udisks2/2.1.7-1ubuntu1 (amd64)
multipath-tools/0.5.0+git1.656f8865-5ubuntu2.5 (armhf)
nplan/0.32~16.04.7 (amd64)


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

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

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

Thank you!

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

Title:
  systemd doesn't restart a service after crashes

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [impact]

  when a service configured to restart crashes, under certain
  configurations, that service is not correctly restarted.

  [test case]

  see comment 8

  [regression potential]

  this changes the job mode of manager-triggered restarts to 'replace'
  any existing queued job(s), instead of failing if there are queued
  job(s).  thus any regressions would occur when a service fails, that
  is configured to restart on failure.

  [scope]

  This is needed only for Xenial and Bionic.

  this is fixed with commit 03ff2dc71ecb09272d728d458498b44f7f132f51
  which is included already in Eoan.

  Fixed in Disco with the backported v240 patch from
  
https://github.com/systemd/systemd/commit/677b4cc753f183731fc54fcb68ad46f806c394bc

  [other info]

  original description:
  ---

  Affected versions of OS and systemd:
  $ cat /etc/issue
  Ubuntu 16.04.6 LTS \n \l
  $ systemd --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  Affected packages:
  systemd 229-4ubuntu21.22 and previous versions.

  Expected behaviour you didn't see:
  Scheduling restart of failed service.
  A process crashed by sigabrt and didn't restart.

  Description:
  The bug was reported to a systemd upstream repository: 
https://github.com/systemd/systemd/issues/11456
  The bug was fixed and accepted to the master branch: 
https://github.com/systemd/systemd/pull/11467/files

  Action:
  Include this patch to Ubuntu 16.04 and other version of Ubuntu which are 
supported.

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

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

[Touch-packages] [Bug 1868892] Autopkgtest regression report (systemd/229-4ubuntu21.28)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (229-4ubuntu21.28) for xenial 
have finished running.
The following regressions have been reported in tests triggered by the package:

udisks2/2.1.7-1ubuntu1 (amd64)
multipath-tools/0.5.0+git1.656f8865-5ubuntu2.5 (armhf)
nplan/0.32~16.04.7 (amd64)


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

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

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

Thank you!

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

Title:
  initramfs-tools/hooks/udev for network *.link really sucks

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Eoan:
  Fix Committed
Status in systemd source package in Focal:
  In Progress

Bug description:
  [impact]

  If the /{etc,lib}/systemd/network directory itself is a symlink, the find
  command will not actually find any of the files in the dir it links to.

  [test case]

  $ sudo touch /etc/systemd/network/lp1868892.link
  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic
  ...
  $ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
  usr/lib/systemd/network/lp1868892.link
  $ sudo mv /etc/systemd/network /etc/systemd/network.abc
  $ sudo ln -s network.abc /etc/systemd/network
  $ sudo update-initramfs -u
  $ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
  $ 

  [regression potential]

  this adjusts how link files are included in the initramfs, so
  regressions would likely occur when creating new initramfs, such as
  failure to create initramfs at all, or failure to properly copy link
  files into the initramfs, causing network setup failure.

  [scope]

  this is a Debian/Ubuntu specific file, and the Debian MR was just
  opened, so this is needed for Debian and all releases of Ubuntu.

  [other info]

  This bug likely has a very limited impact, as it is uncommon to
  symlink either the /lib/systemd/network or /etc/systemd/network dirs.

  [original description]

  If one creates e.g. /etc/systemd/network.cu and
  /etc/systemd/network.fc and symlinks  /etc/systemd/network to one of
  them, network setup will fail on reboot, because /usr/share/initramfs-
  tools/hooks/udev does a very poor job: it simply checks for a
  directory instead of the link files and therefore skips copying
  required files to the ram image. Another poor job is done when copying
  the files to the ram image: instead of following symlinks it copies
  them as which in turn makes them useless, because it does not copy the
  related dirs and thus the symlinks point to nothing. So keeping the
  system in an consistent state which such poor scripts is very hard,
  asking for trouble.

  Suggested fix is attached.

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

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

[Touch-packages] [Bug 1870194] Autopkgtest regression report (systemd/229-4ubuntu21.28)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (229-4ubuntu21.28) for xenial 
have finished running.
The following regressions have been reported in tests triggered by the package:

udisks2/2.1.7-1ubuntu1 (amd64)
multipath-tools/0.5.0+git1.656f8865-5ubuntu2.5 (armhf)
nplan/0.32~16.04.7 (amd64)


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

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

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

Thank you!

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

Title:
  systemd-fsckd autopkgtest always fails on arm64

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  [impact]

  the autopkgtest arm64 instances fail to reboot and always fail the
  test

  [test case]

  check autopkgtest results for arm64 instances, e.g.
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/s/systemd/20200401_09_34f60@/log.gz

  [regression potential]

  these tests have never successfully run on arm64, so skipping them on
  arm64 should have almost no regression potential; any regression would
  likely involve incorrectly failed test or not-run tests.

  [scope]

  this test is already skipped on arm64 starting on Eoan.  This is
  needed only for Xenial and Bionic.

  [other info]

  related is bug 1748280

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

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

[Touch-packages] [Bug 1862232] Autopkgtest regression report (systemd/229-4ubuntu21.28)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (229-4ubuntu21.28) for xenial 
have finished running.
The following regressions have been reported in tests triggered by the package:

udisks2/2.1.7-1ubuntu1 (amd64)
multipath-tools/0.5.0+git1.656f8865-5ubuntu2.5 (armhf)
nplan/0.32~16.04.7 (amd64)


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

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

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

Thank you!

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

Title:
  Long hostname causes networking setup to fail

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  [impact]

  networkd fails to bring up networking on systems with long hostname

  [test case]

  setting the hostname:

  $ sudo hostnamectl set-hostname
  asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf

  then reboot and check the networking.

  [regression potential]

  as this adjusts logging and certain error handling while performing
  dhcp, any regression would likely cause dhcp failure.

  [scope]

  this is fixed by upstream commit
  a8494759b4f14af5337391727ba295ab708b92f9 (along with some associated
  commits around it), which is included starting in v240, so this is
  included already in Eoan and later.

  This is needed in Bionic and Xenial.

  [other info]

  the problem around this is that Linux sets HOST_NAME_MAX to 64, but
  RFC 1035 limits DNS labels to 63 characters, so any host with a max-
  length single-label hostname (i.e. a 64 character hostname with no
  dots) will be "valid" from Linux's perspective, but will violate RFC
  1035 and thus systemd will consider it invalid and won't pass it to
  the dhcp server.

  Also note that a 64-character hostname that is *not* single-label
  (i.e. a hostname with at least 1 dot) will not cause this problem.

  The systemd patches continue to reject sending the invalid hostname to
  the dhcp server, but do not prevent networkd from finishing setting up
  networking.

  [original description]

  1) ubuntu version
  # lsb_release -rd
  Description:Ubuntu 18.04.3 LTS
  Release:18.04

  2) package version
  # apt-cache policy systemd
  systemd:
    Installed: 237-3ubuntu10.31
    Candidate: 237-3ubuntu10.31
    Version table:
   *** 237-3ubuntu10.31 500
  500 http://mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 
Packag
  es
  100 /var/lib/dpkg/status
   237-3ubuntu10.29 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   237-3ubuntu10 500
  500 http://mirrors.digitalocean.com/ubuntu bionic/main amd64 Packages

  3) I expect the network to come online correctly regardless of how
  long the hostname is. This is what happens with both 14.0 and 19.0 (I
  tested the same behavior with both of them).

  4) the external network interface fails to be configured and is stuck
  in a (pending) state as reported by networkctl status -a

  setting the hostname:

  # hostnamectl set-hostname
  asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf

  after rebooting the machine, it no longer has network access.

  # journalctl
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd[1]: 
Starting Wait for Network to be Configured...
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: eth0: Link state is up-to-date
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: eth0: found matching network 
'/run/systemd/network/10-netplan-eth0.network'
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: sd-netlink: callback failed: Invalid argument
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: lo: Link state is up-to-date

  # networkctl status -a:
  ● 1: lo
     Link File: /lib/systemd/network/99-default.link
  Network File: n/a
  Type: loopback
     State: carrier (unmanaged)
   Address: 127.0.0.1
    ::1

  ● 2: eth0
     Link File: /run/systemd/network/10-netplan-eth0.link
  Network File: /run/systemd/network/10-netplan-eth0.network
  Type: ether
     State: off (pending)
  Path: pci-:00:03.0
    Driver: virtio_net
    Vendor: Red Hat, Inc.
     Model: 

[Touch-packages] [Bug 1847816] Autopkgtest regression report (systemd/229-4ubuntu21.28)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (229-4ubuntu21.28) for xenial 
have finished running.
The following regressions have been reported in tests triggered by the package:

udisks2/2.1.7-1ubuntu1 (amd64)
multipath-tools/0.5.0+git1.656f8865-5ubuntu2.5 (armhf)
nplan/0.32~16.04.7 (amd64)


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

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

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

Thank you!

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

Title:
  storage autopkgtest always fails with linux-{kvm,azure,etc} kernels
  that don't include scsi_debug module

Status in autopkgtest-cloud:
  Fix Released
Status in linux-kvm package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in linux-kvm source package in Xenial:
  New
Status in systemd source package in Xenial:
  Fix Committed
Status in linux-kvm source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in linux-kvm source package in Disco:
  New
Status in systemd source package in Disco:
  Won't Fix
Status in linux-kvm source package in Eoan:
  New
Status in systemd source package in Eoan:
  Fix Released
Status in linux-kvm source package in Focal:
  New
Status in systemd source package in Focal:
  Fix Released

Bug description:
  Note: this bug touches on multiple packages:
  - autopkgtest-cloud: merge request open to install 'modules-extra' package
  - systemd: update autopkgtest to skip test if scsi_debug module isn't 
available (SRU template below is for this change)
  - linux-kvm: has CONFIG_SCSI_DEBUG unset, but would be good to have 
scsi_debug module built for this kernel

  [SRU template for systemd]

  [impact]

  the 'storage' autopkgtest requires the 'scsi_debug' module, and if it
  can't load it (and it's not built-in), the test fails.  On some custom
  kernels, this module is included in the new 'linux-modules-extra-*'
  deb which isn't installed by default, so the test always fails when
  doing a reverse-dep autopkgtest using such a kernel's meta pkg.

  Additionally, some custom kernels, like linux-kvm, have SCSI_DEBUG
  disabled entirely; for those kernels, it will never be possible to
  load the scsi_debug module and the test should be skipped.

  [test case]

  run the 'storage' autopkgtest with a custom kernel that doesn't
  provide the scsi_debug module in the standard linux-modules deb, or
  check the autopkgtest.u.c history, for example:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/amd64/s/systemd/20191209_150835_237a5@/log.gz

  [regression potential]

  as this modifies one of the autopkgtest --setup-commands, a regression
  would most likely cause immediate test failure due to failing to
  install the proper linux-* debs.

  For the systemd 'storage' test change, this only skips the test if the
  scsi_debug module can't be loaded (and isn't already present, i.e.
  loaded or built-in).  Any regression potential from that is low, but
  likely would involve incorrect test skips and/or missing valid
  problems due to skipping the test.

  [scope]

  systemd in all releases needs to have its 'storage' test updated

To manage notifications about this bug go to:
https://bugs.launchpad.net/autopkgtest-cloud/+bug/1847816/+subscriptions

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

[Touch-packages] [Bug 1873031] Re: 245.4-2ubuntu1 throws stderr messages on timesyncd restart in its dhcp hook

[Mathew Hodson]

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

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

Title:
  245.4-2ubuntu1 throws stderr messages on timesyncd restart in its dhcp
  hook

Status in chrony package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  systemd has broken this by the split of timesyncd.

  On a system that installed chrony (or other NTP servers) you'll have:

  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  VersionArchitecture Description
  
+++-=-==--===
  ii  chrony3.5-6ubuntu3   amd64Versatile implementation of 
the Network Time Protocol
  rc  systemd-timesyncd 245.4-4ubuntu1 amd64minimalistic service to 
synchronize local time with NTP servers

  That left this behind:
/etc/dhcp/dhclient-exit-hooks.d/timesyncd

  And if you now run a dhcp based time server push it will fail very
  badly.

  P.S. This is triggered by the chrony autopkgtests but not an issue in chrony 
yet it is in systemd.
  But due to that one can use [1] as easy reproducer, I wonder how systemd 
slipped by this issue in autopkgtest?

  It contains:
  systemctl try-restart systemd-timesyncd.service || true

  Which in the setup the system now has will trigger:
   sudo dhclient dummy0
  Failed to try-restart systemd-timesyncd.service: Unit 
systemd-timesyncd.service is masked.

  P.S. I'll harden the chrony test to not stumble over this but it
  should be revisited for systemd to provide a better fix than causing
  this message every time (maybe pre-check if it is enabled and
  unmasked)?

  [1]: https://git.launchpad.net/ubuntu/+source/chrony/tree/debian/tests
  /time-sources-from-dhcp-servers?h=ubuntu/focal-devel

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

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

[Touch-packages] [Bug 1875620] Re: [Vostro 5590, Realtek ALC3204, Black Headphone Out, Front] Pulseaudio fails to detect card

[Hui Wang]

The version of the linux-firmware is correct, but the content of it is
not.

Could you please temporarily backup the existing sof-firmware:
sudo mv /lib/firmware/intel/sof /lib/firmware/intel/sof-bak
sudo mv /lib/firmware/intel/sof-tplg /lib/firmware/intel/sof-tplg-bak

sudo apt reinstall linux-firmware

reboot


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

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

Title:
  [Vostro 5590, Realtek ALC3204, Black Headphone Out, Front] Pulseaudio
  fails to detect card

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 12:49:51 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00
  InstallationDate: Installed on 2020-02-05 (82 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_Jack: Black Headphone Out, Front
  Title: [Vostro 5590, Realtek ALC3204, Black Headphone Out, Front] Pulseaudio 
fails to detect card
  UpgradeStatus: Upgraded to focal on 2020-04-28 (0 days ago)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 051P23
  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:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5590
  dmi.product.sku: 095A
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1872059] Proposed package upload rejected

[Chris Halse Rogers]

An upload of apport to focal-proposed has been rejected from the upload
queue for the following reason: "Groovy already has an apport verson
2.20.11-0ubuntu28 uploaded, withThis will need a new upload with a new
version.".

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

Title:
  missing hardware/runtime info when reporing linux-firmware bugs via
  apport

Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Bionic:
  Invalid
Status in linux-firmware source package in Eoan:
  Invalid
Status in apport source package in Focal:
  In Progress
Status in linux-firmware source package in Focal:
  Invalid

Bug description:
  linux-firmware doesn't install any package hooks for apport, so it
  will only carry some default items leaving hardware list, kernel
  messages unattached. Suggest symlink /usr/share/apport/package-hooks
  /source_linux-firmware.py to source_linux.py as other linux image debs
  do in bug 1847967.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 10 19:15:15 2020
  Dependencies:
   
  InstallationDate: Installed on 2019-09-28 (194 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Dependencies:
   
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-09-28 (194 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  MachineType: Apple Inc. MacBookPro11,1
  NonfreeKernelModules: wl
  Package: linux-firmware
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic 
root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet 
splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 06/13/2019
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 156.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

[Mathew Hodson]

** Changed in: network-manager (Ubuntu Bionic)
   Importance: Undecided => Medium

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Bionic:
  Fix Committed
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Fix Committed
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  [Test Case]

  Assume that test vm and host are ppc64

  1. deploy ppc64 vm instance ( with 1 cpu )
  2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
  3. apt install network-manager rfkill
  4. modify /etc/netplan/[conf], renderer as NetworkManager
  5. netplan apply
  6. run below command
  - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli 
radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi

  enabled
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  enabled
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  enabled

  second 'enabled' should be 'disabled' but not updated properly.

  Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
  rfkill block/unblock and nmcli radio wifi will help updating status changes 
after rfkill block/unblock.

  [Regression Potential]

  This fixes testcase only, so any regression would cause incorrect test
  pass/fail, and might cause other missed bugs.

  [scope]

  this is needed for all releases.  Debian does not include this
  autopkgtest, and so does not need this fix.

  [Other Info]

  this is caused by the 'systemd-rfkill.socket' listening to rfkill, and
  starting up 'systemd-rfkill.service' for any change.  On a 1-cpu
  system (which all autopkgtest instances for network-manager are), this
  service startup sometimes blocks the uevent from reaching network-
  manager before the autopkgtest proceeds to call nmcli to check the
  rfkill status.  This causes the test case to fail.

  There are (at least) 2 options to fix this:
  1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest
  2) call udevadm settle between the rfkill block/unblock and the nmcli call to 
check status

  This does not need to be fixed outside the test case, as normal nmcli
  use should be not done by users in a script immediately after changing
  rfkill state, nor is there anything that either rfkill or nmcli could
  even do to address this (technically, nmcli could internally issue a
  'udevadm settle' every time it's called, but that seems paranoid and
  extreme).

  [original description]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

  # original test case

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

To 

[Touch-packages] [Bug 1873777] Re: Update to 2.64.2

[Chris Halse Rogers]

The same reason that Mozilla, Google, and Microsoft reverted disabling
TLS 1.0/1.1: government websites which don't support TLS 1.2 (see also:
https://www.mozilla.org/en-US/firefox/74.0/releasenotes/)

** Changed in: glib-networking (Ubuntu Focal)
   Status: Incomplete => Fix Committed

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

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

Title:
  Update to 2.64.2

Status in glib-networking package in Ubuntu:
  Fix Released
Status in glib-networking source package in Focal:
  Fix Committed

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

  * Test case

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

  Check that GNOME web still works correctly

  * Regression potential

  The update restore the TLS 1.0/1.1 protocols due to COVID-19, try to
  browse one of those websites from the GNOME browser

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

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

[Touch-packages] [Bug 1873777] Please test proposed package

[Chris Halse Rogers]

Hello Sebastien, or anyone else affected,

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

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

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

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

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

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

Title:
  Update to 2.64.2

Status in glib-networking package in Ubuntu:
  Fix Released
Status in glib-networking source package in Focal:
  Fix Committed

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

  * Test case

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

  Check that GNOME web still works correctly

  * Regression potential

  The update restore the TLS 1.0/1.1 protocols due to COVID-19, try to
  browse one of those websites from the GNOME browser

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

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

[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

[Brian Murray]

Hello Kleber, or anyone else affected,

Accepted network-manager into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.10.6-2ubuntu1.5 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: network-manager (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Bionic:
  Fix Committed
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Fix Committed
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  [Test Case]

  Assume that test vm and host are ppc64

  1. deploy ppc64 vm instance ( with 1 cpu )
  2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
  3. apt install network-manager rfkill
  4. modify /etc/netplan/[conf], renderer as NetworkManager
  5. netplan apply
  6. run below command
  - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli 
radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi

  enabled
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  enabled
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  enabled

  second 'enabled' should be 'disabled' but not updated properly.

  Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
  rfkill block/unblock and nmcli radio wifi will help updating status changes 
after rfkill block/unblock.

  [Regression Potential]

  This fixes testcase only, so any regression would cause incorrect test
  pass/fail, and might cause other missed bugs.

  [scope]

  this is needed for all releases.  Debian does not include this
  autopkgtest, and so does not need this fix.

  [Other Info]

  this is caused by the 'systemd-rfkill.socket' listening to 

[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

[Brian Murray]

Hello Kleber, or anyone else affected,

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

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

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

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

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

** Changed in: network-manager (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

** Changed in: network-manager (Ubuntu Eoan)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-eoan

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Bionic:
  In Progress
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Fix Committed
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  [Test Case]

  Assume that test vm and host are ppc64

  1. deploy ppc64 vm instance ( with 1 cpu )
  2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
  3. apt install network-manager rfkill
  4. modify /etc/netplan/[conf], renderer as NetworkManager
  5. netplan apply
  6. run below command
  - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli 
radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi

  enabled
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  enabled
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  enabled

  second 'enabled' should be 'disabled' but not updated properly.

  Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
  rfkill block/unblock and nmcli radio wifi will help updating status changes 
after rfkill block/unblock.

  [Regression Potential]

  This fixes testcase only, so any regression would cause incorrect test
  pass/fail, and might cause other missed bugs.

  [scope]

  this is needed for all releases.  Debian does not 

[Touch-packages] [Bug 1733321] Please test proposed package

[Brian Murray]

Hello Kleber, or anyone else affected,

Accepted network-manager into eoan-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.20.4-2ubuntu2.3 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Bionic:
  In Progress
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Fix Committed
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  [Test Case]

  Assume that test vm and host are ppc64

  1. deploy ppc64 vm instance ( with 1 cpu )
  2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
  3. apt install network-manager rfkill
  4. modify /etc/netplan/[conf], renderer as NetworkManager
  5. netplan apply
  6. run below command
  - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli 
radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi

  enabled
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  enabled
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  enabled

  second 'enabled' should be 'disabled' but not updated properly.

  Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
  rfkill block/unblock and nmcli radio wifi will help updating status changes 
after rfkill block/unblock.

  [Regression Potential]

  This fixes testcase only, so any regression would cause incorrect test
  pass/fail, and might cause other missed bugs.

  [scope]

  this is needed for all releases.  Debian does not include this
  autopkgtest, and so does not need this fix.

  [Other Info]

  this is caused by the 'systemd-rfkill.socket' listening to rfkill, and
  starting up 'systemd-rfkill.service' for any change.  On a 1-cpu
  system (which all autopkgtest instances for network-manager are), 

[Touch-packages] [Bug 1873777] Re: Update to 2.64.2

[Brian Murray]

How is TLS1.0/1.1 related to Covid-19? I didn't see any explanation
upstream.

** Also affects: glib-networking (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: glib-networking (Ubuntu Focal)
   Status: New => Incomplete

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

Title:
  Update to 2.64.2

Status in glib-networking package in Ubuntu:
  Fix Released
Status in glib-networking source package in Focal:
  Incomplete

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

  * Test case

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

  Check that GNOME web still works correctly

  * Regression potential

  The update restore the TLS 1.0/1.1 protocols due to COVID-19, try to
  browse one of those websites from the GNOME browser

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

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

[Touch-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

[Pablo Catalina]

I had the same problem with a Thunderbolt audio device and BT. I removed 
.config/pulse and started working fine again.
Not sure if it will fail, but for the moment is working.

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

Title:
  External audio device shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker, or none at
  all.

Status in gnome-control-center:
  Unknown
Status in PulseAudio:
  New
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  In Progress
Status in gnome-control-center source package in Focal:
  Invalid
Status in pulseaudio source package in Focal:
  In Progress

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

  1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
  2. Make sure it's the one selected as "Output device"
  3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  5. Try to switch back to the BT device and click Test
  -> same result as in step 3

  Tested with 2 different BT devices (one headset and one speaker) as
  well as a USB audio interface (Zoom H2N microphone).

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+subscriptions

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

[Touch-packages] [Bug 1875759] [NEW] keeps crashing

[Billy Blake]

Public bug reported:

not sure it's a bug

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-96.97~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-96-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.23
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Apr 28 18:10:36 2020
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems RS880M [Mobility Radeon HD 
4225/4250] [1179:ff1f]
InstallationDate: Installed on 2020-04-19 (9 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: TOSHIBA Satellite L505D
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic 
root=UUID=4e2c2708-04af-4c97-ae5b-247752b16fe1 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/07/2009
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.00
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: AMD
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.00:bd09/07/2009:svnTOSHIBA:pnSatelliteL505D:pvrPSLV6U-01F009:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone:
dmi.product.family: Type1Family
dmi.product.name: Satellite L505D
dmi.product.version: PSLV6U-01F009
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Apr 28 17:50:45 2020
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  keeps crashing

Status in xorg package in Ubuntu:
  New

Bug description:
  not sure it's a bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-96.97~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Apr 28 18:10:36 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems RS880M [Mobility Radeon HD 
4225/4250] [1179:ff1f]
  InstallationDate: Installed on 2020-04-19 (9 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: TOSHIBA Satellite L505D
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic 
root=UUID=4e2c2708-04af-4c97-ae5b-247752b16fe1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2009
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.00
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: AMD
  dmi.chassis.version: None
  dmi.modalias: 

[Touch-packages] [Bug 1874501] Re: vgscan --mknodes creates block device multipath nodes in /dev/mapper

[Ryan Harper]

I don't think this is the right fix.  We need to test that it doesn't
prevent vgscan from finding and creating /dev/vg/lv device files outside
of of multipath.

The real fix involves:

  1) omitting the call to vgmknodes if there are no volume groups present
  2) if vgnodes are present, device_mapper/libdm-common.c should determine if 
DM_DISABLE_LIBRARY_FALLBACK should be set in the same way that dmsetup.c does.

I'd much prefer upstream to produce a proper fix.

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

Title:
  vgscan --mknodes creates block device multipath nodes in /dev/mapper

Status in Ubuntu on IBM z Systems:
  New
Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 20.04 LTS
  Release:20.04

  # apt-cache policy multipath-tools
  multipath-tools:
Installed: 0.8.3-1ubuntu2
Candidate: 0.8.3-1ubuntu2
Version table:
   *** 0.8.3-1ubuntu2 500
  500 http://ports.ubuntu.com/ubuntu-ports focal/main s390x Packages
  100 /var/lib/dpkg/status

  
  /dev/mapper/mpatha is symlink which points to ../../dm-X device

  /dev/mapper/mpath is block device

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: multipath-tools 0.8.3-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: s390x
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  Date: Thu Apr 23 17:32:12 2020
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release s390x 
(20200423.1)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: multipath-tools
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.multipath.conf:
   defaults {
   user_friendly_names yes
   skip_kpartx no
   verbosity 4
   }
  mtime.conffile..etc.multipath.conf: 2020-04-23T15:47:28.659850

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

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

[Touch-packages] [Bug 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS

[Lucas Kanashiro]

Thank you for taking the time to file a bug report.

In order to reproduce the bug you faced, could you please share your
config files? OpenSSH and OpenVPN ones. Otherwise we cannot do anything.

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

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

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

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

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

Title:
  SSH fails with connection timed out - in VPN and hangs here "expecting
  SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS

Status in linux package in Ubuntu:
  Invalid
Status in openssh package in Ubuntu:
  Incomplete
Status in openvpn package in Ubuntu:
  Incomplete

Bug description:
  Hello Team,

  SSH timeout issue, once connect to VPN.

  Environment

  ==
  Dell XPS 9570 
  Ubuntu 16.04.6 Xenial Xerus)
  kernel - 4.15.0-55-generic

  $dpkg -l | grep -i openssh
  ii  openssh-client 1:7.2p2-4ubuntu2.8  --> 
  ii  openssh-server 1:7.2p2-4ubuntu2.8  
  ii  openssh-sftp-server  1:7.2p2-4ubuntu2.8

  
  VPN tunnel info 
  
  vpn0  Link encap:UNSPEC  HWaddr 
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:IP  P-t-P:xx  Mask:255.255.252.0
inet6 addr: fe80::b8e2:bea4:2e62:fe08/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1406  Metric:1
RX packets:962 errors:0 dropped:0 overruns:0 frame:0
TX packets:1029 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:87839 (87.8 KB)  TX bytes:238740 (238.7 KB)

  Issue
  
  Unable to connect to any host via ssh or sftp after VPN connection 

  Tried 
  =

  Reinstalled the openssh-client package and still no luck. May I know
  why the default cipher is not taking/hanging? Please let me know .
  There were no recent changes.

  
  Workaround
  ===
  Able to connect to ssh / sftp $ssh -c aes128-ctr   user@IP

  
  Below is the debug ssh client logs ===
  ==

  $ssh -vvv  user@ip
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug2: resolving "IP" port 22
  debug2: ssh_connect_direct: needpriv 0
  debug1: Connecting to IP [IP] port 22.
  debug1: Connection established.
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_rsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 
Ubuntu-4ubuntu0.3
  debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400
  debug2: fd 3 setting O_NONBLOCK
  debug1: Authenticating to IP:22 as 'user'
  debug3: send packet: type 20
  debug1: SSH2_MSG_KEXINIT sent
  debug3: receive packet: type 20
  debug1: SSH2_MSG_KEXINIT received
  debug2: local client KEXINIT proposal
  debug2: KEX algorithms: 
curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c
  debug2: host key algorithms: 

[Touch-packages] [Bug 1874501] Re: vgscan --mknodes creates block device multipath nodes in /dev/mapper

[Michael Hudson-Doyle]

FWIW I reported this upstream at
https://bugzilla.redhat.com/show_bug.cgi?id=1828617, you might want to
attach the patch there too?

** Bug watch added: Red Hat Bugzilla #1828617
   https://bugzilla.redhat.com/show_bug.cgi?id=1828617

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

Title:
  vgscan --mknodes creates block device multipath nodes in /dev/mapper

Status in Ubuntu on IBM z Systems:
  New
Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 20.04 LTS
  Release:20.04

  # apt-cache policy multipath-tools
  multipath-tools:
Installed: 0.8.3-1ubuntu2
Candidate: 0.8.3-1ubuntu2
Version table:
   *** 0.8.3-1ubuntu2 500
  500 http://ports.ubuntu.com/ubuntu-ports focal/main s390x Packages
  100 /var/lib/dpkg/status

  
  /dev/mapper/mpatha is symlink which points to ../../dm-X device

  /dev/mapper/mpath is block device

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: multipath-tools 0.8.3-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: s390x
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  Date: Thu Apr 23 17:32:12 2020
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release s390x 
(20200423.1)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: multipath-tools
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.multipath.conf:
   defaults {
   user_friendly_names yes
   skip_kpartx no
   verbosity 4
   }
  mtime.conffile..etc.multipath.conf: 2020-04-23T15:47:28.659850

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

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

[Touch-packages] [Bug 1875699] Re: python3-venv missing ensurepip

[blueblob11]

Bug is perhaps the same as another one on bionic but is on focal fossa:

https://bugs.launchpad.net/ubuntu/+source/python3.8/+bug/1851684

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

Title:
  python3-venv missing ensurepip

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  I believe that I cannot even report this correctly because it appears
  the problem is in a package called python3-venv, however, launchpad
  tells me '"python3-venv" does not exist in Ubuntu.' despite it clearly
  being both installed and recommended by python itself.

  When trying to create a python3 virtual environment, I get errors
  about ensurepip missing, however I have installed python3-venv. The
  python3-venv package does not include ensurepip:

  python3.8 -mvenv .env
  The virtual environment was not created successfully because ensurepip is not
  available.  On Debian/Ubuntu systems, you need to install the python3-venv
  package using the following command.

  apt-get install python3-venv

  You may need to use sudo with that command.  After installing the python3-venv
  package, recreate your virtual environment.

  Failing command: ['/mnt/d/src/.env/bin/python3.8', '-Im', 'ensurepip',
  '--upgrade', '--default-pip']


  This is on Focal Fossa:
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  python3-venv:
Installed: 3.8.2-0ubuntu2
Candidate: 3.8.2-0ubuntu2
Version table:
   *** 3.8.2-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1875751] Re: Fractional scaling options do not appear in wayland session

[Matthew Holder]

** Attachment added: "Screenshot from 2020-04-28 21-28-05.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875751/+attachment/5362948/+files/Screenshot%20from%202020-04-28%2021-28-05.png

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

Title:
  Fractional scaling options do not appear in wayland session

Status in xorg package in Ubuntu:
  New

Bug description:
  When in a Wayland session, the options display the button to enable
  fractional scaling, but no options appear. Only 100% and 200% show

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 21:27:39 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 500 [8086:5a85] (rev 0b) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphics 500 [8086:2212]
  InstallationDate: Installed on 2020-04-23 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper Ezbook X3
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rz1ysp@/vmlinuz-5.4.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_rz1ysp ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Jumper10x.WP313P.1809100.NHNAUHL03
  dmi.board.asset.tag: Default string
  dmi.board.name: P313P
  dmi.board.vendor: Jumper
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.WP313P.1809100.NHNAUHL03:bd11/05/2019:svnJumper:pnEzbookX3:pvrDefaultstring:rvnJumper:rnP313P:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Ezbook
  dmi.product.name: Ezbook X3
  dmi.product.sku: 1809100
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1875751] Re: Fractional scaling options do not appear in wayland session

[Matthew Holder]

** Attachment added: "Screenshot from 2020-04-28 21-27-53.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875751/+attachment/5362947/+files/Screenshot%20from%202020-04-28%2021-27-53.png

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

Title:
  Fractional scaling options do not appear in wayland session

Status in xorg package in Ubuntu:
  New

Bug description:
  When in a Wayland session, the options display the button to enable
  fractional scaling, but no options appear. Only 100% and 200% show

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 21:27:39 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 500 [8086:5a85] (rev 0b) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphics 500 [8086:2212]
  InstallationDate: Installed on 2020-04-23 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper Ezbook X3
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rz1ysp@/vmlinuz-5.4.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_rz1ysp ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Jumper10x.WP313P.1809100.NHNAUHL03
  dmi.board.asset.tag: Default string
  dmi.board.name: P313P
  dmi.board.vendor: Jumper
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.WP313P.1809100.NHNAUHL03:bd11/05/2019:svnJumper:pnEzbookX3:pvrDefaultstring:rvnJumper:rnP313P:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Ezbook
  dmi.product.name: Ezbook X3
  dmi.product.sku: 1809100
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1875751] Re: Fractional scaling options do not appear in wayland session

[Matthew Holder]

Sorry for not filing this bug against wayland. The ubuntu-bug tool
wouldn't let me do so and I wanted to supply the logs it collects

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

Title:
  Fractional scaling options do not appear in wayland session

Status in xorg package in Ubuntu:
  New

Bug description:
  When in a Wayland session, the options display the button to enable
  fractional scaling, but no options appear. Only 100% and 200% show

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 21:27:39 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 500 [8086:5a85] (rev 0b) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphics 500 [8086:2212]
  InstallationDate: Installed on 2020-04-23 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper Ezbook X3
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rz1ysp@/vmlinuz-5.4.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_rz1ysp ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Jumper10x.WP313P.1809100.NHNAUHL03
  dmi.board.asset.tag: Default string
  dmi.board.name: P313P
  dmi.board.vendor: Jumper
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.WP313P.1809100.NHNAUHL03:bd11/05/2019:svnJumper:pnEzbookX3:pvrDefaultstring:rvnJumper:rnP313P:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Ezbook
  dmi.product.name: Ezbook X3
  dmi.product.sku: 1809100
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1875751] [NEW] Fractional scaling options do not appear in wayland session

[Matthew Holder]

Public bug reported:

When in a Wayland session, the options display the button to enable
fractional scaling, but no options appear. Only 100% and 200% show

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 28 21:27:39 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 500 [8086:5a85] (rev 0b) (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation HD Graphics 500 [8086:2212]
InstallationDate: Installed on 2020-04-23 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Jumper Ezbook X3
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rz1ysp@/vmlinuz-5.4.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_rz1ysp ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/05/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: Jumper10x.WP313P.1809100.NHNAUHL03
dmi.board.asset.tag: Default string
dmi.board.name: P313P
dmi.board.vendor: Jumper
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.WP313P.1809100.NHNAUHL03:bd11/05/2019:svnJumper:pnEzbookX3:pvrDefaultstring:rvnJumper:rnP313P:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
dmi.product.family: Ezbook
dmi.product.name: Ezbook X3
dmi.product.sku: 1809100
dmi.product.version: Default string
dmi.sys.vendor: Jumper
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu wayland-session

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

Title:
  Fractional scaling options do not appear in wayland session

Status in xorg package in Ubuntu:
  New

Bug description:
  When in a Wayland session, the options display the button to enable
  fractional scaling, but no options appear. Only 100% and 200% show

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 21:27:39 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 500 [8086:5a85] (rev 0b) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphics 500 [8086:2212]
  InstallationDate: Installed on 2020-04-23 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper Ezbook X3
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rz1ysp@/vmlinuz-5.4.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_rz1ysp ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 

[Touch-packages] [Bug 1874515] Re: 20.04 does not bring up certain bridges

[Mikael]

The difference between bridges managing to come up correctly and the
ones which does not seem to be that bridges defined as "inet manual"
fails and the ones defined as "inet static" succeeds. An example of a
bridge coming up correctly with a similar setup without the post-up
brctl addbr command;


auto int0.70
iface int0.70 inet manual
vlan-raw-device int0
pre-up ifconfig $IFACE up
post-down ifconfig $IFACE down

auto br_nat
iface br_nat inet static
bridge_ports int0.70
bridge_maxwait 5
address 172.X.X.X/24
up ip ro add 10.X.X.X/10 via 172.X.X.X dev $IFACE


So two conclusions;

1) Bridges configured with bridge_ports with interfaces defined as "inet
manual" while the bridge is also configured as "inet manual" will fail
to come up correctly.

2) If a bridge fails to come up with the inet manual directive the
dhclient for br_ext_prim also dies after receiving one lease.


Reservation on #1 that this could probably also be true with an "inet static" 
interface for a bridge configured as "inet manual". 


Both of the above works 100% fine in 18.04.

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

Title:
  20.04 does not bring up certain bridges

Status in ifupdown package in Ubuntu:
  New

Bug description:
  After upgrading from a fully patched ubuntu-server 18.04 to 20.04 and
  rebooting I noticed that some of my bridge interfaces defined in
  /etc/network/interfaces would not come up while others would.

  Bridges brought up at boot:

  br_ext_prim
  br_ext_sec
  br_int_50
  br_nat

  Bridges missing:

  br_int_500
  br_nat_ext

  
  Relevant log from 18.04 prior to upgrade:

  Apr 23 19:11:37 fancy systemd-udevd[725]: Could not generate persistent MAC 
address for br_nat_ext: No such file or directory
  Apr 23 19:11:37 fancy systemd[1]: Found device 
/sys/subsystem/net/devices/br_nat_ext.
  Apr 23 19:11:37 fancy systemd[1]: Started ifup for br_nat_ext.
  Apr 23 19:11:37 fancy systemd-networkd[2284]: br_nat_ext: Link UP
  Apr 23 19:11:37 fancy sh[2383]: Waiting for br_nat_ext to get ready (MAXWAIT 
is 5 seconds).
  Apr 23 19:11:37 fancy kernel: [9.447538] br_nat_ext: port 1(int0.51) 
entered blocking state
  Apr 23 19:11:37 fancy kernel: [9.447540] br_nat_ext: port 1(int0.51) 
entered disabled state
  Apr 23 19:11:37 fancy systemd-networkd[2284]: br_nat_ext: Gained carrier
  Apr 23 19:11:37 fancy kernel: [   10.942682] br_nat_ext: port 1(int0.51) 
entered blocking state
  Apr 23 19:11:37 fancy kernel: [   10.942683] br_nat_ext: port 1(int0.51) 
entered forwarding state
  Apr 23 19:11:37 fancy kernel: [   10.943270] IPv6: ADDRCONF(NETDEV_CHANGE): 
br_nat_ext: link becomes ready
  Apr 23 19:11:39 fancy systemd-networkd[2284]: br_nat_ext: Gained IPv6LL

  
  Relevant log from 20.04 after upgrade:

  Apr 23 19:39:52 fancy ifup[1845]: br_nat_ext: ERROR while getting interface 
flags: No such device
  Apr 23 19:39:52 fancy ifup[1066]: ifup: failed to bring up br_nat_ext
  Apr 23 19:40:04 fancy libvirtd[1935]: Cannot get interface MTU on 
'br_nat_ext': No such device
  Apr 23 19:40:04 fancy libvirtd[1935]: internal error: Failed to autostart VM 
'dns': Cannot get interface MTU on 'br_nat_ext': No such device
  Apr 23 19:43:43 fancy libvirtd[1935]: Cannot get interface MTU on 
'br_nat_ext': No such device
  Apr 23 19:39:52 fancy systemd[1]: networking.service: Main process exited, 
code=exited, status=1/FAILURE
  Apr 23 19:39:52 fancy systemd[1]: networking.service: Failed with result 
'exit-code'.
  Apr 23 19:39:52 fancy systemd[1]: Failed to start Raise network interfaces.

  
  Similar logs show up for br_int_500.

  
  Some examples of entries of /etc/network/interfaces:

  Not working:

  # NAT via main FW
  auto int0.51
  iface int0.51 inet manual
 vlan-raw-device int0
 pre-up ifconfig $IFACE up
 post-down ifconfig $IFACE down

  auto br_nat_ext
  iface br_nat_ext inet manual
  bridge_ports int0.51
  bridge_maxwait 5
  pre-up ifconfig $IFACE up
  post-down ifconfig $IFACE down

  
  Working:

  # 1GE
  auto ext0.10
  iface ext0.10 inet manual
  vlan-raw-device ext0
  pre-up ifconfig $IFACE up
  post-down ifconfig $IFACE down

  # Secondary bridge 1GE
  auto br_ext_sec
  iface br_ext_sec inet manual
  bridge_ports ext0.10
  bridge_maxwait 5
  post-up ifconfig $IFACE up
  post-down ifconfig $IFACE down

  
  Output from syslog in regards to br_ext_sec after upgrade:

  Apr 23 19:39:52 fancy systemd-udevd[1366]: br_ext_sec: Could not generate 
persistent MAC: No data available
  Apr 23 19:39:52 fancy kernel: [   24.353151] br_ext_sec: port 1(ext0.10) 
entered blocking state
  Apr 23 19:39:52 fancy kernel: [   24.353156] br_ext_sec: port 1(ext0.10) 
entered disabled state
  Apr 23 19:39:52 fancy 

[Touch-packages] [Bug 1874515] Re: 20.04 does not bring up certain bridges

[Mikael]

Modifying /etc/network/interfaces to include the following post-up
completed networking startup successfully;

auto int0.51
iface int0.51 inet manual
vlan-raw-device int0
pre-up ifconfig $IFACE up
post-up brctl addbr br_nat_ext
post-down ifconfig $IFACE down

auto br_nat_ext
iface br_nat_ext inet manual
bridge_ports int0.51
bridge_maxwait 5
pre-up ifconfig $IFACE up
post-down ifconfig $IFACE down


auto int0.500
iface int0.500 inet manual
vlan-raw-device int0
pre-up ifconfig $IFACE up
post-up brctl addbr br_int_500
post-down ifconfig $IFACE down

auto br_int_500
iface br_int_500 inet manual
bridge_ports int0.500
bridge_maxwait 5
pre-up ifconfig $IFACE up
post-down ifconfig $IFACE down



Interestingly enough the dhclient also survived (see previous update) when 
networking completed successfully;


root@fancy:/data# ps auxf | grep -i dhclient
root1264  0.0  0.0  99896  5700 ?Ssl  21:59   0:00 
/sbin/dhclient -1 -4 -v -i -pf /run/dhclient.br_ext_prim.pid -lf 
/var/lib/dhcp/dhclient.br_ext_prim.leases -I -df 
/var/lib/dhcp/dhclient6.br_ext_prim.leases br_ext_prim


Both prior boots to this one had no running dhclient after the bridges failed 
to come up. 

This should imho be unrelated.

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

Title:
  20.04 does not bring up certain bridges

Status in ifupdown package in Ubuntu:
  New

Bug description:
  After upgrading from a fully patched ubuntu-server 18.04 to 20.04 and
  rebooting I noticed that some of my bridge interfaces defined in
  /etc/network/interfaces would not come up while others would.

  Bridges brought up at boot:

  br_ext_prim
  br_ext_sec
  br_int_50
  br_nat

  Bridges missing:

  br_int_500
  br_nat_ext

  
  Relevant log from 18.04 prior to upgrade:

  Apr 23 19:11:37 fancy systemd-udevd[725]: Could not generate persistent MAC 
address for br_nat_ext: No such file or directory
  Apr 23 19:11:37 fancy systemd[1]: Found device 
/sys/subsystem/net/devices/br_nat_ext.
  Apr 23 19:11:37 fancy systemd[1]: Started ifup for br_nat_ext.
  Apr 23 19:11:37 fancy systemd-networkd[2284]: br_nat_ext: Link UP
  Apr 23 19:11:37 fancy sh[2383]: Waiting for br_nat_ext to get ready (MAXWAIT 
is 5 seconds).
  Apr 23 19:11:37 fancy kernel: [9.447538] br_nat_ext: port 1(int0.51) 
entered blocking state
  Apr 23 19:11:37 fancy kernel: [9.447540] br_nat_ext: port 1(int0.51) 
entered disabled state
  Apr 23 19:11:37 fancy systemd-networkd[2284]: br_nat_ext: Gained carrier
  Apr 23 19:11:37 fancy kernel: [   10.942682] br_nat_ext: port 1(int0.51) 
entered blocking state
  Apr 23 19:11:37 fancy kernel: [   10.942683] br_nat_ext: port 1(int0.51) 
entered forwarding state
  Apr 23 19:11:37 fancy kernel: [   10.943270] IPv6: ADDRCONF(NETDEV_CHANGE): 
br_nat_ext: link becomes ready
  Apr 23 19:11:39 fancy systemd-networkd[2284]: br_nat_ext: Gained IPv6LL

  
  Relevant log from 20.04 after upgrade:

  Apr 23 19:39:52 fancy ifup[1845]: br_nat_ext: ERROR while getting interface 
flags: No such device
  Apr 23 19:39:52 fancy ifup[1066]: ifup: failed to bring up br_nat_ext
  Apr 23 19:40:04 fancy libvirtd[1935]: Cannot get interface MTU on 
'br_nat_ext': No such device
  Apr 23 19:40:04 fancy libvirtd[1935]: internal error: Failed to autostart VM 
'dns': Cannot get interface MTU on 'br_nat_ext': No such device
  Apr 23 19:43:43 fancy libvirtd[1935]: Cannot get interface MTU on 
'br_nat_ext': No such device
  Apr 23 19:39:52 fancy systemd[1]: networking.service: Main process exited, 
code=exited, status=1/FAILURE
  Apr 23 19:39:52 fancy systemd[1]: networking.service: Failed with result 
'exit-code'.
  Apr 23 19:39:52 fancy systemd[1]: Failed to start Raise network interfaces.

  
  Similar logs show up for br_int_500.

  
  Some examples of entries of /etc/network/interfaces:

  Not working:

  # NAT via main FW
  auto int0.51
  iface int0.51 inet manual
 vlan-raw-device int0
 pre-up ifconfig $IFACE up
 post-down ifconfig $IFACE down

  auto br_nat_ext
  iface br_nat_ext inet manual
  bridge_ports int0.51
  bridge_maxwait 5
  pre-up ifconfig $IFACE up
  post-down ifconfig $IFACE down

  
  Working:

  # 1GE
  auto ext0.10
  iface ext0.10 inet manual
  vlan-raw-device ext0
  pre-up ifconfig $IFACE up
  post-down ifconfig $IFACE down

  # Secondary bridge 1GE
  auto br_ext_sec
  iface br_ext_sec inet manual
  bridge_ports ext0.10
  bridge_maxwait 5
  post-up ifconfig $IFACE up
  post-down ifconfig $IFACE down

  
  Output from syslog in regards to br_ext_sec after upgrade:

  Apr 23 19:39:52 fancy systemd-udevd[1366]: br_ext_sec: Could not generate 
persistent MAC: No data available
  Apr 

[Touch-packages] [Bug 1875745] Re: Waffle button on dock doesn't do anything in wayland session

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:

  apport-collect 1875745

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.

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

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

** Changed in: gnome-shell (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/1875745

Title:
  Waffle button on dock doesn't do anything in wayland session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When using the waffle button menu on the dock when in a wayland
  session nothing happens

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 21:14:31 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 500 [8086:5a85] (rev 0b) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphics 500 [8086:2212]
  InstallationDate: Installed on 2020-04-23 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper Ezbook X3
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rz1ysp@/vmlinuz-5.4.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_rz1ysp ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Jumper10x.WP313P.1809100.NHNAUHL03
  dmi.board.asset.tag: Default string
  dmi.board.name: P313P
  dmi.board.vendor: Jumper
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.WP313P.1809100.NHNAUHL03:bd11/05/2019:svnJumper:pnEzbookX3:pvrDefaultstring:rvnJumper:rnP313P:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Ezbook
  dmi.product.name: Ezbook X3
  dmi.product.sku: 1809100
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1875628] Re: getting white and purple blocks on top of some texts

[Pratiksha Sahu]

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

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

Title:
  getting white and purple blocks on top of some texts

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Everytime I start Ubuntu, I get gren blocks all of the home screen,
  which is solved by changing the wallpaper. But I also get white &
  purple blocks over texts like my wifi name, "Night Light On" and Time
  on the top bar (see attached photo). This is not solved.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 17:01:19 2020
  DistUpgraded: 2020-04-25 20:54:39,691 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-46-generic, x86_64: installed
   nvidia, 435.21, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fc]
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TU117M [GeForce GTX 1650 Mobile / 
Max-Q] [103c:85fc]
  InstallationDate: Installed on 2019-08-26 (245 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b627 Chicony Electronics Co., Ltd HP Wide Vision 
HD Camera
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=e82ecf26-25d1-4191-8a15-74a3ab24420c ro acpi_backlight=vendor
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-25 (2 days ago)
  dmi.bios.date: 11/22/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.20
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 85FC
  dmi.board.vendor: HP
  dmi.board.version: 42.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.20:bd11/22/2019:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FC:rvr42.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx
  dmi.product.sku: 7LG86PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1874501] Re: vgscan --mknodes creates block device multipath nodes in /dev/mapper

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  vgscan --mknodes creates block device multipath nodes in /dev/mapper

Status in Ubuntu on IBM z Systems:
  New
Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 20.04 LTS
  Release:20.04

  # apt-cache policy multipath-tools
  multipath-tools:
Installed: 0.8.3-1ubuntu2
Candidate: 0.8.3-1ubuntu2
Version table:
   *** 0.8.3-1ubuntu2 500
  500 http://ports.ubuntu.com/ubuntu-ports focal/main s390x Packages
  100 /var/lib/dpkg/status

  
  /dev/mapper/mpatha is symlink which points to ../../dm-X device

  /dev/mapper/mpath is block device

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: multipath-tools 0.8.3-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: s390x
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  Date: Thu Apr 23 17:32:12 2020
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release s390x 
(20200423.1)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: multipath-tools
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.multipath.conf:
   defaults {
   user_friendly_names yes
   skip_kpartx no
   verbosity 4
   }
  mtime.conffile..etc.multipath.conf: 2020-04-23T15:47:28.659850

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

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

[Touch-packages] [Bug 1874915] Re: krb5kdc[27833]: Couldn't open log file /var/log/krb5kdc.log: Read-only file system

[Lucas Kanashiro]

I agree with Sam and Andreas, we should not change the krb5kdc systemd
unit file because of freeipa. I am assigning this bug back to freeipa.

** Package changed: krb5 (Ubuntu) => freeipa (Ubuntu)

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

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

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

Title:
  krb5kdc[27833]: Couldn't open log file /var/log/krb5kdc.log: Read-only
  file system

Status in freeipa package in Ubuntu:
  Triaged

Bug description:
  Hopefully this can trivially be corrected.

  Seems the systemd service file for the kerberos portion of freeipa
  could use a minor tweak.

  When restarting the kerberos service, it (incorrectly) reports that
  the default configured log file (/var/log/krb5kdc.log) is sending to a
  "read only filesystem".  This is a misleading error, since the
  /var/log directory by default -IS- writeable, but systemd is in fact
  preventing the daemon from writing.  Why systemd can't inject itself
  inappropriately and report that it's causing the trouble is another
  conversation. ;) [not personally a systemd fan]

  
  File:
  =
  /lib/systemd/system/krb5-kdc.service

  Command:
  =
  service krb5-kdc restart

  Error:
  =
  krb5kdc[27833]: Couldn't open log file /var/log/krb5kdc.log: Read-only file 
system

  
  Please make the following adjustment to the default systemd file.
  =
  13c13
  < ReadWriteDirectories=-/var/tmp /tmp /var/lib/krb5kdc -/var/run /run
  ---
  > ReadWriteDirectories=-/var/tmp /tmp /var/lib/krb5kdc -/var/run /run /var/log


  Thank you for all the help and support.  :)

  Cheers,
  -Chris

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

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

[Touch-packages] [Bug 1875745] [NEW] Waffle button on dock doesn't do anything in wayland session

[Matthew Holder]

Public bug reported:

When using the waffle button menu on the dock when in a wayland session
nothing happens

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 28 21:14:31 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 500 [8086:5a85] (rev 0b) (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation HD Graphics 500 [8086:2212]
InstallationDate: Installed on 2020-04-23 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Jumper Ezbook X3
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rz1ysp@/vmlinuz-5.4.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_rz1ysp ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/05/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: Jumper10x.WP313P.1809100.NHNAUHL03
dmi.board.asset.tag: Default string
dmi.board.name: P313P
dmi.board.vendor: Jumper
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.WP313P.1809100.NHNAUHL03:bd11/05/2019:svnJumper:pnEzbookX3:pvrDefaultstring:rvnJumper:rnP313P:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
dmi.product.family: Ezbook
dmi.product.name: Ezbook X3
dmi.product.sku: 1809100
dmi.product.version: Default string
dmi.sys.vendor: Jumper
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu wayland-session

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

Title:
  Waffle button on dock doesn't do anything in wayland session

Status in xorg package in Ubuntu:
  New

Bug description:
  When using the waffle button menu on the dock when in a wayland
  session nothing happens

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 21:14:31 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 500 [8086:5a85] (rev 0b) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphics 500 [8086:2212]
  InstallationDate: Installed on 2020-04-23 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper Ezbook X3
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rz1ysp@/vmlinuz-5.4.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_rz1ysp ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 

[Touch-packages] [Bug 1875714] Re: No sound from headphones

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  No sound from headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi,

  I upgraded to focal and since then I have the following problems with
  my audio on my laptop:

  1. If I start my laptop with my headphones pluged-in I initially have
  sound from my headphones, If I unplug my headphones speakers work
  normally. But when insert my headphone again the sound stops from the
  speakers but I have no sound from my headphones. To "fix" the problem
  I have to go to the kde systemsettings and in "audio" settings in the
  advanced tab change the profile to something else and then restore the
  option.

  If I start the laptop WITHOUT the headphones pluged-in then everything
  works as it should. I have deleted the ~./config/pulse folder but it
  changes nothing.

  2. If the computer starts WITHOUT headphones and the computer goes
  into hibernation when it wakes I get a static noise from the speakers
  (although the headphones are plugined-in) I have to reboot the
  computer in order to fix this.

  Kind Regards

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Apr 28 21:37:41 2020
  InstallationDate: Installed on 2018-11-22 (523 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to focal on 2020-04-26 (1 days ago)

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

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

[Touch-packages] [Bug 1875742] [NEW] Screen tearing shows when resizing windows

[Matthew Holder]

Public bug reported:

When resizing terminator (terminal emulator) and the file browser the
contents of the window disappears and I see various different
corruption. Some horizontal lines and some that looks like old fashioned
static on the TV

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 28 21:07:42 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 500 [8086:5a85] (rev 0b) (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation HD Graphics 500 [8086:2212]
InstallationDate: Installed on 2020-04-23 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Jumper Ezbook X3
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rz1ysp@/vmlinuz-5.4.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_rz1ysp ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/05/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: Jumper10x.WP313P.1809100.NHNAUHL03
dmi.board.asset.tag: Default string
dmi.board.name: P313P
dmi.board.vendor: Jumper
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.WP313P.1809100.NHNAUHL03:bd11/05/2019:svnJumper:pnEzbookX3:pvrDefaultstring:rvnJumper:rnP313P:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
dmi.product.family: Ezbook
dmi.product.name: Ezbook X3
dmi.product.sku: 1809100
dmi.product.version: Default string
dmi.sys.vendor: Jumper
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption 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/1875742

Title:
  Screen tearing shows when resizing windows

Status in xorg package in Ubuntu:
  New

Bug description:
  When resizing terminator (terminal emulator) and the file browser the
  contents of the window disappears and I see various different
  corruption. Some horizontal lines and some that looks like old
  fashioned static on the TV

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 21:07:42 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 500 [8086:5a85] (rev 0b) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphics 500 [8086:2212]
  InstallationDate: Installed on 2020-04-23 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Jumper Ezbook X3
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rz1ysp@/vmlinuz-5.4.0-26-generic 

[Touch-packages] [Bug 1875714] [NEW] No sound from headphones

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hi,

I upgraded to focal and since then I have the following problems with my
audio on my laptop:

1. If I start my laptop with my headphones pluged-in I initially have
sound from my headphones, If I unplug my headphones speakers work
normally. But when insert my headphone again the sound stops from the
speakers but I have no sound from my headphones. To "fix" the problem I
have to go to the kde systemsettings and in "audio" settings in the
advanced tab change the profile to something else and then restore the
option.

If I start the laptop WITHOUT the headphones pluged-in then everything
works as it should. I have deleted the ~./config/pulse folder but it
changes nothing.

2. If the computer starts WITHOUT headphones and the computer goes into
hibernation when it wakes I get a static noise from the speakers
(although the headphones are plugined-in) I have to reboot the computer
in order to fix this.

Kind Regards

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base (not installed)
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Tue Apr 28 21:37:41 2020
InstallationDate: Installed on 2018-11-22 (523 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
SourcePackage: alsa-driver
UpgradeStatus: Upgraded to focal on 2020-04-26 (1 days ago)

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


** Tags: amd64 apport-bug focal
-- 
No sound from headphones
https://bugs.launchpad.net/bugs/1875714
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver in Ubuntu.

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

[Touch-packages] [Bug 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red

[Tim Hockin]

I just filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712
which feels like it might be similar?

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

Title:
  [nouveau, GeForce 7300 LE] screen background overlaid with scan type
  artifact in red

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  My desktop has both it's usual items in place; toolbar on left and
  desktop icons distributed around the screen. Then there's what appears
  to be a bunch of scan line, raster line artifacts, in red, laid over
  my normal background, which is a star field photo on what is
  ordinarily a black field.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 21 13:04:20 2020
  DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405]
  InstallationDate: Installed on 2016-08-19 (1249 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 531
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago)
  dmi.bios.date: 11/09/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0RY206
  dmi.board.vendor: Dell Inc.
  dmi.board.version: ���
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion:
  dmi.product.name: Inspiron 531
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct  3 10:41:28 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard KEYBOARD, id 8
   inputLogitech USB Trackball MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1875737] [NEW] Stdin overrun with dots when ubuntu-bug is run as non-superuser

[PlantDaddy]

Public bug reported:

$ lsb_release -rd
Description:Ubuntu 19.10
Release:19.10

2.20.11-0ubuntu8.8

When ubuntu-bug is run without sudo or without being logged in as a
superuser, ubuntu-bug prompts for your accounts password to execute its
functionality as a superuser to gathered required debugging information.
However, when input of the password is request of the user, the stdin
line is ovverrun with dots that appear to be also entered into stdin, as
the password authentication will always fail.

stdin for users password shouldnt be ovverrun by dots produced by
ubuntu-bug. I tried this numerous times to make sure it wasn't repeated
typos, but it appears to be a bug.

~$ ubuntu-bug update-manager-core

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
...
*** Is the issue you are reporting one you encountered when upgrading Ubuntu 
from one release to another?


What would you like to do? Your options are:
  Y: Yes
  N: No
  C: Cancel
Please choose (Y/N/C): Y

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.. AUTHENTICATING FOR org.freedesktop.policykit.exec ===
Authentication is needed to run `/bin/cat' as the super user
Authenticating as: lost,,, (lost)
Password: 
 AUTHENTICATION FAILED ===
 AUTHENTICATING FOR com.ubuntu.apport.root-info ===
Authentication is required to collect system information for this problem report
Authenticating as: lost,,, (lost)
Password: .
...polkit-agent-helper-1: pam_authenticate failed: Authentication failure
 AUTHENTICATION FAILED ===
Error executing command as another user: Not authorized

This incident has been reported.
..

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (2.4 MB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): ^C

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: apport 2.20.11-0ubuntu8.8
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportLog:
 
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
CrashReports: 640:0:0:49490:2020-04-28 14:14:46.039684173 -0500:2020-04-28 
13:40:57.606173803 -0500:/var/crash/_usr_bin_do-release-upgrade.0.crash
Date: Tue Apr 28 14:31:42 2020
InstallationDate: Installed on 2019-02-19 (434 days ago)
InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: Upgraded to eoan on 2020-04-28 (0 days ago)

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


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

** Summary changed:

- Dots overrun stdin with dots when ubuntu-bug is run as non-superuser
+ Stdin overrun with dots when ubuntu-bug is run as non-superuser

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

Title:
  Stdin overrun with dots when ubuntu-bug is run as non-superuser

Status in apport package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  2.20.11-0ubuntu8.8

  When ubuntu-bug is run without sudo or without being logged in as a
  superuser, ubuntu-bug prompts for your accounts password to execute
  its functionality as a superuser to gathered required debugging
  information. However, when input of the password is request of the
  user, the stdin line is ovverrun with dots that appear to be also
  entered into stdin, as the password authentication will always fail.

  stdin for users password shouldnt be ovverrun by dots produced by
  ubuntu-bug. I tried this numerous times to make sure it wasn't
  repeated typos, but it appears to be a bug.

  ~$ ubuntu-bug update-manager-core

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ...
  *** Is the issue you are reporting one you encountered when upgrading Ubuntu 
from one release to another?

  
  What would you like to do? Your options are:
Y: Yes
N: No
C: Cancel
  Please choose (Y/N/C): Y

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR 

[Touch-packages] [Bug 1875369] Re: recording device won't change

[gregrwm]

hello, thank you, ok did that.  a new and populated .config/pulse was
created upon logout.  bug still present as described.

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

Title:
  recording device won't change

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  installed from lubuntu .iso
  fully updated as of yesterday
  fresh boot this morning

  some of these details are most likely irrelevant, but it's what i do to keep 
things simple:
  ignore graphical login screen, change to VT2
  startx /usr/bin/xterm

  in the xterm:
  /opt/firefox/firefox&  #(nightly)
  openbox&
  pavucontrol-qt&
  pavucontrol&#results are the same regardless which of the pavucontrols is 
invoked

  in firefox:
  voice.google.com
  start a call

  in either of the pavucontrols:
  try to change the recording device:
  the menu opens, select the desired device, but it just doesn't change.
  doesn't matter which of the two pavucontrols was invoked

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Apr 27 07:49:12 2020
  InstallationDate: Installed on 2020-03-15 (42 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314)
  ProcEnviron:
   LC_TIME=en_DK.utf8
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/20/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ETA2WW (2.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C6008SUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C6008SUS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6008SUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Edge E540
  dmi.product.name: 20C6008SUS
  dmi.product.sku: LENOVO_MT_20C6_BU_Think_FM_ThinkPad Edge E540
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1848862] Re: HP Elitebook 840 G1 - 19.10 - Microphone mute key does not work

[Simple Machine]

While this is a bug. It is also a question on how to implement the
potential fix identified.

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

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/systemd/+question/690306

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

Title:
  HP Elitebook 840 G1 - 19.10 - Microphone mute key does not work

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I just installed Ubuntu 19.10 on my HP Elitebook 840 G1. Switching
  from Windows to Ubuntu for personal use.

  The mic does not enable/disable with FN+F8 combo and the light is
  constantly on.

  I found the following solution to my problem. However, I do not know how to 
implement it in Ubuntu 19.10 (new to Ubuntu and generally not as techinical).
  
https://wiki.archlinux.org/index.php/HP_EliteBook_840_G1#Enable_the_microphone_muting_key

  1. Would greatly appreciate if someone could point me to step by step 
instructions to install the code from the link above. I can report back if this 
resolve the issue.
  2. Also, is there a way to incorporate a fix for this issue with HP laptops 
in Ubuntu going forward? When I was searching for a fix, I found this to be a 
widespread issue with various HP laptops and Ubuntu dating back a couple years.

  Many thanks.

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

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

[Touch-packages] [Bug 1848862] Re: HP Elitebook 840 G1 - 19.10 - Microphone mute key does not work

[Simple Machine]

Forgot to mention that when I run "sudo showkey -s" in terminal to test
the output for the Fn+F8 combination I do not see any output.

Other key press combinations show outputs. For example pressing Fn+F7
shows "0xe0 0x30 0xe0 0xb0"

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

Title:
  HP Elitebook 840 G1 - 19.10 - Microphone mute key does not work

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I just installed Ubuntu 19.10 on my HP Elitebook 840 G1. Switching
  from Windows to Ubuntu for personal use.

  The mic does not enable/disable with FN+F8 combo and the light is
  constantly on.

  I found the following solution to my problem. However, I do not know how to 
implement it in Ubuntu 19.10 (new to Ubuntu and generally not as techinical).
  
https://wiki.archlinux.org/index.php/HP_EliteBook_840_G1#Enable_the_microphone_muting_key

  1. Would greatly appreciate if someone could point me to step by step 
instructions to install the code from the link above. I can report back if this 
resolve the issue.
  2. Also, is there a way to incorporate a fix for this issue with HP laptops 
in Ubuntu going forward? When I was searching for a fix, I found this to be a 
widespread issue with various HP laptops and Ubuntu dating back a couple years.

  Many thanks.

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

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

[Touch-packages] [Bug 1848862] Re: HP Elitebook 840 G1 - 19.10 - Microphone mute key does not work

[Simple Machine]

@rbalint I updated the laptop to Ubuntu 20.04. The mic still does not 
enable/disable with FN+F8 combo and the light is constantly on. I haven't been 
able to implement in the following link (due to lack of technical know how):
https://wiki.archlinux.org/index.php/HP_EliteBook_840_G1#Enable_the_microphone_muting_key

However, the auto screen rotation issue appears to have been fixed in 20.04 as 
detailed in the link you posted.
https://github.com/systemd/systemd/issues/13463

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

Title:
  HP Elitebook 840 G1 - 19.10 - Microphone mute key does not work

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I just installed Ubuntu 19.10 on my HP Elitebook 840 G1. Switching
  from Windows to Ubuntu for personal use.

  The mic does not enable/disable with FN+F8 combo and the light is
  constantly on.

  I found the following solution to my problem. However, I do not know how to 
implement it in Ubuntu 19.10 (new to Ubuntu and generally not as techinical).
  
https://wiki.archlinux.org/index.php/HP_EliteBook_840_G1#Enable_the_microphone_muting_key

  1. Would greatly appreciate if someone could point me to step by step 
instructions to install the code from the link above. I can report back if this 
resolve the issue.
  2. Also, is there a way to incorporate a fix for this issue with HP laptops 
in Ubuntu going forward? When I was searching for a fix, I found this to be a 
widespread issue with various HP laptops and Ubuntu dating back a couple years.

  Many thanks.

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

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

[Touch-packages] [Bug 1875730] [NEW] Ubuntu 19.10+ screen corruption

[Antoine Brunner]

Public bug reported:

Last week-end, after restarting my T470s running Ubuntu 19.10, I
experienced a lot of visual glitches that didn't occur before. However,
I had already noticed that some applications were unexpectedly freezing
for about 5-10 seconds.

I have already tried reinstalling xorg, without success. Then, I tried
running Ubuntu 20.04 from a USB stick, and the problem doesn't occur.
Today, I have upgraded Ubuntu to version 20.04 to see if it would fix
it, but without success again.

Note that when I restart the display server (Alt-F2 -> r -> Enter), it
fixes the problem (sometimes I have to restart it several times).

I would be happy to give you more information if you need.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 28 21:06:33 2020
DistUpgraded: 2020-04-28 18:36:07,244 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.6, 5.3.0-46-generic, x86_64: installed
 virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed
 virtualbox-guest, 6.1.6, 5.3.0-46-generic, x86_64: installed
 virtualbox-guest, 6.1.6, 5.4.0-26-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 620 [17aa:224b]
InstallationDate: Installed on 2019-09-19 (221 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20HGS14X00
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=66402066-cedd-46a8-ba1a-67104f3abff7 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-28 (0 days ago)
dmi.bios.date: 02/27/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N1WET58W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HGS14X00
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: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET58W(1.37):bd02/27/2020:svnLENOVO:pn20HGS14X00:pvrThinkPadT470s:rvnLENOVO:rn20HGS14X00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470s
dmi.product.name: 20HGS14X00
dmi.product.sku: LENOVO_MT_20HG_BU_Think_FM_ThinkPad T470s
dmi.product.version: ThinkPad T470s
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.101+git2004261830.fd7f37~oibaf~e
version.libgl1-mesa-dri: libgl1-mesa-dri 20.1~git2004280730.b4cc11~oibaf~e
version.libgl1-mesa-glx: libgl1-mesa-glx 20.1~git2004280730.b4cc11~oibaf~e
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption focal ubuntu

** Attachment added: "This is one (but not the only one unfortunately) of the 
visual glitches that I am experiencing"
   
https://bugs.launchpad.net/bugs/1875730/+attachment/5362790/+files/screenshot3.png

** Description changed:

  Last week-end, after restarting my T470s running Ubuntu 19.10, I
  experienced a lot of visual glitches that didn't occur before. However,
  I had already noticed that some applications were unexpectedly freezing
  for about 5-10 seconds.
  
  I have already tried reinstalling xorg, without success. Then, I tried
  running Ubuntu 20.04 from a USB stick, and the problem doesn't occur.
  Today, I have upgraded Ubuntu to version 20.04 to see if it would fix
  it, but without success again.
+ 
+ Note that when I restart the display server (Alt-F2 -> r -> Enter), it
+ fixes the problem (sometimes I have to restart it several times).
  
  I would be happy to give you more information if you need.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  

[Touch-packages] [Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)

[Tim Hockin]

** Attachment added: "photo of screens"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712/+attachment/5362778/+files/IMG_20200428_104657.jpg

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

Title:
  Unusable graphics, nouveau + G73 (GEForce 7600)

Status in xorg package in Ubuntu:
  New

Bug description:
  This is an older card, but it worked well on ubuntu 12.x :)

  Booting "Try Ubuntu" on 20.04 get the correct resolution and 2
  displays, but the video glitches and shows all sorts of noise.  It is
  largely unusable (which makes filing this bug very hard).

  Safe Graphics works in low-res.

  The nvidia proprietary driver seems to not support this device any
  more.  I like this card because it has no fan (and I don't do a lot of
  graphics-intense stuff).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 18:13:48 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd G73 [GeForce 7600 GT] [1458:3417]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd  
---  priority=low
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: X58 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd12/30/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme6: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.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1875684] Re: Can't connect to Pulseaudio after user change on Lubuntu 20.04

[Brian Murray]

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

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

Title:
  Can't connect to Pulseaudio after user change on Lubuntu 20.04

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On fresh install of Lubuntu 20.04:
  - First login after Computer startup, no sound problem.
  - User Account logout and login to another account => Very often, the sound 
is off (with a prohibited sign instead of the speaker in the dashboard).
  And the status of Pulse audio is "connecting" when I call pavucontrol.

  The way to get the sound again is to lauch pulseaudio in a terminal or
  to reboot the computer.

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

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

[Touch-packages] [Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)

[Tim Hockin]

** Attachment added: "photo of screens"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712/+attachment/5362777/+files/IMG_20200428_104633.jpg

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

Title:
  Unusable graphics, nouveau + G73 (GEForce 7600)

Status in xorg package in Ubuntu:
  New

Bug description:
  This is an older card, but it worked well on ubuntu 12.x :)

  Booting "Try Ubuntu" on 20.04 get the correct resolution and 2
  displays, but the video glitches and shows all sorts of noise.  It is
  largely unusable (which makes filing this bug very hard).

  Safe Graphics works in low-res.

  The nvidia proprietary driver seems to not support this device any
  more.  I like this card because it has no fan (and I don't do a lot of
  graphics-intense stuff).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 18:13:48 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd G73 [GeForce 7600 GT] [1458:3417]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd  
---  priority=low
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: X58 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd12/30/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme6: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.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)

[Tim Hockin]

** Attachment added: "photo of screens"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712/+attachment/5362776/+files/IMG_20200428_105019.jpg

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

Title:
  Unusable graphics, nouveau + G73 (GEForce 7600)

Status in xorg package in Ubuntu:
  New

Bug description:
  This is an older card, but it worked well on ubuntu 12.x :)

  Booting "Try Ubuntu" on 20.04 get the correct resolution and 2
  displays, but the video glitches and shows all sorts of noise.  It is
  largely unusable (which makes filing this bug very hard).

  Safe Graphics works in low-res.

  The nvidia proprietary driver seems to not support this device any
  more.  I like this card because it has no fan (and I don't do a lot of
  graphics-intense stuff).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 18:13:48 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd G73 [GeForce 7600 GT] [1458:3417]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd  
---  priority=low
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: X58 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd12/30/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme6: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.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)

[Tim Hockin]

** Attachment added: "photo of screens"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712/+attachment/5362775/+files/IMG_20200428_111516.jpg

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

Title:
  Unusable graphics, nouveau + G73 (GEForce 7600)

Status in xorg package in Ubuntu:
  New

Bug description:
  This is an older card, but it worked well on ubuntu 12.x :)

  Booting "Try Ubuntu" on 20.04 get the correct resolution and 2
  displays, but the video glitches and shows all sorts of noise.  It is
  largely unusable (which makes filing this bug very hard).

  Safe Graphics works in low-res.

  The nvidia proprietary driver seems to not support this device any
  more.  I like this card because it has no fan (and I don't do a lot of
  graphics-intense stuff).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 18:13:48 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd G73 [GeForce 7600 GT] [1458:3417]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd  
---  priority=low
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: X58 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd12/30/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme6: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.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)

[Tim Hockin]

Note: the corruption is not changing unless I move windows around.
Moving the mouse alone draws the pointer corrctly.

** Attachment added: "photo of screens"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712/+attachment/5362774/+files/IMG_20200428_084746.jpg

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

Title:
  Unusable graphics, nouveau + G73 (GEForce 7600)

Status in xorg package in Ubuntu:
  New

Bug description:
  This is an older card, but it worked well on ubuntu 12.x :)

  Booting "Try Ubuntu" on 20.04 get the correct resolution and 2
  displays, but the video glitches and shows all sorts of noise.  It is
  largely unusable (which makes filing this bug very hard).

  Safe Graphics works in low-res.

  The nvidia proprietary driver seems to not support this device any
  more.  I like this card because it has no fan (and I don't do a lot of
  graphics-intense stuff).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 18:13:48 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd G73 [GeForce 7600 GT] [1458:3417]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd  
---  priority=low
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: X58 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd12/30/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme6: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.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1875712] [NEW] Unusable graphics, nouveau + G73 (GEForce 7600)

[Tim Hockin]

Public bug reported:

This is an older card, but it worked well on ubuntu 12.x :)

Booting "Try Ubuntu" on 20.04 get the correct resolution and 2 displays,
but the video glitches and shows all sorts of noise.  It is largely
unusable (which makes filing this bug very hard).

Safe Graphics works in low-res.

The nvidia proprietary driver seems to not support this device any more.
I like this card because it has no fan (and I don't do a lot of
graphics-intense stuff).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 28 18:13:48 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: Gigabyte Technology Co., Ltd G73 [GeForce 7600 GT] [1458:3417]
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
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=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd  --- 
 priority=low
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/30/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.name: X58 Extreme6
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd12/30/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme6: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.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

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

Title:
  Unusable graphics, nouveau + G73 (GEForce 7600)

Status in xorg package in Ubuntu:
  New

Bug description:
  This is an older card, but it worked well on ubuntu 12.x :)

  Booting "Try Ubuntu" on 20.04 get the correct resolution and 2
  displays, but the video glitches and shows all sorts of noise.  It is
  largely unusable (which makes filing this bug very hard).

  Safe Graphics works in low-res.

  The nvidia proprietary driver seems to not support this device any
  more.  I like this card because it has no fan (and I don't do a lot of
  graphics-intense stuff).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 18:13:48 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd G73 [GeForce 7600 GT] [1458:3417]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd  
---  priority=low
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2010
  dmi.bios.vendor: American 

[Touch-packages] [Bug 1875684] [NEW] Can't connect to Pulseaudio after user change on Lubuntu 20.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

On fresh install of Lubuntu 20.04:
- First login after Computer startup, no sound problem.
- User Account logout and login to another account => Very often, the sound is 
off (with a prohibited sign instead of the speaker in the dashboard).
And the status of Pulse audio is "connecting" when I call pavucontrol.

The way to get the sound again is to lauch pulseaudio in a terminal or
to reboot the computer.

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


** Tags: bot-comment
-- 
Can't connect to Pulseaudio after user change on Lubuntu 20.04
https://bugs.launchpad.net/bugs/1875684
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio in Ubuntu.

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

[Touch-packages] [Bug 1875483] Re: vulkan failed with ERROR_INITIALIZATION_FAILED

[Vova]

Found how to solve this problem:

Add radeon.si_support=0 amdgpu.si_support=1 radeon.cik_support=0
amdgpu.cik_support=1 to GRUB_CMDLINE_LINUX in /etc/default/grub. Do it
via the command line with a text editor such as Nano or Vim.

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

Title:
  vulkan failed with ERROR_INITIALIZATION_FAILED

Status in mesa package in Ubuntu:
  New

Bug description:
  1.The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  2. The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Установлен: 20.0.4-2ubuntu1
Кандидат:   20.0.4-2ubuntu1
Таблица версий:
   *** 20.0.4-2ubuntu1 500
  500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. What you expected to happen

  run vulkaninfo
  run vkcube

  4. What happened instead

  $ vulkaninfo
  ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: 
wrong ELF class: ELFCLASS32
  ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: 
wrong ELF class: ELFCLASS32
  
/build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/vulkaninfo/vulkaninfo.h:477:
 failed with ERROR_INITIALIZATION_FAILED

  $ vkcube
  vkcube: 
/build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/cube/cube.c:3173: 
demo_init_vk: Assertion `!err' failed.
  Аварийный останов (стек памяти сброшен на диск)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mesa-vulkan-drivers 20.0.4-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon Apr 27 22:47:58 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7560D] [1043:8526]
   Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 
250/350] [1002:6610] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Oland XT [Radeon HD 8670 / R7 
250/350] [1458:226e]
  InstallationDate: Installed on 2020-04-23 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=24f6821a-8923-45d6-ad53-4f5250d5064a ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A58M-E
  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.:bvr1801:bd12/14/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA58M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1875699] Re: python3-venv missing ensurepip

[blueblob11]

** Attachment added: "List of files installed by python3 -mvenv .env"
   
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1875699/+attachment/5362714/+files/find.txt

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

Title:
  python3-venv missing ensurepip

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  I believe that I cannot even report this correctly because it appears
  the problem is in a package called python3-venv, however, launchpad
  tells me '"python3-venv" does not exist in Ubuntu.' despite it clearly
  being both installed and recommended by python itself.

  When trying to create a python3 virtual environment, I get errors
  about ensurepip missing, however I have installed python3-venv. The
  python3-venv package does not include ensurepip:

  python3.8 -mvenv .env
  The virtual environment was not created successfully because ensurepip is not
  available.  On Debian/Ubuntu systems, you need to install the python3-venv
  package using the following command.

  apt-get install python3-venv

  You may need to use sudo with that command.  After installing the python3-venv
  package, recreate your virtual environment.

  Failing command: ['/mnt/d/src/.env/bin/python3.8', '-Im', 'ensurepip',
  '--upgrade', '--default-pip']


  This is on Focal Fossa:
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  python3-venv:
Installed: 3.8.2-0ubuntu2
Candidate: 3.8.2-0ubuntu2
Version table:
   *** 3.8.2-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1875699] Re: python3-venv missing ensurepip

[blueblob11]

** Attachment added: "List of installed packages found via dpkg -l|grep python3"
   
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1875699/+attachment/5362702/+files/dpkg-l-grep-python3.txt

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

Title:
  python3-venv missing ensurepip

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  I believe that I cannot even report this correctly because it appears
  the problem is in a package called python3-venv, however, launchpad
  tells me '"python3-venv" does not exist in Ubuntu.' despite it clearly
  being both installed and recommended by python itself.

  When trying to create a python3 virtual environment, I get errors
  about ensurepip missing, however I have installed python3-venv. The
  python3-venv package does not include ensurepip:

  python3.8 -mvenv .env
  The virtual environment was not created successfully because ensurepip is not
  available.  On Debian/Ubuntu systems, you need to install the python3-venv
  package using the following command.

  apt-get install python3-venv

  You may need to use sudo with that command.  After installing the python3-venv
  package, recreate your virtual environment.

  Failing command: ['/mnt/d/src/.env/bin/python3.8', '-Im', 'ensurepip',
  '--upgrade', '--default-pip']


  This is on Focal Fossa:
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  python3-venv:
Installed: 3.8.2-0ubuntu2
Candidate: 3.8.2-0ubuntu2
Version table:
   *** 3.8.2-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1875699] [NEW] python3-venv missing ensurepip

[blueblob11]

Public bug reported:

I believe that I cannot even report this correctly because it appears
the problem is in a package called python3-venv, however, launchpad
tells me '"python3-venv" does not exist in Ubuntu.' despite it clearly
being both installed and recommended by python itself.

When trying to create a python3 virtual environment, I get errors about
ensurepip missing, however I have installed python3-venv. The
python3-venv package does not include ensurepip:

python3.8 -mvenv .env
The virtual environment was not created successfully because ensurepip is not
available.  On Debian/Ubuntu systems, you need to install the python3-venv
package using the following command.

apt-get install python3-venv

You may need to use sudo with that command.  After installing the python3-venv
package, recreate your virtual environment.

Failing command: ['/mnt/d/src/.env/bin/python3.8', '-Im', 'ensurepip', '
--upgrade', '--default-pip']


This is on Focal Fossa:
Description:Ubuntu 20.04 LTS
Release:20.04

python3-venv:
  Installed: 3.8.2-0ubuntu2
  Candidate: 3.8.2-0ubuntu2
  Version table:
 *** 3.8.2-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  python3-venv missing ensurepip

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  I believe that I cannot even report this correctly because it appears
  the problem is in a package called python3-venv, however, launchpad
  tells me '"python3-venv" does not exist in Ubuntu.' despite it clearly
  being both installed and recommended by python itself.

  When trying to create a python3 virtual environment, I get errors
  about ensurepip missing, however I have installed python3-venv. The
  python3-venv package does not include ensurepip:

  python3.8 -mvenv .env
  The virtual environment was not created successfully because ensurepip is not
  available.  On Debian/Ubuntu systems, you need to install the python3-venv
  package using the following command.

  apt-get install python3-venv

  You may need to use sudo with that command.  After installing the python3-venv
  package, recreate your virtual environment.

  Failing command: ['/mnt/d/src/.env/bin/python3.8', '-Im', 'ensurepip',
  '--upgrade', '--default-pip']


  This is on Focal Fossa:
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  python3-venv:
Installed: 3.8.2-0ubuntu2
Candidate: 3.8.2-0ubuntu2
Version table:
   *** 3.8.2-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1875697] [NEW] drop fix-ldap-distribution.patch?

[Ryan Tandy]

Public bug reported:

Hi,

In version 2.4.49+dfsg-3 I fixed a bug where the version was missing
from the -V output in OpenLDAP programs:
.

At the same time, I've patched it to display the package version there,
instead of the upstream version:

# slapd -VV
@(#) $OpenLDAP: slapd 2.4.49+dfsg-4 (Apr 15 2020 04:33:16) $
Debian OpenLDAP Maintainers 

If showing the distro version here fulfills the same requirements as the
fix-ldap-distribution.patch, then maybe that patch can be dropped?

Thanks.

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

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

Title:
  drop fix-ldap-distribution.patch?

Status in openldap package in Ubuntu:
  New

Bug description:
  Hi,

  In version 2.4.49+dfsg-3 I fixed a bug where the version was missing
  from the -V output in OpenLDAP programs:
  .

  At the same time, I've patched it to display the package version
  there, instead of the upstream version:

  # slapd -VV
  @(#) $OpenLDAP: slapd 2.4.49+dfsg-4 (Apr 15 2020 04:33:16) $
Debian OpenLDAP Maintainers 

  If showing the distro version here fulfills the same requirements as
  the fix-ldap-distribution.patch, then maybe that patch can be dropped?

  Thanks.

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

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

[Touch-packages] [Bug 1875645] Re: Graphics corruption on shell on login screen and session screen

[Sebastien Bacher]

Thanks, you only included one screen of log though, could you do
$ journalctl -b 0 > log
and add the 'log' file to the bug?

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

Title:
  Graphics corruption on shell on login screen and session screen

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading from 19.10 to 20.04 I am seeing blocky green and
  purple artefacts on icons, background images and text. This is visible
  on the login screen and once logged in.

  Only the "shell" is corrupted and any subsequent changes, such as
  changing the background image, are displayed without corruption. The
  corruption is random but it is predictable that it will appear on the
  launcher icons, background image and shell menu icons and text.

  I've tried swapping between available graphics drivers but it makes no
  difference.

  Text corruption in menus is on particular glyphs selected at random.
  In the screen shots, for example, all upper-case and lower-case 'O's
  are currupted but on a subsequent reboot the affected glyphs will
  vary. On filing this bug I also notice that the pop-up modal password
  requests also displayed the corrupted glyphs. No programms run
  subsequently will display any problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 14:29:39 2020
  DistUpgraded: 2020-04-24 15:49:16,469 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0905]
 Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905]
  InstallationDate: Installed on 2019-12-05 (144 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 15 7590
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-26-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-24 (3 days ago)
  dmi.bios.date: 02/06/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0VYV0G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd02/06/2020:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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