Please login or register.

Login with username, password and session length
Advanced search  


Visit our home page for VL info. For support and documentation, visit the Vector Linux Knowledge Center or search the Knowledge Center and this Forum using the search box above.


Do applications using gksu have trouble restarting on your installation, and is ENV set?

No trouble restarting, ENV not set
- 0 (0%)
No trouble restarting, ENV is set
- 0 (0%)
There's trouble restarting, ENV is not set
- 1 (100%)
There's trouble restarting, ENV is set
- 0 (0%)
There's trouble restarting, not sure if ENV setting is correct
- 0 (0%)

Total Members Voted: 1

Voting closed: June 18, 2010, 09:27:48 pm

Author Topic: applications using gksu won't restart  (Read 1762 times)


  • Vectorian
  • ****
  • Posts: 774
  • it's enough
applications using gksu won't restart
« on: June 13, 2010, 09:27:48 pm »

I'm having the problem described here

Basically, applications which call gksu for root priveleges will start the first time, but often won't restart after they're closed. If one runs

ps aux | grep gksu | grep -v grep

the "non-started" application will appear on the list with a "?" where the user's display identifier should be for programs that use a display. I usually have the problem with GSlapt or VASM (I don't have VasmCC).

I'm beginning to think it's a problem of gksu being started in an uninitialized environment, or environment changes supposed to have been made by the first gksu run aren't being retained. This would explain apparently unrelated bugs, as well. I just don't have the computer to test this in different versions, applications, situations.

Anyone who is or is not having this problem can help. Please take the poll. Easiest way to find your ENV setting is do "echo $ENV" in a terminal: xterm, konsole, rvxt, etc.

I get this:
Code: [Select]
sixforty:$ echo $ENV

which is to say, "nothing there".

If a clear pattern emerges, the poll can be closed. If you have more than one VL installation, please test it on 2 or 3 of them if you have time. If you get different answers on different installs, please select an option for each result, up to 3. You can also change your vote.

The other option for the source of the problem is trouble accessing an .Xauthority file. That one's beyond me just now; I'd need additional help.

Thank you.
« Last Edit: June 13, 2010, 10:10:43 pm by sixforty »