[Linux-cluster] Issue with KDE with kernel later than 2.6.18-53.1.21
Corey Kovacs
corey.kovacs at gmail.com
Wed Feb 4 17:37:02 UTC 2009
I had a similar problem. Reducing my rsize back to 8k from 32k fixed
it. Problem root was the lock files in the .qt directory.
Regards,
Corey
On Feb 4, 2009, at 16:00, Randy Brown <randy.brown at noaa.gov> wrote:
> We are seeing a very strange issue with KDE with all kernels later
> than 2.6.18-53.1.21 on our cluster nodes. When users attempt to log
> into the machine using KDE, it never makes it to the KDE splash
> screen. The machine just hangs on a solid blue screen. I can then
> restart the Xserver and login using Gnome, and it logs in without
> any issues. Unfortunately, for us, KDE is the standard desktop
> environment used by our development group. I can reboot the the
> cluster to the 2.6.18-53.1.21 kernel and both KDE and Gnome work as
> expected. Obviously, I'd prefer to be running the latest kernel. I
> will gladly provide more info if needed. Any help or suggestions
> would be greatly appreciated.
>
> Randy
>
> Info about our cluster:
> It is a 2 node cluster running Centos 5 with up to date patches. I
> am using the cluster as a NAS head to serve NFS mounts out to our
> network from an iscsi SAN.
>
> Current running kernel:
> 2.6.18-53.1.21.el5 (Running this kernel so KDE logins work)
>
> Most current installed kernel:
> 2.6.18-92.1.22.el5
>
> Cluster packages:
> lvm2-cluster-2.02.32-4.el5
> cman-2.0.84-2.el5_2.3
> gfs2-utils-0.1.44-1.el5_2.1
> rgmanager-2.0.38-2.el5_2.1
> <randy_brown.vcf>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
More information about the Linux-cluster
mailing list