I’ve burned the most recent KDE image to a usb drive formatted as NTFS using Rufus on Windows 10.
I can boot from the USB drive, but when I click on the Install Manjaro application on the desktop nothing happens.
I noticed that, just before the KDE desktop appears, the spinning wheel on the loading screen is distorted (meaning I only see a rotating square of randomly-colored pixels)
I installed Manjaro on this PC less than 2 years ago, so I doubt there are any hardware incompatibilities.
Clicking “Launch installer” on the Manjaro Hello window has the same effect (i.e. none).
If I run the install application from the commandline what I get is>
> /home/manjaro/Desktop/calamares.desktop
/home/manjaro/Desktop/calamares.desktop: line 1: [Desktop: command not found
/home/manjaro/Desktop/calamares.desktop: line 4: Manjaro: command not found
/home/manjaro/Desktop/calamares.desktop: line 5: `Name[da]': not a valid identifier
/home/manjaro/Desktop/calamares.desktop: line 6: Installer: command not found
/home/manjaro/Desktop/calamares.desktop: line 8: the: command not found
/home/manjaro/Desktop/calamares.desktop: line 9: `Comment[da]': not a valid identifier
/home/manjaro/Desktop/calamares.desktop: line 10: `Comment[de]': not a valid identifier
/home/manjaro/Desktop/calamares.desktop: line 11: fg: no job control
/home/manjaro/Desktop/calamares.desktop: line 16: System: command not found
The contents of the calamares.desktop file are as follow>
[Desktop Entry]
Type=Application
Version=1.0
Name=Install Manjaro Linux
Name[da]=Installer Manjaro Linux
GenericName=Live Installer
GenericName[da]=Live-installationsprogram
Comment=Install the operating system to disk
Comment[da]=Installer styresystemet på disk
Comment[de]=Manjaro Linux installieren
Exec=/usr/bin/calamares_polkit %f
Icon=calamares
Terminal=false
StartupNotify=true
Type=Application
Categories=Qt;System;
If I try to run the command specified in that file I get this>
1. Download the latest available Manjaro ISO for your chosen DE; do not use any other you might still have from previous installs; this is important. The splash screen issue you describe has already been addressed (fixed) on the latest ISO.
2. It’s possible that Rufus will fail to write a good copy of an ISO to the USB. Using Ventoy instead is strongly recommended. Search the forum for information.
So, basically, perform a new installation using the latest ISO, and from a Ventoy USB, and you may have better luck.
Hi @carllacan and welcome to the Manjaro community.
As a new user, please take some time to familiarise yourself with Forum requirements; in particular, the many ways to use the forum to your benefit. To that end, some or all these links will be invaluable:
Thank you both for your help, I managed to reinstall Manjaro!
I’m not sure what was the problem, though.
Ventoy is a pretty cool tool. When I used it to book the most recent iso the install application worked.
However in my previous attempts I had also used the most recent iso, and I verified that the sha256 was correct, so that wasn’t the problem.
Furthermore, the bug with the spinning wheel in the splash screen persisted, even in the most recent iso (manjaro-kde-24.0.3-240702-linux69.iso)
There’s also another bug that I forgot to describe in my first post when you select “Edit boot options” in the boot menu: instead of showing the boot options the menu item right below “Edit boot options” (I forgot what it said originally) changes to “Edit boot options” too. If you select this item then the original “Edit boot options” changes to “Edit boot options Edit boot options”, and every time you select it it adds another “Edit boot options”. It’s quite bizarre.
In conclusion: burning the iso with Rufus seems to have been the problem, given that switching to Ventoy fixed it. However I still observed a couple bugs. Should I make a bug report somewhere?
I think since it will “burn” the ISO, the initial file system is irrelevant as it will write the ISO and its file system, unless Rufus changed how it works.
Maybe they are not bugs, open a thread, or reply here to list the issues then you may see what to do from here.
I’m honestly not sure either, but I am under the impression that it does do something to the way the .ISO is incorporated. … when I used it way back when, it took some experimentation to get it working.
It was probably because of the tickbox you needed to check for the Manjaro ISO to be working with RUFUS, it is long time I can’t recall everything but it was needed to not do the same way as other distros, for Manjaro.
Indeed. This can happen for a variety of reasons; bad/cheap USB drives; incorrectly seated USB drive; humidity; etc.
Ventoy avoids issues related to writing an ISO to USB, simply by not doing it. Naturally, I’d still recommend comparing the ISO with the provided checksums.
That’s not the case here; I can’t reproduce it in Plasma 6; the spinner spins as expected. A possible workaround is to disable the splash screen entirely, or choose another.
As bizarre as your description seems to be, I cannot reproduce that either. Choosing E (Edit Boot Options) in the GRUB menu takes me to the options to be edited (dependent on which menu option is highlighted), as expected.
Generally speaking, if a condition cannot be reproduced, it’s not a bug; it’s likely caused instead by … something … specific to your machine; usually configuration.
The best path forward is to create a new thread (if you think it’s warranted) and see if anyone else experiences the same issues when performing a fresh install using the new ISO.
This thread has a solution; the suggested use of Ventoy (instead of Rufus) to perform a new installation. All that remains is for you to mark the appropriate thread as the solution (using the under the post).
& @carllacan for your perusal:
Indeed, and you can actually use the sha256sum -c on the copied .ISO on the USB stick itself, to confirm it has been written correctly. That’s worth pointing out to people using this method here. AFAIK more awkward or impractical on a USB created with Rufus or just by simply using dd as I’ve done in the past.
Easiest way is to simply copy the sha256sum file to the Ventoy stick and then run the command I posted directly on that, by navigating to the device in your Terminal. You can also probably add the path to the command, but I have not tried that yet.
… when I used it way back when, it took some experimentation to get it working.
under the post).
AFAIK more awkward or impractical on a USB created with Rufus or just by simply using