[Touch-packages] [Bug 1866351] Re: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Expired

Bug description:
  OK
  Hope it is not too serious a problem

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.8
  ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208
  Uname: Linux 4.4.0-173-generic i686
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: i386
  Date: Fri Mar  6 08:22:31 2020
  DpkgHistoryLog:
   Start-Date: 2020-03-06  08:21:40
   Commandline: aptdaemon role='role-commit-packages' sender=':1.53'
   Upgrade: libsasl2-modules-db:i386 (2.1.26.dfsg1-14ubuntu0.1, 
2.1.26.dfsg1-14ubuntu0.2), openjdk-8-jre:i386 (8u232-b09-0ubuntu1~16.04.1, 
8u242-b08-0ubuntu3~16.04), libsasl2-2:i386 (2.1.26.dfsg1-14ubuntu0.1, 
2.1.26.dfsg1-14ubuntu0.2), libsasl2-modules:i386 (2.1.26.dfsg1-14ubuntu0.1, 
2.1.26.dfsg1-14ubuntu0.2), firefox-locale-en:i386 
(72.0.1+build1-0ubuntu0.16.04.1, 73.0.1+build1-0ubuntu0.16.04.1), 
openjdk-8-jre-headless:i386 (8u232-b09-0ubuntu1~16.04.1, 
8u242-b08-0ubuntu3~16.04), firefox:i386 (72.0.1+build1-0ubuntu0.16.04.1, 
73.0.1+build1-0ubuntu0.16.04.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-05-18 (1022 days ago)
  InstallationMedia: Custom 14.04 - Release i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-10-11 (512 days ago)

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

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

[Touch-packages] [Bug 1877473] Re: Upgrading from 18.04 to 20.04 encrypted installation with LUKS and LVM makes it unbootable without manual intervention

[Serhiy Zahoriya]

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

** This bug has been marked a duplicate of bug 1874381
   LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for 
device /dev/mapper/s5lp8--v g-home

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

Title:
  Upgrading from 18.04 to 20.04 encrypted installation with LUKS and LVM
  makes it unbootable without manual intervention

Status in lvm2 package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  Incomplete

Bug description:
  Volume Group metadata had to be upgraded manually with

  vgck --updatemetadata yourvgname

  The VG name was somehow changed from lvm-name to just name and I had
  to edit /etc/crypttab and update-initramfs -u -k all

  Also cryptsetup-initramfs package was deleted for some reason, had to
  re-install it in chroot. Maybe it happened because I have disabled
  installing recommended and suggested packages or maybe because none of
  *buntu-desktop packages are installed on my system. Not sure if I have
  to report it as a separate problem, please advise.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri May  8 01:35:04 2020
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1867029] Re: Package ifupdown breaks network configuration by cloud-init

[Chad Smith]

This bug is believed to be fixed in cloud-init in version 20.2. If this
is still a problem for you, please make a comment and set the state back
to New

Thank you.

** Changed in: cloud-init
   Status: Fix Committed => Fix Released

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

Title:
  Package ifupdown breaks network configuration by cloud-init

Status in cloud-init:
  Fix Released
Status in ifupdown package in Ubuntu:
  New

Bug description:
  It appears the `ifupdown` package breaks networking configuration that
  cloud-init would normally handle (?) on both providers. The result, if
  you image an instance with the `ifupdown` package installed, is that
  the image is not bootable by Azure/AWS. I'm not familiar with how
  Azure/AWS/etc use cloud-init for network start up however. I'm filing
  here for now, in case `cloud-init` needs to be more defensive against
  `ifupdown`.

  To reproduce with Packer (I confirmed this method):

  * Add necessary Azure subscription env vars from `ifupdown-bug.json`
  * `packer build ifupdown-bug.json`
  * Try to boot an instance with resulting image
  * Instance will never boot -- more specifically, networking never comes up. 
See `boot.log` for an example boot

  To reproduce manually (only a guess, I did not confirm):

  * Boot 18.04 ubuntu instance
  * Install ifupdown
  * Image the instance
  * Try to boot instance using new image
  * Instance won't boot

  I hit this with Packer, creating new images for booting instances in
  scaling groups -- `ifupdown` is brought in by `salt`. If this is
  reproducible via manual installation, there could be some backup
  images/snapshots that are unable to boot though.

  This appears to be because cloud-init network start up operations are
  broken by whatever `ifupdown` sysv/systemd scripts perform on boot.
  With `ifupdown` installed on Azure, `eth0` does not get an IP address,
  the instance never fully boots according to Azure, and it will enter
  an error state. On AWS, the instance boots, but network operations
  like SSH fail.

  The `boot.log` is from Azure. Eventually `cloud-init` gives an
  exception (see `exception.log`), but this seems like a secondary issue
  related to networking being down.

  I did try to upgrade cloud-init using nightly PPAs (version 20.1 I
  believe), but no luck. This is on Ubuntu 18.04 instances from Azure
  marketplace and AWS Canonical AMI, cloud-init version
  `19.4-33-gbb4131a2-0ubuntu1~18.04.1`.

  Related: https://github.com/Azure/WALinuxAgent/issues/1612

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

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

[Touch-packages] [Bug 1404172] Re: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory

[Daniel Richard G.]

This issue persists in lightdm 1.30.0-0ubuntu3.1 in Ubuntu focal.

I see the warnings not only for pam_kwallet.so, but also its successor
pam_kwallet5.so, as well as pam_gnome_keyring.so (which I do not have
installed). All three of these are referenced in /etc/pam.d/lightdm and
/etc/pam.d/lightdm-greeter as "optional" modules.

I attempted to eliminate the warnings by replacing the "optional"
keyword with "[success=ok module_unknown=ignore default=ignore]", but
that had no visible effect.

The entries referring to these modules need to be removed from LightDM's
PAM config files. If libpam-gnome-keyring is installed, it will already
make itself known to PAM via a pam-auth-update profile, which is the
correct approach. The libpam-kwallet5 package has no pam-auth-update
profile, but that is an issue for that package, not this one.

** Tags added: focal

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

Title:
  lightdm: PAM unable to dlopen(pam_kwallet.so):
  /lib/security/pam_kwallet.so: cannot open shared object file: No such
  file or directory

Status in One Hundred Papercuts:
  Confirmed
Status in Light Display Manager:
  Confirmed
Status in systemd:
  New
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  auth.log complaints:

  Dec 19 07:24:42 u32 lightdm: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Dec 19 07:24:42 u32 lightdm: PAM adding faulty module: pam_kwallet.so
  Dec 19 07:24:42 u32 lightdm: pam_unix(lightdm-greeter:session): session 
opened for user lightdm by (uid=0)
  Dec 19 07:24:42 u32 systemd-logind[656]: New session c1 of user lightdm.
  Dec 19 07:24:42 u32 systemd: pam_unix(systemd-user:session): session opened 
for user lightdm by (uid=0)
  Dec 19 07:24:46 u32 lightdm: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Dec 19 07:24:46 u32 lightdm: PAM adding faulty module: pam_kwallet.so
  Dec 19 07:24:46 u32 lightdm: pam_succeed_if(lightdm:auth): requirement "user 
ingroup nopasswdlogin" not met by user "oem"
  Dec 19 07:24:53 u32 lightdm: pam_unix(lightdm-greeter:session): session 
closed for user lightdm
  Dec 19 07:24:53 u32 lightdm: pam_unix(lightdm:session): session opened for 
user oem by (uid=0)

  
  As per lp:1309535 #18 comment such 'warnings' should be silenced (as they 
scared unawared users about the both needs of pam's gnome/kde)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.13.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-7.8-generic 3.18.0
  Uname: Linux 3.18.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Fri Dec 19 10:47:07 2014
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Hui Wang]

It is not easy to debug without hardware, so the best way is to report
this issue to https://github.com/thesofproject/linux/issues/new

-- 
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 HWE Next:
  New
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/hwe-next/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

[Jeff Wang]

Toshiba Satellite Radius 12 C-720  same problem ubuntu 20.04

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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

[Touch-packages] [Bug 1870316] Re: 'sudo hwclock -s' fails with 'settimeofday() failed: Invalid argument'

[Bug Watch Updater]

** Changed in: util-linux (Debian)
   Status: Confirmed => Fix Released

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

Title:
  'sudo hwclock -s' fails with 'settimeofday() failed: Invalid argument'

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux package in Debian:
  Fix Released

Bug description:
  In Focal VM.
  util-linux: 2.34-0.1ubuntu8

  $ sudo hwclock -s
  [sudo] password for focal: 
  hwclock: settimeofday() failed: Invalid argument

  Result should be syncing the time to the RTC, which until recently
  (possibly before glibc update) worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: util-linux 2.34-0.1ubuntu8
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Apr  2 11:20:45 2020
  InstallationDate: Installed on 2019-12-24 (99 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191224)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1877686] Re: Mouse lags since 20.04 update

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Mouse lags since 20.04 update

Status in xorg package in Ubuntu:
  New

Bug description:
  After installing ubuntu 20.04, I have an issue with my mouse pointer
  lagging a lot.

  It happens on my trackpad, physical mouse, wacom tablet, and
  trackpoint.

  It's only a graphical issue (ie: The underlying whatever is actually
  moving. The visible pointer just isn't).

  Other mouse moving related actions do not exhibit the same behaviour.
  Window dragging is smooth. Applications that use custom mouse
  pointers, such as krita, work smoothly.

  The issue persists both on nVidia graphics and intel integrated
  graphics.

  I am using a lenovo thinkpad p50.

  The issue persists constantly when I am using the in built laptop
  screen. However, when I connect a second monitor, it only happens
  occasionally.

  I installed ubuntu 20.04 from a usb drive, keeping my home partition
  from 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-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: Sat May  9 01:28:03 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 530 [17aa:222e]
   NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:222e]
  InstallationDate: Installed on 2020-05-08 (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 003: ID 138a:0090 Validity Sensors, Inc. VFS7500 Touch 
Fingerprint Sensor
   Bus 001 Device 002: ID 04ca:7058 Lite-On Technology Corp. Integrated Camera
   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/10p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
   |__ Port 8: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
   |__ Port 8: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
   |__ Port 9: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
  MachineType: LENOVO 20EQS2BH00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=9eb4b789-a22e-455b-8e8b-19e78e0ef3d6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET86W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS2BH00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET86W(1.59):bd08/28/2019:svnLENOVO:pn20EQS2BH00:pvrThinkPadP50:rvnLENOVO:rn20EQS2BH00:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EQS2BH00
  dmi.product.sku: LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50
  dmi.product.version: ThinkPad P50
  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/1877686/+subscriptions

-- 
Mailing list: 

[Touch-packages] [Bug 1877686] [NEW] Mouse lags since 20.04 update

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After installing ubuntu 20.04, I have an issue with my mouse pointer
lagging a lot.

It happens on my trackpad, physical mouse, wacom tablet, and trackpoint.

It's only a graphical issue (ie: The underlying whatever is actually
moving. The visible pointer just isn't).

Other mouse moving related actions do not exhibit the same behaviour.
Window dragging is smooth. Applications that use custom mouse pointers,
such as krita, work smoothly.

The issue persists both on nVidia graphics and intel integrated
graphics.

I am using a lenovo thinkpad p50.

The issue persists constantly when I am using the in built laptop
screen. However, when I connect a second monitor, it only happens
occasionally.

I installed ubuntu 20.04 from a usb drive, keeping my home partition
from 18.04.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-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: Sat May  9 01:28:03 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 530 [17aa:222e]
 NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:222e]
