Calamares crash when installing OMA ROME

Support
1

Hello,

  • OpenMandriva Lx version:

DISTRIB_RELEASE=24.12
DISTRIB_CODENAME=ROME
DISTRIB_DESCRIPTION=“OpenMandriva Lx 24.12”
znver1 version, my CPU is “AMD Ryzen 7 5700X 8-Core Processor”

  • Desktop environment (KDE, LXQT…):

KDE (LiveOS)

  • Description of the issue (screenshots if relevant):

image
image1156×922 88.7 KB

When I click on “No swap” combobox, and I select "Swap (with hibernate), the installer crashes, and KCrash handler appears. When I install gdb, it produces the following stacktrace:

Application: Calamares (calamares), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f4f4e89dcf1 in QStandardItemModel::flags(QModelIndex const&) const () from /usr/lib64/qt6/lib/libQt6Gui.so.6
#5  0x00007f4f4f388032 in QAbstractItemView::currentChanged(QModelIndex const&, QModelIndex const&) () from /usr/lib64/qt6/lib/libQt6Widgets.so.6
#6  0x00007f4f4f3ca224 in QListView::currentChanged(QModelIndex const&, QModelIndex const&) () from /usr/lib64/qt6/lib/libQt6Widgets.so.6
#7  0x00007f4f4deeec64 in QObject::event(QEvent*) () from /usr/lib64/qt6/lib/libQt6Core.so.6
#8  0x00007f4f4f0b2ff1 in QWidget::event(QEvent*) () from /usr/lib64/qt6/lib/libQt6Widgets.so.6
#9  0x00007f4f4f15b1bb in QAbstractScrollArea::event(QEvent*) () from /usr/lib64/qt6/lib/libQt6Widgets.so.6
#10 0x00007f4f4f380134 in QAbstractItemView::event(QEvent*) () from /usr/lib64/qt6/lib/libQt6Widgets.so.6
#11 0x00007f4f4f06bf8d in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt6/lib/libQt6Widgets.so.6
#12 0x00007f4f4f069c77 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt6/lib/libQt6Widgets.so.6
#13 0x00007f4f4de92b4d in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/qt6/lib/libQt6Core.so.6
#14 0x00007f4f4de9b092 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/qt6/lib/libQt6Core.so.6
#15 0x00007f4f4e197e04 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/qt6/lib/libQt6Core.so.6
#16 0x00007f4f4c18c495 in g_main_context_dispatch_unlocked () from /lib64/libglib-2.0.so.0
#17 0x00007f4f4c169964 in g_main_context_iterate_unlocked () from /lib64/libglib-2.0.so.0
#18 0x00007f4f4c1d5384 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#19 0x00007f4f4e19807e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt6/lib/libQt6Core.so.6
#20 0x00007f4f4dea3825 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt6/lib/libQt6Core.so.6
#21 0x00007f4f4de99d14 in QCoreApplication::exec() () from /usr/lib64/qt6/lib/libQt6Core.so.6
#22 0x0000563bde437831 in main ()
[Inferior 1 (process 5315) detached]

The same thing happens when I just change the filesystem in the combobox to the right.

A small dialog window appears for 2-3 seconds saying “enumerating devices” (or something similar), a circular progress indicator is working, and then it crashes.

  • Relevant informations (hardware involved, software version, logs or output…):

Outputs from # calamares -d kconsole 2>stderr.txt >stdout.txt:

stderr.txt (309 Bytes)
stdout.txt (82.3 KB)

  • Additional information

It works on Rock 5.0, I can select different combobox options, and I can change filesystems. After clicking “next”, the installer goes to another page properly. I didn’t start the actual installation though, so I’m not sure if it’s table until the end.

Under qemu, ROME Calamares doesn’t crash; I can select all items from the combobox and all filesystems just fine.

2

My first guess is a corrupted download or copy to flash drive or other media. I am not a developer but that output is indeed not normal. That output is complaining about missing .so files which points to something missing on the iso install media.

So I would try downloading again, for sure check checksums, perhaps not downloading with a browser downloader. And also how you copy to install media matters, not just everything works. You should tell us how you downloaded and copied.

Downloading an OMLx .iso file from terminal (Konsole):

wget path_to_.iso
or
wget copy_and_pasted_link_to_.iso

or you can use curl or aria2c instead of wget.

This is from Release Notes:

: Booting from USB

It is possible to boot this release from a USB storage device. To create the live/installation media you may:

  • Use isowriter tool available from our repos:

sudo dnf --refresh install om-imagewriter

Or, if you do not have OpenMandriva Lx yet, you can get rosa-imagewriter download links at this page.
At least 4 GB of flash drive capacity is recommended. Persistent storage is not necessary. Note that this will erase everything on your USB!

Please do not use other usb-writing tools as some Windows tools (e.g. Rufus) truncate the volume name. This breaks the boot process.

  • Via dd
    You may alternatively dd the image to your USB stick:

sudo dd if=<iso_name> of=<usb_drive> bs=4M conv=fdatasync status=progress

Replace <iso_name> with the path to the ISO and <usb_drive> with the device node of the USB drive, i.e. /dev/sdb.

  • SUSE Studio ImageWriter and Balena Etcher have also been tested and work to transfer ISO images to USB storage device.
  • Ventoy is not fully supported. Under some circumstances it may or may not work. Please create the live/installation media choosing one among the suggested methods here above. See ROME Errata for Ventoy workarounds.

If problems continue:

What to do if there is a problem installing OMLx

Another alternative is OM-Chat the OpenMandriva channel is user channel and OpenMandriva Cooker channel is developer/contributor channel.

And finally if these issues persist you can file a bug report.

3

I would suggest to format or delete the partition where you want to install before start installation.

Under some circumstances the Calamares installer may not be able to perform some tasks (like for example to change the file system). So let’s give it a clean partition to begin with.
You can use the kde Partition manager from live mode, or use gparted, or what you prefer.

4

Thanks for the suggestions. I’ve verified the checksums and they were all OK. I’ve written the USB stick on macOS with the “Etcher” app, which also seems to verify if the write succeeded. I was about to follow @rugyada suggestions, but I think I’ve found the problem.

I’ve accidentally booted up the image using the legacy BIOS mode. When I boot it up as UEFI, the installer doesn’t crash anymore. It’s 100% reproducible for me – when booted as BIOS, it crashes, when booting as UEFI, it doesn’t crash.

I should be booting as UEFI anyway, so the problem can be marked as solved :slight_smile:

1 Like
5

Please let us know.
Preferably write down the steps exactly you did in order to get the issue resolved, so that it would be helpful for the others.
If not already covered, the how-to may well go to Resouces too.
Thanks.

6

FWIW you can mark problems as solved in your posts with the checkmark under the post with the solution. I went ahead and did that this time. Flexing my power as mighty moderator. (Actually sometimes I forget I am a mod)

7

Just FYI, this is the boot selector on my machine (Gigabyte AORUS X570S):

IMG_5101
IMG_51011920×1440 295 KB

SanDisk is my USB Stick with OpenMandriva written to it. The “SanDisk” entry boots OMA in the BIOS mode, and I was using it when the installer was crashing. When I booted up “UEFI: SanDisk”, it booted in UEFI mode, and everything worked and installed correctly (I’m writing this on a properly working OMA). That’s about it :slight_smile:

1 Like
8

the boot for install UEFI is always Uefi:< vendor name USB > Partition 2

1 Like