Humor me, but its Quiz time: What are you entering in place of PASSWD bolded above?
a. That exact phrase PASSWD?
b. The 32 hex as found in the gui_rpc_auth.cfg file?
c. The simplified password you entered in place of the 32hex in the gui_rpc_auth.cfg file?

If you simplified the password, did you restart BOINC? Never tried it, but who knows does it remember the password it was started with.

On the display issue:

What language is your OS run in? Found a German and Italian article suggesting that during compiling of the XXXX package, the translation was not performed correctly. The reports highlighted different fonts. Think Didactylos is right. Rip the BOINC instance out and get a reliable version for your distro.... 5.4.11..... change to a popular Linux distro like Ubuntu might also do the trick.

Per the BOINC FAQ

* think a few CA's wipe sweat off forhead.

Since you opened this thread, go to first post, hit the little pencil next to title and insert with brackets [RESOLVED] in the post header and hit "Edit a Post" at bottom, so all know the case is closed.

cheers

Oh and yes i saw that command a few days ago. It think you have to omit the http:// part. The process tries a secure transaction which is not on http. If you look in the My grid > My profile page you see at bottom that BOINC Project URL: www.worldcommunitygrid.org . If the command is wrong, you wont get the account key to populate a local xml file. Without that no authorization/authentication.

Added: Word is, as long as the www.worldcommunitygrid.org string is part of the url, will it be able to proceed, but suggest to stick to the instructions by the letter.

The BOINC -no_gui_rpc is covered in a Bug Report:

Bug#362257: boinc-client: -no_gui_rpc option is poorly named and misleading
Steffen Moeller moeller at inb.uni-luebeck.de
Thu Apr 13 12:57:24 UTC 2006
    
Greetings

Steffen

Am Donnerstag 13 April 2006 13:49 schrieb Frank S. Thomas:
> Would be
>    -no_gui_rpc
>                don't allow GUI RPC connections, don't make socket.
>                If this option is given the client can't be controlled
>                by the BOINC command tool (boinc_cmd) or the BOINC Manager
>                (boincmgr) or other tools that use RPCs to communicate
>                with the client.

    -no_gui_rpc
                omits creation of the socket (a file as communication channel) 
as required for the remote control ot the client. Consequently the client
cannot be monitored by external tools like GUIs (boincmgr etc.) or the console 
command tool (boinc_cmd).

That's not the whole story - there's an issue with the version of GTK being used.