InstallationDate: Installed on 2020-05-08 (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 003: ID 138a:0090 Validity Sensors, Inc. VFS7500 Touch 
Fingerprint Sensor
 Bus 001 Device 002: ID 04ca:7058 Lite-On Technology Corp. Integrated Camera
 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/10p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
 |__ Port 8: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
 |__ Port 8: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
 |__ Port 9: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
MachineType: LENOVO 20EQS2BH00
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=9eb4b789-a22e-455b-8e8b-19e78e0ef3d6 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/28/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1EET86W (1.59 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20EQS2BH00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET86W(1.59):bd08/28/2019:svnLENOVO:pn20EQS2BH00:pvrThinkPadP50:rvnLENOVO:rn20EQS2BH00:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P50
dmi.product.name: 20EQS2BH00
dmi.product.sku: LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50
dmi.product.version: ThinkPad P50
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

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


** Tags: amd64 apport-bug focal ubuntu
-- 
Mouse lags since 20.04 update
https://bugs.launchpad.net/bugs/1877686
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

[bcander...@cableone.net]

Asus Gl703VD has the same problem Ubuntu 20.04

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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

[Touch-packages] [Bug 1872863] Autopkgtest regression report (kmod/24-1ubuntu3.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted kmod (24-1ubuntu3.4) for bionic have 
finished running.
The following regressions have been reported in tests triggered by the package:

chrony/3.2-4ubuntu4.4 (armhf)
linux-hwe-5.0/5.0.0-48.52~18.04.1 (arm64)
linux-aws-5.3/5.3.0-1018.20~18.04.1 (arm64)
linux/4.15.0-100.101 (arm64)


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#kmod

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

Title:
  QEMU/KVM display is garbled when booting from kernel EFI stub due to
  missing bochs-drm module

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in kmod source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1872863

  [Impact]

  A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the
  kernel EFI stub whenever EFI is enabled. This causes problems for
  QEMU/KVM virtual machines which use the VGA=std video device, as the
  efifb driver yields an unreadable garbled screen. See the attached
  image.

  The correct framebuffer driver to use in this situation is bochs-drm,
  and modprobing it from a HWE kernel fixes the issues.

  bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled
  in LP #1378648 due to bochs-drm causing problems in a PowerKVM
  machine. This problem appears to be fixed now, and bochs-drm has been
  re-enabled for Disco and up, in LP #1795857 and has been proven safe.

  This has also come up again in LP #1823152, as well as chatter on LP
  #1795857 to get this enabled on Bionic.

  The customer which is experiencing this issue cannot switch to VGA=qxl
  as a workaround, and must use VGA=std, hence I suggest we re-enable
  bochs-drm for Bionic.

  [Fix]

  I noticed on Focal, if you boot, the framebuffer is initially efifb:

  [ 0.603716] efifb: probing for efifb
  [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k
  [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1
  [ 0.603736] efifb: scrolling: redraw
  [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
  [ 0.604462] Console: switching to colour frame buffer device 100x37
  [ 0.605829] fb0: EFI VGA frame buffer device

  This soon changes to bochs-drm about a second later:

  [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
0: 0xc000 -> 0xc0ff
  [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
2: 0xc1c8c000 -> 0xc1c8cfff
  [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100)
  [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA
  [ 0.939085] Console: switching to colour dummy device 80x25
  [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console
  [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5.
  [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000.
  [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized
  [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB
  [ 0.942081] [TTM] Initializing pool allocator
  [ 0.942089] [TTM] Initializing DMA pool allocator
  [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 
GB/10.0 GiB)
  [ 0.944019] [drm] Found EDID data blob.
  [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on 
minor 0
  [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device
  [ 0.947712] Console: switching to colour frame buffer device 128x48

  On bionic, the framebuffer never changes from efifb, since the bochs-
  drm kernel module is not built, and it is also present on the module
  banlist in /etc/modprobe.d/blacklist-framebuffer.conf

  bochs-drm needs to be enabled to be built in the kernel config, and
  removed from the module blacklist in kmod.

  [Testcase]

  Create a new QEMU/KVM virtual machine, I used virt-manager. Before you
  install the OS, check the box to modify settings before install. In
  the "Overview" tab, enable EFI by setting the firmware to "UEFI
  x86_64: /usr/share/OVMF/OVMF_CODE.secboot.fd".

  Set the video device to qxl while you install Bionic. Once the install
  is done, reboot, do a "apt update" and "apt upgrade", to ensure you
  have grub2 2.02-2ubuntu8.15 installed.

  Shut the VM down, and set the video device to VGA. Or VGA=std if you
  use the QEMU command line.

  Start the VM up, and the screen will be garbled. See attached picture.

  If you install my test packages, which are available here:

  

[Touch-packages] [Bug 1871185] Re: urls in ubuntu-bug's dialog not really clickable

[Brian Murray]

** Summary changed:

- urls in ubuntu-bugs dialog not really clickable
+ urls in ubuntu-bug's dialog not really clickable

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

Title:
  urls in ubuntu-bug's dialog not really clickable

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Triaged

Bug description:
  when ubuntu-bug report suggests filing a bug report directly in
  launchpad for snap packages, the displayed url is clickable but the
  url stops at the first + symbol. see attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8.8
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CrashReports: 640:1000:124:8919925:2020-03-29 20:16:13.456640958 
+0200:2020-03-29 20:16:14.456640958 
+0200:/var/crash/_usr_bin_python3.7.1000.crash
  CurrentDesktop: XFCE
  Date: Mon Apr  6 19:50:16 2020
  InstallationDate: Installed on 2020-03-18 (18 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1871176] Re: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1

[Jeffery To]

I got this error after a few steps:

* After upgrading from eoan to focal and rebooting, I was dropped into
the initramfs shell. Exiting from the shell, I see the error message
"/dev/mapper/ubuntu--vg-root does not exist".

* After some searching online, I reboot using my previous kernel and
reach the desktop.

* I open Synaptic and see that lvm2 was removed. When I try to install
it, I get the error in this issue.

After some more searching online, I see
https://askubuntu.com/questions/1049727/every-time-i-install-or-
remove-a-package-i-get-lvm2-error/1085420 and try the suggested answer
(purge lvm2 before reinstalling) - this worked.

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

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

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  hayden@t470s:~$ sudo apt-get install gnome-boxes
  [sudo] password for hayden: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  gnome-boxes is already the newest version (3.36.2-1).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up lvm2 (2.03.07-1ubuntu1) ...
  update-initramfs: deferring update (trigger activated)
  Failed to restart lvm2-lvmpolld.service: Unit lvm2-lvmpolld.socket is masked.
  invoke-rc.d: initscript lvm2-lvmpolld, action "restart" failed.
  ● lvm2-lvmpolld.service - LVM2 poll daemon
   Loaded: loaded (/lib/systemd/system/lvm2-lvmpolld.service; static; 
vendor preset: enabled)
   Active: active (exited) since Mon 2020-04-06 09:33:50 EDT; 4h 10min ago
 Docs: man:lvmpolld(8)
Tasks: 0 (limit: 23811)
   Memory: 0B
   CGroup: /system.slice/lvm2-lvmpolld.service

  Apr 06 09:33:50 t470s systemd[1]: Starting LSB: LVM2 poll daemon...
  Apr 06 09:33:50 t470s systemd[1]: Started LSB: LVM2 poll daemon.
  dpkg: error processing package lvm2 (--configure):
   installed lvm2 package post-installation script subprocess returned error 
exit status 1
  Processing triggers for initramfs-tools (0.136ubuntu2) ...
  update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic
  Errors were encountered while processing:
   lvm2
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  Date: Mon Apr  6 13:38:10 2020
  ErrorMessage: installed lvm2 package post-installation script subprocess 
returned error exit status 1
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.1
  SourcePackage: lvm2
  Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed 
lvm2 package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1877675] [NEW] Workspaces broken with latest update

[Byron]

Public bug reported:

Multiple workspaces broke with latest gnome config update.

Unable to create, or go to different workspaces.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
.proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09: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
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May  8 17:05:52 2020
DistUpgraded: 2020-04-27 21:42:55,589 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 440.64, 5.4.0-28-generic, x86_64: installed
 nvidia, 440.64, 5.4.0-29-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1660 Ti] 
[1458:3fbe]
InstallationDate: Installed on 2018-07-01 (677 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6998b6fb-9ba7-4ce9-a023-b36dab34d51a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-28 (10 days ago)
dmi.bios.date: 11/27/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F50
dmi.board.asset.tag: Default string
dmi.board.name: X470 AORUS ULTRA GAMING-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.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: X470 AORUS ULTRA GAMING
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

Title:
  Workspaces broken with latest update

Status in xorg package in Ubuntu:
  New

Bug description:
  Multiple workspaces broke with latest gnome config update.

  Unable to create, or go to different workspaces.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09: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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri 

[Touch-packages] [Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

[Gaetano Canepa]

On my ASUS Rog GL703VD-GC028T Notebook, I was able to use both microphone and 
sound adding the line
options snd-hda-intel model=laptop-dmic,headset-mic,auto
to /etc/modprobe.d

and modifing the line
#load-module module-alsa-sink control=xxx
with
load-module module-alsa-sink control=PCM
and modifying the line 
load-module module-udev-detect
with
load-module module-udev-detect ignore_dB=1
to /etc/pulse/default.pa file

I'm not sure all the modifications are essential. Check the ubuntu sound 
setting for output
Built-in Audio

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1877670] [NEW] Display Freezes and frequently mouse cursor disappears.

[Myra Bandikalla]

Public bug reported:

Display Freezes and frequently mouse cursor disappears. After restart
mouse cursor comes back again.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-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 May  9 02:25:55 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA 
controller])
   Subsystem: Acer Incorporated [ALI] Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1025:1022]
InstallationDate: Installed on 2020-04-23 (14 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 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 2386:0401 Raydium Corporation Raydium Touch System
 Bus 001 Device 002: ID 04f2:b520 Chicony Electronics Co., Ltd HD WebCam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire R3-131T
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-29-generic 
root=UUID=5b613349-680c-466c-b069-960c9c12c462 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.17
dmi.board.name: Aspire R3-131T
dmi.board.vendor: Acer
dmi.board.version: V1.17
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.17
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireR3-131T:pvrV1.17:rvnAcer:rnAspireR3-131T:rvrV1.17:cvnAcer:ct10:cvrV1.17:
dmi.product.family: BSW
dmi.product.name: Aspire R3-131T
dmi.product.sku: Aspire R3-131T_1022_1.17
dmi.product.version: V1.17
dmi.sys.vendor: Acer
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

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

Title:
  Display Freezes and frequently mouse cursor disappears.

Status in xorg package in Ubuntu:
  New

Bug description:
  Display Freezes and frequently mouse cursor disappears. After restart
  mouse cursor comes back again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-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 May  9 02:25:55 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1025:1022]
  InstallationDate: Installed on 2020-04-23 (14 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 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 2386:0401 Raydium Corporation Raydium Touch System
   Bus 001 Device 002: ID 04f2:b520 Chicony Electronics Co., Ltd HD WebCam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire R3-131T
  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-29-generic 
root=UUID=5b613349-680c-466c-b069-960c9c12c462 ro quiet splash vt.handoff=7
  

[Touch-packages] [Bug 1877655] Re: Synaptic Trackpad works until actually logged into Xorg desktop

[Tony Harris]

I have no idea what sub group/package this belongs in.  I know it
affects Gnome and KDE on Xorg.  I don't know if GDM (or whatever now
handles the login process) does differently from the full gnome that
allows the trackpad to at least partially work (movement, but not button
clicks)

** Description changed:

  I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery
  dock.  PopOS 20.04 fully updated.  I have experienced this bug on stock
  Ubuntu 20.04 as well as Kubuntu 20.04.
  
-   When at the login page, the trackpad and keyboard operate as they
+   When at the login page, the trackpad and keyboard operate as they
  should.  Once the login process is complete and the desktop is
  displayed, the keyboard still works as expected but the trackpad no
  longer controls the pointer.  The touch display still functions as
  expected but the trackpad on the keyboard dock doesn't work.
  
  The attached document is my device list, here is the evtest:
  
  Input driver version is 1.0.1
  Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111
  Input device name: "Synaptics T Pad V 01.31 Touchpad"
  Supported events:
-   Event type 0 (EV_SYN)
-   Event type 1 (EV_KEY)
- Event code 272 (BTN_LEFT)
- Event code 325 (BTN_TOOL_FINGER)
- Event code 330 (BTN_TOUCH)
- Event code 333 (BTN_TOOL_DOUBLETAP)
- Event code 334 (BTN_TOOL_TRIPLETAP)
-   Event type 3 (EV_ABS)
- Event code 0 (ABS_X)
-   Value483
-   Min0
-   Max 1056
-   Resolution  12
- Event code 1 (ABS_Y)
-   Value266
-   Min0
-   Max  516
-   Resolution  12
- Event code 47 (ABS_MT_SLOT)
-   Value  0
-   Min0
-   Max2
- Event code 53 (ABS_MT_POSITION_X)
-   Value  0
-   Min0
-   Max 1056
-   Resolution  12
- Event code 54 (ABS_MT_POSITION_Y)
-   Value  0
-   Min0
-   Max  516
-   Resolution  12
- Event code 55 (ABS_MT_TOOL_TYPE)
-   Value  0
-   Min0
-   Max2
- Event code 57 (ABS_MT_TRACKING_ID)
-   Value  0
-   Min0
-   Max65535
-   Event type 4 (EV_MSC)
- Event code 5 (MSC_TIMESTAMP)
+   Event type 0 (EV_SYN)
+   Event type 1 (EV_KEY)
+ Event code 272 (BTN_LEFT)
+ Event code 325 (BTN_TOOL_FINGER)
+ Event code 330 (BTN_TOUCH)
+ Event code 333 (BTN_TOOL_DOUBLETAP)
+ Event code 334 (BTN_TOOL_TRIPLETAP)
+   Event type 3 (EV_ABS)
+ Event code 0 (ABS_X)
+   Value483
+   Min0
+   Max 1056
+   Resolution  12
+ Event code 1 (ABS_Y)
+   Value266
+   Min0
+   Max  516
+   Resolution  12
+ Event code 47 (ABS_MT_SLOT)
+   Value  0
+   Min0
+   Max2
+ Event code 53 (ABS_MT_POSITION_X)
+   Value  0
+   Min0
+   Max 1056
+   Resolution  12
+ Event code 54 (ABS_MT_POSITION_Y)
+   Value  0
+   Min0
+   Max  516
+   Resolution  12
+ Event code 55 (ABS_MT_TOOL_TYPE)
+   Value  0
+   Min0
+   Max2
+ Event code 57 (ABS_MT_TRACKING_ID)
+   Value  0
+   Min0
+   Max65535
+   Event type 4 (EV_MSC)
+ Event code 5 (MSC_TIMESTAMP)
  Properties:
-   Property type 0 (INPUT_PROP_POINTER)
-   Property type 2 (INPUT_PROP_BUTTONPAD)
+   Property type 0 (INPUT_PROP_POINTER)
+   Property type 2 (INPUT_PROP_BUTTONPAD)
  Testing ... (interrupt to exit)
  
- 
- I did try to remove xserver-xorg-input-synaptics, but it is not installed on 
20.04.
+ I did try to remove xserver-xorg-input-synaptics, but it is not
+ installed on 20.04.
  
  There is still an issue with Wayland and the trackpad, but it's
  different than Xorg so the problem may be in how Xorg is processing the
  trackpad (I honestly don't know) - in Wayland, it will work until I
  attempt to run the sofware center.

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

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

Title:
  Synaptic Trackpad works until actually logged into Xorg desktop

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery
  dock.  PopOS 20.04 fully updated.  I have experienced this bug on
  stock Ubuntu 20.04 as well as Kubuntu 20.04.

    When at the login page, the trackpad and keyboard operate as they
  should.  Once the login process is complete and the desktop is
  displayed, the keyboard still works as expected but the trackpad no
  longer controls the pointer.  The touch display still functions as
  expected but the trackpad on the keyboard dock doesn't work.

  The attached document is my device list, here is the evtest:

  

[Touch-packages] [Bug 1875697] Re: drop fix-ldap-distribution.patch?

[Andreas Hasenack]

I patched the patch, ugh, but I'll think of a nice way to set this
dynamically before uploading. I'm dropping a lot of delta in the 2.4.50
merge :)

-- 
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:
  In Progress
Status in openldap source package in Focal:
  Won't Fix

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 1877655] [NEW] Synaptic Trackpad works until actually logged into Xorg desktop

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery
dock.  PopOS 20.04 fully updated.  I have experienced this bug on stock
Ubuntu 20.04 as well as Kubuntu 20.04.

  When at the login page, the trackpad and keyboard operate as they
should.  Once the login process is complete and the desktop is
displayed, the keyboard still works as expected but the trackpad no
longer controls the pointer.  The touch display still functions as
expected but the trackpad on the keyboard dock doesn't work.

The attached document is my device list, here is the evtest:

Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111
Input device name: "Synaptics T Pad V 01.31 Touchpad"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
Event code 272 (BTN_LEFT)
Event code 325 (BTN_TOOL_FINGER)
Event code 330 (BTN_TOUCH)
Event code 333 (BTN_TOOL_DOUBLETAP)
Event code 334 (BTN_TOOL_TRIPLETAP)
  Event type 3 (EV_ABS)
Event code 0 (ABS_X)
  Value483
  Min0
  Max 1056
  Resolution  12
Event code 1 (ABS_Y)
  Value266
  Min0
  Max  516
  Resolution  12
Event code 47 (ABS_MT_SLOT)
  Value  0
  Min0
  Max2
Event code 53 (ABS_MT_POSITION_X)
  Value  0
  Min0
  Max 1056
  Resolution  12
Event code 54 (ABS_MT_POSITION_Y)
  Value  0
  Min0
  Max  516
  Resolution  12
Event code 55 (ABS_MT_TOOL_TYPE)
  Value  0
  Min0
  Max2
Event code 57 (ABS_MT_TRACKING_ID)
  Value  0
  Min0
  Max65535
  Event type 4 (EV_MSC)
Event code 5 (MSC_TIMESTAMP)
Properties:
  Property type 0 (INPUT_PROP_POINTER)
  Property type 2 (INPUT_PROP_BUTTONPAD)
Testing ... (interrupt to exit)

I did try to remove xserver-xorg-input-synaptics, but it is not
installed on 20.04.

There is still an issue with Wayland and the trackpad, but it's
different than Xorg so the problem may be in how Xorg is processing the
trackpad (I honestly don't know) - in Wayland, it will work until I
attempt to run the sofware center.

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


** Tags: bot-comment
-- 
Synaptic Trackpad works until actually logged into Xorg desktop
https://bugs.launchpad.net/bugs/1877655
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1873658] Re: Deb Files are not associated with an application that manages packages

[Launchpad Bug Tracker]

This bug was fixed in the package desktop-file-utils - 0.24-1ubuntu4

---
desktop-file-utils (0.24-1ubuntu4) groovy; urgency=medium

  * debian/defaults.list
- Updated for the transition to snap-store (LP: #1873658)

 -- Ken VanDine   Fri, 08 May 2020 10:01:44
-0400

** Changed in: desktop-file-utils (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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:
  Fix Released
Status in gdebi package in Ubuntu:
  Invalid
Status in desktop-file-utils source package in Focal:
  Fix Committed
Status in gdebi source package in Focal:
  Invalid

Bug description:
  [Impact]

   * When a deb is downloaded the default handler is not capable of
  installing on 20.04.

  [Test Case]

   We should perform this test on Ubuntu 20.04 as well as some flavors
  to ensure we do not regress.

   * Download any deb in firefox, double click on the downloaded file
 - On Ubuntu this should open "Ubuntu Software"
 - On flavors it should open whatever their default app for handling debs is

  [Regression Potential]

   * For Ubuntu, very low, rarely would a user expect to open a deb with
  file-roller

   * Other flavors of ubuntu are overriding this default and should not
  be affected.  We do need to test this on other flavors to ensure their
  defaults are still honored.

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 1875697] Re: drop fix-ldap-distribution.patch?

[Andreas Hasenack]

I don't think this change is worth an SRU for focal, as the goal is to
drop a delta. It would also change a signature of sorts, so best not to
change that in an LTS release.

** Changed in: openldap (Ubuntu Focal)
   Status: Triaged => Won't Fix

** Changed in: openldap (Ubuntu)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

** Changed in: openldap (Ubuntu)
   Status: Triaged => In Progress

-- 
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:
  In Progress
Status in openldap source package in Focal:
  Won't Fix

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 1867375] Re: systemd-networkd: UseRoutes behavior change with introduction of UseGateway param

[Dan Streetman]

** Description changed:

  [impact]
  
  the networkd UseRoutes parameter allowed ignoring all routes provided by
  a dhcp4 server, including the route via the dhcp4-provided gateway.
  This was the behavior of networkd until recently, and in Focal the
  UseRoutes parameter does *not* prevent networkd from adding the route
  via the dhcp4-provided gateway.  This is now controlled with a new
  parameter, UseGateway.
  
  The systemd in Focal unfortunately has part of the upstream code; it no
  longer ignores the gateway route when UseRoutes=false is specified, but
  also it does not include the UseGateway parameter.
  
  Before Focal, networkd did not allow ignoring dhcpv4 routes and the
  gateway separately; the UseRoutes= parameter either used, or ignored,
  both.  This is why upstream added the UseGateway= paramter, which should
  be backported to allow control of ignoring the dhcpv4 routes and gateway
  separately.
  
  [test case]
  
  In Focal, bug 1872589 has a good test case netplan config, but a very
  quick test can be done with the networkd config:
  
  [Match]
  Name=eth0
  
  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  
  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false
  
  this results in the system incorrectly setting a route via the default
  gateway:
  
  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100
  
  Before Focal, the above test case shows "correct" behavior, but there is
  no way to ignore the dhcpv4 routes but use the dhcpv4 gateway.  This
  pre-Focal, the test case would be to use the UseGateway= parameter,
  e.g.:
  
  [Match]
  Name=eth0
  
  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  
  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false
  UseGateway=true
  
  which *should* result in the default gateway being configured:
  
  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100
  
  [regression potential]
  
  Any regression would likely involve incorrect setting, or ignoring, of
  dhcpv4-provided routes, and/or incorrect setting, or ignoring, of the
  dhcpv4-provided gateway.
  
  [scope]
  
  This is fixed by these upstream PRs:
  https://github.com/systemd/systemd/pull/15443
  https://github.com/systemd/systemd/pull/15136
  https://github.com/systemd/systemd/pull/14983
  
  Parts of all those PRs are required in Focal, Eoan, and Bionic.
  
  I am not fixing this for Xenial, at this time.
  
+ For Debian, I opened this MR:
+ https://salsa.debian.org/systemd-team/systemd/-/merge_requests/92
+ 
+ For Groovy, I opened this MR:
+ 
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/383661
+ 
  [other info]
  
  to properly support separation of 'routes' and 'gateways' received via
  dhcp4, SRU releases should also support the UseGateway parameter, which
  is what this bug was originally opened requesting.
  
  [original description]
  
  requesting backport of PR https://github.com/systemd/systemd/pull/14983 which 
fixes the issue described in
  https://github.com/systemd/systemd/issues/14982 to 18.04 (bionic)

** Also affects: systemd (Ubuntu Groovy)
   Importance: High
 Assignee: Dan Streetman (ddstreet)
   Status: In Progress

** Also affects: netplan.io (Ubuntu Groovy)
   Importance: Undecided
   Status: New

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

Title:
  systemd-networkd: UseRoutes behavior change with introduction of
  UseGateway param

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in netplan.io source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in netplan.io source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  In Progress
Status in netplan.io source package in Focal:
  New
Status in systemd source package in Focal:
  In Progress
Status in netplan.io source package in Groovy:
  New
Status in systemd source package in Groovy:
  In Progress

Bug description:
  [impact]

  the networkd UseRoutes parameter allowed ignoring all routes provided
  by a dhcp4 server, including the route via the dhcp4-provided gateway.
  This was the behavior of networkd until recently, and in Focal the
  UseRoutes parameter does *not* prevent networkd from adding the route
  via the dhcp4-provided gateway.  This is now controlled with a new
  parameter, UseGateway.

  The systemd in Focal unfortunately has part of the upstream code; it
  no longer ignores the gateway route when 

[Touch-packages] [Bug 1867375] Re: systemd-networkd: UseRoutes behavior change with introduction of UseGateway param

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/383661

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

Title:
  systemd-networkd: UseRoutes behavior change with introduction of
  UseGateway param

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in netplan.io source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in netplan.io source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  In Progress
Status in netplan.io source package in Focal:
  New
Status in systemd source package in Focal:
  In Progress
Status in netplan.io source package in Groovy:
  New
Status in systemd source package in Groovy:
  In Progress

Bug description:
  [impact]

  the networkd UseRoutes parameter allowed ignoring all routes provided
  by a dhcp4 server, including the route via the dhcp4-provided gateway.
  This was the behavior of networkd until recently, and in Focal the
  UseRoutes parameter does *not* prevent networkd from adding the route
  via the dhcp4-provided gateway.  This is now controlled with a new
  parameter, UseGateway.

  The systemd in Focal unfortunately has part of the upstream code; it
  no longer ignores the gateway route when UseRoutes=false is specified,
  but also it does not include the UseGateway parameter.

  Before Focal, networkd did not allow ignoring dhcpv4 routes and the
  gateway separately; the UseRoutes= parameter either used, or ignored,
  both.  This is why upstream added the UseGateway= paramter, which
  should be backported to allow control of ignoring the dhcpv4 routes
  and gateway separately.

  [test case]

  In Focal, bug 1872589 has a good test case netplan config, but a very
  quick test can be done with the networkd config:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false

  this results in the system incorrectly setting a route via the default
  gateway:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  Before Focal, the above test case shows "correct" behavior, but there
  is no way to ignore the dhcpv4 routes but use the dhcpv4 gateway.
  This pre-Focal, the test case would be to use the UseGateway=
  parameter, e.g.:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false
  UseGateway=true

  which *should* result in the default gateway being configured:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  [regression potential]

  Any regression would likely involve incorrect setting, or ignoring, of
  dhcpv4-provided routes, and/or incorrect setting, or ignoring, of the
  dhcpv4-provided gateway.

  [scope]

  This is fixed by these upstream PRs:
  https://github.com/systemd/systemd/pull/15443
  https://github.com/systemd/systemd/pull/15136
  https://github.com/systemd/systemd/pull/14983

  Parts of all those PRs are required in Focal, Eoan, and Bionic.

  I am not fixing this for Xenial, at this time.

  For Debian, I opened this MR:
  https://salsa.debian.org/systemd-team/systemd/-/merge_requests/92

  For Groovy, I opened this MR:
  
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/383661

  [other info]

  to properly support separation of 'routes' and 'gateways' received via
  dhcp4, SRU releases should also support the UseGateway parameter,
  which is what this bug was originally opened requesting.

  [original description]

  requesting backport of PR https://github.com/systemd/systemd/pull/14983 which 
fixes the issue described in
  https://github.com/systemd/systemd/issues/14982 to 18.04 (bionic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1867375/+subscriptions

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

[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

[Jeff Nappi]

Great to see traction on this, thank you for all your efforts Daniel!
And to everyone else, this is a far more complex problem than you can
imagine  However it can and will be solved :)

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~touch-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] Re: drop fix-ldap-distribution.patch?

[Andreas Hasenack]

That comes from debian/patches/set-maintainer-name

-- 
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:
  Triaged
Status in openldap source package in Focal:
  Triaged

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 1877661] Re: package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 2

Status in lvm2 package in Ubuntu:
  New

Bug description:
  This error came when I do a fresh install.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lvm2 2.02.133-1ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-45-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  CasperVersion: 1.376.2
  Date: Fri May  8 21:09:09 2020
  DuplicateSignature:
   package:lvm2:2.02.133-1ubuntu10
   Removing lvm2 (2.02.133-1ubuntu10) ...
   dpkg (subprocess): unable to execute installed pre-removal script 
(/var/lib/dpkg/info/lvm2.prerm): Input/output error
   dpkg: error processing package lvm2 (--purge):
subprocess installed pre-removal script returned error exit status 2
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 2
  LiveMediaBuild: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29ubuntu0.1
  SourcePackage: lvm2
  Title: package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1875697] Re: drop fix-ldap-distribution.patch?

[Ryan Tandy]

On Fri, May 08, 2020 at 07:57:38PM -, Andreas Hasenack wrote:
>But looks like the email is wrong, we should be showing ubuntu-devel@ 
>there instead of the debian maintainers list.

I'm fine with receiving mail from Ubuntu users as well. (in IRC I'm 
usually supporting at least as many Ubuntu users as Debian users.) But 
feel free to patch this in your build, or send me a patch to pick up 
Maintainer dynamically from the control file (or based on dpkg-vendor or 
whatever).

-- 
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:
  Triaged
Status in openldap source package in Focal:
  Triaged

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 1877661] [NEW] package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2

[Pradeep]

Public bug reported:

This error came when I do a fresh install.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: lvm2 2.02.133-1ubuntu10
ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-45-generic i686
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
CasperVersion: 1.376.2
Date: Fri May  8 21:09:09 2020
DuplicateSignature:
 package:lvm2:2.02.133-1ubuntu10
 Removing lvm2 (2.02.133-1ubuntu10) ...
 dpkg (subprocess): unable to execute installed pre-removal script 
(/var/lib/dpkg/info/lvm2.prerm): Input/output error
 dpkg: error processing package lvm2 (--purge):
  subprocess installed pre-removal script returned error exit status 2
ErrorMessage: subprocess installed pre-removal script returned error exit 
status 2
LiveMediaBuild: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.29ubuntu0.1
SourcePackage: lvm2
Title: package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 2

Status in lvm2 package in Ubuntu:
  New

Bug description:
  This error came when I do a fresh install.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lvm2 2.02.133-1ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-45-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  CasperVersion: 1.376.2
  Date: Fri May  8 21:09:09 2020
  DuplicateSignature:
   package:lvm2:2.02.133-1ubuntu10
   Removing lvm2 (2.02.133-1ubuntu10) ...
   dpkg (subprocess): unable to execute installed pre-removal script 
(/var/lib/dpkg/info/lvm2.prerm): Input/output error
   dpkg: error processing package lvm2 (--purge):
subprocess installed pre-removal script returned error exit status 2
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 2
  LiveMediaBuild: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29ubuntu0.1
  SourcePackage: lvm2
  Title: package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1876693] Re: [SRU] New stable release 1.64.1

[Brian Murray]

Hello Iain, or anyone else affected,

Accepted gobject-introspection into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gobject-introspection/1.64.1-1~ubuntu20.04.1 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: gobject-introspection (Ubuntu Focal)
   Status: In Progress => 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 gobject-introspection in
Ubuntu.
https://bugs.launchpad.net/bugs/1876693

Title:
  [SRU] New stable release 1.64.1

Status in gobject-introspection package in Ubuntu:
  Fix Released
Status in gobject-introspection source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  GNOME upstream have released a new stable version of gobject-
  introspection.

  Changes:

  1.64.1 - 2020-04-05
  ---

  * Replace calls to deprecated xml.etree.cElementTree removed in Python 3.9 
:mr:`202` (:user:`Stephen Gallagher `)
  * gimarshallingtests: Use g_assert_cmpfloat_with_epsilon. Fixes tests on some 
architectures :mr:`200` (:user:`Iain Lane `)

  [ QA ]

  GNOME has a micro release exception that covers this package.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  So we don't need to verify the fixes explicitly.

  Do this:

- Install the update, smoke test some of the reverse depends (apt rdepends 
libgirepository-1.0-1 and more importantly the indirect rdepends via python3-gi)
- Run "reverse-depends -b src:gobject-introspection" and test rebuild a few 
of them

  [ Regression potential ]

  g-i being broken will break pretty much the whole desktop, but you'd
  know that quite fast.

  The .py changes, if they're wrong or bad, could break the build of r
  -build-deps.

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

-- 
Mailing list: https://launchpad.net/~touch-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] Re: drop fix-ldap-distribution.patch?

[Andreas Hasenack]

I think dropping this delta is fine, as the "ubuntu" name will still
show as long as there is a delta. But looks like the email is wrong, we
should be showing ubuntu-devel@ there instead of the debian maintainers
list.

-- 
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:
  Triaged
Status in openldap source package in Focal:
  Triaged

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 1877473] Re: Upgrading from 18.04 to 20.04 encrypted installation with LUKS and LVM makes it unbootable without manual intervention

[Serhiy Zahoriya]

Can't. /var/log is in tmpfs and I didn't save them unfortunately. Feel
free to close this as a duplicate of
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/1874381

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

Title:
  Upgrading from 18.04 to 20.04 encrypted installation with LUKS and LVM
  makes it unbootable without manual intervention

Status in lvm2 package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  Incomplete

Bug description:
  Volume Group metadata had to be upgraded manually with

  vgck --updatemetadata yourvgname

  The VG name was somehow changed from lvm-name to just name and I had
  to edit /etc/crypttab and update-initramfs -u -k all

  Also cryptsetup-initramfs package was deleted for some reason, had to
  re-install it in chroot. Maybe it happened because I have disabled
  installing recommended and suggested packages or maybe because none of
  *buntu-desktop packages are installed on my system. Not sure if I have
  to report it as a separate problem, please advise.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri May  8 01:35:04 2020
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1843007] Re: namespace: make MountFlags=shared work again

[Dan Streetman]

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

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

Title:
  namespace: make MountFlags=shared work again

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Invalid

Bug description:
  Systemd in Bionic fails to handle MountFlags correctly. Would you mind
  to include
  
https://github.com/systemd/systemd/commit/37ed15d7edaf59a1fc7c9e3552cd93a83f3814ef
  into Bionic? This bug seriously affects Docker > 18.6, see the Docker
  release notes for 18.09.1 (https://docs.docker.com/engine/release-
  notes/#18091).

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

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

[Touch-packages] [Bug 1877633] Re: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64

[Jamie Strandboge]

** Description changed:

- This was reported via the snapcraft forum:
+ This was reported via the snapcraft forum[1]:
  
  On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2
  
  $ lsb_release -d
  Description:  Ubuntu 18.04.4 LTS
  $ scmp_sys_resolver -a aarch64 163
  getrlimit
  $ scmp_sys_resolver -a aarch64 getrlimit
  163
  
  focal amd64, libseccomp 2.4.3-1ubuntu1 -- *__BROKEN__*
  
  $ lsb_release -d
  Description:  Ubuntu 20.04 LTS
  $ scmp_sys_resolver -a aarch64 163
  UNKNOWN
  $ scmp_sys_resolver -a aarch64 getrlimit
  -10180
+ 
+ [1]https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal-
+ arm64/17237/8

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

Title:
  libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the
  getrlimit syscall on arm64

Status in libseccomp package in Ubuntu:
  Confirmed
Status in libseccomp source package in Focal:
  Confirmed
Status in libseccomp source package in Groovy:
  Confirmed

Bug description:
  This was reported via the snapcraft forum[1]:

  On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2

  $ lsb_release -d
  Description:  Ubuntu 18.04.4 LTS
  $ scmp_sys_resolver -a aarch64 163
  getrlimit
  $ scmp_sys_resolver -a aarch64 getrlimit
  163

  focal amd64, libseccomp 2.4.3-1ubuntu1 -- *__BROKEN__*

  $ lsb_release -d
  Description:  Ubuntu 20.04 LTS
  $ scmp_sys_resolver -a aarch64 163
  UNKNOWN
  $ scmp_sys_resolver -a aarch64 getrlimit
  -10180

  [1]https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal-
  arm64/17237/8

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

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

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

[Wittawat Jitkrittum]

Trying more things here. I changed Hdmi.conf back to my original file.
The system boots with your v5 kernel.

http://alsa-project.org/db/?f=441f6bdb49c44e8ce84cee41ef1b6917544febcb

Still no sound. Seeing Dummy Output.

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874698/+attachment/5368592/+files/dmesg

-- 
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 HWE Next:
  New
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/hwe-next/+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 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem

[Wittawat Jitkrittum]

Trying more things here. I changed Hdmi.conf back to my original file.
The system boots with your v5 kernel.

http://alsa-project.org/db/?f=441f6bdb49c44e8ce84cee41ef1b6917544febcb

Still no sound. Seeing Dummy Output.

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874698/+attachment/5368591/+files/dmesg

-- 
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 HWE Next:
  New
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/hwe-next/+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 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem

[Wittawat Jitkrittum]

Thanks for this. I tried it with your Hdmi.conf from v4. I could boot up
to the login screen. After seeing the login GUI screen for a few
seconds, the system just freezes (no longer responds to mouse and
keyboard input). Attaching dmesg.0. I guess there is some file system
check or something else that gets executed at that moment and disrupts
the whole boot sequence.

** Attachment added: "dmesg.0"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874698/+attachment/5368568/+files/dmesg.0

-- 
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 HWE Next:
  New
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/hwe-next/+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 1877648] [NEW] Laptop video problem

[Karim BAKKAL]

Public bug reported:

After a fresh install, the system goes to sleep mode in place of showing
logon display. After waking up, the screen stay black but login action
and shutdown button seems to work so there's no video on laptop screen
(LVDS-1).

When i connect an DVI-I monitor before starting, the computer doesn't go
in sleep mode at startup. I can see the logon on external monitor but
there nothing on internal monitor.

I can use the two monitor when i use those commands:
xrandr --output DVI-I-1 --mode 1400x1050 --primary
xrandr --output LVDS-1 --mode 1440x900 --right-of DVI-I-1 --crtc 0

LVDS-1 is reported as "unknown connection" in place of "connected" or
"disconnected".

Xorg0.log report that the internal monitor is disconnected :
[31.856] (II) NOUVEAU(0): Output VGA-1 disconnected
[31.856] (II) NOUVEAU(0): Output LVDS-1 disconnected
[31.856] (II) NOUVEAU(0): Output DVI-I-1 connected
[31.856] (II) NOUVEAU(0): Output TV-1 disconnected

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
Uname: Linux 4.15.0-99-generic i686
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: i386
CompositorRunning: None
CurrentDesktop: XFCE
Date: Fri May  8 20:28:43 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation NV41M [GeForce Go 6800] [10de:00c8] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: Fujitsu Technology Solutions NV41M [GeForce Go 6800] [1734:107c]
InstallationDate: Installed on 2020-04-17 (21 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426)
MachineType: FUJITSU SIEMENS Amilo M3438 Series
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic 
root=UUID=f910d7c1-f499-455a-ade2-472c22149dcd ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/05/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.10C
dmi.board.name: P71EN0
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.10C:bd10/05/2005:svnFUJITSUSIEMENS:pnAmiloM3438Series:pvr:rvn:rnP71EN0:rvr:cvnFUJITSUSIEMENS:ct10:cvr:
dmi.product.name: Amilo M3438 Series
dmi.sys.vendor: FUJITSU SIEMENS
version.compiz: compiz N/A
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 2:1.19.6-1ubuntu4.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
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

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


** Tags: apport-bug bionic i386 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/1877648

Title:
  Laptop video problem

Status in xorg package in Ubuntu:
  New

Bug description:
  After a fresh install, the system goes to sleep mode in place of
  showing logon display. After waking up, the screen stay black but
  login action and shutdown button seems to work so there's no video on
  laptop screen (LVDS-1).

  When i connect an DVI-I monitor before starting, the computer doesn't
  go in sleep mode at startup. I can see the logon on external monitor
  but there nothing on internal monitor.

  I can use the two monitor when i use those commands:
  xrandr --output DVI-I-1 --mode 1400x1050 --primary
  xrandr --output LVDS-1 --mode 1440x900 --right-of DVI-I-1 --crtc 0

  LVDS-1 is reported as "unknown connection" in place of "connected" or
  "disconnected".

  Xorg0.log report that the internal monitor is disconnected :
  [31.856] (II) NOUVEAU(0): Output VGA-1 disconnected
  [31.856] (II) NOUVEAU(0): Output LVDS-1 disconnected
  [31.856] (II) NOUVEAU(0): Output DVI-I-1 connected
  [31.856] (II) NOUVEAU(0): Output TV-1 disconnected

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  Uname: Linux 4.15.0-99-generic i686
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Fri May  8 20:28:43 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation NV41M [GeForce Go 6800] [10de:00c8] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Fujitsu Technology Solutions NV41M [GeForce Go 6800] [1734:107c]
  InstallationDate: Installed on 2020-04-17 (21 days ago)
  InstallationMedia: Xubuntu 

[Touch-packages] [Bug 1877640] Re: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones.

[Vitaly Syromyatnikov]

** Tags added: kernel-sound

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

Title:
  [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack
  headphones.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04.4 LTS dual boot with Windows 10.
  On Windows all is fine. On Ubuntu i have sound for speakers, but no sound at 
all for 3.5mm jack headphones. Tried using latest kernel versions for 4.*, 5.*, 
tried even 5.7-rc4.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.6.11-050611-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corsarstl   1728 F pulseaudio
   /dev/snd/pcmC0D0p:   corsarstl   1728 F...m pulseaudio
   /dev/snd/controlC1:  corsarstl   1728 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  8 20:25:27 2020
  InstallationDate: Installed on 2020-05-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1227 F pulseaudio
corsarstl   1728 F pulseaudio
   /dev/snd/controlC1:  gdm1227 F pulseaudio
corsarstl   1728 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294, Speaker, Internal] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GU502GV.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GU502GV
  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.:bvrGU502GV.307:bd02/15/2020:svnASUSTeKCOMPUTERINC.:pnZephyrusMGU502GV_GU502GV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU502GV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: Zephyrus M
  dmi.product.name: Zephyrus M GU502GV_GU502GV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1877640] [NEW] [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones.

[Vitaly Syromyatnikov]

Public bug reported:

Ubuntu 18.04.4 LTS dual boot with Windows 10.
On Windows all is fine. On Ubuntu i have sound for speakers, but no sound at 
all for 3.5mm jack headphones. Tried using latest kernel versions for 4.*, 5.*, 
tried even 5.7-rc4.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 5.6.11-050611-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  corsarstl   1728 F pulseaudio
 /dev/snd/pcmC0D0p:   corsarstl   1728 F...m pulseaudio
 /dev/snd/controlC1:  corsarstl   1728 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri May  8 20:25:27 2020
InstallationDate: Installed on 2020-05-07 (0 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1227 F pulseaudio
  corsarstl   1728 F pulseaudio
 /dev/snd/controlC1:  gdm1227 F pulseaudio
  corsarstl   1728 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294, Speaker, Internal] No sound 
at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/15/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GU502GV.307
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GU502GV
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.:bvrGU502GV.307:bd02/15/2020:svnASUSTeKCOMPUTERINC.:pnZephyrusMGU502GV_GU502GV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU502GV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: Zephyrus M
dmi.product.name: Zephyrus M GU502GV_GU502GV
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug bionic

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

Title:
  [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack
  headphones.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04.4 LTS dual boot with Windows 10.
  On Windows all is fine. On Ubuntu i have sound for speakers, but no sound at 
all for 3.5mm jack headphones. Tried using latest kernel versions for 4.*, 5.*, 
tried even 5.7-rc4.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.6.11-050611-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corsarstl   1728 F pulseaudio
   /dev/snd/pcmC0D0p:   corsarstl   1728 F...m pulseaudio
   /dev/snd/controlC1:  corsarstl   1728 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  8 20:25:27 2020
  InstallationDate: Installed on 2020-05-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1227 F pulseaudio
corsarstl   1728 F pulseaudio
   /dev/snd/controlC1:  gdm1227 F pulseaudio
corsarstl   1728 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294, Speaker, Internal] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GU502GV.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GU502GV
  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.:bvrGU502GV.307:bd02/15/2020:svnASUSTeKCOMPUTERINC.:pnZephyrusMGU502GV_GU502GV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU502GV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: Zephyrus M
  

[Touch-packages] [Bug 1877473] Re: Upgrading from 18.04 to 20.04 encrypted installation with LUKS and LVM makes it unbootable without manual intervention

[Brian Murray]

Please include the log files from your upgrade, which can be found in
'/var/log/dist-upgrade', to this bug report. Running 'apport-collect
1877473' should do this automatically. Thanks in advance!

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: New => Incomplete

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

Title:
  Upgrading from 18.04 to 20.04 encrypted installation with LUKS and LVM
  makes it unbootable without manual intervention

Status in lvm2 package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  Incomplete

Bug description:
  Volume Group metadata had to be upgraded manually with

  vgck --updatemetadata yourvgname

  The VG name was somehow changed from lvm-name to just name and I had
  to edit /etc/crypttab and update-initramfs -u -k all

  Also cryptsetup-initramfs package was deleted for some reason, had to
  re-install it in chroot. Maybe it happened because I have disabled
  installing recommended and suggested packages or maybe because none of
  *buntu-desktop packages are installed on my system. Not sure if I have
  to report it as a separate problem, please advise.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri May  8 01:35:04 2020
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1876952] Re: missing a package hook for linux-raspi and linux-raspi2

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-core-dev/ubuntu/groovy/apport/ubuntu

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

Title:
  missing a package hook for linux-raspi and linux-raspi2

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  In Progress

Bug description:
  Apport does not include a source package hook for the linux-raspi or
  linux-raspi2 kernels which are used on the Raspberry Pi images,
  subsequently if 'ubuntu-bug linux-raspi' is used valuable information
  will not be collected.

  Test Case
  -
  1) On a Raspberry Pi run 'ubuntu-bug linux-raspi'.
  2) Choose 'View report'
  3) Observe that 'ProcFB' is not collected

  With the version of apport from -proposed 'ProcFB' will be in the
  report.

  Repeat the test case for 'linux-raspi2'.

  Regression Potential
  
  None, as we are just adding a symlink from linux-meta-raspi to the linux 
