Hi Mike, Thank you for the quick reply. Your time and help are always very appreciated. :)
To test the xf86 server X11 functionality I
* configured the xf86 server code (./configure --with-init-dir=/etc/init.d
--with-xorg-module-dir=/usr/lib64/xorg/modules/)
* built guacd using the xf86 server code
* checked - guacd has no config file, so defaults are enforce (port=4822
and hostname=localhost)
* checked - the X.org/Guac driver is in the local X11 modules directory
(/usr/lib64/xorg/modules/)
* deployed the guacamole-example war file in Tomcat with the following:
String hostname = "localhost";
int port = 4822;
GuacamoleConfiguration config = new GuacamoleConfiguration();
config.setProtocol("xorg²);
* started guacd
* started Tomcat
* hit http://localhost:8080/guacamole-example-0.9.12-incubating/ with the
local browser
* tunnel?connect returned a 504
* syslog for guacd shows "Support for protocol "xorg" is not installed²
What did I miss? I did notice the protocol directory in the xf86 server
source doesn¹t have an xorg directory. I expected to see one similar to
the other protocol plugins.
My xorg.conf file, deployed into /etc/X11, is below.
Thanks & Regards,
Jeff
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
Screen 1 "GuacScreen" LeftOf "Screen0"
#Mirror
#Screen 1 "GuacScreen" 0 0
InputDevice "GuacInput" "SendCoreEvents"
# The following is not required, but useful when debugging X with gdb.
# WIthout it, X traps segfaults itself, and gdb never gets a chance.
#Option "NoTrapSignals"
EndSection
#
# IMPORTANT: The X.Org driver doesn't support RENDER yet. This section
must be
# included, or graphical artifacts may result, particularly with
# Gnome.
#
Section "Extensions"
Option "RENDER" "disable"
EndSection
#
# Set files location and fonts
#
Section "Files"
ModulePath "/usr/lib64/xorg/modules"
FontPath "catalogue:/etc/X11/fontpath.d"
FontPath "built-ins"
EndSection
#
# Set regular video driver
#
Section "Module"
Load "glx"
EndSection
#
# Mouse and keyboard input from regular console
#
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
#
# Mouse and keyboard input from Guacamole
#
Section "InputDevice"
Identifier "GuacInput"
Driver "guac"
EndSection
#
# Video output to regular console
#
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
Identifier "Card0"
Driver "vboxvideo"
BusID "PCI:0:2:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
#
# Video output to Guacamole
#
Section "Monitor"
Identifier "GuacMonitor"
EndSection
Section "Device"
Identifier "GuacCard"
Driver "guac"
Option "ListenAddress" "0.0.0.0"
Option "ListenPort" "4823"
EndSection
Section "Screen"
Identifier "GuacScreen"
Device "GuacCard"
Monitor "GuacMonitor"
EndSection
On 4/3/17, 6:43 PM, "Mike Jumper" <[email protected]> wrote:
>On Mon, Apr 3, 2017 at 9:44 AM, McRoy, Jeffrey (GE Healthcare)
><[email protected]> wrote:
>> Hi Mike,
>>
>> I was able to get the X11 versions of the Guac client and server to
>>build
>> and deploy. I assume the guacamole.properties file for the server would
>>look
>> something like this:
>>
>> # Hostname and port of guacamole proxy
>> guacd-hostname: localhost
>
>If the X.Org driver will be running on localhost relative to the
>Guacamole web application, this is correct.
>
>> guacd-port: 4822
>>
>
>The X.Org driver listens on port 4823.
>
>> # User authorization
>> lib-directory: /Tomcat-8.5.5/webapps/guacamole-0.9.12/WEB-INF/classes
>
>I don't know why so many tutorials keep recommending this, but it is
>wrong.
>
>The "lib-directory" property was deprecated back in 0.9.7. You would
>have received a warning in the logs about the deprecation until
>version 0.9.10-incubating when support for these properties was
>removed entirely. The property no longer has any effect:
>
>http://guacamole.incubator.apache.org/releases/0.9.10-incubating/#deprecat
>ion--compatibility-notes
>
>Even back when it did have an effect, specifying WEB-INF/classes/ as
>Guacamole's lib directory would have caused the .jar files to be
>loaded by both Tomcat's classloader and Guacamole's classloader, with
>Guacamole's classloader overriding the duplicate classes loaded by
>Tomcat. I'm not sure whether this would cause issues in practice or
>not, but tying the classloaders in a knot like that just doesn't make
>sense. My best guess would be that someone got confused many years
>ago, flailed around until things worked, and then documented
>everything as-is without determining what fixed the issue, ultimately
>preserving the "lib-directory: .../WEB-INF/classes" recommendation for
>all eternity.
>
>Please follow the manual instead:
>
>http://guacamole.incubator.apache.org/doc/gug/installing-guacamole.html
>
>http://guacamole.incubator.apache.org/doc/gug/configuring-guacamole.html
>
>You will not find any reference to the deprecated properties in the links
>above.
>
>> auth-provider:
>> net.sourceforge.guacamole.net.basic.BasicFileAuthenticationProvi$
>
>As with the "lib-directory" property, the "auth-provider" property was
>deprecated back in 0.9.7. You would have received a warning in the
>logs about the deprecation until version 0.9.10-incubating when
>support for these properties was removed entirely. The property no
>longer has any effect (see deprecation notes linked above).
>
>> basic-user-mapping:
>> /Tomcat-8.5.5/webapps/guacamole-0.9.12/WEB-INF/classes/user-mapping.xml
>
>This will not hurt anything, but it doesn't make sense to store
>Guacamole's configuration files within WEB-INF/classes/. They'll be
>wiped out every time you redeploy. Please instead follow the
>installation instructions in the manual. I would recommend using the
>default location for configuration files (aka "GUACAMOLE_HOME), which
>is the ".guacamole" directory within the home directory of the user
>running the Tomcat service.
>
>>
>> Do you have an example of what the ³user-mapping.xml² file would look
>>like
>> for testing the X11 functionality?
>>
>
>The connection definition would look like:
>
> <connection name="Some Arbitrary Name">
> <protocol>xorg</protocol>
> </connection>
>
>Note the lack of parameters. The hostname/port in this case are
>dictated by the guacd-hostname and guacd-port properties (because the
>X.Org driver implements guacd). This is not the expected mechanism for
>using the X.Org driver in production - support for multiple guacd
>instances is being added to facilitate this:
>
>https://issues.apache.org/jira/browse/GUACAMOLE-189
>
>That support is present on the "xf86-video-guac" branch of
>guacamole-client in the form of modifications to the database
>authentication. If you're willing to set up the database auth using a
>build from the "xf86-video-guac" branch, that would be more intuitive.
>
>- Mike
smime.p7s
Description: S/MIME cryptographic signature
