No I am not logged in as root. I realised when I posted that I did the startup attempt as su
I struggled to figure out the run command for Avidemux in konsole, then I went su
did an updatedb
and locate avidemux
and from the result here I guessed that I needed the avidemux2-gtk
The story is a little bit more complicated than originally posted:
A little thing that also happened when I started LXDE today was Opera requesting I agree to the License, the ask that normally happens when Opera is freshly installed. (I just can't do without Opera, so that is another install, Opera always going in early when running in a new system KiCAD, Opera, AvideMux and FileZilla).
Before trying to run AvideMux, I had used FilZilla to connect to my NAS box and copy a 5.7GB video file to the "Movies" directory, forgetting I am running LXDE in my testing size partition of about 10-15GB, this is normally fine for testing but since I have started to be a bit more interested Movies and Video a few big files soon bust the boundary. This happened here, Filezilla terminated midway in the file I was transferring.
I realised that I had hit the limit, copied the offending section to another partition and removed the section to free up space. All went fine and LXDE kept running but for Avidemux would not start.
Thinking about it I also decided to re-boot to KDE-Mini and do a e2fsck -f
on the LXDE partition, could not hurt, the result did not show any problems.
When I considered re-installing AvideMux, this reminded me that the LXDE Repo List for some reason does not have the Australian "aarnet" mirror, which I have taken to use. I was using "heanet" in Ireland, does not really make sense for me as I am in Australia.
So I decided "tweak" sources list for LXDE by adding the "aarnet" (just copied the line from KDE-Mini) and after reloading I have re-installed AvideMux.
AvideMux is back running again, I will spare the post the result I get when starting in Konsole, most impressive size (since it works I have not studied the content but I have a copy).
I am assuming that most likely the odd circumstances I found myself in today had to do with hitting the partition limit and something srrewed up, but it is a guess on my part.
I will consider the problem solved, and mark the topic as such.