source package hook.

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

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

[Touch-packages] [Bug 1871185] Re: urls in ubuntu-bugs dialog not really clickable

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-core-dev/ubuntu/groovy/apport/ubuntu

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

Title:
  urls in ubuntu-bugs dialog not really clickable

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Triaged

Bug description:
  when ubuntu-bug report suggests filing a bug report directly in
  launchpad for snap packages, the displayed url is clickable but the
  url stops at the first + symbol. see attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8.8
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CrashReports: 640:1000:124:8919925:2020-03-29 20:16:13.456640958 
+0200:2020-03-29 20:16:14.456640958 
+0200:/var/crash/_usr_bin_python3.7.1000.crash
  CurrentDesktop: XFCE
  Date: Mon Apr  6 19:50:16 2020
  InstallationDate: Installed on 2020-03-18 (18 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1877633] [NEW] libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64

[Jamie Strandboge]

Public bug reported:

This was reported via the snapcraft forum:

On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2

$ lsb_release -d
Description:Ubuntu 18.04.4 LTS
$ scmp_sys_resolver -a aarch64 163
getrlimit
$ scmp_sys_resolver -a aarch64 getrlimit
163

focal amd64, libseccomp 2.4.3-1ubuntu1 -- *__BROKEN__*

$ lsb_release -d
Description:Ubuntu 20.04 LTS
$ scmp_sys_resolver -a aarch64 163
UNKNOWN
$ scmp_sys_resolver -a aarch64 getrlimit
-10180

