Your message dated Sat, 22 Aug 2015 15:54:41 +0200
with message-id <[email protected]>
and subject line Re: Bug#741083: Unable to configure SecureBoot settings
has caused the Debian Bug report #741083,
regarding Unable to configure SecureBoot settings
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
741083: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741083
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ovmf
Version: 0~20131112.2590861a-2
Severity: important
The OVMF SecureBoot configuration hangs. If I press ESC after boot,
select "Device Manager" and then "Secure Boot Configuration" just a
black screen appears and the configuration menu is never displayed.
The virtual machine is started with "qemu -bios /usr/share/ovmf/OVMF.fd
-m 1g -enable-kvm". The same happens if I use
<loader>/usr/share/ovmf/OVMF.fd</loader> in my libvirt machine configuration.
The whole Tianocore configuration interface also feels a lot slower with
this version than with previous versions.
Downgrading ovmf to version 0~20131112.2590861a-1 solves the problem. As
nothing in the changelog suggests a change related to this, I wonder if
this is the result of a miscompilation. But a simple rebuild in a clean
sid chroot does not solve the problem.
Gaudenz
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (800, 'testing'), (700, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Steve
Steve Langasek <[email protected]> writes:
> Control: tags -1 moreinfo
>
> Hi Gaudenz,
>
> Are you still affected by this bug? stable is at version
> 0~20131112.2590861a-3 and unstable is at 0~20150106.5c2d456b-1, so if this
> problem you saw due to a miscompilation it may have been fixed in the
> meantime.
>
> If you confirm this is still a problem with the current versions, I will
> look at reproducing the problem. Locally, I can't reproduce the described
> symptom using a local build of a pending 0~20150106.5c2d456b-2.
I can no longer reproduce this issue with the version in
testing/unstable. So closing this bug.
Gaudenz
--- End Message ---
