qt6 and vtk
by Theodore Papadopoulo
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
with
one of the libraries it provides and qt6 is problematic (well I do not
even pass
the cmake configury step as cmake errors on the mix of Qt5 and Qt6
libraries).
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).
Theo.
1 year, 5 months
blocks of random characters spewed during boot?
by Tom Horsley
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?
1 year, 5 months
Something keeps creating Events.json in my home directory
by Matti Pulkkinen
Hello
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
Fedora 36.
--
Terveisin / Regards,
Matti Pulkkinen
1 year, 5 months
Can't create msdos partition table without advanced partitioning?
by Tom Horsley
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?
1 year, 5 months
Re: It's a brick :-<(
by Barry Scott
> 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.
Barry
1 year, 5 months
F37 workstation live
by Bill Cunningham
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?
B
1 year, 5 months
Re: F37 workstation live
by Bill Cunningham
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
guess.
1 year, 5 months
Fwd: F37 workstation live
by Bill Cunningham
-------- Forwarded Message --------
Subject: Re: F37 workstation live
Date: Sun, 20 Nov 2022 19:45:18 -0500
From: Bill Cunningham <bill.cu1234(a)gmail.com>
To: Tom Horsley <horsley1953(a)gmail.com>
On 11/20/2022 7:14 PM, Tom Horsley wrote:
> On Sun, 20 Nov 2022 18:59:41 -0500
> Bill Cunningham wrote:
>
>> What should I be doing here?
> The innards of the iso image were different from f36. I can boot
> the .iso file itself directly from a grub2 entry with a little
> work. I've got a directory named "images" in a partition with the
> UUID of 7ad8f114-5b24-47bb-86c6-0b229519d76c and I use this grub2
> gibberish:
>
> set data_usb_uuid="7ad8f114-5b24-47bb-86c6-0b229519d76c"
>
> function set_data_usb_root {
> insmod ext2
> insmod gzio
> insmod part_gpt
> insmod part_msdos
> load_env bootvid
> set root='hd0,msdos2'
> search --no-floppy --fs-uuid --set=root ${data_usb_uuid}
> }
>
> menuentry 'Fedora Workstation Live 64-bit 37 (1.7)' {
> set_data_usb_root
> set isofile="/images/Fedora-Workstation-Live-x86_64-37-1.7.iso"
> loopback loop "$isofile"
> linux (loop)/images/pxeboot/vmlinuz
> root=live:CDLABEL=Fedora-WS-Live-37-1-7 iso-scan/filename="$isofile"
> rd.live.image
> initrd (loop)/images/pxeboot/initrd.img
> }
>
> This is all actually on a USB stick where I have grub installed,
> but with appropriate modification to uuid and partition numbers
> (from the hd0,msdos2 thing) it should work from a hard disk as well.
>
> I've got a slew of different iso files on the USB stick and menu
> entries for all of them, so it is handy to do installs as well
> as rescue operations. Takes a while to get it set up and working,
> but is quite useful once it works. I used this info to build it:
>
> https://wiki.archlinux.org/index.php/Multiboot_USB_drive
Whew, ok I see. I think myself, it would be simpler to just make a USB
with syslinux. Is syslinux becoming depricated? I myself never like
grub, especially grub2. I liked lilo but no one, at least, any big
distros are using it now. Thanks much Tom I will work on this. Is there
anything that can quickly be entered into the grub2 CLI to boot from?
B
>
1 year, 5 months
It's a brick :-<(
by Geoffrey Leach
I find myself in need of a bootable rescue disk that provides (at least)
disk diagnostics and disk wipe programs. (I have a F36 thumb - I assume
that it has neither)
Referrals would be greatly appreciated.
1 year, 5 months
F37 in Beta?
by Bill Cunningham
I noticed that the "beta" label was taken off of the latest fedora 37
release. I use rufus to create a fedora server net install and usually I
can create an ISO with it and all is fine. But it seems, when in beta, I
have to use 'dd' version to copy bit for bit to the USB to repair or net
install. That seems to be what I am having to do. I use 'fdisk /dev/sdb'
too and the contents say EFI partition names and GPT, my machine is an
old MBR.
Now all of this is really no big deal, but it all seems to be with
something still in beta. Is this true or my imagination? The grub gui is
different too than it is with a regular release stage. If I am right and
this is beta stuff? Is F37 then, still in beta? I usually wait until
after beta but I will use it anyway.
Bill
1 year, 5 months
