On Sun, Sep 24, 2023 at 1:36 PM Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx> wrote: > > Martin Gansser writes: > > > I have copied the virtual machine from a Windows computer to my Fedora 38 > > computer and shotcut can no longer be compiled here, but it can on the > > Windows computer. > > Do I have to repair the file system on the Linux computer or do anything > > else? > > You snipped out the relevant details of the filesystem being corrupted due > to a likely RAM error. > > The bad RAM could be on either machine. If the bad RAM was on your Windows > computer, you copied it off unstable hardware, and your entire VM's > integrity has been compromised in some unknown way. > > You might try making another copy of the VM, and if you don't end up with > identical corruption it likely indicates that the bad RAM corrupted the > data in transit, and the original VM image is /probably/ ok. However until > you isolate and replace the faulty RAM you can't really do anything with > some guarantee of stability. Only after identifying and replacing the faulty > RAM you can then make another copy of the VM with some level of confidence. Other than that, I'm not sure why this needs to be built inside a Fedora VM on a Fedora host. I would first try building with mock on the Fedora host *outside* the VM. Fabio _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
