Cannot run gnome-session

64-bitgnomerhel5

I'm having issues running an X Windows session on a RHEL5 64-bit server – whenever I execute the command "gnome-session &", the process goes into the background but nothing happens. I have Exceed installed on my Windows machine which is running when I try to start the gnome-session. I've tried just starting firefox by itself instead of the whole gnome session, but it doesn't work either. Any suggestions?

BTW, here's the error message I get when I try to start firefox:

firefox: Fatal IO error 104 (Connection reset by peer) on X server localhost:10.0.

Best Answer

Have you tried issuing the startx command?

You appear to be getting the firefox error as you are launching it without a supporting X session (in your questions, gnome) running.

That's the proper way to start gnome and it should start automatically, if it doesn't than running startx manually will launch the graphical client that is specified in your /etc/X11/xinit/Xclients script file.

Check the startx manual page for more information:

man startx

That should explain how it works and where the default files are located.

Related Solutions

Automatically change the gnome-terminal “title” for the window

Take a look at your /etc/bashrc (or equivalent). Modern Linux distributions have this already in place - you just may have to enable it.

For instance, on openSuSE, it's handled by a bash function:

ppwd () 
{ 
    local _t="$1" _w _x _u="$USER" _h="$HOST";
    test -n "$_t" || return;
    test "${_t#tty}" = $_t && _t=pts/$_t;
    test -O /dev/$_t || return;
    _w="$(dirs +0)";
    _x=$((${#_w}-18));
    test ${#_w} -le 18 || _w="...${_w#$(printf "%.*s" $_x "$_w")}";
    printf "\e]2;%s@%s:%s\007\e]1;%s\007" "$_u" "$_h" "$_w" "$_h" > /dev/$_t
}

and my PS1 is:

$(ppwd \l)\u@\h:\w>

This causes my xterm & gnome-terminal title to be set to user@host:/smartpath every time the prompt is displayed.

If you're read this far, you should know that the easy way to set the title one time is:

echo -e '\e]2;Title Text\007\e]1;\007'

CommunicationException when shutting down JBoss 4.2.2

Shutdown.sh launches a separate java program that sends a JMX request to the jboss server process. It doesn't reference any configuration files to discover the new port, it just assumes the defaults. (how could it? you're not passing it your configuration directory)

So to connect to your jboss server running on the non-default port, you need to run it like so:

shutdown.sh --server=YOURHOST:1299

Also, if you're actually using the sample-binding.xml, i.e., if you uncommented the jboss.system:service=ServiceBindingManager mbean in jboss-service.xml & configured ServerName & StoreURL appropriately, then you shouldn't need to make any other configuration changes for the new ports. That's the point of the binding manager, to centralize all of that work.

Best Answer

Related Solutions

Automatically change the gnome-terminal “title” for the window

CommunicationException when shutting down JBoss 4.2.2

Related Topic