Just to make sure: you are referring to the 64 bit Debian package, not the 32 bit? The AppImage is always 64 bit, at least now. MatN On Mon, 28 Jun 2021 10:32:20 +0200 david via Cin <[email protected]> wrote:

El lunes 28 de junio, Спицын Андрей via Cin escribió:

...

Hi, David.

I tested latest AppImage on my debian testing laptop. I cannot confirm this behavior. Does older package launch a segment violation error?

Last cin Debian package worked perfectly.

David, OK, I will boot the Debian partitions here and see if I can duplicate the error. This will probably take me all day due to unfamiliarity with Debian. On Mon, Jun 28, 2021 at 9:39 AM david via Cin <[email protected]> wrote:

El lunes 28 de junio, Phyllis Smith via Cin escribió:

...

Have you tried this one instead: https://cinelerra-gg.org/download/images/C inGG-20210331-x86_64-older_distros.AppImage < https://cinelerra-gg.org/download/images/CinGG-20210331-x86_64-older_distros...

If that does not work, please let us know and I will try to boot a couple of different versions of Debian and see if I can duplicate the error.

It doesn't work neither :(

But I use Debian testing updated to last packages, so my system doesn't seem old at all.

-- David -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin

David, well the good news is that it did not take me all day but the bad news is that I can not duplicate the error. Here is what I tried and all worked correctly. However, I was "root" when testing. Debian 64-bit 9.1 (stretch) -- used the older distros AppImage for 4.9.228-1 (2020-07-05) as shown in "uname -a" Debian 32-bit 9.1 (stretch) -- used the older distros AppImage for 4.9.228-1 (2020-07-05) as shown in "uname -a" Debian 64-bit 10 (buster) -- used the older distros AppImage for 4.19-132-1 (2020-07-24) as shown in "uname -a" Debian 8 64&32-bit - unable to boot When AppImage "new" (as opposed to "older") does not work, it does not get that error message; it will get an error message similar to "GLIBC_#.# not found" or maybe some other library. I have to user older because I have not kept any of these systems upgraded. Alt/h hotkey for help is very nice so it would be really good for you to use the latest version. When/if you have time and would like to try to help analyze the problem, try the following: 1) It is possible that you $HOME/.bcast5 is somehow corrupted, so just to eliminate this, from a window keyin: CIN_CONFIG=/tmp/bcast1 /{location-where-you put}/CinGG-20210531-x86_64-older_distros.AppImage 1.1) Obviously you will not have your default settings, but at least it eliminate this as a problem. 1.2) If it fails (and even if it works) send the messages on that startup window so we can analyze further. 2) ONLY IF comfortable logging in and running as "root", try to run the older AppImage (the older will work on new systems). YOU MUST BE CAREFUL running temporarily as root, so do not do this if you are not to avoid ruining your work.

OK, I will boot the Debian partitions here and see if I can duplicate the

...

error. This will probably take me all day due to unfamiliarity with Debian.

Arg! I don't know how to help more :(

Yeah! I should have suggested this first and saved a lot of work. You can probably save some of your settings by looking at $HOME/.bcast5/Cinelerra_rc but it is quite voluminous and hard to edit. I would still save a copy of it temporarily in case you can not remember your settings for something specific. On Mon, Jun 28, 2021 at 11:53 AM david via Cin <[email protected]> wrote:

El lunes 28 de junio, Phyllis Smith via Cin escribió:

...

1) It is possible that you $HOME/.bcast5 is somehow corrupted, so just to eliminate this

This resolves problem. Now I need to remember my preferences and reconfig cinelerra. Thank you :)

-- David -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin