I just made a new install of VL 5.9 gold on a new partition and did a slapt-get --update followed by a slapt-get --upgrade. I did this with only "packages", "extra", and "patches" enabled.

After which I could no longer use vasmCC, either through gui or the terminal. (see pictures)

I was able to get things working again, via downgrading back to 1.06.

This bug may be alarming to some new users who simply want to upgrade there system, from what should be the safe sources.

I've just hit the same thing. Reinstalled 5.9 Standard to fix a few problems with the build environment (I was picking up updates from 6.0). I then did 'salpt-get --update' followed by 'slapt-get -upgrade'. Same repos enabled. I'm now getting exactly the same problem with VasmCC.

I think the vpackager in 5.9 works differently...I would do the same for vpackager, becuase of the fact that if you just did a re-install of 5.9, you probabbly have an old vpackager too

the only reason it works is because at the time it was being developed, the code for the gambas interpreter was so unstable, the devs included the specific libs that vpackager neds to run, this is no longer necessary, as gambas2 has gone final since then, and we have a solid interpreter for it.

I would upgrade vpackager too using the same method... remove the old one first (because it installs to a different place) and grab the new one

I think the vpackager in 5.9 works differently...I would do the same for vpackager, becuase of the fact that if you just did a re-install of 5.9, you probabbly have an old vpackager too

the only reason it works is because at the time it was being developed, the code for the gambas interpreter was so unstable, the devs included the specific libs that vpackager neds to run, this is no longer necessary, as gambas2 has gone final since then, and we have a solid interpreter for it.

I would upgrade vpackager too using the same method... remove the old one first (because it installs to a different place) and grab the new one

Ok, I'll do so as soon as I finish downloading the 5.9 Standard live iso

One thing I notice which may have some bearing - I still have entries in /var/log/packages for gambas-runtime-1.0.19-i586-1vl59 and gambas2-runtime-2.5.0-i586-1vl59. There is no sign that the older runtime was removed before the new one was installed. I may try uninstalling both packages and manually install the later version.

I don't remember the last time I looked at Vpackager - it was just the only thing I could think of that used the gambas-runtime.

One thing I notice which may have some bearing - I still have entries in /var/log/packages for gambas-runtime-1.0.19-i586-1vl59 and gambas2-runtime-2.5.0-i586-1vl59. There is no sign that the older runtime was removed before the new one was installed.

Both are included because vl-hot-config only works with the 1.x version.

One thing I notice which may have some bearing - I still have entries in /var/log/packages for gambas-runtime-1.0.19-i586-1vl59 and gambas2-runtime-2.5.0-i586-1vl59. There is no sign that the older runtime was removed before the new one was installed.

Both are included because vl-hot-config only works with the 1.x version.

There must be something wrong with one of the vasmCC entries in your system.This error is due to a missing image file for one of the entries...I bet if you click any other section on vasmCC it'll work fine, which means one of the .desktop files in /usr/share/vasmCC/utilities is pointing to a non-existant icon

There must be something wrong with one of the vasmCC entries in your system.This error is due to a missing image file for one of the entries...I bet if you click any other section on vasmCC it'll work fine, which means one of the .desktop files in /usr/share/vasmCC/utilities is pointing to a non-existant icon

I thought so also, but the bad string errors happen when any icon is clicked. Also I did download the source from google code, and get the same errors. Also VASM is totaly unuseable, and I tried to re install that one also. Hmm

The bad string errors are again due to *some* unrecognized text (for some reason) in the .desktop files.Try looking into /usr/share/vasmCC/The directories in there represent categories in vasmCC. Each .desktop file in these categories is read at the time you click on the category to render the icons and names. Look into these .desktop files to see if you find anything unusual. Maybe post one on to compare it to the same file on another system.