** Affects: libseccomp (Ubuntu)
 Importance: High
 Assignee: Alex Murray (alexmurray)
 Status: Confirmed

** Affects: libseccomp (Ubuntu Focal)
 Importance: High
 Assignee: Alex Murray (alexmurray)
 Status: Confirmed

** Affects: libseccomp (Ubuntu Groovy)
 Importance: High
 Assignee: Alex Murray (alexmurray)
 Status: Confirmed

** Also affects: libseccomp (Ubuntu Groovy)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Changed in: libseccomp (Ubuntu Groovy)
 Assignee: (unassigned) => Alex Murray (alexmurray)

** Changed in: libseccomp (Ubuntu Focal)
 Assignee: (unassigned) => Alex Murray (alexmurray)

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

Title:
  libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the
  getrlimit syscall on arm64

Status in libseccomp package in Ubuntu:
  Confirmed
Status in libseccomp source package in Focal:
  Confirmed
Status in libseccomp source package in Groovy:
  Confirmed

Bug description:
  This was reported via the snapcraft forum:

  On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2

  $ lsb_release -d
  Description:  Ubuntu 18.04.4 LTS
  $ scmp_sys_resolver -a aarch64 163
  getrlimit
  $ scmp_sys_resolver -a aarch64 getrlimit
  163

  focal amd64, libseccomp 2.4.3-1ubuntu1 -- *__BROKEN__*

  $ lsb_release -d
  Description:  Ubuntu 20.04 LTS
  $ scmp_sys_resolver -a aarch64 163
  UNKNOWN
  $ scmp_sys_resolver -a aarch64 getrlimit
  -10180

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

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

