[FreeNX-kNX] (FreeBSD) session startup problems
dewey hylton
freenx at deweyonline.com
Wed Aug 9 13:24:46 UTC 2006
Quoting Mark Nernberg <marknernberg at gmail.com>:
>
> On Aug 8, 2006, at 10:20 PM, dewey hylton wrote:
>
> > Quoting Mark Nernberg <marknernberg at gmail.com>:
> >
> >> On Aug 8, 2006, at 7:57 PM, dewey hylton wrote:
> >>
> >>> Quoting Mark Nernberg <marknernberg at gmail.com>:
> >>>
> >>>> I built it from ports.
> >>>>
> >>>> The server's log is:
> >>>>
> >>>> -- NX SERVER START: -c /usr/X11R6/NX//bin/nxserver
> >>>> HELLO NXSERVER - Version 1.4.0-44 OS (GPL)
> >>>> NX> 105 hello NXCLIENT - Version 1.4.0
> >>>> NX> 134 Accepted protocol: 1.4.0
> >>>> NX> 105 SET SHELL_MODE SHELL
> >>>> NX> 105 SET AUTH_MODE PASSWORD
> >>>> NX> 105 login
> >>>> NX> 101 User: marknern
> >>>> NX> 102 Password:
> >>>> Info: Auth method: passdb ssh
> >>>> NX> 103 Welcome to: echo.1fast.us user: marknern
> >>>> NX> 105 listsession --user="marknern" --status="suspended,running"
> >>>> --geometry="1024x768x16+render" --type="unix-xdm"
> >>>> NX> 127 Sessions list of user 'marknern' for reconnect:
> >>>>
> >>>> Display Type Session ID Options
> >>>> Depth
> >>>> Screen Status Session Name
> >>>> ------- ---------------- -------------------------------- --------
> >>>> -----
> >>>> -------------- ----------- ------------------------------
> >>>>
> >>>>
> >>>> NX> 148 Server capacity: not reached for user: marknern
> >>>> NX> 105
> >>>
> >>> excellent; i'm glad someone is using it. let's see the session log;
> >>> that's where
> >>> the helpful information tends to hide, at least for my problems.
> >>> you may want/
> >>> need to set SESSION_LOG_CLEAN=0 and NX_LOG_LEVEL=7 in your
> >>> node.conf first ...
> >>>
> >>
> >> Those are both set in node.conf, and this is all that is logged.
> >>
> >> I also posted some other examples to the list from other session
> >> settings on the client.
> >>
> >> Do you think the problem is a setting within X11, or is this an NX
> >> problem?
> >>
> >
> > you're showing the nxserver log, not the session log. look for
> > ~username/.nx/$sessionid/session
> > where $sessionid looks something like this:
> > F-C-hostname-1000-7134D0B0F3F17EF242BA664E1F5C961F
> >
>
> cat /var/log/nxserver.log
> -- NX SERVER START: -c /usr/X11R6/NX//bin/nxserver
> HELLO NXSERVER - Version 1.4.0-44 OS (GPL)
> NX> 105 hello NXCLIENT - Version 1.4.0
> NX> 134 Accepted protocol: 1.4.0
> NX> 105 SET SHELL_MODE SHELL
> NX> 105 SET AUTH_MODE PASSWORD
> NX> 105 login
> NX> 101 User: marknern
> NX> 102 Password:
> Info: Auth method: passdb ssh
> NX> 103 Welcome to: echo.1fast.us user: marknern
> NX> 105 listsession --user="marknern" --status="suspended,running" --
> geometry="1024x768x16+render" --type="unix-application"
> NX> 127 Sessions list of user 'marknern' for reconnect:
>
> Display Type Session ID Options
> Depth Screen Status Session Name
> ------- ---------------- -------------------------------- --------
> ----- -------------- ----------- ------------------------------
>
>
> NX> 148 Server capacity: not reached for user: marknern
> NX> 105 startsession --virtualdesktop="1" --application="twm" --
> link="adsl" --backingstore="1" --nodelay="1" --encryption="1" --
> cache="8M" --images="32M" --samba="1" --media="1" --mediahelper="esd"
> --session="echo" --type="unix-application" --cookie="******" --
> geometry="fullscreen" --kbtype="pc102/en_US" --screeninfo="1024x768x16
> +render"
>
> &virtualdesktop=1&application=twm&link=adsl&backingstore=1&nodelay=1&enc
> ryption=1&cache=8M&images=32M&samba=1&media=1&mediahelper=esd&session=ec
> ho&type=unix-
> application&cookie=******&geometry=fullscreen&kbtype=pc102/
> en_US&screeninfo=1024x768x16
> +render&clientproto=1.4.0&user=marknern&userip=192.168.254.20&uniqueid=D
> 32356BB2C7F3DB631D08FA9D276FA56&display=1001
> Password:
> NX> 1000 NXNODE - Version 1.4.0-44 OS (GPL)
> NX> 700 Session id: echo.1fast.us-1001-D32356BB2C7F3DB631D08FA9D276FA56
> NX> 705 Session display: 1001
> NX> 703 Session type: unix-application
> NX> 701 Proxy cookie: 270811e84091e4be9e4ed6fc4e5edd60
> NX> 702 Proxy IP: 127.0.0.1
> NX> 706 Agent cookie: 699b6d85b2f19292ce7b12ab251214b4
> NX> 704 Session cache: unix-application
> NX> 707 SSL tunneling: 1
> NX> 1004 Error: nxagent failed to start with: Unrecognized option: 1
> NX> 105 NX> 504 Session startup failed.
> NX> 1001 Bye.
> quit
> Quit
>
> echo# cat session
>
> Warning: Option -bs without arguments disables backing-store.
> Warning: Use -bs [forced|when_requested|never] to set required mode.
> Unrecognized option: 1
> use: X [:<display>] [option]
> -a # mouse acceleration (pixels)
> -ac disable access control restrictions
> -audit int set audit trail level
> -auth file select authorization file
> bc enable bug compatibility
> -br create root window with black background
> +bs enable any backing store support
> -bs disable any backing store support
> -c turns off key-click
> c # key-click volume (0-100)
> -cc int default color visual class
> -co file color database file
> -core generate core dump on fatal error
> -dpi int screen resolution in dots per inch
> dpms enables VESA DPMS monitor control
> -dpms disables VESA DPMS monitor control
> -deferglyphs [none|all|16] defer loading of [no|all|16-bit] glyphs
> -f # bell base (0-100)
> -fc string cursor font
> -fn string default font name
> -fp string default font path
> -help prints message with these options
> -I ignore all remaining arguments
> -ld int limit data space to N Kb
> -lf int limit number of open files to N
> -ls int limit stack space to N Kb
> -nolock disable the locking mechanism
> -logo enable logo in screen saver
> nologo disable logo in screen saver
> -nolisten string don't listen on protocol
> -p # screen-saver pattern duration (minutes)
> -pn accept failure to listen on all ports
> -nopn reject failure to listen on all ports
> -r turns off auto-repeat
> r turns on auto-repeat
> -render [default|mono|gray|color] set render color alloc policy
> -s # screen-saver timeout (minutes)
> -sp file security policy file
> -su disable any save under support
> -t # mouse threshold (pixels)
> -terminate terminate at server reset
> -to # connection time out
> -tst disable testing extensions
> ttyxx server started from init on /dev/ttyxx
> v video blanking for screen-saver
> -v screen-saver without video blanking
> -wm WhenMapped default backing-store
> -x string loads named extension at init time
> -query host-name contact named host for XDMCP
> -broadcast broadcast for XDMCP
> -indirect host-name contact named host for indirect XDMCP
> -port port-num UDP port number to send messages to
> -from local-address specify the local address to connect from
> -once Terminate server after one session
> -class display-class specify display class to send in manage
> -displayID display-id manufacturer display ID for request
> The X Keyboard Extension adds the following arguments:
> -kb disable the X Keyboard Extension
> +kb enable the X Keyboard Extension
> [+-]accessx [ timeout [ timeout_mask [ feedback [ options_mask] ] ] ]
> enable/disable accessx key sequences
> -ar1 set XKB autorepeat delay
> -ar2 set XKB autorepeat interval
> -noloadxkb don't load XKB keymap description
> -xkbdb file that contains default XKB keymaps
> -xkbmap XKB keyboard description to load on startup
> -display string display name of the real server
> -sync sinchronize with the real server
> -full utilize full regeneration
> -class string default visual class
> -depth int default depth
> -sss use software screen saver
> -geometry WxH+X+Y window size and position
> -bw int window border width
> -name string window name
> -scrns int number of screens to generate
> -install instal colormaps directly
> The NX system adds the following arguments:
> -forcenx force use of NX protocol messages assuming
> communication through nxproxy
> -imgstop int wait for confirmation from nxproxy after any
> X_PutImage bigger than int
> -getifocus mask X_GetInputFocus requests and wait for
> confirmation from nxproxy
> -imgframe let NXlib draw a tiny rectangle around images
> -imgsplit PW,PH,BW,BH force NXlib to split images to the given width
> and height
> -backingstore force backing-store on all windows
> -maxbsarea int maximum area occupied by a window candidate
> for backing-store
> -bstimeout int timeout for realizing the backing-store
> -norender disable use of the render extension
> -nopersistent disable disconnection/reconnection to the X
> display on SIGHUP
> -noshmem disable use of shared memory in path from
> remote nxproxy to the X server
> -noignore don't ignore pointer and keyboard
> configuration changes mandated by clients
>
>
>
> > that's where you'll find debugging information. all this is covered
> > in the docs,
> > even somewhat in the node.conf file you've already edited. but we
> > all know the
> > more-or-less official docs are severely lacking and too many others
> > have spread
> > bad information around so it's confusing as anything. :(
> >
>
> Got it.
>
> > obviously freenx/nxserver both build under 6.1-release (pointy-hat
> > says so!) but
> > i have not personally tested against 6.1-release myself for actual
> > operation.
> > with all the changes to x11 and the fact that nomachine uses hacked
> > up x11
> > sources, it's bound to happen sooner or later that i'll be severely
> > broken. i
> > was never successful porting their 1.5 backend to freebsd, and
> > haven't even
> > looked at the 2.0 product yet. hopefully it's much cleaner than the
> > 1.x branch.
> > if you have any experience with x11, i'd love some help. :)
> >
>
> I have some experience, but probably not enough to be useful.
>
> > oh, and to answer your question, it's really hard to say where the
> > problem is
> > without a bit more information - though one thing i saw in what you
> > provided
> > looks more like a freenx issue than nxserver (well, more like some
> > core os
> > utility that freenx depends on has changed - this happens with
> > relative
> > frequency in freebsd, but of course i've maintained this through 3
> > major
> > branches of freebsd, 4.x-6.x).
>
> It looks like its passing some wierd option to X?
hrm, what client and version are you using? please try using a 1.5 client if
you're using a 2.x client.
More information about the FreeNX-kNX
mailing list