Cinelerra-gg AppImage doesn't show my mounted drives

Skywalker71 · November 18, 2024, 8:49am

A weird problem I am facing regarding ‘AppImage’. I tried to install Cinelerra-gg and the command they have given here: Fedora - Cinelerra GG did not work. See the image below:

I have found that currently they are only releasing AppImage packages. Now from the image below, you will see the nature of the problem:

In this image in the red marked ‘A’ section on the left hand side, you can clearly see that the drives are mounted successfully. But on the right side, in the 'Load section of Cinelerra AppImage no drive is showing. This same problem happened in Kdenlive AppImage package. Flathub packages also suffering from this problem. In KDE forum, people showed that their AppImage is showing everything okay. But not in my OS. Why is so?! What am I doing wrong?! Or, what am I missing?! Please help me to solve this. For my OS specs, please see the image below:

kovacslt · November 18, 2024, 10:15am

Your mounted drives -mounted AFTER you logged in- should be somewhere in /media/skywalker/…
There you’ll see the volume name, or if is empty, the UUID of the mounted volume.
So something like
/media/skywalker/WD1TB
or /media/skywalker/99035d45-dad3-436f-9058-1e944a85c5f0
(UUID is just an example here)
Navigate to these directories to find them, or if you want to make it real easy, create a simlink to them in your home.
I do it with my most frequently used external drives.

That is something like
ln -s THE_DIR_TO_SHOW /media/skywalker/the_drives_mount_point

Now when you look at the link, it will behave as a directory.
Once you disconnect the drive, the link becomes a broken link, but whenever you mount the same drive again, the link will work as before.
I find this a very convenient way to acces data on different drives.

Skywalker71 · November 18, 2024, 10:44am

Should I write it in the fstab file?

kovacslt · November 18, 2024, 10:49am

Oh, no!
It’s a command, that creates a simlink.
Of course I messed up…
I should have tried it before posting…

ln -s /media/skywalker/the_drives_mount_point THE_DIR_TO_SHOW

This should be a one time command.
The link stais, the drive may come and go…
If you want to put it into the fstab, the drives should be always present.

nevj · November 18, 2024, 11:48am

I thought fstab was only for mounts, not commands
You should not need to do an ‘ln’ every time you boot… do it once it is permanent
or
did I misunderstand you?

kovacslt · November 18, 2024, 12:35pm

Reading back it seems I worded it wrong (again).

You are right, fstab needs mounts, not commands.

Creating the link is a one-time process, it needs to be done only once, assuming the mount point does not change.
Mount point may change if the label of the volume is changed for example, or the volume is reformatted (UUID changes).

It is possible to edit fstab, so that the system automounts the drive on startup, but it is a less flexible way.
Generally, if the drive is built-in, I prefer to have it in fstab, but not the external disks. Adding external disks to fstab is a technical possibility, but I find it rather risky, not practical.

Skywalker71 · November 18, 2024, 7:57pm

Why all the strange things are happening with me???!!! Earlier I used gparted to partition my 500gb SSD in two equal parts, say A and B. Both were formatted in ext4 filesystem. Then I installed Fedora from scratch in partition A. I mounted the B partition using ‘fstab’ and it properly automounted. But I could not create any fike, folder in it. I will give you guys (and gals) all the steps I followed, tomorrow as I always write down the command I use, its purpose and sometimes its result(s) and that file is in my computer and it’s shutdown as it is 1:24 am here and I am writing from my phone. So, goodnight to you all. See you tomorrow.

nevj · November 18, 2024, 10:28pm

Are you sure you formatted it. ?
Does it contain a filesystem?
You should see lost+found if it has an ext4 filesystem.

daniel.m.tripp · November 18, 2024, 10:55pm

You probably don’t have write permission to the mount point.

Example : you mounted /dev/sdb2 in /mnt/mydrive

e.g.
sudo mount /dev/sdb2 /mnt/mydrive

