date:20200424

Thank you for your bug report.

In bionic
/usr/lib/libreoffice/share/basic/Access2Base/Application.xbalibreoffice-base

In focal
/usr/lib/libreoffice/share/basic/Access2Base/Application.xba
libreoffice-common

The -common in focal needs a Replaces/Breaks << version-in-which-the-
file-was-moved

Settings rls-ff-incoming since that can break upgrades

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

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

** Tags added: rls-ff-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874556

Title:
  package libreoffice-common 1:6.4.2-0ubuntu3 failed to install/upgrade:
  trying to overwrite
  '/usr/lib/libreoffice/share/basic/Access2Base/Application.xba', which
  is also in package libreoffice-base 1:6.0.7-0ubuntu0.18.04.10

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874639] Status changed to Confirmed

2020-04-24 Thread Ubuntu Kernel Bot

This change was made by a bot.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874639

Title:
  desktop pcs start to suspend by default

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874638] Re: error: cannot open `/boot/efi/EFI/ubuntu/grubx64.efi': Not a directory.

** Summary changed:

- While installing all late versions of Ubuntu and variants. on a nvme SSD. 
with Windows 10
+ error: cannot open `/boot/efi/EFI/ubuntu/grubx64.efi': Not a directory.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874638

Title:
  error: cannot open `/boot/efi/EFI/ubuntu/grubx64.efi': Not a
  directory.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874647] Comment bridged from LTC Bugzilla

--- Comment From mihaj...@de.ibm.com 2020-04-24 04:49 EDT---
I just realized that AMD SEV faces the equivalent issue, as can be seen in 
https://github.com/libvirt/libvirt/blob/master/docs/kbase/launch_security_sev.rst.
 The only difference is that for Secure Execution it's the kernel command line 
setting, wheras SEV uses a module parameter.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874647

Title:
  [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874509] Re: Keyboard not working while on desktop. Can't navigate through icons with arrows or letter buttons

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

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

** This bug has been marked a duplicate of bug 1868924
   a desktop launcher icon can not be activated by focusing and pressing enter

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874509

Title:
  Keyboard not working while on desktop. Can't navigate through icons
  with arrows or letter buttons

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874320] Re: error: cannot open `/boot/efi/EFI/ubuntu/grubx64.efi': Input/output error.

** Summary changed:

- i instal ubuntu but grub is not working and windows directly open grub is not 
shown and then i reinstall ubuntu it crashes and says fatal error so plz solve 
these errors thanku.
+ error: cannot open `/boot/efi/EFI/ubuntu/grubx64.efi': Input/output error.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874320

Title:
  error: cannot open `/boot/efi/EFI/ubuntu/grubx64.efi': Input/output
  error.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874642] Re: Touchpad is not working

Could you attach binary output file 'acpi.dump' of command `sudo apt
install acpica-tools && sudo acpidump -o acpi.dump`?

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874642

Title:
  Touchpad is not working

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874568] Re: Working config in eoan, bind9 fails after upgrade to fossa

2020-04-24 Thread Timo Aaltonen

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874568

Title:
  Working config in eoan, bind9 fails after upgrade to fossa

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874656] [NEW] on ubuntu 20.04, firefox does not start well

2020-04-24 Thread gerbier

Public bug reported:

I have upgraded from ubuntu 19.04 to 20.04 this morning.
and now firefox asks to restart.

I have also tested with a fresh firefox profile, and it is the same
problem.

the console shows the following error message
###!!! [Parent][MessageChannel] Error: 
(msgtype=0x370034,name=PContent::Msg_UpdateSharedData) Channel error: cannot 
send/recv

I have stopped apparmor (systemctl stop apparmor) and the problem remain

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 75.0+build3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: mfe_aac_100608112
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  eric   2799 F pulseaudio
 /dev/snd/controlC1:  eric   2799 F pulseaudio
BuildID: 20200403170909
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Fri Apr 24 10:45:06 2020
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2016-01-11 (1564 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
IpRoute:
 default via 192.168.0.254 dev wlo1 proto dhcp metric 600 
 169.254.0.0/16 dev wlo1 scope link metric 1000 
 192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.11 metric 600
KernLog:
 
Locales: extensions.sqlite corrupt or missing
PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
PrefSources: prefs.js
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=75.0/20200403170909 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
dmi.bios.date: 12/22/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SCF Ver. F.22
dmi.board.name: 1618
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 97.4A
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN
dmi.product.name: HP EliteBook 8560p
dmi.product.sku: WX788AV
dmi.product.version: A0001D02
dmi.sys.vendor: Hewlett-Packard
mtime.conffile..etc.apparmor.d.usr.bin.firefox: 2020-01-11T19:43:12.618232

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


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874656

Title:
  on ubuntu 20.04, firefox does not start well

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874543] Status changed to Confirmed

2020-04-24 Thread Ubuntu Kernel Bot

This change was made by a bot.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874543

Title:
  Artifacts when connected to an external 4K display

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874312] Re: error: cannot open `/boot/efi/EFI/ubuntu/grubx64.efi': Read-only file system.

the log has

Apr 22 19:38:13 ubuntu ubiquity: Installing for x86_64-efi platform.
Apr 22 19:38:23 ubuntu kernel: [  703.524619] FAT-fs (sda2): error, 
fat_free_clusters: deleting FAT entry beyond EOF
Apr 22 19:38:23 ubuntu kernel: [  703.524623] FAT-fs (sda2): Filesystem has 
been set read-only

looks like the filesystem was corrupted

** Summary changed:

- Something wrong
+ error: cannot open `/boot/efi/EFI/ubuntu/grubx64.efi': Read-only file system.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874312

