HiI had the same error trying to install...oops, I don't recall what I was trying to install:-(. I think it was vpackager, but I am not sure.Anyway, I just searched gslapt for that libffi, and installed it.

Until we can get a fixed gambas2-runtime package, I'd suggest simply installing it manually. It's not that hard...

Working fine. And looks good! Thanks.

Just one question. I found both the gambas-runtime and the gambas2-runtime packages installed. Is this alright, or could it cause some kind of conflict?

So far as I could see, both vpackager and vasmCC require gambas2 now, so I was wondering if anything else actually requires a version < 2 (perhaps vcpufreq?).If that's the case, it would be nice if it could be rewritten for gambas2... Wouldn't mind helping myself, although I would have to learn it (saw your "gambas calling", M0E)

Just tried to install this on a fresh 5.9 Std install and found another issue (besides the libffi dependency).It doesn't seem to be in the list of packages to be upgraded by slapt-get --upgrade, and I had instead to downgrade it.

I think it might be because the one that comes on the cd is wrongly numbered: 1.06, instead of 1.0.6, which makes slapt-get think 1.0.12 is a downgrade.

Of course, not this problem or that dependency can be solved by changing this package, so not much to be done.Just to let people know if they come across this issue.

When running freemem, in the shown panel the results aren't properly lined up, making it a tad hard to see the outcome in a glance.

I find the same... that seems to be a freemem (or zenity) issue.I find it gets a bit better aligned (though not perfect) and more easily readable, by replacing the two "free" commands in /sbin/VLFreeMem with "free -m"... if you're ok with Mb for the results.

I could not find anywhere else to post this. I looked at google codepage however you have to have an ID. Since I do not have I figuredto post this question that was posed to me:

I have encountered arelatively serious bug. As I am of Hungarian nationality, I prefer usingHungarian (exactly: hu_HU.UTF-8) language setting. I can set it inVector Control Center after the first install, but after rebooting (andso applying the hu_HU.UTF-8 setting), some functions of VCC getcorrupted, for example the whole Utilites section, and some more as well-- I found gibberish int /etc/rc.d/rc.inet3, for example, and myLOCALE variables got set to "GDK Warning:" (yes, that was their -- allof them -- value after giving the "locale" command on CLI -- I supposethey got an error message from VCC's graphical interface, or somethinglike that). And in the last line of /etc/profile.d/vasm.sh the LC_ALLvariable somehow doesn't take the value of LANG -- I had to change it tothe hu_HU.UTF8 constant to get my locale settings work.

Anyway this is the only bug that is worth of mentioning, VL 5.9 isbeautiful, stable and fast, congratulations to it.