[Bug 1935709] Re: grpc++-dev doesn't install gRPCConfig.cmake

[Ken Dreyer (Red Hat)]

Also reported at
https://bugs.launchpad.net/ubuntu/+source/grpc/+bug/2019881

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

Title:
  grpc++-dev doesn't install gRPCConfig.cmake

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


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

[Bug 2019881] Re: Dev package does not contain cmake files

[Ken Dreyer (Red Hat)]

See also https://bugs.launchpad.net/ubuntu/+source/grpc/+bug/1935709

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

Title:
  Dev package does not contain cmake files

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


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

[Bug 1963934] Re: Audio device not detected after pipewire update

[Red Green]

I can confirm the solution you found making the
/usr/share/pipewire/media-session.d/with-pulseaudio file allows the
pipewire to function again. I would think it is time for new upload
including the required file so this package functions correctly again.

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

Title:
  Audio device not detected after pipewire update

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


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

[Bug 1865900] Re: apache 2.4.29-1ubuntu4.12 authentication with client certificate broken

[Ken Dreyer (Red Hat)]

Focal's curl 7.68.0-1ubuntu2.6 now supports post-handshake client
authentication.

curl \
  --tls-max 1.2 \
  --cacert ~/.koji/pki/koji-ca.crt \
  --cert ~/koji-ansible/koji-tools/admin.crt \
  --key ~/koji-ansible/koji-tools/admin.key \
  https://localhost/kojihub/ssllogin

However, python-requests on Focal or Groovy still cannot do post-
handshake client auth with the default SSLProtocol setting. Sample
Python script:

  import requests

  r = requests.get('https://localhost/kojihub/ssllogin',
   verify='.koji/pki/koji-ca.crt',
   cert=('koji-ansible/koji-tools/admin.crt',
 'koji-ansible/koji-tools/admin.key'))
  r.raise_for_status()

 The Apache error logs say:

  [ssl:error] AH10158: cannot perform post-handshake authentication
  [ssl:error] SSL Library Error: error:14268117:SSL  
routines:SSL_verify_client_post_handshake:extension not received

Applying
https://github.com/psf/requests/commit/db47b9b4a0c5877fb97f64ac442757604c4c45cc
or updating to hirsute's python3-requests_2.25.1+dfsg-2 does work.

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

Title:
  apache 2.4.29-1ubuntu4.12 authentication with client certificate
  broken

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


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

[Bug 1882671] Re: unbalanced UEFI TPL manipulations in iPXE with DOWNLOAD_PROTO_HTTPS enabled

[Laszlo Ersek (Red Hat)]

Per comment #32, fixed in upstream iPXE commit 2ae5d4338, setting ticket
status for iPXE to "Fix Committed".

** Changed in: ipxe
   Status: New => Fix Committed

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

Title:
  unbalanced UEFI TPL manipulations in iPXE with DOWNLOAD_PROTO_HTTPS
  enabled

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

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

[Bug 1888133] [NEW] package libpam-systemd:amd64 204-5ubuntu20.24 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100

[Red Willoughby]

Public bug reported:

This happened immediately after booting a Live CD for GNUradio.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libpam-systemd:amd64 204-5ubuntu20.24
ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5
Uname: Linux 3.19.0-28-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.24
Architecture: amd64
CasperVersion: 1.340.2
Date: Sat Apr 22 23:25:15 2017
Df:
 Filesystem 1K-blocks  Used Available Use% Mounted on
 udev 1992364 0   1992364   0% /dev
DuplicateSignature: package:libpam-systemd:amd64:204-5ubuntu20.24:subprocess 
installed post-installation script returned error exit status 100
ErrorMessage: subprocess installed post-installation script returned error exit 
status 100
LiveMediaBuild: LilacSats 14.04 - Release amd64
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: systemd
Title: package libpam-systemd:amd64 204-5ubuntu20.24 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 100
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check trusty

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

Title:
  package libpam-systemd:amd64 204-5ubuntu20.24 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 100

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

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

[Bug 1882671] Re: unbalanced UEFI TPL manipulations in iPXE with DOWNLOAD_PROTO_HTTPS enabled

[Laszlo Ersek (Red Hat)]

Hi Michael, thank you for the fix, and for mentioning it here. I didn't
ignore your comment 32 when I was writing what would become comments 33
and 34 -- I think we must have been writing our comments in parallel,
and I simply didn't see yours.

Christian, now you should be able to resolve this LP ticket without
modifying anything on the packaging side, by backporting upstream iPXE
commit 2ae5d4338.

Thanks!

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

Title:
  unbalanced UEFI TPL manipulations in iPXE with DOWNLOAD_PROTO_HTTPS
  enabled

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

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

[Bug 1882671] Re: unbalanced UEFI TPL manipulations in iPXE with DOWNLOAD_PROTO_HTTPS enabled

[Laszlo Ersek (Red Hat)]

Sorry about the malformed table in comment 33 -- that's not my doing. I
laid it out correctly; Launchpad messed it up by squeezing whitespace.
Here it is again, using dots rather than spaces.

Ubuntu.release..edk2.HTTPS.enabled..iPXE.HTTPS.enabled..iPXE.TPL.regression
--..--..--..---
Bionic..no..no.
Focal...no..yes.yes
Groovy..yes.(bug.1883114)...no.(this.bug)...masked.(this.bug)..

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

Title:
  unbalanced UEFI TPL manipulations in iPXE with DOWNLOAD_PROTO_HTTPS
  enabled

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

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

[Bug 1882671] Re: unbalanced UEFI TPL manipulations in iPXE with DOWNLOAD_PROTO_HTTPS enabled

[Laszlo Ersek (Red Hat)]

Hello Christian,

For *some* form of UEFI HTTPS boot, you have to enable *at least one* of
the {edk2, iPXE} HTTPS stacks. I'm unfamiliar with the Ubuntu releases,
but my understanding is the following:

Ubuntu release  edk2 HTTPS enabled  iPXE HTTPS enabled  iPXE TPL regression
--  --  --  ---
Bionic  no  no
Focal   no  yes yes
Groovy  yes (bug 1883114)   no (this bug)   masked (this bug)

In Groovy, you can work around the iPXE TPL regression by disabling the
iPXE HTTPS stack (i.e., in the efi-e1000e option ROM). Because, you can
effectively "replace" it with the edk2 HTTPS stack in the platform
firmware (in the OVMF binary), per bug 1883114.

In Focal, if you do the same to iPXE, you can't fall back to the edk2
HTTPS stack in OVMF -- because bug 1883114 is out of scope for Focal,
AIUI.

However, disabling the iPXE HTTPS stack in Focal would not cause a
regression, in my opinion. That's because in Focal you can't boot the
"OVMF + efi-e1000e" combination *at all* -- you don't get far enough in
the boot process to even *attempt* HTTPS boot (or a boot from another
kind of media, for that matter).

Thus in Focal, no form of *UEFI boot* (HTTPS or otherwise) has ever
worked, so there's nothing to regress by disabling the iPXE HTTPS stack
in "efi-e1000e.rom".

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

Title:
  unbalanced UEFI TPL manipulations in iPXE with DOWNLOAD_PROTO_HTTPS
  enabled

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

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

[Bug 1882671] Re: unbalanced UEFI TPL manipulations in iPXE with DOWNLOAD_PROTO_HTTPS enabled

[Laszlo Ersek (Red Hat)]

Christian,

> But it seems for legacy roms like 82540em.rom CONFIG=qemu being set or not 
> doesn't make a
> difference.

(1) That's my understanding as well; from the following original iPXE
commits anyway:

- a15c0d7e868a ("[efi] Allow user experience to be downgraded", 2015-07-22),
- a200ad462e69 ("[build] Add named configuration for qemu", 2015-07-22).

(I played a part in those commits existing.)

(2) However, just to be 100% sure, I recommend *not* changing the
CONFIG= setting for the traditional BIOS build. If you have
had CONFIG=qemu there, then keep it. If you haven't, then don't add it
now.

What matters is that the EFI build be performed with CONFIG=qemu.

(FWIW, last time I looked, in RHEL downstream we used to build iPXE with
CONFIG=qemu covering *both* the traditional BIOS image and the EFI
image. But, I don't think that's enough reason for you to diverge now
from your previous BIOS image settings in Ubuntu. I don't think you
should risk regressions with that. Really, what matters is that the EFI
image be built with CONFIG=qemu.)

Thanks
Laszlo

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

Title:
  unbalanced UEFI TPL manipulations in iPXE with DOWNLOAD_PROTO_HTTPS
  enabled

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

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

[Bug 1882671] Re: unbalanced UEFI TPL manipulations in iPXE with DOWNLOAD_PROTO_HTTPS enabled

[Laszlo Ersek (Red Hat)]

I used

qemu-system-x86_64 \
  -enable-kvm \
  -monitor stdio \
  -drive if=pflash,snapshot=on,format=raw,file=OVMF.fd \
  -global e1000.romfile=82540em.combined.rom \
  -debugcon file:debug.log \
  -global isa-debugcon.iobase=0x402

where "OVMF.fd" was built from edk2 at then-master (14c7ed8b51f6 -- see
comment 7), and "82540em.combined.rom" is the combined oprom (with HTTPS
enabled in the EFI driver too) built from the problematic iPXE
version(s).

OVMF was built with "-b DEBUG". ("-b RELEASE" would remove the ASSERT()s
from the firmware modules.)

"debug.log" captures the firmware debug output. That's the file that
ends with the ASSERT failure seen in comment 4.

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

Title:
  unbalanced UEFI TPL manipulations in iPXE with DOWNLOAD_PROTO_HTTPS
  enabled

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

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

[Bug 1882671] Re: unbalanced UEFI TPL manipulations in iPXE with DOWNLOAD_PROTO_HTTPS enabled

[Laszlo Ersek (Red Hat)]

Christian,

what you describe seems to be exactly what I propose. Namely:
- build "82540em.rom" with HTTPS enabled,
- build "82540em.efirom" with CONFIG=qemu, and HTTPS disabled,
- create a combined option ROM image from the above two, using "catrom.pl".

Thanks
Laszlo

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

Title:
  unbalanced UEFI TPL manipulations in iPXE with DOWNLOAD_PROTO_HTTPS
  enabled

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

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

[Bug 1882671] Re: unbalanced UEFI TPL manipulations in iPXE with DOWNLOAD_PROTO_HTTPS enabled

[Laszlo Ersek (Red Hat)]

Christian,

you can enable DOWNLOAD_PROTO_HTTPS in the traditional BIOS image built
from iPXE, and disable it in the UEFI driver built from iPXE. You can
still combine both drivers into a combined option ROM. For SeaBIOS
guests, there's not going to be any change.