[Touch-packages] [Bug 1877626] [NEW] new upstream version

[Mind Booster Noori]

Public bug reported:

Debian's dh-python is now in version 4.20200315, which fixed a number of
bugs, as can be seen on its changelog[1]. Please sync with the latest
version.

[1] https://metadata.ftp-master.debian.org/changelogs//main/d/dh-python
/dh-python_4.20200315_changelog

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

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

Title:
  new upstream version

Status in dh-python package in Ubuntu:
  New

Bug description:
  Debian's dh-python is now in version 4.20200315, which fixed a number
  of bugs, as can be seen on its changelog[1]. Please sync with the
  latest version.

  [1] https://metadata.ftp-master.debian.org/changelogs//main/d/dh-
  python/dh-python_4.20200315_changelog

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

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

[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

[George Kraft]

Removing charm-keepalived since I believe no changes are needed there.
It should pick up fixes once they are available on apt archives.

** No longer affects: charm-keepalived

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

Title:
  [master] Restarting systemd-networkd breaks keepalived, heartbeat,
  corosync, pacemaker (interface aliases are restarted)

Status in netplan:
  Confirmed
Status in heartbeat package in Ubuntu:
  Won't Fix
Status in keepalived package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in keepalived source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Confirmed
Status in keepalived source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed
Status in keepalived source package in Disco:
  Won't Fix
Status in systemd source package in Disco:
  Won't Fix
Status in keepalived source package in Eoan:
  In Progress
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [impact]

  - ALL related HA software has a small problem if interfaces are being
  managed by systemd-networkd: nic restarts/reconfigs are always going
  to wipe all interfaces aliases when HA software is not expecting it to
  (no coordination between them.

  - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
  smarter in this case because it has a service monitor that will
  restart the virtual IP resource, in affected node & nic, before
  considering a real failure, but other HA service might consider a real
  failure when it is not.

  [test case]

  - comment #14 is a full test case: to have 3 node pacemaker, in that
  example, and cause a networkd service restart: it will trigger a
  failure for the virtual IP resource monitor.

  - other example is given in the original description for keepalived.
  both suffer from the same issue (and other HA softwares as well).

  [regression potential]

  - this backports KeepConfiguration parameter, which adds some
  significant complexity to networkd's configuration and behavior, which
  could lead to regressions in correctly configuring the network at
  networkd start, or incorrectly maintaining configuration at networkd
  restart, or losing network state at networkd stop.

  - Any regressions are most likely to occur during networkd start,
  restart, or stop, and most likely to involve missing or incorrect ip
  address(es).

  - the change is based in upstream patches adding the exact feature we
  needed to fix this issue & it will be integrated with a netplan change
  to add the needed stanza to systemd nic configuration file
  (KeepConfiguration=)

  [other info]

  original description:
  ---

  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
  addresses: [192.168.0.5/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth2:
  addresses:
    - 12.13.14.18/29
    - 12.13.14.19/29
  gateway4: 12.13.14.17
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth3:
  addresses: [10.22.11.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth4:
  addresses: [10.22.14.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth7:
  addresses: [9.5.17.34/29]
  dhcp4: false
  optional: true
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  version: 2

  Configure keepalived (again, a working config with IP addresses
  obfuscated)

  global_defs   # Block id
  {
  notification_email {
  sysadm...@blah.com
  }
  notification_email_from keepali...@system3.hq.blah.com
  smtp_server 10.22.11.7 # IP
  smtp_connect_timeout 30  # integer, seconds
  router_id system3  # string identifying the machine,
   # (doesn't have to be hostname).
  vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
  vrrp_mcast_group6 ff02::12   # optional, default ff02::12
  enable_traps   

[Touch-packages] [Bug 1582899] Re: in-target: mkinitramfs: failed to determine device for /

[Rafael David Tinoco]

I'm marking this as incomplete for 18.04.2 and wont fix for xenial based
on @ahasenack's last input.

** Also affects: base-installer (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: live-installer (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: base-installer (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: live-installer (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: live-installer (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: live-installer (Ubuntu Bionic)
   Status: New => Incomplete

** Changed in: live-installer (Ubuntu Xenial)
   Status: New => Won't Fix

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

Title:
  in-target: mkinitramfs: failed to determine device for /

Status in base-installer package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in live-installer package in Ubuntu:
  Incomplete
Status in base-installer source package in Xenial:
  New
Status in initramfs-tools source package in Xenial:
  New
Status in live-installer source package in Xenial:
  Won't Fix
Status in base-installer source package in Bionic:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in live-installer source package in Bionic:
  Incomplete

Bug description:
  Sysadmin reported in #ubuntu (later #ubuntu-kernel) the 16.04 ubuntu-
  server ISO installer failed due to being unable to configure linux-
  image-4.4.0-21-generic.

  Lots of diagnostics and one SSH remote session later we seem to have
  narrowed it down to the installer.

  At the installer's boot menu the F6 option "Expert mode" is chosen.

  During initial ram file-system creation (after the kernel image is installed) 
the /dev/ file-system is not mounted in /target/ and therefore
  the initramfs-tools/hook-functions::dep_add_modules_mount() cannot match
  the mount device of "/" (in this case /dev/sda3) with any node under /dev/ 
which only contains static entries.

  Cause appears to be that live-installer.postinst has the crucial step
  calling library.sh:setup_dev() commented out:

  #waypoint 1 setup_dev

  OS=linux
  setup_dev() calls setup_dev_${OS}
  setup_dev_linux() mounts procfs and devtmpfs into /target/

  

  Originally the cause of the error message appeared to be that the
  symlink names in /dev/disk/by-uuid/  haven't been updated after the
  partitioning stage if there were pre-existing partitions and file-
  systems on the install device, *and* the sysadmin chose to format the
  existing partitions when selecting mountpoints.

  In this case a hardware RAID device presents:

  /dev/sda1 (/boot/)
  /dev/sda2 (swap)
  /dev/sda3 (/)

  From the shell I noticed:

  root@tmpstorage:/# ll /dev/disk/by-uuid/
  total 0
  lrwxrwxrwx 1 root root  10 May 17 19:39 130e4419-4bfd-46d2-87f9-62e5379bf591 
-> ../../sda1
  lrwxrwxrwx 1 root root  10 May 17 19:39 127d3fa1-c07c-48e4-9e26-1b926d37625c 
-> ../../sda3
  lrwxrwxrwx 1 root root  10 May 17 19:39 78b88456-2b0b-4265-9ed2-5db61522d887 
-> ../../sda2
  lrwxrwxrwx 1 root root   9 May 17 19:39 2016-04-20-22-45-29-00 -> ../../sr1
  drwxr-xr-x 6 root root 120 May 17 19:39 ..
  drwxr-xr-x 2 root root 120 May 17 19:39 .

  root@tmpstorage:/# blkid /dev/sda*
  /dev/sda: PTUUID="a84e60fd" PTTYPE="dos"
  /dev/sda1: UUID="61365714-8ff7-47a2-8035-8aed9e3191a6" TYPE="ext4" 
PARTUUID="a84e60fd-01"
  /dev/sda2: UUID="78b88456-2b0b-4265-9ed2-5db61522d887" TYPE="swap" 
PARTUUID="a84e60fd-02"
  /dev/sda3: UUID="75f68451-9472-47c7-9efc-ed032bfa9987" TYPE="ext4" 
PARTUUID="a84e60fd-03"

  More details to follow.

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

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

[Touch-packages] [Bug 1582899] Re: in-target: mkinitramfs: failed to determine device for /

[Rafael David Tinoco]

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

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

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

Title:
  in-target: mkinitramfs: failed to determine device for /

Status in base-installer package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in live-installer package in Ubuntu:
  Incomplete
Status in base-installer source package in Xenial:
  New
Status in initramfs-tools source package in Xenial:
  New
Status in live-installer source package in Xenial:
  Won't Fix
Status in base-installer source package in Bionic:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in live-installer source package in Bionic:
  Incomplete

Bug description:
  Sysadmin reported in #ubuntu (later #ubuntu-kernel) the 16.04 ubuntu-
  server ISO installer failed due to being unable to configure linux-
  image-4.4.0-21-generic.

  Lots of diagnostics and one SSH remote session later we seem to have
  narrowed it down to the installer.

  At the installer's boot menu the F6 option "Expert mode" is chosen.

  During initial ram file-system creation (after the kernel image is installed) 
the /dev/ file-system is not mounted in /target/ and therefore
  the initramfs-tools/hook-functions::dep_add_modules_mount() cannot match
  the mount device of "/" (in this case /dev/sda3) with any node under /dev/ 
which only contains static entries.

  Cause appears to be that live-installer.postinst has the crucial step
  calling library.sh:setup_dev() commented out:

  #waypoint 1 setup_dev

  OS=linux
  setup_dev() calls setup_dev_${OS}
  setup_dev_linux() mounts procfs and devtmpfs into /target/

  

  Originally the cause of the error message appeared to be that the
  symlink names in /dev/disk/by-uuid/  haven't been updated after the
  partitioning stage if there were pre-existing partitions and file-
  systems on the install device, *and* the sysadmin chose to format the
  existing partitions when selecting mountpoints.

  In this case a hardware RAID device presents:

  /dev/sda1 (/boot/)
  /dev/sda2 (swap)
  /dev/sda3 (/)

  From the shell I noticed:

  root@tmpstorage:/# ll /dev/disk/by-uuid/
  total 0
  lrwxrwxrwx 1 root root  10 May 17 19:39 130e4419-4bfd-46d2-87f9-62e5379bf591 
-> ../../sda1
  lrwxrwxrwx 1 root root  10 May 17 19:39 127d3fa1-c07c-48e4-9e26-1b926d37625c 
-> ../../sda3
  lrwxrwxrwx 1 root root  10 May 17 19:39 78b88456-2b0b-4265-9ed2-5db61522d887 
-> ../../sda2
  lrwxrwxrwx 1 root root   9 May 17 19:39 2016-04-20-22-45-29-00 -> ../../sr1
  drwxr-xr-x 6 root root 120 May 17 19:39 ..
  drwxr-xr-x 2 root root 120 May 17 19:39 .

  root@tmpstorage:/# blkid /dev/sda*
  /dev/sda: PTUUID="a84e60fd" PTTYPE="dos"
  /dev/sda1: UUID="61365714-8ff7-47a2-8035-8aed9e3191a6" TYPE="ext4" 
PARTUUID="a84e60fd-01"
  /dev/sda2: UUID="78b88456-2b0b-4265-9ed2-5db61522d887" TYPE="swap" 
PARTUUID="a84e60fd-02"
  /dev/sda3: UUID="75f68451-9472-47c7-9efc-ed032bfa9987" TYPE="ext4" 
PARTUUID="a84e60fd-03"

  More details to follow.

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

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

[Touch-packages] [Bug 1875493] Re: [core] log rotation doesn't properly restart rsyslogd

[Oliver Grawert]

well, rsyslog is completely gone from core after UC16 ... how would you
test that in UC18 or UC20 to verify SRUs ?

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

Title:
  [core] log rotation doesn't properly restart rsyslogd

Status in Snappy:
  New
Status in rsyslog package in Ubuntu:
  New

Bug description:
  One of our commercial partners is developing a device agent snap for
  UC16. One of their engineers just shared the following bug report:

  I wanted to give you a heads up on an issue that we encountered with
  one of our gateways (a Dell 3000) regarding a full disk (/writable).
  It seems as though rsyslog had a bad logrotate config and was holding
  on to deleted files as described here:

   - 
https://www.claudiokuenzler.com/blog/861/after-ubuntu-update-trusty-xenial-disk-filled-syslog-logrotate
   - https://bugzilla.redhat.com/show_bug.cgi?id=1713358

  Both df and du where showing different results for the “/writable”
  path on the Dell gateway.

  We were able to copy the lsof binary over and found this:

  $ sudo /tmp/lsof | grep deleted
  ...
  rsyslogd 1765 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted)
  rsyslogd 1765 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted)
  rsyslogd 1765 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted)
  in:imuxso 1765 1776 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog 
(deleted)
  in:imuxso 1765 1776 syslog 6w REG 179,4 45056 130836 /var/log/auth.log 
(deleted)
  in:imuxso 1765 1776 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log 
(deleted)
  in:imklog 1765 1777 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog 
(deleted)
  in:imklog 1765 1777 syslog 6w REG 179,4 45056 130836 /var/log/auth.log 
(deleted)
  in:imklog 1765 1777 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log 
(deleted)
  rs:main 1765 1778 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog 
(deleted)
  rs:main 1765 1778 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted)
  rs:main 1765 1778 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log 
(deleted)
  ...

  Restarting the service freed up the deleted files / disk space:

  sudo service rsyslog restart

  The rsyslog config (/etc/logrotate.d/rsyslog) calls this script post
  rotate:

  /usr/lib/rsyslog/rsyslog-rotate

  Which does not actually kill the rsyslog process:

  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2305 0.7 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n
  admin 2464 0.0 0.0 12984 932 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog
  admin@GR0GP42:~$ sudo /usr/lib/rsyslog/rsyslog-rotate
  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n
  admin 2469 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog

  The fix appears to be using the following command: sudo systemctl
  restart rsyslog >/dev/null 2>&1 || true

  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n
  admin 2482 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog
  admin@GR0GP42:~$ sudo systemctl restart rsyslog >/dev/null 2>&1 || true
  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2487 1.0 0.1 262692 3432 ? Ssl 20:36 0:00 /usr/sbin/rsyslogd -n
  admin 2496 0.0 0.0 12984 980 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog

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

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

[Touch-packages] [Bug 1875493] Re: [core] log rotation doesn't properly restart rsyslogd

[Michael Vogt]

Thanks for your bugreport.

What happens is that rsyslog:
- has a rsyslog.logrotate config file that has "postrotate" 
/usr/lib/rsyslog/rsyslog-rotate
- the rsyslog-rotate has "systemctl kill -s HUP rsyslog.service" in it

It looks like neither rsyslog.logrotate nor rsyslog-rotate have changed between 
both xenial (UC16) and focal (UC20). So this needs some deeper investigation, I 
don't think we can change the postrotate line for UC16 only without 
understanding if:
a) does this affect ubuntu classic as well?
b) if not, why is it only affecting core?

We will also then SRU it (and maybe put in the ppa:snappy-dev/image to
get testing in edge). But we need to stay in sync with xenial here.

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

Title:
  [core] log rotation doesn't properly restart rsyslogd

Status in Snappy:
  New
Status in rsyslog package in Ubuntu:
  New

Bug description:
  One of our commercial partners is developing a device agent snap for
  UC16. One of their engineers just shared the following bug report:

  I wanted to give you a heads up on an issue that we encountered with
  one of our gateways (a Dell 3000) regarding a full disk (/writable).
  It seems as though rsyslog had a bad logrotate config and was holding
  on to deleted files as described here:

   - 
https://www.claudiokuenzler.com/blog/861/after-ubuntu-update-trusty-xenial-disk-filled-syslog-logrotate
   - https://bugzilla.redhat.com/show_bug.cgi?id=1713358

  Both df and du where showing different results for the “/writable”
  path on the Dell gateway.

  We were able to copy the lsof binary over and found this:

  $ sudo /tmp/lsof | grep deleted
  ...
  rsyslogd 1765 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted)
  rsyslogd 1765 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted)
  rsyslogd 1765 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted)
  in:imuxso 1765 1776 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog 
(deleted)
  in:imuxso 1765 1776 syslog 6w REG 179,4 45056 130836 /var/log/auth.log 
(deleted)
  in:imuxso 1765 1776 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log 
(deleted)
  in:imklog 1765 1777 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog 
(deleted)
  in:imklog 1765 1777 syslog 6w REG 179,4 45056 130836 /var/log/auth.log 
(deleted)
  in:imklog 1765 1777 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log 
(deleted)
  rs:main 1765 1778 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog 
(deleted)
  rs:main 1765 1778 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted)
  rs:main 1765 1778 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log 
(deleted)
  ...

  Restarting the service freed up the deleted files / disk space:

  sudo service rsyslog restart

  The rsyslog config (/etc/logrotate.d/rsyslog) calls this script post
  rotate:

  /usr/lib/rsyslog/rsyslog-rotate

  Which does not actually kill the rsyslog process:

  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2305 0.7 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n
  admin 2464 0.0 0.0 12984 932 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog
  admin@GR0GP42:~$ sudo /usr/lib/rsyslog/rsyslog-rotate
  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n
  admin 2469 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog

  The fix appears to be using the following command: sudo systemctl
  restart rsyslog >/dev/null 2>&1 || true

  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n
  admin 2482 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog
  admin@GR0GP42:~$ sudo systemctl restart rsyslog >/dev/null 2>&1 || true
  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2487 1.0 0.1 262692 3432 ? Ssl 20:36 0:00 /usr/sbin/rsyslogd -n
  admin 2496 0.0 0.0 12984 980 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog

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

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

[Touch-packages] [Bug 1877567] Re: Automatic Login

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Automatic Login

Status in xorg package in Ubuntu:
  New

Bug description:
  Problem
  1. Switched to automatic login option during the fresh install
  2. On a start up Login screen is still shown.
  3. Typing correct user name and password does not start the system.
  4. End up stuck in login loop

  Solution
  1. Restart system
  2. Selected Ubuntu Recovery mode
  3. Select normal boot
  4. System starts
  5. Go to to User Settings and disable automatic login
  6. Reboot
  7. System starts with login screen
  8. Type name and password.
  9. system starts

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:06: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 May  8 08:04:14 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] [10de:2187] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1650 SUPER] 
[1458:401b]
  InstallationDate: Installed on 2020-05-04 (4 days ago)
  InstallationMedia: 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:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=f070f159-e92a-44d2-9c1b-d791f0e697c6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: A320M-HDV R4.0
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320M-HDVR4.0: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.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/1877567/+subscriptions

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

[Touch-packages] [Bug 1875493] Re: [core] log rotation doesn't properly restart rsyslogd

[Michael Vogt]

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

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

Title:
  [core] log rotation doesn't properly restart rsyslogd

Status in Snappy:
  New
Status in rsyslog package in Ubuntu:
  New

Bug description:
  One of our commercial partners is developing a device agent snap for
  UC16. One of their engineers just shared the following bug report:

  I wanted to give you a heads up on an issue that we encountered with
  one of our gateways (a Dell 3000) regarding a full disk (/writable).
  It seems as though rsyslog had a bad logrotate config and was holding
  on to deleted files as described here:

   - 
https://www.claudiokuenzler.com/blog/861/after-ubuntu-update-trusty-xenial-disk-filled-syslog-logrotate
   - https://bugzilla.redhat.com/show_bug.cgi?id=1713358

  Both df and du where showing different results for the “/writable”
  path on the Dell gateway.

  We were able to copy the lsof binary over and found this:

  $ sudo /tmp/lsof | grep deleted
  ...
  rsyslogd 1765 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted)
  rsyslogd 1765 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted)
  rsyslogd 1765 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted)
  in:imuxso 1765 1776 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog 
(deleted)
  in:imuxso 1765 1776 syslog 6w REG 179,4 45056 130836 /var/log/auth.log 
(deleted)
  in:imuxso 1765 1776 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log 
(deleted)
  in:imklog 1765 1777 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog 
(deleted)
  in:imklog 1765 1777 syslog 6w REG 179,4 45056 130836 /var/log/auth.log 
(deleted)
  in:imklog 1765 1777 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log 
(deleted)
  rs:main 1765 1778 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog 
(deleted)
  rs:main 1765 1778 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted)
  rs:main 1765 1778 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log 
(deleted)
  ...

  Restarting the service freed up the deleted files / disk space:

  sudo service rsyslog restart

  The rsyslog config (/etc/logrotate.d/rsyslog) calls this script post
  rotate:

  /usr/lib/rsyslog/rsyslog-rotate

  Which does not actually kill the rsyslog process:

  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2305 0.7 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n
  admin 2464 0.0 0.0 12984 932 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog
  admin@GR0GP42:~$ sudo /usr/lib/rsyslog/rsyslog-rotate
  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n
  admin 2469 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog

  The fix appears to be using the following command: sudo systemctl
  restart rsyslog >/dev/null 2>&1 || true

  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n
  admin 2482 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog
  admin@GR0GP42:~$ sudo systemctl restart rsyslog >/dev/null 2>&1 || true
  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2487 1.0 0.1 262692 3432 ? Ssl 20:36 0:00 /usr/sbin/rsyslogd -n
  admin 2496 0.0 0.0 12984 980 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog

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

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

[Touch-packages] [Bug 1877567] [NEW] Automatic Login

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Problem
1. Switched to automatic login option during the fresh install
2. On a start up Login screen is still shown.
3. Typing correct user name and password does not start the system.
4. End up stuck in login loop

Solution
1. Restart system
2. Selected Ubuntu Recovery mode
3. Select normal boot
4. System starts
5. Go to to User Settings and disable automatic login
6. Reboot
7. System starts with login screen
8. Type name and password.
9. system starts

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:06: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 May  8 08:04:14 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] [10de:2187] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1650 SUPER] 
[1458:401b]
InstallationDate: Installed on 2020-05-04 (4 days ago)
InstallationMedia: 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:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=f070f159-e92a-44d2-9c1b-d791f0e697c6 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.30
dmi.board.name: A320M-HDV R4.0
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320M-HDVR4.0: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.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

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


** Tags: amd64 apport-bug focal ubuntu
-- 
Automatic Login
https://bugs.launchpad.net/bugs/1877567
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

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

[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 1873658] Re: Deb Files are not associated with an application that manages packages

[AsciiWolf]

Hello Chris, I have tested the latest desktop-file-utils (0.24-1ubuntu3)
package from focal-proposed and can confirm that the issue is now fixed
- Software installation is now the default action for deb packages
opened from Nautilus.

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

-- 
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:
  Fix Committed
Status in gdebi source package in Focal:
  Invalid

Bug description:
  [Impact]

   * When a deb is downloaded the default handler is not capable of
  installing on 20.04.

  [Test Case]

   We should perform this test on Ubuntu 20.04 as well as some flavors
  to ensure we do not regress.

   * Download any deb in firefox, double click on the downloaded file
 - On Ubuntu this should open "Ubuntu Software"
 - On flavors it should open whatever their default app for handling debs is

  [Regression Potential]

   * For Ubuntu, very low, rarely would a user expect to open a deb with
  file-roller

   * Other flavors of ubuntu are overriding this default and should not
  be affected.  We do need to test this on other flavors to ensure their
  defaults are still honored.

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 1877536] Re: BlueZ 5.54 release

[Mathew Hodson]

** Tags added: upgrade-software-version

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

Title:
  BlueZ 5.54 release

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Release BlueZ 5.54 to groovy

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

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

[Touch-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Mathew Hodson]

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

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
   State: RUNNING
   Name: alsa_input.pci-_00_1f.3.analog-stereo
   Description: Built-in Audio Analog Stereo
   Driver: module-alsa-card.c
   Sample Specification: s16le 2ch 44100Hz
   Channel Map: front-left,front-right
   Owner Module: 7
   Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

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

-- 
Mailing list: https://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 1877467] Re: Input device does not switch back to internal microphone when analog headset unplugged

[Brian Pursley]

Hi Sebastien.

Yes, that fixes the problem. Thank you for the fast response!

Brian

On Fri, May 8, 2020 at 4:05 AM Sebastien Bacher 
wrote:

