VNC is not setting the correct DISPLAY= value

hackerError

I am running tightvnc on display :1

The window manager that I am using is fluxbox.

When I attempt to launch anything via the fluxbox menu, such as xterm, the program appears on display :0 rather than :1. If I manually run a program like this:

hackerError · Posted: Sat Dec 18, 2010 3:11 pm Post subject:

I created a test user, and the new user also has the same issue. This leads me to believe that there is a global config setting somewehre doing this. Where does VNC get it's initial DISPLAY variable set when launching?
_________________
Before you insult someone, it is often best to walk a mile in their shoes.

That way when you insult them you're already a mile away and have their shoes.

hackerError · Posted: Mon Dec 20, 2010 3:20 pm Post subject: :?:

Is there somewhere that tightvnc stores DISPLAY variable by default? They charge $100 per incident tech support, and I'm not at that point... yet.
_________________
Before you insult someone, it is often best to walk a mile in their shoes.

That way when you insult them you're already a mile away and have their shoes.

bendagr8 · Posted: Sun Jan 02, 2011 7:35 pm Post subject:

I am having the exact same problem. Perhaps this is you? https://bugs.gentoo.org/show_bug.cgi?id=349272

I've been really stumped on trying to figure out what's going wrong. I too feel it's some variable not being set properly, but I don't think it's the DISPLAY variable. Like the bug suggests, I think the problem is either in X, or fluxbox.

The only things I will add are: TWM works fine, and using the -display option for fluxbox doesn't seem to make the problem go away. I'm completely stumped.

Here's my current workaround, which is good enough for me since I usually run these sessions for a long period of time.
Change xstartup to launch twm.
Start the vnc server, and connect.
Within twm create a new xterm.
In that new xterm kill twm, and other stuff you don't want.
From that xterm start fluxbox.

Gusar · Posted: Sun Jan 02, 2011 7:37 pm Post subject:

No guarantee that it will fix things... but have you tried tigervnc?

bendagr8 · Posted: Sun Jan 02, 2011 7:47 pm Post subject:

The bug I linked was against tigervnc.

Edweirdo · Posted: Tue Jan 04, 2011 2:39 am Post subject:

I have this problem, but not only with VNC. I also have it with multiple monitors. If run anything in display :0 everything is fine, but when I try it in :1 nothing happens. I don't think it is VNC related.
_________________
Life is too short and too important to { take seriously | use Windows }.

hitman_bond007 · n00b Joined: 07 May 2004 Posts: 15 Location: NC

Changing $DISPLAY from :1 to :1.0 before launching fluxbox seems to make it work for me.

I made the following change in my ~/.vnc/xstartup.

From:

bendagr8 · Posted: Thu Jan 06, 2011 12:54 am Post subject:

hackerError · Posted: Thu Jan 06, 2011 3:50 pm Post subject:

Edweirdo · Posted: Thu Jan 06, 2011 7:54 pm Post subject:

I originally had:

hackerError · Posted: Fri Jan 07, 2011 4:38 pm Post subject:

I'll try that when I get home, however I wonder if it might cause issues on my local session.

My setup is dual monitors, with 0.0 being the right monitor, and 0.1 being the left, do you think adding the explicit .0 to the xinitrc will affect the 0.1 display?
_________________
Before you insult someone, it is often best to walk a mile in their shoes.

That way when you insult them you're already a mile away and have their shoes.

hanj · Veteran Joined: 19 Aug 2003 Posts: 1496

bendagr8 · Posted: Sat Jan 15, 2011 5:29 am Post subject:

I ended up having to do an emerge -e system; emerge -e world as a result of a botched upgrade from ext3->ext4.

After this, everything is back to normal. So now unfortunately I don't know what fixed the problem.

hitman_bond007 · n00b Joined: 07 May 2004 Posts: 15 Location: NC