[Bug 1903724] Re: [SRU] Package fails to build with missing 'systemctl'

2020-11-30 Thread Chris MacNaughton
I think this upload will be superceded by an upstream point release that
is being handled now.

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

Title:
  [SRU] Package fails to build with missing 'systemctl'

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

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

[Bug 1903724] Re: [SRU] Package fails to build with missing 'systemctl'

2020-11-30 Thread Chris MacNaughton
As evidenced by the build log in the acceptance log, the Nova package
builds successfully after this change in Focal.

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

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

Title:
  [SRU] Package fails to build with missing 'systemctl'

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

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

[Bug 1906364] Re: unattended-upgrade still restarts blacklisted daemons

2020-11-30 Thread Orgad Shaneh
We have at least 4 servers on which docker daemon was shutdown due to
this unattended upgrade, and was not restarted.

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

Title:
  unattended-upgrade still restarts blacklisted daemons

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

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

[Bug 1906364] [NEW] unattended-upgrade still restarts blacklisted daemons

2020-11-30 Thread sascha arthur
Public bug reported:

Hello,

Today plenty of our systems running ubuntu 20.04 were restarting the
docker daemon, even if i blacklisted the docker package. Since docker
has an dependency on containerd thats the reason why it was restarted.
IMO the blacklist should also check the full tree of dependencies...
This should NOT happen!

>From the log you find:

2020-12-01 06:40:13,881 INFO Starting unattended upgrades script
2020-12-01 06:40:13,882 INFO Allowed origins are: o=Ubuntu,a=focal, 
o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, 
o=UbuntuESM,a=focal-infra-security
2020-12-01 06:40:13,882 INFO Initial blacklist: docker docker.io
2020-12-01 06:40:13,882 INFO Initial whitelist (not strict):
2020-12-01 06:40:19,139 INFO Packages that will be upgraded: containerd 
qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui 
qemu-system-x86 qemu-utils
2020-12-01 06:40:19,140 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
2020-12-01 06:40:46,996 INFO All upgrades installed
2020-12-01 06:40:50,732 INFO Starting unattended upgrades script
2020-12-01 06:40:50,732 INFO Allowed origins are: o=Ubuntu,a=focal, 
o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, 
o=UbuntuESM,a=focal-infra-security
2020-12-01 06:40:50,733 INFO Initial blacklist: docker docker.io
2020-12-01 06:40:50,733 INFO Initial whitelist (not strict):

Also this happened for us on plenty of our servers almost at the same
(why the unattended updates are not spread over time?), which destroyed
the second time an production environment.

This is not how unattended-upgraded should be, sadly this package lost
our trust and we disable it and schedule the 'unattended updates' now on
our own.

PS: Not to say that on some servers the docker daemon did not even
restart..

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Hello,
  
  Today plenty of our systems running ubuntu 20.04 were restarting the
  docker daemon, even if i blacklisted the docker package. Since docker
  has an dependency on containerd thats the reason why it was restarted.
  IMO the blacklist should also check the full tree of dependencies...
  This should NOT happen!
  
  From the log you find:
  
  2020-12-01 06:40:13,881 INFO Starting unattended upgrades script
  2020-12-01 06:40:13,882 INFO Allowed origins are: o=Ubuntu,a=focal, 
o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, 
o=UbuntuESM,a=focal-infra-security
  2020-12-01 06:40:13,882 INFO Initial blacklist: docker docker.io
  2020-12-01 06:40:13,882 INFO Initial whitelist (not strict):
  2020-12-01 06:40:19,139 INFO Packages that will be upgraded: containerd 
qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui 
qemu-system-x86 qemu-utils
  2020-12-01 06:40:19,140 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  2020-12-01 06:40:46,996 INFO All upgrades installed
  2020-12-01 06:40:50,732 INFO Starting unattended upgrades script
  2020-12-01 06:40:50,732 INFO Allowed origins are: o=Ubuntu,a=focal, 
o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, 
o=UbuntuESM,a=focal-infra-security
  2020-12-01 06:40:50,733 INFO Initial blacklist: docker docker.io
  2020-12-01 06:40:50,733 INFO Initial whitelist (not strict):
  
- 
- Also this happened for us on plenty of our servers almost at the same (why 
the unattended updates are not spread over time?), which destroyed the second 
time an production environment.
+ Also this happened for us on plenty of our servers almost at the same
+ (why the unattended updates are not spread over time?), which destroyed
+ the second time an production environment.
  
  This is not how unattended-upgraded should be, sadly this package lost
  our trust and we disable it and schedule the 'unattended updates' now on
  our own.
+ 
+ PS: Not to say that on some servers the docker daemon did not even
+ restart..

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

Title:
  unattended-upgrade still restarts blacklisted daemons

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

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

[Bug 1906365] [NEW] package elpa-magit 2.90.1-2 failed to install/upgrade: installed elpa-magit package post-installation script subprocess returned error exit status 2

2020-11-30 Thread pradeep
Public bug reported:

While installation the GIT on Ubuntu it failed.
sudo apt install git-all

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: elpa-magit 2.90.1-2
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Dec  1 13:00:42 2020
ErrorMessage: installed elpa-magit package post-installation script subprocess 
returned error exit status 2
InstallationDate: Installed on 2020-11-13 (17 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: magit
Title: package elpa-magit 2.90.1-2 failed to install/upgrade: installed 
elpa-magit package post-installation script subprocess returned error exit 
status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal 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/1906365

Title:
  package elpa-magit 2.90.1-2 failed to install/upgrade: installed elpa-
  magit package post-installation script subprocess returned error exit
  status 2

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

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

[Bug 1865032] Re: [UBUNTU] zipl/libc: Fix potential buffer overflow in printf

2020-11-30 Thread Mathew Hodson
** Changed in: s390-tools (Ubuntu)
   Importance: Undecided => High

** Changed in: s390-tools (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: s390-tools (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: s390-tools (Ubuntu Eoan)
   Importance: Undecided => High

** Changed in: s390-tools (Ubuntu Focal)
   Importance: Undecided => High

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

Title:
  [UBUNTU] zipl/libc: Fix potential buffer overflow in printf

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

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

[Bug 1870514] Re: update containerd:amd64 1.3.3-0 stops docker daemon

2020-11-30 Thread Gert van den Berg
This also took Docker down on 18.04 with the update for USN-4653-1

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

Title:
  update containerd:amd64 1.3.3-0 stops docker daemon

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

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

[Bug 1902044] Re: SRU the current 42.5 stable update

2020-11-30 Thread Sebastien Bacher
Ok, 42.6 uploaded to hirsute and SRUed now

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

Title:
  SRU the current 42.5 stable update

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

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

[Bug 1885087] Re: Can't keep brightness value after reboot/poweroff in some nvidia gfx

2020-11-30 Thread hugh chao
tried nvidia-graphics-drivers-455 in groovy which can fix this issue, I
didn't observe any regression.

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

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

Title:
  Can't keep brightness value after reboot/poweroff in some nvidia gfx

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

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

[Bug 1902044] Re: SRU the current 42.5 stable update

2020-11-30 Thread Sebastien Bacher
It's not under the GNOME MRE no, just a micro release update worth
SRUing for the fixes it includes. The .6 update is newer than the upload
in the queue but we should get the current version so feel free to
reject .5 and I will upload the new one today

** Changed in: deja-dup (Ubuntu Groovy)
   Status: Incomplete => New

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

Title:
  SRU the current 42.5 stable update

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

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

[Bug 1905740] Re: SRU the current 3.36.5 stable update

2020-11-30 Thread Sebastien Bacher
Yes, that's the part of the changelog

'   * debian/patches/revert_vino_deprecated.patch:
 - revert the upstream change to remove the vino control option, it's
   still working in Ubuntu because we reverted the g-s-d commit
   which deprecated the backend handling'

** Changed in: gnome-control-center (Ubuntu Focal)
   Status: Incomplete => New

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

Title:
  SRU the current 3.36.5 stable update

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

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

[Bug 1877835] Re: "Shell to examine situation" during upgrade fails

2020-11-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-release-upgrader (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/1877835

Title:
  "Shell to examine situation" during upgrade fails

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

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

[Bug 1905272] Re: Can't get h/w video acceleration on rpi4

2020-11-30 Thread Juerg Haefliger
This is gated by snapd work. I don't have visibility into the snap
team's schedule.

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

Title:
  Can't get h/w video acceleration on rpi4

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

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

[Bug 1836167] Re: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing nodes

2020-11-30 Thread Po-Hsu Lin
Spotted on B-5.4 P9 node baltar

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

Title:
  cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing
  nodes

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

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

[Bug 1892860] Re: af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on B-arm64

2020-11-30 Thread Po-Hsu Lin
Found on B-5.4 P9 baltar 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/1892860

Title:
  af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on
  B-arm64

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

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

[Bug 1875773] Re: package snapcraft (not installed) failed to install/upgrade: new snapcraft package pre-installation script subprocess returned error exit status 1

2020-11-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: snapcraft (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/1875773

Title:
  package snapcraft (not installed) failed to install/upgrade: new
  snapcraft package pre-installation script subprocess returned error
  exit status 1

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

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

[Bug 1906359] [NEW] config unusable 4k monitor

2020-11-30 Thread whitis
Public bug reported:

imwheel -c is totally unusable on a 50" 4K/UHD monitor.   The buttons
are tiny and illegible.  The preview is tiny.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: imwheel 1.0.0pre12-12
ProcVersionSignature: Ubuntu 5.4.0-53.59~18.04.1-generic 5.4.65
Uname: Linux 5.4.0-53-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec  1 01:37:41 2020
InstallationDate: Installed on 2019-05-02 (578 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: imwheel
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: imwheel (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/1906359

Title:
  config unusable 4k monitor

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

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

Re: [Bug 1905790] Re: Recompile SSSD in 20.04 using OpenSSL (instead of NSS) support

2020-11-30 Thread Robie Basak
On Tue, Dec 01, 2020 at 03:33:45AM -, Marco Trevisan (Treviño) wrote:
> Probably not enough to compare, but from what I see in these matrices
> [4], there's basically nothing that NSS supports and OpenSSL doesn't
> (while it's true the other way around).

OK, but what about build configuration and default enabled cryptosuites
and suchlike? For example we've "locked down" OpenSSL's default
configuration to no longer support some older cryptosuites. Will
swapping NSS for OpenSSL cause user configurations to narrow the set of
cryptosuites that are enabled?

What if, for example, someone has an LDAP server that only supports
older TLS, and switching to OpenSSL causes their sssd LDAP TLS client to
require newer TLS because of our stronger defaults? What I describe
would result in a regression for that user until they reconfigure
things. Is this a realistic possibility?

> Not to mention that we already switched to an OpenSSL-based version of
> SSSD in 21.10, and even if its user base can't be compared to 20.04, so
> far I didn't read about related issues [5].

I think you're thinking of functional regressions here (ie. introducing
actual bugs), whereas I'm more bothered about regressing edge case user
configurations (eg. introducing a change that requires users to change
their local configurations to avoid a behavioural regression).

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

Title:
  Recompile SSSD in 20.04 using OpenSSL (instead of NSS) support

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

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

[Bug 1905593] Re: Support synaptics devices 0xF9, 0xFC, 0xC2

2020-11-30 Thread Shengyao Xue
** Tags added: oem-priority originate-from-1899432 sutton

** Changed in: oem-priority
 Assignee: (unassigned) => Shengyao Xue (xueshengyao)

** Changed in: oem-priority
   Status: New => In Progress

** Changed in: oem-priority
   Importance: Undecided => High

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

Title:
  Support synaptics devices 0xF9, 0xFC, 0xC2

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

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

[Bug 1890435] Re: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault

2020-11-30 Thread Christian Ehrhardt 
r10-6586 - passed 27 good runs, no fails

Updated Result Overview:
20190425 good
r10-1014
r10-2027 good?4
r10-2533
r10-3040 good?4
r10-3220
r10-3400 good?4
r10-3450
r10-3475
r10-3478
r10-3593
r10-3622
r10-3657 good?5
r10-3727 good?3
r10-4054 other kind of bad - signature different, and rare?
r10-6080 good?10
r10-6586 good?27
r10-7093 bad, but slow to trigger (2 of 19)
20200507 bad bad bad

Signatures:
r10-4054 arm_legitimate_address_p (nonimmediate)
r10-7093 add_regs_to_insn_regno_info (lra)
r10-7093 add_regs_to_insn_regno_info (lra)
20200507 extract_plus_operands (lra)
20200507 avoid_constant_pool_reference (lra)
20200507 add_regs_to_insn_regno_info (lra)
ubu-10.2 add_regs_to_insn_regno_info (lra)
ubu-10.2 avoid_constant_pool_reference (lra)
ubu-10.2 thumb2_legitimate_address_p (lra)
ubu-10.2 add_regs_to_insn_regno_info (lra)

Next I'll run r10-7093 in this new setup.
@Doko - It would be great to have ~6760 be built for the likely next step.

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

Title:
  gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation
  fault

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

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

[Bug 1906341] Status changed to Confirmed

2020-11-30 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/1906341

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906356] Status changed to Confirmed

2020-11-30 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/1906356

Title:
  Trackpad not recognised

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

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

[Bug 1906190] Re: Ubuntu 20.10 Live, debian-installer/language=de not working anymore

2020-11-30 Thread beta-tester
** Summary changed:

- Ubuntu 20.10 Live, locale set to aa_DJ, when bootoption tells to setup to 
locale de_DE
+ Ubuntu 20.10 Live, debian-installer/language=de not working anymore

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

Title:
  Ubuntu 20.10 Live, debian-installer/language=de not working anymore

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

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

[Bug 1906356] [NEW] Trackpad not recognised

2020-11-30 Thread Pranav Vijayaraghavan
Public bug reported:

Trackpad/Touchpad is not recognized by Ubuntu 20.04. Cursor can be moved
only by mouse and not track pad.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-54-generic 5.4.0-54.60
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pranav  981 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec  1 11:30:43 2020
InstallationDate: Installed on 2020-11-28 (2 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0408:5300 Quanta Computer, Inc. HP Wide Vision HD Camera
 Bus 001 Device 002: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical 
Mouse
 Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=5fe853f7-97de-4764-83e8-465adc03881b ro quiet splash acpi_osi=
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-54-generic N/A
 linux-backports-modules-5.4.0-54-generic  N/A
 linux-firmware1.187.4
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
dmi.bios.date: 11/22/2019
dmi.bios.vendor: Insyde
dmi.bios.version: F.20
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 85FA
dmi.board.vendor: HP
dmi.board.version: 42.34
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.20:bd11/22/2019:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FA:rvr42.34:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx
dmi.product.sku: 2X017PA#ACJ
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot from 2020-12-01 11-44-43.png"
   
https://bugs.launchpad.net/bugs/1906356/+attachment/5439911/+files/Screenshot%20from%202020-12-01%2011-44-43.png

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

Title:
  Trackpad not recognised

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

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

[Bug 1901627] Re: Update product naming: Simplify UA Infrastructure ESM to UA Infra: ESM

2020-11-30 Thread Chad Smith
** Description changed:

+ [Impact]
+ 
+  The product names and product URLs of Ubuntu Advantage Extended
+ Security Maintenance offerings have been rebranded prior to an official
+ launch of the product ESM product in Ubuntu Xenial, Bionic and Focal.
+ MOTD messages reference the old product name UA Infrastructure: Extended
+ Security Maintenance as well as an invalid product URL
+ https://ubuntu.com/esm.
+ 
+ Correct both the product name "UA Infra: ESM" and the apt URL message
+ See https://ubuntu.com/security/esm.
+ 
+ Because these text messages are translated using gettext, translations
+ will need to be updated as well.
+ 
+ [Test Case]
+ 
+  * Install unreleased ubuntu-advantage-tools from a PPA
+  * Run: ua enable  to activate UA apt repositories
+  * Check MOTD messaging related to UA Infra: ESM prior to upgrade to 
-proposed update-notifier via /usr/lib/update-notifier/apt-check 
--human-readable
+ 
+  * Upgrade update-notifier to -proposed 
+  * Re-check MOTD messaging related to UA Infra: ESM to see expected messages
+ 
+ 
+ #!/bin/bash
+ #
+ # SRU Verification update-notifier + ubuntu=advantage-tools
+ # Test procedure:
+ # - launch container Trusty, Xenial or Bionic
+ # - Install ubuntu-advantage-tools from 
https://launchpad.net/~ua-client/+archive/ubuntu/proposed which supports esm on 
trusty, xenial, bionic, and focal
+ # - Attach container to UA subscription (which activates the ESM APT repos
+ # - run apt_check --human-readable to assert ESM pkg counts ARE NOT reported
+ # - Upgrade update-notifier to -proposed
+ # - re-run apt_check --human-readable to assert ESM pkg counts ARE reported
+ 
+ set -e
+ UA_TOKEN=$1
+ if [ -z "$1" ]; then
+  echo "Usage: $0 "
+  exit 1
+ fi
+ # sources:
+ # ua.proposed:
+ # source: deb 
http://ppa.launchpad.net/canonical-server/ua-client-daily/ubuntu \$RELEASE main
+ # keyid: 94E187AD53A59D1847E4880F8A295C4FB8B190B7
+ 
+ cat > test-un.yaml  setup_proposed.sh  Focal. If messaging falls over the result is a 
lack of MOTD information about ESM package updates in motd, which is not yet 
released. If we can ensure we receive MOTD messaging about both ESM and non-ESM 
package updates without error, then risk of regression is minimal.
+ 
+ 
+ [Other Info]
+ 
+ 
+ [Original Description]
+ 
  MOTD text should align with the messaging that is being surfaced by
  ubuntu-advantage-tools and apt command line hook messaging.
  
  Current ESM product name is represented in MOTD as the following when
  logging into a VM:
  
  ### Current ESM-relatedMOTD messaging
  
  # When ESM is disabled:
  UA Infrastructure Extended Security Maintenance \(ESM\) is not enabled.
  
  Enable UA Infrastructure ESM to receive 14 additional security updates.
  
  # When ESM is enabled:
  UA Infrastructure Extended Security 

[Bug 1905740] Re: SRU the current 3.36.5 stable update

2020-11-30 Thread Robie Basak
Most of this looks fine but I'm concerned about this upstream changelog
item:

 sharing: Replace vino with gnome-remote-desktop for X11 sessions

It looks like that was done because of a problem with Wayland only.
Changing behaviour for X11 that isn't for the purpose of fixing a bug is
something we would normally avoid in a stable release. Will this change
functionality from a user perspective? Is it appropriate to be making
this change in an LTS?

** Also affects: gnome-control-center (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: gnome-control-center (Ubuntu Focal)
   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/1905740

Title:
  SRU the current 3.36.5 stable update

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

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

[Bug 1905740] Re: SRU the current 3.36.5 stable update

2020-11-30 Thread Robie Basak
Oh sorry, it looks like you reverted this in your upload.

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

Title:
  SRU the current 3.36.5 stable update

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

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

[Bug 1906341] Re: Touchpad button doesn't work on Dell Precision 7550/7750

2020-11-30 Thread Daniel van Vugt
** Changed in: libevdev (Ubuntu)
 Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh)

** Changed in: libinput (Ubuntu)
 Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh)

** Changed in: libevdev (Ubuntu)
   Status: New => In Progress

** Changed in: libinput (Ubuntu)
   Status: New => In Progress

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

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] xdpyinfo.txt

2020-11-30 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1906341/+attachment/5439910/+files/xdpyinfo.txt

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] Xrandr.txt

2020-11-30 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1906341/+attachment/5439909/+files/Xrandr.txt

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] XorgLogOld.txt

2020-11-30 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1906341/+attachment/5439908/+files/XorgLogOld.txt

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] XorgLog.txt

2020-11-30 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1906341/+attachment/5439907/+files/XorgLog.txt

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] WifiSyslog.txt

2020-11-30 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1906341/+attachment/5439906/+files/WifiSyslog.txt

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] UdevDb.txt