For UEFI guests, see my comment#7 -- you don't need the iPXE HTTPS
implementation, because OVMF already contains the edk2 HTTPS BOOT
feature (assuming you build OVMF with "-D NETWORK_HTTP_BOOT_ENABLE -D
NETWORK_TLS_ENABLE"). The whole point of CONFIG=qemu is to strip the
UEFI build of iPXE to a mere Simple Network Protocol driver. Such a
build provides only the lowest level hardware abstraction for UEFI, and
the rest (IPv[46], TCP/UDP, DHCP, PXE, TFTP, HTTP(S)) are provided on
top by the edk2 implementations of various standard UEFI interfaces.

If you want to run a full-featured iPXE build on a UEFI machine
(including: in an OVMF guest), you still can, of course; lots of people
do that, for good reasons. But that use case is best served by the
*standalone UEFI application* build of iPXE (produced at "bin-
x86_64-efi/ipxe.efi" by "make"). The UEFI *driver* build of iPXE should
be as minimal as possible, in comparison -- just provide SNP for the
desired NIC models.

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

Title:
  unbalanced UEFI TPL manipulations in iPXE with DOWNLOAD_PROTO_HTTPS
  enabled

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

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

[Bug 1882671] Re: unbalanced UEFI TPL manipulations in iPXE with DOWNLOAD_PROTO_HTTPS enabled

[Laszlo Ersek (Red Hat)]

Vlad,

you could subscribe to ipxe-devel at
, wait until it's
confirmed (I think it's automatic, so no moderator approval is needed
for subscribing), and then resend your message. You can even stay
subscribed -- if you don't want to get the ipxe-devel list traffic, you
can click "unsubscribe or edit options", and then "disable mail
delivery" (which is *different* from unsubscribing). That way you'd
remain a subscriber (so you could post at any time), but you wouldn't
get the general list traffic.

hth
Laszlo

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

Title:
  unbalanced UEFI TPL manipulations in iPXE with DOWNLOAD_PROTO_HTTPS
  enabled

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

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

[Bug 1882671] Re: unbalanced UEFI TPL manipulations in iPXE with DOWNLOAD_PROTO_HTTPS enabled

[Laszlo Ersek (Red Hat)]

** Summary changed:

- qemu-system-x86_64 (ver 4.2) stuck at boot with OVMF bios
+ unbalanced UEFI TPL manipulations in iPXE with DOWNLOAD_PROTO_HTTPS enabled

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

Title:
  unbalanced UEFI TPL manipulations in iPXE with DOWNLOAD_PROTO_HTTPS
  enabled

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

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

[Bug 1882671] Re: qemu-system-x86_64 (ver 4.2) stuck at boot with OVMF bios

[Laszlo Ersek (Red Hat)]

Hi Vlad,

the ipxe-qemu package in Ubuntu (1.0.0+git-20190109.133f4c4-0ubuntu3) is
built with DOWNLOAD_PROTO_HTTPS enabled (in "src/config/general.h").
According to the Ubuntu changelog, this is a new feature added in
"1.0.0+git-20190109.133f4c4-0ubuntu1".

With DOWNLOAD_PROTO_HTTPS enabled, I can reproduce the issue locally,
with iPXE built from source at git commit 133f4c4 (which you report the
issue for), and also at current iPXE master (9ee70fb95bc2).

The issue does not reproduce (with DOWNLOAD_PROTO_HTTPS enabled) at
commit fbe8c52d. This suggests the problem should be bisectable.

If I disable DOWNLOAD_PROTO_HTTPS, then the problem goes away even at
133f4c4 (i.e., the issue is masked).

I've used current edk2 master to test with (14c7ed8b51f6).

Viewed at 133f4c4:

The DOWNLOAD_PROTO_HTTPS feature test macro seems to result in iPXE
attempting to gather entropy. (Likely for setting up TLS connections.)
For entropy gathering, iPXE seems to use an EFI timer, and to measure
jitter across one timer tick. In this, iPXE plays some tricks with the
UEFI TPL (Task Priority Level).

In general, iPXE seems to want to run at TPL_CALLBACK most of the time,
to mask the timer interrupt in most code locations, and drops down to
TPL_APPLICATION only when it actively wants a timer callback (for the
jitter collection, see above).

When the iPXE driver is launched, the StartImage() UEFI boot service
takes a note of the current TPL. It is TPL_APPLICATION (value 4). Then
iPXE seems to perform the above trickery with TPL_CALLBACK & entropy
collection. Finally, after installing EfiDriverBindingProtocol and
EfiComponentName2Protocol, the iPXE driver exits (as expected from a
UEFI driver model driver -- the entry point function is only supposed to
perform some setup steps & install some protocol interfaces). At this
point, StartImage() verifies whether the TPL has been restored to the
same as it was before launching the driver.

Unfortunately, something about the TPL manipulations in iPXE is
unbalanced, because I see the following TPL changes:

- raise: APPLICATION (4) -> CALLBACK (8)
- raise: CALLBACK (8) -> NOTIFY (16)
- raise: NOTIFY (16) -> NOTIFY (16)
- restore: NOTIFY (16) -> NOTIFY (16)
- restore: NOTIFY (16) -> CALLBACK (8)

Note that the final "restore: CALLBACK (8) -> APPLICATION (4)"
transition is missing, before iPXE exits. This is what StartImage()
catches and reports with the failed ASSERT().

So, as I mentioned, the problem is bisectable. Here's the bisection log:

> git bisect start
> # bad: [9ee70fb95bc266885ff88be228b044a2bb226eeb] [efi] Attempt to
> # connect our driver directly if ConnectController fails
> git bisect bad 9ee70fb95bc266885ff88be228b044a2bb226eeb
> # bad: [133f4c47baef6002b2ccb4904a035cda2303c6e5] [build] Handle
> # R_X86_64_PLT32 from binutils 2.31
> git bisect bad 133f4c47baef6002b2ccb4904a035cda2303c6e5
> # good: [fbe8c52d0d9cdb3d6f5fe8be8edab54618becc1f] [ena] Fix spurious
> # uninitialised variable warning on older versions of gcc
> git bisect good fbe8c52d0d9cdb3d6f5fe8be8edab54618becc1f
> # bad: [bc85368cdd311fe68ffcf251e7e8e90c14f8a9dc] [librm] Ensure that
> # inline code symbols are unique
> git bisect bad bc85368cdd311fe68ffcf251e7e8e90c14f8a9dc
> # bad: [0778418e29ea16fc897fc5b6e497054f5ba86ebd] [golan] Do not
> # assume all devices are identical
> git bisect bad 0778418e29ea16fc897fc5b6e497054f5ba86ebd
> # good: [f672a27b34220865b403df519593f382859559e0] [efi] Raise TPL
> # within EFI_USB_IO_PROTOCOL entry points
> git bisect good f672a27b34220865b403df519593f382859559e0
> # bad: [d8c500b7945e57023dde5bd0be2b0e40963315d9] [efi] Drop to
> # TPL_APPLICATION when gathering entropy
> git bisect bad d8c500b7945e57023dde5bd0be2b0e40963315d9
> # good: [c84f9d67272beaed98f98bf308471df16340a3be] [iscsi] Parse IPv6
> # address in root path
> git bisect good c84f9d67272beaed98f98bf308471df16340a3be
> # first bad commit: [d8c500b7945e57023dde5bd0be2b0e40963315d9] [efi]
> # Drop to TPL_APPLICATION when gathering entropy

The bisection fingers d8c500b7945e ("[efi] Drop to TPL_APPLICATION when
 gathering entropy", 2018-03-12) as first bad commit.

Feel free to report this problem on the upstream iPXE mailing list.

Regarding Ubuntu downstream, you should be able to work around this
issue by #undef-ing DOWNLOAD_PROTO_HTTPS again, in
"src/config/general.h" -- *minimally* in the CONFIG=qemu build(s). That
is, in the ipxe-qemu subpackage.

That's because in a CONFIG=qemu build, you totally don't need (or even
*use*) the iPXE HTTPS infrastructure (the entropy gathering that trips
the ASSERT seems spurious to me, with CONFIG=qemu). With CONFIG=qemu,
iPXE provides the UEFI SNP (Simple Network Protocol) interface on top of
the e1000 NIC, and the crypto stuff (if any) is done by the platform
firmware (edk2 / OVMF).



** Project changed: qemu => ipxe

** Package changed: qemu (Ubuntu) => ipxe (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed 

[Bug 1882671] Re: qemu-system-x86_64 (ver 4.2) stuck at boot with OVMF bios

[Laszlo Ersek (Red Hat)]

(From the UEFI executable name "82540em.efi" in the log, I initially
suspected an assigned physical NIC with a buggy flashed-on oprom. But
grepping the iPXE tree for "82540em" yields a match, and QEMU loads the
iPXE oproms by default into the emulated NICs' ROM BARs.)

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

Title:
  qemu-system-x86_64 (ver 4.2) stuck at boot with OVMF bios

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

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

[Bug 1882671] Re: qemu-system-x86_64 (ver 4.2) stuck at boot with OVMF bios

[Laszlo Ersek (Red Hat)]

Vladislav,

The OVMF debug log ends like this (with UEFI protocol GUIDs decoded as
their textual identifiers in edk2):

> [Security] 3rd party image[6D19D18] can be loaded after EndOfDxe: 
> PciRoot(0x0)/Pci(0x3,0x0)/Offset(0x16400,0x4B1FF).
> InstallProtocolInterface: [EfiLoadedImageProtocol] 6D187C0
> Loading driver at 0x6B1F000 EntryPoint=0x6B25497 82540em.efi
> InstallProtocolInterface: [EfiLoadedImageDevicePathProtocol] 6D18498
> ProtectUefiImageCommon - 0x6D187C0
>   - 0x06B1F000 - 0x000B6E60
> InstallProtocolInterface: [EfiDriverBindingProtocol] 6B50C00
> InstallProtocolInterface: [EfiComponentName2Protocol] 6B50BD0
> ASSERT 
> /home/jenkins/workspace/edk2/rpms/build/edk2-g6ff7c838d0/MdeModulePkg/Core/Dxe/Image/Image.c(1676):
>  Image->Tpl == gEfiCurrentTpl

This final log snippet confirms that a UEFI device driver called
"82540em.efi" is being loaded and started from the option ROM BAR of the
PCI device that is at slot 3, function 0, of the root bridge.

When this UEFI device driver is started, it trips an assert in the
platform firmware. Namely, in the CoreStartImage() function in the
"MdeModulePkg/Core/Dxe/Image/Image.c" source file of edk2:

  //
  // Image has completed.  Verify the tpl is the same
  //
  ASSERT (Image->Tpl == gEfiCurrentTpl);

This suggests that the "82540em.efi" driver exits its entry point
function after having raised, but not having restored, the TPL (Task
Priority Level). In other words, the symptom indicates a bug in the UEFI
driver.

I *suspect* (but am not sure) that you are using an e1000 emulated NIC,
and the "82540em.efi" driver exposed in its oprom comes from the iPXE
project:

src/drivers/net/intel.c:PCI_ROM ( 0x8086, 0x100e, "82540em",
"82540EM", 0 ),

Therefore I suspect a bug in the iPXE version that the Ubuntu 20.04
upgrade brought to you.

(I can see a number of TPL-related patches in the iPXE git history,
around Feb-Mar 2018. And QEMU loads the iPXE oprom into the emulated
NICs ROM BAR.)

Please try installing different versions of the iPXE package on your
Ubuntu host, and re-run your test (without changing any other elements
of your setup).

Thanks.

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

Title:
  qemu-system-x86_64 (ver 4.2) stuck at boot with OVMF bios

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

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

[Bug 1882671] Re: qemu-system-x86_64 (ver 4.2) stuck at boot with OVMF bios

[Laszlo Ersek (Red Hat)]

Please add

  -debugcon file:debug.log -global isa-debugcon.iobase=0x402

to the QEMU cmdline, and attach "debug.log". Thanks.

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

Title:
  qemu-system-x86_64 (ver 4.2) stuck at boot with OVMF bios

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

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

[Bug 1875016] Re: Driver doesn't work on Ubuntu 20.04

[red]

Is there anything new on this topic?

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

Title:
  Driver doesn't work on Ubuntu 20.04

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

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

[Bug 1865900] Re: apache 2.4.29-1ubuntu4.12 authentication with client certificate broken

[Ken Dreyer (Red Hat)]

"SSLProtocol all -SSLv3" is in the default /etc/apache2/mods-
enabled/ssl.conf. Why does the behavior change when I set "SSLProtocol
TLSv1.3 TLSv1.2"?

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

Title:
  apache 2.4.29-1ubuntu4.12 authentication with client certificate
  broken

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

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

[Bug 1865900] Re: apache 2.4.29-1ubuntu4.12 authentication with client certificate broken

[Ken Dreyer (Red Hat)]

With Bionic's apache 2.4.29-1ubuntu4.12:

"SSLProtocol TLSv1.3 TLSv1.2" - works
"SSLProtocol TLSv1.3 +TLSv1.2" - does not work
"SSLProtocol all -SSLv3" - does not work

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

Title:
  apache 2.4.29-1ubuntu4.12 authentication with client certificate
  broken

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

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

[Bug 1865900] Re: apache 2.4.29-1ubuntu4.12 authentication with client certificate broken

[Ken Dreyer (Red Hat)]

>From https://bugzilla.redhat.com/show_bug.cgi?id=1761403:
"The fix is available in urllib3 1.25.4. The fix requires Python 3.7.4 or newer 
with fix https://bugs.python.org/issue37428 ."

I upgraded urllib3 and requests to the Disco versions:

Unpacking python3-urllib3 (1.24.1-1ubuntu0.1) over (1.22-1ubuntu0.18.04.1) ...
Unpacking python3-requests (2.21.0-1) over (2.18.4-2ubuntu0.1) ...

I still get "HTTPError: 403 Client Error: Forbidden for url:
https://localhost/kojihub/ssllogin; in my Bionic VM when I try those
versions.

** Bug watch added: Red Hat Bugzilla #1761403
   https://bugzilla.redhat.com/show_bug.cgi?id=1761403

** Bug watch added: Python Roundup #37428
   http://bugs.python.org/issue37428

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

Title:
  apache 2.4.29-1ubuntu4.12 authentication with client certificate
  broken

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

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

[Bug 1865900] Re: apache 2.4.29-1ubuntu4.12 authentication with client certificate broken

[Ken Dreyer (Red Hat)]

I can confirm this as well. I have a CI job that uses python-requests to
contact Apache with SSL x590 client authentication. This job passed with
apache 2.4.29-1ubuntu4.11 and it fails with apache 2.4.29-1ubuntu4.12.

Passing: https://travis-ci.org/ktdreyer/koji-ansible/builds/655568368
Failing: https://travis-ci.org/ktdreyer/koji-ansible/builds/657818117

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

Title:
  apache 2.4.29-1ubuntu4.12 authentication with client certificate
  broken

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

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

[Bug 1808773] Re: python-boto: libssl1.1 dependency problems

[red shaphiro]

Solved with:

sudo dpkg -i python-boto_2.44.0-1.1_all.deb
sudo dpkg -i python-boto3_2.44.0-1.1_all.deb

apt-get update
apt-get upgrade

But is it a safe solution?

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

Title:
  python-boto: libssl1.1 dependency problems

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

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

[Bug 1808773] Re: python-boto: libssl1.1 dependency problems

[red shaphiro]

Same problem for me in all my debian 9.6 servers.

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

Title:
  python-boto: libssl1.1 dependency problems

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

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

[Bug 1803423] [NEW] koji-client should depend on requests and dateutil

[Ken Dreyer (Red Hat)]

Public bug reported:

I'm using koji-client_1.16.0-2 on Cosmic.

$ koji hello
Traceback (most recent call last):
  File "/usr/bin/koji", line 40, in 
import koji
  File "/usr/lib/python2.7/dist-packages/koji/__init__.py", line 64, in 
import requests
ImportError: No module named requests


After "apt-get install python-requests"...


$ koji hello
Traceback (most recent call last):
  File "/usr/local/bin/kojidev", line 46, in 
from koji_cli.commands import *
  File "/usr/lib/python2.7/dist-packages/koji_cli/commands.py", line 5, in 

import dateutil.parser
ImportError: No module named dateutil.parser

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

** Summary changed:

- koji-client should depend on requests
+ koji-client should depend on requests and dateutil

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

Title:
  koji-client should depend on requests and dateutil

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

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

[Bug 1803416] [NEW] update bionic to 1.16.0

[Ken Dreyer (Red Hat)]

Public bug reported:

Bionic currently has Koji v1.10.0. This version lacks the "import-cg"
command. Would you please update the Bionic package to the 1.16.0 one in
Cosmic?

** Affects: koji (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/1803416

Title:
  update bionic to 1.16.0

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

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

[Bug 1776271] Re: Could not prepare Boot variable: No space left on device (package shim-signed 1.34.9+13-0ubuntu2 [origin: Ubuntu] failed to install/upgrade: Unterprozess installed shim-signed packag

[Red Dress]

I just need to do this:
sudo apt install --reinstall shim-signed
Thanks abssorb.

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

Title:
  Could not prepare Boot variable: No space left on device (package
  shim-signed 1.34.9+13-0ubuntu2 [origin: Ubuntu] failed to
  install/upgrade: Unterprozess installed shim-signed package post-
  installation script gab den Fehler-Ausgangsstatus 1 zurück)

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

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

[Bug 1794011] [NEW] crash during installation of UbuntuStudio

[Red McPanda]

Public bug reported:

UbuntuStudio 18.04

crash after setting partition table and pressing continue.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
Uname: Linux 4.15.0-20-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
Date: Sun Sep 23 21:29:26 2018
InstallCmdLine: file=/cdrom/preseed/ubuntustudio.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash ---
LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
ProcEnviron:
 LANGUAGE=en_CA.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.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 ubuntustudio

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

Title:
  crash during installation of UbuntuStudio

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

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

[Bug 1791543] [NEW] package shim-signed 1.34.9.2+13-0ubuntu2 failed to install/upgrade: problemas com dependências - a deixar triggers por processar

[Red Dress]

Public bug reported:

failed to install

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: shim-signed 1.34.9.2+13-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
.proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] Ficheiro ou directoria 
inexistente: '/proc/sys/kernel/moksbstate_disabled'
ApportVersion: 2.20.9-0ubuntu7.3
AptOrdering:
 python3-problem-report:amd64: Install
 python3-apport:amd64: Install
 apport:amd64: Install
 apport-gtk:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sun Sep  9 21:10:35 2018
EFITables:
 set 09 21:12:41 reddress-HP-Notebook kernel: efi: EFI v2.40 by INSYDE Corp.
 set 09 21:12:41 reddress-HP-Notebook kernel: efi:  ACPI 2.0=0x76fb6014  
SMBIOS=0x75803000  ESRT=0x75801e18 
 set 09 21:12:41 reddress-HP-Notebook kernel: secureboot: Secure boot could not 
be determined (mode 0)
 set 09 21:12:41 reddress-HP-Notebook kernel: esrt: Reserving ESRT space from 
0x75801e18 to 0x75801e50.
ErrorMessage: problemas com dependências - a deixar triggers por processar
InstallationDate: Installed on 2018-07-23 (48 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SecureBoot: 6   0   0   0   0
SourcePackage: shim-signed
Title: package shim-signed 1.34.9.2+13-0ubuntu2 failed to install/upgrade: 
problemas com dependências - a deixar triggers por processar
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: shim-signed (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package shim-signed 1.34.9.2+13-0ubuntu2 failed to install/upgrade:
  problemas com dependências - a deixar triggers por processar

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

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

[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise

[Red]

Susi,

It appears you aren't reading the full threads. Your solution does not
work. This has been a bug for YEARS and needs to be fixed.

I posted a possible real solution or at least how to get started with a
real solution above and on the other bug report for this same issue.

Please read the full thread(s) before commenting.

Sincerely,
Red

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

Title:
  installer uses first EFI system partition found even when directed
  otherwise

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

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

[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI

[Laszlo Ersek (Red Hat)]

I may be able to provide some information here, about iPXE. (Corrections
welcome, obviously!)

iPXE can be built in a number of ways. Two of those are: (1) as a UEFI
*driver* that is presented in a NIC's PCI ROM BAR (i.e., as part of a
PCI expansion ROM), (2) as a UEFI *application* that can be loaded from
optical media / an ISO image, or a USB flash drive, or chain-loaded over
the network with the platform firmware's built-in netboot capabilities.

Independently of that dimension (i.e., build target), iPXE can be built
with different features enabled (through feature test macros). One of
those feature macros is "EFI_DOWNGRADE_UX". You can read about it e.g.
in iPXE commit a15c0d7e868a ("[efi] Allow user experience to be
downgraded", 2015-07-22).

I'll spare you the technical details; the point is that without
"EFI_DOWNGRADE_UX" (that is, in the default case), iPXE sort of takes
over the entire UEFI netboot process, supplanting most of the edk2
network stack (which is built into OVMF).

It is widely agreed upon that this behavior is appropriate for build
type (2) above, i.e. when iPXE is launched as a UEFI *application*.

Opinions differ whether this behavior is approprite for build type (1),
that is, when iPXE is built as a UEFI *driver*, to be included in a
specific NIC's PCI ROM BAR / expansion ROM image.

In my personal opinion, which some others (but definitely not all)
share, for build type (1), the "take-over" behavior of iPXE is not
desirable, and iPXE should only provide the lowest level hardware driver
for the NIC. (And then the rest of the UEFI network stack will come from
the edk2 modules -- this is precisely the situation that Steve describes
in comment#1.) In other words, for build type (1), the
"EFI_DOWNGRADE_UX" feature test macro should be defined -- in my
opinion. And, since iPXE commit a200ad462e69 ("[build] Add named
configuration for qemu", 2015-07-22), this is easily achievable by
passing the "CONFIG=qemu" macro definition to "make", when the "bin-
x86_64-efi/*.efidrv" files are built.

>From the pics attached earlier (e.g. comment#3), I'm nearly 100% sure
that the iPXE UEFI drivers in question -- build type (1) --  had been
built *without* EFI_DOWNGRADE_UX. While more recent iPXE commit
3376fa520b0c ("[efi] Implement the EFI_PXE_BASE_CODE_PROTOCOL",
2015-09-02) suggests this should function OK, I would still suggest
rebuilding the iPXE UEFI drivers (the PCI oproms) with "CONFIG=qemu",
and retrying.

"CONFIG=qemu" is certainly what we use in RHEL and Fedora, in the ipxe-
roms-qemu package. It's easy to refer to the Fedora spec file:

https://koji.fedoraproject.org/koji/packageinfo?packageID=13673

One more addition: from comment #2, I see that the NIC device model is
virtio. For a virtio NIC, you don't even need that "lowest level
hardware driver" to come from iPXE -- OVMF has a built-in (= native to
edk2) driver for virtio-net. It's located under OvmfPkg/VirtioNetDxe.
This means that, if you want to, you can netboot entirely without iPXE.
(Note I'm not saying you "should" boot without iPXE, just that you
"can", *if* you want to.) This is how:

As explained in OvmfPkg/README (see "Network Support"), if you use a
virtio NIC, and do not prevent QEMU (through the libvirt domain config)
from loading the iPXE oprom for the NIC, then iPXE's UEFI driver will
take precedence (regardless of whether it was built with or without
CONFIG=qemu) over OVMF's built-in driver. Using modern libvirt, you can
disable oprom loading (thereby opt for the built-in virtio-net driver)
by adding "rom enabled='no'/" under the "interface" element. Using less
recent libvirt, "rom bar='off'/" works somewhat similarly, although
technically it's quite different, and it won't work if you try to add it
to multiple "interface" elements. (Refer to RHBZ#1425058 for details.)

(I'm sorry for not including actual XML fragments -- I don't know if
Launchpad gets confused by unescaped angle brackets in comments.)

Summary:

- *If* you think this use case -- i.e., build type (1) -- is worth
testing with an iPXE oprom limited to the lowest level hardware driver
feature, then I suggest rebuilding iPXE (just the efidrv files) with
"CONFIG=qemu" passed on the "make" command line.

- *If* you think this use case -- i.e., build type (1) -- is worth
testing with iPXE entirely absent, then I suggest (a) sticking with the
virtio NIC, and (b) disabling oprom loading in the libvirt domain XML,
preferably with "rom enabled='no'", and less preferably with "rom
bar='off'".

(In either of the above two cases, it's still possible to use the super-
advanced features of a full-blown iPXE build. For that, build iPXE
without CONFIG=qemu (which is the default) for build target (2), i.e.,
as a UEFI application ("ipxe.efi"), and chain-load that over the
network.)

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

Title:
  Unable to load shimx64.efi 

[Bug 1173457] Re: Ubuntu Installer uses wrong bootloader location for USB UEFI installs

[Red]

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

Please note that this bug report is a duplicate of bug #1396379 (
https://bugs.launchpad.net/bugs/1396379 ). The last comment on that bug
report as of this comment by me, Red, posted by "Tim Richardson (tim-
richardson)" on 2018-07-14 has a potential work around that subscribers
to this thread, and future visitors to this bug report, may appreciate

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

Title:
  Ubuntu  Installer uses wrong bootloader location for USB UEFI installs

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

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

[Bug 1777479] [NEW] RFE: add "allow-unauthenticated" option to add-apt-repository

[Ken Dreyer (Red Hat)]

Public bug reported:

The apt command has an "--allow-unauthenticated" option.

It would be great to add "--allow-unauthenticated" to "add-apt-
repository" as well. This could add the "[trusted=yes]" option to the
/etc/apt/sources.list.d/my_trusted_repo.list definition. Like so:

  deb [trusted=yes] https://example.com/ bionic main

** Affects: software-properties (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/1777479

Title:
  RFE: add "allow-unauthenticated" option to add-apt-repository

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

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

[Bug 1173457] Re: Ubuntu Installer uses wrong bootloader location for USB UEFI installs

[Red]

Possible workaround: (instructions are for macs, but the idea of
starting ubiquity with:

ubiquity --no-bootloader

might lead in a direction to a workaround for PCs. If you figure out a
full solution, please post on this forum as I'm monitoring it and it
looks like people are starting to find this bug report from Google after
much agony).

https://medium.com/@mmiglier/ubuntu-installation-on-usb-stick-with-pure-
efi-boot-mac-compatible-469ad33645c9

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

Title:
  Ubuntu  Installer uses wrong bootloader location for USB UEFI installs

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

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

[Bug 1173457] Re: Ubuntu Installer uses wrong bootloader location for USB UEFI installs

[Red]

Wanted to create a *portable* Linux Mint USB stick with encryption via
LUKS. Installed grub to EFI of local system and not on USB stick itself.
EFI of local system points to USB stick. Successfully boots to USB stick
on this one system, wrecked my local EFI.

What a mess. I'm fortunate I even figured it out and ended up on this
page, confirming I am not crazy.

Commenters on Linux forums, Stackexchange/Superuser, etc sent me down
various rabbit holes for n00bs (probably because they observed I was
attempting install with encryption). Fortunately I had enough Linux
experience to finally narrow it down to finding this damn page.

And for the curious, I got the encryption working. On this one system.
And my local EFI now has to be repaired. And my USB stick is useless
until I repartition and start over.

* CRITICAL ISSUE *

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

Title:
  Ubuntu  Installer uses wrong bootloader location for USB UEFI installs

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

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

[Bug 1173457] Re: Ubuntu Installer uses wrong bootloader location for USB UEFI installs

[Red]

me too.

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

Title:
  Ubuntu  Installer uses wrong bootloader location for USB UEFI installs

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

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

Re: [Bug 1754555] Re: acer电脑无法启动wifi

[Frost Red Lee]

regessio是什麼意思呢？

2018-04-26 14:04 GMT+08:00 Kai-Heng Feng :

> 請在 [0] 找出第一個產生regressio的v4.10-rc* kernel.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1754555
>
> Title:
>   acer电脑无法启动wifi
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   acer aspire 4752安装了ubuntu16.04
>   内核4.4一切正常，升级了18.04，内核4.15，发现无法启动无线网卡，具体问题也是点击“开启wifi”，
> 然后开启后，提示wifi已禁用，用热键开启wifi也不行。
>
>   $lspci
>   网卡型号是：Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express)
> (rev 01)
>   各种方法都尝试了，最后在一个不起眼的角落里找到了方法，如下：
>
>   sudo vim /etc/modprobe.d/blacklist.conf
>
>   最后加入一行 blacklist acer-wmi  #将acer-wmi驱动加入黑名单
>   重启即可。。。
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: linux-image-generic 4.15.0.10.11
>   ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
>   Uname: Linux 4.15.0-10-generic x86_64
>   AlsaVersion: Advanced Linux Sound Architecture Driver Version
> k4.15.0-10-generic.
>   AplayDevices: Error: [Errno 2] No such file or directory: 'aplay':
> 'aplay'
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
> 'arecord'
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/pcmC0D0p:   admin  1187 F...m pulseaudio
>/dev/snd/controlC0:  admin  1187 F pulseaudio
>   Card0.Amixer.info: Error: [Errno 2] No such file or directory:
> 'amixer': 'amixer'
>   Card0.Amixer.values: Error: [Errno 2] No such file or directory:
> 'amixer': 'amixer'
>   CurrentDesktop: MATE
>   Date: Fri Mar  9 12:09:53 2018
>   IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig':
> 'iwconfig'
>   MachineType: Acer Aspire 4752
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic
> root=UUID=d4b4468a-f732-42b5-89ac-dbeef56e0c79 ro quiet swapaccount=1
>   RelatedPackageVersions:
>linux-restricted-modules-4.15.0-10-generic N/A
>linux-backports-modules-4.15.0-10-generic  N/A
>linux-firmware 1.172
>   RfKill:
>0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   WifiSyslog:
>
>   dmi.bios.date: 08/11/2011
>   dmi.bios.vendor: Phoenix Technologies Ltd.
>   dmi.bios.version: V2.09
>   dmi.board.asset.tag: No Asset Tag
>   dmi.board.name: Aspire 4752
>   dmi.board.vendor: Acer
>   dmi.board.version: V2.09
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Acer
>   dmi.chassis.version: V2.09
>   dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.09:bd08/11/2011:
> svnAcer:pnAspire4752:pvrV2.09:rvnAcer:rnAspire4752:rvrV2.09:
> cvnAcer:ct9:cvrV2.09:
>   dmi.product.family: HuronRiver System
>   dmi.product.name: Aspire 4752
>   dmi.product.version: V2.09
>   dmi.sys.vendor: Acer
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1754555/+subscriptions
>

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

Title:
  acer电脑无法启动wifi

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

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

Re: [Bug 1754555] Re: acer电脑无法启动wifi

[Frost Red Lee]

是的，4.9还是正常的

On Wed, Apr 25, 2018, 3:10 PM Kai-Heng Feng 
wrote:

> 所以4.9是好的? 4.10開始是壞的?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1754555
>
> Title:
>   acer电脑无法启动wifi
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   acer aspire 4752安装了ubuntu16.04
>
> 内核4.4一切正常，升级了18.04，内核4.15，发现无法启动无线网卡，具体问题也是点击“开启wifi”，然后开启后，提示wifi已禁用，用热键开启wifi也不行。
>
>   $lspci
>   网卡型号是：Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express)
> (rev 01)
>   各种方法都尝试了，最后在一个不起眼的角落里找到了方法，如下：
>
>   sudo vim /etc/modprobe.d/blacklist.conf
>
>   最后加入一行 blacklist acer-wmi  #将acer-wmi驱动加入黑名单
>   重启即可。。。
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: linux-image-generic 4.15.0.10.11
>   ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
>   Uname: Linux 4.15.0-10-generic x86_64
>   AlsaVersion: Advanced Linux Sound Architecture Driver Version
> k4.15.0-10-generic.
>   AplayDevices: Error: [Errno 2] No such file or directory: 'aplay':
> 'aplay'
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
> 'arecord'
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/pcmC0D0p:   admin  1187 F...m pulseaudio
>/dev/snd/controlC0:  admin  1187 F pulseaudio
>   Card0.Amixer.info: Error: [Errno 2] No such file or directory:
> 'amixer': 'amixer'
>   Card0.Amixer.values: Error: [Errno 2] No such file or directory:
> 'amixer': 'amixer'
>   CurrentDesktop: MATE
>   Date: Fri Mar  9 12:09:53 2018
>   IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig':
> 'iwconfig'
>   MachineType: Acer Aspire 4752
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic
> root=UUID=d4b4468a-f732-42b5-89ac-dbeef56e0c79 ro quiet swapaccount=1
>   RelatedPackageVersions:
>linux-restricted-modules-4.15.0-10-generic N/A
>linux-backports-modules-4.15.0-10-generic  N/A
>linux-firmware 1.172
>   RfKill:
>0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   WifiSyslog:
>
>   dmi.bios.date: 08/11/2011
>   dmi.bios.vendor: Phoenix Technologies Ltd.
>   dmi.bios.version: V2.09
>   dmi.board.asset.tag: No Asset Tag
>   dmi.board.name: Aspire 4752
>   dmi.board.vendor: Acer
>   dmi.board.version: V2.09
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Acer
>   dmi.chassis.version: V2.09
>   dmi.modalias:
> dmi:bvnPhoenixTechnologiesLtd.:bvrV2.09:bd08/11/2011:svnAcer:pnAspire4752:pvrV2.09:rvnAcer:rnAspire4752:rvrV2.09:cvnAcer:ct9:cvrV2.09:
>   dmi.product.family: HuronRiver System
>   dmi.product.name: Aspire 4752
>   dmi.product.version: V2.09
>   dmi.sys.vendor: Acer
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754555/+subscriptions
>

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

Title:
  acer电脑无法启动wifi

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

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

[Bug 1754555] Re: acer电脑无法启动wifi

[Frost Red Lee]

** Attachment added: "rfkill_after.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754555/+attachment/5103830/+files/rfkill_after.txt

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

Title:
  acer电脑无法启动wifi

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

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

[Bug 1754555] Re: acer电脑无法启动wifi

[Frost Red Lee]

我的电脑也是这个型号，也遇见了这个问题，我试过到4.9还是正常的，之后的版本全有这个问题，另外我用的是 Manjaro
发行版，网上只搜到了这一个报这个问题的地方。blacklist添加后就能打开wifi了。

** Attachment added: "dmesg_before.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754555/+attachment/5103827/+files/dmesg_before.txt

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

Title:
  acer电脑无法启动wifi

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

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

[Bug 1754555] Re: acer电脑无法启动wifi

[Frost Red Lee]

** Attachment added: "dmesg_after.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754555/+attachment/5103829/+files/dmesg_after.txt

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

Title:
  acer电脑无法启动wifi

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

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

[Bug 1754555] Re: acer电脑无法启动wifi

[Frost Red Lee]

** Attachment added: "rfkill_before.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754555/+attachment/5103828/+files/rfkill_before.txt

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

Title:
  acer电脑无法启动wifi

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

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

[Bug 1744072] Re: MIR Chrony in 18.04

[Ken Dreyer (Red Hat)]

Ceph tracker to switch from ntpd to chronyd:
http://tracker.ceph.com/issues/22751

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

Title:
  MIR Chrony in 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ntp-charm/+bug/1744072/+subscriptions

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

[Bug 1725560] Re: OVMF UEFI firmware causes Windows 10 to not boot after upgrade

[Laszlo Ersek (Red Hat)]

@Max: most important is to isolate the component whose upgrade causes
the regression for you. OVMF, QEMU, libvirt (possibly, but unlikely),
and host kernel (=KVM). Once isolated, the component should be
bisectable. See also LP#1723731 -- the issue you are seeing might be a
duplicate. (I haven't commented on LP#1723731 because I totally don't
have the time to guide a user through component isolation, feature
removal / cmdline trimming, and bisection; sorry.) Either way I agree
with @dannf that it should be discussed elsewhere. Thanks.

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

Title:
  OVMF UEFI firmware causes Windows 10 to not boot after upgrade

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

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

[Bug 1728605] [NEW] (Artful) bombono-dvd crashes when adding videos or loading a project

[Red]

Public bug reported:

Hi,

Ever since I upgraded one of my computers to Artful, I am unable to use
bombono-dvd. After attempting to add video files to the project (or
loading a pre-existing bombono-dvd project), it crashes with
"segmentation fault", sometimes (but not always) having messages
referring to "estimate_timings_from_pts" and/or "bad_dst_image_pointers"

This crash occurs when attempting to add video files of any format to
the project, including the "DVD-compliant" format. The same crash
happens when loading a pre-existing Bombono DVD project.

Searching this issue finds a small number of Arch users making similar
complaints. An example crash message from this page:

https://aur.archlinux.org/packages/bombono-dvd/

--

[swscaler @ 0x250ae80] bad dst image pointers
Segmentation fault

--

The Arch user claims he has no problems on 32-bit distributions. I am
running Xubuntu Artful 64-bit, and so cannot test it unless I set up a
VirtualBox, I can do it if needed. And again it has worked properly on
this machine until the Artful upgrade, and continues to work properly on
a Xenial LTS machine I have.

** Affects: bombono-dvd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful bombono-dvd bombono-dvd-data

** Tags added: bombono-dvd

** Project changed: sikuli => bombono-dvd (Ubuntu)

** Tags added: artful bombono-dvd-data

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

Title:
  (Artful) bombono-dvd crashes when adding videos or loading a project

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

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

[Bug 1725560] Re: OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot after upgrade

[Laszlo Ersek (Red Hat)]

Thanks everyone for the help; I pushed the patch in comment #40 as edk2
commit 76fd5a660d70.

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

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

Title:
  OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot
  after upgrade

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

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

[Bug 1725560] Re: OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot after upgrade

[Laszlo Ersek (Red Hat)]

Posted:

[edk2] [PATCH] MdeModulePkg/AtaAtapiPassThru: disable only BM-DMA at
   ExitBootServices()
http://mid.mail-archive.com/20171026154819.20865-1-lersek@redhat.com
https://lists.01.org/pipermail/edk2-devel/2017-October/016535.html

I CC'd a few people for feedback -- please send your Tested-by's if
appropriate.

I couldn't CC Krupp because their profile page on LP does not disclose their
email address, and my privmsg to them (via LP) hadn't been answered until I
mailed out the patch.

Nonetheless, anyone can fetch the patch by using the repo / branch URL
marked in the Notes section of the patch email:

Repo:   https://github.com/lersek/edk2.git
Branch: ata_disable_only_bmdma

Please note, if you decide to follow up on the email, the edk2-devel mailing
list drops messages from non-subscribers. I've been trying to change this
practice:

  https://bugzilla.tianocore.org/show_bug.cgi?id=451

but I haven't succeeded thus far. So, if you'd like to respond, please
subscribe to the list first (wait for your subscription to complete!), and
then respond. The list page is:

  https://lists.01.org/mailman/listinfo/edk2-devel


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

** Bug watch added: bugzilla.tianocore.org/ #451
   https://bugzilla.tianocore.org/show_bug.cgi?id=451

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

Title:
  OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot
  after upgrade

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

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

[Bug 1725560] Re: OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot after upgrade

[Laszlo Ersek (Red Hat)]

Re: comment 32:

> BTW, I've also noticed that a large chunk of the delay, with i440fx, is
> not even spent loading data from the IDE CD-ROM. IDE emulation means host
> CPU load, but in this case, Windows just sits there with the empty
> purplish/bluish screen, and there is zero host CPU load -- nothing
> happens. It's as if Windows was waiting for some timer to expire.

The time Windows spends in this stuck state is exactly 1 minute.

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

Title:
  OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot
  after upgrade

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

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

[Bug 1725560] Re: OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot after upgrade

[Laszlo Ersek (Red Hat)]

(

Aleksei: no, mail-archive.com is a public mailing list archive, it does
not require subscription.

After the demise of GMANE, I started using references to mail-
archive.com because similarly to GMANE, it also provides lookup by
Message-Id -- regardless of the specific mailing list(s) that the
message in question was posted to. (The only requirement is that mail-
archive.com be subscribed to at least one of the lists that the message
was sent to.) The URL format is

  http://mid.mail-archive.com/

The trick is that such URLs can be constructed, on the email sender's
side, ahead of mail-archive.com picking up the message (from at least
one mailing list) and indexing it. The URL can be constructed without
any delay because the sender knows the Message-Id of the message they
just sent. Initially the link will appear dead, but after a while it
will start working.

So using these links I can just send the email, generate the link right
after, and forget about it, regardless of how slow or fast the archive
is that day.

)

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

Title:
  OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot
  after upgrade

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

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

[Bug 1725560] Re: OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot after upgrade

[Laszlo Ersek (Red Hat)]

OK, given that the edk2 commit in question is correct, I asked
specifically for bug-compat ideas on edk2-devel:

http://mid.mail-archive.com/5bf829cb-4517-a579-ba7c-
745c4ee89...@redhat.com

I'll also try to ask IDE and Windows experts for help with figuring out
what Windows is waiting for, when it's apparently doing nothing.

As a mid-term mitigation / work-around, I suggest using virtio-block or
virtio-scsi for hard disks, and virtio-scsi for CD-ROMs. Windows (7, 8,
and 10) can be perfectly well installed from a virtio-scsi CD-ROM to a
virtio-scsi or virtio-blk hard disk, as long as the guest has *another*
CD-ROM, using IDE or AHCI, and this CD-ROM presents the virtio-win ISO.
The only thing the Windows installer *really* has to read from an
IDE/AHCI CD-ROM is the virtio-scsi/virtio-block driver, all the rest can
work with virtio.

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

Title:
  OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot
  after upgrade

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

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

[Bug 1725560] Re: OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot after upgrade

[Laszlo Ersek (Red Hat)]

** Attachment added: "undamaged table from comment#32"
   
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1725560/+attachment/4994611/+files/lp-1725560-c-32-table.txt

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

Title:
  OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot
  after upgrade

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

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

[Bug 1725560] Re: OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot after upgrade

[Laszlo Ersek (Red Hat)]

Using the script from comment#30:

QEMU  machine  OVMF   time from launch to
  typefirst install screen
  ---  -  
v2.8.1.1  pc   704b71d7e11f  117 s
v2.8.1.1  pc   704b71d7e11f\6fb8ddd36bde  44 s

v2.8.1.1  q35  704b71d7e11f9 s
v2.8.1.1  q35  704b71d7e11f\6fb8ddd36bde   9 s

v2.10.1   pc   704b71d7e11f  119 s
v2.10.1   pc   704b71d7e11f\6fb8ddd36bde  46 s

v2.10.1   q35  704b71d7e11f   10 s
v2.10.1   q35  704b71d7e11f\6fb8ddd36bde   9 s

Observe:

- The QEMU release plays no role

- on q35 the boot is generally much faster than i440fx

- q35 is unaffected by edk2 commit 6fb8ddd36bde

- on i440fx, reverting edk2 commit 6fb8ddd36bde on top of current master
  (704b71d7e11f) decreases the wall clock time from ~118s to ~45s.

To me this totally looks like a Windows bug; edk2 commit 6fb8ddd36bde does
the right thing. The patch disables PCI bus master DMA for the IDE/AHCI
controller in question at ExitBootServices(), i.e. when the OS gains control
of the system from the firmware. At that point ownership of the RAM is
transferred to the OS, and in-flight DMA has to be aborted (otherwise DMA
pending from the firmware could overwrite RAM that is now owned by the OS).
Whether a controller is passed -- from firmware to the OS -- with DMA
enabled vs. DMA disabled in the PCI command register, should have zero
consequence on how the OS drives the controller subsequently, with its own
native driver.

BTW, I've also noticed that a large chunk of the delay, with i440fx, is not
even spent loading data from the IDE CD-ROM. IDE emulation means host CPU
load, but in this case, Windows just sits there with the empty
purplish/bluish screen, and there is zero host CPU load -- nothing happens.
It's as if Windows was waiting for some timer to expire.

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

Title:
  OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot
  after upgrade

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

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

[Bug 1725560] Re: OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot after upgrade

[Laszlo Ersek (Red Hat)]

In other news, LaunchPad is an abomination. Way to screw up my nicely
laid out table in comment#32.

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

Title:
  OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot
  after upgrade

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

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

[Bug 1725560] Re: OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot after upgrade

[Laszlo Ersek (Red Hat)]

Hold on, the machine type could have an impact. I switched my script in
comment#30 from q35 to pc, and the IDE CD-ROM boot slowed to a crawl.
I've always assumed that this difference was simply due to q35 having
AHCI/SATA and pc having only plain IDE, but maybe there is a perf
regression specific to IDE (pc) only.

FWIW, edk2 commit 6fb8ddd36bde applies to both controllers.

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

Title:
  OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot
  after upgrade

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

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

[Bug 1725560] Re: OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot after upgrade

[Laszlo Ersek (Red Hat)]

Thanks everyone for the investigation thus far.

I cannot reproduce the issue (using an IDE CD-ROM):

* QEMU: tested both the v2.10.1 release, and current upstream master
  (3d7196d43bfe, "Merge remote-tracking branch
  'remotes/kraxel/tags/usb-20171023-pull-request' into staging", 2017-10-24)

* OVMF: built from current upstream master (704b71d7e11f,
  "MdeModulePkg/Variable/RuntimeDxe: delete & lock MOR in the absence of
  SMM", 2017-10-10)

QEMU script:

> ISO=/mnt/data/isos/iso-windows/en_windows_10_enterprise_2015_ltsb_n_x64_dvd_6848316.iso
> CODE=/home/virt-images/OVMF_CODE.4m.fd
> TMPL=/home/virt-images/OVMF_VARS.4m.fd
>
> cp $TMPL vars18.fd
>
> /opt/qemu-installed/bin/qemu-system-x86_64 \
>   -m 2048 \
>   -M q35 \
>   -enable-kvm \
>   -device qxl-vga \
>   -drive if=pflash,readonly,format=raw,file=$CODE \
>   -drive if=pflash,format=raw,file=vars18.fd \
>   -drive id=cdrom,if=none,readonly,format=raw,cache=writethrough,file=$ISO \
>   -device ide-cd,drive=cdrom,bootindex=0 \
>   -debugcon file:debug18.log \
>   -global isa-debugcon.iobase=0x402 \
>   -monitor stdio

Wall clock time from QEMU invocation to first install screen: 9 seconds.

Now, this script does not assign a GPU with vfio-pci, but I understand Dann
didn't do that either, yet he managed to reproduce the issue. Can someone
please paste a *minimal* QEMU command line reproducer , preferably without
vfio-pci; even more preferably with just an IDE CD-ROM? (To my
understanding, this is exactly how Dann reproduced the issue; see
comment#17.)

Also, from the comments thus far, it looks like edk2 commit 6fb8ddd36bde
makes a difference under QEMU 2.10. However, it is not clear to me if the
same edk2 commit makes a similar difference under QEMU 2.8. The original
report mentions a full system upgrade, which (I assume) upgraded both OVMF
and QEMU. Can someone -- who otherwise reproduces the issue -- please test
OVMF, built from upstream edk2, under QEMU 2.8?

Thanks.

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

Title:
  OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot
  after upgrade

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

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

[Bug 1725560] Re: OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot after upgrade

[Laszlo Ersek (Red Hat)]

In comment 17, Krupp confirmed that even current-ish upstream
(d8e36289cef7, "EmbeddedPkg: add driver to set graphical/serial console
preference", 2017-10-20) was broken for them; so I was definitely off
with my LP#1715700 parallel. Sorry about that.

The bisection thus far has narrowed down the introduction of the issue
to the following commits:

  git log --oneline --reverse --no-decorate c50596a70143..5659ec3fa913 \
  | cat -n

 1  3d4361663276 MMC : Added missing __FUNCTION__ macro.
 2  ea21f1d98dcc SD : Updated CMD 6 implememtation.
 3  3281ebb4ae7d Nt32Pkg: Clean up DSC to remove unnecessary build
 option in SecMain
 4  eed3f7130522 MdeModulePkg/AtaAtapiPassThru: cache
 EnabledPciAttributes
 5  509daa658b79 MdeModulePkg/AtaAtapiPassThru: unmap DMA buffers
 after disabling BM DMA
 6  6fb8ddd36bde MdeModulePkg/AtaAtapiPassThru: disable the device
 at ExitBootServices()
 7  5659ec3fa913 OvmfPkg/VirtioBlkDxe: don't unmap VRING at
 ExitBootServices()

I don't see how patches #1 through #3 could be relevant.

Patch #7 is a no-op in non-SEV guests.

Patches #4 through #6 are also from yours truly. I wonder if patch #6:

  https://github.com/tianocore/edk2/commit/6fb8ddd36bde

tickles something in QEMU 2.10 that makes the IDE controller unusable to
Windows.

I don't think that edk2 commit 6fb8ddd36bde is broken; disabling bus
master DMA at ExitBootServices() is valid. The commit been used on
physical ATA controllers as well, since its introduction.

Given that I can't see anything suspicious and/or invalid in the above
edk2 commit range, I suggest that -- after the current edk2 bisection is
completed -- we bisect QEMU between 2.8 and 2.10, using the package

  ovmf_0-20170911.5dfba97c-1_all.deb

In comment #1 Dann stated he could *not* reproduce the issue. Was that
perhaps because Krupp used IDE but Dann used virtio? Krupp, can you
please provide your exact QEMU command line and/or libvirt domain XML?
Thanks.

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

Title:
  OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot
  after upgrade

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

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

[Bug 1725560] Re: OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot after upgrade

[Laszlo Ersek (Red Hat)]

You are probably hitting one of LP#1715700 and LP#1714331. (Upgrading
from "Zesty" (17.04) to "Artful" (17.10) seems to imply a QEMU upgrade
from 2.8 to 2.10.)

LP#1715700 was fixed in edk2 commit range b68c793144e8..947f3737abf6:

ba1d245f1d3d OvmfPkg/CsmSupportLib: move PAM register addresses to 
IndustryStandard
ce461ae240a7 OvmfPkg/QemuVideoDxe/VbeShim: rename Status to 
Segment0AllocationStatus
947f3737abf6 OvmfPkg/QemuVideoDxe/VbeShim: handle PAM1 register on Q35 correctly

edk2 commits related to LP#1714331 are:

198a46d768fb MdeModulePkg/AcpiTableDxe: improve FADT.{DSDT,X_DSDT} mutual 
exclusion
78807f605082 MdeModulePkg/AcpiTableDxe: Not make FADT.{DSDT,X_DSDT} mutual 
exclusion
072060a6f81b OvmfPkg: Allow multiple add-pointer linker commands to same ACPI 
table

at least; in this order.

Regarding the change to the boot animation, that's due to commit
6e5e544f227f ("OvmfPkg: Install BGRT ACPI table", 2017-01-06).

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

Title:
  OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot
  after upgrade

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

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

[Bug 1275524] Re: notify-osd crashed with signal 5 in _XReply()

[Red Bike Master]

I just got this error in 17.04

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

Title:
  notify-osd crashed with signal 5 in _XReply()

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

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

[Bug 1709396] Re: gcc-7/i386|armhf 12.1.2 FTBFS

[Ken Dreyer (Red Hat)]

For the record this went upstream in
https://github.com/ceph/ceph/pull/16938

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

Title:
  gcc-7/i386|armhf 12.1.2 FTBFS

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

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

[Bug 1636322] Re: [SRU] upstart: ceph-all service starts before networks up

[Ken Dreyer (Red Hat)]

Thanks Billy, I'll update upstream's tracker with that PR link.

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

Title:
  [SRU] upstart: ceph-all service starts before networks up

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

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

[Bug 1636322] Re: [SRU] upstart: ceph-all service starts before networks up

[Ken Dreyer (Red Hat)]

James and Billy, was a patch sent upstream for this?

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

Title:
  [SRU] upstart: ceph-all service starts before networks up

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

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

[Bug 1647864] Re: google-perftools can deadlock with dlopen on startup

[Ken Dreyer (Red Hat)]

Would you please fix this in Xenial?

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

Title:
  google-perftools can deadlock with dlopen on startup

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

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

[Bug 1411030] Re: backport support for unix domain sockets

[Ken Dreyer (Red Hat)]

We're going to remove support for FCGI in RGW:
http://tracker.ceph.com/issues/16784, so we won't need this bug any
more.

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

Title:
  backport support for unix domain sockets

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

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

[Bug 1422417] Re: ceph radosgw needs mod-proxy-fcgi for apache 2.2

[Ken Dreyer (Red Hat)]

We're going to remove support for FCGI in RGW:
http://tracker.ceph.com/issues/16784, so we won't need this bug any
more.

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

Title:
  ceph radosgw needs mod-proxy-fcgi for apache 2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/precise-backports/+bug/1422417/+subscriptions

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

[Bug 1331856] Re: apparmor-utils don't work when defining a variable on

[Red Ink]

This bug is still present in AppArmor in Xenial. Shouldn't this be an
easy fix?

** Also affects: apparmor (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/1331856

Title:
  apparmor-utils don't work when defining a variable on
  

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

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

[Bug 1647864] Re: google-perftools can deadlock with dlopen on startup

[Ken Dreyer (Red Hat)]

Here's the RHEL 7 bug: http://bugzilla.redhat.com/1339710

Patch we used in RHEL 7:
https://git.centos.org/raw/rpms!gperftools/7a06cf7fbfd7d53213c1c5f1206f3b8b0c89101d/SOURCES
!gp-Use-initial-exec-tls-for-libunwind-s-recursion-flag.patch

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

Title:
  google-perftools can deadlock with dlopen on startup

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

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

[Bug 1636544] Re: SUSE lrbd support for high availability iSCSI gateway and multipath support of Ceph RBD images

[Ken Dreyer (Red Hat)]

Sure. Also note that I think these utilities rely on features in kernel
4.9 (also backported to RHEL 7.3's upcoming kernel-3.10.0-514.el7 or
later), so it probably won't work on Ubuntu 14.04 and 16.04's standard
kernels. In terms of HWE kernels for those, it looks like only 16.04.3
or 16.04.4 will have HWE kernel 4.9 or newer.

https://wiki.ubuntu.com/Kernel/LTSEnablementStack

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

Title:
  SUSE lrbd support for high availability iSCSI gateway and multipath
  support of Ceph RBD images

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

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

[Bug 1636544] Re: SUSE lrbd support for high availability iSCSI gateway and multipath support of Ceph RBD images

[Ken Dreyer (Red Hat)]

To clarify the list of supported OSes: I am leaning towards retiring
lrbd from Fedora, and we have no plans to ship that tool on RHEL (via
the Red Hat Ceph Storage product).

Instead, we're going to use these projects to manage the userland iSCSI
bits:

https://github.com/pcuzner/ceph-iscsi-ansible
https://github.com/pcuzner/ceph-iscsi-config
https://github.com/pcuzner/ceph-iscsi-tools

We have not put ceph-iscsi-ansible into Fedora yet because there is
still some question regarding whether ceph-iscsi-ansible upstream will
eventually merge with ceph-ansible upstream, but it's 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/1636544

Title:
  SUSE lrbd support for high availability iSCSI gateway and multipath
  support of Ceph RBD images

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

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

[Bug 1632870] Re: Package is broken since Google stopped shipping Flash with Chrome 54 for Linux

[Red Ink]

CLARIFICATION:

Adobe's unreleased, new NPAPI Linux plugin will be crippled compared to
the PPAPI plugin:

   "Because this change is primarily a security initiative, some
features (like GPU 3D acceleration and premium video DRM) will not be
fully implemented."

Emphasis mine:

   "If you require this functionality, WE RECOMMEND THAT YOU USE THE
ppapi VERSION OF FLASH PLAYER."

-- https://blogs.adobe.com/flashplayer/2016/08/beta-news-flash-player-
npapi-for-linux.html

Using Adobe's official, crippled NPAPI plugin isn't an option for most
of us end users.

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

Title:
  Package is broken since Google stopped shipping Flash with Chrome 54
  for Linux

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

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

[Bug 1629356] [NEW] update xenial to 0.8.0

[Ken Dreyer (Red Hat)]

Public bug reported:

Would you please ship zstd 0.8.0 for Xenial and Trusty? Ceph is going to
have to bundle a newer zstd in the meantime, which makes Ceph's build
times longer, and makes it harder for us all to track security issues in
this library (https://github.com/ceph/ceph/pull/11156)

** Affects: libzstd (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/1629356

Title:
  update xenial to 0.8.0

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

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

[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim

[Laszlo Ersek (Red Hat)]

@Jason -- your script looks alright to me. Can you attach the OVMF debug
log captured with the script? (Although, if the debug mask configured at
build time in the DSC files don't enable the DEBUG_VERBOSE bit, I won't
see everything in the log that I would like to see.)

More importantly, can you upload your test ISO image (with the shim bug
fixed, or worked around) somewhere? If you don't want to expose the URL
publicly, feel free to send it to me in a private email, or in a private
Launchpad message. (I vaguely recall that such a thing exists.)

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

Title:
  yakkety: backport (or rebase to) fix eliminating a double-close in
  shim

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

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

[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim

[Laszlo Ersek (Red Hat)]

@Jason, there are two separate topics in your question.

First, controlling the boot order from the QEMU command line (i.e.,
filtering and/or reordering the persistent UEFI boot options that (a)
exist from earlier in the varstore, plus (b) OVMF's platform BDS
regenerates at every boot).

For this, you have to use the

-device ,bootindex=N

propertiey, which in turn necessitates the modern, separate notation for
backend/frontend.

For example, for network devices you have to spell out

-netdev ,id=netdev0,... \
-device virtio-net-pci,netdev=netdev0,bootindex=2

For disks, for example with the virtio-blk-pci frontend, it requires

-drive if=none,id=drive0,file=ZZZ,... \
-device virtio-blk-pci,drive=drive0,bootindex=1

The various shorthands like "-net nic", "-hda", "-drive if=virtio" don't
allow you to specify the bootindex=N property, and therefore are
unsuitable for OVMF. (At least if you want to control the boot order
from the QEMU command line.)

So, in this specific case, assuming you have one QCOW2 system disk
(created with qemu-img) that you want to install Ubuntu to, plus the
installer ISO you want to install from, I would recommend:

-drive if=pflash,readonly,format=raw,file=PATH_TO_OVMF_CODE_FD \
-drive if=pflash,format=raw,file=PATH_TO_PRIVATE_VARSTORE \
\
-debugcon file:ovmf.debug.log \
-global isa-debugcon.iobase=0x402 \
\
-chardev stdio,signal=off,mux=on,id=char0 \
-mon chardev=char0,mode=readline,default \
-serial chardev:char0 \
\
-device virtio-scsi-pci,id=scsi0 \
\
-drive id=sysdisk,if=none,format=qcow2,discard=on,cache=writeback,file=... \
-device scsi-hd,drive=sysdisk,bus=scsi0.0,bootindex=1 \
\
-drive id=installer,if=none,format=raw,file=... \
-device scsi-cd,drive=installer,bus=scsi0.0,bootindex=2 \

This will (a) capture the OVMF log; (b) give you access to both the QEMU
monitor and the guest's serial console -- switch between them with [C-a
c]; (c) create a virtio-scsi disk and CD-ROM for the guest, with the
(target) system disk and the installer ISO, respectively; (d) assign
bootindex=1 to the system disk, and bootindex=2 to the installer ISO.

The upshot is that when you first boot the VM, the installer ISO will be
launched (because the system disk is still empty), but after
installation, the VM will boot off of the system disk.

If there is a (QEMU default, or manually configured) virtual NIC in the
VM as well, then PXE boot will *not* be attempted. The reason is that
you assign a bootindex to at least one device, but no bootindex is
assigned to the NIC. This will cause OVMF to filter out any UEFI boot
options (created manually or automatically) that would refer to the NIC.

If the yakkety installer still doesn't boot with the above command line
snippet (*and* with the shim bug fixed or worked around), then I'd say
the installer ISO is malformed in some other way.


The second topic is why the shim bug doesn't hit hard on some physical systems. 
For this, consider how EFI_FILE_PROTOCOL.Close() works -- it releases the 
entire container structure that contains EFI_FILE_PROTOCOL. When you call 
FileProtocol->Close() next, using the same pointer -- i.e., use-after-free --, 
then the Close function pointer is read from freed storage.

As I mentioned earler, due to OVMF setting bit #3 (value 8) in
PcdDebugPropertyMask, memory that is freed gets scrubbed with the byte
value 0xAF. (Funnily enough, this hex value comes from the name of
Andrew Fish, the inventor of EFI.) So when you read the Close function
pointer from an EFI_FILE_PROTOCOL instance that has been closed
(released) already, you get 0xAFAFAFAFAFAFAFAF -- that's why you see
such an instruction pointer (RIP) in the register dump above.

Now, when shim executes the use-after-free (= the second close) on a
UEFI system that does *not* do the memory scrubbing on free, then all
the earlier contents of the freed EFI_FILE_PROTOCOL instance are likely
still in place. Hence the call probably corrupts memory elsewhere, but
it does not blow up at once. (Which is actually much worse bug
behavior.)

This is why you don't see any direct symptoms on physical machines:
memory scrubbing on free is a debugging feature, and none of the
physical firmwares in question enable it apparently. The upstream shim
commit that fixes the regression also mentions "This issue only affects
certain systems".

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

Title:
  yakkety: backport (or rebase to) fix eliminating a double-close in
  shim

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

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

[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim

[Laszlo Ersek (Red Hat)]

Also, I should mention in passing -- again -- that Launchpad is
completely retarded for truncating comments in the full bug view. It
doesn't offer any option to see both the full bug and full comments. How
stupid is that?! Are people who take the time to explain things in
detail really considered "verbose"? Do their comments really deserve to
be abbreviated in the full bug view? "Your comment is too long, so users
who care about it should click another link, and *replace* the full bug
view with a sole comment".

Screw you Launchpad.

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

Title:
  yakkety: backport (or rebase to) fix eliminating a double-close in
  shim

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

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

[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim

[Laszlo Ersek (Red Hat)]

@Jason -- according to the upstream fix (7052e7530755) that Yakkety is
currently missing, the upstream regression comes from upstream commit
4794822.

That commit (i.e., the regression) is between the 0.9 release and
14a5905. According to
,
the previous ubuntu shim version was "0.8-0ubuntu2", while the most
recent one is "0.9+1465500757.14a5905-0ubuntu1" (including the
regression but not its fix). So, in Ubuntu, it was the latest shim
rebase (dated "Tue, 26 Jul 2016 16:48:32 -0400") that introduced the
bug.

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

Title:
  yakkety: backport (or rebase to) fix eliminating a double-close in
  shim

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

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

[Bug 1624096] Re: yakkety: desktop and server ISOs wont boot under QEMU in UEFI mode

[Laszlo Ersek (Red Hat)]

Actually, I don't need to write any new patches, upstream shim has the
problem fixed already:

commit 7052e75307553edc8f04eb529b0d37844fbcc30b
Author: Benjamin Antin 
Date:   Mon Jul 18 12:28:12 2016 -0700

Don't close file twice in should_use_fallback error path

When fallback.efi is not present, the should_use_fallback error path
attempts to close a file that has already been closed, resulting in a
hang. This issue only affects certain systems.

This is a regression from version 0.8 and was introduced by commit
4794822.

Signed-off-by: Benjamin Antin 

You guys just need to rebase Yakkety's shim package on top of an
upstream git commit that comes after 7052e7530755. (Alternatively, you
can also backport 7052e7530755, but I guess Yakkety's release schedule
might allow another rebase at this point.) You are currently based on
14a5905, which does not include the fix.

** Package changed: debian-installer (Ubuntu) => shim (Ubuntu)

** Summary changed:

- yakkety: desktop and server ISOs wont boot under QEMU in UEFI mode
+ yakkety: backport (or rebase to) fix eliminating a double-close in shim

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

Title:
  yakkety: backport (or rebase to) fix eliminating a double-close in
  shim

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

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

[Bug 1624096] Re: yakkety: desktop and server ISOs wont boot under QEMU in UEFI mode

[Laszlo Ersek (Red Hat)]

I found the error in shim. It is a double-close (on error handling) of
the root directory of the filesystem. I'll submit a patch soon.

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

Title:
  yakkety: desktop and server ISOs wont boot under QEMU in UEFI mode

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

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

[Bug 1624096] Re: yakkety: desktop and server ISOs wont boot under QEMU in UEFI mode

[Laszlo Ersek (Red Hat)]

Add all three of the following options to your QEMU command line:

-debugcon file:debug.log \
-global isa-debugcon.iobase=0x402 \
-serial stdio

In the OVMF debug log, you will see that your boot loader is launched:

[Bds]Booting UEFI QEMU DVD-ROM QM3 
FatDiskIo: Cache Page OutBound occurred! 
FSOpen: Open '\EFI\BOOT\BOOTX64.EFI' Success
[Bds] DevicePath expand: 
PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0) -> 
PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0)/CDROM(0x1,0xC83AD,0x11C0)/\EFI\BOOT\BOOTX64.EFI
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 6C4D040
Loading driver at 0x6486000 EntryPoint=0x64A3000 
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 700E318

And on the serial console, you will get the register dump for the crash:

 X64 Exception Type - 0D(#GP - General Protection)  CPU Apic ID - 
 
RIP  - AFAFAFAFAFAFAFAF, CS  - 0038, RFLAGS - 0206
ExceptionData - 
RAX  - AFAFAFAFAFAFAFAF, RCX - 070176A0, RDX - 070176A0
RBX  - 06C4D018, RSP - 07AFBA28, RBP - 07AFBAE0
RSI  - 06534D9A, RDI - 06485FBA
R8   - , R9  - , R10 - 0020
R11  - 067E7180, R12 - , R13 - 06F883E8
R14  - 06F883F0, R15 - 07B1E9D0
DS   - 0030, ES  - 0030, FS  - 0030
GS   - 0030, SS  - 0030
CR0  - 8033, CR2 - , CR3 - 07A9A000
CR4  - 0668, CR8 - 
DR0  - , DR1 - , DR2 - 
DR3  - , DR6 - 0FF0, DR7 - 0400
GDTR - 07A88698 0047, LDTR - 
IDTR - 07442018 0FFF,   TR - 
FXSAVE_STATE - 07AFB680

The pattern AFAFAFAFAFAFAFAF is used to fill memory that's being freed,
for debugging purposes. So, your BOOTX64.EFI application dances fandango
on core.

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

Title:
  yakkety: desktop and server ISOs wont boot under QEMU in UEFI mode

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

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

[Bug 1582011] Re: Swap Failed, Indefinite hang on reboot/shutdown "Reached target Shutdown"

[Red]

I have now downloaded and installed 16.04 32-bit Ubuntu and it has the
shutdown problem. So, in my case, I do not have the problem if I use the
disk that was originally 11.04 and upgraded to continually to 16.04. I
only have the problem with a clean install of 16.04.

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

Title:
  Swap Failed, Indefinite hang on reboot/shutdown "Reached target
  Shutdown"

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

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

[Bug 1582011] Re: Swap Failed, Indefinite hang on reboot/shutdown "Reached target Shutdown"

[Red]

One addendum to the above, as a verification process, the 16-04 64-bit
install was repeated, each time discarding any previous contents on the
drive, just the eliminate any one-time glitches that might have
occurred.

Also, only Ubuntu and updates through Software Updater have been
installed. No extra software.

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

Title:
  Swap Failed, Indefinite hang on reboot/shutdown "Reached target
  Shutdown"

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

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

[Bug 1582011] Re: Swap Failed, Indefinite hang on reboot/shutdown "Reached target Shutdown"

[Red]

I first installed Ubuntu 32-bit desktop some years ago (I believe 11.04)
and have been upgrading it every six months. I am now up to 16.04 and
have not ever experienced this shutdown problem.

Since Chrome no longer supports 32-bit, I have downloaded 16.04 64-bit
(and verified the sha256).

I have burned the 64-bit to both DVD and thumb drives. I can boot live
from either and shutdown without a problem.

If I install to a brand new SSD, I hang during shutdown.

If I replace the SSD with the original HDD with 16.04 32-bit, I can
shutdown without problem.

I have found several suggestions on the Web to modify the
/etc/default/grub file to solve the problem. My two /etc/default/grub
files are identical so I don't see that as a problem.

None of the following work, they just hang:
  shutdown -h now
  shutdown -P now
  reboot -p
  sudo reboot -f (Just responds “Rebooting” and then nothing.)
  sudo halt
  poweroff

In summary, 11.04 (32-bit) upgraded to 11.10 upgraded to 12.04 upgraded
to ... 16.04 shuts down without a problem while 16.04 clean install
hangs.

Maybe, given time, I'll download 16.04 32-bit and do a clean install to
see what that will do.

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

Title:
  Swap Failed, Indefinite hang on reboot/shutdown "Reached target
  Shutdown"

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

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

[Bug 1597406] Re: Incorrect location of /etc/defaults in ceph systemd files

[Ken Dreyer (Red Hat)]

"/etc/default/ceph/ceph" is wrong and this needs to be
"/etc/default/ceph" everywhere. This has been fixed in Ceph upstream.

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

Title:
  Incorrect location of /etc/defaults in ceph systemd files

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

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

[Bug 1596063] [NEW] split server packages

[Ken Dreyer (Red Hat)]

Public bug reported:

Would you please split the yakkety ceph packages according to the split
that's happened in the upstream ceph.com Debian packaging?

"ceph" is now "ceph-base" "ceph-mon" + "ceph-osd"

** Affects: ceph (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/1596063

Title:
  split server packages

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

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

[Bug 1585008] Re: Windows 7 guests hang on bootup when qxl video is used

[Laszlo Ersek (Red Hat)]

This is a dupe of LP#1581936 and LP#1591724. The issue is fixed by
upstream QEMU commit 94ef4f337fb6.

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

Title:
  Windows 7 guests hang on bootup when qxl video is used

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

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

[Bug 1034989] Re: Wi-Fi doesn't connect; disconnecting causes "Connection Activation Failed (32)" dialog; reboot usually fixes it

[Red Bike Master]

I have to manually delete and re-add my Wifi every time I turn my laptop
on or resume it. I have to have it plugged in at all times, and awake,
to keep the connection up. The only was I can reconnect is to completely
wipe the config files for my network, then add it back using the
"Connect to a Hidden WiFi" option. I am running Ubuntu 15.04.

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

Title:
  Wi-Fi doesn't connect; disconnecting causes "Connection Activation
  Failed (32)" dialog; reboot usually fixes it

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

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

[Bug 1432644] Re: VM permanently tries to read /dev/shm/lttng-ust-wait-5

[Ken Dreyer (Red Hat)]

FYI ceph v0.94.6 will load LTTng-UST only when specifically configured.
This should avoid SELinux / AppArmor denials in most cases. See
http://tracker.ceph.com/issues/13274

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1432644

Title:
  VM permanently tries to read /dev/shm/lttng-ust-wait-5

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1432644] Re: VM permanently tries to read /dev/shm/lttng-ust-wait-5

[Ken Dreyer (Red Hat)]

FYI ceph v0.94.6 will load LTTng-UST only when specifically configured.
This should avoid SELinux / AppArmor denials in most cases. See
http://tracker.ceph.com/issues/13274

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

Title:
  VM permanently tries to read /dev/shm/lttng-ust-wait-5

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

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

[Bug 1445947] Re: 'pip3 list' throws AssertionError

[Red Ink]

A work-around would be great...

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

Title:
  'pip3 list' throws AssertionError

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

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

[Bug 1353940] Re: webgl no longer works

[Red hot smasher]

chromium-browser -disable-gpu-sandbox doesn't work anymore, just tells
me I'm using an unsupported command line parameter and has seemingly no
effect.

Someone in the discussion at
https://code.google.com/p/chromium/issues/detail?id=401106 claims
chromium-browser --single-process works but when I try that it tells me
I'm using an unsupported command line parameter and segfaults within ~10
seconds.

Apparently google-chrome exhibits the same issue (according to
https://code.google.com/p/chromium/issues/detail?id=401106), which means
either a) the same packaging issue is going on in both packages or b)
Google's developers are shifting blame because it's convenient, I dunno.
Needs fixing either way.

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

Title:
  webgl no longer works

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

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

[Bug 1432786] Re: upgrade of ceph in vivid breaks qemu-system-arm

[Ken Dreyer (Red Hat)]

The patch was merged to Ceph master upstream in
35c5fd0091fc4d63b21207fb94e46b343519fd56
(https://github.com/ceph/ceph/pull/4839)

** Bug watch added: Red Hat Bugzilla #186
   https://bugzilla.redhat.com/show_bug.cgi?id=186

** Also affects: ceph (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=186
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1432786

Title:
  upgrade of ceph in vivid breaks qemu-system-arm

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1432786] Re: upgrade of ceph in vivid breaks qemu-system-arm

[Ken Dreyer (Red Hat)]

The patch was merged to Ceph master upstream in
35c5fd0091fc4d63b21207fb94e46b343519fd56
(https://github.com/ceph/ceph/pull/4839)

** Bug watch added: Red Hat Bugzilla #186
   https://bugzilla.redhat.com/show_bug.cgi?id=186

** Also affects: ceph (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=186
   Importance: Unknown
   Status: Unknown

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

Title:
  upgrade of ceph in vivid breaks qemu-system-arm

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

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

[Bug 1281074] Re: updatedb.conf: CephFS should be included in PRUNEFS

[Ken Dreyer (Red Hat)]

** Bug watch added: Red Hat Bugzilla #1223582
   https://bugzilla.redhat.com/show_bug.cgi?id=1223582

** Also affects: mlocate (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1223582
   Importance: Unknown
   Status: Unknown

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

** Package changed: debian = mlocate (Debian)

** Changed in: mlocate (Debian)
   Importance: Undecided = Unknown

** Changed in: mlocate (Debian)
   Status: New = Unknown

** Changed in: mlocate (Debian)
 Remote watch: None = Debian Bug tracker #786433

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

Title:
  updatedb.conf: CephFS should be included in PRUNEFS

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

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

[Bug 1281074] Re: updatedb.conf: CephFS should be included in PRUNEFS

[Ken Dreyer (Red Hat)]

Wido, did you end up filing a bug with Debian on this? If not, I can do
so.

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

Title:
  updatedb.conf: CephFS should be included in PRUNEFS

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

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

[Bug 1221330] Re: FAT32 can't be mounted - IO charset iso8859-1 not found

[Red hot smasher]

(Running Ubuntu 14.10 (I'm gonna upgrade to Vivid as soon as I can be
bothered to) with lowlatency kernel)

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

Title:
  FAT32 can't be mounted - IO charset iso8859-1 not found

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

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

[Bug 1221330] Re: FAT32 can't be mounted - IO charset iso8859-1 not found

[Red hot smasher]

My system refused to boot after updating and after much debugging I
finally figured out how to get my hidden GRUB menu to show (ESC works
but neither shift key works for me). I edited the GRUB line to be able
to figure out what the error was and saw FAT-fs (sda2): IO charset
iso8859-1 not found (/boot is sda1 and EFI is sda2).

I tried booting from a previous kernel version (3.16.0-33) and it seems
to work, while the current version (3.16.0-34) gets stuck every time.

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

Title:
  FAT32 can't be mounted - IO charset iso8859-1 not found

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

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

[Bug 1411757] Re: update to latest msgpack-python release

[Ken Dreyer (Red Hat)]

Agreed, 0.4.6 is better :)

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

Title:
  update to latest msgpack-python release

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

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

[Bug 1411030] Re: backport support for unix domain sockets

[Ken Dreyer (Red Hat)]

Here's the patch that Red Hat ships to provide UDS support for their
httpd 2.4.6 package on RHEL 7. (This patch can be found in CentOS' git
repository, https://git.centos.org/log/!rpms!httpd.git/refs!heads!c7 )

** Patch added: Red Hat's patch for UDS support in httpd 2.4.6
   
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1411030/+attachment/4315849/+files/httpd-2.4.6-uds.patch

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

Title:
  backport support for unix domain sockets

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

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

[Bug 1411030] Re: backport support for unix domain sockets

[Ken Dreyer (Red Hat)]

Here's the patch that Red Hat ships to provide UDS support for their
httpd 2.4.6 package on RHEL 7. (This patch can be found in CentOS' git
repository, https://git.centos.org/log/!rpms!httpd.git/refs!heads!c7 )

** Patch added: Red Hat's patch for UDS support in httpd 2.4.6
   
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1411030/+attachment/4315849/+files/httpd-2.4.6-uds.patch

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1411030

Title:
  backport support for unix domain sockets

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1411757] [NEW] update to latest msgpack-python release

[Ken Dreyer (Red Hat)]

Public bug reported:

msgpack-python version 0.4.4 is out on PyPI. Would you mind updating the
Ubuntu packages to 0.4.4?

(It would be great to see a newer version in Precise as well)

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

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to msgpack-python in Ubuntu.
https://bugs.launchpad.net/bugs/1411757

Title:
  update to latest msgpack-python release

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs