I am getting the following error message displayed before the
display of the grub boot menu, can someone explain to me what this means
and why it is occurring in F37 when it was never produced in F36, and
what I need to do to rectify it?
error: ../../grub-core/kern/efi/sb.c:169:prohibited by
secure boot policy
Is there a way to use vtk and qt6 together in fedora (36 in my case) ?
Currently vtk-qt.x86-64 links with qt5 libraries, so anything that links
one of the libraries it provides and qt6 is problematic (well I do not
the cmake configury step as cmake errors on the mix of Qt5 and Qt6
I understand that for now Qt5 and Qt6 are coexisting, but would there be
a way to extend
this coexistence to vtk-qt ?? This would definitely ease the migration
path from Qt5 to Qt6.
Thank's for any clue on how to achieve this (of course I can
recompile vtk locally, but I'd like to avoid that if possible).
New f37 install. Turned off rhgb and quiet boot options. Now
interspersed with the "normal" boot messages, I get blocks
of strange gibberish characters spewed on the screen from time
to time, like something just wrote a bunch of random binary data.
Doesn't seem to hurt anything, but it sure is strange.
Anyone looking at this, or is it too trivial to bother?
Something keeps creating a file, Events.json, in my home directory. It
only ever contains an empty JSON array, but if I remove the file,
something just creates it again. Has anyone seen this before? What
program could be behind this? This only started happening after I
installed Fedora 37 Workstation, and never happened to me before on
Terveisin / Regards,
Installing fedora 37 from workstation live iso to a virtual machine.
I couldn't find any way to partition a blank disk with a msdos
partition table without using the advanced manual partitioning.
Did I miss something, or is that the way it works now?
> On 20 Nov 2022, at 22:45, Michael D. Setzer II <mikes(a)guam.net> wrote:
> Not always the case. Going back to the old DOS days,
> believe the OS would try 3 times before giving the
> abort/retry/ignore error message, and sometimes many
> retires would get a good read...
To clarify the drive will not substitute a good block after a bad block read.
As you say tools like spinrite have smart algorithms in them to recover data
in spite of errors by looking at pattern in the raw data come from the disk
after multiple reads of the same block. Relies on the error patten changing
to gives clues to the bits that are probable right I recall.
Hum. I believe this has to do with the new grub policy. I used
rufus's dd option to copy the live workstation iso to a USB. When I boot
from this, I get the grub rescue mode. There is the 'grub>' prompt. I
must be really over looking something here. The same happens if I am in
fedora and using 'dd' from the CLI. What should I be doing here?
After updating F37 nut is unhappy, spewing this every couple of seconds:
Nov 21 06:48:28 monster.email-scan.com nut-server: Can't connect to
UPS [nutdev1] (usbhid-ups-nutdev1): No such file or directory
Interestingly enough, the XFCE desktop's panel has a widget that shows the
UPS and its charged status.
Today's project is to figure out what's broken, does anyone happen to know
what's up with this, and save me some time?
On 11/20/2022 8:06 PM, Tom Horsley wrote:
> On Sun, 20 Nov 2022 19:45:18 -0500
> Bill Cunningham wrote:
>> Is there
>> anything that can quickly be entered into the grub2 CLI to boot from?
> Probably if you're a grub2 expert, but I'm not I'm afraid :-).
Nor am I. I myself favored syslinux. But, must stay up with the times I