Preferably you should set the owner of /mnt/mydrive BEFORE you mount it so - correct order :

sudo umount /mnt/mydrive
sudo chown $MYUSER:$MYGROUP /mnt/mydrive
3. let’s say your User ID is 1000, and your default Group ID is 1000
4. sudo chown 1000:1000 /mnt/mydrive
5. and maybe even :
6. sudo chmod 775 /mnt/mydrive
sudo mount /dev/sdb1 /mnt/mydrive

Note above - in the “olden days” one should need to specify the filesystem type and perhaps some other options… But Linux is smart enough these days to figure out what filesystem the device hosts (e.g. /dev/sdb2 is ext4).

If above doesn’t work, maybe try mount with “rw” as an option :

sudo umount /mnt/mydrive
sudo chown $MYUSER:$MYGROUP /mnt/mydrive
3. let’s say your User ID is 1000, and your default Group ID is 1000 (you can find your UID and GID with the “id” command :

╭─x@titan ~/wiz/HZP  
╰─➤  id                                                                                                                   1 ↵
       uid=1000(x) gid=1000(x) groups=1000(x),4(adm),27(sudo),44(video),123(lpadmin),134(vboxusers),2000(pwn)

sudo chown 1000:1000 /mnt/mydrive
sudo mount -o rw /dev/sdb1 /mnt/mydrive

What I usually do when I’ve successfully mount an internal partition - I check the entry in /etc/mtab and append it to /etc/fstab - BUT ALWAYS MAKE A BACKUP OF /etc/fstab before changing ANYTHING!
e.g. sudo tail /etc/mtab

If that looks good - I make a backup of /etc/fstab
sudo cp /etc/fstab /etc/fstab.bkup.YYYYMMDD
then :

sudo -i
tail -1 /etc/mtab >> /etc/fstab

(tail -1 only shows the last line of the mtab file - and only appends the last line to fstab)

pdecker · November 18, 2024, 11:36pm

I get that backward almost every time too.

Skywalker71 · November 19, 2024, 4:10am

100%. After partitioning, I specifically formatted it with ext4 filesystem and without any mounting point. As Davinci Resolve, Kdenlive AppImage could not access any of the mounted drives, I thought may be formatting the partition with ext4 filesystem and make it automounted might solve the problem of the drive inaccessibility. So, I formatted it with ext4 and automounted it using fstab. But, the problem remained. I don’t know why all the weird problem is happening with me??!! First, Debian could not detect the USB 2 ports. Then DR could not recognise RX550. Then AMDGPU PRO could not be installed. Then this AppImage problem. I could not understand what’s wrong with my syatem. May be my decision of switching to Linux was bad. But I don’t know about any other OS in which I can do my works. I am superbly frustrated at this time.

Skywalker71 · November 19, 2024, 4:22am

EXACTLY!!! After mounting it through fstab, when I tried to create a file / folder in that drive, it showed ‘**You have no write permission… **’. When I accessed the drive as administrator, I could create file / folder in it but could not understand how to make it permanent. Now the problem might be solved. Thank you Dan @daniel.m.tripp.
Oh! I am sorry. I forgot to mention that after being unsuccessful to automount the drive, I formatted it again with exFAT. I don’t think that it will make any difference, right? Though I will know when I will do all the steps.

Skywalker71 · November 19, 2024, 8:50am

@kovacslt, @nevj and @daniel.m.tripp Some more weird things I should report.

1st WEIRD thing:

After updating to Fedora 41, whenever I switch to Fedora from Windows, the Grub menu shows with different versions of the kernel. See the image below:

Now, if I try to boot into 6.11.7 kernel it shows this:

At this point, if I don’t touch anything, it boots into 6.11.7. See the image below:

But if I press any key, it goes back to the Grub Menu and then if I try to boot into any of the kernels, it shows this:

and then goes back to the Grub Menu. Then I have to press ctrl+alt+del to soft reboot and then it comes back to the Grub menu after rebooting. At this point, if I don’t touch anything, it perfectly boots into 6.11.8 which is the current version of the kernel. But, if I press enter to boot quickly, it will not boot. It will show the above error (see the image above).

2nd WEIRD thing:

As I never dual boot using the Grub bootloader, instead I use BIOS to boot into either OS, the Linux Grub menu never showed Windows. But yesterday I received a system update and after updating I am seeing Windows in my Grub menu. See the image below:

3rd WEIRD thing:

I tried to boot into Debian 12 live USB today. I got some info here: Why is USB not working in Linux when it works in UEFI/BIOS? - Unix & Linux Stack Exchange. In this page, see the 3rd answer which got 5 votes. That person had the same motherboard which I have. But, when I do as mentioned there, which is:

xHCI handoff - Enabled
EHCI handoff - Enabled
IOMMU controller - Enabled
UEFI - Disabled
All boot options - Legacy Only

Debian Live USB indeed booted using USB 2 port but could not recognize USB 3 ports and my keyboard and mouse which are connected in USB 3 ports got turned off. I could not do anything. So, I had to hard reset.

Now, what would be the solutions? If you want, I can create separate thread for each of the problems for future references. Please let me know.

kovacslt · November 19, 2024, 9:12am

The exfat is a good choice espaially if you intend to use that drive/partition both from Linux and Windows.

As for “automounting” it does not matter.
For make it it “automount”:
cat /etc/fstab

to see the current content of fstab.
sudo blkid

to see the list of blockdevices and their ID’s.

Just name the drive/partition you want to automount on boot, we’ll show you what to add to fstab.

Déjà vu

You got a kernel update, which when installed, updated grub configuration.
As os-prober was probably enabled, and the Windows drive was accessible, it found the Windows bootloader.
That’s harmless.

Now that’s really weird

Skywalker71 · November 19, 2024, 9:27am

I have edited.

kovacslt · November 19, 2024, 9:44am

Apart from that those ports should be working, why do you connect the slowest devices (keyboard, mouse) to the fastest ports?

iommu=soft maybe?
When booting Debian live add that kernel parameter!
Here’s a comic about it:

press Tab

add iommu=soft

press Enter, and let it boot.
Does the USB3 work?

Edit: you may even try iommu=off

daniel.m.tripp · November 19, 2024, 10:41am

I’d love to use exFAT - but - it doesn’t support soft (or hard) symlinks - so it’s out of the question for me…

I barely use Windows these days - it’s all Linux or MacOS - both support symlinks on whatever Apple is calling its filesystems these days (seems to contantly change) HFS or whatever - and ext2/3/4 - and ZFS!

So on the odd occasion my NAS or Cloud shares don’t work to share something - I just use Fat32 on USB drives - without symlinks… that sux… I still find it beyond comprehension why Microsoft wouldn’t use something so flexible as symlinks - for me that’s one of the “killer app” features of UNIX systems… it’s a killer feature…

Oh you can’t find that file - let’s just plonk a symlink to it here! e.g. SSL cert file… that’s quicker and way easier than editing some obscure text (or YAML) file…

Had a case just last week - some app wasn’t working right - oops - let’s plonk a symlink to the filename it’s expecting here - and woohooo - it worked! Try that on Windows - FUGGEDABOUDIT!

kovacslt · November 19, 2024, 10:58am

You can do it actually

(But that doesn’t mean I’ll return to Win anytime soon )

nevj · November 19, 2024, 11:18am

If an update installs a new kernel, it automatically does
update-grub
and that will run os-prober, which will find Windows and all the Fedora kernels that are present in /boot

That is OK, you can just ignore the Win grub entry if you dont want to use it. It is harmless.

Skywalker71 · November 19, 2024, 11:36am

Microsoft doesn’t want anyone to use any other OS which is really absurd. It seems they are going towards Intel’s way.