RE: [F8] Setting up VNC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



John Summerfield wrote
>Daniel B. Thurman wrote:
>> [snip!]
>> Does anyone have any recommendations as to the proper way
>> to set up VNC servers for F8?
>1. stick to realvnc. tightvnc collapses when switching to/from 
>fullscreen (several distros) (I forget which direction).
>2. Edit /etc/sysconfig/vncservers to taste. The 2 in 
>VNCSERVERARGS[2] is 
>the screen number (2) in VNCSERVERS="2:myusername"
>
>More generally, to find configuration files
>  rpm -qc <package>
>and documentation
>  rpm -qd <package>
>and for more rpm magic
>  rpm -qd rpm
>

Gah! ;)

My /etc/sysconfig/vncserver file:

VNCSERVERS="2:dant"
VNCSERVERARGS[2]="-geometry 1024x768 -depth 24"


This is the errors I am seeing in my log file:
==============================================

Xvnc Free Edition 4.1.2
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Underlying X server release 10300000, The X.Org Foundation


Wed Dec 12 16:32:28 2007
 vncext:      VNC extension running!
 vncext:      Listening for VNC connections on port 5902
 vncext:      Listening for HTTP connections on port 5802
 vncext:      created VNC server for screen 0
Could not init font path element unix/:7100, removing from list!
No profile for user 'dant' found
===== BEGIN MILESTONES (/usr/sbin/sabayon-apply) =====
MainThread 2007/12/12 16:32:37.5745 (sabayon-apply): Fatal exception!  Exiting abnormally.
MainThread 2007/12/12 16:32:37.5761 (sabayon-apply): Traceback (most recent call last):
  File "/usr/sbin/sabayon-apply", line 99, in <module>
    sys.exit (util.EXIT_CODE_FATAL)
SystemExit: 1

===== END MILESTONES (/usr/sbin/sabayon-apply) =====
===== BEGIN RING BUFFER (/usr/sbin/sabayon-apply) =====
MainThread 2007/12/12 16:32:37.5745 (sabayon-apply): Fatal exception!  Exiting abnormally.
MainThread 2007/12/12 16:32:37.5761 (sabayon-apply): Traceback (most recent call last):
  File "/usr/sbin/sabayon-apply", line 99, in <module>
    sys.exit (util.EXIT_CODE_FATAL)
SystemExit: 1

===== END RING BUFFER (/usr/sbin/sabayon-apply) =====


This configuration for the debug log can be re-created
by putting the following in ~/sabayon-debug-log.conf
(use ';' to separate domain names):

[debug log]
max lines = 1000
SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/4471,unix/unix:/tmp/.ICE-unix/4471


Tracker version 0.6.3 Copyright (c) 2005-2007 by Jamie McCracken (jamiemcc@xxxxxxxxx)

This program is free software and comes without any warranty.
It is licensed under version 2 or later of the General Public License which can be viewed at http://www.gnu.org/licenses/gpl.txt

Initialising tracker...

** (trackerd:4515): WARNING **: Tracker daemon is already running - exiting
Failure: Module initalization failed
GSynaptics couldn't initialize.
You have to set 'SHMConfig' 'true' in Xorg.conf or XFree86.conf to use GSynaptics
mail-notification-Message: Mail Notification is already running
Initializing nautilus-open-terminal extension
Initializing nautilus-image-converter extension
Initializing nautilus-flac-converter extension
seahorse nautilus module initialized

** (nm-applet:4529): WARNING **: <WARN>  applet_dbus_manager_start_service(): Could not acquire the NetworkManagerUserSettings service as it is already taken.  Return: 3


(nm-applet:4529): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table != NULL' failed

(nm-applet:4529): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(nm-applet:4529): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Initializing nautilus-search-tool extension

Gdk-ERROR **: The program 'xulrunner-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 34 error_code 3 request_code 20 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.)
aborting...

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.503 / Virus Database: 269.17.1/1181 - Release Date: 12/11/2007 5:05 PM
 


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux