LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   startx fails to launch and returns errors on Linux Redhat (https://www.linuxquestions.org/questions/linux-newbie-8/startx-fails-to-launch-and-returns-errors-on-linux-redhat-4175434796/)

Nanosuz 10-30-2012 02:36 PM

startx fails to launch and returns errors on Linux Redhat
 
Hello

Running startx returns a very long error (see below).

My server is running Redhat Enterprise Linux 5.5 x64 and is a host for some VMs. I am running startx to launch the GUI so that I can then launch Virtual Machine Manager.

I have connected to the server using Putty (ssh) and am logged in as root. On a sidenote I have recently inherited responsibility for my company's network and did not build this server.

Any advice would be appreciated.

Thanks,

Suzan

-----------------------------------------------------------

X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: Linux 2.6.18-194.el5 x86_64 Red Hat, Inc.
Current Operating System: Linux audi.nanometrics.ca 2.6.18-194.11.3.el5xen #1 SMP Mon Aug 23 16:12:21 EDT 2010 x86_64
Build Date: 15 April 2010
Build ID: xorg-x11-server 1.1.1-48.76.el5_5.1
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Oct 30 11:54:43 2012
(==) Using config file: "/etc/X11/xorg.conf"
(WW) MGA(0): Failed to set up write-combining range (0xd9f80000,0x70000)
(WW) MGA(0): Failed to set up write-combining range (0xd9f00000,0xf0000)
(WW) MGA(0): Failed to set up write-combining range (0xd9e00000,0x1f0000)
(WW) MGA(0): Failed to set up write-combining range (0xd9c00000,0x3f0000)
(WW) MGA(0): Failed to set up write-combining range (0xd9800000,0x7f0000)
(WW) MGA(0): Failed to set up write-combining range (0xd9f80000,0x70000)
(WW) MGA(0): Failed to set up write-combining range (0xd9f00000,0xf0000)
(WW) MGA(0): Failed to set up write-combining range (0xd9e00000,0x1f0000)
(WW) MGA(0): Failed to set up write-combining range (0xd9c00000,0x3f0000)
(WW) MGA(0): Failed to set up write-combining range (0xd9800000,0x7f0000)
(EE) MGA(0): Static buffer allocation failed, not initializing the DRI
(EE) MGA(0): Need at least 9216 kB video memory at this resolution, bit depth
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Multiple symbols for level 1/group 1 on key <I5F>
> Using XF86Sleep, ignoring XF86Standby
> Warning: Symbol map for key <I5F> redefined
> Using last definition for conflicting fields
Errors from xkbcomp are not fatal to the X server
localuser:root being added to access control list
No profile for user 'root' found
SESSION_MANAGER=local/audi.nanometrics.ca:/tmp/.ICE-unix/20716
Getting adapter list failed: The name org.bluez was not provided by any .service files
Passkey agent registration failed: The name org.bluez was not provided by any .service files

** (eggcups:20784): WARNING **: IPP request failed with status 1280

** (eggcups:20784): WARNING **: IPP request failed with status 1280
Initializing nautilus-open-terminal extension

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

** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
Unable to open desktop file /usr/share/applications/redhat-email.desktop for panel launcher: No such file or directory
Unable to open desktop file /usr/share/applications/openoffice.org-1.9-writer.desktop for panel launcher: No such file or directory
Unable to open desktop file /usr/share/applications/openoffice.org-1.9-impress.desktop for panel launcher: No such file or directory
Unable to open desktop file /usr/share/applications/openoffice.org-1.9-calc.desktop for panel launcher: No such file or directory
Introspect error: Launch helper exited with unknown return code 0
could not attach to desktop process

waiting for X server to shut down Window manager warning: Lost connection to the display ':0.0';
most likely the X server was shut down or you killed/destroyed
the window manager.

(gnome-panel:20778): libgnomevfs-WARNING **: Failed to re-activate daemon: Connection was disconnected before a reply was received
The application 'Gecko' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
..

xinit: unexpected signal 2.

-------------End of error messages-----------------------------

MensaWater 10-31-2012 10:24 AM

PuTTY doesn't support X Windows directly - you'd need an X emulator to see X Windows on your MS Windows based system. You can get that by downloading Cygwin/X for Windows.

On the server run "who -r" to determine current run level. For RHEL/CentOS run level 5 is multi-user but doesn't start X. Run level 3 is multi-user and does start X. If X is already running (e.g. the console has a GUI) then you can't run "startx" to start it again. You also don't need to. You just need to address getting X to your MS Windows based system.

Nanosuz 11-01-2012 03:19 PM

Thank you MensaWater. I was able to load startx successfully from the console. I had assumed there was something wrong with xinit configuration. I haven't been able to load Cygwin/X successfully, but Now I know it's just my remote accessibility.

Cheers,

Suzan

unSpawn 11-01-2012 05:32 PM

In addition to what MensaWater wrote:
Please edit your original post and remove the host name (no need for anyone to see it).


Quote:

Originally Posted by Nanosuz (Post 4818416)
My server is running Redhat Enterprise Linux 5.5

Then it's out of date. Update 8 (bug / security fixes, improvements) was released some time ago.


Quote:

Originally Posted by Nanosuz (Post 4818416)
I am running startx to launch the GUI so that I can then launch Virtual Machine Manager.

Depending on what virtualization product the machine runs a Virtual Machine Manager may be a standalone application you can install on any client machine without requiring the virtualization server to run Xorg. Saves resources and may be safer.


Quote:

Originally Posted by Nanosuz (Post 4818416)
I have connected to the server using Putty (ssh) and am logged in as root.

That is not a security best practice. Unless you're inside a LAN with only trusted users / machines best not make it a habit.

chrism01 11-02-2012 06:40 AM

I think MensaWater has a typo here
Quote:

Run level 3 is multi-user and does start X.
On RHEL/Centos, as he said, level 3 is multi-user/server, no X server. To automatically boot with X GUI, that should be level 5.

Se the file /etc/inittab
Code:

id:5:initdefault:

MensaWater 11-02-2012 07:58 AM

Quote:

Originally Posted by chrism01 (Post 4820391)
I think MensaWater has a typo here

Yep - it was a typo - it should have said run level 3 does NOT start X and run level 5 DOES start x. My original post has been updated to fix that.

MensaWater 11-02-2012 08:02 AM

Quote:

Originally Posted by unSpawn (Post 4820040)
That is not a security best practice. Unless you're inside a LAN with only trusted users / machines best not make it a habit.

Since PuTTY is using ssh by default connections to hosts are encrypted so I don't see how this is a major security issue beyond using any form of ssh into a system. One can of course do call back setups to increase security. I've seen a rather nice presentation on that idea but it isn't something you implement willy nilly as once you do it you also are restricted on local LAN.

unSpawn 11-02-2012 09:07 AM

Quote:

Originally Posted by MensaWater (Post 4820457)
I don't see how this is a major security issue

Simply put root should not be allowed to log in over the network.
Besides that given proper Sudo configuration it isn't even necessary.

MensaWater 11-02-2012 01:54 PM

Quote:

Originally Posted by unSpawn (Post 4820529)
given proper Sudo configuration it isn't even necessary.

I'll agree that admins should get in the habit of using sudo to become root rather than logging in directly most of the time. However on occasion ONLY the root login works. (Of course on other occasions only the console works and others only single user works.) Not every distro does the bizarre Ubuntu "sudo required for everything" setup.


All times are GMT -5. The time now is 11:31 AM.