Title:
  error: cannot open `/boot/efi/EFI/ubuntu/grubx64.efi': Read-only file
  system.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1748105] Re: port80 test in ubuntu_kvm_unit_tests failed with timeout

Typo in #8, recommended to bump it up to 900 seconds

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748105

Title:
  port80 test in ubuntu_kvm_unit_tests failed with timeout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1748105/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1057985] Re: grub-probe: error: cannot find a device for /boot (is /dev mounted?).

** Summary changed:

- grub instalation problem
+ grub-probe: error: cannot find a device for /boot (is /dev mounted?).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057985

Title:
  grub-probe: error: cannot find a device for /boot (is /dev mounted?).

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1860313] Re: megaraid_sas fails after rtcwake

2020-04-24 Thread Tommy Giesler

The issue appears to be fixed in Mainline Kernel 5.6.6.

So far, I have not done further research, when this fix was implemented
excatly. If needed, I can do further mainline or -rc tests.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860313

Title:
  megaraid_sas fails after rtcwake

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874642] Re: Touchpad is not working

btw, does kernel from
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1861610 work for you?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874642

Title:
  Touchpad is not working

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874641] Re: Can't create writecache LV

2020-04-24 Thread Vladimir Khristenko

** Description changed:

  #lvconvert --type writecache --cachesettings 'low_watermark=0 
high_watermark=10 writeback_jobs=2048' --cachevol cache ssd
-   WARNING: Unrecognised segment type writecache
-   Invalid argument for --type: writecache
-   Error during parsing of command line.
+   WARNING: Unrecognised segment type writecache
+   Invalid argument for --type: writecache
+   Error during parsing of command line.
  
  lvm2 package was build without key --with-writecache=internal
  
  #lvm version
-   LVM version: 2.03.07(2) (2019-11-30)
-   Library version: 1.02.167 (2019-11-30)
-   Driver version:  4.41.0
-   Configuration:   ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=${prefix}/include --mandir=${prefix}/share/man 
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu 
--libexecdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking --exec-prefix= 
--bindir=/bin --libdir=/lib/x86_64-linux-gnu --sbindir=/sbin 
--with-usrlibdir=/usr/lib/x86_64-linux-gnu --with-optimisation=-O2 
--with-cache=internal --with-device-uid=0 --with-device-gid=6 
--with-device-mode=0660 --with-default-pid-dir=/run 
--with-default-run-dir=/run/lvm --with-default-locking-dir=/run/lock/lvm 
--with-thin=internal --with-thin-check=/usr/sbin/thin_check 
--with-thin-dump=/usr/sbin/thin_dump --with-thin-repair=/usr/sbin/thin_repair 
--enable-applib --enable-blkid_wiping --enable-cmdlib --enable-dmeventd 
--enable-dbus-service --enable-lvmlockd-dlm --enable-lvmlockd-sanlock 
--enable-lvmpolld --enable-notify-dbus --enable-pkgconfig --enable-readline 
--enable-udev_rules --enable-udev_sync
+   LVM version: 2.03.07(2) (2019-11-30)
+   Library version: 1.02.167 (2019-11-30)
+   Driver version:  4.41.0
+   Configuration:   ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=${prefix}/include --mandir=${prefix}/share/man 
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu 
--libexecdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking --exec-prefix= 
--bindir=/bin --libdir=/lib/x86_64-linux-gnu --sbindir=/sbin 
--with-usrlibdir=/usr/lib/x86_64-linux-gnu --with-optimisation=-O2 
--with-cache=internal --with-device-uid=0 --with-device-gid=6 
--with-device-mode=0660 --with-default-pid-dir=/run 
--with-default-run-dir=/run/lvm --with-default-locking-dir=/run/lock/lvm 
--with-thin=internal --with-thin-check=/usr/sbin/thin_check 
--with-thin-dump=/usr/sbin/thin_dump --with-thin-repair=/usr/sbin/thin_repair 
--enable-applib --enable-blkid_wiping --enable-cmdlib --enable-dmeventd 
--enable-dbus-service --enable-lvmlockd-dlm --enable-lvmlockd-sanlock 
--enable-lvmpolld --enable-notify-dbus --enable-pkgconfig --enable-readline 
--enable-udev_rules --enable-udev_sync
  
  #lsmod | grep dm_writecache
  dm_writecache  36864  0
  
  #lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  
  #apt-cache policy lvm2
  lvm2:
-   Installed: 2.03.07-1ubuntu1
-   Candidate: 2.03.07-1ubuntu1
-   Version table:
-  *** 2.03.07-1ubuntu1 500
- 500 http://ua.archive.ubuntu.com/ubuntu focal/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 2.03.07-1ubuntu1
+   Candidate: 2.03.07-1ubuntu1
+   Version table:
+  *** 2.03.07-1ubuntu1 500
+ 500 http://ua.archive.ubuntu.com/ubuntu focal/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  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: pass
  Date: Fri Apr 24 07:48:49 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)
+ 
+ 
+ # lvs
+   LVVG  Attr   LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync 
Convert
+   cache ssd -wi-a-  <5.00g

+   data  ssd -wi-a- <10.00g

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874641

Title:
  Can't create writecache LV

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'

@Brian, please file another bug for your thinbook 14iil and attach
result of `sudo acpidump | grep -C3 ELAN` there as well.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861610

Title:
  'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874343] Re: Thunar hangs for several seconds on first launch

Is this bug specific to a view (icon, detailed, list) or side pane view
(shortcuts, tree)? Do you maybe have bookmarks to remote locations, or
(broken) symbolic links in your home folder?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874343

Title:
  Thunar hangs for several seconds on first launch

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874663] [NEW] package lirc 0.10.1-6.1 failed to install/upgrade: installed lirc package post-installation script subprocess returned error exit status 1

2020-04-24 Thread Stephen Worthington

Public bug reported:

root@vb-Ubuntu-20:/etc/lirc# lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04
root@vb-Ubuntu-20:/etc/lirc# apt-cache policy lirc
lirc:
  Installed: 0.10.1-6.1
  Candidate: 0.10.1-6.1
  Version table:
 *** 0.10.1-6.1 500
500 http://nz.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status


I installed Ubuntu 20.04 beta in a VirtualBox virtual machine a few days ago.  
Today (after I got the message that 20.04 has been released), I updated the vm 
to the latest packages, then tried:

apt install lirc

and got this:

root@vb-Ubuntu-20:/home/stephen# apt install lirc
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  libftdi1-2 liblirc0 libportaudio2 libusb-0.1-4
Suggested packages:
  lirc-compat-remotes lirc-drv-irman lirc-doc lirc-x setserial ir-keytable
Recommended packages:
  gir1.2-vte
The following NEW packages will be installed:
  libftdi1-2 liblirc0 libportaudio2 libusb-0.1-4 lirc
0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 654 kB of archives.
After this operation, 3,178 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://nz.archive.ubuntu.com/ubuntu focal/universe amd64 libftdi1-2 amd64 
1.4-2build2 [25.6 kB]
Get:2 http://nz.archive.ubuntu.com/ubuntu focal/universe amd64 libportaudio2 
amd64 19.6.0-1build1 [65.4 kB]
Get:3 http://nz.archive.ubuntu.com/ubuntu focal/main amd64 libusb-0.1-4 amd64 
2:0.1.12-32 [17.4 kB]
Get:4 http://nz.archive.ubuntu.com/ubuntu focal/main amd64 liblirc0 amd64 
0.10.1-6.1 [82.8 kB]
Get:5 http://nz.archive.ubuntu.com/ubuntu focal/universe amd64 lirc amd64 
0.10.1-6.1 [463 kB]
Fetched 654 kB in 0s (2,455 kB/s)
Selecting previously unselected package libftdi1-2:amd64.
(Reading database ... 261704 files and directories currently installed.)
Preparing to unpack .../libftdi1-2_1.4-2build2_amd64.deb ...
Unpacking libftdi1-2:amd64 (1.4-2build2) ...
Selecting previously unselected package libportaudio2:amd64.
Preparing to unpack .../libportaudio2_19.6.0-1build1_amd64.deb ...
Unpacking libportaudio2:amd64 (19.6.0-1build1) ...
Selecting previously unselected package libusb-0.1-4:amd64.
Preparing to unpack .../libusb-0.1-4_2%3a0.1.12-32_amd64.deb ...
Unpacking libusb-0.1-4:amd64 (2:0.1.12-32) ...
Selecting previously unselected package liblirc0:amd64.
Preparing to unpack .../liblirc0_0.10.1-6.1_amd64.deb ...
Unpacking liblirc0:amd64 (0.10.1-6.1) ...
Selecting previously unselected package lirc.
Preparing to unpack .../lirc_0.10.1-6.1_amd64.deb ...
Unpacking lirc (0.10.1-6.1) ...
Setting up libportaudio2:amd64 (19.6.0-1build1) ...
Setting up libusb-0.1-4:amd64 (2:0.1.12-32) ...
Setting up libftdi1-2:amd64 (1.4-2build2) ...
Setting up liblirc0:amd64 (0.10.1-6.1) ...
Setting up lirc (0.10.1-6.1) ...
Job for lircd.service failed because a fatal signal was delivered causing the 
control process to dump core.
See "systemctl status lircd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript lircd, action "start" failed.
● lircd.service - Flexible IR remote input/output application support
 Loaded: loaded (/lib/systemd/system/lircd.service; disabled; vendor 
preset: enabled)
 Active: failed (Result: core-dump) since Fri 2020-04-24 20:52:00 NZST; 
36ms ago
   Docs: man:lircd(8)
 http://lirc.org/html/configure.html
Process: 10762 ExecStart=/usr/sbin/lircd --nodaemon (code=dumped, 
signal=SEGV)
   Main PID: 10762 (code=dumped, signal=SEGV)

Apr 24 20:52:00 vb-Ubuntu-20 systemd[1]: Starting Flexible IR remote 
input/output application support...
Apr 24 20:52:00 vb-Ubuntu-20 lircd[10762]: Warning: cannot open 
/etc/lirc/lirc_options.conf
Apr 24 20:52:00 vb-Ubuntu-20 lircd-0.10.1[10762]: Info: lircd:  Opening log, 
level: Info
Apr 24 20:52:00 vb-Ubuntu-20 lircd-0.10.1[10762]: Notice: Version: lircd 0.10.1
Apr 24 20:52:00 vb-Ubuntu-20 lircd-0.10.1[10762]: Notice: System info: Linux 
vb-Ubuntu-20 5.4.0-26-generic #30-Ubuntu
 SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Apr 24 20:52:00 vb-Ubuntu-20 systemd[1]: lircd.service: Main process exited, 
code=dumped, status=11/SEGV
Apr 24 20:52:00 vb-Ubuntu-20 systemd[1]: lircd.service: Failed with result 
'core-dump'.
Apr 24 20:52:00 vb-Ubuntu-20 systemd[1]: Failed to start Flexible IR remote 
input/output application support.
dpkg: error processing package lirc (--configure):
 installed lirc package post-installation script subprocess returned error exit 
status 1
Processing triggers for systemd (245.4-4ubuntu3) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for libc-bin (2.31-0ubuntu9) ...
Errors were encountered while processing:
 lirc
E: Sub-process /usr/bin/dpkg returned an error code (1)

This appears to be caused by the /etc/lirc/lirc_options.conf file not
being present.  When I copy /etc/lirc/lirc_options.conf.dist to
/etc

[Bug 1874644] Comment bridged from LTC Bugzilla

--- Comment From shiva...@in.ibm.com 2020-04-24 05:12 EDT---
There are quite a few changes. Can you upgrade instead ? This is IBM Power 
specific package and wont affect other architectures.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874644

Title:
  Update ppc64-diag package to v2.7.6

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874660] [NEW] Please make an "update in progress" message for snap updates

2020-04-24 Thread Richard Baka

Public bug reported:

Distro is Kubuntu 20.04
I got a notification message about the new Chromium version or about the 
Chromium update (I don't remember precisely). I wanted to restart the browser 
to do something helping the update so I closed it then I couldn't find the 
starter icon of its.

sudo snap refresh said
snap "chromium" is already installed, see 'snap help refresh'

chromium command said chromium is not installed.

Then later I could start it again using the chromium command.

Please create a better notification about the upgrading process not just
about the update possibility!

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874660

Title:
  Please make an "update in progress" message for snap updates

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874662] [NEW] Corrupted installation medium

2020-04-24 Thread Jean-Baptiste Lallement

Public bug reported:

If you have been redirected to this page, it means that your
installation of Ubuntu or a flavour failed.

If you look in the log file /var/log/syslog, you'll see messages like
the above:

Apr 24 00:01:40 ubuntu kernel: [  329.409695] SQUASHFS error: zlib 
decompression failed, data probably corrupt
Apr 24 00:01:40 ubuntu kernel: [  329.409704] SQUASHFS error: 
squashfs_read_data failed to read block 0x37545

This failure is usually caused by bad ISO download, corrupted install
media, or device failure.

We suggest you verify your ISO download, and note the validation of your
ISO before install to ensure a good download & write.

You may also find this tutorial useful: https://ubuntu.com/tutorials
/tutorial-how-to-verify-ubuntu

If you experienced an issue during installation and think it is not
caused by a corrupted installation media, do not hesitate to report a
bug by running the following command from a terminal:

$ ubuntu-bug ubiquity

Thanks for using Ubuntu.

** Affects: ubuntu
 Importance: Medium
 Status: Triaged


** Tags: do-not-close-this-report

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

** Changed in: ubuntu
   Importance: Undecided => Medium

** Tags added: do-not-close-this-report

** Description changed:

  If you have been redirected to this page, it means that your
  installation of Ubuntu or a flavour failed.
  
  If you look in the log file /var/log/syslog, you'll see messages like
  the above:
  
  Apr 24 00:01:40 ubuntu kernel: [  329.409695] SQUASHFS error: zlib 
decompression failed, data probably corrupt
  Apr 24 00:01:40 ubuntu kernel: [  329.409704] SQUASHFS error: 
squashfs_read_data failed to read block 0x37545
  
  This failure is usually caused by bad ISO download, corrupted install
  media, or device failure.
  
  We suggest you verify your ISO download, and note the validation of your
  ISO before install to ensure a good download & write.
  
+ You may also find this tutorial useful: https://ubuntu.com/tutorials
+ /tutorial-how-to-verify-ubuntu#1-overview
+ 
  If you experienced an issue during installation and think it is not
  caused by a corrupted installation media, do not hesitate to report a
  bug by running the following command from a terminal:
  
  $ ubuntu-bug ubiquity
  
  Thanks for using Ubuntu.

** Description changed:

  If you have been redirected to this page, it means that your
  installation of Ubuntu or a flavour failed.
  
  If you look in the log file /var/log/syslog, you'll see messages like
  the above:
  
  Apr 24 00:01:40 ubuntu kernel: [  329.409695] SQUASHFS error: zlib 
decompression failed, data probably corrupt
  Apr 24 00:01:40 ubuntu kernel: [  329.409704] SQUASHFS error: 
squashfs_read_data failed to read block 0x37545
  
  This failure is usually caused by bad ISO download, corrupted install
  media, or device failure.
  
  We suggest you verify your ISO download, and note the validation of your
  ISO before install to ensure a good download & write.
  
  You may also find this tutorial useful: https://ubuntu.com/tutorials
- /tutorial-how-to-verify-ubuntu#1-overview
+ /tutorial-how-to-verify-ubuntu
  
  If you experienced an issue during installation and think it is not
  caused by a corrupted installation media, do not hesitate to report a
  bug by running the following command from a terminal:
  
  $ ubuntu-bug ubiquity
  
  Thanks for using Ubuntu.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874662

Title:
  Corrupted installation medium

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874640] Re: Errors while installing Ubuntu 20.04

2020-04-24 Thread MaximAL

First time I was using Ubuntu media creation tool. And the installation
failed.

Then I used RuFus on Windows. And the same flash drive went okay.

I had the same issue on previous Ubuntu (19.10), installation wend okay
only when using Rufus and not the Ubuntu bundled tool.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874640

Title:
  Errors while installing Ubuntu 20.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1872941] Comment bridged from LTC Bugzilla

--- Comment From cborn...@de.ibm.com 2020-04-24 05:09 EDT---
So now a stupid question:
Obviously the new installer also has kernel, ramdisk parmfile
see
https://ubuntu-on-big-iron.blogspot.com/2020/03/glimpse-at-subiquity.html

why dont you just put THOSE NEW files on the webpage on the installer location?
Then virt-install would continue to work (maybe small fixes) and you would 
redirect people to the new installer?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872941

Title:
  [Ubuntu 20.04] virt-install fails to detect path after images folder
  name has changed

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874661] [NEW] networkd sometimes doesn't set mtu received by dhcp

2020-04-24 Thread Christoph Ziebuhr

Public bug reported:

I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 
242-7ubuntu3.7.
GCE has mtu 1460, set by dhcp. After having networking issues, I figured out 
that the mtu on the interface was sometimes incorrectly set to 1500.
I manually changed it to 1420 to have a working system again and enabled 
debugging for systemd-networkd.

Log (filtered for ens4, some columns removed for better readability):
09:51:00 ens4: New device has no master, continuing without
09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
09:51:00 ens4: Link 2 added
09:51:00 ens4: udev initialized link
09:51:00 ens4: Saved original MTU: 1420
09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever)
09:51:00 ens4: Gained IPv6LL
09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s)
09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a
09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: n/a, 
prefsrc: n/a
09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a
09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
09:51:00 ens4: Link state is up-to-date
09:51:00 ens4: found matching network 
'/run/systemd/network/10-netplan-ens4.network'
09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0'
09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0'
09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0'
09:51:00 ens4: Started LLDP.
09:51:00 ens4: Setting address genmode for link
09:51:00 ens4: Setting address genmode done.
09:51:00 ens4: Removing address 10.164.0.2
09:51:00 ens4: Acquiring DHCPv4 lease
09:51:00 ens4: Discovering IPv6 routers
09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s)
09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1
09:51:00 ens4: Setting MTU: 1460
09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0'
09:51:00 ens4: IPv6 successfully enabled
09:51:00 ens4: Setting MTU done.
09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d)
09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
09:51:00 ens4: Configured
21:50:59 ens4: DHCP lease lost
21:50:59 ens4: Removing address 10.164.0.2
21:50:59 ens4: Setting MTU: 1420
21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0'
21:50:59 ens4: IPv6 successfully enabled
21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1
21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s)
21:50:59 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
21:50:59 ens4: Setting MTU done.
21:50:59 ens4: Adding address: 10.164.0.2/32 (valid for 1d)
21:50:59 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
21:50:59 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
21:50:59 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
21:50:59 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
21:50:59 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
21:50:59 ens4: Configured

On dhcp renew (09:51:00), mtu got properly changed to 1460.
On next dhcp renew (21:50:59) it got changed back to previous value 1420.
In all cases, /run/systemd/netif/leases/2 correctly contained MTU=1460.

There have been some changes to mtu handling in the past, I assume this
is a regression, potentially from
https://github.com/systemd/systemd/issues/12552 or
https://github.com/systemd/systemd/issues/6593.

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

** Description changed:

  I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 
242-7ubuntu3.7.
  GCE has mtu 1460, set by dhcp. After having networking issues, I figured out 
that the mtu on the interface was sometimes incorrectly set to 1500.
  I manually changed it to 1420 to have a working system again and enabled 
debugging for systemd-networkd.
  
- Log (filtered for ens4):
- Apr 23 09:51:00 host systemd-networkd[1737]: ens4: New device

[Bug 1874606] Re: Cannot import .ovpn file (The Add button is greyed out) but can import via command-line

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

Thanks, that does sound like bug #1810660 then, marking as duplicate

** This bug has been marked a duplicate of bug 1810660
   vpn configuration requires to enter a gateway

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874606

Title:
  Cannot import .ovpn file (The Add button is greyed out) but can import
  via command-line

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874422] Comment bridged from LTC Bugzilla

--- Comment From heinz-werner_se...@de.ibm.com 2020-04-24 05:22 EDT---
This request will be rejected. I will close it on IBM side. No further action 
are required by Canonial.

DES will not be used anymore...

--- Comment From heinz-werner_se...@de.ibm.com 2020-04-24 05:22 EDT---
IBM bugzilla status-> closed, not requested anymore

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874422

Title:
  [Ubuntu 20.04] FIPS: libica: TDES key check must change

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1874642] Re: Touchpad is not working

2020-04-24 Thread Muhannad

Hi,

You may excuse me cause im new to Linux in general, per your request
below, how can i implement (or install) the kernel you referring to?



From: boun...@canonical.com  on behalf of You-Sheng Yang 
<1874...@bugs.launchpad.net>
Sent: Friday, April 24, 2020 12:10 PM
To: muhannad_ali...@hotmail.com 
Subject: [Bug 1874642] Re: Touchpad is not working

btw, does kernel from
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1861610 work for you?

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1874642

Title:
  Touchpad is not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HI,

  I've installed kubuntu 20.04 and found that the touch pad is not working, my 
laptop is lenovo ideapad S340
  I have tried the reporting guide line in :

  https://wiki.ubuntu.com/DebuggingTouchpadDetection/evtest
  and
  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#General_information_before_filing_the_bug
  with no luck
  Any suggestions?

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  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/controlC0:  muhannad   1133 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Apr 24 10:49:35 2020
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Kubuntu 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 5986:2115 Acer, Inc Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp.
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81WL
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=8431a97f-7667-473b-b32e-3ce9f70938eb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/03/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CUCN62WW(V3.04)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S340-15IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrCUCN62WW(V3.04):bd01/03/2020:svnLENOVO:pn81WL:pvrLenovoIdeaPadS340-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-15IIL:
  dmi.product.family: IdeaPad S340-15IIL
  dmi.product.name: 81WL
  dmi.product.sku: LENOVO_MT_81WL_BU_idea_FM_IdeaPad S340-15IIL
  dmi.product.version: Lenovo IdeaPad S340-15IIL
  dmi.sys.vendor: LENOVO

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874642

Title:
  Touchpad is not working

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873268] Re: Enable Xfce 4.14 folder thumbnailing

** Package changed: thunar (Ubuntu) => tumbler (Ubuntu)

** Also affects: xubuntu-default-settings (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873268

Title:
  Enable Xfce 4.14 folder thumbnailing

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1872305] Re: keyboard layouts do not change

** Package changed: thunar (Ubuntu) => xfce4-settings (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872305

Title:
  keyboard layouts do not change

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures

2020-04-24 Thread Christian Ehrhardt 

The case with the module parameter in SEV needs a fix similar to

https://libvirt.org/git/?p=libvirt.git;a=commit;h=b183a75319b90d0af5512be513743e1eab950612
as it can be re-loaded at any time.

Essentially the checks in virQEMUCapsLoadCache check qemu/kernel version and
many other things.
They also check microcode version ...

I think the decision there can be two ways, either "on any reboot we need to
refresh caps" which makes the code small but probably also wastes quite some
refreshes that were not needed.
Or it could along all the versions that it checks also keep a full string of
/proc/cmdline and compare it. If changed it needs to be refreshed.

I agree to Frank that this should be reported upstream.
No matter if you or I write a fix, it needs to go upstream then - so a bug
tracker there can't hurt.
OTOH you can as well start right away with a RFC patch there if you have
something prepared already - there is no "strict need" for an upstream bug,
only if you hope someone there will fix it for you.

Since workarounds are available the prio is medium IMHO, eager to see
what upstream thinks.

P.S. Even if you have no patch, it would be great if you (as the
affected) would kick off the discussion upstream. Please provide a link
here to the mailing list entry.

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

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

** Changed in: libvirt (Ubuntu)
Importance: Undecided => Medium

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874647

Title:
[Ubuntu 20.04] Stale libvirt cache leads to VM startup failures

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

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1836235] Re: ubuntu-bug thunar

Not a bug in Thunar.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836235

Title:
  ubuntu-bug thunar

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874422] Re: [Ubuntu 20.04] FIPS: libica: TDES key check must change

2020-04-24 Thread Frank Heimes

Ok, closing ticket as invalid.

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

** Changed in: ubuntu-z-systems
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874422

Title:
  [Ubuntu 20.04] FIPS: libica: TDES key check must change

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1874642] Re: Touchpad is not working

2020-04-24 Thread Muhannad

Ok ,  i added the PPA from the kernel:


sudo add-apt-repository ppa:vicamo/ppa-1861610
sudo apt-get update

 and restarted the laptop, then from system setting - Touch pad, still
giving me "no touch pad found"


From: Muhannad Al Issa 
Sent: Friday, April 24, 2020 12:25 PM
To: Bug 1874642 <1874...@bugs.launchpad.net>
Subject: Re: [Bug 1874642] Re: Touchpad is not working

Hi,

You may excuse me cause im new to Linux in general, per your request
below, how can i implement (or install) the kernel you referring to?



From: boun...@canonical.com  on behalf of You-Sheng Yang 
<1874...@bugs.launchpad.net>
Sent: Friday, April 24, 2020 12:10 PM
To: muhannad_ali...@hotmail.com 
Subject: [Bug 1874642] Re: Touchpad is not working

btw, does kernel from
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1861610 work for you?

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1874642

Title:
  Touchpad is not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HI,

  I've installed kubuntu 20.04 and found that the touch pad is not working, my 
laptop is lenovo ideapad S340
  I have tried the reporting guide line in :

  https://wiki.ubuntu.com/DebuggingTouchpadDetection/evtest
  and
  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#General_information_before_filing_the_bug
  with no luck
  Any suggestions?

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  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/controlC0:  muhannad   1133 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Apr 24 10:49:35 2020
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Kubuntu 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 5986:2115 Acer, Inc Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp.
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81WL
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=8431a97f-7667-473b-b32e-3ce9f70938eb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/03/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CUCN62WW(V3.04)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S340-15IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrCUCN62WW(V3.04):bd01/03/2020:svnLENOVO:pn81WL:pvrLenovoIdeaPadS340-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-15IIL:
  dmi.product.family: IdeaPad S340-15IIL
  dmi.product.name: 81WL
  dmi.product.sku: LENOVO_MT_81WL_BU_idea_FM_IdeaPad S340-15IIL
  dmi.product.version: Lenovo IdeaPad S340-15IIL
  dmi.sys.vendor: LENOVO

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


** Attachment added: "Screenshot_20200424_123735.png"
   
https://bugs.launchpad.net/bugs/1874642/+attachment/5359193/+files/Screenshot_20200424_123735.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874642

Title:
  Touchpad is not working

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874667] [NEW] Upgrade to 20 LTS not working

2020-04-24 Thread Mihai Suta

Public bug reported:

Upgrade from 18.04. LTS to 20.04 LTS keeps crashing

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.37
ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
Uname: Linux 4.15.0-96-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 11:35:24 2020
InstallationDate: Installed on 2018-05-16 (708 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2020-04-24 (0 days ago)
VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
VarLogDistupgradeTermlog:

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic dist-upgrade

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874667

Title:
  Upgrade to 20 LTS not working

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()

2020-04-24 Thread Robert Ancell

** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862553

Title:
  gnome-control-center crashed with SIGSEGV in
  cc_panel_get_title_widget()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874655] Re: After suspend / resume, WiFi does not reconnect automatically to an hidden access point

Thank you for your bug report. gnome-control-center is just a configuration 
interface and doesn't have any service / doesn't handle any action when not 
open so it seems the issue there would rather be with the network service, 
reassigning
Could you get a 'journalctl -b 0' log after getting the issue and add to the 
bug while specifying at what time you resumed

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

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

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874655

Title:
  After suspend / resume, WiFi does not reconnect automatically to an
  hidden access point

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874113] Re: IPv6 not working

2020-04-24 Thread Tomi Malkki

Seems that IPv6 autoconf/DHCP is broken

IPv6 works when using static netplan configuration

** Package changed: linux (Ubuntu) => netplan.io (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874113

Title:
  IPv6 not working

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874671] [NEW] UBi-partman crashed while installing 20.04 on 204 MBP

2020-04-24 Thread Ryan

Public bug reported:

Tried installing Ubuntu 20.04 on a mid-204 MBP, file checks showed 1
error. Installer crashed when trying to install. No other partitions on
this MBP

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckMismatches: ./casper/filesystem.squashfs
CasperMD5CheckResult: fail
CasperVersion: 1.445
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 16:42:49 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity pci=noaer quiet splash ---
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu

** Attachment added: "syslog"
   https://bugs.launchpad.net/bugs/1874671/+attachment/5359200/+files/syslog

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874671

Title:
  UBi-partman crashed while installing 20.04 on 204 MBP

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1844771] Re: Thunar interactive search sometimes stops accepting input after one character

Fixed in Ubuntu 20.04.

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844771

Title:
  Thunar interactive search sometimes stops accepting input after one
  character

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874547] Re: Super key does not open activities overview

2020-04-24 Thread Eduard Santamaria

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

Yes, sounds pretty much like it. I have two keyboard layouts configured
(German and Catalan). Now I realized that the Super key works when the
active layout is the same as the top one in the Region & Language
settings. If I change the order in the settings dialog, then it will
work only for the language that was moved to the top.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874547

Title:
  Super key does not open activities overview

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1834014] Re: thunar crashed with SIGSEGV

Thunar 1.8.14 is available in the 20.04 repository.

https://git.xfce.org/xfce/thunar/tree/NEWS?h=xfce-4.14

** Changed in: thunar (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834014

Title:
  thunar crashed with SIGSEGV

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874547] Re: Super key does not open activities overview

2020-04-24 Thread Eduard Santamaria

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

Ok, someone already described that behavior, so it must be the same.
Thank you and sorry for not noticing it before.

** This bug has been marked a duplicate of bug 1871913
   super key does not work with secondary keyboard layout

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874547

Title:
  Super key does not open activities overview

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874649] Comment bridged from LTC Bugzilla

--- Comment From shiva...@in.ibm.com 2020-04-24 05:39 EDT---
Can you cherrypick these commits?

2f133f2 servicelog: Validates fgets return value
f0b03ba servicelog: Validates return value of some servicelog api's
3d2d413 servicelog: Close opened service descriptor on failure of api's

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874649

Title:
  Update servicelog package to version v1.1.15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874673] [NEW] lua-http is missing lua-binaryheap dependency

2020-04-24 Thread Tomas Krizek

Public bug reported:

Upstream lua-http has a dependency on binaryheap >= 0.3.
See https://github.com/daurnimator/lua-http#dependencies

The package lua-http-0.3-1 for Ubuntu 20.04 is missing this dependency, 
resulting in
error such as:
error: /usr/share/lua/5.1/http/cookie.lua:7: module 'binaryheap' not found

Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958665

** Affects: lua-http (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874673

Title:
  lua-http is missing lua-binaryheap dependency

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871733] Re: [20.04 Focal Fossa] Light menus when dark mode is active

2020-04-24 Thread Tofik Sonono

I also experience this

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871733

Title:
  [20.04 Focal Fossa] Light menus when dark mode is active

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874646] Comment bridged from LTC Bugzilla

--- Comment From shiva...@in.ibm.com 2020-04-24 05:45 EDT---
Can you cherry pick these ?

9376ee6 udev rules: don't generate multiple vpdupdate events for SCSI/NVMe
e82ee3b udev rules: more software devices to ignore
1ed44e6 udev rules: don't touch run.vpdupdate for ignored devices

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874646

Title:
  Update libvpd package to v2.2.7

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821589] Re: thunar crashed with SIGSEGV

Thunar 1.8.14 is available in the 20.04 repository.

https://git.xfce.org/xfce/thunar/tree/NEWS?h=xfce-4.14

** Changed in: thunar (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821589

Title:
  thunar crashed with SIGSEGV

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1802264] Re: Thunar 1.8.1 core dumps under Ubuntu Wayland

** Changed in: thunar (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802264

Title:
  Thunar 1.8.1 core dumps under Ubuntu Wayland

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829921] Re: thunar crashed with SIGSEGV

2020-04-24 Thread Karol „Zal” Zalewski via ubuntu-bugs

Thunar 1.8.14 is available in the 20.04 repository.

https://git.xfce.org/xfce/thunar/tree/NEWS?h=xfce-4.14

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829921

Title:
  thunar crashed with SIGSEGV

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1863258] Re: [Snap] Install the widevine binary upon request in Chromium snap

2020-04-24 Thread Michel-Ekimia

** Summary changed:

- Install the widevine binary upon request in Chromium snap
+ [Snap] Install the widevine binary upon request in Chromium snap

** Summary changed:

- [Snap] Install the widevine binary upon request in Chromium snap
+ [Snap] Install the widevine binary upon request in Chromium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863258

Title:
  [Snap] Install the widevine binary upon request in Chromium

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-04-24 Thread hugh chao

verified pulseaudio version - 1:11.1-1ubuntu7.6 in a hp sff[0] which has
dual front jacks, works well, didn't find any Regression potential.


[0]https://www8.hp.com/h20195/v2/GetPDF.aspx/4AA7-5395EEAP.pdf

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874680] [NEW] Epson XP-8500 a 4 alimentations possibles, cassette 1, cassette 2, alimentation arrière et CD. Le pilote gutenprint ne mentionne que bac arrière, bac avant et imrimer un cd !

2020-04-24 Thread Floquet René

Public bug reported:

Il n'est pas possible avec le printer-driver-gutenprint d'adresser le
bac avant (cassette 1) qui  sert pour l'impression de photos par
exemple.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: printer-driver-gutenprint 5.3.3-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
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 11:53:40 2020
InstallationDate: Installed on 2019-05-29 (330 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: gutenprint
UpgradeStatus: Upgraded to focal on 2020-04-19 (4 days ago)

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


** Tags: amd64 apport-bug focal wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874680

Title:
  Epson XP-8500 a 4 alimentations possibles,  cassette 1, cassette 2,
  alimentation arrière et CD. Le pilote gutenprint ne mentionne que bac
  arrière, bac avant et imrimer un cd !

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873922] Re: 20.04 not compatible with virtualbox-guest-x11: Fails changing display

I have the same issue with Windows 10 (as host), VirtualBox 6.1.6
r137129m, VirtualBox Guest Utils 6.1.6 and Ubuntu 20.04 LTS official
release (as guest, upgraded with `do-release-upgrade -d` from 18.04
LTS).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873922

Title:
  20.04 not compatible with virtualbox-guest-x11: Fails changing display

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871913] Re: super key does not work with secondary keyboard layout

2020-04-24 Thread Pedro Teixeira

I also tried different configs in gnome-tweaks for the Alt/Win key
behavior (under Additional Layout Options) but it did not seem to make
any difference.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871913

Title:
  super key does not work with secondary keyboard layout

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1863258] Re: [Snap] Install the widevine binary upon request in Chromium

2020-04-24 Thread Michel-Ekimia

Brave have implented their own Widevine module downloader :

https://github.com/brave/brave-browser/pull/3300/files

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863258

Title:
  [Snap] Install the widevine binary upon request in Chromium

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873922] Re: 20.04 not compatible with virtualbox-guest-x11: Fails changing display

2020-04-24 Thread Launchpad Bug Tracker

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873922

Title:
  20.04 not compatible with virtualbox-guest-x11: Fails changing display

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874437] Re: Intel 82579LM [8086:1502] Subsystem [1028:0498] Network driver for e1000 card not loaded on boot on beta 20.04

2020-04-24 Thread Naveed Khan

Hi

I downloaded the released 20.04 Desktop image. I get the same behaviour.
With no additional cards plugged in I do not get a network.
When I attach a WiFi USB - I get a wifi network
It says the wired card has no cable.

On main system boot
Once I plug in a USB WiFI card - the wired network and wireless become 
available.
A bug in NetworkManager?


I havr attacted to typescripts one when booted from istall media and other on 
the installed system

** Attachment added: "I havr attacted to typescripts one when booted from 
istall media and other on the installed system"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874437/+attachment/5359213/+files/typescript-pre-and-post-boot

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874437

Title:
  Intel 82579LM [8086:1502] Subsystem [1028:0498]  Network driver for
  e1000 card not loaded on boot on beta 20.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1856410] Re: ubiquity prompts for a MOK password that it then does not use

2020-04-24 Thread Didier Roche

Confirming

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856410

Title:
  ubiquity prompts for a MOK password that it then does not use

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871913] Re: super key does not work with secondary keyboard layout

2020-04-24 Thread Pedro Teixeira

I am facing the same problem. 
Can confirm  that only input 1 works regardless of language. And that keyboard 
shortcuts with Super work regardless.

Here is my extra 2 cents:

When I go into 'Show keyboard layout' to see which keypresses are registered, 
the left super key is not registered but the right one is.
 
One more thing: if I change the activities overview to be triggered by the 
right super key instead of left (via gnome-tweaks), then the left super key 
will be registered but the right super key will not.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871913

Title:
  super key does not work with secondary keyboard layout

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874647] Comment bridged from LTC Bugzilla

--- Comment From boris_fiuczyn...@de.ibm.com 2020-04-24 06:03 EDT---
(In reply to comment #8)
> The case with the module parameter in SEV needs a fix similar to
> https://libvirt.org/git/?p=libvirt.git;a=commit;
> h=b183a75319b90d0af5512be513743e1eab950612
> as it can be re-loaded at any time.
>
> Essentially the checks in virQEMUCapsLoadCache check qemu/kernel version and
> many other things.
> They also check microcode version ...
>
> I think the decision there can be two ways, either "on any reboot we need to
> refresh caps" which makes the code small but probably also wastes quite some
> refreshes that were not needed.
> Or it could along all the versions that it checks also keep a full string of
> /proc/cmdline and compare it. If changed it needs to be refreshed.
>
> I agree to Frank that this should be reported upstream.
> No matter if you or I write a fix, it needs to go upstream then - so a bug
> tracker there can't hurt.
> OTOH you can as well start right away with a RFC patch there if you have
> something prepared already - there is no "strict need" for an upstream bug,
> only if you hope someone there will fix it for you.
>
> Since workarounds are available the prio is medium IMHO, eager to see what
> upstream thinks.
>
> P.S. Even if you have no patch, it would be great if you (as the affected)
> would kick off the discussion upstream. Please provide a link here to the
> mailing list entry.

I agree with you. Please regard this as a tracking bug to pick up the
upstream commits.

We (IBM) will prepare a write up for Secure Execution comparable to what
exists for AMD SEV and also provide a fix for the cap caching invalidity
problem. If that is going to look similar for what was done for nesting
needs to be seen but it is a good starting point. Thanks for providing
it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874647

Title:
  [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1505670] Re: "uncaptured python exception"

2020-04-24 Thread Rolf Leggewie

Andreas, I cannot confirm this for focal and I believe you should have
asked for confirmation from others before closing.

Code inspection suggests nothing was done to fix this bug, but of course
it was possible that a change in asyncore.py fixed this.  That does not
look to be the case.  I tested the patch from #4 again, it works and I
believe it should be applied in focal and bionic.

$ /usr/share/squid-deb-proxy-client/apt-avahi-discover
error: uncaptured python exception, closing channel  
('2003:d3:b725:fb45:290:27ff:fe25:f52', 3142, 0, 0): 9223372036854775807 
(:[Errno 111] Connection refused 
[/usr/lib/python3.8/asyncore.py|read|83] 
[/usr/lib/python3.8/asyncore.py|handle_read_event|417] 
[/usr/lib/python3.8/asyncore.py|handle_connect_event|425])
error: uncaptured python exception, closing channel  
('2003:d3:b725:fb45:290:27ff:fe25:f52', 3142, 0, 0): 9223372036854775807 
(:[Errno 111] Connection refused 
[/usr/lib/python3.8/asyncore.py|read|83] 
[/usr/lib/python3.8/asyncore.py|handle_read_event|417] 
[/usr/lib/python3.8/asyncore.py|handle_connect_event|425])
error: uncaptured python exception, closing channel  
('2003:d3:b725:fb45:2e0:c5ff:fe34:f66c', 3142, 0, 0): 9223372036854775807 
(:[Errno 111] Connection refused 
[/usr/lib/python3.8/asyncore.py|read|83] 
[/usr/lib/python3.8/asyncore.py|handle_read_event|417] 
[/usr/lib/python3.8/asyncore.py|handle_connect_event|425])
error: uncaptured python exception, closing channel  
('2003:d3:b725:fb45:2e0:c5ff:fe34:f66c', 3142, 0, 0): 9223372036854775807 
(:[Errno 111] Connection refused 
[/usr/lib/python3.8/asyncore.py|read|83] 
[/usr/lib/python3.8/asyncore.py|handle_read_event|417] 
[/usr/lib/python3.8/asyncore.py|handle_connect_event|425])
error: uncaptured python exception, closing channel  
('192.168.34.22', 3142): 9223372036854775807 (:[Errno 111] Connection refused 
[/usr/lib/python3.8/asyncore.py|read|83] 
[/usr/lib/python3.8/asyncore.py|handle_read_event|417] 
[/usr/lib/python3.8/asyncore.py|handle_connect_event|425])
error: uncaptured python exception, closing channel  
('192.168.34.22', 3142): 9223372036854775807 (:[Errno 111] Connection refused 
[/usr/lib/python3.8/asyncore.py|read|83] 
[/usr/lib/python3.8/asyncore.py|handle_read_event|417] 
[/usr/lib/python3.8/asyncore.py|handle_connect_event|425])
http://192.168.34.5:3142/


** Changed in: squid-deb-proxy (Ubuntu)
   Status: Fix Released => Confirmed

** Tags added: bionic

** Tags added: focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505670

Title:
  "uncaptured python exception"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1505670/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874686] [NEW] package libreoffice-common 1:6.4.2-0ubuntu3 failed to install/upgrade: tentative de remplacement de « /usr/lib/libreoffice/share/basic/Access2Base/Application.xba », qui appartient

2020-04-24 Thread Aldrik KLEBER

Public bug reported:

I was using thunderbird with lightning extension when this crash occur
so I don't know what happened

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libreoffice-common 1:6.4.2-0ubuntu3
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 Apr 23 19:56:51 2020
ErrorMessage: tentative de remplacement de « 
/usr/lib/libreoffice/share/basic/Access2Base/Application.xba », qui appartient 
aussi au paquet libreoffice-base 1:6.3.5-0ubuntu0.19.10.1
InstallationDate: Installed on 2020-04-23 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
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.2
SourcePackage: libreoffice
Title: package libreoffice-common 1:6.4.2-0ubuntu3 failed to install/upgrade: 
tentative de remplacement de « 
/usr/lib/libreoffice/share/basic/Access2Base/Application.xba », qui appartient 
aussi au paquet libreoffice-base 1:6.3.5-0ubuntu0.19.10.1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874686

Title:
  package libreoffice-common 1:6.4.2-0ubuntu3 failed to install/upgrade:
  tentative de remplacement de «
  /usr/lib/libreoffice/share/basic/Access2Base/Application.xba », qui
  appartient aussi au paquet libreoffice-base 1:6.3.5-0ubuntu0.19.10.1

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874684] ProcCpuinfoMinimal.txt

2020-04-24 Thread Maximilian Federle via ubuntu-bugs

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1874684/+attachment/5359215/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874684

Title:
  "Show on" setting does nothing in dual-monitor setup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1874684/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874685] [NEW] Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found due to firmware crash

Public bug reported:

[9.924130] iwlwifi :00:14.3: enabling device ( -> 0002)
[   10.031456] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 
58.3.35.22
[   10.031480] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM
[   10.031489] iwlwifi :00:14.3: Found debug configuration: 0
[   10.033948] iwlwifi :00:14.3: loaded firmware version 50.3e391d3e.0 
op_mode iwlmvm
[   10.218293] iwlwifi :00:14.3: Detected Killer(R) Wi-Fi 6 AX1650i 160MHz 
Wireless Network Adapter (201NGW), REV=0x354
[   10.232843] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[   10.235398] iwlwifi :00:14.3: Allocated 0x0040 bytes for firmware 
monitor.
[   11.241180] iwlwifi :00:14.3: Collecting data: trigger 15 fired.
[   11.489274] iwlwifi :00:14.3: Start IWL Error Log Dump:
[   11.489293] iwlwifi :00:14.3: Status: 0x, count: -673266569
[   11.489303] iwlwifi :00:14.3: Loaded firmware version: 50.3e391d3e.0
[   11.489315] iwlwifi :00:14.3: 0x90F1F96A | ADVANCED_SYSASSERT  
[   11.489323] iwlwifi :00:14.3: 0x7A7986FC | trm_hw_status0
[   11.489331] iwlwifi :00:14.3: 0x09E990EC | trm_hw_status1
[   11.489338] iwlwifi :00:14.3: 0x3073F272 | branchlink2
[   11.489345] iwlwifi :00:14.3: 0xD569005D | interruptlink1
[   11.489352] iwlwifi :00:14.3: 0xFEA17D01 | interruptlink2
[   11.489359] iwlwifi :00:14.3: 0x4BBD0C7B | data1
[   11.489367] iwlwifi :00:14.3: 0xB33DAF15 | data2
[   11.489375] iwlwifi :00:14.3: 0xC8E4188F | data3
[   11.489382] iwlwifi :00:14.3: 0xDEC3F4B3 | beacon time
[   11.489389] iwlwifi :00:14.3: 0xD5B7AAC7 | tsf low
[   11.489395] iwlwifi :00:14.3: 0x00073EAF | tsf hi
[   11.489402] iwlwifi :00:14.3: 0xB943A8DA | time gp1
[   11.489409] iwlwifi :00:14.3: 0x6CCF8627 | time gp2
[   11.489417] iwlwifi :00:14.3: 0x7944BDC6 | uCode revision type
[   11.489424] iwlwifi :00:14.3: 0x3C9DCF39 | uCode version major
[   11.489431] iwlwifi :00:14.3: 0xAF537547 | uCode version minor
[   11.489439] iwlwifi :00:14.3: 0xBC11442E | hw version
[   11.489447] iwlwifi :00:14.3: 0x160C9445 | board version
[   11.489453] iwlwifi :00:14.3: 0x276F21F6 | hcmd
[   11.489460] iwlwifi :00:14.3: 0x022688AB | isr0
[   11.489466] iwlwifi :00:14.3: 0xEBF64685 | isr1
[   11.489473] iwlwifi :00:14.3: 0x9D16A85F | isr2
[   11.489480] iwlwifi :00:14.3: 0x606C870F | isr3
[   11.489488] iwlwifi :00:14.3: 0x1B3967BF | isr4
[   11.489495] iwlwifi :00:14.3: 0xFFBCEAB8 | last cmd Id
[   11.489503] iwlwifi :00:14.3: 0xAEB80995 | wait_event
[   11.489512] iwlwifi :00:14.3: 0x95AD6DCD | l2p_control
[   11.489518] iwlwifi :00:14.3: 0x06D3D9B3 | l2p_duration
[   11.489526] iwlwifi :00:14.3: 0x51B4EEA2 | l2p_mhvalid
[   11.489533] iwlwifi :00:14.3: 0x51B8C323 | l2p_addr_match
[   11.489540] iwlwifi :00:14.3: 0x81E0114B | lmpm_pmg_sel
[   11.489548] iwlwifi :00:14.3: 0xF4D75F29 | timestamp
[   11.489555] iwlwifi :00:14.3: 0x1AFE14FD | flow_handler
[   11.489635] iwlwifi :00:14.3: Start IWL Error Log Dump:
[   11.489643] iwlwifi :00:14.3: Status: 0x, count: 7
[   11.489652] iwlwifi :00:14.3: 0x201013F1 | ADVANCED_SYSASSERT
[   11.489659] iwlwifi :00:14.3: 0x | umac branchlink1
[   11.489666] iwlwifi :00:14.3: 0x80465E6A | umac branchlink2
[   11.489674] iwlwifi :00:14.3: 0x | umac interruptlink1
[   11.489681] iwlwifi :00:14.3: 0x | umac interruptlink2
[   11.489688] iwlwifi :00:14.3: 0x0003 | umac data1
[   11.489695] iwlwifi :00:14.3: 0x2302 | umac data2
[   11.489702] iwlwifi :00:14.3: 0x01300504 | umac data3
[   11.489710] iwlwifi :00:14.3: 0x0032 | umac major
[   11.489717] iwlwifi :00:14.3: 0x3E391D3E | umac minor
[   11.489732] iwlwifi :00:14.3: 0x5D89 | frame pointer
[   11.489743] iwlwifi :00:14.3: 0xC0887F58 | stack pointer
[   11.489755] iwlwifi :00:14.3: 0x | last host cmd
[   11.489763] iwlwifi :00:14.3: 0x | isr status reg
[   11.489822] iwlwifi :00:14.3: Fseq Registers:
[   11.489846] iwlwifi :00:14.3: 0x0003 | FSEQ_ERROR_CODE
[   11.489870] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION
[   11.489898] iwlwifi :00:14.3: 0x | FSEQ_CNVIO_INIT_VERSION
[   11.489926] iwlwifi :00:14.3: 0xA482 | FSEQ_OTP_VERSION
[   11.489956] iwlwifi :00:14.3: 0x0003 | FSEQ_TOP_CONTENT_VERSION
[   11.489984] iwlwifi :00:14.3: 0x35ABFD09 | FSEQ_ALIVE_TOKEN
[   11.490008] iwlwifi :00:14.3: 0xB544286A | FSEQ_CNVI_ID
[   11.490039] iwlwifi :00:14.3: 0xC47C8677 | FSEQ_CNVR_ID
[   11.490065] iwlwifi :00:14.3: 0x2302 | CNVI_AUX_MISC_CHIP
[   11.490097] iwlwifi :00:14.3: 0x01300504 | CNVR_AUX_MISC_CHIP
[   11.490130] iwlwifi :00:14.3: 0x05B0905B | 
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[   11.490161] iwlwifi :00:14.3: 0x025B | 
CNVR_SCU_SD_R

[Bug 1874684] [NEW] "Show on" setting does nothing in dual-monitor setup

2020-04-24 Thread Maximilian Federle via ubuntu-bugs

Public bug reported:

I have two identical monitors that appear with the same name in
settings: Dell Inc. 25"

In the appearance settings I have three options for "Show on":

- All displays
- Dell Inc. 25"
- Dell Inc. 25"

If I want to restrict the dock to one monitor only by switch from "All
displays" to either one of the two "Dell Inc. 25"", nothing changes; the
dock is still shown on both monitors.

Gnome-shell itself has no problems differentiating both monitors and
displays its top-panel only on the primary one.

Ubuntu 20.04 fully updated
Nvidia + XOrg
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2016-11-08 (1262 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5
PackageArchitecture: all
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Tags:  focal
Uname: Linux 5.4.0-26-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-06 (18 days ago)
UserGroups: adm cdrom dialout dip disk lp lpadmin lxd plugdev sambashare sudo 
vboxusers
_MarkForUpload: True

** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-collected focal

** Tags added: apport-collected focal

** Description changed:

  I have two identical monitors that appear with the same name in
  settings: Dell Inc. 25"
  
  In the appearance settings I have three options for "Show on":
  
  - All displays
  - Dell Inc. 25"
  - Dell Inc. 25"
  
  If I want to restrict the dock to one monitor only by switch from "All
  displays" to either one of the two "Dell Inc. 25"", nothing changes; the
  dock is still shown on both monitors.
  
  Gnome-shell itself has no problems differentiating both monitors and
  displays its top-panel only on the primary one.
  
  Ubuntu 20.04 fully updated
  Nvidia + XOrg
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2016-11-08 (1262 days ago)
+ InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
+ Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5
+ PackageArchitecture: all
+ ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
+ Tags:  focal
+ Uname: Linux 5.4.0-26-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-04-06 (18 days ago)
+ UserGroups: adm cdrom dialout dip disk lp lpadmin lxd plugdev sambashare sudo 
vboxusers
+ _MarkForUpload: True

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874684

Title:
  "Show on" setting does nothing in dual-monitor setup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1874684/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874685] Re: Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found due to firmware crash

Upstream fix: https://patchwork.kernel.org/patch/11507349/

** Tags added: oem-priority originate-from-1872037 somerville

** Tags removed: oem-priority originate-from-1872037 somerville
** Tags added: hwe-networking-wifi

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874685

Title:
  Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW),
  REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not
  found due to firmware crash

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874684] Dependencies.txt

2020-04-24 Thread Maximilian Federle via ubuntu-bugs

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1874684/+attachment/5359214/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874684

Title:
  "Show on" setting does nothing in dual-monitor setup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1874684/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874684] ProcEnviron.txt

2020-04-24 Thread Maximilian Federle via ubuntu-bugs

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1874684/+attachment/5359216/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874684

Title:
  "Show on" setting does nothing in dual-monitor setup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1874684/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-04-24 Thread hugh chao

verified pulseaudio version - 1:11.1-1ubuntu7.6 in a hp dm[0] which has
dual front jacks, works well, didn't find any Regression potential.

[0]https://www8.hp.com/h20195/v2/GetPDF.aspx/4AA7-5436EEAP.pdf

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873922] Re: 20.04 not compatible with virtualbox-guest-x11: Fails changing display

2020-04-24 Thread Hadmut Danisch

BTW, copy-paste between host and client (checked that enabled in config)
doesn't work either.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873922

Title:
  20.04 not compatible with virtualbox-guest-x11: Fails changing display

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874647] Comment bridged from LTC Bugzilla

--- Comment From cborn...@de.ibm.com 2020-04-24 06:08 EDT---
(In reply to comment #9)
> (In reply to comment #8)
> > The case with the module parameter in SEV needs a fix similar to
> > https://libvirt.org/git/?p=libvirt.git;a=commit;
> > h=b183a75319b90d0af5512be513743e1eab950612
> > as it can be re-loaded at any time.
> >
> > Essentially the checks in virQEMUCapsLoadCache check qemu/kernel version and
> > many other things.
> > They also check microcode version ...
> >
> > I think the decision there can be two ways, either "on any reboot we need to
> > refresh caps" which makes the code small but probably also wastes quite some
> > refreshes that were not needed.
> > Or it could along all the versions that it checks also keep a full string of
> > /proc/cmdline and compare it. If changed it needs to be refreshed.
> >
> > I agree to Frank that this should be reported upstream.
> > No matter if you or I write a fix, it needs to go upstream then - so a bug
> > tracker there can't hurt.
> > OTOH you can as well start right away with a RFC patch there if you have
> > something prepared already - there is no "strict need" for an upstream bug,
> > only if you hope someone there will fix it for you.
> >
> > Since workarounds are available the prio is medium IMHO, eager to see what
> > upstream thinks.
> >
> > P.S. Even if you have no patch, it would be great if you (as the affected)
> > would kick off the discussion upstream. Please provide a link here to the
> > mailing list entry.
>
> I agree with you. Please regard this as a tracking bug to pick up the
> upstream commits.
>
> We (IBM) will prepare a write up for Secure Execution comparable to what
> exists for AMD SEV and also provide a fix for the cap caching invalidity
> problem. If that is going to look similar for what was done for nesting
> needs to be seen but it is a good starting point. Thanks for providing it.

I think the proper solution is to rebuild the capabilities whenever the date of 
/dev/kvm changed. There are module parameters (hpage and nested) that will 
change the capabilities. Caching beyond the lifetime of /dev/kvm is just wrong.
When the startup takes slightly longer after reboot - so be it.

Agreed to discuss this upstream. Please cc me

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874647

Title:
  [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2020-04-24 Thread Dan Streetman

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Eoan)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Focal)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu Eoan)
   Importance: Undecided => Medium

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

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

** Changed in: systemd (Ubuntu Eoan)
   Status: Confirmed => In Progress

** Changed in: systemd (Ubuntu Bionic)
   Status: Confirmed => In Progress

** 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]
  
- One possible direction is this upstream PR
+ 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
  
- If accepted, that (and previous commits adding UseGateway= parameter)
- would need to be applied to Debian and all Ubuntu releases; Focal, Eoan,
- Bionic, and Xenial.
+ Parts of all those PRs are required in Focal, Eoan, and Bionic.
+ 
+ I am not fixing this for Xenial, at this time.
  
  [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)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867375

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1838154] Re: Something hinders XFCE performance. >:]

\]\}

address url bar example


Only other trick I use is commented templates
described in here:
https://bugzilla.redhat.com/show_bug.cgi?id=1729666


>:]  https://bugzilla.redhat.com/show_bug.cgi?id=1674486#c83

** Attachment added: "address url bar example   \]\}"
   
https://bugs.launchpad.net/ubuntu/+source/xfce4/+bug/1838154/+attachment/5359240/+files/Screenshot_2020-04-24_10-43-34.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838154

Title:
  Something hinders XFCE performance.  >:]

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

2020-04-24 Thread Michel-Ekimia

** Description changed:

+ News :
+ 
+ - Beta Chromium 80 Snap with vaapi enabled :
+ 
+ https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from-
+ source-enable-
+ vaapi/+build/918074/+files/chromium_81.0.4044.113_amd64.snap
+ 
+ Install it with --devmode
+ 
+ 
+ --Original Bug report -
+ 
  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)
  
  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium
  
  My amdgpu can use libva
  
  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
-   VAProfileMPEG2Simple:   VAEntrypointVLD
-   VAProfileMPEG2Main  :   VAEntrypointVLD
-   VAProfileVC1Simple  :   VAEntrypointVLD
-   VAProfileVC1Main:   VAEntrypointVLD
-   VAProfileVC1Advanced:   VAEntrypointVLD
-   VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
-   VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
-   VAProfileH264Main   :   VAEntrypointVLD
-   VAProfileH264Main   :   VAEntrypointEncSlice
-   VAProfileH264High   :   VAEntrypointVLD
-   VAProfileH264High   :   VAEntrypointEncSlice
-   VAProfileHEVCMain   :   VAEntrypointVLD
-   VAProfileHEVCMain10 :   VAEntrypointVLD
-   VAProfileJPEGBaseline   :   VAEntrypointVLD
-   VAProfileNone   :   VAEntrypointVideoProc`
+   VAProfileMPEG2Simple:   VAEntrypointVLD
+   VAProfileMPEG2Main  :   VAEntrypointVLD
+   VAProfileVC1Simple  :   VAEntrypointVLD
+   VAProfileVC1Main:   VAEntrypointVLD
+   VAProfileVC1Advanced:   VAEntrypointVLD
+   VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
+   VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
+   VAProfileH264Main   :   VAEntrypointVLD
+   VAProfileH264Main   :   VAEntrypointEncSlice
+   VAProfileH264High   :   VAEntrypointVLD
+   VAProfileH264High   :   VAEntrypointEncSlice
+   VAProfileHEVCMain   :   VAEntrypointVLD
+   VAProfileHEVCMain10 :   VAEntrypointVLD
+   VAProfileJPEGBaseline   :   VAEntrypointVLD
+   VAProfileNone   :   VAEntrypointVideoProc`

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816497

Title:
  [snap] vaapi chromium no video hardware decoding

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1838154] Re: Something hinders XFCE performance. >:]

I am trying to save what's possible to save
from this bug report.

\]\}

This is closed brackets and closed curly brackets.

This suggest lose code somewhere.

The only workaround is to type it in interactive
fields like address bar or workspace name.


Speed difference is really noticeable.


>:]   https://bugzilla.redhat.com/show_bug.cgi?id=1674486#c82


** Attachment added: "closed brackets and curly brackets"
   
https://bugs.launchpad.net/ubuntu/+source/xfce4/+bug/1838154/+attachment/5359239/+files/Screenshot_2020-04-24_10-42-31.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838154

Title:
  Something hinders XFCE performance.  >:]

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1838154] Re: Something hinders XFCE performance. >:]

New bug report:

https://bugs.launchpad.net/ubuntu/+source/chromium/+bug/1874687


>:]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838154

Title:
  Something hinders XFCE performance.  >:]

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874687] [NEW] stuck scrolling fix

Public bug reported:


There is relatively easy way
to fix stuck scrolling by
typing

\]\}

in address url bar.

This suggest lose code
somewhere.


>:]


also reported:
https://bugs.launchpad.net/ubuntu/+source/xfce4/+bug/1838154/comments/39
https://bugzilla.redhat.com/show_bug.cgi?id=1674486#c83
this might be needed to:
https://bugzilla.redhat.com/show_bug.cgi?id=1729666

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

** Attachment added: "address url bar example   \]\}"
   
https://bugs.launchpad.net/bugs/1874687/+attachment/5359241/+files/Screenshot_2020-04-24_10-43-34.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874687

Title:
  stuck scrolling fix

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1872569] Re: alsa/sof: external mic can't be deteced on Lenovo and HP laptops

2020-04-24 Thread AceLan Kao

** Changed in: linux-oem-osp1 (Ubuntu Bionic)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872569

Title:
  alsa/sof: external mic can't be deteced on Lenovo and HP laptops

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874685] Status changed to Confirmed

2020-04-24 Thread Ubuntu Kernel Bot

This change was made by a bot.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874685

Title:
  Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW),
  REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not
  found due to firmware crash

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874688] [NEW] cannot add a user with username beginning with a number

2020-04-24 Thread Josep Lladonosa Capell

Public bug reported:

The GUI to add a user in Ubuntu allows a username beginning with a number
(checked appears ok but call to user creation fails).
The reason is that the called Perl script adduser does not accept it. This 
script is configurable in /etc/adduser.conf:

# check user and group names also against this regular expression.
#NAME_REGEX="^[a-z][-a-z0-9_]*\$"

As it is commented out, (same) value is taken from
/usr/share/perl5/Debian/AdduserCommon.pm:

$configref->{"name_regex"} = "^[a-z][-a-z0-9_]*\$";


To solve this, you could:

- validate only names matching the expression.

- modify /etc/adduser.conf with another NAME_REGEX to fit Ubuntu's policies
(in this case, adduser would be affected, too).

Added to this, in a root terminal, adduser/passwd allow any password.
This GUI limits this possibility (for security matters, that is ok, but IMHO 
user creating an account from GUI should behave "like root").

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.12
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 11:59:24 2020
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2020-03-10 (45 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874688

Title:
  cannot add a user with username beginning with a number

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821390] Re: apic-split will fail in kvm_units_tests

For the timeout issue on Oracle B-5.0, VM.Standard2.16
this test will take about 2 minutes to run:

SUMMARY: 51 tests, 1 unexpected failures
FAIL apic-split (51 tests, 1 unexpected failures)

real1m53.292s
user1m22.798s
sys 2m22.239s

SUMMARY: 51 tests, 1 unexpected failures
FAIL apic-split (51 tests, 1 unexpected failures)

real1m47.981s
user1m15.764s
sys 2m18.655s

SUMMARY: 51 tests, 1 unexpected failures, 1 skipped
FAIL apic-split (51 tests, 1 unexpected failures, 1 skipped)

real1m52.938s
user1m12.339s
sys 2m32.482s


** Tags added: sru-20200406

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821390

Title:
  apic-split will fail in kvm_units_tests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1807056] Re: Occasional Keyboard freeze

2020-04-24 Thread Dilip

I installed 20.04. And the bug is back as is from 18.04. I can get out
of this if I wait or type on the search box. Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807056

Title:
  Occasional Keyboard freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1807056/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-04-24 Thread hugh chao

verified pulseaudio version - 1:11.1-1ubuntu7.6 in a dell laptop[0]
which only has one headset jack, works well, didn't find any Regression
potential.

[0] https://www.dell.com/en-us/work/shop/dell-laptops-and-
notebooks/latitude-5501-business-laptop/spd/latitude-15-5501-laptop

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874690] [NEW] Using 2 screens, one horizontally and the other vertically

2020-04-24 Thread ERIK LOPEZ RODRIGUEZ

Public bug reported:

I have 2 screens. One horizontally (left) and the other vertically
(right).

Since I updated to Ubuntu 20.04 I can't set the one on the right to
vertical again.

I have tried to install 20.04 in different ways, but the problem
persists.

With the previous version there was no problem.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/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  435.21  Sun Aug 25 08:17:57 
CDT 2019
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 11:25:16 2020
DistUpgraded: 2020-04-23 20:11:30,100 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso 
hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8))
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 435.21, 5.3.0-46-generic, x86_64: installed
 nvidia, 435.21, 5.4.0-26-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company TU117 [GeForce GTX 1650] [103c:8558]
InstallationDate: Installed on 2020-04-23 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Pavilion Gaming Desktop TG01-0xxx
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=31f8c9e1-cef6-4c45-aa8d-7d875b76abd9 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago)
dmi.bios.date: 11/26/2019
dmi.bios.vendor: AMI
dmi.bios.version: F.11
dmi.board.name: 8653
dmi.board.vendor: HP
dmi.board.version: A (SMVB)
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnAMI:bvrF.11:bd11/26/2019:svnHP:pnHPPavilionGamingDesktopTG01-0xxx:pvr:rvnHP:rn8653:rvrA(SMVB):cvnHP:ct3:cvr:
dmi.product.family: 103C_53311M HP Pavilion Desktop PC
dmi.product.name: HP Pavilion Gaming Desktop TG01-0xxx
dmi.product.sku: 8BW13EA#ABE
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874690

Title:
  Using 2 screens, one horizontally and the other vertically

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874662] Re: Corrupted installation medium

2020-04-24 Thread Jean-Baptiste Lallement

** Description changed:

  If you have been redirected to this page, it means that your
  installation of Ubuntu or a flavour failed.
  
- If you look in the log file /var/log/syslog, you'll see messages like
- the above:
+ If you search in the log file /var/log/syslog, you'll see messages like
+ above:
  
  Apr 24 00:01:40 ubuntu kernel: [  329.409695] SQUASHFS error: zlib 
decompression failed, data probably corrupt
  Apr 24 00:01:40 ubuntu kernel: [  329.409704] SQUASHFS error: 
squashfs_read_data failed to read block 0x37545
  
  This failure is usually caused by bad ISO download, corrupted install
  media, or device failure.
  
  We suggest you verify your ISO download, and note the validation of your
  ISO before install to ensure a good download & write.
  
- You may also find this tutorial useful: https://ubuntu.com/tutorials
- /tutorial-how-to-verify-ubuntu
- 
  If you experienced an issue during installation and think it is not
  caused by a corrupted installation media, do not hesitate to report a
  bug by running the following command from a terminal:
  
  $ ubuntu-bug ubiquity
  
  Thanks for using Ubuntu.

** Description changed:

  If you have been redirected to this page, it means that your
  installation of Ubuntu or a flavour failed.
  
  If you search in the log file /var/log/syslog, you'll see messages like
  above:
  
  Apr 24 00:01:40 ubuntu kernel: [  329.409695] SQUASHFS error: zlib 
decompression failed, data probably corrupt
  Apr 24 00:01:40 ubuntu kernel: [  329.409704] SQUASHFS error: 
squashfs_read_data failed to read block 0x37545
  
  This failure is usually caused by bad ISO download, corrupted install
  media, or device failure.
  
- We suggest you verify your ISO download, and note the validation of your
- ISO before install to ensure a good download & write.
+ We suggest you verify your ISO download, your installation medium or use
+ another USB stick.
  
  If you experienced an issue during installation and think it is not
  caused by a corrupted installation media, do not hesitate to report a
  bug by running the following command from a terminal:
  
  $ ubuntu-bug ubiquity
  
  Thanks for using Ubuntu.

** Description changed:

  If you have been redirected to this page, it means that your
  installation of Ubuntu or a flavour failed.
  
  If you search in the log file /var/log/syslog, you'll see messages like
  above:
  
  Apr 24 00:01:40 ubuntu kernel: [  329.409695] SQUASHFS error: zlib 
decompression failed, data probably corrupt
  Apr 24 00:01:40 ubuntu kernel: [  329.409704] SQUASHFS error: 
squashfs_read_data failed to read block 0x37545
  
  This failure is usually caused by bad ISO download, corrupted install
  media, or device failure.
  
  We suggest you verify your ISO download, your installation medium or use
  another USB stick.
  
+ You may also find useful information in this tutorial:
+ https://tutorials.ubuntu.com/tutorial/tutorial-how-to-verify-ubuntu
+ 
  If you experienced an issue during installation and think it is not
  caused by a corrupted installation media, do not hesitate to report a
  bug by running the following command from a terminal:
  
  $ ubuntu-bug ubiquity
  
  Thanks for using Ubuntu.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874662

Title:
  Corrupted installation medium

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874693] [NEW] vmx_host_state_area test from ubuntu_kvm_unit_tests crashed with Eoan Azure

Public bug reported:

Only Standard_F32s_v2 and Standard_D48_v3 can be tested with KVM unit
test.

And it looks like the kvm_unit_test will crash with vmx_host_state_area:

01:49:05 DEBUG| Running 
'/home/azure/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_host_state_area'
 BUILD_HEAD=4671e4ba
 timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.p1fskNt1wF -smp 1 
-cpu host,+vmx -append vmx_host_state_area_test # -initrd /tmp/tmp.YTVFJ025gz
 enabling apic
 paging enabled
 cr0 = 80010011
 cr3 = 477000
 cr4 = 20

 Test suite: vmx_host_state_area_test
 PASS: HOST_CR0 8021: vmlaunch succeeds
 PASS: HOST_CR0 80010030: vmlaunch fails
 PASS: HOST_CR0 80010030: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 80010011: vmlaunch fails
 PASS: HOST_CR0 80010011: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 10031: vmlaunch fails
 PASS: HOST_CR0 10031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 180010031: vmlaunch fails
 PASS: HOST_CR0 180010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 280010031: vmlaunch fails
 PASS: HOST_CR0 280010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 480010031: vmlaunch fails
 PASS: HOST_CR0 480010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 880010031: vmlaunch fails
 PASS: HOST_CR0 880010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 1080010031: vmlaunch fails
 PASS: HOST_CR0 1080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 2080010031: vmlaunch fails
 PASS: HOST_CR0 2080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 4080010031: vmlaunch fails
 PASS: HOST_CR0 4080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 8080010031: vmlaunch fails
 PASS: HOST_CR0 8080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 10080010031: vmlaunch fails
 PASS: HOST_CR0 10080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 20080010031: vmlaunch fails
 PASS: HOST_CR0 20080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 40080010031: vmlaunch fails
 PASS: HOST_CR0 40080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 80080010031: vmlaunch fails
 PASS: HOST_CR0 80080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 100080010031: vmlaunch fails
 PASS: HOST_CR0 100080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 200080010031: vmlaunch fails
 PASS: HOST_CR0 200080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 400080010031: vmlaunch fails
 PASS: HOST_CR0 400080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 800080010031: vmlaunch fails
 PASS: HOST_CR0 800080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 180010031: vmlaunch fails
 PASS: HOST_CR0 180010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 280010031: vmlaunch fails
 PASS: HOST_CR0 280010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 480010031: vmlaunch fails
 PASS: HOST_CR0 480010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 880010031: vmlaunch fails
 PASS: HOST_CR0 880010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 1080010031: vmlaunch fails
 PASS: HOST_CR0 1080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 2080010031: vmlaunch fails
 PASS: HOST_CR0 2080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 4080010031: vmlaunch fails
 PASS: HOST_CR0 4080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 8080010031: vmlaunch fails
 PASS: HOST_CR0 8080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 10080010031: vmlaunch fails
 PASS: HOST_CR0 10080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 20080010031: vmlaunch fails
 PASS: HOST_CR0 20080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 40080010031: vmlaunch fails
 PASS: HOST_CR0 40080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 80080010031: vmlaunch fails
 PASS: HOST_CR0 80080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 100080010031: vmlaunch fails
 PASS: HOST_CR0 100080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 200080010031: vmlaunch fails
 PASS: HOST_CR0 200080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 400080010031: vmlaunch fails
 PASS: HOST_CR0 400080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR0 800080010031: vmlaunch fails
 PASS: HOST_CR0 800080010031: VMX inst error is 8 (actual 8)
 PASS: HOST_CR4 2000: vmlaunch succeeds
 PASS: HOST_CR4 3020: vmlaunch fails
 PASS: HOST_CR4 3020: VMX inst error is 8 (actual 8)
 PASS: HOST_CR4 20: vmlaunch fails
 PASS: HOST_CR4 20: VMX inst error is 8 (actual 8)
 PASS: HOST_CR4 6020: vmlaunch fails
 PASS: HOST_CR4 6020: VMX inst error is 8 (actual 8)
 PASS: HOST_CR4 a020: vmlaunch fails
 PASS: HOST_CR4 a020: VMX inst error is 8 (actual 8)
 PASS: HOST_CR4 82020: vmlaunch fails
 PASS: HOST_CR4 82020: VMX inst error is 8 (actual 8)
 PASS: HOS

[Bug 1874693] Re: vmx_host_state_area test from ubuntu_kvm_unit_tests crashed with Eoan Azure

We would need access to the console for debugging this.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874693

Title:
  vmx_host_state_area test from ubuntu_kvm_unit_tests crashed with Eoan
  Azure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1874693/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874692] [NEW] cannot update to 20.04

2020-04-24 Thread Mehrdad

Public bug reported:

Could not calculate the upgrade

An unresolvable problem occurred while calculating the upgrade.

 This was caused by:
 * Upgrading to a pre-release version of Ubuntu
This is most likely a transient problem, 
please try again later.
If none of this applies, then please report this bug using the command 
'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to 
investigate this yourself the log files in '/var/log/dist-upgrade' will contain 
details about the upgrade. Specifically, look at 'main.log' and 'apt.log'.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.37
ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 15:10:11 2020
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2020-04-24 (0 days ago)
VarLogDistupgradeTermlog:

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874692

Title:
  cannot update to 20.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1856410] Re: ubiquity prompts for a MOK password that it then does not use

2020-04-24 Thread Dimitri John Ledkov

1) ubiquity already does list-oem which can query from ubuntu-drivers-
common if any oem stuff needs to happen

2) ubuntu-drivers-common should provide '--package-list' option on the
regular list command too

3) this way ubiquity can run 'list' with '--package-list' ahead of the
prepare stage to peak, if any dkms modules would get installed.

4) then ubiquity would be able to show the right ui when people tick
third-party drivers, i.e. determine if mok is needed or not.

5) under secureboot however, I don't think ubiquity should be trying to
install any dkms drivers as they will all fail to load. Thus it can even
skip calling `install` on them altogether.

** Also affects: ubuntu-drivers-common (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856410

Title:
  ubiquity prompts for a MOK password that it then does not use

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874700] [NEW] file selection represents impossibly small file previews

Public bug reported:


File selection shows impossibly small
file previews.

Can they be increased as in current
case Nautilus is unusable to select
files.


>:]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874700

Title:
  file selection represents impossibly small file previews

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874698] [NEW] [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem

2020-04-24 Thread Wittawat Jitkrittum

Public bug reported:

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

** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874698

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874702] [NEW] python crash during "do-release-upgrade -d"

2020-04-24 Thread Ievgen Pyrogov

Public bug reported:

The original bug report was submitted to https://discourse.ubuntu.com/t
/error-upgrading-to-development-version-of-20-04/15522. Moving it here.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.18
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
CrashDB: ubuntu
Date: Fri Apr 24 13:51:58 2020
InstallationDate: Installed on 2020-04-11 (12 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874702

Title:
  python crash during "do-release-upgrade -d"

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874696] [NEW] shift-alt-TAB can cause strange sound lag