I did a fresh install with a Manjaro Gnome 6.5 kernel iso, tried Kdenlive appimage, and it worked.
Then I did an update without touching the GPU stuff, and I was back in the same predicament. That cuts out a lot of user-induced problems.
I can’t remember if I tried the package manager and AUR route at the time. I assume I did not, which I find unfortunate now.
The installation process didn’t go smooth as described in this comment I made today.
Regardless, remember, Kdenlive worked after plowing through the installation. Only after updating, it stopped working.
I’ve done all I can do to give clues to what could be going on. I certainly don’t know.
This is an old laptop but it works fine. 2.7 GHz quad core does the job without me having to wait all day. Sure, a newer laptop would be nice, but that’s for later.
@wongs No, it means I did not open Manjaro Settings and execute an Auto-install proprietary drivers.
@wtechgo you can get today’s build of stable branch ISO and just install kdelive in the live-session to check if everything works with the latest package updates. This way you don’t change your internal installation at all: Release 202312100136 · manjaro/release-review · GitHub
That user is also this user, with an alternate account.
You hadn’t mentioned it was a laptop; I imagine that only compounds the complication. Is this laptop also the Windows multiboot system you mentioned? I took it to mean you had a separate multiboot system.
It’s a laptop with Intel-Nvidia hybrid, meaning an Intel GPU and a dedicated Nvidia GPU, hence Bumblebee390.
It’s a multiboot install on an SSD of 512GB with two partitions, one for Windows (first) and one for Linux, as recommended and executed by Manjaro iso install process, a long time ago.
Are you sure? Nvidia 535 doesn’t seem to specifically list the GT 740m as being supported. These driver versions seem to be the latest supporting the GeForce GT 740M (Notebooks):
Noteworthy, my password did not authenticate which I worked around by resetting it as root in live USB env.
Once booted from disk, system time was 1 hour in the future, fixed that.
Then, I ran update and got the arch-keyring error, no permission to write to file or can’t find file, it says.
Now I have commands to work around that too, but last time I did that, I ended up stranded.
I’m running memtest86 atm and will continue with the arch-keyring commands when that finished successfully, like resetthe keyring and do an init of the keyring.
However, when things don’t go smooth from the get-go, it’s often bad news.
If somebody has some inputs on the situation, shoot.
Kdenlive works now and I think I’m going to like KDE more than Gnome.
I only need to re-install and reconfigure everything…
That’s my fault though, because I didn’t back up my home directory with all the config files. Big mistake.
It most likely does, but the second you start to do strange things like:
And then install, you are no longer in a “fresh install” state.
Ehm, in this case I actually HOPE you were in chroot or yeah, trying to change the password for the user on the usb stick is no good.
Finding out the REASON it happens would be very important thugh, because that to me is a big warning signal that something is VERY wrong.
If I suddenly lost access to my system I would want to know EXACTLY why.
It seems that everything boils down to you doing strange things, and when the user does strange things, the system will react back with strange things.
And I say it again, without us knowing EXACTLY every step of how you do things, there really is nothing we can do.
If you consider you have solved the problem, please pick a post and select that as the “solution” so the thread will close.
I don’t do manjaro-chroot -a before the installation (in live USB env). I do it after the installation ran an threw this error at the end, after it has written the whole OS to disk, but failed to write GRUB.
Error: The bootloader could not be installed. The installation command <pre>grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Manjaro --force</pre> returned error code 1.
The only thing I haven’t mentioned is, that during the Live USB session to re-install Manjaro , I chose ‘replace partition’.
From the command manjaro-chroot -a and onwards, I barely know what I’m doing. For all I know, GRUB wasn’t built or configured correctly. I don’t know why and I don’t know much about GRUB, /boot/efi etc.
I don’t think I do crazy things in general on my system. Only now when I’m trying to navigate my way out of this situation where I cannot continue working. From my perspective, Kdenlive just stopped working for no clear reason.
I create truthful audiovisual content, hence controversial these days… There definitely are people that don’t like what I’m doing, but my conscience is clear. I wonder if these issues could have been caused by an attack.
I’m not very advanced in Linux. I’ve only been using Manjaro as my daily driver for two years, without Nvidia drivers but still better than Winblowz.
There we go, THAT is the issue, but you have to my knowledge not communicated that very clear. It means you are NOT on a fresh install, you are on a BROKEN install.
If you had provided logs like people requested very early in this thread, it would probably have been solved long ago.
To me that error indicates you have something not correctly set in bios.
Make sure:
update your bios firmware if available
Efi is enabled
Fast boot is disabled
Secure boot is disabled.
Then reinstall.
I can not advice how to install since you, again, have not provided information more than “I choose replace partition”. We have NO IDEA, how many partitions you have, how many disks, other operating systems, what filesystem you choose etc etc etc.
Just by finally showing that I can identify that you use the windows boot partition to try to install grub, that might be the issue.
I do not know if it is sda5 or sdb3 that you want to be your root.
If you are asking for help?
I would prefer a lsblk -o name,fstype,size,label and a description of what you think the different partitions are and what you want to achieve.
I also want you to confirm you have checked for bios updates, issued them if they existed and then configured bios as I instructed here
Without that, everything is pointless.
annoying, but yes, they need to be catenated.