Gslapt doesn't function

[w2gnd]

I am running 5.9.1 standard edition on a Micron TransPort GX3 notebook with 1Gig of RAM and 20 Gig hard drive.  10G for root, 6Gig for tmp, and 4 for media.  My problem is with the Gslapt package manager.  When I attempted to access Gslapt, I got a message "Not enough free memory available".  I rebooted and double clicked the icon, the bottom of the screen showed the tumbling hourglass indicating that a process was working.........and then it stops. 

This has happened to me before with other applications and I simply reloaded the notebook.  But that's not fixing the problem.  Any ideas?

[overthere]

you may try opening the programs in a terminal..it may offer some additional error messages regarding the malfunction.
hope that is helpfull

[M0E-lnx]

That is rather odd.
I think you are running 5.9.1 SOHO though... STD did not get a 5.9.1 release, just a 5.9

Never the less, 1GB of ram should be plenty. I'm running 5.9 SOHO on 512MB RAM and it works just fine

In addition to overther's suggestion, would you post the output of of "free" (without quotes) and also "df -h" (also without quotes)

[rbistolfi]

I have had a problem once with vsuper launching itself recursively, I like to play with the scripts , you may want to check with htop which program is taking all your ram.

[w2gnd]

The output of df -h is:

Filesystem            Size  Used Avail Use% Mounted on
/dev/hda1             9.4G  4.9G  4.6G  52% /
/dev/hda2             5.6G  694M  5.0G  13% /home
/dev/hda3             3.8G   53M  3.7G   2% /tmp
tmpfs                 504M     0  504M   0% /dev/shm

I wish I could post the output of "free" but that happened only once before I couldn't access Gslapt.  I also found the executable file, Gslapt, in \usr\sbin\.  That doesn't work either.  And finally, my ability to troubleshoot this using the terminal is limited to the command I just posted the output of at the beginning of this reply.

[newt]

In a terminal, as root, try excuting '/usr/sbin/gslapt' to see if you have the same (no response) results.  Use the 'su' command to switch to root - you'll need to enter roots password when prompted; then '/usr/sbin/gslapt' should start gslapt.

[w2gnd]

Okay, I get the following output:

root:# /usr/sbin/gslapt
WORKINGDIR directive not set within /etc/slapt-get/slapt-getrc.
vector:/~
root:#

Needless to say Its still not working.

[newt]

What is returned when you run: 'cat /etc/slapt-get/slapt-getrc | grep WORKINGDIR'

It should be /home/ftp/pub/veclinux/packages

[w2gnd]

After running that command I get this:

root:# cat /etc/slapt-get/slapt-getrc | grep WORKINGDIR
WORKINGDIR=
vector:/~
root:#

[newt]

Try this:
In a terminal, 'su' to root
type 'medit /etc/slapt-get/slapt-getrc' - should start a graphical text editor with slapt-getrc opened
Make the WORKINGDIR line read: WORKINGDIR=/home/ftp/pub/veclinux/packages
Save and close medit.
Back in the terminal, as root, try '/usr/sbin/gslapt' again

edit: forgot 'packages' at the end of the path.... sorry

[w2gnd]

Here is what I get:

root:# medit /etc/slapt-get/slapt-getrc
-bash: medit: command not found
vector:/~
root:#

I tried getting into vasm via command line and got this:

root:# vasm
bad string content
bad string content
bad string content
bad string content
bad string content
bad string content
bad string content
bad string content
bad string content
bad string content
bad string content
bad string content
bad string content
bad string content
vector:/~
root:#         

I DID get a VASM administration window to open after the errors stopped but nothing appears to work so there's no output I can show you.

Question:  If the hard drive is working overtime on the notebook system but I'm not doing anything on it and I am using a wireless device, could someone be attempting to get into my home network?

[newt]

You could try: mousepad /etc/slapt-get/slapt-getrc

And if they fails as well then: nano /etc/slapt-get/slapt-getrc
should work.  You will use Ctrl-o to save, and Ctrl-x to exit.

Overall, it seems to me that something happened during your install of VL 5.9 Standard.  With slapt-getrc begin messed up, vasm behaving strangely, missing medit package, I wonder if a re-installation is possible.  If you don't have any data invested in your current installation then you may want to try reinstalling VL.

BTW, when you did the initial installation did you run the 'file check' option?  I can't remember the name exactly but what I mean by the 'file check' option is the option that checks the data on the CD to make sure it's not corrupt.

Hope this helps.

[The Headacher]

I tried getting into vasm via command line and got this:

Oh yes, vasm is pretty messed up in 5.9.1 SOHO alright  . Not sure wat happened, but vasm is pretty much rendered useles in X..  .

I have seen the same thing on my computer, but I haven't tried fixing it. It's the result of hardly any testing on 5.9.1 SOHO before release  . The only good thing is, that VASM still works in CLI. You can use CTRL+ALT+F1 to go to commandline, login as root there and use vasm. It will use a textbased menu, which should work. When you're done with it, you can use CTRL+ALT+F7 to go back to X. It's ugly, I know.

mousepad /etc/slapt-get/slapt-getrc

medit and mousepad only came with standard. In SOHO 5.9.1, one of the nicest editors is kate:

Code:

kate /etc/slapt-get/slapt-getrc &

[edgeofthewoods]

I had the same issues in vasmCC in 5.9.1  Here is a fix for that one.

http://forum.vectorlinux.com/index.php?topic=5443.30

Moe was a great resource in fixing the Gambas and GTK++2

Chuck