> Thank you for your bug report, could you check if the stable update
> https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.1
> fixes the issue for you?
>
> ** No longer affects: gnome-control-center (Ubuntu)
>
> ** Changed in: pulseaudio (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1877467
>
> Title:
>   Input device does not switch back to internal microphone when analog
>   headset unplugged
>
> Status in pulseaudio package in Ubuntu:
>   Incomplete
>
> Bug description:
>   1. Open Settings - Sound
>   2. Confirm Output Device = "Speakers - Built-in Audio" and Input Device
> = Internal Microphone - Built-in Audio"
>   3. Plug analog headset into jack
>   4. When prompted to select audio device, select "Headset"
>   5. Confirm Output Device = "Headphones - Built in Audio" and Input
> Device = "Headset Microphone - Built-in Audio"
>   6. Unplug analog headset from jack
>
>   PROBLEM OCCURS HERE:
>
>   Output Device goes back to "Speakers - Built-in Audio", but Input
>   Device remains at "Headset Microphone - Built-in Audio".  It should go
>   back to the original setting of "Internal Microphone - Built-in Audio"
>
>   WORKAROUND:
>
>   Manually change Input Device back to "Internal Microphone - Built-in
>   Audio"
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: gnome-control-center 1:3.36.1-1ubuntu5
>   ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
>   Uname: Linux 5.4.0-29-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu May  7 18:01:19 2020
>   ExecutablePath: /usr/bin/gnome-control-center
>   InstallationDate: Installed on 2019-12-26 (133 days ago)
>   InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
>   ProcEnviron:
>PATH=(custom, user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gnome-control-center
>   UpgradeStatus: Upgraded to focal on 2020-04-24 (13 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877467/+subscriptions
>


-- 
Brian Pursley
bpurs...@cinlogic.com

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

Title:
  Input device does not switch back to internal microphone when analog
  headset unplugged

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  1. Open Settings - Sound
  2. Confirm Output Device = "Speakers - Built-in Audio" and Input Device = 
Internal Microphone - Built-in Audio"
  3. Plug analog headset into jack
  4. When prompted to select audio device, select "Headset"
  5. Confirm Output Device = "Headphones - Built in Audio" and Input Device = 
"Headset Microphone - Built-in Audio"
  6. Unplug analog headset from jack

  PROBLEM OCCURS HERE:

  Output Device goes back to "Speakers - Built-in Audio", but Input
  Device remains at "Headset Microphone - Built-in Audio".  It should go
  back to the original setting of "Internal Microphone - Built-in Audio"

  WORKAROUND:

  Manually change Input Device back to "Internal Microphone - Built-in
  Audio"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  7 18:01:19 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-12-26 (133 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-04-24 (13 days ago)

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

-- 
Mailing list: https://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 1866625] Re: OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit Integers.

[Wolf Pichler]

It should indeed be done like this:

 import gi
 gi.require_version('Gtk', '3.0')
 from gi.repository import Gtk

 from gi.repository import GObject

 mystore = Gtk.ListStore(GObject.TYPE_UINT64)
 mystore.insert_with_valuesv(-1, [1], [GObject.Value(GObject.TYPE_UINT64, 
1330400507426)])

###

I was completely unaware of that possibility because the source of my
GTK knowlege is

https://lazka.github.io/pgi-
docs/#Gtk-3.0/classes/ListStore.html#Gtk.ListStore.set_column_types

When checking out the available types one ends up here:

https://lazka.github.io/pgi-
docs/#GObject-2.0/classes/GType.html#GObject.GType

Which does not ring any bell ...

So I did it like in

https://python-gtk-3-tutorial.readthedocs.io/en/latest/treeview.html
#the-model

where the Python types are used.

###

With the knowlege I gained through this FR it was possible to find this:

GObject Built-in Type Constants
The Built-in Type constants specify the pre-defined types used by gobject.

https://developer.gnome.org/pygobject/stable/gobject-constants.html
#gobject-type-constants

which is quite useful.

###

Thanks!

On 11.03.20 17:56, Christoph Reiter wrote:
>  import gi
>   gi.require_version('Gtk', '3.0')
>   from gi.repository import Gtk
>
>   This works in Python 2:
>
>   mystore = Gtk.ListStore(long)
>   mystore.insert_with_valuesv(-1, [1], [long(1330400507426)])
>
>   This does not work in Python 3:
>
>   mystore = Gtk.ListStore(int)
>   mystore.insert_with_valuesv(-1, [1], [int(1330400507426)])

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

Title:
  OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit
  Integers.

Status in pygobject package in Ubuntu:
  New

Bug description:
  import gi
  gi.require_version('Gtk', '3.0')
  from gi.repository import Gtk

  This works in Python 2:

  mystore = Gtk.ListStore(long)
  mystore.insert_with_valuesv(-1, [1], [long(1330400507426)])

  This does not work in Python 3:

  mystore = Gtk.ListStore(int)
  mystore.insert_with_valuesv(-1, [1], [int(1330400507426)])

  OverflowError: Item 0: out of range for int property

  

  lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  apt-cache policy python3-gi
  python3-gi:
Installed: 3.26.1-2ubuntu1
Candidate: 3.26.1-2ubuntu1
Version table:
   *** 3.26.1-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.26.1-2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  python3 -V
  Python 3.6.9

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

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

[Touch-packages] [Bug 1877590] Re: SRU the current 3.24.20 stable update

[Sebastien Bacher]

** Changed in: gtk+3.0 (Ubuntu)
   Status: In Progress => Fix Committed

** Tags added: upgrade-software-version

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

Title:
  SRU the current 3.24.20 stable update

Status in gtk+3.0 package in Ubuntu:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/NEWS

  * Test case

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

  Check that GNOME Desktop and GTK software still work correctly

  * Regression potential

  The update has some fixes in the filechooser and the emoji picker,
  test those

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1877590/+subscriptions

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

[Touch-packages] [Bug 1877598] [NEW] package avahi-daemon 0.7-3.1ubuntu1.2 failed to install/upgrade: Unterprozess installiertes avahi-daemon-Skript des Paketes post-installation gab den Fehler-Ausgan

[step21]

Public bug reported:

Error during sudo do-release-upgrade. Possibly due to sudo timeout.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: avahi-daemon 0.7-3.1ubuntu1.2
ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
Uname: Linux 4.4.0-128-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
Date: Fri May  8 16:17:25 2020
ErrorMessage: Unterprozess installiertes avahi-daemon-Skript des Paketes 
post-installation gab den Fehler-Ausgangsstatus 1 zurück
InstallationDate: Installed on 2017-08-13 (999 days ago)
InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt  1.6.12
SourcePackage: avahi
Title: package avahi-daemon 0.7-3.1ubuntu1.2 failed to install/upgrade: 
Unterprozess installiertes avahi-daemon-Skript des Paketes post-installation 
gab den Fehler-Ausgangsstatus 1 zurück
UpgradeStatus: Upgraded to bionic on 2020-05-08 (0 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package avahi-daemon 0.7-3.1ubuntu1.2 failed to install/upgrade:
  Unterprozess installiertes avahi-daemon-Skript des Paketes post-
  installation gab den Fehler-Ausgangsstatus 1 zurück

Status in avahi package in Ubuntu:
  New

Bug description:
  Error during sudo do-release-upgrade. Possibly due to sudo timeout.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: avahi-daemon 0.7-3.1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Fri May  8 16:17:25 2020
  ErrorMessage: Unterprozess installiertes avahi-daemon-Skript des Paketes 
post-installation gab den Fehler-Ausgangsstatus 1 zurück
  InstallationDate: Installed on 2017-08-13 (999 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12
  SourcePackage: avahi
  Title: package avahi-daemon 0.7-3.1ubuntu1.2 failed to install/upgrade: 
Unterprozess installiertes avahi-daemon-Skript des Paketes post-installation 
gab den Fehler-Ausgangsstatus 1 zurück
  UpgradeStatus: Upgraded to bionic on 2020-05-08 (0 days ago)

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

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

[Touch-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

[Sebastien Bacher]

** Description changed:

+ * Impact
+ Changes on the 'Other Software tab' sometime fail to ask for credential and 
fail to apply as a consequence
+ 
+ * Test Case
+ - start software-properties-gtk
+ - got to the 'Other Software Tab'
+ - try to change the value of a checkbox
+ 
+ The change should prompt for a password and be active
+ 
+ * Regression potential
+ the change is a small sleep workaround to avoid trying to get the focus while 
GTK still has it, outside of a tiny delay in the active it should have no 
consequence
+ 
+ ---
+ 
  
  On the "Other Software" tab, I am unable to select "Canonical Partners".
  Similarly, the other checkboxes on the "Other Software" can not be clicked.
  Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.
  
  However, activating or deactivating checkboxes on other tabs causes an
  authorization dialog to be presented to the user.
  
  I experience this bug in an an Xorg session.
  
  sources.list and sources.list.d have the following permissions:
  -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
  drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d
  
  All files in sources.list.d have the following permissions as this example:
  -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list
  
  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  
  $ apt-cache policy software-properties-gtk
  software-properties-gtk:
-   Installed: 0.96.24.17
-   Candidate: 0.96.24.17
-   Version table:
-  *** 0.96.24.17 500
- 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
- 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
- 100 /var/lib/dpkg/status
+   Installed: 0.96.24.17
+   Candidate: 0.96.24.17
+   Version table:
+  *** 0.96.24.17 500
+ 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
+ 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
+ 100 /var/lib/dpkg/status
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 26 22:45:09 2017
  InstallationDate: Installed on 2017-10-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Confirmed

Bug description:
  * Impact
  Changes on the 'Other Software tab' sometime fail to ask for credential and 
fail to apply as a consequence

  * Test Case
  - start software-properties-gtk
  - got to the 'Other Software Tab'
  - try to change the value of a checkbox

  The change should prompt for a password and be active

  * Regression potential
  the change is a small sleep workaround to avoid trying to get the focus while 
GTK still has it, outside of a tiny delay in the active it should have no 
consequence

  ---

  
  On the "Other Software" tab, I am unable to select "Canonical Partners".
  Similarly, the other checkboxes on the "Other Software" can not be clicked.
  Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.

  However, activating or deactivating checkboxes on other tabs causes an
  authorization dialog to be presented to the user.

  I experience this bug in an an Xorg session.

  sources.list and sources.list.d have the following permissions:
  -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
  drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d

  All files in sources.list.d have the following permissions as this example:
  -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy software-properties-gtk
  software-properties-gtk:
    Installed: 0.96.24.17
    Candidate: 0.96.24.17
    Version table:
   *** 0.96.24.17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu 

[Touch-packages] [Bug 1877599] [NEW] package linux-firmware 1.173.18 failed to install/upgrade: Unterprozess installiertes linux-firmware-Skript des Paketes post-installation gab den Fehler-Ausgangsst

[step21]

Public bug reported:

Error during sudo do-release-upgrade. Possibly due to sudo timeout.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-firmware 1.173.18
ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
Uname: Linux 4.4.0-128-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
Date: Fri May  8 16:36:25 2020
Dependencies:
 
ErrorMessage: Unterprozess installiertes linux-firmware-Skript des Paketes 
post-installation gab den Fehler-Ausgangsstatus 2 zurück
InstallationDate: Installed on 2017-08-13 (999 days ago)
InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt  1.6.12
SourcePackage: initramfs-tools
Title: package linux-firmware 1.173.18 failed to install/upgrade: Unterprozess 
installiertes linux-firmware-Skript des Paketes post-installation gab den 
Fehler-Ausgangsstatus 2 zurück
UpgradeStatus: Upgraded to bionic on 2020-05-08 (0 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package linux-firmware 1.173.18 failed to install/upgrade:
  Unterprozess installiertes linux-firmware-Skript des Paketes post-
  installation gab den Fehler-Ausgangsstatus 2 zurück

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Error during sudo do-release-upgrade. Possibly due to sudo timeout.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.18
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Fri May  8 16:36:25 2020
  Dependencies:
   
  ErrorMessage: Unterprozess installiertes linux-firmware-Skript des Paketes 
post-installation gab den Fehler-Ausgangsstatus 2 zurück
  InstallationDate: Installed on 2017-08-13 (999 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.173.18 failed to install/upgrade: 
Unterprozess installiertes linux-firmware-Skript des Paketes post-installation 
gab den Fehler-Ausgangsstatus 2 zurück
  UpgradeStatus: Upgraded to bionic on 2020-05-08 (0 days ago)

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

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

[Touch-packages] [Bug 1872564] Re: /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice

[Sergio Durigan Junior]

I'm building a PPA with the backported fix here:

https://launchpad.net/~sergiodj/+archive/ubuntu/apparmor-bug1872564

** Changed in: apparmor (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

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

Title:
  /proc/sys/kernel/random/boot_id rule missing from
  abstractions/nameservice

Status in apparmor package in Ubuntu:
  Fix Committed

Bug description:
  # Description

  On a default Focal install, systemd is used when looking up passwd and
  group information:

  # grep systemd /etc/nsswitch.conf 
  passwd: files systemd
  group:  files systemd

  Daemons confined by Apparmor that also query those "databases" will
  cause this Apparmor denial:

  audit: type=1400 audit(1586825456.411:247): apparmor="DENIED"
  operation="open" namespace="root//lxd-fb1_"
  profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id"
  pid=7370 comm="named" requested_mask="r" denied_mask="r" fsuid=100
  ouid=100

  Many daemons confined by Apparmor also happen to downgrade their
  privileges so they always end up looking up user/group information.

  # Steps to reproduce

  1) launch a Focal container (named fb1 here)
  $ lxc launch images:ubuntu/focal fb1

  2) setup apparmor inside the container (already done on official Ubuntu 
images)
  $ lxc exec fb1 -- apt update && lxc exec fb1 -- apt install apparmor -y

  3) install bind9
  $ lxc exec fb1 -- apt install bind9 -y

  4) check kernel logs for DENIED
  $ journalctl -o cat -b0 -k | grep 'apparmor="DENIED"' | grep -F 
'profile="/usr/sbin/named"'

  
  Step 4, should not return anything. Because systemd is involved in the 
user/group lookups, it currently returns the following:

  audit: type=1400 audit(1586826072.115:266): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:267): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:268): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:269): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:270): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100

  
  # Workaround

  1) remove systemd from nsswitch.conf
  $ lxc exec fb1 -- sed -i 's/ systemd$/ # systemd/' /etc/nsswitch.conf
  2) restart named
  $ lxc exec fb1 -- service named restart
  3) notice no more denials in kernel logs

  # Additional information

  root@fb1:~# apt-cache policy apparmor
  apparmor:
Installed: 2.13.3-7ubuntu4
Candidate: 2.13.3-7ubuntu4
Version table:
   *** 2.13.3-7ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  root@fb1:~# uname -a
  Linux fb1 5.3.0-46-generic #38~18.04.1-Ubuntu SMP Tue Mar 31 04:17:56 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  root@fb1:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

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

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

