[Touch-packages] [Bug 1917183] Re: Font spacing and rendering is wrong in latest 21.04

2021-02-28 Thread Bill (franksmcb) 
** Changed in: fonts-noto-color-emoji (Ubuntu)
   Status: New => Confirmed

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

Title:
  Font spacing and rendering is wrong in latest 21.04

Status in Ubuntu MATE:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in fontconfig package in Ubuntu:
  Confirmed
Status in fonts-noto-color-emoji package in Ubuntu:
  Confirmed
Status in yelp package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu MATE 21.04 Font spacing is incorrect.

  Including screen shots of pages.

  This front spacing issue is occurring whilst filing this bug report on
  Launchpad.

  Expected outcome:
  Font's space and render properly in Firefox

  Actual outcome:
  Font space and render is incorrect.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: firefox 86.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  franksmcb   2695 F pulseaudio
  BuildID: 20210222142601
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: MATE
  Date: Sat Feb 27 16:50:33 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:348
  DefaultProfilePrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntumate.js
   prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2019-12-13 (442 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 
(20191213)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.154 metric 
600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:348
  Profile0PrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntumate.js
   prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=77.0/20200528194502 (Out of date)
   Profile0 - LastVersion=86.0/20210222142601 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to hirsute on 2020-06-02 (270 days ago)
  dmi.bios.date: 08/07/2019
  dmi.bios.release: 2.82
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETC2WW (2.82 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2347GBU
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2347GBU:pvrThinkPadT430:rvnLENOVO:rn2347GBU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2347GBU
  dmi.product.sku: LENOVO_MT_2347
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

2021-02-07 Thread Bill (franksmcb) 
Some follow-up with users from the Ubuntu MATE Community forums show
that this is occurring on Focal and Groovy; with 5.4, 5.8, and 5.10
kernels.


Following is a list of hardware and graphics information from affected users:

System:
  Host: huppyryzen Kernel: 5.4.0-54-generic x86_64 bits: 64 
  Desktop: MATE 1.24.0 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) 
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x 
  serial:  UEFI: American Megatrends v: 5602 
  date: 07/14/2020 
Graphics:
  Device-1: AMD Vega 10 XL/XT [Radeon RX Vega 56/64] driver: amdgpu 
  v: kernel 
  Display: x11 server: X.Org 1.20.8 driver: amdgpu,ati 
  unloaded: fbdev,modesetting,vesa resolution: 3440x1440~60Hz 
  OpenGL: 
  renderer: Radeon RX Vega (VEGA10 DRM 3.35.0 5.4.0-54-generic LLVM 11.0.0) 
  v: 4.6 Mesa 20.3.0-rc2

System:
  Host: marptop Kernel: 5.4.0-54-generic x86_64 bits: 64 
  Desktop: MATE 1.24.0 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) 
Machine:
  Type: Laptop System: HP product: HP Laptop 17-ca0xxx v: N/A 
  serial:  
  Mobo: HP model: 84D2 v: 91.17 serial:  UEFI: AMI 
  v: F.21 date: 11/15/2018 
Graphics:
  Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] 
  driver: amdgpu v: kernel 
  Display: x11 server: X.Org 1.20.8 driver: amdgpu,ati 
  unloaded: fbdev,modesetting,vesa resolution: 1600x900~60Hz 
  OpenGL: renderer: AMD RAVEN (DRM 3.35.0 5.4.0-54-generic LLVM 10.0.0) 
  v: 4.6 Mesa 20.0.8

System:
Host: duck-laptop2 Kernel: 5.8.0-29-generic x86_64 bits: 64 Desktop: MATE 
1.24.1 
Distro: Ubuntu 20.10 (Groovy Gorilla) 
Machine:   
Type: Laptop System: HP product: HP Laptop 15-db0xxx v: 
Type1ProductConfigId serial:  
Mobo: HP model: 84AE v: 86.20 serial:  UEFI: 
Insyde v: F.10 date: 05/31/2018 
Graphics: 
Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] 
driver: amdgpu v: kernel 
Device-2: Lite-On 1351 type: USB driver: uvcvideo 
Display: x11 server: X.Org 1.20.9 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa resolution: 1920x1080~60Hz 
OpenGL: renderer: AMD RAVEN (DRM 3.38.0 5.8.0-29-generic LLVM 11.0.0) v: 
4.6 Mesa 20.2.1