2020-11-30 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1906341/+attachment/5439905/+files/UdevDb.txt

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] RfKill.txt

2020-11-30 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1906341/+attachment/5439904/+files/RfKill.txt

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] PulseList.txt

2020-11-30 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1906341/+attachment/5439903/+files/PulseList.txt

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] ProcModules.txt

2020-11-30 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1906341/+attachment/5439902/+files/ProcModules.txt

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] ProcInterrupts.txt

2020-11-30 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1906341/+attachment/5439901/+files/ProcInterrupts.txt

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] ProcEnviron.txt

2020-11-30 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1906341/+attachment/5439900/+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/1906341

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] ProcCpuinfoMinimal.txt

2020-11-30 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1906341/+attachment/5439899/+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/1906341

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] ProcCpuinfo.txt

2020-11-30 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1906341/+attachment/5439898/+files/ProcCpuinfo.txt

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] Lsusb.txt

2020-11-30 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1906341/+attachment/5439897/+files/Lsusb.txt

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] Lspci.txt

2020-11-30 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1906341/+attachment/5439896/+files/Lspci.txt

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] IwConfig.txt

2020-11-30 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1906341/+attachment/5439895/+files/IwConfig.txt

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] DpkgLog.txt

2020-11-30 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1906341/+attachment/5439894/+files/DpkgLog.txt

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] CurrentDmesg.txt

2020-11-30 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1906341/+attachment/5439893/+files/CurrentDmesg.txt

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] CRDA.txt

2020-11-30 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1906341/+attachment/5439892/+files/CRDA.txt

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] Re: Touchpad button doesn't work on Dell Precision 7550/7750

2020-11-30 Thread Kai-Chuan Hsieh
apport information

** Tags added: apport-collected bionic ubuntu

** Description changed:

  [Impact]
  
   * The touchpad's right button become no function after update to 5.4
  kernel
  
   * The INPUT_PROP_BUTTONPAD property is set by 5.4 kernel, so that
  libinput regard it as clickpad.
  
   * Add a model quirk to unset the bit can make touchpad's right button
  works normally.
  
  [Test Case]
  
   * 1. Boot into Ubuntu
     2. Identify touchpad input device number,
    can be obtained in $HOME/.local/share/xorg/Xorg.0.log
     3. $ udevadm info /sys/class/input/inputX
    check PROP environment variable,
    it is 5 if INPUT_PROP_BUTTONPAD property is set
     4. And the touchpad right button become no function
     5. After update the libevdev with disable_property
    API and libinput10 with model quirk
     6. reboot
     7. The input device PROP is still 5,
    but touchpad right button is workable
  
  [Where problems could occur]
  
   * For libevdev2 package, backport the upstream commit:
     
https://gitlab.freedesktop.org/libevdev/libevdev/-/commit/4226c7801b4ea1b0c7d1eaac47ca24ece8f24809
     The API is not originally exist in the system,
     so it will only be utilized by our model quirk.
  
   * For libinput, add model quirk for the platform to disable
     INPUT_PROP_BUTTONPAD bit.
     Only disable the INPUT_PROP_BUTTONPAD for specified model,
     and it doesn't issue any
     IO command to kernel, so the behavior should be the same
     as previous kernel when INPUT_PROP_BUTTONPAD is not set.
  
  [Other Info]
  
   * A public bug is reported
     
https://www.dell.com/community/Linux-Developer-Systems/Touchpad-right-click-button-not-working-with-Ubuntu-20-04-on/td-p/7636831
   * A workable build for Bionic is in my ppa
     https://launchpad.net/~kchsieh/+archive/ubuntu/training
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.16
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  u  1646 F pulseaudio
+ BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
+ CompositorRunning: None
+ CurrentDesktop: ubuntu:GNOME
+ DistUpgraded: Fresh install
+ DistroCodename: bionic
+ DistroRelease: Ubuntu 18.04
+ DistroVariant: ubuntu
+ GraphicsCard:
+  Intel Corporation Device [8086:9bc4] (rev 05) (prog-if 00 [VGA controller])
+Subsystem: Dell Device [1028:09c3]
+ InstallationDate: Installed on 2020-12-01 (0 days ago)
+ InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
+ MachineType: Dell Inc. Precision 7550
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=2964a5af-ac17-45ee-a009-41879da14e1b ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-42-generic N/A
+  linux-backports-modules-5.4.0-42-generic  N/A
+  linux-firmware1.173.19
+ Tags:  bionic ubuntu
+ Uname: Linux 5.4.0-42-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 09/01/2020
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.4.0
+ dmi.board.vendor: Dell Inc.
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd09/01/2020:svnDellInc.:pnPrecision7550:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
+ dmi.product.family: Precision
+ dmi.product.name: Precision 7550
+ dmi.product.sku: 09C3
+ dmi.sys.vendor: Dell Inc.
+ version.compiz: compiz N/A
+ version.libdrm2: libdrm2 2.4.101-2~18.04.1
+ version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
+ version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
+ version.xserver-xorg-core: xserver-xorg-core N/A
+ version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
+ version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
+ version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
+ version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1906341/+attachment/5439891/+files/AlsaInfo.txt

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1618516] Re: Byobu does not read aliases defined in /etc/profile.d or in .profile

2020-11-30 Thread Wileam Yonatan Phan
Seconding this. I confirm it is also present in both Ubuntu 18.04.5 LTS
and Ubuntu 20.04.1 LTS.