[Touch-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones

[Anibal Sanchez]

Same issue on Ubuntu 20.04 LTS and HP Omen 15-AX204NS

Still now #17 works OK.

Thanks!

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New
Status in Fedora:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  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_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

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

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

[Touch-packages] [Bug 1875882] Re: debconf attempts interactive configuration; breaks Docker image builds

[Robert C Jennings]

** Changed in: cloud-images
   Status: New => Invalid

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

Title:
  debconf attempts interactive configuration; breaks Docker image builds

Status in cloud-images:
  Invalid
Status in debconf package in Ubuntu:
  New

Bug description:
  When I build a container image using a Dockerfile based on the
  official "ubuntu" image, if I try to install packages that use debconf
  to obtain configuration information, the build fails because debconf
  tries to interact with the user (which is not possible when building a
  container, since the build process must be non-interactive).

  How to reproduce:

  1) install Docker (the version doesn't seem to matter; tried with
  various 19.03 variants)

  2) run the following command to try and build an image:

  ```
  docker build - 

[Touch-packages] [Bug 1877588] [NEW] SRU the current 3.24.20 stable update

[Sebastien Bacher]

Public bug reported:

* Impact
That's the current GNOME stable update, including some fixes and translation 
updates
https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/NEWS

* Test case

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

Check that GNOME Desktop and GTK software still work correctly

* Regression potential

The update has some fixes in the filechooser and the emoji picker, test
those

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Invalid

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

Title:
  SRU the current 3.24.20 stable update

Status in gtk+3.0 package in Ubuntu:
  Invalid

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/NEWS

  * Test case

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

  Check that GNOME Desktop and GTK software still work correctly

  * Regression potential

  The update has some fixes in the filechooser and the emoji picker,
  test those

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1877588/+subscriptions

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

[Touch-packages] [Bug 1877590] [NEW] SRU the current 3.24.20 stable update

[Sebastien Bacher]

Public bug reported:

* Impact
That's the current GNOME stable update, including some fixes and translation 
updates
https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/NEWS

* Test case

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

Check that GNOME Desktop and GTK software still work correctly

* Regression potential

The update has some fixes in the filechooser and the emoji picker, test
those

** Affects: gtk+3.0 (Ubuntu)
 Importance: Wishlist
 Status: In Progress

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => In Progress

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  SRU the current 3.24.20 stable update

Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/NEWS

  * Test case

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

  Check that GNOME Desktop and GTK software still work correctly

  * Regression potential

  The update has some fixes in the filechooser and the emoji picker,
  test those

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1877590/+subscriptions

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

[Touch-packages] [Bug 1877183] Re: segfault in mysql_server_end() from libmysqlclient.so.21

[JonHurst]

OK, disregard. I was using mariadb-server. After replacing it with
mysql-server-8.0, I no longer get the segfault. Thanks for your help.

** Changed in: mysql-8.0 (Ubuntu)
   Status: New => Invalid

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Invalid

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

Title:
  segfault in mysql_server_end() from libmysqlclient.so.21

Status in mysql-8.0 package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  libmysqlclient.so.21 causes a segfault on shutdown.

  Test case attached ==> "Removed database" will not be reported.

  Backtrace:
  #0  0x714c330f in ?? () from 
/lib/x86_64-linux-gnu/libmysqlclient.so.21
  #1  0x714c8823 in ?? () from 
/lib/x86_64-linux-gnu/libmysqlclient.so.21
  #2  0x71466243 in mysql_server_end () from 
/lib/x86_64-linux-gnu/libmysqlclient.so.21
  #3  0x71b4d0ee in ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/sqldrivers/libqsqlmysql.so
  #4  0x71b4d10d in ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/sqldrivers/libqsqlmysql.so
  #5  0x778e55fb in ?? () from /lib/x86_64-linux-gnu/libQt5Sql.so.5
  #6  0x778e588e in QSqlDatabase::~QSqlDatabase() () from 
/lib/x86_64-linux-gnu/libQt5Sql.so.5
  #7  0x778e5d9c in ?? () from /lib/x86_64-linux-gnu/libQt5Sql.so.5
  #8  0x5579 in cause_segfault () at main.cpp:16
  #9  0x5729 in main (argc=1, argv=0x7fffeb18) at main.cpp:23

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libqt5sql5-mysql 5.12.8+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed May  6 21:40:58 2020
  InstallationDate: Installed on 2020-04-27 (9 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1877454] Re: openssh-server hangs with AuthorizedKeysCommand

[Jeremy Norris]

Another link discussing it:
https://secure.phabricator.com/T11827

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

Title:
  openssh-server hangs with AuthorizedKeysCommand

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Xenial:
  Confirmed

Bug description:
  Please consider applying this change to openssh-server distributed in Xenial 
(16.04).
  Without it, sshd can sporadically hang when making use of the 
`AuthorizedKeysCommand` option.

  https://github.com/openssh/openssh-
  portable/commit/ddd3d34e5c7979ca6f4a3a98a7d219a4ed3d98c2

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

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

[Touch-packages] [Bug 1856731] Re: Cannot add a Google accounts with GOA

[Launchpad Bug Tracker]

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

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

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

Title:
  Cannot add a Google accounts with GOA

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

Bug description:
  On a freshly installed 20.04 system, going through the initial setup
  and I'm presented with the Online Accounts panel where I selected
  Google, entered my email and password. Then Google's 2-factor
  authentication kicks in and instructs me to check my phone. I do and
  approve the connection, but the online accounts page on the laptop
  never updates until it eventually asks if I want the authentication to
  be resent.

  There are two older bugs that looks like this - both are fix committed:
  - https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1687019
  - https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1175122

  Opening a new bug since the issue definitely exists and the other bugs
  have been fix committed for years.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-online-accounts 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 17 09:17:06 2019
  InstallationDate: Installed on 2019-12-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1877454] Re: openssh-server hangs with AuthorizedKeysCommand

[Jeremy Norris]

Also see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905226

** Bug watch added: Debian Bug tracker #905226
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905226

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

Title:
  openssh-server hangs with AuthorizedKeysCommand

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Xenial:
  Confirmed

Bug description:
  Please consider applying this change to openssh-server distributed in Xenial 
(16.04).
  Without it, sshd can sporadically hang when making use of the 
`AuthorizedKeysCommand` option.

  https://github.com/openssh/openssh-
  portable/commit/ddd3d34e5c7979ca6f4a3a98a7d219a4ed3d98c2

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

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

[Touch-packages] [Bug 1877580] [NEW] [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound at all

[Vasilis]

Public bug reported:

After upgrade from 19.10 to 20.04 (xubuntu) I've lost the sound on the 
headphones.
The internal loud speakers works ok when the headphones are not plugged in.

More specifically:
If I open the pavucontrol without the headphones plugged in I see that is 
correctly mentioning the output as Port: "Speakers (plugged-in)" and everything 
works ok, I have sound from the speakers.

The moment I plug in the headphones, for a fraction of a second I can
hear sound on the headphones, and then the output port switches to
"headphones" which is the moment I lose the sound.

The fraction that I hear the sound is when the jack is half-inserted and
I get the sound on one channel only. When is fully inserted, the
computer detects it and makes the switch.

I've tried also in alsamixer all possibilities I could imagine, playing
with mute/unmute and gain of each channel, with no success

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bnv1312 F pulseaudio
  bnv   21367 F alsamixer
 /dev/snd/pcmC0D0c:   bnv1312 F...m pulseaudio
 /dev/snd/pcmC0D0p:   bnv1312 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Fri May  8 15:41:08 2020
InstallationDate: Installed on 2019-08-08 (274 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
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/controlC0:  bnv1312 F pulseaudio
  bnv   21367 F alsamixer
 /dev/snd/pcmC0D0c:   bnv1312 F...m pulseaudio
 /dev/snd/pcmC0D0p:   bnv1312 F...m pulseaudio
Symptom_Jack: Black Headphone Out, Front
Symptom_Type: No sound at all
Title: [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound at 
all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/08/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.13.1
dmi.board.name: 0KP0FT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 7490
dmi.product.sku: 081C
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal

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

Title:
  [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound
  at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After upgrade from 19.10 to 20.04 (xubuntu) I've lost the sound on the 
headphones.
  The internal loud speakers works ok when the headphones are not plugged in.

  More specifically:
  If I open the pavucontrol without the headphones plugged in I see that is 
correctly mentioning the output as Port: "Speakers (plugged-in)" and everything 
works ok, I have sound from the speakers.

  The moment I plug in the headphones, for a fraction of a second I can
  hear sound on the headphones, and then the output port switches to
  "headphones" which is the moment I lose the sound.

  The fraction that I hear the sound is when the jack is half-inserted
  and I get the sound on one channel only. When is fully inserted, the
  computer detects it and makes the switch.

  I've tried also in alsamixer all possibilities I could imagine,
  playing with mute/unmute and gain of each channel, with no success

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bnv1312 F pulseaudio
bnv   21367 F alsamixer
   /dev/snd/pcmC0D0c:   bnv1312 F...m pulseaudio
   /dev/snd/pcmC0D0p:   bnv1312 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri May  8 15:41:08 2020
  InstallationDate: Installed on 2019-08-08 (274 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  

[Touch-packages] [Bug 1877496] Re: focal sshd snubs VX Connectbot

[gregrwm]

** Tags added: android sshd

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

Title:
  focal sshd snubs VX Connectbot

Status in openssh package in Ubuntu:
  New

Bug description:
  what is the subtle change to sshd such that now VX Connectbot no
  longer gets any response?  VX Connectbot can connect to the bionic
  sshd just fine, even if it's running on the focal kernel.  but gets no
  response from the focal sshd.  what's up with that?

  yes meanwhile it works fine to connect to the focal sshd from
  elsewhere eg from the bionic ssh client.  so what's the subtle snub to
  VX Connectbot?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssh-server 1:8.2p1-4
  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: Thu May  7 21:21:26 2020
  InstallationDate: Installed on 2020-03-15 (53 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
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 
255: Missing privilege separation directory: /run/sshd
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1877571] [NEW] bash is missing feature to use keyword if identically named alias exists

[Mikko Rantalainen]

Public bug reported:

If following command is run

(sleep 1 & sleep 1 & time wait); date

bash is supposed to run two commands in parallel, wait for both to
complete and the run third command.

However, if current environment has following alias configured

alias time='/usr/bin/time -v'

then the above command will fail with

   /usr/bin/time: cannot run wait: No such file or directory

and the final command is run without a wait.

Bash already has "command" to force interpretation as system command and
"builtin" to force interpretation as built-in command. However bash is
missing "keyword" to force interpretation as keyword.

One should be able to write

(sleep 1 & sleep 1 & keyword time wait); date

to force time to be interpreted as bash keyword.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bash 4.4.18-2ubuntu1.2
ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-lowlatency 5.3.18
Uname: Linux 5.3.0-51-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
CurrentDesktop: MATE
Date: Fri May  8 15:48:23 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-01-05 (488 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: bash
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  bash is missing feature to use keyword if identically named alias
  exists

Status in bash package in Ubuntu:
  New

Bug description:
  If following command is run

  (sleep 1 & sleep 1 & time wait); date

  bash is supposed to run two commands in parallel, wait for both to
  complete and the run third command.

  However, if current environment has following alias configured

  alias time='/usr/bin/time -v'

  then the above command will fail with

 /usr/bin/time: cannot run wait: No such file or directory

  and the final command is run without a wait.

  Bash already has "command" to force interpretation as system command
  and "builtin" to force interpretation as built-in command. However
  bash is missing "keyword" to force interpretation as keyword.

  One should be able to write

  (sleep 1 & sleep 1 & keyword time wait); date

  to force time to be interpreted as bash keyword.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bash 4.4.18-2ubuntu1.2
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-lowlatency 5.3.18
  Uname: Linux 5.3.0-51-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri May  8 15:48:23 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-01-05 (488 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: bash
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Clay]

apport information

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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1875944] xdpyinfo.txt

[Clay]

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1875944/+attachment/5368374/+files/xdpyinfo.txt

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

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

-- 
Mailing list: 

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

[Clay]

apport information

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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1875944] Xrandr.txt

[Clay]

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1875944/+attachment/5368373/+files/Xrandr.txt

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

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

[Clay]

I added the apport information with the system running 18.04. It isn't
possible to submit the info when on 20.04 as the display is unusable.

** Changed in: ubuntu-mate
   Status: New => Confirmed

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

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

[Touch-packages] [Bug 1875944] XorgLogOld.txt

[Clay]

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1875944/+attachment/5368372/+files/XorgLogOld.txt

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1875944] XorgLog.txt

[Clay]

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1875944/+attachment/5368371/+files/XorgLog.txt

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

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

[Clay]

apport information

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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

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

[Clay]

apport information

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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1875944] WifiSyslog.txt

[Clay]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1875944/+attachment/5368370/+files/WifiSyslog.txt

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

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

[Clay]

apport information

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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

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

[Clay]

apport information

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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

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

[Clay]

apport information

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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

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

[Clay]

apport information

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

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

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

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

[Clay]

apport information

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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1875944] LightdmLog.txt

[Clay]

apport information

** Attachment added: "LightdmLog.txt"
   
https://bugs.launchpad.net/bugs/1875944/+attachment/5368359/+files/LightdmLog.txt

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1875944] CurrentDmesg.txt

[Clay]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1875944/+attachment/5368355/+files/CurrentDmesg.txt

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

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

[Clay]

apport information

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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

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

[Clay]

apport information

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

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

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

[Touch-packages] [Bug 1875944] LightdmDisplayLog.txt

[Clay]

apport information

** Attachment added: "LightdmDisplayLog.txt"
   
https://bugs.launchpad.net/bugs/1875944/+attachment/5368358/+files/LightdmDisplayLog.txt

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1875944] DpkgLog.txt

[Clay]

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1875944/+attachment/5368356/+files/DpkgLog.txt

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

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

[Clay]

apport information

** Tags added: apport-collected bionic ubuntu

** Description changed:

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

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

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

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

[Clay]

apport information

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

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

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

[Touch-packages] [Bug 1838329] Re: Cryptswap periodically fails to mount at boot due to missing a udev notification

[Francis Ginther]

** Tags added: id-5eb44cf735b12c4b9b721452

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

Title:
  Cryptswap periodically fails to mount at boot due to missing a udev
  notification

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Focal:
  Triaged

Bug description:
  On some systems, cryptsetup-based encrypted swap partitions cause
  systemd to get stuck at boot. This is a timing-sensitive Heisenbug, so
  the rate of occurrence varies from one system to another. Some
  hardware will not experience the issue at all, others will only
  occasionally experience the issue, and then there are the unlucky who
  are unable to boot at all, no matter how many times they restart.

  The workaround is for the cryptsetup-generator to generate cryptswap
  service entries that call `udevadm trigger` after `mkswap`. This will
  ensure that the udev event is triggered, so that systemd is notified
  that the encrypt swap partition is ready to activate. This patch has
  already been submitted upstream to systemd, but it was not accepted
  because it is a workaround for the side effect of systemd not seeing
  the udev event upon creating the swap partition.

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

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

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

[Francis Ginther]

** Tags added: id-5eb42c73b200d93d8fb66e1e

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed-5.4 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

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

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

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

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

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

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

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

[Touch-packages] [Bug 1557157] Re: apparmor profile denied for saslauthd: /run/saslauthd/mux

[Andreas Hasenack]

** Tags added: bitesize

** Tags added: server-next

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

Title:
  apparmor profile denied for saslauthd: /run/saslauthd/mux

Status in openldap package in Ubuntu:
  Confirmed

Bug description:
  When using slapd with saslauthd the processes communicate via the
  {,/var}/run/saslauthd/mux socket (this is the default location for the
  saslauthd server from the sasl2-bin package in the
  /etc/default/saslauthd config), but the apparmor profile for
  usr.sbin.slapd does not allow access to this socket/file.

  Syslog message:
  apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd" 
name="/run/saslauthd/mux" pid=1880
  4 comm="slapd" requested_mask="r" denied_mask="r" fsuid=108 ouid=0

  
  Please add the following line to  /etc/apparmor.d/usr.sbin.slapd:
  /{,var/}run/saslauthd/mux rw,

  
  Ubuntu version: Ubuntu 14.04.4 LTS
  slapd version: 2.4.31-1+nmu2ubu

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

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