Forum Home
Press F1
Thread ID: 37163	2003-08-30 11:33:00	COBRA errors in GNOME - Red Hat 9	Jen C (20)	Press F1

Post ID	Timestamp	Content	User
171744	2003-08-30 11:33:00	I have done something nasty to GNOME ... not sure which things contributed to it (about from the user). In Red Hat 9 I normally use KDE, and I hardly use GNOME. The last couple of times I have loaded GNOME I had noticed that the taskbar had lost the previous colour setting and was all black. However, I was having a bit of a fiddle last night with switching consoles (had never tried this before) and whilst in KDE I tried CTRL-ALT-F1 to see what would happen. Not sure quite what happened but I did end up with a CLI only and after some more fiddling started GNOME. Memory goes very vague here, however I tried CTRL-ALT-F1 (& F2) again and got some message about server is busy and will use server 1 ?? (I think). I also got whilst starting up the GUI some error box with a 4 lettered nonsense word (mixed upper and lowercase letters) with an YES or NO option. YES seemed to be the default so I selected that. I saw that message box twice during this obviously stuffed up attempt at switching consoles. I eventually gave up on this and restarted KDE. KDE works like a charm still, however I started up GNOME tonight and it was a bit of a mess. It has a complete black-out of the desktop (as well as the previously turned black taskbar) with only the icons text being white with no visible desktop icons, however the icons in the taskbar had colour. Clicking on the GNOME panel brings up multiple error boxes "an error occured while loading or saving configuration for gnome-panel. Some of your configuration settings may not work properly" [no kidding!]. Under details it said three times: Configuration server couldn't be contacted. COBRA error: IDL:omg.org/COBRA/BAD_OPERATION:1.0 Selecting any option off the gnome-panel will also bring up the same COBRA error, but not always on the 2nd attempt at selecting that same option. The only other thing I have done recently was to update KDE to the latest version. So, is GNOME doomed from my not-to-gentle attempts at using console switching, or can it be fixed? Any advice would be appreciated, (and yes, I know I shouldn't fiddle so much but how else am I to learn :) ) TIA Jen	Jen C (20)
171745	2003-08-30 12:02:00	It might be a good idea to nuke the GUI for your current user. To do this: 1. Delete all Xwindows files in the home directory. They are all hidden ones starting with a period. For example, gnome* 2. Login as root user and delete /tmp/orbit-YourUserName 3. Restart X - you should have a brand new copy of GNOME. John	JohnD (509)
171746	2003-08-30 13:10:00	Thanks John :) That did the trick, and GNOME is back in one piece again. Cheers Jen	Jen C (20)
1