date:20210107

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

** Changed in: openjdk-8 (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/1797101

Title:
  incompatibility with libxmlsec

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

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

[Bug 1910565] [NEW] Ubuntu 20.04 Text Editor displays a black screen, unable to type.

2021-01-07 Thread Bernard Stafford

Public bug reported:

gedit 3.36.2 opens. Displays a black screen, unable to type to form a
document. Save works and the drop-down box opens preferences and the
other functions work. Just unable to type on the screen.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2
ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18
Uname: Linux 5.8.0-34-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan  7 10:04:30 2021
InstallationDate: Installed on 2020-11-28 (39 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-5.8
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Summary changed:

- Text Editor displays a black screen, unable to type.
+ Ubuntu 20.04 Text Editor displays a black screen, unable to type.

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

Title:
  Ubuntu 20.04 Text Editor displays a black screen, unable to type.

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

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

[Bug 1901797] Re: The upgrade to 20.10 is not taking place

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

Title:
  The upgrade to 20.10 is not taking place

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

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

[Bug 1910134] Re: Provide .bin files too

Not too happy with the test case, but also not much else one can do.
Especially that the SRU itself is trivial with no real risk of
regressions. Accepting.

** Changed in: opensbi (Ubuntu Groovy)
   Status: In Progress => Fix Committed

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

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

Title:
  Provide .bin files too

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

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

[Bug 1910134] Please test proposed package

Hello Dimitri, or anyone else affected,

Accepted opensbi into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/opensbi/0.8-1~ubuntu0.20.04.2 in a
few hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  Provide .bin files too

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

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

[Bug 1899233] Re: post login - no apps launched - virtualbox-dkms 6.1.10-dfsg-1~ubuntu1.20.04.1: virtualbox kernel module failed to build

2021-01-07 Thread Salim

as peterzay said, I'm facing the same bug after updating my Ubuntu 20.04
this morning.

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

Title:
  post login - no apps launched - virtualbox-dkms
  6.1.10-dfsg-1~ubuntu1.20.04.1: virtualbox kernel module failed to
  build

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

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

[Bug 1880197] Re: ephemeral key used to sign mokmanager should have better certificate attributes

2021-01-07 Thread Jeff Squyres

** Merge proposal linked:
   
https://code.launchpad.net/~jsquyres-cisco/ubuntu/+source/shim/+git/shim/+merge/395923

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

Title:
  ephemeral key used to sign mokmanager should have better certificate
  attributes

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

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

[Bug 1910561] Re: Fix right sounds and mute/micmute LEDs for HP ZBook Fury 15/17 G7 Mobile Workstation

2021-01-07 Thread jeremyszu

Here is the discussion on upstream
https://lkml.org/lkml/2021/1/6/336

This patch is merged into maintainer's tree
https://github.com/tiwai/sound/commit/a5c0c44b637e9cdc6b3c05aed2fbeb352df767d4

** Tags added: oem-priority originate-from-1909984 stella

** Tags added: originate-from-1909960

** Tags added: originate-from-1909983

** Changed in: oem-priority
 Assignee: (unassigned) => jeremyszu (os369510)

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

** Changed in: oem-priority
   Status: New => Triaged

** Description changed:

  [Impact]
- * Mute and micmute LED are not work accurately on HP ZBook Fury 15/17 G7
- Mobile Workstation when muting corresponding audio devices.
+ * Mute and micmute LED are not work accurately on HP ZBook Fury 15/17 G7 
Mobile Workstation when muting corresponding audio devices.
  * The right channel of internal speaker has not sound.
  
  [Fix]
- Apply ALC285_FIXUP_HP_GPIO_AMP_INIT quirk to expose GPIOs for controlling LEDs
- and initialing AMP.
+ Apply ALC285_FIXUP_HP_GPIO_AMP_INIT quirk to expose GPIOs for controlling 
LEDs and initialing AMP.
  
  [Test]
- Built a test kernel with applying this patch, the mute/micmute LEDs are work 
as
- expected. The internal speaker could play the sounds from left and right 
channels.
+ Built a test kernel with applying this patch, the mute/micmute LEDs are work 
as expected.
+ The internal speaker could play the sounds from left and right channels.
  
  [Where problems could occur]
- This quirk is specific for these two platforms. It should not cause the 
regression
- to other systems.
+ This quirk is specific for these two platforms. It should not cause the 
regression to other systems.

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

Title:
  Fix right sounds and mute/micmute LEDs for HP ZBook Fury 15/17 G7
  Mobile Workstation

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

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

[Bug 1910561] Re: Fix right sounds and mute/micmute LEDs for HP ZBook Fury 15/17 G7 Mobile Workstation

2021-01-07 Thread jeremyszu

I've no permission to change the bug affects/status.
Could someone help me to change it? thanks.

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

Title:
  Fix right sounds and mute/micmute LEDs for HP ZBook Fury 15/17 G7
  Mobile Workstation

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

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

[Bug 1910134] Please test proposed package

Hello Dimitri, or anyone else affected,

Accepted opensbi into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/opensbi/0.8-1ubuntu0.20.10.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: opensbi (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  Provide .bin files too

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

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

[Bug 1799550] Re: No way to encrypt at partition level (dual boot)

2021-01-07 Thread Brian Murray

** Tags removed: rls-hh-incoming
** Tags added: rls-hh-notfixing

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

Title:
  No way to encrypt at partition level (dual boot)

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

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

[Bug 1908050] Re: Support post install enablement of OEM-enabled devices

** Attachment added: "_usr_bin_update-manager.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1908050/+attachment/5450318/+files/_usr_bin_update-manager.1000.crash

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

Title:
  Support post install enablement of OEM-enabled devices

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

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

[Bug 1908050] Re: Support post install enablement of OEM-enabled devices

The system of Dell Inspiron 5391 is installed by the stock Ubuntu
20.04.1 ISO without any update but only with update-manager/1:20.04.10.2
and update-notifier/3.192.30.4 from focal-proposed.

It keeps crashing on Dell Inspiron 5391.

** Attachment added: "Screenshot from 2021-01-07 11-26-46.png"
   
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1908050/+attachment/5450317/+files/Screenshot%20from%202021-01-07%2011-26-46.png

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

Title:
  Support post install enablement of OEM-enabled devices

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

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

[Bug 1908050] Re: Support post install enablement of OEM-enabled devices

I am testing more.

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

Title:
  Support post install enablement of OEM-enabled devices

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

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

[Bug 1908050] Re: Support post install enablement of OEM-enabled devices

Dell Inspiron 5391 doesn't have the OEM metapackage.

** Attachment added: "Dell_Inspiron_5391.png"
   
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1908050/+attachment/5450316/+files/Dell_Inspiron_5391.png

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

Title:
  Support post install enablement of OEM-enabled devices

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

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

[Bug 1909789] Re: YouTube flickers when in full screen (RADEON)

2021-01-07 Thread Hark

Probably chromium-bug:
https://bugs.chromium.org/p/chromium/issues/detail?id=1140606

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

Title:
  YouTube flickers when in full screen (RADEON)

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

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

[Bug 1910562] Re: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34

2021-01-07 Thread munbi

Kernel 5.8 lsmod, lscpic, dmesg, sensors output

** Attachment added: "Kernel 5.8 lsmod, lscpic, dmesg, sensors output"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1910562/+attachment/5450315/+files/kern_5.8.txt

** Description changed:

- After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-3 
the fan on my
+ After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 
the fan on my
  machine started switching on (for an instant) and off every 10 seconds even
  when idle with CPU at 48/50°C.
  
  Switching back to previous kernel solves temporary the problem, i.e. fans are 
always off
  with light desktop work.
  
  The new behavior is really annoying and I guess not healthy for the
  fans.
  
  I'm on latest Dell bios, with every other package updated.
  
  Di something in the thermal policies change between those two kernels?
  Is it possible to go back to previous behavior ?
  
  Thanks in advance for help
  
  Machine: Dell Precison 7540, intel i7-9750
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  7 17:14:54 2021
  InstallationDate: Installed on 2020-05-06 (246 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

- After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 
the fan on my
- machine started switching on (for an instant) and off every 10 seconds even
- when idle with CPU at 48/50°C.
+ After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel
+ 5.8.0-34 the fan on my machine started switching on (for an instant) and
+ off every 10 seconds even when idle with CPU at 48/50°C.
  
- Switching back to previous kernel solves temporary the problem, i.e. fans are 
always off
- with light desktop work.
+ Switching back to previous kernel solves temporary the problem, i.e.
+ fans are always off with light desktop work.
  
  The new behavior is really annoying and I guess not healthy for the
  fans.
  
  I'm on latest Dell bios, with every other package updated.
  
  Di something in the thermal policies change between those two kernels?
  Is it possible to go back to previous behavior ?
  
  Thanks in advance for help
  
  Machine: Dell Precison 7540, intel i7-9750
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  7 17:14:54 2021
  InstallationDate: Installed on 2020-05-06 (246 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Fans switching on and off every 10 seconds after update to kernel
  5.8.0-34

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

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

[Bug 1910562] [NEW] Fans switching on and off every 10 seconds after update to kernel 5.8.0-34

2021-01-07 Thread munbi

Public bug reported:

After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel
5.8.0-34 the fan on my machine started switching on (for an instant) and
off every 10 seconds even when idle with CPU at 48/50°C.

Switching back to previous kernel solves temporary the problem, i.e.
fans are always off with light desktop work.

The new behavior is really annoying and I guess not healthy for the
fans.

I'm on latest Dell bios, with every other package updated.

Di something in the thermal policies change between those two kernels?
Is it possible to go back to previous behavior ?

Thanks in advance for help

Machine: Dell Precison 7540, intel i7-9750

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2
ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18
Uname: Linux 5.8.0-34-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan  7 17:14:54 2021
InstallationDate: Installed on 2020-05-06 (246 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: linux-signed-hwe-5.8
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dell fan focal thermal

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

Title:
  Fans switching on and off every 10 seconds after update to kernel
  5.8.0-34

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

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

[Bug 1910562] Re: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34

2021-01-07 Thread munbi

Kernel 5.4 lsmod, lscpic, dmesg, sensors output

** Attachment added: "Kernel 5.4 lsmod, lscpic, dmesg, sensors output"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1910562/+attachment/5450314/+files/kern_5.4.txt

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

Title:
  Fans switching on and off every 10 seconds after update to kernel
  5.8.0-34

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

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

[Bug 1909946] Re: Gnome Wayland session starts, then quits.

2021-01-07 Thread Stephen Allen

Damn doesn't seem to be a close or delete option. Daniel could you
please do the honours?

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

Title:
  Gnome Wayland session starts, then quits.

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

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

[Bug 1906612] 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 127

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

** Changed in: mysql-8.0 (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/1906612

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 127

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

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

[Bug 1905166] Re: systemd-shutdown cannot detach DM

2021-01-07 Thread j

Have the same problem, here is the log:

** Attachment added: "Log of systemd"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+attachment/5450309/+files/lp1905166.log

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

Title:
  systemd-shutdown cannot detach DM

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

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

[Bug 1910560] [NEW] autopkgtest fails in groovy in 2021

2021-01-07 Thread Balint Reczey

Public bug reported:

https://autopkgtest.ubuntu.com/packages/g/golang-github-
spf13-cobra/groovy/armhf

=== RUN   TestGoldenAddCmd
add_test.go:26: 
"/tmp/autopkgtest.bI0QyR/autopkgtest_tmp/obj-arm-linux-gnueabihf/src/github.com/spf13/cobra/cobra/cmd/testproject/cmd/test.go"
 and "testdata/test.go.golden" are not equal!

$ diff -u 
/tmp/autopkgtest.bI0QyR/autopkgtest_tmp/obj-arm-linux-gnueabihf/src/github.com/spf13/cobra/cobra/cmd/testproject/cmd/test.go
 testdata/test.go.golden
--- 
/tmp/autopkgtest.bI0QyR/autopkgtest_tmp/obj-arm-linux-gnueabihf/src/github.com/spf13/cobra/cobra/cmd/testproject/cmd/test.go
2021-01-06 14:50:42.535821792 +
+++ testdata/test.go.golden 2020-07-16 12:39:18.0 +
@@ -1,5 +1,5 @@
 /*
-Copyright © 2021 NAME HERE 
+Copyright © 2020 NAME HERE 
 
 Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.

exit status 1
--- FAIL: TestGoldenAddCmd (0.03s)

** Affects: golang-github-spf13-cobra (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: update-excuse

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

Title:
  autopkgtest fails in groovy in 2021

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-spf13-cobra/+bug/1910560/+subscriptions

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

[Bug 1910553] Re: [WIP] [MIR] python-certbot

2021-01-07 Thread Paride Legovini

** Description changed:

  [Availability]
  
  The package is in Ubuntu universe since Xenial and it's available on all
  the architectures (arch: all). The package is currently a sync from
  Debian.
  
  [Rationale]
  
  [Security]
  
  [Quality assurance]
  
  Upstream ships a pytest-based test suite which is run when building the 
Ubuntu package. The package also comes with an autopkgtest which tests certbot 
using pebble, a self-hosted version of the ACME server certbot uses to get the 
certificates. The autopkgtest pass reliably in both
  Debian [1] and Ubuntu [2]
  
  The package has a single debconf question which is asked at postrm time
  when purging the package. The questions regards the removal of unexpired
  certificates and it asked with high priority only if such certificates
  exist.
  
  There are no long-term outstanding bugs neither in Ubuntu nor in Debian.
  
  The package is maintained well maintained in Debian by an active team.
  The package is widely used and its popularity is growing.
  
  The package does not deal with specific hardware.
  The package does not rely on obsolete or about to be demoted packages.
  There are no lintian errors or warnings.
  
  d/watch is present
  
  [1] https://ci.debian.net/packages/p/python-certbot/testing/amd64/
  [2] https://autopkgtest.ubuntu.com/packages/python-certbot
  
  [UI standards]
  
  CLI application means for interactive and non-interactive use. Respects
  modern standards and conventions. The target audience are system
  administrators.
  
  [Dependencies]
  
  [Standards compliance]
  
  The package does meet the FHS and Debian Policy standards.
  
  [Maintenance]
  
+ The Server team will subscribe for the package for maintenance.
+ 
  [Background information]

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

Title:
  [WIP] [MIR] python-certbot

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

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

[Bug 1910561] [NEW] Fix right sounds and mute/micmute LEDs for HP ZBook Fury 15/17 G7 Mobile Workstation

2021-01-07 Thread jeremyszu

Public bug reported:

[Impact]
* Mute and micmute LED are not work accurately on HP ZBook Fury 15/17 G7
Mobile Workstation when muting corresponding audio devices.
* The right channel of internal speaker has not sound.

[Fix]
Apply ALC285_FIXUP_HP_GPIO_AMP_INIT quirk to expose GPIOs for controlling LEDs
and initialing AMP.

[Test]
Built a test kernel with applying this patch, the mute/micmute LEDs are work as
expected. The internal speaker could play the sounds from left and right 
channels.

[Where problems could occur]
This quirk is specific for these two platforms. It should not cause the 
regression
to other systems.

** Affects: linux-oem-5.10 (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/1910561

Title:
  Fix right sounds and mute/micmute LEDs for HP ZBook Fury 15/17 G7
  Mobile Workstation

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

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

[Bug 1878045] Re: doing dist-upgrade got error related do Broadcom

2021-01-07 Thread Angels Trias-i-Valls

I am also on 20.04.1 and my wifi connection has never worked. I have
BCM4312.

I tried all the steps above, but it did not work.

It can detect if I am on airplane mode, but it does not switch to wi-fi.
I have followed all the
https://ubuntuforums.org/showthread.php?t=2214110 previous threads too.

The Additional drivers, the Broadcom ones (device is not working). Using 
broadcom 802 does not allow me to select (I was able to select before between 
Broadcom, continue using manually, do not use device). At the moment it is set 
on 'do not use device' and it won't unselect from this option.
Waiting for 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/1878045

Title:
  doing dist-upgrade got error related do Broadcom

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

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

[Bug 1908717] Re: Black screen with blinking cursor

2021-01-07 Thread Luis Alberto Pabón

Thank you Daniel. I needed oibaf's updates to get ahold of Mesa <=20.2
and libgnvd <=1.3.2 in order to successfully compile wlroots and sway
from sources.

Now that hwe has come out with the updates I needed I ppa-purged oibaf,
but the issue remains.

I have re-opened this on
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1910559

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

Title:
  Black screen with blinking cursor

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

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

[Bug 1910559] Re: GDM3: Black screen with blinking cursor

2021-01-07 Thread Luis Alberto Pabón

I have temporarily switched to lightdm, which works fine.

Recording of the issue:

https://www.youtube.com/watch?v=6VaizT4uC8w=youtu.be

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

Title:
  GDM3: Black screen with blinking cursor

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

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

[Bug 1901797] Re: The upgrade to 20.10 is not taking place

2021-01-07 Thread pleabargain

I tried to upgrade via the UI
I click on upgrade. NOTHING happens in the UI.


here's the video
https://youtu.be/6VpA5nAeEEI

I tried to post the bug via
apport-bug software-center 

Then got this error:
ERROR: AttributeError("'NoneType' object has no attribute 'origins'")
The problem cannot be reported:
An error occurred while attempting to process this problem report:

'NoneType’ object has no attribute ‘origins’

Close

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

Title:
  The upgrade to 20.10 is not taking place

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

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

[Bug 1904406] Re: autopkgtest hangs in timedated test

This bug was fixed in the package systemd - 247.1-4ubuntu1

---
systemd (247.1-4ubuntu1) hirsute; urgency=medium

  [ Dan Streetman ]
  * d/p/lp1905044-test-use-cap_last_cap-for-max-supported-cap-number-n.patch:
Fix test use of new cap numbers with 5.8 kernel (LP: #1905044)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d55c6f8186cb2cb73f61d6ff5b2e0ded82ef265c

  [ Balint Reczey ]
  * Merge to Ubuntu from Debian unstable
  * Refresh patches
- Dropped changes:
  * debian/patches/dhcp-Allow-setting-request-options-again.patch
(Upstream code has been changed in a similar way)
  * 
debian/patches/Revert-network-do-not-drop-foreign-config-if-interface-is.patch

debian/patches/network-Set-link-state-to-LINK_STATE_PENDING-instead-of-t.patch
(Revert-network-prevent-interfaces-to-be-initialized-multi.patch is 
still kept)
  * 
debian/patches/lp1845909/0002-network-add-link-setting_genmode-flag.patch
  * d/p/lp1905044-test-use-cap_last_cap-for-max-supported-cap-number-n.patch
(Present in upstream 247.)
  * debian/udev.NEWS: Mention udev rules changes in 247
File: debian/udev.NEWS

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9f33f19683c2b864384c2ae59b312b2c844ed633
  * Don't start systemd-udev-trigger.service in containers.
It fails and is not likely to be useful.
File: 
debian/patches/units-Don-t-start-systemd-udev-trigger.service-in-a-conta.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7b04fe5f98a4d204f73a1ec22884b9b3053a9a82
  * test: use modern qemu numa arguments (LP: #1908259)
File: debian/patches/test-use-modern-qemu-numa-arguments.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=158106e74d452cf6cd5cd737432cbe6b7d47286c

systemd (247.1-4) unstable; urgency=medium

  [ наб ]
  * debian/extra/kernel-install.d/85-initrd.install: Don't install initrd when
an explicit path was passed (Closes: #970213)
  * debian/extra/kernel-install.d/85-initrd.install: Match initrd installation
messages and uninstallation to 90-loaderentry.install

  [ Michael Biebl ]
  * sd-device: keep escaped strings in DEVLINK= property (Closes: #976699)

systemd (247.1-3) unstable; urgency=medium

  * d/t/timedated: Ignore return code of dbus-monitor in wait_mon()
We are not really interested in the return code and error messages from
dbus-monitor after killing it, so ignore them to avoid undesired
autopkgtest failures.

systemd (247.1-2) unstable; urgency=medium

  [ Michael Biebl ]
  * Upload to unstable
  * Revert "d/t/timedated: use /bin/bash to work around job handling issue in
dash"

  [ Balint Reczey ]
  * debian/tests/timedated: Wait for the killed child only.
There may be other children of the script due to autopkgtest machinery
and they exit after the script exited. (LP: #1904406)

systemd (247.1-1) experimental; urgency=medium

  * New upstream version 247.1

systemd (247-1) experimental; urgency=medium

  * New upstream version 247
  * Rebase patches
  * Update symbol versions for the v247 release

systemd (247~rc2-3) experimental; urgency=medium

  * Merge changes from unstable
  * sd-device: make sd_device_has_current_tag() compatible with udev database
generated by older udevd
(Closes: #974730)
  * Add Breaks: udev (<< 247~) to systemd.
This ensures that udev is upgraded alongside systemd and both support
the new udev tags concept introduced in v247. (Closes: #975554)

systemd (247~rc2-2) experimental; urgency=medium

  * missing: define several syscall numbers for MIPS arch (Closes:
#974619)

systemd (247~rc2-1) experimental; urgency=medium

  [ Michael Biebl ]
  * New upstream version 247~rc2
- tmpfiles: Handle filesystems without ACL support in more cases
  (Closes: #972135)
  * Rebase patches
  * Explicitly disable oomd
  * Use -Dmode=release as we want a release, not developer, build
  * Update symbols file for libudev1 and libsystemd0

  [ Luca Boccassi ]
  * systemd-container: install systemd-dissect binary.
Required for TEST-50-DISSECT since:
https://github.com/systemd/systemd/pull/16046
  * d/t/control: install squashfs-tools for upstream test.
Required by TEST-50-DISSECT since upstream PR:
https://github.com/systemd/systemd/pull/16046

  [ Dan Streetman ]
  * d/control: update meson minimum version
https://github.com/systemd/systemd/pull/13842#issuecomment-601105975
  * d/t/upstream: convert 'blacklist' term to 'deny-list'
Support transition for upstream-ci from
https://github.com/systemd/systemd/pull/16262

 -- Balint Reczey   Wed, 16 Dec 2020 10:27:06 +0100

** Changed in: systemd (Ubuntu)
   Status: Invalid => 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/1904406

Title:
  autopkgtest

[Bug 1905044] Re: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8

This bug was fixed in the package systemd - 247.1-4ubuntu1

---
systemd (247.1-4ubuntu1) hirsute; urgency=medium

  [ Dan Streetman ]
  * d/p/lp1905044-test-use-cap_last_cap-for-max-supported-cap-number-n.patch:
Fix test use of new cap numbers with 5.8 kernel (LP: #1905044)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d55c6f8186cb2cb73f61d6ff5b2e0ded82ef265c

  [ Balint Reczey ]
  * Merge to Ubuntu from Debian unstable
  * Refresh patches
- Dropped changes:
  * debian/patches/dhcp-Allow-setting-request-options-again.patch
(Upstream code has been changed in a similar way)
  * 
debian/patches/Revert-network-do-not-drop-foreign-config-if-interface-is.patch

debian/patches/network-Set-link-state-to-LINK_STATE_PENDING-instead-of-t.patch
(Revert-network-prevent-interfaces-to-be-initialized-multi.patch is 
still kept)
  * 
debian/patches/lp1845909/0002-network-add-link-setting_genmode-flag.patch
  * d/p/lp1905044-test-use-cap_last_cap-for-max-supported-cap-number-n.patch
(Present in upstream 247.)
  * debian/udev.NEWS: Mention udev rules changes in 247
File: debian/udev.NEWS

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9f33f19683c2b864384c2ae59b312b2c844ed633
  * Don't start systemd-udev-trigger.service in containers.
It fails and is not likely to be useful.
File: 
debian/patches/units-Don-t-start-systemd-udev-trigger.service-in-a-conta.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7b04fe5f98a4d204f73a1ec22884b9b3053a9a82
  * test: use modern qemu numa arguments (LP: #1908259)
File: debian/patches/test-use-modern-qemu-numa-arguments.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=158106e74d452cf6cd5cd737432cbe6b7d47286c

systemd (247.1-4) unstable; urgency=medium

  [ наб ]
  * debian/extra/kernel-install.d/85-initrd.install: Don't install initrd when
an explicit path was passed (Closes: #970213)
  * debian/extra/kernel-install.d/85-initrd.install: Match initrd installation
messages and uninstallation to 90-loaderentry.install

  [ Michael Biebl ]
  * sd-device: keep escaped strings in DEVLINK= property (Closes: #976699)

systemd (247.1-3) unstable; urgency=medium

  * d/t/timedated: Ignore return code of dbus-monitor in wait_mon()
We are not really interested in the return code and error messages from
dbus-monitor after killing it, so ignore them to avoid undesired
autopkgtest failures.

systemd (247.1-2) unstable; urgency=medium

  [ Michael Biebl ]
  * Upload to unstable
  * Revert "d/t/timedated: use /bin/bash to work around job handling issue in
dash"

  [ Balint Reczey ]
  * debian/tests/timedated: Wait for the killed child only.
There may be other children of the script due to autopkgtest machinery
and they exit after the script exited. (LP: #1904406)

systemd (247.1-1) experimental; urgency=medium

  * New upstream version 247.1

systemd (247-1) experimental; urgency=medium

  * New upstream version 247
  * Rebase patches
  * Update symbol versions for the v247 release

systemd (247~rc2-3) experimental; urgency=medium

  * Merge changes from unstable
  * sd-device: make sd_device_has_current_tag() compatible with udev database
generated by older udevd
(Closes: #974730)
  * Add Breaks: udev (<< 247~) to systemd.
This ensures that udev is upgraded alongside systemd and both support
the new udev tags concept introduced in v247. (Closes: #975554)

systemd (247~rc2-2) experimental; urgency=medium

  * missing: define several syscall numbers for MIPS arch (Closes:
#974619)

systemd (247~rc2-1) experimental; urgency=medium

  [ Michael Biebl ]
  * New upstream version 247~rc2
- tmpfiles: Handle filesystems without ACL support in more cases
  (Closes: #972135)
  * Rebase patches
  * Explicitly disable oomd
  * Use -Dmode=release as we want a release, not developer, build
  * Update symbols file for libudev1 and libsystemd0

  [ Luca Boccassi ]
  * systemd-container: install systemd-dissect binary.
Required for TEST-50-DISSECT since:
https://github.com/systemd/systemd/pull/16046
  * d/t/control: install squashfs-tools for upstream test.
Required by TEST-50-DISSECT since upstream PR:
https://github.com/systemd/systemd/pull/16046

  [ Dan Streetman ]
  * d/control: update meson minimum version
https://github.com/systemd/systemd/pull/13842#issuecomment-601105975
  * d/t/upstream: convert 'blacklist' term to 'deny-list'
Support transition for upstream-ci from
https://github.com/systemd/systemd/pull/16262

 -- Balint Reczey   Wed, 16 Dec 2020 10:27:06 +0100

** Changed in: systemd (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/1905044

Title:

[Bug 1908050] Re: Support post install enablement of OEM-enabled devices

2021-01-07 Thread Julian Andres Klode

@fourdollars So, I guess you meant to set this as verification-done now,
or do you want to do more testing?

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

Title:
  Support post install enablement of OEM-enabled devices

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

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

[Bug 1908259] Re: TEST-36-NUMAPOLICY fails with qemu 5.2

This bug was fixed in the package systemd - 247.1-4ubuntu1

---
systemd (247.1-4ubuntu1) hirsute; urgency=medium

  [ Dan Streetman ]
  * d/p/lp1905044-test-use-cap_last_cap-for-max-supported-cap-number-n.patch:
Fix test use of new cap numbers with 5.8 kernel (LP: #1905044)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d55c6f8186cb2cb73f61d6ff5b2e0ded82ef265c

  [ Balint Reczey ]
  * Merge to Ubuntu from Debian unstable
  * Refresh patches
- Dropped changes:
  * debian/patches/dhcp-Allow-setting-request-options-again.patch
(Upstream code has been changed in a similar way)
  * 
debian/patches/Revert-network-do-not-drop-foreign-config-if-interface-is.patch

debian/patches/network-Set-link-state-to-LINK_STATE_PENDING-instead-of-t.patch
(Revert-network-prevent-interfaces-to-be-initialized-multi.patch is 
still kept)
  * 
debian/patches/lp1845909/0002-network-add-link-setting_genmode-flag.patch
  * d/p/lp1905044-test-use-cap_last_cap-for-max-supported-cap-number-n.patch
(Present in upstream 247.)
  * debian/udev.NEWS: Mention udev rules changes in 247
File: debian/udev.NEWS

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9f33f19683c2b864384c2ae59b312b2c844ed633
  * Don't start systemd-udev-trigger.service in containers.
It fails and is not likely to be useful.
File: 
debian/patches/units-Don-t-start-systemd-udev-trigger.service-in-a-conta.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7b04fe5f98a4d204f73a1ec22884b9b3053a9a82
  * test: use modern qemu numa arguments (LP: #1908259)
File: debian/patches/test-use-modern-qemu-numa-arguments.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=158106e74d452cf6cd5cd737432cbe6b7d47286c

systemd (247.1-4) unstable; urgency=medium

  [ наб ]
  * debian/extra/kernel-install.d/85-initrd.install: Don't install initrd when
an explicit path was passed (Closes: #970213)
  * debian/extra/kernel-install.d/85-initrd.install: Match initrd installation
messages and uninstallation to 90-loaderentry.install

  [ Michael Biebl ]
  * sd-device: keep escaped strings in DEVLINK= property (Closes: #976699)

systemd (247.1-3) unstable; urgency=medium

  * d/t/timedated: Ignore return code of dbus-monitor in wait_mon()
We are not really interested in the return code and error messages from
dbus-monitor after killing it, so ignore them to avoid undesired
autopkgtest failures.

systemd (247.1-2) unstable; urgency=medium

  [ Michael Biebl ]
  * Upload to unstable
  * Revert "d/t/timedated: use /bin/bash to work around job handling issue in
dash"

  [ Balint Reczey ]
  * debian/tests/timedated: Wait for the killed child only.
There may be other children of the script due to autopkgtest machinery
and they exit after the script exited. (LP: #1904406)

systemd (247.1-1) experimental; urgency=medium

  * New upstream version 247.1

systemd (247-1) experimental; urgency=medium

  * New upstream version 247
  * Rebase patches
  * Update symbol versions for the v247 release

systemd (247~rc2-3) experimental; urgency=medium

  * Merge changes from unstable
  * sd-device: make sd_device_has_current_tag() compatible with udev database
generated by older udevd
(Closes: #974730)
  * Add Breaks: udev (<< 247~) to systemd.
This ensures that udev is upgraded alongside systemd and both support
the new udev tags concept introduced in v247. (Closes: #975554)

systemd (247~rc2-2) experimental; urgency=medium

  * missing: define several syscall numbers for MIPS arch (Closes:
#974619)

systemd (247~rc2-1) experimental; urgency=medium

  [ Michael Biebl ]
  * New upstream version 247~rc2
- tmpfiles: Handle filesystems without ACL support in more cases
  (Closes: #972135)
  * Rebase patches
  * Explicitly disable oomd
  * Use -Dmode=release as we want a release, not developer, build
  * Update symbols file for libudev1 and libsystemd0

  [ Luca Boccassi ]
  * systemd-container: install systemd-dissect binary.
Required for TEST-50-DISSECT since:
https://github.com/systemd/systemd/pull/16046
  * d/t/control: install squashfs-tools for upstream test.
Required by TEST-50-DISSECT since upstream PR:
https://github.com/systemd/systemd/pull/16046

  [ Dan Streetman ]
  * d/control: update meson minimum version
https://github.com/systemd/systemd/pull/13842#issuecomment-601105975
  * d/t/upstream: convert 'blacklist' term to 'deny-list'
Support transition for upstream-ci from
https://github.com/systemd/systemd/pull/16262

 -- Balint Reczey   Wed, 16 Dec 2020 10:27:06 +0100

** Changed in: systemd (Ubuntu)
   Status: In Progress => 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/1908259

Title:

[Bug 1910557] [NEW] Buildd images do not launch on macOS under multipass due to missing unpacked kernels and initrd

2021-01-07 Thread David Krauser

Public bug reported:

livecd-rootfs v2.700 in hirsute introduced a fix to produce unpacked
artifacts for use by multipass on macOS hosts. These hosts require
direct access to a kernel and initrd to boot the buildd images.

See: https://git.launchpad.net/livecd-
rootfs/commit/?id=065c82314464fa78337d5122e1d4826a7d6edbb0

This change needs to be backported to all suites.

[Impact]

 * Without this change, users are unable to use the buildd images with
multipass on macOS hosts. Snapcraft utilizes multipass to build snaps,
so this blocks macOS users from building snaps.

As a workaround, the CPC team is manually extracting these artifacts and
publishing them to cloud-images.ubuntu.com. This is not ideal for the
long-term, and could result in breakage in the event that the CPC team
forgets to manually publish these artifacts.

[Test Case]

 * After this change lands, a user should be able to build images with
the ubuntu-base project and buildd subproject, and the resulting build
should produce extracted kernel and initrd artifacts.

[Where problems could occur]

 * These changes are minor, but a mistake could result in broken buildd image 
hooks (where the build fails) or broken buildd image artifacts (where the 
images don't work as expected).
* Since all buildd images are manually tested by the launchpad team, multipass 
team, and snapcraft team before they enter production, the risk of introducing 
breakage for end users is low.

** Affects: livecd-rootfs (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/1910557

Title:
  Buildd images do not launch on macOS under multipass due to missing
  unpacked kernels and initrd

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

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

[Bug 1910559] [NEW] GDM3: Black screen with blinking cursor

2021-01-07 Thread Luis Alberto Pabón

Public bug reported:

About a month ago, GDM ceased to work. I opened another issue here
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1908717 but due to
me using oibaf's ppa it was considered prudent to discard that issue and
re-open after I removed the ppa and restored Ubuntu's dist packages.

Upon boot, gdm goes to a black screen with a cursor. This screen
flickers to show the underlying tty and on each flicker the cursor
position resets to the bottom right. It will do this a number of times
until GDM dies and I'm left on a tty.

I can start my window manager (sway) without issue from the console
still and everything functions normally.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.36.3-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
Uname: Linux 5.4.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: sway
Date: Thu Jan  7 15:55:43 2021
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  GDM3: Black screen with blinking cursor

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

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

[Bug 1909946] Re: Gnome Wayland session starts, then quits.

2021-01-07 Thread Stephen Allen

Daniel I was pretty sure that the problem existed in my home directory. So, 
rather than go through all the gnome gnome settings one by one, with subsequent 
reboots, I cleaned out my home directory of all gnome specific settings at once 
this am, and rebooted and problem is gone - I'm now in XWayland.
 
This would have taken a long time to troubleshoot, so I took the quick route it 
was a Fool's errand to try to figure out which setting was creating the 
problem, because I have backed up my home directory for over 10 years 
continuously, and I had a lot of cruft in there, so it was time to clean it 
out.I'm going to close this bug now, thanks for all your help Daniel I didn't 
want to waste any more of your time. Cheers.

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

Title:
  Gnome Wayland session starts, then quits.

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

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

[Bug 1896119] Re: Catting the SecureBoot efivar in /sys hangs

2021-01-07 Thread Jeff Lane

** Summary changed:

- secure boot test locks machine up
+ Catting the SecureBoot efivar in /sys hangs

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

Title:
  Catting the SecureBoot efivar in /sys hangs

To manage notifications about this bug go to:
https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1896119/+subscriptions

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

[Bug 1908050] Re: Support post install enablement of OEM-enabled devices

** Attachment added: "Dell_XPS_13_9300.png"
   
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1908050/+attachment/5450295/+files/Dell_XPS_13_9300.png

** Attachment removed: "update-manager.png"
   
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1908050/+attachment/5450090/+files/update-manager.png

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

Title:
  Support post install enablement of OEM-enabled devices

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

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

Re: [Bug 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"

And, for clarity, when systemd does hibernate, I haven't had issues
restoring: it's just getting systemd to find the correct swap space to
use that's been the issue.

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

Title:
  `systemctl hibernate` incorrectly reports "Not enough swap space for
  hibernation"

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

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

Re: [Bug 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"

On Thu, Jan 07, 2021 at 03:23:36PM -, Dimitri John Ledkov wrote:
> Also, you do disable secureboot as well right? Because with secureboot
> on, even though hybernation image is created, it will be ignored and
> not used upon resume.

Yep, Secure Boot is disabled on this system.

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

Title:
  `systemctl hibernate` incorrectly reports "Not enough swap space for
  hibernation"

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

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

[Bug 1910553] Re: [WIP] [MIR] python-certbot

2021-01-07 Thread Paride Legovini

** Description changed:

  [Availability]
  
  The package is in Ubuntu universe since Xenial and it's available on all
  the architectures (arch: all). The package is currently a sync from
  Debian.
  
  [Rationale]
  
  [Security]
  
  [Quality assurance]
  
+ Upstream ships a pytest-based test suite which is run when building the 
Ubuntu package. The package also comes with an autopkgtest which tests certbot 
using pebble, a self-hosted version of the ACME server certbot uses to get the 
certificates. The autopkgtest pass reliably in both
+ Debian [1] and Ubuntu [2]
+ 
+ The package has a single debconf question which is asked at postrm time
+ when purging the package. The questions regards the removal of unexpired
+ certificates and it asked with high priority only if such certificates
+ exist.
+ 
+ There are no long-term outstanding bugs neither in Ubuntu nor in Debian.
+ 
+ The package is maintained well maintained in Debian by an active team.
+ The package is widely used and its popularity is growing.
+ 
+ The package does not deal with specific hardware.
+ The package does not rely on obsolete or about to be demoted packages.
+ There are no lintian errors or warnings.
+ 
+ d/watch is present
+ 
+ [1] https://ci.debian.net/packages/p/python-certbot/testing/amd64/
+ [2] https://autopkgtest.ubuntu.com/packages/python-certbot
+ 
  [Dependencies]
  
  [Standards compliance]
  
  [Maintenance]
  
  [Background information]

** Description changed:

  [Availability]
  
  The package is in Ubuntu universe since Xenial and it's available on all
  the architectures (arch: all). The package is currently a sync from
  Debian.
  
  [Rationale]
  
  [Security]
  
  [Quality assurance]
  
  Upstream ships a pytest-based test suite which is run when building the 
Ubuntu package. The package also comes with an autopkgtest which tests certbot 
using pebble, a self-hosted version of the ACME server certbot uses to get the 
certificates. The autopkgtest pass reliably in both
  Debian [1] and Ubuntu [2]
  
  The package has a single debconf question which is asked at postrm time
  when purging the package. The questions regards the removal of unexpired
  certificates and it asked with high priority only if such certificates
  exist.
  
  There are no long-term outstanding bugs neither in Ubuntu nor in Debian.
  
  The package is maintained well maintained in Debian by an active team.
  The package is widely used and its popularity is growing.
  
  The package does not deal with specific hardware.
  The package does not rely on obsolete or about to be demoted packages.
  There are no lintian errors or warnings.
  
  d/watch is present
  
  [1] https://ci.debian.net/packages/p/python-certbot/testing/amd64/
  [2] https://autopkgtest.ubuntu.com/packages/python-certbot
  
+ [UI standards]
+ 
+ CLI application means for interactive and non-interactive use. Respects
+ modern standards and conventions.
+ 
  [Dependencies]
  
  [Standards compliance]
  
  [Maintenance]
  
  [Background information]

** Description changed:

  [Availability]
  
  The package is in Ubuntu universe since Xenial and it's available on all
  the architectures (arch: all). The package is currently a sync from
  Debian.
  
  [Rationale]
  
  [Security]
  
  [Quality assurance]
  
  Upstream ships a pytest-based test suite which is run when building the 
Ubuntu package. The package also comes with an autopkgtest which tests certbot 
using pebble, a self-hosted version of the ACME server certbot uses to get the 
certificates. The autopkgtest pass reliably in both
  Debian [1] and Ubuntu [2]
  
  The package has a single debconf question which is asked at postrm time
  when purging the package. The questions regards the removal of unexpired
  certificates and it asked with high priority only if such certificates
  exist.
  
  There are no long-term outstanding bugs neither in Ubuntu nor in Debian.
  
  The package is maintained well maintained in Debian by an active team.
  The package is widely used and its popularity is growing.
  
  The package does not deal with specific hardware.
  The package does not rely on obsolete or about to be demoted packages.
  There are no lintian errors or warnings.
  
  d/watch is present
  
  [1] https://ci.debian.net/packages/p/python-certbot/testing/amd64/
  [2] https://autopkgtest.ubuntu.com/packages/python-certbot
  
  [UI standards]
  
  CLI application means for interactive and non-interactive use. Respects
- modern standards and conventions.
+ modern standards and conventions. The target audience are system
+ administrators.
  
  [Dependencies]
  
  [Standards compliance]
  
+ The package does meet the FHS and Debian Policy standards.
+ 
  [Maintenance]
  
  [Background information]

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

Title:
  [WIP] [MIR] python-certbot

To manage notifications about this bug go

[Bug 1910556] [NEW] update-manager is hanging after clicking on "install updates"

2021-01-07 Thread Bigbiz

Public bug reported:

This after launching update-manager in a terminal's window:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/UpdateManager/Dialogs.py", line 118, in 

button.connect("clicked", lambda x: callback())
  File "/usr/lib/python3/dist-packages/UpdateManager/UpdatesAvailable.py", line 
880, in on_button_install_clicked
self.window_main.start_install()
  File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line 
234, in start_install
self._start_pane(install_backend)
  File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line 
174, in _start_pane
pane.start()
  File "/usr/lib/python3/dist-packages/UpdateManager/backend/__init__.py", line 
61, in start
self.commit_oem(pkgs_install_oem, pkgs_upgrade_oem)
UnboundLocalError: local variable 'pkgs_install_oem' referenced before 
assignment

I tried with sudo but nothing to do.

I've the same problem on 3 systems.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: update-manager 1:20.04.10.2
ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
Uname: Linux 5.4.0-59-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan  7 16:30:48 2021
ExecutablePath: /usr/bin/update-manager
InstallationDate: Installed on 2019-04-13 (635 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
InterpreterPath: /usr/bin/python3.8
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
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
SourcePackage: update-manager
UpgradeStatus: Upgraded to focal on 2020-12-29 (8 days ago)

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


** Tags: amd64 apport-bug focal package-from-proposed

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

Title:
  update-manager is hanging after clicking on "install updates"

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

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

[Bug 1910555] [NEW] Driver build error on kernel 5.8, but works on 5.4

2021-01-07 Thread ZdravkoG

Public bug reported:

Recently kernel was updated on Focal from 5.4 to 5.8. From that moment on WiFi 
doesn't work anymore. After a try rebuild (reconfigure) the result is:
---
# dpkg-reconfigure bcmwl-kernel-source
Removing all DKMS Modules
Done.
Loading new bcmwl-6.30.223.271+bdcom DKMS files...
Building for 5.4.0-59-generic 5.8.0-34-generic
Building for architecture x86_64
Building initial module for 5.4.0-59-generic
Done.

wl.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.4.0-59-generic/updates/dkms/

depmod

DKMS: install completed.
Building initial module for 5.8.0-34-generic
ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/bcmwl-kernel-source.0.crash'
Error! Bad return status for module build on kernel: 5.8.0-34-generic (x86_64)
Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more 
information.
---
As could be seen, the build for 5.4 completes successfully (and works on same 
kernel), but for 5.8 fails. Seems something is going wrong with missing 
function declaration - function "ioremap_nocache", as could be seen in attached 
make.log.
I'm guessing, driver code may need be updated according to the new kernel 
headers.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
Uname: Linux 5.4.0-59-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Thu Jan  7 17:13:05 2021
InstallationDate: Installed on 2020-06-22 (198 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: bcmwl
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Log for driver build on kernel 5.8"
   https://bugs.launchpad.net/bugs/1910555/+attachment/5450291/+files/make.log

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

Title:
  Driver build error on kernel 5.8, but works on 5.4

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

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

[Bug 1896119] Missing required logs.

2021-01-07 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 1896119

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

Title:
  Catting the SecureBoot efivar in /sys hangs

To manage notifications about this bug go to:
https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1896119/+subscriptions

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

[Bug 1896119] Re: secure boot test locks machine up

2021-01-07 Thread Jeff Lane

At this point, this is not a problem I can fix.  It's very much tied to
their hardware, and to the kernel on that hardware.  This is the only
instance of this I have ever seen, anywhere, over literally thousands of
test runs, and it is very easily reproduced manually by simply catting
the efi variable for SecureBoot, so it exists outside the test suite.

I've added a kernel task, if there's any fix to be had here, it would
have to occur there.

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

** Changed in: plainbox-provider-checkbox
   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/1896119

Title:
  Catting the SecureBoot efivar in /sys hangs

To manage notifications about this bug go to:
https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1896119/+subscriptions

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

[Bug 1908761] Re: Can't deploy using root XFS partition using 18.04

2021-01-07 Thread Eric Desrochers

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

I have started the SRU.

For more details about the SRU, please refer to bug #1652822.

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

Title:
  Can't deploy using root XFS partition using 18.04

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

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

[Bug 1908099] Re: nvidia-dkms-390 fails to build on unstable / 5.10

2021-01-07 Thread Andrea Righi

New debdiff that prevents building UVM w/ Linux 5.10 (thanks
@albertomilone) and with a refreshed version of
buildfix_kernel_5.10.patch that should prevent a potential memory leak
due to the missing .gem_free_object in 5.10.

** Patch added: "hirsute-nvidia-dkms-390.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1908099/+attachment/5450289/+files/hirsute-nvidia-dkms-390.debdiff

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

Title:
  nvidia-dkms-390 fails to build on unstable / 5.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1908099/+subscriptions

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

[Bug 1908099] Re: nvidia-dkms-390 fails to build on unstable / 5.10

2021-01-07 Thread Andrea Righi

Sorry, I posted the wrong file in comment #3, this is the right one.

** Patch added: "hirsute-nvidia-dkms-390-v2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1908099/+attachment/5450290/+files/hirsute-nvidia-dkms-390-v2.debdiff

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

Title:
  nvidia-dkms-390 fails to build on unstable / 5.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1908099/+subscriptions

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

[Bug 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"

2021-01-07 Thread Dimitri John Ledkov

these things are very weird indeed.


Also, you do disable secureboot as well right? Because with secureboot on, even 
though hybernation image is created, it will be ignored and not used upon 
resume.

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

Title:
  `systemctl hibernate` incorrectly reports "Not enough swap space for
  hibernation"

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

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

[Bug 1910262] Re: [MIR] libbackuppc-xs-perl

2021-01-07 Thread Christian Ehrhardt 

[Summary]
MIR team Ack, it is a small reasonable package without too much attack
surface nor any obvious flaws.

List of specific binary packages to be promoted to main: libbackuppc-xs-
perl

[Duplication]
There is no other package in main providing the same functionality.

[Dependencies]
OK:
- no other Dependencies to MIR due to this
- no -dev/-debug/-doc packages that need exclusion

[Embedded sources and static linking]
OK:
- no static linking

Problems:
- embedded source zlib is ok (present, but patched out and not used)
- embedded source md5 is ok (this one is used, but it is from rsync which
  does not provide it as a reusable library). While there would be options
  from libbsd and libssl I think there are so many custom md5's out there,
  just many don't state it as external code - that I think this isn't a
  blocker)
  I filed https://github.com/backuppc/backuppc-xs/issues/7 for it

[Security]
OK:
- history of CVEs does not look concerning
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not parse data formats
- does not open a port
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)

[Common blockers]
OK:
- does not FTBFS currently
- does have a test suite that runs at build time (trivial test but yes)
  - test suite fails will fail the build upon error.
- does have a test suite that runs as autopkgtest
- The package has a team bug subscriber
- no translation present, but none needed for this case (user visible)?
- not a python/go package, no extra constraints to consider int hat regard
- no new python2 dependency

[Packaging red flags]
OK:
- Ubuntu does not carry a delta
- symbols tracking not applicable for this kind of code.
- d/watch is present and looks ok
- Upstream update history is good
- Debian update history is good
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
  maintained the package
- no massive Lintian warnings
- d/rules is rather clean
- Does not have Built-Using

[Upstream red flags]
OK:
- no Errors/warnings during the build (some minimal warnings due to the
  new compiler for Wformat-truncation, but nothing severe)
  => https://github.com/backuppc/backuppc-xs/issues/6
- no incautious use of malloc/sprintf (as far as I can check it)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH
- no use of user nobody
- no use of setuid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- not part of the UI for extra checks


** Bug watch added: github.com/backuppc/backuppc-xs/issues #7
   https://github.com/backuppc/backuppc-xs/issues/7

** Bug watch added: github.com/backuppc/backuppc-xs/issues #6
   https://github.com/backuppc/backuppc-xs/issues/6

** Changed in: libbackuppc-xs-perl (Ubuntu)
   Status: New => In Progress

** Changed in: libbackuppc-xs-perl (Ubuntu)
 Assignee: Christian Ehrhardt  (paelzer) => (unassigned)

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

Title:
  [MIR] libbackuppc-xs-perl

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

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

[Bug 1910264] Re: [plugin][ceph] include time-sync-status for ceph mon

2021-01-07 Thread Eric Desrochers

There is currently an SRU for sosreport started by mfo.
I'll have to wait for it to end.

I'll take a note to revisit this bug sponsoring in 1 week.


- Eric

** Tags added: sts-sponsors-slashd

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

Title:
  [plugin][ceph] include time-sync-status for ceph mon

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

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

[Bug 1910544] Re: Bash search history vi-mode hang the process

2021-01-07 Thread Joakim Kasimir

I think I solved by removing the .bash_history file.

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

Title:
  Bash search history vi-mode hang the process

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

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

[Bug 1906496] Re: [SRU] mgr can be very slow in a large ceph cluster

2021-01-07 Thread Ponnuvel Palaniyappan

** Description changed:

[Impact]
Ceph upstream implemented a new feature [1] that will check/report those long
network ping times between OSDs, but it introduced an issue that ceph-mgr might
be very slow because it needs to dump all the new OSD network ping stats [2]
for some tasks, this can be bad especially when the cluster has large number of
OSDs.

Since these kind OSD network ping stats doesn't need to be exposed to
- the python mgr module. so, it only makes the mgr doing more work than it
+ the python mgr module. So, it only makes the mgr doing more work than it
needs to, it could cause the mgr slow or even hang and could cause the
CPU usage of mgr process constantly high. The fix is to disable the ping
time dump for those mgr python modules.

This resulted in ceph-mgr not responding to commands and/or hanging (and
- had to be restarted) in clusters with a large number of OSDs.
+ had to be restarted) in clusters with many OSDs.

[0] is the upstream bug. It was backported to Nautilus but rejected for
Luminous and Mimic because they reached EOL in upstream. But I want to
backport to these two releases Ubuntu/UCA.

The major fix from upstream is here [3], and also I found an improvement
commit [4] that submitted later in another PR.

[Test Case]
Deploy a Ceph cluster (Luminous 13.2.9 or Mimic 13.2.9) with large number of
Ceph OSDs (600+). During normal operations of the cluster, as the ceph-mgr
dumps the network ping stats regularly, this problem would manifest. This is
relatively hard to reproduce as the ceph-mgr may not always get overloaded and
thus not hang.

A simpler version could be to deploy a Ceph cluster with as many OSDs as
the hardware/system setup allows (not necessarily 600+) and drive I/O on
the cluster for sometime (say, 60 mins). Then various queries could be
sent to the manager to verify it does report and doesn't get stuck.

[Regression Potential]
Fix has been accepted upstream (the changes are here in "sync" with upstream
to the extent these old releases match the latest source code) and have been
confirmed to work. So the risk is minimal.

At worst, this could affect modules that consume the stats from ceph-mgr
(such as prometheus or other monitoring scripts/tools) and thus becomes
less useful. But still shouldn't cause any problems to the operations of
the cluster itself.

[Other Info]
- In addition to the fix from [1], another commit [4] is also cherry-picked
and backported here - this was also accepted upstream.

- Since the ceph-mgr hangs when affected, this also impact sosreport
collection - commands time out as the mgr doesn't respond and thus info
get truncated/not collected in that case. This fix should help avoid
that problem in sosreports.

[0] https://tracker.ceph.com/issues/43364
[1] https://github.com/ceph/ceph/pull/28755
[2]
https://github.com/ceph/ceph/pull/28755/files#diff-5498d83111f1210998ee186e98d5836d2bce9992be7648addc83f59e798cddd8L430
[3] https://github.com/ceph/ceph/pull/32406
[4]
https://github.com/ceph/ceph/pull/32554/commits/1112584621016c4a8cac1bedb1a1b8b17c394f7f

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

Title:
[SRU] mgr can be very slow in a large ceph cluster

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

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

[Bug 1909012] Re: my display are disappeared with I used libreoffice or other software

2021-01-07 Thread Michele N

As you can see from the attached photo, the central screen suddenly blackens 
when I hover while I was working on a word processor. The problem could be a 
conflict between opening shotwell program in the background, as could very well 
happen with other programs that still require cpu resources. I ask to have some 
answers and to be able to know if doing the upgrade of the ubuntu version, 
always in LTS, can solve some bugs.
I ask for an answer to updates as well and also to the fact that I have to keep 
restarting my computer to fix these bugs.
Thanks

** Attachment added: "IMG_20201222_123937.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1909012/+attachment/5450285/+files/IMG_20201222_123937.jpg

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

Title:
  my display are disappeared with I used libreoffice or other software

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

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

[Bug 1826737] Re: lshw does not list NVMe storage devices as "disk" nodes

2021-01-07 Thread Eric Desrochers

[sts-sponsors[hirsute]

In the absence of a reply from Debian, I have sponsored the patchset in
Hirsute.

My preference would have been to have a version bump but nevertheless,
the request to bump the version is still opened, and it's not too late
for us to sync with Debian once done if this still fit with the current
Hirsute freeze schedule: (or worse case scenario for next active devel
release)

https://discourse.ubuntu.com/t/hirsute-hippo-release-schedule/18539

- Eric

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

Title:
  lshw does not list NVMe storage devices as "disk" nodes

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

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

[Bug 1900668] Re: MAAS PXE Boot stalls with grub 2.02

2021-01-07 Thread Junien Fridrick

@xnox as far as I know, the Foundations team still has access to the
test hardware, if you want to test this new grub.

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

Title:
  MAAS PXE Boot stalls with grub 2.02

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/1900668/+subscriptions

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

[Bug 1909879] Re: taskwarrior-2.5.2 is out

2021-01-07 Thread Hans Joachim Desserud

You're welcome :)

I agree this can be closed, espically now that 2.5.3 has been
successfully synced to Hirsute
https://bugs.launchpad.net/ubuntu/+source/task/2.5.3+dfsg-1

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

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

Title:
  taskwarrior-2.5.2 is out

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

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

[Bug 1910554] [NEW] Freezes randomly and buttons/mouse don't work. Have to shut down by long pressing the power button

2021-01-07 Thread Mohan Kumar

Public bug reported:

Freezes randomly and buttons/mouse don't work. Have to shut down by long
pressing the power button. Don't particularly know what is causing it.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
Uname: Linux 5.8.0-34-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan  7 20:30:20 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
InstallationDate: Installed on 2021-01-06 (1 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: ubiquity
Symptom: installation
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy ubiquity-20.10.13

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

Title:
  Freezes randomly and buttons/mouse don't work. Have to shut down by
  long pressing the power button

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

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

[Bug 1910553] [NEW] [WIP] [MIR] python-certbot

2021-01-07 Thread Paride Legovini

Public bug reported:

[Availability]

The package is in Ubuntu universe since Xenial and it's available on all
the architectures (arch: all). The package is currently a sync from
Debian.

[Rationale]

[Security]

[Quality assurance]

[Dependencies]

[Standards compliance]

[Maintenance]

[Background information]

** Affects: python-certbot (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/1910553

Title:
  [WIP] [MIR] python-certbot

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

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

[Bug 1652822] Re: grub efi doesn't install fs module needed to access root

Hello Jeremiah, or anyone else affected,

Accepted grub2 into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/grub2/2.02-2ubuntu8.21
in a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: grub2 (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

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

Title:
  grub efi doesn't install fs module needed to access root

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

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

[Bug 1900401] Re: Ryzen 1800X soft lockups

2021-01-07 Thread ed20900

I tried "pcie_aspm=off nvme_core.default_ps_max_latency_us=0" but did
not help. I'll try with "force" and "performance" policy.

I ended fed up with crashes and upgraded to a Ryzen 7 2700X, with the
rest of the system unchanged. It still crashes from time to time, but it
takes much more time. Instead of 48h of uptime it can last weeks.

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

Title:
  Ryzen 1800X soft lockups

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

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

[Bug 1908509] Re: [SRU] Update to netplan.io 0.101

2021-01-07 Thread Lukas Märdian

netplan.io 0.101-0ubuntu3~20.10.1 passed the full test suite on Groovy.

** Description changed:

  [Impact]
  This release contains both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these improvements.
  
  The most notable changes (besides usual bug-fixes) incoming in 0.101-0ubuntu3:
  - Implementation of DBus Config/Get/Set/Try APIs
  - Compatibility with systemd v247
  - Documentation improvements
  - Improved integration tests
  - Improve test stability
  - Add more examples for Wireguard, Open vSwitch, DBus
  - Add per-route MTU option (LP: #1860201)
  
  See the changelog entry below for a full list of changes and bugs.
  
  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NetplanUpdates
  
  Netplan contains an extensive integration test suite that is ran using
  the SRU package for each releases. This test suite's results are available 
here:
  http://autopkgtest.ubuntu.com/packages/n/netplan.io
  
  A successful run is required before the proposed netplan package
  can be let into -updates.
  
  The netplan team will be in charge of attaching the artifacts and console
  output of the appropriate run to the bug. Netplan team members will not
  mark ‘verification-done’ until this has happened.
  
  [Where problems could occur]
  In order to mitigate the regression potential, the results of the
  aforementioned integration tests are attached to this bug.
  
  Groovy:
- groovy_amd64_log
- groovy_arm64_log
- groovy_armhf_log
- groovy_ppc64el_log
- groovy_s390x_log
+ https://git.launchpad.net/~slyon/+git/files/tree/LP1908509/groovy_amd64_log
+ https://git.launchpad.net/~slyon/+git/files/tree/LP1908509/groovy_arm64_log
+ https://git.launchpad.net/~slyon/+git/files/tree/LP1908509/groovy_armhf_log
+ https://git.launchpad.net/~slyon/+git/files/tree/LP1908509/groovy_ppc64el_log
+ https://git.launchpad.net/~slyon/+git/files/tree/LP1908509/groovy_s390x_log
  
  Focal:
  focal_amd64_log
  focal_arm64_log
  focal_armhf_log
  focal_ppc64el_log
  focal_s390x_log
  
  [Changelog]
  41bfbd6 parse: fix 'networkmanager:' backend options for modem connections 
(#179)
  85ff2f5 Fix changing of macaddress with systemd v247 (#178)
  e445b87 Fix rename of matched interfaces at runtime (LP: #1904662) (#174)
  fad12c1 Fix is_ovs_interface method in cli/ovs.py (LP: #1904633) (LP: 
#1905156) (#172)
  40aef1b Documentation for get/set CLI and DBus 
Config/Try/Cancel/Apply/Get/Set (#173)
  6eafac5 DBus Config Management (try-improvement) (#170)
  0275cc0 test:integration: add link-local tests
  5b9ee56 Implement DBus try-commit handling (#134)
  097d875 Add per-route MTU option (LP: #1860201) (#160)
  4efd4e7 doc: Fix Wireguard formatting
  068a2b5 doc: Add note about default gateway4/6 usage
  83c1c1c Do not try to match/rename duplicated MAC of vlan (LP: #1888726) 
(#166)
  449957e Update README badges (#168)
  fdcb3d4 Use Github Actions for unit tests and Codecov upload (#167)
  71b64ce Fix MAAS/OVS first boot for single NIC/PXE systems (#165)
  b1000bc cli:utils: fix libnetplan loading
  05780d1 tests:ovs: fix OVS timeouts
  5bef614 tests:tunnels: improve WG handshake regex
  a1497d1 Implement netplan get/set CLI and DBus API (#163)
  b8286ce Remove version information from the description of the info flag 
(#164)
  19726c7 .github: update PR template checklist, to not forgett about examples
  00822cd tests: remove 'cloud-init' reboot test, was migrated to 
debian/tests/cloud-init script
  72af970 examples: add wireguard.yaml example
  4a0e7a9 examples: add openvswitch.yaml example
  6b3ac28 Implement just-in-time behaviour for generate (#162)

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

Title:
  [SRU] Update to netplan.io 0.101

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

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

[Bug 1910538] Re: Cannot set scale of screen

2021-01-07 Thread Hans Joachim Desserud

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

** This bug has been marked a duplicate of bug 1910539
   Cannot set scale of screen

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

Title:
  Cannot set scale of screen

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

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

[Bug 1910262] Re: [MIR] libbackuppc-xs-perl

2021-01-07 Thread Christian Ehrhardt 

MIR Team ACK for backuppc-rsync, assigning to security as explained
above.

** Changed in: backuppc-rsync (Ubuntu)
   Status: In Progress => New

** Changed in: backuppc-rsync (Ubuntu)
 Assignee: Christian Ehrhardt  (paelzer) => Ubuntu Security Team 
(ubuntu-security)

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

Title:
  [MIR] libbackuppc-xs-perl

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

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

[Bug 1652822] Re: grub efi doesn't install fs module needed to access root

** Description changed:

  [Impact]
  
  One can't deploy using root XFS partition using 18.04 on UEFI platform.
  
  [Test case]
  
  * Deploy a Bionic machine with a storage layout as follows:
  
  vda-part1 536.9 MB fat32 /boot/efi
  vgroot-lvroot 31.7 GB xfs / ## Only xfs is important here.
  
  The Bionic/18.04LTS deployments will fail to boot and will be redirected to 
grub prompt:
  grub>
  
- [Where could problem occurs]
+ [Where problems could occur]
  
  I checked the delta between the 2 grub (Bionic and Focal) versions after
  the add of 'xfs' module to see if thre is any fixes/CVE/... that we
  should pick up, and I found nothing.
  
  There is this change:
  - xfs: Accept filesystem with sparse inodes
  
  But it only seems to affect xfsprogs (4.16.0) which is not found in
  Bionic.
  
  Ryan, cyphermox and I were concerned that it is adding to the set of
  modules included in the secureboot-signed binary. I confirmed with
  vorlon and everything seemed okay on his end.
  
  If something arise, it will be around xfs itself, and shouldn't affect
  other FS module. Situation would be as it is right now, xfs not working
  with uefi platform.
  
  [Other information]
  
  * Debian:
  
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911147
  
  debian/changelog:
   - Add xfs module to signed UEFI images (closes: #911147, LP: #1652822).
  
  * Salsa commit:
  
https://salsa.debian.org/grub-team/grub/-/commit/01f1eee93acd4113475b403f80661cf651fbcc00
  
  * The workaround is to create a /boot partition, with ext4, so you have:
  
  # Example
  vda-part1 ext4 /boot
  vda-part2 fat32 /boot/efi
  vgroot-lvroot xfs /
  
  [Original Description]
  
  If I do a fresh install on an efi system and use xfs for the root and
  boot filesystems, the install will succeed and then on reboot grub will
  drop to a grub shell and fail to boot.  If I try to do an ls on any of
  the xfs filesystems, grub reports unsupported filesystem.  Doing an
  insmod on xfs.mod doesn't work on the xfs filesystem since it can't be
  read
  
  /boot/efi is a fat32 esp partition and can be read by grub.  I can make the 
system boot by putting a copy of /boot/grub/x86_64-efi/xfs.mod in 
/boot/efi/EFI/ubuntu/xfs.mod and then putting the following line in 
/boot/efi/EFI/ubuntu/grub.cfg
  insmod (hd0,gpt1)/EFI/ubuntu/xfs.mod
  
  I'm guessing this would work if boot was ext2.
  
  My current HDD setup is:
  fdisk -l /dev/sda
  Disk /dev/sda: 477 GiB, 512110190592 bytes, 1000215216 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: gpt
  Disk identifier: 5F358931-DDAE-4F78-8647-B54434A5A3DC
  
  Device   Start   End   Sectors   Size Type
  /dev/sda1 2048   2000895   1998848   976M EFI System
  /dev/sda2  2000896   4001791   2000896   977M Linux filesystem
  /dev/sda3  4001792 804902911 800901120 381.9G Linux LVM
  
  My current fstab is:
  /dev/mapper/vgroot-lvroot /   xfs defaults0   0
  # /boot was on /dev/sda2 during installation
  UUID=006c4d31-8c29-4e25-b8c2-5f70f5f19afd /boot   xfs defaults
0   0
  # /boot/efi was on /dev/sda1 during installation
  UUID=DFD4-FB95  /boot/efi   vfatumask=0077  0   1
  /dev/mapper/vgroot-lvhome /home   xfs defaults0   0
  /dev/mapper/vgroot-lvswap noneswapsw  0   0
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: grub-efi-amd64 2.02~beta2-36ubuntu3.2
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Dec 27 12:42:40 2016
  InstallationDate: Installed on 2016-12-27 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  grub efi doesn't install fs module needed to access root

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

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

[Bug 1907559] Re: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build

2021-01-07 Thread michael moris

duno how relevant this is but my graphics card fryed itself this week
was an asus geforce gtx 570 swapped it for a 670 no issues yesterday on
the same card this is the 2nd time i have turned my machine on with this
card in and first time i have seen the error. hope this helps

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

Title:
  nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1: nvidia kernel
  module failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1907559/+subscriptions

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

[Bug 1909012] Re: my display are disappeared with I used libreoffice or other software

2021-01-07 Thread Michele N

casa@casa-System-Product-Name:~$ sudo journalctl -f
[sudo] password di casa: 
-- Logs begin at Fri 2020-06-05 13:14:15 CEST. --
gen 07 15:27:40 casa-System-Product-Name systemd[1]: mnt-9B78\x2dB5E9.mount: 
Job mnt-9B78\x2dB5E9.mount/start failed with result 'dependency'.
gen 07 15:27:40 casa-System-Product-Name systemd[1]: 
dev-disk-by\x2duuid-9B78\x2dB5E9.device: Job 
dev-disk-by\x2duuid-9B78\x2dB5E9.device/start failed with result 'timeout'.
gen 07 15:31:23 casa-System-Product-Name rtkit-daemon[1437]: Supervising 4 
threads of 2 processes of 1 users.
gen 07 15:31:23 casa-System-Product-Name rtkit-daemon[1437]: Supervising 4 
threads of 2 processes of 1 users.
gen 07 15:34:03 casa-System-Product-Name dbus-daemon[1175]: [session uid=1000 
pid=1175] Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.102' (uid=1000 pid=3326 
comm="/usr/bin/gnome-terminal.real " label="unconfined")
gen 07 15:34:03 casa-System-Product-Name systemd[1025]: Starting GNOME Terminal 
Server...
gen 07 15:34:03 casa-System-Product-Name dbus-daemon[1175]: [session uid=1000 
pid=1175] Successfully activated service 'org.gnome.Terminal'
gen 07 15:34:03 casa-System-Product-Name systemd[1025]: Started GNOME Terminal 
Server.
gen 07 15:34:16 casa-System-Product-Name sudo[3349]: casa : TTY=pts/0 ; 
PWD=/home/casa ; USER=root ; COMMAND=/bin/journalctl -f
gen 07 15:34:16 casa-System-Product-Name sudo[3349]: pam_unix(sudo:session): 
session opened for user root by (uid=0)

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

Title:
  my display are disappeared with I used libreoffice or other software

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

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

[Bug 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"

> So, looking at the systemd code at
https://github.com/systemd/systemd/blob/c5b6b4b6d08cf4c16a871401358faeb5a186c02a/src/shared
/sleep-config.c#L422-L426, perhaps setting /sys/power/resume to the
correct device actually was the workaround/fix?

The confusing part about this is that I don't believe I set
/sys/power/resume when I first booted, so I guess that was set correctly
for some reason this time around?  (Or maybe something else is going on
entirely, of course.)

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

Title:
  `systemctl hibernate` incorrectly reports "Not enough swap space for
  hibernation"

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

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

[Bug 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"

I enabled systemd-logind debug logging, and I saw:

Jan 06 17:45:18 surprise systemd-logind[73027]: Got message type=method_call 
sender=:1.264 destination=:1.220 path=/org/freedesktop/login1 
interface=org.freedesktop.login1.Manager member=CanHibernate cookie=6 
reply_cookie=0 signature=n/a error-name=n/a error-message=n/a
Jan 06 17:45:18 surprise systemd-logind[73027]: Sleep mode "disk" is supported 
by the kernel.
Jan 06 17:45:18 surprise systemd-logind[73027]: /dev/dm-2: is a candidate 
device.
Jan 06 17:45:18 surprise systemd-logind[73027]: /dev/sda2: ignoring device with 
lower priority
Jan 06 17:45:18 surprise systemd-logind[73027]: No swap partitions or files 
matching resume config were found in /proc/swaps.
Jan 06 17:45:18 surprise systemd-logind[73027]: Sent message type=method_return 
sender=n/a destination=:1.264 path=n/a interface=n/a member=n/a cookie=185 
reply_cookie=6 signature=s error-name=n/a error-message=n/a
Jan 06 17:45:18 surprise systemd-logind[73027]: Got message type=method_call 
sender=:1.264 destination=:1.220 path=/org/freedesktop/login1 
interface=org.freedesktop.login1.Manager member=CanHybridSleep cookie=7 
reply_cookie=0 signature=n/a error-name=n/a error-message=n/a
Jan 06 17:45:18 surprise systemd-logind[73027]: Sleep mode "disk" is supported 
by the kernel.
Jan 06 17:45:18 surprise systemd-logind[73027]: /dev/dm-2: is a candidate 
device.
Jan 06 17:45:18 surprise systemd-logind[73027]: /dev/sda2: ignoring device with 
lower priority
Jan 06 17:45:18 surprise systemd-logind[73027]: No swap partitions or files 
matching resume config were found in /proc/swaps.

However, after a reboot this morning, hibernation does seem to be
working, and I instead see:

Jan 07 09:29:37 surprise systemd-logind[1798]: Got message type=method_call 
sender=:1.125 destination=org.freedesktop.login1 path=/org/freedesktop/login1 
interface=org.freedesktop.login1.Manager member=Hibernate cookie=3 
reply_cookie=0 signature=b error-name=n/a error-message=n/a
Jan 07 09:29:37 surprise systemd-logind[1798]: Sleep mode "disk" is supported 
by the kernel.
Jan 07 09:29:37 surprise systemd-logind[1798]: /dev/sda2: device matches 
configured resume settings.
Jan 07 09:29:37 surprise systemd-logind[1798]: Hibernation will attempt to use 
swap entry with path: /dev/sda2, device: 8:2, offset: 0, priority: -3
Jan 07 09:29:37 surprise systemd-logind[1798]: Enough swap for hibernation, 
Active(anon)=3080788 kB, size=102401108 kB, used=0 kB, threshold=98%

So it looks like the issue is that my resume device was not being
detected correctly previously, meaning that priority was being used
(which resulted in the wrong device being selected).

So, looking at the systemd code at
https://github.com/systemd/systemd/blob/c5b6b4b6d08cf4c16a871401358faeb5a186c02a/src/shared
/sleep-config.c#L422-L426, perhaps setting /sys/power/resume to the
correct device actually was the workaround/fix?

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

Title:
  `systemctl hibernate` incorrectly reports "Not enough swap space for
  hibernation"

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

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

[Bug 1910551] [NEW] Qt Creator uses Clang-8 and expects Clang-8 include files but has no dependency on clang-8 include files

2021-01-07 Thread M W

Public bug reported:

```
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
```

qtcreator version:

```
apt show qtcreator
Package: qtcreator
Version: 4.11.0-2build2
Priority: optional
Section: universe/devel
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian Qt/KDE Maintainers 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 115 MB
Depends: libqt5sql5-sqlite, qml-module-qtqml-models2, 
qml-module-qtquick-controls (>= 5.5.0~), qml-module-qtquick2 (>= 5.5.0~), 
qtchooser, qtcreator-data (= 4.11.0-2build2), libc6 (>= 2.29), libclang1-8 (>= 
1:7~svn334604-1~+0~), libgcc-s1 (>= 3.0), libkf5syntaxhighlighting5, libllvm8 
(>= 1:8~svn298832-1~), libqbscore1.13 (>= 1.12.0), libqt5concurrent5 (>= 
5.6.2~), libqt5core5a (>= 5.12.2), libqt5designer5 (>= 5.6.2~), 
libqt5designercomponents5 (>= 5.6.2~), libqt5gui5 (>= 5.12.2) | libqt5gui5-gles 
(>= 5.12.2), libqt5help5 (>= 5.9.0), libqt5network5 (>= 5.6.2~), 
libqt5printsupport5 (>= 5.6.2~), libqt5qml5 (>= 5.2.0~rc1), libqt5quick5 (>= 
5.9.0~beta) | libqt5quick5-gles (>= 5.9.0~beta), libqt5quickwidgets5 (>= 
5.11.0), libqt5script5 (>= 5.6.2~), libqt5serialport5 (>= 5.9.0), libqt5sql5 
(>= 5.6.2~), libqt5widgets5 (>= 5.12.2), libqt5xml5 (>= 5.6.2~), libstdc++6 (>= 
9), qtbase-abi-5-12-8, qtdeclarative-abi-5-12-8
Recommends: clang, clang-tidy, gdb, make, qmlscene, qt5-doc, 
qt5-qmltooling-plugins, qtbase5-dev-tools, qtcreator-doc, 
qtdeclarative5-dev-tools, qttools5-dev-tools, qttranslations5-l10n, 
qtxmlpatterns5-dev-tools, xterm | x-terminal-emulator
Suggests: clazy (>= 1.5), cmake, g++, git, kate-data, subversion, valgrind
Breaks: qtcreator-data (<< 4.5.2-2~)
Replaces: qtcreator-data (<< 4.5.2-2~)
Homepage: https://doc.qt.io/qt-5/topics-app-development.html
Download-Size: 29.0 MB
APT-Manual-Installed: yes
APT-Sources: http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
Description: integrated development environment (IDE) for Qt
 Qt Creator is a cross-platform integrated development environment (IDE)
 designed to make development with the Qt application framework faster
 and easier.
 .
 It includes:
  * An advanced C++ code editor
  * Integrated GUI layout and forms designer
  * Project and build management tools
  * Integrated, context-sensitive help system
  * Visual debugger
  * Rapid code navigation tools
  * Supports multiple platforms
  * Qt Quick Designer
```

Qt Creator has a code model which shows errors as the project is being
worked on.

However, in the event that clang-8's include files are missing (which
was the case because I did not have clang-8 installed, just libclang1-8
which was the actual dependency, and clang-10), the Clang code model
shows errors about "stddef" not being found, thus indirectly causing C++
Qt projects to show a lot of phantom errors.

This is essentially a missing-dependency issue; Qt Creator expects the
include files of the Clang version it was compiled with, and it doesn't
get them.

The exact issue was determined via:
```
ldd /usr/lib/x86_64-linux-gnu/qtcreator/libexec/clangbackend
linux-vdso.so.1 (0x7ffde3bee000)
libSqlite.so.4 => 
/usr/lib/x86_64-linux-gnu/qtcreator/libexec/../libSqlite.so.4 
(0x7fe611caf000)
libClangsupport.so.4 => 
/usr/lib/x86_64-linux-gnu/qtcreator/libexec/../libClangsupport.so.4 
(0x7fe611c2d000)
libUtils.so.4 => 
/usr/lib/x86_64-linux-gnu/qtcreator/libexec/../libUtils.so.4 
(0x7fe61196d000)
libclang-8.so.1 => /lib/x86_64-linux-gnu/libclang-8.so.1 
(0x7fe60ffc2000)
<...further details omitted...>
```

Installing package "clang-8" completely resolved the issue.
If that is not an available workaround, providing /usr/include/clang/8/include 
(symlink to other Clang include directory?) should be sufficient, but I haven't 
tested this.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: qtcreator 4.11.0-2build2
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Thu Jan  7 14:20:01 2021
InstallationDate: Installed on 2020-10-06 (93 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: qtcreator
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Summary changed:

- Qt Creator has dependency on Clang-10 but uses Clang-8 and expects Clang-8 
include files
+ Qt Creator uses Clang-8 and expects Clang-8 include files but has no 
dependency on clang-8 include files

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

Title:
  Qt Creator uses Clang-8 and expects Clang-8 include files but has no
  dependency on clang-8 include files

[Bug 1908756] Re: Ubuntu 20.10 - elfutils unwinding broken for s390 compat

2021-01-07 Thread Frank Heimes

** Changed in: elfutils (Ubuntu Groovy)
   Status: New => 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/1908756

Title:
  Ubuntu 20.10 - elfutils unwinding broken for s390 compat

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

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

[Bug 1910542] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1910542/+attachment/5450274/+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/1910542

Title:
  Last kernel breaks cable connection

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

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

[Bug 1910542] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1910542/+attachment/5450275/+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/1910542

Title:
  Last kernel breaks cable connection

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

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

[Bug 1910542] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1910542/+attachment/5450273/+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/1910542

Title:
  Last kernel breaks cable connection

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

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

[Bug 1910542] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1910542/+attachment/5450272/+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/1910542

Title:
  Last kernel breaks cable connection

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

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

[Bug 1910542] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1910542/+attachment/5450271/+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/1910542

Title:
  Last kernel breaks cable connection

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

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

[Bug 1910542] ProcEnviron.txt

apport information

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

Title:
  Last kernel breaks cable connection

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

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

[Bug 1910542] ProcCpuinfoMinimal.txt

apport information

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

Title:
  Last kernel breaks cable connection

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

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

[Bug 1910542] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1910542/+attachment/5450268/+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/1910542

Title:
  Last kernel breaks cable connection

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

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

[Bug 1910542] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1910542/+attachment/5450267/+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/1910542

Title:
  Last kernel breaks cable connection

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

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

[Bug 1910542] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1910542/+attachment/5450266/+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/1910542

Title:
  Last kernel breaks cable connection

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

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

[Bug 1910542] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1910542/+attachment/5450265/+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/1910542

Title:
  Last kernel breaks cable connection

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

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

[Bug 1910542] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1910542/+attachment/5450264/+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/1910542

Title:
  Last kernel breaks cable connection

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

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

[Bug 1910542] Re: Last kernel breaks cable connection