date:20210812

[Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

2021-08-12 Thread Kai-Heng Feng

But that commit didn't modify any file...

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

Title:
  Thinkpad T430u won't boot without noapic workaround

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


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

[Bug 1939658] [NEW] Several potential bugs of null pointer dereference

2021-08-12 Thread yuxuan He

Public bug reported:

Ubuntu version: 18.04
libx11-xcb-dev version:1.6.2
Hello,I found some potential bugs in package libx11-xcb-dev,and the word file 
in the attachment I uploaded shows the occurrence process of the bug in a 
graphical way.Would you help me check whether the bugs mentioned below are 
true? I'm not 100% sure that the bugs I submitted is correct. I hope you don't 
mind seeing the wrong bug I submitted.Thank you very much for your patience.

In file libx11-1.6.2/src/Xrm.c,defination of function 
XrmCombineFileDatabase,line 1700 or line 1702.
there is a statement call function NewDataBase(),load its return value to 
db,and this function may return a null pointer.in line 1703,there is a 
statement derefer db without check it.the process of this potential bug is 
shown in figure 1. 

In file libx11-1.6.2/src/Xrm.c,defination of function XrmGetStringDatebase,line 
1559.
there is a statement call function NewDataBase(),load its return value to 
db,and this function may return a null pointer.in line 1560,there is a 
statement derefer db without check it.the process of this potential bug is 
shown in figure 2. 

In file libx11-1.6.2/src/Xrm.c,defination of function append_value_list,line 
489.
there is a statement call function Xmalloc to allocate memory,load its return 
value to value_list,but Xmalloc may fail to allocate memory,so value_list may 
be a null pointer.in line 490,there is a statement derefer value_list without 
check it.the process of this potential bug is shown in figure 3. 

In file libx11-1.6.2/modules/im/ximcp/imLcIm.c,defination of function 
_XimWriteCachedDefaultTree,line 472.
there is a statement call function Xmalloc to allocate memory,load its return 
value to m,but Xmalloc may fail to allocate memory,so m may be a null 
pointer.statements after derefer value_list without check it.the process of 
this potential bug is shown in figure 4. 

In file libx11-1.6.2/src/PolyReg.c,defination of function InsertEdgeInET,line 
98.
there is a statement call function Xmalloc to allocate memory,load its return 
value to tmpSLLBlock,but Xmalloc may fail to allocate memory,so tmpSLLBlock may 
be a null pointer.in line 100,there is a statement derefer tmpSLLBlock without 
check it.the process of this potential bug is shown in figure 5. 

In file libx11-1.6.2/modules/im/ximcp/imCallbk.c,defination of function 
_XimStrConversionCallback,line 342.
there is a statement call function Xmalloc to allocate memory,load its return 
value to buf,but Xmalloc may fail to allocate memory,so buf may be a null 
pointer.in line 344,buf act as the first parameter of funcion 
_XimSetHeader(this function is in file 
libx11-1.6.2/modules/im/ximcp/imDefIm.c,line 78),in this function there are 
several statement derefer buf without check.the process of this potential bug 
is shown in figure 6. 

In file libx11-1.6.2/modules/im/ximcp/imCallbk.c,defination of function 
_read_text_from_packet,line 532.
there is a statement call function Xmalloc to allocate memory,load its return 
value to text->feedback,but Xmalloc may fail to allocate memory,so 
text->feedback may be a null pointer.In line 535,there is a statement derefer 
text->feedback without check it.the process of this potential bug is shown in 
figure 7. 

In file libx11-1.6.2/src/xcms/cmsColNm.c,defination of function 
_XcmsParseColorString,line 212.
there is a statement call function Xmalloc to allocate memory,load its return 
value to string_lowered ,but Xmalloc may fail to allocate memory,so 
string_lowered may be a null pointer.In line 219,there is a statement derefer 
string_lowered without check it.the process of this potential bug is shown in 
figure 8. 

In file libx11-1.6.2/src/xcms/cmsColNm.c,defination of function 
_XcmsLookupColorName,line 421.
there is a statement call function Xmalloc to allocate memory,load its return 
value to name_lowered ,but Xmalloc may fail to allocate memory,so name_lowered 
may be a null pointer.In line 432,there is a statement derefer name_lowered 
without check it.the process of this potential bug is shown in figure 9.

In file libx11-1.6.2/src/xcms/IdOfPr.c,defination of function 
XcmsFormatOfPrefix,line 70.
there is a statement call function Xmalloc to allocate memory,load its return 
value to string_lowered ,but Xmalloc may fail to allocate memory,so 
string_lowered  may be a null pointer.In line 82,there is a statement derefer 
string_lowered without check it.the process of this potential bug is shown in 
figure 10.

In file libx11-1.6.2/src/InitExt.c,defination of function XESetWireToError,line 
332.
there is a statement call function Xmalloc to allocate memory,load its return 
value to dpy->error_vec ,but Xmalloc may fail to allocate memory,so 
dpy->error_vec may be a null pointer.In line 334,there is a statement derefer 
dpy->error_vec without check it.the process of this potential bug is shown in 
figure 11.

In file libx11-1.6.2/src/xlibi18n/XDefaultIMIF.c,defination of function 
_SetIMValues,line 279.
there i

[Bug 1939657] [NEW] install crashes

2021-08-12 Thread monasterio

Public bug reported:

crashes midway of install

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.6
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 12 00:25:00 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu

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

Title:
  install crashes

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


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

[Bug 1939565] Re: kernel signed by mok failed to boot if secure boot is on

2021-08-12 Thread Kai-Chuan Hsieh

@ycheng-twn

I try to update my manifest and install iso on DLPN-MT-EVT-C1/BIOS 0.10.28.
The ISO is 
http://10.101.46.50:8080/job/dell-bto-focal-fossa-davos-adl/lastSuccessfulBuild/artifact/out/dell-bto-focal-fossa-davos-adl-X142-20210812-9.iso

I can finish the installation and the secure boot is enabled after
installation.


** Attachment added: "chroot.sh.log"
   
https://bugs.launchpad.net/oem-priority/+bug/1939565/+attachment/5517471/+files/chroot.sh.log

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

Title:
  kernel signed by mok failed to boot if secure boot is on

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


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

[Bug 1939379] Re: ARM kernel builds fail with GCC 11

2021-08-12 Thread Launchpad Bug Tracker

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

** Changed in: gcc-11 (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/1939379

Title:
  ARM kernel builds fail with GCC 11

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


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

[Bug 1939664] [NEW] Several potential bugs of memory leak

2021-08-12 Thread yuxuan He

Public bug reported:

Ubuntu version: 18.04
libx11-xcb-dev version:1.6.2
Hello,I found some potential bugs in package libx11-xcb-dev,and the microsoft 
word file in the attachment I uploaded shows the occurrence process of the bug 
in a graphical way.Would you help me check whether the bugs mentioned below are 
true? I'm not 100% sure that the bugs I submitted is correct. I hope you don't 
mind seeing the wrong bug I submitted.Thank you very much for your patience.

In file libx11-1.6.2/modules/im/ximcp/imLcPrs.c,defination of 
parsestringfile,line 733.
The statement "tbp=malloc(size);"allocate memory to tbp and in line 733,if 
select false branch at this statement,tbp will not be freed correctly.the 
process of this potential bug is shown in figure 1.

In file libx11-1.6.2/src/xlibi18n/lcDB.c,defination of f_numeric,line 882.
The statement "wordp=malloc(len+1);"allocate memory to wordp and in line 883,if 
select false branch at this statement,function f_numeric will go on to 
execute.In line 910,if select false branch at this statement,wordp will not be 
freed correctly.the process of this potential bug is shown in figure 2.

In file libx11-1.6.2/src/xlibi18n/lcDB.c,defination of f_numeric,line 882.
The statement "wordp=malloc(len+1);"allocate memory to wordp and in line 883,if 
select false branch at this statement,function f_numeric will go on to 
execute.and if select true branch in line 938,flow goto err,In line 989,if 
select false branch here,wordp will not be freed correctly.the process of this 
potential bug is shown in figure 3.

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

** Attachment added: "libx11_memory_leak.docx"
   
https://bugs.launchpad.net/bugs/1939664/+attachment/5517495/+files/libx11_memory_leak.docx

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

Title:
  Several potential bugs of memory leak

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


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

[Bug 1939665] [NEW] "apt-get update" fails if another instance is running

2021-08-12 Thread Avi Kivity

Public bug reported:

This snippet:

 sudo apt-get update & sudo apt-get update & wait; wait

will result in one apt-get run succeeding and the other failing on the
lock:

[1] 3006473
[2] 3006474
Hit:1 http://ports.ubuntu.com/ubuntu-ports groovy InRelease
Hit:2 http://ports.ubuntu.com/ubuntu-ports groovy-backports InRelease
Hit:3 http://ports.ubuntu.com/ubuntu-ports groovy-security InRelease
Hit:4 http://ports.ubuntu.com/ubuntu-ports groovy-updates InRelease
Reading package lists... Done
E: Could not get lock /var/lib/apt/lists/lock. It is held by process 3006476 
(apt-get)
N: Be aware that removing the lock file is not a solution and may break your 
system.
E: Unable to lock directory /var/lib/apt/lists/
Reading package lists... Done
[1]-  Donesudo apt-get update
[2]+  Exit 100sudo apt-get update


Note that apt-get upgrade will correctly wait.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: apt 2.1.10ubuntu0.3
ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
Uname: Linux 5.8.0-48-generic aarch64
ApportVersion: 2.20.11-0ubuntu50.7
Architecture: arm64
CasperMD5CheckResult: skip
Date: Thu Aug 12 07:50:16 2021
ProcEnviron:
 LC_TIME=C.UTF-8
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: apt
UpgradeStatus: Upgraded to groovy on 2021-03-25 (139 days ago)

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


** Tags: apport-bug arm64 groovy uec-images

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

Title:
  "apt-get update" fails if another instance is running

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


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

[Bug 1939638] Re: [regression] USB device is not detected during boot

2021-08-12 Thread Anthony Wong

** Summary changed:

- USB device is not detected during boot
+ [regression] USB device is not detected during boot

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

Title:
  [regression] USB device is not detected during boot

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


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

[Bug 1939222] Re: DisplayPort over USB-C not working after release update

2021-08-12 Thread AaronMa

Could you try 5.13 kernel too?
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13/amd64/

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

Title:
  DisplayPort over USB-C not working after release update

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


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

[Bug 1930645] Re: Fix Ethernet not working by hotplug - RTL8106E

2021-08-12 Thread Stefan Bader

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

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

Title:
  Fix Ethernet not working by hotplug - RTL8106E

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


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

[Bug 1938999] Re: External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock

2021-08-12 Thread AaronMa

I am trying to find T490 to reproduce.
Please wait a while.

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

Title:
  External displays not working on Thinkpad T490 with ThinkPad
  Thunderbolt 3 Dock

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


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

[Bug 1939618] Re: EP11 cards going offline => Fix backport to U20.04LTS

2021-08-12 Thread Frank Heimes

Well, this is a patch set of 34 commits, which is significant, and looks
to me that they cover much more than just fixing "EP11 cards going
offline", rather than bringing the entire driver to the latest level.
The usual way is to pick the minimal set of patches that fix a
particular issue and get these SRUed.

And btw. this is a relatively unusual way of sharing patches or backports -- if 
about a handful of patches (or two) are needed, we would do cherry-picks or 
apply selective backport patch-files.
In case of more patches the usual way is a branch with a pull-request.

But the patches seem to apply cleanly to the current focal master-next
tree and touch s390x specific files only (either in /arch/s390/ or in
/drivers/s390/).

Please notice that hirsute's 5.11 kernel would need to be on the same
level, to avoid any potential regressions on upgrades.

I'll bring this to the kernel teams attention and we'll discuss if this
is doable as SRU.


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

** Changed in: linux (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel 
Team (canonical-kernel-team)

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

Title:
  EP11 cards going offline => Fix backport to U20.04LTS

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


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

[Bug 1939665] Re: "apt-get update" fails if another instance is running

2021-08-12 Thread Chris Guiver

Thank you for reporting this bug to Ubuntu.

Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please re-report the issue using
`ubuntu-bug`.

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

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

Title:
  "apt-get update" fails if another instance is running

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


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

[Bug 1939665] Re: "apt-get update" fails if another instance is running

2021-08-12 Thread Chris Guiver

Please note:  I see your issue as being opinion & expected behavior.
Many users use the conditional "&&" in commands like yours as it can be
considered safer.

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

Title:
  "apt-get update" fails if another instance is running

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


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

[Bug 1939406] Re: o2cb service doesn't have online/offline/configure commands on Ubuntu 20.04 LTS

2021-08-12 Thread Pierre Allétru

Thanks for the prompt answer and action Athos, much appreciated!

** Description changed:

- On Ubuntu 20.04 the service `o2cb` have some important commands missing,
+ On Ubuntu 20.04 the service `o2cb` has some important commands missing,
  such as `online`, `offline`, and `configure`. The issue doesn't happen
  on Ubuntu 18.04 and below.
  
  Ubuntu 18.04:
  ```
  $ o2cb --version
  o2cb 1.8.5
  $ sudo service o2cb something
  Usage: /etc/init.d/o2cb 
{start|stop|restart|force-reload|enable|disable|configure|load|unload|online|offline|force-offline|status|online-status}
  ```
  
  Ubuntu 20.04:
  ```
  $ o2cb --version
  o2cb 1.8.6
  $ sudo service o2cb online
  Usage: /etc/init.d/o2cb {start|stop|status|restart|try-restart|force-reload}
  ```
  
  In both cases I installed `o2cb` via:
  ```
  $ sudo apt-get update && sudo apt-get install ocfs2-tools -y
  ```
  
  Is there something I am missing? The
  [manpage](http://manpages.ubuntu.com/manpages/focal/man7/o2cb.7.html)
  for Ubuntu 20.04 does mention the `online` command.
  
  See related Github issue:
  https://github.com/markfasheh/ocfs2-tools/issues/50

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

Title:
  o2cb service doesn't have online/offline/configure commands on Ubuntu
  20.04 LTS

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


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

[Bug 1938143] Re: Include product_sku info to modalias

2021-08-12 Thread Stefan Bader

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

** Changed in: linux (Ubuntu Hirsute)
   Importance: Medium => Wishlist

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

Title:
  Include product_sku info to modalias

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


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

[Bug 1930645] Re: Fix Ethernet not working by hotplug - RTL8106E

2021-08-12 Thread koba

** No longer affects: linux-oem (Ubuntu)

** No longer affects: linux-oem (Ubuntu Focal)

** No longer affects: linux-oem (Ubuntu Hirsute)

** No longer affects: linux-oem (Ubuntu Impish)

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

Title:
  Fix Ethernet not working by hotplug - RTL8106E

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


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

[Bug 1641303] Re: Wish: apt shouldn't show kept-back packages within the list of upgradable

2021-08-12 Thread Julian Andres Klode

There's some misconception here; held back is a package-level flag.

ALinuxUser: Just use pinning instead of holds to achieve that.

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

Title:
  Wish: apt shouldn't show kept-back packages within the list of
  upgradable

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


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

[Bug 1939665] Re: "apt-get update" fails if another instance is running

2021-08-12 Thread Julian Andres Klode

Please ignore Chris (well, do upgrade though, 20.10 is ld, it hasn't
seen security updates in months)

I understand your report, I only implemented lock waiting for the dpkg
lock, not for the list lock that update holds.

Note that apt-get generally doesn't wait for the lock, only apt does
(you can pass/set options to make apt-get behave the same).

I'm not sure update lock waiting is necessary - there's little point in
running update again if you are already updating. It makes sense for
install, because you might just want to schedule two installs.

OTOH, I can see you writing a script that does update and install, and
which breaks because apt-daily.service is running in the background.

** Changed in: apt (Ubuntu)
   Status: Invalid => Triaged

** Changed in: apt (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  "apt-get update" fails if another instance is running

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


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

[Bug 1845765] Re: asterisk-modules package built without amr_codec.so

2021-08-12 Thread Dmitriy Rodin

This module depends on opencore-amrnb, opencore-amrwb and vo-amrwbenc
together.

Because the libvo-amrwbenc-dev package was not found in the build
environment, the compilation of this module was silently skipped.

To solve this problem, add libvo-amrwbenc-dev to build dependencies in
debian/control file and rebuild the package.


I copied this module to existing installation and reload asterisk:


Connected to Asterisk 16.2.1~dfsg-2ubuntu1 currently running on vserver3 (pid = 
6653)
vserver3*CLI> module show like codec_amr
Module Description  Use 
Count  Status  Support Level
codec_amr.so   AMR Coder/Decoder0   
   Running  core
1 modules loaded

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

Title:
  asterisk-modules package built without amr_codec.so

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


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

[Bug 1939658] Re: Several potential bugs of null pointer dereference

2021-08-12 Thread Ubuntu Foundations Team Bug Bot

The attachment "libx11_nullptr_dereference.docx" seems to be a patch.
If it isn't, please remove the "patch" flag from the attachment, remove
the "patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Several potential bugs of null pointer dereference

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


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

[Bug 1939657] Re: install crashes

2021-08-12 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your log files attached to this bug report it
seems that there is a problem with your installation media (CD/DVD).
You can verify the integrity of the Ubuntu ISO files you downloaded by
following the instructions at
https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry
your installation with new media.  In the event that is is not in fact
an error with your installation media please set the bug's status back
to New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

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

** Tags added: ident-mismatch

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

Title:
  install crashes

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


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

[Bug 1939665] Re: "apt-get update" fails if another instance is running

2021-08-12 Thread Avi Kivity

In practice the two processes that run apt-get update are unaware of
each other. When I'm updating of course I wouldn't intentionally run two
instances in parallel. Indeed the other process is likely apt-
daily.service.

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

Title:
  "apt-get update" fails if another instance is running

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


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

[Bug 1939658] Re: Several potential bugs of null pointer dereference

2021-08-12 Thread yuxuan He

** Tags removed: patch

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

Title:
  Several potential bugs of null pointer dereference

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


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

[Bug 1939671] [NEW] nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build

2021-08-12 Thread moosa jati waspodo

Public bug reported:

cashed while updating

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-340 340.108-0ubuntu5.20.04.2
ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-63-generic x86_64
NonfreeKernelModules: wl nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.11.0-25-generic
Date: Thu Aug 12 15:53:22 2021
InstallationDate: Installed on 2021-07-31 (11 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageVersion: 340.108-0ubuntu5.20.04.2
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: nvidia-graphics-drivers-340
Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to 
build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed
  to build

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


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

[Bug 1936899] Re: [IoTG] [TGL-H] TPM tests fail

2021-08-12 Thread Anthony Wong

** Changed in: linux-intel (Ubuntu)
   Status: New => Invalid

** Changed in: intel
   Status: New => Invalid

** Changed in: intel
   Importance: Critical => Undecided

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

Title:
  [IoTG] [TGL-H] TPM tests fail

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


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

[Bug 1845765] Re: asterisk-modules package built without amr_codec.so

2021-08-12 Thread Dmitriy Rodin

** Changed in: asterisk (Ubuntu)
   Status: Triaged => Confirmed

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

Title:
  asterisk-modules package built without amr_codec.so

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


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

[Bug 1906970] Re: dpkg hook hostname error

2021-08-12 Thread Paride Legovini

I verified that the landed fix also fixes the sbuild autopkgtest
failure:

build-procenvPASS
unshare-qemuwrapper  SKIP installation fails and skip-not-installable set
unshare  PASS


** Changed in: sbuild (Ubuntu)
   Status: Triaged => 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/1906970

Title:
  dpkg hook hostname error

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


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

[Bug 1929860] Re: initrdfail can result in resuming with different initrd images and hanging resume

2021-08-12 Thread Launchpad Bug Tracker

** Merge proposal linked:
   https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/407003

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

Title:
  initrdfail can result in resuming with different initrd images and
  hanging resume

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


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

[Bug 1925507] Re: grub-common: snapd autopkgtests fail on s390x

2021-08-12 Thread Launchpad Bug Tracker

** Merge proposal linked:
   https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/407003

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

Title:
  grub-common: snapd autopkgtests fail on s390x

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


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

[Bug 1939673] [NEW] Update the 470 and the 470-server NVIDIA drivers

2021-08-12 Thread Alberto Milone

Public bug reported:

Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic,
Focal, Hirsute.

[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.

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

Certification test suite must pass on a range of hardware:
https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

The QA team that executed the tests will be in charge of attaching the
artifacts and console output of the appropriate run to the bug. nVidia
maintainers team members will not mark ‘verification-done’ until this
has happened.

[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned system level tests are attached to this bug.

[Discussion]

[Changelog]

== 470.57.02 (470-server) ==

  *

** Affects: nvidia-graphics-drivers-470 (Ubuntu)
 Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
 Status: Triaged

** Affects: nvidia-graphics-drivers-470-server (Ubuntu)
 Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
 Status: New

** Affects: nvidia-graphics-drivers-470 (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
 Status: New

** Affects: nvidia-graphics-drivers-470-server (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
 Status: New

** Affects: nvidia-graphics-drivers-470 (Ubuntu Focal)
 Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
 Status: New

** Affects: nvidia-graphics-drivers-470-server (Ubuntu Focal)
 Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
 Status: New

** Affects: nvidia-graphics-drivers-470 (Ubuntu Hirsute)
 Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
 Status: New

** Affects: nvidia-graphics-drivers-470-server (Ubuntu Hirsute)
 Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
 Status: New

** Also affects: nvidia-graphics-drivers-470 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-470 (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-470 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-470-server (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Bionic)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Focal)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Hirsute)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Bionic)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Focal)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Hirsute)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  Update the 470 and the 470-server NVIDIA drivers

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


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

[Bug 1929860] Re: initrdfail can result in resuming with different initrd images and hanging resume

2021-08-12 Thread Julian Andres Klode

** Description changed:

- Ubuntu Focal (and new releases) on AWS will normally boot without an
- initrd image (just the microcode.cpio). There is a fallback mechanism to
- reboot with the full initrd image when the boot fails to complete. The
- grub environment variable "initrdfail" is used to track when a boot
- failed and switch between the optimized initrd-less boot path and the
- full initrd path.
+ [Impact]
+ Ubuntu Focal (and new releases) on AWS will normally boot without an initrd 
image (just the microcode.cpio). There is a fallback mechanism to reboot with 
the full initrd image when the boot fails to complete. The grub environment 
variable "initrdfail" is used to track when a boot failed and switch between 
the optimized initrd-less boot path and the full initrd path.
  
  On a normal successful boot, the "initrdfail" variable is cleared by
  grub-initrd-fallback.service. However, this doesn't happen when resuming
  from hibernation. As a result, the initrd fallback will get triggered on
  the second hibernation / resume cycle despite the original boot using
  only the microcode.cpio. This switch in initrd images leads to the
  second resume hanging.
  
  We've been able to successfully avoid this issue by adding the following
  to the ec2-hibinit-agent resume handler:
  
  /usr/bin/grub-editenv - unset initrdfail
  /usr/bin/grub-editenv - unset recordfail
  
  (Note: clearing recordfail may not be necessary, will need to try again
  without it.)
  
  This bug was filed against grub2 as it appears to own initrdfail.
+ 
+ [Test plan]
+ TBD w/ CPC
+ 
+ [Regression potential]
+ Services get changed to oneshot, and wantedby=multi-user sleep; maybe we miss 
other places it should run, or record the wrong thing on resume?

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

Title:
  initrdfail can result in resuming with different initrd images and
  hanging resume

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


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

[Bug 1901553] Re: Improve documentation around initrdless boot

2021-08-12 Thread Julian Andres Klode

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

** Changed in: grub2 (Ubuntu Focal)
Milestone: None => ubuntu-20.04.3

** Description changed:

  [Impact]
+ (sort of prerequisite of bug 1929860 to avoid having to edit the patches and 
possibly introduce bugs that way)
  
   * Sometimes it is not obvious why initrdless boot is generated; when is
  it attempted; and when it fails and boots with initrd.
  
   * Improve UX by leaving breadcrumbs and emit messages about initrdless
  boot, in more places
  
  [Test Case]
  
   * Boot system with initrdless boot
-- for example minimal cloud image from 
https://cloud-images.ubuntu.com/minimal/releases/
-- boot without graphical terminal, i.e. -nographics qemu option
+    - for example minimal cloud image from 
https://cloud-images.ubuntu.com/minimal/releases/
+    - boot without graphical terminal, i.e. -nographics qemu option
   * Upgrade to new grub package
-  * Uncomment GRUB_TERMINAL=console in /etc/default/grub
+  * Uncomment GRUB_TERMINAL=console in /etc/default/grub
  
- 
-  1. Call `sudo update-grub`, a message should be emitted that initrdless boot 
will be attempted.
+  1. Call `sudo update-grub`, a message should be emitted that initrdless
+ boot will be attempted.
  
   2. Inspecting /boot/grub/grub.cfg, there are comments that initrdless
  boot will be attempted
  
   * Reboot
  
   * Observe the following:
  
   3. Inspecting console log, there are echo message from grub about
  attempting initrdless boot.
  
   * Install linux-generic kernel flavour; and remove kvm kernel flavour,
  reboot.
  
   * Observe in the console log
  
   1. There should be message about attempting initrdless boot
   2. kernel panic
   3. message about initrdless boot failing and attempting to boot with initrd
  
  [Regression Potential]
  
   * This change adds a few more user visible message, without
  translations. The actual behaviour that is happening is unchanged. This
  simply better notifies users about what is happening, and can be
  inspected interactively, statically, and from boot logs.
  
  [Other Info]
  
   * CPC requested these UX improvements, as there have been concerns that
  users are failing to discover why initrdless boot is happening; or
  failing; and how to effect it.

** Description changed:

  [Impact]
- (sort of prerequisite of bug 1929860 to avoid having to edit the patches and 
possibly introduce bugs that way)
+ (sort of prerequisite of bug 1929860 to avoid having to edit the patches and 
possibly introduce bugs that way, because these changes port the service to 
systemd unit)
  
   * Sometimes it is not obvious why initrdless boot is generated; when is
  it attempted; and when it fails and boots with initrd.
  
   * Improve UX by leaving breadcrumbs and emit messages about initrdless
  boot, in more places
  
  [Test Case]
  
   * Boot system with initrdless boot
     - for example minimal cloud image from 
https://cloud-images.ubuntu.com/minimal/releases/
     - boot without graphical terminal, i.e. -nographics qemu option
   * Upgrade to new grub package
   * Uncomment GRUB_TERMINAL=console in /etc/default/grub
  
   1. Call `sudo update-grub`, a message should be emitted that initrdless
  boot will be attempted.
  
   2. Inspecting /boot/grub/grub.cfg, there are comments that initrdless
  boot will be attempted
  
   * Reboot
  
   * Observe the following:
  
   3. Inspecting console log, there are echo message from grub about
  attempting initrdless boot.
  
   * Install linux-generic kernel flavour; and remove kvm kernel flavour,
  reboot.
  
   * Observe in the console log
  
   1. There should be message about attempting initrdless boot
   2. kernel panic
   3. message about initrdless boot failing and attempting to boot with initrd
  
  [Regression Potential]
  
   * This change adds a few more user visible message, without
  translations. The actual behaviour that is happening is unchanged. This
  simply better notifies users about what is happening, and can be
  inspected interactively, statically, and from boot logs.
  
  [Other Info]
  
   * CPC requested these UX improvements, as there have been concerns that
  users are failing to discover why initrdless boot is happening; or
  failing; and how to effect it.

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

Title:
  Improve documentation around initrdless boot

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


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

[Bug 1925507] Re: grub-common: snapd autopkgtests fail on s390x

2021-08-12 Thread Julian Andres Klode

** Description changed:

+ [Impact]
+ Probably regression from #1901553, failing to install on s390x, info below.
+ 
+ [Test plan]
+ Just ensure those tests don't fail like that
+ 
+ [Regression potential]
+ grub units only start when /boot is mounted now, as they require 
/boot/grub/grub.cfg to exist. Should be fine, but might not start if boot 
failed to mount for some reason.
+ 
+ [Original bug report]
  Snapd autopkgtests depend on grub-common:
  
  debian/tests/control:
  Depends: @builddeps@
  
  debian/control:
  Build-Depends:
  ...
  grub-common,
  ...
  
  but grub-common fails to install on s390x, consequently snapd
  autopkgtests fall apart on s390x.
  
  Full log:
  
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-
  hirsute-canonical-kernel-team-
  unstable/hirsute/s390x/s/snapd/20210422_080633_56960@/log.gz
  
  ```
  Setting up grub-common (2.04-1ubuntu45) ...
  Created symlink 
/etc/systemd/system/multi-user.target.wants/grub-common.service → 
/lib/systemd/system/grub-common.service.
  Created symlink 
/etc/systemd/system/multi-user.target.wants/grub-initrd-fallback.service → 
/lib/systemd/system/grub-initrd-fallback.service.
  Created symlink 
/etc/systemd/system/rescue.target.wants/grub-initrd-fallback.service → 
/lib/systemd/system/grub-initrd-fallback.service.
  Created symlink 
/etc/systemd/system/emergency.target.wants/grub-initrd-fallback.service → 
/lib/systemd/system/grub-initrd-fallback.service.
  Job for grub-initrd-fallback.service failed because the control process 
exited with error code.
  See "systemctl status grub-initrd-fallback.service" and "journalctl -xe" for 
details.
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  Job for grub-common.service failed because the control process exited with 
error code.
  See "systemctl status grub-common.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript grub-common, action "start" failed.
  [0;1;31m●[0m grub-common.service - Record successful boot for GRUB
-  Loaded: loaded 
(]8;;file://autopkgtest/lib/systemd/system/grub-common.service/lib/systemd/system/grub-common.service]8;;;
 enabled; vendor preset: enabled)
-  Active: [0;1;31mfailed[0m (Result: exit-code) since Thu 2021-04-22 
08:06:10 UTC; 8ms ago
- Process: 3111 ExecStartPre=/bin/sh -c [ -s /boot/grub/grubenv ] || rm -f 
/boot/grub/grubenv; mkdir -p /boot/grub (code=exited, status=0/SUCCESS)
- Process: 3114 ExecStart=grub-editenv /boot/grub/grubenv unset recordfail 
[0;1;31m(code=exited, status=1/FAILURE)[0m
- Process: 3115 ExecStartPost=/bin/sh -c if grub-editenv /boot/grub/grubenv 
list | grep -q initrdless_boot_fallback_triggered=1; then echo "grub: 
GRUB_FORCE_PARTUUID set, initrdless boot paniced, fallback triggered."; fi 
(code=exited, status=0/SUCCESS)
-Main PID: 3114 (code=exited, status=1/FAILURE)
+  Loaded: loaded 
(]8;;file://autopkgtest/lib/systemd/system/grub-common.service/lib/systemd/system/grub-common.service]8;;;
 enabled; vendor preset: enabled)
+  Active: [0;1;31mfailed[0m (Result: exit-code) since Thu 2021-04-22 
08:06:10 UTC; 8ms ago
+ Process: 3111 ExecStartPre=/bin/sh -c [ -s /boot/grub/grubenv ] || rm -f 
/boot/grub/grubenv; mkdir -p /boot/grub (code=exited, status=0/SUCCESS)
+ Process: 3114 ExecStart=grub-editenv /boot/grub/grubenv unset recordfail 
[0;1;31m(code=exited, status=1/FAILURE)[0m
+ Process: 3115 ExecStartPost=/bin/sh -c if grub-editenv /boot/grub/grubenv 
list | grep -q initrdless_boot_fallback_triggered=1; then echo "grub: 
GRUB_FORCE_PARTUUID set, initrdless boot paniced, fallback triggered."; fi 
(code=exited, status=0/SUCCESS)
+    Main PID: 3114 (code=exited, status=1/FAILURE)
  
  Apr 22 08:06:10 autopkgtest systemd[1]: Starting Record successful boot for 
GRUB...
  Apr 22 08:06:10 autopkgtest grub-editenv[3114]: grub-editenv: error: cannot 
rename the file /boot/grub/grubenv.new to /boot/grub/grubenv.
  Apr 22 08:06:10 autopkgtest systemd[1]: 
[0;1;39m[0;1;31m[0;1;39mgrub-common.service: Main process exited, 
code=exited, status=1/FAILURE[0m
  Apr 22 08:06:10 autopkgtest systemd[1]: 
[0;1;38;5;185m[0;1;39m[0;1;38;5;185mgrub-common.service: Failed with result 
'exit-code'.[0m
  Apr 22 08:06:10 autopkgtest systemd[1]: [0;1;31m[0;1;39m[0;1;31mFailed to 
start Record successful boot for GRUB.[0m
  dpkg: error processing package grub-common (--configure):
-  installed grub-common package post-installation script subprocess returned 
error exit status 1
+  installed grub-common package post-installation script subprocess returned 
error exit status 1
  ```

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

** Changed in: grub2 (Ubuntu Focal)
Milestone: None => ubuntu-20.04.3

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

[Bug 1937277] Re: [SRU] OpenSBI 0.9 backport to Focal

2021-08-12 Thread Heinrich Schuchardt

Hello Brian,

booting with 
U-Boot 2021.01+dfsg-3ubuntu0~20.04.3 (Jul 30 2021 - 14:38:17 +)
fails.

Found 14 disks
** Invalid partition 21 **
Cannot read EFI system partition
BootOrder not defined
EFI boot manager: Cannot load any image

The following patches are missing:

3dca77b1dc1b ("efi_loader: partition numbers are hexadecimal")
17f8cda505e3 ("efi_loader: set partition GUID in device path for SIG_TYPE_GUID")

Documentation for flashing U-Boot for the HiFive Unmatched is missing:

70415e1e528d ("board: sifive: add HiFive Unmatched board support")

Generally I would prefer to have the following configuration settings:

CONFIG_CMD_EFIDEBUG=y
CONFIG_CMD_NVEDIT_EFI=y
CONFIG_HEXDUMP=y
# CONFIG_SPL_HEXDUMP is not set

But maybe adjusting these setting is a question of the current release.

Best regards

Heinrich

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

Title:
  [SRU] OpenSBI 0.9 backport to Focal

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


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

[Bug 1939673] Re: Update the 470 and the 470-server NVIDIA drivers

2021-08-12 Thread Alberto Milone

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Focal)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Hirsute)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu)
   Status: New => Triaged

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Focal)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Hirsute)
   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/1939673

Title:
  Update the 470 and the 470-server NVIDIA drivers

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


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

[Bug 1932559] Re: [MIR] oem-somerville-gendry-meta

2021-08-12 Thread Shih-Yuan Lee

** Changed in: oem-priority
 Assignee: OEM Taipei Jenkins Role Account (oem-taipei-bot) => Shih-Yuan 
Lee (fourdollars)

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

Title:
  [MIR] oem-somerville-gendry-meta

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


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

[Bug 1937914] Re: [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older kernel versions work

2021-08-12 Thread Launchpad Bug Tracker

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

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

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

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

Title:
  [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older
  kernel versions work

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


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

[Bug 1939160] Re: [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older kernel versions work (updated system log)

2021-08-12 Thread Launchpad Bug Tracker

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

** Changed in: linux-signed-hwe-5.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/1939160

Title:
  [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older
  kernel versions work (updated system log)

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


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

[Bug 1906970] Re: dpkg hook hostname error

2021-08-12 Thread Paride Legovini

This small patch is worth SRUing to Focal and Hirsute, I added tasks for
those.

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

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

** Also affects: postfix (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: sbuild (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** No longer affects: sbuild (Ubuntu Focal)

** No longer affects: sbuild (Ubuntu Hirsute)

** Changed in: postfix (Ubuntu Focal)
 Assignee: (unassigned) => Paride Legovini (paride)

** Changed in: postfix (Ubuntu Hirsute)
 Assignee: (unassigned) => Paride Legovini (paride)

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

** Changed in: postfix (Ubuntu Hirsute)
   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/1906970

Title:
  dpkg hook hostname error

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


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

[Bug 1939160] Re: [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older kernel versions work (updated system log)

2021-08-12 Thread Eugeny Bachar

Exact same behaviour for me and my collegues on HP Probook 450 G7:

HP ProBook 450 G7 (8VU58EA#ACB)
CPU: Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz
RAM: 16Gb
GPU: Intel UDH Graphics
Disk: SSD WDC PC SN520 SDAPNUW-512G-1006

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

Title:
  [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older
  kernel versions work (updated system log)

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


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

[Bug 1939676] [NEW] Scanning with clamtk does not work

2021-08-12 Thread Michał Krassowski

Public bug reported:

As reported in Debian bug tracker the essential clamtk functionality is
broken in version 6.03-1 https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=981384 - both scanning and analysing do not work
and end with a silent error with the following traceback:

***   FATAL: invalid GtkDialogFlags value no-separator, expecting: modal / 
GTK_DIALOG_MODAL, destroy-with-parent / GTK_DIALOG_DESTROY_WITH_PARENT, 
use-header-bar / GTK_DIALOG_USE_HEADER_BAR at /usr/share/perl5/Gtk3.pm line 
1136.
***  ignoring at /usr/share/perl5/Gtk3.pm line 572.

A fix was already released and the Debian team included the patch as
6.03-2. Would it be possible to backport the fix by syncing the package
with Debian 6.03-2 version for the Hirsute Hippo (and possibly further
back)?

I believe that this is an important bugfix as the current faulty
behaviour may make some users believe that the scan proceeded and no
issues were found when in fact it did not even begin due to an error in
handling of the GTK file picker.

** Affects: clamtk (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/1939676

Title:
  Scanning with clamtk does not work

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


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

[Bug 1938818] Re: Add support for packet-per-second policing

2021-08-12 Thread Stefan Bader

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

** Changed in: linux-bluefield (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: linux-bluefield (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux-bluefield (Ubuntu Focal)
 Assignee: (unassigned) => Bodong Wang (bodong-wang)

** Changed in: linux-bluefield (Ubuntu)
   Status: New => Invalid

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

Title:
  Add support for packet-per-second policing

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


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

[Bug 1939677] [NEW] oz test fails in impish with new libvirt 7.6

2021-08-12 Thread Christian Ehrhardt 

Public bug reported:

This was found when checking the new libvirt 7.6

https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-
service-4644/impish/amd64/o/oz/20210811_210304_40f24@/log.gz

It had various problems like:
>   raise libvirtError('virConnectOpen() failed')
E   libvirt.libvirtError: Failed to connect socket to 
'/home/ubuntu/.cache/libvirt/virtqemud-sock': No such file or directory

While trying to recreate this it did not happen again.
But instead I found

def test_init_guest():
guest = setup_guest(tdlxml2)

assert guest.disksize == 20
assert guest.image_name() == 'tester'
>   assert guest.output_image_path() == '/home/%s/.oz/images/tester.dsk' % 
> getpass.getuser()
E   AssertionError: assert '/var/lib/libvirt/images/tester.dsk' == 
'/home/root/.oz/images/tester.dsk'
E - /home/root/.oz/images/tester.dsk
E + /var/lib/libvirt/images/tester.dsk

That is due to our default of LIBVIRT_DEFAULT_URI=qemu:///system
But this worked in the past in autopkgtests
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/o/oz/20210723_190656_116de@/log.gztest_init_guest

Also it is independent, I can downgrade/upgrade between 7.4 / 7.6 and the issue 
remains.
I need to drive a bunch of VM based testing with/without PPA hoping that it 
will help to find what is broken.

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

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

** Also affects: libvirt (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/1939677

Title:
  oz test fails in impish with new libvirt 7.6

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


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

[Bug 1934014] Re: [SRU] Update amdgpu/renoir firmware

2021-08-12 Thread Timo Aaltonen

still missing verification

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

Title:
  [SRU] Update amdgpu/renoir firmware

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


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

[Bug 1939638] Re: [regression] USB device is not detected during boot

2021-08-12 Thread Chris Chiu

** Tags added: austin oem-priority originate-from-1939113

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

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

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

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

** Changed in: linux (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  [regression] USB device is not detected during boot

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


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

[Bug 1939413] Re: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0

2021-08-12 Thread Gunnar Hjalmarsson

Thanks for reporting this, Heinrich! It looks like protobuf needs to be
built with gcc-11.

** Changed in: protobuf (Ubuntu)
   Status: New => Fix Committed

** Changed in: protobuf (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

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

Title:
  /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version
  9.2 instead of the expected 11.0

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


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

[Bug 1939678] [NEW] Apache2 Balancer Manager not working after dist-upgrade to focal behind a Proxy

2021-08-12 Thread Horst Platz

Public bug reported:

Description: Ubuntu 20.04.2 LTS
Release: 20.04
Codename: focal

Approximately two years ago i creat the following bug report.

https://bugs.launchpad.net/apache2/+bug/1842701/

At the end talk to that bug report is a hin "that bug is still opend in
apache 2.4.41" and further on "it should be fixed in 2.4.42". mybe this is
now  forgotten to fix in focal and it is a regression bug or the
"(e.g. want to have it broken for better security)." ist happend.

any suggestion is appreciated

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-

To Reproduced i create two new Virtual Box VMs on my local Machine

 -
|Bastian Host |
|Apache Proxy | ---> LB Apache Balancer Manger
 -

Debian 10 -> Bastion Host (Proxy) / 192.168.56.90
Ubuntu 18.04 -> LB Manager / 192.168.56.160

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-

Ubuntu 18.04 with LB Manager

:~# apt-get install apache2

:~# dpkg -l | grep apache2
ii  apache22.4.29-1ubuntu4.16  amd64  Apache HTTP Server
ii  apache2-bin2.4.29-1ubuntu4.16  amd64  Apache HTTP Server (modules and 
other binary files)
ii  apache2-data   2.4.29-1ubuntu4.16  allApache HTTP Server (common files)
ii  apache2-utils  2.4.29-1ubuntu4.16  amd64  Apache HTTP Server (utility 
programs for web servers)

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-

:~# vim /etc/apache2/sites-available/management.conf

Servername 127.0.0.1
ServerAdmin root@localhost


SetHandler balancer-manager
Require local
#Require ip 192.168.56.0/24 127.0.0.1/24
Require all granted



SetHandler balancer-manager
Require local
#Require ip 192.168.56.0/24 127.0.0.1/24
Require all granted


LogLevel warn
ErrorLog ${APACHE_LOG_DIR}/management_error.log
CustomLog ${APACHE_LOG_DIR}/management_access.log combined



# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-

:~# vim /etc/apache2/sites-available/proxytest.conf

BalancerMember "http://192.168.168.130/test";
BalancerMember "http://192.168.168.131/test"; status=+H
ProxySet lbmethod=bybusyness



ServerAdmin root@localhost
ServerName testapp01
ServerAlias 127.0.0.1:8100

ProxyPass "/test" "balancer://test"
ProxyPassReverse "/test" "balancer://test"

CustomLog ${APACHE_LOG_DIR}/test-access.log combined
ErrorLog ${APACHE_LOG_DIR}/test-error.log



# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-

:~# a2enmod proxy_balancer proxy_http lbmethod_bybusyness lbmethod_byrequests
:~# a2ensite management proxytest

:~# vim /etc/apache2/ports.conf
[...]
Listen 81
Listen 8100

:~# systemctl restart apache2

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-

At that point i install also some console Browsers for testing.

:~# apt-get install lynx elinks

:~# tail -f /var/log/apache2/management_error.log

:~# elinks http://127.0.0.1:81/balancer-manager
:~# lynx http://127.0.0.1:81/balancer-manager

LB Manager -> "Edit worker settings for..." is visible and usable, no
error log entrys

-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -
-

Connect with firefox from outside

http://192.168.56.160:81/balancer-manager

LB Manager -> "Edit worker settings for..." is visible and usable, no
error log entrys

-

Create Debian 10 Proxy VM

:~# apt-get install apache2 lynx elinks

:~# dpkg -l | grep apache
ii  apache22.4.38-3+deb10u5  amd64  Apache HTTP Server
ii  apache2-bin2.4.38-3+deb10u5  amd64  Apache HTTP Server (modules and 
other binary files)
ii  apache2-data   2.4.38-3+deb10u5  allApache HTTP Server (common files)
ii  apache2-utils  2.4.38-3+deb10u5  amd64  Apache HTTP Server (utility 
programs for web servers)


Check from that VM that LB Manager is usable

:~# elinks 192.168.56.160:81/balancer-manager
:~# elinks 192.168.56.160:81/test-web01/balancer-manager

check direkt in Firefox
http://192.168.56.160:81/balancer-manager

:~# tail -f /var/log/apache2/management_error.log
LB Manager -> "Edit worker settings for..." is visible and usable, no error log 
entrys

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-

Create Proxy Config

~# vim /etc/apache2/sites-enabled/000-default.conf
[...]
   
ProxyPass http://192.168.56.160:81/test-web01
ProxyPassReverse http://192.168.56.160:81/test-web01
SetOutputFilter INFLATE;SUBSTITUTE
Substitute "s|http://192.168.56.90:81|http://192.168.56.160|i"
   
[...]

:~# a2enmod proxy_http substitute
:~# systemctl restart apache2


Check now over proxy config

:~# elinks 192.168.56.90/test-web01/balancer-manager
-> "E

[Bug 1939638] Re: [regression] USB device is not detected during boot

2021-08-12 Thread Chris Chiu

** Description changed:

+ [SRU Justification]
+ 
+ [Impact]
+ The USB devices (keyboard, storage...) are failed to be detected when 
connecting to the problematic root hubs which need longer PowerOn-to-PowerGood 
delay than it claims in the hub descriptor. It's caused by the upstream fix 
90d28fb53d4a ("usb: core: reduce power-on-good delay time of root hub").
+ 
+ 
+ [Fix]
+ Reverting the upstream fix until a formal fix been placed.
+ 
+ [Test Case]
+ 1. Plug the USB device to the ports of problematic root hub.
+ 2. Power on the machine.
+ 3. Check if the USB device can work or not after boot.
+ 
+ [Regression Potential]
+ Low. The longer delay is proven safe in old kernels.
+ 
+ == Original Bug Description ==
+ 
  [Summary]
  
  The USB devices (keyboard, storage...) are failed to be detected during boot 
after upgrade to UBUNTU focal kernel 5.4.0-78 and hirsute 5.11.0-26. However, 
they will be detected and working ok after re-plugging. The kernel output shows 
as down below during boot
  [ 39.350435] hub 1-0:1.0: USB hub found
  [ 39.398835] hub 1-0:1.0: 12 ports detected
  [ 39.622744] usb usb1-port3: couldn't allocate usb_device
  
  And when I plug out then plug in the same device, it shows
  [57210.794140] usb 1-3: new low-speed USB device number 4 using xhci_hcd
  [57210.951289] usb 1-3: New USB device found, idVendor=17ef, idProduct=6099, 
bcdDevice= 1.14
  [57210.951293] usb 1-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  
  After doing kernel bisecting, we found the upstream commit 
https://github.com/torvalds/linux/commit/90d28fb53d4a51299ff324dede015d5cb11b88a2
 makes the difference. It indicates that the delay for the root hub from 
power_on to power_good is not long enough. There was no problem if the delay is 
100 ms. From the Hub Descriptor of the root hub, the value is 10 * 2 
milliseconds. And the XHCI spec also says in section 5.4.8
  """
  The host is required to have power stable to the port within 20 milliseconds 
of the '0' to '1' transition of PP. If PPC = '1', software is responsible for 
waiting 20ms.
  """
  
  The commit seems to follow the SPEC but could cause problems on some
  hubs.
  
  [Reproduce Steps]
  1. Plug the USB device to the physical port #1 and #4 which belongs to 
high-speed hub.
  2. Power on the machine.
  3. Check if the USB device can work or not after boot.
  
  [Results]
  Expected:
-   All usb devices connect to the hub should work OK.
+   All usb devices connect to the hub should work OK.
  
  Actual:
-   USB devices connects to high-speed hub can not be probed.
+   USB devices connects to high-speed hub can not be probed.
  
  [Additional Information]
  Kernel Version: focal 5.4.0-78 and hirsute 5.11.0-26
  
  [Upstream bug]
  https://bugzilla.kernel.org/show_bug.cgi?id=214021

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

Title:
  [regression] USB device is not detected during boot

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


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

[Bug 1939457] Re: Update EoL dates for 16.04 LTS and 21.04 so they are not on weekends

2021-08-12 Thread Robie Basak

Hello Brian, or anyone else affected,

Accepted distro-info-data into hirsute-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/distro-
info-data/0.46ubuntu3 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-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. 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: distro-info-data (Ubuntu Hirsute)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-hirsute

** Changed in: distro-info-data (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/1939457

Title:
  Update EoL dates for 16.04 LTS and 21.04 so they are not on weekends

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1939457/+subscriptions


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

[Bug 1939457] Please test proposed package

2021-08-12 Thread Robie Basak

Hello Brian, or anyone else affected,

Accepted distro-info-data into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/distro-
info-data/0.43ubuntu1.6 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: distro-info-data (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: 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/1939457

Title:
  Update EoL dates for 16.04 LTS and 21.04 so they are not on weekends

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1939457/+subscriptions


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

[Bug 1939457] Please test proposed package

2021-08-12 Thread Robie Basak

Hello Brian, or anyone else affected,

Accepted distro-info-data into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/distro-
info-data/0.37ubuntu0.11 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: distro-info-data (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  Update EoL dates for 16.04 LTS and 21.04 so they are not on weekends

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1939457/+subscriptions


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

[Bug 1939457] Re: Update EoL dates for 16.04 LTS and 21.04 so they are not on weekends

2021-08-12 Thread Robie Basak

> How about we update the new release process document to indicate that
ubuntu.csv should be copied from the development release so that things
end up being consistent?

+1

> The packages need to be built in a PPA w/ -security and not -updates
which is not as trivial as just re-uploading the package to the queue.

I thought distro-info-data was an exception as it's trivially verifiable
that it's only shipping non-pocket-dependent CSVs? Either way, maybe we
can document the requirement here, too.

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

Title:
  Update EoL dates for 16.04 LTS and 21.04 so they are not on weekends

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1939457/+subscriptions


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

[Bug 1939457] Please test proposed package

2021-08-12 Thread Robie Basak

Hello Brian, or anyone else affected,

Accepted distro-info-data into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/distro-
info-data/0.28ubuntu0.18 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-
xenial to verification-done-xenial. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-xenial. 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/1939457

Title:
  Update EoL dates for 16.04 LTS and 21.04 so they are not on weekends

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1939457/+subscriptions


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

[Bug 1862372] Re: ubuntu-upload-permission TypeError crash

2021-08-12 Thread Paride Legovini

This doesn't seem to be fully fixed. On Focal and Impish:


$ ubuntu-upload-permission --list-uploaders cloud-init
All upload permissions for cloud-init:

Component (main)

* Ubuntu Core Development Team (ubuntu-core-dev) [team]

Packagesets
===

core:

ubuntu-cloud:
* Ubuntu Cloud Uploaders (ubuntu-cloud-uploaders) [team]
Traceback (most recent call last):
  File "/usr/bin/ubuntu-upload-permission", line 144, in 
main()
  File "/usr/bin/ubuntu-upload-permission", line 101, in main
ppu_uploaders = archive.getUploadersForPackage(
  File "/usr/lib/python3/dist-packages/ubuntutools/lp/lpapicache.py", line 746, 
in getUploadersForPackage
self._pkg_uploaders[source_package_name] = sorted(set(
TypeError: '<' not supported between instances of 'PersonTeam' and 'PersonTeam'


** Changed in: ubuntu-dev-tools (Ubuntu)
   Status: Fix Released => New

** Changed in: ubuntu-dev-tools (Ubuntu Focal)
   Status: Fix Released => New

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

Title:
  ubuntu-upload-permission TypeError crash

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


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

[Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

2021-08-12 Thread Pham Quoc Hung

Same issue for me. Bluetooth is one of the most annoying issues on Linux.
- OS: Ubuntu 20.04.1 LTS
- Kernel: 5.4.0-80-generic
- Machine: Dell precision M4700
- Headset: Sony WH-CH510

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

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


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

[Bug 1692671] Re: intel driver fails to reenable display

2021-08-12 Thread Alejandro Mery

it's been more than 4 years. nothing is the same as when this problem
happened

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

Title:
  intel driver fails to reenable display

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


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

[Bug 1939657] Re: install crashes

2021-08-12 Thread Chris Guiver

Thank you for taking the time to report this issue and helping to make
Ubuntu better.

This package failure looks like it was caused by bad ISO download,
corrupted install media, or device failure. eg. look in the logs and
you'll see messages like these :-

Aug 12 07:24:43 ubuntu kernel: [  242.141151] SQUASHFS error: zlib 
decompression failed, data probably corrupt
Aug 12 07:24:43 ubuntu kernel: [  242.141158] SQUASHFS error: 
squashfs_read_data failed to read block 0x2d7e90fe
Aug 12 07:24:43 ubuntu kernel: [  242.141424] SQUASHFS error: zlib 
decompression failed, data probably corrupt
Aug 12 07:24:43 ubuntu kernel: [  242.141427] SQUASHFS error: 
squashfs_read_data failed to read block 0x2d7e90fe

Examining the information it appears to be a bad ISO or faulty device
(inc. bad write-to-device). The bot reply refers to CD/DVD which refers
to whatever media you installed from (ie. applies even if using
HDD/SSD/thumb-drive/flash-memory-card/CD/DVD). I suggest you verify your
ISO download, and validate the write of ISO to install media before
trying to install.

Possibly useful:
- https://tutorials.ubuntu.com/tutorial/tutorial-how-to-verify-ubuntu#0
- https://help.ubuntu.com/community/Installation/CDIntegrityCheck

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

Title:
  install crashes

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


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

[Bug 1939293] Re: unable to load externals: undefined symbol "__pow_finite" and similar

2021-08-12 Thread Kaj Ailomaa

I'd also like to confirm that the package in -proposed fixes the bug.

Creating for example a [bonk~] now works fine.

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

Title:
  unable to load externals: undefined symbol "__pow_finite" and similar

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


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

[Bug 1870597] Re: libinput says: scheduled expiry is in the past... your system is too slow

2021-08-12 Thread P.Constantine

Looks like the incarnation of "intel gdm" bug to me, where pressing Alt would 
unfreeze everything.
But that time it's for NV and pressing Alt doesn't help at all.
The scenarios are the same though for me: any hard work done by JetBrains Idea 
and it freezes for some time.

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

Title:
  libinput says: scheduled expiry is in the past... your system is too
  slow

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


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

[Bug 1939673] Re: Update the 470 and the 470-server NVIDIA drivers

2021-08-12 Thread Alberto Milone

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Hirsute)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Hirsute)
   Importance: Undecided => Medium

** Description changed:

  Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic,
  Focal, Hirsute.
  
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.
  
  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/NVidiaUpdates
  
  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu
  
  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.
  
  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.
  
  [Discussion]
  
  [Changelog]
  
  == 470.57.02 (470-server) ==
  
-   *
+   * debian/nvidia_supported,
+ debian/rules (LP: #1939673):
+ - Use the json database file to generate the modaliases.
+ - Fix aliases generation.
+   We were not matching some of the aliases because of some missing
+   zeroes in the subdevice and subvendor ids.
+   * debian/pm-aliases-gen:
+ - Fix aliases generation for runtimepm.
+   We were not matching some of the aliases because of some missing
+   zeroes in the subdevice and subvendor ids.
+ 
+ == 470.63.01 (470) ==
+ 
+   * New upstream release (LP: #1939673):
+ - Added support for the following GPUs:
+ NVIDIA RTX A2000
+ - Fixed a Vulkan performance regression that affected rFactor2.
+   * debian/nvidia_supported,
+ debian/rules:
+ - Use the json database file to generate the modaliases.
+ - Fix aliases generation.
+   We were not matching some of the aliases because of some missing
+   zeroes in the subdevice and subvendor ids.
+   * debian/pm-aliases-gen:
+ - Fix aliases generation for runtimepm.
+   We were not matching some of the aliases because of some missing
+   zeroes in the subdevice and subvendor ids.

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

Title:
  Update the 470 and the 470-server NVIDIA drivers

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


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

[Bug 1939618] Re: EP11 cards going offline => Fix backport to U20.04LTS

2021-08-12 Thread Krzysztof Kozlowski

As Frank mentioned, the patches cannot be accepted in that form. There
is no information where these came from and what was changed in the
backport. This is a series of 33 commits, it's enormous. Are these all
fixes? Looks like not because only two patches have stable tags, +three
patches have Fixes tag. What's with the rest? Are they going to stable
trees?

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

Title:
  EP11 cards going offline => Fix backport to U20.04LTS

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


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

[Bug 1939222] Re: DisplayPort over USB-C not working after release update

2021-08-12 Thread Geri Joskowicz

Trying, but I'm stuck with the libc6 (>= 2.33) dependency. 
Install of 5.13 fails. 
Sorry

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

Title:
  DisplayPort over USB-C not working after release update

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


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

[Bug 1939618] Re: EP11 cards going offline => Fix backport to U20.04LTS

2021-08-12 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: Triaged => Incomplete

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

Title:
  EP11 cards going offline => Fix backport to U20.04LTS

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


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

[Bug 1931249] Re: btrfs filesystem - swapfile created leads to error - swap disabled

2021-08-12 Thread Vlad Orlov

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

** This bug has been marked a duplicate of bug 1818811
   The swapfile on the Btrfs file system is not activated

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

Title:
  btrfs filesystem - swapfile created leads to error - swap disabled

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


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

[Bug 1818811] Re: The swapfile on the Btrfs file system is not activated

2021-08-12 Thread Launchpad Bug Tracker

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

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

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

Title:
  The swapfile on the Btrfs file system is not activated

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


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

[Bug 1936240] Re: Sync to SGX 1.33.2

2021-08-12 Thread Tim Gardner

** Changed in: linux-azure (Ubuntu Groovy)
   Status: In Progress => Won't Fix

** Changed in: linux-azure (Ubuntu Groovy)
 Assignee: Tim Gardner (timg-tpi) => (unassigned)

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

Title:
  Sync to SGX 1.33.2

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


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

[Bug 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid

2021-08-12 Thread Launchpad Bug Tracker

This bug was fixed in the package openssh - 1:7.6p1-4ubuntu0.5

---
openssh (1:7.6p1-4ubuntu0.5) bionic-security; urgency=medium

  * SECURITY REGRESSION: User enumeration issue (LP: #1934501)
- debian/patches/CVE-2018-15473.patch: updated to fix bad patch
  backport.

 -- Marc Deslauriers   Wed, 11 Aug 2021
14:02:09 -0400

** Changed in: openssh (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-15473

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

Title:
  openssh tests use "not valid yet" certificate from 2020, which is now
  valid

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


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

[Bug 1813003] Re: Invalid free while running docker build

2021-08-12 Thread Athos Ribeiro

I tested this in a bionic lxc container with the following steps:

# install affected golang-docker-credential-helpers version 0.5.0-2
apt update && apt install -y docker.io golang-docker-credential-helpers
# prepare Dockerfile and run build
mkdir /tmp/dummy-docker-build
cd /tmp/dummy-docker-build
cat < Dockerfile
FROM ubuntu:focal
LABEL hello=label
EOF
docker build -t testing . # This will get the error to be reproduced.
# then we can enable -proposed and upgrade golang-docker-credential-helpers
cat

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

2021-08-12 Thread Maanus Kask

I installed the package from bionic-proposed and performed the test
cases using keepalived - VIP is not lost. This resolves it.

Thank you!

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

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

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


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

[Bug 1010737] Re: firefox no option to print double sided

2021-08-12 Thread madbiologist

Is this still occurring on Firefox 91?

** Changed in: firefox (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/1010737

Title:
  firefox no option to print double sided

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


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

[Bug 1936240] Re: Sync to SGX 1.33.2

2021-08-12 Thread Tim Gardner

https://lists.ubuntu.com/archives/kernel-team/2021-August/123118.html

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

Title:
  Sync to SGX 1.33.2

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


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

[Bug 1906970] Re: [SRU] dpkg hook hostname error

2021-08-12 Thread Paride Legovini

** Summary changed:

- dpkg hook hostname error
+ [SRU] dpkg hook hostname error

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

Title:
  [SRU] dpkg hook hostname error

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


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

[Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

2021-08-12 Thread bmaupin

I don't understand; doesn't the commit say it changed files?

> 6 files changed, 42 insertions(+), 18 deletions(-)

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

Title:
  Thinkpad T430u won't boot without noapic workaround

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


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

[Bug 1906970] Re: [SRU] dpkg hook hostname error

2021-08-12 Thread Paride Legovini

** Description changed:

+ [Impact]
+ 
+ /etc/resolv.cinf search domain with a leading dot cause postfix.postinst
+ to fail because it constructs a 'myhostname' with a duplicate dot.
+ 
+ The glibc resolver tolerates such domains and strips the leading dot
+ from the search domain [1]. This change makes postfix.postinst do the
+ same.
+ 
+ This same fix has been proposed for inclusion in Debian [2].
+ 
+ [1] 
https://sourceware.org/git/?p=glibc.git;a=blob;f=resolv/res_query.c;h=ebbe5a6a4ed86abe3fccd4a134bfcf6f613c9bbb;hb=HEAD#l411
+ [2] https://salsa.debian.org/postfix-team/postfix-dev/-/merge_requests/12
+ 
+ [Test Plan]
+ 
+ 1. Start an LXD container
+ 2. Edit /etc/resolv.conf and add search line like one of these:
+ 
+  search .
+  search .foo.bar
+  domain .foo.bar
+ 
+ 3. Install postfix from the archive, accept all the debconf defaults,
+and verify that postinst fails with a broken domain name.
+ 4. Purge postfix and install the version to test (e.g. from -proposed).
+ 5. Verify that the installation succeeds.
+ 6. Verify that `myhostname` in /etc/postfix/main.cf is sane.
+ 
+ [Regression Potential]
+ 
+ There is no reasonable case where a user could rely on a "broken" setup,
+ as its result is a postinst failure (= install failure) and an invalid
+ "myhostname" in main.cf.
+ 
+ The regression potential is negligible,
+ 
+ [Development Fix]
+ 
+ This is fixed already in the current devel release (Impish). This SRU
+ backports the very same fix to the stable releases.
+ 
+ [Original Description]
+ 
  I tried to install postfix (3.4.13-0ubuntu1) within a Dockerfile (Ubuntu
  20.04.01 LTS) and it failed because there is an error in the dpkg info
  file.
  
  I'm attaching the log of the 2nd time "apt install -y postfix" is
  executed, as it is way shorter and still shows the error message.
  
  ```
  root@cc1a572af0dc:/etc# apt install -y postfix
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  postfix is already the newest version (3.4.13-0ubuntu1).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up postfix (3.4.13-0ubuntu1) ...
  
  Postfix (main.cf) configuration was untouched.  If you need to make changes,
  edit /etc/postfix/main.cf (and others) as needed.  To view Postfix
  configuration values, see postconf(1).
  
  After modifying main.cf, be sure to run 'systemctl reload postfix'.
  
  Running newaliases
  newaliases: warning: valid_hostname: misplaced delimiter: cc1a572af0dc..
  newaliases: fatal: file /etc/postfix/main.cf: parameter myhostname: bad 
parameter value: cc1a572af0dc..
  dpkg: error processing package postfix (--configure):
   installed postfix package post-installation script subprocess returned error 
exit status 75
  Processing triggers for libc-bin (2.31-0ubuntu9.1) ...
  Errors were encountered while processing:
   postfix
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ```
  
  I then looked into the /etc/postfix/main.cf file and tried to manually
  change the hostname, but it automatically gets overwritten by dpkg when
  apt install is ran.
  
  After that I was able to track the issue into the script
  "/var/lib/dpkg/info/postfix.postinst" more exactly the sed command in
  line 52. It reads the content of the search parameter from
  /etc/resolv.conf, and concatenates it with a "." as delimiter with the
  hostname, but it doesn't honor the special case of "search ." and
  therefore constructs an incorrect myhostname parameter for postfix of
  "cc1a572af0dc..".
  
  I'd propose to remove this resolve.conf lookup entirely so that the package 
installation doesn't fail within docker containers...
  It is a bad practice in my opinion to overwrite existing config files upon 
package installation.
  Also I'd suggest not executing postfix after the configuration is written, so 
that in case of unforeseen circumstances (like this one) a user can just simply 
run a sed against the config file after installing the package.
  
  And the Dockerfile for reference:
  ```
  FROM ubuntu:latest
  
  ENV DEBIAN_FRONTEND=noninteractive
  #ENV DEBIAN_PRIORITY=low
  
  RUN apt update \
  && echo "postfix postfix/main_mailer_type select Internet Site" | 
debconf-set-selections \
  && echo "postfix postfix/mailname string mysubdomain.mydomain.com" | 
debconf-set-selections \
  && apt install -y postfix
  ```

** Description changed:

  [Impact]
  
  /etc/resolv.cinf search domain with a leading dot cause postfix.postinst
  to fail because it constructs a 'myhostname' with a duplicate dot.
  
  The glibc resolver tolerates such domains and strips the leading dot
  from the search domain [1]. This change makes postfix.postinst do the
  same.
  
  This same fix has been proposed for inclusion in Debian [2].
  
  [1] 
https://sourceware.org/git/?p=glibc.git;a=blob;f=resolv/res_query.c;h

[Bug 306003] Re: smartctl short test hangs at 90%

2021-08-12 Thread Austin

I can confirm this bug as well.

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename:   focal

Self-test execution status:  ( 249) Self-test routine in progress...
90% of test remaining.

Appears to be common for WD shucked drives. 
Ran across it on my wd 8 TB HDD WD80EMAZ-00WJTA0 (FW ver. 83.H0A83)
Some via CLI finished the smart test, some are hung, the ubuntu disk manager 
did not complete its scans either.

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

Title:
  smartctl short test hangs at 90%

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


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

[Bug 1939688] [NEW] »ubuntu-desktop« kann nicht installiert werden

2021-08-12 Thread Alexander Schaer

Public bug reported:

Es war nicht möglich, ein erforderliches Paket zu installieren. Bitte
melden Sie diesen Fehler, indem Sie im Terminal den Befehl »ubuntu-bug
ubuntu-release-upgrader-core« eingeben.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.44
ProcVersionSignature: Ubuntu 4.15.0-153.160-generic 4.15.18
Uname: Linux 4.15.0-153-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.24
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 12 14:27:09 2021
InstallationDate: Installed on 2017-12-23 (1327 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2021-08-12 (0 days ago)
VarLogDistupgradeTermlog:

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


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

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

Title:
  »ubuntu-desktop« kann nicht installiert werden

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


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

Re: [Bug 1900388] Re: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0

2021-08-12 Thread Daniel Gutson

I think this is a symptom of a bug which cause we don't know and need to
find out.

El jue., 12 ago. 2021 2:20 a. m., Kai-Heng Feng <1900...@bugs.launchpad.net>
escribió:

> So what we need to do is to lower the log level?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1900388
>
> Title:
>   blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ)
>   flags 0x80700 phys_seg 1 prio class 0
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ)
>   flags 0x80700 phys_seg 1 prio class 0
>
>   PIONEER BD-RW   BDR-205
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.10
>   Package: linux-image-5.8.0-23-generic 5.8.0-23.24
>   ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
>   Uname: Linux 5.8.0-23-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.20.11-0ubuntu50
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC2:  navycat2032 F pulseaudio
>/dev/snd/controlC0:  navycat2032 F pulseaudio
>/dev/snd/controlC1:  navycat2032 F pulseaudio
>   CasperMD5CheckResult: skip
>   Date: Mon Oct 19 10:11:53 2020
>   InstallationDate: Installed on 2020-10-07 (11 days ago)
>   InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64
> (20201007)
>   IwConfig:
>lono wireless extensions.
>
>eno1  no wireless extensions.
>   MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME
>   ProcFB: 0 EFI VGA
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-23-generic
> root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed ro quiet splash vt.handoff=7
>   PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
>   RelatedPackageVersions:
>linux-restricted-modules-5.8.0-23-generic N/A
>linux-backports-modules-5.8.0-23-generic  N/A
>linux-firmware1.190
>   RfKill:
>
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 04/09/2018
>   dmi.bios.release: 4.6
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 4.6.5
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: 150-SE-E789
>   dmi.board.vendor: EVGA
>   dmi.board.version: Patsburg
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:
>   dmi.product.family: X86 AT
>   dmi.product.name: MODEL_NAME
>   dmi.product.sku: PROJECT_SUB_TAG
>   dmi.product.version: BASE_BOARD_VERSION
>   dmi.sys.vendor: BASE_BOARD_MANUFACTURER
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900388/+subscriptions
>
>

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

Title:
  blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ)
  flags 0x80700 phys_seg 1 prio class 0

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


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

[Bug 1906970] Re: [SRU] dpkg hook hostname error

2021-08-12 Thread Paride Legovini

** Description changed:

  [Impact]
  
  /etc/resolv.cinf search domain with a leading dot cause postfix.postinst
  to fail because it constructs a 'myhostname' with a duplicate dot.
  
  The glibc resolver tolerates such domains and strips the leading dot
  from the search domain [1]. This change makes postfix.postinst do the
  same.
  
  This same fix has been proposed for inclusion in Debian [2].
  
  [1] 
https://sourceware.org/git/?p=glibc.git;a=blob;f=resolv/res_query.c;h=ebbe5a6a4ed86abe3fccd4a134bfcf6f613c9bbb;hb=HEAD#l411
  [2] https://salsa.debian.org/postfix-team/postfix-dev/-/merge_requests/12
  
  [Test Plan]
  
  1. Start an LXD container
  2. Edit /etc/resolv.conf and add search line like one of these:
  
   search .
   search .foo.bar
   domain .foo.bar
  
  3. Install postfix from the archive, accept all the debconf defaults,
     and verify that postinst fails with a broken domain name.
  4. Purge postfix and install the version to test (e.g. from -proposed).
  5. Verify that the installation succeeds.
  6. Verify that `myhostname` in /etc/postfix/main.cf is sane.
+ 
+ Test PPA: Test PPA:
+ https://launchpad.net/~paride/+archive/ubuntu/postfix-lp1906970
  
  [Regression Potential]
  
  There is no reasonable case where a user could rely on a "broken" setup,
  as its result is a postinst failure (= install failure) and an invalid
  "myhostname" in main.cf.
  
  The regression potential is negligible.
  
  [Development Fix]
  
  This is fixed already in the current devel release (Impish). This SRU
  backports the very same fix to the stable releases.
  
  [Original Description]
  
  I tried to install postfix (3.4.13-0ubuntu1) within a Dockerfile (Ubuntu
  20.04.01 LTS) and it failed because there is an error in the dpkg info
  file.
  
  I'm attaching the log of the 2nd time "apt install -y postfix" is
  executed, as it is way shorter and still shows the error message.
  
  ```
  root@cc1a572af0dc:/etc# apt install -y postfix
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  postfix is already the newest version (3.4.13-0ubuntu1).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up postfix (3.4.13-0ubuntu1) ...
  
  Postfix (main.cf) configuration was untouched.  If you need to make changes,
  edit /etc/postfix/main.cf (and others) as needed.  To view Postfix
  configuration values, see postconf(1).
  
  After modifying main.cf, be sure to run 'systemctl reload postfix'.
  
  Running newaliases
  newaliases: warning: valid_hostname: misplaced delimiter: cc1a572af0dc..
  newaliases: fatal: file /etc/postfix/main.cf: parameter myhostname: bad 
parameter value: cc1a572af0dc..
  dpkg: error processing package postfix (--configure):
   installed postfix package post-installation script subprocess returned error 
exit status 75
  Processing triggers for libc-bin (2.31-0ubuntu9.1) ...
  Errors were encountered while processing:
   postfix
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ```
  
  I then looked into the /etc/postfix/main.cf file and tried to manually
  change the hostname, but it automatically gets overwritten by dpkg when
  apt install is ran.
  
  After that I was able to track the issue into the script
  "/var/lib/dpkg/info/postfix.postinst" more exactly the sed command in
  line 52. It reads the content of the search parameter from
  /etc/resolv.conf, and concatenates it with a "." as delimiter with the
  hostname, but it doesn't honor the special case of "search ." and
  therefore constructs an incorrect myhostname parameter for postfix of
  "cc1a572af0dc..".
  
  I'd propose to remove this resolve.conf lookup entirely so that the package 
installation doesn't fail within docker containers...
  It is a bad practice in my opinion to overwrite existing config files upon 
package installation.
  Also I'd suggest not executing postfix after the configuration is written, so 
that in case of unforeseen circumstances (like this one) a user can just simply 
run a sed against the config file after installing the package.
  
  And the Dockerfile for reference:
  ```
  FROM ubuntu:latest
  
  ENV DEBIAN_FRONTEND=noninteractive
  #ENV DEBIAN_PRIORITY=low
  
  RUN apt update \
  && echo "postfix postfix/main_mailer_type select Internet Site" | 
debconf-set-selections \
  && echo "postfix postfix/mailname string mysubdomain.mydomain.com" | 
debconf-set-selections \
  && apt install -y postfix
  ```

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

Title:
  [SRU] dpkg hook hostname error

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


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

[Bug 1934501] Re: CVE-2018-15473 patch introduce user enumeration vulnerability

2021-08-12 Thread Marc Deslauriers

** Information type changed from Private Security to Public Security

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

Title:
  CVE-2018-15473 patch introduce user enumeration vulnerability

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


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

[Bug 1936894] Re: microvm is not the default type for qemu-system-x86_64-microvm >=qemu5.2

2021-08-12 Thread Christian Ehrhardt 

Fixed by
commit 3f9e518010693a98f23f50ea45f98837204c597e
Author: Michael Tokarev 
Date:   Tue Jul 20 08:56:48 2021 +0300

fix microvm default machine type for a new build system (LP#1936894)

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

Title:
  microvm is not the default type for qemu-system-x86_64-microvm
  >=qemu5.2

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


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

[Bug 1906970] Re: [SRU] dpkg hook hostname error

2021-08-12 Thread Paride Legovini

** Also affects: postfix (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: sbuild (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Changed in: postfix (Ubuntu Bionic)
 Assignee: (unassigned) => Paride Legovini (paride)

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

Title:
  [SRU] dpkg hook hostname error

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


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

[Bug 1906970] Re: [SRU] dpkg hook hostname error

2021-08-12 Thread Launchpad Bug Tracker

** Merge proposal linked:
   
https://code.launchpad.net/~paride/ubuntu/+source/postfix/+git/postfix/+merge/407020

** Merge proposal linked:
   
https://code.launchpad.net/~paride/ubuntu/+source/postfix/+git/postfix/+merge/407021

** Merge proposal linked:
   
https://code.launchpad.net/~paride/ubuntu/+source/postfix/+git/postfix/+merge/407022

** Merge proposal linked:
   
https://code.launchpad.net/~paride/ubuntu/+source/postfix/+git/postfix/+merge/407023

** Merge proposal linked:
   
https://code.launchpad.net/~paride/ubuntu/+source/postfix/+git/postfix/+merge/407024

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

Title:
  [SRU] dpkg hook hostname error

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


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

[Bug 1153517] Re: evince does not save filled PDF forms

2021-08-12 Thread madbiologist

** Tags added: raring

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

Title:
  evince does not save filled PDF forms

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


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

[Bug 1906970] Re: [SRU] dpkg hook hostname error

2021-08-12 Thread Paride Legovini

** No longer affects: sbuild (Ubuntu Bionic)

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

Title:
  [SRU] dpkg hook hostname error

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


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

[Bug 1939457] Autopkgtest regression report (distro-info-data/0.46ubuntu3)

2021-08-12 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted distro-info-data (0.46ubuntu3) for 
hirsute have finished running.
The following regressions have been reported in tests triggered by the package:

distro-info-data/0.46ubuntu3 (arm64, ppc64el, amd64, s390x, armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#distro-info-data

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Update EoL dates for 16.04 LTS and 21.04 so they are not on weekends

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1939457/+subscriptions


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

[Bug 1939638] Re: [regression] USB device is not detected during boot

2021-08-12 Thread Chris Chiu

https://lists.ubuntu.com/archives/kernel-team/2021-August/123129.html
https://lists.ubuntu.com/archives/kernel-team/2021-August/123130.html

sent to kernel mailing list

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

Title:
  [regression] USB device is not detected during boot

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


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

[Bug 1939399] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build

2021-08-12 Thread Jeffrey Pych

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

** This bug has been marked a duplicate of bug 1938978
nvidia-340 kernel module failed to build (ERROR: Kernel configuration is 
invalid)

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

Title:
  nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed
  to build

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


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

[Bug 1939671] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build

2021-08-12 Thread Jeffrey Pych

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

** This bug has been marked a duplicate of bug 1938978
nvidia-340 kernel module failed to build (ERROR: Kernel configuration is 
invalid)

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

Title:
  nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed
  to build

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


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

[Bug 1938408] Re: EHL board does not support soft reboot

2021-08-12 Thread Ubuntu Kernel Bot

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


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

Title:
  EHL board does not support soft reboot

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


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

[Bug 1938413] Re: Shutdown hangs on EHL board

2021-08-12 Thread Ubuntu Kernel Bot

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


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

Title:
  Shutdown hangs on EHL board

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


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

[Bug 1929902] Re: [EHL] enable USB-dw3

2021-08-12 Thread Ubuntu Kernel Bot

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


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

Title:
  [EHL] enable USB-dw3

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


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

[Bug 1929892] Re: [TGL] enable USB-dw3

2021-08-12 Thread Ubuntu Kernel Bot

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


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

Title:
  [TGL] enable USB-dw3

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


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

[Bug 1939577] Re: Missing dependency in libvirt-guests.service leads sometimes to killed VMs on host shutdown

2021-08-12 Thread Paride Legovini

Hello Helmut and thanks for this bug report. From my testing libvirt VMs
do not automatically get registered to machined (they are not listed by
`systemctl list-machines`), and indeed machined, not "owning" then,
doesn't seem to touch them at shutdown.

To better understand your issue here and verify this is actually a bug
in Ubuntu and not a local configuration issue we need more details on
how you start the affected VMs. Could you please provide a minimal set
of steps to reproduce the issue from a clean Ubuntu system?

I can't exclude that libvirt doesn't play well with machined in some
cases, but should this behavior given by how libvirt behaves and not by
how it's distributed in Ubuntu then my suggestion here is to file a bug
upstream:

  https://gitlab.com/libvirt/libvirt/-/issues

Waiting for your reply here I'm marking this bug report as Incomplete.

** Changed in: libvirt (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/1939577

Title:
  Missing dependency in libvirt-guests.service leads sometimes to killed
  VMs on host shutdown

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


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

[Bug 1939640] Re: libvpx FTBFS with LTO enabled

2021-08-12 Thread Sergio Durigan Junior

** Changed in: lto-disabled-list (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

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

Title:
  libvpx FTBFS with LTO enabled

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


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

[Bug 1939352] Re: FTBFS 4.13-10ubuntu3 error: ‘numeric_limits’ is not a member of ‘std’

2021-08-12 Thread Paride Legovini

I can reproduce the ftbfs locally with sbuild. Tried to cherry-pick the
patch linked by Amos, which applies cleanly, but the build still fails:

Icmp4.cc: In member function ‘Icmp4::SendEcho(Ip::Address&, int, char const*, 
int)’:
Icmp4.cc:116:11: error: array subscript ‘struct icmpEchoData[0]’ is partly 
outside array bounds of ‘char[282]’ [-Werror=array-bounds]
  116 | echo->opcode = (unsigned char) opcode;
  | ~~^~
In file included from ../../include/squid.h:87,
 from Icmp4.cc:13:
Icmp4.cc:87:23: note: while referencing ‘Icmp4::SendEcho(Ip::Address&, int, 
char const*, int)::pkt’
   87 | LOCAL_ARRAY(char, pkt, MAX_PKT4_SZ);
  |   ^~~
cc1plus: all warnings being treated as errors
make[5]: *** [Makefile:959: Icmp6.o] Error 1
make[5]: *** Waiting for unfinished jobs
cc1plus: all warnings being treated as errors
make[5]: *** [Makefile:959: Icmp4.o] Error 1

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

Title:
  FTBFS 4.13-10ubuntu3 error: ‘numeric_limits’ is not a member of ‘std’

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


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

[Bug 1938920] Re: [SRU] Update to netplan.io 0.103

2021-08-12 Thread Łukasz Zemczak

I think Robie has a point here. I think there were times where we 'JFDI'
regarding backporting everything along with deprecation messages, but
mainly because we weren't really aware or missed it during review. I
don't have a strong opinion, since this is just a deprecation warning so
my personal feeling regarding that is that it doesn't really matter much
- but we need to be always considerate of never breaking existing
configurations for a series for sure. So at least once at some moment of
time we decide to deprecate this completely, we need to make sure not to
change it for focal users. That being said, this will probably not be a
problem since we won't do it before the next LTS and we only really
support one LTS back.

Anyway, maybe just removing the deprecation notice as a delta for
focal/hirsute could be an option?

And +1 on getting a hirsute upload prepared. I suppose the focal one is
also not completely up-to-date as it seems to be ubuntu2 while impish
has ubuntu3?

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

Title:
  [SRU] Update to netplan.io 0.103

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


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

[Bug 1939640] Re: libvpx FTBFS with LTO enabled

2021-08-12 Thread Sergio Durigan Junior

This patch adds libvpx to the lto-disabled-list package, thus working
around the problem and disabling LTO for libvpx.

** Patch added: "fix-ftbfs-libvpx-lto.patch"
   
https://bugs.launchpad.net/ubuntu/+source/lto-disabled-list/+bug/1939640/+attachment/5517532/+files/fix-ftbfs-libvpx-lto.patch

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

Title:
  libvpx FTBFS with LTO enabled

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


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

[Bug 1818811] Re: The swapfile on the Btrfs file system is not activated

2021-08-12 Thread Norbert

Latest Ubuntu MATE 21.10 20210812 - btrfs rootfs, swapfile is not
attached (output of `swapon -s` is empty).

** Also affects: ubuntu-mate
   Importance: Undecided
   Status: New

** Tags removed: disco
** Tags added: impish iso-testing

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

Title:
  The swapfile on the Btrfs file system is not activated

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


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

[Bug 1939708] [NEW] Impish update: v5.13.10 upstream stable release

2021-08-12 Thread Kamal Mostafa

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.13.10 upstream stable release
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Impish)
   Importance: Undecided
   Status: Confirmed

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

Title:
  Impish update: v5.13.10 upstream stable release

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


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

1 2 3 4 >

1 - 100 of 328 matches

Mail list logo