tightvnc depends on non-modular xorg. Steps to reproduce: 1. emerge tightvnc --pretend localhost ~ # emerge tightvnc --pretend These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] x11-libs/libXft (is blocking x11-base/xorg-x11-6.8.2-r6) [ebuild N ] x11-base/opengl-update-2.2.4 [ebuild UD] x11-base/xorg-x11-6.8.2-r6 [7.0-r1] USE="bitmap-fonts% ipv6% nls% opengl% pam% truetype-fonts% type1-fonts% xv% -3dnow% -cjk% -debug% -dlloader% -dmx% -doc% -font-server% -insecure-drivers% -minimal% -mmx% -nocxx% -sdk% -sse% -static% -xprint%" [ebuild N ] virtual/x11-6.8 [ebuild N ] net-misc/tightvnc-1.2.9-r1 USE="tcpd -java" Also, I'm seeing that it wants to emerge opengl-update, which from what I can tell, has been replaced with eselect. Though, that's another bug for another day.
After a very, very minimal amount of poking, it looks like this should depend on several other packages, just for the build process: 1) x11-misc/gccmakedep -Used in the build 2) app-text/rman -Used in the install, man page related. With modular xorg installed, along with these two packages, emerge tightvnc --nodeps emerges just fine. However, more problems occur when starting vncserver by hand: localhost ~ # vncserver You will require a password to access your desktops. Password: Verify: Would you like to enter a view-only password (y/n)? n Couldn't start Xvnc; trying default font path. Please set correct fontPath in the vncserver script. Couldn't start Xvnc process. Couldn't open RGB_DB '/usr/X11R6/lib/X11/rgb' 20/02/06 20:37:59 Xvnc version 3.3.tight1.2.9 20/02/06 20:37:59 Copyright (C) 1999 AT&T Laboratories Cambridge. 20/02/06 20:37:59 Copyright (C) 2000-2002 Constantin Kaplinsky. 20/02/06 20:37:59 All Rights Reserved. 20/02/06 20:37:59 See http://www.uk.research.att.com/vnc for information on VNC 20/02/06 20:37:59 See http://www.tightvnc.com for TightVNC-specific information 20/02/06 20:37:59 Desktop name 'X' (localhost:1) 20/02/06 20:37:59 Protocol version supported 3.3 20/02/06 20:37:59 Listening for VNC connections on TCP port 5901 20/02/06 20:37:59 Listening for HTTP connections on TCP port 5801 20/02/06 20:37:59 URL http://localhost:5801 Font directory '/usr/lib/X11/fonts/misc/' not found - ignoring Font directory '/usr/lib/X11/fonts/75dpi/' not found - ignoring Fatal server error: could not open default font 'fixed' Couldn't open RGB_DB '/usr/X11R6/lib/X11/rgb' 20/02/06 20:38:00 Xvnc version 3.3.tight1.2.9 20/02/06 20:38:00 Copyright (C) 1999 AT&T Laboratories Cambridge. 20/02/06 20:38:00 Copyright (C) 2000-2002 Constantin Kaplinsky. 20/02/06 20:38:00 All Rights Reserved. 20/02/06 20:38:00 See http://www.uk.research.att.com/vnc for information on VNC 20/02/06 20:38:00 See http://www.tightvnc.com for TightVNC-specific information 20/02/06 20:38:00 Desktop name 'X' (localhost:1) 20/02/06 20:38:00 Protocol version supported 3.3 20/02/06 20:38:00 Listening for VNC connections on TCP port 5901 20/02/06 20:38:00 Listening for HTTP connections on TCP port 5801 20/02/06 20:38:00 URL http://localhost:5801 Font directory '/usr/X11R6/lib/X11/fonts/misc/' not found - ignoring Font directory '/usr/X11R6/lib/X11/fonts/Speedo/' not found - ignoring Font directory '/usr/X11R6/lib/X11/fonts/Type1/' not found - ignoring Font directory '/usr/X11R6/lib/X11/fonts/75dpi/' not found - ignoring Font directory '/usr/X11R6/lib/X11/fonts/100dpi/' not found - ignoring Fatal server error: could not open default font 'fixed' localhost ~ # Note that in theory, I have every possible font in portage installed, so, I'd also assume that this is a modular xorg-related thing.
1.3_alpha7 does have the dependencies. I don't think it's expected that people running stable systems would go unmasking modular X.
Ah, sorry. I actually run a stable system, just with modular xorg unmasked. In ~x86, yes, it emerges correctly, however I'm still having the font problem with the server. Sorry for the confusion.
Starts okay for me. /usr/lib/X11/fonts is a symlink to /usr/share/fonts. It has been reported though. See bug #122807.
*turns a bright shade of red* I even looked over that, too..
*** This bug has been marked as a duplicate of 122649 ***
*** Bug 124807 has been marked as a duplicate of this bug. ***