** Also affects: byobu (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/1618516

Title:
  Byobu does not read aliases defined in /etc/profile.d or in .profile

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

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

[Bug 1902044] Re: SRU the current 42.5 stable update

2020-11-30 Thread Robie Basak
Also 42.6 includes:

- Exclude snap and flatpak cache files (fixed regression that stopped
doing this)

Would this be a regression introduced by this upload?

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

Title:
  SRU the current 42.5 stable update

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

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

[Bug 1902044] Re: SRU the current 42.5 stable update

2020-11-30 Thread Robie Basak
I'm not clear on whether you want to update deja-dup on the basis of the
GNOME MRE or not.

If you intend to base this on the GNOME MRE, then I don't see this in
the current working list of included packages at
https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/8?u=rbasak so if
you want to proceed on this basis, this needs further discussion there.

If not based on the GNOME MRE, then your provided upload needs to meet
the criteria listed at
https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases.
Please provide a summary of how the package meets that criteria in the
SRU information.

** Also affects: deja-dup (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: deja-dup (Ubuntu Groovy)
   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/1902044

Title:
  SRU the current 42.5 stable update

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

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

[Bug 1902210] Proposed package upload rejected

2020-11-30 Thread Robie Basak
An upload of boinc to groovy-proposed has been rejected from the upload
queue for the following reason: "Upload contains many changes which
appear to contradict SRU policy to avoid regressions, and information on
them has not been provided.".

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

Title:
  Error when I launch Boinc Manager

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

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

[Bug 1902210] Re: Error when I launch Boinc Manager

2020-11-30 Thread Robie Basak
> the current package is not usable

AIUI, it is usable, just not by default, because a workaround is
available? In this case I don't think this is a justification for
ignoring normal SRU requirements to avoid regressing existing users.
Please provide an upload that either contains a minimal fix or otherwise
complies with SRU policy.

** Changed in: boinc (Ubuntu Groovy)
   Status: In Progress => Incomplete

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

Title:
  Error when I launch Boinc Manager

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

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

[Bug 1906128] Re: Touchpad not detected on ByteSpeed C15B laptop

2020-11-30 Thread Po-Hsu Lin
** Changed in: linux (Ubuntu)
   Status: Incomplete => In Progress

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

Title:
  Touchpad not detected on ByteSpeed C15B laptop

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

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

[Bug 1906341] Re: Touchpad button doesn't work on Dell Precision 7550/7750

2020-11-30 Thread Kai-Chuan Hsieh
Upload bionic libevdev debdiff.

** Patch added: "libevdev.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1906341/+attachment/5439889/+files/libevdev.debdiff

** Description changed:

  [Impact]
  
   * The touchpad's right button become no function after update to 5.4
  kernel
  
   * The INPUT_PROP_BUTTONPAD property is set by 5.4 kernel, so that
  libinput regard it as clickpad.
  
   * Add a model quirk to unset the bit can make touchpad's right button
  works normally.
  
  [Test Case]
  
   * 1. Boot into Ubuntu
     2. Identify touchpad input device number,
    can be obtained in $HOME/.local/share/xorg/Xorg.0.log
     3. $ udevadm info /sys/class/input/inputX
    check PROP environment variable,
-   it is 5 if INPUT_PROP_BUTTONPAD property is set
+   it is 5 if INPUT_PROP_BUTTONPAD property is set
     4. And the touchpad right button become no function
     5. After update the libevdev with disable_property
-   API and libinput10 with model quirk
+   API and libinput10 with model quirk
     6. reboot
     7. The input device PROP is still 5,
-   but touchpad right button is workable
+   but touchpad right button is workable
  
  [Where problems could occur]
  
   * For libevdev2 package, backport the upstream commit:
     
https://gitlab.freedesktop.org/libevdev/libevdev/-/commit/4226c7801b4ea1b0c7d1eaac47ca24ece8f24809
     The API is not originally exist in the system,
-so it will only be utilized by our model quirk.
+    so it will only be utilized by our model quirk.
  
   * For libinput, add model quirk for the platform to disable
-INPUT_PROP_BUTTONPAD bit.
+    INPUT_PROP_BUTTONPAD bit.
     Only disable the INPUT_PROP_BUTTONPAD for specified model,
-and it doesn't issue any
+    and it doesn't issue any
     IO command to kernel, so the behavior should be the same
-as previous kernel when INPUT_PROP_BUTTONPAD is not set.
+    as previous kernel when INPUT_PROP_BUTTONPAD is not set.
  
  [Other Info]
  
   * A public bug is reported
     
https://www.dell.com/community/Linux-Developer-Systems/Touchpad-right-click-button-not-working-with-Ubuntu-20-04-on/td-p/7636831
+  * A workable build for Bionic in my ppa
+https://launchpad.net/~kchsieh/+archive/ubuntu/training

** Description changed:

  [Impact]
  
   * The touchpad's right button become no function after update to 5.4
  kernel
  
   * The INPUT_PROP_BUTTONPAD property is set by 5.4 kernel, so that
  libinput regard it as clickpad.
  
   * Add a model quirk to unset the bit can make touchpad's right button
  works normally.
  
  [Test Case]
  
   * 1. Boot into Ubuntu
     2. Identify touchpad input device number,
    can be obtained in $HOME/.local/share/xorg/Xorg.0.log
     3. $ udevadm info /sys/class/input/inputX
    check PROP environment variable,
    it is 5 if INPUT_PROP_BUTTONPAD property is set
     4. And the touchpad right button become no function
     5. After update the libevdev with disable_property
    API and libinput10 with model quirk
     6. reboot
     7. The input device PROP is still 5,
    but touchpad right button is workable
  
  [Where problems could occur]
  
   * For libevdev2 package, backport the upstream commit:
     
https://gitlab.freedesktop.org/libevdev/libevdev/-/commit/4226c7801b4ea1b0c7d1eaac47ca24ece8f24809
     The API is not originally exist in the system,
     so it will only be utilized by our model quirk.
  
   * For libinput, add model quirk for the platform to disable
     INPUT_PROP_BUTTONPAD bit.
     Only disable the INPUT_PROP_BUTTONPAD for specified model,
     and it doesn't issue any
     IO command to kernel, so the behavior should be the same
     as previous kernel when INPUT_PROP_BUTTONPAD is not set.
  
  [Other Info]
  
   * A public bug is reported
     
https://www.dell.com/community/Linux-Developer-Systems/Touchpad-right-click-button-not-working-with-Ubuntu-20-04-on/td-p/7636831
-  * A workable build for Bionic in my ppa
-https://launchpad.net/~kchsieh/+archive/ubuntu/training
+  * A workable build for Bionic is in my ppa
+    https://launchpad.net/~kchsieh/+archive/ubuntu/training

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] Re: Touchpad button doesn't work on Dell Precision 7550/7750

2020-11-30 Thread Kai-Chuan Hsieh
Upload libinput debdiff

** Patch added: "libinput.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1906341/+attachment/5439888/+files/libinput.debdiff

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1802269] Re: script `lmod.sh` in `/etc/profile.d` errors out and dumps stack trace

2020-11-30 Thread Wileam Yonatan Phan
Try installing lua-posix, which is one of the prerequisites of Lmod, as shown 
in the documentation:
https://lmod.readthedocs.io/en/latest/030_installing.html

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

Title:
  script `lmod.sh` in `/etc/profile.d` errors out and dumps stack trace

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

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

[Bug 1906128] Re: Touchpad not detected on ByteSpeed C15B laptop

2020-11-30 Thread Po-Hsu Lin
** Summary changed:

- Touchpad not deteced on Bytespeed C15B laptop
+ Touchpad not detected on ByteSpeed C15B laptop

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

Title:
  Touchpad not detected on ByteSpeed C15B laptop

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

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

[Bug 1776622] Re: snapd updates on focal never finish installing. Can't install any other updates.

2020-11-30 Thread Daniel van Vugt
** Changed in: snapd
 Assignee: Manoj Bhargav (manoj-bhargav333) => (unassigned)

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

Title:
  snapd updates on focal never finish installing. Can't install any
  other updates.

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

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

[Bug 1906349] Re: package mysql-server-8.0 8.0.22-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1

2020-11-30 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package mysql-server-8.0 8.0.22-0ubuntu0.20.04.3 failed to
  install/upgrade: installed mysql-server-8.0 package post-installation
  script subprocess returned error exit status 1

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

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

[Bug 1906330] Re: nautilus crashes on opening

2020-11-30 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

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

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

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

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

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Low

** Changed in: nautilus (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/1906330

Title:
  nautilus crashes on opening

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

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

[Bug 1877089] Re: zfcpdump kernel can not be IPLed, wrong file name

2020-11-30 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   Status: In Progress => 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/1877089

Title:
  zfcpdump kernel can not be IPLed, wrong file name

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

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

[Bug 1906341] Re: Touchpad button doesn't work on Dell Precision 7550/7750

2020-11-30 Thread Kai-Chuan Hsieh
** Tags added: oem-priority originate-from-1905819 timbuktu

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

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906341] Missing required logs.

2020-11-30 Thread Ubuntu Kernel Bot
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1906341

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (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/1906341

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1906349] [NEW] package mysql-server-8.0 8.0.22-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1

2020-11-30 Thread Arjun Sharma
Public bug reported:

It's coming up again and again.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mysql-server-8.0 8.0.22-0ubuntu0.20.04.3
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.13
AptOrdering:
 mysql-client-8.0:amd64: Install
 mysql-server-8.0:amd64: Install
 mysql-server-core-8.0:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Dec  1 10:55:45 2020
