Arch Linux

Haiyadragon

Member

Registered: 2006-03-21

Posts: 56

Tightvnc (font) problems

I'm getting a

Couldn't start Xvnc; trying default font path.
Please set correct fontPath in the vncserver script.
Couldn't start Xvnc process.

when I try to run vncserver.

I've tried several $fontPath values. All valid paths to fonts. I read someplace this might have something to do with the 64-bit version. I'm running Arch64 so...

Any ideas?

Edit:

After snooping around I found out that the real problem is Xvnc, which segfaults. Vncserver ommits the error bit running Xvnc directly reveals it. This sucks.

Last edited by Haiyadragon (2007-01-30 10:37:18)

Haiyadragon

Member

Registered: 2006-03-21

Posts: 56

Re: Tightvnc (font) problems

Ehm, anybody have an alternative? RealVNC seems to be useless the way it is built (without Xvnc). What's the point?

There must be a way to get it to work.

setti

Member

Registered: 2006-07-12

Posts: 20

Re: Tightvnc (font) problems

# pacman -Q | grep vnc
x11vnc 0.8.3-1

working very well.
Tested client: UltraVNC Viewer from windows.

Haiyadragon

Member

Registered: 2006-03-21

Posts: 56

Re: Tightvnc (font) problems

Thanks for your reply. Unfortunately x11vnc only hooks into existing X11 sessions. It's a good temporary solution thought.

ise

Developer

From: Karlsruhe / Germany

Registered: 2005-10-06

Posts: 404

Website

Re: Tightvnc (font) problems

Hi,

there is a new version in the repo. It should be fixed and everything should work.

Daniel

---

23 page
My blog

Haiyadragon

Member

Registered: 2006-03-21

Posts: 56

Re: Tightvnc (font) problems

Thanks. Xvnc doesn't segfault anymore. However, for some odd reason X crashes with anything I tried to put in xstartup. (Xfce, Gnome, KDE).

The program 'xfce4-session' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 9 error_code 2 request_code 2 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Calling startxfce4 directly works.

Before, I compiled Realvnc on Gentoo and copied Xvnc over to Arch.  Which worked perfectly.