System:
Host: jgjmate-ThinkPad-E595 Kernel: 5.8.0-32-generic x86_64 bits: 64
Desktop: MATE 1.24.1 Distro: Ubuntu 20.10 (Groovy Gorilla)
Machine:
Type: Laptop System: LENOVO product: 20NF0012US v: ThinkPad E595
serial: 
Mobo: LENOVO model: 20NF0012US serial: 
UEFI: LENOVO v: R11ET39W (1.19 ) date: 09/11/2020
Graphics:
Device-1: AMD Picasso driver: amdgpu v: kernel
Device-2: Acer SunplusIT Integrated Camera type: USB driver: uvcvideo
Display: x11 server: X.Org 1.20.9 driver: amdgpu,ati
unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: AMD RAVEN (DRM 3.38.0 5.8.0-32-generic LLVM 11.0.0)
v: 4.6 Mesa 20.2.1

System:
Host:  Kernel: 5.4.0-58-generic x86_64 bits: 64
Desktop: MATE 1.24.0 Distro: Ubuntu 20.04.1 LTS (Focal Fossa)
Machine:
Type: Laptop System: HP product: HP Laptop 15-db0xxx
v: Type1ProductConfigId serial: 
Mobo: HP model: 84AC v: 85.26 serial: 
UEFI: Insyde v: F.22 date: 11/06/2019
Graphics:
Device-1: AMD Stoney [Radeon R2/R3/R4/R5 Graphics] driver: amdgpu
v: kernel
Display: x11 server: X.Org 1.20.8 driver: amdgpu,ati
unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz
OpenGL: renderer: AMD STONEY (DRM 3.35.0 5.4.0-58-generic LLVM 10.0.0)
v: 4.5 Mesa 20.0.8

System:
Host: pc Kernel: 5.4.0-58-generic x86_64 bits: 64 Desktop: MATE 1.24.0 
Distro: Ubuntu 20.04.1 LTS (Focal Fossa) 
Machine:   
Type: Desktop Mobo: MSI model: B75MA-P45 (MS-7798) v: 1.0 serial: 
 
BIOS: American Megatrends v: 1.9 date: 09/30/2013 
Graphics:  
Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 
XT / 5700/5700 XT] driver: amdgpu 
v: kernel 
Display: x11 server: X.Org 1.20.8 driver: amdgpu,ati unloaded: 
fbdev,modesetting,radeon,vesa 
resolution: 1366x768~60Hz 
OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.38.0 5.4.0-58-generic 
LLVM 11.0.0) 
v: 4.6 Mesa 21.0.0-devel (git-6a34a68 2020-12-13 focal-oibaf-ppa)

System:
Host: ACER-xk2308 Kernel: 5.10.4-051004-generic x86_64 bits: 64 Desktop: 
MATE 1.24.0 
Distro: Ubuntu 20.04.1 LTS (Focal Fossa) 
Machine:   
Type: Desktop Mobo: MSI model: B75MA-P45 (MS-7798) v: 1.0 serial: 
 
BIOS: American Megatrends v: 1.9 date: 09/30/2013 
Graphics:  
Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 
XT / 5700/5700 XT] driver: amdgpu 
v: kernel 
Display: x11 server: X.Org 1.20.8 driver: amdgpu,ati unloaded: 
fbdev,modesetting,radeon,vesa 
resolution: 1366x768~60Hz 
OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.40.0 
5.10.4-051004-generic LLVM 11.0.0) 
v: 4.6 Mesa 21.0.0-devel (git-24dcdc3 2021-01-04 focal-oibaf-ppa)

System:
Host: ACER-xk2308 Kernel: 5.8.0-38-generic x86_64

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