DpkgHistoryLog:
 Start-Date: 2020-12-01  10:54:00
 Commandline: /usr/bin/unattended-upgrade
 Upgrade: mysql-client-8.0:amd64 (8.0.22-0ubuntu0.20.04.2, 
8.0.22-0ubuntu0.20.04.3), mysql-server-8.0:amd64 (8.0.22-0ubuntu0.20.04.2, 
8.0.22-0ubuntu0.20.04.3), mysql-server-core-8.0:amd64 (8.0.22-0ubuntu0.20.04.2, 
8.0.22-0ubuntu0.20.04.3)
ErrorMessage: installed mysql-server-8.0 package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2020-11-28 (2 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Logs.var.log.daemon.log:
 
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
 [mysqldump]
 quick
 quote-names
 max_allowed_packet = 16M
MySQLVarLibDirListing: ['mysql.ibd', 'server-cert.pem', 'ib_buffer_pool', 
'sys', 'binlog.01', 'ibtmp1', 'pharmacy', 'ibdata1', 'debian-5.7.flag', 
'#ib_16384_1.dblwr', 'performance_schema', 'undo_002', 'binlog.index', 
'ib_logfile1', '#innodb_temp', '#ib_16384_0.dblwr', 'ca.pem', 'client-key.pem', 
'undo_001', 'public_key.pem', 'FX505GE.pid', 'ib_logfile0', 'client-cert.pem', 
'auto.cnf', 'binlog.05', 'private_key.pem', 'ca-key.pem', 'binlog.03', 
'binlog.04', 'mysql', 'binlog.02', 'server-key.pem']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=339fd928-2477-4714-bb51-e3529b745c25 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: mysql-8.0
Title: package mysql-server-8.0 8.0.22-0ubuntu0.20.04.3 failed to 
install/upgrade: installed mysql-server-8.0 package post-installation script 
subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mysql-8.0 (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/1906349

Title:
  package mysql-server-8.0 8.0.22-0ubuntu0.20.04.3 failed to
  install/upgrade: installed mysql-server-8.0 package post-installation
  script subprocess returned error exit status 1

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

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

[Bug 1776622] Re: snapd updates on focal never finish installing. Can't install any other updates.

2020-11-30 Thread Manoj Bhargav
Updating snap never finish-while I do not have/removed all snaps.

** Changed in: snapd
 Assignee: Michael Vogt (mvo) => Manoj Bhargav (manoj-bhargav333)

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

Title:
  snapd updates on focal never finish installing. Can't install any
  other updates.

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

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

[Bug 1906320] Re: fake-device-wrapper should bind-mount efivars

2020-11-30 Thread Martin Pitt
FTR, I would strongly advise against that, see
https://github.com/martinpitt/umockdev/issues/110#issuecomment-736224503
. You want the tests to work independently on the hardware it's running
on, so that you can run it on e.g. standard autopkgtest infra.

You could create /sys/firmware/efi/efivars/ tarballs of a bunch of real
systems with the properties that you want, keep them in the tests, and
unpack these in your test cases. You most probably just need a few of
them, so you can strip them down or possibly create them individually as
files, but a full tarball might be the quickest start.

** Bug watch added: github.com/martinpitt/umockdev/issues #110
   https://github.com/martinpitt/umockdev/issues/110

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

Title:
  fake-device-wrapper should bind-mount efivars

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

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

[Bug 1906128] Re: Touchpad not deteced on Bytespeed C15B laptop

2020-11-30 Thread Po-Hsu Lin
Hi Tom,

Thanks for the test, it will be a plus to verify this on Bionic as well.

I will submit this patch upstream and bring it back to ubuntu kernels.
Cheers

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

Title:
  Touchpad not deteced on Bytespeed C15B laptop

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

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

[Bug 1906341] Re: Touchpad button doesn't work on Dell Precision 7550/7750

2020-11-30 Thread Daniel van Vugt
** Tags added: focal

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

** Also affects: linux (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/1906341

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

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

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

[Bug 1307175] Re: parted_server crashed with SIGABRT in ped_assert()

2020-11-30 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1306704 ***
https://bugs.launchpad.net/bugs/1306704

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

** Changed in: ubiquity (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/1307175

Title:
  parted_server crashed with SIGABRT in ped_assert()

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

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

[Bug 1906344] Re: grub is unable to chainboot from network to SATA drive

2020-11-30 Thread Lee Trager
** Description changed:

  Machines which are managed by MAAS are configured to always network
  boot. When an operating system is deployed grub is sent[1] a
  configuration file which searches drives for recognized boot loaders.
  When the local disk is a SATA drive this process is not working. The
  config exits at the end to fallback to booting the next configured
  device but this config does not always exist. In that case the
  deployment fails.
  
+ I've verified this happens with grub from
+ Focal(1.142.9+2.04-1ubuntu26.7) and Bionic(1.93.22+2.02-2ubuntu8.20).
+ 
  Reproduction:
  1. Create a KVM which uses an emulated SATA drive and UEFI firmware.
  2. Add the machine and commission it in MAAS
  3. Try deploying any operating system. CentOS 8 currently fails to deploy 
because it does not create a UEFI entry.
  
  [1]
  
https://git.launchpad.net/maas/tree/src/provisioningserver/templates/uefi/config.local.amd64.template

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

Title:
  grub is unable to chainboot from network to SATA drive

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

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

[Bug 1862878] Re: add_key01 from ubuntu_ltp_syscalls failed on Bionic s390x

2020-11-30 Thread Po-Hsu Lin
Passed with 4.15.0-126.129-generic on B s390x LPAR / zVM
Closing this bug 

** Changed in: ubuntu-kernel-tests
   Status: Incomplete => Fix Released

** Changed in: linux (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/1862878

Title:
  add_key01 from ubuntu_ltp_syscalls failed on Bionic s390x

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

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

[Bug 1906344] [NEW] grub is unable to chainboot from network to SATA drive

2020-11-30 Thread Lee Trager
Public bug reported:

Machines which are managed by MAAS are configured to always network
boot. When an operating system is deployed grub is sent[1] a
configuration file which searches drives for recognized boot loaders.
When the local disk is a SATA drive this process is not working. The
config exits at the end to fallback to booting the next configured
device but this config does not always exist. In that case the
deployment fails.

I've verified this happens with grub from
Focal(1.142.9+2.04-1ubuntu26.7) and Bionic(1.93.22+2.02-2ubuntu8.20).

Reproduction:
1. Create a KVM which uses an emulated SATA drive and UEFI firmware.
2. Add the machine and commission it in MAAS
3. Try deploying any operating system. CentOS 8 currently fails to deploy 
because it does not create a UEFI entry.

[1]
https://git.launchpad.net/maas/tree/src/provisioningserver/templates/uefi/config.local.amd64.template

** Affects: grub2 (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/1906344

Title:
  grub is unable to chainboot from network to SATA drive

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

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

[Bug 1783881] Re: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes

2020-11-30 Thread Kelsey Margarete Skunberg
Found on Groovy/linux 5.8.0-31.33

** Tags added: 5.8 groovy

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

Title:
  ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits
  number of processes

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

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

[Bug 1906236] Re: Allow host runtime PM as default for Intel Maple Ridge xHCI

2020-11-30 Thread You-Sheng Yang
** Description changed:

  Intel Maple Ridge is successor of Titan Ridge Thunderbolt controller. As
  Titan Ridge this one also includes xHCI host controller. In order to
  safe energy we should put it to low power state by default when idle.
  For this reason allow host runtime PM for Maple Ridge.
  
  
https://lore.kernel.org/linux-usb/20201105110031.8691-1-mika.westerb...@linux.intel.com/
  Accepted in 
https://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git/log/?h=for-usb-linus
+ 
+ And
+ 
https://lore.kernel.org/lkml/20201119155523.41332-1-mika.westerb...@linux.intel.com/

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

Title:
  Allow host runtime PM as default for Intel Maple Ridge xHCI

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

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

[Bug 1891944] Re: please remove golang-1.13 from groovy

2020-11-30 Thread Launchpad Bug Tracker
[Expired for golang-1.13 (Ubuntu) because there has been no activity for
60 days.]

** Changed in: golang-1.13 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  please remove golang-1.13 from groovy

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

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

[Bug 1894221] Re: system is not able to recognize touchpad

2020-11-30 Thread Launchpad Bug Tracker
[Expired for linux-signed-hwe-5.4 (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: linux-signed-hwe-5.4 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  system is not able to recognize touchpad

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

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

[Bug 1897890] Re: Upgrade fails on python-is-python2 calculation step

2020-11-30 Thread Launchpad Bug Tracker
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no
activity for 60 days.]

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

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

Title:
  Upgrade fails on python-is-python2 calculation step

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

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

[Bug 1897781] Re: System upgrade from Ubuntu 18.04 to 20.04 stops part-way through.

2020-11-30 Thread Launchpad Bug Tracker
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no
activity for 60 days.]

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

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

Title:
  System upgrade from Ubuntu 18.04 to 20.04 stops part-way through.

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

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

[Bug 1897939] Re: package freeradius-mysql 3.0.20+dfsg-3build1 failed to install/upgrade: el subproceso instalado paquete freeradius-mysql script post-installation devolvió el código de salida de erro

2020-11-30 Thread Launchpad Bug Tracker
[Expired for freeradius (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  package freeradius-mysql 3.0.20+dfsg-3build1 failed to
  install/upgrade: el subproceso instalado paquete freeradius-mysql
  script post-installation devolvió el código de salida de error 1

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

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

[Bug 1898008] Re: [Errno5] Input/output error

2020-11-30 Thread Launchpad Bug Tracker
[Expired for Ubuntu because there has been no activity for 60 days.]

** Changed in: ubuntu
   Status: Incomplete => Expired

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

Title:
  [Errno5] Input/output error

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

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

[Bug 1898073] Re: There is a bug.

2020-11-30 Thread Launchpad Bug Tracker
[Expired for Ubuntu because there has been no activity for 60 days.]

** Changed in: ubuntu
   Status: Incomplete => Expired

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

Title:
  There is a bug.

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

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

[Bug 1902710] Re: [SRU] Enable support for Wallaby Cloud Archive

2020-11-30 Thread Launchpad Bug Tracker
This bug was fixed in the package software-properties - 0.99.4

---
software-properties (0.99.4) hirsute; urgency=medium

  * cloudarchive: Enable support for the Wallaby Ubuntu Cloud Archive on
20.04 (LP: #1902710).

 -- Corey Bryant   Tue, 03 Nov 2020 08:58:47
-0500

** Changed in: software-properties (Ubuntu Hirsute)
   Status: Fix Committed => 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/1902710

Title:
  [SRU] Enable support for Wallaby Cloud Archive

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

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

[Bug 1902808] Re: Upgrade sssd in 20.04 to the version in 20.10 as the 20.04 version crashes

2020-11-30 Thread Treviño
Adam,

I've marked this as fixed for ubuntu in the latest released version (so
20.10), however it's not clear what upstream commit fixed this yet.

If sssd completely crashes you should install the debug symbols [1] and
try to attach to the process with gdb or see if you get a crash in
/var/crash

[1] https://wiki.ubuntu.com/Debug%20Symbol%20Packages

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

Title:
  Upgrade sssd in 20.04 to the version in 20.10 as the 20.04 version
  crashes

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

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

[Bug 1906341] [NEW] Touchpad button doesn't work on Dell Precision 7550/7750

2020-11-30 Thread Kai-Chuan Hsieh
Public bug reported:

[Impact]

 * The touchpad's right button become no function after update to 5.4
kernel

 * The INPUT_PROP_BUTTONPAD property is set by 5.4 kernel, so that
libinput regard it as clickpad.

 * Add a model quirk to unset the bit can make touchpad's right button
works normally.

[Test Case]

 * 1. Boot into Ubuntu
   2. Identify touchpad input device number,
  can be obtained in $HOME/.local/share/xorg/Xorg.0.log
   3. $ udevadm info /sys/class/input/inputX
  check PROP environment variable,
  it is 5 if INPUT_PROP_BUTTONPAD property is set
   4. And the touchpad right button become no function
   5. After update the libevdev with disable_property
  API and libinput10 with model quirk
   6. reboot
   7. The input device PROP is still 5,
  but touchpad right button is workable

[Where problems could occur]

 * For libevdev2 package, backport the upstream commit:
   
https://gitlab.freedesktop.org/libevdev/libevdev/-/commit/4226c7801b4ea1b0c7d1eaac47ca24ece8f24809
   The API is not originally exist in the system,
   so it will only be utilized by our model quirk.

 * For libinput, add model quirk for the platform to disable
   INPUT_PROP_BUTTONPAD bit.
   Only disable the INPUT_PROP_BUTTONPAD for specified model,
   and it doesn't issue any
   IO command to kernel, so the behavior should be the same
   as previous kernel when INPUT_PROP_BUTTONPAD is not set.

[Other Info]

 * A public bug is reported
   
https://www.dell.com/community/Linux-Developer-Systems/Touchpad-right-click-button-not-working-with-Ubuntu-20-04-on/td-p/7636831

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

** Description changed:

  [Impact]
  
-  * The touchpad's right button become no function after update to 5.4
+  * The touchpad's right button become no function after update to 5.4
  kernel
  
-  * The INPUT_PROP_BUTTONPAD property is set by 5.4 kernel, so that
+  * The INPUT_PROP_BUTTONPAD property is set by 5.4 kernel, so that
  libinput regard it as clickpad.
  
-  * Add a model quirk to unset the bit can make touchpad's right button
+  * Add a model quirk to unset the bit can make touchpad's right button
  works normally.
  
  [Test Case]
  
-  * 1. Boot into Ubuntu
-2. Identify touchpad input device number,
-   can be obtained in $HOME/.local/share/xorg/Xorg.0.log
-3. $ udevadm info /sys/class/input/inputX
-   check PROP environment variable, it is 5 if INPUT_PROP_BUTTONPAD 
property is set
-4. And the touchpad right button become no function
-5. After update the libevdev with disable_property API and libinput10 with 
model quirk
-6. reboot
-7. The input device PROP is still 5, but touchpad right button is workable
+  * 1. Boot into Ubuntu
+    2. Identify touchpad input device number,
+   can be obtained in $HOME/.local/share/xorg/Xorg.0.log
+    3. $ udevadm info /sys/class/input/inputX
+   check PROP environment variable,
+   it is 5 if INPUT_PROP_BUTTONPAD property is set
+    4. And the touchpad right button become no function
+    5. After update the libevdev with disable_property
+   API and libinput10 with model quirk
+    6. reboot
+    7. The input device PROP is still 5,
+   but touchpad right button is workable
  
  [Where problems could occur]
  
-  * For libevdev2 package, backport the upstream commit:
-
https://gitlab.freedesktop.org/libevdev/libevdev/-/commit/4226c7801b4ea1b0c7d1eaac47ca24ece8f24809
-The API is not originally exist in the system, so it will only be utilized 
by our model quirk.
+  * For libevdev2 package, backport the upstream commit:
+    
https://gitlab.freedesktop.org/libevdev/libevdev/-/commit/4226c7801b4ea1b0c7d1eaac47ca24ece8f24809
+    The API is not originally exist in the system,
+so it will only be utilized by our model quirk.
  
-  * For libinput, add model quirk for the platform to disable 
INPUT_PROP_BUTTONPAD bit.
-Only disable the INPUT_PROP_BUTTONPAD for specified model, and it doesn't 
issue any
-IO command to kernel, so the behavior should be the same as previous 
kernel when 
-INPUT_PROP_BUTTONPAD is not set
+  * For libinput, add model quirk for the platform to disable
+INPUT_PROP_BUTTONPAD bit.
+    Only disable the INPUT_PROP_BUTTONPAD for specified model,
+and it doesn't issue any
+    IO command to kernel, so the behavior should be the same
+as previous kernel when INPUT_PROP_BUTTONPAD is not set.
  
  [Other Info]
-  
-  * A public bug is reported 
-
https://www.dell.com/community/Linux-Developer-Systems/Touchpad-right-click-button-not-working-with-Ubuntu-20-04-on/td-p/7636831
+ 
+  * A public bug is reported
+    
https://www.dell.com/community/Linux-Developer-Systems/Touchpad-right-click-button-not-working-with-Ubuntu-20-04-on/td-p/7636831

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

Title:
  Touchpad 

[Bug 1857810] Re: osspd no longer works: ERR: failed to connect context, state=5 (Bad state)

2020-11-30 Thread Douglas Wiedemann
Wasn't able to get this working. but found that padsp is still working
for 64-bit binaries.

32-bit binaries will need the libpulsedsp:i386 package and to create a
"padsp32" binary by copying the padsp in /usr/bin back as padsp32, and
editing the binary to point the LD_PRELOAD to /usr/lib/i386-linux-
gnu/pulseaudio/libpulsedsp.so instead of /usr/lib/x86_64-linux-
gnu/pulseaudio/libpulsedsp.so

After that, just use either padsp or padsp32 in front of the program and
it should work.

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

Title:
  osspd no longer works: ERR: failed to connect context, state=5 (Bad
  state)

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

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

[Bug 1867570] Re: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le

2020-11-30 Thread Kelsey Margarete Skunberg
Found on Groovy/linux 5.8.0-31.33 with some output differences:


11/26 10:07:52 DEBUG| utils:0153| [stdout] # selftests: net: 
reuseport_bpf_numa
11/26 10:07:52 DEBUG| utils:0153| [stdout] #  IPv4 UDP 
11/26 10:07:52 DEBUG| utils:0153| [stdout] # send node 0, receive socket 0
11/26 10:07:52 DEBUG| utils:0153| [stdout] # libnuma: Warning: Cannot read 
node cpumask from sysfs
11/26 10:07:52 DEBUG| utils:0153| [stdout] # ./reuseport_bpf_numa: failed 
to pin to node: No such file or directory
11/26 10:07:52 DEBUG| utils:0153| [stdout] not ok 3 selftests: net: 
reuseport_bpf_numa # exit=1

** Tags added: 5.8 groovy sru-20201109

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

Title:
  reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on
  ppc64le

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

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

[Bug 1906158] Re: Mouse and Keyboard input stalling/pausing/freezing after there is no mouse or keyboard activity for a few seconds.

2020-11-30 Thread Craig Christie
I'm out of my element here and don't know what I'm doing.  I do know
that the updates release today resolved the problem I was having so I'll
make the changes that seem right to me.  Hopefully it won't leave too
big a mess for someone else to clean up.

** Changed in: ubuntu
   Status: New => Fix Released

** Changed in: ubuntu
 Assignee: (unassigned) => Craig Christie (curmudgeoncraig)

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

Title:
  Mouse and Keyboard input stalling/pausing/freezing after there is no
  mouse or keyboard activity for a few seconds.

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

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

[Bug 1845951] Re: ubuntu_lttng_smoke_test failed with B-hwe 5.0 ARM64

2020-11-30 Thread Kelsey Margarete Skunberg
Found on Groovy/linux 5.8.0-31.33


stdout:
== lttng smoke test of session create/destroy ==
Spawning a session daemon
FAILED (lttng create)
FAILED (lttng destroy)
 
== lttng smoke test trace context switches ==
Spawning a session daemon
FAILED (lttng create)
 
Summary: 0 passed, 4 failed
stderr:
PERROR - 08:02:55.459419324 [2194052/2194052]: fcntl lock file: Resource 
temporarily unavailable (in utils_create_lock_file() at utils.c:657)
Error: Could not get lock file /var/run/lttng/lttng-sessiond.lck, another 
instance is running.
Error: A session daemon is already running.
Error: Session daemon terminated with an error (exit status: 1)
Error: Problem occurred while launching session daemon (/usr/bin/lttng-sessiond)
Error: No session daemon is available
PERROR - 08:02:55.512473464 [2194055/2194055]: fcntl lock file: Resource 
temporarily unavailable (in utils_create_lock_file() at utils.c:657)
Error: Could not get lock file /var/run/lttng/lttng-sessiond.lck, another 
instance is running.
Error: A session daemon is already running.
Error: Session daemon terminated with an error (exit status: 1)
Error: Problem occurred while launching session daemon (/usr/bin/lttng-sessiond)
11/26 08:02:55 DEBUG| utils:0116| Running 'apt-get remove --yes 
lttng-modules-dkms

** Tags added: 5.8 groovy sru-20201109

** Tags added: ppc64el

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

Title:
  ubuntu_lttng_smoke_test failed with B-hwe 5.0 ARM64

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

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

[Bug 1864140] Re: ubuntu_fan_smoke_test failed with unable to fetch file from http://ports.ubuntu.com on PowerPC

2020-11-30 Thread Kelsey Margarete Skunberg
Found on Groovy/linux 5.8.0-31.33

** Tags added: 5.8 groovy sru-20201109

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

Title:
  ubuntu_fan_smoke_test failed with unable to fetch file from
  http://ports.ubuntu.com on PowerPC

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

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

[Bug 1837365] Re: ubuntu_kvm_smoke_test failed on Intel KVM node with D-KVM kernel

2020-11-30 Thread Kelsey Margarete Skunberg
Found on Groovy/linux 5.8.0-31.33

** Tags added: 5.8 groovy sru-20201109

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

Title:
  ubuntu_kvm_smoke_test failed on Intel KVM node with D-KVM kernel

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

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

[Bug 1885087] Re: Can't keep brightness value after reboot/poweroff in some nvidia gfx

2020-11-30 Thread hugh chao
tried nvidia-graphics-drivers-455 in focal which can fix this issue, I
didn't observe any regression.

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

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

Title:
  Can't keep brightness value after reboot/poweroff in some nvidia gfx

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

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

[Bug 1847361] Re: Upgrade of qemu binaries causes running instances not able to dynamically load modules

2020-11-30 Thread Trent Lloyd
Note: This patch has related regressions in Hirsute due to the version number 
containing a space:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906245
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1905377

Seems the patch is temporarily dropped will need to ensure we don't
totally lose the fix

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

Title:
  Upgrade of qemu binaries causes running instances not able to
  dynamically load modules

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

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

[Bug 1905790] Re: Recompile SSSD in 20.04 using OpenSSL (instead of NSS) support

2020-11-30 Thread Treviño
> Are you sure about this? TLS has a wide variety of protocol options and the 
> supported vs.
> "available" cryptosystem matrix is complex. Won't these all change if the 
> underlying
> implementation changes?

Well, I focused mostly in the PKCS#11 changes, but for all its internal
crypto operations SSSD had for some long time now [1] started supporting
OpenSSL, replaced as default [2] and finally dropped [3] NSS at all and
the two crypto backends have been used as feature-parity alternatives.

Probably not enough to compare, but from what I see in these matrices
[4], there's basically nothing that NSS supports and OpenSSL doesn't
(while it's true the other way around).

Not to mention that we already switched to an OpenSSL-based version of
SSSD in 21.10, and even if its user base can't be compared to 20.04, so
far I didn't read about related issues [5].

That said, if the SRU team would feel more confident in only having the
p11_child to be built with OpenSSL, it should be technically possible,
of course not as easy (and probably safer and more future-proof) as
switching completely.


[1] https://github.com/SSSD/sssd/issues/4521
[2] https://github.com/SSSD/sssd/pull/1042
[3] https://github.com/SSSD/sssd/issues/1041
[4] https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations
[5] https://github.com/SSSD/sssd/issues?q=is%3Aissue+openssl+

** Bug watch added: github.com/SSSD/sssd/issues #4521
   https://github.com/SSSD/sssd/issues/4521

** Bug watch added: github.com/SSSD/sssd/issues #1041
   https://github.com/SSSD/sssd/issues/1041

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

Title:
  Recompile SSSD in 20.04 using OpenSSL (instead of NSS) support

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

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

[Bug 1906128] Re: Touchpad not deteced on Bytespeed C15B laptop

2020-11-30 Thread Tom Anschutz
Hi Po-Hsu,

I installed the Focal kernel (using dpkg -i) then removed the
i8042.noloop=1 boot option and rebooted.  The touchpad still works, and
I confirmed that I was actually running the 5.0.4-57 kernel you
provided.   Looks really good for Focal.

Would you like me to do the same for the Bionic kernel, or was that just
a choice in case I needed it?

Thanks and Very Best Regards!
Tom

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

Title:
  Touchpad not deteced on Bytespeed C15B laptop

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

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

[Bug 1830361] Re: cpuset_sched_domains from controller test suite in LTP failed

2020-11-30 Thread Kelsey Margarete Skunberg
Found on Groovy/linux 5.8.0-31.33 P9  with a little bit different
output:


99606.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 29 
TINFO: /bin/echo: write error: Invalid argument
99607.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 29 
TFAIL: set general group1 parameter failed.
99608.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 31 
TINFO: general group load balance test
99609.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 31 
TINFO: root group info:
99610.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 31 
TINFO: sched load balance: 0
99611.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 31 
TINFO: general group1 info:
99612.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 31 
TINFO: cpus: 1,2
99613.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 31 
TINFO: sched load balance: 1
99614.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 31 
TINFO: general group2 info:
99615.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 31 
TINFO: cpus: 0,3
99616.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 31 
TINFO: sched load balance: 1
99617.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 31 
TINFO: CPU hotplug: none
99618.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 31 
TINFO: /bin/echo: write error: Invalid argument
99619.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 31 
TFAIL: set general group1 parameter failed.
99620.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 33 
TINFO: general group load balance test
99621.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 33 
TINFO: root group info:
99622.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 33 
TINFO: sched load balance: 0
99623.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 33 
TINFO: general group1 info:
99624.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 33 
TINFO: cpus: 1,2
99625.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 33 
TINFO: sched load balance: 1
99626.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 33 
TINFO: general group2 info:
99627.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 33 
TINFO: cpus: 1,3
99628.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 33 
TINFO: sched load balance: 1
99629.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 33 
TINFO: CPU hotplug: none
99630.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 33 
TINFO: /bin/echo: write error: Invalid argument
99631.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 33 
TFAIL: set general group1 parameter failed.
99632.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 35 
TINFO: general group load balance test
99633.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 35 
TINFO: root group info:
99634.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 35 
TINFO: sched load balance: 0
99635.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 35 
TINFO: general group1 info:
99636.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 35 
TINFO: cpus: 1,2
99637.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 35 
TINFO: sched load balance: 1
99638.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 35 
TINFO: general group2 info:
99639.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 35 
TINFO: cpus: 1,3
99640.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 35 
TINFO: sched load balance: 1
99641.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 35 
TINFO: CPU hotplug: offline
99642.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 35 
TINFO: /bin/echo: write error: Invalid argument
99643.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 35 
TFAIL: set general group1 parameter failed.
99644.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 37 
TINFO: general group load balance test
99645.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 37 
TINFO: root group info:
99646.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 37 
TINFO: sched load balance: 0
99647.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 37 
TINFO: general group1 info:
99648.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 37 
TINFO: cpus: 1,2
99649.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 37 
TINFO: sched load balance: 1
99650.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 37 
TINFO: general group2 info:
99651.  11/26 19:15:21 DEBUG| utils:0153| [stdout] cpuset_sched_domains 37 
TINFO: cpus: 1,3
99652.  11/26 19:15:21 DEBUG| utils:0153| 

Re: [Bug 1906304] Re: Deja Dup should delete old backups to make room for new backups and it doesn't

2020-11-30 Thread TOP
I also uninstalled the vanilla version of deja-dup that came with 18.04 and
installed the snap with the latest. Will see in a few days whether anything
is different.

On Mon, Nov 30, 2020 at 5:00 PM Michael Terry <1906...@bugs.launchpad.net>
wrote:

> Oh that’s interesting yes. I’ll have to see how to get the quota info
> from gvfs and apply it to our calculations. Thank you for the report!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1906304
>
> Title:
>   Deja Dup should delete old backups to make room for new backups and it
>   doesn't
>
> Status in deja-dup package in Ubuntu:
>   New
>
> Bug description:
>   Backups are being stored using and external usb drive with the zfs
>   filesystem. There is a quota set on the backup partition. When deja-
>   dup fills the partition to it's quota it simply stops backing up
>   instead of deleting the oldest backups to make room for new backups.
>   Setting the quota higher will allow deja-dup to continue, but the this
>   is not a desired behavior, after all, what are quotas for but to limit
>   disk usage.
>
>   Deja-dup does not seem to recognize a zfs quota limit as a full disk.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: deja-dup 37.1-2fakesync1ubuntu0.1
>   ProcVersionSignature: Ubuntu 5.4.0-54.60~18.04.1-generic 5.4.65
>   Uname: Linux 5.4.0-54-generic x86_64
>   NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
>   ApportVersion: 2.20.9-0ubuntu7.20
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Nov 30 14:40:16 2020
>   InstallationDate: Installed on 2020-01-09 (326 days ago)
>   InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
> (20190805)
>   SourcePackage: deja-dup
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1906304/+subscriptions
>


-- 
*Paul B. Kellner*

###
Check out my favorite tunes from Pocket Vinyl 

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

Title:
  Deja Dup should delete old backups to make room for new backups and it
  doesn't

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

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

[Bug 1830360] Re: cpuset_load_balance from controller test suite in LTP failed

2020-11-30 Thread Kelsey Margarete Skunberg
Found on Groovy/linux 5.8.0-31.33

** Tags added: 5.8 groovy sru-20201109

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

Title:
  cpuset_load_balance from controller test suite in LTP failed

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

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

[Bug 1905790] Re: Recompile SSSD in 20.04 using OpenSSL (instead of NSS) support

2020-11-30 Thread Treviño
** Description changed:

  [ Impact ]
  
- SSSD supports two security backends: NSS and OpenSSL.
+ SSSD supports in 20.04 two security backends: NSS and OpenSSL.
+ (speaking in past tense as upstream dropped NSS support completely)
  
  Those two backends are used for various generic crypto features (so they
  are interchangeable), but also for the management of the PKCS#11 modules
  for smart cards.
  
  In this case, the main problem is that by using NSS it also relies on
  the presence of a "system NSS" database [1] that is something present in
  Fedora and RHEL, but not in ubuntu or generic Linux distributions.
  
  In order to make SSSD to find a smart card module, we would then need to 
create a such database that mentions a p11kit proxy that will eventually load 
the p11-kit module and then add the card CA certificate to the same DB (see 
more details in [2]).
  And even in such case... It will not work at login phase.
  
  This is making support for Smart-card based authentication in 20.04
  quite complicated, and hard to implement in professional environments.
  
  As per this, just recompiling SSSD to use OpenSSL (as it already happens
  starting from 20.10) would be enough to make the p11_child tool (the one
  in charge for smartcard authentications) to be able to get the smartcard
  devices from p11-kit allowed modules and to check their certificate
  using CA certificates in the ubuntu system ca certificate files (or
  other configured file).
  
  One more mayor reason to do this, is also that if we fix 20.04 now to
  use the "proper" method, people who will configure smartcard access
  there via SSSD (not easily possible right now) won't be affected by
  future migrations.
  
  [ Test case ]
  
  With a smartcard reader available (and with a card in its slot) launch:
   - sudo /usr/libexec/sssd/p11_child --pre -d 10 --debug-fd=2 \
     --nssdb=/etc/ssl/certs/ca-certificates.crt
  
  The tool should find your card:
  
  (2020-11-26 21:34:22:020395): [p11_child[100729]] [do_card] (0x4000): Module 
List:
  (2020-11-26 21:34:22:020481): [p11_child[100729]] [do_card] (0x4000): common 
name: [p11-kit-trust].
  (2020-11-26 21:34:22:020497): [p11_child[100729]] [do_card] (0x4000): dll 
name: [/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so].
  (2020-11-26 21:34:22:020569): [p11_child[100729]] [do_card] (0x4000): 
Description [/etc/ssl/certs/ca-certificates.crt  
PKCS#11 Kit ] Manufacturer [PKCS#11 Kit 
] flags [1] removable [false] token present [true].
  (2020-11-26 21:34:22:020611): [p11_child[100729]] [do_card] (0x4000): common 
name: [opensc-pkcs11].
  (2020-11-26 21:34:22:020646): [p11_child[100729]] [do_card] (0x4000): dll 
name: [/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so].
  (2020-11-26 21:34:22:025443): [p11_child[100729]] [do_card] (0x4000): 
Description [VMware Virtual USB CCID 00 00   
VMware  ] Manufacturer [VMware  
] flags [7] removable [true] token present [true].
  (2020-11-26 21:34:22:025725): [p11_child[100729]] [do_card] (0x4000): Found 
[MARCO TREVISAN (PIN CNS0)] in slot [VMware Virtual USB CCID 00 00][0] of 
module [1][/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so].
  
  Then the tool might fail if the card certificate is not added to the ca-
  certificates.crt, but this is outside the scope of the test case.
  
  What it matters is that the card is found.
  
  [ Regression potential ]
  
- While the change may involve quite different code paths when it comes to
- security features, I think we trust OpenSSL enough to be an acceptable
- crypto backend. And behavior should not change.
+ While the change may involve quite different code paths when it comes to 
security features, I think we trust OpenSSL enough to be an acceptable crypto 
backend. And behavior should not change.
+ Also assuming that upstream dropped NSS support completely in latest release, 
keeping the same functionalities.
  
  The only binary that is really affected in its behavior is p11_child.
  
  And I'm confident that even changing this a lot, it will break only
  those setup (if there are any, given that smartcard access is currently
  not supported by ubuntu) that have been manually configured using an
  unsupported system NSS db.
  
  In the remote case there are such configurations, though, the fix will
  be as easy as adding the CA certificates to the new PAM cert DB (by
  default /etc/sssd/pki/sssd_auth_ca_db.pem), while the p11-kit modules
  will continue to work as before.
  
  It's also technically easy to do a postinst script that will just export
  all the certificates from the old nss db (/etc/pki/nssdb) into the new
  file, if we want to avoid any unlikely breakage.
  
  [1] 
https://github.com/SSSD/sssd/blob/sssd-2_3_1/src/responder/pam/pamsrv.c#L53
  [2] 

[Bug 1842032] Re: cpufreq_boost from kernel_misc in ubuntu_ltp failed on B-5.0 / 5.3 P9

2020-11-30 Thread Kelsey Margarete Skunberg
Found on Groovy/linux 5.8.0-31.33 ppc64el (P9)

** Tags added: 5.8 groovy sru-20201109

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

Title:
  cpufreq_boost from kernel_misc in ubuntu_ltp failed on B-5.0 / 5.3 P9

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

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

  1   2   3   4   5   6   7   8   >