AuthorTopic: No VASM from Console (Read 3962 times)

In VL-5.8 I can't use vasm from the console, neither as root nor as user. Giving the command just nothing happens, no pid is assigned no error message. Only when in X can I use vasm which is somewhat a problem if for example I want to change the graphic card.

Pita: vasm is where it should be and your PATHNAMES are fine, so I simply cannont understand why you cannot run vasm from a terminal. There must be something seriously weird about your system - it simply does not make any sense.

Logged

"As people become more intelligent they care less for preachers and more for teachers". Robert G. Ingersoll

I was going to recommend deleting or commenting out the line that says aspect = 0 in /etc/dialogrc but f—ing Seamonkey hung on me and I forgot what I was doing. (Seamonkey does not restore the session.) I'm slightly happier but still miserable with Firefox again. Flashblock has helped a lot in cutting the massive, massive bloat.

Out of sheer curiosity, does that file mention anything about 'aspect' this time?

Sorry, I rejoiced too early. Rebooting after reinstall vasm things were weird. Only root was mounted among others. Restore etc/ from back-up and back to square one.

Now in console if I do "xtrace /sbin/vasm" I get:

xterm XT error: Can't open displayxterm: DISPLAY is not set

In console "sudo xtrace /sbin/vasm" I get:

Function File Line--------------------------------------------------------------------------------Warning: This program is an suid-root program or is being run by the root user.The full text of the error or warning message cannot be safely formattedin this environment. You may get a more descriptive message by running theprogram as a non-root user or by removing the suid bit on the executable.xterm Xt error: Can't open display: %sxterm: DISPLAY is not set

So it seems my vasm only wants to open in X either from xterm or from menu-System-vasm.

I have uncommended now this aspect line, however, not yet rebooted and can now not check what happened.

Looking into the vasm-functions file I can see that there switches to run as TUI or GUI which seems to fail in my case.

I now copied the dialogrc file over from VL-5.9 in which one finds only references to colors rebooted and vasm starts now from the console.Epic Fail Guy (or was it hazzlemuzzle?) guess you were right about that aspect which is now all gone.