Hello,
I have several CentOS 6.2 hosts (2.6.32-220.7.1.el6.x86_64) that lock up when attempting to use the Gnome desktop from the console. I can always log in, but then all I get is the blue root window, the round initial mouse pointer, and nothing else. The last process associated with the console is "xprop -root" which strace shows as hanging indefinitely.
There are cases (sporadic, unpredictable) when I get further; the screen contains desktop icons, the menu at the top, and an arrow mouse pointer, but the mouse and keyboard don't work. I can reproduce this behavior frequently by setting the system run level to 3, logging into the console, and running "strace -f startx".
One other bit of information: I build all the hosts with the same kickstart file, and most of the hosts work fine; only a handful are acting up.
Has anyone seen this before and/or know how to troubleshoot it?
Thanks, Jack
On Tue, 20 Mar 2012 11:21:19 -0700 Jack Bailey wrote:
Has anyone seen this before and/or know how to troubleshoot it?
Does it work if you set up a new user and log in as the new user?
If not, have you made any changes in /etc/skel?
On 20.03.2012 14:21, Jack Bailey wrote:
Hello,
I have several CentOS 6.2 hosts (2.6.32-220.7.1.el6.x86_64) that lock up when attempting to use the Gnome desktop from the console. I can always log in, but then all I get is the blue root window, the round initial mouse pointer, and nothing else. The last process associated with the console is "xprop -root" which strace shows as hanging indefinitely.
There are cases (sporadic, unpredictable) when I get further; the screen contains desktop icons, the menu at the top, and an arrow mouse pointer, but the mouse and keyboard don't work. I can reproduce this behavior frequently by setting the system run level to 3, logging into the console, and running "strace -f startx".
One other bit of information: I build all the hosts with the same kickstart file, and most of the hosts work fine; only a handful are acting up.
<snip> My first reaction would be to look at /etc/X11/xorg.conf, if there is one - the few that don't might have some odd differences from generic. Should I assume that the ones that hang are USB mice & keyboards? How old are the ones that hang?
mark
On 03/20/12 11:59, m.roth@5-cent.us wrote:
<snip> My first reaction would be to look at /etc/X11/xorg.conf, if there is one - the few that don't might have some odd differences from generic. Should I assume that the ones that hang are USB mice& keyboards? How old are the ones that hang?
Thanks for reminding me. I generated new files using "X -configure".
All the servers (both working and broken) are recent builds, fully patched.
Jack
On 20.03.2012 15:11, Jack Bailey wrote:
On 03/20/12 11:59, m.roth@5-cent.us wrote:
<snip> My first reaction would be to look at /etc/X11/xorg.conf, if there is one - the few that don't might have some odd differences from generic. Should I assume that the ones that hang are USB mice& keyboards? How old are the ones that hang?
Thanks for reminding me. I generated new files using "X -configure".
All the servers (both working and broken) are recent builds, fully patched.
Did it fix them?
mark "inquiring minds, and all that"
On 03/20/12 12:19, m.roth@5-cent.us wrote:
On 20.03.2012 15:11, Jack Bailey wrote:
On 03/20/12 11:59, m.roth@5-cent.us wrote:
<snip> My first reaction would be to look at /etc/X11/xorg.conf, if there is one - the few that don't might have some odd differences from generic. Should I assume that the ones that hang are USB mice& keyboards? How old are the ones that hang?
Thanks for reminding me. I generated new files using "X -configure".
All the servers (both working and broken) are recent builds, fully patched.
Did it fix them?
No. Using the newly-generated xorg.conf file or no conf file at all makes no difference.
Jack
On 20.03.2012 16:21, Jack Bailey wrote:
On 03/20/12 12:19, m.roth@5-cent.us wrote:
On 20.03.2012 15:11, Jack Bailey wrote:
On 03/20/12 11:59, m.roth@5-cent.us wrote:
<snip> My first reaction would be to look at /etc/X11/xorg.conf, if there is one - the few that don't might have some odd differences from generic. Should I assume that the ones that hang are USB mice& keyboards? How old are the ones that hang?
Thanks for reminding me. I generated new files using "X -configure".
All the servers (both working and broken) are recent builds, fully patched.
Did it fix them?
No. Using the newly-generated xorg.conf file or no conf file at all makes no difference.
Any USB errors in the logs of the ones that fail?
mark
On 03/20/2012 02:21 PM Jack Bailey wrote:
Hello,
I have several CentOS 6.2 hosts (2.6.32-220.7.1.el6.x86_64) that lock up when attempting to use the Gnome desktop from the console. I can always log in, but then all I get is the blue root window, the round initial mouse pointer, and nothing else. The last process associated with the console is "xprop -root" which strace shows as hanging indefinitely.
There are cases (sporadic, unpredictable) when I get further; the screen contains desktop icons, the menu at the top, and an arrow mouse pointer, but the mouse and keyboard don't work. I can reproduce this behavior frequently by setting the system run level to 3, logging into the console, and running "strace -f startx".
One other bit of information: I build all the hosts with the same kickstart file, and most of the hosts work fine; only a handful are acting up.
Has anyone seen this before and/or know how to troubleshoot it?
Thanks, Jack
It's been a long time since I've had to fix this problem, but I recall the necessity for setting the windowmanager variable to gnome before running startx.
Also you may want to try invoking startx from runlevel 5.
hth, ken
On 03/20/12 14:11, m.roth@5-cent.us wrote:
On 20.03.2012 17:09, ken wrote:
On 03/20/2012 02:21 PM Jack Bailey wrote:
<snip> > Also you may want to try invoking startx from runlevel 5. That doesn't make sense to me - runlevel 5, AFAIK, *is* X running.
Right. I am running at run level 3 so I can invoke X manually for debugging. There are no USB errors, but I got some interesting output from "Xorg -keeptty":
Build Date: 25 February 2012 04:11:35PM Build ID: xorg-x11-server 1.10.4-6.el6_2.1.0.1.centos Current version of pixman: 0.18.4 Before reporting problems, check http://wiki.centos.org/Documentation to make sure that you have the latest version. 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 Mar 20 14:25:28 2012 (==) Using config file: "/etc/X11/xorg.conf" (EE) open /dev/fb0: No such device expected keysym, got XF86TouchpadOn: line 120 of inet expected keysym, got XF86TouchpadOff: line 121 of inet expected keysym, got XF86TouchpadOn: line 120 of inet expected keysym, got XF86TouchpadOff: line 121 of inet
No framebuffer?
# ls -l /dev/fb0 crw-rw---- 1 root root 29, 0 Mar 17 13:32 /dev/fb0
# lsattr /dev/fb0 lsattr: Operation not supported While reading flags on /dev/fb0
On 03/20/2012 04:31 PM, Jack Bailey wrote:
On 03/20/12 14:11, m.roth@5-cent.us wrote:
On 20.03.2012 17:09, ken wrote:
On 03/20/2012 02:21 PM Jack Bailey wrote:
<snip> > Also you may want to try invoking startx from runlevel 5. That doesn't make sense to me - runlevel 5, AFAIK, *is* X running.
Right. I am running at run level 3 so I can invoke X manually for debugging. There are no USB errors, but I got some interesting output from "Xorg -keeptty":
Build Date: 25 February 2012 04:11:35PM Build ID: xorg-x11-server 1.10.4-6.el6_2.1.0.1.centos Current version of pixman: 0.18.4 Before reporting problems, check http://wiki.centos.org/Documentation to make sure that you have the latest version. 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 Mar 20 14:25:28 2012 (==) Using config file: "/etc/X11/xorg.conf" (EE) open /dev/fb0: No such device expected keysym, got XF86TouchpadOn: line 120 of inet expected keysym, got XF86TouchpadOff: line 121 of inet expected keysym, got XF86TouchpadOn: line 120 of inet expected keysym, got XF86TouchpadOff: line 121 of inet
No framebuffer?
# ls -l /dev/fb0 crw-rw---- 1 root root 29, 0 Mar 17 13:32 /dev/fb0
# lsattr /dev/fb0 lsattr: Operation not supported While reading flags on /dev/fb0
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
There may be things that start at runlevel 5 that are not one at runlevel 3.
do a "chkconfig --list" and start any services that are 3:on and 5:off before you "startx".
-
Frank Cox -
Jack Bailey -
Johnny Hughes -
ken -
m.roth＠5-cent.us