2020-10-22 Thread Bill (franksmcb) 
This is confirmed working correctly on Ubuntu MATE with 20201022 re-
spin.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1897934] Re: [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero (mute)

2020-10-21 Thread Bill (franksmcb) 
This breaks Screen Reader installs for Visually impaired users and
breaks testcase #1305

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

Title:
  [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero
  (mute)

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

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

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

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

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

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

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

[Touch-packages] [Bug 1897934] Re: [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero (mute)

2020-10-21 Thread Bill (franksmcb) 
This is occurring on 20.10 Ubuntu MATE 20201021.2

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

Title:
  [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero
  (mute)

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

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

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

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

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

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

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

[Touch-packages] [Bug 1844426] Re: Impossible to set up Livepatch on Ubuntu MATE

2020-05-31 Thread Bill (franksmcb) 
** Also affects: software-properties (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Impossible to set up Livepatch on Ubuntu MATE

Status in Ubuntu MATE:
  Confirmed
Status in software-properties package in Ubuntu:
  New

Bug description:
  In Ubuntu MATEE 18.04, in the Software Properties window (available
  from Software Boutique > Preferences > Show Software Sources > Manage
  Repositories, among other places), there is a Livepatch tab. This tab
  says "To use Livepatch, you need to sign in" and provides a "Sign
  In..." button.

  This button launches an empty version of gnome-control-center with no
  icons in it.

  If one is technically adept, it is possible to do what (I think) that
  button is trying to do by launching g-c-c directly in a terminal and
  overriding the desktop, thus:

  env XDG_CURRENT_DESKTOP=GNOME gnome-control-center online-accounts

  This online accounts window permits attempting to add an Ubuntu One
  account. However, when one tries, a window pops up with a place to add
  one's Ubuntu One username and password, but the window has no Submit
  button; there is no way to actually initiate sign in.

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

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

[Touch-packages] [Bug 1875944] Re: Lenovo Ideapad 130-15AST 20.04 distorted and unusable

2020-05-08 Thread Bill (franksmcb) 
*** This bug is a duplicate of bug 1873895 ***
https://bugs.launchpad.net/bugs/1873895

** This bug has been marked a duplicate of bug 1873895
   Regression: block staircase display with side-by-side monitors of different 
pixel widths

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

Title:
  Lenovo Ideapad 130-15AST 20.04 distorted and unusable

Status in Ubuntu MATE:
  Confirmed
Status in libdrm package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Output of lshw here: https://pastebin.com/NMBigV4G

  Screenshot of the desktop here in the community forum: 
  
https://ubuntu-mate.community/t/lenovo-ideapad-20-04-upgrade-distorted-and-unusable/21617

  I'm not all that experienced at filing bug reports here so I have
  included the attachment of the photo found at the forum link.

  The picture in the community forum link is what the MATE 20.04 live USB boots 
to.
  I first upgraded from 18.04 using do-release-upgrade. The result looked like 
the photo as well.
  Then I reinstalled 18.04, upgraded to 19.10, which looked and performed 
normally. I then upgraded the 19.10 install to 20.04 with the same result as 
the photo.
  I also tried with a different flash drive just to rule that out.

  Then I made the live USB of the 20.04 image and booted it to what you see in 
the forum post.
  I made a live USB of both Stock Ubuntu and Kubuntu 20.04 and both worked just 
fine.

  Until I tried the other two flavors I was thinking it was system
  specific, but after they worked normally it seems to be a MATE
  specific issue with this system.

  It appears to be only a display problem. The DE is completely unusable with 
the mouse, but I can launch a terminal and run commands, although the terminal 
is just as distorted as the photo above, so you can't see what you are typing 
or the resulting output.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  clay   1524 F pulseaudio
   /dev/snd/controlC0:  clay   1524 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: rtl8821ce, v5.5.2_34066.20200325, 5.3.0-46-generic, x86_64: 
installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev ea) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:39f5]
  InstallationDate: Installed on 2020-04-27 (11 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: LENOVO 81H5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=bec09cbc-83af-49f6-8aeb-f02059977f4a ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  bionic ubuntu
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8ZCN15WW(V1.04)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 130-15AST
  dmi.modalias: 
dmi:bvnLENOVO:bvr8ZCN15WW(V1.04):bd06/27/2018:svnLENOVO:pn81H5:pvrLenovoideapad130-15AST:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad130-15AST:
  dmi.product.family: ideapad 130-15AST
  dmi.product.name: 81H5
  dmi.product.sku: LENOVO_MT_81H5_BU_idea_FM_ideapad 130-15AST
  dmi.product.version: Lenovo ideapad 130-15AST
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

[Touch-packages] [Bug 1873386] Re: nmcli error report on reboot after latest 20.04 updates

2020-04-17 Thread Bill (franksmcb) 
Link to crash report from step #2:

https://errors.ubuntu.com/oops/88d785d4-80ba-11ea-a860-fa163ee63de6

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

Title:
  nmcli error report on reboot after latest 20.04 updates

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Ubuntu MATE 20.04. Updated to latest updates and newest kernel, on
  20200416.

  Upon reboot system should error and error for nmcli.

  Crash file located in /var/crash

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Thu Apr 16 21:58:56 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-04-25 (357 days ago)
  InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.159 metric 
600
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-04 (12 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATEIP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH 
 CONNECTION  CON-UUID   
   CON-PATH   
   wlp2s0  wifi  connectedfull  full  
/org/freedesktop/NetworkManager/Devices/3  Lothlorien  
41892137-acd0-46f2-8959-5f1e126489b0  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  none  none  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo  loopback  unmanagedunknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1873386] [NEW] nmcli error report on reboot after latest 20.04 updates

2020-04-16 Thread Bill (franksmcb) 
Public bug reported:

Ubuntu MATE 20.04. Updated to latest updates and newest kernel, on
20200416.

Upon reboot system should error and error for nmcli.

Crash file located in /var/crash

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
Uname: Linux 5.4.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Thu Apr 16 21:58:56 2020
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2019-04-25 (357 days ago)
InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Release amd64 (20190416)
IpRoute:
 default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp2s0 scope link metric 1000 
 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.159 metric 600
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to focal on 2020-04-04 (12 days ago)
nmcli-dev:
 DEVICE  TYPE  STATEIP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH   
   CONNECTION  CON-UUID 
 CON-PATH   
 wlp2s0  wifi  connectedfull  full  
/org/freedesktop/NetworkManager/Devices/3  Lothlorien  
41892137-acd0-46f2-8959-5f1e126489b0  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 enp1s0  ethernet  unavailable  none  none  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
 lo  loopback  unmanagedunknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  nmcli error report on reboot after latest 20.04 updates

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu MATE 20.04. Updated to latest updates and newest kernel, on
  20200416.

  Upon reboot system should error and error for nmcli.

  Crash file located in /var/crash

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Thu Apr 16 21:58:56 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-04-25 (357 days ago)
  InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.159 metric 
600
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-04 (12 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATEIP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH 
 CONNECTION  CON-UUID   
   CON-PATH   
   wlp2s0  wifi  connectedfull  full  
/org/freedesktop/NetworkManager/Devices/3  Lothlorien  
41892137-acd0-46f2-8959-5f1e126489b0  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  none  none  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo  loopback  unmanagedunknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

-- 
Mailing list: https:

[Touch-packages] [Bug 1869923] [NEW] lightdm crashes on login to system 20.04

2020-03-31 Thread Bill (franksmcb) 
Public bug reported:

Ubuntu MATE 20.04 updated 03312020

Hesitation on login to system
Login successful
System reports error and crash file located in /var/crash

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lightdm 1.30.0-0ubuntu3.1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Mar 31 11:13:52 2020
InstallationDate: Installed on 2019-12-13 (109 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20191213)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  lightdm crashes on login to system 20.04

Status in lightdm package in Ubuntu:
  New

Bug description:
  Ubuntu MATE 20.04 updated 03312020

  Hesitation on login to system
  Login successful
  System reports error and crash file located in /var/crash

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Mar 31 11:13:52 2020
  InstallationDate: Installed on 2019-12-13 (109 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 
(20191213)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

2020-03-30 Thread Bill (franksmcb) 
Tested with latest packages in proposed Ubuntu MATE and able to install
and use balena-etcher-electron.

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  Fix Committed

Bug description:
  I just updated my machine, and when I did libpango1.0-0 was removed.
  This removed minecraft-launcher - the (very) popular launcher for
  Minecraft Java edition.

  I have reported this upstream, in case they can update their package
  https://bugs.mojang.com/browse/MCL-13512

  I am filing this bug so we can track it internally. I personally think
  this shouldn't have been done this late in the cycle, but there may
  well have been good reasons for it.

  As a result of the change though, it's now not possible to install
  Minecraft on Ubuntu 20.04.

  $ sudo apt install ./Minecraft\(1\).deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

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

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

[Touch-packages] [Bug 1869787] Re: libpango1.0-0 has been removed from 20.04 and is not installable

2020-03-30 Thread Bill (franksmcb) 
*** This bug is a duplicate of bug 1869716 ***
https://bugs.launchpad.net/bugs/1869716

https://packages.ubuntu.com/bionic/libpango1.0-0

** Package changed: ubuntu => pango1.0 (Ubuntu)

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

Title:
  libpango1.0-0 has been removed from 20.04 and is not installable

Status in pango1.0 package in Ubuntu:
  New

Bug description:
  Upon update on 30 March 2020 libpango1.0-0 was removed from the
  system.

  Package libpango1.0-0 is not available, but is referred to by another package.
  This may mean that the package is missing, has been obsoleted, or
  is only available from another source
  However the following packages replace it:
libpangox-1.0-0

  However applications such as balena-etcher require libpango1.0-0

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

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

[Touch-packages] [Bug 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed

2020-03-02 Thread Bill (franksmcb) 
Using 20.04 current build still see:

$ python

Command 'python' not found, but can be installed with:

If I run sudo apt install python

Package python is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  python2-minimal:i386 python2:i386 python2-minimal python2 2to3

E: Package 'python' has no installation candidate

This has an effect on an upgrade to 20.04 of uninstalling any package
that depends on "python" for example slack-desktop.

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

Title:
  Invoking "python" brings inappropriate response from command-not-found
  when python3 installed

Status in command-not-found package in Ubuntu:
  Triaged
Status in python3-defaults package in Ubuntu:
  Triaged
Status in command-not-found source package in Focal:
  Triaged
Status in python3-defaults source package in Focal:
  Triaged

Bug description:
  Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't
  have python 2.7 installed, but have python 3 installed as per default.

  Please see ascii-cast at
  https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 .

  Running `python` brings up text from command-not-found which suggests
  installing `python3` as a solution to the missing command. `python3`
  is already installed, is a later version than the one indicated by
  command-not-found and does not supply a binary or symlink named
  `python`.

  $ apt policy python
  python:
Installed: (none)
Candidate: (none)
Version table:
   2.7.17-1 -1
  100 /var/lib/dpkg/status
  $ apt policy python3
  python3:
Installed: 3.8.0-3
Candidate: 3.8.0-3
Version table:
   *** 3.8.0-3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt policy command-not-found
  command-not-found:
Installed: 19.10.0
Candidate: 19.10.0
Version table:
   *** 19.10.0 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  I don't know whether this is a bug in python3 or command-not-found
  (the latter of which doesn't seem to have been updated for 20.04 yet).
  i don't know if it is intentional that `python3` will not provide a
  binary or symlink named `python`. if that is the case, the output of
  `command-not-found` should be updated to reflect that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.0-3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Feb 17 01:35:16 2020
  InstallationDate: Installed on 2019-10-11 (128 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  SourcePackage: python3-defaults
  UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+subscriptions

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

[Touch-packages] [Bug 1863825] [NEW] 20.04 apt update of python 3.8 gives errors

2020-02-18 Thread Bill (franksmcb) 
Public bug reported:

Run sudo apt dist-upgrade on 20.04 install.

Expected result:

python3 is updated without issue

Actual result:


After this operation, 1,114 kB disk space will be freed.
Do you want to continue? [Y/n] y
Get:1 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3-minimal 
amd64 3.8.0-3ubuntu1 [23.3 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3 amd64 
3.8.0-3ubuntu1 [47.6 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu focal/main amd64 libpython3-stdlib 
amd64 3.8.0-3ubuntu1 [6,872 B]
Get:4 http://us.archive.ubuntu.com/ubuntu focal/main amd64 libnewt0.52 amd64 
0.52.21-4ubuntu2 [41.1 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu focal/main amd64 whiptail amd64 
0.52.21-4ubuntu2 [17.0 kB]
Get:6 http://us.archive.ubuntu.com/ubuntu focal/main amd64 gnome-disk-utility 
amd64 3.35.91-1ubuntu1 [186 kB]
Get:7 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 onboard-data all 
1.4.1-2ubuntu7 [3,803 kB]
Get:8 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 onboard amd64 
1.4.1-2ubuntu7 [351 kB] 
Get:9 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 onboard-common 
all 1.4.1-2ubuntu7 [530 kB]
Get:10 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 
python3-html5-parser amd64 0.4.9-3build1 [125 kB]   
 
Get:11 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3-renderpm 
amd64 3.5.34-1build1 [60.4 kB]  
Get:12 http://us.archive.ubuntu.com/ubuntu focal/main amd64 
python3-reportlab-accel amd64 3.5.34-1build1 [19.4 kB]  
 
Get:13 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3-reportlab 
all 3.5.34-1build1 [546 kB]
Get:14 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3-systemd 
amd64 234-3build2 [36.5 kB]  
Fetched 5,793 kB in 8s (694 kB/s)   
 
(Reading database ... 529746 files and directories currently installed.)
Preparing to unpack .../python3-minimal_3.8.0-3ubuntu1_amd64.deb ...
Unpacking python3-minimal (3.8.0-3ubuntu1) over (3.8.0-3) ...
Setting up python3-minimal (3.8.0-3ubuntu1) ...
/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering 
(buffering=1) isn't supported in binary mode, the default buffer size will be 
use
d
  self.stdin = io.open(p2cwrite, 'wb', bufsize)
(Reading database ... 529746 files and directories currently installed.)
Preparing to unpack .../00-python3_3.8.0-3ubuntu1_amd64.deb ...
running python pre-rtupdate hooks for python3.8...
Unpacking python3 (3.8.0-3ubuntu1) over (3.8.0-3) ...
Preparing to unpack .../01-libpython3-stdlib_3.8.0-3ubuntu1_amd64.deb ...
Unpacking libpython3-stdlib:amd64 (3.8.0-3ubuntu1) over (3.8.0-3) ...
Preparing to unpack .../02-libnewt0.52_0.52.21-4ubuntu2_amd64.deb ...
Unpacking libnewt0.52:amd64 (0.52.21-4ubuntu2) over (0.52.21-4ubuntu1) ...
Preparing to unpack .../03-whiptail_0.52.21-4ubuntu2_amd64.deb ...
Unpacking whiptail (0.52.21-4ubuntu2) over (0.52.21-4ubuntu1) ...
Preparing to unpack .../04-gnome-disk-utility_3.35.91-1ubuntu1_amd64.deb ...
Unpacking gnome-disk-utility (3.35.91-1ubuntu1) over (3.35.2-1ubuntu1) ...
Preparing to unpack .../05-onboard-data_1.4.1-2ubuntu7_all.deb ...
Unpacking onboard-data (1.4.1-2ubuntu7) over (1.4.1-2ubuntu6) ...
Preparing to unpack .../06-onboard_1.4.1-2ubuntu7_amd64.deb ...
Unpacking onboard (1.4.1-2ubuntu7) over (1.4.1-2ubuntu6) ...
Preparing to unpack .../07-onboard-common_1.4.1-2ubuntu7_all.deb ...
Unpacking onboard-common (1.4.1-2ubuntu7) over (1.4.1-2ubuntu6) ...
Preparing to unpack .../08-python3-html5-parser_0.4.9-3build1_amd64.deb ...
Unpacking python3-html5-parser (0.4.9-3build1) over (0.4.9-3) ...
Preparing to unpack .../09-python3-renderpm_3.5.34-1build1_amd64.deb ...
Unpacking python3-renderpm:amd64 (3.5.34-1build1) over (3.5.34-1) ...
Preparing to unpack .../10-python3-reportlab-accel_3.5.34-1build1_amd64.deb ...
Unpacking python3-reportlab-accel:amd64 (3.5.34-1build1) over (3.5.34-1) ...
Preparing to unpack .../11-python3-reportlab_3.5.34-1build1_all.deb ...
Unpacking python3-reportlab (3.5.34-1build1) over (3.5.34-1) ...
Preparing to unpack .../12-python3-systemd_234-3build2_amd64.deb ...
Unpacking python3-systemd (234-3build2) over (234-3build1) ...
Setting up libnewt0.52:amd64 (0.52.21-4ubuntu2) ...
Setting up whiptail (0.52.21-4ubuntu2) ...
Setting up gnome-disk-utility (3.35.91-1ubuntu1) ...
Setting up libpython3-stdlib:amd64 (3.8.0-3ubuntu1) ...
Setting up python3 (3.8.0-3ubuntu1) ...
running python rtupdate hooks for python3.8...
/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering 
(buffering=1) isn't supported in binary mode, the default buffer size will be 
use
d

[Touch-packages] [Bug 1856927] Re: totem crashed with SIGSEGV in build_flavored_key() from insert_key_mapping()

2020-02-18 Thread Bill (franksmcb) 
@seb128 this is working correctly now after the grilo update.
Thanks

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

Title:
  totem crashed with SIGSEGV in build_flavored_key() from
  insert_key_mapping()

Status in Grilo Plugins:
  Fix Released
Status in grilo-plugins package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/55095074fb3c3335c19f63f3c91d3a8231be2034

  ---

  Test case:
  Fresh 20.04 install, updated
  Open totem
  What happens: segfault

  Installing grilo-plugins-0.3-extra allows totem to open fine.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: totem 3.34.1-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu14
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 18 19:51:40 2019
  ExecutablePath: /usr/bin/totem
  ExecutableTimestamp: 1570435741
  InstallationDate: Installed on 2019-12-19 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcCwd: /home/doug
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f76b92f6dd6:movzbl (%rax),%eax
   PC (0x7f76b92f6dd6) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so
   grl_tracker_setup_key_mappings () from 
/usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so
   ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so
   ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so
   ?? () from /lib/x86_64-linux-gnu/libtracker-sparql-2.0.so.0
  Title: totem crashed with SIGSEGV in grl_tracker_setup_key_mappings()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/grilo-plugins/+bug/1856927/+subscriptions

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

[Touch-packages] [Bug 1861191] Re: System hangs on graphical boot after kernel and nVidia upgrade

2020-01-28 Thread Bill (franksmcb) 
nVidia driver 340.107 is available, however switching to that in
Software & Updates has resulted in some issues.

After Apply Changes, I am kicked to the Nouveau driver.

And I get an ErrorBrokenCount > 0

Trying to resolve with sudo apt --fix-broken install as recommended by
apt gives me:

The following additional packages will be installed:
  libnvidia-gl-390 libnvidia-gl-390:i386
The following NEW packages will be installed:
  libnvidia-gl-390 libnvidia-gl-390:i386
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
Need to get 0 B/29.1 MB of archives.
After this operation, 147 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 482145 files and directories currently installed.)
Preparing to unpack .../libnvidia-gl-390_390.116-0ubuntu0.18.04.3_i386.deb ...
diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to 
/usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340
dpkg-divert: error: mismatch on package
  when removing 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 by 
libnvidia-gl-390'
  found 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to 
/usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340'
dpkg: error processing archive 
/var/cache/apt/archives/libnvidia-gl-390_390.116-0ubuntu0.18.04.3_i386.deb 
(--unpack):
 new libnvidia-gl-390:i386 package pre-installation script subprocess returned 
error exit status 2
Preparing to unpack .../libnvidia-gl-390_390.116-0ubuntu0.18.04.3_amd64.deb ...
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to 
/usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340
dpkg-divert: error: mismatch on package
  when removing 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 by 
libnvidia-gl-390'
  found 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to 
/usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340'
dpkg: error processing archive 
/var/cache/apt/archives/libnvidia-gl-390_390.116-0ubuntu0.18.04.3_amd64.deb 
(--unpack):
 new libnvidia-gl-390:amd64 package pre-installation script subprocess returned 
error exit status 2
Errors were encountered while processing:
 /var/cache/apt/archives/libnvidia-gl-390_390.116-0ubuntu0.18.04.3_i386.deb
 /var/cache/apt/archives/libnvidia-gl-390_390.116-0ubuntu0.18.04.3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  System hangs on graphical boot after kernel and nVidia upgrade

Status in xorg package in Ubuntu:
  New

Bug description:
  System is Ubuntu MATE 18.04.3 T430 with nVidia

  On 27 Jan 2019 nvidia drivers were updated to 390.116 via apt upgrades with 
no issues.
  On 28 Jan 2919 kernel was updated to 5.3.0-28.30-18 via apt upgrades with no 
issues.
  System was rebooted today.

  Expected outcome:
  System reboots into desktop login

  Actual outcome:
  System gets to grub menu then hangs on black screen. TTYs are not responsive.

  This is reproducible and consistent. System will return to black
  screen and hung state.

  Workaround:
  Editing Grub and adding nouveau.modset=0 allows system to boot to GUI login.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Tue Jan 28 09:57:02 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 5.3.0-26-generic, x86_64: installed
   nvidia, 390.116, 5.3.0-28-generic, x86_64: installed
   virtualbox, 5.2.34, 5.0.0-37-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-26-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  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: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f4]
   NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo GF108M [NVS 5400M] [17aa:21f4]
  InstallationDate: Installed on 2019-12-05 (

[Touch-packages] [Bug 1861191] [NEW] System hangs on graphical boot after kernel and nVidia upgrade

2020-01-28 Thread Bill (franksmcb) 
Public bug reported:

System is Ubuntu MATE 18.04.3 T430 with nVidia

On 27 Jan 2019 nvidia drivers were updated to 390.116 via apt upgrades with no 
issues.
On 28 Jan 2919 kernel was updated to 5.3.0-28.30-18 via apt upgrades with no 
issues.
System was rebooted today.

Expected outcome:
System reboots into desktop login

Actual outcome:
System gets to grub menu then hangs on black screen. TTYs are not responsive.

This is reproducible and consistent. System will return to black screen
and hung state.

Workaround:
Editing Grub and adding nouveau.modset=0 allows system to boot to GUI login.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
 GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: MATE
Date: Tue Jan 28 09:57:02 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.116, 5.3.0-26-generic, x86_64: installed
 nvidia, 390.116, 5.3.0-28-generic, x86_64: installed
 virtualbox, 5.2.34, 5.0.0-37-generic, x86_64: installed
 virtualbox, 5.2.34, 5.3.0-26-generic, x86_64: installed
 virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
ExtraDebuggingInterest: Yes
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: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f4]
 NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo GF108M [NVS 5400M] [17aa:21f4]
InstallationDate: Installed on 2019-12-05 (53 days ago)
InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
MachineType: LENOVO 23445PU
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=5977afa2-a407-43bd-a6f4-e5dfd01188c0 ro quiet splash mouveau.modset=0
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/07/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: G1ETC2WW (2.82 )
dmi.board.asset.tag: Not Available
dmi.board.name: 23445PU
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:svnLENOVO:pn23445PU:pvrThinkPadT430:rvnLENOVO:rn23445PU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T430
dmi.product.name: 23445PU
dmi.product.sku: LENOVO_MT_2344
dmi.product.version: ThinkPad T430
dmi.sys.vendor: LENOVO
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic freeze ubuntu

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

Title:
  System hangs on graphical boot after kernel and nVidia upgrade

Status in xorg package in Ubuntu:
  New

Bug description:
  System is Ubuntu MATE 18.04.3 T430 with nVidia

  On 27 Jan 2019 nvidia drivers were updated to 390.116 via apt upgrades with 
no issues.
  On 28 Jan 2919 kernel was updated to 5.3.0-28.30-18 via apt upgrades with no 
issues.
  System was rebooted today.

  Expected outcome:
  System reboots into desktop login

  Actual outcome:
  System gets to grub menu then hangs on black screen. TTYs are not responsive.

  This is reproducible and consistent. System will return to black
  screen and hung state.

  Workaround:
  Editing Grub and adding nouveau.modset=0 al